Porteus

I built my Mate 1.20 and it built for Porteus-4.0rc4-x86_64.iso and it works great to. Well today I upgraded Porteus to the release version dated 29-Apr-2018 and I lost the time and internet icons when I try to add them it would not let me. When I use Porteus-4.0rc4-x86_64 it seen everthing when I first try it.

My question is what got change from Porteus-4.0rc4-x86_64 to the release version? I want to fix it in my Mate build. Is there a change log what got change for rc4 to time of the release of Porteus?

I check 001 and 002 in both and here what I found.

extra-gcc-libs-7.3.0-x86_64-1jay
nghttp2-1.31.0-x86_64-1
talloc-2.1.11-x86_64-1
tevent-0.9.36-x86_64-1

Is that what cause my problem with the icons not working? Or is it something else?

Have you checked your 003-Mate file against the 003-Mate file in the Porteus-Mate-v4.0-x86_64.iso?

I just check it here is the output.

Here is his list that wasn't in mind.

asunder-2.8-x86_64-1jss
brisk-menu-0.5.0-x86_64-1jss
ffmpegthumbnailer-2.2.0-x86_64-1jss
glade-3.22.1-x86_64-1jss
gnome-mpv-0.11-x86_64-1jss
gnome-themes-standard-3.22.3-x86_64-1
hunspell-1.6.2-x86_64-1
iso-codes-3.76-noarch-1
jasper-2.0.12-x86_64-1
keybinder-0.3.1-x86_64-1
lxtask-0.1.8-x86_64-1jss
mate-settings-daemon-1.20.1-x86_64-1jss
openldap-client-2.4.46-x86_64-1
transmission-2.92-x86_64-1_SBo

Here is my list that wasn't in his.

aspell-en-7.1_0-x86_64-1
binutils-2.30-x86_64-1
caja-dropbox-1.20.0-x86_64-1_msb
glib-1.2.10-x86_64-4
graphviz-2.40.1-x86_64-1_msb
gtk+-1.2.10-x86_64-6
gtk-engines-2.21.0-x86_64-1_msb
libbluray-1.0.1-x86_64-1
mate-applets-1.20.0-x86_64-1_msb
mate-sensors-applet-1.20.0-x86_64-1_msb
mate-settings-daemon-1.20.0-x86_64-1_msb
mate-system-monitor-1.20.0-x86_64-1_msb
mate-themes-3.22.15-noarch-1_msb
pygobject-2.28.7-x86_64-1
pygtk-2.24.0-x86_64-4
udftools-1.0.0b3-x86_64-3_slonly
vala-0.38.7-x86_64-1_msb
yelp-tools-3.18.0-x86_64-1_msb
yelp-xsl-3.20.1-x86_64-1_msb

It's deps of samba

Jack wrote: ↑

14 Sep 2018, 04:02

Here is his list that wasn't in mind.

"his" being me (jss), I thought I had to answer. It is slightly complicated, but I think still doable.
Jack, from your package list you are taking Willy Sudiarto Raharjo's packages (who maintains msb).

Now, here is the problem:
Willy Sudiarto Raharjo's packages are updated to the latest Slackware current. (That is, today). Porteus 4.0 packages are based on the Slackware current snapshot as of 29-Apr-2018 when Porteus 4 was released. (The reason why rc4 works for you is because, you have taken Willy Sudiarto Raharjo's packages when what Slackware current was at the tme Porteus 4 rc4 was at that same time).
The only way you can upgrade your MATE to Porteus 4.0, Jack, is not to take Willy Sudiarto Raharjo's packages, but to build MATE based on his slackbuild scripts.

And another thing: Comparing Willy Sudiarto Raharjo's packages with Porteus 4's MATE packages (-jss packages) would not help you because I have built MATE for Porteus 4 not based on Willy Sudiarto Raharjo's packages. For example, you can see how, like you have pointed out, how taking his msb packages, you have dependencies with gtk-1 to be included, while MATE is now pure gtk-3.

Jack wrote: ↑

14 Sep 2018, 04:02

Here is my list that wasn't in his.

Jack wrote: ↑

14 Sep 2018, 04:02

gtk+-1.2.10-x86_64-6

I will live for what I have and as long as it works I won't worry about it @70 it will out live me I think. I found out today that rc5 works too.

If I build a Current Mate 1.20 do I need to do a full install of Slackware? If so I can get a current iso from here http://bear.alienbase.nl/mirrors/slackw ... rrent-iso/ and will that be all I need?

While you CAN build from a full slackware install I usually compile from porteus with the 05_devel module activated.

brokenman wrote: ↑

16 Sep 2018, 21:19

While you CAN build from a full slackware install I usually compile from porteus with the 05_devel module activated.

When you build do you build in Always Fresh? Do you load any Desktop?

I always build in always fresh mode. I generally build from a very minimal desktop such as lxde or xfce. This ensures I only add what is needed at compile time. If you are building mate then I would build it from a mate desktop. Cinnamon from a cinnamon desktop etc.

Jack wrote: ↑

14 Sep 2018, 00:51

I built my Mate 1.20 and it built for Porteus-4.0rc4-x86_64.iso and it works great to.

Sorry off-topic maybe but would you advise me to build too my own MATE and why? If so, is it easy to replace the standard desktop in my live USB with this new build?

Macchiato wrote: ↑

19 Sep 2018, 05:52

If so, is it easy to replace the standard desktop in my live USB with this new build?

Two ways to do it. 1. Open the ISO file, remove the 003-Mate module there and replace it with the new 003-Mate module, close the ISO file. 2. Put the new 003-Mate file in your /porteus/modules folder, give it a unique name, like 003-MyDE, then add these cheatcodes to your Porteus start menu: extramods=/porteus/modules noload=mate

Number 2 is especially easy when testing a new module.

I have a brokenman current base version and I just built a new version of Mate current files. When I get up I will do some testing of my new Mate.

I try it today and I try it in Always Fresh and then in Text Mode and then type Slim and both times in a Black screen. I use my new Acer Computer and I use EFI to boot it. So what could the problem be?