public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: jimedrand@autistici.org
To: "Sebastian Hörberg" <sebastian@cozycabin.se>
Cc: Gwml <gwml@vger.gnuweeb.org>
Subject: Re: Getting Waydroid into Factory
Date: Mon, 12 Jan 2026 23:18:35 +0000	[thread overview]
Message-ID: <fa0123104fc881842d761d2b006ba0b4@autistici.org> (raw)
In-Reply-To: <f0e9981a-5003-43eb-951b-e9a0c44d7459@cozycabin.se>

On 2026-01-12 19:58, Sebastian Hörberg wrote:
> Hello,
Oh, hello to you.

> I saw that you did some big updates on the repo. Just wanted to let you 
> know that it seems to break when updating:
> 
> Resolving dependencies...
> Resolving package dependencies...
> 
> Problem: 1: the to be installed waydroid-1.6.1-12.1.noarch requires 
> '(kmod(binder_linux.ko) if kernel)', but this requirement cannot be 
> provided
>  Solution 1: Following actions will be done:
>   deinstallation of kernel-default-6.18.3-9.1.g1198a45.x86_64
>   deinstallation of kernel-default-6.18.3-11.1.g16d7e52.x86_64
>   deinstallation of kernel-default-6.18.3-1.0.6.1.sr20251204.x86_64
>  Solution 2: do not install waydroid-1.6.1-12.1.noarch
>  Solution 3: break waydroid-1.6.1-12.1.noarch by ignoring some of its 
> dependencies

Yeah, I am working to make the updates and adding the solution by making 
Shell script to manage the DKMS, since KMP approach aren't effective 
anymore. If you have idea, you can help me to tell which should I did 
for improving the packages before pulling into. I hope these solution 
will let them pull it without touching the kernel and utilise DKMS.

I was doing the big update yesterday when I am in hospital for control 
at psychiatry and I am using hospital's public internet for working the 
updates. Just let me know when everything works at the upcoming updates 
(always refresh the repo during the updates).

That's it from me.

Regards

Jim


       reply	other threads:[~2026-01-12 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1940ab8d-86ef-4982-bf5f-1cb7595b121b@cozycabin.se>
     [not found] ` <47bcf98d-3109-4972-84a9-225258e9d00e@cozycabin.se>
     [not found]   ` <DEA3743F-A0DE-4410-916C-312169534C94@autistici.org>
     [not found]     ` <f0e9981a-5003-43eb-951b-e9a0c44d7459@cozycabin.se>
2026-01-12 23:18       ` jimedrand [this message]
2026-01-13  0:35         ` Getting Waydroid into Factory jimedrand
2026-01-18 17:13           ` Sebastian Hörberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa0123104fc881842d761d2b006ba0b4@autistici.org \
    --to=jimedrand@autistici.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=sebastian@cozycabin.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox