Your message dated Mon, 11 Nov 2024 16:59:46 +0000 with message-id <e1taxls-002bt2...@fasolo.debian.org> and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #397885, regarding guessnet: /etc/network/interfaces parsing problems to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 397885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: guessnet Version: 0.41-1 Severity: important I'm using the following /e/n/i file to test guessnet. mapping wlan0 script guessnet-ifupdown map timeout: 10 map verbose: true map debug: true map default: dhcp map foo-wlan map bar-wlan iface foo-wlan inet static test command sleep 2; true iface bar-wlan inet static test command sleep 1; true iface baz-wlan inet static test command true Using the command cat < /dev/null | sudo guessnet -i -v wlan0 I get the following output: sds@santefisi:/etc/network$ cat < /dev/null | sudo guessnet -i -v wlan0 guessnet: Link beat detection (mii) failed: Operation not supported guessnet: 3 candidate profiles guessnet: Starting command test subsystem guessnet: adding candidate script [sleep 2; true] with tag [command 'sleep 2; true'] guessnet: adding candidate script [sleep 1; true] with tag [command 'sleep 1; true'] guessnet: adding candidate script [true] with tag [command 'true'] guessnet: script [command 'true'] terminated with status 0 baz-wlan I'm getting the following unexpected behaviours. 1) Substituting the word "test" with "guessnet" in the guessent test line in the logical interfaces stanzas I don0t get anymore recongized the test (the profile isn't recognized by guessnet, and so it's not executed). While this isn't a big issue, it's very confusing for the newbie, since documentation tells the "guessnet" word may be used instead of "test". E.g. with the test line in the baz-wlan interface substituted by a corresponding guessnet line I get: sds@santefisi:/etc/network$ cat < /dev/null | sudo guessnet -i -v wlan0 guessnet: Link beat detection (mii) failed: Operation not supported guessnet: 2 candidate profiles guessnet: Starting command test subsystem guessnet: adding candidate script [sleep 2; true] with tag [command 'sleep 2; true'] guessnet: adding candidate script [sleep 1; true] with tag [command 'sleep 1; true'] guessnet: script [command 'sleep 1; true'] terminated with status 0 bar-wlan 2) The "limiting valid logical intefaces" mechanism in the mapping stanza seems not to work. In the previous example I always get baz-wlan as the discovered interface, although in the mapping stanza I listed the wanted interfaces (excluding baz-wlan). The same issue raises using as physical interface "eth0" instead of "wlan": sds@santefisi:/etc/network$ cat < /dev/null | sudo guessnet -d none -i -v eth0 guessnet: 3 candidate profiles guessnet: Starting command test subsystem guessnet: adding candidate script [sleep 2; true] with tag [command 'sleep 2; true'] guessnet: adding candidate script [sleep 1; true] with tag [command 'sleep 1; true'] guessnet: adding candidate script [true] with tag [command 'true'] guessnet: script [command 'true'] terminated with status 0 baz-wlan while I expected to have as result the "none" interface. Another problem concerning the guessnet design is that it returns every time the first interface discovered, which is something that in many cases is quite meaningless: in many cases is important to discover all the possible interfaces available, then to choose between them according to an assigned priority, that may not depend on the time requested to discover the interface. I like the general design of guessnet, as well as the nice integration with the ifupdown system, but the previous problems affect quite seriously its usability. I also would like to know if you are planning to support anymore guessnet (that actually seems quite undermaintained). In each case thanks for your valuable effort. Cheers -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1.061109.homer Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages guessnet depends on: ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-19 GCC support library ii libnet1 1.1.2.1-2 library for the construction and h ii libpcap0.7 0.7.2-7 System interface for user-level pa ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 guessnet recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 0.58+rm Dear submitter, as the package guessnet has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1084746 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
