[02:35] <andersk> This Mercurial import failed with a strange error; anyone know why? https://code.launchpad.net/~edwardzyang/urweb/default
[02:35] <andersk> “RuntimeError: if we move self._source_infos, then we need to change all of the index pointers as well.”
[06:51] <crass> I keep getting a "Could not be uploaded correctly" failure, for a recipe build. Here's the log: https://launchpadlibrarian.net/111260367/buildlog.txt.gz
[06:52] <crass> I don't see any errors, just some warnings building the source package, but I don't think they are causing the failure
[06:53] <crass> unless source packages need the newer 3.0 format... but I don't think they do
[06:54] <wgrant> crass: If you click on the build link you'll see a separate link to the upload loag
[06:54] <wgrant> log
[06:55] <wgrant> https://launchpadlibrarian.net/111260396/upload_3989462_log.txt
[06:55] <wgrant> INFO Processing upload wader_0.5.12+svn20120727+r842-0~r843~crass~quantal1_source.changes
[06:55] <wgrant> INFO Upload was rejected:
[06:55] <wgrant> INFO 	wader_0.5.12+svn20120727+r842-0~r843~crass~quantal1.dsc: Unknown section '-'
[06:55] <wgrant> INFO 	wader_0.5.12+svn20120727+r842-0~r843~crass~quantal1.tar.gz: Unknown section '-'
[06:55] <wgrant> INFO 	Further error processing not possible because of a critical previous error.
[06:56] <wgrant> http://bazaar.launchpad.net/~crass/wader/rename-debian/view/head:/debian/control
[06:56] <wgrant> There's no Section field in the source stanza
[06:56] <crass> thanks wgrant, hadn't noticed that. So is that referring to the '-' in the version part of the file name?
[06:57] <crass> oh, ok, got it
[06:57] <wgrant> It's referring to the Files section of the changes file that debuild produces from debian/control and that you'd normally upload
[06:57] <wgrant> In this case it's generated automatically, but if you build the package locally you should see the issue in the .changes file
[06:58] <wgrant> To fix, just add the Section field to the Source stanza
[07:01] <crass> it would be nice to have the upload log linked incase of an upload error, as oppose to the buildlog (or even better have it in one log)
[07:02] <wgrant> They have to be separate logs, but indeed it should be linked.
[07:02] <crass> they have to be because they are on separate machines?
[07:02] <wgrant> Pretty much.
[07:03] <wgrant> (upload failures like this are pretty rare, so it wasn't a priority to shown the log prominently)
[12:28] <jonathanj> hrm, is something up with launchpad at the moment? trying to do a bzr merge i get "Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist."
[12:28] <jonathanj> and push (from another machine) seems to either be taking a really long time or is doing nothing (i'm not sure how to tell which of those it is)
[12:30] <jelmer> jonathanj: we're looking into it
[17:09] <abentley> sinzui: AIUI, there are 5 information types.  Why not six?  (i.e. adding "Public proprietary")  Or four?  (i.e. removing "Public Security")
[17:53] <sinzui> abentley: Each information type represents who owns the data and how we expect to to change or not change.
[17:53] <sinzui> abentley: we expect private security to become public security
[17:53] <sinzui> proprietary will never be public
[17:54] <sinzui> private could be public if the personal information is scrub from the bug or branch
[17:54] <sinzui> abentley: and we might need 6 or 7 if PES believe there are several kinds of proprietary
[17:55] <sinzui> I am have anxiety attacking over the very matter
[17:55] <abentley> sinzui: Well, there are cases like Staroffice -> Openoffice and the open-sourcing of Netscape.
[17:56] <abentley> sinzui: they may  not be common enough to worry about, though.
[17:56] <sinzui> abentley: product strategy did that to all webapp projects 7 days ago
[17:59] <sinzui> abentley: They had to decide if they could reveal the entire commit history of the repository and decide if the bugs could be seen by other people