Bug#981461: ser2net: unable to start, undefined symbol: gensio_alloc_mdns

[Gedalya]

Package: ser2net
Version: 4.3.2-1
Severity: grave

When attempting to start ser2net I get the message:
/usr/sbin/ser2net: symbol lookup error: /usr/sbin/ser2net: undefined 
symbol: gensio_alloc_mdns
This happens when I start it in any way, such as just invoking the 
executable with no parameters, or as:

/usr/sbin/ser2net -c /etc/ser2net.yaml
However the parameters -h and -v do work.

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

Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ser2net depends on:
ii  libc6    2.31-9
ii  libgensio0   2.2.3-1
ii  libyaml-0-2  0.2.2-1
ii  lsb-base 11.1.0

ser2net recommends no packages.

Versions of packages ser2net suggests:
ii  telnet  0.17-41.2

-- Configuration Files:
/etc/ser2net.conf changed:
BANNER:banner:\r\nser2net port \p device \d [\s] (Debian GNU/Linux)\r\n\r\n
2000:raw:600:/dev/ttyS0:9600 8DATABITS NONE 1STOPBIT
2001:raw:600:/dev/ttyS1:9600 8DATABITS NONE 1STOPBIT
3000:raw:600:/dev/ttyS0:115200 8DATABITS NONE 1STOPBIT
3001:raw:600:/dev/ttyS1:115200 8DATABITS NONE 1STOPBIT

/etc/ser2net.yaml changed:
%YAML 1.1
---
define:  \r\nser2net port \p device \d [\B] (Debian 
GNU/Linux)\r\n\r\n

connection: 
    accepter: tcp,2000
    enable: on
    options:
  banner: *banner
  kickolduser: true
  telnet-brk-on-sync: true
    connector: serialdev,
  /dev/ttyS0,
  9600n81,local
connection: 
    accepter: telnet(rfc2217),tcp,3000
    enable: on
    options:
  banner: *banner
  kickolduser: true
  telnet-brk-on-sync: true
    connector: serialdev,
  /dev/ttyS0,
  19200n81,local


-- no debconf information

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

[Gedalya]

Opened an issue with ungoogled-chromium to discuss this on their end.

https://github.com/ungoogled-software/ungoogled-chromium-debian/issues/184

Bug#972134: RE: chromium: please, consider moving the package to team-maintainance to properly maintain it

[Gedalya]

Hello,

I wonder if some collaboration would be possible with the ungoogled-chromium 
people, and linux mint (#975060)?

In the case of linux-mint, they seem to have given up in Debian being their 
upstream for this package, and ungoogled-chromium seems to be held back, 
adhering to Debian as their upstream.

Could all this capability and effort somehow come together?

Bug#930469: chromium: Insta-segfault on start

[Gedalya]

I got this behavior with "session":{"restore_on_startup":1} in 
~/.config/chromium/{profile}/Preferences.

I only get this on my laptop, for some reason, not my desktop.

I can set that to 0 instead of 1 and everything is OK, except my saved tabs of 
course which are not restored.

Also, I've noticed that having that set to 1, I can sometimes close Chromium 
and open it again. I'm not quite sure on what the condition is, but closing it 
down with Ctrl+W, tab by tab down to the last one, seems to cause the issue, 
and closing all of Chromium with Ctrl+Q actually seems to work better. Again, 
not 100% sure about this.

For some reason, opening with --disable-extensions works around the issue, too.

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Gedalya]

> This currently looks like this now (after I have uninstalled
> cgroupfs-mount):
>
> → findmnt -R /sys/fs/cgroup
> TARGET   SOURCE  FSTYPE  OPTIONS
> /sys/fs/cgroup   tmpfs   tmpfs   rw,nosuid,nodev,noexec,mode=755
> ├─/sys/fs/cgroup/unified cgroup2 cgroup2 
> rw,nosuid,nodev,noexec,relatime,nsdelegate
> └─/sys/fs/cgroup/elogind cgroup  cgroup  
> rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind
>
> But I have to assume that these mount points where at least present
> before I uninstalled cgroupfs-mount, too.
>
>   Regards, Axel

I can say I've always had this issue with only cgroup2 mounted and no cgroup 
(what you might call "v1")

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1

[Gedalya]

This is affecting EAP with wpa_supplicant.
See https://bugs.debian.org/877904

Bug#820974: bind9 crypto issue

[Gedalya]

On Fri, 20 Jan 2017 07:38:32 -0700 LaMont Jones wrote:

>
> Can you provide a named.conf that reproduces the issue?
>

I've tried commenting out everything locally modified, leaving basically a 
default config.
It seems the only thing needed to reproduce this issue is to run bind in a 
chroot.
bind-mounting /usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines (on amd64) into 
the chroot works around the issue.
I got this so far on several servers with dissimilar configurations.

Bug#845785: still crashes

[Gedalya]

Package: chromium
Version: 55.0.2883.75-1

Over here it crashes much less, but still crashes on web.whatsapp.com and 
sometimes on certain facebook pages.
The attached debugger output is from web.whatsapp.com


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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.1-1
ii  libavformat577:3.2.1-1
ii  libavutil55  7:3.2.1-1
ii  libc62.24-7
ii  libcairo21.14.6-1.1
ii  libcups2 2.2.1-2
ii  libdbus-1-3  1.10.12-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-1
ii  libflac8 1.3.1-4
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.1-5
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnettle6   3.3-1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.26-2
ii  libpulse09.0-5
ii  libre2-3 20161101+dfsg-2
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.2.1-5
ii  libvpx4  1.6.0-3
ii  libwebp6 0.5.1-3
ii  libwebpdemux20.5.1-3
ii  libx11-6 2:1.6.3-1
ii  libx11-xcb1  2:1.6.3-1
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b3

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

# Env:
# LD_LIBRARY_PATH=
#PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
#GTK_PATH=
#  CHROMIUM_FLAGS= --show-component-extension-options 
--ignore-gpu-blacklist --disable-background-networking 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=22.0.0.209
/usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.4qSw2Q
GNU gdb (Debian 7.11.1-2+b1) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium/chromium...Reading symbols from 
/usr/lib/debug/.build-id/0b/ff698125612b352cb147d3c5af76bf6461e7bd.debug...(no 
debugging symbols found)...done.
(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/lib/chromium/chromium --show-component-extension-options 
--ignore-gpu-blacklist --disable-background-networking 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=22.0.0.209 --single-process 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdea8b700 (LWP 8185)]
[New Thread 0x7fffde28a700 (LWP 8190)]
[New Thread 0x7fffdd681700 (LWP 8191)]
[New Thread 0x7fffdce80700 (LWP 8192)]
[New Thread 0x7fffdc67f700 (LWP 8193)]
[New Thread 0x7fffdc677700 (LWP 8194)]
[New Thread 0x7fffdbe6f700 (LWP 8195)]
[New Thread 0x7fffdb66e700 (LWP 8196)]
[New Thread 0x7fffd98d8700 (LWP 8197)]
[New Thread 0x7fffd90d7700 (LWP 

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/10/2016 05:26 AM, Bernhard Schmidt wrote:
> I have just uploaded 2.5.5~dfsg-3 with all patches bundled in Asterisk
> applied. Please take a look, should be available shortly.

Installed, works just fine.

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

OK, confirmed.
The patch (r5401) works, we're back with the previous behavior:

[Nov  9 20:43:33] ERROR[14871]: res_pjsip.c:2883 ast_sip_create_dialog_uac: 
Could not create dialog to endpoint '' as URI '' is not valid
[Nov  9 20:43:33] ERROR[14871]: chan_pjsip.c:1947 request: Failed to create 
outgoing session to endpoint ''
[Nov  9 20:43:33] WARNING[14935][C-0001]: app_dial.c:2524 dial_exec_full: 
Unable to create channel of type 'PJSIP' (cause 3 - No route to destination)
[Nov  9 20:43:33] ERROR[14871]: res_pjsip.c:2883 ast_sip_create_dialog_uac: 
Could not create dialog to endpoint '' as URI '' is not valid
[Nov  9 20:43:33] ERROR[14871]: chan_pjsip.c:1947 request: Failed to create 
outgoing session to endpoint ''
[Nov  9 20:43:33] WARNING[14935][C-0001]: app_dial.c:2524 dial_exec_full: 
Unable to create channel of type 'PJSIP' (cause 3 - No route to destination)

And the call goes through just fine.

I guess the problem you had when reproducing the issue was another problem. 
Probably including some more of the upstream patches would be a good measure 
indeed.

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

r5401 seems to be the fix:

https://trac.pjsip.org/repos/ticket/1946

However I'm having trouble adding a patch with this source package :-(

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/09/2016 06:26 PM, Gedalya wrote:
> asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: 
> Assertion `sess && sess->endpt' failed.
> Aborted
>
> This is me calling myself via my outbound trunk and coming back in via my 
> inbound trunk.
> The problem comes up only on the inbound calls, at the point where I dial 
> them to the phones and other devices.
> If I just call e.g. my mobile phone it works fine, I can complete the call 
> and asterisk continues fine.

Per [0] + google translate and testing and confirming locally, the problem is 
isolated to missing (not currently registered) SIP peers.

Making sure the Dial() app is only dialing registered and available peers makes 
the problem go away.

Next step would be to see if there is a patch upstream addressing this.

[0] https://forum.asterisk.ru/viewtopic.php?f=5=7772=10

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/09/2016 04:51 AM, Bernhard Schmidt wrote:

> I have now uploaded Asterisk 13.12.1~dfsg-1 into sid, should be built
> and available within a few hours. This works well for me with pjproject
> from sid. Maybe it really just needed a recompile, but you had already
> tested that in the beginning. Would it be possible that something went
> wrong there?
I don't see what or how. I definitely rebuilt against the new pjproject.
I'm getting the same problems now, with the new packages in the debian archive.

Note that I can make outbound calls just fine. The problem is perhaps triggered 
by something specific in my inward dialing plan.

This is with the new packages:

-- Executing *desk-out:1] Goto("PJSIP/*-", 
"desk-out,*,1") in new stack
-- Goto (desk-out,*,1)
-- Executing [*@desk-out:1] Set("PJSIP/*-", 
"CALLERID(num)=*") in new stack
-- Executing [*@desk-out:2] Goto("PJSIP/*-", 
"out-vitel,*,1") in new stack
-- Goto (out-vitel,*,1)
-- Executing [*@out-vitel:1] MixMonitor("PJSIP/*-", 
"/var/local/callrec/2016-11/1478733136.0.wav") in new stack
  == Begin MixMonitor Recording PJSIP/*-
-- Executing [*@out-vitel:2] Set("PJSIP/*-", 
"CDR(peername)=*") in new stack
-- Executing [*@out-vitel:3] Dial("PJSIP/*-", 
"PJSIP/*@trunk-didlogic") in new stack
-- Called PJSIP/*@trunk-didlogic
    -- Executing [*@from-external:1] 
Goto("PJSIP/trunk-vitelity-in-0002", "internal,gedalya-all,1")
-- Goto (internal,gedalya-all,1)
    -- Executing [gedalya-all@internal:1] 
Set("PJSIP/trunk-vitelity-in-0002", "CDR(peername)=trunk-vitelity-in") in 
new stack
-- Executing [gedalya-all@internal:2] 
MixMonitor("PJSIP/trunk-vitelity-in-0002", 
"/var/local/callrec/2016-11/1478733137.2.wav") in new stack
  == Begin MixMonitor Recording PJSIP/trunk-vitelity-in-0002
-- Executing [gedalya-all@internal:3] 
Dial("PJSIP/trunk-vitelity-in-0002", 
"PJSIP/*/*/*/*/*,30") in new stack
asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: Assertion 
`sess && sess->endpt' failed.
Aborted

This is me calling myself via my outbound trunk and coming back in via my 
inbound trunk.
The problem comes up only on the inbound calls, at the point where I dial them 
to the phones and other devices.
If I just call e.g. my mobile phone it works fine, I can complete the call and 
asterisk continues fine.

I'll try patching pjproject now and see how that goes.

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/06/2016 05:50 PM, Bernhard Schmidt wrote:
> Nothing productive on the upstream mailinglist (or rather disturbing,
> they say that ABI can change in backward incompatible way even in minor
> versions and you're always expected to recompile),
Yea, I followed the conversation there. Looks rather grim.

>  BUT thanks to Stepan
> Golosunov and Tzafrir in Bug#828240 there now seems to be a way to build
> Asterisk 13.12.1 against OpenSSL 1.1.0. 
>
> I have tested that build (built against pjproject 2.5.5~dfsg-2 in sid)
> and it does not crash for me.
OK, a little confused here: the resulting asterisk will link against both 
libssl1.1 and libssl1.0.2 (via pjsip) during runtime?
Does that kind of thing work?


> It will probably take a few more days to fully test this (and import a
> few other crash fixes for pjproject as well for good measure),
Agreed, basically all the revisions in SVN related to DNS resolution since 
2.5.5 look important.

Anyhow, I'll try this on my end soon and let you know how it went.

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/03/2016 07:39 AM, Bernhard Schmidt wrote:
> Confirmed. If you start Asterisk in the foreground you actually get an
> assertion
>
> asterisk: ../src/pj/os_core_unix.c:1254: pj_mutex_lock: Assertion
> `mutex' failed.
> Aborted
>
> Haven't done any further debugging until now, since we can't build
> asterisk.

Hi,

I decided to try this: I made a sid chroot, manually downgraded to libssl-dev 
1.0.2j-1 from stretch, and built asterisk from the current packaging git head 
(ec0143a).
I actually enabled OpenSSL-1.1.0-support.patch while I was at it.

Ultimately, running this with pjproject 2.5.5~dfsg-2 failed at the same stage, 
but with a different assert:

asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: Assertion 
`sess && sess->endpt' failed.
Aborted

Bug#833501: found in 53.0.2785.92-2

[Gedalya]

fixed 833501 52.0.2743.116-2
found 833501 53.0.2785.92-2
thanks


now that we're back with gcc 6, same crashes occur with facebook, google maps 
and other sites.

This got it working for me

--- rules.orig2016-09-06 15:44:51.692191414 -0400
+++ rules2016-09-06 15:47:29.097229998 -0400
@@ -16,6 +16,10 @@
 export CFLAGS+=-fuse-ld=gold
 export CXXFLAGS+=-fuse-ld=gold
 
+# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68853
+export CFLAGS+=-fno-delete-null-pointer-checks
+export CXXFLAGS+=-fno-delete-null-pointer-checks
+
 # treat all warnings as errors
 defines=werror=
 

Bug#821154: chromium: crashes on video

[Gedalya]

On 04/20/2016 08:13 PM, Gedalya wrote:
> Going to try this patch now.

Built with pbuilder against sid. /usr/lib/chromium/chromium is now ~2MB smaller.
New packages pulled in from sid: libavcodec57 libavformat57 libavutil55 
libswresample2 - version 7:3.0.1-3
ldd does show it's actually using them.
Video sites work fine.
Will report if anything interesting happens.

Bug#821154: chromium: crashes on video

[Gedalya]

On Wed, 20 Apr 2016 09:31:34 +0200 Sebastian Ramacher wrote:
> On 2016-04-16 10:20:26, Michael Gilbert wrote:
> > control: tag -1 help, confirmed
> > control: severity -1 grave
> > x-debbugs-cc: pkg-multimedia-maintain...@lists.alioth.debian.org
> >
> > Jose A. Fernandez Gonzalez wrote:
> > > Version 49 of Chromium and earlier versions depend on ffmpeg libraries
> > > (libavcodec, libavformat, libavutil, ...) and it seems version 50 doesn't
> > > depend on those libraries, maybe the problem comes out with HTML5 content
> > > because of that.
> >
> > Chromium's linking of ffmpeg has somehow changed, so ffmpeg.patch will
> > need to be updated, or the embedded copy of ffmpeg could be used
> > again.
> >
> > I don't have much free time right now, so it may be some time before I
> > get to this. Help is appreciated.
>
> With the attached patch chromium links against ffmpeg at least. Other than 
> that
> it's untested.
>
> Regards
> --
> Sebastian Ramacher

It occurred to me to try to rebuild the package locally, unmodified. I built it 
with pbuilder against sid. ldd doesn't show it linking against system's ffmpeg. 
Video now works fine without crashing.

Going to try this patch now.

Bug#816042: Don't include in stretch

[Gedalya]

On Mon, 14 Mar 2016 01:56:06 +0100 Jonas Smedegaard wrote:

>
> If noone else cares, I will consider step up and take over maintaining
> this package (but I really would prefer not to do so: I have plenty of
> other packages to look after already).
>
> - Jonas

I see you're preparing a release in git, thank you so much!! Much appreciated.

Bug#810847: php5.6-json not available

[Gedalya]

Package: php5.6-fpm
Version: 5.6.17+dfsg-1
Severity: grave


Hi,

apt-get install php5.6-fpm results in:

The following packages have unmet dependencies:
 php5.6-fpm : Depends: php5.6-json but it is not installable

Thanks!

Bug#696817: dovecot destroys user ssl configuration

[Gedalya]

On 01/23/2013 03:10 PM, Herwin Weststrate wrote:

Here is what I came up with, if this seems to make sense and is
considered as a patch, *please do proofread and test it, I did no
such thing on my end.*


One small remark: the + after ssl_key and ssl_cert (lines 122+123) 
mean match one or more of the last character. Thus, a config line 
like ssl_certt=/foo/bar would match too. The line should be fine 
without the + here.
And it will break if the filename contains whitespace, but I'm not 
sure if dovecot supports this (and imho it's a stupid idea anyway).




Yes you're right, it makes no sense, that + sign should be omitted. Sorry.

awk is probably faster anyway:
$(awk -F '/\s|=|' '/^\s*ssl_cert/ {print $3; exit}' 
/etc/dovecot/conf.d/10-ssl.conf)
$(awk -F '/\s|=|' '/^\s*ssl_key/ {print $3; exit}' 
/etc/dovecot/conf.d/10-ssl.conf)



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

Bug#696817: dovecot destroys user ssl configuration

[Gedalya]

On 01/14/2013 03:10 PM, Jaldhar H. Vyas wrote:
So what we really need is more testing before an upload even happens.  
In theory there is a team maintaining this package but in practice the 
others have even less free time than I do and this last year I have 
had next to no time at all.  (I mean its been 3 weeks since this 
problem was reported and I'm only just responding. That would be 
unacceptable as a user even to me.)  I try and recruit anyone who 
shows interest but that hasn't worked either so far.  So once again, I 
ask anyone reading this who cares about the best possible dovecot 
package in Debian to pitch in. It's easy to get access to the source 
repository and I'll help in anyway I can even giving you ownership if 
you can do a better job. 


I'd definitely be interested in being contacted when you're changing 
stuff and want testing. To me it would be an opportunity to learn about 
Debian packaging, and I might be even able to help a bit, too. I'm a 
novice but it shouldn't cost you much just to add me to your tester list :-)



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

Bug#696817: dovecot destroys user ssl configuration

[Gedalya]

-if (/^\w*?ssl_cert/) {
-say 'ssl_cert = $OLD_SSL_CERT'
+if (m|^\w*?ssl_cert\s*=\s*$OLD_SSL_CERT|) {
+say 'ssl_cert = $SSL_CERT'
  }
-elsif (/^\w*?ssl_key/) {
-say 'ssl_key = $OLD_SSL_KEY'
+elsif (m|^\w*?ssl_key\s*=\s*$OLD_SSL_KEY|) {
+say 'ssl_key = $SSL_KEY'


If I'm following the logic correctly then that would change to $SSL_CERT 
and $SSL_KEY while these will never be generated.

And I'm still trying to figure out why that whole block of code exists..

Here is what I came up with, if this seems to make sense and is 
considered as a patch, *please do proofread and test it, I did no such 
thing on my end.*
The assumption being made is that current config works, and if it 
doesn't then it's not our business to attempt to fix it - it was broken 
and will remain broken for reasons beyond the scope of a package 
installation. And as for the recommendation to move the certificates, I 
can't see why we should try to actually do it for the user automatically.


--- postinst.old	2012-12-30 23:44:27.537179984 -0500
+++ postinst	2012-12-31 00:41:22.250090217 -0500
@@ -119,8 +119,8 @@ if [ $1 = configure ]; then
 
   ## SSL Certs
   # Certs and key file
-  OLD_SSL_CERT=/etc/ssl/certs/dovecot.pem
-  OLD_SSL_KEY=/etc/ssl/private/dovecot.pem
+  OLD_SSL_CERT=$(perl -ne 'print $1 and exit if m/^\s*ssl_cert+\s*=\s*(\S+)/' /etc/dovecot/conf.d/10-ssl.conf)
+  OLD_SSL_KEY=$(perl -ne 'print $1 and exit if m/^\s*ssl_key+\s*=\s*(\S+)/' /etc/dovecot/conf.d/10-ssl.conf)
   SSL_CERT=/etc/dovecot/dovecot.pem
   SSL_KEY=/etc/dovecot/private/dovecot.pem
 
@@ -128,24 +128,15 @@ if [ $1 = configure ]; then
 install -d -o root -g root -m0700 /etc/dovecot/private
   fi
 
-  if [ -e $OLD_SSL_CERT ] || [ -e $OLD_SSL_KEY ]; then
+  if [ $OLD_SSL_CERT = $SSL_CERT ]  [ -e $SSL_CERT ]  [ $OLD_SSL_KEY = $SSL_KEY ]  [ -e $SSL_KEY ]; then
+  echo You already have ssl certs for dovecot.
+  elif ([ -n $OLD_SSL_CERT ]  [ -e $OLD_SSL_CERT ]) || ([ -n $OLD_SSL_KEY ]  [ -e $OLD_SSL_KEY ]); then
   echo You already have ssl certs for dovecot.
   echo However you should move them out of /etc/ssl
   echo and into /etc/dovecot and update the configuration
   echo in /etc/dovecot/conf.d/10-ssl.conf accordingly.
   echo See /usr/share/doc/dovecot-core/NEWS.Debian.gz for details.
-perl -i -nE 
-if (/^\w*?ssl_cert/) {
-say 'ssl_cert = $OLD_SSL_CERT'
-}
-elsif (/^\w*?ssl_key/) {
-say 'ssl_key = $OLD_SSL_KEY'
-} else {
-print;
-} /etc/dovecot/conf.d/10-ssl.conf
   # Generate new certs if needed
-  elif [ -e $SSL_CERT ] || [ -e $SSL_KEY ]; then
-  echo You already have ssl certs for dovecot.
   else
   echo Creating generic self-signed certificate: $SSL_CERT
   echo This certificate will expire in 10 years.

Bug#696817: dovecot destroys user ssl configuration

[Gedalya]

Yes, I just hit this problem too.
My config was pointing to my own certificate and was changed to point to 
the self-signed cetificate.



I'm not quite sure what is the intended purpose of the following code in 
postinst?


  OLD_SSL_CERT=/etc/ssl/certs/dovecot.pem
  OLD_SSL_KEY=/etc/ssl/private/dovecot.pem

.

  if [ -e $OLD_SSL_CERT ] || [ -e $OLD_SSL_KEY ]; then
  echo You already have ssl certs for dovecot.
  echo However you should move them out of /etc/ssl
  echo and into /etc/dovecot and update the configuration
  echo in /etc/dovecot/conf.d/10-ssl.conf accordingly.
  echo See /usr/share/doc/dovecot-core/NEWS.Debian.gz for details.
perl -i -nE 
if (/^\w*?ssl_cert/) {
say 'ssl_cert = $OLD_SSL_CERT'
}
elsif (/^\w*?ssl_key/) {
say 'ssl_key = $OLD_SSL_KEY'
} else {
print;
} /etc/dovecot/conf.d/10-ssl.conf

First, why should you ever modify the conf file at all? And without 
informing the user and without keeping a backup?
And why do this just because dovecot's generated certificate files 
happen to exist?


Thanks,

Gedalya


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

Bug#685540: getting the asterisk module loadable

[Gedalya]

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689109
Re: asterisk-espeak


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

Bug#685540: asterisk-flite: app_flite fails to load

[Gedalya]

Package: asterisk-flite
Version: 2.1-1
Severity: grave

Using asterisk 1:1.8.13.0~dfsg-1+b1 on wheezy.

asterisk01-noc01*CLI module load app_flite
Unable to load module app_flite
Command 'module load app_flite' failed.
[Aug 21 15:02:01] WARNING[10528]: loader.c:779 inspect_module: Module 
'app_flite.so' was not compiled with the same compile-time options as 
this version of Asterisk.
[Aug 21 15:02:01] WARNING[10528]: loader.c:780 inspect_module: Module 
'app_flite.so' will not be initialized as it may cause instability.
[Aug 21 15:02:01] WARNING[10528]: loader.c:863 load_resource: Module 
'app_flite' could not be loaded.



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

Bug#680035: Dovecot v2.1.8 released

[Gedalya]

On 07/03/2012 02:49 AM, Jaldhar H. Vyas wrote:
Ok I'm escalating this then.  I'll ask if we can get 2.1.8 in or patch 
2.1.7 as you've suggested.  (A more likely outcome IMO.) 


I'd advocate for 2.1.8. The following fix,

- imapc: Fixed a crash when message had more than 8 keywords.
is something that I ran into while working on a long-running project of 
migrating a proprietary email system to dovecot. Currently I must use 
the auto-built dovecot binary packages, since it turned out to be 
impossible to do imapc-based migration for some email accounts using 
2.1.7. I don't know how common it is to have more than 8 keywords but it 
happened to me, and the new imapc thing is a wonderful and very useful 
thing, and it's nice to have it working and usable.





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

Bug#659818: dahdi-linux 2.5.0.1 won't build against Linux 3.2

[Gedalya]

fixed: 659818 2.6.1+dfsg-1
thanks




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

Bug#672862: wheezy currently uninstallable

[Gedalya]

Currently I'm unable to install wheezy:

May 19 07:41:08 debootstrap: Setting up tasksel (3.09) ...
May 19 07:41:11 debootstrap: Errors were encountered while processing:
May 19 07:41:11 debootstrap:  ifupdown
May 19 07:41:12 debootstrap: dpkg: dependency problems prevent configuration of 
ifupdown:
May 19 07:41:12 debootstrap:  netbase (5.0) breaks ifupdown (  0.7~rc1) and 
is installed.
May 19 07:41:12 debootstrap:   Version of ifupdown to be configured is 
0.7~alpha5+really0.6.16.
May 19 07:41:12 debootstrap: dpkg: error processing ifupdown (--configure):
May 19 07:41:12 debootstrap:  dependency problems - leaving unconfigured
May 19 07:41:12 debootstrap: Errors were encountered while processing:
May 19 07:41:12 debootstrap:  ifupdown
May 19 07:41:13 debootstrap: dpkg: dependency problems prevent configuration of 
ifupdown:
May 19 07:41:13 debootstrap:  netbase (5.0) breaks ifupdown (  0.7~rc1) and 
is installed.
May 19 07:41:13 debootstrap:   Version of ifupdown to be configured is 
0.7~alpha5+really0.6.16.
May 19 07:41:13 debootstrap: dpkg: error processing ifupdown (--configure):
May 19 07:41:13 debootstrap:  dependency problems - leaving unconfigured
May 19 07:41:13 debootstrap: Errors were encountered while processing:
May 19 07:41:13 debootstrap:  ifupdown
May 19 07:41:14 debootstrap: dpkg: dependency problems prevent configuration of 
ifupdown:
May 19 07:41:14 debootstrap:  netbase (5.0) breaks ifupdown (  0.7~rc1) and 
is installed.
May 19 07:41:14 debootstrap:   Version of ifupdown to be configured is 
0.7~alpha5+really0.6.16.
May 19 07:41:14 debootstrap: dpkg: error processing ifupdown (--configure):
May 19 07:41:14 debootstrap:  dependency problems - leaving unconfigured
May 19 07:41:14 debootstrap: Errors were encountered while processing:
May 19 07:41:14 debootstrap:  ifupdown
May 19 07:41:15 debootstrap: dpkg: dependency problems prevent configuration of 
ifupdown:
May 19 07:41:15 debootstrap:  netbase (5.0) breaks ifupdown (  0.7~rc1) and 
is installed.
May 19 07:41:15 debootstrap:   Version of ifupdown to be configured is 
0.7~alpha5+really0.6.16.
May 19 07:41:15 debootstrap: dpkg: error processing ifupdown (--configure):
May 19 07:41:15 debootstrap:  dependency problems - leaving unconfigured
May 19 07:41:16 debootstrap: Errors were encountered while processing:
May 19 07:41:16 debootstrap:  ifupdown
May 19 07:41:32 base-installer: error: exiting on error 
base-installer/debootstrap-failed
May 19 07:41:36 main-menu[167]: WARNING **: Configuring 'bootstrap-base' failed 
with error code 30
May 19 07:41:36 main-menu[167]: WARNING **: Menu item 'bootstrap-base' failed.





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

Bug#659818: dahdi-linux 2.5.0.1 won't build against Linux 3.2

[Gedalya]

Just tried the dahdi-source 2.6.1+dfsg-1 package currently in sid and it 
worked with no problem.

This bug should probably be marked as fixed?




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

Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen (also affects ext3 as of linux-image-3.1.0-1-amd64 et al)

[Gedalya]

notfound 637234 3.2.6-1
notfound 637234 2.6.32-41
thanks

Timo  all,

This has been a bug in the dom0 kernel. If I've been following this bug 
correctly, then the only thing about the 3.0+ kernels is that they have 
barriers enabled by default, which we then disable as a workaround. But 
this is supposed to work, and it was mishandled by the kernel in dom0. I 
therefore see no point in marking this bug as found in 3.0+ kernels used 
in domU's.


This bug was apparently fixed in 2.6.32-40 or 2.6.32-41, I waited for 
2.6.32-41 and now I'm running that kernel in my dom0. You have to 
upgrade your dom0 to the latest kernel. I now have various wheezy domU's 
with barriers enabled again, running with no issues.


Regards,

Gedalya


On 02/07/2012 05:17 AM, Timo Juhani Lindfors wrote:

package linux-2.6
notfound 637234 3.0.0-3
found 637234 3.1.0-1~experimental.1
found 637234 3.1.1-1
found 637234 3.1.8-2
found 637234 3.2.4-1
thanks

dom0


amd64 squeeze with
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-39) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 3 05:42:31 UTC 2011

config
--

name = 'lindi2'
vcpus = '4'
memory = '1024'
disk = [ 'file:/local/xen/lindi2/disk.img,xvda,w' ]
vif = [ 'mac=00:01:01:99:80:02' ]
on_crash = 'restart'

domU


amd64 wheezy with
Linux version 3.1.0-1-amd64 (Debian 3.1.0-1~experimental.1) (wa...@debian.org) 
(gcc version 4.6.1 (Debian 4.6.1-16) ) #1 SMP Thu Nov 3 19:35:59 UTC 2011

(also occurs with 3.1.1-1, 3.1.8-2 and 3.2.4-1 but listing the first
version where the bug occurs)

Using ext3 for rootfs. dmesg has

...
blkfront: barrier: empty write xvda op failed
blkfront: xvda: barrier or flush: disabled
end_request: I/O error, dev xvda, sector 16519664
end_request: I/O error, dev xvda, sector 16519664
...

Full dmesg attached.



workaround
==

Setting barrier=0 for / in fstab seems to help. Thanks Konrad for the
tip, now I can continue working :-)

Bug#605760: #613328 crashes when invoke pcmanfm twice

[Gedalya]

Also bug #605760 seems to be about the same exact thing.
When will someone pull 0.9.10 from upstream?




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