Re: Ever rebuilding openpkg-2.1.0
On Sun, Jul 25, 2004, Michael van Elst wrote: On Sun, Jul 25, 2004 at 12:03:09AM +0200, Ralf S. Engelschall wrote: On Sat, Jul 24, 2004, Michael van Elst wrote: [..] One could special case the openpkg package, but I'd like to avoid this if possible. The following patch therefore will simply select the database entry with the smallest version number, i.e. OpenPKG-2.1.0-2.1.0 when deciding on wether it needs an update. [...] I've tested this patch. Now it works as expected for a RELEASE based OpenPKG instances, but on a CURRENT based OpenPKG instance (really all packages from CURRENT, no mix), it now tries there to always rebuild and upgrade an already up-to-date openpkg CURRENT package. I think we have to afford a special case here, haven't we? Thanks to your last change it doesn't happen anymore :) | revision 1.349 | date: 2004-07-24 22:10:41 +; author: rse; state: Exp; lines: +1 -2 | remove useless Provides for the corresponding RELEASE version grin This was my hope yesterday evening, too. Cool. Then I'll release openpkg-tool with your patch. Thanks. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Ever rebuilding openpkg-2.1.0
On Sun, Jul 25, 2004, Ralf S. Engelschall wrote: [...] Then I'll release openpkg-tool with your patch. Thanks. Ok, openpkg-tools-0.8.16-20040725 and openpkg-tools-0.8.16-2.1.1 now contain this patch and no longer try to update the bootstrap package every time. Thanks for the fast help, Michael. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Ever rebuilding openpkg-2.1.0
On Sat, Jul 24, 2004 at 08:59:01AM +0200, Ralf S. Engelschall wrote: That's a known bug in the openpkg build command (see http://cvs.openpkg.org/getfile/openpkg-tools/TODO for a list of known issues). It works fine for CURRENT, but when updating a RELEASE it always thinks that the openpkg package has to be recompiled. This is caused by the openpkg package that provides an additional current version. After installing openpkg-2.1 and the tools I get: [EMAIL PROTECTED] openpkg rpm --provides -qa OpenPKG openpkg = 20040712-20040712 openpkg = 2.1.0-2.1.0 gpg(OpenPKG [EMAIL PROTECTED]) = 4:807593e063c4cb9f-3c591eda gpg(63c4cb9f) = 4:807593e063c4cb9f-3c591eda openpkg-tools = 0.8.15-2.1.0 The build tool then tries to update openpkg-20040712-20040712 to the one described in the index. Either the bogus version information has to be removed from database or the build tool needs to have some idea how to detect and handle packages that appear more than once in the database. Note that there is no real package behind that entry in the database, it is just a Provides: value. Greetings, -- Michael van Elst Internet: [EMAIL PROTECTED] A potential Snark may lurk in every tree. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Ever rebuilding openpkg-2.1.0
On Sat, Jul 24, 2004, Michael van Elst wrote: On Sat, Jul 24, 2004 at 08:59:01AM +0200, Ralf S. Engelschall wrote: That's a known bug in the openpkg build command (see http://cvs.openpkg.org/getfile/openpkg-tools/TODO for a list of known issues). It works fine for CURRENT, but when updating a RELEASE it always thinks that the openpkg package has to be recompiled. This is caused by the openpkg package that provides an additional current version. After installing openpkg-2.1 and the tools I get: [EMAIL PROTECTED] openpkg rpm --provides -qa OpenPKG openpkg = 20040712-20040712 openpkg = 2.1.0-2.1.0 gpg(OpenPKG [EMAIL PROTECTED]) = 4:807593e063c4cb9f-3c591eda gpg(63c4cb9f) = 4:807593e063c4cb9f-3c591eda openpkg-tools = 0.8.15-2.1.0 The build tool then tries to update openpkg-20040712-20040712 to the one described in the index. Either the bogus version information has to be removed from database or the build tool needs to have some idea how to detect and handle packages that appear more than once in the database. Note that there is no real package behind that entry in the database, it is just a Provides: value. Oh, now I understand the problem! Unfortunately the Provides for the CURRENT version is very important for mixing RELEASE and CURRENT and hence cannot be removed. So, we should tell openpkg build about this special case, I think. Do you have a quick patch at hand, Michael? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Ever rebuilding openpkg-2.1.0
On Sat, Jul 24, 2004, Michael van Elst wrote: [..] One could special case the openpkg package, but I'd like to avoid this if possible. The following patch therefore will simply select the database entry with the smallest version number, i.e. OpenPKG-2.1.0-2.1.0 when deciding on wether it needs an update. [...] I've tested this patch. Now it works as expected for a RELEASE based OpenPKG instances, but on a CURRENT based OpenPKG instance (really all packages from CURRENT, no mix), it now tries there to always rebuild and upgrade an already up-to-date openpkg CURRENT package. I think we have to afford a special case here, haven't we? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Ever rebuilding openpkg-2.1.0
On Sun, Jul 25, 2004 at 12:03:09AM +0200, Ralf S. Engelschall wrote: On Sat, Jul 24, 2004, Michael van Elst wrote: [..] One could special case the openpkg package, but I'd like to avoid this if possible. The following patch therefore will simply select the database entry with the smallest version number, i.e. OpenPKG-2.1.0-2.1.0 when deciding on wether it needs an update. [...] I've tested this patch. Now it works as expected for a RELEASE based OpenPKG instances, but on a CURRENT based OpenPKG instance (really all packages from CURRENT, no mix), it now tries there to always rebuild and upgrade an already up-to-date openpkg CURRENT package. I think we have to afford a special case here, haven't we? Thanks to your last change it doesn't happen anymore :) | revision 1.349 | date: 2004-07-24 22:10:41 +; author: rse; state: Exp; lines: +1 -2 | remove useless Provides for the corresponding RELEASE version Greetings, -- Michael van Elst Internet: [EMAIL PROTECTED] A potential Snark may lurk in every tree. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
