Re: [Rpm-maint] [rpm-software-management/rpm] option to disable fsync (#1401)

2020-10-17 Thread Colin Walters
> Are you aware of https://github.com/kjn/nosync Looks like the same as what I mentioned above originally: > I know about things like libeatmydata but the problem of course is that > librpm is linked into the same process (rpm-ostree) as the code that is doing > the ostree commit. -- You

[Rpm-maint] [rpm-software-management/rpm] option to disable fsync (#1401)

2020-10-14 Thread Colin Walters
For rpm-ostree, we rely on ostree for transactionality - ostree does fsync (or not) per its configuration. As best I can tell, rpm doesn't offer an API to disable its use of fsync (for the database or for writing files, though I only really care about the former). There are references to

Re: [Rpm-maint] [rpm-software-management/rpm] Add dbus-announce plugin (#1255)

2020-06-25 Thread Colin Walters
> imposes its own signal handling on users when the db is open Can turn that off since 56f49d7f5af7c1c8a3eb478431356195adbfdd25 right? > and our ABI hasn't been particularly stable historically Maintaining C shared libraries is indeed extremely hard. I've messed up in the past and only just

Re: [Rpm-maint] [rpm-software-management/rpm] RFE: add database change notification API (#1124)

2020-06-17 Thread Colin Walters
Just to echo https://github.com/rpm-software-management/rpm/pull/1255#issuecomment-645103007 here - inotify is used today for e.g. `/usr/share/applications` - when you e.g. `zypper/apt/yum/whatever install firefox` that's how the desktops pick up the change. As far as portability, there are

Re: [Rpm-maint] [rpm-software-management/rpm] Add dbus-announce plugin (#1255)

2020-06-16 Thread Colin Walters
> This isn't just for dnf's benefit. It's a mechanism that anybody who needs to > do so is free to listen, and everybody else can ignore. Speaking as a former DBus maintainer upstream here and I have written many DBus APIs... It seems dramatically simpler to me to go with the inotify approach,

Re: [Rpm-maint] [rpm-software-management/rpm] Add dbus-announce plugin (#1255)

2020-06-10 Thread Colin Walters
> Well, we add this on request of the DNF team that need to be notified if > something else (rpm cli) changes the rpmdb underneath their daemon. Ah, I see. Well, nothing else can/should be changing the rpmdb on rpm-ostree based systems (see also https://github.com/coreos/rpm-ostree/pull/1789

Re: [Rpm-maint] [rpm-software-management/rpm] Add dbus-announce plugin (#1255)

2020-06-08 Thread Colin Walters
@cgwalters commented on this pull request. > +state->logging = 1; + +/* ...don't log test transactions */ +if (rpmtsFlags(ts) & (RPMTRANS_FLAG_TEST|RPMTRANS_FLAG_BUILD_PROBS)) + state->logging = 0; + +/* ...don't log chroot transactions */ +if

Re: [Rpm-maint] [rpm-software-management/rpm] Add dbus-announce plugin (#1255)

2020-06-08 Thread Colin Walters
Is there any coordination between this and the work to add dbus to libdnf in https://github.com/rpm-software-management/libdnf/pull/941 for example? For rpm-ostree we are already a DBus daemon, and having multiple other libraries in the stack also going out and talking to DBus is going to be a

Re: [Rpm-maint] [rpm-software-management/rpm] Support ed25519 signatures (#1202)

2020-05-26 Thread Colin Walters
Just to xref, in ostree we recently merged an ed25519 signing system too: see https://github.com/ostreedev/ostree/issues/1233 and https://github.com/ostreedev/ostree/pull/1878 The main motivation apparently is that GPG being lgplv3 and carrying the patent clauses is problematic for some people

Re: [Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)

2020-04-15 Thread Colin Walters
Just to xref, since this one was closed the current plan is for rpm-ostree to wrap rpm, instead of having rpm wrap rpm-ostree: https://github.com/coreos/rpm-ostree/pull/1789 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] 4.16: no longer possible to package invalid symlink (#1159)

2020-04-01 Thread Colin Walters
> This is, however, a regression and places us in a difficult situation wrt > packaging our tests. You can just ship a tarball of this stuff instead right? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Make database backends self-aware (#910)

2019-10-21 Thread Colin Walters
> Make database backends self-aware :cold_sweat: -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/910#issuecomment-544540645___

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Fully shutdown DBUS on systemd_inhibit cleanup (RhBug:1714657)" (#900)

2019-10-16 Thread Colin Walters
Maybe key off `rpmsqSetInterruptSafety()`? I don't think mock calls that yet but it probably should. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Fully shutdown DBUS on systemd_inhibit cleanup (RhBug:1714657)" (#900)

2019-10-16 Thread Colin Walters
Oh wow. Is there a way for me to unconditionally turn this off in rpm-ostree? Since our upgrades are always offline+transactional we never need it. More generally, it seems like this plugin should be a no-op if we're installing into a root != `/` for e.g. the mock case right? -- You are

Re: [Rpm-maint] [rpm-software-management/rpm] Remove "support" for loading keyring from filesystem (#857)

2019-09-26 Thread Colin Walters
(Except I think that code is still not used by dnf because it dates to the PackageKit C vs yum Python days?) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Remove "support" for loading keyring from filesystem (#857)

2019-09-26 Thread Colin Walters
Also worth noting https://github.com/rpm-software-management/libdnf/issues/43 (libdnf auto-injects `/etc/pki/rpm-gpg`) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Fix excessive use of thread local storage (RhBug:1722181) (#759)

2019-06-20 Thread Colin Walters
LGTM. Regarding > The __thread uses in rpmsq don't make sense at all in reality, so better > revert and rethink from scratch. I don't know what all is writing/reading to those variables but, global mutable statics are basically always wrong. In Rust for example a common pattern is

Re: [Rpm-maint] [rpm-software-management/rpm] Compress annobin notes (#751)

2019-06-14 Thread Colin Walters
Can you keep the commit message title to < 80 chars? And move the text from the PR description into the commit message as well. Seems OK to me but: why don't the compilers do this by default? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or

Re: [Rpm-maint] [rpm-software-management/rpm] RPM must kill all childs on exit (from section?) (#134)

2018-09-17 Thread Colin Walters
Keep in mind that if rpmbuild itself used container features it'd heavily overlap with tools like `mock` - and while recursive containerization does work, it really requires both ends to be ready for it. See also https://github.com/projectatomic/bubblewrap/issues/284 -- You are receiving this

Re: [Rpm-maint] [rpm-software-management/rpm] luaext/Pexec: optimize setting CLOEXEC (#444)

2018-05-17 Thread Colin Walters
At a quick glance anyways, your code looks fine to me. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Make sure all dependencies for scriptlet are installed before executing them (#436)

2018-04-25 Thread Colin Walters
FWIW, in rpm-ostree today we lay out all files before executing scripts. Then we execute all `%pre`, then `%post` and `%posttrans`. Becuase of the `%pre` -> passwd dependency, we then do chowns after `%pre`. Also, [speaking of dependency loops and

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2018-01-08 Thread Colin Walters
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

Re: [Rpm-maint] [rpm-software-management/rpm] COPYING: Minor grammar fixes (#380)

2018-01-08 Thread Colin Walters
Updated :arrow_up: to use your suggestion - though can you help me understand: what's the difference between "RPM" and "its source code"? Documentation? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[Rpm-maint] [rpm-software-management/rpm] COPYING: Minor grammar fixes (#380)

2018-01-05 Thread Colin Walters
I was looking at this file in the context of dnf/rpm-ostree integration: https://github.com/rpm-software-management/dnf/pull/991#issuecomment-355587679 The incorrect use of "it's" was distracting; I ended up rewording the initial sentence to be more direct. The second hunk is another grammar

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2017-12-13 Thread Colin Walters
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

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2017-11-29 Thread Colin Walters
[/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

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2017-10-18 Thread Colin Walters
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

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2017-10-12 Thread Colin Walters
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

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2017-10-10 Thread Colin Walters
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

Re: [Rpm-maint] RFC: SUSE/openSUSE's proposed relocation of /var/lib/rpm

2017-10-10 Thread Colin Walters
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

Re: [Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)

2017-09-09 Thread Colin Walters
> @cgwalters: This patch looks very specific to RPM-OSTree. Is there not a > better, more general way to do this? More general to...other image systems that happen to use rpm? Possibly. As far as I'm aware though rpm-ostree is fairly unique in the way it's a hybrid image/package system. I

Re: [Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)

2017-09-08 Thread Colin Walters
BTW, down the line I'd like to extend this ostree-detection functionality a bit more so that e.g. `rpm -V` understands that timestamps are different, and that's OK. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Sync disks at the end of transactions (RhBug:1461765)" (#318)

2017-09-08 Thread Colin Walters
In active use? I don't think there's that many. Certainly the original bug report was from someone using dnf. I just don't understand the logic for pushing this directly into librpm without even making it configurable after all of the feedback from people using librpm for higher level tools

Re: [Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)

2017-09-07 Thread Colin Walters
Hi @herrold - I read your comment a few times and I'm confused...isn't that what my patch is doing? BTW, it's easy to try an rpm-ostree based system, see https://getfedora.org/atomic/ and https://pagure.io/workstation-ostree-config for example. One thing I'd note though is that the rpm

[Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)

2017-09-07 Thread Colin Walters
Down the line, it's likely that for rpm-ostree based systems we'll install an interceptor for `/usr/bin/rpm` to redirect at least things like local package installs. There's a lot of work to do for that, so in the meantime let's help admins out by giving them a helpful error message. You can

Re: [Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)

2017-09-07 Thread Colin Walters
This PR rolls in https://github.com/rpm-software-management/rpm/pull/319 After: ``` # rpm -e atomic error: This system is managed by rpm-ostree error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system) ``` This is still a WIP/RFE - the code here isn't pretty

[Rpm-maint] [rpm-software-management/rpm] lib/transaction: Don't SEGV in sync if a txn was failed (#319)

2017-09-07 Thread Colin Walters
I was actually testing a change to better handle `rpm -e atomic` on Fedora Atomic Host, wondering why my patch was crashing, but in fact it was the recently added sync code in master. You can view, comment on, or merge this pull request online at:

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Sync disks at the end of transactions (RhBug:1461765)" (#318)

2017-09-07 Thread Colin Walters
Anyone (including you) could trivially submit a patch to dnf or whatever to call `sync` after transactions and have that ship to users pretty quickly if that's what you want. That'd address the original bug report, no? Why should this be hardcoded in librpm? -- You are receiving this because

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Sync disks at the end of transactions (RhBug:1461765)" (#318)

2017-09-07 Thread Colin Walters
Or stated another way, if you change dnf it'd feel for the vast majority of people that it defaults to on, and do so pretty quickly. Right? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Sync disks at the end of transactions (RhBug:1461765) (b7a869f)

2017-09-06 Thread Colin Walters
https://github.com/rpm-software-management/rpm/pull/318 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[Rpm-maint] [rpm-software-management/rpm] Revert "Sync disks at the end of transactions (RhBug:1461765)" (#318)

2017-09-06 Thread Colin Walters
This reverts commit b7a869f0f322cbe428e78150f2c175abea4c8c4b. This would need to be at a minimum configurable, and default to off for compatibility with software like rpm-ostree that is already taking care of all of this. You can view, comment on, or merge this pull request online at:

Re: [Rpm-maint] [rpm-software-management/rpm] Sync disks at the end of transactions (RhBug:1461765) (b7a869f)

2017-09-06 Thread Colin Walters
BTW, see also https://github.com/ostreedev/ostree/pull/1049 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Sync disks at the end of transactions (RhBug:1461765) (b7a869f)

2017-09-06 Thread Colin Walters
rpm-ostree also has its own `syncfs()` calls and we definitely don't want librpm doing it. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Adding an event loop in RPM to run asynchronous operations. (#258)

2017-08-07 Thread Colin Walters
> all file operations are durable (in the sense that all installed files are > known written to disk). Right now many real world systems rely on files written by scripts (for example, the bootloader configuration, `/etc/ld.so.cache`, etc.); librpm as designed today doesn't have visibility into

Re: [Rpm-maint] [rpm-software-management/rpm] Semaphore CI (#266)

2017-07-20 Thread Colin Walters
cgwalters commented on this pull request. > @@ -0,0 +1,49 @@ +FROM fedora +MAINTAINER Igor Gnatenko + +WORKDIR /opt/rpm +COPY . . + +RUN echo -e "deltarpm=0\ninstall_weak_deps=0\ntsflags=nodocs" >> /etc/dnf/dnf.conf +RUN dnf -y update +RUN dnf -y install \ Which

Re: [Rpm-maint] [rpm-software-management/rpm] Semaphore CI (#266)

2017-07-20 Thread Colin Walters
cgwalters commented on this pull request. > @@ -0,0 +1,49 @@ +FROM fedora +MAINTAINER Igor Gnatenko + +WORKDIR /opt/rpm +COPY . . + +RUN echo -e "deltarpm=0\ninstall_weak_deps=0\ntsflags=nodocs" >> /etc/dnf/dnf.conf +RUN dnf -y update +RUN dnf -y install \ In some

Re: [Rpm-maint] [rpm-software-management/rpm] Don't modify interupts if db is read only (#251)

2017-07-14 Thread Colin Walters
Just a note to remember that for generating new roots (i.e. not inplace upgrades), we can just let SIGINT kill us. For rpm-ostree, every operation is a new root, so we [turn off rpm's SIGINT

Re: [Rpm-maint] [rpm-software-management/rpm] Add macro to force fsync() on close() (#187)

2017-04-18 Thread Colin Walters
@n3npq Regarding full-system durability - I'm the maintainer of https://github.com/projectatomic/rpm-ostree/ which uses https://github.com/ostreedev/ostree/ to implement full-system transactional updates. Every change (package install, update) is atomic. libostree currently [stages objects

Re: [Rpm-maint] [rpm-software-management/rpm] Add macro to force fsync() on close() (#187)

2017-04-15 Thread Colin Walters
@jaymzh But are your tests with a kernel with the writeback changes or not? It looks like this commit? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e34cbd307477ae07c5d8a8d0bd15e65a9ddaba5c Which offhand appears to be in v4.10. Ah yes, [kernelnewbies has a

Re: [Rpm-maint] [rpm-software-management/rpm] Add macro to force fsync() on close() (#187)

2017-04-14 Thread Colin Walters
Isn't this https://lwn.net/Articles/682582/ ? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/187#issuecomment-294231945___

Re: [Rpm-maint] [rpm-software-management/rpm] RFE: add a digest on the compressed payload content (#163)

2017-03-01 Thread Colin Walters
Okay, but that'd also be caught by MD5, right? So...do we expect every package system to verify *both* the rpm-md checksum and this one? Running SHA256 or whatever *is* pretty cheap, I know. Perhaps enough people rely on "untrusted rpm-md fetched over http + GPG signed RPMs" that we have to

Re: [Rpm-maint] [rpm-software-management/rpm] RFE: add a digest on the compressed payload content (#163)

2017-03-01 Thread Colin Walters
In practice though, people shouldn't be using raw `rpm` to install RPMs. They should (and 90% of the time are) using a higher level system like zypper, yum, or rpm-ostree. These systems all consume "rpm-md/yum" metadata, which obviously today has a checksum over the content, which can be

Re: [Rpm-maint] [rpm-software-management/rpm] heap out of bounds read in copyTdEntry() (#133)

2017-01-25 Thread Colin Walters
Need to check if this happens before GPG verification. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Check return value of uname() (#132)

2017-01-20 Thread Colin Walters
Under what conditions? An aggressive seccomp policy? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] testing GHPRB (#67)

2016-04-22 Thread Colin Walters
Any chance you could set up Jenkins against e.g. your personal fork of the repo and test things there first? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm] te: Don't reload header for JUSTDB transactions (#52)

2016-01-24 Thread Colin Walters
I ended up storing lead/sig/header in the ostree commit, then checking it out as a tempfile and passing it back to librpm. So we can close this. Long term, I think what I really want is to make `rpmdbOpen` and `rpmdbAdd` public. Then I can stay out of the business of writing to the db and

Re: [Rpm-maint] [rpm] te: Don't reload header for JUSTDB transactions (#52)

2016-01-24 Thread Colin Walters
Closed #52. --- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/52#event-524294958___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint

Re: [Rpm-maint] [rpm] te: Don't reload header for JUSTDB transactions (#52)

2016-01-22 Thread Colin Walters
Ideally, we just let `mmap()` handle that. That's what OSTree does for metadata by default. It'd probably work for packed RPMs as well...except in practice we byteswap in `regionSwab()` so require a writable mapping =/ For OSTree, GVariant handles a lot of this automatically for interior

[Rpm-maint] [rpm] te: Don't reload header for JUSTDB transactions (#52)

2016-01-21 Thread Colin Walters
I'm working on some custom rpm-ostree code to "install" rpms by unpacking them with libarchive (since this can be a lot safer than invoking librpm - my process has total control over writes), then just using librpm to update the database via _JUSTDB. However, it appears that for some reason that

Re: [Rpm-maint] [RFC v5 00/11] RPM: Include and install file signatures

2015-02-20 Thread Colin Walters
On Tue, Jan 27, 2015, at 10:04 AM, f...@linux.vnet.ibm.com wrote: IMA-appraisal, upstreamed in linux-3.7, enforces local file integrity based on a known 'good' value stored as an extended attribute 'security.ima'. Labeling the filesystem is currently done post install using a local private key.

Re: [Rpm-maint] [PATCH] Add API to completely disable librpm's use of Unix signal handlers

2015-02-19 Thread Colin Walters
On Tue, Feb 17, 2015, at 07:07 AM, Florian Festi wrote: Sorry, for the last response. DevConf takes its toll... On 01/23/2015 04:07 AM, Colin Walters wrote: Numerous consumers of librpm use it in a pattern where they're constructing fresh chroots. For example, rpm-ostree operates

Re: [Rpm-maint] whitelisting/wrapping script execution

2015-02-12 Thread Colin Walters
could change librpm to automatically delete /etc/ld.so.cache and force the search-all-the-paths mode of the dynamic linker until the end. I doubt anyone would notice the difference. On Wed, Apr 23, 2014, at 08:13 AM, Colin Walters wrote: Hi, For the rpm-ostree project, I need the ability

[Rpm-maint] [PATCH] Add API to completely disable librpm's use of Unix signal handlers

2015-01-22 Thread Colin Walters
insertions(+) From cb6f9a97baa4022789b469881bbc87aa1fb86697 Mon Sep 17 00:00:00 2001 From: Colin Walters walt...@verbum.org Date: Thu, 22 Jan 2015 17:57:14 -0500 Subject: [PATCH] Add API to completely disable librpm's use of Unix signal handlers Numerous consumers of librpm use it in a pattern

[Rpm-maint] fsync and package systems

2014-05-21 Thread Colin Walters
Hi, See: https://bugs.freedesktop.org/show_bug.cgi?id=70366 TL;DR: Should triggers like ldconfig, gtk-update-icon-cache, and update-mime-database: 1) Not fsync, and honor an environment variable like PKGSYSTEM_ENABLE_FSYNC 2) Do fsync, and honor PKGSYSTEM_DISABLE_FSYNC 3) Something else?

[Rpm-maint] whitelisting/wrapping script execution

2014-04-23 Thread Colin Walters
Hi, For the rpm-ostree project, I need the ability to whitelist scriptlets. There are a few reasons for this, but the most critical is that due to the way OSTree uses hardlinks, and because I can't assume I have copy-on-write links, I need to know that scriptlets will cleanly break hardlinks

Re: [Rpm-maint] installroot and NSS modules

2014-01-28 Thread Colin Walters
On Tue, Jan 28, 2014 at 4:16 AM, Panu Matilainen pmati...@laiskiainen.org wrote: Rpm 4.6 - 4.11.0 are buggy on non-trivial nsswitch setups due to my less-than-brilliant idea (wish I knew what I was thinking at the time...) See

[Rpm-maint] installroot and NSS modules

2014-01-08 Thread Colin Walters
Hi, I'm working on https://mail.gnome.org/archives/ostree-list/2014-January/msg0.html and it has some code that uses yum --installroot. However, the system requires a custom nss-altfiles NSS module that causes /usr/sbin/useradd -r to write to /usr/lib/passwd. But rpm from the host side is

Re: [Rpm-maint] installroot and NSS modules

2014-01-08 Thread Colin Walters
On Wed, 2014-01-08 at 15:06 -0500, Colin Walters wrote: But rpm from the host side is not correctly detecting these users. I realized after sending this sentence is unclear. More precisely, from the current polkit.spec: %attr(0700,polkitd,root) %dir %{_datadir}/polkit-1/rules.d rpm says

Re: [Rpm-maint] Add appdata() and application() auto-provides

2013-10-02 Thread Colin Walters
+ echo application() + echo application(${instfile##*/applications/}) if ! grep -q '^Type=Application$' $instfile; then continue; fi if ! grep -q '^Exec=' $instfile; then continue; fi Shouldn't these pairs of lines be swapped, so that we