| 1 |
On 2023-01-15, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> Hello list, |
| 4 |
> |
| 5 |
> Today's update of my LAN server failed to resolve a block. It said it couldn't |
| 6 |
> emerge net-proxy/squid-5.7 because of: |
| 7 |
> |
| 8 |
> [blocks B ] <net-proxy/squid-5 ("<net-proxy/squid-5" is hard blocking |
| 9 |
> net-proxy/squid-5.7) |
| 10 |
> [,,,] |
| 11 |
> (net-proxy/squid-5.7:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 12 |
> net-proxy/squid required by @apps |
| 13 |
> |
| 14 |
> That's all I got. No sign of what required <net-proxy/squid-5, nor of where |
| 15 |
> the < had come from. |
| 16 |
|
| 17 |
It came from the squid ebuild itself. |
| 18 |
|
| 19 |
From a quick look (I might have overlooked something), it sounds like it |
| 20 |
has to be manually uninstalled beforehand (so, precisely what you did |
| 21 |
:-) ). |
| 22 |
|
| 23 |
https://bugs.gentoo.org/show_bug.cgi?id=834503 |
| 24 |
|
| 25 |
> The apps set does not specify a version, and no other package depends on |
| 26 |
> squid, so I removed it with emerge -C, then restarted the update, which ran to |
| 27 |
> completion. |
| 28 |
> |
| 29 |
> It seems to me that portage should have been able to do the same, and upgrade |
| 30 |
> squid smoothly. |
| 31 |
|
| 32 |
-- |
| 33 |
Nuno Silva |
Archives