=== scott-kernel-bui is now known as scott-kernel [03:21] persia, i'm having the following lintian error but i am unsure how serious it is given the context [03:21] section-area-mismatch [03:21] i believe this kernel is going into the universe repository [03:22] The package shouldn't know which component it will end up in. [03:22] but doesn't the control file dictate this? in Section: [03:23] if i leave Section: as devel or admin it builds without errors [03:23] Ah, right. You have "universe/foo" in Section:. It should be "foo". [03:23] No, it's dictated by the archive overrides. [03:23] right, but here's the weird part...the kernel builds with universe/devel giving errors and devel not giving errors [03:23] meta is the inverse, where universe/devel doesn't give errors and devel does :/ [03:24] ah, "builds" = debuild -S -sa [03:25] No control file should ever specify the component. [03:25] What errors do you get from the meta? [03:28] sorry, phone call from father [03:28] but i'm back and getting error [03:29] E: linux-meta-lowlatency source: section-area-mismatch Package linux-headers-lowlatency [03:30] E: linux-meta-lowlatency source: section-area-mismatch Package linux-image-lowlatency [03:30] E: linux-meta-lowlatency source: section-area-mismatch Package linux-lowlatency [03:30] E: linux-meta-lowlatency source: section-area-mismatch Package linux-headers-lowlatency-pae [03:30] E: linux-meta-lowlatency source: section-area-mismatch Package linux-image-lowlatency-pae [03:30] E: linux-meta-lowlatency source: section-area-mismatch Package linux-lowlatency-pae [03:30] W: linux-meta-lowlatency source: native-package-with-dash-version [03:30] i'm guessing the last warning isn't a show stopper and have decided to ignore it for the moment as i can't find a way to fix it [03:31] persia, hmmm, i just noticed part of the problem now, it seems that the control file is being built and the packages that are added are being assigned as Section: universe/devel which the package defined in the control.stub is Section: devel [03:32] hah! You found the culprit. [03:32] i presume that i need to look in the rules file then [03:32] grep -rin the source for "universe/devel" and change that to "devel" and the error should go away. [03:32] I don't believe it's in the rules file, but yeah, if you want to *understand* why it's "universe/devel", the rules file is a good place to start. [03:33] i forget (and tired after six hours of driving today), are the quotes necessary for grep [03:36] No, except when you have something you need to quote. [03:36] To put that differently, some strings are interpreted by the shell before grep even sees them [03:36] So, for example, `grep \\ myfile` and `grep '\' myfile` are the same. [03:37] grep -rin universe/devel [03:37] is that correct? because it seems to be hanging up [03:37] Neither really does what you want, because grep then also parses the string. So to really search for literal '\', you need \\\\ or '\\'. [03:37] `grep -rin universe/devel .` [03:37] It's waiting for you to give it input, since you didn't specify a location for it to search. [03:38] Ctrl-D will tell it you're done giving it input, and it will exit. [03:38] The final '.' in my command is the location (current directory) [03:38] okay, found it [03:40] oh, was i correct to ignore the 'native-package-with-dash-version' warning? [03:41] Yeah, go ahead and ignore that. [03:41] There's reasons it needs the dash, and if I remember correctly, reasons it needs to be native. [03:45] persia, https://launchpad.net/~slavender/+archive/broken [03:46] linux-lowlatency should be fine because i had already removed the universe/* and the only warning or error was the native-package-dash warning [03:46] linux-meta is uploading again, ppa1 was wrong but ppa2 (uploading still) will be correct (again, less the native-package-dash warning) [03:47] i'm super tired and going to bed [03:47] I'm grabbing ~ppa2 for the meta? [03:47] persia, aye [03:48] OK. I have linux-lowlatency_3.0.0-5.6~ppa1.dsc and linux-meta-lowlatency_3.0.0-5.6~ppa2.dsc [03:48] Would you prefer me to review, fix, and upload or review, complain, wait for you? [03:48] yes, that should be correct [03:48] be gentle, i expect you to point out lots and lots 'o stuff that i'll need to fix :P [03:53] So, which way do you want it? [03:53] I can complain a bundle, and you can go fix it. [03:54] Or I can upload the package, fixing along the way, and you can see what I changed (and I'll be happy to explain each change) [03:57] But do tell me which you want, as it affects when I can do things. [03:57] Note that I'm not doing anything too soon, as I'm supposed to leave for a concert in the next (short) while. [11:52] persia, i suppose it would be easier for you to fix it, however, i expect that it would be a better educational experience if i fixed it [11:53] so, i think you probably should complain a bundle and let me fix it [12:01] and i do feel responsible for it [12:04] ailo_, ping [12:06] oh, i see the linux-meta didn't build in my ppa either :( [14:39] ScottL, Sounds like a plan. I'll dig into it, and give you a list. [15:09] persia, did i disappoint you? [15:09] No. [15:10] I haven't looked at it yet, because I've been away from my computer, and I'm not looking at it now because I'm just checking backscroll before sleeping. [15:10] I don't really care which way you'd prefer to deal with the package: the key is that it is the way you believe you learn best. [15:10] Some folk prefer to have their problems identified, with suggested ways to find solutions. Other folk prefer to have solutions demonstrated, with explanations. [15:11] As far as I can tell the choice between the two seems to be completely independent of most demographic variables. I have a suspicion that it's a combination of what their caretakers did when they were three and how they felt about their caretakers. [15:12] (but this could be completely wrong)