Re: From srebuild sbuild-wrapper to debrebuild

[Johannes Schauer]

Hi,

Quoting HW42 (2016-11-17 05:10:00)
> After discussing this in the irc meeting yesterday I propose that:
> 
>  - we keep it as a separate tool.
>  - put it in a git repo under
>https://anonscm.debian.org/git/reproducible/
>  - We have more than enough DDs who are willing to sponsor uploads, so
>having it in the Debian archive is no problem.
>  - we mainly maintain this as a group. I will try to especially keep an
>eye on it.
> 
> Since you have done all the work so far the final decision is obviously
> up to you.
> 
> If the above is fine with you I will prepare packaging it during the next
> week (I also have a few improvements planed).

please go ahead.

I'll make sure that sbuild adds a facility to receive a full binNMU changelog
entry from the user.

Thanks!

cheers, josch


signature.asc
Description: signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: From srebuild sbuild-wrapper to debrebuild

[HW42]

Johannes Schauer:
> Hi,
> 
> On Thu, 10 Nov 2016 05:54:13 -0200 Johannes Schauer  wrote:
>> On Tue, 02 Aug 2016 22:49:00 +0200 Johannes Schauer  wrote:
>>> But then on IRC, HW42 suggested to approach this problem differently.
>>> Instead of integrating the functionality of figuring out the right
>>> repositories to reproduce the contents of a buildinfo file into sbuild,
>>> write a tool that can drive any package builder (like pbuilder).
> 
> there seems to be a conceptual problem with such an approach.
> 
> For binNMUs, the full changelog entry has to be passed to sbuild or pbuilder.
> How does one best pass such a multi-line value via command line options? Would
> the best way to pass the changelog entry via the .buildinfo file? And if
> pbuilder and sbuild then already are parsing the .buildinfo file, would it not
> be better for the debrebuild machinery to be implemented by either in the 
> first
> place?

Since this is somewhat relevant to the discussion in the other part of
this thread: I don't think this is a conceptual problem. Sure it could
be nicer if we don't had binNMUs, but I see no real problem in passing
it via cmd line option or via a plain file. I would anyway modify
debrebuild to be able to call sbuild/pbuiler/etc. directly and then you
are able to use a tempfile cleanly.



signature.asc
Description: OpenPGP digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: From srebuild sbuild-wrapper to debrebuild

[HW42]

Johannes Schauer:
> Hi all,
> 
> On Tue, 02 Aug 2016 22:49:00 +0200 Johannes Schauer  wrote:
>> I was thinking about this issue again and thought that instead of creating a
>> wrapper for sbuild which then uses a chroot-setup hook to install the
>> dependencies, what I should instead do is to let sbuild itself accept
>> .buildinfo files and then do the right thing like:
>>
>>  - use snapshot.d.o to retrieve the right timestamps needed to gather all
>>packages
>>  - mangle the build dependencies such that the source package now depends on
>>the exact right package versions and let the resolver figure out the rest
>>(thanks Benjamin for that idea)
>>  - check whether the generated binaries produce the same checksum as given in
>>the supplied buildinfo file
>>
>> But then on IRC, HW42 suggested to approach this problem differently. Instead
>> of integrating the functionality of figuring out the right repositories to
>> reproduce the contents of a buildinfo file into sbuild, write a tool that can
>> drive any package builder (like pbuilder).
>>
>> I now wrote such a script.
> 
> now that libdpkg-perl comes with support for .buildinfo files, I improved the
> script (new version attached) with the following changes:
> 
>  - don't use DateTime::Format::Strptime but Time::Piece instead (which is a
>perl core module)
>  - don't use CTRL_INDEX_SRC but CTRL_FILE_BUILDINFO now that dpkg supports
>.buildinfo files
>  - Dpkg::Compression::FileHandle as it is not needed
>  - the .dsc file name is no longer part of the .buildinfo file, so assemble 
> the
>.dsc file name from the package name and version using 
> Dpkg::Source::Package
>  - use the information from the Environment field
>  - instead of splitting Installed-Build-Depends manually, use
>Dpkg::Deps::deps_parse
>  - instead of using [trusted=yes], retrieve the gpg key of the reproducible
>builds repository and verify its fingerprint
>  - set Binary::apt-get::Acquire::AllowInsecureRepositories to false so that
>apt-get fails to update repositories it cannot authenticate
>  - use Dpkg::Vendor to retrieve the keyring filenames
> 
> Thanks to Guillem Jover for the code review!

After discussing this in the irc meeting yesterday I propose that:

 - we keep it as a separate tool.
 - put it in a git repo under
   https://anonscm.debian.org/git/reproducible/
 - We have more than enough DDs who are willing to sponsor uploads, so
   having it in the Debian archive is no problem.
 - we mainly maintain this as a group. I will try to especially keep an
   eye on it.

Since you have done all the work so far the final decision is obviously
up to you.

If the above is fine with you I will prepare packaging it during the next
week (I also have a few improvements planed).



signature.asc
Description: OpenPGP digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Bug#821793: fusermount should not attempt to use /etc/mtab

[Ximin Luo]

Nikolaus Rath:
> Can someone clarify if this is a bug in upstream fuse (which assumes
> existence of /etc/mtab) or in the software that creates the chroots
> without /etc/mtab?
> 
> If someone can give me a decent source that states that /etc/mtab does
> not need to exist, I'll be happy to change fusermount accordingly. 
> 

Hi Nikolaus,

It's hard to find an "authoritative" source for this but:

http://man.cat-v.org/unix_8th/5/mtab
"It does not matter to mount if there are duplicated entries nor to umount if a 
name cannot be found."

https://www.gnu.org/software/libc/manual/html_node/Mount-Information.html
"Note that the fstab and mtab files are maintained on a system by convention. 
It is possible for the files not to exist or not to be consistent with what is 
really mounted or available to mount, if the system’s administration policy 
allows it. But programs that mount and unmount filesystems typically maintain 
and use these files as described herein."

https://unix.stackexchange.com/questions/24182/how-to-get-the-complete-and-exact-list-of-mounted-filesystems-in-linux
"The definitive list of mounted filesystems in in /proc/mounts... [etc why 
/etc/mtab sometimes differs]".

In other words it's generally understood that /etc/mtab might not reflect 
"reality" and so fusermount shouldn't be relying on it to make decisions.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Bug#821793: fusermount should not attempt to use /etc/mtab

[Nikolaus Rath]

Hi,

Can someone clarify if this is a bug in upstream fuse (which assumes
existence of /etc/mtab) or in the software that creates the chroots
without /etc/mtab?

If someone can give me a decent source that states that /etc/mtab does
not need to exist, I'll be happy to change fusermount accordingly. 

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

New "reproducible-bugs" mailing list

[Chris Lamb]

Dear all,

It was agreed at the IRC meeting last night that we create a separate
mailing list for bugs submitted "on behalf of" the Reproducible Builds
project.

These bugs include patches submitted to other packages as well as QA and
FTBFS work; the intention is to prevent human-oriented discussions being
obscured.

(Bugs regarding our own tools, such as disorderfs and diffoscope will
continue to be sent to the existing list.)


What you need to do
===

a) If you wish to receive these bugs, you will need to subscribe to the
   new list:

 https://lists.alioth.debian.org/mailman/listinfo/reproducible-bugs


b) When filing bugs against other Debian packages, where you had been
   filing with an "X-Debbugs-CC" pseudo-header of reproducible-builds@,
   please replace that with:

   reproducible-b...@lists.alioth.debian.org

   (It is conceivable that for some important bugs it may make more sense
   to use the -builds address to ensure a wider audience. Feel free to do
   so in those circumstances.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Next Reproducible Builds IRC meeting on 29 Nov 2016 at 18h00 UTC

[Chris Lamb]

Dear all,

Thanks to all who attended the IRC meeting last night. The minutes and
logs are available here:

  
http://meetbot.debian.net/reproducible-builds/2016/reproducible-builds.2016-11-15-17.59.html

The next meeting will be held at:

   http://time.is/compare/1800_29_Nov_2016_in_UTC


The meeting will be held on #reproducible-builds on OFTC, will start promptly
and will last no longer than 1 hour. The meeting will be logged.

The audience is for anyone interested in the Reproducible Builds effort,
regardless of the project(s) they contribute to. :)


What you need to do
===

 a) Convert the above time in your timezone and add to your diary/planner. To
reliably translate with respect to DST changes I suggest using a link such
as:

  http://time.is/compare/1800_29_Nov_2016_in_UTC/Singapore

 b) Please add any agenda items to:

  https://pad.riseup.net/p/reproducible-irc-meeting-5

Items should be suffixed with your name.

 c) Forward this email to anyone you feel would be interested.

 d) If you cannot make it (but would have liked to) please addyourself to
the "Apologies" section on the agenda above.

Thanks again and looking forward to see you there.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Bug#821793: fusermount should not attempt to use /etc/mtab

[Ximin Luo]

Control: affects -1 disorderfs
Control: affects -1 devscripts
Control: affects -1 reprotest

debrepro from devscripts, and reprotest, both use disorderfs. When cleaning up 
a build, they try to unmount the disorderfs filesystem using `fusermount -u` 
which doesn't work inside an schroot since it doesn't have /etc/mtab.

The workaround is to manually use "sudo umount" but this requires root access. 
Or symlink /etc/mtab to /proc/self/mounts.

X

On Mon, 23 May 2016 08:22:03 -0700 Nikolaus Rath  wrote:
> Hi Santiago,
> 
> On May 21 2016, Santiago Vila  wrote:
> > Hello Nikolaus and Laszlo.
> >
> > A recent build of python-llfuse does not fail to build anymore
> > in my /etc/mtab-less chroot.
> >
> > Has this bug been fixed in fusermount?
> >
> > This is likely but I'm not confindent enough to close this bug myself.
> > Could any of you check this?
> 
> The problem has not been fixed upstream. But maybe Laszlo has added a
> Debian patch?
> 
> Best,
> -Nikolaus
> 
> -- 
> GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
> Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
> 
>  »Time flies like an arrow, fruit flies like a Banana.«
> 
> 

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#844512: reprotest: make diffoscope optional

[Ximin Luo]

Package: reprotest
Version: 0.3.2
Severity: wishlist

Dear Maintainer,

It would be good to make diffoscope optional. Sometimes for various reasons a
developer might want to run reprotest inside a container/chroot/environment
where they don't want to install diffoscope. Then reprotest should save the
build output so the user can copy it to a system that does have diffoscope.

For example I have access to a remote jessie machine, so I have to run all my
builds inside a schroot already. Inside the schroot I run reprotest with a null
virtual server, but I don't want diffoscope's dependencies to possibly affect
the build.

(Yes I could use another schroot inside the schroot but I have a feeling this
wouldn't work so well and I'd rather not spend time debugging it. Also this
would not be possible on Debian porter machines where we don't have root to be
able to set up the inner schroots.)

X

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages reprotest depends on:
ii  apt-utils  1.3.1
ii  diffoscope 62
ii  libdpkg-perl   1.18.10
ii  procps 2:3.3.12-2
ii  python3-debian 0.1.29
ii  python3-pkg-resources  28.0.0-1
pn  python3:any

Versions of packages reprotest recommends:
ii  autodep8 0.8
ii  disorderfs   0.5.1-1
ii  locales-all  2.24-5
ii  qemu-system  1:2.7+dfsg-3
ii  qemu-utils   1:2.7+dfsg-3
ii  schroot  1.6.10-2+b1

reprotest suggests no packages.

-- no debconf information

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

За първи път на българската сцена - Moscow City Ballet

[Московски сити балет]

 
 
 
 
 
 


   За първи път
на българската сцена Moscow City Ballet
представя:   РОМЕО И ЖУЛИЕТА „И до
днес светът не знае любов по-чиста и
съдба 
 по-клета от
тази на Ромео и Жулиета.”
„Ромео и
Жулиета” е една от най-интригуващите
балетни постановки, смятана днес за част
от съкровищницата на класическия балет.
Драматичният спектакъл, разказващ
най-известната любовна история на всички
времена, ще бъде представен на българска
сцена от известната руска балетна трупа
„Московският сити балет”.Ценителите на балетното изкуство у нас,
ще могат да видят уникалният спектакъл
на 24-ти ноември в София в зала 1 на
НДК, на 26-ти ноември във Варна в
Дворецът на културата и спорта и на
27- ноември в Бургас в Държавната
Опера. Билетите варират от 30лв. до
90лв. и могат да бъдат закупени в мрежата
на EVENTIM. 

Премиерата
на балета, поставен за пръв път от Леонид
Лавровски, с Галина Уланова в ролята на
Жулиета, се е състояла в Санкт Петербург,
на 11 януари 1940 година, на сцената на
Маринския театър.Музиката е на
Сергей Прокофиев, която по
художествената си стойност и силата на
емоционално въздействие не отстъпва на
Шекспировата трагедия. „Московският
сити балет” ще представи постановката
за първи път в България. Над петдесет
балетисти ще разказват, чрез необичайна
комбинация от спиращи дъха хореографии,
ослепителни костюми и впечатляващи
танци, за фаталната обреченост на
любовта и невъзможността тя да се
реализира в света на враждуващите
фамилии.Автор на хореографията и
постановката е Виктор Смирнов-Голованов,
бивш солист на Болшой балет и създател на
Московския сити балет. В главните роли ще
се превъплътят някои от известните руски
балетни артисти - Талгат Коджабаев, Лилия
Орекхова, Андрей Журавлев, Анна Ижанова и
Юлия Журавлева. Действието се развива в
тринадесет сцени, под съпровода на
музиката на един от най-великите
композитори на 20 век. Сергей Прокофиев. 


 






 Съгласно ЗЕТ Ви съобщаваме, че
това търговско съобщение може да не е
поискано предварително от Вас. Ако не
искате да получавате повече съобщения за
"Московски Сити Балет", моля
натиснете ОТПИСВНАЕ
линка на брошурата за автоматично
отписван! Ако сме Ви притеснили, моля да
ни извините.





___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#844498: disorderfs: using it for building kills the host (with a 686 kernel)

[Holger Levsen]

Package: disorderfs
Version: 0.5.1-1
Severity: normal

Hi,

so we had disorderfs disabled for a long time on our reproducible setup
and yesterday I enabled it again for i386 only, which rather immediatly
caused profitbricks-build2-i386.debian.net to hang/die… so I rebootet it
and logged in to investigate…

and while watched diskspace… and suddenly the host was "gone". I observed this
as I typed "ps fax|grep wesnot" in another shell. Also Trying to ssh in 
resulted 
in this:

$ ssh profitbricks-build2-i386.debian.net 
Last login: Wed Nov 16 10:14:27 2016 from …

and hangs there.

So "killing the host" means: the kernel and processes are still running but
are stuck on io, eg I had "watch df" running in an ssh session, it was
not updating anymore but I could ctrl-c it and get back to the shell
prompt. as soon as i pressed enter on a command, it hung.

Interesting, disorderfs was used on two hosts, but this only happened on pb2,
but not pb6! pb2 is running 3.16.0-4-686-pae while pb6 is running 3.16.0-4-amd64
(and both run i386 userland).

Thogh it's unclear whether it would not also "kill" pb6 if we were using it
long enough.

Also, using disorderfs for a few jobs seems to be fine, but there are 8 pbuilder
jobs running simultaenously on each of these hosts and half of them are using
disorderfs.

Next easy tests:
- enable disorderfs on some armhf hosts (running 32bit kernels too)
- upgrade pb2 to a 4.7 bpo 686 kernel
- eneable disorderfs on amd64


-- 
cheers,
Holger


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#844493: twisted-web2: FTBFS: twisted.python.dist module not found

[Chris Lamb]

Source: twisted-web2
Version: 8.1.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

twisted-web2 fails to build from source in unstable/amd64:

  […]

  
   debian/rules build
  python2.7 setup.py build
  twisted.python.dist module not found.  Make sure you have installed the 
Twisted core package before attempting to install any other Twisted projects.
  debian/rules:13: recipe for target 'build-python2.7' failed
  make: *** [build-python2.7] Error 1

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


twisted-web2.8.1.0-3.unstable.amd64.log.txt.gz
Description: Binary data
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#844491: linux-atm: FTBFS: time.h:9:8: error: redefinition of 'struct timespec'

[Chris Lamb]

Source: linux-atm
Version: 1:2.5.1-1.6
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

linux-atm fails to build from source in unstable/amd64:

  […]

(void) write(1,rotor[i = (i+1) & 3],2);
^~
  mv -f .deps/aping.Tpo .deps/aping.Po
  /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -I../../src/include -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes  
-Wl,-z,relro -o aping aping.o ../../src/lib/libatm.la 
  libtool: link: gcc -I../../src/include -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wl,-z 
-Wl,relro -o .libs/aping aping.o  ../../src/lib/.libs/libatm.so
  gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2  
-I../../src/include -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -MT br.o -MD 
-MP -MF .deps/br.Tpo -c -o br.o br.c
  mv -f .deps/br.Tpo .deps/br.Po
  /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -I../../src/include -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes  
-Wl,-z,relro -o br br.o ../../src/lib/libatm.la 
  libtool: link: gcc -I../../src/include -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wl,-z 
-Wl,relro -o .libs/br br.o  ../../src/lib/.libs/libatm.so
  gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2  
-I../../src/include -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -MT bw.o -MD 
-MP -MF .deps/bw.Tpo -c -o bw.o bw.c
  bw.c: In function 'main':
  bw.c:60:19: warning: ignoring return value of 'write', declared with 
attribute warn_unused_result [-Wunused-result]
while (blocks--) (void) write(s,buffer,BSIZE);
 ^~~~
  bw.c:62:6: warning: ignoring return value of 'write', declared with attribute 
warn_unused_result [-Wunused-result]
(void) write(s,buffer,size);
^~~
  mv -f .deps/bw.Tpo .deps/bw.Po
  /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -I../../src/include -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes  
-Wl,-z,relro -o bw bw.o ../../src/lib/libatm.la 
  libtool: link: gcc -I../../src/include -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wl,-z 
-Wl,relro -o .libs/bw bw.o  ../../src/lib/.libs/libatm.so
  gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2  
-I../../src/include -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116094316.Tj0RL2UOKo.db.linux-atm/linux-atm-2.5.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wall -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -MT isp.o 
-MD -MP -MF .deps/isp.Tpo -c -o isp.o isp.c
  isp.c: In function 'send_msg':
  isp.c:40:44: warning: format '%d' expects argument of type 'int', but 
argument 4 has type 'long unsigned int' [-Wformat=]
   else fprintf(stderr,"bad write: %d != %d\n",wrote,sizeof(*msg));
  ^
  isp.c: In function 'recv_msg':
  isp.c:52:43: warning: format '%d' expects argument of type 'int', but 
argument 4 has type 'long unsigned int' [-Wformat=]
   else fprintf(stderr,"bad read: %d != %d\n",got,sizeof(*msg));
 ^
  mv -f .deps/isp.Tpo .deps/isp.Po
  /bin/bash ../../ylwrap ispl_y.y y.tab.c 

Bug#844492: lua-sql: FTBFS: cc: error: .specs: No such file or directory

[Chris Lamb]

Source: lua-sql
Version: 2.3.0-4
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

lua-sql fails to build from source in unstable/amd64:

  […]

  Preparing to unpack .../02-pkg-config_0.29-4_amd64.deb ...
  Unpacking pkg-config (0.29-4) ...
  Selecting previously unselected package liblua5.3-0:amd64.
  Preparing to unpack .../03-liblua5.3-0_5.3.1-1.1+b1_amd64.deb ...
  Unpacking liblua5.3-0:amd64 (5.3.1-1.1+b1) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../04-libtinfo-dev_6.0+20160917-1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160917-1) ...
  Selecting previously unselected package libreadline-dev:amd64.
  Preparing to unpack .../05-libreadline-dev_7.0-1_amd64.deb ...
  Unpacking libreadline-dev:amd64 (7.0-1) ...
  Selecting previously unselected package liblua5.3-dev:amd64.
  Preparing to unpack .../06-liblua5.3-dev_5.3.1-1.1+b1_amd64.deb ...
  Unpacking liblua5.3-dev:amd64 (5.3.1-1.1+b1) ...
  Selecting previously unselected package lua5.3.
  Preparing to unpack .../07-lua5.3_5.3.1-1.1+b1_amd64.deb ...
  Unpacking lua5.3 (5.3.1-1.1+b1) ...
  Selecting previously unselected package liblua5.2-0:amd64.
  Preparing to unpack .../08-liblua5.2-0_5.2.4-1.1+b1_amd64.deb ...
  Unpacking liblua5.2-0:amd64 (5.2.4-1.1+b1) ...
  Selecting previously unselected package liblua5.2-dev:amd64.
  Preparing to unpack .../09-liblua5.2-dev_5.2.4-1.1+b1_amd64.deb ...
  Unpacking liblua5.2-dev:amd64 (5.2.4-1.1+b1) ...
  Selecting previously unselected package lua5.2.
  Preparing to unpack .../10-lua5.2_5.2.4-1.1+b1_amd64.deb ...
  Unpacking lua5.2 (5.2.4-1.1+b1) ...
  Selecting previously unselected package liblua5.1-0:amd64.
  Preparing to unpack .../11-liblua5.1-0_5.1.5-8.1+b2_amd64.deb ...
  Unpacking liblua5.1-0:amd64 (5.1.5-8.1+b2) ...
  Selecting previously unselected package liblua5.1-0-dev:amd64.
  Preparing to unpack .../12-liblua5.1-0-dev_5.1.5-8.1+b2_amd64.deb ...
  Unpacking liblua5.1-0-dev:amd64 (5.1.5-8.1+b2) ...
  Selecting previously unselected package lua5.1.
  Preparing to unpack .../13-lua5.1_5.1.5-8.1+b2_amd64.deb ...
  Unpacking lua5.1 (5.1.5-8.1+b2) ...
  Selecting previously unselected package libnumber-compare-perl.
  Preparing to unpack .../14-libnumber-compare-perl_0.03-1_all.deb ...
  Unpacking libnumber-compare-perl (0.03-1) ...
  Selecting previously unselected package libtext-glob-perl.
  Preparing to unpack .../15-libtext-glob-perl_0.10-1_all.deb ...
  Unpacking libtext-glob-perl (0.10-1) ...
  Selecting previously unselected package libfile-find-rule-perl.
  Preparing to unpack .../16-libfile-find-rule-perl_0.34-1_all.deb ...
  Unpacking libfile-find-rule-perl (0.34-1) ...
  Selecting previously unselected package dh-lua.
  Preparing to unpack .../17-dh-lua_23+nmu2_all.deb ...
  Unpacking dh-lua (23+nmu2) ...
  Selecting previously unselected package mysql-common.
  Preparing to unpack .../18-mysql-common_5.8+1.0.1_all.deb ...
  Unpacking mysql-common (5.8+1.0.1) ...
  Selecting previously unselected package libmysqlclient20:amd64.
  Preparing to unpack .../19-libmysqlclient20_5.7.16-1_amd64.deb ...
  Unpacking libmysqlclient20:amd64 (5.7.16-1) ...
  Selecting previously unselected package zlib1g-dev:amd64.
  Preparing to unpack .../20-zlib1g-dev_1%3a1.2.8.dfsg-2+b3_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b3) ...
  Selecting previously unselected package libmysqlclient-dev.
  Preparing to unpack .../21-libmysqlclient-dev_5.7.16-1_amd64.deb ...
  Unpacking libmysqlclient-dev (5.7.16-1) ...
  Selecting previously unselected package libsqlite3-dev:amd64.
  Preparing to unpack .../22-libsqlite3-dev_3.15.1-1_amd64.deb ...
  Unpacking libsqlite3-dev:amd64 (3.15.1-1) ...
  Selecting previously unselected package libpq5:amd64.
  Preparing to unpack .../23-libpq5_9.6.1-2_amd64.deb ...
  Unpacking libpq5:amd64 (9.6.1-2) ...
  Selecting previously unselected package libpq-dev.
  Preparing to unpack .../24-libpq-dev_9.6.1-2_amd64.deb ...
  Unpacking libpq-dev (9.6.1-2) ...
  Setting up libtool-bin (2.4.6-2) ...
  Setting up libsqlite3-dev:amd64 (3.15.1-1) ...
  Setting up mysql-common (5.8+1.0.1) ...
  update-alternatives: using /etc/mysql/my.cnf.fallback to provide 
/etc/mysql/my.cnf (my.cnf) in auto mode
  Setting up libtinfo-dev:amd64 (6.0+20160917-1) ...
  Setting up dctrl-tools (2.24-2) ...
  Setting up libtext-glob-perl (0.10-1) ...
  Setting up lua5.1 (5.1.5-8.1+b2) ...
  update-alternatives: using /usr/bin/lua5.1 to provide /usr/bin/lua 
(lua-interpreter) in auto mode
  update-alternatives: using /usr/bin/luac5.1 to provide /usr/bin/luac 
(lua-compiler) in auto mode
  Setting up pkg-config (0.29-4) ...
  Setting up libpq5:amd64 (9.6.1-2) ...
  Processing triggers for libc-bin (2.24-5) ...
  Setting up lua5.2 (5.2.4-1.1+b1) ...
  update-alternatives: using /usr/bin/lua5.2 to