Re: vim on powerpc

Hi,

that's just unstable being unstable, unrelaxed to other packages. vim and 
vim-common are built from the same source package, so they update 
together, but if the package fails to build, the vim package will fall 
behind because vim-common is shared between architectures.

IIRC there is a failing testcase that breaks a lot of architectures. 
Quick fix is to build the package yourself in pbuilder with 
DEB_BUILD_OPTIONS=nocheck.

   Simon

12 Oct 2025 03:32:20 Stan Johnson <[email protected]>:

> Hello,
>
> After upgrading to the latest Debian SID (systemd) on a PowerBook G3 
> Wallstreet, vim was deleted. I did not run into this issue updating 
> Debian SID (sysvinit) on a PowerBook G3 Lombard, so it's possible that 
> systemd (or something related to systemd) pulled in a version of 
> vim-common that is incompatible with the latest available version of 
> vim.
>
> Here's the applicable error:
>
> # apt-get install vim
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Solving dependencies... Error!
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>   vim : Depends: vim-common (= 2:9.1.1230-2) but 2:9.1.1846-1 is to be 
> installed
>         Depends: vim-runtime (= 2:9.1.1230-2) but it is not going to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> E: The following information from --solver 3.0 may provide additional 
> context:
>     Unable to satisfy dependencies. Reached two conflicting decisions:
>     1. vim:powerpc=2:9.1.1230-2 is selected for install
>     2. vim:powerpc Depends vim-common (= 2:9.1.1230-2)
>        but none of the choices are installable:
>        [no choices]
>
> ---
>
> I can just wait and hope that a newer version of vim eventually becomes 
> available, or I can use pico, which IMO is good but not as good as vi.
>
> I could also compile and install the latest version of traditional vi 
> (ex-050325) available from "https://sourceforge.net/projects/ex-vi/".
>
> If anyone has any other recommendations, please let me know. Thanks.
>
> -Stan Johnson