Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-73605

tzdata in c10s (2024a) lags behind c9s (2024b)

XMLWordPrintable

    • No
    • Low
    • rhel-sst-pt-libraries
    • ssg_platform_tools
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • CentOS Stream
    • None
    • None
    • None
    • All
    • None

      What were you trying to do that didn't work?

      Migrate systems from CentOS Stream 9 to CentOS Stream 10 without packages being downgraded

      What is the impact of this issue to you?

      Having an inconsistent timezone database between systems on c9s and the new systems being provisioned with c10s

      Please provide the package NVR for which the bug is seen:

      $ fedrq pkgs --notsrc tzdata -b c10s
      tzdata-2024a-3.el10.noarch

      $ fedrq pkgs --notsrc tzdata -b c9s
      tzdata-2024b-3.el9.noarch

      How reproducible is this bug?:

      Always

      Steps to reproduce

      See fedrq invocation above

      Expected results

      c10s version >= c9s version

      Actual results

      c10s version < c9s version

            [RHEL-73605] tzdata in c10s (2024a) lags behind c9s (2024b)

            Carlos O'Donell added a comment -

            In practice c9s and c10s are distinct distributions, and may downgrade components to resolve technical issues, there is no explicit guarantee that you won't get a downgrade.

            In this particular case we know that tzdata is zone data form upstream IANA so we can make the assumption that we want to avoid a regression.

            This should have been fixed on our about the exact time you filed the issue since the builds were already in progress: https://kojihub.stream.centos.org/koji/buildinfo?buildID=73274

            Carlos O'Donell added a comment - In practice c9s and c10s are distinct distributions, and may downgrade components to resolve technical issues, there is no explicit guarantee that you won't get a downgrade. In this particular case we know that tzdata is zone data form upstream IANA so we can make the assumption that we want to avoid a regression. This should have been fixed on our about the exact time you filed the issue since the builds were already in progress: https://kojihub.stream.centos.org/koji/buildinfo?buildID=73274

              pfrankli Patsy Griffin
              michel.lind Michel Lind
              Patsy Griffin Patsy Griffin
              Michal Kolar Michal Kolar
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: