fedelibre / LilyDev

containers and images for LilyPond contributors
8 stars 7 forks source link

guile-devel is not installed in LilyDev container #33

Open Tobertet opened 2 years ago

Tobertet commented 2 years ago

Hi @fedelibre, first of all thanks for this magnificent tool.

I downloaded the LilyDev3 resources for running a container in Linux and it looks like everything went well.

However, when following these steps https://lilypond.org/doc/v2.23/Documentation/contributor/compiling-with-lilydev, I am having the following error: ERROR: Please install required programs: guile-devel >= 2.2

I am not sure if I am having this error because the documentation/guide is not updated or if it is a problem of the container. Should I install it manually or the documentation is out of date?

PS: Besides, I also get an error when running the command sudo shutdown (as in the readme of this repository).

fedelibre commented 2 years ago

Hi, I'm glad someone is using LilyDev. To be honest, I don't use it so the reports like yours are very valuable :-)

The latest LilyPond dev released a few days ago switched to guile2 and I haven't updated LilyDev yet. I will do it soon.

I think you can quickly fix the problem in your container by installing this package: sudo apt install guile-2.2-dev. I don't know if you'll have conflicts with guile1.8 installation...

Tobertet commented 2 years ago

Hi @fedelibre

I receive the following error when trying to install guile: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

I started using LilyDev because that is what the Lilypond documentation says. If you and other devs are developing Lilypond in a different manner I would take a look at that as well. Is it documented?

fedelibre commented 2 years ago

If you use Linux, then everything is documented. If you want to use a container in Linux, I would suggest toolbox.

LilyDev was meant mainly to provide virtual images for developers using Windows or Mac. In the last release I was not able to upload the VM image as it took too much time... Anyway, I consider the virtual machine a huge waste of time and resources nowadays, as there are better alternatives (like Docker).

I'll open a discussion on lilypond-devel when I have some time. I think I'll make the last release, then maybe archive this project and change the LilyPond documentation.

fedelibre commented 2 years ago

I receive the following error when trying to install guile: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

I've built a new image using debian bullseye and I see these errors:

‣  Running postinstall script…
usermod: group 'sudo' does not exist
chpasswd: error while loading shared libraries: libaudit.so.1: cannot open shared object file: Permission denied
/root/postinst: line 36: dpkg: command not found
/root/postinst: line 37: apt: command not found
/root/postinst: line 38: apt: command not found
/root/postinst: line 42: apt: command not found
/root/postinst: line 43: apt: command not found

The first one might explain your problem. I'll have a look at it tomorrow.

Tobertet commented 2 years ago

Alright, thank you.

Anyways, I will try to set up everything without using LilyDev as well.

Tobertet commented 2 years ago

Hello @fedelibre, did you make any progress with the new release?

If not, could you tell me what is the password for the root user? That way I can install guile-2.2-dev and try again using LilyDev.

fedelibre commented 2 years ago

Hello @fedelibre, did you make any progress with the new release?

Not much. mkosi changed a lot and I don't have time to work on it this week.

Which Linux distro do you use? Did you try to set it up? If you use Fedora, setting up a container for lilypond development is very easy.

Tobertet commented 2 years ago

In the end, I managed to install everything on my machine and I even issued already a Merge Request with the feature I needed. I use Linux Mint.

I don't think I will need the LilyDev container anymore since I already completed the setup. Apologies for mentioning you earlier.

Feel free to close this issue if think it won't be important for future users or if you are planning to archive this project.