Community ISO maintenance and build issues - 2

[grizzler]

It would, but why bother using geoip-database-contrib at all? The geoip-database package has been around for years. It's available in stretch, even goes back as far as wheezy.

Because geoip-database-contrib is a download script:

I see. Then the real replacement would probably be geoipupdate:
https://dev.maxmind.com/geoip/geoipupdate/
https://tracker.debian.org/pkg/geoipupdate
https://tracker.debian.org/pkg/libmaxminddb

Perhaps for the installer it's overkill to have the contrib package.

Wouldn't you still need something to keep the database up-to-date?

[kurotsugi]

btw, is it really safe to run deborphan there? in my experience autoremove is enough. OTOH deborphan could became quite nasty. the system would still works, but since deborphan works deeper, some recommended packages sometimes got removed, which leads to loss of some functionalities.

[Arjen Balfoort]

I've adapted live-installer-3 to use geoipupdate instead of geoip-database-contrib.
I had to manually create /etc/GeoIP.conf:

Code: Select all

# The following AccountID and LicenseKey are required placeholders.
# For geoipupdate versions earlier than 2.5.0, use UserId here instead of AccountID.
UserId 0
LicenseKey 000000000000

# Include one or more of the following edition IDs:
# * GeoLite2-City - GeoLite 2 City
# * GeoLite2-Country - GeoLite2 Country
# For geoipupdate versions earlier than 2.5.0, use ProductIds here instead of EditionIDs.
ProductIds GeoLite2-City GeoLite2-Country

In SolydXK-10:

Code: Select all

# The following AccountID and LicenseKey are required placeholders.
# For geoipupdate versions earlier than 2.5.0, use UserId here instead of AccountID.
AccountID 0
LicenseKey 000000000000

# Include one or more of the following edition IDs:
# * GeoLite2-City - GeoLite 2 City
# * GeoLite2-Country - GeoLite2 Country
# For geoipupdate versions earlier than 2.5.0, use ProductIds here instead of EditionIDs.
EditionIDs GeoLite2-City GeoLite2-Country

For this reason I've also adapted the cleanup.sh script of solydxk-constructor. It generates this .conf file depending the version of geoipupdate.

[grizzler]

Great! I've also updated my ISO build scripts.

Now to figure out why upgrading the lot still wants to remove the installer...

Edit
Curious. You need to install geoip-database separately first, or apt will get seriously confused.

P.S.
You do know about dpkg --compare-versions, don't you? The relevant bit in my script is:

Code: Select all

if dpkg --compare-versions "$InstalledVersion" lt "2.5.0"; then
	ID1=UserId
	ID2=ProductIds
else
	ID1=AccountID
	ID2=EditionIDs
fi
cat >"$RootPath/etc/GeoIP.conf" <<-EOT
# The following AccountID and LicenseKey are required placeholders.
# For geoipupdate versions earlier than 2.5.0, use UserId here instead of AccountID.
$ID1 0
LicenseKey 000000000000

# Include one or more of the following edition IDs:
# * GeoLite2-City - GeoLite 2 City
# * GeoLite2-Country - GeoLite2 Country
# For geoipupdate versions earlier than 2.5.0, use ProductIds here instead of EditionIDs.
$ID2 GeoLite2-City GeoLite2-Country
EOT
ChrootRun /usr/bin/geoipupdate

Where $InstalledVersion is set by a function that checks whether the specified package is installed (in a chroot if $RootPath is set), $RootPath points to the root in the ISO's chroot and ChrootRun runs the specified binary in that chroot.

[Arjen Balfoort]

Great! I've also updated my ISO build scripts.

Now to figure out why upgrading the lot still wants to remove the installer...

Edit
Curious. You need to install geoip-database separately first, or apt will get seriously confused.

Yes, I thought it was just me...

P.S.
You do know about dpkg --compare-versions, don't you?

No, I didn't. I never had to use that in bash, just in Python. Thanks, I'll update the cleanup script with your code.

[Arjen Balfoort]

...but the live installer is not working:

Code: Select all

Error Opening file /usr/share/GeoIP/GeoIPCity.dat

I'll have to look into that.

[Arjen Balfoort]

That was easier than I thought. Use python3-geoip2: https://geoip2.readthedocs.io/en/latest/
Updated live-installer-3 in repository.

[Arjen Balfoort]

Don't forget to adapt boot/live/filesystem.packages-remove:

Code: Select all

live-installer*
python3-geoip2
geoipupdate
live-boot
live-boot-initramfs-tools
live-config
live-config-sysvinit
live-config-systemd
live-build
live-tools
gdisk
gparted
jfsutils
libgtkmm-2.4*
xfsprogs
libreadline5
streamer
isoquery
libparted-fs-resize0

[grizzler]

Hadn't looked at that yet. Thanks.

By the way, I'm leaving gdisk out of that list. There was a good reason, but I'm too busy to check right now...

Just remembered. This was it: https://forums.solydxk.com/viewtopic.ph ... isk#p67172

[grizzler]

I am not sure why I have no solydxk-system as I simply did a normal install, I assume it is part of the normal install?

It is. It's in all the ISO build structures. I'll do another install this weekend to see if anything weird happens.

Used a different approach and ran an apt purge simulation for all the files listed in filesystem.packages-remove. This is what happened with the last one:

Code: Select all

p07@asus /data/onderzoek $ imt ex64 chroot -- apt purge -s libparted-fs-resize0
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  geoipupdate haveged libblockdev-crypto2 libblockdev-loop2 libblockdev-swap2
  libblockdev-utils2 libblockdev2 libcdio-cdda2 libcdio-paranoia2 libcdio18
  libgdata-common libgdata22 libgtkmm-2.4-1v5 libhavege1 libmaxminddb0
  liboauth0 libvolume-key1 python3-dateutil python3-geoip2 python3-maxminddb
  python3-parted python3-pyqt4 python3-sip
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  gparted* gvfs* gvfs-backends* gvfs-daemons* gvfs-fuse* libblockdev-fs2*
  libblockdev-part-err2* libblockdev-part2* libparted-fs-resize0*
  live-installer-3* live-installer-3-slideshow* solydxk-system* udisks2*
  usb-creator*
0 upgraded, 0 newly installed, 14 to remove and 0 not upgraded.
Purg live-installer-3-slideshow [2018.08.01]
Purg live-installer-3 [2018.08.01]
Purg gparted [0.30.0-3]
Purg gvfs-backends [1.36.2-1]
Purg gvfs-fuse [1.36.2-1]
Purg gvfs [1.36.2-1]
Purg gvfs-daemons [1.36.2-1]
Purg usb-creator [0.5.4]
Purg solydxk-system [3.0.7b6]
Purg udisks2 [2.7.6-3]
Purg libblockdev-fs2 [2.16-2]
Purg libblockdev-part2 [2.16-2]
Purg libblockdev-part-err2 [2.16-2]
Purg libparted-fs-resize0 [3.2-21+b1]

So that file will have to be removed from filesystem.packages-remove. I'll build new EE ISOs later.

[grizzler]

Built new EE ISOs and they're bad. The SolydKs have no desktop, just a default Debian background with the SolydXK install icon top left (seems to work...) and the 32-bits still need safe mode in my VM to start. The VM window then resizes somewhat, but not to its normal full proportions. Only the SolydX EE 64 appears more or less normal.

At this point I'm not sure what to do. Because of the filesystem.packages-remove mess mentioned in my previous posting, leaving the current 201808 set in place is not a good idea: the installer will remove solydxk-system. But in a way the new set is worse and I have no idea how long it will take to figure out what's wrong this time.

P.S.
I have to be elsewhere the rest of the evening and most of tomorrow...

Edit
Uploading the Xs now (runs unattended). Keep the old Ks? Remove them?

[grizzler]

Just before I started to prepare for a thorough examination of the SolydKs, I read this, which sums up some of the issues I saw when I tried the live systems.

So for now, I'm not going to waste time on this junk.

[grizzler]

Seems to be fixed. New SolydK EE ISOs built and being uploaded now.

[Mia]

Hello,

Following this topic
https://forums.solydxk.com/viewtopic.ph ... 986#p68986
I just tried it with SolydK EE 64 bits and the problem is unfortunately still there
The desktop is empty except the background image as soon as the installation is done while it works if I stay on the live.


Indeed, my graphics card is not compatible, it's a shame.

Another thing that has nothing to do with it but that happens with any version, the numeric keypad is inverted to enter the login, you have to disable it to access the numeric keypad

[Arjen Balfoort]

I found that buster removed WebKit (gir1.2-webkit-3.0) from the repository in favor of WebKit2 (gir1.2-webkit2-4.0).

I have to rewrite code for the live installer but it's a lot more complicated than I hoped for. So, for now, you'll have to keep gir1.2-webkit-3.0 on your ISOs if you want to use the live installer on the EEs.

I'll let you know when I've finished coding.

[grizzler]

OK. Thanks for the warning.

[Arjen Balfoort]

WebKit2 is a dead end for now. It seems that it is missing some very needed Python bindings. So, I'm reverting back to WebKit and I will provide the needed packages for solydxk-10:

Code: Select all

gir1.2-javascriptcoregtk-3.0_2.4.11-3_amd64.deb
gir1.2-javascriptcoregtk-3.0_2.4.11-3_i386.deb
gir1.2-webkit-3.0_2.4.11-3_amd64.deb
gir1.2-webkit-3.0_2.4.11-3_i386.deb
libicu57_57.1-6+deb9u2_amd64.deb
libicu57_57.1-6+deb9u2_i386.deb
libjavascriptcoregtk-3.0-0_2.4.11-3_amd64.deb
libjavascriptcoregtk-3.0-0_2.4.11-3_i386.deb
libwebkitgtk-3.0-0_2.4.11-3_amd64.deb
libwebkitgtk-3.0-0_2.4.11-3_i386.deb

I'm testing this now with SolydK 10.

If you're interested in the technicalities, I posted the question at Stackoverflow: https://stackoverflow.com/questions/528 ... omdocument

[grizzler]

Are you sure about those version numbers? The javascriptcoregtk-3.0 and webkit(gtk)-3.0 packages on my system (and the EE ISOs) are 2.4.11-4 and libicu57 is 57.1-9. That's buster/testing, when it still had them.

[Arjen Balfoort]

I'm afraid those version were removed from buster. They are not available anymore or, in case of libicu57, not available for for amd64 or i386.

The packages I added are from stretch and they at least work on SolydK 10. I haven't had the time to test them on SolydX 10 but I assume there will be no difference.

I could get them from sid but we'd need a lot more testing. I prefer to get those versions naturally whenever they are moved to testing.

[Arjen Balfoort]

I just found out that if you install the backports packages in stretch, I get a JSCValue object back. At least that's not an error

Code: Select all

apt install -t stretch-backports gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libjavascriptcoregtk-4.0-18 libwebkit2gtk-4.0-37  libwebkit2gtk-4.0-37-gtk2

I haven't checked but I bet those are the same versions as in buster. So, I will be checking that further when I have some time.