Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #230820 > unrolled thread

Python 3 wicd

Back to article view | Back to linux.debian.user

Contents

  Python 3 wicd "Gareth Evans" <donotspam@fastmail.fm> - 2021-01-19 04:00 +0100
    Re: Python 3 wicd Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-19 09:20 +0100
      Re: Python 3 wicd "Gareth Evans" <donotspam@fastmail.fm> - 2021-01-19 11:50 +0100
      Re: Python 3 wicd Sven Joachim <svenjoac@gmx.de> - 2021-01-19 17:50 +0100
        Re: Python 3 wicd Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-19 21:20 +0100
          Re: Python 3 wicd Vincent Lefevre <vincent@vinc17.net> - 2021-01-22 13:30 +0100

#230820 — Python 3 wicd

There is apparently a Python 3 fork of wicd (or two) but I can't figure out what state they're in - are either of these likely to become available in Buster repos?  Backports?

https://github.com/PXke/wicd-reloaded

https://github.com/zeph/wicd

The latter is apparently "migrated upstream" to
https://code.launchpad.net/wicd

- while the former refers to
https://launchpad.net/wicd

What's going on there?

Thanks,
Gareth

[toc] | [next] | [standalone]

#230827

[Multipart message — attachments visible in raw view] — view raw

On Ma, 19 ian 21, 02:54:25, Gareth Evans wrote:
> There is apparently a Python 3 fork of wicd (or two) but I can't 
> figure out what state they're in - are either of these likely to 
> become available in Buster repos?  Backports?

Wicd is currently only available in experimental (according to 
https://tracker.debian.org/wicd)[1], while backports can only be done 
from packages in testing (currently bullseye).

Considering bullseye is now already in the first stage of the freeze 
before release there is little chance for Wicd to be included in 
bullseye at all.

After bullseye is released it might become available in 
bullseye-backports, maybe also buster-backports-sloppy.

[1] apparently the version in experimental has been ported to Python 3, 
since it builds the python3-wicd binary package.

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

[toc] | [prev] | [next] | [standalone]

#230832

On Tue, 19 Jan 2021, at 08:16, Andrei POPESCU wrote:
> On Ma, 19 ian 21, 02:54:25, Gareth Evans wrote:
> > There is apparently a Python 3 fork of wicd (or two) but I can't 
> > figure out what state they're in - are either of these likely to 
> > become available in Buster repos?  Backports?
> 
> Wicd is currently only available in experimental (according to 
> https://tracker.debian.org/wicd)[1], while backports can only be done 
> from packages in testing (currently bullseye).
> 
> Considering bullseye is now already in the first stage of the freeze 
> before release there is little chance for Wicd to be included in 
> bullseye at all.
> 
> After bullseye is released it might become available in 
> bullseye-backports, maybe also buster-backports-sloppy.
> 
> [1] apparently the version in experimental has been ported to Python 3, 
> since it builds the python3-wicd binary package.
> 
> Kind regards,
> Andrei
> -- 
> http://wiki.debian.org/FAQsFromDebianUser
> 
> Attachments:
> * signature.asc

Thanks, that's helpful.  
G

[toc] | [prev] | [next] | [standalone]

#230856

On 2021-01-19 10:16 +0200, Andrei POPESCU wrote:

> On Ma, 19 ian 21, 02:54:25, Gareth Evans wrote:
>> There is apparently a Python 3 fork of wicd (or two) but I can't
>> figure out what state they're in - are either of these likely to
>> become available in Buster repos?  Backports?
>
> Wicd is currently only available in experimental (according to
> https://tracker.debian.org/wicd)[1], while backports can only be done
> from packages in testing (currently bullseye).
>
> Considering bullseye is now already in the first stage of the freeze
> before release there is little chance for Wicd to be included in
> bullseye at all.
>
> After bullseye is released it might become available in
> bullseye-backports, maybe also buster-backports-sloppy.

The version in experimental is a git snapshot from September 2019,
apparently development has stalled.  People upgrading to bullseye should
probably look for alternatives, I think network-manager is the only
reasonable one unless you are willing to resort to commandline tools.

Cheers,
       Sven

[toc] | [prev] | [next] | [standalone]

#230861

[Multipart message — attachments visible in raw view] — view raw

On Ma, 19 ian 21, 17:40:47, Sven Joachim wrote:
> 
> The version in experimental is a git snapshot from September 2019,
> apparently development has stalled.  People upgrading to bullseye should
> probably look for alternatives, I think network-manager is the only
> reasonable one unless you are willing to resort to commandline tools.

Fully agreed.

While it might have had its toothing problems in the beginning 
NetworkManager has been reliable for me since switching from Wicd (some 
time around the wheezy release I believe).

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

[toc] | [prev] | [next] | [standalone]

#230968

On 2021-01-19 22:09:49 +0200, Andrei POPESCU wrote:
> While it might have had its toothing problems in the beginning 
> NetworkManager has been reliable for me since switching from Wicd (some 
> time around the wheezy release I believe).

I use Debian/unstable, and I've also switched to NetworkManager
(I'm using nmcli only, no GUI). It seems reliable, perhaps more
than wicd (which would often not reconnect after an unexpected
WiFi disconnection, due to some bug in its connection logic).
However, WiFi connections are lost when NetworkManager is upgraded.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web