Arch Linux

vicentereyes

Member

Registered: 2017-02-17

Posts: 5

[SOLVED] package with a 3 day lifespan

I have a package (libcloudproviders) don't remember installing, and I'm not the only one who has it. The following two forum threads post their package list and you can find libcloudproviders by Ctrl-F-ing:
https://bbs.archlinux.org/viewtopic.php?id=235692
https://bbs.archlinux.org/viewtopic.php?id=235771
the curious thing is it doesn't exist:
https://www.archlinux.org/packages/?sor … dproviders
https://aur.archlinux.org/packages/?K=libcloudproviders

Anyway. According to pacman.log I installed it March 28th and it was installed as a dependency for another package.

Does this happen frequently?

Last edited by vicentereyes (2018-04-02 00:54:01)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,218

Re: [SOLVED] package with a 3 day lifespan

It was added in November. A package existing for 4+ months is nothing shocking or extreme.

vicentereyes

Member

Registered: 2017-02-17

Posts: 5

Re: [SOLVED] package with a 3 day lifespan

Now that I think about it, I reinstalled arch the 28th, which makes my original post really stupid. Thanks

dakota

Member

Registered: 2016-05-20

Posts: 357

Re: [SOLVED] package with a 3 day lifespan

Does this happen frequently?

I don't know.

According to my pacman log, it was installed on my system on 3/24 as a result of 'pacman -Syu'. I noticed it today when running 'pacman -Qm'.  I removed it with 'pacman -Rns $(pacman -Qtdq)'.

It may not be shocking or extreme, but it does seem weird.

---

"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,091

Re: [SOLVED] package with a 3 day lifespan

TLDR:  GTK3 is to blame

Libcloudproviders enters the stage :

https://git.archlinux.org/svntogit/pack … bddb1c2d52

and exits
https://git.archlinux.org/svntogit/pack … 82dd3c7712

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky