koobs added the comment:
YES, finally. Thanks :)
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28027>
___
___
Pyth
koobs added the comment:
Re-open and assign for regressions. Observed in all koobs-freebsd* buildbots
(9/10/11) and build types. Issue is in default branch (add version 3.7)
First failing test run:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Non-Debug%203.x/builds/110
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27904>
___
__
koobs added the comment:
This appears to have spontaneously resolved itself after build #957 after many
failures. For reference, other builders on the same host were failing as well:
AMD64 FreeBSD CURRENT Debug 3.5 (#567, #568)
AMD64 FreeBSD CURRENT Non-Debug 3.5 (#8, #9)
And possibly others
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
versions: +Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26040>
___
__
koobs added the comment:
For posterity, the following failure was observed on all (9/10/11(current)
FreeBSD buildbots:
==
FAIL: testFraction (test.test_statistics.Test_Nth_Root
koobs added the comment:
@Brett / Ned I'm happy to carry the proposed patch in the FreeBSD
ports/packages until the next releases if that helps your confidence levels.
--
versions: +Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.
koobs added the comment:
Not sure why the stage field changed on last submission. Restore accordingly to
previous state
--
stage: patch review -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
koobs added the comment:
@Stefan I'll touch base with Antoine (OP) and confirm that this is a
root-cause, permanent solution
--
stage: commit review -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
koobs added the comment:
@Stefan I've notified our FreeBSD Clang/LLVM people of the upstream bug status,
though there are indications that the "-Wl,-rpath" method is considered the
recommended/canonical/future way to do thing
koobs added the comment:
Nothing is required (as far as I'm aware) other than commit/merge on a two line
change scoped only to FreeBSD.
The issue was reported for and on FreeBSD and the patch has been carried
locally in all FreeBSD Python ports/packages (2.7, 3.3, 3.4, 3.5) for over two
koobs added the comment:
Thank you Alexander, consider me satisfied :)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24773>
___
__
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue23968>
___
__
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26852>
___
__
koobs added the comment:
Forgive me for asking a question that may have already been asked, or beaten to
death, but what is preventing Python from requiring libffi as an
external/required dependency, rather than keeping it and taking on the burden
of fixes/backporting in lieu of updates
Changes by koobs <koobs.free...@gmail.com>:
--
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19613>
___
_
koobs added the comment:
This just failed on 3.x (default) on koobs-freebsd{9,10} bots:
==
FAIL: test_article_head_body (test.test_nntplib.NetworkedNNTP_SSLTests
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26662>
___
__
koobs added the comment:
@David
The symptoms from FreeBSD look a little different:
Only gethostbyname affected only on 2.7 and 3.3 on all freebsd versions (9, 10,
11).
Python 3.2 was not tested (freebsd port was deleted), but likely affected as
well
Feels/Appears like a gethostbyname fix
koobs added the comment:
koobs-freebsd-* 3.x builds are now passing, but I'd like to make an additional
(trivial) proposal, and that is:
If the tests that were previously failling, aren't *specifically* testing for
'backward compatible' timezone definitions, that the tests that currently use
koobs added the comment:
See Also:
non standard (standard?) timezones.
https://lists.freebsd.org/pipermail/freebsd-hackers/2015-May/047765.html
I don't know to what extent these links are considered standard, but I'll talk
to Julian about whether we can get these links installed in FreeBSD
koobs added the comment:
I can help providing information on the koobs-* freebsd buildbots (I run them).
In a default installation, the timezone entries are available in
/usr/share/zoneinfo (see attachment for contents)
Iran is not in the root directory, 'Tehran' is in Asia/ subdirectory
koobs added the comment:
Also failing on all freebsd buildbots, all tests failing with:
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/zoneinfo/Iran'
--
nosy: +koobs
resolution: fixed ->
___
Python tracker &
koobs added the comment:
Thank you Benjamin :)
--
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24557>
___
__
koobs added the comment:
==
ERROR: test_path_with_null_unicode (test.test_posix.PosixTester)
--
Traceback (most recent call last):
File
"/usr/home/bui
koobs added the comment:
koobs-freebsd{9,10,current) failing after
30099abdb3a46d0e306a4cf995b95fa8cfb8b78a merge to 2.7
--
nosy: +koobs
resolution: fixed ->
status: closed -> open
___
Python tracker <rep...@bugs.python.org>
<http://
Changes by koobs <koobs.free...@gmail.com>:
--
versions: +Python 3.3
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22928>
___
_
koobs added the comment:
3.3 is supported for security related fixes until September 2017 [1], but only
3.4, 3.5 and 2.7 have received the backport, reopen for outstanding merge
[1] https://docs.python.org/devguide/#status-of-python-branches
Update summary to reflect the RedHat CVE
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26566>
___
__
koobs added the comment:
@Victor, it would be nice if this test could instead use/fake/mock what it
needs in the build directory, or is this not possible because it needs an
'actual' user/group context to work?
--
nosy: +koobs
___
Python tracker
Changes by koobs <koobs.free...@gmail.com>:
--
resolution: fixed ->
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22847>
___
__
koobs added the comment:
It appears this change broke all FreeBSD builders (9: gcc, 10/11: clang) for
the 2.7 branch with:
koobs-freebsd-current (clang 3.7.x)
cc -pthread -c -fno-strict-aliasing -OPT:Olimit=0 -g -O2 -g -O0 -Wall
-Wstrict-prototypes -I. -IInclude -I./Include
koobs added the comment:
OH THANK YOU!
If possible, add Months or Quarter (Q1-4) for the EoL's, if those are defined,
would be great.
We @ FreeBSD/Python would like to proactively (as early as possible) set
DEPRECATED dates in our ports to ensure our users have ample time to upgrade
koobs added the comment:
This issue is becoming increasingly important as FreeBSD 11.0-RELEASE time
nears.
What remains to be done/identified/answers here to make progress?
--
versions: +Python 2.7, Python 3.5
___
Python tracker <
koobs added the comment:
Wow. *thank you* Georg and Martin :)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25940>
___
___
Pyth
koobs added the comment:
This needs review, commit, merge.
We've back-ported and committed these patches against all of our FreeBSD Python
ports (27,32,33,34,35)
https://svnweb.freebsd.org/ports?view=revision=405569
--
stage: needs patch -> patch review
versions: +Python 3.2, Pyt
Changes by koobs <koobs.free...@gmail.com>:
--
keywords: +needs review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20397>
___
_
koobs added the comment:
As many branches as we can muster, ideally all, at least 3.4, 3.5 default and
2.7 please. Back porting is a massive pain, and downstream OS's want to retain
integrity of tests to ensure quality of Python in their respective ecosystems
koobs added the comment:
setuptools and therefore pip are also affected by this
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by koobs <koobs.free...@gmail.com>:
--
keywords: +easy
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
koobs added the comment:
Can't / Shouldn't these be mocked?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25940>
___
___
Pyth
Changes by koobs <koobs.free...@gmail.com>:
--
priority: normal -> high
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25950>
___
_
New submission from koobs:
It appears all HTTPS/SSL tests that use the remote host svn.python.org are
failing.
All branch builds (tests) are currently broken on koobs-freebsd-current. I
think it's the only bot that has run builds post 24th December so far.
http://buildbot.python.org/all
koobs added the comment:
I'm here from (duplicate) issue 25950
--
nosy: +koobs
priority: normal -> high
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Changes by koobs <koobs.free...@gmail.com>:
--
keywords: +easy, needs review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
koobs added the comment:
Thank you all. A+++, would collaborate again.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25809>
___
__
koobs added the comment:
Just to note, the koobs-freebsd-current buildbot is still failing on 3.4, which
reminded me to re-open
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
koobs added the comment:
Re-open for 3.4 merge
--
status: closed -> open
versions: +Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Changes by koobs <koobs.free...@gmail.com>:
--
nosy: +koobs
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25809>
___
__
koobs added the comment:
To clarify, the bug remains in all branches including default, but only 3.4+
use the .sh script, leaving 3.3, 3.2, 2.7 using the python implementation.
--
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.
koobs added the comment:
The attached patch courtesy of Jan Beich @ FreeBSD minimally mimics (in the
python version), the --ldflags output of the shell version of
python-config(.sh).
The ideal scenario of course would be to use the shell script across all
versions, as per revision
koobs added the comment:
@Serhiy If anyone can provide me some test code (I dont know how to test it)
I'm happy to test it on 'unpatched' 2.7 and 3.5 ports
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
koobs added the comment:
Thanks for the insight Serhiy. A few questions ..
Is clinic code updated based on *.c declarations at build time? If not when/how
is the best place/method to run this for our ports/package builds?
Does your suggestion to switch unsigned_int to unsigned_long imply
koobs added the comment:
@Serhiy
If by "type of code at the time of commit" you mean upstream python code,
msg250163 contains a link to what bits we replace in fcntlmodule.c and that "I
-> k" has always been the same.
--
New submission from koobs:
In my current attempt to create a FreeBSD port for python35, I've come across a
patch rejection for the fcntlmodule.c for a local port patch we've been
carrying since Python 2.6:
https://svnweb.freebsd.org/ports/head/lang/python27/files/patch-Modules__fcntlmodule.c
koobs added the comment:
@Martin, weird, I'm still not seeing any files/dirs matching 'rc3'.
I have refreshed properly (cache-control 0 + empty cache) and still getting a
similar listing.
Fresh fetch output on the index URL:
Python-3.5.0rc1.tar.xz 11-Aug-2015 01:00
14798596^M
Python
koobs added the comment:
Was a bug, now fixed (adjust title/resolution to compensate)
Thanks Berker!
--
resolution: not a bug -> fixed
title: Missing 3.5.0 RC3 tarballs (FTP) -> Missing 3.5.0 RC3 tarballs (FTP) on
Fastly nodes
___
Python t
New submission from koobs:
3.5.0 rc3 tarballs appear to be missing on:
https://www.python.org/ftp/python/3.5.0/
--
messages: 250159
nosy: koobs
priority: normal
severity: normal
status: open
title: Missing 3.5.0 RC3 tarballs (FTP)
versions: Python 3.5
Changes by koobs koobs.free...@gmail.com:
--
components: +Build, Library (Lib)
keywords: +easy, needs review
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24557
Changes by koobs koobs.free...@gmail.com:
--
keywords: +needs review
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24520
koobs added the comment:
Observed the following test_smtplib failure on koobs-freebsd10, noting that the
timeout parameter is still 3
test test_smtplib failed -- Traceback (most recent call last):
File
/usr/home/buildbot/python/2.7.koobs-freebsd10/build/Lib/test/test_smtplib.py,
line 222
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13501
___
___
Python-bugs-list mailing
koobs added the comment:
Incorrect recursive use of make will be fixed in default, 3.5, 3.4 (?), 2.7 in
issue 22359, reflect the versions correctly here so they're not forgotten.
--
nosy: +koobs
versions: +Python 2.7, Python 3.4, Python 3.6
Changes by koobs koobs.free...@gmail.com:
--
components: +Build
keywords: +needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7352
koobs added the comment:
Initial commit to default is done. Backport to 2.7 3.4 branches remains to do
--
components: -Cross-Build
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22359
koobs added the comment:
Add 3.5 to list of versions merging required for
--
versions: +Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22359
koobs added the comment:
Additionally on koobs-freebsd9, in my home directory (which is on ZFS)
The buildbot home directories are on UFS
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15745
koobs added the comment:
Larry: The same two hosts that the FreeBSD Python buildslaves run on :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15745
koobs added the comment:
I have tested both patches (test_os by trent) and almostequaltime by harrison
on the default branch, and *both* result in test_os passing.
They also resolve the test_utime failure reported in bug 24175 and very likely
16287 (born from this issue)
--
versions
koobs added the comment:
Hmm, that was supposed to be: issue 24175 and very likely issue 16287
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15745
koobs added the comment:
Can a test be made to show a message (similar to a skipIf reason=) mentioning
that a reduced precision is being used for certain tests?
It would be nice not to have to remember this issue as platform support changes
(reads: improves) over time.
Not withstanding, it's
koobs added the comment:
martin: yes, if the incorrect usage of recursive make is in the 2.7 and 3.4
branches and the fix is relevant to the issues I reported. Of course all
subsequent changes (fixing cross-builds) should be applied there too
koobs added the comment:
test_utime is now consistently failing on 3.4, 3.5 and default
--
priority: normal - high
title: Sporadic test_utime() failures on FreeBSD - Consistent test_utime()
failures on FreeBSD
versions: +Python 3.6
___
Python
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22359
___
___
Python-bugs-list mailing
koobs added the comment:
We've (FreeBSD) seen and received several random and intermittent reports of
failures during this stage of the build for all versions of Python, resulting
in errors such as, among others:
Parser/pgen.o: file not recognized: File truncated
*** [Parser/pgen] Error code
Changes by koobs koobs.free...@gmail.com:
--
stage: resolved - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22359
___
___
Python-bugs
koobs added the comment:
My mistake, revision 1ca30423b0c99c9599d5d4654323eeeae4a03804 or
revision 29b95625a07cc5bb22e260c983500ed9efed67bf
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24308
New submission from koobs:
test_with_pip fails since revision 0d0989359bbbff9aa502158e362eb298e1a8ba7c
with the following output:
==
FAIL: test_with_pip (test.test_venv.EnsurePipTest
koobs added the comment:
See also:
Issue 16287 (Solaris)
Issue 15745 (Related to FreeBSD/ZFS, has patch)
3.4 and 3.x are still failing
--
title: Test failure in test_utime on FreeBSD - Sporadic test_utime() failures
on FreeBSD
___
Python tracker
New submission from koobs:
The following test failure is observable in koobs-freebsd9 and koobs-freebsd10
buildbots, on the 3.4 and 3.x branches.
==
FAIL: test_utime (test.test_os.StatAttributeTests
koobs added the comment:
After running the latest builds, it appears 3.x is now green, leaving 3.4
failing
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24175
Changes by koobs koobs.free...@gmail.com:
--
components: +Tests
keywords: +needs review
stage: needs patch - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15745
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16287
___
___
Python-bugs-list mailing
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23485
___
___
Python-bugs-list mailing
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22117
___
___
Python-bugs-list mailing
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23863
___
___
Python-bugs-list mailing
koobs added the comment:
@RAW, can you attach a patch against the default branch please so we can move
this forward?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17120
koobs added the comment:
@haypo, if you could take care of the change in default, 3.4 and 2.7, we can
backport the rest downstream. Thank you :)
@bapt, can you create a separate issue to cover the create foo.so.X' symlink
request, so python@ (freebsd team) can work to patch locally
koobs added the comment:
@haypo, yes, absolutely and no
We will backport to security-only branches ourselves.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23817
koobs added the comment:
@doko, as per the original report by Joel, the issue is:
* Reproducible with --enable-shared (most downstream OS's / packages use this)
Additionally:
* in the python script, not the shell script (by default used by 3.4)
* Is reproducible in all branches (including
koobs added the comment:
+1
--
stage: - needs patch
type: - enhancement
versions: +Python 2.7, Python 3.4, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23817
koobs added the comment:
See also:
Issue: https://github.com/atgreen/libffi/issues/180
Title: OSX/i386 build is broken in v3.2.1
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23042
koobs added the comment:
@marc I took a look at the code upstream and it does indeed appear to be the
same. It was introduced in 3.1 [1].
I cant explain however how or why our Python ports work with libffi 3.2.1.
See msg238767 for a link to another similar (same?) issue, with failure of OSX
koobs added the comment:
@Marc, if upstream 3.2.1 also has the issue, then that would mean the current
FreeBSD Python ports, which use --use-system-ffi and the security/libffi port,
currently at version 3.2.1 [1], can reproduce the issue.
I'm not aware of reports that they fail
koobs added the comment:
FWIW, see #23042
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22521
___
___
Python-bugs-list mailing list
Unsubscribe
koobs added the comment:
+nosy doko on ned_deily's advice
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7352
___
___
Python-bugs
koobs added the comment:
Still an issue on 2.7, 3.2, 3.3. Updating Versions to reflect this fact and
assist downstreams in backporting a forthcoming fix to those versions that
won't get it due to security-fix only branches.
See Also:
Issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7352
___
___
Python-bugs-list mailing list
koobs added the comment:
For what it's worth, we've been running with patch 0001 on FreeBSD's Python 3.4
port for 8 months with no issues [1].
It allows downstreams like us to easily customise what modules gets built, and
offers substantial flexibility and benefits for various packaging
1 - 100 of 248 matches
Mail list logo
