Re: [arch-general] teapot package could be improved

2020-04-08 Thread Jude DaShiell
that package won't even build with libtirpc though it got a little further this time. I was curious about this package but can use it on another version of Linux I run to check it out. On Wed, 8 Apr 2020, Jude DaShiell wrote: > Date: Wed, 8 Apr 2020 19:21:37 > From: Jude DaShiell > Reply-To: Ge

Re: [arch-general] teapot package could be improved

2020-04-08 Thread Jude DaShiell
thanks, I will try to take teapot further and see where it crashes. This is keenerd's package if I'm not much mistaken. If that developer is no longer in circulation maybe the package needs flagged as outdated. On Thu, 9 Apr 2020, Lone_Wolf wrote: > Date: Wed, 8 Apr 2020 19:01:06 > From: Lone_Wo

Re: [arch-general] teapot package could be improved

2020-04-08 Thread Lone_Wolf
Jude uses TalkingArch, logging in on AUR and adding comments may be near impossible. Jude, I've checked the files and it looks like teapot needs rpc/types.h and rpc/xdr.h . The libtirpc package has those files but installing it doesn't help. The sourcecode for teapot is from 2012 and the pa

Re: [arch-general] teapot package could be improved

2020-04-08 Thread brent s.
On 4/8/20 17:24, Jude DaShiell wrote: > which package has the version of rpc.h teapot needs to build? > Whichever package that is, the dependency is missing from the build > script. > You should probably instead post this on the AUR package's comment section, as it is an AUR package and the maint

[arch-general] teapot package could be improved

2020-04-08 Thread Jude DaShiell
which package has the version of rpc.h teapot needs to build? Whichever package that is, the dependency is missing from the build script. --

Re: [arch-general] rEFInd package being neglected by maintainer.

2020-04-08 Thread Mike Cloaked via arch-general
On Tue, Apr 7, 2020 at 6:55 PM mike lojkovic via arch-general < arch-general@archlinux.org> wrote: > rEFInd has had multiple versions came out, and the mainter has been > neglecting to update it for nearly two years. Is there an eta or talk of > changing the maintainer for that package? Pretty sur