Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 543390 - GLSA 201503-06 - cannot fix GLSA, no unaffected packages available
Summary: GLSA 201503-06 - cannot fix GLSA, no unaffected packages available
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: GLSA Errors (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Security
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-15 06:35 UTC by Kirill Elagin
Modified: 2016-07-02 07:18 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kirill Elagin 2015-03-15 06:35:07 UTC
~~~~
$ glsa-check -f affected
Fixing GLSA 201503-06
>>> cannot fix GLSA, no unaffected packages available
~~~~

~~~~
$ glsa-check -p 201503-06
Checking GLSA 201503-06
>>> No upgrade path exists for these packages:
     dev-libs/icu-51.2-r1
~~~~

On the other hand, manually running the command from the advisory gives a correct resolution:

~~~~
$ emerge --ask --oneshot --verbose ">=dev-libs/icu-54.1-r1"
These are the packages that would be merged, in order:

Calculating dependencies                                   ... done!  
[ebuild     U  ] dev-libs/icu-54.1-r1:0/54a [51.2-r1:0/51.2] USE="-debug -doc -examples -static-libs" ABI_X86="(64%*) (-32) (-x32)" 24,889 KiB

Total: 1 package (1 upgrade), Size of downloads: 24,889 KiB
~~~~

Well, this doesn’t actually look as an GLSA text error but I wasn’t sure which component to choose.
Comment 1 Aaron Bauman (RETIRED) gentoo-dev 2016-07-02 03:16:04 UTC
The versions of packages addressed in that GLSA are no longer in the tree.  Have you had any additional issues with this matter?
Comment 2 Kirill Elagin 2016-07-02 07:17:09 UTC
Ugh, well, I don‘t know. This should probably be closed as obsolete.
Comment 3 Aaron Bauman (RETIRED) gentoo-dev 2016-07-02 07:18:10 UTC
(In reply to Kirill Elagin from comment #2)
> Ugh, well, I don‘t know. This should probably be closed as obsolete.

Correct, just wanted to make sure you didn't have any other issues.  Please let us know if you do.