Bug#697602: Bug count confusion when unrelated binary and source has same name
Hi, On Tue, 15 Jan 2013 13:24:33 +0100 Philipp Kern pk...@debian.org wrote: On Mon, Jan 07, 2013 at 03:16:42PM +0100, Niels Thykier wrote: I'd seriously argue that one of the source packages has to change its name. I don't think that the two namespaces (source and binary packages) should be considered that separated, so that might warrant an addition to policy? (Do not build a binary package that has the name of a totally unrelated source package?) I seriously think that source and binary packages are separate namespace, and any tool that does trips over a conflict is probably not very clear about what its data actually means and should be improved for greater general robustness. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#697602: Bug count confusion when unrelated binary and source has same name
On Mon, Jan 07, 2013 at 03:16:42PM +0100, Niels Thykier wrote: If a source package produces and identically named binary (e.g. src:eclipse produces a binary named eclipse), it usually doesn't matter which of them gets the blame. The problem is when a binary has the same name as a source that _doesn't_ built it. An example in the archive being: source:sm builds binary r-cran-sm, source:screen-message builds binary sm If a BugsV file contains sm 123456 Britney will assume that RC bug applies to _both_ the source package sm and the binary sm (and thus screen-message). I'd seriously argue that one of the source packages has to change its name. I don't think that the two namespaces (source and binary packages) should be considered that separated, so that might warrant an addition to policy? (Do not build a binary package that has the name of a totally unrelated source package?) Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697602: Bug count confusion when unrelated binary and source has same name
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: britney Adam, Julien and I talked about this in #d-qa today and it turns out that Britney cannot reliably distinguish between RC bugs affecting source packages and RC bugs affecting binary packages. If a source package produces and identically named binary (e.g. src:eclipse produces a binary named eclipse), it usually doesn't matter which of them gets the blame. The problem is when a binary has the same name as a source that _doesn't_ built it. An example in the archive being: source:sm builds binary r-cran-sm, source:screen-message builds binary sm If a BugsV file contains sm 123456 Britney will assume that RC bug applies to _both_ the source package sm and the binary sm (and thus screen-message). ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
