Re: [Fink-devel] renaming a package
On Sun, Sep 25, 2005 at 07:37:41AM -0400, Dave Vasilevsky wrote: On Sep 25, 2005, at 7:22 AM, Koen van der Drift wrote: Found the problem, I forgot to remove the Conflicts field in biopython-py.info: What about the Replaces and Provides fields, can they stay in the info file ? Hmm, it looks to me like they should all be there (including Conflicts). I hope this doesn't mean my dependency resolution algorithm is broken, I'll have to look into the situation. IIRC, Conflicts+Provides+Depends:foo has never worked correctly in dpkg (one of the three is ignored, can't remember which) despite the triple cocktail being used in Debian's own docs. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
On Sep 24, 2005, at 11:21 PM, Dave Vasilevsky wrote: Hi Koen, Judging from your error messages, it looks like the biopython-py24 you had installed and the one you had in a .deb were different, even though they had the same version/revision. (This can happen if you make changes and rebuild.) Could you try installing python- biopython-py24 again, and see if the error is the same or different? Also, please run fink with the -v flag, just in case there are any messages that Fink isn't printing. Dave Found the problem, I forgot to remove the Conflicts field in biopython-py.info: Info2: Package: biopython-py%type_pkg[python] Version: 1.40b Revision: 1 Type: python (2.2 2.3 2.4) Depends: python%type_pkg[python], python-mx-py%type_pkg[python], numeric-py%type_pkg[python], reportlab-py%type_pkg[python] Conflicts: python-biopython-py%type_pkg[python] Replaces: python-biopython-py%type_pkg[python] Provides: python-biopython-py%type_pkg[python] ... What about the Replaces and Provides fields, can they stay in the info file ? cheers, - Koen. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
On Sep 25, 2005, at 7:22 AM, Koen van der Drift wrote: Found the problem, I forgot to remove the Conflicts field in biopython-py.info: What about the Replaces and Provides fields, can they stay in the info file ? Hmm, it looks to me like they should all be there (including Conflicts). I hope this doesn't mean my dependency resolution algorithm is broken, I'll have to look into the situation. Dave PGP.sig Description: This is a digitally signed message part
Re: [Fink-devel] renaming a package
Hi, I finally got around to look at this again. As a reminder, this is what I am trying to do: I recently took over maintainership for the package 'python-biopython-py'. However, I think the name biopython-py would be more appropriate. Back in July, Dan MAcks suggested the following: A second problem is how the user who has the old-name package installed will know about this upgrade...his old-name-1.0-1 isn't marked out-of-date when new-name-2.0-1 appears. One solution is to create a final old-name-2.0-1:Depends:new-name(=2.0-1) but is Type:bundle and has a Description noting that it's just a upgrade compatibility game. That way his old old-name will be out-of-date, and when he upgrades it he will get he'll get the new one. Here's the info file for the old package I created: Info2: Package: python-biopython-py%type_pkg[python] Type: bundle, python (2.2 2.3 2.4) Version: 1.40b Revision: 1 Depends: biopython-py%type_pkg[python] (= 1.40b) Description: Python tools for computational biology Maintainer: Koen van der Drift [EMAIL PROTECTED] DescPackaging: This is a convenience package for biopython-py, to ensure the transition to a more consistant package name. Unfortunaltely this doesn't work, here's the output in the terminal: [EMAIL PROTECTED]:/sw/fink/dists/local/main/finkinfo/sci] $ fink install python-biopython-py24 Information about 4967 packages read in 2 seconds. The package 'python-biopython-py24' will be installed. Reading dependency for python-biopython-py24-1.40b-1... The following package will be installed or updated: python-biopython-py24 Resolving inconsistent dependencies... Solution resolved. Will install extra packages: biopython-py24-1.40b-1 /sw/bin/dpkg-lockwait -i /sw/fink/dists/local/main/binary-darwin- powerpc/sci/python-biopython-py24_1.40b-1_darwin-powerpc.deb /sw/fink/ dists/local/main/binary-darwin-powerpc/sci/biopython- py24_1.40b-1_darwin-powerpc.deb Selecting previously deselected package python-biopython-py24. dpkg: regarding .../python-biopython-py24_1.40b-1_darwin-powerpc.deb containing python-biopython-py24: biopython-py24 conflicts with python-biopython-py24 python-biopython-py24 (version 1.40b-1) is to be installed. /sw/bin/dpkg: error processing /sw/fink/dists/local/main/binary- darwin-powerpc/sci/python-biopython-py24_1.40b-1_darwin-powerpc.deb (--install): conflicting packages - not installing python-biopython-py24 (Reading database ... 33496 files and directories currently installed.) Preparing to replace biopython-py24 1.40b-1 (using .../biopython- py24_1.40b-1_darwin-powerpc.deb) ... Unpacking replacement biopython-py24 ... Setting up biopython-py24 (1.40b-1) ... Errors were encountered while processing: /sw/fink/dists/local/main/binary-darwin-powerpc/sci/python-biopython- py24_1.40b-1_darwin-powerpc.deb ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 Failed: can't batch-install packages: /sw/fink/dists/local/main/ binary-darwin-powerpc/sci/python-biopython-py24_1.40b-1_darwin- powerpc.deb /sw/fink/dists/local/main/binary-darwin-powerpc/sci/ biopython-py24_1.40b-1_darwin-powerpc.deb [EMAIL PROTECTED]:/sw/fink/dists/local/main/finkinfo/sci] $ Any suggestions how this might be fixed? Package manager version: 0.24.99.cvs Distribution version: 0.8.0.cvs thanks, - Koen. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
Hi Koen, Judging from your error messages, it looks like the biopython-py24 you had installed and the one you had in a .deb were different, even though they had the same version/revision. (This can happen if you make changes and rebuild.) Could you try installing python-biopython- py24 again, and see if the error is the same or different? Also, please run fink with the -v flag, just in case there are any messages that Fink isn't printing. Dave PGP.sig Description: This is a digitally signed message part
Re: [Fink-devel] renaming a package
On Sat, Jul 09, 2005 at 01:44:46PM -0400, Koen van der Drift wrote: Hi, (repost from April 2005) I recently took over maintainership for the package 'python-biopython-py'. However, I think the name biopython-py would be more appropriate. I agree. Unless there is a special reason why (some) python. packages have the python prefix, although most don't. So upstream programs really do call themselves python-foo, and some other package managers use python- as a naming convention for python modules. Would it be a big problem, if I rename the package? I can leave in the old info files, and add the new ones. The new ones will only be updated in the future. One problem is compatibility with other packages. Do any others depend on this one? If so, they must all be fixed to use the new name at the same time as the name changes. A second problem is how the user who has the old-name package installed will know about this upgrade...his old-name-1.0-1 isn't marked out-of-date when new-name-2.0-1 appears. One solution is to create a final old-name-2.0-1:Depends:new-name(=2.0-1) but is Type:bundle and has a Description noting that it's just a upgrade compatibility game. That way his old old-name will be out-of-date, and when he upgrades it he will get he'll get the new one. A more long-range solution would be to implement an Obsoletes field... if foo:Obsoletes:bar, any version of foo would be seen as newer than every version of bar, and dpkg would make some intelligent decisions about automatically trying to remove bar. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
On Jul 11, 2005, at 2:03 AM, Daniel Macks wrote: One solution is to create a final old-name-2.0-1:Depends:new-name(=2.0-1) but is Type:bundle and has a Description noting that it's just a upgrade compatibility game. That way his old old-name will be out-of-date, and when he upgrades it he will get he'll get the new one. That sounds like a good plan. If I use Type: bundle, how do I add the variants, so that the user can define the python version she wants to use? thanks, - Koen. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
On Mon, Jul 11, 2005 at 03:51:28PM -0400, Koen van der Drift wrote: On Jul 11, 2005, at 2:03 AM, Daniel Macks wrote: One solution is to create a final old-name-2.0-1:Depends:new-name(=2.0-1) but is Type:bundle and has a Description noting that it's just a upgrade compatibility game. That way his old old-name will be out-of-date, and when he upgrades it he will get he'll get the new one. That sounds like a good plan. If I use Type: bundle, how do I add the variants, so that the user can define the python version she wants to use? I think same as usual...multivariants give you every combination of the choice sets. And omitting an explicit for a type key set means there's only one choice for this key, so the long-existing Type:bundle is now just a special case of the generic variant syntax. Perhaps: Package: foo-py%type_pkh[python] Type: bundle, python (2.3 2.4) would give you packages foo-py23 and foo-py24, each of Type:bundle. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
On Jul 11, 2005, at 3:58 PM, Daniel Macks wrote: Type: bundle, python (2.3 2.4) Ah, I didn't realize I could add two arguments to the Type field. I'll try it out. thanks, - Koen. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] renaming a package
Hi, (repost from April 2005) I recently took over maintainership for the package 'python-biopython-py'. However, I think the name biopython-py would be more appropriate. Unless there is a special reason why (some) python packages have the python prefix, although most don't. Would it be a big problem, if I rename the package? I can leave in the old info files, and add the new ones. The new ones will only be updated in the future. cheers, - Koen. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] renaming a package
On 2005-07-09, Koen van der Drift wrote: Hi, (repost from April 2005) I recently took over maintainership for the package 'python-biopython-py'. However, I think the name biopython-py would be more appropriate. Unless there is a special reason why (some) python packages have the python prefix, although most don't. Would it be a big problem, if I rename the package? I can leave in the old info files, and add the new ones. The new ones will only be updated in the future. It might be better to remove the old .info file, and use Provides: python-biopython-py in the new package. Other than that suggestion, I have no opinion. crh pgpTGzu9fTt37.pgp Description: PGP signature
Re: [Fink-devel] renaming a package
On Jul 9, 2005, at 4:33 PM, Corey Halpin wrote: On 2005-07-09, Koen van der Drift wrote: Would it be a big problem, if I rename the package? I can leave in the old info files, and add the new ones. The new ones will only be updated in the future. It might be better to remove the old .info file, and use Provides: python-biopython-py in the new package. The package with the new name will be for a new upstream version, so I am not sure if the Provides field is needed in that case. I have added a Replaces and Conflicts field, though. Other than that suggestion, I have no opinion. I'll wait for some more reactions/opinions, otherwise I will just add the new .info file and remove the old ones. - Koen. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
