On Wed, Aug 24, 2011 at 3:22 PM, James Antill <ja...@fedoraproject.org> wrote:
> On Wed, 2011-08-24 at 14:09 +0200, tim.laurid...@gmail.com wrote:
>> On Tue, Aug 23, 2011 at 8:44 PM, James Antill <ja...@and.org> wrote:
>> > ---
>> > output.py | 3 +++
>> > 1 files changed, 3 insertions(+), 0 deletions(-)
>> >
>> > diff --git a/output.py b/output.py
>> > index 00e0e6f..db64eff 100755
>> > --- a/output.py
>> > +++ b/output.py
>> > @@ -1423,6 +1423,9 @@ Transaction Summary
>> > (_('Remove'), len(self.tsInfo.removed) +
>> > len(self.tsInfo.depremoved)),
>> > (_('Reinstall'), len(self.tsInfo.reinstalled)),
>> > (_('Downgrade'), len(self.tsInfo.downgraded)),
>> > + (_('Skipped (dependency problems)'),
>> > len(self.skipped_packages)),
>> > + (_('Not installed'), len(self._not_found_i.values())),
>> > + (_('Not available'), len(self._not_found_a.values())),
>> > ):
>> > if count: out.append('%-9s %5d %s\n' % (
>> > action, count, P_('Package', 'Packages', count),
>> > --
>> > 1.7.6
>> >
>> > _______________________________________________
>> > Yum-devel mailing list
>> > Yum-devel@lists.baseurl.org
>> > http://lists.baseurl.org/mailman/listinfo/yum-devel
>> >
>>
>> Stupid question, What does it mean when a package is 'not installed'
>> and 'not available', feels at little strange to me
>
> It's used with "ts-load" and "history redo/undo/etc." where we have a
> set of packages that are to be install/updated/removed/etc. ... if say
> we want to remove blah-1.0 but that isn't installed, then it's added to
> the "Not installed" list.
>
> _______________________________________________
> Yum-devel mailing list
> Yum-devel@lists.baseurl.org
> http://lists.baseurl.org/mailman/listinfo/yum-devel
>
ACK
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
