LinuxQuestions.org - dropline GNOME 3.38

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - dropline GNOME 3.38 - testing (https://www.linuxquestions.org/questions/slackware-14/dropline-gnome-3-38-testing-4175682242/)

Quote:

Originally Posted by reddog83 (Post 6176469)

I am wondering if you will include a .md5 CHECKSUM file as well as the rest of the files needed to run slackpkg+ with out error. I have downloaded all files and used a different program to make the repo readable with slackpkg+ but I am missing the Changelog.txt file with descriptions etc. in it
I understand you are working on the mainline programs but is there a away to make these certain repo files so that slackpkg+ can pick them up during the upgrade process and not barf on the GPG and MD5 errors?

It is not a problem adding a MD5 checksums file, but the preffered way of installing will be with the dropline-installer. We never had a slackpkg+ compliant repo but if you want to work it out please go ahead and I can try to see what we need to make it go by that distribution channel too.
Changelog file is included in each package, this is a way how our DBS work, so there is no way to get an central changelog as we went away from it years ago.

Quote:

Originally Posted by biker_rat (Post 6176363)

Saxa, I noticed you tried to fix pitivi in 3.38 testing on 10-14-20. It didn't work for me at first. Pitivi couldn't detect matplotlib and numpy. I found an old python-numpy package from alienbob was clobbering your numpy and removing the python-numpy package from alienbob fixed that. I removed you matplotlib and installed matplotlib using "pip3 install matplotlib" and then pitivi worked. "pip3 install matplotlib" pulled in a couple of deps, so that might have something to do with it. I wish I wrote down or remembered what those deps were but I dropped the ball there, sorry.

I'm the maintainer of pitivi on SBo, and when I switched it to a source build, these are the dependencies I found are needed for pitivi on a standard 14.2 install:

Code:

python3

python3-six

python3-dateutil

gstreamer-editing-services

py3cairo

pygobject3-python3

python3-tornado

python3-kiwisolver

pyhton3-cycler

pytz

python3-pyparsing

numpy3

python3-matploglib

gst-plugins-bad

Many of the python3 dependencies will likely be provided in -current itself, so some trimming will be required.

I also found the following optional dependencies, but SlackBuilds were not available on SBo at the time (not sure if they've been added since I last checked), but some or all might be provided with Gnome.

Code:

pycanberra - enable sound notification when rendering completes

GnomeDesktop - file thumbnails provided by GNOME's thumbnailers

notify - enables visual notifications when rendering is complete

Many thanks bassmadrigal, as far as I know lots of that stuff should be already in current. Also for now I think kiwisolver, cycler and dateutil are missing on my machine, not sure, but will take a closer look at it when I have all set up and in place.

Here is acouple of the files that are needed for slackpkg+ repo.

Quote:

Originally Posted by saxa (Post 6176673)

Quote:

Originally Posted by reddog83 (Post 6176928)

Here is acouple of the files that are needed for slackpkg+ repo.

Can you please post this to the DLG devel mailing list on the sf.net ?
I would like to keep that kind of info centralized, and if possible lets discuss it there, rather than here in a forum.
Also if possible please supply the tools scripts on how to generate that. I need help, so go ahead and prepare all the work.

Mailing list is: https://sourceforge.net/p/dropline-gnome/mailman/

Decided to give this a try. Installed it on top of a relatively fresh slackware64-current. I got a bit white 'oops, something went wrong' error whenever I started x, but only with my user.. others were fine.

Something amongst these files in ~/.config were the culprit.

28064 Nov 25 17:22 Trolltech.conf
4096 Nov 27 00:22 dconf
4096 Nov 27 00:37 gconf
4096 Nov 27 00:35 gnome-session
4096 Nov 27 00:22 goa-1.0
4096 Nov 27 00:22 ibus
624 Feb 17 2020 user-dirs.dirs
5 Feb 15 2020 user-dirs.locale

I haven't spent much time with this yet but so far it seems to be working.

I added these to /etc/slackpkg/greylist

1dl
2dl
3dl
4dl
5dl

(I'm not sure all of 1-5 are necessarily in use but whatever), now slackpkg clean-system does not select any of dropline gnome.

Slackware current have had many changes from the time I started building this. These days some new stuff came in and I will be building few updates shortly.

For slackpkg you can list *dl as blacklist or better ?dl.

Thanks a lot for making the latest GNOME possible in Slackware!
So far, it's working very well for me, still found out the following issues:

- cant find a login manager capable of starting gnome-session, lxdm from SBo does not work for me, see https://www.linuxquestions.org/quest...on-4175685803/
- adding a google account in Online accounts does not work for me, haven't tried other account types
- had to tweak xscreensaver to be able to lock the screen and turn off monitor by dpms

As i'm using slackpkg(plus) to manage software packages, would it be possible to add the required metadata files (PACKAGE.txt etc) and create a proper dropline gnome repository. then we could easily identify and upgrade _dl plackages :-)

Thanks for the effort!

Tomáš

PS: what is the right way to track bugs that i find in the future? Do you have bugzilla or some other tracker?

Hi Tomas, thanks for using it. GDM needs love to make it work. I have no rush to work on that until we see a stable release. What are you using is testing packages which on most of the part were just genuine sources compiled and they need some tweaking in some cases to make them fully slackware compliant and working.

Since it is a testing build, there is some stuff still missing etc.... so the google accounts i have not even used it and if you can make it work and inform the changes needed I will be happy to include it. SAme is for other stuff you see do not working.

As for the slackpkg I will think of it, but when released the preffered way of install will be most probably the dropline-installer.
Maybe I see that there is no need for a specific order of install as in the past and we supply the slackpkg repo. Will see that.

For bugs and other development you can safely use the dropline-gnome sourceforge.net project page or the development mailing list.

Quote:

Originally Posted by ganjaplanet (Post 6189671)

[snip]
cant find a login manager capable of starting gnome-session, lxdm from SBo does not work for me

You can use lightdm and lightdm-gtk-greeter to start gnome-session under Xorg. For some reason lightdm will not start gnome-session under wayland properly for me, although it will start weston.

There are somewhat outdated slackbuilds available for these on github if you google for them, which I do not use, so I cannot vouch for the slackbuilds. However they will be useful as starters.

Wondered what happen to what was here. See my next post for the whole enchilada. :)

I was helping out in this thread regarding upgraded to dropline GNOME 3.38 using slackpkg with slackpg+. I decide to give this a shot. The last time I use GNOME was back when it was part of Slackware. So hey why not check it out.

I installed this to a VirtualBox guest. The host OS is Slackware64-current with testing (gcc10 and vtown), up to date as of ChangeLog.txt Tue Dec 1 20:18:01 UTC 2020. The guest OS is Slackware64-current. I always do Full Installs. The guest is also up to date as of Tue Dec 1 20:18:01 UTC 2020. This is a plain install, no third parties except for slackpkg+ I am using slackpkg+ version 1.7.0. From this point on, when referring to slackpkg, I am referring to slackpkg with slackpkg+

This probably is not the solution some are looking for as noted in the comments above but you can use slackpkg with a local mirror. The initial setup. This is all done on the host.

I created a bash script to mirror both the 3.36 and 3.38 packages linked to from the instructions web page. Here is the key lines from the script.

Code:

lftp -c "open http://www.droplinegnome.org/files/3.36/x86_64/testing/; mirror -v -e . dropline-gnome/36/packages"

lftp -c "open http://www.droplinegnome.org/files/3.38/x86_64/testing/; mirror -v -e . dropline-gnome/38/packages"

This places the package files in /home/non-slack/dropline-gnome/36/packages and .../38/packages.

The next step was to make the repositories compatible with slackpkg. Do this this you will need a script from AlienBob's tools: http://www.slackware.com/~alien/tools/ called gen_repos_files.sh, read the comments in this batch file for usage. You also need to create a gpg key.

In each repository I created a repository defaults file .genreprc (Copy the sane default section from the script and tailor it to the repository. Should be self explanatory.) You do need one of these defaults file in each repository. I placed them in .../dropline-gnome/36 ...dropline-gnome/38.

Once that is completed then you run the gen_repos_files.sh on each repository to create the needed files. This is the command line I use to do this based on my setup.

Code:

USERDEFS=/home/non-slack/dropline-gnome/36/.genreprc bash gen_repos_files.sh

USERDEFS=/home/non-slack/dropline-gnome/38/.genreprc bash gen_repos_files.sh

Now the repositories are ready for use.

Setup on the VirtualBox guest. From root, I modified /etc/slackpkg/slackpkgplus.conf as follows. I included alienbobs repos to this because they are frequently used.

Code:

# The first three are to give priority to slackware64. This is a clean slackware64-current install.

PKGS_PRIORITY=( slackware64:id3lib ) # Also in alienbob

PKGS_PRIORITY+=( slackware64:ffmpeg ) # Also in alienbob

PKGS_PRIORITY+=( slackware64:oxygen-gtk2 ) # Also in alienbob

# Give priority to dropline38 over dropline36

PKGS_PRIORITY+=( dropline38 dropline36 )

PKGS_PRIORITY+=( slackpkgplus alienbob restricted )



REPOPLUS=( slackpkgplus dropline38 dropline36 alienbob restricted )



MIRRORPLUS['slackpkgplus']=http://slakfinder.org/slackpkg+/

# These are all local mirrors on my system.

MIRRORPLUS['alienbob']=file://home/non-slack/alienbob/

MIRRORPLUS['restricted']=file://home/non-slack/alienbob_restricted/

MIRRORPLUS['dropline36']=file://home/non-slack/dropline-gnome/36/

MIRRORPLUS['dropline38']=file://home/non-slack/dropline-gnome/38/

I next need to make sure my local repositories on the host are accessible to the guest. I created two directories off /home, same as on my host.

Code:

mkdir -p /home/{slackware,non-slack}

I then mount those to the corresponding location on the host. My /etc/slackpkg/mirrors points to "/home/slackware/slackware64-current/"

We are now ready to install dropline GNOME on this clean slackware64-current system.

Code:

slackpkg update gpg 

slackpkg update

slackpkg install dropline36

slackpkg install dropline38

slackpkg upgrade-all

Done. dropline GNOME is installed. I rebooted the guest, then logged in as me, ran startx. dropline GNOME is running. I tried all of the default Activities, all worked, even copied over a Benny Goodman mp3 over to Music to play. As it was mentioned in further up in the comments, runlevel 4 is not working. I'm not to familiar with GNOME3 so it is a bit of a learning curve. I did try gnome-tweaks mentioned above somewhere, it works.

I did run in to one issue with using slackpkg, there was two different versions of gnome-bluetooth and two ipython's with different build numbers in the dropline38 repo. I am guessing maybe I did the mirror in the middle of an update.

This isn't a grand solution for those who want a slackpkg compatible on-line repo, but if you have to room for a local repo, this in my opinion is a decent comprimise. One draw back is you have to regenerate the repository files needed for slackpkg after each mirror update. It doesn't take that long to do though, especially since I put the mirror on the host, vice the guest. That and I'm not sure if this is the way dropline GNOME is intended to be installed as I see a reference to a script to do this. If all of the packages for 3.38 will end up in the same place and installation order is not critical this should work.

I tested this three times. Including an additional test using upgradepkg. Hope this is useful to some.

Thank you so much chrisretusn, your approach is thorough.
I followed similar path and hd the same duplicity in packages, so chances are the repo is not totally cleaned of old versions.
`telinit 4` spits errors for me as well, `startx` runs just fine. the only thing that is not working for me is `gnome-online-accounts` - when trying to add a google (or microsoft) account, it tells that CLIENT_ID is unknown

nice day

Tomas

Quote:

Originally Posted by ganjaplanet (Post 6191405)

You are welcome. I believe saxa mentioned about that the online accounts wasn't up to speed either.