Re: Poudriere
Well I zfs destory'd my jails and redone everything, Works now On Tuesday, September 11, 2018, 11:32:14 AM CDT, Nathan Owens wrote: It happens only on non x86 no matter version of freebsd. Py-pytest at py36 does it for me. Koobs tested it in his arm64 at py36. It’s not the port itself. As the file that touches during build isn’t related to the port The freebsd11 changes to freebsd12 according to jail version usr/local/lib/python3.6/__pycache__/_sysconfigdata_m_freebsd11_.cpython-36.pyc: size (17379, 17331) Sent from Yahoo Mail for iPhone On Tuesday, September 11, 2018, 6:44 AM, Lorenzo Salvadore via freebsd-ports wrote: > Submitting this here as I believe this may be best place to ask the question > as I use poudriere to test ports before sending patches > I am on 12 current. If I’m building a port that can use either py27 or py36 > on an non x86based system the py27 works fine on all my jails. If I test with > py36 poudriere errors out saying a file touched my FS during build and it > actually does install a file on my FS as I can delete the file it refers to > and retry build and it will be there again. The FS violation happens on my > mips/mips64/armv6/arm64/ poudriere jails with py36. To try something I forced > it to use py37 and it does the same. > I’ve created a new arch jail with new name and it happens on fresh jail > install as well. I’ve disabled ccache and that didn’t fix the issue either This looks like a problem in some py36 port's Makefile. Can you tell us which file is installed? This might help find the right package. Moreover, does it happen only on 12 current? Can you try on 11.2-RELEASE for example? What about changing architecture? Is py36 fine on a x86 based system? I could do some testing too: can you give an explicit example of broken port? Lorenzo Salvadore. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
On 12/09/2018 13:33, Robert Huff wrote: How many ports_require_ python 3? How many ports_require_ python 2? yeah, I'd like to know too. I mean, I've never installed python as like requiring it to program - it's installed as a dependency of other stuff I want to actually run. And I thought python2 and 3 are actually different languages rather than simply versions. Might be wrong though. tjhanks, -- J. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openssl111 TLSv1.3 port options
On Wed, 12 Sep 2018, Koichiro Iwao wrote: Hi, OpenSSL 1.1.1 has been added to ports tree. AFAIK OpenSSL 1.1.1 supports TLSv1.3 but no port options for TLSv1.3. There're only TLS1, TLS1_1, TLS1_2. I assume TLSv1.3 will be enabled by default unless disabled explicitly so security/openssl111 will always be built with TLSv1.3 enabled, am I correct? And why not add port options to enable/disable TLSv1.3 as well as older TLS versions? Moreover -- is OpenSSL 1.1.1 going to be the default in FreeBSD 12? Probably not as it's already in the RE phase. If that's the case, people who want tls13 are going to be building ports/packages against the non-base version until at least FreeBSD 13. At least tls13 and freebsd13 would coincide nicely, linguistally speaking. -Dan -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC FB: fb.com/DanielMahoneyIV LI: linkedin.com/in/gushi Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/openssl111 TLSv1.3 port options
Hi, OpenSSL 1.1.1 has been added to ports tree. AFAIK OpenSSL 1.1.1 supports TLSv1.3 but no port options for TLSv1.3. There're only TLS1, TLS1_1, TLS1_2. I assume TLSv1.3 will be enabled by default unless disabled explicitly so security/openssl111 will always be built with TLSv1.3 enabled, am I correct? And why not add port options to enable/disable TLSv1.3 as well as older TLS versions? -- meta ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[CFT] Mesa 18.2.0 update (mesa-libs, mesa-dri, libosmesa, clover)
Mesa provides OpenGL/Vulkan drivers for Intel/AMD cards and also VAAPI/VDPAU
drivers for AMD cards. Recently, a new minor version was released. So far it
was only tested Skylake with drm-stable-kmod on 12.0-CURRENT. Can someone test
on FreeBSD < 11.2 for regressions? If you find any don't forget to attach
/var/log/Xorg.0.log and LIBGL_DEBUG=verbose output in advance.
I'd like to land the update sometime after 2018-09-21.
# Apply
$ fetch -qo /tmp/mesa-18.2.0.diff
'https://reviews.freebsd.org/D16571?download=true'
$ patch -Efsp0 -i /tmp/mesa-18.2.0.diff -d /usr/ports
$ make all deinstall install clean -C /usr/ports/graphics/mesa-libs
$ make all deinstall install clean -C /usr/ports/graphics/mesa-dri
# Undo
$ patch -REfsp0 -i /tmp/mesa-18.2.0.diff -d /usr/ports
$ make all deinstall install clean -C /usr/ports/graphics/mesa-libs
$ make all deinstall install clean -C /usr/ports/graphics/mesa-dri
# Testing examples
- graphics/mesa-demos: glxgears, eglgears_x11
- multimedia/mpv: --hwdec=auto (VAAPI/VDPAU EGL interop)
- www/firefox: MOZ_ACCELERATED=1 MOZ_WEBRENDER=1 (GPU compositing)
- https://forums.freebsd.org/threads/unreal-engine-4.65300/
- devel/vulkan-tools: vulkaninfo
- games/vkquake or emulators/{ppsspp,rpcs3} with Vulkan renderer
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
tech-lists writes: > > The only question I have there - why we still don't switched to > > python3 by default?) > > yeah!!! :D How many ports _require_ python 3? How many ports _require_ python 2? Curiously, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere
> > Removed that file from those ports and didn't seem to help
>
> Can you tell if installing port lang/python36 alone instead of as a
> dependency works? I think it does not.
> The problem might be at the end of lang/python36/Makefile (from
> line 140 and down). There is a similiar block at the end of
> lang/python37/Makefile, while lang/python27/Makefile last block
> is a bit different.
Could you also execute the following Makefile and give us the output?
all:
@echo OSVERSION = ${OSVERSION}
@echo OSREL = ${OSREL}
.include
It might be that 12-CURRENT on a non x86 architecture sets wrongly
those variables.
Lorenzo Salvaore.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: RUN_DEPENDS and portmaster
Am 12.09.18 um 07:58 schrieb Matthias Fechner: > Dear Stefan, Dear Mathieu, > > Am 10.09.18 um 14:10 schrieb Stefan Esser: >> This is a design decision in portmaster that has existed for at least >> a decade. >> >> Use INSTALL_DEPENDS if you depend on a port being available and upgraded >> before your port's do-install is invoked. >> >> Changing the current portmaster version in ports is no option, since it >> does not offer to recursively upgrade or install any other port while >> working on some port and it cannot easily be made to support such a >> sequence of actions. > > thanks a lot for your explanation, so it seems to be a problem with > portmaster. > But as I do not want to block all users from using gitlab-ce that are > using portmaster I think it is ok to define all RUN_DEPENDS also as > BUILD_DEPENDS? Yes, adding them to BUILD_DEPENDS will cause all those ports to be built and installed by portmaster before the port that executes those tests. I had thought there also was INSTALL_DEPENDS, but now I see that in fact there only is INSTALLS_DEPENDS, which is used internally in bsd.port.mk. So, BUILD_DEPENDS is the variable to use in that case. Regards, STefan ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere
> Removed that file from those ports and didn't seem to help Can you tell if installing port lang/python36 alone instead of as a dependency works? I think it does not. The problem might be at the end of lang/python36/Makefile (from line 140 and down). There is a similiar block at the end of lang/python37/Makefile, while lang/python27/Makefile last block is a bit different. Lorenzo Salvadore. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
On 12/09/2018 09:50, Ruslan Makhmatkhanov wrote: The only question I have there - why we still don't switched to python3 by default?) yeah!!! :D -- J. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
> Maybe I need to stop using portupgrade. What is the best replacement? I never liked traditional updaters: to me, they seem too complex for a task that should be rather simple. Thus I wrote one myself: Caronte. It has not yet been committed to the port tree, but you can find the port here, waiting for a commit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230769 Keep in mind that the project is new and I have not tested it in many situation yet. In particular, I found that I need to work a bit in the case new options are added to a port after an update (at the moment, in this case, the upgrade is suspended in the configuration step of the updated port until you press CTRL + C), but I will fix that as soon as possible (it was not a priority until I was the only user). I think my updater has a nice behavior with flavors (read manpage), but if it has not, you can post an issue on github and I will deal with it as a priority: https://github.com/lsalvadore/caronte Lorenzo Salvadore. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
tech-lists wrote on 9/12/18 11:09 AM: Hello, On 11/09/2018 15:54, Ruslan Makhmatkhanov wrote: No, it's because pylint2 as itself requires python > 3.4. User should switch to older devel/pylint1 if he needs to stick with 2.7. But I'm not upgrading pylint2: >>> (pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1 You upgrading to pylint mainline version (2.1), that was switched to python 3.x by upstream developers. Since version 2.0 pylint doesn't work with python 2. See: https://github.com/PyCQA/pylint/blob/master/doc/whatsnew/2.0.rst If you need pylint version (1.9.3) that works (and depends upon) python2.7, you need to manually remove your current pylint package and install devel/pylint1 instead. Maybe I need to stop using portupgrade. What is the best replacement? I see no reason to not use stock pkg :). If you absolutely need to make the packages with your customizations, it's better to build them with poudriere and then install/update with pkg. qt4 and qt5 has similar issues to python2 and python3. These are installed as either build or runtime dependencies of other programs I want to run. I just want a version to be picked and stuck with. thanks, It's essential process. qt4 is deprecated and no more supported, so application developers switching to the next supported qt branch, and so the corresponding changes landing in FreeBSD ports tree. The same with python - python applications moving to python3 because python2 is deprecated and will not be supported after year 2020: https://pythonclock.org/ so developers tend to move forward to python3 and there is no issue with FreeBSD package repository - it simply adjusts to upstream requirements. The only question I have there - why we still don't switched to python3 by default?) -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
Hello, On 11/09/2018 15:54, Ruslan Makhmatkhanov wrote: No, it's because pylint2 as itself requires python > 3.4. User should switch to older devel/pylint1 if he needs to stick with 2.7. But I'm not upgrading pylint2: >>> (pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1 Maybe I need to stop using portupgrade. What is the best replacement? qt4 and qt5 has similar issues to python2 and python3. These are installed as either build or runtime dependencies of other programs I want to run. I just want a version to be picked and stuck with. thanks, -- J. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
