[00:13] <bdrung> ari-tczew: the "-b XXXXXXX -b XXXXXX" method is easy to implement. if you want a different behaviour, file a bug and describe how it should behave.
[00:21] <MTecknology> I just want to get an opinion..... Application has a line "include path/*" which includes backup files created by those incredibly annoying editors. Application fails to start because multiple files with the same contents exist. Should it be the user or the application that needs to make up for the short coming of the editor?
[00:22] <ebroder> MTecknology: Having the application deal with it is ideal, but there are plenty of applications that don't
[00:23] <Laney> it would be a valid upstream bug imo
[00:24] <RAOF> It sounds like the application is loading code from a user-writable directory?  That's always going to be fragile.
[00:50] <TheMuso> ari-tczew: Please remember to include debian changelog entries when uploading a merge.
[00:50] <ari-tczew> TheMuso: example?
[00:50] <TheMuso> dssi-vst
[00:52] <MTecknology> RAOF: no - /etc/nginx/sites-enabled/*
[00:52] <ari-tczew> TheMuso: pull sources on hard disk.
[00:52] <MTecknology> RAOF: and /etc/nginx/conf.d/*.conf
[00:52] <ari-tczew> TheMuso: there are changelog including Debian changes. that LP handle incorrect merges.
[00:53] <RAOF> MTecknology: Ah.  More excusable :)
[00:53] <ari-tczew> TheMuso: please check it right now and give back to me
[00:53] <TheMuso> ari-tczew: I am not talking about the source package, I am talking about when you create the changes file for upload.
[00:53] <micahg> ari-tczew: he's referring to using -v when uploading
[00:53] <MTecknology> RAOF: especially since the defaults imply you should edit the site in sites-available/ and symlink in sites-enabled/
[00:53] <Laney> ari-tczew: https://lists.ubuntu.com/archives/natty-changes/2010-November/002091.html
[00:54] <ari-tczew> micahg: -v to which command?
[00:54] <Laney> you should see the -v option to debuild/dpkg-buildpackage
[00:55] <MTecknology> RAOF: I'm just wondering whether or not it's worth dealing with and marking wishlist to never actually get to unless someone else does or say that they should edit files correctly.
[00:55] <ari-tczew> aha, now I have debuild -S -sa
[00:55] <Laney> -v<previous ubuntu version>
[00:56] <ari-tczew> Laney: in this case, debuild -S -sa -v0.9.2-0ubuntu1 ?
[00:57] <Laney> sounds right
[00:57] <Laney> cat *_source.changes to see if the debian changelog is in there too
[00:58] <ari-tczew> Laney: I prefer to use graphical editors.
[00:58] <ari-tczew> like gedit
[00:58] <Laney> ok
[00:58] <micahg> ari-tczew: it's not for editing
[00:58] <ari-tczew> micahg: OMG... editing/reading
[00:59] <micahg> ari-tczew: there's a risk, that's why tools like cat/less are nice
[00:59] <Laney> I wish more wasn't in my muscle memory :(
[00:59] <ari-tczew> micahg: I'm careful
[01:00] <Laney> it's pgp signed anyway so you can't break it accidently
[01:00] <ari-tczew> +1 ^
[01:01] <ari-tczew> TheMuso: otherwise, do you have any another questions about this upload?
[01:02] <micahg> Laney: one can't get into the archive accidentally, but one can certainly create more work for oneself accidentally
[01:02] <TheMuso> No.
[01:02] <ari-tczew> great
[01:04] <Laney> https://wiki.ubuntu.com/MOTU/New is where -v is documented btw
[01:06] <ari-tczew> Laney: heh, my first time to see this one
[01:06] <ebroder> Also in Mom's REPORT
[01:06] <ebroder> *MoM
[01:06]  * ari-tczew is off to bed, good night.
[01:11] <MTecknology> !info nginx natty
[01:11] <MTecknology> ya....
[01:12] <MTecknology> so there's two changes being made from debian going into -1ubuntu1; the problem I'm having is that these issues were actually addressed already
[02:56] <RAOF> Hm.  Why can't I upload tracker to universe?
[02:56] <StevenK> What's the error?
[02:57] <RAOF> Lack of permissions.  Let me roust up the email.
[02:57] <ajmitch_> it's not magically exclusive to a packageset, is it?
[02:57] <RAOF> Are there packages which are exclusive to a packageset?
[02:58] <RAOF> “The signer of this package is lacking the upload rights for the source package, component or package set in question.”
[02:58] <ajmitch_> I thought the kernel packages may have been, but not for any others
[02:58] <ajmitch_> I haven't kept up on the confusing permissions
[03:01] <ajmitch_> it doesn't appear to be in any packageset for natty
[03:02] <ajmitch_> http://paste.ubuntu.com/537712/
[03:04] <StevenK> Looks like only -desktop got rights to it for karmic only
[03:04] <micahg> RAOF: MOTU should be able to upload according to the ACL
[03:05] <micahg> StevenK: was in main then
[03:05] <RAOF> How does one inspect the ACL, incidentally?
[03:05] <micahg> RAOF: ubuntu-archive-tools
[03:05]  * ajmitch_ was using edit_acl.py from ubuntu-archive-tools
[03:07] <ajmitch_> I get the feeling that I'm killing LP from how slow this is :P
[03:08] <RAOF> gpg says the changes are signed with the key that launchpad has, so it shouldn't be that.
[03:09] <ajmitch_> you haven't expired from the uploading team recently, have you?
[03:11] <RAOF> launchpad.net/~raof says I'm still a member of ~ubuntu-dev, which IIRC is the appropriate team.
[03:11] <ajmitch_> I think ~motu is the necessary team still
[03:11] <ajmitch_> but the team listing no longer shows expired members
[03:11] <micahg> RAOF: you're no longer a member of MOTU
[03:12] <RAOF> Ah.  That would be it.  I thought ~motu was deprecated, and had been for ~a year?
[03:12] <ajmitch_> I don't think ubuntu-dev membership grants upload rights, everyone including per-package uploaders are members of it
[03:12] <micahg> RAOF: no, MOTU will transition into Masters of the Unseeded when the reorg happens
[03:13] <RAOF> Well, that's why I can't upload tracker, clearly :)
[03:13] <micahg> RAOF: you still have cli-mono packageset upload rights ATM
[03:13] <RAOF> Yup.
[03:13] <ajmitch_> time to bug the DMB!
[03:13] <ajmitch_> & apply for core-dev while you're at it
[03:14] <StevenK> What ajmitch_ said
[03:14] <lifeless> ajmitch_: is it timing out
[03:15] <ajmitch_> lifeless: no, it just took ~50 seconds to get the information for one package
[03:15] <lifeless> ajmitch_: grag.
[03:15] <ajmitch_> I haven't seen what it's doing in the code, but that seems like a long time
[03:15] <lifeless> thats fucked
[03:15] <lifeless> check the api code is sane, and if it is, file a bug on lp
[03:16] <micahg> RAOF: I'm happy to sponsor for you while you await reactivation
[03:16] <RAOF> micahg: Ta.
[03:17] <ajmitch_> it seems to loop over a few things, but doesn't appear to be too insane
[03:23] <lifeless> ajmitch_: still, file bugs.
[03:25] <ajmitch_> will do
[03:32] <RAOF> micahg: http://cooperteam.net/Packages/tracker_0.8.17-1ubuntu1_source.changes with associated debdiff http://cooperteam.net/Packages/tracker.debdiff .  Thanks.
[03:37] <micahg> RAOF: in progress
[04:01] <micahg> RAOF: done
[04:01] <RAOF> micahg: Thanks muchly!
[04:02] <micahg> RAOF: np
[04:24] <micahg> what's the proper way to not update timestamps on PO files if any (or do I have to go edit the debian.tar.gz)?
[04:49] <micahg> what's the proper way to attribute when you take half a patch someone makes
[04:50] <RAOF> Thank them in the changelog, I think.
[04:50] <RAOF> “Based on a patch by $FOO”
[04:50] <micahg> RAOF: ok, what about DEP-3 for Origin/Author?
[04:50] <micahg> I added a thanks in teh changelog and have origin as the debian revision, but no author
[04:51] <RAOF> That'd fly.
[04:51] <micahg> in the patch that's straight from Debian, I added author and origin with the package revision
[05:31] <micahg> RAOF: do you know how to not update PO creation times on source package creation?
[05:32] <RAOF> Not off the top of my head, no, sorry.
[05:32] <RAOF> Why is it updating the creation times, though?
[05:35] <micahg> RAOF: debian/clean they get updated
[05:36] <micahg> oops d/rules clean
[06:16] <micahg> RAOF: tracker regressed on PowerPC
[06:17] <RAOF> Well, not so much regressed as *still* FTBFS :).  I'll take a look.
[06:17] <micahg> RAOF: according to the logs it built fine before for 0.8.17-1
[06:17] <RAOF> Yeah, it did.
[06:17] <RAOF> Then we uploaded e-d-s 2.32, and it wouldn't have built against that.
[06:18] <micahg> RAOF: ah, It's a dependency issue
[06:31] <bilalakhtar> Meh, another careless merge by Bhavani. Looks like he merged nginx in a hurry, the package is now broken.
[06:35] <micahg> bilalakhtar: https://bugs.edge.launchpad.net/ubuntu/+source/nginx/+bug/547267/comments/12 <-- this is not an appropriate comment in a bug
[06:36] <micahg> bilalakhtar: also, we don't reopen bugs that have been fixed, but file new ones and reference the old one
[06:36] <bilalakhtar> micahg: No, its like this:
[06:36] <bilalakhtar> The directory is referenced twice
[06:37] <bilalakhtar> and hence dpkg gives an error, and the result is the same as it was earlier: no default site
[06:37] <micahg> bilalakhtar: I agree with MTecknology, the Debian way is more appropriate for a default site
[06:38] <bilalakhtar> micahg: that's what I am doing
[06:38] <MTecknology> hm?
[06:38] <micahg> bilalakhtar: oh, ok, I got the impression you disagreed with him from your comment
[06:38] <bilalakhtar> micahg: In the old debian package no default site existed, but there was an explanation in debian/README.Debian
[06:39] <bilalakhtar> RoAkSoAx went ahead with a direct fix by putting the site in /var/www/nginx/
[06:39] <bilalakhtar> but that was against the D-p
[06:39] <bilalakhtar> so I did what apache2 does
[06:39] <bilalakhtar> but the debian way is even better
[06:40] <bilalakhtar> Also, if I had done the merge, it would have been a sync instead
[06:40] <bilalakhtar> all the changes had been accepted
[06:40] <MTecknology> oh- bilalakhtar that was a crap ton of my changes going into debian btw
[06:40] <bilalakhtar> but now a new change has been added: - Add support for html5 codecs
[06:41] <MTecknology> kartik did the html5 addition
[06:42] <bilalakhtar> and another thing:
[06:42] <bilalakhtar> The UFW profile is being added twice
[06:42] <bilalakhtar> with different file names
[06:43] <bilalakhtar> such a head-breaking merge...
[06:43] <MTecknology> Is there anything even in the ubuntu version at this point that isn't in the debian version?
[06:43] <micahg> bilalakhtar: BTW, if it should be a sync and the package is broke, you can reverse the Ubuntu changes with an appropriate changelog note and reupload
[06:44] <bilalakhtar> micahg: No, the sync isn't possible now, bhavani added another Ubuntu change: - Add support for html5 codecs
[06:44] <bilalakhtar> I am dropping the rest and uploading
[06:44] <micahg> didn't MTecknology just say the Debian maintainer added that?
[06:45] <MTecknology> micahg: that's not in the uploaded package jsut yet - but it is in the branch
[06:45] <bilalakhtar> so I will closely watch the package, when its added then I'll sync
[06:45] <MTecknology> give me a minute..
[06:47] <micahg> ah, right, he just upstreamed it, but w/out a patch :(
[06:48] <MTecknology> micahg: there were about 10 different merges from the branch i popped off - I'll do better next time
[06:49] <bilalakhtar> done, just test-building before uploading
[06:49] <bilalakhtar> (though the build should run fine)
[06:49] <bilalakhtar> It was like a whole merge re-done
[06:50] <MTecknology> bilalakhtar: http://bazaar.launchpad.net/~nginx/nginx/debian/revision/102
[06:50] <bilalakhtar> MTecknology: good!
[06:50] <MTecknology> :)
[06:52] <MTecknology> bilalakhtar: from now on anythign that breaks - yell at me :D
[06:52] <bilalakhtar> MTecknology: it won't
[06:52] <MTecknology> well... i'm an upstream maintainer now so.... ya.....
[06:52] <MTecknology> we'll hope so :P
[06:53] <micahg> MTecknology: that's great, we need more people working with both Distros
[06:55] <MTecknology> micahg: I'm trying- I'm enjoying it enough
[06:56] <bilalakhtar> I think this must be the highest number of uploads I did for a single package: nginx
[06:56] <bilalakhtar> 3rd one in the way
[06:57] <bilalakhtar> MTecknology, micahg: uploaded
[06:58] <MTecknology> micahg: So far- I think the most confusing thing is policy; not difference but trying to understand them and hwo they go together
[06:58] <micahg> MTecknology: yep, that's an important thing
[07:03] <bilalakhtar> micahg: using natty?
[07:03] <micahg> bilalakhtar: not yet
[07:03] <bilalakhtar> hmm, I would move right now if I had the daily build in my hands
[07:03] <MTecknology> I should upgrade....
[07:05] <MTecknology> I upgraded to an SSD too- that's been amazing
[07:05] <MTecknology> truely the american way, buying stuff I can't afford
[07:12] <MTecknology> and a reboot - if I come back - I'm on natty
[07:12] <MTecknology> :P
[07:13] <MTecknology> yay
[07:56] <dholbach> good morning!
[08:41] <poolie> quick question: is it correct that packages in main can't have build-dependencies on things in universe?
[08:41] <maco> yes, i believe so
[08:41] <micahg> poolie: yes
[08:45] <poolie> thanks
[08:45] <micahg> poolie: if you need something, you can file an MIR if it's worth it
[08:46] <poolie> thanks
[08:46] <poolie> the context is https://lists.ubuntu.com/archives/bazaar/2010q4/071019.html
[08:46] <poolie> i think we will file a MIR for natty
[08:47] <micahg> poolie: I think you can get away with it in a PPA though if it's not native
[08:48] <poolie> what do you mean?
[08:48] <micahg> poolie: build-dep on universe
[08:49] <micahg> poolie: I'm just wondering why you would add something like that on a stable branch?
[08:49] <poolie> we didn't add it
[08:50] <micahg> oh, hmm, so what changed that the microreleaseexception was broken?
[08:50] <poolie> all of 2.2.0 has had this run-time requirement to run the test suite
[08:50] <poolie> when 2.2.0 was uploaded to maverick, it didn't run the test suite as the package was built
[08:50] <poolie> for SRUs, they want to change the build rules to run the test suite
[08:51] <poolie> which sounds pretty reasonable, but because of this snag apparently won't work
[08:51] <micahg> poolie: ah, ok, I would suggest uploading to a PPA to run the test suite and include a link to the logs in the SRU
[08:51] <poolie> yep
[08:51] <poolie> that's what we'll do
[08:51] <poolie> i hope
[08:52] <poolie> well, we will do that and will i hope the sru  will be accepted
[10:10] <spaceboy> index help
[10:10] <spaceboy> index HELP
[10:10] <spaceboy> INDEX HELP
[10:11] <Rhonda> spaceboy: erm, … yes?
[10:11] <spaceboy> Hi, was just trying to use the commands in the list
[10:12] <Rhonda> You can query ubottu if you like to play with it, it doesn't need to be in the channel, you know. :)
[10:13] <spaceboy> Oh, ok, I don't really know much about IRC, thanks
[11:38] <andol> Seems to be some missunderstandings going on in https://bugs.launchpad.net/ubuntu/+source/libssh2/+bug/681423
[11:38] <andol> Perhaps someone suitable could write a few wise words?
[11:59] <Riddell> andol: I don't think I have any more to add
[14:02] <AnAnt> Hello, is natty still auto-importing from Debian ?
[14:02] <AnAnt> or should I sync manually ?
[14:03] <jpds> AnAnt: http://irclogs.ubuntu.com/2010/11/29/%23ubuntu-devel.html#t13:40
[14:04] <AnAnt> ah, alpha-1 should be out this week ?
[14:05] <Rhonda> AnAnt: https://wiki.ubuntu.com/NattyReleaseSchedule
[14:05] <Rhonda> Debian Import Freeze is on December 30th
[14:05] <AnAnt> Rhonda: thanks
[14:06] <Rhonda> But jpds is right of course, at this very moment it's not autosyncing
[14:35] <bdrung> bilalakhtar: around?
[14:35] <bilalakhtar> bdrung: yup
[14:36] <bdrung> bilalakhtar: audacious joined the pkg-multimedia group in debian. join pkg-multimedia to get access to the git repository.
[14:37] <bilalakhtar> bdrung: :o okay
[14:38] <bdrung> bilalakhtar: audacious-plugins need a license review (both 2.3 and 2.4.1)
[14:39]  * bilalakhtar logs into alioth
[14:42] <bilalakhtar> bdrung: sent request
[15:56] <RenatoSilva> I have a patch for a new feature on a specific project, but I'm lazy to create an account on their tracker and I think they don't care too much about it. Is it worth reporting a wishlist bug in Launchpad for keeping a patched version of the project in Ubuntu?
[15:58] <cody-somerville> udienz, Saying 'Please use ppa' is not satisfactory rationale to mark a Ubuntu bug as Fix Released.
[16:02] <udienz> cody-somerville: so a bugs switch to new again?
[16:06] <ScottK> RenatoSilva: Unless it's a package that sees a lot of Ubuntu specific development probably not.
[16:57] <RenatoSilva> ok
[21:16] <ari-tczew> BlackZ: say thanks to zul due to merging nagios-plugins
[23:50] <stilia-johny> hi is any alive?
[23:52] <micahg> stilia-johny: you might want to try #ubuntu-app-devel for Makefile help if it's not part of the packaging
[23:53] <stilia-johny> yhnks


[15:07] <SebastianGrabows> Hi! I'm having some problems to set up an iscsi target on Ubuntu Server 20.04. I've set up the target using targetcli and saved the config. The configuration gets restored after reboot, so everything looks fine there. But although the target is configured to listen on <IP_ADDRESS>:3260 it seems that the server is not listening on port 3260 (at least according to `lsof -i`). Is there something special (like e.g. some service) that has
[15:07] <SebastianGrabows> to be enabled here?
[15:16] <TJ-> SebastianGrabows: is this something you've read? https://ubuntu.com/server/docs/service-iscsi
[15:17] <SebastianGrabows> <TJ- "Sebastian Grabowski: is this som"> Yes, it unfortunately describes only the initiator setup. I'm stuck at configuring the target.
[15:18] <TJ-> oh!
[15:20] <TJ-> SebastianGrabows: can the debian wiki links help? https://wiki.debian.org/SAN/iSCSI
[15:28] <SebastianGrabows> <TJ- "Sebastian Grabowski: can the deb"> Not really. My steps were actually similar to the workflow described there: https://wiki.debian.org/SAN/iSCSI/LIO . The targetcli config looks like this right now: https://paste.ubuntu.com/p/NjjM2dsjxK/ The problem is that the portal isn't listening: https://paste.ubuntu.com/p/73nNy9fFMH/
[15:39] <TJ-> SebastianGrabows: is the service actually running?
[15:40] <TJ-> SebastianGrabows: something like "systemctl status iscsitarget"
[15:48] <SebastianGrabows> <TJ- "Sebastian Grabowski: something l"> These are all services with scsi or target in their names and all are enabled: https://paste.ubuntu.com/p/tG7nHVpvXQ/
[15:51] <TJ-> SebastianGrabows: are they running now, though?
[16:03] <SebastianGrabows> They all run, except of open-iscsi but that shouldn't be a problem because as far as I understand it is used only by initiators.
[16:06] <TJ-> I'm stumped then; network tooling seems to show the process isn't listening so I'd assume it isn't running, so that would be where I'd focus - what is the process name, which service file starts it, what is its status
[16:11] <SebastianGrabows> I think that maybe there shouldn't be a systemd service since LIO is handled by the kernel: https://wiki.archlinux.org/title/ISCSI/LIO
[16:11] <SebastianGrabows> The necessary modules are currently loaded.
[16:14] <TJ-> can you use another system to probe the expected port?
[16:22] <SebastianGrabows> Oh! Probing with nmap shows that the port is actually open! Funny thing that `lsof -i` says otherwise. Sorry for wasting your time on this. Thanks!
[16:24] <TJ-> SebastianGrabows: grrr @ kernel !
[16:24] <TJ-> SebastianGrabows: does 'ss' report the port if lsof doesn't? "sudo ss -tnlp sport = 3260"
[16:27] <SebastianGrabows> <TJ- "Sebastian Grabowski: does 'ss' r"> Yup: https://paste.ubuntu.com/p/Sbg3MvkPG8/
[16:40] <SebastianGrabows> I think I found out why lsof didn't show the port. It seems that lsof looks in /proc/*/fd for sockets. Thus ports opened by the kernel may not show up there. Good to know!
[16:46] <TJ-> SebastianGrabows: yeah, horrible when you get caught out by things like that


[00:14] <st3fan> xnox: when i go through the setup too quick (..., time zone, account setup) the installer window disappears ... i see some disk activity but i have no idea if it is actually finishing the install
[00:14] <st3fan> it barely started copying files when the window closed, so it can't be done i'm sure
[00:15] <st3fan> unfortunately i can't seem to switch to a text based console to check what is happening
[00:16]  * st3fan will try again and this time will not fill in his account info until the installer is done
[00:22] <xnox> st3fan: is that with panda image. what timestamp? we are respinning it due to crashing like that....
[00:24] <st3fan> grabbed it from http://cdimage.ubuntu.com/daily-live/current/ an hour ago
[00:24] <st3fan> quantal-desktop-armhf+omap4.img       12-Oct-2012 14:39
[00:26] <st3fan> should i grab an earlier one?
[00:28] <xnox> you should want the http://cdimage.ubuntu.com/daily-live/20121012.3/quantal-desktop-armhf+omap4.img
[00:28] <st3fan> downloading
[00:28] <xnox> current is a symlink =) currently points to 20121012.3
[00:28] <xnox> st3fan: you can use zsync.
[00:29] <xnox> if you have the old one around use: $ zsync http://cdimage.ubuntu.com/daily-live/20121012.3/quantal-desktop-armhf+omap4.img.zsync
[00:29] <st3fan> cool i'll do that next time
[00:29] <xnox> and it will download the delta =) which should be very small
[00:29] <xnox> st3fan: if it still fails. please report bug from the panda (if you can) with `ubuntu-bug ubiquity`
[00:30] <st3fan> ok
[00:30] <xnox> st3fan: and add a "install result" to http://iso.qa.ubuntu.com/qatracker/milestones/240/builds/25703/testcases
[00:30] <xnox> the entire disk test case ;-)
[00:32] <st3fan> the internets are fast today, the download took 4 minutes
[00:32] <st3fan> dd'ing a diff would be better :)
[00:40] <st3fan> ok booting
[00:44] <st3fan> ah yes now i get a little window with a progress bar 'copying files'
[01:27] <st3fan> xnox: success!
[22:06] <st3fan> ubuntu 12.10 keeps crashing on the pandaboard :-(
[22:06] <st3fan> it just hangs, how do i find out what actually happens?
[22:17] <st3fan> i wonder if this is the network controller .. i think i read something about that in the release notes?
[23:10] <infinity> st3fan: Are you sure it's hung?  Are you watching on a serial console?
[23:56] <st3fan> infinity: i don't get much on the serial console .. should i congigure that as a boot parameter to get it going?


[09:32] <natefinch> morning fwereade_
[11:28] <fwereade_> natefinch, heyhey
[11:29] <natefinch> fwereade_: so, do we have a mechanism for charms to say what version of juju they're compatible with?  My guess is the answer is "no" and that some people will have a heart attack at the thought.
[11:30] <fwereade_> natefinch, so, I wrote this a while back: https://docs.google.com/a/canonical.com/document/d/1lV6Vlqj3VlOXPLZD1T4vV865Ab16YgIJivyWnZXdhCo/edit
[11:31] <fwereade_> natefinch, it seemed pretty uncontroversial -- but equally we've, uh, ocmpletely failed to explicitly schedule it
[11:33] <fwereade_> natefinch, and, yeah, it's important for a lot of things
[11:33] <natefinch> fwereade_: seems like it
[11:34] <fwereade_> natefinch, so, dammit, we need to get it done somehow, and probably backported to older versions
[11:35] <natefinch> fwereade_: well, my team is doing the charmers pain points, seems like it could go to us.  Doesn't seem terribly difficult from a 10,000 foot view.
[11:36] <fwereade_> natefinch, I don't think it should be
[11:36] <fwereade_> natefinch, there will probably be some devils in the details
[11:36] <natefinch> fwereade_: there usually are.
[11:36] <fwereade_> natefinch, in particular it onvolves charm store work
[11:36] <fwereade_> natefinch, which will need some extra coordination
[11:37] <natefinch> fwereade_: hmm... that's unfortunate.  I had hoped we could get away with keeping the changes only in core.... but yeah, I guess not.
[11:39] <fwereade_> natefinch, ok, so, I think this is a prerequisite for a bunch of things your team will want to be involved with
[11:40] <fwereade_> natefinch, when do you think you can get it scheduled? and would you start a conversation with rick_h__ (?) about how to coordinate the charm store stuff?
[11:41] <natefinch> fwereade_: I'm going to start on it ASAP.  Since it's required for the default-hook stuff, I might as well get going on it right now.
[11:41] <natefinch> fwereade_: I'll coordinate with Rick on it.
[11:43] <fwereade_> natefinch, cool
[11:44] <fwereade_> natefinch, do a first pass over the spec looking for places I get it completely hilariously wrong
[11:44] <fwereade_> natefinch, there will almost certainly be at least one
[11:45] <fwereade_> natefinch, you've aleady got edit on that doc I think
[11:45] <natefinch> fwereade_: yep, looks like it.  Thanks.
[11:50] <natefinch> fwereade_: gotta run. Will keep you up to date, though.
[15:58] <rick_h__> fwereade_: cool on the feature flags, will comment on the doc some