Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 525
    • Issues 525
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #1751

Closed
Open
Created Apr 09, 2020 by Michal Nowak@mnowakOwner

abi-check does not know which source is older, newer

We are not bumping the API version number compared to the reference version, so this results in abi-checker being unable to discern which version is "older" and which one is "newer". As a result, it uses git commit hashes to tell them apart. In case of https://gitlab.isc.org/isc-projects/bind9/-/jobs/814076 current HEAD of v9_16 to be treated as "old":

Report: compat_reports/libns/1601.0.0-2c0adf7e5a_to_1601.0.0-d497c325e7/compat_report.html
commit d497c325e70400f082bf59f61430e3f20a708d0d
Author: Tinderbox User <tbox@isc.org>
Date:   Wed Mar 11 16:35:45 2020 +0000

commit 2c0adf7e5abf1ad7932eb845e7dce9231e505d45
Merge: e11d690ae7 ad79e7c080
Author: Ondřej Surý <ondrej@isc.org>
Date:   Wed Apr 8 15:13:10 2020 +0000
Assignee
Assign to
Time tracking