Bug#423041: binNUMUs - all-depends-any
Hi, I know that the git-core package doesn't support binNMUs, and AFAIK there's no convenient way to change that, as it builds arch: all package that depend on the specific arch: any package. http://bugs.debian.org/423041 Loosening the dependencies as suggested in http://wiki.debian.org/binNMU isn't a good solution, as it can lead to http://bugs.debian.org/425494 Can I register the package as non-binNMUable anywhere?, it needs a sourceful upload anyway. http://bugs.debian.org/430128 Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423041: binNUMUs - all-depends-any
Gerrit Pape [EMAIL PROTECTED] writes: Hi, I know that the git-core package doesn't support binNMUs, and AFAIK there's no convenient way to change that, as it builds arch: all package that depend on the specific arch: any package. http://bugs.debian.org/423041 Loosening the dependencies as suggested in http://wiki.debian.org/binNMU isn't a good solution, as it can lead to http://bugs.debian.org/425494 The recommendation for cases like this is to use a dependency like: git-core (= 1:1.5.2.2-1), git-core ( 1:1.5.2.2-2~) or a bit looser if the Debian revision won't matter: git-core (= 1:1.5.2.2), git-core ( 1:1.5.2.3~) -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423041: binNUMUs - all-depends-any
Gerrit Pape [EMAIL PROTECTED] writes: Hi, I know that the git-core package doesn't support binNMUs, and AFAIK there's no convenient way to change that, as it builds arch: all package that depend on the specific arch: any package. http://bugs.debian.org/423041 Loosening the dependencies as suggested in http://wiki.debian.org/binNMU isn't a good solution, as it can lead to http://bugs.debian.org/425494 Is there a reason why a set of dependencies that only allow package versions based on the same upstream version to be installed wouldn't work? [1] Marc Footnotes: [1] For a package foo-bar, this would mean that deps should be like foo-bar (= 1.2.3), foo-bar ( 1.2.4~) (or something similiar) -- Fachbegriffe der Informatik - Einfach erklärt 67: Für mich steht die Kommunikation im Vordergrund Ich weiß, daß mein Gateway Mist baut, aber das ist mir egal. (Arno Eigenwillig) pgpMcXs0hfNGv.pgp Description: PGP signature
Bug#423041: binNUMUs - all-depends-any
On Sat, Jun 23, 2007 at 11:31:49AM +0200, Marc 'HE' Brockschmidt wrote: Gerrit Pape [EMAIL PROTECTED] writes: Hi, I know that the git-core package doesn't support binNMUs, and AFAIK there's no convenient way to change that, as it builds arch: all package that depend on the specific arch: any package. http://bugs.debian.org/423041 Loosening the dependencies as suggested in http://wiki.debian.org/binNMU isn't a good solution, as it can lead to http://bugs.debian.org/425494 Is there a reason why a set of dependencies that only allow package versions based on the same upstream version to be installed wouldn't work? [1] [1] For a package foo-bar, this would mean that deps should be like foo-bar (= 1.2.3), foo-bar ( 1.2.4~) (or something similiar) That'd work. I was hoping, with the increased usage of binNMUs, there's something more convenient than changing debian/control by hand. I'll now go with Depends: git-core ( ${source:Upstream-Version}, git-core ( ${source:Upstream-Version}-.) I think. Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]