Your message dated Fri, 12 Apr 2024 19:05:38 +
with message-id
and subject line Bug#1068810: fixed in sch-rnd 1.0.5-2
has caused the Debian Bug report #1068810,
regarding sch-rnd: hardcoded librnd4 dependency
to be marked as done.
This means that you claim that the problem has been dealt
Gianfranco Costamagna writes:
> yes, but the library was renamed in librnd4t64, so either you need to
> depend on the new one, or drop it, to let the auto decrufter finish
> the time64_t transition and decruft it.
Ah, thank you, that's a useful observation. Since the relevant version
hasn't
control: reopen -1
control: severity -1 serious
On Thu, 11 Apr 2024 13:17:44 -0600 Bdale Garbee wrote:
The librnd4 runtime dependency is needed to ensure at least a minimum
version of that library is available so required capability is present.
The "hard coded" dependency is not actually a
act ow...@bugs.debian.org
immediately.)
--
1068810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sch-rnd
Version: 1.0.5-1
Severity: normal
Tags: patch
Hello, I found that l
Gianfranco Costamagna writes:
> Hello, I found that librnd4 is correctly evaluated from shlibs:Depends
> in the core library and then it can be dropped also on core
> reverse-dependencies.
The point of the dependency is to require version 4.1.0 or later, since
that's the librnd version that
5 matches
Mail list logo
