Hi, I just tried to build my container image and let osbs generate the help.1 file. It worked!
help.1
The only problem I have is that the present version deployed inside infrastructure does not support rendering tables.
Which means that this help.md page
% tools (1) Container Image Pages % Tomas Tomecek % September 11th, 2017 # NAME tools - container with all the management tools you miss in Atomic Host # DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: | Package | Summary | Executables | | --------------- | ------------------------------------------------------------------------------------------- | ---------------------------------- | | bash-completion | Programmable completion for Bash | | | bc | GNU's bc (a numeric processing language) and dc (a calculator) | /usr/bin/bc | | | | /usr/bin/dc | | bind-utils | Utilities for querying DNS name servers | /usr/bin/arpaname |
is translated to
tools (1) September 11th, 2017 tools (1) NAME tools - container with all the management tools you miss in Atomic Host DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: USAGE You should invoke this container using atomic command: $ atomic run f26/tools
(yes, the table is missing)
when it should be translated to
tools (1) September 11th, 2017 tools (1) NAME tools - container with all the management tools you miss in Atomic Host DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: ┌────────────────┬────────────────────────────────────────────┬────────────────────────────────────┐ │Package │ Summary │ Executables │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bash-completion │ Programmable completion for Bash │ │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bc │ GNU's bc (a numeric processing language) │ /usr/bin/bc │ │ │ and dc (a calculator) │ │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │ │ │ /usr/bin/dc │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bind-utils │ Utilities for querying DNS name servers │ /usr/bin/arpaname │
I used golang-github-cpuguy83-go-md2man-1.0.7-1.fc28.x86_64 to do that. Would be awesome to have that version deployed.
golang-github-cpuguy83-go-md2man-1.0.7-1.fc28.x86_64
Metadata Update from @ttomecek: - Issue tagged with: build-service
@ttomecek I'm not sure who has the ability to update OSBS. If you have a suggestion please /cc them in to the issue.
Since Adam moved to Ansible team, I was told that @kushal will be taking his place.
It would be awesome if the present OSBS deployment had all its scripts, playbooks easily available so one can easily contribute to them. (I know what needs to be done, I have no idea where to send a patch).
@ttomecek the place your are looking for is the fedora infra ansible repo
After a quick search it looks like go-md2man is present here : https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/files/osbs/buildroot-Dockerfile-production.j2 https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/files/osbs/buildroot-Dockerfile-staging.j2
Neat! That's a great pointer.
How do I request a rebuild of the buildroot image?
Edit: hm, that's not pagure, I can't send a PR there.
@ttomecek you can send a patch to the fedora infra mailing list.
Regarding the rebuild of the image, I am not sure !! There might be a playbook to do that. I am sure @puiterwijk would know :smile:
@ttomecek if you are interested in finding this information let's set up some time to talk to the infra team to find out how you can dig in and possibly help contribute a fix.
Adam maintained this system before, but he has gone to Ansible. Until his replacement arrives, I am maintaining OSBS. Please ping me on IRC or create a Fedora Infra issue.
https://pagure.io/fedora-infrastructure/issue/6556
I cancelled the meeting since @puiterwijk declined -- @dustymabe just to let you know.
Patrick and Clement described the process in comments above, so I have all the answers I needed.
@ttomecek The reason I declined is because right now, OSBS is in a maintenance-only state until Adam's replacement arrives and takes that over.
Right. In that case, we can postpone this suggestion, since it's a nice to have thing.
Patrick, any idea when the replacement arrives?
I think @cverna is the replacement
@cverna hides :) and officially starts in Jan
Welcome @cverna! :fireworks:
I assigned this to you but we understand that it won't be looked at until Jan.
Metadata Update from @smilner: - Issue assigned to cverna
@smilner Well, if atomic-reactor is installable, I can rebuild the buildroot.... But right now, we're awaiting @ttomecek to get that fixed.
@puiterwijk I looked at atomic-reactor update and it looked good :) I gave it some karma in bodhi
https://bodhi.fedoraproject.org/updates/FEDORA-2017-8a03ef01ba
Sure, unfortunately though, our buildroot is built from the stable repo. So this build will need to go to stable before it can be used in the buildroot.
So we need another 2 people giving it +1 or wait for 5 days .
@ttomecek can you submit the atomic-reactor's update to stable ? Then we should be able to rebuild the container buildroot.
It's in batched now, will promote to stable then.
@puiterwijk kindly rebuild the buildroot images so that should fix this issue.
@ttomecek can you give it a try ?
This is fixed now and can be closed
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.