SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
JayByrd, ... Trailing spaces don't seem to make a difference, for what it's worth.
Quote:
Originally Posted by marav
From what I see, it's just a removal of the 1 space after the url and one of the empty line
Well that settles it!
OK, so I removed the trailing spaces in my local copy of the zseal slack-desc, and that seems to have fixed that one. However, I have another that has no trailing spaces and, like above, it doesn't show the PACKAGE DESCRIPTION when installing:
Code:
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description.
# Line up the first '|' above the ':' following the base package name, and
# the '|' on the right side marks the last column you can put a character in.
# You must make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':' except on otherwise blank lines.
|-----handy-ruler------------------------------------------------------|
rtl8192eu: Driver for USB wifi adapters based on the Realtek RTL8192e chip.
rtl8192eu:
rtl8192eu: Specifically for D-Link and TP-Link adapters:
rtl8192eu: D-Link DWA-131. TP-Link: TL-WN821N V6/TL-WN822N V5/
rtl8192eu: TL-WN823N V3 & V2.
rtl8192eu:
rtl8192eu: May also work on other brands using the rtl8192e driver.
rtl8192eu:
rtl8192eu: For more information, see:
rtl8192eu: http://support.dlink.com.au/
rtl8192eu:
Things I have verified on this one:
1. No trailing spaces on any of the lines.
2. Tried both with and without a blank "newline" at the end of the file.
3. Verified correct permissions: 644.
Still, no dice... The only thing left that I can think of might be an encoding issue: UTF vs. ASCII, perhaps..? I doubt that that is the cause, because I've tried both Mousepad and vi (elvis,) and the results are the same--i.e., some work and some don't. Still stumped, for now...
You can remove it yourself through here: https://slackbuilds.org/remove/
submission MD5 should be sent to your email during submission process
Thanks Willy, I am going to remove and resubmit the ones that have template compliance errors. Sorry about that, I am trying to make as little work for you admins as necessary but mistakes happen. I'll correct them and try not to abuse the removal page .
I am a little busy with personal stuff, so if adcdam wants to be swaywm/wlroots guy for slackbuilds.org, I am fine with it.
Thanks Biker-rat i have to remove the submission of wlroots i sent because i sent wlroots 0.15 and the problem is sway 1.7 needs meson 0.60+.
sway 1.7 need wlroots 0.15+ (sway 1.7 with wlroots 0.15.1 work fine in current)
and sway 1.6.1 need version 0.14.0
i have to downgrade de slackbuilds
if you want send yours, if you are very busy let me know and i send the downgraded slackbuilds. (i can do it today)
wlroots is very important and many packages use it, like sway, river, dwl (like dwm but for wayland), wayfire and many more.
edit i deleted two submissions wlroots and river im trying to send wlroots again (this time version 0.14.1) but it say
File exists; a submission by the name 'wlroots' is already pending approval. the thing is i already deleted my previous submission. will try again tomorrow.
Swaywm will compile for 15.0 If you patch the meson.build file a teensy bit. Lower the line were minimum meson version is declared from 0.60.0 to 0.59.4(the slackversion). The build will fail with an error in line 95 because 2 arguements not supported until version 0.60.0. So,scroll down to line 95 and erase the term relating to systemd and leave the one in referring to elogind and it then compiles fine. Since 15.0 has no systemd this is probably ok patch.
Swaywm will compile for 15.0 If you patch the meson.build file a teensy bit. Lower the line were minimum meson version is declared from 0.60.0 to 0.59.4(the slackversion). The build will fail with an error in line 95 because 2 arguements not supported until version 0.60.0. So,scroll down to line 95 and erase the term relating to systemd and leave the one in referring to elogind and it then compiles fine. Since 15.0 has no systemd this is probably ok patch.
Biker rat i test a build with the modified meson build, it build fine. I sent wlroots 0.14.1 before seeing your post. i still can remove my submission and submit back wlroots 0.15 or 0.15.1 but by the way dont you prefer to send yours?
if you want i can post here the info.files and README so in case you are busy you can save time.
Please send in yours adcdam. I just had enough time to do the patch, not get whole slackbuild for swaym the way I want.
hi biker-rat i sent the sway slackbuild today, i made a patch with what you told me here. I started making slackbuilds after seeing yours my first one was river another wayland tilling windows. Kudos to you!!!
best regards!
edit: i have to send also bemenu, fuzzel, perhaps wofi those will be good for sway or other wayland tilling windows.
yambar a wayland bar
and foot a native wayland terminal.
I'm actually working on gitea-bin (gitea slackbuild with pre-compiled binary)
The gitea part (rc script) is ready and the slackbuild builds and works well
I still have the supervisor part to do
Basically, either I keep it to myself, or I can upload it to slackbuild.org
Would people be interested?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
