+folks with Linux packaging knowledge, FYI.

eberapa mesin Linux memiliki file yang dihasilkan otomatis ini di direktori root, yang hampir pasti berasal dari script paket chrome-remote-desktop untuk menyiapkan entri sources.list.d APT.

$ Cat /chrome-remote-desktop.list
### FILE INI secara otomatis dikonfigurasi ###
# Anda dapat komentar keluar entri ini, tapi modifikasi lain mungkin akan hilang.
deb [lengkungan = amd64] http://dl.google.com/linux/chrome-remote-desktop/deb/ utama stabil

Beberapa mesin Linux memiliki file yang dihasilkan otomatis ini di direktori root, yang hampir pasti berasal dari script paket chrome-remote-desktop untuk menyiapkan entri sources.list.d APT.

$ Cat /chrome-remote-desktop.list
### FILE INI secara otomatis dikonfigurasi ###
# Anda dapat komentar keluar entri ini, tapi modifikasi lain mungkin akan hilang.
deb [lengkungan = amd64] http://dl.google.com/linux/chrome-remote-desktop/deb/ utama stabil

I'm not sure what happened here, but best guess is somewhere during the fix for  Issue 663069 , the chromoting package scripts ended up in a bad state. I found a system where that file was in the root dir (dated Nov 15th), and after removing it and then purging and reinstalling the chromoting package, the file is back in /etc/apt/sources.list.d/ as expected, so it seems the current release is OK.

It might be worth adding an extra check for this condition in the chromoting packaging scripts, and then forcing the file to be recreated in the right place, since I think it won't "fix itself" unless the user does a complete purge/reinstall like I did.

Lambros, can this be closed now or do you think we need to add something to remove that file?