From owner-freebsd-ports-bugs@freebsd.org Wed Oct 2 13:41:04 2019 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7287212F745 for ; Wed, 2 Oct 2019 13:41:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46jy2m2NQTz4RD4 for ; Wed, 2 Oct 2019 13:41:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 51BCA12F744; Wed, 2 Oct 2019 13:41:04 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5183C12F743 for ; Wed, 2 Oct 2019 13:41:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46jy2m18pDz4RD0 for ; Wed, 2 Oct 2019 13:41:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0C58B2C406 for ; Wed, 2 Oct 2019 13:41:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x92Df3k4097954 for ; Wed, 2 Oct 2019 13:41:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x92Df3TN097953 for ports-bugs@FreeBSD.org; Wed, 2 Oct 2019 13:41:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 241012] sysutils/iocage No such command since update to 1.2 Date: Wed, 02 Oct 2019 13:41:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-ports@jan0sch.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: araujo@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 13:41:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241012 Bug ID: 241012 Summary: sysutils/iocage No such command since update to 1.2 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: araujo@FreeBSD.org Reporter: freebsd-ports@jan0sch.de Flags: maintainer-feedback?(araujo@FreeBSD.org) Assignee: araujo@FreeBSD.org Hi, I just upgraded the sysutils/iocage port (via py36-iocage package) on some = of my machines from 1.1 to 1.2 and it seems that all commands are gone. For example `iocage list` is supposed to list all jails. But after the upda= te I get this: % iocage list Usage: iocage [OPTIONS] COMMAND [ARGS]... Try "iocage --help" for help. Error: No such command "list". % iocage --help Usage: iocage [OPTIONS] COMMAND [ARGS]... A jail manager. Options: -v, --version Display iocage's version and exit. -f, --force Allow iocage to rename datasets. -D, --debug Log debug output to the console. --help Show this message and exit. Commands: migrate Migrate all iocage_legacy develop basejails to new clonejails. On a machine still using the "old" package everything works and the command gives the following output: % iocage --help Usage: iocage [OPTIONS] COMMAND [ARGS]... A jail manager. Options: -v, --version Display iocage's version and exit. -f, --force Allow iocage to rename datasets. --help Show this message and exit. Commands: activate Set a zpool active for iocage usage. chroot Chroot to a jail. clean Destroy specified dataset types. clone Clone a jail. console Login to a jail. create Create a jail. debug Create a directory with all the debug for iocage jails. destroy Destroy specified jail(s). df Show resource usage of all jails. exec Run a command inside a specified jail. export Exports a specified jail. fetch Fetch a version of FreeBSD for jail usage or a preconfigured.= .. fstab Manipulate the specified jails fstab. get Gets the specified property. import Import a specified jail. list List a specified dataset type, by default lists all jails. migrate Migrate all iocage_legacy develop basejails to new clonejails. pkg Use pkg inside a specified jail. rename Rename a jail. restart Restarts the specified jails or ALL. rollback Rollbacks the specified jail. set Sets the specified property. snaplist Show snapshots of a specified jail. snapremove Remove specified snapshot of a jail. snapshot Snapshots the specified jail. start Starts the specified jails or ALL. stop Stops the specified jails or ALL. update Run freebsd-update to update a specified jail to the latest... upgrade Run freebsd-update to upgrade a specified jail to the RELEASE= ... Any ideas what might have gone wrong? Regards, Jens --=20 You are receiving this mail because: You are the assignee for the bug.=