search

pop-os / shop

Pop!_Shop
GNU General Public License v3.0
91 stars 19 forks source link

Pop Shop does not properly install deluge #260

Open cwestkaemper opened 3 years ago

cwestkaemper commented 3 years ago

Pop OS 20.10

deluge: Installed: 2.0.3-3 Candidate: 2.0.3-3 Version table: *** 2.0.3-3 500 500 http://us.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu groovy/universe i386 Packages 100 /var/lib/dpkg/status

When installing deluge from the pop shop, some packages required for standalone client mode are not installed.

Remove deluge + any other torrent software. Run apt autoremove. Install the Ubuntu deb of deluge from the pop shop. Launch deluge, and it will force you to run deluge in "thin client mode" due to missing packages. Installing from "sudo apt install deluge" always results in a proper, complete install that runs in standalone mode by default. This can be verified by opening edit->prefrences and checking if the "standalone" button is checked.

Deluge should come with the same packages you get from apt install deluge. These packages enable the on-by-default standalone client mode that the vast majority of users will use exclusively.

NOTES If you run apt install deluge after installing from the pop shop, the following packages are installed-

deluge libboost-python1.71.0 libtorrent-rasterbar10 python3-libtorrent

After installing them, deluge works as intended.

I suspect the lack of these packages is what is causing the issue.

bflanagin commented 3 years ago

Seems to be an issue with the package and the lack of appstream data for the other deluge packages. Unfortunately we don't have any control over these packages.

On closer inspection the Deluge client that is available in the Pop!_Shop does mention (albeit poorly) that it only installs what is required to create a thin client.

Screenshot from 2021-03-02 11-30-39

We'll keep this ticket open for further consideration.

cwestkaemper commented 3 years ago

So should I report this to the ubuntu maintainer then?

cwestkaemper commented 3 years ago

Well, since this only effects the software center iteration, it's not the problem of the package maintainer (I think). So, who would be responsible for the upstream issue?