Your message dated Sun, 1 Jun 2025 16:10:02 +0000 with message-id <aDx7WrDZBnZ0YZwQ@debian.org> and subject line Re: Bug#1106200: unblock: ruby-aws-sdk/1.67.0-3 has caused the Debian Bug report #1106200, regarding unblock: ruby-aws-sdk/1.67.0-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1106200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106200 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: unblock: ruby-aws-sdk/1.67.0-3
- From: Lucas Kanashiro <kanashiro@debian.org>
- Date: Tue, 20 May 2025 22:45:47 -0300
- Message-id: <08a25f2ce97ef66c2a297d748bf00bb063c03ed0.camel@debian.org>
Package: release.debian.org Control: affects -1 + src:ruby-aws-sdk X-Debbugs-Cc: ruby-aws-sdk@packages.debian.org User: release.debian.org@packages.debian.org Usertags: unblock Severity: normal Please unblock package ruby-aws-sdk This package version fixed a reproducible builds issue. [ Reason ] There was a reproducible builds issue because this package was not rebuilt for more than 5 years. The tooling changed and a simple rebuild was needed to fix it. [ Impact ] The package shipped in Trixie will reproducibly build without issue. [ Tests ] Unfortunately, this package runs no test during build time, and therefore, nothing during autopkgtest time. However, the changes applied were cosmetic (bump debhelper version, Stadards-Version, and add a new runtime dependency for ${ruby:Depends}). There is no code change. I manually installed the package and made use of the main functions and it is working well. [ Risks ] The risk is that something changed in the new debhelper that made it behave differently. I, personally, did not spotted any issue, but that's the only risk that I foresee. There is no code change, so nothing related to the upstream code is expected. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock ruby-aws-sdk/1.67.0-3diff -Nru ruby-aws-sdk-1.67.0/debian/changelog ruby-aws-sdk-1.67.0/debian/changelog --- ruby-aws-sdk-1.67.0/debian/changelog 2018-03-18 22:45:48.000000000 -0300 +++ ruby-aws-sdk-1.67.0/debian/changelog 2025-05-07 15:03:18.000000000 -0300 @@ -1,3 +1,12 @@ +ruby-aws-sdk (1.67.0-3) unstable; urgency=medium + + * Team upload. + * Bump debhelper compat level to 13 + * Declare compliance with Debian Policy 4.7.1 + * d/control: runtime depend on ${ruby:Depends} + + -- Lucas Kanashiro <kanashiro@debian.org> Wed, 07 May 2025 15:03:18 -0300 + ruby-aws-sdk (1.67.0-2) unstable; urgency=medium * Team upload. diff -Nru ruby-aws-sdk-1.67.0/debian/compat ruby-aws-sdk-1.67.0/debian/compat --- ruby-aws-sdk-1.67.0/debian/compat 2018-03-18 22:45:48.000000000 -0300 +++ ruby-aws-sdk-1.67.0/debian/compat 1969-12-31 21:00:00.000000000 -0300 @@ -1 +0,0 @@ -11 diff -Nru ruby-aws-sdk-1.67.0/debian/control ruby-aws-sdk-1.67.0/debian/control --- ruby-aws-sdk-1.67.0/debian/control 2018-03-18 22:45:48.000000000 -0300 +++ ruby-aws-sdk-1.67.0/debian/control 2025-05-07 15:03:18.000000000 -0300 @@ -3,9 +3,9 @@ Priority: optional Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org> Uploaders: David Suárez <david.sephirot@gmail.com> -Build-Depends: debhelper (>= 11~), +Build-Depends: debhelper-compat (= 13), gem2deb -Standards-Version: 4.1.3 +Standards-Version: 4.7.1 Vcs-Git: https://salsa.debian.org/ruby-team/ruby-aws-sdk.git Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-aws-sdk.git Homepage: https://aws.amazon.com/sdkforruby @@ -19,6 +19,7 @@ ruby-json (>= 1.4), ruby-nokogiri (>= 1), ruby-uuidtools (>= 2.1), + ${ruby:Depends}, ${misc:Depends}, ${shlibs:Depends} Suggests: pryAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Paul Gevers <elbrus@debian.org>
- Cc: Lucas Kanashiro <kanashiro@debian.org>, 1106200-done@bugs.debian.org
- Subject: Re: Bug#1106200: unblock: ruby-aws-sdk/1.67.0-3
- From: Ivo De Decker <ivodd@debian.org>
- Date: Sun, 1 Jun 2025 16:10:02 +0000
- Message-id: <aDx7WrDZBnZ0YZwQ@debian.org>
- In-reply-to: <64afa4da-49ab-48a4-acf7-9fe54863d92e@debian.org>
- References: <08a25f2ce97ef66c2a297d748bf00bb063c03ed0.camel@debian.org> <893501c9-626a-4b08-b6c3-b7ca2ccab4d8@debian.org> <08a25f2ce97ef66c2a297d748bf00bb063c03ed0.camel@debian.org> <e52905adc13f925b092750f973cf80baf9e9bf91.camel@debian.org> <64afa4da-49ab-48a4-acf7-9fe54863d92e@debian.org>
Hi, On Thu, May 29, 2025 at 10:05:42AM +0200, Paul Gevers wrote: > On 29-05-2025 01:20, Lucas Kanashiro wrote: > > Right, it is not. I ran diffoscope against the two versions, you can > > see the output attached. From what I can see, there are just the > > changes I already presented via debdiff plus some timestamp changes in > > some files. > > > I was more thinking of a diffoscope diff with and without the bump. Because > of the large list of changes in the files, it's hard to check if e.g. there > are no new/missing files. I expect the timestamp of the files to be due to > changes in rules-requires-root defaults, so a diff like I propose would make > the check much more trivial. I double-checked the changes in the .deb and unblocked ruby-aws-sdk. Thanks, Ivo
--- End Message ---