Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
User Guide › Reference › Binary Package Tracking
ContentsContents
User Guide
  1. About this Guide
  2. I First Steps
    1. 1 Beginnerʼs Guide
  3. II Concepts
    1. 2 Supported Build Recipes and Package Formats
  4. III Setup
    1. 3 osc, the Command Line Tool
    2. 4 Build Configuration
  5. IV Usage
    1. 5 Basic OBS Workflow
    2. 6 Local Building
    3. 7 Using Source Services
    4. 8 SCM/CI Workflow Integration
    5. 9 Staging Workflow
    6. 10 Notifications
    7. 11 Moderation
  6. V Best Practices
    1. 12 Using the OBS Web UI
    2. 13 Basic Concepts and Work Styles
    3. 14 How to integrate external SCM sources
    4. 15 Publishing Upstream Binaries
    5. 16 Bootstrapping
    6. 17 osc Example Commands
    7. 18 Advanced Project Setups
    8. 19 Building Kernel Modules
    9. 20 Common Questions and Solutions
  7. VI Reference
    1. 21 OBS Architecture
    2. 22 OBS Concepts
    3. 23 Build Process
    4. 24 Build Containers
    5. 25 Source Management
    6. 26 SCM Bridge
    7. 27 Supported Formats
    8. 28 Request And Review System
    9. 29 Image Templates
    10. 30 Multiple Build Description File Handling
    11. 31 Maintenance Support
    12. 32 Binary Package Tracking
    13. 33 Administration
    14. 34 Scheduling and Dispatching
    15. 35 Build Constraints
    16. 36 Building Preinstall Images
    17. 37 Authorization
    18. 38 Quality Assurance(QA) Hooks
    19. 39 openSUSE Factory
  8. Glossary
  9. A GNU Licenses
Navigation←→
User Guide › Reference › Binary Package Tracking
Top
←→

32 Binary Package Tracking

32.1 Which Binaries Are Tracked?
32.2 What Data Is Tracked?
32.3 API Search Interface

Products and updates to them are often officially supported by a company. To allow giving such support, there is binary package tracking. This feature allows checking which exact version of a package was shipped at what time. This feature is often important for release managers, maintenance engineers, QA engineers and supporters.

OBS can track these binary packages and offer a database to search them.

32.1 Which Binaries Are Tracked?

All binaries which are released into projects providing kind=maintenance_release are tracked. In addition to that, the OBS administrator can configure additional projects via the packtrack setting in BSConfig.pm.

32.2 What Data Is Tracked?

In short the information to identify a binary, its building place and timestamps are tracked. In addition to that also information about possible successor versions or if the binary got removed in the meantime. If products do reference the repositories the search interface offers also a listing of products which are supposed to use it. Either as part of the product media itself or in one of its update repositories.

32.2.1 Binary Identifier

A binary is identified by the following information which is extracted from components of the file path of the binary:

  • Repository:  Where is the binary hosted?

  • Name:  Name of the binary file

  • Epoch:  The epoch version (optional, usually not used)

  • Version:  The version

  • Release:  The release number

  • Architecture:  The hardware architecture

  • Medium:  Name of the medium (exists only for product builds)

32.2.2 Binary Information

Additional information about a binary is information which gets updated when a binary gets added or replaced.

  • operation, got the binary added, removed or modified

  • publish time, aka the time when the repository gets published by OBS. This is not the same time as when the release action got invoked.

  • build time

  • obsolete time, exists only when a binary gets removed or replaced

  • supportstatus, meta information about the level of support which is granted for the binary at the time of releasing it.

  • updateinfo id from rpm-md repository

  • maintainer of the binary who has prepared this update

  • disturl, the exact identifier to the source and build repository

32.2.3 Product information

Additional information about products referencing to this binary.

  • updatefor: the listed products do reference the repository as update channel.

  • product: exists when the binary was part of a product medium

32.3 API Search Interface

The search of released binaries is provided via the following API endpoints:

  • /search/released/binary/id : short form, just listing the matched binary identifiers. See the reference documentation.

  • /search/released/binary : long form, provides all other tracked information as described above. See the reference documentation.

Please visit the before mentioned links to get details and several examples of how to use these API endpoints.

→Chapter 33 Administration←Chapter 31 Maintenance Support
Print this page

© 2024 SUSE