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

Re: [RFS] -- ruby-graphql-client 0.18.0
On Mon, Aug 15 2022 at 10:13:25 AM +05:30:00 +05:30:00, Vivek K J <vivekkj@disroot.org> wrote: 

On 10/08/22 17:28, Pirate Praveen wrote:



On Mon, Aug 1 2022 at 05:58:53 PM +05:30:00 +05:30:00, Vivek K J
<vivekkj@disroot.org> wrote:

Hi Team,

        I've updated the package ruby-graphql-client from 0.16.0 to
0.18.0. The package is lintian clean and the updated package is
available at https://salsa.debian.org/ruby-team/ruby-graphql-client. All 
the reverse build dependencies are successfully built.

Requesting for Sponsorship


Gitlab 15.1.x needs only 0.17 (via graphlient 0.5) so I suggest to
update to 0.17 only or make sure the new version does not break
graphlient 0.5. Building fine is not necessarily enough if tests are
not enabled. Did you check if upstream tests are actually run?



The upstream doesn't provide any tests in their repo.
If you have not verified the update, which can include breaking changes as per semver.org, don't break a reverse dependency, it is safer to upload to experimental. 


I wasn't able to build the package and there reverse build deps in a
sbuild environment due to this error:

```

dpkg: error processing archive
/tmp/apt-dpkg-install-dNHVwP/11-gcc-12_12.1.0-8_amd64.deb (--unpack):
unable to make backup link of './usr/lib/gcc/x86_64-linux-gnu/12/lto1' 
before installing new version: No space left on device


This looks like your disk space is full.


dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../12-cpp-12_12.1.0-8_amd64.deb ...
Unpacking cpp-12 (12.1.0-8) over (12.1.0-7) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-dNHVwP/12-cpp-12_12.1.0-8_amd64.deb (--unpack):
 unable to make backup link of './usr/lib/gcc/x86_64-linux-gnu/12/cc1'
before installing new version: No space left on device

```
Anyway I've updated to 0.17.0 and pushed the changes. Please also enable 
pipeline for the salsa repo.
Did you check if it breaks ruby-graphlient? If not it is safer to upload to experimental, as 0.x versions can include breaking changes as per semver.org.
Reply to: