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

Bug#739906: marked as done (svn-buildpackage: Generated .changes file has file size mismatch)

Your message dated Mon, 27 Nov 2017 20:50:46 -0500
with message-id <20171128015046.GA4220@hcoop.net>
and subject line Closing Bug
has caused the Debian Bug report #739906,
regarding svn-buildpackage: Generated .changes file has file size mismatch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
739906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739906
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Subject: svn-buildpackage: Generated .changes file has file size mismatch
Package: svn-buildpackage
Version: 0.8.5
Severity: normal

I'm filing this bug with svn-buildpackage because that's my interface
into the build system.  It seems likely the problem is some other
utility down below svn-buildpackage, but I'm not sure how to find it.
Feel free to reassign this somewhere else if you think that's
appropriate.

I maintain all of my packages with svn-buildpackage.  Today, I've built
and uploaded changes to every package.  I had no problems with any of
them other than epydoc.  With epydoc, I'm getting a file size mismatch
in the generated .changes file.  

Here's the command-line I'm using:

   > svn-buildpackage --svn-noautodch --svn-move-to=/home/pronovic/projects/debstage/jessie/amd64/epydoc --svn-tag --svn-retag

Once the build completes, I run lintian:

   > lintian --version 
   Lintian v2.5.21

   > lintian -I /home/pronovic/projects/debstage/jessie/amd64/epydoc/epydoc_3.0.1+dfsg-4_amd64.changes
   E: epydoc changes: file-size-mismatch-in-changes-file epydoc_3.0.1+dfsg-4.dsc 931 != 1160
   E: epydoc changes: file-size-mismatch-in-changes-file epydoc_3.0.1+dfsg-4.dsc 931 != 1160
   E: epydoc changes: file-size-mismatch-in-changes-file epydoc_3.0.1+dfsg-4.dsc 931 != 1160
   E: epydoc changes: checksum-mismatch-in-changes-file md5 epydoc_3.0.1+dfsg-4.dsc

Here's what the dsc file looks like on disk, showing that the size of
1160 bytes is correct:

   > ls -l /home/pronovic/projects/debstage/jessie/amd64/epydoc/epydoc_3.0.1+dfsg-4.dsc
   -rw-rw-r-- 1 pronovic pronovic 1160 Feb 23 18:21 /home/pronovic/projects/debstage/jessie/amd64/epydoc/epydoc_3.0.1+dfsg-4.dsc

When I look at the generated .changes file, the file length is correct
in the Checksums-Sha1 and Checksums-Sha256 sections, but incorrect in
the Files section:

   Checksums-Sha1: 
    51a9ecf8291ac13f43e571d30bb4b9c34dea05d2 1160 epydoc_3.0.1+dfsg-4.dsc
    a6bdd3dccef3db95503532247a018dac0a7f7b91 12892 epydoc_3.0.1+dfsg-4.debian.tar.xz
    6770bf66933abdd088271ff561f831818619526f 218512 python-epydoc_3.0.1+dfsg-4_all.deb
    3234b305a8a906c01f2031db3d1293c8f7ee297e 898542 epydoc-doc_3.0.1+dfsg-4_all.deb
   Checksums-Sha256: 
    06450f5382a588cd9de7807cffa6c50146e723218b563472569a7b0388b5b51c 1160 epydoc_3.0.1+dfsg-4.dsc
    0f2ee0137f3c550ec287322346828628d72317722b074239feae5affe3c06ead 12892 epydoc_3.0.1+dfsg-4.debian.tar.xz
    7dc9c3b03ae184f543f783031dd63603597eeedf6d79619804fb975550fafec9 218512 python-epydoc_3.0.1+dfsg-4_all.deb
    dc54ffc952ea60686451a47c8e8586506fbbf4796802645d19f90c48c4c502de 898542 epydoc-doc_3.0.1+dfsg-4_all.deb
   Files: 
    584c81f8310ad88dea8c38759b303ec1 931 python optional epydoc_3.0.1+dfsg-4.dsc
    aa24c6e9434891cd88cfe9a6641b5e18 12892 python optional epydoc_3.0.1+dfsg-4.debian.tar.xz
    94ea2f9724447b92243cd73339394b22 218512 python optional python-epydoc_3.0.1+dfsg-4_all.deb
    ae0ffe56fda45881415903044e07fdef 898542 doc optional epydoc-doc_3.0.1+dfsg-4_all.deb

I've never seen behavior like this before.  I'm kind of at a loss.  

I build all of my other packages using the exact same svn-buildpackage
command line, and everything works fine for those packages.  All of the
packages use source format 3.0, with very similar build processes.  I'm
executing the build in an amd64 schroot environment, which is up-to-date
as of earlier today.

Please let me know what I can do to help debug this.  The code is in a 
private svn repository, but I could send you a tarball of the latest
unreleased source tree, if you'd like.

Thanks,

KEN

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages svn-buildpackage depends on:
ii  devscripts              2.14.1
ii  file                    1:5.17-0.1
ii  libcapture-tiny-perl    0.24-1
ii  libfile-libmagic-perl   1.00-1
ii  liblocale-gettext-perl  1.05-7+b2
ii  libsvn-perl             1.8.8-1
ii  liburi-perl             1.60-1
ii  perl                    5.18.2-2
ii  subversion              1.8.8-1
ii  unp                     2.0~pre7+nmu1
ii  wget                    1.15-1

Versions of packages svn-buildpackage recommends:
ii  debhelper  9.20131227

svn-buildpackage suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
This bug report from 2014 never got a reply, and it doesn't
appear to happen any more.  Closing.

--- End Message ---
Reply to: