 Relationships |
||||||
|
||||||
| Anonymous | Login | 2024-05-06 01:37 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0002944 | [pkg_get] regular use | major | always | 2008-11-14 21:44 | 2009-02-27 18:10 | ||
| Reporter | bfr-murphy | View Status | public | ||||
| Assigned To | phil | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | closed | ||||||
| Summary | 0002944: latest version of pkg-get added bad flag to pkgrm | ||||||
| Description |
Issue ID 0002173 was resolved by having pkg-get add the -G flag when calling pkgrm. Unfortunately, on Solaris 10 5/08 pkgrm does not have a -G command line option. This breaks trying to do 'pkg-get -u' because the pkgrm fails, and then the pkgadd fails since the previous package version is still installed. The addition informatino below contains the output from okgrm when pkg-get calls it with the -G option. |
||||||
| Additional Information |
pkgrm: illegal option -- G usage: pkgrm [-a admin] [-n] [[-M|-A] -R host_path] [-V fs_file] [-v] [-Y category[,category ...] | pkg [pkg ...]] pkgrm -s spool [-Y category[,category ...] | pkg [pkg ...]] |
||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
||||||
|
||||||
|
Notes |
|
|
(0005414) phil (manager) 2008-11-17 22:50 |
Are you saying that pkgadd now still HAS a -G option, but pkgrm, no longer does? If so, then if the prior, zone-friendly behaviour was pkgadd -G blah... ; pkgrm -G blah ... what is the new zone-friendly behaviour? |
|
(0005415) bfr-murphy (reporter) 2008-11-20 00:51 |
pkgrm does not have a -G option on a Ultra 20 running 'Solaris 10 11/06 s10x_u3wos_10 X86', or a T2000 running 'Solaris 10 8/07 s10s_u4wos_12b SPARC', or a SunBlade 100 running 'Solaris 10 5/08 s10s_u5wos_10 SPARC'. According to the pkgrm(1M) man page, and confirmed by actually running the command on those systems, the pkgrm command does not have a -G option. pkgadd on those systems does have a -G option. I do not know if this was a change, nor do I know what the correct zone-friendly method is supposed to be. As near as I can tell on the range of Solaris 10 systems (update 3, update 4, and update 5) I use, pkgadd has always had a -G option and pkgrm has never had a -G option. |
|
(0005416) philadmin (viewer) 2008-11-21 05:25 |
It may not be documented, but if it doesnt exist at all, then what is our bug 0002173 about?? |
|
(0005424) bfr-murphy (reporter) 2008-11-24 21:55 |
The first Note attached to bug 0002173 points out that pkgrm does not have a -G option. I think the issue is that if you run pkgrm from within the global zone it will remove the package from all the local zones no matter what. pkgrm does not offer the option of not removing local zone packages when it is invoked from the global zone. Since pkgadd does honor the -G option in the global zone 'pkg-get -u' removes the local CSW packages, but does not install the updated packages in the local zones. I don't know what a good solution is, but having 'pkgget -u' call pkgrm with a -G option definitely breaks things both globally and locally. The non-optimum solutions are either not having a -G option for pkgget, or not installing CSW packages in the global zone. |
|
(0005471) phil (manager) 2008-12-19 17:05 |
pkg-get 4.0 supports separate PKGADDFLAGS and PKGRMFLAGS now. |
| Copyright © 2000 - 2008 Mantis Group |  |
