[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Many ruby library transitions for gitlab reupload to experimental





On Wed, Jun 14 2023 at 09:22:24 PM +05:30:00 +05:30:00, Praveen Arimbrathodiyil <praveen@onenetbeyond.org> wrote:
On 13/06/23 1:16 pm, Pirate Praveen wrote:
I'm using this pad to track the reuploads
https://storm.debian.net/shared/KsibMVg-48Iaa_ooNGxsMxaFisv74u1tDeH_jX00GWJ

about 32 packages have been re-uploaded so far, ruby-googleauth being a
major update among this.

- ruby-countries - it built fine locally, but failed on the buildd so
help is welcome to check one failing test
- ruby-rouge - redmine still needs fixing 1037465 (thanks to boutil and
terceiro for fixing asciidoctor/ruby-kramdown-parser-gfm and nanoc).

I proposed on the redmine bug to upload ruby-rouge on July 1st in case redmine is not fixed by then.

- ruby-cfpropertylist - fix ruby-fission ftbfs

fixed thanks to boutil.
- ruby-net-http-persistent - this has to go along with ruby-faraday,
which seems like a bigger transition

ruby-faraday: will need fixing 15 packages, some of them already fixed upstream, though needs packaging some new gems which were split from faraday. Help is very much welcome here.

these are fixed upstream: ruby-acme-client 1025098 (new gem: ruby-faraday-retry - praveen, in new), ruby-asana 1025097 (new gems: faraday-multipart and faraday-follow_redirects),

not investigated upstream status yet: rabbit 1037963, ruby-azure-storage-common 1025095, ruby-behance 1025094, ruby-faraday-middleware 1025092, ruby-gh 1025090, ruby-google-cloud-env 1025087, ruby-google-cloud-translate 1025085, ruby-graphlient 1025084, ruby-ms-rest 1037992, ruby-ms-rest-azure 1037994, ruby-octokit - indirectly via ruby-sawyer 1025077, ruby-puppet-forge 1025078, ruby-typhoeus 1025075


6 ruby-google-apis-* is probably a simple rebuild as ruby-googleauth
1.3
and ruby-google-apis-core are available in unstable.

All of these requploaded to unstable (now only ruby-recaptcha and ruby-ruby-parser is left)



Reply to: