[00:59] <ahoneybun> xnox, vorlon: tagging you folks as I'm not sure who to tag for slideshow changes in the installer for Kubuntu: https://code.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/kubuntu-jammy/+merge/416000
[00:59] <ahoneybun> mmikowski: ^
[01:00] <vorlon> ahoneybun: I believe this has always been managed by the desktop team; pinging kenvandine who I see has uploaded it in the past
[01:05] <ahoneybun> vorlon: :star: thank you!
[01:25] <kenvandine> hey ahoneybun
[01:28] <kenvandine> ahoneybun: i requested a review from seb128
[01:30] <ahoneybun> thank you kenvandine!
[01:45] <kenvandine> ahoneybun: you're welcome
[08:53] <schopin> tumbleweed: I found an easy way to crash reverse-depends: reverse-depends -b rustc :)
[09:04] <schopin> Anyone knows of a way to get the list of binary packages from a source name? (without having to download the source...)
[09:32] <jbicha> schopin: if you just want to read the file, you can add this as a Chrome search engine/Firefox bookmark: https://sources.debian.org/src/%s/unstable/debian/control/
[09:39] <schopin> jbicha: thanks, but I'm looking for something that can be then scripted :)
[10:33] <cjwatson> schopin: apt-cache showsrc foo | grep ^Binary: ?
[10:38] <schopin> cjwatson: eh. that would have worked indeed! I ended up using custom python-apt code
[11:13] <rbasak> schopin: chdist has a src2bin command. But you need a chdist set up of course.
[12:01] <ahasenack> didrocks: hi, morning
[12:01] <ahasenack> didrocks: can you give me a hint at what was the actual failure in this adsys test with my samba 4.15.5 upload<EMAIL_ADDRESS>[12:39] <didrocks> ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server
[12:39] <didrocks> maybe the configuration option changed in the new version?
[12:39] <ahasenack> when you say "our smbd" daemon, you mean the normal smbd, but with a custom config?
[12:39] <didrocks> and hey :)
[12:40] <didrocks> indeed, normal smbd, run with a custom config for our package tests
[12:40] <ahasenack> where in the logs is that, more or less?
[12:40] <ahasenack> or the startup is hidden?
[12:40] <ahasenack> definitely some smb.conf options changed, also command line options
[12:41] <ahasenack> but I need a hint. It's fine to tell me to run the test manually, the log was just too much for a first triage, hence my ask
[12:42] <didrocks> ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16
[12:42] <didrocks> https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular
[12:42] <didrocks> you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21
[12:43] <didrocks> and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55
[12:43] <ahasenack> 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully
[12:43] <ahasenack> that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129
[12:43] <ahasenack> you wait for the port to be open?
[12:44] <ahasenack> which port is that, 445/tcp?
[12:45] <didrocks> we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking
[12:45] <didrocks> 1446
[12:45] <didrocks> https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47
[12:46] <ahasenack> huh
[12:46] <didrocks> I think I can make it better to still capture stderr in that case for easier debugging in the future
[12:46] <ahasenack> and I think I have enough to go on, I'll try this locally
[12:46] <ahasenack> see what's up with smbd on that port
[12:46] <ahasenack> thanks
[12:46] <didrocks> np! keep me posted
[12:47] <didrocks> you just need to run go test . in internal/ad/
[12:47] <didrocks> the failure is as the pre-test setup
[12:47] <didrocks> at*
[12:47] <ahasenack> didrocks: I'll file a bug against the adsys package in lp to keep track of it, but it might as well be a samba bug, I'll update the bug when I have new info, but it will be assigned to me for now
[12:48] <didrocks> ahasenack: sure, thanks!
[12:59] <tumbleweed> schopin: hah :)
[13:07] <rbasak> schopin: can we conclude something on https://code.launchpad.net/~eivnaes/ubuntu/+source/ppp/+git/ppp/+merge/415397 please?
[13:08] <rbasak> I don't want to discourage new contributors by waiting until after FF and then telling them it's too late :-/
[13:08] <schopin> rbasak: eivnaes seems invested in the issue so IMO we should take in the patch.
[13:09] <rbasak> OK, thanks. I'll review and upload it if OK then. I'm mostly going to accept the code changes as-is given (and checking that they are) upstream.
[13:09] <rbasak> And assuming there's no other fixes to it landed upstream since.
[13:15] <schopin> rbasak: was my message on the MP itself not clear enough on my +1 for the patch?
[13:16] <rbasak> Oh sorry, I hadn't seen that.
[13:16] <rbasak> Which is odd. The reason I know about the MP in the first place is because I got emailed about it.
[13:17] <rbasak> But yeah, thank you for having done that already, and sorry I hadn't seen it.
[13:17] <schopin> np :)
[14:14] <oSoMoN> bdmurray, I'm working on bug #1962021, and thinking about what will happen when the firefox deb is merely a wrapper that installs the snap, and a user does `ubuntu-bug firefox`. We'd want the bug to be reported against the firefox snap, to collect all the relevant information. Is there a mechanism in apport to let a package specify that the bug should be reported against another (snap) package?
[15:38] <bdmurray> oSoMoN: I'd think just seting the CrashDB section of the report would do see the subiquity package hook.
[15:38] <bdmurray> https://paste.ubuntu.com/p/p7sg8B6MSM/
[15:40] <jeroen___> Hello
[15:40] <jeroen___> I was wondering if it would be possible to upgrade nodejs-16 from debian-experimental for the release: https://packages.debian.org/experimental/libnode-dev
[15:41] <jeroen___> It seems stuck in Debian because it requires to update libicu, but ubuntu has this new icu: https://packages.ubuntu.com/jammy/libicu-dev
[15:42] <jeroen___> nodejs-12, which is currently in ubuntu, will be EOL by the time of the ubuntu-22.04 release: https://nodejs.org/en/about/releases/
[15:47] <jbicha> jeroen___: the version in experimental currently appears to be nodejs 14 (the version numbering can be confusing)
[15:47] <rbasak> jeroen___: that's a very late request - today is feature freeze. If someone wants to do it and take on any consequences they they can, but it's too much for me to take on right now, sorry. I don't know if that'd be the response from others or not though.
[15:48] <jbicha> I feel like updating to a new node version is a really big task and I wouldn't be able to help much with anything that breaks
[16:05] <oSoMoN> bdmurray, would that allow me to bypass the dialog that asks the user to choose whether to report a bug against the snap or the deb? (I just noticed that the snap appears to be selected by default, so that's something, but it would be even better to skip it altogether)
[16:06] <bdmurray> oSoMoN: I'd have to look into that
[16:44] <jeroen___> I had actually requested it before (including in this channel on December 6th) but there was no response. I assumed somebody was on it.
[16:46] <jeroen___> The experimental version in debian actually was nodejs 16 at some point, but I suppose they downgraded to 14 to keep i386 support.
[16:53] <rbasak> Sorry. Generally this kind of task turns out to be much more complicated than some people assume, and big tasks really need volunteers to do the work.
[16:54] <rbasak> I think it's probably too late now.
[16:54] <rbasak> But if an uploader steps up, then great.
[16:55] <rbasak> I'm just being the messenger here - I don't like to leave people hanging.
[16:55] <jeroen___> That's OK, I guess we can set up a PPA. I just thought i would let it know again, in case folks had not realized you are shipping an EOL version of a pretty important pkg...
[16:57] <jeroen___> Perhaps it can be put on the queue for 22.10 then?
[17:07] <lvoytek> hallyn: Before I get the swtpm apparmor profile uploaded, do you think my update for the home directory will cover your use case properly? Thanks! https://code.launchpad.net/~lvoytek/ubuntu/+source/swtpm/+git/swtpm/+merge/415813
[17:25] <rbasak> had not realized you are shipping an EOL version> that's not really a thing for a distribution. Most upstreams do not declare support periods like that. And just because an upstream sets some dates doesn't invalidate distribution's use of them beyond that date. It's been the norm before any upstreams did that.
[17:25] <rbasak> I mean ideally things would align, but as long as upstreams don't support some specific downstream distribution's release schedule, then there are always going to be cases where things mismatch.
[17:26] <rbasak> Put in whose queue? Like I said, we need volunteers. Otherwise it doesn't happen.
[17:27] <rbasak> One thing that is often unappreciated is that there are usually reverse dependencies of packages too, and they often need adjusting to work with the new version. So it's often not just a case of bumping the version of one package.
[17:38] <rbasak> So in ppp 2.4.9-1+1ubuntu3 I'm going to add some symbols
[17:38] <rbasak> The contributor has added things like this to the symbols file:
[17:38] <rbasak> + mppe_clear_keys@Base 2.4.9-1+1~
[17:38] <rbasak> + mppe_get_recv_key@Base 2.4.9-1+1~
[17:38] <rbasak> Is that right? Or should it be 2.4.9-1+1ubuntu3~ ?
[17:39] <rbasak> The only shared objects being shipped are plugins, so maybe it doesn't actually matter?
[17:41] <ahasenack> if an ubuntu patch is adding them, then the ubuntu version should be used
[17:41] <ahasenack> about it being plugins only, unsure, specially if you had a symbols file before
[17:41] <rbasak> I don't even understand why there's a symbols file :-/
[17:41] <ahasenack> yeah
[17:41] <rbasak> https://code.launchpad.net/~eivnaes/ubuntu/+source/ppp/+git/ppp/+merge/415397
[17:42] <rbasak> pppd.so.2.4.9 ppp #MINVER#
[17:42] <rbasak> But the package doesn't ship a pppd.so.2.4.9. Only plugins in /usr/lib/pppd/2.4.9/
[17:43] <xnox> rbasak:  i think the mppe_ functions are exported by pppd.so; with multiple plugins calling functions from pppd.so; in practice we ship all the plugins one can possibly need
[17:43] <ahasenack> what about the symbol removal?
[17:44] <rbasak> Yeah don't know either.
[17:44] <rbasak> xnox: what pppd.so though?
[17:44] <xnox> but in theory, one could also compile a third-party plugin against ppd.so
[17:44] <xnox> blah
[17:44] <xnox> not .so but daemon itself.
[17:44] <xnox> think of this equivalent to mod_apache modules
[17:44] <rbasak> I don't know how those work.
[17:44] <rbasak> I'm just trying to sponsor this
[17:45] <rbasak> If you understand what's going on, I'd appreciate your help in telling me it's correct, or what to adjust ;)
[17:46] <rbasak> https://paste.ubuntu.com/p/sbwkcYmtKB/
[17:46] <hallyn> lvoytek: ah, thanks.  sorry, my @ubuntu.com email is very unreliable.  will look at that today.
[17:46] <xnox> rbasak:  it looks mostly fine. I would only check any reverse build-deps of pppd to make sure they are all fine.
[17:46] <lvoytek> hallyn: Thanks!
[17:46] <hallyn> ("at that" - at the swtpm link, not my email :)
[17:46] <hallyn> thank you
[17:47] <rbasak> $ reverse-depends -b src:ppp
[17:47] <rbasak> ...
[17:47] <rbasak> httplib2.socks.HTTPError: (403, b'Forbidden')
[17:47] <rbasak> :-(
[17:51] <xnox> $ reverse-depends -b src:ppp
[17:51] <xnox> Reverse-Build-Depends
[17:51] <xnox> * connman                       (for ppp-dev)
[17:51] <xnox> * network-manager               (for ppp-dev)
[17:51] <xnox> * network-manager-fortisslvpn   (for ppp-dev)
[17:51] <xnox> * network-manager-l2tp          (for ppp-dev)
[17:52] <xnox> * network-manager-pptp          (for ppp-dev)
[17:52] <xnox> * pptpd                         (for ppp-dev)
[17:52] <rbasak> Thanks
[17:52] <xnox> * rp-pppoe                      (for ppp-dev)
[17:52] <rbasak> I had just managed to poke the same out of grep-dctrl :)
[17:52] <rbasak> What should I check in the reverse build depends?
[17:53] <xnox> i would just rebuild them against the new ppp; to see that they don't break; or like poke the .debs and see which symbols they use (if any) from ppp
[17:55] <rbasak> OK I'll poke them into a PPA. Thanks!
[17:59] <jbicha> hi, I would have expected gnome-shell-extension-appindicator to have autosynced from Debian by now. Is there an issue with the Debian importer?
[18:15] <bdmurray> jbicha: I see the same version in Ubuntu here https://launchpad.net/debian/+source/gnome-shell-extension-appindicator
[18:20] <jbicha> right, we stopped getting Debian imports earlier today https://people.canonical.com/~ubuntu-archive/auto-sync/2022-02-24/
[20:13] <ddstreet> bdmurray can you clarify if FF has already happened, or if this is the final day before FF?  i.e. is jammy FF yet or not?
[20:13] <ahasenack> it's still open, but today is FF, in a few hors
[20:13] <ahasenack> the #ubuntu-release topic has the info
[20:14] <ddstreet> thanks!
[20:18] <bdmurray> ddstreet: events like FF usually happen around EoD in the Pacific time zone
[20:41] <cjwatson> jbicha: Yeah, I just noticed the same thing earlier today and asked for help in ~is
[20:41] <cjwatson> There's some kind of memory exhaustion issue
[20:42] <cjwatson> Might be nice to get a final auto-sync in before FF, given that ...
[20:53] <cjwatson> OK, issue worked around for now, Debian importer running
[20:54] <cjwatson> And I think it would make sense for me to do a manual auto-sync after that, since it hasn't yet been disabled and we missed the last couple of runs
[21:11] <cjwatson> auto-syncing now
[21:18] <bdmurray> thanks
[21:25] <cjwatson> and done
[22:09] <rbasak> ppp rdeps all built successfully in my PPA so I uploaded the contribution. Thanks ahasenack and xnox for your help in reviewing.


[16:19] <locodir-MikeH> Hello all
[16:23] <locodir-MikeH> 60 million + ppl in the uk and Ubuntu is dead.....dang nabber
[16:23] <belkinsa> Please explain.
[16:39] <coolbhavi> hello locodir-MikeH
[16:39] <coolbhavi> hey belkinsa
[16:39] <belkinsa> Hey there.


[00:56] <Mousa> salam Alikom
[00:58] <Mousa> is there anybody here?
[00:58] <elacheche_anis> salam Mousa
[00:58] <Yoda`> w Alikum Al-Slam
[00:58] <Mousa> i have problem in installing Ubuntu
[00:59] <elacheche_anis> what problem!
[00:59] <Mousa> in setup .   Because I installed Ubuntu with WinBug 7 many time too without any problems.. May be it's problem with some updates/patchs of WinBug 7
[01:03] <Mousa> ok Thanks elacheche_anis :)
[01:03] <elacheche_anis> But I'm sure that the problem is because of WinBug7 not Ubuntu because a friend from this channel asked me the same question in the same day that I found the proble
[01:03] <elacheche_anis> do you want to know what solution I got!!
[01:04] <Mousa> tell me
[01:04] <elacheche_anis> Installing Ubuntu in the HD, then re-install Win7.. Then repairing the GRUB.. It's not a perfect solution, but I don't find any other solutions :-/
[01:05] <Mousa> I think that's what I'll do
[01:05] <elacheche_anis> ok :)
[01:05] <elacheche_anis> Yoda`, have you any informations about that!
[01:06] <Mousa> ok :) thnaks for ur help
[01:06] <Mousa> thanks*
[01:06] <elacheche_anis> welcome
[01:34] <a3Dman> If only Windows has an option not to install a bootloader :)
[01:35] <elacheche_anis> yeh.. "IF"


[15:59] <Laney> hi
[15:59] <Laney> can anyone help me find Christopher Lee please?
[16:06] <Laney> ah, that's veebers, I see
[20:45] <balloons> Laney, correct


[00:01] <fullermd> Noldorin: I have vague memories that say it has an env variable you can use to point at an object store elsewhere at least...
[00:02] <jelmer> Noldorin: somewhat
[00:02] <Noldorin> fullermd, hrmm. sounds hacky
[00:02] <Noldorin> basically i just don't want to pull all the RCS crud.
[00:02] <jelmer> Noldorin: you can create a tree in a different location and then set an environment variable
[00:03] <fullermd> Noldorin: Well, you did say "git", didncha?   ;>
[00:03] <Noldorin> fullermd, fair point ;-)
[00:03] <jelmer> Noldorin: yeah, as fullermd says
[00:03] <Noldorin> would it let me avoid pulling all the branch data?
[00:03] <fullermd> I expect it only works on local disk.
[00:03] <achiang> hello, is there a way to get the diff of my tree, starting from -r -1 to the current dirty state?
[00:03] <fullermd> (well, mounted filesystem anyway.  A little NFS across the internet never hurt anybody...)
[00:04] <fullermd> achiang: Wouldn't that just be 'bzr diff'?
[00:04] <jelmer> Noldorin: it doesn't work for remote repositories
[00:04] <Noldorin> jelmer, fullermd ah, so i thought. oh well to that idea then.... thanks anyway :-)
[00:05] <achiang> fullermd: hm, i didn't explain myself... i fixed something in -r -1 based on a review comment, but pretty much rewrote the commit at the top of the tree. I want to show what the diff would look like if i never committed -1 at all...
[00:05] <achiang> so i want -r -2 to current state, i think
[00:07] <fullermd> Do you mean "if I hadn't run 'ci' with what's in -r-1" or "if I'd not made the changes in -r-1"?
[00:07] <fullermd> The former would be -r-2.  The latter would be...   uh...   magic.
[00:07] <wgrant> achiang: 'bzr diff -r-2..' will show you the combined differences.
[00:07] <achiang> well, asked another way, i want the output that loggerhead might show you if you submitted an MP consisting of 2 commits that modified the same section of source
[00:08] <wgrant> "diff -r -2.."
[00:08] <fullermd> No, "-r-2.." is equivalent to "-r-2..-1".  You want "-r-2".
[00:08] <achiang> i tried bzr diff -r -2 (with a space)
[00:08] <achiang> oops, i mean i tried bzr diff -r -2..
[00:09] <achiang> i have uncommitted changes... any way to get those into the combined diff?
[00:09] <fullermd> That's what "-r-2" does.
[00:10] <fullermd> Though I imagine what the MP shows is actually more like a merge --preview from the other side, which may not correspond to that diff if there are other changes.
[00:10] <achiang> fullermd: hm, it works now. i *thought* that is what i was typing, but i must have gotten it wrong
[00:10] <achiang> thanks all
[06:29] <vila> hi all !
[06:58] <poolie> hi there vila
[06:58] <mgz> morning all
[06:58] <vila> poolie: hey, 1-on-1 ?
[06:58] <vila> mgz: heya
[06:59] <poolie> yes please
[07:06] <jam> morning all
[07:57] <jam> poolie, vila, mgz, Riddell, jelmer: standup?
[07:58] <poolie> hi
[07:58] <poolie> absolutely
[07:58] <poolie> mumblicious?
[07:59] <jam> i'm on
[08:00] <jam> but I'm all alone
[08:00] <jam> well, jelmer stopped by for a second :)
[08:00] <jam> http://pad.ubuntu.com/RXCaDM4J3u
[08:27] <poolie> Riddell: have a 'dulce et decorum' badge :)
[08:34] <mgz> poolie: like jelmer asked earlier, what's the plan on 1-1s?
[08:35] <mgz> I'd managed to miss a google calendar thing from you last week as well.
[09:04] <poolie> jam, mgz, did you see http://people.mozilla.com/~tglek/lpc2011/ - you might like it
[09:06]  * mgz looks
[09:06] <poolie> wow especially: http://glandium.org/blog/?p=1764
[09:07] <poolie> running a busy-loop in the background makes the benchmark faster
[09:07] <poolie> (through not letting the cpu spin down)
[09:07] <mwhudson> there was an SMP bug on ARM recently where running ping -f localhost made usb transfers go 10x faster
[09:13] <mgz> hm, been seeing the updates going by on p.m.o but presentation is new to me
[09:17] <lifeless> mwhudson: win
[09:18] <mwhudson> lifeless: turns out assumptions along the lines of "this architecture will only ever be uniprocessor" are dangerous :-)
[09:18]  * mwhudson puts the computer down
[09:33] <nigelb> mwhudson: Really? o_O
[10:48] <lifeless> mgz: did you see my ping about FixtureResource ?
[10:50] <lifeless> mgz: http://bazaar.launchpad.net/~canonical-launchpad-branches/python-oops-amqp/trunk/view/head:/oops_amqp/tests/__init__.py#L83 - example of use
[10:50] <mgz> lifeless: thanks
[10:51] <lifeless> mgz: RabbitServer() is a Fixture. That declaration is using a resource
[10:52] <lifeless> mgz: and you wrap the test suite in an OptimisingTestSuite(); done.
[10:53] <mgz> where do I find rabbitfixture?
[10:54] <mgz> also, I'd be very sad if I was a test given a resource called 'rabbit' and it wasn't an actual bunny
[10:54] <lifeless> mgz: pypi rabbitfixture ;)
[10:54] <mgz> woho! a fluffy friend... wait no... ;_;
 is 404?
[10:57] <lifeless> bwah. it should be
[10:57] <lifeless> lp:rabbitfixture too, for sure
[10:57] <mgz> lp will do.
[10:57] <lifeless> (not that its code is particularly relevant
[10:58] <lifeless> (its convoluted due to dealing with heinous erlang stuff)
[10:59] <mgz> lifeless: I'm curious how reset is handled.
[10:59] <mgz> the answer seems to be... it's not
[11:00] <mgz> but actually there is quite a lot of interesting code in there
[11:01] <lifeless> mgz: reset defaults to stop(); start()
[11:01] <lifeless> mgz: doing a smarter one is an optimisation rather than a semantic facility
[11:02] <mgz> right.
[11:03] <mgz> but is also the whole point, in some respects
[11:03] <lifeless> sure
[11:04] <mgz> the way this uses TempDir and EnvrionmentalVariableFixture is enlightening too
[11:04] <lifeless> :)
[11:04] <lifeless> cool
[11:09] <lifeless> mgz: is that a good thing ?
[11:14] <mgz> understanding is always good
[11:15] <lifeless> :>
[11:15] <mgz> so the way useFixture is used there helps seperate concerns, but punts entirely on resource reusage
[11:17] <lifeless> right
[11:17] <lifeless> this is the Fixture-does-not-have-introspection-apis issue I was trying to explain
[11:18] <lifeless> fixture is a neat easy api, but hard to do layers-of-resource-reuse with
[11:18] <mgz> the filesystem is prepared seperately from the environment, and then a super-fixture inits and uses both
[11:18] <lifeless> its totally easy to take the end result and wrap that as a Resource
[11:23] <mgz> okay, and I can see how FixtureResource could be changed to split RabbitServerResources and RabbitServerRunner and have the latter depend on the former
[11:23] <mgz> ...in fact, let me do that as an exercise
[11:24] <lifeless> ah, thats where its tricky
[11:24] <lifeless> because the optimiser runs before setUp
[11:24] <lifeless> by definition
[11:25] <lifeless> and because RabbitServer acquires its dependencies by calling useFixture(new object)
[11:25] <lifeless> but please - have a fiddle :)
[11:25] <mgz> okay, I see the problem
[11:25] <lifeless> but that said, you can use the testresources contract with a fixture that expects it
[11:25] <lifeless> testresources injects the dependencies as attributes
[11:26] <lifeless> so a fixture which expects a self.config to exist before its setup and go after its cleaned up, will work fine in conjunction with testresources - but not standalone :)
[11:27] <lifeless> so the handwaving plan is to expose a static, optional, graph api for fixture
[11:27] <lifeless> which testresources can introspect and do its thing on, and which fixtures can bring up itself if its running standalone
[11:33] <mgz> I don't see why fixtures shouldn't init other fixtures in their init
[11:33] <mgz> is there a reason that might be a bad thing?
[11:33] <lifeless> mgz: well, init != setUp
[11:33] <mgz> right.
[11:34] <lifeless> mgz: is 1230am; thats a good question, but I'm just barely managing to delete unneeded tests right now ;)
[11:34] <lifeless> mgz: let me get back to you on it; see if I can page in m thoughts (if I had any prior ones)
[11:34]  * mgz cuts lifeless some slack
[12:00] <mgz> okay
[12:01] <mgz> lifeless, mind if I just propose this to lp:python-oops-ampq so you can look at the diff at your leisure?
[12:01] <lifeless> mgz: uhm yeah :) - 20 folk will get mail, and someone will review it
[12:02] <mgz> ...maybe pastebin would be wiser
[12:02] <lifeless> you could just push a branch up, no need for the proposal angle
[12:02] <mgz> good plan
[12:05] <mgz> okay, `bzr diff -r2..3 lp:~gz/python-oops-amqp/rabbitserverresource`
[12:05] <mgz> I think that's correct, and should do bascially the same thing as the current formulation
[12:07] <mgz> it doesn't seem very generalisable without defining a specific interface on top of fixtures though
[12:08] <lifeless> I will look tomorrowish at it; 1am now, just winding down for halt()
[12:08] <mgz> night :)
[12:26] <deni> hi guys.... does bzr have something like git submodule?
[12:57] <deni> anyone?
[13:01] <briandealwis> deni: I've not actually used git submodule, but from what I vaguely understand, you might want to check out bzr-externals
[13:02] <briandealwis> deni: there's a similar project called scmproj that has a different approach
[13:18] <deni> briandealwis: tnx i'll check it out
[15:25] <jelmer> maxb: hi
[15:25] <maxb> hi
[15:25] <jelmer> maxb: Is there a branch with the python-helper used in the daily PPA?
[15:25] <maxb> there is
[15:26] <maxb> somewhere.... :-)
[15:26]  * maxb hunts
[15:27] <maxb> https://code.launchpad.net/~maxb/ubuntu/maverick/python-backport-helper/ppa
[15:27] <maxb> apparently
[15:27] <maxb> Which surprises even me
[15:27] <maxb> Suggestions of a better place welcome
[15:28] <jelmer> maxb: Is it used by just bzr at this point? If so, would you mind having it owned by ~bzr?
[15:28] <maxb> That's fine
[15:29] <maxb> It's not used elsewhere
[15:29] <maxb> (But having it under ubuntu/maverick isn't exactly helpful either)
[15:29] <jelmer> yeah
[15:29] <mgz> if I'm a plugin, how do I go about adding something to the library_state?
[15:30] <jelmer> mgz: that's a good question
[15:31] <mgz> it seems I can address it as bzrlib.global_state by the time I'm imported, but I don't know if that's the right way or not
[15:31] <jelmer> maxb: and that's used by both lucid and maverick?
[15:31] <maxb> yes
[23:53] <poolie> hi maxb
[23:54] <maxb> hello


[20:49]  * AlanBell sees mouse tweaks simulate secondary click working
[20:49] <AlanBell> and I think I see onboard stacking above the dash
[20:50] <charlie-tca> Getting several reports that Onboard is starting automatically on login today
[20:50] <AlanBell> ah, no :(
[20:51] <AlanBell> onboard is above the dash on unity2d, but below in unity 3d
[20:51] <charlie-tca> 2d counts
[20:51] <charlie-tca> If we could get all of a11y working in 2d, it can be transitioned to 3d
[20:52] <AlanBell> I think it will be a mix
[20:52] <AlanBell> if you want x and y use 3d, if you want w and z then use 2d
[20:52] <charlie-tca> That kind of sucks, especially if screen-reader installation defaults to 2d
[20:53] <AlanBell> actually I can't see much in 3d that is better than 2d
[20:53] <AlanBell> probably compiz zoom
[20:54] <AlanBell> and the other visual impairment things compiz can do like filters
[21:37] <AlanBell> maco: just turned off the add_widget code and discovered that the upgrade button in the install says it will install 11.04!
[21:43] <AlanBell> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/ubiquity/oneiric/view/head:/gui/gtk/stepPartAsk.ui#L233


[17:17] <Wild_Man> Hello krytarik, I am just starting to publish, I figured I should leave the forum to Bashing-om so he can learn how to do it
[17:19] <Wild_Man> I have been looking at the logs for he weekend but they are pretty much blank, is the logging working?
[17:19] <krytarik> Just a sec please, need to check something on the issue wiki page first.
[17:19] <Wild_Man> Okay
[17:19] <krytarik> Yep, there just wasn't much talking here the last few days.
[17:20] <Wild_Man> okay, just wanted to make sure, I have not been near a computer but a few minutes all weekend, I am still not fully awake, I had a nap a few hours ago
[17:32] <krytarik> Wild_Man: Ok, done - if you haven't done so already, please run the publish script again to pull in the latest changes.
[17:32] <krytarik> Erm, I mean if you *have* done so already. :P
[17:35] <Wild_Man> I will
[17:51] <Wild_Man> krytarik, do you think bashing-om wants to publish to the forum today so we can learn to do it while I am here to walk him through it?
[17:51] <Wild_Man> we/he
[17:53] <krytarik> I don't know, but seeing that he isn't here right now anyway, 1.) you shouldn't let that hold you back, and 2.) I'm sure there will be another occasion for him to do it.
[17:54] <Wild_Man> Okay
[17:54] <Wild_Man> I was just going to leave the forum to the end instead of doing it first
[17:55] <krytarik> Well, we could wait a little on him still too, since I haven't done the Fridge yet either.
[17:56] <Wild_Man> I will give him a little while
[18:09] <Wild_Man> Do you know if the clean up has been done on the wiki including archiving?
[18:10] <krytarik> I haven't looked yet, but think not yet.
[18:10] <krytarik> Also, have just done the Fridge and Google+
[18:10] <Wild_Man> I will look
[18:11] <Wild_Man> I have done all publishing except the forum
[18:13] <krytarik> Well, similar to last week, when we almost skipped you entirely, I'd say let's not wait any longer on him - like I said, there is always another time.
[18:13] <Wild_Man> krytarik, Ronnie Tucker wants to know if we will add Full Circle Magazine back into UWN, I know we briefly discussed this a few weeks ago
[18:13] <Wild_Man> I will do the forum then
[18:13] <krytarik> Yes, and I stick to the reached decision not to.
[18:14] <krytarik> I.e. there is not much additional value for us in there.
[18:14] <Wild_Man> I will email him back and let him know and I just received another unsubscribe from the list
[18:15] <Wild_Man> I think Full Circle is all podcasts now
[18:15] <krytarik> No, I think there were always two versions.
[18:21] <krytarik> Wow, I've just got a little wuzzy I might have gotten tricked by the wiki's caching again! >_>
[18:24] <Wild_Man> That is not good
[18:25] <krytarik> Well, it turned out it didn't. :P
[18:25] <Wild_Man> It was to large again I had to remove a section then save and then add it back in, are you sure that only the new links are being posted from week to week?
[18:26] <Wild_Man> there are a lot of them
[18:26] <krytarik> Yes, but yeah it did seem a little much this week.
[18:27] <Wild_Man> Okay, I have to feed my cat, she is bugging me, bbia
[18:35] <Wild_Man> Cleaning up wiki now
[18:35] <krytarik> Cool, thanks!
[18:51] <Wild_Man> Done, I have to leave for a little while and Your Welcome!
[19:00] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 529 @ http://fridge.ubuntu.com/2018/05/28/ubuntu-weekly-newsletter-issue-529/
[20:35] <Wild_Man> Hello Bashing-om
[20:36] <Bashing-om> Wild_Man: :)
[20:39] <Wild_Man> Bashing-om, I am leaving in a few minutes but if you want to publish the letter to the forum I will remove it and you can publish it so you can learn how or you can just click on administrative at the top of the thread and see how it is done for next time
[20:39] <krytarik> Oh no, please no republishing on the forums..
[20:39] <Bashing-om> Wild_Man: No hurry to learn . We see aboit next time .
[20:40] <Wild_Man> krytarik, I knew you would say that, it really is not a big deal
[20:40] <Wild_Man> Bashing-om, I am good with that
[20:40] <Bashing-om> krytarik: Got a respinse from Rex " The link has changed.  It is now http://azloco.org/?q=node/28.  I am in the process of changing all the links in the portal and elsewhere." .
[20:41] <krytarik> Wild_Man: Well, I mean if the initial one sticks instead, that'd work for me too.
[20:41] <krytarik> Bashing-om: Aha, interesting, thanks.
[20:42] <Wild_Man> Bashing-om, when I clicked on that link I received "AdGuard has detected an attempt by this website to use your browser as a crypto-currency miner. It can create significant CPU load. Press "Cancel" to prevent it."
[20:42] <Bashing-om> Wild_Man: Lomme see what I get !
[20:43] <Bashing-om> Wild_Man: the A loco link completes as expected for me .
[20:44] <krytarik> Yeah, looks like a false positive to me.
[20:44] <Wild_Man> I am using the newest FF with security enabled and it gives the warning
[20:44] <krytarik> But I did laugh initially! :P
[20:44] <Wild_Man> It may be krytarik
[20:46] <Bashing-om> Wild_Man: FF here also on a default install of 18.10 xubuntu . No issue here .
[20:53] <krytarik> Wild_Man: I'm happy with uBlock Origin as an ad blocker btw.
[20:54] <Wild_Man> krytarik, I am using Adblocker ultimate right now but I was using that one and I like it
[20:55] <krytarik> You use *two* ad blockers? >_>
[20:57] <Wild_Man> The one I listed above and I do use ghostery
[20:58] <Wild_Man> I do not have uBlock installed at this time
[20:58] <krytarik> I mean AdGuard is one too.
[21:00] <Wild_Man> No, I did not install Adguard and I do not see it listed up top so I need to see why it is saying Adguard, maybe it is installed in this version of FF be default
[21:01] <Wild_Man> It is not install, so it must be running on that particular page the Bashing-om linked to
[21:02] <krytarik> And warning about itself, and out of us three only you? :P
[21:04] <Wild_Man> If it can happen it will happen to me!
[21:05] <Wild_Man> where is the best place to post a screenshot?
[21:05] <krytarik> Imgur still I think.
[21:06] <Wild_Man> That is what I thought, thanks
[21:06] <Wild_Man> See if you can see that https://imgur.com/a/vtvTKgJ
[21:10] <Wild_Man> I have tracking protection turned on in FF so that may be why I received that message
[21:10] <Wild_Man> I also have "Deceptive Content and Dangerous Software Protection" enabled
[21:12] <krytarik> But this ain't Windows, is it?
[21:13] <krytarik> Because there is also: https://adguard.com/en/download.html
[21:15] <krytarik> Oh, the screenshot tells.. >_>
[21:16] <wildmanne39> krytarik, is it a valid issue?
[21:17] <wildmanne39> My computer froze and my fan started running real fast I had to restart it
[21:19] <krytarik> wildmanne39: What's the red shield icon on the right of your toolbar in the screenshot?
[21:20] <wildmanne39> krytarik, the is Adblocker ultimate
[21:21] <wildmanne39> The one that is shows in the screenshot is not installed in add-ons
[21:26] <krytarik> Curious then...  But not a general issue with the site, I don't think.
[21:27] <wildmanne39> Strange category then
[21:36] <krytarik> Appart from why it's there in the first place, might be it's triggered by the occurrence of "coin" in here: http://upgraderservices.cf/drupal.js
[21:37] <krytarik> ...Uh oh. :D
[21:38] <krytarik> https://krebsonsecurity.com/2018/03/who-and-what-is-coinhive/
[21:39] <krytarik> No kidding, this does look way more serious right now.
[21:39] <wildmanne39> krytarik, yes it looks serious
[21:40] <krytarik> Bashing-om: Can you please contact Rex on this asap?
[21:40] <wildmanne39> I think if we are including that link somewhere we need to remove it and notify the person here maintains it
[21:41] <krytarik> Well, we aren't directly - but it doesn't matter much here.
[21:42] <Bashing-om> krytarik: No not know how fast the turn-a-rounbd-will be but sure I can drop a E-mail to him .
[21:43] <krytarik> Well, I was just thinking of going directly to their IRC channel this time.
[21:43] <Bashing-om> krytarik: Good thought there too .
[21:44] <krytarik> And since I'm the one most familiar with it right now, I might just do this.
[21:50] <krytarik> Thankfully, wildmanne39 here stumbled across anything and everything.. :D
[21:51] <Bashing-om> testing and punching holes :P
[21:51] <krytarik> "Wooops, it gets deep in there!" :P
[23:13] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Canonical Won’t Go Public This Year @ https://www.omgubuntu.co.uk/?p=131676 (by Joey Sneddon)
[23:28] <Wild_Man> Thanks krytarik, did post the newletter to google+ do I just click on what is new with you?
[23:28] <Wild_Man> did/to
[23:29] <krytarik> Yeah, and what I do then is just post the intro there, but add the link through the respective icon - something that none of the other services offer.
[23:31] <Wild_Man> Sounds good to me, it is the exact same message we put on twitter?
[23:32] <krytarik> Yeah, except we split it like that, of course.
[23:34] <krytarik> Posting the bare URL along with it would also be fine though - this way it's easier to make out.
[23:34] <Wild_Man> okay
[23:35] <Wild_Man> I posted here https://community.ubuntu.com/t/ubuntu-weekly-newsletter/359/4 that the UWN is back and that we can still can use more contributors
[23:35] <Wild_Man> I just replied to what was already there
[23:35] <krytarik> Fun!
[23:36] <Wild_Man> It was still showing UWN as on break
[23:48] <Wild_Man> krytarik, this is what I plan to send to the full circle magazine "Hello, the UWN team discussed adding the Full Circle Magazine back into the publication of UWN two weeks ago but since largely what you write about duplicates what is in the UWN and covers linux in general and the UWN focuses on the official Ubuntu Flavors only we decided for now to publish without including the Full Circle Magazine. You have an excellent magazine
[23:48] <Wild_Man> though." Do you want to edit it or are you happy with it?
[23:49] <krytarik> Sec, editing a little.
[23:50] <Wild_Man> I thought it might have a rough spot or two
[23:55] <krytarik> "Hello, the Ubuntu Weekly Newsletter team discussed adding the Full Circle Magazine back into the publication of UWN two weeks ago, but since largely what you write about duplicates what is already in the issue, and focuses more on Linux in general while we do on Ubuntu and its official flavors, we decided against including it for now. You have an excellent magazine though."
[23:55] <krytarik> Wild_Man: ^


[08:00] <mercutio> i noticed that ubuntu trusty seems to have the xenial lts kernel available already.  is this already considered stable?
[08:00] <mercutio> it seems that options are to have a kernel that's only supported until August, or use xenial kernel?   and there seems to be an unpatched bug in 3.13...
[08:52] <apw> mercutio, 3.13 is the release kernel so has 5 years of support ...
[08:53] <mercutio> but it's not an upstream lts support version so only vulnerabilities are fixed?
[08:54] <mercutio> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672
[08:54] <ubot5`> Launchpad bug 1423672 in linux (Ubuntu Trusty) "ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y" [High,Confirmed]
[08:54] <mercutio> i was looking at that bug which doesn't seem to be fixed
[08:55] <apw> mercutio, lts-xenial i would not normally suggested until the .1 release of the lts, it is considered an early preview before then
[08:55] <mercutio> so would 4.2 be recommended for something to use for a long time?
[08:56] <mercutio> having file system corruption bug of course is not really desired
[09:33] <apw> kamal, ^
[12:06] <arges> mercutio: looks like there was a patch (7dec560e) identified that fixes that issue, so that seems like a reasonable thing to fix in 3.13 as well
[12:08] <mercutio> arges: yeah, there was a short patch identified
[12:09] <mercutio> but i checked gitweb and it wasn't in
[12:10] <arges> mercutio: this is our kerenl SRU process: https://wiki.ubuntu.com/KernelTeam/KernelUpdates
[12:13] <arges> mercutio: so I could submit this as an SRU and then when the update comes into 3.13 someone would need to test it and verify it does fix the issue, then eventually it is released
[12:13] <mercutio> arges: what kind of time frame is there for that?
[12:14] <arges> 3-6 weeks
[12:14] <arges> if it is verified quickly and causes no regressions
[12:14] <mercutio> i see
[12:15] <mercutio> yeh i think i waant to change kernels quicker than that personally
[12:21] <arges> well this is probably worth fixing it for other users too, I'll post a test kernel on the bug regardless
[12:34] <mercutio> yeah it's definitely worth fixing
[12:58] <arges> mercutio: ok commentd on the bug with a test kernel