Bug#997130: marked as pending in acmetool

[Peter Colberg]

Control: tag -1 pending

Hello,

Bug #997130 in acmetool reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/acmetool/-/commit/51cb87026ab18000d161b359efce35eb59083e5c


Fix FTBFS due to signature verification error

Closes: #997130


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997130

Bug#954189: Upload approval for acmetool 0.2 in buster-backports

[Peter Colberg]

Hi Ralph,

On Thu, Aug 06, 2020 at 03:38:33PM -0700, Ralph Giles wrote:
> I wanted to request approval from the maintainer team to upload the
> acmetool 0.2.1-2 package currently in testing/unstable to buster-
> backports.

Please feel free to go ahead with backporting acmetool and needed
golang dependencies to buster. I recently moved the acmetool package
to the go-team, which you will need to join on salsa to push to its
git repository. Please let me know in case you have any questions.

Peter

Bug#899439: Bug #899439 in acmetool marked as pending

[Peter Colberg]

Control: tag -1 pending

Hello,

Bug #899439 in acmetool reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/letsencrypt-team/acmetool/commit/0e21a13bb9664445b779e8a67df5c164cea4e393


Update Maintainer address

Closes: #899439
Thanks: Lukas Schwaighofer



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/899439

Bug#853691: closing 853691

[Peter Colberg]

close 853691 7.0.0-10
thanks

Bug#861486: [Pkg-julia-devel] Bug#861486: Bug#861486: julia: FTBFS on mips64el (segmentation fault)

[Peter Colberg]

Hi Graham,

On Mon, May 01, 2017 at 01:53:43PM +0200, Graham Inggs wrote:
> Simply running, e.g. 'debian/shlibdeps pow', 10 or so times in a row
> is enough to get it to segfault.
> Unfortunately, it doesn't seem to happen when run in gdb.
> I don't know why this program [1], which is used to generate
> julia.links, would be failing randomly in this way (it seems to occur
> after the final 'printf') and only on this architecture.
> 
> [1] 
> https://anonscm.debian.org/cgit/pkg-julia/julia.git/tree/debian/shlibdeps.c

Since I don’t have access to mips64el at the moment:

Could you comment all lines and then successively uncomment to see
which line triggers the segfault?

You could also try querying a symbol in libm other than pow and see
whether that changes anything.

Regards,
Peter

Bug#844817: [Pkg-cgit-devel] Bug#844817: cgit: FTBFS: build-dependency not installable: libssl-dev

[Peter Colberg]

Control: reassign -1 apache2-dev

Reassigning this bug to be closed in the next upload of apache2.

https://bugs.debian.org/845033#21

Peter

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Hi Jonas,

Any chance you could upload the fixed ucommon version to unstable?

Otherwise, please let me know whether I should submit an NMU.

Regards,
Peter

Bug#817626: RFS: poppassd/1.8.5-4.1 [RC, NMU]

[Peter Colberg]

Control: -1 tags pending

Hi Adam,

I hope you are well. Following advice from the MIA team, I have
uploaded with the help of debian-mentors to the DELAYED/7 queue
a minimal NMU of poppassd that resolves #817626 [1].

Please let me know whether and how to proceed with the changes
proposed in #836008. In case I do not hear from you till the NMU is
accepted, I will take this as a signal that you are, at least for the
moment, too busy to take care of the package and request sponsorship
for poppassd/1.8.7-1. Before the transition freeze in four weeks, I
further plan to add a systemd unit as an alternative to inetd that
restricts the priviledges of poppassd to the necessary minimum.

Whenever you feel ready to work on Debian again, please let me know
and I will gladly return maintenance of poppasswd back to you.

Peter

[1] https://bugs.debian.org/839859

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Hi Jonas,

On Sun, Sep 11, 2016 at 09:21:22AM +0200, Jonas Smedegaard wrote:
> I will look at it tonight.
> 
> Thanks for nudging!

Thanks for uploading a new version to experimental. Since the builds
passed on all release architectures, could you upload to unstable?

Regards,
Peter

Bug#817626: src:poppassd: Co-maintain poppassd

[Peter Colberg]

On Wed, Sep 21, 2016 at 05:46:09PM -0400, Peter Colberg wrote:
> Please clone the updated package using
> 
>   gbp clone ssh://git.debian.org/git/collab-maint/poppassd.git

For verification, these are the current branch heads:

  git show-ref --heads

  6e26c876530625d4cdc3451bef921ce635887658 refs/heads/master
  db27d6addd476baf420d49f362b79b373462063e refs/heads/pristine-tar
  79da3cf634ebe761d494fcbbcf36a4da71379383 refs/heads/upstream

Please note that debian/copyright includes the following line:

  Files-Excluded: m4/* auto.sh

When you download a new tarball using uscan or gbp import-orig --uscan
in the future, this will automatically repack the orig tarball while
excluding the embedded files from the package autoconf-archive.

Peter

Bug#817626: src:poppassd: Co-maintain poppassd

[Peter Colberg]

Hi Adam,

With the stretch freeze getting close, I have imported the poppassd
history into a collab-maint git repository and updated the packaging
to fix #817626 and conform to Debian policy. Please note that I have
*not* added myself to Uploaders. If you wish to continue to maintain
the package on your own, that is perfectly fine with me.

This is the summary of the proposed changes:

  * New upstream version 1.8.7
  * Switch source format to 3.0 (quilt)
  * Use dh with autoreconf in debian/rules (Closes: #817626)
  * Build with hardening flags
  * Add machine-readable debian/copyright
  * Update Homepage field
  * Add Vcs-Git and Vcs-Browser fields
  * Update debian/watch
  * Run wrap-and-sort
  * Update Standards-Version to 3.9.8

Please clone the updated package using

  gbp clone ssh://git.debian.org/git/collab-maint/poppassd.git

Please inspect the changes to the previous version using, e.g.,

  git log -p --stat --decorate --reverse debian/1.8.5-4..master

I have compared the upstream source line-by-line with the former
patched Debian source. The patch for #287820 has been included
upstream, otherwise the upstream changes are cosmetic.

All you would need to do now is update the changelog with

  gbp dch --commit --release

and prepare a source-only upload and tag a new release with

  gbp buildpackage -S --git-tag

In case this is the first time you are using git-buildpackage, it is
good practice to push the debian/* git tag only after the upload has
been accepted. This allows further changes if the upload is rejected.

Thanks,
Peter

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Dear Debian VoIP team,

Could a DD review and upload the attached NMU for ucommon? I verified
that twinkle still works when libucommon8:amd64 is built with GCC 6.

Peter
>From d731868c2267e0462e6f727188b0253912bcec80 Mon Sep 17 00:00:00 2001
From: Peter Colberg <pe...@colberg.org>
Date: Sun, 11 Sep 2016 00:08:14 -0400
Subject: [PATCH] Update symbols file for GCC 6

---
 debian/changelog   |  7 
 debian/libucommon8.symbols | 91 +-
 2 files changed, 9 insertions(+), 89 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 562ab75..9587d8a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ucommon (7.0.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update symbols file for GCC 6. (Closes: #831211)
+
+ -- Peter Colberg <pe...@colberg.org>  Sun, 11 Sep 2016 00:08:01 -0400
+
 ucommon (7.0.0-6) unstable; urgency=medium
 
   * Use dh-autoreconf (not cdbs) to regenerate autotools.
diff --git a/debian/libucommon8.symbols b/debian/libucommon8.symbols
index 02ed398..76f46ba 100644
--- a/debian/libucommon8.symbols
+++ b/debian/libucommon8.symbols
@@ -888,10 +888,8 @@ libcommoncpp.so.8 libucommon8 #MINVER#
  _ZNK3ost9TimerPort10getElapsedEv@Base 7.0.0
  _ZNK3ost9TimerPort8getTimerEv@Base 7.0.0
  (optional=templinst)_ZNKSt5ctypeIcE8do_widenEc@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS5_S7_EERKS5_@Base 7.0.0
- (optional=templinst|arch=hppa sparc64)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZNSt6vectorIPN3ost13PersistObjectESaIS2_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS2_S4_EERKS2_@Base 7.0.0
- (optional=templinst|arch=hppa sparc64)_ZNSt6vectorIPN3ost13PersistObjectESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base 7.0.0
+ (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base 7.0.0
+ (optional=templinst)_ZNSt6vectorIPN3ost13PersistObjectESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base 7.0.0
  (optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 7.0.0
  (optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 7.0.0
  (optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 7.0.0
@@ -2524,32 +2522,6 @@ libucommon.so.8 libucommon8 #MINVER#
  (subst)_ZN7ucommon7keyfileC2E{size_t}@Base 7.0.0
  _ZN7ucommon7keyfileD0Ev@Base 7.0.0
  _ZN7ucommon7keyfileD1Ev@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE3b64EPKh{size_t}PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE3hexEPKh{size_t}PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE3setES2_PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE5value7destroyEv@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE5valueC1EPc{size_t}S2_PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE5valueC2EPc{size_t}S2_PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE5valueD0Ev@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE5valueD1Ev@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE6assignEPNS3_5valueE@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE6createE{size_t}PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE6expandEPPNS3_5valueE{size_t}@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEE7destroyEPNS3_5valueE@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEEC1ERKS3_@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEEC1ES2_PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEEC1Ev@Base 7.0.0
- (optional=templinst|subst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEEC1E{size_t}PNS_11TypeReleaseE@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEEC2ERKS3_@Base 7.0.0
- (optional=templinst|arch=!hppa !sparc64)_ZN7ucommon7typerefIPKcLZNS_12auto_releaseEEEC2ES2_PNS_11TypeReleaseE@Base 7.0.0
- (optional

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Hi Jonas,

Now that GCC 6 has been made default in unstable, could you upload
a new version of ucommon with an updated symbols file to prevent the
auto-removal of dependent packages from testing on 2016-09-02?

Regards,
Peter

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Dear Debian Release Team,

twinkle has been marked for autoremoval from testing on 2016-08-27 due
to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields
slight differences in the list of visible symbols.

How should this bug be dealt with? Is it not simply a matter of
waiting for GCC 6 to become default, uploading ucommon with an
updated symbols file and an ABI bump (if needed), and submitting
binNMUs for dependent packages?

If so, can this bug be downgraded to severity important until then?

Regards,
Peter

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Hi Lucas, Jonas,

twinkle has been marked for autoremoval from testing on 2016-08-27 due
to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields
slight differences in the list of visible symbols.

How should this bug be dealt with? Is it not simply a matter of
waiting for GCC 6 to become default, uploading ucommon with an
updated symbols file and an ABI bump (if needed), and submitting
binNMUs for dependent packages?

If so, can this bug be downgraded to severity important until then?

Regards,
Peter

Bug#831252: [Pkg-julia-devel] Bug#831252: julia: FTBFS: Tests failures

[Peter Colberg]

Hi Lucas,

On Thu, Jul 14, 2016 at 11:57:56AM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

I rebuilt julia successfully five times on my amd64 machine with sbuild.

> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/07/14/julia_0.4.6-1_unstable_gcc5.log

The test log is full of segmentation faults, which might indicate a
problem with the build machine. Does your instance have enough RAM?

Julia requires ~1 GB per process to run the test suite.

Regards,
Peter

Bug#829236: [Pkg-julia-devel] Bug#829236: utf8proc: FTBFS: line 16413: normalization failed for ? -> 配

[Peter Colberg]

On Fri, Jul 01, 2016 at 04:40:52PM +0200, Chris Lamb wrote:
>   test/normtest data/NormalizationTest.txt
>   line 16413: normalization failed for  -> 配

The test fails due to unicode-data having been updated to Unicode 9.0.

This has been resolved upstream but not released yet.

Peter

Bug#827405: cgit: update to version 1.0 fixes CVE-2016-2315 and CVE-2016-2324

[Peter Colberg]

Dear Debian Security Team,

I believe that cgit versions before 1.0 are affected by both
CVE-2016-2315 and CVE-2016-2324. I did not include the latter
when reporting this bug initially since it was not mentioned
in the release announcement for cgit 1.0.

Regards,
Peter

Bug#827405: cgit: update to version 1.0 fixes CVE-2016-2315

[Peter Colberg]

Package: cgit
Version: 0.12.0.git2.7.0-1
Severity: grave
Tags: security upstream
Justification: user security hole

Dear Maintainer,

The above version of cgit embeds git 2.7.0, which is affected
by CVE-2016-2315 [1]. The update to cgit 1.0 [2, 3] includes
git 2.8.3, which fixes the issue.

[1] https://security-tracker.debian.org/tracker/CVE-2016-2315
[2] http://article.gmane.org/gmane.comp.version-control.cgit/3076
[2] https://bugs.debian.org/826764

Regards,
Peter

Bug#824946: twinkle: module "QtQuick" is not installed

[Peter Colberg]

Package: twinkle
Version: 1:1.9.0+git20160321.0.64a0816+dfsg-1
Severity: serious

After upgrading to the above version, twinkle fails to start:

Language name: "en"
qrc:/qml/osd.qml:1:1: module "QtQuick" is not installed
QObject::connect: Cannot connect (null)::clicked() to OSD::onHangupClicked()
QObject::connect: Cannot connect (null)::clicked() to OSD::onMuteClicked()
QObject::connect: Cannot connect (null)::moved() to OSD::saveState()
qrc:/qml/incoming_call.qml:1:1: module "QtQuick" is not installed
QObject::connect: Cannot connect (null)::clicked() to 
IncomingCallPopup::onAnswerClicked()
QObject::connect: Cannot connect (null)::clicked() to 
IncomingCallPopup::onRejectClicked()
QObject::connect: Cannot connect (null)::moved() to 
IncomingCallPopup::saveState()
zsh: segmentation fault  twinkle

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 3.16.0-4-armmp-lpae (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages twinkle depends on:
ii  libasound2  1.1.0-1
ii  libc6   2.22-7
ii  libccrtp2v5 2.0.9-2.2+b2
ii  libgcc1 1:6.1.1-3
ii  libgsm1 1.0.13-4+b1
ii  libmagic1   1:5.25-2
ii  libqt5core5a5.5.1+dfsg-16+b1
ii  libqt5gui5  5.5.1+dfsg-16+b1
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libqt5widgets5  5.5.1+dfsg-16+b1
ii  libreadline66.3-8+b4
ii  libsndfile1 1.0.25-10
ii  libspeex1   1.2~rc1.2-1
ii  libspeexdsp11.2~rc1.2-1
ii  libstdc++6  6.1.1-3
ii  libucommon8 7.0.0-5
ii  libxml2 2.9.3+dfsg1-1

twinkle recommends no packages.

twinkle suggests no packages.

-- no debconf information

Bug#821022: julia is marked for autoremoval from testing

[Peter Colberg]

Hi Sylvestre,

Julia has been marked for autoremoval from testing on 2016-06-06 due
to Debian bug #821022 on python-lldb-3.8. Could you upload a fixed
version using the patch [1] provided by Pablo Oliveira?

[1] https://bugs.debian.org/821022#20

Regards,
Peter

Bug#821234: twinkle: FTBFS: error: 'ucommon::Digest::Digest(const ucommon::Digest&)' is private

[Peter Colberg]

Hi Chris, Logan,

On Sat, Apr 16, 2016 at 11:24:16PM +0100, Chris Lamb wrote:
> twinkle fails to build from source in unstable/amd64:

Thank you for reporting the FTBFS and pointing to the upstream fix.

I am still hoping that the upstream maintainer of twinkle will tag
a new release soon, which further fixes compatibility with Qt 5.6:

https://github.com/LubosD/twinkle/issues/64

Regards,
Peter

Bug#816980: [Pkg-julia-devel] Bug#816980: julia: FTBFS in testing

[Peter Colberg]

Hi Santiago,

On Mon, Apr 25, 2016 at 09:24:51PM +0200, Santiago Vila wrote:
> Question: Why should this package be the only one which does not work
> with eatmydata? Are there good reasons for the build system to be
> incompatible with eatmydata? Could julia be made compatible with
> eatmydaya again? I'm building a lot of packages and this is a real
> time saver.

I had the same issue with eatmydata causing segmentation faults:

https://github.com/JuliaLang/julia/issues/14033

You can still use eatmydata by diverting dpkg inside the sbuild chroot

dpkg-divert --rename /usr/bin/dpkg

and putting the following script in its place:

#!/bin/sh
exec /usr/bin/eatmydata /usr/bin/dpkg.distrib "$@"

Regards,
Peter

Bug#820220: [Pkg-julia-devel] Bug#820220: julia: FTBFS on armel/armhf

[Peter Colberg]

Hi Graham,

julia 0.4.5-3 FTBFS on armel due to an outdated llvm-3.8 package:

https://buildd.debian.org/status/fetch.php?pkg=julia=armel=0.4.5-3=1461030510

I think it would be a good idea to retain the version constraint
llvm-3.8-dev (>= 1:3.8~+rc1) that was dropped in commit 17796f1.

Regards,
Peter

Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

[Peter Colberg]

On Fri, Apr 08, 2016 at 09:55:02PM +0200, Graham Inggs wrote:
> On 8 April 2016 at 21:16, Emilio Pozuelo Monfort  wrote:
> > Why did you switch to 3.8? The default in unstable is 3.6 and in 
> > experimental is
> > 3.7.
> 
> I understood there were severe performance regressions with Julia on
> LLVM > 3.3 that were only fixed in 3.8.

The reason for switching to LLVM 3.8 was the abysmal performance
of LLVM 3.7 on i386, and complete failure of LLVM 3.6 or earlier.

https://github.com/JuliaLang/julia/issues/14191

Peter

Bug#820220: [Pkg-julia-devel] Bug#820220: julia: FTBFS on armel/armhf

[Peter Colberg]

On Wed, Apr 06, 2016 at 07:30:56PM +0200, Emilio Pozuelo Monfort wrote:
> Source: julia
> Version: 0.4.5-1
> Severity: serious
> 
> Your package failed to build on armel and armhf:
> 
> https://buildd.debian.org/status/package.php?p=julia

Graham, should we remove these two archs from testing for the time
being as you suggested? From the amount of open bugs for 0.5.0,
I am guessing the release will be delayed till northern summer,
which would be the same time as the 0.4.0 release last year.

https://github.com/JuliaLang/julia/milestones

Peter

Bug#813263: ucommon: FTBFS: devlibs error: There is no package matching [libgnutls30-dev] and noone provides it,

[Peter Colberg]

Hi Jonas,

I received a notice that the package twinkle is marked for autoremoval
from testing on 2016-03-21 due to this bug. Could you upload the
ucommon version in experimental to unstable to close this bug?

Regards,
Peter

Bug#746054: Sponsored upload of twinkle/1:1.9.0+dfsg-2

[Peter Colberg]

Hi Clint,

Could you sponsor one more upload of twinkle?

I was not aware at first that the OpenSSL license issue with
libzrtpcpp would prevent twinkle from entering testing.

If yes, could you upload only the source package so that we have
a published buildd log for amd64 as well? Please pull from the git
repository for twinkle/1:1.9.0+dfsg-2 [1].

[1] https://anonscm.debian.org/cgit/users/pc-guest/twinkle.git

(I have not received a reply from pkg-voip-maintainers yet.)

Regards,
Peter

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Peter Colberg]

Package: systemd
Version: 215-11
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

After upgrading to jessie from wheezy, I noticed that some of the
system logs experience corruption when rebooting the system.

After rebooting the system using the command ‘reboot’ or ‘systemctl
reboot’, some log files such as /var/log/syslog contain a hole with
nil bytes:

  Feb 11 14:48:22 himeji systemd[20266]: Reached target Sockets.
  Feb 11 14:48:22 himeji systemd[20266]: Starting Basic System.
  Feb 11 14:48:22 himeji systemd[20266]: Reached target Basic System.
  Feb 11 14:48:22 himeji systemd[20266]: Starting Default.
  Feb 11 14:48:22 himeji systemd[20266]: Reached target Default.
  Feb 11 14:48:22 himeji systemd[20266]: Startup finished in 3ms.
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb 11 14:54:55 himeji 
rsyslogd: [origin software=rsyslogd swVersion=8.4.2 x-pid=539 
x-info=http://www.rsyslog.com;] start
  Feb 11 14:54:55 himeji systemd-fsck[137]: /dev/vda3: clean, 81576/2621440 
files, 889144/10485760 blocks
  Feb 11 14:54:55 himeji systemd-fsck[233]: /dev/vda4: clean, 2187/3670016 
files, 1858872/14679547 blocks
  Feb 11 14:54:55 himeji networking[245]: Configuring network 
interfaces...Waiting for DAD... Done
  Feb 11 14:54:55 himeji networking[245]: done.

This happened with log files managed by rsyslog as well as one log
file not managed by rsyslog. I assume this issue is not related to
logging, but rather manifests itself in any files that are modified
right before the reboot, e.g. due to daemons logging a shutdown
notice.

I could reproduce this issue with three machines that are virtualized
with qemu-kvm. On the other hand, I did not see this issue with two
physical machines. All of these are running the above version of
systemd.

Further, I found a work-around to avoid data corruption as seen in the
log files. If the system is rebooted through an external ACPI event
(sent to the qemu-kvm process), /var/log/syslog is not corrupted:

  Feb 11 18:17:03 himeji systemd[4412]: Reached target Default.
  Feb 11 18:17:03 himeji systemd[4412]: Startup finished in 4ms.
  Feb 11 18:17:04 himeji systemd[4412]: Stopping Default.
  Feb 11 18:17:04 himeji systemd[4412]: Stopped target Default.
  Feb 11 18:17:04 himeji systemd[4412]: Stopping Basic System.
  Feb 11 

Bug#775705: nftables: init script fails due to flush ruleset

[Peter Colberg]

Package: nftables
Version: 0.4-2
Severity: serious

Dear Maintainer,

The init script shipped with the package fails with this error:

/etc/nftables.conf:3:1-14: Error: Could not process rule: Address family not 
supported by protocol
flush ruleset
^^

The reason is that “flush ruleset” requires kernel version 3.18 or later,
as hinted in the release notes for nftables 0.4, while Debian ships 3.16.

http://lists.netfilter.org/pipermail/netfilter-announce/2014/000211.html

Maybe this particular feature could be backported to 3.16?

Regards,
Peter

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages nftables depends on:
ii  init-system-helpers  1.22
ii  libc62.19-13
ii  libgmp10 2:6.0.0+dfsg-6
ii  libmnl0  1.0.3-5
ii  libnftnl01.0.3-4
ii  libreadline6 6.3-8+b3

nftables recommends no packages.

nftables 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#542102: mpd: audio skips once per second

[Peter Colberg]

On Wed, Sep 02, 2009 at 08:27:26AM -0400, Decklin Foster wrote:
 Excerpts from Peter Colberg's message of Tue Aug 18 13:45:00 -0400 2009:
  On Tue, Aug 18, 2009 at 06:43:56AM +0200, Max Kellermann wrote:
   On 2009/08/18 01:51, Peter Colberg pe...@colberg.org wrote:
Reverting commit 7133f56 fixes the audio skips :-).
 
 Can you confirm if this is fixed in 0.15.3-1? Thanks.

At the moment, I do not have access to the amd64+alsa+sblive box
on which mpd 0.15.2-1 exhibits the bug. I will be able to test
0.15.3-1 on that system next week.

Regards,
Peter



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

Bug#542102: mpd: audio skips once per second

[Peter Colberg]

On Tue, Aug 18, 2009 at 06:43:56AM +0200, Max Kellermann wrote:
 On 2009/08/18 01:51, Peter Colberg pe...@colberg.org wrote:
  Reverting commit 7133f56 fixes the audio skips :-).
 
 Thanks for the bisect!
 
 I suspect this is an uninitialized variable.  Please try two
 approaches at working around it:
 
 1. mpc toggle twice (enter pause, leave pause) - this should
initialize the pause flag retroactively
 
 2. try the attached patch

Both the workaround and the patch resolve the skipping playback.

(Btw, the release-0.15.2 tag is missing in the git repository.)

Regards,
Peter



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

Bug#542102: mpd: audio skips once per second

[Peter Colberg]

Package: mpd
Version: 0.15.2-1
Severity: grave
Justification: renders package unusable

Hi,

with the new version of mpd, I experience skipping audio about once per
second, where a skip could be described as a crackling noise followed by
a fast forward of a fraction of a second. I verified this behaviour for
FLAC, Ogg and MP3 files.

A downgrade to the previous version 0.15.1-1 restores smooth playback.


My audio output section of the mpd config reads as follows:

audio_output {
typealsa
nameMy ALSA Device
device  hw:0,0# optional
format  44100:16:2# optional
mixer_devicedefault   # optional
mixer_control   Master# optional
mixer_index 0 # optional
}

ALSA uses the following card as shown by lspci:

00:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)


Regards,
Peter

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

Kernel: Linux 2.6.30-maia (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mpd depends on:
ii  adduser  3.110   add and remove users and groups
ii  libao2   0.8.8-5 Cross Platform Audio Output Librar
ii  libasound2   1.0.20-3shared library for ALSA applicatio
ii  libaudiofile00.2.6-7 Open-source version of SGI's audio
ii  libavcodec52 4:0.5+svn20090609-2 ffmpeg codec library
ii  libavformat524:0.5+svn20090609-2 ffmpeg file format library
ii  libavutil49  4:0.5+svn20090609-2 ffmpeg utility library
ii  libc62.9-25  GNU C Library: Shared libraries
ii  libcue1  1.3.0-1 CUE Sheet Parser Library
ii  libcurl3-gnutls  7.19.5-1Multi-protocol file transfer libra
ii  libfaad0 2.6.1-3.1   freeware Advanced Audio Decoder - 
ii  libflac8 1.2.1-2+b1  Free Lossless Audio Codec - runtim
ii  libgcc1  1:4.4.1-2   GCC support library
ii  libglib2.0-0 2.20.4-1The GLib library of C routines
ii  libid3tag0   0.15.1b-10  ID3 tag reading library from the M
ii  libjack0 0.116.2+svn3592-2   JACK Audio Connection Kit (librari
ii  libmad0  0.15.1b-4   MPEG audio decoder library
ii  libmms0  0.4-2   MMS stream protocol library - shar
ii  libmpcdec3   1:1.2.2-2.1 Musepack (MPC) format library
ii  libogg0  1.1.4~dfsg-1Ogg bitstream library
ii  libpulse00.9.15-4.1  PulseAudio client libraries
ii  libresid-builder0c2a 2.1.1-7 SID chip emulation class based on 
ii  libsamplerate0   0.1.7-2 audio rate conversion library
ii  libshout32.2.2-5+b1  MP3/Ogg Vorbis broadcast streaming
ii  libsidplay2  2.1.1-7 SID (MOS 6581) emulation library
ii  libsqlite3-0 3.6.17-2SQLite 3 shared library
ii  libstdc++6   4.4.1-2 The GNU Standard C++ Library v3
ii  libvorbis0a  1.2.0.dfsg-6The Vorbis General Audio Compressi
ii  libvorbisenc21.2.0.dfsg-6The Vorbis General Audio Compressi
ii  libvorbisfile3   1.2.0.dfsg-6The Vorbis General Audio Compressi
ii  libwavpack1  4.50.1-1an audio codec (lossy and lossless

mpd recommends no packages.

Versions of packages mpd suggests:
pn  avahi-daemon  none (no description available)
ii  glurp [mpd-client]0.11.6-4   gtk2.4+ frontend to the Music Play
ii  gmpc [mpd-client] 0.18.98-1  Gnome Music Player Client (graphic
pn  icecast2  none (no description available)
ii  mpc [mpd-client]  0.16-1 A command-line tool to interface M
ii  ncmpc [mpd-client]0.14-1 ncurses-based audio player
pn  pulseaudionone (no description available)
ii  sonata [mpd-client]   1.6.2-1GTK+ client for the Music Player D

-- debconf information:
  mpd/playlist_directory: /var/lib/mpd/playlists
* mpd/systemwide: false
  mpd/music_directory: /usr/share/mpd/music



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

Bug#542102: mpd: audio skips once per second

[Peter Colberg]

On Mon, Aug 17, 2009 at 10:36:41PM +0200, Max Kellermann wrote:
 On 2009/08/17 22:15, Peter Colberg pe...@colberg.org wrote:
  with the new version of mpd, I experience skipping audio about once per
  second, where a skip could be described as a crackling noise followed by
  a fast forward of a fraction of a second. I verified this behaviour for
  FLAC, Ogg and MP3 files.
 
 Please enable verbose mode and watch the log file for related
 messages.

With log_level = verbose, restarting mpd and thereby resuming playback:

Aug 17 22:41 : state_file: Saving state file
Aug 17 22:41 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 01 - So What.flac
Aug 17 22:41 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 02 - Freddie Freeloader.flac
Aug 17 22:41 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 03 - Blue In Green.flac
Aug 17 22:41 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 04 - All Blues.flac
Aug 17 22:41 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 05 - Flamenco Sketches.flac
Aug 17 22:41 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 06 - Flamenco Sketches (Alternate Take).flac
Aug 17 22:41 : playlist: play 0:Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 01 - So What.flac
Aug 17 22:41 : decoder: audio_format=44100:16:2, seekable=true
Aug 17 22:41 : alsa: default period_time = buffer_time/4 = 371519/4 = 92879
Aug 17 22:41 : alsa: buffer_size=16384 period_size=4096
Aug 17 22:41 : output: opened plugin=alsa name=My ALSA Device 
audio_format=44100:16:2
Aug 17 22:41 : playlist: queue song 1:Miles Davis/Kind of Blue 
(1997)/Miles Davis - Kind of Blue - 02 - Freddie Freeloader.flac

(error.log remains empty.)

 Then try switching to an OSS output, and see if the same
 problem occurs.

A restart of mpd results in the following messages:

Aug 17 22:46 : output: closed plugin=alsa name=My ALSA Device
Aug 17 22:46 : listen: listen_global_finish called
Aug 17 22:46 : db_finish took 0.00 seconds
Aug 17 22:46 : state_file: Saving state file
Aug 17 22:46 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 01 - So What.flac
Aug 17 22:46 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 02 - Freddie Freeloader.flac
Aug 17 22:46 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 03 - Blue In Green.flac
Aug 17 22:46 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 04 - All Blues.flac
Aug 17 22:46 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 05 - Flamenco Sketches.flac
Aug 17 22:46 : database: get song: Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 06 - Flamenco Sketches (Alternate Take).flac
Aug 17 22:46 : playlist: play 0:Miles Davis/Kind of Blue (1997)/Miles 
Davis - Kind of Blue - 01 - So What.flac
Aug 17 22:46 : decoder: audio_format=44100:16:2, seekable=true
Aug 17 22:46 : output: opened plugin=oss name=My OSS Device 
audio_format=44100:16:2
Aug 17 22:46 : playlist: queue song 1:Miles Davis/Kind of Blue 
(1997)/Miles Davis - Kind of Blue - 02 - Freddie Freeloader.flac
Aug 17 22:46 : decoder: audio_format=44100:16:2, seekable=true
Aug 17 22:46 : playlist: queue song 2:Miles Davis/Kind of Blue 
(1997)/Miles Davis - Kind of Blue - 03 - Blue In Green.flac


During playback no messages are printed.

Peter



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

Bug#542102: mpd: audio skips once per second

[Peter Colberg]

On Mon, Aug 17, 2009 at 11:20:22PM +0200, Max Kellermann wrote:
 On 2009/08/17 22:53, Peter Colberg pe...@colberg.org wrote:
  Aug 17 22:41 : playlist: queue song 1:Miles Davis/Kind of Blue 
  (1997)/Miles Davis - Kind of Blue - 02 - Freddie Freeloader.flac
 
 Nothing to see here, no underruns.. :(
 
   Then try switching to an OSS output, and see if the same
   problem occurs.
  
  A restart of mpd results in the following messages:
 
 So does the problem occur with OSS?

Sorry, forgot to mention: yes, it also occurs with OSS.

 Can you make a git bisect from release-0.15.1 to release-0.15.2 to
 isolate the commit which broke playback for you?  It's very difficult
 for me to find the cause, because I don't hear that problem over here.

Ok, I will hopefully report back with the faulty commit.

Peter



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

Bug#542102: mpd: audio skips once per second

[Peter Colberg]

On Mon, Aug 17, 2009 at 11:20:22PM +0200, Max Kellermann wrote:
 Can you make a git bisect from release-0.15.1 to release-0.15.2 to
 isolate the commit which broke playback for you?  It's very difficult
 for me to find the cause, because I don't hear that problem over here.

This took longer than expected…

git bisect start
# bad: [5715534b530cfed0d6650b0fb34cfcb17da4088b] mpd version 0.15.2
git bisect bad 5715534b530cfed0d6650b0fb34cfcb17da4088b
# good: [d7bad6ae020ffabfd5d2ae9d2ce723e67e999077] mpd version 0.15.1
git bisect good d7bad6ae020ffabfd5d2ae9d2ce723e67e999077
# good: [cf1fd2b0da4be4675ddb16c5421d949a0e923b20] decoder/flac: return 
early from flac_find_float_comment()
git bisect good cf1fd2b0da4be4675ddb16c5421d949a0e923b20
# good: [1c4f407a6db4c4795bbbc354f5cf311762fb8e33] decoder/flac: don't 
allocate cuesheet twice (memleak)
git bisect good 1c4f407a6db4c4795bbbc354f5cf311762fb8e33
# good: [79beda2bb0505758bb6a32cae6feb3215733] directory: free empty 
directories after removing them (memleak)
git bisect good 79beda2bb0505758bb6a32cae6feb3215733
# bad: [f38ce5408b5d0126b8cfe730c91d5203ee59a987] output/shout: minimize 
the unpause latency
git bisect bad f38ce5408b5d0126b8cfe730c91d5203ee59a987
# bad: [7133f560ec24c90671a40c9f9bc9cea6eb31cc17] output: fixed shout stuck 
pause bug
git bisect bad 7133f560ec24c90671a40c9f9bc9cea6eb31cc17


The commit which causes skipping audio is:

commit 7133f560ec24c90671a40c9f9bc9cea6eb31cc17
Author: Max Kellermann m...@duempel.org
Date:   Fri Aug 14 11:52:12 2009 +0200

output: fixed shout stuck pause bug

Explicitly make the output thread leave the ao_pause() loop.  This
patch is a workaround, and the pause flag is not managed in a
thread-safe way, but that's good enough for now.


I had to do two complete bisects as the bug turned out to randomly
appear and disappear on each execution of mpd. The second round of git
bisect, however, revealed that all versions  7133f56 were definitly
good, and all versions = 7133f56 produced skipping playback on some
executions of mpd and smooth playback on others.

Reverting commit 7133f56 fixes the audio skips :-).

Čau,
Peter



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

Bug#392943: wmaker: Broken keyboard shortcuts with new default theme

[Peter Colberg]

Hello Gürkan,

On Sun, Oct 15, 2006 at 03:39:26AM +0200, Gürkan Sengün wrote:
 I disagree with your grave severity. The software is perfectly usable 
 without

Yes, the severity I picked might be a bit out of proportion.
Please feel free to downgrade it to a sensible choice.

 the so called standard configuration that you say is default by 
 Window Maker.

Maybe I should clarify as to what I meant with default configuration:
The global configuration as shipped with the Debian package, not the
unaltered upstream one.


 After an initial shock over the new default theme (which this bug 
 does not 
 mean to put in question), I found the WindowMaker keyboard shortcuts, 
 for 
 example for switching workspaces, not working at all.
 
 are you sure they work if you take the upstream tarball and build it?
 you can set them in WPrefs, the 5th icon from the right.

I did not consider building wmaker from pristine upstream upstream
source or in fact any source. This bug simply means to compare the
previous Debian package version with the current one.

After your suggestion, I tried with a fresh user account and found the
same behaviour, namely missing keyboard bindings. For clarification,
I attached the global and a pristine user configuration.


It is of course very easy for a user to assign keyboard bindings with
WPref or wmakerconf or by any other means, but isn't this exactly the
purpose of a default configuration, i.e. to provide sane defaults
for all configuration options needed for proper usage of a package?


The current Debian config should really include all the previous
config options (that is, the missing options as found in the file
'debian/WindowMaker.default' in source package version 0.92.0-5.3),
while keeping the new NeXTstep theme.

(Regarding the theme: You are absolutely right, my comment on the
previous and the current theme was absolutely subjective, and not
meant to offend anybody.)

Regards,
Peter
{
  LargeDisplayFont = -*-helvetica-bold-r-normal-*-24-*-*-*-*-*-*-*;
  HighlightColor = white;
  FTitleColor = white;
  MenuTextFont = -*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  WorkspaceBack = (
spixmap,
/usr/share/WindowMaker/Backgrounds/debian.tiff,
gray20
  );
  UTitleBack = (solid, rgb:aa/aa/aa);
  IconTitleFont = -*-helvetica-bold-r-normal-*-9-*-*-*-*-*-*-*;
  PTitleBack = (solid, gray40);
  WindowTitleFont = -*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  UTitleColor = black;
  ClipTitleFont = Verdana:bold:pixelsize=10;
  MenuDisabledColor = gray40;
  MenuStyle = normal;
  MenuTextBack = (solid, rgb:aa/aa/aa);
  PTitleColor = white;
  IconBack = (dgradient, rgb:a6/a6/b6, rgb:51/55/61);
  DisplayFont = -*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  MenuTitleBack = (solid, black);
  FTitleBack = (solid, black);
  TitleJustify = center;
  CClipTitleColor = gray20;
  ResizebarBack = (solid, rgb:aa/aa/aa);
  MenuTextColor = black;
  ClipTitleColor = black;
  IconTitleBack = black;
  HighlightTextColor = black;
  IconTitleColor = white;
  MenuTitleFont = -*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  MenuTitleColor = white;
}
{
  FTitleColor = white;
  MenuTitleBack = (solid, black);
  MenuDisabledColor = gray40;
  IconTitleBack = black;
  FTitleBack = (solid, black);
  ClipTitleFont = Verdana:bold:pixelsize=10;
  ClipTitleColor = black;
  IconTitleFont = 
helvetica:bold:pixelsize=9:xlfd=-*-helvetica-bold-r-normal-*-9-*-*-*-*-*-*-*;
  HighlightColor = white;
  WindowTitleFont = 
helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  MenuTextBack = (solid, rgb:aa/aa/aa);
  LargeDisplayFont = 
helvetica:bold:pixelsize=24:xlfd=-*-helvetica-bold-r-normal-*-24-*-*-*-*-*-*-*;
  CClipTitleColor = gray20;
  MenuStyle = normal;
  ResizebarBack = (solid, rgb:aa/aa/aa);
  DisplayFont = 
helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  IconTitleColor = white;
  TitleJustify = center;
  MenuTextColor = black;
  PTitleBack = (solid, gray40);
  IconBack = (dgradient, rgb:a6/a6/b6, rgb:51/55/61);
  MenuTitleColor = white;
  UTitleColor = black;
  MenuTitleFont = 
helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  UTitleBack = (solid, rgb:aa/aa/aa);
  PTitleColor = white;
  MenuTextFont = 
helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*;
  WorkspaceBack = (spixmap, /usr/share/WindowMaker/Backgrounds/debian.tiff, 
gray20);
  HighlightTextColor = black;
}

Bug#392943: wmaker: Broken keyboard shortcuts with new default theme

[Peter Colberg]

Package: wmaker
Version: 0.92.0-6
Severity: grave
Justification: renders package unusable

After an initial shock over the new default theme (which this bug does
not mean to put in question), I found the WindowMaker keyboard
shortcuts, for example for switching workspaces, not working at all.

This does not come as a surprise, given that most configuration options
have vanished in '/etc/Defaults/WindowMaker'.

Please revert to the previous, working default configuration.

Regards,
Peter

p.s. On a side note, why is the wmaker package not allowed to ship with
a Debian-inspired theme by default (see bug #286344)? As a default, the
Debian theme looked much better than the ugly NeXTSTEP theme found in
most other distributions :-).


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (400, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-maia
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages wmaker depends on:
ii  cpp  4:4.1.1-11  The GNU C preprocessor (cpp)
ii  libc62.3.6.ds1-6 GNU C Library: Shared libraries
ii  libfontconfig1   2.4.1-2 generic font configuration library
ii  libwraster3  0.92.0-6Shared libraries of Window Maker r
ii  libx11-6 2:1.0.3-1   X11 client-side library
ii  libxext6 1:1.0.1-2   X11 miscellaneous extension librar
ii  libxft2  2.1.8.2-8   FreeType-based font drawing librar
ii  libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library

wmaker recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#386347: [Pkg-sysvinit-devel] Bug#386347: initscripts 2.86.ds1-18 didn't fix my boot problem

[Peter Colberg]

Hi,

after fully recovering from the update-rc.d breakage, I also still have
trouble booting with sysvinit version 2.86.ds1-18. Downgrading to
2.86.ds1-15 solves the problem.

Upon trying to boot an LVM on root system, with a custom kernel and an
initrd image residing on a small boot partition, I receive an fsck
error message as follows below. I have attached dumps acquired from the
rescue shell of /proc/mdstat, /proc/mounts, my fstab as well as the
output of fdisk, lvdisplay, vgdisplay and mount in order to provide
some detail on my system.

I hope this will help resolve the issue in some way.

Regards,
Peter


==
Switching root ...
INIT: version 2.86 booting
Setting hostname to 'maia' ...done.
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...eth1394: eth2: IEEE-1394 IPv4 over 1394
 Ethernet (fw-host0)
done.
Setting parameters of disc: (none).
Activating swap:swapon: unable to open loop device /dev/loop6
 failed!
* Files under mount point '/tmp' will be hidden.
Will now check root file system: fsck 1.39 (29-May-2006)
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a rootdev -C0 /dev/vg/root
Usage: fsck.ext3 [-panyrcdfvstDFSV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-I|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
 -p   Automatic repair (no questions)
 -n   Make no changes to the filesystem
 -y   Assume yes to all questions
 -c   Check for bad blocks and add them to badblock list
 -f   Force checking even if filesystem is marked clean
 -v   Be verbose
 -b superblockUse alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal  Set location of the external journal
 -l bad_blocks_file   Add to badblocks list
 -L bad_blocks_file   Set badblocks list
fsck died with exit status 16
 failed!
* An automatic file system check (fsck) of the root filesystem failed.
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
* The root filesystem is currently mounted in read-only mode.
A maintainance shell will now be started.
After performing system maintenance, press CONTROL-D
to terminate the maintenance shell and restart the system.
Give root password for maintenance
(or type Control-D to continue):



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (400, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-maia
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages sysvinit depends on:
hi  initscripts  2.86.ds1-18 Scripts for initializing and shutt
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  libselinux1  1.30.27-2   SELinux shared libraries
ii  libsepol11.12.26-1   Security Enhanced Linux policy lib
hi  sysv-rc  2.86.ds1-18 System-V-like runlevel change mech

sysvinit recommends no packages.

-- no debconf information

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1  31  248976   fd  Linux raid autodetect
/dev/sda2  32   19457   1560393455  Extended
/dev/sda5  32   19457   156039313+  fd  Linux raid autodetect

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1   1  31  248976   fd  Linux raid autodetect
/dev/sdb2  32   19457   1560393455  Extended
/dev/sdb5  32   19457   156039313+  fd  Linux raid autodetect
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
/dev/vg/root/   ext3defaults,errors=remount-ro 01
/dev/md0/boot   ext3defaults0   2
/dev/vg/tmp /tmpext3defaults0   2
/dev/vg/swapnoneswapsw,loop=/dev/loop6,encryption=AES256
0   0
/dev/vg/home/home   ext3defaults0   2
/dev/cdrom  /media/cdromiso9660 ro,user,noauto  0   0
/dev/dvd/media/dvd  iso9660 ro,user,noauto  0   0
/dev/dvdrw  /media/dvdrwiso9660 ro,user,noauto  0   0
/dev/fd0/media/floppy   autorw,user,noauto  0