On 2015-08-16 13:43, Jakub Wilk wrote:
> * Christian Kastner , 2015-08-15, 23:57:
The Vcs-Git URL should use the git:// protocol specifier, and you
could add a Vcs-Browser URL pointing to the github package, like so:
-Vcs-Git: https://github.com/asciiprod/yadifa.git
+Vcs-
* Christian Kastner , 2015-08-15, 23:57:
The Vcs-Git URL should use the git:// protocol specifier, and you
could add a Vcs-Browser URL pointing to the github package, like so:
-Vcs-Git: https://github.com/asciiprod/yadifa.git
+Vcs-Git: git://github.com/asciiprod/yadifa.git
The original URL
On 2015-08-15 16:17, Jakub Wilk wrote:
> * Christian Kastner , 2014-04-09, 20:50:
>> The Vcs-Git URL should use the git:// protocol specifier, and you
>> could add a Vcs-Browser URL pointing to the github package, like so:
>>
>> -Vcs-Git: https://github.com/asciiprod/yadifa.git
>> +Vcs-Git: git:/
* Christian Kastner , 2014-04-09, 20:50:
The Vcs-Git URL should use the git:// protocol specifier, and you could
add a Vcs-Browser URL pointing to the github package, like so:
-Vcs-Git: https://github.com/asciiprod/yadifa.git
+Vcs-Git: git://github.com/asciiprod/yadifa.git
The original URL
On 04/09/2014 09:00 PM, Christian Kastner wrote:
> Oh, I missed something here: you are using the substitution variable
> ${Description}, but you are not setting it anywhere, which results in
> half-empty descriptions (see the output in
> debian/libdns*/DEBIAN/control). See deb-substvars(5).
Agai
On 2014-04-09 20:50, Christian Kastner wrote:
>>> debian/control
>>> ==
>
> I like your approach with a common description provided through a
> substitution variable! Very efficient.
Oh, I missed something here: you are using the substitution variable
${Description}, but you are not s
On 2014-04-09 09:26, Markus Schade wrote:
> thanks for the review, Christian!
Glad I can help :-)
Here is some further feedback:
>> debian/control
>> ==
>> If you're using a VCS for your packaging, Vcs-* URLs would be nice (to
>> simplify contributing to your packaging). You can als
Hi,
thanks for the review, Christian!
On 04/05/2014 06:16 PM, Christian Kastner wrote:
> AFAIK bind9 only stores run-time data in /var/cache/bind (from dynamic
> DNS updates, etc). bind9's zone files are in /etc/bind/zones.
>
> [...]
>
> I'd either go with /etc/yadifa or /var/lib/yadifa. Check
Hi,
On 2014-03-18 22:34, Markus Schade wrote:> However there is one
question, which I am not sure, what is correct.
> Upstream uses /var/zones as base for its zone files. My guess was
> that this is not the proper location for such files in Debian. So I
> changed it to /var/cache/yadifa like bind9
Dear mentors,
I have made some corrections/improvements and re-uploaded the package
again.
However there is one question, which I am not sure, what is correct.
Upstream uses /var/zones as base for its zone files. My guess was that
this is not the proper location for such files in Debian.
So I cha
Hello,
since Martijn has not followed up on this bug for the last months,
I would like to ask if it is okay to have this bug assigned to me.
I have packaged the current version 1.0.3 and uploaded the package(s)
to mentors.debian.net seeking sponsorship:
http://mentors.debian.net/package/yadifa
11 matches
Mail list logo
