Bug#751333: marked as done (yrmcds: non-standard gcc/g++ used for build (gcc-4.8))

[Debian Bug Tracking System]

Your message dated Thu, 07 Aug 2014 06:34:00 +
with message-id 
and subject line Bug#751333: fixed in yrmcds 1.0.4-3
has caused the Debian Bug report #751333,
regarding yrmcds: non-standard gcc/g++ used for build (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.)


-- 
751333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yrmcds
Version: 1.0.4-2
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.7-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.7 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: yrmcds
Source-Version: 1.0.4-3

We believe that the bug you reported is fixed in the latest version of
yrmcds, 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 751...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kouhei Maeda  (supplier of updated yrmcds 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: Thu, 07 Aug 2014 10:29:10 +0900
Source: yrmcds
Binary: yrmcds
Architecture: source amd64
Version: 1.0.4-3
Distribution: experimental
Urgency: medium
Maintainer: Kouhei Maeda 
Changed-By: Kouhei Maeda 
Description:
 yrmcds - memcached compatible KVS with master/slave replication
Closes: 751333
Changes:
 yrmcds (1.0.4-3) experimental; urgency=medium
 .
   * Fixed non-standard gcc/g++ used for build (gcc-4.8) (Closes: #751333)
 - debian/control
   * Removed [!ia64 sparc] from g++ >= 4:4.8, g++ == 4:4.8 [ia64 sparc]
 at Build-Depends.
 - debian/rules
   * Removed export CC, CXX for ia64 and sparc.
   * Removed --with quilt at dh command.
Checksums-Sha1:
 58d35768c24cdd3518329082c5888fc1a99ceb1e 1828 yrmcds_1.0.4-3.dsc
 138091bb88f5ed3def3c518c20158b986a13383c 9156 yrmcds_1.0.4-3.debian.tar.xz
 5d4f27564c64f47dfd5b1e8bcc5dd8da3ded8c6a 115726 yrmcds_1.0.4-3_amd64.deb
Checksums-Sha256:
 b55cd168a910ccd2a8e2b0900de695ca7eafa0ec4f1cb306db6d984f8104 1828 
yrmcds_1.0.4-3.dsc
 bee50ee648bff2e1a359c44220d758de88a96bf3f206dc2353ea95bb26329a80 9156 
yrmcds_1.0.4-3.debian.tar.xz
 17ad508954cba2799f66bf34d30f9ed2a35243efaf341b228f8ea0b09ae9f3a0 115726 
yrmcds_1.0.4-3_amd64.deb
Files:
 f6fdff17fc20733fd68a65b18fa7ae1d 115726 web optional yrmcds_1.0.4-3_amd64.deb
 f9796be3f7bda1344ad99461c5b4a7ec 1828 web optional yrmcds_1.0.4-3.dsc
 b2b45921e446163edf6ceff34958e5d1 9156 web optional yrmcds_1.0.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT4xlPAAoJEDIkf7tArR+mKZsP/1JUU43ka/VeIuWoLfGv/QZ4
yOgLcjlIsEavgfeKf/WSW7dfQVemR1zo+mBBRLQdZTmT8dOHQq5s6rE5jU9Ql9F4
38SdL6CgsqseXSqkhWwS3Lq7425PEFk7hmSp9Du7dDAXfDRt354kzHKGIbAjmPD6
pYC/740lZW+19kOHsyPncjJHcetTuq/im/MmrTW+gfbPy/ouT1gPWtbOadOaSbeU
ESsGOccCymRE4JpthezPU0uNHSlTmSVZj192+t1uuCj5M8O2Hot/1D+uNGHrce98
O6xDI4XTnBFc3eCzR5gFrKHIz/kDiAFWHDDgKbSbjO5tVCLkwSRhtE0hkp538nY/
1ceK2ezJc6T2FEHWDT2Sd21mGdi8rEeuV1oijR3K1jUb6ZloEw9Rp+SwGp4WWNhU
1FTGfhAbom4Y2oOS3D+0dnz1gVUhxhP5xUxo5nmVyY8+3lwjVueX7DH62T6751AU
VNtCjctmtI32fdTNduFIIYFn6jR6qXOE5COb+du7J9bdNnHeKbQNrQ9kUFjWd5aL
00lD7cEFJEDosaFgKHStwKUbhk8bKHwpRmZqmwQ1Cq3ac8+7K2lF1PGf3zNdy780
+TFnm7DprdX1o/ipa1kmcinKF/xdmfgEYspsmkzNHQ/sLyHmWvONghXq230CP/7B
iW9E2Y7ygfb9kajtSvww
=8lFS
-END PGP SIGNATURE End Message ---

Bug#757293: [Pkg-libvirt-maintainers] Bug#757293: libvirt-daemon-system (1.2.7-3) fails to start

[Marc J. Driftmeyer]

Could be a simple out of order configuration dependency throwing a failure.

- Marc

On 08/06/2014 10:10 PM, Guido Günther wrote:

journalctl /usr/sbin/libvirtd


--
Marc J. Driftmeyer
Email :: m...@reanimality.com 
Web :: http://www.reanimality.com
Cell :: (509) 435-5212

Bug#757293: [Pkg-libvirt-maintainers] Bug#757293: libvirt-daemon-system (1.2.7-3) fails to start

[Marc J. Driftmeyer]

Install just means an apt-get update/apt-get upgrade within Sid.

No dist-upgrade was made.

mdriftmeyer@horus:~$ journalctl /usr/sbin/libvirtd
-- Logs begin at Sat 2014-08-02 19:02:24 PDT, end at Tue 2014-08-05 
07:44:38 PDT


/usr/sbin/libvirtd

Output:

mdriftmeyer@horus:~$ /usr/sbin/libvirtd
libnuma: Warning: Cannot parse distance information in sysfs: Success



On 08/06/2014 10:10 PM, Guido Günther wrote:

journalctl /usr/sbin/libvirtd


It just pukes on the libvirt-daemon-system package upgrade.

Use 'apt-get autoremove' to remove them.
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up libvirt-daemon-system (1.2.7-3) ...
Job for libvirtd.service failed. See 'systemctl status libvirtd.service' 
and 'journalctl -xn' for details.

invoke-rc.d: initscript libvirtd, action "start" failed.
dpkg: error processing package libvirt-daemon-system (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libvirt-bin:
 libvirt-bin depends on libvirt-daemon-system (>= 1.2.7-3); however:
  Package libvirt-daemon-system is not configured yet.

dpkg: error processing package libvirt-bin (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libvirt-daemon-system
 libvirt-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)



- Marc

--
Marc J. Driftmeyer
Email :: m...@reanimality.com 
Web :: http://www.reanimality.com
Cell :: (509) 435-5212

Bug#757207: systemd: Installation of systemd makes system unbootable

[Jens Stavnstrup]

As requested

content of /etc/fstab
===

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/ares-root /   ext4errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=CS0IM3-x23c-6Iyg-vtLc-NPWI-FuS2-cSFvr8 /boot   ext2
defaults0   2
/dev/mapper/ares-swap_1 noneswapsw  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
/dev/sdb1   /media/usb0 autorw,user,noauto  0   0



content of /etc/crypttab
=

sda5_crypt UUID=08cb6482-b013-44a8-8158-3bb41812a7f4 none luks



Output ofls -la /dev/disk/by-uuid/
==

lrwxrwxrwx 1 root root  10 Aug  7 07:30
08cb6482-b013-44a8-8158-3bb41812a7f4 -> ../../sda5
lrwxrwxrwx 1 root root  10 Aug  7 07:30
39eb5a09-2859-4891-a22f-ff844891f5cf -> ../../dm-1
lrwxrwxrwx 1 root root  10 Aug  7 07:30
da9bc68a-a904-40aa-b8cc-26df3faf5c6d -> ../../dm-2

Regards

Jens

Bug#722293: marked as done (Fails to generate video due to the lack of ffmpeg command)

[Debian Bug Tracking System]

Your message dated Thu, 07 Aug 2014 03:36:52 +
with message-id 
and subject line Bug#722293: fixed in imagination 3.0-5
has caused the Debian Bug report #722293,
regarding Fails to generate video due to the lack of ffmpeg command
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.)


-- 
722293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagination
Severity: important
User: pkg-multimedia-maintain...@lists.alioth.debian.org
Usertags: ffmpeg-removal

The libav source package no longer builds a ffmpeg binary package.
Please convert your package to avconv from libav-tools.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: imagination
Source-Version: 3.0-5

We believe that the bug you reported is fixed in the latest version of
imagination, 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 722...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated imagination 
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: Wed, 06 Aug 2014 22:06:06 -0400
Source: imagination
Binary: imagination imagination-common
Architecture: source amd64 all
Version: 3.0-5
Distribution: unstable
Urgency: medium
Maintainer: Andrew Starr-Bochicchio 
Changed-By: Andrew Starr-Bochicchio 
Description:
 imagination - DVD slide show maker
 imagination-common - DVD slide show maker - common files
Closes: 722293
Changes:
 imagination (3.0-5) unstable; urgency=medium
 .
   * Add patch porting to use avconv as ffmpeg was removed.
 Thanks to Theppitak Karoonboonyanan! Closes: #722293
   * Bump Standards-Version to 3.9.5
   * Bump libav Recommends.
Checksums-Sha1:
 d1d45ca0d09fe0c63b86d8e131397d34ae485e83 2042 imagination_3.0-5.dsc
 08af10d0a5391bac7d6096489494ec823a5216e1 11956 imagination_3.0-5.debian.tar.xz
 698bde98b1751bb31771880a02446a5ae1694524 95324 imagination_3.0-5_amd64.deb
 628ed6b27a5efe19ab0a99300458eca0ef57efc1 2535266 
imagination-common_3.0-5_all.deb
Checksums-Sha256:
 5e5926d74fe9d41c86c1d4f5de0c45bc101715d4d016236efc640ca203cb8890 2042 
imagination_3.0-5.dsc
 f003e14f86c5e0d129040026aa25a012db35207ecd5da915da30bee99fcfab5c 11956 
imagination_3.0-5.debian.tar.xz
 79b6fb672a6b2107c65b739e35cf48eb38c43e28d7bfca9e9198021b70c9b89c 95324 
imagination_3.0-5_amd64.deb
 ade6a01de60e243624a934f9f34744f5807717d5f4a8a25e30843d163aa3267e 2535266 
imagination-common_3.0-5_all.deb
Files:
 5dfd3d4bb998773e6d5e4857fc7e0e7c 95324 video optional 
imagination_3.0-5_amd64.deb
 602e226bbbd1fa2c29c61d2a188564bc 2535266 video optional 
imagination-common_3.0-5_all.deb
 7deda59077635e796b2e0cc9b0d1e654 2042 video optional imagination_3.0-5.dsc
 7ed29fb0027553fc24911d6c10b4ea37 11956 video optional 
imagination_3.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT4ud+AAoJEDtW4rvVP9yxXzoQAKzuJ5cs4A/4BrPJnqLHySMO
xx97dS0ti08h2hPq6zX//rspLlt4xDOUQ1HWgraZPFhI1QaCzFhZ/DmFob+B8Svk
q8gNX5cHWfXWLUijV7Dd0bN89+y9ojaH+lVOclljE1jWPz/MrMdAJqSWMPa9vV2v
eY0f9mtJYUZgEvtyFsNAdOTSYw85XlmAhdw0D6YNUnyABPd5SmTI8uIqCdYdJpgq
nSWcveFSWOZ+NOoT7TXKEGWZ2Nzkh4Ep4tbW4YoIDC36PWHOoPDzcDCWvwFCPXRR
rT1F7SJpztwLtuDm5D0FTjtN6ANlC5YNMQ2ELKEEWs7hlXggvlIiaPmwLizss3vV
C833ur1cTP+ShJyIfrvDYt2OX8tOEbYyDx8nKJpdaDm6Cy7br7DBfPyu9XKuUqNJ
+Zy/1OTIWa4K0GYtrxfsrlMEKs8rlg4oQvnhTB4DCwB2UxfvjkidqFp6IraV2ylL
CZnOYqNtvAXl4Ozb/ldNZG5QzyLzj+SJbFwQC2fUq0x6A+UuCcEUlrTHcWClcscP
FkebfGFu0jFSJPfS6GijjAlhkenwqnUazAaJzGVZW5Q6iwDAeNlOczw9k8ypeoSY
fZ2sVtXto0vRfMFQl8toO7Rgulk9rxIlpRSGeD1GvIwglfuIY2uhpeM+H8BEEbBk
8nV16h4BdSjUS6hD4Q7Y
=VC6B
-END PGP SIGNATURE End Message ---

Bug#755017: marked as done (FTBFS against cgsi-gsoap 1.3.6-1+b1)

[Debian Bug Tracking System]

Your message dated Thu, 7 Aug 2014 04:52:14 +0200
with message-id <1407379934.5276.5.camel@localhost>
and subject line transition completed
has caused the Debian Bug report #755017,
regarding FTBFS against cgsi-gsoap 1.3.6-1+b1
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.)


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

Doing rebuilds for the libgsoap5 transition, your package failed to build
everywhere except on amd64, i386 and hurd-i386. That seems to be because
in those builds, the version of libcgsi-gsoap1 was 1.3.6-1 (i.e. before the
binNMU for libgsoap5) while on the builds that failed libcgsi-gsoap1 was at
1.3.6-1+1. The error was:

/usr/bin/c++   -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2-Wl,-z,relro 
CMakeFiles/unit_test_srm_plugin.dir/tests_srm.cpp.o  -o unit_test_srm_plugin  
-L/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/src  
-L/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/plugins -rdynamic 
../../../../src/libgfal2.so.2.3.0 -lgfal_srm_ifce -lgfal_transfer 
-lgfal_plugin_srm -lm ../../../../src/libgfal2.so.2.3.0 
../../../gtest/libgtest.a ../../../gtest/libgtest_main.a -luuid -lstdc++ 
-lglib-2.0 -lgthread-2.0 -lglib-2.0 -lgthread-2.0 -ldl 
../../../gtest/libgtest.a -lpthread 
-Wl,-rpath,/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/src:/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/plugins
 
//usr/lib/libcgsi_plugin.so.1: undefined reference to 
`soap_init_LIBRARY_VERSION_REQUIRED_20817'
collect2: error: ld returned 1 exit status
make[4]: *** [test/unit/common/srm/unit_test_srm_plugin] Error 1

I'm filing this against gfal2, although it bothers me that the libraries
shipped by libcgsi-gsoap1 have undefined references. But that's been
happening for a long time, so filing here. Please reassign if necessary.

Emilio
--- End Message ---
--- Begin Message ---
notfound 755017 gfal2/2.3.0-4
done

The gsoap transition has completed without any permanent FTBFS (except
for virtualbox that failed for unrelated reasons and has since been
fixed).

Mattias



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

Processed (with 5 errors): transition completed

[Debian Bug Tracking System]

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

> notfound 755017 gfal2/2.3.0-4
Bug #755017 [src:gfal2] FTBFS against cgsi-gsoap 1.3.6-1+b1
No longer marked as found in versions gfal2/2.3.0-4.
> done
Unknown command or malformed arguments to command.
> The gsoap transition has completed without any permanent FTBFS (except
Unknown command or malformed arguments to command.
> for virtualbox that failed for unrelated reasons and has since been
Unknown command or malformed arguments to command.
> fixed).
Unknown command or malformed arguments to command.
>   Mattias
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

[Debian Bug Tracking System]

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

> # blocks the on-going wxwidgets3.0 transition
> severity 751566 serious
Bug #751566 [src:gnudatalanguage] gnudatalanguage: Please update to use 
wxwidgets3.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> severity 757293 grave
Bug #757293 [libvirt-daemon-system] libvirt-daemon-system (1.2.7-3) fails to 
start
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> close 754629
Bug #754629 [src:gdb-arm-none-eabi] gdb-arm-none-eabi: FTBFS on kfreebsd-i386: 
error: right-hand operand of comma expression has no effect
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754629
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: fixed 754629 in 7.7.1-1+3

[Debian Bug Tracking System]

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

> fixed 754629 7.7.1-1+3
Bug #754629 [src:gdb-arm-none-eabi] gdb-arm-none-eabi: FTBFS on kfreebsd-i386: 
error: right-hand operand of comma expression has no effect
The source 'gdb-arm-none-eabi' and version '7.7.1-1+3' do not appear to match 
any binary packages
Marked as fixed in versions gdb-arm-none-eabi/7.7.1-1+3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754629
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 754629 in 7.6.1-1+1

[Debian Bug Tracking System]

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

> found 754629 7.6.1-1+1
Bug #754629 [src:gdb-arm-none-eabi] gdb-arm-none-eabi: FTBFS on kfreebsd-i386: 
error: right-hand operand of comma expression has no effect
The source 'gdb-arm-none-eabi' and version '7.6.1-1+1' do not appear to match 
any binary packages
Marked as found in versions gdb-arm-none-eabi/7.6.1-1+1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754629
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#757207: systemd: Installation of systemd makes system unbootable

[Michael Biebl]

Could you please also attach your /etc/fstab and /etc/crypttab.

Apparently the emergency shell is triggered after:

Aug 06 11:19:58 ares systemd[1]: Expecting device
dev-disk-by\x2duuid-CS0IM3\x2dx23c\x2d6Iyg\x2dvtLc\x2dNPWI\x2dFuS2\x2dcSFvr8.device...

What's the output of
ls -la /dev/disk/by-uuid/ when you run that from the debug shell on
tty9? I.e., is this device missing during boot.





signature.asc
Description: OpenPGP digital signature

Processed: forcibly merging 755581 757072, severity of 755581 is important

[Debian Bug Tracking System]

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

> forcemerge 755581 757072
Bug #755581 [systemd] systemd: emergency mode infinite loop after systemd 
upgrade
Bug #757072 [systemd] systemd: Emergency mode is broken, conflicts with rescue 
mode
Severity set to 'normal' from 'critical'
Merged 755581 757072
> severity 755581 important
Bug #755581 [systemd] systemd: emergency mode infinite loop after systemd 
upgrade
Bug #757072 [systemd] systemd: Emergency mode is broken, conflicts with rescue 
mode
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
755581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581
757072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757072
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#752954: marked as done (nikola: FTBFS - shell's echo does not interpret -e)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 22:34:23 +
with message-id 
and subject line Bug#752954: fixed in nikola 7.0.1-2
has caused the Debian Bug report #752954,
regarding nikola: FTBFS - shell's echo does not interpret -e
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.)


-- 
752954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nikola
Version: 7.0.1-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
   debian/rules override_dh_bash-completion
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-nikola/nikola-7.0.1'
echo -e '#!/bin/bash\nexport 
PYTHONPATH=/srv/jenkins-slave/workspace/sid-goto-cc-nikola/nikola-7.0.1\n/srv/jenkins-slave/workspace/sid-goto-cc-nikola/nikola-7.0.1/debian/nikola/usr/bin/nikola
 $@' > debian/nikola.sh
chmod +x ./debian/nikola.sh
./debian/nikola.sh init -q debian/dpackaging_site
./debian/nikola.sh: 1: ./debian/nikola.sh: -e: not found
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-nikola/nikola-7.0.1/debian/nikola/usr/bin/nikola",
 line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2837, in 

working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 449, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 742, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 639, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: python-dateutil
debian/rules:26: recipe for target 'override_dh_bash-completion' failed
make[1]: *** [override_dh_bash-completion] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible. It seems that "-e" is not interpreted as a command line option
by "echo", which is likely due to the fact that the default shell is dash. You
may want to use printf instead.

Best,
Michael


nikola-build-log.txt.gz
Description: application/gunzip


pgpskmiQ0dUlt.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: nikola
Source-Version: 7.0.1-2

We believe that the bug you reported is fixed in the latest version of
nikola, 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 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Agustin Henze  (supplier of updated nikola 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: SHA512

Format: 1.8
Date: Wed, 06 Aug 2014 19:10:19 -0300
Source: nikola
Binary: nikola
Architecture: source all
Version: 7.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Agustin Henze 
Description:
 nikola - simple yet powerful and flexible static website and blog generato
Closes: 752954
Changes:
 nikola (7.0.1-2) unstable; urgency=medium
 .
   * Add nikola.sh (nikola runner to create sh_completion files) (Closes:
 #752954)
Checksums-Sha1:
 2eacd68fa3f1cfe37f1ef0b40cf60c49f10d0270 2109 nikola_7.0.1-2.dsc
 d402214dea4503040da77ee9b6c8441b125f340f 14392 nikola_7.0.1-2.debian.tar.xz
 c32f90a9b3a309996cba8a3afcdca31ccb74976f 610448 nikola_7.0.1-2_all.deb
Checksums-Sha256:
 1000fa2dcb062b74bb28d6496dfea122d9641e9342420e30c65a45c77c22996f 2109 
nikola_7.0.1-2.dsc
 5c4b9c3cd61beb030b8e22d08b164450c3a58cc287f36c9c79ad9024d7d62b5c 14392 
nikola_7.0.1-2.debian.tar.xz
 536a7492fdc8f2ef0eda94956bfddc0f65e18e142b985eaaa47f16540b329917 610448 
nikola_7.0.1-2_all.deb
Files:
 c33d2c6d9c25b091428382c65cccbd90 610448 python optional nikola_7.0.1-2_all.deb
 9b6b82aefbd1ef119527c7addfaa252a 2109 python optional nikola_7.0.1-2.dsc
 67701fbd8dc9e8c3137b8f8966a17a42 14392 python optional 
nikola_7.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJT4qlWAAoJEAIoUhB4kDjy1MQQAIP2I5y1K91KJQHr1jVIA0Fb
61M5IrzLL4d4FWDtHgB43eYFlM

Bug#640601: havp: installation fails

[Andreas Cadhalpun]

Control: tags -1 moreinfo unreproducible
Control: severity -1 important

Hi,

I can't reproduce this bug.

For me the installation works fine, but the init script fails to start.
The reason for this is that newer kernels need to load the loop module 
before mounting a loop device.


After running 'sudo modprobe loop' starting the service works.

Can you still reproduce this bug?

Best regards,
Andreas


--
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#640601: havp: installation fails

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #640601 [havp] havp: installation fails
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #640601 [havp] havp: installation fails
Severity set to 'important' from 'serious'

-- 
640601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640601
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#757286: segfault: in libspeexdsp.so.1.5.0

[Carsten Otto]

Package: asterisk
Version: 1:1.8.13.1~dfsg1-3+deb7u3
Severity: serious

Asterisk crashes:

[35737.133589] asterisk[8584]: segfault at 7f7208021000 ip 7f7227e3def9 sp
7f720f2c4480 error 6 in libspeexdsp.so.1.5.0[7f7227e2f000+12000]

I can trigger this using a test in my application, which produces the following
few lines of debug output just before the crash:

Sending ManagerAction:
org.asteriskjava.manager.action.RedirectAction[action='Redirect',actionid='null',extracontext='null',priority='1',extrachannel='null',context
='conf-hold',exten='moh',extrapriority='null',channel='Local/18202@dial-out-
from-conference-98e9;1',extraexten='null',systemHashcode=1463699668]

ManagerResponse is: org.asteriskjava.manager.response.ManagerResponse:
actionId='null'; message='Redirect successful'; response='Success';
uniqueId='null'; systemHashcode=1058186770

No ManagerEventInterpreter was found for eventtype: MeetMeLeaveEvent

VarSetEventInterpreter will now process:
org.asteriskjava.manager.event.VarSetEvent[dateReceived='Wed Aug 06 23:56:09
CEST
2014',privilege='dialplan,all',sequencenumber=null,timestamp=null,uniqueid='1407362109.11',value='56',server=null,variable='MEETMESECS',channel='Local/18202
@dial-out-from-conference-98e9;1',systemHashcode=255564526]

I also created a backtrace for asterisk, which is available here:
http://server.c-otto.de/~cotto/backtrace.txt

For that I compiled asterisk from source and configured DONT_OPTIMIZE and
BETTER_BACKTRACES.

I'm happy to provide further information!



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

Kernel: Linux 3.2.0-4-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 asterisk depends on:
ii  adduser   3.113+nmu3
ii  asterisk-config   1:1.8.13.1~dfsg1-3+deb7u3
ii  asterisk-core-sounds-en [asterisk-prompt-en]  1.4.22-1
ii  asterisk-core-sounds-en-gsm   1.4.22-1
ii  asterisk-modules  1:1.8.13.1~dfsg1-3+deb7u3
ii  binutils  2.22-8
ii  libc6 2.13-38+deb7u3
ii  libcap2   1:2.22-1.2
ii  libgcc1   1:4.7.2-5
ii  libssl1.0.0   1.0.1e-2+deb7u11
ii  libstdc++64.7.2-5
ii  libtinfo5 5.9-10
ii  libxml2   2.8.0+dfsg1-7+wheezy1

Versions of packages asterisk recommends:
ii  asterisk-moh-opsound-gsm 2.03-1
pn  asterisk-voicemail | asterisk-voicemail-storage  
ii  sox  14.4.0-3

Versions of packages asterisk suggests:
ii  asterisk-dahdi   1:1.8.13.1~dfsg1-3+deb7u3
pn  asterisk-dev 
pn  asterisk-doc 
pn  asterisk-ooh323  

-- Configuration Files:
/etc/init.d/asterisk changed [not included]

-- 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#582306: marked as done (Links against libclamav)

[Debian Bug Tracking System]

Your message dated Thu, 07 Aug 2014 00:02:31 +0200
with message-id <53e2a5f7.1040...@googlemail.com>
and subject line Re: Bug#582306: Links against libclamav
has caused the Debian Bug report #582306,
regarding Links against libclamav
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.)


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

havp links against libclamav and is thus affected by #577013. As such
it needs to be moved to volatile.debian.org and blocked out of stable
with a RC blocker bug.

Cheers,
Moritz

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

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=de_DE.ISO-8859-15@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages havp depends on:
ii  adduser   3.112  add and remove users and groups
ii  debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
pn  libclamav4 (no description available)
ii  libgcc1   1:4.4.4-1  GCC support library
ii  libstdc++64.4.4-1The GNU Standard C++ Library v3

Versions of packages havp recommends:
pn  clamav-freshclam   (no description available)

Versions of packages havp suggests:
pn  squid  (no description available)


--- End Message ---
--- Begin Message ---

On 04.07.2014 05:05, Scott Kitterman wrote:

On Monday, October 04, 2010 21:28:12 you wrote:

On Wednesday 19 May 2010 23:08:14 Moritz Muehlenhoff wrote:

havp links against libclamav and is thus affected by #577013. As such
it needs to be moved to volatile.debian.org and blocked out of stable
with a RC blocker bug.


 From now on, havp will remain in unstable only and updates will be pushed to
stable-volatile. This release blocker bug will remain open to prevent a
transition to testing.


Now that we are pushing clamav updates to stable, this bug is obsolete.


Therefore I'm closing this bug now.

Best regards,
Andreas--- End Message ---

Bug#751320: marked as done (libstdc++-arm-none-eabi: non-standard gcc/g++ used for build)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 21:56:56 +
with message-id 
and subject line Bug#751320: fixed in libstdc++-arm-none-eabi 3
has caused the Debian Bug report #751320,
regarding libstdc++-arm-none-eabi: non-standard gcc/g++ used for build
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.)


-- 
751320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++-arm-none-eabi
Version: 1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.7-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.7 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: libstdc++-arm-none-eabi
Source-Version: 3

We believe that the bug you reported is fixed in the latest version of
libstdc++-arm-none-eabi, 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 751...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Agustin Henze  (supplier of updated libstdc++-arm-none-eabi 
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: SHA512

Format: 1.8
Date: Wed, 06 Aug 2014 17:50:55 -0300
Source: libstdc++-arm-none-eabi
Binary: libstdc++-arm-none-eabi-newlib
Architecture: source all
Version: 3
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Agustin Henze 
Description:
 libstdc++-arm-none-eabi-newlib - GNU Standard C++ Library v3 for ARM 
Cortex-A/R/M processors (newl
Closes: 751320
Changes:
 libstdc++-arm-none-eabi (3) unstable; urgency=medium
 .
   * Rebuilt using current gcc version (Closes: #751320)
Checksums-Sha1:
 8eae296deddd2af623fa79ac54bf11aa3e8119e2 1942 libstdc++-arm-none-eabi_3.dsc
 5068a7bc5dde2ba5eb592ab8b00c03f730dd6b22 3113 libstdc++-arm-none-eabi_3.tar.gz
 c80bfa5030480c81b15e9b9ff3f540376553fa9e 24505498 
libstdc++-arm-none-eabi-newlib_4.8.3-7+3_all.deb
Checksums-Sha256:
 496fbc1de7b024d62ed3b2c14a531db8897197224ec96c7cd01562fc127323ad 1942 
libstdc++-arm-none-eabi_3.dsc
 95f72e0ccf90624f91cf00896fb2a389ac515f9fb0778177ecc03231c8dd6780 3113 
libstdc++-arm-none-eabi_3.tar.gz
 514634071379e1a94cb47b259ae6c1726984c74448504e41692e001a4357a503 24505498 
libstdc++-arm-none-eabi-newlib_4.8.3-7+3_all.deb
Files:
 f92f24cff0d7058fbfd76d0ffcb47dfa 24505498 devel extra 
libstdc++-arm-none-eabi-newlib_4.8.3-7+3_all.deb
 9530afa1178080835bbaa827e67efbd4 1942 devel extra libstdc++-arm-none-eabi_3.dsc
 9cce012d7342d5a7ec603dc4c42373a6 3113 devel extra 
libstdc++-arm-none-eabi_3.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJT4pn4AAoJEAIoUhB4kDjyPuUQALjaq1TV42+jz+opxZLCQuGX
L/2pYKbf6ZYQn7s+iy/C0F46soWrGXilLbfEqiOMRfqEX8RXcRkWplBEJWuxJZ1P
L933IxGCYl68ZM9zevAavEY8RU6c6shbOvatAqQGazSv9vbUncqgUzNEXmPXLcob
6dX/M3Eu+su1h1o7u5qo1HXTc9k3R/eRMBwTub4EEHWx3PZEjKF40SKFyZzqiK/G
nhvD8ihu/eUl7+rB5w1Go/jHPlhW6IZ1zARJvVYKFBzURqRz+TkJUMhwDW6SD1KL
mlmEhCGXe6yzO5MdD6aoPRqTrgqYg7CncDwUoxKlNgPsnfFrFaVbjPCnx3hNppQh
CFHFt/nB5bvyFlkxPYdhrC1uO198re6lqTsVnXLloA9njhlFVCtX0w5IfV415XM7
0vx/Y+cSQ1nqfYtQwWoHqeMSu7mg62xyvQcU0oJ/cnxlQvZH61HLwXZdu5RrSYvW
EN+7J0cWcbo/A20uwfZ5l2+C4x3w4oiJ5YrMpIkN/FNR+kUHj/M3U3lfFMxr8GU2
EBmRH8o2kU9Gl3srqt9IM4sOFg3hoeeisqutFvs/N25hYtTMuJ+s00kJyAtVV+kb
FlOqBB8JuUPPCkuzn1Qj2si2HhD+mrT+bZKjNXUQk3PkZdVSgrRQyTbk/my8y3xi
yUh/L+hGCJIEwXTlhpHM
=7C93
-END PGP SIGNATURE End Message ---

Bug#753833: marked as done (Source package contains non-free IETF RFC/I-D)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 21:57:41 +
with message-id 
and subject line Bug#753833: fixed in uriparser 0.8.0.1-1
has caused the Debian Bug report #753833,
regarding Source package contains non-free IETF RFC/I-D
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.)


-- 
753833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Severity: serious
Package: uriparser
Version: 0.7.5-1
User: debian-rele...@lists.debian.org
Usertags: nonfree-doc rfc

Hi!

This source package contains the following files from the
IETF under non-free license terms:


E license-problem-non-free-RFC

doc/rfc3513.htm

E license-problem-non-free-RFC-BCP78

doc/rfc3986.htm



The license on RFC/I-Ds is not DFSG-free, see:

 * http://wiki.debian.org/NonFreeIETFDocuments
 * http://bugs.debian.org/199810

According to the squeeze/wheezy release policy, source packages must be
DFSG-free, see:

 * http://release.debian.org/squeeze/rc_policy.txt
 * http://release.debian.org/wheezy/rc_policy.txt

The severity is serious, because this violates the Debian policy:

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

There are (at least) three ways to fix this problem.  In order of
preference:

1. Ask the author of the RFC to re-license the RFC under a free
   license.  A template for this e-mail request can be found at
   http://wiki.debian.org/NonFreeIETFDocuments

2. Remove the non-free material from the source, e.g., by re-packaging
   the upstream archive and adding 'dfsg' to the Debian package
   version name.

3. Move the package to non-free.

General discussions are kindly requested to take place on debian-legal
or debian-devel in the thread with Subject: "Non-free IETF RFC/I-Ds in
source packages".

Thanks,
--- End Message ---
--- Begin Message ---
Source: uriparser
Source-Version: 0.8.0.1-1

We believe that the bug you reported is fixed in the latest version of
uriparser, 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 753...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated uriparser 
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: Wed, 06 Aug 2014 21:23:55 +0200
Source: uriparser
Binary: liburiparser1 liburiparser-dev
Architecture: source amd64
Version: 0.8.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Description:
 liburiparser-dev - development files for uriparser
 liburiparser1 - URI parsing library compliant with RFC 3986
Closes: 552993 668244 727517 753833 754473
Changes:
 uriparser (0.8.0.1-1) unstable; urgency=medium
 .
   * New Maintainer (Closes: #754473).
   * New upstream release (Closes: #668244).
 - Remove nonfree items from source (Closes: #753833):
   + doc/rfc3513.htm.
   + doc/rfc3986.htm.
   + doc/rfc3986_grammar_only.txt.
   + Remove debian/prune-tarball.sh.
   + Remove debian/README.Debian-source.
   * debian/control:
 - Set myself as maintainer.
 - Bump Standards-Version to 3.9.5 (no changes required).
 - Update Build-Depends:
   + Add dh-autoreconf for update Build Environment (Closes: #727517).
 - Change description of liburiparser1  (Closes: #552993).
 - For previously not existing Vcs
   + Create a new git repository on alioth.
   + Add the Fields Vcs-Browser and Vcs-Git.
   * Change debian/compat to 9 (no changes required).
   * Add debian/source/options:
 - Set compression to xz & compression-level to 9 to save space.
   * debian/copyright:
 - Rewrite into machine-readable format.
 - Add myself to the list of authors for debian/*.
 - Update copyright years for 2014.
Checksums-Sha1:
 681d2420857cc9020343f1cd742e47aa6c1e32d6 1950 uriparser_0.8.0.1-1.dsc
 53b16dd0640fda006ba4f9d750fec7e7c58836a9 337905 uriparser_0.8.0.1.orig.tar.bz2
 84d76284e3c925c9c30fb786401b379f79b389cf 4652 uriparser_0.8.0.1-1.debian.tar.xz
 decde82449b00f515181062448e7691aaf4ea97e 40932 
liburiparser1_0.8.0.1-1_amd64.deb
 3f8857ae763e4a7a2a4a78c7895616753e66b12e 15388 
liburiparser-d

Bug#751311: marked as done (gcc-arm-none-eabi: non-standard gcc/g++ used for build (gcc-4.8))

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 21:50:10 +
with message-id 
and subject line Bug#751311: fixed in gcc-arm-none-eabi 10
has caused the Debian Bug report #751311,
regarding gcc-arm-none-eabi: non-standard gcc/g++ used for build (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.)


-- 
751311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-arm-none-eabi
Version: 8
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.7-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.7 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: gcc-arm-none-eabi
Source-Version: 10

We believe that the bug you reported is fixed in the latest version of
gcc-arm-none-eabi, 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 751...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Agustin Henze  (supplier of updated gcc-arm-none-eabi 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: SHA512

Format: 1.8
Date: Wed, 06 Aug 2014 17:15:42 -0300
Source: gcc-arm-none-eabi
Binary: gcc-arm-none-eabi
Architecture: source amd64
Version: 10
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Agustin Henze 
Description:
 gcc-arm-none-eabi - GCC cross compiler for ARM Cortex-A/R/M processors
Closes: 751311
Changes:
 gcc-arm-none-eabi (10) unstable; urgency=medium
 .
   * Rebuilt using current gcc (Closes: #751311)
Checksums-Sha1:
 5d3a8096e8f7d25f4a4573119736cb3c97252d6b 1927 gcc-arm-none-eabi_10.dsc
 88a8b6ca3f8bfbacd1280f89b7c142550aff96f9 8943 gcc-arm-none-eabi_10.tar.gz
 639e85cf77eecd9e0d9483a90cb1744dea749f87 14954098 
gcc-arm-none-eabi_4.8.3-7+10_amd64.deb
Checksums-Sha256:
 bd59e30c8c04fcbe8cb2131e8646918d8446eb708ca4404f8b981ef113c6eef0 1927 
gcc-arm-none-eabi_10.dsc
 5f3f343162c458bece71b0b2fbd3c8ec7a48ba1709c2754e1ddcce2b9de18568 8943 
gcc-arm-none-eabi_10.tar.gz
 69bc74632ee69d2f28afca5b55db8afba93bc818704e6a787cbb0f1aba28953b 14954098 
gcc-arm-none-eabi_4.8.3-7+10_amd64.deb
Files:
 59da91ecf51aa79a85955cf678449e02 14954098 devel extra 
gcc-arm-none-eabi_4.8.3-7+10_amd64.deb
 5f563a3ef119bf7a574a7cd3b57c0aef 1927 devel extra gcc-arm-none-eabi_10.dsc
 994388df72df357a1792641a95cc9490 8943 devel extra gcc-arm-none-eabi_10.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJT4pF2AAoJEAIoUhB4kDjyb/IQAK/zNzajNKaaXydJccD6+fSy
W3QCd0anyDgGAxqVD66x6ebMl87LQ98MEsSA05DuQ13puSqsBshhorgpN0GOVlPS
emJIWWUVthxkzt/zvfyJV6ek+h0RA4VIOimMfoHvGXDMIQbqu2+hBptJ8Ztdke3U
58Nbrycz+PR3EPZIRQdJ9CkXF+R1uYx+X4VPQxJGiPpyFxSp6goialKTMqRgh93F
qxRL66Wmzk0kweYFL0CvKCKJwri6Epf3VnHTuQ24Kk28w6SdlpavmpRjklUq9sjY
iIp6Txuyl9fVRcsekEWjzgMI+VTmjQalJKYihhArPhMtVTjuw5c/Osx5QsUed3Bq
O9CmEWCXSZbRXcIV2VnjJT4lrZW/d6yOF38uQsICTqONIfAha48LUiK/ilAP2sd/
306SJdUrX5fpVE0jhA4HLTFh9nxAzygju6TCdbIKgqsJkKZ823dvbx9zq7vMWbeL
eMtDNq6LxjpbkfDFdd1mhxuZxbCZnDaDoUaTP2+qBtlPT2XiZnbBM+fuRPOALgUe
NWvEGIxUNw1zGuYBDHdvsPslMUjxGEma8f+NDZeRq/Nj0W68+R/aBweBPHIdXUfv
VmSwGzgx2k7r/E75PUBQ4IwR+D0P3HWtqlwncN3+fxpaALvFu7Gp5uERC0fzvETJ
ipqgwQeCxGjWXciUI3h+
=ipg8
-END PGP SIGNATURE End Message ---

Bug#754237: RFC: disable SCTP in Debian's kFreeBSD?

[Moritz Mühlenhoff]

On Wed, Jul 09, 2014 at 01:26:22AM +0100, Steven Chamberlain wrote:
> Hi,
> So I'm obviously asking here - could we just drop SCTP from the default
> kernel config?  In jessie/sid?  Even in wheezy-security?

We can certainly do this for wheezy-security if the kfreebsd maintainers
think it's the best course of action.

Cheers,
Moritz


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

Bug#755814: kde4libs: CVE-2014-5033

[Moritz Mühlenhoff]

On Thu, Jul 31, 2014 at 09:07:22PM +0200, Felix Geyer wrote:
> Hi Moritz,
> 
> On Wed, 23 Jul 2014 16:05:25 +0200 Moritz Muehlenhoff  wrote:
> > Package: kde4libs
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> > 
> > Hi,
> > please see https://bugzilla.novell.com/show_bug.cgi?id=864716 for the 
> > original
> > bug report. The upstream fix is available here:
> > http://quickgit.kde.org/?p=kdelibs.git&a=commit&h=e4e7b53b71e2659adaf52691d4accc3594203b23
> > 
> > We should also fix this in Wheezy.
> 
> Attached is a debdiff that adds the upstream patch to kde4libs/wheezy.
> I've tested that kauth still works (e.g. changing the display manager setting 
> in system settings).
> Please let me know if I can go ahead and upload it to the security archive.

Please build with "-sa" (since this is the first wheezy security update for
kde4libs) and upload to security-master.

I'm mostly offline until next week, if noone gets to it earlier, I'll
deal with it in a week.

Thanks,
Moritz


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

Bug#757280: bino: FTBFS: gettext infrastructure mismatch

[Andreas Cadhalpun]

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 AmigaOS, at least up
+-  # to version 4, is to share data among multiple programs linked
+-  # with the same dynamic library.  Since this doesn't match the
+-  # behavior of shared libraries on other platforms, we cannot use
+-  # them.
+-  ld_shlibs=no
++  case "$host_cpu" in
++powerpc)
++  ;;
++m68k)
++  hardcode_libdir_flag_spec='-L$libdir'
++  hardcode_minus_L=yes
++  ;;
++  esac
+   ;;
+ beos*)
+   if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
+@@ -198,11 +208,13 @@ if test "$with_gnu_ld" = yes; then
+ ld_shlibs=no
+   fi
+   ;;
++haiku*)
++  ;;
+ interix[3-9]*)
+   hardcode_direct=no
+   hardcode_libdir_flag_spec='${wl}-rpath,$libdir'
+  

Bug#736426: freehep-graphicsio-svg: Recompilation of the package breaks other packages

[Giovanni Mascellani]

Hi.

Il 06/08/2014 00:06, Emmanuel Bourg ha scritto:
> Le 05/08/2014 23:55, Giovanni Mascellani a écrit :
> 
>> For what it's worth, I'm inclined to think that the fix to #688043
>> should be ported to stable and then the affected packages should be
>> rebuilt. But this is a decision that competes to maven-debian-helper
>> maintainers.
> 
> I haven't studied this issue precisely, but would a backport of
> maven-debian-helper/1.6.8 to unstable help?

The patch in [1] is enough (I just tried in a stable chroot).

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

There should be no reason to rebuilt freehep-graphicsio-svg, because the
binary package is already ok (the problem is triggered when
_rebuiliding_ the binary package, but the one currently in stable is ok;
I don't know why the first compilation was ok, but it is good that it
was). I don't know whether some other package have to be rebuilt.

Probably the Stable Release Managers should be contacted in order to
understand whether they are interested in this upload. I can do it if
maven-debian-helper's maintainers are ok.

Thanks, Gio.
-- 
Giovanni Mascellani 
PhD Student - Scuola Normale Superiore, Pisa, Italy

http://poisson.phc.unipi.it/~mascellani



signature.asc
Description: OpenPGP digital signature

Bug#757269: slic3r fails to run on sid

[Bdale Garbee]

Package: slic3r
version: 1.1.7+dfsg-1
Severity: serious

On an up-to-date system running sid:

bdale@rover:~$ slic3r
Running Slic3r under Perl >= 5.16 is not supported nor recommended
Can't locate object method "new" via package "Slic3r::Model" at 
/usr/share/perl5/Slic3r/GUI/Plater.pm line 53.
bdale@rover:~$ 

Bdale


pgpDgSaOwIMpm.pgp
Description: PGP signature

Processed: Re: Bug#757076: unionfs-fuse: "library too old, some operations may not not work", writing does not work

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #757076 [unionfs-fuse] unionfs-fuse: "library too old, some operations may 
not not work", writing does not work
Severity set to 'normal' from 'grave'

-- 
757076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757076
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#757076: unionfs-fuse: "library too old, some operations may not not work", writing does not work

[Frank Heckenbach]

Control: severity -1 normal

> > # mkdir 1 2 3
> > # unionfs-fuse 1:2 3
> > fuse: warning: library too old, some operations may not not work
> >
> > According to the dependencies it requires libfuse2 >= 2.8.1.
> > I have 2.9.0-2 installed, so how can it be too old?
> >
> > But indeed "some" operations don't work. In particular writing
> > doesn't seem to work at all (with or without "-o cow"), which
> > renders the whole thing quite useless:
> >
> > # touch 3/foo
> > touch: cannot touch `3/foo': Permission denied

> Any chance you could try to re-compile to libfuse package?

No difference.

> And if that
> shouldn't help to recompile unionfs-fuse?

This made the "too old" warning disappear. Though I'm confused, does
this mean the binary on the Debian servers was built wrongly? Don't
they use automated scripts to build them? Anyway, I suppose this
would be fixed if they rebuild the package now!?

The main problem (writing doesn't work) was a misunderstanding. It
works with "1=rw", or "2=rw" and "-o cow". (Also with the original
version, despite the warning.)

I only realized this when, after building it, I found the "test.sh"
script and wondered why it did work

Note that the only mention of "rw" (and "ro") in the man page is
under examples, not in the main description which just says:

  top_branch:lower_branch:...:lowest_branch

I suggest writing something like this to prevent such
misunderstandings:

  top_branch[=ro|rw]:lower_branch[=ro|rw]:...:lowest_branch[=ro|rw]

Frank


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

Bug#755361: saga: FTBFS on arm*: undefined reference to `wxCommandEvent::Clone() const'

[Johan Van de Wauw]

As mentioned on the list I think this issue is due to a bug in gcc/wxwidgets.

https://lists.debian.org/debian-gis/2014/08/msg00011.html

As a workaround I will try building saga on arm/armel without gui
support for now.


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

Bug#754811: marked as done (taurus 3.3.0 brakes sardana)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 17:48:39 +
with message-id 
and subject line Bug#754811: fixed in taurus 3.3.0+dfsg-2
has caused the Debian Bug report #754811,
regarding taurus 3.3.0 brakes sardana
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.)


-- 
754811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-taurus
Version: 3.3.0+dfsg-1
Severity: serious

prevent the migration of taurus into testing.

this new version of taurus does not provide the sardana dedicated
widgets, macroexecutor etc...

To avoid regression for user, it is better to stop the migration of taurus
until a new version of sardana is released with these widgets.



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

Kernel: Linux 3.14-1-486
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-taurus depends on:
ii  python2.7.8-1
ii  python-guiqwt 2.3.1-1
ii  python-h5py   2.2.1-1+b2
ii  python-lxml   3.3.5-1+b1
ii  python-numpy  1:1.8.1-1+b1
ii  python-ply3.4-3
ii  python-pytango8.1.1-1+b3
ii  python-qt44.11.1+dfsg-1
ii  python-qwt5-qt4   5.2.1~cvs20091107+dfsg-7+b2
ii  python-spyderlib  2.3.0~rc+dfsg-1~experimental2

Versions of packages python-taurus recommends:
ii  pymca 4.7.1+dfsg-2
ii  qt4-designer  4:4.8.6+dfsg-2

python-taurus suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: taurus
Source-Version: 3.3.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
taurus, 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 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated taurus 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: Wed, 06 Aug 2014 10:17:19 +0200
Source: taurus
Binary: python-taurus python-taurus-doc
Architecture: source all
Version: 3.3.0+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description: 
 python-taurus - framework for Tango Control System CLI and GUI applications.
 python-taurus-doc - framework for Tango Control System CLI and GUI 
applications.
Closes: 754811
Changes: 
 taurus (3.3.0+dfsg-2) unstable; urgency=low
 .
   * debian/control
 - Add Breaks python-sardana (<< 1.4.0-1~) (Closes: #754811)
Checksums-Sha1: 
 bd2b8d777492070792923114e65b138c44b68bac 1479 taurus_3.3.0+dfsg-2.dsc
 0fd24cf80e67c4820806cbe6b7c0de76631967d2 16856 
taurus_3.3.0+dfsg-2.debian.tar.xz
 48ed8f71b32763580be08a933bbeb79cce6f2484 9183926 
python-taurus_3.3.0+dfsg-2_all.deb
 38b4837e513f2b2aebc495261acf74c26e4bd254 7843526 
python-taurus-doc_3.3.0+dfsg-2_all.deb
Checksums-Sha256: 
 0b39f049f7520a6a44aa10501a7985a5ae7cb249b6b3833ca916a8dc4585aa83 1479 
taurus_3.3.0+dfsg-2.dsc
 bc88a91cd11f80a302f728fe9e7272b55f7ba4068fc793dace2452eb06da54b6 16856 
taurus_3.3.0+dfsg-2.debian.tar.xz
 d9c1efac4ad1ec0fafea095ef77a6461bce4a89f6891d55d947dd088c4750564 9183926 
python-taurus_3.3.0+dfsg-2_all.deb
 26fc86fcdd1020508b233dac7f66b3f5cfc5e50673471e390169946014ae5ce7 7843526 
python-taurus-doc_3.3.0+dfsg-2_all.deb
Files: 
 be7bb91dd6c00ebf697b653cbeb8c630 1479 science extra taurus_3.3.0+dfsg-2.dsc
 e654d6cba4faeafbf6c0b12e1efe91f7 16856 science extra 
taurus_3.3.0+dfsg-2.debian.tar.xz
 5c54b1ea921427959bc6c54249bb5d66 9183926 python extra 
python-taurus_3.3.0+dfsg-2_all.deb
 0120c01d2f59d5bdd11962210ec93d71 7843526 doc extra 
python-taurus-doc_3.3.0+dfsg-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlPiaRMACgkQtqm6aqWbEXHKZgCdGvxIWiLHVNj3t9zox8A1hDgo
tH0AnR4Ypr6JJxZMVofb9S6BPMaVFmI2
=Uz0T
-END PGP SIGNATURE End Message ---

Bug#752804: marked as done (owfs: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 17:00:08 +
with message-id 
and subject line Bug#752804: fixed in owfs 2.9p5-1
has caused the Debian Bug report #752804,
regarding owfs: hardcodes /usr/lib/perl5
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.)


-- 
752804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: owfs
Version: 2.8p15-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

  dh_install: libow-perl missing files (usr/lib/perl*/OW.pm), aborting
  make[1]: *** [override_dh_install] Error 255
  debian/rules:72: recipe for target 'override_dh_install' failed
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  make: *** [binary-arch] Error 2

One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: owfs
Source-Version: 2.9p5-1

We believe that the bug you reported is fixed in the latest version of
owfs, 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 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Danjean  (supplier of updated owfs 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, 07 Jul 2014 13:27:43 +0200
Source: owfs
Binary: owfs-common owfs libow-2.9-5 libowcapi-2.9-5 libow-dev libownet-2.9-5 
libownet-dev owserver ow-shell ow-tools owfs-fuse owhttpd owftpd libow-php5 
libownet-php libow-perl libownet-perl python-ow python-ownet libow-tcl owfs-doc 
owfs-dbg
Architecture: all amd64 source
Version: 2.9p5-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean 
Changed-By: Vincent Danjean 
Closes: 646764 698180 737400 752804
Description: 
 libow-2.9-5 - 1-Wire File System full library
 libowcapi-2.9-5 - 1-Wire File System C library
 libow-dev  - 1-Wire File System (development files)
 libownet-2.9-5 - owserver protocol library
 libownet-dev - owserver protocol library (development files)
 libownet-perl - Perl module for accessing 1-wire networks
 libownet-php - Dallas 1-wire support: PHP OWNet library
 libow-perl - Dallas 1-wire support: Perl5 bindings
 libow-php5 - Dallas 1-wire support: PHP5 bindings
 libow-tcl  - Dallas 1-wire support: Tcl bindings
 owfs-common - common files used by any of the OWFS programs
 owfs   - Dallas 1-wire support
 owfs-dbg   - Debugging symbols for the OWFS packages
 owfs-doc   - Dallas 1-wire support: Documentation for owfs
 owfs-fuse  - 1-Wire filesystem
 owftpd - FTP daemon providing access to 1-Wire networks
 owhttpd- HTTP daemon providing access to 1-Wire networks
 owserver   - Backend server for 1-Wire control
 ow-shell   - shell utilities to talk to an 1-Wire owserver
 ow-tools   - tools to monitor or inspect a ow-server link
 python-ow  - Dallas 1-wire support: Python bindings
 python-ownet - Python module for accessing 1-wire networks
Changes:
 owfs (2.9p5-1) unstable; urgency=medium
 .
   * New upstream release
   * Fix "hardcodes /usr/lib/perl5":
 make debian/libow-perl.install executable and use $Config{vendorarch}
 there (Closes: #752804)
 Thanks Gregor Herrmann  for the patch
 .
 owfs (2.9p1-2) unstable; urgency=medium
 .
   * move TclTk scripts to an arch-indep package (Closes: #737400)

Bug#756097: marked as done (FTBFS: sys/xattr.h:32:3: error: expected identifier before numeric constant)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 17:00:16 +
with message-id 
and subject line Bug#756097: fixed in systemd 208-7
has caused the Debian Bug report #756097,
regarding FTBFS: sys/xattr.h:32:3: error: expected identifier before numeric 
constant
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.)


-- 
756097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 208-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Using pbuilder updated today. Build stops at:
In file included from ../src/core/socket.c:32:0:
/usr/include/x86_64-linux-gnu/sys/xattr.h:32:3: error: expected identifier 
before numeric constant
   XATTR_CREATE = 1, /* set value, fail if attr already exists.  */
   ^
Makefile:9750: recipe for target 'src/core/libsystemd_core_la-socket.lo' failed
make[4]: *** [src/core/libsystemd_core_la-socket.lo] Error 1
Makefile:12641: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
Makefile:6433: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/tmp/buildd/systemd-208/build-deb'
dh_auto_build: make -j1 returned exit code 2
debian/rules:67: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/systemd-208'
debian/rules:221: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /source/pbuilder/build//29239 and its subdirectories
pdebuild  78,76s user 18,80s system 32% cpu 5:04,16 total



-- Package-specific info:

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

Kernel: Linux 3.16.0-rc6-pipin-lxtec-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl  2.2.52-1
ii  adduser  3.113+nmu3
ii  initscripts  2.88dsf-53.2
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.7-1
ii  libblkid12.20.1-5.8
ii  libc62.19-7
ii  libcap2  1:2.24-2
ii  libcap2-bin  1:2.24-2
ii  libcryptsetup4   2:1.6.4-4
ii  libdbus-1-3  1.8.6-1
ii  libgcrypt11  1.5.3-4
ii  libkmod2 18-1
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.8-3
ii  libselinux1  2.3-1
ii  libsystemd-daemon0   208-6
ii  libsystemd-journal0  208-6
ii  libsystemd-login0208-6
ii  libudev1 208-6
ii  libwrap0 7.6.q-25
ii  sysv-rc  2.88dsf-53.2
ii  udev 208-6
ii  util-linux   2.20.1-5.8

Versions of packages systemd recommends:
ii  libpam-systemd  208-6

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information
0 overridden configuration files found.
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service

==> /var/lib/systemd/deb-systemd-helper-enabled/ModemManager.service.dsh-also 
<==
/etc/systemd/system/multi-user.target.wants/ModemManager.service
/etc/systemd/system/dbus-org.freedesktop.ModemManager1.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation-early.service.dsh-also
 <==
/etc/systemd/system/local-fs.target.wants/lvm2-activation-early.service

==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==

==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cron.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also <==
/etc/systemd/system/local-fs.target.wants/lvm2-activation.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmetad.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/lvm2-lvmetad.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh

Bug#753589: marked as done (systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 17:00:16 +
with message-id 
and subject line Bug#753589: fixed in systemd 208-7
has caused the Debian Bug report #753589,
regarding systemd: needs Pre-Depends for transitively Essential functionality 
of systemd-sysv
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.)


-- 
753589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 208-5
Severity: normal

While updating, systemd was updated before glibc.

Needless to say, this does not work at all.

# aptitude(wd: ~)
Reading changelogs...
apt-listchanges: Mailing smurf-chan...@smurf.noris.de: apt-listchanges: news 
for eltern
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 59720 files and directories currently installed.)
Removing homevent ...
Stopping homevent: Removing python-twisted-conch ...
Removing python-twisted-core ...
Removing python-zope.interface ...
Removing python-pkg-resources ...
Removing debconf-i18n ...
Removing fuse-utils ...
Processing triggers for man-db ...
(Reading database ... 57308 files and directories currently installed.)
Preparing to replace systemd-sysv 44-11+deb7u4 (using 
.../systemd-sysv_208-5_i386.deb) ...
Unpacking replacement systemd-sysv ...
Preparing to replace libtirpc1:i386 0.2.2-5 (using 
.../libtirpc1_0.2.3-1_i386.deb) ...
Unpacking replacement libtirpc1:i386 ...
Preparing to replace libgcrypt11:i386 1.5.0-5+deb7u1 (using 
.../libgcrypt11_1.5.3-4_i386.deb) ...
Unpacking replacement libgcrypt11:i386 ...
Preparing to replace libsystemd-daemon0:i386 204-8 (using 
.../libsystemd-daemon0_208-5_i386.deb) ...
Unpacking replacement libsystemd-daemon0:i386 ...
Preparing to replace libsystemd-journal0:i386 44-11+deb7u4 (using 
.../libsystemd-journal0_208-5_i386.deb) ...
Unpacking replacement libsystemd-journal0:i386 ...
Selecting previously unselected package libudev1:i386.
Unpacking libudev1:i386 (from .../libudev1_204-8_i386.deb) ...
Preparing to replace libsystemd-login0:i386 44-11+deb7u4 (using 
.../libsystemd-login0_208-5_i386.deb) ...
Unpacking replacement libsystemd-login0:i386 ...
Selecting previously unselected package acl.
Unpacking acl (from .../archives/acl_2.2.52-1_i386.deb) ...
Preparing to replace libpam-systemd:i386 44-11+deb7u4 (using 
.../libpam-systemd_208-5_i386.deb) ...
Unpacking replacement libpam-systemd:i386 ...
Preparing to replace systemd 44-11+deb7u4 (using .../systemd_208-5_i386.deb) ...
Moving obsolete conffile /etc/bash_completion.d/systemd-bash-completion.sh out 
of the way...
Unpacking replacement systemd ...
Processing triggers for man-db ...
(Reading database ... 57471 files and directories currently installed.)
Removing libaudit0 ...
Selecting previously unselected package libaudit-common.
(Reading database ... 57465 files and directories currently installed.)
Unpacking libaudit-common (from .../libaudit-common_1%3a2.3.7-1_all.deb) ...
Selecting previously unselected package libaudit1:i386.
Unpacking libaudit1:i386 (from .../libaudit1_1%3a2.3.7-1_i386.deb) ...
Preparing to replace nscd 2.13-38+deb7u1 (using 
.../archives/nscd_2.19-4_i386.deb) ...
/sbin/runlevel: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.17' 
not found (required by /sbin/runlevel)
/sbin/runlevel: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.14' 
not found (required by /sbin/runlevel)
/sbin/runlevel: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' 
not found (required by /lib/i386-linux-gnu/libgcrypt.so.11)


-- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.6-trunk-486
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 systemd depends on:
ii  acl  2.2.52-1
ii  adduser  3.113+nmu3
ii  initscripts  2.88dsf-41+deb7u1
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.7-1
ii  libblkid12.20.1-5.3
ii  libc62.19-4
ii  libcap2  1:2.22-1.2
ii  libcap2-bin  1:2.22-1.2
ii  libcryptsetup4   2:1.4.3-4
ii  libdbus-1-3  1.6.8-1+deb7u1
iu  libgcrypt11  1.5.3-4
ii  libkmod2 9-3
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-9
ii  libselinux1  2.1.9-5
ii  libsystemd-daemon0   208-5
iu  libsystemd-journal0  208-5
ii  libsystemd-login0208-5
i

Bug#753957: marked as done (ahven-dbg: not installable in sid)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 17:00:06 +
with message-id 
and subject line Bug#753957: fixed in ahven 2.4+repack-1
has caused the Debian Bug report #753957,
regarding ahven-dbg: not installable in sid
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.)


-- 
753957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libahven3-dev
Version: 2.1-4
Severity: grave
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

libahven3-dev is not installable in sid, at least since 2014-05-02. 
The reason is that it depends both on gnat and gnat-4.6.
However, gnat depends on gnat-4.9 which is in Conflict with gnat-4.6.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: ahven
Source-Version: 2.4+repack-1

We believe that the bug you reported is fixed in the latest version of
ahven, 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 753...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reto Buerki  (supplier of updated ahven 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: Mon, 04 Aug 2014 22:52:09 +0200
Source: ahven
Binary: libahven24.0 libahven4-dev ahven-dbg
Architecture: source amd64
Version: 2.4+repack-1
Distribution: unstable
Urgency: medium
Maintainer: Reto Buerki 
Changed-By: Reto Buerki 
Description:
 ahven-dbg  - Unit test library for Ada (debug)
 libahven24.0 - Unit test library for Ada
 libahven4-dev - Unit test library for Ada (development)
Closes: 753957 755010
Changes:
 ahven (2.4+repack-1) unstable; urgency=medium
 .
   * Imported Upstream version 2.4
   * Strip pre-built manual
   * Remove obsolete DM-Upload-Allowed from debian/control
   * Update binary package names
   * Transition to gnat-4.9 compiler (Closes: #753957, #755010)
   * Update to Standards-Version 3.9.5
   * Enable dpkg-buildflags hardening options
   * Update library kind support patch
   * New patch 0002-Fix-misplaced-then-warnings-style.patch
   * Update debian/copyright
   * Remove pre-built manual files from debian/copyright
Checksums-Sha1:
 52ad5d7192143f3aa6c81a557ba7a75abea402f6 1991 ahven_2.4+repack-1.dsc
 1ae18e6dc45288d006f5118a043c142c14929fd7 94824 ahven_2.4+repack.orig.tar.bz2
 0c6b5d275c8f13fd27c0ffbfe7e39d41d937725e 6352 ahven_2.4+repack-1.debian.tar.xz
 7263a47e0191d1a960054d38a629b5db5d6dbab4 64404 
libahven24.0_2.4+repack-1_amd64.deb
 d9046b639715569802632558eaf57e2c10e02445 121956 
libahven4-dev_2.4+repack-1_amd64.deb
 62ab55c6fbc5f7e4fbbf4a3f473e6d1c82f77cf9 101038 
ahven-dbg_2.4+repack-1_amd64.deb
Checksums-Sha256:
 fcc486211f42d71aca009caabc59e477b602ece840214f64322eb49cf4166082 1991 
ahven_2.4+repack-1.dsc
 51e9a8f0f97859280e740d92c928f16018afbdb3566f076d9a5e77dd76de3d29 94824 
ahven_2.4+repack.orig.tar.bz2
 e3d255697385613e7e8c1e2b3d97a2b6feb2f49f1d10c318d97985578990a82b 6352 
ahven_2.4+repack-1.debian.tar.xz
 a4f161333cb90bfb513b11e66dc8d70dbc90c34264ed3e455f7ff9677dc22dd5 64404 
libahven24.0_2.4+repack-1_amd64.deb
 d1d7d968e4ae981531683f8cb4623cb9e78dc0c05474da4263be64caf2713308 121956 
libahven4-dev_2.4+repack-1_amd64.deb
 652ef9c44cf032531e9c18e2dcae536b85a8fa9b12925a5fbd8815771432699d 101038 
ahven-dbg_2.4+repack-1_amd64.deb
Files:
 79f2acc0bc427c1df5f05c968968a3b1 64404 libs optional 
libahven24.0_2.4+repack-1_amd64.deb
 7d42c7a4dd8d81073a6140e532265aaa 121956 libdevel optional 
libahven4-dev_2.4+repack-1_amd64.deb
 70c7fdfe9b7d1f6f926ea56d981dffa4 101038 debug extra 
ahven-dbg_2.4+repack-1_amd64.deb
 ec9bc7dc87fea53f62ce7e0c0e46 1991 libs optional ahven_2.4+repack-1.dsc
 a8758e06a28f8be1c3e8b3a9f926f4ea 94824 libs optional 
ahven_2.4+repack.orig.tar.bz2
 5a6b025c3ad12dc01cfa236da4b8cc46 6352 libs optional 
ahven_2.4+repack-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJT4S7ZAAoJENPhc4PPp/8GKNgP/iG/SoJSf4E3zNgVzLX9/m5J
kZ/Fqm6cHwF7+gcsWHOkufM1fIhTGSNwjivjxm+qn3+T9+Y+ImRKk407FYiMB20B
RDubx/dY+W2sA9kdEk9afXpeSVAZOcT7z6A0LOpS7cmQHUjqmSoLDaW2dEDuSkV1
v1SpQ2oJN8Qr9B79wM0DWd3bDT9XLJNs807m61BjgaXPVLXEmkEJSQz0+KRH2yld
XatBT7wNChBTdYdgDugem+CAAJOCQgM69oi0VontAbpzZGcV6hOz4EFCrVRrY0Lw
0nfELb8jJkeAfF

Bug#746915: marked as done (sslsniff: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 16:20:13 +
with message-id 
and subject line Bug#746915: fixed in sslsniff 0.8-4.2
has caused the Debian Bug report #746915,
regarding sslsniff: ftbfs with GCC-4.9
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.)


-- 
746915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sslsniff
Version: 0.8-4.1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/sslsniff_0.8-4.1_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols
files.  For other C/C++ related build failures see the porting guide
at http://gcc.gnu.org/gcc-4.9/porting_to.html

[...]
# Add here commands to compile the package.
/usr/bin/make
make[1]: Entering directory `/«PKGBUILDDIR»'
g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"sslsniff\" -DVERSION=\"0.8\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -I.  
  -ggdb -g -O2 -MT SSLConnectionManager.o -MD -MP -MF 
.deps/SSLConnectionManager.Tpo -c -o SSLConnectionManager.o 
SSLConnectionManager.cpp
In file included from SSLBridge.hpp:41:0,
 from HTTPSBridge.hpp:24,
 from FirefoxUpdater.hpp:23,
 from FirefoxAddonUpdater.hpp:26,
 from SSLConnectionManager.cpp:20:
certificate/Certificate.hpp: In member function 'std::string 
Certificate::parseNameFromOCSPUrl(std::string&)':
certificate/Certificate.hpp:60:37: warning: overflow in implicit constant 
conversion [-Woverflow]
 else  forwardSlash  = std::string::npos;
 ^
SSLConnectionManager.cpp: In member function 'void 
SSLConnectionManager::interceptUpdate(boost::shared_ptr
 >, boost::asio::ip::tcp::endpoint&, bool)':
SSLConnectionManager.cpp:98:17: error: redeclaration of 'std::string error' 
[-fpermissive]
 std::string error = errorStream.str();
 ^
SSLConnectionManager.cpp:95:32: note: 'SSLConnectionError& error' previously 
declared here
   } catch (SSLConnectionError &error) {
^
SSLConnectionManager.cpp:103:17: error: redeclaration of 'std::string error' 
[-fpermissive]
 std::string error = errorStream.str();
 ^
SSLConnectionManager.cpp:100:36: note: 'FirefoxUpdateException& error' 
previously declared here
   } catch (FirefoxUpdateException &error) {
^
SSLConnectionManager.cpp: In member function 'void 
SSLConnectionManager::interceptAddon(boost::shared_ptr
 >, boost::asio::ip::tcp::endpoint&, bool)':
SSLConnectionManager.cpp:123:17: error: redeclaration of 'std::string error' 
[-fpermissive]
 std::string error = errorStream.str();
 ^
SSLConnectionManager.cpp:120:32: note: 'SSLConnectionError& error' previously 
declared here
   } catch (SSLConnectionError &error) {
^
SSLConnectionManager.cpp:128:17: error: redeclaration of 'std::string error' 
[-fpermissive]
 std::string error = errorStream.str();
 ^
SSLConnectionManager.cpp:125:36: note: 'FirefoxUpdateException& error' 
previously declared here
   } catch (FirefoxUpdateException &error) {
^
SSLConnectionManager.cpp: In member function 'void 
SSLConnectionManager::interceptSSL(boost::shared_ptr
 >, boost::asio::ip::tcp::endpoint&, bool)':
SSLConnectionManager.cpp:154:19: error: redeclaration of 'std::string error' 
[-fpermissive]
   std::string error = errorStream.str();
   ^
SSLConnectionManager.cpp:151:34: note: 'SSLConnectionError& error' previously 
declared here
 } catch (SSLConnectionError &error) {
 

Bug#746915: sslsniff: diff for NMU version 0.8-4.2

[Raphael Hertzog]

tags 746915 + patch
tags 746915 + pending
thanks

Hi,

I've uploaded an NMU for sslsniff (versioned as 0.8-4.2).
Please find the patch attached.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
diff -Nru sslsniff-0.8/debian/changelog sslsniff-0.8/debian/changelog
--- sslsniff-0.8/debian/changelog	2013-08-12 22:50:12.0 +0200
+++ sslsniff-0.8/debian/changelog	2014-08-06 17:38:40.0 +0200
@@ -1,3 +1,11 @@
+sslsniff (0.8-4.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add debian/patches/02-fix-compatibility-with-gcc49.patch
+to fix FTFBS with gcc-4.9 (Closes: #746915)
+
+ -- Sophie Brun   Wed, 06 Aug 2014 17:06:53 +0200
+
 sslsniff (0.8-4.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru sslsniff-0.8/debian/patches/02-fix-compatibility-with-gcc49.patch sslsniff-0.8/debian/patches/02-fix-compatibility-with-gcc49.patch
--- sslsniff-0.8/debian/patches/02-fix-compatibility-with-gcc49.patch	1970-01-01 01:00:00.0 +0100
+++ sslsniff-0.8/debian/patches/02-fix-compatibility-with-gcc49.patch	2014-08-06 17:46:18.0 +0200
@@ -0,0 +1,59 @@
+Description: Fix failure to build with GCC 4.9
+ gcc-4.9 doesn't like the conflict between two variables named
+ "error", so rename one of them to avoid the conflict.
+Author: Sophie Brun 
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746915
+Last-Update: 2014-08-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/SSLConnectionManager.cpp
 b/SSLConnectionManager.cpp
+@@ -95,13 +95,13 @@ void SSLConnectionManager::interceptUpda
+   } catch (SSLConnectionError &error) {
+ std::stringstream errorStream;
+ errorStream << "Got exception: " << error.what();
+-std::string error = errorStream.str();
+-Logger::logError(error);
++std::string errortext = errorStream.str();
++Logger::logError(errortext);
+   } catch (FirefoxUpdateException &error) {
+ std::stringstream errorStream;
+ errorStream << "Got exception: " << error.what();
+-std::string error = errorStream.str();
+-Logger::logError(error);
++std::string errortext = errorStream.str();
++Logger::logError(errortext);
+   }
+ }
+ 
+@@ -120,13 +120,13 @@ void SSLConnectionManager::interceptAddo
+   } catch (SSLConnectionError &error) {
+ std::stringstream errorStream;
+ errorStream << "Got exception: " << error.what();
+-std::string error = errorStream.str();
+-Logger::logError(error);
++std::string errortext = errorStream.str();
++Logger::logError(errortext);
+   } catch (FirefoxUpdateException &error) {
+ std::stringstream errorStream;
+ errorStream << "Got exception: " << error.what();
+-std::string error = errorStream.str();
+-Logger::logError(error);
++std::string errortext = errorStream.str();
++Logger::logError(errortext);
+   }
+ }
+ 
+@@ -151,9 +151,9 @@ void SSLConnectionManager::interceptSSL(
+ } catch (SSLConnectionError &error) {
+   std::stringstream errorStream;
+   errorStream << "Got exception: " << error.what();
+-  std::string error = errorStream.str();
++  std::string errortext = errorStream.str();
+ 
+-  Logger::logError(error);
++  Logger::logError(errortext);
+ }
+   }
+ }
diff -Nru sslsniff-0.8/debian/patches/series sslsniff-0.8/debian/patches/series
--- sslsniff-0.8/debian/patches/series	2012-01-03 09:35:15.0 +0100
+++ sslsniff-0.8/debian/patches/series	2014-08-06 17:38:40.0 +0200
@@ -1 +1,2 @@
 01-fix-compatibility-with-boost-1.48.patch
+02-fix-compatibility-with-gcc49.patch

Processed: sslsniff: diff for NMU version 0.8-4.2

[Debian Bug Tracking System]

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

> tags 746915 + patch
Bug #746915 [src:sslsniff] sslsniff: ftbfs with GCC-4.9
Added tag(s) patch.
> tags 746915 + pending
Bug #746915 [src:sslsniff] sslsniff: ftbfs with GCC-4.9
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
746915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746915
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#739308: marked as done (libzip-dev: Include file in wrong place)

[Debian Bug Tracking System]

Your message dated Wed, 06 Aug 2014 15:51:00 +
with message-id 
and subject line Bug#739308: fixed in libzip 0.11.2-1.1
has caused the Debian Bug report #739308,
regarding libzip-dev: Include file in wrong place
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.)


-- 
739308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libzip-dev
Version: 0.11.2-1
Severity: serious

Dear Maintainer,

zipconf.h is in /usr/lib/i386-linux-gnu/libzip/include/

when the rigth place is (was the case in previous package 0.10.1-1.2)

/usr/include

Christian

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

Kernel: Linux 3.13.3 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libzip-dev depends on:
ii  libzip2 0.11.2-1
ii  zlib1g-dev  1:1.2.8.dfsg-1

libzip-dev recommends no packages.

libzip-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libzip
Source-Version: 0.11.2-1.1

We believe that the bug you reported is fixed in the latest version of
libzip, 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 739...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
libzip 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: Wed, 06 Aug 2014 15:38:27 +0200
Source: libzip
Binary: libzip-dev libzip2 zipcmp zipmerge ziptorrent
Architecture: source amd64
Version: 0.11.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Fathi Boudra 
Changed-By: John Paul Adrian Glaubitz 
Description:
 libzip-dev - library for reading, creating, and modifying zip archives (develo
 libzip2- library for reading, creating, and modifying zip archives (runtim
 zipcmp - compare contents of zip archives
 zipmerge   - merge zip archives
 ziptorrent - torrentzip zip archives
Closes: 739308
Changes:
 libzip (0.11.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Put a symlink to zipconf.h on the default search path, so that
 packages that do not use pkg-config to locate libzip will not FTBFS.
 Thanks to Simon McVittie (Closes: #739308).
Checksums-Sha1:
 1730fbdec6cfd547848236ec81063dcfa7149290 1912 libzip_0.11.2-1.1.dsc
 eeb3b5567fcf3532fa4bcb6440a87c7ad8507d2d 591913 libzip_0.11.2.orig.tar.gz
 d4cffd5fa7d6d16bd3e0fbbf0d4a37e185a17dec 4528 libzip_0.11.2-1.1.debian.tar.xz
 313bd85b1e133a123aee44cbb53ca697299068fa 89334 libzip-dev_0.11.2-1.1_amd64.deb
 2f3ee9495f7a0a58e79510531af52b96903df537 32058 libzip2_0.11.2-1.1_amd64.deb
 1c2319ebebaa953671aa877b8a6ab9afd5fcd3d5 9564 zipcmp_0.11.2-1.1_amd64.deb
 1dd38e11af5d175992f91605f9900f173c0e13fb 7912 zipmerge_0.11.2-1.1_amd64.deb
 97771b159a2d38578fec4b12be878f06cc6173f1 7036 ziptorrent_0.11.2-1.1_amd64.deb
Checksums-Sha256:
 3a1718cbe75d34fcc639ebf41a943708da262b5e25a56af1494a9d6bd2b93108 1912 
libzip_0.11.2-1.1.dsc
 83db1fb43a961ff7d1d1b50e1c6bea09c67e6af867686d1fc92ecb7dc6cf98d5 591913 
libzip_0.11.2.orig.tar.gz
 932aa5a72741bcc0d0b2d8437bbca0e7a3700e82d29ebbe81a42ba9a1f937597 4528 
libzip_0.11.2-1.1.debian.tar.xz
 1b1ae603b85d4b5231a349eae83f90f5540e9f25a1a4c9e4477e967933d32f14 89334 
libzip-dev_0.11.2-1.1_amd64.deb
 d6951bf5c4ef9b8d2bc482e32c46bb86245f7c6bbb45aa1661d4a3d5d25cf128 32058 
libzip2_0.11.2-1.1_amd64.deb
 0287c1a1b45d1dbcf2be31ba8ff49ae57c0acdea6c10390ef894732136db055c 9564 
zipcmp_0.11.2-1.1_amd64.deb
 0ff80544c261bee0ba1a12eb9deb784eb1b766bb1da8c836f0cb0f0d8e4ffa00 7912 
zipmerge_0.11.2-1.1_amd64.deb
 b8624a7c1edc65de6c2eaed52a00d4a2a16f0890398fe030fc669945acf32a4c 7036 
ziptorrent_0.11.2-1.1_amd64.deb
Files:
 7ec1108e7037e186df9fbb2619eafa24 89334 libdevel optional 
libzip-dev_0.11.2-1.1_amd64.deb
 05764f82c7ee11e0be491d6240ff00e0 32058 libs optional 
libzip2_0.11.2-1.1_amd64.deb
 67975b1b01f962061ee69c7e3da2b9d4 9564 utils optional 
zipcmp_0.11.2-1.1_amd64.deb
 0de917f611846dabea909f30ba76e073 7912 utils optional 
zip

Bug#756658: DB upgrade failed (owncloud 6 to 7 on debian sid) (#9893)

[blizzz]

do you still have the old table somewhere available? could you give us the 
structure before  the migration? The SQL command would be

```sql
DESCRIBE oc_ldap_user_mapping;
```

---
Reply to this email directly or view it on GitHub:
https://github.com/owncloud/core/issues/9893#issuecomment-51322625


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

Bug#744215: wvdial: Segmentation fault during modem initialization

[Raphael Hertzog]

Control: severity -1 important
Control: tag -1 + unreproducible moreinfo

Hello,

On Mon, 04 Aug 2014, m...@risca.eu wrote:
> I've currently using wvdial since many year on my system and it never ever
> occurs the error reported in this bug report.

Thank you for this information. It seems indeed that the severity of this
bug is overinflated. I'm downgrading it to important.

Thierry, as the wvdial maintainer, it's your responsibility to handle
bug reports and to ensure that the package remains in testing. Are
you still up to the task? If not, maybe you should consider orphaning
the package.

Daniel, if you are not able to provide some more specific information
of how to reproduce it and/or a full backtrace, I doubt that this bug can
be fixed. Upstream developers likely don't have access to sparc machines.

BTW Daniel, are you still having the problem? Can you reproduce it
on another architecture?

Thank you!
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


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

Processed: Re: wvdial: Segmentation fault during modem initialization

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #744215 [wvdial] wvdial: Segmentation fault during modem initialization
Severity set to 'important' from 'critical'
> tag -1 + unreproducible moreinfo
Bug #744215 [wvdial] wvdial: Segmentation fault during modem initialization
Added tag(s) unreproducible and moreinfo.

-- 
744215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744215
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: Update bug

[Debian Bug Tracking System]

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

> severity 757150 normal
Bug #757150 [stellarium] [stellarium] Fails to display
Severity set to 'normal' from 'grave'
> notforwarded 757150
Bug #757150 [stellarium] [stellarium] Fails to display
Unset Bug forwarded-to-address
> tags 757150 - upstream + unreproducible
Bug #757150 [stellarium] [stellarium] Fails to display
Removed tag(s) upstream.
Bug #757150 [stellarium] [stellarium] Fails to display
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757150
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#757150: [Debian-astro-maintainers] Bug#757150: Bug#757150: Bug#757150:

[Tomasz Buchert]

On 06/08/14 17:08, Alexander Wolf wrote:
> >
> > > Thanks a lot for this!
> > > However, this is VERY weird since in theory stellarium 0.13 uses Qt5!
> > > Moreover, as I just checked, on some architectures libqt4-opengl is
> > > installed as a dependency, but not on amd64:
> > > https://packages.debian.org/sid/stellarium
> > >
> > > Why would a Qt5 application require Qt4 libraries in the case
> > > of your bug escapes me... Moreover, I've just removed libqt4-opengl
> > > from my system and stellarium works hapilly anyway, so it is
> > > probably still linked to your particular configuration. Is your
> > > previous bug still reproducible, even if you remove libqt4-opengl
> > > now? Maybe you did something also as well?
> > >
> > > Tomasz
> >
> > Hi Tomasz,
> >
> > Yes now, I removed libqt4-opengl and stellarium starts normally
> >
> >
> Hm. Looks like some opengl library did not installed - why? Has debian a
> separate library for shaders support?

Hi,
I don't think there is a special shader library. I've just installed
a clean jessie and sid chroots and installed stellarium 0.13.0-2 inside them.
It worked perfectly in both cases.
Considering that Davide has stellarium working now, I think it was some
kind of interference between packages coming from 
unstable/testing/deb-multimedia.org.
As I said before, I'll drop the severity of this bug and keep it open for
more or less 2 weeks unless somebody will hit the problem again.

Tomasz


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

Bug#753968: [src:gtk+3.0 ] Some sources are not included in your package

[Emilio Pozuelo Monfort]

On 06/08/14 12:47, Simon McVittie wrote:
> On Sun, 06 Jul 2014 at 19:25:53 +, bastien ROUCARIES wrote:
>> Your package seems to include some files that lack sources
>> in prefered forms of modification:
>>
>> gdk/broadway/rawinflate.min.js
> 
> This is not trivial to fix.
> 
> The preferred form for modification appears to be found at
> https://github.com/imaya/zlib.js - our rawinflate.min.js matches
> the precompiled/minified version 0.1.6 from that repository.
> 
> That repository contains JS source code which is compiled with the
> Google Closure Compiler (implemented in Java), a copy of which
> can be found in that repository as non-source (a precompiled
> jar file).
> 
> The Closure compiler exists in Debian, but probably not at the same version,
> and some of the command-line syntax seems to have changed. It was not
> clear to me how to reconstruct the desired version of rawinflate.min.js
> from that repository, but that's not surprising, because I have no idea
> how Closure is meant to work in any case.
> 
> Gtk maintainers: how important is the Broadway backend? Would it
> be reasonable to disable that backend, and remove rawinflate.min.js
> from a .dfsg repacked tarball?

I don't think dropping the broadway backend is reasonable.

> If not, I think this will require help from someone who knows the
> Javascript ecosystem, and/or Gtk upstream.

We can probably add the source to debian/ and some instructions on how the
min.js file is generated. We don't need to generate it though, shipping the
pre-generated file is fine.

Emilio


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

Processed: libpdl-io-hdf5-perl: diff for NMU version 0.63-3.1

[Debian Bug Tracking System]

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

> tags 729343 + patch
Bug #729343 [libpdl-io-hdf5-perl] libpdl-io-hdf5-perl: package is empty if 
built in sid
Added tag(s) patch.
> tags 729343 + pending
Bug #729343 [libpdl-io-hdf5-perl] libpdl-io-hdf5-perl: package is empty if 
built in sid
Added tag(s) pending.
> tags 756676 + pending
Bug #756676 [src:libpdl-io-hdf5-perl] libpdl-io-hdf5-perl: [hdf5 transition] 
please support hdf5 1.8.13 new packaging layout
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
729343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729343
756676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756676
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#729343: libpdl-io-hdf5-perl: diff for NMU version 0.63-3.1

[Gilles Filippini]

tags 729343 + patch
tags 729343 + pending
tags 756676 + pending
thanks

Dear maintainer,

I've prepared an NMU for libpdl-io-hdf5-perl (versioned as 0.63-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

_g.

diff -Nru libpdl-io-hdf5-perl-0.63/debian/changelog 
libpdl-io-hdf5-perl-0.63/debian/changelog
--- libpdl-io-hdf5-perl-0.63/debian/changelog   2012-05-31 09:11:55.0 
+0200
+++ libpdl-io-hdf5-perl-0.63/debian/changelog   2014-08-06 09:00:13.0 
+0200
@@ -1,3 +1,11 @@
+libpdl-io-hdf5-perl (0.63-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch support-hdf5-1.8.13.patch: support hdf5 1.8.13 new
+packaging layout (closes: #756676, #729343).
+
+ -- Gilles Filippini   Wed, 06 Aug 2014 08:58:17 +0200
+
 libpdl-io-hdf5-perl (0.63-3) unstable; urgency=low
 
   * rebuild with fixed pdl dh_pdl, update build-dep 
diff -Nru libpdl-io-hdf5-perl-0.63/debian/patches/series 
libpdl-io-hdf5-perl-0.63/debian/patches/series
--- libpdl-io-hdf5-perl-0.63/debian/patches/series  2012-05-28 
11:46:12.0 +0200
+++ libpdl-io-hdf5-perl-0.63/debian/patches/series  2014-08-06 
08:57:38.0 +0200
@@ -1,3 +1,4 @@
 remove-interpreter-from-package.patch
 clean_newFile_hd5.patch
 ccflags-5.14.patch
+support-hdf5-1.8.13.patch
diff -Nru libpdl-io-hdf5-perl-0.63/debian/patches/support-hdf5-1.8.13.patch 
libpdl-io-hdf5-perl-0.63/debian/patches/support-hdf5-1.8.13.patch
--- libpdl-io-hdf5-perl-0.63/debian/patches/support-hdf5-1.8.13.patch   
1970-01-01 01:00:00.0 +0100
+++ libpdl-io-hdf5-perl-0.63/debian/patches/support-hdf5-1.8.13.patch   
2014-08-06 08:57:38.0 +0200
@@ -0,0 +1,20 @@
+Index: libpdl-io-hdf5-perl-0.63/Makefile.PL
+===
+--- libpdl-io-hdf5-perl-0.63.orig/Makefile.PL  2014-07-25 11:39:35.0 
+0200
 libpdl-io-hdf5-perl-0.63/Makefile.PL   2014-07-31 10:21:48.402573366 
+0200
+@@ -39,6 +39,7 @@
+ $ENV{'HOME'} = '' unless defined( $ENV{'HOME'} ) ;
+ 
+ foreach my $libdir (
++  "$ENV{HDF5_LIBDIR}",
+   '/usr/local/hdf5/lib',
+   '/usr/local/lib',
+   '/opt/local/lib',
+@@ -70,6 +71,7 @@
+ } 
+ 
+ foreach my $incdir (
++  "$ENV{HDF5_INCDIR}",
+   '/usr/local/hdf5/include',
+   '/usr/local/include',
+   '/opt/local/include',
diff -Nru libpdl-io-hdf5-perl-0.63/debian/rules 
libpdl-io-hdf5-perl-0.63/debian/rules
--- libpdl-io-hdf5-perl-0.63/debian/rules   2012-05-28 12:27:39.0 
+0200
+++ libpdl-io-hdf5-perl-0.63/debian/rules   2014-08-06 08:57:38.0 
+0200
@@ -2,6 +2,14 @@
 
 export DEB_LDFLAGS_MAINT_APPEND:=-Wl,--as-needed
 
+ifneq ($(wildcard /usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/serial/libhdf5.so),)
+  export HDF5_INCDIR := /usr/include/hdf5/serial
+  export HDF5_LIBDIR := /usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/serial
+else
+  export HDF5_INCDIR := /usr/include
+  export HDF5_LIBDIR := /usr/lib/$(DEB_HOST_MULTIARCH)
+endif
+
 build:
dh build
 


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

Bug#753968: [src:gtk+3.0 ] Some sources are not included in your package

[Simon McVittie]

On Sun, 06 Jul 2014 at 19:25:53 +, bastien ROUCARIES wrote:
> Your package seems to include some files that lack sources
> in prefered forms of modification:
> 
> gdk/broadway/rawinflate.min.js

This is not trivial to fix.

The preferred form for modification appears to be found at
https://github.com/imaya/zlib.js - our rawinflate.min.js matches
the precompiled/minified version 0.1.6 from that repository.

That repository contains JS source code which is compiled with the
Google Closure Compiler (implemented in Java), a copy of which
can be found in that repository as non-source (a precompiled
jar file).

The Closure compiler exists in Debian, but probably not at the same version,
and some of the command-line syntax seems to have changed. It was not
clear to me how to reconstruct the desired version of rawinflate.min.js
from that repository, but that's not surprising, because I have no idea
how Closure is meant to work in any case.

Gtk maintainers: how important is the Broadway backend? Would it
be reasonable to disable that backend, and remove rawinflate.min.js
from a .dfsg repacked tarball?

If not, I think this will require help from someone who knows the
Javascript ecosystem, and/or Gtk upstream.

S


-- 
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#756476: AM_PATH_GTK_3_0 fails if gthread is in 4th argument

[Debian Bug Tracking System]

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

> retitle 756476 AM_PATH_GTK_3_0 fails if gthread is in 4th argument
Bug #756476 [libgtk-3-dev] gtk-3.0.m4 doesn't work as header files in
Changed Bug title to 'AM_PATH_GTK_3_0 fails if gthread is in 4th argument' from 
'gtk-3.0.m4 doesn't work as header files in'
> forwarded 756476 https://bugzilla.gnome.org/show_bug.cgi?id=641638
Bug #756476 [libgtk-3-dev] AM_PATH_GTK_3_0 fails if gthread is in 4th argument
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=641638'.
> tags 756476 + patch upstream
Bug #756476 [libgtk-3-dev] AM_PATH_GTK_3_0 fails if gthread is in 4th argument
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
756476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756476
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#756476: AM_PATH_GTK_3_0 fails if gthread is in 4th argument

[Simon McVittie]

retitle 756476 AM_PATH_GTK_3_0 fails if gthread is in 4th argument
forwarded 756476 https://bugzilla.gnome.org/show_bug.cgi?id=641638
tags 756476 + patch upstream
thanks

On Wed, 06 Aug 2014 at 01:49:05 +0300, Yavor Doganov wrote:
> The problem is due to changed behavior of pkg-config, most probably
> occurred in version 0.28.  "pkg-config --atleast-version N libA libB"
> now checks if both libraries are >= N (which will always return false
> for gtk+-3.0 if the last macro argument is used because the
> gthread-2.0 version is 2.40.x).

Retitling bug, thanks for this analysis.

I don't think this should be considered RC: AM_PATH_GTK_3_0 is rarely-used
and there are much better ways to achieve the same thing (pkg-config).
Gtk maintainers' opinions?

gtk-3.0.m4 should be considered deprecated: it's far too complicated
for the value it provides. All packages that use AM_PATH_GTK_3_0 should simply
replace it with an equivalent PKG_CHECK_MODULES call, something like:

AM_PATH_GTK_3_0([3.4]) -> PKG_CHECK_MODULES([GTK], [gtk+-3.0 >= 3.4])

AM_PATH_GTK_3_0([3.4], [], [], [gthread]) ->
PKG_CHECK_MODULES([GTK], [gtk+-3.0 >= 3.4, gthread-2.0])

(PKG_CHECK_MODULES can also take ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
arguments if you really need them.)

> Trivial patch attached.  I can't reproduce this with pkg-config/0.26-1
> on wheezy which makes me think that this is new behavior as of 0.28.
> I am not sure it was intended though, seems unnatural/incorrect to me.

"pkg-config --atleast-version V pkg1 pkg2" is documented to be equivalent
to pkg1 >= V, pkg2 >= V. It looks as though the documented behaviour was
not actually implemented until recently.

I think all uses of pkg-config --atleast-version should be replaced by
explicit ">=" version specifiers. I attach a patch which does that;
I think that's better than deleting the gthread check entirely, but
not as good as adapting packages that use AM_PATH_GTK_3_0 to stop
doing so.

For packages that do not already use autoreconf at build time, a sourceful
upload will be needed to pick up the new gtk-3.0.m4, and if you're
doing a sourceful upload anyway, please just fix your configure.ac to not
do this. It'll make your build quicker, too.

Regards,
S
>From d2fb42cbaec9328f65d0413d13bde9f6cb065df2 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 6 Aug 2014 11:02:38 +0100
Subject: [PATCH 1/3] Avoid "pkg-config --atleast-version"

AM_PATH_GTK_3_0([3.4], [], [], [gthread]) results in calling
"pkg-config --atleast-version 3.4 gtk+-3.0 gthread-2.0".

With pkg-config 0.28, that test fails, because the version of
gthread-2.0 is smaller than 3.4. This appears to be a behaviour
change since 0.26, but matches what the documentation said in 0.26.
---
 m4macros/gtk-3.0.m4 | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/m4macros/gtk-3.0.m4 b/m4macros/gtk-3.0.m4
index 5238b43..0d605fb 100644
--- a/m4macros/gtk-3.0.m4
+++ b/m4macros/gtk-3.0.m4
@@ -11,8 +11,9 @@ dnl Get the cflags and libraries from pkg-config
 dnl
 AC_ARG_ENABLE(gtktest, [  --disable-gtktest   do not try to compile and run a test GTK+ program],
 		, enable_gtktest=yes)
+  min_gtk_version=ifelse([$1], [], [3.0.0], [$1])
 
-  pkg_config_args=gtk+-3.0
+  pkg_config_args="gtk+-3.0 >= $min_gtk_version"
   for module in . $4
   do
   case "$module" in
@@ -38,7 +39,6 @@ AC_ARG_ENABLE(gtktest, [  --disable-gtktest   do not try to compile and run
 no_gtk=yes
   fi
 
-  min_gtk_version=ifelse([$1], ,3.0.0,$1)
   AC_MSG_CHECKING(for GTK+ - version >= $min_gtk_version)
 
   if test x$PKG_CONFIG != xno ; then
@@ -48,7 +48,7 @@ AC_ARG_ENABLE(gtktest, [  --disable-gtktest   do not try to compile and run
 	  enable_gtktest=no
 fi
 
-if $PKG_CONFIG --atleast-version $min_gtk_version $pkg_config_args; then
+if $PKG_CONFIG $pkg_config_args; then
 	  :
 else
 	  no_gtk=yes
@@ -202,10 +202,11 @@ AC_DEFUN([GTK_CHECK_BACKEND],
 [
   pkg_config_args=ifelse([$1],,gtk+-3.0, gtk+-$1-3.0)
   min_gtk_version=ifelse([$2],,3.0.0,$2)
+  pkg_config_args="$pkg_config_args >= $min_gtk_version"
 
   AC_PATH_PROG(PKG_CONFIG, [pkg-config], [AC_MSG_ERROR([No pkg-config found])])
 
-  if $PKG_CONFIG --atleast-version $min_gtk_version $pkg_config_args ; then
+  if $PKG_CONFIG $pkg_config_args ; then
 target_found=yes
   else
 target_found=no
-- 
2.1.0.rc1

>From b3f49ec9fa9ec67142d614e9b4a7959d80eba07f Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 6 Aug 2014 11:23:23 +0100
Subject: [PATCH 2/3] Deprecate AM_PATH_GTK_3_0 in favour of PKG_CHECK_MODULES

That's what GNOME applications use.
---
 m4macros/gtk-3.0.m4 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/m4macros/gtk-3.0.m4 b/m4macros/gtk-3.0.m4
index 0d605fb..274cd32 100644
--- a/m4macros/gtk-3.0.m4
+++ b/m4macros/gtk-3.0.m4
@@ -6,7 +6,7 @@ dnl Test for GTK+, and define GTK_CFLAGS and GTK_LIBS, if gthread is specified i
 dnl pass to pkg-config
 dnl
 AC_DEFUN([AM_PATH_GTK

Bug#745529: Please drop lcms1

[Jonas Smedegaard]

Quoting Moritz Mühlenhoff (2014-08-06 12:10:09)
> On Tue, Apr 22, 2014 at 05:48:51PM +0200, Moritz Muehlenhoff wrote:
>> As pre-announced in
>> https://lists.debian.org/debian-devel/2013/12/msg00570.html
>> it is planned to remove lcms1 for jessie. 
>> 
>> According to the changelog this is mostly done:
>> 
>> |  * Link against lcms2 (not lcms1).
>> |Regenerate autoconf during build (needed for patch 1001).
>> |Build-depend on autoconf.
>> |Build-depend on liblcms1-dev (in addition to liblcms2-dev): Provides
>> |needed icc34.h header.
>> 
>> Please fix ghostscript so that liblcms1-dev can be dropped.
>> 
>> The severity will be bumped to RC-level before the jessie freeze.
>
> This is fixed in experimental for three months now and the freeze is 
> coming closer, are you planning to upload this to sid soon?

Yes.  First upload to unstable will however not be the 9.10 now in 
experimental, but instead 9.06 sitting in git ready for release.  Plan 
is posted here: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723719#39


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#745529: Please drop lcms1

[Moritz Mühlenhoff]

On Tue, Apr 22, 2014 at 05:48:51PM +0200, Moritz Muehlenhoff wrote:
> Package: ghostscript
> Version: 9.05~dfsg-8.1
> Severity: important
> 
> As pre-announced in
> https://lists.debian.org/debian-devel/2013/12/msg00570.html
> it is planned to remove lcms1 for jessie. 
> 
> According to the changelog this is mostly done:
> 
> |  * Link against lcms2 (not lcms1).
> |Regenerate autoconf during build (needed for patch 1001).
> |Build-depend on autoconf.
> |Build-depend on liblcms1-dev (in addition to liblcms2-dev): Provides
> |needed icc34.h header.
> 
> Please fix ghostscript so that liblcms1-dev can be dropped.
> 
> The severity will be bumped to RC-level before the jessie freeze.

This is fixed in experimental for three months now and the freeze is
coming closer, are you planning to upload this to sid soon?

Cheers,
Moritz


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

Bug#757150: [Debian-astro-maintainers] Bug#757150: Bug#757150:

[Alexander Wolf]

>
> > Thanks a lot for this!
> > However, this is VERY weird since in theory stellarium 0.13 uses Qt5!
> > Moreover, as I just checked, on some architectures libqt4-opengl is
> > installed as a dependency, but not on amd64:
> > https://packages.debian.org/sid/stellarium
> >
> > Why would a Qt5 application require Qt4 libraries in the case
> > of your bug escapes me... Moreover, I've just removed libqt4-opengl
> > from my system and stellarium works hapilly anyway, so it is
> > probably still linked to your particular configuration. Is your
> > previous bug still reproducible, even if you remove libqt4-opengl
> > now? Maybe you did something also as well?
> >
> > Tomasz
>
> Hi Tomasz,
>
> Yes now, I removed libqt4-opengl and stellarium starts normally
>
>
Hm. Looks like some opengl library did not installed - why? Has debian a
separate library for shaders support?

Bug#757150: [Debian-astro-maintainers] Bug#757150: Bug#757150:

[Tomasz Buchert]

Ok, this is a bit strange.
Do you consider your bug fixed then?

What I propose is to keep your bug open for some time
(say 2 weeks) and if nothing changes we will close it, ok?

Tomasz


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

Bug#754783: marked as done ([src:moin] Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Wed, 6 Aug 2014 11:03:44 +0100
with message-id <20140806100344.ga13...@einval.com>
and subject line Fixed in moin 1.9.7-2
has caused the Debian Bug report #754783,
regarding [src:moin] Some sources are not included in your package
to be marked as done.

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

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


-- 
754783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:moin 
Version: 1.9.7-1
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

Old jquery file (v1.4.4)

   MoinMoin/support/werkzeug/debug/shared/jquery.js

The following one have source and should be overriden (or better use the 
packaged fsck)

MoinMoin/web/static/htdocs/applets/FCKeditor/editor/js/fckeditorcode_gecko.js
MoinMoin/web/static/htdocs/applets/FCKeditor/editor/js/fckeditorcode_ie.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft licenses such 
as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus full 
filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract
--- End Message ---
--- Begin Message ---
Source: moin
Source-Version: 1.9.7-2

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Jul 2014 14:34:47 +0100
Source: moin
Binary: python-moinmoin
Architecture: source all
Version: 1.9.7-2
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 python-moinmoin - Python clone of WikiWiki - library
Changes:
 moin (1.9.7-2) unstable; urgency=medium
 .
   * Add source for the minified copy of jquery.js included in the
   upstream
 source tarball, even though it's never used in the Debian build
 at all.
 Close: #754783. Mention it in README.source too
   * Minor updates prompted by lintian:
 + Update Standards-Version
 + Switch from "dh_clean -k" to "dh_prep"
 + Minor tweaks to debian/copyright to fix parse errors
Checksums-Sha1:
 b7efd8428be4c156086d88716bb69d238b483ead 1868 moin_1.9.7-2.dsc
 23600b6a87bd1ac88969afa18bb480d7734de02c 149536
 moin_1.9.7-2.debian.tar.xz
 b4a32f591c89189817fe1da301f9f374b355ef75 8285330
 python-moinmoin_1.9.7-2_all.deb
Checksums-Sha256:
 ada215e1d8361da330cdae9fd9be03e4f23a9ce0a25d4de5ff70f4899bc1f65e 1868
 moin_1.9.7-2.dsc
 786b50a750a31af8fbb5a18f621c49fcd4d1c571a35d624e08016f88da537f82
 149536 moin_1.9.7-2.debian.tar.xz
 6c8eda22ac4b26f62f28e7c1c3d060c1a9b44d6e37f625c863ea1841e2048a1c
 8285330 python-moinmoin_1.9.7-2_all.deb
Files:
 5a937c67c3c906785c29b74a1017500d 8285330 python optional
 python-moinmoin_1.9.7-2_all.deb
 5e8830acc51feebf048aba96e0fa0e6b 1868 net optional moin_1.9.7-2.dsc
 109c22a2a0ead358607be76f6b584d5e 149536 net optional
 moin_1.9.7-2.debian.tar.xz

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

iQIcBAEBCAAGBQJT2lifAAoJEFh5eVc0QmhO0KcP/jrLN54+ncfvxonEjXy3IFBx
/uJcF4ldAk7BAgSp6/ff61Dwr1Zbl872jg5aBKlro+5x/uhMe+wqeaPMInpHHtUt
773kj++026BNny/n7tJ6WvZ7ahvJidtaAEm5jF/7y6V7q8U0/ulpV0i/DNXo9tPO
aYwVbmfEc4eEuiKuw+IWFXlFSSaWKM3cYZDMmT0I8s54gXf5JvkVC1rv9KQmodVJ
fClbUkdYMtnLOwapVu4PF9SNlJm750s2TSaBix4OC70940xeBWZGoZA6SKjR/+9u
r2mwwCCpoqllCSDNYacfSiFFh0GKcZqOvCAKSzI6TpRyViE+kkZtlJbVd8wrOh91
AdbqI4Jq2bz7Cu7sP0dIq8DoJgH0itsy74MdVgLrv5Kto3QoyW5cNem8wgXZYUeP
WNuoz9vfX6Og1zrrUB+TO63R+ZzXLuYfsDl/WyHFq6Iq9iHOwbv0QXZby6awIcRl
7zfoal3fnnd5l9Rxe0gZZJAzQPKe+SMLIj4C8WRwWyVYwLDvDQ98247BWaz2gX2j
uelf4MIVeCddML5jizwuHN3Ni

Processed: Re: nullmailer ignores permanent SMTP errors

[Debian Bug Tracking System]

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

> clone 329192 -1
Bug #329192 [nullmailer] nullmailer ignores permanent SMTP errors
Bug 329192 cloned as bug 757221
> retitle -1 nullmailer performs excessive retries on failures
Bug #757221 [nullmailer] nullmailer ignores permanent SMTP errors
Changed Bug title to 'nullmailer performs excessive retries on failures' from 
'nullmailer ignores permanent SMTP errors'
> submitter -1 plugw...@p10link.net
Bug #757221 [nullmailer] nullmailer performs excessive retries on failures
Changed Bug submitter to 'plugw...@p10link.net' from 'Roy Hills 
'
> forwarded -1 https://github.com/bruceg/nullmailer/issues/4
Bug #757221 [nullmailer] nullmailer performs excessive retries on failures
Changed Bug forwarded-to-address to 
'https://github.com/bruceg/nullmailer/issues/4' from 'br...@untroubled.org'
> severity 329192 normal
Bug #329192 [nullmailer] nullmailer ignores permanent SMTP errors
Severity set to 'normal' from 'serious'
> forwarded 329192 https://github.com/bruceg/nullmailer/issues/1
Bug #329192 [nullmailer] nullmailer ignores permanent SMTP errors
Changed Bug forwarded-to-address to 
'https://github.com/bruceg/nullmailer/issues/1' from 'br...@untroubled.org'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
329192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329192
757221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757221
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#329192: nullmailer ignores permanent SMTP errors

[Nick Leverton]

clone 329192 -1
retitle -1 nullmailer performs excessive retries on failures
submitter -1 plugw...@p10link.net
forwarded -1 https://github.com/bruceg/nullmailer/issues/4
severity 329192 normal
forwarded 329192 https://github.com/bruceg/nullmailer/issues/1
thanks


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

Processed: tagging 753589

[Debian Bug Tracking System]

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

> tags 753589 + pending
Bug #753589 [systemd] systemd: needs Pre-Depends for transitively Essential 
functionality of systemd-sysv
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589
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#747804: spotlighter: FTBFS: error: Test for GTK3+ failed

[Simon McVittie]

On Wed, 30 Jul 2014 at 16:10:25 +0800, YunQiang Su wrote:
> I think this problem is caused by libgtk-3-dev.
> File /usr/share/aclocal/gtk-3.0.m4, it doesn't work,
> as the header files of gtk+3 is in /usr/include/gtk-3.0
> 
> And I will nmu spotlighter to not use gtk-3.0.m4.

Whenever you NMU a package, you should send the diff between the
current package and your proposed NMU to the BTS. (See §5.11.1 in
.)

I attach the diff between 0.3-1 and 0.3-1.1.

A much simpler Gtk version check, suitable for sending upstream:

- delete the call to AM_PATH_GTK_3_0 as was done in the NMU
- delete this block:
  AC_MSG_CHECKING([if GTK+ is version 2.99.3 or newer])
  ...
  AC_MSG_RESULT($have_gtk_3)
- delete the unused pkg_modules variable
- change PKG_CHECK_MODULES(spotlighter, [gtk+-3.0])
  to PKG_CHECK_MODULES([spotlighter], [gtk+-3.0 >=] gtk_required_version)

S
diffstat for spotlighter-0.3 spotlighter-0.3

 changelog   |8 
 control |3 ++-
 patches/no_AM_PATH_GTK_3_0.diff |   16 
 patches/series  |1 +
 rules   |2 +-
 5 files changed, 28 insertions(+), 2 deletions(-)

diff -Nru spotlighter-0.3/debian/changelog spotlighter-0.3/debian/changelog
--- spotlighter-0.3/debian/changelog	2013-12-14 09:41:29.0 +
+++ spotlighter-0.3/debian/changelog	2014-07-30 09:48:24.0 +0100
@@ -1,3 +1,11 @@
+spotlighter (0.3-1.1) unstable; urgency=low
+  
+  * Non-maintainer upload.
+  * don't use AM_PATH_GTK_3_0 in configure.ac, as it cannot work
+  * use dh-autoreconf update build system (Closes: #747804 #727974)
+
+ -- YunQiang Su   Wed, 30 Jul 2014 16:26:02 +0800
+
 spotlighter (0.3-1) unstable; urgency=low
 
   * New upstream release. (Closes: #685911)
diff -Nru spotlighter-0.3/debian/control spotlighter-0.3/debian/control
--- spotlighter-0.3/debian/control	2013-12-14 09:35:10.0 +
+++ spotlighter-0.3/debian/control	2014-07-30 09:29:19.0 +0100
@@ -6,7 +6,8 @@
autotools-dev,
intltool,
pkg-config,
-   libgtk-3-dev
+   libgtk-3-dev,
+   dh-autoreconf
 Standards-Version: 3.9.5
 Homepage: http://code.google.com/p/ardesia/
 Vcs-Git: git://anonscm.debian.org/collab-maint/spotlighter.git
diff -Nru spotlighter-0.3/debian/patches/no_AM_PATH_GTK_3_0.diff spotlighter-0.3/debian/patches/no_AM_PATH_GTK_3_0.diff
--- spotlighter-0.3/debian/patches/no_AM_PATH_GTK_3_0.diff	1970-01-01 01:00:00.0 +0100
+++ spotlighter-0.3/debian/patches/no_AM_PATH_GTK_3_0.diff	2014-07-30 09:28:48.0 +0100
@@ -0,0 +1,16 @@
+Index: spotlighter-0.3/configure.ac
+===
+--- spotlighter-0.3.orig/configure.ac	2012-09-04 18:38:43.0 +0800
 spotlighter-0.3/configure.ac	2014-07-30 16:28:44.745410082 +0800
+@@ -73,11 +73,6 @@
+ ###
+ # Gtk 3
+ ###
+-AM_PATH_GTK_3_0(gtk_required_version, :,
+-  AC_MSG_ERROR(Test for GTK3+ failed. See the file 'INSTALL' for help.),
+-  gthread)
+-
+-
+ AC_MSG_CHECKING([if GTK+ is version 2.99.3 or newer])
+ if $PKG_CONFIG --atleast-version=2.99.3 gtk+-3.0; then
+   have_gtk3=yes
diff -Nru spotlighter-0.3/debian/patches/series spotlighter-0.3/debian/patches/series
--- spotlighter-0.3/debian/patches/series	2013-12-13 17:40:23.0 +
+++ spotlighter-0.3/debian/patches/series	2014-07-30 09:28:28.0 +0100
@@ -1,2 +1,3 @@
 00_desktop.patch
 01_ftbfs_mips.patch
+no_AM_PATH_GTK_3_0.diff
diff -Nru spotlighter-0.3/debian/rules spotlighter-0.3/debian/rules
--- spotlighter-0.3/debian/rules	2013-12-13 12:18:42.0 +
+++ spotlighter-0.3/debian/rules	2014-07-30 09:29:02.0 +0100
@@ -2,4 +2,4 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@ --with autotools_dev
+	dh $@ --with autoreconf

Bug#756788: libwebp: FTBFS on mips*

[Dejan Latinovic]

Adding -mips32r2 is not a good idea,
since all Debian on mips* is built for mips2.

Instead, i think that better solution would be to
define  WEBP_USE_MIPS32 only in mips32 case.
(src/dsp/dsp.h)

The patch that contains needed changes is attached.

With this patch I was able to successfully build libwebp for both mips and 
mipsel.


Could you please consider including this patch?--- libwebp-0.4.1.orig/src/dsp/dsp.h	2014-07-29 00:22:32.0 +
+++ libwebp-0.4.1/src/dsp/dsp.h	2014-08-04 12:10:23.0 +
@@ -60,7 +60,7 @@
 #define WEBP_USE_NEON
 #endif
 
-#if defined(__mips__)
+#if defined(__mips__) && defined(_MIPS_ARCH_MIPS32)
 #define WEBP_USE_MIPS32
 #endif
 

Bug#329192: nullmailer ignores permanent SMTP errors

[Nick Leverton]

I'm splitting this bug into two:

329192 remains the original bug about ignoring SMTP errors (message
#5) and having no queue expiry time (message #10).

The clone concerns the "hammering on closed door" effect of the
default pausetime, which is what has really taken up people's
bandwidth and log space and which led to it being marked 'serious'
(messages #29 onwards).

I'm doing this because upstream has logged them as separate issues in
their own tracker, and so that we can consider whether upstream's fix
for the second issue is adequate to allow this package to be
reintroduced into Jesse.

Nick


-- 
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#757207: systemd: Installation of systemd makes system unbootable

[Debian Bug Tracking System]

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

> tags 757207 + moreinfo
Bug #757207 [systemd] systemd: Installation of systemd makes system unbootable
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757207
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#757207: systemd: Installation of systemd makes system unbootable

[Michael Biebl]

tags 757207 + moreinfo
thanks

Am 06.08.2014 10:28, schrieb Jens Stavnstrup:
> Package: systemd
> Severity: critical
> Justification: breaks the whole system
> 
> The bug is properly related to #754059, but unlike Filippo, I was stupid 
> enough to update to systemd,

Please keep technical. We won't communicate on that level.

> Using emergency mode (which is also a problem due to #755581), I was able to 
> re-add sysvinit-core, which subsequently removed
> 
> network-manager:i386 (0.9.10.0-1), kde-plasma-desktop:i386
> (84), hplip:i386 (3.14.6-1), plasma-nm:i386 (0.9.3.3-4),
> printer-driver-postscript-hp:i386 (3.14.6-1), systemd-sysv:i386
> (208-6), kde-standard:i386 (84), polkit-kde-1:i386 (0.99.1-1),
> packagekit:i386 (0.8.17-4), appstream-index:i386 (0.7.0-2),
> task-kde-desktop:i386 (3.20), policykit-1-gnome:i386 (0.105-2),
> listaller:i386 (0.5.8-2), plasma-widget-networkmanagement:i386
> (0.9.3.3-4), gvfs:i386 (1.20.2-1), colord:i386 (1.2.1-1),
> libpam-systemd:i386 (208-6), udisks2:i386 (2.1.3-2),
> packagekit-tools:i386 (0.8.17-4), gvfs-daemons:i386 (1.20.2-1),
> policykit-1:i386 (0.105-6.1), apper:i386 (0.8.2-3)
> 
> Have looked at the different bug reports, but have not found anyway to 
> restablish my system.
> 
> What systemd packages should be added, it order for my system to work 
> properly again? And do I need to modify anything else? Looked at the systemd 
> wiki entry, but that seems a bit outdated with respect to the discussion 
> taking place on the debian-devel mailing-list.
> 
> Adding systemd, systemd-shim and cgmanager did not help. 
> 
> Trying to add several of the packages in the above list .e.f. network-manager 
> requires systemd and will remove sysvinit-core and make my system unbootable 
> again. 
> 
> 
> Since I am using a LVM2 encripted disk, this report may also be related to 
> #678438 and/or #692120.
> 
> 

Please enable the debug-shell.service (systemctl enable
debug-shell.service), then boot with the following kernel command line
option to enable a verbose debug log

systemd.log_level=debug


During boot when the system "get's stuck", switch to tty9 and get us the
output of "systemctl list-jobs" and "journalctl -alb"

What is the last output you see on tty1?


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



signature.asc
Description: OpenPGP digital signature

Bug#729132: patch: FTBFS due to ed check, with solution

[Simon McVittie]

On Tue, 05 Aug 2014 at 08:45:32 +0200, Helmut Grohne wrote:
> What I am getting out of that command for mips occasionally is "`ed"
> (without the double quotes but including the back-quote).

I can't help thinking that rather than parsing the binary, it would be
simpler to check that EDITOR_PROGRAM is defined the way you want it:

--- patch-2.7.1/debian/rules2013-11-04 12:43:02.0 +
+++ patch/debian/rules  2014-08-06 09:28:56.798604137 +0100
@@ -37,8 +37,8 @@
dh_testdir
$(MAKE)
dh_auto_test
-   # make sure we call ed as "ed"
-   [ "$$(strings -n 2 src/patch | grep -w 'ed$$')" = "ed" ]
+   # make sure we call ed as "ed", not "/bin/ed" or something
+   grep '#define  *EDITOR_PROGRAM  *"ed"' config.h
touch build-stamp
 
 clean:

Regards,
S


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

Bug#757207: systemd: Installation of systemd makes system unbootable

[Jens Stavnstrup]

Package: systemd
Severity: critical
Justification: breaks the whole system

The bug is properly related to #754059, but unlike Filippo, I was stupid enough 
to update to systemd, which resulted in the removal of sysvinit-core and 
resulted in an unbotable system.

Using emergency mode (which is also a problem due to #755581), I was able to 
re-add sysvinit-core, which subsequently removed

network-manager:i386 (0.9.10.0-1), kde-plasma-desktop:i386
(84), hplip:i386 (3.14.6-1), plasma-nm:i386 (0.9.3.3-4),
printer-driver-postscript-hp:i386 (3.14.6-1), systemd-sysv:i386
(208-6), kde-standard:i386 (84), polkit-kde-1:i386 (0.99.1-1),
packagekit:i386 (0.8.17-4), appstream-index:i386 (0.7.0-2),
task-kde-desktop:i386 (3.20), policykit-1-gnome:i386 (0.105-2),
listaller:i386 (0.5.8-2), plasma-widget-networkmanagement:i386
(0.9.3.3-4), gvfs:i386 (1.20.2-1), colord:i386 (1.2.1-1),
libpam-systemd:i386 (208-6), udisks2:i386 (2.1.3-2),
packagekit-tools:i386 (0.8.17-4), gvfs-daemons:i386 (1.20.2-1),
policykit-1:i386 (0.105-6.1), apper:i386 (0.8.2-3)

Have looked at the different bug reports, but have not found anyway to 
restablish my system.

What systemd packages should be added, it order for my system to work properly 
again? And do I need to modify anything else? Looked at the systemd wiki entry, 
but that seems a bit outdated with respect to the discussion taking place on 
the debian-devel mailing-list.

Adding systemd, systemd-shim and cgmanager did not help. 

Trying to add several of the packages in the above list .e.f. network-manager 
requires systemd and will remove sysvinit-core and make my system unbootable 
again. 


Since I am using a LVM2 encripted disk, this report may also be related to 
#678438 and/or #692120.


Relevant version numbers for the systemd packages are

systemd 208-6
systemd-shim 6-4
cgmanager 0.28.3



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

Kernel: Linux 3.14-1-686-pae (SMP w/4 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 systemd depends on:
ii  acl  2.2.52-1
ii  adduser  3.113+nmu3
ii  initscripts  2.88dsf-53.2
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.7-1
ii  libblkid12.20.1-5.8
ii  libc62.19-7
ii  libcap2  1:2.24-3
ii  libcap2-bin  1:2.24-3
ii  libcryptsetup4   2:1.6.4-4
ii  libdbus-1-3  1.8.6-1
ii  libgcrypt11  1.5.3-5
ii  libkmod2 18-1
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.8-3
ii  libselinux1  2.3-1
ii  libsystemd-daemon0   208-6
ii  libsystemd-journal0  208-6
ii  libsystemd-login0208-6
ii  libudev1 208-6
ii  libwrap0 7.6.q-25
ii  sysv-rc  2.88dsf-53.2
ii  udev 208-6
ii  util-linux   2.20.1-5.8

Versions of packages systemd recommends:
pn  libpam-systemd  

Versions of packages systemd suggests:
pn  systemd-ui  


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

Bug#757150: [Debian-astro-maintainers] Bug#757150:

[Davide Governale]

Il giorno Wed, 6 Aug 2014 09:24:40 +0200
Tomasz Buchert  ha scritto:

> On 06/08/14 08:57, Davide Governale wrote:
> > Il giorno Tue, 5 Aug 2014 22:15:41 +0200
> > Tomasz Buchert  ha scritto:
> > 
> > > Hi Davide,
> > > thanks for your information. Did the previous version
> > > of stellarium work for you? Your GPU is GeForce 7300 SE/7200
> > > and it seems that it does not support some fragment shader
> > > functionality (e.g., see
> > > https://code.google.com/p/flightgear-bugs/issues/detail?id=750).
> > > Is This bug is not specific to Debian and therefore I'll forward
> > > it to upstream as they will be probably interested in it.
> > > 
> > > I'll keep you informed.
> > > 
> > > Cheers,
> > > Tomasz
> > > 
> > > 
> > 
> > Hi Tomasz,
> > 
> > I have installed the package libqt4-opengl, and the software has
> > successfully started. I think that it's a problem of dependency-on
> > debian. You see the output now:
> > 
> > $ stellarium
> >  ---
> > [ This is Stellarium 0.13.0 - http://www.stellarium.org ]
> > [ Copyright (C) 2000-2014 Fabien Chereau et al  ]
> >  ---
> > Writing log file to: "/home/magellanino/.stellarium/log.txt"
> > File search paths:
> >   0 .  "/home/magellanino/.stellarium"
> >   1 .  "/usr/share/stellarium"
> > Config file is:  "/home/magellanino/.stellarium/config.ini"
> > OpenGL versions supported: "1.1, 1.2, 1.3, 1.4, 1.5, 2.0, 2.1"
> > Driver version string: "2.1.2 NVIDIA 304.123"
> > GL vendor is "NVIDIA Corporation"
> > GL renderer is "GeForce 7300 SE/7200 GS/PCIe/SSE2"
> > Cache directory is:
> > "/home/magellanino/.cache/stellarium/stellarium" Sky language is
> > "it_IT" Application language is  "it_IT"
> > Loading Solar System data ...
> > Found an old starsConfig.json file, upgrade..
> > Creates file
> > "/home/magellanino/.stellarium/stars/default/starsConfig.json"
> > Loading star data ... "Loading
> > "/usr/share/stellarium/stars/default/stars_0_0v0_5.cat": 0_0v0_2;
> > 4963" "Loading
> > "/usr/share/stellarium/stars/default/stars_1_0v0_5.cat": 1_0v0_2;
> > 21598" "Loading
> > "/usr/share/stellarium/stars/default/stars_2_0v0_5.cat": 2_0v0_2;
> > 150090" "Loading
> > "/usr/share/stellarium/stars/default/stars_3_1v0_3.cat": 3_1v0_3;
> > 428466" Finished loading star catalogue data, max_geodesic_level:
> > 3 navigation/preset_sky_time is a double - treating as jday:
> > 2.45151e+06 Loaded 10051 NGC records Loading NGC name data ...
> > Loaded 416 / 416 NGC name records successfully Loading star names
> > from "/usr/share/stellarium/skycultures/western/star_names.fab"
> > Loaded 237 / 237 common star names Loading star names from
> > "/usr/share/stellarium/stars/default/name.fab" Loaded 4359 / 4359
> > scientific star names Loading variable stars from
> > "/usr/share/stellarium/stars/default/gcvs_hip_part.dat" Loaded
> > 6886 / 6886 variable stars Loaded 88 / 88 constellation records
> > successfully for culture "western" Loaded 85 / 85 constellation art
> > records successfully for culture "western" Loaded 89 / 89
> > constellation names Loading constellation boundary data ... Loaded
> > 782 constellation boundary segments Intializing basic GL shaders...
> > Creating GUI ... Loaded plugin "Satellites"
> > Satellites::init copied default satellites.json to
> > "/home/magellanino/.stellarium/modules/Satellites/satellites.json"
> > Satellites: loading catalog file:
> > "/home/magellanino/.stellarium/modules/Satellites/satellites.json"
> > Unable to find module called "TimeZoneConfiguration" Loaded plugin
> > "TimeZoneConfiguration" Satellites: starting Internet update...
> > Satellite added: "02802" "SL-8 R/B" Satellites: purging objects
> > that were not updated... Satellite removed: "23833" "GPS BIIA-25
> > (PRN 03)" Satellites:  1 satellites proposed for removal,  1
> > removed,  665  remain. Satellites::saveTleMap() writing to:
> > "/home/magellanino/.stellarium/modules/Satellites/satellites.json"
> > Satellites: update finished. 664 / 665 updated, 1 added, 1 missing
> > or removed. 833 source entries parsed. Creating directory
> > "/home/magellanino/.stellarium/data" Unloaded plugin
> > "TimeZoneConfiguration" Unloaded plugin "Satellites" Downloaded 0
> > files (0 kbytes) in a session of 31.515 sec (average of 0 kB/s + 0
> > files from cache (0 kB)).
> > 
> > I discovered this by installing the previous version of stellarium.
> > During the installation of the old version, it was required
> > dependency libqt4-opengl # apt-get -t stable install stellarium
> > Lettura elenco dei pacchetti... Fatto Generazione albero delle
> > dipendenze Lettura informazioni sullo stato... Fatto
> > Alcuni pacchetti non possono essere installati. Questo può voler
> > dire che è stata richiesta una situazione impossibile oppure, se si
> > sta usando una distribuzione in sviluppo, che alcuni pacchetti
> > richiesti non sono ancora stati creati o sono stati rimossi da
> > Incoming. 

Processed: jessie

[Debian Bug Tracking System]

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

> tags 499480 + sid jessie
Bug #499480 [libmemcache0] libmemcache0 obsolete
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
499480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499480
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#757150: [Debian-astro-maintainers] Bug#757150:

[Tomasz Buchert]

On 06/08/14 08:57, Davide Governale wrote:
> Il giorno Tue, 5 Aug 2014 22:15:41 +0200
> Tomasz Buchert  ha scritto:
> 
> > Hi Davide,
> > thanks for your information. Did the previous version
> > of stellarium work for you? Your GPU is GeForce 7300 SE/7200
> > and it seems that it does not support some fragment shader
> > functionality (e.g., see
> > https://code.google.com/p/flightgear-bugs/issues/detail?id=750). Is
> > This bug is not specific to Debian and therefore I'll forward
> > it to upstream as they will be probably interested in it.
> > 
> > I'll keep you informed.
> > 
> > Cheers,
> > Tomasz
> > 
> > 
> 
> Hi Tomasz,
> 
> I have installed the package libqt4-opengl, and the software has
> successfully started. I think that it's a problem of dependency-on
> debian. You see the output now:
> 
> $ stellarium
>  ---
> [ This is Stellarium 0.13.0 - http://www.stellarium.org ]
> [ Copyright (C) 2000-2014 Fabien Chereau et al  ]
>  ---
> Writing log file to: "/home/magellanino/.stellarium/log.txt"
> File search paths:
>   0 .  "/home/magellanino/.stellarium"
>   1 .  "/usr/share/stellarium"
> Config file is:  "/home/magellanino/.stellarium/config.ini"
> OpenGL versions supported: "1.1, 1.2, 1.3, 1.4, 1.5, 2.0, 2.1"
> Driver version string: "2.1.2 NVIDIA 304.123"
> GL vendor is "NVIDIA Corporation"
> GL renderer is "GeForce 7300 SE/7200 GS/PCIe/SSE2"
> Cache directory is:  "/home/magellanino/.cache/stellarium/stellarium"
> Sky language is  "it_IT"
> Application language is  "it_IT"
> Loading Solar System data ...
> Found an old starsConfig.json file, upgrade..
> Creates file  "/home/magellanino/.stellarium/stars/default/starsConfig.json"
> Loading star data ...
> "Loading "/usr/share/stellarium/stars/default/stars_0_0v0_5.cat": 0_0v0_2; 
> 4963"
> "Loading "/usr/share/stellarium/stars/default/stars_1_0v0_5.cat": 1_0v0_2; 
> 21598"
> "Loading "/usr/share/stellarium/stars/default/stars_2_0v0_5.cat": 2_0v0_2; 
> 150090"
> "Loading "/usr/share/stellarium/stars/default/stars_3_1v0_3.cat": 3_1v0_3; 
> 428466"
> Finished loading star catalogue data, max_geodesic_level:  3
> navigation/preset_sky_time is a double - treating as jday: 2.45151e+06
> Loaded 10051 NGC records
> Loading NGC name data ...
> Loaded 416 / 416 NGC name records successfully
> Loading star names from 
> "/usr/share/stellarium/skycultures/western/star_names.fab"
> Loaded 237 / 237 common star names
> Loading star names from "/usr/share/stellarium/stars/default/name.fab"
> Loaded 4359 / 4359 scientific star names
> Loading variable stars from 
> "/usr/share/stellarium/stars/default/gcvs_hip_part.dat"
> Loaded 6886 / 6886 variable stars
> Loaded 88 / 88 constellation records successfully for culture "western"
> Loaded 85 / 85 constellation art records successfully for culture "western"
> Loaded 89 / 89 constellation names
> Loading constellation boundary data ... 
> Loaded 782 constellation boundary segments
> Intializing basic GL shaders... 
> Creating GUI ...
> Loaded plugin "Satellites"
> Satellites::init copied default satellites.json to  
> "/home/magellanino/.stellarium/modules/Satellites/satellites.json"
> Satellites: loading catalog file: 
> "/home/magellanino/.stellarium/modules/Satellites/satellites.json"
> Unable to find module called "TimeZoneConfiguration"
> Loaded plugin "TimeZoneConfiguration"
> Satellites: starting Internet update...
> Satellite added: "02802" "SL-8 R/B"
> Satellites: purging objects that were not updated...
> Satellite removed: "23833" "GPS BIIA-25 (PRN 03)"
> Satellites:  1 satellites proposed for removal,  1  removed,  665  remain.
> Satellites::saveTleMap() writing to: 
> "/home/magellanino/.stellarium/modules/Satellites/satellites.json"
> Satellites: update finished. 664 / 665 updated, 1 added, 1 missing or 
> removed. 833 source entries parsed.
> Creating directory  "/home/magellanino/.stellarium/data"
> Unloaded plugin "TimeZoneConfiguration"
> Unloaded plugin "Satellites"
> Downloaded 0 files (0 kbytes) in a session of 31.515 sec (average of 0 kB/s + 
> 0 files from cache (0 kB)).
> 
> I discovered this by installing the previous version of stellarium. During 
> the installation of the old version, it was required dependency libqt4-opengl
> # apt-get -t stable install stellarium
> Lettura elenco dei pacchetti... Fatto
> Generazione albero delle dipendenze   
> Lettura informazioni sullo stato... Fatto
> Alcuni pacchetti non possono essere installati. Questo può voler dire
> che è stata richiesta una situazione impossibile oppure, se si sta
> usando una distribuzione in sviluppo, che alcuni pacchetti richiesti
> non sono ancora stati creati o sono stati rimossi da Incoming.
> Le seguenti informazioni possono aiutare a risolvere la situazione:
> 
> I seguenti pacchetti hanno dipendenze non soddisfatte:
>  stellarium : Dipende: libqt4-opengl (>= 4:4.8.0) ma non sta per essere 
> installato
> 

Bug#757199: [icedove] [32bit] getdents() = EOVERFLOW - Mail & Extensions inaccessible when profile folder resides on large XFS or BTRFS volume with 64bit inodes

[Marcel Partap]

Package: icedove
Version: 31.0-1
Severity: serious

--- Please enter the report below this line. ---
After migrating my home directory to a 1.8TiB XFS partition, I could not
access my emails anymore. Icedove would open, but all extensions from
the profile folder were missing. The accounts were listed with the name
crossed out in the folder pane - yet the INBOX of my POP3 account (and a
single subfolder) would show up (including the mail contained
therein)... Rsyncing the profile folder from my backup one time after
another and trying various things kept me busy for most of the day...
with an AUFS union set up merging the backup root partition (ro) and
/tmp (rw), the same profile folder did work!
Digging deeper I finally found the right clues to identify the problem
cause: xfs uses 64-bit inodes by default for volumes >1TiB (and I think
BTRFS does now, too).. Icedove chokes on those.

The failing 32bit-getdents() call in strace:
> access("/home/empee584/.icedove/profile/extensions", F_OK) = 0
> stat64("/home/empee584/.icedove/profile/extensions", {st_mode=S_IFDIR|0770, 
> st_size=4096, ...}) = 0
> openat(AT_FDCWD, "/home/empee584/.icedove/profile/extensions", 
> O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 24
> getdents(24, 0xab44401c, 32768) = -1 EOVERFLOW (Value too large for defined 
> data type)
> close(24)   = 0  
> gettimeofday({1407252551, 784289}, NULL) = 0
> gettimeofday({1407252551, 784852}, NULL) = 0
> write(1, "1407252551784\taddons.xpi\tWARN\tCa"..., 10321407252551784
> addons.xpi  WARNCan't iterate directory /home/empe e584/.icedov
> e/profile/extensions: [Exception... "Component returned failure code: 
> 0x80004005 (NS_ERROR_FAILURE) [nsIFile.directoryEntries]"  nsres ult: 
> "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: 
> resource://gre/modules/addons/XPIProvider.jsm :: getDirectoryEntries :: line 
> 1355"  d ata: no] Stack trace: 
> getDirectoryEntries()@resource://gre/modules/addons/XPIProvider.jsm:1355 < 
> DirInstallLocation__readAddons()@resource://gre/m 
> odules/addons/XPIProvider.jsm:6889 < 
> DirectoryInstallLocation()@resource://gre/modules/addons/XPIProvider.jsm:6828 
> < addDirectoryInstallLocation() 
> @resource://gre/modules/addons/XPIProvider.jsm:1775 < 
> XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:1856 < 
> AMI_callProviders()@resou rce://gre/modules/AddonManager.jsm:869 < 
> AMI_startup()@resource://gre/modules/AddonManager.jsm:745 < 
> AMP_startup()@resource://gre/modules/AddonMan ager.jsm:2318 < 
> AMC_observe()@resource://gre/components/addonManager.js:55 < 
>  ) = 1032
> ...

With the very same profile folder bind-mounted into ~/.icedove on an
ext4 (using 32bit-inodes):
> access("/home/empee584/.icedove/profile/extensions", F_OK) = 0
> stat64("/home/empee584/.icedove/profile/extensions", {st_mode=S_IFDIR|0770, 
> st_size=4096, ...}) = 0
> openat(AT_FDCWD, "/home/empee584/.icedove/profile/extensions", 
> O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 24
> getdents(24, /* 61 entries */, 32768) = 2832
> getdents(24, /* 0 entries */, 32768) = 0
> close(24)   = 0  
> stat64("/home/empee584/.icedove/profile/extensions/{57068FBE-1506-42ee-AB02-BD183E7999E4}",
>  {st_mode=S_IFDIR|0770, st_size=4096, ...})  = 0
> stat64("/home/empee584/.icedove/profile/extensions/{57068FBE-1506-42ee-AB02-BD183E7999E4}",
>  {st_mode=S_IFDIR|0770, st_size=4096, ...})  = 0
> stat64("/home/empee584/.icedove/profile/extensions/{4C9FE6FE-2C83-11DC-90B4-DC8456D89593}",
>  {st_mode=S_IFDIR|0755, st_size=4096, ...})  = 0
> stat64("/home/empee584/.icedove/profile/extensions/{4C9FE6FE-2C83-11DC-90B4-DC8456D89593}",
>  {st_mode=S_IFDIR|0755, st_size=4096, ...})  = 0
> stat64("/home/empee584/.icedove/profile/extensions/{CC3C233D-6668-41bc-AAEB-F3A1D1D594F5}",
>  {st_mode=S_IFDIR|0755, st_size=4096, ...})  = 0
> stat64("/home/empee584/.icedove/profile/extensions/{CC3C233D-6668-41bc-AAEB-F3A1D1D594F5}",
>  {st_mode=S_IFDIR|0755, st_size=4096, ...})  = 0
> ...

chromium seemingly had the problem:
> https://code.google.com/p/nativeclient/issues/detail?id=1253


64-bit icedove reportedly does work with xfs/inode64..
> http://oss.sgi.com/archives/xfs/2013-07/msg00152.html

Running a 32bit distro with >1TeraByte partitions is probably rather
uncommon so I couldn't find a bug reported for this upstream..
just something similar (?) fixed up 4 years ago..
> https://bugzilla.mozilla.org/show_bug.cgi?id=389087
> Bug 389087: nsILocalFileUnix affected by 32bit stat/statvfs/truncate, 
> therefore does not work with large files

> # wget https://raw.githubusercontent.com/gnb/junkcode/master/summarise_stat.pl
> # perl summarise_stat.pl /usr/lib/icedove/
> Summary by status
> -
> 476 97.3% are scripts (shell, perl, whatever)
>  10  2.0% don't use any stat() family calls at all
>   2  0.4% use 32-bit stat() family interfaces only [BROKEN]
>   1  0.2% use both 32-bit and 64-bit stat() 

Bug#751337: [PATCH] tests: test_ctf_writer: replace HOST_NAME_MAX

[Sebastian Andrzej Siewior]

On 2014-08-05 16:14:12 [-0400], Jon Bernard wrote:
> This may also work as well:
> 
> diff --git a/configure.ac b/configure.ac
> index 80eba33..248044e 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -50,6 +50,17 @@ AC_C_INLINE
>  AC_TYPE_PID_T
>  AC_TYPE_SIZE_T
> 
> +# FreeBSD does not define HOST_NAME_MAX
> +AC_CHECK_DECL(HOST_NAME_MAX,,
> +   [
> +AC_CHECK_DECL(_POSIX_HOST_NAME_MAX,
> +  AC_DEFINE(HOST_NAME_MAX, _POSIX_HOST_NAME_MAX, []),
> +  AC_DEFINE(HOST_NAME_MAX, 256, [Define to 256 if 
> neither have HOST_NAME_MAX nor _POSIX_HOST_NAME_MAX]),
> +  [[#include ]])
> +   ],
> +   [[#include ]]
> +)

Sure it will. I have no strong opinion on how it gets fixed :)

> +
>  # Checks for library functions.
>  AC_FUNC_MALLOC
>  AC_FUNC_MMAP
> 

Sebastian


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

Bug#757150:

[Davide Governale]

Il giorno Tue, 5 Aug 2014 22:15:41 +0200
Tomasz Buchert  ha scritto:

> Hi Davide,
> thanks for your information. Did the previous version
> of stellarium work for you? Your GPU is GeForce 7300 SE/7200
> and it seems that it does not support some fragment shader
> functionality (e.g., see
> https://code.google.com/p/flightgear-bugs/issues/detail?id=750). Is
> This bug is not specific to Debian and therefore I'll forward
> it to upstream as they will be probably interested in it.
> 
> I'll keep you informed.
> 
> Cheers,
> Tomasz
> 
> 

Hi Tomasz,

I have installed the package libqt4-opengl, and the software has
successfully started. I think that it's a problem of dependency-on
debian. You see the output now:

$ stellarium
 ---
[ This is Stellarium 0.13.0 - http://www.stellarium.org ]
[ Copyright (C) 2000-2014 Fabien Chereau et al  ]
 ---
Writing log file to: "/home/magellanino/.stellarium/log.txt"
File search paths:
  0 .  "/home/magellanino/.stellarium"
  1 .  "/usr/share/stellarium"
Config file is:  "/home/magellanino/.stellarium/config.ini"
OpenGL versions supported: "1.1, 1.2, 1.3, 1.4, 1.5, 2.0, 2.1"
Driver version string: "2.1.2 NVIDIA 304.123"
GL vendor is "NVIDIA Corporation"
GL renderer is "GeForce 7300 SE/7200 GS/PCIe/SSE2"
Cache directory is:  "/home/magellanino/.cache/stellarium/stellarium"
Sky language is  "it_IT"
Application language is  "it_IT"
Loading Solar System data ...
Found an old starsConfig.json file, upgrade..
Creates file  "/home/magellanino/.stellarium/stars/default/starsConfig.json"
Loading star data ...
"Loading "/usr/share/stellarium/stars/default/stars_0_0v0_5.cat": 0_0v0_2; 4963"
"Loading "/usr/share/stellarium/stars/default/stars_1_0v0_5.cat": 1_0v0_2; 
21598"
"Loading "/usr/share/stellarium/stars/default/stars_2_0v0_5.cat": 2_0v0_2; 
150090"
"Loading "/usr/share/stellarium/stars/default/stars_3_1v0_3.cat": 3_1v0_3; 
428466"
Finished loading star catalogue data, max_geodesic_level:  3
navigation/preset_sky_time is a double - treating as jday: 2.45151e+06
Loaded 10051 NGC records
Loading NGC name data ...
Loaded 416 / 416 NGC name records successfully
Loading star names from 
"/usr/share/stellarium/skycultures/western/star_names.fab"
Loaded 237 / 237 common star names
Loading star names from "/usr/share/stellarium/stars/default/name.fab"
Loaded 4359 / 4359 scientific star names
Loading variable stars from 
"/usr/share/stellarium/stars/default/gcvs_hip_part.dat"
Loaded 6886 / 6886 variable stars
Loaded 88 / 88 constellation records successfully for culture "western"
Loaded 85 / 85 constellation art records successfully for culture "western"
Loaded 89 / 89 constellation names
Loading constellation boundary data ... 
Loaded 782 constellation boundary segments
Intializing basic GL shaders... 
Creating GUI ...
Loaded plugin "Satellites"
Satellites::init copied default satellites.json to  
"/home/magellanino/.stellarium/modules/Satellites/satellites.json"
Satellites: loading catalog file: 
"/home/magellanino/.stellarium/modules/Satellites/satellites.json"
Unable to find module called "TimeZoneConfiguration"
Loaded plugin "TimeZoneConfiguration"
Satellites: starting Internet update...
Satellite added: "02802" "SL-8 R/B"
Satellites: purging objects that were not updated...
Satellite removed: "23833" "GPS BIIA-25 (PRN 03)"
Satellites:  1 satellites proposed for removal,  1  removed,  665  remain.
Satellites::saveTleMap() writing to: 
"/home/magellanino/.stellarium/modules/Satellites/satellites.json"
Satellites: update finished. 664 / 665 updated, 1 added, 1 missing or removed. 
833 source entries parsed.
Creating directory  "/home/magellanino/.stellarium/data"
Unloaded plugin "TimeZoneConfiguration"
Unloaded plugin "Satellites"
Downloaded 0 files (0 kbytes) in a session of 31.515 sec (average of 0 kB/s + 0 
files from cache (0 kB)).

I discovered this by installing the previous version of stellarium. During the 
installation of the old version, it was required dependency libqt4-opengl
# apt-get -t stable install stellarium
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
Alcuni pacchetti non possono essere installati. Questo può voler dire
che è stata richiesta una situazione impossibile oppure, se si sta
usando una distribuzione in sviluppo, che alcuni pacchetti richiesti
non sono ancora stati creati o sono stati rimossi da Incoming.
Le seguenti informazioni possono aiutare a risolvere la situazione:

I seguenti pacchetti hanno dipendenze non soddisfatte:
 stellarium : Dipende: libqt4-opengl (>= 4:4.8.0) ma non sta per essere 
installato
E: Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati.

Kindly,
Davide Governale.


signature.asc
Description: PGP signature