On Mon, 2014-10-13 at 16:45 -0500, Bruce Dubbs wrote:
> I've created a script that should run at 1135 GMT daily that sends a 
> summary of out-of-date packages to blfs-book.  It looks like:
> 
>              BLFS Package        BLFS Version             Latest
> chapter 04: nettle              2.7.1                    3.0
> chapter 11: ImageMagick         6.8.9-7                  6.8.9-8
> chapter 12: colord              1.2.3                    1.2.4
> chapter 12: obex-data-server    0.4.6                    0
> chapter 13: nasm                2.11.05                  0
> chapter 13: python3             3.4.2                    3.3.6
> chapter 13: ruby                2.1.3                    2.2.0-preview1
> chapter 17: lynx                2.8.8rel.2               2.8.9dev.1
> chapter 24: MesaLib             10.3.0                   10.3.1
> chapter 24: xf86-video-intel    2.99.916                 2.21.15
> chapter 25: gdk-pixbuf          2.31.1                   2.30.8
> chapter 25: gtk+2               2.24.24                  2.24.25
> chapter 27: kactivities         4.13.3                   check
> chapter 27: kde-workspace       4.11.12                  check
> chapter 30: gjs                 1.41.91                  1.41.4
> chapter 32: parole              0.5.4                    0.7.0
> chapter 36: firefox             32.0.1                   32.0.3
> chapter 39: x264                snapshot-20141008-2245   daily
> 
> ---------
> 
> Note 1: Some packages are in the ticket system waiting for some event. 
> For example: nettle and parole.
> 
> Note 2: A 0 (zero) in the latest column means that the upstream site is 
> down or has changed something to prevent the current script from 
> determining the latest package version.
> 
> Note 3: At times we use a development version of the package.  For 
> example: xf86-video-intel, gdk-pixbuf, and gjs.
> 
> Note 4: The upstream structure of how packages are made available make 
> it difficult to determine the real latest stable version of a package. 
> For example: ruby, lynx, kactivities, kde-workspace.
> 
> Note 5: We normally only update ImageMagick for new point versions. For 
> example: 6.8.x where x changes.
> 
> Note 6: x264 changes daily.
> 
> Note 7: Some packages have already been updated today so gtk+2, colord, 
> and MesaLib will not show up in the next run.
> 
>    -- Bruce

Hello Bruce,

Thank you for the clarification of this with the notes.  It answered the
question I had with regards to zero in the latest column.

I periodically manually check for updated versions on the upstream
servers as well as using your currency check, as I know that things can
change during the time that the script is run.

Regards,

Christopher.

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to