Processed: reassign 897572 to plymouth

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 897572 plymouth 0.9.3-2
Bug #897572 [linux] getrandom hang in early boot prevents plymouth passphrase 
entry
Bug #897958 [linux] getrandom hang in early boot prevents plymouth passphrase 
entry
Bug #898097 [linux] getrandom hang in early boot prevents plymouth passphrase 
entry
Bug reassigned from package 'linux' to 'plymouth'.
Bug reassigned from package 'linux' to 'plymouth'.
Bug reassigned from package 'linux' to 'plymouth'.
No longer marked as found in versions linux/4.16.5-1.
No longer marked as found in versions linux/4.16.5-1.
No longer marked as found in versions linux/4.16.5-1.
Ignoring request to alter fixed versions of bug #897572 to the same values 
previously set
Ignoring request to alter fixed versions of bug #897958 to the same values 
previously set
Ignoring request to alter fixed versions of bug #898097 to the same values 
previously set
Bug #897572 [plymouth] getrandom hang in early boot prevents plymouth 
passphrase entry
Bug #897958 [plymouth] getrandom hang in early boot prevents plymouth 
passphrase entry
Bug #898097 [plymouth] getrandom hang in early boot prevents plymouth 
passphrase entry
Marked as found in versions plymouth/0.9.3-2.
Marked as found in versions plymouth/0.9.3-2.
Marked as found in versions plymouth/0.9.3-2.
> thanks
Stopping processing here.

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

Bug#897572: [PATCH] Copy fontconfig .uuid files to avoid getrandom hang in early boot

[Ben Caradoc-Davies]

Fixes:
Bug#897572: getrandom hang in early boot prevents plymouth passphrase entry
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572

Signed-off-by: Ben Caradoc-Davies 
---
 debian/local/plymouth.hook | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/local/plymouth.hook b/debian/local/plymouth.hook
index fe44511..bde2d2c 100644
--- a/debian/local/plymouth.hook
+++ b/debian/local/plymouth.hook
@@ -99,12 +99,16 @@ case "${THEME_NAME}" in
mkdir -p "${DESTDIR}/usr/share/fonts/truetype/dejavu"
cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
"${DESTDIR}/usr/share/fonts/truetype/dejavu"
cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf  
"${DESTDIR}/usr/share/fonts/truetype/dejavu"
+   cp -a /usr/share/fonts/truetype/dejavu/.uuid 
"${DESTDIR}/usr/share/fonts/truetype/dejavu"
else
# wheezy
mkdir -p 
"${DESTDIR}/usr/share/fonts/truetype/ttf-dejavu"
cp -a 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf 
"${DESTDIR}/usr/share/fonts/truetype/ttf-dejavu"
cp -a 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf  
"${DESTDIR}/usr/share/fonts/truetype/ttf-dejavu"
+   cp -a /usr/share/fonts/truetype/ttf-dejavu/.uuid 
"${DESTDIR}/usr/share/fonts/truetype/ttf-dejavu"
fi
+   cp -a /usr/share/fonts/truetype/.uuid 
"${DESTDIR}/usr/share/fonts/truetype"
+   cp -a /usr/share/fonts/.uuid "${DESTDIR}/usr/share/fonts"
 
# pango
if ls /usr/lib/@DEB_HOST_MULTIARCH@/pango/1* > /dev/null 2>&1
-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#897802: linux: ftbfs with GCC-8

[Ben Hutchings]

Control: tag -1 upstream

These are the relevant error messages:

  CC   
/<>/debian/build/build_amd64_none_amd64/tools/objtool/pager.o
pager.c: In function 'pager_preexec':
pager.c:36:12: error: passing argument 2 to restrict-qualified parameter 
aliases with argument 4 [-Werror=restrict]
  select(1, , NULL, , NULL);
^~~~~~
cc1: all warnings being treated as errors

  CC   
/<>/debian/build/build_amd64_none_amd64/tools/objtool/str_error_r.o
../lib/str_error_r.c: In function 'str_error_r':
../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified 
parameter aliases with argument 5 [-Werror=restrict]
   snprintf(buf, buflen, "INTERNAL ERROR: strerror_r(%d, %p, %zd)=%d", errnum, 
buf, buflen, err);
   ^~~~
cc1: all warnings being treated as errors

These seem to be genuine bugs.

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


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

Processed: Re: Bug#897802: linux: ftbfs with GCC-8

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream
Bug #897802 [src:linux] linux: ftbfs with GCC-8
Added tag(s) upstream.

-- 
897802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Fixing Linux getrandom() in stable

[Ben Hutchings]

# Background

The Linux kernel random number generator (RNG) historically supported
two character devices for reading random data:

* `/dev/urandom`: non-blocking, may be predictable if called soon after
  boot or based on other output
* `/dev/random`: blocking, intended to be cryptographically secure

Since Linux 3.19 it has also supported a `getrandom()` system call,
which provides flags for cryptographically secure behaviour
(`GRND_RANDOM`) and non-blocking behaviour (`GRND_NONBLOCK`). 
Crucially, this call should never return predictable data after boot -
it will either block or return an error, depending on whether
`GRND_NONBLOCK` is used.

# Security flaw and initial fix

Recently it was discovered that getrandom() could return successfully
before the RNG was really ready to produce unpredictable data.  This
issue was designated as CVE-2018-1108, and was fixed in Linux 4.17-rc2 
and various stable updates.

We fixed CVE-2018-1108 with an update to stretch last week
(DSA-4188-1).  The kernel versions in wheezy and jessie do not provide
getrandom().

# Regression

The version of glibc in stretch does not provide access to getrandom(),
but some packages in stable use syscall() to call it anyway, including:

* krb5: k5_get_os_entropy()
* libbsd: arc4_random_buf().  This is used by many other packages
  including libICE, and so indirectly by gnome-session.

Following DSA-4188-1, it turned out that the RNG did not become ready
on some systems until several minutes after boot, causing severe
regressions for GNOME/gdm (#897631, #897632) and Kerberos (#897599,
#897917).  We therefore reverted the fix in yesterday's update
(DSA-4196-1).

# Options for a new fix

It is unlikely that any further fix will be forthcoming on the kernel
side, so I believe that we need to do one of:

1. Add entropy to the kernel during boot; either:
   a. Improve systemd-random-seed
   b. Recommend use of haveged
2. For each affected userland package, either:
   a. Revert to using /dev/urandom
   b. Tolerate a longer wait for getrandom() to return

I asked about haveged on Twitter, and got into a discussion with Jann
Horn (who reported the original issue).  He pointed out that the
systemd-random-seed service already saves and restores some random data
between boots.  It currently doesn't tell the RNG that this should be
treated as adding to available entropy, so it doesn't help to unblock
getrandom().  It also doesn't fully protect against using the same
saved data twice, which would be a prerequisite.

The libbsd maintainer (Guillem Jover) favours option 2a.

One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and
also proposed that systemd could provide a wait-for-rng-ready unit to
support this.

*If* these are the only users in stable, then it may be that it would
be sufficient to do stable updates for them and then for linux.  But
I'm not sure that they are, so we may need to pursue option 1 as well.

I would like to hear opinions from the release team and the systemd
maintainers on these options.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates


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

Bug#897631: marked as done (Kernel update breaks GDM)

[Debian Bug Tracking System]

Your message dated Wed, 09 May 2018 23:22:44 +0100
with message-id <5c94024e3023096fea1172fc1c1a58533b9839c1.ca...@decadent.org.uk>
and subject line [Fwd: Re: Kernel update breaks GDM]
has caused the Debian Bug report #897631,
regarding Kernel update breaks GDM
to be marked as done.

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

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


-- 
897631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.9.0-6-amd64

The update for package linux-image-4.9.0-6-amd64 from 4.9.82-1+deb9u3
to the newest 4.9.88-1 breaks the autostart of GDM. This was on a fresh
install of Debian 9 (stable).

When I did the update after installing I couldn't login with GDM after
reboot, the boot would freeze. And I know that the NVIDIA drivers
(version 375.82-1~deb9u1) weren't loaded because the fan on my graphics
card are ramped up when the NVIDIA driver is not loaded (so when the
driver loads the fan will go silent).

I actually reinstalled the system a couple of times and the error would
occur every single time. Only installing the NVIDIA drivers after
install and not updating works just fine so it's not the NVIDIA drivers
that are erroneous. I found the error by installing updates one by one.
And after updating the kernel the error would appear.

Anyway the system refused to load GDM and the only way I could log in
was by switching to another TTY and log in from the command line.

However soon after logging in (usually by the time I had written a
couple of commands) GDM would start and I could then log in from the
GUI and from then on everything would work just fine. GDM would however
not start if I didn't log in from the command line, instead the system
would just hang indefinetly (I actually left it on for about 30 min
while going on lunch).

I ran 'systemctl status gdm3' right after logging in on TTY2 in and it
stated that it was indeed running but it wouldn't show the login screen
or load the NVIDIA drivers (since my graphics cards fans were going
full blast).

There also was no errors in any logs from what I could see. The gdm3
folder in /var/log was completely empty.

Rolling back to kernel version 4.9.82-1+deb9u3 resolved the problem.
--- End Message ---
--- Begin Message ---
Version: 4.9.88-1+deb9u1

 Forwarded Message 
From: silvio.s...@gmail.com
To: Ben Hutchings 
Subject: Re: Kernel update breaks GDM
Date: Wed, 09 May 2018 21:16:42 +0200
Message-Id: <1525893402.4140.1.camel@localhost>

tis 2018-05-08 klockan 01:07 +0200 skrev silvio.s...@gmail.com:
> > Control: tag -1 moreinfo
> > 
> > On Thu, 03 May 2018 18:59:36 +0200 silvio.s...@gmail.com wrote:
> > [...]
> > > However soon after logging in (usually by the time I had written
> > > a
> > > couple of commands) GDM would start and I could then log in from
> > > the
> > > GUI and from then on everything would work just fine. GDM would
> > > however
> > > not start if I didn't log in from the command line, instead the
> > > system
> > > would just hang indefinetly (I actually left it on for about 30
> > > min
> > > while going on lunch).
> > 
> > [...]
> > 
> > This may sound like a silly request, but does GDM start up if you
> > wiggle the mouse for a few seconds?
> > 
> > Ben.
> > 
> 
> 
> No it doesn't. It starts only if I log in and only if I start typing
> some command in the terminal after I've logged in.
> 
> If I wiggle the mouse for a while it just continues to hang. If I
> just
> log in and don't type any command it doesn't start either. It's
> really
> weird!
> 
> Here's what I've tried so far:
> 
> - I've added the "Debian-gdm" user to "video" group as well, thought
> it
> might help, but it didn't.
> 
> - I updated the NVIDIA driver to both 384.130 and the newest 396-
> version but neither of those helped.
> 
> - If I edit the "/etc/gdm3/daemon.conf"-file and comment out the
> "#WaylandEnable=false"-line the NVIDIA driver does load (I can hear
> the
> fans of my graphics card go silent) but then I get a completely blank
> screen.


Hi again.

The new update to 4.9.88-1+deb9u1 seems to have resolved the problem
for me.

I've had a few reboots now and all seems to be working fine again.

/Silvio


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

Processed: tagging 897631

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 897631 - pending
Bug #897631 [src:linux] Kernel update breaks GDM
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#898074: linux-image-4.9.0-6-amd64: gdm3 fails to start

[Kevin Bube]

I just wanted to verify that I just did not wait long enough for gdm3 to
start. I reinstalled linux-image-4.9.0-6-amd64 and now the issue went
away! So it seems to be some sort of race condition, whatsoever. I
booted at least five times now without a single problem.

Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14

[Ben Hutchings]

On Wed, 2018-05-09 at 22:44 +0300, eHenry Berg wrote:
> Hi,
> 
> This bug report is about linux-image-armmp-lpae. I tested
> linux-image-armmp with versions 4.15.0-3 and 4.16.0-1, it works!
> This bug 884601 can therefore be closed.

The RPi 2 has Cortex-A7 cores, which support LPAE and therefore should
be able to run Debian's armmp-lpae kernel flavour.  So although you
have a way to avoid the bug, I think there's still a bug here.

(I'm not sure about RPi 3 as I don't know to what extent ARM supports
running 32-bit kernels on 64-bit cores.  I would certainly recommend
using the arm64 kernel.)

Ben.

> I am planning to put out a guide for 32-bit and 64-bit how to install
> Debian desktop on Raspberry, but I have another Debian bug 897925
> which means web browsers do not work for 32-bit.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates



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

linux_3.16.56-1_multi.changes REJECTED

[Debian FTP Masters]

Moving back to unchecked, try 2.




===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14

[eHenry Berg]

Hi,

This bug report is about linux-image-armmp-lpae. I tested
linux-image-armmp with versions 4.15.0-3 and 4.16.0-1, it works!
This bug 884601 can therefore be closed.
I am planning to put out a guide for 32-bit and 64-bit how to install
Debian desktop on Raspberry, but I have another Debian bug 897925
which means web browsers do not work for 32-bit.

Best Regards,
Evald

linux_3.16.56-1_multi.changes is NEW

[Debian FTP Masters]

Mapping oldstable-security to oldstable-proposed-updates.
linux_3.16.56-1.debian.tar.xz is only available in NEW.
linux_3.16.56.orig.tar.xz is only available in NEW.
linux_3.16.56-1.dsc is only available in NEW.
linux_3.16.56.orig.tar.xz is only available in NEW.
linux_3.16.56-1.debian.tar.xz is only available in NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

linux_3.16.56-1+deb8u1_multi.changes REJECTED

[Debian FTP Masters]

Moving back to unchecked




===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

linux_3.16.56-1_multi.changes REJECTED

[Debian FTP Masters]

Moving back to unchecked




===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

Bug#897631: Wiggling works!

[Magnus Wallin]

>This may sound like a silly request, but does GDM start up if you>wiggle the 
>mouse for a few seconds?Silly request or not, this actually works.
Tested on three different laptops (Dell, HP and Lenovo),
all running the latest kernel, and all having the same issue 
with GDM.

Would prefer a somewhat more permanent fix than, eh, ”wiggling” :)

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com 

Bug#897632: (Boot timeout after latest security update)

[Miroslav Kure]

Just a quick confirmation - today's update 4.9.88-1+deb9u1 fixed the
boot timeout for me.

-- 
Miroslav Kure

Bug#897572: urandom hang in early boot

[Yves-Alexis Perez]

On Tue, 2018-05-08 at 13:23 +0200, Bjørn Mork wrote:
> And sd_id128_randomize() is called from all over the place.  I haven't
> bothered looking at all the call sites, but would be surprised if not at
> least one of them is unconditionally called at boot.
> 
> If I am correct, then I guess this is a systemd bug?

It might be (I took the liberty to add your findings to https://github.com/sys
temd/systemd/issues/4167).

In our case, as far as I can tell since we're still in the initramfs, systemd
is not yet PID1, but we do use udev which might have the same issue.

Regards,
-- 
Yves-Alexis

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

Bug#897599: Hotfix with haveged

[Alf]

works fine here.
Entropy pool gets filled within a few seconds instead of minutes.

Bug#886858:

[Dennis Heddicke]

The bug is fixed for me with the last kernel update (3.16.0-6-686-pae). 
I don't know if it was a real bug or a side effect of a mixture of 
packages from stable and unstable (among other things libc6). Last week 
i reverted all packages to stable. Maybe this solved the issue. Thank 
you for your help.

Bug#898267: [firmware-misc-nonfree] Missing firmware i915/kbl_dmc_ver1_04.bin

[Alexander Kernozhitsky]

Package: firmware-misc-nonfree
Version: 20170823-1
Severity: minor

Linux kernel shows me the warning at boot time. It looks like "missing 
firmware i915/kbl_dmc_ver1_04.bin", but the package contains i915/
kbl_dmc_ver1_01.bin. A newer kernel requires 1.04 version. Please update the 
firmware.

--- System information. ---
Architecture: 
Kernel:   Linux 4.16.0-1-amd64

Debian Release: buster/sid
  990 testing ftp.by.debian.org 
  500 unstableftp.by.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
initramfs-tools| 0.130
-- 
-
Alexander Kernozhitsky

Bug#893912: firmware-realtek: Failed to load rtl_bt/rtl8821a_config.bin

[Francisco M Neto]

This happens on my machine as well. 

I'm running buster with 4.16 kernel and firmware-realtek is installed.
It seems that this file should be in the package but it hasn't been
include for some reason, even though it is available from https://githu
b.com/lwfinger/rtl8723au_bt/.

Installing the file on /lib/firmware/rtl_bt/ solves the issue.


On Fri, 23 Mar 2018 19:02:48 +0100 "Rathorian" 
wrote:
> Package: firmware-realtek
> Version: 20161130-3
> Severity: important
> 
> Dear Maintainer,
> 
> Every time I start Debian, I get an error message saying:
> "bluetooth hci0: firmware: failed to load rtl_bt/rtl8821a_config.bin"
> 
> I have also tried to install the package since stretch-backports,
without
> any success.
> 
> Cordially
> Rathorian
> 
> -- System Information:
> Debian Release: 9.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
> LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> firmware-realtek depends on no packages.
> 
> firmware-realtek recommends no packages.
> 
> Versions of packages firmware-realtek suggests:
> ii  initramfs-tools  0.130
> 
> -- no debconf information
> 
-- 
--
[]s,

Francisco M Neto

Bug#897572: getrandom hang in early boot prevents plymouth passphrase entry

[Esokrates]

I confirm this issue.
It affects plymouth in general, not related to any passphrase entry.
Booting in recovery mode helps to get around the plymouth problem, but 
if there is not enough entropy gdm3 will simply not start. Pressing 
keys/switching VTs leads to the crng_init finished message to be printed 
and gdm3 starts after that.


Please consider adjusting the importance of the issue, it makes the 
system almost unbootable for regular users.

Bug#887932: firmware-iwlwifi: Bluetooth not working

[Ryan Lue]

Package: firmware-iwlwifi
Version: 20161130-3
Followup-For: Bug #887932

Just a quick follow-up on my last message:

Downgrading to 20161130-3 allows bluetooth devices to connect,
BUT Wi-Fi performance is severely degraded when bluetooth is connected.

Better than nothing, though.


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.130

-- no debconf information

Re: [PATCH v2] kbuild: deb-pkg improve maintainer address generation

[Uwe Kleine-König]

Hello,

On Mon, May 07, 2018 at 10:11:34AM +0300, riku.voi...@linaro.org wrote:
> From: Riku Voipio 
> 
> There is multiple issues with the genaration of maintainer string
> 
> It uses DEBEMAIL and EMAIL enviroment variables, which may contain angle 
> brackets,
> creating invalid maintainer strings. The documented KBUILD_BUILD_USER and
> KBUILD_BUILD_HOST variables are not used. Undocumented and uncommon NAME
> variable is used. Refactor the Maintainer string to:
> 
> - use EMAIL or DEBEMAIL directly if they are in form "name "
> - use KBUILD_BUILD_USER and KBUILD_BUILD_HOST if set before falling
>   back to autodetection
> - no longer use NAME variable or the useless Anonymous string
> 
> The logic is switched from multiline if/then/fi statements to compact
> shell variable substition commands.
> 
> Reported-by: Mathieu Malaterre 
> Signed-off-by: Riku Voipio 
> ---
> v2: include improvements suggested by Masahiro-san
> 
>  scripts/package/mkdebian | 27 +--
>  1 file changed, 13 insertions(+), 14 deletions(-)
> 
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index 6adb3a16ba3b..985d72d1ab34 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -71,22 +71,21 @@ if [ "$ARCH" = "um" ] ; then
>   packagename=user-mode-linux-$version
>  fi
>  
> -# Try to determine maintainer and email values
> -if [ -n "$DEBEMAIL" ]; then
> -   email=$DEBEMAIL
> -elif [ -n "$EMAIL" ]; then
> -   email=$EMAIL
> -else
> -   email=$(id -nu)@$(hostname -f 2>/dev/null || hostname)
> -fi
> -if [ -n "$DEBFULLNAME" ]; then
> -   name=$DEBFULLNAME
> -elif [ -n "$NAME" ]; then
> -   name=$NAME
> +email=${DEBEMAIL-$EMAIL}
> +
> +# use email string directly if it contains 
> +if echo $email | grep -q '<.*>'; then
> + maintainer=$email

Alternatively you can do:

case "$email" in
*\<*\>*)
maintainer="$email"
;;
*)
...

esac

which might be a tad quicker because case is shell-builtin.

>  else
> -   name="Anonymous"
> + # or construct the maintainer string
> + user=${KBUILD_BUILD_USER-$(id -nu)}
> + name=${DEBFULLNAME-$user}
> + if [ -z "$email" ]; then
> + buildhost=${KBUILD_BUILD_HOST-$(hostname -f 2>/dev/null || 
> hostname)}

On Debian machines there is also /etc/mailname which should be preferred
over hostname -f.

Best regards
Uwe

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | http://www.pengutronix.de/  |