Your message dated Tue, 29 Dec 2020 03:20:42 +0900
with message-id <9414a464016e60d09ec015e716bd0...@duckcorp.org>
and subject line Re: python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: 
plugin flit failed with: Not supported proxy scheme None
has caused the Debian Bug report #975832,
regarding python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: plugin flit 
failed with: Not supported proxy scheme None
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 ow...@bugs.debian.org
immediately.)


-- 
975832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aiosqlite
Version: 0.15.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_build
> E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy 
> scheme None
> E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy 
> scheme None
> dh_auto_build: error: pybuild --build -i python{version} -p "3.8 3.9" 
> returned exit code 13
> make[1]: *** [debian/rules:18: override_dh_auto_build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/python-aiosqlite_0.15.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Quack,

This is no longer failing.

Recently #975825 caused problems too but this is fixed.

I re-ran the build on Salsa to check and all is fine:
  https://salsa.debian.org/debian/aiosqlite/-/pipelines/204076

Regards.
\_o<

--
Marc Dequènes

--- End Message ---

Reply via email to