On Mon, May 13, 2013 at 03:21:35PM +0200, Helmut Grohne wrote:
On Mon, May 13, 2013 at 11:48:06AM +0200, Goswin von Brederlow wrote:
Both cases would need data for multiple archs.
For the second case if identical files are in all foo_arch.deb then
those should be in foo-common_all.deb. A
On Tue, Apr 16, 2013 at 09:09:06PM +0200, Helmut Grohne wrote:
On Tue, Apr 16, 2013 at 03:04:20PM +0200, Goswin von Brederlow wrote:
Will that also detect files in multiarch packages that are not identical?
No, it does not do this at the moment. The main reason here is that
currently only
On Mon, May 13, 2013 at 11:48:06AM +0200, Goswin von Brederlow wrote:
Both cases would need data for multiple archs.
For the second case if identical files are in all foo_arch.deb then
those should be in foo-common_all.deb. A dedup across archs instead of
across packages.
Thanks for
On Sun, Apr 14, 2013 at 04:48:20PM +0800, Paul Wise wrote:
On Thu, Feb 21, 2013 at 9:54 PM, Paul Wise wrote:
For duplicate file detection, there is now the Debian duplication
detector (still importing the archive):
http://dedup.debian.net/
This will soon be linked to from the PTS for
On Tue, Apr 16, 2013 at 03:04:20PM +0200, Goswin von Brederlow wrote:
Will that also detect files in multiarch packages that are not identical?
No, it does not do this at the moment. The main reason here is that
currently only amd64 is processed. Support for multiple architectures
would take a
On Thu, Feb 21, 2013 at 9:54 PM, Paul Wise wrote:
For duplicate file detection, there is now the Debian duplication
detector (still importing the archive):
http://dedup.debian.net/
This will soon be linked to from the PTS for packages that share a
significant amount of data. Here is an
Hi,
recent discussion (e.g. w.r.t. jquery.js) has shown that Contents files
as is are not really suitable as a source for reporting bugs.
On my side I'd like to do further analysis on symlink vs. directory
conflicts and conffile takeovers (that may possibly corrupt the dpkg
database).
What would
For duplicate file detection, there is now the Debian duplication
detector (still importing the archive):
http://dedup.debian.net/
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Thu, Feb 21, 2013 at 09:54:54PM +0800, Paul Wise wrote:
For duplicate file detection, there is now the Debian duplication
detector (still importing the archive):
http://dedup.debian.net/
Neat!
Helmut, can you please add a footer to every dedup.d.n page stating: who
is in charge of the
Since Paul Wise advertised dedup.debian.net already, I have a few more
bits.
This was an afternoon proof-of-concept thingy that kind of accidentally
got a debian.net pointer, but so be it. It seems to be somewhat useful.
The service basically records checksums of all regular files in Debian
sid
On Thu, Feb 21, 2013 at 03:48:20PM +0100, Helmut Grohne wrote:
The software is available in
git://murkel.subdivi.de/~helmut/debian-dedup.git, but currently lacks
any documentation. (Hey it was just a proof-of-concept, right?)
All data is obtained by examining binary packages and stored in a
[You set mail-follow-up to debian-devel, so here it goes to the list.]
On 21-02-13 15:48, Helmut Grohne wrote:
So yeah, bug reports, comments and of course patches are welcome.
This indeed looks very useful. However, I don't think it is really
useful to trigger on common changelog and copyright
On 13129 March 1977, Helmut Grohne wrote:
This was an afternoon proof-of-concept thingy that kind of accidentally
got a debian.net pointer, but so be it. It seems to be somewhat useful.
The service basically records checksums of all regular files in Debian
sid main and provides a web
On Thu, Feb 21, 2013 at 07:05:08PM +0100, Paul Gevers wrote:
This indeed looks very useful. However, I don't think it is really
useful to trigger on common changelog and copyright files from the same
source package as they indeed usually are the same, which is fine of course.
Answering this
14 matches
Mail list logo
