Woof CE Debian Stretch and Devuan Ascii Based Development

[Billtoo]

@billtoo & ttuuxxx,

Will either of you be releasing that kernel separately where I could (some way) drop it in this dpup-stretch of mine to upgrade from the 3.14.79?

I'm using the original dpup stretch iso that I posted on Smokey01's
server, I got the kernel from an (auto woof-CE) tahrpup build that I did on
feb23rd.
I used the method I described a few pages back to change the kernel in
Dpup Stretch.
I've been running it for 5+ hours without anything awful happening

Hi pemasu.

[pemasu]

I downloaded the woof-ce and created stretch platform.

DISTRO_PKGS_SPECS-debian-stretch:

yes|pup-volume-monitor||exe

yes|glib|libglib2.0-bin,libglib2.0-0,libglib2.0-data,libglib2.0-dev|exe,dev,doc>null,nls>null #does not work with pup-volume-monitor

yes|zzz_glib||exe,dev,doc>null,nls>null #pet

So...If the builder has not changed this, there is debian glib and self-compiled glib installed. And if the error still happens, then the file locations are different in those packages and debian glib libraries are called first. Maybe because they are on the /lib and self-compiled has them on the /usr/lib or the loading gio binary is called from the debian installation first.

[ttuuxxx]

I downloaded the woof-ce and created stretch platform.

DISTRO_PKGS_SPECS-debian-stretch:

yes|pup-volume-monitor||exe

yes|glib|libglib2.0-bin,libglib2.0-0,libglib2.0-data,libglib2.0-dev|exe,dev,doc>null,nls>null #does not work with pup-volume-monitor

yes|zzz_glib||exe,dev,doc>null,nls>null #pet

So...If the builder has not changed this, there is debian glib and self-compiled glib installed. And if the error still happens, then the file locations are different in those packages and debian glib libraries are called first. Maybe because they are on the /lib and self-compiled has them on the /usr/lib.

Your 100% correct and thank-you I installed the zzz_glib-2.50.2-i686-dpup-stretch.pet and dev and now it doesn't crash , Man it feels good when things work out , Thanks Once again
ttuuxxx

[pemasu]

I still would check the package structure, it might be that the debian and zzz version has different locations of the bins and libs. And....I would remove the debian version from the recipe to build using woof-ce.

##yes|glib|libglib2.0-bin,libglib2.0-0,libglib2.0-data,libglib2.0-dev|exe,dev,doc>null,nls>null #does not work with pup-volume-monitor and should not be used if pup-volume-monitor is installed

[ttuuxxx]

I still would check the package structure, it might be that the debian and zzz version has different locations of the bins and libs. And....I would remove the debian version from the recipe to build using woof-ce.

##yes|glib|libglib2.0-bin,libglib2.0-0,libglib2.0-data,libglib2.0-dev|exe,dev,doc>null,nls>null #does not work with pup-volume-monitor and should not be used if pup-volume-monitor is installed

yes I'm removing the debian versions. Thanks for help
ttuuxxx

[musher0]

@belham2 : apologies accepted. Have a great day!

[ttuuxxx]

Here's an idea guys download and compile Glib, The two that are included aren't compatible with each other, One uses /lib and the other usr/lib one (DEB) has needed dev files that the pet doesn't have. A fresh compile of glib-2.50.3 should be done, I just did and its more complete than both.
ttuuxxx

[musher0]

Glad to see you back, pemasu!

[musher0]

ttuuxxx?

Maybe remove the Devuan Ascii mention from your title? Sailor Enceladus has
started a thread for development of it here.

Just a thought.

[ttuuxxx]

ttuuxxx?

Maybe remove the Devuan Ascii mention from your title? Sailor Enceladus has
started a thread for development of it here.

Just a thought.

The two distro's are almost 100% identical, I don't see any reason to do it.
Also a lot of fixes on here can be applied to it, it would be counter productive to do that.
ttuuxxx

[ttuuxxx]

ttuuxxx?

Maybe remove the Devuan Ascii mention from your title? Sailor Enceladus has
started a thread for development of it here.

Just a thought.

LoL there latest issue on that post is identical to the one I just had and we fixed it on here.
And that my friend is the reason why the name is staying in the title
ttuuxxx

[ttuuxxx]

Ok its starting to shape up now, I'm going to build another iso and see if all the latest fixes work
ttuuxxx

[musher0]

Hi ttuuxxx.

As I said, it was "just a thought"! No need to fuss. Don't make a whole
dish out of it.

(Geez, the Anglo-Canadian mentality, sometimes...)

If you want to NOT co-operate, be the ultimate competitor, trample on
everyone else and grab Sailor's development thread as your own as well
as this one, go right ahead.

Just remember that there are other people here -- who are not idiots,
either. And that a lesson in humility might be waiting for you just around
the corner.

Regards.

[pemasu]

Since I downloaded the woof-ce, I decided to give a spin for woof-ce of today`s version. New git clone I mean.
I created dpup stretch and then I compiled in it new kernel and then I woofed the distro with new kernel.
The bugs I found in dpup stretch building. There is missing symlink in the devx from /usr/bin/gcc to /usr/bin/cc. It caused that the aufs-util didnt compile and the kernel packaging failed. I fixed the symlink and then the kernel compiling, aufs-util compiling and kernel packaging worked as a charm. Never has the kernel compiling been so easy. I created 4.1.38 kernel using the existing DOTconfig. Thanks to someone.

Sandbox3/devx folder. 2 missplaced symlinks are created to the root of the filesystem: gcc and g++ symlinks. I believe that the packages-templates folder gcc_dev and fixuphacks script inside might be the reason. Debian stretch has difficult name for gcc: i686-linux-gnu-gcc-6 and for g++ also. It might be that the template gets confused, or the reason is somewhere else.

working iptables binary needs still 2 packages. I give the working specs row:

yes|iptables|iptables,libip4tc0,libip6tc0,libxtables12,iptables-dev|exe,dev,doc>null,nls>null

Rc.firewall script has hardcoded path for iptables. Symlink is needed: # ln -s /sbin/iptables /usr/sbin/iptables
And after that Firewall setup started to work.

I compiled the patched evince with patches found for 2.32 version. The size is 482 k, so I cant upload it here, I think. I also compiled Mplayer.
Kernel compiling works and app compiling seems to work. I think the devx base is quite good.

Glib bug has been fixed already in the woof-ce. Really fast work. Somebody is watching, lol. And thanks.

I have to say that the woof has really taken huge steps forward and it was easy platform to create puplet and kernel compiling and including to the distro was unbelievably easy. Woof-ce guys (girls ?) have done splendid job. My compliments to them.

[peebee]

I have to say that the woof has really taken huge steps forward and it was easy platform to create puplet and kernel compiling and including to the distro was unbelievably easy. Woof-ce guys (girls ?) have done splendid job. My compliments to them.

Great to see you back pemasu

Recent woof-CE improvements are 90% down to wdlkmpx / jlst who's done a splendid job largely single handed....building of course on the solid foundations provided by barryk, 01micko, iguleder, jamesbond, zigbert and mavrothal etc.

FYI....
You can use the EXTRA_COMMANDS section in _00build.conf to implement small fixes like missing links until they are fixed "properly" at the woof-CE level....but there are many other mechanisms including zz pets, package-templates etc. etc.

Cheers
peebee

[pemasu]

Thanks peebee of the woof-ce info.

I uploaded the evince-2.32 ( last of the gtk-2 versions ) and it has the patches I found from the net. Same patches as Barry Kauler has used.

It installs as the default pdf viewer when clicking the pdf.

http://www.smokey01.com/pemasu/DpupStre ... 0-i686.pet

http://www.smokey01.com/pemasu/DpupStre ... 0-i686.pet

[musher0]

Hello pemasu.

Thanks for this. Two problems, however:

1) petget was unable to install the pets and UExtract was unable to un-
compress them. I had to use peazip and then Xarchive to get to the files.

2) the executables were labeled as dynamic libraries, so I had to use
OscalTalks' suggestion of using elfedit to correct the file type from DYN
to EXEC.

I have corrected the types of the executables and repackaged as xz
archived pet files.

No mean to insult anyone, but please find below URLs for download of
the corrected pets. This may save some time.

I tested them on my Dpup Stretch-7 and they work as expected, but
feedback would nevertheless be appreciated. TIA.

evince-2.32.0-i686.pet
http://www59.zippyshare.com/v/e203zI4o/file.html

evince_NLS-2.32.0-i686.pet
http://www110.zippyshare.com/v/yUjmQOxC/file.html
(Download addresses above valid for 30 days from date of last download.
Please send me a PM if the delay is expired. TIA.)

Sincerely,

[belham2]

Hello pemasu.

Thanks for this. Two problems, however:

1) petget was unable to install the pets and UExtract was unable to un-
compress them. I had to use peazip and then Xarchive to get to the files.

2) the executables were labeled as dynamic libraries, so I had to use
OscalTalks' suggestion of using elfedit to correct the file type from DYN
to EXEC.

I have corrected the types of the executables and repackaged as xz
archived pet files.

No mean to insult anyone, but please find below URLs for download of
the corrected pets. This may save some time.

I tested them on my Dpup Stretch-7 and they work as expected, but
feedback would nevertheless be appreciated. TIA.

evince-2.32.0-i686.pet
http://www59.zippyshare.com/v/e203zI4o/file.html

evince_NLS-2.32.0-i686.pet
http://www110.zippyshare.com/v/yUjmQOxC/file.html
(Download addresses above valid for 30 days from date of last download.
Please send me a PM if the delay is expired. TIA.)

Sincerely,

Hi Musher,

Can I ask a question, and please do not get offended, because this is me being truly dumb. So I had downloaded pemasu's evince-2.32 (thank you, pemasu!) and I had used UExtract to extract, which it did, then I used Rox and placed the extracted contents in every place they were supposed to go. And I used Evince 4-5 of times and it worked with no problems. Then I just see your post now, and it says pemasu's evince does not work and UExtract didn't either. I honestly don't understand...how is it possible it works on my woof-CE dpup-stretch 700 build but you're saying it doesn't/didn't work on yours?

I had downloaded your elfedit.sh days ago, and made it a right-click option, but I have yet to use it. This is making me really confused...same thing about reading people saying Leafpad and Geany crash or just close when using 'save-as', but I have used them both, multiple times, both 'save' and 'save-as', and neither one of them has ever closed and/or crashed on me.

I just don't understand what is going on and how the build I did can be acting different.

Thank you kindly for any explanations about pemasu's evince .pet and what I saw UeXtracting it and installing it, plus the Leafpad/Geany talk of problems....I am sure it all is something simple and I am just too dense to understand it.

[Sailor Enceladus]

same thing about reading people saying Leafpad and Geany crash or just close when using 'save-as', but I have used them both, multiple times, both 'save' and 'save-as', and neither one of them has ever closed and/or crashed on me.

I just don't understand what is going on and how the build I did can be acting different.

I was right! Talk about a lucky guess. Hahaha. When you made your build, libglib-2.0.so.0.5000.2 was at 5000.2 (see /root/.packages/builtin_files/glib), but in mine the glib was up to 5000.3, so in mine it was out of sync with zzz_glib which was still at 5000.2 (so there were pieces of 5000.2 and 5000.3 together), but in yours it was all still at 5000.2. Funny thing was your ISO was sitting right infront of me the entire time and I posted a reply asking you and I didn't even think of just opening it - lol.

[belham2]

same thing about reading people saying Leafpad and Geany crash or just close when using 'save-as', but I have used them both, multiple times, both 'save' and 'save-as', and neither one of them has ever closed and/or crashed on me.

I just don't understand what is going on and how the build I did can be acting different.

I was right! Talk about a lucky guess. Hahaha. When you made your build, libglib-2.0.so.0.5000.2 was at 5000.2 (see /root/.packages/builtin_files/glib), but in mine the glib was up to 5000.3, so in mine it was out of sync with zzz_glib which was still at 5000.2 - so there were pieces of 5000.2 and 5000.3 together, but in yours it was all still at 5000.2. Funny thing was your ISO was sitting right infront of me the entire time and I posted a reply asking you and I didn't even think of just opening it - lol.

Ah, I feel better now---seriously. I was getting worried, lol, I had some alien install or something. Thanks, Sailor!!!