I can reproduce the situation, it seems like the "--" of "--noconf" or "--no-conf" is not taken into account if not place as the first ARG.
Unknown option: no-conf Unknown option: noconf Example : rmadison -s trusty --no-conf devscripts rmadison -u debian,ubuntu --noconf devscripts * If the "no conf" option is place as first ARG, then it passes without error. I haven't read the code yet, but before going further, could you please confirm the --no-conf and --noconf work as expected if pass as first ARG ? to make sure the feature is functioning as it should. # rmadison --no-conf -s trusty devscripts devscripts | 2.14.1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el # rmadison --noconf -u debian,ubuntu devscripts debian: devscripts | 2.12.6+deb7u2 | oldoldstable | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc devscripts | 2.14.11~bpo70+1 | wheezy-backports | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc devscripts | 2.15.3 | oldstable-kfreebsd | source, kfreebsd-amd64, kfreebsd-i386 devscripts | 2.15.3+deb8u1 | oldstable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x devscripts | 2.17.6~bpo8+1 | jessie-backports | source, amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x devscripts | 2.17.6+deb9u1 | stable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x devscripts | 2.17.6+deb9u1 | stable-debug | source devscripts | 2.17.11~bpo9+1 | stretch-backports | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x devscripts | 2.17.11~bpo9+1 | stretch-backports-debug | source devscripts | 2.17.11 | testing | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x devscripts | 2.17.11 | unstable | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x devscripts | 2.17.11 | unstable-debug | source ubuntu: devscripts | 2.11.6ubuntu1 | precise | source, amd64, armel, armhf, i386, powerpc devscripts | 2.11.6ubuntu1.7 | precise-security | source, amd64, armel, armhf, i386, powerpc devscripts | 2.11.6ubuntu1.7 | precise-updates | source, amd64, armel, armhf, i386, powerpc devscripts | 2.14.1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el devscripts | 2.14.1ubuntu0.1 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el devscripts | 2.14.1ubuntu0.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el devscripts | 2.16.2ubuntu3 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x devscripts | 2.16.8ubuntu2 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x devscripts | 2.17.9build1 | artful | source, amd64, arm64, armhf, i386, ppc64el, s390x devscripts | 2.17.11 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732667 Title: rmadison --no-conf option not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1732667/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
