[11:36] <bdrung> who decided about this list: https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel/extension-list
[11:39] <chrisccoulson> bdrung, me
[11:39] <chrisccoulson> although other people have looked at it too
[11:40] <bdrung> chrisccoulson: why can bugmail-extension stay, but pwdhash has to go. both work, but pwdhash has six times more users
[11:40] <bdrung> s/\./?/
[11:40] <chrisccoulson> oh, bugmail-extensions could probably go too tbh
[11:41] <bdrung> and downloadstatusbar?
[11:41] <bdrung> bindwood?
[11:42] <chrisccoulson> bdrung, bindwood is canonical maintained and we don't ship a xpi file for that
[11:42] <chrisccoulson> extensions that aren't easily installable from a.m.o stay
[11:42] <persia> Why shouldn't extensions that are easily installable from a.m.o also stay?
[11:42] <chrisccoulson> and downloadstatusbar is incredibly popular and well maintained
[11:43] <chrisccoulson> persia - we're trimming down the extensions in preparation for how we're supporting firefox in the future
[11:43] <bdrung> chrisccoulson: popcon stat = 18?
[11:44] <chrisccoulson> bdrung -that's only because it appeared in the archive this cycle. i'm also using figures on a.m.o too, and downloadstatusbar is currently at 27,978,689
[11:44] <chrisccoulson> versus 91,532 for pwdhash
[11:44] <persia> Well, OK.  I'm philosophically against the concept of encouraging folks to install anything from anywhere other than the repos, but if it won't be maintained otherwise, it makes sense.
[11:45] <chrisccoulson> persia - the issue is that it's going to be difficult and time consuming to maintain these in 4 supported releases moving forwards
[11:45] <chrisccoulson> persia - this explains everything - https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel/
[11:45] <Mitch> You're against Firefox users installing extensions from its own addons site?
[11:45] <persia> Mitch: Yes.
[11:45] <bdrung> chrisccoulson: i still think that pwdhash should stay - it's maintained by me and isn't easy installable from a.m.o atm
[11:45] <persia> chrisccoulson: I understand.  It doesn't mean I like it.  It's a matter of not having an infinite number of maintainers.
[11:45]  * bdrung agrees with persia.
[11:46]  * Mitch scratches head
[11:46] <chrisccoulson> bdrung, why is it not easily installable from a.m.o? i even provided a link to the xpi on the wiki page
[11:46] <bdrung> chrisccoulson: you have to edit install.rdf to allow FF 3.6
[11:48] <bdrung> Mitch: this is an example why a debian package is better ^
[11:48] <chrisccoulson> bdrung - well, it works here from a.m.o
[11:49] <chrisccoulson> and i disagree there. i'm sure if you looked at all the extensions on a.m.o, you will find plenty of them with various problems which mean they don't work properly, but that's not a good reason to package them in our archive
[11:49] <chrisccoulson> in fact, i think that's a good reason *not* to package them
[11:49] <bdrung> chrisccoulson: "PwdHash 1.7 konnte nicht installiert werden, da es nicht kompatibel mit Firefox 3.6.3 ist." - not compatible with FF 3.6.3
[11:49] <Mitch> bdrung: You can't always bump the maxVersion and expect it to work.
[11:49] <chrisccoulson> bdrung - well, i just installed it from there and it's working fine
[11:50] <bdrung> Mitch: i know, but in this case the extension needs no modification
[11:50] <bdrung> chrisccoulson: with FF 3.6?
[11:50] <chrisccoulson> bdrung - yes
[11:51] <persia> chrisccoulson: It's a philosophical thing: my packaging it, we can patch it to work, and provide some expectation to users that it should work.  By not packaging popular stuff, we encourage users to pull from other sources, which may spread to e.g. PPAs, and cause systems to become unstable through no fault of our own.
[11:51] <bdrung> chrisccoulson: but why does mine FF complain about it?
[11:52] <chrisccoulson> persia - i've deliberately tried to keep some of the most popular extensions though
[11:52] <chrisccoulson> we just want to keep the number to a mimimum so we don't have to spend ages fixing them each time we update firefox in the stable release
[11:53] <bdrung> chrisccoulson: you agree, that this issue is a lack of manpower?
[11:53] <chrisccoulson> we can't have extensions blocking firefox updates, and users won't be happy if we update firefox and break all their extensions until we find the time to fix them all
[11:54] <chrisccoulson> bdrung - yes, but the answer is not increasing manpower
[11:54] <persia> chrisccoulson: Like I said, I understand, I'm just opposed.  To me the right solution is for firefox to have a sane release model. :)
[11:54] <chrisccoulson> persia - agreed, but that is beyond our control
[11:55] <chrisccoulson> and it's the same support model that chromium will be using too
[11:55] <chrisccoulson> that is never going to change unfortunately, so we just have to adapt our processes to that
[11:55] <persia> I thought that was still being hotly debated.
[11:55] <chrisccoulson> which bit was being debated?
[11:55] <persia> At least chromium doesn't have the annoying "you can't patch this without our approval" restriction.
[11:56] <persia> The chromium support model.
[11:56] <bdrung> chrisccoulson: really? we can release a new version of FF and it will break the extensions downloaded from e.m.o and the users will be unhappy, too
[11:56] <persia> But anyway, I'm dragging you off-topic, on to something I don't wish to debate, as it's long been decided :)
[11:56] <chrisccoulson> i'm not that familiar with chromium, but i don't think they're going to adopt the model that mozilla have been using all this time
[11:56] <chrisccoulson> bdrung - but those will be updated faster than the ones in our archive
[11:56] <Mitch> Chromium != Google Chrome.
[11:57] <chrisccoulson> Mitch, i know ;)
[11:57] <Mitch> They're not letting anyone use their name either.
[11:57] <bdrung> chrisccoulson: only if we lack manpower. e.g. pwdhash is updated in the archive earlier
[11:57] <persia> This is OK though, because it's true for *every* distribution.
[11:59] <chrisccoulson> bdrung - why would pwdhash be updated in the archive earlier? we definately don't want to be spending efforts porting extensions ourselves each time there is a firefox update
[12:00] <chrisccoulson> and if you're saying that pwdhash will be slow to be ported, then that really isn't a good argument for keeping it in the archive anyway
[12:00] <bdrung> chrisccoulson: because i updated it.
[12:01] <chrisccoulson> bdrung - so, if pwdhash was in the archive, you would be able to guarantee to support this on all 4 stable releases plus the development release?
[12:01] <bdrung> chrisccoulson: yes
[12:02] <bdrung> chrisccoulson: i am using it on a daily basis - i have an incentive to have a working version of it
[12:02] <chrisccoulson> ok, well, maybe we could keep that one then. but i'm not going to start adding lots of extensions back just because people have a preference for them
[12:03] <chrisccoulson> otherwise we would still end up with an archive full of random extensions ;)
[12:03] <persia> Which ought be fine, if we have sufficient maintainers.
[12:10] <BUGa_vacations> morning
[12:11] <persia> On a completely different topic, does anyone happen to know how the localised search providers hook referenced in bug #526411 works?
[12:17] <chrisccoulson> persia - good question, i will try and find that out
[12:17] <persia> chrisccoulson: That'd be great.  English Yahoo fails miserably for Japan, and we'd like to use yahoo.jp at least.
[12:18] <chrisccoulson> persia - oh, ok. so, you're actually asking for a locale specific search URL instead?
[12:18] <persia> Yeah.  Based on the changes, I *think* it can be set in the langpack, but I just can't find any docs on what settings are needed.
[12:19] <chrisccoulson> yeah, i'm not too sure how to provide localised search plugins at the moment
[12:22] <bdrung> chrisccoulson: do you want to keep livehttpheaders if it's updated?
[12:23] <chrisccoulson> bdrung - i'm indifferent about that one. it seems quite popular according to popcon, so i'm ok with keeping that if it gets updated
[12:24] <bdrung> chrisccoulson: a.m.o shows 2 M downloads. sage-extension (low popcon due to new package) has 2.5 M downloads. the question is where to make the cut
[12:25] <chrisccoulson> bdrung - tbh, those are all borderline really. for consistency, we should probably srop livehttpheaders (it doesn't really fall in the category of the really popular extensions like adblock and greasemonkey
[12:26] <chrisccoulson> s/srop/drop
[12:26] <bdrung> agreed
[12:27] <chrisccoulson> noscript needs updating too, and that is one that we should keep around
[12:29] <bdrung> chrisccoulson: i'll update greasemonkey - to short the todo list
[12:29] <chrisccoulson> bdrung, thanks
[12:37] <bdrung> chrisccoulson: the install.rdf from webdeveloper says maxVersion 3.5
[12:37] <chrisccoulson> bdrung - yeah, micahg thinks that was changed in debian, as that's different to the upstream version
[12:38] <bdrung> chrisccoulson: nope. upstream is the same - look into the xpi file from e.m.o
[12:39] <bdrung> chrisccoulson: it's the same issue as pwdhash. e.m.o says that it works with FF 3.6, but the install.rdf says max version = 3.5
[12:43] <chrisccoulson> now i'm confused :-/
[12:43] <bdrung> :)
[12:44] <bdrung> chrisccoulson: greasemonkey uploaded
[12:44] <chrisccoulson> thanks
[12:47] <bdrung> chrisccoulson: btw, look at http://chrispederick.com/work/web-developer/history/ -> No FF 3.6 mentioned
[13:00] <bdrung> asac: around?
[13:22] <fta2> !info closure-compiler
[14:22] <fta2> BUGabundo, http://www.tijuana.fr/wp-content/uploads/2008/11/groupe-suricate.jpg
[14:24] <BUGabundo> hihih
[14:33] <fta2> who's volunteering to package closure-compiler?
[14:33] <fta2> debian 555683
[14:56] <nijaba> Hello. Do you know of a thunderbird with enigmail bug where the pinentry window sometimes does not get displayed and TB gets stuck waiting in lucid?
[21:07] <moldo> hi, anyone using googles toolbar with firefox?- can i get favicons in the favorites?
[21:28] <BUGabundo> \o
[21:33] <fta> http://www.youtube.com/watch?v=lAl28d6tbko
[22:23] <bdrung> chrisccoulson: regarding pwdhash, upstream is very responsive. i wrote a mail today and got a response hours later. upstream knew that pwdhash works with FF 3.6. so he bumped the version via e.m.o (that's the reason that you see FF 3.6 support there)


[13:32] <c7p> hey tomswartz07
[14:05] <hannie> Hello everyone present in this channel
[14:07] <c7p>    hello hannie
[14:07] <hannie> hi c7p, sorry my presence is a bit different, CET = UTC + 2
[14:07] <hannie> not +1 like I said before
[14:08] <c7p> No worries nobody asked for help :-P
[14:09] <c7p> The problem is there no feedback from authors on how they are doing
[14:10] <hannie> perhaps later, when they have worked on their chapters
[14:10] <hannie> We can ask via the mailing list if they have an interest in chatting
[14:11] <c7p> Yap maybe that would help
[14:12] <hannie> c7p, I plan to assign editors to chapters in the coming week
[14:12] <hannie> hey stillnotcool
[14:12] <stillnotcool> hey hannie
[14:12] <c7p> Sounds good
[14:12] <stillnotcool> great to see you here
[14:12] <hannie> how are you doing?
[14:12] <c7p> Hi
[14:13] <stillnotcool> hannie: doing well.  I am working on a paper for school, but thought I would hang out here in case anyone needs help
[14:13] <stillnotcool> hey c7p
[14:13] <hannie> stillnotcool, I was just wondering if your chapter needs some screenshots
[14:13] <stillnotcool> hannie: well, I wouldn't be against the idea
[14:14] <stillnotcool> hannie: however, one of my favorite things about dealing with that chapter is not having to worry about screen shots!
[14:14] <hannie> I will see if I can come with suggestions
[14:15] <hannie> you do not have to worry about screenshots, I will do it if you agree on my choice
[14:15] <stillnotcool> Because the chapter is less about doing something task-specific with Ubuntu, it doesn't lend itself to screenshots in quite the same way other chapters do
[14:15] <hannie> fair enough
[14:16] <stillnotcool> but, since I am going to add a few references to the Ubuntu Software Center in this revision
[14:16] <stillnotcool> perhaps those sections could use some shots demonstrating the interface, etc.
[14:16] <stillnotcool> we can chat about it when the content is finalized :)
[14:16] <hannie> btw, have you seen the Unity poster for beginners?
[14:16] <stillnotcool> no; where is it?
[14:17] <hannie> Just a moment, I'll get the link
[14:17] <hannie> http://ubuntuforums.org/showthread.php?p=11872878#post11872878
[14:19] <c7p_> Got to do sth. I ll be bacj in some mins
[14:19] <hannie> http://spreadubuntu.org/en/material/brochure/1204-poster
[14:19] <hannie> c7p_, ok
[14:19] <stillnotcool> this is pretty neat, hannie!
[14:20] <hannie> yes, I like it too. Perhaps we can refer to it somewhere in the manual
[14:20] <stillnotcool> I'm looking forward to finally installing 12.04 when final papers and exams are over
[14:21] <hannie> ah, exams first of course
[14:21] <stillnotcool> Yep.  Then play. :)
[14:21] <hannie> I do not see that much difference yet
[14:22] <stillnotcool> That's good!  An LTS should't make redical changes
[14:22] <stillnotcool> er, radical
[15:30] <hannie> godbyk, are you awake already?
[21:28]  * godbyk is around now.


[00:01] <bschaefer> andyrock, wait it does. The launcher had it built in, and two functions were closely named...haha
[00:02] <bschaefer> OnWindowMaybeIntellihideDelayed vs OnWindowMaybeIntellihide haha; but there is a comment saying to remove them from oneiric...
[00:09] <andyrock> bschaefer, yeah we have a lot of TODO comments :)
[00:10] <andyrock> bschaefer, «on a sidenote the window_focus_changed doens't get called on a click to the current window»
[00:11] <andyrock> have you'already tested it?
[00:15] <bschaefer> andyrock, haha, yeah I see a lot of them
 bschaefer, «on a sidenote the window_focus_changed doens't get called on a click to the current window»
 have you'already tested it?
[00:18] <bschaefer> andyrock, yeah I tested it; it does get called
[00:19] <bschaefer> andyrock, I was looking at the wrong call back function when I tested it at first (similar names)
[00:20] <andyrock> bschaefer, you should talk with smspillaz about corner cases
[00:21] <bschaefer> andyrock, what do you mean by corner cases? Like dragging a window?
[00:21] <andyrock> bschaefer, extreme cases
[00:21] <bschaefer> andyrock, hmm I am trying to think of an example of one.
[00:22] <bschaefer> andyrock, but he would be the one to ask :). Is he on break?
[00:22] <bschaefer> andyrock, im not sure what his time zone is either
[00:23] <andyrock> you should ask smspillasz if exists extreme cases on which WindowManager::window_focus_changed signals doesn't work
[00:23] <bschaefer> yeah
[00:23] <andyrock> bschaefer, it's not on break
[00:24] <bschaefer> andyrock, it? haha
[00:24] <andyrock> ops...
[00:24] <andyrock> ;)
[00:24] <andyrock> he
[00:24] <andyrock> he just woke up
[00:24] <bschaefer> andyrock, it's ok he must be a machine or something
[00:24] <bschaefer> andyrock, really? Like 4-5 am?
[00:24] <bschaefer> andyrock, wait no...(looks up time)
[00:24] <bschaefer> 1 24
[00:25] <bschaefer> wow that is a weird time to wake up
[00:26] <andyrock> it' 8:25 am in australia
[00:26] <bschaefer> andyrock, ...I thought you said you just woke up
[00:26] <bschaefer> haha
[00:26] <andyrock> 1:24 in italy :/
[00:26] <andyrock> my english is too bad :)
[00:27] <andyrock> bschaefer, smspillaz is online ;)
[00:28] <bschaefer> andyrock, pming him :). It's more that I cant read haha
[00:28] <andyrock> bschaefer, btw are you going to be in budapest?
[00:29] <bschaefer> andyrock, when is it?
[00:30] <bschaefer> April?
[00:30] <andyrock> bschaefer, mmm no... January
[00:30] <bschaefer> andyrock, well I haven't been told about it...and still don't have a passport...
[00:31] <andyrock> :(
[00:32] <bschaefer> andyrock, well that sucks...


[03:20] <sergio-br2> thunar segfault or whatever when I Alt+Up arrow
[03:20] <sergio-br2> does it happen in vivid or willy?
[15:30] <sergio-br2> system-udevd using 100% of my cpu
[15:30] <sergio-br2> in the 8 threads
[15:31] <sergio-br2> second time this day
[15:32] <sergio-br2> http://hastebin.com/uxisorisap.css
[15:33] <knome> sergio-br2, have you filed a bug?
[15:33] <sergio-br2> not yet
[15:33] <sergio-br2> what's the package?
[15:36] <knome> try udev
[15:37] <Unit193> systemd.
[15:37] <krytarik> sergio-br2: knome is right.
[15:37] <sergio-br2> systemd or udev ? :/
[15:37] <genii> udev is indicated by packages.ubuntu.com
[15:38] <sergio-br2> ok
[15:38] <Unit193> 'udev' is a binary package of source package 'systemd'
[15:38] <sergio-br2> weird, I closed some programs here, and now it's ok
[15:38] <sergio-br2> virtual box was one of them
[15:38] <krytarik> Unit193: Hah, indeed. :)
[15:39] <Unit193> (and it is systemd-udevd, to be precise.)
[15:43] <sergio-br2> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1498070
[15:51] <xubuntu239> could you help me? how do you start up window manager?
[15:54] <knome> xubuntu239, what have you done in order to not make it start up automatically?
[17:54] <m3n3chm0> dear all guys, I would like use WICD instead of network-manager
[17:54] <knome> dear m3n3chm0, you are free to
[17:54] <m3n3chm0> may I purge network-manager package and also dependences
[17:55] <knome> you're very welcome, sir
[17:55] <m3n3chm0> or just unmark from start-aplications network-manager and keep it installed ¿?
[17:55] <knome> i think installing wicd might just remove it anyway.
[18:01] <m3n3chm0> nope
[18:01] <m3n3chm0> because in wicd I setup static IP and in network-manager it's DHCP enabled
[18:02] <m3n3chm0> and it's taking DHCP IP... :(
[18:02] <m3n3chm0> mmmm so I don't know how to purge network-manager
[18:02] <m3n3chm0> just sudo purge network-manager-*
[18:07] <koegs> dont forget apt-get
[18:08] <m3n3chm0> aptitude :)
[18:09] <m3n3chm0> mmm question, dependencies unresolved ¿?
[18:10] <m3n3chm0> xubuntu-core recomienda network-manager-gnome      xubuntu-desktop recomienda network-manager-gnome
[20:20] <atrika> hello, i've manually built and "make install" gtk 3.16 because I needed some new feature, but now my lightdm greeter isnt able to launch because ubuntu_menu_item_factory_get_type is not in libido3-0.1.so.0. help!
[20:21] <knome> atrika, building stuff kind of voids your "warranty"...
[20:22] <Unit193> It may have a  make uninstall  though.
[20:22] <knome> that's what i'd do
[20:23] <atrika> is there a way i can find which package has done this?
[20:24] <atrika> i did keep all the makefiles and libraries in case i needed to uninstall them, I will try this now
[20:26] <genii> When there's no "make uninstall" sometimes "make distclean" works
[20:27] <atrika> ok i'll try rebooting now, wish me luck
[20:33] <atrika> ok, it still doesnt work and now nm-applet wont launch because nm-applet: symbol lookup error: /usr/local/lib/libgtk-3.so.0: undefined symbol: gdk__private__, should i reinstall libgtk3?
[21:05] <Se7> hello guys
[21:05] <knome> hello
[21:06] <Se7> got a problem with dkms someone can help me please?
[21:06] <Se7> i removed dkms but now i can t install it anymore :(
[21:07] <Se7> Package dkms is not available, but is referred to by another package.
[21:07] <Se7> This may mean that the package is missing, has been obsoleted, or
[21:16] <genii> It's in Main so if it can't be found that's sort of a problem.
[21:17] <knome> Se7, which xubuntu version?
[21:17] <genii> Se7: Please try: sudo apt-get update && apt-cache policy dkms    ...and tell us what the apt-cache policy dkms   says
[21:17] <Se7> sec
[21:17] <genii> knome: EOL maybe?
[21:17] <knome> genii, maybe.
[21:18] <Se7>  apt-cache policy dkms
[21:18] <Se7> dkms:
[21:18] <Se7>   Installed: (none)
[21:18] <Se7>   Candidate: (none)
[21:18] <Se7>   Version table:
[21:18] <Se7>      <IP_ADDRESS>-1.1ubuntu5.14.04 0
[21:18] <Se7>         100 /var/lib/dpkg/status
[21:18] <knome> !pastebin | Se7
[21:18] <Se7>  sorry
[21:19] <genii> !info dkms saucy
[21:19] <genii> meh
[21:20] <Se7> so can t install it?
[21:20] <knome> Se7, which xubuntu version are you running?
[21:20] <genii> Se7: What says result of: cat /etc/issue
[21:21] <Se7> Ubuntu 14.04.2 LTS \n \l
[21:21] <genii> So not EOL
[21:21] <knome> Se7, please run 'sudo apt-get update', then 'sudo apt-get dist-upgrade'
[21:21] <Se7> done
[21:22] <genii> Were there any errors?
[21:22] <Se7> no problem at all
[21:22] <knome> Se7, now run 'cat /etc/apt/sources.list | pastebinit' and paste us the url you get
[21:22] <Se7> ok sec
[21:23] <Se7> http://paste.ubuntu.com/12517375/
[21:25] <genii> Ouch, PPAs and Debian repos directly in the sources.list
[21:26] <knome> Se7, so can you pastebin the whole output of 'sudo apt-get install dkms'
[21:26] <Se7> yep because i ve got an ubuntu phone :)
[21:27] <knome> so you're running xubuntu with your ubuntu phone? that's not really supported..
[21:27] <Se7> http://paste.ubuntu.com/12517397/
[21:27] <Se7> noo
[21:27] <Se7> ubuntu run ubuntu phone
[21:27] <Se7> xubuntu desktop :)
[21:28] <knome> maybe you should ask somebody in the ubuntu phone channels
[21:28] <Se7> no
[21:28] <knome> no?
[21:28] <Se7> the problem it s in xubuntu desktop
[21:28] <knome> ok, well, xubuntu desktop isn't supported for ubuntu phone
[21:29] <Se7> doesn t mean nothing
[21:29] <Se7> i don t talk about phone :)
[21:29] <knome> aha... right. sorry, i've misunderstood then
[21:29] <Se7> i m talking dkms installing in xubuntu
[21:29] <Se7> lol
[21:29] <genii> Se7: Please clarify: Is this sources.list file from a computer running Xubuntu but that you use for flashing ubuntu touch, or is this sources.list from a phone running ubuntu touch with XFCE on it?
[21:30] <Se7> source from xubuntu desktop
[21:30] <knome> everything seems to be correct in the sources list (the PPAs do not mess with dkms), but then something must be wrong, because dkms is totally available for trusty
[21:30] <knome> !info dkms trusty
[21:30] <Se7> and yes the ppa it s for ubuntu phone
[21:30] <genii> knome: sources.list has EXTRAS main repo, but I don't see the normal Main entry
[21:31] <Se7> 'i have disinstalled dkms
[21:31] <knome> genii, yeah, actually, you are right...
[21:31] <genii> Only multiverse and universe
[21:31] <Se7> and when i e tried to reinstall the problem came up :(
[21:31] <knome> i wonder how that happened
[21:32] <knome> Se7, in lines 18 and 19, add 'main' after 'trusty'
[21:32] <knome> deb http://archive.ubuntu.com/ubuntu trusty main multiverse universe
[21:32] <knome> deb-src http://archive.ubuntu.com/ubuntu trusty main multiverse universe #Added by software-properties
[21:32] <Se7> yes?
[21:32] <knome> Se7, yes?
[21:32] <knome> Se7, please re-read.
[21:32] <Se7> yes tell me i was listen :)
[21:32] <knome> i told you already
[21:32] <knome> re-re-read.
[21:33] <Se7> but you didn t tell ma what i have to do
[21:33] <knome> or if you prefer GUI, open the software sources dialog and enable main there
[21:33] <knome> yes i did
[21:33] <knome> i'll repeat the line:
[21:33] <knome> 00:32  knome: Se7, in lines 18 and 19, add 'main' after 'trusty'
[21:34] <Se7> lol
[21:34] <knome> after that, i pasted you the lines how they should be after you did that
[21:34] <Se7> sorry my fault
[21:34]  * knome prescribes 10 lessons in reading
[21:35] <knome> once you've done that, run the update and dist-upgrade commands again
[21:36] <Se7> ok done without problem
[21:36] <Se7> 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade
[21:37] <genii> apt-cache policy dkms   ...say what now?
[21:38] <Se7> http://paste.ubuntu.com/12517482/
[21:41] <genii> Are you sure you ran: sudo apt-get update  ...before you ran the: apt-cache policy dkms ...?
[21:42] <Se7> yes
[21:44] <Se7> sorry i runned dist-upgrade
[21:45] <genii> Se7: Please run: sudo apt-get update
[21:45] <Se7> http://paste.ubuntu.com/12517534/
[21:46] <genii> Se7: As you can see now, line 3 shows a candidate to install for dkms
[21:46] <Se7> cai yep
[21:46] <Se7> i m installimg thank you all
[21:47] <Se7> installed without problem tnx again
[21:48]  * genii makes more coffee and wanders back to work
[21:57] <sprk3737> Hi there! I've succesfully replaced my window manager in my session by editing .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session/xfce4-session.xml , but am unable to remove xfdesktop and xfce4-panel. Is there a better way for me to be going about changing the default session applications, or more reading I can do on xfsession in particular?


[01:48] <smplman>  i have ubuntu 10.10 running on my beagleboard xm. im trying to configure my lilliput um70 7" usb touchscreen. I have the screen working with the display link drivers, but i cant get the touchscreen to work.
[01:49] <smplman> i have looked through the input devices, but i cant find any for the usb touchscreen. I did find an event for the power button on the monitor.
[04:36] <xerebz> i'm trying to get out audio to come out of the beagle
[04:36] <xerebz> i tested powered speakers on the same file on a fresh mplayer install on my laptop and it was fine
[04:36] <xerebz> i used the speakers on the bb
[04:37] <xerebz> running the same file and mplayer but there's no sound
[04:37] <xerebz> what are some of the things i can check to see what's wrong?
[04:37] <xerebz> btw mplayer acts the exact same it looks like it's playing i just can't hear anything
[08:24] <hrw> morning
[08:35] <persia> hrw, You had a flash-kernel fix for the efikas: have you tested that with linux-linaro-imx51?  Does it work?  Has it been applied to natty?
[08:49] <hrw> persia: merging flash-kernel is still on ogra's todolist
[08:50] <hrw> persia: and I did not tested it with other kernels then own ones (or genesi one)
[08:50] <persia> Where is your branch/bug?
[08:51] <hrw> bug 671027
[08:51] <ubot2> Launchpad bug 671027 in flash-kernel "Add Efika MX Smartbook/Smarttop support" [Undecided,New] https://launchpad.net/bugs/671027
[08:57] <persia> Thanks.
[08:57] <persia> What is expected to create /boot/boot.script?
[08:57] <persia> Also, this looks like it wouldn't work for a bare install (where /boot/uImage and /boot/uInitrd don't exist yet)
[08:58] <lool> hrw: i see you're adding efikamx support in your patch as well; did you test that successfully?
[09:00] <hrw> lool: no, but genesi version had same code for both
[09:00] <hrw> lool: it is cleaned version of their code
[09:00] <lool> Ok
[09:01] <hrw> persia: I had /boot/boot.script on my system, similar one I have on panda/ubuntu. where from it came? no idea
[09:02] <hrw> persia: and this code is not perfect but works for me. there were no comments on improving code anyway
[09:02] <persia> We'll need something to create it, if we expect it to be there.  Obviously, if it's already there, fine, but consider the case where someone wants to completely reinstall.
[09:02] <persia> Also, why comment out check_subarch?
[09:02]  * persia is currently trying to provide comments on code
[09:03] <hrw> persia: let me boot efika to check at original code
[09:03] <persia> Thanks.  If you're busy with something else, feel free to tell me to ask about this another time :)
[09:04] <hrw> persia: add comments to the bug - this will maybe take genesi guys to react too
[09:04] <hrw> *** /dev/sda2 will be checked for errors at next reboot ***
[09:04] <hrw> I need to track down script which says that and kill it
[09:06] <hrw> persia: looks like 'check_subarch' checks does machine runs proper flavour of debian/ubuntu kernel. if this is right then it has no use on efika so far as it runs only unofficial kernels (at least with ubuntu)
[09:07] <hrw> whole flash-kernel script is full of copy/paste code ;(
[09:09] <hrw> efikamx_flash_kernel() is more or less based on code for dove
[09:13] <persia> hrw, The efika can boot with linux-linaro-imx51, so we should expect that.  That's perfectly official.
[09:23] <persia> lool, hrw: would you mind attaching /proc/cpu for each of the MX and Sb to bug #718615?  Needs samples to match against the kernel selector.  Thanks!
[09:23] <ubot2> Launchpad bug 718615 in base-installer "Please add support for linux-linaro-imx51 on efika MX and efika SB" [Undecided,Incomplete] https://launchpad.net/bugs/718615
[09:29] <lool> persia: I'm not a fan of subarch detection; we're trying to build a common kernel with support for more than one SoC, so uname -r wont mean much anymore
[09:30] <hrw> persia: I have efikasb only
[09:30] <hrw> added
[09:31] <lool> persia: cpuinfo > will add when I get the chance to boot it
[09:31] <hrw> persia: efikamx can be taken from flash-kernel patch ;d
[09:31] <persia> hrw, I need the *complete* cpuinfo, for the base-installer test suite.
[09:31] <hrw> lool: subarch is used in many places other then just scripts like flash-kernel
[09:31] <persia> lool, Thanks.  no huge rush.
[09:31] <hrw> persia: mkey
[09:32] <persia> I suspect that the MX looks almost identical to the SB, but want to be careful so that I don't break MX folks.
[09:32] <persia> (especially because right now, MX works and SB doesn't, with the in-archive kernel)
[09:33] <hrw> define 'works' probably
[09:36]  * hrw -> breakfast
[09:37] <persia> The information I have is that linaro-linux-imx51 boots successfully on the MX.  I'm following upstream, and will prepare a queue of other things to get merged just after the update to 2.6.38-rc5, which *should* support SB as well.
[09:57] <lool> hrw: Where is it used?
[09:57] <lool> hrw: There is another subarch concept in d-i, which I believe is computed differently (from cpuinfo, not uname -r)
[10:02] <hrw> ok
[12:12] <hrw> persia: looks like you got all info for bug 718615 now ;)
[12:12] <ubot2> Launchpad bug 718615 in base-installer "Please add support for linux-linaro-imx51 on efika MX and efika SB" [Wishlist,Incomplete] https://launchpad.net/bugs/718615
[12:13] <persia> Cool.  Thanks.
[12:14] <persia> lool, hrw got steev to submit the cpuinfo: no need for you to hunt it up later.
[12:14] <hrw> steev has to2 and to3 efikamx so extra info were given too
[12:21] <lool> persia: thanks
[12:28] <ogra> you would need to extend archdetect to make use of the actual revision info, currently all detection is based on the Hardware: line
[12:29] <davidm> g'day persia you are around quite late today
[12:30] <persia> davidm, DMB meeting today.
[12:31] <persia> ogra, I'm going to pretend to not care, unless you see some reason why it's important to distinguish the T02 from T03 devices.
[12:32] <ogra> i dont think it is
[12:32] <ogra> just noted that the different cpuinfos wont gain you much there
[12:33] <hrw> the only difference is neon in to3 and noneon in to2 - but thats handled by kernel to not give neon cpuflag for to2
[12:35] <persia> Anyway, I'll toss them into the test cases.  Doesn't matter.
[12:35] <xerebz> does anyone have a quick link to how to fix the no audio issue for beagleboard xms?
[12:40] <rcn-ee> xerebz, http://bazaar.launchpad.net/~beagleboard-kernel/+junk/2.6-stable/view/head:/patches/beagle/0001-xM-audio-fix-from-Ashok.patch seems to work for me..
[12:43] <persia> Has that been proposed for the Ubuntu kernel?
[17:04] <JYRO> hi everybody....
[17:05] <JYRO> where I download the arm toolchain??
[17:06] <JYRO> I have the 3.3.2 version... but I need the 4.1 version
[17:11] <hrw> JYRO: which ubuntu ver you are using?
[17:12] <JYRO> one moment please while I see that
[17:14] <JYRO> jaunty, and <IP_ADDRESS> kernel
[17:20] <hrw> sorry, there are cross toolchains for lucid and newer only
[17:21] <JYRO> really?  :(
[17:22] <JYRO> ok.. in my laptop I have a 10.10 ubuntu version.....
[17:22] <JYRO> How I can install the arm toolchain?
[17:22] <JYRO> I have my laptop at my side
[17:22] <hrw> on 10.10: apt-get install gcc-arm-linux-gnueabi
[17:23] <ogra>  see the channel topic
[17:23] <ogra> there is a link
[17:23] <hrw> substiture gcc with g++ gobjc gfortran if want other langs
[17:24] <JYRO> this install get the utilbins too?
[17:24] <hrw> which utilbins?
[17:25] <JYRO> I need to compile a kernel for a ARM target.... just I need the toolchain?
[17:27] <hrw> you may need uboot-mkimage package too
[17:27] <prpplague> JYRO: if all you need is just a toolchain, you can try getting the codesourcery packages
[17:28] <prpplague> JYRO: http://omapedia.org/wiki/Android:_Configuring_the_Host_PC#ARM_Cross_Compiler
[17:29] <hrw> prpplague: since 10.10 ubuntu contains cross toolchain
[17:29] <prpplague> hrw: ahh
[17:29] <hrw> prpplague: took me some time to make them ;D
[17:30] <JYRO> I'm using a M-501 development kit....  in this moment I learn how to compile a kernel for a target.... then I would try probe a example module ....
[17:33] <JYRO> hrw... I try use the apt-get command and the system said that it can't found the gcc-arm-linux-gnueabi packet
[17:36] <JYRO> hrw... I'm sorry... but my ubuntu version is karmic ....
[17:37] <JYRO> is it the reason why I can't install the arm toolchain?
[17:37] <hrw> like I said - you need at least 10.04 (lucid)
[17:38] <JYRO> I'm sorry for that....
[17:39] <hrw> no need to
[17:40] <JYRO> hrw another question...  I find this page
[17:40] <JYRO> http://www.gnuarm.com/
[17:41] <JYRO> can I install this toolchain??
[17:41] <hrw> better go to http://emdebian.org or to code sourcery labs
[17:41] <hrw> I would avoid anything under gcc 4.3.3
[17:41] <hrw> which is old too
[17:42] <JYRO> who is the last gcc version??
[17:42] <hrw> 4.5.2
[17:43]  * hrw ends a day
[17:43] <JYRO> hrw... a last question...
[17:43] <hrw> go
[17:44] <JYRO> can I install debian packets in ubuntu?? I'm sorry for this question, but I newbie :$
[17:45] <hrw> I would not suggest it for a newbie.
[17:46] <JYRO> can I crash my system if I can't install it correctly??
[17:48] <JYRO> :$
[18:10] <JYRO> someone knows how I can get the public key from http://emdebian.org??
[18:14] <LetoThe2nd> JYRO: i guess you're here... and therefore, i suggest to start reading - at the top.
[18:15] <LetoThe2nd> http://www.emdebian.org/crosstools.html
[18:15] <LetoThe2nd> JYRO: there's a topic "secure apt"...
[18:16] <JYRO> LetoThe2nd... thanks for that... I read this link now
[18:17] <LetoThe2nd> JYRO: i've seen that the documentation for your specific development board is outdated and rather crappy... but in general, reading is a _very_ good idea if you want to get into arm/embedded/kernel stuff :-)
[18:19] <LetoThe2nd> JYRO: BTW - your target is not able to run ubuntu, if that's what you're heading for.
[18:20] <JYRO> LetoThe2nd...  I tell you that I need....
[18:21] <JYRO> I have a M-501 target, is a development kit for a ARM91 SoC....
[18:21] <LetoThe2nd> JYRO: i know. you told us, and i looked it up.
[18:22] <JYRO> ok... :$
[18:23] <JYRO> in this machine... I have the 3.3.2 version for arm-linux toolchain.... that's very old....
[18:23] <LetoThe2nd> JYRO: and to get you nomenclature right: it's not an "arm91" development kit, it an "arm9" platform, and in that one in the at91 family incarnation myde by atmel.
[18:23] <LetoThe2nd> JYRO: i know, you told us.
[18:24] <JYRO> ok LetoThe2nd...  thanks
[18:24] <LetoThe2nd> JYRO: but because you are asking in the #ubuntu-arm channel, there is the possibility that you might be aiming to run ubuntu on that target. and that is not possible.
[18:26] <JYRO> I know it, I don't need to run ubuntu in this target... just I need to run the 2.6 kernel linux
[18:26] <JYRO> am I in the wrong place?
[18:27] <GrueMaster> How is the natty-server-armel+dove.img even building?  I thought the dove kernel was removed from natty?
[18:29] <GrueMaster> JYRO: Unfortunately, yes.  This channel is specifically for developers discussing current ubuntu builds on current arm hardware.
[18:29] <LetoThe2nd> JYRO: a bit, yes :-) it's not much of a problem, but mainly this channel is about running ubuntu on arms, not about making arms work using ubuntu as the development platform.
[18:29] <GrueMaster> Try #debian-arm on OFTC network.
[18:29] <LetoThe2nd> JYRO: you maybe want to checkout elinux.org and see if they have an IRC channel. or if you have decided which toolchain to use, head for their channel.
[18:31] <LetoThe2nd> JYRO: specifically: http://elinux.org/Toolchains
[18:31] <JYRO> LetoThe2nd: thank you very much....
[18:32] <JYRO> GrueMaster: thank you too!
[18:36] <JYRO> it's too late for me .... I'm going for my house now...... thanks for all!!
[19:15] <prpplague> hey is there any updated info on ubuntu build for the ac100?
[20:10] <ogra> prpplague, there is a guy in the #ac100 channel hacking on getting the overlay filesystem from linux4tegra to work on it, beyond that not much, without nvidias help it will always be hackish and unstable
[20:10] <prpplague> ogra: ahh
[20:10] <ogra> look for "phh" in the channel if you want more details
[20:11] <ogra> i dont touch the L4T crap
[20:11] <prpplague> ogra: i was just curious
[20:11] <ogra> k
[20:11] <ogra> :)
[20:11] <prpplague> ogra: there were some conversation threads on some of the hardware channels about doing open source laptop/netbook design
[20:11] <ogra> heh, i doubt nvidia will ever get to that
[20:12] <ogra> they are nvidia after all
[20:12] <prpplague> ogra: sorry, the conversation turned to asking if ubuntu was available for any arm based netbook
[20:12] <ogra> ah, ok
[20:12] <ogra> yes, indeed, the image is publically available
[20:13] <prpplague> ahh dandy
[20:13]  * prpplague would love to do a omap4 netbook if only he could get the chips
[20:13] <ogra> either in my plain version that doesnt use any nvidia bits and thus has no features or in phh's version that has all features but is neither upgradeable nor stable
[20:14] <ogra> i heard it slowly gets better wrt chips
[20:14] <prpplague> ogra: indeed
[21:05]  * armin76 throws l4t at ogra
[21:06] <armin76> prpplague: you can also use gentoo :D there's some ppl on #ac100 using gentoo as well :D
[21:06] <GrueMaster> But who (in their right mind) would use gentoo?  :P

[21:07] <armin76> GrueMaster: i'm pretty sure your dreams are powered by gentoo :P
[21:07] <prpplague> armin76: hehe indeed
[21:07] <armin76> who doesn't like nice gentoo penguins? :(
[21:08] <GrueMaster> Due to international laws, I can not state publicly what powers my dreams.
[21:50] <xerebz> hello i've been given a bug patch that consists of a uimage files and a modules.tar.gz how can i apply this patch?
[23:47] <XorA> boinmg


[18:58] <olly> morning
[18:59] <ibeardslee> morning
[21:04] <chilts> morning
[21:04] <chilts> I almost typed moring - that would have been terrible


[04:39] <altmount> I oppose!
[04:40] <Randolf> altmount:  What do you oppose?
[06:06] <cpaelzer> good morning
[06:17] <Randolf> Good morning cpaelzer.
[06:22] <cpaelzer> hi Randolf, good mornign to you as well
[06:53] <lordievader> Good morning
[07:16] <Randolf> Good morning lordievader.
[07:16] <lordievader> Hey Randolf
[07:17] <lordievader> How are you doing?
[07:17] <Randolf> Good.  How are you?
[07:17] <lordievader> Doing good here :)
[10:36] <rbasak> cpaelzer: may I have your opinion please, as my potential future memcached MP reviewer?
[10:36] <rbasak> Upstream landed https://github.com/memcached/memcached/pull/285 in a "bugfix" update.
[10:37] <rbasak> Which is really for RHEL. It disables some systemd sandboxing features as RHEL's systemd doesn't support it.
[10:37] <rbasak> It does so by prefixing '##safer##' to certain lines.
[10:37] <rbasak> The RPM .spec is updated to sed them out again if the systemd is new enough.
[10:37] <rbasak> In our case, systemd is always new enough.
[10:38] <rbasak> But if I pull the new upstream and do nothing, the systemd service unit regresses by disabling this sandboxing.
[10:38] <rbasak> IMHO, it is inappropriate for upstream to ship the lowest common denominator by default.
[10:38] <rbasak> Older RHEL should patch out the lines it can't support or something. So I intend to file an issue about it.
[10:38] <rbasak> In the meantime, how should I package this in Debian?
[10:39] <rbasak> sedding them out again in debian/rules works just fine, and is reasonably future proof if upstream keeps to the same pattern.
[10:39] <rbasak> Or I could add a more rigid quilt patch.
[10:39] <rbasak> Opinion?
[10:40] <cpaelzer> rbasak: start reading ...
[10:45] <cpaelzer> rbasak: as you already said sedding as well as a patch works
[10:45] <cpaelzer> rbasak: I'm somewhat afraid that sed'ding might enable/disable random bits in the future
[10:46] <cpaelzer> I also think upstream does that the wrong way
[10:51] <rbasak> cpaelzer: so you'd prefer I add a quilt patch for now, rather than sed?
[10:58] <cpaelzer> rbasak: sort of yes, quilt + a check if there are more ##safer##
[10:58] <cpaelzer> rbasak: the check could break build
[10:58] <cpaelzer> rbasak: maybe even check count of ##safer## and if != the expected amount the packager has to check them one by one if it is ok to disable
[10:59] <cpaelzer> this could still fail if they add one and remove one upstream but you see where I'm heading to
[10:59] <cpaelzer> some sort of safety what we enable/disable with the sedding
[11:00] <cpaelzer> if at least they would have taken safer-<systemdversion> or something
[11:00] <cpaelzer> then the decision would again be where it belongs (upstream)
[11:00] <cpaelzer> but they didn't
[11:08] <rbasak> cpaelzer: perhaps a quilt patch for now, and a dep8 test to verify that ##safer## doesn't appear in the shipped service unit file?
[11:09] <rbasak> That should cover your mutate-but-count-is-same case.
[11:11] <cpaelzer> rbasak: yes
[11:11] <cpaelzer> rbasak: but dep8 is needlessly late for this
[11:12] <cpaelzer> rbasak: why not a d/rules entry that checks
[11:12] <cpaelzer> so people would realize it mcuh earlier, probably also before it is in some -proposed
[11:13] <rbasak> cpaelzer: good point. Easy enough to do in override_dh_auto_install.
[11:14]  * rbasak has filed https://github.com/memcached/memcached/issues/359
[11:19]  * rbasak has filed https://bugs.launchpad.net/memcached/+bug/1755460
[11:58] <frickler> looks like memcached maintainers are proud of the current publicity and want to make sure they can keep riding that wave? :-/
[11:59] <rbasak> frickler: huh?
[12:10] <frickler> https://blogs.akamai.com/2018/03/memcached-fueled-13-tbps-attacks.html
[12:28] <rbasak> Oh. That's something quite separate. I said "secure" in my bug summary, but it's really a different (and lower) order of magnitude of "secure" than the amplification vulnerability.
[12:29] <ahasenack> hi,
[12:29] <ahasenack> how would I go about updating a package version in ubuntu's git with a new upstream (not from debian) tarball?
[12:30] <ahasenack> non-git workflow is essentially uupdate on the new tarball
[12:30] <ahasenack> (the one I know of)
[12:30] <rbasak> I happen to have just done this for memcached (MP not up yet).
[12:30] <rbasak> I used uscan/uupdate, and then hacked things around to gitify it again.
[12:30] <rbasak> Then added one commit that changed upstream sources only (not committing the debian/changelog change made by uupdate).
[12:30] <ahasenack> git status followed by git add/remove as needed?
[12:31] <rbasak> uupdate puts everything in a different directory so I had to bring it all back, including any dotfiles (there were none in my case).
[12:31] <ahasenack> right
[12:31] <ahasenack> feels a bit error prone
[12:31] <rbasak> So a bunch of hackery done by hand, but the end result being that there's a single git commit that pulls in the new upstream but doesn't touch debian/
[12:32] <ahasenack> how does debian do it in their git, do you know?
[12:32] <ahasenack> same thing?
[12:32] <rbasak> This could be automated in the future by git ubuntu uupdate or something, but that's not implemented.
[12:32] <rbasak> gbp has some functionality to do something similar
[12:32] <rbasak> gbp import-orig
[12:32] <rbasak> Maintains a separate upstream branch
[12:32] <rbasak> gbp updates that and then merges upstream into master (and there's a --no-merge flag)
[12:32] <rbasak> That's the common gbp workflow
[12:33] <rbasak> ahasenack: in terms of error-proneness, you can gain some confidence when dpkg-buildpackage doesn't complain. As if it's a 3.0 (quilt) package, then everything apart from debian/ must exactly match the orig tarball, and the orig tarball isn't hacked with.
[12:34] <ahasenack> true, I got such errors in other occasions
[12:57] <cpaelzer> ahasenack: FYI this was a uupdate for example https://git.launchpad.net/~paelzer/ubuntu/+source/iproute2/log/?h=bionic-merge-4.14.1
[12:57] <cpaelzer> going ahead of Debian
[12:58] <ahasenack> I'll take a look, thanks
[14:33] <smoser> rbasak: do you recall the bug where you were asking to change cloud-init to manage_etc_hosts : true ?
[14:34] <rbasak> Yes. Do you want the number? :)
[14:34] <rbasak> smoser: https://bugs.launchpad.net/cloud-init/+bug/1741277
[14:37] <smoser> thanks
[16:04] <nacc> rbasak: when using a fixture with pytest.mark.parametrize, do i need to pass the fixture as a parametrized thing each time? or will pytest dtrt?
[16:05] <nacc> fixture *and* mark.parameterize
[16:05] <rbasak> I think you just add the fixtures to the def line
[16:05] <rbasak> I can't remember whether at the end or the start.
[16:06] <rbasak> But one of those should work I think.
[16:06] <nacc> rbasak: ok, i'll test to figure it out (that's what i wasn't sure of either)
[16:09] <rbasak> nacc, ahasenack: I just created https://code.launchpad.net/~racb/ubuntu/+source/memcached/+git/memcached/+merge/341340. Process question: is it a problem that usd-import-team isn't in the list of reviewers?
[16:10] <rbasak> This happened because I added the first reviewer from the MP creation page.
[16:10] <Odd_Bloke> rbasak: nacc: Adding them anywhere in the parameters should DTRT.
[16:10] <nacc> Odd_Bloke: thanks!
[16:10] <nacc> rbasak: process-wise, no, except that only usd-import-team can create the upload tag
[16:20] <nacc> rbasak: had another test question for you, if you have a moment (HO would be preferred, but I can do IRC)
[16:20] <rbasak> HO is fine. Two minutes. Standup HO?
[16:20] <nacc> rbasak: thanks
[16:53] <ahasenack> rbasak: mp is fine
[16:53] <ahasenack> wrt your question
[17:07] <ahasenack> rbasak: hm, question
[17:07] <ahasenack> rbasak: debian repacks samba's tarball
[17:07] <ahasenack> samba_4.7.4+dfsg.orig.tar.gz
[17:08] <ahasenack> upstream is like https://download.samba.org/pub/samba/stable/samba-4.7.6.tar.gz
[17:08] <ahasenack> how do I know what was changed in that +dfsg repacking? untar it and compare?
[17:13] <ahasenack> rbasak: my connection dropped, not sure you saw my dfsg question above?
[17:16] <nacc> ahasenack: gbp.conf (see debian/README.source)
[17:16] <nacc> ahasenack: (debian/gbp.conf)
[17:18] <ahasenack> I see
[17:19] <ahasenack> nacc: the filter setting in [import-orig] should be enough?
[17:20] <ahasenack> I have
[17:20] <ahasenack>   'source4/heimdal/lib/wind/rfc*txt',
[17:20] <ahasenack>   'source4/ldap_server/devdocs',
[17:20] <ahasenack>   '*chm',
[17:20] <nacc> ahasenack: based upon debian/README.source, that's what ends up munging the orig
[17:20] <ahasenack> ok
[17:28] <nacc> rbasak: i need to drop
[17:28] <rbasak> nacc: sorry, back now. That too longer than expected :(
[17:39] <nacc> rbasak: np
[17:39] <nacc> rbasak: i think your pad does write it up correctly now
[17:40] <nacc> rbasak: or, at least, mostly -- do you want to take that up next, then?
[17:40] <rbasak> nacc: yeah I guess I need to :)
[17:41] <nacc> rbasak: thanks; i'll hold off on the new tests for a bit
[17:44] <ahasenack> nacc: rbasak: could one of you please feed samba to the importer? Debian just released a new package: https://launchpad.net/debian/+source/samba/2:4.7.4+dfsg-2
[17:44] <ahasenack> it's not yet in https://code.launchpad.net/~usd-import-team/ubuntu/+source/samba/+git/samba
[17:44] <nacc> ahasenack: keep-up has not yet started
[17:44] <nacc> ahasenack: once the reimport is done (i just kicked off the remainder)
[17:44] <ahasenack> what is keep-up?
[17:44] <nacc> the normal import script that keeps up with the publisher
[17:44] <ahasenack> ok
[17:45] <ahasenack> it's a daily cron?
[17:45] <ahasenack> or a long-running daemon?
[17:45] <nacc> the latter
[17:45] <ahasenack> which you stopped because of the reimport, right?
[17:45] <nacc> right
[17:45] <ahasenack> ok, thanks
[17:45] <nacc> no publish in the last ~8 days is guaranteed to have been imported
[17:45] <ahasenack> ETA sometime today?
[17:45] <nacc> yeah
[17:45] <nacc> at least, well, to start it
[17:46] <ahasenack> ok
[17:46] <nacc> it will probably take a while to catch all the way up
[17:46] <ahasenack> ah, it's been stopped for all this time
[17:46] <ahasenack> not just since saturday?
[17:46] <nacc> since a week ago saturday, or so
[17:46] <nacc> march 5
[17:46] <ahasenack> ok
[17:46] <nacc> when i started the reimport
[17:56] <ahasenack> nacc: if we go ahead of debian in some package, does git-ubuntu merge work with that package afterwards? Let's say debian updates the version too
[17:56] <ahasenack> I saw there is a -f option to force a merge, would that do it correctly?
[17:56] <ahasenack> s/would/should/
[17:56] <nacc> ahasenack: i expect git-ubuntu merge to be pretty broken right now
[17:56] <nacc> ahasenack: due to the bug you reported
[17:57] <nacc> it needs updating for the new import algorithm
[17:57] <ahasenack> ok
[17:57] <nacc> ahasenack: you can manually tag the old, new bits and just do the rebase yourself
[17:57] <nacc> that's really all git-ubuntu merge is doing
[17:57] <ahasenack> I was just wondering about that case where we would be ahead
[17:58] <ahasenack> since the normal merge is normally with debian being ahead of us instead
[17:58] <nacc> ahasenack: wait, we're ahead of debian and still are?
[17:58] <ahasenack> in this hypothetical case, yes
[17:59] <ahasenack> the "merge" would be to just grab debian/* changes from them in that case
[18:00] <nacc> that's not an ubuntu merge then :)
[18:00] <ahasenack> correct
[18:00] <nacc> ahasenack: so, no, it wouldn't work, as git-ubuntu-merge is for ubuntu merges
[18:00] <ahasenack> "Are you sure you want to merge? (Pass -f to force the merge)." <-- was wondering what would happen with -f here
[18:00] <nacc> you'd get a weird delta that you don't really want to merge?
[18:01] <ahasenack> in other words, going ahead of debian also makes getting future changes from them harder
[18:01] <nacc> ahasenack: well, you'd cherry-pick them
[18:01] <nacc> ahasenack: you wouldn't merge to them
[18:01] <ahasenack> right, it's another process
[18:02] <nacc> right
[18:02] <nacc> i don't think it's harder, though
[18:02] <nacc> it's easier, if anything
[18:02] <ahasenack> harder because debian uploads are just one big commit
[18:02] <ahasenack> you would have to take it apart before cherry picking
[18:02] <ahasenack> or just grab what you want and apply, without cherry picking a specific commit
[18:03] <ahasenack> taking it apart is part of the merge workflow already
[18:03] <nacc> ahasenack: did you see if it's their VCS?
[18:03] <nacc> *in their
[18:03] <nacc> we don't ever take apart debian uploads, fwiw
[18:04] <ahasenack> it's there, yes
[18:04] <ahasenack> I'm just considering pros and cons of going ahead of them
[18:04] <ahasenack> and yes, we take apart our changes only, not theirs, my mistake
[18:05] <nacc> mostly because if you really carea bout that level of granularity, check the debian vcs and use that
[18:12] <hallyn> ruh roh - bionic: apt build-dep libvirt:
[18:12] <hallyn> The following packages have unmet dependencies: builddeps:libvirt : Depends: libcgmanager-dev but it is not installable
[18:12] <MitchT> Hello all.
[18:12] <hallyn> cpaelzer: ^
[18:13] <hallyn> we're inf eature freeze only so i guess i coudl push a fix for this,
[18:13] <hallyn> i assume noone else is doing a libvirt update since, well, we're in feature freeze
[18:14] <MitchT> I hope this is a decent place to ask, but has anyone attempted to deploy an azure vm using 18.04 beta?  As of March8th, all daily images are unable to deploy.  I figured it was azure. I opened a ticket and after escalation, their team confirmed that all images from March 8th+ are 'broken'
[18:14] <hallyn> kirkland: ^
[18:14] <hallyn> kirkland: who handles azure vms these days?
[18:14] <nacc> Odd_Bloke: --^ ?
[18:14] <hallyn> gonna guess not utlelmming utlemming :)
[18:15] <hallyn> meh
[18:15] <hallyn> my control keys why dey no work
[18:15]  * MitchT posts the list of what works and what doesn't https://hastebin.com/icuzavoner.css
[18:15] <hallyn> hm, but in my other vm i don't have that failed dependency,
[18:16] <Odd_Bloke> nacc: Thanks!
[18:16] <Odd_Bloke> MitchT: o/ I'm a person you can talk to about that; how are you deploying them?
[18:16] <hallyn> backports?
[18:17] <MitchT> I'm deploying using a template
[18:17] <hallyn> oh!  haha - do-release-upgrade failed me.  it did not update the release name in deb-src lines
[18:17] <nacc> hallyn: wouldn't expect backports to matter for bionic :)
[18:17] <nacc> hallyn: ah...
[18:17] <hallyn> nacc: yeah this is worse :)
[18:17] <hallyn> thanks
[18:17] <hallyn> cpaelzer: ignore me
[18:17] <MitchT> the template hasn't changed since early feb. it took me a few days to track down that if i specify that last version i have marked "OK" it will deploy.
[18:20] <MitchT> @Odd_Bloke I've found that the problem is exactly what i've described. I'm honestly out of ideas. I'm glad freenode is still around. I should know linux guys would be on IRC
[18:23] <Odd_Bloke> MitchT: OK, I can reproduce the issue, I'll dig in to it a bit more.  Thanks for reporting it here!
[18:24] <Odd_Bloke> MitchT: Could I also ask you to file a cloud-images bug at https://bugs.launchpad.net/cloud-images/+filebug, please?
[18:24] <MitchT> My IT department sits in awe at the level of support from the ubuntu team
[18:24] <MitchT> i will file a bug.
[18:36] <MitchT> Bug filed.  I hope this is helpful.   I can provide more details if needed, but its pretty straightforward. https://bugs.launchpad.net/cloud-images/+bug/1755565
[19:35] <ahasenack> hm, I have a question regarding dfsg orig tarballs
[19:35] <ahasenack> let's say I produce one
[19:36] <ahasenack> using the same exclusion rules as debian
[19:36] <ahasenack> build the ubuntu package, upload to the ubuntu archive, all is well
[19:36] <ahasenack> then debian catches up, produces the dfsg tarball too
[19:36] <ahasenack> but for some silly reason, it has a different md5
[19:36] <ahasenack> it's the same content, but different md5 because of, say, different compression level
[19:37] <ahasenack> won't that break things on our side? Because it will be the same filename, same tarball version and so on, but with a different md5 (but same content)
[20:02] <rbasak> ahasenack: yeah, that can happen. It's annoying, but sometimes unavoidable.
[22:24] <nacc> ahasenack: yeah, that's something the importer catches (and why we import origs separately for debian & ubuntu)
[22:24] <nacc> ahasenack: but it *really* should be avoided if at all possible


[01:48] <teward> sarnold: nice call on that 'security' nginx bug that wasnt a security issue OR a bug.
[01:49] <teward> bad for you though i know you're around. you may or may not have incoming.
[01:49]  * sarnold hides
[01:50] <sarnold> teward: it might still be a bug of some sort if whatever tool requests those certs was busted on the upgrade and didn't run or something
[01:50] <teward> sarnold: true, but Invalid for nginx and certbot/letsencrypt is a snap now so
[01:50] <sarnold> ah :)
[01:51] <teward> server team triage guideline for nginx when the issue is a non-package, local config issue is Invalid + general explanation based on the error in systemctl output
[01:51] <teward> it irks me people file these as security bugs tho >.<
[02:04] <sarnold> yeah, you know how it goes, folks don't know if it is or isn't, and they want to do the right thing
[02:04] <sarnold> what *really* grinds my gears is the guys reporting "hey ftp.ubuntu.com is open" "yes, thats how we distribute ubuntu, thanks" "surely my hard work deserves rewards"
[02:24] <teward> sarnold: well we call those people certain unseemly words behind their backs so :p
[02:24] <teward> versus me where I just torture you with the reminders of the mailman3 MIR that made you rage xD
[02:25]  * sarnold flips a table
[02:25] <teward> **so which of us is worse :P**
[02:25] <sarnold> teward: honestly, the *first* time hearing from any of these guys is one thing, they're looking for security problems and reporting them.. but some of these dudes have zero reading comprehension and keep reporting non-issues and demanding payment for it over and over again..
[02:27] <teward> sarnold: so reply to them with @canonical address saying "Canonical and Ubuntu do not have bug or security bounty programs, you will receive nothing if that is your intention."
[02:27] <teward> :P
[02:30] <sarnold> teward: every. single. time. I copy-and-paste the paragraph from https://ubuntu.com/security/disclosure-policy and give them the link every time and it makes no difference.
[02:31] <teward> *leaves the button that says "Ban With Orbital Strikes" on the ground in front of sarnold*
[02:32] <sarnold> hehe
[12:27] <ebarretto> ricotz, my colleague will be sponsoring it. Sorry for the delay on this, it has been a busy week, but hopefully monday it will be released. Thanks again for providing the debdiffs, it is very much appreciated!
[12:55] <ricotz> ebarretto, thank you, and don't worry; I can imagine the workload coming due to esm-apps
[16:41] <ripa> I want to Host a MEA2N  (Mongo + Express + A2+ Node) Stack app on aws free tier...
[16:41] <ripa> I came across SELinux and Apparmor.
[16:41] <ripa> I understand SElinux is harder to config
[16:41] <ripa> Please advice
[17:44] <sdeziel> ripa: on Ubuntu, it will be simpler to stick with Apparmor as that's the default LSM
[17:45] <ripa> thanks.. i feel you are right..
[17:45] <ripa> i am reading up on apparmor profiles
[17:49] <ripa> learnt a new abbrev. LSM :)
[17:49] <ripa> thanks sdeziel
[17:51] <sdeziel> ripa: np, FYI some packages come with ready made profiles but it's usually easy to create your own


[06:38] <dholbach> good morning
[07:36] <LE1> 人好少阿
[07:41] <LE1> :-D
[12:52] <AnAnt> Hello, can someone have a look at this bug #254368
[12:52] <AnAnt> I filed the bug about 2-3 weeks ago , yet no one responded to it
[14:18] <slytherin> persia: FYI ... I have been added to pkg-java project. Will do the svn setup today.
[14:19] <persia> slytherin: Excellent news.  Congratulations!
[14:19] <slytherin> persia: Now I can do major changes directly to Debian. :-D
[14:20] <persia> Well, I'm not sure that's the goal, but at least it will help keep Debian and Ubuntu in sync, as you're certainly the most active of the Java maintainers in Ubuntu.
[14:21] <persia> (or at least most visibly active)
[14:24] <slytherin> right. When we do big changes like we did for jftp, it is better if those at least get forwarded to Debian.
[14:52] <persia> Team meeting in 8 minutes in #ubuntu-meeting
[15:00] <persia> Team meeting in #ubuntu-meeting now
[21:36] <vbabiy> Hey any one know why I would be getting this error http://paste2.org/p/66985


[08:51] <bluebirch> Can't get any sound out of JACK here... drives me nuts. I did this before. Why not now?
[18:47] <katronix> Hi all, in 16.04 how do I disable LineIn via Alsa? Having issues with Google Hangouts working with my Mic
[18:49] <katronix> Wonder if I should try installing UbuntuStudio and see if that does better...
[18:57] <zequence> katronix: Ubuntu Studio uses the exact same pulseaudio server, so there will be no difference.
[18:57] <zequence> Think you are not the first person to have a problem with that. But, I never heard what caused it or what solved it
[18:58] <katronix> zequence: someone in #google suggested disabling linein
[18:58] <zequence> I suggested the guy who had problems earlier to check out #pulseaudio and #opensourcemusicians
[18:58] <zequence> Not sure you can disable the linein, but if you can, I'm sure the pulseaudio folks can tell you how it is done
[18:58] <katronix> okay
[18:59] <katronix> is opensourcemusicians another audio engine?
[18:59] <zequence> #opensourcemusicians is just a channel for the audio interested (especially those who make music on Linux)
[18:59] <zequence> There's a web page too http://opensourcemusician.com/index.php/Main_Page
[19:00] <katronix> oh ok