On Wed, May 10, 2006 at 02:30:37AM +0800, Dan Jacobson wrote:

I really think this is pretty clear:

PERL_UNICODE Equivalent to the -C command-line switch.

so these are equivalent:

%% perl -CSD -le 'print ${^UNICODE}'
31
%% PERL_UNICODE=SD perl -le 'print ${^UNICODE}'
31

I suppose an explicit example wouldn't hurt, although this already comes close:

Dear maintainer of sugarplum,

On 11 Apr 2008 I sent you a notice announcing my intent to upload a
NMU of your package to fix its pending l10n issues, after an initial
notice sent on 26 Mar 2008.

You either agreed for this NMU or did not respond to my notices.

I will now upload this NMU to DELAYED/2-DAY.

The NMU patch is attached to this mail.

The NMU changelog is:

Package: console-common
Version: 0.7.75
Severity: important

I just performed a typical upgrade of my lenny and here's what aptitude
said:

Setting up console-common (0.7.75) ...
Looking for keymap to install:
NONE
unknown keysym 'terminalsigma'
/etc/console/boottime.kmap.gz:135: syntax error
syntax error in map file
key bindings not changed
* Problem when loading /etc/console/boottime.kmap.gz, use install-keymap

I haven't changed anything (as far as I remember) in any file manually...

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (x86_64)

-------- Original Message --------
Subject: milkytracker_0.90.80-1_powerpc.changes REJECTED
Date: Tue, 22 Apr 2008 22:07:21 +0000
From: Joerg Jaspert debian.org>
To: Gürkan Sengün
CC: Debian Installer ftp-master.debian.org>

Hi Maintainer,

rejected, the w32/milkytracker_vs8.zip seems to contain a .dll file and
I miss its source.

Also, you want to put all the various (C) holders and licenses into the
copyright file.

--
bye Joerg

===

If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.

I hope you don't mind, but I did some work on this package as well. Here's
what I've done so far.

[Andres Mejia]
* Make the build output verbose.
* Allow options passed to cmake to be overridable using DEB_CMAKE_OPTIONS.
* Support nostrip option.
* Build "Release" type libraries by default.
* Support building of static libraries.
* Added myself in Uploaders field.
* Set libopenal-dev to depend on binary version.
* Added new todo. Also renamed TODO to TODO.Debian.
* Added README.Debian.

The changes have been committed to SVN of course. I have some questions. Isn't
there going to be a problem with having a binary package (libopenal-dev) in
two source packages? Wouldn't it be better if this package replaced the old
openal package?

--
Regards,
Andres

Package: smb4k
Version: 0.9.2-1
Severity: wishlist

Hi,
Due to general stability issues with unmount I'm experiencing with the 0.9.2
release, plus the authentication issues, could you please package the new
upstream release:

Release Name: 0.9.3

Notes:

Overview:This version comes with a backport from the current development
branch that improves the handling of login information. To achieve this, the
format of the data that is written to the wallet had to be changed and,
thus, Smb4K 0.9.3 is not compatible with earlier versions. The conversion of
the old data will be done automatically. Apart from that two (un)mount
issues and a regression in the network browser have been eliminated.

Hello,

I'm working on an l10n NMU of the wipl package and was considering to
include the patch proposed in that bug report, to make the package
depend on a more recent version of libpcap development files.

However, doing so triggers the following:

checking for extraneous pcap header directories... found -- -I/usr/include added to CPPFLAGS
checking for net/bpf.h... no
configure: error: Header file net/bpf.h not found; if you installed libpcap from source, did you also do "make install-incl"?
make: *** [configure-stamp] Error 1

Indeed, bpf.h is provided in libpcap0.7-dev but not in libpcam0.8-dev.

I don't have the expertise to investigate this further. So, unless
someone with such expertise comes up with a cooked solution, I only
can leave this bug aside...

--

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

Package: kerneloops
Version: 0.10-2
Severity: minor

Rather than using the shipped upstream init script, the Debian init
script should either use Debian policy-compliant logging directly
(e.g. "Starting kerneloops service:" (startup) " kerneloops.\n") or
use the Debian functions in /lib/lsb/init-functions that automate this
process (log_daemon_msg / log_end_msg).

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

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

# Automatically generated email from bts, devscripts version 2.10.26
#
# devscripts (2.10.27) UNRELEASED; urgency=low
#
# * debcheckout: Use the Vcs-* headers from the highest available version
# rather than the first returned by "apt-get source" (Closes: #477386)
#

package devscripts
tags 477386 + pending

Package: aegis
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.

If you do not already use it, you might consider using the
"podebconf-report-po" utility, which helps warning translators about
changes when you modify some debconf templates in your packages.

The usual policy when using it is sending a warning to translators
when you plan to upload a version of your package with debconf
templates changes (even typo corrections). Then leave about one week
for them to update their files (several translation teams have a QA
process which requires time).

podebconf-report-po will take care of sending the translators the
needed material as well as getting the translators adresses from the
PO files. All you have to do is just using the utility..:-)

Example use (from your package build tree):

$ podebconf-report-po