[09:52] <mup> PR operator#375 opened: first pass at getting travis to do a windows run <Created by chipaca> <https://github.com/canonical/operator/pull/375>
[11:09] <facubatista> ¡Muy buenos días a todos!
[11:22] <Chipaca> FACUBATISTA: HELLO FROM WINDOWS
[11:22] <Chipaca> :-D
[11:23]  * Chipaca not really in windows
[11:23] <facubatista> Chipaca, ah, I was about to ask you if needed to be rescued
[11:23] <Chipaca> facubatista: https://travis-ci.org/github/canonical/operator/builds/717875138 tho
[11:25] <facubatista> ugh
[11:25] <Chipaca> facubatista: :)
[11:26] <facubatista> Chipaca, let's talk about terminals? You know way more than I about those, and I need some direction here...
[11:26] <Chipaca> i just wish i could trigger them directly instead of having to go me → github → travis
[11:26] <Chipaca> facubatista: shoot
[11:26] <facubatista> ho?
[11:26] <facubatista> 1:1?
[11:29] <Chipaca> facubatista: 1 sec
[11:31] <Chipaca> facubatista: 1:1
[11:50] <Chipaca> facubatista: https://github.com/paramiko/paramiko/blob/master/demos/interactive.py
[11:57] <facubatista> oooohhh
[11:57] <facubatista> wow Copyright (C) 2003-2007
[11:58] <Chipaca> facubatista: the termios stuff is because of the echo issue i mentioned (which was 'details' also)
[11:58] <Chipaca> facubatista: but, well, that's probably what we need
[12:21]  * facubatista brb
[13:19]  * facubatista is back
[13:19]  * Chipaca lives
[13:30] <bthomas> standup ?
[13:32] <Chipaca> nah
[13:32] <Chipaca> :-
[13:32] <Chipaca> :-p
[13:58] <bthomas> Chipaca: https://www.scivision.dev/python-calling-python-subprocess/
[13:59] <Chipaca> bthomas: yep, it's quite likely that's at least part of it
[13:59] <Chipaca> bthomas: thank you
[14:00] <narindergupta> Chipaca, I am looking for method to get IP address o pod .  I am trying this one self.model.get_binding("").network.ingress_address but there is no binding exist in the kubernetes and it complains ops.model.ModelError: b'ERROR no binding name specified\n'
[14:24] <mup> PR operator#376 opened: Move test_model to use Harness for resource, pod-spec tests <Created by chipaca> <https://github.com/canonical/operator/pull/376>
[14:28] <facubatista> justinclark, Chipaca, I replaced relativise content by doing pathlib.Path(os.path.relpath(dst, src.parent)) and it worked! thanks!
[14:29] <facubatista> my question is if I should leave those tests, or also just remove them
[14:29] <facubatista> (and kill relativise itself)
[14:29] <Chipaca> i don't understand how
[14:29] <Chipaca> because i ran those things and got those results
[14:29] <Chipaca> hmm
[14:30] <facubatista> Chipaca, let's dig and reproduce, it may be some obscure thing that we better find now
[14:31] <Chipaca> i'm definitely getting ../..... things now
[14:31] <Chipaca> ¯\_(ツ)_/¯
[14:31] <Chipaca> I blame justinclark
[14:31] <Chipaca> he changed all the pythons everywhere just to prove his point
[14:32] <Chipaca> that's clearly the only reasonable possibility
[14:33] <justinclark> Haha it could have been a python version thing? I'm also not sure what happens if two paths don't contain a common ancestor.
[14:33] <justinclark> I tested with 3.8
[14:34] <Chipaca> >>> os.path.relpath(str(dst), str(src.parent))
[14:34] <Chipaca> '../../baz1/baz2/baz3/dst.txt'
[14:34] <Chipaca> ^ python 3.5
[14:35] <Chipaca> (you need to str() the pathlibs, but other than that it works)
[14:35] <facubatista> justinclark, for our case they always have a common ancestor, as they must be inside the projects dir
[14:35] <facubatista> Chipaca, that result for which values of dst and parent?
[14:36] <Chipaca> facubatista: in linux they'll always have a common ancestor ('/') :)
[14:36] <Chipaca> windows might be more fun
[14:36] <Chipaca> facubatista: the same ones justinclark used in https://github.com/canonical/charmcraft/pull/118#discussion_r470604335
[14:36] <mup> PR charmcraft#118: Some changes in preparation for big "include everything but jujuignored" branch <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/118>
[14:39] <facubatista> Chipaca, justinclark, considering that in windows this can be tougher, and that the line it's not super small (`pathlib.Path(os.path.relpath(str(dst), str(src.parent)))`) I'll leave the 'relativise' function with the tests
[14:40] <facubatista> pushed
[14:40] <Chipaca> facubatista: you mean leave the function but it's just that line?
[14:40] <facubatista> yeap
[14:41] <facubatista> the separated function, with the tests, being that function just that ugly line
[14:42] <justinclark> Approved
[14:44] <justinclark> agreed - probably good to be safe and keep the tests for windows..
[15:16]  * Chipaca ⇝ physio
[15:17] <Chipaca> bbl to carry on porting fake_script to fake_pyscript
[17:06] <Chipaca> the windows test suite read like a edgelord greentext
[17:06] <Chipaca> they're all REEEEEEE
[17:16] <facubatista> jajaja
[17:24] <facubatista> Chipaca, justinclark, jam, dstathis, https://github.com/canonical/charmcraft/pull/112 is ready for review
[17:24] <mup> PR charmcraft#112: Include everything but what is explicity ignored to Juju <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/112>
[17:24] <facubatista> (thanks)
[17:35] <justinclark> Taking a look facubatista. This one will take a bit longer for me to wrap my head around. Even if someone beats me to it, I'm sure it'll still be a good exercise.
[17:39] <facubatista> justinclark, exactly! thanks
[17:39] <facubatista> ballot, I just annotated a couple of minor details in https://code.launchpad.net/~ballot/charm-k8s-mm-pd-bot/+git/charm-k8s-mm-pd-bot/+merge/388497 , thanks
[17:39] <facubatista> Chipaca, ^
[17:43] <dstathis> I'm having some issues with the operator tests
[17:43] <dstathis> When I run them, I'm getting 18 errors
[17:46] <dstathis> actually I think I figured it out
[17:46] <facubatista> dstathis, show us in a pastebin how you're running the tests and the errors you get
[17:47] <dstathis> all the errors have the message 'yaml does not have libyaml extensions, using slower pure Python yaml' somewhere in them
[17:47] <dstathis> so I'm guessing that's the problem
[17:51] <facubatista> dstathis, try doing 'apt build-dep python3-yaml'
[17:54] <dstathis> I needed to install libyaml-dev which I had already done. The tricky bit was I needed to reinstall pyyaml with --no-cache-dir
[17:55] <justinclark> I noticed that log message in the `ops.main` package ^ https://github.com/canonical/operator/blob/55158e3d1963106702222454c1cb8912c30dd077/ops/main.py#L302
[17:55] <justinclark> Is there actually a "slower pure Python yaml loader" being used somewhere?
[17:57] <facubatista> dstathis, looks like this is a good thing to annotate in the README, would you propose a PR for that? thanks
[18:01] <mup> PR operator#377 opened: change fake_script so it always creates python scripts <Created by chipaca> <https://github.com/canonical/operator/pull/377>
[18:02] <Chipaca> siiiiigh
[18:04] <Chipaca> justinclark: if you 'pip install yaml' (as opposed to apt install), and don't have the libyaml bits, you'll use a pure-python one which can be significantly slower
[18:04] <Chipaca> like 40× slower
[18:04] <Chipaca> thus the warning
[18:05] <Chipaca> but my melancholy sigh is because the fake_script PR is nasty, not because of yaml :)
[18:05] <Chipaca> but anyway, I'm at EOW
[18:05] <justinclark> Oh I see. Thanks Chipaca
[18:06] <Chipaca> justinclark: no probs! have a good one
[18:14] <mup> Issue operator#378 opened: Docstyle for `ops` is Google doc style but parsed with Sphinx <Created by justinmclark> <https://github.com/canonical/operator/issues/378>
[18:22] <mup> PR operator#379 opened: Assume version 0.0.0 if JUJU_VERSION is not set <Created by dstathis> <https://github.com/canonical/operator/pull/379>
[18:37] <mup> PR operator#380 opened: Add info about fixing pyyaml in README.md <Created by dstathis> <https://github.com/canonical/operator/pull/380>
[19:47] <ballot> facubatista: Ack thanks. I didn't know for the docstring vs "pass", TIL !
[19:48] <facubatista> ballot, :)
[19:48] <ballot> facubatista: for the index in fir format style, that's a rule from job -1. It was really really really frowned upon to NOT use index there because we had to support python 2.6 and I guess the habit stuck with me :)
[19:48] <facubatista> ballot, ah, yes, in the prehistory it was mandatory
[19:49] <ballot> facubatista: prehistory is actually daily lives on some software, sadly :/
[19:49] <ballot> facubatista: especially when you have to support ... centos 6
[19:49] <facubatista> ugh
[19:49] <ballot> oh well that's behind me now
[19:49] <facubatista> right, charms are py3 only
[19:49] <facubatista> >=3.5
[19:49] <ballot> yup
[19:50] <ballot> Will adapt accordingly next time I have to touch the charm
[19:54] <facubatista> ballot, thanks!
[21:12] <justinclark> facubatista: is there an issue or discussion somewhere that gives context to https://github.com/canonical/charmcraft/pull/112? I think that would help me understand what's going on.
[21:12] <mup> PR charmcraft#112: Include everything but what is explicity ignored to Juju <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/112>
[21:13] <facubatista> justinclark, that issue, but note that inside that issue a discourse page is linked
[21:13] <facubatista> that maybe will provide more context
[21:14] <facubatista> the bottom line is: what should go inside a charm? we started nickpicking some specific parts (the charm, metadata.yaml, etc), but experience proved that people want more stuff in... so, what should we include? we ended up deciding "everything that is not being ignored by juju"
[21:18] <justinclark> I might be blind.. Is there a linked issue in that PR? I see https://github.com/canonical/charmcraft/issues/39 which seems related to what you're saying
[21:22] <justinclark> But that gives me plenty to work with ^ thanks facubatista
[21:26] <facubatista> justinclark, ah, right, it's linked in the issue, not in the PR
[21:27] <facubatista> there I linked the issue to the PR
[21:27]  * facubatista eods and eows now
[21:27] <facubatista> see you all on Tuesday!
[21:35] <justinclark> Have a good holiday weekend!


[02:15] <micahg> ajmitch: ping about backports open at feature freeze LP stuff :)
[02:16] <ajmitch> micahg: pong about replacement system sitting behind me for dead hardware at home ;)
[02:17] <micahg> ajmitch: heh, I just had to swap out RAM last night myself :)
[02:17]  * ajmitch had it go kaput altogether
[02:17] <ajmitch> yes it's been on my todo list to get it in, sorry I missed FF
[02:18] <micahg> ajmitch: anytime before R would be fine IMHO :)
[02:19] <ajmitch> sooner the better
[02:19] <ajmitch> I'll bug StevenK to help me land it soon, he won't mind much
[02:20]  * StevenK glares at ajmitch.
[02:20] <ajmitch> you did offer
[03:19] <ScottK> micahg: Cool.
[03:19] <ScottK> Thanks for letting me know.
[07:22] <oly> hi, I am quite new to debian packageing, is anyone able to shed some light on this error ? E: geany-plugin-code-snippets: dir-in-usr-local usr/local/share/
[07:36] <oly> I am also getting this error using a slightly different rules file which has me stumped, rmdir: failed to remove `debian/geany-plugin-code-snippets/usr/local/share/geany/geanypy/plugins/geany-snippets': Directory not empty
[07:37] <oly> why the build process would be creating files it can then not delete later on is a tad strange
[07:42] <geser> it's not a file but a non-empty directory you try to remove
[07:43] <oly> yeah i get that but i dont get why, as its all pretty much done and handled by the build process as far as i can tell
[07:44] <oly> I am no longer doing anything in the rules file and leaving it to the helpers to manage
[07:45] <oly> I basically have %:	dh $@ in my rules file
[07:45] <oly> this is a python program, and i have created similar projects and not hit the issue
[07:47] <oly> I have everything on launchpad bzr branch lp:~oly/geany-code-snippets/trunk
[07:47] <oly> and i am building with bzr-buildpackage -- -uc -us if thats any help, the debian files are in the repository as well if anyone has any ideas
[07:49] <geser> your debian/install files mentions to copy the geany-snippets directory to there (/usr/local/...)
[07:50] <oly> yeah, its the path for the plugin folder for geany
[07:51] <geser> a package shouldn't install to /usr/local/...
[07:51] <geser> does geany find the plugins also in /usr/share/geany/...?
[07:51] <oly> hum, maybe will look see if that exists
[07:52] <geser> if yes then let your debian/install install it there (simply remove the /local from the path)
[07:53] <oly> does not exist, but i recon your onto something geser :)
[07:53] <oly> got a feeling my machines have geany compiled from source, instead of from the debian file which could be why the paths are different
[07:54] <oly> I will setup a vm to test this out, thank you for your time.
[07:57] <oly> well changing the path fixes all my issues at least, so i know its definitely the /usr/local causing me the issues :)
[14:16] <marcos> hello everybody.
[14:16] <marcos> someone Can you tell me about "edit-patch" command? i try create a new patch for hello package but "no series file found" error occurs.
[14:17] <marcos> may be this is a basic question, but i'm a n00b :)
[14:17] <marcos> developer n00b*
[14:17] <arand> That sounds like there are no current patches? 'series' is normally the patch "index" file
[14:18] <marcos> arand: very curious. the help say to create a new patch with edit-patch.
[14:18] <marcos> where is series file?
[14:19] <arand> Which help?
[14:20] <marcos> arand: man page. sorry.
[14:21] <marcos> "It  can  also be used to incorporate new patches."
[14:23] <arand> I'm not sure if it would work if you just "mkdir debian/patches; touch debian/patches/series" ...
[14:25] <marcos> doesn't work :(
[14:26] <marcos> may be i wait for class about patches in ubuntu developer week to learn how i can make a patch
[14:26] <marcos> by the way, there's a channel about ubuntu cloud? i have a specific question about juju and cloud.
[14:27] <Bachstelze> marcos: "new patches" here means "adding a patch when patches already exist"
[14:27] <Bachstelze> if there are no patchs you have to create a patch system before
[14:27] <marcos> Bachstelze: first create a .patch file. second: add to source?
[14:28] <marcos> Bachstelze: or: exist a patch. add another patch?
[14:28] <Bachstelze> marcos: to create the first patch you can use quilt directly for example
[14:29] <marcos> Bachstelze: ok. thanks. the session about patches on developer week may be very helpful :)
[14:44] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 2 starting in ~15 minutes in #ubuntu-classroom
[17:02] <FlowRiser> uhmm, hello :D
[17:03] <FlowRiser> I want to develop a new login screen for Ubuntu. What's the best way to do this ? (to make it as lightweight as necessary)
[17:04]  * ogra_ thought that was actually the purpose of lightdm
[17:05] <FlowRiser> oh, hi ogra;
[17:05] <FlowRiser> ogra_: it is, but i want to style it up a bit
[17:05] <FlowRiser> and to be honest, i find the lightdm documentation lacking
[17:32] <xnox> FlowRiser: "style it  up" visuals or code/features? There are multiple lightdm login screen (greeters) providers in: gtk, kde, and other toolkits. (html/css as well or am I wrong)
[17:33] <xnox> FlowRiser: pull the sample code with apt-get source and hack away.
[17:33] <FlowRiser> xnox: i tried to do that, but they just won't make sense for me; Is it possible to use C++/GTK ?
[17:34] <FlowRiser> xnox: i found a python sample, a commented sample; That i can convert to c++, but i'm not sure if the headers will work ...
[17:35] <FlowRiser> My main problem is that the most sample codes are not commented at all
[17:36] <xnox> my opinion "you are doing it wrong if you are using C++ & GTK", but it should still all work just fine.
[17:37] <xnox> FlowRiser: take Qt sample/greeter. It's in C++. Look at the unity greeter (is it gtk? i think it is)
[17:37] <xnox> for equivalent gtkmm stuff.
[17:37] <FlowRiser> so gtkmm is for c++ ?
[17:38] <FlowRiser> this works
[17:38] <FlowRiser> wow
[17:38] <FlowRiser> thanks :D
[17:38] <FlowRiser> xnox: But why do you think, it is wrong to use C++ & GTK ?
[17:39] <xnox> FlowRiser: because GTK is a C toolkit for C and it implements it's own object model. gtkmm are C++ bindings with C++ objects.
[17:40] <xnox> using C implementations of objects in C++ is not sensible at all.
[17:40] <xnox> C++ & gtkmm is somewhat sensible
[17:43] <FlowRiser> xnox: Thanks allot! This is handy info, and the code makes sense to me now :)
[17:44] <FlowRiser> When i finish my greeter, how can i make it public ?
[17:44] <Manoj> #hackerrank


[22:16] <pleia2> finally just used adb to set my ridiculous wifi password, so I was able to get on my wifi and upgrade my nexus7
[22:16] <pleia2> things are looking really good :)
[22:22] <akk> You did this because it doesn't keep an existing connection open when you connect with adb?
[22:22] <pleia2> akk: I don't understand the question :\
[22:23] <akk> Isn't there normally a gui on tablets for setting wifi password? I was trying to figure out why you'd need to use adb.
[22:23] <pleia2> oh, there's a bug for long passwords https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445630
[22:23] <darthrobot> Title: [Bug #1445630 “Can't connect to Wifi network secured with long PS...” : Bugs : Canonical System Image]
[22:23] <pleia2> so it doesn't work through the gui
[22:25] <akk> ah
[22:26] <pleia2> on most devices I just tether through my phone for a minute so I can grab the wifi password in email and copy/paste, but that doesn't work either https://launchpad.net/bugs/1454416
[22:26] <darthrobot> [R: bugs.launchpad.net] Title: [Bug #1454416 “WiFi connect dialog does not allow pasting of pass...” : Bugs : unity8 package : Ubuntu]
[22:26] <pleia2> so adb was my only option
[22:26] <ianorlin> I like how ethernet just works
[22:27] <ianorlin> even with my like 10 year old pci card
[22:27] <ianorlin> on a desktop I built last year
[22:27] <ianorlin> althuogh showing better speedtests than other people with that is a little rude
[22:29] <akk> Yeah, it's sad seeing the new trend toward laptops with no wired ethernet.
[22:30] <akk> For ubuntu/debian installs sometimes that's been the only option for me.
[22:30] <ianorlin> also then you can't set up bridge utils from a working laptop with wifi and plug an ehternet cord to a working laptop with wifi if it needs the stupid broadcom blob
[22:31] <ianorlin> it actully worked
[22:31] <akk> Right, exactly.
[22:31] <akk> It's still all too common to have laptops where the wifi doesn't work right in the installer.
[22:31] <ianorlin> I keep an ancient usb wifi that is b/g around because it works with kernel
[22:32] <akk> I just put a couple of usb wifi dongles in my laptop bag after a vacation where I had no net access
[22:33] <akk> because the latest linux driver for my broadcom chip couldn't talk to the hotel's WEP (who uses WEP these days? answer: hotels in the Utah boonies)
[22:33] <ianorlin> I had the broadcom driver flood my ttys with stupid messages for several months until an update fixed it
[22:34] <akk> At that hotel, attempting to connect to the WEP wifi turned off the chip at the level where rfkill said it was both hard and soft blocked
[22:34] <akk> but couldn't un-block it
[22:35] <akk> and even rebooting didn't fix that, it was still rfkill blocked
[22:35] <akk> but I finally tried rebooting into a distro with an earlier kernel, and that unblocked it (it still didn't connect, though)


[20:26] <TheSonOfPeter> Goodafternoon what are we allowed to discuss in this channel?
[20:34] <tomreyn> TheSonOfPeter: the purpose of this channel is state don /topic -and the overall guidelines stated in #ubuntu 's /topic most likely apply here, too
[20:36] <tomreyn> most of the time: make use of common sense and you'll be fine.


[14:59] <oerheks> best Q of today; "trying to extundelete some stuff chatgpt gave me a command to. (git clean -something)"
[15:00] <oerheks> 🤣
[15:01] <ogra> lol
[15:07] <oerheks> ogra, should we have a factoid too?
[15:07] <oerheks>  <randall> !chatgpt [17:06:02] <dpkg> Don't ever take ChatGPT as advice to fix your Debian problems. It's just as bad as following random stackexchange advice, from which ChatGPT likely was trained from.


[19:18] <Guest99> hi
[19:18] <leftyfb> Guest99: you are welcome to also hang out in #ubuntu in case someone comes along that might know how to help you
[19:20] <Guest99> i tryed there they say to go here instead
[19:20] <leftyfb> Guest99: it was me who suggested to also try here.
[19:21] <Guest99> then i shouldleave then ?
[19:21] <leftyfb> I pointed you here to potentially get a quicker answer since the folks here work with Budgie directly.
[19:21] <leftyfb> Guest99: you know you can join more than 1 channel at a time on IRC right
[19:22] <Guest99> im sorry this is kinda confuseing
[19:22] <Guest99> i will leave now , have nice day


[19:07] <internalkernel> BugeyeD_: I'm running into a wall with my rsync incremental backups, how do I remove the duplicate files from each snapshot?
[19:07] <internalkernel> I was thinking of something along the lines of --remove-source-files or --itemize-changes to get a list of the files that are unique to that snapshot....
[19:08] <internalkernel> My goal is to end up with only the changed files in the directory... so I can tarball that and archive it. Got any ideas?