[Pkg-emacsen-addons] Bug#893598: Bug#893598: yasnippet-snippets: Error while updating

[Nicholas D Steeves]

Control: tags -1 confirmed

Hi Axel,

Thank you for confirming this bug!

On Tue, Mar 20, 2018 at 10:44:34PM +0100, Axel Beckert wrote:
> Hi Nicholas,
> 
> I just experienced the (probably) same issue:
> 
> Preparing to unpack .../87-yasnippet-snippets_0~git20180307.2b4c4d7e-1_all.deb ...
> Unpacking yasnippet-snippets (0~git20180307.2b4c4d7e-1) over (0~git20161123-1) ...
> dpkg: error processing archive /tmp/apt-dpkg-install-lJHmtd/87-yasnippet-snippets_0~git20180307.2b4c4d7e-1_all.deb (--unpack):
>  unable to open '/usr/share/yasnippet-snippets/clojure-mode/.yas-parents.dpkg-new': No such file or directory
> Errors were encountered while processing:
>  /tmp/apt-dpkg-install-lJHmtd/87-yasnippet-snippets_0~git20180307.2b4c4d7e-1_all.deb
> 
> Nicholas D Steeves wrote:
> > Is /usr or /usr/share a symlink or bind mount to somewhere else, or
> > are either of them mounted via NFS?
> 
> Not in my case:
> 
> → mount | fgrep usr
> → ls -ldF /usr /usr/share
> drwxr-xr-x  12 root root  4096 Feb 28 05:29 /usr/
> drwxr-xr-x 990 root root 32768 Mar 20 22:01 /usr/share/
> 
> > Also, will the following
> > commands reproduce "unable to open
> > '/usr/share/yasnippet-snippets/clojure-mode/.yas-parents.dpkg-new': No
> > such file or directory"?
> [...]
> > curl -O https://debian.org/debian/pool/main/y/yasnippet-snippets/yasnippet-snippets_0~git20161123-1_all.deb
> 
> JFTR: This is no valid Debian mirror URL.

Oh my, sorry about that!  I guess this one will have to do:
    http://ftp.debian.org/debian/pool/main/y/yasnippet-snippets/yasnippet-snippets_0~git20161123-1_all.deb

> Anyway, I first purged yasnippet-snippets (0~git20161123-1 was still
> installed due to the failed upgrade), then I installed
> yasnippet-snippets 0~git20161123-1 from Debian Testing again. Then I
> tried to upgrade yasnippet-snippets to 0~git20180307.2b4c4d7e-1 from
> Debian Unstable again:
> 
> [...]
> Removing yasnippet-snippets (0~git20161123-1) ...
> [...]
> Selecting previously unselected package yasnippet-snippets.
> (Reading database ... 1040898 files and directories currently installed.)
> Preparing to unpack .../yasnippet-snippets_0~git20161123-1_all.deb ...
> Unpacking yasnippet-snippets (0~git20161123-1) ...
> Setting up yasnippet-snippets (0~git20161123-1) ...
> [...]
> Preparing to unpack .../yasnippet-snippets_0~git20180307.2b4c4d7e-1_all.deb ...
> Unpacking yasnippet-snippets (0~git20180307.2b4c4d7e-1) over (0~git20161123-1) ...
> Setting up yasnippet-snippets (0~git20180307.2b4c4d7e-1) ...
> [...]
> 
> So, no, if the initially installed yasnippet-snippets version is
> 0~git20161123-1, the issue doesn't seem to happen.
> 
> Which leaves the question: Upgrading from which version does exhibit
> that behaviour?
> 
> In my case it was an Debian Unstable which has been upgraded
> regularily since its installation on 2014-04-08. yasnippet-snippets
> has been first installed in version 0~git20150512-1 on Thu May 28
> 19:16:25 2015 +0200.

Thank you very much for this information!  Luckily the only three
versions are: 0~git20150512-1, 0~git20161123-1, and
0~git20180307.2b4c4d7e-1.

Because http://archive.debian.net is not available I'll try building
these three versions, purging my current 0~git20180307.2b4c4d7e-1, and
then sequentially installing/upgrading.  My hypothesis is now that
this bug is cause by an artifact introduced by upgrading from the 2015
to 2016 version.


Time to test!
Nicholas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-emacsen-addons/attachments/20180320/1e343b82/attachment.sig>