Re: https://github.com/ilbers/hello conflicts with upstream hello

[Baurzhan Ismagulov <ibr@radix50.net>]

On Thu, Jan 17, 2019 at 05:10:02PM +0100, Henning Schild wrote:
> Yes, but conflicts that are known are mentioned in the metadata.
> (debian/control)
> So apt sees it before dpkg unpacks it and finds it.

Conflicts: isn't the only way to handle various kinds of interoperability
problems that arise in a large distribution like Debian. There are also
diversions, which allow installing packages with conflicting files by renaming
them in a controlled way after installation.


> I just sent a series that shows the problem. You can also see it if you
> IMAGE_INSTALL=example-hello and IMAGE_PREINSTALL=hello

I see, thanks.

I think we should use this opportunity to also rename the source package to
hello-isar to avoid conflicts with apt-get source hello.


> That or the metadata should know about the conflict. We can not change
> upstream metadata, maybe one side is good enough.

Conflicts: on the Isar side would be enough to make the packages incompatible,
but apt-get installing example-hello after hello would fail.


> One way or another. My series adds the feature to rebuild an upstream
> package, and hello is a very good example for that. A conflict would
> mean we could not test example-hello and hello in the same image, so
> avoiding the conflict will be useful for that case and not overkill.

I agree that using upstream hello would be nice. An alternative could be
building e.g. arc for the time being. In parallel, Maxim has started fixing
example-hello. I'd prefer merging your code without breaking example-hello.


With kind regards,
Baurzhan.