Bug#840186: closed by Michael Banck (Bug#840186: fixed in nwchem 6.6+r27746-3)

[Adrian Bunk]

Control: clone -1 -2
Control: notfixed -2 6.6+r27746-3
Control: severity -2 important
Control: retitle -2 nwchem builds on amd64 with -mtune=native


On Fri, Nov 18, 2016 at 12:24:04PM +, Debian Bug Tracking System wrote:
>...
>* debian/patches/19_disable_march_native.patch: New patch, disables
>  -march=native on amd64, by Edoardo Apra (Closes: #840186).
>...
> Date: Sun, 09 Oct 2016 14:59:15 +0300
> From: Adrian Bunk 
> To: Debian Bug Tracking System 
> Subject: nwchem builds on amd64 with -march=native
> 
> Source: nwchem
> Version: 6.6+r27746-2
> Severity: grave
> 
> src/config/makefile{,-legacy}.h sets -march=native
> and -mtune=native in amd64 builds.
> 
> -march=native means the code will only run on machines with a CPU
> compatible with the one on the machine where the package
> was built.
> 
> Building on a different buildd machine can also change
> where the code can run - including breaking existing
> setups in stable updates.
> 
> -mtune=native is less fatal, but in addition to (rare) problems
> due to the fact that the program is compiled differently depending
> on the build machine it makes the build non-reproducible.
> 
> Please remove -march=native and -mtune=native

-march=native was removed, but -mtune=native is still present.

This is less bad, but still a bug:
The resulting code is now expected to run everywhere, but it will be 
different depending on what build machine was used.
This leaves an opportunity for strange bugs that disappear when 
recompiling (on a different machine).
And it makes the build non-reproducible.

Please also remove -mtune=native.

Thanks
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844764: borgbackup: Please update package description

[Matteo Cypriani]

Source: borgbackup
Version: 1.0.8-1
Severity: minor

Hi there,

The descriptions of both packages borgbackup and borgbackup-doc state:
“It was forked from the attic backup program which is also packaged in
Debian.”

attic was removed [1] from Debian in September, so I believe the
reference to the attic Debian package should be removed as well.

[1] https://packages.qa.debian.org/a/attic/news/20160915T130956Z.html

Cheers,
  Matteo

Bug#844339: [PATCH v3 2/4] libvirt-daemon-system.{config,templates,postinst,NEWS}: warn if allocated uid/gid is taken

[Mauricio Faria de Oliveira]

Guido,

On 11/18/2016 04:24 PM, Guido Günther wrote:

I'm failing to spot how you make sure you only run on new
installations. [snip]


Oops. You're right. Not sure where my head was at. It passed
tests due to debconf again; sorry.

I thought of not doing a whole-file guard, but an early exit,
to keep it short.  Is this snippet OK with you?

# Only perform this check/warning on new installations
# (precisely: when not creating neither user nor group).
if getent passwd libvirt-qemu >/dev/null \
&& getent group  libvirt-qemu >/dev/null; then
exit 0
fi


> +# Check if allocated UID/GID are assigned to a different user/group.
> +UID_TO_NAME="$(getent passwd $LIBVIRT_QEMU_UID | cut -d: -f1)"
> +GID_TO_NAME="$(getent group  $LIBVIRT_QEMU_GID | cut -d: -f1)"
> +
> +if ( [ -n "$UID_TO_NAME" ] && [ "$UID_TO_NAME" != 'libvirt-qemu' ] ) \
> +|| ( [ -n "$GID_TO_NAME" ] && [ "$GID_TO_NAME" != 'libvirt-qemu' ] )
> \

I think this can be shortened to:

if [ "$UID_TO_NAME" != 'libvirt-qemu' ] || [ "$GID_TO_NAME" != 'libvirt-qemu' 
]; then


Hm, but if the uid/gid is not taken, then getent output is null,
which is != 'libvirt-qemu', so the warning shows up incorrectly.

If you're OK w/ my suggestions, would you apply the guard snippet,
or would prefer a v4 of this particular patch submitted?

Thanks,

--
Mauricio Faria de Oliveira
IBM Linux Technology Center

Bug#829078: Any word?

[Logan Schmidt]

 

Is there any word on this? We are deploying Elasticsearch servers today
and are getting the same YAML problem when trying to start the service.
We are using Ubuntu 16.10 (64 bit). Could we try different distro level
like 16.04? This is a Debian specific issue not to sure what course of
action to take here. 

Any help is appreciated. Thanks, 

-- 

Logan Schmidt / Chief Technology Officer
lschm...@realpeoplesratings.com / 262-278-0243 

Real Peoples Ratings 
www.realpeoplesratings.com [1] 

  

Links:
--
[1] http://www.realpeoplesratings.com/

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

[Dominique Dumont]

On Friday, 18 November 2016 10:54:36 CET Russ Allbery wrote:
>> Considering [1], we may want to patch Debian's perl to produce utf8 man
> > pages even if upstream cannot, due to portability constraints.
> 
> That's not strictly true, which is the reason why I haven't already
> switched Linux systems over to generating UTF-8 by default.  This means
> that you cannot create man pages with pod2man on a Linux system and have
> them work on any other system, something that pod2man has, up until this
> point, always guaranteed.

Looks like I was not clear. I was thinking of patching perl build system to 
generate  perl* man page (perlrun perlunicook...) as utf8 man page. 

That should not impact the generation of other man pages (i.e. not in Debian 
perl package) using pod2man.

HTH
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#829078: Temporary Solution to end-users

[Logan Schmidt]

 

Our team discovered the issue is not present on the Debian used in
Ubuntu 16.04.1. 

30,000ft answer, use 16.04.1 until this Debian specific issue is
resolved. Refrain from Ubuntu 16.10 and apt-get'ing elasticsearch 

Hope this helps anyone else,-- 
-- 

Logan Schmidt / Chief Technology Officer
lschm...@realpeoplesratings.com / 262-278-0243 

Real Peoples Ratings 
www.realpeoplesratings.com [1] 

  

Links:
--
[1] http://www.realpeoplesratings.com/

Bug#839539: svn2git: git-svn should be a dependency for svn2git

[Sascha Girrulat]

updated and fixed in vcs.

Upload is comming soon.

Regards
Sascha


[1] https://anonscm.debian.org/git/users/sagiru-guest/svn2git.git
[2] https://mentors.debian.net/package/svn2git



signature.asc
Description: OpenPGP digital signature

Bug#844765: RFS: gitless/0.8.4-1 -- new package

[Peter Pentchev]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for the initial upload of my package
"gitless" - a version control system on top of Git.

* Package name: gitless
  Version : 0.8.4-1
  Upstream Author : Santiago Perez de Rosso 
* URL : http://gitless.com/
* License : GPL-2+
  Section : devel

It builds a single binary package that has been built with sbuild and
tested with Lintian and cme:

  gitless- version control system on top of Git

Unfortunately there have been some issues with uploading the Gitless
package to mentors.d.n (I'm in contact with the administrators), but you
can fetch it from my website:

  dget -x 
https://devel.ringlet.net/devel/gitless/debian/0.8.4-1/gitless_0.8.4-1.dsc

...or, alternatively, from a GitHub repository:

  git clone https://github.com/ppentchev/gitless.git -b debian
  cd gitless
  git describe # should output mentors/0.8.4-1-2
  git tag -v mentors/0.8.4-1-2
  pristine-tar checkout ../gitless_0.8.4.orig.tar.gz

More information about Gitless can be obtained from http://gitless.com/

Thanks in advance for your time, and keep up the great work!

G'luck,
Peter

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

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

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

[Russ Allbery]

Dominique Dumont  writes:

> Looks like I was not clear. I was thinking of patching perl build system
> to generate perl* man page (perlrun perlunicook...) as utf8 man page.

> That should not impact the generation of other man pages (i.e. not in
> Debian perl package) using pod2man.

Oh, yes.  I thought that had already been done at some point by forcing
the build system to pass -u, but possibly not.  I'm not sure how hard that
is to do.

-- 
Russ Allbery (r...@debian.org)   

Bug#844767: RM: liggghts [mips mipsel] -- ROM; FTBFS on mips and mipsel

[Anton Gladky]

Package: ftp.debian.org
Severity: normal

Dear FTP team,

the package liggghts fails to build on mips and mipsel
due to unsifficient RAM. The package will unlikely be
useful on those archs, so please remove it for now.

Thank you

Anton

Bug#844768: ruby-berkshelf-api-client FTBFS in stretch due to missing berkshelf-api

[Adrian Bunk]

Source: ruby-berkshelf-api-client
Version: 2.0.2-1
Severity: serious
Tags: stretch
Control: block -1 by 841704

ruby-berkshelf-api-client build-depends on berkshelf-api,
which is not in testing due to #841704

Bug#844766: rtslib FTBFS in stretch due to missing simpleparse

[Adrian Bunk]

Source: rtslib
Version: 1:3.0~pre4.1~g1b33ceb-3
Severity: serious
Tags: stretch
Control: block -1 by 824738

rtslib build-depends on python-simpleparse, which is not in stretch
due to #824738

Bug#844718: kmail: Kmail cannot be synchronized between 2 computers anymore

[Sandro Knauß]

Hey,

> I am using kmail on different computers (in particular: 1 desktop and 1
> laptop) and I need to keep all mail synchronized between these computers.
> That is all :-)

Well it still possible, but yes the data are more cluttered. So if you want to 
sync all data you need to stop akonadi before, so the database is shutdown.
And the default paths have changed, so you will need to update the paths you 
want to synchronize.

akonadictl stop
* ~/.local/share/akonadi/
* ~/.config/akonadi*
  -> all paths, that you defined inside the resoureses 
 ~/.config/akonadi*resource_*rc
* passwords from kwallet5

akonadictl start

for the other machine you need also to stop akonadi first and restart it 
afterwards.

Just for your information, if you only copy the .config files akonadi will 
redownload everything from IMAP.

If you just update the local maildir folder, akonadi should just detect the 
new mails and show this within kmail. akonadi uses inotify, so make sure that 
inotify has not run into a limit of watched directories. The default in debian 
is quite low.

This is for akonadi data, than you also have configuration for the pim apps, 
these are still configfiles, you can simply copy around, but these might also 
moved to .local or .config.

@baloo: baloo is simply the file indexer for KDE and has nothing to do with 
kdepim. (at least for unstable). The pim indexer was split out and renamed to 
akonadisearch. but in both cases the indexer is shut down with akonadi, cause 
it it a resource in akonadi, too.

> o the key problem is the non-sync of the "local" folders since I transfer
> lots of mails from IMAP to "local" folders, and these must stay in sync.
> (hey, syncing IMAP is not a problem ;-)

Try to just sync your local maildir - search for the config file to get the 
correct location of you maildir folder and sync this to the other computer.

> o I have tried 'pimsettingexporter' but this was a major mess - (a) it takes
> a very long time to create the archive, and (2) on unpacking, both the mail
> folders and account settings/names are lost/garbled. This is not a valid
> option :-/

I never tried the 'pimsettingexporter'  :)

Best regards,

sandro

signature.asc
Description: This is a digitally signed message part.

Bug#809388: evince: evince aborts after a few seconds without an error message

[Jason Crain]

Control: tags -1 - moreinfo unreproducible

On Wed, Nov 16, 2016 at 05:20:52PM +0100, Janusz S. Bień wrote:
> Another crash,  still a not typical one:

I might have found what's causing it.  Try setting environment variable
G_SLICE=always-malloc before evince runs and see if that stops the
crashes.

Bug#844769: RFS: node-resumer/0.0.0-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-resumer"

 * Package name: node-resumer
   Version : 0.0.0-1
   Upstream Author : James Halliday  (http://substack.net)
 * URL :https://github.com/substack/resumer
 * License : Expat
   Section : web

It builds this binary package:

node-resumer  - a through stream that starts paused and resumes on the
 next tick

Unfortunately, it is not possible for me to upload to mentors at the moment.

But the packaging can be found here:

https://anonscm.debian.org/cgit/pkg-javascript/node-resumer.git/

Changes since the last upload:
|

  * Initial release (Closes: #814286)

|Regards,
Ross Gammon

Bug#832704: RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source Evernote client

[Sean Whitton]

Hello Gianfranco,

On Fri, Nov 18, 2016 at 06:54:01PM +, Gianfranco Costamagna wrote:
> Hi, I put the package in deferred/5, because I'm not sure about the whole 
> license.
> Isn't it something like GPL-2+ instead of GPL-2?
> I agree single files are ok, but the "*" wildcard seems a GPL-2+ to me, even 
> if
> I didn't find a copying file.

See license.html.  The project is GPL-2, but some files have GPL-2+ in
their headers.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#844503: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

[Sebastian Andrzej Siewior]

On 2016-11-18 15:22:07 [+0100], Benjamin Drung wrote:
> Instead of forcing salt to use OpenSSL 1.0, let's try to make it work
> with OpenSSL 1.1. Adjusting the initialization to work with OpenSSL 1.1
> was quite easy. I forwarded the patch upstream to
> https://github.com/saltstack/salt/pull/37772 to get it reviewed and
> accepted.

so it is just two calls? I was a little afraid once I all those rsa ops
and so on. But if nothing else breaks - good.
A little note: OPENSSL_INIT_ADD_ALL_CIPHERS & friends could change on
the next so.bump. Probably they won't but they could.
A "Depend: libssl-1.0.2 || libssl-1.1.0" would avoid further breakage if
ABI changes.

Sebastian

Bug#722717: RM: adzapper -- RoQA; not in stable, outdated

[Adrian Bunk]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: adzapper -- RoQA; not in stable, outdated

adzapper is not in stable, and due to the build-dependency on 
libswf-perl (see the RC bugs in src:ming) it is anyway not
likely that it could get released in stretch.

Advertisement zapping is a field that changes very quickly.
The latest adzapper upstream release is from 2011, and the version
in Debian is from 2009 (the package is orphaned since 2013).

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#829078: Any word?

[Emmanuel Bourg]

Le 18/11/2016 à 20:44, Logan Schmidt a écrit :

> Is there any word on this? We are deploying Elasticsearch servers today
> and are getting the same YAML problem when trying to start the service.
> We are using Ubuntu 16.10 (64 bit). Could we try different distro level
> like 16.04? This is a Debian specific issue not to sure what course of
> action to take here.

Hi Logan,

If you need Elasticsearch on Debian/Ubuntu your best bet for now is to
install the upstream package available on the download page [1]. The
elasticsearch package maintained by Debian isn't ready for prime time
yet and will probably not be part of the Stretch release.

Emmanuel Bourg

[1] https://www.elastic.co/downloads/elasticsearch

Bug#844770: xzcmp: SIGPIPE is raised because CMP does exit while the XZ commands are still writing to the pipe

[ViaThinkSoft]

Package: xz-utils
Version: 5.1.1alpha+20120614-2+b3
Severity: important
Tags: newcomer



I noticed that xzcmp returns status code 2 (error) for a few file pairs, 
especially if they differ in size.

After some investigation, I found out that exit status 141 (SIGPIPE) is raised 
by the xz-commands, because cmp seems to have already quit after it found the 
first difference between the two streams. After that, the two xz commands write 
into the broken pipe.

The exit status of the two xz commands is written into $xz_status . At the end 
of the script, if $xz_status is not 0, then xzcmp's exit status will become 2 
(although the actual CMP did work fine in this specific case)


Workaround:

If the following line is added, the signal SIGPIPE (exit status 141) will not 
be raised by the xz commands, and thus, the xzdiff process will return the 
correct exit code:

trap '' PIPE



-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages xz-utils depends on:
ii  libc6 2.19-18+deb8u6
ii  liblzma5  5.1.1alpha+20120614-2+b3

xz-utils recommends no packages.

xz-utils suggests no packages.

-- no debconf information

Bug#844771: CVE-2016-9427: Integer overflow in GC_MALLOC_ATOMIC

[Markus Koschany]

Package: libgc
Severity: important
Tags: security

Hi,

the following vulnerability was published for libgc.

CVE-2016-9427[0]:
 Integer overflow in GC_MALLOC_ATOMIC

Upstream bug report:
https://github.com/ivmai/bdwgc/issues/135

Patches:
https://github.com/ivmai/bdwgc/commit/4e1a6f9d8f2a49403bbd00b8c8e5324048fb84d4
https://github.com/ivmai/bdwgc/commit/7292c02fac2066d39dd1bcc37d1a7054fd1e32ee
https://github.com/ivmai/bdwgc/commit/552ad0834672fed86ada6430150ef9ebdd3f54d7

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9427
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9427
Please adjust the affected versions in the BTS as needed.




signature.asc
Description: OpenPGP digital signature

Bug#841560: [Debian-med-packaging] Bug#841560: Could anybody please check the issue in python-skbio

[Kevin Murray]

Hi all,

AFAICT I think I should have fixed the issues in skbio. I've filed an ROM bug,
and updated to latest upstream. Could I please get an upload and see if the
test failure goes away?

Cheers,
Kevin

---
Kevin Murray

Bug#844679: [Python-modules-team] Bug#844679: /usr/bin/pip: Should use --disable-pip-version-check by default

[Barry Warsaw]

On Nov 17, 2016, at 11:17 PM, Nelson A. de Oliveira wrote:

>Since we are installing pip from a Debian package, shouldn't we have it
>using "--disable-pip-version-check" by default, to avoid this?

Yes, I think we should.

Bug#832704: RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source Evernote client

[Gianfranco Costamagna]

Hi


>See license.html.  The project is GPL-2, but some files have GPL-2+ in
>their headers.


rescheduled, thanks :)

and sorry for the useless question
G.

Bug#844772: ITP: r-bioc-mergeomics -- Integrative network analysis of omics data

[Dylan]

Package: wnpp
Severity: wishlist
Owner: Dylan Aïssi 

Package name: r-bioc-mergeomics
URL: https://bioconductor.org/packages/Mergeomics/
License: GPL-2+
Description: Integrative network analysis of omics data
 The Mergeomics pipeline serves as a flexible framework for integrating
 multidimensional omics-disease associations, functional genomics,
 canonical pathways and gene-gene interaction networks to generate
 mechanistic hypotheses. It includes two main parts:
 1) Marker set enrichment analysis (MSEA);
 2) Weighted Key Driver Analysis (wKDA).


This package will be maintained by the Debian Med Packaging Team at:
https://anonscm.debian.org/git/debian-med/r-bioc-mergeomics.git/

Bug#844773: RFS: ustr/1.0.4-6

[Václav Ovsík]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ustr"

* Package name: ustr
  Version : 1.0.4-6
  Upstream Author : James Antill 
* URL : http://www.and.org/ustr/
* License : LGPL, BSD, MIT
  Section : libs

It builds those binary packages:

libustr-1.0-1 - Micro string library: shared library
libustr-1.0-1-dbg - Micro string library: debugging symbols
libustr-dev - Micro string library: development stuff
libustr-doc - Micro string library: documentation

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/ustr

Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/u/ustr/ustr_1.0.4-6.dsc

Changes since the last upload:

   * Patch fixes/autoconf:
 - Fixed race condition on creation shared library symbolic links when make
   runs parallel. Thanks to Yann E. MORIN .
 - Fixed FTBFS (LDFLAGS with -pie): move LDFLAGS before -shared. Thanks to
   Helmut Grohne .
   Closes: #843459
   * Patch fixes/man-spelling: added corrections.
   * Added fixes/attr-nonnull: to disable nonnull attribute.
   * Added fixes/suppress-warn: to suppress warning about indentation.
   * Added hardening=+all in the debian/rules.
   * Changed Vcs-Git to URL with https.
   * Changed Standards-Version to 3.9.8.
   * Added dependency on quilt and include /usr/share/quilt/quilt.make
 in the debian/rules.
   * For libustr-doc added Multi-Arch: foreign.

Regards
-- 
Václav Ovsík

Bug#844774: libvshadow FTBFS: test failure on all architectures

[Adrian Bunk]

Source: libvshadow
Version: 2016-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libvshadow&suite=sid


FAIL: test_python_functions.sh
==

Testing Python-bindings functions: get_version  (FAIL)
FAIL test_python_functions.sh (exit status: 1)


Testsuite summary for libvshadow 2016

# TOTAL: 4
# PASS:  1
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to joachim.m...@gmail.com

Makefile:1252: recipe for target 'test-suite.log' failed

Bug#608843: Shipment delivery problem #00144524

[FedEx International Ground]

Dear Customer,

This is to confirm that one or more of your parcels has been shipped.
Delivery Label is attached to this email.

Yours sincerely,
Frank Wood,
Sr. Support Agent.



FedEx_00144524.doc
Description: MS-Word document

Bug#844254: NMU to DELAYED/5

[Hilko Bengen]

Hi,

I have just made a non-maintainer upload (libesmtp/1.0.6-4.1) to
DELAYED/5-day. If necessary, feel free to reschedule or cancel my
upload.

The simple change I made can be found in my Github fork at
. I have verified that the libesmtp6
package (built using sbuild) indeed depends on libssl1.1.

Cheers,
-Hilko

Bug#844703: [l10n] Updated Czech translation of apt-listbugs

[Francesco Poli]

On Fri, 18 Nov 2016 10:08:02 +0100 Miroslav Kure wrote:

[...]
> Hi,
> 
> in attachement there is updated Czech (cs.po) translation of 
> apt-listbugs. Please include it with the package.
> 
> Thank you

Hello Miroslav!
Thanks for the update.

I will soon push the translation to the public git repository; it will
be included in the next upload.

Your contribution is really appreciated!
Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp7kvotRVK3Z.pgp
Description: PGP signature

Bug#842675: lightdm FTBFS on !x86: error: symbols mismatch

[Adrian Bunk]

Control: severity -1 serious
Control: retitle -1 lightdm FTBFS on !x86: error: symbols mismatch

https://buildd.debian.org/status/package.php?p=lightdm&suite=sid

The only successful builds of 1.18.2-3 were on x86.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844775: udev: initramfs init-bottom/udev script fails to mount /dev when using virtual filesystems

[Luca Boccassi]

Package: udev
Version: 232-3
Severity: normal

Dear Maintainer,

Due to a recent change in busybox and initramfs-tools, the mount utility
in the initramfs now comes from util-linux rather than busybox.

scripts/init-bottom/udev calls "mount -o move", which was supported by
busybox's mount but not by util-linux's mount.

See the following for the full discussion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823856

This causes an error and a failure to boot when using virtual file
systems.

Both utilities support "mount --move", so attached is a patch that
implements this small change. I've successfully used this change to get
our squashfs based image working again.

Thank you!

Kind regards,
Luca Boccassi

From 34addb1aeae38026b1f8a451a99d1bde4d922da7 Mon Sep 17 00:00:00 2001
From: Luca Boccassi 
Date: Fri, 18 Nov 2016 20:09:58 +
Subject: [PATCH] Use mount --move in initramfs-tools udev script

Due to recent changes in busybox and initramfs-tools the mount
utility is no longer the one from busybox but from util-linux.
The latter does not support mount -o move.
The former supports both -o move and --move, so use it instead to be
compatible with both.
See this discussion for more details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823856
---
 debian/extra/initramfs-tools/scripts/init-bottom/udev | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/extra/initramfs-tools/scripts/init-bottom/udev 
b/debian/extra/initramfs-tools/scripts/init-bottom/udev
index 81081e3..e997380 100755
--- a/debian/extra/initramfs-tools/scripts/init-bottom/udev
+++ b/debian/extra/initramfs-tools/scripts/init-bottom/udev
@@ -15,7 +15,7 @@ esac
 udevadm control --exit
 
 # move the /dev tmpfs to the rootfs
-mount -n -o move /dev ${rootmnt}/dev
+mount -n --move /dev ${rootmnt}/dev
 
 # create a temporary symlink to the final /dev for other initramfs scripts
 if command -v nuke >/dev/null; then
-- 
2.1.4



signature.asc
Description: This is a digitally signed message part

Bug#844776: cbmc FTBFS on s390x and mips*: Running Pointer_array5/test.desc FAILED

[Adrian Bunk]

Source: cbmc
Version: 5.5-1
Severity: serious

https://buildd.debian.org/status/package.php?p=cbmc&suite=sid

...
  Running Pointer_array5/test.desc  [FAILED]
...
Tests failed
  1 of 383 tests failed, 20 tests skipped
Failed test: Pointer_array5
CBMC version 5.5 64-bit s390x linux
Parsing main.c
file  line 0: :0:0: warning: "__STDC_VERSION__" 
redefined
: note: this is the location of the previous definition
Converting
Type-checking main
Generating GOTO Program
Adding CPROVER library (s390x)
file  line 0: :0:0: warning: "__STDC_VERSION__" 
redefined
: note: this is the location of the previous definition
Removal of function pointers and virtual functions
Partial Inlining
Generic Property Instrumentation
Starting Bounded Model Checking
size of program expression: 95 steps
simple slicing removed 24 assignments
Generated 1 VCC(s), 1 remaining after simplification
Passing problem to propositional reduction
converting SSA
Running propositional reduction
Post-processing
Solving with MiniSAT 2.2.1 with simplifier
12568 variables, 25409 clauses
SAT checker: instance is SATISFIABLE
Runtime decision procedure: 0.114s

** Results:
[main.assertion.1] assertion address==&a0: FAILURE

** 1 of 1 failed (1 iteration)
VERIFICATION FAILED
EXIT=10
SIGNAL=0


debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:15: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#829078: Any word?

[Hilko Bengen]

* Emmanuel Bourg:

> Hi Logan,
>
> If you need Elasticsearch on Debian/Ubuntu your best bet for now is to
> install the upstream package available on the download page [1]. The
> elasticsearch package maintained by Debian isn't ready for prime time
> yet and will probably not be part of the Stretch release.

As the person who did the initial packaging work, I second this.

While it might be nice to get the package in order, I do not feel that
it's worth it. At this point, Elasticsearch is a crippled open-core
product that can only be properly used if one pays to use non-free
plug-ins for basic features that ought to be part of the core in the
first place, i.e. authentication or the option of encrypting inter-node
communication.

It is unclear to me whether or not upstream considers the 1.7 release
still supported. From my previous interactions with them regarding
security fixes I got the sense that this is not the case. They are not
even interested in providing detailed information about CVE-worthy
security issues that may help wih backporing.

Cheers,
-Hilko

Bug#825086: Package links against libmysqlclient_r

[Michael Prokop]

* Robie Basak [Mon May 23, 2016 at 02:16:52PM +0100]:

> Please stop linking against libmysqlclient_r and link directly against
> libmysqlclient instead.

> Your package currently links against libmysqlclient_r. libmysqlclient_r
> was the thread-safe version of libmysqlclient in previous MySQL
> releases. However, libmysqlclient has been itself been made thread-safe
> since before the current libmysqlclient18. Thus libmysqlclient_r is
> currently deprecated and provided as a compatibility symlink only, and
> will disappear in MySQL 5.7. This change can be made now, in advance of
> a possible future transition to libmysqlclient20, which does not provide
> the _r variant.

> In Ubuntu, we have done this with the attached quilt patch, which I
> believe is also applicable to Debian.

Any news on this one? Is there anything prevent the package
maintainer to upload a new package version with the patch applied?
libmysql++-dev isn't in testing because of this and the freeze for
stretch is coming closer.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#844777: why FTBFS on mips*, ppc64el, s390x: cannot stat './META.frama-c-jessie'

[Adrian Bunk]

Source: why
Version: 2.36-2
Severity: serious

https://buildd.debian.org/status/package.php?p=why&suite=sid

...
mkdir -p /«PKGBUILDDIR»/debian/why/usr/share/why/coq
cp -f lib/coq/Jessie_memory_model.vo /«PKGBUILDDIR»/debian/why/usr/share/why/coq
/usr/bin/make -C frama-c-plugin install
make[3]: Entering directory '/«PKGBUILDDIR»/frama-c-plugin'
mkdir -p /«PKGBUILDDIR»/debian/why/usr/lib/frama-c/plugins
cp ./META.frama-c-jessie ./Jessie.cmi ./Jessie.cmo ./Jessie.cma  
/«PKGBUILDDIR»/debian/why/usr/lib/frama-c/plugins
cp: cannot stat './META.frama-c-jessie': No such file or directory
/usr/share/frama-c/Makefile.dynamic:263: recipe for target 'install' failed
make[3]: *** [install] Error 1

Bug#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

[Adrian Bunk]

Source: clsync
Version: 0.4.2-1
Severity: serious

https://buildd.debian.org/status/package.php?p=clsync&suite=sid

...
In file included from privileged.c:64:0:
privileged.c:88:34: error: '__NR_select' undeclared here (not in a function)
  BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, __NR_##syscall, 0, 1), \
...

Bug#844779: osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope

[Adrian Bunk]

Source: osmose-emulator
Version: 1.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=osmose-emulator&suite=sid

...
g++ -c -pipe -std=c++11 -Wall -Wextra -Wno-unused -Wcast-qual -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT 
-fPIC -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB 
-I. -I. -Icpu -Iosmose -isystem /usr/include/arm-linux-gnueabi/qt5 -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtOpenGL -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtWidgets -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtGui -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtCore -I. -I. 
-I/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++ -o QGLImage.o QGLImage.cpp
QGLImage.cpp: In member function 'virtual void QGLImage::paintGL()':
QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope
 glLoadIdentity();
^
QGLImage.cpp:111:103: error: 'GL_UNSIGNED_INT_8_8_8_8_REV' was not declared in 
this scope
 glTexImage2D (GL_TEXTURE_2D, 0, GL_RGBA, adjustedTextureWidth, 
adjustedTextureHeight, 0, GL_RGBA, GL_UNSIGNED_INT_8_8_8_8_REV, textureBuffer);

   ^~~
QGLImage.cpp:112:13: error: 'GL_QUADS' was not declared in this scope
 glBegin(GL_QUADS);
 ^~~~
QGLImage.cpp:112:21: error: 'glBegin' was not declared in this scope
 glBegin(GL_QUADS);
 ^
QGLImage.cpp:114:21: error: 'glTexCoord2f' was not declared in this scope
 glTexCoord2f(0,0);
 ^
...

Bug#258096: Are you getting my email?

[Simon]

*Good day and how are you?  This is like the 3rd mail I have sent to this
email without any reply. Are you no longer using this email...? Please let
me know if this email is still valid or not. or better give me your working
email. *

*I have sent 3 mails to your email and they all failed. Dont know  if  this
will also be received or not? Please confirm.*

*I will resend the mail if you did not receive the first one I sent. *

*Thanks*

Bug#826297: patch

[積丹尼 Dan Jacobson]

--- README.Debian   2016-11-19 07:17:12.657166692 +0800
+++ README.Debian.NEW   2016-11-19 07:25:48.293169579 +0800
@@ -45,6 +45,16 @@
 and then get more detailed information with "systemctl status -l foo.service"
 to get a service "foo"'s status and recent logging.
 
+To make a /shutdown-log.txt file on Debian:
+1. boot with the debug options:
+systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0
+2. save the following script as /lib/systemd/system-shutdown/debug.sh and make 
it executable:
+#!/bin/sh
+mount -o remount,rw /
+dmesg > /shutdown-log.txt
+mount -o remount,ro /
+3. reboot
+
 Enable and use networkd
 ===
 networkd is a small and lean service to configure network interfaces, designed

Bug#844780: gcc-6-arm-linux-gnueabihf: cross-compiled code fails to link on target with native gcc-6

[Matthijs van Duin]

Package: gcc-6-arm-linux-gnueabihf
Version: 6.1.1-9cross1
Severity: important

Dear Maintainer,

If I cross-compile any code (even a basic hello-world) and then attempt
to link the resulting objects on the target system (stretch, armhf)
using the native gcc-6 toolchain (which is 6.2.0 in testing and has
already been for a while) I get the following failure:

/usr/bin/ld: hello.o: relocation R_ARM_THM_MOVW_ABS_NC against `a local symbol' 
can not be used when making a shared object; recompile with -fPIC
hello.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status

Recompiling with -fPIC as suggested does in fact fix the problem, but
this should not be necessary and never has been.  (Compiling without it
but linking with the cross-toolchain also results in a working binary.)

Note that cross-compiling + native linking is for example needed to be
able to use distcc to speed up compilation on small ARM systems by
delegating most of the work to a build server, which is how I ran into
this issue.  This setup is currently completely broken due to this bug.


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

Kernel: Linux 4.8.0-2.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_NL.UTF-8, LC_CTYPE=en_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-6-arm-linux-gnueabihf depends on:
ii  binutils-arm-linux-gnueabihf2.27.51.20161108-1
ii  cpp-6-arm-linux-gnueabihf   6.1.1-9cross1
ii  gcc-6-arm-linux-gnueabihf-base  6.1.1-9cross1
ii  libc6   2.24-5
ii  libcc1-06.2.0-13
ii  libgcc-6-dev-armhf-cross6.1.1-9cross1
ii  libgcc1 1:6.2.0-13
ii  libgmp102:6.1.1+dfsg-1
ii  libisl150.17.1-1
ii  libmpc3 1.0.3-1
ii  libmpfr43.1.5-1
ii  libstdc++6  6.2.0-13
ii  zlib1g  1:1.2.8.dfsg-2+b3

Versions of packages gcc-6-arm-linux-gnueabihf recommends:
ii  libc6-dev-armhf-cross  2.24-1cross1

Versions of packages gcc-6-arm-linux-gnueabihf suggests:
ii  gcc-6-doc 6.1.0-1
pn  gcc-6-locales 
pn  libasan3-dbg-armhf-cross  
pn  libatomic1-dbg-armhf-cross
pn  libcilkrts5-dbg-armhf-cross   
pn  libgcc1-dbg-armhf-cross   
pn  libgomp1-dbg-armhf-cross  
pn  libitm1-dbg-armhf-cross   
pn  liblsan0-dbg-armhf-cross  
pn  libmpx2-dbg-armhf-cross   
pn  libquadmath0-dbg-armhf-cross  
pn  libtsan0-dbg-armhf-cross  
pn  libubsan0-dbg-armhf-cross 

-- no debconf information

Bug#844254: NMU to DELAYED/5

[Jeremy T. Bouse]

I've taken a look at the diff of your fork. I'm about to be out of town
and away from my development box for the next two weeks in about 8 hours
so I can't do anything at this time... I'll let the NMU go through and
then pull your commit hash 96eb8e628c8e87200a208281e569523c8fb77bf8 in
and prepare a 1.0.6-5 build to accept it.


On 11/18/2016 5:52 PM, Hilko Bengen wrote:
> Hi,
>
> I have just made a non-maintainer upload (libesmtp/1.0.6-4.1) to
> DELAYED/5-day. If necessary, feel free to reschedule or cancel my
> upload.
>
> The simple change I made can be found in my Github fork at
> . I have verified that the libesmtp6
> package (built using sbuild) indeed depends on libssl1.1.
>
> Cheers,
> -Hilko

Bug#844781: libowfat FTBFS on s390x: undefined reference to `__libc_waitpid'

[Adrian Bunk]

Source: libowfat
Version: 0.30-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libowfat&arch=s390x&ver=0.30-2&stamp=1460534507

...

gcc -nostdlib -static -L/usr/lib/diet/lib-s390x /usr/lib/diet/lib-s390x/start.o 
-g -o t t.o libowfat.a -lpthread -isystem /usr/lib/diet/include -D__dietlibc__ 
-Os -fomit-frame-pointer /usr/lib/diet/lib-s390x/libc.a -lgcc 
-fno-stack-protector 
t.o: In function `ret0':
/«PKGBUILDDIR»/t.c:54: warning: warning: your code still has assertions enabled!
/usr/lib/diet/lib-s390x/libpthread.a(pthread_internal.o): In function 
`pthread_exit':
pthread_internal.c:(.text+0x3a2): undefined reference to `__libc_waitpid'
/usr/lib/diet/lib-s390x/libpthread.a(pthread_internal.o): In function 
`__thread_restart':
pthread_internal.c:(.text+0x9ca): undefined reference to `__libc_waitpid'
collect2: error: ld returned 1 exit status
/«PKGBUILDDIR»/GNUmakefile:171: recipe for target 't' failed
make[2]: *** [t] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»/build-diet'
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:9: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#844780: gcc-6-arm-linux-gnueabihf: cross-compiled code fails to link on target with native gcc-6

[Matthijs van Duin]

I've found the problem, it has nothing to do with cross-gcc. The issue lies
with the native gcc 6.2 which has been configured with
--enable-default-pie, which (at least on arm) breaks its ability to link
any code produced by earlier compilers.

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Vincent Lefevre]

Control: tags -1 patch

On 2016-11-17 15:37:13 +0200, Adrian Bunk wrote:
> On Thu, Nov 17, 2016 at 09:41:07AM +0100, Vincent Lefevre wrote:
> > A warning can be very annoying (e.g. because it mixes with other output
> > to the terminal) and possibly break scripts that don't expect output to
> > stderr. If this is not expected to work, then an error like upstreams's
> > behavior is the right thing to do (there is a real issue, and the user
> > must make sure that it gets fixed). Otherwise a warning isn't needed,
> > except in some debug mode for developers or andvanced users (but such
> > a mode would not be the default).
> 
> Yes, this is what should be done.

Removing the

  wxLogWarning(msg.c_str());

line from the warn-for-compiler-abi-mismatch.patch patch (and
updating the comment) is sufficient. This gives the attached
patch.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- wxwidgets3.0-3.0.2.orig/src/common/appbase.cpp
+++ wxwidgets3.0-3.0.2/src/common/appbase.cpp
@@ -762,6 +762,22 @@ bool wxAppConsoleBase::CheckBuildOptions
 msg.Printf(wxT("Mismatch between the program and library build 
versions detected.\nThe library used %s,\nand %s used %s."),
lib.c_str(), progName.c_str(), prog.c_str());
 
+
+   int l_off = lib.Find("compiler with C++ ABI ");
+   int p_off = prog.Find("compiler with C++ ABI ");
+   if (l_off != wxNOT_FOUND && p_off != wxNOT_FOUND) {
+   int space;
+   space = lib.Find(' ', l_off);
+   lib.erase(l_off, space - l_off);
+   space = prog.Find(' ', l_off);
+   prog.erase(p_off, space - p_off);
+   if (lib == prog) {
+   // Only difference is the ABI version, which apparently only
+   // affect obscure cases.
+   return false;
+   }
+   }
+
 wxLogFatalError(msg.c_str());
 
 // normally wxLogFatalError doesn't return

Bug#843454: ITP: docker-credential-helpers -- native store to keep Docker credentials, safe

[Felipe Sateler]

On 17 November 2016 at 01:41, Jason Pleau  wrote:
>
> Hi Felipe,
>
> 2016-11-16 17:40 GMT-05:00 Felipe Sateler :
> > Hi Jason
> >
> > On Sun, 6 Nov 2016 13:16:58 -0500 Jason Pleau  wrote:
> >> Package: wnpp
> >> Severity: wishlist
> >> Owner: Jason Pleau 
> >>
> >> * Package name: docker-credential-helpers
> >>   Version : 0.3.0
> >>   Upstream Author : David Calavera 
> >> * URL : https://github.com/docker/docker-credential-helpers/
> >> * License : MIT
> >>   Programming Lang: Go / C
> >>   Description : native store to keep Docker credentials safe
> >>
> >> docker-credential-helpers provides a Linux executable to store Docker
> >> credentials. (It also has one for OSX and Windows, but those won't be
> >> built nor used in Debian).
> >>
> >> It is a dependency of an upcoming python package
> >> "dockerpy-creds", which is needed to update python-docker to its latest
> >> upstream version.
> >
> >
> > Have you done some work yet on this? If so, could you push it to
> > collab-maint so I can take a look?
>
> Not yet, I scheduled some time saturday to work on it and hopefully
> finalize it, I will keep you updated :)

I had some time today so I took the liberty to start the packaging. I
have added it to collab-maint/docker-credential-helpers.git.

-- 

Saludos,
Felipe Sateler

Bug#844782: Please revert problematic sparc64 GOT patch

[James Clarke]

Source: binutils
Version: 2.27.51.20161118-1
Severity: important
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc: debian-sp...@lists.debian.org

Hi Matthias,
While global symbol references are now fine, we've noticed that TLS is
broken in a similar way, except in this case the linker can't do much to
fix it up unless it wants to patch the opcodes themselves. This has the
very bad side effect of causing apt-get to segfault in libstdc++. Until
this gets properly dealt with upstream, could you please revert the
relevant patch[1]?

James

[1] b19753ce31da347605dfa903c6fd2158e2444f0d

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

[John Paul Adrian Glaubitz]

Hi!

Would it be possible to change the build dependency from libssl-dev to
libssl1.0-dev for the time being to temporarily resolve this issue?

It's rather ugly to have a library as central as kde4libs FTBFS because
it blocks archive rebuilds or the bootstrapping of new architectures.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#844782: Please revert problematic sparc64 GOT patch

[John Paul Adrian Glaubitz]

On 11/19/2016 01:37 AM, James Clarke wrote:
> [1] b19753ce31da347605dfa903c6fd2158e2444f0d

Attaching the reversed patch which applies cleanly against git master
for binutils-gdb when removing the part that patches the upstream
changelog.

Fixing this is important, it causes quite a number of segfaults. I suspect
this is also the reason why cmake fails to build from source.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff --git b/bfd/elfxx-sparc.c a/bfd/elfxx-sparc.c
index 30daedf..63558c7 100644
--- b/bfd/elfxx-sparc.c
+++ a/bfd/elfxx-sparc.c
@@ -2661,19 +2661,19 @@ _bfd_sparc_elf_size_dynamic_sections (bfd *output_bfd,
   /* Allocate .plt and .got entries, and space for local symbols.  */
   htab_traverse (htab->loc_hash_table, allocate_local_dynrelocs, info);
 
-  if (!htab->is_vxworks
+  if (! ABI_64_P (output_bfd)
+  && !htab->is_vxworks
   && elf_hash_table (info)->dynamic_sections_created)
 {
-  if (! ABI_64_P (output_bfd))
-{
-  /* Make space for the trailing nop in .plt.  */
-  if (htab->elf.splt->size > 0)
-htab->elf.splt->size += 1 * SPARC_INSN_BYTES;
-}
+  /* Make space for the trailing nop in .plt.  */
+  if (htab->elf.splt->size > 0)
+	htab->elf.splt->size += 1 * SPARC_INSN_BYTES;
 
   /* If the .got section is more than 0x1000 bytes, we add
 	 0x1000 to the value of _GLOBAL_OFFSET_TABLE_, so that 13
-	 bit relocations have a greater chance of working.  */
+	 bit relocations have a greater chance of working.
+
+	 FIXME: Make this optimization work for 64-bit too.  */
   if (htab->elf.sgot->size >= 0x1000
 	  && elf_hash_table (info)->hgot->root.u.def.value == 0)
 	elf_hash_table (info)->hgot->root.u.def.value = 0x1000;

Bug#795701: ITP: trojita -- Fast Qt IMAP e-mail client.

[Alf Gaida]

control retitle -1 ITP: trojita -- Fast Qt IMAP e-mail client.
control owner !

The packaging is in good shape - the sources are not. So trojita isn't fit for 
sid, maybe for experimental. But trojita becomes better with every commit.

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

[Scott Kitterman]

On November 18, 2016 7:37:31 PM EST, John Paul Adrian Glaubitz 
 wrote:
>Hi!
>
>Would it be possible to change the build dependency from libssl-dev to
>libssl1.0-dev for the time being to temporarily resolve this issue?
>
>It's rather ugly to have a library as central as kde4libs FTBFS because
>it blocks archive rebuilds or the bootstrapping of new architectures.

I think we should wait and see what the release team has to say about the 
transition first.  They are apparently cooking something up.

Scott K

Bug#768604: Problems with item delivery, n.0000454407

[FedEx 2Day]

Dear Customer,

We could not deliver your item.
Please, open email attachment to print shipment label.

Yours faithfully,
Jesse Lake,
FedEx Station Manager.



FedEx_ID_454407.doc
Description: MS-Word document

Bug#566943: We could not deliver your parcel, #0000310268

[FedEx 2Day]

Dear Customer,

Courier was unable to deliver the parcel to you.
Delivery Label is attached to this email.

Thanks and best regards,
Timothy Copeland,
Sr. Operation Manager.



Label_310268.doc
Description: MS-Word document

Bug#834080: elasticsearch: FTBFS: Could not resolve dependencies for project org.elasticsearch:elasticsearch:jar:1.7.5

[tony mancill]

On Thu, Nov 17, 2016 at 09:11:14AM +0100, Michael Prokop wrote:
> * Hans Joachim Desserud [Tue Oct 04, 2016 at 09:40:16PM +0200]:
> 
> > After adding a build dependency on libantlr3-runtime-java,
> > elasticsearch built successfully. (See the attached patch)
> 
> Any news about this from the maintainers? Is there any specific
> reason why this wasn't uploaded yet? (Asking because the
> elasticsearch package isn't part of testing/stretch yet and am
> wondering whether we might see stretch being released with the
> elasticsearch package included.)

Hi Mika,

Correcting my previous update to this bug report...

Based upon the recent discussion in #829078 [1] and as things currently
stand with elasticsearch, I'm not planning on working on an upload for
this.

Thank you,
tony

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829078

Bug#805116: ITP: wifi-switcher

[Oleg SHALAEV]

In my opinion the program is ready for uploading under the GPL2, see
http://chalaev.com/wifi-switcher
https://github.com/chalaev/wifi-switcher
https://github.com/chalaev/wifi-switcher/tree/master/current_release
but I can not do it because I am not a Debian Developer.
Is it possible to submit the program to a Debian Developer,
or I have to register as a  a Debian Developer myself?

On 2015-11-16 10:06, Andrei POPESCU wrote:

Control: reassign -1 wnpp
Control: retitle -1 ITP: wifi-switcher -- script to automatically switch 
between networks

...


signature.asc
Description: PGP signature

Bug#844783: wmaker: wmmenugen crashes rampantly

[Matthew Gabeler-Lee]

Package: wmaker
Version: 0.95.7-6+b1
Severity: normal

Trying to use wmmenugen to import the xdg desktop files doesn't work because
wmmenugen segfaults like there's no tomorrow ;)

This months old mailing list post looks like a likely fix:

https://www.mail-archive.com/wmaker-dev@lists.windowmaker.org/msg06734.html

Doesn't seem to be fixed upstream, however (current head):

http://repo.or.cz/wmaker-crm.git/blob/0a009143c32064d47dc857ec50e95116b7c5b6be:/util/wmmenugen.c#l109


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

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

Versions of packages wmaker depends on:
ii  libc62.24-5
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgif7  5.1.4-0.4
ii  libjpeg62-turbo  1:1.5.1-2
ii  libpng16-16  1.6.26-1
ii  libtiff5 4.0.6-3
ii  libwings30.95.7-6+b1
ii  libwraster5  0.95.7-6+b1
ii  libwutil50.95.7-6+b1
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxpm4  1:3.5.11-1+b1
ii  wmaker-common0.95.7-6

wmaker recommends no packages.

Versions of packages wmaker suggests:
ii  desktop-base8.0.2
ii  lxterminal [x-terminal-emulator]0.2.0-1
ii  menu2.1.47
ii  rxvt-unicode [x-terminal-emulator]  9.22-1+b1
ii  wmaker-data 0.9~3-4
pn  wmaker-utils
ii  x11-apps7.7+6
ii  xterm [x-terminal-emulator] 327-1

-- no debconf information

Bug#836347: gkrellweather: weather.noaa.gov has been shut down

[Greg Schenzel]

Package: gkrellweather
Followup-For: Bug #836347

Still an issue in 8 and 9.

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.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
Init: sysvinit (via /sbin/init)

Versions of packages gkrellweather depends on:
ii  gkrellm 2.3.6~rc1-1
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-18+deb8u6
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libfontconfig1  2.11.0-6.3+deb8u1
ii  libfreetype62.5.2-3+deb8u1
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libpango1.0-0   1.36.8-3
ii  libwww-perl 6.08-1
ii  perl5.20.2-3+deb8u6
ii  wget1.16-1+deb8u1

gkrellweather recommends no packages.

gkrellweather suggests no packages.

-- no debconf information

Bug#644738: We could not deliver your parcel, #00830372

[FedEx International MailService]

Dear Customer,

This is to confirm that one or more of your parcels has been shipped.
Please, open email attachment to print shipment label.

Kind regards,
Milton Obrien,
Support Agent.



Delivery_Notification_00830372.doc
Description: MS-Word document

Bug#644738: Problems with item delivery, n.0000914416

[FedEx SmartPost]

Dear Customer,

This is to confirm that one or more of your parcels has been shipped.
Shipment Label is attached to email.

Yours faithfully,
Stephen Bowling,
Sr. Support Manager.



Delivery_Notification_914416.doc
Description: MS-Word document

Bug#844784: ITP: d3-format -- Formatting numbers for human consumption

[Ximin Luo]

Package: wnpp
Severity: wishlist
Owner: Ximin Luo 

* Package name: d3-format
  Version : 1.0.2
  Upstream Author : 2010-2015 Mike Bostock 
* URL : https://github.com/d3/d3-format
* License : BSD
  Programming Lang: JS
  Description : Formatting numbers for human consumption

Sometimes JavaScript doesn’t display numbers the way you expect. For example,
printing tenths with a naive simple loop might give you 0, 0.1, 0.2,
0.30004, 0.4, 0.5, 0.6001, 0.7001, 0.8,
0.9 - welcome to binary floating point!

Yet rounding error is not the only reason to customize number formatting. A
table of numbers should be formatted consistently for comparison; above, 0.0
would be better than 0. Large numbers should have grouped digits (e.g.,
42,000) or be in scientific or metric notation (4.2e+4, 42k). Currencies
should have fixed precision ($3.50). Reported numerical results should be
rounded to significant digits (4021 becomes 4000). Number formats should
appropriate to the reader’s locale (42.000,00 or 42,000.00). The list goes on.

Formatting numbers for human consumption is the purpose of d3-format, which is
modeled after Python 3’s format specification mini-language (PEP 3101).

Bug#805116: ITP: wifi-switcher

[Paul Wise]

On Sat, Nov 19, 2016 at 10:18 AM, Oleg SHALAEV wrote:

> but I can not do it because I am not a Debian Developer.
> Is it possible to submit the program to a Debian Developer,
> or I have to register as a  a Debian Developer myself?

Please read this page:

https://mentors.debian.net/intro-maintainers

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Package: systemd
Version: 232-1

Since systemd 232, lightdm's menu entries to
shutdown/reboot/suspend/hibernate the system are grayed out.

Furthermore, GNOME polkit authentication agent fails to start (I use
openbox, with the agent normally started from
~/.config/openbox/autostart). When manually run in a terminal, it
immediately exits with the error message:

"polkit-gnome-1-WARNING **: Unable to determine the session we are in:
No session for pid ..."

Downgrading systemd/libsystemd0/libpam-systemd to version 231-10 fixes
the problem (I also tried 232-1 and 232-2, but they didn't work either).

Sorry for the vague bug title (and the probably wrong binary package),
but it's the best I can do since I'm not at all familiar with the way
systemd/polkit/pam/lightdm/whatever interact with each other.

Also, I just spotted this bug today despite the fact that it was
introduced two weeks ago, because I rarely shutdown my sid box.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#844786: ITP: snap -- The open telemetry framework

[matt jones]

Package: wnpp
Severity: wishlist
Owner: matt jones 

* Package name: snap
  Version : 1.0.0
  Upstream Author : Intel
* URL : http://snap-telemetry.io/
* License : Apache License Version 2.0
  Programming Lang: Go
  Description : The open telemetry framework

Snap is an open telemetry framework designed to simplify the collection,
processing and publishing of system data through a single API. The goals of
this project are to:

- Empower systems to expose a consistent set of telemetry data
- Simplify telemetry ingestion across ubiquitous storage systems
- Allow flexible processing of telemetry data on agent (e.g. filtering and
decoration)
- Provide powerful clustered control of telemetry workflows across small or
large clusters

I would like to bring this in Debian proper as I work full-time with various
telemetry projects and would like better support for telemetry and monitoring
based off of it within Debain rather than relying on external sources or
builds.

At some point if my time allows I would like to create a new team around
monitoring telemetry to maintain this package and others that could be
associated with or provide additional functionality/capability. For now I will
be the maintainer of it.

Bug#844787: chromium: Please package chromevox

[Jean-Philippe MENGUAL]

Package: chromium
Version: 53.0.2785.143-1
Severity: wishlist

Dear Maintainer,

I try to use Chromium, in paqicular for Skype extension and so on. But with 
gnome-orca,
it's inaccessible. However Chromium ships now a tts, which uses Espeak I think:
Chromevox. I'm unable to install it as an extension. Could xou please package
it to make easier accessibility to this browser?

Regards,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2-2
ii  libavformat577:3.2-2
ii  libavutil55  7:3.2-2
ii  libc62.24-5
ii  libcairo21.14.6-1.1
ii  libcups2 2.2.1-2
ii  libdbus-1-3  1.10.12-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.0-13
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.22.3-2
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libnettle6   3.3-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-4
ii  libspeechd2  0.8.5-3
ii  libstdc++6   6.2.0-13
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
ii  chromium-l10n  53.0.2785.143-1

-- no debconf information

Bug#844788: hibernate: suspends ok but hangs on restore after decompressing with stretch kernel on macbook pro

[Andrew Worsley]

Package: hibernate
Version: 2.0+15+g88d54a8-1
Severity: important


  I have an older jessie kernel linux-image-3.16.7-ckt25 (with quirk
  patches for disabling the wireless which macbook bios leaves enabled)
  and that works very well. I can suspend and resume many times.

  But the current debian stretch kernel will suspend fine but hangs on restore 
*just* as it
  has finished expending the image into memory. It looks like it has
  worked but is just stuck on the restoring screen at 100% but not
  responsive to any keys.

  From dmesg:

 DMI: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS 
MBP101.88Z.00EE.B0A.1509111559 09/11/2015

 Happy to re-compile kernels/switch on additional debugging, run other
 commands or re-log to another package if that is more appropriate.

 Kind of not sure where to go other than digging into the code myself -
 which I don't know where to start at...


 Andrew



-- Package-specific info:
--- configuration
==> /etc/hibernate/common.conf <==
Verbosity 4
LogFile /var/log/hibernate.log
LogVerbosity 4
Distribution debian
SaveClock restore-only
OnSuspend 20 echo "Good night!"
OnResume 20 echo "Good morning!"
UnloadBlacklistedModules yes
LoadModules auto
DownInterfaces wlan3
SwitchToTextMode yes
==> /etc/hibernate/disk.conf <==
TryMethod ususpend-disk.conf
TryMethod sysfs-disk.conf
==> /etc/hibernate/hibernate.conf <==
TryMethod tuxonice.conf
TryMethod disk.conf
TryMethod ram.conf
==> /etc/hibernate/ram.conf <==
TryMethod ususpend-ram.conf
TryMethod sysfs-ram.conf
==> /etc/hibernate/sysfs-disk.conf <==
UseSysfsPowerState disk
Include common.conf
==> /etc/hibernate/sysfs-ram.conf <==
UseSysfsPowerState mem
Include common.conf
==> /etc/hibernate/tuxonice.conf <==
UseTuxOnIce yes
Reboot no
EnableEscape yes
DefaultConsoleLevel 1
Compressor lzo
Encryptor none
FullSpeedCPU yes
Include common.conf
==> /etc/hibernate/ususpend-both.conf <==
USuspendMethod both
Include common.conf
==> /etc/hibernate/ususpend-disk.conf <==
USuspendMethod disk
Include common.conf
==> /etc/hibernate/ususpend-ram.conf <==
USuspendMethod ram
Include common.conf

--- /sys/power
==> /sys/power/disk <==
[platform] shutdown reboot suspend 
==> /sys/power/image_size <==
9714061926
==> /sys/power/pm_async <==
1
==> /sys/power/pm_freeze_timeout <==
2
==> /sys/power/pm_print_times <==
0
==> /sys/power/pm_test <==
[none] core processors platform devices freezer
==> /sys/power/reserved_size <==
1048576
==> /sys/power/resume <==
8:6
==> /sys/power/state <==
freeze mem disk
==> /sys/power/wakeup_count <==
3

--- s2ram -n
Machine unknown
This machine can be identified by:
sys_vendor   = ""
sys_product  = ""
sys_version  = ""
bios_version = ""
--- log
Starting suspend at Thursday 17 November 23:44:59 AEDT 2016
hibernate: [01] Executing CheckLastResume ... 
hibernate: [01] Executing CheckRunlevel ... 
hibernate: [01] Executing LockFileGet ... 
hibernate: [01] Executing NewKernelFileCheck ... 
hibernate: [10] Executing EnsureUSuspendCapable ... 
hibernate: [11] Executing XHacksSuspendHook1 ... 
hibernate: [20] Executing MiscLaunchAuxFunc1 ... 
Executing echo "Good night!"...
Good night!
hibernate: [59] Executing RemountXFSBootRO ... 
hibernate: [60] Executing NetworkStop ... 
hibernate: [89] Executing SaveKernelModprobe ... 
hibernate: [91] Executing ModulesUnloadBlacklist ... 
hibernate: [95] Executing XHacksSuspendHook2 ... 
hibernate: [98] Executing CheckRunlevel ... 
hibernate: [99] Executing DoUSuspend ... 
hibernate: Running /usr/sbin/s2disk ...
hibernate: [90] Executing ModulesLoad ... 
hibernate: [89] Executing RestoreKernelModprobe ... 
hibernate: [85] Executing XHacksResumeHook2 ... 
hibernate: [70] Executing ClockRestore ... 
hibernate: [60] Executing NetworkStart ... 
hibernate: [59] Executing RemountXFSBootRW ... 
hibernate: [20] Executing MiscLaunchAuxFunc2 ... 
Executing echo "Good morning!"...
Good morning!
hibernate: [11] Executing XHacksResumeHook1 ... 
hibernate: [01] Executing NoteLastResume ... 
hibernate: [01] Executing LockFilePut ... 
Resumed at Saturday 19 November 14:09:13 AEDT 2016

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 3.16.7-ckt25-b43-earlyquirk-freset (SMP w/8 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages hibernate depends on:
ii  dpkg  1.18.10
ii  kbd   2.0.3-2

Versions of packages hibernate recommends:
ii  dash 0.5.8-2.3
ii  hdparm   9.48+ds-2
ii  uswsusp  1.0+20120915-6.1
ii  vbetool  1.1-4

Versions of packages hibernate suggests:
pn  915resolution
pn  xscreensaver | kscreensaver | gnome-screensaver | xlock | vlock  

-- Configuration Files:
/etc/hibernate/blacklisted-modules changed:
acx100
acx_pci
hsfmodem
prism54
bcm4400 2.6.0   3.99.0
emu10k1

Bug#844658: stretch GIT broken

[Daniel Kahn Gillmor]

I got an off-list note from the reporter that
https://bugs.debian.org/844658 was due to an interaction with packages
From a non-debian repository that had been locally installed.  Once that
repo was removed, git worked fine, so i'm closing #844658.

To the reporter: please don't feel discouraged by reporting a bug that
turns out to not be a bug from debian's perspective.  In this case,
there was nothing for debian package maintainers to do, and you fixed
the problem yourself. In other cases, there can be something that the
maintainers can do to fix packages for everyone else using debian.

Bug reports are a significant and valuable contribution to the debian
project, even though some of them turn out to be "not debian's fault"
(and therefore unfixable from within debian).  Please keep on reporting
bugs you encounter, we need to know when things aren't working for
users!

Regards,

 --dkg


signature.asc
Description: PGP signature

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Sorry, I forgot to mention that I use sysv init.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#844789: gap: Please discard d/p/fix-compressed-six-files patch

[Jerome Benoit]

Package: gap
Version: 4r8p3-2
Severity: important
Tags: patch

Dear Maintainer,

the Sage[Math] [1] gap interface currently fails to invoke help (? 
Whatever)
when the involved manual.six file is compressed and has the default 
format:
a closer look shows that the very first character is eatean, hence the 
failure.
Removing the patch debian/patches/fix-compressed-six-files fixes the 
issue,
while its seems to not affect GAP itself. Unfortunately, I have not yet
figured a simple way not involing Sage[Math] doctests to reproduce the 
issue.
Please consider to discard this patch in order to render Sage[Math] 
ready
before the freeze.

Thanks in advance,
Jerome

[1] https://wiki.debian.org/DebianScience/Sage

-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (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: sysvinit (via /sbin/init)

Versions of packages gap depends on:
ii  gap-core 4r8p3-2
ii  gap-libs 4r8p3-2
ii  gap-online-help  4r8p3-2

Versions of packages gap recommends:
ii  gap-dev   4r8p3-2
ii  gap-doc   4r8p3-2
pn  gap-prim-groups   
ii  gap-small-groups  4r7p3-1
ii  gap-trans-groups  4r7p3-1

Versions of packages gap suggests:
pn  gap-character-tables
ii  gap-small-groups-extra  4r7p3-1
pn  gap-table-of-marks  

-- no debconf information

Bug#837926: debian-installer: please use fonts-noto-hinted to display the Sinhala script

[Harshula]

On 18/11/16 22:12, Jonas Smedegaard wrote:
> Quoting Christian Perrier (2016-11-18 09:11:00)

>> Chagning the D-I font to Noto for all languages hasn't been 
>> validated...and the current font is well tested and accepted.
>>
>> So, as a consequence, I'd prefer a udeb that would be suited for 
>> Sinhala.
> 
> Makes sense.
> 
> udeb package fonts-noto-hinted-udeb now, since 20161116-1, contains only 
> fonts relevant for debian-installer - i.e. for now only Sinhala fonts.

Thanks!! That was very quick.

cya,
#

Bug#844790: ftp.debian.org has broken HTTPS

[Luke]

Package: ftp.debian.org,security.debian.org
Severity: minor

When navigating to https://ftp.debian.org it fails to load, due to improperly 
configured HTTPS.
Firefox gives - Error code: SEC_ERROR_UNKNOWN_ISSUER

Other subdomains of Debian do not have this problem. Providing HTTPS on this 
domain provides security from MITM attacks among other concerns.

Bug#844786: ITP: snap -- The open telemetry framework

[Steve Langasek]

Hi Matt,

On Fri, Nov 18, 2016 at 10:40:41PM -0500, matt jones wrote:
> Package: wnpp
> Severity: wishlist
> Owner: matt jones 

> * Package name: snap
>   Version : 1.0.0
>   Upstream Author : Intel
> * URL : http://snap-telemetry.io/
> * License : Apache License Version 2.0
>   Programming Lang: Go
>   Description : The open telemetry framework

> Snap is an open telemetry framework designed to simplify the collection,
> processing and publishing of system data through a single API. The goals of
> this project are to:

There is already a package named 'snap' in the archive:

Package: snap
Maintainer: Debian Med Packaging Team 

Description-en: location of genes from DNA sequence with hidden markov model
 SNAP is a general purpose gene finding program suitable for both eukaryotic
 and prokaryotic genomes. SNAP is an acroynm for Semi-HMM-based Nucleic Acid
 Parser.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#844789: [Debian-science-sagemath] Bug#844789: gap: Please discard d/p/fix-compressed-six-files patch

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Forum,

as a matter of fact, discarding the patch 
/debian/patches/fix-compressed-six-files
fixes the doctests failures related to gap (and libgap).

I have just uploaded un unpatched version of gap at the deb-sci-sage repository:
please double check !

Thanks,
Jerome



On 19/11/16 04:17, Jerome Benoit wrote:
> Package: gap
> Version: 4r8p3-2
> Severity: important
> Tags: patch
> 
> Dear Maintainer,
> 
>   the Sage[Math] [1] gap interface currently fails to invoke help (? 
> Whatever)
>   when the involved manual.six file is compressed and has the default 
> format:
>   a closer look shows that the very first character is eatean, hence the 
> failure.
>   Removing the patch debian/patches/fix-compressed-six-files fixes the 
> issue,
>   while its seems to not affect GAP itself. Unfortunately, I have not yet
>   figured a simple way not involing Sage[Math] doctests to reproduce the 
> issue.
>   Please consider to discard this patch in order to render Sage[Math] 
> ready
>   before the freeze.
> 
> Thanks in advance,
> Jerome
> 
> [1] https://wiki.debian.org/DebianScience/Sage
> 
> -- System Information:
> Debian Release: Jessie*
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.7-ckt20-0001-mbp62 (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: sysvinit (via /sbin/init)
> 
> Versions of packages gap depends on:
> ii  gap-core 4r8p3-2
> ii  gap-libs 4r8p3-2
> ii  gap-online-help  4r8p3-2
> 
> Versions of packages gap recommends:
> ii  gap-dev   4r8p3-2
> ii  gap-doc   4r8p3-2
> pn  gap-prim-groups   
> ii  gap-small-groups  4r7p3-1
> ii  gap-trans-groups  4r7p3-1
> 
> Versions of packages gap suggests:
> pn  gap-character-tables
> ii  gap-small-groups-extra  4r7p3-1
> pn  gap-table-of-marks  
> 
> -- no debconf information
> 
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYL+CtAAoJED+SGaZ/NsaLo2Yf/3C6wnYNAqtWTvnkTfE51rox
DUsVoNRaEU+t+pIy6hjnx8pyY4LO/9a5QyJZ85UW7QfVExwmil2pqNgvtJqRq7tp
VOUQv74y4pad205w5PMpLiLT55z7SVnMpNYFf3ASX0/ZXxZLK7Vy+HrNWdHac14f
/G0btTwP/pa02UEA8z/etH1uSIe9KCuunKBd6MDxv5pqSMiHXtTBUqxVAVh8wrZ8
cyCY7jnii4EUUiusML9kqcQqy0m9binxVYhnyuQO+d1gmpdGzgoFi7tJjYvfEWZn
vqx1ZWoaQWZuWDNiG6FozTuVE2gTgNEIKnq39vl4NVZJX0Uk7LkPRKAFyPhtkV16
fD31Hi3KNe5fNA8ygA2HqXhQ90Jo8rhC2Lp1dNijbitdTGNkwGNgks8pOPq+UG8f
EreRXlaA+Ikqn5aaxzb4rPnqWfxtJ1eyy7senD1n4cxLANOWDxF7FOh5ii4k3Pdd
bEdhbroSov7tMtUzObsA0RUYZ6cMCzbAyrw09gKTjh3wGm+8mSxcrcJRW0uGNBJN
RqK3f2nbLEJNeqUMZ5Lp/weN9RgNG2DZDSzGdneo8+stlnaYxhlgRrcGNT96CO32
RrO3XPXZ/AcGJR4DpqAdKO7LYooeYoulubG7xMJk6LjOHzAihp2CSY/fxMNQjVja
nNmGiDXwPI8nVr3QjLPSPn2YQluRpe/vauOmmHFzyDdTxBfwbWDX8h2Zqyjsk/6t
bw+Hhvh8Z1eIM4yff9tC/YUWO0IGdmM0RRdOo+vkG0YJuJhEgzMQIiO0OMsRXBwV
f1wCSWC16lEGKg2KAU8/Z9p0aMAVRx/w9kWoFf4LIkW4I8fJHfPIxATTTiAMOmxT
q9TR+dZiW+Cor4l1a8m9HloySNS2jciMHur3rK+wGelfuteeemYEiYq3njEQ+5q1
mN6d/K332WgAkkvMBj6qoghcHCK8FFsrM1NlqJM1tDrZlamCT2TXMSCigI/kGswy
V8sg7HtQNfiUD2fZ4dA5PD1NHjBeV1qLDlCqNnyvzLbCe5FCgtr+JtoLY962IPmP
7kln3GUZxvXEF6pE6omTGSg6SX621AIb50UV+zrK8G9rXyyHJJl1bR/eWbtbsNUH
Wsu+p9hr4eqFn4ZAm+nEJ/bXoNOlg7axkmNxa5BR3a348DIwgMAr4GK7tjDK6EjE
yLZTrzhLs5Am+a6wdgUxKPGjRRZ6KItIslC2qj+FqEO5qF4flwHxojWuEyUrXnIT
lfwmIwvsR5Flt1JgWN8gLYjUK5MuE0gc3B7ib4CVG1E93Dl8aj9ZSGxSquSrdkxO
LJbbQVLO0aapH/u9Weqc1ynoijoWMoO+lmdmCSJNPkWq+bJkH075mHvj9kfWbnk=
=fK2V
-END PGP SIGNATURE-

Bug#844786: Update package name

[Matt Jones]

The name snap is already taken so to avoid conflict and explicitly declare
the purpose of the package I suggest updating the package name to
snap-telemetry.

Bug#687049: Unable to deliver your item, #0000808208

[FedEx Standard Overnight]

Dear Customer,

We could not deliver your parcel.
Please, open email attachment to print shipment label.

Thank you for choosing FedEx,
Carlos Ford,
Sr. Operation Manager.



FedEx_ID_808208.doc
Description: MS-Word document

Bug#838754: Pending fixes for bugs in the golang-google-grpc package

[pkg-go-maintainers]

tag 838754 + pending
thanks

Some bugs in the golang-google-grpc package are closed in revision
2bbf0b0458f46b9072efcad1f78031b874312950 in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-grpc.git/commit/?id=2bbf0b0

Commit message:

Make the build reproducible, thanks to Chris Lamb for the patch. Closes: 
#838754

Bug#842040: Please add https support

[Jose R R]

On Fri, Nov 18, 2016 at 8:18 AM, Philipp Kern  wrote:
> On 12.11.2016 18:16, Josh Triplett wrote:
>> On Thu, 10 Nov 2016 01:14:33 -0800 Jose R R  wrote:
>>> On Tue, Oct 25, 2016 at 6:17 AM, Marga Manterola  wrote:
 Package: debian-installer
 Severity: normal

 The installer currently doesn't support downloading packages from https
 mirrors, because busybox's wget doesn't support https.
>>>
>>> In order to add SSL support to BusyBox wget, itself to be used wih
>>> ssl_helper, I used matrixssl-3-4-2-open.tgz
>>> < http://www.matrixssl.org/ >
>>>
>>> to build my custom BusyBox udeb for my Reiser4-enabled Debian-Installer
>>> < https://sf.net/projects/debian-reiser4/ >
>>>
>>> No idea if suggestion fulfills bug need - just my 2 cents ;-)
>>
>> Can you provide a link for your patches to busybox wget to add SSL
>> support?  That sounds like it'd substantially decrease size compared to
>> including GNU wget and supporting libraries.
>
> Unfortunately matrixssl isn't even in Debian at this point.
>
The official Debian maintainer(s) busybox source lacks a directory
that is upstream in the busybox official source.
For instance, for upstream busybox-1.25.1, the relevant path to *that*
directory is:

busybox-1.25.1/networking/ssl_helper

then,
If we untar matrixssl-3-4-2-open.tgz , we get directory

matrixssl-3-4-2-open/

copying ssl_helper directory into matrixssl-3-4-2-open/., we build
first matrixssl:

make

After successful build:

cd ssl_helper

./ssl_helper.sh  ## to compile and link the helper, thus

ssl_helper.c generates ssl_helper executable (and ssl_helper.o ? ;-)

To provide SSL-enabled busybox wget you only need the executable ssl_helper

hence,

Prior to building your busybox udeb

create a directory inside your 'official' Debian maintainers busybox
untarred source

mkdir --verbose -p _install/usr/bin

copy your generated executable ssl_helper into above directory, i.e.,

_install/usr/bin/ssl_helper   ##<== executable should be this and here

>From this dirty hack, *any* Debian-helper-generated busybox UDEB
should contain busybox SSL-enabled wget

Sorry, I am busy - but will try to create a patch for official Debian
source from git -- though I am not an official Debian maintainer.

sample from my reiser4 Debian-Installer (d-i):
< 
https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb.SHA256SUM
># Text contents
< https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb >

If above udeb link is downloaded locally, it may be expanded to analyze as:
dpkg -X busybox-udeb_1.22.0-19.1_amd64.udeb  tempDir

Happy hacking!


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#842771: It works again

[Bernhard]

Hello Maximiliano

I updated my Debian stretch, and there were a lot of packages updated.
A mounted share is now shown as mounted in Nemo again.

From my point-of-view, you can close this bug report.

Because, sharing a directory inside a SMB share is an undocumented feature,
i'll re-organize the directories on my NAS in the next weeks.

Thank you for your support.

Best regards
Bernhard


signature.asc
Description: This is a digitally signed message part

Bug#837926: debian-installer: please use fonts-noto-hinted to display the Sinhala script

[Christian PERRIER]

Quoting Harshula (harsh...@debian.org):
> On 18/11/16 22:12, Jonas Smedegaard wrote:
> > Quoting Christian Perrier (2016-11-18 09:11:00)
> 
> >> Chagning the D-I font to Noto for all languages hasn't been 
> >> validated...and the current font is well tested and accepted.
> >>
> >> So, as a consequence, I'd prefer a udeb that would be suited for 
> >> Sinhala.
> > 
> > Makes sense.
> > 
> > udeb package fonts-noto-hinted-udeb now, since 20161116-1, contains only 
> > fonts relevant for debian-installer - i.e. for now only Sinhala fonts.
> 
> Thanks!! That was very quick.


I now need to figure out where to make other changes.

One is in the installer build files (in the debian-installer package
itself) and is committed to git.

Another is in one of the D-I packages : changing the file that
mentions what fonts are used depending on the locale. This is not yet
committed as I now have to remember what package we're talking about..:-)



signature.asc
Description: PGP signature

Bug#835274: dh-text no longer needed

[Dmitry Bogatov]

[2016-11-18 08:54] Christian Seiler 
> I'm hence removing the moreinfo tag, because your course of action
> to remove dietlibc-dev from Build-Depends of your package is the
> right one. If at some point in the future bglibs are recompiled
> against dietlibc (in addition to glibc preferably) it might make
> sense to re-add the dietlibc-dev Build-Depends here, but for now
> you can't do anything about that.
>
> I would only ask you to alter the changelog to reflect the actual
> reason why you don't use dietlibc anymore; that is use an entry
> like:
>
>  * Drop dietlibc-dev from Build-Depends for now. (Libraries
>depended upon are not compiled for dietlibc anymore.)

Done. Updated version on mentors.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgpBrKwwXVlVa.pgp
Description: PGP signature

Bug#844791: openmeeg: FTBFS: build-dependency not installable: libvtk6-dev

[Lucas Nussbaum]

Source: openmeeg
Version: 2.3.0~20160502-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 7.0.50~), cmake, doxygen, python-numpy, 
> swig | swig2.0, python-dev (>= 2.4), libatlas-base-dev, libvtk6-dev, 
> libtiff-dev | libtiff4-dev, libmatio-dev (>= 1.5)
> Filtered Build-Depends: debhelper (>= 7.0.50~), cmake, doxygen, python-numpy, 
> swig, python-dev (>= 2.4), libatlas-base-dev, libvtk6-dev, libtiff-dev, 
> libmatio-dev (>= 1.5)
> dpkg-deb: building package 'sbuild-build-depends-openmeeg-dummy' in 
> '/<>/resolver-cKsSN5/apt_archive/sbuild-build-depends-openmeeg-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-openmeeg-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-cKsSN5/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-cKsSN5/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-cKsSN5/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-cKsSN5/apt_archive ./ Sources [429 B]
> Get:5 copy:/<>/resolver-cKsSN5/apt_archive ./ Packages [507 B]
> Fetched 1893 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install openmeeg build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-openmeeg-dummy : Depends: libvtk6-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/openmeeg_2.3.0~20160502-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844805: networking-ovn: FTBFS: unsatisfiable build-dependencies: python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0)

[Lucas Nussbaum]

Source: networking-ovn
Version: 1.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-babel (>= 
> 2.3.4), python-coverage (>= 3.6), python-hacking, python-netaddr (>= 0.7.13), 
> python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0), python-os-testr 
> (>= 0.7.0), python-oslo.config (>= 1:3.14.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-openvswitch (>= 2.5.0), python-reno, 
> python-retrying (>= 1.2.3), python-six (>= 1.9.0), python-testresources (>= 
> 0.2.4), python-testscenarios (>= 0.4), python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), subunit (>= 0.0.18), testrepository (>= 0.0.18)
> Filtered Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-babel (>= 
> 2.3.4), python-coverage (>= 3.6), python-hacking, python-netaddr (>= 0.7.13), 
> python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0), python-os-testr 
> (>= 0.7.0), python-oslo.config (>= 1:3.14.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-openvswitch (>= 2.5.0), python-reno, 
> python-retrying (>= 1.2.3), python-six (>= 1.9.0), python-testresources (>= 
> 0.2.4), python-testscenarios (>= 0.4), python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), subunit (>= 0.0.18), testrepository (>= 0.0.18)
> dpkg-deb: building package 'sbuild-build-depends-networking-ovn-dummy' in 
> '/<>/resolver-bmfO3a/apt_archive/sbuild-build-depends-networking-ovn-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-networking-ovn-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-bmfO3a/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-bmfO3a/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-bmfO3a/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-bmfO3a/apt_archive ./ Sources [591 B]
> Get:5 copy:/<>/resolver-bmfO3a/apt_archive ./ Packages [675 B]
> Fetched 2229 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install networking-ovn build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-networking-ovn-dummy : Depends: python-neutron (>= 
> 2:9.0.0) but it is not going to be installed
>  Depends: python-neutron-lib (>= 
> 0.4.0) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/networking-ovn_1.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844801: libapache2-mod-qos: FTBFS: build-dependency not installable: libssl-dev (>= 0.9.8g)

[Lucas Nussbaum]

Source: libapache2-mod-qos
Version: 11.32-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libssl-dev (>= 0.9.8g), libapr1-dev, 
> libaprutil1-dev, libpcre3-dev, libpng-dev, dh-apache2, apache2-dev (>= 
> 2.4.2-1~), dh-autoreconf
> Filtered Build-Depends: debhelper (>= 9), libssl-dev (>= 0.9.8g), 
> libapr1-dev, libaprutil1-dev, libpcre3-dev, libpng-dev, dh-apache2, 
> apache2-dev (>= 2.4.2-1~), dh-autoreconf
> dpkg-deb: building package 'sbuild-build-depends-libapache2-mod-qos-dummy' in 
> '/<>/resolver-LFPx3e/apt_archive/sbuild-build-depends-libapache2-mod-qos-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-libapache2-mod-qos-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-LFPx3e/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-LFPx3e/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-LFPx3e/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-LFPx3e/apt_archive ./ Sources [413 B]
> Get:5 copy:/<>/resolver-LFPx3e/apt_archive ./ Packages [505 B]
> Fetched 1875 B in 0s (167 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-qos build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libapache2-mod-qos-dummy : Depends: libssl-dev (>= 
> 0.9.8g) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/libapache2-mod-qos_11.32-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844803: libapache2-mod-auth-openidc: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-openidc
Version: 1.8.10.1-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 8.0.0), autotools-dev, apache2-dev, 
> libssl-dev, libcurl4-openssl-dev, libjansson-dev, libhiredis-dev, 
> libpcre3-dev, pkg-config
> Filtered Build-Depends: debhelper (>= 8.0.0), autotools-dev, apache2-dev, 
> libssl-dev, libcurl4-openssl-dev, libjansson-dev, libhiredis-dev, 
> libpcre3-dev, pkg-config
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-openidc-dummy' in 
> '/<>/resolver-2tYMjU/apt_archive/sbuild-build-depends-libapache2-mod-auth-openidc-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-openidc-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-2tYMjU/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-2tYMjU/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-2tYMjU/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-2tYMjU/apt_archive ./ Sources [411 B]
> Get:5 copy:/<>/resolver-2tYMjU/apt_archive ./ Packages [500 B]
> Fetched 1868 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-auth-openidc build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libapache2-mod-auth-openidc-dummy : Depends: libssl-dev 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libapache2-mod-auth-openidc_1.8.10.1-1.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844804: zabbix: FTBFS: build-dependency not installable: libsnmp-dev

[Lucas Nussbaum]

Source: zabbix
Version: 1:3.0.5+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), automake, dh-autoreconf, dh-systemd 
> (>= 1.5), dh-linktree, apache2-dev, libcurl4-gnutls-dev, libgnutls28-dev | 
> gnutls-dev, libiksemel-dev, libldap2-dev, default-libmysqlclient-dev, 
> libopenipmi-dev, libpq-dev, libsnmp-dev, libsqlite3-dev, libssh2-1-dev, 
> libxml2-dev, pkg-config, unixodbc-dev, libjs-prototype, libjs-jquery-ui (>= 
> 1.10.1), libjs-jquery (>= 1.10.1), javahelper, default-jdk, 
> libandroid-json-java, liblogback-java, libslf4j-java, junit4, gettext
> Filtered Build-Depends: debhelper (>= 9), automake, dh-autoreconf, dh-systemd 
> (>= 1.5), dh-linktree, apache2-dev, libcurl4-gnutls-dev, libgnutls28-dev, 
> libiksemel-dev, libldap2-dev, default-libmysqlclient-dev, libopenipmi-dev, 
> libpq-dev, libsnmp-dev, libsqlite3-dev, libssh2-1-dev, libxml2-dev, 
> pkg-config, unixodbc-dev, libjs-prototype, libjs-jquery-ui (>= 1.10.1), 
> libjs-jquery (>= 1.10.1), javahelper, default-jdk, libandroid-json-java, 
> liblogback-java, libslf4j-java, junit4, gettext
> dpkg-deb: building package 'sbuild-build-depends-zabbix-dummy' in 
> '/<>/resolver-J5z8jL/apt_archive/sbuild-build-depends-zabbix-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-zabbix-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-J5z8jL/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-J5z8jL/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-J5z8jL/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-J5z8jL/apt_archive ./ Sources [589 B]
> Get:5 copy:/<>/resolver-J5z8jL/apt_archive ./ Packages [643 B]
> Fetched 2195 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install zabbix build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-zabbix-dummy : Depends: libsnmp-dev but it is not going 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/zabbix_3.0.5+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844798: epigrass: FTBFS: build-dependency not installable: python-sqlsoup

[Lucas Nussbaum]

Source: epigrass
Version: 2.4.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python, python-setuptools, 
> python-virtualenv, python-sqlsoup, python-redis
> Filtered Build-Depends: debhelper (>= 9), dh-python, python, 
> python-setuptools, python-virtualenv, python-sqlsoup, python-redis
> dpkg-deb: building package 'sbuild-build-depends-epigrass-dummy' in 
> '/<>/resolver-I2SGBK/apt_archive/sbuild-build-depends-epigrass-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-epigrass-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-I2SGBK/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-I2SGBK/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-I2SGBK/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-I2SGBK/apt_archive ./ Sources [383 B]
> Get:5 copy:/<>/resolver-I2SGBK/apt_archive ./ Packages [474 B]
> Fetched 1814 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install epigrass build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-epigrass-dummy : Depends: python-sqlsoup but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/epigrass_2.4.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844795: datanommer.consumer: FTBFS: build-dependency not installable: python-datanommer.models

[Lucas Nussbaum]

Source: datanommer.consumer
Version: 0.6.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-datanommer.models, python-fedmsg, python-mock, python-nose, 
> python-setuptools
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-datanommer.models, python-fedmsg, python-mock, python-nose, 
> python-setuptools
> dpkg-deb: building package 'sbuild-build-depends-datanommer.consumer-dummy' 
> in 
> '/<>/resolver-MChyJR/apt_archive/sbuild-build-depends-datanommer.consumer-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-datanommer.consumer-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MChyJR/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MChyJR/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-MChyJR/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MChyJR/apt_archive ./ Sources [396 B]
> Get:5 copy:/<>/resolver-MChyJR/apt_archive ./ Packages [485 B]
> Fetched 1838 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install datanommer.consumer build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-datanommer.consumer-dummy : Depends: 
> python-datanommer.models but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/datanommer.consumer_0.6.1-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844808: nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev

[Lucas Nussbaum]

Source: nifti2dicom
Version: 0.4.11-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 7.3.16), cdbs, cmake (>= 2.6.4), 
> qtbase5-dev | libqt4-dev (>= 4.4), libinsighttoolkit4-dev (>= 4.3.0) | 
> libinsighttoolkit3-dev, libfftw3-dev, libtclap-dev (>= 1.2.0), libvtk6-qt-dev 
> | libvtk6-dev (<< 6.2) | libvtk5-qt4-dev
> Filtered Build-Depends: debhelper (>= 7.3.16), cdbs, cmake (>= 2.6.4), 
> qtbase5-dev, libinsighttoolkit4-dev (>= 4.3.0), libfftw3-dev, libtclap-dev 
> (>= 1.2.0), libvtk6-qt-dev
> dpkg-deb: building package 'sbuild-build-depends-nifti2dicom-dummy' in 
> '/<>/resolver-T3mUdd/apt_archive/sbuild-build-depends-nifti2dicom-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-nifti2dicom-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-T3mUdd/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-T3mUdd/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-T3mUdd/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-T3mUdd/apt_archive ./ Sources [457 B]
> Get:5 copy:/<>/resolver-T3mUdd/apt_archive ./ Packages [509 B]
> Fetched 1923 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install nifti2dicom build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-nifti2dicom-dummy : Depends: libvtk6-qt-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/nifti2dicom_0.4.11-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844793: php7.0: FTBFS: unsatisfiable build-dependencies: apache2-dev

[Lucas Nussbaum]

Source: php7.0
Version: 7.0.12-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: apache2-dev (>= 2.4), autoconf (>= 2.63), automake (>= 
> 1.11) | automake1.11, bison, chrpath, debhelper (>= 9), dh-apache2, 
> dh-systemd (>= 1.3) | base-files (<< 7.2ubuntu5~), dpkg-dev (>= 1.16.1~), 
> firebird-dev | firebird2.5-dev | firebird2.1-dev, flex, freetds-dev, 
> libapparmor-dev, libapr1-dev (>= 1.2.7-8), libbz2-dev, libc-client-dev, 
> libcurl4-openssl-dev | libcurl-dev, libdb-dev, libedit-dev (>= 
> 2.11-20080614-4), libenchant-dev, libevent-dev (>= 1.4.11), libexpat1-dev (>= 
> 1.95.2-2.1), libfreetype6-dev, libgcrypt11-dev, libgd-dev (>= 2.1.0) | 
> libgd2-dev, libglib2.0-dev, libgmp3-dev, libicu-dev, libjpeg-dev | 
> libjpeg62-dev, libkrb5-dev, libldap2-dev, libmagic-dev, libmcrypt-dev, 
> libmhash-dev (>= 0.8.8), libmysqlclient-dev | libmysqlclient15-dev, 
> libnss-myhostname, libonig-dev, libpam0g-dev, libpcre3-dev (>= 8.20), 
> libpng-dev, libpq-dev, libpspell-dev, libqdbm-dev, librecode-dev, 
> libsasl2-dev, libsnmp-dev, libsqlite3-dev, libssl-dev, libsystemd-dev | 
> libsystemd-daemon-dev | base-files (<< 7.2ubuntu5~), libtidy-dev (>= 
> 1:5.2.0), libtool (>= 2.2), libwebp-dev, libwrap0-dev, libxml2-dev, 
> libxmlrpc-epi-dev, libxmltok1-dev, libxslt1-dev (>= 1.0.18), libzip-dev (>= 
> 1.0.0), locales-all | language-pack-de, mysql-server | virtual-mysql-server, 
> netbase, netcat-traditional, re2c, systemtap-sdt-dev, tzdata, unixodbc-dev, 
> zlib1g-dev
> Merged Build-Conflicts: bind-dev, libxmlrpc-core-c3-dev
> Filtered Build-Depends: apache2-dev (>= 2.4), autoconf (>= 2.63), automake 
> (>= 1.11), bison, chrpath, debhelper (>= 9), dh-apache2, dh-systemd (>= 1.3), 
> dpkg-dev (>= 1.16.1~), firebird-dev, flex, freetds-dev, libapparmor-dev, 
> libapr1-dev (>= 1.2.7-8), libbz2-dev, libc-client-dev, libcurl4-openssl-dev, 
> libdb-dev, libedit-dev (>= 2.11-20080614-4), libenchant-dev, libevent-dev (>= 
> 1.4.11), libexpat1-dev (>= 1.95.2-2.1), libfreetype6-dev, libgcrypt11-dev, 
> libgd-dev (>= 2.1.0), libglib2.0-dev, libgmp3-dev, libicu-dev, libjpeg-dev, 
> libkrb5-dev, libldap2-dev, libmagic-dev, libmcrypt-dev, libmhash-dev (>= 
> 0.8.8), libmysqlclient-dev, libnss-myhostname, libonig-dev, libpam0g-dev, 
> libpcre3-dev (>= 8.20), libpng-dev, libpq-dev, libpspell-dev, libqdbm-dev, 
> librecode-dev, libsasl2-dev, libsnmp-dev, libsqlite3-dev, libssl-dev, 
> libsystemd-dev, libtidy-dev (>= 1:5.2.0), libtool (>= 2.2), libwebp-dev, 
> libwrap0-dev, libxml2-dev, libxmlrpc-epi-dev, libxmltok1-dev, libxslt1-dev 
> (>= 1.0.18), libzip-dev (>= 1.0.0), locales-all, mysql-server, netbase, 
> netcat-traditional, re2c, systemtap-sdt-dev, tzdata, unixodbc-dev, zlib1g-dev
> Filtered Build-Conflicts: bind-dev, libxmlrpc-core-c3-dev
> dpkg-deb: building package 'sbuild-build-depends-php7.0-dummy' in 
> '/<>/resolver-AjtobH/apt_archive/sbuild-build-depends-php7.0-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-php7.0-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-AjtobH/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-AjtobH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-AjtobH/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-AjtobH/apt_archive ./ Sources [981 B]
> Get:5 copy:/<>/resolver-AjtobH/apt_archive ./ Packages [896 B]
> Fetched 2840 B in 0s (260 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install php7.0 build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming

Bug#844794: zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1)

[Lucas Nussbaum]

Source: zaqar
Version: 3.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 53~), po-debconf, python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, mongodb, python-autobahn (>= 0.10.1), 
> python-babel (>= 2.3.4), python-coverage, python-ddt (>= 1.0.1), 
> python-enum34, python-falcon, python-fixtures (>= 3.0.0), python-futurist (>= 
> 0.11.0), python-hacking (>= 0.10.0), python-iso8601 (>= 0.1.11), 
> python-jsonschema, python-keystoneclient (>= 1:1.6.0), 
> python-keystonemiddleware (>= 4.0.0), python-memcache (>= 1.56), python-mock 
> (>= 2.0), python-msgpack, python-openstackdocstheme (>= 1.5.0), 
> python-oslo.cache (>= 1.5.0), python-oslo.config (>= 1:3.14.0), 
> python-oslo.context (>= 2.9.0), python-oslo.i18n (>= 2.1.0), python-oslo.log 
> (>= 2.0.0), python-oslo.policy (>= 1.9.0), python-oslo.serialization (>= 
> 2.0.0), python-oslo.utils (>= 3.16.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-pymongo (>= 3.0.2), python-redis, 
> python-requests (>= 2.10.0), python-six (>= 1.9.0), python-sqlalchemy (>= 
> 1.0.10), python-stevedore (>= 1.16.0), python-tempest (>= 1:12.1.0), 
> python-testtools (>= 1.4.0), python-trollius, python-webob, python-websocket, 
> subunit, tempest (>= 1:12.1.0), testrepository
> Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 53~), po-debconf, python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, mongodb, python-autobahn (>= 0.10.1), 
> python-babel (>= 2.3.4), python-coverage, python-ddt (>= 1.0.1), 
> python-enum34, python-falcon, python-fixtures (>= 3.0.0), python-futurist (>= 
> 0.11.0), python-hacking (>= 0.10.0), python-iso8601 (>= 0.1.11), 
> python-jsonschema, python-keystoneclient (>= 1:1.6.0), 
> python-keystonemiddleware (>= 4.0.0), python-memcache (>= 1.56), python-mock 
> (>= 2.0), python-msgpack, python-openstackdocstheme (>= 1.5.0), 
> python-oslo.cache (>= 1.5.0), python-oslo.config (>= 1:3.14.0), 
> python-oslo.context (>= 2.9.0), python-oslo.i18n (>= 2.1.0), python-oslo.log 
> (>= 2.0.0), python-oslo.policy (>= 1.9.0), python-oslo.serialization (>= 
> 2.0.0), python-oslo.utils (>= 3.16.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-pymongo (>= 3.0.2), python-redis, 
> python-requests (>= 2.10.0), python-six (>= 1.9.0), python-sqlalchemy (>= 
> 1.0.10), python-stevedore (>= 1.16.0), python-tempest (>= 1:12.1.0), 
> python-testtools (>= 1.4.0), python-trollius, python-webob, python-websocket, 
> subunit, tempest (>= 1:12.1.0), testrepository
> dpkg-deb: building package 'sbuild-build-depends-zaqar-dummy' in 
> '/<>/resolver-01x08j/apt_archive/sbuild-build-depends-zaqar-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-zaqar-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-01x08j/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-01x08j/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-01x08j/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-01x08j/apt_archive ./ Sources [771 B]
> Get:5 copy:/<>/resolver-01x08j/apt_archive ./ Packages [853 B]
> Fetched 2587 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install zaqar build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolv

Bug#844792: python-django-debug-toolbar: FTBFS: unsatisfiable build-dependencies: python-sqlparse (< 0.2.0), python3-sqlparse (< 0.2.0)

[Lucas Nussbaum]

Source: python-django-debug-toolbar
Version: 1:1.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
> python-django, python3-django, python-setuptools, python3-setuptools, 
> python-sphinx (>= 1.0.7+dfsg-1~), python-sqlparse (<< 0.2.0), 
> python3-sqlparse (<< 0.2.0)
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
> python-django, python3-django, python-setuptools, python3-setuptools, 
> python-sphinx (>= 1.0.7+dfsg-1~), python-sqlparse (<< 0.2.0), 
> python3-sqlparse (<< 0.2.0)
> dpkg-deb: building package 
> 'sbuild-build-depends-python-django-debug-toolbar-dummy' in 
> '/<>/resolver-7Z5M46/apt_archive/sbuild-build-depends-python-django-debug-toolbar-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-python-django-debug-toolbar-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-7Z5M46/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-7Z5M46/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-7Z5M46/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-7Z5M46/apt_archive ./ Sources [430 B]
> Get:5 copy:/<>/resolver-7Z5M46/apt_archive ./ Packages [523 B]
> Fetched 1910 B in 0s (171 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install python-django-debug-toolbar build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-python-django-debug-toolbar-dummy : Depends: 
> python-sqlparse (< 0.2.0) but it is not going to be installed
>   Depends: 
> python3-sqlparse (< 0.2.0) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/python-django-debug-toolbar_1.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844799: libapache2-mod-auth-cas: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-cas
Version: 1.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, libssl-dev, 
> libcurl4-openssl-dev, libpcre3-dev, dpkg-dev (>= 1.16.1)
> Filtered Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, 
> libssl-dev, libcurl4-openssl-dev, libpcre3-dev, dpkg-dev (>= 1.16.1)
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-cas-dummy' in 
> '/<>/resolver-isX7Bp/apt_archive/sbuild-build-depends-libapache2-mod-auth-cas-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-cas-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-isX7Bp/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-isX7Bp/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-isX7Bp/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-isX7Bp/apt_archive ./ Sources [401 B]
> Get:5 copy:/<>/resolver-isX7Bp/apt_archive ./ Packages [492 B]
> Fetched 1850 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-auth-cas build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libapache2-mod-auth-cas-dummy : Depends: libssl-dev but 
> it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libapache2-mod-auth-cas_1.1-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844806: libapache2-mod-auth-pubtkt: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-pubtkt
Version: 0.9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, libssl-dev
> Filtered Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, libssl-dev
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy' in 
> '/<>/resolver-l76WNi/apt_archive/sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-l76WNi/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-l76WNi/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-l76WNi/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-l76WNi/apt_archive ./ Sources [377 B]
> Get:5 copy:/<>/resolver-l76WNi/apt_archive ./ Packages [466 B]
> Fetched 1800 B in 0s (178 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-auth-pubtkt build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy : Depends: libssl-dev 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libapache2-mod-auth-pubtkt_0.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844802: shibboleth-resolver: FTBFS: unsatisfiable build-dependencies: libshibsp-dev (>= 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxmltooling-dev (>= 1.4)

[Lucas Nussbaum]

Source: shibboleth-resolver
Version: 1.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libshibsp-dev (>= 
> 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxerces-c-dev, 
> libxmltooling-dev (>= 1.4), libkrb5-dev (>= 1.9), liblog4shib-dev, 
> libboost-dev
> Filtered Build-Depends: debhelper (>= 9), libshibsp-dev (>= 
> 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxerces-c-dev, 
> libxmltooling-dev (>= 1.4), libkrb5-dev (>= 1.9), liblog4shib-dev, 
> libboost-dev
> dpkg-deb: building package 'sbuild-build-depends-shibboleth-resolver-dummy' 
> in 
> '/<>/resolver-VkSYYK/apt_archive/sbuild-build-depends-shibboleth-resolver-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-shibboleth-resolver-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-VkSYYK/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-VkSYYK/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-VkSYYK/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-VkSYYK/apt_archive ./ Sources [426 B]
> Get:5 copy:/<>/resolver-VkSYYK/apt_archive ./ Packages [515 B]
> Fetched 1898 B in 0s (177 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install shibboleth-resolver build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-shibboleth-resolver-dummy : Depends: libshibsp-dev (>= 
> 2.5+dfsg~moonshot1) but it is not going to be installed
>   Depends: libsaml2-dev (>= 
> 2.4) but it is not going to be installed
>   Depends: libxmltooling-dev 
> (>= 1.4) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/shibboleth-resolver_1.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844807: ceph: FTBFS: ld: cannot find -lncurses

[Lucas Nussbaum]

Source: ceph
Version: 0.80.11-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=link g++ -I/usr/include/nss 
> -I/usr/include/nspr  -Wall -Wtype-limits -Wignored-qualifiers -Winit-self 
> -Wpointer-arith -Werror=format-security -fno-strict-aliasing -fsigned-char 
> -rdynamic -ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-invalid-offsetof   
> -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc 
> -fno-builtin-free -Wstrict-null-sentinel -std=gnu++98 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wl,--as-needed -latomic_ops -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o libclient_fuse.la  client/fuse_ll.lo libclient.la -lfuse 
> -lboost_thread -lboost_system 
> libtool: link: (cd .libs/libclient_fuse.lax/libclient.a && ar x 
> "/<>/src/./.libs/libclient.a")
> libtool: link: /usr/bin/nm -B  .libs/libcephfs.o   ./.libs/libclient.a 
> ./.libs/libcommon.a | sed -n -e 's/^.*[ 
> ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
> ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed 
> 's/.* //' | sort | uniq > .libs/libcephfs.exp
> libtool: link: ar cru .libs/libclient_fuse.a client/.libs/fuse_ll.o   
> .libs/libclient_fuse.lax/libclient.a/Client.o 
> .libs/libclient_fuse.lax/libclient.a/ClientSnapRealm.o 
> .libs/libclient_fuse.lax/libclient.a/Dentry.o 
> .libs/libclient_fuse.lax/libclient.a/Filer.o 
> .libs/libclient_fuse.lax/libclient.a/Inode.o 
> .libs/libclient_fuse.lax/libclient.a/Journaler.o 
> .libs/libclient_fuse.lax/libclient.a/MetaRequest.o 
> .libs/libclient_fuse.lax/libclient.a/MetaSession.o 
> .libs/libclient_fuse.lax/libclient.a/ObjectCacher.o 
> .libs/libclient_fuse.lax/libclient.a/Objecter.o 
> .libs/libclient_fuse.lax/libclient.a/Striper.o 
> .libs/libclient_fuse.lax/libclient.a/Trace.o 
> ar: `u' modifier ignored since `D' is the default (see `U')
> libtool: link: /bin/grep -E -e "^ceph_.*" ".libs/libcephfs.exp" > 
> ".libs/libcephfs.expT"
> libtool: link: mv -f ".libs/libcephfs.expT" ".libs/libcephfs.exp"
> libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/6/crtbeginS.o  .libs/libcephfs.o  
> -Wl,--whole-archive ./.libs/libclient.a ./.libs/libcommon.a 
> -Wl,--no-whole-archive  /usr/lib/x86_64-linux-gnu/libatomic_ops.a 
> -Wl,--as-needed -ledit -lncurses -lbsd -ldl -lpthread -lnss3 -lnssutil3 
> -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 -luuid -lrt -lboost_thread 
> -lboost_system -L/usr/lib/gcc/x86_64-linux-gnu/6 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../.. -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/x86_64-linux-gnu/6/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crtn.o  -g -O2 
> -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname 
> -Wl,libcephfs.so.1 -Wl,-retain-symbols-file -Wl,.libs/libcephfs.exp -o 
> .libs/libcephfs.so.1.0.0
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ceph_0.80.11-1.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844800: alljoyn-core-1509: FTBFS: common/crypto/openssl/CryptoAES.cc:286:92: error: 'AES_ctr128_encrypt' was not declared in this scope

[Lucas Nussbaum]

Source: alljoyn-core-1509
Version: 15.09a-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> g++ -o build/linux/x86_64/release/obj/common/crypto/CryptoAES.o -c -std=c++11 
> -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
> -fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
> -fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
> -Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC -DNDEBUG -DROUTER 
> -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
> -Ibuild/linux/x86_64/release/dist/cpp/inc 
> -Ibuild/linux/x86_64/release/dist/c/inc 
> -Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
> -Icommon/crypto -Ibuild/linux/x86_64/release/dist/cpp/inc 
> common/crypto/openssl/CryptoAES.cc
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Encrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:286:92: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(T.data, U.data, 16, &keyState->key, ivec.data, 
> ecount_buf.data, &num);
>   
>   ^
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Decrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:339:104: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(U.data, T.data, sizeof(T.data), &keyState->key, 
> ivec.data, ecount_buf.data, &num);
>   
>   ^
> scons: *** [build/linux/x86_64/release/obj/common/crypto/CryptoAES.o] Error 1
> scons: building terminated because of errors.
> debian/rules:39: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/alljoyn-core-1509_15.09a-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844797: cabal-debian: FTBFS: build-dependency not installable: libghc-debian-doc

[Lucas Nussbaum]

Source: cabal-debian
Version: 4.33-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-ansi-wl-pprint-dev (<< 0.7), 
> libghc-ansi-wl-pprint-dev (>= 0.6), libghc-ansi-wl-pprint-prof, 
> libghc-bifunctors-dev, libghc-bifunctors-prof, libghc-data-default-dev, 
> libghc-data-default-prof, libghc-debian-dev (>= 3.91), libghc-debian-prof, 
> libghc-diff-dev (>= 0.3.1), libghc-diff-prof, libghc-exceptions-dev, 
> libghc-exceptions-prof, libghc-hsemail-dev, libghc-hsemail-prof, 
> libghc-hunit-dev, libghc-hunit-prof, libghc-lens-dev, libghc-lens-prof, 
> libghc-memoize-dev (>= 0.7), libghc-memoize-prof, libghc-mtl-dev, 
> libghc-mtl-prof, libghc-network-uri-dev, libghc-network-uri-prof, 
> libghc-newtype-generics-dev (>= 0.4), libghc-newtype-generics-prof, 
> libghc-optparse-applicative-dev (>= 0.11), libghc-optparse-applicative-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-puremd5-dev, 
> libghc-puremd5-prof, libghc-regex-tdfa-dev, libghc-regex-tdfa-prof, 
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof, 
> libghc-text-dev, libghc-text-prof, libghc-unixutils-dev (>= 1.53), 
> libghc-unixutils-prof, libghc-utf8-string-dev, libghc-utf8-string-prof, 
> ghc-doc, libghc-ansi-wl-pprint-doc, libghc-bifunctors-doc, 
> libghc-data-default-doc, libghc-debian-doc, libghc-diff-doc, 
> libghc-exceptions-doc, libghc-hsemail-doc, libghc-hunit-doc, libghc-lens-doc, 
> libghc-memoize-doc, libghc-mtl-doc, libghc-network-uri-doc, 
> libghc-newtype-generics-doc, libghc-optparse-applicative-doc, 
> libghc-parsec3-doc, libghc-puremd5-doc, libghc-regex-tdfa-doc, 
> libghc-set-extra-doc, libghc-syb-doc, libghc-text-doc, libghc-unixutils-doc, 
> libghc-utf8-string-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-ansi-wl-pprint-dev (<< 0.7), 
> libghc-ansi-wl-pprint-dev (>= 0.6), libghc-ansi-wl-pprint-prof, 
> libghc-bifunctors-dev, libghc-bifunctors-prof, libghc-data-default-dev, 
> libghc-data-default-prof, libghc-debian-dev (>= 3.91), libghc-debian-prof, 
> libghc-diff-dev (>= 0.3.1), libghc-diff-prof, libghc-exceptions-dev, 
> libghc-exceptions-prof, libghc-hsemail-dev, libghc-hsemail-prof, 
> libghc-hunit-dev, libghc-hunit-prof, libghc-lens-dev, libghc-lens-prof, 
> libghc-memoize-dev (>= 0.7), libghc-memoize-prof, libghc-mtl-dev, 
> libghc-mtl-prof, libghc-network-uri-dev, libghc-network-uri-prof, 
> libghc-newtype-generics-dev (>= 0.4), libghc-newtype-generics-prof, 
> libghc-optparse-applicative-dev (>= 0.11), libghc-optparse-applicative-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-puremd5-dev, 
> libghc-puremd5-prof, libghc-regex-tdfa-dev, libghc-regex-tdfa-prof, 
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof, 
> libghc-text-dev, libghc-text-prof, libghc-unixutils-dev (>= 1.53), 
> libghc-unixutils-prof, libghc-utf8-string-dev, libghc-utf8-string-prof, 
> ghc-doc, libghc-ansi-wl-pprint-doc, libghc-bifunctors-doc, 
> libghc-data-default-doc, libghc-debian-doc, libghc-diff-doc, 
> libghc-exceptions-doc, libghc-hsemail-doc, libghc-hunit-doc, libghc-lens-doc, 
> libghc-memoize-doc, libghc-mtl-doc, libghc-network-uri-doc, 
> libghc-newtype-generics-doc, libghc-optparse-applicative-doc, 
> libghc-parsec3-doc, libghc-puremd5-doc, libghc-regex-tdfa-doc, 
> libghc-set-extra-doc, libghc-syb-doc, libghc-text-doc, libghc-unixutils-doc, 
> libghc-utf8-string-doc
> dpkg-deb: building package 'sbuild-build-depends-cabal-debian-dummy' in 
> '/<>/resolver-Wl2fHm/apt_archive/sbuild-build-depends-cabal-debian-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-cabal-debian-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Wl2fHm/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Wl2fHm/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Wl2fHm/apt_archive ./ Release.gpg
> Get:4 copy:/<&

Bug#844820: shibboleth-sp2: FTBFS: unsatisfiable build-dependencies: libsaml2-dev (>= 2.5), libxmltooling-dev (>= 1.5)

[Lucas Nussbaum]

Source: shibboleth-sp2
Version: 2.6.0+dfsg1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: apache2-dev (>> 2.4.4), debhelper (>= 9), dh-apache2, 
> dh-autoreconf, dh-exec, libboost-dev, libfcgi-dev, libkrb5-dev, 
> liblog4shib-dev, libmemcached-dev (>= 1.0), libsaml2-dev (>= 2.5), 
> libsystemd-dev, libxerces-c-dev, libxml-security-c-dev (>= 1.7), 
> libxmltooling-dev (>= 1.5), opensaml2-schemas, pkg-config, unixodbc-dev, 
> xmltooling-schemas, doxygen, graphviz
> Filtered Build-Depends: apache2-dev (>> 2.4.4), debhelper (>= 9), dh-apache2, 
> dh-autoreconf, dh-exec, libboost-dev, libfcgi-dev, libkrb5-dev, 
> liblog4shib-dev, libmemcached-dev (>= 1.0), libsaml2-dev (>= 2.5), 
> libsystemd-dev, libxerces-c-dev, libxml-security-c-dev (>= 1.7), 
> libxmltooling-dev (>= 1.5), opensaml2-schemas, pkg-config, unixodbc-dev, 
> xmltooling-schemas, doxygen, graphviz
> dpkg-deb: building package 'sbuild-build-depends-shibboleth-sp2-dummy' in 
> '/<>/resolver-VqBxZO/apt_archive/sbuild-build-depends-shibboleth-sp2-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-shibboleth-sp2-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-VqBxZO/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-VqBxZO/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-VqBxZO/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-VqBxZO/apt_archive ./ Sources [533 B]
> Get:5 copy:/<>/resolver-VqBxZO/apt_archive ./ Packages [599 B]
> Fetched 2089 B in 0s (184 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install shibboleth-sp2 build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-shibboleth-sp2-dummy : Depends: libsaml2-dev (>= 2.5) 
> but it is not going to be installed
>  Depends: libxmltooling-dev (>= 
> 1.5) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/shibboleth-sp2_2.6.0+dfsg1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844812: dacs: FTBFS: build-dependency not installable: apache2-dev

[Lucas Nussbaum]

Source: dacs
Version: 1.4.38-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), apache2-dev, libssl-dev, 
> libexpat1-dev, chrpath, libsasl2-dev, libperl-dev, libldap2-dev, 
> autotools-dev, groff-base, xsltproc, docbook-xsl, libxmlsec1-dev, libpam0g-dev
> Filtered Build-Depends: debhelper (>= 9), apache2-dev, libssl-dev, 
> libexpat1-dev, chrpath, libsasl2-dev, libperl-dev, libldap2-dev, 
> autotools-dev, groff-base, xsltproc, docbook-xsl, libxmlsec1-dev, libpam0g-dev
> dpkg-deb: building package 'sbuild-build-depends-dacs-dummy' in 
> '/<>/resolver-NzANqk/apt_archive/sbuild-build-depends-dacs-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-dacs-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-NzANqk/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-NzANqk/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-NzANqk/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-NzANqk/apt_archive ./ Sources [423 B]
> Get:5 copy:/<>/resolver-NzANqk/apt_archive ./ Packages [512 B]
> Fetched 1892 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install dacs build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-dacs-dummy : Depends: apache2-dev but it is not going 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/dacs_1.4.38-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844821: libapache2-mod-auth-gssapi: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-gssapi
Version: 1.4.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: apache2-dev (>= 2.4), debhelper (>= 9), dh-apache2, 
> dh-autoreconf, gss-ntlmssp-dev, libapr1-dev, libkrb5-dev, libssl-dev, 
> pkg-config
> Filtered Build-Depends: apache2-dev (>= 2.4), debhelper (>= 9), dh-apache2, 
> dh-autoreconf, gss-ntlmssp-dev, libapr1-dev, libkrb5-dev, libssl-dev, 
> pkg-config
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-gssapi-dummy' in 
> '/<>/resolver-txxqMc/apt_archive/sbuild-build-depends-libapache2-mod-auth-gssapi-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-gssapi-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-txxqMc/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-txxqMc/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-txxqMc/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-txxqMc/apt_archive ./ Sources [413 B]
> Get:5 copy:/<>/resolver-txxqMc/apt_archive ./ Packages [502 B]
> Fetched 1872 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-auth-gssapi build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libapache2-mod-auth-gssapi-dummy : Depends: libssl-dev 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libapache2-mod-auth-gssapi_1.4.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#844818: networking-mlnx: FTBFS: build-dependency not installable: python-neutron (>= 2:9.0.0~rc1)

[Lucas Nussbaum]

Source: networking-mlnx
Version: 1:9.0.0~b1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 52~), po-debconf, python-all, python-pbr (>= 0.11), 
> python-sphinx, python-babel, python-cliff (>= 1.15.0), python-coverage, 
> python-ddt (>= 1.0.1), python-ethtool, python-fixtures (>= 1.3.1), 
> python-hacking, python-lxml, python-mock (>= 1.3), python-neutron (>= 
> 2:9.0.0~rc1), python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.5.1), 
> python-os-testr (>= 0.4.1), python-psycopg2, python-pymysql, 
> python-requests-mock (>= 0.7.0), python-tempest-lib (>= 0.13.0), 
> python-testresources, python-testscenarios, python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), python-zmq, subunit (>= 0.0.18), testrepository (>= 
> 0.0.18)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 52~), po-debconf, python-all, python-pbr (>= 0.11), 
> python-sphinx, python-babel, python-cliff (>= 1.15.0), python-coverage, 
> python-ddt (>= 1.0.1), python-ethtool, python-fixtures (>= 1.3.1), 
> python-hacking, python-lxml, python-mock (>= 1.3), python-neutron (>= 
> 2:9.0.0~rc1), python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.5.1), 
> python-os-testr (>= 0.4.1), python-psycopg2, python-pymysql, 
> python-requests-mock (>= 0.7.0), python-tempest-lib (>= 0.13.0), 
> python-testresources, python-testscenarios, python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), python-zmq, subunit (>= 0.0.18), testrepository (>= 
> 0.0.18)
> dpkg-deb: building package 'sbuild-build-depends-networking-mlnx-dummy' in 
> '/<>/resolver-mNH6jQ/apt_archive/sbuild-build-depends-networking-mlnx-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-networking-mlnx-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-mNH6jQ/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-mNH6jQ/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-mNH6jQ/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-mNH6jQ/apt_archive ./ Sources [620 B]
> Get:5 copy:/<>/resolver-mNH6jQ/apt_archive ./ Packages [703 B]
> Fetched 2286 B in 0s (210 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install networking-mlnx build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-networking-mlnx-dummy : Depends: python-neutron (>= 
> 2:9.0.0~rc1) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/networking-mlnx_9.0.0~b1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.