[13:26] wxl: can you file a bug please? I won't be able to look until at least tomorrow and will probably have forgotten about it otherwise [22:40] Hi, I got this error: "Rejected: sam_0.13-1.dsc: Unknown section '-'" - it makes no sense, there's no '-' section [22:42] dsi_: might help us if you pastebin the dsc [22:43] I mean, help us help you [22:44] https://pastebin.com/CbRG8qh9 [22:51] might be the Package-List 'unknown' [22:51] Package-List: [22:51] sam deb unknown optional arch=amd64 [22:56] I have no idea from where the "unknown" is coming from [22:56] working with launchpad is very painful [22:59] I don't think this is a launchpad issue, more packaging but whatever [23:00] you're welcome to try get your package landed in Debian, and from that I think will sync across to Ubuntu [23:02] you're also welcome to build the packages yourself, set up your own APT archive and host it yourself [23:04] thanks, that was very helpful \s [23:11] dsi_: You probably forgot a Section field in either the Source or one of the Package stanzas in debian/control [23:11] dsi_: lintian will warn you about this sort of thing locally; it's in no way Launchpad-specific. [23:13] those fields are in the control file, lintian only shows me warnings [23:15] Can you pastebin your debian/control? [23:17] https://gitlab.com/sam-resources/sam/blob/master/sam_0.13-1/DEBIAN/control that? [23:17] unless a modified version was used [23:18] That's a binary control file, not sure why it's in version control [23:27] that's a different thing from hours ago [23:29] https://pastebin.com/aVnEH5sY [23:29] this debian thing is way too overcomplicated [23:33] dsi_: How did you build the package? That control file shouldn't have produced that .dsc. [23:34] debuild -S -sa [23:34] (but you also probably just want Section: utils, not Section: contrib/utils) [23:34] the documentation is pure gold... [23:34] The "unknown" in "sam deb unknown optional arch=amd64" in the .dsc suggests there was no section field. [23:36] dsi_: We're more likely to be able to help if we can see exactly what you're trying. [23:36] e.g. the source tree that you're using, or both the .dsc and the .tar.gz [23:36] And the documentation you're following [23:37] I started to fix the warnings and now it says that it accepted the package [23:39] Warnings are generally there for a reason :) [23:39] Some checks that lintian may only have as a warning may be enforced by archive management software like LP and dak. [23:40] Yeah, but it seems like a warning wasn't a warning but an error [23:40] Error: signing key fingerprint does not exist [23:41] Where did you get that/ [23:41] add-apt-repository -y ppa:istvand/sam [23:42] dsi_: Your PPA's signing key is only generated once you upload the first package, so it can take a few minutes to show up (and it takes a few minutes for uploaded packages to appear there anyway) [23:44] The key is there now [23:45] I still get the same error [23:47] weird, now it starts an apt update log and says "403 Forbidden [IP: 91.189.95.83 80]" [23:49] On which file? That's not very possible. [23:49] Unless you have a weird proxy [23:50] i have no proxy [23:50] I ran add-apt-repository ppa:istvand/sam [23:50] then pressed Enter because it asked me to [23:50] huh, something very weird is going on, let me see. [23:50] then it tried to download the repo [23:52] dsi_: Ah, it wasn't quite published yet. It won't 403 any more. [23:52] perfect! [23:53] thanks! [23:53] Just a bit of a setup process for a new PPA, which can take a few minutes.