Bug#964939: ITP: emacs-orgalist -- Manage Org-like lists in non-Org Emacs buffers

[Sean Whitton]

Package: wnpp
Severity: wishlist
Owner: Sean Whitton 

* Package name: emacs-orgalist
  Version : 1.12
  Upstream Author : Nicolas Goaziou 
* URL : https://elpa.gnu.org/packages/orgalist.html
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : Manage Org-like lists in non-Org Emacs buffers

Recent Org-mode doesn't include orgstruct-mode, and this is the
replacement Org-mode upstream recommends.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#964938: ITP: golang-blackfriday-v2 -- Blackfriday: a markdown processor for Go version 2

[Reinhard Tartler]

Package: wnpp
Owner: Reinhard Tartler 
Severity: wishlist

* Package name: golang-blackfriday-v2
  Version : 2.0
  Upstream Author : Russ Ross
* URL or Web page : https://github.com/russross/blackfriday
* License : BSD-2-clause
  Description : Blackfriday: a markdown processor for Go version 2

This is pretty much a copy of the golang-blackfriday package, but this
is packaging the v2 branch of the project, which breaks API
compatibility. There are a number of packages using the old API and packaging
both branches side-by-side allows a more smooth transition.

To be more specific, this is required for newer versions of the
golang-blackfriday package, which in turn is required for podman/libpod 2.0.

I plan to package this under the Golang packaging team umbrella.

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Russell Stuart]

On Sat, 2020-07-11 at 22:12 -0400, The Wanderer wrote:
> I don't run either systemd or NetworkManager, and I'm not currently
> interested in changing either of those things, but I am interested in
> trying out an alternative to wpa_supplicant. Is there an appropriate
> similar procedure for such an environment, or would I have to
> experiment and play around trying to get things to work?

I don't use network manager, so I'm in a similar position.

From what I can see iwd lacks two features of wpa_supplicant.

Firstly, there doesn't seem to be a way to attach iwd to a particular
wireless interface.  Iwctl doesn't provide one, and I don't see any
other way to tell it.  Most people have just one wireless interface so
it may not be a huge issue but it is an impedance miss-match with
things like ifupdown that are focused on interfaces.  Maybe that's the
problem with network manager too.

Secondly, it doesn't support wpa_supplicant's priorities.  I use them a
fair bit.  For example, I tell wpa_supplicant to favour my phone WiFi
hotspot over others, so if I have a connectivity issue I can just turn
it on.  That said, I guess I could just use iwctl to manually connect
to the phone.


signature.asc
Description: This is a digitally signed message part

Bug#964933: ITP: golang-github-brentp-goluaez: Easy embedding Lua in go

[Nilesh Patra]

Package: wnpp
Severity: wishlist
Owner: Nilesh Patra 
X-Debbugs-CC: debian-devel@lists.debian.org


* Package name: golang-github-brentp-goluaez
  Version : 0.0~git20160116.dd35d08-1
  Upstream Author : Brent Pedersen
* URL : https://github.com/brentp/goluaez

* License : Expat
  Programming Lang: Golang
  Description : Easy embedding Lua in go

 goluaez wraps gopher-lua  and gopher-luar.
 gopher-luar does a nice job of converting
 go values to Lua. This package uses that and
 also converts Lua values to go and converts
 go slices to Lua tables.

I shall maintain this package.

Bug#964932: ITP: golang-github-yuin-gluare: Regular expression library for the GopherLua

[Nilesh Patra]

Package: wnpp
Severity: wishlist
Owner: Nilesh Patra 
X-Debbugs-CC: debian-devel@lists.debian.org


* Package name: golang-github-yuin-gluare
  Version : 0.0~git20170607.d7c94f1-1
  Upstream Author : Yusuke Inuzuka
* URL : https://github.com/yuin/gluare

* License : Expat
  Programming Lang: Golang
  Description : Regular expression library for the GopherLua
 Gluare has almost the same API as Lua pattern match.
 "re.find" , "re.gsub", "re.match", "re.gmatch"
 are available. These functions have the same API
 as Lua pattern match. gluare uses the Go regexp package,
 so you can use regular expressions that are supported
 in the Go regexp package.

I shall maintain this package.

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Jeremy Stanley]

On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote:
[...]
> What is (unusual but) usable, however, is to *not* use Network
> Manager for wifi, but use IWD+systemd or IWD standalone for wifi,
> and use Network Manager to manage _other_ network components.
> 
> In such unusual-but-real setup, wpa-supplicant would be dead
> weight. Lightweight, arguably, but a daemon and therefore
> additional risk of hair-pulling confusions: If wpa-supplicant
> daemon is running, IWD fails to work.
[...]
> On Debian you can only remove the wpa-supplicant if you also
> remove network-manager - which I find is an unnecessary tight
> coupling.
[...]

Worth considering is that it still may in fact not be *too* unusual
to have systems with no wireless network interface at all. I have
quite a few in my possession running current releases of Debian.
Granted I've been eschewing NM on them in favor of ifupdown for
simplicity, but I could foresee wanting to install it on them and
having zero use for either wpa-supplicant or iwd. I've actually
grown quite fond of nmcli, once NM mostly got over its (lengthy)
rough patch.
-- 
Jeremy Stanley


signature.asc
Description: PGP signature

Re: IPv6-only buildds and AI_ADDRCONFIG

[smcv]

On Sat, 11 Jul 2020 at 23:59:33 +0300, Niko Tyni wrote:
> src:perl suddenly failed to build due to test suite
> failures.
> 
> This was quickly diagnosed to be a result of passing the AI_ADDRCONFIG
> flag to getaddrinfo(3).

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952740 and
these maybe-related glibc bugs:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780294
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455762
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854301
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854302
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897662

#952740 has some more references.

> glib2.0_2.64.3-1

I'm surprised GLib 2.64.x is affected, because
GLib since 2.63.1 has implemented the Internet-Draft
,
which I believe is also implemented in the major web browsers, and
should have made it bypass the issues that prompted me to open #952740.
(But perhaps something different is happening here.)

Older GLib versions (in buster and older) are unlikely to be fixed.

As I said on #952740, I don't think it's particularly
scalable for every consumer of the getaddrinfo() API (or at
least those that want to resolve and talk to localhost in
their unit tests) to have an independent reimplementation of
,
so it would be great if glibc could solve this for all of us at once.

smcv

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Jonas Smedegaard]

Quoting Andrey Rahmatullin (2020-07-12 20:00:23)
> On Sun, Jul 12, 2020 at 08:29:08PM +0300, Andrei POPESCU wrote:
> > > Network-Manager needing wpa-supplicant in _most_ situations is a reason 
> > > to _recommend_ it not a reason to _depend_ on it, per Debian Policy!
> > 
> > If Network Manager needs to depend on the wireless component, that could 
> > probably be:
> > 
> > Depends: wpasupplicant | iwd
> As discussed in the bug report linked earlier, this can only work if NM
> supports iwd by default, which it currently doesn't and apparently isn't
> going to.

Yes: Network Manager needs a _specific_ wireless component for 
_specific_ network management tasks.

It would therefore be wrong for network-manager do declare a fallback 
dependency on iwd because network-manager cannot (reliably or at all) 
use iwd the same way as it uses wpa-supplicant.

What is (unusual¹ but) usable, however, is to *not* use Network Manager 
for wifi, but use IWD+systemd or IWD standalone for wifi, and use 
Network Manager to manage _other_ network components.

In such unusual-but-real setup, wpa-supplicant would be dead weight.  
Lightweight, arguably, but a daemon and therefore additional risk of 
hair-pulling confusions: If wpa-supplicant daemon is running, IWD fails 
to work.

Simpler if possible to avoid having wpa-supplicant installed on systems 
where wpa-supplicant is never used anyway: On Debian² you can only 
remove the wpa-supplicant if you also remove network-manager - which I 
find is an unnecessary tight coupling.


 - Jonas


¹ Debian Policy § 7.2 says that packages needed "in all but unusual 
installations" should be _recommended_ not depended on.

² Using equivs is not Debian but a slight fork of Debian.

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Andrey Rahmatullin]

On Sun, Jul 12, 2020 at 08:29:08PM +0300, Andrei POPESCU wrote:
> > Network-Manager needing wpa-supplicant in _most_ situations is a reason 
> > to _recommend_ it not a reason to _depend_ on it, per Debian Policy!
> 
> If Network Manager needs to depend on the wireless component, that could 
> probably be:
> 
> Depends: wpasupplicant | iwd
As discussed in the bug report linked earlier, this can only work if NM
supports iwd by default, which it currently doesn't and apparently isn't
going to.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Andrei POPESCU]

On Du, 12 iul 20, 13:33:13, Jonas Smedegaard wrote:
> 
> Network-Manager needing wpa-supplicant in _most_ situations is a reason 
> to _recommend_ it not a reason to _depend_ on it, per Debian Policy!

If Network Manager needs to depend on the wireless component, that could 
probably be:

Depends: wpasupplicant | iwd
 
> It could be even simpler by providing a package with a config snippet 
> for network-manager.

+1

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Jonas Smedegaard]

Quoting Andrey Rahmatullin (2020-07-12 16:27:16)
> On Sun, Jul 12, 2020 at 01:07:37PM +0200, Jonas Smedegaard wrote:
> > How to use iwd without NetworkManager or systemd:
> > 
> > apt install iwd resolvconf
> > cat << END > /etc/NetworkManager/conf.d/iwd.conf
> "without NetworkManager" yet "/etc/NetworkManager/conf.d"? What will read
> this config?

Whoops, copy-paste error: Should be /etc/iwd/main.conf

Thanks for spotting it, Andrey!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Andrey Rahmatullin]

On Sun, Jul 12, 2020 at 01:07:37PM +0200, Jonas Smedegaard wrote:
> How to use iwd without NetworkManager or systemd:
> 
> apt install iwd resolvconf
> cat << END > /etc/NetworkManager/conf.d/iwd.conf
"without NetworkManager" yet "/etc/NetworkManager/conf.d"? What will read
this config?

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Jonas Smedegaard]

Quoting Andrey Rahmatullin (2020-07-12 09:34:32)
> On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote:
> > > > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > > > https://bugs.debian.org/919619
> > > That Depends is not a problem.
> > 
> > Yes a problem, but not a unsurmountable one: You can...
> > 
> >  a) pollute your Debian system using equivs, or
> > 
> >  b) install the dependency but then disable the daemon
> You still need manual action to use iwd, so disabling wpa-supplicant is
> just another command.

Yes, iwd requires configuration.  We should _minimize_ the need for 
configuration: iwd needing configuration of NetworkManager is no reason 
to _depend_ on wpa-supplicant.

Network-Manager needing wpa-supplicant in _most_ situations is a reason 
to _recommend_ it not a reason to _depend_ on it, per Debian Policy!

Current minimal fresh installation with network-manager and iwd:

1) apt install network-manager iwd
2) Configure Network-Manager to use iwd
3) Stop wpa-supplicant
4) Disable wpa-supplicant
5) Restart iwd
6) Restart network-manager

This would be simpler if network-manager followed Debian Policy in 
acknowledging that wpa-supplicant is not *ALWAYS* needed, by 
recommending not depending on it:

1) apt install network-manager iwd wpa-supplicant-
2) Configure Network-Manager to use iwd
3) Restart network-manager

It could be even simpler by providing a package with a config snippet 
for network-manager.

It *cannot* be much simpler with a helper pacakge while network-manager 
depends on wpa-supplicant, because such helper package would then need 
to Provide: wpa-supplicant which is not Policy compliant, and such 
package could therefore not be part of Debian.

Using equivs could not be part of Debian.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Jonas Smedegaard]

Quoting Marco d'Itri (2020-07-12 03:56:57)
> On Jul 11, Jonas Smedegaard  wrote:
> 
> > > (Way more people should switch from wpa_supplicant to iwd.)
> > 
> > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > https://bugs.debian.org/919619
> How to switch to iwd:
> 
> apt install iwd
> cat << END > /etc/NetworkManager/conf.d/iwd.conf
> [device]
> wifi.backend=iwd
> END
> systemctl restart NetworkManager

Above is not enough - also needs either disabling the wpa-supplicant 
daemon or force-avoid it e.g. using equivs.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Jonas Smedegaard]

Quoting The Wanderer (2020-07-12 04:12:54)
> On 2020-07-11 at 21:56, Marco d'Itri wrote:
> 
> > On Jul 11, Jonas Smedegaard  wrote:
> > 
> >>> (Way more people should switch from wpa_supplicant to iwd.)
> >> 
> >> Difficult when network-manager depends (not recommends) wpa-supplicant:
> >> https://bugs.debian.org/919619
> > 
> > How to switch to iwd:
> > 
> > apt install iwd
> > cat << END > /etc/NetworkManager/conf.d/iwd.conf
> > [device]
> > wifi.backend=iwd
> > END
> > systemctl restart NetworkManager
> 
> I don't run either systemd or NetworkManager, and I'm not currently
> interested in changing either of those things, but I am interested in
> trying out an alternative to wpa_supplicant. Is there an appropriate
> similar procedure for such an environment, or would I have to experiment
> and play around trying to get things to work?
> 
> I also have quite a few network definitions in wpa_supplicant.conf, and
> I wouldn't want to have to re-enter them manually into a new system if I
> could avoid it. Is there a migration procedure, other convenient way to
> bring those settings across into iwd?
> 
> (I'm not at the computer involved at the moment, so I can't easily check
> things to see whether any of the answers might be quickly obvious.)

How to use iwd without NetworkManager or systemd:

apt install iwd resolvconf
cat << END > /etc/NetworkManager/conf.d/iwd.conf
[General]
EnableNetworkConfiguration = true

[Network]
NameResolvingService = resolvconf
END

You then also need to start iwd as a daemon somehow - and consider 
filing patches to support those: Debian package provides hooks for 
systemd but not sysv or runit.

Debian package includes hooks for connman, but I am not sure which iwd 
or connman configuration changes that involves.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Geert Stappers]

On Sun, Jul 12, 2020 at 12:34:32PM +0500, Andrey Rahmatullin wrote:
> On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote:
> > > > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > > > https://bugs.debian.org/919619
> > > That Depends is not a problem.
> > 
> > Yes a problem, but not a unsurmountable one: You can...
> > 
> >  a) pollute your Debian system using equivs, or
> > 
> >  b) install the dependency but then disable the daemon
> You still need manual action to use iwd, so disabling wpa-supplicant is
> just another command.
> 
> 
> 
> -- 
> WBR, wRAR

FWIW   I think that Andrey is happy with a disabled wpa-supplicant
and that Jonas is right for asking wpa-supplicant not required by
network-manager.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.

[Andrey Rahmatullin]

On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote:
> > > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > > https://bugs.debian.org/919619
> > That Depends is not a problem.
> 
> Yes a problem, but not a unsurmountable one: You can...
> 
>  a) pollute your Debian system using equivs, or
> 
>  b) install the dependency but then disable the daemon
You still need manual action to use iwd, so disabling wpa-supplicant is
just another command.



-- 
WBR, wRAR


signature.asc
Description: PGP signature