Page MenuHomeFreeBSD
Differential D19141

net-p2p/jackett: Update to 0.10.733
ClosedPublic
Actions

Authored by kai on Feb 11 2019, 6:13 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Mar 5, 2:14 PM
Unknown Object (File)
Fri, Feb 28, 4:43 PM
Unknown Object (File)
Dec 12 2024, 6:01 AM
Unknown Object (File)
Nov 26 2024, 5:16 AM
Unknown Object (File)
Nov 26 2024, 5:16 AM
Unknown Object (File)
Nov 26 2024, 5:15 AM
Unknown Object (File)
Nov 26 2024, 4:47 AM
Unknown Object (File)
Nov 23 2024, 2:11 AM
View All 99 Files
Subscribers
None

Details

Reviewers
miwi
joneum
tcberner
Commits
rP492678: net-p2p/jackett: Update to 0.10.733
Summary

PR 235642

Changelog:

  • Lots of fixes to tracker definitions.
  • Added some new tracker definitions.
  • Removed some dead tracker definitions.

While I'm here:

  • Add LICENSE_FILE
Test Plan
  • poudriere (11.2-, 12.0-RELEASE, 13.0-CURRENT@r342772 amd64 + i386) -> OK
  • portlint -> OK

Runtime tests -> OK

Diff Detail

Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 22424
Build 21582: arc lint + arc unit

Event Timeline

kai created this revision.Feb 11 2019, 6:13 AM
Harbormaster completed remote builds in B22424: Diff 53757.Feb 11 2019, 6:13 AM
miwi accepted this revision.Feb 11 2019, 8:35 AM

LGTM

This revision is now accepted and ready to land.Feb 11 2019, 8:35 AM
Closed by commit rP492678: net-p2p/jackett: Update to 0.10.733 (authored by kai). · Explain WhyFeb 11 2019, 9:18 AM
This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

PathSize
net-p2p/
jackett/
3 lines
6 lines
26 lines

Diff 53757

View Options

net-p2p/jackett/Makefile

Show First 20 Lines • Show All 140 Lines • ▼ Show 20 Lines
[.programlisting] [.programlisting]
.... ....
# When upgrading to a new FreeBSD release, files which match MergeChanges # When upgrading to a new FreeBSD release, files which match MergeChanges
# will have any local changes merged into the version from the new release. # will have any local changes merged into the version from the new release.
MergeChanges /etc/ /var/named/etc/ /boot/device.hints MergeChanges /etc/ /var/named/etc/ /boot/device.hints
.... ....
List of directories with configuration files that `freebsd-update` should attempt to merge. List of directories with configuration files that `freebsd-update` should attempt to merge.
The file merge process is a series of man:diff[1] patches similar to man:mergemaster[8], but with fewer options. The file merge process is a series of man:diff[1] patches.
Merges are either accepted, open an editor, or cause `freebsd-update` to abort. Merges are either accepted, open an editor, or cause `freebsd-update` to abort.
When in doubt, backup [.filename]#/etc# and just accept the merges. When in doubt, backup [.filename]#/etc# and just accept the merges.
See man:mergemaster[8] for more information about `mergemaster`.
[.programlisting] [.programlisting]
.... ....
# Directory in which to store downloaded updates and temporary # Directory in which to store downloaded updates and temporary
# files used by FreeBSD Update. # files used by FreeBSD Update.
# WorkDir /var/db/freebsd-update # WorkDir /var/db/freebsd-update
.... ....
▲ Show 20 Lines • Show All 811 Lines • ▼ Show 20 Lines
A few final tasks complete the update. A few final tasks complete the update.
Any modified configuration files are merged with the new versions, outdated libraries are located and removed, then the system is restarted. Any modified configuration files are merged with the new versions, outdated libraries are located and removed, then the system is restarted.
[[updating-src-completing-merge-etcupdate]] [[updating-src-completing-merge-etcupdate]]
==== Merging Configuration Files with man:etcupdate[8] ==== Merging Configuration Files with man:etcupdate[8]
man:etcupdate[8] is a tool for managing updates to files that are not updated as part of an installworld such as files located in [.filename]#/etc/#. man:etcupdate[8] is a tool for managing updates to files that are not updated as part of an installworld such as files located in [.filename]#/etc/#.
It manages updates by doing a three-way merge of changes made to these files against the local versions. It manages updates by doing a three-way merge of changes made to these files against the local versions.
It is also designed to minimize the amount of user intervention, in contrast to man:mergemaster[8]'s interactive prompts. man:etcupdate[8] is designed to minimize the amount of user intervention.
[NOTE] [NOTE]
==== ====
In general, man:etcupdate[8] does not need any specific arguments for its job. In general, man:etcupdate[8] does not need any specific arguments for its job.
There is however a handy in between command for sanity checking what will be done the first time man:etcupdate[8] is used: There is however a handy in between command for sanity checking what will be done the first time man:etcupdate[8] is used:
[source,shell] [source,shell]
.... ....
Show All 21 Lines
# etcupdate diff <.> # etcupdate diff <.>
.... ....
<.> Bootstrap the database of stock [.filename]#/etc# files; for more information see man:etcupdate[8]. <.> Bootstrap the database of stock [.filename]#/etc# files; for more information see man:etcupdate[8].
<.> Check the diff after bootstrapping. Trim any local changes that are no longer needed to reduce the chance of conflicts in future updates. <.> Check the diff after bootstrapping. Trim any local changes that are no longer needed to reduce the chance of conflicts in future updates.
==== ====
[[updating-src-completing-merge-mergemaster]]
==== Merging Configuration Files with man:mergemaster[8]
man:mergemaster[8] provides a way to merge changes that have been made to system configuration files with new versions of those files.
man:mergemaster[8] is an alternative to the preferred man:etcupdate[8]
With `-Ui`, man:mergemaster[8] automatically updates files that have not been user-modified and installs new files that are not already present:
[source,shell]
....
# mergemaster -Ui
....
If a file must be manually merged, an interactive display allows the user to choose which portions of the files are kept.
See man:mergemaster[8] for more information.
If the standard [.filename]#/usr/src# was not used, another parameter must be passed to man:mergemaster[8]:
[source,shell]
....
# mergemaster -Ui PATH_TO_SRC
....
[[updating-src-completing-check-old]] [[updating-src-completing-check-old]]
==== Checking for Outdated Files and Libraries ==== Checking for Outdated Files and Libraries
Some obsolete files or directories can remain after an update. Some obsolete files or directories can remain after an update.
These files can be located: These files can be located:
[source,shell] [source,shell]
.... ....
▲ Show 20 Lines • Show All 75 Lines • ▼ Show 20 Lines
Also, each build machine should have its kernel name set with `KERNCONF` in [.filename]#/etc/make.conf#, Also, each build machine should have its kernel name set with `KERNCONF` in [.filename]#/etc/make.conf#,
and the build machine should list them all in its `KERNCONF`, listing its own kernel first. and the build machine should list them all in its `KERNCONF`, listing its own kernel first.
The build machine must have the kernel configuration files for each machine in its [.filename]#/usr/src/sys/arch/conf#. The build machine must have the kernel configuration files for each machine in its [.filename]#/usr/src/sys/arch/conf#.
On the build machine, build the kernel and world as described in <<makeworld>>, On the build machine, build the kernel and world as described in <<makeworld>>,
but do not install anything on the build machine. but do not install anything on the build machine.
Instead, install the built kernel on the test machine. Instead, install the built kernel on the test machine.
On the test machine, mount [.filename]#/usr/src# and [.filename]#/usr/obj# via NFS. On the test machine, mount [.filename]#/usr/src# and [.filename]#/usr/obj# via NFS.
Then, run `shutdown now` to go to single-user mode in order to install the new kernel and world and run `mergemaster` as usual. Then, run `shutdown now` to go to single-user mode in order to install the new kernel and world and run `etcupdate` as usual.
When done, reboot to return to normal multi-user operations. When done, reboot to return to normal multi-user operations.
After verifying that everything on the test machine is working properly, After verifying that everything on the test machine is working properly,
use the same procedure to install the new software on each of the other machines in the build set. use the same procedure to install the new software on each of the other machines in the build set.
The same methodology can be used for the ports tree. The same methodology can be used for the ports tree.
The first step is to share [.filename]#/usr/ports# via NFS to all the machines in the build set. The first step is to share [.filename]#/usr/ports# via NFS to all the machines in the build set.
To configure [.filename]#/etc/make.conf# to share distfiles, To configure [.filename]#/etc/make.conf# to share distfiles,
▲ Show 20 Lines • Show All 50 Lines • Show Last 20 Lines
View Options

net-p2p/jackett/distinfo

Show First 20 Lines • Show All 140 Lines • ▼ Show 20 Lines
[.programlisting] [.programlisting]
.... ....
# When upgrading to a new FreeBSD release, files which match MergeChanges # When upgrading to a new FreeBSD release, files which match MergeChanges
# will have any local changes merged into the version from the new release. # will have any local changes merged into the version from the new release.
MergeChanges /etc/ /var/named/etc/ /boot/device.hints MergeChanges /etc/ /var/named/etc/ /boot/device.hints
.... ....
List of directories with configuration files that `freebsd-update` should attempt to merge. List of directories with configuration files that `freebsd-update` should attempt to merge.
The file merge process is a series of man:diff[1] patches similar to man:mergemaster[8], but with fewer options. The file merge process is a series of man:diff[1] patches.
Merges are either accepted, open an editor, or cause `freebsd-update` to abort. Merges are either accepted, open an editor, or cause `freebsd-update` to abort.
When in doubt, backup [.filename]#/etc# and just accept the merges. When in doubt, backup [.filename]#/etc# and just accept the merges.
See man:mergemaster[8] for more information about `mergemaster`.
[.programlisting] [.programlisting]
.... ....
# Directory in which to store downloaded updates and temporary # Directory in which to store downloaded updates and temporary
# files used by FreeBSD Update. # files used by FreeBSD Update.
# WorkDir /var/db/freebsd-update # WorkDir /var/db/freebsd-update
.... ....
▲ Show 20 Lines • Show All 811 Lines • ▼ Show 20 Lines
A few final tasks complete the update. A few final tasks complete the update.
Any modified configuration files are merged with the new versions, outdated libraries are located and removed, then the system is restarted. Any modified configuration files are merged with the new versions, outdated libraries are located and removed, then the system is restarted.
[[updating-src-completing-merge-etcupdate]] [[updating-src-completing-merge-etcupdate]]
==== Merging Configuration Files with man:etcupdate[8] ==== Merging Configuration Files with man:etcupdate[8]
man:etcupdate[8] is a tool for managing updates to files that are not updated as part of an installworld such as files located in [.filename]#/etc/#. man:etcupdate[8] is a tool for managing updates to files that are not updated as part of an installworld such as files located in [.filename]#/etc/#.
It manages updates by doing a three-way merge of changes made to these files against the local versions. It manages updates by doing a three-way merge of changes made to these files against the local versions.
It is also designed to minimize the amount of user intervention, in contrast to man:mergemaster[8]'s interactive prompts. man:etcupdate[8] is designed to minimize the amount of user intervention.
[NOTE] [NOTE]
==== ====
In general, man:etcupdate[8] does not need any specific arguments for its job. In general, man:etcupdate[8] does not need any specific arguments for its job.
There is however a handy in between command for sanity checking what will be done the first time man:etcupdate[8] is used: There is however a handy in between command for sanity checking what will be done the first time man:etcupdate[8] is used:
[source,shell] [source,shell]
.... ....
Show All 21 Lines
# etcupdate diff <.> # etcupdate diff <.>
.... ....
<.> Bootstrap the database of stock [.filename]#/etc# files; for more information see man:etcupdate[8]. <.> Bootstrap the database of stock [.filename]#/etc# files; for more information see man:etcupdate[8].
<.> Check the diff after bootstrapping. Trim any local changes that are no longer needed to reduce the chance of conflicts in future updates. <.> Check the diff after bootstrapping. Trim any local changes that are no longer needed to reduce the chance of conflicts in future updates.
==== ====
[[updating-src-completing-merge-mergemaster]]
==== Merging Configuration Files with man:mergemaster[8]
man:mergemaster[8] provides a way to merge changes that have been made to system configuration files with new versions of those files.
man:mergemaster[8] is an alternative to the preferred man:etcupdate[8]
With `-Ui`, man:mergemaster[8] automatically updates files that have not been user-modified and installs new files that are not already present:
[source,shell]
....
# mergemaster -Ui
....
If a file must be manually merged, an interactive display allows the user to choose which portions of the files are kept.
See man:mergemaster[8] for more information.
If the standard [.filename]#/usr/src# was not used, another parameter must be passed to man:mergemaster[8]:
[source,shell]
....
# mergemaster -Ui PATH_TO_SRC
....
[[updating-src-completing-check-old]] [[updating-src-completing-check-old]]
==== Checking for Outdated Files and Libraries ==== Checking for Outdated Files and Libraries
Some obsolete files or directories can remain after an update. Some obsolete files or directories can remain after an update.
These files can be located: These files can be located:
[source,shell] [source,shell]
.... ....
▲ Show 20 Lines • Show All 75 Lines • ▼ Show 20 Lines
Also, each build machine should have its kernel name set with `KERNCONF` in [.filename]#/etc/make.conf#, Also, each build machine should have its kernel name set with `KERNCONF` in [.filename]#/etc/make.conf#,
and the build machine should list them all in its `KERNCONF`, listing its own kernel first. and the build machine should list them all in its `KERNCONF`, listing its own kernel first.
The build machine must have the kernel configuration files for each machine in its [.filename]#/usr/src/sys/arch/conf#. The build machine must have the kernel configuration files for each machine in its [.filename]#/usr/src/sys/arch/conf#.
On the build machine, build the kernel and world as described in <<makeworld>>, On the build machine, build the kernel and world as described in <<makeworld>>,
but do not install anything on the build machine. but do not install anything on the build machine.
Instead, install the built kernel on the test machine. Instead, install the built kernel on the test machine.
On the test machine, mount [.filename]#/usr/src# and [.filename]#/usr/obj# via NFS. On the test machine, mount [.filename]#/usr/src# and [.filename]#/usr/obj# via NFS.
Then, run `shutdown now` to go to single-user mode in order to install the new kernel and world and run `mergemaster` as usual. Then, run `shutdown now` to go to single-user mode in order to install the new kernel and world and run `etcupdate` as usual.
When done, reboot to return to normal multi-user operations. When done, reboot to return to normal multi-user operations.
After verifying that everything on the test machine is working properly, After verifying that everything on the test machine is working properly,
use the same procedure to install the new software on each of the other machines in the build set. use the same procedure to install the new software on each of the other machines in the build set.
The same methodology can be used for the ports tree. The same methodology can be used for the ports tree.
The first step is to share [.filename]#/usr/ports# via NFS to all the machines in the build set. The first step is to share [.filename]#/usr/ports# via NFS to all the machines in the build set.
To configure [.filename]#/etc/make.conf# to share distfiles, To configure [.filename]#/etc/make.conf# to share distfiles,
▲ Show 20 Lines • Show All 50 Lines • Show Last 20 Lines
View Options

net-p2p/jackett/pkg-plist

Show First 20 Lines • Show All 140 Lines • ▼ Show 20 Lines
[.programlisting] [.programlisting]
.... ....
# When upgrading to a new FreeBSD release, files which match MergeChanges # When upgrading to a new FreeBSD release, files which match MergeChanges
# will have any local changes merged into the version from the new release. # will have any local changes merged into the version from the new release.
MergeChanges /etc/ /var/named/etc/ /boot/device.hints MergeChanges /etc/ /var/named/etc/ /boot/device.hints
.... ....
List of directories with configuration files that `freebsd-update` should attempt to merge. List of directories with configuration files that `freebsd-update` should attempt to merge.
The file merge process is a series of man:diff[1] patches similar to man:mergemaster[8], but with fewer options. The file merge process is a series of man:diff[1] patches.
Merges are either accepted, open an editor, or cause `freebsd-update` to abort. Merges are either accepted, open an editor, or cause `freebsd-update` to abort.
When in doubt, backup [.filename]#/etc# and just accept the merges. When in doubt, backup [.filename]#/etc# and just accept the merges.
See man:mergemaster[8] for more information about `mergemaster`.
[.programlisting] [.programlisting]
.... ....
# Directory in which to store downloaded updates and temporary # Directory in which to store downloaded updates and temporary
# files used by FreeBSD Update. # files used by FreeBSD Update.
# WorkDir /var/db/freebsd-update # WorkDir /var/db/freebsd-update
.... ....
▲ Show 20 Lines • Show All 811 Lines • ▼ Show 20 Lines
A few final tasks complete the update. A few final tasks complete the update.
Any modified configuration files are merged with the new versions, outdated libraries are located and removed, then the system is restarted. Any modified configuration files are merged with the new versions, outdated libraries are located and removed, then the system is restarted.
[[updating-src-completing-merge-etcupdate]] [[updating-src-completing-merge-etcupdate]]
==== Merging Configuration Files with man:etcupdate[8] ==== Merging Configuration Files with man:etcupdate[8]
man:etcupdate[8] is a tool for managing updates to files that are not updated as part of an installworld such as files located in [.filename]#/etc/#. man:etcupdate[8] is a tool for managing updates to files that are not updated as part of an installworld such as files located in [.filename]#/etc/#.
It manages updates by doing a three-way merge of changes made to these files against the local versions. It manages updates by doing a three-way merge of changes made to these files against the local versions.
It is also designed to minimize the amount of user intervention, in contrast to man:mergemaster[8]'s interactive prompts. man:etcupdate[8] is designed to minimize the amount of user intervention.
[NOTE] [NOTE]
==== ====
In general, man:etcupdate[8] does not need any specific arguments for its job. In general, man:etcupdate[8] does not need any specific arguments for its job.
There is however a handy in between command for sanity checking what will be done the first time man:etcupdate[8] is used: There is however a handy in between command for sanity checking what will be done the first time man:etcupdate[8] is used:
[source,shell] [source,shell]
.... ....
Show All 21 Lines
# etcupdate diff <.> # etcupdate diff <.>
.... ....
<.> Bootstrap the database of stock [.filename]#/etc# files; for more information see man:etcupdate[8]. <.> Bootstrap the database of stock [.filename]#/etc# files; for more information see man:etcupdate[8].
<.> Check the diff after bootstrapping. Trim any local changes that are no longer needed to reduce the chance of conflicts in future updates. <.> Check the diff after bootstrapping. Trim any local changes that are no longer needed to reduce the chance of conflicts in future updates.
==== ====
[[updating-src-completing-merge-mergemaster]]
==== Merging Configuration Files with man:mergemaster[8]
man:mergemaster[8] provides a way to merge changes that have been made to system configuration files with new versions of those files.
man:mergemaster[8] is an alternative to the preferred man:etcupdate[8]
With `-Ui`, man:mergemaster[8] automatically updates files that have not been user-modified and installs new files that are not already present:
[source,shell]
....
# mergemaster -Ui
....
If a file must be manually merged, an interactive display allows the user to choose which portions of the files are kept.
See man:mergemaster[8] for more information.
If the standard [.filename]#/usr/src# was not used, another parameter must be passed to man:mergemaster[8]:
[source,shell]
....
# mergemaster -Ui PATH_TO_SRC
....
[[updating-src-completing-check-old]] [[updating-src-completing-check-old]]
==== Checking for Outdated Files and Libraries ==== Checking for Outdated Files and Libraries
Some obsolete files or directories can remain after an update. Some obsolete files or directories can remain after an update.
These files can be located: These files can be located:
[source,shell] [source,shell]
.... ....
▲ Show 20 Lines • Show All 75 Lines • ▼ Show 20 Lines
Also, each build machine should have its kernel name set with `KERNCONF` in [.filename]#/etc/make.conf#, Also, each build machine should have its kernel name set with `KERNCONF` in [.filename]#/etc/make.conf#,
and the build machine should list them all in its `KERNCONF`, listing its own kernel first. and the build machine should list them all in its `KERNCONF`, listing its own kernel first.
The build machine must have the kernel configuration files for each machine in its [.filename]#/usr/src/sys/arch/conf#. The build machine must have the kernel configuration files for each machine in its [.filename]#/usr/src/sys/arch/conf#.
On the build machine, build the kernel and world as described in <<makeworld>>, On the build machine, build the kernel and world as described in <<makeworld>>,
but do not install anything on the build machine. but do not install anything on the build machine.
Instead, install the built kernel on the test machine. Instead, install the built kernel on the test machine.
On the test machine, mount [.filename]#/usr/src# and [.filename]#/usr/obj# via NFS. On the test machine, mount [.filename]#/usr/src# and [.filename]#/usr/obj# via NFS.
Then, run `shutdown now` to go to single-user mode in order to install the new kernel and world and run `mergemaster` as usual. Then, run `shutdown now` to go to single-user mode in order to install the new kernel and world and run `etcupdate` as usual.
When done, reboot to return to normal multi-user operations. When done, reboot to return to normal multi-user operations.
After verifying that everything on the test machine is working properly, After verifying that everything on the test machine is working properly,
use the same procedure to install the new software on each of the other machines in the build set. use the same procedure to install the new software on each of the other machines in the build set.
The same methodology can be used for the ports tree. The same methodology can be used for the ports tree.
The first step is to share [.filename]#/usr/ports# via NFS to all the machines in the build set. The first step is to share [.filename]#/usr/ports# via NFS to all the machines in the build set.
To configure [.filename]#/etc/make.conf# to share distfiles, To configure [.filename]#/etc/make.conf# to share distfiles,
▲ Show 20 Lines • Show All 50 Lines • Show Last 20 Lines