Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #735713 > unrolled thread

Bug#823138: python-djvulibre: please make the build reproducible on i386

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#823138: python-djvulibre: please make the build reproducible on i386 Daniel Stender <stender@debian.org> - 2016-05-01 13:00 +0200
    Bug#823138: [Reproducible-builds] Bug#823138: python-djvulibre: please make the build reproducible on i386 Mattia Rizzolo <mattia@debian.org> - 2016-05-01 13:10 +0200
      Bug#823138: [Reproducible-builds] Bug#823138: python-djvulibre: please make the build reproducible on i386 Jakub Wilk <jwilk@debian.org> - 2016-05-01 13:40 +0200

#735713 — Bug#823138: python-djvulibre: please make the build reproducible on i386

Source: python-djvulibre
Version: 0.7.1-1
Severity: wishlist

python-djvulibre doesn't build reproducible on i386. I can't tell yet
what's the problem here, but I'll get into this, soon.

Thanks,
DS

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[toc] | [next] | [standalone]

#735717 — Bug#823138: [Reproducible-builds] Bug#823138: python-djvulibre: please make the build reproducible on i386

[Multipart message — attachments visible in raw view] — view raw

control: user reproducible-builds@lists.alioth.debian.org
control: usertag -1 environment

On Sun, May 01, 2016 at 12:51:32PM +0200, Daniel Stender wrote:
> Source: python-djvulibre
> Version: 0.7.1-1
> Severity: wishlist
> 
> python-djvulibre doesn't build reproducible on i386. I can't tell yet
> what's the problem here, but I'll get into this, soon.

That's due to different kernel.

One builder has a 32 bit kernel, the other a 64 bit ones, both with a 32
bit userland.

At least to me it looks like it is saving that information, then causing
offsets everywhere.

│   │   │   │   │ -  1	build/temp.linux-i686-2.7-pydebug/src
│   │   │   │   │ +  1	build/temp.linux-x86_64-2.7-pydebug/src

(most probably, what is causing the offsets is DW_AT_name, not this line
I reported, but this is shorter)

No clue about what does that, nor anything else, just read the
diffoscope report.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[toc] | [prev] | [next] | [standalone]

#735726 — Bug#823138: [Reproducible-builds] Bug#823138: python-djvulibre: please make the build reproducible on i386

* Mattia Rizzolo <mattia@debian.org>, 2016-05-01, 11:07:
>│   │   │   │   │ -  1	build/temp.linux-i686-2.7-pydebug/src
>│   │   │   │   │ +  1	build/temp.linux-x86_64-2.7-pydebug/src

From the upstream changelog:

>   + Put files that vary with Python version (*.c, config.pxi) into a
>     version-specific temporary directory.

The problem is that, as seen above, distutils puts the platform name in 
the temporary build directory name; and the platform name depends on 
uname:

$ linux32 python -c 'import distutils.util as u; print u.get_platform()'
linux-i686
$ linux64 python -c 'import distutils.util as u; print u.get_platform()'
linux-x86_64

So ideally this should be fixed in distutils. But it should be possible 
to work around this by passing appropriate --build-temp to "setup.py 
build".

(No clue about the Debian package, just being upstream.)

-- 
Jakub Wilk

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web