Devuan bug report logs - #503
Let's fork iwd for Devuan

Full log

Message #65 received at 503@bugs.devuan.org (full text, mbox, reply):

Received: (at 503) by bugs.devuan.org; 7 Aug 2020 10:40:23 +0000
Return-Path: <bardot.jerome@gmail.com>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 07 Aug 2020 10:40:23 +0000 (UTC)
Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 3A482F60D19
	for <503@bugs.devuan.org>; Fri,  7 Aug 2020 12:34:19 +0200 (CEST)
Authentication-Results: vm6.ganeti.dyne.org;
	dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="r9KhzQ4C";
	dkim-atps=neutral
Received: by mail-lj1-f173.google.com with SMTP id g6so1643742ljn.11
        for <503@bugs.devuan.org>; Fri, 07 Aug 2020 03:34:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=y+mughoQg4FqStCPM2ZU941Ef7npZjRTwI6jss8rCCc=;
        b=r9KhzQ4CSdAot6lZJhdaSiH9iyXrQsUtMczHG7R9WQKQE/bjVkRCZpwQYDrkc3iaTu
         F+VW4pT6ITQJHcyZXOyEReRSQng++zLbHrUeqrzdeEqc0blP0+ZmyBMgRKLNW5I6R/VI
         S049w95aRuipzs0Khb1L8/E6mXZiRnVZGYLU3s+Y+vQ+EbdCqevJBBY/bAtF/TwEe9jP
         208TYNIwqUAqtmwaBZWCLUDh5bY9Jkqp83ZNIpblKm/2pj2e80dm9EsJD2dCrhUF2uB+
         RIw3w1blsYtkeP45wsaEWOBVMXo2sdmHjQwXOo422XxE3IMIMU6NV0/uDbJ/xOW01iHQ
         bLkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=y+mughoQg4FqStCPM2ZU941Ef7npZjRTwI6jss8rCCc=;
        b=eQgKFQiEV6DTPIia74T0g1kPgUTnjF5vvgwmkq3Td5Qp8+EV5luR5FAhP+ZuXxekgs
         /5oJ9ujxYe6YT7Z+9kOrdml7R+Ew9eENfWygmOkB0gVm05b3yuQ8j8iaXXESvhwonUyg
         7arKKKdwEOBpFIvlOBY90aJcxPUucCS7R/ve7IdmGs2VGALOT7vDc7zbv9SzUzLfkC1q
         N6573n9EqR597qEuGNsmeRnmyUKbdVI+yXF0zwiNu5m7BnSGrfLG5ZZO1ABFFWutZU9/
         voII6eQhDIJF6t9NuyRXLGBVKQKvFZwZF3F3wbMm8453lQ1JqPeS673nqGpgIQTZWnl1
         /VYQ==
X-Gm-Message-State: AOAM533JrmO8lBGGhAa+JTsjKyjJUnHiIyhAq8tP0GnAM/7JTtS9Vhma
	BT2LWeburSSX17021UyGd1PKQo0jJ9Q8a2fQ9w==
X-Google-Smtp-Source: ABdhPJzgMp6CcFuMcCg8k2jTFWYbEZZfiS9iJHvie9wAZ51UuMPQ6ZyE+KUX+GmJbwPxY2uIUtIwJc0mfMN/uV6vIaY=
X-Received: by 2002:a05:651c:505:: with SMTP id o5mr5974707ljp.306.1596796457448;
 Fri, 07 Aug 2020 03:34:17 -0700 (PDT)
MIME-Version: 1.0
References: <FiXiKc927Z_oR8ANirTfYvBFEyWwdRIceWiwAfJ8Bdg8GNY3hElHXtJFRBujiY2WyWxqEygwxVDfAJtvMVh-6GWAXh5C3-6TaUkncW7VpbE=@protonmail.com>
 <20200805120745.GX3011@hindley.org.uk> <20200805122334.GY3011@hindley.org.uk>
 <CAK6hYTviB06Kk8PMAfmq1M_cxHfEoUpUyCCHz36Sjsj-ChddSw@mail.gmail.com>
 <ipQrEfC9J_OQ9jXsoNno9rHaYXRvG5MH3RiBSAanmV4c1aJc8q3q5V83zsjOZTBAwz7Gv5L-g4ttPWgMSquaVmu3BgnPMKutWHBZOdjlOS8=@protonmail.com>
 <896a5dff-f104-e242-06ee-3e8d18368bac@gmail.com> <TZctggqPuYPy9J6OSac6r33Y-pJd6NIJG5bf3HJWyDCfftoz_9nQxXBOA0jDxF0XWLRioVeeMG1pgZf6kKSLKAn_UT6i5RGQKN0BFYNCmak=@protonmail.com>
 <737fdb19-b22b-52ae-7a3d-c3df90be068d@gmail.com>
In-Reply-To: <737fdb19-b22b-52ae-7a3d-c3df90be068d@gmail.com>
From: Jérôme Bardot <bardot.jerome@gmail.com>
Date: Fri, 7 Aug 2020 12:34:05 +0200
Message-ID: <CAK6hYTvCdFfNCo8UyOvCS9VemnSmE5v6g9bwXRcqa+XVU8jJDw@mail.gmail.com>
Subject: Re: [devuan-dev] bug#503: Let's fork iwd for Devuan
To: Job Bautista <jobbautista9@protonmail.com>
Cc: "503@bugs.devuan.org" <503@bugs.devuan.org>, Mark Hindley <mark@hindley.org.uk>
Content-Type: multipart/mixed; boundary="000000000000a0094005ac4725b6"
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,FROM_EXCESS_BASE64,
	RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

[Message part 1 (text/plain, inline)]

I just sysd2v v0.3 the /lib/systemd/system/iwd.service and the start
look good. Process is in ps auxf |grep "iwd"
I’m currently not able to be sure furthermore if it’s really working i
have to read more about init script  (never know what is needed or/and
for what) iw and connman integration there is a systemd script for
that to

cat /usr/share/dbus-1/system-services/net.connman.iwd.service
[D-BUS Service]
Name=net.connman.iwd
Exec=/bin/false
User=root
SystemdService=iwd.service

but not sure it s a really usefull one

Le ven. 7 août 2020 à 12:14, Bardot Jérôme <bardot.jerome@gmail.com> a écrit :
>
> If it’s really the case it’s not fair and not profesionnal at all.
>
> For me the fact is the current situation is not suitable at all. debian
> and devuan need a way to select init system and apt install related
> packages even if the default package is systemd. Something like that.
>
> mypackage
> mypackage-sysinit
>
>
> For the current problem i guess if we do the init file maybe we can
> upstream push request it instead of forking it ?
>
> Also i don t know state of devuan's $$ ressources but it will be
> necessary to have some kind of testing of all package (pseudo code)
>
> service package start
> if $? == 0
>  ok
> else
>  notok
>
> And also scenario cases to improve qualities because it’s the only way
> to keep diversity on long term. (a day i will have time to weekly meeting)
>
>
>
> On 07/08/2020 04:12, Job Bautista wrote:
> > It's not declared in Depends, but iwd has a hidden dependency on systemd. On
> > non-systemd systems, iwd doesn't autostart on boot, requiring you to start it
> > manually or create an initscript for it. Debian packages are supposed to work
> > out-of-the-box when you install them. If today's iwd was being packaged
> > before systemd became the default init of Debian, no sane DD would have
> > sponsored or accepted it into the main archive.
> >
> > iwd also has a Build-Depends on systemd, which means it's impossible to build
> > iwd on Devuan without disabling the compilation of the systemd service on
> > debian/rules. Or maybe it does build without systemd even when the systemd
> > service compilation is enabled. I haven't tested that yet I think.
> >
> > Job Bautista
> >
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Thursday, August 6, 2020 11:28 PM, Bardot Jérôme <bardot.jerome@gmail.com> wrote:
> >
> >> I just check in testing debian and
> >>
> >
> >> #apt show iwd
> >>
> >
> >> Package: iwd
> >> Version: 1.8-1
> >> Priority: optional
> >> Section: net
> >> Maintainer: Andreas Henriksson andreas@fatal.se
> >> Installed-Size: 2 019 kB
> >> Depends: libc6 (>= 2.27), libreadline8 (>= 6.0)
> >> Download-Size: 483 kB
> >> APT-Manual-Installed: yes
> >> APT-Sources: tor+http://ftp.fr.debian.org/debian testing/main amd64 Packages
> >> Description: wireless daemon for Linux
> >> Minimalistic wireless daemon that uses modern Linux interfaces like
> >> cfg80211 and nl80211 (netlink). The daemon provides a D-Bus API.
> >> .
> >> The daemon can be controlled from the command line with the included
> >> iwctl client utility.
> >> .
> >> The included iwmon utility can be used to monitor the 802.11 subsystem
> >> generic netlink commands and events. It uses the nlmon kernel driver
> >> from Linux 3.10 and later.
> >>
> >
> >> If it s the right package it’s look like their is no dependencies to
> >> systemd.
> >>
> >
> >> On 06/08/2020 06:54, Job Bautista wrote:
> >>
> >
> >>> Hi Jérôme, that looks like a good alternative indeed. It should be packaged by
> >>> Debian though, not Devuan. However, I don't think I can maintain more than two
> >>> packages. I already have a a sponsorship request pending on
> >>> mentors.debian.net for the xfce4-alsa-plugin package.1 And now I'm going to
> >>> maintain a fork of iwd. So you will have to ask someone else to package eiwd.
> >>> I will ask the eiwd dev to consider adding support for sysvinit though. They
> >>> might be more open to supporting multiple inits than their upstream iwd. Or
> >>> they might just reject it because they want to modify as little as possible
> >>> from upstream. Who knows...
> >>> Job Bautista
> >>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >>> On Wednesday, August 5, 2020 9:58 PM, Jérôme Bardot bardot.jerome@gmail.com wrote:
> >>>
> >
> >>>> i also will ask for it, also maybe try to use
> >>>> https://github.com/dylanaraps/eiwd look like a good alternative
> >>>> because of the no dbus functionalities ?
> >>>
> >
> >>>> Le mer. 5 août 2020 à 14:31, Mark Hindley mark@hindley.org.uk a écrit :
> >>>
> >
> >>>>> Job,
> >>>>> Many thanks for taking this on.
> >>>>> A few comments on https://git.devuan.org/jobbautista9/iwd
> >>>
> >
> >>>>> -   The branch should be suites/unstable.
> >>>>> -   Add Origin: Devuan to d/control
> >>>>> -   You need to update d/gbp.conf, in particular debian-branch, debian-tag and
> >>>>>     pristine-tar. Devuan avoids using pristine-tar.
> >>>>>
> >
> >>>
> >
> >>>>> -   Vcs-* fields in d/control should be https://git.devuan.org/devuan/iwd (where
> >>>>>     the definitive source will be once it is accepted)
> >>>>>
> >
> >>>
> >
> >>>>> -   You don't need quilt patches for changes in debian/. So you can just create
> >>>>>     the initscript as debian/iwd.init.
> >>>>>
> >
> >>>
> >
> >>>>> -   You shouldn't add the initscript control fragments to the maintscripts
> >>>>>     manually, debhelper should do it (correctly) for you.
> >>>>>
> >
> >>>
> >
> >>>>>
> >
> >>>
> >
> >>>>> Other than the last item, these are documented in the Devuan Maintainers
> >>>>> Guide1. If anything is not clear do ping me on #devuan-dev.
> >>>>> Thanks
> >>>>> Mark (LeePen)
> >>>>> 1 https://git.devuan.org/devuan/documentation/src/branch/master/maintainers
> >>>
> >
> >>>>> devuan-dev internal mailing list
> >>>>> devuan-dev@lists.dyne.org
> >>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
> >
>

[iwd (application/octet-stream, attachment)]

Send a report that this bug log contains spam.