Re: Messed up perldoc

[Stephen Quinney]

On Sat, Sep 05, 2015 at 05:20:12PM -0700, ToddAndMargo wrote:
> On 09/05/2015 09:00 AM, Stephen Quinney wrote:
> >On Sat, Sep 05, 2015 at 04:08:13AM -0700, ToddAndMargo wrote:
> >>On 09/04/2015 11:45 PM, Stephen Quinney wrote:
> >>>The fix for that problem is to use a newer version of Pod::Perldoc. I
> >>>grabbed the SRPM for version 3.25 of perl-Pod-Perldoc from Fedora 23
> >>>and rebuilt it for SL7.
> >>>
> >>
> >># rpmbuild --rebuild perl-Pod-Perldoc-3.25-347.fc23.src.rpm
> >>...
> >>Processing files: perl-Pod-Perldoc-3.25-347.el7.noarch
> >>error: File not found: 
> >>/root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-347.el7.x86_64/usr/bin/perldoc
> >>error: File not found by glob: 
> >>/root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-347.el7.x86_64/usr/share/perl5/vendor_perl/*
> >>error: File not found by glob: 
> >>/root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-347.el7.x86_64/usr/share/man/man1/*
> >>error: File not found by glob: 
> >>/root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-347.el7.x86_64/usr/share/man/man3/*
> >>
> >
> >It looks like I used 3.25-1 which is still available on koji:
> >
> >https://kojipkgs.fedoraproject.org//packages/perl-Pod-Perldoc/3.25/1.fc22/src/perl-Pod-Perldoc-3.25-1.fc22.src.rpm
> >
> 
> Got the same stuff back.  Rats.
> 
> I wonder if the spec file has the man pages call out wrong.
> 
> RPM build errors:
> 
> File not found: 
> /root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-1.el7.x86_64/usr/bin/perldoc
> File not found by glob: 
> /root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-1.el7.x86_64/usr/share/perl5/vendor_perl/*
> File not found by glob: 
> /root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-1.el7.x86_64/usr/share/man/man1/*
> File not found by glob: 
> /root/rpmbuild/BUILDROOT/perl-Pod-Perldoc-3.25-1.el7.x86_64/usr/share/man/man3/*
> 


It builds fine for me on SL7.1, I wonder if there is a build
dependency which has not been specified in the specfile.


Stephen

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: root is unable to open display

[Tom H]

On Sun, Sep 6, 2015 at 10:04 AM, Nico Kadel-Garcia  wrote:
> On Sun, Sep 6, 2015 at 6:51 AM, Tom H  wrote:
>> On Sat, Sep 5, 2015 at 10:42 AM, Nico Kadel-Garcia  wrote:
>>> On Sat, Sep 5, 2015 at 4:52 AM, Tom H  wrote:

 systemd introduced "machinectl shell localhost" in systemd 225 that
 essentially does the same as "ssh localhost" from an env perspective.

 Since it's being rebased to 219 for SL 7.2, perhaps that command'll be
 included in SL 7.4 with a systemd 22x (or it might be backported at
 some point...).
>>>
>>> systemd's tendency to find a particular issue with a known, stable
>>> toolkit and then bolt it onto systemd is scaring the tar out of me.
>>> Attempting to replace su or sudo seems to be yet another example of
>>> this. The subject has been discussed, heatedly, in the Fedora mailing
>>> list.
>>
>> AFAIR there was a systemd-devel@ thread and various bug reports about
>> people having a problem with su/sudo when using them to launch X apps
>> because XDG_RUNTIME_DIR was the su-ing/sudo-ing user's and perms of
>> XDG_RUNTIME_DIR or of its contents were being changed to root because
>> that directory couldn't be changed within a session.
>>
>> So the problem's that su doesn't create a new login session but su was
>> never intended for this. Its man page even says "The su command is
>> used to become another user during a login session".
>
> Right. "su" doesn't. "sudo" can, by setting /etc/sudoers or
> /etc/sudoers.d options.

I don't think that sudo can create a new session where "session"
corresponds to the consolekit/logind meaning, but I'd have to read
"man sudoers" to be sure.