[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#891188: blends-dev: created d/control recommends packages not in main

Hi Ole,

On Thu, Mar 22, 2018 at 11:29:14AM +0100, Ole Streicher wrote:
> Control: affects -1 src:debian-astro
> On 22.03.2018 11:04, Andreas Tille wrote:
> > Control: severity -1 important
> Sure. Debian Astro the only one which is affected.

Thanks for confirming.
> I wrote:
> > In the moment, I would tend to rewrite blend-gen-control from scratch,
> > using Python 3 and the standard Debian Python packages (debian.deb822,
> > apt) in  a modular fashion.
> FYI, you may find the scratch development (to be integrated in the
> blends package) at
> https://salsa.debian.org/olebole/python-debian-blends
> Currently it is able to generate d/control with the help of (python-)
> apt, and it would resolve this bug. To replace the current
> blends-gen-control I still need to implement the generation of the
> tasks-desc file. Then (and after some finetuning) I would integrate this
> and create a new blends version for "experimental" (publish early,
> publish often). It would then also solve #764589, #785678, #825161, and
> #885145.

Sounds pretty cool!
> Reading the packages from UDD would follow then (taking the SQL
> statements from the GSOC approach) by implementing an "apt.Cache" like
> package repository that is built from UDD.

I do not mind much about the actual implementation.  If this "apt.Cache"
like will be able to reflect dependency of architecture.
> The structure of the package is a bit more complicated than just for
> d/control generation; the idea however is to re-use the same code for
> the Web pages.

Sounds very sensible!

> For this, it may be nice to have a separate Python package.

Perfectly fine for me.
> To get the documentation, do a `make html` in the doc subdir (needs
> sphinx installed).

I think that's just the code documentation not the general Blends
documentation which is currently in the same source package as
blends-dev, right?

> Package is tested under Python 3 only.

That's the only sensible approach.  We should get rid of any Python2
rather sooner than later.

Thanks a lot for your effort.  Its highly appreciated.

Kind regards


PS: Do you plan to also implement the dependency_data statistics?


Reply to: