Bug#1018713: mailfilter: Filtering at pop.gmail.com doesn't work

[Elimar Riesebieter]

Package: mailfilter
Version: 0.8.8-1
Severity: grave
Justification: renders package unusable


I enabled pop on Port 995 at gmail. 2FA password is generated and works well 
fetching mails with getmail6. Running mailfilter -r -M mailfilterrc gives

Aug 16 14:18:52 mailfilter: 0.8.8 querying m...@gmail.com@pop.gmail.com.
Aug 16 14:18:53 mailfilter: Error: SSL connection could not be established: 
self-signed certificate
Aug 16 14:18:53 mailfilter: Error: SSL connection could not be established.
Aug 16 14:18:53 mailfilter: Error: Could not establish network connection.

mailfilterrc:

SERVER="pop.gmail.com"
USER="m...@gmail.com"
PASS="blafasel"
PROTOCOL="pop3/ssl"
PORT=995



-- System Information:
Debian Release: bookworm/sid
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.59-baumbart-lxtec-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mailfilter depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  libc6  2.34-7
ii  libgcc-s1  12.2.0-1
ii  libssl33.0.5-2
ii  libstdc++6 12.2.0-1

mailfilter recommends no packages.

mailfilter suggests no packages.

-- debconf information excluded

Bug#998125: libasound2-plugins: Config file for a52 plugin (60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)

[Elimar Riesebieter]

Control: severity -1 normal

Hi Jens,

* Jens Schmidt  [2021-10-30 20:27 +0200]:

> Package: libasound2-plugins
> Version: 1.2.2-2
> Severity: grave
> Justification: renders package unusable

The package is not unusable because of one use case out of many.

> Dear Maintainer,
> 
> * What led up to the situation?
> Fresh Debian 11 install.
> I want to output 5.1 sound via toslink.
> Used KDE settings to switch from analog output to digital out 5.1.
> This produced no or garbled sound and Youtube videos would
> play back way to fast without sound.
> Then I switched to digital out stereo, this worked as expected but only
> stereo.
> 
> I could trace back the error to the shipped config file for alsa's a52
> plugin: 60-a52-encoder.conf.

Well 60-a52-encoder.conf is shipped from upstream. So would you
please report this to alsa-de...@alsa-project.org and keep
998...@bugs.debian.org in Cc: ?

> 
> When I replaced that file with a much simpler one (see below) 5.1
> digital out worked as expedted.

We won't replace your a52.conf with 60-a52-encoder.conf as there are
users who might find the original conf file ok. You can create a
$HOME/.asoundrc with your configuration.

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Bug#996648: dkms: The templates in /etc/dkms are pointing do debhelper 7

[Elimar Riesebieter]

Control: found -1 2.6.1-4
Control: found -1 2.8.4-3
* Elimar Riesebieter  [2021-10-16 21:20 +0200]:

> Package: dkms
> Version: 2.8.7-2
> Severity: serious
> Justification: 5
> X-Debbugs-Cc: hostmast...@hostsharing.de


-- 
  Numeric stability is probably not all that
  important when you're guessing;-)

Bug#996648: dkms: The templates in /etc/dkms are pointing do debhelper 7

[Elimar Riesebieter]

Package: dkms
Version: 2.8.7-2
Severity: serious
Justification: 5
X-Debbugs-Cc: hostmast...@hostsharing.de

Dear maintainers,

please adjust the control file in the templates provided in
/etc/dkms to point to at least version 12 of debhelper. This should
be backported to stable and oldstable as well. Check
whether debian/compat is needed (oldoldstable?). Installing
module binaries are complaining about version 7 which blocks the
setup of remaining packages.

Thanks
Elimar

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

Kernel: Linux 5.10.73-baumbart-lxtec-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dkms depends on:
ii  build-essential12.9
ii  clang-13 [c-compiler]  1:13.0.0-5
ii  coreutils  8.32-4+b1
ii  dctrl-tools2.24-3+b1
ii  dpkg-dev   1.20.9
ii  gcc [c-compiler]   4:11.2.0-2
ii  gcc-10 [c-compiler]10.3.0-11
ii  gcc-11 [c-compiler]11.2.0-9
ii  kmod   29-1
ii  lsb-release11.1.0
ii  make   4.3-4.1
ii  patch  2.7.6-7

Versions of packages dkms recommends:
ii  fakeroot  1.26-1
pn  linux-headers-686-pae | linux-headers-amd64 | linux-headers-gene  
ii  sudo  1.9.5p2-3

Versions of packages dkms suggests:
ii  e2fsprogs  1.46.4-1
pn  menu   

-- no debconf information

Bug#994179: Upstream mess

[Elimar Riesebieter]

Control: severity -1 normal
Control: tags -1 + wontfix

Hi Dan,

severity critical means "makes unrelated software on the system (or
the whole system) break, or causes serious data loss, or introduces
a security hole on systems where you install the package."

So is your system damaged or burned down? Did you loose any data?
Severity reseted hereby.

* 積丹尼 Dan Jacobson  [2021-09-26 14:23 +0800]:

> several 994179 critical
> thanks
> 
> # alsactl restore
> alsa-lib parser.c:2372:(load_toplevel_config) Unable to find the top-level 
> configuration file '/usr/share/alsa/ucm2/ucm.conf'.
> alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use 
> case configuration -2
> alsa-lib parser.c:2372:(load_toplevel_config) Unable to find the top-level 
> configuration file '/usr/share/alsa/ucm2/ucm.conf'.
> alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:2 use 
> case configuration -2
> 
> One would think that doing
> 
> # aptitude install alsa-ucm-conf
> 
> a non dependency, would fix it.
> 
> Alas, no:
> 
> # alsactl restore
> alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model 
> (HD-Audio Generic at 0xfe96 irq 46)
> alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use 
> case configuration -6
> alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model 
> (HDA ATI HDMI at 0xfe964000 irq 45)
> alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:2 use 
> case configuration -6
> 
> https://github.com/alsa-project/alsa-utils/issues/101

According to this issue the error is harmless for the legacy
hardware.

> 
> https://github.com/alsa-project/alsa-lib/issues/159

According to this issue one can add -U parameter to the alsactl call
in the initscripts (systemd or whatever). This issue is tagged
'wonfix' as I do with this bug as well.

Elimar
-- 
.~.
/V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^

Bug#991683: [Pkg-alsa-devel] Bug#991683: libasound2-plugins: version 1.2.2-dmo2 >> no sound

[Elimar Riesebieter]

Hi Alain Michel

* alain-michel  [2021-07-30 11:32 +0200]:

> Package: libasound2-plugins
> Version: 1.2.2-dmo2

This package isn't maintained by the official Debian maintainers.
Bugs popped up from deb-multimedia.org have to be filed to the
dmo.changes mailing list [0].

[0] https://deb-multimedia.org/faq#q5

Bug closed hereby.

Elimar
-- 
  Experience is something you don't get until
  just after you need it!

Bug#983632: Backport to buster

[Elimar Riesebieter]

Dear maintainers,

is there any chance to get an appropriate backport for buster?
According to [1] buster is vulnerable.

[1] https://security-tracker.debian.org/tracker/source-package/salt

Thanks in advance

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)

Bug#966424: inxi: Running latest sid version I get many "Global symbol (did you forget to declare " errors

[Elimar Riesebieter]

Package: inxi
Version: 3.1.05-1-1
Severity: grave
Justification: renders package unusable

Dear maintainer,

Running inxi I get:

$ inxi -F
Global symbol "%row" requires explicit package name (did you forget to declare 
"my %row"?) at /bin/inxi line 8749.
[...]
Global symbol "@rows" requires explicit package name (did you forget to declare 
"my @rows"?) at /bin/inxi line 8817.
Global symbol "$smartctl_missing" requires explicit package name (did you 
forget to declare "my $smartctl_missing"?) at /bin/inxi line 8856.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 8938.
[...]
Global symbol "@by_path" requires explicit package name (did you forget to 
declare "my @by_path"?) at /bin/inxi line 8946.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 8999.
[...]
Global symbol "@by_path" requires explicit package name (did you forget to 
declare "my @by_path"?) at /bin/inxi line 9570.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 9683.
Global symbol "@vendors" requires explicit package name (did you forget to 
declare "my @vendors"?) at /bin/inxi line 9709.
[...]
Global symbol "$b_nvme" requires explicit package name (did you forget to 
declare "my $b_nvme"?) at /bin/inxi line 10049.
Global symbol "$nvme" requires explicit package name (did you forget to declare 
"my $nvme"?) at /bin/inxi line 10052.
[...]
Global symbol "$b_hddtemp" requires explicit package name (did you forget to 
declare "my $b_hddtemp"?) at /bin/inxi line 10071.
Global symbol "$hddtemp" requires explicit package name (did you forget to 
declare "my $hddtemp"?) at /bin/inxi line 10074.
[...]
Unmatched right curly bracket at /bin/inxi line 10203, at end of line
/bin/inxi has too many errors.


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

Kernel: Linux 5.4.53-toy-lxtec-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages inxi depends on:
ii  pciutils  1:3.7.0-2
ii  perl  5.30.3-4
ii  procps2:3.3.16-5

Versions of packages inxi recommends:
ii  bind9-dnsutils [dnsutils]  1:9.16.4-1
ii  dmidecode  3.2-3
ii  dnsutils   1:9.16.4-1
ii  file   1:5.38-5
ii  hddtemp0.3-beta15-53
ii  iproute2   5.7.0-1
ii  kmod   27+20200310-2
ii  lm-sensors 1:3.6.0-2
pn  mesa-utils 
ii  net-tools  1.60+git20180626.aebd88e-1
ii  sudo   1.9.1-2
pn  tree   
ii  usbutils   1:012-2
pn  x11-utils  
pn  x11-xserver-utils  

Versions of packages inxi suggests:
ii  curl  7.68.0-1+b1
pn  libcpanel-json-xs-perl | libjson-xs-perl  
pn  libxml-dumper-perl
ii  perl [libhttp-tiny-perl]  5.30.3-4
ii  wget  1.20.3-1+b3

-- no debconf information

Bug#963046: libcddb-get-perl: freedb server down

[Elimar Riesebieter]

Control: tags -1 patch

* Stephan Seitz  [2020-06-18 12:18 +0200]:

> Package: libcddb-get-perl
> Version: 2.28-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> the freedb.freedb.org server was switched off since April, so you can’t 
> get any CD information anymore.
> 
> I found that you can use the gnudb.gnudb.org server.
> 
> Maybe you should change the default server.

Attached patch should fix the issue.

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)
From 81bbf0bf33736f9ff7df4030323148dc5049b36e Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Tue, 21 Jul 2020 11:55:24 +0200
Subject: [PATCH] Replace freedb server with gnudb server

---
 CDDB_get.pm | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/CDDB_get.pm b/CDDB_get.pm
index f446214..35e643d 100644
--- a/CDDB_get.pm
+++ b/CDDB_get.pm
@@ -66,9 +66,9 @@ my $CDROM_MSF=0x02;
 
 # default config
 
-my $CDDB_HOST = "freedb.freedb.org";
-my $CDDB_PORT = 8880;
-my $CDDB_MODE = "cddb";
+my $CDDB_HOST = "gnudb.gnudb.org";
+my $CDDB_PORT = 80;
+my $CDDB_MODE = "http";
 my $CD_DEVICE = "/dev/cdrom";
 
 my $HELLO_ID  = "root nowhere.com fastrip 0.77";
@@ -608,9 +608,9 @@ CDDB - Read the CDDB entry for an audio CD in your drive
 
  # following variables just need to be declared if different from defaults
 
- $config{CDDB_HOST}="freedb.freedb.org";	# set cddb host
- $config{CDDB_PORT}=8880;			# set cddb port
- $config{CDDB_MODE}="cddb";			# set cddb mode: cddb or http
+ $config{CDDB_HOST}="gnudb.gnudb.org";		# set cddb host
+ $config{CDDB_PORT}=80;			# set cddb port
+ $config{CDDB_MODE}="http";			# set cddb mode: cddb or http
  $config{CD_DEVICE}="/dev/cdrom";		# set cd device
 
  # user interaction welcome?
-- 
2.28.0.rc1



signature.asc
Description: PGP signature

Bug#962073: alsa-info is calling home without asking

[Elimar Riesebieter]

* Christoph Berg  [2020-06-02 23:23 +0200]:

> Package: alsa-utils
> Version: 1.2.2-1
> Severity: serious
> 
> Hi,
> 
> I just launched alsa-info and was surprised that it presented me with
> this popup box:
> 
> ┌───┐
> │ Newer version of ALSA-Info has been   │
> │ found │
> │   │
> │ Do you wish to download it?   │
> ├───┤
> │ < Yes > < No  >   │
> └───┘
> 
> Note that this box comes before it asks if the generated report should
> be uploaded somewhere.
> 
> I don't think it is appropriate for a simple CLI utility to call home
> without asking first.

What do you mean with "call home"?

There is indeed a new version available in [0] and [1]. It will be
contributed witch the next release of alsa-utils. So what makes this
"bug" serious?

[0] 
https://git.alsa-project.org/?p=alsa-utils.git;a=history;f=alsa-info/alsa-info.sh
[1] https://git.alsa-project.org/?p=alsa-utils.git;a=summary

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

Bug#959684: [cveh...@saltstack.com] Action Required: SaltStack CVE Follow-Up Patch

[Elimar Riesebieter]

Hi Salvatore and others,

* Salvatore Bonaccorso  [2020-05-06 13:09 +0200]:

> Hi Elimar,
> 
> On Wed, May 06, 2020 at 10:36:42AM +0200, Elimar Riesebieter wrote:
> > Hi all,
> > 
> > please notice the attached note from saltstack! I assume this is not
> > integrated into DSA 4676-1, isn't it?
> 
> Yes this is right, those parts were missing. 
> 
> Do you have possibility to test updated salt packages for stretch?

we fired up your kindly provided deb9u4 packages and run the
verification script http://em.saltstack.com/F1sH900oN0P0M17U000Qhf7
with the following result:

CVE-2020-11651 - OK
CVE-2020-11652 - OK

Thanks for cooperation
Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Bug#959684: [cveh...@saltstack.com] Action Required: SaltStack CVE Follow-Up Patch

[Elimar Riesebieter]

Hi all,

please notice the attached note from saltstack! I assume this is not
integrated into DSA 4676-1, isn't it?

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)
--- Begin Message ---
SaltStack CVE Follow-Up Patch
We have a few important developments to share with you regarding CVE-2020-11651 
and CVE-2020-11652. 

-  Follow-up patch for Salt 2017.x and earlier  -  Patch 
Validation to confirm your Salt environment is secure  -  CVE Technical 
Guide
ACTIVE CVE: 
IF YOU HAVE NOT YET UPDATED SALT OR APPLIED PATCHES, 
PLEASE DO SO IMMEDIATELY
FOLLOW-UP PATCH FOR SALT 2017.X AND EARLIER
 If you have already applied the patch for Salt 2017.x or earlier, there is a 
follow-up patch to apply. You can download the patch and instructions below. 
**This applies to 2017.x, 2016.x, and 2015.x. This does NOT apply to 2018.x, 
2019.x, or 3000.x.** 

- 2015.x   - 
2016.x   - 2017.x 
  - CVE Technical Guide 
 

 The original patch for versions 2017.x and earlier secured against arbitrary 
commands running on Salt minions and eliminated the exposure (CVE-2020-11651 
). This 
additional patch is required to completely resolve arbitrary directory access 
to authenticated users (CVE-2020-11652 
).
PATCH VALIDATION SCRIPTS
 Once you have updated / patched Salt, you can verify that your Salt 
environment is secure. We are offering this to all Salt users to ensure the 
patches were applied correctly and optionally perform a non-disruptive 
exploitation test. Details can be found here: CVE Patch Verification. 
 We strongly encourage you to 
take advantage of this tool. We understand many of you want that additional 
assurance and confirmation.
CVE TECHNICAL GUIDE
 This document provides technical guidelines for applying CVE-2020-11651 / 
CVE-2020-11652 patches and performing exploitation assessment and check up 
analysis. It is an additional resource that can be leveraged by your technical 
teams for in depth analysis of exploitation scenarios and how to check for 
these using a variety of techniques. Download the CVE Technical Guide Here. 

HELPFUL RESOURCES 

- PDF Description of the CVEs 
 - Upgrading your Salt 
Infrastructure   - SaltStack 
Response Policy for Cybersecurity Vulnerabilities and Exposures (CVE) 
 - If you run into any 
major obstacles and can’t find a solution in the provided resources, you can 
email cveh...@saltstack.com 
--- End Message ---


signature.asc
Description: PGP signature

Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

[Elimar Riesebieter]

There are official patches from saltstack available here:

2018.3.x 
2017.7.x 
2016.x.x 

I requested them via
https://www.saltstack.com/lp/request-patch-april-2020/

Please notice that there are more CVE' not fixed yet:

CVE-2019-17361 => 2016.11.2+ds-1+deb9u2 and 2018.3.4+dfsg1-6
CVE-2019-1010259 => 2016.11.2+ds-1+deb9u2
CVE-2018-15751 => 2016.11.2+ds-1+deb9u2

See https://security-tracker.debian.org/tracker/source-package/salt.

I asked saltstack for patches of those as well.

HTH
Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

Bug#926305: nis startup scripts are completely broken

[Elimar Riesebieter]

* Anton Ivanov  [2019-04-18 15:05 +0100]:

> That is not an advice.
> 
> If nscd is a required dependency, NIS should bring it in.

This is not a "must have"

> 
> Presently it is not.
> 
> Still broken

The advice is also mentioned in the changelog:

  * Drop -no-dbus from YPBINDARGS= in /etc/default/nis.
We no longer build nis with NetworkManager/D-Bus support, so setting
this option made ypbind fail to start. (Closes: #906436)

So setting "YPBINDARGS=" in /etc/default/nis should be your first step to get
nis working in buster ;-)

Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche


signature.asc
Description: PGP signature

Bug#926305: nis startup scripts are completely broken

[Elimar Riesebieter]

* Elimar Riesebieter  [2019-04-03 11:06 +0200]:

> * Anton Ivanov  [2019-04-03 09:43 +0100]:
> 
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > 
> > Startup scripts are completely broken. Something in the systemd 
> > conversion/autogeneration.
> > 
> > The ypbind binary is never started, the script goes into "backgrounded" and 
> > fails. From there
> > on the system is unusable - you cannot log in, UIDs and groups do not 
> > resolve, etc.
> > 
> > The same system operated correctly before buster upgrade and will operate 
> > correctly if
> > ypbind is invoked from the command line.
> > 
> > This looks like a pure systemd conversion issue of some sort.
> 
> At my systems installing nscd helped. As well setting "YPBINDARGS="
> in /etc/default/nis must be.

This bug should be closed as there is no response from the reporter.
As well it seems to be fixed following the advices given above,
though.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


signature.asc
Description: PGP signature

Bug#925455: alsa volume never saved/restored

[Elimar Riesebieter]

* gregor herrmann  [2019-04-09 18:09 +0200]:

> On Sun, 07 Apr 2019 19:39:34 +0200, Elimar Riesebieter wrote:
> 
> > > > Jordi is MIA at the moment. Tried to reach him since a few days. I
> > > > can't upload the fix myself, though...
> > > I pinged him on a different channel, but if he doesn't have time I'm
> > > happy to offer a sponsored upload to fix this bug.
> > Would be nice. Yes, please :-)
> 
> It looks like Jordi is still busy, so I decided to help out and
> uploaded 1.1.8-2 from the git repo. 

Many thanks :-)

Elimar
-- 
.~.
/V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^


signature.asc
Description: PGP signature

Bug#925455: alsa volume never saved/restored

[Elimar Riesebieter]

* gregor herrmann  [2019-04-07 18:16 +0200]:

> On Sun, 07 Apr 2019 18:05:06 +0200, Elimar Riesebieter wrote:
> 
> > > There is a commit in the packaging repo which claims to fix this bug:
> > > https://salsa.debian.org/alsa-team/alsa-utils/commit/af161676131e94bbaed72f37d0c5d4c6685a119e
> > Jordi is MIA at the moment. Tried to reach him since a few days. I
> > can't upload the fix myself, though...
> 
> I pinged him on a different channel, but if he doesn't have time I'm
> happy to offer a sponsored upload to fix this bug.

Would be nice. Yes, please :-)

-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche


signature.asc
Description: PGP signature

Bug#925455: alsa volume never saved/restored

[Elimar Riesebieter]

* gregor herrmann  [2019-04-07 17:46 +0200]:

> Control: tag -1 + patch pending
> 
> On Mon, 25 Mar 2019 12:05:36 +0100, Laurent Bigonville wrote:
> 
> > The more obvious solution would of course be to remove the condition in the
> > .service file
> 
> There is a commit in the packaging repo which claims to fix this bug:
> https://salsa.debian.org/alsa-team/alsa-utils/commit/af161676131e94bbaed72f37d0c5d4c6685a119e

Jordi is MIA at the moment. Tried to reach him since a few days. I
can't upload the fix myself, though...

Elimar
-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds


signature.asc
Description: PGP signature

Bug#926305: nis startup scripts are completely broken

[Elimar Riesebieter]

* Anton Ivanov  [2019-04-03 09:43 +0100]:

> Package: nis
> Version: 3.17.1-3+b1
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> Startup scripts are completely broken. Something in the systemd 
> conversion/autogeneration.
> 
> The ypbind binary is never started, the script goes into "backgrounded" and 
> fails. From there
> on the system is unusable - you cannot log in, UIDs and groups do not 
> resolve, etc.
> 
> The same system operated correctly before buster upgrade and will operate 
> correctly if
> ypbind is invoked from the command line.
> 
> This looks like a pure systemd conversion issue of some sort.

At my systems installing nscd helped. As well setting "YPBINDARGS="
in /etc/default/nis must be.

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

Bug#870406: There is a possible patch available

[Elimar Riesebieter]

Hi all,

did someone checked

https://git.xiph.org/?p=libao.git;a=commit;h=d5221655dfd1a2156aa6be83b5aadea7c1e0f5bd
 

?

Elimar
-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds


signature.asc
Description: PGP signature

Bug#921016: start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure

[Elimar Riesebieter]

Control: tags -1 patch

* Brian May  [2019-02-12 17:06 +1100]:

> > I don't know whether this is an issue from amavisd-new or dpkg
> > (start-stop-daemon) but feel free to assign it properly.
> 
> Bug #921557 is relevant here.

Attached patch works on my sysvinit system.

Elimar
-- 
  The path to source is always uphill!
-unknown-
From 3df4cd09ec8231c468347a7478e9e4940139b97e Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Tue, 12 Feb 2019 10:31:40 +0100
Subject: [PATCH] Fix initscript to run non-root pid file.

---
 debian/amavisd-new.amavis.init | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/amavisd-new.amavis.init b/debian/amavisd-new.amavis.init
index 7890ce7..c07c05c 100644
--- a/debian/amavisd-new.amavis.init
+++ b/debian/amavisd-new.amavis.init
@@ -42,7 +42,7 @@ test -f ${DAEMON} || exit 0
 set -e
 
 START="--start --quiet --pidfile $PIDFILE --startas ${DAEMON}"
-STOP="--stop --quiet --pidfile $PIDFILE"
+STOP="--stop --quiet --pidfile $PIDFILE --user amavis"
 PARAMS=
 
 check_noncompatible_upgrade() {
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#920720: Regession: Fix unescaped left brace in regex makes amavid-new unusable

[Elimar Riesebieter]

Control: tags -1 patch


-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche

Bug#921016: start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure

[Elimar Riesebieter]

Package: amavisd-new
Version: 1:2.11.0-4
Severity: serious

Restarting amavisd-new like it is done by a spamassassin hook
doesn't work:

start-stop-daemon: matching only on non-root pidfile 
/var/run/amavis/amavisd.pid is insecure

If a restart i.e. triggerd by spamassassin it doesn't restart
properly and has to be started by the sys-admin again. At least on a
sysvinit-system.

I don't know whether this is an issue from amavisd-new or dpkg
(start-stop-daemon) but feel free to assign it properly.

Thanks
Elimar

-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

Bug#920720: Regession: Fix unescaped left brace in regex makes amavid-new unusable

[Elimar Riesebieter]

Package: amavisd-new
Version: 1:2.11.0-4
Followup-For: Bug #920720

Dear maintainer,

I am running attached patch since 3 days with no doubt. It should
fix the "left brace" issue.

-- 
  The path to source is always uphill!
-unknown-
>From e3e7555261a07dc05736483bd8493cbbfc4b4c09 Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Thu, 31 Jan 2019 16:25:39 +0100
Subject: [PATCH] Fix escaped brased really now

Fix escaped brased really now, hopefully.

Please notice the "blank" between the escaped left brace and the escaped right
brace.
This works fine on my system in corelation to exim4, though.


---
 amavisd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/amavisd b/amavisd
index 7f93194..1862ee8 100755
--- a/amavisd
+++ b/amavisd
@@ -28848,7 +28848,7 @@ sub run_av(@) {
 my $f = $bare_fnames->[$k];  my $multi = 0;
 if ($one_at_a_time) {  # glob templates may be substrings anywhere
   local($1);  @query_expanded = @query_template;  # start afresh
-  s{ ( {} (?: / \* )? | \* ) }
+  s{ ( \{ \} (?: / \* )? | \* ) }
{ $1 eq '{}'   ? "$tempdir/parts"
: $1 eq '{}/*' ? ($multi=1,"$tempdir/parts/$f")
: $1 eq '*'? ($multi=1,$f)  : $1
-- 
2.20.1

Bug#916052: alsa-oss FTBFS with glibc 2.28

[Elimar Riesebieter]

* Takashi Sakamoto  [2018-12-13 07:32 +0900]:

[...]

> > In file included from alsa-oss.c:736:
> > stdioemu.c:40:10: fatal error: libio.h: No such file or directory
> >  #include 
> >   ^
> > compilation terminated.
> > make[2]: *** [Makefile:517: alsa-oss.lo] Error 1
> > 
> 
> In glibc upstream, libio/libio.h had been deprecated for applications and
> became internal header in its v2.28 release. We can see below message in
> its release note[1].
> 
> ```
> * The nonstandard header files  and <_G_config.h> are no longer
>   installed.  Software that was using either header should be updated to
>   use standard  interfaces instead.
> ```
> 
> I posted PR to fix the FTBFS into github.com repository[1]. (In last month
> we introduced github service to our workload for reviewing/merging tasks
> just for userspace stuffs.)
> 
> In next release (v1.1.7), the fix will be merged and released.
> 
> [1] https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html
> [2] https://github.com/alsa-project/alsa-oss/pull/1

Many thanks for cooperation!

Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

Bug#916052: [b...@debian.org] Bug#916052: alsa-oss FTBFS with glibc 2.28

[Elimar Riesebieter]

Control: forwarded -1 alsa-de...@alsa-project.org


Hi,

could you please investigate? It seems as alsa-oss doesn't built
with glibc 2.28.

Thanks in advance
Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)
--- Begin Message ---
Source: alsa-oss
Version: 1.1.6-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html

...
In file included from alsa-oss.c:736:
stdioemu.c:40:10: fatal error: libio.h: No such file or directory
 #include 
  ^
compilation terminated.
make[2]: *** [Makefile:517: alsa-oss.lo] Error 1

--- End Message ---

Bug#913486: [Pkg-alsa-devel] Bug#913486: libasound2: segfault on usb audio devive

[Elimar Riesebieter]

Control: reassign -1 libasound2-plugins 1.1.7-2
Control: forcemerge 912921 -1

* Grant Johnson  [2018-11-11 07:50 -0700]:

> Package: libasound2
> Version: 1.1.7-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> After upgrading from 1.1.6-1 to 1.1.7-2, the crash began every time the device
> was connected.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> I downgraded back to 1.1.6-1
> 
>* What was the outcome of this action?
> It works again
> 
>* What outcome did you expect instead?
> 
> Here is the dmesg from the crash:
> 
> [  321.160923] usb 2-3: new high-speed USB device number 4 using xhci_hcd
> [  321.319001] usb 2-3: New USB device found, idVendor=2972, idProduct=0035,
> bcdDevice= 1.05
> [  321.319007] usb 2-3: New USB device strings: Mfr=1, Product=3,
> SerialNumber=2
> [  321.319010] usb 2-3: Product: FiiO Q1
> [  321.319013] usb 2-3: Manufacturer: GuangZhou FiiO Electronics Co.,Ltd
> [  321.319015] usb 2-3: SerialNumber: FFB14517
> [  324.611237] usb 2-3: 1:3 : unsupported format bits 0x1
> [  324.819415] usbcore: registered new interface driver snd-usb-audio
> [  326.361759] pulseaudio[2051]: segfault at fff0 ip
> 7f7caa8bb906 sp 7fff6ac1f110 error 5 in
> libasound.so.2.0.0[7f7caa8ae000+8f000]
> [  326.361767] Code: 36 08 00 e8 8c 2c ff ff 66 66 2e 0f 1f 84 00 00 00 00 00
> 90 55 53 48 83 ec 08 48 8b 35 13 47 0c 00 48 85 ff 0f 84 0d 01 00 00 <48> 8b 
> 57
> 20 48 8b 4f 28 48 89 fb 31 ed 48 8d 05 f6 46 0c 00 48 89
> [  327.803101] pulseaudio[3544]: segfault at 51 ip 7f965056391a sp
> 7ffc5cbca870 error 6 in libasound.so.2.0.0[7f9650556000+8f000]
> [  327.803108] Code: 55 53 48 83 ec 08 48 8b 35 13 47 0c 00 48 85 ff 0f 84 0d
> 01 00 00 48 8b 57 20 48 8b 4f 28 48 89 fb 31 ed 48 8d 05 f6 46 0c 00 <48> 89 
> 11
> 48 89 4a 08 48 39 c6 74 05 48 39 00 74 75 8b 03 85 c0 74
> [  329.213504] pulseaudio[3547]: segfault at fff0 ip
> 7f30e2b3b906 sp 7ffec3480d80 error 5 in
> libasound.so.2.0.0[7f30e2b2e000+8f000]
> [  329.213511] Code: 36 08 00 e8 8c 2c ff ff 66 66 2e 0f 1f 84 00 00 00 00 00
> 90 55 53 48 83 ec 08 48 8b 35 13 47 0c 00 48 85 ff 0f 84 0d 01 00 00 <48> 8b 
> 57
> 20 48 8b 4f 28 48 89 fb 31 ed 48 8d 05 f6 46 0c 00 48 89
> [  330.451686] traps: pulseaudio[3551] general protection ip:7fbb1ef2f5d6
> sp:7ffdbe6617a8 error:0 in libasound.so.2.0.0[7fbb1eef6000+8f000]
> [  331.698768] traps: pulseaudio[3555] general protection ip:7f91d50c73b9
> sp:7ffdc2da0490 error:0 in libasound.so.2.0.0[7f91d508e000+8f000]
> [  332.940592] traps: pulseaudio[3558] general protection ip:7f24d3043906
> sp:7fff49355f10 error:0 in libasound.so.2.0.0[7f24d3036000+8f000]
> 
> 
> *** End of the template - remove these template lines ***

Symptoms are similar to #912921

Elimar
-- 
  Do you smell something burning or is it me?


signature.asc
Description: PGP signature

Bug#913133: [Pkg-alsa-devel] Bug#913133: Acknowledgement (pulseaudio crashes (SIGSEGV) after failing to set 48000 sample rate in pcm_a52.c)

[Elimar Riesebieter]

Control: reassign -1 libasound2-plugins 1.1.7-2
Control: forcemerge 912921 -1

* Felipe Sateler  [2018-11-11 10:10 -0300]:

> Control: reassign -1 libasound2
> Control: found -1 1.1.7-1
> 
> On Sat, Nov 10, 2018 at 2:48 AM ewe2  wrote:
> 
> > Hi,
> >
> > I just wanted to add that I'd been having this issue too and rolling
> > back libasound2 altogether, not just the plugins packages was
> > required. With the plugins packages rolled back I stopped having
> > segv's but the bigger issue was that nothing in a dbus session could
> > see the changes; alsa could see all devices yet pulseaudio was unable
> > to find or connect to anything but a secondary usb interface, indeed
> > it seemed to be trying to open non-existent devices under /dev/snd/. I
> > also rolled back the kernel upgrade just in case and rebooted and took
> > care to check with alsactl init and store. Only then did I recover
> > access to my internal sound card. I'm also wondering whether a recent
> > udisks2 upgrade may have also contributed, but it's very difficult to
> > pin down where exactly the breakdown is, I don't think it's pulseaudio
> > itself, it's what it depends on.
> >
> 
> Based on this information I'm reassigning to the alsa library.

The symptoms are looking like them from #912921

Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche

Bug#913409: libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2

[Elimar Riesebieter]

Control: reassign -1 libasound2-plugins 1.1.7-2
Control: forcemerge 912921 -1

* Florin Iucha  [2018-11-10 12:12 -0500]:

> Package: libasound2
> Version: 1.1.7-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
>Purchased a new USB DAC. It worked fine last night, then this morning
>it is crashing pulseaudio every time it is attached / turned on.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>Plug the USB DAC.
> 
>* What was the outcome of this action?
> 
>Nov 10 12:03:07 herakles kernel: do_general_protection: 10 callbacks 
> suppressed
>Nov 10 12:03:07 herakles kernel: traps: pulseaudio[6311] general 
> protection ip:7f8f3e557532 sp:7fff1aa8bb20 error:0 in 
> libasound.so.2.0.0[7f8f3e51e000+8f000]
> 
>* What outcome did you expect instead?
> 
>Music coming out from the headphones.

Please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912921


Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)


signature.asc
Description: PGP signature

Bug#911510: nfs-utils: scripts using rpcinfo don't find it

[Elimar Riesebieter]

Source: nfs-utils
Version: 1.3.4-2.2
Severity: grave
Tags: patch
Justification: renders package unusable


bug- and initscripts using rpcinfo are looking in $PREFIX/sbin.
Since rpcbind installs rpcinfo in $PREFIX/bin we need to adjust the
scripts as proposed in the attached patch.

Or we need to change rpcbind to install rpcinfo in $PREFIX/sbin

-- 
   Elimar
>From fd47a590a82c2bcced8c0d5f45ae8a37cb660744 Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Sun, 21 Oct 2018 09:43:58 +0200
Subject: [PATCH] Change binary dir of rpcinfo

---
 debian/nfs-common.bugscript| 2 +-
 debian/nfs-common.init | 4 ++--
 debian/nfs-kernel-server.bugscript | 2 +-
 debian/nfs-kernel-server.init  | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/debian/nfs-common.bugscript b/debian/nfs-common.bugscript
index 7e6a73a..7af3df0 100644
--- a/debian/nfs-common.bugscript
+++ b/debian/nfs-common.bugscript
@@ -2,7 +2,7 @@
 set -e
 
 echo '-- rpcinfo --' >&3
-/usr/sbin/rpcinfo -p >&3
+/usr/bin/rpcinfo -p >&3
 
 echo '-- /etc/default/nfs-common --' >&3
 cat /etc/default/nfs-common|grep -v -e '^\#' -e '^$' >&3
diff --git a/debian/nfs-common.init b/debian/nfs-common.init
index 052de51..134e53f 100644
--- a/debian/nfs-common.init
+++ b/debian/nfs-common.init
@@ -123,8 +123,8 @@ case "$1" in
log_progress_msg "statd"

# See if rpcbind is running
-   if [ -x /usr/sbin/rpcinfo ]; then
-   /usr/sbin/rpcinfo -p >/dev/null 2>&1
+   if [ -x /usr/bin/rpcinfo ]; then
+   /usr/bin/rpcinfo -p >/dev/null 2>&1
RET=$?
if [ $RET != 0 ]; then
   echo
diff --git a/debian/nfs-kernel-server.bugscript 
b/debian/nfs-kernel-server.bugscript
index eed581d..5599834 100644
--- a/debian/nfs-kernel-server.bugscript
+++ b/debian/nfs-kernel-server.bugscript
@@ -2,7 +2,7 @@
 set -e
 
 echo '-- rpcinfo --' >&3
-/usr/sbin/rpcinfo -p >&3
+/usr/bin/rpcinfo -p >&3
 
 echo '-- /etc/default/nfs-kernel-server --' >&3
 cat /etc/default/nfs-kernel-server|grep -v -e '\#' -e '^$' >&3
diff --git a/debian/nfs-kernel-server.init b/debian/nfs-kernel-server.init
index e0c51d6..f25db3f 100644
--- a/debian/nfs-kernel-server.init
+++ b/debian/nfs-kernel-server.init
@@ -90,7 +90,7 @@ case "$1" in
log_progress_msg "nfsd"

# See if rpcbind is running
-   $PREFIX/sbin/rpcinfo -p >/dev/null 2>&1
+   $PREFIX/bin/rpcinfo -p >/dev/null 2>&1
RET=$?
if [ $RET != 0 ]; then
echo
-- 
2.19.1

Bug#834298: nis: problem appears to be in invocation in /etc/init.d/nis

[Elimar Riesebieter]

* Christoph Terasa  [2018-10-17 11:56 +0200]:

> On Tue, 16 Oct 2018 14:56:57 -0600 Joe Pfeiffer 
> wrote:
> > The problem appears to be in line 172 of /etc/init.d/nis:
> > --exec ${NET}/ypbind -- $broadcast ${YPBINDARGS}
> >
> > If I execute this by hand (for my environment, which does not use
> > -broadcast and has empty YPBINDARGS), ie
> >
> > [...]
> >
> > If I delete the -- from the invocation it works.
> >
> 
> Good find, though the "--" is signaling the end of the start-stop-daemon
> options, and is not an option to ypbind. Options to the daemon (ypbind) come
> after the "--". Since your options to ypbind are empty anyway, it works in
> your case, but it might fail otherwise. This still looks like a
> bug/regression in the ypbind binary to me, not like a bug in the init.d
> script.

According to the changelog of 3.17.1-3

Drop -no-dbus from YPBINDARGS= in /etc/default/nis.
We no longer build nis with NetworkManager/D-Bus support, so setting
this option made ypbind fail to start. (Closes: #906436)

Running ypbind with no options and an empty YPBINDARGS= works here. So this bug
isn't relevant any more. Please confirm.

I am thinking about packaging

libnsl 1.2.0  
libnss_nis 3.0
ypbind-mt 
ypserv 2.5
yp-tools 4.2.2

separately to create clean packages. Whatt do you think?

libtirpc has to be updated to minimum 1.0.2 (not only in experimental!). Any co
maintaining would be great ;-) The packaging of Mark Brown aka broonie is
somewhat, h, old fashioned?  The versions are outdated. Anyway FMPOV not
maintainable.


Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Bug#910891: nis build against libgdbm.6 doesn't work as server on a sysvinit system

[Elimar Riesebieter]

* Elimar Riesebieter  [2018-10-12 22:12 +0200]:

> Package: nis
> Version: 3.17.1-3+b1
> Severity: serious
> Justification: 5 (f)
> 
> 
> Dear maintainer,
> 
> since 3.17.1-3+b1 nis dosn't work as server on a sysvinit system.
> 
> 3.17.1-3+b1:
> $ ldd /usr/sbin/ypbind
> 
[...] 

> 3.17.1-2:
> $ ldd /usr/sbin/ypbind
Should have been 3.17.1-1 !!

Well 3.17.1-3+b1 works now. Can't reproduce the bug playing with
different compile options so closing.

Sorry for the noise.

Elimar
-- 
.~.
/V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^


signature.asc
Description: PGP signature

Bug#910891: nis build against libgdbm.6 doesn't work as server on a sysvinit system

[Elimar Riesebieter]

Package: nis
Version: 3.17.1-3+b1
Severity: serious
Justification: 5 (f)


Dear maintainer,

since 3.17.1-3+b1 nis dosn't work as server on a sysvinit system.

3.17.1-3+b1:
$ ldd /usr/sbin/ypbind

linux-vdso.so.1 (0x7ffd9699)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7ff8ce6ff000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ff8ce6de000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7ff8ce6c5000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff8ce508000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ff8ce4fe000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff8ce2d8000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7ff8ce0b9000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7ff8cdd9d000)
/lib64/ld-linux-x86-64.so.2 (0x7ff8ce7a5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff8cdd98000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7ff8cdd76000)



3.17.1-2:
$ ldd /usr/sbin/ypbind

linux-vdso.so.1 (0x7ffd11af2000)
libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 
(0x7fd5fb4c4000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7fd5fb471000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fd5fb41d000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fd5fb30)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7fd5fb274000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd5fb253000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7fd5fb238000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5fb07b000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fd5faed7000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7fd5facce000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fd5fac5a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd5fac5)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fd5faa28000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fd5fa80b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7fd5fa4ef000)
/lib64/ld-linux-x86-64.so.2 (0x7fd5fb509000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fd5fa4e9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fd5fa2cb000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fd5fa0a3000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fd5fa088000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7fd5fa02c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5fa027000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7fd5fa005000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7fd5f9fb3000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fd5f9fa8000)

Elimar

-- Package-specific info:

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

Kernel: Linux 4.14.71-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  hostname   3.21
ii  libc6  2.27-6
ii  libgdbm6   1.18-2
ii  libsystemd0239-10
ii  lsb-base   9.20170808
ii  make   4.2.1-1.2
ii  netbase5.4
ii  rpcbind [portmap]  0.2.3-0.6

nis recommends no packages.

Versions of packages nis suggests:
ii  nscd  2.27-6

-- Configuration Files:
/etc/ypserv.securenets changed [not included]
/var/yp/Makefile changed [not included]

Bug#675857: [Pkg-alsa-devel] Bug#675857: pulseaudio creates .config/pulse in a root directory

[Elimar Riesebieter]

Hi gents,

* Niels Thykier  [2018-09-24 06:24 +]:

[...]
> Hi,
> 
> I added a MR on salsa for this issue[1] fixing a missing call to
> alsactl.  I could not see any (direct) calls to aumix, so these are not
> covered.  There are some calls to amixer but it does not seem to create
> .config if missing despite looking for it.
> 
> Admittedly, Daniel's solution of simply setting HOME is probably easier
> to maintain in the long run and less like to "miss" a call.

Just for the record: In stable we have 1.1.3-1 which doesn't fit to
this bug. Debian alsa pkg maintainers won't fix any older version
than that. So I close this bug hereby. BTW stable can run sysvinit
very well.

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Bug#675857: [Pkg-alsa-devel] Bug#675857: pulseaudio creates .config/pulse in a root directory

[Elimar Riesebieter]

* Niels Thykier  [2018-09-24 06:24 +]:

> On Sun, 7 Jan 2018 14:33:51 + Simon McVittie  wrote:
> > Control: retitle 675857 /etc/init.d/alsa-utils creates /.config/pulse under 
> > sysvinit
> > 
> > Forwarding the text of Daniel Reichelt's message reopening RC bug
> > #675857 (and its merged duplicates) to the bug, so that it's visible
> > to the alsa-utils maintainers and on the BTS without rummaging in "Show
> > full text".
> > 
> > I'm also retitling it to clarify which systems it affects (those that
> > boot with sysvinit or similar, but not systemd). I've checked that the
> > systemd units don't invoke aumix, and pass -E HOME=/run/home to every
> > alsactl invocation.

Hmmm, 1.0.28-1 ist compiled with "--with-alsactl-home-dir=/var/run/alsa"

So I can't reproduce?

Elimar
-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds

Bug#906568: closed by Mathieu Parent (Bug#906562: fixed in samba 2:4.8.4+dfsg-2)

[Elimar Riesebieter]

Control: reopen -1
Control: severity -1 grave

The following packages have unmet dependencies:
 samba-dsdb-modules : Depends: libldb1 (< 2:1.4.0+really1.3.6~) but 
2:1.4.0+really1.3.6-1 is to be installed
E: Unable to correct problems, you have held broken packages.

Elimar
-- 
  From The Collaborative International Dictionary of English v.0.48 [gcide]:
  .
  arsehole \arse"hole`\ ([aum]rs"h[=o]l`), n.
 1. execretory opening at the end of the alimentary canal.

Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1

[Elimar Riesebieter]

Package: cups-filters
Followup-For: #907026
Control: tags -1 +confirmed

I get a 
`(/usr/lib/cups/filter/foomatic-rip) crashed on signal 11'
on a Samsung ML-6060 as well.

Downgrading to 1.20.4-1 fixes the problem.

Ciao
Elimar
-- 
  The path to source is always uphill!
-unknown-

Bug#906568: samba-dsdb-modules not installable

[Elimar Riesebieter]

Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable

# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is 
to be installed
E: Unable to correct problems, you have held broken packages.

-- Package-specific info:
* /etc/samba/smb.conf not present
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5+b1
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.9.1-1
ii  libc6 2.27-5
ii  libldb1   2:1.4.0+really1.3.5-2
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpopt0  1.16-11
ii  libpython2.7  2.7.15-3
ii  libtalloc22.1.14-1
ii  libtdb1   1.3.15-4
ii  libtevent00.9.36-2
ii  lsb-base  9.20170808
ii  procps2:3.3.15-2
ii  python2.7.15-3
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.8.4+dfsg-1
ii  python2.7 2.7.15-3
ii  samba-common  2:4.8.4+dfsg-1
ii  samba-common-bin  2:4.8.4+dfsg-1
ii  samba-libs2:4.8.4+dfsg-1
ii  tdb-tools 1.3.15-4

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.8.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.4+dfsg-4
ii  bind9utils 1:9.11.4+dfsg-4
pn  ctdb   
ii  ldb-tools  2:1.4.0+really1.3.5-2
ii  ntp1:4.2.8p12+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.8.4+dfsg-1

-- no debconf information

Bug#906562: samba-dsdb-modules not installable

[Elimar Riesebieter]

Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable

# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is 
to be installed
E: Unable to correct problems, you have held broken packages.

-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5+b1
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.9.1-1
ii  libc6 2.27-5
ii  libldb1   2:1.4.0+really1.3.5-2
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpopt0  1.16-11
ii  libpython2.7  2.7.15-3
ii  libtalloc22.1.14-1
ii  libtdb1   1.3.15-4
ii  libtevent00.9.36-2
ii  lsb-base  9.20170808
ii  procps2:3.3.15-2
ii  python2.7.15-3
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.8.4+dfsg-1
ii  python2.7 2.7.15-3
ii  samba-common  2:4.8.4+dfsg-1
ii  samba-common-bin  2:4.8.4+dfsg-1
ii  samba-libs2:4.8.4+dfsg-1
ii  tdb-tools 1.3.15-4

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.8.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.4+dfsg-4
ii  bind9utils 1:9.11.4+dfsg-4
pn  ctdb   
ii  ldb-tools  2:1.4.0+really1.3.5-2
ii  ntp1:4.2.8p12+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.8.4+dfsg-1

-- no debconf information
# Global parameters
[global]
workgroup = LXTEC
realm = HOME.LXTEC.NET
netbios name = TOY
server role = active directory domain controller
#server role = standalone server
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, 
winbind, ntp_signd, kcc, dnsupdate
#server services = s3fs, rpc, nbt, wrepl, kdc, drepl, winbind, 
ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
interfaces = 192.168.200.1


 Debugging/Accounting 

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.toy
#   log level = 3

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
#   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d

# This parameter determines if nmbd(8) advertises itself as a time server to 
Windows clients.
   time server = yes

printing = bsd
printcap name = /dev/null

#nsupdate command = nsupdate


[netlogon]
comment = Logon scripts for Users
#path = /var/lib/samba/sysvol/home.lxtec.de/scripts
path = /samba/logon
read only = No

[sysvol]
path = /var/lib/samba/sysvol
read only = No

[home]
comment = Unix Home
path = /home/users
read only = No
#valid users = %S
#create mask = 0600
#directory mask = 0700
#browseable = No

[Profiles]
comment = Heimatverzeichnis für: %u
path = /samba/profiles
read only = No
#create mask = 0660
#directory mask = 0760
#csc policy = disable

[DATA]
comment = Daten für Win
path = /samba/DATA
read only = No
#create mask = 0666
#directory mask = 0766


[MUSIK]
comment = MP3 DATABASE
path = /home/archiv/MP3
read only = No
create mask = 0666
directory mask = 0766

[DIGIKAM]
comment = Das Bild Archiv
path = /home/archiv/DIGICAM
read only = No
create mask = 0666
directory mask = 0766

[BLASPHEMY]
comment = Ein wenig virtuell

Bug#888353: moc: FTBFS with FFmpeg 4.0

[Elimar Riesebieter]

* James Cowgill  [2018-07-19 18:32 +0100]:

> Hi,
> 
> On 19/07/18 18:05, Elimar Riesebieter wrote:
[...] 
> My patch hasn't been uploaded to unstable yet, so you can ignore those
> logs. It's still in deferred [1,2].
> 
> [1] https://ftp-master.debian.org/deferred.html
> [2] https://ftp-master.debian.org/deferred/
> 
> > I can prepare a tuned patch with upstream over the weekend and upload
> > next week via mentors.debian.net.
> 
> Do you want me to cancel my NMU? Can I just upload it now?

OK, please upload. Nevertheless I'll keep on tuning together with
upstream.

Thanks for contribution!

Elimar
-- 
  Experience is something you don't get until
  just after you need it!


signature.asc
Description: PGP signature

Bug#888353: moc: FTBFS with FFmpeg 4.0

[Elimar Riesebieter]

* James Cowgill  [2018-07-17 11:36 +0100]:

> Control: tags -1 pending
> 
> Hi,
> 
> On Mon, 28 May 2018 20:24:23 +0100 James Cowgill 
> wrote:
> > Control: tags -1 patch
> > 
> > Hi,
> > 
> > On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote:
> > > Source: moc
> > > Version: 1:2.6.0~svn-r2949-2
> > > Severity: important
> > > User: debian-multime...@lists.debian.org
> > > Usertags: ffmpeg-3.5-transition
> > > 
> > > Hi,
> > > 
> > > Your package FTBFS with the upcoming version 3.5 of FFmpeg.
> > 
> > The attached patch fixes this.
> 
> I've uploaded the attached NMU (based on my previously posted patch) to
> DELAYED/5. Please tell me if I should cancel it.

It seems that your patch doesn't build. Check the logs at [0].

[0] https://buildd.debian.org/status/package.php?p=moc=unstable

I can prepare a tuned patch with upstream over the weekend and upload
next week via mentors.debian.net.

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


signature.asc
Description: PGP signature

Bug#892360: core: do not free stack-allocated strings

[Elimar Riesebieter]

Control: tags -1 patch

Hi all,

* Jindřich Makovička  [2018-03-08 19:46 +]:

> There is a fix in upstream master.
> 
> https://github.com/systemd/systemd/pull/8391

I managed to build Debian's 238-1 with the attached patch included.
I hereby confirm that those packages fix this bug.


Elimar
-- 
  The path to source is always uphill!
-unknown-

From 5cbaad2f6795088db56063d20695c6444595822f Mon Sep 17 00:00:00 2001
From: Yu Watanabe 
Date: Thu, 8 Mar 2018 22:21:54 +0900
Subject: [PATCH] core: do not free heap-allocated strings (#8391)

Fixes #8387.
---
 src/core/mount-setup.c | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/core/mount-setup.c b/src/core/mount-setup.c
index 536c17b4d..9c27972af 100644
--- a/src/core/mount-setup.c
+++ b/src/core/mount-setup.c
@@ -248,6 +248,7 @@ int mount_setup_early(void) {
 
 int mount_cgroup_controllers(char ***join_controllers) {
 _cleanup_set_free_free_ Set *controllers = NULL;
+bool has_argument = !!join_controllers;
 int r;
 
 if (!cg_is_legacy_wanted())
@@ -255,7 +256,7 @@ int mount_cgroup_controllers(char ***join_controllers) {
 
 /* Mount all available cgroup controllers that are built into the kernel. */
 
-if (!join_controllers)
+if (!has_argument)
 /* The defaults:
  * mount "cpu" + "cpuacct" together, and "net_cls" + "net_prio".
  *
@@ -300,7 +301,8 @@ int mount_cgroup_controllers(char ***join_controllers) {
 
 t = set_remove(controllers, *i);
 if (!t) {
-free(*i);
+if (has_argument)
+free(*i);
 continue;
 }
 }
-- 
2.16.2



signature.asc
Description: PGP signature

Bug#892360: core: do not free stack-allocated strings

[Elimar Riesebieter]

* Jindřich Makovička  [2018-03-08 19:46 +]:

> There is a fix in upstream master.
> 
> https://github.com/systemd/systemd/pull/8391

Patched Debian sources and tried to build packages:

OK:   239
FAIL:   1
SKIP:  15
TIMEOUT:0
debian/rules:281: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/source/systemd/systemd-238'
debian/rules:294: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned
exit status 2
debuild: fatal error at line 1152:
dpkg-buildpackage -rfakeroot -us -uc -ui -jauto failed
mydebuild auto  4036,66s user 309,41s system 98% cpu 1:13:39,49 tota


Hope Debian mainatiners provide new packages for testing

Thanks for your efforts
Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche

Bug#892360: systemd: No problem on my amd64 systems

[Elimar Riesebieter]

* Diederik de Haas  [2018-03-08 20:29 +0100]:

> Package: systemd
> Followup-For: Bug #892360
> 
> Wanting to let you know that I had no problem on my PC (from which I'm
> reporting) and also not on my laptop.
> 
> I did not have to specify any (systemd related) kernel parameters
> $ cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-4.15.0-1-amd64 
> root=UUID=a2a5e481-0ac6-4e68-818f-38255bf7dd57 ro quiet

Well, I reported the initial reportfor x86 only, though.

Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Elimar Riesebieter]

* Elimar Riesebieter <riese...@lxtec.de> [2018-03-08 19:13 +0100]:

[...]

> ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's
> wait and see

"CONFIG_CGROUP_CPUACCT is not set" gives the same error as shown in
the picture of my initial bug report.

The problem must be triggerd from within systemd.

Elimar
-- 
  355/113: Not the famous irrational number pi,
   but an incredible simulation!
-unknown

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Elimar Riesebieter]

* Eric Valette <eric.vale...@free.fr> [2018-03-08 19:08 +0100]:

> On 3/8/18 7:03 PM, Elimar Riesebieter wrote:
> > * Michael Biebl <bi...@debian.org> [2018-03-08 18:54 +0100]:
> > 
> > [...]
> > > Can you check your custom kernel config, specifically if
> > > CONFIG_CGROUP_CPUACCT=y
> > 
> > I do have CONFIG_CGROUP_CPUACCT=y
> > 
> > Well, but why does 237 works with the very same kernel?
> 
> In my case it is not set, so maybe it is another combined config set ...

I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd
runs fine...

ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's
wait and see

Elimar
-- 
  Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Elimar Riesebieter]

* Michael Biebl  [2018-03-08 18:54 +0100]:

[...] 
> Can you check your custom kernel config, specifically if
> CONFIG_CGROUP_CPUACCT=y

I do have CONFIG_CGROUP_CPUACCT=y

Well, but why does 237 works with the very same kernel?

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Elimar Riesebieter]

* Michael Biebl  [2018-03-08 17:09 +0100]:

> Am 08.03.2018 um 17:05 schrieb Michael Biebl:
> > Control: tags -1 moreinfo
> > 
> > Am 08.03.2018 um 16:23 schrieb valette:
> > 
[...]

> Could you check if
> https://github.com/systemd/systemd/issues/8387
> looks related
> 
> I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem.

Booting with ystemd.unified_cgroup_hierarchy avoids the problem. But
FMPOV this is only a workaround. Maybe
https://github.com/systemd/systemd/pull/8391 should be merged
upstream?

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

Bug#892360: systemd pid 1 freezes at startup on x86 systems

[Elimar Riesebieter]

* Michael Biebl  [2018-03-08 17:05 +0100]:

> Control: tags -1 moreinfo
> 
> Am 08.03.2018 um 16:23 schrieb valette:
> 
> > Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
> 
> Is this also happening with a Debian provided kernel?
> I see both you and Elimar use a custom one.

Didn't test it.

> Is this a virtualized environment or read hardware?
> Do you get a coredump? If so, please attach to this bug report.

No coredump available. This is on real hardware.

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Bug#884973: tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?

[Elimar Riesebieter]

* Evgeni Golov <evg...@debian.org> [2017-12-22 12:34 +0100]:

> control: severity -1 important
> 
> On Fri, Dec 22, 2017 at 10:03:17AM +0100, Elimar Riesebieter wrote:
> > Package: tp-smapi-dkms
> > Version: 0.42-1
> > Severity: serious
> > Justification: fails to build from source
> 
> Nope. 4.15 is not in Debian (not even experimental), so it can't be serious.

4.15 has been arrived in sid..

Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

Bug#884973: tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?

[Elimar Riesebieter]

Package: tp-smapi-dkms
Version: 0.42-1
Severity: serious
Justification: fails to build from source


Dear maintainer,

tp-smapi doesn't build for the upcoming kernels 4.15:

 /var/lib/dkms/tp_smapi/0.42/build/hdaps.c: In function ‘hdaps_init’:¬
  /var/lib/dkms/tp_smapi/0.42/build/hdaps.c:781:2: error: implicit declaration 
of function ‘init_timer’; did you mean ‘init_timers’? [-Werr>
init_timer(_timer);¬
^~¬
init_timers¬
  /var/lib/dkms/tp_smapi/0.42/build/hdaps.c:782:23: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]¬
hdaps_timer.function = hdaps_mousedev_poll;

Thanks
Elimar

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

Kernel: Linux 4.15.0-rc4-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tp-smapi-dkms depends on:
ii  dkms  2.3-3

tp-smapi-dkms recommends no packages.

tp-smapi-dkms suggests no packages.

-- no debconf information

Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

[Elimar Riesebieter]

Control: severity -1 normal
Control: tags -1 +moreinfo

* Ben Elliston  [2017-10-06 08:41 +1100]:

> As a workaround, I have switched to using the IMAP server that runs on
> localhost.

This I don't understand...

Elimar
-- 
  Do you smell something burning or is it me?



signature.asc
Description: PGP signature

Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

[Elimar Riesebieter]

* Ben Elliston <b...@air.net.au> [2017-10-06 08:04 +1100]:

> On Thu, Oct 05, 2017 at 11:00:10PM +0200, Elimar Riesebieter wrote:
> 
> > How does the corruption looks like?
> 
> One partial message in my mbox, then a From line for the start of the
> next message, and the rest of the mbox is OK.

Did you ever tried maildir instead of mbox?

> 
> > Well, is it possible to open your mbox?
> 
> Yes, but not in mutt.

Hmm, but with which?

> > Maybe your filesystem is full? What tells
> > $ df
> 
> 13% in /var/mail.
ok

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


signature.asc
Description: PGP signature

Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

[Elimar Riesebieter]

* Ben Elliston  [2017-10-06 07:36 +1100]:

> Hi Ellmar
> 
> > > mutt is corrupting my mbox when writing back the mbox after deleting 
> > > messages
> > > (and quiting mutt).  I have a partial message in the start of the mbox, 
> > > which
> > > makes mutt unable to read any of the messages in the mbox.
> > 
> > The following predication I don't understand?
> 
> mutt is intermittenly corrupting my mbox when it saves out a modified
> mailbox (ie I have deleted some messages).  It happens seemingly
> randomly.

How does the corruption looks like?
Well, is it possible to open your mbox?
Maybe your filesystem is full? What tells
$ df 

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)


signature.asc
Description: PGP signature

Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

[Elimar Riesebieter]

Hi Ben,

* Ben Elliston  [2017-10-06 06:46 +1100]:

> Package: mutt
> Version: 1.8.3+neomutt20170609-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> mutt is corrupting my mbox when writing back the mbox after deleting messages
> (and quiting mutt).  I have a partial message in the start of the mbox, which
> makes mutt unable to read any of the messages in the mbox.

The following predication I don't understand? 

> This has only just started happening, but that could just be a coincidence.

Could you please describe more precisely what is corrupting your
mbox?

What tells:

$ mutt -D | grep mbox_type

What sort of messages did you deleted?
What is your definition of the "partial message"?

Elimar
-- 
  Do you smell something burning or is it me?

Bug#871247: [Pkg-alsa-devel] Bug#871247: alsa-base: Front Panel Jack for play audio not working

[Elimar Riesebieter]

Control: reassign -1 alsa-utils
Control: severity -1 normal
Control: tags -1 +moreinfo

* Alex B  [2017-08-07 10:35 +0300]:

> Package: alsa-base
> Version: 1.0.27+1
> Severity: serious
> Tags: newcomer
> Justification: Unknown
> 
> Dear Maintainer,
> 
> Sound from back panel is working. Sound from front panel is not working.
> 
> * What led up to the situation?
> Upgrade from debian 8 to 9.1.
> 
> * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> alsactl init
> change in alsamixer

What did you change in alsamixer? What exactly do you mean with
front panel? Are you running a laptop with headphone jacks at the
front or are you running a desktop PC with a front-panel connected
to the mainboard?

Elimar
-- 
  The path to source is always uphill!
-unknown-

Bug#848577: moc: no longer starting

[Elimar Riesebieter]

Control: severity -1 normal


* Reiner Herrmann <rei...@reiner-h.de> [2016-12-18 17:38 +0100]:

> On Sun, Dec 18, 2016 at 05:02:01PM +0100, Elimar Riesebieter wrote:
> > > I even removed the .moc directory, to make sure there is nothing in it
> > > that might be incompatible now, but it didn't help.
> > > I also tried it with and without the moc-ffmpeg-plugin package.
> 
> I have to correct this statement a bit:
> With an empty/removed .moc directory it's starting up again.
> It wasn't working on my first attempt, because I tried it with a
> different user with a different (non-working) asoundrc.
> 
> But with my old config it's not starting. The breaking change seems to
> be a custom AlsaDevice that I have also configured in my .asoundrc.

So it is not moc's fault. I can see in the debug server logs that
there are no mixers or sound devices available. Could be caused by
your .asoundrc.

What custom sound device do you have configured? Does sound work
with other apps like aplay some_file.wav?

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)


signature.asc
Description: PGP signature

Bug#848577: moc: no longer starting

[Elimar Riesebieter]

Control: tags -1 +moreinfo
Control: tags -1 +unreproducible

* Reiner Herrmann  [2016-12-18 15:04 +0100]:

> Source: moc
> Version: 1:2.6.0~svn-r2935-1
> Severity: serious
> 
> Dear maintainer,
> 
> after upgrading moc from 1:2.6.0~svn-r2848-1 to 1:2.6.0~svn-r2935-1, it
> is no longer starting:
> 
> > $ mocp
> > Running the server...
> > Trying JACK...
> > Trying ALSA...
> > Trying OSS...
> > 
> > FATAL_ERROR: No valid sound driver!
> > 
> > 
> > FATAL_ERROR: Server exited!
> 
> I even removed the .moc directory, to make sure there is nothing in it
> that might be incompatible now, but it didn't help.
> I also tried it with and without the moc-ffmpeg-plugin package.
> 
> After downgrading moc to 1:2.6.0~svn-r2848-1, it starts working again.

I can't reproduce. It seems your sound setting are somewhat
confused.

Could you please fire up 2.6.0~svn-r2935-1 like:
$ mocp -D
and send the logfiles mocp_client_log and mocp_server_log compressed
by PM to me?

Thanks
Elimar

-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche


signature.asc
Description: PGP signature

Bug#844501: [Pkg-alsa-devel] Bug#844501: alsa-firmware-loaders: udev rule causes race condition which blocks us-122 initialisation (with fix!)

[Elimar Riesebieter]

Control: severity -1 normal

The package isn't unusable for always most users.

* Jaime T  [2016-11-16 13:34 +]:

> On 16 November 2016 at 10:50, jaimet  wrote:
> > My udev-fu is very weak, but after stumbling around with "udevadm
> > monitor" for a bit, I replaced that udev rule line with:
> >
> > SUBSYSTEM=="sound", ACTION=="add", KERNEL=="hwC2D0", 
> > RUN+="/lib/udev/tascam_fpga"
> 
> It now appears that my udev-fu is even weaker than I thought: "hwC2D0"
> is obviously an "arbitrary-card-ordering-dependent" reference which
> breaks if my sound cards are discovered in a different order. A much
> better alternative (that is *not* order-dependent) is:
> 
> SUBSYSTEM=="sound", ACTION=="add", ATTR{id}=="USX2Y",
> RUN+="/lib/udev/tascam_fpga"
> 
> Apologies for the noise. J :-)

So should we close this bug?

Elimar
-- 
  Experience is something you don't get until
  just after you need it!

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

[Elimar Riesebieter]

* 積丹尼 Dan Jacobson  [2016-11-06 06:11 +0800]:

> severity 843251 grave
> thanks
> Yes i386.
> And you know what?
> the user cannot ever boot his computer ever again, even from grub
> menus' "(recovery mode)".
> 
> ER> I can confirm this behaviour. Be care to reboot:
> ER> If booting with systemd you will be pulled in maintenance mode.
> 
> No you (I) will never get a prompt again, all one sees

Yes, I got it.

[...]
> Please tell me how to fix my computer to boot now. I am using a
> different one to write this message.

Read #843160
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843160

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)

Bug#837590: [Pkg-alsa-devel] Bug#837590: Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

[Elimar Riesebieter]

Control: tags -1 + fixed pending

* Elimar Riesebieter <riese...@lxtec.de> [2016-09-12 18:57 +0200]:

> Control: forwarded -1 
> http://mailman.alsa-project.org/pipermail/alsa-devel/2016-September/112697.html
> 
> * Helmut Grohne <hel...@subdivi.de> [2016-09-12 18:23 +0200]:
> 
> > Source: alsa-tools
> > Version: 1.1.0-1
> > Severity: serious
> > 
> > I noticed that alsa-tools fails to cross build from source for armel due
> > to gcc-6 narrowing conversion issues. Issues about narrowing conversions
> > are generally not cross compilation specific and reproducible natively.
> > Thus filing at RC severity. A full (cross) build log is attached. The
> > relevant excerpt is:
> > 
> > | arm-linux-gnueabi-g++ -DPACKAGE_NAME=\"hdspmixer\" 
> > -DPACKAGE_TARNAME=\"hdspmixer\" -DPACKAGE_VERSION=\"1.11\" 
> > -DPACKAGE_STRING=\"hdspmixer\ 1.11\" -DPACKAGE_BUGREPORT=\"\" 
> > -DPACKAGE_URL=\"\" -DPACKAGE=\"hdspmixer\" -DVERSION=\"1.11\" 
> > -DSTDC_HEADERS=1 -DHAVE_LIBASOUND=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  
> > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> > -Wformat -Werror=format-security   -I/usr/include/freetype2   
> > -D_THREAD_SAFE -D_REENTRANT -fno-exceptions -MT channelmap.o -MD -MP -MF 
> > .deps/channelmap.Tpo -c -o channelmap.o channelmap.cxx
> > | channelmap.cxx:59:1: error: narrowing conversion of '-1' from 'int' to 
> > 'char' inside { } [-Wnarrowing]
> > |  };
> > |  ^
> > 
> > Helmut
> 
> 
> > ___
> > Pkg-alsa-devel mailing list
> > pkg-alsa-de...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel
> 
> 
> -- 
>   Learned men are the cisterns of knowledge,
>   not the fountainheads ;-)
> 
> ___
> Pkg-alsa-devel mailing list
> pkg-alsa-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel
> 

-- 
  Do you smell something burning or is it me?

Bug#837590: [Pkg-alsa-devel] Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

[Elimar Riesebieter]

Control: forwarded -1 
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-September/112697.html

* Helmut Grohne  [2016-09-12 18:23 +0200]:

> Source: alsa-tools
> Version: 1.1.0-1
> Severity: serious
> 
> I noticed that alsa-tools fails to cross build from source for armel due
> to gcc-6 narrowing conversion issues. Issues about narrowing conversions
> are generally not cross compilation specific and reproducible natively.
> Thus filing at RC severity. A full (cross) build log is attached. The
> relevant excerpt is:
> 
> | arm-linux-gnueabi-g++ -DPACKAGE_NAME=\"hdspmixer\" 
> -DPACKAGE_TARNAME=\"hdspmixer\" -DPACKAGE_VERSION=\"1.11\" 
> -DPACKAGE_STRING=\"hdspmixer\ 1.11\" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"hdspmixer\" -DVERSION=\"1.11\" 
> -DSTDC_HEADERS=1 -DHAVE_LIBASOUND=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security   -I/usr/include/freetype2   -D_THREAD_SAFE 
> -D_REENTRANT -fno-exceptions -MT channelmap.o -MD -MP -MF 
> .deps/channelmap.Tpo -c -o channelmap.o channelmap.cxx
> | channelmap.cxx:59:1: error: narrowing conversion of '-1' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> |  };
> |  ^
> 
> Helmut


> ___
> Pkg-alsa-devel mailing list
> pkg-alsa-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel


-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

Bug#833950: [alsa-devel] locking looks odd

[Elimar Riesebieter]

* Samuel Thibault <sthiba...@debian.org> [2016-08-22 19:52 +0200]:

> Elimar Riesebieter, on Mon 22 Aug 2016 19:33:26 +0200, wrote:
> >  If that dosn't come tto mind we either
> >  have to disable pthread (we can't forsee what breaks then)
> 
> Disabling pthread just drops the mutexes, without putting back the old
> locking code...

Let's wait 2 more weeks and hope of a solid solution from
alsa-devel. I try to discuss this with Jordi (MIA at the moment) and
Luke within this bug, so cc'ed.

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)


signature.asc
Description: PGP signature

Bug#833950: [alsa-devel] locking looks odd

[Elimar Riesebieter]

* Samuel Thibault  [2016-08-20 14:12 +0200]:

> Jaroslav Kysela, on Wed 17 Aug 2016 19:46:42 +0200, wrote:
> > Dne 16.8.2016 v 23:03 Samuel Thibault napsal(a):
> > > - snd_pcm_new seems to initialize pcm->thread_safe to 0 by default, this
> > >   does not seem safe. The attached patch initializes it to 1, which
> > >   fixes the bug in our tests.
> > > 
> > > - snd_pcm_hw_open_fd forces it to 1, thus ignoring what snd_pcm_new set.
> > 
> > The thread_safe has this meaning:
> > 
> > 0  - the pcm plugin is not thread safe
> > 1  - the pcm plugin is thread safe (actually only the hw plugin)
> > -1 - disable thread safety
> 
> So now with rethinking all of this, I'm starting to understand: from
> reading the variable name, I would have thought "thread_safe=1" means
> "I want thread safety thanks to a mutex", while apparently it means
> "the plugin is already thread-safe, there is no need for a mutex"...
> Really, all of this should be documented clearly along the source code,
> otherwise people will get it wrong.
> 
> I'd just like to check something: do we agree that libasound must be
> thread-safe by default (otherwise it breaks the application assumption
> that it's thread-safe)?  If so, then there are thread-safety bugs: the
> mentioned Debian report is far from alone, the upgrade to the newer
> libasound has severely broken quite a few applications, I'm at the point
> of advising the Debian maintainer to just revert to the previous version
> for Stretch, otherwize we'll be shipping just very-buggy software.

 suppose that we should wait for a response of the maintainer
 Takashi Sakamoto mentioned. If that dosn't come tto mind we either
 have to disable pthread (we can't forsee what breaks then) or really
 downgrade to 1.1.1.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


signature.asc
Description: PGP signature

Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Elimar Riesebieter]

* Sebastian Humenda <shume...@gmx.de> [2016-08-17 07:59 +0200]:

> Hi,
> 
> Elimar Riesebieter schrieb am 11.08.2016, 19:40 +0200:
> >* Sebastian Humenda <shume...@gmx.de> [2016-08-10 20:30 +0200]:
> >
> >> Package: libasound2
> >> Version: 1.1.2
> >> Severity: serious
> >> Tags: patch
> >> Justification: breaks system for blind users [RC, stretch]
> >> 
> >> After an upgrade to the specified version, BRLTTY starts up with speech 
> >> working
> >> (brltty-espeak is using libao -> libasoun2), but speech stops working after
> >> roughly a minute. The BRLTTY process is still running, but speech cannot be
> >> brought back, only a restart of BRLTTY fixes this issue. All other 
> >> playback of
> >> sound using ALSA works fine. Since it is not related to any changes in 
> >> BRLTTY
> >> (tried several stable versions), the issue must be in libasound2. The 
> >> provided
> >> patch fixes the issue reliably for me.
> >
> >Thanks for the patch.
> The patch seems to introduce another issue. Aplay does not terminate after
> playback and keeps the handle to the file open as well. I use aplay for
> notifications on my system, so ended up with no free file descriptors after a
> while. This behaviour is not present in the unpatched version.
> Please let me know if there is anything else I can do.

So I cancelled the upload. I think we have to wait for a response
from alsa-devel to Samuels post there.

http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/111836.html

Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Elimar Riesebieter]

* Samuel Thibault <sthiba...@debian.org> [2016-08-16 23:03 +0200]:

> Elimar Riesebieter, on Sat 13 Aug 2016 15:17:19 +0200, wrote:
> > > Luke Yelavich, on Fri 12 Aug 2016 08:04:56 +1000, wrote:
> > [...]
> > > > Has anybody sent this upstream?
> > > 
> > > I have sent a mail to alsa-devel but it doesn't seem to have been
> > > moderated yet.
> > 
> > Hmm, can't find the thread/initial [0]?
> > 
> > [0] 
> > http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/thread.html
> 
> It seems moderators are not reactive. I have subscribed to the list in
> order to be able to post without moderation.

Now I see [1]. Many thanks for contribution ;-)

[1] http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/111836.html

Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

Bug#834298: nis: Can't ypbind

[Elimar Riesebieter]

control reopen +1

* Mark Brown <broo...@debian.org> [2016-08-16 12:11 +0100]:

> On Sun, Aug 14, 2016 at 12:02:06PM +0200, Elimar Riesebieter wrote:
> 
> > since 3.17-35 I can't bind to my nisserver anymore. Downgrading to
> > 3.17-34 succeeded. Please notice:
> 
> This appears to be some change that's systemd related, AFAICT it works
> fine outside of systemd but gets killed when running inside systemd.
> I'm assuming that the dbus integration was causing systemd to notice
> that it was still running.

My server is a sysvinit system. Can't bind from either a sysvinit
Desktop nor a systemd Desktop the sysvinit server. Nevertheless why
don't we update to ypbind-mt-1.38?

Elimar

-- 
  The path to source is always uphill!
-unknown-

Bug#834298: nis: Can't ypbind

[Elimar Riesebieter]

Package: nis
Version: 3.17-35
Severity: grave
Justification: renders package unusable


Hi,

since 3.17-35 I can't bind to my nisserver anymore. Downgrading to
3.17-34 succeeded. Please notice:

3.17-35:
# ldd $(which ypbind)
linux-vdso.so.1 (0x7ffdb879f000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f8380e26000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7f8380c0e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f838086c000)
/lib64/ld-linux-x86-64.so.2 (0x56204e973000)

3.17-34:
# ldd $(which ypbind)
 linux-vdso.so.1 (0x7ffe2a7f6000)
libslp.so.1 => /usr/lib/x86_64-linux-gnu/libslp.so.1 
(0x7f71748d1000)
libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 
(0x7f71746aa000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7f717445a000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7f7174207000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f7173ef6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f7173cd8000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7f7173ac)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f717371f000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7f7173396000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f717330e000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7f7173105000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f7172e92000)
/lib64/ld-linux-x86-64.so.2 (0x556d37459000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7f7172c8e000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f7172a73000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7f717284b000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f7172634000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f717242c000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f7172208000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f7171ef9000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f7171cf5000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f7171ae)

I tried ypbind-mt-1.38 as well which binds just fine, though.

-- 
   Elimar

-- Package-specific info:

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

Kernel: Linux 4.7.0-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT)
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)

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  hostname   3.18
ii  libc6  2.23-4
ii  libdbus-1-31.10.8-1
ii  libdbus-glib-1-2   0.106-1
ii  libgdbm3   1.8.3-14
ii  libglib2.0-0   2.48.1-2
ii  libslp11.2.1-11
ii  lsb-base   9.20160629
ii  make-guile [make]  4.1-9
ii  netbase5.3
ii  rpcbind [portmap]  0.2.3-0.5

nis recommends no packages.

Versions of packages nis suggests:
pn  nscd  

Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Elimar Riesebieter]

* Samuel Thibault  [2016-08-12 00:18 +0200]:

> Luke Yelavich, on Fri 12 Aug 2016 08:04:56 +1000, wrote:
[...]
> > Has anybody sent this upstream?
> 
> I have sent a mail to alsa-devel but it doesn't seem to have been
> moderated yet.

Hmm, can't find the thread/initial [0]?

[0] http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/thread.html

Elimar
-- 
  The path to source is always uphill!
-unknown-

Bug#825379: cairo-dock-weather-plug-in: weather.com changed API

[Elimar Riesebieter]

Ping?

* Elimar Riesebieter <riese...@lxtec.de> [2016-05-26 15:37 +0200]:

> * Elimar Riesebieter <riese...@lxtec.de> [2016-05-26 15:24 +0200]:
> 
> > Package: cairo-dock-weather-plug-in
> > Version: 3.4.0-1.5lxtec1
> > Severity: grave
> > Tags: patch
> > Justification: renders package unusable
> > 
> > weather.com changed the API. Attached patch fixed it.
> 
> Wrong patch. Use the now attached one
> 
> -- 
>Elimar

> From: Elimar Riesebieter <riese...@lxtec.de>
> Date: Thu, 26 May 2016 14:39:44 +0200
> Subject: Corrected CD_WEATHER_BASE_URL
> 
> 
> diff -Naurd a/weather/src/applet-config.c b/weather/src/applet-config.c
> --- a/weather/src/applet-config.c 2014-08-18 01:10:45.0 +0200
> +++ b/weather/src/applet-config.c 2016-05-26 14:37:35.099729076 +0200
> @@ -174,7 +174,7 @@
>   gldi_task_discard (myData.pGetLocationTask);
>   myData.pGetLocationTask = NULL;
>  }
> -#define CD_WEATHER_BASE_URL "http://xml.weather.com;
> +#define CD_WEATHER_BASE_URL "http://wxdata.weather.com/wxdata;
>  static void _cd_weather_search_for_location (GtkEntry *pEntry, 
> GldiModuleInstance *myApplet)
>  {
>   const gchar *cLocationName = gtk_entry_get_text (pEntry);
> diff -Naurd a/weather/src/applet-read-data.c b/weather/src/applet-read-data.c
> --- a/weather/src/applet-read-data.c  2014-08-18 01:10:45.0 +0200
> +++ b/weather/src/applet-read-data.c  2016-05-26 14:37:22.041744777 +0200
> @@ -30,7 +30,7 @@
>  #include "applet-load-icons.h"
>  #include "applet-read-data.h"
>  
> -#define CD_WEATHER_BASE_URL "http://xml.weather.com;
> +#define CD_WEATHER_BASE_URL "http://wxdata.weather.com/wxdata;
>  
>  
>  static xmlDocPtr _cd_weather_open_xml_buffer (const gchar *cData, xmlNodePtr 
> *root_node, const gchar *cRootNodeName, GError **erreur)




-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse

[Elimar Riesebieter]

Control: reassign -1 libasound2-plugins
Control: severity -1 minor

* Lev Livnev  [2016-06-18 23:45 +0100]:

> Package: libasound2
> Version: 1.1.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> 
> After the update to libasound2 version 1.1.1-1 from 1.1.0-1, it is no longer
> possible to control audio, the below command, which should adjust the audio
> levels, fails with the following error:
> 
> ~/ amixer -D pulse sset Master 5%+
> ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse
> amixer: Mixer attach pulse error: No such file or directory

Since libasound2-plugins 1.1.1 we don't install 50-pulseaudio.conf
anymore. So the device pulse isn't available anymore by Debian's
default config. See also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739329.

$ amixer sset Master 5%+
should adjust the default advice as wanted.

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse

[Elimar Riesebieter]

* Lev Livnev  [2016-06-19 09:36 +]:

> Elimar, thank you for your help:
> 
> I am unable to adjust the sound, so I felt like the package is unusable in
> my configuration. Here are the outputs:
> 
> $ dpkg -l | egrep '(alsa|libasound)'

[...]
Output looks fine.

> $ aplay -l
>  List of PLAYBACK Hardware Devices 
> card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: PCH [HDA Intel PCH], device 0: ALC3263 Analog [ALC3263 Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0

So your default card is HDMI device 3 or do you want to run the
analog output (card 1)?

> # alsactl init
> [sudo] password for lev:
> alsactl: sysfs_init:48: sysfs path '/sys' is invalid
> 
> Found hardware: "HDA-Intel" "Intel Broadwell HDMI"
> "HDA:80862808,80860101,0010" "0x1028" "0x0665"
> Hardware is initialized using a generic method

Your soundcard is recognized and should work if configured
correctly.

Elimar
-- 
  355/113: Not the famous irrational number pi,
   but an incredible simulation!
-unknown

Bug#827636: [Pkg-alsa-devel] Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse

[Elimar Riesebieter]

* Lev Livnev  [2016-06-18 23:45 +0100]:

> Package: libasound2
> Version: 1.1.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> 
> After the update to libasound2 version 1.1.1-1 from 1.1.0-1, it is no longer
> possible to control audio, the below command, which should adjust the audio
> levels, fails with the following error:
> 
> ~/ amixer -D pulse sset Master 5%+
> ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse
> amixer: Mixer attach pulse error: No such file or directory
> 
> I can't be sure if this is related to the package libasound2,
> libasound2-plugins, or alsa-utils, or even something else, so please 
> reclassify
> if necessary.

But you're sure to set severity to grave?

Is sound working? Anyway, what tells:

$ dpkg -l | egrep '(alsa|libasound)'

$ aplay -l

# alsactl init

# alsactl restore

Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

Bug#812371: rpcbind: Regression: must restart rpc bind to run ypbind (nis)

[Elimar Riesebieter]

* Michael Biebl <bi...@debian.org> [2016-05-25 20:24 +0200]:

> Hi
> 
> On Sun, 15 Nov 2015 13:56:50 +0100 Elimar Riesebieter
> <riese...@lxtec.de> wrote:
> > Package: rpcbind
> > Version: 0.2.3-0.2
> > Severity: important
> > 
> > Can't run nis:
> > # ypbind -no-dbus -broadcast -debug
> > 1679: add_server() domain: mynisdomain, broadcast
> > 1679: [Welcome to ypbind-mt, version 1.20.1]
> > 1679: ping interval is 20 seconds
> > Cannot register service: RPC: Unable to receive; errno = Connection refused
> > 1679: Unable to register (YPBINDPROG, YPBINDVERS, udp).
> > 
> > Restarting rpc bind gets me back to restart nis successfull.
> > 
> > # service rpcbind restart
> > # service nis restart
> > 
> > Reverting to rpcbind 0.2.1-6.1 solves the problem. Please notice
> > that this happens only on systemd machines. Running sysvinit doesn't
> > show this behaviour.
> 
> Maybe the rpcbind.socket is simply not up yet.
> Elimar et al, could you try the change from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812371#31

This fixed my problem. ypbind is up running with rpcbind 0.2.3-0.2.

Elimar
-- 
  The path to source is always uphill!
-unknown-

Bug#825379: cairo-dock-weather-plug-in: weather.com changed API

[Elimar Riesebieter]

* Elimar Riesebieter <riese...@lxtec.de> [2016-05-26 15:24 +0200]:

> Package: cairo-dock-weather-plug-in
> Version: 3.4.0-1.5lxtec1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
> 
> weather.com changed the API. Attached patch fixed it.

Wrong patch. Use the now attached one

-- 
   Elimar
From: Elimar Riesebieter <riese...@lxtec.de>
Date: Thu, 26 May 2016 14:39:44 +0200
Subject: Corrected CD_WEATHER_BASE_URL


diff -Naurd a/weather/src/applet-config.c b/weather/src/applet-config.c
--- a/weather/src/applet-config.c	2014-08-18 01:10:45.0 +0200
+++ b/weather/src/applet-config.c	2016-05-26 14:37:35.099729076 +0200
@@ -174,7 +174,7 @@
 	gldi_task_discard (myData.pGetLocationTask);
 	myData.pGetLocationTask = NULL;
 }
-#define CD_WEATHER_BASE_URL "http://xml.weather.com;
+#define CD_WEATHER_BASE_URL "http://wxdata.weather.com/wxdata;
 static void _cd_weather_search_for_location (GtkEntry *pEntry, GldiModuleInstance *myApplet)
 {
 	const gchar *cLocationName = gtk_entry_get_text (pEntry);
diff -Naurd a/weather/src/applet-read-data.c b/weather/src/applet-read-data.c
--- a/weather/src/applet-read-data.c	2014-08-18 01:10:45.0 +0200
+++ b/weather/src/applet-read-data.c	2016-05-26 14:37:22.041744777 +0200
@@ -30,7 +30,7 @@
 #include "applet-load-icons.h"
 #include "applet-read-data.h"
 
-#define CD_WEATHER_BASE_URL "http://xml.weather.com;
+#define CD_WEATHER_BASE_URL "http://wxdata.weather.com/wxdata;
 
 
 static xmlDocPtr _cd_weather_open_xml_buffer (const gchar *cData, xmlNodePtr *root_node, const gchar *cRootNodeName, GError **erreur)


signature.asc
Description: PGP signature

Bug#825379: cairo-dock-weather-plug-in: weather.com changed API

[Elimar Riesebieter]

Package: cairo-dock-weather-plug-in
Version: 3.4.0-1.5lxtec1
Severity: grave
Tags: patch
Justification: renders package unusable

weather.com changed the API. Attached patch fixed it.

-- 
   Elimar
--- weather/src/applet-config.c.orig2016-05-16 20:41:00.989532095 -0400
+++ weather/src/applet-config.c2016-05-16 20:41:05.890473638 -0400
@@ -174,7 +174,7 @@
gldi_task_discard (myData.pGetLocationTask);
myData.pGetLocationTask = NULL;
}
-#define CD_WEATHER_BASE_URL "http://xml.weather.com;
+#define CD_WEATHER_BASE_URL "http://wxdata.weather.com/wxdata;
static void _cd_weather_search_for_location (GtkEntry *pEntry, GldiModuleInstance *myApplet)
{
const gchar *cLocationName = gtk_entry_get_text (pEntry);
--- weather/src/applet-read-data.c.orig2016-05-16 20:39:06.222916780 -0400
+++ weather/src/applet-read-data.c2016-05-16 20:39:40.641497521 -0400
@@ -30,7 +30,7 @@
#include "applet-load-icons.h"
#include "applet-read-data.h"

-#define CD_WEATHER_BASE_URL "http://xml.weather.com;
+#define CD_WEATHER_BASE_URL "http://wxdata.weather.com/wxdata;


static xmlDocPtr _cd_weather_open_xml_buffer (const gchar *cData, xmlNodePtr *root_node, const gchar *cRootNodeName, GError **erreur)

Bug#812668: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Elimar Riesebieter]

Hi Andreas,

* Andreas Bauer <baue...@gmail.com> [2016-03-25 19:20 +0100]:

> Hi Elimar,
> 
> thanks again for letting me know about this issue and building the
> patch.  I too have tested the latest patch for a few weeks and just
> made a release of it, as it seems to do the trick:
> 
>   https://sourceforge.net/projects/mailfilter/files/Mailfilter/0.8.4/
> 
> I hope that as such, this package can remain in Debian.  Would be much
> obliged to get a quick confirmation of this, or further instructions
> on how I may be able to help in this regard.

mailfilter 0.8.4.1-1 has entered Debian unstable today. Our package
checker "lintian" found some spell errors which I patched into the
package. Please find the patches attached.

Thanks for your contribution
Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
     Friedrich Nietzsche
Author: Elimar Riesebieter <riese...@lxtec.de>
Subject: Fix spellerror in mailfilterex.5 
Forwarded: yes
Last-Update: 2016-03-28

diff -Naurd a/man/mailfilterex.5 b/man/mailfilterex.5
--- a/man/mailfilterex.5	2014-05-11 17:24:35.0 +0200
+++ b/man/mailfilterex.5	2016-03-28 13:42:18.030238819 +0200
@@ -214,7 +214,7 @@
 errors and the like.  Examples in this man page all use extended type.
 .SH "NOTES"
 If you are new to Regular Expressions and new to Mailfilter, you might want to
-experiment a bit, before you accidently delete messages for real. For such
+experiment a bit, before you accidentally delete messages for real. For such
 cases Mailfilter provides two keywords. TEST can be used to only simulate the
 deletion of messages and SHOW_HEADERS stores all the e-mail headers that get
 examined by the program.
Author: Elimar Riesebieter <riese...@lxtec.de>
Subject: Fix spellerror for occured in several files
Forwarded: yes
Last-Update: 2016-03-28

diff -Naurd a/src/header.cc b/src/header.cc
--- a/src/header.cc	2014-05-11 17:16:44.0 +0200
+++ b/src/header.cc	2016-03-28 13:57:57.307154131 +0200
@@ -130,7 +130,7 @@
 	}
   catch (const exception& r_err)
 	{
-	  ERROR_MSG("Runtime exception occured while parsing rcfile: "
+	  ERROR_MSG("Runtime exception occurred while parsing rcfile: "
 		+ (string)r_err.what ());
 	  exit (-1);
 	}
diff -Naurd a/src/mailfilter.cc b/src/mailfilter.cc
--- a/src/mailfilter.cc	2014-05-11 17:16:44.0 +0200
+++ b/src/mailfilter.cc	2016-03-28 13:57:12.452489891 +0200
@@ -111,7 +111,7 @@
 }
   catch (const exception& r_err)
 {
-  ERROR_MSG("Runtime exception occured: "
+  ERROR_MSG("Runtime exception occurred: "
 		+ (string)r_err.what ());
   return -1;
 }
@@ -183,7 +183,7 @@
 }
   catch (const exception& r_err)
 {
-  logger->print_err ("Runtime exception occured: "
+  logger->print_err ("Runtime exception occurred: "
 			+ (string)r_err.what ());
   return -1;
 }
diff -Naurd a/src/pop3.cc b/src/pop3.cc
--- a/src/pop3.cc	2016-02-29 15:45:10.0 +0100
+++ b/src/pop3.cc	2016-03-28 13:58:44.585691415 +0200
@@ -61,14 +61,14 @@
   // Send user name and read server reply.
   if (conn->c_write (usr_name.c_str ()) == -1 || !REPLY_OK)
 {
-  logger->print_err("Error occured while sending username to server.");
+  logger->print_err("Error occurred while sending username to server.");
   return false;
 }
 
   // Send password and read server reply.
   if (conn->c_write (pass_wd.c_str ()) == -1 || !REPLY_OK)
 {
-  logger->print_err("Error occured while sending password to server.");
+  logger->print_err("Error occurred while sending password to server.");
   return false;
 }
 
@@ -97,7 +97,7 @@
 // The function scans the headers inside a POP3 account for spam.  It
 // will delete all spam messages in the account and return 0 when all
 // the hard work is done.  A negative integer is returned if an error
-// occured.
+// occurred.
 
 int POP3 :: scan (void) const
 {
@@ -111,7 +111,7 @@
   // Determine number of messages waiting to be examined.
   if ((num_messages = status ()) < 0)
 {
-  logger->print_err ("Error occured while sending STAT to server.");
+  logger->print_err ("Error occurred while sending STAT to server.");
   return GEN_FAILURE_FLAG;
 }
   
@@ -130,7 +130,7 @@
 	  cmd = "LIST " + msg_no.str () + "\r\n";
 	  if (conn->c_write (cmd.c_str ()) == -1 || !REPLY_OK)
 	{
-	  logger->print_err ("Error occured while sending LIST to server.");
+	  logger->print_err ("Error occurred while sending LIST to server.");
 	  return GEN_FAILURE_FLAG;
 	}
 	  
@@ -143,7 +143,7 @@
 	  cmd = "TOP " + msg_no.str () + " 0\r\n";
 	  if (conn->c_write (cmd.c_str ()) == -1 || !HEADER_OK)
 	{
-	  log

Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Elimar Riesebieter]

Hi gents,

* Andreas Bauer <baue...@gmail.com> [2016-03-25 19:20 +0100]:

> Hi Elimar,
> 
> thanks again for letting me know about this issue and building the
> patch.  I too have tested the latest patch for a few weeks and just
> made a release of it, as it seems to do the trick:
> 
>   https://sourceforge.net/projects/mailfilter/files/Mailfilter/0.8.4/
> 
> I hope that as such, this package can remain in Debian.  Would be much
> obliged to get a quick confirmation of this, or further instructions
> on how I may be able to help in this regard.

I've prepared a lintian cleaned package. You can find it here:
http://mentors.debian.net/package/mailfilter

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

dget -x 
http://mentors.debian.net/debian/pool/main/m/mailfilter/mailfilter_0.8.4-1.dsc

Changelog:
[ Elimar Riesebieter ]
* New upstream version  Fixes a FTBS (Closes: 812668)
* Fixed some spellerrors via spellfixpatches.
* debian/rules:
  - Introduced DEB_BUILD_MAINT_OPTIONS = hardening=+all
  - Build contrib.tar.gz without timestamp
* debian/control:
  - Added Homepage field
  - Changed Standards-Version to 3.9.7. No changes needed.
  - Add myself to uploaders
* debian/copyright:
  - Changed to dep5-copyright
* Added 'set -e' stanza to maintainer scripts


Thanks in advance
Elimar
-- 
  The path to source is always uphill!
-unknown-


signature.asc
Description: PGP signature

Bug#812668: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Elimar Riesebieter]

* Andreas Bauer  [2016-03-25 19:20 +0100]:

> Hi Elimar,
> 
> thanks again for letting me know about this issue and building the
> patch.  I too have tested the latest patch for a few weeks and just
> made a release of it, as it seems to do the trick:
> 
>   https://sourceforge.net/projects/mailfilter/files/Mailfilter/0.8.4/
> 
> I hope that as such, this package can remain in Debian.  Would be much
> obliged to get a quick confirmation of this, or further instructions
> on how I may be able to help in this regard.

Would one of the uploaders please update mailfilter to 0.8.4?

Thanks
Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)


signature.asc
Description: PGP signature

Bug#812668: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Elimar Riesebieter]

Control: tags -1 patch

* Andreas Bauer <baue...@gmail.com> [2016-02-29 16:52 +0100]:

> Hi Elimar, Michael,
> 
> just letting you know that in SVN is a release candidate of 0.8.4 of
> mailfilter, which hopefully fixes the issue.  It's a bit ugly, hence I
> want to keep testing it for a while, before I release - say, 1 or 2
> weeks.
> 
> Hope it will still be able to keep the package in Debian this way.  If
> either of you is curious, you could grab it from SVN and rebuild, etc.
> 
>   https://sourceforge.net/p/mailfilter/code/HEAD/tree/

I have cherry picked the respective patch and can confirm that
mailfilter builds fine on i386, ppc32 and amd64. I've build my own
package with the patch attached for testing.

Thanks Andreas for contribution ;-)

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)
Author: Andreas Bauer <baue...@gmail.com, Elimar Riesebieter <riese...@lxtec.de>
Subject: Fix compilation issues stemming from flex >= 2.6.0, which no longer
 uses pointers for yyin, but references it seems.
Last-Update: 2016-03-02
Index: mailfilter-0.8.3/ChangeLog
===
--- mailfilter-0.8.3.orig/ChangeLog
+++ mailfilter-0.8.3/ChangeLog
@@ -1,6 +1,13 @@
 Mailfilter ChangeLog
 -=-=-=-=-=-=-=-=-=-=
 
+Mon Feb 29 16:44:08 CET 2016 baueran
+
+- src/rcfile.ll: yyin is now a reference. So use different ifstream
+ pointer and pass it on.
+- src/pop3.cc: FlexLexer::switch_stream no longer has 2nd argument
+   optional, it seems.  So pass NULL as second object.
+
 Sat May 17 19:21:57 CEST 2014 baueran
 
  src/preferences.cc:
Index: mailfilter-0.8.3/configure.ac
===
--- mailfilter-0.8.3.orig/configure.ac
+++ mailfilter-0.8.3/configure.ac
@@ -26,7 +26,7 @@
 # Process this file with autoconf to produce a configure script.
 
 AC_PREREQ(2.54)
-AC_INIT(mailfilter, 0.8.3, [baue...@gmail.com])
+AC_INIT(mailfilter, 0.8.4, [baue...@gmail.com])
 AC_REVISION($Revision: 1.1.2.4.2.12 $)
 AC_SUBST(PACKAGE_COPYRIGHT)
 AC_DEFINE(PACKAGE_COPYRIGHT,
Index: mailfilter-0.8.3/NEWS
===
--- mailfilter-0.8.3.orig/NEWS
+++ mailfilter-0.8.3/NEWS
@@ -1,6 +1,13 @@
 Mailfilter NEWS (Summary)
 -=-=-=-=-=-=-=-=-=-=-=-=-
 
+mailfilter 0.8.4 (under development)
+
+  - Fix compilation issues stemming from flex >= 2.6.0, which no
+longer uses pointers for yyin, but references it seems.
+
+  - Minor other code fixes that relate to the above.
+
 mailfilter 0.8.3 (Sat May 17 19:37:27 CEST 2014)
 
   - (Hopefully) fixed Debian Bug #716522: mailfilter crashes
Index: mailfilter-0.8.3/src/pop3.cc
===
--- mailfilter-0.8.3.orig/src/pop3.cc
+++ mailfilter-0.8.3/src/pop3.cc
@@ -204,7 +204,7 @@ int POP3 :: invoke_msg_parser (const str
 	  stringstream cur_header;
 	  cur_header << *header;
 	  rfclexer = new rfcFlexLexer;
-	  rfclexer->switch_streams (_header);
+	  rfclexer->switch_streams (_header, NULL);
 	  int error = rfcparse ((void*) msg_header);
 	  delete rfclexer;
 	  return error;
Index: mailfilter-0.8.3/src/rcfile.ll
===
--- mailfilter-0.8.3.orig/src/rcfile.ll
+++ mailfilter-0.8.3/src/rcfile.ll
@@ -146,17 +146,21 @@ CTRL_CHAR	.
 	   cerr << yytext << "' could not be found." << endl;
 	   exit (-1);
 }
+
+	// yyin is now a std::istream& it seems. So the following no longer works:
+	// yyin = new ifstream (sub_file.c_str ());
+	std::ifstream* infile = new ifstream (sub_file.c_str ());
 
-yyin = new ifstream (sub_file.c_str ());
-
-if (!((ifstream*) yyin)->is_open ())
+	// if (!((std::ifstream*) yyin)->is_open ())
+if (!infile->is_open ())
 {
cerr << PACKAGE_NAME << ": Error: Nested rcfile '";
 	   cerr << sub_file << "' could not be opened." << endl;
 	   exit (-1);
 }
 
-yy_switch_to_buffer (yy_create_buffer (yyin, YY_BUF_SIZE));
+yy_switch_to_buffer (yy_create_buffer (infile, YY_BUF_SIZE));
+	// yy_switch_to_buffer (yy_create_buffer (yyin, YY_BUF_SIZE));
  }
  catch (...)
  {


signature.asc
Description: PGP signature

Bug#812668: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Elimar Riesebieter]

* Michael Tautschnig <m...@debian.org> [2016-02-08 09:02 +]:

> Hi Andreas, Elimar,
> 
> A bit more info on the bug report: this is likely caused by the upgrade to 
> flex
> 2.6. Re-generating the lexer may do the trick, see also
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812681

find . -name '*.ll' | sed -e 's/[.]ll$/.cc/' | xargs rm -rf

doesn't help either. If we want the package in Debian we need to fix
this bug. mailfilter will be removed from testing soon.
 
> On Wed, Feb 03, 2016 at 21:18:31 +0100, Andreas Bauer wrote:
> > Hi Elimar,
> > 
> > will def. look at it.  Thanks for pointing this out!
> > 
> > @Michael, long time no see!  :-)
> > 
> > Cheers,
> > 
> > Andreas.
> > 
> > 
> > On Wed, Feb 03, 2016 at 08:54:34PM +0100, Elimar Riesebieter wrote:
> > > Hi Andreas,
> > > 
> > > could you please investigate?
> > > 
> > > Thanks
> > > Elimar


-- 
  The path to source is always uphill!
-unknown-

Bug#813479: [Pkg-alsa-devel] Bug#813473: alsa-utils: Upgrade failed with bacula-console-qt installed

[Elimar Riesebieter]

Control: severity -1 serious
Control: merge -1 813479


-- 
 >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--

Bug#813563: [Pkg-alsa-devel] Bug#813563: alsa-utils: Overwrite files from unrelated package

[Elimar Riesebieter]

Control: severity -1 serious
Control: merge -1 813479

* Michael Rasmussen  [2016-02-03 08:03 +0100]:

> Package: alsa-utils
> Version: 1.0.29-1+b1
> Severity: critical
> Justification: breaks unrelated software
> 
> This bug: #813528 actually should have been made here. Please link.
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (900, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.3.0-1-amd64 (SMP w/6 CPU cores)
> Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages alsa-utils depends on:
> ii  dialog  1.2-20150920-1
> ii  kmod22-1
> ii  libasound2  1.1.0-1
> ii  libc6   2.21-7
> ii  libncursesw56.0+20151024-2
> ii  libsamplerate0  0.1.8-8
> ii  libtinfo5   6.0+20151024-2
> ii  lsb-base9.20160110
> ii  whiptail0.52.18-2
> 
> alsa-utils recommends no packages.
> 
> alsa-utils suggests no packages.
> 
> -- no debconf information
> 
> 
> 
> This mail was virus scanned and spam checked before delivery.
> This mail is also DKIM signed. See header dkim-signature.
> 
> ___
> Pkg-alsa-devel mailing list
> pkg-alsa-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel
> 

-- 
 Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)

Bug#812474: texlive-base: error processing package texlive-base

[Elimar Riesebieter]

Package: texlive-base
Version: 2015.20160117-1
Severity: grave
Justification: renders package unusable


Installing texlive-base gives:

Setting up texlive-base (2015.20160117-1) ...
basename: missing operand
Try 'basename --help' for more information.
dpkg: error processing package texlive-base (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of texlive-latex-base:
 texlive-latex-base depends on texlive-base (>= 2015); however:
  Package texlive-base is not configured yet.

Bug#812474: texlive-base: error processing package texlive-base

[Elimar Riesebieter]

* Elimar Riesebieter <riese...@lxtec.de> [2016-01-24 11:56 +0300]:

> Package: texlive-base
> Version: 2015.20160117-1
> Severity: grave
> Justification: renders package unusable
> 
> 
> Installing texlive-base gives:
> 
> Setting up texlive-base (2015.20160117-1) ...
> basename: missing operand
> Try 'basename --help' for more information.
> dpkg: error processing package texlive-base (--configure):
>  subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of texlive-latex-base:
>  texlive-latex-base depends on texlive-base (>= 2015); however:
>   Package texlive-base is not configured yet.

After running an upgrade everything went ok.

Elimar
-- 
 >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--

Bug#812499: FTBFS: undefined reference to `gnutls_protocol_set_priority'

[Elimar Riesebieter]

Control: merge -1 812424

* Vincent Lefevre  [2016-01-24 14:30 +0100]:

> Package: lynx-cur
> Version: 2.8.9dev8-1
> Severity: serious
> 
> The lynx-cur build fails with the error:
> 
> .../lynx-cur-2.8.9dev8/src/tidy_tls.c:282: undefined reference to 
> `gnutls_protocol_set_priority'

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812424

Elimar
-- 
 >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--

Bug#798237: isc-dhcp-server: after upgrading to 4.3.3-3 the server doesn't start

[Elimar Riesebieter]

Control: severity -1 normal

-- 
 On the keyboard of life you have always
  to keep a finger at the escape key;-)

Bug#798237: isc-dhcp-server: after upgrading to 4.3.3-3 the server doesn't start

[Elimar Riesebieter]

Package: isc-dhcp-server
Version: 4.3.3-3
Followup-For: Bug #798237

Control: serverity -1 normal

The bug is:
Support for ddns-update-style not compiled in

In 4.3.2 ddns-update-style worked, though.

-- 
Elimar

Bug#798237: isc-dhcp-server: after upgrading to 4.3.3-3 the server doesn't start

[Elimar Riesebieter]

Package: isc-dhcp-server
Version: 4.3.2-1
Severity: grave
Justification: renders package unusable

Setting up isc-dhcp-server (4.3.3-3) ...
Installing new version of config file /etc/init.d/isc-dhcp-server ...
dhcpd self-test failed. Please fix /etc/dhcp/dhcpd.conf.
The error was:
Internet Systems Consortium DHCP Server 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Support for ddns-update-style not compiled in

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

The error was: 
Is not that much expressive

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

Kernel: Linux 4.1.6-baumbart-lxtec-i686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.57
ii  debianutils4.5.1
ii  isc-dhcp-common4.3.2-1
ii  libc6  2.19-19
ii  libdns-export100   1:9.9.5.dfsg-12
ii  libirs-export911:9.9.5.dfsg-12
ii  libisc-export951:9.9.5.dfsg-12
ii  lsb-base   4.1+Debian14

isc-dhcp-server recommends no packages.

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed:
authoritative;
ddns-update-style interim;
ddns-updates on;
ddns-domainname "home.lxtec.de";
ddns-rev-domainname "in-addr.arpa.";
option domain-name "home.lxtec.de";
option domain-name-servers 192.168.200.1;
default-lease-time 28800;
max-lease-time 86400;
ignore client-updates;
log-facility local7;
update-static-leases true;
include "/etc/bind/rndc.key";
 zone home.lxtec.de. {
 primary 192.168.200.1;
 key "lxtec-dhcp";
 }
 zone 200.168.192.in-addr.arpa. {
 primary 192.168.200.1;
 key "lxtec-dhcp";
 }
   # Ein paar feste IP-Adressen werden vergeben
# INTEL 2400 Linux
host gandalf {
option dhcp-client-identifier 1:0:1b:21:70:ec:ca;
fixed-address 192.168.200.201;
ddns-hostname "gandalf";
option host-name "gandalf";
max-lease-time 28800;
}
 ..
 
   subnet 192.168.200.0 netmask 255.255.255.0 {
   option domain-name-servers 192.168.200.1;
   option broadcast-address 192.168.200.255;
   option routers 192.168.200.254;
   range 192.168.200.100 192.168.200.199;
 }

/etc/logcheck/ignore.d.server/isc-dhcp-server 71f490713ed345ec955be8e2a5bc6cf4 
[Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/isc-dhcp-server 
71f490713ed345ec955be8e2a5bc6cf4'

-- debconf information:
  isc-dhcp-server/config_warn:
  isc-dhcp-server/interfaces:

Bug#794342: gnote: Please rebuild gnote

[Elimar Riesebieter]

Package: gnote
Version: 3.16.2-1
Severity: grave
Justification: renders package unusable

Due to the transition to gcc-5 gnote needs a rebuild against
libgcc1. Otherwise it would be removed or substituded by tomboy
which blows up installations with mono stuff. Pick up the chance to
upgrade to 5.17.

Elimar

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-rc4-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT)
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)

Versions of packages gnote depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  libatk1.0-0  2.16.0-2
ii  libatkmm-1.6-1   2.22.7-2.1
ii  libc62.19-19
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libenchant1c2a   1.6.0-10.1
ii  libgcc1  1:5.1.1-14
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libglib2.0-0 2.44.1-1.1
ii  libglibmm-2.4-1c2a   2.44.0-1
ii  libgtk-3-0   3.16.6-1
ii  libgtkmm-3.0-1   3.16.0-1
ii  libgtkspell3-3-0 3.0.7-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangomm-1.4-1 2.36.0-1
ii  libsecret-1-00.18.2-1
ii  libsigc++-2.0-0c2a   2.4.1-1
ii  libstdc++6   5.1.1-14
ii  libuuid1 2.26.2-9
ii  libx11-6 2:1.6.3-1
ii  libxml2  2.9.2+dfsg1-3
ii  libxslt1.1   1.1.28-2+b2

gnote recommends no packages.

gnote suggests no packages.

-- no debconf information


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

Bug#794342: gnote: Please rebuild gnote

[Elimar Riesebieter]

* Elimar Riesebieter riese...@lxtec.de [2015-08-01 20:54 +0200]:

 Pick up the chance to upgrade to 5.17.

Should be 3.17.

Elimar
-- 
 Numeric stability is probably not all that
  important when you're guessing;-)


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

Bug#742388: Fixed in alsa-utils 1.0.27.2-1

[Elimar Riesebieter]

On Mon, 28 Apr 2014 18:37:30 -0400 Felipe Sateler fsate...@debian.org wrote:
 This was fixed in alsa-utils by a similar approach.

So bug closed herewith.

Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
 Friedrich Nietzsche


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

Bug#720678: Bug#712980: fixed in alsa-utils 1.0.27.2-1

[Elimar Riesebieter]

On Sat, 19 Oct 2013 14:34:36 + Jordi Mallach jo...@debian.org wrote:
 Source: alsa-utils
 Source-Version: 1.0.27.2-1
 
 We believe that the bug you reported is fixed in the latest version of
 alsa-utils, which is due to be installed in the Debian FTP archive.

Should be closed really.

Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
 Friedrich Nietzsche


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

Bug#762984: Alert! /dev/vg0/usr does not exist

[Elimar Riesebieter]

* Simon McVittie s...@debian.org [2014-11-27 11:51 +]:

 On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote:
  I suspect this is essentially the same bug as #616689 and #678696,
  except that now it may affect mounting /usr as well as /.
 
 I think this bug report is actually describing more than one bug in more
 than one package that have similar symptoms. There might be things
 that can be fixed in mdadm and lvm2 to fix the initramfs-tools/0.117
 regressions without needing to implement a full event-driven setup in
 initramfs-tools.
 
  RAID (Elimar, Sven) 
 
 Elimar Riesebieter's System 2 has a bunch of mdadm (RAID) partitions.
 
 Elimar, what is in your /etc/default/mdadm on System 2 (and System 1
 for that matter)? I predict that the answer includes something like
 INITRDSTART=/dev/md6.

Right, adding root and usr raid partitions to INITRDSTART like
INITRDSTART='/dev/md3 /dev/md5' or just 'all' does the job. There
is no need to involve initramfs to mount /usr before init.

[...]
  LVM (Elimar's System 1, Sven, Torsten, IOhannes, Javier) 
 
 In the LVM case, debian/initramfs-tools/lvm2/scripts/local-top
 does this:
 
 activate_vg $ROOT
 activate_vg $resume
 
 Note the lack of handling for /usr here.
 
 Further, activate_vg uses lvm lvchange to activate only the LV
 necessary for the root filesystem; if /usr is on a separate VG,
 it's not going to work.
 
 This on its own would be enough to make Sven Hartge's system fail:
 /usr needs a LVM partition activated that / does not. Similarly,
 I think Elimar's System 1 is going to activate vg0/root but not
 vg0/usr.

Right!

 We don't have enough information in this bug report to know what
 layout Torsten, IOhannes, Javier used on their systems, but we can
 guess from the fact that vgchange -a y is a successful workaround...
 I predict that these are LVM over either a single RAID array, or
 real partitions.
 
 
 
 The ideal thing in both of these situations would be to use the same
 logic as *mounting* /usr - mount the rootfs first, then read its fstab
 to find out where /usr is, avoiding hard-coding that knowledge into
 the initramfs - but I think that would need a significantly more
 complicated hook structure.
 
 Perhaps modifying mdadm and lvm2 so they will set up enough md/lvm bits
 for /usr in the initramfs would be sufficient for a 95% solution?

What do you propose to adapt it to lvm2? Why should we avoid hardcoding via
/etc/initramfs-tools/scripts? Maybe a move from
/usr/share/initramfs-tools/scripts/local-top/lvm2 to
/lib/initramfs-tools/scripts/local-top/lvm2 should work?

Elimar
-- 
 Learned men are the cisterns of knowledge,
  not the fountainheads ;-)


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

Bug#762984: Alert! /dev/vg0/usr does not exist

[Elimar Riesebieter]

* Simon McVittie s...@debian.org [2014-11-27 21:19 +]:

 On 27/11/14 20:09, Elimar Riesebieter wrote:
  Right, adding root and usr raid partitions to INITRDSTART like
  INITRDSTART='/dev/md3 /dev/md5' or just 'all' does the job. There
  is no need to involve initramfs to mount /usr before init.
 
 If your init is systemd, initramfs-tools = 0.117 *does* automatically
 mount /usr before init, to ensure that rootfs - /usr interdependencies
 can never be a problem (for instance third-party udev rules often need
 helpers in /usr).

Not always. If the raid partition for /usr isn't initialized it
can't be mounted, though.

 That's the feature that I'm trying to get migratable
 into testing, because when it works, it'll make the boot sequence a lot
 simpler; but it's also the feature that caused this regression.

We have to catch the case whether /usr is on a seperated raid
partition here!

 (It was meant to do the same for non-systemd too, but initscripts
 doesn't currently support that.)

Doesn't matter

  Perhaps modifying mdadm and lvm2 so they will set up enough md/lvm bits
  for /usr in the initramfs would be sufficient for a 95% solution?
  
  What do you propose to adapt it to lvm2? Why should we avoid hardcoding via
  /etc/initramfs-tools/scripts? Maybe a move from
  /usr/share/initramfs-tools/scripts/local-top/lvm2 to
  /lib/initramfs-tools/scripts/local-top/lvm2 should work?
 
 No, whether /usr/share/initramfs-tools is on the rootfs is irrelevant:
 it's only used when update-initramfs is run, on a fully booted system,
 usually as a result of a dpkg run.
 
 What the initramfs does is currently (in pseudocode):
 
 * (hook provided by cryptsetup)
   decrypt encrypted volumes needed for / or swap
 * (hook provided by mdadm) start RAID arrays needed for / or swap

Only if initialized by INITRDSTART

 * (hook provided by lvm2) start LVM volumes needed for / or swap
 * (basic functionality of initramfs-tools) if swap contains a
   hibernation image, resume from it
 * (basic functionality of initramfs-tools) mount /
 * (basic functionality of initramfs-tools) if /usr is a separate
   filesystem, mount it

Only if initialized by INITRDSTART

 * (basic functionality of initramfs-tools) run the real init
 
 The patch I attached to #767832 changes the cryptsetup step to decrypt
 encrypted volumes needed for /, /usr or swap so that, when we get to
 the mount /usr step, it actually works, even if /usr is on an
 encrypted volume.

Will have a further look at it on weekend

Elimar
-- 
 Numeric stability is probably not all that
  important when you're guessing;-)


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

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[Elimar Riesebieter]

Control: found -1 0.118

* Elimar Riesebieter riese...@lxtec.de [2014-09-26 22:03 +0200]:

 Package: initramfs-tools
 Version: 0.117


-- 
  Alles was viel bedacht wird ist bedenklich!;-)
 Friedrich Nietzsche


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

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[Elimar Riesebieter]

* Elimar Riesebieter riese...@pipin.home.lxtec.de [2014-09-27 22:14 +0200]:

 On Sat, 27 Sep 2014 20:05:07 +0100 Ben Hutchings b...@decadent.org.uk wrote:

[...]

  Is / on RAID and/or LVM?  I suspect we may not correctly handle some
  cases where /usr requires a RAID or VG that / does not.
 
 ##
 System 1:
 /dev/mapper/vg0-burn /burn
 /dev/mapper/vg0-home /home
 /dev/mapper/vg0-root /
 /dev/mapper/vg0-source   /source
 /dev/mapper/vg0-tmp  /tmp
 /dev/mapper/vg0-usr  /usr
 /dev/mapper/vg0-var  /var
 /dev/mapper/vg0-working  /working
 /dev/md5 /boot
 
 where the volume group resides on a RAID1
 /dev/md5 is a RAID1 as well
 Alert! /dev/vg0/usr does not exist

Workaround:
cat /etc/initramfs-tools/scripts/local-top/vgscan

#!/bin/sh
vgchange -ay


 ##
 System 2:
 /dev/md5   /boot
 /dev/md6   /
 /dev/md7   /usr
 /dev/md8   /var
 /dev/md9   /tmp
 /dev/md10  /burn
 /dev/md11  /source
 /dev/md12  /working
 
 where all partitions are configured as RAID1
 Alert! /dev/md5 does not exist

Must be: Alert! /dev/md7 does not exist

Workaround:
cat /etc/initramfs-tools/scripts/local-top/mdadm-assemble

#!/bin/sh
mdadm --assemble --scan /dev/md7


Elimar
-- 
 We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds


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

Bug#762870: initramfs-tools: fails to boot after upgrade from 0.116 to 0.117

[Elimar Riesebieter]

On Fri, 26 Sep 2014 14:59:28 +0200 Jakub Wilk jw...@debian.org wrote:
 -f: No such file or directory
 
 I believe this was caused by:
 http://anonscm.debian.org/cgit/kernel/initramfs-tools.git/commit/?id=be18fee1bd52
 
 The readlink command in initramfs doesn't seem to support -f:
 
 $ readlink -f /
 -f: No such file or directory

Inspired from:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762870#42

Have had the same symptoms on one machine. Installing busybox works
around this issue and boots as expected, though.

Elimar
-- 
 You cannot propel yourself forward by
  patting yourself on the back.


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

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[Elimar Riesebieter]

* Elimar Riesebieter riese...@lxtec.de [2014-09-28 11:54 +0200]:

 * Elimar Riesebieter riese...@pipin.home.lxtec.de [2014-09-27 22:14 +0200]:
 
[...]
 Workaround:
 cat /etc/initramfs-tools/scripts/local-top/vgscan
 
 #!/bin/sh
 vgchange -ay
[...]
 Workaround:
 cat /etc/initramfs-tools/scripts/local-top/mdadm-assemble
 
 #!/bin/sh
 mdadm --assemble --scan /dev/md7

To make sure this works one has to install busybox which provides
/usr/share/initramfs-tools/hooks/zz-busybox, though.

Elimar
-- 
 Experience is something you don't get until
  just after you need it!


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

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[Elimar Riesebieter]

On Fri, 26 Sep 2014 22:03:29 +0200 Elimar Riesebieter riese...@lxtec.de wrote:
 Package: initramfs-tools
 Version: 0.117
 Severity: normal
 
 
 LVM2 running on top of RAID1.

Running /usr on a separate raid partition is not recognized too.
Verified that on an other System:

Alert! /dev/md5 does not exist

Elimar
-- 
 what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


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