Re: What is UpdateXorgRecipe? And how do I update Xorg-Server?
Robert Alexander <[email protected]> Sun, 13 Jan 2019 20:27:56 +0100
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <CAFie_ABw=k20KXaZiXGuy0DdP4oC38c=OSpbP+HL6Y3sd75EEQ@mail.gmail.com> |
--===============2139106131355156362== Content-Type: multipart/alternative; boundary="0000000000009aa9a3057f5bec95" --0000000000009aa9a3057f5bec95 Content-Type: text/plain; charset="UTF-8" Hello Philip, I see you are not to be discouraged easily. :-) I can not answer most of your questions as I don't easily remember, and am on slackware right now. Perhaps lucas or hisham can add a meson package, and update pip and python: http://recipes.gobolinux.org/r/?list=Python URLs for these three as update would be: https://www.python.org/ftp/python/3.7.2/Python-3.7.2.tgz https://files.pythonhosted.org/packages/45/ae/8a0ad77defb7cc903f09e551d88b443304a9bd6e6f124e75c0fbbf6de8f7/pip-18.1.tar.gz https://files.pythonhosted.org/packages/b6/22/55d0b08695abf2f425e7b4130b37f6202ca5e37c93dca7512f2ee2b8f4f4/meson-0.49.0.tar.gz I am tracking programs like these these via some ruby scripts. :-) On GoboLinux I also ended up compiling things mostly via these ruby scripts. It's however had quite messy in general and even after many years just a hobby project. Although I can not speak for anyone else, this may be a partial reason for when GoboLinux may be not as active as, say, in 2006 or so. Personally I had more success building something without depending on the official tools, mostly because I have no idea how things work and just keep on brute-forcing my way around. ;-) (I do, however had, try to make notes and register what programs may install.) As for meson, after you installed it, it should be at e. g. /Programs/Python/Current/bin/meson - at the least I have it there on my slackware system (it's slackware but I compile almost everything in a GoboLinux-like manner). GoboLinux is somewhat active at: https://github.com/gobolinux There are recipes added/updated, and some changes to part of the software system every now and then. I think lucas said that some time in 2019 there will be a new GoboLinux release. There is quite a bit of documentation at: https://github.com/gobolinux/Documentation/wiki Joel wrote some really nice parts here. If lucas has some time perhaps he can give some more advice; I do not know who maintains the server at http://recipes.gobolinux.org/r/ but it would be nice if that one could be made to work again. On a side note, if you do not mind, do you happen to have some experience in any of the "scripting" family of programming languages? E. g. ruby python lua php perl ? I personally like ruby a lot; hisham is a heavy lua user (and I think both lucas and hisham know/use python, at the least I remember some python code in the gobolinux software system). I am asking specifically because you could always try a "brute force" approach too, that is, just compile into /Programs/ for the time being and not worry too much about the recipes. In the long run I assume the recipes will be improved anyway; lucas updates them when he prepares a new gobolinux release. I think even if something is just installed under /Programs/, the gobolinux scripts can be used to automatically symlink etc... On my todo list there is a "make my ruby scripts work on gobolinux as-is, by default" - but I am also very lazy, so I tend to wait for new releases before trying things again. :D (I used to have quite a lot of problems whenever something in the linux ecosystem changed. On the other hand, I am quite close to being able to compile + run a full KDE5 plasma system; e. g. I am using konsole here compiled from source, okular works fine too and most other programs too, only starting kde5 plasma fails with some message that some shell-components could not be found; then I wait until a new release, and usually things work a LOT better the next time. Once I have things work here on slackware, it should be quite easy to have them work on gobolinux too. Biggest problem is my lack of knowledge how things connect with one another, and some not-so-well behaving parts, such as docbook, dconf and so forth - ironically enough usually programs that do not come with GNU configure, cmake or meson. Meson is fairly simple actually, one needs only python3, ninja and that's it - usually also compile via a build directory. Lucas asked whether someone can add meson support to the gobolinux scripts but I am terrible at shell scripts.) On Sat, Jan 12, 2019 at 6:33 AM Philip White <[email protected]> wrote: > This is a pretty helpful response, but I just sat down to try working on > this because I had some time and I'm running into issues making a recipe > for Meson. > > First question: What is the right approach to "package management" in > gobolinux? > > Intuitively, I'm thinking that everything should have a recipe, and if > something is broken, the recipe should be fixed, or if something doesn't > have a recipe but you want to install it, you should make a Recipe. Of > course, the filesystem structure is such that you don't always need to have > a recipe for something, but it would seem that having a recipe for > everything would be better if someone is willing to put in the work. > Specifically, if you are recommending that I install meson, why isn't there > a recipe for it? Or, why do I have to fix Xorg myself? I'm not really > complaining, I just would have expected it to have been done, so I'm > thinking I could be misunderstanding gobolinux. > > Second question: How do I get this Recipe for Meson to work? > > # Recipe (MakeRecipe) for Meson by Philip White < > [email protected]>, on Thu Jan 3 21:00:28 EST 2019 > # Recipe for version 0.49.0 by Philip White <[email protected]>, > on Thu Jan 3 21:00:28 EST 2019 > compile_version=016.02 > url="https://github.com/mesonbuild/meson/archive/0.49.0.tar.gz" > file="meson-0.49.0.tar.gz" > file_size=1911251 > file_md5=a615fdb0d5920aa78175cda18a6f838f > dir='meson-0.49.0' > recipe_type=python > python_major=3 > > The Recipe builds just fine, but `meson` is not a command on my path. > > I thought perhaps I should try to run `pip3 install meson` to do things > the easy way, but apparently Pip is out of date (why is that); that > hearkens back to the first question though. > > On Sat, Jan 5, 2019 at 8:21 PM Robert Alexander <[email protected]> > wrote: > >> > When I ran `startx` on the next boot, the server shutdown >> > because the VESA driver's ABI was at a different version than Xorg's. >> > So I tried update that driver but I ran into some other issues. I >> > could describe those issues, but I'm feeling like that isn't the >> > root issue. >> >> I am not currently running GoboLinux but I remember ABI-related problems >> and xorg-server not starting. >> >> What I usually do is to make sure that LLVM is up to date; and cmake; >> then I compile meson ( >> http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/meson.html >> ) (even though the URL includes systemd, meson works perfectly well >> without systemd of course; I only have this "bookmarked" as link, >> LFS/BLFS instructions can be super-helpful). After meson I tend to >> compile the xorg-libs (libx11, libice, libsm, libxcb - all available >> on the same URL where the xorg-server is), then I compile the >> xorg-server. Here you have to be a bit careful in that I have had >> problems in the past; e. g. wayland related parts aren't that good; >> I tend to do things such as --disable-xwayland-eglstream and similar >> to xorg-server. This serves me better than enabling these snippets. >> >> By the way, from my own experience it is quite hard to break a >> GoboLinux system because you should always have the older versions >> in the respective directory under /Programs/ so you can just >> re-symlink that. :) >> >> To your problem like this: >> >> >> Requested 'xproto >= 7.0.31' but version of Xproto is 7.0.29 >> Requested 'randrproto >= 1.6.0' but version of RandrProto is 1.5.0 >> Requested 'presentproto >= 1.1' but version of PresentProto is 1.0 >> >> >> I think if you install >> >> https://www.x.org/releases/individual/proto/xorgproto-2018.4.tar.bz2 >> >> then this should be fine. >> >> That has all the .pc files as far as I can see for the protos: >> >> scrnsaverproto.pc, trapproto.pc, videoproto.pc and so forth. >> >> I also recommend to you to keep information in a text file - this >> may help you at a later time a LOT. I started noting down how >> to resolve some problems within the yaml-files that I use to >> compile/install programs from source; a bit like the LFS/BLFS >> project but more tuned towards the problems I encounter. >> >> I also used to autogenerate something similar to LFS/BLFS - will >> try to see to do so and then make this available somewhere again. >> >> PS: The mailing interface confuses me too a bit. I see your emails >> but I don't see the other email that came first in 2019 altogether, >> so I could not hit on "reply" (I sent a mail to the email listed though). >> >> I find mailing lists pretty confusing altogether in general. >> >> On Sat, Jan 5, 2019 at 6:52 PM Philip White <[email protected]> >> wrote: >> >>> I realized that digest mode is not what I want for a mailing list, since >>> I cannot reply to emails individually. >>> >>> Anyway, my attempt to build i3 has been sidetracked because I ran >>> >>> InstallPackage Xorg-Server >>> >>> which broke X. When I ran `startx` on the next boot, the server shutdown >>> because the VESA driver's ABI was at a different version than Xorg's. So I >>> tried update that driver but I ran into some other issues. I could describe >>> those issues, but I'm feeling like that isn't the root issue. >>> >>> I would expect this is an issue other people have run into, since nearly >>> everyone uses Xorg, and people generally keep their systems up to the >>> latest version. >>> >>> While looking for a solution, I noticed the UpdateXorgRecipe script. I >>> ran it, and it made a bunch of local recipes, but as far as I can tell, it >>> didn't actually compile anything. Thus, I tried to run `Compile >>> Xorg-Server` to compile the newly generated recipes. I got the dependency >>> issues: >>> >>> Requested 'xproto >= 7.0.31' but version of Xproto is 7.0.29 >>> Requested 'randrproto >= 1.6.0' but version of RandrProto is 1.5.0 >>> Requested 'presentproto >= 1.1' but version of PresentProto is 1.0 >>> >>> Has anybody encountered this error before? Also, is there any >>> documentation for what UpdateXorgRecipe does? >>> >>> Last question, how do I search these mailing list archives? The link on >>> the website points to >>> http://search.gmane.org/search.php?group=gmane.linux.distributions.gobo.general, >>> which does not work. >>> >>> Thanks, >>> Philip >>> _______________________________________________ >>> gobolinux-users mailing list >>> [email protected] >>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >>> >> _______________________________________________ >> gobolinux-users mailing list >> [email protected] >> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >> > _______________________________________________ > gobolinux-users mailing list > [email protected] > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > --0000000000009aa9a3057f5bec95 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">Hello Philip,<br><br>I see you are not to= be discouraged easily. :-)<br><br>I can not answer most of your questions = as I don't easily remember,<br>and am on slackware right now.<br><br>Pe= rhaps lucas or hisham can add a meson package, and update pip<br>and python= :<br><br>=C2=A0 <a href=3D"http://recipes.gobolinux.org/r/?list=3DPython">h= ttp://recipes.gobolinux.org/r/?list=3DPython</a><br><br>URLs for these thre= e as update would be:<br><br>=C2=A0 <a href=3D"https://www.python.org/ftp/p= ython/3.7.2/Python-3.7.2.tgz">https://www.python.org/ftp/python/3.7.2/Pytho= n-3.7.2.tgz</a><br>=C2=A0 <a href=3D"https://files.pythonhosted.org/package= s/45/ae/8a0ad77defb7cc903f09e551d88b443304a9bd6e6f124e75c0fbbf6de8f7/pip-18= .1.tar.gz">https://files.pythonhosted.org/packages/45/ae/8a0ad77defb7cc903f= 09e551d88b443304a9bd6e6f124e75c0fbbf6de8f7/pip-18.1.tar.gz</a><br>=C2=A0 <a= href=3D"https://files.pythonhosted.org/packages/b6/22/55d0b08695abf2f425e7= b4130b37f6202ca5e37c93dca7512f2ee2b8f4f4/meson-0.49.0.tar.gz">https://files= .pythonhosted.org/packages/b6/22/55d0b08695abf2f425e7b4130b37f6202ca5e37c93= dca7512f2ee2b8f4f4/meson-0.49.0.tar.gz</a><br><br>I am tracking programs li= ke these these via some ruby scripts. :-)<br><br>On GoboLinux I also ended = up compiling things mostly via these<br>ruby scripts. It's however had = quite messy in general and even<br>after many years just a hobby project. A= lthough I can not speak<br>for anyone else, this may be a partial reason fo= r when GoboLinux<br>may be not as active as, say, in 2006 or so. Personally= I had<br>more success building something without depending on the official= <br>tools, mostly because I have no idea how things work and just<br>keep o= n brute-forcing my way around. ;-) (I do, however had,<br>try to make notes= and register what programs may install.)<br><br>As for meson, after you in= stalled it, it should be at e. g.<br>/Programs/Python/Current/bin/meson - a= t the least I have it<br>there on my slackware system (it's slackware b= ut I compile<br>almost everything in a GoboLinux-like manner).<br><br>GoboL= inux is somewhat active at:<br><br><a href=3D"https://github.com/gobolinux"= >https://github.com/gobolinux</a><br><br>There are recipes added/updated, a= nd some changes to part of<br>the software system every now and then.<br><b= r>I think lucas said that some time in 2019 there will be a new<br>GoboLinu= x release.<br><br>There is quite a bit of documentation at:<br><br>=C2=A0 <= a href=3D"https://github.com/gobolinux/Documentation/wiki">https://github.c= om/gobolinux/Documentation/wiki</a><br><br>Joel wrote some really nice part= s here.<br><br>If lucas has some time perhaps he can give some more advice;= <br>I do not know who maintains the server at <br><a href=3D"http://recipes= .gobolinux.org/r/">http://recipes.gobolinux.org/r/</a> but it would be nice= if that<br>one could be made to work again.</div><div dir=3D"ltr"><br></di= v><div>On a side note, if you do not mind, do you happen to have some</div>= <div>experience in any of the "scripting" family of programming l= anguages?</div><div><br></div><div>E. g. ruby python lua php perl ?</div><d= iv><br></div><div>I personally like ruby a lot; hisham is a heavy lua user<= /div><div>(and I think both lucas and hisham know/use python,</div><div>at = the least I remember some python code in the gobolinux</div><div>software s= ystem).</div><div><br></div><div>I am asking specifically because you could= always try a</div><div>"brute force" approach too, that is, just= compile into /Programs/</div><div>for the time being and not worry too muc= h about the recipes.</div><div>In the long run I assume the recipes will be= improved anyway;</div><div>lucas updates them when he prepares a new gobol= inux release.</div><div><br></div><div>I think even if something is just in= stalled under /Programs/, the</div><div>gobolinux scripts can be used to au= tomatically symlink etc...</div><div><br></div><div>On my todo list there i= s a "make my ruby scripts work on gobolinux</div><div>as-is, by defaul= t" - but I am also very lazy, so I tend to wait for new</div><div>rele= ases before trying things again. :D <br></div><div><br></div><div>(I used t= o have quite a lot of problems whenever something in the</div><div>linux ec= osystem changed. On the other hand, I am quite close to</div><div>being abl= e to compile + run a full KDE5 plasma system; e. g. I am</div><div>using ko= nsole here compiled from source, okular works fine too</div><div>and most o= ther programs too, only starting kde5 plasma fails with</div><div>some mess= age that some shell-components could not be found;</div><div>then I wait un= til a new release, and usually things work a LOT better</div><div>the next = time. Once I have things work here on slackware, it should</div><div>be qui= te easy to have them work on gobolinux too. Biggest problem</div><div>is my= lack of knowledge how things connect with one another, and</div><div>some = not-so-well behaving parts, such as docbook, dconf and</div><div>so forth -= ironically enough usually programs that do not come with</div><div>GNU con= figure, cmake or meson. Meson is fairly simple actually,</div><div>one need= s only python3, ninja and that's it - usually also compile</div><div>vi= a a build directory. Lucas asked whether someone can add meson</div><div>su= pport to the gobolinux scripts but I am terrible at shell scripts.)<br></di= v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Jan 12, 201= 9 at 6:33 AM Philip White <<a href=3D"mailto:[email protected]"= >[email protected]</a>> wrote:<br></div><blockquote class=3D"gm= ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,= 204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt= r"><div dir=3D"ltr"><div dir=3D"ltr"><div>This is a pretty helpful response= , but I just sat down to try working on this because I had some time and I&= #39;m running into issues making a recipe for Meson.</div><div><br></div><d= iv>First question: What is the right approach to "package management&q= uot; in gobolinux?</div><div><br></div><div>Intuitively, I'm thinking t= hat everything should have a recipe, and if something is broken, the recipe= should be fixed, or if something doesn't have a recipe but you want to= install it, you should make a Recipe. Of course, the filesystem structure = is such that you don't always need to have a recipe for something, but = it would seem that having a recipe for everything would be better if someon= e is willing to put in the work. Specifically, if you are recommending that= I install meson, why isn't there a recipe for it? Or, why do I have to= fix Xorg myself? I'm not really complaining, I just would have expecte= d it to have been done, so I'm thinking I could be misunderstanding gob= olinux.</div><div><br></div><div>Second question: How do I get this Recipe = for Meson to work?</div><div><br></div><div># Recipe (MakeRecipe) for Meson= by Philip White <<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>>, on Thu Jan 3 21:00:28 EST 2= 019<br># Recipe for version 0.49.0 by Philip White <<a href=3D"mailto:ph= [email protected]" target=3D"_blank">[email protected]</a>&= gt;, on Thu Jan 3 21:00:28 EST 2019<br>compile_version=3D016.02<br>url=3D&q= uot;<a href=3D"https://github.com/mesonbuild/meson/archive/0.49.0.tar.gz" t= arget=3D"_blank">https://github.com/mesonbuild/meson/archive/0.49.0.tar.gz<= /a>"<br>file=3D"meson-0.49.0.tar.gz"<br>file_size=3D1911251<= br>file_md5=3Da615fdb0d5920aa78175cda18a6f838f<br>dir=3D'meson-0.49.0&#= 39;<br>recipe_type=3Dpython<br>python_major=3D3<br></div><div></div><div><b= r></div><div>The Recipe builds just fine, but `meson` is not a command on m= y path.</div><div><br></div><div>I thought perhaps I should try to run `pip= 3 install meson` to do things the easy way, but apparently Pip is out of da= te (why is that); that hearkens back to the first question though.<br></div= ></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Jan 5, 2019 = at 8:21 PM Robert Alexander <<a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">> Whe= n I ran `startx` on the next boot, the server shutdown<br>> because the = VESA driver's ABI was at a different version than Xorg's.<br>> S= o I tried update that driver but I ran into some other issues. I<br>> co= uld describe those issues, but I'm feeling like that isn't the<br>&= gt; root issue.<br><br>I am not currently running GoboLinux but I remember = ABI-related problems<br>and xorg-server not starting.<br><br>What I usually= do is to make sure that LLVM is up to date; and cmake;<br>then I compile m= eson (<br>=C2=A0 <a href=3D"http://www.linuxfromscratch.org/lfs/view/system= d/chapter06/meson.html" target=3D"_blank">http://www.linuxfromscratch.org/l= fs/view/systemd/chapter06/meson.html</a><br>) (even though the URL includes= systemd, meson works perfectly well <br>without systemd of course; I only = have this "bookmarked" as link,<br>LFS/BLFS instructions can be s= uper-helpful). After meson I tend to<br>compile the xorg-libs (libx11, libi= ce, libsm, libxcb - all available<br>on the same URL where the xorg-server = is), then I compile the<br>xorg-server. Here you have to be a bit careful i= n that I have had<br>problems in the past; e. g. wayland related parts aren= 't that good;<br>I tend to do things such as --disable-xwayland-eglstre= am and similar<br>to xorg-server. This serves me better than enabling these= snippets.<br><br>By the way, from my own experience it is quite hard to br= eak a<br>GoboLinux system because you should always have the older versions= <br>in the respective directory under /Programs/ so you can just <br>re-sym= link that. :)<br><br>To your problem like this:<br><br><br>Requested 'x= proto >=3D 7.0.31' but version of Xproto is 7.0.29<br>Requested '= ;randrproto >=3D 1.6.0' but version of RandrProto is 1.5.0<br>Reques= ted 'presentproto >=3D 1.1' but version of PresentProto is 1.0<b= r><br><br>I think if you install <br><br><a href=3D"https://www.x.org/relea= ses/individual/proto/xorgproto-2018.4.tar.bz2" target=3D"_blank">https://ww= w.x.org/releases/individual/proto/xorgproto-2018.4.tar.bz2</a><br><br>then = this should be fine.<br><br>That has all the .pc files as far as I can see = for the protos:<br><br>scrnsaverproto.pc, trapproto.pc, videoproto.pc and s= o forth.<br><br>I also recommend to you to keep information in a text file = - this<br>may help you at a later time a LOT. I started noting down how<br>= to resolve some problems within the yaml-files that I use to <br>compile/in= stall programs from source; a bit like the LFS/BLFS<br>project but more tun= ed towards the problems I encounter.<br><br>I also used to autogenerate som= ething similar to LFS/BLFS - will<br>try to see to do so and then make this= available somewhere again.</div><div dir=3D"ltr"><br></div><div>PS: The ma= iling interface confuses me too a bit. I see your emails</div><div>but I do= n't see the other email that came first in 2019 altogether,</div><div>s= o I could not hit on "reply" (I sent a mail to the email listed t= hough).</div><div><br></div><div>I find mailing lists pretty confusing alto= gether in general.<br></div></div><br><div class=3D"gmail_quote"><div dir= =3D"ltr">On Sat, Jan 5, 2019 at 6:52 PM Philip White <<a href=3D"mailto:= [email protected]" target=3D"_blank">[email protected]</a= >> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px= 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di= v dir=3D"ltr"><div dir=3D"ltr"><div>I realized that digest mode is not what= I want for a mailing list, since I cannot reply to emails individually.</d= iv><div><br></div><div>Anyway, my attempt to build i3 has been sidetracked = because I ran</div><div><br></div><div>InstallPackage Xorg-Server</div><div= ><br></div><div>which broke X. When I ran `startx` on the next boot, the se= rver shutdown because the VESA driver's ABI was at a different version = than Xorg's. So I tried update that driver but I ran into some other is= sues. I could describe those issues, but I'm feeling like that isn'= t the root issue.</div><div><br></div><div>I would expect this is an issue = other people have run into, since nearly everyone uses Xorg, and people gen= erally keep their systems up to the latest version.</div><div><br></div><di= v>While looking for a solution, I noticed the UpdateXorgRecipe script. I ra= n it, and it made a bunch of local recipes, but as far as I can tell, it di= dn't actually compile anything. Thus, I tried to run `Compile Xorg-Serv= er` to compile the newly generated recipes. I got the dependency issues:</d= iv><div><br></div><div>Requested 'xproto >=3D 7.0.31' but versio= n of Xproto is 7.0.29<br><div>Requested 'randrproto >=3D 1.6.0' = but version of RandrProto is 1.5.0<br><div>Requested 'presentproto >= =3D 1.1' but version of PresentProto is 1.0</div><div><br></div><div>Ha= s anybody encountered this error before? Also, is there any documentation f= or what UpdateXorgRecipe does?</div><div><br></div><div>Last question, how = do I search these mailing list archives? The link on the website points to = <a href=3D"http://search.gmane.org/search.php?group=3Dgmane.linux.distribut= ions.gobo.general" target=3D"_blank">http://search.gmane.org/search.php?gro= up=3Dgmane.linux.distributions.gobo.general</a>, which does not work.</div>= <div><br></div><div>Thanks,</div><div>Philip<br></div></div></div></div></d= iv> _______________________________________________<br> gobolinux-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">go= [email protected]</a><br> <a href=3D"http://lists.gobolinux.org/mailman/listinfo/gobolinux-users" rel= =3D"noreferrer" target=3D"_blank">http://lists.gobolinux.org/mailman/listin= fo/gobolinux-users</a><br> </blockquote></div> _______________________________________________<br> gobolinux-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">go= [email protected]</a><br> <a href=3D"http://lists.gobolinux.org/mailman/listinfo/gobolinux-users" rel= =3D"noreferrer" target=3D"_blank">http://lists.gobolinux.org/mailman/listin= fo/gobolinux-users</a><br> </blockquote></div></div></div></div></div> _______________________________________________<br> gobolinux-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">go= [email protected]</a><br> <a href=3D"http://lists.gobolinux.org/mailman/listinfo/gobolinux-users" rel= =3D"noreferrer" target=3D"_blank">http://lists.gobolinux.org/mailman/listin= fo/gobolinux-users</a><br> </blockquote></div> --0000000000009aa9a3057f5bec95-- --===============2139106131355156362== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZ29ib2xpbnV4 LXVzZXJzIG1haWxpbmcgbGlzdApnb2JvbGludXgtdXNlcnNAbGlzdHMuZ29ib2xpbnV4Lm9yZwpo dHRwOi8vbGlzdHMuZ29ib2xpbnV4Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dvYm9saW51eC11c2Vy cwo= --===============2139106131355156362==--