' /usr/bin/ruby.ruby2.2 -I/usr/lib64/ruby/gems/2.2.0/gems/rspec-support-3.2.2/lib:/usr/lib64/ruby/gems/2.2.0/gems/rspec-core-3.2.3/lib /usr/lib64/ruby/gems/2.2.0/gems/rspec-core-3.2.3/exe/rspec --pattern spec/integration/\*\*/\*_spec.rb failed - -- James Mason Technical Architect, Public Cloud openSUSE Member SUSE jmason at suse.com - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXWdDZAAoJEBs5UYhsRJAj5IwH/3/dWrXLF6YYnzllhm2uf/m1 DUJkxJXxuEbeYhCUQyPsVyf9wRCksUL38fyLjFDi71RgAM8J9Sr0OYc4CVMs4xwV iSHLvgO2oaaADbyHY7KJ9J/3FaM7M72Gb4CVk+xti2bAfd+oufZkgxC/pnQRwLhB rSVlJR9Au9zaK896DhzsToCo/pLMFWC4PVZTp539JvdgDweujkZimhfq+LhixjaD MrrlHUlCYd1huyY9mwPKQa8ZFLHFUkcwmrATT3zMBLszs26pxnuM59xcjoErIUg4 /3OnTk6xPRmnOZef8i7KaHzVOOye/LTTFwrGYAS1S/L8fLQibaS7mKHNiorK2b0= =gJxt -----END PGP SIGNATURE----- From mamorales at suse.de Fri Jun 10 06:59:42 2016 From: mamorales at suse.de (Mauro Morales) Date: Fri, 10 Jun 2016 14:59:42 +0200 Subject: [Machinery] Checked out machinery - getting a test failure In-Reply-To: <1465503961.9258.30.camel@suse.com> References: <1464111135.3016.67.camel@suse.com> <574EF059.2060303@suse.de> <1465503961.9258.30.camel@suse.com> Message-ID: <575AB9BE.3030001@suse.de> On 06/09/2016 10:26 PM, James Mason wrote: > While all the tests pass now, the suite still fails out, assuming > pennyworth is installed locally: Machinery expects to have pennyworth installed in the same parent directory. In my case I have both under ~/src as you can see below: $ tree -L 1 . ??? machinery ??? pennyworth From JMason at suse.com Mon Jun 13 12:26:21 2016 From: JMason at suse.com (James Mason) Date: Mon, 13 Jun 2016 18:26:21 +0000 Subject: [Machinery] Checked out machinery - getting a test failure In-Reply-To: <575AB9BE.3030001@suse.de> References: <1464111135.3016.67.camel@suse.com> <574EF059.2060303@suse.de> <1465503961.9258.30.camel@suse.com> <575AB9BE.3030001@suse.de> Message-ID: <1465842379.585.15.camel@suse.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Fri, 2016-06-10 at 14:59 +0200, Mauro Morales wrote: > > On 06/09/2016 10:26 PM, James Mason wrote: > > While all the tests pass now, the suite still fails out, assuming > > pennyworth is installed locally: > Machinery expects to have pennyworth installed in the same parent > directory. In my case I have both under ~/src as you can see below: > > ?$ tree -L 1 > . > ??? machinery > ??? pennyworth >? Are there any plans to support `pennyworth` on _any_ of our current OS offerings?? I see it's not supported with SLES 12 SP1, SLES 11 SP4, openSUSE Leap 42.1, or openSUSE Tumbleweed - only SLES 12 GA and openSUSE 13.2. - -- James Mason Technical Architect, Public Cloud openSUSE Member SUSE jmason at suse.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXXvrLAAoJEBs5UYhsRJAjcVYH/31Vo+C9WabRv2bSlBdNuL+A p3ymlwAh9kMutIBrzzgzZjW+ZgUzZWHTht3DMXcMLg7rCuNK//h9l3lVXTB0XRxQ c1wdZ4SdWgBe7aJemBc4Cl8Aoa7DRfA+rFelyHE2VYJzpUrIgF1/cfqwZlrDkp3a KCn6LV+ePgx83cUkkuxh56DZfn8hsWpxL+ME6eTafYJZw+aK1jf2MgM6Wu5fKB4/ jxqOts247TZvkSWHgPMKZrRgkWXNRaSTjRuZ3FO0kVBNkxJV0hpN+jYcE3jyK0WI 5SIsx6KUMAOlgVCsFgokJeqqXBmV2SWKZlXd22XaW/dJbUre9JdLFA3NOKlCJH4= =ygwK -----END PGP SIGNATURE----- From cschum at suse.de Mon Jun 13 19:26:16 2016 From: cschum at suse.de (Cornelius Schumacher) Date: Tue, 14 Jun 2016 03:26:16 +0200 Subject: [Machinery] Checked out machinery - getting a test failure In-Reply-To: <1465842379.585.15.camel@suse.com> References: <1464111135.3016.67.camel@suse.com> <575AB9BE.3030001@suse.de> <1465842379.585.15.camel@suse.com> Message-ID: <2192476.ZdC3BLW8a1@linux-j6w7> On Monday 13 June 2016 18:26:21 James Mason wrote: > On Fri, 2016-06-10 at 14:59 +0200, Mauro Morales wrote: > > On 06/09/2016 10:26 PM, James Mason wrote: > > Are there any plans to support `pennyworth` on _any_ of our current OS > offerings? > I see it's not supported with SLES 12 SP1, SLES 11 SP4, openSUSE Leap > 42.1, or openSUSE Tumbleweed - only SLES 12 GA and openSUSE 13.2. It actually should work on the current versions of our OS offering. That's where we are developing and testing. Where do you get the support state from, from documentation or code? -- Cornelius Schumacher From JMason at suse.com Tue Jun 14 09:44:36 2016 From: JMason at suse.com (James Mason) Date: Tue, 14 Jun 2016 15:44:36 +0000 Subject: [Machinery] Checked out machinery - getting a test failure In-Reply-To: <2192476.ZdC3BLW8a1@linux-j6w7> References: <1464111135.3016.67.camel@suse.com> <575AB9BE.3030001@suse.de> <1465842379.585.15.camel@suse.com> <2192476.ZdC3BLW8a1@linux-j6w7> Message-ID: <1465919073.3973.7.camel@suse.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, 2016-06-14 at 03:26 +0200, Cornelius Schumacher wrote: > On Monday 13 June 2016 18:26:21 James Mason wrote: > > On Fri, 2016-06-10 at 14:59 +0200, Mauro Morales wrote: > > > On 06/09/2016 10:26 PM, James Mason wrote: > >? > > Are there any plans to support `pennyworth` on _any_ of our current > OS > > offerings?? > > I see it's not supported with SLES 12 SP1, SLES 11 SP4, openSUSE > Leap > > 42.1, or openSUSE Tumbleweed - only SLES 12 GA and openSUSE 13.2. > > It actually should work on the current versions of our OS offering. > That's? > where we are developing and testing.? > > Where do you get the support state from, from documentation or code? Both: https://github.com/SUSE/pennyworth#installation https://github.com/SUSE/pennyworth/blob/master/lib/pennyworth/commands/ setup_command.rb#L45 My experience on Tumbleweed: $ bin/pennyworth setup Warning: Pennyworth is not tested upstream on this platform. Use at your own risk. Installing packages: ? * Installing curl... ? * Installing iptables... ? * Installing dnsmasq... ? * Installing libxml2-devel... ? * Installing libxslt-devel... ? * Installing libvirt-devel... ? * Installing libvirt... ? * Installing expect... Reloading udev rules Installing libvirt plugin for Vagrant... Pennyworth experienced an unexpected error. Please file a bug report at https://github.com/SUSE/pennyworth/issues/new. Execution of "vagrant plugin install --plugin-version\=0.0.30 vagrant- libvirt" failed with status 1: Bundler, the underlying system Vagrant uses to install plugins, (...). Error output: Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: An error occurred while installing ruby-libvirt (0.6.0), and Bundler cannot continue. Make sure that `gem install ruby-libvirt -v '0.6.0'` succeeds before bundling. Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. ????/opt/vagrant/embedded/bin/ruby extconf.rb? *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers.??Check the mkmf.log file for more details.??You may need configuration options. Provided configuration options: --with-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/opt/vagrant/embedded/bin/ruby --with-libvirt-include --without-libvirt-include --with-libvirt-lib --without-libvirt-lib --with-libvirt-config --without-libvirt-config --with-pkg-config --without-pkg-config /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:434:in `try_do': The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first. from /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:519:in `try_link0' from /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:534:in `try_link' from /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:620:in `block in try_ldflags' from /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:613:in `with_ldflags' from /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:619:in `try_ldflags' from /opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:1725:in `pkg_config' from extconf.rb:72:in `

' Gem files will remain installed in /home/jmason/.vagrant.d/gems/gems/ruby-libvirt-0.6.0 for inspection. Results logged to /home/jmason/.vagrant.d/gems/gems/ruby-libvirt- 0.6.0/ext/libvirt/gem_make.out Standard output: Installing the 'vagrant-libvirt --version '0.0.30'' plugin. This can take a few minutes... Backtrace: /usr/lib64/ruby/gems/2.2.0/gems/cheetah-0.5.0/lib/cheetah.rb:641:in `check_errors' /usr/lib64/ruby/gems/2.2.0/gems/cheetah-0.5.0/lib/cheetah.rb:404:in `run' /home/jmason/projects/github/pennyworth/lib/pennyworth/commands/setup_c ommand.rb:135:in `install_vagrant_plugin' /home/jmason/projects/github/pennyworth/lib/pennyworth/commands/setup_c ommand.rb:31:in `execute' /home/jmason/projects/github/pennyworth/lib/pennyworth/cli.rb:118:in `block (2 levels) in ' /usr/lib64/ruby/gems/2.2.0/gems/gli- 2.14.0/lib/gli/command_support.rb:126:in `call' /usr/lib64/ruby/gems/2.2.0/gems/gli- 2.14.0/lib/gli/command_support.rb:126:in `execute' /usr/lib64/ruby/gems/2.2.0/gems/gli- 2.14.0/lib/gli/app_support.rb:296:in `block in call_command' /usr/lib64/ruby/gems/2.2.0/gems/gli- 2.14.0/lib/gli/app_support.rb:309:in `call' /usr/lib64/ruby/gems/2.2.0/gems/gli- 2.14.0/lib/gli/app_support.rb:309:in `call_command' /usr/lib64/ruby/gems/2.2.0/gems/gli-2.14.0/lib/gli/app_support.rb:83:in `run' bin/pennyworth:25:in `

' - -- James Mason Technical Architect, Public Cloud openSUSE Member SUSE jmason at suse.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXYCZhAAoJEBs5UYhsRJAjO4wH/1ZtrCa6OIAIyc8A4UYYnBVy T/uVJPFqIEbp/mbUBuQrMNECqbqubODc6wFpwf7l/dkkJMLaxo+lYpjHsbAObknz GxKQBkf1fl3tR44geX+RXfuloHPe3ruE2dQgELKDNnmifI/tAp5wSFOIspJxzeHL yD2O0RvDmEUaRqjxzkUiVJdRprUmkfFd/q9BRD7HQOELQ68TZOjWfB35Fl8Aqe2J otWwY+xJPCDRcMe+MyrncCMUYxBOvtDmLPNCoTPxFy4uTniZ3gaejJOa5YgKi87/ 9ODmPV0TCEyKfAUyun/eUmLP8U8FR5wZyYDBCHc7vhWKQuvoTCkkEQrEgLih7gs= =f3J2 -----END PGP SIGNATURE----- From matwey.kornilov at gmail.com Thu Jun 23 04:11:14 2016 From: matwey.kornilov at gmail.com (Matwey V. Kornilov) Date: Thu, 23 Jun 2016 13:11:14 +0300 Subject: [Machinery] machinery kiwi-export requires unmanaged-files Message-ID: Hello, machinery export-kiwi says: The scope 'unmanaged-files' is part of the system description but the corresponding files weren't extracted during inspection. So, how could I avoid exporting unmanaged files to kiwi description? I really don't need them for fresh kiwi build. From mschnitzer at suse.de Thu Jun 23 04:29:04 2016 From: mschnitzer at suse.de (Manuel Schnitzer) Date: Thu, 23 Jun 2016 12:29:04 +0200 Subject: [Machinery] machinery kiwi-export requires unmanaged-files In-Reply-To: References: Message-ID: <20160623122904.7762ec3a@suse.de> Hi Matwey, you can specify the scopes you'd like to inspect with -s Here's a list of all available scopes: http://machinery-project.org/machinery_main_scopes.1/ Manuel On Thu, 23 Jun 2016 13:11:14 +0300 "Matwey V. Kornilov" wrote: > Hello, > > > machinery export-kiwi says: > > The scope 'unmanaged-files' is part of the system description but the > corresponding files weren't extracted during inspection. > > So, how could I avoid exporting unmanaged files to kiwi description? > I really don't need them for fresh kiwi build. > > _______________________________________________ > Machinery mailing list > Machinery at lists.suse.com > http://lists.suse.com/mailman/listinfo/machinery -- Manuel Schnitzer, SUSE Manager Team SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) GPG Fingerprint: 9D2E 219D 6B71 77A7 E666 909C 8753 CB67 DEFD C709 From matwey.kornilov at gmail.com Thu Jun 23 05:20:09 2016 From: matwey.kornilov at gmail.com (Matwey V. Kornilov) Date: Thu, 23 Jun 2016 14:20:09 +0300 Subject: [Machinery] machinery kiwi-export requires unmanaged-files In-Reply-To: <20160623122904.7762ec3a@suse.de> References: <20160623122904.7762ec3a@suse.de> Message-ID: Thank you, this works. p.s. scopes are named with underscores instead of dashed on http://machinery-project.org/machinery_main_scopes.1/ 23.06.2016 13:29, Manuel Schnitzer ?????: > Hi Matwey, > > you can specify the scopes you'd like to inspect with -s > > Here's a list of all available scopes: > http://machinery-project.org/machinery_main_scopes.1/ > > Manuel > > > On Thu, 23 Jun 2016 13:11:14 +0300 > "Matwey V. Kornilov" wrote: > >> Hello, >> >> >> machinery export-kiwi says: >> >> The scope 'unmanaged-files' is part of the system description but the >> corresponding files weren't extracted during inspection. >> >> So, how could I avoid exporting unmanaged files to kiwi description? >> I really don't need them for fresh kiwi build. >> >> _______________________________________________ >> Machinery mailing list >> Machinery at lists.suse.com >> http://lists.suse.com/mailman/listinfo/machinery > > > From matwey.kornilov at gmail.com Thu Jun 23 05:28:08 2016 From: matwey.kornilov at gmail.com (Matwey V. Kornilov) Date: Thu, 23 Jun 2016 14:28:08 +0300 Subject: [Machinery] machinery: kiwi and filesystem Message-ID: Hello, I am running machinery 1.20.0 (I suppose the latest). I do inspect + export-kiwi. In config.xml I see the following: whereas my target filesystem is btrfs. Is it just unsupported, or I am doing it wrong? From mschnitzer at suse.de Thu Jun 23 05:42:45 2016 From: mschnitzer at suse.de (Manuel Schnitzer) Date: Thu, 23 Jun 2016 13:42:45 +0200 Subject: [Machinery] machinery kiwi-export requires unmanaged-files In-Reply-To: References: <20160623122904.7762ec3a@suse.de> Message-ID: <20160623134245.2b07b04a@suse.de> Hi Matwey, I'm glad I helped you. Thanks btw. for reporting that issue. I opened an issue on GitHub for that: https://github.com/SUSE/machinery/issues/2117 Manuel On Thu, 23 Jun 2016 14:20:09 +0300 "Matwey V. Kornilov" wrote: > > Thank you, this works. > > p.s. scopes are named with underscores instead of dashed on > http://machinery-project.org/machinery_main_scopes.1/ > -- Manuel Schnitzer, SUSE Manager Team SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) GPG Fingerprint: 9D2E 219D 6B71 77A7 E666 909C 8753 CB67 DEFD C709 From mschnitzer at suse.de Thu Jun 23 05:57:50 2016 From: mschnitzer at suse.de (Manuel Schnitzer) Date: Thu, 23 Jun 2016 13:57:50 +0200 Subject: [Machinery] machinery: kiwi and filesystem In-Reply-To: References: Message-ID: <20160623135750.0bd02889@suse.de> Hi Matwey, On Thu, 23 Jun 2016 14:28:08 +0300 "Matwey V. Kornilov" wrote: > Hello, > > I am running machinery 1.20.0 (I suppose the latest). No, the current release is 1.21.0. It might take a while until the package is available for all of our products because it'll go through many reviews. If you always want to get the latest version of Machinery, you can add the systems management repository to your distribution. How it works: 1. Go to https://build.opensuse.org/package/repositories/systemsmanagement:machinery/machinery and select your distribution 2. Click "Go to download repository" 3. Copy the URL 4. Type as root `zypper ar [COPIED_LINK] systemsmanagement:machinery` 5. Refresh your repositories `zypper ref` 6. Now run an update `zypper up` - if nothing happens, try `zypper dup` (I'm not sure if `up` is enough) 7. Done! > I do inspect + export-kiwi. In config.xml I see the following: > > boot="vmxboot/suse-leap42.1" format="qcow2" bootloader="grub2"/> > > whereas my target filesystem is btrfs. Is it just unsupported, or I > am doing it wrong? > So you did an inspection of your system and it recognizes "ext3" as file system but you're actually using "btrfs" ? Maybe search inside the kiwi config for "btrfs". Manuel -- Manuel Schnitzer, SUSE Manager Team SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) GPG Fingerprint: 9D2E 219D 6B71 77A7 E666 909C 8753 CB67 DEFD C709 From matwey.kornilov at gmail.com Thu Jun 23 06:03:10 2016 From: matwey.kornilov at gmail.com (Matwey V. Kornilov) Date: Thu, 23 Jun 2016 15:03:10 +0300 Subject: [Machinery] machinery: kiwi and filesystem In-Reply-To: <20160623135750.0bd02889@suse.de> References: <20160623135750.0bd02889@suse.de> Message-ID: 23.06.2016 14:57, Manuel Schnitzer ?????: > Hi Matwey, > > On Thu, 23 Jun 2016 14:28:08 +0300 > "Matwey V. Kornilov" wrote: > >> Hello, >> >> I am running machinery 1.20.0 (I suppose the latest). > > No, the current release is 1.21.0. It might take a while until the > package is available for all of our products because it'll go through > many reviews. > > If you always want to get the latest version of Machinery, you can add > the systems management repository to your distribution. > > How it works: > 1. Go to > https://build.opensuse.org/package/repositories/systemsmanagement:machinery/machinery > and select your distribution > 2. Click "Go to download repository" > 3. Copy the URL > 4. Type as root `zypper ar [COPIED_LINK] systemsmanagement:machinery` > 5. Refresh your repositories `zypper ref` > 6. Now run an update `zypper up` - if nothing happens, try `zypper dup` > (I'm not sure if `up` is enough) > 7. Done! > >> I do inspect + export-kiwi. In config.xml I see the following: >> >> > boot="vmxboot/suse-leap42.1" format="qcow2" bootloader="grub2"/> >> >> whereas my target filesystem is btrfs. Is it just unsupported, or I >> am doing it wrong? >> > > So you did an inspection of your system and it recognizes "ext3" as > file system but you're actually using "btrfs" ? Maybe search inside the > kiwi config for "btrfs". > There are some installed btrfs-related packages in kiwi config. Files in ~/.machinery don't mention neither btrfs nor ext3. I suppose used filesystem is not part of machinery profile. > Manuel > From mschnitzer at suse.de Thu Jun 23 06:16:24 2016 From: mschnitzer at suse.de (Manuel Schnitzer) Date: Thu, 23 Jun 2016 14:16:24 +0200 Subject: [Machinery] machinery: kiwi and filesystem In-Reply-To: References: <20160623135750.0bd02889@suse.de> Message-ID: <20160623141624.1e55e48b@suse.de> On Thu, 23 Jun 2016 15:03:10 +0300 "Matwey V. Kornilov" wrote: > > There are some installed btrfs-related packages in kiwi config. > > > > > > Files in ~/.machinery don't mention neither btrfs nor ext3. I suppose > used filesystem is not part of machinery profile. I think this will need a little more research. The guys from the Machinery team are off till next week (it seems). It might help us to inspect the generated files from Machinery. Would you mind giving us the result of the inspection and the generated kiwi configuration? You can send the data directly to me and I'll forward it to the internal Machinery mailing list. My email address: mschnitzer at suse.com This might speed up some things. I'm not sure if they're already aware of this issue but we'll clarify that. If you want to send the data to me, please include the following files into an archive: The inspection of the system (located in ~/.machinery) and the generated kiwi configuration files. Manuel > > -- Manuel Schnitzer, SUSE Manager Team SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) GPG Fingerprint: 9D2E 219D 6B71 77A7 E666 909C 8753 CB67 DEFD C709 From matwey.kornilov at gmail.com Thu Jun 23 06:16:26 2016 From: matwey.kornilov at gmail.com (Matwey V. Kornilov) Date: Thu, 23 Jun 2016 15:16:26 +0300 Subject: [Machinery] The systemd unit state indirect is unknown Message-ID: Hello, I am running machinery 1.21.0 and do inspection of Tumbleweed system. When I try to export inspected profile, I see the following The systemd unit state indirect is unknown. manifest.json has the following about indirect { "name": "systemd-journal-remote.service", "state": "indirect" }, At the target system I see the following about joural-remote # systemctl status systemd-journal-remote.service ? systemd-journal-remote.service - Journal Remote Sink Service Loaded: loaded (/usr/lib/systemd/system/systemd-journal-remote.service; indirect; vendor preset: disabled) Active: inactive (dead) From mschnitzer at suse.com Thu Jun 23 04:27:34 2016 From: mschnitzer at suse.com (Manuel Schnitzer) Date: Thu, 23 Jun 2016 12:27:34 +0200 Subject: [Machinery] machinery kiwi-export requires unmanaged-files In-Reply-To: References: Message-ID: <20160623122734.27dc16fc@suse.de> Hi Matwey, you can specify the scopes you'd like to inspect with -s Here's a list of all available scopes: http://machinery-project.org/machinery_main_scopes.1/ Manuel On Thu, 23 Jun 2016 13:11:14 +0300 "Matwey V. Kornilov" wrote: > Hello, > > > machinery export-kiwi says: > > The scope 'unmanaged-files' is part of the system description but the > corresponding files weren't extracted during inspection. > > So, how could I avoid exporting unmanaged files to kiwi description? > I really don't need them for fresh kiwi build. > > _______________________________________________ > Machinery mailing list > Machinery at lists.suse.com > http://lists.suse.com/mailman/listinfo/machinery -- Manuel Schnitzer, SUSE Manager Team SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) GPG Fingerprint: 9D2E 219D 6B71 77A7 E666 909C 8753 CB67 DEFD C709 From aj at suse.com Thu Jun 23 23:46:52 2016 From: aj at suse.com (Andreas Jaeger) Date: Fri, 24 Jun 2016 07:46:52 +0200 Subject: [Machinery] machinery: kiwi and filesystem In-Reply-To: References: Message-ID: <576CC94C.6010803@suse.com> On 06/23/2016 01:28 PM, Matwey V. Kornilov wrote: > Hello, > > I am running machinery 1.20.0 (I suppose the latest). > I do inspect + export-kiwi. In config.xml I see the following: > > boot="vmxboot/suse-leap42.1" format="qcow2" bootloader="grub2"/> > > whereas my target filesystem is btrfs. Is it just unsupported, or I am > doing it wrong? Machinery does not inspect the filesystem currently and just writes out a default. You can change your kiwi file for your needs, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From matwey.kornilov at gmail.com Fri Jun 24 03:42:33 2016 From: matwey.kornilov at gmail.com (Matwey V. Kornilov) Date: Fri, 24 Jun 2016 12:42:33 +0300 Subject: [Machinery] machinery: kiwi and filesystem In-Reply-To: <576CC94C.6010803@suse.com> References: <576CC94C.6010803@suse.com> Message-ID: 24.06.2016 08:46, Andreas Jaeger ?????: > On 06/23/2016 01:28 PM, Matwey V. Kornilov wrote: >> Hello, >> >> I am running machinery 1.20.0 (I suppose the latest). >> I do inspect + export-kiwi. In config.xml I see the following: >> >> > boot="vmxboot/suse-leap42.1" format="qcow2" bootloader="grub2"/> >> >> whereas my target filesystem is btrfs. Is it just unsupported, or I am >> doing it wrong? > > Machinery does not inspect the filesystem currently and just writes out > a default. You can change your kiwi file for your needs, > Ok, thanks. > Andreas