[00:07] <emgent> heya
[00:07] <NCommander> hey emgent
[00:07] <emgent> hey NCommander
[00:07] <NCommander> emgent, what be up?
[00:07] <emgent> i saw your private message about utu
[00:08] <emgent> one moment :)
[00:08] <emgent> fixed
[00:11] <NCommander> Cool
[00:11]  * NCommander eyes #4 on the list
[01:51] <kirkland> anyone familiar with inoticoming?
[01:52] <kirkland> is it possible to watch an nfs-mounted directory?
[02:21] <james_w> if you get "warning: format not a string literal and no format arguments" for a printf(foo); call then the fix is printf("%s", foo); isn't it?
[02:21] <james_w> I mean, the two printfs are equivalent, correct?
[02:21] <Byrnison> I think so.
[02:22] <Byrnison> The latter will not do formatting if foo has %'s.
[02:22] <Byrnison> But that's the point.
[02:23] <james_w> but formatting would require subsequent arguments wouldn't it?
[02:24] <Byrnison> Yes.
[02:25] <james_w> ok, thanks
[02:25] <Byrnison> The warning is there because printf(foo); is dangerous if foo is a user-inputted string. It would probably crash the program if there were %'s in the string. There are worse things that could happen, though.
[02:49] <phirestalker>  I am trying to compile a program but it is giving a version mismatch error on libtool. I have libtool 2.2.4 but the program may be expecting the old 1.5, what can I do?
[02:53] <ScottK> relibtoolize.
[02:54] <phirestalker> that didn't work I have tried libtoolize and libtoolize --force, I have also tried aclocal to rebuild aclocal.m4 as the error suggests but nothing works
[02:55] <phirestalker> they developers say they have got it to compile on the same version of linux I have Ubuntu 8.10, so I guess it is something about my system
[03:05] <NCommander> ScottK, feel like sponsoring an upload?
[03:06] <phirestalker> what files besides ltmain.sh have commands or directives that pertain to libtool that I may need to update to match ltmain.sh?
[03:08] <NCommander> phirestalker, what package is it?
[03:09] <phirestalker> it is oreka from oreka.sourceforge.com
[03:09] <NCommander> (usually you can get away with libtoolize --force --install --verbose in the source code folder)
[03:11] <phirestalker> the only complaint seems to be about install-sh: libtoolize: `/usr/share/libtool/config/install-sh' is serial 2<IP_ADDRESS>, greater than 0 in `./install-sh'
[06:25] <stefanlsd> Anyone with a WP installation that gets the WP update announcement that can test something for me?
[08:32] <thinkgnu> how can i make a changelog ? is there any tool to create a standard changeLog ?
[08:33] <thinkgnu> it seems i should ask my question in #ubuntu-motu !
[08:34] <thinkgnu> or not !?
[08:38] <legreffier> just write yours in the standard
[08:38] <legreffier> way
[08:39] <legreffier> it's pretty trivial...
[08:40] <thinkgnu> i do that already :)
[08:46] <legreffier> there's an emacs helper dpkg-dev-el
[08:46] <legreffier> it has a changelog mode
[08:46] <legreffier> might help
[08:54] <Hobbsee> legreffier: thinkgnu dch (dch -i is also useful)
[08:58] <legreffier> it's not in my ubuntu :/
[08:58] <legreffier> (using hardy currently)
[08:58] <thinkgnu_> me too ! :P
[09:01] <thinkgnu_> legreffier: it seems you need ubuntu-dev-tools
[09:06] <legreffier> apt-cache search dch didn't show the way, thanks
[09:07] <thinkgnu_> np ;)
[09:13] <thinkgnu> Hobbsee:  it seems what i want , thanks.
[10:04] <directhex> man, still with the a1? o_o
[11:29] <deufrai> hi there, is it the right place to ask for advice about packaging for ubuntu ?
[11:30] <cjwatson> deufrai: #ubuntu-motu is more used to doing mentoring work
[11:30] <deufrai> cjwatson: thank you
[11:32] <cjwatson> directhex: ^-
[11:36] <ogra> urgh
[11:37] <ogra> so how am i supposed to handle a patch in a quilt package that needs an autoreconf run ?
[11:37] <ogra> afaik quilt requires me to add all touched files to the patch, how would i know which these were ?
[11:38]  * ogra curses quilt once again
[12:20] <soren> ogra: What I've done on a few occasions is to do all the patching I wanted, dpkg-buildpackage -S, run debdiff between the previous version and this one, filterdiff -x '*debian/*'.. That's usually the stuff that ought to be in the quilt patch... So I pipe it to a file and quilt import that, and "patch -R -p1" it on the dev tree. Presto.
[12:20] <ogra> phew
[12:20] <ogra> lots of work induced by a silly patch system :)
[12:20] <soren> It sounds bad, yes.
[12:20] <ogra> but right, that would indeed work
[12:20] <soren> You get used to it, though :)
[12:21] <soren> Have fun! :)
[12:21] <ogra> well, i ry to stay away from quilt, but wanted to see whats up with rpm (keeps alien from armel)
[12:21] <ogra> rpm itself is weirdly packages though
[12:21] <ogra> *packaged
[12:22] <ogra> soren, thanks for the hint
[12:22] <ogra> :)
[12:22] <soren> Quilt is growing on me, actually. It's very good when patches need to be refreshed.
[12:22] <soren> ogra: sure thing.
[12:22]  * soren wanders off again
[12:22] <ogra> right, but in cases like the above i would just liked dpatch or even cdbs-edit-patch
[15:16] <directhex> cjwatson, yay! of course, now someone needs to ack the mono upload. where's pitti hiding...
[15:19] <persia> directhex, NEW or upload?
[15:20] <persia> directhex, Reason being that most of the archive admins won't NEW stuff they upload, so if it needs both, you might do better to find a non-archive-admin uploader.
[15:21] <directhex> persia, name names. the longer this takes, the more painful it is for everybody
[15:22] <persia> directhex, See, it's not about names.  It's about teams.
[15:22] <persia> I think you already subscribed ubuntu-main-sponsors.  From there, someone ought get it.
[15:22] <persia> Mentioning the bug and asking generally for an upload is one way to escalate, but doing that too much tends to bother people.
[15:23] <persia> Asking each of the main sponsors individually is very likely to bother people.
[15:23] <persia> My main recommendation is that if you are going to poke specific individuals, it might be fastest to not poke the archive-admins until the new package split is waiting in NEW, just because of the multistep process involved.
[15:24] <persia> (and launchpad does have a list of main sponsors, if you're *really* curious)
[15:30] <directhex> persia, it's not my intention to be more obnoxious than my natural baseline level, i'm just a bit fed up with queues at the moment - especially on a package which experience says a lot of people don't want to be associated with. the last thing i want to see is a release turn up halfway through a package transition, gnat-style
[15:31] <Silicium> hi there
[15:31] <Silicium> iam searching for the gnome-volume-control maintainer
[15:31] <directhex> in my defence, pitti IS in u-m-s, and has been helpful in the past when i've needed merges and updates to get pushed through
[15:32] <directhex> Silicium, Ubuntu Desktop Team<EMAIL_ADDRESS>[15:32] <Silicium> ok i will try
[15:33] <Silicium> so maybe anoyne know that bug
[15:33] <persia> directhex, Sorry if I came off wrong: I don't mean to attack you: it's just that because I know you're doing a source split, and because the set of archive-admins is smaller than the set of main sponsors, I thought you'd be faster with another.
[15:34] <Silicium> gnome setting "detachable menubars" was set, and the menubar of gnome-volume-control has been detached, and now it coulnt be attached again, the app faults with the following msg:
[15:34] <Silicium> Bonobo:ERROR:(bonobo-dock-item.c:1342):bonobo_dock_item_get_child: code should not be reached
[15:34] <Silicium> i think i should directly contact the gnome-dev ml
[15:35] <directhex> persia, s'okay. what with ubuntu-motu@lists and boycottnovell.com, i assume a baseline level of attack at all times :p
[15:35] <persia> directhex, I can see that.
[15:35] <azeem> Silicium: file a bug, rather
[16:29] <maxb_> I've just had usb-creator hang, and I think it's because I was using a USB stick that turns out to be preformatted *without* an MBR: i.e. /dev/sdb is a vfat FS, *not* /dev/sdb1 !
[16:38] <directhex> maxb_, i've lost track of whether you're meant to do that or not, in general. i know i've had devices which looked at me funny for not doing what they expected
[16:39] <persia> maxb_, If you can recreate with it formatted that way, and the same key works with partitions, please file a bug.  usb-creator is expecting partitions, but it's not supposed to hang.
[16:56] <doko> cjwatson, Riddell: is there a reason not to enable mono in P-a-s? just seen that kde4bindings does ftbfs on lpia (NCommander mentioned that)
[16:57] <NCommander> Scratch that
[16:57] <NCommander> SOmeone added lpia support a few commits back
[16:57]  * NCommander hasn't recently checked the file
[16:57] <NCommander> Someone needs to change the build-dependences on kde4bindings then
[16:58] <directhex> NCommander, they do anyway.
[16:59] <NCommander> ??
[16:59] <directhex> NCommander, kde4bindings is affected by the 2.0 transition
[16:59] <NCommander> oh yay
[17:00] <directhex> NCommander, it has no rdepends though AFAIK, so it ought to be possible to make those changes pretty much immediately, ignoring the "wait for apps to transition first" rule. once mono 2.0 lands
[17:01] <NCommander> directhex, kde4bindings are libraries :-P
[17:01] <NCommander> Its depressing though if nothing uses them
[17:01] <directhex> NCommander, the cli bindings are pretty new
[17:01] <directhex> NCommander, meebey, who as well as being the main mono packager is upstream on an irc client called smuxi, was considering playing with them to make a kde frontend as well as gtk
[17:02] <NCommander> ah cool
[17:02] <NCommander> Just keep me apprised, if you need a sponsor, ping me
[17:02] <directhex> NCommander, really though, i don't know what more i can do to keep people informed about this, other than mass-filing 90 odd bugs on packages :/
[17:03] <NCommander> The changes are non-trivial (more than changing a build-dep, and bumping the changelog)
[17:03] <NCommander> It will be slow going
[17:04] <directhex> NCommander, some packages are worse tha others. let me take a peek at kdebindings for you. not like i have much else to do at this moment in time
[17:04] <NCommander> kde4bindings :-)
[17:05] <NCommander> (kdebindings is another package ;-))
[17:05] <directhex> yes yes i know. it's kdebindings on debian
[17:05] <directhex> directhex@mortos:~$ monodis --assemblyref /usr/lib/cli/qyoto-4.3/qt-dotnet.dll | grep -B1 corlib
[17:05] <directhex> 1: Version=<IP_ADDRESS>
[17:05] <directhex> 	Name=mscorlib
[17:06] <directhex> NCommander, good news, that means there's no additional testing needed, nor any reason to delay the transition, as it's already building against clr 2.0
[17:06] <NCommander> someone just needs to attempt the merge
[17:07] <directhex> i.e. the only changes are the build-dep, and making sure it uses 'csc' instead of 'gmcs' when building
[17:07] <directhex> of course, it's blocked on mono 2.0 itself, but it means it should be a *relatively* stress-free one
[17:08] <doko> directhex: does it make sense to start with mono before we have a base kde4 built?
[17:09] <NCommander> doko, w.r.t. to KDE, a new version going up on monday, so aside from the base libraries, I'm going to wait for that to land before running around fixing stuff
[17:09] <directhex> doko, other than kde4bindings (and i don't know how important that package is), it should be pretty unrelated. all mono apps in ubuntu are gtk-based
[17:12] <directhex> doko, as long as the appropriate parties understand that kde4bindings will FTBFS until it's been transitioned, once mono 2.0 lands, then i don't want to tell people how to do their jobs nor insist they alter their workflow
[17:13] <doko> directhex: ahh, ok I'll stay out of the loop then.
[17:14] <doko> directhex: does openoffice build with mono-2.0?
[17:14] <directhex> doko, i;ll check that for you
[17:14] <doko> that would be nice
[17:15]  * NCommander wonders if OOo will explode
[17:15] <directhex> o_o
[17:16] <NCommander> :-)
[17:16] <directhex> doko, OOo looks like it'll be rather less simple than kde4bindings
[17:17] <doko> directhex: because I would like to get OOo on armel first built ... if it doesn't work with mono-2.0
[17:18] <directhex> doko, okay, looking at it, you're only attempting to build the mono bindings on [i386 amd64 ia64 lpia sparc]
[17:18] <doko> I know ...
[17:19] <directhex> doko, i can let you in on how to make it not ftbfs on other platforms, but please, it still needs to be transitioned
[17:19] <doko> but it doesn't help if the binary-indep packages cannot be built on the i386 buildd
[17:21] <directhex> doko, 's/mono-2.0-devel/mono-devel/' will fix FTBFS, but please, those libs really need to be built against the 2.0 runtime (currently it seems OOo builds three 1.0 libs, and a 2.0 lib - all four should be 2.0)
[17:22] <doko> directhex: a bug report including a patch would be fine, hint, hint ;)
[17:22] <doko> calc: ^^^
[17:22] <directhex> doko, i'll start on an apt-get source. it might be done by tomorrow
[17:27] <directhex> what build system does OOo use?
[17:34] <directhex> hm, i need a faster archive
[17:34] <directhex> oh bugger, forgot to change my mirror on this install
[17:47] <Xsss4hell> howto unbind the "Menu" key on the right side near the STRG key from gnome-terminal
[17:54] <directhex> a 100 meg diff.gz is officially insane
[17:59] <hyperair> directhex: where did you get that?
[18:03] <directhex> hyperair, OOo
[18:03] <hyperair> good grief
[18:04] <RainCT> o_O
[18:26] <madduck> so i have this 8.04 system here that can't be upgraded to 8.10
[18:27] <madduck> update-manager tells me 8.10 is available, so i click on it, see the README, click on upgrade, and then it just exits
[18:28] <madduck> it prints to the console:
[18:28] <madduck> extracting 'intrepid.tar.gz'
[18:28] <madduck> authenticate 'intrepid.tar.gz' against 'intrepid.tar.gz.gpg'
[18:28] <madduck> and then just exits
[18:30] <kirkland> madduck: possibly related to https://bugs.edge.launchpad.net/ubuntu/+bug/245219 ?
[18:31] <kirkland> madduck: ie, are you behind some sort of a proxy?
[18:31] <madduck> no, it works when I run do-release-upgrade by hand
[18:31] <madduck> i just didn't know about that.
[18:32] <madduck> yes, a transparent http proxy
[18:32] <madduck> actually, do-release upgrade does an apt-get update with hardy, not intrepid
[18:32] <madduck> aha, now it's coming int...
[18:32] <madduck> anyway, works for me now, sorry for the noise.
[18:35] <kirkland> madduck: not that this conversation has to take place now, but I'm working on merging mdadm again for ubuntu, and i'm curious if you're interested in getting this package somewhat closer to being 'in sync'
[18:36] <kirkland> madduck: i did some work to improve booting on degraded devices for intrepid, which may or may not be of interest to you
[18:43] <madduck> kirkland: absolutely. I am talking to doug kirkland @redhat too about merging
[18:44] <madduck> kirkland: i saw your work. I would love to make use of most of it, but I have not found the time to wade through the entire huge patch
[18:44] <madduck> I do want to convert mdadm to quilt soon
[18:44] <kirkland> madduck: that would be nice ;-)
[18:44] <kirkland> (quilt)
[18:44] <madduck> based on a topgit repo
[18:44] <kirkland> madduck: or git would be even better
[18:44] <madduck> don't you have to use launchpad?
[18:45] <kirkland> madduck: i'm happy to help work through the diff with you at some point
[18:45] <madduck> kirkland: if i added quilt to mdadm post-lenny, would you be prepared to split the changes into quilt patches?
[18:45] <kirkland> madduck: when's "post-lenny"?
[18:45] <madduck> kirkland: when it's ready. ;)
[18:46] <kirkland> madduck: (trick question)  :-)
[18:46] <madduck> kirkland: I am happy to do so earlier if I find the time, targetting experimental
[18:46] <kirkland> madduck: sure, i think quilt would be a big improvement
[18:46] <madduck> It shouldn't even be a lot of work, but it is still time that's needed
[18:46] <madduck> and i am about 160% loaded these days
[18:47] <kirkland> madduck: i'm certainly most familiar with the boot-degraded changes;  i'd have to do some research about the rest of the changes ubuntu carries on mdadm
[18:47] <kirkland> madduck: understood.
[18:47] <kirkland> madduck: i got a little burnt out with users complaining about RAID 24x7, so i was happy to step away from RAID for a little while :-)
[18:47] <madduck> kirkland: would you send me an email to<EMAIL_ADDRESS>so I get your details?
[18:47] <kirkland> madduck: you bet.
[18:48] <kirkland> madduck: i'm happy to work through Debian BTS, but looking at the size of the mdadm debian/ubuntu diff, it might take a few irc conversations to peel through everything
[18:48] <madduck> sweet. maybe i can find the time to give you an update on the cooperation with doug and maybe some time, ubuntu, fedora, redhat, and debian will all build their mdadm packages from the same repo.
[18:48] <kirkland> madduck: remarkable ... Red Hat has a "Doug Kirkland" working on RAID?
[18:48] <madduck> kirkland: yeah, and as I said, I am very pressed for time up until around May.
[18:48] <kirkland> madduck: and Canonical has a "Dustin Kirkland"  :-)
[18:49] <madduck> no,
[18:49] <madduck> Ledford
[18:49] <kirkland> madduck: fair enough
[18:49] <madduck> Doug Ledford
[18:49] <kirkland> ah
 kirkland: absolutely. I am talking to doug kirkland @redhat too about merging
[18:49] <madduck> freudian slip i know
[18:49] <kirkland> ;-)
[18:49] <madduck> do you read pkg-mdadm-devel?
[18:50] <kirkland> madduck: i haven't, to date.  i certainly can subscribe.
[18:50] <madduck> well, might be useful if you track mdadm for Ubuntu...
[18:51] <madduck> there's also pkg-mdadm-commits
[18:52] <kirkland> madduck: well, i haven't been really "tracking mdadm for Ubuntu" ...  but I did decide to fix booting degraded RAID for Ubuntu, which put me deep into mdadm, initramfstools, and grub
[18:52] <madduck> lovely world, ey?
[18:52] <madduck> in a sentence or less, what is booting degraded RAID?
[18:52] <kirkland> madduck: and i have a priority of trying to simplify the mdadm diff betwix debian/ubuntu, per request by jcastro
[18:52] <madduck> i mean, mdadm on Debian can boot degraded raids, no?
[18:53] <madduck> kirkland: awesome. hug jcastro from me. now it seems like i owe him another beer. :)
[18:53] <kirkland> madduck: i'm not sure ... this might be a result of Debian/Ubuntu forkage
[18:53] <kirkland> madduck: he's been on us about syncing back up, in a good way ;-)
[18:53] <madduck> that's great news.
[18:53] <madduck> you do know about http://vcs-pkg.org, yes?
[18:54] <kirkland> madduck: so when a RAID becomes degraded (loses a disk) in Ubuntu, on the next boot, the mdadm --assemble with be tried a number of times (3 minutes in Hardy, 30 seconds in Intrepid), waiting for all the disks to spin up
[18:54] <kirkland> madduck: in Hardy, when that timer expires, if disks are missing, the user gets dropped to an initramfs shell
[18:55] <kirkland> madduck: the work i've done in Intrepid (and backported to hardy) includes:
[18:55] <kirkland> madduck: a debconf question "Do you want to boot if your RAID becomes degraded?"  (more or less the question)
[18:55] <madduck> damnit, i have to help my mother. i'll be back later to read this, ok? sorry about that. keep writing.
[18:55] <kirkland> madduck: (sorry, not less than 1 sentence --  not possible :-)
[18:56] <kirkland> madduck: the answer to that question is written to a file in /etc/initramfs-tools/conf.d/mdadm, which get's added to the initramfs
[18:57] <kirkland> madduck: and in the initramfs, if the wait for all disks to spin up expires, the BOOT_DEGRADED value is read from file
[18:57] <kirkland> madduck: if it's "true" or "yes" or whatever, the system RAID is assembled in degraded mode, and the system boots
[18:58] <kirkland> madduck: if it's "false" or "no" or undefined, a message will be displayed, informing the user that a new RAID degrade event has been detected; do you want to boot on a degraded RAID [y/N]:
[18:59] <kirkland> madduck: after 15s, "N" is assumed, and the system drops to an initramfs (busybox) shell, which is the legacy ubuntu behavior
[18:59] <kirkland> madduck: dpkg-reconfigure mdadm can be used to change the value of your BOOT_DEGRADED selection
[19:00] <kirkland> madduck: and we've added that debconf question to the debian-installer/partman if you're installing onto a RAID
[19:00] <kirkland> madduck: beyond that, i also made some changes to grub (and grub-installer), to write the bootloader to each disk in an array
[19:03] <kirkland> madduck: perhaps the most "compressed" patches for this functionality are the ones attached to https://bugs.edge.launchpad.net/ubuntu/+source/mdadm/+bug/290885
[19:03] <kirkland> madduck: that was the "backport" of the functionality, as contained as possible, to Hardy
[19:04] <kirkland> madduck: the mdadm portion is http://launchpadlibrarian.net/19438493/mdadm.290885.debdiff
[19:04] <kirkland> madduck: most of which is PO/translation noise
[19:07] <kirkland> madduck: pruning out the i18n distractions, the functional patch looks more like this: http://pastebin.ubuntu.com/75724/
[19:10] <kirkland> madduck: that patch is dependent on an initramfs-tools patch, http://launchpadlibrarian.net/19438280/initramfs-tools.290885.debdiff , which provides a "mount root failure" framework whereby hooks can be defined and executed
[19:18] <kirkland> madduck: all in all, udev will likely be the biggest hurdle
[19:39] <directhex> calc, ping
[20:14] <calc> directhex: hi
[20:14] <calc> directhex: whats up?
[20:14] <directhex> calc, i wanted to ask when debian/control is rebuild on OOo
[20:14] <directhex> seems it's when i hoped, so only debian/rules needs patching
[20:14] <directhex> which means.....
[20:14] <directhex> directhex@mortos:/tmp$ diffstat openoffice.org-2.4.1_mono2.0transition.diff
[20:14] <directhex>  rules |    7 +++----
[20:14] <directhex>  1 file changed, 3 insertions(+), 4 deletions(-)
[20:15] <directhex> in THEORY that's correct & valid
[20:15] <calc> debian/control gets rebuilt when you run debian/rules control
[20:16] <calc> ok
[20:16] <calc> yea i uploaded a new version of OOo 3.0 to the ppa last night waiting on doko to do some testing
[20:16] <calc> i'm on vacation/holiday all next week
[20:16] <directhex> calc, well, i hope this section of debian/rules hasn't changed in 3.0 :/
[20:16] <calc> but i could do a new upload if needed
[20:16] <calc> directhex: if it has it should be simple enough for me to port
[20:17] <calc> directhex: you can email it to me at<EMAIL_ADDRESS>[20:17] <directhex> calc, yeah, i reckon you can handle things like
[20:17] <directhex> -MONO_MINVER= (>= 1.2.3)
[20:17] <directhex> +MONO_MINVER= (>= 2.0)
[20:17] <calc> yea :)
[20:19] <directhex> calc, OOo appears to have the build system from hell, but underneath it all, it smells like autofoo. and the transition with autofoo is pretty simple as long as you know the AC_PATH_PROGs to override
[20:20] <calc> oh
[20:20] <calc> yea OOo is very confusing in that it has two different configures
[20:21] <directhex> no, OOo is confusing as it seems to have three different patches for adding mono to the build
[20:21] <directhex> mono-build.diff, mono-build-m14.diff, mono-build-m15.diff
[20:22] <calc> oh heh, yea it has many different confusing bits :\
[20:22] <calc> there are no apparent mono patches for 3.0 not sure if they were integrated or not
[20:23] <calc> at least none named *mono* under ooo-build/patches/dev300/
[20:23] <directhex> calc, anyway, i'll mail you this patch, but please be aware that i've neither tested it (partly because i don't like mucking with 'pristine' pbuilders, partly because i only just wrote it and don't have the 600ghz needed to have been able to test it by now), and it can't be applied until mono 2 is in jaunty
[20:23] <calc> directhex: ok no problem
[20:24] <directhex> calc, i want to keep my transition wiki page updated. shall i assign OOo to you or me on it, to show that work is being done?
[20:25] <calc> leave it as yourself but i will look into as i get time, i will be on vacation most of the rest of the year though (other than during UDS)
[20:25] <directhex> calc, who else should i speak to r.e. OOo/mono issues (or who should be speaking to me?)
[20:26] <calc> i think there is a week after UDS that i will be around, so i could look at it then if i am not too slammed with other work
[20:26] <calc> directhex: maybe doko, but he will probably be away a lot as well
[21:16] <NCommander> Can a core developer give-back k3b on armel
[21:17] <directhex> evenin' NCommander!
[21:17] <NCommander> evening
[21:17]  * NCommander preparing for his company's turkey party
[21:18] <directhex> yay, turkey
[21:22] <NCommander> Free boozie
[21:23]  * NCommander is going to discover if balmer's peak exists
[21:24] <geser> do I resolve this correctly to http://xkcd.com/323/?
[21:48] <RainCT> awalton__: oh, hi :)
[21:51] <RainCT> awalton__: wouldn't it be better if your patch (nautilus scripts) also looked for deleted and modified files?
[21:51] <directhex> geser, yes, you do
[22:00] <ianm_> anyone know of software for head tracking using a laptop camera?
[22:01] <RainCT> ianm_: me not, but tell me if you find out ;P
[22:07] <ianm_> RainCT: oh you'll hear about it... you already package my screenruler app ;)
[22:09] <ianm_> opencv!
[22:10] <RainCT> :)
[22:12]  * directhex wonders who's about this evening
[22:14]  * RainCT is to stupid to parse directhex's sentence :P
[22:15] <Mithrandir> yo, directhex
[22:16] <directhex> Mithrandir! long time, no see. man, how long is it since i loitered in #debian-amd64?
[22:17] <Mithrandir> long enough I have to look at another machine's irc logs. :-P
[22:17] <Mithrandir> how's life?
[22:18] <directhex> good, good! looking after a LOT of kit these days
[22:18] <directhex> working on mono packaging in my spare time, it seems
[22:18] <Mithrandir> yeah, I've noticed you asking about bits and pieces
[22:18] <Mithrandir> kit> any fun, or just much of it?
[22:20] <directhex> Mithrandir, ehm... a 128-box xeon cluster, a 128-box opteron cluster, a new 66-blade SGI cluster, and a 256-core itanium SGI box
[22:20] <cjwatson> NCommander: k3b given back
[22:21] <cjwatson> directhex: ok, so what needs to go first?
[22:21] <cjwatson> directhex: mono itself?
[22:22] <Mithrandir> directhex: wow.
[22:22] <directhex> cjwatson, yes, that's the important one
[22:22] <cjwatson> directhex: is http://launchpadlibrarian.net/19799395/mono_2.0.1.orig.tar.gz definitely bitwise-identical to what will end up in Debian?
[22:22] <directhex> ah. hm. let me triple-check that
[22:24] <NCommander> hey cjwatson
[22:24] <NCommander> cjwatson, I dunno if you caught the conversation between me and doko, but I'm going to hold off any more KDE-core FTBFS fixes until Monday when Beta 1 gets uploaded
[22:24] <NCommander> *KDE4
[22:24]  * RainCT feels ignored by directhex *g*
[22:25] <directhex> RainCT, sorry
[22:26] <cjwatson> NCommander: yeah, I saw, thanks
[22:26] <RainCT> directhex: heh just joking ;)
[22:28] <directhex> cjwatson, it seems not. shite. hold on...
[22:33] <ianm_> RainCT or others, is it hard to make a PPA .deb of a C app that uses a version of the liblo library that isn't in the repos yet? (0.25)
[22:33] <Mithrandir> ianm_: it requires the liblo package to be uploaded to the PPA too
[22:34] <ianm_> Mithrandir: would that interfere with enduser systems at all?
[22:34] <Mithrandir> ianm_: the newer version would obviously be installed on the user's system.
[22:34] <Mithrandir> assuming it works fine, that's not a problem
[22:35] <ianm_> two versions of the same library installed is ok?
[22:37] <Mithrandir> if the soname is different, yes.
[22:38] <cjwatson> directhex: there's at least one Ubuntu change missing here
[22:38] <cjwatson> +     + libmono-mozilla0.2-cil: Drop libgluezilla to Suggests, it is in universe
[22:38] <cjwatson> +       and pulls in the old xulrunner.
[22:39] <ianm_> RainCT: there's also this http://code.google.com/p/ehci/
[22:39] <directhex> cjwatson, gluezilla no longer needs xul 1.8. i'll file a MIR
[22:40] <cjwatson> ah yes, so it doesn't
[22:41] <cjwatson> directhex: what about the doc directory symlinking?
[22:42] <directhex> cjwatson, the patch for it is badly written and will never be accepted in debian. given the multi-meg savings elsewhere, i don't see it as a good reason to merge instead of syncing, for the sake of tens of k
[22:45] <cjwatson> I think it was more like 1.8MB, as it happens, though less compressed
[22:46] <cjwatson> but I'm OK with that rationale given that the number of binary packages is shrinking (isn't it?)
[22:47] <directhex> the number produced is *increasing*. the number needed for tomboy/f-spot is decreasing by about 50%
[22:47] <cjwatson> oh, hmm
[22:48] <cjwatson> I suppose it's more the latter we care about
[22:49] <cjwatson> as written the patch goes to more work than it needs to, certainly (I think it came from an implementation in cdbs); I would suggest that you should consider the idea (not necessarily the specific implementation) in Debian anyway, since symlinking documentation directories to a common base package is a perfectly reasonable thing to do there too
[22:50] <directhex> yes, i'll add it to the TODO
[22:50] <RainCT> ianm_: thanks :)
[22:50] <cjwatson> directhex: ta
[22:51] <RainCT> ianm_: btw, have you tried out touchlib/tbeta?
[22:56] <directhex> cjwatson, i don't think me or meebey realised the little issue w/ gzip reproducibility. i'm asking him to upload a copy of what will be uploaded to debian.
[22:56] <cjwatson> oh, upstream only releases bz2, I see
[22:56] <cjwatson> ok
[22:58] <directhex> i wonder if the debian archive will properly handle bz2 any time soon
[22:58] <cjwatson> should do with dpkg-source v3
[22:59] <cjwatson> iirc, anyway
[23:00] <NCommander> directhex, Debian has handled bzr2 for ages
[23:01] <NCommander> I think they even handle lzma
[23:01] <directhex> NCommander, *all* of it? iirc some of the toolchain has gaps
[23:01] <cjwatson> NCommander: not as orig.tar compression methods
[23:01] <cjwatson> which is the matter at hand
[23:02] <NCommander> I was fairly sure this feature was properly implemented
[23:02] <NCommander> If not, well, I have a dak installation + source
[23:02]  * NCommander queues the evil laugh
[23:03] <cjwatson> it's rather easy to verify that it is not supported by Debian; you could for example search for files ending with .orig.tar.bz2 in a Debian mirror ...
[23:04] <NCommander> my mistake
[23:04] <NCommander> I was sure it was supported though :-/
[23:04] <cjwatson> http://liorkaplan.wordpress.com/2008/01/31/origtarbz2-packages-in-debian/
[23:04] <ianm_> RainCT: not yet
[23:06] <NCommander> cjwatson, I thought I already admitted they are not supported ;-)
[23:07] <cjwatson> just some verification
[23:08] <directhex> cjwatson, shall i upload the new orig to the LP bug? wait, i need to re-do the dsc too don't i
[23:08] <cjwatson> directhex: don't worry about the dsc
[23:08] <cjwatson> directhex: either upload it there or give me a URL
[23:08] <directhex> http://www.meebey.net/temp/debian/mono_2.0.1.orig.tar.gz
[23:09] <cjwatson> grabbing
[23:13] <RainCT> ianm_: do you know if there's some .deb with OpenCV 1.1?
[23:14] <ianm_> RainCT: nope.  I got the same "Requested 'opencv >= 1.1.0' but version of OpenCV is 1.0.0"
[23:14]  * RainCT sighs and installs CVS
[23:15] <cjwatson> directhex: hmm, does this have stuff stripped out of the tarball as well as simply changing the compression type?
[23:15] <directhex> cjwatson, no, not anymore. the +dfsg was previously due to some non-dfsg-free licenses on some code (a CC license, i forget which). it was relicensed to expat at meebey's request
[23:16] <cjwatson> directhex: meebey seems to have repacked the tar as well, though
[23:16] <cjwatson> which seems a bit gratuitous?
[23:16] <directhex> yes, i've told him off about that. he'll be using bunzip2 | gzip in future
[23:17] <cjwatson> ok
[23:17] <directhex> apparently it never used to be an issue, which is technically true...
[23:18] <cjwatson> it's not an issue as such, it just makes it more effort to independently verify the status of divergence from upstream
[23:19] <directhex> if there's no +dfsg on it, assume it's just a workflow glitch by meebey
[23:20] <cjwatson> "independently verify" ;-)
[23:20] <cjwatson> (I've already checked myself
[23:20] <cjwatson> )
[23:32] <madduck> kirkland: why would a user not want to assemble a degraded array?
[23:33] <madduck> anyway i need to sleep. we'll talk again, thanks for the explanation! :)
[23:37] <cjwatson> directhex: mono uploaded
[23:37] <cjwatson> directhex: what else can/should be done in the first stage before that builds?
[23:38] <cjwatson> directhex: libgdiplus?
[23:38] <directhex> cjwatson, yes, please sync it
[23:38] <directhex> cjwatson, i know it's possible to use mismatched versions of some packages like libgdiplus, but i don't know if there are side-effects
[23:39] <cjwatson> directhex: do you want to keep bug 300133 open to track this, or shall I close it?
[23:39] <directhex> cjwatson, close it - i'm tracking it on wiki.debian.org, and i don't want to crapflood people who aren't me by tracking 90 packages from one bug
[23:40] <cjwatson> ok
[23:40] <directhex> cjwatson, thanks very much for your help
[23:41] <cjwatson> directhex: done
[23:42] <cjwatson> directhex: xsp/mod-mono/mono-debugger now or later?
[23:42] <directhex> cjwatson, is dep-wait a problem in the real archive?
[23:42] <cjwatson> in what sense?
[23:43] <directhex> xsp can't build until 2.0 is there, i was under the impression uploading unbuildable source was frowned upon in debianland
[23:43] <cjwatson> I'm not aware of that being a problem for either Debian or Ubuntu
[23:44] <directhex> really? perhaps i'm just paranoid then
[23:44] <cjwatson> not a problem in Debian at any rate
[23:44] <cjwatson> err
[23:44] <cjwatson> not a problem in UBUNTU at any rate
[23:44] <cjwatson> brains
[23:45] <cjwatson> directhex: same question for the .orig.tar.gz files in those three bugs, then
[23:45] <directhex> cjwatson, i've asked meebey to grab them and use them as his own
[23:45] <cjwatson> directhex: has he said yes? just want to avoid sync problems in the future
[23:46] <directhex> i'm double-checking
[23:47] <cjwatson> directhex: I think I need to go to bed though, maybe I should stop here and resume tomorrow
[23:47] <directhex> cjwatson, understood. i'll try and get monodoc ready by then - didn't get a chance tonight


[06:50] <dholbach> good morning
[08:50] <RawChid> Good morning. The tutorial about the wikipedia lense was useful! I think it is an easy tutorial to get familiar with programming lenses!
[08:51] <RawChid> GTK+ 3, PyGI, and GSettings. See.....
[08:51] <RawChid> dholbach: dpm ^^
[08:51] <RawChid> Only one thing. Maybe you already know this, but I get the following warning: WARNING: Your project is out of date.  Newly created projects use
[08:51] <RawChid> GTK+ 3, PyGI, and GSettings. See.....
[08:52] <RawChid> Just FYI
[08:52] <RawChid> Goodbye
[08:52] <dpm> RawChid, awesome!
[08:52] <dpm> I'd suggest filing a bug against quickly for that issue
[08:52] <dpm> you can just type 'ubuntu-bug quickly'
[08:53] <RawChid> Have to go now, but will definitly do it later.
[08:54] <RawChid> BTW, I mailed you before dpm. Are you very busy atm?
[08:54] <RawChid> I understand there something to release today which has highest prio ;)
[08:54] <dpm> :-)
[08:55] <dpm> RawChid, I know, sorry for not having replied. I'll try go get back to you tomorrow.
[08:55] <RawChid> Take your time
[08:55] <RawChid> Now I at least know that it will be processed...
[08:56] <RawChid> Good luck today and bye!
[08:57] <dpm> RawChid, it will, I did have a look at the merge proposal, and I'm happy with the overall changes except for one part, which is why I did not merge it straight away
[09:07] <dholbach> RawChid, good work :)


[15:59] <bdmurray> o/
[15:59] <ginggs> o/
[15:59] <dbungert> o/
[16:00] <jawn-smith> o/
[16:00] <bdmurray> #startmeeting Weekly Ubuntu Foundations team
[16:00] <meetingology> Meeting started at 16:00:07 UTC.  The chair is bdmurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[16:00] <meetingology> Available commands: action, commands, idea, info, link, nick
[16:00] <slyon> o/
[16:00] <bdmurray> #topic Lightning Round
[16:00]  * bdmurray shuffles cards
[16:00] <bdmurray> ginggs mwhudson doko juliank jawn-smith dbungert sil2100 ogayot slyon schopin waveform xypron bdmurray alexghiti vorlon
[16:00] <bdmurray> ginggs: first for the year!
[16:01] <ginggs> * Happy New Year!
[16:01] <ginggs> * +1 rotation this week; retrying builds, helping along transitions
[16:01] <ginggs> * uncovered some LTO issues
[16:01] <ginggs> * in-between, I sponsored an opensbi sync for xypron (LP: #1956362)
[16:01] <ginggs> * and sponsored an upload of libzpc for fheimes (LP: #1932522)
[16:01] <ginggs> (done)
[16:01] <bdmurray> skipping doko for now
[16:02] <bdmurray> juliank:
[16:02] <juliank> * Investigated ufw <-> cloud-init ordering cycle further
[16:02] <juliank> * grub riscv64 discussion with xypron
[16:02] <juliank> * Raised issues about ESM Apps messaging to the right people
[16:02] <juliank> * Reviewed some APT merge requests
[16:02] <juliank> * Trying to understand the signing policies and keys for secure boot
[16:02] <juliank> * Asked bdmurray to hint command-not-found/focal
[16:02] <juliank> * Reading up on usrmerge on Debian - hint: it's too early to move files from / to /usr before bookworm is released
[16:02] <juliank> (done)
[16:02] <jawn-smith> * A few more RISC-V summit follow ups
[16:02] <jawn-smith> * Experimenting with Adafruit GPS hat on Ubuntu
[16:02] <jawn-smith>     * Can successfully read raw data off of /dev/<serial-device>
[16:02] <jawn-smith>     * Adafruit's python library relies on RPi.GPIO
[16:02] <jawn-smith>     * We discovered an incompatibility with RPi.GPIO and gcc-10 and waveform to contact upstream
[16:02] <jawn-smith> * LP: #1955017 discussing with snapd team and identifying minimal snapd change needed to resolve the issue
[16:02] <jawn-smith> * Reviewing ubuntu-image classic redesign spec, adding comments/questions
[16:02] <jawn-smith> * Investigating livecd-rootfs autopkgtest failures.
[16:02] <jawn-smith> [done]
[16:02] <dbungert> * libcrypt-openssl-pkcs10-perl - my previous 'PASS' sid tests were invalid and
[16:02] <dbungert> based on openssl-1.1.  Removed (LP: #1955082)
[16:02] <dbungert> * curtin vs rockylinux - previous submitter came back, things get farther but a
[16:02] <dbungert> new issue was found.  Add rockylinux to the distro list, as other curtin code
[16:02] <dbungert> does need this. (LP: #1955671)  Asking submitter to help test before merge.
[16:02] <dbungert> * curtin vs uefi arm64 - Relax EFI check to be more robust to kernel changes.
[16:02] <dbungert> https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/413644
[16:02] <dbungert> * curtin build deb - the build-deb tool was not easy to use for arbitrary
[16:02] <dbungert> people to upload deb snapshots.  Use dch instead of sed-ing, and other fixes.
[16:02] <dbungert> https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/413637
[16:02] <dbungert> * subiquity vs cloud-init - file LP:#1956539 based on user feedback that
[16:02] <dbungert> cloud-init, as used by subiquity, reset some values back to previous config.
[16:02] <dbungert> We're working w/ cloud-init crew to ensure subiquity usage is correct.
[16:02] <dbungert> (done)
[16:03] <bdmurray> let's have doko go now
[16:03] <doko>  - during the EOY break: retry builds for the test rebuilds
[16:03] <doko>  - dpkg merge
[16:03] <bdmurray> as sil_2100 is out
[16:03] <doko>  - binutils trunk uploaded to jammy
[16:03] <doko>  - gcc-12 update
[16:03] <doko>  - archive test rebuilds almost finished, results pending
[16:03] <doko> (done)
[16:03] <bdmurray> ogayot:
[16:03] <ogayot> * subiquity
[16:03] <ogayot>   * added autoinstall support for Ubuntu Advantage
[16:03] <ogayot>   * reworked PR for checking Ubuntu Advantage token using ua client
[16:03] <ogayot>   * opened PR to fix incorrect integration test
[16:03] <ogayot>   * reviewed simple changes in subiquity / curtin
[16:04] <ogayot>   * implemented subiquity side support for APT preferences
[16:04] <ogayot>   * currently working on curtin side implementaion for APT preferences
[16:04] <ogayot> * proposed migration for libconfig-model-dpkg-perl -> checked with help from slyon. Should be fixed with MIR for libset-intspan-perl
[16:04] <ogayot> done
[16:04] <slyon> - GlusterFS MIR review, LP: #1950321
[16:04] <slyon> - finalized systemd SRU verification (Bionic/Focal/Impish)
[16:04] <slyon> - cont. work on systemd-oomd enablement in Debian:
[16:04] <slyon>   https://salsa.debian.org/systemd-team/systemd/-/merge_requests/133
[16:04] <slyon> - sync'ed klibc to drop the Ubuntu delta, applied upstream
[16:04] <slyon> - some coordination around dbus timeout, LP: #1871538
[16:04] <slyon> - proposed-migration
[16:04] <slyon>   + pygments vs python-django-extensions
[16:04] <slyon>   + pygments vs djangorestframework, LP: #1955134
[16:04] <slyon>   + systemd vs linux 5.15
[16:04] <slyon> [16:04] <slyon> - Merged https://github.com/canonical/netplan/pull/247
[16:04] <slyon> - Finished https://github.com/canonical/netplan/pull/248, in review
[16:04] <slyon> - Reviewed https://github.com/canonical/netplan/pull/241
[16:04] <slyon> - Reviewed https://github.com/canonical/netplan/pull/249
[16:04] <slyon> (done)
[16:04] <bdmurray> schopin:
[16:04] <schopin> * netplan:
[16:04] <schopin>   + Worked on the YAML consolidation feature, splitting the branch into multiple smaller PRs:
[16:04] <schopin>     - low hanging fruits: https://github.com/canonical/netplan/pull/241
[16:04] <schopin>     - prelude: OVS handing changes: https://github.com/canonical/netplan/pull/249
[16:04] <schopin>     - prelude: Python bindings: https://github.com/canonical/netplan/pull/250
[16:04] <schopin>     - New YAML generation API: https://github.com/canonical/netplan/pull/251
[16:04] <schopin>     - Port `netplan get` away from PyYAML: https://github.com/canonical/netplan/pull/252
[16:04] <schopin>   + PR reviews for slyon (still ongoing):
[16:04] <schopin>     - https://github.com/canonical/netplan/pull/248
[16:04] <schopin>     - https://github.com/canonical/netplan/pull/247
[16:05] <schopin> * openssl: reviewed a python-cryptography patch to fix the build against 3.0.1
[16:05] <schopin> * lintian: (ongoing) writing a MIR for libio-tiny-perl
[16:05] <schopin> ✓ done
[16:05] <bdmurray> waveform:
[16:05] <waveform> * Short week (wading through email from xmas break!)
[16:05] <waveform> * Investigated snaps on raspios (following reports on IRC); kernel needs LZ4 support for newer snaps (needs further investigation to see if that's all that's required)
[16:05] <waveform> * Investigating reports of wifi failure (outdated firmware?) on UC18
[16:05] <waveform> * Working on adding tests to raqm for MIR (LP: #1951069)
[16:05] <waveform> * Pi meetings
[16:05] <waveform> (done)
[16:05] <bdmurray> xypron:
[16:06] <xypron> Working on enable RISC-V in GRUB LP #1876620
[16:06] <xypron> Currently I am testing on different architectures.
[16:06] <xypron> Create a Sync request for OpenSBI #
[16:06] <xypron> <done />
[16:06] <bdmurray> cleaned up offical Ubuntu bug tags
[16:06] <bdmurray> merged, uploaded anacron
[16:06] <bdmurray> sync'ed pycountry
[16:06] <bdmurray> tried to install Ubuntu on my new laptop
[16:06] <bdmurray> reported LP: #1956386 regarding Bitlocker detection
[16:06] <bdmurray> candidate application review
[16:06] <bdmurray> uploaded debian-goodies so popularity-contest can be demoted
[16:06] <bdmurray> sponsored gvfs SRU for LP: #1927100
[16:06] <bdmurray> overrode a command-not-found phasing crash
[16:06] <bdmurray> uploaded ubuntu-release-upgrader fixing LP: #1955843
[16:06] <bdmurray> alexghiti:
[16:06] <alexghiti> LP #1956440: proposed a bumped version to Debian maintainers
[16:06] <alexghiti> Packaged starfive-u-boot
[16:06] <alexghiti> Adding support for the BeagleV to livecd-rootfs
[16:06] <alexghiti> Bumping linux riscv to 5.16 to have a single kernel for BeagleV, Nezha and Unmatched.
[16:06] <alexghiti> (done)
[16:07] <bdmurray> actually bug 1956385 is the one I reported
[16:07] <bdmurray> Steve is also out
[16:07] <bdmurray> Any questions on status?
[16:08] <bdmurray> waveform: what is raqm?
[16:08] <waveform> bdmurray, it's a new dependency of Pillow (née PIL, the Python Imaging Library) which supports advanced text layouts
[16:08] <bdmurray> Okay! Any other questions?
[16:10] <bdmurray> #topic Release Incoming Bugs
[16:10] <bdmurray> We've a fair bit to go through today but might also save some for next week when we have steve and sil_2100
[16:10] <bdmurray> bug 1840122
[16:11] <bdmurray> Oh this is paride's finalrd ordering change
[16:12] <bdmurray> I'll work on that today
[16:12] <paride> hey, thanks!
[16:12] <bdmurray> It seems safe and I don't think we should wait another week
[16:12] <bdmurray> bug 1842047 is something the community team brought up a bit ago
[16:13] <bdmurray> It's surely still important so let's card it and I'll follow up with them just to confirm
[16:13] <bdmurray> bug 1951519 (that's a lot of repeating digits)
[16:14] <mclemenceau> bdmurray: the slideshow one is already carded I believe
[16:14] <bdmurray> mclemenceau: oh, it is indeed
[16:15] <bdmurray> the build failure should be carded and set to be fixed for the 20.04.4 point release
[16:15] <mclemenceau> ok
[16:15] <bdmurray> bug 1955084
[16:16] <bdmurray> let's leave that for when steve gets back
[16:16] <bdmurray> and let's not select tasksel this week ;-)
[16:16] <bdmurray> bug 1952947
[16:17] <bdmurray> This has come up more than once and would fixing it would keep the bug reporting story at the same standard
[16:17] <bdmurray> So I think we should fix it but am open to second opinions on the priority of it
[16:18] <bdmurray> Okay, well lets leave that in the queue for now too
[16:18] <schopin> anyone *knows* how to fix it?
[16:19] <bdmurray> Maybe the desktop team could help give guidance?
[16:19] <bdmurray> bug 1955109
[16:20] <bdmurray> juliank: has anything come of the mailing list discussion?
[16:21] <juliank> bdmurray: os-prober?
[16:21] <bdmurray> Yes
[16:22] <juliank> We came up with a plan to enable os-prober if enabled during install, basically
[16:22] <juliank> Have not implemented it _yet_
[16:22] <juliank> (or simpler, if there is os-prober entries in grub.cfg, or no grub.cfg, keep generating them)
[16:22] <bdmurray> Okay, so let's card that bug or link to it from the existing card so that we remember to changelog close that bug.
[16:22] <bdmurray> Is there an existing card?
[16:22] <juliank> There's no card for this yet
[16:23] <bdmurray> Okay, the next two in the JJ list are tasks of bugs we've already discussed
[16:24] <bdmurray> so #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ii-incoming-bug-tasks.html
[16:24] <bdmurray> bug 1956385
[16:25] <dbungert> I think we should card that
[16:25] <bdmurray> This is one I reported and I still haven't installed Ubuntu on that system yet. I saw somebody say turn bitlocker on and off and then you'll be able to install.
[16:25] <bdmurray> I'm happy to try that but don't want to lose any relevant information for fixign this.
[16:25] <bdmurray> I guess I should try jammy too but I'd be surprised.
[16:26] <bdmurray> But let's card it.
[16:26] <dbungert> done
[16:27] <bdmurray> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[16:27] <bdmurray> Oh that's the same failure to build bug
[16:27] <bdmurray> #topic Team proposed-migration report
[16:28] <bdmurray> doko:
[16:28] <bdmurray> #link https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[16:28] <doko> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html
[16:29] <doko> python-crypto: mine, needs removal
[16:29] <doko> lintian/lintian-brush
[16:29] <doko> didn't we volunteer somebody to write a MIR? lintian/amd64 in main cannot depend on libio-prompt-tiny-perl in universe
[16:29] <schopin> o/
[16:30] <schopin> the MIR is almost written.
[16:31] <doko> pillow: needs a MIR?
[16:31] <waveform> that's mine
[16:31] <doko> lemonldap-ng: schopin?
[16:31] <schopin> briefly looked into it, seems fixable but haven't time to actually do it.
[16:32] <schopin> (PEM format changed a bit in openssl 3)
[16:32] <doko> autofs: looks like server is looking at this
[16:32] <doko> pygments/ruby-pygments.rb: ?
[16:32] <alexghiti> I proposed a new version to Debian
[16:32] <alexghiti> that fixes the issues encountered
[16:33] <slyon> see bug #1956440
[16:33] <doko> let me look at python3.10/setuptools
[16:33] <bdmurray> Do update-excuses bugs not show up on this report?
[16:33] <doko> they should
[16:33] <doko> slyon, can you follow up on this?
[16:34] <bdmurray> alexghiti: Is there a Launchpad bug about pygments / ruby-pygments
[16:34] <doko> livecd-rootfs: ?
[16:34] <slyon> I think the update-excuse bug needs to affect the "parent" package (pygments in this case).. but the bug is with ruby-pygments.rb
[16:34] <jawn-smith> o/
[16:34] <jawn-smith> livecd-rootfs is another issue with mountpoints behaving differently in the autopkgtest environment than they do in local builds
[16:34] <jawn-smith> I'm looking into it
[16:34] <doko> ta
[16:34] <alexghiti> Yes slyon gave it above: #1956440
[16:35] <doko> openssl: schopin: did you look at these, or should I have a look?
[16:36] <doko> libstring-copyright-perl/amd64 in main cannot depend on libset-intspan-perl: another MIR needed
[16:36] <schopin> haven't looked at python yet.
[16:36] <ogayot> I can do the MIR for this
[16:36] <schopin> (-cryptography should be fixed)
[16:36] <ogayot> I created #1956444
[16:36] <doko> ta
[16:37] <schopin> doko: help welcome for the python3.* packages
[16:37] <doko> lapack/octave: ?
[16:37] <ginggs> i'll take it
[16:37] <doko> e2fs/freedombox: ?
[16:37] <slyon> i'll investigate that
[16:38] <doko> sqlite3: ?
[16:38] <dbungert> I can take sqlite3
[16:38] <doko> python-click: ?
[16:38] <ginggs> is that still mwhudson's?
[16:38] <bdmurray> Didn't that need a new mailman?
[16:39] <bdmurray> That sounds familiar
[16:39] <doko> ok, leaving this with him
[16:39] <doko> fwupd: did we start a protobuf transition?
[16:40] <doko> no
[16:41] <doko> I'll look at it later
[16:41] <doko> systemd: ?
[16:41] <doko> curl: ftbfs ... ?
[16:41] <slyon> systemd is on me, currently investigating
[16:42] <doko> ubuntu-release-upgrader / update-manager?
[16:42] <slyon> (or actually testing a fix)
[16:42] <bdmurray> there were some LP network failures which caused the u-r-u issue
[16:42] <bdmurray> maybe the same with curl?
[16:42] <bdmurray> I'll have a look at curl
[16:42] <ginggs> i just gave back the build of curl / amd64, it failed without a log
[16:42] <bdmurray> Man, that was gonna be my easy win
[16:43] <ginggs> :D
[16:43] <doko> anything later was uploaded today, that's it
[16:43] <bdmurray> Okay, thanks doko!
[16:43] <bdmurray> #topic AOB
[16:44] <bdmurray> Okay, thanks everybody.
[16:44] <bdmurray> #endmeeting
[16:44] <meetingology> Meeting ended at 16:44:30 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-01-06-16.00.moin.txt
[16:48] <Kilos> Thank you for all your hard work guys
[16:49] <nicoz-> :)
[19:12] <Carlin0> o/
[19:12] <Kilos> o/
[19:12] <Mr_Pan> uh  ?
[19:13] <Kilos> waves
[19:13] <nicoz-> one hour to go
[19:13] <nicoz-> 45 minutes and we leave
[19:13] <nicoz-> :P
[19:14] <Mr_Pan> keep calm
[19:14] <Kilos> can we leave now I am falling asleep
[19:15] <Kilos> hi genii
[19:15] <nicoz-> could you be seriuos
[19:15] <nicoz-> :P
[19:16] <nicoz-> I’ll be back in a few minutes
[19:16] <Kilos> ok
[19:16]  * genii makes sure a fresh batch of coffee is going
[19:16] <Kilos> yoohoo
[19:18] <genii> Kilos: Mostly I idle during meetings since I'm not usually in any of them, but am always glad to provide coffee on request :)
[19:18] <Kilos> genii  thank you so much
[19:23]  * genii goes back to tending the coffeepot
[19:24] <Carlin0> no more coffee, then you won't sleep tonight
[19:24] <Carlin0> lol
[19:27] <Kilos> i need to stay awake for th meeting
[19:38] <nicoz-> ok i'm ready
[19:39] <Kilos> lol
[19:39] <nicoz-> :P
[19:39] <nicoz-> hi Wild_Man ;)
[19:39] <nicoz-> glad to see you
[19:41] <Mr_Pan> hi Wild_Man
[19:44] <Wild_Man> hi nicoz- and Mr_Pan good to see you both, be back in a few minutes I am getting ready
[19:44] <Mr_Pan> Wild_Man, ok
[19:49] <Mr_Pan> hi Bashing-om
[19:50] <Bashing-om> Mr_Pan: :D Pleased you are here - we get settled up and do this :D
[19:50] <nicoz-> all right bashing-om?
[19:51] <Mr_Pan> Bashing-om, we are (me and Carlin0 ) ready
[19:51] <nicoz-> :P
[19:51] <Bashing-om> nicoz-: Yup - all here under control :D You ?
[19:51] <Carlin0> hi all
[19:52] <nicoz-> yes it is all right, i'm always studying :P
[19:52] <Bashing-om> Carlin0: Welcome to the fold.
[19:53] <Bashing-om> nicoz-: Such is life :P
[19:53] <Carlin0> My English is really poor
[19:53] <madhens> Hello all! I'll have to miss part of today's meeting but yay for starting off the new year with two candidates for membership!
[19:54] <Mr_Pan> Carlin0, reverso, deepl, google translate are your friends ;)
[19:55] <Carlin0> Mr_Pan, i know them well
[19:55] <sarnold> I haven't heard of deepl before, thanks
[19:55] <nicoz-> hi madhens nice to hear you
[19:55] <Bashing-om> Carlin0: nicoz-: has offered his services to translate in the event there is any difficulties :D
[19:55] <nicoz-> ;)
[19:56] <nicoz-> i am here ;)
[19:56] <Carlin0> Bashing-om, I'll take advantage
[19:57] <Bashing-om> Carlin0: It's Ubuntu - we can overcome !
[19:58] <nicoz-> I suggested to him to prepare a presentative speech
[20:01] <Kilos> welcome everyone
[20:01] <Mr_Pan> Kilos, thank u
[20:01] <diddledani> okie dokie
[20:02] <diddledani> here we go
[20:02] <nicoz-> hi diddledani
[20:02] <diddledani> .startmeeting Ubuntu Membership Board
[20:02]  * diddledani prods bot
[20:02] <diddledani> .startmeeting Ubuntu Membership Board
[20:02] <diddledani> have I forgotten the command again?
[20:02] <nicoz-> #
[20:02] <diddledani> bah
[20:03] <diddledani> #startmeeting Ubuntu Membership Board
[20:03] <meetingology> Meeting started at 20:03:02 UTC.  The chair is diddledani.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[20:03] <meetingology> Available commands: action, commands, idea, info, link, nick
[20:03] <diddledani> there we go
[20:03] <nicoz-> :D lol
[20:03] <diddledani> thanks :-)
[20:03] <nicoz-> ;*
[20:03] <diddledani> here comes the big paste
[20:03] <diddledani> Hello and welcome to the Ubuntu Membership Review Board meeting for 6th January 2022 (yes, 2022!). The wiki page for the Review Boards is available here: https://wiki.ubuntu.com/Membership/Boards
[20:03] <diddledani> We will attempt to get through all the applicants that have added themselves to that list, or posted a thread to the Ubuntu Discourse, before today's meeting. If we are unable to make it through the complete list due to time constraints, then at the next meeting we will pick up where we left off.
[20:03] <diddledani> The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).
[20:03] <diddledani> Each applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page or Ubuntu Discourse thread. After the introduction, the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.
[20:03] <diddledani> During this time, it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are reading wiki/launchpad/forum/other pages and deciding how they are going to vote.
[20:03] <diddledani> When the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If most of the voting board members vote +1, then the applicant is now an official Ubuntu member! (Feel free congratulate them!)
[20:03] <Wild_Man> I have the same problem
[20:03] <diddledani> Now, with any further ado, let's get started with the first applicant...
[20:03] <Mr_Pan> me  ?
[20:04] <Mr_Pan> Hello everyone
[20:04] <Mr_Pan> my name is Marco, 48 yers old, Italian but i live in Gemrmany
[20:05] <Wild_Man> Mr_Pan, please post links to your wiki and launchpad pages
[20:05] <diddledani> First up we've got Mr_Pan. Can you introduce yourself to the board and share the link to your wiki page or forum post and your launchpad.net profile
[20:05] <Mr_Pan> I wors as IT administrator in a Foudation that deals with projects for environmental protection
[20:05] <Mr_Pan> ok
[20:05] <Mr_Pan> LP Profile https://launchpad.net/~mrpan
[20:07] <Mr_Pan> My name is Marco, I am Italian, 48 years old and I live in Germany.
[20:07] <Mr_Pan> I work as IT Administrator in a foundation that deals with projects for environmental protection.
[20:07] <Mr_Pan> I approached the world of Linux for the first time in 1996 with RedHat and in 2006 I installed my first version of Ubuntu 5.04, distribution that I have not left since, choosing XFCE as DE.
[20:07] <Mr_Pan> In Italy I was the founder of a Linux User Group called "GioveLUG" now closed.
[20:07] <Mr_Pan> For 3 years I operate as OP of the Italian IRC Ubuntu channels
[20:08] <diddledani> Can you also share your wiki page link, please?
[20:09] <Wild_Man> Mr_Pan, how much have you been directly contributing to Ubuntu? and in what ways?
[20:09] <Wild_Man> For how long
[20:09] <Mr_Pan> https://wiki.ubuntu.com/mrpan
[20:09] <Mr_Pan> sorry
[20:10] <Mr_Pan> c
[20:10] <nicoz-> are both Op delegates on ubuntu-it channels
[20:11] <Mr_Pan> Wild_Man, with activity on IRC and i  organinized some Linux Day in Italy
[20:11] <nicoz-> https://launchpad.net/~ubuntu-it-irc/+members
[20:12] <nicoz-> both pug and mrpan
[20:12] <Wild_Man> Is the Linux day specifically for Ubuntu?
[20:12] <Mr_Pan> Wild_Man, no
[20:13] <Mr_Pan> it is an open day for all linux distro
[20:13] <Wild_Man> That is what I was thinking
[20:14] <Mr_Pan> Wild_Man, ok ...
[20:14] <Mr_Pan> i use ubuntu since 2006 version 5.06
[20:15] <diddledani> FTR there are testimonials here: https://discourse.ubuntu.com/t/mrpan-membership-application/25706
[20:15] <Mr_Pan> right
 i use ubuntu since 2006 version 5.06   >> 5.04 ... sorry
[20:16] <Kilos> http://wiki.ubuntu.com/mrpan
[20:17] <Kilos> oops
[20:17] <Mr_Pan> Kilos, don't worry
[20:18] <diddledani> Quick question while we review the testimonies, you have signed the Ubuntu Code of Conduct. Did you, and do you understand it, and do you confirm that you will be held to it for the duration of your membership if granted?
[20:18] <Mr_Pan> yes i confirm
[20:20] <Wild_Man> Mr_Pan, pan do you plan to contribute in any other ways in the future?
[20:20] <Mr_Pan> for now my commitment is online. I am always available.
[20:21] <Wild_Man> Okay
[20:21] <nicoz-> he provides support on ubuntu-it irc and forums
[20:21] <Mr_Pan> I am available for other activities in addition to irc if there was the possibility
[20:21] <Wild_Man> Thanks nicoz-
[20:22] <nicoz-> https://forum.ubuntu-it.org/memberlist.php?mode=viewprofile&u=2260
[20:22] <nicoz-> especially on irc.. for this are op delegates both he and Carlino
[20:24] <diddledani> any further questions from the board?
[20:24] <Wild_Man> No
[20:24] <Mr_Pan> no i have not questions
[20:24] <Kilos> nope
[20:24] <Bashing-om> no
[20:24] <diddledani> ok
[20:24] <diddledani> #vote Mr_Pan's membership
[20:24] <meetingology> Please vote on: Mr_Pan's membership
[20:24] <meetingology> Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname')
[20:24] <diddledani> wait for it
[20:25] <diddledani> #voters Wild_Man Bashing-om diddledani Kilos
[20:25] <meetingology> Current voters: Bashing-om, Kilos, Wild_Man, diddledani
[20:25] <diddledani> go
[20:25] <Wild_Man> +1
[20:25] <meetingology> +1 received from Wild_Man
[20:25] <Kilos> +1
[20:25] <meetingology> +1 received from Kilos
[20:25] <Bashing-om> +1 due to CoC confirmations and supporting testimonies.
[20:25] <meetingology> +1 due to CoC confirmations and supporting testimonies. received from Bashing-om
[20:26] <diddledani> +0 I'm going to abstain this time, because I'm not certain either way
[20:26] <meetingology> +0 I'm going to abstain this time, because I'm not certain either way received from diddledani
[20:26] <diddledani> #endvote
[20:26] <meetingology> Voting ended on: Mr_Pan's membership
[20:26] <meetingology> Votes for: 3, Votes against: 0, Abstentions: 1
[20:26] <meetingology> Motion carried
[20:26] <nicoz-> congrats Mr_Pan ;) welcome to board
[20:26] <Kilos> Mr_Pan  congratulations
[20:26] <Mr_Pan> thank u :D
[20:26] <Wild_Man> Congratulations Mr_Pan
[20:26] <diddledani> #topic Carlin0
[20:26] <Bashing-om> congrats here too Mr_Pan :D
[20:27] <Mr_Pan> :)
[20:27] <Carlin0> Hello, I started using Ubuntu in 2009 and having previous experiences with linux I immediately dedicated myself to helping less experienced users both on the Italian forum and on IRC
[20:27] <Carlin0> Unfortunately my presence on the forum stopped only 3 years later ( in which I wrote about 7500 msg https://forum.ubuntu-it.org/memberlist.php?mode=viewprofile&u=89839 ) due to misunderstandings and disagreements with the forum staff
[20:27] <diddledani> OK, next up we have Carlin0. Could you please introduce yourself to the board and share the links for your wiki page or forum post and your launchpad.net profile
[20:27] <Mr_Pan> thank u so much ... Vielen Dank ... Molte Grazie
[20:27] <Carlin0> Hello, I started using Ubuntu in 2009 and having previous experiences with linux I immediately dedicated myself to helping less experienced users both on the Italian forum and on IRC
[20:27] <Carlin0> Unfortunately my presence on the forum stopped only 3 years later ( in which I wrote about 7500 msg https://forum.ubuntu-it.org/memberlist.php?mode=viewprofile&u=89839 ) due to misunderstandings and disagreements with the forum staff
[20:27] <nicoz-> https://launchpad.net/~carlin0
[20:28] <Carlin0> Various links → https://discourse.ubuntu.com/t/carlin0-membership-application/25618/2 https://launchpad.net/~carlin0 https://wiki.ubuntu.com/Carlin0 https://wiki.ubuntu-it.org/Carlin0
[20:28] <Carlin0> I finished... and thank you for your time ;)
[20:28] <diddledani> ok, question the same as for Mr_Pan, you've signed the Code of Conduct. Did you, and do you understand it, and do you confirm that you will be held to it for the duration of your membership if granted?
[20:29] <Carlin0> of course diddledani
[20:29] <Carlin0> But I continued on IRC where I found a better environment for myself, and my commitment to helping and maintaining a clean environment was recognized with the proposal to become an "Ubuntu Italian IRC Operator" in 2018
[20:29] <Carlin0> In the future I would also like to dedicate myself to documentation, despite the obstacles that the Italian community poses me (I'm working on it)
[20:30] <diddledani> what kind of obstacles do you see with working in the Italian community?
[20:30] <nicoz-> no obstacles.. we are solving everything
[20:31] <nicoz-> had problems in the past with the ubuntu-it forum staff
[20:31] <Carlin0> diddledani, the Italian documentation group is mainly coordinated on the forum and I’m banned from the forum
[20:32] <nicoz-> but I know Carlino is bringing a great job to the wiki and on irc... a very experienced user
[20:32] <diddledani> ah, I see, thanks for that.
[20:33] <nicoz-> a user with a very friendly approach and always present and with excellent solutions
[20:33] <Bashing-om> Carlin0: Presently there is a big push to get our docs updated. How will these changes in procedure affect your effort to contribute to documentation translations ?
[20:34] <nicoz-> carlin0 is not very practical with English but is very useful on both forum and irc
[20:35] <Carlin0> Bashing-om, translation is not really my forte, but I can try.
[20:35] <diddledani> Thanks for helping out, nicoz- . Your input here is greatly appreciated :-)
[20:35] <nicoz-> ;)*
[20:37] <nicoz-> As a member, I tell you that Carlino deserves more than me membership... in the years he contributed more than me
[20:37] <Kilos> lol
[20:37] <nicoz-> is a very experienced user... see ubuntulog... almost always its supports help people
[20:38] <Mr_Pan> he will write guides for the italian ubuntu site
[20:38] <nicoz-> in presence and constancy, one of the best of the Italian IRC team
[20:38] <diddledani> any more questions from teh board members?
[20:39] <Kilos> and plenty support
[20:39] <Kilos> not here
[20:39] <diddledani> okthen, here we go.
[20:39] <nicoz-> thanks for listening to me..
[20:39] <Bashing-om> no - satisfied.
[20:39] <diddledani> #vote Carlin0 membership application
[20:39] <meetingology> Please vote on: Carlin0 membership application
[20:39] <meetingology> Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname')
[20:40] <diddledani> #voters diddledani kilos Bashing-om Wild_Man
[20:40] <meetingology> Current voters: Bashing-om, Kilos, Wild_Man, diddledani, kilos
[20:40] <diddledani> go
[20:40] <Kilos> +1
[20:40] <meetingology> +1 received from Kilos
[20:40] <Bashing-om> +1 again, due to CoC confirmations and supporting testimonies.
[20:40] <meetingology> +1 again, due to CoC confirmations and supporting testimonies. received from Bashing-om
[20:40] <nicoz-> ;)
[20:40] <Wild_Man> +1
[20:40] <meetingology> +1 received from Wild_Man
[20:41] <diddledani> +1 I see you've got the sum total of one person mad at you in your forum post, but the overwhelming support from your other community fellows shows you're doing things right.
[20:41] <meetingology> +1 I see you've got the sum total of one person mad at you in your forum post, but the overwhelming support from your other community fellows shows you're doing things right. received from diddledani
[20:41] <diddledani> #endvote
[20:41] <meetingology> Voting ended on: Carlin0 membership application
[20:41] <meetingology> Votes for: 4, Votes against: 0, Abstentions: 0
[20:41] <meetingology> Motion carried
[20:41] <nicoz-> congrats Carlin0
[20:41] <diddledani> Congratulations Carlin0
[20:41] <nicoz-> 4 to 4
[20:41] <nicoz-> woooow
[20:41] <Kilos> congrats Carlin0
[20:41] <nicoz-> :P
[20:41] <Carlin0> WoW thankks all
[20:41] <Wild_Man> Congratulations Carlin0
[20:41] <Kilos> welcome aboard
[20:41] <Bashing-om> \o/ Carlin0
[20:41] <nicoz-> Wild_Man diddledani Bashing-om Kilos thanks your time
[20:41] <Kilos> guys can we do something from here about unbanning him
[20:42] <nicoz-> Wild_Man diddledani Bashing-om Kilos thanks for your time
[20:42] <Mr_Pan> congrats Carlin0 !!!!
[20:42] <Kilos> or do we need CC help
[20:42] <nicoz-> Kilos thank you for introducing this argument
[20:42] <Wild_Man> Thank you nicoz- you help is very much appreciated
[20:42] <nicoz-> thank you Wild_Man
[20:42] <Kilos> thank you nicoz-
[20:43] <Carlin0> i'm very happy :o)
[20:43] <diddledani> We'll get both Mr_Pan and Carlin0 added to the ubuntumembers group shortly. When you're added you may then claim your certificate at https://forms.canonical.com/certificate/ Don't forget to check the rest of the perks at https://wiki.ubuntu.com/Membership#The_Perks Your @ubuntu.com emails will go live within 48 hours. Please do not set your @ubuntu.com email as your primary Launchpad.net address as that will cause loops
[20:43] <diddledani> and with that, I'll end the meeting
[20:43] <diddledani> #endmeeting
[20:43] <meetingology> Meeting ended at 20:43:19 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-01-06-20.03.moin.txt
[20:43] <nicoz-> ;)
[20:43] <Kilos> thank you board guys
[20:43] <Mr_Pan> Thanks !
[20:44] <nicoz-> Congratulations to new members Carlin0 and Mr_Pan .. i'm very happy
[20:44] <Kilos> now i can sleep
[20:44] <Carlin0> good night Kilos
[20:44] <Mr_Pan> good night guys
[20:44] <Kilos> thank you Carlin0  w will look into th unbanning
[20:45] <Carlin0> thanks :)
[20:45] <Kilos> my keyboard is packing up
[20:45] <Kilos> madhens  you were very quiet
[20:46] <Kilos> thank you for the reminder
[20:46] <nicoz-> madhens you haven't say any words
[20:46] <diddledani> yes, thanks madhens for the reminders about upcoming meetings. It really helps
[21:10] <Maik> keep in mind when applying for a certificate, it can take a year until you receive it
[21:15] <Bashing-om> Maik: Uh huh - mine still proudly on the wall above the monitor :P
[23:10] <madhens> Belated congrats to the new members! Went with Mr. Monica to his doctor's appointment.
[23:11] <Mr_Pan> madhens, thank u
[23:12] <nicoz-> :P
[23:13] <nicoz-> madhens your word is missing tonight
[23:16] <madhens> I was a little sad to miss it! I really love being here to cheer on all the potential and new members. But today, I was also a good wife, so I could only be here for the beginning.
[23:17] <nicoz-> the family always first of all, have you had good holidays?
[23:30] <madhens> I did! I hope you did as well.
[23:42] <madhens> I am gonna close the window but see you all in the next membership meeting, I'm sure!


[10:08] <xnox> sforshee, is 4.13 ready to go into artful release? just needs a d-i rebuild + remove "block-proposed" tag, no?
[10:08] <xnox> or are we waiting on something else too.
[10:11] <apw> xnox, it is close
[10:12] <apw> xnox, i am just looking at some adt bits to confirm they are falsies
[10:12] <apw> xnox, did you have a particular reason to care
[10:12] <xnox> ah, ok. I will be rebuilding d-i today for netcfg fixes, and i was wondering if i should bump the kernel d-i build uses.
[10:13] <xnox> otherwise a separate d-i build with kernel bump will need to be uploaded later
[10:13] <apw> xnox, difficult call, you likely wnat that to migrate today regardless
[10:13] <apw> xnox, so i would be inclined to waste buildds and do two
[10:14] <xnox> ack


[04:32] <lindar> Hi hi.
[04:32] <lindar> Anybody around?
[08:29] <Altiric> Anyone happen to be around?
[09:10] <chrionix> hi all, anyone using thinkfinger?


[17:48] <mhall119> pleia2: I was reading through the email thread on https://lists.ubuntu.com/archives/ubuntu-doc/2016-January/019674.html and you said you weren't sure about the feasibility of 2-factor auth, was that because you didn't know if it could be enabled, or because you didn't know if casual editors would have a 2-factor device/app?
[17:49] <pleia2> mhall119: it's just not my call, it may be tolerable on the community side but I don't know all the stakeholders here
[17:50] <pleia2> I think it would be ok to enable 2-factor on *just* the wikis maybe, it would be a barrier but tolerable, that's not something I think IS would do for *all* SSO things though (lots of people in the world using Ubuntu's SSO)
[17:50] <pleia2> certainly would be a lot better than what we have now :)
[17:51] <mhall119> yeah, but SSO already has the ability for individual sites to request/require 2-factor on login
[17:51] <pleia2> yep, it does exist
[17:51] <pleia2> I don't use it
[17:51] <mhall119> I don't know if the moin auth stuff has that ability though
[17:51] <pleia2> I do a lot of work with openstack and it's not all awesome with 2-factor
[17:51] <pleia2> (we are moving off of Launchpad/Ubuntu SSO some day...)
[17:52] <pleia2> anyway, yeah, I don't know either re: moin
[17:52] <mhall119> not to github I hope :)
[17:52] <pleia2> no, we can't use proprietary software in our infra, we have our own openstackid project+service
[17:53] <mhall119> ah, cool
[17:53] <pleia2> and I'm pretty sure captcha was one of the ideas in the ticket
[17:53] <pleia2> we have lots of ideas, but no feedback loop from IS about what's reasonable to expect
[17:53] <mhall119> anyway, I worked on SSO and 2FA while in ISD, so if you want me to look more info the feasibility of it for the wiki I'd be happy to
[17:54] <pleia2> if IS thinks that's the path to follow, I think it would be fine
[17:54] <mhall119> ack, popey and I are continuing to poke people in IS about it
[17:54] <pleia2> just don't want anyone wasting their time if it won't pan out because $reasons
[17:54] <pleia2> like, political reasons
[18:25] <knome> mhall119, i acknowledge it's a side issue, but re: the logging in issue; no, it was not fixed "many years ago", it was not until recently that ubuntu sso accounts had a username (without having been linked with launchpad)
[18:26] <mhall119> knome: I had to deal with this in summit (and LTP I think) which I've barely touched in the last 3 years, so unless we're talking about different things, it was a while ago
[18:28] <knome> this affected logins to the wikis and the qa trackers at least, it had a recent IS ticket
[18:28] <knome> pleia2 can confirm
[18:28] <knome> or might have a handy link to the ticket or sth
[18:28] <pleia2> I think loco.ubuntu.com too, but I could never properly confirm with someone who cared enough and had never logged in
[18:28] <knome> this totally wasn't "many years ago"
[18:29] <knome> so maybe it has something to do with this issue
[18:29]  * pleia2 nods
[20:19] <mhall119> pleia2: knome: can you see ifyou can edit help.ubuntu.com/community/ now?
[20:21] <mhall119> or, rather, that the people who could edit itbefore it was locked down can edit it agian?
[21:20] <pleia2> will have to ask someone not in the https://help.ubuntu.com/community/EditorGroup (or AdminGroup)
[21:20] <pleia2> (I am)
[21:27] <pleia2> mhall119: you could try :)
[21:37] <mhall119> do I have the right set of permissions (and non-permission)?
[21:38] <pleia2> I don't know, I don't know what you're trying to get by asking me to edit a page (I already know I can)
[21:38] <pleia2> I assumed IS had made a change :)
[21:39] <pleia2> since January 4th, only people in https://help.ubuntu.com/community/EditorGroup and AdminGroup can edit
[21:39] <pleia2> that's only a few of us, so for the past month and a half the wiki has only been edited by those people, and people sending us diffs and things on the mailing list (very tedious, I don't have time for this)
[21:40] <pleia2> since both EditorGroup and AdminGroup give administrative access, we don't want to just hand this out to everyone (the team has a process in place for building up a body of work as a trusted contributor for admin powers)
[21:41] <mhall119> pleia2: I was poking IS and was told: 15:16 < neale> mhall119: known users now have read/write
[21:41] <pleia2> I don't know what "known users" are
[21:41] <mhall119> so I just wanted to have someone here check that it was all back to how it was
[21:41] <mhall119> pleia2: I'm guessing people with accounts already on the wiki
[21:42] <pleia2> I assume he means EditorGroup and AdminGroup? We got no word back on the non administrative ContributorGroup that we requested in the ticket
[21:42] <mhall119> not sure what that means for new accounts though
[21:42] <pleia2> we should probably figure out what they mean, there's been no communication in the ticket
[21:43] <mhall119> ack, I'll ask neale to update the ticket
[21:43] <pleia2> thanks
[21:44] <mhall119> hmmm, they all show as ImmutablePage to me
[21:45] <pleia2> so you're not a "known user", whatever that means :)
[21:49] <mhall119> it means IS is pretending they don't know me :)
[21:51] <mhall119> pleia2: In theory, a new user should be able to edit https://help.ubuntu.com/community/Lubuntu/Documentation right?
[21:53] <pleia2> mhall119: not since the lockdown
[21:53] <pleia2> mhall119: but in a properly functioning wiki, like we want back, yes
[21:54] <pleia2> just like wiki.ubuntu.com
[22:00] <pleia2> mhall119: update from neale just now indicates you (normal people) should be able to edit pages now
[22:00] <pleia2> it's heavily cached, so may need to do a hard refresh when logging in to see things Edit-able
[22:00] <mhall119> pleia2: yeah, something was wonky for a bit, but I can edit pages now
[22:01] <pleia2> if it continues to be Immutable, welcome to our world, it's a nightmare
[22:01] <pleia2> \o/
[22:01] <pleia2> this gets us to our second topic, moinmoin sucks and is slow and is wonky :)
[22:01] <mhall119> keep an eye out for more spam, but hopefully they've all moved on by now
[22:01]  * pleia2 nods
[22:01] <mhall119> yes,but moinmoin is editable again, baby steps :)
[22:01] <pleia2> \o/
[22:02] <pleia2> not sure I want to do a splashy announcement on ubuntu-doc in case spammers are watching :\
[22:02] <pleia2> maybe people will just start to notice they can edit again
[22:02] <mhall119> yeah, I was thinking that same thing, let the folks who regularly edit know it's back
[22:03] <mhall119> but otherwise not advertise it too much
[23:33] <pmatulis> wiki.ubuntu.com was attacked just a few days ago. it will probabl happen again to the help wiki


[00:50] <mup> PR snapcraft#3896 closed: requirements: update craft-providers to 1.4.1 <Created by mr-cal> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3896>
[07:00] <mup> PR snapd#12092 opened: overlord/servicestate: disallow removal of quota group with any limits set <Simple 😃> <quota> <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/12092>
[07:10] <mup> PR snapd#12093 opened: multiple: clear up naming convention for thread quota <Simple 😃> <quota> <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/12093>
[09:11] <mup> PR snapd#12094 opened: data/systemd/Makefile: add comment warning about "snapd." prefix <Simple 😃> <Documentation> <Skip spread> <Created by mardy> <https://github.com/snapcore/snapd/pull/12094>
[09:26] <mup> PR snapd#12046 closed: cmd/snap-bootstrap: changes to be able to boot classic rootfs <Run nested> <Created by alfonsosanchezbeato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12046>
[10:16] <dot-tobias> Does someone here have experience with distributed compilation from snapcraft's LXD container? Basically, I want to set up icecc / distcc instances in my local network to aid the main snapcraft builder which uses LXD.
[10:21] <mup> PR snapd#12095 opened: snap/quota,wrappers: allow using 0 values for the journal rate limit <quota> <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/12095>
[10:24] <mardy> dot-tobias: not me, but please be sure to document the process in a blog post because it sounds very interesting!
[11:01] <mup> PR snapd#12084 closed: tests: check snap download with snapcraft v7+ export-login auth data <snap-revision-delegation> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/12084>
[11:06] <mup> PR snapd#12096 opened: store/tooling,tests: support UBUNTU_STORE_URL override env var <Created by pedronis> <https://github.com/snapcore/snapd/pull/12096>
[11:36] <lissyx> mardy, I might need some advice
[11:37] <lissyx> mardy, for v
[11:37] <lissyx> mardy, for https://github.com/canonical/firefox-snap/pull/4#discussion_r957445517
[11:37] <mup> PR canonical/firefox-snap#4: Bug 1732755 - Expose Snap hunspell based on System hunspell sets <Created by lissyx> <https://github.com/canonical/firefox-snap/pull/4>
[11:46] <mardy> lissyx: I'm not sure, what "too late" means here. At first sight, it would seem reasonable to me if the umount was done in the disconnect hook
[13:30] <mup> PR snapcraft#3893 closed: config: add snap config model <Created by mr-cal> <Closed by mr-cal> <https://github.com/snapcore/snapcraft/pull/3893>
[14:59] <lissyx> mardy, ok, and is it a good or bad idea to try to unmount in the post-refresh script ?
[15:04] <lissyx> mardy, from my point of view, I was worried of having the mountpoint kept mounted for no good reason once we have done what we had to do
[15:18] <mup> PR snapd#12097 opened: tests: create initial fake-installer that uses the GET /systems/<label>  API <Created by mvo5> <https://github.com/snapcore/snapd/pull/12097>
[17:43] <mup> PR snapd#12098 opened: tests: skip interfaces-udisks2 in fedora <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/12098>
[18:56] <mup> PR snapcraft#3897 opened: cli: graciously handle keyboard interrupt <Created by cmatsuoka> <https://github.com/snapcore/snapcraft/pull/3897>
[20:19] <mup> PR snapd#12099 opened: daemon: implement stub `"action": "install"` <Created by mvo5> <https://github.com/snapcore/snapd/pull/12099>
[20:41] <mup> PR snapcraft#3894 closed: Merge 7.1.3 release <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3894>
[20:56] <mup> PR snapcraft#3897 closed: cli: graciously handle keyboard interrupt <Created by cmatsuoka> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3897>
[21:46] <mup> PR snapcraft#3898 opened: config: add snap config model <Created by mr-cal> <https://github.com/snapcore/snapcraft/pull/3898>
[21:46] <mup> PR snapcraft#3899 opened: providers: choose default provider from snap config for core 22 <Created by mr-cal> <https://github.com/snapcore/snapcraft/pull/3899>


[00:06] <guiverc> ack.
[02:42] <Guest2039> hello
[02:43] <guiverc> G'day Guest2039, if you have a Lubuntu support question, just ask it, be patient, people will respond when they can.  #lubuntu-offtopic for non-support talk though
[02:43] <Guest2039> ok thank you!
[02:44] <Guest2039> basically, is there a way that i can set up persistent storage on the same usb device as the live install?
[02:44] <Guest2039> also... did i word that right?
[02:45] <guiverc> I have little experience with persistent devices; if I was to create one I'd use `mkusb`, see https://help.ubuntu.com/community/mkusb  (section 7 is persistent live systems)
[02:46] <guiverc> Once upon a time I used to install to thumb-drive (non-live installation), that's much harder with modern lubuntu, but I believe still possible with Lubuntu 18.04 (ie. install to thumb-drive; but haven't done it in years so this is opinion only)
[02:54] <Guest2039> if that were to work.... how would one go about that? and would that be far easier from my windows machine (or even the only way?)
[02:54] <Guest2039> because i THINK thatd be ideal
[02:55] <Guest2039> correct me if im wrong but what you just described would be the best way if possible to use this usb drive as my only drive on the system right?
[02:56] <guiverc> I can't advise on windows (I don't use it), Lubuntu manual on writing is https://manual.lubuntu.me/stable/1/1.2/booting_the_image.html which has links to creating boot media from nix/macos/windows
[02:59] <guiverc> it could create the *live* environment, which could then be booted to install & use `mkusb`  (how I'd do it on windows as windows is something I've forgotten; XP was last I used).. live media can install to other media (my second prior comment about non-live install on media which I'm not sure is easy/possible post-18.04 with calamares installer; but opinion only)
[03:00] <guiverc> you can have a VM operate live & write to media to (avoiding two thumb-drives), but that involves some setup on host virtualization software
[03:03] <Guest2039> either way this is going to require 2 seperate physical devices/// ok well what you just said i think is kindof an answer, being either 2 physical drives, or at least... well effectively using a vm to run a second layer to... kindof fake it out.... did i understand that right
[03:04] <guiverc> yeah the VM is running the first LIVE media meaning first-thumb-drive isn't required... it can then write to the '2nd' thumb-drive as install (18.04 anyway), but it required some setup as I recall for virtualbox; I wouldn't recall how to do that (only did it once)
[03:06] <guiverc> persistence is the easier alternative; which can also be used via VM/two thumb-drives (two thumb-drives to use mkusb; it no doubt can be created on windows directly; I just don't know how sorry)
[03:06] <Groot> ok Thank You for the help, even if it didnt get me set up its certainly helped send me in the right direction rather then just a more or less dead end (i think im going to try figuring it out on windows)
[03:07] <Groot> unfortunetly, all my thumbdrives (or even SD cards) either are setup with specific other things or, those that just hold things like photos i dont really have other drives to merge to at the moment (at least not that i know where they are since we moved)
[03:07] <Groot> Thanks again!
 Hi there. I wonder if anyone can help me for a lubuntu installation.
[19:23] <kc2bez> Which version of Lubuntu?
 I have Debian 10 installed in my machine. I want to dual boot lubuntu 20.10 alongside it. I edited the partition to give 27gb for lubuntu (via installation wizard) but it failed. It happened twice (I cleared up the new free partition with gparted).
[19:27] <kc2bez> Do you have a screenshot of the failure or if we could get a paste of the logfile that would be helpful too.
[19:27] <kc2bez> !paste
 I'll re-attempt it now.
 Okay. I have two photos. How do I take a logfile, please? (re @lubuntu_bot: (irc) <kc2bez> Do you have a screenshot of the failure or if we could get a paste of the logfile that would be helpful too.)
 My Imgur keeps failing to upload. (re @lubuntu_bot: (irc) <kc2bez> Do you have a screenshot of the failure or if we could get a paste of the logfile that would be helpful too.)
 https://matterbridge.lubuntu.me/8b2f3490/file_1440.jpg
 https://matterbridge.lubuntu.me/4fd44c1e/file_1441.jpg
 Here's the photos though


[15:16] <cmaloney> Morning
[15:17] <jrwren_> good morning!
[15:21] <rick_h__> party party
[16:05] <cmaloney> http://deathwishcoffee.myshopify.com/products/death-cups-10-pack
[16:47] <rick_h__> I know someone that got some deathwishcoffee and liked it a lot
[16:49] <cmaloney> That's cool
[16:49] <cmaloney> JoDee's not convinced. :)
[16:49] <cmaloney> OK, I'm going to make a proclaimation (sp)
[16:49] <cmaloney> January is Backlog month
[16:50] <cmaloney> That means that I'm only going to read / watch / play things from my backlog
[17:13] <cmaloney> http://www.reddit.com/r/fossworldproblems/comments/1tqdl9/i_like_to_tell_everyone_that_a_gnulinux_os_is_at/
[17:33] <greg-g> sometimes you just need to start your day doing a mega deep clean of the bathroom.
[17:34] <greg-g> and showering after, cuz, gross.
[19:23] <rick_h__> hah
[19:23] <rick_h__> yea, having cleaners out for a mega cleaning today before the birthday party.


[07:21] <kcj> Evening.
[07:23] <ajmitch> hi
[07:37] <kcj> Hello.
[09:00]  * hads considers coming down the road for PyCon
[09:02] <ajmitch> hads: you should
[20:31] <ojwb> morning
[22:16] <ajmitch> morning
[22:32] <kcj> Morning.
[23:19] <chilts> morning


A particular task that is newbie friendly?