Package: leafnode
Version: 1.11.10-1
Followup-For: Bug #759869

THanks for having filed the bug and submitted the patch. I wondered
lately why I was having the same problem. I wondered that I must have
done something wrong while migrating my data from the previous laptop.


It also looks like Robert Grimm (DD maintaining leafnode) has not
uploaded since 2012. 

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages leafnode depends on:
ii  debconf [debconf-2.0]             1.5.55
ii  libc6                             2.19-15
ii  libpcre3                          2:8.35-3.3
ii  logrotate                         3.8.7-1+b1
ii  netbase                           5.3
ii  openbsd-inetd [inet-superserver]  0.20140418-2
ii  tcpd                              7.6.q-25

leafnode recommends no packages.

Versions of packages leafnode suggests:
ii  perl                5.20.2-2
pn  slrn | news-reader  <none>

-- Configuration Files:
/etc/cron.daily/leafnode changed:
. /etc/news/leafnode/debian-config
cd /
if [ -x /usr/sbin/texpire ]; then
   su news -s /bin/sh -c "/usr/sbin/texpire" >/dev/null
fi
if [ -x /usr/bin/touch_newsgroup -a -f /etc/news/leafnode/touch_groups ]; then
   if /usr/bin/perl -MNet::NNTP < /dev/null 2>/dev/null ; then
      su news -s /bin/sh -c "/usr/bin/touch_newsgroup -f 
/etc/news/leafnode/touch_groups"
   else
      cat << EOF
      You have requested that touch_newsgroup be run to mark the groups 
      listed in /etc/news/leafnode/touch_groups as read.  This requires
      that both perl and the Net::NNTP module (part of libnet-perl) are
      avalible, which does not appear to be the case:
EOF
      /usr/bin/perl -MNet::NNTP < /dev/null
   fi
fi
if [ "" != "`ls /var/spool/news/failed.postings/ 2>/dev/null`" ]; then
   cat << EOF
Some articles posted via Leafnode have been placed in the
failed.postings directory.  This typically means that they were
rejected by one or more of the upstream news servers.  Examining the
news log files should provide some indication as to why.
To retry the posting move the queue files into /var/spool/news/out.going
and run /usr/sbin/fetchnews.
EOF
   /usr/bin/newsq -f
fi


-- debconf information:
* leafnode/server: news.gmane.org
  leafnode/update-groups: false
  leafnode/purge: false
  leafnode/tcpd: true
* leafnode/network: permanent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to