[02:40] <alexandros_c> good day is the update for 18.04 to 20.04 out?
[02:57] <Bashing-om> alexandros_c: Last I was aware the .1 is to be released Jul23.
[02:59] <alexandros_c> thanks for responding, so no upgrade path from 18.04 to 20.04 as yet?
[03:01] <Bashing-om> alexandros_c: There is a means if you are in a hurry - yes .
[03:02] <alexandros_c> no I am not in a hurry just checking
[03:03] <alexandros_c> once again, thanks Bashing-om for asking my questions
[03:03] <Bashing-om> alexandros_c: Be aware that untill the .1 release that 20.04 remains under the development umbrella. There is a command to effect that release upgrade.
[03:04] <alexandros_c> just out of curiosity, what is it?
[03:06] <Bashing-om> alexandros_c: Once your system is fully updated - PPAs reverted ( graphic's driver) then ' sudo do-release-upgrade -d ' .
[03:08] <alexandros_c> it did that and it said no updates available
[03:09] <Bashing-om> alexandros_c: Terminal command ' grep -i ^prompt /etc/update-manager/release-upgrades ' returns what ?
[03:11] <alexandros_c> I am not at that machine atm
[03:12] <alexandros_c> I will try it when I git access to that machine
[03:12] <alexandros_c> *get
[03:12] <Bashing-om> alexandros_c: ack - no hurry :P
[03:13] <alexandros_c> lol
[16:10] <xu-help23w> Hey, I am having trouble establishing an initial wifi connection on my new xubuntu system.
[16:14] <diogenes_> xu-help23w, initial?
[16:14] <xu-help23w> Yes, my first connection to a wireless network
[16:17] <diogenes_> xu-help23w, details
[16:18] <xu-help23w> I am selecting the Icon in the taskbar and I have only a few avaliable options: VPN Connections, Enable Networking (checked) and Edit Connections
[16:18] <xu-help23w> The unselected ones are Ethernet network, and connection information
[16:19] <diogenes_> xu-help23w, can you connect with cable?
[16:19] <xu-help23w> No, I dont have a space ethernet cable
[16:20] <xu-help23w> No, I dont have a space ethernet cable
[16:20] <diogenes_> xu-help23w,  try with phone tethering.
[16:21] <juno> run dmesg and look for detection of your wifi card
[16:23] <xu-help23w> I should mention that I am dual booting
[16:23] <xu-help23w> so that may effect tethering
[16:23] <diogenes_> xu-help23w, it won't affect anything.
[16:24] <xu-help23w> What should I look for when running dmesg
[16:25] <diogenes_> it would be almost impossible to fix your issue if you don't get internet on that PC.
[16:26] <xu-help23w> After enabling tethering, where should I look to check for connections?
[16:27] <diogenes_> it should be via usb cable just open firefox.
[16:28] <juno> something like 'dmesg | grep -i wifi' or 'dmesg | grep -i wlan'
[16:29] <xu-help23w> No matches
[16:29] <xu-help23w> Should I try a different linux distro?
[16:30] <juno> from the options you listed in the applet it sounds like the wifi isn't enabled at the hardware level
[16:30] <juno> or its just a complete driver failure which wouldn't be too surprising
[16:31] <juno> but i would expect to see that in dmesg
[16:34] <juno> do you know the chipset of your card?
[16:35] <xu-help23w> I do not, is there a way to get this hardware info?
[16:35] <juno> try lspci
[16:35] <juno> maybe slpci -knn
[16:36] <juno> lspci -knn
[16:36] <juno> sorry
[16:36] <xu-help23w> Yeah, quick hardware test says processing is fine
[16:38] <juno> need to find the chipset
[16:38] <juno> so, lspci | grep -i broadcom
[16:39] <juno> same for intel
[16:39] <xu-help23w> just lspci?
[16:39] <xu-help23w> no flags/
[16:39] <juno> try lspci | grep -i wireless too
[16:39] <xu-help23w> it lists my network controller
[16:40] <xu-help23w> PCIe Wireless network adapter
[16:41] <juno> ah good
[16:42] <juno> so anything in 'dmesg | grep -i pcie'
[16:43] <xu-help23w> ACPI FAST deckares the system doesn't support PCIe ASPM, so dsiable it
[16:43] <xu-help23w> FADT*
[16:43] <xu-help23w> and it lists pcieports
[16:44] <juno> you might try: https://help.ubuntu.com/stable/ubuntu-help/net-wireless-troubleshooting-hardware-check.html
[16:51] <xu-help23w> From the looks of it I have a supported wireless card
[16:51] <xu-help23w> (reltec PCI)
[16:52] <xu-help23w> I think the network drivers may be the issue.
[16:52] <xu-help23w> They may not be dysfunctional, but they were designed for windows machines.
[16:52] <juno> does 'dmesg | grep -i reltec' show any errors
[16:53] <juno> sorry i meant realtek
[16:54] <xu-help23w> I dont see any errors, just memory addresses, and driver information
[16:55] <xu-help23w> ``ums-realtek 1-9:1.0: USB Mass sotrage device detected``
[16:56] <juno> at this point I would follow this advice: https://help.ubuntu.com/stable/ubuntu-help/net-wireless-troubleshooting-device-drivers.html.en
[16:57] <xu-help23w> Is there a way to check if your driver is designed for a particular operating system?
[16:58] <xu-help23w> Maybe I should use the NDISwrapper?
[16:58] <juno> without knowing the exact chipset, I don't know
[16:58] <juno> but if it's designed for windows, you're probably SOL with that card
[17:01] <xu-help23w> SOL?
[17:03] <juno> it probably won't work if it's windows-specific
[17:04] <xu-help23w> So say I have the chipset, how can I tell if my driver is Windows-Specific?
[17:06] <xu-help23w> chipset information*
[17:06] <juno> check this list: https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported
[17:07] <xu-help23w> Realtec support pci and usb
[17:07] <xu-help23w> supports*
[17:08] <juno> chipsets: https://help.ubuntu.com/community/HardwareSupportComponentsWirelessNetworkCardsRealTek
[17:12] <xu-help23w> What if my chipset is not stated in the By Card Section?
[17:14] <juno> at this point I'd throw up my hands and go buy a cheap tp-link usb card :)
[17:15] <juno> sorry I can't be of further help
[17:19] <Previous> @juno
[17:19] <Previous> sorry, my broadband disconnected
[17:21] <Previous> What should I do given that my chipset is not listed on wifidocs
[17:27] <juno> at this point I'd throw up my hands and go buy a cheap tp-link usb card :)
[17:27] <juno> sorry I can't be of further help
[17:49] <Previous> Thanks for your time
[17:49] <Previous> :)
[19:35] <xubuntu22i> hello
[19:36] <xubuntu22i> is there HexChat like linux mint?


[00:08] <deansouth8> Lots of little perl errors in .26 and mythbuntu. Is there a tried and true distro where everything just works? Lol.
[00:12] <tgm4883> deansouth8, where are these perl errors?
[00:15] <deansouth8> Today it's in archive files DVD...  log viewer says typeerror corcing to Unicode need string or buffer artwork found
[00:17] <tgm4883> deansouth8, honestly, I didn't even know the archive dvd thing still existed
[00:20] <deansouth8> Are you on .27? Is everyone?
[00:20] <tgm4883> i'm on 0.26
[22:54] <Shadow__X> I keep getting this error /etc/cron.weekly/mythtv-database:
[22:54] <Shadow__X> ERROR: DBBackupDirectory not specified, stopped at /usr/share/mythtv/mythconverg_backup.pl line 856.
[22:54] <Shadow__X> run-parts: /etc/cron.weekly/mythtv-database exited with return code 255 but when i run the backup script it find the directory no problem
[23:01] <tgm4883> Shadow__X, what user is that running as?
[23:05] <Shadow__X> tgm4883: how can i check
[23:06] <tgm4883> Shadow__X, it's probably running as root
[23:06] <tgm4883> so you should su to root and see if the issue persists
[23:06] <Shadow__X> thats what i am thinking but how can i check to see who it is running as?
[23:06] <Shadow__X> just check the crontab?
[23:16] <tgm4883> Shadow__X, well it's in /etc/cron.weekly/ so it should be root
[23:16] <Shadow__X> right so login to root and run the command thats in cron.weekly?
[23:16] <tgm4883> you could open the file to be sure
[23:16] <tgm4883> Shadow__X, yea
[23:21] <Shadow__X> so i logged into root and did ./mythtv-database thats in cron.weekly and it gave me the same error
[23:21] <Shadow__X> i know the user i log in to can do it fine so i am guessing i need to make another config file for it
[23:26] <Shadow__X> where do i put the config for backup under root
[23:33] <tgm4883> Shadow__X, IIRC, it needs to be in the home dir
[23:33] <tgm4883> so for root, that is /root
[23:44] <Shadow__X> so i created a bacuprc but it still throwing up the error
[23:49] <Shadow__X> nvm got it. Forgot to put backuprc in .mythtv under root
[23:49] <Shadow__X> should of known better thanks tgm4883


[02:27] <Pomare> Hello
[02:27] <Pomare> What is the largest ubuntu conference in the world?
[02:28] <lifeless> the shadow knows
[02:28] <Pomare> If i want to organize an international event here, who should I contact about this?
[02:32] <lifeless> Pomare: I don't think you need to contact anyone, do you ?
[02:33] <Pomare> lifeless maybe there is a project already in the making.
[02:35] <lifeless> you could discuss it on one of the ubuntu lists (see lists.ubuntu.com) if you want to coordinate
[02:35] <Pomare> thank you my friend
[02:35] <lifeless> IME though, folk running conferences are well aware of other conferences already
[02:36] <Pomare> Do you go to these conferences regularly?


[01:27] <lifeless> EdwinGrubbs: https://code.edge.launchpad.net/~lifeless/launchpad/registry/+merge/31805
[01:27] <lifeless> (if you're still oncall)
[02:10] <mwhudson> lifeless: looking
[02:14] <mwhudson> lifeless: you've seen TestCase.assertStatementCount ?
[02:15] <mwhudson> it's sort of a bit like but not quite like QueryCounter
[02:19] <lifeless> I looked for it
[02:19] <lifeless> but found QueryCounter
[02:19] <lifeless> oh yay two totally different ways of doing the same thing.
[02:20] <lifeless> uhm
[02:20] <lifeless> sigh, thanks.
[02:20] <lifeless> I think my refactoring is not harmful
[02:20] <lifeless> in fact, I think QueryCounter is useful because its aimed directly at the request, not at the storm layer
[02:20] <lifeless> so its useful for 'is this page request going to be ok'
[02:21] <lifeless> which, record_statements on allmembers is not a good answers for
[02:21] <mwhudson> ah, i just commented on the mp
[02:23] <mwhudson> lifeless: looking at the implementation, the two things are actually doing very similar things
[02:23] <mwhudson> also this makes me wince:
[02:23] <mwhudson> def clear_request_started():
[02:23] <mwhudson>     """Clear the request timer.  This function should be called when
[02:23] <mwhudson>     the request completes.
[02:23] <lifeless> where is that ?
[02:24] <mwhudson> canonical.launchpad.webapp.adapter
[02:24] <lifeless> oh heh
[02:24] <lifeless> nasty file that
[02:25] <mwhudson> yes
[02:26] <mwhudson> lifeless: anyway, perfectly happy to approve branch as is, just wanted you to know about the other way
[02:27] <mwhudson> lifeless: approved
[02:29] <lifeless> mwhudson: thanks!
[02:29] <lifeless> mwhudson: I think its ok to have two semanticly different things
[02:29] <lifeless> mwhudson: because I can imagine as we get more event driveny that they will be rather different
[02:31] <mwhudson> lifeless: i guess i'd be happier if get_request_statements did something closer to what its name suggested, it's not reaaaaaaally tied to the request at the moment
[02:32] <mwhudson> it's just 'queries issued in this thread between beginPublication and endPublication' or whatever
[02:32] <mwhudson> no getting around that with an implicit database connection i guess
[02:32] <lifeless> right
[02:32] <lifeless> so I can see that getting fixed
[02:32] <lifeless> e.g. if we get more twisted into the appservers (long poll!)
[02:32] <lifeless> or whatever
[05:34] <wgrant> jtv: Hi.
[05:34] <jtv> hi wgrant!
[05:34] <StevenK> wgrant: Stalker!
[05:34] <wgrant> jtv: Thanks for the review yesterday.
[05:35] <wgrant> jtv: But you approved but didn't approve it.
[05:35] <jtv> wgrant: ah yes, sorry… that's something we often do for ourselves.
[05:35] <wgrant> jtv: Yeah, I can't do that :)
[05:36] <jtv> I sort of got in the habit of letting the author set the status for themselves after they process any review suggestions I give them, but since I didn't do that either...
[05:36] <wgrant> Heh.
[05:36] <jtv> StevenK: if you say william's stalking me, note I'd been online for several hours.  Wouldn't be very efficient stalking.
[05:37] <jtv> wgrant: there, done.  Now I suppose you'll want me to land it as well?
[05:37] <wgrant> jtv: I want to run it past bigjools again this evening.
[05:37] <wgrant> So, please don't.
[05:38] <wgrant> Just in case, you know.
[05:38] <jtv> wgrant: so… just the sort of thing you want to defer the Approved status for?
[05:38] <wgrant> jtv: hmmm.
[05:38] <lifeless> so, approved should mean
[05:38] <lifeless> 'the reviewer does not need to see it again'
[05:38] <jtv> say mwhudson, would you be free for an oversized review?  Couldn't get anyone yesterday and it's starting to hold me up.
[05:39] <lifeless> which is != 'it is ready to land'
[05:39] <jtv> lifeless: an approved _vote_ means the reviewer doesn't have to see it again.  But multiple people are involved in an MP.
[05:39] <lifeless> jtv: that too is true
[05:39] <jtv> So the Approved status comes about when everyone who's planning to say anything about the branch, including the author, feels it's ready to ladn.
[05:39] <jtv> land.
[05:40] <lifeless> jtv: that does not match the model the code team have.
[05:40] <jtv> what do they do?
[05:40] <lifeless> the approved status is /intended/ to mean 'the branch is approved from the point of view of the approval policy for the project, whatever that may be'
[05:41] <jtv> lifeless: I should amend what I said to: anyone who's _supposed_ to say anything about the branch.
[05:41] <lifeless> the 'queued' status is used for 'land it now' - but is disabled in the web UI for a few reasons.
[05:43] <jtv> lifeless: I didn't even know that state existed.  What's wrong with defining approval policy the way I said?
[05:44] <lifeless> jtv: it implies a blocking transition where one may not be needed
[05:44] <jtv> May not.  If that needs to be established, you've got a blocking transition.
[05:45] <lifeless> so, on a per project, per review basis - sure
[05:45] <lifeless> you can say 'this proposal is not ready to approve' and approve it when it is ready.
[05:45] <mwhudson> jtv: i should probably do some linaro stuff really, is it large and complicated or just large?
[05:46] <jtv> mwhudson: ah yes, I forgot about linaro.  It's reasonably complicated, so I'll find some other suc^H^H^Hhelpful soul
[05:46] <lifeless> I was told when I did a bunch of reviews that the LP policy is 'approved status + needs-fixing vote' to say 'fix this up and then land it', and so on.
[05:48] <jtv> lifeless: I wasn't aware of that—I thought "needs fixing" meant "fix it and then come back to me."  Seems to match the privileges better: only the reviewer can change that vote but the engineer can usually change the status.
[05:51] <jtv> thumper, are you someone I can bother for an oversized review at the moment?
[05:51] <thumper> jtv: no
[05:51]  * jtv puts up the it's-alright-I-understand act
[05:52] <thumper> lifeless: if I say fix it and land, I vote approve with 'conditional' or something
[05:52] <jtv> Same here.
[05:52] <thumper> lifeless: to me needs-fixing means get back to the reviewer
[05:54] <jtv> lifeless: you know I hate to lean on you so heavily but is this oversized review something you could do?
[05:55] <jtv> It's this one: https://code.edge.launchpad.net/~jtv/launchpad/recife-traits/+merge/31729
[05:55] <lifeless> jtv: I'm playing catchup myself today :(
[05:55] <lifeless> jtv: is it mechanical
[05:55] <jtv> Alas, no
[05:55] <lifeless> jtv: or does it require thought?
[05:56] <jtv> Alas, yes
[05:56] <jtv> so that leaves… jml?
[05:56] <lifeless> jml, stub, danilo, all of eastern europe
[05:57] <jtv> I don't see any of those right now
[05:57] <lifeless> right, I'm talking candidates-while-you'l;-be-awake :)
[09:51] <lifeless> jelmer: jtv has a big patch he's begging for a review of
[09:53] <jelmer> k
[09:53] <lifeless> jtv: ^
[10:10] <jtv> lifeless: thanks otp
[10:18] <wgrant> jelmer: Could you review https://code.edge.launchpad.net/~wgrant/launchpad/destroy-publishedpackage/+merge/31813, when you have a moment?
[10:18] <jelmer> wgrant: yes, of course
[10:18] <lifeless> wgrant: I reviewed it from a code angle fwiw
[10:20] <jelmer> lifeless,wgrant: what other angle does it need review from?
[10:21] <lifeless> none AFAIK
[10:21] <wgrant> lifeless, jelmer: Ah, sorry, I'd assumed that was a DB review.
[10:21] <wgrant> lifeless: Can you land that, then, please?
[10:21] <lifeless> wgrant: e-rather-late; jelmer can :)
[10:22] <jelmer> sure, no problemo
[10:22] <wgrant> Thanks.
[10:23] <jtv> jelmer: thanks for putting me on the queue.  Overweight branch, with apologies.
[11:28] <jelmer> StevenK: You mention in your MP that IDistroSeries.initialiseFromParent() has nothing to do with DistroSeries in general, which puzzles me a bit.
[11:29] <jelmer> it seems like a reasonable thing to have on IDistroSeries, if only as a convenience method
[11:32] <StevenK> jelmer: It looked to bigjools and me as completly seperate ...
[11:33] <lifeless> FWIW
[11:33] <lifeless> it looks to me like its conceptually a class method
[11:33] <lifeless> as in
[11:33] <lifeless> it creates a new type X from another type X
[11:33] <lifeless> thats kindof like __new__
[11:33] <lifeless> if you squint
[11:34] <jelmer> lifeless: Yep, though it's called on a freshly created DistroSeries, it doesn't create one itself.
[11:34] <bigjools> i-f-p is a soyuz function that acts on a registry object
[11:35] <bigjools> it's *nothing* to do with Registry and should not live on IDistroSeries
[11:36] <lifeless> so IDistroSeries has nothing to do with registry ?
[11:36] <jelmer> lifeless: IDistroSeries is owned by registry, i-f-p is sozuz
[11:37] <lifeless> jelmer: I *still* don't get why
[11:37] <lifeless> but its late, and I'm this || far away from trolling by mistake
[11:37] <lifeless> so I'm going to stop work :)
[11:37] <bigjools> lifeless: you're twisting what I said
[11:38] <jelmer> bigjools, StevenK: Thanks. I still think it makes sense conceptually to have i-f-p or a convenience method that calls out to i-f-p on IDistroSeries, but I can understand why it's not there.
[11:38] <bigjools> i-f-p initialises a distroseries in a soyuz context
[11:38] <bigjools> our model objects are too big already
[11:38] <lifeless> bigjools: see above, really, epically tired and there is stuff I need to learn here but I won't after being up for 17 hours
[11:39] <bigjools> lifeless: !
[11:39] <bigjools> go to bed
[11:39] <lifeless> I *don't* want to troll by accident
[11:39] <lifeless> When I troll, I want to mean it :)
[11:39] <bigjools> go to your bed under that bridge over there
[11:55] <jelmer> StevenK: r=me
[11:56] <henninge> jelmer: I took jtv's branch
[11:57] <jelmer> henninge: ah, great - thanks
[12:33]  * jelmer lunches
[13:27] <jtv> henninge: any luck with that review?
[13:27] <jtv> (I'm pretty much EOD at this point)
[13:27] <jtv> So if you're stuck on anything, do say so soon!
[14:43] <henninge> jtv: sorry, still working on it.
[14:43] <jtv> No worries.  I'll eod then.
[14:46] <henninge> jtv: what's the purpose of MessageSideHelper?
[14:47] <henninge> jtv: couldn't those methods be simply on Translationmessage?
[14:47] <jtv> henninge: it's a bit legacy: it's where I extracted the Traits from.  One thing it does though is provide a place where the incumbent messages can be cached.
[14:47] <jtv> (Can't do that in the TM model class of course)
[14:47] <henninge> jtv: sorry, POTMsgSet, I guess.
[14:48] <jtv> Can't do it in any model class.
[14:48] <jtv> I'd like to avoid relying automatically on a method that queries for incumbent messages.
[14:49] <jtv> At the moment we do check that in makeCurrentUpstream and makeCurrentUbuntu; I'd prefer to have that check a bit higher up somewhere, or at least let the traits go to a lower-level setter.
[14:50] <jtv> That also means we won't need the duplication between those two methods—it'd be a single traits-based implementation.
[15:08] <henninge> jtv: we will have to continue that tomorrow morning. I still have to switch locations for the rest of the day.
[15:09] <jtv> henninge: and me for the night.  :)  Bis dann!
[15:09] <henninge> Tschüss
[16:34] <james_w> jelmer: https://code.edge.launchpad.net/~james-w/launchpad/stop-publishing-nagging/+merge/31851 please
[16:35] <jelmer> james_w, yessir
[16:37] <james_w> jelmer: oh, second revision pushed to remove the import too
[16:39] <jelmer> k
[17:17] <EdwinGrubbs> jelmer: can you review this branch for me? https://code.edge.launchpad.net/~edwin-grubbs/launchpad/bug-602385-register-project-from-sourcepackage-page/+merge/31856
[17:18] <jelmer> EdwinGrubbs: yes, sure.
[17:18] <jelmer> EdwinGrubbs: great to see a fix for that bug.
[17:19] <jelmer> EdwinGrubbs: There seems to be a (unnecessary?) conflict in that branch
[17:19] <jelmer> EdwinGrubbs: lib/lp/testing/factory.py
[17:39] <EdwinGrubbs> jelmer: I fixed the conflict and pushed it up.
[17:40] <jelmer> EdwinGrubbs: Thanks
[17:42] <jelmer> EdwinGrubbs, lib/lp/registry/model/sourcepackage.py has a print statement in it, is that intentional?
[17:51] <EdwinGrubbs> jelmer: no, that was a mistake, the changes I just pushed should have removed that.
[18:21] <jelmer> EdwinGrubbs: I'm off soon, once but I'll finish the review of your branch.
[18:21] <EdwinGrubbs> ok
[18:31] <jelmer> EdwinGrubbs: I've just followed up
[18:32] <EdwinGrubbs> thanks
[19:57] <abentley> rockstar, I can has rubberstamp? https://code.edge.launchpad.net/~bzr-loom-devs/bzr-loom/trunk/+merge/31873
[19:57] <rockstar> abentley, rs=me
[20:14] <abentley> rockstar, I can has rubberstamp? https://code.edge.launchpad.net/~bzr-hg/bzr-hg/trunk/+merge/31876
[20:14] <rockstar> abentley, rs=me
[20:29] <abentley> rockstar, how long does a branch upgrade usually take?
[20:30] <rockstar> abentley, depends on the size of the branch.
[20:30] <rockstar> abentley, in most cases, a few minutes maximum.  In other cases, hours.
[20:30] <abentley> rockstar, this branch is taking longer than I would expect: https://code.edge.launchpad.net/~launchpad-pqm/bzr-loom/trunk
[20:31] <abentley> rockstar, takes ~2 seconds locally.
[20:36] <rockstar> abentley, it might have other branch upgrade jobs in front of it.
[20:37] <rockstar> abentley, all it's really doing is copying the tree over a local file transport, and upgrading the branch.  I can't imagine it would be that slow.
[20:38] <abentley> rockstar, it's done now, but it did take 10 minutes or so.
[20:39] <rockstar> abentley, yeah, we need some better logging.  There's an open bug about that.
[20:40] <rockstar> abentley, maybe it's small enough that I can get to it sometime today.
[22:02] <james_w> if anyone is up for a review https://code.edge.launchpad.net/~james-w/launchpad/soyuz-factory-improvements/+merge/31890
[22:15] <james_w> https://code.edge.launchpad.net/~james-w/launchpad/no-more-sampledata-2/+merge/31891 is a follow-on from that one
[23:04] <rockstar> thumper, i can has revyooz?  https://code.edge.launchpad.net/~rockstar/launchpad/recipe-build-table/+merge/31882
[23:05]  * mwhudson also has a review request, for a bug that's breaking staging and will break edge: https://code.edge.launchpad.net/~mwhudson/launchpad/disable-vostok-when-not-configured/+merge/31901
[23:06] <rockstar> mwhudson, we just talked about this on our standup.
[23:06] <rockstar> mwhudson, r=me
[23:08] <mwhudson> rockstar: thanks


[01:17] <PaulW2U> pleia2: there's a bullet point formatting error under cloud news
[01:17] <PaulW2U> I've fixed the wiki but can't edit the forum :(
[01:18] <Unit193> Oops, never said it was a-ok.
[01:18] <pleia2> PaulW2U: thanks!
[01:19] <PaulW2U> I *should* be able to edit the forum version, shouldn't I?
[01:21] <pleia2> PaulW2U: I couldn't edit your posts either, I think admins can only edit their own :\
[01:22] <PaulW2U> But now I'm a full mod.....
[01:23] <pleia2> oh, I don't know
[01:24] <pleia2> the forums confound me :)
[01:25] <PaulW2U> I'll look into it as I can't edit sammiev's posts there either and that is just wrong
[01:26] <PaulW2U> probably just a setting and it's never been a problem
[01:32] <pleia2> Welcome to the Ubuntu Weekly Newsletter, Issue 426 for the week July 13 - 19, 2015 https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue426
[01:32] <pleia2> alright, I think we're all released
[01:32] <pleia2> now to crash for 20 minutes before dinner meetup, oof
[01:37] <PaulW2U> and I must go to bed - 2:37am
[14:35] <PaulW2U> pleia2: will send you an email re forum access and editing rights
[14:36] <pleia2> PaulW2U: great, thanks
[21:28] <ahoneybun> pleia2: I did not know that was going to be in the newsletter lol
[21:32] <pleia2> :D
[21:41] <ahoneybun> pleia2: I have a blog post you could have used if I had known
[21:44] <pleia2> ahoneybun: aw, nothing on planet ubuntu
[21:58] <ahoneybun> pleia2: it is broken...
[21:58] <ahoneybun> I can't seem to get it right
[21:58] <ahoneybun> the link to my blog
[22:02] <pleia2> ahoneybun: aw, ping me on friday and I can see if I can help you fix it
[22:02] <pleia2> (conferencing this week, brain explode)
[22:02] <ahoneybun> I just found something about the links on that wiki page
[22:02] <ahoneybun> I'll try that and let you know, thanks pleia2
[22:03] <pleia2> good luck :)
[22:04] <ahoneybun> thanks
[22:04] <ahoneybun> :)


[11:19] <primes2h> good morning ara
[11:19] <primes2h> :-)
[11:19] <ara> morning primes2h
[11:21] <primes2h> I moved old reports on /Karmic/Reports and Lucid/Reports. btw,  there are two people that have left a signature but they never created a report about their laptop. I'm going to delete their entries...
[11:21] <primes2h> ara: I think it's all ok now.
[11:21] <ara> primes2h, thanks!
[11:22] <primes2h> I also added links to Karmic and Lucid reports on the main report page.
[11:22] <ara> primes2h, nice!
[11:24] <primes2h> ara: do you have other things you think should be added?
[11:25] <ara> primes2h, I think it looks good
[15:21] <xdatap> hello everybody
[15:23] <xdatap> ara, good evening
[15:23] <ara> xdatap, hello
[15:25] <xdatap> ara, newcomers in the Italian testing ML are facing difficulties in registering to the ISO Tracker. How can I help them?
[15:25] <ara> xdatap, what kind of difficulties?
[15:26] <xdatap> ara, they don't receive the welcome email
[15:26] <ara> xdatap, the ISO tracker was moved temporarily to a different server, that's maybe why
[15:27] <ara> xdatap, let me ask
[15:27] <xdatap> ara, thanks
[15:32] <ara> xdatap, it should be fixed now. Please, let me know if it does not work
[15:33] <xdatap> ara, thanks!
[15:33] <ara> xdatap, np


[08:10] <jamespage> lots of openstack clients and oslo libraries being synced from experimental today - re-alignment for rc1
[09:17] <jamespage> ^^ that last sync is needed for barbican, which is its only reverse depends in the ubuntu archive
[14:37] <Riddell> someone accepting things in double quick time or no packagset packages don't get blocked?
[14:39] <Laney> second one
[14:39] <ogra_> Riddell, there is a bot
[14:39] <ogra_> iirc
[14:39] <ogra_> for the non-packageset ones
[15:46] <coreycb> bdmurray, can you promote software-properties to trusty-updates?  for bug 1472586
[15:47] <bdmurray> coreycb: I'll have a look this morning
[15:48] <coreycb> bdmurray, thanks
[16:33] <wxl> could we turn the daily images cronjobs back on? pretty please?
[16:33] <infinity> wxl: I did so a day or two ago....
[16:34] <wxl> oh yeah i guess i was a little early today, but for the past couple days, nope
[16:34] <wxl> oh well, i'll assume all is well
[18:52] <Laney> That ubuntu-docs reminded me to run the old UDD query I had hanging around
[18:52] <Laney> https://udd.debian.org/~laney/less.txt
[18:52] <Laney> There's a few other packages where vivid{,-updates,-proposed} < wily{,-proposed}
[18:54] <Laney> just mentioning in case someone is more aroudn than I am and wants to look at it
[18:54] <Laney> Otherwise I can maybe look tomorrow
[18:54]  * Laney fades away
[19:11] <Ukikie> Seen ca-certificates get in there too.
[19:25] <robru> stgraber: https://code.launchpad.net/~robru/queuebot/ping-everybody can you merge this please?
[19:28] <infinity> cyphermox: Yo.
[19:28] <infinity> cyphermox: modemmanager.  Isn't that something the phone uses?
[19:29] <cyphermox> no
[19:29] <cyphermox> it's desktop
[19:29] <infinity> cyphermox: The phone is, AFAIK, still upstart, at least until they converge with snappy.
[19:29] <infinity> cyphermox: Oh.  No phone interest at all?
[19:29] <cyphermox> yes
[19:29] <cyphermox> no, no ubuntu phone interest at all, they use ofono instead
[19:29] <ogra_> infinity, ofono doesnt really like fighting with modemmanager over devices ;)
[19:30] <infinity> cyphermox: Kay.
[19:30] <infinity> cyphermox: The other bit I'm confused by is removal of the service link.  Do the sysv and systemd jobs still have matching names after that change?
[19:30] <infinity> (And does that mean they didn't before?)
[19:31] <cyphermox> the right name for ModemManager is ModemManager, the systemd service should be fine
[19:31] <infinity> cyphermox: But the systemd service must match the init script.
[19:31] <infinity> cyphermox: Or life goes topsy-turvy.
[19:31] <cyphermox> infinity: I'm just removing special-casing we had just for us, the package as it is in Debian should work 100%
[19:32] <cyphermox> (just for us -- just for upstart)
[19:32] <ogra_> well, it goes interesting at lleast, since the sysvinit generator of systemd would start generating another unit from the sysv script
[19:32] <infinity> ogra_: Right.
[19:33] <ogra_> are actually both installed in the binary ?
[19:33] <cyphermox> lemme get back some state about it, it's been on my hd for a little bit now
[19:35] <infinity> Erm, that's not actually a delta at all, that's in the Debian source.
[19:35] <cyphermox> right, so the service name needs to match, but we don't ship a sysv init script
[19:35] <stgraber> robru: done
[19:35] <robru> stgraber: thanks
[19:35] <cyphermox> infinity: I know, I had convinced mbiebl to keep things in debian source.
[19:35] <infinity> So the Debian package is buggy and doesn't ship a sysv init script? :P
[19:37] <cyphermox> it ships systemd magic only
[19:37] <cyphermox> the sysv script may well have been dropped, MM is typically dbus-activated by NM when needed, not just started
[19:38] <infinity> Anyhow.  Fair enough.  Please jam this in Debian too, it's rather odd to have an Ubuntu delta to remove an Ubuntu delta. ;)
[19:38] <ogra_> inception !
[19:39] <cyphermox> infinity: yep :)
[19:39]  * ogra_ doesnt like where that might go ... in the end it removes Ubuntu altogether
[19:40] <infinity> ogra_: I think it would be lovely if all Ubuntu deltas were in Debian, and all it took was changing base-files and dpkg/vendor and rebuilding Debian to get Ubuntu out of the other end.
[19:40] <infinity> ogra_: I'm pretty sure some Canonical management would disagree with me. :P
[19:40] <ogra_> hah
[21:57] <flexiondotorg> My Pebble Time has just altered me that I need to say a quick thankyou to cyphermox :-)
[21:57] <cyphermox> your pebble time alters you?
[21:57] <cyphermox> ;)
[21:58] <flexiondotorg> Well, that was a typo. But I suppose it does in a way ;-)
[22:57] <flexiondotorg> cyphermox, Can you take a peek at this merge proposal please? https://code.launchpad.net/~ubuntu-mate-dev/debian-cd/ubuntu-mate-logo/+merge/272432


[08:18] <adac> Hi there! I would like to start virt-viewer on my server via ssh. This used to work but I had to re-setup my machine and now it  is not anymore. Maybe I'm missing a package or a setting. The error I get is: https://pastebin.com/0HfHyZRU
[08:19] <RoyK> is $DISPLAY set?
[08:19] <RoyK> echo $DISPLAY - on the server
[08:19] <adac> RoyK seems to be empty. How can I set this?
[08:20] <RoyK> are you logged in directly or have you sudoed to root later?
[08:20] <adac> I'm ssh directly as root atm
[08:20] <RoyK> ok - apt install xauth might be sufficient
[08:21] <adac> RoyK, awesome! That did the trick!
[08:21] <adac> thanks a lot!
[08:21] <RoyK> :)
[10:04] <kovacs-andras> Have you realised that the latest subiquity in 22.04 still making a sha512 password hash instead of using yescrypt?
[11:25] <adac> What is actually the best way to find out which disks are the boot disks (Raid 1 for example). I guess with Raid1 all disks in the Raid have to be boot disks or?
[11:32] <adac> actually with lsbk it should be possible and reliable. there is also /boot/grub/device.map but I think that is deprecated
[12:37] <RoyK> adac: just make sure you install grub on both (or all) drives in the mirror in case one the one you booted from last time dies