On Sat, Sep 10, 2016 at 02:46:54PM +0100, Sandro Tosi wrote:
> On Sat, Sep 10, 2016 at 2:19 PM,
> wrote:
> > Your membership in the mailing list Python-modules-team has been
> > disabled due to excessive bounces The last bounce received from you
> > was dated 10-Sep-2016. You will not get any mor
On Sat, Sep 10, 2016 at 04:15:19PM +0100, Sandro Tosi wrote:
> On Sat, Sep 10, 2016 at 3:32 PM, Santiago Vila wrote:
> > AFAIK, Gmail does not bounce spam. It rejects messages with broken
> > DKIM signatures.
>
> no. it rejects (yes technically not bounce, the mails are r
Yes, you are mistaken :-)
https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail#How_it_works
Thanks.
Hello.
I'd like to work on QA issues. Mainly FTBFS bugs, and mainly ensuring that
they are backported to stable if needed (with similar aim I joined debian-med
and go team).
I've read Python Policy and accept it.
Thanks.
Hi. I found 316 affected packages, which I reported here:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian...@lists.debian.org;tag=python-distutils
I'm using a tag so that the bug numbers are easy to get, just in case you people
want to reconsider if adding 316 RC bugs in a day (not re
Hi.
Am I the first person who gets this weird errors?
dh_auto_configure: error: unable to load build system class
'python_distutils': Can't locate
Debian/Debhelper/Buildsystem/python_distutils.pm in @INC (you may need to
install the Debian::Debhelper::Buildsystem::python_distutils module) (@
Thanks a lot for your quick reply.
If you were still relying on python_distutils, you were doing something
horribly wrong.
Not really me. Asking for a friend :-)
El 18/12/24 a las 0:55, Stefano Rivera escribió:
It was obviously assumed that nobody still depended on this.
Ok, I guess we sho
Can you give me a list of packages potentially broken
by this
Would
grep buildsystem=python_distutils
on the (previous) build logs be a good start?
Thanks.
El 27/2/25 a las 12:15, Simon McVittie escribió:
Please add "Build-Depends: dh-sequence-gir" [...]
Thanks a lot.
I confirm that this makes the autopkgtests to work again.
Additionally, there was a wrong declaration which made the
build for i386 to fail, but it was easy to fix.
I've pushed se
El 11/6/25 a las 15:39, PICCA Frederic-Emmanuel escribió:
Now if I build the package within sbuild I get this file list.
[...]
And with a simple dpkg-buildpackage on unstable distribution.
[...]
When using dpkg-buildpackage, try at least using a chroot containing
only build-essential packages
El 11/6/25 a las 17:27, PICCA Frederic-Emmanuel escribió:
setuptools-scm is also use in order to generate the version number.
Our packaging tools are dealing with this ?
The version number is in the very first line of debian/changelog.
El 11/6/25 a las 16:52, PICCA Frederic-Emmanuel escribió:
When using dpkg-buildpackage, try at least using a chroot containing
only build-essential packages and the build-dependencies.
both are using the python -m build method...
so the setuptools build system has different behaviour depending
there is no policy requirement to add build-conflicts.
Or maybe it is but most people believe they are not really useful
if we all use minimal chroots.
El 11/6/25 a las 17:10, PICCA Frederic-Emmanuel escribió:
It seems that this is due to setuptools-scm which provide the list of the data
during the dpkg-buildpackage.
That's it. You can now add setuptools-scm to build-conflicts if it makes you
happy.
It might help some people (for example, yo
14 matches
Mail list logo
