Bug#727665: lintian: FTBFS: Test failures

[Daniel Schepler]

Source: lintian
Version: 2.5.19
Severity: serious

From my pbuilder build log:

...
Running deb-format-ancient-file... building... testing... FAILED
--- t/debs/deb-format-ancient-file/tags 2013-09-23 16:56:58.0 +
+++ /tmp/buildd/lintian-2.5.19/debian/test-out/tags.deb-format-ancient-file
2013-10-25 05:47:47.181164244 +
@@ -1,2 +1 @@
 E: deb-format-ancient-file: package-contains-ancient-file 
usr/share/doc/deb-format-ancient-file/changelog.gz 1970-01-01
-E: deb-format-ancient-file: tar-errors-from-control control: implausibly old 
time stamp 1970-01-01 00:00:00
...
Running cruft-ancient-file... building... testing... FAILED
--- t/source/cruft-ancient-file/tags2013-09-23 16:56:58.0 +
+++ /tmp/buildd/lintian-2.5.19/debian/test-out/tags.cruft-ancient-file  
2013-10-25 05:48:16.737762120 +
@@ -1 +0,0 @@
-I: cruft-ancient-file source: tar-errors-from-source 
cruft-ancient-file-1.0/README: implausibly old time stamp 1970-01-01 00:00:00
...
Running legacy-filenames 1:12-0.1... building... testing... FAILED
legacy-filenames: Can't open 
'/tmp/temp-lintian-lab-eqmZo0u5T7/pool/f/filenames/filenames_1_12-0.1_all_binary/unpacked/usr/share/doc/filenames/bokm\\\ål'
 for reading: 'No such file or directory' at 
/tmp/buildd/lintian-2.5.19/collection/scripts line 93
legacy-filenames: warning: collect info scripts about package filenames failed
legacy-filenames: warning: skipping check of binary package filenames
legacy-filenames: md5sum: usr/share/doc/filenames/bokm\\\ål: No such file or 
directory
legacy-filenames: md5sum: usr/share/doc/filenames/bokm\\\�l: No such file or 
directory
legacy-filenames: internal error: command failed with error code 123 at 
/tmp/buildd/lintian-2.5.19/lib/Lintian/Command.pm line 314.
legacy-filenames: warning: collect info md5sums about package filenames failed
legacy-filenames: warning: skipping check of binary package filenames
legacy-filenames: W: filenames source: no-section-field-for-source
legacy-filenames: W: filenames source: diff-contains-arch-control-dir .arch-ids
legacy-filenames: W: filenames source: diff-contains-bzr-control-dir .bzr
legacy-filenames: W: filenames source: diff-contains-svn-control-dir .svn
legacy-filenames: W: filenames source: diff-contains-cvs-control-dir CVS
internal error: /tmp/buildd/lintian-2.5.19/frontend/lintian --no-user-dirs 
--profile debian --allow-root --no-cfg -I -E 
/tmp/buildd/lintian-2.5.19/debian/test-out/filenames/filenames-1:12-0.1/../filenames_12-0.1_amd64.changes
 exited with status 2 at t/runtests line 573 thread 8.

legacy-filenames: W: filenames source: diff-contains-editor-backup-file 
filenames.c~
legacy-filenames: W: filenames source: diff-contains-arch-control-dir {arch}
legacy-filenames: W: filenames source: diff-contains-cvs-conflict-copy 
files/.#Maelstrom Sound.1.1.1
legacy-filenames: W: filenames source: diff-contains-arch-inventory-file 
files/.arch-inventory
legacy-filenames: W: filenames source: diff-contains-svn-conflict-file 
files/Maelstrom Sounce.r121
legacy-filenames: W: filenames source: diff-contains-svk-commit-file 
files/svk-commitsEr9P.tmp
legacy-filenames: W: filenames source: diff-contains-svn-commit-file 
files/svn-commit.tmp
legacy-filenames: W: filenames source: ancient-standards-version 3.1.1 (current 
is 3.9.4)
legacy-filenames: E: more-filename-games: no-copyright-file
legacy-filenames: W: more-filename-games: package-section-games-but-has-usr-bin
legacy-filenames: W: more-filename-games: binary-without-manpage 
usr/bin/another-test-game
legacy-filenames: W: more-filename-games: binary-without-manpage 
usr/games/yet-another-test-game
legacy-filenames: I: more-filename-games: no-md5sums-control-file
legacy-filenames: E: filename-games: no-copyright-file
legacy-filenames: W: filename-games: no-priority-field
legacy-filenames: E: filename-games: package-section-games-but-contains-no-game
legacy-filenames: I: filename-games: package-contains-empty-directory usr/games/
legacy-filenames: W: filename-games: binary-without-manpage usr/bin/test-game
legacy-filenames: I: filename-games: no-md5sums-control-file
FAILED 
...
Skipped/disabled tests:
  [tests]
binaries-missing-lfs: architecture mismatch
runtests-arch-i386: architecture mismatch
shared-libs-non-pic-i386: architecture mismatch

Failed tests (3)
deb-format-ancient-file
cruft-ancient-file
legacy-filenames
make: *** [runtests] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler


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

Bug#727657: [Debian-med-packaging] Bug#727657: unconditional build dependency on g++-multilib

[Thorsten Alteholz]

Hi Matthias,

On Fri, 25 Oct 2013, Matthias Klose wrote:

uc-echo has an unconditional build dependency on g++-multilib, which is not
available on all architectures.


do you know a better choice?


also, it fails to build on mips* which does have g++-multilib, so it seems that
this package has hardcoded ix86 assumptions.


The problem on mips* is not g++-multilib but the parameter -m64 for gcc. 
Somewhere I read that -mabi=64 is default on mips, but 'gcc -dumpspecs' 
tells me:

  *multilib_defaults:
  EB mips1 mabi=32
I guess I am totally confused now :-(. Can you please point me in the 
right direction?


  Thorsten


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

Bug#726863: pdns: FTBFS on s390x

[Peter van Dijk]

Hello,

On Oct 22, 2013, at 23:31 , Peter van Dijk wrote:

 We now have an upstream patch for this at 
 https://github.com/PowerDNS/pdns/commit/0c3742099d6f94a8928ac5e6eca11f8d3f4cb3ad
 
 Maintainers, please pick this patch up for 3.3-2


With that patch, one failing test remains. 
https://github.com/PowerDNS/pdns/commit/916a0fda31405290cedac058aab7f5d9f9c26a7b
 fixes it. Please pick this patch as well.

Kind regards,
-- 
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#727666: FTBFS: mipsel-linux-gnu-gcc: internal compiler error: Killed (program cc1plus)

[Picca Frédéric-Emmanuel]

Package: python-pytango
Version: 8.0.3-3
Severity: critical
File: pytango


Here the log message during the build on mayer.

/«PKGBUILDDIR»/src/boost/cpp/server/attribute.cpp: In function 'void 
PyAttribute::__set_value_date_quality_array(Tango::Attribute, 
boost::python::api::object, double, Tango::AttrQuality*, long int*, long int*, 
const string, bool)':
/«PKGBUILDDIR»/src/boost/cpp/server/attribute.cpp:267:64: warning: typedef 
'TangoArrayType' locally defined but not used [-Wunused-local-typedefs]
 typedef typename TANGO_const2arraytype(tangoTypeConst) TangoArrayType;
^
mipsel-linux-gnu-gcc: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
error: command 'mipsel-linux-gnu-gcc' failed with exit status 4


I rebuilt it on eder (porter box), (attached the non-FTBFS build log).


what is wrong with mayer ?

cheers

Frederic

-- 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.11-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-pytango depends on:
ii  ipython   0.13.2-2
ii  libboost-python1.54.0 1.54.0-3
ii  libc6 2.17-93
ii  libcos4-1 4.1.6-2
ii  libgcc1   1:4.8.2-1
ii  liblog4tango5 8.1.2c+dfsg-1
ii  libomniorb4-1 4.1.6-2
ii  libomnithread3c2  4.1.6-2
ii  libstdc++64.8.2-1
ii  libtango8 8.1.2c+dfsg-1
ii  libzmq3   3.2.4+dfsg-1
ii  python2.7.5-5
ii  python-numpy [python-numpy-abi9]  1:1.7.1-3

python-pytango recommends no packages.

python-pytango suggests no packages.

-- no debconf information


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

Bug#724731: [gdm3] gdm does not start properly, cannot login via gdm

[Ludovic Lebègue]

It seems to be solved for me after upgrading to 3.8.4-3.


Here are the information regarding each packages that seems involved in
this bug report :

===

gdm3 :

===


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

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

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.34-2
ii  adduser   3.113+nmu3
ii  dconf-cli 0.18.0-1
ii  dconf-gsettings-backend   0.18.0-1
ii  debconf [debconf-2.0] 1.5.51
ii  gir1.2-gdm3   3.8.4-3
ii  gnome-session [x-session-manager] 3.8.4-2
ii  gnome-session-bin 3.8.4-2
ii  gnome-settings-daemon 3.8.5-2
ii  gnome-shell   3.8.4-4
ii  gnome-terminal [x-terminal-emulator]  3.10.1-1
ii  gsettings-desktop-schemas 3.8.2-2
ii  libaccountsservice0   0.6.34-2
ii  libatk1.0-0   2.10.0-2
ii  libaudit1 1:2.3.2-2
ii  libc6 2.17-93
ii  libcairo-gobject2 1.12.16-2
ii  libcairo2 1.12.16-2
ii  libcanberra-gtk3-00.30-2
ii  libcanberra0  0.30-2
ii  libgdk-pixbuf2.0-02.28.2-1
ii  libgdm1   3.8.4-3
ii  libglib2.0-0  2.38.1-1
ii  libglib2.0-bin2.38.1-1
ii  libgtk-3-03.8.6-1
ii  libpam-modules1.1.3-10
ii  libpam-runtime1.1.3-10
ii  libpam0g  1.1.3-10
ii  libpango-1.0-01.36.0-1
ii  libpangocairo-1.0-0   1.36.0-1
ii  librsvg2-common   2.40.0-1
ii  libselinux1   2.1.13-3
ii  libwrap0  7.6.q-24
ii  libx11-6  2:1.6.2-1
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.1-1
ii  libxrandr22:1.4.1-1
ii  lsb-base  4.1+Debian12
ii  metacity [x-window-manager]   1:2.34.13-1
ii  upower0.9.23-2
ii  x11-common1:7.7+4
ii  x11-xserver-utils 7.7+1
ii  xfwm4 [x-window-manager]  4.10.1-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.10.0-1+b1
ii  desktop-base   7.0.3
ii  gnome-icon-theme   3.10.0-1
ii  gnome-icon-theme-symbolic  3.10.1-1
ii  x11-xkb-utils  7.7~1
ii  xserver-xephyr 2:1.14.3-4
ii  xserver-xorg   1:7.7+4
ii  zenity 3.8.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.4.2-2
ii  libpam-gnome-keyring  3.8.2-2

-- debconf information excluded

===

systemd :

===


-- Package-specific info:
--
systemd-delta:
--

0 overridden configuration files found.

--
Contents of /var/lib/systemd/deb-systemd-helper-enabled:
--
== /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
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service

== /var/lib/systemd/deb-systemd-helper-enabled/plymouth.service ==

== 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service 
==

== 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/libvirt-guests.service
 ==

== 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
 ==

== 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service
 ==

== 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/virtlockd.socket
 ==

== 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/libvirt-bin.service
 ==

== /var/lib/systemd/deb-systemd-helper-enabled/plymouth-quit.service.dsh-also 
==
/etc/systemd/system/plymouth.service

== 
/var/lib/systemd/deb-systemd-helper-enabled/plymouth-read-write.service.dsh-also
 ==
/etc/systemd/system/plymouth-log.service

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

== 
/var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/accounts-daemon.service
 ==

== 

Processed: reassign 727666 to buildd.debian.org

[Debian Bug Tracking System]

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

 reassign 727666 buildd.debian.org
Bug #727666 [python-pytango] FTBFS: mipsel-linux-gnu-gcc: internal compiler 
error: Killed (program cc1plus)
Bug reassigned from package 'python-pytango' to 'buildd.debian.org'.
No longer marked as found in versions pytango/8.0.3-3.
Ignoring request to alter fixed versions of bug #727666 to the same values 
previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
727666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727666
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#727668: roundcube:CVE-2013-6172: vulnerability in handling _session argument of utils/save-prefs

[Salvatore Bonaccorso]

Package: roundcube
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for roundcube.

CVE-2013-6172[0]:
vulnerability in handling _session argument of utils/save-prefs

See [1] for further information.

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

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6172
http://security-tracker.debian.org/tracker/CVE-2013-6172
[1] http://roundcube.net/news/2013/10/21/security-updates-095-and-087/
[2] http://trac.roundcube.net/ticket/1489382

Please adjust the affected versions in the BTS as needed (not yet
verified if also roundcube in oldstable/squeeze is affected).

Do you have a chance to prepare packages also for wheezy-security (and
squeeze-security if affected)?

Regards,
Salvatore


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

Bug#721763: [brltty] Idea to get id for free

[Bastien ROUCARIES]

Le 24 oct. 2013 23:31, Samuel Thibault sthiba...@debian.org a écrit :

 bastien ROUCARIES, le Thu 24 Oct 2013 21:51:10 +, a écrit :
  May be we could ask openmoko to get usb/vid/pid for braille stuff ?
 
  see http://wiki.openmoko.org/wiki/USB_Product_IDs

 Sure, but the problem is not the possibility of asking; it is convincing
 the *manufacturers* that they should do it and record the obtained ID in
 their devices.

 Samuel

Fdti and the other one in this thread accept to be reflashed for pid/vid
only. So let reserve a few id on openmoko and ask your user to reflash.

Brltty could be slipt in two package
Brltty that will get support for only well behaved driver and brltty-cruft
for the conflict id stuff.

Debian-install will use both so we will not loose stability but during
install you will be ask to reflash bad behaved serial converter.

Brltty-cruft will not be enable by default except if answer use it during
install.

Bastien

Processed: retitle 727668 to roundcube: CVE-2013-6172: vulnerability in handling _session argument of utils/save-prefs

[Debian Bug Tracking System]

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

 retitle 727668 roundcube: CVE-2013-6172: vulnerability in handling _session 
 argument of utils/save-prefs
Bug #727668 [roundcube] roundcube:CVE-2013-6172: vulnerability in handling 
_session argument of utils/save-prefs
Changed Bug title to 'roundcube: CVE-2013-6172: vulnerability in handling 
_session argument of utils/save-prefs' from 'roundcube:CVE-2013-6172: 
vulnerability in handling _session argument of utils/save-prefs'
 thanks
Stopping processing here.

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


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

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

[Debian Bug Tracking System]

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

 # Friday 25 October  07:03:31 UTC 2013
 # Tagging as pending bugs that are closed by packages in NEW
 # http://ftp-master.debian.org/new.html
 #
 # Source package in NEW: a href=http://packages.qa.debian.org/mono;mono/a
 tags 725279 + pending
Bug #725279 [src:mono] Upgrade to the version 3.2.3
Added tag(s) pending.
 # Source package in NEW: a href=http://packages.qa.debian.org/mono;mono/a
 tags 727542 + pending
Bug #727542 [mono] mono: out of date binaries on sparc and ia64
Added tag(s) pending.
 # Source package in NEW: pytaglib
 tags 696455 + pending
Bug #696455 [wnpp] ITP: pytaglib -- Python 2.x/3.x bindings for the Taglib 
audio, metadata library
Added tag(s) pending.
 # Source package in NEW: maven-shared-utils
 tags 710216 + pending
Bug #710216 [wnpp] ITP: maven-shared-utils -- A replacement for plexus-utils in 
Maven
Added tag(s) pending.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
696455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696455
710216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710216
725279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725279
727542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727542
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#724731: XDG_RUNTIME_DIR has incorrect value

[Gabriel Mainberger]

Same issue for me after upgrading to gdm 3.8.4-3. A black screen after 
starting gdm, except if I chmod 777 /run/user/0.


/var/log/gdm3/:0-slave.log:

gdm-simple-slave[5325]: Failed to give slave programs access to the 
display. Trying to proceed.
gdm-launch-environment][5358]: pam_env(gdm-launch-environment:session): 
Unable to open env file: /etc/environment: Datei oder Verzeichnis nicht 
gefunden
gdm-launch-environment][5358]: pam_unix(gdm-launch-environment:session): 
session opened for user Debian-gdm by (uid=0)
gdm-launch-environment][5358]: 
pam_systemd(gdm-launch-environment:session): Asking logind to create 
session: uid=115 pid=5358 service=gdm-launch-environment type=x11 
class=greeter seat=seat0 vtnr=7 tty= display=:0 remote=no remote_user= 
remote_host=
gdm-launch-environment][5358]: 
pam_systemd(gdm-launch-environment:session): Reply from logind: id=c1 
object_path=/org/freedesktop/login1/session/c1 runtime_path=/run/user/0 
session_fd=13 seat=seat0 vtnr=1
gdm-launch-environment][5358]: 
pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring 
PAM_TTY :0
gdm3][5591]: pam_env(gdm3:session): Unable to open env file: 
/etc/environment: Datei oder Verzeichnis nicht gefunden
gdm3][5591]: pam_unix(gdm3:session): session opened for user gabriel by 
(uid=0)
gdm3][5591]: pam_systemd(gdm3:session): Asking logind to create session: 
uid=1000 pid=5591 service=gdm3 type=x11 class=user seat=seat0 vtnr=7 
tty= display=:0 remote=no remote_user= remote_host=
gdm3][5591]: pam_systemd(gdm3:session): Reply from logind: id=c1 
object_path=/org/freedesktop/login1/session/c1 runtime_path=/run/user/0 
session_fd=15 seat=seat0 vtnr=1

gdm3][5591]: pam_ck_connector(gdm3:session): nox11 mode, ignoring PAM_TTY :0
gdm-launch-environment][5358]: pam_unix(gdm-launch-environment:session): 
session closed for user Debian-gdm
gdm-simple-slave[5325]: Failed to remove slave program access to the 
display. Trying to proceed.

gdm-simple-slave[5325]: Child process -5369 was already dead.
gdm3][5591]: pam_unix(gdm3:session): session closed for user gabriel
gdm-simple-slave[5325]: GLib-GObject: g_object_ref: assertion 
`object-ref_count  0' failed
gdm-simple-slave[5325]: GLib-GObject: g_object_unref: assertion 
`object-ref_count  0' failed


If I login with my user account, I still get the wrong runtime_path.


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

Processed: correct epoch for openchange versions for 701332

[Debian Bug Tracking System]

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

 fixed 701332 1:2.0-1
Bug #701332 {Done: Jelmer Vernooij jel...@samba.org} [src:openchange] 
openchange: ftbfs with GCC-4.8
Bug #707539 {Done: Jelmer Vernooij jel...@samba.org} [src:openchange] 
openchange: FTBFS: exchange.idl:4125: error: EcDoRpc: [out] argument 'size' is 
not a pointer or array, skip client functions
Marked as fixed in versions openchange/1:2.0-1.
Marked as fixed in versions openchange/1:2.0-1.
 notfixed 701332 2:2.0-2
Bug #701332 {Done: Jelmer Vernooij jel...@samba.org} [src:openchange] 
openchange: ftbfs with GCC-4.8
Bug #707539 {Done: Jelmer Vernooij jel...@samba.org} [src:openchange] 
openchange: FTBFS: exchange.idl:4125: error: EcDoRpc: [out] argument 'size' is 
not a pointer or array, skip client functions
The source 'openchange' and version '2:2.0-2' do not appear to match any binary 
packages
No longer marked as fixed in versions openchange/2:2.0-2.
No longer marked as fixed in versions openchange/2:2.0-2.
 notfixed 701332 2:2.0-1
Bug #701332 {Done: Jelmer Vernooij jel...@samba.org} [src:openchange] 
openchange: ftbfs with GCC-4.8
Bug #707539 {Done: Jelmer Vernooij jel...@samba.org} [src:openchange] 
openchange: FTBFS: exchange.idl:4125: error: EcDoRpc: [out] argument 'size' is 
not a pointer or array, skip client functions
The source 'openchange' and version '2:2.0-1' do not appear to match any binary 
packages
No longer marked as fixed in versions openchange/2:2.0-1.
No longer marked as fixed in versions openchange/2:2.0-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701332
707539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707539
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#719943: makedumpfile: fails to dump kernel log, continually appends the line [ 0.000000] to dmesg file

[John Wright]

On Sun, Oct 20, 2013 at 10:25:31PM -0400, Alex Vanderpol wrote:
 Unfortunately I no longer have any of those crash dumps available to
 send you anything, I had sent what I had gotten to the kernel
 maintainers previously in an attempt to track down the cause of the
 crashing, which I don't believe was ever figured out exactly but was
 ultimate fixed in a later kernel version. I don't know if they would
 still happen to have it on hand or not, though.
 
 For what it's worth, there never was a vmcore file created any time
 I did get a dump, instead I always got two separate files, one which
 is the main core dump and one which is supposed to be the dmesg log
 dump which unfortunately was never actually able to be dumped (the
 issue I filed this bug report about). If the end result is supposed
 to be one vmcore file, I suspect the inability of makedumpfile to
 dump the kernel dmesg log prohibited it from combining the two files
 into one file.

It's always two separate files.  They are not meant to be combined - the
dmesg dump is just intended for convenience (you can just read the file
as text instead of opening a dump with crash).

 Using the 'log' command from within crash was ultimately useless as
 well, as the kernel log wasn't dumped, therefore there wasn't any
 log for crash to open.
 
 This issue was with kernel 3.11-rc4-amd64 in its stock configuration.

Not a Debian package?  I'm not sure what you mean when you say stock
configuration.  Do you mean you ran 'make defconfig' to generate the
kernel .config?

 I hope what information I am able to give you proves to be at least
 somewhat useful.

I'm not really sure what you saw. :-/  I'll see if I can reproduce
anything with linux-image-3.11-1-amd64_3.11.5-1_amd64 when I have some
free time (I lost the VM I use for testing this stuff).  It's possible
there was a short-lived bug in the kernel itself, causing some corrupt
representation of its log buffer.

 On 2013-10-20 10:29 PM, John Wright wrote:
 Hi Alex,
 
 On Fri, Aug 16, 2013 at 10:12:39PM -0400, Alex Vanderpol wrote:
 Package: makedumpfile
 Version: 1.5.4-1
 Severity: grave
 Justification: renders package unusable
 
 Dear Maintainer,
 
 There seems to be a serious issue with makedumpfile that causes it to fail 
 to
 dump the kernel log when collecting crash dump information. Instead, the
 program continues to run indefinitely, continually appending the line [
 0.00]  to the file as it seems to attempt to dump the log, which, if 
 left
 alone for any considerable length of time, can rapidly result in a very 
 large,
 entirely useless dmesg dump file.
 
 I have been trying to collect crash dump information for a crash that's
 triggered whenever Folding@Home's FahCore_a4 attempts to resume an 
 in-progress
 work unit, however, every crash dump I've collected has had this problem. 
 The
 main dump file seems to be dumped without a problem (though crash 
 identifies it
 as a partial dump, possibly due to the kernel log being dumped into a 
 separate
 file).
 
 I hope you can look into this issue and hopefully it can be sorted out soon.
 Sorry for the long delay in my response.  This seems like a serious but
 not actually grave issue, since the core dump does actually exist (even
 though you have to interrupt the dmesg extraction).  crash identifies
 the dump as a partial dump because we explicitly ignore zero pages and
 userspace pages.  Within crash, you should be able to use the 'log'
 command to get the most recent log messages before the crash...assuming
 crash doesn't break in the same way makedumpfile does.
 
 I will try to reproduce this, but I worry the problem might be somewhat
 specific either to your crash or some other part of your configuration.
 Would you feel comfortable making the vmcore available to me?  It would
 also help to know the exact kernel version, and access to a dbg package
 if it's not a stock kernel.
 
 Sorry for the issue and thanks for the report!

-- 
John Wright j...@debian.org


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

Bug#719943: makedumpfile: fails to dump kernel log, continually appends the line [ 0.000000] to dmesg file

[Alex Vanderpol]

On 2013-10-25 4:02 AM, John Wright wrote:

On Sun, Oct 20, 2013 at 10:25:31PM -0400, Alex Vanderpol wrote:

Unfortunately I no longer have any of those crash dumps available to
send you anything, I had sent what I had gotten to the kernel
maintainers previously in an attempt to track down the cause of the
crashing, which I don't believe was ever figured out exactly but was
ultimate fixed in a later kernel version. I don't know if they would
still happen to have it on hand or not, though.

For what it's worth, there never was a vmcore file created any time
I did get a dump, instead I always got two separate files, one which
is the main core dump and one which is supposed to be the dmesg log
dump which unfortunately was never actually able to be dumped (the
issue I filed this bug report about). If the end result is supposed
to be one vmcore file, I suspect the inability of makedumpfile to
dump the kernel dmesg log prohibited it from combining the two files
into one file.

It's always two separate files.  They are not meant to be combined - the
dmesg dump is just intended for convenience (you can just read the file
as text instead of opening a dump with crash).


Using the 'log' command from within crash was ultimately useless as
well, as the kernel log wasn't dumped, therefore there wasn't any
log for crash to open.

This issue was with kernel 3.11-rc4-amd64 in its stock configuration.

Not a Debian package?  I'm not sure what you mean when you say stock
configuration.  Do you mean you ran 'make defconfig' to generate the
kernel .config?
What I meant was that it was the kernel image as supplied in the Debian 
repos, without any custom changes of any sort made. I'm sorry if I 
confused you, the correct terminology for some things eludes me at times.

I hope what information I am able to give you proves to be at least
somewhat useful.

I'm not really sure what you saw. :-/  I'll see if I can reproduce
anything with linux-image-3.11-1-amd64_3.11.5-1_amd64 when I have some
free time (I lost the VM I use for testing this stuff).  It's possible
there was a short-lived bug in the kernel itself, causing some corrupt
representation of its log buffer.
I am quite sorry I can't be of any real help here. If I had thought they 
might be necessary at all for this particular bug I would have held onto 
what I got from the crash dumps, but once the bug I was having with the 
kernel was resolved with a later kernel version, and since I'd already 
sent a copy of what I got to the kernel maintainers prior to the newer 
release, I didn't think I needed them anymore and removed them as part 
of my routine cleanup.


It is quite possible that, as the kernel in question was an RC build, 
this issue may have been just one more kink that was ultimately smoothed 
out in the later builds, along with whatever was causing the kernel to 
crash on me whenever Folding@Home tried to resume its current work unit.


Digging back to one of my messages on the kernel bug I filed at the 
time, I mentioned to the kernel maintainers that:


When I run the 'log' command within crash I get this message:
log: WARNING: log buf data structure(s) have changed

and of course, the separate log dump file issue this bug is about.

The first message in the kernel bug thread when I ran into this problem 
with makedumpfile is here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719277#65 if you want 
to have a look, I don't know if there's anything that might be useful 
there as it wasn't long after that I filed this bug.

On 2013-10-20 10:29 PM, John Wright wrote:

Hi Alex,

On Fri, Aug 16, 2013 at 10:12:39PM -0400, Alex Vanderpol wrote:

Package: makedumpfile
Version: 1.5.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

There seems to be a serious issue with makedumpfile that causes it to fail to
dump the kernel log when collecting crash dump information. Instead, the
program continues to run indefinitely, continually appending the line [
0.00]  to the file as it seems to attempt to dump the log, which, if left
alone for any considerable length of time, can rapidly result in a very large,
entirely useless dmesg dump file.

I have been trying to collect crash dump information for a crash that's
triggered whenever Folding@Home's FahCore_a4 attempts to resume an in-progress
work unit, however, every crash dump I've collected has had this problem. The
main dump file seems to be dumped without a problem (though crash identifies it
as a partial dump, possibly due to the kernel log being dumped into a separate
file).

I hope you can look into this issue and hopefully it can be sorted out soon.

Sorry for the long delay in my response.  This seems like a serious but
not actually grave issue, since the core dump does actually exist (even
though you have to interrupt the dmesg extraction).  crash identifies
the dump as a partial dump because we explicitly ignore zero pages and
userspace pages.  Within crash, 

Bug#727607: RabbitMQ allows anyone to connect by default over IPv6

[Emile Joubert]

On 24/10/13 15:34, Thomas Goirand wrote:

 I reported this to the maintainer, and to the security team a *very*
 long time ago, though it seems to be that nothing has been done to
 address this issue.

Your suggestions have not been ignored, and we take feedback on security
issues very seriously.

Please bear in mind that v3.2.0 is the first feature release since June
2013 when the discussion you refer to took place. Entry 24094 from the
release notes is the first step towards a solution:
http://www.rabbitmq.com/release-notes/README-3.2.0.txt
This will allow the broker to report authentication failures explicitly.
This is a feature that AMQP does not offer, so the protocol had to be
extended in a backwards-compatible way.

Only now that the broker can reliably report authentication failures do
we plan to execute the next step, which is to remove the ability to log
in with a default account on a public interface in the default
configuration. (BTW this has nothing to do with IPv6 as suggested in the
bug title.)

I'm sorry you feel disappointed that not enough progress has been made.
We are attempting to introduce this change to the default configuration
in a way that will cause as little disruption as possible. Since the
incidence of authentication failures is expected to rise dramatically it
was deemed necessary to improve their reporting before proceeding.


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

Processed: affects 727666

[Debian Bug Tracking System]

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

 affects 727666 + pytango
Bug #727666 [buildd.debian.org] FTBFS: mipsel-linux-gnu-gcc: internal compiler 
error: Killed (program cc1plus)
Added indication that 727666 affects pytango
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
727666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727666
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#727540: Downgrading libept1.4.12 fix

[Guillaume Seren]

Hi,
I can confirm that downgrading libept1.4.12, fix the symbol 'lookup
error', like :
sudo apt-get -t stable install libept1.4.12


Guillaume.


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

Processed: Found in testing, make RC since DSA for stable was issued

[Debian Bug Tracking System]

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

 found 722724 2.0.20-1
Bug #722724 {Done: Eric Dorland e...@debian.org} [gnupg2] CVE-2013-4351 
gnupg2: gpg2 treats no-usage-permitted keys as all-usages-permitted
Marked as found in versions gnupg2/2.0.20-1.
 found 725433 2.0.20-1
Bug #725433 {Done: Eric Dorland e...@debian.org} [gnupg2] CVE-2013-4402: 
infinite recursion in the compressed packet parser
Marked as found in versions gnupg2/2.0.20-1.
 severity 722724 serious
Bug #722724 {Done: Eric Dorland e...@debian.org} [gnupg2] CVE-2013-4351 
gnupg2: gpg2 treats no-usage-permitted keys as all-usages-permitted
Severity set to 'serious' from 'normal'
 severity 725433 serious
Bug #725433 {Done: Eric Dorland e...@debian.org} [gnupg2] CVE-2013-4402: 
infinite recursion in the compressed packet parser
Severity set to 'serious' from 'normal'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
722724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722724
725433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725433
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#727538: ocaml-sqlexpr: out-of-date binaries on architectures without ocaml-estring

[Stéphane Glondu]

Le 24/10/2013 08:27, Niels Thykier a écrit :
 Your package has out of date binaries on architectures were
 ocaml-estring is unavailable (e.g. armhf), but it appears to have
 built there in the past.  This is a blocker for ocaml-sqlexpr
 migrating to testing[1].
   If ocaml-sqlexpr should no longer be built on these architectures,
 then please reassign this bug to ftp.debian.org and request them to
 remove the binaries on the affected architectures.

Why has this bug been reported against ocaml-sqlexpr? The problem boils
down to ocaml-estring failing to build on some architectures...


Cheers,

-- 
Stéphane


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

Processed: your mail

[Debian Bug Tracking System]

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

 tags 726863 patch
Bug #726863 [pdns] pdns: FTBFS on s390x
Added tag(s) patch.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
726863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726863
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#727659: marked as done (pidgin-skype: API package depends on to disappear)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 12:12:59 +0200
with message-id 201310251213.01167.holger.lev...@profitbricks.com
and subject line it's not december yet and plans may change
has caused the Debian Bug report #727659,
regarding pidgin-skype: API package depends on to disappear
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.)


-- 
727659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pidgin-skype
Version: 20130613+svn660+dfsg-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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

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

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

Tech publication *The Register* reported on 2013-10-25 that 
Skype is expected to terminate its desktop API in December 
2013 which will render this package unusable.  This may 
require removal or severe refactoring upstream.  The story 
containing details can be found here: 
http://www.theregister.co.uk/2013/10/25/skype_petition/


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

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

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

iQIcBAEBAgAGBQJSaew7AAoJELuROrXgYcnAbyYP/3G+0mwKzx8+n8oLlcDrVwMp
5t5/j2OrvmSMt1y+UnmK86+bJzmHEhFyDQ9VurCNYdAASHpN+JAHLr9w8j9J5d6D
tLo8nzqD/Ptxg6ISSifoo0hTOTcZGS9MxUqoSNVhgZJTVm/yoCK/J8M5qG6jGvbQ
hYy5KbYWNC+6bSt5za7U2VUXsjF1Zbx7ZdFjhsRL6QW1aEB7FtvZwG+2OyLAz/KZ
iAwYWiYk+FxDKrcHdd5bkIoakOnGP9+qhP1Yy45PRDZxA1H+LDqHSiX38bGYA3dZ
VuJXCYho8JMS/IU3zWkiwhn+9SFdyS/7vgENUhHQwxNqOZJdoVIC6PbQqf2gisMg
y9Dl0VuekoPkhxFBga6RXtZ0G5VpVrTZRKyDICr52ed+ovvffzdy59rakpNNZO2y
ruO4xyxU1cfQMqr09YSJgnDoZdvS5H5/6EHdCfI2EYspTUzEW4joNfRNRA5XDvXQ
n47dY7JlYrO0LBle2oN4plQxCI/ufd4LtO+ehxUVZqyuEMCRv5mhYx0VHO9jNAS8
J3b+77nqpis0M9V9U/lKPE7j9CFl7cnrNDuKficBI554F6eOWBTHe3GNtOwJIcd3
4pc52A9XZ5rVI0gddaY39crDiQ3tSgqAYVUn32hSo7VOeVkfIF6M8o0QCSKJOrw/
6BNpG6xeRqhms1HeI0ed
=Byif
-END PGP SIGNATURE-
---End Message---
---BeginMessage---
Hi,

it's not december yet and plans may change, thus closing.


cheers,
Holger---End Message---

Processed: closing 727663

[Debian Bug Tracking System]

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

 close 727663 0.4.11-1
Bug #727663 [src:libproxy] libproxy: FTBFS: 
/usr/include/mozjs/mozjs/js/RequiredDefines.h: No such file or directory
Marked as fixed in versions libproxy/0.4.11-1.
Bug #727663 [src:libproxy] libproxy: FTBFS: 
/usr/include/mozjs/mozjs/js/RequiredDefines.h: No such file or directory
Marked Bug as done
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
727663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727663
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#727682: bilibop-rules: Fails to configure: lsbilibop calls udevadm in an unsupported way

[Axel Beckert]

Package: bilibop-rules
Version: 0.4.17
Severity: serious

Dear Maintainer,

I've just dist-upgraded my Debian armhf running Toshiba AC100 (an
ARM-based netbook originally running Android) from Wheezy to Jessie.
As it currently runs of an SD card, installing bilibop sounds like a
good idea.

But bilibop-rules fails to install during configure phase. I've added a
set -x to the package's postinst script to see where it exactly fails:

+ [ false = false ]
+ CUSTOM_RULES=false
+ HELPER=bilibop_rules_generator
+ [ -f /etc/udev/rules.d/66-bilibop.rules ]
+ db_get bilibop-rules/bilibop_rules_generator/customize
+ _db_cmd GET bilibop-rules/bilibop_rules_generator/customize
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET bilibop-rules/bilibop_rules_generator/customize
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=false
+ return 0
+ [ false = true ]
+ [ false = true ]
+ lsbilibop -l
Usage: udevadm info OPTIONS
  --query=type query device information:
  name name of device node
  symlink  pointing to node
  path sys device path
  property the device properties
  all  all values
  --path=syspath   sys device path used for query or attribute walk
  --name=name  node or symlink name used for query or attribute 
walk
  --root prepend dev directory to path names
  --attribute-walk   print all key matches while walking along the chain
 of parent devices
  --device-id-of-file=file print major:minor of device containing this file
  --export   export key/value pairs
  --export-prefixexport the key name with a prefix
  --export-dbexport the content of the udev database
  --cleanup-db   cleanup the udev database
  --help

+ BILIBOP_LIST=
dpkg: error processing bilibop-rules (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of bilibop:
 bilibop depends on bilibop-rules (= 0.4.17); however:
  Package bilibop-rules is not configured yet.

/bin/lsbilibop seems to call udevadm in line 44 as follows:

udev_root=$(udevadm info --root)

But calling udevadm info --root manually on the commandline throws
exactly the above error message. According to the man-page, the --root
option is only thought as additional option for two query types:

   --root
   Print absolute paths in name or symlink query.

So I guess, some more parameters are necessary to get it working
again. I'm just not sure which.

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

Kernel: Linux 2.6.38-ac2-ac100 (SMP w/2 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 bilibop-rules depends on:
ii  bilibop-common 0.4.17
ii  debconf [debconf-2.0]  1.5.51
ii  initramfs-tools0.114
ii  initscripts2.88dsf-43

Versions of packages bilibop-rules recommends:
pn  grub-common  none
pn  lvm2 none
pn  udisks   none

Versions of packages bilibop-rules suggests:
ii  bilibop-lockfs 0.4.17
pn  cryptsetup none
pn  grub-coreboot | grub-efi-amd64 | grub-efi-ia32 | grub-ieee1275 |   none
ii  pmount 0.9.23-2
pn  policykit-1none

-- debconf information:
  bilibop-rules/belongs_to_floppy_group/custom_rules_error:
  bilibop-rules/make_unpersistent_rules: keep
  bilibop-rules/belongs_to_floppy_group/internal_error:
  bilibop-rules/grub_device_map_manager: keep
  bilibop-rules/bilibop_rules_generator/bad_options:
  bilibop-rules/physical_volumes_filter/obtain_device_list_from_udev:
  bilibop-rules/bilibop_rules_generator/options:
* bilibop-rules/on-live-system: false
  bilibop-rules/physical_volumes_filter/system-only: false
  bilibop-rules/physical_volumes_filter/warning:
  bilibop-rules/bilibop_rules_generator/customize: false
  bilibop-rules/physical_volumes_filter/filter:
  bilibop-rules/bilibop_rules_generator/overwrite: keep


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

Bug#707432: fixed by new upstream version (which is already packaged)

[Matthias Klose]

Control: tags -1 + patch

fixed by new upstream version (which is already packaged) by the Debian
maintainer in
https://launchpad.net/~pmiller-opensource/+archive/ppa


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

Bug#727663: closing 727663

[Laurent Bigonville]

close 727663 0.4.11-1
thanks

Hi,

Libproxy 0.4.11-1 is building fine

Closing this bug

Cheers

Laurent Bigonville


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

Processed: tagging 727663

[Debian Bug Tracking System]

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

 tags 727663 + sid jessie
Bug #727663 {Done: Laurent Bigonville bi...@debian.org} [src:libproxy] 
libproxy: FTBFS: /usr/include/mozjs/mozjs/js/RequiredDefines.h: No such file or 
directory
Added tag(s) sid and jessie.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
727663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727663
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 by new upstream version (which is already packaged)

[Debian Bug Tracking System]

Processing control commands:

 tags -1 + patch
Bug #707432 [src:libexplain] libexplain: FTBFS: 
libexplain/buffer/v4l2_buf_flags.c:43:34: error: 'V4L2_BUF_FLAG_INPUT' 
undeclared (first use in this function)
Added tag(s) patch.

-- 
707432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707432
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#727538: ocaml-sqlexpr: out-of-date binaries on architectures without ocaml-estring

[Niels Thykier]

On 2013-10-25 11:55, Stéphane Glondu wrote:
 Le 24/10/2013 08:27, Niels Thykier a écrit :
 Your package has out of date binaries on architectures were
 ocaml-estring is unavailable (e.g. armhf), but it appears to have
 built there in the past.  This is a blocker for ocaml-sqlexpr
 migrating to testing[1].
   If ocaml-sqlexpr should no longer be built on these architectures,
 then please reassign this bug to ftp.debian.org and request them to
 remove the binaries on the affected architectures.
 
 Why has this bug been reported against ocaml-sqlexpr? The problem boils
 down to ocaml-estring failing to build on some architectures...
 
 
 Cheers,
 

One solution would be to fix ocaml-estring, so it builds on these
architectures.  However, ocaml-estring has no obligation[1] to be
built on these architectures, since it was never built on these in the past.
  However, ocaml-sqlexpr built on these architectures in the past, so it
has an obligation to build there again.  But ocaml-sqlexpr picked up an
unconditional Build-Dependency on ocaml-estring, which means it can no
longer be built on these architectures.  This is why I filed this bug
against ocaml-sqlexpr.

This means there are (basically) 3 solutions to this problem:
  1 make ocaml-estring build on these architectures.
  2 make ocaml-sqlexpr's build-depends on ocaml-estring conditional
(i.e. limit it to architectures where ocaml-estring is available)
  3 retire support for architectures without ocmal-estring and reomving
the obligation to be built on these architectures for now.

To be honest, I do not really care which solution you go with.  I just
want a new version of ocaml-sqlexpr to migrate to testing (as it fixes
#718138).

You are welcome to claim that it is reasonably possible for
ocaml-estring to support these architectures and therefore this is a bug
in ocaml-estring.
  However, I am pretty sure you need to convince the maintainer to
accept this or he/she can simply downgrade it to wishlist (possibly with
a wontfix tag) and ocaml-sqlexpr would remain RC buggy.  However, given
the maintainer is the same in this case, I doubt this will be a problem.

~Niels

[1] http://release.debian.org/jessie/rc_policy.txt


4. Autobuilding

[...]

Packages must autobuild without failure on all architectures on
which they are supported. Packages must be supported on as many
architectures as is reasonably possible. Packages are assumed to
be supported on all architectures for which they have previously
built successfully. Prior builds for unsupported architectures
must be removed from the archive (contact -release or ftpmaster
if this is the case).




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

Bug#727607: RabbitMQ allows anyone to connect by default over IPv6

[Thomas Goirand]

Hi Emile,

On 10/25/2013 04:13 PM, Emile Joubert wrote:
 On 24/10/13 15:34, Thomas Goirand wrote:
 
 I reported this to the maintainer, and to the security team a *very*
 long time ago, though it seems to be that nothing has been done to
 address this issue.
 
 Your suggestions have not been ignored, and we take feedback on security
 issues very seriously.

It's good to read this! :)

 Please bear in mind that v3.2.0 is the first feature release since June
 2013 when the discussion you refer to took place. Entry 24094 from the
 release notes is the first step towards a solution:
 http://www.rabbitmq.com/release-notes/README-3.2.0.txt
 This will allow the broker to report authentication failures explicitly.
 This is a feature that AMQP does not offer, so the protocol had to be
 extended in a backwards-compatible way.
 
 Only now that the broker can reliably report authentication failures do
 we plan to execute the next step, which is to remove the ability to log
 in with a default account on a public interface in the default
 configuration. (BTW this has nothing to do with IPv6 as suggested in the
 bug title.)

As much as I can see, there's no problem with IPv4 only (eg: RabbitMQ
would not bind on the public interface by default). Am I wrong to say
that the server only binds on the local public IPv6? If so, feel free to
fix the title of the bug.

 I'm sorry you feel disappointed that not enough progress has been made.
 We are attempting to introduce this change to the default configuration
 in a way that will cause as little disruption as possible. Since the
 incidence of authentication failures is expected to rise dramatically it
 was deemed necessary to improve their reporting before proceeding.

Unfortunately, this public bug report has very little to do with the
fact that there's not enough progress. It has everything to do with
the fact that I have discussed the issue publicly, and that I'm writing
this on a publicly available documentation (eg: OpenStack), so I felt
that this issue had to be available on the Debian BTS as well. I hope
you understand that, and that you don't mind too much that I reported it
this way.

Cheers,

Thomas Goirand


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

Bug#720419: Switching from openmpi to mpich2 on ia64?

[Mathieu Malaterre]

On Thu, Oct 24, 2013 at 11:04 PM, Michael Banck mba...@debian.org wrote:
 The 1.6 release of openmpi fails badly on ia64, see Bug #720419.  As no
 solution appears to be forthcoming, maybe the best would be to remove
 ia64 from openmpi's arch list and switch to mpich2 as default
 implementation for mpi-default-{bin,dev}?

Why bother ? Itanium support is being dropped. At least this what I
understood from a RM request on my of my package:

http://bugs.debian.org/727600

2cts


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

Bug#720419: Switching from openmpi to mpich2 on ia64?

[Mathieu Malaterre]

On Fri, Oct 25, 2013 at 1:18 PM, Mathieu Malaterre ma...@debian.org wrote:
 On Thu, Oct 24, 2013 at 11:04 PM, Michael Banck mba...@debian.org wrote:
 The 1.6 release of openmpi fails badly on ia64, see Bug #720419.  As no
 solution appears to be forthcoming, maybe the best would be to remove
 ia64 from openmpi's arch list and switch to mpich2 as default
 implementation for mpi-default-{bin,dev}?

 Why bother ? Itanium support is being dropped. At least this what I
 understood from a RM request on my of my package:

 http://bugs.debian.org/727600

Sorry misread the bug description, it only applied to upstream Mono. I
got confused with the recent mail from Niels [*], where no porter for
ia64 showed up.

Anyone knows what's the actual status of Itanium then ?

[*] https://lists.debian.org/debian-release/2013/10/msg00071.html


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

Bug#720419: Switching from openmpi to mpich2 on ia64?

[Michael Banck]

On Fri, Oct 25, 2013 at 01:23:56PM +0200, Mathieu Malaterre wrote:
 On Fri, Oct 25, 2013 at 1:18 PM, Mathieu Malaterre ma...@debian.org wrote:
  On Thu, Oct 24, 2013 at 11:04 PM, Michael Banck mba...@debian.org wrote:
  The 1.6 release of openmpi fails badly on ia64, see Bug #720419.  As no
  solution appears to be forthcoming, maybe the best would be to remove
  ia64 from openmpi's arch list and switch to mpich2 as default
  implementation for mpi-default-{bin,dev}?
 
  Why bother ? Itanium support is being dropped. At least this what I
  understood from a RM request on my of my package:
 
  http://bugs.debian.org/727600
 
 Sorry misread the bug description, it only applied to upstream Mono. I
 got confused with the recent mail from Niels [*], where no porter for
 ia64 showed up.
 
 Anyone knows what's the actual status of Itanium then ?

Well, chances are ia64 will be dropped for jessie, but waiting for this
is not a solution for the openmpi 1.6 transition, which is taking place
right now and is being held up by 1.6 not working on ia64.


Michael


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

Processed: Re: Found in testing, make RC since DSA for stable was issued

[Debian Bug Tracking System]

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

 severity 722724 normal
Bug #722724 {Done: Eric Dorland e...@debian.org} [gnupg2] CVE-2013-4351 
gnupg2: gpg2 treats no-usage-permitted keys as all-usages-permitted
Severity set to 'normal' from 'serious'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
722724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722724
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#720419: Switching from openmpi to mpich2 on ia64?

[Anton Gladky]

Just a side note. I would then recommend mpich instead of mpich2, as the
current mpich version os 3.0.4 e.g. mpich3 [1].

[1] http://packages.debian.org/source/testing/mpich

Anton


2013/10/24 Michael Banck mba...@debian.org:
 Hello,

 The 1.6 release of openmpi fails badly on ia64, see Bug #720419.  As no
 solution appears to be forthcoming, maybe the best would be to remove
 ia64 from openmpi's arch list and switch to mpich2 as default
 implementation for mpi-default-{bin,dev}?

 I built aces3 on merulo.debian.org with mpich2, and did not encounter
 any problem, are there known issues with mpich2 on ia64?


 Michael


 --
 To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/20131024210456.gg7...@raptor.chemicalconnection.dyndns.org



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

Bug#721763: [brltty] Idea to get id for free

[Samuel Thibault]

Bastien ROUCARIES, le Fri 25 Oct 2013 08:55:48 +0200, a écrit :
 Fdti and the other one in this thread accept to be reflashed for pid/vid only.
 So let reserve a few id on openmoko and ask your user to reflash.

I don't think a user will dare to reflash his braille device. Those cost
thousands of dollars and are typically the only way their owners would
be able to use a computer.

 Brltty could be slipt in two package
 Brltty that will get support for only well behaved driver and brltty-cruft for
 the conflict id stuff.

That could still be an idea worth considering.

 Brltty-cruft will not be enable by default except if answer use it during
 install.

Well, that is *already* what is supposed to happen.  I'm not aware of
any other way brltty would end up being installed on a Debian system
without the user explicitly requesting it.

(except when starting from an Ubuntu system, but we can't really control
that).

Samuel


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

Bug#727140: order of conf files

[Hontvári József Levente]

I would add, that creating the link
/etc/apache2/conf-available/dokuwiki.conf is not enough if dokuwiki is
installed in the root path, e.g. wiki.example.com. In that case
javascript-common.conf, which is dependency, will be read only after
dokuwiki.conf. The order is important, the javascript-common Alias
/javascript /usr/share/javascript/ directive must come first, before
the  dokuwiki Alias / /usr/share/dokuwiki/ directive. Using the link
name zzzdokuwiki.conf, for example, solves the ordering issue.

I do not know Apache2 enough, but I guess a more elegant solution would
be to adding dokuwiki to apache as a virtual host, instead of a server
level configuration. In that case the name of the link would not affect
the behavior.


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

Bug#713192: virtuoso-opensource: FTBFS: /bin/sh: 1: aclocal-1.11: not found

[Hideki Yamane]

On Fri, 25 Oct 2013 00:21:32 -0300
Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote:
 I don't understand why you add subdir-objects. The FTBFS seems to come from 
 outdated autotools stuff.

 Oops, please get rid of it, I was confused with other packages' FTBFS
 issue (try to fix almost 50 packages, so forgive me... ;)

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane


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

Bug#713209: libmpc: FTBFS: /bin/sh: 1: aclocal-1.11: not found

[Hideki Yamane]

Control: tags -1 +patch

Hi,

 Attached patch would fix this FTBFS, could you check and consider to 
 apply it, please?

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
diff -Nru libmpc-0.1~r459/debian/changelog libmpc-0.1~r459/debian/changelog
--- libmpc-0.1~r459/debian/changelog	2012-06-21 16:39:19.0 +0900
+++ libmpc-0.1~r459/debian/changelog	2013-10-22 16:25:03.0 +0900
@@ -1,3 +1,15 @@
+libmpc (2:0.1~r459-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+- auto detect aclocal/automake/autoconf version (Closes: #713209)
+- include autoreconf.mk to add config/compile file
+  * debian/control
+- add Build-Depends: dh-autoreconf to provide above autreconf.mk
+  * debian/patches
+- add add_subdir-objects.patch for automake
+
+ -- Hideki Yamane henr...@debian.org  Tue, 22 Oct 2013 16:11:05 +0900
+
 libmpc (2:0.1~r459-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru libmpc-0.1~r459/debian/control libmpc-0.1~r459/debian/control
--- libmpc-0.1~r459/debian/control	2012-06-18 03:52:44.0 +0900
+++ libmpc-0.1~r459/debian/control	2013-10-22 16:15:51.0 +0900
@@ -9,6 +9,7 @@
gnulib,
automake,
autoconf,
+   dh-autoreconf,
libtool,
pkg-config,
libreplaygain-dev (= 1.0~r412),
diff -Nru libmpc-0.1~r459/debian/patches/add_subdir-objects.patch libmpc-0.1~r459/debian/patches/add_subdir-objects.patch
--- libmpc-0.1~r459/debian/patches/add_subdir-objects.patch	1970-01-01 09:00:00.0 +0900
+++ libmpc-0.1~r459/debian/patches/add_subdir-objects.patch	2013-10-22 19:47:40.0 +0900
@@ -0,0 +1,16 @@
+Description: avoid automake error
+Author: Hideki Yamane henr...@debian.org
+Forwarded: no
+Last-Update: 2013-10-23
+
+--- libmpc-0.1~r459.orig/configure.in
 libmpc-0.1~r459/configure.in
+@@ -3,7 +3,7 @@ AC_CONFIG_AUX_DIR([config])
+ AC_CONFIG_MACRO_DIR([m4])
+ AC_CONFIG_SRCDIR([libmpcdec/mpc_reader.c])
+ AM_CONFIG_HEADER([include/config.h])
+-AM_INIT_AUTOMAKE
++AM_INIT_AUTOMAKE(subdir-objects)
+ AM_MAINTAINER_MODE
+ 
+ AC_LANG_C
diff -Nru libmpc-0.1~r459/debian/patches/series libmpc-0.1~r459/debian/patches/series
--- libmpc-0.1~r459/debian/patches/series	2012-06-21 16:13:44.0 +0900
+++ libmpc-0.1~r459/debian/patches/series	2013-10-22 16:16:44.0 +0900
@@ -3,3 +3,4 @@
 03_mpcchap.patch
 04_link-order.patch
 1001_missing_extern_kw.patch
+add_subdir-objects.patch
diff -Nru libmpc-0.1~r459/debian/rules libmpc-0.1~r459/debian/rules
--- libmpc-0.1~r459/debian/rules	2012-06-18 03:43:41.0 +0900
+++ libmpc-0.1~r459/debian/rules	2013-10-22 16:15:21.0 +0900
@@ -3,14 +3,15 @@
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
 include /usr/share/cdbs/1/rules/utils.mk
+include /usr/share/cdbs/1/rules/autoreconf.mk
 
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
 DEB_AUTO_UPDATE_LIBTOOL = pre
-DEB_AUTO_UPDATE_ACLOCAL = 1.11
-DEB_AUTO_UPDATE_AUTOCONF = 2.67
-DEB_AUTO_UPDATE_AUTOHEADER = 2.67
-DEB_AUTO_UPDATE_AUTOMAKE = 1.11
+DEB_AUTO_UPDATE_ACLOCAL = $(shell dpkg -s automake | perl -nle '/^Version: (?:\d:)?(\d+\.\d+)?/ and print $$1')
+DEB_AUTO_UPDATE_AUTOCONF = $(shell dpkg -s autoconf | perl -nle '/^Version: (?:\d:)?(\d+\.\d+)?/ and print $$1')
+DEB_AUTO_UPDATE_AUTOMAKE = $(shell dpkg -s automake | perl -nle '/^Version: (?:\d:)?(\d+\.\d+)?/ and print $$1')
+DEB_AUTO_UPDATE_AUTOHEADER = $(shell dpkg -s autoheader | perl -nle '/^Version: (?:\d:)?(\d+\.\d+)?/ and print $$1')
 
 common-binary-post-install-arch:: list-missing
 

Bug#727682: bilibop-rules: Fails to configure: lsbilibop calls udevadm in an unsupported way

[quidame]

Hi,

On 25/10/2013 12:24, Axel Beckert wrote:
 
 But bilibop-rules fails to install during configure phase. I've added a
 set -x to the package's postinst script to see where it exactly fails:
 
 [...]
 
 /bin/lsbilibop seems to call udevadm in line 44 as follows:
 
 udev_root=$(udevadm info --root)
 
 But calling udevadm info --root manually on the commandline throws
 exactly the above error message. According to the man-page, the --root
 option is only thought as additional option for two query types:

Oh my bad, you're right. This no more works since udev is now a part of
systemd. I wil fix it today, thanks for your detailed report.

Cheers,
quidame



signature.asc
Description: OpenPGP digital signature

Processed: RE: libmpc: FTBFS: /bin/sh: 1: aclocal-1.11: not found

[Debian Bug Tracking System]

Processing control commands:

 tags -1 +patch
Bug #713209 [src:libmpc] libmpc: FTBFS: /bin/sh: 1: aclocal-1.11: not found
Added tag(s) patch.

-- 
713209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713209
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#721763: [brltty] Idea to get id for free

[Bastien ROUCARIES]

On Fri, Oct 25, 2013 at 1:45 PM, Samuel Thibault sthiba...@debian.org wrote:
 Bastien ROUCARIES, le Fri 25 Oct 2013 08:55:48 +0200, a écrit :
 Fdti and the other one in this thread accept to be reflashed for pid/vid 
 only.
 So let reserve a few id on openmoko and ask your user to reflash.

 I don't think a user will dare to reflash his braille device. Those cost
 thousands of dollars and are typically the only way their owners would
 be able to use a computer.

Changind vid/pid of usb adaptater is ultra low risk. You could always
do it in reverse. And if manufacturer but the usb logo on their
product it is violation of FTDI usb forum trademark so we could prod
the manufactuer.


 Brltty could be slipt in two package
 Brltty that will get support for only well behaved driver and brltty-cruft 
 for
 the conflict id stuff.

 That could still be an idea worth considering.

 Brltty-cruft will not be enable by default except if answer use it during
 install.

 Well, that is *already* what is supposed to happen.  I'm not aware of
 any other way brltty would end up being installed on a Debian system
 without the user explicitly requesting it.

 (except when starting from an Ubuntu system, but we can't really control
 that).

 Samuel


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

Bug#727660: gnutls28: CVE-2013-4466: GNUTLS-SA-2013-3

[Daniel Kahn Gillmor]

On 10/25/2013 12:20 AM, Salvatore Bonaccorso wrote:

 CVE-2013-4466[0]:
 gnutls/libdane buffer overflow
 
 This only affects 3.1.x and 3.2.x so, gnutls28. A patch [1] is
 provided (upstream recomendation is to directly update to 3.2.5, see
 [2]).

Is this relevant for debian, given that we build with --disable-libdane?

btw, it's not clear to me why we --disable-libdane -- I see that it was
set (along with --without-tpm) in 3.1.3-1, but i don't see the reason
for it.  could that be clarified someplace?

--dkg



signature.asc
Description: OpenPGP digital signature

Bug#720419: Switching from openmpi to mpich2 on ia64?

[Sylvestre Ledru]

On 25/10/2013 13:25, Michael Banck wrote:
 On Fri, Oct 25, 2013 at 01:23:56PM +0200, Mathieu Malaterre wrote:
 On Fri, Oct 25, 2013 at 1:18 PM, Mathieu Malaterre ma...@debian.org wrote:
 On Thu, Oct 24, 2013 at 11:04 PM, Michael Banck mba...@debian.org wrote:
 The 1.6 release of openmpi fails badly on ia64, see Bug #720419.  As no
 solution appears to be forthcoming, maybe the best would be to remove
 ia64 from openmpi's arch list and switch to mpich2 as default
 implementation for mpi-default-{bin,dev}?
 Why bother ? Itanium support is being dropped. At least this what I
 understood from a RM request on my of my package:

 http://bugs.debian.org/727600
 Sorry misread the bug description, it only applied to upstream Mono. I
 got confused with the recent mail from Niels [*], where no porter for
 ia64 showed up.

 Anyone knows what's the actual status of Itanium then ?
 Well, chances are ia64 will be dropped for jessie, but waiting for this
 is not a solution for the openmpi 1.6 transition, which is taking place
 right now and is being held up by 1.6 not working on ia64.

I did quite some work with upstream regarding openmpi on ia64 but
without success for now.
I have to go back on the subject but I have been busy lately (and
knowing that ia64 is going to
be removed does not increase my motivation).
:(
Sylvestre


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

Bug#727660: marked as done (gnutls28: CVE-2013-4466: GNUTLS-SA-2013-3)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 17:18:56 +0200
with message-id 20131025151856.GA30348@eldamar.local
and subject line Re: Bug#727660: gnutls28: CVE-2013-4466: GNUTLS-SA-2013-3
has caused the Debian Bug report #727660,
regarding gnutls28: CVE-2013-4466: GNUTLS-SA-2013-3
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.)


-- 
727660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gnutls28
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for gnutls28.

CVE-2013-4466[0]:
gnutls/libdane buffer overflow

This only affects 3.1.x and 3.2.x so, gnutls28. A patch [1] is
provided (upstream recomendation is to directly update to 3.2.5, see
[2]).

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

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4466
http://security-tracker.debian.org/tracker/CVE-2013-4466
[1] 
https://gitorious.org/gnutls/gnutls/commit/ed51e5e53cfbab3103d6b7b85b7ba4515e4f30c3
[2] http://www.gnutls.org/security.html#GNUTLS-SA-2013-3

Regards,
Salvatore
---End Message---
---BeginMessage---

Hi Daniel,

On Fri, Oct 25, 2013 at 09:56:58AM -0400, Daniel Kahn Gillmor wrote:
 On 10/25/2013 12:20 AM, Salvatore Bonaccorso wrote:

  CVE-2013-4466[0]:
  gnutls/libdane buffer overflow
 
  This only affects 3.1.x and 3.2.x so, gnutls28. A patch [1] is
  provided (upstream recomendation is to directly update to 3.2.5, see
  [2]).

 Is this relevant for debian, given that we build with --disable-libdane?

Thanks for this heads-up. I missed this part when checking for the
mentioned CVE. Apologies for the mistaken bugreport.

 btw, it's not clear to me why we --disable-libdane -- I see that it was
 set (along with --without-tpm) in 3.1.3-1, but i don't see the reason
 for it.  could that be clarified someplace?

I'm closing the bugreport regarding, CVE-2013-4466. But it still is
valid, to clarify the above if possible?

Thanks Daniel again.

Regards,
Salvatore---End Message---

Bug#727628: This bug affects me too in Wheezy and is really nasty

[Ingo]

I do hope we get the fix backported to Wheezy soon.

/Ingo


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

Processed: tagging 649038, tagging 649038

[Debian Bug Tracking System]

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

 tags 649038 - wontfix
Bug #649038 [elfutils] elfutils FTBFS on kfreebsd
Removed tag(s) wontfix.
 tags 649038 + help
Bug #649038 [elfutils] elfutils FTBFS on kfreebsd
Added tag(s) help.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
649038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649038
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#723051: marked as done (scorched3d: FTBFS: config.status: error: cannot find input file: `Makefile.in')

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 15:51:58 +
with message-id e1vzjg6-vw...@franck.debian.org
and subject line Bug#723051: fixed in scorched3d 43.3+dfsg-1
has caused the Debian Bug report #723051,
regarding scorched3d: FTBFS: config.status: error: cannot find input file: 
`Makefile.in'
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.)


-- 
723051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: scorched3d
Version: 43.2a.dfsg-6.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130915 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
 checking iconv.h usability... yes
 checking iconv.h presence... yes
 checking for iconv.h... yes
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: error: cannot find input file: `Makefile.in'
 make[1]: *** [override_dh_auto_configure] Error 1
 make[1]: Leaving directory `/«PKGBUILDDIR»'

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/15/scorched3d_43.2a.dfsg-6.1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: scorched3d
Source-Version: 43.3+dfsg-1

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

Debian distribution maintenance software
pp.
Juhani Numminen juhaninummin...@gmail.com (supplier of updated scorched3d 
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, 21 Oct 2013 15:51:38 +0300
Source: scorched3d
Binary: scorched3d scorched3d-dbg scorched3d-data
Architecture: source amd64 all
Version: 43.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
Changed-By: Juhani Numminen juhaninummin...@gmail.com
Description: 
 scorched3d - 3D artillery game similar to Scorched Earth
 scorched3d-data - data files for Scorched3D game
 scorched3d-dbg - 3D artillery game similar to Scorched Earth, debug data
Closes: 634843 662497 723051
Changes: 
 scorched3d (43.3+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Stephen M. Webb ]
   * new upstream release
   * added myself as an uploader
   * refreshed debian/patches/01-openal-pkgconfig.diff
   * update to debhelper compat level 9
   * removed embedded copy of GLEW library (closes: #634843)
 - removed lintian overrides
   * added dpkg Pre-Depends to -dbg and -data packages for xz compression
   * replaced the embedded copy of DejaVuCondensedBold font with the system one
 .
   [ Juhani Numminen ]
   * Build-Depend on libpng-dev instead of libpng12-dev (Closes: #662497).
   * Update of debian/rules to dh 9 by Stephen M. Webb eliminates cannot find
 Makefile.in FTBFS (Closes: #723051).
   * Set urgency to medium due to fix for release-critical bug.
   * Update standards version to 3.9.4. No changes were necessary.
   * Correct Vcs-* URLs to point to anonscm.debian.org.
   * Add missing patch metadata and unify patch style.
   * Add 0005-append-buildflags.patch to enable hardening.
   * Refer to GPL-2 instead of unversioned GPL in debian/copyright.
   * Add keywords to scorched3d.desktop file.
Checksums-Sha1: 
 a60bd3baec04ce961cc63946cf222acf868802a1 1847 scorched3d_43.3+dfsg-1.dsc
 c64b3efdbe8cc3222e365a1b81b56291f2fbe507 68795472 
scorched3d_43.3+dfsg.orig.tar.xz
 1f20cd46ecdfebd513af7f9f64fded3a2e87a799 119056 
scorched3d_43.3+dfsg-1.debian.tar.xz
 0dfc99da37136d9caee7d98ddbbc2796406583a5 1512434 
scorched3d_43.3+dfsg-1_amd64.deb
 09cb50579974a80ed8dddfb01d5da52eb4206a78 27710164 

Bug#720239: marked as done (ruby-mustache: FTBFS with ruby2.0: ERROR: Test ruby2.0 failed.)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 15:51:18 +
with message-id e1vzjfs-my...@franck.debian.org
and subject line Bug#720239: fixed in ruby-mustache 0.99.4-4
has caused the Debian Bug report #720239,
regarding ruby-mustache: FTBFS with ruby2.0: ERROR: Test ruby2.0 failed.
to be marked as done.

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

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


-- 
720239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ruby-mustache
Version: 0.99.4-3
Severity: important
Tags: jessie sid
User: debian-r...@lists.debian.org
Usertags: ruby2-ftbfs-20130818 ruby2-ftbfs
Justification: FTBFS on amd64 with ruby2.0

Hi,

During a rebuild of all packages that build depends on gem2deb
using the new ruby2.0 interpreter, your package failed to build
on amd64.

Relevant part (hopefully):
 /usr/lib/ruby/2.0.0/minitest/unit.rb:867:in `_run_anything'
 /usr/lib/ruby/2.0.0/minitest/unit.rb:1060:in `run_tests'
 /usr/lib/ruby/2.0.0/minitest/unit.rb:1047:in `block in _run'
 /usr/lib/ruby/2.0.0/minitest/unit.rb:1046:in `each'
 /usr/lib/ruby/2.0.0/minitest/unit.rb:1046:in `_run'
 /usr/lib/ruby/2.0.0/minitest/unit.rb:1035:in `run'
 /usr/lib/ruby/2.0.0/test/unit.rb:21:in `run'
 /usr/lib/ruby/2.0.0/test/unit.rb:774:in `run'
 /usr/lib/ruby/2.0.0/test/unit.rb:366:in `block (2 levels) in autorun'
 /usr/lib/ruby/2.0.0/test/unit.rb:27:in `run_once'
 /usr/lib/ruby/2.0.0/test/unit.rb:365:in `block in autorun'
 
 87 tests, 111 assertions, 0 failures, 1 errors, 0 skips
 
 ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux-gnu]
 ERROR: Test ruby2.0 failed.

The full build log is available from:
  
http://aws-logs.debian.net/ftbfs-logs/ruby2.0/ruby-mustache_0.99.4-3_unstable_ruby2.log

This build is part of an effort to add gem2deb support for ruby2.0.
Information about is available at https://wiki.debian.org/Teams/Ruby/Jessie.

About the rebuild: The rebuild was done on EC2 VM instances from Amazon Web 
Services,
using a clean, minimal and up-to-date chroot, plus gem2deb and ruby2.0 packages 
from
the repository at http://people.debian.org/~terceiro/packages/. The gem2deb 
version
in that repository does not pull ruby1.8 as a dependency anymore, and builds 
packages
against ruby1.9.1 and ruby2.0. Every failed build was retried once to eliminate 
random
failures.

The version of gem2deb used for this rebuild, as well as ruby2.0,
will be uploaded to unstable soon.
---End Message---
---BeginMessage---
Source: ruby-mustache
Source-Version: 0.99.4-4

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

Debian distribution maintenance software
pp.
Cédric Boutillier bou...@debian.org (supplier of updated ruby-mustache 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Oct 2013 16:32:24 +0200
Source: ruby-mustache
Binary: ruby-mustache
Architecture: source all
Version: 0.99.4-4
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras Maintainers 
pkg-ruby-extras-maintain...@lists.alioth.debian.org
Changed-By: Cédric Boutillier bou...@debian.org
Description: 
 ruby-mustache - Mustache is a framework-agnostic way to render logic-free views
Closes: 720239
Changes: 
 ruby-mustache (0.99.4-4) unstable; urgency=low
 .
   * Team upload
   * Bump Standards-Version: to 3.9.4 (no changes needed)
   * Add Vcs-* fields in debian/control
   * Extend fix-encoding patch to all versions of Ruby defining Encoding
 This fixes FTBFS with ruby2.0 (Closes: #720239)
Checksums-Sha1: 
 2492e814f540ee7e2e3502fbbb2e106f28bb3f98 2058 ruby-mustache_0.99.4-4.dsc
 4363cc5077db02b49d641980af0935d80eed2107 2839 
ruby-mustache_0.99.4-4.debian.tar.gz
 3d45f5691412d41e1eb22c6b3b7c9f4347250263 26352 ruby-mustache_0.99.4-4_all.deb
Checksums-Sha256: 
 20417173689dbedac56c276790f06abc6730e044658ef65e5d1adc62d17505df 2058 
ruby-mustache_0.99.4-4.dsc
 62a6703d6792f0f84309aa84e4d3faf5714e9b16b550692ecdda24a33ff45860 2839 
ruby-mustache_0.99.4-4.debian.tar.gz
 

Bug#725347: marked as done (mpqc: depends on deprecated Tcl/Tk 8.4)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 15:51:11 +
with message-id e1vzjfl-k8...@franck.debian.org
and subject line Bug#725347: fixed in mpqc 2.3.1-15
has caused the Debian Bug report #725347,
regarding mpqc: depends on deprecated Tcl/Tk 8.4
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.)


-- 
725347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: mpqc
Version: 2.3.1-14
Severity: normal
Tags: patch

Dear Maintainer,

We plan to remove an obsolete Tcl/Tk 8.4 from the Debian archive before jessie
release. And appears that mpqc build-depends and mpqc-support depends on tk8.4 |
wish. So, it's better to remove tk8.4 dependency by replacing the whole thing
by just tk (tk pulls the current default tk8.* package, tk8.5 in sid, tk8.6 in
experimental and soon in sid).

I've prepared a small patch which does exactly that.

-- System Information:
Debian Release: 7.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru mpqc-2.3.1/debian/changelog mpqc-2.3.1/debian/changelog
--- mpqc-2.3.1/debian/changelog	2012-03-24 14:16:57.0 +0400
+++ mpqc-2.3.1/debian/changelog	2013-10-04 16:06:36.0 +0400
@@ -1,3 +1,10 @@
+mpqc (2.3.1-14.1) unstable; urgency=low
+
+  * Non-maintaoner upload.
+  * Switched to the default tk dependency from an obsolete tk8.4.
+
+ -- Sergei Golovan sgolo...@debian.org  Fri, 04 Oct 2013 16:06:30 +0400
+
 mpqc (2.3.1-14) unstable; urgency=low
 
   * debian/rules (override_dh_auto_test): Set OMPI_MCA_plm_rsh_agent
diff -Nru mpqc-2.3.1/debian/control mpqc-2.3.1/debian/control
--- mpqc-2.3.1/debian/control	2012-02-17 03:12:34.0 +0400
+++ mpqc-2.3.1/debian/control	2013-10-04 16:05:27.0 +0400
@@ -17,7 +17,7 @@
mpi-default-bin,
mpi-default-dev,
perl,
-   tk8.4 | wish
+   tk
 Standards-Version: 3.9.2
 Homepage: http://www.mpqc.org
 Vcs-Browser: http://svn.debian.org/wsvn/debichem/unstable/mpqc/
@@ -127,7 +127,7 @@
 
 Package: mpqc-support
 Architecture: any
-Depends: mpqc, tk8.4 | wish, ${misc:Depends}, ${perl:Depends}, ${shlibs:Depends}
+Depends: mpqc, tk, ${misc:Depends}, ${perl:Depends}, ${shlibs:Depends}
 Description: Massively Parallel Quantum Chemistry Program (support tools)
  MPQC is an ab-inito quantum chemistry program.  It is especially designed
  to compute molecules in a highly parallelized fashion.
---End Message---
---BeginMessage---
Source: mpqc
Source-Version: 2.3.1-15

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

Debian distribution maintenance software
pp.
Michael Banck mba...@debian.org (supplier of updated mpqc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 24 Oct 2013 20:53:09 +0200
Source: mpqc
Binary: mpqc mpqc-openmpi libsc-dev libsc7 libsc-data libsc-doc mpqc-support
Architecture: source amd64 all
Version: 2.3.1-15
Distribution: unstable
Urgency: low
Maintainer: Michael Banck mba...@debian.org
Changed-By: Michael Banck mba...@debian.org
Description: 
 libsc-data - Scientific Computing Toolkit (basis set and atom data)
 libsc-dev  - Scientific Computing Toolkit (development files)
 libsc-doc  - Scientific Computing Toolkit (documentation)
 libsc7 - Scientific Computing Toolkit (library)
 mpqc   - Massively Parallel Quantum Chemistry Program
 mpqc-openmpi - Massively Parallel Quantum Chemistry Program (OpenMPI 
transitiona
 mpqc-support - Massively Parallel Quantum Chemistry Program (support tools)
Closes: 725347
Changes: 
 mpqc (2.3.1-15) unstable; urgency=low
 .
   [ Michael Banck ]
   * debian/rules (override_dh_auto_test): Update OMPI_MCA environment variable
 to orte_rsh_agent as the original plm_rsh_agent variable is 

Bug#721763: [brltty] Idea to get id for free

[Samuel Thibault]

Bastien ROUCARIES, le Fri 25 Oct 2013 15:43:17 +0200, a écrit :
 On Fri, Oct 25, 2013 at 1:45 PM, Samuel Thibault sthiba...@debian.org wrote:
  Bastien ROUCARIES, le Fri 25 Oct 2013 08:55:48 +0200, a écrit :
  Fdti and the other one in this thread accept to be reflashed for pid/vid 
  only.
  So let reserve a few id on openmoko and ask your user to reflash.
 
  I don't think a user will dare to reflash his braille device. Those cost
  thousands of dollars and are typically the only way their owners would
  be able to use a computer.
 
 Changind vid/pid of usb adaptater is ultra low risk.

Does one need specific hardware for that?

Also, it means windows screen readers won't recognize the hardware any
more.

 You could always do it in reverse.

So windows screen readers could work again.  That however means having
to do the operation each time.

 And if manufacturer but the usb logo on their product it is violation
 of FTDI usb forum trademark so we could prod the manufactuer.

Users are mostly dependent on their manufacturer, not really the
converse :/

Actually, I don't think manufacturers care a lot about being allowed to
put the USB logo on their product, it is mostly unreadable for blind
people anyway.

Samuel


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

Bug#723910: FTBFS: test failures

[Michael Stapelberg]

Hi Damyan,

I think your bug was fixed with
http://code.stapelberg.de/git/kanla/commit/?id=1f98463aaf2b2ad2570dc17f057e37501c457123

I was finally able to reproduce it in a clean pbuilder instance. This
commit is contained in the 1.4 release, which I just uploaded.

Thanks.

-- 
Best regards,
Michael


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

Bug#723869: marked as done (src:freetable: FTBFS with perl 5.18: POD errors)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 16:19:09 +
with message-id e1vzk6p-00061j...@franck.debian.org
and subject line Bug#723869: fixed in freetable 2.3-4.1
has caused the Debian Bug report #723869,
regarding src:freetable: FTBFS with perl 5.18: POD errors
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.)


-- 
723869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:freetable
Version: 2.3-4
Severity: serious
Justification: FTBFS
User: debian-p...@lists.debian.org
Usertags: perl-5.18-transition

freetable fails to build in current clean sid chroot:

make[1]: Entering directory `/tmp/buildd/freetable-2.3'
ln -sf en.pod freetable.pod  pod2man --center='Freetable' freetable.pod en.1
rm -f freetable.pod
ln -sf fr.pod freetable.pod  pod2man --center='Freetable' freetable.pod fr.1
freetable.pod around line 3: Non-ASCII character seen before =encoding in 
'gE9nE9ration'. Assuming ISO8859-1
POD document had syntax errors at /usr/bin/pod2man line 71.
make[1]: *** [fr.1] Error 255

Feel free to contact debian-perl[1] if you need help fixing this.

[1] http://wiki.debian.org/Teams/DebianPerlGroup
---End Message---
---BeginMessage---
Source: freetable
Source-Version: 2.3-4.1

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

Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated freetable 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, 23 Oct 2013 17:34:08 +0200
Source: freetable
Binary: freetable
Architecture: source all
Version: 2.3-4.1
Distribution: unstable
Urgency: low
Maintainer: Felipe Augusto van de Wiel (faw) f...@debian.org
Changed-By: gregor herrmann gre...@debian.org
Description: 
 freetable  - Facilitates production of HTML tables
Closes: 723869
Changes: 
 freetable (2.3-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS with perl 5.18: POD errors:
 add =encoding directives to {fr,pl}.pod and convert them to utf8;
 call pod2man with --utf8 in Makefile.
 (Closes: #723869)
Checksums-Sha1: 
 95878acec2c1ab05712840881d04006a4f103b2c 1677 freetable_2.3-4.1.dsc
 6f9a3df4c16b937d3f46c3b7c759c9ac1f029e1f 11906 freetable_2.3-4.1.diff.gz
 c9aa115ec514084d234edd8b38a1623efae8344b 19604 freetable_2.3-4.1_all.deb
Checksums-Sha256: 
 f9eeb3fea0b146a8ed7a1931855417939e354c7c929d21ab15cedfa53d12c16a 1677 
freetable_2.3-4.1.dsc
 a27690be5fb44002d14bb7f83a73807c6801ad3f4fe5a73dc8f41733e7d686c2 11906 
freetable_2.3-4.1.diff.gz
 59f712c0eed7af731ca69da5f8db5fe8a05f59af7ef21b7de382ac9c59b336ed 19604 
freetable_2.3-4.1_all.deb
Files: 
 e47270d80cd44c5217727b7f800f2516 1677 web optional freetable_2.3-4.1.dsc
 484a3f73a663bcdcd093c5e808580e22 11906 web optional freetable_2.3-4.1.diff.gz
 178e3b208b175f2eb6fe16928f6db012 19604 web optional freetable_2.3-4.1_all.deb

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

iQIcBAEBCAAGBQJSZ+5IAAoJELs6aAGGSaoGvjwP/3SB1qAjvOlOS70dbbOCzHyv
KNaK2H3+swS/KS/yLrORsU6nY73CkSE2nidrigj01GIn3BPQ3IvWWzCQMyhUGA5I
PQAO31pWiIhpjlV7VOnvAlIA3mZkfDlTwTiYf9Za94GfUOCTf1rYqG22e9hV1oH3
5pkzYV+qCeyIZ0G7MZYpDoVHTLGJneuxtM9+GcLFA72GIO1lDJnTqnYH3HHjA3mv
R0FABd02qQEIrFE2VSG/jfkA7nUajYm0Zxx6QvD8uIDTL2Y1Zd7bPZ81s2OpnIHo
dirGpllDjdZDKy3mkE98eM1HsEYFUdtZ3hs9oxlYUXBronaH1DEkN1r87kizMr2e
G1V7VHzlczK+EFrT/Qmkds/EMOyg7IAejYrb8309BGrrT65Ty9euDnJDlHnzxZim
YEoOkCCmkicYsXtB1c9qPO/zz3YcBDVlccJ/dTWXRYSAfD6wy6dpBsJHgqRzwzBR
s45RnPeHAEZxJUHRu8nXYKjPSY5UqaaeZjz5CUgMvoxMvMpMC3nCbfpD3tMyPU46
PMkL+8uQUmbsc99EQVzjHkA9fVfJGPdQ5txbeC+a2DALNq/QAfDPWyG819s7gXb5
lQ+CT5mtMLwzMUZgposExM0yZqdSRx1edxH4463Zo1ZO26f07NZ4FAYubqNLz/AY
ZuObIJ7vg5dQ6ZyP/par
=qsiV
-END PGP SIGNATUREEnd Message---

Bug#721763: [brltty] Idea to get id for free

[Mario Lang]

Bastien ROUCARIES roucaries.bast...@gmail.com writes:

 On Fri, Oct 25, 2013 at 1:45 PM, Samuel Thibault sthiba...@debian.org wrote:
 Bastien ROUCARIES, le Fri 25 Oct 2013 08:55:48 +0200, a écrit :
 Fdti and the other one in this thread accept to be reflashed for pid/vid 
 only.
 So let reserve a few id on openmoko and ask your user to reflash.

 I don't think a user will dare to reflash his braille device. Those cost
 thousands of dollars and are typically the only way their owners would
 be able to use a computer.

 Changind vid/pid of usb adaptater is ultra low risk. You could always
 do it in reverse. And if manufacturer but the usb logo on their
 product it is violation of FTDI usb forum trademark so we could prod
 the manufactuer.

Reflashing will break compatibility with drivers on other platforms,
which is likely another reason why a user will not want to do this.

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Debian Developer URL:http://debian.org/
  .''`. | Get my public key via finger mlang/k...@db.debian.org
 : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
 `. `'
   `-  URL:http://delysid.org/  URL:http://www.staff.tugraz.at/mlang/


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

Bug#727609: marked as done (libbuffy-bindings: not buildable in unstable due to new version of libwibble-dev)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 16:20:31 +
with message-id e1vzk7j-0006oh...@franck.debian.org
and subject line Bug#727609: fixed in libbuffy-bindings 0.15
has caused the Debian Bug report #727609,
regarding libbuffy-bindings: not buildable in unstable due to new version of 
libwibble-dev
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.)


-- 
727609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libbuffy-bindings
Version: 0.14
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty

The new version of libwibble in unstable means that libbuffy-bindings
can no longer be built from source, because it Build-Depends:
libwibble-dev ( 0.2).

Thanks,

-- 
Colin Watson   [cjwat...@ubuntu.com]
---End Message---
---BeginMessage---
Source: libbuffy-bindings
Source-Version: 0.15

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

Debian distribution maintenance software
pp.
Enrico Zini enr...@debian.org (supplier of updated libbuffy-bindings package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Oct 2013 17:19:11 +0200
Source: libbuffy-bindings
Binary: libbuffy-perl python-buffy
Architecture: source amd64
Version: 0.15
Distribution: unstable
Urgency: low
Maintainer: Enrico Zini enr...@debian.org
Changed-By: Enrico Zini enr...@debian.org
Description: 
 libbuffy-perl - Perl wrapper for the libbuffy library
 python-buffy - Python wrapper for the libbuffy library
Closes: 727609
Changes: 
 libbuffy-bindings (0.15) unstable; urgency=low
 .
   * Cleaned up dependencies. Closes: #727609.
Checksums-Sha1: 
 cc5b1458110233d1a0071cf8ed06f6009e16ce72 1845 libbuffy-bindings_0.15.dsc
 640189867f204b1cf153cbfaad3bb9a0090b9e0f 20768 libbuffy-bindings_0.15.tar.gz
 dc52dd28f042c72830ed255c259ddb233e85bb56 96816 libbuffy-perl_0.15_amd64.deb
 7f9d5ebe108a60b90e9df584b30d509044ecd68e 122498 python-buffy_0.15_amd64.deb
Checksums-Sha256: 
 98a7a47d178c3a3663255e0265631814b245c131f9feebdeea08eff154b8aa69 1845 
libbuffy-bindings_0.15.dsc
 2029d9b0b9778417f87825cd7255468cdc721208ea8c1e7ca3c30ef5d04e68a5 20768 
libbuffy-bindings_0.15.tar.gz
 cea80a1f529327e7305cbcac1364a6b815eb50e838210ae248ab5f4f4e13f639 96816 
libbuffy-perl_0.15_amd64.deb
 76b91db608e1c139ca1a2514bddf4585c44fd98c58d69cfa62700f4b88b701a3 122498 
python-buffy_0.15_amd64.deb
Files: 
 df1d1adee7ef4c85e4e5fd5997a3220b 1845 misc optional libbuffy-bindings_0.15.dsc
 ad42566492e060aefbb4c0a8c32334b2 20768 misc optional 
libbuffy-bindings_0.15.tar.gz
 d52dc6b895d670876ec609140c57 96816 perl optional 
libbuffy-perl_0.15_amd64.deb
 e8fa16595f883843abc6d64b537ad0dc 122498 python optional 
python-buffy_0.15_amd64.deb

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

iQIcBAEBCAAGBQJSapgrAAoJEB5qw/OH8O2sG1IP/3BikcWaC7af45nGmCmbR5a4
53aLyHLdDODvM3WJfsj7oYgpioMLf+oGXeumPFoXTfiTupfiBGdTp5yQPqdOCSwu
pimkOLOvOYbnWaePulYczREVPOxsbx08VnJmrv+W7241fLU1lk8E3EFxDTDr3ZP8
Srk4DzWd8rQBCU7L9+U5NufKecgDfuCfOAkS/9zAy0ntcibh2RzDiqcdYPsA/rT9
/x+8N8f2cHXoRcw5TTAOlmd5RKlge1WQSbA18UumunVa8RaY7aiDWbQ5EbYcNhBS
t7Pot8uRVLjxHQWQ7mUtcE2sOCJCZTHTVQm3aXImyq0A6CEdCqp35N+XT4EdyJz0
4QzYT0DPKuWksjtOxpt5+3/crfx7JSVsza2oYXb5x1YCw8cOxHZySLOjAY7i+0vm
qKB5heMiI7hdUjTQ5fufOl6CZ9KYWEqQIPnK9WoI9uo59lwYttjfi6GPLedi9YY6
0j0VjJCXy8+6i+DgMCFlRumTKUAH5s8+c/k3NCRiIos6qOpWb+s8u7dndRLRVwX2
l7Lbilc5Wm4XA8onHydLBFEnp3tF/iZIDe2f4Q3YkwR9a0z23+ZEEtEVb2ygHADB
1MiBmmxEvbi46NOKMabX5ZNGToGy8m03locKrpfpdvP4HEJFFQXVD284SG+VgqWg
os7C8mWjsMD1MuKNLKSk
=rWqh
-END PGP SIGNATUREEnd Message---

Bug#723910: marked as done (FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 16:20:11 +
with message-id e1vzk7p-0006hd...@franck.debian.org
and subject line Bug#723910: fixed in kanla 1.4-1
has caused the Debian Bug report #723910,
regarding FTBFS: test failures
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.)


-- 
723910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:kanla
Version: 1.3-2
Severity: serious
Justification: FTBFS
User: debian-p...@lists.debian.org
Usertags: perl-5.18-transition

kanla fails to build in a clean sid pbuilder chroot:

Test Summary Report
---
t/004-smtp.t  (Wstat: 1024 Tests: 4 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
t/005-http.t  (Wstat: 1536 Tests: 6 Failed: 6)
  Failed tests:  1-6
  Non-zero exit status: 6
Files=5, Tests=27,  2 wallclock secs ( 0.06 usr  0.01 sys +  1.25 cusr  0.19 
csys =  1.51 CPU)
Result: FAIL
Failed 2/5 test programs. 10/27 subtests failed.
make[1]: *** [test_dynamic] Error 6

There are a couple of Smartmatch is experimental warnings so this may be 
related to perl 5.18 upgrade.


-- dam
---End Message---
---BeginMessage---
Source: kanla
Source-Version: 1.4-1

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

Debian distribution maintenance software
pp.
Michael Stapelberg stapelb...@debian.org (supplier of updated kanla 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: Fri, 25 Oct 2013 17:57:15 +0200
Source: kanla
Binary: kanla
Architecture: source all
Version: 1.4-1
Distribution: unstable
Urgency: low
Maintainer: Michael Stapelberg stapelb...@debian.org
Changed-By: Michael Stapelberg stapelb...@debian.org
Description: 
 kanla  - small-scale alerting daemon
Closes: 723910
Changes: 
 kanla (1.4-1) unstable; urgency=low
 .
   * New upstream release. (Closes: #723910)
Checksums-Sha1: 
 44931623429b41601f080f438c6b276d04917208 2050 kanla_1.4-1.dsc
 09da9c84a2897c6d4142be809129f2d5986e6d6a 68174 kanla_1.4.orig.tar.gz
 b983db0b1559e187ea5fd4ef6fe92f20f2c43586 4666 kanla_1.4-1.debian.tar.gz
 00cb66e7974684f2dc21dcf951a1802b5881bfc7 40354 kanla_1.4-1_all.deb
Checksums-Sha256: 
 0f5fc0ce85b119c6eaccd969b9fa051163e10c603e272e1ecc4c1506074037ce 2050 
kanla_1.4-1.dsc
 0d531facb3612bc805eac876a8fbfb50620378cbfae726d82df443261156232f 68174 
kanla_1.4.orig.tar.gz
 26560976bdd4b9da7cbbf6ddb9bff2856dfe57c5d879794653363cbdfc3a3b84 4666 
kanla_1.4-1.debian.tar.gz
 a42cfe4cd1965c39ac963ce641902bae3345f4e7084a36e8483f679e9ae35d8a 40354 
kanla_1.4-1_all.deb
Files: 
 60815c1824a33e16bae1070adde64e6c 2050 net optional kanla_1.4-1.dsc
 4cf5e4118d6f9b8fecbc5d761b30ec95 68174 net optional kanla_1.4.orig.tar.gz
 47006f7315e5e35cca5457fae5ff1a8c 4666 net optional kanla_1.4-1.debian.tar.gz
 f8994fef5180befd6655ad5732526c3f 40354 net optional kanla_1.4-1_all.deb

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

iQIcBAEBCgAGBQJSapUhAAoJEE5xYO1KyO4dCs0QAKw3jRbZuHQn5slbGcq0WAZ1
d38TuozwWlwSJsuZeruAKwLmvVemI3Mlfz2CdY9Rb4y/k3rGKSTFmY7/vMcwhiLh
t/oPSnb89CLUBJId0vKwnBIneptBZOOdHQ2YfMOFeh8OmlR2+f4/pe8oh5wVdlxq
wXwPq495QMgWeF3db4CuUmSJMS21W8gKhFwMG8Lb7uBh3dVFEHz4ok09i0h1o88c
8ISWdnowPqMz4NePRGc7soAuhPM9afxMOTFUfPls+6E+dpEQ+rusZz9A/5gllbRY
AjR6Cpsf4/QevdcOEGK+1664DtqN8bgpRWGDKqjmboWCDd8c1oHpiCDwV/FP9smF
ouN4LP0zZOws5UslgaL7iSKQYWDZ8P5zV5U4A5pS4HzTQ9W2zf4PcFF+rCHlpeHs
5JfFJ6Hk+QVl1TaE18iyqKiDrc0KkM19HInuJdrNJu2sqlpCSgUO7r3QVuzGm2P0
aY96SgOgANvk1kfjCk67Ng81R+0IazGp9wZ15yipVuI164YUVBNKpuBVzUXC+XXA
SHM4VVNbzWFo3ETrQNNydgY90lF2l8xalHRmPWXHmczYzwhy20u9gH7vTH067YCj
EX+LbrILE7VFptfd0qcucvLdezT6Mj2NJWb3YWNbAwfi7QQ+b42IHinMrrEycTw9
Yj/p7iITwaCH8d+1Nnmh
=FLPI
-END PGP SIGNATUREEnd Message---

Processed: Re: Bug#727665: lintian: FTBFS: Test failures

[Debian Bug Tracking System]

Processing control commands:

 tags -1 confirmed
Bug #727665 [src:lintian] lintian: FTBFS: Test failures
Added tag(s) confirmed.

-- 
727665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727665
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#665719: flint: FTBFS on mips/mipsel (impossible constraint in 'asm'

[Dejan Latinovic]

Hi,

gcc for mips/mipsel used in wheezy and jessie (sid) doesn't support
define_register_constraint h.


I have attached a patch solving the issue.

Cheers,
Dejan Latinovićdiff -uNr flint-1.011.orig/longlong.h flint-1.011/longlong.h
--- flint-1.011.orig/longlong.h	2008-06-16 03:31:56.0 +
+++ flint-1.011/longlong.h	2013-10-23 15:48:54.0 +
@@ -1011,27 +1011,17 @@
 #endif /* __m88000__ */
 
 #if defined (__mips)  W_TYPE_SIZE == 32
-#if __GNUC__  2 || __GNUC_MINOR__ = 7
-#define umul_ppmm(w1, w0, u, v) \
-  __asm__ (multu %2,%3 : =l (w0), =h (w1) : d (u), d (v))
-#else
 #define umul_ppmm(w1, w0, u, v) \
   __asm__ (multu %2,%3\n\tmflo %0\n\tmfhi %1\
 	   : =d (w0), =d (w1) : d (u), d (v))
-#endif
 #define UMUL_TIME 10
 #define UDIV_TIME 100
 #endif /* __mips */
 
 #if (defined (__mips)  __mips = 3)  W_TYPE_SIZE == 64
-#if __GNUC__  2 || __GNUC_MINOR__ = 7
-#define umul_ppmm(w1, w0, u, v) \
-  __asm__ (dmultu %2,%3 : =l (w0), =h (w1) : d (u), d (v))
-#else
 #define umul_ppmm(w1, w0, u, v) \
   __asm__ (dmultu %2,%3\n\tmflo %0\n\tmfhi %1\
 	   : =d (w0), =d (w1) : d (u), d (v))
-#endif
 #define UMUL_TIME 20
 #define UDIV_TIME 140
 #endif /* __mips */

Bug#727665: lintian: FTBFS: Test failures

[Niels Thykier]

Control: tags -1 confirmed

On 2013-10-25 08:11, Daniel Schepler wrote:
 Source: lintian
 Version: 2.5.19
 Severity: serious
 
From my pbuilder build log:
 
 [...]
 

Hi,

I can confirm this failure on (a slightly updated) git master branch;
downgrading tar to the version in testing makes the problems go away.
Odds are recent changes in tar to blame for this; question is now
whether it is a regression in tar or Lintian relying on non-interface bits.

~Niels


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

Processed: reassign 712410 to src:webkitgtk, reassign 710631 to src:webkitgtk, reassign 673469 to src:webkitgtk ...

[Debian Bug Tracking System]

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

 reassign 712410 src:webkitgtk
Bug #712410 [src:webkit] webkit: FTBFS on kfreebsd-amd64: collect2: error: ld 
terminated with signal 9 [Killed]
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.8.1-4.
Ignoring request to alter fixed versions of bug #712410 to the same values 
previously set
 reassign 710631 src:webkitgtk
Bug #710631 {Done: David Suárez david.sephi...@gmail.com} [src:webkit] 
webkit: FTBFS: ../Source/WebCore/xml/XPathParser.cpp:478:39: error: too many 
arguments to function 'int WebCore::XPath::xpathyyparse()'
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.8.1-3.4.
Ignoring request to alter fixed versions of bug #710631 to the same values 
previously set
 reassign 673469 src:webkitgtk
Bug #673469 [src:webkit] libwebkitgtk-1.0-0: segfaults all the time on armel, 
javascript related
Bug #651636 [src:webkit] GtkLauncher segfaults on mipsel, JavaScript-related
Bug #688640 [src:webkit] JavaScriptCore segmentation fault on PowerPC
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.8.1-3.3 and webkit/1.8.1-3.4.
No longer marked as found in versions webkit/1.8.1-3.3 and webkit/1.8.1-3.4.
No longer marked as found in versions webkit/1.8.1-3.3 and webkit/1.8.1-3.4.
Ignoring request to alter fixed versions of bug #673469 to the same values 
previously set
Ignoring request to alter fixed versions of bug #651636 to the same values 
previously set
Ignoring request to alter fixed versions of bug #688640 to the same values 
previously set
 reassign 677338 src:webkitgtk
Bug #677338 [src:webkit] webkit: libwekitgtk+.so contains rpath on hurd-i386, 
leading to link failures
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.8.1-3.1.
Ignoring request to alter fixed versions of bug #677338 to the same values 
previously set
 reassign 688640 src:webkitgtk
Bug #688640 [src:webkitgtk] JavaScriptCore segmentation fault on PowerPC
Bug #651636 [src:webkitgtk] GtkLauncher segfaults on mipsel, JavaScript-related
Bug #673469 [src:webkitgtk] libwebkitgtk-1.0-0: segfaults all the time on 
armel, javascript related
Ignoring request to reassign bug #688640 to the same package
Ignoring request to reassign bug #651636 to the same package
Ignoring request to reassign bug #673469 to the same package
 reassign 651636 src:webkitgtk
Bug #651636 [src:webkitgtk] GtkLauncher segfaults on mipsel, JavaScript-related
Bug #673469 [src:webkitgtk] libwebkitgtk-1.0-0: segfaults all the time on 
armel, javascript related
Bug #688640 [src:webkitgtk] JavaScriptCore segmentation fault on PowerPC
Ignoring request to reassign bug #651636 to the same package
Ignoring request to reassign bug #673469 to the same package
Ignoring request to reassign bug #688640 to the same package
 reassign 662547 src:webkitgtk
Bug #662547 [src:webkit] webkit: Please Build-Depends on libpng-dev, change 
from libpng12-dev
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/2.3-2.
Ignoring request to alter fixed versions of bug #662547 to the same values 
previously set
 reassign 696295 src:webkitgtk
Bug #696295 [src:webkit] webkit: Sets FD_CLOEXEC incorrectly with F_SETFL 
instead of F_SETFD
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.9.2-1.
Ignoring request to alter fixed versions of bug #696295 to the same values 
previously set
 reassign 700164 src:webkitgtk
Bug #700164 [src:webkit] src:webkit: first pile of 2013 CVEs
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
Ignoring request to alter found versions of bug #700164 to the same values 
previously set
Ignoring request to alter fixed versions of bug #700164 to the same values 
previously set
 reassign 696236 src:webkitgtk
Bug #696236 [src:webkit] webkit: please add patch to make it build on m68k
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.8.1-3.3.
Ignoring request to alter fixed versions of bug #696236 to the same values 
previously set
 reassign 700967 src:webkitgtk
Bug #700967 [src:webkit] webkit: diff for nmu 1.8.1-3.4
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
Ignoring request to alter found versions of bug #700967 to the same values 
previously set
Ignoring request to alter fixed versions of bug #700967 to the same values 
previously set
 reassign 700795 src:webkitgtk
Bug #700795 [src:webkit] webkit: FTBFS on x32: Tries and fails to build x86_64 
JIT compiler
Bug reassigned from package 'src:webkit' to 'src:webkitgtk'.
No longer marked as found in versions webkit/1.8.1-3.3.
Ignoring request to alter 

Bug#727719: ergo: FTBFS on mips/mipsel

[Jurica Stanojkovic]

Package: ergo
Version: 3.3.1-1
Severity: serious
Tags: sid
Justification: FTBFS

Package ergo failed to build from source on mips/mipsel because R3000 used
in integrals_hermite.cc is already defined.

Full build logs:
https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipsver=3.3.1-1stamp=1380475129
https://buildd.debian.org/status/fetch.php?pkg=ergoarch=mipselver=3.3.1-1stamp=1380477528

I have attached a patch resolving the issue.

Best regards,
Jurica

--- ergo-3.3.1.orig/source/integrals/integrals_hermite.cc
+++ ergo-3.3.1/source/integrals/integrals_hermite.cc
@@ -30,6 +30,9 @@
 #include cmath
 #include stdio.h
 
+#ifdef R3000
+ #undef R3000
+#endif
 
 int
 get_related_integrals_hermite(const IntegralInfo  integralInfo,

Processed: Patch for the build failure

[Debian Bug Tracking System]

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

 tags 713575 patch
Bug #713575 [src:libgcal] libgcal: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o):
 undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'
Added tag(s) patch.
 forwarded 713575 https://code.google.com/p/libgcal/issues/detail?id=94
Bug #713575 [src:libgcal] libgcal: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o):
 undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'
Set Bug forwarded-to-address to 
'https://code.google.com/p/libgcal/issues/detail?id=94'.
 kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
713575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713575
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#713575: Patch for the build failure

[Andreas Moog]

tags 713575 patch
forwarded 713575 https://code.google.com/p/libgcal/issues/detail?id=94
kthxbye

Hello David, Hello Michael,

attached is a patch to fix building on Debian. I've opened
https://code.google.com/p/libgcal/issues/detail?id=94 upstream and sent
my patch there as well.

Thanks for considering the patch.
-- 
Andreas Moog, Berliner Str. 29, 36205 Sontra/Germany
Ubuntu Developer
PGP-encrypted mails preferred (Key-ID: 74DE6624)
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624
Description: explicitly link the tests with pthread to fix FTBFS (Closes: #713575)
Author: Andreas Moog am...@ubuntu.com
Bug-Debian: http://bugs.debian.org/713575

--- libgcal-0.9.6.orig/utests/CMakeLists.txt
+++ libgcal-0.9.6/utests/CMakeLists.txt
@@ -21,7 +21,7 @@ set(GCAL_TEST_SOURCE_FILES
 )
 
 add_executable(testgcal ${GCAL_TEST_SOURCE_FILES})
-target_link_libraries(testgcal gcal ${CHECK_LIBRARIES})
+target_link_libraries(testgcal gcal ${CHECK_LIBRARIES} pthread)
 
 add_custom_target(
 	test


signature.asc
Description: OpenPGP digital signature

Bug#723867: dpkg-sig: diff for NMU version 0.13.1+nmu1

[gregor herrmann]

tags 723867 + patch
tags 723867 + pending
thanks

Dear maintainer,

I've prepared an NMU for dpkg-sig (versioned as 0.13.1+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   
diff -Nru dpkg-sig-0.13.1/debian/changelog dpkg-sig-0.13.1+nmu1/debian/changelog
--- dpkg-sig-0.13.1/debian/changelog	2006-11-20 16:10:47.0 +0100
+++ dpkg-sig-0.13.1+nmu1/debian/changelog	2013-10-25 20:07:39.0 +0200
@@ -1,3 +1,14 @@
+dpkg-sig (0.13.1+nmu1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS with perl 5.18: POD errors:
+fix POD by adding missing '=back'.
+(Closes: #723867)
+  * debian/control: replace Build-Depends-Indep with Build-Depends. Both
+debhelper and perl are needed during clean (lintian error).
+
+ -- gregor herrmann gre...@debian.org  Fri, 25 Oct 2013 20:07:08 +0200
+
 dpkg-sig (0.13.1) unstable; urgency=low
 
   * Non-Maintainer Upload by Gunnar Wolf
diff -Nru dpkg-sig-0.13.1/debian/control dpkg-sig-0.13.1+nmu1/debian/control
--- dpkg-sig-0.13.1/debian/control	2006-11-20 16:08:07.0 +0100
+++ dpkg-sig-0.13.1+nmu1/debian/control	2013-10-25 20:07:05.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Uploaders: Andreas Barth a...@not.so.argh.org
 Maintainer: Marc 'HE' Brockschmidt h...@debian.org
-Build-Depends-Indep: debhelper (= 4), perl
+Build-Depends: debhelper (= 4), perl
 Standards-Version: 3.6.2
 
 Package: dpkg-sig
diff -Nru dpkg-sig-0.13.1/dpkg-sig dpkg-sig-0.13.1+nmu1/dpkg-sig
--- dpkg-sig-0.13.1/dpkg-sig	2006-11-20 16:08:31.0 +0100
+++ dpkg-sig-0.13.1+nmu1/dpkg-sig	2013-10-25 20:04:33.0 +0200
@@ -1506,6 +1506,8 @@
 
 =item Signs I$changes_file and write the signed copy back.
 
+=back
+
 =cut
 
 sub sign_control_files {


signature.asc
Description: Digital signature

Processed: dpkg-sig: diff for NMU version 0.13.1+nmu1

[Debian Bug Tracking System]

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

 tags 723867 + patch
Bug #723867 [dpkg-sig] dpkg-sig: FTBFS with perl 5.18: POD errors
Added tag(s) patch.
 tags 723867 + pending
Bug #723867 [dpkg-sig] dpkg-sig: FTBFS with perl 5.18: POD errors
Added tag(s) pending.
 thanks
Stopping processing here.

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


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

Processed: Re: Bug#724054: exrtools: FTBFS: no dependency information found for /usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by debian/exrtools/usr/bin/pngtoexr)

[Debian Bug Tracking System]

Processing control commands:

 tag -1 + unreproducible
Bug #724054 [src:exrtools] exrtools: FTBFS: no dependency information found for 
/usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by 
debian/exrtools/usr/bin/pngtoexr)
Added tag(s) unreproducible.

-- 
724054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724054
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#724054: exrtools: FTBFS: no dependency information found for /usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by debian/exrtools/usr/bin/pngtoexr)

[gregor herrmann]

Control: tag -1 + unreproducible

On Sun, 22 Sep 2013 08:06:01 -0700, Daniel Schepler wrote:

 dh_shlibdeps
 dh_shlibdeps: Compatibility levels before 5 are deprecated (level 4 in use)
 dpkg-shlibdeps: error: no dependency information found for 
 /usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by 
 debian/exrtools/usr/bin/pngtoexr)
 dh_shlibdeps: dpkg-shlibdeps -Tdebian/exrtools.substvars 
 debian/exrtools/usr/bin/exricamtm debian/exrtools/usr/bin/ppmtoexr 
 debian/exrtools/usr/bin/exrblur debian/exrtools/usr/bin/exrpptm 
 debian/exrtools/usr/bin/jpegtoexr debian/exrtools/usr/bin/exrstats 
 debian/exrtools/usr/bin/exrnlm debian/exrtools/usr/bin/exrnormalize 
 debian/exrtools/usr/bin/pngtoexr debian/exrtools/usr/bin/exrtopng 
 debian/exrtools/usr/bin/exrchr returned exit code 2

Builds fine here, probably due to recent changes in the libpng
package?

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: Bob Dylan: My Wife's Home Town


signature.asc
Description: Digital signature

Processed: gpaint: diff for NMU version 0.3.3-6.1

[Debian Bug Tracking System]

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

 tags 705875 + pending
Bug #705875 [gpaint] FTBFS with gcc-4.8 in experimental and eglibc-2.17
Added tag(s) pending.
 tags 724915 + patch
Bug #724915 [src:gpaint] gpaint: FTBFS: image_processing.o: undefined reference 
to symbol 'log@@GLIBC_2.2.5'
Added tag(s) patch.
 tags 724915 + pending
Bug #724915 [src:gpaint] gpaint: FTBFS: image_processing.o: undefined reference 
to symbol 'log@@GLIBC_2.2.5'
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
705875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705875
724915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724915
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#724915: gpaint: diff for NMU version 0.3.3-6.1

[gregor herrmann]

tags 705875 + pending
tags 724915 + patch
tags 724915 + pending
thanks

Dear maintainer,

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

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: U2: New York
diff -Nru gpaint-0.3.3/debian/changelog gpaint-0.3.3/debian/changelog
--- gpaint-0.3.3/debian/changelog	2009-12-30 02:04:24.0 +0100
+++ gpaint-0.3.3/debian/changelog	2013-10-25 20:27:16.0 +0200
@@ -1,3 +1,18 @@
+gpaint (0.3.3-6.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gcc-4.8 in experimental and eglibc-2.17:
+add patch 27_fix_missing_hdrs_libs.diff from Ubuntu / Daniel T Chen:
+* Fixed FTBFS:
+  - added missing preprocessor directives and math lib to link;
+  - added forward declarations, fixing implicit declaration warnings
+that would have caused FTBFS on amd64 buildds.
+(Closes: #705875)
+  * This patch also fixes FTBFS: image_processing.o: undefined reference to
+symbol 'log@@GLIBC_2.2.5' (Closes: #724915)
+
+ -- gregor herrmann gre...@debian.org  Fri, 25 Oct 2013 20:26:51 +0200
+
 gpaint (0.3.3-6) unstable; urgency=low
 
   * debian/patches/26_fix_toolbar.diff: don't set the style for the toolbar,
diff -Nru gpaint-0.3.3/debian/patches/27_fix_missing_hdrs_libs.diff gpaint-0.3.3/debian/patches/27_fix_missing_hdrs_libs.diff
--- gpaint-0.3.3/debian/patches/27_fix_missing_hdrs_libs.diff	1970-01-01 01:00:00.0 +0100
+++ gpaint-0.3.3/debian/patches/27_fix_missing_hdrs_libs.diff	2013-10-25 20:25:31.0 +0200
@@ -0,0 +1,71 @@
+Index: gpaint-0.3.3/src/image.c
+===
+--- gpaint-0.3.3.orig/src/image.c	2013-04-21 10:13:06.029569664 -0400
 gpaint-0.3.3/src/image.c	2013-04-21 10:13:23.209284134 -0400
+@@ -28,6 +28,8 @@
+ #include image.h
+ #include debug.h
+ #include math.h
++#include string.h
++#include libintl.h
+ #include gdk/gdk.h
+ #include gdk/gdkx.h  /* for gdk_root_parent */
+ #include gdk-pixbuf/gdk-pixbuf.h
+Index: gpaint-0.3.3/src/text.c
+===
+--- gpaint-0.3.3.orig/src/text.c	2013-04-21 10:13:06.009569962 -0400
 gpaint-0.3.3/src/text.c	2013-04-21 10:13:23.209284134 -0400
+@@ -26,6 +26,8 @@
+ #  include config.h
+ #endif
+ 
++#include ctype.h
++#include stdlib.h
+ #include string.h
+ 
+ #ifdef HAVE_STRING_H
+@@ -76,6 +78,7 @@
+ static void text_draw_string(gpaint_text *text);
+ static gint text_handle_timeout(gpaint_text *text);
+ static void text_draw_current_string(gpaint_tool *tool);
++extern void convert_color(const GdkColor *color, unsigned char *r, unsigned char *g, unsigned char *b);
+ 
+ gpaint_tool *text_create(const char *name)
+ {
+Index: gpaint-0.3.3/src/main.c
+===
+--- gpaint-0.3.3.orig/src/main.c	2013-04-21 10:13:06.017569892 -0400
 gpaint-0.3.3/src/main.c	2013-04-21 10:13:23.209284134 -0400
+@@ -36,6 +36,7 @@
+ 
+ static GList *window_list = 0;
+ static void create_window(void);
++extern void text_set_fontpicker(gpaint_tool *tool, GtkFontButton *fontpicker);
+ 
+ 
+ 
+Index: gpaint-0.3.3/src/Makefile.am
+===
+--- gpaint-0.3.3.orig/src/Makefile.am	2013-04-21 10:15:52.766801609 -0400
 gpaint-0.3.3/src/Makefile.am	2013-04-21 10:16:09.014530578 -0400
+@@ -67,6 +67,6 @@
+ 
+ 
+ gpaint_2_CFLAGS = -I$(srcdir)
+-gpaint_2_LDADD = $(GUI_LIBS) $(PRINT_LIBS)
++gpaint_2_LDADD = $(GUI_LIBS) $(PRINT_LIBS) -lm
+ gpaint_2_LDFLAGS = -Wl,--export-dynamic
+ 
+Index: gpaint-0.3.3/src/Makefile.in
+===
+--- gpaint-0.3.3.orig/src/Makefile.in	2013-04-21 10:15:59.014697621 -0400
 gpaint-0.3.3/src/Makefile.in	2013-04-21 10:16:16.050413141 -0400
+@@ -168,7 +168,7 @@
+ 
+ 
+ gpaint_2_CFLAGS = -I$(srcdir)
+-gpaint_2_LDADD = $(GUI_LIBS) $(PRINT_LIBS)
++gpaint_2_LDADD = $(GUI_LIBS) $(PRINT_LIBS) -lm
+ gpaint_2_LDFLAGS = -Wl,--export-dynamic
+ mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+ CONFIG_CLEAN_FILES = 
diff -Nru gpaint-0.3.3/debian/patches/series gpaint-0.3.3/debian/patches/series
--- gpaint-0.3.3/debian/patches/series	2009-12-30 01:06:14.0 +0100
+++ gpaint-0.3.3/debian/patches/series	2013-10-25 20:25:31.0 +0200
@@ -10,3 +10,4 @@
 24_fix_crash_on_failed_write.diff
 25_fix_color_selection.diff
 26_fix_toolbar.diff
+27_fix_missing_hdrs_libs.diff


signature.asc
Description: Digital signature

Processed: merging 725511 725549

[Debian Bug Tracking System]

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

 merge 725511 725549
Bug #725511 [src:yorick-gl] yorick-gl: FTBFS: No rule to make target `check.i', 
needed by `check-dll'
Bug #725549 [src:yorick-gl] yorick-gl: FTBFS: make[1]: *** No rule to make 
target `check.i', needed by `check-dll'
Merged 725511 725549
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
725511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725511
725549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725549
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#713240: ebview: FTBFS: configure: error: Package requirements (pangox) were not met:

[gregor herrmann]

On Sun, 13 Oct 2013 01:00:26 +0800, YunQiang Su wrote:

 This patch can fix this problem.

#701840 has another patch that is related to pangox. 

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: Bob Dylan: I Was Young When I Left Home


signature.asc
Description: Digital signature

Bug#726371: I have this bug too

[CrabMan]

Synaptiks used to work for me before this moment. What happened is: I 
switched my laptop to sleep mode for the first time in a very long time. 
Before I did it synaptiks had been working fine. When my laptop slept 
and woke up, I opened the screen and found kde crash report helper 
saying that synaptiks crashed. It said my backtrace wasn't useful, so I 
installed:


apt-get install python2.7-dbg
sudo apt-get install python-dbg
sudo apt-get install python-kde4-dbg

After that every time I launch synaptiks, it crashes with segmentation 
fault, also whenever I enter touchpad settings in kde system settings, 
it crashes too.



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

Bug#727628: [Pkg-xfce-devel] Bug#727628: This bug affects me too in Wheezy and is really nasty

[Yves-Alexis Perez]

On Fri, 2013-10-25 at 17:33 +0200, Ingo wrote:
 I do hope we get the fix backported to Wheezy soon.
 
 /Ingo
 
I uploaded to wheezy-proposed-updates yesterday, it's now in the queue
(see http://release.debian.org/proposed-updates/stable.html).
Unfortunately, the last point release is really recent so the next one
will not be around soon.

Regards,
-- 
Yves-Alexis


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

Bug#726725: feed2imap: uninstallable in sid

[Dominik George]

Package: feed2imap
Version: 1.0-2
Followup-For: Bug #726725

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

How exactly does fixing this in experimental fix it in the sid version?
The status of the bug is inadequate.

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

Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh

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

iQJOBAEBCAA4BQJSasCWMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pZDBBAAgwKm5vMpY7BeoXTAwDfW
roH7qWlYB1uAa0A1ZpprYM1Qj8smgYFFBAo1crMHwbOtUeLha35N4t4FFjnD6hin
JuyghtzBrINbUdCFH5oQ8oJZA8bWxhRxiAsdh1jHL/PM8lRVUXC86sByI0X5EPEh
fKwEOcphzlr5a4lL5+LjHr1K5R0iy2ux0/lZEL07SBNrP2PwF2t03YMpi9vqqlxy
GDi3XWtukps0d2hVAJja/t/xrIAixfZ4z5MjQpVz/CMtYbqAXm431Qd+Lexm+G40
PRn2hJV5Cj3dL31ahZ5ujOv+bWTrKqAUTpW3fANRZ7DwN+KPm2BbXfyp8Z7nW7xV
y32ak/ujwk6VpGeJZqEGNeFBuq2d9fFyrish4gSf7st/PnFB5SzeUid2LapHINFy
/Rv8Wvr/ivHd7kbj+Su+VSqrfkGSZnJ5vjhS2jFFryozrHwg7rR5UPBk2CfMoxqI
133dYjfLy3DrJfuhe5GqomTQBv0yCPL+fq3gvS+SNIZcnNIC9PG0cSXeXawbnpVa
Xl6NrnozDuRJciosAuPLNZxYGPwVvFFuyB3su26tCCfdceniKSzjceXOd1KfjaXF
Fck7uX17lRyRBAn4IzyR6TazsDnvFDI1/Uv2WQle+4OWAnMYEAWvbYEnylzLX6e1
NI0+N7qWq5uiChd3VxotbQg=
=3VGI
-END PGP SIGNATURE-


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

Bug#727657: unconditional build dependency on g++-multilib

[Dejan Latinovic]

Hi,

  uc-echo has an unconditional build dependency on g++-multilib, which
is not
  available on all architectures.
 do you know a better choice?


maybe the better way would be to list all architectures that support
g++-multilib.
For sid those architectures are:  amd64, i386, kfreebsd-amd64, mips,
mipsel, powerpc, ppc64, s390x, sparc, sparc64, x32
For example, g++-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc
ppc64 s390x sparc sparc64 x32]


  also, it fails to build on mips* which does have g++-multilib, so it
seems that
  this package has hardcoded ix86 assumptions.

 The problem on mips* is not g++-multilib but the parameter -m64 for gcc.
 Somewhere I read that -mabi=64 is default on mips, but 'gcc -dumpspecs'
 tells me:
  *multilib_defaults:
  EB mips1 mabi=32
 I guess I am totally confused now :-(. Can you please point me in the
 right direction?

Mips doesn't support neither -m64 nor -m32 options.
For MIPS64 you should use -mips64 -mabi=64.
For MIPS32 you should use defaults options.


Cheers,
Dejan Latinović


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

Processed: your mail

[Debian Bug Tracking System]

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

 Found 726009 1.00.0-4
Bug #726009 {Done: Anton Gladky gl...@debian.org} [src:yade] Yade requires 
too much RAM for building
Marked as found in versions yade/1.00.0-4; no longer marked as fixed in 
versions yade/1.00.0-4 and reopened.
 Thanks
Stopping processing here.

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

[Anton Gladky]

Found 726009 1.00.0-4
Thanks


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

Bug#727728: flup: debian/copyright does not contain the license

[Luke Faraone]

Package: flup
Version: 1.0.2-2
Severity: serious
Justification: Policy 12.5

The package is under the BSD-2-Clause license, but the license text is
not reproduced in debian/copyright.

While you're fixing this, please also switch to the approved shortname
for the license (indicated above).

Cheers,

Luke Faraone

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.0-41-generic (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


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

Bug#727665: lintian: FTBFS: Test failures

[Niels Thykier]

On 2013-10-25 19:09, Niels Thykier wrote:
 Control: tags -1 confirmed
 
 On 2013-10-25 08:11, Daniel Schepler wrote:
 Source: lintian
 Version: 2.5.19
 Severity: serious

 From my pbuilder build log:

 [...]

 
 Hi,
 
 I can confirm this failure on (a slightly updated) git master branch;
 downgrading tar to the version in testing makes the problems go away.
 Odds are recent changes in tar to blame for this; question is now
 whether it is a regression in tar or Lintian relying on non-interface bits.
 
 ~Niels
 
 

Okay, first two of 3 problems solved (thanks to Jakub Wilk).  See
attached patch for a sample work around / solution.

Ref: http://sources.debian.net/src/tar/1.27-1/ChangeLog?hl=265#L261

~Niels


From dad5e05115ec05822d300a7e05bd07bebea11dd3 Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Fri, 25 Oct 2013 21:58:08 +0200
Subject: [PATCH] t: Use -d@-1 to create ancient files in tarballs

Signed-off-by: Niels Thykier 
---
 t/debs/deb-format-ancient-file/Makefile | 2 +-
 t/debs/deb-format-ancient-file/tags | 2 +-
 t/source/cruft-ancient-file/Makefile| 2 +-
 t/source/cruft-ancient-file/tags| 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/t/debs/deb-format-ancient-file/Makefile b/t/debs/deb-format-ancient-file/Makefile
index a2ea7fc..d6cdf10 100644
--- a/t/debs/deb-format-ancient-file/Makefile
+++ b/t/debs/deb-format-ancient-file/Makefile
@@ -9,7 +9,7 @@ all:
 
 	chown 0:0 control
 	chmod 644 control
-	env TZ=GMT touch -t 19700101 control
+	env TZ=GMT touch -d@-1 control
 
 	# Use --no-fix-perm to avoid it messing with the
 	# our created "mod-times"
diff --git a/t/debs/deb-format-ancient-file/tags b/t/debs/deb-format-ancient-file/tags
index 83de2df..c00701c 100644
--- a/t/debs/deb-format-ancient-file/tags
+++ b/t/debs/deb-format-ancient-file/tags
@@ -1,2 +1,2 @@
 E: deb-format-ancient-file: package-contains-ancient-file usr/share/doc/deb-format-ancient-file/changelog.gz 1970-01-01
-E: deb-format-ancient-file: tar-errors-from-control control: implausibly old time stamp 1970-01-01 00:00:00
+E: deb-format-ancient-file: tar-errors-from-control control: implausibly old time stamp 1969-12-31 23:59:59
diff --git a/t/source/cruft-ancient-file/Makefile b/t/source/cruft-ancient-file/Makefile
index f11f631..284c123 100644
--- a/t/source/cruft-ancient-file/Makefile
+++ b/t/source/cruft-ancient-file/Makefile
@@ -4,7 +4,7 @@ dir  = $(name)-1.0
 all:
 	mkdir $(dir)
 	echo 'Some upstream README' > $(dir)/README
-	env TZ=GMT touch -t 19700101 $(dir)/README
+	env TZ=GMT touch -d@-1 $(dir)/README
 	tar -c -f $(name)_1.0.orig.tar.gz -z $(dir)
 	mkdir $(dir)/debian
 	cp changelog copyright control rules $(dir)/debian/
diff --git a/t/source/cruft-ancient-file/tags b/t/source/cruft-ancient-file/tags
index e5945ba..18765f6 100644
--- a/t/source/cruft-ancient-file/tags
+++ b/t/source/cruft-ancient-file/tags
@@ -1 +1 @@
-I: cruft-ancient-file source: tar-errors-from-source cruft-ancient-file-1.0/README: implausibly old time stamp 1970-01-01 00:00:00
+I: cruft-ancient-file source: tar-errors-from-source cruft-ancient-file-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
-- 
1.8.4.rc3

Bug#713475: [Pkg-ayatana-devel] Bug#713475: libindicator: diff for NMU version 0.5.0-1.1

[Andrew Starr-Bochicchio]

On Sat, Oct 12, 2013 at 4:53 AM, Andrea Colangelo war...@ubuntu.com wrote:
 tags 713475 + patch
 tags 713475 + pending
 thanks

 Dear maintainer(s),

 I've prepared an NMU for libindicator (versioned as 0.5.0-1.1). Please, find 
 the
 attached debdiff, ready for sponsorship.

Hi Andrea,

Thanks for the patch. I'm about to sponsor it. In the future note that
you shouldn't tag a bug as pending if you are looking for a sponsor.
Pending means that a solution to this bug has been found and an
upload will be made soon. [0] Basically it assumes that the
maintainer has committed the patch to vcs and is planning to upload
it. So the PTS doesn't list the patch in the TODO section, the BTS
moves bugs tagged pending to the bottom of the list as they are no
longer interesting to the maintainer, etc...

[0] http://www.debian.org/Bugs/Developer#tags

Thanks!

-- Andrew Starr-Bochicchio

   Ubuntu Developer https://launchpad.net/~andrewsomething
   Debian Developer http://qa.debian.org/developer.php?login=asb
   PGP/GPG Key ID: D53FDCB1


-- 
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#725599: squid3: FTBFS: cp: cannot stat '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

 tag -1 + confirmed patch
Bug #725599 [src:squid3] squid3: FTBFS: cp: cannot stat 
'/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or 
directory
Added tag(s) confirmed and patch.

-- 
725599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725599
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#725599: squid3: FTBFS: cp: cannot stat '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or directory

[gregor herrmann]

Control: tag -1 + confirmed patch

On Sun, 06 Oct 2013 21:52:15 +0200, David Suárez wrote:

  dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp 
  cp: cannot stat 
  '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such 
  file or directory

The manpage is not there to be installed because it doesn't get
built.

From the ./configure run:

pod2man: unable to format
configure: Basic auth helper DB ... found but cannot be built

Reading configure shows that it tests with
helpers/basic_auth/DB/config.test:

## Test: do we have perl to build the helper scripts?
## Test: do we have pod2man to build the manual?
perl --version /dev/null  echo | pod2man /dev/null

and this fails (probably due to changes in Perl 5.18) with the error
quoted above.

Same for
helpers/log_daemon/DB/config.test
and
helpers/external_acl/SQL_session/config.test
.


I suggest to replace the weird test in the three config.test files
with something like

command -v perl /dev/null  command -v pod2man /dev/null


Comments?


Cheers,
gregor, attaching a debdiff

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: Dire Straits: Six Blade Knife
diff -Nru squid3-3.3.8/debian/changelog squid3-3.3.8/debian/changelog
--- squid3-3.3.8/debian/changelog   2013-07-22 00:08:07.0 +0200
+++ squid3-3.3.8/debian/changelog   2013-10-25 23:10:06.0 +0200
@@ -1,3 +1,15 @@
+squid3 (3.3.8-1.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS: cp: cannot stat
+'/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No
+such file or directory:
+new patch 17-pod2man-check.patch:
+fix config.test files' check for perl and pod2man
+(Closes: #725599)
+
+ -- gregor herrmann gre...@debian.org  Fri, 25 Oct 2013 21:22:24 +0200
+
 squid3 (3.3.8-1) unstable; urgency=high
 
   * Urgency high due to security fixes
diff -Nru squid3-3.3.8/debian/patches/17-pod2man-check.patch 
squid3-3.3.8/debian/patches/17-pod2man-check.patch
--- squid3-3.3.8/debian/patches/17-pod2man-check.patch  1970-01-01 
01:00:00.0 +0100
+++ squid3-3.3.8/debian/patches/17-pod2man-check.patch  2013-10-25 
23:18:18.0 +0200
@@ -0,0 +1,40 @@
+Description: fix check for perl and pod2man
+ At least under Perl 5.18, the current version fails with
+ | pod2man: unable to format
+ | configure: FOO ... found but cannot be built
+Origin: vendor
+Bug-Debian: http://bugs.debian.org/725599
+Forwarded: no
+Author: gregor herrmann gre...@debian.org
+Last-Update: 2013-10-25
+
+--- a/helpers/basic_auth/DB/config.test
 b/helpers/basic_auth/DB/config.test
+@@ -2,6 +2,6 @@
+ 
+ ## Test: do we have perl to build the helper scripts?
+ ## Test: do we have pod2man to build the manual?
+-perl --version /dev/null  echo | pod2man /dev/null
++command -v perl /dev/null  command -v pod2man /dev/null
+ 
+ exit $?
+--- a/helpers/external_acl/SQL_session/config.test
 b/helpers/external_acl/SQL_session/config.test
+@@ -2,6 +2,6 @@
+ 
+ ## Test: do we have perl to build the helper scripts?
+ ## Test: do we have pod2man to build the manual?
+-perl --version /dev/null  echo | pod2man /dev/null
++command -v perl /dev/null  command -v pod2man /dev/null
+ 
+ exit $?
+--- a/helpers/log_daemon/DB/config.test
 b/helpers/log_daemon/DB/config.test
+@@ -2,6 +2,6 @@
+ 
+ ## Test: do we have perl to build the helper scripts?
+ ## Test: do we have pod2man to build the manual?
+-perl --version /dev/null  echo | pod2man /dev/null
++command -v perl /dev/null  command -v pod2man /dev/null
+ 
+ exit $?
diff -Nru squid3-3.3.8/debian/patches/series squid3-3.3.8/debian/patches/series
--- squid3-3.3.8/debian/patches/series  2013-07-22 00:07:44.0 +0200
+++ squid3-3.3.8/debian/patches/series  2013-10-25 23:07:04.0 +0200
@@ -2,3 +2,4 @@
 02-makefile-defaults.patch
 15-cachemgr-default-config.patch
 16-ipc-statedir.patch
+17-pod2man-check.patch


signature.asc
Description: Digital signature

Bug#713475: marked as done (libindicator: FTBFS: indicator-image-helper.c:72:3: error: 'gtk_icon_info_free' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkicontheme.h:198): Use 'g_object_unref

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 21:34:43 +
with message-id e1vzp1n-0003du...@franck.debian.org
and subject line Bug#713475: fixed in libindicator 0.5.0-1.1
has caused the Debian Bug report #713475,
regarding libindicator: FTBFS: indicator-image-helper.c:72:3: error: 
'gtk_icon_info_free' is deprecated (declared at 
/usr/include/gtk-3.0/gtk/gtkicontheme.h:198): Use 'g_object_unref' instead 
[-Werror=deprecated-declarations]
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.)


-- 
713475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libindicator
Version: 0.5.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
 /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
 -I/«PKGBUILDDIR»/./libindicator -I..   -D_FORTIFY_SOURCE=2 -pthread 
 -I/usr/include/gtk-3.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
 -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 
 -I/usr/include/libdrm-DG_LOG_DOMAIN=\libindicator\ -Wall -Werror -g -O2 
 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
 -Wall -c -o libindicator3_la-indicator-image-helper.lo `test -f 
 'indicator-image-helper.c' || echo 
 '/«PKGBUILDDIR»/./libindicator/'`indicator-image-helper.c
 libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./libindicator 
 -I.. -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-3.0 
 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
 -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 
 -I/usr/include/libdrm -DG_LOG_DOMAIN=\libindicator\ -Wall -Werror -g -O2 
 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
 -Wall -c /«PKGBUILDDIR»/./libindicator/indicator-image-helper.c  -fPIC -DPIC 
 -o .libs/libindicator3_la-indicator-image-helper.o
 /«PKGBUILDDIR»/./libindicator/indicator-image-helper.c: In function 
 'refresh_image':
 /«PKGBUILDDIR»/./libindicator/indicator-image-helper.c:72:3: error: 
 'gtk_icon_info_free' is deprecated (declared at 
 /usr/include/gtk-3.0/gtk/gtkicontheme.h:198): Use 'g_object_unref' instead 
 [-Werror=deprecated-declarations]
gtk_icon_info_free(icon_info);
^
 cc1: all warnings being treated as errors
 make[4]: *** [libindicator3_la-indicator-image-helper.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/libindicator_0.5.0-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio a...@debian.org (supplier of updated libindicator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Oct 2013 16:56:27 -0400
Source: libindicator
Binary: libindicator7 libindicator-dev libindicator-tools libindicator3-7 
libindicator3-dev libindicator3-tools
Architecture: source amd64
Version: 0.5.0-1.1
Distribution: unstable
Urgency: low
Maintainer: The Ayatana 

Bug#727172:

[Thiago Bellini Ribeiro]

Never mind about the issue. After trying to install the broken
dependencies, I found that the problem is that libopus0 is missing
multi-arch support, an that issue is being *exhaustedly* discussed
here [1].

So, fell free to mark this as invalid :)

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674467

-- 
Thiago Bellini Ribeiro
http://hackedbellini.org

“Real knowledge is to know the extent of one's ignorance.” - Confucius


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

Bug#712410: marked as done (webkit: FTBFS on kfreebsd-amd64: collect2: error: ld terminated with signal 9 [Killed])

[Debian Bug Tracking System]

Your message dated Sat, 26 Oct 2013 02:27:26 +0200
with message-id 526b0c6e.3010...@debian.org
and subject line Re: Bug#712410: webkit: FTBFS on kfreebsd-amd64: collect2: 
error: ld terminated with signal 9 [Killed]
has caused the Debian Bug report #712410,
regarding webkit: FTBFS on kfreebsd-amd64: collect2: error: ld terminated with 
signal 9 [Killed]
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.)


-- 
712410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: webkit
Version: 1.8.1-4
Severity: serious
Tags: help

Hi,

webkit 1.8.1-4 FTBFS on kfreebsd-amd64. From the buildd logs[1][2]:

libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../x86_64-kfreebsd-gnu/crti.o 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/crtbeginS.o  [*very long list of objects*] 
-Wl,--whole-archive ./.libs/libWebCore.a ./.libs/libWebCoreGtk.a 
-Wl,--no-whole-archive  -Wl,-rpath -Wl,/«PKGBUILDDIR»/build-2.0/.libs -lpthread 
./.libs/libjavascriptcoregtk-1.0.so /usr/lib/x86_64-kfreebsd-gnu/libenchant.so 
-lgailutil -lgeoclue -ldbus-glib-1 -ldbus-1 -lgstapp-0.10 -lgstaudio-0.10 
-lgstfft-0.10 -lgstinterfaces-0.10 -lgstpbutils-0.10 -lgstvideo-0.10 
/usr/lib/x86_64-kfreebsd-gnu/libgstbase-0.10.so 
/usr/lib/x86_64-kfreebsd-gnu/libgstreamer-0.10.so -lgmodule-2.0 -lgthread-2.0 
-lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 
/usr/lib/x86_64-kfreebsd-gnu/libcairo.so -ljpeg -lsoup-2.4 -lgio-2.0 -lxslt 
-lxml2 -lGL -ldl -lpangoft2-1.0 -lpango-1.0 
/usr/lib/x86_64-kfreebsd-gnu/libfreetype.so -lfontconfig -lgobject-2.0 
-lglib-2.0 -lpng12 /usr/
 lib/x86_64-kfreebsd-gnu/libsqlite3.so -licui18n -licuuc -licudata -lXrender 
-lXt -lX11 -lz -L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7 
-L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../x86_64-kfreebsd-gnu 
-L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../../lib 
-L/lib/x86_64-kfreebsd-gnu -L/lib/../lib -L/usr/lib/x86_64-kfreebsd-gnu 
-L/usr/lib/../lib -L/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../.. -lstdc++ -lm 
-lc -lgcc_s /usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/crtendS.o 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../x86_64-kfreebsd-gnu/crtn.o  -O2 
-Wl,--as-needed -O2 -Wl,--version-script -Wl,../Source/autotools/symbols.filter 
-Wl,-z -Wl,relro -Wl,--export-dynamic -pthread -pthread   -pthread -Wl,-soname 
-Wl,libwebkitgtk-1.0.so.0 -o .libs/libwebkitgtk-1.0.so.0.13.2
collect2: error: ld terminated with signal 9 [Killed]

At first I thought it would be running out of memory. Note that we build
with -Wl,--no-keep-memory on 32 bit arches and so not here. But given that
a retry failed similarly I started a build on falla.d.o which failed
similarly. I then built with -Wl,--no-keep-memory only and with
-Wl,--no-keep-memory -Wl,--reduce-memory-overheads afterwards and it failed
both times. The failure is similar to the above.

It doesn't seem to be a too long command line (we have had that previously)
because the linker takes about 25 minutes to fail on falla.

CC'ing -bsd. I'd appreciate if you could take a look.

Thank you,
Emilio

[1] 
https://buildd.debian.org/status/fetch.php?pkg=webkitarch=kfreebsd-amd64ver=1.8.1-4stamp=1371160901
[2] 
https://buildd.debian.org/status/fetch.php?pkg=webkitarch=kfreebsd-amd64ver=1.8.1-4stamp=1371129678

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (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
---End Message---
---BeginMessage---
Version: 2.0.2-1

On 25/06/13 23:18, Emilio Pozuelo Monfort wrote:
 On 25/06/13 22:41, Christoph Egger wrote:
 Aurelien Jarno aurel...@aurel32.net writes:
 That's something I can try if the above fails, but I first need to
 setup a machine with enough swap, mine currently don't have so much?

 FWIW it's currently building on my notebook (8GB physical + 8GB SWAP)
 and should be ready soon
 
 Thanks to both of you.
 
 For the future to avoid this situation, I have added -gstabs on kfreebsd-*.
 
 I can also add -Wl,--reduce-memory-overheads -Wl,--no-keep-memory,
 -Wl,--hash-size=31, or if that's not enough, I can disable debugging symbols 
 (as
 we do on a few other arches).
 
 Regards,
 Emilio
 

webkit is building fine now on kbsd, so let's close this.

Emilio---End Message---

Bug#727740: installation-reports: wireless and wired network works in the installer but not transfered to the installed system

[Nick Gawronski]

Package: installation-reports
Severity: critical
Tags: d-i
Justification: breaks the whole system



-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/debian-cd/7.2.0/and64/iso-cd/debian-7.2.0-amd64-netinst.iso
 2013-10-12 16:06
Date: Date and time of the install

Machine: asus laptop i7 as well as samsung laptop i7
Partitions: df -Tl will do; the raw partition table is preferred


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

Initial boot:   [O ]
Detect network card: [E worked during the installation but was not 
transfered to the installed system which should have been done ]
Configure network:  [E worked during the installation process but was not 
transfered to the installed system which should have been done]
Detect CD:  [O ]
Load installer modules: [O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Detect hard drives: [O ]
Partition hard drives:  [O ]
Install base system:[O ]
Install tasks:  [O ]
Install boot loader:[O ]
Overall install:[E network configuration was not transfered to 
installed system so after I booted my system I had no internet access ]

Comments/Problems:
I managed to do the installation successfully but found that after the 
installation my network configuration settings were not transfered to my 
installed system so I had no internet access after the installation on a 
wireless network and had to restart the installation and go to the portion 
right after I was connected to the wireless network and copy over from the 
installer /etc/network/interfaces to my target system as I am totally blind and 
don't know of a nice user friendly tool for configuring wired or wireless 
networking after the installation is complete and am not using X windows
Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.
I think that over all the installation went ok but one thing that should be 
done is if more then one network interface is detected during the installation 
process like wired and wireless setup all of these network interfaces so they 
work during and after the installer and have these settings transfered to the 
installed system.  Also, have a package that uses your debconf frontend 
settings for setting up another network interface or for adding another 
wireless network or removing a wireless network for users who don't use X 
windows but like the method that the installer uses.

-- 

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

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

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7 (wheezy) - installer build 20130613+deb7u1
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux chihuahual2 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd 
Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel 

Bug#724054: marked as done (exrtools: FTBFS: no dependency information found for /usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by debian/exrtools/usr/bin/pngtoexr))

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2013 18:45:36 -0700
with message-id 1451439.VTvvUAC4mQ@frobozz
and subject line Re: Bug#724054: exrtools: FTBFS: no dependency information 
found for /usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by 
debian/exrtools/usr/bin/pngtoexr)
has caused the Debian Bug report #724054,
regarding exrtools: FTBFS: no dependency information found for 
/usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by 
debian/exrtools/usr/bin/pngtoexr)
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.)


-- 
724054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: exrtools
Version: 0.4-1.2
Severity: serious

From my pbuilder build log:

...
dh_fixperms
dh_fixperms: Compatibility levels before 5 are deprecated (level 4 in use)
dh_installdeb
dh_installdeb: Compatibility levels before 5 are deprecated (level 4 in use)
dh_shlibdeps
dh_shlibdeps: Compatibility levels before 5 are deprecated (level 4 in use)
dpkg-shlibdeps: error: no dependency information found for 
/usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by 
debian/exrtools/usr/bin/pngtoexr)
dh_shlibdeps: dpkg-shlibdeps -Tdebian/exrtools.substvars 
debian/exrtools/usr/bin/exricamtm debian/exrtools/usr/bin/ppmtoexr 
debian/exrtools/usr/bin/exrblur debian/exrtools/usr/bin/exrpptm 
debian/exrtools/usr/bin/jpegtoexr debian/exrtools/usr/bin/exrstats 
debian/exrtools/usr/bin/exrnlm debian/exrtools/usr/bin/exrnormalize 
debian/exrtools/usr/bin/pngtoexr debian/exrtools/usr/bin/exrtopng 
debian/exrtools/usr/bin/exrchr returned exit code 2
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
-- 
Daniel Schepler
---End Message---
---BeginMessage---
On Friday, October 25, 2013 08:18:32 PM gregor herrmann wrote:
 Builds fine here, probably due to recent changes in the libpng
 package?

I just tried it again and it builds fine here, too.  Closing.
-- 
Daniel Schepler---End Message---