Re: GitHub migration complete
On Mon, Oct 31, 2016 at 12:38 AM, Lawrence Velázquez wrote: > Old habits die hard, but from now on do NOT refer to Trac tickets as > "#12345" in your commit messages; GitHub's website interprets those as > pull request numbers. Copy and paste the full Trac URL instead. > Sounds like a job for a commit-msg hook (sadly it can't rewrite them, just see #xxx and suggest replacements). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: GitHub migration complete
> On Oct 30, 2016, at 9:54 PM, Clemens Lang wrote: > > MacPorts developers should now have commit access to the GitHub > repositories. A quick reminder about commit messages: Old habits die hard, but from now on do NOT refer to Trac tickets as "#12345" in your commit messages; GitHub's website interprets those as pull request numbers. Copy and paste the full Trac URL instead. vq P.S. If you want to see something nifty, use this line in a commit that resolves a ticket: Closes: https://trac.macports.org/ticket/[NUMBER] ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: GitHub migration complete
> On Oct 30, 2016, at 9:54 PM, Clemens Lang wrote: > > Our Subversion repository has been split into several repositories on > GitHub. Please note that Ryan ran the svn2git conversion several times this weekend, so any clones made previously will have nothing in common with the final repositories, and a naïve "git pull" will try to produce a merge commit. This is not desirable. You should instead press the proverbial reset button. Assuming you made a straightforward clone and only checked out a local master branch: $ git fetch $ git reset --hard origin/master $ git gc --aggressive This fetches the new history, forces your local master branch to match ours, and garbage-collects the old objects. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: GitHub migration complete
> On Oct 30, 2016, at 10:28 PM, Carlo Tambuatco wrote: > > Is that mailto link macports-us...@lists.macosforge.org in the signature > still valid…? Yes, our previous mailing lists have not moved yet. And even when they do, the old addresses will remain valid. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
GitHub migration complete
Good day MacPorts developers and users, We are pleased to announce that MacPorts has moved to GitHub. Our Subversion repository has been split into several repositories on GitHub . The buildbot, email notifications, and Trac are now triggered by changes made on GitHub. MacPorts developers should now have commit access to the GitHub repositories. If you are a MacPorts developer and have not yet joined the MacPorts GitHub organization, please follow instructions in the FAQ linked below. If you have further questions, please refer to this new FAQ page: https://trac.macports.org/wiki/FAQ/GitHubMigration If your question is not yet answered, ask on the mailing lists so it can be added. We have tested the changes thoroughly, but in a system this complex there might still be undiscovered problems. If you notice any, please do not hesitate to ask on the mailing lists or file a ticket in Trac against the "server/hosting" component. On behalf of the MacPorts migration team, Lawrence Velázquez Rainer Müller Ryan Schmidt Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Subversion switched to read-only
Hi everybody, we are making Subversion read-only in a couple of seconds. If you get an error message when comitting that is expected. We will re-configure a couple of hooks and tools to the new GitHub-based setup and then enable write access on GitHub. We try to keep the downtime short and will keep you updated. -- Clemens ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compiling dnsmasq with dnssec support?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
On 30.10.16 17:28 Clemens Lang wrote:
> I'd suggest to just enable it without a variant. If it's
> configurable at runtime, I don't see the need to make users jump
> through hoops.
I tried both, and both seemed to work in my tests.
This is just a rough draft, as I do not know if it is better to put
the trust-anchors in a separate file (which seems to be the case
upstream) or not.
Find my two Portfiles attached.
Johannes
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlgWIvcACgkQzi3gQ/xETbLLXwCfWizZtGKqkpdrclOJB8nyARFR
uUQAni1tbeSAgxOffs/fqtMNkMsPvqN9
=Ul/2
-END PGP SIGNATURE-
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
# $Id: Portfile 148957 2016-05-23 19:28:42Z s...@macports.org $
PortSystem 1.0
namednsmasq
version 2.76
categories net
license GPL
maintainers snc openmaintainer
description lightweight DNS forwarder and DHCP server
long_descriptionDnsmasq is lightweight, easy to configure DNS \
forwarder and DHCP server. It is designed to provide \
DNS and, optionally, DHCP, to a small network. It can \
serve the names of local machines which are not in the \
global DNS. The DHCP server integrates with the DNS \
server and allows machines with DHCP-allocated \
addresses to appear in the DNS with names configured \
either in each host or in a central configuration \
file. Dnsmasq supports static and dynamic DHCP leases \
and BOOTP for network booting of diskless machines.
homepagehttp://www.thekelleys.org.uk/dnsmasq/doc.html
platforms darwin
notes "A startup item has been generated that will aid in\
starting ${name} with launchd. You must specify the\
path to resolv.conf. For your protection, this script\
is disabled by default. Execute the following command\
to start it, and to cause it to launch at startup:\
\n\nsudo port load ${name}"
master_siteshttp://www.thekelleys.org.uk/dnsmasq/
use_xz yes
checksums rmd160 9932b6624dd705fa8826b055ebe23138d3b0302b \
sha256
4b92698dee19ca0cb2a8f2e48f1d2dffd01a21eb15d1fbed4cf085630c8c9f96
patchfiles patch-src-config.h.diff \
patch-src-network.c.diff
post-patch {
reinplace "s|@PREFIX@|${prefix}|g" ${worksrcpath}/src/config.h
reinplace s|#resolv-file=|resolv-file=/etc/resolv.conf| \
${worksrcpath}/dnsmasq.conf.example
}
use_configure no
variant universal {}
build.env-appendCC="${configure.cc} [get_canonical_archflags]"
destroot.env-appendCC="${configure.cc} [get_canonical_archflags]"
destroot.args PREFIX=${prefix}
destroot.keepdirs ${destroot}${prefix}/var/run/${name}
livecheck.type regex
livecheck.url ${master_sites}
livecheck.regex LATEST_IS_(\\d\\.\\d+)
# TODO: remove no_* variants after 2015-01-09
if { ! [variant_isset no_dhcp] } {
default_variants-append +dhcp
}
if { ! [variant_isset no_tftp] } {
default_variants-append +tftp
}
if { ! [variant_isset no_ipv6] } {
default_variants-append +ipv6
}
variant no_dhcp conflicts dhcp description { obsolete } {}
variant dhcp conflicts no_dhcp description { Provide built-in DHCP server } {
build.args-delete -DNO_DHCP
}
variant no_tftp conflicts tftp description { obsolete } {}
variant tftp conflicts no_tftp description { Provide built-in TFTP server } {
build.args-delete -DNO_TFTP
}
variant no_ipv6 conflicts ipv6 description { obsolete } {}
variant ipv6 conflicts no_ipv6 description { Provide IPV6 support } {
build.args-delete -DNO_IPV6
}
variant dnssec description {Enable DNSSEC} {
patchfiles-appendpatch-src-config.h_DNSSEC.diff
}
set COPTS {}
if {![variant_isset dhcp]} {
lappend COPTS -DNO_DHCP
}
if {![variant_isset tftp]} {
lappend COPTS -DNO_TFTP
}
if {![variant_isset ipv6]} {
lappend COPTS -DNO_IPV6
}
if {[llength $COPTS] > 0} {
set mycopts [join $COPTS " "]
build.args-append COPTS="$mycopts"
}
post-destroot {
copy ${worksrcpath}/dnsmasq.conf.example
${destroot}${prefix}/etc/dnsmasq.conf.example
# Create the directory that dnsmasq likes to store its pid in.
xinstall -d -m 777 ${destroot}${prefix}/var/run/${name}
#
# Set up a launchd item. The daemondo wrapper is not needed.
#
# Create the plist file.
set itemname${startupitem.name}
set uniquename ${startupitem.uniquename}
set plistname ${startupitem.plist}
set daemondest ${startupitem.location}
set itemdir ${prefix}/etc
Re: Compiling dnsmasq with dnssec support?
Hi, On Sun, Oct 30, 2016 at 04:50:33PM +0100, Johannes Kastl wrote: > Thanks Rainer, I'll try that. I'd suggest to just enable it without a variant. If it's configurable at runtime, I don't see the need to make users jump through hoops. -- Clemens ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compiling dnsmasq with dnssec support?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30.10.16 16:49 Rainer Müller wrote:
> On 2016-10-30 16:40, Johannes Kastl wrote:
>> As the documentation (at least the pages I found) does not have
>> an example of this, do you know of any port that uses this?
>
> variant dnssec description {Enable DNSSEC} { patchfiles-append
> patch-dnssec.diff }
Thanks Rainer, I'll try that.
Johannes
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlgWFsQACgkQzi3gQ/xETbKAfwCeIb2W57P4kKyrZTpdbiKfrdJE
cgoAn2l85xu0nPwSDvi9+Az2G2NtC9Ul
=P3nv
-END PGP SIGNATURE-
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compiling dnsmasq with dnssec support?
On 2016-10-30 16:40, Johannes Kastl wrote:
> Hi Joshua,
>
> On 30.10.16 12:19 Joshua Root wrote:
>> On 2016-10-30 19:15 , Johannes Kastl wrote:
>>> Question 1: Is it possible to use different
>>> patchfiles-statements, depending on the variant?
>
>> Yes.
>
> As the documentation (at least the pages I found) does not have an
> example of this, do you know of any port that uses this?
variant dnssec description {Enable DNSSEC} {
patchfiles-appendpatch-dnssec.diff
}
Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compiling dnsmasq with dnssec support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Joshua, On 30.10.16 12:19 Joshua Root wrote: > On 2016-10-30 19:15 , Johannes Kastl wrote: >> Question 1: Is it possible to use different >> patchfiles-statements, depending on the variant? > > Yes. As the documentation (at least the pages I found) does not have an example of this, do you know of any port that uses this? >> Question 2: Is it possible to add another patch in one >> variant? > > Yes. see above. >> Question 3: Is there any reason why no +dnssec variant exists? >> Or why dnssec is not enabled by default (as long as the dnssec >> stuff is commented in the dnsmasq.conf it should not interfere, >> I guess)? > > Probably just nobody asked for it before now. That was my first guess. Johannes -BEGIN PGP SIGNATURE- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlgWFFoACgkQzi3gQ/xETbIvvwCeNYjoEpfjwZ6Mn2+/GZG8t72s PwwAn1ZzdE1rFqHFU5n4SaUNJ63LL9fv =RnpW -END PGP SIGNATURE- ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
Hi, On Sat, Oct 29, 2016 at 08:21:23PM -0700, Fred Wright wrote: > Though if the new "Cc me" button were any smaller, it would be > considered a web bug. :-) That's https://trac.macports.org/ticket/52675 If you have time, read through the ticket and submit a pull request to fix it. -- Clemens ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Trac's Cc Me button is too small
On 2016-10-30 04:21, Fred Wright wrote: > Though if the new "Cc me" button were any smaller, it would be considered > a web bug. :-) I agree it is too small. The CSS rules for this button are minimal in addition to what Trac has for all other buttons. CSS and full plugin sources are available and linked in the corresponding ticket. If anyone has suggestions how to make it look better, just post them. https://trac.macports.org/ticket/52675 Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compiling dnsmasq with dnssec support?
On 2016-10-30 19:15 , Johannes Kastl wrote: Question 1: Is it possible to use different patchfiles-statements, depending on the variant? Yes. Question 2: Is it possible to add another patch in one variant? Yes. Question 3: Is there any reason why no +dnssec variant exists? Or why dnssec is not enabled by default (as long as the dnssec stuff is commented in the dnsmasq.conf it should not interfere, I guess)? Probably just nobody asked for it before now. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compiling dnsmasq with dnssec support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30.10.16 09:15 Johannes Kastl wrote: >> patchfiles patch-src-config.h.diff \ >> patch-src-network.c.diff \ patch-src-config.h_DNSSEC.diff This would be the patch file patch-src-config.h_DNSSEC.diff: ### - --- src/config.h.orig 2016-10-30 07:35:53.0 +0100 +++ src/config.h2016-10-30 07:36:08.0 +0100 @@ -174,7 +174,7 @@ /* #define HAVE_DBUS */ /* #define HAVE_IDN */ /* #define HAVE_CONNTRACK */ - -/* #define HAVE_DNSSEC */ +#define HAVE_DNSSEC /* Default locations for important system files. */ ### Johannes -BEGIN PGP SIGNATURE- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlgVsdEACgkQzi3gQ/xETbI/wwCeNHCFWvoZw0fTqkNMIEkqG3zm iW8An1MTuVoWNPHtuRuM+h/N1UcpSlXA =ki96 -END PGP SIGNATURE- ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Compiling dnsmasq with dnssec support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I just tried to get dnssec working with dnsmasq, but I found no way to compile it with DNSSEC via macports (i.e. there is no variant +dnssec). I tried to create a variant (in my local repository), which sets - -DHAVE_DNSSEC in the COPTS list, but during compilation it never got used and thus dnsmasq does not start as soon as dnssec-related options (https://wiki.gentoo.org/wiki/Dnsmasq#DNSSEC) appear in the conf file. I then created a patch, put it into the files folder, and told the portfile to use it: > patchfiles patch-src-config.h.diff \ > patch-src-network.c.diff \ patch-src-config.h_DNSSEC.diff And now it seems to compile and does start with dnssec-related stuff in dnsmasq.conf. If I understand the config.h correctly, using COPTS should work, alas in my tests it did not... Question 1: Is it possible to use different patchfiles-statements, depending on the variant? Question 2: Is it possible to add another patch in one variant? Question 3: Is there any reason why no +dnssec variant exists? Or why dnssec is not enabled by default (as long as the dnssec stuff is commented in the dnsmasq.conf it should not interfere, I guess)? Kind regards, Johannes -BEGIN PGP SIGNATURE- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlgVrBYACgkQzi3gQ/xETbI9AwCfXtv3w95oB02aRR5WKSTh5rjB wd8AnRmFrpV/M6/Xy3LCiJY0qc4xJnJ9 =9w20 -END PGP SIGNATURE- ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
