Bug#705524: Request for confirmation

[Rolf Leggewie]

Jack,

can you please confirm that removing the scim-anthy package resolves the 
problem for you as well?  Once we have a solid understanding of the root 
cause of the problem instead of the bashing and frantic, baseless 
hand-waving that some people prefer we can think about what will be the 
best course of action to fix what looks like a version incompatibility 
between oldstable and stable.  Thank you.


Regards

Rolf


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#707051: updated version information

[Ronny Wegener]

Version: 1.0.5

Bug#712283: qcontrol: add support for i386/amd64 based devices like the QNAP TS-569 Pro

[Ian Campbell]

Control: forcemerge -1 712191

On Fri, 2013-06-14 at 23:44 +0200, Christoph Anton Mitterer wrote:
> As discussed previously, support for i386/amd basd devices (I have the QNAP 
> TS-569 Pro)
> would be nice.

Why are you filing this as a new bug? You can follow up to an existing
bug by writing to nn...@bugs.debian.org. I have merged the previous bug
with this one.

> It seems that many of the newer QNAPs have Atom CPUs, especially all of the 
> more
> professional ones, so I guess this is crucial for qcontrol.
> 
> 
> I compiled qcontrol on amd64 (which works),... but then not much happens.
> The init-script won't work already, as there is no "Hardware" in 
> /proc/cpuinfo at all
> (using Debian sid).

Is there any way (via /proc or /sys) to distinguish the different x86
QNAP platforms?

> Staring the daemon manually (qcontrol -d) leads also to nothing (but $?=0) 
> the same
> for -f.
> Any ideas?

Which qcontrol.conf did you use? You will need one for your platform.
You may also need to author a supporting C module for your platform
(which is the loaded by qcontrol.conf).

See ts219.c and friends (ts41x.c etc) for existing examples of the
supporting C modules. There is a lot of redundancy in these modules,
which I intend to look at one day.

> There doesn't seem to be that gpio_keys module, or any such device in 
> /dev/input.

This is a platform specific driver on ARM. I'm not sure it is so common
to use gpio in this way on x86 platforms so it is possible that the
buttons etc are exposed differently. If they were using GPIO for it then
you would need to write a suitable platform specific driver.

You'll probably need to examine the stock firmware to see how this works
on your x86 platform. Or you could try asking qnap via their forums.

> Some further notes:
> I was already able to manually set the LCD display (A125), and the UART 
> command strings
> used there seem to be the same as they're used in the a125.c of qcontrol.
> 
> But I have no idea on how to get the LEDs, buttons, etc. pp. running any 
> ideas?

LEDs on the ARM platforms are controlled by the PIC. Do you know if the
x86 versions have the same one or even if they have one at all? You may
need to look into the qnap kernel drivers to figure it out.

Buttons relates to the gpio_keys question above.

It sounds like the LCD could work if you just wrote a qcontrol.conf
which loaded that module and didn't fumble over the other two things.

> One further note... the fan seems to be controllable through plain the 
> fancontrol package,
> and it seems to support much more steps than just the 4 or 5 that we know 
> from qcontrol.
> So maybe it's a good idea to put responsibility on fan control into 
> fancontrol.

Being an x86 platform I expect it uses the usual x86 mechanisms for
fancontrol and not the custom PIC used on ARM. If fancontrol works then
I suggest you use fancontrol.

> I'm happy to do any testing,... but don't quite know where to start.

I'm afraid this is probably going to involve more than testing on your
part. Likely it will involve some investigation of the stock firmware
(and some simple reverse engineering) and a bit of coding. I can try and
offer general advice but I don't have any knowledge about the x86
versions of qnap's hardware (nor am I particularly motivated to find out
about them). You might find it useful to try and get in contact with
QNAP to see if they can describe e.g. how the buttons are wired up on
x86.

Ian.


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

Bug#712285: llvm-toolchain-3.3: FTBFS: lldb not fully ported everywhere

[Sylvestre Ledru]

Hello,

On 15/06/2013 00:29, Aaron M. Ucko wrote:
> Source: llvm-toolchain-3.3
> Version: 1:3.3-1
> Severity: serious
> Justification: fails to build from source
> 
> Builds of llvm-toolchain-3.3 have failed for several architectures
> because lldb doesn't compile there; you can find the logs at
> https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-3.3&ver=1%3A3.3-1.
> 
> Could you please take a look?
Yes, it is an on going task (with the help of Luca, thanks again btw)

Cheers,
Sylvestre


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#708660: [LCFC] templates://keystone/{keystone.templates}

[Christian PERRIER]

Quoting Thomas Goirand (z...@debian.org):

> I think that someone who doesn't know what a tenant is in OpenStack
> should either give-up using it or read some more documentation. So I'd
> be fine with simply removing "(project)".


Still...:-)

I'm thinking about translators who need information in order to choose
the right thing to do.

I propose the following:


Template: keystone/create-admin-tenant
Type: boolean
Default: false
# Translators: a "tenant" in OpenStack world is
# an entity that contains one or more username/password couples. 
# It's typically the tenant that will be used for billing. Having more than one
# username/password is very helpful in larger organization.
# You're advised to either keep "tenant" without translating it
# or keep it aside with your translation. Example for French:
# propriétaire ("tenant")
_Description: Register administration tenants?
 For OpenStack to work, you need a basic tenant configuration. The
 creation of these administration tenants can be done automatically.



signature.asc
Description: Digital signature

Bug#712296: 5.1: only sound from front right speaker with VT1720/24 [Envy24PT/HT]

[Xavier Langevin]

Package: installation-reports
Severity: normal
Tags: upstream

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
standard install

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

$ lshw
-multimedia
description: Multimedia audio controller
produit: VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio
Controller
fabriquant: VIA Technologies Inc.
identifiant matériel: 2
information bus: pci@:04:02.0
version: 01
bits: 32 bits
horloge: 33MHz
fonctionnalités: pm bus_master cap_list
configuration: driver=snd_ice1724 latency=64
ressources: irq:18 portE/S:dc60(taille=32)
portE/S:dc80(taille=128)



$ lspci -vvv
04:02.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24
[Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)
Subsystem: VIA Technologies Inc. Device 2403
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- 

Machine: Dell Optiplex 760
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20130430"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux bob 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM 
Controller [8086:2e10] (rev 03)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI 
Express Root Port [8086:2e11] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4 
Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation 4 Series 
Chipset Integrated Graphics Controller [8086:2e13] (rev 03)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation 4 Series 
Chipset HECI Controller [8086:2e14] (rev 03)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: 00:03.2 IDE interface [0101]: Intel Corporation 4 Series Chipset PT 
IDER Controller [8086:2e16] (rev 03)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: ata_generic
lspci -knn: 00:03.3 Serial controller [0700]: Intel Corporation 4 Series 
Chipset Serial KT Controller [8086:2e17] (rev 03)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM-3 
Gigabit Network Connection [8086:10de] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #4 [8086:3a67] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #5 [8086:3a68] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #6 [8086:3a69] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:027f]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB2 EHCI Controller #2 [8086:3a6c] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:027

Bug#708660: [Openstack-devel] Bug#708660: [LCFC] templates://keystone/{keystone.templates}

[Thomas Goirand]

On 06/15/2013 05:25 AM, Justin B Rye wrote:
> Thomas Goirand wrote:
>> In OpenStack, a tenant is a synonym of a project. I don't think it was a
>> rename, I saw both. For example, the OpenStack dashboard (Horizon) shows
>> "projects" and not "tenants" in the admin interface:
>> http://www.openstack.org/themes/openstack/images/essex/project-users.jpg
>>
>> Or this one too:
>> http://docs.openstack.org/trunk/openstack-compute/admin/content/figures/1/figures/horizon-screenshot.jpg
>>
>> I'm cc-ing the OpenStack list just in case I'm wrong. :)
> 
> I was going by phrases like:
> 
> # Note: Earlier versions of OpenStack used the term "project" instead
> # of "tenant". Because of this legacy terminology, some command-line
> # tools use --project_id when a tenant ID is expected. 
>   
> (http://docs.openstack.org/trunk/openstack-compute/admin/content/users-and-projects.html)
> 
> but if it isn't obviously a good idea then we should probably avoid
> complicating things with alternative names.
> 
> (I'm a bit baffled by this choice of term, though.  Why would a
> "resource container" occupied by users, keys, etc. be called a
> "tenant"?  It seems backwards; wouldn't it make more sense if the
> individual resources doing the occupying were thought of as "tenants"
> and the container was called a "leasehold" or "domicile" or whatever?
> I hope the person who coined the term wasn't confusing "tenants" with
> "tenements" or "tenure" or something...)

Thanks for pointing to the right documentation Justin. I really didn't
expect you would teach me something about OpenStack! :)

So indeed, we probably should write "(previously known as project)" or
something similar.

Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#707843: gbirthday: recommends python-evolution which is no longer built

[foss]

On Friday, 14 June, 2013 03:26 PM, Emilio Pozuelo Monfort wrote:

On 14/06/13 09:22, Emilio Pozuelo Monfort wrote:

ISTR recommending a package not in the archive was a bug, but I can't find a
reference. So if you would like to keep this that's fine with me as it won't
prevent migration of your package. Though perhaps you may want to downgrade it
to a suggest. I leave that decision to you.

Found the reference now, see

http://www.debian.org/doc/debian-policy/ch-archive.html#s-main

"must not require or recommend a package outside of main".

You could downgrade it to a suggests though.



Hello Emilio,

thank you very much for adding that information.  I am certainly not 
trying to keep that Recommends line around forever even though the 
package is gone.  My intention is to fully understand what you and 
Jeremy are trying to fix and to make sure it is fixed in the right way.  
In particular I was tripped by the suggested change not being to simply 
drop the recommends line but making changes to the build where the added 
patch 03_disable_evo_database.patch claims in the subject that the 
evolution backend no longer works.  All I can say is that the last time 
I tried it (admittedly on Ubuntu precise) it was working just fine 
IIRC.  This might no longer be the case with the latest Debian and 
Ubuntu releases which I only run in virtual containers on an as-needed 
basis.


As far as the quoted policy is concerned, I believe that mostly concerns 
the DFSG.  A package in main should not recommend a package in non-free, 
for example.  Besides, python-evolution IS in main, just simply not in 
unstable.  So, it is my understanding that the gbirthday package in its 
current form does not violate the policy.


Thank you again for the discussion.

Regards

Rolf


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712298: RFS: amanda/1:3.3.3-3 [ITA]

[Bill Blough]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: amanda
   Version : 1:3.3.3-3
   Upstream Author : Amanda Development Team 
 * URL : http://www.amanda.org
 * License : GPL and University of Maryland License
   Section : utils

  It builds those binary packages:

 amanda-client - Advanced Maryland Automatic Network Disk Archiver (Client)
 amanda-common - Advanced Maryland Automatic Network Disk Archiver (Libs)
 amanda-server - Advanced Maryland Automatic Network Disk Archiver (Server)

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

  http://mentors.debian.net/package/amanda


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

dget -x 
http://mentors.debian.net/debian/pool/main/a/amanda/amanda_3.3.3-3.dsc

  More information about amanda can be obtained from http://www.amanda.org.

  Changes since the last upload:

Updated maintainer info [ITA] Bug #700484
Updated policy compliance to 3.9.4
Several changes to fix the broken amserverconfig utility.  Bug #551564

  Regards,
   Bill Blough


signature.asc
Description: Digital signature

Bug#711997: hugin: Hugin fails with segfault; program partially unusable

[Andreas Metzler]

On 2013-06-14 Charlie Hagedorn  wrote:
> mesa-utils was not installed. After installing it (didn't pull in any other
> packages), I get:

> [:~]$ glxgears -info
> Xlib:  extension "GLX" missing on display ":0.0".
> Error: couldn't get an RGB, Double-buffered visual
> [:~]$

And at this point it simply exits?

Do you have libgl1-mesa-dri or libgl1-mesa-swx11 installed?

[...]
> Providing a backtrace is new to me, but if I run hugin with gdb, this is
> what I get, following these instructions
> http://wiki.debian.org/HowToGetABacktrace :

> [:~]$ gdb hugin
[...]
> Reading symbols from /usr/bin/hugin...(no debugging symbols found)...done.

I have rebuilt hugin with debugging symbols and have uploaded the
binaries to .

[...]
> Program received signal SIGSEGV, Segmentation fault.
> 0x005b9183 in PreviewIdentifyTool::setConstantOn(bool) ()
[...]

Could enter bt at this point?

cu Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#708658: [BTS#708658] templates://cinder/{cinder-common.templates,cinder-api.templates} : Final update for English review

[Christian PERRIER]

Dear Debian maintainer,

On Tuesday, May 21, 2013, I notified you of the beginning of a review process
concerning debconf templates for cinder.

The debian-l10n-english contributors have now reviewed these templates,
and the final proposed changes are attached to this update to the
original bug report.

Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.

However, please try to avoid uploading cinder with these changes
right now.

The second phase of this process will begin on Tuesday, June 18, 2013, when I 
will
coordinate updates to translations of debconf templates.

The existing translators will be notified of the changes: they will
receive an updated PO file for their language.

Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.

Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.

The call for translation updates and new translations will run until
about Tuesday, July 09, 2013. Please avoid uploading a package with fixed or 
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.

Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.

Around Wednesday, July 10, 2013, I will contact you again and will send a final 
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).

Again, thanks for your attention and cooperation.


-- 


# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.

Template: cinder/start_services
Type: boolean
Default: true
_Description: Start Cinder services at boot?
 Please choose whether you want to start Cinder services when the
 machine is booted up.

Template: cinder/configure_db
Type: boolean
Default: false
_Description: Set up a database for Cinder?
 No database has been set up for Cinder to use. Before
 continuing, you should make sure you have the following information:
 .
  * the type of database that you want to use;
  * the database server hostname (that server must allow TCP connections from 
this
machine);
  * a username and password to access the database.
 .
 If some of these requirements are missing, do not choose this option and run 
with
 regular SQLite support.
 .
 You can change this setting later on by running "dpkg-reconfigure -plow
 cinder".

Template: cinder/auth-host
Type: string
Default: 127.0.0.1
_Description: Authentication server hostname:
 Please specify the hostname of the authentication server. Typically
 this is also the hostname of the OpenStack Identity Service (Keystone).

Template: cinder/admin-tenant-name
Type: string
Default: admin
# Translators: a "tenant" in OpenStack world is
# an entity that contains one or more username/password couples. 
# It's typically the tenant that will be used for billing. Having more than one
# username/password is very helpful in larger organization.
# You're advised to either keep "tenant" without translating it
# or keep it aside with your translation. Example for French:
# propriétaire ("tenant")
_Description: Authentication server tenant name:
 Please specify the authentication server tenant name.

Template: cinder/admin-user
Type: string
Default: admin
_Description: Authentication server username:
 Please specify the username to use with the authentication server.

Template: cinder/admin-password
Type: password
_Description: Authentication server password:
 Please specify the password to use with the authentication server.

Template: cinder/volume_group
Type: string
_Description: Cinder volume group:
 Please specify the name of the LVM volume group on which Cinder
 will create partitions.
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.

Template: cinder/register-endpoint
Type: boolean
Default: false
_Description: Register Cinder in the Keystone endpoint catalog?
 Each OpenStack service (each API) should be registered in order to be
 accessible. This is done using "keystone service-create" and "keystone
 endpoint-create". This can be done automatically now.
 .
 Note that you will need to have an up and running Keystone server on which to
 connect using the Keystone authentication token.

Template: c

Bug#712297: texlive-latex-base: babel.sty adaption from thailatex is not undone

[Norbert Preining]

Package: texlive-latex-base
Version: 2013.20130530-1
Severity: serious

babel.sty in /var/lib/texmf/tex/generic/babel/babel.sty was created
by thailatex and must be removed ...


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712300: FTBFS: tests require internet connectivity

[Felix Geyer]

Source: libgit2
Version: 0.18.0-1
Severity: serious
Justification: fails to build from source

This package requires internet connectivity for its test suite
to pass. Package builds must not not rely on external network
connectivity, but should be self-contained.

The test tries to resolve github.com:

  1) Failure:
online::clone::network_full 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:41]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error

  2) Failure:
online::clone::network_bare 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:54]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error

  3) Failure:
online::clone::empty_repository 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:65]
  Function call failed: git_clone(&g_repo, LIVE_EMPTYREPO_URL, "./foo", 
&g_options)
  error -1 - Failed to resolve address for github.com: System error

  4) Failure:
online::clone::can_checkout_a_cloned_repo 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:105]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error

  5) Failure:
online::clone::custom_remote_callbacks 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:138]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error

  6) Failure:
online::clone::bitbucket_style 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:170]
  Function call failed: git_clone(&g_repo, BB_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for bitbucket.org: System error

  7) Failure:
online::clone::can_cancel 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/clone.c:199]
  GIT_EUSER != git_clone(&g_repo, 
"http://github.com/libgit2/TestGitRepository";, "./foo", &g_options)
  -7 != -1

  8) Failure:
online::fetch::default_git 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:47]
  Function call failed: git_remote_connect(remote, GIT_DIRECTION_FETCH)
  error -1 - Failed to resolve address for github.com: System error

  9) Failure:
online::fetch::default_http 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:47]
  Function call failed: git_remote_connect(remote, GIT_DIRECTION_FETCH)
  error -1 - Failed to resolve address for github.com: System error

  10) Failure:
online::fetch::no_tags_git 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:47]
  Function call failed: git_remote_connect(remote, GIT_DIRECTION_FETCH)
  error -1 - Failed to resolve address for github.com: System error

  11) Failure:
online::fetch::no_tags_http 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:47]
  Function call failed: git_remote_connect(remote, GIT_DIRECTION_FETCH)
  error -1 - Failed to resolve address for github.com: System error

  12) Failure:
online::fetch::doesnt_retrieve_a_pack_when_the_repository_is_up_to_date 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:95]
  Function call failed: git_clone(&_repository, 
"https://github.com/libgit2/TestGitRepository.git";, "./fetch/lg2", &opts)
  error -1 - Failed to resolve address for github.com: System error

  13) Failure:
online::fetch::can_cancel 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:132]
  Function call failed: git_remote_connect(remote, GIT_DIRECTION_FETCH)
  error -1 - Failed to resolve address for github.com: System error

  14) Failure:
online::fetch::ls_disconnected 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetch.c:155]
  Function call failed: git_remote_connect(remote, GIT_DIRECTION_FETCH)
  error -1 - Failed to resolve address for github.com: System error

  15) Failure:
online::fetchhead::wildcard_spec 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetchhead.c:33]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error

  16) Failure:
online::fetchhead::explicit_spec 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetchhead.c:33]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error

  17) Failure:
online::fetchhead::no_merges 
[/tmp/buildd/libgit2-0.18.0/tests-clar/online/fetchhead.c:33]
  Function call failed: git_clone(&g_repo, LIVE_REPO_URL, "./foo", &g_options)
  error -1 - Failed to resolve address for github.com: System error



0% tests passed, 1 tests failed out of 1

Total Test time (real) =   5.32 sec

The following tests FAILED:
  1 - libgit2_clar (Failed)
Errors while running CTest
make[1]: *** [test] Error 8


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712251: ca-certificates: Ackward package description

[Thijs Kinkhorst]

On Fri, June 14, 2013 16:46, Martin Geisler wrote:
> Package: ca-certificates
> Version: 20130119
> Severity: wishlist
>
> I feel this part of the package description is ackward:
>
>   Please note that Debian can neither confirm nor deny whether the
>   certificate authorities whose certificates are included in this
>   package have in any way been audited[...]
>
> I think the "can neither confirm nor deny" part should read "cannot
> promise" or "cannot guarantee" or similar.
>
> The point is that Debian doesn't know if the CAs have been audited,
> not that Debian refuses to comment on the subject.

Does it? Debian *could* know if it would spend lots of time to investigate
each certificate. Debian chooses not to spend that time. Or am I mistaken?


Cheers,
Thijs


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712301: FTBFS: tests require internet connectivity

[Felix Geyer]

Source: node-oauth
Version: 0.9.8-1
Severity: serious
Justification: fails to build from source

This package requires internet connectivity for its test suite
to pass. Package builds must not not rely on external network
connectivity, but should be self-contained.

Build log:

[...]
  When performing a secure Request With a Callback And A 302 redirect is 
received and there is a location header
✓ it should (re)perform the secure request but with the new location
  When performing a secure Request With a Callback And A 302 redirect is 
received but there is no location header
✓ it should execute the callback, passing the HTTP Response code
  
  ♢ OAuth2 
  

events.js:48
throw arguments[1]; // Unhandled 'error' event
   ^
Error: getaddrinfo EADDRINFO
at errnoException (dns.js:31:11)
at Object.onanswer [as oncomplete] (dns.js:140:16)
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory `/tmp/buildd/node-oauth-0.9.8'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712232: LIVE_NOCONFIGS in /etc/live/config/* broken

[tails]

Hi,

> i think that has been fixed in 4.0~a21-1, can you check?

Unfortunately, we can't easily check since the 4.0 series dropped
support for Squeeze.

Any bugfix commit we could try backporting to 3.0.23 and see if it
fixes things up? Would that be b018878 ("Reading configuration files
before cmdline options."), perhaps?


-- 


pgpigyRDom8Eq.pgp
Description: PGP signature

Bug#712302: FTBFS: missing build-dependency on python-setuptools

[Felix Geyer]

Source: python-django-treebeard
Version: 2.0~beta1-1
Severity: serious
Justification: fails to build from source

python-django-treebeard fails to build from source in a minimal
build environment because it is missing a build-dependency on
python-setuptools.

Build log:

dpkg-buildpackage: source package python-django-treebeard
dpkg-buildpackage: source version 2.0~beta1-1
dpkg-buildpackage: source changed by Chris Lamb 
 dpkg-source --before-build python-django-treebeard-2.0~beta1
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory `/tmp/buildd/python-django-treebeard-2.0~beta1'
dh_auto_clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
Traceback (most recent call last):
  File "setup.py", line 4, in 
from setuptools import setup
ImportError: No module named setuptools
dh_auto_clean: python setup.py clean -a returned exit code 1
make[1]: *** [override_dh_auto_clean] Error 1
make[1]: Leaving directory `/tmp/buildd/python-django-treebeard-2.0~beta1'
make: *** [clean] Error 2


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712303: Wishlist: Please update to a newer version - it has (hopefully!) many usability fixes.

[Matt Nottingham]

Package: kicad
Version: 0.20120526+bzr3261-1
Severity: wishlist


Err, not much else to add!



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

Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kicad depends on:
ii  kicad-common  0.20120526+bzr3261-1
ii  libc6 2.13-38
ii  libgcc1   1:4.7.2-5
ii  libgl1-mesa-glx [libgl1]  8.0.5-4
ii  libglu1-mesa [libglu1]8.0.5-4
ii  libstdc++64.7.2-5
ii  libwxbase2.8-02.8.12.1-12
ii  libwxgtk2.8-0 2.8.12.1-12
ii  libx11-6  2:1.5.0-1
ii  libxext6  2:1.3.1-2
ii  zlib-bin  1:1.2.7.dfsg-13

kicad recommends no packages.

Versions of packages kicad suggests:
ii  extra-xdg-menus  1.0-4
ii  kicad-doc-en 0.20120526+bzr3261-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712232: LIVE_NOCONFIGS in /etc/live/config/* broken

[Daniel Baumann]

[ please do not drop the bts from cc ]

On 06/15/2013 10:22 AM, ta...@boum.org wrote:
> 
> Hi,
> 
>> i think that has been fixed in 4.0~a21-1, can you check?
> 
> Unfortunately, we can't easily check since the 4.0 series dropped 
> support for Squeeze.
> 
> Any bugfix commit we could try backporting to 3.0.23 and see if it 
> fixes things up? Would that be b018878 ("Reading configuration
> files before cmdline options."), perhaps?

yes; and note that the command line will overwrite the config file, so
you should have nothing else (wrt/ live) but 'boot=live' in your cmdline.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712304: glx-diversions: broken symlinks with libgl1-mesa-glx 9.1.3-6

[Sven Joachim]

Package: glx-diversions
Version: 0.3.0
Severity: serious

In Mesa 9.1 the libGL installation has changed, especially libGL.so.1 no
longer points to libGL.so.1.2 but rather libGL.so.1.2.0:

,
| $ ls -l /usr/lib/i386-linux-gnu/libGL.so*
| lrwxrwxrwx 1 root root 14 Jun  7 21:37 /usr/lib/i386-linux-gnu/libGL.so 
-> libGL.so.1.2.0
| lrwxrwxrwx 1 root root 14 Jun  7 21:37 /usr/lib/i386-linux-gnu/libGL.so.1 
-> libGL.so.1.2.0
| -rw-r--r-- 1 root root 354876 Jun  7 21:37 
/usr/lib/i386-linux-gnu/libGL.so.1.2.0
`

Installing glx-diversions in this situation leads to broken symlinks
(see Package-specific info below), and the glx-alternative-mesa package
silently fails to set up any alternatives, AFAICS.

Even after purging the glx-diversions package, broken symlinks remain:

,
| # aptitude purge --purge-unused glx-alternative-mesa
| The following packages will be REMOVED:
|   glx-alternative-mesa{p} glx-diversions{pu} nvidia-installer-cleanup{pu} 
| 0 packages upgraded, 0 newly installed, 3 to remove and 9 not upgraded.
| Need to get 0 B of archives. After unpacking 227 kB will be freed.
| Do you want to continue? [Y/n/?] 
| (Reading database ... 200494 files and directories currently installed.)
| Removing glx-alternative-mesa ...
| Removing glx-diversions ...
| Removing 'diversion of /usr/lib/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions'
| Removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions'
| Removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions'
| Removing 'diversion of /usr/lib/libGL.so.1.2 to 
/usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions'
| Removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions'
| Removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions'
| Removing 'diversion of /usr/lib/libGL.so.1 to 
/usr/lib/mesa-diverted/libGL.so.1 by glx-diversions'
| Removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions'
| Removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions'
| Removing 'diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so 
by glx-diversions'
| Removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions'
| Removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions'
| Purging configuration files for glx-diversions ...
| Removing nvidia-installer-cleanup ...
| Purging configuration files for nvidia-installer-cleanup ...
| 
| # ls -l /usr/lib/i386-linux-gnu/libGL.so*
| lrwxrwxrwx 1 root root 10 Jun 15 10:27 /usr/lib/i386-linux-gnu/libGL.so 
-> libGL.so.1
| lrwxrwxrwx 1 root root 12 Jun 15 10:27 /usr/lib/i386-linux-gnu/libGL.so.1 
-> libGL.so.1.2
| -rw-r--r-- 1 root root 354876 Jun  7 21:37 
/usr/lib/i386-linux-gnu/libGL.so.1.2.0
`

I had to reinstall libgl1-mesa-glx (and libgl1-mesa-dev for the libGL.so
symlink) to fix that.


-- Package-specific info:
Diversions:
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions

/usr/lib/mesa-diverted:
total 124
drwxr-xr-x   4 root root   4096 Jun 15 10:35 .
drwxr-xr-x 149 root root 110592 Jun 15 10:35 ..
drwxr-xr-x   2 root root   4096 Jun 15 10:35 i386-linux-gnu
drwxr-xr-x   

Bug#712305: RM: eventstat [kfreebsd-amd64,kfreebsd-i386] -- RoM; ANAIS

[Ansgar Burchardt]

Package: ftp.debian.org

Kamal Mostafa  writes:
> Package 'eventstat' is stuck and won't migrate to testing, apparently
> due to old kfreebsd binary packages from eventstat (0.01.18-1):
>
> http://packages.qa.debian.org/e/eventstat.html
>
> In version 0.01.19-1, the author realized that this package wasn't
> functional or appropriate for non-linux, so we switched from "any" to
> "Architecture: linux-any".  I think the kfreebsd binary packages just
> need to be removed.  Please do so.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712306: libp11-kit0: if gnome-keyring is not installed p11-kit complains on stderr

[Vaibhav Niku]

Package: libp11-kit0
Version: 0.12-3
Severity: minor

Hello

If I try using mpop (with SSL) to download mail, the terminal is clobbered the
error:

---
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-
pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot
open shared object file: No such file or directory
---

p11-kit obviously couldn't load the module: none of the gnome-keyring files is
installed on my system. If p11 doesn't find the module, shouldn't it let it
pass silently? (It should inform about the missing module only when --debug,
--verbose or some such option is used.)

Note that I know I can pass the stderr to /dev/null.


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

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

Versions of packages libp11-kit0 depends on:
ii  libc6  2.13-38
ii  multiarch-support  2.13-38

libp11-kit0 recommends no packages.

libp11-kit0 suggests no packages.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712307: dokuwiki: Postrm fails if lighttpd is installed but not configured

[Jean-Philippe Guérard]

Package: dokuwiki
Severity: normal

Dear Maintainer,

I installed the dokuwiki package, then removed it.

During installation, I choose not to configure lighttpd, but
lighttpd was installed on my system.

The postrm did a:

  lighty-disable-mod dokuwiki

This cammand failed with the following error:

  Ignoring unknown module: dokuwiki

Making the postrm process fail.


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dokuwiki depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  javascript-common  7
ii  libjs-jquery   1.7.2+dfsg-1
ii  libjs-jquery-cookie6-1
ii  libjs-jquery-ui1.8.ooops.21+dfsg-2
ii  libphp-simplepie   1.2.1-3
ii  php-geshi  1.0.8.4-2
ii  php5   5.4.4-14
ii  ucf3.0025+nmu3

Versions of packages dokuwiki recommends:
ii  php5-cli  5.4.4-14
ii  php5-gd   5.4.4-14

Versions of packages dokuwiki suggests:
pn  libapache2-mod-xsendfile  


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#707843: gbirthday: recommends python-evolution which is no longer built

[Emilio Pozuelo Monfort]

Hi,

On 15/06/13 09:30, f...@rolf.leggewie.biz wrote:
> On Friday, 14 June, 2013 03:26 PM, Emilio Pozuelo Monfort wrote:
>> On 14/06/13 09:22, Emilio Pozuelo Monfort wrote:
>>> ISTR recommending a package not in the archive was a bug, but I can't find a
>>> reference. So if you would like to keep this that's fine with me as it won't
>>> prevent migration of your package. Though perhaps you may want to downgrade 
>>> it
>>> to a suggest. I leave that decision to you.
>> Found the reference now, see
>>
>> http://www.debian.org/doc/debian-policy/ch-archive.html#s-main
>>
>> "must not require or recommend a package outside of main".
>>
>> You could downgrade it to a suggests though.
> 
> 
> Hello Emilio,
> 
> thank you very much for adding that information.  I am certainly not trying to
> keep that Recommends line around forever even though the package is gone.  My
> intention is to fully understand what you and Jeremy are trying to fix and to
> make sure it is fixed in the right way.  In particular I was tripped by the
> suggested change not being to simply drop the recommends line but making 
> changes
> to the build where the added patch 03_disable_evo_database.patch claims in the
> subject that the evolution backend no longer works.  All I can say is that the
> last time I tried it (admittedly on Ubuntu precise) it was working just fine
> IIRC.  This might no longer be the case with the latest Debian and Ubuntu
> releases which I only run in virtual containers on an as-needed basis.

I don't know what Jeremy did, but I never suggested to touch the build system or
anything similar. From my initial report:

"Your package recommends python-evolution, which is gone. Please remove that
recommendation from your package."

The only problem is with the recommendation. You can drop it or demote it to a
suggests and everything will be fine then.

> As far as the quoted policy is concerned, I believe that mostly concerns the
> DFSG.  A package in main should not recommend a package in non-free, for
> example.  Besides, python-evolution IS in main, just simply not in unstable. 
> So, it is my understanding that the gbirthday package in its current form does
> not violate the policy.

It is about that, but more importantly it is about having a self-contained
suite. E.g. if a package in unstable depends on something that is not in
unstable, then it *can't* be installed and violates Policy per the above.
Similarly if a package in unstable recommends something that is not in unstable,
it violates Policy as well. I think it is very clear.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#705524: similar bug 708269 and 705524

[Rolf Leggewie]

I am starting to get the feeling that tickets 708269 and 705524 have a 
similar root cause, namely multi-arch incompatibilities between 
different binary packages in the scim eco system.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712294: Error in the program glines

[Emilio Pozuelo Monfort]

Hi,

On 15/06/13 06:16, Eduardo Ono wrote:
> Package: glines
> 
> Version: 3.4.2-3
> 
> ii  glines   1:3.4.2-3
> i386 make color lines of five or more length

Please next time use reportbug, it will tell us that and more information that
we need.

> In menu games when i touch "FIVE or more", it doesn't execute.
> 
> In received in /var/log/messages:
> 
> glines[4911]: segfault at 17 ip b6e6f07a sp bfff7480 error 4 in
> libcairo.so.2.11200.14[b6e1e000+117000]

So glines is segfaulting. Install libcairo2-dbg libglib2.0-0-dbg libgtk-3-0-dbg
libpango1.0-0-dbg and then get a backtrace, see

http://wiki.debian.org/HowToGetABacktrace

if you need instructions.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712262: [pkg-db-devel] Bug#712262: libdb_sql-5.3 doesn't link with needed libraries

[Ondřej Surý]

On Fri, Jun 14, 2013 at 11:24 PM, Iain Lane wrote:

> On Fri, Jun 14, 2013 at 09:04:24PM +0200, Ondřej Surý wrote:
> > Iain,
> >
> > thanks for the patch, however db5.3 will be obsoleted by db6.0 (in NEW),
> so this won't be fixed.
> >
> > Would it be possible for you to check if db6.0 is affected?
>
> OK, thanks for the info.


It would be great if Ubuntu could also transition to db6.0 and skip db5.3.

You can pull the db-defaults from experimental to do so.


> I checked it out of git and had a look and that
> part of the code is the same. The patch applies too, so I'm fairly
> confident it's still needed.
>

Applied and pushed.


> The git repo for 6.0 is in a bit of a strange state so I didn't manage
> to get a source package out of it yet to do a build in order to
> confirm/deny this.
>

The git was 8 commits behind, it has been pushed now.

O.
-- 
Ondřej Surý 

Bug#712245: many segfault occur concerning libglib-2.0.so.0.3200.4

[Emilio Pozuelo Monfort]

On 15/06/13 03:11, Takashi Yano wrote:
> Hi,
> 
> Thanks for checking the backtrace log.
> 
>>> (gnome-control-center:5976): Clutter-CRITICAL **: Unable to initialize 
>>> Clutter: Unable to find suitable fbconfig for the GLX
> context: Failed to find any compatible fbconfigs
>>> [New Thread 0xacf89b70 (LWP 5980)]
>>
>> I suppose clutter doesn't like that you're running it through VNC.
> 
> This message appears even in other machines which cause no segfault.
> So it may not have a direct causal relationship to the problem.
> 
> 
> On the other hand,
> 
>>> (gnome-control-center:5976): Bluetooth-WARNING **: Could not open RFKILL 
>>> control device, please verify your installation
>>> [New Thread 0xac24cb70 (LWP 5982)]
> 
> this error message appears only in the machine which causes segfaults.

OK that makes sense as only bluetooth apps are crashing.

What's the output of `ls -l /dev/rfkill' ? The permissions may be wrong, or it
may be a problem with the ACLs. What version of udev and kernel do you have?

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712308: libkrb5-3: broke multiarch feature

[merlin]

Package: libkrb5-3
Version: 1.10.1+dfsg-6
Severity: important

Dear Maintainer,
update of libkrb5-3 from 1.10.1+dfsg-5 to 1.10.1+dfsg-6 in Sid AMD64 broke
multiarch feature all krb5 libs in :i386 are
suppressed(libkrkrb5-3:i386,libkrb5support0:i386,libgssapi-
krb5-2:i386,libk5crypto3:i386) so other packages belonging to these packages
are also suppressed.
Downgrading krb5 to 1.10.1+dfsg-5 solve the problem




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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#711107: gtk+3.0: FTBFS on ia64 and mips

[Emilio Pozuelo Monfort]

Hi,

On 15/06/13 04:01, Stephan Schreiber wrote:
> I'm using Debian unstable on ia64.
> 
> I built the gtk+3.0 package twice; the test always fails as on the ia64 
> buildd:
> 
> /usr/bin/make  check-local
> make[4]: Entering directory
> `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y'
> TEST: accessibility-dump... (pid=3867)
> PASS: accessibility-dump
> TEST: tree-performance... (pid=3889)
> PASS: tree-performance
> TEST: text... (pid=3908)
>   /text/bold/GtkLabel: OK
>   /text/basic/GtkLabel:OK
>   /text/basic/GtkEntry:OK
>   /text/basic/GtkTextView: OK
>   /text/words/GtkLabel:OK
>   /text/words/GtkEntry:OK
>   /text/words/GtkTextView: OK
>   /text/changed/GtkLabel:  OK
>   /text/changed/GtkEntry:  OK
>   /text/changed/GtkTextView:   OK
>   /text/selection/GtkLabel:OK
>   /text/selection/GtkEntry:OK
>   /text/selection/GtkTextView: OK
> PASS: text
> TEST: children... (pid=3927)
>   /scrolledwindow/child-count: OK
>   /child/add-remove/GtkScrolledWindow: OK
>   /child/add-remove/GtkBox:OK
>   /child/add-remove/GtkPaned:  OK
>   /child/add-remove/GtkGrid:   OK
>   /child/add-remove/GtkEventBox:   OK
>   /child/add-remove/GtkWindow: OK
>   /child/add-remove/GtkAssistant:  OK
>   /child/add-remove/GtkFrame:  OK
>   /child/add-remove/GtkExpander:   OK
>   /child/add-remove/GtkTable:  OK
>   /child/add-remove/GtkTextView:   OK
>   /child/add-remove/GtkTreeView:   OK
>   /child/add-remove/GtkNotebook:   OK
>   /child/add-remove/GtkEntry:  **
> ERROR:/home/stephan/gtkplus2/gtk+3.0-3.8.2/./tests/a11y/children.c:201:test_add_remove:
> assertion failed: (parent_data[j].parent == NULL)
> FAIL
> GTester: last random seed: R02S2c373dee33e29d116c561db135f16945
> (pid=3946)
> FAIL: children
> TEST: derive... (pid=3960)
> PASS: derive
> TEST: value... (pid=3979)
>   /value/basic/GtkSpinButton:  OK
>   /value/basic/GtkLevelBar:OK
> PASS: value
> TEST: tree-relationships... (pid=3998)
>   /a11y/tree/focus:OK
>   /a11y/tree/relations:OK
> PASS: tree-relationships
> TEST: util... (pid=4018)
>   /util/toolkit-name:  OK
>   /util/toolkit-version:   OK
>   /util/root:  OK
> PASS: util
> make[4]: *** [test-cwd] Error 1
> make[4]: Target `check-local' not remade because of errors.
> make[4]: Leaving directory
> `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y'
> make[3]: *** [check-am] Error 2
> make[3]: Target `check' not remade because of errors.
> make[3]: Leaving directory
> `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y'
> 
> 
> 
> The test passes when I run it subsequently:
> 
> stephan@itanic:~/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y$ 
> xvfb-run
> ./children
> /scrolledwindow/child-count: OK
> /child/add-remove/GtkScrolledWindow: OK
> /child/add-remove/GtkBox: OK
> /child/add-remove/GtkPaned: OK
> /child/add-remove/GtkGrid: OK
> /child/add-remove/GtkEventBox: OK
> /child/add-remove/GtkWindow: OK
> /child/add-remove/GtkAssistant: OK
> /child/add-remove/GtkFrame: OK
> /child/add-remove/GtkExpander: OK
> /child/add-remove/GtkTable: OK
> /child/add-remove/GtkTextView: OK
> /child/add-remove/GtkTreeView: OK
> /child/add-remove/GtkNotebook: OK
> /child/add-remove/GtkEntry: OK
> 
> 
> 
> It works with fakeroot as well:
> 
> stephan@itanic:~/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y$ 
> fakeroot
> xvfb-run ./children
> /scrolledwindow/child-count: OK
> /child/add-remove/GtkScrolledWindow: OK
> /child/add-remove/GtkBox: OK
> /child/add-remove/GtkPaned: OK
> /child/add-remove/GtkGrid:

Bug#712309: RM: haskell-quickcheck1 -- ROM; Old version not needed any more

[Joachim Breitner]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

another package of an old version that can be dropped now:

$ dak rm -nR haskell-quickcheck1
Working... done.
Will remove the following packages from unstable:

haskell-quickcheck1 |  1.2.0.1-6 | source
libghc-quickcheck1-dev |  1.2.0.1-6 | amd64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
libghc-quickcheck1-doc |  1.2.0.1-6 | all
libghc-quickcheck1-prof |  1.2.0.1-6 | amd64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc

Maintainer: Debian Haskell Group 


- --- Reason ---

- --

Checking reverse dependencies...
No dependency problem found.


Thanks,
Joachim

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlG8OtcACgkQ9ijrk0dDIGw8VwCgr3fLtqCv970aKJmt+H0MHVXn
pC4AoKWTVLboqMaXz9+jCWzaeVUs75Cp
=PWoJ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#419647: w3m-el should not silently reject cookies by default

[Tatsuya Kinoshita]

Hi emacs-w3m developers,

Could you please reconsider setting w3m-use-cookies to t by default
for the next release?

On April 17, 2007, [emacs-w3m:09385], jasonspiro4 (at gmail.com) wrote:
> 2007/4/17, Katsumi Yamaoka  wrote:
>> > Why don't you enable the option by default?
>>
>> It might be because no one has never requested it. ;-)
>> Otherwise, no developer might have wanted to enable it since it
>> is still experimental.  Anyway, we will need much time and
>> effort to complete the feature.
> 
> I think that in most cases, some cookie support is far better than
> none.  Could you kindly enable it by default for the next release?
> That way less people will undergo the same frustration I did before
> I learned to set w3m-use-cookies to t.

Thanks,
-- 
Tatsuya Kinoshita


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712299: iceape: Iceape becomes default x-www-browser

[Axel Beckert]

Hi Lorenzo,

I'm Cc'ing the bug-report again as I think this discussion should be
public.

On Sat, Jun 15, 2013 at 11:34:42AM +0200, Lorenzo Sutton wrote:
> > There is such a mechanism. See the update-alternatives(8) man page.
> 
> I'm aware of the update-alternatives.
> What I'm saying is that it would be more friendly if when a
> (x-www-browser) browser is already present and selected installing
> another one (in this case iceape) wouldn't necessarily change the
> current x-www-browser.

In my humble opinion, you can't expect that the first web browser ever
installed on a system stays the default forever.

But besides that, the administrator as well as the user do have this
choice. They just have to state it once explicitly. (They're not asked
automatically, though. They have to take action theirselves.)
Otherwise the packages will continue to choose the default.

The details:

update-alternatives supports not changing x-www-browser upon
installation of an alternative with higher priority. I mentioned it
briefly in my initial reply. I'll make an example more specific on
that topic below.

> In my case iceweasel had already been installed and was of course
> the x-www-browser.
> 
> Ultimately what I mean is that the user should have the choice to
> decide what has higher priority, and not the package.

As administrator you have to explicitly choose any browser in "manual
mode" (i.e. the user's choice is honoured) instead of "auto mode"
(i.e. the packages decide which seems the best), as I did here:

# update-alternatives --config x-www-browser 
There are 13 choices for the alternative x-www-browser (providing
/usr/bin/x-www-browser).

  SelectionPath   Priority   Status

  0/usr/bin/opera  200   auto mode
  1/usr/bin/chromium   40manual mode
* 2/usr/bin/conkeror   20manual mode
  3/usr/bin/dillo  50manual mode
  4/usr/bin/iceweasel  70manual mode
  5/usr/bin/luakit 10manual mode
  6/usr/bin/midori 50manual mode
  7/usr/bin/netsurf100   manual mode
  8/usr/bin/opera  200   manual mode
  9/usr/bin/surf   30manual mode
  10   /usr/bin/uzbl-browser   10manual mode
  11   /usr/bin/vimprobable2   20manual mode
  12   /usr/bin/xlinks269manual mode
  13   /usr/bin/xxxterm50manual mode

Press enter to keep the current choice[*], or type selection number: 
[...]

In my case, the default browser by package choice would be the
non-free opera package (priority 200), but I prefer to have conkeror
as default browser system-wide. So I've chosen option 2 (conkeror in
manual mode). Now, conkeror stays x-www-browser even if I'd install a
browser which says that it has priority 300.

Besides that, each user can still override the default browser per user
instead of using the system-wide setting via x-www-browser by two ways:

1) In case of using a desktop environment, usually the desktop
   environment allows to change the default web browser for the
   current user. (This may depend on the desktop environment -- at
   least GNOME offered to configure that the last time I checked.)

2) For users without a full-blown desktop environment there's also
   /usr/bin/sensible-browser (of the package sensible-utils) which, in
   addition to the above, checks if the environment variable $BROWSER
   is set as well if GNOME is running, in which case it prefers
   gnome-www-browser over x-www-browser. It can even run text-mode
   based browsers like lynx and w3m in a terminal if prefered by the
   user.

In my humble opinion, those three places to change the default web
browser together allow full and fine granulated control over which
alternatives is used in which situation for each, the administrator,
for the desktop environment user as well as for the commandline user.

If you think, that all is still not a good enough solution, i.e.
because they're not asked without taking action theirselves, I would
recommend you to file a more general bug instead of this one against a
single web browser which can't and won't change the overall situation
and infrastructure.

update-alternatives is part of the dpkg package, so I think that
filing a bug report against dpkg would be a proper starting point. I
though suspect that this would be a more general discussion, maybe
held on the debian-de...@lists.debian.org mailing list.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debia

Bug#712310: galternatives crashes with Python traceback when run from a terminal

[Noel Duffy]

Package: galternatives
Version: 0.13.5+nmu2
Severity: important

Dear Maintainer,

I installed galternatives with apt-get install. When I run it from gnome-
terminal, I get this python traceback:

$ galternatives
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could
not open display
  warnings.warn(str(e), _gtk.Warning)
/usr/lib/pymodules/python2.7/galternatives/main.py:52: Warning: invalid (NULL)
pointer instance
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: Warning:
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: GtkWarning:
IA__gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: Warning: g_object_get:
assertion `G_IS_OBJECT (object)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: Warning: value "TRUE" of
type `gboolean' is invalid or out of range for property `visible' of type
`gboolean'
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: GtkWarning:
IA__gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_context_set_font_description: assertion `context != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_context_set_base_dir: assertion `context != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_context_set_language: assertion `context != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_new: assertion `context != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_set_text: assertion `layout != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_set_attributes: assertion `layout != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_set_alignment: assertion `layout != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_set_ellipsize: assertion `PANGO_IS_LAYOUT (layout)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_set_single_paragraph_mode: assertion `PANGO_IS_LAYOUT (layout)'
failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_set_width: assertion `layout != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_get_extents: assertion `layout != NULL' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: PangoWarning:
pango_layout_get_pixel_extents: assertion `PANGO_IS_LAYOUT (layout)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: Warning: g_object_unref:
assertion `G_IS_OBJECT (object)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: GtkWarning: Screen for
GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: GtkWarning:
IA__gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main.py:52: GtkWarning:
IA__gtk_icon_size_lookup_for_settings: assertion `GTK_IS_SETTINGS (settings)'
failed
  self.gui = glade.XML ('/usr/share/galternatives/galternatives.glade')
/usr/lib/pymodules/python2.7/galternatives/main

Bug#709490: The bug is fixed

[Adam D. Barratt]

Control: fixed -1 7.1

On Sat, 2013-06-15 at 17:21 +0700, Aleksey Kravchenko wrote:
> Fixed in the RHash version 1.2.9-8+deb7u1 :)

The bug in rhash, yes. Not the release.d.o bug.

For future reference, the release.d.o bug should stay open until the
point release has happened, at which point we close it. As the point
release is actually in progress anyway, I'll just add the fixed version
this time.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712311: [INTL:da] Danish translation of the debconf templates nss-pam-ldapd

[Joe Dalton]

Package: nss-pam-ldapd
Severity: wishlist
Tags: l10n patch

Please include the attached Danish nss-pam-ldapd translations.

joe@pc:~/over/debian/nss-pam-ldapd$ msgfmt --statistics -c -v -o /dev/null da.po
da.po: 51 oversatte tekster.

bye
Joe


da.po.tar.gz
Description: GNU Zip compressed data

Bug#630120: hi

[Celestina Valenza]

Greetings! I am having a look for guy!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712312: evince: 2 pages per side does not work

[Rustom Mody]

Package: evince
Version: 3.4.0-3.1
Severity: normal

Dear Maintainer,

When I use evince I can print one page per side.
If I choose 2 pages per side it prints 4.

I have a canon printer whose drivers could be the problem, however libreoffice
works... so I think its not there



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages evince depends on:
ii  evince-common3.4.0-3.1
ii  gnome-icon-theme 3.4.0-2
ii  libatk1.0-0  2.8.0-2
ii  libc62.17-3
ii  libcairo-gobject21.12.14-4
ii  libcairo21.12.14-4
ii  libevdocument3-4 3.4.0-3.1
ii  libevview3-3 3.4.0-3.1
ii  libgail-3-0  3.4.2-6
ii  libgdk-pixbuf2.0-0   2.28.1-1
ii  libglib2.0-0 2.36.1-2build1
ii  libgnome-keyring03.4.1-1
ii  libgtk-3-0   3.4.2-6
ii  libice6  2:1.0.8-2
ii  libnautilus-extension1a  3.4.2-1+build1
ii  libpango1.0-01.32.5-5+b1
ii  libsm6   2:1.2.1-2
ii  libx11-6 2:1.5.0-1+deb7u1
ii  libxml2  2.8.0+dfsg1-7+nmu1
ii  shared-mime-info 1.0-1+b1
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages evince recommends:
ii  dbus-x11  1.6.10-1
ii  gvfs  1.12.3-4

Versions of packages evince suggests:
ii  nautilus  3.4.2-1+build1
ii  poppler-data  0.4.6-3
ii  unrar 1:4.2.4-0.3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712313: RM: some Haskell library packages [mips mipsel s390 s390x] -- RoM; unbuildable on architectures without GHCi

[Colin Watson]

Package: ftp.debian.org
Severity: normal

Recent updates to various Haskell packages have made them unbuildable on
the architectures that lack GHCi (interpreter) support.  I already filed
a request for armel and armhf in #712036, which were unusual because
they had GHCi disabled recently; this bug is for architectures where
GHCi has never been available.

  dak rm -a mips,mipsel,s390,s390x -b libghc-adjunctions-dev 
libghc-adjunctions-prof libghc-algebra-dev libghc-algebra-prof 
libghc-comonad-transformers-dev libghc-comonad-transformers-prof 
libghc-comonads-fd-dev libghc-comonads-fd-prof libghc-data-lens-dev 
libghc-data-lens-prof libghc-distributive-dev libghc-distributive-prof 
libghc-free-dev libghc-free-prof libghc-hopenpgp-dev libghc-hopenpgp-prof 
libghc-keys-dev libghc-keys-prof libghc-representable-functors-dev 
libghc-representable-functors-prof libghc-representable-tries-dev 
libghc-representable-tries-prof

Here's annotated 'dak rm -Rn' output:

  # Broken Build-Depends:
  haskell-adjunctions: libghc-comonad-transformers-dev (< 2.2)
   libghc-comonad-transformers-dev (>= 2.1.1.1)
   libghc-comonad-transformers-dev (>= 3.0)
   libghc-comonad-transformers-prof
   libghc-distributive-dev (< 0.3)
   libghc-distributive-dev (>= 0.2.2)
   libghc-distributive-prof
   libghc-keys-dev (< 2.2)
   libghc-keys-dev (>= 2.1.3.1)
   libghc-keys-dev (>= 3.0)
   libghc-keys-prof
   libghc-representable-functors-dev (< 2.5)
   libghc-representable-functors-dev (>= 2.4.0.1)
   libghc-representable-functors-dev (>= 3.0.0.1)
   libghc-representable-functors-prof
  haskell-algebra: libghc-distributive-dev (< 0.3)
   libghc-distributive-dev (>= 0.2.2)
   libghc-distributive-prof
   libghc-keys-dev (< 2.2)
   libghc-keys-dev (>= 2.1.3.1)
   libghc-keys-dev (>= 3.0)
   libghc-keys-prof
   libghc-representable-functors-dev (< 2.5)
   libghc-representable-functors-dev (>= 2.4.0.1)
   libghc-representable-functors-dev (>= 3.0)
   libghc-representable-functors-prof
   libghc-representable-tries-dev (< 2.5)
   libghc-representable-tries-dev (>= 2.4.0.1)
   libghc-representable-tries-dev (>= 3.0)
   libghc-representable-tries-prof
  haskell-comonad-transformers: libghc-distributive-dev (< 0.3)
libghc-distributive-dev (> 0.2.2)
libghc-distributive-dev (>= 0.2.2)
libghc-distributive-prof
  haskell-comonads-fd: libghc-comonad-transformers-dev (< 2.2)
   libghc-comonad-transformers-dev (> 3.0)
   libghc-comonad-transformers-dev (>= 2.1.1.1)
   libghc-comonad-transformers-prof
  haskell-data-lens: libghc-comonad-transformers-dev (< 2.2)
 libghc-comonad-transformers-dev (< 3.1)
 libghc-comonad-transformers-dev (>= 2.0)
 libghc-comonad-transformers-prof
  haskell-free: libghc-comonad-transformers-dev (< 2.2)
libghc-comonad-transformers-dev (>= 2.1.1.1)
libghc-comonad-transformers-dev (>= 3.0)
libghc-comonad-transformers-prof
libghc-comonads-fd-dev (< 2.2)
libghc-comonads-fd-dev (>= 2.1.1.1)
libghc-comonads-fd-dev (>= 3.0)
libghc-comonads-fd-prof
libghc-data-lens-dev (< 2.11)
libghc-data-lens-dev (>= 2.0.4.1)
libghc-data-lens-prof
libghc-distributive-dev (< 0.3)
libghc-distributive-dev (>= 0.2.1)
libghc-distributive-prof
  haskell-keys: libghc-comonad-transformers-dev (< 2.2)
libghc-comonad-transformers-dev (>= 2.1.1.1)
libghc-comonad-transformers-dev (>= 3.0)
libghc-comonad-transformers-prof
libghc-comonads-fd-dev (< 2.2)
libghc-comonads-fd-dev (>= 2.1.1.1)
libghc-comonads-fd-dev (>= 3.0)
libghc-comonads-fd-prof
libghc-free-dev (< 2.2)
libghc-free-dev (>= 2.1.1)
libghc-free-dev (>= 3.0)
libghc-free-prof

Binaries removed by the command above.

  haskell-lens: libghc-comonad-transformers-dev (< 4)
libghc-comonad-transformers-dev (> 3)
libghc-comonad-transformers-prof
libghc-comonads-fd-dev (< 4)
libghc-comonads-fd-dev (> 3)
libghc-comonads-fd-prof
libghc-

Bug#703841: i18nspector: X-POFile-SpellExtra field currently needs to be duped

[Jakub Wilk]

* Guillem Jover , 2013-06-15, 05:19:
The X-POFile-SpellExtra field, generated and parsed by POFileSpell 
(from gettext-lint), currently needs to be present multiple times, 
one per line. Merging all those fields into a single one, spanning 
multiple lines makes POFileSpell unable to recognize it. So please 
whitelist that field from the duped checks.
This will be partially addressed in i18nspector 0.10 (hopefully to be 
released over this weekend). duplicate-header-field has been 
downgraded to minor/wild-guess (so it's an I: rather than scary E:), 
and there are separate duplicate-header-field-$FIELD tags for the 
well-known header fields:


https://bitbucket.org/jwilk/i18nspector/src/dc9f59be4584/data/tags?at=default#cl-135


Ah! Very nice. I guess it will still be printed by default?


That's right.

If there could be a way (a la lintian) to either not print some of 
these by default and enable them on the command line, or print 
everything but being able to disable some, ideally from a config file, 
that would be perfect.


Support for overrides is on my to-do list (and I added it here precisely 
with this bug in mind). It won't be ready for 0.10, though.



I can file a separate wishlist if either of these seem fine to you.


Feel free. :)

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712323: gnat-gps: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: gnat-gps
Version: 5.0-13
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_strip --package=gnat-gps --dbg-package=gnat-gps-dbg
> dh_strip --remaining-packages
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_installdeb -a
>dh_gencontrol -a
>dh_md5sums -a
>dh_builddeb -a
> dpkg-deb: building package `gnat-gps' in `../gnat-gps_5.0-13_amd64.deb'.
> dpkg-deb: building package `gnat-gps-dbg' in 
> `../gnat-gps-dbg_5.0-13_amd64.deb'.
> sed -e 's,@prefix@,/usr,' -e 's,@MAKEINFO@,makeinfo,' \
>   -e 's,@TEXI2DVI@,texi2dvi,' -e 's,@INSTALL@,install,' \
>   -e 's,@INSTALL_DATA@,install -m 644,' < docs/Makefile.in > 
> docs/Makefile
> makeinfo --no-split -o docs/gps.info docs/gps.texi
> docs/gps.texi:2: unknown command `input'
> docs/gps.texi:46: misplaced {
> docs/gps.texi:46: misplaced }
> docs/gps.texi:2699: command @bullet not accepting argument in brace should 
> not be on @table line
> docs/gps.texi:2712: command @bullet not accepting argument in brace should 
> not be on @table line
> docs/gps.texi:2733: command @bullet not accepting argument in brace should 
> not be on @table line
> docs/gps.texi:13535: warning: node `Defining project attributes' is next for 
> `Defining text aliases' in menu but not in sectioning
> docs/gps.texi:13749: warning: node `Defining text aliases' is prev for 
> `Defining project attributes' in menu but not in sectioning
> docs/gps.texi:16360: warning: node `Subprogram parameters' is next for `The 
> Python Interpreter' in menu but not in sectioning
> docs/gps.texi:16538: warning: node `The Python Interpreter' is prev for 
> `Subprogram parameters' in menu but not in sectioning
> make: *** [docs/gps.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/gnat-gps_5.0-13_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712319: binutils-h8300-hms: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: binutils-h8300-hms
Version: 2.16.1-8
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[4]: Entering directory 
> `/«PKGBUILDDIR»/builddir-h8300-hitachi-coff/bfd/doc'
> cc -o chew.$$ ../../../bfd/doc/chew.c \
>\
> -I.. -I../../../bfd/doc/.. -I../../../bfd/doc/../../include 
> -I../../../bfd/doc/../../intl -I../../intl; \
>   /bin/sh ../../../bfd/doc/../../move-if-change chew.$$ chew
> make[4]: Leaving directory 
> `/«PKGBUILDDIR»/builddir-h8300-hitachi-coff/bfd/doc'
> ./chew -f ../../../bfd/doc/doc.str  <../../../bfd/doc/../opncls.c >opncls.tmp
> /bin/sh ../../../bfd/doc/../../move-if-change opncls.tmp opncls.texi
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && cd ../../../bfd/doc && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   for f in ../../../bfd/doc/bfd.info ../../../bfd/doc/bfd.info-[0-9] 
> ../../../bfd/doc/bfd.info-[0-9][0-9] ../../../bfd/doc/bfd.i[0-9] 
> ../../../bfd/doc/bfd.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>   done; \
>   cd "$am__cwd"; \
>   if makeinfo --split-size=500   -I ../../../bfd/doc \
>-o ../../../bfd/doc/bfd.info ../../../bfd/doc/bfd.texinfo; \
>   then \
> rc=0; \
> cd ../../../bfd/doc; \
>   else \
> rc=$?; \
> cd ../../../bfd/doc && \
> $restore $backupdir/* `echo "./../../../bfd/doc/bfd.info" | sed 
> 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> ../../../bfd/doc/elf.texi:1: warning: @section missing argument
> ../../../bfd/doc/bfd.texinfo:335: unknown command `colophon'
> ../../../bfd/doc/bfd.texinfo:346: unknown command `cygnus'
> ../../../bfd/doc/bfdt.texi:313: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/init.texi:5: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/archive.texi:54: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/format.texi:27: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/reloc.texi:495: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/core.texi:8: raising the section level of @subsubsection 
> which is too low
> ./opncls.texi:5: raising the section level of @subsubsection which is too low
> ../../../bfd/doc/libbfd.texi:10: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/cache.texi:14: raising the section level of @subsubsection 
> which is too low
> ../../../bfd/doc/elf.texi:13: raising the section level of @subsubsection 
> which is too low
> make[3]: *** [../../../bfd/doc/bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-h8300-hms_2.16.1-8_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712316: xemacs21-packages: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: xemacs21-packages
Version: 2009.02.17.dfsg.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> cd . && makeinfo  -o smtpmail.info smtpmail.texi
> smtpmail.texi:34: misplaced {
> smtpmail.texi:34: misplaced }
> smtpmail.texi:35: misplaced {
> smtpmail.texi:35: misplaced }
> smtpmail.texi:36: misplaced {
> smtpmail.texi:36: misplaced }
> make[3]: *** [smtpmail.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/xemacs21-packages_2009.02.17.dfsg.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712318: yafc: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: yafc
Version: 1.2.4-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/doc'
> Updating ./version.texi
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash /«PKGBUILDDIR»/support/missing makeinfo --version) 
> >/dev/null 2>&1; then \
> for f in yafc.info yafc.info-[0-9] yafc.info-[0-9][0-9] yafc.i[0-9] 
> yafc.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if /bin/bash /«PKGBUILDDIR»/support/missing makeinfo   -I . \
>-o yafc.info yafc.texi; \
>   then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd .; \
>   else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd . && \
> $restore $backupdir/* `echo "./yafc.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> ./yafc_intro.texi:25: raising the section level of @subsection which is too 
> low
> ./yafc_bookmark.texi:35: raising the section level of @subsection which is 
> too low
> ./yafc_intro.texi:1: warning: Prev pointer `top' (for node `Overview') 
> different from node name `Top'
> ./yafc_intro.texi:1: warning: Up pointer `top' (for node `Overview') 
> different from node name `Top'
> ./yafc_invoke.texi:1: warning: Up pointer `top' (for node `Invoking Yafc') 
> different from node name `Top'
> ./yafc_shell.texi:1: warning: Up pointer `top' (for node `The shell') 
> different from node name `Top'
> ./yafc_config.texi:1: warning: Up pointer `top' (for node `Configuration') 
> different from node name `Top'
> ./yafc_bookmark.texi:1: warning: Up pointer `top' (for node `Bookmarks') 
> different from node name `Top'
> yafc.texi:99: warning: Up pointer `top' (for node `Kerberos') different from 
> node name `Top'
> make[3]: *** [yafc.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/yafc_1.2.4-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712320: xserver-xorg-video-nouveau: FTBFS: configure: error: Package requirements (libdrm_nouveau = 0.6) were not met:

[David Suárez]

Source: xserver-xorg-video-nouveau
Version: 1:1.0.1-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_configure -- CURDIR="/«PKGBUILDDIR»"
> configure: WARNING: unrecognized options: --disable-maintainer-mode
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether make supports nested variables... (cached) yes
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... none
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
> func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
> libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking dependency style of gcc... (cached) none
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking if RANDR is defined... yes
> checking if RENDER is defined... yes
> checking if XV is defined... yes
> checking if DPMSExtension is defined... yes
> checking for LIBDRM_NOUVEAU_DUMMY... no
> configure: error: Package requirements (libdrm_nouveau = 0.

Bug#712315: binutils-z80: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: binutils-z80
Version: 2.22-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/build/bfd/doc'
> make[5]: `chew' is up to date.
> make[5]: Leaving directory `/«PKGBUILDDIR»/build/bfd/doc'
> ./chew -f /«PKGBUILDDIR»/src/bfd/doc/doc.str 
> linker.tmp
> /bin/bash /«PKGBUILDDIR»/src/bfd/doc/../../move-if-change linker.tmp 
> linker.texi
> restore=: && backupdir=".am$$" && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (makeinfo --split-size=500 --split-size=500 --version) 
> >/dev/null 2>&1; then \
> for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
> bfd.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   if makeinfo --split-size=500 --split-size=500   -I 
> /«PKGBUILDDIR»/src/bfd/doc \
>-o bfd.info `test -f 'bfd.texinfo' || echo 
> '/«PKGBUILDDIR»/src/bfd/doc/'`bfd.texinfo; \
>   then \
> rc=0; \
>   else \
> rc=$?; \
> $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> /«PKGBUILDDIR»/src/bfd/doc/bfd.texinfo:325: unknown command `colophon'
> /«PKGBUILDDIR»/src/bfd/doc/bfd.texinfo:336: unknown command `cygnus'
> make[4]: *** [bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-z80_2.22-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712314: yap: FTBFS: command @bullet not accepting argument in brace should not be on @table line

[David Suárez]

Source: yap
Version: 5.1.3-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/arch'
> makeinfo ../docs/yap.tex
> ../docs/swi.tex:54: warning: @example should only appear at a line beginning
> ../docs/yap.tex:13407: command @bullet not accepting argument in brace should 
> not be on @table line
> make[1]: *** [yap.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/yap_5.1.3-6_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712317: elib: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: elib
Version: 1.0-11.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> dh_testdir
> /usr/bin/make info
> make[1]: Entering directory `/«PKGBUILDDIR»'
> makeinfo elib.texi
> elib.texi:41: @sp missing argument
> elib.texi:43: @sp missing argument
> make[1]: *** [elib.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/elib_1.0-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712321: oneliner-el: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: oneliner-el
Version: 0.3.6-7.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/info'
> sed -e 's/@setfilename oneliner.info/@setfilename oneliner.jis.info/' \
>   -e 's/@set us/@set jp/' oneliner.texi > tmp.texi
> mv tmp.texi oneliner.texi
> /bin/rm -f oneliner.jis.info*
> /usr/bin/touch oneliner.jis.info
> /usr/bin/makeinfo --no-split oneliner.texi
> oneliner.texi:28: warning: @center missing argument
> oneliner.texi:778: raising the section level of @subsubsection which is too 
> low
> make[2]: *** [info-ja] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/oneliner-el_0.3.6-7.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712324: emms: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: emms
Version: 3.0+20110425+1.git298e022-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«BUILDDIR»/emms-3.0+20110425+1.git298e022/doc'
> makeinfo --no-split emms.texinfo
> ./gpl.texi:668: @unnumberedsec seen before @end enumerate
> ./gpl.texi:725: unmatched `@end enumerate'
> emms.texinfo:1054: warning: node next `Markable Playlists' in menu `The 
> Browser' and in sectioning `APE / FLAC Commands' differ
> emms.texinfo:1138: warning: node prev `APE / FLAC Commands' in menu `Last.fm' 
> and in sectioning `Markable Playlists' differ
> emms.texinfo:1179: warning: node next `Extending Emms' in menu `Copying' and 
> in sectioning `The Browser' differ
> emms.texinfo:1343: warning: node prev `The Browser' in menu `Markable 
> Playlists' and in sectioning `Extending Emms' differ
> emms.texinfo:1968: warning: node next `Music Player Daemon' in menu 
> `Streaming Audio' and in sectioning `Lyrics' differ
> emms.texinfo:2086: warning: node prev `Lyrics' in menu `Streaming Audio' and 
> in sectioning `Music Player Daemon' differ
> emms.texinfo:2227: warning: node next `Last.fm' in menu `APE / FLAC Commands' 
> and in sectioning `Streaming Audio' differ
> emms.texinfo:2379: warning: node next `Streaming Audio' in menu `Lyrics' and 
> in sectioning `Copying' differ
> emms.texinfo:2379: warning: node prev `Streaming Audio' in menu `Music Player 
> Daemon' and in sectioning `Last.fm' differ
> make[1]: *** [emms.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/emms_3.0+20110425+1.git298e022-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712334: r5rs-doc: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: r5rs-doc
Version: 20010328-7
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> #f
> makeinfo r5rs.txi
> r5rs.txi:94: warning: @author missing argument
> r5rs.txi:104: @unnumbered seen before @end titlepage
> r5rs.txi:166: unmatched `@end titlepage'
> r5rs.txi:184: warning: @center missing argument
> r5rs.txi:761: warning: @center missing argument
> r5rs.txi:780: warning: @item missing argument
> r5rs.txi:2351: must be after `@deffn' to use `@deffnx'
> r5rs.txi:5610: warning: @center missing argument
> r5rs.txi:5625: warning: @item missing argument
> r5rs.txi:7330: warning: @cindex should not appear in @t
> r5rs.txi:7337: warning: @cindex should not appear in @t
> r5rs.txi:7367: warning: @cindex should not appear in @t
> r5rs.txi:7368: warning: @cindex should not appear in @t
> r5rs.txi:7377: warning: @cindex should not appear in @t
> r5rs.txi:7384: warning: @ignore should not appear in @t
> r5rs.txi:7451: warning: @vindex should not appear in @t
> r5rs.txi:7452: warning: @vindex should not appear in @t
> r5rs.txi:7454: warning: @vindex should not appear in @t
> r5rs.txi:7456: warning: @vindex should not appear in @t
> r5rs.txi:7459: warning: @vindex should not appear in @t
> r5rs.txi:8127: warning: @center missing argument
> r5rs.txi:8129: warning: @center missing argument
> r5rs.txi:179: warning: lowering the section level of @top appearing after a 
> lower element
> make: *** [build-stamp] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/r5rs-doc_20010328-7_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712330: tamuanova: FTBFS: command @bullet not accepting argument in brace should not be on @table line

[David Suárez]

Source: tamuanova
Version: 0.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»'
> Updating ./version-ref.texi
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash /«PKGBUILDDIR»/missing makeinfo --version) >/dev/null 
> 2>&1; then \
> for f in tamu_anova.info tamu_anova.info-[0-9] 
> tamu_anova.info-[0-9][0-9] tamu_anova.i[0-9] tamu_anova.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if /bin/bash /«PKGBUILDDIR»/missing makeinfo   -I . \
>-o tamu_anova.info tamu_anova.texi; \
>   then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd .; \
>   else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd . && \
> $restore $backupdir/* `echo "./tamu_anova.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> tamu_anova.texi:180: warning: missing name for @deftypefn
> tamu_anova.texi:188: warning: missing name for @deftypefn
> ./fdl.texi:406: raising the section level of @unnumberedsubsec which is too 
> low
> make[2]: *** [tamu_anova.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/tamuanova_0.2-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712326: gri: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: gri
Version: 2.12.23-2.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/doc/tst_suite'
> perl ./../gri2html tst_IO.gri tst_IO.html
> perl ./../gri2html tst_control.gri tst_control.html
> perl ./../gri2html tst_rpn.gri tst_rpn.html
> perl ./../gri2html tst_var_syn.gri tst_var_syn.html
> make[2]: Leaving directory `/«PKGBUILDDIR»/doc/tst_suite'
> /bin/bash /«PKGBUILDDIR»/missing --run makeinfo   -I. gri.texi
> gri.texi:18489: raising the section level of @subsubsection which is too low
> make[1]: *** [html] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/gri_2.12.23-2.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712328: biomaj: FTBFS: [javac] /«PKGBUILDDIR»/usr/share/biomaj/src/org/inria/biomaj/ant/task/BmajExecute.java:543: cannot find symbol

[David Suárez]

Source: biomaj
Version: 1.2.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> echo 
> 
> ant -Dant.build.javac.source=1.5 -Dant.build.javac.target=1.5 -f 
> usr/share/biomaj/build.xml
> Buildfile: /«PKGBUILDDIR»/usr/share/biomaj/build.xml
> 
> test_env:
> 
> compile:
> [mkdir] Created dir: /«PKGBUILDDIR»/usr/share/biomaj/build/classes
> [mkdir] Created dir: /«PKGBUILDDIR»/usr/share/biomaj/dist
> [javac] /«PKGBUILDDIR»/usr/share/biomaj/build.xml:110: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 137 source files to 
> /«PKGBUILDDIR»/usr/share/biomaj/build/classes
> [javac] 
> /«PKGBUILDDIR»/usr/share/biomaj/src/org/inria/biomaj/ant/task/BmajExecute.java:543:
>  cannot find symbol
> [javac] symbol  : method 
> getRecursiveProperty(java.util.Hashtable,java.lang.String)
> [javac] location: class org.inria.biomaj.exe.bank.BankFactory
> [javac]   String res = 
> BankFactory.getRecursiveProperty(getProject().getProperties(), key);
> [javac]   ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: 
> /«PKGBUILDDIR»/usr/share/biomaj/src/org/inria/biomaj/ant/task/BmajSymlink.java
>  uses unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 error
> 
> BUILD FAILED
> /«PKGBUILDDIR»/usr/share/biomaj/build.xml:110: Compile failed; see the 
> compiler error output for details.
> 
> Total time: 10 seconds
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/biomaj_1.2.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712332: aalib: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: aalib
Version: 1.4p5-40
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/doc'
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash /«PKGBUILDDIR»/missing makeinfo --version) >/dev/null 
> 2>&1; then \
> for f in aalib.info aalib.info-[0-9] aalib.info-[0-9][0-9] 
> aalib.i[0-9] aalib.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if /bin/bash /«PKGBUILDDIR»/missing makeinfo   -I . \
>-o aalib.info aalib.texinfo; \
>   then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd .; \
>   else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd . && \
> $restore $backupdir/* `echo "./aalib.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> aalib.texinfo:32: misplaced {
> aalib.texinfo:32: misplaced }
> aalib.texinfo:33: misplaced {
> aalib.texinfo:33: misplaced }
> aalib.texinfo:34: misplaced {
> aalib.texinfo:34: misplaced }
> aalib.texinfo:36: misplaced {
> aalib.texinfo:36: misplaced }
> aalib.texinfo:64: warning: @tex should only appear at a line beginning
> aalib.texinfo:1321: raising the section level of @subsection which is too low
> make[2]: *** [aalib.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/aalib_1.4p5-40_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712327: freepops: FTBFS: Package babel Error: You haven't specified a language option.

[David Suárez]

Source: freepops
Version: 0.2.9-7
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part: 
> Overfull \hbox (36.65346pt too wide) in paragraph at lines 2426--2426
>  []\T1/pcr/m/n/10 log.say("Session loaded for " .. 
> internal_sta
> te.name .. "@" ..[] 
> [62] [63] [64]
> Overfull \hbox (6.16461pt too wide) in paragraph at lines 2559--2559
> []\T1/pbk/db/n/14.4 I've in-stalled FreeP-OPs and prop-erly con-fig-ured my 
> mai
> l client,
> [65]
> Overfull \hbox (1.39658pt too wide) in paragraph at lines 2631--2633
> []\T1/pbk/l/n/12 Unix ex-am-ple: \T1/pcr/m/n/12 /usr/bin/freepopsd -P 
> proxy:por
> t -A user:pass -w
> [66]
> Overfull \hbox (0.1494pt too wide) in paragraph at lines 2639--2647
> \T1/pbk/l/n/12 Stop us-ing that crazy an-tivirus :-) Se-ri-ously, FreeP-OPs 
> doe
> s not con-tain viruses,
> 
> Overfull \hbox (115.86478pt too wide) in paragraph at lines 2659--2661
> \T1/pbk/l/n/12 This man-ual has been writ-ten by En-rico Tassi \T1/pcr/m/n/12 
> <
> gareuselesinge [at] users.sourceforge.net>
> 
> Overfull \hbox (94.91243pt too wide) in paragraph at lines 2659--2661
> \T1/pbk/l/n/12 and re-vised and trans-lated by Nicola Coc-chiaro 
> \T1/pcr/m/n/12
>   
> 
> Overfull \hbox (32.65671pt too wide) in paragraph at lines 2674--2676
> \T1/pbk/l/n/12 yahoo.lua, hot-mail.lua, aol.lua, netscape.lua, mail-com.lua, 
> ju
> no.lua, mail2world.lua,
> 
> Underfull \hbox (badness 1) in paragraph at lines 2678--2679
> 
> 
> Underfull \hbox (badness 1) in paragraph at lines 2689--2690
> 
> [67]
> Underfull \hbox (badness 1) in paragraph at lines 2694--2695
> 
> [68] (./manual.aux) )
> (see the transcript file for additional information)
> Output written on manual.dvi (68 pages, 171024 bytes).
> Transcript written on manual.log.
> This is dvips(k) 5.993 Copyright 2013 Radical Eye Software 
> (www.radicaleye.com)
> ' TeX output 2013.06.08:2050' -> 
> 
> 
> 
> . 
> 
> 
> 
> 
> 
> 
> 
> 
> [1] 
> [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14<./EPS/main.eps>] [15
> <./EPS/settings.eps><./EPS/server.eps>] [16<./EPS/advanced.eps>] [17] [18] 
> [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] 
> [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47
> <./EPS/login.eps>] [48] [49] [50<./EPS/logindone.eps>] [51<./EPS/inbox.eps>] 
> [52] [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63] [64] [65] [66] 
> [67] [68] 
> Generating the PDF manuals
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./manual-it.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/bookman.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/a4wide/a4wide.sty
> (/usr/share/texlive/texmf-dist/tex/latex/ntgclass/a4.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def)))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: You haven't specified a language option.
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> No pages of output.
> Transcript written on manual-it.log.
> make[2]: *** [manual-it.dvi] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/freepops_0.2.9-7_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debi

Bug#712329: epix: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: epix
Version: 1.2.10-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/samples'
> touch sample-stamp
> tar -cf sample_src.tar R_demo.xp S2_harmonics.xp artifacts.xp bowl.xp 
> butterfly.xp calculus.xp clipping.xp color_sep.xp conic.xp contour.xp 
> coord_tricks.xp cropplot.xp dataplot.xp decorate.xp demoivre.xp denom.xp 
> densityplot.xp dipole.xp extract.xp geomsum.xp golden_rect.xp hello.xp 
> histogram.xp hyperboloid.xp inverse.xp koch.xp label_debug.xp layout.xp 
> layout2.xp legend.xp levelset.xp levelset2.xp levelset3.xp line_debug.xp 
> lissajous.xp log.xp lorenz.xp medians.xp minkowski.xp newton.xp objects.xp 
> oscillator.xp parabola.xp pascal.xp planes.xp plotting.xp plotting2.xp 
> plotting3.xp polar.xp pole.xp polyhedra.xp saddle.xp semicirc.xp shadeplot.xp 
> slopefield.xp sphere.xp spherical.xp sqrt.xp sqrt2.xp std_F.xp 
> surface_shade.xp symmetries.xp tori.xp torus.xp twisted_cubic.xp uppersum.xp 
> vfield.xp weierstrass.xp wheel.xp cube.flx helicoid.flx house.flx 
> lighting.flx mirrorball.flx pendulum.flx riemann.flx steiner.flx steiner2.flx 
> stereo_proj.flx trig.flx \
>   README binom.cc lighting.h std_F.cc std_F.h
> gzip -9 sample_src.tar
> make[2]: Leaving directory `/«PKGBUILDDIR»/samples'
> Making all in doc
> make[2]: Entering directory `/«PKGBUILDDIR»/doc'
> latex -interaction=batchmode manual 2>&1 >/dev/null
> make[2]: *** [manual-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/epix_1.2.10-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712331: slime: FTBFS: command @bullet not accepting argument in brace should not be on @table line

[David Suárez]

Source: slime
Version: 1:20120525-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/doc'
> cat ../ChangeLog | \
>   sed -ne '/^[0-9]/{s/^[^ ]* *//; s/ *<.*//; p;}' | \
>   sort | \
>   uniq -c | \
>   sort -nr| \
>   sed -e 's/^[^A-Z]*//' | \
>   awk -f texinfo-tabulate.awk | \
>   sed -e "s/\o341/@'a/g" | \
> sed -e "s/\o355/@'{@dotless{i}}/g" | \
>   sed -e "s/\o351/@'e/g" | \
>   sed -e "s/\o361/@~n/g" | \
>   sed -e 's/\o370/@o{}/g' \
>   > contributors.texi
> HOME=/«PKGBUILDDIR»/doc texi2dvi slime.texi
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./slime.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2013-02-01.11]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.)
> (slime-small.eps
> )
> [1] [2] [-1] Chapter 1 Chapter 2 [1] [2]
> Cross reference values unknown; you must run TeX again. [3]
> Overfull \hbox (20.69044pt too wide) in paragraph at lines 515--515
>  []@texttt (NAME (PROGRAM PROGRAM-ARGS...) &key CODING-SYSTEM INIT 
> INIT-FUNCTIO
> N ENV)[] |
> [4] Chapter 3 [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] Chapter 4
> [16] [17] [18] [19] Chapter 5 [20] [21] [22] Chapter 6 [23] [24] [25] [26]
> Chapter 7 [27]
> Overfull \hbox (26.43913pt too wide) in paragraph at lines 2004--2004
>  []@texttt (swank:create-server :port 4005  :dont-close t :coding-system 
> "utf-8
> -unix")[] |
> [28]
> Overfull \hbox (14.94176pt too wide) in paragraph at lines 2069--2069
>  []@texttt :remote-host 
> "remote.example
> .com"[] |
> [29] Chapter 8 [30] [31] [32] [33] [34]
> Overfull \hbox (15.27109pt too wide) in paragraph at lines 2495--2495
>  []@texttt (defmethod initialize-instance :after ((object foo) &key blub))[] |
> [35] [36] [37] [38] [39] [40] [41] [42] Chapter 9 [43] (./contributors.texi
> [44]) (Key (Character) Index) [45] (Command and Function Index) [46]
> (Variable and Concept Index) [47] [48] )
> (see the transcript file for additional information)
> Output written on slime.dvi (51 pages, 119192 bytes).
> Transcript written on slime.log.
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./slime.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2013-02-01.11]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.) 
> (./slime.aux)
> (slime-small.eps
> )
> [1] [2] (./slime.toc [-1] [-2]) [-3] Chapter 1 Chapter 2 [1] [2] [3]
> Overfull \hbox (20.69044pt too wide) in paragraph at lines 515--515
>  []@texttt (NAME (PROGRAM PROGRAM-ARGS...) &key CODING-SYSTEM INIT 
> INIT-FUNCTIO
> N ENV)[] |
> [4] Chapter 3 [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] Chapter 4
> [16] [17] [18] Chapter 5 [19] [20] [21] Chapter 6 [22]
> Underfull \hbox (badness 7168) in paragraph at lines 1684--1688
>  @texttt symbol*[] @textrm (see Sec-tion 8.5 [Com-pound Com-ple-tion], page 
> 34)
> , and
> 
> Underfull \hbox (badness 1) in paragraph at lines 1684--1688
>  @texttt slime-fuzzy-complete-symbol[] @textrm (see Sec-tion 8.6 [Fuzzy 
> Com-ple
> -tion],
> [23] [24] [25] Chapter 7 [26]
> Overfull \hbox (26.43913pt too wide) in paragraph at lines 2004--2004
>  []@texttt (swank:create-server :port 4005  :dont-close t :coding-system 
> "utf-8
> -unix")[] |
> [27]
> Overfull \hbox (14.94176pt too wide) in paragraph at lines 2069--2069
>  []@texttt :remote-host 
> "remote.example
> .com"[] |
> [28] Chapter 8 [29] [30] [31] [32] [33]
> Overfull \hbox (15.27109pt too wide) in paragraph at lines 2495--2495
>  []@texttt (defmethod initialize-instance :after ((object foo) &key blub))[] |
> [34] [35] [36] [37] [38] [39] [40] [41] Chapter 9 [42] (./contributors.texi
> [43]) (Key (Character) Index) [44] (./slime.kys [45])
> (Command and Function Index) [46] (./slime.fns [47])
> (Variable and Concept Index) [48] (./slime.vrs) [49] )
> (see the transcript file for additional information)
> Output written on slime.dvi (54 pages, 248240 bytes).
> Transcript written on slime.log.
> This is pdfTeX, Version 3.14159

Bug#712325: eukleides: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: eukleides
Version: 1.5.4-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> Making eukleides
> Building parser
> Building lexer
> Making dependencies
> Building circle.o
> Building compiler.o
> Building conic.o
> Building core.o
> Building error.o
> Building function.o
> Building interactive.o
> Building intersection.o
> Building io.o
> Building keywords.o
> Building line.o
> Building locus.o
> Building number.o
> Building point.o
> Building quadrilateral.o
> Building set.o
> Building setting.o
> Building strings.o
> Building symbol.o
> Building test.o
> Building triangle.o
> Building utils.o
> Building variable.o
> Building vector.o
> Building args.o
> Building check.o
> Building draw.o
> Building main.o
> Building parser.tab.o
> Building lex.yy.o
> Linking eukleides
> Making euktopst
> Building parser
> Building lexer
> Making dependencies
> Building circle.o
> Building compiler.o
> Building conic.o
> Building core.o
> Building error.o
> Building function.o
> Building interactive.o
> Building intersection.o
> Building io.o
> Building keywords.o
> Building line.o
> Building locus.o
> Building number.o
> Building point.o
> Building quadrilateral.o
> Building set.o
> Building setting.o
> Building strings.o
> Building symbol.o
> Building test.o
> Building triangle.o
> Building utils.o
> Building variable.o
> Building vector.o
> Building args.o
> Building check.o
> Building draw.o
> Building main.o
> Building parser.tab.o
> Building lex.yy.o
> Linking euktopst
> Making documentation
> Building info pages
> eukleides.texi:9: misplaced {
> eukleides.texi:9: misplaced {
> eukleides.texi:9: misplaced }
> eukleides.texi:9: misplaced }
> eukleides.texi:10: misplaced {
> eukleides.texi:10: misplaced }
> eukleides.texi:12: misplaced {
> eukleides.texi:12: misplaced {
> eukleides.texi:12: misplaced }
> eukleides.texi:12: misplaced }
> eukleides.texi:13: misplaced {
> eukleides.texi:13: misplaced {
> eukleides.texi:13: misplaced }
> eukleides.texi:13: misplaced {
> eukleides.texi:13: misplaced }
> eukleides.texi:13: misplaced }
> eukleides.texi:14: misplaced {
> eukleides.texi:14: misplaced {
> eukleides.texi:14: misplaced }
> eukleides.texi:14: misplaced }
> eukleides.texi:36: warning: redefining Texinfo language command: @LaTeX
> make[2]: *** [eukleides.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/eukleides_1.5.4-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712337: arbtt: FTBFS: hlibrary.setup: At least the following dependencies are missing

[David Suárez]

Source: arbtt
Version: 0.6.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING:  DEB_COMPRESS_EXCLUDE is a 
> deprecated variable
> if test ! -e Setup.lhs -a ! -e Setup.hs; then echo "No setup script found!"; 
> exit 1; fi
> for setup in Setup.lhs Setup.hs; do if test -e $setup; then ghc --make $setup 
> -o debian/hlibrary.setup; exit 0; fi; done
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> debian/hlibrary.setup configure --ghc -v2 \
>   --prefix=/usr --libdir=/usr/lib/haskell-packages/ghc/lib \
>   --builddir=dist-ghc \
>   --haddockdir=/usr/lib/ghc-doc/haddock/arbtt-0.6.2/ \
>   --htmldir=/usr/share/doc/libghc-arbtt-doc/html/   \
>  
> Configuring arbtt-0.6.2...
> hlibrary.setup: At least the following dependencies are missing:
> base ==4.5.*
> make: *** [dist-ghc] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/arbtt_0.6.2-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712336: stumpwm: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: stumpwm
Version: 1:20110819.gitca08e08-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> 0 errors, 0 warnings
> ;; Loading file /«PKGBUILDDIR»/manual.fas ...
> ;; Loaded file /«PKGBUILDDIR»/manual.fas
> T
> NIL
> Bye.
> makeinfo stumpwm.texi
> stumpwm.texi:345: @itemx must follow @item
> make[1]: *** [stumpwm.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/stumpwm_20110819.gitca08e08-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712341: octave-fixed: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: octave-fixed
Version: 0.7.10-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> cd doc/ && makeinfo fixed.texi
> fixed.texi:4: @include: could not find fixedversion.txi
> fixed.texi:17: warning: undefined flag: VERSION
> fixed.texi:3456: warning: @end should only appear at a line beginning
> fixed.texi:3276: raising the section level of @subsection which is too low
> make: *** [build/octave-fixed] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/octave-fixed_0.7.10-5_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712343: bnd: FTBFS: [javac] /«PKGBUILDDIR»/biz.aQute.bnd/src/aQute/bnd/ant/WrapTask.java:45: cannot find symbol

[David Suárez]

Source: bnd
Version: 1.50.0-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> cd /«PKGBUILDDIR» && /usr/lib/jvm/default-java/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/ant.jar:/usr/share/java/junit.jar:/usr/lib/jvm/default-java/lib/tools.jar
>   -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
> -Dcompile.optimize=true   -buildfile /«PKGBUILDDIR»/debian/bootstrap.xml 
> -propertyfile /«PKGBUILDDIR»/debian/ant.properties
> Buildfile: /«PKGBUILDDIR»/debian/bootstrap.xml
> 
> bootstrap:
> [mkdir] Created dir: /«PKGBUILDDIR»/bootstrap/build
> [javac] /«PKGBUILDDIR»/debian/bootstrap.xml:14: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 215 source files to /«PKGBUILDDIR»/bootstrap/build
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:127: 
> warning: unmappable character for encoding ASCII
> [javac]  * 8.1.3.5) as a sender's option. NOTE ??? The short form can 
> only be used if
> [javac]^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:127: 
> warning: unmappable character for encoding ASCII
> [javac]  * 8.1.3.5) as a sender's option. NOTE ??? The short form can 
> only be used if
> [javac] ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:127: 
> warning: unmappable character for encoding ASCII
> [javac]  * 8.1.3.5) as a sender's option. NOTE ??? The short form can 
> only be used if
> [javac]  ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:138: 
> warning: unmappable character for encoding ASCII
> [javac]  * 2 shall not be used. ISO/IEC 8825-1:2003 (E) NOTE 
> 1 ??? This
> [javac]   
>  ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:138: 
> warning: unmappable character for encoding ASCII
> [javac]  * 2 shall not be used. ISO/IEC 8825-1:2003 (E) NOTE 
> 1 ??? This
> [javac]   
>   ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:138: 
> warning: unmappable character for encoding ASCII
> [javac]  * 2 shall not be used. ISO/IEC 8825-1:2003 (E) NOTE 
> 1 ??? This
> [javac]   
>^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:145: 
> warning: unmappable character for encoding ASCII
> [javac]  * bit. EXAMPLE L = 201 can be encoded as: 10012 
> 110010012 NOTE 2 ??? In
> [javac]   
> ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:145: 
> warning: unmappable character for encoding ASCII
> [javac]  * bit. EXAMPLE L = 201 can be encoded as: 10012 
> 110010012 NOTE 2 ??? In
> [javac]   
>  ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:145: 
> warning: unmappable character for encoding ASCII
> [javac]  * bit. EXAMPLE L = 201 can be encoded as: 10012 
> 110010012 NOTE 2 ??? In
> [javac]   
>   ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:155: 
> warning: unmappable character for encoding ASCII
> [javac]  * value as specified in subsequent clauses. NOTE ??? The 
> contents octets
> [javac]   ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:155: 
> warning: unmappable character for encoding ASCII
> [javac]  * value as specified in subsequent clauses. NOTE ??? The 
> contents octets
> [javac]^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:155: 
> warning: unmappable character for encoding ASCII
> [javac]  * value as specified in subsequent clauses. NOTE ??? The 
> contents octets
> [javac] ^
> [javac] /«PKGBUILDDIR»/aQute.libg/src/aQute/libg/asn1/BER.java:160: 
> warning: unmappable character for encoding ASCII
> [javac]  * end-of-contents octets shall consist of two zero octets. 
> NOTE ??? The
> [javac]  

Bug#712335: kbuild: FTBFS: /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/config/missing: line 81: makeinfo: command not found

[David Suárez]

Source: kbuild
Version: 1:0.1.9998svn2577+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory 
> `/«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/out/linux.amd64/release/bootstrap/sed/doc'
> Updating /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/version.texi
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/config/missing makeinfo 
> --version) >/dev/null 2>&1; then \
> for f in /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.info 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.info-[0-9] 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.info-[0-9][0-9] 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.i[0-9] 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if /bin/bash 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/config/missing makeinfo   -I 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc \
>-o /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.info 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.texi; \
>   then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc; \
>   else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd 
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc && \
> $restore $backupdir/* `echo 
> ".//«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.info" | sed 
> 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> /«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/config/missing: line 81: 
> makeinfo: command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> make[5]: *** [/«BUILDDIR»/kbuild-0.1.9998svn2577+dfsg/src/sed/doc/sed.info] 
> Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/kbuild_0.1.9998svn2577+dfsg-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712340: monotone: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: monotone
Version: 1.0-8
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/doc'
> rm -rf monotone.htp
> if /bin/bash /«PKGBUILDDIR»/missing --run makeinfo --html -I ../src -I . 
> --number-sections --no-split --no-headers --css-ref=texinfo.css  -I . \
>-o monotone.htp monotone.texi; \
>   then \
> rm -rf monotone.html; \
> if test ! -d monotone.htp && test -d monotone; then \
>   mv monotone monotone.html; else mv monotone.htp monotone.html; fi; \
>   else \
> if test ! -d monotone.htp && test -d monotone; then \
>   rm -rf monotone; else rm -Rf monotone.htp monotone.html; fi; \
> exit 1; \
>   fi
> monotone.texi:4782: @itemx must follow @item
> monotone.texi:6153: @itemx must follow @item
> monotone.texi:12100: warning: @item missing argument
> ./pcrepattern.texi:77: warning: @itemx should not begin @table
> ./pcrepattern.texi:79: @itemx must follow @item
> ./pcrepattern.texi:81: @itemx must follow @item
> ./pcrepattern.texi:83: @itemx must follow @item
> ./pcrepattern.texi:85: @itemx must follow @item
> ./pcrepattern.texi:87: @itemx must follow @item
> ./pcrepattern.texi:89: @itemx must follow @item
> ./pcrepattern.texi:91: @itemx must follow @item
> ./pcrepattern.texi:93: @itemx must follow @item
> ./pcrepattern.texi:97: @itemx must follow @item
> ./pcrepattern.texi:99: @itemx must follow @item
> ./pcrepattern.texi:102: @itemx must follow @item
> ./pcrepattern.texi:111: warning: @itemx should not begin @table
> ./pcrepattern.texi:113: @itemx must follow @item
> ./pcrepattern.texi:115: @itemx must follow @item
> ./pcrepattern.texi:117: @itemx must follow @item
> ./pcrepattern.texi:120: @itemx must follow @item
> ./pcrepattern.texi:162: warning: @itemx should not begin @table
> ./pcrepattern.texi:164: @itemx must follow @item
> ./pcrepattern.texi:166: @itemx must follow @item
> ./pcrepattern.texi:168: @itemx must follow @item
> ./pcrepattern.texi:170: @itemx must follow @item
> ./pcrepattern.texi:172: @itemx must follow @item
> ./pcrepattern.texi:174: @itemx must follow @item
> ./pcrepattern.texi:176: @itemx must follow @item
> ./pcrepattern.texi:178: @itemx must follow @item
> ./pcrepattern.texi:180: @itemx must follow @item
> ./pcrepattern.texi:247: warning: @itemx should not begin @table
> ./pcrepattern.texi:249: @itemx must follow @item
> ./pcrepattern.texi:252: @itemx must follow @item
> ./pcrepattern.texi:254: @itemx must follow @item
> ./pcrepattern.texi:257: @itemx must follow @item
> ./pcrepattern.texi:259: @itemx must follow @item
> ./pcrepattern.texi:261: @itemx must follow @item
> ./pcrepattern.texi:264: @itemx must follow @item
> ./pcrepattern.texi:267: @itemx must follow @item
> ./pcrepattern.texi:297: warning: @itemx should not begin @table
> ./pcrepattern.texi:299: @itemx must follow @item
> ./pcrepattern.texi:301: @itemx must follow @item
> ./pcrepattern.texi:303: @itemx must follow @item
> ./pcrepattern.texi:305: @itemx must follow @item
> ./pcrepattern.texi:307: @itemx must follow @item
> ./pcrepattern.texi:309: @itemx must follow @item
> ./pcrepattern.texi:311: @itemx must follow @item
> ./pcrepattern.texi:313: @itemx must follow @item
> ./pcrepattern.texi:315: @itemx must follow @item
> ./pcrepattern.texi:345: warning: @itemx should not begin @table
> ./pcrepattern.texi:347: @itemx must follow @item
> ./pcrepattern.texi:349: @itemx must follow @item
> ./pcrepattern.texi:351: @itemx must follow @item
> ./pcrepattern.texi:353: @itemx must follow @item
> ./pcrepattern.texi:357: @itemx must follow @item
> ./pcrepattern.texi:359: @itemx must follow @item
> ./pcrepattern.texi:361: @itemx must follow @item
> ./pcrepattern.texi:363: @itemx must follow @item
> ./pcrepattern.texi:365: @itemx must follow @item
> ./pcrepattern.texi:367: @itemx must follow @item
> ./pcrepattern.texi:371: @itemx must follow @item
> ./pcrepattern.texi:373: @itemx must follow @item
> ./pcrepattern.texi:375: @itemx must follow @item
> ./pcrepattern.texi:377: @itemx must follow @item
> ./pcrepattern.texi:379: @itemx must follow @item
> ./pcrepattern.texi:381: @itemx must follow @item
> ./pcrepattern.texi:389: warning: @itemx should not begin @table
> ./pcrepattern.texi:391: @itemx must follow @item
> ./pcrepattern.texi:393: @itemx must follow @item
> ./pcrepattern.texi:395: @itemx must follow @item
> ./pcrepattern.texi:397: @itemx must follow @item
> ./pcrepattern.texi:399: @itemx must follow @item
> ./pcrepattern.texi:401: @itemx must follow @item
> ./pcrepattern.texi:421: warning: @itemx should not begin @table
> ./pcrepattern.texi:423: @itemx must follow @item
> ./pcrepattern.texi:425: @itemx must follow @item
> ./pcrepattern.texi:427: @itemx must follow @item
> ./pcrepattern.texi:429: @itemx must follow @item
> .

Bug#712338: gnugo: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: gnugo
Version: 3.8-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[4]: Entering directory `/«PKGBUILDDIR»/doc'
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && cd . && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash /«PKGBUILDDIR»/missing --run makeinfo --version) 
> >/dev/null 2>&1; then \
> for f in gnugo.info gnugo.info-[0-9] gnugo.info-[0-9][0-9] 
> gnugo.i[0-9] gnugo.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if /bin/bash /«PKGBUILDDIR»/missing --run makeinfo   -I . \
>-o gnugo.info gnugo.texi; \
>   then \
> rc=0; \
> cd .; \
>   else \
> rc=$?; \
> cd . && \
> $restore $backupdir/* `echo "./gnugo.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> gnugo.texi:29: misplaced {
> gnugo.texi:29: misplaced }
> ./reading.texi:126: warning: @findex should only appear at a line beginning
> ./montecarlo.texi:248: raising the section level of @subsection which is too 
> low
> gnugo.texi:159: warning: node next `Patterns' in menu `Tactical Reading' and 
> in sectioning `DFA' differ
> gnugo.texi:164: warning: node next `DFA' in menu `Utility Functions' and in 
> sectioning `Tactical Reading' differ
> gnugo.texi:164: warning: node prev `DFA' in menu `SGF' and in sectioning 
> `Patterns' differ
> gnugo.texi:169: warning: node prev `Tactical Reading' in menu `Patterns' and 
> in sectioning `DFA' differ
> gnugo.texi:193: warning: node next `SGF' in menu `DFA' and in sectioning 
> `API' differ
> gnugo.texi:198: warning: node next `API' in menu `GTP' and in sectioning 
> `Utility Functions' differ
> gnugo.texi:198: warning: node prev `API' in menu `Utility Functions' and in 
> sectioning `SGF' differ
> gnugo.texi:203: warning: node next `Utility Functions' in menu `API' and in 
> sectioning `GTP' differ
> gnugo.texi:203: warning: node prev `Utility Functions' in menu `DFA' and in 
> sectioning `API' differ
> gnugo.texi:208: warning: node prev `GTP' in menu `API' and in sectioning 
> `Utility Functions' differ
> make[4]: *** [gnugo.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/gnugo_3.8-5_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712348: ht: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: ht
Version: 2.0.20-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/doc'
> /bin/bash /«PKGBUILDDIR»/missing --run makeinfo --no-split --fill-column=64 
> --output hthelp.info ht.texi
> ht.texi:54: misplaced {
> ht.texi:54: misplaced }
> ht.texi:55: misplaced {
> ht.texi:55: misplaced }
> ht.texi:57: misplaced {
> ht.texi:57: misplaced }
> ht.texi:139: bad syntax for @macro argument: _table_columns
> ht.texi:139: warning: redefining Texinfo language command: @key
> ht.texi:372: warning: @itemize has text but no @item
> ht.texi:383: warning: @itemize has text but no @item
> make[3]: *** [hthelp.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/ht_2.0.20-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712345: binutils-m68hc1x: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: binutils-m68hc1x
Version: 1:2.18-3.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/build/bfd/doc'
> x86_64-linux-gnu-gcc -o chew.$$ ../../../binutils-2.18/bfd/doc/chew.c \
> -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -U_FORTIFY_SOURCE   \
> -I.. -I../../../binutils-2.18/bfd/doc/.. 
> -I../../../binutils-2.18/bfd/doc/../../include 
> -I../../../binutils-2.18/bfd/doc/../../intl -I../../intl; \
>   /bin/bash ../../../binutils-2.18/bfd/doc/../../move-if-change chew.$$ 
> chew
> ../../../binutils-2.18/bfd/doc/chew.c: In function 'print_stack_level':
> ../../../binutils-2.18/bfd/doc/chew.c:476:3: warning: format '%d' expects 
> argument of type 'int', but argument 3 has type 'long int' [-Wformat]
> ../../../binutils-2.18/bfd/doc/chew.c:477:3: warning: format '%d' expects 
> argument of type 'int', but argument 3 has type 'long int' [-Wformat]
> ../../../binutils-2.18/bfd/doc/chew.c: In function 'main':
> ../../../binutils-2.18/bfd/doc/chew.c:1564:9: warning: format '%d' expects 
> argument of type 'int', but argument 3 has type 'long int' [-Wformat]
> make[5]: Leaving directory `/«PKGBUILDDIR»/build/bfd/doc'
> ./chew -f ../../../binutils-2.18/bfd/doc/doc.str 
> <../../../binutils-2.18/bfd/doc/../elf.c >elf.tmp
> /bin/bash ../../../binutils-2.18/bfd/doc/../../move-if-change elf.tmp elf.texi
> restore=: && backupdir=".am$$" && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/«PKGBUILDDIR»/binutils-2.18/missing makeinfo --split-size=500 
> --split-size=500 --version) >/dev/null 2>&1; then \
> for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
> bfd.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   if /«PKGBUILDDIR»/binutils-2.18/missing makeinfo --split-size=500 
> --split-size=500   -I ../../../binutils-2.18/bfd/doc \
>-o bfd.info `test -f 'bfd.texinfo' || echo 
> '../../../binutils-2.18/bfd/doc/'`bfd.texinfo; \
>   then \
> rc=0; \
>   else \
> rc=$?; \
> $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> WARNING: `makeinfo' is missing on your system.  You should only need it if
>  you modified a `.texi' or `.texinfo' file, or any other file
>  indirectly affecting the aspect of the manual.  The spurious
>  call might also be the consequence of using a buggy `make' (AIX,
>  DU, IRIX).  You might want to install the `Texinfo' package or
>  the `GNU make' package.  Grab either from any GNU archive site.
> make[4]: *** [bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-m68hc1x_2.18-3.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712346: remake: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: remake
Version: 3.82+dbg0.9+dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«BUILDDIR»/remake-3.82+dbg0.9+dfsg/doc'
> Updating ./version-remake.texi
> restore=: && backupdir=".am$$" && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash /«BUILDDIR»/remake-3.82+dbg0.9+dfsg/config/missing 
> makeinfo --version) >/dev/null 2>&1; then \
> for f in remake.info remake.info-[0-9] remake.info-[0-9][0-9] 
> remake.i[0-9] remake.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   if /bin/bash /«BUILDDIR»/remake-3.82+dbg0.9+dfsg/config/missing 
> makeinfo   -I . \
>-o remake.info `test -f 'remake.texi' || echo './'`remake.texi; \
>   then \
> rc=0; \
>   else \
> rc=$?; \
> $restore $backupdir/* `echo "./remake.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> remake.texi:2390: warning: @table has text but no @item
> remake.texi:2755: unknown command `colophon'
> remake.texi:2767: unknown command `cygnus'
> remake.texi:1085: warning: multiple @menu
> make[3]: *** [remake.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/remake_3.82+dbg0.9+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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712351: binutils-avr: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: binutils-avr
Version: 2.20.1-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/src/bfd/doc'
> make[5]: `chew' is up to date.
> make[5]: Leaving directory `/«PKGBUILDDIR»/src/bfd/doc'
> ./chew -f ./doc.str <./../targets.c >targets.tmp
> /bin/bash ./../../move-if-change targets.tmp targets.texi
> restore=: && backupdir=".am$$" && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (makeinfo --split-size=500 --split-size=500 --version) 
> >/dev/null 2>&1; then \
> for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
> bfd.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   if makeinfo --split-size=500 --split-size=500   -I . \
>-o bfd.info `test -f 'bfd.texinfo' || echo './'`bfd.texinfo; \
>   then \
> rc=0; \
>   else \
> rc=$?; \
> $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> bfd.texinfo:325: unknown command `colophon'
> bfd.texinfo:336: unknown command `cygnus'
> make[4]: *** [bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-avr_2.20.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712347: binutils-mingw-w64: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: binutils-mingw-w64
Version: 2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/build/i686-w64-mingw32/bfd/doc'
> make[5]: `chew' is up to date.
> make[5]: Leaving directory `/«PKGBUILDDIR»/build/i686-w64-mingw32/bfd/doc'
> ./chew -f ../../../../upstream/bfd/doc/doc.str 
> <../../../../upstream/bfd/doc/../linker.c >linker.tmp
> /bin/bash ../../../../upstream/bfd/doc/../../move-if-change linker.tmp 
> linker.texi
> restore=: && backupdir=".am$$" && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (makeinfo --split-size=500 --split-size=500 --version) 
> >/dev/null 2>&1; then \
> for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
> bfd.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   if makeinfo --split-size=500 --split-size=500   -I 
> ../../../../upstream/bfd/doc \
>-o bfd.info `test -f 'bfd.texinfo' || echo 
> '../../../../upstream/bfd/doc/'`bfd.texinfo; \
>   then \
> rc=0; \
>   else \
> rc=$?; \
> $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> ../../../../upstream/bfd/doc/bfd.texinfo:325: unknown command `colophon'
> ../../../../upstream/bfd/doc/bfd.texinfo:336: unknown command `cygnus'
> make[4]: *** [bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-mingw-w64_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712349: cdk: FTBFS: This CDK release requires Ant 1.7.1 or better

[David Suárez]

Source: cdk
Version: 1:1.2.10-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> jh_linkjars
> jh_build -J   
> touch debian/jh_build_stamp
> cd . && /usr/lib/jvm/default-java/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/ant-contrib.jar:/usr/share/java/javacc.jar:/usr/lib/jvm/default-java/lib/tools.jar
>   -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
> -Dcompile.optimize=true -Dlib=/usr/share/java   -propertyfile 
> /«PKGBUILDDIR»/debian/ant.properties info dist-all
> Buildfile: /«PKGBUILDDIR»/build.xml
> 
> checkPlatforms:
> 
> check:
> 
> BUILD FAILED
> /«PKGBUILDDIR»/build.xml:204: This CDK release requires Ant 1.7.1 or better.
> 
> Total time: 1 second
> make: *** [debian/stamp-ant-build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/cdk_1.2.10-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712344: cfi: FTBFS: Package babel Error: Unknow option `swedish'. Either you misspelled it

[David Suárez]

Source: cfi
Version: 3.0-9
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe you need the depend on texlive-lang-swedish package ?

Relevant part:
>  debian/rules build
> dh_testdir
> cd sv && latex cfi
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./cfi.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: Unknow option `swedish'. Either you misspelled it
> (babel)or the language definition file swedish.ldf was not 
> foun
> d.
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> No pages of output.
> Transcript written on cfi.log.
> make: *** [build-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/cfi_3.0-9_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#709915: libgdk-pixbuf2.0-0: gdk_pixbuf_new_from_file_at_scale() fails to scale xpm images

[falconbird]

Package: gdk-pixbuf
Followup-For: Bug #709915

Dear Maintainer,

Thanks for forwarding this bug, but it seems that developers are ignoring
this. Please, could you apply this patch in debian build.

https://bug686514.bugzilla-attachments.gnome.org/attachment.cgi?id=244569 .

There are some similar reports on Launchpad about breaking some functiona-
lity and some people must hold the wheezy version of packege, that is not
good. I think that patch is simple enough to be included.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712350: auto-multiple-choice: FTBFS: Package babel Error: Unknow option `french'

[David Suárez]

Source: auto-multiple-choice
Version: 1.2.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe you need the depend on texlive-lang-french package ?

Relevant part:
> Transcript written on auto-multiple-choice.en.log.
> rm -f auto-multiple-choice.en.aux auto-multiple-choice.en.cb 
> auto-multiple-choice.en.cb2 auto-multiple-choice.en.glo 
> auto-multiple-choice.en.idx auto-multiple-choice.en.log 
> auto-multiple-choice.en.out auto-multiple-choice.en.toc
> dblatex -t tex --xslt-opts="--nonet" --xslt-opts="--catalogs"  
> auto-multiple-choice.fr.xml -o auto-multiple-choice.fr.tex
> Build the book set list...
> Variable $SGML_CATALOG_FILES not set
> Build the listings...
> Variable $SGML_CATALOG_FILES not set
> Variable $SGML_CATALOG_FILES not set
> XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3)
> ===
> 'auto-multiple-choice.fr.tex' successfully built
> perl addlink.pl auto-multiple-choice.fr.tex
> case auto-multiple-choice.fr.tex in \
> *.ja.tex) platex auto-multiple-choice.fr.tex; platex 
> auto-multiple-choice.fr.tex; dvipdf auto-multiple-choice.fr.dvi ;; \
> *.tex) pdflatex auto-multiple-choice.fr.tex; pdflatex 
> auto-multiple-choice.fr.tex ;; \
>   esac
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./auto-multiple-choice.fr.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/fancybox/fancybox.sty
> Style option: `fancybox' v1.4 <2010/05/15> (tvz)
> ) (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: Unknow option `french'. Either you misspelled it
> (babel)or the language definition file french.ldf was not 
> found
> .
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on auto-multiple-choice.fr.log.
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./auto-multiple-choice.fr.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/fancybox/fancybox.sty
> Style option: `fancybox' v1.4 <2010/05/15> (tvz)
> ) (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: Unknow option `french'. Either you misspelled it
> (babel)or the language definition file french.ldf was not 
> found
> .
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on auto-multiple-choice.fr.log.
> make[2]: *** [auto-multiple-choice.fr.pdf] Error 1

The full buil

Bug#712353: speechd-el: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: speechd-el
Version: 2.5-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> dh_testdir
> /usr/bin/make info info-cs
> make[1]: Entering directory `/«PKGBUILDDIR»'
> make[1]: Nothing to be done for `info'.
> makeinfo speechd-el.cs.texi
> speechd-el.cs.texi:2: misplaced {
> speechd-el.cs.texi:2: misplaced }
> ./fdl.texi:404: raising the section level of @appendixsubsec which is too low
> make[1]: *** [speechd-el.cs.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/speechd-el_2.5-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712361: cln: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: cln
Version: 1.3.2-1.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/doc'
> rm -rf cln.htp
> if /bin/bash /«PKGBUILDDIR»/autoconf/missing --run makeinfo --html --no-split 
>  -I . \
>-o cln.htp cln.texi; \
>   then \
> rm -rf cln.html; \
> if test ! -d cln.htp && test -d cln; then \
>   mv cln cln.html; else mv cln.htp cln.html; fi; \
>   else \
> if test ! -d cln.htp && test -d cln; then \
>   rm -rf cln; else rm -Rf cln.htp cln.html; fi; \
> exit 1; \
>   fi
> cln.texi:3285: @itemx must follow @item
> cln.texi:392: warning: node `Cleaning up' is prev for `C++ compiler' in menu 
> but not in sectioning
> cln.texi:417: warning: node `Using the GNU MP Library' is next for `Sed 
> utility' in menu but not in sectioning
> cln.texi:539: warning: node `Exact numbers' is next for `Using the GNU MP 
> Library' in menu but not in sectioning
> cln.texi:539: warning: node `Sed utility' is prev for `Using the GNU MP 
> Library' in menu but not in sectioning
> cln.texi:591: warning: node `C++ compiler' is next for `Cleaning up' in menu 
> but not in sectioning
> cln.texi:679: warning: node `Using the GNU MP Library' is prev for `Exact 
> numbers' in menu but not in sectioning
> cln.texi:808: warning: node `Constructing numbers' is next for `Conversions' 
> in menu but not in sectioning
> cln.texi:945: warning: node `Conversions' is prev for `Constructing numbers' 
> in menu but not in sectioning
> cln.texi:958: warning: node `Modifying operators' is prev for `Constructing 
> integers' in menu but not in sectioning
> cln.texi:1000: warning: node `Exponential and logarithmic functions' is next 
> for `Constructing complex numbers' in menu but not in sectioning
> cln.texi:1548: warning: node `Constructing complex numbers' is prev for 
> `Exponential and logarithmic functions' in menu but not in sectioning
> cln.texi:1902: warning: node `Logical functions' is next for `Riemann zeta' 
> in menu but not in sectioning
> cln.texi:1932: warning: node `Riemann zeta' is prev for `Logical functions' 
> in menu but not in sectioning
> cln.texi:2211: warning: node `Conversion to floating-point numbers' is next 
> for `Combinatorial functions' in menu but not in sectioning
> cln.texi:2356: warning: node `Combinatorial functions' is prev for 
> `Conversion to floating-point numbers' in menu but not in sectioning
> cln.texi:2426: warning: node `Internal and printed representation' is next 
> for `Conversion to rational numbers' in menu but not in sectioning
> cln.texi:2512: warning: node `Constructing integers' is next for `Modifying 
> operators' in menu but not in sectioning
> cln.texi:2586: warning: node `Conversion to rational numbers' is prev for 
> `Internal and printed representation' in menu but not in sectioning
> cln.texi:2735: warning: node `Modular integer rings' is next for `Output 
> functions' in menu but not in sectioning
> cln.texi:2913: warning: node `Output functions' is prev for `Modular integer 
> rings' in menu but not in sectioning
> cln.texi:2973: warning: node `Strings' is next for `Functions on modular 
> integers' in menu but not in sectioning
> cln.texi:3099: warning: node `Functions on modular integers' is prev for 
> `Strings' in menu but not in sectioning
> cln.texi:3148: warning: node `Univariate polynomial rings' is next for 
> `Symbols' in menu but not in sectioning
> cln.texi:3191: warning: node `Symbols' is prev for `Univariate polynomial 
> rings' in menu but not in sectioning
> cln.texi:3432: warning: node `Why C++ ?' is next for `Special polynomials' in 
> menu but not in sectioning
> cln.texi:3474: warning: node `Special polynomials' is prev for `Why C++ ?' in 
> menu but not in sectioning
> cln.texi:3582: warning: node `Compiler options' is next for `Garbage 
> collection' in menu but not in sectioning
> cln.texi:3618: warning: node `Garbage collection' is prev for `Compiler 
> options' in menu but not in sectioning
> cln.texi:3944: warning: node `Error handling' is next for `Reporting 
> Problems' in menu but not in sectioning
> cln.texi:3970: warning: node `Reporting Problems' is prev for `Error 
> handling' in menu but not in sectioning
> make[1]: *** [cln.html] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/cln_1.3.2-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-r

Bug#712356: cairo-dock: FTBFS: A required package was not found

[David Suárez]

Source: cairo-dock
Version: 3.1.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> cd obj-x86_64-linux-gnu && cmake /«PKGBUILDDIR»/. 
> -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_C_COMPILER:FILEPATH="cc" 
> -DCMAKE_CXX_COMPILER:FILEPATH="g++" -DCMAKE_C_FLAGS="-g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2" -DCMAKE_CXX_FLAGS="-g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2" -DCMAKE_SKIP_RPATH=ON 
> -DCMAKE_VERBOSE_MAKEFILE=ON 
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.26") 
> -- The C compiler identification is GNU 4.7.3
> -- The CXX compiler identification is GNU 4.7.3
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/g++
> -- Check for working CXX compiler: /usr/bin/g++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- checking for modules 
> 'glib-2.0;gthread-2.0;cairo;librsvg-2.0;dbus-1;dbus-glib-1;libxml-2.0;xrender;gl;glu;pangox;libcurl'
> --   package 'pangox' not found
> CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:279 (message):
>   A required package was not found
> Call Stack (most recent call first):
>   /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:333 
> (_pkg_check_modules_internal)
>   CMakeLists.txt:78 (pkg_check_modules)
> 
> 
> -- checking for modules 'xtst;xcomposite;xinerama;xrandr'
> --   found xtst, version 1.2.1
> --   found xcomposite, version 0.4.3
> --   found xinerama, version 1.1.2
> --   found xrandr, version 1.3.2
> -- checking for module 'gtk+-3.0'
> --   found gtk+-3.0, version 3.8.2
> -- Looking for encrypt in crypt
> -- Looking for encrypt in crypt - found
> -- Looking for LC_MESSAGES
> -- Looking for LC_MESSAGES - found
> -- Looking for include file math.h
> -- Looking for include file math.h - found
> -- Looking for sin in m
> -- Looking for sin in m - found
> -- Looking for include file dlfcn.h
> -- Looking for include file dlfcn.h - found
> -- Looking for dlopen in dl
> -- Looking for dlopen in dl - found
> -- Building cairo-dock_en.1.gz
> --   Building hu.gmo...
> --   Building sk.gmo...
> --   Building ca.gmo...
> --   Building be.gmo...
> --   Building sr.gmo...
> --   Building ja.gmo...
> --   Building fi.gmo...
> --   Building eu.gmo...
> --   Building ko.gmo...
> --   Building it.gmo...
> --   Building ru.gmo...
> --   Building cy.gmo...
> --   Building cs.gmo...
> --   Building de.gmo...
> --   Building uk.gmo...
> --   Building he.gmo...
> --   Building gl.gmo...
> --   Building lt.gmo...
> --   Building ar.gmo...
> --   Building oc.gmo...
> --   Building sv.gmo...
> --   Building es.gmo...
> --   Building sl.gmo...
> --   Building bn.gmo...
> --   Building eo.gmo...
> --   Building ro.gmo...
> --   Building fr.gmo...
> --   Building el.gmo...
> --   Building nb.gmo...
> --   Building vi.gmo...
> --   Building id.gmo...
> --   Building tr.gmo...
> --   Building en.gmo...
> --   Building zh_CN.gmo...
> --   Building pt.gmo...
> --   Building nl.gmo...
> --   Building pl.gmo...
> --   Building zh_TW.gmo...
> --   Building et.gmo...
> --   Building fo.gmo...
> --   Building pt_BR.gmo...
> -- 
> -- Cairo-Dock 3.1.1 will be compiled with the following options:
> --  * Use X Extensions: Yes
> --  * Crypt passwords : Yes
> --  * GTK version : 3 (3.8.2)
> --  * Installation in : /usr
> --  * Lib directory   : /usr/lib
> --  * Themes directory: themes3.1
> -- 
> -- Configuring incomplete, errors occurred!
> make: *** [obj-x86_64-linux-gnu/CMakeCache.txt] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/cairo-dock_3.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712352: sml-mode: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: sml-mode
Version: 4.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> echo "\
>   ;;; sml-mode-startup.el --- automatically extracted autoloads\n\
>   ;;; Code:\n\
>   (add-to-list 'load-path\n\
>(or (file-name-directory load-file-name) (car 
> load-path)))\n\
>   " >sml-mode-startup.el
> emacs --batch --eval '(setq generated-autoload-file 
> "'`pwd`'/sml-mode-startup.el")' -f batch-update-autoloads "."
> Loading 00debian-vars...
> Generating autoloads for sml-compat.el...
> Generating autoloads for sml-compat.el...done
> Generating autoloads for sml-defs.el...
> Generating autoloads for sml-defs.el...done
> Generating autoloads for sml-mode.el...
> Generating autoloads for sml-mode.el...done
> Generating autoloads for sml-move.el...
> Generating autoloads for sml-move.el...done
> Generating autoloads for sml-proc.el...
> Generating autoloads for sml-proc.el...done
> Generating autoloads for sml-util.el...
> Generating autoloads for sml-util.el...done
> Saving file /«PKGBUILDDIR»/sml-mode-startup.el...
> Wrote /«PKGBUILDDIR»/sml-mode-startup.el
> (No changes need to be saved)
> mkdir -p /«PKGBUILDDIR»/debian/sml-mode/usr/share/emacs/site-lisp/sml-mode
> for f in sml-compat.elc sml-util.elc sml-defs.elc sml-move.elc sml-mode.elc 
> sml-proc.elc sml-mode-startup.el; do \
>   cp $f 
> /«PKGBUILDDIR»/debian/sml-mode/usr/share/emacs/site-lisp/sml-mode/$f ;\
>   done
> makeinfo sml-mode.texi
> sml-mode.texi:37: misplaced {
> sml-mode.texi:37: misplaced }
> sml-mode.texi:37: warning: @center missing argument
> sml-mode.texi:38: misplaced {
> sml-mode.texi:38: misplaced }
> sml-mode.texi:38: warning: @center missing argument
> sml-mode.texi:66: warning: multiple @setchapternewpage
> make[1]: *** [sml-mode.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/sml-mode_4.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712354: binutils-msp430: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: binutils-msp430
Version: 2.22~msp20120406-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/binutils-2.21.1/bfd/doc'
> make[5]: `chew' is up to date.
> make[5]: Leaving directory `/«PKGBUILDDIR»/binutils-2.21.1/bfd/doc'
> ./chew -f ./doc.str <./../reloc.c >reloc.tmp
> /bin/bash ./../../move-if-change reloc.tmp reloc.texi
> restore=: && backupdir=".am$$" && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (makeinfo --split-size=500 --split-size=500 --version) 
> >/dev/null 2>&1; then \
> for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
> bfd.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   if makeinfo --split-size=500 --split-size=500   -I . \
>-o bfd.info `test -f 'bfd.texinfo' || echo './'`bfd.texinfo; \
>   then \
> rc=0; \
>   else \
> rc=$?; \
> $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> bfd.texinfo:325: unknown command `colophon'
> bfd.texinfo:336: unknown command `cygnus'
> make[4]: *** [bfd.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/binutils-msp430_2.22~msp20120406-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712358: tetex-brev: FTBFS: Package babel Error: You haven't specified a language option.

[David Suárez]

Source: tetex-brev
Version: 4.22.6+nmu1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«BUILDDIR»/tetex-brev-4.22.6+nmu1'
> latex demo
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./demo.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (./brev.cls
> Document Class: brev 2003/11/18 17:07:55 v4.22 Class for private letters
> (/usr/share/texlive/texmf-dist/tex/latex/base/letter.cls
> Document Class: letter 1999/04/29 v1.2z Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> No file demo.aux.
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1cmtt.fd)
> Underfull \hbox (badness 1) has occurred while \output is active
> []
> [1] (./demo.aux) )
> (see the transcript file for additional information)
> Output written on demo.dvi (1 page, 816 bytes).
> Transcript written on demo.log.
> latex eksempel
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./eksempel.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (./brev.cls
> Document Class: brev 2003/11/18 17:07:55 v4.22 Class for private letters
> (/usr/share/texlive/texmf-dist/tex/latex/base/letter.cls
> Document Class: letter 1999/04/29 v1.2z Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: You haven't specified a language option.
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> No pages of output.
> Transcript written on eksempel.log.
> make[1]: *** [eksempel.dvi] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/tetex-brev_4.22.6+nmu1_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712362: acl2: FTBFS: ls: cannot access bvecs.cert: No such file or directory

[David Suárez]

Source: acl2
Version: 6.1-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>| start address -T 0xc5bbfb0 Finished loading 
> /«PKGBUILDDIR»/books/data-structures/no-duplicates.o
>| start address -T 0x76bb000 Finished loading 
> /«PKGBUILDDIR»/books/clause-processors/witness-cp.o
>| start address -T 0x1c14f60 Finished loading 
> /«PKGBUILDDIR»/books/centaur/misc/witness-cp.o
>| start address -T 0x5f17ce0 Finished loading 
> /«PKGBUILDDIR»/books/centaur/misc/equal-sets.o
>| start address -T 0xf78000 Finished loading 
> /«PKGBUILDDIR»/books/centaur/misc/hons-alphorder-merge.o
>| start address -T 0x78a6920 Finished loading 
> /«PKGBUILDDIR»/books/centaur/aig/base.o
>| start address -T 0x62a5000 Finished loading 
> /«PKGBUILDDIR»/books/centaur/aig/witness.o
>| start address -T 0x770b000 Finished loading 
> /«PKGBUILDDIR»/books/centaur/gl/bfr.o
>| [SGC for 3000 CONS pages..(64194 writable)..(T=2).GC finished]
>| [SGC for 3000 CONS pages..(64299 writable)..(T=2).GC finished]
>| [SGC for 3000 CONS pages..(64367 writable)..(T=2).GC finished]
>| [SGC for 3000 CONS pages..(64739 writable)..(T=3).GC finished]
>| [SGC for 3000 CONS pages..(65292 writable)..(T=2).GC finished]
>| [SGC for 10019 CONS pages..(72757 writable)..(T=4).GC finished]
>| [SGC off]
>| Error: Caught fatal error [memory may be damaged]
>| Fast links are on: do (si::use-fast-links nil) for debugging
>| Error signalled by PROG1.
>| Backtrace: funcall > eval > lp > let* > let > cond > let* > prog1 > 
> ev-rec > system::break-level-for-acl2 > let* > UNLESS
>| ACL2 !>Bye.
>| bvecs.cert seems to be missing
> 
> make: 
> *** [debian/test.log] Error 2
> **CERTIFICATION FAILED** for /«PKGBUILDDIR»/books/centaur/gl/bvecs.lisp
> 
> make[3]: *** [centaur/gl/bvecs.cert] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/acl2_6.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712360: doc-debian-es: FTBFS: Package babel Error: You haven't specified a language option.

[David Suárez]

Source: doc-debian-es
Version: 2.6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/FAQ'
> LC_ALL=es_ES && echo "" > 
> faqdynamic.ent
> debiandoc2html -l es debian-faq-es.sgml
> debiandoc2text -l es debian-faq-es.sgml
> debiandoc2latex -l es debian-faq-es.sgml
> latex debian-faq-es.tex
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./debian-faq-es.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/pifont.sty
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/upzd.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/upsy.fd))
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/wasysym/wasysym.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: You haven't specified a language option.
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> No pages of output.
> Transcript written on debian-faq-es.log.
> make[1]: [debian-faq-es.dvi] Error 1 (ignored)
> latex debian-faq-es.tex
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./debian-faq-es.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/pifont.sty
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/upzd.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/upsy.fd))
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/wasysym/wasysym.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: You haven't specified a language option.
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.326 ...ry to proceed from here, type x to quit.}
>   
> No pages of output.
> Transcript written on debian-faq-es.log.
> make[1]: [debian-faq-es.dvi] Error 1 (ignored)
> latex debian-faq-es.tex
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./debian-faq-es.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))

Bug#712355: xemacs21: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: xemacs21
Version: 21.4.22-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/man'
> makeinfo -o ../info/cl.info cl.texi
> makeinfo -o ../info/custom.info custom.texi
> custom.texi:63: raising the section level of @section which is too low
> make[3]: *** [../info/custom.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/xemacs21_21.4.22-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712359: biojava3-live: FTBFS: [javac] /«PKGBUILDDIR»/biojava3-forester/src/main/java/org/forester/archaeopteryx/PdfExporter.java:93: cannot find symbol

[David Suárez]

Source: biojava3-live
Version: 3.0.5-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> cd biojava3-forester && ant jar
> Buildfile: /«PKGBUILDDIR»/biojava3-forester/build.xml
> 
> compile:
> [mkdir] Created dir: /«PKGBUILDDIR»/build/biojava3-forester/classes
> [mkdir] Created dir: /«PKGBUILDDIR»/dist
> [javac] /«PKGBUILDDIR»/biojava3-forester/build.xml:70: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 332 source files to 
> /«PKGBUILDDIR»/build/biojava3-forester/classes
> [javac] 
> /«PKGBUILDDIR»/biojava3-forester/src/main/java/org/forester/archaeopteryx/PdfExporter.java:42:
>  cannot find symbol
> [javac] symbol  : class DefaultFontMapper
> [javac] location: package com.itextpdf.text.pdf
> [javac] import com.itextpdf.text.pdf.DefaultFontMapper;
> [javac] ^
> [javac] 
> /«PKGBUILDDIR»/biojava3-forester/src/main/java/org/forester/archaeopteryx/PdfExporter.java:93:
>  cannot find symbol
> [javac] symbol  : class DefaultFontMapper
> [javac] location: class org.forester.archaeopteryx.PdfExporter
> [javac] final DefaultFontMapper mapper = new DefaultFontMapper();
> [javac]   ^
> [javac] 
> /«PKGBUILDDIR»/biojava3-forester/src/main/java/org/forester/archaeopteryx/PdfExporter.java:93:
>  cannot find symbol
> [javac] symbol  : class DefaultFontMapper
> [javac] location: class org.forester.archaeopteryx.PdfExporter
> [javac] final DefaultFontMapper mapper = new DefaultFontMapper();
> [javac]  ^
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 3 errors
> 
> BUILD FAILED
> /«PKGBUILDDIR»/biojava3-forester/build.xml:70: Compile failed; see the 
> compiler error output for details.
> 
> Total time: 13 seconds
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/biojava3-live_3.0.5-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712357: packaging-tutorial: FTBFS: Error: Unknow option `german'. Either you misspelled it

[David Suárez]

Source: packaging-tutorial
Version: 0.8
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe you need the depend on texlive-lang-german package ?

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»'
> make[3]: Nothing to be done for `LU_WATCH_FILES_SAVE'.
> make[3]: Leaving directory `/«PKGBUILDDIR»'
>  ==> building  packaging-tutorial.de.pdf <==
> Running: 'pdflatex' '--interaction' 'errorstopmode' '--jobname' 
> 'packaging-tutorial.de' 
> '\RequirePackage[extension=.pdf]{texdepends}\input{packaging-tutorial.de.tex}'
>   
>   
> *
> Building packaging-tutorial.de.pdf fails
> *
> Here are the last lines of the log file
> If this is not enought, try to
> call 'make' with 'VERB=verbose' option
> *
> ==> Last lines in packaging-tutorial.de.log <==
> File: pgfcalendar.code.tex 2007/07/23 v2.10 (rcs-revision 1.11)
> \pgfcalendarcurrentjulian=\count181
> 
> (/usr/share/texlive/texmf-dist/tex/latex/ae/aecompl.sty
> Package: aecompl 1998/07/23 0.9 T1 Complements for AE fonts (D. Roegel)
> ))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> Package: babel 2013/05/16 v3.9f The Babel package
> 
> 
> ! Package babel Error: Unknow option `german'. Either you misspelled it
> (babel)or the language definition file german.ldf was not 
> found
> .
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> make[2]: *** [packaging-tutorial.de.pdf] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/packaging-tutorial_0.8_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712368: vm: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: vm
Version: 8.1.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/info'
> echo @set VERSION 8.1.2 > version.texinfo
> makeinfo  vm.texinfo -o vm.info
> vm.texinfo:786: warning: @end should only appear at a line beginning
> vm.texinfo:2345: warning: superfluous arguments for node
> vm.texinfo:: warning: @vindex should only appear at a line beginning
> vm.texinfo:3337: warning: @vindex should only appear at a line beginning
> vm.texinfo:999: @ref reference to nonexistent node `maildrop
>   specification'
> vm.texinfo:4591: raising the section level of @unnumberedsubsec which is too 
> low
> make[2]: *** [vm.info] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/vm_8.1.2-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712367: bashdb: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: bashdb
Version: 4.2.0.8-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/doc'
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (makeinfo --version) >/dev/null 2>&1; then \
> for f in bashdb.info bashdb.info-[0-9] bashdb.info-[0-9][0-9] 
> bashdb.i[0-9] bashdb.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if makeinfo   -I . \
>-o bashdb.info bashdb.texi; \
>   then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd .; \
>   else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd . && \
> $restore $backupdir/* `echo "./bashdb.info" | sed 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> bashdb.texi:120: unknown command `sourceforge'
> bashdb.texi:4473: unknown command `colophon'
> bashdb.texi:4485: unknown command `cygnus'
> make[3]: *** [bashdb.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/bashdb_4.2.0.8-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712364: octave-communications: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: octave-communications
Version: 1.1.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/doc'
> Making texinfo comms.texi
> Function prbs_sequence, does not contain texinfo help
> Function prbs_generator, does not contain texinfo help
> Function prbs_iterator, does not contain texinfo help
> Making dvi comms.dvi
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./comms.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2013-02-01.11]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.) [1] [2]
> [-1] Chapter 1 Chapter 2 [1] [2] [3]
> (awgn.eps
> )
> [4] [5] [6]
> (eyediagram.eps
> )
> [7]
> (scatterplot.eps
> )
> Chapter 3 [8] [9] Chapter 4 [10] [11] [12] [13] [14] [15] [16] [17] Chapter 5
> [18] Chapter 6 [19] Chapter 7 [20] Chapter 8 [21] [22] [23] [24] [25] [26]
> [27] [28] [29] [30] [31] [32] [33] [34] [35] Chapter 9 [36] [37] [38] [39]
> [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54]
> [55] [56] [57] [58] [59] [60] [61]
> Overfull \hbox (49.59799pt too wide) in paragraph at lines 4286--4286
>  []@texttt c = [1+j -1+j -1-j 1-j 1+sqrt(3) j*(1+sqrt(3)) -1-sqrt(3) 
> -j*(1+sqrt
> (3))];[] |
> [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76]
> [77] [78] [79] [80] [81] [82]
> Overfull \hbox (26.60324pt too wide) in paragraph at lines 5871--5871
>  []@texttt hcode=shannonfanoenco(1:4,hd) #  [ 1   0   1   0   0   0   0   0   
> 1
>  ][] |
> 
> Overfull \hbox (20.85455pt too wide) in paragraph at lines 5921--5921
>  []@texttt shannonfanoenco(1:4,hd) #  [   0   1   0   1   1   0   1   1   1   > 0
> ][] |
> [83] [84] [85] [86] )
> (see the transcript file for additional information)
> Output written on comms.dvi (89 pages, 241756 bytes).
> Transcript written on comms.log.
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./comms.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2013-02-01.11]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.) 
> (./comms.aux)
> [1] [2] (./comms.toc [-1] [-2] [-3]) [-4] Chapter 1 Chapter 2 [1] [2] [3]
> (awgn.eps
> )
> [4] [5] [6]
> (eyediagram.eps
> )
> [7]
> (scatterplot.eps
> )
> Chapter 3 [8] [9] Chapter 4 [10] [11] [12] [13] [14] [15] [16] [17] Chapter 5
> [18] Chapter 6 [19] Chapter 7 [20] Chapter 8 [21] [22] [23] [24] [25] [26]
> [27] [28] [29] [30] [31] [32] [33] [34] [35] Chapter 9 [36] [37] [38] [39]
> [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54]
> [55] [56] [57] [58] [59] [60] [61]
> Overfull \hbox (49.59799pt too wide) in paragraph at lines 4286--4286
>  []@texttt c = [1+j -1+j -1-j 1-j 1+sqrt(3) j*(1+sqrt(3)) -1-sqrt(3) 
> -j*(1+sqrt
> (3))];[] |
> [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76]
> [77] [78] [79] [80] [81] [82]
> Overfull \hbox (26.60324pt too wide) in paragraph at lines 5871--5871
>  []@texttt hcode=shannonfanoenco(1:4,hd) #  [ 1   0   1   0   0   0   0   0   
> 1
>  ][] |
> 
> Overfull \hbox (20.85455pt too wide) in paragraph at lines 5921--5921
>  []@texttt shannonfanoenco(1:4,hd) #  [   0   1   0   1   1   0   1   1   1   > 0
> ][] |
> [83] [84] [85] [86] )
> (see the transcript file for additional information)
> Output written on comms.dvi (92 pages, 308132 bytes).
> Transcript written on comms.log.
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./comms.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2013-02-01.11]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.) 
> (./comms.aux)
> [1] [2] (./comms.toc [-1] [-2] [-3]) [-4] Chapter 1 Chapter 2 [1] [2] [3]
> (awgn.eps
> )
> [4] [5] [6]
> (eyediagram.eps
> )
> [7]
> (scatterplot.eps
> )
> Chapter 3 [8] [9] Chapter 4 [

Bug#712365: e2fsprogs: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)

[David Suárez]

Source: e2fsprogs
Version: 1.42.5-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/debian/BUILD-STD/lib/et'
> makeinfo  /«PKGBUILDDIR»/lib/et/com_err.texinfo -o com_err.info
> /«PKGBUILDDIR»/lib/et/com_err.texinfo:309: warning: missing name for 
> @deftypefun
> /«PKGBUILDDIR»/lib/et/com_err.texinfo:324: warning: missing name for 
> @deftypefun
> /«PKGBUILDDIR»/lib/et/com_err.texinfo:141: raising the section level of 
> @section which is too low
> make[1]: *** [com_err.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/e2fsprogs_1.42.5-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712366: xen: FTBFS: configure: error: Could not find libcrypto

[David Suárez]

Source: xen
Version: 4.2.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»'
> mkdir -p debian/build/build-utils_amd64
> cp -al CODING_STYLE COPYING Config.mk MAINTAINERS Makefile README autogen.sh 
> buildconfigs config configure docs extras install.sh scripts stubdom tools 
> unmodified_drivers version.sh xen debian/build/build-utils_amd64
> cd debian/build/build-utils_amd64; ./configure
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether make sets $(MAKE)... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for bison... no
> checking for flex... no
> checking for perl... /usr/bin/perl
> checking for ocamlc... ocamlc
> OCaml version is 3.12.1
> OCaml library path is /usr/lib/ocaml
> checking for ocamlopt... ocamlopt
> checking for ocamlc.opt... no
> checking for ocamlopt.opt... no
> checking for ocaml... ocaml
> checking for ocamldep... ocamldep
> checking for ocamlmktop... ocamlmktop
> checking for ocamlmklib... ocamlmklib
> checking for ocamldoc... ocamldoc
> checking for ocamlbuild... ocamlbuild
> checking for bash... /bin/bash
> checking for python... /usr/bin/python
> checking for python version >= 2.3 ... yes
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for python-config... /usr/bin/python-config
> checking Python.h usability... yes
> checking Python.h presence... yes
> checking for Python.h... yes
> checking for PyArg_ParseTuple in -lpython2.7... yes
> checking for xgettext... /usr/bin/xgettext
> checking for as86... /usr/bin/as86
> checking for ld86... /usr/bin/ld86
> checking for bcc... /usr/bin/bcc
> checking for iasl... /usr/bin/iasl
> checking uuid/uuid.h usability... yes
> checking uuid/uuid.h presence... yes
> checking for uuid/uuid.h... yes
> checking for uuid_clear in -luuid... yes
> checking uuid.h usability... no
> checking uuid.h presence... no
> checking for uuid.h... no
> checking curses.h usability... yes
> checking curses.h presence... yes
> checking for curses.h... yes
> checking for clear in -lcurses... yes
> checking ncurses.h usability... yes
> checking ncurses.h presence... yes
> checking for ncurses.h... yes
> checking for clear in -lncurses... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for glib... yes
> checking bzlib.h usability... no
> checking bzlib.h presence... no
> checking for bzlib.h... no
> checking lzma.h usability... yes
> checking lzma.h presence... yes
> checking for lzma.h... yes
> checking for lzma_stream_decoder in -llzma... yes
> checking lzo/lzo1x.h usability... no
> checking lzo/lzo1x.h presence... no
> checking for lzo/lzo1x.h... no
> checking for io_setup in -laio... yes
> configure: error: Could not find libcrypto
> checking for MD5 in -lcrypto... no
> make[2]: *** [debian/stamps/setup-utils_amd64] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/09/xen_4.2.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712369: felix-latin: FTBFS: Package babel Error: Unknow option `frenchb'. Either you misspelled it

[David Suárez]

Source: felix-latin
Version: 2.0-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe you need the depend on texlive-lang-french package ?

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/TeX'
> xelatex felix34.tex
> This is XeTeX, Version 3.1415926-2.5-0..3 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (./felix34.tex
> LaTeX2e <2011/06/27>
> Babel <3.9f> and hyphenation patterns for 2 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3names.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3bootstrap.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/etex-pkg/etex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3basics.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3expan.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3tl.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3seq.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3int.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3quark.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3prg.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3clist.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3token.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3prop.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3msg.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3file.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3skip.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3keys.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3fp.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3box.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3coffins.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3color.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3luatex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3candidates.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-patches.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty)
> *
> * LaTeX warning: "xparse/redefine-command"
> * 
> * Redefining document command \oldstylenums with arg. spec. 'm' on line 128.
> *
> ) (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmr.fd))
> (/usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty
> (/usr/share/texmf/tex/latex/tipa/t3enc.def
> (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmss.fd))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)
> (/usr/share/texlive/texmf-dist/tex/xelatex/xetex-def/xetex.def
> (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> 
> ! Package babel Error: Unknow option `frenchb'. Either you misspelled it
> (babel)or the language definition file frenchb.ldf was not 
> foun
> d.
> 
> See the babel package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> ? 
> ! Emergency stop.
>  ...  
>   
> l.293 \ProcessOptions*
>   
> No pages of output.
> Transcript written on felix34.log.
> make[2]: *** [tout] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/f

Bug#711167: Bug#711213: libapache2-mod-perl2: occasional core dumps after the test suite

[Niko Tyni]

On Fri, Jun 14, 2013 at 10:24:07AM +0200, Stefan Fritsch wrote:
 
> The problem is that MP_CMD_SRV_DECLARE2(authz_provider) and 
> MP_CMD_SRV_DECLARE2(authn_provider) register the cleanup against 
> parms->server->process->pool which lives longer than the pconf pool 
> and therefore the load time of the mod-perl shared object. It should 
> probably use parms->pool (which is pconf) instead.

> Now, if there is a good reason that the above functions use server-
> >process->pool, we need to figure out a way to fix that. But the 
> original commit of that code has no comment with respect to the pool 
> requirement. Therefore I think it may be simply a bug and you should 
> test it with a cleanup against pconf, first.

Thanks! The attached patch indeed fixes the problem for me without
introducing any new regressions in the test suite.

@pkg-perl: I'm away from my keys ATM; could somebody please upload
this? The ia64 problem (#711167) is still a mystery but I have high
hopes this at least fixes the armel buildd crashes.
-- 
Niko Tyni   nt...@debian.org
>From 75662f4285bad8d28fe787d1293bdd95a535cad1 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Fri, 14 Jun 2013 14:07:22 +0300
Subject: [PATCH] Make sure authn and authz providers are cleaned up in time

The authn and authz providers need to be registered in the configuration
pool rather than the server process pool.  The latter outlives the load
time of the mod_perl shared object, so cleanup hooks could get called
after the registered functions were unloaded, causing SIGSEGVs and other
undefined behaviour.

Fix suggested by Stefan Fritsch.

Bug-Debian: http://bugs.debian.org/711213
---
 src/modules/perl/modperl_cmd.c |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/modules/perl/modperl_cmd.c b/src/modules/perl/modperl_cmd.c
index 4ae0a62..d14b330 100644
--- a/src/modules/perl/modperl_cmd.c
+++ b/src/modules/perl/modperl_cmd.c
@@ -419,7 +419,7 @@ MP_CMD_SRV_DECLARE(init_handlers)
 
 MP_CMD_SRV_DECLARE2(authz_provider)
 {
-apr_pool_t *p = parms->server->process->pool;
+apr_pool_t *p = parms->pool;
 char *name = apr_pstrdup(p, arg1);
 char *cb = apr_pstrdup(p, arg2);
 
@@ -431,7 +431,7 @@ MP_CMD_SRV_DECLARE2(authz_provider)
 
 MP_CMD_SRV_DECLARE2(authn_provider)
 {
-apr_pool_t *p = parms->server->process->pool;
+apr_pool_t *p = parms->pool;
 char *name = apr_pstrdup(p, arg1);
 char *cb = apr_pstrdup(p, arg2);
 
-- 
1.7.10.4

Bug#712370: apparmor: Please package AppArmor 2.8

[intrigeri]

Package: apparmor
Version: 2.7.103-4
Severity: wishlist

Please package AppArmor 2.8 in Debian.

This bug report is here so that we can mark other bugs are blocked by
this one, track progress, and report initial tests.

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712050: linux: Apparmor not working with kernels after wheezy

[intrigeri]

Control: retitle -1 aa-status does not show loaded profiles
Control: severity -1 normal
Control: tag -1 - moreinfo
Control: block -1 by 712370

Hi,

(Hopefully the reporter's email does not bounce this time.)

> I will try to answer your questions. First, rules are working and AppArmor is 
> blocking access to files.
[...]
> But when I try to run aa-status, I got this 
[...]
> So it isn't showing loaded profiles (actually, I thought that it even not
> shwing profiles, but I mistaken).

Thanks for following-up. I can reproduce this problem on my
sid system.

Now that the actual problem has been better defined, I'm setting the
bug title accordingly, and the severity to something more reasonable.
I should actually have set it to "minor" to be more in line with how
severities are used on this package.

> When I tried to rebuild Ubuntu 2.8 AppArmor
> it also worked but showed me something about 2.4 compitablity patch.

This is useful information, thanks! I've just created a bug to track
2.8 packaging efforts: #712370. Would you please report in
more details your experiences with AppArmor 2.8 on Debian on that
other bug?

Cheers,
-- 
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712245: many segfault occur concerning libglib-2.0.so.0.3200.4

[Takashi Yano]

> What's the output of `ls -l /dev/rfkill' ?

crw-r--r-T+ 1 root root 10, 59 Jun  8 21:18 /dev/rfkill

> What version of udev and kernel do you have?

udev version is:
ii  udev 175-7.2  i386  
   /dev/ and hotplug management daemon

Kernel Version is:
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2+deb7u2 i686 GNU/Linux

Thanks,
Takashi Yano


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#708660: [LCFC] templates://keystone/{keystone.templates}

[Justin B Rye]

Christian PERRIER wrote:
> I'm thinking about translators who need information in order to choose
> the right thing to do.
> 
> I propose the following:
> 
> 
> Template: keystone/create-admin-tenant
> Type: boolean
> Default: false
> # Translators: a "tenant" in OpenStack world is
> # an entity that contains one or more username/password couples. 
> # It's typically the tenant that will be used for billing. Having more than 
> one
> # username/password is very helpful in larger organization.
^s
> # You're advised to either keep "tenant" without translating it
> # or keep it aside with your translation. Example for French:

(By "keep it aside" do you mean "keep it set off by commas"?)

> # propriétaire ("tenant")

"Propriétaire" ("Landlord, owner") might make sense, but the actual
word is "tenant", which equates to "locataire".  I suspect this is one
that's best treated as a meaningless name...

> _Description: Register administration tenants?
>  For OpenStack to work, you need a basic tenant configuration. The
>  creation of these administration tenants can be done automatically.
 
(In fact I had forgotten that for keystone we were talking plural
tenants.)
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#708660: [LCFC] templates://keystone/{keystone.templates}

[Justin B Rye]

Justin B Rye wrote:
> (By "keep it aside" do you mean "keep it set off by commas"?)

I mean "set off by parentheses", obviously.  Or just "parenthesized".
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712050: linux: Apparmor not working with kernels after wheezy

[intrigeri]

intrigeri wrote (15 Jun 2013 11:02:26 GMT) :
> (Hopefully the reporter's email does not bounce this time.)

It still does:

  : host mx.lavabit.com[72.249.41.52] said: 550 This
  account has been locked as a result of inactivity. (in reply to RCPT TO
  command)

falconbird, please do consider using a *working* email address in
here. Otherwise, you're adding unnecessary noise to everyone
involved's mailbox. Thanks in advance :)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712306: libp11-kit0: if gnome-keyring is not installed p11-kit complains on stderr

[Andreas Metzler]

On 2013-06-15 Vaibhav Niku  wrote:
> Package: libp11-kit0
> Version: 0.12-3
> Severity: minor

> Hello

> If I try using mpop (with SSL) to download mail, the terminal is clobbered the
> error:

> ---
> p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-
> pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot
> open shared object file: No such file or directory
> ---

> p11-kit obviously couldn't load the module: none of the gnome-keyring files is
> installed on my system. If p11 doesn't find the module, shouldn't it let it
> pass silently? (It should inform about the missing module only when --debug,
> --verbose or some such option is used.)

> Note that I know I can pass the stderr to /dev/null.

Hello,

I guess you have got got gnome-keyring uninstalled, but not purged,
therefore /etc/pkcs11/modules/gnome-keyring-module which tells p11-kit
to try loading gnome-keyring-pkcs11.so is present. How about purging
gnome-keyring to get rid of the message?

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org