[Request] micro-nightly

[davidusrex]

What software are you requesting to be packaged? micro https://github.com/zyedidia/micro

Describe the motivation A clear and concise description of why you want this package. Would this provide value to other users? The package in Fedora is two minor versions behind (but is still being built for current Fedora versions). This is not a major problem in and of itself, but... upstream seems to have stopped tagging releases for the time being, with the last tagged release being 2.0.13 from October 2023. There have been 243 commits since then and development has been very active. So the Fedora package is actually more than a year out of date. I've come up with the idea of packaging a micro-nightly version so as not to conflict with the Fedora package. Upstream actually does have a "nightly" tag which is a snapshot of the repo taken every day at midnight.

Additional context I'll try to package it myself, just wanted to make sure it was okay to package a different version of an existing package.

[linear[bot]]

FYRA-29 [Request] micro-nightly

[madonuko]

You have my approval, go ahead and thanks in advance for the work!

[madonuko]

Hey, just checking up on the progress; do you need help or do you want me to just package this?

[davidusrex]

Hi mado, sorry that it's taken me so long to come back with a PR. It took me a while to understand how RPM macros work and the packaging guidelines for packages written in go are exceptionally onerous.

I think I've written the specfile correctly and I'm fine with opening a PR right now, but the package fails to build in mock. It's specifically failing here:

mock    |  # /usr/bin/systemd-nspawn -q -M 9f12218e72c74fd3a9624ff26da5599d -D /var/lib/mock/terra-40-x86_64/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.dlap4jly:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --setenv=CCACHE_DIR=/var/tmp/ccache --setenv=CCACHE_UMASK=002 --setenv=CCACHE_COMPRESS=on --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -ba --noprep  --target x86_64 /builddir/build/SPECS/micro-nightly.spec'

[madonuko]

Ah… could you either send the full logs (using gist or pastebin or something) or just PR the spec files? The CI will automatically run a build and we could see why this happens.