Bug#796588: adjtimex: Has init script in runlevel S but no matching service file

2015-12-01 Thread Roger Shimizu
Dear Felipe,

Considering now we have consensus on the service file except the
description part, which is quite minor, I made a release build of
adjtimex package and uploaded to mentors.

I also created a RFS: https://bugs.debian.org/806797

Since you helped me greatly on the service file, which is the most
significant improvement of this version (adjtimex/1.29-6), I hope you
can kindly be my sponsor to upload. Thank you!

Cheers,
Roger



Bug#792428: openresolv: "Failed to get D-Bus connection" randomly at update and boot on bind9 restart

2015-12-01 Thread Thibaut Chèze
Hi,

Sorry about the late response, notifications seems to be failed.

/etc/resolvconf.conf:
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1
name_servers=127.0.0.1

search_domains=test

# Mirror the Debian package defaults for the below resolvers
# so that resolvconf integrates seemlessly.
#dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
#pdnsd_conf=/etc/pdnsd.conf
#unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
named_options=/var/lib/bind/resolvconf-options.conf
named_zones=/var/lib/bind/resolvconf-zones.conf


I did some tests since Thursday, with versions /3.7.0-1/, /3.7.1-1/ and
/3.7.2-1/, and I see a new message instead of the old one:
Failed to try-restart nscd.service: No such method 'TryRestartUnit'
Failed to try-restart named.service: No such method 'TryRestartUnit'


The second line appears alone some times.

These lines make me think that /systemd/ is used to reload the service,
but my configurations use /sysvinit/.
The previous version /3.5.2-1/ seems to use the init script in
//etc/init.d/ instead.

Best regards,

Thibaut Chèze



signature.asc
Description: OpenPGP digital signature


Bug#792430: openresolv: Fail if a zone is declared on multiple interfaces.

2015-12-01 Thread Thibaut Chèze
Hi,

Sorry about the late response, notification seems to have failed too.

To produce outputs that you requested, I did some tests.

test$ resolvconf -l
# resolv.conf from tun10.openvpn
search test1.example.org example.org test2.example.org
nameserver 192.168.1.1

# resolv.conf from wlan0
# resolv.conf for wlan0
domain test2.example.org
search test2.example.org. example.org. test1.example.org
nameserver 192.168.0.1


test$ resolvconf -v
DOMAIN='test2.example.org'
SEARCH='test test1.example.org example.org test2.example.org
test2.example.org. example.org. test1.example.org.'
NAMESERVERS='192.168.0.1'
LOCALNAMESERVERS=''
DOMAINS='test1.example.org:192.168.1.1 example.org:192.168.1.1
test2.example.org:192.168.1.1 test2.example.org.:192.168.0.1
example.org.:192.168.0.1 test1.example.org.:192.168.0.1'


The bug seems linked with the dot at the end of domain names.
When all entries have the same syntax, it works !

Can you add the trailing dot when it's not present ? It will limit DNS
queries with suffixes in /search/ (without that, a combination of
suffixes is tried for each query).


Otherwise, I do not think this is the best solution to merge resolvers
addresses provided by the various network interfaces for a zone.
Indeed, if the zone is the same on all networks, there is no problem.
But if not, wouldn't it cause strange behaviors, like not predictable
mixed resolutions, induced by timeouts for example ?
In my opinion, we should only have access to one zone at a time, the one
provided by the highest priority interface for example. However, it
would be useful to keep the fusion for resolvers on the same interface,
provided by different sources like DHCP and DHCPv6... What do you think ?

Best regards,

Thibaut Chèze



signature.asc
Description: OpenPGP digital signature


Processing of netrik_1.16.1-2_amd64.changes

2015-12-01 Thread Debian FTP Masters
netrik_1.16.1-2_amd64.changes uploaded successfully to localhost
along with the files:
  netrik_1.16.1-2.dsc
  netrik_1.16.1-2.debian.tar.xz
  netrik_1.16.1-2_amd64.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)



netrik_1.16.1-2_amd64.changes ACCEPTED into unstable

2015-12-01 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Dec 2015 00:31:56 +0100
Source: netrik
Binary: netrik
Architecture: source amd64
Version: 1.16.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Description:
 netrik - text mode WWW browser with vi like keybindings
Closes: 656004
Changes:
 netrik (1.16.1-2) unstable; urgency=medium
 .
   * QA upload. (See #770237)
 + Set Maintainer to QA group
   * Add collab-maint git repository and according Vcs-* headers.
   * Apply wrap-and-sort.
   * Convert to source format "3.0 (quilt)".
 + Fix AUTHORS.patch to properly convert file to UTF-8.
   * Bump debhelper compatibility to 9 as recommended.
 + Update versioned build-dependency on debhelper accordingly.
   * Rewrite debian/rules with dh v7 style and dh-autoreconf
 + Replace build-dependency on automake with dh-autoreconf
 + Remove debian/Makefile.* and patch out "SUBDIRS = debian"
 + No more delete files from orig.tar.gz in clean target.
 + Use dh_auto_{configure,build,install,clean}
   * Remove no more needed lintian override.
   * Rename all debian/netrik.… files to debian/… for consistency.
   * Declare compliance with Debian Policy 3.9.6.
   * Don't install test suite into binary package. (Also fixes lintian
 warning package-contains-timestamped-gzip.)
   * Install NEWS as upstream changelog instead just as documentation.
   * Fix lintian warning copyright-refers-to-symlink-license.
   * Apply configure.ac patch by Simon Ruderich to properly pass hardening
 flags. (Closes: #656004)
   * Add patch to fix spelling errors found by lintian.
   * Convert debian/copyright to machine-readable DEP-3 format.
   * Update long package description:
 + Add asterisks in front of list items.
 + Remove upstream author name (that's what debian/copyright is for)
 + Mention that there's neither HTTPS nor IPv6 support.
Checksums-Sha1:
 0d801f5cbbfe055c662dfdd3e6d7d6911c4da7f0 1855 netrik_1.16.1-2.dsc
 8108d4a7cd0490f0b7e8273fe8fee6de643a9a38 11012 netrik_1.16.1-2.debian.tar.xz
 f75c309a111e7bda90965f39ce1d4bd8bc23add4 242962 netrik_1.16.1-2_amd64.deb
Checksums-Sha256:
 6b213ccceefa1b9738156417e2664e2268fa844d3bd784b08bc07de2a45c3d93 1855 
netrik_1.16.1-2.dsc
 d2e05d9fbb63b4d69b3167d8ddd8395d86cb1be915257f2c41c4c8d6a297c126 11012 
netrik_1.16.1-2.debian.tar.xz
 241407ee1636eae34f4ef7262304d3f0eb64d568e6044dbb043b0ce41e313a5f 242962 
netrik_1.16.1-2_amd64.deb
Files:
 504f188eb69477b1009fa7be8aac303f 1855 web optional netrik_1.16.1-2.dsc
 328161271c1f1f59545e31d5dc343158 11012 web optional 
netrik_1.16.1-2.debian.tar.xz
 699c34f642133540e24d9e8cc7627a8e 242962 web optional netrik_1.16.1-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWXjUPAAoJEGvmY8daNcl1GVkQALBw/4llBnrwcCAvHL+laHOO
jlLryIFYsEP5b3XG6FVSQrirWQiJmwotKFu6nYjNtn42wO7uKrHfMO2rzLvAUmyt
mc2G3Xh4iB1co3NvYzHo6GrubpCCzLo0bINlVd/9vbe6kWStbWlgKTVHltswShWf
R/qugrdpNobMSojF+A7lOtbSHPtRoelYoTiXVGOMurHiG2i9xjjJkjAL3ROMdOi1
JJRTAx9Dupr1sJR9FAihZLp9xW5rygGouMGEfVn13MVlSm9wAgYPCGZ7E2D/zVCw
+NFNckxAyeMAExzj2lsUsfUvcFJzVZnbN8aP4pwTdEbZcoeqKYImCFvoToLlFhyA
aJE+rNyI4N8PQ8l9DlG9/LVebvfthhqUohxPkjb8+ltHkLM8vDmy14cIPgIikZ+h
EguVILTmnNhhKVIpQ9tbiCMEYt2xuuj+zH8w1bMIi3X8RXaQksnYWnxsgN7gzZgD
NOYNsW7EHDZX2/kl02P2tzRqw/KWiNfoERwBbeBhHHzqsK1+Y5jEEaFYFqB0bDhQ
enPXfVmgsRop4mOeVPmbY9tkXlPbwuCh0/pOzvFKqln/r/3ryDdZfMJn3CCKcHhr
eWNSlYFYG3EPlRKzT8b36UgLrK6TLgg8yGuO5ptSCUUwWIuXOyNGi/MVe3sAdpDW
HHKHXJOJZxZy4PhY8wzU
=nNv4
-END PGP SIGNATURE-


Thank you for your contribution to Debian.