Re: Searching for autopkgtest regressions in Noble

[Lucas Kanashiro]

I forgot to mention but I'd like to thank Brian Murray for helping me 
with the autopkgtest SQLite database and also suggestions for 
improvements. And sharing the results for other teams was his idea as 
well :)


Em 16/04/2024 18:54, Lucas Kanashiro escreveu:

Hi everyone,

As Noble release is approaching and in the final part of the cycle we 
had some big changes in the archive (time_t transition, xz's CVE fix), 
the Server team decided to compare the autopkgtest results from before 
the end of February, more precisely 2024-02-28 (a guess of a date 
before the time_t work started), and now (2024-04-16). This comparison 
could show us any potential regression due to big changes in the 
archive, and allow us to try to address those issues before the release.


What we did is basically get the latest test result of the packages in 
all architectures before the reference date (2024-02-28) and compare 
with the latest test run (2024-04-16) of the packages on the same 
architecture. We are using the autopkgtest SQLite database available 
here [1]. I am calling it "bad news" when the tests of a package in a 
given architecture was passing before the reference date and now they 
are not.


The script I used to do this is available here [2]. And I used the 
mapping of packages and teams [3] to get the list of packages. The 
output of the script is a JSON file that looks like the following for 
one package:

"adsys": {
"arm64": {
"before": {
"result": "all tests passed",
"test_run_id": "20240227_182345_d0549@",
"triggers": "samba/2:4.19.5+dfsg-1ubuntu1",
"test_log": 
"https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/a/adsys/20240227_182345_d0549@/log.gz;

},
"after": {
"result": "at least one test failed",
"test_run_id": "20240416_122755_08ec0@",
"triggers": "sssd/2.9.4-1.1ubuntu6 c-ares/1.27.0-1.0ubuntu1 
samba/2:4.19.5+dfsg-4ubuntu9",
"test_log": 
"https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/a/adsys/20240416_122755_08ec0@/log.gz;

}
}
    },

Attached are the output of the scripts for the following teams:
- foudantions-bugs
- desktop-packages
- kernel-package
- ubuntu-server

The Server team is already going through the list to check if there is 
any real regression requiring some work. Keep in mind that not all 
packages listed there are necessarily real problems, maybe the test 
failed because of a bad trigger, or autopkgtest infra issue, so manual 
check is required to make sure this is a real regression.It is also 
important to note that the script always gets the latest test result 
before the reference date, so the failure being analysed could be a 
flaky test for instance, too.


If you have any question or suggestion on this let me know.

I hope that's useful for other teams.

[1] https://autopkgtest.ubuntu.com/static/autopkgtest.db
[2] https://github.com/lucaskanashiro/autopkgtest-diff
[3] http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.json
--
Lucas Kanashiro


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

Searching for autopkgtest regressions in Noble

[Lucas Kanashiro]

Hi everyone,

As Noble release is approaching and in the final part of the cycle we 
had some big changes in the archive (time_t transition, xz's CVE fix), 
the Server team decided to compare the autopkgtest results from before 
the end of February, more precisely 2024-02-28 (a guess of a date before 
the time_t work started), and now (2024-04-16). This comparison could 
show us any potential regression due to big changes in the archive, and 
allow us to try to address those issues before the release.


What we did is basically get the latest test result of the packages in 
all architectures before the reference date (2024-02-28) and compare 
with the latest test run (2024-04-16) of the packages on the same 
architecture. We are using the autopkgtest SQLite database available 
here [1]. I am calling it "bad news" when the tests of a package in a 
given architecture was passing before the reference date and now they 
are not.


The script I used to do this is available here [2]. And I used the 
mapping of packages and teams [3] to get the list of packages. The 
output of the script is a JSON file that looks like the following for 
one package:

"adsys": {
"arm64": {
"before": {
"result": "all tests passed",
"test_run_id": "20240227_182345_d0549@",
"triggers": "samba/2:4.19.5+dfsg-1ubuntu1",
"test_log": 
"https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/a/adsys/20240227_182345_d0549@/log.gz;

},
"after": {
"result": "at least one test failed",
"test_run_id": "20240416_122755_08ec0@",
"triggers": "sssd/2.9.4-1.1ubuntu6 c-ares/1.27.0-1.0ubuntu1 
samba/2:4.19.5+dfsg-4ubuntu9",
"test_log": 
"https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/a/adsys/20240416_122755_08ec0@/log.gz;

}
}
    },

Attached are the output of the scripts for the following teams:
- foudantions-bugs
- desktop-packages
- kernel-package
- ubuntu-server

The Server team is already going through the list to check if there is 
any real regression requiring some work. Keep in mind that not all 
packages listed there are necessarily real problems, maybe the test 
failed because of a bad trigger, or autopkgtest infra issue, so manual 
check is required to make sure this is a real regression.It is also 
important to note that the script always gets the latest test result 
before the reference date, so the failure being analysed could be a 
flaky test for instance, too.


If you have any question or suggestion on this let me know.

I hope that's useful for other teams.

[1] https://autopkgtest.ubuntu.com/static/autopkgtest.db
[2] https://github.com/lucaskanashiro/autopkgtest-diff
[3] http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.json

--
Lucas Kanashiro


bad_news_2024-02-28_ubuntu-server.json
Description: application/json


bad_news_2024-02-28_desktop-packages.json
Description: application/json


bad_news_2024-02-28_foundations-bugs.json
Description: application/json


bad_news_2024-02-28_kernel-packages.json
Description: application/json
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

+1 maintenance report

[Lucas Kanashiro]

Hi,

I had my +1 maintenance shift this week, because the archive is not opened
yet, I tried to follow-up on some bugs already tagged as update-excuses,
and checked NBS (nothing is reported there).

- ruby-celluloid

  Its migration is blocked for a while due to some breaking changes
affecting other ruby packages.  After taking a look at the current state in
Debian, I believe we should remove the packages blocking its migration
until this situation gets sorted out in Debian (those packages were removed
from Debian testing a while ago) once the archive opens for NN series. I
filed a removal request and subscribed ubuntu-archive in LP: #2029329.

- roger-router

  It is FTBFSing in Mantic because it depends on librm-dev >= 2.2.3.
librm-dev is not present in Mantic nor Debian testing (and stable) because
its current version b-d on libgupnp-1.{2,0}-dev and libgssdp-1.{2,0}-dev
and libsoup2.4. There are some patches upstream to support version 1.6 of
both libs which are available in Debian and Ubuntu but these transitions
require more changes to fully move to libsoup-3.0. More info in this
upstream issue:

  https://gitlab.com/tabos/librm/-/issues/4

  I added a comment to the upstream bug to check if there is any update on
this. More info in LP: #1998219.

- cgreen

  It is FTBFSing in s390x in Mantic, vorlon filed a bug in Debian, and it
was fixed in version 1.6.3-1. To make sure of that I uploaded it to a PPA
and it indeed built fine in all supported architectures. So once the
archive opens for the NN series the new version should be sync'ed and the
FTBFS fixed. More info in LP: #2024063.

Since this shift was a bit different, I also spent time on patch piloting,
reviewing some packages which are trying to land in the archive once it
opens (NEW packages). Also started to do some work in Debian to prepare for
the Ruby 3.2 transition that I am planning to do next cycle. src:ruby3.2 is
already in experimental, src:rubygems was patched to support both versions
of the interpreter for now (some breaking changes between ruby3.1 and
ruby3.2), and src:ruby-defaults is now uploaded to experimental to support
both versions of the interpreter. Next step is to rebuild reverse
dependencies and start to file bugs against packages FTBFSing with ruby3.2.

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

Re: Changes in the container stack

[Lucas Kanashiro]

Hi Seth,

Em 01/08/2023 23:02, Seth Arnold escreveu:

On Tue, Aug 01, 2023 at 06:45:59PM -0300, Lucas Kanashiro wrote:

With that in mind, we, the Server team, identified the need to decouple the
application (what users really use) and the library (what is used by rdeps)
in a way that, on the one hand, we can keep following upstream projects
without worrying about breaking changes and on the other hand, we keep the
library (-dev package) stable to avoid breakages of packages sync'ed from
Debian or already in stable releases during SRUs.

Hello Lucas, I'm very concerned about this plan, I hope you can assuage my
fears.


Thanks for raising your concerns. I hope I can help you clear them out :)


This sounds like we'll introduce a new problem, where third-party
applications built against the libraries will become incompatible with
the main application.


That _might_ happen (depending on how those apps are interacting) if 
they are using the -dev package in the archive to build their app. 
However, from what I have seen in the Go ecosystem, people will not be 
doing that, they will be using the vendor code from upstream, pinning 
the version they want.


For the packages in the archive depending on -dev packages, I have seen 
API changes in generic functions used by other packages (software that 
does not interact directly with the containers stack but re-use some 
exported functions). So making those rdeps use an old version of the 
library does not seem an issue most of the time, considering there is no 
interaction during runtime among those components.



If the ecosystems are changing external library ABIs too often, I can
only shudder in fear at how quickly internal library ABIs are changing.

What gives us the confidence that the internal ABIs are actually more
stable and reliable than the external ABIs?


All the breakages I have seen so far are related to API changes (TBH not 
too complex changes), the main problem is that those changes require 
backporting upstream patches which usually slow down our velocity of 
updates (in the end, we cannot follow upstream releases because SRU 
process takes too long). I haven't seen weird ABI changes.


For the container stack itself, I do some manual testing with all the 
packages and there are also DEP-8 tests which guarantee that those 3 
pieces of software work well together before I perform any upload to the 
archive. Thinking about third-party apps interacting with the stack, 
usually, those upstream projects follow the latest (or considerably new) 
version of docker/containerd/runc, so to avoid ABI breakages would be 
better to follow upstream closely. Keeping an old version of those 
software is more likely to cause ABI issues.


As I mentioned, this ecosystem moves fast, if we do not try to follow 
upstream we will not be able to provide value to those users. This is a 
problem I have seen, some users are preferring to use, for instance, the 
Docker debian package provided by the Docker upstream maintainers 
instead of ours, because we are sometimes way behind them. I have some 
plans in mind to change this scenario, the decoupling I presented here 
is just the first step to improve users' experience.


I hope my answer makes sense to you Seth. Let me know if it does not.

Cheers!

--
Lucas Kanashiro


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

Changes in the container stack

[Lucas Kanashiro]

Hi -devel,


Historically, the container stack, which is composed by src:docker.io, 
src:containerd and src:runc, has diverged from Debian to deliver the 
"upstream" experience to our users [1] instead of worrying too much 
about backward compatibility or regressions. However, recently, those 
fast-moving projects have been introducing some breaking changes which 
have impacted an increasing number of packages (Golang specifically) in 
the archive. Not just the breaking changes have been an issue but also 
the way we maintain those packages, bundling all the vendor code (rdeps 
cannot load the vendor code without introducing a delta), so we can 
easily backport them to old releases.



With that in mind, we, the Server team, identified the need to decouple 
the application (what users really use) and the library (what is used by 
rdeps) in a way that, on the one hand, we can keep following upstream 
projects without worrying about breaking changes and on the other hand, 
we keep the library (-dev package) stable to avoid breakages of packages 
sync'ed from Debian or already in stable releases during SRUs.



The way this decoupling was implemented this cycle (Mantic) can be 
summarized as follows:



- src:docker.io now provides just the -dev package (library) and it is 
in "sync" with Debian, without bundled vendor code (i.e., with proper 
dependencies on Debian packages). Sync is in quotation marks because 
there is a delta to make it not provide the docker.io binary anymore 
(application). And now there is a new src:docker.io-app, which provides 
just the application and the documentation for our users.



- The same was done to src:containerd. Now, src:containerd provides just 
the library and src:containerd-app provides the application.



- src:runc was kept as is, one source package providing application and 
library. It will very likely follow docker.io and containerd in the next 
cycle. It was not done now because it has not presented big issues, but 
for consistency we will follow the same pattern. I'll let you know once 
this happens.



The changes listed above are about to be SRU'ed to all supported 
releases [2].



With that, the -dev packages of docker.io and containerd will be kept 
stable in all supported releases from now on (also devel). And in the 
near future, the same will happen for runc. Just the -app source 
packages will be updated across all releases with major version bumps; 
I'll be working on updating the current SRU exception to cover those 
changes.



I've sent a heads-up email to people actively working on those packages 
(Security and CPC) but here is another reminder.



[1] https://wiki.ubuntu.com/DockerUpdates

[2] 
https://bugs.launchpad.net/ubuntu/lunar/+source/docker.io-app/+bug/2022390



Cheers!

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

+1 maintenance report

[Lucas Kanashiro]

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

Re: DKMS upload rights application

[Lucas Kanashiro]

The DMB voted today in favor of Paolo's application for the DKMS set, he
has been added to ~ubuntu-kernel-dkms-uploaders team now.

Congratulations Paolo!

On Tue, Feb 21, 2023 at 5:10 AM Paolo Pisati 
wrote:

> I would like to announce my application for the membership in the DKMS
> package set uploader team. My application can be found at:
>
> https://wiki.ubuntu.com/PaoloPisati/DKMSUploadApplication
>
> I have added myself to the agenda for the DMB meeting at:
>
> https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
>
> Thanks!
> --
> bye,
> p.
>
> --
> Devel-permissions mailing list
> devel-permissi...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/devel-permissions
>
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

PCS is replacing crmsh from Ubuntu Lunar onwards

[Lucas Kanashiro]

Hi,

The Canonical Server team has been maintaining/recommending crmsh as the
main tool to manage Corosync/Pacemaker clusters, but starting in Ubuntu
23.04 Lunar Lobster we will replace crmsh with PCS. PCS was promoted to the
main Ubuntu repository and is now fully supported by Canonical. For Ubuntu
23.04 Lunar Lobster, both, PCS and crmsh, will be in main and supported,
but from Ubuntu 23.10 onwards PCS will be the only supported and
recommended tool to manage Corosync/Pacemaker clusters by the Server team.

This is a warning for the crmsh users so they can plan for the migration to
PCS, since the next Ubuntu LTS release (24.04) will have PCS as the
recommended and supported tool for the purpose of managing
Corosync/Pacemaker clusters.

The Canonical Server team tried to create a page in the Ubuntu Server guide
to help users migrate from crmsh to PCS:

https://discourse.ubuntu.com/t/ubuntu-ha-migrate-from-crmsh-to-pcs/34818

If you have any questions do not hesitate to contact us (Server team).


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

Ruby 3.1 transition

[Lucas Kanashiro]

Hi everyone,

I'd like to let you know that next week I'll be starting the ruby 3.1 
transition as it was planned in the beginning of the cycle [1]. The 
transition was done in Debian already and I do not expect any blocker, 
we might need to remove some packages but I'll let AAs know if it is 
necessary.


Any feedback is welcome :)

[1] https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284

--
Lucas Kanashiro


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

+1 maintenance report

[Lucas Kanashiro]

Hi,

Below you can find mostly everything I did this week, I tried to unblock
most of the ruby related packages.

- unblock puppet-agent
  + retrigger ruby-rspec-puppet with correct triggers
  + the other test failures does not seem to be a regression, but needs
further investigation

- unblock ruby-mime-types-data
  + retrigger ruby-mime-types with correct triggers

- fix golang-github-containerd-stargz-snapshotter and
golang-github-containers-psgo FTBFSes
  + reviewed and approved a containerd patch provided by @bdrung
  + there will be a follow up fix (a more appropriate one) which will
expose the vendor code to GOPATH

- rails FTBFS
  + sync ruby-image-processing from Debian unstable (missing b-d). This is
also blocking:
* ruby-webpacker
* ruby-mail
* ruby-bootsnap
* ruby-builder
  + to sync ruby-image-processing I needed to fix the ruby-vips FTBFS in
Debian. Both were manually removed from Ubuntu.
  + uploaded ruby-vips/2.1.4-1 to Debian unstable.

- unblock ruby-mail
  + rerun redmine test with the right triggers

- ruby-pg-query FTBFS
  + it depends on the protobuf transition (new protobuf version), not sure
when this will happen.

- ruby-commonmarker blocked
  + ruby-jekyll-commonmark regression because jekyll is uninstallable, it
requires ruby-liquid < 5 and
we have ruby-liquid/5.4.0-2.
  + Debian bug for jekyll: #1017524
  + Upstream PR stuck for many months:
https://github.com/jekyll/jekyll/pull/9030

- ruby-rack-session and ruby-rackup FTBFSes
  + they require ruby-rack >= 3 and it is still in Debian experimental.

- unblock ruby-fog-core
  + blocked by ruby-fog-google -> ruby-google-api-client ->
ruby-representable -> ruby-virtus
  + fixed FTBFS in ruby-virtus/2.0.0-1 in Debian: bug #1019676

- unblock systemd
  + retriggered some tests for enr0n

- unblock ruby-omniauth
  + uploaded ruby-omniauth-oauth/1.2.0-1 from Debian experimental to
unstable to fix ruby-omniauth-bitbucket failure.
  + uploaded ruby-omniauth-multipassword/2.0.0~rc1-1 from Debian
experimental to unstable to fix its test failure.
  + filed a removal request to all other packages: LP #1999697
* they are gitlab dependencies (not shipped in Ubuntu or Debian) and
not well maintained upstream.

- unblock ruby-prawn-icon
  + emailed the debian maintainer to ask for an update to a newer version
of ruby-asciidoctor-pdf.
  + became a co-maintainer and uploaded version 2.3.4-1 to unstable, should
be synced soon.

- unblock ruby-eventmachine
  + rerun ruby-em-http-requests tests with the right triggers

This is the last work day of the year, so enjoy the break and see you all
next year!

Cheers!

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

Re: +1 maintenance report

[Lucas Kanashiro]

Hi,

Em sex., 21 de out. de 2022 19:47, Sergio Durigan Junior <
sergio.duri...@canonical.com> escreveu:

> * golang-github-containerd-stargz-snapshotter
>   - FTBFSing on Ubuntu, but not on Debian, which is strange.
>   - I've started investigating it but couldn't progress much further
> before my EOW.
>

This one requires a new containerd version to get fixed. The update will
happen in the "L" cycle. And this is not reproducible in Debian because our
containerd package differs from there.

Cheers!
Lucas Kanashiro

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

+1 maintenance report

[Lucas Kanashiro]

Hi,

This is the summary of my +1 maintenance shift from last week. I did not
manage to do more because of a local holiday and internal reviews over the
week.

# passwordsafe

There was a "regression" in arm64 which was actually not a regression. I
did run the test with migration-reference/0 and it failed anyway. Package
unblocked.

# rails

It is stuck in -proposed because the new version contains a fix for
CVE-2022-32224 which introduced a behavior change in the way hashes are
serialized. I filed LP: #1988782 and tagged it as update-excuse. Utkarsh as
one of the Debian maintainers will be pushing this forward.

# ruby-html-proofer

Fixed FTBFS. Some tests were requiring Internet access, so I skipped them
and uploaded the package to Debian. Version 3.19.2-7 contains the fix.
Package unblocked.

# tup

autopkgtest was failing because the test is expecting a binary which has
not been generated. Fixed the binary generation and uploaded version
0.7.11-1ubuntu1. Also committed the same change in the salsa git
repository, this an orphaned package, not expecting an upload of a new
version soon.

The change explained above was uploaded but then it FTBFS on s390x. Created
a patch to support that and uploaded version 0.7.11-1ubuntu2. The patch was
forwarded upstream, and it was already merged:

https://github.com/gittup/tup/pull/470

Package unblocked.

# loggerhead

The autopkgtest regression was reported in Debian and it was theoretically
closed in version 2.0.0-1. However, the regression is still there. I
reopened the Debian bug (#1016452) and gave a hint about what might be the
issue.

# r-cran-uwot

A couple of tests are failing only on arm64, ppc64el and s390x. I tried to
fix them by myself but no luck with that yet. I filed an upstream bug:

https://github.com/jlmelville/uwot/issues/100

# autopkgtest

Re-triggered some tests of other packages blocking it. Package unblocked.

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

Re: +1 maintenance report

[Lucas Kanashiro]

Hi,

On 18/07/2022 12:02, Nick Rosbrook wrote:

### ruby-certificate-authority FTBFS (https://pad.lv/1981458)

There was a print format change for the x509 v3 authority key
identifer field in openssl 3.0, and this test suite appears to depend
on that format. Changing the expected test string to match the new
format fixes the issue.

William sponsored an upload that resolved this.

Thanks for the patch. I uploaded it to Debian already.

--
Lucas Kanashiro


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

Re: +1 maintenance report

[Lucas Kanashiro]

Hi,

On Mon, Jun 13, 2022 at 7:29 AM Simon Chopin 
wrote:

> ruby-gitlab-fog-azure-rm:
> The test suite fails due to Ruby 3.0 incompatibilities.
> I patched out the Proc.new.call invocations into explicit block.call ones,
> submitted both to upstream and Debian. The upstream MR has been merged
> and a new version has been released, but the Salsa MR is still opened:
>
> https://salsa.debian.org/ruby-team/ruby-gitlab-fog-azure-rm/-/merge_requests/1
>

I merged your patch and sponsored the upload in Debian. I did a small
change where you forgot to add a colon after "Closes" in the changelog.

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

+1 maintenance report

[Lucas Kanashiro]

Hi,

Last week was my +1 maintenance shift, this time I decided to try to unblock
packages stuck in -proposed for too long (bottom of the excuses page). Below
you can find a summary of what I did:

# debos

Revisit this package and submitted a patch to implement the solution vorlon
brought up in the discussion (introducing some delta):

https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1940077

Package uploaded and added a comment to the Debian bug about it.

# ruby-parallel

Gave it a shot with the latest upstream release and I was not able to
reproduce
the autopkgtest failure anymore. Uploaded version 1.22.1-1 to Debian. It was
synced but it is still failing, and needs further investigation.

# ruby-tty-screen

Filed an upstream bug report to fix tests in s390x:

https://github.com/piotrmurach/tty-screen/issues/14

Once this is fixed it will also unblock ruby-tty-reader and ruby-tty-prompt.

# redmine

Fixed FTBFS via ruby-rack.

# ruby-rack

Synced version 2.2.3-4 from Debian. The Ubuntu delta was merged into Debian
and this was impacting the redmine FTBFS.

# python-omegaconf

It builds fine in a local kinetic chroot. In LP it cannot satisfy the
pytest-runner dependency, not sure yet why.

# xdg-utils-cxx

The symbols file needed an update. Sent a patch to Debian here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004109

I did not add a delta, let's see if Debian can sort this out soon.

# ruby-omniauth-ultraauth

Fixed the following bug in Debian:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995411

It finally migrated to the release pocket. ruby-omniauth-openid-connect
should
migrate soon as well.

# libdancer2-plugin-passphrase-perl

Filed a bug to remove it from kinetic:

https://bugs.launchpad.net/ubuntu/+source/libdancer2-plugin-passphrase-perl/+bug/1975868

This is a leaf package blocking libdigest-bcrypt-perl for more than 120
days,
and it is also blocked in Debian unstable for more than 765 days.

# puppet

There is an issue with the latest update of puppet trying to make it work
with
ruby 3 (upstream moved to a new major version which supports ruby 3 but we
can't right now due to its dependencies).

https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939

This is still ongoing. I'll spend more time this week on this to see if I
can
come up with a patch.

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

Re: MOTU application

[Lucas Kanashiro]

Hi,

Per today's Developer Membership Board meeting, Athos is the newest
member of MOTU. Welcome and congratulations on the achievement, keep up
the good work!

Lucas Kanashiro on behalf of the DMB.

Em 14/03/2022 20:27, Athos Ribeiro escreveu:
> Hello,
>
> I hereby apply for MOTU.
>
> My application is available at
>
> https://wiki.ubuntu.com/AthosRibeiro/MOTUDeveloperApplication
>
> I have added an entry for my application to the DMB meeting agenda at
>
> https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
>
> I understand the DMB is understaffed and getting quorum may be hard for
> this matter. Therefore, I left a note beside my agenda entry to block a
> slot for the first meeting after March 30, 2022, once the new DMB
> members get elected.
>
> Best regards,
>
-- 
Lucas Kanashiro


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

+1 maintenance report

[Lucas Kanashiro]

Hi,

Below some comments about my +1 maintenance shift from last week:

# docker.io

Sponsored upload for xypron to enable the riscv64 architecture (LP:
#1963920)

# Unblock ruby2.7 removal

A simple re-run of some tests with the right triggers made some packages
still depending on ruby2.7 migrate, and ruby2.7 was finally removed from
Jammy. Below are some blockers that I found.

## ruby-em-socksify

The DEP-8 test was failing because of a missing runtime dependency on
ruby-webrick which was removed from ruby itself. Version 0.3.1-3 was
uploaded to Debian with the fix. ruby-eventmachine migrated from -proposed.

## ruby-net-ssh

It still does not support OpenSSL 3, a bunch of tests are failing because
of that. A bug was filed upstream by the Fedora maintainer and I filed the
following LP bug to track this case (LP: #1964025). I spent most of my time
on it, writing a patch to submit upstream but it is still not ready. I am
coordinating this with schopin and hopefully we will get this fixed soon.

After a migration-reference/0 run it unblocked ruby2.7 removal because this
is already broken in the release pocket. Thanks for that vorlon.

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

+1 maintenance report

[Lucas Kanashiro]

Hi all,

This is the summary of my +1 maintenance shift:

# consul

The package in Debian is FTBFS [1], this was reported by me in Ubuntu as
well [2]. I added a commit to salsa backporting an upstream patch which
fixes the FTBFS, but autopkgtest was still failing. Those tests have been
failing in Debian for many years [3], so I believe this was not a blocker.
However, Reinhard submitted a salsa MR to at least make autopkgtest happy,
so I reviewed and merged it [4]. Version 1.8.7+dfsg1-3 was uploaded to
Debian with the fixes.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997133
[2] https://bugs.launchpad.net/ubuntu/+source/consul/+bug/1940152
[3] https://ci.debian.net/packages/c/consul/unstable/amd64/
[4] https://salsa.debian.org/go-team/packages/consul/-/merge_requests/3

# golang-github-vbauerster-mpb

Re-trigger tests with the correct version of golang-github-containers-image
in all architectures. This also unblocked
golang-github-containers-{images,storage}.

# ruby-jekyll-remote-theme

The package was a FTBFS because it was running some tests trying to access
the Internet, it was building fine in Debian but due to the network policy
we use in our builders it was caught by us. Uploaded version 0.4.3-2 to
Debian skipping those tests.

# ruby-tty-prompt

Re-trigger autopkgtest with the needed dependencies from proposed.
Unblocked ruby-pastel, ruby-tty-command, ruby-tty-prompt, ruby-tty-reader.

# ruby-tty-screen

Re-trigger autopkgtest with the needed dependencies from proposed to
unblock itself.

# ruby-acsiidoctor-pdf

Re-trigger autopkgtest with correct version of ruby-prawn-icon and
ruby-prawn-svg to unblock both of them.

# Ruby packages FTBFSes due to 3.0 transition

There are a bunch of ruby packages FTBFS but most of them are because we
need to start rebuilding packages against ruby3.0, the current version of
ruby-defaults we have in -proposed already force the build against both,
ruby2.7 and ruby3.0. I'll be working on the transition in Ubuntu next week,
things will start to look better. In Debian, it is mostly done from the
release team perspective (97% done at the moment) [1], but there are still
some FTBFS needing some work [2], eventually we will need to get those
packages fixed as well or remove them when it is possible.

[1] https://release.debian.org/transitions/html/ruby3.0-add.html
[2]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org

# Python packages FTBFSes due to 3.10 transition (Athos)

Athos got a fix accepted in Debian and once it got sync'ed he needed to
retry the build of a bunch of packages [1]. I helped him with that. I think
he will reply to this email detailing his work.

[1] https://bugs.launchpad.net/ubuntu/+source/unittest2/+bug/1949778

Have a great weekend!

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

Plus one maintenance report

[Lucas Kanashiro]

Hi,

This week some unplanned things came up and I was not able to be dedicated
full time to my +1 maintenance duty. Moreover, since we reached the final
freeze there were more complex issues to tackle which would require more
time. Below you can find a summary of what I managed to do.

# golang-github-containers-common (migrated)

Re-triggered tests against the correct libpod version in all non-amd64
architectures.

# thin (migrated)

Sergio proposed a fix upstream and it was waiting for their feedback but
got none so far. Approved Sergio's MP and asked him to upload it as a delta
for now.

# ruby-chef-utils (migrated)

This FTBFS is caused by the outdated version of ruby-fauxhai. The JSON
files to represent the several platform families were outdated, and then it
was trying to download the new ones from Github. ruby-fauxhai was updated
in Debian to version 7.5.0 and synced into Ubuntu, which fixes the issue.
As a consequence of now having ruby-chef-utils built, the FTBFes of
ruby-chef-config and ohai were fixed as well.

# libpandoc-wrapper-perl

This package has a block-proposed bug since Groovy because upstream does
not support the pandoc version we have in the archive. I checked if there
is any upstream movement to fix this but they seem dead (last commit was
more than 2 years and a half ago). We may want to remove
libpandoc-wrapper-perl and libpandoc-elements-perl from impish-proposed,
they do not seem to get fixed any time soon.

Have a great weekend!

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

+1 maintenance report

[Lucas Kanashiro]

Hi,

Below you can find a summary of what I did in my shift:

=== Packages migrated ===

- gpgme1.0 (migrated)
  + Retrigger golang-github-containers-buildah and libpod with the latest
version of those packages in proposed.

- golang-github-containers-common (migrated)
  + Retrigger golang-github-containers-buildah and libpod with the latest
version of those packages in proposed.

- r10k (migrated)
  + Apply patch to skip tests trying to change the proxy settings. They are
failing only in the Ubuntu autopkgtest infrastructure because both are
trying to change the same variable.
  + https://bugs.launchpad.net/ubuntu/+source/r10k/+bug/1940104

- golang-golang-x-text (migrated)
  + Retrigger golang-github-nicksnyder-go-i18n.v2 test with the latest
version
to grab the Go 1.16 fix.

- golang-gopkg-alecthomas-kingpin.v2 (migrated)
  + Retrigger golang-github-prometheus-common test with the latest version.

- ruby-rails-assets-diaspora-jsxc (migrated)
  + Submitted a change to the hints git repo to badtest
ruby-rails-assets-diaspora-jsxc in i386. Its javascripts dependencies
are not
available in i386.
  +
https://code.launchpad.net/~lucaskanashiro/britney/+git/hints-ubuntu-1/+merge/407283

- nsscache (migrated)
  + The package was synced from Debian but it still does not support
OpenLDAP
2.5.x. Re-apply the delta we had before to fix the tests.
  + https://bugs.launchpad.net/ubuntu/+source/nsscache/+bug/1938942
  +
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nsscache/+git/nsscache/+merge/407286

- xwayland (migrated)
  + Retrigger mir tests

=== Packages waiting for glib migration ===

- prometheus (waiting for glibc migration)
  + Apply upstream patch to fix a test with Go 1.16. A bug with the upstream
patch was already filed and I see that the intention would be to let the
fix land in Debian and then sync it, but we are already reaching the
feature
freeze and there is some good improvements in this new prometheus
version
that we should release in Impish (I am one of the maintainers in
Debian).
  + https://bugs.launchpad.net/ubuntu/+source/prometheus/+bug/1930752

- redshift (waiting for glibc migration)
  + It is FTBFS at the moment after a NMU in Debian. The systemd service
files
were removed but dh_missing is complaining because the files are still
in
the build directory.
  + https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1940465

- thrift (waiting for glibc migration)
  + The version in proposed FTBFS because it lacks PHP 8 and Go 1.16
support.
Backported an upstream patch to add support for PHP8 and set
GO111MODULE to off.
  + https://bugs.launchpad.net/ubuntu/+source/thrift/+bug/1940473

=== Packages waiting for Debian ===

- rust-alacritty-terminal (waiting on Debian)
  + There is an unsatisfiable build dependency which will be dropped in
Debian
when the latest upstream version is imported. The maintainer said this
will
be done after the Debian release, so I think this should be fixed soon.
  +
https://bugs.launchpad.net/ubuntu/+source/rust-alacritty-terminal/+bug/1940573

- gitlab-ci-multi-runner (waiting on Debian)
  + There are some missing build dependencies but also an incompatibility
with
our docker library.
  + It is also blocked in Debian because of a CVE.
  +
https://bugs.launchpad.net/ubuntu/+source/gitlab-ci-multi-runner/+bug/1940667

=== Misc ===

- consul (still needs some work)
  + Found an upstream patch to fix a TLS related test, allowing x509
certificates comparison with Go 1.16.
  + https://bugs.launchpad.net/ubuntu/+source/consul/+bug/1940152
  + It seems there is a missing dependency (github.com/hashicorp/vault)
  + This will likely unblock nomad (latest version from Debian)

- golang-golang-x-net (still needs some work)
  + Retrigger the tests of the following packages:
* golang-github-prometheus-common
* golang-github-go-resty-resty
* golang-github-mattn-go-sqlite3
* golang-github-smartystreets-assertions
* golang-github-wellington-go-libsass

- golang-github-spf13-cobra (waiting for golang-yaml.v2 migration)
  + Retrigger golang-github-containerd-buildah tests with the version in
proposed.

- request-tracker4(5)
  + It has a fix for the FTBFS staged in salsa but it seems that they will
not
release it in time for Impish release.
  + https://bugs.launchpad.net/ubuntu/+source/request-tracker5/+bug/1932076
  + Since feature freeze already started, I did not upload the package.

That's all for this week. Have a great weekend!

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

+1 maintenance report

[Lucas Kanashiro]

 with fixes in
-propose

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

+1 maintenance report

[Lucas Kanashiro]

Hi,

During this week I've been working on +1 maintenance and you can find a
summary of my work and some considerations below:

# Rails 6 transition

The rails migration is blocked mainly because of yarnpkg, a npm alternative
tool used by rails. yarnpkg is uninstallable at the moment because it
depends on node-babel-runtime >= 7 which is also blocked in proposed. The
node-babel7 source package FTBFS now, and I was not able to sort this out,
some help is appreciated.

No ruby related issue is blocking the Rails 6 transition, all the packages
listed as blockers are ruby packages providing javascript assets.

There are some other package blocked by rails where the tests would be
fixed by patching the test to call "rails new" passing "--skip-javascript
--skip-webpack-install", this is not the best solution but it is a valid
workaround if the package does not relate with javascript assets.

# Rebuild ruby libraries to apply changes included in gem2deb/1.4

We made some changes to gem2deb on how the gemspec is generated when the
library provides native extensions. If you find a ruby library providing a
native extension and it was not built with gem2deb/1.4 then it MUST be
rebuilt. Some packages were missing this change, so I made a no-changes
upload:

- ruby-sqlite3
- ruby-msgpack
- ruby-bindex

After rebuilding them, the other packages which depend on them were able to
also be rebuilt (they were FTBFS previously):

- ruby-invisible-captcha
- ruby-fakeredis
- ruby-voight-kampff
- ruby-rollout
- ruby-bootsnap
- thin

# ruby-faraday{,-middleware} transition

There is a new major release for both packages which requires some changes
to let them migrate. The action item needing attention is the removal of
some packages which do not support those new versions yet. Debian already
did that. The following packages need removal of their source and binary
packages:

- ruby-diaspora-federation
- ruby-puppet-forge
- r10k
- librarian-puppet
- vagrant-librarian-puppet

More details can be found in LP #1913596 and LP #1913598. I subscribed
ubuntu-archive to this bug but I do not know whether they track it. It will
unblock many other ruby libraries.

I also uploaded ruby-faraday to Debian fixing an Ubuntu autopkgtest failure
due to a proxy issue.

# Misc

- Re-triggered ubuntu-fan test which I fixed last week to unblock docker.io
and iproute2
- Re-triggered pcs test in amd64 to unblock pacemaker
- Uploaded golang-github-caarlos0-env/6.4.0-1 to Debian fixing a couple of
tests. The patch was submitted upstream and it was already merged. Also
re-triggered tests in all architectures.
- Uploaded apt-clone to Ubuntu fixing an autopkgtest failure due to a proxy
issue. The patch was submitted upstream, waiting for review.
- Uploaded nanoc to Ubuntu fixing an autopkgtest failure due to a proxy
issue. In Debian, this package is in the middle of an upstream version
bump, when the git repo is better organized I'll commit this change myself.
- Re-triggered ruby-dalli test in armhf to unblock itself.
- Re-triggered syncthing tests to unblock some packages:
  + golang-golang-x-net
  + golang-golang-x-text
  + golang-github-miscreant-miscreant.go
  + golang-github-syncthing-notify
  + golang-github-thejerf-suture
  + golang-github-gobwas-glob

Something that is worth mentioning is that I've seen a considerable number
of test failures due to proxy issues in our autopkgtest infrastructure.
Usually, you just need to tweak the no_proxy variable to make them pass.

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

Re: +1 maintenance report - 26th and 27th November

[Lucas Kanashiro]

Sorry, in the subject it should be 26th and 27th (not 28th and 29th :)

On Fri, Nov 27, 2020 at 5:41 PM Lucas Kanashiro <
lucas.kanash...@canonical.com> wrote:

> Hi,
>
> My +1 maint shift was supposed to be the whole week but there are some
> side projects that did not allow me to do so. I have worked on +1 maint
> yesterday and today. I focused mainly on ruby packages, there is a small
> change where rubygems was extracted from the interpreter source package and
> now it has its own source package (which also ships bundler). Many packages
> FTBFS and tests failed because of uninstallability issues (rubygems and
> bundler), to fix it I needed to:
>
> - ruby-defaults: sync version 1:2.7+2 from Debian unstable. rubygems will
> not migrate without this new version.
> - rubygems: investigated test failures. Fixed in Debian version
> 3.2.0~rc.2-4 (should land in proposed soon).
>
> Fixed FTBFS because rubygems binaries are not installable:
>
> - rails
> - ruby-serverengine
> - ruby-apollo-upload-server
> - ruby-jekyll-polyglot
> - ruby-jquery-ui-rails
> - ruby-asset-sync
> - ruby-dalli
> - ruby-data-migrate
> - ruby-enumerize
> - ruby-execjs
> - ruby-jekyll-default-layout
> - ruby-jekyll-feed
> - ruby-jekyll-include-cache
> - ruby-jekyll-readme-index
> - ruby-jekyll-seo-tag
> - ruby-jekyll-toc
> - ruby-leaflet-rails
> - ruby-specinfra
> - ruby-strptime
> - ruby-webpacker
>
> Test failures because rubygems binaries are not installable:
>
> - ruby-backbone-on-rails
> - ruby-bootstrap-sass
> - ruby-bootstrap-switch-rails
> - ruby-markdown-it-html5-embed
> - ruby-rails-assets-corejs-typeahead
> - ruby-rails-assets-fine-uploader
> - ruby-rails-assets-jquery
> - ruby-rails-assets-jquery-nicescroll
> - ruby-rails-assets-jquery.are-you-sure
> - ruby-rails-assets-markdown-it-diaspora-mention
> - ruby-rails-assets-perfect-scrollbar
>
> Some of those tests might fail because they need some extra triggers. I am
> still waiting for results and I will keep tracking them, and also the new
> ruby-defaults and rubygems tests.
>
> Some work unrelated to the ruby-defaults/rubygems changes:
>
> - ruby-pygements.rb: run tests with the right triggers in arm64 and armhf
> (migrated).
> - ruby-activeldap: run tests with the right triggers in amd64 and armhf
> (migrated)
> - prometheus-sql-exporter: run tests with the right triggers in armhf
> (migrated).
> - ruby-doorkeeper-openid-connect: run tests in all arches with proper
> triggers to unblock ruby-doorkeeper (migrated).
> - ruby-doorkeeper-openid-connect: request another amd64 build to pull in
> ruby-doorkeeper from proposed. FTBFS fixed.
> - rclone: request another build in ppc64el. It seems like a flaky test.
> FTBFS fixed.
>
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

+1 maintenance report - 28th and 29th November

[Lucas Kanashiro]

Hi,

My +1 maint shift was supposed to be the whole week but there are some side
projects that did not allow me to do so. I have worked on +1 maint
yesterday and today. I focused mainly on ruby packages, there is a small
change where rubygems was extracted from the interpreter source package and
now it has its own source package (which also ships bundler). Many packages
FTBFS and tests failed because of uninstallability issues (rubygems and
bundler), to fix it I needed to:

- ruby-defaults: sync version 1:2.7+2 from Debian unstable. rubygems will
not migrate without this new version.
- rubygems: investigated test failures. Fixed in Debian version
3.2.0~rc.2-4 (should land in proposed soon).

Fixed FTBFS because rubygems binaries are not installable:

- rails
- ruby-serverengine
- ruby-apollo-upload-server
- ruby-jekyll-polyglot
- ruby-jquery-ui-rails
- ruby-asset-sync
- ruby-dalli
- ruby-data-migrate
- ruby-enumerize
- ruby-execjs
- ruby-jekyll-default-layout
- ruby-jekyll-feed
- ruby-jekyll-include-cache
- ruby-jekyll-readme-index
- ruby-jekyll-seo-tag
- ruby-jekyll-toc
- ruby-leaflet-rails
- ruby-specinfra
- ruby-strptime
- ruby-webpacker

Test failures because rubygems binaries are not installable:

- ruby-backbone-on-rails
- ruby-bootstrap-sass
- ruby-bootstrap-switch-rails
- ruby-markdown-it-html5-embed
- ruby-rails-assets-corejs-typeahead
- ruby-rails-assets-fine-uploader
- ruby-rails-assets-jquery
- ruby-rails-assets-jquery-nicescroll
- ruby-rails-assets-jquery.are-you-sure
- ruby-rails-assets-markdown-it-diaspora-mention
- ruby-rails-assets-perfect-scrollbar

Some of those tests might fail because they need some extra triggers. I am
still waiting for results and I will keep tracking them, and also the new
ruby-defaults and rubygems tests.

Some work unrelated to the ruby-defaults/rubygems changes:

- ruby-pygements.rb: run tests with the right triggers in arm64 and armhf
(migrated).
- ruby-activeldap: run tests with the right triggers in amd64 and armhf
(migrated)
- prometheus-sql-exporter: run tests with the right triggers in armhf
(migrated).
- ruby-doorkeeper-openid-connect: run tests in all arches with proper
triggers to unblock ruby-doorkeeper (migrated).
- ruby-doorkeeper-openid-connect: request another amd64 build to pull in
ruby-doorkeeper from proposed. FTBFS fixed.
- rclone: request another build in ppc64el. It seems like a flaky test.
FTBFS fixed.
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

+1 maintenance report - 08/09 -> 11/09

[Lucas Kanashiro]

Hi,

Below you can find the notes I took during this week of +1 maintenance duty
(I likely missed small things here and there):

+ django-axes: re-ran tests with the right trigger. Unblock
python-django/2:2.2.16-1

+ r-cran-htmltools: fix test artifacts path in DEP-8 tests.
  -> MP:
https://code.launchpad.net/~lucaskanashiro/+git/r-cran-htmltools/+merge/390496
  -> Debian bug: https://bugs.debian.org/969288
  -> Uploaded

+ r-cran-tibble: fix missing test dependencies in DEP-8 tests.
  -> MP:
https://code.launchpad.net/~lucaskanashiro/+git/r-cran-tibble/+merge/390509
  -> Debian bug: https://bugs.debian.org/970001
  -> Uploaded
  -> Re-run tests with the right triggers, unblock itself, r-cran-rlang and
r-cran-vctrs
  -> Sync from Debian:
https://tracker.debian.org/news/1175296/accepted-r-cran-tibble-303-2-source-into-unstable/

+ r-cran-remotes: fix missing test dependencies in DEP-8 tests.
  -> MP:
https://code.launchpad.net/~lucaskanashiro/+git/r-cran-remotes/+merge/390556
  -> Debian bug: https://bugs.debian.org/970030
  -> Uploaded
  -> Sync from Debian:
https://tracker.debian.org/news/1175302/accepted-r-cran-remotes-220-2-source-into-unstable/

+ r-cran-fs: re-ran test with the correct triggers, it requires the fixed
r-cran-tibble

+ r-cran-ggplot2: re-ran test with the correct triggers, it requires the
fixed r-cran-tibble

+ r-cran-seurat: filed a bug in Debian because it's missing an important
dependency for the main feature in version 3.2.0.
  -> Debian bug: https://bugs.debian.org/970038

+ r-cran-mice: version 3.10.0-1 is missing a DEP-8 test dependency, the new
dependency is in the Debian NEW queue waiting for approval.
  -> LP bug:
https://bugs.launchpad.net/ubuntu/+source/r-cran-mice/+bug/1895203

+ golang-github-mmcloughlin-avo: re-ran test with the correct triggers to
unblock golang-golang-x-tools.

+ golang-github-smartystreets-goconvey: re-ran test with the correct
triggers to unblock golang-golang-x-tools.

+ golang-github-sap-hdb: a test fails to build on 32 bits architectures.
Uploaded a new release to Debian skipping this test on armhf.
  -> Upstream bug: https://github.com/SAP/go-hdb/issues/57
  -> Debian release: 0.100.10-2

+ lua-say: fix minor issue in the DEP-8 test. Unblock dh-lua/27.
  -> Debian bug: https://bugs.debian.org/970089
  -> LP bug: https://bugs.launchpad.net/bugs/1895296

+ nss-wrapper: there is a cmake call in the DEP-8 test failing, changed the
arguments order to fix it.
  -> LP bug: https://bugs.launchpad.net/bugs/1895345
  -> Uploaded

-> Rails 6 migration

  - ruby-has-scope: synced version 0.7.2-3 from Debian. It applies an
upstream bug fix to make it build with Rails 6. Re-run tests with the
correct triggers

  - ruby-carrierwave: re-ran tests with the right trigger

  - ruby-case-transform: re-ran tests with the right trigger

  - ruby-entypo-rails: re-ran tests with the right triggers

  - ruby-joiner: version 0.5.0-2 in Debian fixes tests. It'd need a FFe.

  - ruby-rails-assets-jquery-nicescroll: fixed the DEP-8 test failure with
Rails 6 in Debian in version 3.6.6-3. Re-ran tests with the correct
triggers. There is still an issue with webpack in non-amd64 architectures.

  - ruby-rails-assets-diaspora-jsxc: fixed the DEP-8 test failure with
Rails 6 in Debian in version 0.1.5+dfsg2~develop.7-5. Re-ran tests with the
correct triggers. There is still an issue with webpack in non-amd64
architectures.

  - ruby-rails-assets-markdown-it: fixed the DEP-8 test failure with Rails
6 in Debian in version 8.4.2-3. Re-ran tests with the correct triggers.
There is still an issue with webpack in non-amd64 architectures.

To move to Rails 6 in Groovy we would need to remove some Rails apps we
have in the archive because they still do not support Rails 6 (they were
removed from Debian testing to unblock Rails 6 migration). Since the main
reason to have Rails in the archive is to support those apps their removal
would not benefit users. The Rails debian package is not suitable for Rails
development at the moment. Moreover, the JS management of rails apps is
kind of broken in non-amd64. In short, I'd prefer to finish this transition
next cycle and give more time to upstream projects to support Rails 6, and
the Debian maintainer to fix the existing issues.
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

+1 maintenance report - 29/06 -> 03/07

[Lucas Kanashiro]

Hi,

This is my first week on +1 maintenance duty, I decided to prioritize Ruby
packages (addressed most of the issues) and also worked on some Go
packages. Below you can find all the notes I took during the week (I also
re-triggered some tests not mentioned here and I might have missed
something on the way):

- golang-golang-x-tools: Marked LP #1884314 as Fix Released. The
autopkgtest failure was fixed in Debian version
1:0.0~git20200410.79a7a31+ds-2 and it is already in the Groovy release
pocket.

- puppetdb: Filed an RM bug against it (LP: #1885568). It was removed from
Debian testing because it is stuck in unstable for one year. It never
landed in the release pocket, so nothing to worry about reverse
dependencies.

- puppet-beaker: Filed LP #1885614 and proposed a patch to Debian and
upstream to relax version constraints on ruby-net-s{sh,cp}. Uploaded a new
version fixing the issue.

- ruby-guard: ran autopkgtest triggered by ruby-guard/2.16.2-1 and
pry/0.13.1-1

- pry: ran autopkgtest triggered by pry/0.13.1-1 and
ruby-method-source/1.0.0-2

- ruby-hoe: Reopened the Debian bug #952041 reporting a FTBFS. After some
analysis with another DD we decided to skip the failing test. Turned out it
is not a bug in the upstream code (it affects downstream only), and the
failure does not represent a real bug. Version 3.22.1+dfsg1-2 was uploaded
to Debian skipping this test.

- ruby-webmock: Filed LP #1885760 and proposed a patch to fix autopkgtest
in Ubuntu, it basically appends 0.0.0.0 to no_proxy env variable because
this address is used during the tests.

- devscripts: Filed a component-mismatch bug (LP #1885766) reported by
Christian and submitted a patch to fix it, downgrading pristiner-tar (not
in main) to Suggests.

- cadvisor: Uploaded debdiff attached on LP #1884663 after mwhudson ack the
workaround I proposed. The containerd library package is not working at the
moment due to the vendored code. We are working on it.

- ruby-mustermann-grape: ran autopkgtest triggered by
ruby-mustermann/1.1.1-1 and ruby-mustermann-grape/1.0.1-1

- rubocop: ran autopkgtest triggered by ruby-parallel/1.19.1-1 and
rubocop/0.80.1+dfsg-4

- puppet-beaker: ran autopkgtest triggered by ruby-net-scp/3.0.0-1 and
puppet-beaker/4.21.0-2ubuntu1

- ruby-http: A test marked as flaky by upstream was failing in Ubuntu but
not in Debian autopkgtest infrastructure. I uploaded version 4.4.1-4 to
Debian skipping this test and also reported it to upstream.

- ruby-google-api-client: ran autopkgtest triggered by
ruby-googleauth/0.13.0-2, ruby-signet/0.14.0-2 and
ruby-google-api-client/0.33.0-2

- ruby-googleauth: ran autopkgtest triggered by ruby-signet/0.14.0-3 and
ruby-googleauth/0.13.0-2

- ruby-signet: Uploaded version 0.14.0-3 to Debian skipping the failing
test which checks for a $LOAD_PATH change which should not happen in the
autopkgtest environment anyway.

- ruby-diaspora-federation: Uploaded version 0.2.6-2 to Debian relaxing the
ruby-farday version constraint in gemspec. The package started to FTBFS
after new ruby-faraday landed in Debian.

- bundler: ran autopkgtest triggered by ruby-net-http-persistent/3.1.0-2

- ruby-diaspora-federation: ran autopkgtest triggered by
ruby-faraday/0.17.3-1

- golang-procfs: Sponsored the upload of version 0.1.3-3 to Debian which
fixes the autopkgtest failure in armhf.

- ruby-valid-email: It FTBFS in Groovy because some tests rely on a DNS
setup to perform some lookups. I filed a bug upstream to make tests more
self contained and uploaded version 0.1.3-3 to Debian skipping those tests
for now.

- ruby-arbre: It FTBFS because of some bundler usage in the test helper. I
uploaded version 1.2.1-4 to Debian patching this out and closing bug
#963379.

- ruby-ahoy-email: ran autopkgtest triggered by rails/2:5.2.4.3+dfsg-2 and
ruby-ahoy-email/1.1.0-1

- golang-github-miekg-dns: mwhudson's patch to fix tests in 32 bits
platforms was accepted upstream and I uploaded version 1.1.26-2 to Debian
applying this patch.

- puppet: Merged version 5.5.19-1 from Debian. It should fix the
ruby-puppet-syntax FTBFS. The version 5.5.19-1ubuntu1 was uploaded after
sorting out some mistakes made in 5.5.19-1.

- ruby-arbre: ran autopkgtest triggered by rails/2:5.2.4.3+dfsg-2 and
ruby-arbre/1.2.1-4

- ruby-hdfeos5: ran autopkgtest triggered by hdf-eos5/5.1.16.dfsg.1-3

- ruby-protocol-http1: Upstream has a couple of tests which checks for
memory allocation space and they are failing in 32 bits platforms. I filed
a bug upstream and uploaded version 0.13.0-3 to Debian temporarily
disabling those tests.

Request for help:
During this week I've faced some autopkgtest failures with ruby-http and
ruby-kubeclient in s390x architecture which at a first glance seems an
outdated testbed (unsatisfiable dependencies) but after some retries I was
not able to fix them, I'd appreciate if someone could help me to find the
cause of the failures. FWIW they work fine in the other architectures.

Have a great weekend!
Cheers!
-- 
ubuntu-devel 

Re: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu

[Lucas Kanashiro]

Hi Rafael,

I reported this issue yesterday here:

https://bugs.launchpad.net/chef/+bug/1877462

Steve reviewed it and marked it as Invalid.

On 08/05/2020 10:14, Rafael David Tinoco wrote:
> Forwarding to Ubuntu Devel Mailing list for broader audience.
>
> Should I just open a [RM] bug for all Ubuntu versions ? Any thoughts ?

BTW just Focal would be affected.

Cheers!



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

Ruby 2.7 in Focal

[Lucas Kanashiro]

The Ruby 2.7 transition is now complete and it is another new feature for
users of the upcoming Ubuntu Focal Fossa release.

Ruby 2.7 is probably the last Ruby 2.x series release (the next one should
be 3.0) and it comes with some nice features and improvements like: Pattern
Matching, REPL improvement, Compaction GC, Separation of positional and
keyword arguments and much more. To have a broad overview about the cool
features and improvements check the Ruby 2.7 Release Announcement [1].
Below you can find some changes introduced by this new release.

Experimental features:

* Pattern matching
* Beginless range (i.e. array = [0,1,2,3,4,5]; p array[..2] #=> [0, 1, 2])

Features that emit warnings now and will become errors in the future:

* Using the last argument as keyword parameters
* Numbered parameters: '_1', '_2', and so on are reserved for numbered
parameter
* Proc.new and Kernel#proc with no block in a method called with a block
* Set special variables '$;' and '$,' to non-nil values
* 'yield' in singleton class syntax
* Access and setting of $SAFE, it will become a normal global variable in
Ruby 3.0

Deprecated features, which will raise exceptions now:

* Kernel#lambda with no block in a method called with a block raises an
exception
* Line break is prohibited as an identifier of the quote here document
* Dir.glob and Dir.[] no longer allow NUL-separated glob pattern. Use Array
instead.

Moreover, some libraries are not bundled anymore in Ruby 2.7. If you need
them please install them separately:

* CMath
* Scanf
* Shell
* Synchronizer (ruby-sync)
* ThreadsWait (ruby-thwait)
* E2MM (ruby-e2mmap)

For more information about Ruby 2.7 check the upstream documentation [2]
(section Reference Documentation).

[1] https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/

[2] https://www.ruby-lang.org/en/documentation/


Enjoy it!
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Ruby 2.7 transition

[Lucas Kanashiro]

Hi everyone,

The server team is about to start a transition to Ruby 2.7, targeting the Focal
release.

The current version in the archive is 2.5 and many changes that our users
might take advantage of were introduced in Ruby 2.6 [1] and 2.7 [2]. Since
2.7 is a LTS release it is in our great interest to ship this latest version,
as it will be maintained upstream until 2023 (probably until March);
maintenance on 2.5 ends at the beginning of next year.

I've been rebuilding the reverse dependencies reported by ben in a PPA [3]
and we are good to go, 166 source packages building fine against Ruby 2.7
(no FTBFS). We also have the tracker page for this transition [4] (thanks
to doko). We are going ahead of Debian here to get it done in time for the
feature freeze, but I've been pushing it forward in Debian as well and I'll
make sure we have most of the things in sync.

If you have any concerns about this transition let us know. We plan to kick
this off this week.

Lucas Kanashiro.

[1] https://www.ruby-lang.org/en/news/2018/12/25/ruby-2-6-0-released/
[2] https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/
[3]
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-ruby2.7-transition
[4]
https://people.canonical.com/~ubuntu-archive/transitions/html/html/ruby2.7-add.html
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel