Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
On Wed, 30 Nov 2016, Klaus Ethgen wrote: > No, it worked well for decades and it was exactly why you have small > root and resizable /usr on other medias. It worked because of extraordinary effort by DDs to continuously migrate libraries from /usr to / any time a binary or library in /bin, /sbin, or /lib grew a new feature. And that's not why it existed in the first place, either. See: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html And you can still have them split; you just need an initrd. You can even use something tiny, like: https://github.com/chris-se/tiny-initramfs > It start getting broken when systemd start taking over the world. Correlation is not causation. It has been broken multiple times over the past two decades. Debian has just stopped supporting it after the switch to systemd. > Well, why should it have too many changes? It works great. And it is > that well-hung that there is simply not to much to change. If that's the case, you'd think that someone who actually wanted SysV to be supported going forward would step up and maintain it. But no one has. So either it's not such a small amount of work, no one who can do the work is interested in maintaining SysV any longer, or no one knows that they should be doing the work. This is Debian. If you want SysV maintained, you should do the work. -- Don Armstrong https://www.donarmstrong.com 2: There is no out. There is only in. -- "The Prisoner (2009 Miniseries)" ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
On Wed, Nov 30, 2016 at 09:45:08AM +0100, Klaus Ethgen wrote: > Am Mi den 30. Nov 2016 um 9:36 schrieb Julian Andres Klode: > > In your imagination, that is (yes, I too can write stupid replies > > without any arguments - but I actually can provide arguments too, > > see below). > > Thanks for insulting me. (I do not really care but it is good when it > goes against the users but it is bad when it is against DDs?) I did not insult you. I just wrote that you make claims without any arguments that do not match reality. In contrast, I demonstrated that your claims are false and have shown how initramfs is a superior solution compared a stand-alone root filesystem. > > [systemd religiosity] > > Just accept reality and move on. > > That would mean to let debian die in its religious systemd world? It has absolutely nothing to do with systemd. > > > There is no reason to try to keep that separate / madness up anymore: > > > > (1) we have better solutions now > > Seems to be no. I have given you one reasonable argument that we do have a better solution with initramfs and proved that it solves all problems that existed with a separate /usr partition. > > > (2) nobody really uses the it -> no testing > > I didn't know that my name is nobody. And I also didn't know that I > share this name with many others. Your name is not nobody. There might be a modest minority of users that use a separate /usr without an initramfs. Standard Debian installations use initramfs since a very long time. And as so often, this stuff breaks. And if it is not used by the people doing the uploads (and this is a huge group of people), the chance that it will break installations without anyone noticing early is huge. > It is just in your limited reality where it is "alternativlos", just to > qoute chancellor Merkel. eww. -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
Hello Martin, Martin Steigerwald [2016-11-30 9:20 +0100]: > Also agreed to that… libsystemd is almost one third of the size of libc6.so > here… and it seems upstream basically stuffes *everything* into it, including > reading process attributes that IMHO would be a task for a *different* shared > object like the much lighter libprocps.so.6.0.0. > > But the discussion would need to be brought upstream Please let me clarify that you are talking about two different issues: 1. libsystemd being too big, which is the part which can and should be discussed on the upstream systemd list indeed, as that's not something which is appropriate to change downstream. But this is entirely unrelated to this bug report. I sympathize with this, and maybe the earlier split into three smaller libraries was the better choice. And if someone refrains from starting the discussion with a tone like "you guys suck, break everything, and want to dominate the world", it might even be successful :-) (please forgive me the exaggeration) 2. Debian supporting separate /usr without an initrd, and by extension, if boot-critical bits can link to stuff in /usr, which this bug is about. This is entirely a downstream Debian packaging issue (we could move liblz4 to /lib, like we did with other libraries), and does not belong on an upstream ML. Personally I think this part is a lost cause, both for technical reasons that have existed for a long time (which I will not repeat here), and even more so because the ongoing move to the /usr merge will make this completely obsolete -- if the *entire* OS is in /usr, then there is no alternative to an initrd anyway. This will finally make the whole design simpler, robust, maintainable, and reduce combinatorial explosion. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mi den 30. Nov 2016 um 9:36 schrieb Julian Andres Klode: > In your imagination, that is (yes, I too can write stupid replies > without any arguments - but I actually can provide arguments too, > see below). Thanks for insulting me. (I do not really care but it is good when it goes against the users but it is bad when it is against DDs?) [systemd religiosity] > Just accept reality and move on. That would mean to let debian die in its religious systemd world? > There is no reason to try to keep that separate / madness up anymore: > > (1) we have better solutions now Seems to be no. > (2) nobody really uses the it -> no testing I didn't know that my name is nobody. And I also didn't know that I share this name with many others. It is just in your limited reality where it is "alternativlos", just to qoute chancellor Merkel. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg+kY0ACgkQpnwKsYAZ 9qzRxgv/Yv2pUPnreIkk/GrZ1nQ3x8dMLM1ASlWpov1lU0vacx2jMOqWho3Oyol9 oliRw/greuTuEHWhnjRYSSp6LvJjbrhK1zGxwOfo7m9PV9NKnsbkgsDsfpYwVgLD yMNklpVaIa/l8X4/av+vGKIGcPovDhOGDzr5md3wvSNmddafEaiL+uK/BygTvDjk wCNOX5mneRHR4ZNcjN7hqzJUTYZ8bYUJPTLl9/6abVfFg1jkzEwloR04znv0iPY+ Zl9oIvJo6Ov/T4kMdKkS8BkdMMS9E5jjH+LZ6BYaVyS2nwV6usc9KrfViDdxeEDn xCa+PXQxyTEa5XUUc1b8lh+dj1V1u+HJUvj1rinr8Ig/SB+yaWFy5X1nfw/glF1c k9SRWWW1bGEPQgQPt7sUhu/FLHz/w7synK8YvFZjZqx1ws2aXuB++z6d/bZFlsLE +lAu6DeObAlmQx0h9eIVbR5i6KEppvJHT5Vzkoz4RX7FF81g8UUui1H0eXo/blia RYV3enkz =XJVt -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
(Huh, all emails are CCing listmaster - let's drop them for this subthread for now.) On Wed, Nov 30, 2016 at 07:46:31AM +0100, Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi Martin, > > Am Di den 29. Nov 2016 um 22:36 schrieb Martin Pitt: > > Cristian Ionescu-Idbohrn [2016-11-29 22:16 +0100]: > > > Eversince systemd came about into debian, you've shown direct or > > > indirect disrespect, IMO, to people objecting against screwing up > > > their systems, where they want to keep sysv instead of adopting > > > systemd world domination. > > > > The root issue here is not about the init system, but how initramfses > > and separate partitions play together. Separate /usr without an initrd > > has always been slightly broken, > > No, it worked well for decades and it was exactly why you have small > root and resizable /usr on other medias. In your imagination, that is (yes, I too can write stupid replies without any arguments - but I actually can provide arguments too, see below). > > It start getting broken when systemd start taking over the world. > > > So, the set of what can be supported is certainly debatable, but as > > history has shown it neither makes sense to support this use case nor > > did anyone manage to actually do it. Hence the "wontfix". > > As history shows, that is common use case and makes fully sense. It used to make sense, but it never really worked, as you cannot make a reasonable static decision as to what goes into / vs /usr. And thus, some people had stuff like network they needed for mounting /usr or otherwise early in boot, but the binaries for that happened to be in /usr. *All* these problems were solved with the introduction of initramfs, which allows us to make the decision as to a minimal root filesystem dynamically on the actual system. Why maintain a second solution that is a lot of work, (because it) always breaks, and only solves a small subset of the problems? > > > Also, *if* you want to make this about systemd vs. SysV again: > > Well, systemd, or better the religiosity, systemd is spread, is part of > this particular problem. Exactly that is the case, why so many users > oppose systemd. > > However, this should be fight somewhere else. Here we have a real > problem, that is easily fixable. Look at devuan or debian jessie. Just > do not link against libsystemd what pulls in too many uncontrollable > dependencies. Just accept reality and move on. There is no reason to try to keep that separate / madness up anymore: (1) we have better solutions now (2) nobody really uses the it -> no testing -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
Am Mittwoch, 30. November 2016, 07:46:31 CET schrieb Klaus Ethgen: > > Also, *if* you want to make this about systemd vs. SysV again: > Well, systemd, or better the religiosity, systemd is spread, is part of > this particular problem. Exactly that is the case, why so many users > oppose systemd. I fully agree with that. As I pointed out before the fuss about systemd is not just technical, it is a social issue with the way upstream receives and reacts to any kind of feedback that criticizes the way systemd goes about things. > However, this should be fight somewhere else. Here we have a real > problem, that is easily fixable. Look at devuan or debian jessie. Just > do not link against libsystemd what pulls in too many uncontrollable > dependencies. Also agreed to that… libsystemd is almost one third of the size of libc6.so here… and it seems upstream basically stuffes *everything* into it, including reading process attributes that IMHO would be a task for a *different* shared object like the much lighter libprocps.so.6.0.0. But the discussion would need to be brought upstream, it just seems that these days no one dares to do that. I am not keen to subscribe to systemd-devel mailing list ever again after my last attempt to channel user feedback to this list and having been attacked with "now you are being a dick" by Lennart personally who on the other side rightfully complained about being attacked in person himself. (I unsubscribed from debian-devel mailing list back then for similar reasons.) There is a split in the community that has never been healed, people just try to ignore it, but I doubt that this bug report would be the right place to go about this. And I wonder whether there is someone who would muster to bring up the courage to bring this up with upstream again in a constructive way. Closing with a note to Michael: I learned to know you at DebConf 2016 and I value your work. However I didn´t see what you called an ad hominen attack as actually being one. (I may refrain from any further comment here as I think its not really the place to discuss it.) Thank you, -- Martin ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Martin, Am Di den 29. Nov 2016 um 22:36 schrieb Martin Pitt: > Cristian Ionescu-Idbohrn [2016-11-29 22:16 +0100]: > > Eversince systemd came about into debian, you've shown direct or > > indirect disrespect, IMO, to people objecting against screwing up > > their systems, where they want to keep sysv instead of adopting > > systemd world domination. > > The root issue here is not about the init system, but how initramfses > and separate partitions play together. Separate /usr without an initrd > has always been slightly broken, No, it worked well for decades and it was exactly why you have small root and resizable /usr on other medias. It start getting broken when systemd start taking over the world. > So, the set of what can be supported is certainly debatable, but as > history has shown it neither makes sense to support this use case nor > did anyone manage to actually do it. Hence the "wontfix". As history shows, that is common use case and makes fully sense. > Also, *if* you want to make this about systemd vs. SysV again: Well, systemd, or better the religiosity, systemd is spread, is part of this particular problem. Exactly that is the case, why so many users oppose systemd. However, this should be fight somewhere else. Here we have a real problem, that is easily fixable. Look at devuan or debian jessie. Just do not link against libsystemd what pulls in too many uncontrollable dependencies. > Pleeease step up and maintain SysV init. For all those vocal people > who lobbied for it there has been remarkably little action to show for > it (read: zero): > > https://anonscm.debian.org/cgit/collab-maint/sysvinit.git/log/ Well, why should it have too many changes? It works great. And it is that well-hung that there is simply not to much to change. But yes, there could be some bug mitigation. I just wounder, how frustrated the sysvinit people are about the stuff, systemd people break everyday. I snip out the rest as, even if it is fully true and describe the problem well, it is not about this particular bug. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg+dcEACgkQpnwKsYAZ 9qzMMQwAh+45TIprZ3unyf6Z32LIWfVIQZZAYmjGnPt/swYt9t0Lpa3rVBuoG9Vo TgbKeFiZUTaYV2mZSgSfxSz8zogLPQJWDlrjghv7QA6wTQeRJEP+ZR5yp03Olgmm BdRmuTrzpXOoTFEWLUo8pSpOfblX/G/ltpYd/JjWlBqYJKZvjILAV1VUTvb61ll4 La5WIW6DKIMm4s5LruhAX3zcw05/0g3zqum1ReGxgltVaGlZ36WLW+FoIJ9pfW8c YlUc/1Hi+/osirOzUOoH4hJbaoBJvNPUCoQHFx6eagaf17U5B0TpnGbrLqm8lysm hQCcD5myKx/02Z4UMxnToVaUw+T9FAveCNJ7U378OylL7O87SzWYa5GVcXM6oNYM wjluGGO29g2Ifzhw8X5T3X7WTULZS4qttWSoUJ/JE7Qx7e/9+Vd51zHXXrCciQbl eBrZpSBM53Ebk5zC7mqJcECBoUkJ/Gb0Y33T/ESYF8/05zRUp6DSqn8KrVFkX7gk jTaCUdZc =vHKA -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
Hello Christian, Cristian Ionescu-Idbohrn [2016-11-29 22:16 +0100]: > Eversince systemd came about into debian, you've shown direct or > indirect disrespect, IMO, to people objecting against screwing up > their systems, where they want to keep sysv instead of adopting > systemd world domination. The root issue here is not about the init system, but how initramfses and separate partitions play together. Separate /usr without an initrd has always been slightly broken, and it is simply not realistic to assume that every corner case which once worked for someone can be indefinitively be "supported". Combinatorial explosion and all. So, the set of what can be supported is certainly debatable, but as history has shown it neither makes sense to support this use case nor did anyone manage to actually do it. Hence the "wontfix". Also, *if* you want to make this about systemd vs. SysV again: Pleeease step up and maintain SysV init. For all those vocal people who lobbied for it there has been remarkably little action to show for it (read: zero): https://anonscm.debian.org/cgit/collab-maint/sysvinit.git/log/ Note that the last maintainer upload was two years ago, the rest were some "life support" NMUs, most/all of them from the systemd maintainers. > Arguably, a comment like this: > > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836362#29 > > is somewhat over the edge. Still, it shows the top of the iceberg, > IMO. There's a non-ignorable minority who _still_ don't see systemd > as progress and are not willing to adopt it. What is really your > personal mission, I wonder? Are you sure that this is the right bug? #836362 has absolutely *nothing* to do with anything here. > Now, what I hope for is that you will show more respect in your > comments for those who have not yet "seen the light" [...] Pretty please: We all do this voluntarily. Tossing in comments like this will *not* help to raise attention if/once you come up with a legit problem. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
On Sun, 27 Nov 2016, Michael Biebl wrote: > Am 27.11.2016 um 12:32 schrieb Klaus Ethgen: > > Am So den 27. Nov 2016 um 11:56 schrieb Michael Biebl: > >> We no longer support a split /usr which is not pre-mounted in the > >> initramfs. > > > >> So you either have two options: > >> 1/ Don't use a split /usr > >> 2/ Use an initramfs to mount /usr > > > > And yes, there are still use cases where a separate /usr makes fully > > sense. Even if you cannot imagine that in your gated reality. > > I consider this an adhominem attack and I would appreciate if you stop that. > This is not the first time [1], so I've CCed the listmasters and bts admins. Eversince systemd came about into debian, you've shown direct or indirect disrespect, IMO, to people objecting against screwing up their systems, where they want to keep sysv instead of adopting systemd world domination. Arguably, a comment like this: > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836362#29 is somewhat over the edge. Still, it shows the top of the iceberg, IMO. There's a non-ignorable minority who _still_ don't see systemd as progress and are not willing to adopt it. What is really your personal mission, I wonder? Now, what I hope for is that you will show more respect in your comments for those who have not yet "seen the light" systemd brings to to debian, and also care about the blessings of non-systemd systems bring to people. Bottom line. What you're doing looks more and more religious, _not_ free, with or without the consent of the debian (free)? organisation. Cheers, -- Cristian ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am So den 27. Nov 2016 um 11:56 schrieb Michael Biebl: > We no longer support a split /usr which is not pre-mounted in the initramfs. > > So you either have two options: > 1/ Don't use a split /usr > 2/ Use an initramfs to mount /usr 1. I do not use systemd. 2. I have a kernel with no initrd and 3. That is a problem of udev not able to find what to mount. Sorry to have to say that. Your answer is expected and unusefull as usually. Please stop breaking all stuff with the aggressive systemd forcing! Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg6xbwACgkQpnwKsYAZ 9qwugQv/brhZRiV9O/8L9HuSjnz37KmLkoK2s0V0YQhzEfFustouyNc0nuTcLu6x gFnwaJwqBdMzvGEeZCvdtuQgBKVqiPiy32NnubJ5HXCbwB7iL71y45XxpnnVc2pb bSS0F1ZT1GCshwCmf0tcMoILcXM37Pk2cUMUzo2yDA5ZPJg5a6NSkVJkAvqsGwag DPXGGLSmT336a0rxXkD6JauYXIi/fEPsNSe9+z20UEgdw5tgmm3Z5l0JOX4VfFLF GXHcIfF6WubApJGpAoI6lFWRQ7wSLSDLpUdUwclTs00h89IihnuhL7FN752m/mvK SRAZxA4aHG3sp3GM5Yr8qvYw1TbFtKZF4Y2z1/zuqbo473PeOOI0UivVu198qcyd MfbCoCzzWTkUx6z8wa8oWlWuDPp4a5MUqeVgxnBXuglY0mFD3NsTOpU7qno5PGkl QIt3iK1YbrdxrUD0Lwmnbh+5pQ1cbo5yO+F7RsRv4f/NAJTzJ1DaSbqoijy1SaIR EuCLP6h1 =flvL -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
There are several fields that a process can have that are obtained from the systemd library. man ps and search for systemd shows them all but the ones I noticed were machine, lsession, ouid, seat and slice that come to mind. On Sun, Nov 27, 2016 at 9:41 PM Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hello Craig, > > Am So den 27. Nov 2016 um 11:12 schrieb Craig Small: > > There is a reason for linking to libsystemd and it is to do with > accessing > > the systemd type parameters that can be applied to a process. > > But what has ps to do with such a parameter? That might be of concern > for systemdctl but surelly not for ps. > > Regards >Klaus > - -- > Klaus Ethgen http://www.ethgen.ch/ > pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen > Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C > -BEGIN PGP SIGNATURE- > Comment: Charset: ISO-8859-1 > > iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg6uEkACgkQpnwKsYAZ > 9qyqhgwAmr/PF+tUP9VIkPWjHKZVqCi8T7XHNEfSY6WnmSQaCANZ5iGJ/EhG+Gba > r44kzBUNfljnyLZL6a6mYsodRzbP8TaASSMomEAUqaq7m83ElUoLOBSGlXdmpC/X > PXhFgU4/sX8lBSbEy5u8VCvGNn8fs9A3jdCycgrgSvkafeSONJaDEY7TJukpZ+JN > cBUsXBciXTg2jiMJdeSHIQakOQSAjMPJpnWrUNVG7dZxhIp6k8gZcfBh35hyHCay > h7MkwaV61z40Isk4cL6VrX2iz5zfXoOUUxMNXg7V8X7OsWmZR8hU//m8hwpfQ5/p > cVBuJo8/ucfwtovNPEKdQ/6AwhOOJrm22Gl1JIVORJQaw6LaSYJQ39t8bycadiH8 > yTf32OwjNHKiA90peAdmA/U2qNHMT3BsTtpXkx0tC9vDj2UdS456sGo+dp3kiZ9v > WHhNq+Fqkc0lXzubs9OY5gH+D+uVTZmTZxyHJpGIetoHdRRprjufHJbZfXOm1oPQ > lZ1Aq03n > =szmR > -END PGP SIGNATURE- > ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Craig, Am So den 27. Nov 2016 um 11:12 schrieb Craig Small: > There is a reason for linking to libsystemd and it is to do with accessing > the systemd type parameters that can be applied to a process. But what has ps to do with such a parameter? That might be of concern for systemdctl but surelly not for ps. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlg6uEkACgkQpnwKsYAZ 9qyqhgwAmr/PF+tUP9VIkPWjHKZVqCi8T7XHNEfSY6WnmSQaCANZ5iGJ/EhG+Gba r44kzBUNfljnyLZL6a6mYsodRzbP8TaASSMomEAUqaq7m83ElUoLOBSGlXdmpC/X PXhFgU4/sX8lBSbEy5u8VCvGNn8fs9A3jdCycgrgSvkafeSONJaDEY7TJukpZ+JN cBUsXBciXTg2jiMJdeSHIQakOQSAjMPJpnWrUNVG7dZxhIp6k8gZcfBh35hyHCay h7MkwaV61z40Isk4cL6VrX2iz5zfXoOUUxMNXg7V8X7OsWmZR8hU//m8hwpfQ5/p cVBuJo8/ucfwtovNPEKdQ/6AwhOOJrm22Gl1JIVORJQaw6LaSYJQ39t8bycadiH8 yTf32OwjNHKiA90peAdmA/U2qNHMT3BsTtpXkx0tC9vDj2UdS456sGo+dp3kiZ9v WHhNq+Fqkc0lXzubs9OY5gH+D+uVTZmTZxyHJpGIetoHdRRprjufHJbZfXOm1oPQ lZ1Aq03n =szmR -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#845480: /bin/ps depends on /usr/lib/... which makes the system unbootable
Processing commands for cont...@bugs.debian.org: > reassign 845480 libsystemd0 232-6 Bug #845480 [procps] /bin/ps depends on /usr/lib/... which makes the system unbootable Bug reassigned from package 'procps' to 'libsystemd0'. No longer marked as found in versions procps/2:3.3.12-2 and procps/2:3.3.12-3. Ignoring request to alter fixed versions of bug #845480 to the same values previously set Bug #845480 [libsystemd0] /bin/ps depends on /usr/lib/... which makes the system unbootable Marked as found in versions systemd/232-6. > retitle 845480 libsystemd links to libraries in /usr Bug #845480 [libsystemd0] /bin/ps depends on /usr/lib/... which makes the system unbootable Changed Bug title to 'libsystemd links to libraries in /usr' from '/bin/ps depends on /usr/lib/... which makes the system unbootable'. > affects 845480 procps Bug #845480 [libsystemd0] libsystemd links to libraries in /usr Added indication that 845480 affects procps > thankyou Stopping processing here. Please contact me if you need assistance. -- 845480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers