[08:01] <alextu> cjwatson, hi
[08:02] <wgrant> alextu: Hi
[08:03] <alextu> wgrant, hi ~ I have some question about using git on launchpad.
[08:03] <wgrant> Ask away.
[08:03] <alextu> wgrant, I'm trying to manage repo on lanchpad, so created some repositories in project.
[08:04] <alextu> like this: https://code.qastaging.launchpad.net/what-project/+git
[08:05] <alextu> and the scenario will be like: some merge proposal will be request in different repository.
[08:05] <alextu> in my case repository-1 and repository-2 have one merge proposal for each.
[08:06] <alextu> wgrant, can I have some way to get a list for all merge proposals for all repositories in this project.
[08:06] <alextu> a top view for all MPs.
[08:06] <wgrant> alextu: https://code.qastaging.launchpad.net/what-project/+activereviews
[08:07] <alextu> wgrant, awesome! thanks a lot!
[08:07] <wgrant> np
[08:29] <alextu> wgrant, hi~ sorry to brother you again. Does it possible to set master branch in single repository as private? Say, the only way to commit master is merging from another branch. Just like the protection way that gerrit go with.
[08:30] <wgrant> alextu: It will never be possible to restrict reading of particular branches, but we intend to allow writes to be restricted fairly soon.
[08:30] <wgrant> But for now, if you need varying write permissions you'll need to use separate repositories.
[08:31] <alextu> wgrant, yes, restrict write permission for single branch in repository is what I need. Looking forward it :)
[08:32] <alextu> wgrant, thanks for information :)
[14:31] <mapreri> please correct me, but lp PPAs don't have a way to trigger binNMU (or whatever they're called in ubuntu), do they?
[14:34] <cjwatson> mapreri: That's (unfortunately) correct.
[14:35] <cjwatson> You have to do a new source upload.
[14:46] <mapreri> cjwatson: is there already a open bug/future request for this?
[14:46] <mapreri> otherwise i'd be happy to open one ;P
[14:47] <mapreri> RTFM here it is #245594 :>
[14:48] <cjwatson> Indeed ...
[14:52] <mapreri> well, hopefully one day or another you'll come to it, guess you've got better/more urgent/more awesome thing to do than that :) nevermind ^^
[14:57] <cjwatson> I'd like to do it, but I haven't persuaded everyone that it's a good idea, and it's a non-trivial amount of work ...
[15:01] <mapreri> can't personally get the trouble of associating +bX binary versions to the sources without +bX
[15:02] <cjwatson> It seems fine to me especially given that Debian has been doing it for years.  I'm not sure I've ever persuaded infinity. :-P
[15:12] <mapreri> s/for years/since ever/ might be more accurate :)
[15:19] <cjwatson> mapreri: I wouldn't go that far, since I remember a different form being used :)
[15:20] <mapreri> cjwatson: given the whole debian thing is actually older than me i can easily miss stuff ;)
[15:20] <cjwatson> I feel old now.
[15:20] <teward> eheheh
[15:20] <mapreri> :D
[15:20] <teward> everyone gets to feel like that at some point.  :P
[15:46] <davmor2> cjwatson: you're not allowed to feel old, Cause that means I have to feel older and I'm not up for that :P
[20:47] <costello> Dear Sirs, n00bie here. I'm trying to upload package to ppa repository ; I've done it before once and now I have new version. Packaging is quite similar to previous version.
[20:47] <costello> Now, it's being rejected because "Unhandled exception processing upload: 'ascii' codec can't decode byte 0xc3 in position 7: ordinal not in range(128)"
[20:48] <costello> looks like ascii is expected somewhere and I'm supplying utf-8 or something?
[20:48] <costello> My name has letter ä in it .. but the same naming and everything has worked for me before..
[20:51] <costello> ..ah, possibly some files I've written are in iso-8859-1 and not utf-8 because 0xc3 is exactly "ä" but in iso8859-1 .. so over my rant, I maybe may have already answered correctly to myself. Lets see :-)
[21:07] <mapreri> costello: indeed d/changelog must be utf-8 according to the debian policy
[21:09] <mapreri> "The entire changelog must be encoded in UTF-8." https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog
[21:09] <mapreri> guess you can find similar docs in the .ubuntu.com realm, but the tools are the same so it applies well enough anyway in this case
[21:32] <costello> Now I'm feeling stupid. grep $'\xc4' debian/* yields me 0 results. Is there any other place where the offending character might be coming from? Is there character-set specified in UID-strings of the GPG-key? There is letter ä also..
[21:32] <costello> err \xc3 I meant.
[21:33] <costello> anyway. I'm fairly positive that I have everything as unicode. Is there any way to try interpreting the offset numbers from error message?
[21:47] <costello> ..and lintian should whine about character set problems ; now I have lintian quiet.
[22:52] <costello> could this be a situation for a bug report .. but against what? in debian/control I had changed Standards-Version: to "3.9.5" and when I changed it back to (ancient) 3.8.4 the error message about character set went away.
[22:53] <costello> what is actually the standards-version to use with trusty? I had my sources from debian testing where standards-version is 3.9.6..
[22:57] <costello> ..seems to compile at server side too, so, for your continuous enjoyment https://launchpad.net/~operatornormal/+archive/ubuntu/classifiedads/+build/7665851