Package: freebsd-buildutils,freebsd-glue
Version: freebsd-buildutils/9.0-11
Version: freebsd-glue/0.0.6
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2013-07-06
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file a
Processing control commands:
> severity 715110 normal
Bug #715110 [libsamba-util-dev] Broken library symlink detected in
libsamba-util-dev
Severity set to 'normal' from 'serious'
> severity 715122 normal
Bug #715122 [libtorture-dev] Broken library symlink detected in libtorture-dev
Severity set t
Control: severity 715110 normal
Control: severity 715122 normal
On Sat, Jul 06, 2013 at 05:01:15AM +, David Steele wrote:
> Package: libsamba-util-dev
> Version: 4.0.0~beta2+dfsg1-3.2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts, broken-symlink, broken-symlink-sh
Your message dated Fri, 5 Jul 2013 22:29:48 -0700
with message-id <20130706052948.gg31...@ofb.net>
and subject line Re: [Debichem-devel] Bug#715068: Broken library symlink
detected in gromacs-dev
has caused the Debian Bug report #715068,
regarding Broken library symlink detected in gromacs-dev
to
Package: nordugrid-arc-dev
Version: 3.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. S
Package: trafficserver-dev
Version: 3.2.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. S
Package: rygel-2.0-dev
Version: 0.18.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: sra-toolkit-libs-dev
Version: 2.1.7a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared librar
Package: lldb-3.4
Version: 1:3.4~svn183914-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: yate-dev
Version: 4.3.0-1~dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Suc
Package: libtorture-dev
Version: 4.0.0~beta2+dfsg1-3.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared
Package: libxs-compat-libzmq-dev
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libr
Package: libstarpu-dev
Version: 1.0.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libsquizz-dev
Version: 0.99b+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: lldb-3.3
Version: 1:3.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failu
Package: libwtdbomysql-dev
Version: 3.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. S
Package: libspeechd-dev
Version: 0.7.1-6.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libwnn-dev
Version: 1.1.1~a021+cvs20100325-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared
Package: libuim-dev
Version: 1:1.8.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such f
Package: libwcat1-dev
Version: 1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such fai
Package: libwaei-dev
Version: 3.6.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such fa
Package: libsamba-util-dev
Version: 4.0.0~beta2+dfsg1-3.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a sha
Package: libsaga-dev
Version: 2.0.8+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libsoupcutter-dev
Version: 1.1.7-1.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: libsdl-sound-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libsdl-ttf-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libsocksd0-dev
Version: 1.1.19.dfsg-3+b4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libr
Package: libsbml5-cil
Version: 5.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such f
Package: libscotchmetis-dev
Version: 5.1.12b.dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared li
Package: libsdl-mixer-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libsdl-image-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libpythonqt2-dev
Version: 2.0.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: libpacparser-dev
Version: 1.3.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libpcp-mmv1-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libplplot-dev
Version: 5.9.9-5+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libpcp-import1-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: libpoco-dev
Version: 1.3.6p1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libostyle-dev
Version: 1.4devel1-20.1+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libr
Package: libptscotch-dev
Version: 5.1.12b.dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libra
Package: libpcp-gui2-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libpcp-trace2-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Suc
Package: libpcp-pmda3-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libmpich-shmem1.0-dev
Version: 1.2.7-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libra
Package: libkwnn-dev
Version: 1.1.1~a021+cvs20100325-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared
Package: libm17n-im-config-dev
Version: 0.9.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared librar
Package: libns3-dev
Version: 3.17+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: liblz-dev
Version: 1.3-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failur
Package: libjack-jackd2-dev
Version: 1.9.9.5+20130622git7de15e7a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involv
Package: libopenmpi1.6-dev
Version: 1.6.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. S
Package: libmudflap0-4.8-dev
Version: 4.8.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: libncurses-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libmp3splt-dev
Version: 0.7.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libjack-dev
Version: 1:0.121.3+20120418git75e3e20b-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
Package: libgrok-dev
Version: 1.20110708.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: libhamlib++-dev
Version: 1.2.15.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library.
Package: libgeomview-dev
Version: 1.9.4-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Suc
Package: libiodbc2-dev
Version: 3.52.7-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libdmraid-dev
Version: 1.0.0.rc16-4.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library
Package: libibdm-dev
Version: 1.2-OFED-1.4.2-1.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libra
Package: libelk0-dev
Version: 3.99.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such f
Package: libfence-dev
Version: 3.1.8-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such
Package: libboost-graph1.53-dev
Version: 1.53.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libr
Package: libboost-graph-parallel1.49-dev
Version: 1.49.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a sh
Package: gnash-dev
Version: 0.8.11~git20120629-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libra
Package: libdime-dev
Version: 0.20030921-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Su
Package: gromacs-dev
Version: 4.5.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such fa
Package: libboost-graph1.49-dev
Version: 1.49.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libr
Package: heimdal-multidev
Version: 1.6~git20120403+dfsg1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a sh
Package: libcwnn-dev
Version: 1.1.1~a021+cvs20100325-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared
Package: libboost-graph-parallel1.53-dev
Version: 1.53.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a sh
Package: libapron-dev
Version: 0.9.10-5.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Suc
Package: firebird-dev
Version: 2.5.2.26540.ds4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library
Hi,
During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared libra
Processing commands for cont...@bugs.debian.org:
> tags 701744 + pending
Bug #701744 [src:linux] [xen] Update to hypervisor 4.0.1-5.6 or
linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you nee
Your message dated Sat, 06 Jul 2013 01:48:05 +
with message-id
and subject line Bug#711055: fixed in ucf 3.0027+nmu1
has caused the Debian Bug report #711055,
regarding grub-common: ucfq error reported when installing grub2
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 06 Jul 2013 01:48:05 +
with message-id
and subject line Bug#711055: fixed in ucf 3.0027+nmu1
has caused the Debian Bug report #711055,
regarding Undefined subroutine &conffile::abs_path called at /usr/bin/ucfq line
529, line 13.
to be marked as done.
This means that
Your message dated Sat, 06 Jul 2013 01:48:05 +
with message-id
and subject line Bug#711055: fixed in ucf 3.0027+nmu1
has caused the Debian Bug report #711055,
regarding php5-common: unowned files after purge (policy 6.8, 10.8):
/etc/php5/mods-available/{opcache, pdo}.ini
to be marked as done.
Your message dated Sat, 06 Jul 2013 01:03:03 +
with message-id
and subject line Bug#707531: fixed in python-pam 0.4.2-13.1
has caused the Debian Bug report #707531,
regarding python-pam: FTBFS: /bin/sh: 2: python2.6: not found
to be marked as done.
This means that you claim that the problem h
Your message dated Sat, 06 Jul 2013 00:33:56 +
with message-id
and subject line Bug#701398: fixed in id-utils 4.5+dfsg-0.2
has caused the Debian Bug report #701398,
regarding id-utils: ftbfs with eglibc-2.17
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 06 Jul 2013 00:19:17 +
with message-id
and subject line Bug#701445: fixed in xcp-vncterm 0.1-2.1
has caused the Debian Bug report #701445,
regarding xcp-vncterm: ftbfs with eglibc-2.17
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Sat, 06 Jul 2013 00:03:50 +
with message-id
and subject line Bug#701433: fixed in jfsutils 1.1.15-2.1
has caused the Debian Bug report #701433,
regarding jfsutils: ftbfs with eglibc-2.17
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Processing control commands:
> reopen -1
Bug #714996 {Done: Thomas Leonard } [zeroinstall-injector]
zeroinstall-injector: needs to be Architecture: any due to OCaml dependencies
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you ma
Control: reopen -1
Thanks for the attempt, but you need to move your binary-indep rules to
binary-arch to make this work, otherwise it fails to build everywhere
except the upload architecture:
https://buildd.debian.org/status/package.php?pkg=zeroinstall-injector
https://launchpad.net/ubuntu/+
Your message dated Fri, 05 Jul 2013 21:05:19 +
with message-id
and subject line Bug#701305: fixed in libemu 0.2.0+git20120122-1.1
has caused the Debian Bug report #701305,
regarding libemu: ftbfs with GCC-4.8
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Fri, 05 Jul 2013 21:05:19 +
with message-id
and subject line Bug#693090: fixed in libemu 0.2.0+git20120122-1.1
has caused the Debian Bug report #693090,
regarding python-libemu: doesn't depend on python
to be marked as done.
This means that you claim that the problem has be
Your message dated Fri, 05 Jul 2013 19:19:24 +
with message-id
and subject line Bug#708711: fixed in krb5 1.10.1+dfsg-6.1
has caused the Debian Bug report #708711,
regarding cannot upgrade to 1.10.1+dfsg-6 on multiarch (amd64 and i386)
to be marked as done.
This means that you claim that the
Your message dated Fri, 05 Jul 2013 19:19:24 +
with message-id
and subject line Bug#708711: fixed in krb5 1.10.1+dfsg-6.1
has caused the Debian Bug report #708711,
regarding src:krb5: 1.10.1+dfsg-6 builds on 0 architectures
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 05 Jul 2013 19:19:24 +
with message-id
and subject line Bug#708711: fixed in krb5 1.10.1+dfsg-6.1
has caused the Debian Bug report #708711,
regarding krb5: FTBFS: texinfo errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Fri, 05 Jul 2013 19:19:24 +
with message-id
and subject line Bug#708711: fixed in krb5 1.10.1+dfsg-6.1
has caused the Debian Bug report #708711,
regarding libkrb5-3: depends problem with libkrb5-3:i386 in sid
to be marked as done.
This means that you claim that the problem
Package: netexpect
Version: 0.20-3
Followup-For: Bug #714535
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch
In Ubuntu, I've applied the following naive patch to port to the
wireshark 1.10 API. It looks like the _set_unset calls can probably
just go away, as they're
On Fri, 05 Jul 2013 20:38:03 +0200, Andreas Tille wrote:
> many thanks for the perfect job including committing to Git.
You're welcome!
> Feel free to upload to DELAYED\1 or even 0 in similar cases in the
> future.
Thanks, will try to remember.
Cheers,
gregor
--
.''`. Homepage: http://i
Hi Gregor,
many thanks for the perfect job including committing to Git.
Feel free to upload to DELAYED\1 or even 0 in similar cases in the
future.
Kind regards
Andreas.
On Fri, Jul 05, 2013 at 04:29:35PM +0200, gregor herrmann wrote:
> Control: tag -1 + patch pending
>
> On Thu, 06 J
Package: php-horde-webmail
Version: 5.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.
Your package ships:
/usr/share/horde/gollem/c
Package: php-horde-groupware
Version: 5.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.
Your package ships:
/usr/share/horde/gollem
Your message dated Fri, 05 Jul 2013 17:03:12 +
with message-id
and subject line Bug#713304: fixed in gearman-interface 0.13.2-3
has caused the Debian Bug report #713304,
regarding gearman-interface: FTBFS: /usr/share/automake-1.13/am/ltlibrary.am:
warning: 'libswig.la': linking libtool librar
Your message dated Fri, 05 Jul 2013 16:33:25 +
with message-id
and subject line Bug#714993: fixed in sane-backends 1.0.23-2
has caused the Debian Bug report #714993,
regarding 60-libsane.rules differs between architectures in M-A: same package
to be marked as done.
This means that you claim t
Your message dated Fri, 05 Jul 2013 16:19:05 +
with message-id
and subject line Bug#714987: fixed in gnuradio 3.7.0-2
has caused the Debian Bug report #714987,
regarding gnuradio: fails to install: SyntaxError in
/usr/share/gnuradio/examples/atsc/xlate.py, line 49
to be marked as done.
This
Your message dated Fri, 05 Jul 2013 13:00:48 -0300
with message-id <2303429.GT3ERG7xQX@tonks>
and subject line Re: [Pkg-kde-extras] Bug#713828: (no subject)
has caused the Debian Bug report #713828,
regarding basket: Basket crashes at the start
to be marked as done.
This means that you claim that
Source: basket
Source-Version: 1.81-3
On Friday 05 July 2013 16:01:27 Πρεκατές Αλέξανδρος wrote:
> Lisandro you are right!
>
> I hadnot enabled the lo interface in /etc/network/interfaces
>
> The reason being that after a very bumpy dist-upgrade process to wheezy from
> squueze networking broke
On Fri, Jul 05, 2013 at 02:15:19PM +0200, gregor herrmann wrote:
> Dear maintainer,
>
> I've prepared an NMU for dvbstreamer (versioned as 2.1.0-2.4) and
> uploaded it to DELAYED/2.
thanks a lot.
a.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubsc
Your message dated Fri, 05 Jul 2013 15:21:54 +
with message-id
and subject line Bug#713335: fixed in starpu 1.0.1-4
has caused the Debian Bug report #713335,
regarding starpu: FTBFS: doc/Makefile.am:62: warning: ':='-style assignments
are not portable
to be marked as done.
This means that yo
1 - 100 of 155 matches
Mail list logo
