Paul Gevers writes:
> Please no epoch, we'll go back to the normal versioning scheme in due
> time I'd hope. Debian policy has a section on it [1], that also explain
> what to do instead.
Oh, right, I'll do that. Though if it's acceptable, I might wait a
little bit longer after double-checkin
Hi Rob
On 06-08-2024 03:25, Rob Browning wrote:
Though if it's acceptable, I might wait a
little bit longer after double-checking to see if there's a chance the
relevant people upstream might be about to look in to it. If not, or if
it needs to happen sooner, I'll proceed.
Take your time, we'
Paul Gevers writes:
> Take your time, we're not in a hurry, but the autoremoval timer is
> ticking [1]. It would be a shame if it's removed while you know a path
> forward.
I'm planning to upload the downgrade in the next few days.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
Source: guile-3.0
Version: 3.0.9-1
Severity: serious
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Crit
Paul Gevers writes:
> This bug will trigger auto-removal when appropriate. As with all new
> bugs, there will be at least 30 days before the package is auto-removed.
That sounds appropriate in this case. Unstable is how we found out
about the upstream bug (https://debbugs.gnu.org/71891), which
Hi Rob,
On 04-08-2024 22:02, Rob Browning wrote:
Paul Gevers writes:
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
That sounds appropriate in this case.
Because you replied, I just checked, but
Paul Gevers writes:
> With my Release Team member hat on, I rather have it sooner then.
> Because there will be enough to manage later.
By all means, if that makes things easier for y'all. Do we have any
(sensible) option to just replace it with the trixie version? i.e. it'd
be nice to avoid h
Hi,
On 05-08-2024 05:10, Rob Browning wrote:
Paul Gevers writes:
With my Release Team member hat on, I rather have it sooner then.
Because there will be enough to manage later.
By all means, if that makes things easier for y'all. Do we have any
(sensible) option to just replace it with the
8 matches
Mail list logo
