2022-04-26T10:51:35 Hello team, this one is bit time pressing as we need to publish leap micro release notes https://progress.opensuse.org/issues/110080 2022-04-26T11:10:02 cboltz, ^ could you perhaps help? 2022-04-26T11:14:49 you shouldn't actually even need that iirc 2022-04-26T11:15:08 most of the release note stuff is generated as packages in build.o.o 2022-04-26T11:15:44 LCP0968[m], hmmm let me ask lukas to join 2022-04-26T11:17:34 ah I see now 2022-04-26T11:17:43 lukas did prep the needed package 2022-04-26T11:18:29 right, release notes get deployed automatically 2022-04-26T11:18:30 BUT 2022-04-26T11:18:46 so far we don't automatically sync the config file with the list of release notes from github 2022-04-26T11:18:52 so I guess that's the actual issue 2022-04-26T11:20:27 https://code.opensuse.org/heroes/salt/blob/production/f/salt/profile/documentation/files/releasenotes 2022-04-26T11:20:33 this requires the update 2022-04-26T11:20:46 then just running salt state 2022-04-26T11:20:56 right, and the file on github is in https://github.com/openSUSE/doc-o-o/blob/main/rn-config/etc/releasenotes 2022-04-26T11:21:01 give me a minute ;-) 2022-04-26T11:21:02 probably worth giving lukas access to the server anyway 2022-04-26T11:21:27 but also need to notify him not to modify it directly, but use salt :P 2022-04-26T11:22:01 or we could fetch the file from git yeah 2022-04-26T11:22:01 well, my plan is to regularly pull the file from github, it's just ETOOLONGTODOLIST ;-) 2022-04-26T11:22:10 yeah 2022-04-26T11:23:21 we should have a nicer way to script up pulling from git than writing a new bash script every time and adding it to salt 2022-04-26T11:23:44 salt it supposed to make it so we can avoid having to do that work >:D 2022-04-26T11:31:39 Hello! :) I am here regarding https://progress.opensuse.org/issues/110080 2022-04-26T11:32:27 I'm already working on it (well, on the RN part) 2022-04-26T11:33:06 the deployment is already automated, the only missing part is syncing the "releasenotes" file so that RN for new products also get deployed 2022-04-26T11:33:15 I'll sync it manually once more 2022-04-26T11:34:19 That's great to hear! Will I need to contact you about updating the "releasenote" file when there's a new product? 2022-04-26T11:35:12 the long-term goal is that we fetch the file from doc-o-o on github, it "just" needs someone with some time to do it 2022-04-26T11:35:44 feel free to watch https://progress.opensuse.org/issues/102981 which is (also) about this 2022-04-26T11:36:03 That'd be amazing. I don't really want to ask/keep a SSH access so if it can be done without that, I'm all for it. 2022-04-26T11:36:35 I will keep an eye on it. For the Leap Micro 5.2, is there anything else I need to do? 2022-04-26T11:37:22 Ah, I remember that issue. 2022-04-26T11:37:57 for Leap Micro 5.2, just wait some minutes until I have done the salt highstate ;-) 2022-04-26T11:38:07 cboltz, awesome! 2022-04-26T11:38:09 you'll still need ssh for the documentation (unless we find another solution for that - most boring would be if you push the rendered documentation to a git repo that we can just publish) 2022-04-26T11:39:42 (maybe we could also do the rendering on the server if the requirements aren't too exotic - I guess you have a script or Makefile?) 2022-04-26T11:40:48 Need daps installed, which does pull quite a lot of things: https://build.opensuse.org/package/view_file/Documentation:Auto/release-notes-leap-micro/release-notes-leap-micro.spec?expand=1 2022-04-26T11:42:36 For CI we use this container image: registry.opensuse.org/documentation/containers/containers/opensuse-daps-toolchain 2022-04-26T11:44:38 the spec you linked is about RN, does the documentation have similar requirements? 2022-04-26T11:45:14 The exact same ones AFAIK 2022-04-26T11:47:27 sounds like something we should have a look at - but not today ;-) 2022-04-26T11:49:17 No worries, let me know if you need anything else 2022-04-26T11:51:50 hmm, that's interesting - the Leap 15.4 RN got published, but not the LeapMicro RN :-/ 2022-04-26T11:52:21 fetching and unpacking the RPM worked, but they weren't copied to the docroot 2022-04-26T11:57:56 and diff'ing ~relsync/release-notes and the docroot shows several differences for 15.2 and factory, so something seems to be broken... 2022-04-26T11:58:49 lkucharczyk, can I SR the package as it is to Micro so we can get rid of SLE Micro RN? We'll resubmit it as needed later 2022-04-26T11:59:40 Unfortunately I have to leave, I'll fix this tonight 2022-04-26T12:10:08 cboltz: it's possible I have added it wrongly: https://github.com/openSUSE/doc-o-o/pull/23/files 2022-04-26T12:10:55 lkocman, I don't see a problem with that, go ahead 2022-04-26T12:26:22 lkucharczyk, oky 2022-04-26T12:26:36 lkucharczyk, I see open review in Documentation:Auto / release-notes-leap-micro 2022-04-26T12:26:44 lkucharczyk, I think you should be able to approve it :-) 2022-04-26T12:26:56 see https://build.opensuse.org/request/show/972866 2022-04-26T12:55:19 lkocman, done 2022-04-26T12:56:54 lkucharczyk, thank you 2022-04-26T13:03:50 lkucharczyk, out of blue do you know if this will be the correct path? http://doc.opensuse.org/release-notes/%{_target_cpu}/openSUSE/Leap-Micro/5.2/release-notes-openSUSE.rpm 2022-04-26T13:04:24 ah it's obvious the filename will correspond with package name ... release-notes-leap-micro.rpm 2022-04-26T13:04:47 lkocman, unfortunately I don't know, cboltz said there was some error, and maybe I've added the entry incorrectly to https://github.com/openSUSE/doc-o-o/pull/23/files 2022-04-26T13:06:59 oky I'll have a "placeholder meanwhile" can't be more broken than existing path that references 15.3 ... 2022-04-26T16:23:46 https://doc.opensuse.org/release-notes/x86_64/openSUSE/LeapMicro/5.2/ is online :-) 2022-04-26T16:24:22 for your entertainment - the problem was caused by historic reasons ;-) 2022-04-26T16:25:30 the server that still hosts doc.o.o was too old to unpack current RPMs (new compression method in Tumbleweed), therefore we do this on a new server (pinot.i.o.o) since quite a while 2022-04-26T16:26:05 and in the haproxy config, we have entries to route /release-notes/x86_64/openSUSE/Tumbleweed/ and /release-notes/x86_64/openSUSE/factory/ to pinot 2022-04-26T16:27:00 so it was not too surprising that you couldn't access the Leap Micro RN - requests were still routed to that old server that hosts doc.o.o 2022-04-26T16:31:16 now that special routing in haproxy is done for /release-notes/ so that all RN requests go to pinot 2022-04-26T16:32:38 lkocman: ^^^ 2022-04-26T16:52:55 what is left on that old server? 2022-04-26T18:16:17 AFAIK doc.o.o (except /release-notes/) and community.o.o (some old IRC lots and similar things, could be moved to narwal) 2022-04-26T19:50:19 doc-o-o is now Jekyll 2022-04-26T19:50:47 so we could reuse the jekyll building server or use the existing setup to build doc-o-o on another vm 2022-04-26T19:51:37 all of doc.o.o (including all the content of the manuals), or "just" the overview page? 2022-04-26T20:09:04 just the overview page 2022-04-26T20:09:11 the rest is still built in a way I don't understand 2022-04-26T20:10:42 from what I heard/read today, the doc team uses "daps" 2022-04-26T20:11:04 the manuals are written in XML (docbook-like) 2022-04-26T20:12:19 anyway - if you want to build the overview page on jekyll.i.o.o, we'll find ways to serve it from there (more haproxy fun) or to sync it to the right place/server 2022-04-26T20:12:46 (I'd have to check the URLs of all the manuals to see what's easier)