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

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

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

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. --

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:

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

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

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

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.

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. >

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

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

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

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

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

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