Greetings All, Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed. Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is Product.ycp being dropped completely and I should use something else? At present I am using Product to determine which instructions from a YMP match the installed system. Should I compare against something else, like /etc/SuSE-release? https://bugzilla.novell.com/show_bug.cgi?id=373367 was my report for no product installed. -- Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Benji Weber wrote:
Greetings All,
Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.
Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is Product.ycp being dropped completely and I should use something else?
At present I am using Product to determine which instructions from a YMP match the installed system. Should I compare against something else, like /etc/SuSE-release?
https://bugzilla.novell.com/show_bug.cgi?id=373367 was my report for no product installed.
-- Benjamin Weber
Well, products is the only open topic with respect of installed and non-installed resolvables. Klaus, Michael, should we agree on something? Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Duncan Mac-Vicar P. <dmacvicar@suse.de> [Mar 31. 2008 15:09]:
Benji Weber wrote:
Greetings All,
Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed. [...]
Well, products is the only open topic with respect of installed and non-installed resolvables. Klaus, Michael, should we agree on something?
It is my understanding that we will follow the same path as with patches: - products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management] Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
It is my understanding that we will follow the same path as with patches:
- products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management]
Yes I am aware of that. Now I am trying to jump from layer 30 to layer 1 and figure out the implementation of the APIs benji pointed out. This leaves us with one restriction, unless you have a installation url as repo, you won't see any product (which makes sense). In that case the implementation of installed products would be to look all products (coming from the repo) and give the satisfied ones. is that correct? Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Duncan Mac-Vicar P. napsal(a):
Klaus Kaempf wrote:
It is my understanding that we will follow the same path as with patches:
- products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management]
Yes I am aware of that. Now I am trying to jump from layer 30 to layer 1 and figure out the implementation of the APIs benji pointed out.
This leaves us with one restriction, unless you have a installation url as repo, you won't see any product (which makes sense).
In that case the implementation of installed products would be to look all products (coming from the repo) and give the satisfied ones. is that correct?
I'm afraid this 'might' break (or needn't work correctly) in case of Upgrade from media (Installation->Upgrade) as we often do not have access to network-based repositories when upgrading using CD/DVD media. Lukas
Lukas Ocilka wrote:
I'm afraid this 'might' break (or needn't work correctly) in case of Upgrade from media (Installation->Upgrade) as we often do not have access to network-based repositories when upgrading using CD/DVD media.
The repo is cached locally or? Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Duncan Mac-Vicar Prett napsal(a):
Lukas Ocilka wrote:
I'm afraid this 'might' break (or needn't work correctly) in case of Upgrade from media (Installation->Upgrade) as we often do not have access to network-based repositories when upgrading using CD/DVD media.
The repo is cached locally or?
The repo might but needn't be cached locally (on a target). User downloads DVD of openSUSE 11.0 and boots from it. After that he/she selects Upgrade in the Installation Mode dialog. Then he/she choses the root partition of the system to upgrade and inst-sys initializes the target. If the repository is remote, it might fail as we don't need to have network available. Moreover, on a running system, some products (e.g., Add-Ons) might require a base product to be installed before. If an installation repository of that product is not available (e.g., anymore), solver will keep requesting it or might offer not to install the Add-On - even if the base product is installed and all dependencies (but missing product) are fulfilled. L.
* Lukas Ocilka <lukas.ocilka@suse.cz> [Apr 07. 2008 10:08]:
I'm afraid this 'might' break (or needn't work correctly) in case of Upgrade from media (Installation->Upgrade) as we often do not have access to network-based repositories when upgrading using CD/DVD media.
Do we need the installed product when we upgrade to a newer one ? I currently know of two places where this information is shown 1. Partition selector (in case there are multiple partitions with a valid distribution) 2. Installation overview In case 1 its helpful to have this information, in case 2 its just completeness of information and can be easily dropped, or ? I can imagine two ways of retrieving this information A. the /etc/<xyz>-release files (<xyz> because there might be multiple products) B. the bootloader entry (/boot/grub/menu.lst) Bottom line: There are alternatives for retrieving (an un-authorative) information about the installed product(s) Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dne Monday 31 of March 2008 15:41:42 Klaus Kaempf napsal(a):
* Duncan Mac-Vicar P. <dmacvicar@suse.de> [Mar 31. 2008 15:09]:
Benji Weber wrote:
Greetings All,
Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.
[...]
Well, products is the only open topic with respect of installed and non-installed resolvables. Klaus, Michael, should we agree on something?
It is my understanding that we will follow the same path as with patches:
- products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management]
Since we have to work also without any repository (and thus without any product to be computed), we will need to adapt this part of YaST functionality to get the product information from the related package. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
https://bugzilla.novell.com/show_bug.cgi?id=373367 was my report for no product installed.
... and there are few more * https://bugzilla.novell.com/show_bug.cgi?id=367809 (no release notes URL - no internet test possible) * https://bugzilla.novell.com/show_bug.cgi?id=368104 (yast2-repair does not work) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
On Mon, Mar 31, Benji Weber wrote:
Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.
Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is
Product (Pattern,Patch) will no longer be installed. Instead of this it is computed whether a Products dependencies are satisfied. If so, it should be treated as formerly an installed Product. 2 of the main differences to 'installing a Product': - If one disables or removes the repository providing the product, the product is gone. - If the product you installed gets 'damaged' (it's requirements are not fullfilled), it is gone. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dňa Tuesday 01 April 2008 13:09:32 Michael Andres ste napísal:
On Mon, Mar 31, Benji Weber wrote:
Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.
Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is
Product (Pattern,Patch) will no longer be installed. Instead of this it is computed whether a Products dependencies are satisfied. If so, it should be treated as formerly an installed Product.
2 of the main differences to 'installing a Product':
- If one disables or removes the repository providing the product, the product is gone.
- If the product you installed gets 'damaged' (it's requirements are not fullfilled), it is gone.
In theory, yes. In practice, we are able to determine a broken situation if the package is installed but the either repo is missing or product dependencies are not satisfied. This is important for tools like registration and YaST to work. On SLE10, it is really important that the only step you need to be able to patch your system is simply run suse_register. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 01/04/2008, Michael Andres <ma@suse.de> wrote:
On Mon, Mar 31, Benji Weber wrote:
Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.
Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is
Product (Pattern,Patch) will no longer be installed. Instead of this it is computed whether a Products dependencies are satisfied. If so, it should be treated as formerly an installed Product.
2 of the main differences to 'installing a Product':
- If one disables or removes the repository providing the product, the product is gone.
- If the product you installed gets 'damaged' (it's requirements are not fullfilled), it is gone.
Is it likely to be implemented before beta1? It would be nice if people could test YMP things such as installing codecs and using packman's YMPs earlier on in beta phase. Especially as I have exams all through the final release cycle so won't be doing bugfixing. Also Product::name alone is used in at least 12 different ycp files, so I suspect lack of product is going to break other things. -- Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Mon, Apr 07, Benji Weber wrote:
On 01/04/2008, Michael Andres <ma@suse.de> wrote:
- If the product you installed gets 'damaged' (it's requirements are not fullfilled), it is gone.
Is it likely to be implemented before beta1? It would be nice if
I think so. The solver now provides a function to test whether a solvable is 'satsfied' (not broken). Now we can make them available in the pool. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (9)
-
Benji Weber -
Duncan Mac-Vicar P. -
Duncan Mac-Vicar Prett
-
Jiri Srain -
Katarina Machalkova -
Klaus Kaempf -
Lukas Ocilka -
Michael Andres -
Stanislav Visnovsky