gt; not surprising that ruby3.1 doesn't define its internal versions any
> more, and the attached patch can probably be applied?
glibc 2.38 is now in unstable, so upgrading the severity to serious.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel..
its test suite
> depends on access to the internet,
As network access is forbidden by Debian Policy section 4.9, this is
actually a serious bug. Changing the severity accordingly.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net
bian.net/data/autopkgtest/testing/amd64/p/puma/35598629/log.gz
Could you please have a look? It's annoying for other maintainers to get
their package blocked by this one.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net h
Source: nanoc
Version: 4.12.5-2
Severity: serious
On 2022-01-29 16:19, Debian FTP Masters wrote:
>
>
> Version check failed:
> Your upload included the binary package ruby-nanoc-deploying, version
> 1.0.1-2, for all,
> however testing already has version 1.0.1-2.
> Uploads to unstable must have
Package: ruby-ffi
Version: 1.12.2+dfsg-2
Severity: normal
Tags: ftbfs patch upstream
User: debian-ri...@lists.debian.org
Usertags: riscv64
Forwarded:
https://github.com/ffi/ffi/commit/3a280f70a36b56239d149d6205d20933151a2af3
Hi,
ruby-ffi fails to build on riscv64 with the following testsuite e
testingfrom testing
Unfortunately I have not been able to reproduce this behaviour.
In my testing, the autopktest failure happens already happen in pure
testing (i.e. glibc 2.31-13), and it also appears with testing + glibc
2.31-16. I therefore don't believe glibc has anyt
Source: rubygems
Version: 3.2.0~rc.1-2
Severity: serious
- Forwarded message from Debian FTP Masters
-
From: Debian FTP Masters
To: all Build Daemon
Date: Mon, 19 Oct 2020 03:49:20 +
Subject: rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED
Message-Id:
Version check failed:
Yo
