Martin Steigerwald wrote:
> Marco d'Itri - 23.12.18, 22:30:
>> On Dec 23, Martin Steigerwald wrote:
>>> I think I have seen this with either SLES or RHEL that they created
>>> symlinks for every binary in /bin and /sbin, pointing to the binary
>>> in /usr/bin and /usr/sbin. I did not understand
On Sat, Dec 22, 2018 at 10:11:53AM -0800, Josh Triplett wrote:
> Please note in the following mail that I'm raising this *exclusively* as a
> policy and procedures issue, *not* a technical issue. I would request that
> people *please* focus on the policy and procedures issue, and keep any
> propos
On Sunday, December 23, 2018 08:56:02 PM Thorsten Glaser wrote:
> Sean Whitton dixit:
> >2.3 & 4.5
> >
> >In cases where a package's distribution license explicitly permits
> >its copyright information to be excluded from distributions of
> >binaries built from the source, a verbatim co
Marco d'Itri - 23.12.18, 22:30:
> On Dec 23, Martin Steigerwald wrote:
> > I think I have seen this with either SLES or RHEL that they created
> > symlinks for every binary in /bin and /sbin, pointing to the binary
> > in /usr/bin and /usr/sbin. I did not understand why at the time I
> > have seen
On Dec 23, Martin Steigerwald wrote:
> I think I have seen this with either SLES or RHEL that they created
> symlinks for every binary in /bin and /sbin, pointing to the binary in
> /usr/bin and /usr/sbin. I did not understand why at the time I have seen
> this.
Definitely not RHEL, maybe you a
Thorsten Glaser writes:
> Sean Whitton dixit:
>>2.3 & 4.5
>>In cases where a package's distribution license explicitly permits
>>its copyright information to be excluded from distributions of
>>binaries built from the source, a verbatim copy of the package's
>>copyright informatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Sean Whitton dixit:
>2.3 & 4.5
>In cases where a package's distribution license explicitly permits
>its copyright information to be excluded from distributions of
>binaries built from the source, a verbatim copy of the package's
>cop
Guillem Jover - 23.12.18, 17:17:
> On Sun, 2018-12-23 at 16:45:28 +0100, Guillem Jover wrote:
> > On Sun, 2018-12-23 at 04:06:14 +0100, Guillem Jover wrote:
> > > […] They also imply to permanently suffer the aliasing problems.
> >
> > To expand and clarify a bit on this. We have aliasing in gener
Package : wnpp
Severity : wishlist
Owner : Aman Verma
* Package name : golang-github-fzambia-sentinel
Version : 1.0.0+git20180630.52eb513-1
Upstream Author : Alexander Emelin
* URL : https://github.com/FZambia/senti
The problem I see with alternatives is: what happens when I have init X
set as the current alternative and I boot into init Y with a kernel command
line
or with a Grub-init-Y line?
Will I end up with init Y but with all links pointing to init X commands?
Il giorno dom 23 dic 2018 alle ore 15:58 Dm
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: davs2
Version : 1.6
Upstream Author : Falei LUO
* URL : https://github.com/pkuvcl/davs2
* License : GPL-2+
Programming Lang: C
Descrip
On Tuesday, 18 December 2018 20:11:58 CET you wrote:
> On Mon, Dec 17, 2018 at 09:46:42PM +0100, Stefan Fritsch wrote:
> > There is a random seed file stored by systemd-random-seed.service that
> > saves entropy from one boot and loads it again after the next reboot. The
> > random seed file is re-
On Sun, 2018-12-23 at 16:45:28 +0100, Guillem Jover wrote:
> On Sun, 2018-12-23 at 04:06:14 +0100, Guillem Jover wrote:
> > […] They also imply to permanently suffer the aliasing problems.
>
> To expand and clarify a bit on this. We have aliasing in general with
> symlinks and hardlinks, but those
On Sun, Dec 23, 2018 at 02:58:15PM +, Dmitry Bogatov wrote:
> [2018-12-21 11:31] Josh Triplett
> > You might consider submitting a patch to GRUB to add runit to that list,
> > or better yet making that behavior look for symlinks in /lib/inits/ or
> > similar and make an entry for every link th
On Sat, 2018-12-22 at 22:51:37 +, Simon McVittie wrote:
> On Sat, 22 Dec 2018 at 22:25:48 +0100, Guillem Jover wrote:
> > Procedurally? I guess it was
> > OKish, but I guess that's a consequence we get when people involved
> > the ctte to muddle the social and procedural fabric of the project…
On Sun, 2018-12-23 at 04:06:14 +0100, Guillem Jover wrote:
> […] They also imply to permanently suffer the aliasing problems.
To expand and clarify a bit on this. We have aliasing in general with
symlinks and hardlinks, but those tend to not be as problematic when
aliasing the last component, as t
Hello everyone, and Paul,
It got to my attention the rsync is a little behind our standards wrt to
packaging and it looks like the maintainer doesn't have time to deal with
that at the moment.
Basically what I want to do is to upload the new release (along with some
packaging fixes), adding new U
[2018-12-21 23:57] Thorsten Glaser
> On Fri, 21 Dec 2018, Dmitry Bogatov wrote:
>
> > I propose to replace current approach with update-alternatives(1)
> […]
> > Opinions?
>
> No. update-alternatives is too fragile to handle things like
> /bin/sh and init(8).
What do you mean fragile? Mind to
[2018-12-21 23:19] Lorenz
> A slightly different approach is also possible:
> Ship only /sbin/init as a alternative link ("the default init" as user
> choice)
> and ship in `init-system-helpers' the following
>
> /sbin/halt
> /sbin/poweroff
> /sbin/reboot
> /sbin
[2018-12-21 20:35] Colin Watson
> > (Meanwhile, I don't think it's necessarily a good idea to handle
> > /sbin/init and associated programs with alternatives, not least of which
> > because of the complications of switching the running system's init.)
>
> I quite agree.
Could you please elabor
[2018-12-21 11:31] Josh Triplett
> You might consider submitting a patch to GRUB to add runit to that list,
> or better yet making that behavior look for symlinks in /lib/inits/ or
> similar and make an entry for every link that doesn't match /sbin/init.
> (If you do so with fallbacks to the exi
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: xavs2
Version : 1.3
Upstream Author : Falei LUO
* URL : https://github.com/pkuvcl/xavs2/
* License : GPL-2+
Programming Lang: C
Descri
On Dec 23, Guillem Jover wrote:
> To me it's always been very clear the only *proper* way to deploy
> merged-/usr, is to do the changes to the canonical pathnames on
> each relevant package. Even adding compat symlinks, means that dpkg
> would know about them, and they'd be temporary anyway for t
23 matches
Mail list logo
