openSUSE Autoinstall June 2020

autoinstall@lists.opensuse.org

3 participants
4 discussions

Re: [opensuse-autoinstall] when using autoyast, can a specific version of a package be required?
by Brian Reichert 29 Jun '20

29 Jun '20

On Mon, Jun 29, 2020 at 04:45:31PM +0100, Imobach Gonz?lez Sosa wrote: > Perhaps I am missing something, but mixing packages for multiple releases in > the same repository does not look like a good idea at all. Why not just having > a separate repository for each release? OBS[1] can help with that. Until I got this far down the road, I did not think this was an issue. But, this advice is valuable, and I will look into the pointer you've provided. Thanks! > [..] > > Regards, > Imo > > [1] https://openbuildservice.org/ > > -- > Imobach Gonz?lez Sosa > Blog: https://imobachgs.github.io/ > Twitter: @imobachgs -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

Re: [opensuse-autoinstall] when using autoyast, can a specific version of a package be required?
by Brian Reichert 29 Jun '20

29 Jun '20

On Mon, Jun 29, 2020 at 10:53:05AM -0300, Perry Werneck wrote: > Hi, > > I think you can do this using a meta-package requiring the bash in the exat > version you need. I suppose I should be transparent about what I'm trying to accomplish: At $WORK, we produce SUSE-based appliances for customers, ultimately delivered as an OVA. Internally, we do not use repositories for deployment via autoyast; we have some home-rolled mechanism that is showing it's age. I've been exploring, with some success, using a single private repository, to contain our RPMs of multiple releases, and with 'zypper', I can with fine detail, describe installation and upgrade tasks. (I'm using 'createrepo' to manage that metadata.) I'm now exploring deployments via autoyast, and am finding I don't have the fine-grained control that zypper offers, to declare 'deploy with version 4 vs version 5'. I was considering your suggestion, maintaining a meta-RPM that called out specific dependencies, but as I would implicitly want multiple versions of that meta-RPM, I still suffer from the constraint of <package> in autoyast not letting me call out version numbers. It's entirely possible there's richer metadata in my repo I can manage (for example, I don't really get 'products' yet) that would get me over this planning, if this tactic was in fact possible. > -- > Perry Werneck > Bras??lia/DF -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] when using autoyast, can a specific version of a package be required?
by Brian Reichert 26 Jun '20

26 Jun '20

This is in a SLES 12 SP5 environment, not opensuse, but I'm having difficulty getting questions answered in the SLES web forums. So, I'm poking at folks here. When I use autoyast to introduce a package, I can name the package: <package>bash</package> If a repository has more than one version of a package, autoyast seems to default to using the latest version available. bash-4.3-82.1.x86_64.rpm bash-4.3-83.23.1.x86_64.rpm How can I, via autoyast, communicate I want a specific version? I tried to use <package>bash-4.3-82.1</package> But yast2 said 'no such package in the repository' (I'm paraphrasing here.) -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] using custom repository via AutoYast is not employed
by Brian Reichert 25 Jun '20

25 Jun '20

I've asked this in a SLES forum, but no feedback yet: https://forums.suse.com/discussion/14815/using-custom-repository-via-autoya… is-not-employed And, I've sent email to yast-devel(a)opensuse.org, but that messsage is hung up, awaiting moderator approval. To repeat those details here: I'm exploring maintaining a private repository, and am trying to employ it via AutoYast, all under SLES 12 SP5. I'm hoping someone can provide some guidance. I realize this is an opensuse list, but I'm hoping autoyast syntax is the same across these distributions. I added this to my autoinst.xml file: <add-on> <add_on_others config:type="list"> <listentry> <media_url><![CDATA[http://10.153.19.116/repo/]]></media_url> <product>Example Product</product> <alias>example</alias> <product_dir>/</product_dir> <priority>30</priority> </listentry> </add_on_others> </add-on> But, when I also declare a package from that repository to install, YaST throws errors: 2020-06-18 17:31:15 <3> install(18178) [Ruby] modules/AutoinstSoftware.rb:1096 Cannot select following packages for installation: 2020-06-18 17:31:15 <3> install(18178) [Ruby] modules/AutoinstSoftware.rb:1099 java-13_0_2-openjdk : The package is not available. (selected by AutoYaST con figuration file) And I see no evidence that YaST attempted to process my repository in the logs. I can confirm the repository has the package: localhost:~ # zypper addrepo http://10.153.19.116/repo/ example Adding repository 'example' ..............................................[done] Repository 'example' successfully added URI : http://10.153.19.116/repo/ Enabled : Yes GPG Check : Yes Autorefresh : No Priority : 99 (default priority) Repository priorities are without effect. All enabled repositories share the same priority. localhost:~ # zypper pa -ir example | grep java-13_0_2-openjdk v | example | java-13_0_2-openjdk | 13.0.2-8.2 | x86_64 -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2020