Re: please update devel/android-tools-adb to 30.0.x
On 10/01/2021 2:17 pm, Masachika ISHIZUKA wrote: I've updated my nexus5 to crDroid 7.2 (android 11). After that, I couldn't connect via adb. Please update devel/android-tools-adb to 30.0.x. P.S. I can connect via adb 30.0.5 on ubuntu. -- Masachika ISHIZUKA Could you please create a Bugzilla issue with title: devel/android-tools-adb: Update to 30.0.x Thanks! ___ 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: problem with pear-File_Archive
Hi all, > Am 10.01.2021 um 20:47 schrieb Robert Huff : > lang/php72 no longer exists. >What's up? PHP 7.2 is out of upstream support since Dec 1st 2020 and the port has consequently been retired for Q1. Kind regards, Patrick ___ 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"
problem with pear-File_Archive
Hello: Generating INDEX-13 - please wait..--- describe.accessibility --- --- describe.arabic --- [deletia] --- describe.x11-toolkits --- --- describe.x11-wm --- make_index: /usr/ports/archivers/pear-File_Archive: no entry for /usr/ports/lang/php72 lang/php72 no longer exists. What's up? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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"
License question - New port databases/libmswstr
I intend to update my databases/mdbtools port and add a new databases/libmswstr [1] port as a dependency. This new port should allow mdbtools to use indexes of databases in JET4 format. [1] https://reviews.freebsd.org/D27955 The author of libmswstr [2] did not include a license [3] with his Github project. [2] https://github.com/leecher1337/libmswstr [3] https://github.com/leecher1337/libmswstr/blob/master/COPYING It is not clear to me whether the reverse-engineered data and structures of libmswstr violate license terms and should therefore not be included as a port in FreeBSD. Personally, I think that this form of reverse engineering also happens in many other projects and therefore no legal problems are to be expected. Are there any ideas or statements on this in the community? Thanks in advance. Regards, Rainer Hurling ___ 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: Updating devel/tbb - Introducing devel/onetbb
On Sunday, January 10, 2021 6:29:07 AM CET Shane Ambler wrote: Hello Shane, > You don't have to do it all yourself, you create the bug reports to > change tbb and to create onetbb, one report can depend on the other so > they get committed together. My experience is being told to submit one > report for each port, not one patch to change multiple ports. > > Then you create a report to say blender fails to build with your new > port and add the report number to the Blocks list in your report. That > leaves me to submit a patch to update blender to work with your change > before your update can be committed. I would then add reports to update > other dependencies that block my update. > > At most you submit 20 reports to say xx/yy port needs updating. There is > devel/pybugz and ports-mgmt/freebsd-bugzilla-cli that could automate > that but I haven't used them so can't recommend either. > > Then all the depends and blocks get updated together or some ports can > get marked as broken if they fail to update in a suitable time. OK, using Bugzilla that way will help us synchronize changes and prevent the ports tree from having things depending on both versions. So, finally, here is the plan: - Create a master PR containing expected devel/tbb and devel/onetbb ports (with CONFLICTS). I won't commit devel/onetbb before, to avoid having new ports needing it while others are still not migrated. - Attach a blocking PR for each failing port and wait for patches - At last, commit the new port and all port changes together That should be OK that way :) Thanks again for help! I'll start working on that ASAP, stay tuned! -- Ganael LAPLANCHE http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac , http://www.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"
