Bug#759956: possible graphicsmagick regression?

[GCS]

Hi Bob,

I got a report that drawtiming can't build[1] with newer
GraphicsMagick versions. The exact error is:
caught Magick++ exception: Magick: Non-conforming drawing primitive
definition (text) reported by magick/render.c:3022 (DrawImage)

If the following change is made to memory.txt in drawimage then it works.
-- cut --
-CS1 = 0, OE = 0, ADDR = "".
-OE -tOE> DATA = "";
+CS1 = 0, OE = 0, ADDR = " ".
+OE -tOE> DATA = " ";
-- cut --

Can it be a regression in GraphicsMagick or may be caused by something else?

Regards,
Laszlo/GCS
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759956


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

Bug#762901: python-clang-3.6 and python-clang-3.5: error when trying to install together

[Ralf Treinen]

Package: python-clang-3.5,python-clang-3.6
Version: python-clang-3.5/1:3.5-2
Version: python-clang-3.6/1:3.6~svn218446-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2014-09-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package libdb5.3:amd64.
(Reading database ... 10877 files and directories currently installed.)
Preparing to unpack .../libdb5.3_5.3.28-6_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-6) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-6) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.1-2_amd64.deb ...
Unpacking libffi6:amd64 (3.1-2) ...
Selecting previously unselected package libpython2.7-minimal:amd64.
Preparing to unpack .../libpython2.7-minimal_2.7.8-7_amd64.deb ...
Unpacking libpython2.7-minimal:amd64 (2.7.8-7) ...
Selecting previously unselected package python2.7-minimal.
Preparing to unpack .../python2.7-minimal_2.7.8-7_amd64.deb ...
Unpacking python2.7-minimal (2.7.8-7) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../mime-support_3.56_all.deb ...
Unpacking mime-support (3.56) ...
Selecting previously unselected package libpython2.7-stdlib:amd64.
Preparing to unpack .../libpython2.7-stdlib_2.7.8-7_amd64.deb ...
Unpacking libpython2.7-stdlib:amd64 (2.7.8-7) ...
Selecting previously unselected package python2.7.
Preparing to unpack .../python2.7_2.7.8-7_amd64.deb ...
Unpacking python2.7 (2.7.8-7) ...
Selecting previously unselected package python-minimal.
Preparing to unpack .../python-minimal_2.7.8-1_amd64.deb ...
Unpacking python-minimal (2.7.8-1) ...
Selecting previously unselected package libpython-stdlib:amd64.
Preparing to unpack .../libpython-stdlib_2.7.8-1_amd64.deb ...
Unpacking libpython-stdlib:amd64 (2.7.8-1) ...
Selecting previously unselected package python.
Preparing to unpack .../python_2.7.8-1_amd64.deb ...
Unpacking python (2.7.8-1) ...
Selecting previously unselected package python-clang-3.5.
Preparing to unpack .../python-clang-3.5_1%3a3.5-2_amd64.deb ...
Unpacking python-clang-3.5 (1:3.5-2) ...
Selecting previously unselected package python-clang-3.6.
Preparing to unpack .../python-clang-3.6_1%3a3.6~svn218446-1_amd64.deb ...
Unpacking python-clang-3.6 (1:3.6~svn218446-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-clang-3.6_1%3a3.6~svn218446-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/python2.7/dist-packages/clang/enumerations.py', 
which is also in package python-clang-3.5 1:3.5-2
Processing triggers for man-db (2.7.0.1-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/python-clang-3.6_1%3a3.6~svn218446-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/python2.7/dist-packages/clang/__init__.py
  /usr/lib/python2.7/dist-packages/clang/cindex.py
  /usr/lib/python2.7/dist-packages/clang/enumerations.py

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


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

Bug#762902: python-lldb-3.4 and lldb-3.3: error when trying to install together

[Ralf Treinen]

Package: lldb-3.3,python-lldb-3.4
Version: lldb-3.3/1:3.3-16
Version: python-lldb-3.4/1:3.4.2-9
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2014-09-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package libdb5.3:amd64.
(Reading database ... 10877 files and directories currently installed.)
Preparing to unpack .../libdb5.3_5.3.28-6_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-6) ...
Selecting previously unselected package libbsd0:amd64.
Preparing to unpack .../libbsd0_0.7.0-2_amd64.deb ...
Unpacking libbsd0:amd64 (0.7.0-2) ...
Selecting previously unselected package libedit2:amd64.
Preparing to unpack .../libedit2_3.1-20140620-2_amd64.deb ...
Unpacking libedit2:amd64 (3.1-20140620-2) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ...
Selecting previously unselected package libisl10:amd64.
Preparing to unpack .../libisl10_0.12.2-2_amd64.deb ...
Unpacking libisl10:amd64 (0.12.2-2) ...
Selecting previously unselected package libcloog-isl4:amd64.
Preparing to unpack .../libcloog-isl4_0.18.2-1_amd64.deb ...
Unpacking libcloog-isl4:amd64 (0.18.2-1) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-6) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.1-2_amd64.deb ...
Unpacking libffi6:amd64 (3.1-2) ...
Selecting previously unselected package libllvm3.3:amd64.
Preparing to unpack .../libllvm3.3_1%3a3.3-16_amd64.deb ...
Unpacking libllvm3.3:amd64 (1:3.3-16) ...
Selecting previously unselected package libpython2.7-minimal:amd64.
Preparing to unpack .../libpython2.7-minimal_2.7.8-7_amd64.deb ...
Unpacking libpython2.7-minimal:amd64 (2.7.8-7) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../mime-support_3.56_all.deb ...
Unpacking mime-support (3.56) ...
Selecting previously unselected package libpython2.7-stdlib:amd64.
Preparing to unpack .../libpython2.7-stdlib_2.7.8-7_amd64.deb ...
Unpacking libpython2.7-stdlib:amd64 (2.7.8-7) ...
Selecting previously unselected package libpython2.7:amd64.
Preparing to unpack .../libpython2.7_2.7.8-7_amd64.deb ...
Unpacking libpython2.7:amd64 (2.7.8-7) ...
Selecting previously unselected package python2.7-minimal.
Preparing to unpack .../python2.7-minimal_2.7.8-7_amd64.deb ...
Unpacking python2.7-minimal (2.7.8-7) ...
Selecting previously unselected package python2.7.
Preparing to unpack .../python2.7_2.7.8-7_amd64.deb ...
Unpacking python2.7 (2.7.8-7) ...
Selecting previously unselected package python-minimal.
Preparing to unpack .../python-minimal_2.7.8-1_amd64.deb ...
Unpacking python-minimal (2.7.8-1) ...
Selecting previously unselected package libpython-stdlib:amd64.
Preparing to unpack .../libpython-stdlib_2.7.8-1_amd64.deb ...
Unpacking libpython-stdlib:amd64 (2.7.8-1) ...
Selecting previously unselected package python.
Preparing to unpack .../python_2.7.8-1_amd64.deb ...
Unpacking python (2.7.8-1) ...
Selecting previously unselected package libjsoncpp0.
Preparing to unpack .../libjsoncpp0_0.6.0~rc2-3_amd64.deb ...
Unpacking libjsoncpp0 (0.6.0~rc2-3) ...
Selecting previously unselected package libffi-dev:amd64.
Preparing to unpack .../libffi-dev_3.1-2_amd64.deb ...
Unpacking libffi-dev:amd64 (3.1-2) ...
Selecting previously unselected package binfmt-support.
Preparing to unpack .../binfmt-support_2.1.5-1_amd64.deb ...
Unpacking binfmt-support (2.1.5-1) ...
Selecting previously unselected package llvm-3.3-runtime.
Preparing to unpack .../llvm-3.3-runtime_1%3a3.3-16_amd64.deb ...
Unpacking llvm-3.3-runtime (1:3.3-16) ...
Selecting previously unselected package llvm-3.3.
Preparing to unpack .../llvm-3.3_1%3a3.3-16_amd64.deb ...
Unpacking llvm-3.3 (1:3.3-16) ...
Selecting previously unselected package llvm-3.3-dev.
Preparing to unpack .../llvm-3.3-dev_1%3a3.3-16_amd64.deb ...
Unpacking llvm-3.3-dev (1:3.3-16) ...
Selecting previously unselected package lldb-3.3.
Preparing to unpack .../lldb-3.3_1%3a3.3-16_amd64.deb ...
Unpacking lldb-3.3 (1:3.3-16) ...
Selecting previously unselected package python-lldb-3.4.
Preparing to unpack .../python-lldb-3.4_1%3a3.4.2-9_amd64.deb ...
Unpacking python-lldb-3.4 (1:3.4.2-9) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-lldb-3.4_1%3a3.4.2-9_amd64.deb (--unpack):
 trying to overwrite 
'/usr/lib/python2.7/dist-packages/lldb/utils/symbolication.py', which is also 
in package lldb-3.3 1:3.3-16
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.0.1-1) ...
Processing triggers for install-info (5.2.0.dfsg.1-4) ...
Errors were encountered while pro

Processed: Re: Bug#762863: when using systemd laptop-mode-tools causes read-only root and system is unusable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #762863 [laptop-mode-tools] when using systemd laptop-mode-tools causes 
read-only root and system is unusable
Severity set to 'normal' from 'serious'
> tag -1 +moreinfo
Bug #762863 [laptop-mode-tools] when using systemd laptop-mode-tools causes 
read-only root and system is unusable
Added tag(s) moreinfo.

-- 
762863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762863
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#762863: when using systemd laptop-mode-tools causes read-only root and system is unusable

[Ritesh Raj Sarraf]

Control: severity -1 normal
Control: tag -1 +moreinfo

Wow... A bug with severity serious and no information at all.

On Friday 26 September 2014 12:25 AM, Gianluigi Tiesi wrote:

Package: laptop-mode-tools
Severity: serious

Hi,
if I use systemd and I'm on battery, my system starts with
a read only root and half of the services are not working.


I am using systemd along with laptop-mode-tools for some time now, with 
no issues so far.

Please provide more information

--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

Processed: notfound 762760 in 4.1-3, notfound 762760 in 4.2+dfsg-0.1, notfound 762760 in 4.3-9 ...

[Debian Bug Tracking System]

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

> notfound 762760 4.1-3
Bug #762760 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
Bug #762761 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
No longer marked as found in versions bash/4.1-3.
No longer marked as found in versions bash/4.1-3.
> notfound 762760 4.2+dfsg-0.1
Bug #762760 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
Bug #762761 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
No longer marked as found in versions bash/4.2+dfsg-0.1.
No longer marked as found in versions bash/4.2+dfsg-0.1.
> notfound 762760 4.3-9
Bug #762760 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
Bug #762761 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
No longer marked as found in versions bash/4.3-9.
No longer marked as found in versions bash/4.3-9.
> retitle 762760 bash: CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762760 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
Bug #762761 {Done: Thijs Kinkhorst } [bash] Re: Bug#762760: 
bash: CVE-2014-7169 due to incomplete fix
Changed Bug title to 'bash: CVE-2014-7169: Incomplete fix for CVE-2014-6271' 
from 'Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix'
Changed Bug title to 'bash: CVE-2014-7169: Incomplete fix for CVE-2014-6271' 
from 'Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix'
> found 762760 4.1-3+deb6u1
Bug #762760 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762761 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Marked as found in versions bash/4.1-3+deb6u1.
Marked as found in versions bash/4.1-3+deb6u1.
> found 762760 4.2+dfsg-0.1+deb7u1
Bug #762760 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762761 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Ignoring request to alter found versions of bug #762760 to the same values 
previously set
Ignoring request to alter found versions of bug #762761 to the same values 
previously set
> found 762760 4.3-9.1
Bug #762760 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762761 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Ignoring request to alter found versions of bug #762760 to the same values 
previously set
Ignoring request to alter found versions of bug #762761 to the same values 
previously set
> fixed 762760 4.1-3+deb6u2
Bug #762760 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762761 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Marked as fixed in versions bash/4.1-3+deb6u2; no longer marked as fixed in 
versions 4.1-3+deb6u2.
Marked as fixed in versions bash/4.1-3+deb6u2; no longer marked as fixed in 
versions 4.1-3+deb6u2.
> fixed 762760 4.2+dfsg-0.1+deb7u3
Bug #762760 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762761 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Ignoring request to alter fixed versions of bug #762760 to the same values 
previously set
Ignoring request to alter fixed versions of bug #762761 to the same values 
previously set
> fixed 762760 4.3-9.2
Bug #762760 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Bug #762761 {Done: Thijs Kinkhorst } [bash] bash: 
CVE-2014-7169: Incomplete fix for CVE-2014-6271
Ignoring request to alter fixed versions of bug #762760 to the same values 
previously set
Ignoring request to alter fixed versions of bug #762761 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762760
762761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762761
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#762870: can't boot!

[積丹尼 Dan Jacobson]

All I know is I couldn't boot with that thing at the top of
# ls /boot/ -ltog
-rw-r--r-- 1 2907647 09-26 08:46 initrd.img-3.16-2-686-pae
drwxr-xr-x 54096 09-23 00:39 grub
-rw-r--r-- 1 2726738 09-22 23:00 initrd.img-3.16-1-686-pae
-rw-r--r-- 1 2089608 09-21 01:56 System.map-3.16-2-686-pae
-rw-r--r-- 1  159970 09-21 01:56 config-3.16-2-686-pae
-rw-r--r-- 1 3006608 09-21 01:54 vmlinuz-3.16-2-686-pae
-rw-r--r-- 1 2087689 09-13 14:27 System.map-3.16-1-686-pae
-rw-r--r-- 1  159879 09-13 14:27 config-3.16-1-686-pae
-rw-r--r-- 1 3003440 09-13 14:25 vmlinuz-3.16-1-686-pae
-rw-r--r-- 1 2750492 09-11 10:37 initrd.img-3.14-2-686-pae
-rw-r--r-- 1 1933464 08-09 16:44 System.map-3.14-2-686-pae
-rw-r--r-- 1  157566 08-09 16:44 config-3.14-2-686-pae
-rw-r--r-- 1 2833376 08-09 16:42 vmlinuz-3.14-2-686-pae

so I chose the oldest one from the grub menu and was able to boot.


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

Bug#762870: can't boot!

[積丹尼 Dan Jacobson]

Me too, can't boot.


trace.log
Description: Binary data

Bug#756464: upgrade-reports: [kfreebsd] dist-upgrade to jessie removes the kernel

[Michael Gilbert]

Wouldn't this be fixed somewhat simply if freebsd-net-tools had a
depends: kfreebsd-image-10?  So even though freebsd-image-9 gets
removed due the breaks, the user will at least have the newer kernel
and a bootable system.

This does differ from linux dist-upgrades where it is expected that
the current kernel not go away, but that's possible due to their
avoidance of ABI breakage.  Since freebsd doesn't have that goal,
maybe forced kernel dist-upgrade will be simply unavoidable?

Best wishes,
Mike


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

Processed: closing 762684

[Debian Bug Tracking System]

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

> close 762684 1.71-2.1
Bug #762684 [leptonlib] leptonlib build-depends on libopenjpeg6-dev which is no 
longer built by openjpeg2 source package
There is no source info for the package 'leptonlib' at version '1.71-2.1' with 
architecture ''
Unable to make a source version for version '1.71-2.1'
Marked as fixed in versions 1.71-2.1.
Bug #762684 [leptonlib] leptonlib build-depends on libopenjpeg6-dev which is no 
longer built by openjpeg2 source package
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762684
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#762684: closing 762684

[陳侃如]

close 762684 1.71-2.1
thanks


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

Bug#754757: timeout during g++

[Bas Wijnen]

On Thu, Sep 25, 2014 at 09:50:10PM +1000, Aníbal Monsalve Salazar wrote:
> Please see Dejan's patch at the end of message #25 of bug #754757:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754757#25

Thanks for the reply.  I've seen that patch, but it turns optimization
off.  As I wrote, I think that is undesirable.  Do you mean to say that
the mips team does not want to have this package compiled with
optimization?  That seems like a bad idea to me, but if that's what you
want, I'll do it.

Thanks,
Bas


signature.asc
Description: Digital signature

Bug#761355: closed by Mathieu Malaterre ()

[陳侃如]

Ralf Treinen  writes:

> Hello,
>
> thanks for having investigated that.
>
> On Wed, Sep 24, 2014 at 06:31:04PM +0800, Kan-Ru Chen (陳侃如) wrote:
>> Ralf Treinen  writes:
>> 
>> > On Mon, Sep 15, 2014 at 07:18:12AM +, Debian Bug Tracking System wrote:
>> >
>> >> Date: Mon, 15 Sep 2014 09:15:46 +0200
>> >> From: Mathieu Malaterre 
>> >> To: 761355-d...@bugs.debian.org
>> >> Subject: 
>> >> 
>> >> Control: tags -1 wontfix
>> >> 
>> >> libopenjpeg6-dev never reached testing. closing as wontfix.
>> >
>> > That is not a reason to close a bug while it remains unfixed. Policy
>> > applies to sid as well as to testing or stable. The same holds
>> > of course for #761356 and #761357.
>> 
>> It looks like libopenjpeg6 doesn't exist anymore. It is still in the
>> archive but the source package (openjpeg2) only builds libopenjp2-7. The
>> only rdepends of libopenjpeg6 is leptonlib which still build-depends on
>> libopenjpeg6-dev. leptonlib could be simply rebuilt against
>> libopenjp2-7-dev.
>
> OK. In that case one should simply reassign the bug reports to
> the packages coming from the old version of openjpeg2 (I just 
> did that).
>
>> I think after leptonlib is fixed we should RM libopenjpe6 and friends
>> then mark these bugs as fixed.
>
> No need to do that, the binary packages that are no longer generated
> from the source package will be removed automatically when noone 
> depends on them any longer.

How often do that happen? Even if the packages have inter-dependencies?

> I guess this also means that #762684 can be closed ?

Yes!


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

Bug#762760: Real fix, please!

[Kaz Kylheku]

Can someone provide a patch which removes the whole stupid misfeature 
from bash?


Programs do not need to inject executable code into their children via 
environment variables, even if it is parsed properly. Shell scripted 
applications should properly source all of the functions which they 
need. Personal scripts can obtain functions from the user's .bashrc 
file.


If an attacker somehow gains control over being able to define an 
arbitrary environment variable, the attacker can replace a command like 
"echo" with a harmful function. (That this is possible is easily 
verified by a simple test at your system prompt; it's just a matter of 
the attacker being able to somehow define an environment variable called 
"echo").


Being able to define arbitrary environment variable names with untrusted 
content is a hole in itself, but this feature instantly amplifies the 
hole into an exploit.


At the very least, there should be a loud option to turn on this 
inheritance behavior in the child bash, like "bash 
--parse-functions-from-environment". If this optionn is not supplied, 
then this behavior doesn't occur; variables with contents like "() { 
 }" are left alone.



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

Bug#762730: marked as done (symmetrica: FTBFS: autoreconf: 'configure.ac' or 'configure.in' is required)

[Debian Bug Tracking System]

Your message dated Fri, 26 Sep 2014 01:00:56 +0200
with message-id <54249ea8.2090...@rezozer.net>
and subject line symmetrica: FTBFS: autoreconf: 'configure.ac' or 
'configure.in' is required
has caused the Debian Bug report #762730,
regarding symmetrica: FTBFS: autoreconf: 'configure.ac' or 'configure.in' is 
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.)


-- 
762730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: symmetrica
Version: 2.0+ds-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Automatic builds of symmetrica have been failing:

   debian/rules build-arch
  dh build-arch --with autoreconf --parallel
 dh_testdir -a -O--parallel
 dh_autoreconf -a -O--parallel
  autoreconf: 'configure.ac' or 'configure.in' is required
  dh_autoreconf: autoreconf -f -i returned exit code 1
  make: *** [build-arch] Error 2
  debian/rules:7: recipe for target 'build-arch' failed
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

The problem appears to be that the override_dh_auto_clean target
leaves the tree unpatched, and as such missing configure.ac (which
comes from upstream-autotoolization.patch).  It's not clear that you
need any explicit patch manipulation when using format "3.0 (quilt)",
but if you still do for some reason, please ensure that your patches
are actually in place for the main build* targets.

Thanks!
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Folks,

at the time of writing, the fix is effective.

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

iQEcBAEBAgAGBQJUJJ6VAAoJEIC/w4IMSybjhlcIANOYBGMBvBHu9QGefKpA1SCY
yJAPNal8EdVtHUsTzh6n/cKNl5wJXGyuiEuQlKXnsYp+Lu+24La4Oi4nmMjuyTBm
wF6iWB77Qlz2QWmUk4xUYwJh2viFfFZE/3n3KcfNfrQkVrcQxaNg/a162LuLBlXx
TLYT3CZ/REZXrEDhTwkJgW3MdZ7KS064Yfk4ODTUngWIlWRf2/U/ueyiOzlFX09u
kBg2/MX7Ycr+MmO0uCagPjZKP9Vv7uV6BkrCqOmxeATlzDApcaG0A1c+o0bkO2RR
jUlxM5r+033CrDSByggRCE/LAGdS7NsGBeDYWrI8tJb49YAxsP1Yj0rV32F0IsI=
=AnFa
-END PGP SIGNATURE End Message ---

Bug#762760: marked as done (Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 22:48:37 +
with message-id 
and subject line Bug#762760: fixed in bash 4.1-3+deb6u2
has caused the Debian Bug report #762760,
regarding Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
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.)


-- 
762760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 4.2+dfsg-0.1+deb7u1
Severity: critical
Tags: security

As Tavis Ormandy has tweeted[0], the existing patch is not sufficient to
solve the problem:

  vauxhall ok % dpkg -l bash | grep ^ii; rm -f echo; env X='() { (a)=>\' bash 
-c "echo date"; cat echo
  ii  bash   4.2+dfsg-0.1+deb7u1 amd64GNU Bourne Again SHell
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  Wed Sep 24 23:32:32 UTC 2014

This means all Debian systems are still vulnerable, as bash is an
essential package.

[0] https://twitter.com/taviso/status/514887394294652929
-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-rc5-amd64 (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

Versions of packages bash depends on:
ii  base-files   7.5
ii  dash 0.5.7-4
ii  debianutils  4.4
ii  libc62.19-11
ii  libtinfo55.9+20140913-1

Versions of packages bash recommends:
pn  bash-completion  

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: bash
Source-Version: 4.1-3+deb6u2

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

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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated bash 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 26 Sep 2014 00:10:13 +0200
Source: bash
Binary: bash bash-static bash-builtins bash-doc bashdb
Architecture: source all amd64
Version: 4.1-3+deb6u2
Distribution: squeeze-lts
Urgency: high
Maintainer: Matthias Klose 
Changed-By: Thijs Kinkhorst 
Description: 
 bash   - The GNU Bourne Again SHell
 bash-builtins - Bash loadable builtins - headers & examples
 bash-doc   - Documentation and examples for the The GNU Bourne Again SHell
 bash-static - The GNU Bourne Again SHell (static version)
 bashdb - The GNU Bourne Again SHell Debugger
Closes: 762760 762761
Changes: 
 bash (4.1-3+deb6u2) squeeze-lts; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add variables-affix.patch patch.
 Apply patch from Florian Weimer to add prefix and suffix for environment
 variable names which contain shell functions.
   * Add parser-oob.patch patch.
 Fixes two out-of-bound array accesses in the bash parser.
   * Add CVE-2014-7169.diff diff.
 CVE-2014-7169: Incomplete fix for CVE-2014-6271. (Closes: #762760, #762761)
Checksums-Sha1: 
 184bc50031cb14c7c34c33160bac67c7c9ac958f 1492 bash_4.1-3+deb6u2.dsc
 97bc09677759cc4009a129cf574301f54a30dfc8 85777 bash_4.1-3+deb6u2.diff.gz
 11d84b8c6c44b22856a886f18f6e4aea84da37fb 678314 bash-doc_4.1-3+deb6u2_all.deb
 f7d3cf7d97e2416d965f9f11685af1b589586a38 1328258 bash_4.1-3+deb6u2_amd64.deb
 a61de3da62f6abbfeb10f779f9e82ddaaccc8443 106852 
bash-builtins_4.1-3+deb6u2_amd64.deb
 ee5da1eb1d39f6542749550810ee8ce9bf4f5f13 884112 
bash-static_4.1-3+deb6u2_amd64.deb
Checksums-Sha256: 
 dcf440868e901733ce02389a5a357eb3eb4794de48ad45d813946168e900f524 1492 
bash_4.1-3+deb6u2.dsc
 e64ee3179d581b8274ca245661fb713d532f861b369e9a1f1319df1c34c46012 85777 
bash_4.1-3+deb6u2.

Bug#762761: marked as done (Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 22:48:37 +
with message-id 
and subject line Bug#762760: fixed in bash 4.1-3+deb6u2
has caused the Debian Bug report #762760,
regarding Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
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.)


-- 
762760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 4.2+dfsg-0.1+deb7u1
Severity: grave
Tags: security

http://seclists.org/oss-sec/2014/q3/679

root@diatom:/tmp/empty>bash --version
GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
root@diatom:/tmp/empty>ls
root@diatom:/tmp/empty>X='() { function a a>\' bash -c gohomeyourdrunk
bash: X: line 1: syntax error near unexpected token `a'
bash: X: line 1: `'
bash: error importing function definition for `X'
root@diatom:/tmp/empty>ls
gohomeyourdrunk
root@diatom:/tmp/empty>

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: bash
Source-Version: 4.1-3+deb6u2

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

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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated bash 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 26 Sep 2014 00:10:13 +0200
Source: bash
Binary: bash bash-static bash-builtins bash-doc bashdb
Architecture: source all amd64
Version: 4.1-3+deb6u2
Distribution: squeeze-lts
Urgency: high
Maintainer: Matthias Klose 
Changed-By: Thijs Kinkhorst 
Description: 
 bash   - The GNU Bourne Again SHell
 bash-builtins - Bash loadable builtins - headers & examples
 bash-doc   - Documentation and examples for the The GNU Bourne Again SHell
 bash-static - The GNU Bourne Again SHell (static version)
 bashdb - The GNU Bourne Again SHell Debugger
Closes: 762760 762761
Changes: 
 bash (4.1-3+deb6u2) squeeze-lts; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add variables-affix.patch patch.
 Apply patch from Florian Weimer to add prefix and suffix for environment
 variable names which contain shell functions.
   * Add parser-oob.patch patch.
 Fixes two out-of-bound array accesses in the bash parser.
   * Add CVE-2014-7169.diff diff.
 CVE-2014-7169: Incomplete fix for CVE-2014-6271. (Closes: #762760, #762761)
Checksums-Sha1: 
 184bc50031cb14c7c34c33160bac67c7c9ac958f 1492 bash_4.1-3+deb6u2.dsc
 97bc09677759cc4009a129cf574301f54a30dfc8 85777 bash_4.1-3+deb6u2.diff.gz
 11d84b8c6c44b22856a886f18f6e4aea84da37fb 678314 bash-doc_4.1-3+deb6u2_all.deb
 f7d3cf7d97e2416d965f9f11685af1b589586a38 1328258 bash_4.1-3+deb6u2_amd64.deb
 a61de3da62f6abbfeb10f779f9e82ddaaccc8443 106852 
bash-builtins_4.1-3+deb6u2_amd64.deb
 ee5da1eb1d39f6542749550810ee8ce9bf4f5f13 884112 
bash-static_4.1-3+deb6u2_amd64.deb
Checksums-Sha256: 
 dcf440868e901733ce02389a5a357eb3eb4794de48ad45d813946168e900f524 1492 
bash_4.1-3+deb6u2.dsc
 e64ee3179d581b8274ca245661fb713d532f861b369e9a1f1319df1c34c46012 85777 
bash_4.1-3+deb6u2.diff.gz
 8c9e6467f24c3837d4d03801f9a03f7447fabb85ad68e15690c500a77f4d 678314 
bash-doc_4.1-3+deb6u2_all.deb
 7400f04d074f1699a1993fb79e16d77531fae5739122d87db80ea128cbd62275 1328258 
bash_4.1-3+deb6u2_amd64.deb
 15d75c3fcfe3b7d0b9196fed15ca951101ffd82845bfc66224bf8dd151fcd4de 106852 
bash-builtins_4.1-3+deb6u2_amd64.deb
 eec0ef7041c9ed58ad1aa389da3c33a1bf1f9265eb2d7e9fb6728c198e95 884112 
bash-static_4.1-3+deb6u2_amd64.deb
Files: 
 b01b6c1fa57365c86af7674f286f086b 1492 base required bash_4.1-3+deb6u2.dsc
 565e6ccf144d817df95f956a6b6a49d1 85777 base required bash_4.1-3+deb6u2.diff.gz
 31f749233b5dff0b2c3d7ba878f3c769 678314 doc optional 
bash-doc_4.1-3+deb6u2_all.deb
 ecac954e1879785164537809c6d0d053 1328258 shells required 
bash_4.1-3

Bug#762760: marked as done (Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 22:48:37 +
with message-id 
and subject line Bug#762761: fixed in bash 4.1-3+deb6u2
has caused the Debian Bug report #762761,
regarding Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
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.)


-- 
762761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 4.2+dfsg-0.1+deb7u1
Severity: critical
Tags: security

As Tavis Ormandy has tweeted[0], the existing patch is not sufficient to
solve the problem:

  vauxhall ok % dpkg -l bash | grep ^ii; rm -f echo; env X='() { (a)=>\' bash 
-c "echo date"; cat echo
  ii  bash   4.2+dfsg-0.1+deb7u1 amd64GNU Bourne Again SHell
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  Wed Sep 24 23:32:32 UTC 2014

This means all Debian systems are still vulnerable, as bash is an
essential package.

[0] https://twitter.com/taviso/status/514887394294652929
-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-rc5-amd64 (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

Versions of packages bash depends on:
ii  base-files   7.5
ii  dash 0.5.7-4
ii  debianutils  4.4
ii  libc62.19-11
ii  libtinfo55.9+20140913-1

Versions of packages bash recommends:
pn  bash-completion  

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: bash
Source-Version: 4.1-3+deb6u2

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

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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated bash 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 26 Sep 2014 00:10:13 +0200
Source: bash
Binary: bash bash-static bash-builtins bash-doc bashdb
Architecture: source all amd64
Version: 4.1-3+deb6u2
Distribution: squeeze-lts
Urgency: high
Maintainer: Matthias Klose 
Changed-By: Thijs Kinkhorst 
Description: 
 bash   - The GNU Bourne Again SHell
 bash-builtins - Bash loadable builtins - headers & examples
 bash-doc   - Documentation and examples for the The GNU Bourne Again SHell
 bash-static - The GNU Bourne Again SHell (static version)
 bashdb - The GNU Bourne Again SHell Debugger
Closes: 762760 762761
Changes: 
 bash (4.1-3+deb6u2) squeeze-lts; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add variables-affix.patch patch.
 Apply patch from Florian Weimer to add prefix and suffix for environment
 variable names which contain shell functions.
   * Add parser-oob.patch patch.
 Fixes two out-of-bound array accesses in the bash parser.
   * Add CVE-2014-7169.diff diff.
 CVE-2014-7169: Incomplete fix for CVE-2014-6271. (Closes: #762760, #762761)
Checksums-Sha1: 
 184bc50031cb14c7c34c33160bac67c7c9ac958f 1492 bash_4.1-3+deb6u2.dsc
 97bc09677759cc4009a129cf574301f54a30dfc8 85777 bash_4.1-3+deb6u2.diff.gz
 11d84b8c6c44b22856a886f18f6e4aea84da37fb 678314 bash-doc_4.1-3+deb6u2_all.deb
 f7d3cf7d97e2416d965f9f11685af1b589586a38 1328258 bash_4.1-3+deb6u2_amd64.deb
 a61de3da62f6abbfeb10f779f9e82ddaaccc8443 106852 
bash-builtins_4.1-3+deb6u2_amd64.deb
 ee5da1eb1d39f6542749550810ee8ce9bf4f5f13 884112 
bash-static_4.1-3+deb6u2_amd64.deb
Checksums-Sha256: 
 dcf440868e901733ce02389a5a357eb3eb4794de48ad45d813946168e900f524 1492 
bash_4.1-3+deb6u2.dsc
 e64ee3179d581b8274ca245661fb713d532f861b369e9a1f1319df1c34c46012 85777 
bash_4.1-3+deb6u2.

Bug#762761: marked as done (Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 22:48:37 +
with message-id 
and subject line Bug#762761: fixed in bash 4.1-3+deb6u2
has caused the Debian Bug report #762761,
regarding Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
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.)


-- 
762761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 4.2+dfsg-0.1+deb7u1
Severity: grave
Tags: security

http://seclists.org/oss-sec/2014/q3/679

root@diatom:/tmp/empty>bash --version
GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
root@diatom:/tmp/empty>ls
root@diatom:/tmp/empty>X='() { function a a>\' bash -c gohomeyourdrunk
bash: X: line 1: syntax error near unexpected token `a'
bash: X: line 1: `'
bash: error importing function definition for `X'
root@diatom:/tmp/empty>ls
gohomeyourdrunk
root@diatom:/tmp/empty>

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: bash
Source-Version: 4.1-3+deb6u2

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

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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated bash 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 26 Sep 2014 00:10:13 +0200
Source: bash
Binary: bash bash-static bash-builtins bash-doc bashdb
Architecture: source all amd64
Version: 4.1-3+deb6u2
Distribution: squeeze-lts
Urgency: high
Maintainer: Matthias Klose 
Changed-By: Thijs Kinkhorst 
Description: 
 bash   - The GNU Bourne Again SHell
 bash-builtins - Bash loadable builtins - headers & examples
 bash-doc   - Documentation and examples for the The GNU Bourne Again SHell
 bash-static - The GNU Bourne Again SHell (static version)
 bashdb - The GNU Bourne Again SHell Debugger
Closes: 762760 762761
Changes: 
 bash (4.1-3+deb6u2) squeeze-lts; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add variables-affix.patch patch.
 Apply patch from Florian Weimer to add prefix and suffix for environment
 variable names which contain shell functions.
   * Add parser-oob.patch patch.
 Fixes two out-of-bound array accesses in the bash parser.
   * Add CVE-2014-7169.diff diff.
 CVE-2014-7169: Incomplete fix for CVE-2014-6271. (Closes: #762760, #762761)
Checksums-Sha1: 
 184bc50031cb14c7c34c33160bac67c7c9ac958f 1492 bash_4.1-3+deb6u2.dsc
 97bc09677759cc4009a129cf574301f54a30dfc8 85777 bash_4.1-3+deb6u2.diff.gz
 11d84b8c6c44b22856a886f18f6e4aea84da37fb 678314 bash-doc_4.1-3+deb6u2_all.deb
 f7d3cf7d97e2416d965f9f11685af1b589586a38 1328258 bash_4.1-3+deb6u2_amd64.deb
 a61de3da62f6abbfeb10f779f9e82ddaaccc8443 106852 
bash-builtins_4.1-3+deb6u2_amd64.deb
 ee5da1eb1d39f6542749550810ee8ce9bf4f5f13 884112 
bash-static_4.1-3+deb6u2_amd64.deb
Checksums-Sha256: 
 dcf440868e901733ce02389a5a357eb3eb4794de48ad45d813946168e900f524 1492 
bash_4.1-3+deb6u2.dsc
 e64ee3179d581b8274ca245661fb713d532f861b369e9a1f1319df1c34c46012 85777 
bash_4.1-3+deb6u2.diff.gz
 8c9e6467f24c3837d4d03801f9a03f7447fabb85ad68e15690c500a77f4d 678314 
bash-doc_4.1-3+deb6u2_all.deb
 7400f04d074f1699a1993fb79e16d77531fae5739122d87db80ea128cbd62275 1328258 
bash_4.1-3+deb6u2_amd64.deb
 15d75c3fcfe3b7d0b9196fed15ca951101ffd82845bfc66224bf8dd151fcd4de 106852 
bash-builtins_4.1-3+deb6u2_amd64.deb
 eec0ef7041c9ed58ad1aa389da3c33a1bf1f9265eb2d7e9fb6728c198e95 884112 
bash-static_4.1-3+deb6u2_amd64.deb
Files: 
 b01b6c1fa57365c86af7674f286f086b 1492 base required bash_4.1-3+deb6u2.dsc
 565e6ccf144d817df95f956a6b6a49d1 85777 base required bash_4.1-3+deb6u2.diff.gz
 31f749233b5dff0b2c3d7ba878f3c769 678314 doc optional 
bash-doc_4.1-3+deb6u2_all.deb
 ecac954e1879785164537809c6d0d053 1328258 shells required 
bash_4.1-3

Bug#762870: initramfs-tools: fails to boot after upgrade from 0.116 to 0.117

[Axel Beckert]

Hi Mika,

Michael Prokop wrote:
> * pdorm...@free.fr [Thu Sep 25, 2014 at 10:21:42PM +0200]:
> 
> > System fails to boot with 0.117.
> > Following messages are displayed:
> 
> > -f: No such file or directory
> > fsck: No such file or directory
> > fsck exited with status code 1
> > Usage : mount [-r] [-w] [-o options] [-t type] [-f] [-i ] [-n] device 
> > directory
> > mount: No such file or directory
> > Could not copy file: No such file or directory
> > Target filesystem doesn't have requested /sbin/init
> > No init found. Try passing init=bootarg

as mentioned on IRC, this currently makes xen-tools no more being able
to create Xen DomU running Sid. It still can create them, they fail to
boot as follows, too:

[1.206468] xenbus_probe_frontend: Device with no driver: device/vbd/51714
[1.206472] xenbus_probe_frontend: Device with no driver: device/vbd/51713
[1.206477] xenbus_probe_frontend: Device with no driver: device/vif/0
[1.206521] /build/linux-P15SNz/linux-3.16.3/drivers/rtc/hctosys.c: unable 
to open rtc device (rtc0)
[1.207696] Freeing unused kernel memory: 1196K (818ed000 - 
81a18000)
[1.207712] Write protecting the kernel read-only data: 8192k
[1.211765] Freeing unused kernel memory: 944K (880001514000 - 
88000160)
[1.211978] Freeing unused kernel memory: 224K (8800017c8000 - 
88000180)
Loading, please wait...
[1.236483] systemd-udevd[58]: starting version 215
[1.237364] random: systemd-udevd urandom read with 3 bits of entropy 
available
[1.261487] xen_netfront: Initialising Xen virtual ethernet driver
[1.300840] blkfront: xvda2: flush diskcache: enabled; persistent grants: 
enabled; indirect descriptors: enabled;
[1.303567] blkfront: xvda1: flush diskcache: enabled; persistent grants: 
enabled; indirect descriptors: enabled;
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
-f: No such file or directory
Begin: Checking  file system ... fsck: No such file or directory
fsck exited with status code 1
done.
Usage: mount [-r] [-w] [-o options] [-t type] [-f] [-i] [-n] device directory
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... mount: No such file or directory
done.
Could not copy file: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
[1.665567] usbcore: registered new interface driver usbfs
[1.665916] usbcore: registered new interface driver hub
[1.665976] usbcore: registered new device driver usb
[1.55] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[1.666840] ehci-pci: EHCI PCI platform driver
[1.673431] uhci_hcd: USB Universal Host Controller Interface driver
[1.676679] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[1.680132] hidraw: raw HID events driver (C) Jiri Kosina
[1.680892] usbcore: registered new interface driver usbhid
[1.680897] usbhid: USB HID core driver
(initramfs) ls /sbin/fsck
-rwxr-xr-x 1 0 0 31544 /sbin/fsck

> Do you have a separate /usr partition?

No.

> If so, is it a normal partition or used on top of LVM/RAID/...?

/dev/xvda2 does not use LVM inside the virtual machine, but on the
hosting machine, it's an LV at /dev/${vg}/${hostname}-disk.

> Can you please execute:
> 
>   bash -x mkinitramfs -o /dev/null >/tmp/trace.log 2>&1

Attached the (compressed) output from "bash -x /usr/sbin/mkinitramfs
-o /dev/null 3.16-2-amd64 >/root/trace.log 2>&1"

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


trace.log.xz
Description: Binary data

Processed: fixed 762760 in 4.1-3+deb6u2, fixed 762760 in 4.2+dfsg-0.1+deb7u3, fixed 762760 in 4.3-9.2 ...

[Debian Bug Tracking System]

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

> fixed 762760 4.1-3+deb6u2
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
There is no source info for the package 'bash' at version '4.1-3+deb6u2' with 
architecture ''
Unable to make a source version for version '4.1-3+deb6u2'
Marked as fixed in versions 4.1-3+deb6u2.
Marked as fixed in versions 4.1-3+deb6u2.
> fixed 762760 4.2+dfsg-0.1+deb7u3
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Marked as fixed in versions bash/4.2+dfsg-0.1+deb7u3.
Marked as fixed in versions bash/4.2+dfsg-0.1+deb7u3.
> fixed 762760 4.3-9.2
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Marked as fixed in versions bash/4.3-9.2.
Marked as fixed in versions bash/4.3-9.2.
> close 762760
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762760
762761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762761
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: affects 762870

[Debian Bug Tracking System]

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

> affects 762870 xen-tools
Bug #762870 [initramfs-tools] initramfs-tools: fails to boot after upgrade from 
0.116 to 0.117
Added indication that 762870 affects xen-tools
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762870
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#762838: Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace”

[Kamil Jońca]

I can confirm this bug. 
My *suspection* is that crash after resolvin my own zone. 
IE if bind is authoritative for zone 'kjonca' then 
$dig alfa.kjonca 
causes crash. 
When bind is only forwarding queries it can work pretty long.

KJ

-- 
http://wolnelektury.pl/wesprzyj/teraz/


-- 
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 762870 is serious

[Debian Bug Tracking System]

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

> severity 762870 serious
Bug #762870 [initramfs-tools] initramfs-tools: fails to boot after upgrade from 
0.116 to 0.117
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762870
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#747090: marked as done (systemtap: does not work with kernel 3.14 with enabled USER_NS)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 21:51:29 +
with message-id 
and subject line Bug#747090: fixed in systemtap 2.6-0.1
has caused the Debian Bug report #747090,
regarding systemtap: does not work with kernel 3.14 with enabled USER_NS
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.)


-- 
747090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemtap
Version: 2.3-2
Severity: important
Tags: patch

Doesn't work with 3.15-rc3 either. :-)

Applying this patch:
https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=c91d2e7cc991068fd701d75a4814db87913d57bd
or packaging a newer version should fix this.

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

Kernel: Linux 3.15.0-rc3-lis64+ (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages systemtap depends on:
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc6  2.18-5
ii  libdw1 0.157-3
ii  libelf10.157-3
ii  libgcc11:4.9.0-1
ii  libnspr4   2:4.10.4-1
ii  libnspr4-0d2:4.10.4-1
ii  libnss32:3.16-1
ii  libnss3-1d 2:3.16-1
ii  libsqlite3-0   3.8.4.3-1
ii  libstdc++6 4.9.0-1
ii  make   3.81-8.3
ii  systemtap-common   2.3-2
ii  systemtap-runtime  2.3-2

systemtap recommends no packages.

Versions of packages systemtap suggests:
pn  systemtap-doc  
ii  vim-addon-manager  0.5.3

-- no debconf information

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
--- End Message ---
--- Begin Message ---
Source: systemtap
Source-Version: 2.6-0.1

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

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 747...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated systemtap 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 25 Sep 2014 22:44:45 +0200
Source: systemtap
Binary: systemtap systemtap-common systemtap-runtime systemtap-doc 
systemtap-server systemtap-client systemtap-sdt-dev
Architecture: source amd64 all
Version: 2.6-0.1
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 systemtap  - instrumentation system for Linux
 systemtap-client - instrumentation system for Linux (client for compile server)
 systemtap-common - instrumentation system for Linux (common component)
 systemtap-doc - documentation and examples for SystemTap
 systemtap-runtime - instrumentation system for Linux (runtime component)
 systemtap-sdt-dev - statically defined probes development files
 systemtap-server - instrumentation system for Linux (compile server)
Closes: 747090 761168
Changes:
 systemtap (2.6-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release
 - No longer fails to compile with recent Debian kernels
   (Closes: #747090)
 - No longer fails to compile procfs probes (Closes: #761168)
   * Rebased patches
   * Changed dh-autoreconf build-dependency to autotools-dev as noticed by
 Lintian
Checksums-Sha1:
 1bfbaf2c80a5008022152457e0dd3db39ac584c8 2129 systemtap_2.6-0.1.dsc
 9663615574b94aa2c69b33292c182df407a2a858 2842153 systemtap_2.6.orig.tar.gz
 3a0ec12aa6f8be75de0846b1492defe45b021633 19452 systemtap_2.6-0.1.debian.tar.xz
 eab40fe2db0032a053d95104b86da66c1c36b1b3 927878 systemtap_2.6-0.1_amd64.deb
 f3cafe6b1df6b874c7226577c840517e1c877087 420970 
systemtap-common_2.6-0.1_all.deb
 eee096950ba019a6d9612f0047881daa41075c8e 116474 
systemtap-runtime_2.6-0.1_amd64.deb
 808cc839589baed4039e0dfd300c8c32397a35c8 1161142 systemtap-doc_2.6-0.1_all.deb
 bcb9e3dc29cbe5a1351d2b15156ac9809226365d 128970 
systemtap-server_2.6-0.1_amd64.deb
 b21bdcf0779e7f149bc1ec269569822b7d7121df 17850 
systemtap-cli

Processed: forcibly merging 762838 762876

[Debian Bug Tracking System]

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

> forcemerge 762838 762876
Bug #762838 [bind9] [bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != 
((void *)0)) failed, back trace”
Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c
Severity set to 'grave' from 'normal'
Merged 762838 762876
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762838
762876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762876
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 762638

[Debian Bug Tracking System]

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

> tags 762638 + confirmed
Bug #762638 [src:perl] missing source: Configure
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762638
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: Re: forcibly merging 756464 752194

[Debian Bug Tracking System]

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

> reassign 752194 freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10
Bug #752194 [src:kfreebsd-10] upgrade wheezy->jessie removes kernel
Bug reassigned from package 'src:kfreebsd-10' to 
'freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10'.
Ignoring request to alter found versions of bug #752194 to the same values 
previously set
Ignoring request to alter fixed versions of bug #752194 to the same values 
previously set
> severity 752194 serious
Bug #752194 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade 
wheezy->jessie removes kernel
Severity set to 'serious' from 'important'
> tags 752194 jessie sid help
Bug #752194 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade 
wheezy->jessie removes kernel
Added tag(s) sid, help, and jessie.
> reassign 756464 freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10
Bug #756464 [freebsd-net-tools] upgrade-reports: [kfreebsd] dist-upgrade to 
jessie removes the kernel
Bug reassigned from package 'freebsd-net-tools' to 
'freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10'.
Ignoring request to alter found versions of bug #756464 to the same values 
previously set
Ignoring request to alter fixed versions of bug #756464 to the same values 
previously set
> severity 756464 serious
Bug #756464 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade-reports: 
[kfreebsd] dist-upgrade to jessie removes the kernel
Severity set to 'serious' from 'critical'
> tags 756464 jessie sid help
Bug #756464 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade-reports: 
[kfreebsd] dist-upgrade to jessie removes the kernel
Added tag(s) help.
> merge 756464 752194
Bug #756464 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade-reports: 
[kfreebsd] dist-upgrade to jessie removes the kernel
Bug #752194 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade 
wheezy->jessie removes kernel
Merged 752194 756464
> found 752194 freebsd-utils/10.0+ds1-1
Bug #752194 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade 
wheezy->jessie removes kernel
Bug #756464 [freebsd-net-tools,src:kfreebsd-9,src:kfreebsd-10] upgrade-reports: 
[kfreebsd] dist-upgrade to jessie removes the kernel
Marked as found in versions freebsd-utils/10.0+ds1-1.
Marked as found in versions freebsd-utils/10.0+ds1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
752194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752194
756464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756464
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#762444: RFS: axis 1.4-21 [RC]

[Markus Koschany]

Control: tags -1 patch

Hi,

I have prepared a new revision for axis which addresses the security
vulnerability, bug #762444, and I am looking for someone who wants to
review and upload the package.

The package can either be found at mentors.debian.net

http://mentors.debian.net/debian/pool/main/a/axis/axis_1.4-21.dsc

or in the SVN repository.

I think this issue warrants a DSA and I also intend to prepare a fix for
wheezy soonish.

Changelog:

* Team upload.
* Fix CVE-2014-3596.
  - Relace 06-fix-CVE-2012-5784.patch with CVE-2014-3596.patch which fixes
both CVE issues. Thanks to Raphael Hertzog for the report.
  - The getCN function in Apache Axis 1.4 and earlier does not properly
verify that the server hostname matches a domain name in the subject's
Common Name (CN) or subjectAltName field of the X.509 certificate,
which allows man-in-the-middle attackers to spoof SSL servers via a
certificate with a subject that specifies a common name in a field
that is not the CN field.  NOTE: this issue exists because of an
incomplete fix for CVE-2012-5784.
  - (Closes: #762444)
* Declare compliance with Debian Policy 3.9.6.
* Use compat level 9 and require debhelper >=9.
* Use canonical VCS fields.

Markus


signature.asc
Description: Digital signature

Processed: RFS: axis 1.4-21 [RC]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #762444 [axis] Insecure certificate validation CVE-2014-3596
Added tag(s) patch.

-- 
762444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762444
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#545414: sudo-ldap: sudo fails with "sudo: setreuid(ROOT_UID,

[ramon vazquez]

Date: Sun, 06 Sep 2009 20:50:54 -0400
>From: ben thielsen 
>-
>Body: Package: sudo-ldap
>Version: 1.7.2-2
>Severity: important
>
>both sudo and sudo-ldap fail when a user in ldap attempts to use sudo (for
example, sudo su). with the following message:
>
>sudo: setreuid(ROOT_UID, user_uid): Operation not permitted
>
>users in the traditional passwd database don't appear to be affected.
>
>this system uses ldap with both nss and pam.  all other aspects related to
ldap appear to be working (e.g. id, getent, etc.).  i don't have a solution
>to offer, as i was not able to successfully troubleshoot the problem, but
am happy to test ideas if it helps.  i'll wait to
>include various config files until requested.
>
>-- System Information:
>Debian Release: squeeze/sid
>  APT prefers testing
>  APT policy: (500, 'testing')
>Architecture: i386 (i686)
>
>Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
>Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
>Shell: /bin/sh linked to /bin/dash
>
>Versions of packages sudo-ldap depends on:
>ii  libc6 2.9-25 GNU C Library: Shared
libraries
>ii  libldap-2.4-2 2.4.17-1   OpenLDAP libraries
>ii  libpam-modules1.0.1-10   Pluggable Authentication
Modules f
>ii  libpam0g  1.0.1-10   Pluggable Authentication
Modules l
>
>sudo-ldap recommends no packages.
>
>sudo-ldap suggests no packages.

Processed: tagging 762146

[Debian Bug Tracking System]

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

> tags 762146 + pending
Bug #762146 [udev] Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762146
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: retitle 762760 Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix

[Debian Bug Tracking System]

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

> # adding CVE number;  see
> # http://www.openwall.com/lists/oss-security/2014/09/25/5
> retitle 762760 Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762760 [bash] bash: still vulnerable to environment exploits
Bug #762761 [bash] security fix incomplete
Changed Bug title to 'Re: Bug#762760: bash: CVE-2014-7169 due to incomplete 
fix' from 'bash: still vulnerable to environment exploits'
Changed Bug title to 'Re: Bug#762760: bash: CVE-2014-7169 due to incomplete 
fix' from 'security fix incomplete'
> # this issue was present before and after the fix for CVE-2014-6271
> found 762760 4.3-9
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Marked as found in versions bash/4.3-9.
Marked as found in versions bash/4.3-9.
> found 762760 bash/4.2+dfsg-0.1
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Marked as found in versions bash/4.2+dfsg-0.1.
Marked as found in versions bash/4.2+dfsg-0.1.
> found 762760 bash/4.1-3
Bug #762760 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Bug #762761 [bash] Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
Marked as found in versions bash/4.1-3.
Marked as found in versions bash/4.1-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762760
762761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762761
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 (with 1 errors): forcibly merging 756464 752194

[Debian Bug Tracking System]

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

> forcemerge 756464 752194
Bug #756464 [freebsd-net-tools] upgrade-reports: [kfreebsd] dist-upgrade to 
jessie removes the kernel
Unable to merge bugs because:
package of #752194 is 'src:kfreebsd-10' not 'freebsd-net-tools'
Failed to forcibly merge 756464: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2f584f0)', 
'requester', 'Jonathan Wiltshire ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<1411678131-2767-bts-...@debian.org>', 'request_subject', ...) called at 
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at 
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', undef, 'clonebugs', 
'HASH(0x2ed0c58)', 'limit', 'HASH(0x2ed0640)', 'common_control_options', 
'ARRAY(0x2ed0688)', 'errors', ...) called at /usr/lib/debbugs/service line 474

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
752194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752194
756464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756464
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#762760: retitle 762760 Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix

[Steven Chamberlain]

# adding CVE number;  see
# http://www.openwall.com/lists/oss-security/2014/09/25/5
retitle 762760 Re: Bug#762760: bash: CVE-2014-7169 due to incomplete fix
# this issue was present before and after the fix for CVE-2014-6271
found 762760 4.3-9
found 762760 bash/4.2+dfsg-0.1
found 762760 bash/4.1-3
thanks


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

Bug#762760: Working on an update

[Thijs Kinkhorst]

Hi,

The security team is working on an update which includes amongst others
the patch referenced in this bug.


Thijs


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

Bug#762835: error exit on dafileserver (segfault)

[Benjamin Kaduk]

On Thu, 25 Sep 2014, Thomas Otto wrote:

>
>
> Package: openafs-fileserver
> Version: 1.6.1-3+deb7u2
> Severity: serious
>
>
> Hello,
>
> i used the actual (updated) debian stable.
>
> since last week our dafileserver has problems and exited quite often.
>
> This affects that some client hangs after that.
> I hope the corefile helps.
>
>
> $ bos status afs03 -long
> Instance dafs, (type is dafs) has core file, currently running normally.
> Auxiliary status is: file server running.
> Process last started at Thu Sep 25 11:10:01 2014 (7 proc starts)
> Last exit at Thu Sep 25 11:10:01 2014
> Last error exit at Thu Sep 25 10:17:11 2014, by file, due to signal 11
> Command 1 is '/usr/lib/openafs/dafileserver -syslog'
> Command 2 is '/usr/lib/openafs/davolserver -syslog'
> Command 3 is '/usr/lib/openafs/salvageserver'
> Command 4 is '/usr/lib/openafs/dasalvager'
>
>
> Sep 25 10:12:43 afs03 fileserver[2494]: nUsers == 0, but header not on LRU
> Sep 25 10:14:24 afs03 fileserver[2494]: FindClient: stillborn client 
> 03F59320(5c5433d4); conn 7FF63802D110 (host 141.35.29.92:7001) 
> had client 03F59250(5c5433d4)
> Sep 25 10:16:41 afs03 fileserver[2494]: CheckHost_r: Probing all interfaces 
> of host 93.128.220.70:7001 failed, code -1
> Sep 25 10:17:10 afs03 fileserver[2494]: Scheduling salvage for volume 
> 536890884 on part /vicepa over SALVSYNC
> Sep 25 10:17:11 afs03 fileserver[2494]: FSYNC_com:  invalid protocol version 
> (3523477760)
> Sep 25 10:17:11 afs03 kernel: [ 2459.331071] dafileserver[2869]: segfault at 
> 9 ip 0009 sp 7ff646302eb8 error 14 in 
> dafileserver[40+ca000]
> Sep 25 10:17:11 afs03 davolserver[2495]: SYNC_ask: No response on circuit 
> 'FSSYNC'
> Sep 25 10:17:11 afs03 davolserver[2495]: SYNC_ask: protocol communications 
> failure on circuit 'FSSYNC'; attempting reconnect to server
> Sep 25 10:17:11 afs03 bosserver[2472]: dafs:file exited on signal 11 (core 
> dumped)

Unfortunately, the core file is not particularly helpful, as the stack
trace for the faulting thread is garbage.

It looks like OPENAFS-SA-2014-002 is fixed in wheezy-backports but not in
wheezy itself.  I have no particular reason to think that that use of
uninitialized memory is responsible for your crash, of course, but can ask
if you are willing to run the newer package from -backports.

That the issues started just a week or two ago is rather odd, as I don't
see any changelog entries in any relevant-seeming packages on my VM from
around that time.  Do you have apt logs that might indicate whether a
particular package update was correlated with the onset of the crashes?

Are you in a position to say anything about the usage patterns of your
AFS clients, in case it becomes necessary to try to reproduce the crash
locally?

Thanks,

Ben


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

Bug#734599: Please help with Java lib

[Andreas Tille]

Hi Debian Java folks,

it seems there is no real progress in this issue.  Do you have any hint
what to do.  BTW (as in other cases): if you prefer maintaining
libsnappy-java in Debian Java team I'd happily move the packaging into
your Git repository.

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: Debian bugs #762850, #762853

[Debian Bug Tracking System]

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

> fixed 762850 argyll/1.6.3-2
Bug #762850 [argyll] Please demote argyll-doc dependency to recommends or 
suggests
The source argyll and version 1.6.3-2 do not appear to match any binary packages
Marked as fixed in versions argyll/1.6.3-2.
> fixed 762853 argyll/1.6.3-2
Bug #762853 [argyll] Package is missing copyright file
The source argyll and version 1.6.3-2 do not appear to match any binary packages
Marked as fixed in versions argyll/1.6.3-2.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
762850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762850
762853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762853
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: severity of 762705 is important

[Debian Bug Tracking System]

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

> severity 762705 important
Bug #762705 [libdevmapper1.02.1] kpartx: relocation error: kpartx: symbol 
dm_task_get_info_with_deferred_remove, version Base not defined in file 
libdevmapper.so.1.02.1 with link time reference
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762705
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#762838: Bug#735190: Please back this out NOW

[Nigel Horne]

On 25/09/2014 12:31, Salvatore Bonaccorso wrote:

Hi Nigel,

On Thu, Sep 25, 2014 at 12:05:10PM -0400, Nigel Horne wrote:

On 25/09/2014 11:56, Salvatore Bonaccorso wrote:

Hi Nigel,

On Thu, Sep 25, 2014 at 09:29:58AM -0400, Nigel Horne wrote:

Since updating with this, bind stays up no more than 5 minutes before
crashing.  Please fix urgently.

Can you clarify from which version to which other version you have
updated bind9 packages? Can you confirm the problem dissapear if you
downgrade the packages?

The version is now   1:9.9.5.dfsg-4.1 .  I updated today from what ever the
previous version was.  I looked in dpkg.log, but did doesn't say (or I
couldn't work out from it) what the previous version was, but I always keep
it up to date so it will have been whatever the previous released version
was.

Which version would be best to downgrade to?

Thanks for the additional information provided.

Ok, from the version number, it seems you are not running stable, and
are on unstable. If you downgrade back to 1:9.9.5.dfsg-4 dissapear?
This sounds like #762838

If so, could you follow up there? #735190 was about "CVE-2014-0591: A
Crafted Query Against an NSEC3-signed Zone Can Crash BIND".


I downgraded, it it's now been running for an hour or so without 
crashing.  The command I ran was:


 aptitude install bind9=1:9.9.5.dfsg-4

-Nigel



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#762863: when using systemd laptop-mode-tools causes read-only root and system is unusable

[Gianluigi Tiesi]

Package: laptop-mode-tools
Severity: serious

Hi,
if I use systemd and I'm on battery, my system starts with
a read only root and half of the services are not working.

If I uninstall the package, the system boots normally.

removing /usr/sbin/laptop-mode-tools executable
makes udev wait for 3 minutes, I see a red ascii art
animation and this message:
A start job is running for udev for Complete...

looks like it has something to do with the init script


Regards


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

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

Versions of packages laptop-mode-tools depends on:
ii  lsb-base4.1+Debian13
ii  psmisc  22.21-2
ii  util-linux  2.20.1-5.8

Versions of packages laptop-mode-tools recommends:
pn  ethtool 
pn  hdparm  
ii  net-tools   1.60-26
pn  python-qt4  
pn  sdparm  
pn  udev
pn  wireless-tools  

Versions of packages laptop-mode-tools suggests:
pn  acpid | apmd | pbbuttonsd | pmud  
pn  hal   
ii  python2.7.8-1


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

Bug#759084: londonlaw: Please update to use wxpython3.0

[Juhani Numminen]

Hi Olly,

I just noticed that
your NMU patch doesn’t seem to change the python-wxgtk2.8 dependency of
the binary package.


Cheers,
Juhani


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

Bug#761355: closed by Mathieu Malaterre ()

[Ralf Treinen]

Hello,

thanks for having investigated that.

On Wed, Sep 24, 2014 at 06:31:04PM +0800, Kan-Ru Chen (陳侃如) wrote:
> Ralf Treinen  writes:
> 
> > On Mon, Sep 15, 2014 at 07:18:12AM +, Debian Bug Tracking System wrote:
> >
> >> Date: Mon, 15 Sep 2014 09:15:46 +0200
> >> From: Mathieu Malaterre 
> >> To: 761355-d...@bugs.debian.org
> >> Subject: 
> >> 
> >> Control: tags -1 wontfix
> >> 
> >> libopenjpeg6-dev never reached testing. closing as wontfix.
> >
> > That is not a reason to close a bug while it remains unfixed. Policy
> > applies to sid as well as to testing or stable. The same holds
> > of course for #761356 and #761357.
> 
> It looks like libopenjpeg6 doesn't exist anymore. It is still in the
> archive but the source package (openjpeg2) only builds libopenjp2-7. The
> only rdepends of libopenjpeg6 is leptonlib which still build-depends on
> libopenjpeg6-dev. leptonlib could be simply rebuilt against
> libopenjp2-7-dev.

OK. In that case one should simply reassign the bug reports to
the packages coming from the old version of openjpeg2 (I just 
did that).

> I think after leptonlib is fixed we should RM libopenjpe6 and friends
> then mark these bugs as fixed.

No need to do that, the binary packages that are no longer generated
from the source package will be removed automatically when noone 
depends on them any longer.

I guess this also means that #762684 can be closed ?

Cheers -Ralf.


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

Bug#759970: marked as done (libebook-tools-perl: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 14:28:15 -0400
with message-id <20140925182815.ga23...@calvin1.nccs.nasa.gov>
and subject line Fixed in 0.5.0-1
has caused the Debian Bug report #759970,
regarding libebook-tools-perl: FTBFS: tests failed
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.)


-- 
759970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libebook-tools-perl
Version: 0.4.9-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> /usr/bin/perl Build --makefile_env_macros 1 test
> Module::Build will be removed from the Perl core distribution in the next 
> major release. Please install the separate libmodule-build-perl package. It 
> is being used at Build, line 40.
> t/00-errorhandling.t ... ok
> 
> not well-formed (invalid token) at line 24, column 25, byte 1230 at 
> /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
>  at /«PKGBUILDDIR»/blib/lib/EBook/Tools.pm line 672.
> # Looks like you planned 79 tests but ran 7.
> # Looks like your test exited with 255 just after 7.
> t/01-init_and_accessors.t .. 
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 72/79 subtests 
> t/02-fix_methods.t . ok
> t/10-fix_datestring.t .. ok
> t/15-misc_procedures.t . ok
> Wide character in print at /usr/share/perl5/XML/Twig.pm line 8331.
> 
> not well-formed (invalid token) at line 13, column 27, byte 689 at 
> /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
>  at /«PKGBUILDDIR»/blib/lib/EBook/Tools.pm line 672.
> # Looks like you planned 48 tests but ran 43.
> # Looks like your test exited with 255 just after 43.
> t/20-unpack.t .. 
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 5/48 subtests 
> t/21-mobi_languages.t .. ok
> EBook::Tools::IMP::image(): no image type specified!
>  at t/25-imp.t line 54.
> EBook::Tools::IMP::image(): ID not specified!
>  at t/25-imp.t line 55.
> t/25-imp.t . ok
> t/40-lzss.t  ok
> t/50-user_scripts.t  skipped: Automated testing often breaks on 
> actual scripts.
> t/98-pod.t . skipped: Test::Pod 1.00 required for testing POD
> t/99-pod_coverage.t  skipped: Test::Pod::Coverage 1.00 required for 
> testing POD coverage
> 
> Test Summary Report
> ---
> t/01-init_and_accessors.t (Wstat: 65280 Tests: 7 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 79 tests but ran 7.
> t/20-unpack.t(Wstat: 65280 Tests: 43 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 48 tests but ran 43.
> Files=12, Tests=378,  4 wallclock secs ( 0.09 usr  0.10 sys +  3.39 cusr  
> 0.68 csys =  4.26 CPU)
> Result: FAIL
> Failed 2/12 test programs. 0/378 subtests failed.
> make[1]: *** [test] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/libebook-tools-perl_0.4.9-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.
--- End Message ---
--- Begin Message ---
This particular problem is fixed as of 0.5.0-1, but that version also
has an incorrect dependency listing, so 0.5.1-1 will be coming today
as well.--- End Message ---

Bug#762860: [dfc] dfc: "Error while stating /run/user/1000/gvfs : No such file or directory"

[Thomas Kreft]

Package: dfc
Version: 2.5.0-1
Severity: grave

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

Dear Maintainer,

dfc stopped working. I didn't use it for a while, so I can't be more specific.

Running as a user or as root only prints:

"Error while stating /run/user/1000/gvfs : No such file or directory"

Although not a dependency, the package gvfs is installed:

$ apt-cache policy gvfs
gvfs:
  Installiert:   1.22.0-1
  Installationskandidat: 1.22.0-1
  Versionstabelle:
 *** 1.22.0-1 0
   1000 http://ftp.de.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status

...but a file called gvfs nowhere to be found in /run/user.

Please let me know if you need more information and how to provide it.



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

Debian Release: jessie/sid
 1000 unstableftp.de.debian.org 
1 experimentalftp.de.debian.org 

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


Package's Recommends field is empty.

Package's Suggests field is empty.


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

Processed: reassign 761355 to libopenjpeg6-dev

[Debian Bug Tracking System]

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

> reassign 761355 libopenjpeg6-dev
Bug #761355 [libopenjpeg6-dev] libopenjpeg6-dev and libopenjp2-7-dev: error 
when trying to install together
Ignoring request to reassign bug #761355 to the same package
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761355
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: found 761355 in libopenjpeg6-dev/2.0.0-1

[Debian Bug Tracking System]

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

> found 761355 libopenjpeg6-dev/2.0.0-1
Bug #761355 [libopenjpeg6-dev] libopenjpeg6-dev and libopenjp2-7-dev: error 
when trying to install together
The source libopenjpeg6-dev and version 2.0.0-1 do not appear to match any 
binary packages
Marked as found in versions libopenjpeg6-dev/2.0.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761355
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: found 761357 in openjp3d-tools/2.0.0-1

[Debian Bug Tracking System]

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

> found 761357 openjp3d-tools/2.0.0-1
Bug #761357 [openjp3d-tools] openjp3d-tools and libopenjp3d-tools: error when 
trying to install together
The source openjp3d-tools and version 2.0.0-1 do not appear to match any binary 
packages
Marked as found in versions openjp3d-tools/2.0.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761357
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: reassign 761356 to openjpeg-tools

[Debian Bug Tracking System]

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

> reassign 761356 openjpeg-tools
Bug #761356 [openjpeg-tools] openjpeg-tools and libopenjp2-tools: error when 
trying to install together
Ignoring request to reassign bug #761356 to the same package
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761356
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: found 761356 in openjpeg-tools/2.0.0-1

[Debian Bug Tracking System]

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

> found 761356 openjpeg-tools/2.0.0-1
Bug #761356 [openjpeg-tools] openjpeg-tools and libopenjp2-tools: error when 
trying to install together
The source openjpeg-tools and version 2.0.0-1 do not appear to match any binary 
packages
Marked as found in versions openjpeg-tools/2.0.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761356
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: reassign 761357 to openjp3d-tools

[Debian Bug Tracking System]

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

> reassign 761357 openjp3d-tools
Bug #761357 [openjp3d-tools] openjp3d-tools and libopenjp3d-tools: error when 
trying to install together
Ignoring request to reassign bug #761357 to the same package
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761357
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#762838: bug#762838 -- bind9 crash on update

[Al Stone]

Just upgraded to this version from one about 1 month old from sid
and see the same problem; named will run for a few minutes, and then
the messages shown appear in syslog.  There were no changes to any
of the BIND config files.

The 9.10.0 version in experimental seems to be more stable.

--
Ciao,
al
--
Al Stone Debian Developer
E-mail: a...@debian.org  http://www.debian.org
--


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

Bug#757280: marked as done (bino: FTBFS: gettext infrastructure mismatch)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 17:03:45 +
with message-id 
and subject line Bug#757280: fixed in bino 1.6.0-1
has caused the Debian Bug report #757280,
regarding bino: FTBFS: gettext infrastructure mismatch
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.)


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

Source: bino
Version: 1.4.4-2
Severity: serious
Justification: fails to build from source
Tags: patch

Dear Maintainer,

bino fails to build in a current sid/amd64 chroot:
Making all in po
make[3]: Entering directory '/tmp/buildd/bino-1.4.4/po'
*** error: gettext infrastructure mismatch: using a Makefile.in.in from 
gettext version 0.18 but the autoconf macros are from gettext version 0.19


The reason for this is that the current gettext in sid is newer than the 
version that was used to create the Makefile.in.in.


To resolve this, I ran 'gettextize -f' in the source directory and 
updated po/Makevars as advised by gettextize.


This resulted in the attached patch, which fixes this problem.

Best regards,
Andreas
diff --git a/debian/patches/gettextize-0.19.patch b/debian/patches/gettextize-0.19.patch
new file mode 100644
index 000..77c0381
--- /dev/null
+++ b/debian/patches/gettextize-0.19.patch
@@ -0,0 +1,2890 @@
+Description: Update for gettext 0.19
+ Run gettexttize to update for gettext 0.19.
+ Also update po/Makevars as advised by gettextize.
+
+Author: Andreas Cadhalpun 
+Last-Update: <2014-08-06>
+
+--- bino-1.4.4.orig/Makefile.am
 bino-1.4.4/Makefile.am
+@@ -8,7 +8,7 @@
+ 
+ SUBDIRS = po src doc
+ 
+-EXTRA_DIST = README.Linux README.FreeBSD README.MacOSX README.Windows
++EXTRA_DIST = m4/ChangeLog  README.Linux README.FreeBSD README.MacOSX README.Windows
+ 
+ # Create the ChangeLog file from the git log
+ dist-hook:
+--- bino-1.4.4.orig/build-aux/config.rpath
 bino-1.4.4/build-aux/config.rpath
+@@ -2,7 +2,7 @@
+ # Output a system dependent set of variables, describing how to set the
+ # run time search path of shared libraries in an executable.
+ #
+-#   Copyright 1996-2010 Free Software Foundation, Inc.
++#   Copyright 1996-2014 Free Software Foundation, Inc.
+ #   Taken from GNU libtool, 2001
+ #   Originally by Gordon Matzigkeit , 1996
+ #
+@@ -25,7 +25,7 @@
+ #   known workaround is to choose shorter directory names for the build
+ #   directory and/or the installation directory.
+ 
+-# All known linkers require a `.a' archive for static linking (except MSVC,
++# All known linkers require a '.a' archive for static linking (except MSVC,
+ # which needs '.lib').
+ libext=a
+ shrext=.so
+@@ -57,13 +57,6 @@ else
+ aix*)
+   wl='-Wl,'
+   ;;
+-darwin*)
+-  case $cc_basename in
+-xlc*)
+-  wl='-Wl,'
+-  ;;
+-  esac
+-  ;;
+ mingw* | cygwin* | pw32* | os2* | cegcc*)
+   ;;
+ hpux9* | hpux10* | hpux11*)
+@@ -72,9 +65,7 @@ else
+ irix5* | irix6* | nonstopux*)
+   wl='-Wl,'
+   ;;
+-newsos6)
+-  ;;
+-linux* | k*bsd*-gnu)
++linux* | k*bsd*-gnu | kopensolaris*-gnu)
+   case $cc_basename in
+ ecc*)
+   wl='-Wl,'
+@@ -85,17 +76,26 @@ else
+ lf95*)
+   wl='-Wl,'
+   ;;
+-pgcc | pgf77 | pgf90)
++nagfor*)
++  wl='-Wl,-Wl,,'
++  ;;
++pgcc* | pgf77* | pgf90* | pgf95* | pgfortran*)
+   wl='-Wl,'
+   ;;
+ ccc*)
+   wl='-Wl,'
+   ;;
++xl* | bgxl* | bgf* | mpixl*)
++  wl='-Wl,'
++  ;;
+ como)
+   wl='-lopt='
+   ;;
+ *)
+   case `$CC -V 2>&1 | sed 5q` in
++*Sun\ F* | *Sun*Fortran*)
++  wl=
++  ;;
+ *Sun\ C*)
+   wl='-Wl,'
+   ;;
+@@ -103,13 +103,24 @@ else
+   ;;
+   esac
+   ;;
++newsos6)
++  ;;
++*nto* | *qnx*)
++  ;;
+ osf3* | osf4* | osf5*)
+   wl='-Wl,'
+   ;;
+ rdos*)
+   ;;
+ solaris*)
+-  wl='-Wl,'
++  case $cc_basename in
++f77* | f90* | f95* | sunf77* | sunf90* | sunf95*)
++  wl='-Qoption ld '
++  ;;
++*)
++  wl='-Wl,'
++  ;;
++  esac
+   ;;
+ sunos4*)
+   wl='-Qoption ld '
+@@ -171,15 +182,14 @@ if test "$with_gnu_ld" = yes; then
+   fi
+   ;;
+ amigaos*)
+-  hardcode_libdir_flag_spec='-L$libdir'
+-  hardcode_minus_L=yes
+-  # Samuel A. Falvo II  reports
+-  # that the semantics of dynamic libraries on Am

Bug#745995: dico FTBFS on mips/mipsel -- RFH

[أحمد المحمودي]

On Thu, Sep 25, 2014 at 02:51:42PM +, James Cowgill wrote:
> I've had a small look at this (I don't have much at the moment).
> 
> When you run your example with LD_DEBUG=libs, you get the error:
>  /usr/lib/mips-linux-gnu/libgc.so.1: error: symbol lookup error: undefined 
> symbol: __data_start (fatal)
> 
> The Boehm GC headers (on some arches) indicate that the calling program
> is expected to define __data_start somewhere (presumably by gcc) and
> this isn't happening.
---end quoted text---

  I'd like to note the following:

  * dico 2.2-5 does build on mips/mipsel, this revision builds against 
guile 1.8 not guile 2.0

  * I unpacked the mips arch. of the following packages under the same 
directory: guile-2.0-libs, guile-1.8-libs, dico-module-guile (2.2-5)

Then I ran: grep -r __data_start /path/to/extracted_pkgs/ , the only 
match was: ./usr/lib/mips-linux-gnu/guile-2.0/bin/guile

I grep'ed the guile.so module produced by dico 2.2-6 amd64 build (I 
don't have access to a mips machine) for __data-start, but no match 
was found.

  * I realize that guile-2.0-libs installs 'guile' binary under a 
multiarch dir on mips (/usr/lib/mips-linux-gnu/guile-2.0/bin/guile), 
yet on amd64 it is installed in (/usr/lib/guile-2.0/bin/guile). 
Don't know if that does matter or not.

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: Digital signature

Bug#762853: Package is missing copyright file

[Michael Biebl]

Package: argyll
Version: 1.6.3-1
Severity: serious

The /usr/share/doc/argyll directory is completely empty

# ls -al /usr/share/doc/argyll/
total 8
drwxr-xr-x   2 root root 4096 Sep 25 16:54 .
drwxr-xr-x 151 root root 4096 Sep 25 16:54 ..


Looks like the dir-to-symlink migration is messed up.

My suggestion would be, to *not* use symlinked doc directories. They
cause more trouble then they are worth it.
Especially, since then you can drop the argyll->argyll-doc dependency.

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

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

Versions of packages argyll depends on:
ii  libc6 2.19-11
ii  libicc2   2.12+argyll1.5.1-8
ii  libimdi0  1.5.1-8
ii  libjpeg8  8d1-1
ii  libtiff5  4.0.3-10
ii  libusb-0.1-4  2:0.1.12-24
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.2-1
ii  libxinerama1  2:1.1.3-1
ii  libxrandr22:1.4.2-1
ii  libxss1   1:1.2.2-1
ii  libxxf86vm1   1:1.1.3-1

Versions of packages argyll recommends:
ii  libpam-systemd  215-4
ii  udev215-4

Versions of packages argyll suggests:
ii  colord1.2.1-1
pn  gir1.2-colordgtk-1.0  

-- 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#762852: libprocps4-dev: broken symlink /usr/lib/i386-linux-gnu/libprocps.so

[Sven Joachim]

Package: libprocps4-dev
Version: 1:3.3.10-1
Severity: serious

Packages linking with -lprocps are going to be linked statically or
depend on libprocps3 instead of libprocps4, depending on whether the
latter is installed in the build environment:

,
| $ file /usr/lib/i386-linux-gnu/libprocps.so
| /usr/lib/i386-linux-gnu/libprocps.so: broken symbolic link to 
`/lib/i386-linux-gnu/libprocps.so.3'
`


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.3-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libprocps4-dev depends on:
ii  libprocps4  1:3.3.10-1

libprocps4-dev recommends no packages.

libprocps4-dev 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#762520: Bug report about the package clearlooks-phenix-theme 5.0.2-1 (unstable)

[Andrew Shadura]

Hello,

On 25 September 2014 17:29, Etienne MAHE  wrote:
> Justification: bad graphical integration with apps based on adwaïta theme.

> On some apps based on Adwaïta theme and built on the gtk3 architecture like
> Synaptic or evince, the clearlooks phenix theme let to appear ugly boxes in
> the menu of the app, and that are not well integrated with the graphical
> window. This bug seems to appear since the new version of this theme. So I
> am waiting for any fixes and meanwhile, I am using the clearlooks theme
> built on gtk2. If we could delete these boxes and get an interface like in
> the previous version, it would be great.

If you run GTK+ 3.14 (Debian unstable), this is a known issue. GTK+
broke the compatibility again, and Jean-Philippe (the upstream author)
is aware of that. Unfortunately, he doesn't have 3.14 yet, so he's not
very enthusiastic about updating the theme.

However, the freeze is Real Soon Now, in November, and we should
probably fix this until the end of October. I'll try to do something
with it myself, but I can't guarantee anything, as theming engine
seems to have changed significantly.

-- 
Cheers,
  Andrew


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

Bug#762307: grub2: FTBFS on mipsel: objcopy:none_decompress.img[.text]: File truncated

[Colin Watson]

On Thu, Sep 25, 2014 at 03:52:52PM +, Jurica Stanojkovic wrote:
> --- grub2-2.02~beta2.orig/gentpl.py
> +++ grub2-2.02~beta2/gentpl.py
> @@ -753,7 +753,11 @@ def image(defn, platform):
>  if test x$(TARGET_APPLE_LINKER) = x1; then \
>$(MACHO2IMG) $< $@; \
>  else \
> -  $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) --strip-unneeded 
> -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R 
> .note.gnu.gold-version $< $@; \
> +  case "$(target_cpu)"-"$(target_vendor)" in \
> +mipsel-*) $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) 
> --strip-unneeded -R .MIPS.abiflags -R .note -R .comment -R .note.gnu.build-id 
> -R .reginfo -R .rel.dyn -R .note.gnu.gold-version $< $@; ;; \
> +mips-*) $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) 
> --strip-unneeded -R .MIPS.abiflags -R .note -R .comment -R .note.gnu.build-id 
> -R .reginfo -R .rel.dyn -R .note.gnu.gold-version $< $@; ;; \
> +*) $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) 
> --strip-unneeded -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R 
> .rel.dyn -R .note.gnu.gold-version $< $@; ;; \
> +  esac \
>  fi
>  """)
>  

I think we could just remove that section on all architectures; there
doesn't seem any particular reason to make the code more complex in
order to do it just on mips*.

-- 
Colin Watson   [cjwat...@debian.org]


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

Bug#729062: marked as done (longomatch must depend on gstreamer0.10-plugins-good and gstreamer0.10-x)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 16:33:55 +
with message-id 
and subject line Bug#729062: fixed in longomatch 0.16.8+git20110626-2
has caused the Debian Bug report #729062,
regarding longomatch must depend on gstreamer0.10-plugins-good and 
gstreamer0.10-x
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.)


-- 
729062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: longomatch
Version: 0.16.8+git20110626-1+b2
Severity: serious

longomatch doesn't even start unless both gstreamer0.10-plugins-good
and gstreamer0.10-x are installed.

See https://bugzilla.gnome.org/show_bug.cgi?id=711671 for my report
that the error handling is also broken - and one wouldn't run into
the broken error handling in the first place if the dependencies
would ensure that all needed packages are installed.
--- End Message ---
--- Begin Message ---
Source: longomatch
Source-Version: 0.16.8+git20110626-2

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

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 729...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated longomatch 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 25 Sep 2014 17:15:35 +0100
Source: longomatch
Binary: longomatch
Architecture: source amd64
Version: 0.16.8+git20110626-2
Distribution: unstable
Urgency: medium
Maintainer: Debian CLI Applications Team 

Changed-By: Jo Shields 
Description:
 longomatch - video analysis tool for coaches
Closes: 729062
Changes:
 longomatch (0.16.8+git20110626-2) unstable; urgency=medium
 .
   * [9f9f03c] Depend on both gstreamer0.10-plugins-good and
 gstreamer0.10-x (Closes: #729062)
Checksums-Sha1:
 8d506dbf741c0a6ca9edd10cd3b9778ecc6df247 1926 
longomatch_0.16.8+git20110626-2.dsc
 4b273a1441ccf7a1885d156a7f19097b9a38baf6 7728 
longomatch_0.16.8+git20110626-2.debian.tar.xz
 c97216a4850c2c4089ab60f568aaa8593ccee72b 402620 
longomatch_0.16.8+git20110626-2_amd64.deb
Checksums-Sha256:
 9c25025f57e2b42319817fa461f4e8d54b045ab851506eba1a6355deb652716a 1926 
longomatch_0.16.8+git20110626-2.dsc
 44214b522912d5a2bf890a9f91a4c81532a7089ab057cfc5f74c8bd090c80622 7728 
longomatch_0.16.8+git20110626-2.debian.tar.xz
 5f4f282a9d9859049a63b36ad8b8611ac24b753d1f215f3b47fc867b47ea4395 402620 
longomatch_0.16.8+git20110626-2_amd64.deb
Files:
 9c7a0ec32bf98609f8cb6be2b803efe3 402620 graphics optional 
longomatch_0.16.8+git20110626-2_amd64.deb
 93cf0670b299ae86758cf10ef7224d80 1926 graphics optional 
longomatch_0.16.8+git20110626-2.dsc
 b498b99ad5b6f9de550f94931da4dbef 7728 graphics optional 
longomatch_0.16.8+git20110626-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUJEAsAAoJEMkPnLkOH60MRW0IAL2Q2sTlWa0Dt+2qfJCafaPS
V0/3VDA069NzzjrnCNA6JfHmefZp4A6IRaq/58e8u1/RzhsTDfhTotIan9Z5v8e6
7PkI2g5jX0W/bCRtbsnPM8EkQ836QWZ9HHovzoyOox6vsg9md9grwPU+QfrM6xLi
8nHl9Dh1lOe9Dl31gFaZYjQM22VyF+PLu2UL87nFWcmvkXevAWXUYPoeCRExKnCC
L0ivVjLIeNaVTRY6cEdezC+DGYUTTfIiqfsj95KtnCllmhGB5U7/GII4yqUE3mNv
gTkQLQmq2I11yb16O2D7O+zcNNd2bnP4fCFdfAimHg1QxF+4v6Juss3cJDsMXxc=
=uY7o
-END PGP SIGNATURE End Message ---

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 738501 mono-devel
Bug #738501 [src:nunit] nunit: Frequently FTBFS
Bug reassigned from package 'src:nunit' to 'mono-devel'.
No longer marked as found in versions nunit/2.6.0.12051+dfsg-2.
Ignoring request to alter fixed versions of bug #738501 to the same values 
previously set
> retitle 738501 "resgen frequently crashes on NUnit source"
Bug #738501 [mono-devel] nunit: Frequently FTBFS
Changed Bug title to '"resgen frequently crashes on NUnit source"' from 'nunit: 
Frequently FTBFS'
> found 738501 3.0.6+dfsg2-12
Bug #738501 [mono-devel] "resgen frequently crashes on NUnit source"
Marked as found in versions mono/3.0.6+dfsg2-12.
> severity 738501 normal
Bug #738501 [mono-devel] "resgen frequently crashes on NUnit source"
Severity set to 'normal' from 'serious'
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
738501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738501
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#735190: Please back this out NOW

[Salvatore Bonaccorso]

Hi Nigel,

On Thu, Sep 25, 2014 at 12:05:10PM -0400, Nigel Horne wrote:
> On 25/09/2014 11:56, Salvatore Bonaccorso wrote:
> >Hi Nigel,
> >
> >On Thu, Sep 25, 2014 at 09:29:58AM -0400, Nigel Horne wrote:
> >>Since updating with this, bind stays up no more than 5 minutes before
> >>crashing.  Please fix urgently.
> >Can you clarify from which version to which other version you have
> >updated bind9 packages? Can you confirm the problem dissapear if you
> >downgrade the packages?
> 
> The version is now   1:9.9.5.dfsg-4.1 .  I updated today from what ever the
> previous version was.  I looked in dpkg.log, but did doesn't say (or I
> couldn't work out from it) what the previous version was, but I always keep
> it up to date so it will have been whatever the previous released version
> was.
> 
> Which version would be best to downgrade to?

Thanks for the additional information provided. 

Ok, from the version number, it seems you are not running stable, and
are on unstable. If you downgrade back to 1:9.9.5.dfsg-4 dissapear?
This sounds like #762838

If so, could you follow up there? #735190 was about "CVE-2014-0591: A
Crafted Query Against an NSEC3-signed Zone Can Crash BIND".

Regards,
Salvatore


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

Bug#759901: marked as done (banshee-community-extensions: FTBFS: build-dependency not installable: libtaoframework-sdl-cil-dev (>= 1.2.13))

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 17:13:39 +0100
with message-id <54243f33.4040...@apebox.org>
and subject line 
has caused the Debian Bug report #759901,
regarding banshee-community-extensions: FTBFS: build-dependency not 
installable: libtaoframework-sdl-cil-dev (>= 1.2.13)
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.)


-- 
759901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: banshee-community-extensions
Version: 2.4.0-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ┌──┐
> │ Install banshee-community-extensions 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-banshee-community-extensions-dummy : Depends: 
> libtaoframework-sdl-cil-dev (>= 1.2.13) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/banshee-community-extensions_2.4.0-4_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.
--- End Message ---
--- Begin Message ---

reassign 759901 libtaoframework-sdl-cil-dev 2.1.svn20090801-9
fixed 759901 2.1.svn20090801-10--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 759901 libtaoframework-sdl-cil-dev 2.1.svn20090801-9
Bug #759901 [src:banshee-community-extensions] banshee-community-extensions: 
FTBFS: build-dependency not installable: libtaoframework-sdl-cil-dev (>= 1.2.13)
Bug reassigned from package 'src:banshee-community-extensions' to 
'libtaoframework-sdl-cil-dev'.
No longer marked as found in versions banshee-community-extensions/2.4.0-4.
Ignoring request to alter fixed versions of bug #759901 to the same values 
previously set
Bug #759901 [libtaoframework-sdl-cil-dev] banshee-community-extensions: FTBFS: 
build-dependency not installable: libtaoframework-sdl-cil-dev (>= 1.2.13)
Marked as found in versions taoframework/2.1.svn20090801-9.
> fixed 759901 2.1.svn20090801-10
Bug #759901 [libtaoframework-sdl-cil-dev] banshee-community-extensions: FTBFS: 
build-dependency not installable: libtaoframework-sdl-cil-dev (>= 1.2.13)
Marked as fixed in versions taoframework/2.1.svn20090801-10.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
759901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759901
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#735190: Please back this out NOW

[Nigel Horne]

On 25/09/2014 11:56, Salvatore Bonaccorso wrote:

Hi Nigel,

On Thu, Sep 25, 2014 at 09:29:58AM -0400, Nigel Horne wrote:

Since updating with this, bind stays up no more than 5 minutes before
crashing.  Please fix urgently.

Can you clarify from which version to which other version you have
updated bind9 packages? Can you confirm the problem dissapear if you
downgrade the packages?


The version is now   1:9.9.5.dfsg-4.1 .  I updated today from what ever 
the previous version was.  I looked in dpkg.log, but did doesn't say (or 
I couldn't work out from it) what the previous version was, but I always 
keep it up to date so it will have been whatever the previous released 
version was.


Which version would be best to downgrade to?


Regards,
Salvatore

Regards,

-Nigel



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#735190: Please back this out NOW

[Salvatore Bonaccorso]

Hi Nigel,

On Thu, Sep 25, 2014 at 09:29:58AM -0400, Nigel Horne wrote:
> Since updating with this, bind stays up no more than 5 minutes before
> crashing.  Please fix urgently.

Can you clarify from which version to which other version you have
updated bind9 packages? Can you confirm the problem dissapear if you
downgrade the packages?

Regards,
Salvatore


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

Bug#762307: grub2: FTBFS on mipsel: objcopy:none_decompress.img[.text]: File truncated

[Jurica Stanojkovic]

Control: tags -1 + patch

Hello,

I have tried to build package on mipsel
with change that  Colin Watson has suggested ("-R .MIPS.abiflags").

With that change package does build successfully on mipsel.
Patch resolving this issue is attached.

Regards,
Jurica
--- grub2-2.02~beta2.orig/gentpl.py
+++ grub2-2.02~beta2/gentpl.py
@@ -753,7 +753,11 @@ def image(defn, platform):
 if test x$(TARGET_APPLE_LINKER) = x1; then \
   $(MACHO2IMG) $< $@; \
 else \
-  $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) --strip-unneeded -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R .note.gnu.gold-version $< $@; \
+  case "$(target_cpu)"-"$(target_vendor)" in \
+mipsel-*) $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) --strip-unneeded -R .MIPS.abiflags -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R .note.gnu.gold-version $< $@; ;; \
+mips-*) $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) --strip-unneeded -R .MIPS.abiflags -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R .note.gnu.gold-version $< $@; ;; \
+*) $(TARGET_OBJCOPY) $(""" + cname(defn) + """_OBJCOPYFLAGS) --strip-unneeded -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R .note.gnu.gold-version $< $@; ;; \
+  esac \
 fi
 """)
 

Processed: Re: grub2: FTBFS on mipsel: objcopy:none_decompress.img[.text]: File truncated

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #762307 [src:grub2] grub2: FTBFS on mipsel: 
objcopy:none_decompress.img[.text]: File truncated
Added tag(s) patch.

-- 
762307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762307
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#762520: Bug report about the package clearlooks-phenix-theme 5.0.2-1 (unstable)

[Etienne MAHE]

Package: clearlooks-phenix-theme
Version: 5.0.2-1
Severity: normal
Justification: bad graphical integration with apps based on adwaïta theme.

Good day,

On some apps based on Adwaïta theme and built on the gtk3 architecture
like Synaptic or evince, the clearlooks phenix theme let to appear
ugly boxes in the menu of the app, and that are not well integrated
with the graphical window. This bug seems to appear since the new
version of this theme. So I am waiting for any fixes and meanwhile, I
am using the clearlooks theme built on gtk2. If we could delete these
boxes and get an interface like in the previous version, it would be
great.

I hope I have been understood despite of my approximate english.
,
Kind regards,
Etienne.

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

Processed: severity of 762837 is serious

[Debian Bug Tracking System]

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

> severity 762837 serious
Bug #762837 [nemo] nemo: cp: cannot stat 
'debian/tmp/usr/lib/girepository-1.0/Nemo-3.0.typelib': No such file or 
directory
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762837
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#762838: [bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace”

[Valentin Lorentz]

Package: bind9
Version: 1:9.9.5.dfsg-4.1
Severity: grave

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

Hello,

Since last update, my bind server crashes after a few requests (maybe
when it gets too many at the same time), for instance when I start
Firefox (with some tabs)
Downgrading to the version in testing fixes the issue ( 1:9.9.5.dfsg-4).

The error log I get is:

25-Sep-2014 14:41:51.464 general: critical: mem.c:1321: REQUIRE(ptr != ((void 
*)0)) failed, back trace
25-Sep-2014 14:41:51.464 general: critical: #0 0x7fd288a3b22d in ??
25-Sep-2014 14:41:51.464 general: critical: #1 0x7fd286c287ba in ??
25-Sep-2014 14:41:51.464 general: critical: #2 0x7fd286c3902c in ??
25-Sep-2014 14:41:51.465 general: critical: #3 0x7fd2882ea694 in ??
25-Sep-2014 14:41:51.465 general: critical: #4 0x7fd28829616a in ??
25-Sep-2014 14:41:51.465 general: critical: #5 0x7fd28827dc29 in ??
25-Sep-2014 14:41:51.465 general: critical: #6 0x7fd28827dd99 in ??
25-Sep-2014 14:41:51.465 general: critical: #7 0x7fd2882f17fd in ??
25-Sep-2014 14:41:51.465 general: critical: #8 0x7fd2882ffbf0 in ??
25-Sep-2014 14:41:51.465 general: critical: #9 0x7fd286c49eeb in ??
25-Sep-2014 14:41:51.465 general: critical: #10 0x7fd2865fb0a4 in ??
25-Sep-2014 14:41:51.465 general: critical: #11 0x7fd285fcbc2d in ??
25-Sep-2014 14:41:51.465 general: critical: exiting (due to assertion failure)

I do not know how to install debugging symbols for bind, could you tell
me how if you need them?

Regards,
Valentin

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



signature.asc
Description: OpenPGP digital signature

Processed: severity of 762834 is serious

[Debian Bug Tracking System]

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

> severity 762834 serious
Bug #762834 [mate-panel] mate-panel: FTBFS: cp: cannot stat 
'debian/tmp/usr/lib/girepository-1.0/': No such file or directory
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762834
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#746141: pacemaker: FTBFS: configure: error: Unable to support SNMP

[Jonathan Wiltshire]

notfound 746141 1.1.10+git20130802-4
close 746141
thanks

On Sun, 27 Apr 2014 13:59:17 +0200 David =?iso-8859-1?Q?Su=E1rez?=
 wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

I wasn't able to reproduce this in a clean, up-to-date amd64 chroot. It
must have been something transient.

-- 
Jonathan Wiltshire
Tiger Computing Ltd
"Linux for Business"

Tel: 01600 483 484
Web: http://www.tiger-computing.co.uk
Follow us on Facebook: http://www.facebook.com/TigerComputing

Registered in England. Company number: 3389961
Registered address: Wyastone Business Park,
 Wyastone Leys, Monmouth, NP25 3SR



signature.asc
Description: OpenPGP digital signature

Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed

[Andreas Henriksson]

Hello Lennert Van Alboom!

I suspect that what's being discussed in this bug report is
yet another symptom of the systemd-shim bugs discussed in
#757348 and many more

On Wed, Sep 10, 2014 at 11:06:44AM +0200, Lennert Van Alboom wrote:
> Confirmed on gdm3 3.12.2-4. Any outlook on a fix or workaround that doesn't 
> involve replacing my PID 1 with systemd?

A workaround I've used when testing the xfce4 session with
systemd-shim (which also suffers from systemd-shim not setting up
proper policykit authorities) is to manually write a policykit
configuration snippet to give permissions to a specific group.

eg. to give the sudo group members suspend/hibernate authority do:

sudo cat  cat ./localauthority/50-local.d/org.freedesktop.upower.pkla
[Suspend/hibernate permissions]
Identity=unix-group:sudo
Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.suspend
ResultAny=yes
ResultInactive=yes
ResultActive=yes
EOF

You probably have to adjust this for whatever policykit authority
is needed in this case... (which might be something else then the
logind suspend/hibernate access.)

I would very much suggest that if you're serious about running
something else then the default init system, you step up and help
out solving the issues they have!
Working around them might give you a warm cozy feeling right now
but if you do that the day when these systems gets removed will
be coming closer and closer and be a harsh wakeup for the people
who are still using them (with their accumulated workarounds).

If the above workaround indeed does work (or not) then your
feedback about it (either way) would be welcome here!

Regards,
Andreas Henriksson


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

Bug#762832: fcitx: FTBFS: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0/Fcitx-1.0.typelib': No such file or directory

[Iain Lane]

Package: fcitx
Version: 1:4.2.8.5-1
Severity: serious
Tags: patch pending

Heya,

gobject-introspection in unstable has moved the variable 'typelibdir' to
point to a subdirectory of /usr/lib/$(DEB_HOST_MULTIARCH). Packages
which respect this need to be updated to install files in the new
location, or else they FTBFS. fcitc is in this position.

I've prepared an NMU for fcitx (versioned as 1:4.2.8.5-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer, or to supersede it, or whatever.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
diff -Nru fcitx-4.2.8.5/debian/changelog fcitx-4.2.8.5/debian/changelog
--- fcitx-4.2.8.5/debian/changelog	2014-09-19 22:11:33.0 +0100
+++ fcitx-4.2.8.5/debian/changelog	2014-09-25 15:28:24.0 +0100
@@ -1,3 +1,11 @@
+fcitx (1:4.2.8.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install typelib file in multiarch libdir and mark gir package as M-A:
+same.
+
+ -- Iain Lane   Thu, 25 Sep 2014 15:28:24 +0100
+
 fcitx (1:4.2.8.5-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru fcitx-4.2.8.5/debian/control fcitx-4.2.8.5/debian/control
--- fcitx-4.2.8.5/debian/control	2014-09-19 22:27:19.0 +0100
+++ fcitx-4.2.8.5/debian/control	2014-09-25 15:29:35.0 +0100
@@ -182,6 +182,7 @@
 Suggests: fcitx (>= ${source:Upstream-Version})
 Replaces: fcitx (<< ${source:Upstream-Version})
 Breaks: fcitx (<< ${source:Upstream-Version})
+Multi-Arch: same
 Description: Flexible Input Method Framework - GObject introspection 
  Fcitx is a input method framework with extension support, which provides
  an interface for entering characters of different scripts in applications
diff -Nru fcitx-4.2.8.5/debian/control.in fcitx-4.2.8.5/debian/control.in
--- fcitx-4.2.8.5/debian/control.in	2014-09-19 21:51:15.0 +0100
+++ fcitx-4.2.8.5/debian/control.in	2014-09-25 15:27:05.0 +0100
@@ -182,6 +182,7 @@
 Suggests: fcitx (>= ${source:Upstream-Version})
 Replaces: fcitx (<< ${source:Upstream-Version})
 Breaks: fcitx (<< ${source:Upstream-Version})
+Multi-Arch: same
 Description: Flexible Input Method Framework - GObject introspection 
  Fcitx is a input method framework with extension support, which provides
  an interface for entering characters of different scripts in applications
diff -Nru fcitx-4.2.8.5/debian/gir1.2-fcitx-1.0.install fcitx-4.2.8.5/debian/gir1.2-fcitx-1.0.install
--- fcitx-4.2.8.5/debian/gir1.2-fcitx-1.0.install	2014-09-19 21:51:15.0 +0100
+++ fcitx-4.2.8.5/debian/gir1.2-fcitx-1.0.install	2014-09-25 15:27:32.0 +0100
@@ -1,2 +1,2 @@
-usr/lib/girepository-1.0/Fcitx-1.0.typelib
+usr/lib/*/girepository-1.0/Fcitx-1.0.typelib
 usr/share/gir-1.0/Fcitx-1.0.gir


signature.asc
Description: Digital signature

Bug#736189: [gitit] Sourceless file

[Anthony Towns]

tag 736189 + fixed-upstream
thanks

This bug is reportedly fixed in the new upstream version 0.10.5 about a
month ago:

> I've released gitit 0.10.5.
> 
> CHANGES:
> 
...
>   * Add full versions of minified JavaScript (#400) (Peter Gallagher).

 -- https://groups.google.com/forum/#!topic/gitit-discuss/7t_ew6pw7Ac

Cheers,
aj


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

Processed: Re: Bug#736189: [gitit] Sourceless file

[Debian Bug Tracking System]

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

> tag 736189 + fixed-upstream
Bug #736189 [gitit] [gitit] Sourceless file
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
736189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736189
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#762830: cinnamon-menus: FTBFS: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0': No such file or directory

[Iain Lane]

Package: cinnamon-menus
Version: 2.2.0-2
Severity: serious
Tags: patch pending

Hi guys,

gobject-introspection in unstable has moved the variable 'typelibdir' to
point to a subdirectory of /usr/lib/$(DEB_HOST_MULTIARCH). Packages
which respect this need to be updated to install files in the new
location, or else they FTBFS. cinnamon-menus is in this position.

I've prepared an NMU for cinnamon-menus (versioned as 2.2.0-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I should delay
it longer, or cancel or supersede the upload if you want.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
diff -Nru cinnamon-menus-2.2.0/debian/changelog cinnamon-menus-2.2.0/debian/changelog
--- cinnamon-menus-2.2.0/debian/changelog	2014-07-16 10:30:24.0 +0100
+++ cinnamon-menus-2.2.0/debian/changelog	2014-09-25 15:20:11.0 +0100
@@ -1,3 +1,10 @@
+cinnamon-menus (2.2.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install typelib files in multiarch libdir.
+
+ -- Iain Lane   Thu, 25 Sep 2014 15:20:11 +0100
+
 cinnamon-menus (2.2.0-2) unstable; urgency=medium
 
   * Release to unstable.
diff -Nru cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install
--- cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install	2014-07-16 10:30:24.0 +0100
+++ cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install	2014-09-25 15:16:25.0 +0100
@@ -1 +1 @@
-usr/lib/girepository-1.0
+usr/lib/*/girepository-1.0


signature.asc
Description: Digital signature

Processed: Re: pacemaker: FTBFS: configure: error: Unable to support SNMP

[Debian Bug Tracking System]

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

> notfound 746141 1.1.10+git20130802-4
Bug #746141 [src:pacemaker] pacemaker: FTBFS: configure: error: Unable to 
support SNMP
No longer marked as found in versions pacemaker/1.1.10+git20130802-4.
> close 746141
Bug #746141 [src:pacemaker] pacemaker: FTBFS: configure: error: Unable to 
support SNMP
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
746141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746141
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: jitsi: uninstallable in sid

[Debian Bug Tracking System]

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

> severity 760853 grave
Bug #760853 [jitsi] jitsi is bound/dependant on libavfilter4 instead of 
libavfilter5
Severity set to 'grave' from 'important'
> retitle 760853 jitsi uninstallable in sid
Bug #760853 [jitsi] jitsi is bound/dependant on libavfilter4 instead of 
libavfilter5
Changed Bug title to 'jitsi uninstallable in sid' from 'jitsi is 
bound/dependant on libavfilter4 instead of libavfilter5'
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
760853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
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#753378: josm: not installable in sid

[Christoph Anton Mitterer]

Hi.

Anything going on here...? This is now open for 3 months...


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#762199: zfsutils: zpool import finds nothing

[Steven Chamberlain]

On 14:47, Steven Chamberlain wrote:
> ktrace revealed a openat64, stat64, close of each disk/partition
> without trying to read a ZFS disklabel from it.  It seemed to be taking
> an early exit from detection due to:
> 
> if (statbuf.st_size < SPA_MINDEVSIZE) {
> (void) close(fd);

That doesn't seem to trigger any bug on upstream FreeBSD 10.1-BETA2,
even though the stat st_size for a disk/partition device is 0...

Turns out that cddl/compat/opensolaris/sys/stat.h defines a special
fstat64 that additionally calls DIOCGMEDIASIZE if it is a character
device.  But on GNU/kFreeBSD we're calling the plain GNU libc fstat64.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

[Leon Timmermans]

On Tue, Sep 23, 2014 at 9:59 PM, Niko Tyni  wrote:

> I also had a look at the mips one, and there the problem doesn't seem
> to be with the backtrace, as running gdb separately works as expected.
> However, running perl with -d:bt doesn't seem to do anything. It looks
> like the host is just too slow; inserting a 'sleep(1)' just before the
> "thread apply all backtrace" command in stack_trace() fixes it for
> me. Perhaps the code should just check that the fd is ready for writing?
>

This should not matter. Pipes are buffered at a kernel level. This is not
making sense to me.

Leon

Bug#735190: Please back this out NOW

[Nigel Horne]

Since updating with this, bind stays up no more than 5 minutes before 
crashing.  Please fix urgently.


-Nigel



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#740509: ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address

[Steven Chamberlain]

On 23:34, Steven Chamberlain wrote:
> A sysctl { CTL_NET, PF_ROUTE, 0, 0, NET_RT_IFLIST, 0 } from
> kfreebsd-i386 userland on kfreebsd-amd64 9.0 or 10.0 kernel, never
> seems to fail with ENOMEM!  Regardless of given buffer size:

Have tried on upstream 32-bit kernel with 32-bit userland, and it
doesn't have this issue.  So it is probably a bug in the compat code
only.

GNU libc should perhaps start with an initial 1024-byte allocation
anyway, since 512 bytes is no longer enough even for a machine with
only one NIC.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#731374: marked as done (mono-server4-update uses .NET 4.0, not 4.5 - causes)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 13:00:09 +
with message-id 
and subject line Bug#731374: fixed in xsp 3.8-1
has caused the Debian Bug report #731374,
regarding mono-server4-update uses .NET 4.0, not 4.5 - causes
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.)


-- 
731374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-mono
Version: 2.11+git20130708.6b73e85-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?

Upgrading mono to version 3.0.6 

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

Had to kill the installation after one hour where nothing happened.

   * What was the outcome of this action?

Had to reboot since warned about apache2 process id messed up.

   * What outcome did you expect instead?

A successfull upgrade.



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

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

Versions of packages libapache2-mod-mono depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.6-3
ii  debconf 1.5.52
ii  libc6   2.17-93
ii  mono-apache-server4 3.0.11-1
ii  mono-runtime3.0.6+dfsg2-9

libapache2-mod-mono recommends no packages.

libapache2-mod-mono suggests no packages.

-- debconf information:
  libapache2-mod-mono/mono-server: mod-mono-server4
--- End Message ---
--- Begin Message ---
Source: xsp
Source-Version: 3.8-1

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

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 731...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated xsp 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 25 Sep 2014 10:23:48 +0100
Source: xsp
Binary: dh-xsp mono-xsp2-base mono-xsp4-base mono-xsp4 mono-xsp2 mono-xsp 
asp.net-examples mono-apache-server4 mono-apache-server2 mono-apache-server 
mono-fpm-server libfpm-helper0 mono-fastcgi-server4 mono-fastcgi-server2 
mono-fastcgi-server
Architecture: source all amd64
Version: 3.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mono Group 
Changed-By: Jo Shields 
Description:
 asp.net-examples - demo pages for ASP.NET infrastructure
 dh-xsp - debhelper add-on to handle ASP.NET sites
 libfpm-helper0 - ASP.NET backend for FastCGI Process Manager - helper lib
 mono-apache-server - ASP.NET backend for mod_mono Apache module - default 
version
 mono-apache-server2 - ASP.NET 2.0 backend for mod_mono2 Apache module
 mono-apache-server4 - ASP.NET 4.5 backend for mod_mono Apache module
 mono-fastcgi-server - ASP.NET backend for FastCGI webservers - default version
 mono-fastcgi-server2 - ASP.NET 2.0 backend for FastCGI webservers
 mono-fastcgi-server4 - ASP.NET 4.0 backend for FastCGI webservers
 mono-fpm-server - ASP.NET backend for FastCGI Process Manager
 mono-xsp   - simple web server to run ASP.NET applications - default version
 mono-xsp2  - simple web server to run ASP.NET 2.0 applications
 mono-xsp2-base - base libraries for XSP 2.0
 mono-xsp4  - simple web server to run ASP.NET 4.0 applications
 mono-xsp4-base - base libraries for XSP 4.0
Closes: 692560 731374
Changes:
 xsp (3.8-1) unstable; urgency=medium
 .
   * [2f6490d] Fix libs path (LP: 1293481) (Closes: #731374)
 (Thanks to Shahid Ali)
   * [5f37cfd] Imported Upstream version 3.8
   * [19ead6c] Fix package description 1.0->4.5
   * [fc25680] Fix init message (Closes: #692560)
   * [c428f8d] Add mono-fpm-server package, for "FastCGI Process Manager"
 variant of XSP, and libfpm-helper0, a native C library used by it
 (and also used by the older fastcgi variants)
Checksums-Sha1:
 9e543769c56835c241ad8a2f152652f255ec4e1c 2564 xsp_3.8-1.dsc
 10b24a2a7edd279dcec0a6e0a0ca8127d70ec24e 735140 xsp_3.8.or

Processed: Re: Fails on launch if set to widescreen

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #748525 [pangzero] Fails on launch if set to widescreen
Added tag(s) patch.

-- 
748525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748525
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#748525: Fails on launch if set to widescreen

[Markus Koschany]

Control: tags -1 patch

A new upstream snapshot with a patch for this issue is available at
mentors.debian.net and in the team's SVN repository.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#755612: marked as done (django-reversion: Please ensure it works with Django 1.7)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 12:00:07 +
with message-id 
and subject line Bug#755612: fixed in django-reversion 1.8.4-1
has caused the Debian Bug report #755612,
regarding django-reversion: Please ensure it works with Django 1.7
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.)


-- 
755612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-reversion
Version: 1.8-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package django-reversion depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
Source: django-reversion
Source-Version: 1.8.4-1

We believe that the bug you reported is fixed in the latest version of
django-reversion, which is due to be installed in the Debian FTP archive.

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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
django-reversion 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Sep 2014 08:32:54 +0200
Source: django-reversion
Binary: python-django-reversion python3-django-reversion 
python-django-reversion-doc
Architecture: source all
Version: 1.8.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-reversion - Provides comprehensive version control facilities 
for Django
 python-django-reversion-doc - Provides comprehensive version control 
facilities for Django (Doc
 python3-django-reversion - Provides comprehensive version control facilities 
for Django (Pyt
Closes: 755612
Changes:
 django-reversion (1.8.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #755612).
   * Add dh-python to Build-Depends.
   * Switch buildsystem to pybuild.
   * Remove superfluous install file.
   * Add Python3 support.
   * Bump Build-Depends and Depends for python(3)-django to (>= 1.7).
   * Bump Standards-Version to 3.9.6.
   * Fix the way upstream tests are run during build.
   * Add lintian override for missing PGP signature on upstream tarballs.
   * Remove PHONY target declarations in d/rules.
Checksums-Sha1:
 ab8cb06f8cae9dd954b6ce13215b7b49cff89e5a 2392 django-reversion_1.8.4-1.dsc
 e5e2a6109a8c8778008ff0b34a3220fa2f978a96 66539 
django-reversion_1.8.4.orig.tar.gz
 61568a76764606928dd4de263db55fdebeedf730 4396 
django-reversion_1.8.4-1.debian.tar.xz
 c145bb3c61a68cda01d7b0f3bdc31a72a63f90bd 39732 
pytho

Bug#755604: marked as done (django-sitetree: Please ensure it works with Django 1.7)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 12:00:08 +
with message-id 
and subject line Bug#755604: fixed in django-sitetree 1.1.0-1
has caused the Debian Bug report #755604,
regarding django-sitetree: Please ensure it works with Django 1.7
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.)


-- 
755604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-sitetree
Version: 1.0.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package django-sitetree depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
Source: django-sitetree
Source-Version: 1.1.0-1

We believe that the bug you reported is fixed in the latest version of
django-sitetree, which is due to be installed in the Debian FTP archive.

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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
django-sitetree 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 20 Sep 2014 18:42:33 +0200
Source: django-sitetree
Binary: python-django-sitetree python3-django-sitetree 
python-django-sitetree-doc
Architecture: source all
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-sitetree - site tree, menu and breadcrumbs navigation for Django
 python-django-sitetree-doc - site tree, menu and breadcrumbs navigation for 
Django (Documentat
 python3-django-sitetree - site tree, menu and breadcrumbs navigation for 
Django (Python3 ve
Closes: 755604
Changes:
 django-sitetree (1.1.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #755604).
   * Add dh-python to Build-Depends.
   * Switch buildsystem to pybuild.
   * Add support for Python3.
   * Remove now obsolete d/python-django-sitetree.install.
   * Update years in d/copyright.
Checksums-Sha1:
 a21fd7fd6e2221c723baddc5e16f4d639b34740c 2413 django-sitetree_1.1.0-1.dsc
 557a98c744fdc3a6da0620b57c1ef264969217de 63370 
django-sitetree_1.1.0.orig.tar.gz
 24703e87a9c61378fe0512b56dfc846efb26cffd 3028 
django-sitetree_1.1.0-1.debian.tar.xz
 fb7172cb4bf76898e62c562e4a49a6107cb82902 44330 
python-django-sitetree_1.1.0-1_all.deb
 9520a27ca231f61bdd6253af2f1338d8b05bd38d 44242 
python3-django-sitetree_1.1.0-1_all.deb
 f5b6bda4888619a15f761f8c6446986e472e59e6 42618 
python-django-sitetree-doc_1.1.0-1_all.deb
Checksums-Sha256:
 00354ac6f889cc8eb

Bug#755602: marked as done (django-polymorphic: Please ensure it works with Django 1.7)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 12:00:07 +
with message-id 
and subject line Bug#755602: fixed in django-polymorphic 0.5.6-1
has caused the Debian Bug report #755602,
regarding django-polymorphic: Please ensure it works with Django 1.7
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.)


-- 
755602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-polymorphic
Version: 0.5.4-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package django-polymorphic depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
Source: django-polymorphic
Source-Version: 0.5.6-1

We believe that the bug you reported is fixed in the latest version of
django-polymorphic, which is due to be installed in the Debian FTP archive.

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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
django-polymorphic 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 19 Sep 2014 14:16:19 +0200
Source: django-polymorphic
Binary: python-django-polymorphic python3-django-polymorphic 
python-django-polymorphic-doc
Architecture: source all
Version: 0.5.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-polymorphic - Seamless Polymorphic Inheritance for Django Models
 python-django-polymorphic-doc - Seamless Polymorphic Inheritance for Django 
Models (Documentation
 python3-django-polymorphic - Seamless Polymorphic Inheritance for Django 
Models (Python3 versi
Closes: 755602
Changes:
 django-polymorphic (0.5.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add django-1.7.patch to fix the test-suite with Django 1.7 (Closes:
 #755602).
   * Add dh-python to Build-Depends.
   * Switch buildsystem to pybuild.
   * Remove superfluous install file.
   * Add Python3 support.
   * Update upstream information in d/copyright.
Checksums-Sha1:
 7c05f9ae223eedf3bdfdfa0741c923c5426b5d40 2424 django-polymorphic_0.5.6-1.dsc
 a3de29797cb27c4678a26a3b5fb267c44ee7ebbf 60001 
django-polymorphic_0.5.6.orig.tar.gz
 b7e05913361aa5f21d5764c09fcb95a936a322ab 5804 
django-polymorphic_0.5.6-1.debian.tar.xz
 e2299052cdb4cb39fcd35f235631ba6dd8ab25af 33696 
python-django-polymorphic_0.5.6-1_all.deb
 a54840a4ef1bcc546eb3a7072e4e39b2f2521a13 33550 
python3-django-polymorphic_0.5.6-1_all.deb
 4a2f544223

Bug#754757: timeout during g++

[Aníbal Monsalve Salazar]

On Tue, 2014-09-16 21:20:23 +0200, Bas Wijnen wrote:
> Hello Mips-porters,
> 
> My package, openmsx, failed to build on mips due to a compiler timeout.
> (#754757) Looking at the earlier successful buildd logs, it has always taken
> quite long to build.  In the bug it was reported that compilation does succeed
> if it is not interrupted, so the compiler doesn't hang.  It can be worked
> around by disabling optimization, but my guess is that if even the buildds are
> so slow, mips users will need all the optimization they can get.
> 
> What do you suggest I do?  My preference would be to get the timeout value
> increased, so that it will build as is.  Is that an option?
> 
> Thank you,
> Bas Wijnen
> 
> Ps: Please Cc me on replies, I'm not subscribed.

Please see Dejan's patch at the end of message #25 of bug #754757:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754757#25


signature.asc
Description: Digital signature

Bug#714291: marked as done (uninstallable; depends on obsolete xulrunner-10.0)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 11:30:06 +
with message-id 
and subject line Bug#762803: Removed package(s) from unstable
has caused the Debian Bug report #714291,
regarding uninstallable; depends on obsolete xulrunner-10.0
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.)


-- 
714291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kiwix
Version: 0.9~beta6.8-1
Severity: serious

Hi,

I have installed the package a while back, but I am no longer able to
install it on other 'powerpc' machines as it depends on 'xulrunner-10.0'
which got removed from the pool for that achitecture.

Please update the package dependencies to newer versions of 'xulrunner'.

Regards,

Raf

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (999, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 3.2.0-4-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kiwix depends on:
ii  aria2   1.17.0-1
ii  desktop-file-utils  0.21-1
ii  libc6   2.17-6
ii  libclucene0ldbl 0.9.21b-2+b1
ii  libgcc1 1:4.8.1-4
ii  libicu484.8.1.1-12
ii  liblzma55.1.1alpha+20120614-2
ii  libmicrohttpd10 0.9.27-1
ii  libnspr42:4.10-1
ii  libnspr4-0d 2:4.10-1
ii  libstdc++6  4.8.1-4
ii  libxapian22 1.2.15-2
ii  menu2.1.46
ii  xulrunner-10.0  10.0.12esr-1+nmu1
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages kiwix recommends:
ii  xapian-tools  1.2.15-2

kiwix suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.9~beta6.8-1+rm

Dear submitter,

as the package kiwix has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/762803

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#752837: marked as done (kiwix: build-depends on xulrunner-dev which is gone)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 11:30:06 +
with message-id 
and subject line Bug#762803: Removed package(s) from unstable
has caused the Debian Bug report #752837,
regarding kiwix: build-depends on xulrunner-dev which is gone
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.)


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

kiwix build-depends on xulrunner-dev, which is no longer built by
src:iceweasel. If you use it for libxul or mozilla-plugin, that is
now in iceweasel-dev. If you were using mozilla-js, you may want to
look at src:mozjs24.

Emilio 
--- End Message ---
--- Begin Message ---
Version: 0.9~beta6.8-1+rm

Dear submitter,

as the package kiwix has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/762803

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#713090: marked as done (kiwix: FTBFS: xpidl.IDLError: error: type 'PRUint32' not found, ../../../src/components/zimAccessor/IZimAccessor.idl line 13:30)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 11:30:06 +
with message-id 
and subject line Bug#762803: Removed package(s) from unstable
has caused the Debian Bug report #713090,
regarding kiwix: FTBFS: xpidl.IDLError: error: type 'PRUint32' not found, 
../../../src/components/zimAccessor/IZimAccessor.idl line 13:30
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.)


-- 
713090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kiwix
Version: 0.9~beta6.8-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[4]: Entering directory `/«PKGBUILDDIR»/src/components/zimAccessor'
> /usr/bin/python /usr/lib/xulrunner-devel-17.0/sdk/bin/typelib.py 
> --cachedir=/tmp -o zimAccessor.xpt -I /usr/lib/xulrunner-devel-17.0/idl 
> ../../../src/components/zimAccessor/IZimAccessor.idl
> Traceback (most recent call last):
>   File "/usr/lib/xulrunner-devel-17.0/sdk/bin/typelib.py", line 290, in 
> 
> idl.resolve(options.incdirs, p)
>   File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 287, in resolve
> p.resolve(self)
>   File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 526, in resolve
> member.resolve(self)
>   File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 897, in resolve
> p.resolve(self)
>   File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 1035, in resolve
> self.realtype = method.iface.idl.getName(self.type, self.location)
>   File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 271, in getName
> raise IDLError("type '%s' not found" % id, location)
> xpidl.IDLError: error: type 'PRUint32' not found, 
> ../../../src/components/zimAccessor/IZimAccessor.idl line 13:30
>   boolean getArticleCount(out PRUint32 count);
>   ^
> make[4]: *** [zimAccessor.xpt] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/kiwix_0.9~beta6.8-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.9~beta6.8-1+rm

Dear submitter,

as the package kiwix has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/762803

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#701302: marked as done (kiwix: ftbfs with GCC-4.8)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 11:30:06 +
with message-id 
and subject line Bug#762803: Removed package(s) from unstable
has caused the Debian Bug report #701302,
regarding kiwix: ftbfs with GCC-4.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.)


-- 
701302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kiwix
Version: 0.9~beta6.8-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8

The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.

  FSDirectory.h:92:5: error: looser throw specifier for 'virtual 
lucene::store::FSDirectory::FSIndexInput::SharedHandle::~SharedHandle() throw 
(CLuceneError&)'

The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/kiwix_0.9~beta6.8-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.

To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev

The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.

[...]
   ^
cluceneAccessor.cpp:75:1: note: in expansion of macro 'NS_IMPL_ISUPPORTS1'
 NS_IMPL_ISUPPORTS1(CluceneAccessor, ICluceneAccessor)
 ^
cluceneAccessor.cpp: In destructor 'CluceneAccessor::~CluceneAccessor()':
cluceneAccessor.cpp:85:18: warning: deleting object of polymorphic class type 
'kiwix::CluceneSearcher' which has non-virtual destructor might cause undefined 
behaviour [-Wdelete-non-virtual-dtor]
 delete this->searcher;
  ^
cluceneAccessor.cpp: At global scope:
cluceneAccessor.cpp:90:15: warning: unused parameter 'winDirectory' 
[-Wunused-parameter]
 NS_IMETHODIMP CluceneAccessor::OpenReadableDatabase(const nsACString 
&unixDirectory, const nsACString &winDirectory, mozbool *retVal) {
   ^
cluceneAccessor.cpp:184:1: warning: missing initializer for member 
'mozilla::Module::CIDEntry::service' [-Wmissing-field-initializers]
 };
 ^
cluceneAccessor.cpp:184:1: warning: missing initializer for member 
'mozilla::Module::CIDEntry::getFactoryProc' [-Wmissing-field-initializers]
cluceneAccessor.cpp:184:1: warning: missing initializer for member 
'mozilla::Module::CIDEntry::constructorProc' [-Wmissing-field-initializers]
cluceneAccessor.cpp:189:1: warning: missing initializer for member 
'mozilla::Module::ContractIDEntry::cid' [-Wmissing-field-initializers]
 };
 ^
cluceneAccessor.cpp:196:1: warning: missing initializer for member 
'mozilla::Module::getFactoryProc' [-Wmissing-field-initializers]
 };
 ^
cluceneAccessor.cpp:196:1: warning: missing initializer for member 
'mozilla::Module::loadProc' [-Wmissing-field-initializers]
cluceneAccessor.cpp:196:1: warning: missing initializer for member 
'mozilla::Module::unloadProc' [-Wmissing-field-initializers]
In file included from cluceneAccessor.cpp:35:0:
/usr/lib/xulrunner-devel-10.0/include/mozilla/ModuleUtils.h:156:1: warning: 
unused parameter 'aCompMgr' [-Wunused-parameter]
 NSGetModule(nsIComponentManager* aCompMgr, \
 ^
cluceneAccessor.cpp:199:1: note: in expansion of macro 
'NS_IMPL_MOZILLA192_NSGETMODULE'
 NS_IMPL_MOZILLA192_NSGETMODULE(&kCluceneAccessorModule)
 ^
/usr/lib/xulrunner-devel-10.0/include/mozilla/ModuleUtils.h:156:1: warning: 
unused parameter 'aLocation' [-Wunused-parameter]
 NSGetModule(nsIComponentManager* aCompMgr, \
 ^
cluceneAccessor.cpp:199:1: note: in expansion of macro 
'NS_IMPL_MOZILLA192_NSGETMODULE'
 NS_IMPL_MOZILLA192_NSGETMODULE(&kCluceneAccessorModule)
 ^
make[5]: *** [libCluceneAccessor_la-cluceneAccessor.lo] Error 1
make[5]: Leaving directory `/«PKGBUILDDIR»/src/components/cluceneAccessor'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/«PKGBUILDDIR»/src/components/cluceneAccessor'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/src/components'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»/src'
make[1]: *** [all-recursive] Error 1
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.9~beta6.8-1+rm

Dear submitter,

as the package kiwix has just been removed from the Debian archi

Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

[Aníbal Monsalve Salazar]

On Tue, 2014-09-23 22:59:46 +0300, Niko Tyni wrote:
> 
> I also had a look at the mips one, and there the problem doesn't seem
> to be with the backtrace, as running gdb separately works as expected.
> However, running perl with -d:bt doesn't seem to do anything. It looks
> like the host is just too slow; inserting a 'sleep(1)' just before the
> "thread apply all backtrace" command in stack_trace() fixes it for
> me. Perhaps the code should just check that the fd is ready for writing?

With Niko's workaround, libdevel-bt-perl-0.06 builds on mips and mipsel.

debdiff libdevel-bt-perl_0.06-2.dsc libdevel-bt-perl_0.06-2.1.dsc
diff -Nru libdevel-bt-perl-0.06/debian/changelog 
libdevel-bt-perl-0.06/debian/changelog
--- libdevel-bt-perl-0.06/debian/changelog  2014-09-04 13:24:11.0 
+0100
+++ libdevel-bt-perl-0.06/debian/changelog  2014-09-25 12:08:43.0 
+0100
@@ -1,3 +1,13 @@
+libdevel-bt-perl (0.06-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on mips and mipsel.
+Add sleep-bt.xs.patch.
+Patch by Niko Tyni.
+Closes: #721421.
+
+ -- Anibal Monsalve Salazar   Thu, 25 Sep 2014 12:08:40 
+0100
+
 libdevel-bt-perl (0.06-2) unstable; urgency=low
 
   [ gregor herrmann ]
diff -Nru libdevel-bt-perl-0.06/debian/patches/series 
libdevel-bt-perl-0.06/debian/patches/series
--- libdevel-bt-perl-0.06/debian/patches/series 2014-09-04 13:24:11.0 
+0100
+++ libdevel-bt-perl-0.06/debian/patches/series 2014-09-25 12:07:45.0 
+0100
@@ -1,2 +1,3 @@
 hurd_path_max.patch
 0001-Raise-instead-of-kill-the-signal.patch
+sleep-bt.xs.patch
diff -Nru libdevel-bt-perl-0.06/debian/patches/sleep-bt.xs.patch 
libdevel-bt-perl-0.06/debian/patches/sleep-bt.xs.patch
--- libdevel-bt-perl-0.06/debian/patches/sleep-bt.xs.patch  1970-01-01 
01:00:00.0 +0100
+++ libdevel-bt-perl-0.06/debian/patches/sleep-bt.xs.patch  2014-09-25 
12:07:59.0 +0100
@@ -0,0 +1,25 @@
+From: Niko Tyni 
+Subject: Re: Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, 
kfreebsd-amd64
+Date: Tue, 23 Sep 2014 22:59:46 +0300
+
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721421
+
+I had a look at the mips one, and there the problem doesn't seem to be with the
+backtrace, as running gdb separately works as expected.  However, running perl
+with -d:bt doesn't seem to do anything. It looks like the host is just too
+slow; inserting a 'sleep(1)' just before the "thread apply all backtrace"
+command in stack_trace() fixes it for me. Perhaps the code should just check
+that the fd is ready for writing?
+
+Index: libdevel-bt-perl-0.06/bt.xs
+===
+--- libdevel-bt-perl-0.06.orig/bt.xs
 libdevel-bt-perl-0.06/bt.xs
+@@ -91,6 +91,7 @@ stack_trace (char **args)
+ FD_ZERO(&fdset);
+ FD_SET(out_fd[0], &fdset);
+ 
++sleep(1);
+ write(in_fd[1], "thread apply all backtrace\n", 27);
+ write(in_fd[1], "quit\n", 5);
+ 


signature.asc
Description: Digital signature

Bug#701563: marked as done (kiwix: ftbfs with GCC-4.8)

[Debian Bug Tracking System]

Your message dated Thu, 25 Sep 2014 11:30:06 +
with message-id 
and subject line Bug#762803: Removed package(s) from unstable
has caused the Debian Bug report #701302,
regarding kiwix: ftbfs with GCC-4.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.)


-- 
701302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kiwix
Version: 0.9~beta6.8-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8

The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.

  FSDirectory.h:92:5: error: looser throw specifier for 'virtual 
lucene::store::FSDirectory::FSIndexInput::SharedHandle::~SharedHandle() throw 
(CLuceneError&)'

The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/kiwix_0.9~beta6.8-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.

To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev

The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.

[...]
   ^
cluceneAccessor.cpp:75:1: note: in expansion of macro 'NS_IMPL_ISUPPORTS1'
 NS_IMPL_ISUPPORTS1(CluceneAccessor, ICluceneAccessor)
 ^
cluceneAccessor.cpp: In destructor 'CluceneAccessor::~CluceneAccessor()':
cluceneAccessor.cpp:85:18: warning: deleting object of polymorphic class type 
'kiwix::CluceneSearcher' which has non-virtual destructor might cause undefined 
behaviour [-Wdelete-non-virtual-dtor]
 delete this->searcher;
  ^
cluceneAccessor.cpp: At global scope:
cluceneAccessor.cpp:90:15: warning: unused parameter 'winDirectory' 
[-Wunused-parameter]
 NS_IMETHODIMP CluceneAccessor::OpenReadableDatabase(const nsACString 
&unixDirectory, const nsACString &winDirectory, mozbool *retVal) {
   ^
cluceneAccessor.cpp:184:1: warning: missing initializer for member 
'mozilla::Module::CIDEntry::service' [-Wmissing-field-initializers]
 };
 ^
cluceneAccessor.cpp:184:1: warning: missing initializer for member 
'mozilla::Module::CIDEntry::getFactoryProc' [-Wmissing-field-initializers]
cluceneAccessor.cpp:184:1: warning: missing initializer for member 
'mozilla::Module::CIDEntry::constructorProc' [-Wmissing-field-initializers]
cluceneAccessor.cpp:189:1: warning: missing initializer for member 
'mozilla::Module::ContractIDEntry::cid' [-Wmissing-field-initializers]
 };
 ^
cluceneAccessor.cpp:196:1: warning: missing initializer for member 
'mozilla::Module::getFactoryProc' [-Wmissing-field-initializers]
 };
 ^
cluceneAccessor.cpp:196:1: warning: missing initializer for member 
'mozilla::Module::loadProc' [-Wmissing-field-initializers]
cluceneAccessor.cpp:196:1: warning: missing initializer for member 
'mozilla::Module::unloadProc' [-Wmissing-field-initializers]
In file included from cluceneAccessor.cpp:35:0:
/usr/lib/xulrunner-devel-10.0/include/mozilla/ModuleUtils.h:156:1: warning: 
unused parameter 'aCompMgr' [-Wunused-parameter]
 NSGetModule(nsIComponentManager* aCompMgr, \
 ^
cluceneAccessor.cpp:199:1: note: in expansion of macro 
'NS_IMPL_MOZILLA192_NSGETMODULE'
 NS_IMPL_MOZILLA192_NSGETMODULE(&kCluceneAccessorModule)
 ^
/usr/lib/xulrunner-devel-10.0/include/mozilla/ModuleUtils.h:156:1: warning: 
unused parameter 'aLocation' [-Wunused-parameter]
 NSGetModule(nsIComponentManager* aCompMgr, \
 ^
cluceneAccessor.cpp:199:1: note: in expansion of macro 
'NS_IMPL_MOZILLA192_NSGETMODULE'
 NS_IMPL_MOZILLA192_NSGETMODULE(&kCluceneAccessorModule)
 ^
make[5]: *** [libCluceneAccessor_la-cluceneAccessor.lo] Error 1
make[5]: Leaving directory `/«PKGBUILDDIR»/src/components/cluceneAccessor'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/«PKGBUILDDIR»/src/components/cluceneAccessor'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/src/components'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»/src'
make[1]: *** [all-recursive] Error 1
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.9~beta6.8-1+rm

Dear submitter,

as the package kiwix has just been removed from the Debian archi

Bug#762691: vino: Latest vino update broke gnome-session

[Ondřej Surý]

Hi Andreas,

On Thu, Sep 25, 2014, at 12:54, Andreas Henriksson wrote:
> Hello Ondřej Surý!
> 
> Thanks for your bug report about vino schema changes.
> We briefly discussed this problem on the debian-gnome irc channel
> since ricotz notified us about this fact.
> We probably need a Breaks: gnome-session (<< 3.14) in vino (or
> gnome-settings-daemon? All the details are not clear to me
> since I haven't found the time to look closer at this yet.)
> 
> Could you please share which versions of gnome-session (and
> gnome-settings-daemon?) you where testing with?

/var/log/apt/history.log snippet:

Start-Date: 2014-09-24  14:03:30
Commandline: apt-get dist-upgrade
Install: [...], gnome-session:amd64 (3.12.1-3, 3.14.0-1), [...],
gnome-settings-daemon:amd64 (3.12.2-1+b2, 3.14.0-1), [...]

I could attach full history.log if needed.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Processed: Debian bug: #762771, 762772, 762773, 762780

[Debian Bug Tracking System]

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

> fixed 762771 argyll/1.6.3-2
Bug #762771 [src:argyll] argyll: FTBFS: recipe for target 
'override_dh_installdocs' failed
The source argyll and version 1.6.3-2 do not appear to match any binary packages
Marked as fixed in versions argyll/1.6.3-2.
> fixed 762772 argyll/1.6.3-2
Bug #762772 [src:argyll] argyll: FTBFS on arm64: unable to guess system type
The source argyll and version 1.6.3-2 do not appear to match any binary packages
Marked as fixed in versions argyll/1.6.3-2.
> fixed 762773 argyll/1.6.3-2
Bug #762773 [src:argyll] argyll: FTBFS on kFreeBSD: linux/usbdevice_fs.h: No 
such file or directory
The source argyll and version 1.6.3-2 do not appear to match any binary packages
Marked as fixed in versions argyll/1.6.3-2.
> fixed 762780 argyll/1.6.3-2
Bug #762780 [argyll-ref] argyll-refV File conflict without Replaces field with 
argyll 1.5.1-8
The source argyll and version 1.6.3-2 do not appear to match any binary packages
Marked as fixed in versions argyll/1.6.3-2.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
762771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762771
762772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762772
762773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762773
762780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762780
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