More followup, just a FYI. Note that in this PR the whole of
/usr/lib/sysimage is just usr_t:
https://github.com/fedora-selinux/selinux-policy-contrib/pull/43
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-m
FYI:
https://src.fedoraproject.org/rpms/filesystem/pull-request/3
and
https://github.com/projectatomic/rpm-ostree/pull/1142
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
On Wed, Nov 29, 2017 at 9:20 AM, Colin Walters wrote:
> [/me moves to center of thread, pulls out defibrillation machine, *zzzt*
> *zzzt*]
>
> On Thu, Oct 26, 2017, at 04:59 AM, Richard Brown wrote:
>>
>> As we're pressed on time, openSUSE will be going right ahead and moving it's
>> rpmdb to /u
[/me moves to center of thread, pulls out defibrillation machine, *zzzt* *zzzt*]
On Thu, Oct 26, 2017, at 04:59 AM, Richard Brown wrote:
>
> As we're pressed on time, openSUSE will be going right ahead and moving it's
> rpmdb to /usr/lib/sysimage/rpm as
> fast as possible
I assume this was done?
On Thu, Oct 26, 2017 at 5:59 AM, Richard Brown wrote:
> On Wed, 2017-10-18 at 08:51 -0400, Colin Walters wrote:
>>
>> On Wed, Oct 18, 2017, at 06:56 AM, Panu Matilainen wrote:
>>
>> > I don't see /usr/lib as a *good* place for this, but if a new top level
>> > directory in /usr seems too much then
On Wed, 2017-10-18 at 08:51 -0400, Colin Walters wrote:
>
> On Wed, Oct 18, 2017, at 06:56 AM, Panu Matilainen wrote:
>
> > I don't see /usr/lib as a *good* place for this, but if a new top level
> > directory in /usr seems too much then maybe /usr/lib/sysimage or such
>
> I'm OK with /usr/lib
On Thu, 2017-10-26 at 11:54 +0300, Panu Matilainen wrote:
> On 10/26/2017 11:35 AM, Richard Brown wrote:
> > On Wed, 2017-10-18 at 08:51 -0400, Colin Walters wrote:
> > >
> > > On Wed, Oct 18, 2017, at 06:56 AM, Panu Matilainen wrote:
> > >
> > > > I don't see /usr/lib as a *good* place for this,
On 10/26/2017 11:35 AM, Richard Brown wrote:
On Wed, 2017-10-18 at 08:51 -0400, Colin Walters wrote:
On Wed, Oct 18, 2017, at 06:56 AM, Panu Matilainen wrote:
I don't see /usr/lib as a *good* place for this, but if a new top level
directory in /usr seems too much then maybe /usr/lib/sysimage
On Wed, 2017-10-18 at 08:51 -0400, Colin Walters wrote:
>
> On Wed, Oct 18, 2017, at 06:56 AM, Panu Matilainen wrote:
>
> > I don't see /usr/lib as a *good* place for this, but if a new top level
> > directory in /usr seems too much then maybe /usr/lib/sysimage or such
>
> I'm OK with /usr/lib
On Wed, Oct 18, 2017, at 06:56 AM, Panu Matilainen wrote:
> I don't see /usr/lib as a *good* place for this, but if a new top level
> directory in /usr seems too much then maybe /usr/lib/sysimage or such
I'm OK with /usr/lib/sysimage.
> As Neal pointed out, there's dpkg and the other package
On 10/16/2017 06:22 PM, Richard Brown wrote:
On Fri, 2017-10-13 at 11:31 +0300, Panu Matilainen wrote:
The database path has always been trivially configurable with a macro
without having to patch rpm, nobody is taking that away. And because
it's so trivial to change it really doesn't need a co
On Mon, Oct 16, 2017 at 11:22 AM, Richard Brown wrote:
> On Fri, 2017-10-13 at 11:31 +0300, Panu Matilainen wrote:
>
>> The database path has always been trivially configurable with a macro
>> without having to patch rpm, nobody is taking that away. And because
>> it's so trivial to change it real
On Fri, 2017-10-13 at 11:31 +0300, Panu Matilainen wrote:
> The database path has always been trivially configurable with a macro
> without having to patch rpm, nobody is taking that away. And because
> it's so trivial to change it really doesn't need a configure switch either.
>
> It's also wa
On 10/12/2017 05:44 PM, Mark Hatle wrote:
On 10/12/17 4:52 AM, Neal Gompa wrote:
On Mon, Oct 9, 2017 at 11:25 AM, Richard Brown wrote:
What do you all think? And if a change like this is on the cards as an rpm
default, where would the likely
location be?
So, I think we should probably exp
On 10/12/17 4:52 AM, Neal Gompa wrote:
> On Mon, Oct 9, 2017 at 11:25 AM, Richard Brown wrote:
>>
>> What do you all think? And if a change like this is on the cards as an rpm
>> default, where would the likely
>> location be?
>>
>
> So, I think we should probably expose this as an configure swi
On 10/12/2017 04:04 PM, Colin Walters wrote:
On Thu, Oct 12, 2017, at 07:18 AM, Panu Matilainen wrote:
Rpm is not the only data of this kind, I can think of at least one other
similar need (SWID) and almost certainly there are more. Why not give
this data a place of its own? Something like
/us
On Thu, Oct 12, 2017, at 07:18 AM, Panu Matilainen wrote:
>
> Rpm is not the only data of this kind, I can think of at least one other
> similar need (SWID) and almost certainly there are more. Why not give
> this data a place of its own? Something like
>
> /usr/sysimage
Hm...creating a new su
On 10/09/2017 06:25 PM, Richard Brown wrote:
Hello rpm developers,
openSUSE & SUSE distributions have a growing number of problems with the
current location of the rpmdb in
/var/lib/rpm
All *SUSE Distributions have a default btrfs snapshot & rollback feature.
We need the contents of the rpmdb
On Mon, Oct 9, 2017 at 11:25 AM, Richard Brown wrote:
>
> What do you all think? And if a change like this is on the cards as an rpm
> default, where would the likely
> location be?
>
So, I think we should probably expose this as an configure switch, and
default to /var/lib/rpm. Most people have
> On 10. Oct 2017, at 22:32, Colin Walters wrote:
>
>> We're planning on making this change for all of our distributions via
>> all of their distribution methods, for consistencies sake.
>> Given how we build our containers, we'd actually have to do extra work
>> to exclude my patch and rest
On Tue, Oct 10, 2017, at 03:41 PM, Richard Brown wrote:
> On 2017-10-10 20:05, Colin Walters wrote:
>
> > My opinion here boils down to: if rpm upstream is happy with
> > /usr/lib/rpmdb,
> > I'm happy to do the work of changing rpm-ostree to use that.
>
> That's great news, I'm happy to help if
On 2017-10-10 20:05, Colin Walters wrote:
My opinion here boils down to: if rpm upstream is happy with
/usr/lib/rpmdb,
I'm happy to do the work of changing rpm-ostree to use that.
That's great news, I'm happy to help if I can
(Longer version: I don't find the "sharable architecture-independ
On Mon, Oct 9, 2017, at 11:25 AM, Richard Brown wrote:
> The discussion currently boils down to either copying rpm-ostree and placing
> our rpmdb in /usr/share/rpm, or
> locating it in /usr/lib/rpmdb
I definitely like the "db" suffix, makes it less of a potential naming clash if
librpm decided
Hello rpm developers,
openSUSE & SUSE distributions have a growing number of problems with the
current location of the rpmdb in
/var/lib/rpm
All *SUSE Distributions have a default btrfs snapshot & rollback feature.
We need the contents of the rpmdb contained within the snapshots.
This means /v
24 matches
Mail list logo