gmane.linux.debian.devel.bugs.rc

Processed: Re: Bug#667886: textedit.app: FTBFS with GCC-4.7

Debian Bug Tracking System — 2012-05-23T11:24:59

Processing commands for control< at >bugs.debian.org:

Bug #667886 [src:textedit.app] textedit.app: FTBFS with GCC-4.7
Added tag(s) patch.
Stopping processing here.

Please contact me if you need assistance.

Bug#667886: textedit.app: FTBFS with GCC-4.7

Yavor Doganov — 2012-05-23T11:22:50

tags 667886 + patch
thanks

Patch attached.

Bug#673740: marked as done (ruby-actionmailer-3.2 andruby-actionmailer-2.3: error when trying to install together)

Debian Bug Tracking System — 2012-05-23T11:21:03

Your message dated Wed, 23 May 2012 11:18:57 +0000
with message-id <E1SX9aj-0006JE-08< at >franck.debian.org>
and subject line Bug#673740: fixed in ruby-actionmailer-3.2 3.2.3-2
has caused the Debian Bug report #673740,
regarding ruby-actionmailer-3.2 and ruby-actionmailer-2.3: error when trying to install together
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 owner< at >bugs.debian.org
immediately.)

Processed: closing 671967, notfound 671967 inruby-activeresource-3.2/3.2.3-1

Debian Bug Tracking System — 2012-05-23T11:18:18

Processing commands for control< at >bugs.debian.org:

Bug #671967 [src:ruby-activeresource-3.2] ruby-activeresource-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.3.), ruby-activemodel-3.2 (>= 3.2.3), ruby-activemodel-3.2 (< 3.2.3.)
Marked Bug as done
Bug #671967 {Done: OndÅej SurÃ½ <ondrej< at >debian.org>} [src:ruby-activeresource-3.2] ruby-activeresource-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.3.), ruby-activemodel-3.2 (>= 3.2.3), ruby-activemodel-3.2 (< 3.2.3.)
No longer marked as found in versions ruby-activeresource-3.2/3.2.3-1.
Stopping processing here.

Please contact me if you need assistance.

Bug#671966: marked as done (ruby-activerecord-3.2: FTBFS:unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3),ruby-activesupport-3.2 (< 3.2.3.), ruby-activemodel-3.2 (>= 3.2.3),ruby-activemodel-3.2 (< 3.2.3.))

Debian Bug Tracking System — 2012-05-23T11:13:21

Your message dated Wed, 23 May 2012 13:10:53 +0200
with message-id <CALjhHG_rNpn3r9G+xobNQC80CzcJ4sFsoxxawucF_xAf8wwizQ< at >mail.gmail.com>
and subject line Transient failure, already fixed
has caused the Debian Bug report #671966,
regarding ruby-activerecord-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.3.), ruby-activemodel-3.2 (>= 3.2.3), ruby-activemodel-3.2 (< 3.2.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 owner< at >bugs.debian.org
immediately.)

Processed: notfound 671966 in ruby-activerecord-3.2/3.2.3-2

Debian Bug Tracking System — 2012-05-23T11:13:14

Processing commands for control< at >bugs.debian.org:

Bug #671966 [src:ruby-activerecord-3.2] ruby-activerecord-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.3.), ruby-activemodel-3.2 (>= 3.2.3), ruby-activemodel-3.2 (< 3.2.3.)
No longer marked as found in versions ruby-activerecord-3.2/3.2.3-2.
Stopping processing here.

Please contact me if you need assistance.

Processed: notfound 671986 in ruby-actionpack-3.2/3.2.3-1

Debian Bug Tracking System — 2012-05-23T11:07:40

Processing commands for control< at >bugs.debian.org:

Bug #671986 [src:ruby-actionpack-3.2] ruby-actionpack-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.3.), ruby-activerecord-3.2 (>= 3.2.3), ruby-activerecord-3.2 (< 3.2.3.)
No longer marked as found in versions ruby-actionpack-3.2/3.2.3-1.
Stopping processing here.

Please contact me if you need assistance.

Bug#671959: marked as done (ruby-activemodel-3.2: FTBFS:unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3),ruby-activesupport-3.2 (< 3.2.3.))

Debian Bug Tracking System — 2012-05-23T11:07:29

Your message dated Wed, 23 May 2012 13:05:29 +0200
with message-id <CALjhHG9v2PGNA3Jg1tC4-acv_FC_ZAG6b3As5R-Kxo0Qwp5+LQ< at >mail.gmail.com>
and subject line Transient error, ruby-activesupport-3.2 is already in archive
has caused the Debian Bug report #671959,
regarding ruby-activemodel-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.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 owner< at >bugs.debian.org
immediately.)

Processed: notfound 671959 in ruby-activemodel-3.2/3.2.3-1

Debian Bug Tracking System — 2012-05-23T11:07:07

Processing commands for control< at >bugs.debian.org:

Bug #671959 [src:ruby-activemodel-3.2] ruby-activemodel-3.2: FTBFS: unsatisfiable build-dependencies: ruby-activesupport-3.2 (>= 3.2.3), ruby-activesupport-3.2 (< 3.2.3.)
No longer marked as found in versions ruby-activemodel-3.2/3.2.3-1.
Stopping processing here.

Please contact me if you need assistance.

Bug#673736: marked as done (libdivecomputer0 and smartpm-core: errorwhen trying to install together)

Debian Bug Tracking System — 2012-05-23T11:06:28

Your message dated Wed, 23 May 2012 11:03:31 +0000
with message-id <E1SX9Ln-0005gm-SM< at >franck.debian.org>
and subject line Bug#673736: fixed in libdivecomputer 0.1.0-2
has caused the Debian Bug report #673736,
regarding libdivecomputer0 and smartpm-core: error when trying to install together
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 owner< at >bugs.debian.org
immediately.)

Bug#673568: marked as done (gcc-avr: FTBFS on sid/i386)

Debian Bug Tracking System — 2012-05-23T11:06:04

Your message dated Wed, 23 May 2012 11:02:44 +0000
with message-id <E1SX9L2-0005dd-Iu< at >franck.debian.org>
and subject line Bug#673568: fixed in gcc-avr 1:4.7.0-2
has caused the Debian Bug report #673568,
regarding gcc-avr: FTBFS on sid/i386
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 owner< at >bugs.debian.org
immediately.)

Processed: severity of 668891 is grave

Debian Bug Tracking System — 2012-05-23T10:54:49

Processing commands for control< at >bugs.debian.org:

Bug #668891 [libc6] Static TLS (thread local storage) generates SIGSEGV in libc6 (GNU C-Library)
Severity set to 'grave' from 'important'
Stopping processing here.

Please contact me if you need assistance.

Bug#667874: gworkspace: FTBFS with GCC-4.7

Yavor Doganov — 2012-05-23T10:50:06

tags 667874 + patch
thanks

Patch attached.

Processed: Re: Bug#667874: gworkspace: FTBFS with GCC-4.7

Debian Bug Tracking System — 2012-05-23T10:54:25

Processing commands for control< at >bugs.debian.org:

Bug #667874 [src:gworkspace] gworkspace: FTBFS with GCC-4.7
Added tag(s) patch.
Stopping processing here.

Please contact me if you need assistance.

Processed: zipper.app: diff for NMU (1.3-2.1)

Debian Bug Tracking System — 2012-05-23T10:39:11

Processing commands for control< at >bugs.debian.org:

Bug #667876 [src:zipper.app] zipper.app: FTBFS with GCC-4.7
Added tag(s) pending and patch.
Stopping processing here.

Please contact me if you need assistance.

Bug#667876: zipper.app: diff for NMU (1.3-2.1)

Matej Vela — 2012-05-23T10:35:07

tag 667876 patch pending
thanks

Hi,

I'm uploading an NMU for zipper.app (1.3-2.1) to DELAYED/2-day.
Please let me know if you'd like me to cancel it or delay further.

Cheers,

Matej
--- zipper.app-1.3~/debian/changelog
+++ zipper.app-1.3/debian/changelog
< at >< at > -1,3 +1,11 < at >< at >
+zipper.app (1.3-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * gcc-4.7: Fix build failure with GCC 4.7.  Closes: #667876.
+    - ZipperDocument.m: sel_eq replaced by sel_isEqual.
+
+ -- Matej Vela <vela< at >debian.org>  Wed, 23 May 2012 11:02:09 +0100
+
 zipper.app (1.3-2) unstable; urgency=low
 
   * Upload to unstable.
--- zipper.app-1.3~/debian/patches/gcc-4.7.patch
+++ zipper.app-1.3/debian/patches/gcc-4.7.patch
< at >< at > -0,0 +1,17 < at >< at >
+Description: Fix build failure with GCC 4.7
+ - ZipperDocument.m: sel_eq replaced by sel_isEqual.
+Bug-Debian: http://bugs.debian.org/667876
+Author: Matej Vela <vela< at >debian.org>
+Last-Update: 2012-05-23
+
+--- zipper.app-1.3~/ZipperDocument.m
++++ zipper.app-1.3/ZipperDocument.m
+< at >< at > -210,7 +210,7

Bug#674113: marked as done (netsurf-gtk: problem upgrading as onefile in both netsurf-gtk 2.9-1 and earlier netsurf-common)

Debian Bug Tracking System — 2012-05-23T10:21:38

Your message dated Wed, 23 May 2012 10:18:26 +0000
with message-id <E1SX8eA-0000Pt-NW< at >franck.debian.org>
and subject line Bug#674113: fixed in netsurf 2.9-2
has caused the Debian Bug report #674113,
regarding netsurf-gtk: problem upgrading as one file in both netsurf-gtk 2.9-1 and earlier netsurf-common
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 owner< at >bugs.debian.org
immediately.)

Bug#674014: python-dolfin: Doesn't find python-scientific

Torquil Macdonald Sørensen — 2012-05-23T09:29:48

Package: python-dolfin
Followup-For: Bug #674014

Hi!

Doing import Scientific.Functions.Derivatives does indeed not work, and produces:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/Scientific/Functions/Derivatives.py", line 103, in <module>
    from Scientific import N; Numeric = N
  File "/usr/lib/python2.7/dist-packages/Scientific/N.py", line 1, in <module>
    import Scientific_numerics_package_id
ImportError: No module named Scientific_numerics_package_id

However, as you claimed, installing python-netcdf fixes everything, and after that
I can run the Fenics python demos successfully. So thanks!

Best regards,
Torquil SÃ¸rensen

Processed: merge 646638 671814

Debian Bug Tracking System — 2012-05-23T09:27:30

Processing commands for control< at >bugs.debian.org:

Bug #646638 [cl-clg] cl-clg: Trying to run example code fails with 'no package with name "GTK"'
Bug #671814 [cl-clg] cl-clg: Compilation error on sbcl
Merged 646638 671814
End of message, stopping processing here.

Please contact me if you need assistance.

Bug#674122: otrs2: fails to upgrade from squeeze: Can't create table'otrs2.#sql-1712_71

Andreas Beckmann — 2012-05-23T09:10:51

s/wheezy/sid/ :-)  Forgot to fix the template ...




Just retested and the error happened again.

Unfortunately the piuparts I use is a heavily hacked up development
version that is not available publicly and it may take some time until
database server support moves upstream ...


Andreas

Processed: found 663036 in 16.14-1, found 672374 in 2.3.1-1,severity of 672374 is serious ..., tagging 646540 ...

Debian Bug Tracking System — 2012-05-23T09:06:18

Processing commands for control< at >bugs.debian.org:

Bug #663036 [gnumed-server] gnumed-server: unowned directories after purge: /var/lib/gnumed/server/backups /var/log/gnumed/server
Marked as found in versions gnumed-server/16.14-1.
Bug #672374 [piwigo] piwigo: uninstalable, should depend on smarty3
Marked as found in versions piwigo/2.3.1-1.
Bug #672374 [piwigo] piwigo: uninstalable, should depend on smarty3
Severity set to 'serious' from 'important'
Setting user to debian-qa< at >lists.debian.org (was debian< at >abeckmann.de).
Bug#672374: piwigo: uninstalable, should depend on smarty3
There were no usertags set.
Usertags are now: piuparts.
Bug#646540: phpgacl: please test your package with smarty3
There were no usertags set.
Usertags are now: piuparts.
Bug #646540 [phpgacl] phpgacl: please test your package with smarty3
Severity set to 'serious' from 'minor'
Bug #646540 [phpgacl] phpgacl: please test your package with smarty3
Marked as found in versions phpgacl/3.3.7-7.1.
Bug #646540 [phpgacl] phpgacl: please test yo