FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 08-02-2008, 08:36 PM
Michael Schwendt
 
Default Conflicts in Rawhide i386 (part 2)

Some more packages with file conflicts in Rawhide i386:

batik-slideshow
coda-client
coq
dstat
libtranslate
plt-scheme
rblcheck
sleuthkit
surfraw
synce-hal
synce-serial
udns

[...]

Details:

plt-scheme-4.0-3.fc10.i386
File conflict with: batik-slideshow-1.7-0.5.beta1.noarch
/usr/bin/slideshow

batik-slideshow-1.7-0.5.beta1.noarch
File conflict with: plt-scheme-4.0-3.fc10.i386
/usr/bin/slideshow

coda-client-6.9.4-0.1.rc2.fc10.i386
File conflict with: coq-8.1pl3-2.fc10.i386
/usr/bin/parser

coq-8.1pl3-2.fc10.i386
File conflict with: coda-client-6.9.4-0.1.rc2.fc10.i386
/usr/bin/parser

libtranslate-0.99-15.fc10.i386
File conflict with: surfraw-1.0.7-3.fc8.noarch
/usr/bin/translate

rblcheck-1.5-15.fc9.i386
File conflict with: udns-0.0.9-2.fc10.i386
/usr/bin/rblcheck

sleuthkit-2.52-1.fc10.i386
File conflict with: dstat-0.6.7-3.fc10.noarch
/usr/bin/dstat
/usr/share/man/man1/dstat.1.gz

synce-hal-0.1-1.fc10.i386
File conflict with: synce-serial-0.11-2.fc9.i386
/usr/libexec/synce-serial-chat

synce-serial-0.11-2.fc9.i386
File conflict with: synce-hal-0.1-1.fc10.i386
/usr/libexec/synce-serial-chat

udns-0.0.9-2.fc10.i386
File conflict with: rblcheck-1.5-15.fc9.i386
/usr/bin/rblcheck

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-04-2008, 08:14 AM
"Richard W.M. Jones"
 
Default Conflicts in Rawhide i386 (part 2)

On Sat, Aug 02, 2008 at 10:36:34PM +0200, Michael Schwendt wrote:
> coq-8.1pl3-2.fc10.i386
> File conflict with: coda-client-6.9.4-0.1.rc2.fc10.i386
> /usr/bin/parser

Hmmm, I thought that was going to happen.

https://bugzilla.redhat.com/show_bug.cgi?id=450323#c16

Down at the bottom of that comment I said:

BTW having a binary called /usr/bin/parser is probably a bad idea.
How do Debian package this file? They usually rename such generic
names ('coqparser' or the like). If Debian rename it, then we should
do so too.

We checked Debian, and in fact they ship this as /usr/bin/parser too,
which is why we left it.

Not sure what is the best thing to do here:

(1) Rename it and thus be inconsistent with both upstream & Debian.

(2) Rename Coda's "parser" (breaking things?)

(3) Leave it and tell people that they can't install both packages at
once(!)

Rich.


--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
Read my OCaml programming blog: http://camltastic.blogspot.com/
Fedora now supports 59 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-04-2008, 08:30 AM
Hans de Goede
 
Default Conflicts in Rawhide i386 (part 2)

Richard W.M. Jones wrote:

On Sat, Aug 02, 2008 at 10:36:34PM +0200, Michael Schwendt wrote:

coq-8.1pl3-2.fc10.i386
File conflict with: coda-client-6.9.4-0.1.rc2.fc10.i386
/usr/bin/parser


Hmmm, I thought that was going to happen.

https://bugzilla.redhat.com/show_bug.cgi?id=450323#c16

Down at the bottom of that comment I said:

BTW having a binary called /usr/bin/parser is probably a bad idea.
How do Debian package this file? They usually rename such generic
names ('coqparser' or the like). If Debian rename it, then we should
do so too.

We checked Debian, and in fact they ship this as /usr/bin/parser too,
which is why we left it.

Not sure what is the best thing to do here:

(1) Rename it and thus be inconsistent with both upstream & Debian.

(2) Rename Coda's "parser" (breaking things?)



As the coda packager, let me add the following usefull info (not) I've no idea
what will break with regards to coda if this binary is renamed. It seems to be
a utility which gets called from other coda processes.


Any coda experts here?


(3) Leave it and tell people that they can't install both packages at
once(!)



Regards,

Hans

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-04-2008, 08:35 AM
"Thomas Moschny"
 
Default Conflicts in Rawhide i386 (part 2)

2008/8/4 Hans de Goede <j.w.r.degoede@hhs.nl>:
> As the coda packager, let me add the following useful info (not) I've no
> idea what will break with regards to coda if this binary is renamed. It
> seems to be a utility which gets called from other coda processes.

So ... it should probably be moved to %{_libexecdir}/coda/parser, no?

- Thomas

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-04-2008, 01:03 PM
Hans de Goede
 
Default Conflicts in Rawhide i386 (part 2)

Thomas Moschny wrote:

2008/8/4 Hans de Goede <j.w.r.degoede@hhs.nl>:

As the coda packager, let me add the following useful info (not) I've no
idea what will break with regards to coda if this binary is renamed. It
seems to be a utility which gets called from other coda processes.


So ... it should probably be moved to %{_libexecdir}/coda/parser, no?



Maybe, I haven't investigated that close yet, as I simply don't have the time
for it. Given thatb packages which contain /usr/bin/parser are pretty obscure
packages, the chances of a user actually hitting this problem are small.


That does not mean that it should not be fixed, but that does make it a low
priority thing for me.


Patches (from people who have done their homework and know exactly for what and
when "parser" in coda is used) are welcome.


Regards,

Hans

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-04-2008, 02:01 PM
"Richard W.M. Jones"
 
Default Conflicts in Rawhide i386 (part 2)

On Mon, Aug 04, 2008 at 03:03:58PM +0200, Hans de Goede wrote:
> Maybe, I haven't investigated that close yet, as I simply don't have the
> time for it. Given thatb packages which contain /usr/bin/parser are
> pretty obscure packages, the chances of a user actually hitting this
> problem are small.

Alan Dunn has asked Coq upstream if it is possible for them to rename
this program so it's less generic.

Rich.

--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
Read my OCaml programming blog: http://camltastic.blogspot.com/
Fedora now supports 59 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-04-2008, 04:36 PM
Toshio Kuratomi
 
Default Conflicts in Rawhide i386 (part 2)

Richard W.M. Jones wrote:

On Sat, Aug 02, 2008 at 10:36:34PM +0200, Michael Schwendt wrote:

coq-8.1pl3-2.fc10.i386
File conflict with: coda-client-6.9.4-0.1.rc2.fc10.i386
/usr/bin/parser


Hmmm, I thought that was going to happen.

https://bugzilla.redhat.com/show_bug.cgi?id=450323#c16

Down at the bottom of that comment I said:

BTW having a binary called /usr/bin/parser is probably a bad idea.
How do Debian package this file? They usually rename such generic
names ('coqparser' or the like). If Debian rename it, then we should
do so too.

We checked Debian, and in fact they ship this as /usr/bin/parser too,
which is why we left it.

Not sure what is the best thing to do here:

(1) Rename it and thus be inconsistent with both upstream & Debian.

(2) Rename Coda's "parser" (breaking things?)

We should definitely rename one or both /usr/bin/parser's. The steps
should be something like this:


1) Contact upstream and ask if they are amenable to renaming the binary
in their next release. Then try to rename our binary now.


2) If upstream isn't willing to, see if we can at least get the blessing
to do it locally with a given name.


3) Check with other distros (Maybe Debian now but discuss on
distributions-list@freedesktop.org about keeping a distro-wide list) if
they've seen the problem/would be willing to rename their binaries.


4) Do the rename locally.

-Toshio

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-05-2008, 04:10 PM
"Alan Dunn"
 
Default Conflicts in Rawhide i386 (part 2)

Upstream said the name should probably be changed and that they have
done so in the past with previous binaries in the package. While that
isn't a solid commitment to doing it in the next version, I would say
it's probably good enough to change it, which I'm going to do now.

- Alan

2008/8/4 Toshio Kuratomi <a.badger@gmail.com>:
> Richard W.M. Jones wrote:
>>
>> On Sat, Aug 02, 2008 at 10:36:34PM +0200, Michael Schwendt wrote:
>>>
>>> coq-8.1pl3-2.fc10.i386
>>> File conflict with: coda-client-6.9.4-0.1.rc2.fc10.i386
>>> /usr/bin/parser
>>
>> Hmmm, I thought that was going to happen.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=450323#c16
>>
>> Down at the bottom of that comment I said:
>>
>> BTW having a binary called /usr/bin/parser is probably a bad idea.
>> How do Debian package this file? They usually rename such generic
>> names ('coqparser' or the like). If Debian rename it, then we should
>> do so too.
>>
>> We checked Debian, and in fact they ship this as /usr/bin/parser too,
>> which is why we left it.
>>
>> Not sure what is the best thing to do here:
>>
>> (1) Rename it and thus be inconsistent with both upstream & Debian.
>>
>> (2) Rename Coda's "parser" (breaking things?)
>>
> We should definitely rename one or both /usr/bin/parser's. The steps should
> be something like this:
>
> 1) Contact upstream and ask if they are amenable to renaming the binary in
> their next release. Then try to rename our binary now.
>
> 2) If upstream isn't willing to, see if we can at least get the blessing to
> do it locally with a given name.
>
> 3) Check with other distros (Maybe Debian now but discuss on
> distributions-list@freedesktop.org about keeping a distro-wide list) if
> they've seen the problem/would be willing to rename their binaries.
>
> 4) Do the rename locally.
>
> -Toshio
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-06-2008, 10:35 AM
"Richard W.M. Jones"
 
Default Conflicts in Rawhide i386 (part 2)

On Tue, Aug 05, 2008 at 12:10:36PM -0400, Alan Dunn wrote:
> Upstream said the name should probably be changed and that they have
> done so in the past with previous binaries in the package. While that
> isn't a solid commitment to doing it in the next version, I would say
> it's probably good enough to change it, which I'm going to do now.

Out of interest, what was the new name? I'll alert Debian ...

Rich.

--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-06-2008, 10:48 AM
"Alan Dunn"
 
Default Conflicts in Rawhide i386 (part 2)

The new name is coq-parser.

- Alan

On Wed, Aug 6, 2008 at 6:35 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
> On Tue, Aug 05, 2008 at 12:10:36PM -0400, Alan Dunn wrote:
>> Upstream said the name should probably be changed and that they have
>> done so in the past with previous binaries in the package. While that
>> isn't a solid commitment to doing it in the next version, I would say
>> it's probably good enough to change it, which I'm going to do now.
>
> Out of interest, what was the new name? I'll alert Debian ...
>
> Rich.
>
> --
> Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine. Supports Linux and Windows.
> http://et.redhat.com/~rjones/virt-df/
>
> --
> fedora-devel-list mailing list
> fedora-devel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 04:56 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org