Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 123820

Summary: Ebuild for Chestnut-dialer-0.3.2
Product: Gentoo Linux Reporter: Slavkin Oleg A. <maxanat>
Component: New packagesAssignee: Default Assignee for New Packages <maintainer-wanted>
Status: CONFIRMED ---    
Severity: enhancement CC: gpopac, syscoder, v_2e
Priority: High Keywords: EBUILD
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://chestnut-dialer.sourceforge.net/
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: ebuild
updated ebuild for chestnut
chestnut-dialer-0.3.3.ebuild
chestnut-dialer-9999.ebuild
chestnut-dialer-0.3.3-r1.ebuild
chestnut-dialer-0.3.3-ifconfig.patch
chestnut-dialer-0.3.3-r2.ebuild
chestnut-dialer-0.3.3-disconnections.patch

Description Slavkin Oleg A. 2006-02-23 06:53:48 UTC
Chestnut Dialer is PPP (Point to Point Protocol) dialing program, written in Python.
Comment 1 Slavkin Oleg A. 2006-02-23 06:55:26 UTC
Created attachment 80518 [details]
ebuild

Author this ebuild Popov Maxim B.
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2006-02-23 08:05:39 UTC
- Please attach file as plain text
- S=${WORKDIR}/${P} is superfluous
- remove the lines you've commented out.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-07-12 23:51:13 UTC
*** Bug 140174 has been marked as a duplicate of this bug. ***
Comment 4 Paulo Matias 2006-07-13 05:21:35 UTC
Created attachment 91636 [details]
updated ebuild for chestnut

Attached the updated ebuild, as requested by Jakub Moc.
Comment 5 Milos Popovic 2007-03-22 19:21:46 UTC
Created attachment 114077 [details]
chestnut-dialer-0.3.3.ebuild

New chestnut.
domenu does not work, I put make_desktop... instead
Comment 6 Milos Popovic 2007-04-23 23:10:16 UTC
Created attachment 117106 [details]
chestnut-dialer-9999.ebuild

Here is SVN ebuild for those who don't wana wait 0.4.0 to get System Tray Icon and Serbian translation. Note that you need both QT and GTK2 for Python to compile this program from svn (no mather you don't use both of them).
Comment 7 Vladimir 2013-01-14 01:51:16 UTC
Created attachment 335556 [details]
chestnut-dialer-0.3.3-r1.ebuild

A new rewritten ebuild for net-dialup/chestnut-dialer-0.3.3
It also incorporates the patch related to the new ifconfig output.
Comment 8 Vladimir 2013-01-14 01:59:26 UTC
Created attachment 335558 [details, diff]
chestnut-dialer-0.3.3-ifconfig.patch

Since the ifconfig output changed from this one

ppp0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00
      inet addr:127.0.0.2  P-t-P:127.0.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
      UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
      RX packets:12515094 errors:0 dropped:0 overruns:0 frame:0
      TX packets:9951001 errors:0 dropped:12 overruns:0 carrier:0
      collisions:0 txqueuelen:0 
      RX bytes:17418423778 (16.2 GiB)  TX bytes:1109470296 (1.0 GiB)

to this one

ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 197.0.0.2  netmask 255.255.255.255  destination 127.0.0.2
        ppp  txqueuelen 3  (Point-to-Point Protocol)
        RX packets 992  bytes 261382 (255.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 881  bytes 57529 (56.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

chestnut-dialer stopped showing the connection status at all. So I made this patch to fix this issue.
Comment 9 Vladimir 2013-05-02 13:49:51 UTC
Created attachment 347134 [details]
chestnut-dialer-0.3.3-r2.ebuild

A new ebuild which utilizes the chestnut-dialer-0.3.3-disconnections.patch file
Comment 10 Vladimir 2013-05-02 13:55:43 UTC
Created attachment 347136 [details, diff]
chestnut-dialer-0.3.3-disconnections.patch

A patch that fixes several problems at a time:

1) pppd could not find the temporary chat file, because it was deleted after the first connect; so the subsequent reconnects were not possible;

2) if the interface was down, but pppd was still running, chestnut-dialer did not cause the reconnect (there simply had been no check of the interface state);

3) the GTK interface created the status monitoring timers not deleting the previously created ones, and therefore all the created timers asked for the connection state at their own times, thus causing a very hight CPU load.