Bug#650251: Not building on !linux architectures

2011-11-28 Thread Laurent Bigonville
Source: pcsc-lite
Version: 1.8.1-1
Severity: serious

Hi,

pcsc-lite is not building on !linux architectures due to systemd
support.

1.8.1-1 was failing due to:

dh_install -a
cp: cannot stat `debian/tmp/lib/systemd/system/pcscd.socket': No such file or 
directory
dh_install: cp -a debian/tmp/lib/systemd/system/pcscd.socket 
debian/pcscd//lib/systemd/system/ returned exit code 1
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

And 1.8.1-2 is now build-depending against systemd which is only
available on linux-any architectures.

Cheers

Laurent Bigonville



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



Bug#649591: breaks gnome-do as well

2011-11-28 Thread Romain Francoise
For the record this bug also prevents gnome-do from starting when procps
3.3.0-1 is installed as the wrapper script in /usr/bin uses pgrep -u.

-- 
Romain Francoise rfranco...@debian.org
http://people.debian.org/~rfrancoise/



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



Bug#650252: kazehakase: FTBFS because it needs libxul-embedding-unstable

2011-11-28 Thread Laurent Bonnaud
Package: kazehakase
Version: 0.5.8-4
Severity: serious

Hi,

here is the problem:

$ fakeroot apt-get -b source kazehakase
[...]
checking for MOZILLA_COMPONENT... no
configure: error: Package requirements (libxul-embedding-unstable = 1.9) were 
not met:

No package 'libxul-embedding-unstable' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables MOZILLA_COMPONENT_CFLAGS
and MOZILLA_COMPONENT_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Build command 'cd kazehakase-0.5.8  dpkg-buildpackage -b -uc' failed.
E: Child process failed


Looking for package libxul-embedding instead of
libxul-embedding-unstable would work:

$ pkg-config --list-all | grep libxul
libxul-embeddinglibxul-embedding - Static library for 
version-independent embedding of the Mozilla runtime

-- 
Laurent Bonnaud.
http://www.gipsa-lab.inpg.fr/page_pro.php?vid=96





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



Processed: tagging 556322

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # reverse erroneous removal of patch tag by mpalmer
 tags 556322 + patch
Bug #556322 [src:rlplot] FTBFS with binutils-gold
Added tag(s) patch.
 thanks
Stopping processing here.

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


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



Bug#618048: rlplot: FTBFS: QT_Spec.cpp:1190:16: error: call of overloaded 'QString(int)' is ambiguous

2011-11-28 Thread Olly Betts
On Sun, Mar 13, 2011 at 05:54:56PM +0100, Lucas Nussbaum wrote:
 Source: rlplot
 Version: 1.4-1
 Severity: serious
 Tags: wheezy sid
 User: debian...@lists.debian.org
 Usertags: qa-ftbfs-20110313 qa-ftbfs
 Justification: FTBFS on amd64
 
 Hi,
 
 During a rebuild of all packages in sid, your package failed to build on
 amd64.

This release-critical bug has seen no maintainer response in over 8 months.
The last rlplot upload was over 4 years ago (in 2007) and the last response
to a bug report by the maintainer seems to also have be in 2007.  Meanwhile
there's been a newer upstream release, which has been packaged for Ubuntu but
is not available in Debian.

James: Are you still interested in maintaining this package?  If not, it
would be better to orphan it, so that somebody else interested in it can
take over maintenance.

Cheers,
Olly



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



Bug#650068: [Pkg-cups-devel] Bug#650068: cups-pdf: PDF created are all void without error notice

2011-11-28 Thread Martin-Éric Racine
2011/11/26 Eric Lavarde bugs.debian.nos...@lavar.de:
 Package: cups-pdf
 Version: 2.6.1-3
 Severity: grave
 Justification: renders package unusable

 Hello,

 after having migrated from squeeze to wheezy, cups-pdf does only produce
 minimal PDF files without any content. I tried different apps
 (Iceweasel, LibreOffice) without apparent difference in (bad) behavior.
 The PDFs created do only differentiate in terms of IDs and dates/times
 else they are completely the same; I'll attach an example.
 I have also set the report level to debug and will also attach the
 logfile but I don't see anything noticeable.

 I'm at loss what to do but currently cups-pdf is not usable at all for
 me, hence the high severity.

I'm pretty sure that we had resolved this issue when we introduced
automatic updating of PPD files. However, Debian has taken the habit
of heavily modifying CUPS, which often breaks CUPS-PDF. Let's see if
other CUPS maintainers might know the cause.

Martin-Éric



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



Processed: severity of 650068 is important

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 650068 important
Bug #650068 [cups-pdf] cups-pdf: PDF created are all void without error notice
Severity set to 'important' from 'grave'

 thanks
Stopping processing here.

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


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



Bug#650265: dma: cannot deliver mail to smtp server

2011-11-28 Thread Miquel van Smoorenburg
Package: dma
Version: 0.0.2010.06.17-6
Severity: grave

DMA often fails to deliver mail to my smtp server, keeping messages
in the queue until they expire. They then fail to bounce as well.

That's why I set the severity to grave - it causes dataloss,
at least for me.

This is because it sometimes doesn't read the entire line
in the SMTP conversation up to \r\n. I suspect that happends when
the remote system doesn't send the entire line in one TCP packet,
which is probably unusual (it might be an anti-spam measure),
but valid. Example from strace:

10035 connect(6, {sa_family=AF_INET, sin_port=htons(25), 
sin_addr=inet_addr(194.109.6.51)}, 16) = 0
10035 read(6,  220 smtp-vbr11.xs4all.nl ESMTP Sendmail 8.13.8, 2048) = 46
10035 write(6, EHLO newsfeed5.news.xs4all.nl\r\n, 31) = 31
10035 read(6,  /8.13.8; Mon, 28 Nov 2011 11:34:52 +0100 (CET)\r\n, 2048) = 48
10035 sendto(5, 21Nov 28 11:34:52 dma[1580fa.612b00]: remote delivery 
deferred: smtp.xs4all.nl [194.109.6.51] failed after EHLO: invalid syntax in 
reply from server, 150, MSG_NOSIGNAL, NULL, 0) = 150

As you can see, dma reads the first 46 bytes of the SMTP welcome
line, then sends an EHLO, then wants to read the reply to the EHLO
but gets the rest of the SMTP welcome line, and errors out.

Mike.



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



Bug#619636: Info received (Clutter problem?)

2011-11-28 Thread Luca Capello
user 619636 l...@pca.it
usertags 619636 + pca-communication
thanks

Hi there!

Cc:ing all the people involved with this bug, sorry for the spam.  Also
Cc:ing the Debian X Strike Force for comments about the Mesa part.

On Sat, 16 Apr 2011 17:38:51 +0200, Alex Stewart wrote:
 See also bug 620908. IMO, they should not be merged, because 619636
 can be solved in two ways: depending on a version of libclutter-1.0-0
 with a fix for bug 620908 or, AFAICT, building empathy without
 libchamplain support.

I can confirm that with the following diff empathy works without no
problem on a last-week up-to-date sid on libvirt/KVM with no HW
acceleration:

--8---cut here---start-8---
diff -Nru empathy-3.2.2/debian/control empathy-3.2.2/debian/control
--- empathy-3.2.2/debian/control2011-11-19 18:24:56.0 +0100
+++ empathy-3.2.2/debian/control2011-11-21 00:36:24.0 +0100
@@ -13,7 +13,6 @@
debhelper (= 8),
rarian-compat,
librarian-dev,
-   libchamplain-gtk-0.12-dev,
libglib2.0-dev (= 2.28),
libgtk-3-dev (= 3.0.2),
libtelepathy-glib-dev (= 0.16.0),
diff -Nru empathy-3.2.2/debian/rules empathy-3.2.2/debian/rules
--- empathy-3.2.2/debian/rules  2011-11-19 18:24:56.0 +0100
+++ empathy-3.2.2/debian/rules  2011-11-21 00:51:04.0 +0100
@@ -13,7 +13,7 @@
 
 DEB_CONFIGURE_EXTRA_FLAGS := --enable-spell \
  --enable-webkit \
- --enable-map=yes \
+ --enable-map=no \
  --enable-geocode=yes \
  --with-cheese \
  --with-eds \
--8---cut here---end---8---

On Wed, 16 Nov 2011 11:07:45 +0100, Laurent Bigonville wrote:
 According to upstream this is a known issue and due to the software
 rasterizer in mesa. The only way here is, for now, to use proper
 hardware acceleration.

Until this week-end Mesa updates (see below), it seemed that there was
another way: installing libgl1-mesa-swx11 solved the problem for two
up-to-date sid, a schroot and the libvirt/KVM above.  However, in the
latter case GNOME 3 always crashes and I can not login (this should be
confirmed on a real machine, i.e. not on a VM).  So the situation was
the following:

1) libgl1-mesa-glx alone
   = empathy segfault

2) libgl1-mesa-glx *AND* libgl1-mesa-dri *AND* HW acceleration
   = empathy works

3) libgl1-mesa-swx11 (with or without libgl1-mesa-dri)
   = empathy works, but GNOME 3 crashes 

libclutter-1.0 already Depends: on 'libgl1-mesa-glx | libgl1' and this
includes also libgl1-mesa-swx11 (which Provides: libgl1).  What it could
be needed is a Depends: on 'libgl1-mesa-dri | libgl1-mesa-swx11':

--8---cut here---start-8---
diff -Nru clutter-1.0-1.8.2/debian/control.in 
clutter-1.0-1.8.2/debian/control.in
--- clutter-1.0-1.8.2/debian/control.in 2011-11-14 13:18:06.0 +0100
+++ clutter-1.0-1.8.2/debian/control.in 2011-11-21 15:16:07.0 +0100
@@ -36,6 +36,7 @@
 Architecture: any
 Depends: ${shlibs:Depends},
  ${misc:Depends},
+ libgl1-mesa-dri | libgl1-mesa-swx11
 Recommends: libclutter-1.0-common
 Breaks: python-clutter ( 1.3.2)
 Pre-Depends: ${misc:Pre-Depends}
--8---cut here---end---8---

 The long term solution is to switch to llvmpipe in debian to make it
 work for people that cannot get hardware acceleration. I think that the
 next release of mesa has switch to this.

It seems that upstream Mesa already solved this in a different way:

  https://bugs.archlinux.org/task/26686
  https://bugzilla.redhat.com/show_bug.cgi?id=747276#c18

The upstream fix went into the new Mesa package during the week-end (I
was building the old 7.11-6 plus this patch, but given that the build
process needed more than 5 GB of disk space I could not get it earlier):

  
http://anonscm.debian.org/gitweb/?p=pkg-xorg/lib/mesa.git;a=commitdiff;h=b2fbf8225bfed2d6f5339ba0a97ddbc5e6cc491a
  http://packages.qa.debian.org/m/mesa/news/2028T002111Z.html

Nevertheless, empathy still segfaults witwh libgl1-mesa-glx_7.11.1-1
alone (i.e. without libgl1-mesa-dri) on both sid above, the schroot and
the libvirt/KVM.  However, the error on the latter is a bit more
explicative:
=
luca.capello@gismo-sid:~$ empathy

(empathy:2824): Clutter-CRITICAL **: Unable to initialize Clutter: \
 The OpenGL version could not be determined
Segmentation fault
luca.capello@gismo-sid:~$ empathy
=

Installing libgl1-mesa-dri solves the problem, which is anyway a
progress, given that before it did not work at all on libvirt/KVM with
no HW acceleration (see point 2 above).

Thx, bye,
Gismo / Luca


pgplLeRisoVwF.pgp
Description: PGP signature


Bug#618048: rlplot: FTBFS: QT_Spec.cpp:1190:16: error: call of overloaded 'QString(int)' is ambiguous

2011-11-28 Thread Ricardo Mones
  Hi James,

  Thanks Olly for noticing this and sorry for the late response,

On Mon, Nov 28, 2011 at 11:05:24PM +1300, Olly Betts wrote:
 On Sun, Mar 13, 2011 at 05:54:56PM +0100, Lucas Nussbaum wrote:
  Source: rlplot
  Version: 1.4-1
  Severity: serious
  Tags: wheezy sid
  User: debian...@lists.debian.org
  Usertags: qa-ftbfs-20110313 qa-ftbfs
  Justification: FTBFS on amd64
  
  Hi,
  
  During a rebuild of all packages in sid, your package failed to build on
  amd64.
 
 This release-critical bug has seen no maintainer response in over 8 months.
 The last rlplot upload was over 4 years ago (in 2007) and the last response
 to a bug report by the maintainer seems to also have be in 2007.  Meanwhile
 there's been a newer upstream release, which has been packaged for Ubuntu but
 is not available in Debian.
 
 James: Are you still interested in maintaining this package?  If not, it
 would be better to orphan it, so that somebody else interested in it can
 take over maintenance.

  In addition to Olly's question, and as nothing has been received to his
previous query, if no response is received I will orphan this package next
weekend, so please let us know your intentions.

  regards,
-- 
  Ricardo Mones, on behalf of Debian/QA MIA Team 
  ~
  Absence of evidence is not evidence of absence.  Carl Sagan



signature.asc
Description: Digital signature


Bug#610933: [Pkg-vsquare-devel] Bug#610933: libvdeplug3 declares a conflict with libvdeplug2

2011-11-28 Thread Ludovico Gardenghi
Hello,

On Mon, Jun 20, 2011 at 23:43:03 -0500, Jonathan Nieder wrote:

 Ping?  I've had vde2 on hold because of this bug for several months
 now.  IMHO if the package in experimental is not being maintained, it
 should be removed --- it will still be available from
 snapshot.debian.org.

Thanks for the report and sorry for the delay.

Indeed the conflict will be needed with the next release, as we're
much probably going to move libvdeplug.so from the -dev package to the
shared library one (since several virtualization tools which use VDE
call dlopen with the non-versioned name, see #536373 for example).

VDE version 2.3.2 is going to be released soon in unstable.

Ludovico
-- 
l...@dovi.coIRC: garden@freenode
OpenPGP: 1024D/63D2D5D907F89BB8 Jabber/gtalk: garde...@gmail.com



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



Bug#610933: libvdeplug3 declares a conflict with libvdeplug2

2011-11-28 Thread Jonathan Nieder
Hi Ludovico,

Ludovico Gardenghi wrote:

 Thanks for the report and sorry for the delay.

No problem and glad to hear from you.

 Indeed the conflict will be needed with the next release, as we're
 much probably going to move libvdeplug.so from the -dev package to the
 shared library one

That violates policy §8.1 Run-time shared libraries and would make
smooth upgrades of packages that use the shared library difficult.

 (since several virtualization tools which use VDE
 call dlopen with the non-versioned name, see #536373 for example).

Would it be possible to make a different package, such as vde2,
provide the non-versioned symlink, and such packages depend on it?

 VDE version 2.3.2 is going to be released soon in unstable.

Thanks for the update.  If there's anything I can do to help, let me
know.

Regards,
Jonathan



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



Processed: Re: Bug#580308: distcc-pump: Debian patches to distcc shouldn't hardcode python versions

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 580308 grave
Bug #580308 [distcc-pump] distcc-pump: Debian patches to distcc shouldn't 
hardcode python versions
Severity set to 'grave' from 'important'

 thanks
Stopping processing here.

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


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



Bug#642697: marked as done (autodock-vina: FTBFS: ../../../src/main/main.cpp:50:44: error: invalid conversion from 'bool (*)(const string) {aka bool (*)(const std::basic_stringchar)}' to 'boost::e

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 11:47:45 +
with message-id e1ruzgx-0007xj...@franck.debian.org
and subject line Bug#642697: fixed in autodock-vina 1.1.2-2
has caused the Debian Bug report #642697,
regarding autodock-vina: FTBFS: ../../../src/main/main.cpp:50:44: error: 
invalid conversion from 'bool (*)(const string) {aka bool (*)(const 
std::basic_stringchar)}' to 'boost::enable_if_ctrue, void::type* {aka 
void*}' [-fpermissive]
to be marked as done.

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

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


-- 
642697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: autodock-vina
Version: 1.1.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110923 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++ -pthread -ansi -Wno-long-long -O3 -DNDEBUG -I /usr/include  -I 
 ../../../src/lib -o main.o -c ../../../src/main/main.cpp 
 ../../../src/main/main.cpp: In function 'path make_path(const string)':
 ../../../src/main/main.cpp:50:44: error: invalid conversion from 'bool 
 (*)(const string) {aka bool (*)(const std::basic_stringchar)}' to 
 'boost::enable_if_ctrue, void::type* {aka void*}' [-fpermissive]
 /usr/include/boost/filesystem/v3/path.hpp:130:5: error:   initializing 
 argument 2 of 'boost::filesystem3::path::path(const Source, typename 
 boost::enable_ifboost::filesystem3::path_traits::is_pathabletypename 
 boost::decaySource::type ::type*) [with Source = std::basic_stringchar, 
 typename 
 boost::enable_ifboost::filesystem3::path_traits::is_pathabletypename 
 boost::decaySource::type ::type = void]' [-fpermissive]
 ../../../src/main/main.cpp: In function 'int main(int, char**)':
 ../../../src/main/main.cpp:664:57: error: 'path' has no member named 
 'native_file_string'
 ../../../src/main/main.cpp:676:80: error: 'path' has no member named 
 'native_file_string'
 make[2]: *** [main.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/autodock-vina_1.1.2-1_lsid64.buildlog

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

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


---End Message---
---BeginMessage---
Source: autodock-vina
Source-Version: 1.1.2-2

We believe that the bug you reported is fixed in the latest version of
autodock-vina, which is due to be installed in the Debian FTP archive:

autodock-vina_1.1.2-2.debian.tar.gz
  to main/a/autodock-vina/autodock-vina_1.1.2-2.debian.tar.gz
autodock-vina_1.1.2-2.dsc
  to main/a/autodock-vina/autodock-vina_1.1.2-2.dsc
autodock-vina_1.1.2-2_amd64.deb
  to main/a/autodock-vina/autodock-vina_1.1.2-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 642...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille ti...@debian.org (supplier of updated autodock-vina package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Nov 2011 10:58:42 +0100
Source: autodock-vina
Binary: autodock-vina
Architecture: source amd64
Version: 1.1.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 
debian-med-packag...@lists.alioth.debian.org
Changed-By: Andreas Tille ti...@debian.org
Description: 
 autodock-vina - docking of small molecules to proteins
Closes: 642697
Changes: 
 autodock-vina (1.1.2-2) unstable; urgency=low
 .
   * Fix boost compatibility error (thanks for the patch to
 Sebastian Ramacher s.ramac...@gmx.at)
 Closes: #642697
   * debian/control: Fixed Vcs fields
   * Debhelper 8 (control+compat)
Checksums-Sha1: 
 b0dd0a19a5845e227b39aac4ad7ff2985c6d56b2 1493 autodock-vina_1.1.2-2.dsc
 054619c34ee351ce2a8e9673c278bdb74ed7e45a 5334 
autodock-vina_1.1.2-2.debian.tar.gz
 28037f7ea29fdf420505ec8d40b66f6361056e8c 302034 autodock-vina_1.1.2-2_amd64.deb
Checksums-Sha256: 
 bf521d6e41f3bf0de931b0685c3210bf9f32bb3979e18b893df8f65fb2c2011c 1493 

Bug#618048: rlplot: FTBFS: QT_Spec.cpp:1190:16: error: call of overloaded 'QString(int)' is ambiguous

2011-11-28 Thread James Stone
Yes - sadly I don't have time to devote to this excellent program at
present so I would be grateful if you would orphan it.

Thx,

James

On 28/11/2011, Ricardo Mones mo...@debian.org wrote:
   Hi James,

   Thanks Olly for noticing this and sorry for the late response,

 On Mon, Nov 28, 2011 at 11:05:24PM +1300, Olly Betts wrote:
 On Sun, Mar 13, 2011 at 05:54:56PM +0100, Lucas Nussbaum wrote:
  Source: rlplot
  Version: 1.4-1
  Severity: serious
  Tags: wheezy sid
  User: debian...@lists.debian.org
  Usertags: qa-ftbfs-20110313 qa-ftbfs
  Justification: FTBFS on amd64
 
  Hi,
 
  During a rebuild of all packages in sid, your package failed to build on
  amd64.

 This release-critical bug has seen no maintainer response in over 8
 months.
 The last rlplot upload was over 4 years ago (in 2007) and the last
 response
 to a bug report by the maintainer seems to also have be in 2007.
 Meanwhile
 there's been a newer upstream release, which has been packaged for Ubuntu
 but
 is not available in Debian.

 James: Are you still interested in maintaining this package?  If not, it
 would be better to orphan it, so that somebody else interested in it can
 take over maintenance.

   In addition to Olly's question, and as nothing has been received to his
 previous query, if no response is received I will orphan this package next
 weekend, so please let us know your intentions.

   regards,
 --
   Ricardo Mones, on behalf of Debian/QA MIA Team
   ~
   Absence of evidence is not evidence of absence.  Carl Sagan





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



Bug#555753: FTBFS with binutils-gold

2011-11-28 Thread Paul Merrill
Source: moon-lander
Followup-For: Bug #555753

Dear Maintainer,

This package failed to build with gold/ld because it was missing a link
to libm. The attached Makefile links -lm and fixes the build.

Cheers,
Paul Merrill
# Makefile for test program for game_libs - lunar lander
CFLAGS+=-Wall `sdl-config --cflags` 
CC=gcc

LIBS=SDL_image `sdl-config --libs` -lm

C_FILES=moon_lander.c game_lib.c DT_drawtext.c
OBJ_FILES=moon_lander.o game_lib.o DT_drawtext.o 
OUT_FILE=moon-lander

all: game_lib

game_lib: $(OBJ_FILES)
	$(CC) $(CFLAGS) -o $(OUT_FILE) $(OBJ_FILES) -l$(LIBS) -lSDL_mixer

moon_lander.o: moon_lander.c
	$(CC) $(CFLAGS) -c -o $@ $^

game_lib.o: game_lib.c
	$(CC) $(CFLAGS) -c -o $@ $^

DT_drawtext.o: DT_drawtext.c
	$(CC) $(CFLAGS) -c -o $@ $^

clean: 
	rm -f $(OUT_FILE) $(OBJ_FILES)

install: 
	./install.sh




Bug#618048: rlplot: FTBFS: QT_Spec.cpp:1190:16: error: call of overloaded 'QString(int)' is ambiguous

2011-11-28 Thread Olly Betts
On Mon, Nov 28, 2011 at 11:52:52AM +, James Stone wrote:
 Yes - sadly I don't have time to devote to this excellent program at
 present so I would be grateful if you would orphan it.

Thanks for the quick response to my prod.  Hopefully rlplot will find a
new maintainer soon.  I'll try to apply the patches in the BTS and make
an upload so it's at least buildable again, if nobody beats me to it.

Are you wanting to continue to maintain tunapie?  It looks in better
shape, but it seems worth checking while I'm writing.

Cheers,
Olly



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



Processed: patches were submitted

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 554799 patch
Bug #554799 [src:heroes] FTBFS with binutils-gold
Added tag(s) patch.
 tag 555753 patch
Bug #555753 [src:moon-lander] FTBFS with binutils-gold
Added tag(s) patch.
 thanks
Stopping processing here.

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


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



Bug#650245: python-asterisk: fails to work with current version of Asterisk

2011-11-28 Thread Tzafrir Cohen
On Sun, Nov 27, 2011 at 10:56:17PM -0800, Andrew Pollock wrote:
 Package: python-asterisk
 Version: 0.1a3+r160-4.1
 Severity: grave
 Justification: renders package unusable

I figure that 0.2 from http://code.google.com/p/py-asterisk/ is likely
to fix it.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir



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



Bug#610933: [Pkg-vsquare-devel] Bug#610933: libvdeplug3 declares a conflict with libvdeplug2

2011-11-28 Thread Ludovico Gardenghi
On Mon, Nov 28, 2011 at 05:34:31 -0600, Jonathan Nieder wrote:

  Indeed the conflict will be needed with the next release, as we're
  much probably going to move libvdeplug.so from the -dev package to the
  shared library one
 
 That violates policy §8.1 Run-time shared libraries and would make
 smooth upgrades of packages that use the shared library difficult.

I understand that putting a .so symlink, in general, is against the
policy. Yet I saw this sentence at the beginning of chapter 8:

[...] the bare .so symlink is installed in the development package
since it's only used when linking binaries or shared libraries.
However, there are some exceptions for unusual shared libraries or
for shared libraries that are also loaded as dynamic modules by
other programs.

This is the case with libvdeplug: it's both linked at compile time and
dlopen()ed at runtime, depending on the software which uses it.
Do you think it would still be a policy violation?

(In any case, I still can't figure out what should be the *proper* way
for a program for dlopening a .so while providing the version number...
should it loop over all the (infinite :-)) possible SONAMEs who offer
compatibility for the needed interface version?

  (since several virtualization tools which use VDE
  call dlopen with the non-versioned name, see #536373 for example).
 
 Would it be possible to make a different package, such as vde2,
 provide the non-versioned symlink, and such packages depend on it?

It would be unpractical to put the .so symlink in the vde2 package,
since then the -dev one should depend on vde2 (if I'm not wrong). Should
we create a tiny package with only a single symlink in it? I haven't
checked yet how other packagers solved the problem, so maybe the
solution already exists :-)...

Thanks,
Ludovico
-- 
l...@dovi.coIRC: garden@freenode
OpenPGP: 1024D/63D2D5D907F89BB8 Jabber/gtalk: garde...@gmail.com



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



Bug#650121: marked as done (cmigemo: FTBFS when only covering architecture-dependent packages)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 15:33:37 +
with message-id e1rv3d7-0001aw...@franck.debian.org
and subject line Bug#650121: fixed in cmigemo 20110227-2
has caused the Debian Bug report #650121,
regarding cmigemo: FTBFS when only covering architecture-dependent packages
to be marked as done.

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

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


-- 
650121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: cmigemo
Version: 20110227-1
Severity: serious
Justification: fails to build from source

Builds of cmigemo (as on the autobuilders) that only cover its
architecture-dependent packages have been failing:

  make[1]: Entering directory `/.../cmigemo-20110227'
  chmod 755 
/.../cmigemo-20110227/debian/cmigemo-common/usr/share/cmigemo/tools/*.pl
  chmod: cannot access 
`/.../cmigemo-20110227/debian/cmigemo-common/usr/share/cmigemo/tools/*.pl':
  No such file or directory
  make[1]: *** [override_dh_fixperms] Error 1
  make[1]: Leaving directory `/.../cmigemo-20110227'
  make: *** [binary-arch] Error 2

Please adjust the tools' permissions only when actually building the
cmigemo-common package.  As a matter of style, I'd also suggest specifying
permissions symbolically and omitting the redundant $(CURDIR)/, yielding

if [ -d debian/cmigemo-common/usr/share/cmigemo/tools ]; then
chmod +x debian/cmigemo-common/usr/share/cmigemo/tools/*.pl
fi

Thanks!


---End Message---
---BeginMessage---
Source: cmigemo
Source-Version: 20110227-2

We believe that the bug you reported is fixed in the latest version of
cmigemo, which is due to be installed in the Debian FTP archive:

cmigemo-common_20110227-2_all.deb
  to main/c/cmigemo/cmigemo-common_20110227-2_all.deb
cmigemo_20110227-2.debian.tar.gz
  to main/c/cmigemo/cmigemo_20110227-2.debian.tar.gz
cmigemo_20110227-2.dsc
  to main/c/cmigemo/cmigemo_20110227-2.dsc
cmigemo_20110227-2_amd64.deb
  to main/c/cmigemo/cmigemo_20110227-2_amd64.deb
libmigemo-dbg_20110227-2_amd64.deb
  to main/c/cmigemo/libmigemo-dbg_20110227-2_amd64.deb
libmigemo-dev_20110227-2_amd64.deb
  to main/c/cmigemo/libmigemo-dev_20110227-2_amd64.deb
libmigemo1_20110227-2_amd64.deb
  to main/c/cmigemo/libmigemo1_20110227-2_amd64.deb
vim-migemo_20110227-2_all.deb
  to main/c/cmigemo/vim-migemo_20110227-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 650...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Youhei SASAKI uwab...@gfd-dennou.org (supplier of updated cmigemo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Nov 2011 23:19:53 +0900
Source: cmigemo
Binary: vim-migemo cmigemo-common cmigemo libmigemo1 libmigemo-dev libmigemo-dbg
Architecture: source all amd64
Version: 20110227-2
Distribution: unstable
Urgency: low
Maintainer: Youhei SASAKI uwab...@gfd-dennou.org
Changed-By: Youhei SASAKI uwab...@gfd-dennou.org
Description: 
 cmigemo- Japanse incremental search tool written in C - binary
 cmigemo-common - Japanse incremental search tool written in C - common files
 libmigemo-dbg - Japanse incremental search tool written in C - detached 
debugging
 libmigemo-dev - Japanse incremental search tool written in C - development 
binari
 libmigemo1 - Japanse incremental search tool written in C - library
 vim-migemo - vim plugin for C/Migemo
Closes: 650121
Changes: 
 cmigemo (20110227-2) unstable; urgency=low
 .
   * Add DM-Upload-Allowed: yes
   * Fix FTBFS, thanks to Aaron M.Ucko(Closes: #650121)
   * Separate Vim plugin to vim-migemo package
Checksums-Sha1: 
 40170f8d84762744f3fbcb7d8d138f61b92d85fe 2133 cmigemo_20110227-2.dsc
 5b3b7c49296c1ff54d604b1c5bef15c71d7a411d 11970 cmigemo_20110227-2.debian.tar.gz
 b8098f460656f3c0819ff1c7a9170a51256b0ae4 4486 vim-migemo_20110227-2_all.deb
 9a50a2c5d433d43a7eceddf9a6de77c52ff51967 25870 
cmigemo-common_20110227-2_all.deb
 32c8e8601824b42b4049cae999336f32c8cf3cc1 8750 cmigemo_20110227-2_amd64.deb
 21d9a8da8419d2d5be56431ad409a6ad6c1c9185 16994 libmigemo1_20110227-2_amd64.deb
 df145fdb7428c31aa679b604a1f8c7f6b1f68eb0 17582 
libmigemo-dev_20110227-2_amd64.deb
 98ba25d4caea85aff8a15defd3bdbbb829645b04 31632 

Bug#650245: python-asterisk: fails to work with current version of Asterisk

2011-11-28 Thread Marcos Marado
 I figure that 0.2 from http://code.google.com/p/py-asterisk/ is likely
 to fix it.

It does, but the banner is still hardcoded:
http://code.google.com/p/py-asterisk/source/detail?r=e6b32cbdaeea1c3154888638f5f66a12969bf68dpath=/Asterisk/Manager.py

While it would be nice to have a more sensible way of dealing with
this, upgrading to 0.2 will be enough (for now?) to close this bug.

Also, and in any case, Justification: renders package unusable seems
to be quite exaggerated: after all this package works as well as ever
- the only problem is that it only supports Asterisk 1.0.

Best regards,
-- 
Marcos Marado



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



Bug#650293: segfault while running it with eventlet

2011-11-28 Thread Faule Socke
Source: python-greenlet
Severity: grave

When running this code with the python-eventlet and python-greenlet packages
installed I get a segfault: http://eventlet.net/doc/examples.html#echo-server

The problem lies in the greenlet module and is already fixed on the bitbucket
version from snaury: https://bitbucket.org/snaury/greenlet

The fixed version is _not_ available on pypi yet.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)



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



Bug#613387: marked as done (libbio-das-lite-perl: FTBFS: test failures)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 16:14:53 +
with message-id e1rv3r3-0002ov...@franck.debian.org
and subject line Bug#613387: fixed in libbio-das-lite-perl 2.04-1.1
has caused the Debian Bug report #613387,
regarding libbio-das-lite-perl: FTBFS: test failures
to be marked as done.

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

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


-- 
613387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libbio-das-lite-perl
Version: 2.04-1
Severity: serious
Justification: no longer builds from source

This package failed to build on a clean sid chroot today:

t/00-critic.t ... skipped: Author test.  Set $ENV{TEST_AUTHOR} to a 
true value to run.
t/00-distribution.t . ok
t/00-pod.t .. ok
t/00-podcoverage.t .. ok
t/01-general.t .. ok
t/02-statuscodes.t .. ok

#   Failed test 'dsns call gave a arrayref value for the one key'
#   at t/05-singledsn.t line 37.
Can't use an undefined value as an ARRAY reference at t/05-singledsn.t line 38.
# Looks like you planned 30 tests but ran 18.
# Looks like you failed 1 test of 18 run.
# Looks like your test exited with 115 just after 18.
t/05-singledsn.t  
Dubious, test returned 115 (wstat 29440, 0x7300)
Failed 13/30 subtests 
t/06-singledsn-singleseg.t .. ok
t/07-singledsn-multiseg.t ... ok

#   Failed test 'dsns call gave a arrayref value for the one key'
#   at t/10-multidsn.t line 32.
Can't use an undefined value as an ARRAY reference at t/10-multidsn.t line 34.
# Looks like you planned 10 tests but ran 8.
# Looks like you failed 1 test of 8 run.
# Looks like your test exited with 115 just after 8.
t/10-multidsn.t . 
Dubious, test returned 115 (wstat 29440, 0x7300)
Failed 3/10 subtests 
t/20-authentication.t ... ok
t/21-proxy.t  skipped: Proxy testing requires POE and 
WWW::Curl::Simple
t/40-dna.t .. ok
t/45-sequence.t . ok
t/50-entry_points.t . ok
t/60-features.t . ok
t/60-features_chunked.t . ok
t/60-features_empty.t ... ok
t/61-features_group.t ... ok
t/70-alignment.t  ok
t/80-structure.t  ok
t/90-sources.t .. ok

Test Summary Report
---
t/05-singledsn.t  (Wstat: 29440 Tests: 18 Failed: 1)
  Failed test:  18
  Non-zero exit status: 115
  Parse errors: Bad plan.  You planned 30 tests but ran 18.
t/10-multidsn.t   (Wstat: 29440 Tests: 8 Failed: 1)
  Failed test:  8
  Non-zero exit status: 115
  Parse errors: Bad plan.  You planned 10 tests but ran 8.
Files=22, Tests=106,  5 wallclock secs ( 0.07 usr  0.11 sys +  3.03 cusr  1.21 
csys =  4.42 CPU)
Result: FAIL
Failed 2/22 test programs. 2/106 subtests failed.
dh_auto_test: perl Build test returned exit code 255


---End Message---
---BeginMessage---
Source: libbio-das-lite-perl
Source-Version: 2.04-1.1

We believe that the bug you reported is fixed in the latest version of
libbio-das-lite-perl, which is due to be installed in the Debian FTP archive:

libbio-das-lite-perl_2.04-1.1.diff.gz
  to main/libb/libbio-das-lite-perl/libbio-das-lite-perl_2.04-1.1.diff.gz
libbio-das-lite-perl_2.04-1.1.dsc
  to main/libb/libbio-das-lite-perl/libbio-das-lite-perl_2.04-1.1.dsc
libbio-das-lite-perl_2.04-1.1_all.deb
  to main/libb/libbio-das-lite-perl/libbio-das-lite-perl_2.04-1.1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 613...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated libbio-das-lite-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Nov 2011 16:24:55 +0100
Source: libbio-das-lite-perl
Binary: libbio-das-lite-perl
Architecture: source all
Version: 2.04-1.1
Distribution: unstable
Urgency: low
Maintainer: Richard Holland holl...@eaglegenomics.com
Changed-By: gregor herrmann gre...@debian.org
Description: 
 libbio-das-lite-perl - implementation of the BioDas protocol
Closes: 613387
Changes: 
 libbio-das-lite-perl (2.04-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS: test failures:
 debian/rules:
 - unset 

Processed: [bts-link] source package libmason-perl

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 #
 # bts-link upstream status pull for source package libmason-perl
 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
 #
 user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
 # remote status report for #649066 (http://bugs.debian.org/649066)
 # Bug title: libmason-perl and mason: error when trying to install together
 #  * http://rt.cpan.org/Public/Bug/Display.html?id=72497
 #  * remote status changed: (?) - resolved
 #  * closed upstream
 tags 649066 + fixed-upstream
Bug #649066 [libmason-perl] libmason-perl and mason: error when trying to 
install together
Added tag(s) fixed-upstream.
 usertags 649066 + status-resolved
Bug#649066: libmason-perl and mason: error when trying to install together
There were no usertags set.
Usertags are now: status-resolved.
 thanks
Stopping processing here.

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


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



Processed: [bts-link] source package src:python-docutils

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 #
 # bts-link upstream status pull for source package src:python-docutils
 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
 #
 user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
 # remote status report for #645369 (http://bugs.debian.org/645369)
 # Bug title: python-docutils: FTBFS: FAIL: test_publish 
 (test_writers.test_docutils_xml.DocutilsXMLTestCase)
 #  * 
 http://sourceforge.net/tracker/?func=detailatid=422030aid=3423983group_id=38414
 #  * remote status changed: Pending - Closed
 #  * remote resolution changed: (?) - Fixed
 #  * closed upstream
 tags 645369 + fixed-upstream
Bug #645369 [src:python-docutils] python-docutils: FTBFS: FAIL: test_publish 
(test_writers.test_docutils_xml.DocutilsXMLTestCase)
Added tag(s) fixed-upstream.
 usertags 645369 - status-Pending
Bug#645369: python-docutils: FTBFS: FAIL: test_publish 
(test_writers.test_docutils_xml.DocutilsXMLTestCase)
Usertags were: status-Pending.
Usertags are now: .
 usertags 645369 + status-Closed resolution-Fixed
Bug#645369: python-docutils: FTBFS: FAIL: test_publish 
(test_writers.test_docutils_xml.DocutilsXMLTestCase)
There were no usertags set.
Usertags are now: resolution-Fixed status-Closed.
 thanks
Stopping processing here.

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


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



Bug#650265: dma: cannot deliver mail to smtp server

2011-11-28 Thread Miquel van Smoorenburg
tag 650265 +patch
thanks

This should go into stable too if possible.

Description: Read reponse from smtp server up to crlf
Author: Miquel van Smoorenburg miqu...@cistron.nl
Last-Update: 2011-11-28

--- a/net.c 2011-11-28 12:27:29.0 +0100
+++ b/net.c 2011-11-28 13:00:39.145291582 +0100
@@ -166,6 +166,14 @@
}
len += rlen;
}
+   /* read up to \n */
+   if (memchr(buff + pos, '\n', len - pos) == NULL) {
+   if (len  sizeof(buff))
+   continue;
+   strcpy(neterr, line too long in reply from server);
+   return (-1);
+   }
+
/*
 * If there is an external buffer with a size bigger than zero
 * and as long as there is space in the external buffer and



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



Processed: Re: dma: cannot deliver mail to smtp server

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 650265 +patch
Bug #650265 [dma] dma: cannot deliver mail to smtp server
Added tag(s) patch.
 thanks
Stopping processing here.

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


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



Processed: Re: Bug#650223: Segmentation fault in file open dialog jumping through the directory structure

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 650223 grave
Bug #650223 [libgtk-3-0] Segmentation fault in file open dialog jumping through 
the directory structure
Severity set to 'grave' from 'important'

 forwarded 650223 https://bugzilla.gnome.org/show_bug.cgi?id=664137
Bug #650223 [libgtk-3-0] Segmentation fault in file open dialog jumping through 
the directory structure
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=664137'.
 thanks
Stopping processing here.

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


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



Bug#650307: CVE-2011-3152/CVE-2011-3154

2011-11-28 Thread Moritz Muehlenhoff
Package: update-manager
Severity: grave
Tags: security

Ubuntu released the following security update for update-manager:
http://www.ubuntu.com/usn/usn-1284-1/

Details and patches:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/881548

Cheers,
Moritz



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



Bug#650310: Jackd 2 driver buggy - puredata locks up toggling DSP on/off.

2011-11-28 Thread Matthew Grant
Package: puredata
Version: 0.43.0-4
Severity: grave
Tags: upstream

Puredata locks up when toggling DSP on/off, and it opens/closes its jackd
connections.  There are also problems running jackd asynchronously, with lots
of error messages.

What makes this bug grave is that most default Debian installs are running
pulseaudio which is a required dependency for the default desktop, and most
workstations only have one audio device.  Pulseaudio is very
hard to kill off, being restarted automatically when it is not there.

Puredata works with its ALSA drivers, but you cannot use those drivers with
pulseaudio hogging the audio devices.  Jackd2 can be installed and run from
qjackctl, which is what you expect if you want performance audio, but then
puredata will not work properly due to its bug jack implementation.

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

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

Versions of packages puredata depends on:
ii  puredata-core   0.43.0-4
ii  puredata-dev0.43.0-4
ii  puredata-doc0.43.0-4
ii  puredata-extra  0.43.0-4
ii  puredata-gui0.43.0-4
ii  puredata-utils  0.43.0-4

Versions of packages puredata recommends:
ii  gem  1:0.92.3-2+b1

Versions of packages puredata suggests:
pn  pd-aubio   none
pn  pd-csound  none
pn  pd-pdp none
pn  pd-zexynone

-- no debconf information



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



Bug#641125: marked as done (Could not start application.)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 19:58:28 +0100
with message-id 2028195828.e7b40ecd1f27a1e9e66eb...@yahoo.com
and subject line Done: Could not start application.
has caused the Debian Bug report #641125,
regarding Could not start application.
to be marked as done.

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

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


-- 
641125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: fillmore
Version: 0.1.0-1
Severity: grave


After trying to start the program, I get this error:


Could not start application.
Could not create element gconfaudiosink((null))


-- 
http://www.fastmail.fm - Same, same, but different...



---End Message---
---BeginMessage---
Package: fillmore
Version: 0.1.0-1

Error no longer occurs.

---End Message---


Bug#650314: misses .so symlink

2011-11-28 Thread Daniel Baumann
Package: procps
Version: 3.3.0-1
Severity: serious

Hi,

libproc-dev misses the libproc-ng.so symlink in /usr/lib, thus making
other packages fail building against it.

Regards,
Daniel

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/



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



Bug#650317: netspeed does not work with gnome 3.2

2011-11-28 Thread shirish शिरीष
Package: netspeed
Version: 0.16-3
Justification: renders package unusable
Severity: grave

Dear Maintainer,
I was running updates on my system and netspeed which is/was on
systray is not there anymore. Please see
https://poddery.com/uploads/images/15924d83dcfbd530d280.png . I do not
see a way in which I can see or use netspeed. This makes it harder for
me to know if my networking is giving me correct speeds or not. I
tried to find if there is anyway to do something about it but seems
there isn't. I'm in gnome-session-fallback. I did find a
gnome-shell-extension which does something similar
https://github.com/ojo/gnome-shell-extension-netmonitor but then
gnome-shell-extension still has stuff from experimental.

$ sudo aptitude install gnome-shell-extensions
The following NEW packages will be installed:
  gnome-shell-extensions{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.0 kB of archives. After unpacking 604 kB will be used.
The following packages have unmet dependencies:
  gnome-shell-extensions: Depends: gnome-shell (= 3.2.0) but 3.0.2-8
is installed.
  Depends: gir1.2-gtop-2.0 but it is not going
to be installed.
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) gnome-shell-extensions [Not Installed]


Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages:
1)  evolution-exchange

  Install the following packages:
2)  gir1.2-accountsservice-1.0 [0.6.15-2 (unstable)]
3)  gir1.2-caribou-1.0 [0.4.1-2 (unstable)]
4)  gir1.2-folks-0.6 [0.6.5-1 (testing, unstable)]
5)  gir1.2-gee-1.0 [0.6.1-3 (testing, unstable)]
6)  gir1.2-gmenu-3.0 [3.2.0.1-2 (unstable)]
7)  gir1.2-gtop-2.0 [2.28.4-1 (testing, unstable)]
8)  gnome-contacts [3.2.2-1 (experimental)]
9)  libcamel-1.2-29 [3.2.1-1 (experimental)]
10) libcaribou-common [0.4.1-2 (unstable)]
11) libcaribou0 [0.4.1-2 (unstable)]
12) libcurl3-nss [7.22.0-3 (testing, unstable)]
13) libebook-1.2-12 [3.2.1-1 (experimental)]
14) libecal-1.2-10 [3.2.1-1 (experimental)]
15) libedata-book-1.2-11 [3.2.1-1 (experimental)]
16) libedata-cal-1.2-13 [3.2.1-1 (experimental)]
17) libedataserver-1.2-15 [3.2.1-1 (experimental)]
18) libedataserverui-3.0-1 [3.2.1-1 (experimental)]
19) libfolks-eds25 [0.6.5-2 (experimental)]
20) libgdata13 [0.10.1-1 (experimental)]
21) libgnome-desktop-3-2 [3.2.1-2 (experimental)]
22) libgoa-1.0-0 [3.2.1-2 (unstable)]
23) libgoa-1.0-common [3.2.1-2 (unstable)]
24) liboauth0 [0.9.4-3 (testing, unstable)]

  Upgrade the following packages:
25) evolution [3.0.3-3 (now, unstable) - 3.2.1-1 (experimental)]
26) evolution-common [3.0.3-3 (now, unstable) - 3.2.1-1
(experimental)]
27) evolution-data-server [3.0.3-2 (now, testing, unstable) -
3.2.1-1 (experimental)]
28) evolution-data-server-common [3.0.3-2 (now, testing, unstable)
- 3.2.1-1 (experimental)]
29) evolution-plugins [3.0.3-3 (now, unstable) - 3.2.1-1
(experimental)]
30) gnome-shell [3.0.2-8 (now, unstable) - 3.2.1-5
(experimental)]
31) libebackend-1.2-1 [3.0.3-2 (now, testing, unstable) - 3.2.1-1
(experimental)]
32) libevolution [3.0.3-3 (now, unstable) - 3.2.1-1
(experimental)]
33) libgtkhtml-4.0-0 [4.0.2-1 (now, testing, unstable) - 4.2.1-1
(experimental)]
34) libgtkhtml-4.0-common [4.0.2-1 (now, testing, unstable) -
4.2.1-1 (experimental)]
35) libgtkhtml-editor-4.0-0 [4.0.2-1 (now, testing, unstable) -
4.2.1-1 (experimental)]

Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.

So atm working without a network monitor :(

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

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages netspeed depends on:
ii  libatk1.0-0  2.2.0-2
ii  libc62.13-21
ii  libcairo-gobject21.10.2-6.1
ii  libcairo21.10.2-6.1
ii  libfontconfig1   2.8.0-3
ii  libfreetype6 2.4.8-1
ii  libgconf2-4  3.2.3-1
ii  libgdk-pixbuf2.0-0   2.24.0-1
ii  libglib2.0-0 2.30.2-4
ii  libgtk-3-0   3.2.2-2
ii  libgtop2-7   2.28.4-1
ii  libiw30  30~pre9-7
ii  libpanel-applet-4-0  3.2.1-1
ii  libpango1.0-01.29.4-2

netspeed recommends no packages.

netspeed suggests no packages.

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17



--
To 

Bug#647307: marked as done (haskell-xss-sanitize: fails to build on mipsel)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 21:06:48 +0100
with message-id 1322510808.2666.34.camel@kirk
and subject line Re: [Pkg-haskell-maintainers]  Bug#647307: 
haskell-xss-sanitize: fails to build on mipsel
has caused the Debian Bug report #647307,
regarding haskell-xss-sanitize: fails to build on mipsel
to be marked as done.

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

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


-- 
647307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: haskell-xss-sanitize
Version: 0.3.0.1-1
Severity: serious

See
https://buildd.debian.org/status/fetch.php?pkg=haskell-xss-sanitizearch=mipselver=0.3.0.1-1stamp=1320029811

Cheers,
Julien


---End Message---
---BeginMessage---
Hi,

Am Mittwoch, den 23.11.2011, 17:43 +0100 schrieb Joachim Breitner:
 Am Mittwoch, den 23.11.2011, 17:01 +0100 schrieb Giovanni Mascellani:
  On 22/11/2011 23:20, Joachim Breitner wrote:
   Am Freitag, den 18.11.2011, 14:10 +0100 schrieb Giovanni Mascellani:
   I just asked to install build dependencies on eder to do tests on
   mipsel.
   
   any news from this front?
  
  Yes: the package builds without errors. As usual, I don't know what to
  do in this situation.
 
 oh, and I think it is reasonable to upload the build (if it was built
 with -b -B), as long as it stays the exception.

by some fancy, I re-scheduled a build of xss-sanitize on mipsel and
suddently, it just built (on eysler – the build failures seem to be
buildd-specific), and all its outdated dependencies built as well:
https://buildd.debian.org/status/fetch.php?pkg=haskell-xss-sanitizearch=mipselver=0.3.0.1-1stamp=1322420010

Now the haskell package are in shape for a migration:
http://release.debian.org/transitions/html/haskell.html

@Release team: Do you think its possible to hint ghc and haskell-* into
testing soon? From the last migration it seems to be enough to hint ghc
and britney will figure out that it has to migrate haskell-* with it.
The last upload of a haskell package is haskell-maths, and needs 7 more
days to be ready to migrate.

@Debian Haskell Team: Please avoid uploading haskell libraries the next
8 days or so, or upload to experimental, unless it is a package that is
not yet in testing and not depended upon by a package that has a version
in testing.

Greetings,
Joachim


-- 
Joachim nomeata Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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


Bug#650317: marked as done (netspeed does not work with gnome 3.2)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 02:20:31 +0530
with message-id 
CADdDZRkgmPe0w2TJcDAA309bLgqwjdJ05a5hESW6BSr-6d=o...@mail.gmail.com
and subject line closing because its incorrect.
has caused the Debian Bug report #650317,
regarding netspeed does not work with gnome 3.2
to be marked as done.

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

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


-- 
650317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: netspeed
Version: 0.16-3
Justification: renders package unusable
Severity: grave

Dear Maintainer,
I was running updates on my system and netspeed which is/was on
systray is not there anymore. Please see
https://poddery.com/uploads/images/15924d83dcfbd530d280.png . I do not
see a way in which I can see or use netspeed. This makes it harder for
me to know if my networking is giving me correct speeds or not. I
tried to find if there is anyway to do something about it but seems
there isn't. I'm in gnome-session-fallback. I did find a
gnome-shell-extension which does something similar
https://github.com/ojo/gnome-shell-extension-netmonitor but then
gnome-shell-extension still has stuff from experimental.

$ sudo aptitude install gnome-shell-extensions
The following NEW packages will be installed:
  gnome-shell-extensions{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.0 kB of archives. After unpacking 604 kB will be used.
The following packages have unmet dependencies:
  gnome-shell-extensions: Depends: gnome-shell (= 3.2.0) but 3.0.2-8
is installed.
  Depends: gir1.2-gtop-2.0 but it is not going
to be installed.
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) gnome-shell-extensions [Not Installed]


Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages:
1)  evolution-exchange

  Install the following packages:
2)  gir1.2-accountsservice-1.0 [0.6.15-2 (unstable)]
3)  gir1.2-caribou-1.0 [0.4.1-2 (unstable)]
4)  gir1.2-folks-0.6 [0.6.5-1 (testing, unstable)]
5)  gir1.2-gee-1.0 [0.6.1-3 (testing, unstable)]
6)  gir1.2-gmenu-3.0 [3.2.0.1-2 (unstable)]
7)  gir1.2-gtop-2.0 [2.28.4-1 (testing, unstable)]
8)  gnome-contacts [3.2.2-1 (experimental)]
9)  libcamel-1.2-29 [3.2.1-1 (experimental)]
10) libcaribou-common [0.4.1-2 (unstable)]
11) libcaribou0 [0.4.1-2 (unstable)]
12) libcurl3-nss [7.22.0-3 (testing, unstable)]
13) libebook-1.2-12 [3.2.1-1 (experimental)]
14) libecal-1.2-10 [3.2.1-1 (experimental)]
15) libedata-book-1.2-11 [3.2.1-1 (experimental)]
16) libedata-cal-1.2-13 [3.2.1-1 (experimental)]
17) libedataserver-1.2-15 [3.2.1-1 (experimental)]
18) libedataserverui-3.0-1 [3.2.1-1 (experimental)]
19) libfolks-eds25 [0.6.5-2 (experimental)]
20) libgdata13 [0.10.1-1 (experimental)]
21) libgnome-desktop-3-2 [3.2.1-2 (experimental)]
22) libgoa-1.0-0 [3.2.1-2 (unstable)]
23) libgoa-1.0-common [3.2.1-2 (unstable)]
24) liboauth0 [0.9.4-3 (testing, unstable)]

  Upgrade the following packages:
25) evolution [3.0.3-3 (now, unstable) - 3.2.1-1 (experimental)]
26) evolution-common [3.0.3-3 (now, unstable) - 3.2.1-1
(experimental)]
27) evolution-data-server [3.0.3-2 (now, testing, unstable) -
3.2.1-1 (experimental)]
28) evolution-data-server-common [3.0.3-2 (now, testing, unstable)
- 3.2.1-1 (experimental)]
29) evolution-plugins [3.0.3-3 (now, unstable) - 3.2.1-1
(experimental)]
30) gnome-shell [3.0.2-8 (now, unstable) - 3.2.1-5
(experimental)]
31) libebackend-1.2-1 [3.0.3-2 (now, testing, unstable) - 3.2.1-1
(experimental)]
32) libevolution [3.0.3-3 (now, unstable) - 3.2.1-1
(experimental)]
33) libgtkhtml-4.0-0 [4.0.2-1 (now, testing, unstable) - 4.2.1-1
(experimental)]
34) libgtkhtml-4.0-common [4.0.2-1 (now, testing, unstable) -
4.2.1-1 (experimental)]
35) libgtkhtml-editor-4.0-0 [4.0.2-1 (now, testing, unstable) -
4.2.1-1 (experimental)]

Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.

So atm working without a network monitor :(

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

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of 

Bug#638244: What is the situation of the picard package?

2011-11-28 Thread Vincent Danjean

  Hi,

  This package is really lagging after upstream (current Debian
package: 0.11-2.1+b1, current upstream 0.16 at least). The packaged
version has a lot of problems that have been fixed upstream.
  #554528 is a wishbug for the new upstream, tagged pending by
the maintainer (without any message) on 16 Mar 2010,
with several people that, at one time or another, made the work to
upgrade the package, some of them even talked about hijacking the
package.
  However, the current maintainer only add the tag pending and
write *one* message about a problem in icon licensing, problem that
seems to be fixed for nearly one year according to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554528#59

  For myself, I used the packaging done by sebastien.villemot to
upgrade to 0.16 (for interested users, you can find the source package
and the binary for amd64 on my private repo, see my signature).
  Note that this version compiles correctly with libav. So the
serious bug #638244 seems to have been handled upstream.

  I would really welcome some inputs from the maintainer. Is it MIA?
Does he still take care of this package? Should he add a RFH? Or should
he co-maintain this package within the pkg-multimedia team? ...

  Regards,
Vincent

--
Vincent Danjean   GPG key ID 0x9D025E87 vdanj...@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A  8A94 0BF7 7867 9D02 5E87
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main




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



Bug#649604: marked as done (packagekit: FTBFS on armhf and s390x)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 21:15:00 +
with message-id e1rv8xu-km...@franck.debian.org
and subject line Bug#649604: fixed in packagekit 0.7.1-2
has caused the Debian Bug report #649604,
regarding packagekit: FTBFS on armhf and s390x
to be marked as done.

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

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


-- 
649604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: packagekit
Version: 0.7.1
Severity: serious
Justification: FTBFS

Hello,

  Your package fails to build from source on Debian autobuilder network.

  Please check your package build logs at:
  http://buildd.debian.org/status/package.php?p=packagekitsuite=sid

Best regards


-- System Information:
Debian Release: wheezy/sid
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Source: packagekit
Source-Version: 0.7.1-2

We believe that the bug you reported is fixed in the latest version of
packagekit, which is due to be installed in the Debian FTP archive:

browser-plugin-packagekit_0.7.1-2_amd64.deb
  to main/p/packagekit/browser-plugin-packagekit_0.7.1-2_amd64.deb
gir1.2-packagekitglib-1.0_0.7.1-2_amd64.deb
  to main/p/packagekit/gir1.2-packagekitglib-1.0_0.7.1-2_amd64.deb
gstreamer0.10-packagekit_0.7.1-2_amd64.deb
  to main/p/packagekit/gstreamer0.10-packagekit_0.7.1-2_amd64.deb
libpackagekit-glib2-14_0.7.1-2_amd64.deb
  to main/p/packagekit/libpackagekit-glib2-14_0.7.1-2_amd64.deb
libpackagekit-glib2-dev_0.7.1-2_amd64.deb
  to main/p/packagekit/libpackagekit-glib2-dev_0.7.1-2_amd64.deb
libpackagekit-qt2-2_0.7.1-2_amd64.deb
  to main/p/packagekit/libpackagekit-qt2-2_0.7.1-2_amd64.deb
libpackagekit-qt2-dev_0.7.1-2_amd64.deb
  to main/p/packagekit/libpackagekit-qt2-dev_0.7.1-2_amd64.deb
packagekit-backend-aptcc_0.7.1-2_amd64.deb
  to main/p/packagekit/packagekit-backend-aptcc_0.7.1-2_amd64.deb
packagekit-backend-smart_0.7.1-2_amd64.deb
  to main/p/packagekit/packagekit-backend-smart_0.7.1-2_amd64.deb
packagekit-bash-completion_0.7.1-2_amd64.deb
  to main/p/packagekit/packagekit-bash-completion_0.7.1-2_amd64.deb
packagekit-dbg_0.7.1-2_amd64.deb
  to main/p/packagekit/packagekit-dbg_0.7.1-2_amd64.deb
packagekit-docs_0.7.1-2_all.deb
  to main/p/packagekit/packagekit-docs_0.7.1-2_all.deb
packagekit-gtk3-module_0.7.1-2_amd64.deb
  to main/p/packagekit/packagekit-gtk3-module_0.7.1-2_amd64.deb
packagekit_0.7.1-2.debian.tar.gz
  to main/p/packagekit/packagekit_0.7.1-2.debian.tar.gz
packagekit_0.7.1-2.dsc
  to main/p/packagekit/packagekit_0.7.1-2.dsc
packagekit_0.7.1-2_amd64.deb
  to main/p/packagekit/packagekit_0.7.1-2_amd64.deb
python-packagekit_0.7.1-2_all.deb
  to main/p/packagekit/python-packagekit_0.7.1-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 649...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klumpp matth...@tenstral.net (supplier of updated packagekit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Nov 2011 15:37:55 +0100
Source: packagekit
Binary: packagekit packagekit-bash-completion packagekit-docs 
libpackagekit-glib2-14 libpackagekit-glib2-dev gir1.2-packagekitglib-1.0 
libpackagekit-qt2-2 libpackagekit-qt2-dev packagekit-gtk3-module 
gstreamer0.10-packagekit browser-plugin-packagekit python-packagekit 
packagekit-backend-aptcc packagekit-backend-smart packagekit-dbg
Architecture: source amd64 all
Version: 0.7.1-2
Distribution: unstable
Urgency: low
Maintainer: Matthias Klumpp matth...@tenstral.net
Changed-By: Matthias Klumpp matth...@tenstral.net
Description: 
 browser-plugin-packagekit - Plugin to install missing plugins using PackageKit
 gir1.2-packagekitglib-1.0 - GObject introspection data for the PackageKit GLib 
library
 gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit
 libpackagekit-glib2-14 - Library for accessing PackageKit using GLib
 libpackagekit-glib2-dev - Library for accessing PackageKit using GLib 
(development files)
 libpackagekit-qt2-2 - Library for 

Bug#649604: Acknowledgement of maintainer-only report (packagekit: FTBFS on armhf and s390x)

2011-11-28 Thread Adam D. Barratt
On Tue, 2011-11-22 at 15:26 +, Hector Oron wrote:
 Hello again,
 
  I meant
http://buildd.debian-ports.org/status/package.php?p=packagekitsuite=sid
 
 I set severity serious as armhf and s390x are just about to be
 bootstrapped into main Debian archive and makes GNOME uninstallable.

That doesn't make them release architectures, or the bug RC though...
incredibly annoying, possibly, but that's closer to important. :-)

Regards,

Adam




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



Bug#640828: cxxtools: FTBFS on ia64 (check for atomictype failed)

2011-11-28 Thread Aurelien Jarno
tags 640828 + patch
thanks

On Wed, Sep 07, 2011 at 08:46:40PM +0200, Julien Cristau wrote:
 retitle 640828 cxxtools: FTBFS on ia64, s390, sparc
 kthxbye
 
 On Wed, Sep  7, 2011 at 20:39:46 +0200, Julien Cristau wrote:
 
  Package: cxxtools
  Version: 2.0-1
  Severity: serious
  
  cxxtools FTBFS on ia64 in the configure step:
   configure: error: check for atomictype failed
   make: *** [debian/stamp-autotools] Error 1
  
  See
  https://buildd.debian.org/status/fetch.php?pkg=cxxtoolsarch=ia64ver=2.0-1stamp=1313148320
  
 And same error on other archs.
 

cxxtools includes atomic types support for various architectures, as
well as a a pthread and generic version. The problem is that it doesn't
fallback to them when not on an architecture supported through assembly
code.

The patch below forces the atomic type to pthread if not building on an
architecture known to have assembly support.

diff -Nru cxxtools-2.0/debian/rules cxxtools-2.0/debian/rules
--- cxxtools-2.0/debian/rules   2011-08-08 13:33:35.0 +0200
+++ cxxtools-2.0/debian/rules   2011-11-27 19:29:45.0 +0100
@@ -13,6 +13,12 @@
 
 DEB_CONFIGURE_NORMAL_ARGS += --enable-shared --enable-static
 
+# Automatic detection doesn't fallback to working atomic type.
+# Force it to pthread for architectures not having specific code.
+ifeq (,$(filter $(DEB_HOST_ARCH_CPU), amd64 i386 mips mipsel powerpc))
+DEB_CONFIGURE_NORMAL_ARGS += --with-atomictype=pthread 
+endif
+
 # Actually, rebuilding the whole build chain is a bit overkill
 # currently.  It used to be necessary since we did changes to
 # configure.in and Makefile.am files.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net



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



Bug#648615: Latest update of nautilus in unstable has removed everything from desktop

2011-11-28 Thread Josselin Mouette
Le dimanche 27 novembre 2011 à 19:25 -0800, JS a écrit : 
 Are these changes in nautilus 3.0 or was some default configuration removed
 that allowed them to work as in 2.30?

The default configuration has changed.

-- 
 .''`.  Josselin Mouette
: :' :
`. `'
  `-


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


Processed: Re: Bug#640828: cxxtools: FTBFS on ia64 (check for atomictype failed)

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 640828 + patch
Bug #640828 [cxxtools] cxxtools: FTBFS on ia64, s390, sparc
Added tag(s) patch.
 thanks
Stopping processing here.

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


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



Bug#649841: marked as done (openssl: FTBFS on sparc (Hardware capability mul32 not enabled for smul))

2011-11-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Nov 2011 22:22:18 +
with message-id e1rv9ac-0002aw...@franck.debian.org
and subject line Bug#649841: fixed in openssl 1.0.0e-3
has caused the Debian Bug report #649841,
regarding openssl: FTBFS on sparc (Hardware capability mul32 not enabled for 
smul)
to be marked as done.

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

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


-- 
649841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: openssl
Version: 1.0.0e-2.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

See
https://buildd.debian.org/status/fetch.php?pkg=opensslarch=sparcver=1.0.0e-2.1stamp=1320702109

 gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS 
 -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DB_ENDIAN -DTERMIO -O3 
 -Wa,--noexecstack -mcpu=v8 -g -Wall -DBN_DIV2W   -c -o mem_dbg.o mem_dbg.c
 /tmp/ccVsQzxF.s: Assembler messages:
 /tmp/ccVsQzxF.s:48: Error: Hardware capability mul32 not enabled for smul.
 /tmp/ccVsQzxF.s:51: Error: Hardware capability mul32 not enabled for smul.
 /tmp/ccVsQzxF.s:121: Error: Hardware capability mul32 not enabled for 
 smul.
 /tmp/ccVsQzxF.s:124: Error: Hardware capability mul32 not enabled for 
 smul.
 make[2]: *** [mem_dbg.o] Error 1

Cheers,
Julien


---End Message---
---BeginMessage---
Source: openssl
Source-Version: 1.0.0e-3

We believe that the bug you reported is fixed in the latest version of
openssl, which is due to be installed in the Debian FTP archive:

libcrypto1.0.0-udeb_1.0.0e-3_amd64.udeb
  to main/o/openssl/libcrypto1.0.0-udeb_1.0.0e-3_amd64.udeb
libssl-dev_1.0.0e-3_amd64.deb
  to main/o/openssl/libssl-dev_1.0.0e-3_amd64.deb
libssl-doc_1.0.0e-3_all.deb
  to main/o/openssl/libssl-doc_1.0.0e-3_all.deb
libssl1.0.0-dbg_1.0.0e-3_amd64.deb
  to main/o/openssl/libssl1.0.0-dbg_1.0.0e-3_amd64.deb
libssl1.0.0_1.0.0e-3_amd64.deb
  to main/o/openssl/libssl1.0.0_1.0.0e-3_amd64.deb
openssl_1.0.0e-3.debian.tar.gz
  to main/o/openssl/openssl_1.0.0e-3.debian.tar.gz
openssl_1.0.0e-3.dsc
  to main/o/openssl/openssl_1.0.0e-3.dsc
openssl_1.0.0e-3_amd64.deb
  to main/o/openssl/openssl_1.0.0e-3_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 649...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kurt Roeckx k...@roeckx.be (supplier of updated openssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Nov 2011 22:17:26 +0100
Source: openssl
Binary: openssl libssl1.0.0 libcrypto1.0.0-udeb libssl-dev libssl-doc 
libssl1.0.0-dbg
Architecture: source all amd64
Version: 1.0.0e-3
Distribution: unstable
Urgency: low
Maintainer: Debian OpenSSL Team pkg-openssl-de...@lists.alioth.debian.org
Changed-By: Kurt Roeckx k...@roeckx.be
Description: 
 libcrypto1.0.0-udeb - crypto shared library - udeb (udeb)
 libssl-dev - SSL development libraries, header files and documentation
 libssl-doc - SSL development documentation documentation
 libssl1.0.0 - SSL shared libraries
 libssl1.0.0-dbg - Symbol tables for libssl and libcrypto
 openssl- Secure Socket Layer (SSL) binary and related cryptographic tools
Closes: 649841
Changes: 
 openssl (1.0.0e-3) unstable; urgency=low
 .
   * Don't build v8 and v9 variants of sparc anymore, they're older than
 the default.  (Closes: #649841)
   * Don't build i486 optimized version, that's the default anyway, and
 it uses assembler that doesn't always work on i486.
Checksums-Sha1: 
 dbb9bba271c32a39488bf48c04a34e5ada7947f7 2178 openssl_1.0.0e-3.dsc
 4a5ab2d3118aa342836ac4da5badc065409b7ab7 87343 openssl_1.0.0e-3.debian.tar.gz
 f59f6947e3ad99b128a394edfb59b4f75b7b7d67 1192584 libssl-doc_1.0.0e-3_all.deb
 dbf3a931dc0c2c5766d57781dc0c537cb4fcbc26 679348 openssl_1.0.0e-3_amd64.deb
 83f96beacfaae156e09116485d700dda5034ec65 1143140 libssl1.0.0_1.0.0e-3_amd64.deb
 21f022aca0da2fe09b08d35f24b4b466e75dd0cc 721100 
libcrypto1.0.0-udeb_1.0.0e-3_amd64.udeb
 86b9d2156e406caaf9e0773c424f33ea8d10cfd4 1630820 libssl-dev_1.0.0e-3_amd64.deb
 3f577e5c1940efa40be507cbe62ee465287c614d 2148718 
libssl1.0.0-dbg_1.0.0e-3_amd64.deb
Checksums-Sha256: 
 bd5d9355cb9babeeaf6dd3f0d32a2f927dad7e44dbdb8390111ead1523f66f2a 2178 

Bug#648615: Latest update of nautilus in unstable has removed everything from desktop

2011-11-28 Thread JS
Thank you Josselin,

Can you point me to somewhere that explains how/whether I can restore
the earlier behavior in this version of nautilus? The right click menu
on the desktop is really useful for me.

I've googled a number of terms and the yelp page doesn't seem to mention
this. I didn't want to install gnome-tweak-tool unless absolutely necessary
as it pulls in many other packages that would make it more difficult to
roll back to the earlier nautilus, if necessary.

I will try adding a nautilus --no-default-window --sm-client-id when I get
a chance, if you think this is the cause.

thanks,
--jack

--- On Mon, 11/28/11, Josselin Mouette j...@debian.org wrote:

 From: Josselin Mouette j...@debian.org
 Subject: Re: Bug#648615: Latest update of nautilus in unstable has removed 
 everything from desktop
 To: JS jsh...@yahoo.com, 648...@bugs.debian.org
 Date: Monday, November 28, 2011, 5:10 PM
 Le dimanche 27 novembre 2011 à 19:25
 -0800, JS a écrit : 
  Are these changes in nautilus 3.0 or was some default
 configuration removed
  that allowed them to work as in 2.30?
 
 The default configuration has changed.
 
 -- 
  .''`.      Josselin Mouette
 : :' :
 `. `'
   `-




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



Bug#648615: Latest update of nautilus in unstable has removed everything from desktop

2011-11-28 Thread Michael Biebl
On 28.11.2011 23:49, JS wrote:
 Thank you Josselin,
 
 Can you point me to somewhere that explains how/whether I can restore
 the earlier behavior in this version of nautilus? The right click menu
 on the desktop is really useful for me.
 
 I've googled a number of terms and the yelp page doesn't seem to mention
 this. I didn't want to install gnome-tweak-tool unless absolutely necessary
 as it pulls in many other packages that would make it more difficult to
 roll back to the earlier nautilus, if necessary.
 
 I will try adding a nautilus --no-default-window --sm-client-id when I get
 a chance, if you think this is the cause.

Install gnome-tweak-tools: Desktop → Have file manager handle the desktop

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Processed: [/debian] Revert checking for loaded modules at startup, as this isn't necessary in newer versions ip{,6}tables-restore - instead check that there is a rules file to be loaded. Ensure at le

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 637796 + pending
Bug #637796 [iptables-persistent] firewall rules not loaded at all
Bug #638449 [iptables-persistent] iptables-persistent: rules aren't loaded at 
all
Added tag(s) pending.
Added tag(s) pending.
 thanks
Stopping processing here.

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


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



Processed: tagging 637796

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 637796 + pending
Bug #637796 [iptables-persistent] firewall rules not loaded at all
Bug #638449 [iptables-persistent] iptables-persistent: rules aren't loaded at 
all
Ignoring request to alter tags of bug #637796 to the same tags previously set
Ignoring request to alter tags of bug #638449 to the same tags previously set
 thanks
Stopping processing here.

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


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



Processed: tagging 637796

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 637796 - moreinfo
Bug #637796 [iptables-persistent] firewall rules not loaded at all
Bug #638449 [iptables-persistent] iptables-persistent: rules aren't loaded at 
all
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
 thanks
Stopping processing here.

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


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



Bug#610933: libvdeplug3 declares a conflict with libvdeplug2

2011-11-28 Thread Jonathan Nieder
Ludovico Gardenghi wrote:

 (In any case, I still can't figure out what should be the *proper* way
 for a program for dlopening a .so while providing the version number...
 should it loop over all the (infinite :-)) possible SONAMEs who offer
 compatibility for the needed interface version?

Ah!  Well, it's true that SONAMEs are not a perfect description of
whether the relevant part of the interface changed or not.

When the SONAME is bumped, programs that linked directly to the
library still are linked to the old version.  This has a few
implications:

 1. If you want to dlopen a shared library, in general one practical
way to do so is to call readlink on the .so symlink at build
time and then strip off the minor version (for example in your
configure script) and bake in the target.  This way, if later
versions of the shared library change or remove the interfaces you
are using, your program will still work.

Is there any particular reason for libvdeplug_dyn.h to use the
unversioned name instead of libvdeplug.so.3?

 2. If the SONAME of a shared library is changing very often, that
means old programs linking to the old version are going to
cause a lot of crufty old versions to be kept around on some
machines.  If the SONAME is bumping often enough for this to
be a problem, it can be useful to find ways to make the interface
a little more stable :) --- for example, by using opaque types,
and by using symbol versioning to version backward-compatible
ABI extensions.



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



Processed: limit source to desktop-file-utils, tagging 643373, tagging 575000, tagging 570309, tagging 567338 ...

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 #desktop-file-utils (0.18-1) unstable; urgency=low
 #
 #  * New upstream releases; closes: #575000.
 #- Fixes unguarded usage of variables in format strings, breaking the
 #  build; closes: #643373.
 #- Add manpages for desktop-file-install, desktop-file-validate, and
 #  update-desktop-database; closes: #284831; drop
 #  debian/desktop-file-install.8 and debian/desktop-file-validate.1.  Stop
 #  installing now useless upstream README.
 #  * postrm: allow /usr/local/share/applications to be a symlink, in which 
 case
 #it isn't rmdir-ed; closes: #567338.
 #  * rules: remove snippet to strip emacs syntax file; the default lispdir
 #install path is detected correctly even without an emacs build-dep; there
 #is an example emacs autoload config snippet at the top of
 #/usr/share/emacs/site-lisp/desktop-entry-mode.el and in the Debian bug
 #report; closes: #570309.  Drop now empty debian/TODO.
 #
 limit source desktop-file-utils
Limiting to bugs with field 'source' containing at least one of 
'desktop-file-utils'
Limit currently set to 'source':'desktop-file-utils'

 tags 643373 + pending
Bug #643373 [src:desktop-file-utils] desktop-file-utils: FTBFS: 
update-desktop-database.c:465:7: error: format not a string literal and no 
format arguments [-Werror=format-security]
Added tag(s) pending.
 tags 575000 + pending
Bug #575000 [desktop-file-utils] desktop-file-utils: new upstream release 0.16
Added tag(s) pending.
 tags 570309 + pending
Bug #570309 [desktop-file-utils] desktop-file-utils: desktop-entry-mode.el in 
package
Added tag(s) pending.
 tags 567338 + pending
Bug #567338 [desktop-file-utils] desktop-file-utils: postrm trigger fails when 
/usr/local/share/applications is a symlink.
Added tag(s) pending.
 tags 284831 + pending
Bug #284831 [desktop-file-utils] desktop-file-utils: No manpage for 
update-desktop-database
Added tag(s) pending.
 thanks
Stopping processing here.

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


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



Bug#637796: marked as done (firewall rules not loaded at all)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 00:34:21 +
with message-id e1rvbep-0008oo...@franck.debian.org
and subject line Bug#637796: fixed in iptables-persistent 0.5.3
has caused the Debian Bug report #637796,
regarding firewall rules not loaded at all
to be marked as done.

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

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


-- 
637796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: iptables-persistent
Version: 0.5.2
Severity: wishlist

Hello,

Trying to give a try to iptables-persistent, I fell onto the following 
problem: I got skipping IPv4 (no module loaded) message at startup 
(same for IPV6) whereas doing up /sbin/iptables-restore  
/etc/iptables/rules.v4 in my /etc/network/interface load my iptables 
rules at startup without any error.

The init script (load_rules) checks if /proc/net/ip_tables_names is 
present before loading the rules, meaning that tables modules must be 
loaded first. It seems that with current iptables and kernels shipped 
with Debian, it is not necessary. If I comment the part with the 
/proc/net/ip_tables_names test, my rules are loaded at startup.

man iptables states:
-t, --table table
This  option  specifies the packet matching table which the command 
should operate on. If the kernel is configured with automatic module 
loading, an attempt will be made to load the appropriate module for
that table if it is not already there.

And kernels in Wheezy seem to automatic load the appropriate modules.

I understand that iptables-persistent should take into account other 
kernels than the official Debian ones, but I still wonder if the test is 
really necessary. If modules cannot be loaded automatically and if 
/proc/net/ip_tables_names does not exist, iptables-restore will just 
fail and the result will be the same (no rules loaded).

Moreover, the initscript checks if the table modules are loaded, not if 
that other specific modules required by the rules in 
/etc/iptables/rules.v4 can be loaded (but risk is limited here if the 
rules.v4 is created with the debconf script or by 
/etc/init.d/iptables-presistent save_rules).

There might be some good reasons doing it that way, I such case, please 
disregard this bug report (and close it).

Best regards

Pascal Dormeau

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (90, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages iptables-persistent depends on:
ii  debconf [debconf-2.0] 1.5.40 Debian configuration management sy
ii  iptables  1.4.12-1   administration tools for packet fi
ii  lsb-base  3.2-27 Linux Standard Base 3.2 init scrip

iptables-persistent recommends no packages.

iptables-persistent suggests no packages.

-- Configuration Files:
/etc/init.d/iptables-persistent changed:
.. /lib/lsb/init-functions
rc=0
load_rules()
{
log_action_begin_msg Loading iptables rules
#load IPv4 rules
if [ -f /etc/iptables/rules.v4 ]; then
log_action_cont_msg  IPv4
iptables-restore  /etc/iptables/rules.v4 2 /dev/null
if [ $? -ne 0 ]; then
rc=1
fi
fi
#load IPv6 rules
if [ -f /etc/iptables/rules.v6 ]; then
log_action_cont_msg  IPv6
ip6tables-restore  /etc/iptables/rules.v6 2 /dev/null
if [ $? -ne 0 ]; then
rc=1
fi
fi
log_action_end_msg $rc
}
save_rules()
{
log_action_begin_msg Saving rules
#save IPv4 rules
if [ ! -f /proc/net/ip_tables_names ]; then
log_action_cont_msg  skipping IPv4 (no module loaded)
elif [ -x /sbin/iptables-save ]; then
log_action_cont_msg  IPv4
iptables-save  /etc/iptables/rules.v4
if [ $? -ne 0 ]; then
rc=1
fi
fi
#save IPv6 rules
if [ ! -f /proc/net/ip6_tables_names ]; then
log_action_cont_msg  skipping IPv6 (no module loaded)
elif [ -x /sbin/ip6tables-save ]; then
log_action_cont_msg  IPv6
ip6tables-save  /etc/iptables/rules.v6
if [ $? -ne 0 ]; then
rc=1
fi
fi
log_action_end_msg 

Bug#638449: marked as done (iptables-persistent: rules aren't loaded at all)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 00:34:21 +
with message-id e1rvbep-0008oo...@franck.debian.org
and subject line Bug#637796: fixed in iptables-persistent 0.5.3
has caused the Debian Bug report #637796,
regarding iptables-persistent: rules aren't loaded at all
to be marked as done.

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

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


-- 
637796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: iptables-persistent
Version: 0.5.2
Severity: critical
Tags: security
Justification: root security hole


Hi.

Since the most recent upload, rules aren't loaded any more at all:
Wed Aug 17 13:17:07 2011: Mounting local filesystems...done.
Wed Aug 17 13:17:07 2011: Activating swapfile swap...done.
Wed Aug 17 13:17:07 2011: Cleaning up temporary files
Wed Aug 17 13:17:07 2011: Loading iptables rules... skipping IPv4 (no module 
loaded)... skipping IPv6 (no module loaded)...done.
Wed Aug 17 13:17:07 2011: Setting kernel variables ...done.
Wed Aug 17 13:17:07 2011: Cleaning up ifupdown
Wed Aug 17 13:17:07 2011: Setting up resolvconf...done.
Wed Aug 17 13:17:07 2011: Setting up networking
Wed Aug 17 13:17:07 2011: Scheme unchanged.
Wed Aug 17 13:17:07 2011: Configuring network interfaces...done.


Not sure why the files you check for are not there at this point.

Marking this as critical, and root sec hole, as it can easily be just this, if
one trusts that certain rules are brought up.


Chris.


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

Kernel: Linux 3.0.0-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages iptables-persistent depends on:
ii  debconf [debconf-2.0] 1.5.41 Debian configuration management sy
ii  iptables  1.4.12-1   administration tools for packet fi
ii  lsb-base  3.2-27 Linux Standard Base 3.2 init scrip

iptables-persistent recommends no packages.

iptables-persistent suggests no packages.

-- Configuration Files:
/etc/init.d/iptables-persistent changed [not included]
/etc/iptables/rules.v4 changed [not included]
/etc/iptables/rules.v6 changed [not included]

-- debconf information:
* iptables-persistent/autosave_v6: false
* iptables-persistent/autosave_v4: false


---End Message---
---BeginMessage---
Source: iptables-persistent
Source-Version: 0.5.3

We believe that the bug you reported is fixed in the latest version of
iptables-persistent, which is due to be installed in the Debian FTP archive:

iptables-persistent_0.5.3.dsc
  to main/i/iptables-persistent/iptables-persistent_0.5.3.dsc
iptables-persistent_0.5.3.tar.gz
  to main/i/iptables-persistent/iptables-persistent_0.5.3.tar.gz
iptables-persistent_0.5.3_all.deb
  to main/i/iptables-persistent/iptables-persistent_0.5.3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 637...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Wiltshire j...@debian.org (supplier of updated iptables-persistent 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Nov 2011 23:19:39 +
Source: iptables-persistent
Binary: iptables-persistent
Architecture: source all
Version: 0.5.3
Distribution: unstable
Urgency: low
Maintainer: Jonathan Wiltshire j...@debian.org
Changed-By: Jonathan Wiltshire j...@debian.org
Description: 
 iptables-persistent - boot-time loader for iptables rules
Closes: 637796 637852 645523 650001
Changes: 
 iptables-persistent (0.5.3) unstable; urgency=low
 .
   * [09d9ae] Check for loaded modules in postinst (Closes: #637852)
   * [521544] Fix Default-Start and Default-Stop fields of the LSB header in
 the init script. Thanks to Andreas Rütten (Closes: #650001)
   * [d17b2f] Revert checking for loaded modules at startup, as this isn't
 necessary in newer versions ip{,6}tables-restore - instead check that there
 is a rules file to be loaded. Ensure at least ip{,6}table_filter is loaded
 during save (Closes: #637796)
   * [71aa52] Tidy formatting and spacing in 

Bug#643373: marked as done (desktop-file-utils: FTBFS: update-desktop-database.c:465:7: error: format not a string literal and no format arguments [-Werror=format-security])

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 00:32:30 +
with message-id e1rvbcc-00088h...@franck.debian.org
and subject line Bug#643373: fixed in desktop-file-utils 0.18-1
has caused the Debian Bug report #643373,
regarding desktop-file-utils: FTBFS: update-desktop-database.c:465:7: error: 
format not a string literal and no format arguments [-Werror=format-security]
to be marked as done.

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

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


-- 
643373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: desktop-file-utils
Version: 0.15-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening
Justification: FTBFS on amd64

Hi,

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

Relevant part:
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 
 -I/usr/lib/glib-2.0/include   -DDATADIR=\/usr/share\ 
 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE-g -O2 -fstack-protector 
 --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
 -Werror=format-security -Wall -Wchar-subscripts -Wmissing-declarations 
 -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align 
 -Wsign-compare -c `test -f 'update-desktop-database.c' || echo 
 './'`update-desktop-database.c
 update-desktop-database.c: In function 'print_desktop_dirs':
 update-desktop-database.c:465:7: error: format not a string literal and no 
 format arguments [-Werror=format-security]
 update-desktop-database.c:467:7: error: format not a string literal and no 
 format arguments [-Werror=format-security]
 cc1: some warnings being treated as errors
 
 make[3]: *** [update-desktop-database.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/desktop-file-utils_0.15-2_lsid64.buildlog

This happened because since dpkg 1.16.0 [0], hardening flags are enabled 
under various conditions.

[0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html

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

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


---End Message---
---BeginMessage---
Source: desktop-file-utils
Source-Version: 0.18-1

We believe that the bug you reported is fixed in the latest version of
desktop-file-utils, which is due to be installed in the Debian FTP archive:

desktop-file-utils_0.18-1.debian.tar.gz
  to main/d/desktop-file-utils/desktop-file-utils_0.18-1.debian.tar.gz
desktop-file-utils_0.18-1.dsc
  to main/d/desktop-file-utils/desktop-file-utils_0.18-1.dsc
desktop-file-utils_0.18-1_amd64.deb
  to main/d/desktop-file-utils/desktop-file-utils_0.18-1_amd64.deb
desktop-file-utils_0.18.orig.tar.bz2
  to main/d/desktop-file-utils/desktop-file-utils_0.18.orig.tar.bz2



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Loïc Minier l...@debian.org (supplier of updated desktop-file-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 29 Nov 2011 00:08:14 +0100
Source: desktop-file-utils
Binary: desktop-file-utils
Architecture: source amd64
Version: 0.18-1
Distribution: unstable
Urgency: low
Maintainer: Ross Burton r...@debian.org
Changed-By: Loïc Minier l...@debian.org
Description: 
 desktop-file-utils - Utilities for .desktop files
Closes: 284831 567338 570309 575000 643373
Changes: 
 desktop-file-utils (0.18-1) unstable; urgency=low
 .
   * New upstream releases; closes: #575000.
 - Fixes unguarded usage of variables in format strings, breaking the
   build; closes: #643373.
 - Add manpages for desktop-file-install, desktop-file-validate, and
   update-desktop-database; closes: #284831; drop
   debian/desktop-file-install.8 and debian/desktop-file-validate.1.  Stop
   installing now useless upstream README.
   * Update my email address in control.
   * postrm: allow 

Bug#650346: doc-base trigger during perl upgrade leaves perl installation unusable

2011-11-28 Thread Bryan Donlan
Package: perl
Version: 5.14.2-5
Severity: critical

When upgrading from 5.12 to 5.14.2-5, it is possible for doc-base
triggers to be run after unpacking perl, but prior to unpacking
perl-base or perl-modules, or the upgraded doc-base package. This
results in the apt installation job aborting (due to a failed trigger)
with a broken perl installation. The result looks a bit like this:

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs...
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 66161 files and directories currently installed.)
Preparing to replace perl-doc 5.12.4-6 (using .../perl-doc_5.14.2-5_all.deb) ...
Leaving 'diversion of /usr/bin/perldoc to /usr/bin/perldoc.stub by perl-doc'
Unpacking replacement perl-doc ...
Preparing to replace perl 5.12.4-6 (using .../perl_5.14.2-5_i386.deb) ...
Unpacking replacement perl ...
Preparing to replace libuuid-perl 0.02-4+b1 (using 
.../libuuid-perl_0.02-4+b2_i386.deb) ...
Unpacking replacement libuuid-perl ...
Selecting previously unselected package libperl5.14.
Unpacking libperl5.14 (from .../libperl5.14_5.14.2-5_i386.deb) ...
Preparing to replace speedy-cgi-perl 2.22-13+b1 (using 
.../speedy-cgi-perl_2.22-13+b2_i386.deb) ...
Unpacking replacement speedy-cgi-perl ...
Preparing to replace elinks 0.12~pre5-5 (using 
.../elinks_0.12~pre5-5+b1_i386.deb) ...
Unpacking replacement elinks ...
Preparing to replace irssi 0.8.15-4 (using .../irssi_0.8.15-4+b1_i386.deb) ...
Unpacking replacement irssi ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
/usr/bin/perl: symbol lookup error: /usr/lib/perl5/auto/UUID/UUID.so: undefined 
symbol: Perl_xs_apiversion_bootcheck
dpkg: error processing doc-base (--unpack):
 subprocess installed post-installation script returned error exit status 127
Processing triggers for menu ...
configured to not write apport reports
  Errors were encountered while processing:
 doc-base
Can't locate Digest/MD5.pm in @INC (@INC contains: /etc/perl 
/usr/local/lib/perl/5.12.4 /usr/local/share/perl/5.12.4 /usr/lib/perl5 
/usr/share/perl5 /usr/lib/perl/5.12 /usr/share/perl/5.12 
/usr/local/lib/site_perl /usr/local/lib/perl/5.12.3 
/usr/local/share/perl/5.12.3 .) at /usr/bin/debsums line 16.
BEGIN failed--compilation aborted at /usr/bin/debsums line 16.
E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; 
then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi'
E: Sub-process returned an error code
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
dpkg: dependency problems prevent configuration of libperl5.14:
 libperl5.14 depends on perl-base (= 5.14.2-5); however:
  Version of perl-base on system is 5.12.4-6.
dpkg: error processing libperl5.14 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libuuid-perl:
 libuuid-perl depends on perl-base (= 5.14.2-3); however:
  Version of perl-base on system is 5.12.4-6.
 libuuid-perl depends on perlapi-5.14.2; however:
  Package perlapi-5.14.2 is not installed.
dpkg: error processing libuuid-perl (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of irssi:
 irssi depends on libperl5.14 (= 5.14.2); however:
  Package libperl5.14 is not configured yet.
 irssi depends on perlapi-5.14.2; however:
  Package perlapi-5.14.2 is not installed.
dpkg: error processing irssi (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of elinks:
 elinks depends on libperl5.14 (= 5.14.2); however:
  Package libperl5.14 is not configured yet.
dpkg: error processing elinks (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of speedy-cgi-perl:
 speedy-cgi-perl depends on libperl5.14 (= 5.14.2); however:
  Package libperl5.14 is not configured yet.
dpkg: error processing speedy-cgi-perl (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of perl:
 perl depends on perl-base (= 5.14.2-5); however:
  Version of perl-base on system is 5.12.4-6.
 perl depends on perl-modules (= 5.14.2-5); however:
  Version of perl-modules on system is 5.12.4-6.
dpkg: error processing perl (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of perl-doc:
 perl-doc depends on perl (= 5.14.2-1); however:
  Package perl is not configured yet.
dpkg: error processing perl-doc (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of doc-base:
 doc-base depends on libuuid-perl; however:
  Package libuuid-perl is not configured yet.
dpkg: error processing doc-base (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while 

Bug#611657: executable name is confusing, software already outdated

2011-11-28 Thread Jonathan Nieder
Jeremy Lal wrote:

 Hence it is much more preferable to remove nodejs 0.2.0 from squeeze, instead
 of having an unusable and confusing version.

This report feels out-of-date.  Is it still needed, or has it been
resolved?



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



Processed: can't rely on nodejs command until it exists

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 block 611698 by 650343
Bug #611698 [nodejs] nodejs: conflicts with package node needlessly
Was not blocked by any bugs.
Added blocking bug(s) of 611698: 650343
 block 650345 by 650343
Bug #650345 [npm] npm: please consider rewriting shebangs on the fly to refer 
to nodejs name
Was not blocked by any bugs.
Added blocking bug(s) of 650345: 650343

End of message, stopping processing here.

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


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



Bug#648959: patch to make buttons work

2011-11-28 Thread Johannes Kulik

Hi,
I have a patch here, that fixes this problem for me.

Johannes

export_dynamic.patch
Description: Binary data


Bug#650314: misses .so symlink

2011-11-28 Thread Craig Small
On Mon, Nov 28, 2011 at 08:05:14PM +0100, Daniel Baumann wrote:
 libproc-dev misses the libproc-ng.so symlink in /usr/lib, thus making
 other packages fail building against it.
Damn, missed that in my debian/libproc-dev.install list
Thanks for pointing that out, it will be fixed in the new release coming
out soon to fix pgrep -u too.

Incidently, what are you using to compile against it?  We (upstream) are
looking at reworking libproc completely so it would be a good idea to
know what is using the library and also what bits you like and don't
like.

The idea is it will be better and will have a defined API.

 - Craig
--
Craig Small VK2XLZ   http://enc.com.au/  csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/  csmall at : debian.org
old fingerprint: 1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
NEW fingerprint: 5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5



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



Bug#643447: notebook: FTBFS: ui/nb_ui_interface.c:72:2: error: format not a string literal and no format arguments [-Werror=format-security]

2011-11-28 Thread Johannes Kulik

Hi,
with the attached patch the package can be build again.

Johannes

string_fomart_security_fix.patch
Description: Binary data


Processed: tagging 648959

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 648959 + patch
Bug #648959 [notebook-gtk2] notebook-gtk2: Interaction with UI doesn't trigger 
any action
Added tag(s) patch.
 thanks
Stopping processing here.

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


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



Processed: tagging 643447

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 643447 + patch
Bug #643447 [src:notebook] notebook: FTBFS: ui/nb_ui_interface.c:72:2: error: 
format not a string literal and no format arguments [-Werror=format-security]
Added tag(s) patch.
 thanks
Stopping processing here.

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


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



Bug#650349: bash: FTBFS: undefined reference to `tputs'

2011-11-28 Thread Daniel Schepler
Source: bash
Version: 4.1-3
Severity: serious

From my build log:

...
make[3]: Leaving directory 
`/home/lfs/src/debian/bash/bash-4.1/build-static/lib/tilde'
rm -f bash
gcc -L./builtins -L./lib/readline -L./lib/readline -L./lib/glob -L./lib/tilde  
-L./lib/sh -static -static -rdynamic  -g -O2 -Wall -o bash shell.o eval.o 
y.tab.o general.o make_cmd.o print_cmd.o  dispose_cmd.o execute_cmd.o 
variables.o 
copy_cmd.o error.o expr.o flags.o jobs.o subst.o hashcmd.o hashlib.o 
mailcheck.o trap.o input.o unwind_prot.o pathexp.o sig.o test.o version.o 
alias.o array.o arrayfunc.o assoc.o braces.o bracecomp.o bashhist.o bashline.o  
list.o stringlib.o locale.o findcmd.o redir.o pcomplete.o pcomplib.o syntax.o 
xmalloc.o  -lbuiltins -lglob -lsh -lreadline -lhistory -lcurses -ltilde 
bashline.o: In function `bash_groupname_completion_function':
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/bashline.c:2122: 
warning: Using 'getgrent' in statically linked applications requires at runtime 
the shared libraries from the glibc version used for linking
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/bashline.c:2119: 
warning: Using 'setgrent' in statically linked applications requires at runtime 
the shared libraries from the glibc version used for linking
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/bashline.c:2130: 
warning: Using 'endgrent' in statically linked applications requires at runtime 
the shared libraries from the glibc version used for linking
./lib/readline/libreadline.a(complete.o): In function 
`rl_username_completion_function':
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/complete.c:1977:
 warning: Using 'getpwent' in statically linked applications requires at 
runtime the shared libraries from the glibc version 
used for linking
./lib/readline/libreadline.a(tilde.o): In function `tilde_expand_word':
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/tilde.c:390:
 warning: Using 'getpwnam' in statically linked applications requires at 
runtime the shared libraries from the glibc version used for 
linking
shell.o: In function `get_current_user_info':
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/shell.c:1640: warning: 
Using 'getpwuid' in statically linked applications requires at runtime the 
shared libraries from the glibc version used for linking
./lib/readline/libreadline.a(complete.o): In function 
`rl_username_completion_function':
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/complete.c:1973:
 warning: Using 'setpwent' in statically linked applications requires at 
runtime the shared libraries from the glibc version 
used for linking
shell.o: In function `get_current_user_info':
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/shell.c:1656: warning: 
Using 'endpwent' in statically linked applications requires at runtime the 
shared libraries from the glibc version used for linking
./lib/sh/libsh.a(netopen.o): In function `_netopen6':
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/sh/../../../bash/lib/sh/netopen.c:229:
 warning: Using 'getaddrinfo' in statically linked applications requires at 
runtime the shared libraries from the glibc version used for 
linking
bashline.o: In function `bash_servicename_completion_function':
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/bashline.c:2066: 
warning: Using 'getservent' in statically linked applications requires at 
runtime the shared libraries from the glibc version used for linking
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/bashline.c:2063: 
warning: Using 'setservent' in statically linked applications requires at 
runtime the shared libraries from the glibc version used for linking
/home/lfs/src/debian/bash/bash-4.1/build-static/../bash/bashline.c:2088: 
warning: Using 'endservent' in statically linked applications requires at 
runtime the shared libraries from the glibc version used for linking
bashline.o: In function `bash_execute_unix_command':
bashline.c:(.text+0x380c): undefined reference to `tputs'
./lib/readline/libreadline.a(display.o): In function `cr':
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/display.c:2465:
 undefined reference to `tputs'
./lib/readline/libreadline.a(display.o): In function `_rl_move_cursor_relative':
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/display.c:1981:
 undefined reference to `tputs'
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/display.c:2010:
 undefined reference to `tputs'
/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/display.c:2014:
 undefined reference to `tputs'
./lib/readline/libreadline.a(display.o):/home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/display.c:2053:
 more undefined references to 

Processed: tagging 556322

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 556322 + pending
Bug #556322 [src:rlplot] FTBFS with binutils-gold
Added tag(s) pending.
 thanks
Stopping processing here.

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


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



Processed: Re: [Pkg-running-devel] Bug#650330: pytrainer: Fail to start for missing glade file

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 650330 confirmed
Bug #650330 [pytrainer] pytrainer: Fail to start for missing glade file
Added tag(s) confirmed.
 severity 650330 serious
Bug #650330 [pytrainer] pytrainer: Fail to start for missing glade file
Severity set to 'serious' from 'normal'

 thanks
Stopping processing here.

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


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



Bug#650349: bash: FTBFS: undefined reference to `tputs'

2011-11-28 Thread Jonathan Nieder
forcemerge 645113 650349
quit

Hi,

Daniel Schepler wrote:

 bashline.o: In function `bash_execute_unix_command':
 bashline.c:(.text+0x380c): undefined reference to `tputs'
 ./lib/readline/libreadline.a(display.o): In function `cr':
 /home/lfs/src/debian/bash/bash-4.1/build-static/lib/readline/../../../bash/lib/readline/display.c:2465:
  undefined reference to `tputs'

Fixed in experimental.  Thanks for testing.

Sincerely,
Jonathan



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



Processed (with 1 errors): Re: bash: FTBFS: undefined reference to `tputs'

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 645113 src:bash 4.1-3
Bug #645113 {Done: Jonathan Nieder jrnie...@gmail.com} [bash] bash: FTBFS 
with libncurses5-dev 5.9-3
Bug reassigned from package 'bash' to 'src:bash'.
Bug No longer marked as found in versions bash/4.1-3.
Bug No longer marked as fixed in versions 4.2-1~exp1.
Bug #645113 {Done: Jonathan Nieder jrnie...@gmail.com} [src:bash] bash: FTBFS 
with libncurses5-dev 5.9-3
Bug Marked as found in versions bash/4.1-3.
 fixed 645113 bash/4.2-1~exp1
Bug #645113 {Done: Jonathan Nieder jrnie...@gmail.com} [src:bash] bash: FTBFS 
with libncurses5-dev 5.9-3
Bug Marked as fixed in versions bash/4.2-1~exp1.
 merge 645113 650349
Bug#645113: bash: FTBFS with libncurses5-dev 5.9-3
Bug#650349: bash: FTBFS: undefined reference to `tputs'
Mismatch - only Bugs in same state can be merged:
Values for `done mark' don't match:
 #645113 has `done';
 #650349 has `open'


End of message, stopping processing here.

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


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



Bug#614610: alsa will not load my sound module (echo mia). NO sound.

2011-11-28 Thread Jonathan Nieder
tags 614610 + moreinfo
quit

Jonathan Nieder wrote:

 Anyway, now I'm in suspense.  Did updating the alsa driver make the
 crashes go away?  Do you have a working system now, and if so, do you
 know how it got that way (i.e., which component had to change in order
 to make it so)?

Ping?



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



Processed: Re: alsa will not load my sound module (echo mia). NO sound.

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 614610 + moreinfo
Bug #614610 [alsa-base] [alsa-base] after feb 22, 2011 Squeeze upgrade, alsa 
will not load my sound module (echo mia). NO sound.
Added tag(s) moreinfo.
 quit
Stopping processing here.

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


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



Processed: Re: bash: FTBFS: undefined reference to `tputs'

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forcemerge 645113 650349
Bug#645113: bash: FTBFS with libncurses5-dev 5.9-3
Bug#650349: bash: FTBFS: undefined reference to `tputs'
Forcibly Merged 645113 650349.


End of message, stopping processing here.

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


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



Bug#650351: bibledit-gtk: FTBFS when not building -data package

2011-11-28 Thread Aaron M. Ucko
Source: bibledit-gtk
Version: 4.4-1
Severity: serious
Justification: fails to build from source

Builds of bibledit-gtk that only cover the main architecture-dependent
package (as on the autobuilders) are failing:

  chmod: cannot access 
`debian/bibledit-gtk-data/usr/share/bibledit-gtk/usfm/Makefile.am': No such 
file or directory
  make[1]: *** [override_dh_fixperms] Error 1
  make[1]: Leaving directory `.../bibledit-gtk-4.4'
  make: *** [binary-arch] Error 2

Please conditionalize the call to chmod on its target's existence:

USFM_MAKEFILE=debian/bibledit-gtk-data/usr/share/bibledit-gtk/usfm/Makefile.am

if [ -f $(USFM_MAKEFILE) ]; then chmod 0644 $(USFM_MAKEFILE); fi

Thanks!



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



Bug#650330: marked as done (pytrainer: Fail to start for missing glade file)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 05:34:54 +
with message-id e1rvglg-0003bw...@franck.debian.org
and subject line Bug#650330: fixed in pytrainer 1.9.1-2
has caused the Debian Bug report #650330,
regarding pytrainer: Fail to start for missing glade file
to be marked as done.

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

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


-- 
650330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pytrainer
Version: 1.9.1-1
Severity: normal

After updating to this version, pytrainer doesn't start anymore.
This what i obtain launching from terminal:

--
$ pytrainer 
running pytrainer from egg installation
data_path: /usr/lib/share/pytrainer/
gettext_path: /usr/lib/share/locale
site_path: /usr/lib/lib/python2.7/site-packages

(pytr:2835): libglade-WARNING **: could not find glade file 
'/usr/lib/share/pytrainer/glade/pytrainer.glade'
Traceback (most recent call last):
  File /usr/lib/pytrainer/pytr, line 102, in module
main()
  File /usr/lib/pytrainer/pytr, line 99, in main
pytrainer = pyTrainer(None, data_path)
  File /usr/lib/pymodules/python2.7/pytrainer/main.py, line 88, in __init__
self.windowmain = Main(self._sport_service, data_path,self,self.version, 
gpxDir=self.profile.gpxdir)
  File /usr/lib/pymodules/python2.7/pytrainer/gui/windowmain.py, line 74, in 
__init__
SimpleGladeApp.__init__(self, self.data_path+glade_path, root, domain)
  File /usr/lib/pymodules/python2.7/pytrainer/gui/SimpleGladeApp.py, line 38, 
in __init__
self.glade = gtk.glade.XML(self.glade_path, main_widget_name, domain)
RuntimeError: could not create GladeXML object
--

Looking from aptitude seems that all dependencies are satisfied.

Ciao.

Cesare.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-486
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pytrainer depends on:
ii  gpsbabel   1.4.2-3 
ii  iceweasel  8.0-3   
ii  python 2.7.2-9 
ii  python-glade2  2.24.0-2
ii  python-gtk22.24.0-2
ii  python-libxml2 2.7.8.dfsg-5
ii  python-lxml2.3-0.1+b2  
ii  python-matplotlib  1.1.0-1 
ii  python-migrate 0.7.2-2 
ii  python-numpy   1:1.5.1-3   
ii  python-pysqlite2   2.6.3-2 
ii  python-scipy   0.9.0+dfsg1-1+b2
ii  python-soappy  0.12.0-4
ii  python-support 1.0.14  
ii  python-webkit  1.1.8-2 
ii  zenity 3.2.0-1 

pytrainer recommends no packages.

pytrainer suggests no packages.

-- no debconf information


---End Message---
---BeginMessage---
Source: pytrainer
Source-Version: 1.9.1-2

We believe that the bug you reported is fixed in the latest version of
pytrainer, which is due to be installed in the Debian FTP archive:

pytrainer_1.9.1-2.debian.tar.gz
  to main/p/pytrainer/pytrainer_1.9.1-2.debian.tar.gz
pytrainer_1.9.1-2.dsc
  to main/p/pytrainer/pytrainer_1.9.1-2.dsc
pytrainer_1.9.1-2_all.deb
  to main/p/pytrainer/pytrainer_1.9.1-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 650...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier bubu...@debian.org (supplier of updated pytrainer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 29 Nov 2011 05:59:53 +0100
Source: pytrainer
Binary: pytrainer
Architecture: source all
Version: 1.9.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian running development group 
pkg-running-de...@lists.alioth.debian.org
Changed-By: Christian Perrier bubu...@debian.org
Description: 
 pytrainer  - tool for logging sport activities
Closes: 650330
Changes: 
 pytrainer (1.9.1-2) unstable; urgency=low
 .
   * Move pytr back to /usr/bin. Closes: #650330
Checksums-Sha1: 
 5ab8caafa32770b76440a7b1c763bde2f36bf5e2 1909 pytrainer_1.9.1-2.dsc
 e0df5c164fd2201462995dd15039bb0143acb185 7558 pytrainer_1.9.1-2.debian.tar.gz
 

Processed: Close 646670

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 close 646670 0.8.3-1
Bug#646670: spice: FTBFS: configure: error: Package requirements (CEGUI = 
0.6.0 CEGUI  0.7.0) were not met:
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 0.8.3-1, send any further explanations to 
Mònica Ramírez Arceda mon...@probeta.net

 thanks
Stopping processing here.

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


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



Processed: Re: Bug#650056: src:mozc: orig.tar.gz missing in the main archive

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 650056 ftp.debian.org
Bug #650056 [src:mozc] src:mozc: orig.tar.gz missing in the main archive
Bug reassigned from package 'src:mozc' to 'ftp.debian.org'.
Bug No longer marked as found in versions mozc/1.2.855.102-3.
 severity 650056 serious
Bug #650056 [ftp.debian.org] src:mozc: orig.tar.gz missing in the main archive
Severity set to 'serious' from 'normal'

 merge 650071 650056
Bug#650056: src:mozc: orig.tar.gz missing in the main archive
Bug#650071: mozc_1.2.855.102.orig.tar.gz missing in main
Merged 650056 650071.

 thanks
Stopping processing here.

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


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



Bug#650071: mozc_1.2.855.102.orig.tar.g missing in main

2011-11-28 Thread Nobuhiro Iwamatsu
Hi,

2011/11/28 Luca Falavigna dktrkr...@debian.org:
 Unfortunately true, due to a bug in dak.
 A fix is being worked on for future cases, a workaround for this issue
 would be uploading a new version with a bit-by-bit identical
 .orig.tar.gz, but with a different version (e.g.
 mozc_1.2.855.102+main.orig.tar.gz), or wait for a new upstream
 release.


OK, I will upload new version (mozc_1.2.855.102+main) of mozc.
Thanks for your advice!

Best regards,
  Nobuhiro
-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6



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



Bug#649905: blackbox: FTBFS: libbt0.symbols 64-bit specific

2011-11-28 Thread d+deb
tags 649905 + pending
thanks

fix package uploaded to mentors.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature


Processed: tagging 649461

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 649461 + pending
Bug #649461 [src:foo-yc20] foo-yc20: FTBFS: cc1plus: error: unrecognized 
command line option -march=native
Added tag(s) pending.
 thanks
Stopping processing here.

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


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



Processed: Re: blackbox: FTBFS: libbt0.symbols 64-bit specific

2011-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 649905 + pending
Bug #649905 [src:blackbox] blackbox: FTBFS: libbt0.symbols 64-bit specific
Added tag(s) pending.
 thanks
Stopping processing here.

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


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



Bug#556322: marked as done (FTBFS with binutils-gold)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 07:49:59 +
with message-id e1rvirz-0001xd...@franck.debian.org
and subject line Bug#556322: fixed in rlplot 1.4-2
has caused the Debian Bug report #556322,
regarding FTBFS with binutils-gold
to be marked as done.

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

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


-- 
556322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: rlplot
Version: 1.4-1
Severity: minor
User: peter.fritzs...@gmx.de
Usertags: no-add-needed

Tried to build your package and it fails to build with GNU binutils-gold. The
important difference is that --no-add-needed is the default behavior of of GNU
binutils-gold. Please provide all needed libraries to the linker when building
your executables.

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking

g++ -L/usr/share/qt4/lib -L/usr/X11R6/lib -lQtCore -lQtGui -lQtNetwork -o 
rlplot moc_QT_Spec.o QT_Spec.o Output.o Utils.o UtilObj.o TheDialog.o rlplot.o 
Fileio.o PropertyDlg.o spreadwi.o Export.o PlotObs.o Axes.o ODbuttons.o 
mfcalc.o rlp_math.o use_gui.o reports.o  -lX11 -lm
/usr/bin/ld: QT_Spec.o: in function RLPserver::RLPserver(QObject*, 
GraphObj*):QT_Spec.cpp(.text+0x5a0d): error: undefined reference to 
'pthread_create'
/usr/bin/ld: QT_Spec.o: in function RLPserver::RLPserver(QObject*, 
GraphObj*):QT_Spec.cpp(.text+0x5bcd): error: undefined reference to 
'pthread_create'
collect2: ld returned 1 exit status
make[3]: *** [rlplot] Error 1


---End Message---
---BeginMessage---
Source: rlplot
Source-Version: 1.4-2

We believe that the bug you reported is fixed in the latest version of
rlplot, which is due to be installed in the Debian FTP archive:

rlplot_1.4-2.debian.tar.gz
  to main/r/rlplot/rlplot_1.4-2.debian.tar.gz
rlplot_1.4-2.dsc
  to main/r/rlplot/rlplot_1.4-2.dsc
rlplot_1.4-2_amd64.deb
  to main/r/rlplot/rlplot_1.4-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 556...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olly Betts o...@survex.com (supplier of updated rlplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Nov 2011 06:41:40 +
Source: rlplot
Binary: rlplot
Architecture: source amd64
Version: 1.4-2
Distribution: sid
Urgency: low
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Olly Betts o...@survex.com
Description: 
 rlplot - Generate publication quality graphs
Closes: 556322 610150 618048
Changes: 
 rlplot (1.4-2) unstable; urgency=low
 .
   * QA upload.
 + Orphaned, so set maintainer to QA group.
   * New patch fix-ftbfs-with-gold.patch from Ubuntu to fix FTBFS with gold or
 --no-add-needed. (Closes: #556322)
   * New patch fix-ftbfs-with-qt4.7.patch from Ubuntu which replaces 'QString
 foo(0);' with 'QString foo;' to fix FTBFS with Qt 4.7.
 (Closes: #618048, #610150)
   * Clear executable bit on /usr/share/pixmaps/RLPlot.xpm, fixing lintian
 warning.
   * debian/rules: Rewrite to use dh.
   * debian/copyright: Update to point to GPL-2; update copyright holders and
 years.
   * Don't package upstream README - debian/copyright has the licence
 information, and the details about how to build it aren't relevant to
 those who have installed a binary package.
   * debian/rlplot.1: Fix typo; fix hyphens to be dashes (fixes lintian
 warning).
   * debian/rlplot.desktop: Remove deprecated Encoding field.
Checksums-Sha1: 
 4713f419b40f8a179078a6a90da04e3834540ed8 1723 rlplot_1.4-2.dsc
 86fb8c388bb9c0fb5cc478cf3c6ecf419cd246c2 5354 rlplot_1.4-2.debian.tar.gz
 83e149f91ac004db956eb857abec26e3e45c6dba 1019024 rlplot_1.4-2_amd64.deb
Checksums-Sha256: 
 faa751112f10f2af382fadc36cff3f9e3012719e6a41f3bc682ac09e0dc6459e 1723 
rlplot_1.4-2.dsc
 44e42b0975a8714cffe75dbbbe6add3ae98e241aa8ec8a9c13944e8cb08fcb25 5354 
rlplot_1.4-2.debian.tar.gz
 f2732ffd90983bacddd5b68646be70d1c8e8c847d9b2ffdc39faf8395b6bae0f 1019024 
rlplot_1.4-2_amd64.deb
Files: 
 64dfc1cc1df7ed09de58d7ad5394aaaf 1723 math optional rlplot_1.4-2.dsc
 4b637b3c51f23935140702546658c1aa 5354 math optional rlplot_1.4-2.debian.tar.gz
 

Bug#618048: marked as done (rlplot: FTBFS: QT_Spec.cpp:1190:16: error: call of overloaded 'QString(int)' is ambiguous)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 07:49:59 +
with message-id e1rvirz-0001xo...@franck.debian.org
and subject line Bug#618048: fixed in rlplot 1.4-2
has caused the Debian Bug report #618048,
regarding rlplot: FTBFS: QT_Spec.cpp:1190:16: error: call of overloaded 
'QString(int)' is ambiguous
to be marked as done.

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

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


-- 
618048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: rlplot
Version: 1.4-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110313 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++ -I/usr/include/qt4/Qt -I/usr/include/qt4 -pipe -O2 -o QT_Spec.o -c 
 QT_Spec.cpp
 In file included from QT_Spec.h:19:0,
  from QT_Spec.cpp:26:
 rlplot.h:392:2: warning: 'typedef' was ignored in this declaration
 QT_Spec.cpp: In function 'int ExportQPixmap(GraphObj*, char*, int)':
 QT_Spec.cpp:57:30: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:57:30: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:57:30: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:72:48: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'void OpenExportName(GraphObj*, char*)':
 QT_Spec.cpp:321:52: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'bool YesNoBox(char*)':
 QT_Spec.cpp:347:41: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'int YesNoCancelBox(char*)':
 QT_Spec.cpp:358:41: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'bool ReadCB(char*, GraphObj*)':
 QT_Spec.cpp:854:37: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'void* ServerCB(void*)':
 QT_Spec.cpp:895:24: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:896:24: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:897:24: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In destructor 'RLPserver::~RLPserver()':
 QT_Spec.cpp:994:25: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'void EmptyClip()':
 QT_Spec.cpp:1119:24: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'bool com_GetTextExtentW(wchar_t*, int*, int*, int, 
 TextDEF*, QPainter*)':
 QT_Spec.cpp:1190:16: error: call of overloaded 'QString(int)' is ambiguous
 /usr/include/qt4/QtCore/qstring.h:428:43: note: candidates are: 
 QString::QString(const QByteArray)
 /usr/include/qt4/QtCore/qstring.h:426:43: note: 
 QString::QString(const char*)
 /usr/include/qt4/QtCore/qstring.h:728:8: note: 
 QString::QString(const QString)
 /usr/include/qt4/QtCore/qstring.h:106:5: note: 
 QString::QString(QChar)
 /usr/include/qt4/QtCore/qstring.h:105:14: note: 
 QString::QString(const QChar*)
 QT_Spec.cpp: In function 'bool com_TextOutW(int, int, wchar_t*, TextDEF*, 
 QPainter*, anyOutput*)':
 QT_Spec.cpp:1278:15: error: call of overloaded 'QString(int)' is ambiguous
 /usr/include/qt4/QtCore/qstring.h:428:43: note: candidates are: 
 QString::QString(const QByteArray)
 /usr/include/qt4/QtCore/qstring.h:426:43: note: 
 QString::QString(const char*)
 /usr/include/qt4/QtCore/qstring.h:728:8: note: 
 QString::QString(const QString)
 /usr/include/qt4/QtCore/qstring.h:106:5: note: 
 QString::QString(QChar)
 /usr/include/qt4/QtCore/qstring.h:105:14: note: 
 QString::QString(const QChar*)
 QT_Spec.cpp: In function 'bool ProcMenuEvent(int, QWidget*, anyOutput*, 
 GraphObj*)':
 QT_Spec.cpp:1907:49: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp: In function 'QMenu* MkToolMenu(QMenu*, QWidget*, OutputQT*, 
 GraphObj*)':
 QT_Spec.cpp:2647:2: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:2649:2: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:2650:2: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:2651:2: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:2652:2: warning: deprecated conversion from string constant to 
 'char*'
 QT_Spec.cpp:2653:2: 

Bug#649461: marked as done (foo-yc20: FTBFS: cc1plus: error: unrecognized command line option -march=native)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 07:47:38 +
with message-id e1rvipi-ov...@franck.debian.org
and subject line Bug#649461: fixed in foo-yc20 1.3.0-3
has caused the Debian Bug report #649461,
regarding foo-yc20: FTBFS: cc1plus: error: unrecognized command line option 
-march=native
to be marked as done.

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

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


-- 
649461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: foo-yc20
Version: 1.3.0-2
Severity: serious
Justification: fails to build from source
Tags: patch

Hi,

foo-yc20 FTBFS on some architecture.

 http://buildd.debian.org/status/package.php?p=foo-yc20suite=sid
 http://buildd.debian-ports.org/status/package.php?p=foo-yc20suite=sid

-
make[2]: Leaving directory
`/build/buildd-foo-yc20_1.3.0-2-alpha-so4dXd/foo-yc20-1.3.0'
make[1]: Leaving directory
`/build/buildd-foo-yc20_1.3.0-2-alpha-so4dXd/foo-yc20-1.3.0'
   debian/rules override_dh_auto_build
make[1]: Entering directory
`/build/buildd-foo-yc20_1.3.0-2-alpha-so4dXd/foo-yc20-1.3.0'
dh_auto_build -- PREFIX=/usr
make[2]: Entering directory
`/build/buildd-foo-yc20_1.3.0-2-alpha-so4dXd/foo-yc20-1.3.0'
g++ src/foo-yc20.cpp -O3 -mtune=native -march=native -mfpmath=sse
-ffast-math -ftree-vectorize  -fPIC -DVERSION=1.3.0 -I/usr/lib/faust
-Isrc/ -Iinclude/ -DPREFIX=/usr -Wall  -c -o src/foo-yc20.o
cc1plus: error: unrecognized command line option -march=native
cc1plus: error: unrecognized command line option -mfpmath=sse
make[2]: *** [src/foo-yc20.o] Error 1
make[2]: Leaving directory
`/build/buildd-foo-yc20_1.3.0-2-alpha-so4dXd/foo-yc20-1.3.0'
dh_auto_build: make -j1 PREFIX=/usr returned exit code 2
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory
`/build/buildd-foo-yc20_1.3.0-2-alpha-so4dXd/foo-yc20-1.3.0'
make: *** [build] Error 2
-

-march=native option can not use by all architecture.
Moreover, -mfpmath=sse option is only for Intel architecture.

I created a patch which reivse this problem.
Please check patch and allpy.

Best regards,
 Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
diff --git a/Makefile.orig b/Makefile
index d8f4aed..a3d295d 100644
--- a/Makefile.orig
+++ b/Makefile
@@ -17,7 +17,7 @@ ifeq ($(CFLAGS),)
 ifeq ($(shell uname), Darwin)
 CFLAGS=-O3 -ffast-math -ftree-vectorize -arch ppc -arch i386 -arch x86_64
 else
-CFLAGS=-O3 -mtune=native -march=native -mfpmath=sse -ffast-math -ftree-vectorize 
+CFLAGS=-O2 -ffast-math -ftree-vectorize 
 endif
 endif
 
---End Message---
---BeginMessage---
Source: foo-yc20
Source-Version: 1.3.0-3

We believe that the bug you reported is fixed in the latest version of
foo-yc20, which is due to be installed in the Debian FTP archive:

foo-yc20_1.3.0-3.debian.tar.gz
  to main/f/foo-yc20/foo-yc20_1.3.0-3.debian.tar.gz
foo-yc20_1.3.0-3.dsc
  to main/f/foo-yc20/foo-yc20_1.3.0-3.dsc
foo-yc20_1.3.0-3_amd64.deb
  to main/f/foo-yc20/foo-yc20_1.3.0-3_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 649...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessio Treglia ales...@debian.org (supplier of updated foo-yc20 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 29 Nov 2011 08:33:38 +0100
Source: foo-yc20
Binary: foo-yc20
Architecture: source amd64
Version: 1.3.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Alessio Treglia ales...@debian.org
Description: 
 foo-yc20   - YC-20 organ emulation
Closes: 649461
Changes: 
 foo-yc20 (1.3.0-3) unstable; urgency=low
 .
   * Get rid of Intel optimizations and -m{tune,arch}=native
 flags (Closes: #649461).
Checksums-Sha1: 
 91d3b1fff41ac75aaa6abba0ac56fb82e3316f0d 1448 foo-yc20_1.3.0-3.dsc
 643e5ba8e3a06d010bb143d1ccb9e7f386b94488 4653 foo-yc20_1.3.0-3.debian.tar.gz
 c21be9ed8d2e6ef84e2272470ac931892ed68794 265600 foo-yc20_1.3.0-3_amd64.deb
Checksums-Sha256: 
 38b4863634331df570545001304ff9e07f307bf3373b429a8b76a51169b0a879 1448 
foo-yc20_1.3.0-3.dsc
 e1ee7127d16e8f3325b16de39f04d70496c936134743a8a02a6502d9e433941d 4653 
foo-yc20_1.3.0-3.debian.tar.gz
 

Bug#650359: segmentation fault gmpc

2011-11-28 Thread Dmitry E. Oboukhov
Package: gmpc
Version: 11.8.16-1
Severity: grave

Hi!

I've just upgraded gmpc upto 11.8.16-1. It always crashes.
The bug is reproducible in a few hosts (desktop, notebook, the other
desktop).

Backtrace:

apache:[~]$ gdb gmpc core
GNU gdb (GDB) 7.3-debian
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/gmpc...Reading symbols from 
/usr/lib/debug/usr/bin/gmpc...done.
done.
[New LWP 22022]
[New LWP 22050]

warning: Can't read pathname for load map: Ошибка ввода/вывода.
[Thread debugging using libthread_db enabled]
Core was generated by `gmpc'.
Program terminated with signal 11, Segmentation fault.
#0  0x0046016c in gmpc_easy_handler_get_data_as_string (
handle=0x15158b0) at Tools/gmpc_easy_download.c:502
502 Tools/gmpc_easy_download.c: Нет такого файла или каталога.
in Tools/gmpc_easy_download.c
(gdb) bt
#0  0x0046016c in gmpc_easy_handler_get_data_as_string (
handle=0x15158b0) at Tools/gmpc_easy_download.c:502
#1  0x00470f3d in gmpc_provider_lyr_db_handle_download (d=0x1631d40, 
status=optimized out, handle=optimized out, self=0x12bf1c0)
at Providers/LyrDB.c:459
#2  _gmpc_provider_lyr_db_handle_download_gmpc_async_download_callback_vala (
handle=optimized out, status=optimized out, p=0x1631d40, 
self=0x12bf1c0) at Providers/LyrDB.c:495
#3  0x0045f85d in temp_callback (handle=optimized out, 
status=GEAD_DONE, user_data=0x12ce570) at Tools/gmpc_easy_download.c:611
#4  0x0045fbf0 in gmpc_easy_async_callback (session=optimized out, 
msg=optimized out, data=0x15158b0) at Tools/gmpc_easy_download.c:448
#5  0x7f19207a936a in ?? () from /usr/lib/libsoup-2.4.so.1
#6  0x7f19207a95c0 in ?? () from /usr/lib/libsoup-2.4.so.1
#7  0x7f19207a9c13 in ?? () from /usr/lib/libsoup-2.4.so.1
#8  0x7f191db9fedd in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#9  0x7f191dba06b8 in ?? () from /lib/libglib-2.0.so.0
#10 0x7f191dba0cfa in g_main_loop_run () from /lib/libglib-2.0.so.0
#11 0x7f191f4fb717 in gtk_main ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x00428754 in main (argc=1, argv=0x7fff0545c348) at main.c:592
(gdb)
-- 

. ''`.   Dmitry E. Oboukhov
: :’  :   email: un...@debian.org jabber://un...@uvw.ru
`. `~’  GPGKey: 1024D / F8E26537 2006-11-21
  `- 1B23 D4F8 8EC0 D902 0555  E438 AB8C 00CF F8E2 6537


signature.asc
Description: Digital signature


Bug#611657: marked as done (executable name is confusing, software already outdated)

2011-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Nov 2011 08:52:59 +0100
with message-id 4ed48f5b.8020...@edagames.com
and subject line Re: Bug#611657: executable name is confusing, software already 
outdated
has caused the Debian Bug report #611657,
regarding executable name is confusing, software already outdated
to be marked as done.

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

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


-- 
611657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nodejs
Version: 0.2.0-1
Severity: serious
Tags: squeeze

nodejs version 0.2.0 has its executable renamed to /usr/bin/nodejs [1],
and while it was all right for testing purposes, it is now not
acceptable :
 * it will confuse users, and force them to add /usr/local/bin/node link
 * nodejs is only useful with external modules, they won't work unless
   that link is added.

Moreover, most external modules depend on version 0.2.6 (upstream stable
branch version), for that reason users will more likely use nodejs package
from testing or backports (actually experimental [2]).
Hence it is much more preferable to remove nodejs 0.2.0 from squeeze, instead
of having an unusable and confusing version.

Concerned source packages are nodejs 0.2.0-1 and coffeescript 0.7.0-1.
The maintainer Geza Kovacs of the latter has agreed upon removal of its
package from squeeze.

Regards,
Jérémy Lal

[1]
http://bugs.debian.org/597571
[2]
http://packages.debian.org/changelogs/pool/main/n/nodejs/current/changelog



---End Message---
---BeginMessage---
On 29/11/2011 02:37, Jonathan Nieder wrote:
 Jeremy Lal wrote:
 
 Hence it is much more preferable to remove nodejs 0.2.0 from squeeze, instead
 of having an unusable and confusing version.
 
 This report feels out-of-date.  Is it still needed, or has it been
 resolved?

It's been resolved before squeeze release, hence closing.

Jérémy.


---End Message---