Re: [DNG] Better late than never
Hi Alessandro, El 19/09/18 a las 21:36, Alessandro Selli escribió: On 19/09/18 at 20:34, aitor_czr wrote: Hi, El 19/09/18 a las 20:08, J. Fahrner escribió: Am 2018-09-19 14:18, schrieb aitor_czr: From my point of view a suspend/resume should automatically connect to a known network when it wakes up, just as a reboot does. Antony. This will be easy to do; automatically connect to an available installed wifi after suspend/reboot. The only thing i'd not like to do is to scan the active wifis at every x seconds throughout all the user's session. Reconnect to the last connected wifi would be perfect! No new scanning needed. Jochen Try to connect to a concrete wifi without the conviction about its existence? Mmm..., sorry but it makes little sense... There's nothing bad in failing. Clients do retry their last good TCP connections when they wake up, only to find out the routing and local IP address are no longer valid or available because the laptop moved physically away from the old network. Like they are let fail their connections gracefully, so reconnecting to the last known good WiFi AP can be allowed to fail: if it's lucky, it's going to reconnect to the last AP really fast, otherwise it's going to have to rescan the waves in search of some known AP. Unless there are security concerns in doing this, I would like my laptop to behave like this. Alessandro I have an idea: to save the list of all the neighbors for each saved wifi. So, the scanner would be activated only in case of some detection because of the chance of finding. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
On 19/09/18 at 20:34, aitor_czr wrote: > Hi, > > El 19/09/18 a las 20:08, J. Fahrner escribió: >> >> Am 2018-09-19 14:18, schrieb aitor_czr: >> >>> From my point of view a suspend/resume should automatically connect >>> to a known network when it wakes up, just as a reboot does. Antony. >>> >>> >>> This will be easy to do; automatically connect to an available >>> installed wifi after suspend/reboot. >>> The only thing i'd not like to do is to scan the active wifis at >>> every x seconds throughout all the >>> user's session. >> >> Reconnect to the last connected wifi would be perfect! No new >> scanning needed. >> >> Jochen >> > > Try to connect to a concrete wifi without the conviction about its > existence? Mmm..., sorry but it makes little sense... There's nothing bad in failing. Clients do retry their last good TCP connections when they wake up, only to find out the routing and local IP address are no longer valid or available because the laptop moved physically away from the old network. Like they are let fail their connections gracefully, so reconnecting to the last known good WiFi AP can be allowed to fail: if it's lucky, it's going to reconnect to the last AP really fast, otherwise it's going to have to rescan the waves in search of some known AP. Unless there are security concerns in doing this, I would like my laptop to behave like this. Alessandro -- Alessandro Selli Tel. 3701355486 VOIP SIP: dhatarat...@ekiga.net Chiave firma e cifratura PGP/GPG signing and encoding key: BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-19 20:34, schrieb aitor_czr: > Try to connect to a concrete wifi without the conviction about its existence? > Mmm..., sorry but it makes little sense... When it's non existent, scanning is ok. But if it is, scanning is obsolete.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi, El 19/09/18 a las 20:08, J. Fahrner escribió: Am 2018-09-19 14:18, schrieb aitor_czr: From my point of view a suspend/resume should automatically connect to a known network when it wakes up, just as a reboot does. Antony. This will be easy to do; automatically connect to an available installed wifi after suspend/reboot. The only thing i'd not like to do is to scan the active wifis at every x seconds throughout all the user's session. Reconnect to the last connected wifi would be perfect! No new scanning needed. Jochen Try to connect to a concrete wifi without the conviction about its existence? Mmm..., sorry but it makes little sense... Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-19 14:18, schrieb aitor_czr: > From my point of view a suspend/resume should automatically connect to a > known network when it wakes up, just as a reboot does. Antony. > This will be easy to do; automatically connect to an available installed wifi > after suspend/reboot. > The only thing i'd not like to do is to scan the active wifis at every x > seconds throughout all the > user's session. Reconnect to the last connected wifi would be perfect! No new scanning needed. Jochen___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
El 19/09/18 a las 14:18, aitor_czr escribió: Hi, El 19/09/18 a las 14:07, Antony Stone escribió: On Wednesday 19 September 2018 at 13:01:44, m712 wrote: I'd prefer for it to reconnect, but only to known networks, of course. That way I can read news in the morning at home, close the lid, go to work and start working without fiddling with the network settings. From my point of view a suspend/resume should automatically connect to a known network when it wakes up, just as a reboot does. Antony. This will be easy to do; automatically connect to an available installed wifi after suspend/reboot. The only thing i'd not like to do is to scan the active wifis at every x seconds throughout all the user's session. Aitor. Or maybe leave it as the user's choice? Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
You can just scan when the GUI's open. Maybe make a timeout after which netaid stops searching for a known network after boot/resume (user-configurable)? This way we have error-tolerance too. On September 19, 2018 3:18:01 PM GMT+03:00, aitor_czr wrote: >Hi, > >El 19/09/18 a las 14:07, Antony Stone escribió: >> On Wednesday 19 September 2018 at 13:01:44, m712 wrote: >> >>> I'd prefer for it to reconnect, but only to known networks, of >course. That >>> way I can read news in the morning at home, close the lid, go to >work and >>> start working without fiddling with the network settings. >> From my point of view a suspend/resume should automatically connect >to a known >> network when it wakes up, just as a reboot does. >> >> >> Antony. >> > >This will be easy to do; automatically connect to an available >installed >wifi after suspend/reboot. >The only thing i'd not like to do is to scan the active wifis at every >x >seconds throughout all the >user's session. > >Aitor. m712 -- https://nextchan.org -- https://gitgud.io/blazechan/blazechan I am awake between 3AM-8PM UTC, HMU if the site's broken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi, El 19/09/18 a las 14:07, Antony Stone escribió: On Wednesday 19 September 2018 at 13:01:44, m712 wrote: I'd prefer for it to reconnect, but only to known networks, of course. That way I can read news in the morning at home, close the lid, go to work and start working without fiddling with the network settings. From my point of view a suspend/resume should automatically connect to a known network when it wakes up, just as a reboot does. Antony. This will be easy to do; automatically connect to an available installed wifi after suspend/reboot. The only thing i'd not like to do is to scan the active wifis at every x seconds throughout all the user's session. Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-19 14:07, schrieb Antony Stone: From my point of view a suspend/resume should automatically connect to a known network when it wakes up, just as a reboot does. Exactyly my needs also. This is why I prefer wicd. But wicd has one disadvantage: it takes a long time to reconnect. Looks like it first scans all available networks, and then decides to which it should connect. network-manager is faster, it reconnects immediately to the last connected network. But network-manager has other disadvantages: it uses more resources and does not reconnect at work, where we have a guest network with a public hotspot and a landing page. wicd reconnects fine there, but network-manager needs a manual disconnect and connect. Jochen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
On Wednesday 19 September 2018 at 13:01:44, m712 wrote: > I'd prefer for it to reconnect, but only to known networks, of course. That > way I can read news in the morning at home, close the lid, go to work and > start working without fiddling with the network settings. From my point of view a suspend/resume should automatically connect to a known network when it wakes up, just as a reboot does. Antony. > On September 19, 2018 2:19:05 PM GMT+03:00, Hendrik Boom wrote: > >On Wed, Sep 19, 2018 at 08:13:24AM +0200, aitor_czr wrote: > >> Hi, > >> > >> El 19/09/18 a las 07:55, J. Fahrner escribió: > >> > Am 2018-09-18 11:37, schrieb aitor_czr: > >> > > Thanks for your interest on simple-netaid :) > >> > > >> > Does simple-netaid not automatically reconnect after > > > >suspend/resume? > > > >> > Jochen > >> > >> It doesn't. The automatically connect option still is not > > > >implemented. I > > > >> wanted to do the backend of simple-netaid as lightweith as possible. > >> Close all the apps, web navigator, etc... and keep running only > >> simple-netaid. The CPU requeriment is very low. > > > >Do we even want to automatically reconnect after a suspend/resume? We > >might be resuming in a vastly different environment from where we > >suspended. > > > >-- hendrik -- "this restriction will not apply in the event of the occurrence (certified by the United States Centers for Disease Control or successor body) of a widespread viral infection transmitted via bites or contact with bodily fluids that causes human corpses to reanimate and seek to consume living human flesh, blood, brain or nerve tissue and is likely to result in the fall of organized civilization." - https://aws.amazon.com/service-terms/ paragraph 57.10 Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-19 13:19, schrieb Hendrik Boom: Do we even want to automatically reconnect after a suspend/resume? We might be resuming in a vastly different environment from where we suspended. I use my notebooks mainly at home. When I finished reading mails and news I close the lid until I need it again. When I open the lid, internet should be back again. The only occasion when I do a reboot is after kernel updates. Jochen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
On September 18, 2018 1:34:39 PM GMT+03:00, Edward Bartolo wrote: >Quote: > >The aim of MY simple-netaid IS NOT to enrich my CV. I did it for the >project. It seems a selfish self-centred motivation is more >appreciated here. Edward, this behaviour is really uncalled for. If you have a problem with a certain person please take your issue to them, please do not post passive-aggresively here. m712 -- https://nextchan.org -- https://gitgud.io/blazechan/blazechan I am awake between 3AM-8PM UTC, HMU if the site's broken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
I'd prefer for it to reconnect, but only to known networks, of course. That way I can read news in the morning at home, close the lid, go to work and start working without fiddling with the network settings. On September 19, 2018 2:19:05 PM GMT+03:00, Hendrik Boom wrote: >On Wed, Sep 19, 2018 at 08:13:24AM +0200, aitor_czr wrote: >> Hi, >> >> El 19/09/18 a las 07:55, J. Fahrner escribió: >> > >> > Am 2018-09-18 11:37, schrieb aitor_czr: >> > >> > > Thanks for your interest on simple-netaid :) >> > > >> > Does simple-netaid not automatically reconnect after >suspend/resume? >> > >> > Jochen >> > >> >> It doesn't. The automatically connect option still is not >implemented. I >> wanted to do the backend of simple-netaid as lightweith as possible. >> Close all the apps, web navigator, etc... and keep running only >> simple-netaid. The CPU requeriment is very low. > >Do we even want to automatically reconnect after a suspend/resume? We >might be resuming in a vastly different environment from where we >suspended. > >-- hendrik >___ >Dng mailing list >Dng@lists.dyne.org >https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng m712 -- https://nextchan.org -- https://gitgud.io/blazechan/blazechan I am awake between 3AM-8PM UTC, HMU if the site's broken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
On Wed, Sep 19, 2018 at 08:13:24AM +0200, aitor_czr wrote: > Hi, > > El 19/09/18 a las 07:55, J. Fahrner escribió: > > > > Am 2018-09-18 11:37, schrieb aitor_czr: > > > > > Thanks for your interest on simple-netaid :) > > > > > Does simple-netaid not automatically reconnect after suspend/resume? > > > > Jochen > > > > It doesn't. The automatically connect option still is not implemented. I > wanted to do the backend of simple-netaid as lightweith as possible. > Close all the apps, web navigator, etc... and keep running only > simple-netaid. The CPU requeriment is very low. Do we even want to automatically reconnect after a suspend/resume? We might be resuming in a vastly different environment from where we suspended. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi, El 19/09/18 a las 07:55, J. Fahrner escribió: Am 2018-09-18 11:37, schrieb aitor_czr: Thanks for your interest on simple-netaid :) Does simple-netaid not automatically reconnect after suspend/resume? Jochen It doesn't. The automatically connect option still is not implemented. I wanted to do the backend of simple-netaid as lightweith as possible. Close all the apps, web navigator, etc... and keep running only simple-netaid. The CPU requeriment is very low. Have a look at the lines nº90 - nº124 of the window_main_worker.cpp: https://git.devuan.org/aitor_czr/simple-netaid-gtk/blob/master/src/window_main_worker.cpp This funcion only says you if you are connected or disconnected. Only after the detecction of a change in the status of the network connection, the code of the nº255 - nº582 of netstat.c: https://git.devuan.org/aitor_czr/simple-netaid-gtk/blob/master/backend_src/netstat.c will be run, giving in detail the information about the network connection, including if the wire is plugged/unplugged. Later i'll explain in detail how the backend works, i have no time now (time to work). Have a nice day :) Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-18 11:37, schrieb aitor_czr: > Thanks for your interest on simple-netaid :) Does simple-netaid not automatically reconnect after suspend/resume? Jochen___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-18 11:23, schrieb aitor_czr: > Thanks for your interest on simple-netaid :) I thank you! I installed simple-netaid in parallel with wicd. Now I'm wondering how simple-netaid finds the active connection. It reports "connected to vmnet8". That's some virtual interface of Vmware Player. Jochen___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Better late than never
Quote: "The only existent README file for now was written by Edward Bartolo, and it-s focused to the previous version of simple-netaid, written in C and freepascal. So, it's a bit obsolete. However, the new version of simple-netaid also uses ifupdown, but there is no CLI version for now (this is a work in progress)." -- My latest version of simple-netaid NO longer uses ifupdown. The working mechanism is more low level. Now, open unencrypted connections are supported although there is still an issue that sometimes prevents auto-connect from working. A better approach would be to use a list of preferred wifi-hotspots with ordered priority and for users to choose the if and when to connect. If I were to implement the latter in the front-end GUI, it would not take very long for me. The aim of MY simple-netaid IS NOT to enrich my CV. I did it for the project. It seems a selfish self-centred motivation is more appreciated here. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi again, El 18/09/18 a las 11:23, aitor_czr escribió: Hi Jochen, El 18/09/18 a las 07:56, J. Fahrner escribió: Am 2018-09-18 01:11, schrieb aitor_czr: I uploaded the new packeges after fixing most of the bugs: http://gnuinos.org/simple-netaid/ I also added the .desktop menu entry. Is there some README about simple-netaid? The only existent README file for now was written by Edward Bartolo, and it-s focused to the previous version of simple-netaid, written in C and freepascal. So, it's a bit obsolete. However, the new version of simple-netaid also uses ifupdown, but there is no CLI version for now (this is a work in progress). What is it? Is it a replacement for wicd? Indeed, it's an alternative for wicd without dbus, written in C/C++ and Gtkmm-2.4. Can they live together, or must wicd removed? What's the difference between the two? I've been testing both working together, and i've found the following issue: the behaviour of wicd can be affected by the use of simple-netaid. Not only because of possible failed attempts connecting or disconnecting with wicd, but also for possible wrong information about the status of the network connection. In contrast, i didn' find this behaviour in the other way around; that is, simple-netaid is not affected by the use of wicd. So, it would be interenting to use both together in order to compare them. BTW, i fixed another bug in the wired connections, and built the packges for both architectures: i 386 and amd64. The packages are operative now, but there are still some issues pending to be fixed: a segmentation fault closing the application, the code for the hidden active wifis, a socket sharing information between the window_main_worker thread and the backend, and a lot of warnings during the compilation. Jochen Thanks for your interest on simple-netaid :) Aitor. Another clarification: the backend of simple-netaid has been tested with linux-3.16.x and linux-4.9.x Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi Jochen, El 18/09/18 a las 07:56, J. Fahrner escribió: Am 2018-09-18 01:11, schrieb aitor_czr: I uploaded the new packeges after fixing most of the bugs: http://gnuinos.org/simple-netaid/ I also added the .desktop menu entry. Is there some README about simple-netaid? The only existent README file for now was written by Edward Bartolo, and it-s focused to the previous version of simple-netaid, written in C and freepascal. So, it's a bit obsolete. However, the new version of simple-netaid also uses ifupdown, but there is no CLI version for now (this is a work in progress). What is it? Is it a replacement for wicd? Indeed, it's an alternative for wicd without dbus, written in C/C++ and Gtkmm-2.4. Can they live together, or must wicd removed? What's the difference between the two? I've been testing both working together, and i've found the following issue: the behaviour of wicd can be affected by the use of simple-netaid. Not only because of possible failed attempts connecting or disconnecting with wicd, but also for possible wrong information about the status of the network connection. In contrast, i didn' find this behaviour in the other way around; that is, simple-netaid is not affected by the use of wicd. So, it would be interenting to use both together in order to compare them. BTW, i fixed another bug in the wired connections, and built the packges for both architectures: i 386 and amd64. The packages are operative now, but there are still some issues pending to be fixed: a segmentation fault closing the application, the code for the hidden active wifis, a socket sharing information between the window_main_worker thread and the backend, and a lot of warnings during the compilation. Jochen Thanks for your interest on simple-netaid :) Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Am 2018-09-18 01:11, schrieb aitor_czr: > I uploaded the new packeges after fixing most of the bugs: > > http://gnuinos.org/simple-netaid/ > > I also added the .desktop menu entry. Is there some README about simple-netaid? What is it? Is it a replacement for wicd? Can they live together, or must wicd removed? What's the difference between the two? Jochen___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi, El 17/09/18 a las 15:17, aitor_czr escribió: Hi, El 17/09/18 a las 11:48, aitor_czr escribió: Hi, El 17/09/18 a las 08:22, aitor_czr escribió: I've been testing the packages, and the packaging need a review. There are some bugs non-existent building the sources. Maybe the static library... I'll try to fix it today. Cheers,  Aitor. You can build the sources: https://git.devuan.org/aitor_czr/simple-netaid-gtk running the script: $ ./build src Then, run the application: $ ./simple-netaid-gtk If you want to build the packages, you'll need to checkout the gbp-master branch and also the pristine tarball in the parent directory: $ git checkout gbp-master $ pristine-tar checkout ../simple-netaid-gtk_1.0.0.orig.tar.gz After that, use git-buildpackage: $ git-buildpackage -j4 -tc --git-export-dir="../build-area" --git-pristine-tar --git-tag --git-ignore-branch |If you change the sources, work in the master branch and merge it onto the gbp-master branch (if you don't want to use quilt patches). After that, you'll also need to update the delta binary in the pristine-tar branch. Cheers,  Aitor.| Lines nº43, nº550 and nº632 of the "window_main.cpp" needed to be changed. In previous versions of simple-netaid, the spinner ran "/usr/lib/simple-netaid/bin/backend 8" being this backend the backend developed by Edward Bartolo. Now it runs the new backend. So, the spinner didn't work after clicking on the refresh button or on the systray-icon. I pushed a new commit. Aitor. I uploaded the new packeges after fixing most of the bugs: http://gnuinos.org/simple-netaid/ I also added the .desktop menu entry. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi, El 17/09/18 a las 11:48, aitor_czr escribió: Hi, El 17/09/18 a las 08:22, aitor_czr escribió: I've been testing the packages, and the packaging need a review. There are some bugs non-existent building the sources. Maybe the static library... I'll try to fix it today. Cheers,  Aitor. You can build the sources: https://git.devuan.org/aitor_czr/simple-netaid-gtk running the script: $ ./build src Then, run the application: $ ./simple-netaid-gtk If you want to build the packages, you'll need to checkout the gbp-master branch and also the pristine tarball in the parent directory: $ git checkout gbp-master $ pristine-tar checkout ../simple-netaid-gtk_1.0.0.orig.tar.gz After that, use git-buildpackage: $ git-buildpackage -j4 -tc --git-export-dir="../build-area" --git-pristine-tar --git-tag --git-ignore-branch |If you change the sources, work in the master branch and merge it onto the gbp-master branch (if you don't want to use quilt patches). After that, you'll also need to update the delta binary in the pristine-tar branch. Cheers,  Aitor.| Lines nº43, nº550 and nº632 of the "window_main.cpp" needed to be changed. In previous versions of simple-netaid, the spinner ran "/usr/lib/simple-netaid/bin/backend 8" being this backend the backend developed by Edward Bartolo. Now it runs the new backend. So, the spinner didn't work after clicking on the refresh button or on the systray-icon. I pushed a new commit. Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
Hi, El 17/09/18 a las 08:22, aitor_czr escribió: I've been testing the packages, and the packaging need a review. There are some bugs non-existent building the sources. Maybe the static library... I'll try to fix it today. Cheers, Aitor. You can build the sources: https://git.devuan.org/aitor_czr/simple-netaid-gtk running the script: $ ./build src Then, run the application: $ ./simple-netaid-gtk If you want to build the packages, you'll need to checkout the gbp-master branch and also the pristine tarball in the parent directory: $ git checkout gbp-master $ pristine-tar checkout ../simple-netaid-gtk_1.0.0.orig.tar.gz After that, use git-buildpackage: $ git-buildpackage -j4 -tc --git-export-dir="../build-area" --git-pristine-tar --git-tag --git-ignore-branch |If you change the sources, work in the master branch and merge it onto the gbp-master branch (if you don't want to use quilt patches). After that, you'll also need to update the delta binary in the pristine-tar branch. Cheers, Aitor. | ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
El 16/09/18 a las 23:49, aitor_czr escribió: You must type `chmod +x libnetaid.install`, of course. Here you are the packages of simple-netaid for amd64: http://gnuinos.org/simple-netaid/ This week i'll upload the packages for i386 and i'll explain how to build them for other architectures. Tomorrow i'll push the latest commits to gitlab. Hope you like it :) Aitor. I've been testing the packages, and the packaging need a review. There are some bugs non-existent building the sources. Maybe the static library... I'll try to fix it today. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Better late than never
El 16/09/18 a las 23:49, aitor_czr escribió: You must type `chmod +x libnetaid.install`, of course. Here you are the packages of simple-netaid for amd64: http://gnuinos.org/simple-netaid/ This week i'll upload the packages for i386 and i'll explain how to build them for other architectures. Tomorrow i'll push the latest commits to gitlab. Hope you like it :) Aitor. I've been testing the packages, and the packaging needs a review, there are a few bugs non-existent building the sources. Maybe the static library... Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Better late than never
Hi again,
El 15/09/18 a las 21:26, aitor_czr escribió:
I had an issue packaging simple-netaid. The target of the shared
library "libnetaid.so" was being obj-x86-64-linux-gnu, and trying to
use the variable $(DEB_HOST_MULTIARCH)
in "libnetaid.install", this variable was not replaced by its value:
`x86-64-linux-gnu`. I've just found the following solution for that
doing the "libnetaid.install" executable:
#! /usr/bin/dh-exec
obj-*-linux-gnu/backend_src/libnetaid.so usr/lib/${DEB_HOST_MULTIARCH}
Cheers,
 Aitor.
You must type `chmod +x libnetaid.install`, of course.
Here you are the packages of simple-netaid for amd64:
http://gnuinos.org/simple-netaid/
This week i'll upload the packages for i386 and i'll explain how to
build them for other architectures.
Tomorrow i'll push the latest commits to gitlab.
Hope you like it :)
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
