Bug#927804: vsftpd fails with config error when set to listen on v4 and v6

[Keng-Yu Lin]

It looks to me that this issue can be fixed by adding a new conf file
and some modification as described in
https://access.redhat.com/solutions/1566213

For the package, probably just some wording changes to the document.

Bug#902959: pluginhook: diff for NMU version 0~20150216.0~a320158-2.1

[Keng-Yu Lin]

Control: tags 902959 + patch
Control: tags 902959 + pending

Dear maintainer,

I've prepared an NMU for pluginhook (versioned as 0~20150216.0~a320158-2.1) and
I am looking for a sponsor to uploaded it to DELAYED/7.
Please feel free to tell me if I should delay it longer.

Regards.
diff -Nru pluginhook-0~20150216.0~a320158/debian/changelog pluginhook-0~20150216.0~a320158/debian/changelog
--- pluginhook-0~20150216.0~a320158/debian/changelog	2015-07-01 15:31:36.0 +0800
+++ pluginhook-0~20150216.0~a320158/debian/changelog	2019-05-28 15:47:36.0 +0800
@@ -1,3 +1,20 @@
+pluginhook (0~20150216.0~a320158-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+- Replace golang-go.crypto-dev with golang-golang-x-crypto-dev
+  in Build-Depends. (Closes: #902959)
+- Bump Standards-Version to 4.3.0
+
+debian/control:
+  - Changed Priority from extra to optional, since the priority
+extra has been deprecated in Debian Policy version 4.0.1.
+
+debian/rules:
+  - override_auto_build to build in PIE mode, fixing the lintian
+warnings: hardening-no-relro and hardening-no-pie.
+
+ -- Keng-Yu Lin   Tue, 28 May 2019 15:47:36 +0800
+
 pluginhook (0~20150216.0~a320158-2) unstable; urgency=medium
 
   * Fix crypto's sub-repo import path (Closes: #790681)
diff -Nru pluginhook-0~20150216.0~a320158/debian/control pluginhook-0~20150216.0~a320158/debian/control
--- pluginhook-0~20150216.0~a320158/debian/control	2015-07-01 15:25:29.0 +0800
+++ pluginhook-0~20150216.0~a320158/debian/control	2019-05-28 15:47:36.0 +0800
@@ -1,14 +1,14 @@
 Source: pluginhook
 Section: utils
-Priority: extra
+Priority: optional
 Maintainer: Alessio Treglia 
 Build-Depends:
  debhelper (>= 9~),
  dh-golang,
  golang-go,
- golang-go.crypto-dev,
+ golang-golang-x-crypto-dev,
  golang-godebiancontrol-dev
-Standards-Version: 3.9.6
+Standards-Version: 4.3.0
 Homepage: http://github.com/progrium/pluginhook
 
 Package: pluginhook
diff -Nru pluginhook-0~20150216.0~a320158/debian/rules pluginhook-0~20150216.0~a320158/debian/rules
--- pluginhook-0~20150216.0~a320158/debian/rules	2015-07-01 15:25:29.0 +0800
+++ pluginhook-0~20150216.0~a320158/debian/rules	2019-05-28 15:47:36.0 +0800
@@ -2,12 +2,14 @@
 
 export DH_OPTIONS
 export DH_VERBOSE=1
-
 export DH_GOPKG := github.com/progrium/pluginhook
 
 %:
 	dh $@ --buildsystem=golang --with=golang
 
+override_dh_auto_build:
+	dh_auto_build -O--buildsystem=golang -- -buildmode=pie
+
 override_dh_auto_install:
 	dh_auto_install
 	rm -rf $(CURDIR)/debian/pluginhook/usr/share

Bug#923721: vsftpd: Libgcrypt warning: missing initialization - please fix the application

[Keng-Yu Lin]

On Mon, 4 Mar 2019 at 20:03, Giorgi Modebadze
 wrote:
>
> Package: vsftpd
> Version: 3.0.3-8+b1
>
> Whenever a client connects to vsftpd, Libgcrypt seems to complain. Output in 
> syslog:
>
> > vsftpd: Libgcrypt warning: missing initialization - please fix the 
> > application
>
>
> Dependencies of vsftpd:
>
> $ ldd /usr/sbin/vsftpd
> linux-vdso.so.1 (0x7fffb43e6000)
> libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 
> (0x7fc652b55000)
> libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x7fc652947000)
> libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 
> (0x7fc6526db000)
> libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 
> (0x7fc652242000)
> libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fc65203c000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc651c9d000)
> libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7fc651a85000)
> libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 
> (0x7fc65185d000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc651659000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
> (0x7fc65143c000)
> /lib64/ld-linux-x86-64.so.2 (0x7fc652f88000)
> libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 
> (0x7fc651236000)
>
> $
>
> I believe Libgcrypt initialization is missing. The maintainers of libgcrypt 
> consider that a bug. Even though the issue seems harmless, it heavily spams 
> the syslog.
>
> I am using Debian GNU/Linux 9 (stretch), kernel 4.19.0-0.bpo.2-amd64 and 
> libc-2.24.so.

Hi there,
  vsftpd does not use libgcrypto directly. From the ldd log, libcrypto
is from openssl (no "g").
  I think this issue should be fixed from PAM.

  From 
https://www.gnupg.org/documentation/manuals/gcrypt/Initializing-the-library.html:

Function: const char * gcry_check_version (const char *req_version)

The function gcry_check_version initializes some subsystems used
by Libgcrypt and must be invoked before any other function in the
library.

  gcry_check_version() does not only check the version, it also
initializes something.

  Can you help re-filing the bug to PAM package?

  Thanks,
-kengyu

Bug#914146: dogecoin: diff for NMU version 1.10.0-7.1

[Keng-Yu Lin]

On Mon, 11 Feb 2019 at 21:12, Mattia Rizzolo  wrote:
>
> Control: tags 914146 + patch
> Control: tags 914146 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for dogecoin (versioned as 1.10.0-7.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

I am happy with the NMU.
Thanks for helping and tidying up the format.

-kengyu

Bug#914146: fixed in dogecoin 1.10.0-6

[Keng-Yu Lin]

On Wed, 2 Jan 2019 at 17:48, Emilio Pozuelo Monfort  wrote:
> Yes, we can't remove it yet because there are some unfixed dependencies. But 
> the
> plan is to remove boost1.62 from buster before the release. So please go back 
> to
> using boost-defaults packages.

Reported to upstream as https://github.com/dogecoin/dogecoin/issues/1564
I will take a look too.

Bug#909380: libvidstab: enable Multi-Arch: same

[Keng-Yu Lin]

Hi James:
  While I worked on the package, salsa was kind of messy for non-DD
contributors. I just checked, it looks much better now. I think I will
use salsa as the vcs repository.

  Can you help grant me the DM permission so that I am able to upload?

  `dcut dm` as described in https://wiki.debian.org/DebianMaintainer

Thanks,
-kengyu

Bug#902609: lmbench: Using int for mmap() may cause integer overflow

[Keng-Yu Lin]

Package: lmbench
Version: 3.0-a9+debian.1-2
Severity: normal
Tags: patch

At last on AMD64, size_t is now ‘long unsigned int’.
Using int type for mmap() can cause the integer overflow.

Please consider including the attached patch.



-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages lmbench depends on:
ii  gcc   4:7.3.0-3ubuntu2
ii  libc6 2.27-3ubuntu1
ii  libc6-dev [libc-dev]  2.27-3ubuntu1
ii  perl  5.26.1-6ubuntu0.1

Versions of packages lmbench recommends:
ii  lmbench-doc  3.0-a9+debian.1-2

lmbench suggests no packages.

-- no debconf information
From a409efbc261ca097b414da7986fc2ea6a35af6dd Mon Sep 17 00:00:00 2001
From: Keng-Yu Lin 
Date: Thu, 28 Jun 2018 18:35:54 +0800
Subject: [PATCH] Use size_t for mmap()
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

At last on AMD64, size_t is now ‘long unsigned int’.
Using int type can cause the integer overflow.

Signed-off-by: Keng-Yu Lin 
---
 src/lat_pagefault.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lat_pagefault.c b/src/lat_pagefault.c
index 66f67cd..0e16ddd 100644
--- a/src/lat_pagefault.c
+++ b/src/lat_pagefault.c
@@ -18,7 +18,7 @@ char  *id = "$Id$\n";
 
 typedef struct _state {
int fd;
-   int size;
+   size_t size;
int npages;
int clone;
char* file;
-- 
2.11.0

Bug#844297: vsftpd (3.0.2-17+deb8u1): no welcome message, problem in /etc/pam.d/vsftpd

[Keng-Yu Lin]

2016-11-14 16:51 GMT+08:00 Alexandre LE GALL :
> Subject: vsftpd (3.0.2-17+deb8u1): no welcome message, problem in 
> /etc/pam.d/vsftpd
> Package: vsftpd
> Version: 3.0.2-17+deb8u1
> Severity: important
>
> Dear Maintainer,
>
> Since I update vsftpd to 3.0.2-17+deb8u1, I can't connect to my ftp server.
> To fix this problem, I comment "@include common-auth " in /etc/pam.d/vsftpd.
>
> My server is a VM with samba (in domain) and vsftpd only.
>
> Thanks for your work.


I use 3.0.3-9 with ftpd_banner="FTP Server Ready" in /etc/vsftpd.conf.
I can't reproduce the issue:

ftp> open 192.168.1.10
Connected to 192.168.1.10.
220 "FTP Server Ready"
Name (192.168.1.10:kengyu):

Bug#838678: vsftpd 3.0.2-17+deb8u1 does not start when allow_writeable_chroot=YES is present in vsftpd.conf

[Keng-Yu Lin]

2016-09-23 22:43 GMT+08:00 Robert Mueller :
> Package: vsftpd
> Version: 3.0.2-17+deb8u1
> Severity: important
>
> Dear Maintainer,
>
> when trying to configure vsftpd to allow it to run with user-writeable chroot 
> directories, the daemon does not start up. Removing the 
> allow_writeable_chroot directive helps, but for my configuration here I 
> really need this to be enabled.
> According to vsftpd upstream changelogs, the directive was added in 2.3.5 and 
> never removed. However, the version provided in jessie does not seem to 
> recognise the option, and it's also not mentioned in the vsftpd.conf manpage.
>
> Is this a bug, or was this option removed intentionally in the Debian build?
>

I just tried vsftpd 3.0.3-9 from Jesse. With allow_writeable_chroot
directive=YES in /etc/vsftpd.conf, vsftpd can start.
I believe this bug is fixed by newer version of vsftpd package.

I will close this bug for now. Feel free to reopen it if you still
encounter the bug.





> -- Package-specific info:
>
> -- System Information:
> Debian Release: 8.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages vsftpd depends on:
> ii  adduser3.113+nmu3
> ii  debconf [debconf-2.0]  1.5.56
> ii  dialog 1.2-20140911-1
> ii  init-system-helpers1.22
> ii  libc6  2.19-18+deb8u6
> ii  libcap21:2.24-8
> ii  libpam-modules 1.1.8-3.1+deb8u1+b1
> ii  libpam0g   1.1.8-3.1+deb8u1+b1
> ii  libssl1.0.01.0.1t-1+deb8u4
> ii  libwrap0   7.6.q-25
> ii  netbase5.3
>
> Versions of packages vsftpd recommends:
> ii  logrotate  3.8.7-1+b1
> ii  ssl-cert   1.0.35
>
> vsftpd suggests no packages.
>
> -- Configuration Files:
> /etc/vsftpd.conf changed [not included]
>
> -- debconf information:
>   vsftpd/directory: /srv/ftp
>   vsftpd/username: ftp

Bug#867270: ITA: babl/0.1.28-4

[Keng-Yu Lin]

2017-07-05 21:47 GMT+08:00 Andrey Rahmatullin <w...@debian.org>:
> On Wed, Jul 05, 2017 at 09:26:46PM +0800, Keng-Yu Lin wrote:
>> Thanks for providing the information.
>> Title is fixed. The original maintainer of this orphaned package is
>> included in the mail receivers.
> Please also fix the title of #866873 (and please don't top-post).

Done. Thanks!

Bug#867270: ITA: babl/0.1.28-4

[Keng-Yu Lin]

Thanks for providing the information.
Title is fixed. The original maintainer of this orphaned package is
included in the mail receivers.


2017-07-05 19:33 GMT+08:00 Andrey Rahmatullin :
> It's usually not a good idea to make an upload just to update the
> maintainer name, see
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#adopting
> and
> https://www.debian.org/devel/wnpp/#l3
> for the actual procedures.
> You've also got the RFS title wrong, please read the template more
> carefully.
>
> --
> WBR, wRAR

Bug#867270: ITA: babl/0.1.28-4

[Keng-Yu Lin]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "babl"

 * Package name: babl
   Version : 0.1.28-4
   Upstream Author : Øyvind Kolås <pip...@gimp.org>
 * URL : http://www.gegl.org/babl
 * License : LGPL-3
   Section : libs

  It builds those binary packages:

 libbabl-0.1-0 - Dynamic, any to any, pixel format conversion library
 libbabl-0.1-0-dbg - Dynamic, any to any, pixel format conversion library
(debugging s
 libbabl-dev - Dynamic, any to any, pixel format conversion library
(development
 libbabl-doc - Dynamic, any to any, pixel format conversion library
(documentati

  To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/babl

  Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/b/babl/babl_0.1.28-4.dsc

  Changes since the last upload:
* New maintainer (Closes: #866873)

  Regards,
   Keng-Yu Lin



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-78-generic (SMP w/4 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#844386: Ships unnecessary, explicit trigger for liburfkill-glib0

[Keng-Yu Lin]

Thanks. Noted. I will fix this in the next upload. :-)

2016-11-15 13:17 GMT+08:00 Michael Biebl :
> Source: urfkill
> Version: 0.5.0-5
> Severity: minor
>
> Hi,
>
> in 0.5.0-5 you added an explicit trigger
> debian/liburfkill-glib0.triggers for ldconfig.
>
> This is not necessary. dh_makeshlibs will generate one automatically for
> you, so you can safely drop debian/liburfkill-glib0.triggers.
>
> You can check this after a successful build. You'll have a file
>
> $ cat debian/liburfkill-glib0/DEBIAN/triggers
> # Triggers added by dh_makeshlibs
> activate-noawait ldconfig
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#843540: RFS: urfkill/0.5.0-5 [RC]

[Keng-Yu Lin]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "urfkill"

 * Package name: urfkill
   Version : 0.5.0-5
   Upstream Author : Gary Lin (g...@suse.com), Joey Lee (j...@suse.com)
 * URL : https://www.freedesktop.org/wiki/Software/urfkill/
 * License : GPLv2
   Section : net

It builds those binary packages:

 gir1.2-urfkill-0.5 - GObject introspection data for the urfkill library
 liburfkill-glib-dev - wireless killswitch management library
(development files)
 liburfkill-glib0 - wireless killswitch management library
 liburfkill-glib0-dbg - wireless killswitch management library (debug symbols)
 urfkill- wireless killswitch management daemon for laptops

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/urfkill


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/u/urfkill/urfkill_0.5.0-5.dsc


  Changes since the last upload:

  [Michael Biebl]
  * Follow gobject introspection policy (Closes: #838415)

  [Keng-Yu Lin]
  * Use dpkg-trigger to call ldconfig for liburfkill-glib0
- Add debian/liburfkill-glib0.triggers; remove debian/postinst
  * Bump Standards-Version to 3.9.8
  * Library gir1.2-urfkill-glib0 is renamed to gir1.2-urfkill-0.5,
added the Breaks and Replaces in debian/control


  Regards,
   Keng-Yu Lin

Bug#843056: RFS: urfkill/0.5.0-5

[Keng-Yu Lin]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "urfkill"
This upload fixes a RC bug.

 * Package name: urfkill
   Version : 0.5.0-5
   Upstream Author : Gary Lin (g...@suse.com), Joey Lee (j...@suse.com)
 * URL : https://www.freedesktop.org/wiki/Software/urfkill/
 * License : GPLv2
   Section : net

It builds those binary packages:

gir1.2-urfkill-0.5 - GObject introspection data for the urfkill library
liburfkill-glib-dev - wireless killswitch management library (development files)
liburfkill-glib0 - wireless killswitch management library
liburfkill-glib0-dbg - wireless killswitch management library (debug symbols)
urfkill- wireless killswitch management daemon for laptops

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/urfkill


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/u/urfkill/urfkill_0.5.0-5.dsc

  More information about hello can be obtained from https://www.example.com.

  Changes since the last upload:

  [your most recent changelog entry]


  Regards,
   Keng-Yu Lin

Bug#828285: dogecoin: FTBFS with openssl 1.1.0

[Keng-Yu Lin]

I didn't use openssl in experimental while building.
I think the failure may be something wrong else and now it's fixed in sid.

Feel free to re-open the bug if the failure still persists.

2016-10-28 13:24 GMT+08:00 Kurt Roeckx <k...@roeckx.be>:
> On Fri, Oct 28, 2016 at 12:53:51PM +0800, Keng-Yu Lin wrote:
>> Built on my local machine with the latest sid, the failure is not
>> reproducible any more.
>
> Please note that it's still in experimental.
>
>
> Kurt
>

Bug#835169: RFS: vsftpd/3.0.3-6 [ITA]

[Keng-Yu Lin]

Package: sponsorship-requests
Severity: normal

 Dear mentors,

  I am looking for a sponsor for my package "vsftpd"
  and also set up the DM permission for me.

 * Package name: vsftpd
   Version : 3.0.3-6
   Upstream Author : Chris Evans <scarybea...@gmail.com>
 * URL : http://security.appspot.com/downloads/
 * License : GPL-2 with SSL exception
   Section : net

  It builds those binary packages:

vsftpd - lightweight, efficient FTP server written for security
 vsftpd-dbg - lightweight, efficient FTP server written for security (debug)

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/vsftpd


  Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/v/vsftpd/vsftpd_3.0.3-6.dsc

  More information about hello can be obtained from https://www.example.com.

  Changes since the last upload:

  * New maintainer (Closes: #824694)
  * Update the Debian Policy to 3.9.8
  * Add libeatmydata1 in package Depends
  * Fixed debian/watch

  Regards,
   Keng-Yu Lin

Bug#793841: dogecoin: FTBFS on arm64 and mipsel: leveldb AtomicPointer unimplemented

[Keng-Yu Lin]

The bug is fixed by dogecoin 1.8.10-2 that is already in unstable.

Bug#813973: dogecoin and libbitcoinconsensus0: error when trying to install together

[Keng-Yu Lin]

reported in dogecoin upstream: https://github.com/dogecoin/dogecoin/issues/1325.

2016-02-07 16:19 GMT+08:00 Ralf Treinen :
> Package: libbitcoinconsensus0,dogecoin
> Version: libbitcoinconsensus0/0.11.2-1
> Version: dogecoin/1.8.10-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> Date: 2016-02-07
> Architecture: amd64
> Distribution: sid
>
> Hi,
>
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
>
>
>
> Extracting templates from packages: 30%
> Extracting templates from packages: 60%
> Extracting templates from packages: 90%
> Extracting templates from packages: 100%
> Preconfiguring packages ...
> Selecting previously unselected package libexpat1:amd64.
> (Reading database ... 10944 files and directories currently installed.)
> Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
> Unpacking libexpat1:amd64 (2.1.0-7) ...
> Selecting previously unselected package libpng12-0:amd64.
> Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
> Unpacking libpng12-0:amd64 (1.2.54-1) ...
> Selecting previously unselected package libfreetype6:amd64.
> Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
> Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
> Selecting previously unselected package ucf.
> Preparing to unpack .../archives/ucf_3.0033_all.deb ...
> Moving old data out of the way
> Unpacking ucf (3.0033) ...
> Selecting previously unselected package fonts-dejavu-core.
> Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
> Unpacking fonts-dejavu-core (2.35-1) ...
> Selecting previously unselected package fontconfig-config.
> Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
> Unpacking fontconfig-config (2.11.0-6.3) ...
> Selecting previously unselected package libfontconfig1:amd64.
> Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
> Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
> Selecting previously unselected package fontconfig.
> Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
> Unpacking fontconfig (2.11.0-6.3) ...
> Selecting previously unselected package x11-common.
> Preparing to unpack .../x11-common_1%3a7.7+13_all.deb ...
> Unpacking x11-common (1:7.7+13) ...
> Selecting previously unselected package libice6:amd64.
> Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
> Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
> Selecting previously unselected package libmtdev1:amd64.
> Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
> Unpacking libmtdev1:amd64 (1.1.5-1) ...
> Selecting previously unselected package libsm6:amd64.
> Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
> Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
> Selecting previously unselected package libgcrypt20:amd64.
> Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
> Unpacking libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Processing triggers for man-db (2.7.5-1) ...
> Setting up libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Selecting previously unselected package libsystemd0:amd64.
> (Reading database ... 11204 files and directories currently installed.)
> Preparing to unpack .../libsystemd0_228-6_amd64.deb ...
> Unpacking libsystemd0:amd64 (228-6) ...
> Selecting previously unselected package libxau6:amd64.
> Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
> Unpacking libxau6:amd64 (1:1.0.8-1) ...
> Selecting previously unselected package libxdmcp6:amd64.
> Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
> Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
> Selecting previously unselected package libxcb1:amd64.
> Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
> Unpacking libxcb1:amd64 (1.11.1-1) ...
> Selecting previously unselected package libx11-data.
> Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
> Unpacking libx11-data (2:1.6.3-1) ...
> Selecting previously unselected package libx11-6:amd64.
> Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-6:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libx11-xcb1:amd64.
> Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libxfixes3:amd64.
> Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
> Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
> Selecting previously unselected package libxdamage1:amd64.
> Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
> Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
> Selecting previously unselected package libxext6:amd64.
> Preparing to unpack .../libxext6_2%3a1.3.3-1_amd64.deb ...
> Unpacking libxext6:amd64 (2:1.3.3-1) ...
> Selecting previously unselected package libxshmfence1:amd64.
> Preparing to 

Bug#813974: dogecoin and libbitcoinconsensus-dev: error when trying to install together

[Keng-Yu Lin]

reported in dogecoin upstream: https://github.com/dogecoin/dogecoin/issues/1325.

2016-02-07 16:19 GMT+08:00 Ralf Treinen :
> Package: libbitcoinconsensus-dev,dogecoin
> Version: libbitcoinconsensus-dev/0.11.2-1
> Version: dogecoin/1.8.10-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> Date: 2016-02-07
> Architecture: amd64
> Distribution: sid
>
> Hi,
>
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
>
>
>
> Extracting templates from packages: 29%
> Extracting templates from packages: 59%
> Extracting templates from packages: 89%
> Extracting templates from packages: 100%
> Preconfiguring packages ...
> Selecting previously unselected package libexpat1:amd64.
> (Reading database ... 10944 files and directories currently installed.)
> Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
> Unpacking libexpat1:amd64 (2.1.0-7) ...
> Selecting previously unselected package libpng12-0:amd64.
> Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
> Unpacking libpng12-0:amd64 (1.2.54-1) ...
> Selecting previously unselected package libfreetype6:amd64.
> Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
> Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
> Selecting previously unselected package ucf.
> Preparing to unpack .../archives/ucf_3.0033_all.deb ...
> Moving old data out of the way
> Unpacking ucf (3.0033) ...
> Selecting previously unselected package fonts-dejavu-core.
> Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
> Unpacking fonts-dejavu-core (2.35-1) ...
> Selecting previously unselected package fontconfig-config.
> Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
> Unpacking fontconfig-config (2.11.0-6.3) ...
> Selecting previously unselected package libfontconfig1:amd64.
> Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
> Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
> Selecting previously unselected package fontconfig.
> Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
> Unpacking fontconfig (2.11.0-6.3) ...
> Selecting previously unselected package x11-common.
> Preparing to unpack .../x11-common_1%3a7.7+13_all.deb ...
> Unpacking x11-common (1:7.7+13) ...
> Selecting previously unselected package libice6:amd64.
> Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
> Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
> Selecting previously unselected package libmtdev1:amd64.
> Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
> Unpacking libmtdev1:amd64 (1.1.5-1) ...
> Selecting previously unselected package libsm6:amd64.
> Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
> Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
> Selecting previously unselected package libgcrypt20:amd64.
> Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
> Unpacking libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Processing triggers for man-db (2.7.5-1) ...
> Setting up libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Selecting previously unselected package libsystemd0:amd64.
> (Reading database ... 11204 files and directories currently installed.)
> Preparing to unpack .../libsystemd0_228-6_amd64.deb ...
> Unpacking libsystemd0:amd64 (228-6) ...
> Selecting previously unselected package libxau6:amd64.
> Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
> Unpacking libxau6:amd64 (1:1.0.8-1) ...
> Selecting previously unselected package libxdmcp6:amd64.
> Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
> Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
> Selecting previously unselected package libxcb1:amd64.
> Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
> Unpacking libxcb1:amd64 (1.11.1-1) ...
> Selecting previously unselected package libx11-data.
> Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
> Unpacking libx11-data (2:1.6.3-1) ...
> Selecting previously unselected package libx11-6:amd64.
> Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-6:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libx11-xcb1:amd64.
> Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libxfixes3:amd64.
> Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
> Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
> Selecting previously unselected package libxdamage1:amd64.
> Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
> Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
> Selecting previously unselected package libxext6:amd64.
> Preparing to unpack .../libxext6_2%3a1.3.3-1_amd64.deb ...
> Unpacking libxext6:amd64 (2:1.3.3-1) ...
> Selecting previously unselected package libxshmfence1:amd64.
> Preparing to 

Bug#793840: dogecoin: FTBFS: test_dogecoin-qt fails

[Keng-Yu Lin]

Dogecoin currently does not build in Sid due to libstdc++ transition.
will have to wait until the transition finishes.
status can be tracked from
https://release.debian.org/transitions/html/libstdc++6.html

2015-07-28 10:38 GMT+08:00 Aaron M. Ucko u...@debian.org:
 Source: dogecoin
 Version: 1.8.0-1
 Severity: serious
 Justification: fails to build from source

 Automated builds of dogecoin that get as far as the test suite have
 been failing:

   ../../../src/build-aux/test-driver: line 107: 20919 Aborted 
 $@  $log_file 21
   FAIL: test_dogecoin-qt

 This failure looks very similar to the one from
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790403 , whose
 solution turned out to be setting TMPDIR and HOME to writable
 directories within the build tree.

 (Builds on some architectures have been failing earlier; I'll report
 those bugs separately.)

 Could you please take a look?

 Thanks!


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

Bug#766467: ibus-array: Update package dependency (python-ibus - python-gi)

[Keng-Yu Lin]

Thanks Osamu for updating the new upstream version too.

Tested ibus-array 0.0.4-1 it works without any problem.

2014-10-23 18:45 GMT+08:00 Osamu Aoki os...@debian.org:
 Package: ibus-array
 Version: 0.0.3-1
 Severity: important

 Thank you (Keng-Yu Lin) for updating upstream tarball.

 But this package still is shipped with binary dependency to python-ibus
 which is not in the archive. As seen on:
   https://qa.debian.org/excuses.php?package=ibus-array

 |   Excuse for ibus-array
 |
 |   Too young, only 6 of 10 days old
 |   ibus-array/i386 unsatisfiable Depends: python-ibus
 |   ibus-array/amd64 unsatisfiable Depends: python-ibus
 |   ibus-array/armel unsatisfiable Depends: python-ibus
 |   ibus-array/armhf unsatisfiable Depends: python-ibus
 |   ibus-array/kfreebsd-amd64 unsatisfiable Depends: python-ibus
 |   ibus-array/kfreebsd-i386 unsatisfiable Depends: python-ibus
 |   ibus-array/mips unsatisfiable Depends: python-ibus
 |   ibus-array/mipsel unsatisfiable Depends: python-ibus
 |   ibus-array/powerpc unsatisfiable Depends: python-ibus
 |   ibus-array/s390x unsatisfiable Depends: python-ibus
 |   ibus-array/arm64 unsatisfiable Depends: python-ibus
 |   ibus-array/ppc64el unsatisfiable Depends: python-ibus
 |   Not considered
 ^^

 This is bad.

 Let's remove python-ibus and add python-gi gir-* package.
 Since this is just simple fix, I will upload fixed package soon.

 Please test uploaded package and report bugs since I have no idea how to
 input Chinese with array30.

 With this, all ibus packages are in good shape for the upcoming freeze
 on Nov. 5th.  If anyone find issues and need help uploading fixed
 package, file a bug report CC ing
   IME Packaging Team pkg-ime-de...@lists.alioth.debian.org

 fcitx is also fixed now:-)  So all the funny AUTORM tags should go away.
 Please keep your eyes on:

  
 https://qa.debian.org/developer.php?login=pkg-ime-de...@lists.alioth.debian.org

 Thanks and regards,

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

 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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#766467: ibus-array: Update package dependency (python-ibus - python-gi)

[Keng-Yu Lin]

many thanks Osamu. I will test it when it arrives in main. :-)

2014-10-23 18:45 GMT+08:00 Osamu Aoki os...@debian.org:
 Package: ibus-array
 Version: 0.0.3-1
 Severity: important

 Thank you (Keng-Yu Lin) for updating upstream tarball.

 But this package still is shipped with binary dependency to python-ibus
 which is not in the archive. As seen on:
   https://qa.debian.org/excuses.php?package=ibus-array

 |   Excuse for ibus-array
 |
 |   Too young, only 6 of 10 days old
 |   ibus-array/i386 unsatisfiable Depends: python-ibus
 |   ibus-array/amd64 unsatisfiable Depends: python-ibus
 |   ibus-array/armel unsatisfiable Depends: python-ibus
 |   ibus-array/armhf unsatisfiable Depends: python-ibus
 |   ibus-array/kfreebsd-amd64 unsatisfiable Depends: python-ibus
 |   ibus-array/kfreebsd-i386 unsatisfiable Depends: python-ibus
 |   ibus-array/mips unsatisfiable Depends: python-ibus
 |   ibus-array/mipsel unsatisfiable Depends: python-ibus
 |   ibus-array/powerpc unsatisfiable Depends: python-ibus
 |   ibus-array/s390x unsatisfiable Depends: python-ibus
 |   ibus-array/arm64 unsatisfiable Depends: python-ibus
 |   ibus-array/ppc64el unsatisfiable Depends: python-ibus
 |   Not considered
 ^^

 This is bad.

 Let's remove python-ibus and add python-gi gir-* package.
 Since this is just simple fix, I will upload fixed package soon.

 Please test uploaded package and report bugs since I have no idea how to
 input Chinese with array30.

 With this, all ibus packages are in good shape for the upcoming freeze
 on Nov. 5th.  If anyone find issues and need help uploading fixed
 package, file a bug report CC ing
   IME Packaging Team pkg-ime-de...@lists.alioth.debian.org

 fcitx is also fixed now:-)  So all the funny AUTORM tags should go away.
 Please keep your eyes on:

  
 https://qa.debian.org/developer.php?login=pkg-ime-de...@lists.alioth.debian.org

 Thanks and regards,

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

 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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#748783: ITP: fwts -- firmware test suite PC firmware. It is intended to identify BIOS and ACPI errors and if appropriate it will try to explain the errors and give advice to help workaround or

[Keng-Yu Lin]

Package: wnpp
Severity: wishlist
Owner: Keng-Yu Lin ken...@lexical.tw

* Package name: fwts
  Version : 14.05.00
  Upstream Author : Firmware Testing Team (https://launchpad.net/~firmware-
testing-team)
* URL : https://launchpad.net/fwts
* License : GPLv2, LGPL,
  Programming Lang: C,
  Description : FWTS is a firmware test suite that performs sanity checks
 on Intel/AMD PC firmware. It is intended to identify BIOS and ACPI errors and
 if appropriate it will try to explain the errors and give advice to
 help workaround or fix firmware bugs.  It is primarily intended to
 be a Linux-centric firmware troubleshooting tool.


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

Bug#748799: ITP: dogecoin -- peer-to-peer network based anonymous digital currency

[Keng-Yu Lin]

Package: wnpp
Severity: wishlist
Owner: Keng-Yu Lin ken...@lexical.tw

* Package name: dogecoin
  Version : 1.7.0
  Upstream  :  Shibetoshi Nakamoto billym2k@gmail
* URL : http://dogecoin.com/
* License : MIT/X
  Programming Lang: C, C++
  Description : peer-to-peer network based anonymous digital currency

Dogecoin is a free open source peer-to-peer electronic cash system that
is completely decentralized, without the need for a central server or
trusted parties.  Users hold the crypto keys to their own money and
transact directly with each other, with the help of a P2P network to
check for double-spending.


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

Bug#746968: ibus-array should be removed

[Keng-Yu Lin]

As an Array 30 IM user, the ibus-table-array30 package did not
implement the full features of the Array 30 IME (such as no quick
codes, no first and second class simple codes) where ibus-array
implemented these extra features.

Also as the package maintainer of ibus-array package, I am happy and
will spend some time looking at the ibus-python issue.



2014-05-04 20:49 GMT+08:00 Osamu Aoki os...@debian.org:
 Source: ibus-array
 Version: 0.0.2-9
 Severity: normal

 In short, we should remove this ibus-array package.

 The reason is that ibus-array is one of the few packages which still
 uses ibus-python interface which is about to be removed from ibus(*).

  * ibus-array   popcon=ca. 30 (uses ibus-python)
  * ibus-table-array30   popcon=ca. 30 (does not use ibus-python)

 Since the ibus-table-array30 binary package which is generated from the
 ibus-table-chinese source package seems to support this particular
 array30 chinese input method, I see no major problem.  (I also see a low
 popcon value.)

 So question is what to do for wheezy.  3 options.

  1) we just remove ibus-array. (My choice)
  2) we upload transition package of ibus-array depending on
 ibus-table-array30.
  3) we modify ibus-table-array30 to provide ibus-array.
(need ibus-table-chinese source package upload)

 Unless I get specific request/help/... , I will just do option 1 to
 remove this ibus-array.  Objection?

 Let me know your thought by replying to this Debian bug report.  Once we
 decide on this, I can work on other 3 packages which are affected.

  * ibus-pinyin   popcon=443
ibus-pinyin needs to update its package dependency so it can be
removed from this list.  I will handle this separately.

  * ibus-googlepinyin popcon=330
Considering other newer pinyin methods are available, simply removing
this should be OK just like ibus-array.

  * ibus-el   popcon=103
Whoever uses this with EMACS should consider using uim instead since
they can stay within LISP world using uim bindings of IM.

 Regards,

 Osamu
 (*) ibus-python removal background.
 The upstream does not actively support ibus-python and has been
 recommending to move to use Gobject introspection.  So continuing to
 ship unsupported zombie ibus-python code just because its old code has
 not been removed is not good idea.

 Since most of the IM packages completed this transition, I am planning
 to remove ibus-python.

 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386

 Kernel: Linux 3.14-1-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

 -- 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#674993: debian-maintainers: Please add Keng-Yu Lin as a Debian Maintainer

[Keng-Yu Lin]

Package: debian-maintainers
Severity: normal

Dear Maintainer,
  Please add my key ken...@lexical.tw to the DM keyring. jetring changeset is
attached.

  cheers,
-kengyu



-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-24-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Comment: Add ken...@lexical.tw as a Debian Maintainer
Date: Tue, 29 May 2012 15:23:14 +0800
Recommended-By:
  Ying-Chun Liu (PaulLiu) paul...@debian.org
Agreement:
  http://lists.debian.org/debian-newmaint/2012/03/msg00034.html
Advocates:
  http://lists.debian.org/debian-newmaint/2012/03/msg00035.html
Action: import
Data: 
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: GnuPG v1.4.11 (GNU/Linux)
  
  mQINBEviORoBEADCz5x+cv9E9JQtlTXiDmYanGbDnEzHyQbfRMUOQM7zrplYEwRS
  m+GJ6MatIbgU0/zdMiIHYP3L4CtBH3zVFtmuFrKCJFZ7yBZ/G3N7ERMADLFwshlg
  3yO+oNFAupp2Yuza2MSrgusNCKbQZc8/GuS7ArkBWc/fW2wMqyJKHUZbn9lY8pAu
  gVjKcTp3sjZtfiZwE2z0goK2RiIPyJdCl6k2XVuKQZPbdvhrSbKbWj6x4qypD83Y
  ie88fbnR9iIopNcdKnrLws5HG4fmDIVly8Rj72IIZV5J75258zcJqp/GsByvt5EX
  iAZ8QZbvwPkbstatkTr89raQ3t0OyiVpanHaC8m3J6jWRGwtynNeaR7bLIlgjhmx
  1+XWlGm0wxGe7rzSAxZuhEKgfc/Pc7fZNsqhxDKibMUcrmhmrtBwzxCfMR+TDwPX
  12fmrpD+bmOXtypFDpGNPtYZdnmma67gd0waQ84z06fPsKpX7bV0wRF5OcDJwDpv
  n+wIF47PoRRvb14702cXgsuGOdChtqhCQcATle6UfbsYi0lg82DFUVvRJShHye7/
  QcPcyFMJY9QQiKJOB0iO7R7PUf+tP+MEn8kBVbQLDdguUp+MEEQdqzitNZFjLz0E
  C9sOXjDyXUk4D10bB8XvO4dd3qEc/ZG9TUkJ9CK2yc4oOYsA2F+eFUE3wQARAQAB
  tCBLZW5nLVl1IExpbiA8bGV4aWNhbGxAZ21haWwuY29tPokCOAQTAQIAIgUCS+I/
  gQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQxheGnxR4UE54AQ/+KHhb
  HMkF97f4lgQ3JUYSWc3txuQ+tAJG3fa0ABZagekiukA+zP+eRQ7pn0qCldBSQZKi
  WxnycccQ+Ocqs7s6Q0MbzUhPn8/KRD4/CvojkjuvsJHwYEzQg7jMjKaLry+yPnA0
  Plxq51EfFgKGRVJs0o2xP9CnfDXI4Bpq6EZiA3gI34rz7GCxEfdfCroDxu5p0vT2
  DtW+Y4PKcAn7uEUqwFEfOYEWqG2/YGJ3cwfS2TDGWBKKvCh7KTzRbDIASOGjKigp
  zu0mOHwauoyjL+AJmkatW7h3lIXhZmWT2wKJ3gdVqpDA0gTnZ0Au3YTHjhpr8fAi
  cHoNnklcEdBXtTsDuN6q/ioX7xteBMutVB9QuaH5e+eMXgBYmdzD6ZjERVp5xYhS
  rT9cQ70sLMC/saA72WQ2EenUnYvCI9TXT/sSeuRwkgZkjE7jeX02WQHZGIqjmn8l
  bVJxtngNcDy27saC3Df27aXnhCIuSTFH2EytMfgiq9bsMKmkQZBYIo+Pv9jc5hhn
  Y+F5/UlG5rp8R2FYgbcFIgaMPk5YluLe+bTXVgffvoMTMVXvdX0/FG3Ufc0zp8zV
  cVa6VGQFMGE9G5CGeE02950VxbUJPtdAxgDnq121OXmSSjDkBHHTiV4BibwFp9mK
  eMMGTl7db8/yaOsbWNmrqMkLJ/eqMokgDXKfMh6IRgQQEQIABgUCS+tHpgAKCRCP
  Bg274e8+Sm2TAJ98hNeUB+3o9Pi5Y4eAhVDp6Hw2TwCfU+o42arXJVqtd9S4Wve7
  x7229zeJARwEEAECAAYFAkvrVU4ACgkQPqzuas/XTt5lXwgAmwmTV+2+1r+P99CQ
  HAUiXPZf9hHIfQn/6iPgNTtldVqbst0riE0mpNT+pSM7xSfsVkkSpTQN3C8WHRdH
  Lrvep5iai4w4a0Imt/rruioA8YR25ayM6+yfDdIgtEgXPuS/mfZjIgyNsNKM6Gls
  HTCZM0ln3CRIFQNQhWNpuV/W794+8MTeK3K23IDpzuXnqqs3GeQl45l7LzmHHywb
  iqXyo4WQg1wna2/3SNQ6BNcHsfU/pueoCnWo+B0T5Wr0huizTPCGrgvJiYJzZjjZ
  pOIX7XE0JUjK4ZkPq3nvYXe0h2EIB+7MjGITlMwYQMBMDnUjj7aJ30QX2DvmKK3x
  4kxk+IkCHAQQAQIABgUCS+rp4gAKCRDBJjPh7gGMkytAEACzslA2l2URU3WvoDFG
  2F6sUt9/KxtApIOQDM4unfaDQUmeh/h0woKcgSSpQVrTIiuWW5YfrnPHTlziqVyS
  Bli7MVdvgm237Ofqju7r/SPG6kulWIJh5bOIPtJRAaJA9IuOxBwwm6lwlDw939Hk
  tvYC6NBgZ7aX3IffU7PIVvpIGK8gPxCZ+GQY6Zq1TW49rCx3R75oR6NjCOtyOD08
  oItKmtqhOX7P0ANob8lHjhHT2nusYmKqXenV+7OU1KTvUL8b2J0Yxe4ArNuvAcBM
  1rF19Xc//pM1JCh+Bj+M3HJczsL0bFI0BH8QWFHB11OOxcK62O/K9DRknpdPFL+C
  4RI8FtyzVeGi5wros5ckGtMnupcntcAvwXZw8DGqidVAuQ9v+AUhV2ZKBh+GM26s
  b+ixIaAe5VdJmGYQsaZVqdWfzXAF4Q8N2n/oO7tdDAvZ+ekdlIX9zaOmqlshHAyj
  ixzBm6KJRvPP8ZUf+diww/e09cdKGwZRqeyb7up1SpC/1GLKUobEo957U2xfcnSQ
  gubSFewsfzRre/5uoSWYYQNzUeLC5jBtw6ssBb4jOfpPkZQy5myH0Pnen4S2zZWS
  21Lq6tQ9tESWw8lA9suy0q/76DiukVSLeUP904T5rPZE6MQutcGezA9MwI0BJwF2
  yOJ684P11QrEZJvBCkEyOLEz44hGBBARAgAGBQJL6wi5AAoJEI8cn6pIwYbsq6cA
  n1y6aSxn3tBW1E/kZ0GKf/vLqjYXAJ4nh1o8vN4aeYt0lRjgh0qTX8RvVIhGBBAR
  AgAGBQJL6xd0AAoJEAp+Ei+Q51XKaRAAoIQx2pww7BrHGRcX+okJFk16tFiqAJwL
  zQ21BHkvmDztJJBicyXOJJxDUYhGBBARAgAGBQJL7mV3AAoJED8tEpwgv83HrMQA
  nRUnSxjDgVkhwolHJyjpBgKdNGwaAJ9gykfzs5RKLV4LqhTsAxa8SySma4kCHAQQ
  AQIABgUCS/AIPgAKCRDn9xBVVAnkItwgD/4yFcIXk9Ht3esTNjwbPJGc60mCyoRG
  uL+2JFKS6//lB+1bF4JeT+ffEVDCh9ndavyiDwuOeLG8eAgpd2GiMWfSuIAliCGU
  puSmqkiBGHlC0QCpqoHk7mC/DSWncQ+F/geJOx8Yd0lycMZAG2hXK2aF7x22INEj
  FThu/5hQG57eNr0cMfQyo0xG2ifRIet3Rv/Apc6NdUdG6upQY3uyMRIo9+Gy3MIY
  a/7wzoHDbOUx7FLwK3jfrjnCZeLz/RxiZEPCwxDYn6Lwng9B8uenjQLLz4ualy3s
  PzGle6uVQdGqg/QdgWks6/6xUtVDBVFksMbxQzOGpU4fZktOReA+D7vhUfYOT+rQ
  SZ/m+tM32Wvw7PwQUXroygXdRvz1O4hAcnf8mQIMDyk/6+HEOqXSA0w3gR3BJluv
  Y+HtxLcOwiaYAT2Il6T/GgkZApthWZVMXtXmhgtUBS92sK7zfzGy7muOoeHL7UiA
  LpySquCyszOvOqYtw6EmfockRSOzCqgpa8FM/V+7cdkp8l55UowchsaW6cNJeLW8
  a8PQbxw+tr5QmFoerooW/39Iu87G4uLPBSMGJwzBHtVqWBlXYnzANqRSXT5XBFXz
  2aI1YzEZgJJYb2aks8FwV8Ci4uqGJeDE6mMMT7l/IfDQjcOksTOfPThLbxqESP2f
  sN9DSKRSufWfyYkBHAQQAQIABgUCS/BorwAKCRD8BYRoWRXvJiUfB/9i7xTVMS2Z
  78Vtc7q/+byV4GiBwMTu3zd+LBMSWVN+VPtut+BzR3vjlj6P5BCyWPivJPQcCb92
  

Bug#653227: acpica-unix: New upstream release 20111123 whit full support for the ACPI 5.0 specification

[Keng-Yu Lin]

There is lately another upstream release 20120320.

http://www.acpica.org/download/changes.txt



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

Bug#637351: ITP: urfkill -- urfkill is a daemon for the management of the radio killswitches.

[Keng-Yu Lin]

2011/8/11 Christian PERRIER bubu...@debian.org:
 Quoting Keng-Yu Lin (ken...@lexical.tw):

 Thanks for the suggestion. I modified the description as below.I hope
 that it is better explained and understandable.

 Package: wnpp
  Severity: wishlist
  Owner: Keng-Yu Lin ken...@lexical.tw

  * Package name    : urfkill
   Version         : 0.2.0
   Upstream Author : Gary Lin g...@suse.com
  * URL             : http://www.freedesktop.org/wiki/Software/urfkill
  * License         : GPL, LGPL
   Programming Lang: C
   Description     : wireless killswitch management daemon for laptops

  urfkill daemon provides the management of the rfkill-related hotkeys
  and the killswitches in a more configurable way for the common RF
  devices, e.g. WiFi, Bluetooth, WWan, etc. urfkill handles the various
  key codes (KEY_WLAN, KEY_BLUETOOTH, KEY_RFKILL, etc)
  and toggles the killswitches based on a pre-defined policy.

 Maybe just avoid starting sentences with urfkill as it is always
 wierd to have sentences beginning with a lowercase letter.

 A common trick is using The foo program|daemon. Also avoid e.g.
 which is a latinism that's too often used in English..:). I propose
 parenthesis...another option would be using such as. Replace etc.
 with an ellipsis (...) as it avoids the tricky use of a dot before and
 after a closing parenthesis.

 That would give:

 The urfkill daemon allow managins the rfkill-related hotkeys
 and the killswitches in a more configurable way for the common RF
 devices (WiFi, Bluetooth, WWan...). It handles the various
 key codes (KEY_WLAN, KEY_BLUETOOTH, KEY_RFKILL, etc)
 and toggles the killswitches based on a pre-defined policy.

Thanks for the refinement. I hope the description looks better now. :-)

Package: wnpp
  Severity: wishlist
  Owner: Keng-Yu Lin ken...@lexical.tw

  * Package name: urfkill
  Version : 0.2.0
  Upstream Author : Gary Lin g...@suse.com
  * URL : http://www.freedesktop.org/wiki/Software/urfkill
  * License : GPL, LGPL
  Programming Lang: C
  Description : wireless killswitch management daemon for laptops

  The urfkill daemon allow managing the rfkill-related hotkeys
  and the killswitches in a more configurable way for the common RF
  devices (WiFi, Bluetooth, WWan...). It handles the various
  key codes (KEY_WLAN, KEY_BLUETOOTH, KEY_RFKILL...)
  and toggles the killswitches based on a pre-defined policy.



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

Bug#637351: ITP: urfkill -- urfkill is a daemon for the management of the radio killswitches.

[Keng-Yu Lin]

2011/8/13 Andrea Bolognani e...@kiyuko.org:
 I believe you could achieve the same effect using a combination of
 triggerhappy and the aforementioned rfkill, and I don’t like the idea
 of having a special daemon running to handle a subset of the special
 keys when there’s a more general solution to the problem already in the
 archive.

 That said, urfkill might have advantages I don’t see.


rfkill has nothing to do with the hotkey management. It is just a
tool to enable/disable a wireless device as specify in the argument.
urfkill is a way to manage and toggle these devices based on the
conf file.

The immediate problem is that when KEY_WLAN is commonly generated by
the key press, should bluetooth and 3G be turned off too where there
are in fact keycodes dedicated for each: KEY_BLUETOOTH, KEY_WWAN.

Also as a planned function (but not yet implemented in the code now)
of urfkill, people desire to turn off wifi on the first pressing,
bluetooth on the second and so on... This is only possible if there is
a dedicated daemon for handling this.



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

Bug#637351: ITP: urfkill -- urfkill is a daemon for the management of the radio killswitches.

[Keng-Yu Lin]

2011/8/11 Christian PERRIER bubu...@debian.org:
 Quoting Keng-Yu Lin (ken...@lexical.tw):
 Package: wnpp
 Severity: wishlist
 Owner: Keng-Yu Lin ken...@lexical.tw

 * Package name    : urfkill
   Version         : 0.2.0
   Upstream Author : Gary Lin g...@suse.com
 * URL             : http://www.freedesktop.org/wiki/Software/urfkill
 * License         : GPL, LGPL
   Programming Lang: C
   Description     : urfkill is a daemon for the management of the radio 
 killswitches.

 urfkill daemon handles the configuration of the rfkill-related
 function keys and provides the management of the radio killswitches.


 radiowhat? :-)

 I guess this is about the buttons that are often used to turn wireless
 communication on/off on modern laptops, but this is only a guess.

 I would suggest having a more explicit description.

 Also, the Description you give is a sentence. Short descriptions
 (aka synopsis) shouldn't be sentences, see Developer's Reference.

 Something along wireless killswitch management daemon for laptops
 would be appropriate, imho (assuming the package is indeed what I
 think it is..:-))



Thanks for the suggestion. I modified the description as below.I hope
that it is better explained and understandable.

Package: wnpp
 Severity: wishlist
 Owner: Keng-Yu Lin ken...@lexical.tw

 * Package name: urfkill
  Version : 0.2.0
  Upstream Author : Gary Lin g...@suse.com
 * URL : http://www.freedesktop.org/wiki/Software/urfkill
 * License : GPL, LGPL
  Programming Lang: C
  Description : wireless killswitch management daemon for laptops

 urfkill daemon provides the management of the rfkill-related hotkeys
 and the killswitches in a more configurable way for the common RF
 devices, e.g. WiFi, Bluetooth, WWan, etc. urfkill handles the various
 key codes (KEY_WLAN, KEY_BLUETOOTH, KEY_RFKILL, etc)
 and toggles the killswitches based on a pre-defined policy.



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

Bug#637351: ITP: urfkill -- urfkill is a daemon for the management of the radio killswitches.

[Keng-Yu Lin]

2011/8/11 Karl Goetz k...@kgoetz.id.au:
 Hi,
 How does it differ from rfkill, already in the archive? Perhaps the
 description could be updated to make this clear.
 thanks,
 kk


rfkill package in the archive is just a simple utility for switch
on/off the RF device.
urfkill handles the hotkeys (KEY_WLAN, KEY_BLUETOOTH, KEY_RFKILL, etc)
and can be configurable to behave differently on the key pressed.
Say, one may like the bluetooth to be switched off too on KEY_WLAN,
whereas in fact KEY_WLAN is for Wifi only, at least literally.



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

Bug#637351: ITP: urfkill -- urfkill is a daemon for the management of the radio killswitches.

[Keng-Yu Lin]

Package: wnpp
Severity: wishlist
Owner: Keng-Yu Lin ken...@lexical.tw

* Package name: urfkill
  Version : 0.2.0
  Upstream Author : Gary Lin g...@suse.com
* URL : http://www.freedesktop.org/wiki/Software/urfkill
* License : GPL, LGPL
  Programming Lang: C
  Description : urfkill is a daemon for the management of the radio 
killswitches.

urfkill daemon handles the configuration of the rfkill-related
function keys and provides the management of the radio killswitches.



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

Bug#614902: Info received (Bug#614902: Acknowledgement (bluetooth service needs to be stopped/restarted for successful hibernations))

[Keng-Yu Lin]

2011/2/24 Martin Pitt martin.p...@ubuntu.com:
 Hello Lin,

 Keng-Yu Lin [2011-02-24 14:49 +0800]:
 +btusbget() {
 +    local dev usb
 +    usb=/sys/bus/usb/devices
 +    for dev in $usb/*; do
 +     [[ -f ${dev}/bDeviceClass ]] || continue
 +     [[ $(cat ${dev}/bDeviceClass) = e0 ]] || continue # Wireless
 +     [[ -f ${dev}/bDeviceProtocol ]] || continue
 +     [[ $(cat ${dev}/bDeviceProtocol) = 01 ]] || continue # Bluetooth
 +     case $1 in
 +         vendor) echo $(cat ${dev}/idVendor) ;;
 +         device) echo $(cat ${dev}/idProduct) ;;
 +     esac
 +     break
 +    done
 +}

 This should still be improved, as it will run hundreds of cat
 subprocesses, iterate through the device tree twice, and also stop at
 the first bluetooth adapter instead of testing all of them.

 A nice trick for this is to use udevadm trigger. This works on my
 system (with a different adapter which I added to $quirks for
 testing):

  8 
 quirks=0a5c:219c 0a5c:21bc 413c:8187

 for usbid in $quirks; do
    vendor=${usbid%:*}
    product=${usbid#*:}

    DEVS=$(udevadm trigger --verbose --dry-run \
        --attr-match=bDeviceClass=e0 --attr-match=bDeviceProtocol=01 \
        --attr-match=idVendor=$vendor --attr-match=idProduct=$product)
    if [ -n $DEVS ]; then
        echo add_parameters --quirk-bluetooth-service-off
    fi
 done
  8 

 This will consider all bluetooth adapters and only do one external
 program call. Can you please confirm that this still works on your
 system? This should also be forwarded upstream, but Michael and I can
 also take care of that.


Hi Martin:
  I removed the echo before add_parameters.  It works well.
  I attached the modified patch in this mail.

  Thanks for taking care of this.

-kengyu
From 021a1c5696ec7bdf6434550bb48cca67c1846d82 Mon Sep 17 00:00:00 2001
From: Keng-Yu Lin keng-yu@canonical.com
Date: Fri, 25 Feb 2011 15:59:43 +0800
Subject: [PATCH] Add the quirk support for stoping/restarting bluetooth service

It is found that the bluetooth modules with USB VID/PIDs [0a5c:219c]
[0a5c:21bc] and [413c:8187] are causing random S4 hangs on various
laptops with SandyBridge chipset.

The hangs can be observed by repeating hibernate/resume in a 250
iterations. The successful cycles number before the hang is
usually ranged in tens, though it varies on different types of
laptops.

This patch added a parameter for the use as

	pm-hibernate --quirk-bluetooth-service-off

and a couple of USB ID quirks I found with this S4 problem.

Martin Pitt contributed the code to utilize udevadm for matching
the quirk in sysfs.

Signed-off-by: Keng-Yu Lin keng-yu@canonical.com
---
 pm/sleep.d/44bluetooth-known-quirk |   24 +
 pm/sleep.d/45bluetooth-service |   41 
 pm/sleep.d/Makefile.am |2 +
 3 files changed, 67 insertions(+), 0 deletions(-)
 create mode 100755 pm/sleep.d/44bluetooth-known-quirk
 create mode 100755 pm/sleep.d/45bluetooth-service

diff --git a/pm/sleep.d/44bluetooth-known-quirk b/pm/sleep.d/44bluetooth-known-quirk
new file mode 100755
index 000..f9df8b8
--- /dev/null
+++ b/pm/sleep.d/44bluetooth-known-quirk
@@ -0,0 +1,24 @@
+#!/bin/bash
+
+. ${PM_FUNCTIONS}
+
+quirks=0a5c:219c 0a5c:21bc 413c:8187
+
+case $1 in
+	hibernate|suspend)
+		# known bluetooth devices needing to stop bluetoothd
+		for usbid in $quirks; do
+			vendor=${usbid%:*}
+			product=${usbid#*:}
+
+			DEVS=$(udevadm trigger --verbose --dry-run \
+--attr-match=bDeviceClass=e0 --attr-match=bDeviceProtocol=01 \
+--attr-match=idVendor=$vendor --attr-match=idProduct=$product)
+			if [ -n $DEVS ]; then
+add_parameters --quirk-bluetooth-service-off
+			fi
+		done
+		;;
+	thaw|resume)
+		;;
+esac
diff --git a/pm/sleep.d/45bluetooth-service b/pm/sleep.d/45bluetooth-service
new file mode 100755
index 000..969ca86
--- /dev/null
+++ b/pm/sleep.d/45bluetooth-service
@@ -0,0 +1,41 @@
+#!/bin/bash
+
+. ${PM_FUNCTIONS}
+
+for opt in $PM_CMDLINE; do
+	case ${opt##--quirk-} in # just quirks, please
+		bluetooth-service-off) 	   QUIRK_BLUETOOTH_SERVICE_OFF=true ;;
+		bluetooth-none) 	   QUIRK_BLUETOOTH_NONE=true ;;
+		*) continue ;;
+	esac
+done
+
+quirk() { is_set $1  [ -z $QUIRK_BLUETOOTH_NONE ]; }
+
+suspend_bluetooth_service()
+{
+	quirk ${QUIRK_BLUETOOTH_SERVICE_OFF} 	stopservice bluetooth
+}
+
+resume_bluetooth_service()
+{
+	quirk ${QUIRK_BLUETOOTH_SERVICE_OFF} 	restartservice bluetooth
+}
+
+help() {
+	echo  # first echo makes it look nicer.
+	echo Bluetooth quirk handler options:
+	echo
+	echo   --quirk-bluetooth-service-off
+	echo   --quirk-bluetooth-none
+}
+
+case $1 in
+	hibernate|suspend)
+		suspend_bluetooth_service
+		;;
+	thaw|resume)
+		resume_bluetooth_service
+		;;
+	help) help ;;
+esac
diff --git a/pm/sleep.d/Makefile.am b/pm/sleep.d/Makefile.am
index 2350825..88df79c 100644
--- a/pm/sleep.d/Makefile.am
+++ b/pm/sleep.d/Makefile.am
@@ -4,6 +4,8

Bug#614902: Info received (Bug#614902: Acknowledgement (bluetooth service needs to be stopped/restarted for successful hibernations))

[Keng-Yu Lin]

2011/2/24 Michael Biebl bi...@debian.org:
 Has anyone investigated, why the lockup occurs and if this can be fixed in the
 driver/kernel. Has this problem been reported upstream to the Linux kernel 
 guys
 resp. the bluetooth maintainers?

 I would very much prefer this instead over working around the problem.


This patch included two part actually.

45bluetooth-service adds the argument --quirk-bluetooth-service-off
and it is not enabled unless set explicitly. This should be a safe one
to add. And it utilises the built-in functions stopservice() and
restartservice(). This patch does nothing but exports these two
existing functions to users (as arguments).

45bluetooth-service could be a smelly one. But since current quirking
part in pm-utils is for video qurks only. There is no way to quirk a
bluetooth adaptor in the quirkdb. For a short term solution, this
should be a just-work patch.

It was tested with both Broadcom and Atheros bluetooth adaptors
interchangeably on different laptops. This bug is specific to Broadcom
bluetooth chip only. With both use btusb kernel module, it could be a
hardware or firmware-related issue. However I agree with you that it
is good to get upstream discussion.



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

Bug#614902: bluetooth service needs to be stopped/restarted for successful hibernations

[Keng-Yu Lin]

Package: pm-utils
Version: 1.4.1-5
Severity: normal
Tags: patch



-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-25-generic-pae (SMP w/4 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 pm-utils depends on:
ii  kbd1.15-1ubuntu3 Linux console font and keytable ut
ii  powermgmt-base 1.31  Common utils and configs for power

Versions of packages pm-utils recommends:
ii  hdparm  9.27-2ubuntu2tune hard disk parameters for high
ii  procps  1:3.2.8-9ubuntu3 /proc file system utilities
ii  vbetool 1.1-2run real-mode video BIOS code to a

Versions of packages pm-utils suggests:
pn  cpufrequtilsnone   (no description available)
pn  ethtool none   (no description available)
ii  radeontool  1.6.1-1  utility to control ATI Radeon back
ii  wireless-tools  30~pre9-3ubuntu4 Tools for manipulating Linux Wirel

-- 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#614902: Acknowledgement (bluetooth service needs to be stopped/restarted for successful hibernations)

[Keng-Yu Lin]

It is found that the bluetooth modules with USB VID/PIDs [0a5c:219c]
[0a5c:21bc] and [413c:8187] is causing random S4 hangs on various
laptops with SandyBridge chipset.

The hans can be observed by repeating hibernate/resume in a 250
iterations with fwft. The successful cycles number before the han is
usually ranged in tens, though it varies on different types of
laptops.

A major soak testing was performed across several SandyBridge laptops
installed with Ubuntu Maverick.

The hang can be worked around to stop the bluetooth service before the
hibernate and restart it in the resume in the testing.

This bug is an attempt to get this fixed in Debian. The patch will be
attached in a follow-up mail.

It added a parameter for the use as pm-hibernate
--quirk-bluetooth-service-off and a couple of USB ID quirks I found
with this S4 problem.



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

Bug#614902: Info received (Bug#614902: Acknowledgement (bluetooth service needs to be stopped/restarted for successful hibernations))

[Keng-Yu Lin]

From 8dd91340660a14c55d12372a3e9a767863b7f316 Mon Sep 17 00:00:00 2001
From: Keng-Yu Lin keng-yu@canonical.com
Date: Thu, 24 Feb 2011 13:59:14 +0800
Subject: [PATCH] Add the quirk support for stoping/restarting bluetooth service

It is found that the bluetooth modules with USB VID/PIDs [0a5c:219c]
[0a5c:21bc] and [413c:8187] are causing random S4 hangs on various
laptops with SandyBridge chipset.

The hangs can be observed by repeating hibernate/resume in a 250
iterations. The successful cycles number before the hang is
usually ranged in tens, though it varies on different types of
laptops.

This patch added a parameter for the use as

	pm-hibernate --quirk-bluetooth-service-off

and a couple of USB ID quirks I found with this S4 problem.

Signed-off-by: Keng-Yu Lin keng-yu@canonical.com
---
 pm/sleep.d/44bluetooth-known-quirk |   34 +
 pm/sleep.d/45bluetooth-service |   41 
 pm/sleep.d/Makefile.am |2 +
 3 files changed, 77 insertions(+), 0 deletions(-)
 create mode 100755 pm/sleep.d/44bluetooth-known-quirk
 create mode 100755 pm/sleep.d/45bluetooth-service

diff --git a/pm/sleep.d/44bluetooth-known-quirk b/pm/sleep.d/44bluetooth-known-quirk
new file mode 100755
index 000..7241ec8
--- /dev/null
+++ b/pm/sleep.d/44bluetooth-known-quirk
@@ -0,0 +1,34 @@
+#!/bin/bash
+
+. ${PM_FUNCTIONS}
+
+quirks=0a5c:219c 0a5c:21bc 413c:8187
+
+btusbget() {
+local dev usb
+usb=/sys/bus/usb/devices
+for dev in $usb/*; do
+	[[ -f ${dev}/bDeviceClass ]] || continue
+	[[ $(cat ${dev}/bDeviceClass) = e0 ]] || continue # Wireless
+	[[ -f ${dev}/bDeviceProtocol ]] || continue
+	[[ $(cat ${dev}/bDeviceProtocol) = 01 ]] || continue # Bluetooth
+	case $1 in
+	vendor) echo $(cat ${dev}/idVendor) ;;
+	device) echo $(cat ${dev}/idProduct) ;;
+	esac
+	break
+done
+}
+
+case $1 in
+	hibernate|suspend)
+		# known bluetooth devices needing to stop bluetoothd
+		for usbid in $quirks; do
+			if [ $(btusbget vendor):$(btusbget device) == $usbid ] ; then
+add_parameters --quirk-bluetooth-service-off
+			fi
+		done
+		;;
+	thaw|resume)
+		;;
+esac
diff --git a/pm/sleep.d/45bluetooth-service b/pm/sleep.d/45bluetooth-service
new file mode 100755
index 000..969ca86
--- /dev/null
+++ b/pm/sleep.d/45bluetooth-service
@@ -0,0 +1,41 @@
+#!/bin/bash
+
+. ${PM_FUNCTIONS}
+
+for opt in $PM_CMDLINE; do
+	case ${opt##--quirk-} in # just quirks, please
+		bluetooth-service-off) 	   QUIRK_BLUETOOTH_SERVICE_OFF=true ;;
+		bluetooth-none) 	   QUIRK_BLUETOOTH_NONE=true ;;
+		*) continue ;;
+	esac
+done
+
+quirk() { is_set $1  [ -z $QUIRK_BLUETOOTH_NONE ]; }
+
+suspend_bluetooth_service()
+{
+	quirk ${QUIRK_BLUETOOTH_SERVICE_OFF} 	stopservice bluetooth
+}
+
+resume_bluetooth_service()
+{
+	quirk ${QUIRK_BLUETOOTH_SERVICE_OFF} 	restartservice bluetooth
+}
+
+help() {
+	echo  # first echo makes it look nicer.
+	echo Bluetooth quirk handler options:
+	echo
+	echo   --quirk-bluetooth-service-off
+	echo   --quirk-bluetooth-none
+}
+
+case $1 in
+	hibernate|suspend)
+		suspend_bluetooth_service
+		;;
+	thaw|resume)
+		resume_bluetooth_service
+		;;
+	help) help ;;
+esac
diff --git a/pm/sleep.d/Makefile.am b/pm/sleep.d/Makefile.am
index 2350825..88df79c 100644
--- a/pm/sleep.d/Makefile.am
+++ b/pm/sleep.d/Makefile.am
@@ -4,6 +4,8 @@ sleep_SCRIPTS =			\
 	00logging		\
 	00powersave		\
 	01grub			\
+	44bluetooth-known-quirk	\
+	45bluetooth-service	\
 	49bluetooth		\
 	55NetworkManager	\
 	75modules		\
-- 
1.7.1

Bug#614902: Info received (Bug#614902: Info received (Bug#614902: Acknowledgement (bluetooth service needs to be stopped/restarted for successful hibernations)))

[Keng-Yu Lin]

For those who are interested, the bug is also tracked at
http://launchpad.net/bugs/715643 for Ubuntu.



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

Bug#602358: ITP: rtl8192ce-dkms -- Realtek RTL8192CE driver in DKMS format.

[Keng-Yu Lin]

2010/11/5 Ying-Chun Liu (PaulLiu) grandp...@gmail.com:
 Hi all,

 Just a reference, the package is already in mentors and waiting for
 sponsoring.
 http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=rtl8192ce-dkms

 I roughly looking into the source package and found
 1. firmware/RTL8192CE/*.bin is not free software.
   The license is in firmware/RTL8192CE/Realtek-Firmware-License.txt
   So this package cannot be in main.
 2. HAL/rtl8192/rtl8192c/r8192C_hwimg.c
   It's under GPL, but it's array of bytes.

 Regards,
 Paul


For 2., just FYI, there is a precedent of removing that embedded
firmware fof r8192su in debian kernel package. Both drivers should be
much the same.



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

Bug#602358: ITP: rtl8192ce-dkms -- Realtek RTL8192CE driver in DKMS format.

[Keng-Yu Lin]

2010/11/5 Stefan Lippers-Hollmann s@gmx.de:
 Hi

 On Thursday 04 November 2010, Ben Hutchings wrote:
 On Thu, 2010-11-04 at 19:21 +0100, Julien Cristau wrote:
  On Thu, Nov  4, 2010 at 10:59:41 +0800, Keng-Yu Lin wrote:
 [...]
   * Package name    : rtl8192ce-dkms
     Version         : 2.6.0003.0628.2010+dfsg
     Upstream Author : Realtek Semiconductor Corporation
   * URL             : http://www.realtek.com
   * License         : GPLv2
     Programming Lang: C
     Description     : Realtek RTL8192CE driver in DKMS format.
  
    This package contains Realtek 802.11 Linux wireless driver
    for use with Realtek RTL8192CE-based hardware.
 
  Why is that driver not in the standard kernel package?

 Because it's not upstream.  So the next question is, why is it not
 upstream (in staging)?

 This appears to be scheduled for 2.6.38:
        http://www.spinics.net/lists/linux-wireless/msg58284.html
        Message-ID: 4ccd856e.9010...@lwfinger.net

 as follow up to
        http://www.spinics.net/lists/linux-wireless/msg58273.html
        Message-ID: 4ccce60f.6090...@lwfinger.net

 at least the required firmware for RTL8192CE and RTL8712U (replacing
 RTL8192SU/ r8192s_usb in 2.6.37) has been merged into linux-firmware.git
        http://lkml.indiana.edu/hypermail/linux/kernel/1011.0/00610.html
        Message-ID: 4cd014ec.e0ho4xdm0+tov1xt%larry.fin...@lwfinger.net
        
 http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree;f=rtlwifi

 Assuming RTL8192CE support gets merged for 2.6.38, introducing a new
 package providing dkms support it during a freeze might not be very
 effective. Once it gets actually merged, a backport to (then current)
 2.6.37 should be relatively trivial.

 Regards
        Stefan Lippers-Hollmann


It will be very nice if someone is already working and getting this
driver in staging.

think to close this bug soon and please re-open it if there is still
need for this package.



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

Bug#602358: ITP: rtl8192ce-dkms -- Realtek RTL8192CE driver in DKMS format.

[Keng-Yu Lin]

2010/11/5 Ben Hutchings b...@decadent.org.uk:
 On Thu, 2010-11-04 at 19:21 +0100, Julien Cristau wrote:
 On Thu, Nov  4, 2010 at 10:59:41 +0800, Keng-Yu Lin wrote:

  Package: wnpp
  Severity: wishlist
  Owner: Keng-Yu Lin ken...@lexical.tw
 
  * Package name    : rtl8192ce-dkms
    Version         : 2.6.0003.0628.2010+dfsg
    Upstream Author : Realtek Semiconductor Corporation
  * URL             : http://www.realtek.com
  * License         : GPLv2
    Programming Lang: C
    Description     : Realtek RTL8192CE driver in DKMS format.
 
   This package contains Realtek 802.11 Linux wireless driver
   for use with Realtek RTL8192CE-based hardware.

 Why is that driver not in the standard kernel package?

 Because it's not upstream.  So the next question is, why is it not
 upstream (in staging)?

 Ben.

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


Because staging tree is a place to dump the code temporarily if you
commit to improve the driver and make it upstream eventually.

From [1], it is not a place to dump code and then run away, hoping
that someone else will do the cleanup work for you.  While there are
developers available to do this kind of work, you need to get someone
to agree to babysit the code.

I think it is more like the responsibility for someone from Realtek or
surely someone with wireless expertise.

For this case, I would like it better to enable the hardware for
debian and its downstream users and update the package every time
Realtek drops a new version.

[1] http://kerneltrap.org/mailarchive/linux-kernel/2008/6/10/2086954



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

Bug#602358: ITP: rtl8192ce-dkms -- Realtek RTL8192CE driver in DKMS format.

[Keng-Yu Lin]

Package: wnpp
Severity: wishlist
Owner: Keng-Yu Lin ken...@lexical.tw

* Package name: rtl8192ce-dkms
  Version : 2.6.0003.0628.2010+dfsg
  Upstream Author : Realtek Semiconductor Corporation
* URL : http://www.realtek.com
* License : GPLv2
  Programming Lang: C
  Description : Realtek RTL8192CE driver in DKMS format.

 This package contains Realtek 802.11 Linux wireless driver
 for use with Realtek RTL8192CE-based hardware.



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

Bug#597951: unblock: ibus-array/0.0.2-3

[Keng-Yu Lin]

2010/10/23 Mehdi Dogguy me...@dogguy.org:
 On 09/24/2010 08:58 PM, Adam D. Barratt wrote:
 On Fri, 2010-09-24 at 21:16 +0800, Keng-Yu Lin wrote:
 Please unblock package ibus-array

 This version of ibus-array in unstable fixes bug #596975, which is
 that ibus-array crashes with libibus2.

 The new version of ibus-array also moves the package to use the 3.0
  (quilt) source format, which isn't really appropriate at this
 stage of a freeze.

 More to the point, it also adds a build-dependency on quilt and a
 README.source describing quilt, both of which are unnecessary when
 using 3.0 (quilt).


 I didn't see any answer to Adam questions. Could you please fix your
 upload and revert the source format change in sid so that we could
 include it in Squeeze?

 Regards,

 --
 Mehdi Dogguy مهدي الدڤي
 http://dogguy.org/


Would it better to get this change from debsrc3 to debsrc1 as
testing-proposed-updates? It is not really relevant to make this
change to unstable.



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

Bug#596975: ibus-array crashes with libibus2

[Keng-Yu Lin]

2010/10/17 Jonathan Nieder jrnie...@gmail.com:
 Hi,

 Keng-Yu Lin wrote:

 (ibus-engine-array:3569): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 Is this reproducible with ibus-array 0.0.2-2?  Can you explain how to
 reproduce it?

 Thanks,
 Jonathan




Hi Jonathan:
  This is reproducible with ibus-array 0.0.2-2. It occurs when
switching the input method to ibus-array (using the ctrl+space hotkey)
and input Chinese characters with ibus-array.

  The bug is because libibus API changes. In libibus2,
g_object_unref() is not needed any more.

  Regards,
-kengyu



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

Bug#597951: unblock: ibus-array/0.0.2-3

[Keng-Yu Lin]

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

Please unblock package ibus-array

This version of ibus-array in unstable fixes bug #596975, which is that
ibus-array crashes with libibus2.

unblock ibus-array/0.0.2-3

-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 
'maverick')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-22-generic (SMP w/2 CPU cores)
Locale: LANG=zh_TW.utf8, LC_CTYPE=zh_TW.utf8 (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#596975: ibus-array crashes with libibus2

[Keng-Yu Lin]

Package: ibus-array
Version: 0.0.2-2ubuntu1~maverick1
Severity: grave

ibus-array crashes with libibus2:

(ibus-engine-array:3569): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(ibus-engine-array:3569): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(ibus-engine-array:3569): IBUS-CRITICAL **: ibus_serializable_serialize:
assertion `IBUS_IS_SERIALIZABLE (object)' failed

(ibus-engine-array:3569): IBUS-CRITICAL **: ibus_prop_list_serialize: assertion
`retval' failed

(ibus-engine-array:3569): IBUS-CRITICAL **: ibus_serializable_serialize:
assertion `retval' failed

(ibus-engine-array:3569): IBUS-CRITICAL **: ibus_message_append_args_valist:
assertion `retval' failed

(ibus-engine-array:3569): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(ibus-engine-array:3569): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed



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

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

Versions of packages ibus-array depends on:
ii  ibus  1.3.7-1New input method framework using d
ii  libc6 2.11.2-5   Embedded GNU C Library: Shared lib
ii  libglib2.0-0  2.24.2-1   The GLib library of C routines
ii  libibus2  1.3.7-1New input method framework using d
ii  libsqlite3-0  3.7.2-1SQLite 3 shared library
ii  python2.6.6-1interactive high-level object-orie
ii  python-support1.0.9  automated rebuilding support for P

ibus-array recommends no packages.

ibus-array 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