Opened 10 years ago

Closed 9 years ago

#165 closed bug (wontfix)

Config and binary file conflict

Reported by: Matthias Bethke <matthias@…> Owned by: balaji
Priority: major Milestone: future
Component: mpich Keywords:
Cc:

Description (last modified by balaji)

Hi,

has anyone let you guys know about the file conflict in your "mpd"
projects (Music Player Daemon and Multi Processing Daemon) yet?
This old bug report summarizes it, and aside from telling the package
manager not to install both on the same system, nothing has happened
since: http://bugs.gentoo.org/145367
I've run into the same problem and was wondering if you'd be willing to
do something about it?
Debian calls its mpd "mpich-mpd-bin". Why not just "mpich-mpd" I'm not
sure but that sounds reasonable to me. On the other hand, MusicPD is
pretty much standalone and there are probably less scripts out in the
wild that have its name hardcoded---you start in an init script and
that's it. So that would perhaps be easier to change:
/usr/bin/musicplayerd and /etc/musicplayerd.conf?
Would be great if you guys could work something out...

cheers,

Matthias

--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665

Change History (8)

comment:1 Changed 10 years ago by Matthias Bethke

  • id set to 165

This message has 0 attachment(s)

comment:2 Changed 10 years ago by Anthony Chan

mpd is a process manager for MPICH2 MPI implementation,
it is NOT music player daemon.

A.Chan



Reporter: Matthias Bethke <matthias@…> | Type: bug


Status: new | Priority:

major
Milestone: | Component:
mpich2


Hi,

has anyone let you guys know about the file conflict in your "mpd"
projects (Music Player Daemon and Multi Processing Daemon) yet?
This old bug report summarizes it, and aside from telling the

package

manager not to install both on the same system, nothing has happened
since: http://bugs.gentoo.org/145367
I've run into the same problem and was wondering if you'd be willing

to

do something about it?
Debian calls its mpd "mpich-mpd-bin". Why not just "mpich-mpd" I'm

not

sure but that sounds reasonable to me. On the other hand, MusicPD is
pretty much standalone and there are probably less scripts out in

the

wild that have its name hardcoded---you start in an init script and
that's it. So that would perhaps be easier to change:
/usr/bin/musicplayerd and /etc/musicplayerd.conf?
Would be great if you guys could work something out...

cheers,

Matthias

--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665

--
Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/165>

comment:3 Changed 10 years ago by Matthias Bethke

Hi mpich2,
on Tue, Sep 23, 2008 at 10:58:58PM -0000, you wrote:


Reporter: Matthias Bethke <matthias@…> | Owner:

Type: bug | Status: new

Priority: major | Milestone:

Component: mpich2 | Resolution:

Keywords: |


Comment (by Anthony Chan):

mpd is a process manager for MPICH2 MPI implementation,
it is NOT music player daemon.

YOUR mpd that is. The other mpd whose author I sent this to (maybe youe
bug tracking system hides those email details but I thought it was
obvious from the text anyway) IS a music player. That's exactly the
problem: different applications, different authors, same name. Install
both: breakage.

kind regards,

Matthias Bethke

--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665

comment:4 Changed 10 years ago by Pavan Balaji

Matthias,

YOUR mpd that is. The other mpd whose author I sent this to (maybe youe
bug tracking system hides those email details but I thought it was
obvious from the text anyway) IS a music player. That's exactly the
problem: different applications, different authors, same name. Install
both: breakage.

Thanks for pointing this out. We'll try to figure out a way to avoid
this. Can you send us the contact information for the MPD music player
folks? As you guessed, our bug tracking system swallowed it up.

-- Pavan

--
Pavan Balaji
http://www.mcs.anl.gov/~balaji

comment:5 Changed 10 years ago by Matthias Bethke

Hi Pavan,
on Wed, Sep 24, 2008 at 02:01:51PM -0000, you wrote:

YOUR mpd that is. The other mpd whose author I sent this to (maybe youe
bug tracking system hides those email details but I thought it was
obvious from the text anyway) IS a music player. That's exactly the
problem: different applications, different authors, same name. Install
both: breakage.

Thanks for pointing this out. We'll try to figure out a way to avoid
this. Can you send us the contact information for the MPD music player
folks? As you guessed, our bug tracking system swallowed it up.

Sure, should have done so in the last mail 8)
It's warren.dukes@… (site is at http://www.musicpd.org/)

kind regards,

Matthias

--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665

comment:6 Changed 10 years ago by balaji

  • Owner set to balaji

comment:7 Changed 9 years ago by balaji

  • Milestone set to future

comment:8 Changed 9 years ago by balaji

  • Description modified (diff)
  • Resolution set to wontfix
  • Status changed from new to closed

Based on some discussion within the group and binary package creators, this isn't easy to do without breaking a ton of documentation. Also, MPD will eventually be deprecated in favor of Hydra where this name conflict does not occur. For users whom this effects, the current workaround for this is to not build mpd at all, and just configure mpich2 with Hydra using the configure option --with-pm=hydra.

I'm resolving this ticket as a "wont fix".

Note: See TracTickets for help on using tickets.