On Sun, 21 Jan 2024 at 17:14:11 -0700, Stan Johnson wrote:
> The bottom line is that there appears to be a dependency issue in Debian
> SID at the moment
You can't *necessarily* draw this conclusion from a failure to
upgrade. You are using powerpc, which is a "ports" architecture that is
not
> "Stan" == Stan Johnson writes:
Stan> sysvinit-core. But if wdm really does require systemd now,
Stan> that might explain this issue, with other X packages being
Stan> dependent on either wdm or systemd. As I recall, wdm is the
It does not look like wdm requires systemd.
I set
Hi Colin,
On 1/21/24 3:22 PM, Stan Johnson wrote:
> ...
>
> I'll also try installing systemd first (and let sysvinit-core be
> uninstalled), then I'll run "apt-get dist-upgrade", then re-install
> sysvinit-core and see if that disables systemd and lets the X packages
> remain. I've noticed
Hi Colin,
Thanks for your reply.
On 1/21/24 12:35 PM, Colin Watson wrote:
> On Sun, Jan 21, 2024 at 10:41:05AM -0700, Stan Johnson wrote:
>> I have a PowerMac G4 MDD (two 1.25 GHz CPUs, 2 GiB memory) that has been
>> running Debian SID for years. It was last updated on 15 Oct 2023, with
>> no
On Sun, Jan 21, 2024 at 10:41:05AM -0700, Stan Johnson wrote:
> I have a PowerMac G4 MDD (two 1.25 GHz CPUs, 2 GiB memory) that has been
> running Debian SID for years. It was last updated on 15 Oct 2023, with
> no problems. Yesterday, the update failed. Specifically, "apt-get
> update" worked,
Hello,
I have a PowerMac G4 MDD (two 1.25 GHz CPUs, 2 GiB memory) that has been
running Debian SID for years. It was last updated on 15 Oct 2023, with
no problems. Yesterday, the update failed. Specifically, "apt-get
update" worked, "apt-get upgrade" worked, and "apt-get dist-upgrade"
worked but
6 matches
Mail list logo
