Re: Non-normalised field Provides in UDD table

2018-04-12 Thread Andreas Tille
On Thu, Apr 12, 2018 at 09:22:35PM +0200, Ole Streicher wrote: > > If there are no other urgent things, I would like to upload the new > version (to experimental? or directly to unstable?). Remember, it will > go through NEW (new binary python3-blends) and so take some time. H, diff --git

Re: Non-normalised field Provides in UDD table

2018-04-12 Thread Andreas Tille
Hi Ole, On Thu, Apr 12, 2018 at 04:56:25PM +0200, Ole Streicher wrote: > I extended the queries to allow multiple (and even versionized) provides. Cool. > Andreas Tille writes: > > > > Yes. The package filo is missing and bedtools provides it. That's a > > hint to fix the

Re: Non-normalised field Provides in UDD table

2018-04-12 Thread Ole Streicher
Hi Andreas, I extended the queries to allow multiple (and even versionized) provides. Andreas Tille writes: >> > It has another really great feature. It has the following warning >> > output: >> > >> > WARNING:__main__:"filo" has been replaced with "bedtools" >> >> Where

Re: Non-normalised field Provides in UDD table

2018-04-12 Thread Andreas Tille
On Thu, Apr 12, 2018 at 12:02:38PM +0200, Ole Streicher wrote: > > > It has another really great feature. It has the following warning > > output: > > > > WARNING:__main__:"filo" has been replaced with "bedtools" > > Where does it get this from? Is this issued when "filo" is a "Provides"? See

Re: Non-normalised field Provides in UDD table

2018-04-12 Thread Andreas Tille
Hi Ole, On Thu, Apr 12, 2018 at 12:02:38PM +0200, Ole Streicher wrote: > Andreas Tille writes: > > I mean we need different metapackages for say amd64, arm64, i386, etc. > > I agree that this is no solution for MultiArch but from my point of > > view that's rather a corner

Re: Non-normalised field Provides in UDD table

2018-04-12 Thread Ole Streicher
Hi Andreas, Andreas Tille writes: > On Wed, Apr 11, 2018 at 10:02:39PM +0200, Ole Streicher wrote: >> We had a short discussion in >> >> https://lists.debian.org/debian-blends/2018/03/msg00059.html >> >> and your answer. Do you mean something more? > > I mean we need