Arch Linux User Repository

I have disabled the v up command, as it can break the installed package. v up changes the files in the resulting package after installation, meaning Pacman can't properly track its contents anymore.

I get this error after running v up it seemed to make vlang binary disappear.

How do I re-install it?

Total Installed Size:  15.34 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                   [###################################################################] 100%
(1/1) checking package integrity                                                                                 [###################################################################] 100%
(1/1) loading package files                                                                                      [###################################################################] 100%
(1/1) checking for file conflicts                                                                                [###################################################################] 100%
error: failed to commit transaction (conflicting files)
vlang: /usr/lib/vlang/cmd/tools/vdoc exists in filesystem
Errors occurred, no packages were upgraded.

the vlang-git aur didn't compile for me.

@lberrymage: yeah, I realized my patch didn't actually work, so I deleted my comment. I should've tested it better before posting anything.

I'm not a vlanger yet, I've been meaning to get into this language as it looks promising, but I don't think I know enough to actually help with this issue, sorry :(
If I happen to have an idea though, I'll test it and share here :)

@1ace The problem I'm currently experiencing is related to installing the markdown module, which is required to build vdoc.

If you already have it installed (in ~/.vmodules/markdown, it's super easy to update to 0.2. If you don't have it installed, the markdown module doesn't install with either cgen error while compiling vpm (nothing else, even in verbose mode) or http.fetch: invalid url while installing the markdown module with vpm. The end result is that if you already have vlang installed (and most likely the markdown module), only a .SRCINFO/pkgsums/pkgver etc. change is required. Otherwise, vdoc can't compile.

I've been busy over Christmas and all, so I should be able to give more attention to this in coming days.

If you happen to come up with a patch and/or suggestions I'll be glad to accept either. Thank you for offering.

0.2 is now out (and I can't re-flag as out of date ^^')

I'm also happy to help with packaging if you want :)

I'll get around to updating to 0.1.30 this Sunday or Monday - thank you for the notice @sunng.

Update: Packaging issues concerning v's compilation process kindly request your further patience :).

Amazing, thanks!

@kseistrup The issue should be fixed for everyone now.