Devuan Excalibur is Debian Trixie.

Hi all,

I'd like to report what looks like a repository synchronization issue with tzdata on Devuan Daedalus, and ask whether this is a known problem.

## System

- Devuan Daedalus (based on Debian 13 / Trixie, i.e. deb13 packages)
- Architecture: amd64
- Sources: deb.devuan.org/merged (daedalus, daedalus-updates, daedalus-security)

## Problem

After a routine `apt update`, APT proposed an "upgrade" of tzdata from the installed
2026b-0+deb13u1 to 2026c-0+deb12u1. Note the version string: the candidate is a
*deb12* (Bookworm) build, while the installed package is a *deb13* build.

`apt list --upgradable -a`:

    tzdata/oldstable-security 2026c-0+deb12u1 all [upgradable from: 2026b-0+deb13u1]
    tzdata/now 2026b-0+deb13u1 all [installed,upgradable to: 2026c-0+deb12u1]
    tzdata/oldstable 2026b-0+deb12u1 all
    tzdata/oldstable-updates 2025b-0+deb12u1 all

At first, installing the candidate failed with a dependency conflict:

    Dependency resolution failed:
    The following packages have unmet dependencies:
      tzdata-legacy: Conflicts: tzdata-bookworm

Attempting the upgrade with `apt install -t daedalus-security tzdata` still pulled the
deb12 build from daedalus-security:

    Get:1 http://deb.devuan.org/merged daedalus-security/main amd64 tzdata all 2026c-0+deb12u1 [304 kB]

The upgrade then removed tzdata-legacy, and as a knock-on effect also removed:

    unar, gnustep-base-common, gnustep-base-runtime, libgnustep-base1.31

`apt-cache policy tzdata` afterwards:

    tzdata:
      Installed: 2026c-0+deb12u1
      Candidate: 2026c-0+deb12u1
      Version table:
     *** 2026c-0+deb12u1 500
            500 http://deb.devuan.org/merged daedalus-security/main amd64 Packages
            100 /var/lib/dpkg/status
         2026b-0+deb12u1 500
            500 http://deb.devuan.org/merged daedalus/main amd64 Packages
         2025b-0+deb12u1 500
            500 http://deb.devuan.org/merged daedalus-updates/main amd64 Packages

As you can see, every available version of tzdata in the daedalus repositories is a
deb12 build, even though the rest of the system is deb13.

## Questions

1. Is this a known issue? I could not find an existing bug report for it.
2. Is the deb12 build of tzdata in daedalus-security intentional, or is this a
   synchronization problem where the deb13 build has not yet propagated to the
   Devuan mirrors?
3. Until a proper deb13 build is available, is holding tzdata (`apt-mark hold tzdata`)
   the recommended workaround?
4. Is there a known way to keep both tzdata and tzdata-legacy installed, or is the
   conflict between them expected on this release?

I've held tzdata for now to avoid repeating the mismatched upgrade. Happy to provide
more logs if useful.

Thanks.