Re: [HEADS UP] Planned deprecation of portsnap
Hi! > > > > * This migration away from portsnap fits well with the planned > > > > migration to git. > > Have a look at the archive, and yes, subversion as version control > > system for the FreeBSD project will probably be replaced by git. > This is very bad news for us. I can make so many arguments against > dropping subversion. It's really not (needn't be) a matter of either/or. Can you elaborate on those arguments ? Maybe if you first review those that were mentioned on the git list in the past ? -- p...@opsec.eu+49 171 3101372Now what ? ___ 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: [HEADS UP] Planned deprecation of portsnap
On Wed, 5 Aug 2020 06:40:39 +0200 Kurt Jaeger p...@freebsd.org said Hi! > > * This migration away from portsnap fits well with the planned > > migration to git. > Please tell me that this doesn't mean a > > [HEADS UP] Planned deprecation of subversion > > is on the horizon. There's a list where the git topic is discussed: https://lists.freebsd.org/pipermail/freebsd-git/ Have a look at the archive, and yes, subversion as version control system for the FreeBSD project will probably be replaced by git. Thank you very much for taking the time to respond, Kurt! :-) This is very bad news for us. I can make so many arguments against dropping subversion. It's really not (needn't be) a matter of either/or. Thanks again, Kurt. Even if it wasn't what I wanted to hear. --Chris ___ 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: [HEADS UP] Planned deprecation of portsnap
Hi! > > * This migration away from portsnap fits well with the planned > > migration to git. > Please tell me that this doesn't mean a > > [HEADS UP] Planned deprecation of subversion > > is on the horizon. There's a list where the git topic is discussed: https://lists.freebsd.org/pipermail/freebsd-git/ Have a look at the archive, and yes, subversion as version control system for the FreeBSD project will probably be replaced by git. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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"
Announcing the version 1.0 hexpeek release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Announcing the version 1.0 hexpeek release! I am pleased to announce the first stable release of hexpeek, which seeks to be an efficient, powerful, and portable hex editor for files of all kinds and sizes. This release improves on the beta release with a live undo, a greatly increased backup depth, better support for writing to non-seekable files, and some miscellaneous cleanup. Visit https://www.hexpeek.com for more information. Out of respect for the bandwidth on this mailing list, I do not plan to announce future hexpeek releases here. There is a mailing list on https://www.hexpeek.com where future announcements will be posted. If you are interested in hexpeek becoming a package/port for your distro, please let me know. -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEfeRsn/lRU2hTiGbecMFr/kefAX8FAl8qMysUHGhleHBlZWtA aGV4cGVlay5jb20ACgkQcMFr/kefAX9U9w//QlTM/zrd25att9/yYcqbQPkDAqhr sjCtSfMoY6sLlsI1IFR1GDu0v0l+TiW4R2iDDn8dD7esLBrhHXe+QLWd9OjioCF7 jB3Tpg+ozk9GMmwDFglbU6hiwTAM4w7O4NKrLEuR/kQoWZzweEXGjIV2ytWhCpps tsl3c/t2rSG0SqlhcHrQpy0uZ38v7f7+o3BCH23gqzdAW+mvvPC9iYLfYJqUGDRt fc5zmouLai9ZAARpqK3Mhu/RTlv8DnxpmsIt2cSJ6OFVbonKBqvDk1RFbLqSUwhU iJv+wMF97f2HT7g1RCNG+GGClD0TvceFP+8qhwIYUhBaRXLe1u+gEEqXvmlURd0h m77ydS58Z1ND1YGw01rTTBzDxnW21HHTFCqGHfRKOjVcLEQrt8CkTvcf7tM5fX+n fodXdEv8k8rrhbOYDyWqurdekWPZCrvrzEPuF+Ww/W6ownW8RwP2cgNccfOiuC2P dTJdIe5j4VASLtC17iUcwDiQuZYWdK5oBlf/ws9flInFHOlGVUGXuD1pum05Iq1u OZeJEHJj+yvP1drm4A1O8z3r8XfPa2WmWsQBc0TP8lOvU3l/E20p1T3TPs8EQbqA dRJyN1PcAv63DE0USa2P+tB18jZkvDV15YT/6yDkOtKEgIdtSsw6H5oscs96LfuI cKK++c04aRN9e28= =02ro -END PGP SIGNATURE- ___ 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: [HEADS UP] Planned deprecation of portsnap
On Tue, 4 Aug 2020 14:43:20 -0400 Steve Wills swi...@freebsd.org said We are planning to deprecate use of portsnap in ports. ... Makes sense to me. Thank you. :-) * Portsnap doesn't seem to save disk space compared to svn or git, if you count the metadata (stored in /var/db/portsnap by default) and you do an apples-to-apples comparison of svn or git without history and ignoring possible ZFS compression. That is, you use "svn export" or git "clone --depth 1", you see this disk usage: 342Msvnexport 426Mgit 477Mportsnap * Portsnap also doesn't work offline which git does. With git, you can also easily add the history by running "git pull --unshallow" * This migration away from portsnap fits well with the planned migration to git. Please tell me that this doesn't mean a [HEADS UP] Planned deprecation of subversion is on the horizon. --Chris ___ 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"
[HEADS UP] Planned deprecation of portsnap
We are planning to deprecate use of portsnap in ports. The reasons are as follows (in no particular order): * Portsnap doesn't support quarterly branches, even years after quarterly branches were created and changed to the default for non-HEAD packages. * Portsnap doesn't seem to save disk space compared to svn or git, if you count the metadata (stored in /var/db/portsnap by default) and you do an apples-to-apples comparison of svn or git without history and ignoring possible ZFS compression. That is, you use "svn export" or git "clone --depth 1", you see this disk usage: 342Msvnexport 426Mgit 477Mportsnap * Portsnap also doesn't work offline which git does. With git, you can also easily add the history by running "git pull --unshallow" * This migration away from portsnap fits well with the planned migration to git. * Also based on the patches we've seen in Bugzilla for some time, usage of portsnap causes folks to too easily accidentally submit patches to Bugzilla which don't apply easily. * Since portsnap doesn't support quarterly branches, it often causes users to build on the wrong branch or end up with mismatched packages. That is, they install packages from quarterly via pkg, then want to customize so run portsnap and build from head, which can cause problems, as we often see. Even when this doesn't happen, it adds to troubleshooting to verify that it didn't. We are aware people have gotten used to portsnap, but believe: * People should be able to easily use svnlite in base or git from pkgs. (Very few people seem to actually use WITHOUT_SVNLITE). * There is also the possibility of falling back to fetching a tar or zip from https://cgit-beta.freebsd.org/ports/ although this does make updating harder. How it will be done, in order: * Update poudriere to use svn by default. This is already done: https://github.com/freebsd/poudriere/pull/764 https://github.com/freebsd/poudriere/commit/bd68f30654e2a8e965fbdc09aad238c8bf5cdc10 * Update docs not to mention portsnap. This is already in progress: https://reviews.freebsd.org/D25800 https://reviews.freebsd.org/D25801 https://reviews.freebsd.org/D25803 https://reviews.freebsd.org/D25805 https://reviews.freebsd.org/D25808 https://svnweb.freebsd.org/changeset/base/363798 Many thanks to the folks who have worked and are working on this! * Make WITHOUT_PORTSNAP default in base. Currently not certain when this will happen. May not happen before 13.0, but hopefully it will. * Eventually, portsnap servers will see low enough usage they can be disabled. We welcome any constructive feedback. All input would be heard, and if the plans need to be amended, we will come back to you with the amended plan in a couple of weeks. This process will take some time and hopefully won't be too disruptive to anyone's usual workflow. Steve (with portmgr@ hat) ___ 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: Chromium (& derivatives) and Python 2.7
On Tue, 04 Aug 2020 16:20:01 +0200, Lars Liedtke wrote: At least in Ubuntu the mongodb 3.6 package does not depend on python2. Package: mongodb-server-core Version: 1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5 Priority: optional Section: universe/database Source: mongodb Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian MongoDB Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 77,8 MB Depends: libboost-filesystem1.71.0, libboost-program-options1.71.0, libc6 (>= 2.29), libgcc-s1 (>= 3.4), libgoogle-perftools4, libpcrecpp0v5 (>= 7.7), libsnappy1v5 (>= 1.1.8), libssl1.1 (>= 1.1.0), libstdc++6 (>= 9), libstemmer0d (>= 0+svn527), libyaml-cpp0.6 (>= 0.6.2), zlib1g (>= 1:1.2.0) Breaks: mongodb-server (<< 1:3.4.14-3ubuntu1) Replaces: mongodb-server (<< 1:3.4.14-3ubuntu1) Homepage: https://www.mongodb.org Download-Size: 21,6 MB APT-Sources: http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages [...] I don't know about build dependencies It's a build dependency. Regards, Ronald. Am 28.07.20 um 11:36 schrieb Ronald Klop: The same problem is going to happen with mongodb36 I presume. It uses python2 to build, but does not need it to run. Would it be possible to remove python2 as a RUN_DEPENDS at the end of 2020, but keep it as a BUILD_DEPENDS in the ports framework? This might save some usefull ports. How are other projects (like Debian, etc.) solving this? Regards, Ronald. Van: Adriaan de Groot Datum: maandag, 27 juli 2020 21:36 Aan: freebsd-ports@freebsd.org Onderwerp: Chromium (& derivatives) and Python 2.7 The Chromium build system -- and as a consequence, also QtWebEngine -- still uses Python 2.7. This is going to be a real problem about six months down the line, and I have no idea how upstream is going to deal with it. I've heard there are patches buried deep within the chocolate factory, but not from reliable sources. QtWebEngine is an even specialer case, since it's an LTS and also the last LTS in the Qt5 series, and I have real doubts about upstream -- The Qt Company -- being able or willing to deal with Python 2.7 deprecation there. Has anyone in FreeBSD tried to port the stuff over? I got about an hour or two into the porting process (making configure accept Python 3 is easy, but there's all these wretched code-generating scripts) and hit a brick wall of templating engines doing sensible Python 2.7 things. [ade] ___ 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: Chromium (& derivatives) and Python 2.7
At least in Ubuntu the mongodb 3.6 package does not depend on python2. > Package: mongodb-server-core > Version: 1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5 > Priority: optional > Section: universe/database > Source: mongodb > Origin: Ubuntu > Maintainer: Ubuntu Developers > Original-Maintainer: Debian MongoDB Maintainers > Bugs: https://bugs.launchpad.net/ubuntu/+filebug > Installed-Size: 77,8 MB > Depends: libboost-filesystem1.71.0, libboost-program-options1.71.0, libc6 (>= 2.29), libgcc-s1 (>= 3.4), libgoogle-perftools4, libpcrecpp0v5 (>= 7.7), libsnappy1v5 (>= 1.1.8), libssl1.1 (>= 1.1.0), libstdc++6 (>= 9), libstemmer0d (>= 0+svn527), libyaml-cpp0.6 (>= 0.6.2), zlib1g (>= 1:1.2.0) > Breaks: mongodb-server (<< 1:3.4.14-3ubuntu1) > Replaces: mongodb-server (<< 1:3.4.14-3ubuntu1) > Homepage: https://www.mongodb.org > Download-Size: 21,6 MB > APT-Sources: http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages [...] I don't know about build dependencies Am 28.07.20 um 11:36 schrieb Ronald Klop: > The same problem is going to happen with mongodb36 I presume. It uses > python2 to build, but does not need it to run. > Would it be possible to remove python2 as a RUN_DEPENDS at the end of > 2020, but keep it as a BUILD_DEPENDS in the ports framework? > > This might save some usefull ports. > > How are other projects (like Debian, etc.) solving this? > > Regards, > Ronald. > > > Van: Adriaan de Groot > Datum: maandag, 27 juli 2020 21:36 > Aan: freebsd-ports@freebsd.org > Onderwerp: Chromium (& derivatives) and Python 2.7 >> >> The Chromium build system -- and as a consequence, also QtWebEngine >> -- still >> uses Python 2.7. This is going to be a real problem about six months >> down the >> line, and I have no idea how upstream is going to deal with it. I've >> heard >> there are patches buried deep within the chocolate factory, but not from >> reliable sources. >> >> QtWebEngine is an even specialer case, since it's an LTS and also the >> last LTS >> in the Qt5 series, and I have real doubts about upstream -- The Qt >> Company -- >> being able or willing to deal with Python 2.7 deprecation there. >> >> Has anyone in FreeBSD tried to port the stuff over? I got about an >> hour or two >> into the porting process (making configure accept Python 3 is easy, but >> there's all these wretched code-generating scripts) and hit a brick >> wall of >> templating engines doing sensible Python 2.7 things. >> >> [ade] >> >> >> >> > ___ > 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" -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein signature.asc Description: OpenPGP digital signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/jasperreports | 5.5.2 | 6.14.0 +-+ databases/postgresql-mysql_fdw | 2_5_1 | rel-2_5_4 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ 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"
