#32295: "Skipping obsolete configuration option." doesn't say which one -------------------------------------------------+------------------------- Reporter: arma | Owner: nickm Type: defect | Status: | assigned Priority: Medium | Milestone: Tor: | 0.4.2.x-final Component: Core Tor/Tor | Version: Tor: | 0.4.2.1-alpha Severity: Normal | Resolution: Keywords: network-team-roadmap-november, | Actual Points: 042-backport | Parent ID: #29211 | Points: 0.5 Reviewer: | Sponsor: | Sponsor31-must -------------------------------------------------+-------------------------
Comment (by nickm): My suggestion would be to change how OBSOLETE is implemented: it doesn't really make sense as a type. Instead, there should be an "empty" type for fields that can't be read or written, and a CFLG_OBSOLETE flag that causes these warnings. The CFLG_OBSOLETE flag should be handled at the confvar layer, I think. This makes more sense for 0.4.3 than 0.4.2, though. Personally I think it would almost be okay to leave this as-is in 0.4.2, since we haven't made any options obsolete that weren't obsolete before. But if we think we really need a temporary fix there, we could pass the name down to the typedvar layer in any kludgey way we want. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32295#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs