Monthly snapshot announcement
Re: Monthly snapshot announcement
Thanks, as always, for doing this. I tracked the April snapshot, and over 1,300 people have downloaded it.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Monthly snapshot announcement
It's really easy, it doesn't take a lot of time to create snapshots, I'm glad people find them useful (BTW, SourceForge numbers are only partial since these snapshots are copied to most of the mirrors I think)
- dolphin_oracle
- Developer
- Posts: 19921
- Joined: Sun Dec 16, 2007 1:17 pm
Re: Monthly snapshot announcement
I put up a blog post https://mxlinux.org/may-snapshots-available
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: Monthly snapshot announcement
Right, only have access to SF numbers
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Monthly snapshot announcement
Get Your MX17.1 Linux May Snapshot with ZSYNC Now
For those who still wonder what those iso.zsync files are:
Below find a little zsync-wrapper script.
Place it in the same directory as one of those previous iso‘s you might
already have like:
MX-17_x64.iso, MX-17.1_x64.iso or MX-17.1_April_x64.iso
Make the script executable.
When run it will do:
- install zsync if not available - you might need to enter your password to install zsync
- fetch MX17-signing keys to verify the signature of the iso
- get the iso with help of zsync and if an older iso exists from closest sourceforge-server
- run the checksum- and signature verification
As I already had the April-iso the zsync download needed only 14% to download
to delta merge into a fresh May-ISO!
The script ZSYNC_MX-17.1_May_x64.sh :
EDIT: Any question/ comments to the script welcome ;=)
For those who still wonder what those iso.zsync files are:
Below find a little zsync-wrapper script.
Place it in the same directory as one of those previous iso‘s you might
already have like:
MX-17_x64.iso, MX-17.1_x64.iso or MX-17.1_April_x64.iso
Make the script executable.
When run it will do:
- install zsync if not available - you might need to enter your password to install zsync
- fetch MX17-signing keys to verify the signature of the iso
- get the iso with help of zsync and if an older iso exists from closest sourceforge-server
- run the checksum- and signature verification
As I already had the April-iso the zsync download needed only 14% to download
to delta merge into a fresh May-ISO!
The script ZSYNC_MX-17.1_May_x64.sh :
Code: Select all
#!/bin/bash
#---------------------------------------------------
# get Monthly MX Linux ISO with zsync
#---------------------------------------------------
# filename ZSYNC_MX-17.1_May_x64.sh
# fehlix 19-05-2018
# add available local ISO-sources here - newest last
SOURCE=MX-17_x64.iso
SOURCE=MX-17.1_x64.iso
SOURCE=MX-17.1_April_x64.iso
# new ISO-target we want get with zsync
#
TARGET=MX-17.1_May_x64.iso
#----------------------------------------------------
# some fun @ fehlix
#----------------------------------------------------
function echodo () { echo "#>> : ${@}"; "${@}"; }
function doit () {
local R;
echo "#>> BEGIN: ${@}";
"${@}"; R=$?;
echo "#>> END : ${@}"; return $R;
}
##---------------------------------------------------
# do we have zsync
command -v zsync >&- || {
# opps we need to and install zsync
sudo apt-get update
sudo apt-get install zsync
}
##---------------------------------------------------
# prepare keys for signaure verificytion
# keyserver use either of those below - change if timed out
HKP="--keyserver hkp://pool.sks-keyservers.net" # Global pool
HKP="--keyserver hkp://eu.pool.sks-keyservers.net" # European pool
HKP="--keyserver hkp://na.pool.sks-keyservers.net" # North american pool
HKP="--keyserver hkp://keys.gnupg.net" # Gnupg
##---------------------------------------------------
# MX17 signing keys:
# gpg: key 9B68A1E8B9B6375C: "Dolphin Oracle (mx linux) <dolphinoracle@gmail.com>"
# gpg: key 70938C780679EE98: "Adrian <adrian@mxlinux.org>"
# gpg: key 13C74A22892C32F1: "Steven Pusser <stevep@mxlinux.org>"
KEYS="9B68A1E8B9B6375C 70938C780679EE98 13C74A22892C32F1"
# we only use these trusted keys for signature verifications
RING="--no-default-keyring --keyring $HOME/.gnupg/trustedkeys.kbx"
# receive or update signaure keys
doit gpg -v $RING $HKP --recv-keys $KEYS
##---------------------------------------------------
#
ZSYNC=${TARGET}.zsync
MD5=$TARGET.md5
SIG=$TARGET.sig
# get closes sourceforge server for zsync
DOWNLD=https://sourceforge.net/projects/mx-linux/files/Snapshots/${ZSYNC}/download
SPIDER=$(wget -nv --spider ${DOWNLD} 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')
# let's do zsync
[ -f ${TARGET} ] || doit zsync -i $SOURCE ${SPIDER}
# get checksum and signature
URL="${SPIDER%/*}"
[ -f $MD5 ] || doit curl -RLJO $URL/$MD5
[ -f $SIG ] || doit curl -RLJO $URL/$SIG
# check sum
[ -f $MD5 ] && doit md5sum -c $MD5
# verfy signature with gpgv
[ -f $SIG ] && doit gpgv -v $SIG $TARGET
#-----#
exit #
#-----#
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Monthly snapshot announcement
I'm not sure if anyone can duplicate this but I booted up the 386 May snapshot in Virtualbox and the live session came without a panel.Adrian wrote: ↑Fri May 18, 2018 12:13 pm Snapshots for May are up. Nothing special, about 30 packages were updated, among them a Firefox update 59->60, and an installer bugfix for installing MX Linux on ESP.
Sourforge link: http://bit.ly/mx-monthly
edit-
Launching from terminal yields:
Code: Select all
demo@mx1:~/Desktop
$ xfce4-panel
(xfce4-panel:4151): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap
edit-
This is the thread
Panel dissapearing on Startup at random.
edit-
I believe something in mx-tools was compiled wrong on the 386 architecture. This is based on this forum post I found googling the error message:
https://forum.qt.io/topic/62035/gtk-err ... upported/4
and the fact that if I apt purge mx-tools and run sudo ldconfig, the panel starts.
edit-
Actually, sorry, all that needs to be done is sudo ldconfig.
You do not have the required permissions to view the files attached to this post.
Re: Monthly snapshot announcement
I see the same thing in 32bit, I will remove it from the repo.
I don't understand something, that's just 32bit May snapshot with the latest updates, would people who run regular 32bit see the same issue after they upgraded, why is that a problem only with the ISO?
I don't understand something, that's just 32bit May snapshot with the latest updates, would people who run regular 32bit see the same issue after they upgraded, why is that a problem only with the ISO?
Re: Monthly snapshot announcement
Not sure yet... testing further, basically confirm what was going on in the "Disappearing Panel" thread - April 386 snapshot boots fine, run sudo apt dist-upgrade, relogin and panel will not start with same error. This time sudo ldconfig does not resolve issue. Packages updates were:
So, it may be safe to say, the issue was introduced in these updates. I will check original 17.1 386, see what happens, if it's isolated to the snapshots or not.
Code: Select all
demo@mx1:~
$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
libvlccore8
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
libmicrodns0 libprotobuf-lite10 libva-wayland1 libvlccore9
The following packages will be upgraded:
adobe-flash-properties-gtk adobe-flashplugin antix-libs apt-notifier
cli-installer-antix curl firefox libcurl3 libcurl3-gnutls libmad0
libsdl-image1.2 libsdl2-image-2.0-0 libvlc-bin libvlc5 libwavpack1 mx-installer
mx-packageinstaller-pkglist mx-repo-manager mx-tweak openjdk-8-jre
openjdk-8-jre-headless smxi-inxi-antix tzdata vlc vlc-bin vlc-data vlc-l10n
vlc-plugin-base vlc-plugin-qt vlc-plugin-video-output wavpack wget
32 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 96.8 MB of archives.
After this operation, 17.8 MB disk space will be freed.
Do you want to continue? [Y/n]
Re: Monthly snapshot announcement
I will test the 32 update on 32-bit one by one to identify which causes the problem. Yet another advantage of monthly snapshots we can trace easier this kind of problems...
Re: Monthly snapshot announcement
It's curl or libcurl3, I will ask packagers to take a look and repackage it.