Processing commands for cont...@bugs.debian.org:
> tags 672167 pending
Bug #672167 [fonts-bpg-georgian] fonts-bpg-georgian: fails to upgrade from
'testing' - trying to overwrite
/usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf
Added tag(s) pending.
> thanks
Stopping processing here.
P
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
Package: songwrite
Version: 0.14-8
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Songwrite fails to start like so:
Traceback (most recent call last):
File "/usr/bin/songwrite", line 134, in
import main
File "/usr/bin/../share/songwrite/main.py", line 21, in
Package: python-dolfin
Version: 1.0.0-4+b2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Here's an example traceback when running the poisson equation demo.
$ python demo_poisson.py
Traceback (most recent call last):
File "demo_poisson.py", line 40, in
from dolf
Hi Scott,
thanks for your effort. NMU is fine however, it would be really great
if you would commit your changes to SVN. The easiest way to do so
would probably be
debcheckout --user= pythonqt
Commit permissions are granted to every DD.
Kind regards and thanks again for helping us out
Your message dated Wed, 09 May 2012 06:18:23 +
with message-id
and subject line Bug#669505: fixed in tuxfootball 0.3.1-1
has caused the Debian Bug report #669505,
regarding tuxfootball: FTBFS: gcc: error: unrecognized option '-V'
to be marked as done.
This means that you claim that the proble
Stefan Lippers-Hollmann (09/05/2012):
> Thanks a lot, xserver-xorg-video-savage 1:2.3.4-1 is working perfectly.
Thanks for the confirmation, too.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Package: csladspa
Version: 1:5.17.6~dfsg-2
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
After a recent upgrade which included csladspa, several music/audio programs,
which were not themselves updated, failed to start with a segmentation fault.
So far this applies t
I'll upload the attached diff shortly to delay/2 in order to minimize impact on
the Qt 4.8 transition. If you'd prefer I delay it further because you are
preparing an upload, please let me know.
Scott K
diff -Nru pythonqt-2.0.1/debian/changelog pythonqt-2.0.1/debian/changelog
--- pythonqt-2.0.
On Tue, May 08, 2012 at 09:26:40PM +0200, Julien Cristau wrote:
> > > As I'd like this fixed ASAP to get the buildds back in working
> > > condition, I'll be preparing a NMU with --disable-fat. Please yell if
> > > you think I shouldn't upload it.
Thanks for this.
-Steve
signature.asc
Descrip
Your message dated Wed, 09 May 2012 03:17:20 +
with message-id
and subject line Bug#662712: fixed in fracplanet 0.4.0-2
has caused the Debian Bug report #662712,
regarding fracplanet: FTBFS against Qt 4.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi
On Wednesday 09 May 2012, Julien Cristau wrote:
> On Mon, May 7, 2012 at 09:08:54 +0200, Tormod Volden wrote:
[…]
> > Wow, a savage user! I am hoping to get a newer savage version done
> > soon, unless someone beats me to it. Anyway, this issue might be
> > outside the driver. Do you have libp
Processing commands for cont...@bugs.debian.org:
> #krb5 (1.10.1+dfsg-1) unstable; urgency=low
> #
> # * Fix use counts on preauthentication, Closes: #670457
> # * Fix kadmin access controls, Closes: #670918
> # * Fix history from old databases, Closes: #660869
> # * Fix gcc 4.6.2 may be used
Processing commands for cont...@bugs.debian.org:
> tags 672055 + patch
Bug #672055 [src:libstxxl] libstxxl: FTBFS: mlock.cpp:32:32: error: 'sleep' was
not declared in this scope
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
672055: http://bu
tags 672055 + patch
thanks
diff -Nru libstxxl-1.3.1/debian/changelog libstxxl-1.3.1/debian/changelog
--- libstxxl-1.3.1/debian/changelog 2012-02-18 14:40:48.0 +
+++ libstxxl-1.3.1/debian/changelog 2012-05-09 00:51:21.0 +
@@ -1,3 +1,10 @@
+libstxxl (1.3.1-2.1) unstab
Processing commands for cont...@bugs.debian.org:
> affects 672167 + ttf-bpg-georgian-fonts
Bug #672167 [fonts-bpg-georgian] fonts-bpg-georgian: fails to upgrade from
'testing' - trying to overwrite
/usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf
Added indication that 672167 affects tt
Processing commands for cont...@bugs.debian.org:
> severity 670918 normal
Bug #670918 [krb5] CVE-2012-1012
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
670918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670918
Debian
severity 670918 normal
thanks
> "Moritz" == Moritz Muehlenhoff writes:
Moritz> Package: krb5 Severity: grave Tags: security
Moritz> Please see
Moritz> https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-1012
Moritz> for details
I agree that Debian has the bug, but as Redha
Processing commands for cont...@bugs.debian.org:
> tags 672100 + patch
Bug #672100 [src:presage] presage: FTBFS: profileManagerTest.cpp:86:47: error:
'unlink' was not declared in this scope
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
67210
Processing commands for cont...@bugs.debian.org:
> tags 672076 + patch
Bug #672076 [src:libshevek] libshevek: FTBFS: src/file.cc:47:7: error:
'::close' has not been declared
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
672076: http://bugs.d
tags 672076 + patch
thanks
diff -u libshevek-1.2/debian/changelog libshevek-1.2/debian/changelog
--- libshevek-1.2/debian/changelog
+++ libshevek-1.2/debian/changelog
@@ -1,3 +1,10 @@
+libshevek (1.2-1.1) unstable; urgency=low
+
+ * Non maintainer upload.
+ * Fix build failure with GCC 4.7. Clos
tags 672100 + patch
thanks
diff -Nru presage-0.8.7/debian/changelog presage-0.8.7/debian/changelog
--- presage-0.8.7/debian/changelog 2011-10-23 16:23:26.0 +
+++ presage-0.8.7/debian/changelog 2012-05-08 22:45:24.0 +
@@ -1,3 +1,10 @@
+presage (0.8.7-1.1) unstable;
Processing commands for cont...@bugs.debian.org:
> tags 672086 + patch
Bug #672086 [src:libsfml] libsfml: FTBFS: Linux/Joystick.cpp:103:62: error:
'read' was not declared in this scope
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
672086: ht
Processing commands for cont...@bugs.debian.org:
> tags 672021 + patch
Bug #672021 [src:libpqxx3] libpqxx3: FTBFS: ../include/pqxx/util.hxx:412:5:
error: 'to_string' was not declared in this scope, and no declarations were
found by argument-dependent lookup at the point of instantiation [-fpermi
tags 672086 + patch
thanks
diff -u libsfml-1.6+dfsg1/debian/changelog libsfml-1.6+dfsg1/debian/changelog
--- libsfml-1.6+dfsg1/debian/changelog
+++ libsfml-1.6+dfsg1/debian/changelog
@@ -1,3 +1,10 @@
+libsfml (1.6+dfsg1-2.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix build failur
tags 672021 + patch
thanks
diff -Nru libpqxx3-3.1/debian/changelog libpqxx3-3.1/debian/changelog
--- libpqxx3-3.1/debian/changelog 2011-11-28 21:33:40.0 +
+++ libpqxx3-3.1/debian/changelog 2012-05-08 23:47:30.0 +
@@ -1,3 +1,10 @@
+libpqxx3 (3.1-1.1) unstable; ur
Processing commands for cont...@bugs.debian.org:
> tags 672074 + patch
Bug #672074 [src:libgwenhywfar] libgwenhywfar: FTBFS: libtest.cpp:117:14:
error: 'sleep' was not declared in this scope
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
6720
tags 672074 + patch
thanks
diff -u libgwenhywfar-4.3.1/debian/changelog
libgwenhywfar-4.3.1/debian/changelog
--- libgwenhywfar-4.3.1/debian/changelog
+++ libgwenhywfar-4.3.1/debian/changelog
@@ -1,3 +1,10 @@
+libgwenhywfar (4.3.1-1.1) unstable; urgency=low
+
+ * Non maintainer upload
+ * Fix bu
Package: python3-dbus
Version: 1.0.0-1
Severity: serious
Justification: Policy 3.5
python3-dbus doesn't depend on python3 and doesn't byte-compile its
Python modules. Perhaps you should use dh_python3?
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a
Package: itrans
Version: 5.3-10
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
* tex-common breaks itrans (<= 5.3-10)
It was already re
Package: kmail
Version: 4:4.4.11.1+l10n-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropiate ***
* What led up to the situation?
Upgrading kernel and unrelated software
* What exactly did you do (or not do
Package: libsdl-ruby
Version: 2.1.1.1-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
* ruby-sdl breaks libsdl-ruby (<< 2.1.1.1-2~)
* li
1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> /usr/bin/c++ -DYOSHI_FIFO_DIR=\"/dev/shm\" -
Package: biomaj-watcher
Version: 1.2.0-6
Followup-For: Bug #670495
Hi,
the problem is still present in 1.2.0-6:
Setting up biomaj-watcher (1.2.0-6) ...
Updating Context.xml...
Configuration complete
ln: failed to create symbolic link
`/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/
Package: python-quantum
Version: 2012.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'unstable' fails
because it tries to overwrit
Package: fonts-bpg-georgian
Version: 0.5a-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'unstable' fails
because it tries to overwr
On 08.05.2012 22:21, Neil Williams wrote:
> tag 672085 + help quit
>
> On Tue, 08 May 2012 18:57:52 + Matthias Klose wrote:
>
>> user debian-...@lists.debian.org usertags 672085 + ftbfs-gcc-4.7 thanks
>>
>> The build failure is exposed by building with gcc-4.7/g++-4.7, which is
>> now the d
Processing commands for cont...@bugs.debian.org:
> affects 671716 + texlive-full
Bug #671716 [texlive-latex-base] texlive-latex-base: fails to upgrade from
squeeze - trying to overwrite /usr/share/man/man1/mptopdf.1.gz
Added indication that 671716 affects texlive-full
> thanks
Stopping processing
Roger Leigh (08/05/2012):
> On Wed, May 02, 2012 at 01:15:42AM +0200, Cyril Brulebois wrote:
> > Preparing to replace initscripts 2.88dsf-22 (using
> > .../initscripts_2.88dsf-22.1_amd64.deb) ...
> > Unpacking replacement initscripts ...
> > Processing triggers for man-db ...
> > Setting up inits
Hi,
looks like this one:
https://issues.apache.org/jira/browse/QPID-3652
which - according to the bug itself affects 0.12. Comparing the diff
from
https://reviews.apache.org/r/2988/diff/#index_header
makes me wonder, because the changes are not present in 0.14, but in
the upcoming 0.16 rel
rious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[4]: Entering directory `/«PKGBUILDDIR»/builddir'
> [ 2
heezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> gcc -shared .libs/SDL_sound.o .libs/alt_audio_convert.o
> .libs/audio_conv
Your message dated Tue, 08 May 2012 22:04:42 +
with message-id
and subject line Bug#669949: fixed in sysvinit 2.88dsf-24
has caused the Debian Bug report #669949,
regarding xserver-xorg-core: input devices no longer detected
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 09 May 2012 00:02:48 +0200
with message-id <4fa99808.7000...@debian.org>
and subject line Re: shotwell: Segfault once a photo is selected
has caused the Debian Bug report #670644,
regarding shotwell: Segfault once a photo is selected
to be marked as done.
This means that yo
Your message dated Tue, 08 May 2012 22:04:42 +
with message-id
and subject line Bug#670085: fixed in sysvinit 2.88dsf-24
has caused the Debian Bug report #670085,
regarding insserv: update-rc.d is a dangling symlink
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Tue, 08 May 2012 22:04:42 +
with message-id
and subject line Bug#669949: fixed in sysvinit 2.88dsf-24
has caused the Debian Bug report #669949,
regarding sysvinit: Break X11: no more mouse and keyboard
to be marked as done.
This means that you claim that the problem has bee
Your message dated Tue, 08 May 2012 22:04:42 +
with message-id
and subject line Bug#668307: fixed in sysvinit 2.88dsf-24
has caused the Debian Bug report #668307,
regarding initscripts: recreates /etc/motd
to be marked as done.
This means that you claim that the problem has been dealt with.
I
mart...@brumit.nl said:
>Added patch makes it build again.
Thanks for creating this patch. It has been incorporated into
qsstv-7.1.7-2 (which was uploaded a few minutes ago).
--
Steve Kostecke // K0STK
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "u
rious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> g++ -c -m64 -pipe -O2 -D_REENTRANT -Wall -W -DQT_NO_DEBUG
On Wed, May 02, 2012 at 01:15:42AM +0200, Cyril Brulebois wrote:
> Preparing to replace initscripts 2.88dsf-22 (using
> .../initscripts_2.88dsf-22.1_amd64.deb) ...
> Unpacking replacement initscripts ...
> Processing triggers for man-db ...
> Setting up initscripts (2.88dsf-22.1) ...
> update-rc.d
On Tue, 2012-05-08 at 22:38 +0100, Adam D. Barratt wrote:
> On Mon, 2012-05-07 at 10:02 +0200, Thijs Kinkhorst wrote:
> > PHP upstream has now announced new releases for tomorrow, which also fix
> > another security issue:
> > http://www.php.net/archive/2012.php#id2012-05-06-1
> >
> > It would be
t; User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20120508 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to bui
On Mon, 2012-05-07 at 10:02 +0200, Thijs Kinkhorst wrote:
> PHP upstream has now announced new releases for tomorrow, which also fix
> another security issue:
> http://www.php.net/archive/2012.php#id2012-05-06-1
>
> It would be great if we could get that into unstable swiftly and then
> start the
Your message dated Tue, 08 May 2012 21:37:32 +
with message-id
and subject line Bug#667429: fixed in zsnes 1.510+bz2-3
has caused the Debian Bug report #667429,
regarding zsnes: ftbfs with GCC-4.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: squid
Severity: serious
I remember some discussion before the Squeeze release about both
squid and squid3 being included in a stable release and thus
needing double security updates.
>From what I remember squid3 still lacked some features at that
time and having both in Squeeze was meant
Your message dated Tue, 08 May 2012 21:27:28 +
with message-id
and subject line Bug#672027: fixed in gnome-commander 1.2.8.15-2.1
has caused the Debian Bug report #672027,
regarding gnome-commander: FTBFS with gcc 4.7
to be marked as done.
This means that you claim that the problem has been d
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-commander
Version: 1.2.8.15-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all p
...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> dh_testdir
> # Add here commands to compile the package.
>
1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> g++ -DPACKAGE_NAME=\"dynare\" -DP
: blackbox
Version: 0.70.1-8
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering direct
...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> /usr/bin/install -d /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux
Processing commands for cont...@bugs.debian.org:
> forcemerge 671941 672027
Bug #671941 [src:gnome-commander] gnome-commander: FTBFS with gcc 4.7
Bug #672027 [src:gnome-commander] gnome-commander: FTBFS: ./../dict.h:58:102:
error: 'make_pair' was not declared in this scope, and no declarations we
Hi,
Am 08.05.2012 21:55, schrieb Joey Hess:
> Package: policykit-1
> Version: 0.104-2
> Severity: serious
Could you elaborate on the severity?
> Tags: d-i
>
> In d-i, it is very easy to set up a system without entering a root
> password. d-i sets up sudo, and configures gksu to use it
> (by cha
Processing commands for cont...@bugs.debian.org:
> tags 672079 + patch
Bug #672079 [src:qsstv] qsstv: FTBFS: wavio.cpp:285:33: error: 'lseek' was not
declared in this scope
Added tag(s) patch.
> tags 672079 + pending
Bug #672079 [src:qsstv] qsstv: FTBFS: wavio.cpp:285:33: error: 'lseek' was not
tags 672079 + patch
tags 672079 + pending
thanks
Forgot to mention the bug in the changelog
Regards.
martijn van brummelen
diff -Nru qsstv-7.1.7/debian/changelog qsstv-7.1.7/debian/changelog
--- qsstv-7.1.7/debian/changelog 2012-04-21 05:43:08.0 +0200
+++ qsstv-7.1.7/debian/changelog 201
Processing commands for cont...@bugs.debian.org:
> tag 672085 + help
Bug #672085 [src:qof] qof: FTBFS: md5.c:119:2: error: dereferencing type-punned
pointer will break strict-aliasing rules [-Werror=strict-aliasing]
Added tag(s) help.
> quit
Stopping processing here.
Please contact me if you nee
tag 672085 + help
quit
On Tue, 08 May 2012 18:57:52 +
Matthias Klose wrote:
> user debian-...@lists.debian.org
> usertags 672085 + ftbfs-gcc-4.7
> thanks
>
> The build failure is exposed by building with gcc-4.7/g++-4.7,
> which is now the default gcc/g++ on x86 architectures.
>
> Some hin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
At a first glance it seems that an include is missing.
This issue is mentioned in
http://gcc.gnu.org/gcc-4.7/porting_to.html
(thanks for the link)
My sid vm installation is very dusty and needs an updated first
but I'll try to fix this soon.
- --
Processing commands for cont...@bugs.debian.org:
> severity 671944 minor
Bug #671944 [libnepomuk4] libnepomuk4: Virtuoso entirely missing from testing,
making Nepomuk unusable
Severity set to 'minor' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
67
severity 671944 minor
thanks
Hi,
Alle martedì 8 maggio 2012, Ralf Jung ha scritto:
> Package: libnepomuk4
> Version: 4:4.7.4-4
> Severity: grave
> Justification: renders package unusable
>
> Virtuoso is missing from testing, and without it, Nepomuk does not
> work (also see [1]). As I had to fin
Package: policykit-1
Version: 0.104-2
Severity: serious
Tags: d-i
In d-i, it is very easy to set up a system without entering a root
password. d-i sets up sudo, and configures gksu to use it
(by changing an alternative).
On such a system, I was prompted by policykit for the (nonexistant) root
pas
y: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> g++ -DDATA_PATH=\"/usr/share/xye/\" -I. -I. -g
Your message dated Tue, 08 May 2012 19:50:12 +
with message-id
and subject line Bug#671866: fixed in gmp 2:5.0.5+dfsg-1.1
has caused the Debian Bug report #671866,
regarding gmp: causes gcc ICEs on amd64 and kfreebsd-amd64
to be marked as done.
This means that you claim that the problem has b
On Tue, May 8, 2012 at 19:43:41 +0200, Laurent Fousse wrote:
> Hi,
>
> * Julien Cristau [Tue, May 08, 2012 at 07:19:15PM +0200]:
> > On Mon, May 7, 2012 at 22:09:55 -0500, Steve M. Robbins wrote:
> >
> > > Interesting. It could well be the configure option. For the past 6
> > > years, Debian
Your message dated Tue, 08 May 2012 19:21:13 +
with message-id
and subject line Bug#667385: fixed in sunpinyin 2.0.3+git20120404-1
has caused the Debian Bug report #667385,
regarding sunpinyin: ftbfs with GCC-4.7
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 08 May 2012 19:04:36 +
with message-id
and subject line Bug#665040: fixed in smarty-gettext 1.0b1-5
has caused the Debian Bug report #665040,
regarding smarty-gettext: Fails to install, nmet dependencies
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 08 May 2012 19:04:36 +
with message-id
and subject line Bug#665040: fixed in smarty-gettext 1.0b1-5
has caused the Debian Bug report #665040,
regarding slbackup-php: FTBFS: build-dependency not installable: smarty-gettext
to be marked as done.
This means that you claim
Your message dated Tue, 08 May 2012 19:04:36 +
with message-id
and subject line Bug#665033: fixed in smarty-gettext 1.0b1-5
has caused the Debian Bug report #665033,
regarding smarty-gettext: Fails to install, nmet dependencies
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 08 May 2012 19:04:36 +
with message-id
and subject line Bug#665033: fixed in smarty-gettext 1.0b1-5
has caused the Debian Bug report #665033,
regarding slbackup-php: FTBFS: build-dependency not installable: smarty-gettext
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> notfixed 656115 5.8.0-11
Bug #656115 {Done: Mathieu Malaterre }
[libvtk5-dev] libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without
libvtk5-qt4-dev being installed
Bug #584300 {Done: Mathieu Malaterre }
[libvtk5-dev] libvtk5-dev: Remove inform
Fixed in sludge 2.2-1 [1,2]. I'm waiting for a sponsor to upload it. [3]
Best regards,
Tobias
[1] http://mentors.debian.net/package/sludge
[2] http://mentors.debian.net/debian/pool/main/s/sludge/sludge_2.2-1.dsc
[3] http://wiki.debian.org/Games/Sponsors/Queue
--
To UNSUBSCRIBE, email to debia
notfixed 656115 5.8.0-11
found 656115 5.8.0-11
thanks
My bad. I did not realize VTKConfigQt.cmake is still shipped within
libvtk5-dev and not libvtk5-qt4-dev
very sorry about that.
On Tue, May 8, 2012 at 7:57 PM, Jochen Sprickerhof
wrote:
> found 656115 5.8.0-11
> thanks
>
> Hi,
>
> I'm sorry, b
Your message dated Tue, 08 May 2012 19:02:21 +
with message-id
and subject line Bug#667158: fixed in esys-particle 2.1-4
has caused the Debian Bug report #667158,
regarding esys-particle: ftbfs with GCC-4.7
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 8 May 2012 21:00:54 +0200
with message-id
and subject line Re: Bug#656115: closed by Mathieu Malaterre
(Bug#656115: fixed in vtk 5.8.0-10)
has caused the Debian Bug report #656115,
regarding libvtk5-dev: Remove information about wrapped languages from
VTKConfig.cmake
t
Your message dated Tue, 8 May 2012 21:00:54 +0200
with message-id
and subject line Re: Bug#656115: closed by Mathieu Malaterre
(Bug#656115: fixed in vtk 5.8.0-10)
has caused the Debian Bug report #656115,
regarding libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without
libvtk5-qt4-dev being in
Processing commands for cont...@bugs.debian.org:
> fixed 656115 5.8.0-11
Bug #656115 [libvtk5-dev] libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK
without libvtk5-qt4-dev being installed
Bug #584300 [libvtk5-dev] libvtk5-dev: Remove information about wrapped
languages from VTKConfig.cmake
Marked
user debian-...@lists.debian.org
usertags 672097 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672100 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672098 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672099 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672095 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672094 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672093 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672091 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672090 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672089 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672088 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672087 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672086 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
user debian-...@lists.debian.org
usertags 672085 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
1 - 100 of 456 matches
Mail list logo
