libsoup2.4 2.46.0-2ubuntu1 may have regressed soup_message_set_request

Bug #1322013 reported by Mathieu Trudel-Lapierre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libsoup2.4 (Ubuntu)
New
Undecided
Unassigned

Bug Description

It seems has though something in the gir for libsoup has been broken in the last upload. soup_message_set_request expects the wrong number of parameters, which causes friends' autopkgtests to fail since May 12 (when the new libsoup was uploaded):

https://jenkins.qa.ubuntu.com/job/utopic-adt-friends/ARCH=amd64,label=adt/9/console

ii libsoup2.4-1:amd64 2.46.0-2ubuntu1 amd64 HTTP library implementation in C -- Shared library

I run a minimal test script to exercise the failure; the following snippet fails with a TypeError with 2.46.0-2ubuntu1, but works on 2.44.2-1ubuntu2 (the immediate previous published version, also in Trusty)

"""
from gi.repository import Soup

message = Soup.Message.new('GET', 'http://localhost/')
message.set_request("text/plain", Soup.MemoryUse.COPY, "", 0)
"""

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

The linked branch doesn't fix the bug, but it does add an autopkgtest that catches it (using the small snippet that shows the issue).

Revision history for this message
Dan Winship (danw-gnome) wrote :

soup_message_set_request() had incorrect annotations before; you shouldn't have to explicitly specify the length of the data from python. The annotations are fixed now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.