[06:13] <tj_> /
[06:22] <brcol> What's up everyone?
[08:39] <xu-irc90w> hello! It's strange but mi wireless use to work fine till a couple of days, but after last update no networks are shown...  The device is recognized and turn on but in the menu Network Manager says "Device is not ready"  HELP!
[08:41] <xu-irc90w> UBUNTU 20.04.0-40
[08:43] <KBar> What was updated? Can you check the /var/log/apt/history.log file?
[08:44] <xu-irc90w> rfkill shows two devices (wlan) "ID 0 acer-wireless" and "ID 1 phy0"  could that be?
[08:44] <xu-irc90w> Yes all do that ...
[08:46] <xu-irc90w> 2021 11009 16:36
[08:46] <xu-irc90w> lots of things, it was a major update...
[08:46] <xu-irc90w> I am writing from another machine
[08:47] <xu-irc90w> the xubuntu one is from a friend I help using linux and installed xubuntu...  she gave me the machine because she did not know how to update...
[08:48] <KBar> If you're sure it was after last update, then it's very obvious what to do to fix it.
[08:48] <xu-irc90w> so yesterday I perform the update (huge) and everything is fine excep this issue with the wifi
[08:49] <xu-irc90w> don have timeshift in that machinf...
[08:49] <xu-irc90w> machine
[08:49] <xu-irc90w> what can I do is that obvious (sorry)
[08:50] <xu-irc90w> I don know how to undo the update, besaides I should update at some point no?
[08:53] <xu-irc90w> KBar, What is that obvious thing I don't seem to come up with? : )
[08:55] <xu-irc90w> isn't than wired the output of rfkill showing two wlan devices ?  "acer-wireless" and "phy0"?
[08:56] <xu-irc90w> KBar, please don't giveup on me!  ;  /
[09:06] <xu-irc90w> sorry I need to take down my doggy for a short moment. Be back in a few minutes. Thanks for your patience!
[09:14] <xu-irc90w> I am back..
[10:24] <xu-irc90w> ok! I guess it's lost case. I will have to reinstall. Thnks for your help. bye
[10:25] <xu-irc90w> exit


[01:13] <callmepk> good morning
[01:24] <duflu> Morning callmepk
[02:32] <callmepk> morning duflu
[04:55] <jibel> Good morning $world
[04:59] <duflu> Good morning jibel
[05:03] <jibel> Hi duflu
[05:04] <jibel> hmm, something brings down my entire session when I do a package update.  I wonder what actionnable solution we have
[08:58] <seb128> didrocks, ignore the noise and move on? ;-)
[08:58] <didrocks> seb128: well, we try to keep the list clean, it’s like when you have your first compilation warning on a project and finish with hundreds
[08:59] <didrocks> or same in syslogs :p look at it and you will be scared
[09:00] <seb128> right, I get that, but we don't seem to have an option that doesn't create ongoing workload for our team
[09:00] <seb128> so between noise and increased workload...
[09:01] <seb128> not that I'm happy about it :-/
[09:01] <didrocks999> let’s see what cpaelzer says about it
[09:22] <Laney> is it component-mismatches or germinate not understanding the provides?
[09:25] <didrocks999> germinate from my notes of a discussion between v_orlon and s_eb128
[09:26] <seb128> unsure, or it doesn't like the Recommends having universe options listed as first alternatives
[09:26] <didrocks999> oh, I think you were more categoric that it was the germinate output triggering this
[09:26] <seb128> but changing the order would mean adding a diff over Debian...
[09:26] <seb128> I don't understand germinate enough to make statement, but I pointed out to the reply from Steve
[09:27] <seb128> he's probably right in what he said but I didn't check
[09:27] <jibel> Laney, hi, the ubiquity MP has been updated, can you do another pass?
[09:27] <Laney> Ordering would be weird, it should be able to resolve the relationship with what's there already
[09:27] <Laney> jibel: yeah, I saw, will do later!
[09:28] <jibel> thanks
[09:29] <Laney> hmmmmmmmmmmmmmmm
[09:31] <Laney> didrocks999: seb128: https://paste.ubuntu.com/p/p6zmXmwSN7/
[09:31] <Laney> We don't build ubuntu-desktop on riscv64/s390x, so the Provides isn't there
[09:33] <didrocks999> oh good catch, the issue would be only on those 2 archs… Then the info is lost when c-m takes that as an input
[09:34] <didrocks999> then, excluding the arch on packagegit will introduce the same delta issue…
[09:36] <seb128> would be nice to have an ignore list to add such items...
[09:40] <didrocks999> that’s why I tried the blacklist in the platform seed
[09:40] <didrocks999> but no luck
[09:40] <seb128> :-(
[09:41] <Laney> I think it's going to have to be fix c-m
[09:41] <Laney> e.g. to look at seeds and where they are supposed to be supported
[09:43] <Laney> or stop this happening somehow
[09:43] <Laney> laney@snakefruit:~$ chdist apt-cache groovy-proposed-riscv64 show gstreamer1.0-packagekit | egrep '^Task'
[09:43] <Laney> Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-budgie-desktop
[09:46] <Laney> but either of those are sort of saying that on these arches it's ok for things to not be installable with main only
[09:46] <Laney> perhaps that is ok
[10:55] <cpaelzer> didrocks999: I was experimenting with blacklist today for other reasons
[10:55] <cpaelzer> didrocks999: it seems to have no effect at all and also isn't in the STRUCTURE file anymore
[10:57] <cpaelzer> first of all the same file is present on platform and ubuntu
[11:00] <cpaelzer> adding the package "totalbullshit" to the blacklist on both seed repos makes it NOT show up in the output of germinate
[11:01] <cpaelzer> so the blacklist mechanism seems to be no more exist
[11:06] <cpaelzer> and due to that your recent change does nothing at all
[11:06] <cpaelzer> per germinate doc there is a different way to blacklist
[11:06] <cpaelzer> I'm experimenting with it right now
[11:07] <Laney> cpaelzer: what are you trying to do?
[11:08] <Laney> blacklist entries are almost never the right thing
[11:08] <cpaelzer> Laney: two things, first: above didrocks tried to get gnome-software to no more show up (there is a longer story around snaps behind it)
[11:08] <Laney> *maybe* if you want to cause FTBFS they're appropriate
[11:09] <cpaelzer> Laney: and second: I have a virtual package and some of the providers of said virtual pkg are in main, but it pulls in others which now are in component mismatches
[11:09] <cpaelzer> I was looking at it (experimentally) for the latter and saw the question of didrocks999 above
[11:10] <cpaelzer> and since I just found that blacklist either are processed later (post germinate) or never at all I thought I'll let didrocks999 know about it
[11:14] <cpaelzer> Laney: if you happen to know if the blacklist files are actually used ...? because otherwise we could as well remove them to not mislead.
[11:15] <cpaelzer> Laney: and OTOH if you know a way I can convince germinate to use a pkg already seeded (as described in the germinate man page) instead of a random one in the following step I'd appreciate that as well
[11:15] <cpaelzer> germinate.log:1615:* Chose esmtp-run out of mail-transport-agent to satisfy logcheck
[11:28] <Laney> cpaelzer: I don't know why postfix isn't picked there, that's weird to me since it's in the same seed...
[11:29] <Laney> but I do think that blacklist wouldn't help, it doesn't make germinate try a different path, just would give you an error at best (AFAIK)
[11:29] <cpaelzer> yeah I already found that adding it to blackist won't help too much
[11:30] <cpaelzer> but I fund that we have at least one blacklist file too much (the one in platform.git)
[11:30] <cpaelzer> it isn't read at all
[11:30] <Laney> yeah no idea what that is
[11:31] <Laney> I'm talking about the "* !package" entries when I talk about blacklists
[11:31] <Laney> you might have to ask Colin to help you with the default-mta thing :(
[11:31] <cpaelzer> default-mta is fine, just mail-transport-agent picks up the wrong thing
[11:32] <Laney> it's an or-ed dependency
[11:32] <cpaelzer> yes, and it picks the worst possible
[11:32] <Laney> if default-mta was working it would have followed the first branch and picked postfix there
[11:32] <cpaelzer> it resolves default-mta to postfix and mail-transport-agent to esmtp and then picks the latter
[11:32] <Laney> but it's obviously backtracked
[11:33] <Laney> which means default-mta is not working
[11:33] <cpaelzer> hmm true
[11:33] <cpaelzer> germinate.log:1614:? Unknown dependency default-mta by logcheck
[11:35] <Laney> Unknown supported-misc-servers package postfix
[11:35] <Laney> why
[11:35] <cpaelzer> the log is full of those
[11:37] <Laney> I think this is your problem, whyever that is
[11:40] <Laney> it clearly is in main
[11:40] <Laney> weird weird
[12:08] <xnox> Wimpress:  Laney: Raspiberry Pi
[12:09] <xnox> is that the right way to spell it?
[12:15] <xnox> Raspyberry P
[12:16]  * xnox loves all the variations
[13:15] <Laney> didrocks999: seb128: I just thought at lunch: we could make the seed have gstreamer1.0-packagekit [!riscv64 !s390x] to fix this thing probably
[13:21] <didrocks999> Laney: worth a try, good idea
[13:26] <xnox> Laney:  oooh, i like that.
[13:28] <Laney> it's kind of weird that you have to do this when the metapackage is arch-restricted already, but germinate doesn't know that
[13:29] <Laney> maybe seeds could get that concept as a top-level thing: Seed-Arch: amd64 arm64 i386 ppc64el
[13:29] <Laney> today is a germinate day!
[13:29] <Laney> (talking about it, not doing any actual work on it, the best kind of contribution)
[13:32] <xnox> Laney:  i still don't know the point of the supported seed, given that components-missmatches doesn't look at it. It looks at all seeds ever.
[13:34] <Laney> what do you mean it doesn't look at it, it surely does
[15:01] <hellsworth> good morning desktopers
[15:01] <oSoMoN> good morning hellsworth
[15:01] <hellsworth> hey there oSoMoN
[15:10] <Laney> greetings hellsworth
[15:10] <Laney> how goes
[15:14] <hellsworth> hey there Laney! oh i'm ok, moving slower this morning.
[15:14] <Laney> age catches up on us all
[15:14] <hellsworth> it snowed over night. the earliest snow in record
[15:15] <hellsworth> and it's grey and snowy out... makes the bed seem warmer :)
[15:15] <Laney> nice
[15:15] <Laney> is it sticking around then?
[15:15] <hellsworth> so yesterday the high was like 2 and the day before.. 34
[15:15] <hellsworth> just wild
[15:15] <hellsworth> nah it'll melt over the next couple of days but there's snow on the ground now
[15:19] <Laney> snow angel STAT
[15:21] <hellsworth> haha no it's too wet to really work for a snow angel :)
[17:09] <KGB-2> adwaita-icon-theme signed tags 53f64a6 Iain Lane ubuntu/3.37.92-1ubuntu1 * adwaita-icon-theme Debian release 3.37.92-1ubuntu1 * https://deb.li/qYQh
[17:09] <KGB-0> adwaita-icon-theme ubuntu/master 7b12ebd Iain Lane * pushed 38 commits (first 5 follow) * https://deb.li/3V39c
[17:09] <KGB-0> adwaita-icon-theme ubuntu/master 7c14436 Jakub Steiner Adwaita/ (55 files in 5 dirs) * Merge branch 'wip/jimmac/weather-icons' into 'master' * https://deb.li/Dip7
[17:09] <KGB-0> adwaita-icon-theme ubuntu/master 8a3fff5 Simon McVittie (12 files in 5 dirs) * New upstream version 3.37.2 * https://deb.li/3RCbd
[17:09] <KGB-0> adwaita-icon-theme ubuntu/master f582e3b Simon McVittie (12 files in 5 dirs) * Update upstream source from tag 'upstream/3.37.2' * https://deb.li/T7HF
[17:10] <KGB-0> adwaita-icon-theme ubuntu/master d91e5b7 Simon McVittie debian/changelog * New upstream release * https://deb.li/i3151
[17:10] <KGB-0> adwaita-icon-theme ubuntu/master a2db8db Simon McVittie debian/ copyright copyright.pl CC-BY-SA-4.0.license * d/copyright: Add CC-BY-SA-4.0 reference * https://deb.li/Q7dj


[00:04] <harlowja> smoser btw, it seems like some parts of openstack are moving away from httpretty to https://pypi.python.org/pypi/httmock/
[00:05]  * harlowja might have to dig into why to see if cloud-init should or shouldn't
[08:21] <harmw> mwhudson: I think I have time for aarch64 (or whatever the correct name is) somewhere in and/or after the weekend
[08:21] <mwhudson> harmw: yay
[08:21] <mwhudson> i am on leave for a week so no real hurry:)
[08:21] <harmw> oh lol
[08:21] <harmw> you've got the original arm image working btw?
[08:22] <mwhudson> haven't tried
[08:23] <harmw> what kind of hardware do you run anyway, since it's aarm64 (which isn't widespread in the embedded/small world just yet)?
[08:23] <mwhudson> i keep poking people about things and then forgetting that i'm away next week
[08:23] <harmw> seamicro stuff?
[08:23] <harmw> :P
[08:26] <mwhudson> harmw: i work for canonical / linaro so have access to preprod stuff
[08:28] <harmw> how nice
[08:28] <harmw> :)
[08:30] <mwhudson> yeah it's kinda fun
[08:30] <mwhudson> can't really talk about it though, which is a bit annoying :)
[08:30] <harmw> haha np
[21:18] <smoser> harlowja, i do not understand something
[21:18] <smoser> (big surprise)
[21:18] <harlowja> ?
[21:19] <harlowja> let me help you child
[21:19] <harlowja> how may i help u child
[21:19] <harlowja> j/k
[21:19] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/794/cloudinit/util.py#L148
[21:19] <smoser> if stat.ST_MODE in stats
[21:19] <harlowja> k
[21:20] <harlowja> ^ u just not want that statement?
[21:20] <smoser> what is it for?
[21:21] <smoser> it doesn't seem tomake sense.
[21:21] <smoser> stat.ST_MODE is 0
[21:21] <smoser> (a constant)
[21:21] <smoser> why would you say:
[21:21] <smoser> if 0 in os.stat("/etc/passwd")
[21:21] <smoser> what would that even mean?
[21:22] <harlowja> agreed, wonder why i did that
[21:22] <smoser> ok. thanks.
[21:23] <smoser> that test was failing in sbuild
[21:23] <smoser> where /etc/hosts didn't exist
[21:23] <smoser> so i was making a temp file
[21:23] <smoser> and then the tem pfile for whatever reason did not have a '0' in os.stat()
[21:23] <harlowja> ya, seems like just do stats[stat.ST_MODE]
[21:23] <smoser> yeah, i think that is what youmeant
[21:23] <harlowja> must of been smoking crack when doing that
[21:23] <smoser> but dont even know what that would do
[21:23] <harlowja> ya, odd
[21:23] <smoser> i have to run.
[21:23] <harlowja> all the cracks fault
[21:24] <smoser> for now i will just take that code out
[21:24] <smoser> later
[21:24] <harlowja> kk
[23:25] <smoser> harlowja, can you verify the os.path.realpath and os.path.expanduser seem odd at http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/util.py#L148
[23:26] <harlowja> don't seem so odd if u want the actual path?
[23:29] <smoser> but why didn't they give you the actual path in the first place.
[23:30] <smoser> what if they explicitly gave you a path with a '~' in it that should not have been expanded.
[23:30] <smoser> i guess if you need the full path it makes sense.
[23:30] <smoser> but the expanduser seems like it could false positive
[23:47] <smoser> harlowja, http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/987
[23:47] <smoser> thanks for your help.
[23:48] <harlowja> smoser ya, likely could just remove expanduser
[23:49] <harlowja> smoser cool, selinux will i guess work better now