On 4 December 2017 at 16:56, Baptiste Daroussin wrote:
>
> So this is the issue, somewhere in the way libarchive is handling the
> hardlinks.
I'm not sure libarchive is at fault, it seems to be a bug/limitation
in the way install handles links with -M. For regular installs we
invoke:
install
On Mon, Dec 04, 2017 at 06:59:56PM +, Glen Barber wrote:
> On Mon, Dec 04, 2017 at 10:46:56AM -0800, Rodney W. Grimes wrote:
> > > On Mon, Dec 04, 2017 at 12:46:37PM -0500, Kris Moore wrote:
> > > > On 12/04/2017 11:37, Brad Davis wrote:
> > > > > On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wr
> On 12/04/2017 13:47, Rodney W. Grimes wrote:
> >> On 12/04/2017 11:37, Brad Davis wrote:
> >>> On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> Anybody else noticed a recent regression (say past month or so) where
> pkg base of latest HEAD is now failing to throw setuid on some fil
> On Mon, Dec 04, 2017 at 10:46:56AM -0800, Rodney W. Grimes wrote:
> > > On Mon, Dec 04, 2017 at 12:46:37PM -0500, Kris Moore wrote:
> > > > On 12/04/2017 11:37, Brad Davis wrote:
> > > > > On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> > > > >> Anybody else noticed a recent regression (say
On Mon, Dec 04, 2017 at 10:46:56AM -0800, Rodney W. Grimes wrote:
> > On Mon, Dec 04, 2017 at 12:46:37PM -0500, Kris Moore wrote:
> > > On 12/04/2017 11:37, Brad Davis wrote:
> > > > On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> > > >> Anybody else noticed a recent regression (say past mont
On 12/04/2017 13:47, Rodney W. Grimes wrote:
>> On 12/04/2017 11:37, Brad Davis wrote:
>>> On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
Anybody else noticed a recent regression (say past month or so) where
pkg base of latest HEAD is now failing to throw setuid on some files? We
>>>
> On 12/04/2017 11:37, Brad Davis wrote:
> > On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> >> Anybody else noticed a recent regression (say past month or so) where
> >> pkg base of latest HEAD is now failing to throw setuid on some files? We
> >> saw it at first because /sbin/shutdown lost
> On Mon, Dec 04, 2017 at 12:46:37PM -0500, Kris Moore wrote:
> > On 12/04/2017 11:37, Brad Davis wrote:
> > > On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> > >> Anybody else noticed a recent regression (say past month or so) where
> > >> pkg base of latest HEAD is now failing to throw setu
On Mon, Dec 04, 2017 at 12:46:37PM -0500, Kris Moore wrote:
> On 12/04/2017 11:37, Brad Davis wrote:
> > On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> >> Anybody else noticed a recent regression (say past month or so) where
> >> pkg base of latest HEAD is now failing to throw setuid on some
On 12/04/2017 11:37, Brad Davis wrote:
> On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
>> Anybody else noticed a recent regression (say past month or so) where
>> pkg base of latest HEAD is now failing to throw setuid on some files? We
>> saw it at first because /sbin/shutdown lost its setuid
On Mon, Dec 4, 2017, at 09:25 AM, Kris Moore wrote:
> Anybody else noticed a recent regression (say past month or so) where
> pkg base of latest HEAD is now failing to throw setuid on some files? We
> saw it at first because /sbin/shutdown lost its setuid bit, so users
> can't shutdown the box. I r
Anybody else noticed a recent regression (say past month or so) where
pkg base of latest HEAD is now failing to throw setuid on some files? We
saw it at first because /sbin/shutdown lost its setuid bit, so users
can't shutdown the box. I rolled back pkg to 1.10.1 which was working,
and that didn't
12 matches
Mail list logo
