[opensuse-factory] how to investigate problem of DUD file not handled by yast ?
Hello there, I want to provide a new powerpc-utils rpm via a DUD, for yast to use this new rpm rather than the one from installed DVD. Is it supposed to work ? My trials are not successfull, and the y2log continue to show installation of "old" rpm from DVD. I am not able to find in y2log a reference to a repo that could be associated to the DUD file retrieved by linuxrc. Do you have any idea on how I should investigate such problem ? I tried using mkdud either pointing to a dir (1) or a specific rpm (2) but that do not change the behaviour. === (1) $mkdud -c boo1011529_3.dud --dist tw /home/michel/buildtmp/build-root/standard-ppc64le/home/abuild/rpmbuild/RPMS/ppc64le/ === (2) $mkdud -c boo1011529_5.dud --dist tw /home/michel/buildtmp/build-root/standard-ppc64le/home/abuild/rpmbuild/RPMS/ppc64le/powerpc-utils-1.3.2-9.ppc64le.rpm === linuxrc output extract: ok, ip = 10.0.2.15/24 Loading http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1011529_5.dud - 100% http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1011529_5.dud: adding to installation system Driver Updates added: ~normand/boo1011529_5.dud === -- Michel Normand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 24/11/2016 11:41, Normand wrote:
Hello there,
I want to provide a new powerpc-utils rpm via a DUD, for yast to use this new rpm rather than the one from installed DVD.
Is it supposed to work ?
My trials are not successfull, and the y2log continue to show installation of "old" rpm from DVD.
I am not able to find in y2log a reference to a repo that could be associated to the DUD file retrieved by linuxrc.
Do you have any idea on how I should investigate such problem ?
I tried using mkdud either pointing to a dir (1) or a specific rpm (2) but that do not change the behaviour.
=== (1) $mkdud -c boo1011529_3.dud --dist tw /home/michel/buildtmp/build-root/standard-ppc64le/home/abuild/rpmbuild/RPMS/ppc64le/
=== (2) $mkdud -c boo1011529_5.dud --dist tw /home/michel/buildtmp/build-root/standard-ppc64le/home/abuild/rpmbuild/RPMS/ppc64le/powerpc-utils-1.3.2-9.ppc64le.rpm
=== linuxrc output extract: ok, ip = 10.0.2.15/24 Loading http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1011529_5.dud - 100% http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1011529_5.dud: adding to installation system Driver Updates added: ~normand/boo1011529_5.dud ===
The dud is handled by linuxrc as creating a mounted squashfs (1) But how this dud information is supposed to be passed between linuxrc and yast ? (1) === 1:linux-0mhb:~ # mount |grep mp_0005 /dev/loop7 on /mounts/mp_0005 type squashfs (ro,relatime) === 1:linux-0mhb:~ # find /mounts/mp_0005 -name powerpc-utils\* /mounts/mp_0005/linux/suse/ppc64le-tw/install/powerpc-utils-1.3.2-9.ppc64le.rpm 1:linux-0mhb:~ # ls -la /mounts/mp_0005/linux/suse/ppc64le-tw/install/ total 239 drwxr-xr-x 2 root root 94 Nov 24 10:39 . drwxr-xr-x 4 root root 64 Nov 24 10:39 .. -rw-r--r-- 1 root root 243168 Nov 24 10:36 powerpc-utils-1.3.2-9.ppc64le.rpm -rwxr-xr-x 1 root root 191 Nov 24 10:36 update.post2 -rwxr-xr-x 1 root root 910 Nov 24 10:36 update.pre === -- Michel Normand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I want to provide a new powerpc-utils rpm via a DUD, for yast to use this new rpm rather than the one from installed DVD.
Is it supposed to work ?
Yes, it is. At least it works for me in SLES12-SP2.
$mkdud -c boo1011529_3.dud --dist tw /home/michel/buildtmp/build-root/standard-ppc64le/home/abuild/rpmbuild/RPMS/ppc64le/
My suspection is that the "tw" distribution name actually does not match the real Tumbleweed identification seen by linuxrc and then the DUD is ignored...
The dud is handled by linuxrc as creating a mounted squashfs (1) But how this dud information is supposed to be passed between linuxrc and yast ?
Linuxrc creates /add_on_products.xml file which is then read by YaST, it should contain something like this: # cat /add_on_products.xml <?xml version="1.0"?> <add_on_products xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <product_items config:type="list"> <product_item> <name>Driver Update 0</name> <url>dir:///update/000/repo?alias=DriverUpdate0</url> <priority config:type="integer">50</priority> </product_item> </product_items> </add_on_products> The URL should point to the directory with your packages (/update/000/repo in this case). Check that the directory is there and contains the expected packages. In this case it was tested in SLE12-SP2 with "--dist sle12" option. Unfortunately I do not know what's the correct distribution identifier for Tumbleweed... :-( Or maybe there is bug in linuxrc and it does not create that add_on_products.xml file. -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 25/11/2016 15:31, Ladislav Slezak wrote:
I want to provide a new powerpc-utils rpm via a DUD, for yast to use this new rpm rather than the one from installed DVD.
Is it supposed to work ?
Yes, it is. At least it works for me in SLES12-SP2.
$mkdud -c boo1011529_3.dud --dist tw /home/michel/buildtmp/build-root/standard-ppc64le/home/abuild/rpmbuild/RPMS/ppc64le/
My suspection is that the "tw" distribution name actually does not match the real Tumbleweed identification seen by linuxrc and then the DUD is ignored...
The dud is handled by linuxrc as creating a mounted squashfs (1) But how this dud information is supposed to be passed between linuxrc and yast ?
Linuxrc creates /add_on_products.xml file which is then read by YaST, it should contain something like this:
# cat /add_on_products.xml <?xml version="1.0"?> <add_on_products xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <product_items config:type="list"> <product_item> <name>Driver Update 0</name> <url>dir:///update/000/repo?alias=DriverUpdate0</url> <priority config:type="integer">50</priority> </product_item> </product_items> </add_on_products>
The URL should point to the directory with your packages (/update/000/repo in this case). Check that the directory is there and contains the expected packages.
In this case it was tested in SLE12-SP2 with "--dist sle12" option. Unfortunately I do not know what's the correct distribution identifier for Tumbleweed... :-(
Or maybe there is bug in linuxrc and it does not create that add_on_products.xml file.
Thank you Ladislav for those details. I just created a new bug https://bugzilla.suse.com/show_bug.cgi?id=1012241 to continue investigation. -- Michel Normand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2016-11-25 at 16:27 +0100, Normand wrote:
I just created a new bug https://bugzilla.suse.com/show_bug.cgi?id=10 12241 to continue investigation.
Check /var/log/linuxrc.log (during installation). It should provide some insight. -- Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Ladislav Slezak -
Martin Wilck -
Normand