| rrq | LeePen: re policykit -- since the "promotion pipeline" is not working (yet), would you mind branching to suites/beowulf for a direct build (may need a new version). | 01:13 |
|---|---|---|
| LeePen | rrq: OK. Will do. Thanks. | 08:08 |
| LeePen | rrq: I am having trouble triggering the policykit-1 build for beowulf: I have created suites/beowulf and created a beowulf tag for the build issue. auobuilder closes with "No valid suite label specified and no default suite in [jobs] section. Do nothing". What am I missing? | 14:33 |
| rrq | I'm just looking at it, and also trying to fgure that out :) | 14:34 |
| LeePen | Thanks. | 14:35 |
| fsmithred | I got a lot of those errors | 14:37 |
| fsmithred | haven't tried to build anything lately, so I don't recall for sure if it was fixed, but I think it was. | 14:37 |
| fsmithred | By giving me more permissions. | 14:38 |
| fsmithred | brb | 14:39 |
| rrq | LeePen: you built without problems for unstable? | 14:46 |
| LeePen | rrq: yes, as far as I can remember | 14:47 |
| LeePen | That was https://git.devuan.org/devuan-packages/policykit-1/issues/10 | 14:48 |
| LeePen | rrq: I had to create the beowulf tag. Is that the problem? Did I not do the right thing? | 14:49 |
| fsmithred | and you bumped the version? | 14:50 |
| LeePen | fsmithred: Yes, but the autobuilder didn't get that far, the build wasn't even triggered. | 14:51 |
| fsmithred | yeah, I didn't see a failed build | 14:52 |
| rrq | mmm and before that you tried at issue #9, but then didn't have the permission | 14:52 |
| rrq | then got those permissions | 14:52 |
| LeePen | rrq: yes and either you or Evilham (sorry can't remember which) changed them | 14:53 |
| rrq | yes.. hmm I wonder what now makes beowulf building different | 14:54 |
| LeePen | It seems not to recognise the tag I created? | 14:54 |
| LeePen | ... from the "no valid suite label" message. | 14:55 |
| rrq | did you create that on the fly upon making the issue #11 ? | 14:56 |
| rrq | (it looks perfectly fine; maybe a bit too glossy green) | 14:57 |
| LeePen | Yes. There wasn't one in the list already | 14:57 |
| rrq | that's how I didit too, for consolekit2 | 14:58 |
| LeePen | (Ah, the wrong green! :)) | 14:58 |
| LeePen | afk for a few mins. | 15:01 |
| fsmithred | after you create the label, you have to select it in the dropdown | 15:02 |
| fsmithred | (I'm reading an old conversation about the same thing) | 15:02 |
| fsmithred | still haven't read that we fixed it | 15:05 |
| rrq | do you kow where the autobuild code is? is that releasebot? | 15:08 |
| fsmithred | yeah, I think so | 15:08 |
| fsmithred | https://git.devuan.org/devuan-infrastructure/devuan-releasebot/blob/master/re | 15:12 |
| fsmithred | https://git.devuan.org/devuan-infrastructure/devuan-releasebot/blob/master/releasebot.py#L304 | 15:12 |
| fsmithred | gl.issue_close(issue.project_id, issue.issue_id, "cannot build for this issue, the reporter needs at least master permissions") | 15:12 |
| fsmithred | rrq ^^^ | 15:13 |
| rrq | the complaint comes from line 302 | 15:14 |
| fsmithred | I pulled that from irc log, date is Jan, but pretty sure it's not this year. | 15:15 |
| rrq | the target suite is filtered at line 295, using a config from somewhere... | 15:16 |
| fsmithred | also pretty sure it wasn't solved | 15:16 |
| fsmithred | search for 'valid suite' in #devuan-dev logs and it comes up about 6 times over the last year or two | 15:17 |
| rrq | seems the actual config is not in git; have to dive into the host... | 15:18 |
| rrq | but why is policykit different from consolekit wrt available suites? | 15:20 |
| rrq | hmm releasebot probably runs on dak or something :( | 15:21 |
| Evilham | Yup | 15:23 |
| Evilham | I always wanted to take a look at that config, but couldn't | 15:23 |
| rrq | ah; so if "beowulf" is in "mastersuites" but not in "suites" then I can build for beowulf while LeePen can't | 15:26 |
| rrq | releasebot:290-295 | 15:26 |
| rrq | that'd explain the permission needs | 15:27 |
| rrq | LeePen: I upped your permissions, so please try again; maybe autobuild will behave | 15:32 |
| rrq | "upped" = swenglish for "raised" | 15:34 |
| fsmithred | we use that word in english, too | 15:36 |
| rrq | btw the consolekit fix was good; now the debian-installer mini.iso happily installs grub | 15:46 |
| fsmithred | cool! | 15:47 |
| LeePen | rrq: sorry, still the same. No build triggered "No valid suite label..." | 15:49 |
| rrq | ok. I'll try triggering it... | 15:52 |
| rrq | (the dark green is nice :)) | 15:52 |
| rrq | ah. hmm. same response. | 15:54 |
| LeePen | golinux will be proud of us ;) | 15:54 |
| rrq | mmm I'm not the issue author... trying again | 15:57 |
| rrq | that one worked. | 15:59 |
| LeePen | rrq: great, thanks. Any idea what is going on? | 16:00 |
| * Evilham 's guess is: black magic, that's what feeds computers: if you short circuit them, the black smoke escapes proving that it's black magic </silliness> | 16:00 | |
| rrq | I was thinking that probably the issue author needs "master" permissions, but your idea seems better :) | 16:01 |
| rrq | seems "unstable" is in the "suites" list for releasebot, while "beowulf" is in the "mastersuites" list | 16:02 |
| rrq | that "master permissions" is probably flagged in the devuan-project project | 16:03 |
| rrq | hmm would again need sighting of the magic config... | 16:06 |
| fsmithred | libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 all need to move from ceres to beowulf for the new policykit-1 to install. | 17:00 |
| LeePen | Centurion_Dan rrq: what do you think is the best way to resolve the policykit-1 confusion in beowulf? Centurion_Dan it seems as if you managed to migrate the policykit-1-0.105-25+devuan3 package itself, but all the other packages from the same source are still at +devuan1. Are you abel ti migrate the others in dak? | 20:03 |
| LeePen | able to! | 20:03 |
| andy5995 | This is where I'm at with the maintainer docs https://git.devuan.org/devuan/devuan-maintainers/issues/28#note_14184 | 21:08 |
| andy5995 | rrq: could you add the link to the package maintainer docs in this forum post https://git.devuan.org/devuan/devuan-maintainers/issues/28#note_14184 | 21:24 |
| andy5995 | oops, wrong link.. a moment... | 21:25 |
| andy5995 | https://dev1galaxy.org/viewtopic.php?pid=1380#p1380 | 21:25 |
| andy5995 | The link to add is https://git.devuan.org/devuan/devuan-maintainers/blob/master/README.md | 21:26 |
| fsmithred | andy5995, rrq should be sleeping right now. I took care of it. | 21:33 |
| golinux | No. It's not ready to go on the the forum in that state, | 21:37 |
| fsmithred | wnat me to change it to "Link coming soon"? | 21:39 |
| fsmithred | or do you want me to put the d1h link back? | 21:40 |
| fsmithred | nm, I reverted it. | 21:42 |
| golinux | d1h is dead | 21:44 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!