nicely report any errors involving finding and using ifconfig #1536
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1536
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A couple of users have recently reported errors from iputil when it couldn't find their
ifconfig
executable, e.g.:We should catch this exception and report a useful error message, saying what the
sys.platform
was and asking them to report about theirifconfig
, like David-Sarah did on the list:In changeset:8e69b94588c1c0e7:
Re: changeset:8e69b94588c1c0e7, I would be tempted to use
.startswith('linux')
and.startswith('irix')
, rather than testing for more specific strings.(https://bbs.archlinux.org/viewtopic.php?pid=945602#p945602) &
http://www.archlinux.org/news/deprecation-of-net-tools/
Apparently Arch deprecated ifconfig and "ip addr" is supposed to be
used.
I've just created pull request (#14) on github with a simple patch to use $PATH to find ifconfig.
A few questions that went through my mind during that process:
I considered adding optional iproute2 support, as suggested above (and indeed, net-tools are deprecated in many distros), but I think it's a wrong way to do it - iproute2 docs clearly state that it's output is a subject to change (and it's usually updated once per kernel release) and is not designed to be parseable, so maybe some specialized netlink module should be used on linux instead?
Hi mk.fg! I was just investigating related bugs and I discovered this comment you added to this ticket. I'm sorry I didn't see it when you first posted it! I need to get more reliable monitoring of updates to trac+github...
See #1988.
In /tahoe-lafs/trac-2024-07-25/commit/a493ee0bb641175ecf918e28fce4d25df15994b6:
Milestone renamed
moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
Moving open issues out of closed milestones.
(https://github.com/tahoe-lafs/tahoe-lafs/pull/872) removes use of ifconfig entirely
pull 872 merged in https://github.com/tahoe-lafs/tahoe-lafs/commit/25ee76104ad15e78b33a15643e330d2ec285dc89