Hi,

This week is shorter than usual because of the holiday tomorrow, so I am
sending my report today:

ruby-mocha
==========

It is blocked by ruby-bourne for more than 3 months. ruby-bourne does not
support ruby 3.1 and it was removed from Debian testing. Requested its
removal (and ruby-terrapin as a reverse dependency) here:

https://bugs.launchpad.net/ubuntu/+source/ruby-bourne/+bug/2015231

ruby-influxdb
=============

Its tests were failing. Re-triggered tham and they passed.

ruby-moneta
===========

It is blocked by ruby-upr. ruby-upr was removed from Debian because
upstream is dead and it was also blocking ruby-moneta there. I filed
another removal request:

https://bugs.launchpad.net/ubuntu/+source/ruby-upr/+bug/2015298

ruby-oauth2
===========

It is blocked in -proposed because of ruby-github-api test failure.
ruby-github-api was already removed from Debian testing and unstable to
allow ruby-oauth2 migration. I'd say we need to do the same in Ubuntu, so
filed this removal request:

https://bugs.launchpad.net/ubuntu/+source/ruby-jeweler/+bug/2015305

The ruby-oauth2 migration will also allow ruby-omniauth-google-oauth2
migration.

ruby-foreman
============

It failed to build due to some test failures, they happened because $TERM
was not set which caused some noise in the output of the commands executed
by the tests. I uploaded ruby-foreman/0.87.2-2 to Debian unstable fixing
that and synced it into Ubuntu.

ruby-celluloid
==============

The latest Debian upload added a Breaks statement that will not let
ruby-celluloid-io and ruby-eye be installable (there is no version greater
than the one in Breaks in any release). I got in touch with the uploader to
understand what was his intent when doing that and uploading it to
unstable. We have the same set of failures in Debian.

php-dapphp-radius
=================

The upload stuck in -proposed is trying to fix autopkgtest and it was done
by Debian as well. Synced version 2.5.8-3 after checking the diff and
consulted Athos who has been working on that.

singularity-container
=====================

It is failing to build because of a conflict between the Spec definition in
golang-github-opencontainers-runc-dev (vendored code) and in
golang-github-opencontainers-specs-dev. I updated LP #1882225 with the
latest findings but I was not able to fix it yet.

r-cran-rstan
============

It fails to build only on armhf. There is a upstream bug where a discussion
was started by the Debian maintainer, I filed this bug to track this issue:

https://bugs.launchpad.net/ubuntu/+source/r-cran-rstan/+bug/2015506

Lucas Kanashiro.
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Reply via email to