Leo Famulari writes: >> +;; Replacement package to fix multiple security bugs: >> +;; . >> +(define-public libx11-1.6.6 >> + (package/inherit libx11 > > Does it need to use package/inherit? My understanding is that procedure > is primarily useful for packages that inherit from another package foo, > when foo is being grafted. For example, the current situation with > cups-minimal and cups. Ah yes; you're right: in this case we don't need package/inherit because we are not inheriting an existing graft. I always mix those up, thanks for catching it! Pushed as 94e9d750a22e30459732d2ae14d71c5f3acabd91.