Arch Linux User Repository

This package should not be marked as out of date unless it stops working. If that's the case, proving a diff to get it working is hugely appreciated. See the latest comments for potential solutions and conversation regarding the issue.

I tried to edit the file /usr/share/vscodium/resources/app/product.json and attempted to make it valid. Here's what I've found.

2 lines were missing, at lease it's what I initially thought.

"extensionEnabledApiProposals": {
"extensionSyncedKeys": {

But in fact it's the rest of the lines are duplicates.

(Sorry. I didn't make a backup of the file, so I can't diff it. It's basically a deletion of duplicates)

I don't really know or understand from where this problem could come from, so I'm not able to emit a correction to the script. I'm not sure if it affects only this package

@bkb If you are able to provide a diff to get this package working again, fixing this would be much faster. Otherwise, I'll look into it within a few days. I guess this only affects this package and not when one just installs vscodium-bin?

This package should not be marked as out of date unless it stops working. If that's the case, proving a diff to get it working is hugely appreciated. See the latest comments for potential solutions and conversation regarding the issue.

@70m4c Thanks!

The packages vscodium-bin and sed are run-time dependencies and not necessary for building. You should consider moving the entire line depends=('vscodium-bin' 'sed') into package() like this:

package() {
  depends=('vscodium-bin' 'sed')
  . . .
}

That would make it possible to build this package without vscodium-bin or sed installed, which is helpful in some situations. Please see the first two sentences in this section of the Arch Wiki: https://wiki.archlinux.org/title/PKGBUILD#depends

@silvan_rehm I just tried to reproduce, and got no error when installing fresh.

@silvan_rehm, your issue seems weird. Since we only replace lines with content, and don’t change parentheses, the original package.json sort of has to be bad. I’ll investigate more later.

Thanks!