Your message dated Sat, 03 May 2014 04:48:28 +
with message-id
and subject line Bug#719399: fixed in clojure1.2 1.2.1+dfsg-5
has caused the Debian Bug report #719399,
regarding clojure1.2: FTBFS: Unable to find a javac compiler
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 03 May 2014 04:48:28 +
with message-id
and subject line Bug#717015: fixed in clojure1.2 1.2.1+dfsg-5
has caused the Debian Bug report #717015,
regarding clojure1.2: FTBFS with Java7
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sat, 3 May 2014 12:18:02 +0900
with message-id <20140503031802.gb1...@falafel.plessy.net>
and subject line Re: Bug#746639: netty: CVE-2014-0193
has caused the Debian Bug report #746639,
regarding netty: CVE-2014-0193
to be marked as done.
This means that you claim that the probl
Processing commands for cont...@bugs.debian.org:
> retitle 735339 Non free w3c valid icons
Bug #735339 [src:boost1.54] Non free w3m valid icons
Changed Bug title to 'Non free w3c valid icons' from 'Non free w3m valid icons'
> thanks
Stopping processing here.
Please contact me if you need assistan
On 03/14/2014 03:55 PM, Hideki Yamane wrote:
> control: tags -1 +fixed-upstream +patch
>
> Hi,
>
> I've prepared patch for this bug as attached.
> Please consider to apply it. Thanks.
Hi,
I have applied the fix and uploaded the new version to DELAYED/2.
Cheers,
Balint
--
To UNSUBSCRIBE, e
Your message dated Fri, 02 May 2014 22:48:49 +
with message-id
and subject line Bug#746624: fixed in python-biopython 1.63+dfsg-2
has caused the Debian Bug report #746624,
regarding python-biopython: FTBFS - t_coffee needs HOME or TMP
to be marked as done.
This means that you claim that the p
Processing commands for cont...@bugs.debian.org:
> severity 746592 important
Bug #746592 [mailman] Upgrade/backport mailman as package has been made
unusable by DMARC
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
746592:
severity 746592 important
thanks
On Thu, 1 May 2014, juichenieder-deb...@yahoo.co.uk wrote:
> The introduction of DMARC by certain email-clients has severely
> crippled the use of mailman, making the current version in wheezy,
> virtually unusable
Only for Yahoo users, certainly not “grave”.
by
Your message dated Fri, 02 May 2014 21:34:09 +
with message-id
and subject line Bug#746659: fixed in google-mock 1.7.0-4
has caused the Debian Bug report #746659,
regarding google-mock: depends on python:all
to be marked as done.
This means that you claim that the problem has been dealt with.
If I'm not mistaken this issue has been resolved in rjava/0.9-6-2
uploaded on 17 Apr 2014.
Emmanuel Bourg
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
control: severity -1 important
Hi Dave,
thanks for your flood of bugs against piuparts, seen with fresh eyes, much
appreciated! Also I really like that you're using the packaged version, as...,
well, see the TODO for 0.59 ;-)
Obviously I'd appreciate patches for all those issues as well ;-) Bu
Processing control commands:
> severity -1 important
Bug #746721 [piuparts-master] piuparts-master/slave cron file syntax wrong
Severity set to 'important' from 'serious'
--
746721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746721
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Package: piuparts-master
Severity: serious
thanks
Cron files, installed in /etc/cron.d, are not in the right format. The
required 'user' field is omitted.
Because of this issue, slaves are not started at boot, and no normal
recovery or retest actions are taken. Reports are not automatically
gener
Your message dated Fri, 02 May 2014 22:21:26 +0200
with message-id <87ppjwszi1@deep-thought.43-1.org>
and subject line Re: Bug#746211: coinor-ipopt: FTBFS on s390x (configure:
error: C compiler cannot create executables)
has caused the Debian Bug report #746211,
regarding coinor-ipopt: FTBFS o
Your message dated Fri, 02 May 2014 18:49:17 +
with message-id
and subject line Bug#735940: fixed in tahoe-lafs 1.10.0-2
has caused the Debian Bug report #735940,
regarding Sourceless file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Control: severity -1 normal
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing control commands:
> severity -1 normal
Bug #746702 [libappstream0] libappstream0: Changes in libappstream0 ABI broke
apper [KDE]
Severity set to 'normal' from 'critical'
--
746702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746702
Debian Bug Tracking System
Contact ow...@bugs.d
Control: reassign -1 src:mozjs24 24.2.0-1
On Vi, 02 mai 14, 19:51:39, Emilio Pozuelo Monfort wrote:
> Source: libmozjs-24-0
> Version: 24.2.0-1
> Severity: serious
>
> Hi,
>
> libmozjs-24-0 has wrong shlibs information on !linux. It should be
>
> libmozjs-24 0 libmozjs-24-0
>
> like on linux
Processing control commands:
> reassign -1 src:mozjs24 24.2.0-1
Bug #746705 [src:libmozjs-24-0] libmozjs-24-0: wrong shlibs on !linux
Warning: Unknown package 'src:libmozjs-24-0'
Bug reassigned from package 'src:libmozjs-24-0' to 'src:mozjs24'.
No longer marked as found in versions libmozjs-24-0/2
Package: invesalius
Version: 3.0~b5-1B
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks
Dear Maintainer,
please add the missing licenses of:
invesalius3-3.0-b5\invesalius\gui\widgets\platebtn.py
to debian/copyright.
Thanks!
Thorst
Source: libmozjs-24-0
Version: 24.2.0-1
Severity: serious
Hi,
libmozjs-24-0 has wrong shlibs information on !linux. It should be
libmozjs-24 0 libmozjs-24-0
like on linux arches, but instead they have:
libmozjs 24 libmozjs-24-0
This is causing FTBFS on gjs, hence severity serious.
This i
Your message dated Fri, 02 May 2014 17:49:25 +
with message-id <20140502-124924.sv10516.26...@savannah.gnu.org>
has caused the report #746443,
regarding make: New make behaviour confuses dpkg-buildpackages' test for make
targets
to be marked as having been forwarded to the upstre
Your message dated Fri, 02 May 2014 17:42:37 +
with message-id
and subject line Bug#744250: Removed package(s) from unstable
has caused the Debian Bug report #733959,
regarding Migrate to yui3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 02 May 2014 17:42:37 +
with message-id
and subject line Bug#744250: Removed package(s) from unstable
has caused the Debian Bug report #723909,
regarding jifty: FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 02 May 2014 17:42:37 +
with message-id
and subject line Bug#744250: Removed package(s) from unstable
has caused the Debian Bug report #736730,
regarding [src:jifty] Sourceless file
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 02 May 2014 17:40:22 +
with message-id
and subject line Bug#746676: Removed package(s) from unstable
has caused the Debian Bug report #742442,
regarding garmin-ant-downloader: Segfaults on amd64
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 May 2014 17:36:29 +
with message-id
and subject line Bug#745023: Removed package(s) from unstable
has caused the Debian Bug report #741843,
regarding volview: FTBFS: vtkKWWizard.cxx:162:51: error: 'Tcl_Interp' has no
member named 'result'
to be marked as done.
This
Your message dated Fri, 02 May 2014 17:37:28 +
with message-id
and subject line Bug#746671: Removed package(s) from unstable
has caused the Debian Bug report #724141,
regarding libjifty-plugin-chart-perl: FTBFS: Tests failures
to be marked as done.
This means that you claim that the problem h
Never mind, that command did reproduce the problem after all; I just
thought otherwise at first because t_coffee ran for a while before
reporting failure.
-- Aaron
"Aaron M. Ucko" writes:
> Hi, Andreas.
>
> This failure is due entirely to the autobuilders' configuration, which
> supplies a nomi
On Fri, May 2, 2014 at 12:48 PM, Michael Biebl wrote:
> This is already possible today: The systemd package (intentionally)
> doesn't conflict with sysvinit-core since there are no file conflicts.
>
> You can install it and boot with init=/lib/systemd/systemd.
> The systemd-sysv package is intenti
Am 02.05.2014 18:27, schrieb Zack Weinberg:
> I don't wish to play bug tracker ping-pong here, but I feel that you
> are still missing the point. This is not about the default for new
> installations, this is not about opt-out versus opt-in to the switch.
>
> This is about *upgrade safety*.
>
>
Package: libappstream0
Version: 0.6-1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
libappstream0 was updated in Debian testing from 0.5-1 to 0.6-1, while apper
remained version 0.8.1-1.
* What exactly did you do (or not do)
Hi, Andreas.
This failure is due entirely to the autobuilders' configuration, which
supplies a nominal home directory path of /sbuild-nonexistent because
package builds should ignore users' actual home directories. As such,
an automatic build on amd64 (for a binNMU, or to enforce a strict policy
I don't wish to play bug tracker ping-pong here, but I feel that you
are still missing the point. This is not about the default for new
installations, this is not about opt-out versus opt-in to the switch.
This is about *upgrade safety*.
Upgrade safety, IMNSHO, requires a stabilization point in
Your message dated Fri, 02 May 2014 15:40:53 +
with message-id
and subject line Bug#745720: fixed in polarssl 1.3.7-1
has caused the Debian Bug report #745720,
regarding polarssl: FTBFS on mips, powerpc, s390x and sparc
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 May 2014 15:41:10 +
with message-id
and subject line Bug#746055: fixed in ruby-fakeweb
1.3.0+git20131202.48208f9+dfsg-1
has caused the Debian Bug report #746055,
regarding ruby-fakeweb: FTBFS: ERROR: Test "ruby2.1" failed
to be marked as done.
This means that you c
Your message dated Fri, 02 May 2014 15:40:53 +
with message-id
and subject line Bug#745716: fixed in polarssl 1.3.7-1
has caused the Debian Bug report #745716,
regarding libpolarssl-dev: /usr/lib/libpolarssl.so still points to
libpolarssl.so.5
to be marked as done.
This means that you claim
Your message dated Fri, 02 May 2014 15:41:41 +
with message-id
and subject line Bug#738256: fixed in tomboy 1.15.4-1
has caused the Debian Bug report #738256,
regarding tomboy: FTBFS: unsatisfiable Build-Depends: libdbus1.0-cil-dev (>=
0.4), libdbus-glib1.0-cil-dev (>= 0.3)
to be marked as do
Your message dated Fri, 02 May 2014 17:36:41 +0200
with message-id <5363bb89.2020...@debian.org>
and subject line Re: Bug#746577: closed by Michael Biebl
(Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and
sysvinit-core must be coinstallable)
has caused the Debian Bug report #746
Control: reopen -1
> You didn't show any actual breakage, so closing the bug report.
> If you can show us of actual breakage caused by the switch to
> systemd where the system will not boot, we will certainly deal
> with it.
I believe you have missed the point of the bug report. This is not
abou
Processing control commands:
> reopen -1
Bug #746577 {Done: Michael Biebl } [src:systemd]
systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be
coinstallable
Bug reopened
Ignoring request to alter fixed versions of bug #746577 to the same values
previously set
--
746577: ht
Dear Jordi,
thank you for your reply!
Am Donnerstag, den 01.05.2014, 15:32 +0200 schrieb Jordi Mallach:
> On Wed, Apr 30, 2014 at 01:16:44AM +0200, Paul Menzel wrote:
> > Package: evolution-data-server
> > Version: 3.12.0-1
> > Severity: grave
> > Tags: upstream
> > Justification: renders pack
I could fix this via an NMU if there wouldn't be any objections - I
haven't contacted the release team yet though, and I need a sponsor.
Diff for my suggested NMU attached.
best regards
-- Andreas Rönnquist
gus...@gusnan.se
diff -u catfish-0.3.2/debian/changelog catfish-0.3.2/debian/changelog
---
Your message dated Sat, 3 May 2014 00:03:35 +0900
with message-id <20140502150334.ga21...@lilith.infoblue.home>
and subject line Re: celery: Fails to build from source
has caused the Debian Bug report #745739,
regarding celery: Fails to build from source
to be marked as done.
This means that you c
Your message dated Sat, 3 May 2014 00:03:35 +0900
with message-id <20140502150334.ga21...@lilith.infoblue.home>
and subject line Re: celery: Fails to build from source
has caused the Debian Bug report #745739,
regarding celery: FTBFS: Tests failures
to be marked as done.
This means that you claim
Hi Aaron,
thanks for your bug report. I wonder whether you could test this at you
site and add this variable to the line ind debian/rules starting with
env DIALIGN2_DIR=/usr/share/dialign EMBOSS_ROOT=/usr/lib/emboss
since the problem you reported does not occure on amd64 I can just wild
gues
Dear Georges,
2.5.2014 16.14 kirjoitti "Georges Khaznadar" :
>
> Dear Juhani,
>
> thank you for your hint!
>
> unfortunately, files installed to usr/local are generally not a possible
> cause for FTBFS bugs. In the worst case, the package is built
> successfully, but some files are not copied to t
My system has neither UEFI nor LVM, no issues on reboot with the latest
version (2.02~beta2-9).
--
Joerg
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This bug affects the current stable branch. When upgrading
python2.7-minimal from 2.7.3-6 to 2.7.3-6+deb7u2, python dies an ugly
death.
Please upload a fix soon.
Cheers,
- --
Luis Alejandro Martínez Faneyth
Blog: http://huntingbears.com.ve
Github:
On Fri, May 02, 2014 at 07:32:32PM +0530, Pirate Praveen wrote:
> Hi,
>
> I think the upstream should keep it in a sub-directory like temple, but
> strong_parameters upstream seems adamant on not changing.
>
> Should this be handled at gem2deb level? Moving to debian-ruby for wider
> comments.
>
Processing commands for cont...@bugs.debian.org:
> forwarded 746594 https://tracker.moodle.org/browse/MDL-45395
Bug #746594 [moodle] Embedded OLE is not DFSG-compliant (PHP-2.02)
Set Bug forwarded-to-address to 'https://tracker.moodle.org/browse/MDL-45395'.
> On 2 May 2014 21:50, Thijs Kinkhorst
forwarded 746594 https://tracker.moodle.org/browse/MDL-45395
On 2 May 2014 21:50, Thijs Kinkhorst wrote:
> It's indeeed a second copy, it's under lib/phpexcel/PHPExcel/Shared/
Thanks! Grr!
I've created https://tracker.moodle.org/browse/MDL-45395
cheers,
Dan
--
To UNSUBSCRIBE, email to debi
Processing commands for cont...@bugs.debian.org:
> block 720911 by 717015
Bug #720911 [ftp.debian.org] RM: openjdk-6 -- ROM; openjdk-7 replaces it
720911 was blocked by: 732233 720572 720571 717122 720570 717249 720552 720557
727805 720551 720573 720569 727791 727806 720561 683450 727789 674930
7
Hi,
On Fri, May 02, 2014 at 08:48:28AM +0200, Moritz Muehlenhoff wrote:
> > the following vulnerability was published for rxvt-unicode.
> >
> > CVE-2014-3121[0]: user-assisted arbitrary commands execution
>
> Can you backport the change to oldstable-security and stable-security?
Thanks for the
Hi,
I think the upstream should keep it in a sub-directory like temple, but
strong_parameters upstream seems adamant on not changing.
Should this be handled at gem2deb level? Moving to debian-ruby for wider
comments.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746677
Or should we handle th
control: tags -1 +unreproducible
Hi,
Once I'd tag it as unreproducible as attached log.
Of course, feel free to untag it.
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
ruby-em-hiredis_0.2.1-2.log
Description: Binary data
Processing control commands:
> tags -1 +unreproducible
Bug #746121 [src:ruby-em-hiredis] ruby-em-hiredis: FTBFS: ERROR: Test "ruby2.0"
failed
Added tag(s) unreproducible.
--
746121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746121
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Re: Hannu Valtonen 2014-05-02 <53639ce0.30...@ohmu.fi>
> Hi,
>
> This has now been fixed by:
> https://github.com/ohmu/pgmemcache/commit/47623a545be485d6dd1ffb917e990d267ad57f35
Cool, thanks.
Do you plan to release a new version, or should I apply the patch to
the current version in Debian for
Processing commands for cont...@bugs.debian.org:
> tags 746524 + moreinfo
Bug #746524 [ftp.debian.org] RM: libnl -- ROM; dead upstream, replaced by libnl3
Added tag(s) moreinfo.
> block 746524 with 688168
Bug #746524 [ftp.debian.org] RM: libnl -- ROM; dead upstream, replaced by libnl3
746524 was n
Hi Dan,
On Fri, May 2, 2014 04:02, Dan Poltawski wrote:
> On 2 May 2014 02:46, David Prévot wrote:
>> The embedded PHPExcel copy (#718585) embeds OLE (#487558) which is not
>> DFSG compliant (PHP-2.02)[1,2].
>
> We have removed this library in upstream in version 2.6:
>
> https://tracker.moodle.
Hi,
This has now been fixed by:
https://github.com/ohmu/pgmemcache/commit/47623a545be485d6dd1ffb917e990d267ad57f35
- Hannu
On 2.4.2014 19.02, Christoph Berg wrote:
Hi,
when rebuilt with libmemcached11, pgmemcache in Debian started to
segfault. It worked with libmemcached10 before.
I'm not
Your message dated Fri, 02 May 2014 13:33:22 +
with message-id
and subject line Bug#743863: Removed package(s) from unstable
has caused the Debian Bug report #743862,
regarding keep tiff3 out of testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Fri, 02 May 2014 13:23:39 +
with message-id
and subject line Bug#746664: Removed package(s) from unstable
has caused the Debian Bug report #743120,
regarding haskell-wai-logger-prefork: FTBFS: Not in scope: type constructor or
class `Logger'
to be marked as done.
This mean
Processing commands for cont...@bugs.debian.org:
> clone 741230 -1 -2
Bug #741230 [ftp.debian.org] RM: haskell-tls-extra haskell-wai-logger-prefork
haskell-date-cache -- ROM; obsoleted by upstream
Bug 741230 cloned as bugs 746664-746665
746664 was not blocked by any bugs.
746664 was blocking: 743
Dear Juhani,
thank you for your hint!
unfortunately, files installed to usr/local are generally not a possible
cause for FTBFS bugs. In the worst case, the package is built
successfully, but some files are not copied to the binary package.
Best regards, Georges.
Juhani Nummine
Package: google-mock
Version: 1.7.0-3
Severity: serious
Your package depends on "python:all", a dependency which makes no sense
and which apt considers unsatisfiable, although dpkg apparently has no
problem with it. According to the Debian changelog you meant
"python:any" instead.
-- System Inf
Your message dated Fri, 02 May 2014 12:33:19 +
with message-id
and subject line Bug#743347: Removed package(s) from unstable
has caused the Debian Bug report #720791,
regarding libjifty-plugin-oauth-perl: FTBFS: test failure
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 02 May 2014 12:33:49 +
with message-id
and subject line Bug#742108: Removed package(s) from unstable
has caused the Debian Bug report #722380,
regarding Depends on Ruby 1.8 which will not be available in jessie
to be marked as done.
This means that you claim that the p
Your message dated Fri, 02 May 2014 12:32:46 +
with message-id
and subject line Bug#745900: Removed package(s) from unstable
has caused the Debian Bug report #713709,
regarding rubrica: FTBFS: ld: main.o: undefined reference to symbol
'g_thread_init'
to be marked as done.
This means that you
Your message dated Fri, 02 May 2014 12:29:45 +
with message-id
and subject line Bug#742107: Removed package(s) from unstable
has caused the Debian Bug report #722389,
regarding Depends on Ruby 1.8 which will not be available in jessie
to be marked as done.
This means that you claim that the p
Your message dated Fri, 02 May 2014 12:28:17 +
with message-id
and subject line Bug#743901: Removed package(s) from unstable
has caused the Debian Bug report #659645,
regarding sharand: SHA-1 code is doesn't allow modification
to be marked as done.
This means that you claim that the problem h
Your message dated Fri, 02 May 2014 12:29:00 +
with message-id
and subject line Bug#743346: Removed package(s) from unstable
has caused the Debian Bug report #720792,
regarding libjifty-plugin-wikitoolbar-perl: FTBFS: test failure
to be marked as done.
This means that you claim that the probl
Your message dated Fri, 02 May 2014 12:24:10 +
with message-id
and subject line Bug#744881: Removed package(s) from unstable
has caused the Debian Bug report #637488,
regarding t1lib: history of security issues, unmaintained upstream,
unsupportable
to be marked as done.
This means that you c
Your message dated Fri, 02 May 2014 12:26:58 +
with message-id
and subject line Bug#745862: Removed package(s) from unstable
has caused the Debian Bug report #614498,
regarding guppy: FTBFS with Python 2.7: ImportError: guppy/sets/setsc.so:
undefined symbol: _PyLong_AsScaledDouble
to be marke
Your message dated Fri, 02 May 2014 12:19:23 +
with message-id
and subject line Bug#740680: Removed package(s) from unstable
has caused the Debian Bug report #735433,
regarding aswiki: Please migrate to Ruby 1.9/2.0
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Fri, 02 May 2014 12:21:06 +
with message-id
and subject line Bug#743345: Removed package(s) from unstable
has caused the Debian Bug report #720789,
regarding libjifty-plugin-comment-perl: FTBFS: test failure
to be marked as done.
This means that you claim that the problem h
Your message dated Fri, 02 May 2014 12:20:30 +
with message-id
and subject line Bug#744806: Removed package(s) from unstable
has caused the Debian Bug report #743102,
regarding haskell-zeromq3-haskell: FTBFS: Base.hsc:12:2: error: #error ***
INVALID 0MQ VERSION (must be 3.x) ***
to be marked
Your message dated Fri, 02 May 2014 12:19:59 +
with message-id
and subject line Bug#740679: Removed package(s) from unstable
has caused the Debian Bug report #730972,
regarding ruby-amrita: FTBFS: Hard dependency on ruby1.8
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 02 May 2014 12:19:59 +
with message-id
and subject line Bug#740679: Removed package(s) from unstable
has caused the Debian Bug report #735194,
regarding can we remove ruby-amrita from archive in favour of ruby-amrita2?
to be marked as done.
This means that you claim th
Your message dated Fri, 02 May 2014 12:15:38 +
with message-id
and subject line Bug#742326: Removed package(s) from unstable
has caused the Debian Bug report #708450,
regarding indicator-application: FTBFS: application-service.c:55:2: error:
'g_type_init' is deprecated (declared at
/usr/incl
Your message dated Fri, 02 May 2014 12:12:12 +
with message-id
and subject line Bug#745932: Removed package(s) from unstable
has caused the Debian Bug report #717376,
regarding yardradius: subprocess installed post-installation script returned
error exit status 1 on configure
to be marked as
Your message dated Fri, 02 May 2014 12:12:12 +
with message-id
and subject line Bug#745932: Removed package(s) from unstable
has caused the Debian Bug report #714612,
regarding yardradius: CVE-2013-4147: Multiple Format String Vulnerabilities
to be marked as done.
This means that you claim th
Your message dated Fri, 02 May 2014 12:13:13 +
with message-id
and subject line Bug#745896: Removed package(s) from unstable
has caused the Debian Bug report #707854,
regarding scribes: depends on python-gtkspell which is going away
to be marked as done.
This means that you claim that the pro
Your message dated Fri, 02 May 2014 12:11:03 +
with message-id
and subject line Bug#742342: Removed package(s) from unstable
has caused the Debian Bug report #642570,
regarding python-pyhyphen: FTBFS: Permission denied:
'/usr/lib/python2.7/dist-packages/hyphen/config.pyc'
to be marked as done
Your message dated Fri, 02 May 2014 12:03:42 +
with message-id
and subject line Bug#742340: Removed package(s) from unstable
has caused the Debian Bug report #738390,
regarding telak: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libImlib2.so: undefined
reference to symbol 'XGetWindowAttributes'
to be
Your message dated Fri, 02 May 2014 12:03:42 +
with message-id
and subject line Bug#742340: Removed package(s) from unstable
has caused the Debian Bug report #641409,
regarding package ftbfs with ld --as-needed
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 02 May 2014 11:52:36 +
with message-id
and subject line Bug#730275: Removed package(s) from unstable
has caused the Debian Bug report #735352,
regarding Sourceless file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 02 May 2014 11:52:56 +
with message-id
and subject line Bug#730275: Removed package(s) from experimental
has caused the Debian Bug report #730268,
regarding libboost1.53-tools-dev: file conflicts with libboost1.54-dev,
libboost1.49-dev
to be marked as done.
This means
Your message dated Fri, 02 May 2014 11:52:56 +
with message-id
and subject line Bug#730275: Removed package(s) from experimental
has caused the Debian Bug report #735352,
regarding Sourceless file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 02 May 2014 11:52:36 +
with message-id
and subject line Bug#730275: Removed package(s) from unstable
has caused the Debian Bug report #730268,
regarding libboost1.53-tools-dev: file conflicts with libboost1.54-dev,
libboost1.49-dev
to be marked as done.
This means tha
Your message dated Fri, 02 May 2014 11:52:36 +
with message-id
and subject line Bug#730275: Removed package(s) from unstable
has caused the Debian Bug report #735338,
regarding Non free w3m valid icons
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Fri, 02 May 2014 11:52:56 +
with message-id
and subject line Bug#730275: Removed package(s) from experimental
has caused the Debian Bug report #735338,
regarding Non free w3m valid icons
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Fri, 02 May 2014 11:47:04 +
with message-id
and subject line Bug#745959: Removed package(s) from unstable
has caused the Debian Bug report #71,
regarding "pynetsnmp: hardcodes knowledge about external ABIs"
to be marked as done.
This means that you claim that the proble
Your message dated Fri, 02 May 2014 11:48:23 +
with message-id
and subject line Bug#745905: Removed package(s) from unstable
has caused the Debian Bug report #713654,
regarding pathfinder: FTBFS: functional:495:9: error: cannot allocate an object
of abstract type 'xplc_ptr::ProtectedPtr'
to b
Your message dated Fri, 02 May 2014 11:47:04 +
with message-id
and subject line Bug#745959: Removed package(s) from unstable
has caused the Debian Bug report #712221,
regarding python-pynetsnmp: depends on libsnmp15
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Fri, 02 May 2014 19:13:08 +0800
with message-id <53637dc4.5000...@debian.org>
and subject line Re: FTBFS as test does not terminate
has caused the Debian Bug report #746360,
regarding FTBFS as test does not terminate
to be marked as done.
This means that you claim that the probl
Your message dated Fri, 02 May 2014 11:04:50 +
with message-id
and subject line Bug#746104: fixed in ruby-faraday-middleware 0.9.1-1
has caused the Debian Bug report #746104,
regarding ruby-faraday-middleware: FTBFS: ERROR: Test "ruby2.0" failed
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> severity 746358 serious
Bug #746358 [systemd] systemd: system boot hangs if /etc/fstab contains an NFS
mount
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
746358: http
Your message dated Fri, 02 May 2014 15:35:54 +0530
with message-id <53636e02.10...@onenetbeyond.org>
and subject line binNMUs completed for all affected packages
has caused the Debian Bug report #743664,
regarding ruby-*: file conflict on
/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/mkmf.log
t
Package: wicd-curses
Version: 1.7.2.4-4
Severity: serious
Justification: Policy 7.2
Dear Maintainer,
as already reported in #612501 bug for wicd-kde, it seems that
wicd-curses cannot be installed on kfreebsd-i386 architecture,
since it depends on wicd-daemon package, which in turn depends
on wire
1 - 100 of 105 matches
Mail list logo
