Bug#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)

[Andreas Tille]

On Wed, Jan 25, 2012 at 01:37:59AM +, peter green wrote:
> Andreas Tille wrote:
> > Hi,
> >
> > I have to admit that I do not have any experience with SSE issues.  Any
> > advise what to do in cases like this (see build logs linked below)?
> From looking at the build logs it looks like it is trying to build
> a "plain CPU plugin" and a "CPU with SSE plugin", presumablly the
> "plugins" are different peices of code that can be used to perform
> the core computations. It looks like you will need to modify the
> build system so that it is possible to disable building the "CPU
> with SSE plugin".

Yes, that's also what I guessed from the logs and the code.
 
> But thats only my gut feeling from looking at the build logs and
> package discriptions, this really needs to be confirmed by someone
> who actually knows the internals of the package in question.

Upstream was in CC in all these mails.  I'm urgently hoping for some
answer.

> If you can't handle this then I don't think you are competant to be
> maintaining this package in debian. Knowing how the components of
> the software they are packaging fit together and how to fix the
> build systems to produce packages suitable for debian is IMO a
> pretty key part of a maintainers job.

While I really agree to this statement I think there is few chance that
somebody else will step in.  We are just needing to maintain this as a
predependency for two important packages of the Debian Med team.  As you
know RFP bugs are really rarely resolved and thus we try to drain the
competence to handle this from upstream which is IMHO the fallback for
maintainers in any case.

Kind regards

   Andreas. 

-- 
http://fam-tille.de



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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 652153 + gnome-chemistry-utils
Bug #652153 [chemical-mime-data] Drop gnome-mime-data-2.0 from pkg-config (.pc) 
file
Added indication that 652153 affects gnome-chemistry-utils
> block 657273 by 652153
Bug #657273 [src:gnome-chemistry-utils] gnome-chemistry-utils: FTBFS: Package 
requirements (chemical-mime-data >= 0.1.94) were not met
Was not blocked by any bugs.
Added blocking bug(s) of 657273: 652153
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
657273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657273
652153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657259: [Resolvconf-devel] Bug#657259: resolvconf wipes out /run

[Thomas Hood]

/etc/resolvconf/run should point to /run/resolvconf, not to /run. The
package's maintainer scripts see to that.

Why is your symlink different?

I suggest you purge the resolvconf package, install the package again,
check that /etc/resolvconf/run points to /run/resolvconf, then reboot.
-- 
Thomas Hood
Op 25 jan. 2012 01:39 schreef "Antonio Ospite" 
het volgende:

> Package: resolvconf
> Version: 1.63
> Severity: critical
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> maybe it is just me, but resolvconf breaks udev on my system, so I am
> setting
> the severity to critical here, feel free to downgrade the severity if you
> think this is my fault.
>
> That is what is happening:
>
>  1. /sbin/resolvconf defines
>   RUN_DIR=/etc/resolvconf/run
>
>  2. /etc/resolvconf/run links to /run in my system
>
>  3. resolvconf --wipe-runtime-directories does
>   rm -rf "$RUN_DIR"/*
> which removes non-resolvconf files from /run
>
> After 3., when udev starts I get the message:
>  udevd: Failed to create queue file. No such file or directory.
>
> If I set RUN_DIR=/etc/resolvconf/run/resolvconf then udev works again but
> resolvconf does not work 100%.
>
> I also see that ubuntu got rid of the link in /etc/resolvconf/run and just
> used /run/resolvconf:
> http://package-import.ubuntu.com/diffs/resolvconf
>
> Maybe we could do that too?
>
> Thanks a lot for your time.
>
> Regards,
>   Antonio Ospite
>   http://ao2.it
>
> -- System Information:
> Debian Release: wheezy/sid
>  APT prefers unstable
>  APT policy: (900, 'unstable'), (600, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.2.0-1-amd64 (SMP w/1 CPU core)
> Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
>
> Versions of packages resolvconf depends on:
> ii  debconf [debconf-2.0]  1.5.41
> ii  initscripts2.88dsf-18
> ii  lsb-base   3.2-28.1
>
> resolvconf recommends no packages.
>
> resolvconf suggests no packages.
>
> -- debconf information:
> * resolvconf/linkify-resolvconf: true
>  resolvconf/reboot-recommended-after-removal:
> * resolvconf/downup-interfaces:
>  resolvconf/link-tail-to-original: false
>
>
>
> ___
> Resolvconf-devel mailing list
> resolvconf-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/resolvconf-devel
>

Processed: severity of 657276 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 657276 serious
Bug #657276 [xfonts-traditional] xfonts-traditional: can't cope with 
xfonts-unifont
Severity set to 'serious' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
657276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657275: libswe: FTBFS - unoconv expects writable home, loopback network(?)

[Paul Elliott]

I will begin looking at the problem immediately.

But as I am a beginning packager it may take me a while to completely 
understand the situation.

For instance, libswe just appeared in debian unstable, that means someone must 
have built it. How does the build environment of the autobuilder's differ from 
the one that built libswe on its path to unstable? Why is the autobuilder's 
environment correct? In other words, why is this not a bug against the 
autobuilder's software?

How can I duplicate the autobuilder's builds on my local machine to test this 
problem?

What is a "full" build and can I be sure that a full build will never occur in 
the autobuilder?

Thank You for considering this message.


On Tuesday, January 24, 2012 10:28:17 PM you wrote:
> Source: libswe
> Version: 1.77.00.0004-1
> Severity: serious
> Justification: fails to build from source
> 
> Automated builds of libswe are failing because unoconv (used to
> produce PDF and HTML documentation) assumes a writable home directory,
> which the autobuilders' build environments lack.  (Many also lack
> loopback network interfaces, which may be an issue as well.)  Given
> that the documentation winds up in a separate architecture-independent
> binary package anyway, I'd suggest arranging to build it only in full
> builds, which presumably run in less restrictive environments.
> (Relatedly, I'd suggest moving unoconv from Build-Depends to
> Build-Depends-Indep.)
> 
> Could you please look into it?
> 
> Thanks!

-- 
Paul Elliott   1(512)837-1096
pelli...@blackpatchpanel.com   PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/   Austin TX 78758-3117



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

Bug#657275: libswe: FTBFS - unoconv expects writable home, loopback network(?)

[Aaron M. Ucko]

Source: libswe
Version: 1.77.00.0004-1
Severity: serious
Justification: fails to build from source

Automated builds of libswe are failing because unoconv (used to
produce PDF and HTML documentation) assumes a writable home directory,
which the autobuilders' build environments lack.  (Many also lack
loopback network interfaces, which may be an issue as well.)  Given
that the documentation winds up in a separate architecture-independent
binary package anyway, I'd suggest arranging to build it only in full
builds, which presumably run in less restrictive environments.
(Relatedly, I'd suggest moving unoconv from Build-Depends to
Build-Depends-Indep.)

Could you please look into it?

Thanks!



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

Processed: severity of 657137 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 657137 important
Bug #657137 [glade] glade segfaults when adding a column to a list
Severity set to 'important' from 'grave'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
657137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#655792: marked as done (haskell-hledger-web: FTBFS: unsatisfiable build-dependency: libghc-cmdargs-dev (< 0.9) but 0.9-4 is to be installed)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2012 02:48:46 +
with message-id 
and subject line Bug#655792: fixed in haskell-hledger-web 0.16.5-1
has caused the Debian Bug report #655792,
regarding haskell-hledger-web: FTBFS: unsatisfiable build-dependency: 
libghc-cmdargs-dev (< 0.9) but 0.9-4 is to be installed
to be marked as done.

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

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


-- 
655792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hledger-web
Version: 0.16.3-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ┌──┐
> │ Install haskell-hledger-web build dependencies (apt-based resolver) 
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-haskell-hledger-web-dummy : Depends: libghc-cmdargs-dev 
> (< 0.9) but 0.9-4 is to be installed
> E: Broken packages

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/haskell-hledger-web_0.16.3-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: haskell-hledger-web
Source-Version: 0.16.5-1

We believe that the bug you reported is fixed in the latest version of
haskell-hledger-web, which is due to be installed in the Debian FTP archive:

haskell-hledger-web_0.16.5-1.debian.tar.gz
  to main/h/haskell-hledger-web/haskell-hledger-web_0.16.5-1.debian.tar.gz
haskell-hledger-web_0.16.5-1.dsc
  to main/h/haskell-hledger-web/haskell-hledger-web_0.16.5-1.dsc
haskell-hledger-web_0.16.5.orig.tar.gz
  to main/h/haskell-hledger-web/haskell-hledger-web_0.16.5.orig.tar.gz
hledger-web_0.16.5-1_amd64.deb
  to main/h/haskell-hledger-web/hledger-web_0.16.5-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-hledger-web package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Jan 2012 20:11:16 -0500
Source: haskell-hledger-web
Binary: hledger-web
Architecture: source amd64
Version: 0.16.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description: 
 hledger-web - web interface for the hledger accounting tool
Closes: 655792
Changes: 
 haskell-hledger-web (0.16.5-1) unstable; urgency=low
 .
   * New upstream version.
   * Build with newer cmdargs.  closes: #655792.
Checksums-Sha1: 
 ef297483b6b44627fa7381f865906d0e59753593 3099 haskell-hledger-web_0.16.5-1.dsc
 c081ae8b3287a5fc578e38fcd14bf1be53e8102e 106629 
haskell-hledger-web_0.16.5.orig.tar.gz
 49dd6e5a7b724ea904756c29ca156a7fc7df6fcd 2818 
haskell-hledger-web_0.16.5-1.debian.tar.gz
 3b9a8fbd8aeb1c10627f8f4008f849dddf766782 4172710 hledger-web_0.16.5-1_amd64.deb
Checksums-Sha256: 
 096f13baccdb7a1ec9324d39d251141fa4216680a7cc3989d21af9559657ff23 3099 
haskell-hledger-web_0.16.5-1.dsc
 06d8c254c6b73a4ec0cb7ceecc875605e66e88e4fd5fff4c097f4a61a8af103f 106629 
haskell-hledger-web_0.16.5.orig.tar.gz
 8ce11fdb5affae95037432ff79d477c627a2c6619d0648706d9701949fc658ae 2818 
haskell-hledger-web_0.16.5-1.debian.tar.gz
 796d76f5385439ba

Bug#654613: pyxpcom: FTBFS on armhf, reproduced on sid amd64: No rule to make target `_xpidlgen/py_test_component.h', needed by `export'.

[Cyril Brulebois]

Konstantinos Margaritis  (04/01/2012):
> Package: pyxpcom
> Version: 1:8.0~hg20111006-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=pyxpcom&arch=armhf&ver=1%3A8.0%7Ehg20111006-1&stamp=1324610578
> 
> pyxpcom FTBFS on armhf, but I reproduced the exact failure on sid
> amd64, hence the severity set to serious.
> 
> Excerpt from the build log:
> 
> /usr/bin/python ../../../../config/nsinstall.py -D ../../../dist/idl
> make[6]: *** No rule to make target `_xpidlgen/py_test_component.h',
> needed by `export'.  Stop.

There are other interesting parts during configure:
| ../configure: 774: test: 
/build/buildd-pyxpcom_8.0~hg20111006-1-armhf-1vVrmO/pyxpcom-8.0~hg20111006: 
unexpected operator
…
| ../configure: 9917: ../configure: AM_LANGINFO_CODESET: not found
…
| ../configure: 10886: test: /usr/lib/xulrunner-devel-9.0: unexpected operator
…

Flakky build (configure) system?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#657273: gnome-chemistry-utils: FTBFS: Package requirements (chemical-mime-data >= 0.1.94) were not met

[Cyril Brulebois]

Source: gnome-chemistry-utils
Version: 0.12.10-1
Severity: serious
Justification: FTBFS

Hi,

while checking the binNMUability of the packages for the iceweasel9
transition, your package FTBFS'd with:
| checking for chemical_mime_data... no
| configure: error: Package requirements (chemical-mime-data >= 0.1.94) were 
not met:
| 
| Package gnome-mime-data-2.0 was not found in the pkg-config search path.
| Perhaps you should add the directory containing `gnome-mime-data-2.0.pc'
| to the PKG_CONFIG_PATH environment variable
| Package 'gnome-mime-data-2.0', required by 'chemical-mime-data', not found
| 
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
| 
| Alternatively, you may set the environment variables chemical_mime_data_CFLAGS
| and chemical_mime_data_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.

Either Build-Depends is missing some bits, or another package's Depends
is missing some bits. I'll leave that up to you to investigate though.
:-)

Mraw,
KiBi.



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

Bug#646657: Fix available

[Diego Elio Pettenò]

https://github.com/jimweirich/builder/pull/15 should fix the issue (and
another unrelated one fwiw).

-- 
Diego Elio Pettenò 




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

Bug#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)

[peter green]

Andreas Tille wrote:
> Hi,
>
> I have to admit that I do not have any experience with SSE issues.  Any
> advise what to do in cases like this (see build logs linked below)?
From looking at the build logs it looks like it is trying to build  a 
"plain CPU plugin" and a "CPU with SSE plugin", presumablly the 
"plugins" are different peices of code that can be used to perform the 
core computations. It looks like you will need to modify the build 
system so that it is possible to disable building the "CPU with SSE plugin".


But thats only my gut feeling from looking at the build logs and package 
discriptions, this really needs to be confirmed by someone who actually 
knows the internals of the package in question.


If you can't handle this then I don't think you are competant to be 
maintaining this package in debian. Knowing how the components of the 
software they are packaging fit together and how to fix the build 
systems to produce packages suitable for debian is IMO a pretty key part 
of a maintainers job.




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

Bug#655790: marked as done (haskell-hledger-chart: FTBFS: unsatisfiable build-dependency: libghc-cmdargs-dev (< 0.9) but 0.9-4 is to be installed)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2012 01:17:51 +
with message-id 
and subject line Bug#655790: fixed in haskell-hledger-chart 0.16.1-2
has caused the Debian Bug report #655790,
regarding haskell-hledger-chart: FTBFS: unsatisfiable build-dependency: 
libghc-cmdargs-dev (< 0.9) but 0.9-4 is to be installed
to be marked as done.

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

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


-- 
655790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hledger-chart
Version: 0.16.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ┌──┐
> │ Install haskell-hledger-chart build dependencies (apt-based resolver)   
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-haskell-hledger-chart-dummy : Depends: 
> libghc-cmdargs-dev (< 0.9) but 0.9-4 is to be installed
> E: Broken packages

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/haskell-hledger-chart_0.16.1-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: haskell-hledger-chart
Source-Version: 0.16.1-2

We believe that the bug you reported is fixed in the latest version of
haskell-hledger-chart, which is due to be installed in the Debian FTP archive:

haskell-hledger-chart_0.16.1-2.debian.tar.gz
  to main/h/haskell-hledger-chart/haskell-hledger-chart_0.16.1-2.debian.tar.gz
haskell-hledger-chart_0.16.1-2.dsc
  to main/h/haskell-hledger-chart/haskell-hledger-chart_0.16.1-2.dsc
hledger-chart_0.16.1-2_amd64.deb
  to main/h/haskell-hledger-chart/hledger-chart_0.16.1-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-hledger-chart 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Jan 2012 19:54:13 -0500
Source: haskell-hledger-chart
Binary: hledger-chart
Architecture: source amd64
Version: 0.16.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description: 
 hledger-chart - pie-chart generator for the hledger accounting tool
Closes: 655790
Changes: 
 haskell-hledger-chart (0.16.1-2) unstable; urgency=low
 .
   * Adjust for newer cmdargs.  closes: #655790.
Checksums-Sha1: 
 2546bb190c55a5b793f317c25f9c005d524e68ff 2404 
haskell-hledger-chart_0.16.1-2.dsc
 918d16d017472865de457de1cd855338c6d295e8 2185 
haskell-hledger-chart_0.16.1-2.debian.tar.gz
 fc7f7f7215a40df57eacc010dda91c377d20fb66 1744574 
hledger-chart_0.16.1-2_amd64.deb
Checksums-Sha256: 
 6e13d3cda30855032bee3896ee02f0ea11f9ccd25c768c8fbf0a2fc7b310a011 2404 
haskell-hledger-chart_0.16.1-2.dsc
 32bf7163656a3daa97305b0df08bb0aa3b0a792cb03cef468fb2dbcce83ac86d 2185 
haskell-hledger-chart_0.16.1-2.debian.tar.gz
 0b02fa80858ec7e0d5c2ce28e4a27a9f836307e6e4cfe0deb0db05c8418b1664 1744574 
hledger-chart_0.16.1-2_amd64.deb
Files: 
 398eef3be77ab6cfb0dc87f5956057dd 2404 haskell extra 
haskell-hledger-chart_0.16.1-2.dsc
 fe815ee0dd64495c1c30e19717cc8fae 2185 haskell extra 
haskell-hledger-chart_0.16.1-2.debia

Bug#657261: src:gmime2.4: Rebuild for Mono transition

[Jo Shields]

On Wed, 2012-01-25 at 02:01 +0100, Michael Biebl wrote:
> On 25.01.2012 01:40, Jo Shields wrote:
> > Package: src:gmime2.4
> > Version: 2.4.25-1
> > Severity: serious
> > User: debian-...@lists.debian.org
> > Usertags: mono-2.10-transition
> > 
> > Hi,
> > 
> > A Mono transition is underway. Every source package needs to be rebuilt
> > to compile against CLR 4.0 instead of CLR 2.0. Please upload gmime2.4
> > for this change. You can check it worked if, after rebuilding, 
> > libgmime2.4-cil has a dependency on libmono-corlib4.0-cil instead of 
> > …corlib2.0-cil.
> 
> Does the package need a sourceful update? If not, a simple rebuild can
> requested by filing a binNMU bug (resp. reassign this bug to
> release.debian.org).

libgmime2.4-cil is arch:all therefore a sourceful upload is required


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

Bug#657261: src:gmime2.4: Rebuild for Mono transition

[Michael Biebl]

On 25.01.2012 01:40, Jo Shields wrote:
> Package: src:gmime2.4
> Version: 2.4.25-1
> Severity: serious
> User: debian-...@lists.debian.org
> Usertags: mono-2.10-transition
> 
> Hi,
> 
> A Mono transition is underway. Every source package needs to be rebuilt
> to compile against CLR 4.0 instead of CLR 2.0. Please upload gmime2.4
> for this change. You can check it worked if, after rebuilding, 
> libgmime2.4-cil has a dependency on libmono-corlib4.0-cil instead of 
> …corlib2.0-cil.

Does the package need a sourceful update? If not, a simple rebuild can
requested by filing a binNMU bug (resp. reassign this bug to
release.debian.org).


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#656760: NMU uploaded to DELAYED/3

[Jo Shields]

Dear maintainer,

as per policy, a fix for this release-critical bug has been uploaded to
the Delayed queue. In order to cancel the NMU, please ask, or upload
your own package with a higher version number.


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

Bug#656502: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

[peter green]

Can anyone test if the attached patch improves anything?

I just tried the following on armhf

Replaced debian/patches/0009-fix_FTBFS_with_ffmpeg_debian.patch  
with the version from http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=656502


Added Adapt_to_libav_API_changes.patch from the same message to debian/patches 
as
0010-Adapt_to_libav_API_changes.patch

added 0001-Define-_GNU_SOURCE-when-compiling-libmv.patch from 
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=17;bug=654428 to debian/patches as

0011-Define-_GNU_SOURCE-when-compiling-libmv.patch

Added 0010-Adapt_to_libav_API_changes.patch and 
0011-Define-_GNU_SOURCE-when-compiling-libmv.patch to the quilt series


After applying all those patches it still failed with register errors.

[100%] Building CXX object 
extern/libmv/CMakeFiles/extern_libmv.dir/third_party/glog/src/signalhandler.cc.o
cd /blender-2.61/obj-arm-linux-gnueabihf/extern/libmv && /usr/bin/c++   
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D__LITTLE_ENDIAN__ 
-DV3DLIB_ENABLE_SUITESPARSE -DGOOGLE_GLOG_DLL_DECL="" -D_GNU_SOURCE -DNDEBUG 
-D__STDC_CONSTANT_MACROS -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing  -Wall 
-Wno-invalid-offsetof -Wno-sign-compare  -Wno-deprecated-declarations -Wno-unused-parameter 
-Wno-unused-but-set-variable -O2 -DNDEBUG -I/blender-2.61/extern/libmv 
-I/blender-2.61/extern/Eigen3 -I/blender-2.61/extern/libmv/third_party/ssba 
-I/blender-2.61/extern/libmv/third_party/ldl/Include -I/blender-2.61/extern/colamd/Include 
-I/blender-2.61/extern/libmv/third_party/glog/src-o 
CMakeFiles/extern_libmv.dir/third_party/glog/src/signalhandler.cc.o -c 
/blender-2.61/extern/libmv/third_party/glog/src/signalhandler.cc
/blender-2.61/extern/libmv/third_party/glog/src/signalhandler.cc: In function 
‘void* google::{anonymous}::GetPC(void*)’:
/blender-2.61/extern/libmv/third_party/glog/src/signalhandler.cc:75:28: error: 
‘mcontext_t’ has no member named ‘gregs’
/blender-2.61/extern/libmv/third_party/glog/src/signalhandler.cc:75:28: error: 
‘REG_EIP’ was not declared in this scope
make[3]: *** 
[extern/libmv/CMakeFiles/extern_libmv.dir/third_party/glog/src/signalhandler.cc.o]
 Error 1
make[3]: Leaving directory `/blender-2.61/obj-arm-linux-gnueabihf'
make[2]: *** [extern/libmv/CMakeFiles/extern_libmv.dir/all] Error 2
make[2]: Leaving directory `/blender-2.61/obj-arm-linux-gnueabihf'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/blender-2.61/obj-arm-linux-gnueabihf'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
root@debian:/blender-2.61#




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

Bug#656761: NMU uploaded to DELAYED/3

[Jo Shields]

Dear maintainer,

a fix for this release-critical bug has been uploaded to the DELAYED
queue, as per policy. To cancel the NMU, please ask, or upload your own
package with a higher version


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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 657255 important
Bug #657255 [bluez] [bluez] bluetoothd is hanging up.
Severity set to 'important' from 'serious'

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
657255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: block 648775 with 657261

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 648775 with 657261
Bug #648775 [release.debian.org] transition: mono 2.10
Was blocked by: 656817 656821 656756 657258 656818 656760 656822 649339 656690 
656761 657256
Added blocking bug(s) of 648775: 657261
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
648775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657261: src:gmime2.4: Rebuild for Mono transition

[Jo Shields]

Package: src:gmime2.4
Version: 2.4.25-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: mono-2.10-transition

Hi,

A Mono transition is underway. Every source package needs to be rebuilt
to compile against CLR 4.0 instead of CLR 2.0. Please upload gmime2.4
for this change. You can check it worked if, after rebuilding, 
libgmime2.4-cil has a dependency on libmono-corlib4.0-cil instead of 
…corlib2.0-cil.

  http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775

Cheers,



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

Processed: block 648775 with 657258

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 648775 with 657258
Bug #648775 [release.debian.org] transition: mono 2.10
Was blocked by: 656756 656821 656817 656818 656760 656822 649339 656690 657256 
656761
Added blocking bug(s) of 648775: 657258
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
648775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657259: resolvconf wipes out /run

[Antonio Ospite]

Package: resolvconf
Version: 1.63
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

maybe it is just me, but resolvconf breaks udev on my system, so I am setting
the severity to critical here, feel free to downgrade the severity if you
think this is my fault.

That is what is happening:

  1. /sbin/resolvconf defines
   RUN_DIR=/etc/resolvconf/run

  2. /etc/resolvconf/run links to /run in my system

  3. resolvconf --wipe-runtime-directories does
   rm -rf "$RUN_DIR"/*
 which removes non-resolvconf files from /run

After 3., when udev starts I get the message:
  udevd: Failed to create queue file. No such file or directory.

If I set RUN_DIR=/etc/resolvconf/run/resolvconf then udev works again but
resolvconf does not work 100%.

I also see that ubuntu got rid of the link in /etc/resolvconf/run and just
used /run/resolvconf:
http://package-import.ubuntu.com/diffs/resolvconf

Maybe we could do that too?

Thanks a lot for your time.

Regards,
   Antonio Ospite
   http://ao2.it

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages resolvconf depends on:
ii  debconf [debconf-2.0]  1.5.41
ii  initscripts2.88dsf-18
ii  lsb-base   3.2-28.1

resolvconf recommends no packages.

resolvconf suggests no packages.

-- debconf information:
* resolvconf/linkify-resolvconf: true
  resolvconf/reboot-recommended-after-removal:
* resolvconf/downup-interfaces:
  resolvconf/link-tail-to-original: false



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

Bug#657258: src:libindicate: Rebuild for Mono transition

[Jo Shields]

Package: src:libindicate
Version: 0.5.0-3
Severity: serious
User: debian-...@lists.debian.org
Usertags: mono-2.10-transition

Hi,

A Mono transition is underway. Every source package needs to be rebuilt
to compile against CLR 4.0 instead of CLR 2.0. Please upload libindicate
for this change. You can check it worked if, after rebuilding, 
libindicate0.1-cil has a dependency on libmono-corlib4.0-cil instead of 
…corlib2.0-cil.

  http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775

Cheers,



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

Processed: block 648775 with 657256

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 648775 with 657256
Bug #648775 [release.debian.org] transition: mono 2.10
Was blocked by: 656817 656821 656756 656818 656760 656822 649339 656690 656761
Added blocking bug(s) of 648775: 657256
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
648775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657256: src:libgwibber: Rebuild for Mono transition

[Jo Shields]

Package: src:libgwibber
Version: 0.1.1-1.1
Severity: serious
User: debian-...@lists.debian.org
Usertags: mono-2.10-transition

Hi,

A Mono transition is underway. Every source package needs to be rebuilt
to compile against CLR 4.0 instead of CLR 2.0. Please upload libgwibber
for this change. You can check it worked if, after rebuilding, 
libgwibber0.1-cil has a dependency on libmono-corlib4.0-cil instead of 
…corlib2.0-cil.

  http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775

Cheers,



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

Bug#657255: [bluez] bluetoothd is hanging up.

[Takahide Nojima]

Package: bluez
Version: 4.98-1
Severity: serious

--- Please enter the report below this line. ---

Hello,
 
I checked new package of bluez 4.98-1 , I found it doesn't work my debian box.
There is no bluetooth icon on status bar on gnome3.2 desktop,
and also bluetooth menu in gnome-control-center also grayed out.

I run bluetoothd with debug option, then I found it stop in the middle of 
initialization as below

   ---console log is here --
$ sudo /usr/sbin/bluetoothd -n -d
bluetoothd[2853]: Bluetooth daemon 4.98
bluetoothd[2853]: src/main.c:parse_config() parsing main.conf
bluetoothd[2853]: src/main.c:parse_config() discovto=0
bluetoothd[2853]: src/main.c:parse_config() pairto=0
bluetoothd[2853]: src/main.c:parse_config() pageto=8192
bluetoothd[2853]: src/main.c:parse_config() auto_to=60
bluetoothd[2853]: src/main.c:parse_config() name=%h-%d
bluetoothd[2853]: src/main.c:parse_config() class=0x000100
bluetoothd[2853]: src/main.c:parse_config() discov_interval=30
bluetoothd[2853]: src/main.c:parse_config() Key file does not have key 
'DeviceID'
bluetoothd[2853]: Starting SDP server
bluetoothd[2853]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[2853]: src/plugin.c:add_plugin() Loading pnat plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading audio plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading sap plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading serial plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading proximity plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading service plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading gatt_example plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading time plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading alert plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading health plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading thermometer plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading hciops plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading mgmtops plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading formfactor plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading storage plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading adaptername plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[2853]: src/plugin.c:add_plugin() Loading dbusoob plugin
bluetoothd[2853]: src/plugin.c:plugin_init() Loading plugins 
/usr/lib/x86_64-linux-gnu/bluetooth/plugins
bluetoothd[2853]: plugins/service.c:register_interface() path 
/org/bluez/2853/any
bluetoothd[2853]: plugins/service.c:register_interface() Registered interface 
org.bluez.Service on path /org/bluez/2853/any
bluetoothd[2853]: plugins/dbusoob.c:dbusoob_init() Setup dbusoob plugin
bluetoothd[2853]: health/hdp.c:hdp_manager_start() Starting Health manager
bluetoothd[2853]: alert/main.c:alert_init() Attribute server is disabled
bluetoothd[2853]: Failed to init alert plugin
bluetoothd[2853]: time/main.c:time_init() Attribute server is disabled
bluetoothd[2853]: Failed to init time plugin
bluetoothd[2853]: Parsing /etc/bluetooth/proximity.conf failed: No such file or 
directory
bluetoothd[2853]: proximity/reporter.c:reporter_init() Attribute server is 
disabled
bluetoothd[2853]: Failed to init proximity plugin
bluetoothd[2853]: network/manager.c:read_config() /etc/bluetooth/network.conf: 
Key file does not have key 'DisableSecurity'
bluetoothd[2853]: network/manager.c:read_config() Config options: Security=true
bluetoothd[2853]: input/manager.c:input_manager_init() input.conf: Key file 
does not have key 'IdleTimeout'
bluetoothd[2853]: audio/manager.c:audio_manager_init() audio.conf: Key file 
does not have key 'AutoConnect'
bluetoothd[2853]: plugins/pnat.c:pnat_init() Setup Phonet AT (DUN) plugin
bluetoothd[2853]: plugins/hciops.c:hciops_init() 
bluetoothd[2853]: plugins/gatt-example.c:gatt_example_init() Attribute server 
is disabled
bluetoothd[2853]: Failed to init gatt_example plugin
bluetoothd[2853]: plugins/hciops.c:hciops_setup() 
bluetoothd[2853]: src/main.c:main() Entering main loop
bluetoothd[2853]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 
soft 0 hard 0
bluetoothd[2853]: plugins/hciops.c:init_known_adapters() 
( ... hanging up on this point... )
 --

Switching off-on my bluetooth headphone didn't make no effect, bluetoothd 
doesn't proceed any more.

Does anyone have information of this problem?

Thanks,

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.2.0-1-amd64

Debian Release: wheezy/sid
  500 unstableftp.jp.debian.org 
  150 experimentalftp.jp.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-==
libc6  (>=

Bug#657254: libnl-3-200: Fails to build from source due to missing build-dep on source-highlight

[Len Sorensen]

Package: libnl-3-200
Version: 3.2.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

libnl3 fails to build since it uses asciidoc and hence needs
source-highlight.  However asciidoc only recommends source-highlight
which means buildd's won't have it installed and others might not have
it installed.

So either libnl3 needs an explicit build-dep on source-hightlight,
or asciidoc needs to be made to require source-highlight.

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

Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libnl-3-200 depends on:
ii  libc6  2.13-24

libnl-3-200 recommends no packages.

libnl-3-200 suggests no packages.

-- no debconf information



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

Bug#621440: marked as done (Still uses libdb4.8)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:48:01 +
with message-id 
and subject line Bug#647247: fixed in mailavenger 0.8.2-1
has caused the Debian Bug report #647247,
regarding Still uses libdb4.8
to be marked as done.

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

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


-- 
647247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailavenger
Version: 0.8.1-3
Severity: normal
User: pkg-db-de...@lists.alioth.debian.org
Usertags: db5.1

Your package currently still uses Berkeley DB version 4.8 (libdb4.8).

However, there is a newer Berkeley DB version in the archive (libdb5.1),
with a compatible API.  Berkeley DB version 4.8 will be eventually
removed from unstable in favor of version 5.1.

Please port your package to libdb5.1 as soon as possible.  In most cases
only change required is to update build depends from libdb4.8-dev
to libdb-dev, or just recompile the package.

More complicated scenarios:

- Package does check for DB_VERSION_MAJOR == 4 - this should be updated
  to (DB_VERSION_MAJOR > 4) || ((DB_VERSION_MAJOR == 4) && (DB_VERSION_MINOR >= 
XX)).

- Configure checks - sometime there is a list of db-4.8 db-4.6 db-4.2, etc., 
this
  needs to be updated to just db (or db-5.1 db-5 db), or at least list the 'db'
  in the front

You can see example patch in cyrus-imapd-2.2:
http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD

- The packages which use Berkeley DB transactional mode need to upgrade
  the database files before the upgrade.  This is fairly straightforward
  and is well documented on the Berkeley DB website.  But you probably
  already know that because it's not the first Berkeley DB transition.

The example script can be found in the cyrus-imapd-2.4 (not yet released):
http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD

Thanks, 
--
Ondřej Surý 

-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 
'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: mailavenger
Source-Version: 0.8.2-1

We believe that the bug you reported is fixed in the latest version of
mailavenger, which is due to be installed in the Debian FTP archive:

mailavenger_0.8.2-1.debian.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2-1.debian.tar.gz
mailavenger_0.8.2-1.dsc
  to main/m/mailavenger/mailavenger_0.8.2-1.dsc
mailavenger_0.8.2-1_amd64.deb
  to main/m/mailavenger/mailavenger_0.8.2-1_amd64.deb
mailavenger_0.8.2.orig.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 647...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
der...@debian.org (supplier of updated mailavenger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Dec 2011 09:24:55 -0300
Source: mailavenger
Binary: mailavenger
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Ulises Vitulli 
Changed-By: der...@debian.org
Description: 
 mailavenger - Highly configurable, MTA-independent SMTP filter server
Closes: 621440 625391 634553 647247
Changes: 
 mailavenger (0.8.2-1) unstable; urgency=low
 .
   * New upstream-coordinated snapshot/release:
 - Fix bdb compatibility on 5.x (Closes: #621440, #634553, #647247)
 - Fix some gcc-4.6 warnings (Closes: #625391).
   * Improve building targets for simplifying portscripts.
   * Clean-up on debian/rules for multiarch support.
   * Dropped local patch for typofixing license documentation.
Checksums-Sha1: 
 10670a7c33dae51d7cb92f9d97cf150b5be4832f 1817 mailavenger_0.8.2-1.dsc
 3aa54a5347f83484db4ab938983bbf98302fd276 871608 mailavenger_0.8.2.orig.tar.gz
 19eaf649b6e5a06ae55789738920c3fc3f626d94 8816 mailavenger_0.8.2-1.debian.tar.gz
 f656779960415bac0ebe3af920b622a9e19

Bug#647247: marked as done (mailavenger FTBFS, can't find berkerly DB)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:48:01 +
with message-id 
and subject line Bug#647247: fixed in mailavenger 0.8.2-1
has caused the Debian Bug report #647247,
regarding mailavenger FTBFS, can't find berkerly DB
to be marked as done.

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

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


-- 
647247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: mailavenger
Version: 0.8.1-3
Severity: serious

While trying to confirm if bug 625391 was a false positive or not I 
discovered that your package FTBFS in unstable for another reason.


checking for BerkeleyDB library... no
configure: error: Cannot find BerkeleyDB
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Build command 'cd mailavenger-0.8.1 && dpkg-buildpackage -b -uc' failed.
E: Child process failed
root@debian:/#configure:18178: checking for BerkeleyDB library
configure:18360: result: no
configure:18364: error: Cannot find BerkeleyDB

config.log didn't give any further information on why the test for 
berkerly DB failed


configure:18178: checking for BerkeleyDB library
configure:18360: result: no
configure:18364: error: Cannot find BerkeleyDB




--- End Message ---
--- Begin Message ---
Source: mailavenger
Source-Version: 0.8.2-1

We believe that the bug you reported is fixed in the latest version of
mailavenger, which is due to be installed in the Debian FTP archive:

mailavenger_0.8.2-1.debian.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2-1.debian.tar.gz
mailavenger_0.8.2-1.dsc
  to main/m/mailavenger/mailavenger_0.8.2-1.dsc
mailavenger_0.8.2-1_amd64.deb
  to main/m/mailavenger/mailavenger_0.8.2-1_amd64.deb
mailavenger_0.8.2.orig.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 647...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
der...@debian.org (supplier of updated mailavenger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Dec 2011 09:24:55 -0300
Source: mailavenger
Binary: mailavenger
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Ulises Vitulli 
Changed-By: der...@debian.org
Description: 
 mailavenger - Highly configurable, MTA-independent SMTP filter server
Closes: 621440 625391 634553 647247
Changes: 
 mailavenger (0.8.2-1) unstable; urgency=low
 .
   * New upstream-coordinated snapshot/release:
 - Fix bdb compatibility on 5.x (Closes: #621440, #634553, #647247)
 - Fix some gcc-4.6 warnings (Closes: #625391).
   * Improve building targets for simplifying portscripts.
   * Clean-up on debian/rules for multiarch support.
   * Dropped local patch for typofixing license documentation.
Checksums-Sha1: 
 10670a7c33dae51d7cb92f9d97cf150b5be4832f 1817 mailavenger_0.8.2-1.dsc
 3aa54a5347f83484db4ab938983bbf98302fd276 871608 mailavenger_0.8.2.orig.tar.gz
 19eaf649b6e5a06ae55789738920c3fc3f626d94 8816 mailavenger_0.8.2-1.debian.tar.gz
 f656779960415bac0ebe3af920b622a9e195bf42 579758 mailavenger_0.8.2-1_amd64.deb
Checksums-Sha256: 
 4fd7ff1f7c562975f44bd67f869e268298530c316f4ed6c74b7cce6b98da11cc 1817 
mailavenger_0.8.2-1.dsc
 6039754a72ba70b78a48a92747e36edfbf617a40afd2dad14290f767a8bfad5f 871608 
mailavenger_0.8.2.orig.tar.gz
 ad01ac1f0029a50f7ee82f4f0e5fae744634533aa96ad344f6d7b9416cd12fd2 8816 
mailavenger_0.8.2-1.debian.tar.gz
 548394e83d24f834d3ef534efbdd280d5760788380b7e95966d3651199f26782 579758 
mailavenger_0.8.2-1_amd64.deb
Files: 
 22f2382b61ecf0e9ff0dd8f3e812915f 1817 mail extra mailavenger_0.8.2-1.dsc
 696f9745446a3037696fb55b6b690c56 871608 mail extra 
mailavenger_0.8.2.orig.tar.gz
 c9333813ade4aa56ed5c307b3aa0b59f 8816 mail extra 
mailavenger_0.8.2-1.debian.tar.gz
 7f023b9c9355f3a80f1603843cfea675 579758 mail extra 
mailavenger_0.8.2-1_amd64.deb

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

iQIcBAEBCAAGBQJPHz82AAoJEGin9OG0lUUKR4cP+gI0ROYRHnvq29Pk3NSD41l3
7oAnsiXt91DdCdEiHleduQQeUWMnLo1k2pWxbToV5jovob8SITHX0nQkNcpwoPHM
U5qI/5RO/KAa0dyKq+3DUUFLldz8kpreE37IPVebPG6wC+MGOVIuk7hMracXamS8
BEwY7qSfhyXlQ5zcNY8eHw7qOE7d+9Ot03nIMXXEYz4raZGkmJJo/jCJw2FPS+vk
UsYL75

Bug#634553: marked as done (mailavenger: FTBFS: configure: error: Cannot find BerkeleyDB)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:48:01 +
with message-id 
and subject line Bug#634553: fixed in mailavenger 0.8.2-1
has caused the Debian Bug report #634553,
regarding mailavenger: FTBFS: configure: error: Cannot find BerkeleyDB
to be marked as done.

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

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


-- 
634553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailavenger
Version: 0.8.1-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110718 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
> # Add here commands to configure the package.
> cp -f /usr/share/misc/config.sub config.sub
> cp -f /usr/share/misc/config.guess config.guess
> ./configure --enable-sasl --host=x86_64-linux-gnu \
>--build=x86_64-linux-gnu --prefix=/usr \
>   --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info \
>   --libexecdir=\${prefix}/lib/mailavenger \
>   --docdir=\${prefix}/share/doc/mailavenger \
>   --datadir=\${prefix}/share/doc/mailavenger \
>   --htmldir=\${prefix}/share/doc/mailavenger \
>   CFLAGS="-g -O2-fstack-protector --param ssp-buffer-size=4  
> -D_FORTIFY_SOURCE=2  -Wformat -Wformat-security -Werror=format-security " \
>   LDFLAGS="-Wl,-z,relro  -Wl,-z,now "
> 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 build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-linux-gnu-gcc accepts -g... yes
> checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of x86_64-linux-gnu-gcc... gcc3
> checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
> checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether x86_64-linux-gnu-g++ accepts -g... yes
> checking dependency style of x86_64-linux-gnu-g++... gcc3
> checking whether ln -s works... yes
> 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 x86_64-linux-gnu-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 the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for x86_64-linux-gnu-objdump... no
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for x86_64-linux-gnu-ar... no
> checking for ar... ar
> checking for x86_64-linux-gnu-strip... no
> checking for strip... strip
> checking for x86_64-linux-gnu-ranlib... no
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc 
> object... ok
> 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 whether we are using the GNU C++ compiler... (cached) yes
> checking whether x86_64-linux-gnu-g++ accepts -g... (cached) yes
> checking dependency style of x86_64-linux-gnu-g++... (cached) gcc3
> checking how to run th

Bug#639437: marked as done (package no longer installable)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:49:11 +
with message-id 
and subject line Bug#639437: fixed in screenruler 0.960+bzr41-1
has caused the Debian Bug report #639437,
regarding package no longer installable
to be marked as done.

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

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


-- 
639437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: screenruler
Version: 0.891+bzr25-1
Severity: serious

ruby-gnome2 dropped some packages and screenruler is hence no longer
installable in unstable.  The dependencies affected are libglade2-ruby and
libgconf2-ruby.

Kind regards
Philipp Kern


--- End Message ---
--- Begin Message ---
Source: screenruler
Source-Version: 0.960+bzr41-1

We believe that the bug you reported is fixed in the latest version of
screenruler, which is due to be installed in the Debian FTP archive:

screenruler_0.960+bzr41-1.debian.tar.gz
  to main/s/screenruler/screenruler_0.960+bzr41-1.debian.tar.gz
screenruler_0.960+bzr41-1.dsc
  to main/s/screenruler/screenruler_0.960+bzr41-1.dsc
screenruler_0.960+bzr41-1_all.deb
  to main/s/screenruler/screenruler_0.960+bzr41-1_all.deb
screenruler_0.960+bzr41.orig.tar.gz
  to main/s/screenruler/screenruler_0.960+bzr41.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 639...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Siegfried-Angel Gevatter Pujals  (supplier of updated 
screenruler package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 24 Jan 2012 23:43:17 +0100
Source: screenruler
Binary: screenruler
Architecture: source all
Version: 0.960+bzr41-1
Distribution: unstable
Urgency: low
Maintainer: Siegfried-Angel Gevatter Pujals 
Changed-By: Siegfried-Angel Gevatter Pujals 
Description: 
 screenruler - measure objects on screen with a variety of metrics
Closes: 639437 654710
Changes: 
 screenruler (0.960+bzr41-1) unstable; urgency=low
 .
   * New upstream version + modifications from trunk:
  - Port to GtkBuilder and replace GConf with a YAML file (Closes: #639437,
#654710).
  - Handle symlinks in screenruler.rb.
  - Added a help window and internationalization support.
  - Various bug fixes.
   * debian/control:
  - Update dependencies.
   * debian/screenruler.xpm:
  - Fix typo in Catalan translation and add a German translation.
   * debian/watch:
  - Delete it (no point, upstream version numbers are inconsistent).
   * screenruler.rb:
  - Hardcode Ruby 1.8.
   * Change to source format "3.0 (quilt)" and debhelper compatibility
 version 7, switch from CDBS to dh and bump Standards-Version to 3.9.2.
Checksums-Sha1: 
 8f6fadf81cd71dd75220a2af11ff3bdc4bc0e1dd 1451 screenruler_0.960+bzr41-1.dsc
 eb3b95f2b38ce3e39a2ad07287ac1be5550ec8e3 23053 
screenruler_0.960+bzr41.orig.tar.gz
 7233f7de58de8f8f1d3ef973b6d4535ec8eeda4b 5332 
screenruler_0.960+bzr41-1.debian.tar.gz
 78f49f8694ce0b7ce1f3ea592402b7d9b4aa1982 21608 
screenruler_0.960+bzr41-1_all.deb
Checksums-Sha256: 
 99354b994e96fe7954974d0b11ff6a0caaba81cdda508efb6d6472965753ea8a 1451 
screenruler_0.960+bzr41-1.dsc
 1aa0cef1a6e7b69171613a6c66b8edb090adfbfa29af0f9a0c5863762e382f80 23053 
screenruler_0.960+bzr41.orig.tar.gz
 b350548e347cf7bd9da44c87d77beae49a36289365d6006440d459e0394ce3a1 5332 
screenruler_0.960+bzr41-1.debian.tar.gz
 cafe8247a6778e8c02b8c11984c3b671140c08a0bfb0ac9f7aed2c7f45e1e98d 21608 
screenruler_0.960+bzr41-1_all.deb
Files: 
 26b09fc6c996e448d479dccdcdbe51c3 1451 gnome optional 
screenruler_0.960+bzr41-1.dsc
 448a878f480d55a3ca8bab08d78598ba 23053 gnome optional 
screenruler_0.960+bzr41.orig.tar.gz
 7f9dced8ea4d579e5a05fab436c0f13c 5332 gnome optional 
screenruler_0.960+bzr41-1.debian.tar.gz
 d62582d04b0467c0c6374d0868326e53 21608 gnome optional 
screenruler_0.960+bzr41-1_all.deb

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

iQEcBAEBAgAGBQJPH0DyAAoJEBz8IvM2PerjqToIAJG2fGklXp52kYRB1gS4J9ZT
DvZQvXjKYqRp7tdkWV6pNlxW8tUzohfjcmXZm/dp2g0r/b8lw6v8bwiUc6ldXtDh
5NxId02Erb/wqy24ARcnjzOwsSgbC24pcPIrXbABmEMypkjtNKxUNu7V/pS/oevr
8bmo/P7xphsO0FsQydQwV6xVW7qF1FZXJGxuUsg+JCgwGsxodPlarsd3lpUUQhSl
z4cFOmXdQbpwSY7BoQiDRFxZhDKK3FGxJaLeNIo0EmoTrEeUMyP

Bug#625391: marked as done (mailavenger: ftbfs with gcc-4.6 -Werror)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:48:01 +
with message-id 
and subject line Bug#625391: fixed in mailavenger 0.8.2-1
has caused the Debian Bug report #625391,
regarding mailavenger: ftbfs with gcc-4.6 -Werror
to be marked as done.

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

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


-- 
625391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailavenger
Version: 0.8.1-3
Severity: important
Tags: wheezy sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.6 ftbfs-werror

This package builds with -Werror, and GCC 4.6 triggers new warnings
which will make the package fail to build.  Currently a Debian patch
just passes
-Wno-error=unused-but-set-variable and
-Wno-error=unused-but-set-parameter
to avoid build failures, but this patch will be reverted with the
GCC 4.6.1 release, and the severity of the report will be raised.

The full build log can be found at:
http://people.debian.org/~doko/tmp/werror/mailavenger_0.8.1-3_lsid64.buildlog
The last lines of the build log are at the end of this report.



--- End Message ---
--- Begin Message ---
Source: mailavenger
Source-Version: 0.8.2-1

We believe that the bug you reported is fixed in the latest version of
mailavenger, which is due to be installed in the Debian FTP archive:

mailavenger_0.8.2-1.debian.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2-1.debian.tar.gz
mailavenger_0.8.2-1.dsc
  to main/m/mailavenger/mailavenger_0.8.2-1.dsc
mailavenger_0.8.2-1_amd64.deb
  to main/m/mailavenger/mailavenger_0.8.2-1_amd64.deb
mailavenger_0.8.2.orig.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 625...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
der...@debian.org (supplier of updated mailavenger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Dec 2011 09:24:55 -0300
Source: mailavenger
Binary: mailavenger
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Ulises Vitulli 
Changed-By: der...@debian.org
Description: 
 mailavenger - Highly configurable, MTA-independent SMTP filter server
Closes: 621440 625391 634553 647247
Changes: 
 mailavenger (0.8.2-1) unstable; urgency=low
 .
   * New upstream-coordinated snapshot/release:
 - Fix bdb compatibility on 5.x (Closes: #621440, #634553, #647247)
 - Fix some gcc-4.6 warnings (Closes: #625391).
   * Improve building targets for simplifying portscripts.
   * Clean-up on debian/rules for multiarch support.
   * Dropped local patch for typofixing license documentation.
Checksums-Sha1: 
 10670a7c33dae51d7cb92f9d97cf150b5be4832f 1817 mailavenger_0.8.2-1.dsc
 3aa54a5347f83484db4ab938983bbf98302fd276 871608 mailavenger_0.8.2.orig.tar.gz
 19eaf649b6e5a06ae55789738920c3fc3f626d94 8816 mailavenger_0.8.2-1.debian.tar.gz
 f656779960415bac0ebe3af920b622a9e195bf42 579758 mailavenger_0.8.2-1_amd64.deb
Checksums-Sha256: 
 4fd7ff1f7c562975f44bd67f869e268298530c316f4ed6c74b7cce6b98da11cc 1817 
mailavenger_0.8.2-1.dsc
 6039754a72ba70b78a48a92747e36edfbf617a40afd2dad14290f767a8bfad5f 871608 
mailavenger_0.8.2.orig.tar.gz
 ad01ac1f0029a50f7ee82f4f0e5fae744634533aa96ad344f6d7b9416cd12fd2 8816 
mailavenger_0.8.2-1.debian.tar.gz
 548394e83d24f834d3ef534efbdd280d5760788380b7e95966d3651199f26782 579758 
mailavenger_0.8.2-1_amd64.deb
Files: 
 22f2382b61ecf0e9ff0dd8f3e812915f 1817 mail extra mailavenger_0.8.2-1.dsc
 696f9745446a3037696fb55b6b690c56 871608 mail extra 
mailavenger_0.8.2.orig.tar.gz
 c9333813ade4aa56ed5c307b3aa0b59f 8816 mail extra 
mailavenger_0.8.2-1.debian.tar.gz
 7f023b9c9355f3a80f1603843cfea675 579758 mail extra 
mailavenger_0.8.2-1_amd64.deb

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

iQIcBAEBCAAGBQJPHz82AAoJEGin9OG0lUUKR4cP+gI0ROYRHnvq29Pk3NSD41l3
7oAnsiXt91DdCdEiHleduQQeUWMnLo1k2pWxbToV5jovob8SITHX0nQkNcpwoPHM
U5qI/5RO/KAa0dyKq+3DUUFLldz8kpreE37IPVebPG6wC+MGOVIuk7hMracXamS8
BEwY7qSfhyXlQ5zcNY8eHw7qOE7d+9Ot03nIMXXEYz4raZGkmJJo/jCJw2FPS+vk
UsYL7554LMUgkGJGEl2LkHI1ZtJfIP4fnuMM1/J3PFMMPjZtP7SC+v8hv39CFCHr
9jRaaX1qQSy64ocykDxEZTEWBHb7UfcMbdzPnAcLLcBVoRVZQkY3tqvN1xhw5JtF
+2ezyomVqViDjssReS

Bug#647247: marked as done (mailavenger FTBFS, can't find berkerly DB)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:48:01 +
with message-id 
and subject line Bug#621440: fixed in mailavenger 0.8.2-1
has caused the Debian Bug report #621440,
regarding mailavenger FTBFS, can't find berkerly DB
to be marked as done.

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

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


-- 
621440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: mailavenger
Version: 0.8.1-3
Severity: serious

While trying to confirm if bug 625391 was a false positive or not I 
discovered that your package FTBFS in unstable for another reason.


checking for BerkeleyDB library... no
configure: error: Cannot find BerkeleyDB
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Build command 'cd mailavenger-0.8.1 && dpkg-buildpackage -b -uc' failed.
E: Child process failed
root@debian:/#configure:18178: checking for BerkeleyDB library
configure:18360: result: no
configure:18364: error: Cannot find BerkeleyDB

config.log didn't give any further information on why the test for 
berkerly DB failed


configure:18178: checking for BerkeleyDB library
configure:18360: result: no
configure:18364: error: Cannot find BerkeleyDB




--- End Message ---
--- Begin Message ---
Source: mailavenger
Source-Version: 0.8.2-1

We believe that the bug you reported is fixed in the latest version of
mailavenger, which is due to be installed in the Debian FTP archive:

mailavenger_0.8.2-1.debian.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2-1.debian.tar.gz
mailavenger_0.8.2-1.dsc
  to main/m/mailavenger/mailavenger_0.8.2-1.dsc
mailavenger_0.8.2-1_amd64.deb
  to main/m/mailavenger/mailavenger_0.8.2-1_amd64.deb
mailavenger_0.8.2.orig.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 621...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
der...@debian.org (supplier of updated mailavenger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Dec 2011 09:24:55 -0300
Source: mailavenger
Binary: mailavenger
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Ulises Vitulli 
Changed-By: der...@debian.org
Description: 
 mailavenger - Highly configurable, MTA-independent SMTP filter server
Closes: 621440 625391 634553 647247
Changes: 
 mailavenger (0.8.2-1) unstable; urgency=low
 .
   * New upstream-coordinated snapshot/release:
 - Fix bdb compatibility on 5.x (Closes: #621440, #634553, #647247)
 - Fix some gcc-4.6 warnings (Closes: #625391).
   * Improve building targets for simplifying portscripts.
   * Clean-up on debian/rules for multiarch support.
   * Dropped local patch for typofixing license documentation.
Checksums-Sha1: 
 10670a7c33dae51d7cb92f9d97cf150b5be4832f 1817 mailavenger_0.8.2-1.dsc
 3aa54a5347f83484db4ab938983bbf98302fd276 871608 mailavenger_0.8.2.orig.tar.gz
 19eaf649b6e5a06ae55789738920c3fc3f626d94 8816 mailavenger_0.8.2-1.debian.tar.gz
 f656779960415bac0ebe3af920b622a9e195bf42 579758 mailavenger_0.8.2-1_amd64.deb
Checksums-Sha256: 
 4fd7ff1f7c562975f44bd67f869e268298530c316f4ed6c74b7cce6b98da11cc 1817 
mailavenger_0.8.2-1.dsc
 6039754a72ba70b78a48a92747e36edfbf617a40afd2dad14290f767a8bfad5f 871608 
mailavenger_0.8.2.orig.tar.gz
 ad01ac1f0029a50f7ee82f4f0e5fae744634533aa96ad344f6d7b9416cd12fd2 8816 
mailavenger_0.8.2-1.debian.tar.gz
 548394e83d24f834d3ef534efbdd280d5760788380b7e95966d3651199f26782 579758 
mailavenger_0.8.2-1_amd64.deb
Files: 
 22f2382b61ecf0e9ff0dd8f3e812915f 1817 mail extra mailavenger_0.8.2-1.dsc
 696f9745446a3037696fb55b6b690c56 871608 mail extra 
mailavenger_0.8.2.orig.tar.gz
 c9333813ade4aa56ed5c307b3aa0b59f 8816 mail extra 
mailavenger_0.8.2-1.debian.tar.gz
 7f023b9c9355f3a80f1603843cfea675 579758 mail extra 
mailavenger_0.8.2-1_amd64.deb

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

iQIcBAEBCAAGBQJPHz82AAoJEGin9OG0lUUKR4cP+gI0ROYRHnvq29Pk3NSD41l3
7oAnsiXt91DdCdEiHleduQQeUWMnLo1k2pWxbToV5jovob8SITHX0nQkNcpwoPHM
U5qI/5RO/KAa0dyKq+3DUUFLldz8kpreE37IPVebPG6wC+MGOVIuk7hMracXamS8
BEwY7qSfhyXlQ5zcNY8eHw7qOE7d+9Ot03nIMXXEYz4raZGkmJJo/jCJw2FPS+vk
UsYL75

Bug#621440: marked as done (Still uses libdb4.8)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:48:01 +
with message-id 
and subject line Bug#621440: fixed in mailavenger 0.8.2-1
has caused the Debian Bug report #621440,
regarding Still uses libdb4.8
to be marked as done.

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

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


-- 
621440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailavenger
Version: 0.8.1-3
Severity: normal
User: pkg-db-de...@lists.alioth.debian.org
Usertags: db5.1

Your package currently still uses Berkeley DB version 4.8 (libdb4.8).

However, there is a newer Berkeley DB version in the archive (libdb5.1),
with a compatible API.  Berkeley DB version 4.8 will be eventually
removed from unstable in favor of version 5.1.

Please port your package to libdb5.1 as soon as possible.  In most cases
only change required is to update build depends from libdb4.8-dev
to libdb-dev, or just recompile the package.

More complicated scenarios:

- Package does check for DB_VERSION_MAJOR == 4 - this should be updated
  to (DB_VERSION_MAJOR > 4) || ((DB_VERSION_MAJOR == 4) && (DB_VERSION_MINOR >= 
XX)).

- Configure checks - sometime there is a list of db-4.8 db-4.6 db-4.2, etc., 
this
  needs to be updated to just db (or db-5.1 db-5 db), or at least list the 'db'
  in the front

You can see example patch in cyrus-imapd-2.2:
http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD

- The packages which use Berkeley DB transactional mode need to upgrade
  the database files before the upgrade.  This is fairly straightforward
  and is well documented on the Berkeley DB website.  But you probably
  already know that because it's not the first Berkeley DB transition.

The example script can be found in the cyrus-imapd-2.4 (not yet released):
http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD

Thanks, 
--
Ondřej Surý 

-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 
'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: mailavenger
Source-Version: 0.8.2-1

We believe that the bug you reported is fixed in the latest version of
mailavenger, which is due to be installed in the Debian FTP archive:

mailavenger_0.8.2-1.debian.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2-1.debian.tar.gz
mailavenger_0.8.2-1.dsc
  to main/m/mailavenger/mailavenger_0.8.2-1.dsc
mailavenger_0.8.2-1_amd64.deb
  to main/m/mailavenger/mailavenger_0.8.2-1_amd64.deb
mailavenger_0.8.2.orig.tar.gz
  to main/m/mailavenger/mailavenger_0.8.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 621...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
der...@debian.org (supplier of updated mailavenger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Dec 2011 09:24:55 -0300
Source: mailavenger
Binary: mailavenger
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Ulises Vitulli 
Changed-By: der...@debian.org
Description: 
 mailavenger - Highly configurable, MTA-independent SMTP filter server
Closes: 621440 625391 634553 647247
Changes: 
 mailavenger (0.8.2-1) unstable; urgency=low
 .
   * New upstream-coordinated snapshot/release:
 - Fix bdb compatibility on 5.x (Closes: #621440, #634553, #647247)
 - Fix some gcc-4.6 warnings (Closes: #625391).
   * Improve building targets for simplifying portscripts.
   * Clean-up on debian/rules for multiarch support.
   * Dropped local patch for typofixing license documentation.
Checksums-Sha1: 
 10670a7c33dae51d7cb92f9d97cf150b5be4832f 1817 mailavenger_0.8.2-1.dsc
 3aa54a5347f83484db4ab938983bbf98302fd276 871608 mailavenger_0.8.2.orig.tar.gz
 19eaf649b6e5a06ae55789738920c3fc3f626d94 8816 mailavenger_0.8.2-1.debian.tar.gz
 f656779960415bac0ebe3af920b622a9e19

Bug#657247: marked as done (mozjs: FTBFS on powerpc: missing NUM_[FG]PR_ARG_REGISTERS symbols)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 23:33:16 +
with message-id 
and subject line Bug#657247: fixed in mozjs 1.8.5-1.0.0+dfsg-3
has caused the Debian Bug report #657247,
regarding mozjs: FTBFS on powerpc: missing NUM_[FG]PR_ARG_REGISTERS symbols
to be marked as done.

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

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


-- 
657247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs
Version: 1.8.5-1.0.0+dfsg-2
Severity: serious
Justification: FTBFS

Hi,

regression on the powerpc side:
| --- debian/libmozjs185-1.0.symbols 
(libmozjs185-1.0_1.8.5-1.0.0+dfsg-2_powerpc)
| +++ dpkg-gensymbolsFknNh2 2012-01-24 22:51:18.0 +
| @@ -528,8 +528,8 @@
|   (arch=armhf)JaegerThrowpoline@Base 1.8.5-1.0.0+dfsg
|   (arch=armhf)JaegerTrampoline@Base 1.8.5-1.0.0+dfsg
|   (arch=armhf)JaegerTrampolineReturn@Base 1.8.5-1.0.0+dfsg
| - (arch=powerpc)NUM_FPR_ARG_REGISTERS@Base 1.8.5-1.0.0+dfsg
| - (arch=powerpc)NUM_GPR_ARG_REGISTERS@Base 1.8.5-1.0.0+dfsg
| +#MISSING: 1.8.5-1.0.0+dfsg-2# (arch=powerpc)NUM_FPR_ARG_REGISTERS@Base 
1.8.5-1.0.0+dfsg
| +#MISSING: 1.8.5-1.0.0+dfsg-2# (arch=powerpc)NUM_GPR_ARG_REGISTERS@Base 
1.8.5-1.0.0+dfsg
|   (arch=!amd64 !ia64 !kfreebsd-amd64 
!s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base 
1.8.5-1.0.0+dfsg
|   (arch=amd64 ia64 kfreebsd-amd64 
s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base 
1.8.5-1.0.0+dfsg
|   _Z14js_DateGetDateP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg

Full build logs:
  https://buildd.debian.org/status/package.php?p=mozjs&suite=sid

Mraw,
KiBi.


--- End Message ---
--- Begin Message ---
Source: mozjs
Source-Version: 1.8.5-1.0.0+dfsg-3

We believe that the bug you reported is fixed in the latest version of
mozjs, which is due to be installed in the Debian FTP archive:

libmozjs185-1.0_1.8.5-1.0.0+dfsg-3_amd64.deb
  to main/m/mozjs/libmozjs185-1.0_1.8.5-1.0.0+dfsg-3_amd64.deb
libmozjs185-dev_1.8.5-1.0.0+dfsg-3_amd64.deb
  to main/m/mozjs/libmozjs185-dev_1.8.5-1.0.0+dfsg-3_amd64.deb
mozjs_1.8.5-1.0.0+dfsg-3.debian.tar.gz
  to main/m/mozjs/mozjs_1.8.5-1.0.0+dfsg-3.debian.tar.gz
mozjs_1.8.5-1.0.0+dfsg-3.dsc
  to main/m/mozjs/mozjs_1.8.5-1.0.0+dfsg-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 657...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Coulson  (supplier of updated mozjs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Jan 2012 23:05:41 +
Source: mozjs
Binary: libmozjs185-1.0 libmozjs185-dev
Architecture: source amd64
Version: 1.8.5-1.0.0+dfsg-3
Distribution: unstable
Urgency: low
Maintainer: Chris Coulson 
Changed-By: Chris Coulson 
Description: 
 libmozjs185-1.0 - Spidermonkey javascript engine
 libmozjs185-dev - Spidermonkey javascript library - development headers
Closes: 657247
Changes: 
 mozjs (1.8.5-1.0.0+dfsg-3) unstable; urgency=low
 .
   * Drop a couple of symbols that were exposed from the internal libffi
 on powerpc (Closes: #657247)
 - update debian/libmozjs185-1.0.symbols
Checksums-Sha1: 
 324d0c4a02c4a6715f1167de067ad318babb929d 1997 mozjs_1.8.5-1.0.0+dfsg-3.dsc
 d9a635796e6862585cbb51beb9af064ba4845783 53933 
mozjs_1.8.5-1.0.0+dfsg-3.debian.tar.gz
 02d29c7a05a72ba41f3e623f230db906d94dbccb 1341194 
libmozjs185-1.0_1.8.5-1.0.0+dfsg-3_amd64.deb
 c094f5a6c848af7b2b87b827bb0f1261f1f1802a 2131222 
libmozjs185-dev_1.8.5-1.0.0+dfsg-3_amd64.deb
Checksums-Sha256: 
 d52bc23de5df37a543c8d9faeca3a24ca3ac3c1c0141816d555c4d2eb9b30b41 1997 
mozjs_1.8.5-1.0.0+dfsg-3.dsc
 fad19dfc8e9aec7911f7e68e08b0a56e33c1033b4b02547e98870128b5797469 53933 
mozjs_1.8.5-1.0.0+dfsg-3.debian.tar.gz
 25506cd606958d9184c9437b6ab52410d9df18788112f3acc8a43eca99633fd5 1341194 
libmozjs185-1.0_1.8.5-1.0.0+dfsg-3_amd64.deb
 6f88aff9822c616dcf3e1e5c199e539e0b9f7dfeb8a8665b140acd6136a6da2f 2131222 
libmozjs185-dev_1.8.5-1.0.0+dfsg-3_amd64.deb
Files: 
 28bcc16778448b6bcb9d54d402111338 1997 libs extra mozjs_1.8.5-1.0.0+dfsg-3.dsc
 ee4e8cf94cd597fbd0907cb1f97617f3 53933 libs extra 
mozjs_1.8.5-1.0.0+dfsg-3.debian.tar.gz
 f860f2396f7a94f6d19322f0717c861e 1341194 libs extra 
libmozjs185-1.0_1.8.5-1.0.0+dfsg-3_amd

Processed: severity of 645807 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #This really deserves a higher severity as a potential dfsg violation.
> severity 645807 serious
Bug #645807 [beav] DFSG Violation In BEAV
Severity set to 'serious' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657247: mozjs: FTBFS on powerpc: missing NUM_[FG]PR_ARG_REGISTERS symbols

[Cyril Brulebois]

Source: mozjs
Version: 1.8.5-1.0.0+dfsg-2
Severity: serious
Justification: FTBFS

Hi,

regression on the powerpc side:
| --- debian/libmozjs185-1.0.symbols 
(libmozjs185-1.0_1.8.5-1.0.0+dfsg-2_powerpc)
| +++ dpkg-gensymbolsFknNh2 2012-01-24 22:51:18.0 +
| @@ -528,8 +528,8 @@
|   (arch=armhf)JaegerThrowpoline@Base 1.8.5-1.0.0+dfsg
|   (arch=armhf)JaegerTrampoline@Base 1.8.5-1.0.0+dfsg
|   (arch=armhf)JaegerTrampolineReturn@Base 1.8.5-1.0.0+dfsg
| - (arch=powerpc)NUM_FPR_ARG_REGISTERS@Base 1.8.5-1.0.0+dfsg
| - (arch=powerpc)NUM_GPR_ARG_REGISTERS@Base 1.8.5-1.0.0+dfsg
| +#MISSING: 1.8.5-1.0.0+dfsg-2# (arch=powerpc)NUM_FPR_ARG_REGISTERS@Base 
1.8.5-1.0.0+dfsg
| +#MISSING: 1.8.5-1.0.0+dfsg-2# (arch=powerpc)NUM_GPR_ARG_REGISTERS@Base 
1.8.5-1.0.0+dfsg
|   (arch=!amd64 !ia64 !kfreebsd-amd64 
!s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base 
1.8.5-1.0.0+dfsg
|   (arch=amd64 ia64 kfreebsd-amd64 
s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base 
1.8.5-1.0.0+dfsg
|   _Z14js_DateGetDateP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg

Full build logs:
  https://buildd.debian.org/status/package.php?p=mozjs&suite=sid

Mraw,
KiBi.



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

Bug#657245: blender: possible dfsg violation in release/windows/ subdirectory

[Karl Goetz]

Package: blender
Severity: serious
Justification: fails dfsg (disallows commercial distribution)
User: gnewsense-...@nongnu.org
Usertags: gnewsense libreplanet


Hi,
Someone has pointed out [1] that blender may have a dfsg violation in
the release/windows subtree.
In release/windows/ installer/02.copyright.txt and
release/windows/publ_installer/02.copyright.txt it contains text
detailing various restrictions in relation to "The software"

[1] https://savannah.nongnu.org/bugs/?34590

If you disagree this particular bunding is a problem, feel free to
downgrade this report, but the licence doesn't specify if it applies
only to binaries or not.

Also to note, it only affects stable, all recent releases have this
problem resolved.
thanks,
kk


-- System Information:
Debian Release: 6.0.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

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


-- 
Karl Goetz, (Kamping_Kaiser / VK7FOSS)
http://www.kgoetz.id.au
No, I won't join your social networking group


signature.asc
Description: PGP signature

Bug#657244: batik bundles a non free colour profile in pdf-transcoder.jar

[Karl Goetz]

Package: batik
Severity: serious
Justification: may not be distributed without fee if modified
User: gnewsense-...@nongnu.org
Usertags: gnewsense libreplanet

Hi,
>From [1], it seems the pdf-transcoder.jar in batik contains a colour  
profile with a crazy licence.
 "...permission to use, copy and distribute this file for any purpose is
 hereby granted without fee, provided that the file is not changed
 including the HP copyright notice tag, ... "

The file will need to be removed from the jar, or the jar (and pdf
support) removed from batik :/

[1] https://savannah.nongnu.org/bugs/?34579
thanks,
kk


-- System Information:
Debian Release: 6.0.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

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

-- 
Karl Goetz, (Kamping_Kaiser / VK7FOSS)
http://www.kgoetz.id.au
No, I won't join your social networking group


signature.asc
Description: PGP signature

Processed: Re: [Pkg-libvirt-maintainers] Bug#654849: gtk-vnc: FTBFS with GModule-2.0.gir:46.7-46.66: error: unknown child element `function' in `record'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 654849 gtk-vnc FTBFS if /etc/alternatives/valac uses valac-0.12
Bug #654849 [gtk-vnc] gtk-vnc: FTBFS with GModule-2.0.gir:46.7-46.66: error: 
unknown child element `function' in `record'
Changed Bug title to 'gtk-vnc FTBFS if /etc/alternatives/valac uses valac-0.12' 
from 'gtk-vnc: FTBFS with GModule-2.0.gir:46.7-46.66: error: unknown child 
element `function' in `record''
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
654849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#654849: [Pkg-libvirt-maintainers] Bug#654849: gtk-vnc: FTBFS with GModule-2.0.gir:46.7-46.66: error: unknown child element `function' in `record'

[Daniel Kahn Gillmor]

retitle 654849 gtk-vnc FTBFS if /etc/alternatives/valac uses valac-0.12
thanks

On 01/24/2012 05:23 PM, Guido Günther wrote:
> I'd assume that this is somehow related to the installed vala packages.
> We have valac 0.14 and 0.12 in the archives. Could you check if the non
> chroot build picks up something different in that area? Sorry for being
> vague here, but I've got no clear idea either.

That's way less vague than my mind was about it, so that's good :)

The full system both valac-0.12 and valac-0.14, and
/etc/alternatives/vala and valac both pointed to valac-0.12.  the chroot
only had 0.14.

Installing valac-0.12 in the chroot let update-alternatives pick it up
as the default, and then i get the failure within the chroot.

So this bug is that valac-0.12 can't effectively build gtk-vnc.

Does this mean gtk-vnc needs a Build-Conflicts: valac-0.12 or something?
 i don't know what the right way to resolve this is, but maybe the vala
maintainers can suggest something?  I've tried to cc them here.

Thanks for helping narrow it down!

--dkg



signature.asc
Description: OpenPGP digital signature

Bug#656722: marked as done (mozjs: Various issues with the package)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 22:33:56 +
with message-id 
and subject line Bug#656722: fixed in mozjs 1.8.5-1.0.0+dfsg-2
has caused the Debian Bug report #656722,
regarding mozjs: Various issues with the package
to be marked as done.

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

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


-- 
656722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs
Version: 1.8.5-1.0.0+dfsg-1
Severity: important

(I'm even tempted with an RC severity)

>From a quick glance at the source:
- You're building for armv7 on armel, which you definitely mustn't
- You're building as thumb2 on armel, which you shouldn't
- You're not building against system libffi
- You're missing a lot of important patches that were applied to the js
 engine in iceweasel 4, which is what mozjs185 is:
  - system-libs/Allow-to-build-against-system-libffi.patch
  - porting/Force-NativeARM.o-to-have-arch-armv4t-in-its-.ARM.at.patch
  - porting/Bug-638056-Avoid-The-cacheFlush-support-is-missing-o.patch
  - fixes/Bug-626035-Modify-the-way-arm-compiler-flags-are-set.patch
  - fixes/Bug-589744-Fallback-to-perf-measurement-stub-when-pe.patch
  All of which you can find in 
http://anonscm.debian.org/gitweb/?p=pkg-mozilla/iceweasel.git;a=tree;f=debian/patches;h=d39e60694aa430282907eda7aa91a2dc2f0f2740;hb=42523889c524368b82e935eb0dbde8059003bbe5

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

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


--- End Message ---
--- Begin Message ---
Source: mozjs
Source-Version: 1.8.5-1.0.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
mozjs, which is due to be installed in the Debian FTP archive:

libmozjs185-1.0_1.8.5-1.0.0+dfsg-2_amd64.deb
  to main/m/mozjs/libmozjs185-1.0_1.8.5-1.0.0+dfsg-2_amd64.deb
libmozjs185-dev_1.8.5-1.0.0+dfsg-2_amd64.deb
  to main/m/mozjs/libmozjs185-dev_1.8.5-1.0.0+dfsg-2_amd64.deb
mozjs_1.8.5-1.0.0+dfsg-2.debian.tar.gz
  to main/m/mozjs/mozjs_1.8.5-1.0.0+dfsg-2.debian.tar.gz
mozjs_1.8.5-1.0.0+dfsg-2.dsc
  to main/m/mozjs/mozjs_1.8.5-1.0.0+dfsg-2.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 656...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Coulson  (supplier of updated mozjs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Jan 2012 21:38:44 +
Source: mozjs
Binary: libmozjs185-1.0 libmozjs185-dev
Architecture: source amd64
Version: 1.8.5-1.0.0+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Chris Coulson 
Changed-By: Chris Coulson 
Description: 
 libmozjs185-1.0 - Spidermonkey javascript engine
 libmozjs185-dev - Spidermonkey javascript library - development headers
Closes: 656722
Changes: 
 mozjs (1.8.5-1.0.0+dfsg-2) unstable; urgency=low
 .
   [ Michael Biebl ]
   * Fix various issues in the package. Thanks a lot Mike Hommey for the
 patches and the help tracking down those build failures. (Closes: #656722)
   * Fix build failures on arm and disable thumb2 support for Debian builds
 (but keep it enabled for Ubuntu builds).
 - Add Bug-626035-Modify-the-way-arm-compiler-flags-are-set.patch.
 - Remove no-neon-or-softfp-on-arm patch.
 - Force-NativeARM.o-to-have-arch-armv4t-in-its-.ARM.at.patch.
 - Disable methodjit support on armel for Debian builds.
   * Fix "The cacheFlush support is missing on this platform" build failure on
 mips, ia64 and s390.
 - Add Bug-638056-Avoid-The-cacheFlush-support-is-missing-o.patch
   * Build against the system libffi library.
 - Add Allow-to-build-against-system-libffi.patch.
 - Add Build-Depends on libffi-dev and pkg-config.
 - Pass --enable-system-ffi to ./configure.
   * Fix build failure on 64bit big endian architecture (s390).
 - Add 64bit-big-endian.patch.
   * Fix broken library symlinks on "make install" when using DESTDIR instead
 of creating those symlinks manually.
 - Add destdir.patch.
 - Remove debian/libmozjs185-{1.0,dev}.links.
 - Updat

Bug#631283: marked as done (CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 22:34:08 +
with message-id 
and subject line Bug#631283: fixed in php-suhosin 0.9.33-1
has caused the Debian Bug report #631283,
regarding CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows 
different password pairs to produce the same hash
to be marked as done.

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

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


-- 
631283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-suhosin
Severity: serious
Tags: security

Hi,
The CVE (Common Vulnerabilities & Exposures) CVE-2011-2483 was
published for php5-suhosin.

A bug in crypt_blowfish was reported [1,2,3]. The function BF_set_key from 
crypt_blowfish.c:554 looks vulnerable. The RH report may be useful[4] too.

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.

[1] http://www.openwall.com/lists/oss-security/2011/06/20/2
[2] http://www.openwall.com/lists/john-dev/2011/06/20/3
[3] http://www.openwall.com/lists/john-dev/2011/06/20/5
[4] https://bugzilla.redhat.com/show_bug.cgi?id=715025

-luciano


--- End Message ---
--- Begin Message ---
Source: php-suhosin
Source-Version: 0.9.33-1

We believe that the bug you reported is fixed in the latest version of
php-suhosin, which is due to be installed in the Debian FTP archive:

php-suhosin_0.9.33-1.diff.gz
  to main/p/php-suhosin/php-suhosin_0.9.33-1.diff.gz
php-suhosin_0.9.33-1.dsc
  to main/p/php-suhosin/php-suhosin_0.9.33-1.dsc
php-suhosin_0.9.33.orig.tar.gz
  to main/p/php-suhosin/php-suhosin_0.9.33.orig.tar.gz
php5-suhosin_0.9.33-1_i386.deb
  to main/p/php-suhosin/php5-suhosin_0.9.33-1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 631...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Wagner  (supplier of updated php-suhosin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 24 Jan 2012 23:09:33 +0100
Source: php-suhosin
Binary: php5-suhosin
Architecture: source i386
Version: 0.9.33-1
Distribution: unstable
Urgency: low
Maintainer: php-suhosin maintainers 
Changed-By: Jan Wagner 
Description: 
 php5-suhosin - advanced protection module for php5
Closes: 631283 657190
Changes: 
 php-suhosin (0.9.33-1) unstable; urgency=low
 .
   * New upstream version (Closes: #657190, #631283)
 - Fixed stack based buffer overflow in transparent cookie encryption
 - Fixed environment variables for logging do not go through the filter
   extension anymore
 - Fixed that disabling HTTP response splitting protection also disabled
   NUL byte protection in HTTP headers
 - Removed crypt() support - because not used for PHP >= 5.3.0 anyway
   * Update watch file, upstream changed naming scheme
Checksums-Sha1: 
 ac2ed250f8ba273036d1038d786a8c1071467bda 1360 php-suhosin_0.9.33-1.dsc
 abb30c22e7fe341955b42ec71ed597c43439e2b8 104488 php-suhosin_0.9.33.orig.tar.gz
 1f924e6df42e67cf0c6c9e438571363c51baf8c7 7942 php-suhosin_0.9.33-1.diff.gz
 698b72ffe0879f7059104af871e77f612b4007ef 76602 php5-suhosin_0.9.33-1_i386.deb
Checksums-Sha256: 
 63c56a78500e7f6c7b046dfb7b91a0b622633e0f672c8544db02071b6b4f1948 1360 
php-suhosin_0.9.33-1.dsc
 865b1c72bae9a5a710fe0b07a0635556ce6c838653ec364d2a2a6e6f594529c5 104488 
php-suhosin_0.9.33.orig.tar.gz
 318fc0bf5a26ec7e795c670272515fff6313bab7c17ed52162ae9e40b089aca2 7942 
php-suhosin_0.9.33-1.diff.gz
 51c3382e76e4deabaddfde25a98f88fb260dca14c6ac333bfd342cb5b1c90eb6 76602 
php5-suhosin_0.9.33-1_i386.deb
Files: 
 c32190c0f4d18bc6418e6a89685ce1e3 1360 php optional php-suhosin_0.9.33-1.dsc
 0ce498a02a8281e4274ea8e390c2b487 104488 php optional 
php-suhosin_0.9.33.orig.tar.gz
 3112fd751c7f09e4c397daec3caec657 7942 php optional php-suhosin_0.9.33-1.diff.gz
 e4300b79e2e5be45ac157ae3b71af5f2 76602 php optional 
php5-suhosin_0.9.33-1_i386.deb

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

iD8DBQFPHy2H9u6Dud+QFyQRApY6AJsHJVh6oZ0lyvazQNnVEYO5hepGbQCg99P+
RDr+35O709jbOUonzAIieNA=
=2ciy
-END PGP SIGNATURE-


--- End Message ---

Processed: tagging 616694

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # builds on squeeze just fine, please justify removal of release tag, luk
> tags 616694 + wheezy sid
Bug #616694 {Done: Rob Browning } [src:guile-1.8] 
guile-1.8: FTBFS: unknown doc attribute
Added tag(s) sid and wheezy.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
616694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#654849: [Pkg-libvirt-maintainers] Bug#654849: gtk-vnc: FTBFS with GModule-2.0.gir:46.7-46.66: error: unknown child element `function' in `record'

[Guido Günther]

On Tue, Jan 24, 2012 at 11:57:06AM -0500, Daniel Kahn Gillmor wrote:
> On 01/23/2012 06:07 PM, Guido Günther wrote:
> > I can't seem to reproduct this in a clean amd64 sid chroot. Are you
> > still seeing this?
> 
> Hm, this is still reproducible for me in an up-to-date sid i386 system
> that i've been keeping updated for several months now.
> 
> But i made a fresh chroot on the same machine, and did nothing in it but:
> 
>  apt-get install build-essential fakeroot
>  apt-get build-dep gtk-vnc
> 
> and then tried to rebuild gtk-vnc 0.5.0-2, and it built cleanly.
> 
> So something is amiss in the regularly-upgraded build environment, but
> i'm not sure what it is, or how or why it breaks the build for gtk-vnc.
I'd assume that this is somehow related to the installed vala packages.
We have valac 0.14 and 0.12 in the archives. Could you check if the non
chroot build picks up something different in that area? Sorry for being
vague here, but I've got no clear idea either.
Cheers and thanks for reporting back,
 -- Guido



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

Bug#636923: RM: libwww5.808-perl -- RC-buggy, NPOASR

[Jonathan Nieder]

Andreas Tille wrote:

>Moreover we have a Debian Med sprint this
> weekend where issues like this will be explicitely addressed.

Thanks, that's great to hear.  The event sounds excellent (in other
ways, too).

Jonathan



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

Bug#657055: haskell-hsql-postgresql-doc: fails to upgrade from squeeze - trying to overwrite ...

[Joachim Breitner]

Dear Holger,

Am Dienstag, den 24.01.2012, 21:33 +0100 schrieb Holger Levsen:
> On Dienstag, 24. Januar 2012, Joachim Breitner wrote:
> > Am Montag, den 23.01.2012, 20:46 +0100 schrieb Holger Levsen:
> > > Similar bugs affect _a lot_ of haskell-*-doc packages, please have a look
> > > at the logs linked from:
> > > 
> > > http://piuparts.debian.org/squeeze2wheezy/overwrite_other_packages_files_
> > > error.html
> [list omitted]
> > 
> > hmm, is that a complete list, or just those that have been checked so
> > far?
> 
> thats the complete list for sid, but keep in mind that packages depending on 
> those broken ones are not tested :)
> 
> just visit that url again, it's updated daily.

thanks for that information; this means that our general approach
worked, but just these cases are special for one or the other reason.
Good :-)

In the case of haskell-split, the reason seems to be the existence of
a /usr/share/doc-base/haskell-split-api file, something that only few
packages have.

So the right course of actions seems to be to just fix the few cases on
http://piuparts.debian.org/squeeze2wheezy/overwrite_other_packages_files_error.html
 individually, as we did before. Maybe I’ll get to it in the next few days.

Greetings,
Joachim


-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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

Bug#657199: libgpiv: FTBFS against hdf5 1.8.8

[Gerber van der Graaf]

Thanks, I will have a look at it. Gerber


On Tue, 2012-01-24 at 20:49 +0100, Julien Cristau wrote:
> Source: libgpiv
> Version: 0.6.1-3
> Severity: serious
> Tags: wheezy sid
> Justification: fails to build from source (but built successfully in the past)
> 
> It looks like API changes in hdf5 break libgpiv:
> https://buildd.debian.org/status/fetch.php?pkg=libgpiv&arch=s390x&ver=0.6.1-3&stamp=1326908982
> 
> Cheers,
> Julien





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

Bug#636923: [Debian-med-packaging] Bug#636923: RM: libwww5.808-perl -- RC-buggy, NPOASR

[Steffen Möller]

> original
> maintainers just pushed a broken package to experimental and take this
> distribution as an excuse not to care any more.

No really. The current packaging exactly matches the official
build instructions for Ensembl. That is quite a strong point,
at least for me. Any deviation from that will not necessarily
be welcome.

> I also addressed this
> and I will try to actively care about this in the next couple of weeks.
> I think this bug could serve as a handle to make them care more for
> this package which has quite some importance for them.  So please
> stay a bit tuned, we are working on this.

IMO the issue needs talking more than programming. And that takes time.
And this sprint.

Steffen



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

Bug#636923: [Debian-med-packaging] RM: libwww5.808-perl -- RC-buggy, NPOASR

[Steffen Möller]

Hello,

On 01/24/2012 09:36 PM, Jonathan Nieder wrote:
> reassign 636923 ensembl 63-1
> severity 636923 serious
> quit
> 
> Hi,
> 
> Luca Falavigna wrote:
> 
>> As there's little the FTP Team can do at this point, I'm reassigning
>> this bug to libwww5.808-perl source package, pending a proper fix.
> 
> Since the original report last April, we haven't heard from the
> libwww5.808-perl maintainers at all.  I have run into this same
> problem on multiple machines now, and no one seems to think the
> package's existence is sane, so I'm tempted to suggest just removing
> it, with ensembl as an unfortunate casualty.

Sigh. Wait, please.

> The ensembl package description explains:
> 
>   libwww-perl5.808 will conflict with the latest libwww-perl
>   installation and thus force a downgrade to 5.808, which will disable
>   many other tools on your system. Therefore it is advisable NOT to
>   install this package in parallel with any other software, and/or use
>   a virtual machine or dedicated machine.
> 
> which does not sound like a package that I would expect to find in the
> archive.

But it is not in the archive. It is in experimental, not? Please do
not put too much pressure on us here. Give us time to critical mass
ourselves a bit more.

> However, maybe the ensembl maintainers can come up with some method
> for avoiding this?  E.g., [1] seems to have some ideas that would not
> require such an invasive package.  Cc-ing them.

The package was created for cloud or chroot setups, not for your average
desktop.

We have our Debian Med sprint this week and I take the opportunity to
discuss things there. My personal position is that the change either goes 
through
upstream or it will not happen. If the removal of the package is a consequence,
then so be it. Mysteriously, those folks run more after the science than
after their "working for them" libraries. So, take note, there are apparently
some communities even more stable than Debian stable :o)

Steffen





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

Bug#238245: marked as done (Open Publication License is not DFSG Free)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 17:54:56 -0400
with message-id <4f1f28b0.20...@debian.org>
and subject line Re: Bug#238245: license choice - consensus on dual MIT/GPL-2+
has caused the Debian Bug report #238245,
regarding Open Publication License is not DFSG Free
to be marked as done.

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

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


-- 
238245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=238245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: wishlist

Debian WWW Pages are distributed under the Open Publication
License.  However, it is incompatible with the GNU GPL.

I hope that the Debian WWW Pages will be clearly free and
compatible with the GNU GPL.

See also debian-legal archive:

http://lists.debian.org/debian-legal/2003/debian-legal-200305/threads.html#3

-- 
Tatsuya Kinoshita

--- End Message ---
--- Begin Message ---
Le 24/01/2012 05:41, Stefano Zacchiroli a écrit :

> It seems we've consensus on the license choice \o/
> 
> On Sat, Jan 21, 2012 at 12:57:59PM -0400, David Prévot wrote:
[…]
>> +GNU General Public License; either
>> +version??2 of the License, or any later version (the latest version is
>   ^^^
> as a minor nitpick, I would add "(at your option)" here.

Sure, I thought it wasn't needed, thanks for the fix.

> Looking forward for David to push the big red button :-)

Done, it will be online in three or four hours (I pick tomorrow's date
to be on the safe side). Thanks a lot Stefano for pushing to an accurate
solution of this long standing issue.

We'll soon update #388141 to document the status of pages that were
edited before now, the relicensing workflow and alike, but I'm really
happy to press now the big red button for this first step!

Cheers

David



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#631283: marked as done (CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 22:43:44 +0100
with message-id <201201242243.48592.w...@cyconet.org>
and subject line Re: Bug#631283: CVE-2011-2483 crypt_blowfish: 8-bit character 
mishandling allows different password pairs to produce the same hash
has caused the Debian Bug report #631283,
regarding CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows 
different password pairs to produce the same hash
to be marked as done.

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

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


-- 
631283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-suhosin
Severity: serious
Tags: security

Hi,
The CVE (Common Vulnerabilities & Exposures) CVE-2011-2483 was
published for php5-suhosin.

A bug in crypt_blowfish was reported [1,2,3]. The function BF_set_key from 
crypt_blowfish.c:554 looks vulnerable. The RH report may be useful[4] too.

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.

[1] http://www.openwall.com/lists/oss-security/2011/06/20/2
[2] http://www.openwall.com/lists/john-dev/2011/06/20/3
[3] http://www.openwall.com/lists/john-dev/2011/06/20/5
[4] https://bugzilla.redhat.com/show_bug.cgi?id=715025

-luciano


--- End Message ---
--- Begin Message ---
Hi Luciano,

I contacted upstream about the issue.

On Mittwoch 22 Juni 2011, Luciano Bello wrote:
> The CVE (Common Vulnerabilities & Exposures) CVE-2011-2483 was
> published for php5-suhosin.
> 
> A bug in crypt_blowfish was reported [1,2,3]. The function BF_set_key from
> crypt_blowfish.c:554 looks vulnerable. The RH report may be useful[4] too.
> 
> If you fix the vulnerability please also make sure to include the
> CVE id in your changelog entry.

The broken code is not used since php 5.3 and so this is a theoretical 
vulnerability (in the unused code). As we are shipping php 5.3 with stable, 
this should not be an issue.
Anyways ... the unsued code is removed with recent upstream release.

With kind regards, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y 
--END GEEK CODE BLOCK--


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

Bug#657217: bip: buffer overflow (CVE-2012-0806)

[Luciano Bello]

Package: bip
Severity: grave
Tags: security patch

The following vulnerability had been reported against bip: 
https://projects.duckcorp.org/issues/269

The patch can be found here: 
https://projects.duckcorp.org/projects/bip/repository/revisions/222a33cb84a2e52ad55a88900b7895bf9dd0262c

This bug is present in 0.8.8 and previous versions and, according to reporter, 
remote execution of code should be possible.

Please use CVE-2012-0806 for this issue.

/luciano



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

Bug#636923: RM: libwww5.808-perl -- RC-buggy, NPOASR

[Andreas Tille]

Hi Jonathan,

I can confirm that I'm working on Ensembl and I'm in contact with
upstream since beginning of this year to work on a strategy to get rid
of this nasty dependency.  Moreover we have a Debian Med sprint this
weekend where issues like this will be explicitely addressed.

I admit that I'm also not very happy about the fact that original
maintainers just pushed a broken package to experimental and take this
distribution as an excuse not to care any more.  I also addressed this
and I will try to actively care about this in the next couple of weeks.
I think this bug could serve as a handle to make them care more for
this package which has quite some importance for them.  So please
stay a bit tuned, we are working on this.

Kind regards

  Andreas.

On Tue, Jan 24, 2012 at 02:36:09PM -0600, Jonathan Nieder wrote:
> reassign 636923 ensembl 63-1
> severity 636923 serious
> quit
> 
> Hi,
> 
> Luca Falavigna wrote:
> 
> > As there's little the FTP Team can do at this point, I'm reassigning
> > this bug to libwww5.808-perl source package, pending a proper fix.
> 
> Since the original report last April, we haven't heard from the
> libwww5.808-perl maintainers at all.  I have run into this same
> problem on multiple machines now, and no one seems to think the
> package's existence is sane, so I'm tempted to suggest just removing
> it, with ensembl as an unfortunate casualty.
> 
> The ensembl package description explains:
> 
>   libwww-perl5.808 will conflict with the latest libwww-perl
>   installation and thus force a downgrade to 5.808, which will disable
>   many other tools on your system. Therefore it is advisable NOT to
>   install this package in parallel with any other software, and/or use
>   a virtual machine or dedicated machine.
> 
> which does not sound like a package that I would expect to find in the
> archive.
> 
> However, maybe the ensembl maintainers can come up with some method
> for avoiding this?  E.g., [1] seems to have some ideas that would not
> require such an invasive package.  Cc-ing them.
> 
> Thanks,
> Jonathan
> 
> [1] http://bugs.debian.org/593568#25
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de



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

Bug#631566: psmisc: FTBFS: fuser.c:1904:11: error: EBADE undeclared (first use, in this function)

[peter green]

This is a gentle poke to remind you that an rc bug on your package had a 
patch submitted over

3 months ago which has still not been uploaded or otherwise responded to.



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

Bug#655789: marked as done (wv: FTBFS: configure: error: * * * libwmf >= 0.2.1 required * * *)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 21:03:35 +
with message-id 
and subject line Bug#655789: fixed in wv 1.2.9-0.1
has caused the Debian Bug report #655789,
regarding wv: FTBFS: configure: error: * * * libwmf >= 0.2.1 required * * *
to be marked as done.

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

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


-- 
655789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wv
Version: 1.2.4-2.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 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
> ln -sf /usr/share/misc/config.sub /usr/share/misc/config.guess .
> # Backup files due to modifications below and autoreconf
> for f in aclocal.m4 *.in */*.in *.am configure INSTALL depcomp install-sh 
> ltmain.sh missing mkinstalldirs; do cp $f $f.orig; done
> # autoreconf requires these
> touch NEWS AUTHORS ChangeLog
> # See http://wiki.debian.org/RpathIssue
> sed --in-place --regexp-extended 's/(hardcode_into_libs)=.*/\1=no/' 
> ./configure aclocal.m4
> sed --in-place --regexp-extended 's/(CFLAGS|CPPFLAGS)/AM_\1/' GNUmakefile.am
> autoreconf -vfi
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal --force 
> autoreconf: configure.ac: tracing
> autoreconf: running: libtoolize --copy --force
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> autoreconf: running: /usr/bin/autoconf --force
> autoreconf: running: /usr/bin/autoheader --force
> autoreconf: running: automake --add-missing --copy --force-missing
> autoreconf: Leaving directory `.'
> ./configure --prefix=/usr --mandir=/usr/share/man --with-libwmf 
> --build=x86_64-linux-gnu
> 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 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 for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for gawk... (cached) mawk
> checking whether ln -s works... yes
> checking whether make sets $(MAKE)... (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 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 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
> checkin

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 21:02:29 +
with message-id 
and subject line Bug#655783: fixed in gdcm 2.2.0-1
has caused the Debian Bug report #655783,
regarding itksnap: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
to be marked as done.

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

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


-- 
655783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: itksnap
Version: 2.2.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /usr/bin/c++ -ftemplate-depth-50 -Wall -Wno-deprecated  -Wno-deprecated   
> -Wl,--as-needed   CMakeFiles/InsightSNAP.dir/UserInterface/SNAPMain.cxx.o  -o 
> InsightSNAP -rdynamic -L/usr/lib/InsightToolkit 
> -L/tmp/buildd/gdcm-2.0.19/obj-x86_64-linux-gnu/bin/. -lITKAlgorithms 
> -lITKCommon -lITKBasicFilters libitksnapui.a libitksnaplogic.a 
> Utilities/FLTK/Fl_Table/libfltk_table.a 
> Utilities/FLTK/Fl_Native_File_Chooser/libfltk_native_file_chooser.a -lfltk 
> -lfltk_forms -lfltk_images -lfltk_gl -lpng -ljpeg -lz -lSM -lICE -lX11 -lXext 
> -lXft -lXinerama -lm -lITKIO /usr/lib/libvtkCommon.so.5.8.0 
> /usr/lib/libvtkRendering.so.5.8.0 /usr/lib/libvtkFiltering.so.5.8.0 
> /usr/lib/libvtkGraphics.so.5.8.0 /usr/lib/libvtkImaging.so.5.8.0 
> /usr/lib/libvtkIO.so.5.8.0 -lGLU -lGL -lSM -lICE -lX11 -lXext -lGLU 
> -lITKAlgorithms -lITKStatistics -litkNetlibSlatec -lITKNumerics -lfftw3 
> -lfftw3_threads -lfftw3f -lfftw3f_threads -lITKBasicFilters 
> /usr/lib/libvtkFiltering.so.5.8.0 /usr/lib/libvtkCommon.so.5.8.0 
> /usr/lib/libvtksys.so.5.8.0 -lXft -lXinerama -lm -lGL -lITKIO -lITKNrrdIO 
> /usr/lib/libgdcmMSFF.so.2.0.19 /usr/lib/libgdcmDICT.so.2.0.19 
> /usr/lib/libgdcmIOD.so.2.0.19 /usr/lib/libgdcmDSED.so.2.0.19 
> /usr/lib/libgdcmCommon.so.2.0.19 -litkjpeg8 -lpng -ltiff -lITKSpatialObject 
> -lITKMetaIO -lITKDICOMParser -lITKEXPAT -lITKniftiio -lITKznz -lz 
> -lITKTransformIOReview -lITKCommon -litkvnl_inst -litkvnl_algo 
> -litkv3p_netlib -litkvnl -litkvcl -litkv3p_lsqr -lm -litksys -lpthread -ldl 
> -lm 
> -Wl,-rpath,/usr/lib/InsightToolkit:/tmp/buildd/gdcm-2.0.19/obj-x86_64-linux-gnu/bin/.:
>  
> /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libITKIO.so: undefined 
> reference to `gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
> collect2: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/itksnap_2.2.0-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 2.2.0-1

We believe that the bug you reported is fixed in the latest version of
gdcm, which is due to be installed in the Debian FTP archive:

gdcm_2.2.0-1.debian.tar.gz
  to main/g/gdcm/gdcm_2.2.0-1.debian.tar.gz
gdcm_2.2.0-1.dsc
  to main/g/gdcm/gdcm_2.2.0-1.dsc
gdcm_2.2.0.orig.tar.gz
  to main/g/gdcm/gdcm_2.2.0.orig.tar.gz
libgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-cil_2.2.0-1_amd64.deb
libgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-java_2.2.0-1_amd64.deb
libgdcm-tools_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-tools_2.2.0-1_amd64.deb
libgdcm2-dev_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2-dev_2.2.0-1_amd64.deb
libgdcm2.2-dbg_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2.2-dbg_2.2.0-1_amd64.deb
libgdcm2.2_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2.2_2.2.0-1_amd64.deb
libvtkgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-cil_2.2.0-1_amd64.deb
libvtkgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-java_2.2.0-1_amd64.deb
libvtkgdcm-tools_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-tools_2.2.0-1_amd64.deb
libvtkgdcm2-dev_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm2-dev_2.2.0-1_amd64.deb
libvtkgdcm2.2_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm2.2_2.2.0-1_amd64.deb
python-gdcm_2.2.0-1_amd64.deb
  to main/g/gdcm/python-gdcm_2.2.0-1_amd64.deb
python-vtkgdcm_2.2.0-1_amd64.deb
  to main/g/gdcm/python-vtkgdcm_2.2.0-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now 

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 21:02:29 +
with message-id 
and subject line Bug#655783: fixed in gdcm 2.2.0-1
has caused the Debian Bug report #655783,
regarding ginkgocadx: FTBFS: libITKIO.so.3.20: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
to be marked as done.

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

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


-- 
655783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ginkgocadx
Version: 2.6.0.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /usr/bin/c++-fPIC -pthread -O3 -DNDEBUG
> CMakeFiles/ginkgocadx.dir/main.cpp.o  -o ginkgocadx -rdynamic 
> -L/usr/lib/InsightToolkit ../cadxcore/libCADxCore.so.2.6.0. -ldcmdata 
> -ldcmimage -ldcmimgle -ldcmjpeg -ldcmnet -ldcmpstat -ldcmqrdb -ldcmsr 
> -ldcmtls -lijg12 -lijg16 -lijg8 -lofstd -loflog -ldcmdsig -ldcmtls -lwrap 
> -Wl,-rpath,/usr/lib/InsightToolkit:/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/src/cadxcore:
>  
> Scanning dependencies of target lightvisualizator
> make[3]: Leaving directory 
> `/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu'
> make -f src/lightvisualizator/CMakeFiles/lightvisualizator.dir/build.make 
> src/lightvisualizator/CMakeFiles/lightvisualizator.dir/build
> make[3]: Entering directory 
> `/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 85
> [ 85%] /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 
> /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 
> /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 86
> /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 
> /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 
> [ 85%] /usr/bin/cmake -E cmake_progress_report 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/CMakeFiles 87
> [ 85%] Building CXX object 
> src/lightvisualizator/CMakeFiles/lightvisualizator.dir/lightvisualizatorextension.cpp.o
> [ 86%] [ 86%] cd 
> /build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/obj-x86_64-linux-gnu/src/lightvisualizator
>  && /usr/bin/c++   -Dlightvisualizator_EXPORTS -DUSING_EXTENSIONS 
> -DGINKGO_ARCH_x86_64 -DINTERNET_DIST -DLINUX -D_FILE_OFFSET_BITS=64 
> -D_LARGE_FILES -D__WXGTK__ -fPIC -pthread  -Wno-deprecated  
> -ftemplate-depth-50 -Wall -Wno-deprecated -O3 -DNDEBUG -fPIC 
> -I/usr/include/InsightToolkit/Review/Statistics 
> -I/usr/include/InsightToolkit/Review 
> -I/usr/include/InsightToolkit/Utilities/vxl/core 
> -I/usr/include/InsightToolkit/Utilities/vxl/vcl 
> -I/usr/include/InsightToolkit/Utilities/vxl/v3p/netlib 
> -I/usr/include/InsightToolkit/Utilities 
> -I/usr/include/InsightToolkit/Utilities/itkExtHdrs 
> -I/usr/include/InsightToolkit/Utilities/nifti/znzlib 
> -I/usr/include/InsightToolkit/Utilities/nifti/niftilib 
> -I/usr/include/InsightToolkit/Utilities/expat 
> -I/usr/include/InsightToolkit/Utilities/DICOMParser 
> -I/usr/include/InsightToolkit/Utilities/NrrdIO 
> -I/usr/include/InsightToolkit/Utilities/MetaIO 
> -I/usr/include/InsightToolkit/SpatialObject 
> -I/usr/include/InsightToolkit/Numerics/NeuralNetworks 
> -I/usr/include/InsightToolkit/Numerics/FEM -I/usr/include/InsightToolkit/IO 
> -I/usr/include/InsightToolkit/Numerics -I/usr/include/InsightToolkit/Common 
> -I/usr/include/InsightToolkit/BasicFilters 
> -I/usr/include/InsightToolkit/Algorithms -I/usr/include/InsightToolkit 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/vtk 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/itk 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/wx 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/wx/VTK 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/VTKInria3D 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/VTKInria3D/wxVTK 
> -I/build/ginkgocadx-NUkbV6/ginkgocadx-2.6.0.0/src/cadxcore/VTKInria3D/vtkRenderingAddons
>  -

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 21:02:29 +
with message-id 
and subject line Bug#655783: fixed in gdcm 2.2.0-1
has caused the Debian Bug report #655783,
regarding gofigure2: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
to be marked as done.

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

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


-- 
655783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gofigure2
Version: 0.9.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /usr/bin/c++-fopenmp  -Wno-deprecated  -ftemplate-depth-50 -Wall 
> -Wno-deprecated -O2 -g  CMakeFiles/gofigure.dir/gofigure.cxx.o 
> CMakeFiles/gofigure.dir/QGoTabManager.cxx.o 
> CMakeFiles/gofigure.dir/QGoMainWindow.cxx.o 
> CMakeFiles/gofigure.dir/QGoPluginManager.cxx.o 
> CMakeFiles/gofigure.dir/__/Interfaces/QGoPluginHelper.cxx.o 
> CMakeFiles/gofigure.dir/__/Interfaces/QGoPlugin.cxx.o 
> CMakeFiles/gofigure.dir/__/Interfaces/QGoImageFilterPluginBase.cxx.o 
> CMakeFiles/gofigure.dir/moc_QGoTabManager.cxx.o 
> CMakeFiles/gofigure.dir/moc_QGoMainWindow.cxx.o 
> CMakeFiles/gofigure.dir/moc_QGoPluginManager.cxx.o 
> CMakeFiles/gofigure.dir/__/Interfaces/moc_QGoPlugin.cxx.o 
> CMakeFiles/gofigure.dir/__/Interfaces/moc_QGoImageFilterPluginBase.cxx.o 
> CMakeFiles/gofigure.dir/qrc_axes.cxx.o  -o ../bin/gofigure -rdynamic 
> -L/usr/lib/InsightToolkit 
> -L/tmp/buildd/gdcm-2.0.19/obj-x86_64-linux-gnu/bin/. 
> -L/build/gofigure2-NEbRGe/gofigure2-0.9.0/obj-x86_64-linux-gnu/bin 
> -L/build/gofigure2-NEbRGe/gofigure2-0.9.0/obj-x86_64-linux-gnu/lib 
> ../lib/libQGoGui.so.0.9 ../lib/libQGoIO.so.0.9 ../lib/libitkQt.so.0.9 
> -lboost_program_options-mt ../lib/libvtkLSMReader.so.0.9 -lITKAlgorithms 
> -lITKNumerics -lfftw3 -lfftw3_threads -lfftw3f -lfftw3f_threads 
> -lITKStatistics -litkNetlibSlatec -lITKFEM -lITKBasicFilters -lITKIO 
> -lITKNrrdIO /usr/lib/libgdcmMSFF.so.2.0.19 /usr/lib/libgdcmDICT.so.2.0.19 
> /usr/lib/libgdcmIOD.so.2.0.19 /usr/lib/libgdcmDSED.so.2.0.19 
> /usr/lib/libgdcmCommon.so.2.0.19 -litkjpeg8 -lpng -ltiff -lITKSpatialObject 
> -lITKMetaIO -lITKDICOMParser -lITKEXPAT -lITKniftiio -lITKznz -lz 
> -lITKTransformIOReview -lITKQuadEdgeMesh -lITKCommon -litkvnl_inst 
> -litkvnl_algo -litkv3p_netlib -litkvnl -litkvcl -litkv3p_lsqr -lm -litksys 
> -lpthread /usr/lib/libQVTK.so.5.8.0 /usr/lib/libvtkViews.so.5.8.0 
> /usr/lib/libvtkInfovis.so.5.8.0 /usr/lib/libvtkQtChart.so.5.8.0 -lQtSql 
> -lQtNetwork ../lib/libvtkRenderingAddOn2.so.0.9 
> /usr/lib/libvtkWidgets.so.5.8.0 /usr/lib/libvtkVolumeRendering.so.5.8.0 
> ../lib/libPoissonReconstruction.so.0.9 /usr/lib/libvtkHybrid.so.5.8.0 
> /usr/lib/libvtkParallel.so.5.8.0 /usr/lib/libvtkRendering.so.5.8.0 
> /usr/lib/libvtkIO.so.5.8.0 /usr/lib/libvtkImaging.so.5.8.0 
> /usr/lib/libvtkGraphics.so.5.8.0 /usr/lib/libvtkFiltering.so.5.8.0 
> /usr/lib/libvtkCommon.so.5.8.0 -lm /usr/lib/libvtksys.so.5.8.0 -ldl 
> ../lib/libctk.so.0.9 -lQtGui -lQtCore 
> -Wl,-rpath,/usr/lib/InsightToolkit:/tmp/buildd/gdcm-2.0.19/obj-x86_64-linux-gnu/bin/.:/build/gofigure2-NEbRGe/gofigure2-0.9.0/obj-x86_64-linux-gnu/bin:/build/gofigure2-NEbRGe/gofigure2-0.9.0/obj-x86_64-linux-gnu/lib:
>  
> /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libITKIO.so: undefined 
> reference to `gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
> collect2: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/gofigure2_0.9.0-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 2.2.0-1

We believe that the bug you reported is fixed in the latest version of
gdcm, which is due to be installed in the Debian FTP archive:

gdcm_2.2.0-1.debian.tar.gz
  to main/g/gdcm/gdcm_2.2.0-1.debian.tar.gz
gdcm_2.2.0-1.dsc
  to main/g/gdcm/gdcm_2.2.0-1.dsc
gdcm_2.2.0.orig.tar.gz
  to main/g/gdcm/gdcm_2.2.0.orig.tar.gz
libgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-cil_2.2.0-1_amd64.deb
libgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-java_2

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 21:02:29 +
with message-id 
and subject line Bug#655783: fixed in gdcm 2.2.0-1
has caused the Debian Bug report #655783,
regarding plastimatch: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
to be marked as done.

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

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


-- 
655783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plastimatch
Version: 1.5.5+dfsg0-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /usr/bin/c++ -ftemplate-depth-50 -Wall -Wno-deprecated -O3 -DNDEBUG -fPIC 
> -fopenmp -ldl CMakeFiles/merge_vfs.dir/merge_vector_fields.cxx.o  -o 
> ../../merge_vfs -rdynamic 
> -L/build/plastimatch-1qJADo/plastimatch-1.5.5+dfsg0/obj-x86_64-linux-gnu/libs/liblbfgs-1.9
>  
> -L/build/plastimatch-1qJADo/plastimatch-1.5.5+dfsg0/obj-x86_64-linux-gnu/libs/bstrlib-05122010
>  
> -L/build/plastimatch-1qJADo/plastimatch-1.5.5+dfsg0/obj-x86_64-linux-gnu/libs/nocedal
>  -L/usr/lib/InsightToolkit 
> -L/tmp/buildd/gdcm-2.0.19/obj-x86_64-linux-gnu/bin/. -L/usr/include 
> ../../libplastimatch1.a -lITKAlgorithms -lITKStatistics -lITKFEM 
> ../../libgpuit.a ../../libs/liblbfgs-1.9/liblbfgs.a 
> ../../libs/nocedal/libnocedal.a ../../libplmsys.a -lfftw3f -lfftw3 -lgfortran 
> -lm -lITKNumerics -lfftw3 -lfftw3_threads -lfftw3f -lfftw3f_threads 
> -litkNetlibSlatec -lITKBasicFilters -lITKIO -lITKNrrdIO 
> /usr/lib/libgdcmMSFF.so.2.0.19 /usr/lib/libgdcmDICT.so.2.0.19 
> /usr/lib/libgdcmIOD.so.2.0.19 /usr/lib/libgdcmDSED.so.2.0.19 
> /usr/lib/libgdcmCommon.so.2.0.19 -litkjpeg8 -lpng -ltiff -lITKSpatialObject 
> -lITKMetaIO -lITKDICOMParser -lITKEXPAT -lITKniftiio -lITKznz -lz 
> -lITKTransformIOReview -lITKCommon -litkvnl_inst -litkvnl_algo 
> -litkv3p_netlib -litkvnl -litkvcl -litkv3p_lsqr -lm -litksys -lpthread -ldl 
> ../../libs/bstrlib-05122010/libbstrlib.a -lm -lgfortran -lquadmath 
> /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libITKIO.so: undefined 
> reference to `gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
> collect2: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/plastimatch_1.5.5+dfsg0-2_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 2.2.0-1

We believe that the bug you reported is fixed in the latest version of
gdcm, which is due to be installed in the Debian FTP archive:

gdcm_2.2.0-1.debian.tar.gz
  to main/g/gdcm/gdcm_2.2.0-1.debian.tar.gz
gdcm_2.2.0-1.dsc
  to main/g/gdcm/gdcm_2.2.0-1.dsc
gdcm_2.2.0.orig.tar.gz
  to main/g/gdcm/gdcm_2.2.0.orig.tar.gz
libgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-cil_2.2.0-1_amd64.deb
libgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-java_2.2.0-1_amd64.deb
libgdcm-tools_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-tools_2.2.0-1_amd64.deb
libgdcm2-dev_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2-dev_2.2.0-1_amd64.deb
libgdcm2.2-dbg_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2.2-dbg_2.2.0-1_amd64.deb
libgdcm2.2_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2.2_2.2.0-1_amd64.deb
libvtkgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-cil_2.2.0-1_amd64.deb
libvtkgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-java_2.2.0-1_amd64.deb
libvtkgdcm-tools_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-tools_2.2.0-1_amd64.deb
libvtkgdcm2-dev_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm2-dev_2.2.0-1_amd64.deb
libvtkgdcm2.2_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm2.2_2.2.0-1_amd64.deb
python-gdcm_2.2.0-1_amd64.deb
  to main/g/gdcm/python-gdcm_2.2.0-1_amd64.deb
python-vtkgdcm_2.2.0-1_amd64.deb
  to main/g/gdcm/python-vtkgdcm_2.2.0-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Mala

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 21:02:29 +
with message-id 
and subject line Bug#655783: fixed in gdcm 2.2.0-1
has caused the Debian Bug report #655783,
regarding ants: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
to be marked as done.

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

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


-- 
655783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ants
Version: 1.9.2+svn680.dfsg-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /usr/bin/c++   -Wall -g -O2   -ftemplate-depth-50 -Wall -Wno-deprecated  
> -Wno-deprecated  -ftemplate-depth-50 -Wall -Wno-deprecated   -Wl,--as-needed  
>   CMakeFiles/ANTS.dir/ANTS.o 
> CMakeFiles/ANTS.dir/build/ants-zRCJoE/ants-1.9.2+svn680.dfsg/Utilities/antsCommandLineParser.o
>  
> CMakeFiles/ANTS.dir/build/ants-zRCJoE/ants-1.9.2+svn680.dfsg/Utilities/antsCommandLineOption.o
>   -o /build/ants-zRCJoE/ants-1.9.2+svn680.dfsg/build/bin/ANTS -rdynamic 
> -L/usr/lib/InsightToolkit 
> -L/tmp/buildd/gdcm-2.0.19/obj-x86_64-linux-gnu/bin/. -lITKCommon 
> -lITKBasicFilters -lITKIO -lITKNumerics -lITKStatistics -lITKFEM 
> -litkNetlibSlatec -lITKBasicFilters -lITKIO -lITKNrrdIO 
> /usr/lib/libgdcmMSFF.so.2.0.19 /usr/lib/libgdcmDICT.so.2.0.19 
> /usr/lib/libgdcmIOD.so.2.0.19 /usr/lib/libgdcmDSED.so.2.0.19 
> /usr/lib/libgdcmCommon.so.2.0.19 -litkjpeg8 -lpng -ltiff -lITKSpatialObject 
> -lITKMetaIO -lITKDICOMParser -lITKEXPAT -lITKniftiio -lITKznz -lz 
> -lITKTransformIOReview -lITKCommon -litkvnl_inst -litkvnl_algo 
> -litkv3p_netlib -litkvnl -litkvcl -litkv3p_lsqr -lm -litksys -lpthread -ldl 
> -lm 
> /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libITKIO.so: undefined 
> reference to `gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
> collect2: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/ants_1.9.2+svn680.dfsg-2_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 2.2.0-1

We believe that the bug you reported is fixed in the latest version of
gdcm, which is due to be installed in the Debian FTP archive:

gdcm_2.2.0-1.debian.tar.gz
  to main/g/gdcm/gdcm_2.2.0-1.debian.tar.gz
gdcm_2.2.0-1.dsc
  to main/g/gdcm/gdcm_2.2.0-1.dsc
gdcm_2.2.0.orig.tar.gz
  to main/g/gdcm/gdcm_2.2.0.orig.tar.gz
libgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-cil_2.2.0-1_amd64.deb
libgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-java_2.2.0-1_amd64.deb
libgdcm-tools_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm-tools_2.2.0-1_amd64.deb
libgdcm2-dev_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2-dev_2.2.0-1_amd64.deb
libgdcm2.2-dbg_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2.2-dbg_2.2.0-1_amd64.deb
libgdcm2.2_2.2.0-1_amd64.deb
  to main/g/gdcm/libgdcm2.2_2.2.0-1_amd64.deb
libvtkgdcm-cil_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-cil_2.2.0-1_amd64.deb
libvtkgdcm-java_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-java_2.2.0-1_amd64.deb
libvtkgdcm-tools_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm-tools_2.2.0-1_amd64.deb
libvtkgdcm2-dev_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm2-dev_2.2.0-1_amd64.deb
libvtkgdcm2.2_2.2.0-1_amd64.deb
  to main/g/gdcm/libvtkgdcm2.2_2.2.0-1_amd64.deb
python-gdcm_2.2.0-1_amd64.deb
  to main/g/gdcm/python-gdcm_2.2.0-1_amd64.deb
python-vtkgdcm_2.2.0-1_amd64.deb
  to main/g/gdcm/python-vtkgdcm_2.2.0-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated gdcm 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: 

Processed: Re: RM: libwww5.808-perl -- RC-buggy, NPOASR

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 636923 ensembl 63-1
Bug #636923 [src:libwww5.808-perl] Handle the libwww5.808-perl issue
Bug reassigned from package 'src:libwww5.808-perl' to 'ensembl'.
Bug #636923 [ensembl] Handle the libwww5.808-perl issue
Bug Marked as found in versions ensembl/63-1.
> severity 636923 serious
Bug #636923 [ensembl] Handle the libwww5.808-perl issue
Severity set to 'serious' from 'normal'

> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
636923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657163: gearmand: FTBFS: gearman_worker_set_server_option() failed

[Aaron M. Ucko]

Stig Sandbeck Mathisen  writes:

> I was just wondering: Does your build environment have a "127.0.0.1"
> address? Some OS installs, especially ones used for building, may not
> have a loopback interface, and that would help me narrow this one down a
> bit.

That's a great question, which I'm alas not in a position to answer; I
don't run any autobuilders myself, just keep an eye out for packages
that show up on amd64 but not i386 or vice versa.  That said, I do
recall hearing that some of them have been historically configured to
present build environments with no network interfaces at all, so that
may well be the explanation here.

Thanks for looking into it!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



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

Bug#657055: haskell-hsql-postgresql-doc: fails to upgrade from squeeze - trying to overwrite ...

[Holger Levsen]

Hi Joachim,

On Dienstag, 24. Januar 2012, Joachim Breitner wrote:
> Am Montag, den 23.01.2012, 20:46 +0100 schrieb Holger Levsen:
> > Similar bugs affect _a lot_ of haskell-*-doc packages, please have a look
> > at the logs linked from:
> > 
> > http://piuparts.debian.org/squeeze2wheezy/overwrite_other_packages_files_
> > error.html
[list omitted]
> 
> hmm, is that a complete list, or just those that have been checked so
> far?

thats the complete list for sid, but keep in mind that packages depending on 
those broken ones are not tested :)

just visit that url again, it's updated daily.

> @Holger: I don’t think you need to file more bugs about this, as we
> hopefully can fix this once for all packages.

ok.


cheers,
Holger



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

Processed: block 631019 with 657203

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 631019 with 657203
Bug #631019 [release.debian.org] transition: hdf5 1.8.x
Was blocked by: 651453 652310 652313 652308 643488 650598 652315 651452 652309 
652314 652312 652025 646142 652307 641790 624671 657198 657199 652311
Added blocking bug(s) of 631019: 657203
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
631019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657203: mpb: FTBFS against hdf5 1.8.8

[Julien Cristau]

Source: mpb
Version: 1.4.2-17
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

it seems like mpb doesn't build against hdf5 1.8.8:
https://buildd.debian.org/status/fetch.php?pkg=mpb&arch=s390x&ver=1.4.2-17&stamp=1326908037

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#647231: libvisual-plugins: FTBFS(!linux): error: possibly undefined macro: AM_PATH_ALSA

[peter green]

Note: I have no particular relationship to this package, i'm just trying to
reduce the number of uninstallable packages in armhf testing.


configure.ac:210: warning: macro `AM_PATH_ALSA' not found in library
configure.ac:210: error: possibly undefined macro: AM_PATH_ALSA
 If this token and others are legitimate, please use m4_pattern_allow.
 See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1


AM_PATH_ALSA is defined in /usr/share/aclocal/alsa.m4 which is
in package libasound2-dev which only exists on linux. 


Previously this was not an issue because configure was not rebuilt as part of
the build, however in his QA upload Steve Langasek changed the package build to
rebuild configure and hence made it FTBFS on non-linux architectures.

Having throught about this I see several possible soloutions

1: go back to including configure in the packaging rather than building it at
  package build time.
2: move alsa.m4 to a package that exists on all architectures
3: include a copy of alsa.m4 in the libvisual-plugins source
4: include a dummy definition of AM_PATH_ALSA that does nothing in 
  the libvisual-plugins source and only use it on architectures other

  than linux.

Option 1 is probablly the simplest fix but shipping generated code rather than 
doing the generation at build time seems like a step backwards to me.


Option 2 seems good in theory (after all autoconf is mean to generate configure
scripts that run on platforms other than the ones they were generated on so 
having
AM_PATH_ALSA available on architecture without alsa isn't too unreasonable IMO) 
but the question would be where to move it to and how much disruption would said

move cause...

Option 3 is code duplication that is generally frowned upon

Option 4 seems like the best option if the asla guys don't want to provide 
alsa.m4 on non-linux architectures.


I am CCing Steve (as the last person to touch the package and the one who
introduced the FTBFS) and the ALSA maintainers list to get their opinions on 
this.








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

Processed: block 631019 with 657199 657198

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 631019 with 657199 657198
Bug #631019 [release.debian.org] transition: hdf5 1.8.x
Was blocked by: 624671 641790 643488 646142 650598 651452 651453 652025 652307 
652308 652309 652310 652311 652312 652313 652314 652315
Added blocking bug(s) of 631019: 657198 and 657199
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
631019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657199: libgpiv: FTBFS against hdf5 1.8.8

[Julien Cristau]

Source: libgpiv
Version: 0.6.1-3
Severity: serious
Tags: wheezy sid
Justification: fails to build from source (but built successfully in the past)

It looks like API changes in hdf5 break libgpiv:
https://buildd.debian.org/status/fetch.php?pkg=libgpiv&arch=s390x&ver=0.6.1-3&stamp=1326908982

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#657198: hdf-eos5: FTBFS against hdf5 1.8.8

[Julien Cristau]

Source: hdf-eos5
Version: 5.1.12.dfsg.2-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

It looks like hdf-eos5 is broken by API changes in the new hdf5:
https://buildd.debian.org/status/fetch.php?pkg=hdf-eos5&arch=s390x&ver=5.1.12.dfsg.2-3&stamp=1326908113

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#657055: haskell-hsql-postgresql-doc: fails to upgrade from squeeze - trying to overwrite ...

[Joachim Breitner]

Hi,

Am Montag, den 23.01.2012, 20:46 +0100 schrieb Holger Levsen:
> Similar bugs affect _a lot_ of haskell-*-doc packages, please have a look at 
> the logs linked from:
> 
> http://piuparts.debian.org/squeeze2wheezy/overwrite_other_packages_files_error.html
> 
> fail/haskell-haskelldb-doc_1:6.log (BTS)
> fail/haskell-hsql-odbc-doc_1:6.log (BTS)
> fail/haskell-hsql-postgresql-doc_1:6.log (BTS)
> fail/haskell-hsql-sqlite3-doc_1:6.log (BTS)
> fail/libghc6-datetime-doc_1:6.log (BTS)
> fail/libghc6-feed-doc_1:6.log (BTS)
> fail/libghc6-haskelldb-doc_1:6.log (BTS)
> fail/libghc6-haskore-doc_1:6.log (BTS)
> fail/libghc6-hsql-odbc-doc_1:6.log (BTS)
> fail/libghc6-hsql-postgresql-doc_1:6.log (BTS)
> fail/libghc6-hsql-sqlite3-doc_1:6.log (BTS)
> fail/libghc6-recaptcha-doc_1:6.log (BTS)
> fail/libghc6-split-doc_1:6.log (BTS)

hmm, is that a complete list, or just those that have been checked so
far?

Until now I was under the impression that only those packages were
affected by this that had a haskell-*-doc package at some time
previously, which is a minority. But haskell-split never had that, so
this indicates that all ~400 Haskell source packages are affected. In
that case, we should think some more before trying to fix each
individual package. Ideally, we’d only need to improve the dummy
packages (as shipped by haskell-dummy) and _not_ touch all 400 source
packages.

I’m currently at POPL, so I won’t look into this anytime soon, if
someone else wants to pick this up, that’d be great.

@Holger: I don’t think you need to file more bugs about this, as we
hopefully can fix this once for all packages.

Greetings,
Joachim

-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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

Processed: tagging 656845

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 656845 + pending
Bug #656845 [gnucash-common] gnucash-common: fails to upgrade from squeeze - 
trying to overwrite ...
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
656845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657124: rampart FTBFS "configure: error: could not find axis2inc. stop"

[peter green]

Aaron M. Ucko wrote:

peter green  writes:

  

Unfortunately my searches for axis2inc failed to find anything
relavent in debian so I can't make any suggestions on how to fix this.



There is a libaxis2c-dev package that ought to contain that script;
  
hmm, seems installing libaxis2c-dev does indeed make the package build 
even though I can't find any evidence of a binary called axis2inc..

please try adding it to Build-Depends and checking with pbuilder or the
like that nothing else is missing.
  
I just tested in pbuilder and libaxis2c-dev seems to be the only missing 
build-dependency.

Thanks!

  





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

Processed: tagging as pending bugs that are closed by packages in NEW

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Tue Jan 24 19:03:23 UTC 2012
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: volview
> tags 640511 + pending
Bug #640511 [wnpp] ITP: volview -- Advanced volume visualization tool
Added tag(s) pending.
> # Source package in NEW: gdcm
> tags 655783 + pending
Bug #655783 [gdcm] ants: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
Bug #655784 [gdcm] plastimatch: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
Bug #655785 [gdcm] gofigure2: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
Bug #655786 [gdcm] ginkgocadx: FTBFS: libITKIO.so.3.20: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
Bug #655787 [gdcm] itksnap: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
Bug #655788 [gdcm] igstk: FTBFS: libITKIO.so: undefined reference to 
`gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const&)'
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> # Source package in NEW: gdcm
> tags 656969 + pending
Bug #656969 [gdcm] gdcm: 2.2.0 is out !
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
656969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656969
640511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640511
655783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657193: CVE-2011-5027

[Moritz Muehlenhoff]

Package: zabbix
Severity: grave
Tags: security

Please see https://support.zabbix.com/browse/ZBX-4015

This is CVE-2011-5027

Cheers,
Moritz



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

Bug#657150: _cbsonmodule problems on ARM processors

[Federico Ceratto]

On Tue, Jan 24, 2012 at 1:32 PM, Martin Insulander <
insulander.mar...@gmail.com> wrote:

> Package: python-pymongo
> Version: 2.1-1
> Severity: critical
>
> When doing drop or find on a collection Python returns invalid BSON.
> The collection has to be filled with a couple of entries.
>
> I'm using mongodb from a Qnap server (version 1.8)
> https://github.com/skrabban/**mongo-nonx86
> .
>
> See the following bug report for more info:
> https://jira.mongodb.org/**browse/PYTHON-313
>
> Removing the c extensions seems to solve the problem.
>

Hello Martin, thanks for the feedback.

I'm trying to reproduce the bug on a friend's Sheevaplug, in the meantime
removing the ARM binary package from Debian/Ubuntu seems to be the best
solution.

I'm federico2 on freenode if you like to test it together.

Thanks!
-- 
Federico

Bug#657163: gearmand: FTBFS: gearman_worker_set_server_option() failed

[Stig Sandbeck Mathisen]

"Aaron M. Ucko"  writes:

>   STARTING SERVER(pid:30245): /.../gearmand-0.27/libtool
> --mode=execute /.../gearmand-0.27/./gearmand/gearmand
> --pid-file=var/run/gearmand.pidwRNuyg --daemon --port=32154
> --listen=127.0.0.1

I was just wondering: Does your build environment have a "127.0.0.1"
address? Some OS installs, especially ones used for building, may not
have a loopback interface, and that would help me narrow this one down a
bit.

-- 
Stig Sandbeck Mathisen



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

Processed: Re: ruby-image-science: FTBFS: tests failed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 652802 + unreproducible
Bug #652802 [src:ruby-image-science] ruby-image-science: FTBFS: tests failed
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
652802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#652802: ruby-image-science: FTBFS: tests failed

[Gunnar Wolf]

tags 652802 + unreproducible
thanks

I have rebuilt the package under AMD64, using cowbuilder, and could
not reproduce the failure. Your report mentions some permission
problems regarding /var/lib/sbuild - Can you verify whether it was a
problem in your side?



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

Processed: python-osd: diff for NMU version 0.2.14-5.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 650788 + patch
Bug #650788 [src:python-osd] python-osd: binary-indep doesn't build python-osd
Added tag(s) patch.
> tags 650788 + pending
Bug #650788 [src:python-osd] python-osd: binary-indep doesn't build python-osd
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
650788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#656961: xul-ext-syncplaces: incompatible with iceweasel 8.0...

[Marcos Marado]

Hi there,

Can you please check if upstream's SyncPlaces v4.3.0 works with Iceweasel 8.0?



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

Bug#650788: python-osd: diff for NMU version 0.2.14-5.1

[gregor herrmann]

tags 650788 + patch
tags 650788 + pending
thanks

Dear maintainer,

I've prepared an NMU for python-osd (versioned as 0.2.14-5.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Josh With: Greenville Sheik
diff -u python-osd-0.2.14/debian/rules python-osd-0.2.14/debian/rules
--- python-osd-0.2.14/debian/rules
+++ python-osd-0.2.14/debian/rules
@@ -23,24 +23,34 @@
 	python setup.py install --root=$(p)
 
 binary-indep: build install
+	dh_testdir -i
+	dh_testroot -i
+	dh_installchangelogs -i
+	dh_installdocs -i
+	dh_compress -i
+	dh_fixperms -i
+	dh_installdeb -i
+	dh_gencontrol -i
+	dh_md5sums -i
+	dh_builddeb -i
 
 binary-arch: build install
-	dh_testdir
-	dh_testroot
-	dh_installdocs
-	dh_installexamples
-	dh_installchangelogs ChangeLog
-	dh_link
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_makeshlibs
-	dh_pysupport
-	dh_installdeb
-	dh_shlibdeps 
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
+	dh_testdir -a
+	dh_testroot -a
+	dh_installdocs -a
+	dh_installexamples -a
+	dh_installchangelogs ChangeLog -a
+	dh_link -a
+	dh_strip -a
+	dh_compress -a
+	dh_fixperms -a
+	dh_makeshlibs -a
+	dh_pysupport -a
+	dh_installdeb -a
+	dh_shlibdeps -a
+	dh_gencontrol -a
+	dh_md5sums -a
+	dh_builddeb -a
 
 binary: binary-indep binary-arch
 .PHONY: build clean binary-indep binary-arch binary install
diff -u python-osd-0.2.14/debian/changelog python-osd-0.2.14/debian/changelog
--- python-osd-0.2.14/debian/changelog
+++ python-osd-0.2.14/debian/changelog
@@ -1,3 +1,12 @@
+python-osd (0.2.14-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix "binary-indep doesn't build python-osd":
+update binary-indep and binary-arch targets in debian/rules.
+(Closes: #650788)
+
+ -- gregor herrmann   Tue, 24 Jan 2012 19:02:00 +0100
+
 python-osd (0.2.14-5) unstable; urgency=low
 
   * Rename of the binary package from "python-osd" to "python-pyosd" 


signature.asc
Description: Digital signature

Bug#655817: marked as done (ruby-activesupport-2.3: FTBFS: unsatisfiable build-dependencies: ruby-memcache-client (>= 1.7.4~), ruby-tzinfo (>= 0.3.12~))

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 18:02:22 +
with message-id 
and subject line Bug#655817: fixed in ruby-activesupport-2.3 2.3.14-3
has caused the Debian Bug report #655817,
regarding ruby-activesupport-2.3: FTBFS: unsatisfiable build-dependencies: 
ruby-memcache-client (>= 1.7.4~), ruby-tzinfo (>= 0.3.12~)
to be marked as done.

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

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


-- 
655817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-activesupport-2.3
Version: 2.3.14-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120112 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ┌──┐
> │ Install ruby-activesupport-2.3 build dependencies (apt-based resolver)  
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-ruby-activesupport-2.3-dummy : Depends: 
> ruby-memcache-client (>= 1.7.4~) but it is not installable
>  Depends: ruby-tzinfo (>= 
> 0.3.12~) but it is not installable
> E: Broken packages

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/01/12/ruby-activesupport-2.3_2.3.14-2_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Source: ruby-activesupport-2.3
Source-Version: 2.3.14-3

We believe that the bug you reported is fixed in the latest version of
ruby-activesupport-2.3, which is due to be installed in the Debian FTP archive:

ruby-activesupport-2.3_2.3.14-3.debian.tar.gz
  to main/r/ruby-activesupport-2.3/ruby-activesupport-2.3_2.3.14-3.debian.tar.gz
ruby-activesupport-2.3_2.3.14-3.dsc
  to main/r/ruby-activesupport-2.3/ruby-activesupport-2.3_2.3.14-3.dsc
ruby-activesupport-2.3_2.3.14-3_all.deb
  to main/r/ruby-activesupport-2.3/ruby-activesupport-2.3_2.3.14-3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated ruby-activesupport-2.3 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 22 Jan 2012 11:04:05 +0100
Source: ruby-activesupport-2.3
Binary: ruby-activesupport-2.3
Architecture: source all
Version: 2.3.14-3
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Ondřej Surý 
Description: 
 ruby-activesupport-2.3 - Support and utility classes used by the Rails 2.3 
framework
Closes: 655817
Changes: 
 ruby-activesupport-2.3 (2.3.14-3) unstable; urgency=low
 .
   * Add gbp configuration for PRE
   * Remove alternate dependencies from Build-Depends, they don't work
 with sbuild anyway (Closes: #655817)
Checksums-Sha1: 
 964df8821178e69acb77c15688c08dd0e1bf6a52 1747 
ruby-activesupport-2.3_2.3.14-3.dsc
 13095a793c38b71f236bd8458533e00043a8ad01 143409 
ruby-activesupport-2.3_2.3.14-3.debian.tar.gz
 a1ae3b3ebb3cca43a591577241a90555647ea28d 297450 
ruby-activesupport-2.3_2.3.14-3_all.deb
Checksums-Sha256: 
 a086ac0623207a5e0c594464a88e9e7728329c189f5f002854900e45b022042c 1747 
ruby-activesupport-2.3_2.3.14-3.dsc
 155f4875c666c2b95dbbce6949e301c3553197462731c616db6599a7864cab75 143409 
ruby-activesupport-2.3_2.3.14-3.debian

Bug#642164: Padre::Plugin::Vi is mostly dead upstream

[Dominique Dumont]

Hello

According to http://padre.perlide.org/trac/wiki/Plugins , this plugin does not 
work and is no longer maintained upstream.

So I recommend to remove this package from Debian.

Unless someone objects before Feb, 15th (and takes over upstream development), 
I'll ask for removal.

All the best

Dominique
--
http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/
http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/


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

Processed: bug 642164 is forwarded to http://padre.perlide.org/trac/ticket/1386

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 642164 http://padre.perlide.org/trac/ticket/1386
Bug #642164 [src:libpadre-plugin-vi-perl] libpadre-plugin-vi-perl: FTBFS: tests 
failures
Set Bug forwarded-to-address to 'http://padre.perlide.org/trac/ticket/1386'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
642164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: tagging 657163

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 657163 + confirmed
Bug #657163 [src:gearmand] gearmand: FTBFS: gearman_worker_set_server_option() 
failed
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
657163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: tagging 657165

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 657165 + confirmed
Bug #657165 [src:gearmand] gearmand: FTBFS on 32-bit architectures: symbols 
file mismatch
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
657165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#657165: gearmand: FTBFS on 32-bit architectures: symbols file mismatch

[Stig Sandbeck Mathisen]

"Aaron M. Ucko"  writes:

> Could you please account for such variation?

Already in progress.

Thanks for reporting the bug.

-- 
Stig Sandbeck Mathisen


pgpcyIttMEh6S.pgp
Description: PGP signature

Bug#657163: gearmand: FTBFS: gearman_worker_set_server_option() failed

[Stig Sandbeck Mathisen]

"Aaron M. Ucko"  writes:

> Could you please take a look?

Already in progress.

Thank you for reporting the bug.

-- 
Stig Sandbeck Mathisen


pgp0bhGtWfmiY.pgp
Description: PGP signature

Processed: severity of 657097 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 657097 grave
Bug #657097 [libcairo2] libcairo2: Evolution crash at startup (core dumped)
Severity set to 'grave' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
657097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#656688: usb_modeswitch throws "general protection" errors to syslog

[Joaquim Boura]

> You can uninstall the Debian 
> package and install from source until a fixed "deb" is available.

> http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-1.2.2-1.tar.bz2

This solves the problem for me.

Regards

Joaquim Boura



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

Bug#646474: Unable to reproduce FTBFS

[Vasudev Kamath]

Hello,

I tried to build surf_0.4.1-4.1 on clean chroot using pbuilder and I
could build this package successfully. I'm attaching build log for
reference. Please let me know if this bug still exists as I'm planning
to do a QA upload for this

Best Regards

-- 
Vasudev Kamath
dpkg-checkbuilddeps: Unmet build dependencies: libgtk2.0-dev libwebkit-dev
W: Unmet build-dependency in source
dpkg-buildpackage: source package surf
dpkg-buildpackage: source version 0.4.1-4.1
dpkg-buildpackage: source changed by Bart Martens 
 dpkg-source --before-build surf-0.4.1
dpkg-source: info: using options from surf-0.4.1/debian/source/options: 
--compression=gzip --compression-level=9
dpkg-checkbuilddeps: Unmet build dependencies: libgtk2.0-dev libwebkit-dev
dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: warning: (Use -d flag to override.)
dpkg-buildpackage: warning: This is currently a non-fatal warning with -S, but
dpkg-buildpackage: warning: will probably become fatal in the future.
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
make[1]: Entering directory 
`/home/vasudev/Documents/Debian/qa-upload/surf-0.4.1'
cleaning
make[1]: Leaving directory `/home/vasudev/Documents/Debian/qa-upload/surf-0.4.1'
   dh_clean
 dpkg-source -b surf-0.4.1
dpkg-source: info: using options from surf-0.4.1/debian/source/options: 
--compression=gzip --compression-level=9
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building surf using existing ./surf_0.4.1.orig.tar.gz
dpkg-source: info: building surf in surf_0.4.1-4.1.debian.tar.gz
dpkg-source: info: building surf in surf_0.4.1-4.1.dsc
 dpkg-genchanges -S -sa >../surf_0.4.1-4.1_source.changes
dpkg-genchanges: including full source code in upload
 dpkg-source --after-build surf-0.4.1
dpkg-source: info: using options from surf-0.4.1/debian/source/options: 
--compression=gzip --compression-level=9
dpkg-buildpackage: full upload (original source is included)
I: using fakeroot in build.
I: Current time: Tue Jan 24 22:05:13 IST 2012
I: pbuilder-time-stamp: 1327422913
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: Mounting /var/cache/pbuilder/ccache
I: policy-rc.d already exists
W: hookdir /var/cache/pbuilder/hooks does not exist, skipping
I: Obtaining the cached apt archive contents
I: Setting up ccache
I: Installing the build-deps
W: no hooks of type D found -- ignoring
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 8), libgtk2.0-dev, libwebkit-dev
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in 
`/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11245 files and directories currently installed.)
Unpacking pbuilder-satisfydepends-dummy (from 
.../pbuilder-satisfydepends-dummy.deb) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on debhelper (>= 8); however:
  Package debhelper is not installed.
 pbuilder-satisfydepends-dummy depends on libgtk2.0-dev; however:
  Package libgtk2.0-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libwebkit-dev; however:
  Package libwebkit-dev is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
The following NEW packages will be installed:
  aspell{a} aspell-en{a} bsdmainutils{a} dconf-gsettings-backend{a} 
  dconf-service{a} debhelper{a} dictionaries-common{a} file{a} 
  fontconfig{a} fontconfig-config{a} gettext{a} gettext-base{a} 
  gir1.2-atk-1.0{a} gir1.2-freedesktop{a} gir1.2-gdkpixbuf-2.0{a} 
  gir1.2-glib-2.0{a} gir1.2-gtk-2.0{a} gir1.2-javascriptcoregtk-1.0{a} 
  gir1.2-pango-1.0{a} gir1.2-soup-2.4{a} gir1.2-webkit-1.0{a} 
  glib-networking{a} glib-networking-common{a} glib-networking-services{a} 
  groff-base{a} gsettings-desktop-schemas{a} html2text{a} 
  intltool-debian{a} iso-codes{a} libaspell15{a} libatk1.0-0{a} 
  libatk1.0-data{a} libatk1.0-dev{a} libavahi-client3{a} 
  libavahi-common-data{a} libavahi-common3{a} libcairo-gobject2{a} 
  libcairo-script-interpreter2{a} libcairo2{a} libcairo2-dev{a} 
  libcroco3{a} libcups2{a} libdatrie1{a} libdbus-1-3{a} libdbus-glib-1-2{a} 
  libdconf0{a} libenc

Processed: Trying Merge by reassigning

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 646123 src:surf
Bug #646123 [surf] FTBS: javascriptcoregtk-1.0 missing
Bug reassigned from package 'surf' to 'src:surf'.
Bug No longer marked as found in versions surf/0.4.1-4.1.
> merge 646123 646474
Bug#646123: FTBS: javascriptcoregtk-1.0 missing
Bug#646474: surf: FTBFS: libjavascriptcoregtk-1.0.so.0: could not read symbols: 
Invalid operation
Merged 646123 646474.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
646123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646123
646474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#654849: [Pkg-libvirt-maintainers] Bug#654849: gtk-vnc: FTBFS with GModule-2.0.gir:46.7-46.66: error: unknown child element `function' in `record'

[Daniel Kahn Gillmor]

On 01/23/2012 06:07 PM, Guido Günther wrote:
> I can't seem to reproduct this in a clean amd64 sid chroot. Are you
> still seeing this?

Hm, this is still reproducible for me in an up-to-date sid i386 system
that i've been keeping updated for several months now.

But i made a fresh chroot on the same machine, and did nothing in it but:

 apt-get install build-essential fakeroot
 apt-get build-dep gtk-vnc

and then tried to rebuild gtk-vnc 0.5.0-2, and it built cleanly.

So something is amiss in the regularly-upgraded build environment, but
i'm not sure what it is, or how or why it breaks the build for gtk-vnc.

Since i have a reproducible test case, i'm happy to investigate it
further, but i don't know what i should be looking for.  I've compared
the files are different between the two in /etc/, but see nothing
relevant there.  But there are many more packages installed in the
normal sid system than in the chroot, and i am not sure if any of them
(or the config files they supply) are the cause of the problem.  If
that's the root of the problem, i suspect gtk-vnc is missing a
Build-Conflicts: or something.

Any ideas what i should check or look for?

--dkg



signature.asc
Description: OpenPGP digital signature

Processed (with 1 errors): Merging Duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 646123 serious
Bug #646123 [surf] FTBS: javascriptcoregtk-1.0 missing
Severity set to 'serious' from 'normal'

> merge 646123 646474
Bug#646123: FTBS: javascriptcoregtk-1.0 missing
Bug#646474: surf: FTBFS: libjavascriptcoregtk-1.0.so.0: could not read symbols: 
Invalid operation
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #646123 has `surf';
 #646474 has `src:surf'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
646474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646474
646123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#653953: marked as done (magicmaze searches for Isabella.ttf in wrong place, crashes.)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2012 16:17:36 +
with message-id 
and subject line Bug#653953: fixed in magicmaze 1.4.3.2.dfsg-1.1
has caused the Debian Bug report #653953,
regarding magicmaze searches for Isabella.ttf in wrong place, crashes.
to be marked as done.

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

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


-- 
653953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: magicmaze
Version: 1.4.3.2.dfsg-1
Severity: important

Dear Maintainer,

magicmaze requires the Isabella font to be in the following location:

magicmaze/graphics.rb:102
> fontfile = "/usr/share/fonts/truetype/Isabella.ttf"

However, the Debian package 'ttf-isabella' in testing and unstable now installs 
the font file to /usr/share/fonts/truetype/ttf-isabella/Isabella.ttf (which 
seems to be the more correct location). 
On systems with the newer ttf-isabella package, magicmaze crashes on start.
Therefore, magicmaze should look for the font both in the old and the new 
location. 

Best Regards,

Raphael Wimmer

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

Versions of packages magicmaze depends on:
ii  libsdl-ruby 2.1.1.1-1  
ii  ruby4.8
ii  ruby1.8 [ruby]  1.8.7.352-2
ii  ttf-isabella1.2-2  


--- End Message ---
--- Begin Message ---
Source: magicmaze
Source-Version: 1.4.3.2.dfsg-1.1

We believe that the bug you reported is fixed in the latest version of
magicmaze, which is due to be installed in the Debian FTP archive:

magicmaze_1.4.3.2.dfsg-1.1.diff.gz
  to main/m/magicmaze/magicmaze_1.4.3.2.dfsg-1.1.diff.gz
magicmaze_1.4.3.2.dfsg-1.1.dsc
  to main/m/magicmaze/magicmaze_1.4.3.2.dfsg-1.1.dsc
magicmaze_1.4.3.2.dfsg-1.1_all.deb
  to main/m/magicmaze/magicmaze_1.4.3.2.dfsg-1.1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 653...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated magicmaze package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Jan 2012 16:33:43 +0100
Source: magicmaze
Binary: magicmaze
Architecture: source all
Version: 1.4.3.2.dfsg-1.1
Distribution: unstable
Urgency: low
Maintainer: Joe Nahmias 
Changed-By: gregor herrmann 
Description: 
 magicmaze  - rescue the maiden while avoiding the monsters
Closes: 653953
Changes: 
 magicmaze (1.4.3.2.dfsg-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix "magicmaze searches for Isabella.ttf in wrong place, crashes.":
 - add patch 20_isabella.dpatch: adjust fontfile variable to point to new
   location of Isabella.ttf
 - debian/control: make dependency on ttf-isabella versioned
 Thanks to Raphael Wimmer for the bug report.
 (Closes: #653953)
Checksums-Sha1: 
 38f4c6acecb79d58d3b1b10b2366a05627469bb5 1744 magicmaze_1.4.3.2.dfsg-1.1.dsc
 820556c9ea68f8e8ac73c5f452ea059e06be536f 5428 
magicmaze_1.4.3.2.dfsg-1.1.diff.gz
 836323b5bfafe29318cd5e178438e9bed4e6e602 114104 
magicmaze_1.4.3.2.dfsg-1.1_all.deb
Checksums-Sha256: 
 583f6549e19f893d6cb46f1c587c74f17630c95ff3a7756277ea61887f9ddfb4 1744 
magicmaze_1.4.3.2.dfsg-1.1.dsc
 8967958f0034188a4eae4141051c62fedc2092a20238c4e1747f0af5ffbd152d 5428 
magicmaze_1.4.3.2.dfsg-1.1.diff.gz
 b209b4abfa254fdb4bb2e13eb73ba961653d3ed11da9b9b26fd227538fedbef6 114104 
magicmaze_1.4.3.2.dfsg-1.1_all.deb
Files: 
 1b90f04ddd776218ba270aa91ea01854 1744 games extra 
magicmaze_1.4.3.2.dfsg-1.1.dsc
 a93ffb8f460b7f00457db931ab25b4dc 5428 games extra 
magicmaze_1.4.3.2.dfsg-1.1.diff.gz
 e92ed2b7e65bb63717dbfda608b89600 114104 games extra 
magicmaze_1.4.3.2.dfsg-1.1_all.deb

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

iQIcBAEBCAAGBQJPHC3rAAoJELs6aAGGSaoGV1QP/2pf28NoPYivCilH/hI3LOj0
UJfN5s+ElbaZGZtykqpjzsPfRt1YrDfLGY83ZhL7etDJf9Y8wwLvbtgFFlbgchp3
98IxN6QQNSS77pf//Xv54BRFsCYDl3+eB9dJx2SPP2lhYTY8pdGWcCqhNjQK/oH8
RtLTO8X4mOpx49Do5Hsq46t8Fur8WGp0mt3xicUi9bmcXVMKeRsT6sOxZYd+6DAq
bSc4wd0el2qocFKNK5LItUTdVwmrCA4O3OYhVTiW3FghwxExcLD8GYtoNmQi5Nwe
JSFhHmAamd9hIwnP1C+xcGafFSpEYYAy9Xek/1iA+CzUO6Mh2E9nCiEHVmRLXMV

Bug#657124: rampart FTBFS "configure: error: could not find axis2inc. stop"

[Aaron M. Ucko]

peter green  writes:

> Unfortunately my searches for axis2inc failed to find anything
> relavent in debian so I can't make any suggestions on how to fix this.

There is a libaxis2c-dev package that ought to contain that script;
please try adding it to Build-Depends and checking with pbuilder or the
like that nothing else is missing.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



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

Bug#655430: (no subject)

[John Church]

I think this problem occurs when there is an issue reading in the gtk-execute 
image from the icon theme. For example when icon doesn't exist in the theme, an 
unhandled exception is thrown.

I'm not in a position to do an NMU as I don't know enough about debian 
packaging yet. But in case it's of any help to the package maintainer I've 
attached a dpatch file I created which seems to solve the problem.

Thanks,
John Church


30Fix_gtkiconload.dpatch
Description: Binary data

Bug#657165: gearmand: FTBFS on 32-bit architectures: symbols file mismatch

[Aaron M. Ucko]

Source: gearmand
Version: 0.27-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

32-bit gearmand builds that don't encounter the test suite error I
just reported as #657163 still fail because some symbol names vary
with word size; you can find a list of discrepancies at

https://buildd.debian.org/status/fetch.php?pkg=gearmand&arch=i386&ver=0.27-1&stamp=1327353886

Could you please account for such variation?

Thanks!



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