Package: uuid-runtime
Version: 2.41-5
Severity: serious
Justification: Breaks production system which need the current time
stored in timeuuids
Tags: trixie forky sid

Just noticed that basically my complete infrastructure broke because
uuid-runtime doesn't create correct uuids anymore. The data stored in
my databases is now off by two hours:

```
#include <stdio.h>
#include <uuid/uuid.h>
#include <time.h>

int main() {
    uuid_t uuid;
    char uuid_str[37];
    char time_str[64];
    time_t timestamp;
    struct timeval tv;
    struct tm *tm_info;

    // Generate a time-based UUID (version 1)
    uuid_generate_time(uuid);

    // Convert the UUID to a string representation
    uuid_unparse(uuid, uuid_str);

    // Print the UUID
    printf("Time-based UUID: %s\n", uuid_str);

    // Extract the timestamp from the UUID
    timestamp = uuid_time(uuid, &tv);

    // Print the extracted timestamp
    printf("Timestamp (seconds since epoch): %ld\n", (long)timestamp);
    printf("Timestamp (with microseconds): %ld.%06ld\n",
           (long)tv.tv_sec, (long)tv.tv_usec);

    // Convert to UTC time
    tm_info = gmtime(&timestamp);
    strftime(time_str, sizeof(time_str), "%Y-%m-%d %H:%M:%S UTC", tm_info);
    printf("Human-readable time (UTC): %s\n", time_str);

    return 0;
}
```

$  gcc -o uuid_gen uuid_gen.c -luuid

when I run it now, I get:

```
$  date -u; ./uuid_gen
Di 3. Feb 13:00:08 UTC 2026
Time-based UUID: 80a1a41a-00ef-11f1-8000-2cf05d047039
Timestamp (seconds since epoch): 1770116408
Timestamp (with microseconds): 1770116408.045673
Human-readable time (UTC): 2026-02-03 11:00:08 UTC
```

You can also double check this with https://www.famkruithof.net/uuid/uuidgen

When I install  uuid-runtime_2.38.1-5+deb12u3_amd64.deb from bookworm
(on the same system) then I get the correct output:

```
$  date -u; ./uuid_gen
Di 3. Feb 13:02:01 UTC 2026
Time-based UUID: 87a7a1cc-0100-11f1-8afe-2cf05d047039
Timestamp (seconds since epoch): 1770123721
Timestamp (with microseconds): 1770123721.273390
Human-readable time (UTC): 2026-02-03 13:02:01 UTC
```


Btw. I see this problem on systems which have UTC set as its timezone.
My local system has Europe/Berlin set as its timezone and sees it too.

Reply via email to