Submitting packages

[laprjns]

Yup, its there now.
Thanks

Rich

[mimosa]

Yes, now I see it too.

[ruario]

Sorry, have been away on holiday. Works for me now as well!

[Papasot]

Just a question, what if I have packages ready for submission, but the corresponding *.txz is provided for x86_64 architecture only? I don't have any machine running Salix 32-bit, and I prefer not to use cross-platform compiling (which I never trusted and I doubt it will even work in this case).
To get the 32-bit txz, I tried to create a virtual Salix 32-bit installation with Virtualbox, and set it to be Linux 32-bit. However, the Salix installer won't let me proceed with installation, saying kernel is not appropriate. I am guessing this is because the machine is actually 64 bit.

I do have the 32-bit txz packages but those are built on Slackel, where I do have an actual machine running the OS. However, the binaries are created with gcc 5.3.0, while Salix's default gcc version is 4.8.2.
So, is it acceptable to send the SLKBUILD and the x86_64 files, knowing the exact same SLKBUILD will work on 32-bit, as it works perfectly on Slackel32?

[mimosa]

No, you must build and upload packages for both architectures (assuming you are talking about submissions for the 14.2 repository). You may find salix-chroot-install useful for this in your case. Just download the 32-bit iso, and "install" it to a directory. Then chroot into it with schroot, and build your package. You need to set up a config file first that tells where your chroot lives:

Code: Select all

mimosa[~]$ cat /etc/schroot/chroot.d/alpha32
[alpha32]
description=Salix 14.2 32-bit
directory=/home/mimosa/chroot/alpha32
users=mimosa
root-users=mimosa
personality=linux32
type=directory

Then just do

Code: Select all

schroot -c alpha32

[gapan]

Your problem with virtualbox might be that you need to check the PAE option in the VM settigns.

[djemos]

Or use vmware download trial 12.1.1 version. Install it with sudo sh VMware-Workstation-Full-12.1.1-3770994.x86_64.bundle --ignore-errors
You will need a serial key. Find it in google.

[Papasot]

Thank you all for the suggestions. Since I already had Virtualbox installed, I tried that first, this time checking that "hidden" option "Enable PAE/NX", as gapan suggested, and it worked. Salix was installed without any problem, building the packages with slkbuild worked perefectly, and the resulting packages work as expected as well. However, slkbuild sets the $arch variable for the resulting files as "i486" while the packaging rules say it should be i586 "in most cases".
Indeed, there is a folder, /usr/i486-slackware-linux, while in my "real" Slackel 32-bit installation it's /usr/i586-slackware-linux. I had a look at the package log file and I saw it scans that folder, finds 486, hence the $arch.
What am I doing wrong here?

[gapan]

You're running 14.1, not 14.2.

[Papasot]

You're running 14.1, not 14.2.

Ok, I didn't know Salix 14.2 alpha was available. I suppose the x86_64 packages should also be built on salix64-xfce-14.2alpha1 as well?