Up2Date "size" column

[Sean Earp]

Hello All-

For as long as I can remember, up2date has always put   0k    in the 
size field for every single package that it offers to update.   If you 
select multiple updates, it will tell you that it has maybe 7k to 
download, when in fact you are downloading 80+ MB of packages.   Is 
there a technological reason for this incorrect representation?  Is 
there any purpose for having the size field displayed when the 
information is completely erroneous?  It has been  a problem for so 
long that I don't know if it should be thrown at bugzilla, or if I (we) 
should just keep living with it.  Any thoughts?

-Sean


GPG public key:  <http://homepage.mac.com/smearp/seanpgp.asc>

[Will H. Backman]

On Thu, 2004-04-01 at 09:34, Sean Earp wrote:
>  Hello All-
>  
>  For as long as I can remember, up2date has always put   0k    in the 
>  size field for every single package that it offers to update.   If you 
>  select multiple updates, it will tell you that it has maybe 7k to 
>  download, when in fact you are downloading 80+ MB of packages.   Is 
>  there a technological reason for this incorrect representation?  Is 
>  there any purpose for having the size field displayed when the 
>  information is completely erroneous?  It has been  a problem for so 
>  long that I don't know if it should be thrown at bugzilla, or if I (we) 
>  should just keep living with it.  Any thoughts?
>  
>  -Sean
>  
>  
>  GPG public key:  <http://homepage.mac.com/smearp/seanpgp.asc>
>   
I see that also in the graphical up2date.

[William Hooper]

Sean Earp said:
>  Hello All-
>
>  For as long as I can remember, up2date has always put   0k    in the
>  size field for every single package that it offers to update. 
Only since up2date started using a yum backend.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107048

-- 
William Hooper