Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-26 Thread David Kalnischkies
On Sat, Jun 25, 2016 at 12:04:58PM -0700, Josh Triplett wrote: > > See https://wiki.debian.org/HelmutGrohne/MultiarchSpecChanges (and > > links) for more examples, potential solutions and problems/shortcomings > > from each of them. > > The "Install-Same-As" header on that page looks ideal for

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Josh Triplett
David Kalnischkies wrote: > On Sat, Jun 25, 2016 at 02:01:27AM -0700, Josh Triplett wrote: > > Sven Joachim wrote: > > > On 2016-06-24 23:01 -0700, Josh Triplett wrote: > > > > Some packages, if installed on any architecture, must be installed for > > > > every enabled architecture. Most notably,

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Ian Jackson
Josh Triplett writes ("Re: Handling Multi-Arch packages that must be installed for every enabled architecture?"): > On Sat, Jun 25, 2016 at 07:08:39PM +0100, Ian Jackson wrote: > > * LD_PRELOAD hacks need their .so installing for all architecture "for > > which they are going to be used"

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Josh Triplett
Simon McVittie wrote: > On Fri, 24 Jun 2016 at 23:01:21 -0700, Josh Triplett wrote: > > Some packages, if installed on any architecture, must be installed for > > every enabled architecture. Most notably, an NSS or PAM module package, > > if enabled in /etc/nsswitch.conf or /etc/pam.d

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Josh Triplett
On Sat, Jun 25, 2016 at 07:08:39PM +0100, Ian Jackson wrote: > Josh Triplett writes ("Handling Multi-Arch packages that must be installed > for every enabled architecture?"): > > That would solve the problem for the couple of cases it has come up in, > > but it seems far from ideal; I'd welcome

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Ian Jackson
Josh Triplett writes ("Handling Multi-Arch packages that must be installed for every enabled architecture?"): > That would solve the problem for the couple of cases it has come up in, > but it seems far from ideal; I'd welcome an cleaner alternative > solution. Notably, this doesn't work well

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread David Kalnischkies
On Sat, Jun 25, 2016 at 02:01:27AM -0700, Josh Triplett wrote: > Sven Joachim wrote: > > On 2016-06-24 23:01 -0700, Josh Triplett wrote: > > > Some packages, if installed on any architecture, must be installed for > > > every enabled architecture. Most notably, an NSS or PAM module package, > > >

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Josh Triplett
On Sat, Jun 25, 2016 at 09:37:37AM +0200, Ben Hutchings wrote: > On Fri, 2016-06-24 at 23:01 -0700, Josh Triplett wrote: > > Some packages, if installed on any architecture, must be installed for > > every enabled architecture.  Most notably, an NSS or PAM module package, > > if enabled in

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Ben Hutchings
On Fri, 2016-06-24 at 23:01 -0700, Josh Triplett wrote: > Some packages, if installed on any architecture, must be installed for > every enabled architecture.  Most notably, an NSS or PAM module package, > if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist > for every enabled

Re: Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Sven Joachim
On 2016-06-24 23:01 -0700, Josh Triplett wrote: > Some packages, if installed on any architecture, must be installed for > every enabled architecture. Most notably, an NSS or PAM module package, > if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist > for every enabled

Handling Multi-Arch packages that must be installed for every enabled architecture?

2016-06-25 Thread Josh Triplett
Some packages, if installed on any architecture, must be installed for every enabled architecture. Most notably, an NSS or PAM module package, if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist for every enabled architecture to avoid breaking programs for that architecture.