Re: Packages requires /sbin/service.
On Mon, 2013-03-18 at 11:27 -0500, Rex Dieter wrote: Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Yes, they are saying it very clearly (see [1]). Because blindly doing it breaks stuff (as evidenced by this thread). I believe it is not blinded to follows packaging guidelines. I was asking a mostly rhetorical question. There's some good reasons the guidelines don't say it (yet). :) Same as above. -- rex Michal [1] http://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Michal Sekletar wrote: On Mon, 2013-03-18 at 11:27 -0500, Rex Dieter wrote: Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Yes, they are saying it very clearly (see [1]). Sigh, indeed. In addition, Fedora packages MUST NOT place files or directories in the /bin, /sbin, /lib or /lib64 directories. Instead, the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories must be used. Packages must assume that /bin, /sbin, /lib, and /lib64 are symbolic links to the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories, respectively. IMHO, this needs amending to say: In addition, *new* Fedora packages MUST NOT ... and add language to recommend taking special considering modifications of existing packages, especially those that other packages depend upon. -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Hi Rex, On Tue, 2013-03-19 at 07:57 -0500, Rex Dieter wrote: Michal Sekletar wrote: On Mon, 2013-03-18 at 11:27 -0500, Rex Dieter wrote: Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Yes, they are saying it very clearly (see [1]). Sigh, indeed. In addition, Fedora packages MUST NOT place files or directories in the /bin, /sbin, /lib or /lib64 directories. Instead, the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories must be used. Packages must assume that /bin, /sbin, /lib, and /lib64 are symbolic links to the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories, respectively. IMHO, this needs amending to say: In addition, *new* Fedora packages MUST NOT ... I would argue that this is not what should be done. Packagers should fix their packages instead of relying on the old behavior which in now basically compat only thing. Although, I don't believe it is going to happen any time soon. It is very clear to me, that there is so much opposition against UsrMove and unwillingness to fix packages. Since former is not going to happen, I would say that change as you have proposed might make sense. and add language to recommend taking special considering modifications of existing packages, especially those that other packages depend upon. -- rex Cheers, Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Am 19.03.2013 13:42, schrieb Michal Sekletar: On Mon, 2013-03-18 at 11:27 -0500, Rex Dieter wrote: Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Yes, they are saying it very clearly (see [1]) ok, so anything which refers to /bin and /sbin is a bug after the UsrMove exactly as i felt wow, there are lot of bugs over the distribution http://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout In addition, Fedora packages MUST NOT place files or directories in the /bin, /sbin, /lib or /lib64 directories. Instead, the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories must be used. Packages must assume that /bin, /sbin, /lib, and /lib64 are symbolic links to the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories, respectively signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Hi, On Mar 19, 2013, at 13:54, Reindl Harald h.rei...@thelounge.net wrote: Am 19.03.2013 13:42, schrieb Michal Sekletar: On Mon, 2013-03-18 at 11:27 -0500, Rex Dieter wrote: Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Yes, they are saying it very clearly (see [1]) ok, so anything which refers to /bin and /sbin is a bug after the UsrMove exactly as i felt wow, there are lot of bugs over the distribution I haven't said that. My point was to address the question about guidelines. http://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout In addition, Fedora packages MUST NOT place files or directories in the /bin, /sbin, /lib or /lib64 directories. Instead, the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories must be used. Packages must assume that /bin, /sbin, /lib, and /lib64 are symbolic links to the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories, respectively -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Tue, Mar 19, 2013 at 5:54 AM, Reindl Harald h.rei...@thelounge.netwrote: Am 19.03.2013 13:42, schrieb Michal Sekletar: On Mon, 2013-03-18 at 11:27 -0500, Rex Dieter wrote: Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Yes, they are saying it very clearly (see [1]) ok, so anything which refers to /bin and /sbin is a bug after the UsrMove exactly as i felt wow, there are lot of bugs over the distribution http://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout In addition, Fedora packages MUST NOT place files or directories in the /bin, /sbin, /lib or /lib64 directories. Instead, the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories must be used. Packages must assume that /bin, /sbin, /lib, and /lib64 are symbolic links to the /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64 directories, respectively -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel This might be unrelated, but the latest conversations, this on in particular, make me wonder: Did I miss a preupgrade, or is the above inquiry still focused around F18 bugs? Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Sun, Mar 17, 2013 at 8:10 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 18.03.2013 01:06, schrieb Nico Kadel-Garcia: On Sun, Mar 17, 2013 at 12:36 PM, Peter Lemenkov lemen...@gmail.com wrote: 2013/3/15 Lukáš Nykrýn lnyk...@redhat.com: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. ... rtpproxy Fixed. This is a bad, bad, bad idea for any packages that are going to remain backwards compatible with RHEL, for compilation under EPEL or other backporting. Either switch to systemd, or stick with the old location and allow initscripts to correctly include the old reference. Do not pick a hallfways fix that isn't backwards compatible at all. * Fedora has done UsrMove with F17 * Now we have F18 * in a short we have F19 * RHEL7 will be base on F18/F19 ANY reference in Fedora to /sbin and /bin is BOGUS it leads to all sorts of troubles it leads to additional symlink reslovement If SysV init style scripts are staying in use, even as a compatibility fallback, don't edit the references to them just to prove something. It breaks backporting and forward porting and cross-compatibility for every existing versoin of RHEL, which are still needed for compatibility because *systemd can't be ported back to RHEL 6 or earlier.* I've tried, it's a dependency and critical component upgrade nightmare. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Mon, Mar 18, 2013 at 5:22 AM, Reindl Harald h.rei...@thelounge.net wrote:
Am 18.03.2013 08:27, schrieb Nico Kadel-Garcia:
On Sun, Mar 17, 2013 at 8:10 PM, Reindl Harald h.rei...@thelounge.net
wrote:
Am 18.03.2013 01:06, schrieb Nico Kadel-Garcia:
On Sun, Mar 17, 2013 at 12:36 PM, Peter Lemenkov lemen...@gmail.com
wrote:
2013/3/15 Lukáš Nykrýn lnyk...@redhat.com:
After usr move packages should not install files to /sbin. Unfortunately
there is a lot of packages requiring /sbin/service, which was recently
moved
to /usr/sbin/, and these packages were uninstallable. As a workaround I
have
put Provides: /sbin/service in the initscript spec, but I think that we
should do a proper fix.
So if your package is in following list, please change your Reguires to
/usr/sbin/service.
...
rtpproxy
Fixed.
This is a bad, bad, bad idea for any packages that are going to remain
backwards compatible with RHEL, for compilation under EPEL or other
backporting. Either switch to systemd, or stick with the old location
and allow initscripts to correctly include the old reference. Do not
pick a hallfways fix that isn't backwards compatible at all.
* Fedora has done UsrMove with F17
* Now we have F18
* in a short we have F19
* RHEL7 will be base on F18/F19
ANY reference in Fedora to /sbin and /bin is BOGUS
it leads to all sorts of troubles
it leads to additional symlink reslovement
If SysV init style scripts are staying in use, even as a compatibility
fallback, don't edit the references to them just to prove something.
It breaks backporting and forward porting and cross-compatibility for
every existing versoin of RHEL, which are still needed for
compatibility because *systemd can't be ported back to RHEL 6 or
earlier.* I've tried, it's a dependency and critical component upgrade
nightmare
so what - then it needs a lot of if-clauses in the SPEC
it makes pretty no sense to wait 10 years until the
last RHEL version is on systemd and has also UsrMove
to finish this things for fedora
Yes, it means wait 10 years, just as it does for most software using
/bin/rm and /bin/mkdir. Or at least don't aggressively go update
*every single* init script using package in a way that breaks
compatibility with every older distribution for no performance gain.
Switch to systemd instead, which actually gets you an improvement.
There are examples of just how to do that in my Samba 4.0.3 backport
to RHEL 6 work at:
In particular, if you have to backport a systemd written Fedora
package to older Fedora or RHEL, use something like this from
https://github.com/nkadel/samba-4.0.3-srpm/blob/master/samba.spec.
I've somewhat simplified the example below to leave out the more
complex domain controller and winbind examples, but it's solid working
code, and I'd resent having to stuff in another set of conditionals
because the /sbin/chkconfig and /sbin/server paths, which will
remain valid, are simply not mentioned in another more basic RPM.
# Use systemd, not SysV init scripts, as appropriate
%if 0%{?fedora} 15 || 0%{?rhel} 6
%global with_systemd 1
%else
%global with_systemd 0
%endif
# RHEL specific init scripts, in case systemd not available
Source100: nmb.init
Source101: smb.init
%if %with_systemd
Requires(post): systemd
Requires(preun): systemd
Requires(postun): systemd
%else
Requires(post): /sbin/chkconfig, /sbin/service
Requires(preun): /sbin/chkconfig, /sbin/service
Requires(postun): /sbin/chkconfig, /sbin/service
%endif
%if %with_systemd
install -d -m 0755 %{buildroot}%{_unitdir}
%if %with_dc
for i in nmb smb ; do
%else
for i in nmb smb; do
%endif # with_dc
cat packaging/systemd/$i.service | sed -e
's@Type=forking@Type=forking\nEnvironment=KRB5CCNAME=/run/samba/krb5cc_samba@g'
tmp$i.service
install -m 0644 tmp$i.service %{buildroot}%{_unitdir}/$i.service
done
%else
install -d -m 0755 %{buildroot}%{_initrddir}
install -m 0755 %{SOURCE100} %{buildroot}%{_initrddir}/nmb
install -m 0755 %{SOURCE101} %{buildroot}%{_initrddir}/smb
%endif # with_systemd
%post
%if %with_systemd
%systemd_post smb.service
%systemd_post nmb.service
%else
/sbin/chkconfig --add smb
/sbin/chkconfig --add nmb
if [ $1 -ge 1 ]; then
/sbin/service smb condrestart /dev/null 21 || :
/sbin/service nmb condrestart /dev/null 21 || :
fi
%endif # with_systemd
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, 15.03.13 11:07, Dan Mashal (dan.mas...@gmail.com) wrote: On Fri, Mar 15, 2013 at 11:04 AM, Michal Schmidt mschm...@redhat.com wrote: On 03/15/2013 07:00 PM, Dan Mashal wrote: Looks like you guys added provides(service) and fixed the problem. Yes, Lukáš added it. He even mentioned it in the email that started this thread. Still it would be nice to drop legacy provide name after packages stop Requiring it. Michal Well I was reading an IRC discussion on devel. I'm like a horse with blinders. This used to work and doesn't anymore. Which leads me to my next point: What does it hurt to have the command there? In fact you should just rename systemctl service and make it understand service commands. It's annoying over all. Nope, I am pretty sure I won't add code to systemctl itself to manipulate /etc/rc.d/... It's OK to invoke service from systemctl, and that's what we do if we are run for a SysV service. It's also OK to invoke systemctl from service, and that's also what is being done. But merging the codebases, no thank you. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Am 18.03.2013 04:32, schrieb Mathieu Bridon: On Sun, 2013-03-17 at 17:31 +0100, Reindl Harald wrote: Am 17.03.2013 17:12, schrieb Sérgio Basto: On Sáb, 2013-03-16 at 19:42 +0100, Reindl Harald wrote: [root@fileserver:~]$ system-config-users The value for the SHELL variable was not found the /etc/shells file This incident has been reported [root@fileserver:~]$ cat /etc/shells /bin/sh /bin/bash /sbin/nologin [root@fileserver:~]$ cat /etc/passwd | grep root root:x:0:0:root:/root:/usr/bin/bash and if both are valid both have to be valid as shell in ANY context or anything changed to the physical location This looks like a serious bug indeed. Can you share the link to the bug report, for those of us interested in CC-ing ourselves? https://bugzilla.redhat.com/show_bug.cgi?id=922527 signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? Because blindly doing it breaks stuff (as evidenced by this thread). I was asking a mostly rhetorical question. There's some good reasons the guidelines don't say it (yet). :) -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Am 18.03.2013 08:27, schrieb Nico Kadel-Garcia: On Sun, Mar 17, 2013 at 8:10 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 18.03.2013 01:06, schrieb Nico Kadel-Garcia: On Sun, Mar 17, 2013 at 12:36 PM, Peter Lemenkov lemen...@gmail.com wrote: 2013/3/15 Lukáš Nykrýn lnyk...@redhat.com: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. ... rtpproxy Fixed. This is a bad, bad, bad idea for any packages that are going to remain backwards compatible with RHEL, for compilation under EPEL or other backporting. Either switch to systemd, or stick with the old location and allow initscripts to correctly include the old reference. Do not pick a hallfways fix that isn't backwards compatible at all. * Fedora has done UsrMove with F17 * Now we have F18 * in a short we have F19 * RHEL7 will be base on F18/F19 ANY reference in Fedora to /sbin and /bin is BOGUS it leads to all sorts of troubles it leads to additional symlink reslovement If SysV init style scripts are staying in use, even as a compatibility fallback, don't edit the references to them just to prove something. It breaks backporting and forward porting and cross-compatibility for every existing versoin of RHEL, which are still needed for compatibility because *systemd can't be ported back to RHEL 6 or earlier.* I've tried, it's a dependency and critical component upgrade nightmare so what - then it needs a lot of if-clauses in the SPEC it makes pretty no sense to wait 10 years until the last RHEL version is on systemd and has also UsrMove to finish this things for fedora signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? until now UsrMove is a half-baken thing see below - what the hell, /usr/bin/bash is a valid shell [root@fileserver:~]$ system-config-users The value for the SHELL variable was not found the /etc/shells file This incident has been reported [root@fileserver:~]$ cat /etc/shells /bin/sh /bin/bash /sbin/nologin [root@fileserver:~]$ cat /etc/passwd | grep root root:x:0:0:root:/root:/usr/bin/bash signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Sáb, 2013-03-16 at 19:42 +0100, Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? until now UsrMove is a half-baken thing No, with UsrMove you have symbol links ll / bin - usr/bin lib - usr/lib lib64 - usr/lib64 sbin - usr/sbin I'm not sure, but I'd say, you must have the symbol links. see below - what the hell, /usr/bin/bash is a valid shell [root@fileserver:~]$ system-config-users The value for the SHELL variable was not found the /etc/shells file This incident has been reported [root@fileserver:~]$ cat /etc/shells /bin/sh /bin/bash /sbin/nologin [root@fileserver:~]$ cat /etc/passwd | grep root root:x:0:0:root:/root:/usr/bin/bash -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Am 17.03.2013 17:12, schrieb Sérgio Basto: On Sáb, 2013-03-16 at 19:42 +0100, Reindl Harald wrote: Am 16.03.2013 19:26, schrieb Rex Dieter: Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? but WHY are they not saying it clearly? until now UsrMove is a half-baken thing No, with UsrMove you have symbol links ll / bin - usr/bin lib - usr/lib lib64 - usr/lib64 sbin - usr/sbin I'm not sure, but I'd say, you must have the symbol links and hwat does this change on the fact that the real location is /usr/sbin/service and /usr/bin/bash see below - what the hell, /usr/bin/bash is a valid shell [root@fileserver:~]$ system-config-users The value for the SHELL variable was not found the /etc/shells file This incident has been reported [root@fileserver:~]$ cat /etc/shells /bin/sh /bin/bash /sbin/nologin [root@fileserver:~]$ cat /etc/passwd | grep root root:x:0:0:root:/root:/usr/bin/bash and if both are valid both have to be valid as shell in ANY context or anything changed to the physical location signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
2013/3/15 Lukáš Nykrýn lnyk...@redhat.com: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. ... rtpproxy Fixed. -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. Argh, so UsrMove is STILL biting us in the rear!!! So if your package is in following list, please change your Reguires to /usr/sbin/service. [list of 91 (!) packages] And this is going to be (and remain!) a problem for every single binary. The binary can be found in both /usr/(s)bin and /(s)bin because it's now actually the same directory, but RPM thinks it only lives in either of them. It's a big mess! So who still thinks that UsrMove was a good idea??? Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Sun, Mar 17, 2013 at 12:36 PM, Peter Lemenkov lemen...@gmail.com wrote: 2013/3/15 Lukáš Nykrýn lnyk...@redhat.com: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. ... rtpproxy Fixed. This is a bad, bad, bad idea for any packages that are going to remain backwards compatible with RHEL, for compilation under EPEL or other backporting. Either switch to systemd, or stick with the old location and allow initscripts to correctly include the old reference. Do not pick a hallfways fix that isn't backwards compatible at all. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Sun, 2013-03-17 at 17:31 +0100, Reindl Harald wrote: Am 17.03.2013 17:12, schrieb Sérgio Basto: On Sáb, 2013-03-16 at 19:42 +0100, Reindl Harald wrote: [root@fileserver:~]$ system-config-users The value for the SHELL variable was not found the /etc/shells file This incident has been reported [root@fileserver:~]$ cat /etc/shells /bin/sh /bin/bash /sbin/nologin [root@fileserver:~]$ cat /etc/passwd | grep root root:x:0:0:root:/root:/usr/bin/bash and if both are valid both have to be valid as shell in ANY context or anything changed to the physical location This looks like a serious bug indeed. Can you share the link to the bug report, for those of us interested in CC-ing ourselves? -- Mathieu -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. That's not necessarily true. Do our packaging guidelines actually say that anywhere? -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Packages requires /sbin/service.
After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. Thanks Lukas acpid-sysvinit amanda-client amanda-server amavisd-new amavisd-new-snmp autofs awstats bird-sysvinit bird6-sysvinit bitlbee bluez-compat boa cacti Canna cfengine conmux crossfire-selinux cyphesis cyrus-sasl dahdi-tools dhcp_probe dkim-milter ebtables exim exim-clamav fail2ban glpi greylistd groonga-munin-plugins groonga-server-gqtp groonga-server-http horde hplip ibmasm iputils-sysvinit isdn4k-utils i8kutils keepalived koji-builder koji-vm mailman mimedefang mogilefsd mogstored moodle munin-node nessus-server node nrpe oidentd openslp-server opensm-sysv openswan orbited pathfinderd pcsc-lite-openct phpMemcachedAdmin preload prelude-correlator quagga-sysvinit ratbox-services rinetd roundup rtpproxy setroubleshoot-server sip-redirect sks smstools spamassassin spampd spawn-fcgi squid-sysvinit srptools-sysv sysklogd tftp-server ttywatch ulogd varnish vblade vsftpd-sysvinit wine-desktop xorg-x11-xfs xtide yum-cron zarafa-dagent zarafa-gateway zarafa-ical zarafa-indexer zarafa-monitor zarafa-server zarafa-spooler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, 15 Mar 2013 17:38:53 +0100
Lukáš Nykrýn lnyk...@redhat.com wrote:
After usr move packages should not install files to /sbin.
Unfortunately there is a lot of packages requiring /sbin/service,
which was recently moved to /usr/sbin/, and these packages were
uninstallable. As a workaround I have put Provides: /sbin/service in
the initscript spec, but I think that we should do a proper fix.
So if your package is in following list, please change your Reguires
to /usr/sbin/service.
To clarify, this affects only f19 and f20, right?
So,
%if 0%{?rhel} 6 || 0%{?fedora} 18
Requires: /usr/sbin/service
%else
Requires: /sbin/service
%endif
should work as a portable means of doing this?
Thanks
Lukas
kevin
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
Pá 15. březen 2013, 17:47:05 CET, Kevin Fenzi napsal:
On Fri, 15 Mar 2013 17:38:53 +0100
Lukáš Nykrýn lnyk...@redhat.com wrote:
After usr move packages should not install files to /sbin.
Unfortunately there is a lot of packages requiring /sbin/service,
which was recently moved to /usr/sbin/, and these packages were
uninstallable. As a workaround I have put Provides: /sbin/service in
the initscript spec, but I think that we should do a proper fix.
So if your package is in following list, please change your Reguires
to /usr/sbin/service.
To clarify, this affects only f19 and f20, right?
So,
%if 0%{?rhel} 6 || 0%{?fedora} 18
Requires: /usr/sbin/service
%else
Requires: /sbin/service
%endif
should work as a portable means of doing this?
Thanks
Lukas
kevin
Yes this is related to F19 and F20. But my personal opinion is, that
packages should use systemctl now anyway.
Lukas
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On 03/15/2013 05:38 PM, Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. I am very much opposed to this change. You need to keep files which are expected to be in /bin or /sbin under these paths. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, Mar 15, 2013 at 10:18 AM, Ralf Corsepius rc040...@freenet.de wrote: On 03/15/2013 05:38 PM, Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. I am very much opposed to this change. You need to keep files which are expected to be in /bin or /sbin under these paths. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Me too. Even with the switch to systemd I still use the service command, and plan to keep it that way. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On 03/15/2013 06:53 PM, Dan Mashal wrote: On Fri, Mar 15, 2013 at 10:18 AM, Ralf Corsepius rc040...@freenet.de wrote: I am very much opposed to this change. You need to keep files which are expected to be in /bin or /sbin under these paths. /sbin is a symlink to /usr/sbin, so calling /sbin/service still works. Me too. Even with the switch to systemd I still use the service command, and plan to keep it that way. Nobody's removing the command. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, Mar 15, 2013 at 10:56 AM, Michal Schmidt mschm...@redhat.com wrote: On 03/15/2013 06:53 PM, Dan Mashal wrote: On Fri, Mar 15, 2013 at 10:18 AM, Ralf Corsepius rc040...@freenet.de wrote: I am very much opposed to this change. You need to keep files which are expected to be in /bin or /sbin under these paths. /sbin is a symlink to /usr/sbin, so calling /sbin/service still works. Me too. Even with the switch to systemd I still use the service command, and plan to keep it that way. Nobody's removing the command. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Looks like you guys added provides(service) and fixed the problem. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On 03/15/2013 07:00 PM, Dan Mashal wrote: Looks like you guys added provides(service) and fixed the problem. Yes, Lukáš added it. He even mentioned it in the email that started this thread. Still it would be nice to drop legacy provide name after packages stop Requiring it. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, Mar 15, 2013 at 5:52 PM, Lukáš Nykrýn lnyk...@redhat.com wrote:
Pá 15. březen 2013, 17:47:05 CET, Kevin Fenzi napsal:
On Fri, 15 Mar 2013 17:38:53 +0100
Lukáš Nykrýn lnyk...@redhat.com wrote:
After usr move packages should not install files to /sbin.
Unfortunately there is a lot of packages requiring /sbin/service,
which was recently moved to /usr/sbin/, and these packages were
uninstallable. As a workaround I have put Provides: /sbin/service in
the initscript spec, but I think that we should do a proper fix.
So if your package is in following list, please change your Reguires
to /usr/sbin/service.
To clarify, this affects only f19 and f20, right?
So,
%if 0%{?rhel} 6 || 0%{?fedora} 18
Requires: /usr/sbin/service
%else
Requires: /sbin/service
%endif
should work as a portable means of doing this?
Thanks
Lukas
Yes this is related to F19 and F20. But my personal opinion is, that
packages should use systemctl now anyway.
Yes - if you are going to touch the spec file, migrating to native
systemctl makes much more sense.
With the existing /sbin - /usr/sbin symlinks and the Provides:
/sbin/service, replacing /sbin/service references by /usr/sbin/service
references isn't solving any user-visible problem AFAICS.
Mirek
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, Mar 15, 2013 at 11:04 AM, Michal Schmidt mschm...@redhat.com wrote: On 03/15/2013 07:00 PM, Dan Mashal wrote: Looks like you guys added provides(service) and fixed the problem. Yes, Lukáš added it. He even mentioned it in the email that started this thread. Still it would be nice to drop legacy provide name after packages stop Requiring it. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Well I was reading an IRC discussion on devel. I'm like a horse with blinders. This used to work and doesn't anymore. Which leads me to my next point: What does it hurt to have the command there? In fact you should just rename systemctl service and make it understand service commands. It's annoying over all. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On 03/15/2013 07:07 PM, Dan Mashal wrote: Well I was reading an IRC discussion on devel. I'm like a horse with blinders. This used to work and doesn't anymore. I cannot be sure, but I think you're referring here to the breakage caused by initscripts-9.45-1 due to the missing Provides: /sbin/service, but that has been added in 9.45-2. Which leads me to my next point: What does it hurt to have the command there? I was not suggesting removing the command, but merely the RPM Provides eventually. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On Fri, Mar 15, 2013 at 11:15 AM, Michal Schmidt mschm...@redhat.com wrote: On 03/15/2013 07:07 PM, Dan Mashal wrote: Well I was reading an IRC discussion on devel. I'm like a horse with blinders. This used to work and doesn't anymore. I cannot be sure, but I think you're referring here to the breakage caused by initscripts-9.45-1 due to the missing Provides: /sbin/service, but that has been added in 9.45-2. Which leads me to my next point: What does it hurt to have the command there? I was not suggesting removing the command, but merely the RPM Provides eventually. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Thanks for clarification. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On 15/03/13 11:07 AM, Dan Mashal wrote: On Fri, Mar 15, 2013 at 11:04 AM, Michal Schmidt mschm...@redhat.com wrote: On 03/15/2013 07:00 PM, Dan Mashal wrote: Looks like you guys added provides(service) and fixed the problem. Yes, Lukáš added it. He even mentioned it in the email that started this thread. Still it would be nice to drop legacy provide name after packages stop Requiring it. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Well I was reading an IRC discussion on devel. I'm like a horse with blinders. This used to work and doesn't anymore. Which leads me to my next point: What does it hurt to have the command there? In fact you should just rename systemctl service and make it understand service commands. It's annoying over all. Yes, well, the 'horse with blinkers' thing is kind of annoying sometimes. This has nothing to do with the thread. If you want to propose stuff like that, please do it in a separate thread, but it's really not very likely to happen. This thread was a very simple request for a simple spec change which has now gotten derailed into yet another systemd bikeshed. Sigh. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packages requires /sbin/service.
On 03/15/2013 10:38 AM, Lukáš Nykrýn wrote: After usr move packages should not install files to /sbin. Unfortunately there is a lot of packages requiring /sbin/service, which was recently moved to /usr/sbin/, and these packages were uninstallable. As a workaround I have put Provides: /sbin/service in the initscript spec, but I think that we should do a proper fix. So if your package is in following list, please change your Reguires to /usr/sbin/service. Thanks Lukas fail2ban Finally moved this to systemd for F19+ -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
