Won't fix +1
Pre-Depends is really an easy work-around!!
I see problems with dpkg-divert, but I also see work-arounds and room
for discussions and improvements of individual packages. I don't think
we need to say that "dpkg-divert" should be discouraged because of
debian policy, nor do I see a ne
Regarding the discussion about dpkg-divert: It's inevitable -- I wanna
change something in nginx.conf that's not possible to change elsewhere
because /etc/nginx/conf.d is only loaded in the http { ... } segment:
2015/11/11 22:29:32 [emerg] 15102#0: "worker_processes" directive is not
allowed here
Just read this:
> > Conceptually, a diverting package actually pre-depends on the package
> > being diverted.
Furthermore:
> Current behaviour of dpkg-divert is not an excuse to retain it, IMHO.
> Conceptually, dpkg-divert in preinst scripts is just wrong.
>From this discussion:
https://lists.
@Thomas Ward
Firstly, a correction: 14.04 also has the issue, I was looking at the wrong
file (
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/nginx/trusty/view/head:/debian/nginx-core.postinst
is correct )
Let me try to summarize the issue a little better:
You have a package, john
I'm going to take a wild guess that the issue is because vivid's nginx-
common.postinst has this line:
invoke-rc.d nginx start || exit $?
Which will make postinst fail if nginx fails to start for the first
time.
15.04:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/vivid/nginx/vivid/view/
Public bug reported:
On 14.04, adding a divert for /etc/nginx/nginx.conf would have the
package installation and configuration proceed after installing with
just one error:
Setting up nginx-common (1.4.6-1ubuntu3.3) ...
Processing triggers for ufw (0.34~rc-0ubuntu2) ...
Processing triggers for ur
