Yaourt: orphans not deleted?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I just noticed an unexpected (at least for me) behavior of yaourt. I wanted to clean my system from orphans:
yaourt -Qtd
Which should query for orphans and ask for deletion according to man yaourt:
-t, --unrequired
Filter output to packages not required by any currently installed package.
With -d, yaourt list all real orphans and ask for deletion.
However, after a normally unnecessary checkup with yaourt -Syyu --aur I got this message:
:: Synchronizing package databases...
core 137,8 KiB 984K/s 00:00 [######################] 100%
extra 1772,5 KiB 4,33M/s 00:00 [######################] 100%
community 4,4 MiB 5,34M/s 00:01 [######################] 100%
multilib 178,7 KiB 58,2M/s 00:00 [######################] 100%
qtemu : Orphan
Foreign packages: 27 / 27
Why does yaourt -Syyu --aur tells me that qtemu is an orphan when I have deleted orphans via yaourt -Qtd before?
Additionally, I did not notice the Foreign packages information before. What is this about? After checking dependencies with yaourt -Qs --depends qtemu in order to ensure it can be safely deleted, I did yaourt -Rns qtemu to get rid of it.
After deleting qtemu yaourt now tells me Foreign packages: - 26 / 26, thus qtemu was one of these "foreign packages"?
package-management manjaro yaourt
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
asked Nov 28 '17 at 6:30
daniel451
3883516
add a comment |Â
up vote
0
down vote
favorite
I just noticed an unexpected (at least for me) behavior of yaourt. I wanted to clean my system from orphans:
yaourt -Qtd
Which should query for orphans and ask for deletion according to man yaourt:
-t, --unrequired
Filter output to packages not required by any currently installed package.
With -d, yaourt list all real orphans and ask for deletion.
However, after a normally unnecessary checkup with yaourt -Syyu --aur I got this message:
:: Synchronizing package databases...
core 137,8 KiB 984K/s 00:00 [######################] 100%
extra 1772,5 KiB 4,33M/s 00:00 [######################] 100%
community 4,4 MiB 5,34M/s 00:01 [######################] 100%
multilib 178,7 KiB 58,2M/s 00:00 [######################] 100%
qtemu : Orphan
Foreign packages: 27 / 27
Why does yaourt -Syyu --aur tells me that qtemu is an orphan when I have deleted orphans via yaourt -Qtd before?
Additionally, I did not notice the Foreign packages information before. What is this about? After checking dependencies with yaourt -Qs --depends qtemu in order to ensure it can be safely deleted, I did yaourt -Rns qtemu to get rid of it.
After deleting qtemu yaourt now tells me Foreign packages: - 26 / 26, thus qtemu was one of these "foreign packages"?
package-management manjaro yaourt
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
asked Nov 28 '17 at 6:30
daniel451
3883516
1
The package was likely dropped from the Manjaro repos to the AUR (as it was in Arch), thus moving it into the "foreign" category, and presumably also orphaning it from whatever official package it was a depends of.
– jasonwryan
Nov 28 '17 at 6:35
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I just noticed an unexpected (at least for me) behavior of yaourt. I wanted to clean my system from orphans:
yaourt -Qtd
Which should query for orphans and ask for deletion according to man yaourt:
-t, --unrequired
Filter output to packages not required by any currently installed package.
With -d, yaourt list all real orphans and ask for deletion.
However, after a normally unnecessary checkup with yaourt -Syyu --aur I got this message:
:: Synchronizing package databases...
core 137,8 KiB 984K/s 00:00 [######################] 100%
extra 1772,5 KiB 4,33M/s 00:00 [######################] 100%
community 4,4 MiB 5,34M/s 00:01 [######################] 100%
multilib 178,7 KiB 58,2M/s 00:00 [######################] 100%
qtemu : Orphan
Foreign packages: 27 / 27
Why does yaourt -Syyu --aur tells me that qtemu is an orphan when I have deleted orphans via yaourt -Qtd before?
Additionally, I did not notice the Foreign packages information before. What is this about? After checking dependencies with yaourt -Qs --depends qtemu in order to ensure it can be safely deleted, I did yaourt -Rns qtemu to get rid of it.
After deleting qtemu yaourt now tells me Foreign packages: - 26 / 26, thus qtemu was one of these "foreign packages"?
package-management manjaro yaourt
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
asked Nov 28 '17 at 6:30
daniel451
3883516
I just noticed an unexpected (at least for me) behavior of yaourt. I wanted to clean my system from orphans:
yaourt -Qtd
Which should query for orphans and ask for deletion according to man yaourt:
-t, --unrequired
Filter output to packages not required by any currently installed package.
With -d, yaourt list all real orphans and ask for deletion.
However, after a normally unnecessary checkup with yaourt -Syyu --aur I got this message:
:: Synchronizing package databases...
core 137,8 KiB 984K/s 00:00 [######################] 100%
extra 1772,5 KiB 4,33M/s 00:00 [######################] 100%
community 4,4 MiB 5,34M/s 00:01 [######################] 100%
multilib 178,7 KiB 58,2M/s 00:00 [######################] 100%
qtemu : Orphan
Foreign packages: 27 / 27
Why does yaourt -Syyu --aur tells me that qtemu is an orphan when I have deleted orphans via yaourt -Qtd before?
Additionally, I did not notice the Foreign packages information before. What is this about? After checking dependencies with yaourt -Qs --depends qtemu in order to ensure it can be safely deleted, I did yaourt -Rns qtemu to get rid of it.
After deleting qtemu yaourt now tells me Foreign packages: - 26 / 26, thus qtemu was one of these "foreign packages"?
package-management manjaro yaourt
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
asked Nov 28 '17 at 6:30
daniel451
3883516
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
edited Nov 28 '17 at 6:31
jasonwryan
47k14127176
47k14127176
asked Nov 28 '17 at 6:30
daniel451
3883516
asked Nov 28 '17 at 6:30
daniel451
3883516
asked Nov 28 '17 at 6:30
daniel451
3883516
3883516
1
The package was likely dropped from the Manjaro repos to the AUR (as it was in Arch), thus moving it into the "foreign" category, and presumably also orphaning it from whatever official package it was a depends of.
– jasonwryan
Nov 28 '17 at 6:35
add a comment |Â
1
The package was likely dropped from the Manjaro repos to the AUR (as it was in Arch), thus moving it into the "foreign" category, and presumably also orphaning it from whatever official package it was a depends of.
– jasonwryan
Nov 28 '17 at 6:35
1
1
The package was likely dropped from the Manjaro repos to the AUR (as it was in Arch), thus moving it into the "foreign" category, and presumably also orphaning it from whatever official package it was a depends of.
– jasonwryan
Nov 28 '17 at 6:35
The package was likely dropped from the Manjaro repos to the AUR (as it was in Arch), thus moving it into the "foreign" category, and presumably also orphaning it from whatever official package it was a depends of.
– jasonwryan
Nov 28 '17 at 6:35
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407425%2fyaourt-orphans-not-deleted%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
The package was likely dropped from the Manjaro repos to the AUR (as it was in Arch), thus moving it into the "foreign" category, and presumably also orphaning it from whatever official package it was a depends of.
– jasonwryan
Nov 28 '17 at 6:35