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

Bug#825650: libreoffice-common: prompting due to modified conffiles which were not modified by the user: /etc/libreoffice/sofficerc



tag 825650 + moreinfo
tag 825650 + help
thanks

Hi,

On Sat, May 28, 2016 at 03:29:39PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed the piuparts
> upgrade test because dpkg detected a conffile as being modified and then

> prompted the user for an action. As there is no user input, this fails.
> But this is not the real problem, the real problem is that this prompt
> shows up in the first place, as there was nobody modifying this conffile
> at all, the package has just been installed and upgraded...
>
> This is a violation of policy 10.7.3, see
> https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
> which says "[These scripts handling conffiles] must not ask unnecessary
> questions (particularly during upgrades), and must otherwise be good
> citizens."

Nothing in LO touches (or even touched) sofficerc...
 
> https://wiki.debian.org/DpkgConffileHandling should help with figuring
> out how to do this properly.

Yeah, I "like" templates. Especially if we don't do manual stuff with soffice
at all, so I don't see how that one applies here.

> In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
> followups it has been agreed that these bugs are to be filed with
> severity serious.
> 
> >From the attached log (scroll to the bottom...):

The attached log says openoffice.org-common. That one doesn't exist since
ages. (Yeah, I know it exists in squeeze.)

>   Setting up libreoffice-common (1:5.1.3-1) ...
>   
>   Configuration file '/etc/libreoffice/sofficerc'
>    ==> Modified (by you or by a script) since installation.
>    ==> Package distributor has shipped an updated version.
>      What would you like to do about it ?  Your options are:
>       Y or I  : install the package maintainer's version
>       N or O  : keep your currently-installed version
>         D     : show the differences between the versions
>         Z     : start a shell to examine the situation
>    The default action is to keep your current version.
>   *** sofficerc (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package libreoffice-common (--configure):
>    end of file on stdin at conffile prompt
> 
> This was observed on an upgrade from squeeze (openoffice) =>

Which openoffice package? There was no openoffice in squeeze? Do you mean
openoffice.org? (Yes, "OpenOffice.org" was the name, not "OpenOffice")

> wheezy (libreoffice) => jessie => stretch. Only the last step
> (jessie->stretch) failed.

So you started from oldoldstable which didn't even have libreoffice.

I don't belive upgrade bugs from squeeze are (still) RC, even if the actual
problem arrives now at jessie->stretch.

But let's try it:

- jessie cowbuilder + libreoffice -> stretch: works
- wheezy cowbuilder + libreoffice -> jessie -> stretch: works
- debootstrap squeeze from archive.debian.org + openoffice.org
  -> wheezy -> jessie -> stretch (which you say this is about): running, will
  take, will report back.

(I think any upgrade here just involving
openoffice.org-common/libreoffice-common and not "the rest" is artificial.
But one can try this, too...)

The only thing (see above) which _was_ done with sofficerc was this:

        if [ -n "$2" ] && dpkg --compare-versions "$2" lt "1:3.3.0-3"; then
[...]
        dpkg-maintscript-helper mv_conffile \
                "/etc/openoffice/sofficerc" "/etc/libreoffice/sofficerc" "" libreoffice-common -- "$@"
[...]

in libreoffice-commons postinst/postrm/preinst

But interestingly, in your log this only happened on the wheezy->jessie upgrade,
while it should already have been done in the squeeze->wheezy one. So
maybe dpkg gets confused because the mv_conffile is done "one release late"?

In any case, I don't see what to do here and how to fix *current* packages.

Regards,

Rene


Reply to: