[17:35] <chilts> morning
[17:40] <ojwb> morning
[18:31] <ibeardslee> morning
[19:16] <Atamira> morning


[03:14] <qwebirc7074> I'm attempting to install Mythbuntu, and I think it did install successfully.  I'm attempting to boot it up for the first time after that and I'm getting stuck on a "Loading Operating System..." screen.
[14:12] <FabriceMG> super1, it's possible to add number of DVB device up in mythtv-backend.conf before start the backend?
[17:12] <qwebirc63365> hello, i moved my backend server to new hardware. i used the backup.pl and restore.pl, i then moved the storage harddrives to new machine, mounted in same location then added storage directories in backend-setup. Im have a few problems mythweb status page does not show correct storage available. the mythtv storage folders are set to full control to mythtv:mythtv.
[20:00] <johnf1911> http://askubuntu.com/questions/183372/lirc-zilog-ir-transmission-no-longer-working-with-hd-pvr-on-12-04
[20:00] <Zinn> [askubuntu.com] lirc - lirc_zilog IR transmission no longer working with HD-PVR on 12.04 - Ask Ubuntu
[20:00] <johnf1911> I've moved my question to askubuntu
[20:35] <qwebirc61863> I'm trying to install the latest release of Mythbuntu and I think it installed, but when I'm trying to boot for the first time after doing that I get stuck on a "Loading Operating System..." screen and I'm not sure what to try next.


[01:18] <zul> Philip5: yes if you have a copy already then git pull
[01:19] <Philip5> zul: well, that's what i thought but getting a copy at first can be plenty of data to download
[01:19] <zul> true buts its only once
[01:20] <zul> ../in theory
[01:20] <Philip5> i cloned the ubuntu-dapper.git and got like 400 mb
[01:21] <Philip5> is'n that the draw back with git compared to cvs?
[01:21] <Philip5> where i can get a snapshot and take it from there
[01:21] <zul> there isnt one
[01:22] <Philip5> but it would be a good feature
[01:22] <zul> it would but we dont have one right now
[01:22] <Philip5> true... and that was what i thought
[01:23] <Philip5> but i could have use a feature like that :)
[01:23] <neuralis> Philip5: lightweight checkouts (and partial checkouts) are the most commonly requested git features; it's reasonable to expect git will grow support for them
[01:25] <Philip5> it would be nice
[01:26] <Philip5> i have to make a custom made kernel with ubuntu and want as many of the patches the standard use in it and therefore it would be nice to catch the tree as a snapshot
[01:26] <Philip5> now i had to play sherlock holmes and search the net for all of them instead
[01:28] <zul> Philip5: ah...have you tried apt-get linux-source-2.6.17?
[01:28] <zul> linux-source-2.6.17 - Linux kernel source for version 2.6.17 with Ubuntu patches
[01:29] <Philip5> i need even newer with the -mm patch
[01:29] <Philip5> have brand new hardware that are not supported until right now
[01:29] <zul> jmicron?
[01:30] <Philip5> zul: how could you guess... ;)
[01:30] <zul> Philip5: because i sent a patch to BenC a couple of days ago for edgy
[01:30] <Philip5> zul: great
[01:31] <Philip5> right now i'm building the kernel and have to make my own ubuntu livecd with it to get everthing installed
[01:32] <mjg59> zul: Can you flag the bug pending if it isn't already?
[01:34] <Philip5> zul: do you know if the jmicron will be backported or is it more likely with new kernel in edgy?
[01:34] <Philip5> new=newer
[01:34] <zul> mjg59: pretty sure i already did but ill double check
[01:34] <zul> more likely in edgy
[02:24] <dilinger> cool, jgarzik took the sata_mv fix
[01:32] <AnAnt> anyone knows when the MMC fix will be available ?
[03:15] <Philip5> have anyone here by chance tried to build the latest squashfs3.1-r2?
[03:15] <Philip5> with the patch i mean
[03:17] <Philip5> it breaks for me
[03:17] <Philip5> don't where to ask about this otherwise
[03:17] <Philip5> know..
[04:33] <drew> does 'Ubuntu kernel development discussion' include asking about possible bugs in edgy?
[05:08] <fabbione> hey BenC
[05:08] <BenC> hey
[05:09] <fabbione> BenC: can you please pull from my edgy branch? i have the usual gfs2/gfs/dlmfs updates
[05:09] <drew> I asked this before: does 'Ubuntu kernel development discussion' include asking about possible bugs in edgy?
[05:09] <fabbione> drew: bugs -> launchpad
[05:09] <BenC> fabbione: sure thing
[05:09] <fabbione> BenC: thanks
[05:09] <fabbione> BenC: jbailey is looking into glibc install issue
[05:09] <fabbione> tomorrow i will spend sometime to look at lvm
[05:10] <fabbione> upstart is no go on sparc
[05:10] <fabbione> at least on Niagara
[05:10] <fabbione> i need to check on the normal sparc too
[05:10] <BenC> I need to take pictures of my latest project
[05:10] <fabbione> and we should really really start some install tests for edgy
[05:10] <BenC> Inserted a 20Gig driver into a Watchguard Firebox X 2500
[05:11] <BenC> and installed Ubuntu Edgy on it
[05:11] <BenC> even got the LCD panel working
[05:11] <fabbione> ah nice
[05:12] <BenC> LCD 2x20 panel w/backlight, and 4 buttons...
[05:12] <fabbione> ehehe
[05:12] <BenC> plus it has 6 ethernet ports
[05:12] <fabbione> not bad
[05:13] <fabbione> anyway gfs is rock solid
[05:13] <fabbione> gfs2 still has some issues but upstream is working on our bugs
[05:13] <fabbione> otherwise we are good
[05:14] <BenC> ok, cool
[05:15] <BenC> http://www.watchguard.com/products/x2500.asp
[05:15] <fabbione> neat toy!
[05:15] <BenC> used to work for them, so I have like 8 of their boxes laying around doing nothing
[05:16] <BenC> setting this one up for the T1 firewall
[05:16] <fabbione> is it Gigabit or just fastether?
[05:19] <fabbione> feeeehh my son is crying like hell
[05:19] <fabbione> bbl
[05:22] <BenC> it's fast ethernet rtl8139C+
[05:22] <mvirkkil> Where can I find out if the edgy kernel has the patch for DEVICE_ZD1211B (mentioned here http://reactivated.net/patches/linux-kernel/2.6.17/zd1211rw.patch) and especially my device with the id 0x1215 ?
[05:24] <BenC> mvirkkil: It should have it
[05:25] <mvirkkil> BenC: Ok, thanks. Guess I'll need to give edgy a shot then. (it didn't go in to 2.6.17, but it should be in 2.6.18 iirc.)
[05:26] <BenC> I put it in 2.6.17
[05:26] <BenC> for edgy
[05:26] <BenC> or a similar patch at least
[05:26] <mjg59> BenC: I've got some more suspend patches for you
[05:26] <BenC> mjg59: ok
[05:26] <mjg59> BenC: Any idea when the acpi stuff I sent you will be merged?
[05:26] <mvirkkil> BenC: Excellent. Thankyou very much :)
[05:27] <BenC> mjg59: Today I'm merging all outstanding patches from you guys and preparing another edgy uploaad
[05:27] <mjg59> BenC: Rock
[05:32] <mjg59> BenC: Mailed - should be a tarball of 5 patches
[05:32] <BenC> ok
[05:35] <mjg59> I may have a few more for you later
[05:41] <zul> heh...everyone take down BenC
[06:34] <BenC> mjg59: wow, you sure know how to pack a lot of commits into a short email :)
[06:34] <BenC> 195 commits
[06:34] <mjg59> The ACPI one?
[06:34] <mjg59> Yeah
[06:34] <BenC> yeah, it was 154 alone
[06:34] <mjg59> That was fun
[06:35] <BenC> everything applied, one of your last pm-fixes didn't apply cleanly, but it was just a one-line offset I had to fix
[06:35] <mjg59> Cool
[06:35] <mjg59> I win at patches
[06:38] <mjg59> BenC: Oh, hang on, I've triggered a build failure
[06:38] <mjg59> Hang on, I'll clean it up
[06:38] <BenC> heh, sweet...it's your fault this time :)
[06:40] <mjg59> Hm
[06:40] <mjg59> It might actually be fixed by the patch I've previously sent you
[06:42] <BenC> well, they are all in there...I'm starting some builds so I'll find out pretty quickly
[07:49] <Mithrandir> BenC: you're aware that we're frozen for knot 3 now, right?
[07:49] <Mithrandir> BenC: (just so you don't end up uploading a new kernel in the middle of the freeze)
[08:16] <BenC> Mithrandir: when is knot-3?
[08:16] <Mithrandir> BenC: Thursday, hopefully
[08:16] <BenC> mjg59: looks like the builds went ok except for t he ABI bump
[08:16] <BenC> Mithrandir: ok, I'll plan an upload for Friday then
[08:17] <mjg59> BenC: Yeah
[08:18] <AnAnt> BenC: btw, do you  know when the MMC fix will be on the Ubuntu repos ?
[08:19] <BenC> AnAnt: next upload
[08:21] <AnAnt> BenC: well, I mean, when do you guys upload ?
[08:22] <BenC> I upload on Friday I hope
[08:22] <AnAnt> ok, thanks
[08:22] <zul> oh goody...i can send you more patches then
[08:25] <BenC> mjg59:
[08:25] <BenC> arch/ia64/kernel/acpi.c: In function 'acpi_parse_fadt':
[08:25] <BenC> arch/ia64/kernel/acpi.c:632: error: dereferencing pointer to incomplete type
[08:25] <BenC> arch/ia64/kernel/acpi.c:635: error: dereferencing pointer to incomplete type
[08:25] <BenC> arch/ia64/kernel/acpi.c:638: error: dereferencing pointer to incomplete type
[08:29] <BenC> mjg59: should it do struct fadt_descriptor_rev2 -> fadt_descriptor_rev2_minus?
[08:32] <BenC> actually, looks like it can just use the rev1 struct since it has the same members that the functions uses
[08:38] <mjg59> BenC: Hm
[08:39] <mjg59> Let me take a look
[08:41] <mjg59> BenC: Yeah, just fadt_descriptor
[08:41] <BenC> no rev?
[08:41] <mjg59> Rather than rev anything
[08:42] <mjg59> Right
[08:42] <BenC> ok
[08:42] <mjg59> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=236ee8c33277ab48671995f26dc68a4639936418
[08:43] <TeePOG> good evening
[08:44] <TeePOG> if I installed edubuntu with the i386 installation disc on an AMD64, how do I get the K8 kernel?
[08:44] <mjg59> You probably don't want to do that
[08:44] <TeePOG> how so?
[08:45] <mjg59> Because the i386 distribution uses functionality not provided by the amd64 kernel
[08:45] <mjg59> vm86, specifically
[08:45] <TeePOG> ok...
[08:45] <BenC> and not all ioctls are thunked for 32-bit userspace to a 64-bit kernel
[08:46] <TeePOG> will I get any benefit from the k7 kernel? i need as much as i can get, this machine will run vmware with *doze in
[08:46] <BenC> so things like usb printing may not work
[08:46] <TeePOG> i see
[08:46] <BenC> TePOG: there's not much else to gain, the -k7 kernel is suggested though
[08:46] <TeePOG> we're using network printers anyway, so usb printing is a non-event
[08:47] <TeePOG> thanks a lot BenC
[08:47] <TeePOG> lol
[08:47] <TeePOG> goodnight all
[09:01] <BenC> mjg59: drivers/ide/ide-io.c:160: error: 'pm' undeclared (first use in this function)
[09:01] <BenC> caused by your last patches
[09:01] <BenC> mjg59: I think it just needs rq-> prepended to it, can you check?
[09:03] <mjg59> BenC: Oops
[09:03] <mjg59> BenC: Yeah
[09:03] <mjg59> My error
[09:03] <mjg59> Woo
[09:03] <BenC> ok, thanks
[09:03] <mjg59> The tifm driver works now
[09:40] <zul> right im going home ttyl
[09:41] <ivoks> bye
[10:37] <BenC> mjg59: ...
[10:37] <BenC> drivers/built-in.o: In function `ide_wait_not_busy':
[10:37] <BenC> (.text+0x88270): undefined reference to `touch_nmi_watchdog'
[10:37] <BenC> on ppc
[10:37] <mjg59> Oops
[10:37] <neuralis> Mithrandir: do those fix bug 59997? i haven't had a chance to look at it in detail yet
[10:38] <mjg59> Can you #ifdef that with CONFIG_I386?
[10:38] <mjg59> Or is it CONFIG_X86?
[10:38] <mjg59> Whichever one covers amd64 and i386
[10:39] <Mithrandir> neuralis: hopefully that was fixed by zul's last upload?  If not, I'll fix it, yes.
[10:40] <neuralis> Mithrandir: only if it hasn't hit the archive yet; still fails with the latest packages that are there
[10:41] <Mithrandir> neuralis: hmm, ok. :-/
[10:41] <Mithrandir> I'll poke it
[10:41] <neuralis> thanks
[10:55] <mjg59> BenC: Any chance you can do 59851?
[10:56] <BenC> yeah, can do
[10:58] <mjg59> Ta
[10:58] <mjg59> It's a regression over dapper right now


[00:55] <demophobia> where do we report errors like: /usr/share/themes/Lubuntu-dark-panel/gtk-2.0/gtkrc:682: Unable to find include file: "apps/xfce4-notifyd.rc"
[14:57] <carlS> Having trouble troubleshooting installing a package. Is this a good place to get help or is there a good forum for this elsewhere?
[14:58] <carlS> I have Googled it, and much of the suggestions seem to work, but don't solve the problem.
[15:00] <leszek> just ask your question
[15:00] <leszek> then maybe someone might be able to help
[15:01] <carlS> Using Lubuntu 16.0.4 LTS in VirtualBox here.
[15:02] <carlS> trying to install dotnet as an experiment to play around with it, I find that sudo apt-get install dotnet-sdk-2.0.0 gives message
[15:03] <carlS> that it is unable to locate package, that it cannot find it by glob, cannot find it by regex.
[15:03] <carlS> When using synaptic package manager, it gives red exclamantion point which means that it thinks it is broken.
[15:05] <carlS> When I used Edit|Fix Broken Packages it gives several errors saying that it may be due to something being held.  When I try dpkg --get-selections | grep hold there appears to be nothing held.
[15:06] <carlS> So at this point the package appears in synaptic, but won't install, and when I use apt-get it doesn't find it .
[15:06] <carlS> <-- has to lurk for a second, but will be back in a bit.
[15:11] <carlS> Exact messages in synaptic package manager is: E: Unable to correct problems, you have held broken packages. E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies
[16:13] <carlS> Since I really don't know where the conflict is, I'm backing up data and going to reinstall to <IP_ADDRESS> ISO and see where that gets me. I wish there were some easier way to tell exactly what the problem is.
[17:07] <carlS> In case anyone was wondering, I'm back up and running after reinstalling. Will have to reinstall anaconda python and a few other things, but I think it was faster than trying to debug whatever went wrong in the packages that was giving me the errors.
[19:35] <TheSilentLink> hi when I close the lid it doesn't show the lock screen. Is this because I have 2 an external monitor connected to my laptop


[06:27] <Unit193> Looks like some of the meeting scrolled past, but some of the gnome-software stuff was still there.  "and it uses appdata, another plus" err, that's a plus...?  I hardly see that.  Synaptic isn't super actively maintained, but it is actually maintained.  Perhaps not actively developed would be a better term.  I would say synaptic is certainly more functional and more reliable.  As far as
[06:27] <Unit193> screensavers goes, I'd be hesitent about seeding a semi-new locker option, considering the security concerns they can open.  I'll get the latest version up in the PPA though of course. I too would be against extending the defaults shipped.
[11:50] <brainwash> Unit193: you hardly see what? it being something useful, or it being used only for few applications?
[18:11] <Unit193> brainwash: As that being a plus.
[22:22] <Unit193> bluesabre: We need exo 0.12.2-2 in Bionic.
[22:24] <Unit193> bluesabre: https://salsa.debian.org/xfce-team/desktop/exo/commit/5a73fee69274b4b1e4f599afb5b86ac0b3f11d51
[22:24] <bluesabre> Unit193: welcome back :)
[22:24] <Unit193> Thanks/sorry/unfortunate, I know? :D
[22:25] <bluesabre> :D
[23:25] <bluesabre> Unit193: "I'd be hesitent about seeding a semi-new locker option", technically that's what got us into the mess with light-locker :D
[23:25] <Unit193> Hah, yep!
[23:25] <Unit193> ...I still use xscreensaver though.
[23:26] <bluesabre> :)
[23:29] <Unit193> bluesabre: I don't suppose you did the git things for the new xfce4-screensaver?
[23:35] <bluesabre> Unit193: ah, nope
[23:35] <bluesabre> Just did the bare minumum to get things to the PPA and write a blog post


[00:14] <nacc> jgrimm: check now?
[00:14] <nacc> jgrimm: on nspr
[01:02] <nacc> infinity: fwiw, i think i figured out the horde-crypt failure. It's actually testing things correctly (using the gpg binary and setting up its own test-internal gpg keys). But it's using deprecated/ignored options to gpg :)
[01:19] <mwhudson> slangasek: oh i didn't realize powerpc was going away quite that much
[01:20] <nacc> wtf gpg
[01:20] <nacc> infinity: have to set GPG_TTY=$(tty) and pass '--pinentry-mode loopback' and the tests seem to work
[01:22] <jgrimm> nacc, worked, thanks!
[01:25] <nacc> jgrimm: great, sorry about that
[01:29] <jgrimm> no worries at all!
[01:52] <nacc> infinity: figured out most of them! gpg changed the output and the tests were parsing it, as well..
[02:05] <tsimonq2> Ok, deciding to pick up bug 1516454 again.
[02:05] <tsimonq2> So I'm curious if anything stands out to anybody, I trid the obvious solution of editing the GTK property as I believe it was missing something?
[03:00] <Umeaboy> Hi!
[03:00] <Umeaboy> Who's the maintainer of the mkvtoolnix package in Ubuntu 16.10?
[03:01] <Umeaboy> Hmmmmmmmmmm. I think I better take this in #ubuntu-app-devel.
[03:02] <sarnold> isn't that channel for the phones?
[03:03] <sarnold> given the long list of debian version numbers here https://launchpad.net/ubuntu/+source/mkvtoolnix/+publishinghistory I suspect there's no one at ubuntu that 'tends' to this package -- it mostly appears to be pulled in from debian unchanged, until toolchain issues cause rebuilds
[03:04] <Umeaboy> It has only been pushed to the development release of Ubuntu.
[03:05] <Umeaboy> Seems odd since 9.6.0 is a stable release and not a development release.
[03:05] <Umeaboy> That's my idea of stable anyhow.
[03:42] <mwhudson> stgraber, slangasek: i finally filed https://bugs.launchpad.net/snappy/+bug/1651936
[03:47] <sarnold> are all the failures coming from expect, and are they all password-related?
[03:48] <sarnold> oh I guess not, there's also this:
[03:48] <sarnold> mesg: ttyname failed: Inappropriate ioctl for device
[03:48] <sarnold> but I suspect that's the usual glibc-vs-kernel disagreement about tty devices in filesystem namespaces
[03:49] <sarnold> also tests/main/chattr -- that's an odd one
[05:13] <slangasek> mwhudson: yup
[06:57] <mwhudson> sarnold: ah hah, go would be particularly susceptible to that
[08:47] <fossfreedom> sil2100: thanks - got an autoemail from launchpad to say you have "fix released" our merge request for lp:ubuntu-cdimage
[08:52] <sil2100> fossfreedom: np, did you get my yesterday's message about the image builds failing?
[08:53] <fossfreedom> sil2100: hmm - have looked.  nothing :(
[08:54] <sil2100> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-budgie/zesty/
[08:54] <sil2100> We might be missing some enabling of this project on livefs builders
[08:55] <sil2100> cjwatson: hello! Are you still around today by any chance?
[08:57] <sil2100> fossfreedom: might be a bit hard to get things done, a lot of people are on holidays already
[08:58] <fossfreedom> sil2100: ah - yes. with xmas on the weekend ... good excuse to have a very long break!
[10:54] <cjwatson> sil2100: what do you need?
[10:57] <sil2100> cjwatson: hello! We have enabled a new ubuntu flavor in cdimage, ubuntu-budgie - it seems the builds are failing since there's still something missing in the builders to enable that? http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-budgie/zesty/daily-live-20161221.log
[10:57] <cjwatson> sil2100: do you know about the production config branch on nusakan?
[10:58] <sil2100> cjwatson: I see it but never 'used' it before I think
[10:58] <cjwatson> sil2100: that's what you need to edit :)
[10:58] <sil2100> Ah :)
[10:58] <cjwatson> sil2100: did anyone create the livefs objects in LP?
[10:58] <sil2100> cjwatson: I don't think so...
[10:59] <sil2100> cjwatson: is this also something I can do, or does require some special powers?
[10:59] <cjwatson> You should be able to; let me just look it up
[11:00] <cjwatson> lp-shell production devel -> lp.livefses.new(owner='/~ubuntu-cdimage', distro_series='/ubuntu/zesty', name='ubuntu-budgie')
[11:00] <cjwatson> doesn't need any special powers since you're just trying to build it for amd64 and i386, so no devirtualisation needed
[11:01] <sil2100> cjwatson: ok, let me try running this then, thanks :)
[11:01] <cjwatson> then add it to livefs-launchpad in the production config branch
[11:01] <sil2100> And I'll edit the production config then
[11:01] <sil2100> Thanks for the pointers!
[11:01] <cjwatson> and make sure to pull that onto nusakan of course
[14:44] <ginggs> matplotlib, python-stdlib-extensions and pandas show test regressions in lmfit-py on armhf - where lmfit-py is not installable since python-pandas removal. What needs to be done to let them migrate?
[15:45] <jabowery> A July Debian bugfix has not made it into xenial updates.  The advice at the launchpad unassigned bug tracking comments is: A thing the maintainer perhaps could do would be to create a launchpad mirror of the sourceforge repo maxima's code is kept in - and then to initiate a nightly build ppa for maxima.  https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1602941/comments/8
[15:45] <jabowery> How does one go about identifying or becoming that "maintainer"?
[15:47] <tumbleweed> ubuntu packages usually don't have maintainers, as such
[15:47] <tumbleweed> I'd SRU that patch into xenial
[15:48] <jabowery> What does SRU stand for?
[15:48] <tumbleweed> !sru
[15:48] <tumbleweed> can you find the patch that fixes the bug?
[15:51] <dobey> it looks like 5.37.2-9 could be synced from debian to xenial-updates (and maybe yakkety-updates), as -8 is what's in ubuntu
[15:52] <dobey>    * Bug fix: "maxima do not load the draw package.", thanks to Renato
[15:52] <dobey>      Alvarez Nodarse (Closes: #803251).  rework sys:*load-pathname* patch
[15:52] <tumbleweed> it's a different -8
[15:52] <dobey> ?
[15:53] <tumbleweed> I mean, yakkety is already fixed
[15:53] <cjwatson> maxima/xenial == maxima/yakkety
[15:53] <tumbleweed> I've never heard of syncing into a stable -updates
[15:53] <cjwatson> *zesty* has a different -8
[15:53] <dobey> right
[15:53] <tumbleweed> oh, yes, that's what I was thinking
[15:53] <dobey> yakkety and xenial have the same package
[15:54] <cjwatson> it's certainly *possible* to copy into a stable -proposed and have it verified, but it wouldn't suit the tools very well because it wouldn't refer to a Launchpad bug
[15:54] <cjwatson> so verification wouldn't work right
[15:54] <cjwatson> better to just cherry-pick into 5.37.2-8ubuntu1, even if that ends up essentially identical to 5.37.2-9
[15:55]  * tumbleweed has a poke at it
[16:57] <jabowery> So I take it I should pursue a different procedure than submitting an SRU on the debian fix to maxima?
[16:58] <nacc> jabowery: SRU is not a debian thing
[16:58] <nacc> jabowery: SRU is an ubuntu thing :)
[16:58] <nacc> jabowery: oh i see what you were saying -- the right approach is to SRU the debian change to ubuntu's packages where relevant, but I think tumbleweed may be doing it
[16:58] <jabowery> Great!
[17:00] <tumbleweed> I did it. jabowery will you test it once it's published?
[17:00] <tumbleweed> subscribe to the bug now, if you haven't
[17:01] <jabowery> Sure I'll test it.  I'm subscribed to https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1602941
[17:03] <jabowery> I presume that means I'll receive an email notifying me it has been published.  I've just received an email saying "** Changed in: maxima (Ubuntu)        Status: Confirmed => Fix Released  ** Also affects: maxima (Ubuntu Yakkety)    Importance: Undecided        Status: New", but that's not a notice that it's been published, right?
[17:04] <tumbleweed> jabowery: you will
[17:10] <nacc> infinity: mdeslaur: after some wrangling, debian maintainer has bumped the abi for imagemagick :)
[17:26] <smoser> hey, i'm using apt.Cache() from python apt package.
[17:27] <smoser> im' using it on zesty, and want to be able to apt.Cache(rootdir=foo)
[17:27] <smoser> cache.update()  is failing
[17:27] <smoser> due to i think no keyrings
[17:27] <smoser> to read xenial data
[17:28] <smoser> http://paste.ubuntu.com/23669428/
[17:28] <smoser> what is the right way to tell it that i want it to use the old keyrings ?
[17:33] <nacc> smoser: add_key_from_keyserver? (just paging through the files/APIs)
[17:34] <smoser> whered you see that ?
[17:34] <nacc> smoser: it's in apt/auth.py
[17:34] <smoser> i dont think iw ant to add from a keyserver, but i do wan tot add a key
[17:34] <nacc> you can also add from a file, i think
[17:34] <nacc> add_key_from_file
[17:35] <nacc> or even just add_key :)
[17:46] <smoser> nacc, hm... no dice.
[17:46] <smoser> all that does is run apt-key
[17:47] <nacc> smoser: rbasak: i think this might have been a thinko on my part in the remote addition for `usd clone`: http://paste.ubuntu.com/23669494/; right now, the remote branches in `git branch` do not show up as remote, because they are all fetched into refs/heads (which is the local branches). Thoughts?
[17:47] <nacc> smoser: oh, hrm
[18:32] <sil2100> fossfreedom: ok, with all the builder bits enabled, looks like the images are still failing - I suppose it might be something missing in livecd-rootfs?
[18:33] <sil2100> fossfreedom: from what I see you didn't submit any changes for ubuntu-budgie there? I suppose that should be needed? You mentioned the builds succeeded locally on your build environment though
[18:39] <fossfreedom> sil2100: to be honest - I didnt know there was yet another project to make changes to :(
[18:41] <fossfreedom> sil2100: this project? https://launchpad.net/livecd-rootfs
[18:42] <fossfreedom> looking at the code ... not sure where to make changes.
[18:44] <fossfreedom> maybe this?  - looks to have some flavor specifics http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/auto/config
[19:07] <fossfreedom> sil2100: ok - have created a branch with changes that are very similar to ubuntu-gnome's - https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1652144
[19:24] <sil2100> fossfreedom: ok, let me try taking a look at them but it's a bit lateish here
[19:36] <sil2100> fossfreedom: ok, quick thing - could you switch the changelog entry from 'zesty' to UNRELEASED?
[19:36] <sil2100> We only put series names once the package is released
[19:37] <fossfreedom> yep - doing it now
[19:41] <sil2100> Thanks
[19:41] <sil2100> Ok, I'll try to release this, but then I'm going off ;)
[19:42] <sil2100> fossfreedom: push the change to the branch, I'll merge it, prepare for release and run a test build
[19:43] <fossfreedom> sil2100: ok - thanks - pushed
[19:49] <sil2100> fossfreedom: ok, new livecd-rootfs building
[19:50] <fossfreedom> sil2100: much appreciated!  Have a good night! ... and if you are off for xmas - have a great hols.
[19:50] <sil2100> fossfreedom: thanks for the quick response btw, we might get this building before my EOY ;)
[20:50] <sil2100> fossfreedom: same to you!
[20:50] <sil2100> fossfreedom: I go off now, the package still didn't migrate from -proposed so I can't run the job
[20:50] <sil2100> But when I see it migrated later today I'll just kick a quick build - if not, tomorrow's daily build should catch any possible issues
[20:50] <sil2100> o/
[21:35] <jgrimm> nacc, http://paste.ubuntu.com/23670285/
[21:51] <jgrimm> nacc, ah.. %% will get me what I want.
[22:14] <nacc> jgrimm: ah yes, but even that is incorrect
[22:14] <nacc> err, no, you're right
[22:14] <nacc> it should be fine, sorry!
[22:14] <nacc> jgrimm: can you file a bug on that (or put a comment in the one already filed for logical tag issues)
[22:14] <jgrimm> yeah, %% should escape the % that you've used to represent : for
[22:15] <jgrimm> nacc, yeah, you could probably push out a warning for that at least
[22:15] <jgrimm> will do
[22:16] <nacc> jgrimm: yep, we can do a quick sub in the string to escape certain characters (I think % is the only one we'd need to, actually)
[22:16] <jgrimm> yeah, i had guessed that from the bug you had against logical tag
[23:19] <nacc> infinity: in case you care, and i hope you don't, i think php-horde-crypt's failures are all related to the gpg2 migration: http://paste.ubuntu.com/23670714/. Going to try sending htat upstream as well
[23:40] <nacc> infinity: and nm, i found a even smaller patch for upstream, which doesn't rquire the killall ugliness