Re: [Slackbuilds-users] Concerning 15.0 and 14.2
Luveh Keraph <1.41...@gmail.com>, 1 Şub 2022 Sal, 23:44 tarihinde şunu yazdı: > There have been no updates to any Slackbuilds packages for 14.2 for many > months now - I guess that we all thought that 15.0 would be released > earlier than in fact it will, whenever that happens. My guess is that, > shortly after this release hits the street, normal updating activity will > start for Slackbuilds packages for 15.0. What happens to 14.2? No > Slackbuilds packages for 14.2 will be updated any more? > > 14.2 will be frozen after 15's release. But that is not really official. As others said, most of us won't have time to update. HOwever, I know a lot of us will leave up to date 14.2 when the official freeze is lifted. Regards, Ozan ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Concerning 15.0 and 14.2
On Tue, 1 Feb 2022, King Beowulf wrote: After that message there was "Hey, my shiny brass lamp is almost out of fuel!" Hopefully "real soon now!" Ed, I saw that the cave was closed (is that the home of the Clan of the Cave Bear?) and that his shiny brass lamp was low on fuel but they meant nothing to me as I haven't followed the developer's jargon. And chaning the output to pulse and killing the mics fixed the problem. Thanks, Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Concerning 15.0 and 14.2
On 2/1/22 14:34, Arnaud via SlackBuilds-users wrote: > Well, Pat did write in this morning changelog « The cave is now closed ». > We are at 15.0 RC3. After that message there was "Hey, my shiny brass lamp is almost out of fuel!" Hopefully "real soon now!" -KB OpenPGP_signature Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Concerning 15.0 and 14.2
Well, Pat did write in this morning changelog « The cave is now closed ». We are at 15.0 RC3. We may have jumped ship a bit early last year, but it might not be long before 15.0 is out... - Yth. > OK, thanks. No slur implied - it's just that I have a number of 14.2 > systems, and I needed this information to decide if and when I will upgrade > them to 15.0 once it is available. > > On Tue, Feb 1, 2022 at 1:51 PM B Watson wrote: > > > On 2/1/22, Luveh Keraph <1.41...@gmail.com> wrote: > > > > > What happens to 14.2? No Slackbuilds packages for 14.2 will be updated > > any more? > > > > Correct. 14.2 slackbuilds.org branch is already considered frozen, > > not getting updated. We just don't have the time/energy/resources to > > keep updating builds for previous versions. The same thing happened > > before 14.2 was released, at some point we stopped updating for 14.1 > > and started gearing up for 14.2 (at which time, the submission form > > was closed, just like it is now). > > > > From a user's perspective, it might look like we jumped the gun and > > started updating everything for -current a bit too early... but it's > > been (and still is) a lot of work to get everything ready for 15.0. > > > > Remember we are a small team of unpaid volunteers... > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Concerning 15.0 and 14.2
OK, thanks. No slur implied - it's just that I have a number of 14.2 systems, and I needed this information to decide if and when I will upgrade them to 15.0 once it is available. On Tue, Feb 1, 2022 at 1:51 PM B Watson wrote: > On 2/1/22, Luveh Keraph <1.41...@gmail.com> wrote: > > > What happens to 14.2? No Slackbuilds packages for 14.2 will be updated > any more? > > Correct. 14.2 slackbuilds.org branch is already considered frozen, > not getting updated. We just don't have the time/energy/resources to > keep updating builds for previous versions. The same thing happened > before 14.2 was released, at some point we stopped updating for 14.1 > and started gearing up for 14.2 (at which time, the submission form > was closed, just like it is now). > > From a user's perspective, it might look like we jumped the gun and > started updating everything for -current a bit too early... but it's > been (and still is) a lot of work to get everything ready for 15.0. > > Remember we are a small team of unpaid volunteers... > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Concerning 15.0 and 14.2
On 2/1/22, Luveh Keraph <1.41...@gmail.com> wrote: > What happens to 14.2? No Slackbuilds packages for 14.2 will be updated any > more? Correct. 14.2 slackbuilds.org branch is already considered frozen, not getting updated. We just don't have the time/energy/resources to keep updating builds for previous versions. The same thing happened before 14.2 was released, at some point we stopped updating for 14.1 and started gearing up for 14.2 (at which time, the submission form was closed, just like it is now). >From a user's perspective, it might look like we jumped the gun and started updating everything for -current a bit too early... but it's been (and still is) a lot of work to get everything ready for 15.0. Remember we are a small team of unpaid volunteers... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Concerning 15.0 and 14.2
On 01/02/22 13:44, Luveh Keraph <1.41...@gmail.com> put forth the proposition: > There have been no updates to any Slackbuilds packages for 14.2 for many > months now - I guess that we all thought that 15.0 would be released > earlier than in fact it will, whenever that happens. My guess is that, > shortly after this release hits the street, normal updating activity will > start for Slackbuilds packages for 15.0. What happens to 14.2? No > Slackbuilds packages for 14.2 will be updated any more? Hi Luveh - yeah, 14.2 is frozen now. Updates and submissions will resume with the 15.0 release. -- Dave ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Concerning 15.0 and 14.2
There have been no updates to any Slackbuilds packages for 14.2 for many months now - I guess that we all thought that 15.0 would be released earlier than in fact it will, whenever that happens. My guess is that, shortly after this release hits the street, normal updating activity will start for Slackbuilds packages for 15.0. What happens to 14.2? No Slackbuilds packages for 14.2 will be updated any more? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] duplicated PRGNAM cryptography
On Tuesday, 1 February 2022 16:17:37 CET Ruben Schuller wrote: > Hi list, > > just wanted to drop a note about this, as it probably will generate > problems: > > % grep -R 'PRGNAM="cryptography"' > python/cryptography/cryptography.info:PRGNAM="cryptography" > python/python2-cryptography/python2-cryptography.info:PRGNAM="cryptography" Fixed in my branch. Thanks! :) Grs, Heinz signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] duplicated PRGNAM cryptography
Hi list, just wanted to drop a note about this, as it probably will generate problems: % grep -R 'PRGNAM="cryptography"' python/cryptography/cryptography.info:PRGNAM="cryptography" python/python2-cryptography/python2-cryptography.info:PRGNAM="cryptography" Cheers Ruben ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Epson M105 printer with PPD on CUPS (it was Re: Howto for slackware tgz)
the two printer packages at sbo are epson-inkjet-printer-escpr and epson-inkjet-printer-escpr2 and cater for printers that use the different protocol versions. the m100 series was last supported in 2012, so it must be a really old model. It is not listed in either of the current driver packages available. you'll need to create a package based on epson-inkjet-printer-201215w-1.0.0-1lsb3.2.src.rpm from epson. you can use rpm2tgz to convert the source package to something more useful. If you look at either of the two epson printer packages available, it will give some pointers to getting epson source code to compile. If you are successful, you should end up with the ppd files and the back-end as well. Be prepared for an uphill task. regards, Tim On 01/02/2022 02:01, Beco via SlackBuilds-users wrote: Dear Donald Laster, Jeremy, Chris and Kris, Sorry for the late reply, I was unable to test all the options you gave, due to some health problems. I'm back trying to install the printer. To recap: I have a epson M105 via wifi that I use with other multiple devices, android, linux, etc. (all working.) Now I'm trying to add Slackware to the pool. -- On Sat, 15 Jan 2022 , Donald R Laster Jr wrote: Bèco, Regardless of how you have the printer attached, network or direct, you should be able to use CUPS to setup the printer if CUPS supports the printer. The first thing to do is to insure that you have CUPS running. Make sure that /etc/rc.d/rc.cups is executable and you have started the CUPS daemon. [...cut...] Sincerely, Donald R Laster Jr -- On Wed, 12 Jan 2022 at 23:38, Christoph Willing wrote: On 13/1/22 11:39, Beco via SlackBuilds-users wrote: Hi Jeremy, hi Chris, Thanks for the tips, guys. I'll take a look at every link. Currently I'm having trouble with my printer, Epson M105, and I'm trying to adapt source code from drivers I've found in "src.rpm" to slackware package format. Have a look at: https://slackbuilds.org/repository/14.2/system/epson-printer-utility/ whose README.models claims to support the M105 Series (and is based on a src.rpm too). chris -- The Slackware experience for this specific printer is not the best. I'm trying to configure a new server using Slackware and it is a first attempt after a lifetime away from this distro that I love. (It was my first distro in 1998/1999). So, lets give it a try. I tried to install the "14.2 > System > epson-printer-utility (1.1.1) " (I'm on Slackware Current), and it didn't compile. After some tweeks, I got it to compile with errors but didn't work. Anyway: I was not that much upset, since this is not the path I would prefer to take. I don't need the utility, the monitor, ink levels, nozzles checks, etc. I can skip all that. In all my other linuxes, it is enough a PPD file that I have, and CUPS. And that is it. so, i tried the other path I am more familiar, just to install the printer with PPD. CUPS detected it with a lpd://localhost:port and also I can connect with socket://localhost:port. So, these 2 options can "see" the printer and send "test pages", but all end up as garbage. The PPD file I have that I used in many systems, passing from one to another and it always worked, don't work anymore. I noticed that it gives this error: Idle - "File "/opt/epson-inkjet-printer-201215w/cups/lib/filter/epson_inkjet_printer_filter" not available: No such file or directory" I have tried to compile this filter from many sources, RPM, Debian, Slackbuilds, but I can't find a way to make this filter work. For now, my hope is that the maintainer of the Slackbuilds packages that may offer this would make it updated for slackware-current. Donald, I completely agree with you. Regardless how the printer is connected, if CUPS is working, and I have the PPD, the printer should work fine. I guess this PPD I have is not well suited to the PATH of slackware filters. Maybe a small adjustment, or to find if the printer can work with another filter that comes with CUPS , that could work. Thanks for now, I'll keep trying and keep you guys posted. Cordially, Bèco -- This email has been checked for viruses by AVG. https://www.avg.com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
