Bug#620206: shared files

[Ralf Treinen]

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/libmpl.so.1
  /usr/lib/libmpl.so.1.1.0
  /usr/lib/libopa.so.1
  /usr/lib/libopa.so.1.0.0


-Ralf.



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

Bug#620213: crash on sonic spinball

[Joey Hess]

Package: dgen
Version: 1.23-10
Severity: normal

Game crashes in "boot" after SEGA banner.

Backtrace from unstripped binary is not very helpful:

Program received signal SIGSEGV, Segmentation fault.
0x080c8514 in memoryWrite109 ()
(gdb) bt
#0  0x080c8514 in memoryWrite109 ()
#1  0x in ?? ()

Oddly, I remember it worked ok on this game a few years ago.

I tried building with both --without-musa and --without-star,
and it crashes both ways, so whatever the problem is, it's not
in the CPU cores. Appears to be in mz80 actually.

Hmm.. This binary works ok:

http://archive.debian.net/etch/i386/dgen/download

Afaik, nothing important changed between -9 and -10. The two binaries
link to the same libaries too. So this must be a build environment
change causing the crash. I tried building with etch's nasm, which didn't
help, and with sid's gcc-4.3, which also didn't help.

Hmm, adding -cs to the makez80 command line fixes the crash,
but the resulting dgen fails to play any sounds in this game (other
games seem ok).

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

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dgen depends on:
ii  libc6 2.11.2-11  Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.5.2-6  GCC support library
ii  libgl1-mesa-glx [libgl1]  7.10-4 A free implementation of the OpenG
ii  libsdl1.2debian   1.2.14-6.1 Simple DirectMedia Layer
ii  libstdc++64.5.2-6The GNU Standard C++ Library v3

dgen recommends no packages.

dgen suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#620209: make: inconsistant description of ifdef directive behavior

[Jonathan Nieder]

reassign 620209 make-doc 3.81-5
tags 620209 + upstream
quit

Hi!

Britton Leo Kerin wrote:
[out of order for convenience]

> The manual says:
>
>   ifdef variable-name

I assume you mean the manual shown with "info make"?

[...]
>  The ifdef form takes the name of a variable as its argument, not a
>  reference to a variable. The value of that variable has a non-empty 
> value,
>  the text-if-true is effective; otherwise, the text-if-false, if any, is
>  effective.
[...]
> The second sentence of the first paragraph has a grammar error, it lools like
> it should read "If the vale of that variable..."
[...]
>   Note that ifdef only tests whether a variable has a value. It does not
>   expand the variable to see if that value is nonempty. Consequently, 
> tests
>   using ifdef return true for all definitions except those like foo =. To
>   test for an empty value, use ifeq ($(foo),). For example, 
>
>
> The paragraph that begins 'Note that ifdef only tests...' seems to be wrong in
> a suble way.  Although it is correct for recusively expanded variables, simply
> expanded variables that are assigned values that expand empty can still be
> undefined.

Thanks for reporting; I'm passing your report on to the list of people
interested in the make-doc package that accompanies Debian.  I'd
suggest also reporting this to the upstream bug reporting address
shown by "make --help".

Regards,
Jonathan



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

Bug#620202: ITP: lcrt -- Linux remote login tool

[Andrei Popescu]

On Jo, 31 mar 11, 08:58:27, Asias He wrote:
> 
> Lcrt is a Linux Remote Login Tool. Some linuxer think there is not
> a good terminal like SecureCRT(may be there is but I don't known), 
> so I write one, here it is.

apt-cache show putty

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Bug#620189: perl: please include multiarch lib dirs at build time

[Niko Tyni]

forwarded 620189 http://rt.perl.org/rt3/Ticket/Display.html?id=86854
thanks

On Wed, Mar 30, 2011 at 02:41:25PM -0700, Steve Langasek wrote:
> Package: perl
> Version: 5.10.1-17
> Severity: normal
> Tags: patch
> User: vor...@debian.org
> Usertags: multiarch

> Please consider applying the attached patch to perl in Debian; this (or
> something like it) is needed to let perl build on a system whose libraries
> are converted to use the multiarch directories.  Since this transition is
> expected to start in Debian unstable as soon as dpkg 1.16.0 is uploaded, it
> would be great if perl could be fixed for this early.

Thanks! I see there's some discussion about this upstream to make the
soon-to-be-released 5.14.0 build on such systems.

Your patch seems fine for Debian/Ubuntu purposes until a more generic
solution is implemented upstream.

Dominic, do you have the time to push this in sid soon? I'd do it myself
but I'll be offline most of the upcoming weekend.
-- 
Niko Tyni   nt...@debian.org



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

Bug#620212: libmpd should empty dependency_libs at build time per Debian policy 10.2

[Micah Gersten]

Package: libmpd
Version: 0.20.0-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu natty ubuntu-patch



*** /tmp/tmp2pXHf7
In Ubuntu, the attached patch was applied to achieve the following:

This prevents FTBFS for libmpd's rdepends with multiarch w/out needing a 
rebuild after multiarch is implemented.


Thanks for considering the patch.


-- System Information:
Debian Release: squeeze/sid
  APT prefers natty-updates
  APT policy: (500, 'natty-updates'), (500, 'natty-security'), (500, 
'natty-proposed'), (500, 'natty-backports'), (500, 'natty')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-7-generic (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u libmpd-0.20.0/debian/changelog libmpd-0.20.0/debian/changelog
diff -u libmpd-0.20.0/debian/rules libmpd-0.20.0/debian/rules
--- libmpd-0.20.0/debian/rules
+++ libmpd-0.20.0/debian/rules
@@ -9,6 +9,12 @@
 %:
 	dh --with quilt $@
 
+override_dh_auto_install:
+	dh_auto_install
+	for file in debian/tmp/usr/lib/*.la; do \
+sed -i "/dependency_libs/ s/'.*'/''/" $$file ; \
+done
+
 override_dh_installdocs:
 	dh_installdocs
 	rm -f debian/$(LIB_NAME)/usr/share/doc/$(LIB_NAME)/README

Bug#598765: debian-installer: FTBFS on alpha: needs mirror update?

[Witold Baryluk]

Well,

there is no squeezy for alpha, it was not released with other architectures,
and it will probably not be relesead even after normal release.

debian-alpha team is targeting re-release on normal schedule of Debian wheezy.
But this is not yet decided oficially, so currently only unstable/sid
is available for alpha (and lenny and experimental of course).

Would be nice if debian-installer from sid, would use sid distribution
for building. Currently according to logs, package is from sid,
but it have hardcoded squeezy strings in build process.

Neverthless currently building debian-installer is slightly
pointless for a while, because of udev issues, which will be fixed
when eglibc 2.13 will enter unstable. (it already is fixed for example
in libc6.1 2.13-0exp5 for experimental).

Regards,
Witek


-- 
Witold Baryluk


signature.asc
Description: Digital signature

Bug#615121: #615121: iptables --localtz option of -m time not working

[Damyan Ivanov]

retitle 615121 iptables --localtz option of -m time not working with hardware 
clock in UTC
thanks

-=| Jan Engelhardt, Thu, Mar 31, 2011 at 03:08:40AM +0200 |=-
> 
> >Not sure if it matters, but the hardware clock is using UTC (i.e. 
> >/etc/default/rcS contains "UTC=yes").
> 
> When the xt_time kernel module is loaded, it prints the current timezone 
> the kernel is operating with - and this is what xt_time will be using 
> when doing localtz comparisons.

Thanks for the reply.

Indeed, there is this message in dmesg:

xt_time: kernel timezone is -

I have set the hardware clock to use the local timezone and it changed 
to

xt_time: kernel timezone is +0300

It seems to fix the problem, but I wonder what would happen at the 
next DST change. I guess it would require to shut down the firewall, 
reload xt_time and restart the firewall so that it picks up the 
correct timezone (If the kernel changes its at all. I have never used 
UTC=no before). Still a suboptimal solution?


signature.asc
Description: Digital signature

Bug#620211: make: it would be nice to get -R behavior using a directive inside a Makefile

[Britton Leo Kerin]

Package: make
Version: 3.81-5
Severity: wishlist


Please note I'm actually running my own compiled version of 3.82.  I just find
the debian bug reporting interface a little too easy, and this is an upstream
wishlist item :)

The subject pretty much says it.  What I do now is:

HAVE_NO_BUILTIN_VARIABLES_OPTION := $(shell echo $(MAKEFLAGS) | grep -e R)
ifndef HAVE_NO_BUILTIN_VARIABLES_OPTION
   $(error This makefile requires use of the -R/--no-builtin-variables option)
endif

which forces users of the makefile to do it.  But there should be a way to just
do this from with the Makefile.  The implicit rules and default variable values
represent the cruft of a bygone era and aren't worth all the trouble and
confusion they cause.  And they were an ironic and bad idea to begin with,
since by definition and convention firm enought to merit them is just
going to get put in somebodies IDE anyway: make is useful for the
strange stuff and the custom work.

-- System Information:
Debian Release: 5.0.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

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

Versions of packages make depends on:
ii  libc6   2.7-18lenny7 GNU C Library: Shared libraries

make recommends no packages.

Versions of packages make suggests:
pn  make-doc   (no description available)

-- no debconf information



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

Bug#620210: pu: package samba/2:3.5.6~dfsg3-squeeze3

[Christian Perrier]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu

(I sent the same request manually on March 19th. However, after more
thinking, I think that using a bug report makes it easier for the
release team to track things. No intent from me to put pressure on you
folks.just trying to play nicely.)

Hello,

The samba packaging team would like to upload a new version of samba
3.5.6 in squeeze (that would be 2:3.5.6~dfsg-3squeeze3).

That version fixes three/four important bugs that make samba unusable
in some situations (the first two are likely to be the same bug):

- Upstream bug 7567: printing from Windows 7 fails with 0x03e6.
  Closes: #617429
- Upstream bug 6727: printer device settings not saved for normal
  domain users. Closes: #611177   
- Upstream bug : winbind leaks gids with idmap ldap backend
  Closes: #613624
- Upstream bug 7880: rpcclient deldriver does not remove drivers
  from all architectures.


The first two are fixes by patches in attached
bug_611177-617429_upstream_7567.tar.bz2

Next is fixed by the twp patches in
bug_613624_upstream_.tar.bz2. Adam indeed already acked this one.

Last bug is fixed by the patch in upstream_7880.tar.bz2. This one is
severity important for anyone running a print server with samba 3.5.6.

Those patches were cherry-picked from upstream's 3.5.8 released
version (these bugs are confirmed fixed in samba 3.5.8).




-- System Information:
Debian Release: wheezy/sid
Architecture: i386 (i686)

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


bug_611177-617429_upstream_7567.tar.bz2
Description: BZip2 compressed data


bug_613624_upstream_.tar.bz2
Description: BZip2 compressed data


upstream_7880.tar.bz2
Description: BZip2 compressed data

Bug#620209: make: inconsistant description of ifdef directive behavior

[Britton Leo Kerin]

Package: make
Version: 3.81-5
Severity: normal


The manual says:

  ifdef variable-name

 The ifdef form takes the name of a variable as its argument, not a
 reference to a variable. The value of that variable has a non-empty value,
 the text-if-true is effective; otherwise, the text-if-false, if any, is
 effective. Variables that have never been defined have an empty value. The
 text variable-name is expanded, so it could be a variable or function that
 expands to the name of a variable. For example:

  bar = true
  foo = bar
  ifdef $(foo)
  frobozz = yes
  endif

  The variable reference $(foo) is expanded, yielding bar, which is
  considered to be the name of a variable. The variable bar is not
  expanded, but its value is examined to determine if it is non-empty.

  Note that ifdef only tests whether a variable has a value. It does not
  expand the variable to see if that value is nonempty. Consequently, tests
  using ifdef return true for all definitions except those like foo =. To
  test for an empty value, use ifeq ($(foo),). For example, 

The second sentence of the first paragraph has a grammar error, it lools like
it should read "If the vale of that variable..."

The paragraph that begins 'Note that ifdef only tests...' seems to be wrong in
a suble way.  Although it is correct for recusively expanded variables, simply
expanded variables that are assigned values that expand empty can still be
undefined.

-- System Information:
Debian Release: 5.0.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

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

Versions of packages make depends on:
ii  libc6   2.7-18lenny7 GNU C Library: Shared libraries

make recommends no packages.

Versions of packages make suggests:
pn  make-doc   (no description available)

-- no debconf information



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

Bug#264130: bind9 crashed with strange error

[Witold Baryluk]

Hi,


Can you reproduce problem under any (same or other) version of bind9?

There many possible explenations of this bug, but most likly
it is because of some unreleated bug in this particular (release candidat)
version of bind.

Considering that in lenny we have version 9.6, and in squeezy 9.7.3,
this bug should be probably soon be closed, if
original reporter will not answer.

Regards,
Witek


-- 
Witold Baryluk


signature.asc
Description: Digital signature

Bug#620109: Policy §3.5 (on Pre-Depends) does not reflect actual practice

[Raphael Hertzog]

On Wed, 30 Mar 2011, Jonathan Nieder wrote:
> I like your proposed alternative.  Maybe the policy could say that you
> "should" (in the policy sense) thoroughly analyze the consequences and
> alternatives before adding pre-depends, and that one way to do so (in
> a friendly advice sense) is to ask on debian-devel?

Yes.

On Wed, 30 Mar 2011, Jonathan Nieder wrote:
> So, new proposal.  Before adding new Pre-Depends,
> 
>  A. there should be a discussion on debian-devel or debian-release,
> to get eyeballs on the change and spot problems and easier
> alternatives;

Drop debian-release, it's not a general discussion list.

>  B. debian-devel or debian-devel-announce should be at least notified,
> so other Debian developers can factor it into any plans they have
> for changing their own package relationships.

I don't think debian-devel-announce is warranted.

> In particular, this proposal would drop the requirement of consensus.
> Package maintainers generally know what's best; if not, there are
> other ways to deal with that (e.g., convincing them, or referring the
> issue to the ctte if the maintainer is beyond convincing).

Agreed.

In general I'm okay with reformulating section 3.5 to make it more obvious
why the review on -devel is a good idea.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
  ▶ http://RaphaelHertzog.fr (Français)



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

Bug#620208: i386 build is out of date

[Joey Hess]

Package: dgen
Version: 1.23-10
Severity: normal

Tony, thank you for taking over maintenance of dgen.

Unfortunatly, you only uploaded an amd64 build, so the archive
still has a i386 build with me listed as the maintainer. (Since non-free
is not autobuilt.)

Also, both versions still list my old git repository as the current
source repo for dgen. It's no longer there, but if you would like a copy
of the git repository for historical purposes, I can send one.

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

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dgen depends on:
ii  libc6 2.11.2-11  Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.5.2-6  GCC support library
ii  libgl1-mesa-glx [libgl1]  7.10-4 A free implementation of the OpenG
ii  libsdl1.2debian   1.2.14-6.1 Simple DirectMedia Layer
ii  libstdc++64.5.2-6The GNU Standard C++ Library v3

dgen recommends no packages.

dgen suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#197446: wmmon -i

[cfeller]

Hi,

I thought this bug report was only referring to wmmon -i, that is I/O mode.
All other modes of wmmon seem to work fine.

I'm using WindowMaker.  wmmon, and wmmon -s both work fine.  It is just 
wmmon -i, as mentioned in this bug report, that seems to be having issues.

-Chad


Also, since you said you are fixing wm* tools, would you mind looking at bug
# 559517?  wmfire does work from gnome (via "wmfire -b"), but the -b switch 
seems to have no effect in WindowMaker... 



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

Bug#620184: gdm 2.32.1 released: Upstream fixed vulnerable package

[Josselin Mouette]

reassign 620184 gdm3
thanks

Le mercredi 30 mars 2011 à 21:56 +0200, C. Petersen a écrit : 
> CVE-2011-0727 was assigned for this.
> 
> As I do understand it, all packages <2.32.1 are affected.

A CVE was already released for that in squeeze. And no, old gdm versions
are not affected, but gdm3 in unstable is.

-- 
 .''`.
: :' : “You would need to ask a lawyer if you don't know
`. `'   that a handshake of course makes a valid contract.”
  `---  J???rg Schilling




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

Bug#620207: xfonts-terminus: lacks Japanese support

[Jonathan Nieder]

Package: xfonts-terminus
Version: 4.32-1
Severity: wishlist
Tags: upstream

Trying to read a .po file to check is a bug was fixed, when I look at:

| msgid "attempt to use unsupported feature: `%s'"
| msgstr "サポートされていない機能を使おうとしています: `%s'"

I see something like:

| msgid "attempt to use unsupported feature: `%s'"
| msgstr "??: `%s'"

except the question-marks are double width.  This is probably because
my Xresources contains

*VT100.font:terminus-24

When I right-click on my xterm with ctrl held, I see I am viewing this
with the "default" font.  Switching to the "large" font makes the
characters show up in Japanese.

Questions:

 1) Is there an existing font covering Japanese characters that goes
nicely with terminus?  Is fontconfig be set up to use it?  Will
xterm notice?

 2) If so, can we make the package to install easily discoverable
somehow?

 3) Either way, what is needed to add a character set to terminus
itself?  Is there documentation on this somewhere?  Can I help
when a character is missing?

While I'm curious about (3), I'd be happy enough if (1) is solved,
so please feel free to reassign this if a solution involving another
package is possible.

Thanks for terminus.  I love it. :)
Jonathan



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

Bug#620184: gdm 2.32.1 released: Upstream fixed vulnerable package

[C. Petersen]

|A CVE was already released for that in squeeze. And no, old gdm versions
|are not affected, but gdm3 in unstable is.

Yes, I see it's fixed already.
I've been superficial.

Thanks




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

Bug#620206: Fail to install libmpich2-3

[Lifeng Sun]

Package: libmpich2-3
Version: 1.4~rc1-1

I fail to install libmpich2-3 on a system with libmpich2-2, it seems
libmpich2-3 should declare early versions of libmpich2 in its "Breaks"
field.


Cheers,
- Lifeng

-- 


signature.asc
Description: GnuPG digital signature

Bug#238786: Not a libc bug

[Witold Baryluk]

unmerge 238786
reassign 238786 cyrus-imapd-2.4
retitle 238786 cyrus21-imapd: APPEND fails with Invalid date-time, on 64-bit 
architectures.
thanks

Previous 'gmtime returns NULL for time_ts larger than 40 bits on Alpha' title
was wrong. First it returns NULL only for larger than about 2**58. Second
it is not bug, returning NULL is not a bug, it is just error condition
conforming to POSIX standards. See my posts to bug #200641.

Thus reasigning back to cyrus-imapd

Thanks

-- 
Witold Baryluk



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

Bug#412569: zdump -v on alpha (and other 64-bit archs), and gmtime

[Witold Baryluk]

Hello all.

This message is about bug #412569, but informations
are also relevant to issue #200641.

I looked deeper into zdump and gmtime issues.

And I think there is no error in libc's gmtime or zdump.

$ zdump -v /usr/share/zoneinfo/UTC
/etc/localtime  -9223372036854775808 = NULL
/etc/localtime  -9223372036854689408 = NULL
/etc/localtime  9223372036854689407 = NULL
/etc/localtime  9223372036854775807 = NULL
$

In my opinion it is actually correct output.
Documentation of zdump needs to be updated
to fully reflect this strange (but correct) behaviour.

Why?

-9223372036854775808 is smallest possible time_t
value on alpha (-2**63), as time_t on alpha is
signed long int (64 bits). Next one is one day later.
Similary 9223372036854775807 is biggest possible time_t.

This corectly follows documentation of zdump -v option.

Why such strange output?

Because -9223372036854775808, is more than 2*31 years before 1970.
And a tm_year field of struct tm, have type int, which on alpha have 32-bits.
So oldest year is -2**31 = -2147483648, and in conlusion
oldest possible date/time is  01 Jan 00:00:00 -2147483648 UTC, with
value of ``seconds after epoch'' equal -67768040609740800
(somwhere beetwen -2**56 and -2**55). This minus one, already
cannot be represented in broken-down time format in struct tm.

Similary for maxium date.

Cearfully inspecting source code, and adding some debuging
to zdump, shows also that gmtime properly sets errno to EOVERFLOW,
indicateing it cannot convert data to broken-down format.
I suppose gmtime_r will behave in exactly same way.

This issues will not happen on architectures with sizeof(int) = 8,
as tm_year will be big enugh to fit year -300498215812.
(slightly more 2**38 years before 1970).

So, also #200641 is not a bug. gmtime is behaving properly,
because int is 32-bits, even on 64-bit architectures
in our cases (not tested on amd64 just now,
but AFAIR, int is still 32-bit also there).

I checked POSIX standards and it looks that,
current behaviour do not violatate this standards.
I also think this is same behaviour as under Solaris.

Other solution is to have hardcoded string "01 Jan 00:00:00 -2147483648",
or display -67768040609740800 as smallest one
(it isn't actually smallest, but smalles which can be printed using gmtime).

So in both cases zdump documentation will need to be updated.

I personally think we should just document current behaviour.

PS. Original bug reports of #412569, do not apply anymore.
--version option is working. It still loops, but on any 64-bit
computer I tested, it exit after about 3 to 9 seconds.
And it do not crash anymore in any case.

Regards,
Witek

-- 
Witold Baryluk
JID: witold.baryluk // jabster.pl


signature.asc
Description: Digital signature

Bug#618424: voxbo binary not in PATH

[Junqian Gordon Xu]

On 3/30/11 10:42 PM, Yaroslav Halchenko wrote:
> On Wed, 30 Mar 2011, Junqian Gordon Xu wrote:
>>> voxbo doesn't need much configuration to be functional -- it would be pretty
>>> much only PATH=...
> 
>> I confirm that the two links added in sid 1.9.2+svn680.dfsg-1~nd+1
>> from /usr/bin are good starters for user to find the rest of the binaries
> 
>> ANTS -> ../lib/ants/ANTS
>> WarpImageMultiTransform -> ../lib/ants/WarpImageMultiTransform
> 
> pardon me -- are we switching onto discussing similar setup for ants?
> 

ah, sorry for the noise. I happened to be working on both and didn't
have a good sleep last night.

Gordon



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

Bug#620201: linux-image-2.6.38-1-amd64: Kernel panic with enabled RPS on a highly loaded LVS

[Ben Hutchings]

On Wed, 2011-03-30 at 19:28 +0200, Roland Pallai wrote:
[...]
> Before the building I applied the lightweight "forward_shared-2.6.37-2.diff"
> patch from Julian Anastasov (and I bumped the version to -1.1~magex).
> forward_shared is enabled (by default) on all interfaces.
> 
> I think the problem isn't depend on the small forward_shared patch.
[...]

Please remove it and verify that.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#619695: angband: bashism in configure.ac

[Jonathan Nieder]

(please cc me on replies, since debbugs does not automatically
 cc the submitter)
Hi,

Chris Carr wrote:

> I no longer have a sponsor

Hmm, that's no good.  Not being a DD, I cannot upload your package,
but I'd be glad to provide some feedback, *pretending* I was about
to upload it. :)

Contents:

 1. Where is the upstream source?
 2. Cleaning up
 3. The build
 4. Building the binary packages
 5. The build-time dependencies
 6. The run-time dependencies


1. Where is the upstream source?


Running "uscan --force-download" produces

|  uscan warning: In debian/watch,
|no matching hrefs for watch line
|
http://rephial.org/downloads/3.2/angband-([0-9]\.[0-9]\.[0-9][a-z]?)\-src\.tar\.gz

and no upstream tarball.  debian/copyright says the upstream sources
were obtained from

|  git://github.com/angband/angband.git

debian/rules get-orig-source says

| cd debian//.. &&\
|   uscan --verbose --rename --destdir debian/../.. || true
| -- Scanning for watchfiles in .
| -- Found watchfile in ./debian
| -- In debian/watch, processing watchfile line:
|opts=dversionmangle=s/\-src$// 
http://rephial.org/downloads/3.2/angband-([0-9]\.[0-9]\.[0-9][a-z]?)\-src\.tar\.gz
| uscan warning: In debian/watch,
|   no matching hrefs for watch line
|   
http://rephial.org/downloads/3.2/angband-([0-9]\.[0-9]\.[0-9][a-z]?)\-src\.tar\.gz
| -- Scan finished

I would have expected the first two to get a pristine upstream tarball,
the third to produce a repacked one if necessary (e.g., if building from
a snapshot).

2. Cleaning up
--

| $ debian/rules clean
| == making target CLN-common [new prereqs: ]==
| == making target CLN-common [new prereqs: ]==
| test ! -f Makefile || /usr/bin/make distclean
| make[1]: Entering directory `/tmp/angband'
| mk/buildsys.mk:21: mk/extra.mk: No such file or directory
| mk/buildsys.mk:381: mk/sinclude.mk: No such file or directory
| make[1]: *** No rule to make target `mk/sinclude.mk'.  Stop.
| make[1]: Leaving directory `/tmp/angband'
| make: [CLN-common] Error 2 (ignored)
| == making target CLN-indep [new prereqs: CLN-common]==
| == making target clean-indep [new prereqs: CLN-indep]==
| == making target CLN-arch [new prereqs: CLN-common]==
| == making target CLEAN/angband [new prereqs: CLN-arch]==
| == making target CLEAN/angband [new prereqs: ]==
| rm -rf /tmp/angband/debian/angband
| == making target clean-arch [new prereqs: CLN-arch angband]==
| == making target clean [new prereqs: clean-indep clean-arch]==
| test -f Makefile && /usr/bin/make distclean
| make[1]: Entering directory `/tmp/angband'
| mk/buildsys.mk:21: mk/extra.mk: No such file or directory
| mk/buildsys.mk:381: mk/sinclude.mk: No such file or directory
| make[1]: *** No rule to make target `mk/sinclude.mk'.  Stop.
| make[1]: Leaving directory `/tmp/angband'
| make: [clean] Error 2 (ignored)
| rm -f   debian/files debian/buildinfo debian/substvars angband config.status 
config.log aclocal.m4 src/autoconf.h src/autoconf.h.in mk/extra.mk 
mk/sinclude.mk 
| rm -rf /tmp/angband/debian/clean debian/stamp autom4te.cache debian/stamp
| rm -f core TAGS  \
|`find . ! -regex '.*/\.git/.*' ! -regex '.*/\{arch\}/.*'  \
|! -regex '.*/CVS/.*'   ! -regex '.*/\.arch-ids/.*'\
|! -regex '.*/\.svn/.*'\
|\( -name '*.orig' -o -name '*.rej' -o -name '*~'   -o \
|   -name '*.bak'  -o -name '#*#'   -o -name '.*.orig'  -o \
|   -name '.*.rej' -o -name '.SUMS' \) \
| -print`

It looks alarming (why does cleaning up produce errors?) but probably
okay.

3. The build


| $ debian/rules build
[...]
| checking for stat... yes
| checking if make supports SysV-style inclusion... yes
| checking for make silent include syntax... gnu
| make[2]: Entering directory `/tmp/angband'
| make[2]: *** No rule to make target `conftest.mk'.  Stop.
| make[2]: Leaving directory `/tmp/angband'
| checking for initscr in -lcurses  ... yes

What is this about?

[...]
| Successfully compiled option.c.
| parser.c: In function ‘parser_parse’:
| parser.c:228:8: warning: variable ‘iline’ set but not used 
[-Wunused-but-set-variable]

The build is remarkably light on warnings, but there are some warnings
like this when building with gcc 4.6.

[...]
| dpkg -l gcc 'libc*' binutils ldso make dpkg-dev | \
|   awk '$1 == "ii" { printf("%s-%s\n", $2, $3) }' > \
|debian/buildinfo
| No packages found matching ldso.

This looks harmless but crufty --- checking snapshot.debian.org for
ldso only turns up a package in Debian 0.93R6.  "dpkg-query -W"
might be more convenient than parsing "dpkg-query -l" output.

| $ git status -s
|  M debian
| $ cd debian
| $

Bug#618424: voxbo binary not in PATH

[Junqian Gordon Xu]

On 3/14/11 8:59 PM, Michael Hanke wrote:
> On Mon, Mar 14, 2011 at 08:36:27PM -0500, Junqian Gordon Xu wrote:
>> voxbo binaries in /usr/lib/voxbo/bin not added to the path by the 
>> installation script.
>> could source a configuration script as what's done with the fsl package.
> 
> Only pieces of voxbo get placed into the default path. The selection has
> been made by upstream.
> 
> Do I understand correctly that you'd like a sourceable config script, or
> would a snippet in the manpage be enough? I'm asking because, unlike FSL
> voxbo doesn't need much configuration to be functional -- it would be pretty
> much only PATH=...
> 
> Michael
> 

I confirm that the two links added in sid 1.9.2+svn680.dfsg-1~nd+1
from /usr/bin are good starters for user to find the rest of the binaries

ANTS -> ../lib/ants/ANTS
WarpImageMultiTransform -> ../lib/ants/WarpImageMultiTransform

This bug can be closed.

Thanks
Gordon



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

Bug#620205: No support in sysconfig-hardware for the DASD options

[Stephen Powell]

Package: sysconfig-hardware
Version: 0.0.10
Severity: wishlist

The Debian version of sysconfig-hardware has no support for the
DASD options.  For example, when configuring a DASD device via the
dasd parameter passed to the dasd_mod module, I can specify options
such as "diag" (to request that the dasd_diag_mod driver be used)
or "ro" (to tell the driver that the DASD device is to be treated
as a read-only device).  Here is a sample configuration file called
/etc/modprobe.d/dasd.conf:

   options dasd_mod dasd=0.0.0200(diag),0.0.0201,0.0.0202(ro),0.0.0203(diag:ro)
   softdep dasd_eckd_mod pre: dasd_diag_mod
   softdep dasd_fba_mod pre: dasd_diag_mod

The above file specifies that device numbers 0200 and 0203 are to use
the dasd_diag_mod driver and that device numbers 0202 and 0203 are
to be treated as read-only devices.  By contrast, a DASD device configured
via sysconfig-hardware cannot specify either of these options.  Adding
support for this is both useful and trivial.  I suggest the following
patch file be applied to /etc/sysconfig/scripts/hardware/hwup-ccw-dasd:

-

--- hwup-ccw-dasd-old   2008-07-04 09:29:02.0 -0400
+++ hwup-ccw-dasd   2011-03-29 08:57:28.0 -0400
@@ -17,6 +17,18 @@
 if test "$_online" -eq "1" ; then
   message "already online."
 else
+  [ -z "$DASD_USE_DIAG" ] && DASD_USE_DIAG=0
+  if [ "$DASD_USE_DIAG" = "1" ]; then
+echo 1 > $SYSFS$DEVPATH/use_diag
+  else
+echo 0 > $SYSFS$DEVPATH/use_diag
+  fi
+  [ -z "$DASD_READONLY" ] && DASD_READONLY=0
+  if [ "$DASD_READONLY" = "1" ]; then
+echo 1 > $SYSFS$DEVPATH/readonly
+  else
+echo 0 > $SYSFS$DEVPATH/readonly
+  fi
   echo 1 > $SYSFS$DEVPATH/online
   message "ok. "
 fi

-

Once this patch is applied, the DASD devices listed in the
first example can be configured as follows:

   /etc/sysconfig/hardware/config-ccw-0.0.0200:
   DASD_USE_DIAG=1

   /etc/sysconfig/hardware/config-ccw-0.0.0201:
   (zero-length file created by "touch")

   /etc/sysconfig/hardware/config-ccw-0.0.0202:
   DASD_READONLY=1

   /etc/sysconfig/hardware/config-ccw-0.0.0203:
   DASD_USE_DIAG=1
   DASD_READONLY=1

DASD_USE_DIAG has been used by other Linux distributions,
such as Suse Linux Enterprise Server (SLES).  DASD_READONLY,
as far as I can tell, has not been used in other distributions;
but it seems logical to me to support both, since both can
be specified via the dasd parameter passed to the dasd_mod
module.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



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

Bug#614593: Please add new armel kernel flavour for the Marvell DB-78x00-BP Development Board

[Hector Oron]

Hello,

On Sun, Feb 27, 2011 at 06:21:36PM +, Martin Michlmayr wrote:
 
> As a compromise, we could add a kernel config file for MV78xx0 to the
> Debian kernel package but not build this flavour by Debian.  This way,
> you'd just need to add one line to the config file and rebuild the
> kernel.
> 
> Would that help?
 
 That would be welcome, better than status quo.
 IMHO it would really help on the linux kernel for backports/squeeze.

Cheers,
  -- Héctor Orón



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

Bug#619995: bitlbee does not start on kFreeBSD

[Eric Hermes]

Sorry about that, I initially neglected to reply-all.

Initially there was also the following line:

Mar 28 21:13:03 nene bitlbee[2214]: The configuration directory 
`/var/db/bitlbee/' does not exist. Configuration won't be saved.


However I created this directory and chowned it to bitlbee.  The -n 
argument does cause bitlbee to start properly.  Is there any way I can 
get the daemon to work?  I added the argument to the following line in 
/etc/init.d/bitlbee under d_start():


--exec $DAEMON -- -p $BITLBEE_PORT -P $PIDFILE 
$BITLBEE_OPTS


But it does not daemonize properly.

I apologize if this is perfectly obvious, as I'm not exactly a guru.  
The severity can probably be safely lowered though, as bitlbee does 
appear to work on kBSD.


Thanks,
Eric


On 3/29/2011 04:55, Wilmer van der Gaast wrote:

Hello,

Eric Hermes wrote:

bitlbee will not start on kFreeBSD, and the following error shows up in 
/var/log/daemon.log:

Mar 28 21:17:43 nene bitlbee[2269]: Unable to create UNIX socket: Protocol not 
supported


That one isn't really a big deal, it's just the IPC socket (which isn't
really used yet).

This is the only thing it logs? What if you start it with -n?


Wilmer.

Bug#620204: linux-2.6: FTBFS on armel: ERROR: "__bad_udelay"

[Hector Oron]

Package: linux-2.6
Version: 2.6.38-2
Severity: serious

Hello,

  Your package fails to build on armel autobuilders,

LD  arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Building modules, stage 2.
MODPOST 1761 modules
ERROR: "__bad_udelay" [drivers/net/wireless/rtlwifi/rtlwifi.ko] 
undefined!
WARNING: modpost: Found 2 section mismatch(es).

  Full build log available at:
  
https://buildd.debian.org/fetch.cgi?pkg=linux-2.6&arch=armel&ver=2.6.38-2&stamp=1301476713&file=log&as=raw

  A possible fix can be found at:
  
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commit;h=8c6113cd03c7e927f5ee5f6ad98e155ef2d27177

Cheers

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

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



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

Bug#620203: [alpha] libc-bin / libc6.1: LEVEL*CACHE* inproperly mixed

[Witold Baryluk]

Package: libc6.1
Version: 2.11.2-13
Severity: normal

I tested both 2.7-18lenny7 and 2.11.2-13 on other machine,
result is the same:

$ getconf -a | grep LEVEL
LEVEL1_ICACHE_SIZE 64
LEVEL1_ICACHE_ASSOC65536
LEVEL1_ICACHE_LINESIZE 2
LEVEL1_DCACHE_SIZE 64
LEVEL1_DCACHE_ASSOC65536
LEVEL1_DCACHE_LINESIZE 2
LEVEL2_CACHE_SIZE  64
LEVEL2_CACHE_ASSOC 4194304
LEVEL2_CACHE_LINESIZE  1
LEVEL3_CACHE_SIZE  
LEVEL3_CACHE_ASSOC 
LEVEL3_CACHE_LINESIZE  
LEVEL4_CACHE_SIZE  
LEVEL4_CACHE_ASSOC 
LEVEL4_CACHE_LINESIZE  
$

$ cat /proc/cpuinfo 
cpu : Alpha
cpu model   : EV6
cpu variation   : 7
cpu revision: 0
cpu serial number   : 
system type : Tsunami
system variation: Monet
system revision : 0
system serial number: AY0
cycle frequency [Hz]: 5 
timer frequency [Hz]: 1024.00
page size [bytes]   : 8192
phys. address bits  : 44
max. addr. space #  : 255
BogoMIPS: 994.44
kernel unaligned acc: 24 (pc=fc00010e0748,va=fc00192ca1ea)
user unaligned acc  : 0 (pc=0,va=0)
platform string : COMPAQ Professional Workstation XP1000
cpus detected   : 1
L1 Icache   : 64K, 2-way, 64b line
L1 Dcache   : 64K, 2-way, 64b line
L2 cache: 4096K, 1-way, 64b line
L3 cache: n/a
$

As you can see

  LEVEL2_CACHE_SIZE  64
  LEVEL2_CACHE_ASSOC 4194304
  LEVEL2_CACHE_LINESIZE  1

should be actually

  LEVEL2_CACHE_SIZE  4194304
  LEVEL2_CACHE_ASSOC 1
  LEVEL2_CACHE_LINESIZE  64

for example

Both machines are identical. one have lenny installed, one is
partially using unstable (for example libc* packages).

Both machines runs 2.6.26:

Linux a02 2.6.26-2-alpha-generic #1 Thu Jan 27 05:54:49 UTC 2011 alpha GNU/Linux


Regards,
Witek


-- debconf information:
  glibc/upgrade: true
  glibc/restart-failed:
  glibc/restart-services:



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

Bug#620202: ITP: lcrt -- Linux remote login tool

[Asias He]

On 03/31/2011 09:11 AM, Jonathan McCrohan wrote:
> Hi,
> 
> I think you have a typo in the URL:
> http://code.google.com/p/lcrt/
> 
> Jon

Hi Jon

Yes. It should be http://code.google.com/p/lcrt
Thanks.

-- 
Best Regards,
Asias He



signature.asc
Description: OpenPGP digital signature

Bug#614781: libpam-mount: could not chown ... : Operation not

[Jan Engelhardt]

>Why is there no disk for '%(USER)-server'?

Because the desktop environments usually do not show a disk icon for 
each and every mount, but only for mounts backed by a local hardware 
device.



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

Bug#615121: #615121: iptables --localtz option of -m time not working

[Jan Engelhardt]

>Not sure if it matters, but the hardware clock is using UTC (i.e. 
>/etc/default/rcS contains "UTC=yes").

When the xt_time kernel module is loaded, it prints the current timezone 
the kernel is operating with - and this is what xt_time will be using 
when doing localtz comparisons.



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

Bug#620202: ITP: lcrt -- Linux remote login tool

[Jonathan McCrohan]

Hi,

I think you have a typo in the URL:
http://code.google.com/p/lcrt/

Jon

On 31/03/2011 01:58, Asias He wrote:

Package: wnpp
Severity: wishlist
Owner: Asias He


* Package name: lcrt
   Version : 1.0.0
   Upstream Author : NiuTao
* URL : http://code.google.com/lcrt
* License : GPL2
   Programming Lang: C
   Description : Linux remote login tool

Lcrt is a Linux Remote Login Tool. Some linuxer think there is not
a good terminal like SecureCRT(may be there is but I don't known),
so I write one, here it is.







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

Bug#619708: lprof: diff for NMU version 1.11.4.dfsg+1.11.4.1-5.1

[Jakub Wilk]

tags 619708 + pending
thanks

Dear maintainer,

I've prepared an NMU for lprof (versioned as 1.11.4.dfsg+1.11.4.1-5.1) 
and uploaded it to DELAYED/2. Please feel free to tell me if I should 
delay it longer.


--
Jakub Wilk
diffstat for lprof_1.11.4.dfsg+1.11.4.1-5 lprof_1.11.4.dfsg+1.11.4.1-5.1

 debian/patches/04_HOME.dpatch|   18 ++
 lprof-1.11.4.dfsg+1.11.4.1/debian/changelog  |8 
 lprof-1.11.4.dfsg+1.11.4.1/debian/patches/00list |1 +
 3 files changed, 27 insertions(+)

diff -u lprof-1.11.4.dfsg+1.11.4.1/debian/changelog lprof-1.11.4.dfsg+1.11.4.1/debian/changelog
--- lprof-1.11.4.dfsg+1.11.4.1/debian/changelog
+++ lprof-1.11.4.dfsg+1.11.4.1/debian/changelog
@@ -1,3 +1,11 @@
+lprof (1.11.4.dfsg+1.11.4.1-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/patches/04_HOME.dpatch: Added a patch to fix FTBFS if HOME is
+unset (closes: #619708).
+
+ -- Jakub Wilk   Thu, 31 Mar 2011 00:05:08 +0200
+
 lprof (1.11.4.dfsg+1.11.4.1-5) unstable; urgency=low
 
   * debian/patches/03_lcmsprf.h.dpatch: Added a patch to fix FTBFS against
diff -u lprof-1.11.4.dfsg+1.11.4.1/debian/patches/00list lprof-1.11.4.dfsg+1.11.4.1/debian/patches/00list
--- lprof-1.11.4.dfsg+1.11.4.1/debian/patches/00list
+++ lprof-1.11.4.dfsg+1.11.4.1/debian/patches/00list
@@ -3,0 +4 @@
+04_HOME.dpatch
only in patch2:
unchanged:
--- lprof-1.11.4.dfsg+1.11.4.1.orig/debian/patches/04_HOME.dpatch
+++ lprof-1.11.4.dfsg+1.11.4.1/debian/patches/04_HOME.dpatch
@@ -0,0 +1,18 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 04_HOME.dpatch by Jakub Wilk 
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Don't require HOME to be set.
+
+@DPATCH@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' lprof-1.11.4.dfsg+1.11.4.1~/SConstruct lprof-1.11.4.dfsg+1.11.4.1/SConstruct
+--- lprof-1.11.4.dfsg+1.11.4.1~/SConstruct	2006-06-06 03:11:32.0 +0200
 lprof-1.11.4.dfsg+1.11.4.1/SConstruct	2011-03-30 23:44:51.598463862 +0200
+@@ -25,7 +25,6 @@
+ env = Environment(
+ ENV = {
+   'PATH' : os.environ[ 'PATH' ],
+-  'HOME' : os.environ[ 'HOME' ], # required for distcc
+   'LDFLAGS' : ''
+ }, options = opts)
+ 

Bug#619766: [pkg-boost-devel] Bug#619766: libboost1.46-dev: hardcode-dll-paths feature is missing

[Steve M. Robbins]

Hi,


On Tue, Mar 29, 2011 at 03:12:31PM +0200, Olaf van der Spek wrote:
> > This feature is really useful for developpers.
> 
> Why?

My understanding of the use-case is: suppose you are using
Boost.Build to build a project that contains a library
as well as an executable linked with that lib.  If the
library is built as a shared object, the hardcode-dll-paths
lets you build and run the executable in-place.


I'm Cc'ing the bug submitter for further clarification.

Regards,
-Steve



signature.asc
Description: Digital signature

Bug#620202: ITP: lcrt -- Linux remote login tool

[Asias He]

Package: wnpp
Severity: wishlist
Owner: Asias He 


* Package name: lcrt
  Version : 1.0.0
  Upstream Author : NiuTao 
* URL : http://code.google.com/lcrt
* License : GPL2
  Programming Lang: C
  Description : Linux remote login tool

Lcrt is a Linux Remote Login Tool. Some linuxer think there is not
a good terminal like SecureCRT(may be there is but I don't known), 
so I write one, here it is.



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

Bug#620059: #620059: nfs-kernel: Starting NFS kernel daemon: nfsd mountd failed!

[Robert Miller]

Hi All:

Replacing portmap with rpcbind fixes the problem for me as well...confirmed.
It is hoped that portmap will eventually be fixed to support IPv6 as well as
rpcbind I'm not sure how complete it is but for now this is a good
workaround until portmap is updated.

Cheers

Rob

Bug#620064: apt: please drop dependency on gnupg

[Carsten Hey]

* David Kalnischkies [2011-03-30 18:11 +0200]:
> On Tue, Mar 29, 2011 at 21:30, Carsten Hey  wrote:
> > * David Kalnischkies [2011-03-29 20:03 +0200]:
> >> On Tue, Mar 29, 2011 at 18:32, Carsten Hey  wrote:
> Support was added in 0.7.25.1 -- some bugfixes occurred later,
> so to be save assume squeeze version of APT (0.8.10.3) provides it.

Very good, since skipping a stable release is not supported, this is
nothing we need to think about anymore :)

> > 2b. d-a-k drops the dependency on gnupg and still uses apt-key in its
> >    maintainer scripts
> >
> >    not done
>
> Yeah, either d-a-k or APT can remove the gnupg dependency, but not both
> as otherwise you will have in new installation the problem that gnupg is not
> around to manage the trusted.gpg file…
>
> I mean, APT could remove it now without changing anything - and d-a-k
> can do it after implementing 2c, but if it is done before the key will be not
> available for verification…

First google hit (at least here) when searching for "ubuntu ppa gpg" is:

  
http://gentoo-blog.de/ubuntu/ubuntu-gpg-error-httpppalaunchpadnet-intrepid-release/

... and it explains how to use apt-key to add keys.  The second hit has
essential the same key in the first comment and the third hit also uses
apt-key add.

Sounds like recommending gnupg instead of suggesting it or even droping
the dependency would be a good idea since people really use it.  People
who know what they to could still ignore this recommendation.

When apt recommends gnupg there is not much left for gpgv, either depend
on it or do not mention because gnupg already depends on gpgv.

I wrote earlier that keyring packages are just data.  Maybe letting the
keyring packages depend on gpgv isn't that bad, it would ensure that
installed keyring packages can be used and there isn't much useful you
could with them besides verifying release files.  I see no other way to
express:

  "gnupg should be installed by default because people would be
  surprised if apt-key wouldn't work but they should also be able to
  remove it. gpgv is more important than gnupg, so this should normally
  even be installed if gnupg is not."

The above would lead to:

  apt recommends d-a-k and gnupg
  d-a-k depends on gpgv

or

  apt depends on d-a-k and recommends gnupg
  d-a-k depends on gpgv

> >> For me a plan looks more like:
> >> - switch all keyring packages to store their keyrings in the new (=squeeze
> >>   supports it) trusted.gpg.d directory - at best even more fragments if it
> >>   makes sense, e.g. oldstable keys in an other file than the one for 
> >> testing.
> >>   Links are fine, too.
> >
> > This is 2a and 2c from my list above.
> >
> > As long as the old interface is not removed and the other keyring
> > packages depend on gnupg, there is no need to touch them now.  Switching
> > them can be done later.  Prerequisite for this is that apt-key fails in
> > a sane way if gnupg is not installed.
>
> It doesn't currently (command not found), but after all, what is a
> 'sane way' to fail?

The following is also just a "command not found" and could be written in
better words:

# apt-get purge dialog
# orphaner
/usr/sbin/orphaner: You need "dialog" in $PATH to run this frontend.
zsh: exit 1 orphaner

The difference between the above and the usual "command not found: ..."
is in my opinion that the former makes it clear that this is not a bug
and it is intended to behave that way.

Patch attached.

> apt-key would need to fail, causing the maintainer script to fail, so
> the package fails to install. The alternative is 'just' printing
> a warning, which nobody will see…

I think only one (see below) could fail, the current dependencies should
ensure apt-key works in the keyrings' maintainer scripts.  When keyring
packages would drop the gnupg dependency they need to also
simultaneously switch to the new apt interface (this is vice versa
I originally thought it should be done, but I think this way is better).

> >> (- remove the apt dependency from all keyring packages)
> >
> > I don't think there is one.
>
> debian-ports-archive-keyring for example, but all the others, too.
> Expect d-a-k of course, this would be a circle dependency…

I see.  The postrm script for emdebian-archive-keyring is wrong.
debian-backports-keyring uses prerm.  All other packages only use
postinst to call apt-key.

> >> (- downgrade APTs d-a-k dependency to a recommend)
> >
> > If you want to make d-a-k and gpgv optional, I would let apt recommend
> > both.  In this case, ensuring that debootstrap and cdebootstrap install
> > both in their minimal variants might be useful (people could still
> > remove these packages).
> >
> > I have no opinion whether d-a-k and gpgv should be optional or not.
>
> Its the connotation of #558784 - be able to decide on your own which keys
> to trust, so you properly don't want to automatically trust new keys.
> And as you said chroots or embedded systems might like it, too.
> So a Recommends would in my eyes

Bug#620104: dh-buildinfo breaks co-installability of Multi-Arch: same packages

[Steve Langasek]

On Wed, Mar 30, 2011 at 07:55:50PM -0400, Anders Kaseorg wrote:
> On Wed, 30 Mar 2011, Yann Dirson wrote:
> > On Wed, Mar 30, 2011 at 01:17:01AM -0400, Anders Kaseorg wrote:
> > > dh-buildinfo creates a /usr/share/doc/PACKAGE/buildinfo.gz that’s 
> > > different on different architectures, which breaks co-installability 
> > > of Multi-Arch: same packages.

> > Ah.  Not being familiar with those multi-arch issues yet, but I suppose 
> > they should include the arch in the filename ?

> Yeah, I think that’s a reasonable solution.  Either ‘dpkg-architecture 
> -qDEB_HOST_ARCH’ or ‘dpkg-architecture -qDEB_HOST_MULTIARCH’ should work 
> (the latter requires dpkg 1.16.0).

> I’m CCing Steve Langasek and Paul Wise, with whom I briefly discussed this 
> issue on #multiarch yesterday, in case they have anything else to add.

DEB_HOST_ARCH will be unique for each architecture, and should be suitable
for use here IMHO.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#620104: dh-buildinfo breaks co-installability of Multi-Arch: same packages

[Anders Kaseorg]

On Wed, 30 Mar 2011, Yann Dirson wrote:
> On Wed, Mar 30, 2011 at 01:17:01AM -0400, Anders Kaseorg wrote:
> > dh-buildinfo creates a /usr/share/doc/PACKAGE/buildinfo.gz that’s 
> > different on different architectures, which breaks co-installability 
> > of Multi-Arch: same packages.
> 
> Ah.  Not being familiar with those multi-arch issues yet, but I suppose 
> they should include the arch in the filename ?

Yeah, I think that’s a reasonable solution.  Either ‘dpkg-architecture 
-qDEB_HOST_ARCH’ or ‘dpkg-architecture -qDEB_HOST_MULTIARCH’ should work 
(the latter requires dpkg 1.16.0).

I’m CCing Steve Langasek and Paul Wise, with whom I briefly discussed this 
issue on #multiarch yesterday, in case they have anything else to add.

Anders



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

Bug#616007: dpkg-reconfigure cron fails

[Christian Kastner]

reassign 616007 debconf
forcemerge 560317 616007
thanks


On 01/-10/-28163 08:59 PM, Jari Jokinen wrote:
> Package: cron
> Version: 3.0pl1-116
> Severity: normal
> 
> Running "dpkg-reconfigure cron" fails in fresh installations of Debian
> Squeeze 6.0 (amd64), which means also "dpkg-reconfigure --all" fails if
> the cron package is installed.
> 
> Error message:
> 
>   dpkg-maintscript-helper: error: couldn't identify the package
> 
> I fixed the issue temporarily by commenting out all lines starting with
> "dpkg-maintscript-helper" from the /var/lib/dpkg/info/cron.* files.

This is actually a bug in dpkg-reconfigure, reassigning and merging.



signature.asc
Description: OpenPGP digital signature

Bug#620200: kingston-update-notifier: French debconf templates translation

[Cédric Boutillier]

Package: kingston-update-notifier
Severity: wishlist
Tags: patch l10n

Hi,

Please find attached the french debconf templates translation, proofread by the 


debian-l10n-french mailing list contributors.   





This file should be put as debian/po/fr.po in your package build tree.

Best wishes,

Cédric

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

Kernel: Linux 2.6.38-2-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
# Copyright (C) 2011 Debian French l10n team 

# This file is distributed under the same license as the 
kingston-update-notifier package.
#
# Cédric Boutillier , 2011.
msgid ""
msgstr ""
"Project-Id-Version: kingston-update-notifier 1.2.3\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n";
"POT-Creation-Date: 2011-03-18 15:58+0100\n"
"PO-Revision-Date: 2011-03-22 23:20+0100\n"
"Last-Translator: Cédric Boutillier \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Lokalize 1.1\n"

#: src/notifier.cpp:57
msgid "It is recommended to update your system."
msgstr "La mise à jour du système est recommandée."

#: src/notifier.cpp:57
#, kde-format
msgid "There is %1 update available."
msgid_plural "There are %1 updates available."
msgstr[0] "%1 mise à jour est disponible."
msgstr[1] "%1 mises à jour sont disponibles."

#: src/notifier.cpp:61 src/notifier.cpp:67
msgid "You should update your system."
msgstr "Vous devriez mettre à jour le système."

#: src/notifier.cpp:61
#, kde-format
msgid "There is %1 security update available."
msgid_plural "There are %1 security updates available."
msgstr[0] "%1 mise à jour de sécurité est disponible."
msgstr[1] "%1 mises à jour de sécurité sont disponibles."

#: src/notifier.cpp:63
#, kde-format
msgid "%1 update"
msgid_plural "%1 updates"
msgstr[0] "%1 mise à jour"
msgstr[1] "%1 mises à jour"

#: src/notifier.cpp:64
#, kde-format
msgid "%1 security update"
msgid_plural "%1 security updates"
msgstr[0] "%1 mise à jour de sécurité"
msgstr[1] "%1 mises à jour de sécurité"

#: src/notifier.cpp:67
#, kde-format
msgctxt ""
"%2 is e.g. '3 updates'; %3 is e.g. '1 security update'; the plural form "
"represents the number of total updates (non-security and security ones)"
msgid "There is: %2, and %3"
msgid_plural "There are: %2, and %3"
msgstr[0] "%2 et %3 est disponible."
msgstr[1] "%2 et %3 sont disponibles."

#: src/notifier.cpp:84 src/notifier.cpp:97
msgctxt "Do the proposed action (upgrade, reboot, etc) later"
msgid "Later"
msgstr "Plus tard"

#: src/notifier.cpp:92
msgid "Please reboot your system."
msgstr "Veuillez redémarrer le système."

#: src/notifier.cpp:93
msgid "In order to complete this upgrade, you need to reboot your system."
msgstr ""
"Afin de terminer cette mise à niveau, vous devez redémarrer le "
"système."

#: src/notifier.cpp:98
msgctxt "Reboot the system"
msgid "Reboot"
msgstr "Redémarrer"



signature.asc
Description: Digital signature

Bug#620196: iceweasel: dark gtk theme does not apply colour to certain ui elements

[Ximin Luo]

clone 620196 -1
reassign -1 all-in-one-sidebar
tag -1 upstream
thanks

these problems can be temporarily manually fixed by editing the following
through DOM inspector / Object Viewer / CSS Style Rules:

nav toolbar:
in chrome://browser/skin/browser.css, delete:
#nav-bar:not(:-moz-lwtheme),
#nav-bar[collapsed="true"] + toolbar:not(:-moz-lwtheme),
#nav-bar[collapsed="true"] + #customToolbars + 
#PersonalToolbar:not(:-moz-lwtheme),
#navigator-toolbox[tabsontop="true"] > #nav-bar,
#navigator-toolbox[tabsontop="true"]:not([customizing]) >
#nav-bar[collapsed="true"] + toolbar,
#navigator-toolbox[tabsontop="true"]:not([customizing]) >
#nav-bar[collapsed="true"] + #customToolbars + #PersonalToolbar {
  background-image: -moz-linear-gradient(rgba(255,255,255,.3),
rgba(255,255,255,0));
}

sidebar:
in chrome://aios/skin/addons_fx4.css, delete:
#addons-page[aios_appDefTheme="true"] .addon:not([selected="true"]) {
background-color: #FF;
}

I am using the AIOS extension (hence the cloning), but there is a similar
problem with about:addons (the default fx4 addons UI) - the main content panel
is dark, but the surrounding page has a white background.

X

-- 
GPG: 4096R/5FBBDBCE



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

Bug#610942: Processed: reassign 610942 to mirrors, retitle 610942 to 403 error downloading snmp pkg from ftp.ru.d.o ...

[Simon Paillard]

On Tue, Mar 22, 2011 at 08:45:00PM +0100, Simon Paillard wrote:
> On Mon, Jan 24, 2011 at 02:19:17PM +0100, Simon Paillard wrote:
> > On Mon, Jan 24, 2011 at 10:45:08AM +, Debian Bug Tracking System wrote:
> > > Processing commands for cont...@bugs.debian.org:
> [...]
> > > Bug #610942 [mirrors] 403 error downloading snmp pkg from ftp.ru.d.o
> > > Severity set to 'normal' from 'important'
> > 
> > ftp.ru.d.o temporarily redirected to some other mirror.
> 
> http://ftp.chg.ru/debian/pool/main/n/net-snmp/
> 
> Serge, any news on this issue so that we can set ftp.ru.d.o back to chg.ru ? 

No progress :-(
Ping ? 

-- 
Simon Paillard



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

Bug#620198: lprof: FTBFS if built twice in a row

[Jakub Wilk]

Source: lprof
Version: 1.11.4.dfsg+1.11.4.1-5
Severity: important
User: debian...@lists.debian.org
Usertags: qa-doublebuild

lprof FTBFS if built twice in a row with the following error:
|  dpkg-source -b lprof-1.11.4.dfsg+1.11.4.1
| dpkg-source: warning: no source format specified in debian/source/format, see 
dpkg-source(1)
| dpkg-source: info: using source format `1.0'
| dpkg-source: info: building lprof using existing 
lprof_1.11.4.dfsg+1.11.4.1.orig.tar.gz
| dpkg-source: info: building lprof in lprof_1.11.4.dfsg+1.11.4.1-5.diff.gz
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/parmsqt/moc_profileparms.o: binary file contents 
changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/monqt/moc_monitorvalues.o: binary file contents 
changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/gammaqt/moc_setgamma.o: binary file contents 
changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/checkerqt/moc_profilechecker.o: binary file 
contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/reference_inst_qt/moc_installreffile.o: binary 
file contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/wwfloatspinbox/moc_wwfloatspinbox.o: binary file 
contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/libqtlcmswidgets/moc_qtlcmswidgets.o: binary 
file contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/lprofqt/moc_lprofmain.o: binary file contents 
changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/src/IDqt/moc_profileid.o: binary file contents 
changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/build/linux/lprof: binary file contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/build/linux/icc2it8: binary file contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/build/linux/argyll/rspl/librspl.a: binary file 
contents changed
| dpkg-source: error: cannot represent change to 
lprof-1.11.4.dfsg+1.11.4.1/build/linux/argyll/numlib/libnumlib.a: binary file 
contents changed
| dpkg-source: warning: executable mode 0700 of 
'debian/patches/01_qt3_headers.dpatch' will not be represented in diff
| dpkg-source: warning: executable mode 0700 of 
'debian/patches/02_SConstruct.dpatch' will not be represented in diff
| dpkg-source: warning: executable mode 0700 of 
'debian/patches/03_lcmsprf.h.dpatch' will not be represented in diff
| dpkg-source: warning: the diff modifies the following upstream files:
|  build/linux/IDqt/moc_profileidbase.cc
|  build/linux/IDqt/profileidbase.h
|  build/linux/IDqt/uic_profileidbase.cc
|  build/linux/checkerqt/moc_profilecheckerbase.cc
|  build/linux/checkerqt/profilecheckerbase.h
|  build/linux/checkerqt/uic_profilecheckerbase.cc
|  build/linux/gammaqt/moc_setgammabase.cc
|  build/linux/gammaqt/setgammabase.h
|  build/linux/gammaqt/uic_setgammabase.cc
|  build/linux/lprofqt/lprofmainbase.h
|  build/linux/lprofqt/moc_lprofmainbase.cc
|  build/linux/lprofqt/uic_lprofmainbase.cc
|  build/linux/monqt/moc_monitorvaluesbase.cc
|  build/linux/monqt/monitorvaluesbase.h
|  build/linux/monqt/uic_monitorvaluesbase.cc
|  build/linux/parmsqt/moc_profileparmsbase.cc
|  build/linux/parmsqt/profileparmsbase.h
|  build/linux/parmsqt/uic_profileparmsbase.cc
|  build/linux/reference_inst_qt/installreffilebase.h
|  build/linux/reference_inst_qt/moc_installreffilebase.cc
|  build/linux/reference_inst_qt/uic_installreffilebase.cc
|  src/IDqt/moc_profileid.cc
|  src/checkerqt/moc_profilechecker.cc
|  src/gammaqt/moc_setgamma.cc
|  src/libqtlcmswidgets/moc_qtlcmswidgets.cc
|  src/lprofqt/moc_lprofmain.cc
|  src/monqt/moc_monitorvalues.cc
|  src/parmsqt/moc_profileparms.cc
|  src/reference_inst_qt/moc_installreffile.cc
|  src/wwfloatspinbox/moc_wwfloatspinbox.cc
| dpkg-source: info: use the '3.0 (quilt)' format to have separate and 
documented changes to upstream files, see dpkg-source(1)
| dpkg-source: unrepresentable changes to source
| dpkg-buildpackage: error: dpkg-source -b lprof-1.11.4.dfsg+1.11.4.1 gave 
error exit status 1

It looks like the clean target isn't removing everything it should.

--
Jakub Wilk



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

Bug#620197: Typo in man page gnash(1)

[Gabriele Giacone]

Package: src:gnash
Version: 0.8.9-1

 Original Message 
Subject: [Gnash-commit] [bug #32960] Typo in man page gnash(1)
Date: Wed, 30 Mar 2011 21:53:12 +
From: Reuben Thomas 
To: Reuben Thomas , gnash-com...@gnu.org

URL:
  

 Summary: Typo in man page gnash(1)
 Project: Gnash - The GNU Flash player
Submitted by: rrt
Submitted on: Wed 30 Mar 2011 09:53:12 PM GMT
Category: None
Severity: 3 - Normal
 Release: None
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

comm-separated -> comma-separated




___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Gnash-commit mailing list
gnash-com...@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-commit




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

Bug#615855: cron: strange behaviour of initscript's status option, stop leaving pid file?

[Christian Kastner]

tag 615855 confirmed
thanks

Sorry for the late reply, I somehow managed to unsubscribe myself from
the PTS.

On 01/-10/-28163 08:59 PM, Michael Prokop wrote:
> Package: cron
> Version: 3.0pl1-105
 ^
ITYM -116 from Squeeze; -105 (the version in Lenny) did not support the
status command

> # /etc/init.d/cron status
> Checking periodic command scheduler...done (running).
> # echo $?
> 0
> # /etc/init.d/cron stop
> Stopping periodic command scheduler: cron.
> # echo $?
> 0
> 
> Ok, but:
> 
> # /etc/init.d/cron status
> Checking periodic command scheduler...failed (failed to start).
> # echo $?
> 1
> 
> I'd expected to get return code 3. Looking closer:
> 
> # ls /var/run/crond.pid
> /var/run/crond.pid
> # cat /var/run/crond.pid
> 15510
> # ps aux | grep [1]5510
> #
> 
> Is this by intention?

No, the PID file is not removed because vixie cron-3.1 just spins in a
loop until it receive SIGTERM et al. It is interesting that nobody
noticed this until now.

This doesn't appear to be an issue in unstable (maybe start-stop-daemon
and friends take care of it). I'm not sure if a fix for stable will be
accepted, I'll see what I can do.

 AFAICS it doesn't behave as
> LSB requires it to (see
> http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
> for details).



signature.asc
Description: OpenPGP digital signature

Bug#614567: cron: recurrent error appears in syslog

[Christian Kastner]

forcemerge 608874 614567
thanks

On 01/-10/-28163 08:59 PM, kubrick wrote:
> Package: cron
> Version: 3.0pl1-116
> Severity: normal
> 
> This error appears in the syslog file:
> 
> (CRON) error (grandchild #2323 failed with exit status 143)

I'm pretty sure this is a duplicate of #608874



signature.asc
Description: OpenPGP digital signature

Bug#620195: override: noshell: admin/oldlibs

[Javier Fernández-Sanguino Peña]

Package: ftp.debian.org

Hi, I recently moved the noshell package to a transitional package as the
binaries provided by it are now in the titantools package.

The upload queue tells me this:

On Wed, Mar 30, 2011 at 10:48:50PM +, Debian FTP Masters wrote:
> noshell_4.0.11+notdfsg1-5_all.deb: package says section is non-free/oldlibs, 
> override says non-free/admin.
> 

Since the package is a dummy package I believe the override is incorrect and
the 'noshell' package should be in section non-free/oldlibs.

Thanks

Javier


signature.asc
Description: Digital signature

Bug#620126: 3880 storage control supports 3370 and 3380 devices, but not a 3390 device

[Stephen Powell]

It looks like the same bug exists in
/etc/sysconfig/scripts/hardware/hwup-ccw near line 50:

   3880/*)
   case "$devtype" in
 3370/*)
 name="dasd-fba"
 ;;
 3390/*)
 name="dasd-eckd"
 ;;
   esac
   ;;

That 3390 should also be 3380.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



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

Bug#618871: transition: ocaml

[Stéphane Glondu]

Le 29/03/2011 19:52, Julien Cristau a écrit :
>>> The Debian OCaml team is ready for a transition to OCaml 3.12.0. All
>>> packages depending on ocaml-base-nox-3.11.2 and ocaml-base-3.11.2 will
>>> be affected.
>>>
>>> I am waiting for the approval from the release team to proceed.
>>
>> Any news on that?
>>
> Clearly not.

Could you give more detail, please? Is there an ongoing transition
somehow conflicting and that could use some help? I heard about gmp, but
gmp/gmp4 (and why, which had been temporarily removed from testing) just
migrated to testing, and I didn't find any open bugs tracking this. I
haven't looked at other transitions... but I ask here because you are
supposed to be more knowledgeable :-)

According to [1], there remains stuff, though, but (on amd64 at least),
most of the packages go green after a binNMU. Obvious issues are
cheesetracker, gclcvs, genius, guile-1.8, lilypond, netrek-client-cow,
strongswan, acl2, hol88, mlgmp [I could probably "fix" that, but
haven't been notified], linbox [not sure], maxima, open-cobol,
regina-normal, units-filter [not sure]... is there anyone working on
that right now? FTR, we have far less unsolved "obvious" issues in the
planned ocaml transition, and they are documented at [2].

It would be nice if we used the power of our BTS and set blockers for
this bug (#618871), so that someone outside the release team (such as
me) can see more clearly [than "Clearly not."] what is going on.

[1] http://release.debian.org/transitions/gmp5.html
[2] http://wiki.debian.org/Teams/OCamlTaskForce/OCamlTransitions


Cheers,

-- 
Stéphane




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

Bug#620193: #include statements in packaged header files point to wrong directory

[Jorge Moraleda]

Package: libpoppler-dev
Version: 0.12.4-1.2
Justification: renders package unusable
Severity: grave
Tags: patch

Several header files in /usr/include/poppler/fofi and
/usr/include/poppler/splash include headers that are in
/usr/include/poppler/goo through lines of the form #include "goo/foobar.h"
These
lines are broken and need to be replaced with lines of the form #include
"../goo/foobar.h".

This can be fixed by running:
sed -i 's/#include "goo\//#include "..\/goo\//g' *h
inside usr/include/poppler/fofi and /usr/include/poppler/splash



-- System Information:
Debian Release: 6.0.1
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpoppler-dev depends on:
ii  libfontconfig1-dev2.8.0-2.1  generic font configuration
library
ii  libpoppler5   0.12.4-1.2 PDF rendering library

libpoppler-dev recommends no packages.

libpoppler-dev suggests no packages.

-- no debconf information

Bug#619344: Not ready for multiarchified libx11-dev

[Steve Langasek]

On Wed, Mar 30, 2011 at 03:13:00PM +0200, Stéphane Glondu wrote:
> Le 23/03/2011 21:02, Steve Langasek a écrit :
> >[...] But it does fix the
> >problem, though it can't really be applied to ocaml until dpkg 1.16.0 is
> >uploaded to Debian.

> Does it really matter that /usr/lib/`dpkg-architecture
> -qDEB_HOST_MULTIARCH` is used? Wouldn't using something like
> `pkg-config
> --variable=libdir x11` be better? The versioned dependency on dpkg
> is not good for backports...

Well, you could drop the versioned build-dep; 'dpkg-architecture
-qDEB_HOST_MULTIARCH' will return nothing (except on stderr) in older dpkg
versions.  Or, yes, you could use pkg-config.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#620178: noshell: Transitional package for non-free package should live in non-free

[Javier Fernández-Sanguino Peña]

On Wed, Mar 30, 2011 at 11:53:13AM -0700, Josh Triplett wrote:
> Package: noshell
> Severity: serious
> 
> As a transitional package for the non-free titantools, noshell depends
> on titantools.  Thus, noshell should not live in main.  As a
> transitional package for a non-free package it should go in non-free.

You are right, I will fix it right away.

Regards

Javier


signature.asc
Description: Digital signature

Bug#620152: [f13aab7] Fix for Bug#620152 committed to git

[Anton Gladky]

tags 620152 + pending
thanks

Hello,

 The following change has been committed for this bug by
 Anton Gladky  on Thu, 31 Mar 2011 01:18:01 +0100.
 The fix will be in the next upload. 
=
Fix typo in the .desktop file (Closes: #620152). Thanks: Andrea Carpineti 



=

You can check the diff of the fix at:


http://git.debian.org/?p=debian-science/packages/freemat.git;a=commitdiff;h=f13aab7





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

Bug#619236: [Cbe-oss-dev] Bug#619236: installation-reports: installation works fine on PS3 now, but we still can't boot after the installation

[Geoff Levand]

On 03/22/2011 02:29 AM, Antonio Ospite wrote:
> Hi,
> 
> the installation on PS3 now completes pretty fine, however there are 
> still some details that could be improved.
> 
> The installer warns about the boot loader not being installed, which is 
> fine, I already had the 'petitboot' bootloader installed, but some 
> configuration is still needed to make the system actually boot _after_ 
> the installation.
> 
> petitboot needs a /etc/kboot.conf in the root filesystem with this 
> content to successfully boot the installed system:
> 
> linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1 quiet
> 

I could successfully do a gnome desktop install using the
20110329 daily:

  
http://cdimage.debian.org/cdimage/daily-builds/daily/20110329-5/powerpc/iso-cd/debian-testing-powerpc-netinst.iso

I encountered the same problems as Antonio.  Once the installer
was finished, but before it rebooted the system I used this from
a tty console:

  echo 'linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1' > 
/target/etc/kboot.conf

-Geoff




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

Bug#620059: #620059: nfs-kernel: Starting NFS kernel daemon: nfsd mountd failed!

[Pablo Aguiar]

Hi,

I confirm, replacing portmap with rpcbind worked for me too.

Thanks Rolland.

Regards,
-- 
Pablo S. Blum de Aguiar 
Free/Open Source Software Developer/Consultant
FOSS Infrastructure Specialist


 

Bug#613056: Please compile gmsh with support for .med files

[Sylvestre Ledru]

Le mercredi 30 mars 2011 à 17:02 +0200, Anton Gladky a écrit :
> Please, have a look at rev.38287. Is it ok?
> 
> Also libhdf5-openmpi-dev is not available for all platforms, will we
> not have problems with that?
> http://packages.debian.org/sid/libhdf5-openmpi-dev
You are right. The correct package is mpi-default-dev here.
Thanks! Compilation is started!

Sylvestre





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

Bug#594800: Bug#594802: ITP: 0ad-data -- 3D real-time strategy (RTS) game of ancient warfare

[Vincent Cheng]

Hi,

Are there any updates on this? I'm interested in seeing 0 A.D. in Debian's
repositories as well; would you like any help in packaging it?

Kind regards,
- Vincent Cheng

Bug#619827: linux-source-2.6.38: [linux-dvb] cx88-blackbird broken (since 2.6.37)

[Andreas Huber]

Ok, thanks!

On 30.03.2011 23:43, Ben Hutchings wrote:

All mail regarding Debian bugs should be cc'd to the bug address (in
this case, 619...@bugs.debian.org).

I am not going to spend more time trying to fix this, as I don't know
the media/DVB system well and do not have the hardware in question.  I
will forward your information to the upstream developers.

Ben.






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

Bug#616081: atl1c fails to force 100 full duplex

[Ben Hutchings]

On Wed, 2011-03-02 at 12:46 +0100, luca boncompagni wrote:
> I can't get more 100FD from my network card when running on 2.6.37, if
> I boot on 2.6.32 it works fine.
> 
> If i try to use mii-tool eth1 -F 100baseTx-FD I get the warning at the
> end of dmesg.

This is the usual TX watchdog warning.

> If I try to use ethtool I get no warning but it does not set full duplex.
[...]

Luca later reported that this is still broken in 2.6.38.  His full bug
report is at .

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#619546: php5-fpm init script failing with error code 1 regardless of failure

[Eusebi Giampaolo]

I haven't read all the thread but /etc/init.d/php5-fpm doesn't start
php5-fpm on boot (while it start it if called from the shell)..

I resolved the problem swapping the first two lines of the "start" case
in /etc/init.d/php5-fpm.. something like:

[patch]
*** php5-fpm2011-03-30 23:57:31.989484928 +0200
--- /etc/init.d/php5-fpm2011-03-30 23:58:21.073525751 +0200
***
*** 109,116 
  
  case "$1" in
  start)
-   do_check $VERBOSE
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
case "$?" in
0)
do_start
--- 109,116 
  
  case "$1" in
  start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
+   do_check $VERBOSE
case "$?" in
0)
do_start
[/patch]

I think php5-fpm isn't starting because you're testing the return value
of the wrong line..

Am i right?

Sorry for my english,
by the way thanks for your work.

Eusebi Giampaolo




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

Bug#620192: incomplete udev rules for libdlm3

[Aurelien Requiem]

Package: libdlm3
Version: 3.0.12-2
Severity: important


hi,

After upgrading to squeeze, I had 2 problems with the redhat cluster suite.
1 - Apparently, there's a missing udev rule in /etc/udev/rules.d/45-dlm.rules
about dlm-monitor device. This seems to prevent file systems to be mounted.
To fix the issue, I copied the "dlm-control" and after a reboot this fixed
the problem.
I noticed the problem via dlm_controld reporting this problem
  dlm_controld[920]: cannot find device /dev/misc/dlm-monitor with minor 57

2 - a boot time, udevd-work complains about a discrepancy with the kernel and
the udev rules. Messages are like this one.
  udevd-work[1511]: kernel-provided name 'dlm-control' and NAME= 
'misc/dlm-control' disagree, please use SYMLINK+= or change the kernel to 
provide the proper name
After checking found this :
  https://bugzilla.redhat.com/show_bug.cgi?id=667710
I changed the above mentioned files as follow to remove all the warnings.
  KERNEL=="dlm-control", SYMLINK+="misc/dlm-control", MODE="0666"
  KERNEL=="dlm-monitor", SYMLINK+="misc/dlm-monitor", MODE="0666"
  KERNEL=="dlm_default", SYMLINK+="misc/dlm_default", MODE="0666"
  KERNEL=="dlm_*", SYMLINK+="misc/%k", MODE="0660"
After a reboot,  all was ok.

To add up a bit. I performed an upgrade from lenny. I never touched the udev 
rule in the past.


-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libdlm3 depends on:
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  libldap-2.4-2   2.4.23-7 OpenLDAP libraries
ii  libxml2 2.7.8.dfsg-2 GNOME XML library

libdlm3 recommends no packages.

libdlm3 suggests no packages.

-- no debconf information



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

Bug#618391: [compiz] "env --unset GNOME-DESKTOP-SESSION-ID compiz --replace" works well

[Katsuhiko Nishimra]

Package: compiz
Version: 0.9.2.1+git20110226.f059fae9-4

Hi.

Still suffering this problem with binary from experimental distribution.
However, I found that compiz works well with GNOME-DESKTOP-SESSION-ID
environment variable unset.
It seems to be a problem on compizconfig-backend-gconf, so reassigned.

GNOME-DESKTOP-SESSION-ID contains 'this-is-deprecated' in my environment.
Any help?
Thanks in advance.

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.38-2-amd64

Debian Release: wheezy/sid
  500 unstableftp.nara.wide.ad.jp
  500 unstabledebian-multimedia.org
  500 stable  security.debian.org
  500 stable  dl.google.com
  200 experimentalftp.nara.wide.ad.jp
 1001 unstablerepository.glx-dock.org

--- Package information. ---
Depends  (Version) | Installed
==-+-
compiz-core(>= 0.9.2.1+git20110226.f059fae9-4) |
0.9.2.1+git20110226.f059fae9-4
compiz-plugins (>= 0.9.2.1+git20110226.f059fae9-4) |
0.9.2.1+git20110226.f059fae9-4
compiz-gnome   |
0.9.2.1+git20110226.f059fae9-4
 OR compiz-kde |
compiz-fusion-plugins-main(>= 0.9) |
0.9.2.1+git20110224.g4a6783f-2
libcompizconfig0  (>= 0.9) |
0.9.2.1+git20110226.78a7cc8c-1


Package's Recommends field is empty.

Suggests   (Version) | Installed
-+-===
compizconfig-settings-manager| 0.9.2.1+git20110224.cb1268cb-1

-- 
Katsuhiko Nishimra

ktns...@gmail.com



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

Bug#616081: linux-image-2.6.37-2-amd64: atl1c fail to force 100 full duplex

[Ben Hutchings]

On Mon, 2011-03-07 at 10:21 +0100, luca boncompagni wrote:
> On Sun, Mar 6, 2011 at 5:21 PM, Ben Hutchings  wrote:
> > On Wed, 2011-03-02 at 19:26 +0100, luca boncompagni wrote:
> >> Yes,
> >>
> >> with ethtool I use "autoneg off", but if I veirfy this I get
> >> "Auto-negotiation: on".
> >
> > Disabling autoneg is a silly thing to do, but it ought to work.
> >
> > Please test version 2.6.37 as packaged in unstable.
> >
> > Ben.
> >
> 
> Hi,
> 
> I'm running version 2.6.37-2-amd64, I think this is unstable package.

Sorry, I misread your report.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#618320: kfreebsd: invalid a.out header

[Miguel Figueiredo]

A Segunda 14 Março 2011 11:13:02 Miguel Figueiredo você escreveu:

[...]

> Initial boot menu is displayed but booting gives the following error:
> error: invalid a.out header
> error: only ELF kernel supports module.
> 
> screen image available on: http://i.imgur.com/bVjfW.png
> 

An update on the issue:
 
22:11 < cjwatson> elmig: I think that's fixed in unstable
22:11 < cjwatson> it sounds a bit like this from 1.99~rc1-6:
22:11 < cjwatson> - Account for FreeBSD module headers when calculating 
  allocation size.
22:12 < cjwatson> (25 Mar)
22:12 < cjwatson> 1.99~rc1-8 should generally be happy on kfreebsd

daily images are still using 1.99~rc1-3.


-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org



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

Bug#620191: initscripts: [patch] Please support top-level /run

[Roger Leigh]

Package: initscripts
Version: 2.88dsf-13.1
Severity: normal
Tags: patch

Note: blocked by #620157 and will require versioned dependency on
base-files once it adds top-level /run.

/run is a new cross-distribution location for the storage of
transient writable files needed from system startup to shutdown, but
which do not require preserving across reboots.  This location is
a replacement for several existing locations in the filesystem
hierarchy:

/var/run (→ /run)
/var/lock (→ /run/lock)
/lib/init/rw (→ /run/init)
/dev/.* (→ /run/*)
/dev/shm/.* (→ /run/*)
writable files under /etc (→ /run/*)

Note files abusing /dev and /dev/shm are in contravention of the
FHS; this provides a location for them in the heierarchy.  It
also provides a location for distribution-specific solutions such
as Debian's /lib/init/rw.  /run will be a cross-distribution location
and is now also used by Fedora/SuSE and others will also be using it.
It's also been proposed to the FHS for standardisation.

https://lwn.net/Articles/436012/
http://thread.gmane.org/gmane.linux.redhat.fedora.devel/146976
http://bugs.freestandards.org/show_bug.cgi?id=718
http://lists.debian.org/debian-devel/2011/03/msg01118.html
http://lists.debian.org/debian-devel/2011/03/msg01119.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620157

The attached patch contains a detailed changelog of the changes, so
I won't repeat it here verbatim.  Outstanding issues are marked
TODO, and may require further discussion to resolve them.

One issue is how best to handle the transition for wheezy.  The
patch takes the most conservative approach, modelled on the
/lib/init/rw approach.  /run is not used until a system reboot, at
which point /etc/init/rcS.d will handle setup.  I create a
compatibility bind mount from /run/init to /lib/init/rw.  I've
currently left out bind mounts/symlink of /var/run and /var/lock;
I'd link to get consensus on how best to handle migration before
doing this last small bit.

We could bind mount if a directory, and create symlinks if not,
or they do not exist (to handle new installs).  But, base-files
will also need to drop these locations from itself so we can
co-opt them.

We could take a less conservative approach and do the migration in
one shot, setting up bind mounts from the existing locations to
/run, which would allow other packages to simply have a versioned
dependency on initscripts to start using /run, rather than waiting
until after wheezy to rely upon it.  But this has a much greater
potential for pain and trouble.  But is certainly feasible on
Linux by doing the following:

  check for /lib/init/rw/.ramfs
(not in a chroot or bootstrap env; OK to continue)
  bind mount /var/run on /run
create /run/init and /run/lock
  bind mount /var/lock on /run/lock
  bind mount /lib/init/rw on /run/init

However, we only want to do this once only on initial upgrade;
we don't want to repeat this, or do it following a reboot, or
else things will get seriously screwy.  Note it also needs to
cope with /var/lock and /var/run being symlinks or separately
mounted filesystems; if separately mounted we can mount --move
them and replace with symlinks.


Regards,
Roger

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

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

Versions of packages initscripts depends on:
ii  coreutils   8.5-1GNU core utilities
ii  debianutils 3.4.4Miscellaneous utilities specific t
ii  libc6   2.11.2-13Embedded GNU C Library: Shared lib
ii  lsb-base3.2-27   Linux Standard Base 3.2 init scrip
ii  mount   2.17.2-9.1   Tools for mounting and manipulatin
ii  sysv-rc 2.88dsf-13.1 System-V-like runlevel change mech
ii  sysvinit-utils  2.88dsf-13.1 System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs 1.41.12-2  ext2/ext3/ext4 file system utiliti
ii  psmisc22.13-1utilities that use the proc file s

initscripts suggests no packages.

-- no debconf information
diff -urN sysvinit-2.88dsf.original/debian/changelog sysvinit-2.88dsf/debian/changelog
--- sysvinit-2.88dsf.original/debian/changelog	2011-03-30 16:46:27.675265266 +0100
+++ sysvinit-2.88dsf/debian/changelog	2011-03-30 22:29:57.414026872 +0100
@@ -1,3 +1,68 @@
+sysvinit (2.88dsf-14) unstable; urgency=low
+
+  * Support for new top-level directory /run to replace /var/run,
+/var/lock and /lib/init/rw as a place to store transient
+writable data which should not be preserved across a system
+reboot.  Summary:
+  /var/run → /run
+  /var/lock → /run/lock
+  /lib/init/rw → /run/init
+These changes do not take effect until the sys

Bug#601074: llvm: version 2.8 available, please package

[Sylvestre Ledru]

Le mercredi 30 mars 2011 à 23:56 +0200, Witold Baryluk a écrit :
> On 03-30 23:21, Sylvestre Ledru wrote:
> > Le mercredi 30 mars 2011 à 23:09 +0200, Witold Baryluk a écrit :
> > > Hi.
> > > 
> > > Any progress on packaging llvm 2.8?
> > http://ftp-master.debian.org/new/llvm-2.8_2.8-1.html
> > It is in new (for about a month).
> 
> Thanks.
> 
> I somehow overlooked it (was looking at Arturh Loiret's
> qu page, but found only llvm-2.7. I was also checking buildd
> for experimental but found nothing). Now i see I should
> check LLVM Packaging Team page actually. :)
No worries

> Any reasons llvm-2.8 and many other packages, not entered
> unstable/experimental yet? Some ongoing transitions in archive?
Package names changed, it has to be checked by the ftpmaster team ... Usually,
for such changes, it is faster but not this time...

> I cannot use uploaded amd64 binaries anyway, so still
> will build and test it myself.
Please let me know how it goes!

Sylvestre





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

Bug#620190: /usr/bin/rebuild-gcj-db: line 58: gcj-dbtool-4.5: command not found

[Miguel Landaeta]

Package: libgcj-common
Version: 1:4.4.5-6
Severity: important

As title says. This makes libecj-java-gcj uninstallable and causes
FTBFS on mule.

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

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

Versions of packages libgcj-common depends on:
ii  python2.6.6-12   interactive high-level object-orie

libgcj-common recommends no packages.

libgcj-common suggests no packages.

-- no debconf information

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche



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

Bug#601074: llvm: version 2.8 available, please package

[Witold Baryluk]

On 03-30 23:21, Sylvestre Ledru wrote:
> Le mercredi 30 mars 2011 à 23:09 +0200, Witold Baryluk a écrit :
> > Hi.
> > 
> > Any progress on packaging llvm 2.8?
> http://ftp-master.debian.org/new/llvm-2.8_2.8-1.html
> It is in new (for about a month).

Thanks.

I somehow overlooked it (was looking at Arturh Loiret's
qu page, but found only llvm-2.7. I was also checking buildd
for experimental but found nothing). Now i see I should
check LLVM Packaging Team page actually. :)

Any reasons llvm-2.8 and many other packages, not entered
unstable/experimental yet? Some ongoing transitions in archive?

I cannot use uploaded amd64 binaries anyway, so still
will build and test it myself.

Regards,
Witek

-- 
Witold Baryluk


signature.asc
Description: Digital signature

Bug#620152: [9a44bc9] Fix for Bug#620152 committed to git

[Anton Gladky]

tags 620152 + pending
thanks

Hello,

 The following change has been committed for this bug by
 Anton Gladky  on Thu, 31 Mar 2011 00:41:58 +0100.
 The fix will be in the next upload. 
=
Fix typo in the .desktop file (Closes: #620152). Thanks: Andrea Carpineti 



=

You can check the diff of the fix at:


http://git.debian.org/?p=debian-science/packages/freemat.git;a=commitdiff;h=9a44bc9





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

Bug#620083: 'binary-alpha' also missing

[Dominique Brazziel]

Thanks for the quick reply.  The errors are back again today,
they are for the security updates.  I wish there was a way to 
manually remove the references, but I don't know which file(s)
to alter (Release?), and they'd only be reloaded the next day
anyway I suppose.

Last night and today I re-ran the maint job from the acng web page and
unchecked the 'abort on error' flag and checked the 'force
download' flag and that made for clean runs.  

 
  




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

Bug#620189: perl: please include multiarch lib dirs at build time

[Steve Langasek]

Package: perl
Version: 5.10.1-17
Severity: normal
Tags: patch
User: vor...@debian.org
Usertags: multiarch

Hi folks,

Please consider applying the attached patch to perl in Debian; this (or
something like it) is needed to let perl build on a system whose libraries
are converted to use the multiarch directories.  Since this transition is
expected to start in Debian unstable as soon as dpkg 1.16.0 is uploaded, it
would be great if perl could be fixed for this early.

This patch will be uploaded shortly to Ubuntu with the following
explanation in the changelog:

  * debian/config.debian: pass multiarch paths to the build (if 
available) so that we're able to find libraries needed to build.
LP: #739693.

It is safe to apply this change in advance of the dpkg 1.16.0 upload.  With
a pre-multiarch dpkg, dpkg-architecture -qDEB_HOST_MULTIARCH returns nothing
and the build should proceed normally, ignoring these dirs.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru perl-5.10.1/debian/config.debian perl-5.10.1/debian/config.debian
--- perl-5.10.1/debian/config.debian	2011-02-11 10:07:36.0 -0800
+++ perl-5.10.1/debian/config.debian	2011-03-30 13:51:34.0 -0700
@@ -10,6 +10,7 @@
 ccflags=-DDEBIAN
 arch_cpu=${DEB_BUILD_ARCH_CPU:-$(dpkg-architecture -qDEB_BUILD_ARCH_CPU)}
 gnu_type=${DEB_BUILD_GNU_TYPE:-$(dpkg-architecture -qDEB_BUILD_GNU_TYPE)}
+multiarch_dir=${DEB_HOST_MULTIARCH:-$(dpkg-architecture -qDEB_HOST_MULTIARCH 2>/dev/null)}
 optimize=-O2
 debugging=-g
 
@@ -80,6 +81,10 @@
 	optimize="$optimize${optimize:+ }-O0";;
 esac
 
+if [ -n "$multiarch_dir" ]; then
+	extra_path="\"-Dplibpth=/lib/$multiarch_dir /usr/lib/$multiarch_dir\""
+fi
+
 # post-configure tweaks
 cp debian/config.over .
 
@@ -113,4 +118,5 @@
 -Uusenm	\
 -DDEBUGGING=$debugging			\
 -Doptimize=\"$optimize\"			\
+$extra_path	\
 $opts -des

Bug#620109: Policy §3.5 (on Pre-Depends) does not reflect actual practice

[Jonathan Nieder]

Steve Langasek wrote:

>  1. get more eyeballs on the proposed change, to spot problems which the
> added pre-dep may cause
>
>  2. inform the wider Debian developer community about the change, so they
> can factor it into any plans they have for changing their *own* package
> relationships that might subsequently cause a problem for system
> upgrades.
>
> A discussion on debian-release partly satisfies the need for 1) and
> addresses 2) not at all.

Good point.  In this example it sounds like a useful discussion to
have on debian-devel, anyway.  Sorry for the overreaction.

As for policy §3.5 in general: I have a lingering fear about policy
drifting from reality (and our procedures becoming less obvious as a
result).  How policy §3.5 works in practice also seems worrisome to me
(since pre-depends often are added without discussion on -devel), but
maybe that says more about debian-devel than about the policy.
Discussions on -devel are hard to wrap up nicely, probably because
people are afraid of spamming each other.

So, new proposal.  Before adding new Pre-Depends,

 A. there should be a discussion on debian-devel or debian-release,
to get eyeballs on the change and spot problems and easier
alternatives;

 B. debian-devel or debian-devel-announce should be at least notified,
so other Debian developers can factor it into any plans they have
for changing their own package relationships.

In particular, this proposal would drop the requirement of consensus.
Package maintainers generally know what's best; if not, there are
other ways to deal with that (e.g., convincing them, or referring the
issue to the ctte if the maintainer is beyond convincing).

Thanks for some clarity.



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

Bug#600957: linux-image-2.6.32-5-amd64: Please include vmw_pvscsi (VMware PVSCSI)

[Ben Hutchings]

On Wed, 2011-03-30 at 07:34 +0200, Friedemann Stoyan wrote:
> After installing 2.6.32-32:
> 
> $ dpkg -l linux-image-2.6.32-5-amd64
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version
> Description
> +++--==
> ii  linux-image-2.6.32-5-amd64   2.6.32-32 Linux 2.6.32 for 64-bit PCs
> 
> it seems, that vmw_pvscsi isn't enabled in this kernel:
> 
> $ grep CONFIG_VMWARE_PVSCSI /boot/config-2.6.32-5-amd64 
> # CONFIG_VMWARE_PVSCSI is not set
> 
> Please reopen the bug.

Sorry, somewhere along the line I managed to retype this as
CONFIG_SCSI_VMWARE_PVSCSI=m, which of course is ignored.

Reopened and will be fixed in the next upload (very shortly).

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#601074: llvm: version 2.8 available, please package

[Sylvestre Ledru]

Le mercredi 30 mars 2011 à 23:09 +0200, Witold Baryluk a écrit :
> Hi.
> 
> Any progress on packaging llvm 2.8?
http://ftp-master.debian.org/new/llvm-2.8_2.8-1.html
It is in new (for about a month).

Sylvestre




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

Bug#611410: me too

[dann frazier]

Just a note to say that I'm also seeing this bug, and Loïc's patch
works for me too. Thanks Loïc!



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

Bug#582282: yasm update also needed for mozilla

[Zack Weinberg]

Mozilla development trunk just picked up a requirement for yasm >=1.1.



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

Bug#601074: llvm: version 2.8 available, please package

[Witold Baryluk]

Hi.

Any progress on packaging llvm 2.8?

Or maybe now, given release of llvm 2.9 in April, we should
target a 2.9.

I'm asking because ldc is built using llvm 2.6, and
acording to my analysis of buildd logs, it cannot compile for examplpe
libtango on few architectures including alpha.
So it could be fixed in newer version of llvm
(as error looks to be in llvm backend or middleend).

Build errors when incoking ldc on various architectures:

hurd-i386:   

Error: target 'i486-pc-gnu' is not yet supported

hppa:

Error: failed to auto-select target: Unable to find target for this triple (no 
targets are registered), please use the -march option

s390:

Error: failed to auto-select target: Unable to find target for this triple (no 
targets are registered), please use the -march option

sparc:   

Error: invalid cpu architecture specified: sparc

alpha:

Call result #1 has unhandled type i64UNREACHABLE executed at 
/build/buildd-llvm_2.6-5-alpha-Nsbqnj/llvm-2.6/lib/CodeGen/SelectionDAG/CallingConvLower.cpp:148!
0   ldc 0x000120a11524
1   ldc 0x000120a12000
2   libpthread.so.0 0x02047880
3   libc.so.6.1 0x02359d68 gsignal + 88
4   libc.so.6.1 0x0235e3ec abort + 348
5   ldc 0x0001209eddc4 llvm::llvm_unreachable_internal(char 
const*, char const*, unsigned int) + 836
6   ldc 0x00012032c6b0 
llvm::CCState::AnalyzeCallResult(llvm::SmallVectorImpl 
const&, bool (*)(unsigned int, llvm::EVT, llvm::EVT, 
llvm::CCValAssign::LocInfo, llvm::ISD::ArgFlagsTy, llvm::CCState&)) + 528
7   ldc 0x000120319d64 
llvm::AlphaTargetLowering::LowerCallResult(llvm::SDValue, llvm::SDValue, 
unsigned int, bool, llvm::SmallVectorImpl const&, 
llvm::DebugLoc, llvm::SelectionDAG&, llvm::SmallVectorImpl&) + 
180
8   ldc 0x00012031bb14 
llvm::AlphaTargetLowering::LowerCall(llvm::SDValue, llvm::SDValue, unsigned 
int, bool, bool, llvm::SmallVectorImpl const&, 
llvm::SmallVectorImpl const&, llvm::DebugLoc, 
llvm::SelectionDAG&, llvm::SmallVectorImpl&) + 4852
9   ldc 0x00012036f498 
llvm::TargetLowering::LowerCallTo(llvm::SDValue, llvm::Type const*, bool, bool, 
bool, bool, unsigned int, unsigned int, bool, bool, llvm::SDValue, 
std::vector >&, llvm::SelectionDAG&, 
llvm::DebugLoc) + 3752
10  ldc 0x0001203794d8 
llvm::SelectionDAGLowering::LowerCallTo(llvm::CallSite, llvm::SDValue, bool, 
llvm::MachineBasicBlock*) + 1368
11  ldc 0x000120383a28 
llvm::SelectionDAGLowering::visitCall(llvm::CallInst&) + 1096
12  ldc 0x000120393400 
llvm::SelectionDAGLowering::visit(unsigned int, llvm::User&) + 336
13  ldc 0x000120393888 
llvm::SelectionDAGLowering::visit(llvm::Instruction&) + 40
14  ldc 0x0001203a697c 
llvm::SelectionDAGISel::SelectBasicBlock(llvm::BasicBlock*, 
llvm::ilist_iterator, 
llvm::ilist_iterator) + 396
15  ldc 0x0001203a7284 
llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function&, 
llvm::MachineFunction&, llvm::MachineModuleInfo*, llvm::DwarfWriter*, 
llvm::TargetInstrInfo const&) + 1988
16  ldc 0x0001203a8b98 
llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) + 1992
17  ldc 0x0001204d92e4 
llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + 116
18  ldc 0x000120984b44 
llvm::FPPassManager::runOnFunction(llvm::Function&) + 724
19  ldc 0x000120985080 
llvm::FunctionPassManagerImpl::run(llvm::Function&) + 192
20  ldc 0x00012098538c 
llvm::FunctionPassManager::run(llvm::Function&) + 108
21  ldc 0x0001202d31bc write_asm_to_file(llvm::TargetMachine&, 
llvm::Module&, llvm::raw_fd_ostream&) + 844
22  ldc 0x0001202d64a8 writeModule(llvm::Module*, std::string) 
+ 552
23  ldc 0x0001202ba03c main + 8348
24  libc.so.6.1 0x0234052c __libc_start_main + 236
25  ldc 0x0001201436b8 _start + 56
Stack dump:
0.  Running pass 'Alpha DAG->DAG Pattern Instruction Selection' on function 
'@_D6object8TypeInfo6toHashMFZm'



So at least alpha could be fixed in newer llvm
(there were not so much traffix in lib/Target/Alpha in llvm,
but maybe this is actually bug in other part of llvm,
and is fixed).

Actually similar problem was reported on other 64-bit platform in llvm 2.6
here http://comments.gmane.org/gmane.comp.compilers.llvm.devel/31969 (for 
amd64),
and llvm developers on llvmdev mailing list, thinks this is fixed in
llvm 2.7. I'm not sure it is the same problem, but it looks it can be.



And if problem is still present in newer,
then I will investigate more manually.



Failures on other architectures looks to be general problem
of ldc, which somehow inproperly infers architecture.

How about at least trying building it for experimental?
Some Debian patches will need to be droped, as it was merged upstream,
or wil

Bug#620109: Policy §3.5 (on Pre-Depends) does not reflect actual practice

[Steve Langasek]

On Wed, Mar 30, 2011 at 01:51:40AM -0500, Jonathan Nieder wrote:
> Package: debian-policy
> Version: 3.9.1.0

> Raphael Hertzog wrote[1]:

> > It has been discussed on -release, not on -devel:
> > http://lists.debian.org/debian-release/2011/02/threads.html#00381
> >
> > (I don't think it matters much given that all important stakeholders where
> > involved)

> No strong objection from me.  I guess that suggests we should change
> policy §3.5 at the same time (to permit discussion of Pre-Depends on
> debian-release as an alternative to debian-devel, for example)?

Actually, I was going to reply to your question with an apology and start a
discussion on debian-devel about the pre-depends.  I don't think
debian-release is a substitute.

I believe the purpose of this policy requirement is twofold.

 1. get more eyeballs on the proposed change, to spot problems which the
added pre-dep may cause

 2. inform the wider Debian developer community about the change, so they
can factor it into any plans they have for changing their *own* package
relationships that might subsequently cause a problem for system
upgrades.

A discussion on debian-release partly satisfies the need for 1) and
addresses 2) not at all.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#463857: hotkey-setup fails thinkpad x60

[Peter]

I get startpar hotkey-setup fails on a thinkpad X60.  I assume its the
same bug, I haven't tried the patch.



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

Bug#620188: gnome-menus: please remove foo2zjs's hplj1020.desktop from blacklisted icons

[Luca Capello]

Package: gnome-menus
Version: 2.30.3-2
Severity: minor

Hi there!

To reduce the differences between the Debian and Ubuntu packages,
foo2zjs maintenance has been moved to the Debian Printing Team.

Given that Ubuntu is not displaying by default the "HPLJ 10xx Replaced
Paper" icon, it was decided to do the same in Debian as well:

  

Could you please remove hplj1020.desktop from the gnome-menus blacklist?
This was introduced back with version 2.30.2-1, since I (as the primary
foo2zjs maintainer) was (and FWIW still am) against such a workaround:

  

Thx, bye,
Gismo / Luca

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

Kernel: Linux 2.6.38-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-menus depends on:
ii  python2.6.6-12   interactive high-level object-orie
ii  python-gmenu  2.30.3-2   an implementation of the freedeskt

gnome-menus recommends no packages.

gnome-menus suggests no packages.

-- no debconf information


pgpG4eFUiIoO1.pgp
Description: PGP signature

Bug#558308: closing 558308

[Sandro Tosi]

Thanks for answering!

On Wed, Mar 30, 2011 at 22:24, Lionel Le Folgoc  wrote:
> In Xfce 4.8, there's a new library called garcon that is responsible for
> building the menu. It should be (fully) xdg compliant, and it supports menu
> merging. However, there's no debian menu ready to be merged (shipped in
> /etc/xdg/menus/applications-merged), so you will probably need to build one
> yourself.

How am I gonna do it? will XFCE ship (or provide somewere (wiki?)) a
doc about create a "custom" debian menu? shouldn't it be available by
default on a... debian system? :)

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



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

Bug#610860: popularity-contest: abnormal termination while a package is uninstalled

[Serafeim Zanikolas]

On Wed, Mar 30, 2011 at 10:46:59PM +0200, Bill Allombert wrote:
[..]
> Well, I have already changed the warning to read:
>   "popcon: file $dpkg_db/$pkg.list is missing\n"

Fine by me, cheers.

-- 
Every great idea is worthless without someone to do the work. --Neil Williams



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

Bug#610860: popularity-contest: abnormal termination while a package is uninstalled

[Bill Allombert]

On Wed, Mar 30, 2011 at 07:45:57PM +0200, Serafeim Zanikolas wrote:
> Hi Bill,
> 
> On Wed, Mar 30, 2011 at 05:46:27PM +0200, Bill Allombert wrote [edited]:
> > As far as I understand, this is a warning, not an anormal termination.
> > Yes, we could check the return value of open, but it this instance I
> > feel that the warning is legitimate.
> 
> Agreed, but the user that sees the warning cannot tell that.
> 
> > For example, if the user set up a cron job that automatically update their 
> > system,
> > it can alert them that there is a conflict.
> > 
> > Please note that this bug was also reported as #555790. I am still not 
> > quite sure
> > how to address it.
> 
> Perhaps add a msg to make it clear that it is normal under certain
> circumstances (along the lines of "failed to open xxx (this is normal if
> dpkg was running at the same time)". This will save you from having to deal
> with such bug reports in the future.

Well, I have already changed the warning to read:
  "popcon: file $dpkg_db/$pkg.list is missing\n"

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



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

Bug#620169: chemical-structures: [INTL:fr] French debconf templates translation update

[Georges Khaznadar]

Thank you Christian, 

it will be part of the next release.

Christian Perrier a écrit :
> Package: chemical-structures
> Version: N/A
> Severity: wishlist
> Tags: patch l10n
> 
> Please find attached the french debconf templates update, proofread by the
> debian-l10n-french mailing list contributors.
> 
> 
> 
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.37-1-686 (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash

> #
> #Translators, if you are not familiar with the PO format, gettext
> #documentation is worth reading, especially sections dedicated to
> #this format, e.g. by running:
> # info -n '(gettext)PO Files'
> # info -n '(gettext)Header Entry'
> #Some information specific to po-debconf are available at
> #/usr/share/doc/po-debconf/README-trans
> # or http://www.debian.org/intl/l10n/po-debconf/README-trans#
> #Developers do not need to manually edit POT or PO files.
> #
> # Christian Perrier , 2010.
> msgid ""
> msgstr ""
> "Project-Id-Version: chemical-structures 2.0\n"
> "Report-Msgid-Bugs-To: chemical-structu...@packages.debian.org\n"
> "POT-Creation-Date: 2011-03-26 12:36+0100\n"
> "PO-Revision-Date: 2010-11-06 23:13+0100\n"
> "Last-Translator: Georges Khaznadar \n"
> "Language-Team: French \n"
> "MIME-Version: 1.0\n"
> "Content-Type: text/plain; charset=UTF-8\n"
> "Content-Transfer-Encoding: 8bit\n"
> "Language: fr\n"
> "Plural-Forms: nplurals=2; plural=(n > 1);\n"
> "X-Generator: Lokalize 1.0\n"
> 
> #. Type: boolean
> #. Description
> #: ../chemical-structures.templates:1001
> msgid "Should apache2 be restarted?"
> msgstr "Faut-il redémarrer Apache 2 ?"
> 
> #. Type: boolean
> #. Description
> #: ../chemical-structures.templates:1001
> msgid ""
> "In order to activate the new configuration, apache2 has to be restarted. You 
> "
> "can also restart apache2 by manually executing 'invoke-rc.d apache2 
> restart'."
> msgstr ""
> "Pour activer la nouvelle configuration, il faut redémarrer Apache 2. "
> "Vous pouvez aussi redémarrer Apache 2 à la main en lançant  « invoke-rc.d "
> "apache2 restart »."
> 
> #~ msgid "Web server to reconfigure automatically:"
> #~ msgstr "Serveur web à reconfigurer automatiquement :"
> 
> #~ msgid ""
> #~ "Please choose the web server that should be automatically configured to "
> #~ "run chemical-structures."
> #~ msgstr ""
> #~ "Veuillez choisir le serveur web à reconfigurer automatiquement pour "
> #~ "exécuter chemical-structures."
> 
> #~ msgid "Chemical-structures supports Apache and Apache2."
> #~ msgstr "Chemical-structures supporte Apache et Apache2."


-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: Digital signature

Bug#619059: severity

[Nicholas Bamber]

severity 619059 grave
thanks

This bug should be reassigned to liblwp-protocol-https-perl once that is 
available. Neither package should go into test until this is resolved.




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

Bug#620187: context-doc-nonfree: Missing 3 manuals

[Manuel García]

Package: context-doc-nonfree
Version: 2009.10.27-1
Severity: normal

envelop.pdf letter.pdf, and pstopdf.pdf are xHTML files which show a "404 Not
Found" message.



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

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

context-doc-nonfree depends on no packages.

context-doc-nonfree recommends no packages.

Versions of packages context-doc-nonfree suggests:
ii  context 2009.11.26-2 powerful TeX format
ii  context-nonfree 2007.03.22-1 Non-free items from the ConTeXt di

-- no debconf information



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

Bug#620154: chromium: Flash plug-in was blocked, out of date

[Jonathan Nieder]

Dale A. Harris wrote:
> On Wed, Mar 30, 2011 at 03:59:53PM -0400, Jonathan Nieder wrote:

>> Just for the record, what version of flashplugin-nonfree do you have
>> installed (or do you have Flash installed from elsewhere)?
>
> 1:2.8.3
>
> I don't have any other flash installed. 
>
[...]
>> See http://crbug.com/70467 for hints, including a
>> command-line option that can be used to disable the version checks
>> completely (with all the caveats that entails).
>
> Okay, yeah, I'm able to use that. 

Thanks, cc-ing the bug log.



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

Bug#620183: more similar errors

[Ralf Treinen]

Hello,

similar errors than the one reported in #620183 occur in the following
cases. I am filing only one bug reports since I suspect a common cause:

libghc6-http-doc and libghc-http-doc
files:
   /usr/share/doc/haskell-http-doc/html/*

libghc6-regex-compat-doc and libghc-regex-compat-doc
files: 
  /usr/share/doc/haskell-regex-compat-doc/html/Text-Regex.html
  /usr/share/doc/haskell-regex-compat-doc/html/doc-index.html
  /usr/share/doc/haskell-regex-compat-doc/html/frames.html
  /usr/share/doc/haskell-regex-compat-doc/html/haddock-util.js
  /usr/share/doc/haskell-regex-compat-doc/html/index-frames.html
  /usr/share/doc/haskell-regex-compat-doc/html/index.html
  /usr/share/doc/haskell-regex-compat-doc/html/mini_Text-Regex.html
  /usr/share/doc/haskell-regex-compat-doc/html/minus.gif
  /usr/share/doc/haskell-regex-compat-doc/html/plus.gif
  /usr/share/doc/haskell-regex-compat-doc/html/src/Text-Regex.html
  /usr/share/doc/haskell-regex-compat-doc/html/src/hscolour.css


libghc6-text-doc and libghc-text-doc
files:
  /usr/share/doc-base/haskell-text-api

libghc6-zlib-doc and libghc-zlib-doc
files:
  /usr/share/doc/haskell-zlib-doc/html/Codec-Compression-GZip.html
  /usr/share/doc/haskell-zlib-doc/html/Codec-Compression-Zlib-Internal.html
  /usr/share/doc/haskell-zlib-doc/html/Codec-Compression-Zlib-Raw.html
  /usr/share/doc/haskell-zlib-doc/html/Codec-Compression-Zlib.html
  /usr/share/doc/haskell-zlib-doc/html/doc-index.html
  /usr/share/doc/haskell-zlib-doc/html/frames.html
  /usr/share/doc/haskell-zlib-doc/html/haddock-util.js
  /usr/share/doc/haskell-zlib-doc/html/index-frames.html
  /usr/share/doc/haskell-zlib-doc/html/index.html
  /usr/share/doc/haskell-zlib-doc/html/mini_Codec-Compression-GZip.html
  /usr/share/doc/haskell-zlib-doc/html/mini_Codec-Compression-Zlib-Internal.html
  /usr/share/doc/haskell-zlib-doc/html/mini_Codec-Compression-Zlib-Raw.html
  /usr/share/doc/haskell-zlib-doc/html/mini_Codec-Compression-Zlib.html
  /usr/share/doc/haskell-zlib-doc/html/minus.gif
  /usr/share/doc/haskell-zlib-doc/html/plus.gif
  /usr/share/doc/haskell-zlib-doc/html/src/Codec-Compression-GZip.html
  /usr/share/doc/haskell-zlib-doc/html/src/Codec-Compression-Zlib-Internal.html
  /usr/share/doc/haskell-zlib-doc/html/src/Codec-Compression-Zlib-Raw.html
  /usr/share/doc/haskell-zlib-doc/html/src/Codec-Compression-Zlib-Stream.html
  /usr/share/doc/haskell-zlib-doc/html/src/Codec-Compression-Zlib.html
  /usr/share/doc/haskell-zlib-doc/html/src/hscolour.css


Cheers -Ralf



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

Bug#620109: Policy §3.5 (on Pre-Depends) does not reflect actual practice

[Jonathan Nieder]

Raphael Hertzog wrote:

> The reason
> we request peer review of Pre-Depends is that they have a cost and should
> not be abused.

Okay.  That's not what policy §3.5 says; it does not say Pre-Depends should
or must be peer-reviewed or that one should examine all aspects when adding
them but simply that there should be

 (1) a discussion on debian-devel, and
 (2) a consensus that adding this particular Pre-Depends is a good idea.

I like your proposed alternative.  Maybe the policy could say that you
"should" (in the policy sense) thoroughly analyze the consequences and
alternatives before adding pre-depends, and that one way to do so (in
a friendly advice sense) is to ask on debian-devel?



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

Bug#619558: Does not need a GPG trustdb (/etc/apt/trustdb.gpg), just the trusted keyring

[David Kalnischkies]

On Sun, Mar 27, 2011 at 03:13, Josh Triplett  wrote:
> On Sat, Mar 26, 2011 at 10:33:17AM +0100, David Kalnischkies wrote:
>> I think this is very similar to --secrect-keyring which isn't really needed,
>> but gpg seems to insist on having it around…
>
> --trustdb-name /dev/null seems to work just fine, as does
> --secret-keyring /dev/null.

It works as long as the keyring isn't changed, but if a key is added or
remove you will get the lovely message:

gpg: fatal: /dev/null: invalid trustdb
secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768

The action is executed non the less, but gpg exits with non-zero status
and i don't think ignoring gpg failures is a good idea…


Best regards

David Kalnischkies



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

Bug#616552: fcgiwrap: Should have settings FCGI_SOCKET_OWNER / FCGI_SOCKET_GROUP

[Maik Zumstrull]

>> Would you mind having a look at
>> http://svn.debian.org/viewsvn/collab-maint/deb-maint/fcgiwrap/trunk/debian/init?revision=18335
>>
>> to see if this is what you're looking for?
>
> That's pretty close to what I'm already using, yes. Thanks.

Just looked over it again, and actually, it's not right.

This part is off:

# Socket owner/group (defaults to FCGI_USER/FCGI_GROUP if not defined)
FCGI_SOCKET_OWNER="www-data"
FCGI_SOCKET_GROUP="www-data"

The settings contradict the comment. Instead, you should do something like

FCGI_SOCKET_OWNER="${FCGI_SOCKET_OWNER:-$FCGI_USER}"
FCGI_SOCKET_GROUP="${FCGI_SOCKET_GROUP:-$FCGI_GROUP}"

after you read the user configuration from /etc/default.

Sorry I didn't catch this the first time.



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

Bug#613293: RFS: svgsalamander (updated, take 3)

[Niels Thykier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2011-03-27 14:24, Nicolas Dandrimont wrote:
> 
> Hi,
> 
> I have contacted upstream with my questions about svgsalamander. He
> answered quickly but I took some time to get back to work.
> 

That happens :) Personally I am still waiting for 25 hour days! >.>

> My latest work is available in pkg-java's git repo :
> git://git.debian.org/pkg-java/svgsalamander.git
> 
> I updated the package for latest upstream (svn rev. 0095). Upstream
> doesn't intend to do and keep track of a formal release, so I'm keeping
> the debian version simple (well, modulo the 00, but anyways...).
> 

I am thinking that 0~svn95 might still be a better version; you never
know what the future brings.  Maybe upstream start making formal
releases if/as more people get involved in it.
  Obviously we could still handle that with an epoch, so using 95 (or
0095) as a version would not be the end of the world for us.

> I removed use of the embedded batik code copy as upstream intends it for
> compatibility with Java5 and older. It is still in the source so the
> copyright info is still there.
> 

If you are "repacking" the source package anyway (which you did for the
PDF), please remove this copy as well.  Since we have lost the "pristine
tar" (or rather, there never was a tarball to begin with?) we might as
well reduce the risks of compiling/using the embedded code copy (not to
mention reduce the size of the tarball).

> I think svgsalamander should be quite ready for upload now.
> 
> Latest source is available from mentors.d.n at
> 
> - URL: http://mentors.debian.net/debian/pool/main/s/svgsalamander
> - Source repository: deb-src http://mentors.debian.net/debian unstable main 
> contrib non-free
> - dget 
> http://mentors.debian.net/debian/pool/main/s/svgsalamander/svgsalamander_0095-1.dsc
> 
> Thanks in advance,
> Nicolas Dandrimont
> 
>  [...]

I also noted a minor thing like "cd $dir && dostuff && cd $(CURDIR)".
The last cd $(CURDIR) is not necessary (every line is executed in a
separate shell).  This is a feature of "make".
  The dh --with maven_repo_helper can be written as "maven-repo-helper".
 Personally I find the dashed version nicer to read (but this is a
"pedantic" personal preference).

Unfortunately I did not have a lot of time to look at it this time
(either?), so no build testing or anything done today.

~Niels

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJNk5C2AAoJEAVLu599gGRCLMQP/jbWBa3fVXFkA8CKCl7LnrcS
PrZMaSptcFpcxj5NKYvLBeHDIh24GFg9/iEksfu/0EWh2e9OzOHOCe9auGB1RW8j
tOiMuQ3Gm/EMFPYze+flr8Kn+pgyxtMarVeGksP5dC3L0X1ZxdJd9LorlH8dX5V1
SzMsYKGFWzP7KSmpR1SreiQu7/r+V066c395v0DcGubBw2ndJpoc6dTGz5GoKnpM
DKZdWbXK0IltBuumRREWkDHUZBmwGs64OAi+aFayD8eDp0UJWcshaWwk8hZBxbdt
FiAv69t2YCoqrYS8WNDuPRZ2r5NLXQJSCWTCOojtnPh+hP1guvf/1iBkkclphdrR
zVmM2NGInOUPbioixjdzzR2tuLag97IQiUIl84z8+RbPz/LxLWfKLUeTUiIJlox9
Wxbg39Wx+Lwm6nTQWCWw1dApMxEaRfkZj6IcKNMZccQHATgjaSMCvZndmXcYiAKQ
5CUV8wB+ypSNuSvrR3SaM1mDd3or02ABamiOogdEXwP523A0+W/xlg9zpVM2nal4
jQsHvg4jtelETTIqyzq2b1jxB11IeTIifmq9RgfioT9QSo7XwBij7OfPwtRux/M5
+7WFD5n9buNforJq4HssZ8Uq4rMmOx83xP9grTDTdh7c6OIOfDCI2X8oH2TSEjS7
lrsvEjyn0FUztkmyYKCQ
=Pg1w
-END PGP SIGNATURE-



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

Bug#620109: Policy §3.5 (on Pre-Depends) does not reflect actual practice

[Raphael Hertzog]

On Wed, 30 Mar 2011, Jonathan Nieder wrote:
> Well, I want to interpret it as meaning *something* --- though I'm not
> filing RC bugs or anything.  I had thought that the general rule is
> that violating a policy "should" is always a bug (either in your
> package or in policy), though not necessarily an important one.

When it's a technical rule true, here it's a matter of process. The reason
we request peer review of Pre-Depends is that they have a cost and should
not be abused.

So when you want to add a Pre-Depends, you come to -devel and you say "I
want to add this pre-depends because of X to achieve Y".

Maybe someone else will respond "you can achieve Y by doing Z instead" in
which case you should generally go for the solution Z because you can
avoid the cost of the pre-dependency.

But if nobody comes up with another solution to your problem, then by all
means go ahead with the Pre-Depends... if it causes upgrade problems, the
discussion might come back later but that's part of the way we work.
But the maintainer is still the one who gets to decide what's done in his
own package.


In the precise case of multi-arch, the pre-dependency has already been
discussed as being preferrable over any alternative solution. They have a
higher cost due to stronger dependencies in all packages with binaries
whereas this solution only requires multiarchified libraries to carry the
pre-dependency.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
  ▶ http://RaphaelHertzog.fr (Français)



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

Bug#620186: Init.d-script leaves mpt-statusd process defunct

[Wicla]

Package: mpt-status
Version: 1.2.0-7
Severity: normal


When /etc/init.d/mpt-statusd is used to stop the daemon it leaves mpt-statusd 
defunct because its parent process isn't properly killed (/usr/bin/daemon 
/etc/init.d/mpt-statusd check_mpt).

-- System Information:
Debian Release: 6.0.1
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mpt-status depends on:
ii  daemon  0.6.4-1  turns other processes into daemons
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip

mpt-status recommends no packages.

Versions of packages mpt-status suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20100314cvs-1 simple mail user agent

-- no debconf information



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

Bug#620185: M-q problem in changelog mode

[Peter Eisentraut]

Package: dpkg-dev-el
Version: 34.1
Severity: normal

Consider this minimal changelog:

"""
PACKAGE (VERSION) UNRELEASED; urgency=low

  * foo
  * bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar
  * baz

 -- Peter Eisentraut   Wed, 30 Mar 2011 23:05:11 +0300
"""

If I move the cursor to the "bar" line and press M-q nothing happens.  If I
insert a blank line between the "bar" and the "baz" lines, then M-q works on
the "bar" line.  That seems wrong.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 
'stable'), (101, 'experimental')
Architecture: i386 (x86_64)

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

Versions of packages dpkg-dev-el depends on:
ii  debian-el 34.1   Emacs helpers specific to Debian u
ii  emacs [emacsen]   23.2+1-7   The GNU Emacs editor (metapackage)
ii  emacs23 [emacsen] 23.2+1-7   The GNU Emacs editor (with GTK+ us

Versions of packages dpkg-dev-el recommends:
ii  wget  1.12-2.1   retrieves files from the web

Versions of packages dpkg-dev-el suggests:
ii  dpkg-dev  1.15.8.10  Debian package development tools

-- no debconf information



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

Bug#620000: imvirt: fails to detect KVM in my squeeze VMs

[Thomas Liske]

Hi,

On 03/29/2011 07:30 AM, Mike Gerber wrote:

Package: imvirt
Version: 0.9.0-4
Severity: important


imvirt fails to detect the KVM hypervisor on my squeeze machines (using
the sid package, too). It seems it can't decide if it's QEMU or KVM. As
KVM is essentially QEMU "on the rocks", it's not a surprise.

   # imvirt
   Unknown
   # imvirt -d
   $VAR1 = {
 'Physical' =>  '0.0232558139534884',
 'KVM' =>  '0.488372093023256',
 'QEMU' =>  '0.488372093023256'
   };

I have started to improve heuristics, and can supply a patch. However,
I would like to ask if I should avoid giving points in the QEMU detection
if KVM is detected or if that strategy is not wanted?

>

Currently I tried to give more and more points based on KVM clues, but
that does not help much and proved to be tedious.


I would prefer to prohibit giving points on false detection. If a 
detector code detects another virtualization flavor it should decrease 
its own rating.



Regards,
Thomas


-- System Information:
Debian Release: 6.0.1
   APT prefers squeeze-updates
   APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages imvirt depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libimvirt-perl0.9.0-4Perl module for detecting several
ii  perl  5.10.1-17  Larry Wall's Practical Extraction

Versions of packages imvirt recommends:
ii  dmidecode 2.9-1.2Dump Desktop Management Interface

imvirt suggests no packages.

-- no debconf information






--
supp...@ibh.de  Tel. +49 351 477 77 30
www.ibh.de  Fax  +49 351 477 77 39

---
Dipl.-Ing. Thomas Liske
Netzwerk- und System-Design


IBH IT-Service GmbH Amtsgericht Dresden
Gostritzer Str. 67a HRB 13626
D-01217 Dresden GF: Prof. Dr. Thomas Horn
Germany VAT DE182302907
---
Ihr Partner für: LAN, WAN IP-Quality, Security, VoIP, SAN, Backup, USV
---
   professioneller IT-Service - kompetent und zuverlässig
---



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

Bug#620184: gdm 2.32.1 released: Upstream fixed vulnerable package

[C. Petersen]

Package: gdm
Version: 2.20.11-2
Severity: important

Upstream fixed with the 2.32.1 release a local exploitable bug  (which
would give root)
in the package:
https://mail.gnome.org/archives/gnome-announce-list/2011-March/msg00107.html

CVE-2011-0727 was assigned for this.

As I do understand it, all packages <2.32.1 are affected.


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

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




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