| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Jason Stubbs wrote: |
| 5 |
|
| 6 |
>On Monday 19 September 2005 15:00, gentuxx wrote: |
| 7 |
> |
| 8 |
>>does updating a package for a security fix using the "--oneshot" option |
| 9 |
>>update the same package that is "housed" in the "world" tree? |
| 10 |
> |
| 11 |
> |
| 12 |
>There is no world "tree". There is only a "list". --oneshot has no |
| 13 |
affect on |
| 14 |
>this list. |
| 15 |
> |
| 16 |
>>If so, can I assume that the same package will be updated next time I |
| 17 |
>>update "world"? Meaning, if I run "--oneshot" for |
| 18 |
>>mozilla-firefox-1.0.6-r7 and mozilla-firefox-1.0.7-r1 comes out, will |
| 19 |
>>1.0.6-r7 be upgraded to 1.0.7-r1? |
| 20 |
> |
| 21 |
> |
| 22 |
>If it was in the world list prior to you running --oneshot, it'll still be |
| 23 |
>in the world list afterward. Hence, it will be updated with world. |
| 24 |
> |
| 25 |
>>If every security fix comes out with "--oneshot" being recommended, |
| 26 |
>>how do I know if it's a dependency of a package in world, or an entity |
| 27 |
>>in world? (This seems like an extension of the questioning above.) |
| 28 |
> |
| 29 |
> |
| 30 |
>What does it matter in the context of a security update? |
| 31 |
|
| 32 |
|
| 33 |
Well, I'm trying to see if I can get a better understanding of how it |
| 34 |
all fits together. But, I want to make sure that I don't have 2 |
| 35 |
packages running around on the system (1 patched, and 1 NOT patched). |
| 36 |
|
| 37 |
> |
| 38 |
>>Also, for the most recent firefox update, I would run the command as |
| 39 |
>>recommended with the "-p" flag, and it would see the package. If I |
| 40 |
>>run "emerge -Dupv mozilla-firefox" I only get a few of the (supposed) |
| 41 |
>>dependencies, and not the package itself, while the package installed |
| 42 |
>>(when I do "emerge search mozilla-firefox") is 1.0.6-r5. |
| 43 |
> |
| 44 |
> |
| 45 |
>If that is the case then 1.0.6-r5 is the latest version available for you |
| 46 |
>with respect to your current snapshot of the tree. |
| 47 |
|
| 48 |
|
| 49 |
Well, I did an "emerge sync" right before issuing the command above. |
| 50 |
I would think that if the updated package is available for |
| 51 |
"--oneshot", it would be available when I run "emerge -Du(p)v world". |
| 52 |
But that didn't seem to be the case. |
| 53 |
|
| 54 |
Again, I'm just trying to understand how this all fits together. |
| 55 |
|
| 56 |
Thanks. |
| 57 |
|
| 58 |
|
| 59 |
- -- |
| 60 |
gentux |
| 61 |
echo "hfouvyAdpy/ofu" | perl -pe 's/(.)/chr(ord($1)-1)/ge' |
| 62 |
|
| 63 |
gentux's gpg fingerprint ==> 34CE 2E97 40C7 EF6E EC40 9795 2D81 924A |
| 64 |
6996 0993 |
| 65 |
-----BEGIN PGP SIGNATURE----- |
| 66 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 67 |
|
| 68 |
iD8DBQFDLuNtLYGSSmmWCZMRArF+AJ9gFfQRgSb2ciNNreJ0lNSUbmkZiwCg0m9i |
| 69 |
6bkDqhDyVSr4fT/X7GvuRTI= |
| 70 |
=K2Vt |
| 71 |
-----END PGP SIGNATURE----- |
| 72 |
|
| 73 |
-- |
| 74 |
gentoo-user@g.o mailing list |
Archives