[00:19] <len-dt> ubiquity still crashes today too.
[06:25] <Len-nb> micahg, ubuntustudio-look recommends plymouth-theme-ubuntustudio, but that doesn't seem to exist.
[06:26] <Len-nb> There is a package by that name, but all it has in it is an empty debian directory
[06:27] <Len-nb> ubuntustudio-look seems to have the whole plymouth theme inside anyway, can I safely remove that recommends?
[06:29] <Len-nb> or maybe it should be a replaces or conflicts.
[06:34] <Len-nb> synaptic shows a plymouth-theme-ubuntustudio installed (precise) with all the files the look package has.
[06:38] <astraljava> Len-nb: The bzr branch indeed seems empty.
[06:39] <Len-nb> But there is such a package
[06:39] <Len-nb> And we install it
[06:39] <Len-nb> Where is it coming from?
[06:48] <Len-nb> The look package has not changed since march, but precise shows a lot less files installed than should be in the package.
[06:50] <Len-nb> astraljava, it also recomends ubuntustudio-wallpapers
[06:51] <Len-nb> But I can't find the branch for that at all.
[06:53] <Len-nb> And the look package seems to have all the files in it that the wallpapers package does
[07:08] <Len-nb> micahg, astraljava I have sent a message on the list to Scott (I think he was the last one to hit it) asking what his intent was.
[07:09] <Len-nb> To break up one package into smaller ones or make one package do all.
[07:10] <Len-nb> I was going to add a text plymouth theme that says ubuntustudio to replace the fallback that just says ubuntu.
[07:11]  * Len-nb has a machine that actually gets the text one.
[07:13] <Len-nb> I will wait on my fix until the recommends/replaces/conflicts are figured out. So I can commit that fix first.
[07:15] <Len-nb> astraljava, One thing I do see is that all three installed packages are the same version.
[07:19] <Len-nb> The install scripts in the look package are named for the packages... That is the look package has a plymouth-theme-ubuntustudio.install script as well as a ubuntustudio-wallpapers.install script.
[07:25] <Len-nb> Thats it for me tonight...
[11:54] <ailo> Got ubuntustudio-bugs details before
[11:54] <ailo> Wonder if launchpad has a maximum limit for bug report size?
[12:11] <ailo> I'm waiting until I can confirm everything is working. Then I'll add people to the ubuntustudio-bugs group and make an announcement
[12:32] <astraljava> ailo: Cool!
[12:33] <astraljava> len-dt: Yeah that's a bit of a mystery. I'll look into it once I'm on my Studio desktop, apparently I've forgotten to import my keys on this laptop.
[13:07] <len-dt> astraljava, it's like many things, something got started and not finished. It is pretty easy to forget something.
[13:08] <astraljava> len-dt: Yeah but that branch was created already in '09. :D
[13:09] <len-dt> I think it used to just tie other packages together, but now has everything inside... or maybe it is in the middle of being split into other packages..
[13:10] <len-dt> If Scott tells us which way he was going we can finish it.
[13:17] <ailo> knome: I can't get bug notifications to be forwarded to the mail list. 1. The bugs are created in: https://launchpad.net/ubuntustudio. 2. https://launchpad.net/~ubuntustudio-bugs is a subscriber. 3. Team contact email for ubuntustudio-bugs team is: ubuntustudio-bugs@lists.ubuntu.com 4. I have already confirmed and approved everything between the bug team and the mail list, but seems like nothing is being forwarded, either to th
[13:17] <ailo> Maybe it just takes a while, I don't know
[13:18] <ailo> Launchpad seems to update slowly
[13:43] <ailo> I have misunderstood something
[13:48] <ailo> Xubuntu subscribes to Ubuntu bugs?
[14:08] <ailo> I see that the Xubuntu-bugs mail list has no mail yet
[14:09] <ailo> So far, it seems to me that bugs subscribed by a team will be sent directly to the team members
[14:09] <ailo> And thus, it is up to each member to filter the email
[14:10] <ailo> Still, it would be nice if the mail could just be redirected to the mail list directly
[14:28] <ailo> astraljava: I'm starting to wonder about what teams there are out there, and what would be a good hierarchy for them
[14:28] <ailo> Seems like the UbuntuStudio team is not connected with anything, while it has a lot of members
[14:29] <ailo> Some of the things we do should be open for anyone, like testing, and bug management
[14:30] <ailo> Might as well connect it all, and lead new people into development more easily
[14:46] <ailo> At least we should put them all down somewhere, so people can find them
[14:49] <ailo> knome: You think the only way to send the bug reports to the mail list is to create an account only for that?
[14:49] <ailo> I mean, to use that to subscribe to the bug reports, and then forward to the mail list
[14:52] <ailo> The mail list needs to be properly configured to have replies work the way they are supposed to
[14:53] <ailo> I might be missing something here, so I won't continue on that thread
[15:01] <astraljava> ailo: That's a good point. I remember one list was configured in a way that reply-to-list didn't work.
[15:03] <astraljava> ailo: I also looked at ~ubuntustudio, and it didn't really seem to do much, just a random open team.
[15:04] <ailo> astraljava: Would be good to add some info to that page, and make it easier for people to find ways to help out
[15:05] <ailo> astraljava: If you like, I can help with that. I'd like to go through all teams, and see how we could best use them
[15:05] <astraljava> Hmm... I'm not sure what that team should help out with, actually. Contributor team is ~ubuntustudio-dev.
[15:05] <ailo> I think it's just a good starting point.
[15:05] <ailo> For new people
[15:06] <ailo> But right now, it isn't providing any info. Like links to web pages, or other teams
[15:08] <astraljava> True. But then again, aren't the wiki-pages more of the informational nature?
[15:08] <ailo> I'm working on those as well
[15:09] <ailo> The tools we need, we can use. The tools we don't need, I guess we should think about shutting down. For now, I'm still investigating Launchpad teams/projects to see how things work
[15:10] <ailo> astraljava: I just wish I could do some formatting for the text, is it possible? https://launchpad.net/~ubuntustudio-bugs
[15:10] <astraljava> ailo: It's very valuable work, don't get me wrong. We should indeed review what we can and what we will be using, and for which purpose.
[15:12] <astraljava> ailo: I don't know, really. I don't see where you could even modify the overview text for starters.
[15:13] <ailo> That's the only thing that bugs me. It isn't fun to read that small text
[15:15] <ailo> I think perhaps only the launchpad mail list is good for subcribing to bugs. I'm testing that now
[15:18] <astraljava> ailo: Maybe you should ask on #ubuntu-bugs, cause the similar team ~ubuntu-bugs gets mail to ubuntu-bugs@lists.ubuntu.com.
[15:19] <ailo> good idea
[15:24] <astraljava> ailo: True that, didn't think properly.
[15:31] <ailo> Doesn't seem to work with the mail list either. 
[15:31] <ailo> I mean the launchpad one
[15:32] <astraljava> hrm... have you asked on #launchpad yet=
[15:32] <astraljava> = == ?
[15:34] <ailo> Yes, but I only get, why?
[15:34] <ailo> astraljava: Actually, it is working now
[15:34] <ailo> But, for some reason I wasn't getting duplicate bug reports
[15:35] <ailo> https://lists.ubuntu.com/archives/ubuntustudio-bugs/2012-July/thread.html
[15:38] <astraljava> Hmm... wonder why.
[15:39] <ailo> I had misunderstood. Thought they were coming from launchpad, but instead, I did have bounces@canonical.com in the headers
[15:39] <ailo> So, it is working as it should
[15:40] <ailo> Only, now the launchpad guys think it's evil to do this, cause it might help leak personal email adresses
[15:40] <astraljava> Ok.
[15:40] <astraljava> Oh?
[15:42] <ailo> Well, it's not launchpad specific. Their problem is with the fact that it is a public mail list, etc
[15:48] <astraljava> Oh, and they don't like that the bug reporter email gets out there due that mailing list?
[15:50] <ailo> Yeah. But I could agree on one thing. If you become a member of a team, you'd like to get email automatically
[15:50] <ailo> Only, you'll need to filter it yourself
[15:50] <ailo> For Ubuntu Studio bug reports, there's a header good for that: X-launchpad-bug: product=ubuntustudio;
[15:50] <ailo> Haven't found one that is team specific
[16:02] <ailo> As far as I can see, the only thing that gets included on the mail list, compared to any other mail list, is people's launchpad ID's if they choose to send a mail from Launchpad directly
[16:02] <ailo> But that doesn't really do any harm anyway
[16:05] <ailo> I do believe however, that now all launchpad emails sent to this mail list will be accepted, and I can't seem to find where I can change filtering :(
[16:11] <astraljava> You can probably do that on https://lists.ubuntu.com/mailman/admin/ubuntustudio-bugs/general, if you were given the password for that.
[16:13] <ailo> astraljava: Nope. When I sent the first email from Launchpad, i created some sort of filter. But where is it now, so I can edit it?
[16:14] <ailo> Found it
[16:15] <astraljava> Where? I'm not sure I understood correctly what you are referring to.
[16:18] <ailo> https://lists.ubuntu.com/mailman/admin/ubuntustudio-bugs/privacy/sender
[16:18] <ailo> non-member filters
[16:22] <ailo> Well, it's probably ok for now. Need to go. Another day tomorrow
[16:25] <astraljava> Sure, thanks! :)
[18:14] <ailo> Seems like I didn't go after all
[18:16] <ailo> knome: I can't see how a mail list on lists.ubuntu.com can be used wisely for bug reports. The sender is always the person who makes the bug comment, and for that to be accepted to the mail list, you need to make each sender a subscribed member, which is impossible. 
[18:18] <ailo> Neither launchpad or the mailman seems to provide enough tools to filter the messages in such a way, that it becomes possible
[18:19] <ailo> I mean to get email sent to the mail list, as well as posting it back, without any trouble
[18:38] <ailo> If one could at least filter by headers
[19:32] <astraljava> ailo: What is it that you want to achieve, really? I'm having a bit of trouble decyphering. :)
[19:39] <ailo> astraljava: The idea was to set up a ubuntustudio-bugs mail list, and we'd need to redirect bug notices from the ubuntustudio project paget at launchpad to this mail list. There are blueprints about this, and also, knome suggested (why I'm asking him).
[19:39] <ailo> Another blueprint was to create a ubuntustudio-bug team
[19:39] <ailo> Both have been created, but I can't seem to find a way to make the bug traffic work between the project and the mail list
[19:40] <ailo> Actually, I just realized
[19:42] <ailo> No. Cause the sender is always the bug reporter
[19:42] <ailo> That's where the problem lies
[19:42] <ailo> Or, the sender is always the one commenting the but
[19:42] <ailo> bug*
[19:45] <ailo> Er, no. The sender is bounces@canonical.com, aha
[19:46] <len-dt> That guy seems to be all over the place. wonder who named him/her bounces?
[19:48] <ailo> Another problem is that if you're the reporter/commenter/member of a team, you get email from launchpad directly as well
[19:48] <ailo> Would be great to just get it from the mail list
[19:52] <len-dt> ailo, you need two teams. A one member team that gets all the bug mail and a team with the members in it.
[19:53] <astraljava> ailo: I don't think that's a big problem. If someone is really interested in getting all the bug mail, [s]he'll find a way to drop the duplicates.
[19:53] <ailo> len-dt: I don't follow. There's a project where the bugs are created. Those are sent to a team called ubuntustudio-bugs
[19:53] <len-dt> The one member team would forward mail to the second team as from itself and forward members mail back as itself.
[19:53] <astraljava> len-dt: That's getting a bit complicated, IMHO.
[19:54] <len-dt> ubuntustudio-bugs should have one member. That member is fake and just forwards mail to a mail list as from them selves.
[19:54] <astraljava> ailo: Also, I'm sorry to notice it now when it's too late. But the naming convention was going towards ubuntu-studio-
[19:54] <astraljava> *
[19:54] <ailo> astraljava: Well, I followed the naming in the packages. Didn't realize until later
[19:54] <astraljava> Don't take this as critisicm towards you. We should have paid more attention.
[19:55] <ailo> Doesn't really matter too much I think
[19:55] <astraljava> At some point there was meaning to turn the IRC rooms as such, too. But the IRCC is... Oh hi jussi!
[19:56] <ailo> len-dt: The problem is that even if you are not a member of any team, you'll get bug mail from launchpad, if you commented
[19:56] <ailo> Or reported
[19:56] <ailo> Unless you specifically unsubscribed
[19:56] <ailo> Launchpad makes it that you only get one mail from them though
[19:57] <len-dt> But if you reply to the list, then it would go to LP as from the list not the user.
[19:57] <ailo> So, if you're in three teams that all get the same mail, they only send you one
[19:57] <ailo> The reply-to in headers is set with the bug adress, yes
[19:58] <ailo> There's more confusion for me as well. I think my email service is deleting duplicate mails or something
[19:59] <len-dt> ailo, some do.
[20:00]  * len-dt didn't know scott was on... 
[20:02] <len-dt> ailo, I don't seem to be getting any dupes
[20:03] <len-dt> Maybe I am not on the list though
[20:03] <ailo> len-dt: I'm the only one on the list so far
[20:04] <ailo> ubuntustudio-bugs@lists.ubuntu.com
[20:04] <ailo> I'm doing ridiculous amounts of testing with a bug report
[20:04] <len-dt> Ya I can see that.
[20:06] <len-dt> There is a new ISO today, but Bug 1020574 is not shown as fixed yet so it probably still won't install
[20:21] <ailo> I'll soon create my own project if this doesn't work, and continue playing with the mail list :P
[20:22] <ailo> Hoping this last one will be ok
[20:24] <ailo> len-dt: But I guess the ubuntustudio-bugs team could just as well be kept as a dummy team, just for forwarding bugs
[20:24] <ailo> As you proposed
[20:38] <ailo> I give up for today. And will set up a dummy project to do further testing, if nessecary
[20:39] <ailo> I think Kubuntu has a working setup. I'll ask them tomorrow
[20:55] <len-dt> ailo, astraljava, looking at the change logs on ubuntustudio-look, it appears this package acts as three packages. And is supposed to be the way it is. 
[20:56] <len-dt> So I guess I can just add the text plymouth theme as is.
[20:57] <ailo> I really have no idea about those packages, and would prefer to be ignorant :)
[20:57] <len-dt> I can see why...