Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-05-07 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://github.com/taf2/curb/issues/451
Bug #1069258 [src:ruby-curb] ruby-curb: test regression with curl 8.7.1: client 
read function EOF fail, only only 4/5 of needed bytes read
Set Bug forwarded-to-address to 'https://github.com/taf2/curb/issues/451'.

-- 
1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-05-07 Thread Lucas Nussbaum
Control: forwarded -1 https://github.com/taf2/curb/issues/451

Hi,

I forwarded this upstream.

Lucas



Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-04-29 Thread Samuel Henrique
Hello all,

> These messages with "only only (n)/(n+1) of needed bytes read" seem to
> be characteristic. As well as being a FTBFS, this is also an autopkgtest
> regression when upgrading curl, which is one of several factors preventing
> curl from migrating; that, in turn, blocks elfutils, which blocks GLib,
> which will likely be blocking a significant chunk of the 64-bit time_t
> transition.

I believe this is an issue on ruby-curb and not on curl, check the following
thread on curl-library for details and possible solutions:
https://curl.se/mail/lib-2024-03/0054.html

Cheers,

--
Samuel Henrique 



Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-04-25 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 ruby-curb: test regression with curl 8.7.1: client read function 
> EOF fail, only only 4/5 of needed bytes read
Bug #1069258 [src:ruby-curb] ruby-curb: FTBFS: 178 tests, 699 assertions, 0 
failures, 7 errors, 0 pendings, 0 omissions, 0 notifications
Changed Bug title to 'ruby-curb: test regression with curl 8.7.1: client read 
function EOF fail, only only 4/5 of needed bytes read' from 'ruby-curb: FTBFS: 
178 tests, 699 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 
notifications'.

-- 
1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-04-25 Thread Simon McVittie
Control: retitle -1 ruby-curb: test regression with curl 8.7.1: client read 
function EOF fail, only only 4/5 of needed bytes read
User: debian...@lists.debian.org
Usertags: breaks needs-update

On Thu, 18 Apr 2024 at 22:42:11 +0200, Sebastian Ramacher wrote:
> Error: test_easy_http_verbs(TestCurbCurlEasy): Curl::Err::ReadError: Failed 
> to open/read local data from file/application: client read function EOF fail, 
> only only 4/5 of needed bytes read
...
> Error: test_put_data(TestCurbCurlEasy): Curl::Err::ReadError: Failed to 
> open/read local data from file/application: client read function EOF fail, 
> only only 6/7 of needed bytes read
...
> Error: test_put_data_null_bytes(TestCurbCurlEasy): Curl::Err::ReadError: 
> Failed to open/read local data from file/application: client read function 
> EOF fail, only only 2/3 of needed bytes read

These messages with "only only (n)/(n+1) of needed bytes read" seem to
be characteristic. As well as being a FTBFS, this is also an autopkgtest
regression when upgrading curl, which is one of several factors preventing
curl from migrating; that, in turn, blocks elfutils, which blocks GLib,
which will likely be blocking a significant chunk of the 64-bit time_t
transition.

This could either be a regression in curl, or a pre-existing bug in
ruby-curb that was exposed by a behaviour change in curl (for example
maybe curl started applying stricter checks). I don't know curl well
enough to say which, but perhaps the curl maintainers can help? This
upstream commit introduced the new error message and seems relevant:
https://github.com/curl/curl/commit/9369c30cd87c041cf983bcdfabd1570980abbaf6

Here is a convenient reproducer in an unprivileged container:

$ podman run -v $(pwd):$(pwd):rw -w $(pwd) -it debian:trixie-slim
# sed -i -e 's/Types: deb/& deb-src/' /etc/apt/sources.list.d/debian.sources
# apt update
# apt upgrade
# apt install --no-install-recommends build-essential
# apt source ruby-curb
# cd ruby-curb-*
# apt --no-install-recommends build-dep .
# dpkg-buildpackage -us -uc -B
... succeeds ...
# sed -i -e 's/Suites: trixie /Suites: sid /'
# apt --no-install-recommends install curl
...
The following additional packages will be installed:
  libcurl3t64-gnutls libcurl4-gnutls-dev libcurl4t64
Suggested packages:
  libcurl4-doc libgnutls28-dev libidn-dev libkrb5-dev libldap2-dev librtmp-dev 
libssh2-1-dev pkgconf zlib1g-dev
The following packages will be REMOVED:
  libcurl3-gnutls
The following NEW packages will be installed:
  curl libcurl3t64-gnutls libcurl4t64
The following packages will be upgraded:
  libcurl4-gnutls-dev
...
# dpkg-buildpackage -us -uc -B
... fails as seen in the buildd log ...

Thanks,
smcv