[gentoo-user] Portage wrongly blocking an update

[Peter Humphrey]

Hello list,

Today's update of my LAN server failed to resolve a block. It said it couldn't
emerge net-proxy/squid-5.7 because of:

[blocks B ] <net-proxy/squid-5 ("<net-proxy/squid-5" is hard blocking
net-proxy/squid-5.7)
[,,,]
(net-proxy/squid-5.7:0/0::gentoo, ebuild scheduled for merge) pulled in by
net-proxy/squid required by @apps

That's all I got. No sign of what required <net-proxy/squid-5, nor of where
the < had come from.

The apps set does not specify a version, and no other package depends on
squid, so I removed it with emerge -C, then restarted the update, which ran to
completion.

It seems to me that portage should have been able to do the same, and upgrade
squid smoothly.

[Nuno Silva]

Post by Peter Humphrey
Hello list,
Today's update of my LAN server failed to resolve a block. It said it couldn't
[blocks B ] <net-proxy/squid-5 ("<net-proxy/squid-5" is hard blocking
net-proxy/squid-5.7)
[,,,]
(net-proxy/squid-5.7:0/0::gentoo, ebuild scheduled for merge) pulled in by
That's all I got. No sign of what required <net-proxy/squid-5, nor of where
the < had come from.

It came from the squid ebuild itself.

From a quick look (I might have overlooked something), it sounds like it
has to be manually uninstalled beforehand (so, precisely what you did
:-) ).

https://bugs.gentoo.org/show_bug.cgi?id=834503

Post by Peter Humphrey
The apps set does not specify a version, and no other package depends on
squid, so I removed it with emerge -C, then restarted the update, which ran to
completion.
It seems to me that portage should have been able to do the same, and upgrade
squid smoothly.

[Peter Humphrey]

Post by Nuno Silva
From a quick look (I might have overlooked something), it sounds like it
has to be manually uninstalled beforehand (so, precisely what you did
:-) ).
https://bugs.gentoo.org/show_bug.cgi?id=834503

Thanks Nuno. Interesting bug, too.

[David Rosenbaum]

Thanks

Dave

Post by Peter Humphrey
Hello list,
Today's update of my LAN server failed to resolve a block. It said it couldn't
[blocks B ] <net-proxy/squid-5 ("<net-proxy/squid-5" is hard blocking
net-proxy/squid-5.7)
[,,,]
(net-proxy/squid-5.7:0/0::gentoo, ebuild scheduled for merge) pulled in by
That's all I got. No sign of what required <net-proxy/squid-5, nor of where
the < had come from.
The apps set does not specify a version, and no other package depends on
squid, so I removed it with emerge -C, then restarted the update, which ran to
completion.
It seems to me that portage should have been able to do the same, and upgrade
squid smoothly.
--
Regards,
Peter.