Bug#824900: iroffer-dinoex packaging : some more checks

[Frederic Bonnard]

Hi Weilu,

here are some other remarks on your packaging :

- d/copyright :
 * src/strnatcmp.* : looks more like zlib/libpng than MIT
 * dtd/iroffer-model-10.mod : this one is not GPL-2 with OpenSSL exception
 * missing copyright :
   o src/dinoex_curl.c : from curl tool_cb_hdr.c, Copyright (C) 1998 - 2011, 
Daniel Stenberg
 * Not sure you can extend the copyright period from what is actually in the
   files : d/copyright : "Copyright: 2000-2016 Dirk Meyer"
   You may only merge
   : https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#fields
 * btw, could you confirm the false positive lintian
   "unused-file-paragraph-in-dep5-copyright" ?
   If so could you just re-order paragraphs with wildcards from more general to
   less, that'll also ease reading of the file :
   o put 1st : Files: *
   o then: Files: src/upnp.* debian/*
   o all others
   I'll reopen #776796 if you confirm that (lintian 2.5.47 here)
- d/control : I can't find the link anymore, but I think that the iroffer
  package should declare the same Conflicts/Replaces relationship with 
iroffer-dinoex. 
- d/patches : 
  * did you pushed them upstream ?
  * remove # lines in the DEP3 header if not filled upstream or if done
add "Bug: "
- wrap-and-sort can help tidying some d/ files (minor but this is a tip)
- as a general advice, try to fix all lintians >= Informational : make a patch
  for typos and submit upstream.

Thanks for the work, there was much improvements since the 1st draft.

F.

Bug#839567: rake does not work with jruby

[Helmut Grohne]

Package: rake,jruby
Severity: serious
Justification: policy 3.5
User: helm...@debian.org
Usertags: rebootstrap

Hi,

Please consider the following interaction with a fresh sid chroot:

# apt-get install -y --no-install-recommends jruby
...
# apt-get install --no-install-recommends rake
# rake
-bash: /usr/bin/rake: /usr/bin/ruby: bad interpreter: No such file or directory
#

rake declares a dependency on ruby | ruby-interpreter. jruby declares
that it provides ruby-interpreter. It seems that rake expects
/usr/bin/ruby to be available, but jruby does not contain such a file
nor has a maintainer script that would create one (via alternatives or
other means).

Thus this looks like a broken contract on the meaning of
ruby-interpreter. I believe we have the following options to move
forward:

1. rake removes the ruby-interpreter alternative acknowledging that
   ruby-interpreter does not mean to include /usr/bin/ruby.
2. jruby removes the provides on ruby-interpreter acknowledging that
   ruby-interpreter should provide /usr/bin/ruby.
3. jruby instantiates /usr/bin/ruby as it is required for providing
   ruby-interpreter.

This bug was found by inspecting a valid installation set for ruby:i386
on an amd64 system generated by dose3. Choosing option 1 or 2 will mean
that ruby stops being installable for foreign architectures unless rake
annotates its ruby dependency with :any (ruby is m-a:allowed already).

Helmut

Bug#839544: RFS: btrfs-progs/4.7.3-1~bpo8+1

[Gianfranco Costamagna]

Hi, wonderful!

sponsored,

G.

Bug#811857: fixed in synaptic 0.83+nmu1

[Olly Betts]

On Sun, Oct 02, 2016 at 12:33:42AM -0400, Jeremy Bicha wrote:
> Olly, thanks for fixing this bug.
> 
> Since Ubuntu 16.10 has gcc 6 too, the patch should also be added to
> 00list.Ubuntu like this:

I think that's a job for the package's maintainer (mvo) - AFAICS the NMU
rules don't allow me to upload a change to fix something which isn't even a
bug in Debian.

Also, I NMUed it to unblock a transition, so now isn't the time for another
NMU even if I could, as it would delay that transition completing.

Cheers,
Olly

Bug#839385: marked as done (UDD: incorrect affects_ for fixed bugs)

[Sebastiaan Couwenberg]

Paul Wise wrote:
> This seems to have been caused by the recent VM shuffle at UBC and it
> should be fixed next time the bugs gatherer runs.

Thanks for looking into this issue, what exactly was done to fix it?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#839568: ITP: libmojolicious-plugin-renderfile-perl -- "render_file" helper for Mojolicious

[Hideki Yamane]

Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 

* Package name: libmojolicious-plugin-renderfile-perl
  Version : 0.10
  Upstream Author : Viktor Turskyi 
* URL : https://metacpan.org/release/Mojolicious-Plugin-RenderFile
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : "render_file" helper for Mojolicious

 Mojolicious::Plugin::RenderFile is a Mojolicious plugin that adds
 "render_file" helper. It does not read file in memory and just streaming it
 to a client.

I'll put this package into Debian repository to introduce openQA 
(http://open.qa/)

Bug#839569: ITP: libselenium-remote-driver-perl -- Perl Client for Selenium Remote Driver

[Hideki Yamane]

Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 

* Package name: libselenium-remote-driver-perl
  Version : 1.00
  Upstream Author : Aditya Ivaturi , 
Daniel Gempesaw ,
Emmanuel Peroumalnaïk ,
Luke Closs ,
Mark Stosberg 

* URL : https://metacpan.org/release/Selenium-Remote-Driver
* License : Apache-2.0
  Programming Lang: Perl
  Description : Perl Client for Selenium Remote Driver

 A setup class for all the repetitive things we need to do before running
 tests. First, we're deciding whether the test is in record or replay mode. If
 we're recording, we'll end up writing all the HTTP request/response pairs out
 to /mock_file. If we're replaying, we'll look for our OS-appropriate
 mock_file and try to read from it.
 .
 After we figure that out, we can instantiate our Mock::RemoteConnection with
 the proper constructor arguments and return that as our base_args for use in
 the tests! Finally, on destruction, if we're recording, we make sure to dump
 out all of the request/response pairs to the mock_file.

I'll put this package into Debian repository to introduce openQA 
(http://open.qa/)

Bug#839385: marked as done (UDD: incorrect affects_ for fixed bugs)

[Paul Wise]

On Sun, 2016-10-02 at 10:04 +0200, Sebastiaan Couwenberg wrote:

> Thanks for looking into this issue, what exactly was done to fix it?

Re-adding the NFS mount of the bugs data on the UDD host.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#839385: marked as done (UDD: incorrect affects_ for fixed bugs)

[Sebastiaan Couwenberg]

On 10/02/2016 10:32 AM, Paul Wise wrote:
> On Sun, 2016-10-02 at 10:04 +0200, Sebastiaan Couwenberg wrote:
>> Thanks for looking into this issue, what exactly was done to fix it?
> 
> Re-adding the NFS mount of the bugs data on the UDD host.

Thanks that clarifies the problem.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#811857: fixed in synaptic 0.83+nmu1

[Jeremy Bicha]

On Sun, Oct 2, 2016 at 3:56 AM, Olly Betts  wrote:
> Also, I NMUed it to unblock a transition, so now isn't the time for another
> NMU even if I could, as it would delay that transition completing.

Makes sense. I went ahead and uploaded to Ubuntu then since Ubuntu's
final freeze is only a few days away.

Jeremy

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

[Samuel Thibault]

Control: tags -1 + fixed-upstream

Hello,

Samuel Thibault, on Fri 26 Aug 2016 20:59:28 +0200, wrote:
> Chris Brannon, on Thu 18 Aug 2016 11:32:40 -0700, wrote:
> > I'm almost certain that the problem lies with portaudio, rather than
> > libasound.  It's described in my message to the portaudio list, found
> > here:
> > 
> > https://lists.columbia.edu/pipermail/portaudio/2016-August/000599.html
> 
> And the discussion shows that the issue really does seem to lie in
> there. portaudio maintainers, could you include the upstream patch from
> 
> https://lists.columbia.edu/pipermail/portaudio/2016-August/000623.html

I have attached to this mail the upstream fix that got released
yesterday as RC. Could you please apply it?

This:

> Without it, blind users using a screen reader have their screen reader
> hang every few minutes, making the system basically unusable.

is still preventing all blind users using speech synthesis from being
able to do any kind of serious work with debian testing.

Samuel
diff --exclude .svn --exclude .git --exclude CVS --exclude .hg -urwB 
portaudio-stable/src/hostapi/alsa/pa_linux_alsa.c 
portaudio-test/src/hostapi/alsa/pa_linux_alsa.c
--- portaudio-stable/src/hostapi/alsa/pa_linux_alsa.c   2013-10-17 
14:44:09.0 +0200
+++ portaudio-test/src/hostapi/alsa/pa_linux_alsa.c 2016-10-02 
00:07:12.0 +0200
@@ -1,5 +1,5 @@
 /*
- * $Id: pa_linux_alsa.c 1911 2013-10-17 12:44:09Z gineera $
+ * $Id$
  * PortAudio Portable Real-Time Audio Library
  * Latest Version at: http://www.portaudio.com
  * ALSA implementation by Joshua Haberman and Arve Knudsen
@@ -3805,8 +3805,23 @@
 totalFds += self->playback.nfds;
 }
 
+#ifdef PTHREAD_CANCELED
+if( self->callbackMode )
+{
+/* To allow 'Abort' to terminate the callback thread, enable 
cancelability just for poll() (& disable after) */
+pthread_setcancelstate( PTHREAD_CANCEL_ENABLE, NULL );
+}
+#endif
+
 pollResults = poll( self->pfds, totalFds, pollTimeout );
 
+#ifdef PTHREAD_CANCELED
+if( self->callbackMode )
+{
+pthread_setcancelstate( PTHREAD_CANCEL_DISABLE, NULL );
+}
+#endif
+
 if( pollResults < 0 )
 {
 /*  XXX: Depend on preprocessor condition? */
@@ -4175,12 +4190,18 @@
 int streamStarted = 0;
 
 assert( stream );
+/* Not implemented */
+assert( !stream->primeBuffers );
 
 /* Execute OnExit when exiting */
 pthread_cleanup_push( &OnExit, stream );
-
-/* Not implemented */
-assert( !stream->primeBuffers );
+#ifdef PTHREAD_CANCELED
+/* 'Abort' will use thread cancellation to terminate the callback thread, 
but the Alsa-lib functions
+ * are NOT cancel-safe, (and can end up in an inconsistent state).  So, 
disable cancelability for
+ * the thread here, and just re-enable it for the poll() in 
PaAlsaStream_WaitForFrames(). */
+pthread_testcancel();
+pthread_setcancelstate( PTHREAD_CANCEL_DISABLE, NULL );
+#endif
 
 /* @concern StreamStart If the output is being primed the output pcm needs 
to be prepared, otherwise the
  * stream is started immediately. The latter involves signaling the 
waiting main thread.
@@ -4265,10 +4286,6 @@
 {
 xrun = 0;
 
-#ifdef PTHREAD_CANCELED
-   pthread_testcancel();
-#endif
-
 /** @concern Xruns Under/overflows are to be reported to the 
callback */
 if( stream->underrun > 0.0 )
 {

Bug#839570: Browserified javascript and DFSG 2 (reopening)

[Pirate Praveen]

package: tech-ctte

Following up on #830978. I would like this to be reopened and request
CTTE make a formal vote.

Because, every major web based software will have to be moved to contrib
because its likely at least one of the javascript dependencies are in
browserified form.

1. Diaspora is already moved to contrib because of libjs-handlebars
2. GitLab will need to be moved to contrib #814871
3. Pagure will have to be in contrib #829046
4. Prometheus will need to be moved to contrib #835661

There will be more if we look at all packages depending on javascript
libraries or embedding them.

It is not realistic to expect Grunt will be packaged for stretch or
reimplement the same functionality for all browserified packages.

This will encourage more people to depend on non-free/contrib and I
don't think debian community wants to move in that direction. If that is
really what the community wants, I want it formally declared

I suggest including browserified js in stretch and make an effort to
package grunt for stretch+1.







signature.asc
Description: OpenPGP digital signature

Bug#773791:

[Luca Niccoli]

This seems an upstream bug that should be fixed in text version (which from
the PTS seems to have been just uploaded to unstable):
https://wiki.strongswan.org/issues/1429

The new version has still to propagate to my mirror so I couldn't verify it
yet.

Cheers,

Luca

Bug#834881: onboard: new upstream release 1.3.0

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Sat, 2016-08-20 at 23:48 -0400, Jeremy Bicha wrote:
> On Sat, Aug 20, 2016 at 5:49 AM, Ritesh Raj Sarraf  wrote:
> > There's a new release of onboard, 1.3.0. This release sounds exciting
> > from its NEWS entry, as it states initial Wayland support.
> 
> Sorry to disappoint you but… although onboard 1.3.0 looks nicer in
> Wayland than onboard 1.2 does, I don't think it's actually usable in
> Wayland yet.

Hi Jeremy,

Now that GNOME 3.22 is out, are there other issue why you are holding off the
upload ?

Thanks,
Ritesh

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX8MykAAoJEKY6WKPy4XVpWFgP/jR6jBBiipQHm8CvHsLTD7T2
lVxRX3D7yIsznsn93qmOxhx0zpsFzO0Mp4ADJ2JLNu1QRf8owRn6yJL3SyhV8iti
N2YfxS2LKHhEBhUbzD8J2tr1WrnVSsz75RhbHPgtA9qwriGRJOn5ExfYUDF/KrGB
4yalL29UdDSYYh8q8LMmHStxkv/YnzltZIaVltS+JmxY/NvUYJx+Ff46HsQhUOVZ
nIiZSkMAO5v+lhW6dzeaD35/YTW0k+Q3LEVkLnNi6le0dIOuNFH3OXxY1UrZY+58
zAGfypNQYrVZLuZ1OwTRF3C04yRFUBTEMCuDV+22U/BkW4bZoGqa4CX49RRHBSSY
ZNLAPG6DF90bboCy/gnkhaFNPPp+hJdvQUyJOFatsAnFqLbCURXUNMxej4l5KvPn
ZOyW3ikCj+PTiD3Kg3TAhRGfgm0KNo0Jq/k6lIw/5KA361AZ4ewsNu4d641/9ut8
/fKS4TMQmDWtwmUICSXMRrGLEaYRH2H59jXmGQQ7aPYinbITQZ7yROS/DEnjO+Kv
/vJbEV7SSl8xjjCpSz0M4//p9uISOjS/rOUOVSj3qlIGY9lq4g8f3U0z1axxMg26
RSl7J6y5H5eXAseukWQXj02zZ049EkAOpmob6RFHXr5UACDWbas57oheLROpwWYH
Wj+vcGwZVwxJZddsHz6D
=PFvt
-END PGP SIGNATURE-

Bug#839571: debhelper: Where did the binaries in the package go?

[Petter Reinholdtsen]

Package: debhelper
Version: 10.1
Severity: important

Hi.  My build in unstable suddenly no longer work, because debhelper no
longer ship 'dh':

% dpkg -l debhelper
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version   Architecture  Description
+++--=-=-==
ii  debhelper10.1  all   helper programs for 
debian/rules
% dpkg -L debhelper|grep usr/bin
%

Did the binary move or was the last debhelper build broken?

-- 
Happy hacking
Petter Reinholdtsen

Bug#628843: login: tty hijacking possible in "su" via TIOCSTI ioctl

[up201407890]

Hello Simon,

This has been recently patched by using seccomp to blacklist this ioctl.

https://github.com/karelzak/util-linux/commit/8e4925016875c6a4f2ab4f833ba66f0fc57396a2


This message was sent using IMP, the Internet Messaging Program.

Bug#839571: [debhelper-devel] Bug#839571: debhelper: Where did the binaries in the package go?

[Niels Thykier]

Control: forcemerge 839557 -1

Petter Reinholdtsen:
> 
> Package: debhelper
> Version: 10.1
> Severity: important
> 
> Hi.  My build in unstable suddenly no longer work, because debhelper no
> longer ship 'dh':
> 
> [...]
> %
> 
> Did the binary move or was the last debhelper build broken?
> 

Please use debhelper/10.2.1

Thanks,
~Niels

Bug#839289: RFS: pnmixer/0.7-1 [ITP] -- Simple mixer application for system tray

[Paul Wise]

On Sat, Oct 1, 2016 at 2:23 PM, Arnaud Rébillout wrote:

>   I am looking for a sponsor for my package "pnmixer"

I don't intend to sponsor this but here is a review:

These issues block the upload:

>   pnmixer (0.7-1) UNRELEASED; urgency=medium

You should list the suite (usually unstable) where you intend the
upload to be added to instead of UNRELEASED.

The file downloaded by uscan is different to the one you have included
in your Debian source package. Please adjust your debian/watch file to
use the correct one.

These issues would be nice to fix:

I suggest that you try and make the github generated tarball as
similar as possible to the `make dist` generated tarball. You can use
`diffoscope` to compare the two tarballs.

The debian/watch tells uscan that v0.7-rc1 is newer than v0.7. I think
you want uversionmangle=s/-rc/~rc/

You may want to sign your upstream tarballs, git tags and git commits:

https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
https://mikegerwitz.com/papers/git-horror-story

The images say they were produced in GIMP and look like multi-layer
images that have been rendered to flat bitmaps, did you discard the
XCF images or are they hidden away somewhere? How were these images
produced? In general it is best to render final images from the source
material at build time, using xcf2png or similar.

The bug #816124 should have be tagged fixed-upstream when you commented:

https://www.debian.org/Bugs/server-control#tag

Generated and stamp files should be removed from the upstream git repo
and added to .gitignore:

stamp-h.in

I expect most of autogen.sh can be replaced with a call to autoreconf:

autoreconf --force --install --symlink --warnings=all

Running wrap-and-sort would make diffs of the Debian packaging easier to read:

wrap-and-sort --short-indent --wrap-always --sort-binary-packages
--trailing-comma

The system() and g_spawn_command_line_async() functions should not be
used and I don't think `which` is very portable. Instead of
system()+`which` you should use g_find_program_in_path(). Instead of
g_spawn_command_line_async() you should use g_spawn_async().

http://bonedaddy.net/pabs3/log/2014/02/17/pid-preservation-society/

Please add some upstream metadata:

https://wiki.debian.org/UpstreamMetadata

Since you are upstream, please read our guide for upstreams:

https://wiki.debian.org/UpstreamGuide

Automatic checks:

build:

ui-tray-icon.c:340:2: warning: ‘gtk_status_icon_set_from_pixbuf’ is
deprecated [-Wdeprecated-declarations]
ui-tray-icon.c:358:2: warning: ‘gtk_status_icon_set_tooltip_text’ is
deprecated [-Wdeprecated-declarations]
ui-tray-icon.c:400:2: warning: ‘gtk_status_icon_position_menu’ is
deprecated [-Wdeprecated-declarations]
ui-tray-icon.c:578:2: warning: ‘gtk_status_icon_new’ is deprecated
[-Wdeprecated-declarations]
ui-tray-icon.c:604:2: warning: ‘gtk_status_icon_set_visible’ is
deprecated [-Wdeprecated-declarations]

lintian:

P: pnmixer source: debian-watch-may-check-gpg-signature

check-all-the-things:

$ env PERL5OPT=-m-lib=. duck
E: debian/control: Vcs-Git:
https://anonscm.debian.org/collab-maint/pnmixer.git: ERROR
(Certainty:certain)
   fatal: repository
'https://anonscm.debian.org/collab-maint/pnmixer.git/' not found

E: debian/control: Vcs-Browser:
https://anonscm.debian.org/gitweb/?p=collab-maint/pnmixer.git;a=summary:
ERROR (Certainty:certain)
   Curl:0 HTTP:404 No error

$ env PERL5OPT=-m-lib=. cme check dpkg
...
Warning in 'control source Vcs-Browser' value
'https://anonscm.debian.org/gitweb/?p=collab-maint/pnmixer.git;a=summary':
URL to debian system is not the recommended one
Warning in 'control source Vcs-Git' value
'https://anonscm.debian.org/collab-maint/pnmixer.git': URL to debian
system is not the recommended one

# This command checks style. While a consistent style
# is a good idea, people who have different style
# preferences will want to ignore some of the output.
$ find -type f \( -iname '*.sh' -o -iname '*.bash' \) -exec bashate
--ignore E002,E003 {} +
E001: Trailing Whitespace: 'echo '
 - ./autogen.sh : L25
E010: Do not on same line as for: 'for coin in `find $srcdir -name
configure.ac -print`'
 - ./autogen.sh : L96
E001: Trailing Whitespace: 'do '
 - ./autogen.sh : L97
E001: Trailing Whitespace: ' if test -z "$NO_LIBTOOLIZE" ; then '
 - ./autogen.sh : L124
4 bashate error(s) found

# Check with upstream where the GIMP XCF source files are.
$ find -type f \( -iname '*.png' -o -iname '*.gif' -o -iname '*.jpg'
-o -iname '*.jpeg' \) -exec grep -iF gimp {} +
Binary file ./data/icons/pnmixer.png matches
Binary file ./data/pixmaps/pnmixer-high.png matches
Binary file ./data/pixmaps/pnmixer-muted.png matches
Binary file ./data/pixmaps/pnmixer-low.png matches
Binary file ./data/pixmaps/pnmixer-medium.png matches
Binary file ./data/pixmaps/pnmixer-about.png matches

$ find -type f -iname '*.sh' -exec checkbashisms {} +
could not find any possible bashisms in bash script ./.travis/script.sh
could not find any possi

Bug#784473: [PATCH] kadu-mime-tex: remove extra build dependencies

[Pino Toscano]

tag 784473 + patch
tag 824959 + patch
thanks

Hi Patryk,

attached there is a patch to remove a number of build dependencies which
are not used at all by kadu-mime-tex, including libqtwebkit-dev
(#784473) and qtquick1-5-dev (#824959). qtdeclarative5-dev is explicitly
added now, as it is needed to build and most probably it was implicitly
pulled by one of the removed packages.

I'll most probably NMU/5 in a week, unless it is fixed before, or there
are objections/issues in NMUing.

Thanks,
-- 
Pino Toscano--- a/debian/control
+++ b/debian/control
@@ -4,41 +4,19 @@ Maintainer: Patryk Cisek = 9),
chrpath,
cmake,
-   enchant,
kadu,
kadu-dev (>= 1.2-2),
-   libarchive-dev,
-   libasound2-dev,
-   libaudio-dev,
-   libdbus-1-dev,
-   libenchant-dev,
-   libgadu-dev,
-   libidn11-dev,
libinjeqt-dev,
libkadu,
-   libmpdclient-dev,
-   libotr5-dev,
-   libphonon-dev,
-   libqca2-dev,
-   libqt4-dev,
libqt5webkit5-dev,
libqt5x11extras5-dev,
-   libqtwebkit-dev,
-   libsndfile1-dev (>= 1.0),
-   libsqlite3-dev,
libxfixes-dev,
-   libxss-dev,
-   libxtst-dev,
patchutils (>= 0.2.25),
pkgconf,
qtbase5-dev,
-   qtquick1-5-dev,
-   qtscript5-dev,
+   qtdeclarative5-dev,
qttools5-dev,
qttools5-dev-tools,
-   sharutils,
-   x11proto-scrnsaver-dev,
-   zlib1g-dev
 Standards-Version: 3.9.6
 Section: libs
 Homepage: http://www.kadu.im/~patryk/plugins/mime_tex/


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

Bug#834881: onboard: new upstream release 1.3.0

[Jeremy Bicha]

On Sun, Oct 2, 2016 at 5:00 AM, Ritesh Raj Sarraf  wrote:
> Now that GNOME 3.22 is out, are there other issue why you are holding off the
> upload ?

I'm just waiting on a DD from the Debian MATE team to upload since
it's their package. They are busy this weekend with MATE 1.16 though.

Thanks,
Jeremy Bicha

Bug#835354: libitext-java: uninstallable, makes other packages FTBFS

[Tobias Frost]

Package: src:libitext-java
Followup-For: Bug #835354
Control: close -1

After the NBS packages have been removed, libitext-java can be installed again.
Closing.

--
tobi

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

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

Bug#839572: ITP: libtest-time-perl -- Overrides the time() and sleep() core functions for testing

[Hideki Yamane]

Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 

* Package name: libtest-time-perl
  Version : 0.04
  Upstream Author : cho45 
* URL : https://metacpan.org/release/Test-Time
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Overrides the time() and sleep() core functions for testing

 Test::Time can be used to test modules that deal with time. Once you use this
 module, all references to time and sleep will be internalized.

I'll put this package into Debian repository to introduce openQA 
(http://open.qa/)

Bug#694034: (no subject)

[Thomas Lange]

The host www.aeolusproject.org does not have an entry in DNS any more.
It seems that the source is now hosted at
https://github.com/redhat-imaging/imagefactory
-- 
regards Thomas

Bug#839574: ciscolist file not installed in /etc

[Steinar H. Gunderson]

Package: snmp-mibs-downloader
Version: 1.1+nmu1
Severity: normal

Hi,

In /etc/snmp-mibs-downloader, cisco.conf is installed, but ciscolist isn't;
it's just installed into the example section in /usr/share/doc. This means
that “download-mibs cisco” won't work out of the box.

-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (750, 'stable'), (500, 'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages snmp-mibs-downloader depends on:
ii  patch 2.7.5-1
ii  smistrip  0.4.8+dfsg2-10
ii  wget  1.16-1+deb8u1

snmp-mibs-downloader recommends no packages.

Versions of packages snmp-mibs-downloader suggests:
ii  unzip  6.0-16+deb8u2

-- Configuration Files:
/etc/snmp-mibs-downloader/snmp-mibs-downloader.conf changed [not included]

-- debconf-show failed

Bug#839573: sound-juicer crashes in multiple_album_dialog() for Release "Grandes" (Artist: Maná)

[Lutz Müller]

Package: sound-juicer
Version: 3.14.0-1+b1
Severity: normal

Concerns https://musicbrainz.org/release-group/ad6326e4-917a-
4b2b-8949-2da959c06372

sound-juicer crashes in multiple_album_dialog():

(gdb) run sound-juicer
Starting program: /usr/bin/sound-juicer sound-juicer
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-
gnu/i686/cmov/libthread_db.so.1".
[New Thread 0xb596ab40 (LWP 4044)]
[New Thread 0xb4fffb40 (LWP 4045)]
[New Thread 0xb45ffb40 (LWP 4046)]
[Thread 0xb4fffb40 (LWP 4045) exited]
[New Thread 0xb4fffb40 (LWP 4047)]
[New Thread 0xb3bffb40 (LWP 4049)]
[New Thread 0xb33feb40 (LWP 4050)]
[New Thread 0xb2bfdb40 (LWP 4051)]
[New Thread 0xb23fcb40 (LWP 4052)]
[Thread 0xb2bfdb40 (LWP 4051) exited]
[Thread 0xb33feb40 (LWP 4050) exited]
[Thread 0xb23fcb40 (LWP 4052) exited]
[New Thread 0xb23fcb40 (LWP 4057)]
[Thread 0xb23fcb40 (LWP 4057) exited]
[New Thread 0xb33feb40 (LWP 4058)]
[New Thread 0xb23fcb40 (LWP 4059)]
[Thread 0xb23fcb40 (LWP 4059) exited]
[Thread 0xb33feb40 (LWP 4058) exited]
[New Thread 0xb33feb40 (LWP 4068)]
Unrecognised disc element: 'offset-list'
Unrecognised release element: 'cover-art-archive'
Unrecognised disc element: 'offset-list'
Unrecognised release element: 'release-event-list'
Unrecognised release element: 'cover-art-archive'
Unrecognised disc element: 'offset-list'
[Thread 0xb3bffb40 (LWP 4049) exited]
Unrecognised releasegroup attribute: 'type-id'
Unrecognised secondary type attribute: 'id'
Unrecognised release element: 'cover-art-archive'
Unrecognised disc element: 'offset-list'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised releasegroup attribute: 'type-id'
Unrecognised secondary type attribute: 'id'
Unrecognised relation attribute: 'type-id'
Unrecognised relation attribute: 'type-id'
Unrecognised releasegroup attribute: 'type-id'
Unrecognised secondary type attribute: 'id'
Unrecognised release element: 'release-event-list'
Unrecognised release element: 'cover-art-archive'
Unrecognised disc element: 'offset-list'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised track attribute: 'id'
Unrecognised relation attribute: 'type-id'
Unrecognised relation attribute: 'type-id'
Unrecognised releasegroup attribute: 'type-id'
Unrecognised secondary type attribute: 'id'
Unrecognised relation attribute: 'type-id'
Unrecognised relation attribute: 'type-id'
[Thread 0xb33feb40 (LWP 4068) exited]

Program received signal SIGSEGV, Segmentation fault.
0xb6d2e130 in __GI___libc_free (mem=0x8067cf8) at malloc.c:2945
2945malloc.c: No such file or directory.
(gdb) bt
#0  0xb6d2e130 in __GI___libc_free (mem=0x8067cf8) at malloc.c:2945
#1  0xb6ece821 in g_free () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x08056c25 in multiple_album_dialog ()
#3  0x080583dd in ?? ()
#4  0xb6513a82 in ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
#5  0xb6513556 in ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
#6  0xb6fb807f in g_cclosure_marshal_generic ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#7  0xb6fb784b in g_closure_invoke ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#8  0xb6fc9865 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#9  0xb6fd1fea in g_signal_emit_valist ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#10 0xb6fd26bd in g_signal_emit_by_name ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#11 0x08063e84 in ?? ()
#12 0xb6ec5510 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#13 0xb6ec8cc3 in g_main_context_dispatch ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#14 0xb6ec90d9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 0xb6ec91a6 in g_main_context_iteration ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
#16 0xb70a708c in g_application_run ()
---Type  to continue, or q  to quit---quit

How can I debug this further?



-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.ut

Bug#839575: hangs waiting for openssl

[Richard Kettlewell]

Package: tinyca
Version: 0.7.5-6

Attempting to create a fresh CA, tinyca hangs awaiting openssl.  OpenSSL
in turn is awaiting input on FD 0, which never arrives.

The line 328 diagnostic is suspicous, but I don't know if it's related.

$ tinyca2
create basedir: /home/richard/.TinyCA
create temp dir: /home/richard/.TinyCA/tmp
DEBUG call: /usr/bin/openssl req -new -keyform PEM -outform PEM -passin
env:SSLPASS -config /home/richard/.TinyCA/test/openssl.cnf -out
/home/richard/.TinyCA/test/cacert.req -key
/home/richard/.TinyCA/test/cacert.key -sha256
DEBUG: add to dn: GB
DEBUG: add to dn:
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/tinyca/OpenSSL.pm line 328.
DEBUG: add to dn:
DEBUG: add to dn: Anjou
DEBUG: add to dn: Deodand
DEBUG: add to dn: DeodandTest
DEBUG: add to dn: r...@terraraq.uk
DEBUG: add to dn:
DEBUG: add to dn:
DEBUG return: /usr/bin/openssl req -new -keyform PEM -outform PEM
-passin env:SSLPASS -config /home/richard/.TinyCA/test/openssl.cnf -out
/home/richard/.TinyCA/test/cacert.req -key
/home/richard/.TinyCA/test/cacert.key -sha256

You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-
Country Name (2 letter code) [AU]:State or Province Name (full name)
[Some-State]:Locality Name (eg, city) []:Organization Name (eg, company)
[Internet Widgits Pty Ltd]:Organizational Unit Name (eg, section)
[]:Common Name (eg, YOUR name) []:Email Address []:
Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:An optional company name []:




$ ps -ef | grep -E 'tinyca|openssl'
richard   2279  2262  0 10:35 pts/100:00:00 /usr/bin/perl -w
/usr/bin/tinyca2
richard   2330  2279  0 10:36 pts/100:00:00 /usr/bin/openssl req
-x509 -keyform PEM -outform PEM -passin env:SSLPASS -config
/home/richard/.TinyCA/test/openssl.cnf -out
/home/richard/.TinyCA/test/cacert.pem -key
/home/richard/.TinyCA/test/cacert.key -in
/home/richard/.TinyCA/test/cacert.req -days 3650 -sha256
richard   3227  3204  0 10:41 pts/300:00:00 grep -E tinyca|openssl

$ strace -p 2279
strace: Process 2279 attached
read(10, ^Cstrace: Process 2279 detached
 

$ strace -p 2330
strace: Process 2330 attached
read(0, ^Cstrace: Process 2330 detached
 
$ lsof -p 2330
COMMAND  PIDUSER   FD   TYPE DEVICE SIZE/OFFNODE NAME
openssl 2330 richard  cwdDIR  253,1 4096 1573015 /home/richard
openssl 2330 richard  rtdDIR  253,1 4096   2 /
openssl 2330 richard  txtREG  253,1   625588 2109333 /usr/bin/openssl
openssl 2330 richard  memREG  253,1  1787812 1175596
/lib/i386-linux-gnu/libc-2.24.so
openssl 2330 richard  memREG  253,113860 1175599
/lib/i386-linux-gnu/libdl-2.24.so
openssl 2330 richard  memREG  253,1  2095268 2101234
/usr/lib/i386-linux-gnu/libcrypto.so.1.0.2
openssl 2330 richard  memREG  253,1   432868 2101254
/usr/lib/i386-linux-gnu/libssl.so.1.0.2
openssl 2330 richard  memREG  253,1   146716 1052859
/lib/i386-linux-gnu/ld-2.24.so
openssl 2330 richard0r  FIFO   0,10  0t0   20272 pipe
openssl 2330 richard1w  FIFO   0,10  0t0   20273 pipe
openssl 2330 richard2w  FIFO   0,10  0t0   20273 pipe
$ dpkg -l openssl
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  openssl1.0.2j-1 i386 Secure Sockets Layer
toolkit - cr

ttfn/rjk

Bug#784473: [PATCH] kadu-mime-tex: remove extra build dependencies

[Patryk Cisek]

Hi Pino,

Please, NMU now -- I'm replacing my Debian GnuPG key, thus won't be able to
upload right away. Thanks!

On Sun, Oct 2, 2016 at 11:16 AM, Pino Toscano  wrote:

> tag 784473 + patch
> tag 824959 + patch
> thanks
>
> Hi Patryk,
>
> attached there is a patch to remove a number of build dependencies which
> are not used at all by kadu-mime-tex, including libqtwebkit-dev
> (#784473) and qtquick1-5-dev (#824959). qtdeclarative5-dev is explicitly
> added now, as it is needed to build and most probably it was implicitly
> pulled by one of the removed packages.
>
> I'll most probably NMU/5 in a week, unless it is fixed before, or there
> are objections/issues in NMUing.
>
> Thanks,
> --
> Pino Toscano




-- 
Patryk Cisek

Bug#839576: libio-socket-ssl-perl: Cannot use SSL_key_file with ACL permissions

[Michael Braun]

Package: libio-socket-ssl-perl
Version: 2.002-2+deb8u1
Severity: normal

Dear Maintainer,

I upgraded from wheezy to jessie. The issue did not occur before.

I am running a perl daemon as some non-root user that uses SSL_key_file with 
IO::Socket::SSL->start_SSL($client, SSL_server => 1, SSL_key_file => ..., ...).

The key file given is owned by root:root, but getfacl reports 
user:$daemonuser:r-- and using "sudo -u $daemonuser cat $SSL_key_file" works 
fine.

Though, the daemon does not longer accept clients writing to STDERR 
"SSL_key_file ... is not accessible at /usr/share/perl5/IO/Socket/SSL.pm line 
2010".

That source line reads like it is supposed to check readiblity of the key file 
given. I expect it to pass as the file is actually readable and start SSL 
communication with the client.

Regards,
M. Braun


-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.1-040201-generic (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libio-socket-ssl-perl depends on:
ii  libnet-ssleay-perl  1.65-1+deb8u1
ii  netbase 5.3
ii  perl5.20.2-3+deb8u6

Versions of packages libio-socket-ssl-perl recommends:
ii  libio-socket-inet6-perl 2.72-1
ii  libsocket6-perl 0.25-1+b1
ii  liburi-perl 1.64-1
ii  perl5.20.2-3+deb8u6
ii  perl-base [libsocket-perl]  5.20.2-3+deb8u6

Versions of packages libio-socket-ssl-perl suggests:
ii  ca-certificates  20141019+deb8u1

-- no debconf information

Bug#836317: dh_systemd_start should stop the sevice on remove even if --no-start has been passed

[Laurent Bigonville]

Le 02/10/16 à 02:13, Michael Biebl a écrit :

On Thu, 01 Sep 2016 17:03:42 +0200 Laurent Bigonville 
wrote:

Package: debhelper
Version: 9.20160814
Severity: important
File: /usr/bin/dh_systemd_start

Hi,

ATM, if --no-start is passed to dh_systemd_start, the service is never
stopped even if the package is removed/purged.

IMHO, is should be stopped in that case, I would do something like:

-if ($dh{R_FLAG} || $dh{RESTART_AFTER_UPGRADE}) {
+if ($dh{R_FLAG} || $dh{RESTART_AFTER_UPGRADE} || $dh{NO_START}) {
 # stop service only on remove
 $sd_autoscript->("prerm", "prerm-systemd-restart");
-} elsif (!$dh{NO_START}) {
+} else {
 # always stop service
 $sd_autoscript->("prerm", "prerm-systemd");
 }

What do you think?

I think this makes sense but we should make sure that this is consistent
with dh_installinit/sysv
Have you checked what dh_installinit does in this case?


mmh the manpage of dh_installinit states that:

   --no-start
   Do not start the init script on install or upgrade, or stop 
it on removal.  Only call update-rc.d. Useful for rcS scripts.


So it seems that not stopping the service on remove is intended, but at 
the same time I don't think it's relevant for other services than the 
early initialization ones.

Bug#839577: devede: DivX conversion fails starting

[Marco Mattiolo]

Package: devede
Version: 3.23.0-13-gbfd73f3-2
Severity: normal

Dear Maintainer,
thank you for maintaing Devede package in Debian.

I'm experiencing an unexpected devede behaviour while converting an 
youtube-dl generated .mkv to divx-compressed .mpg: after selecting the 
input file and all the encoding options, I click the "forward" button 
but nothing happens.
I also tried converting the same .mkv to a DVD-grade mpg, and it worked. 
Launching devede from command line, I got a few errors (see below): 
maybe the divx part of devede still refers to ffmpeg (and doesn't find 
it), while the dvd part correctly refers to avconv?

Also found [1] while searching for the error messages.

Greetings

Marco

[1] 
http://www.linuxquestions.org/questions/slackware-14/unable-to-create-video-dvd-with-devede-732887/


$ devede
DeVeDe 3.23.0 beta1
Locale: it_IT.UTF-8
Using package-installed files
/home/marco/
Cores: 4 Virtual cores: 8
Entro en fonts
Salgo de fonts
/home/marco/
Temp Directory is:  /var/tmp
home load:  /home/marco/.devede
linea:  video_format:pal

linea:  temp_folder:/var/tmp/

linea:  multicore:4

linea:  hyperthreading:0

linea:  sub_language:EN (ENGLISH)

linea:  sub_codepage:ISO-8859-1

linea:  AC3_fix:0

linea:  AC3_fix_ffmpeg:0

linea:  AC3_fix_avconv:0

linea:  erase_tmp_files:1

linea:  encoder_video:avconv

linea:  encoder_menu:avconv

linea:
Creating window /usr/share/devede/wdisk_type.ui
Creating window /usr/share/devede/wmain.ui
/usr/lib/devede/devede_other.py:751: GtkWarning: Unknown property: 
GtkMenu.ubuntu-local
   tree.add_from_file(filename)
Launching program:  mplayer -loop 1 -identify -ao null -vo null -frames 
0 /usr/share/devede/silence.ogg
elemento: /usr/bin
Longitud sonido: 38
Launching program:  mplayer -loop 1 -identify -ao null -vo null -frames 
0 /usr/share/devede/silence.ogg
elemento: /usr/bin
Longitud sonido: 38
Calculating size for disk :divx
Calculating size for disk :divx
drop
Dragged files: ['/media/marco/Matt-drive/EEVblog #899 - Extreme 
Mailbag!-boahAP3Sf4s.mkv']
Launching program:  mplayer -loop 1 -identify -ao null -vo null -frames 
0 /media/marco/Matt-drive/EEVblog #899 - Extreme Mailbag!-boahAP3Sf4s.mkv
elemento:  /usr/bin
Launching program:  mplayer -loop 1 -identify -ao null -vo null -frames 
1 /media/marco/Matt-drive/EEVblog #899 - Extreme Mailbag!-boahAP3Sf4s.mkv
elemento:  /usr/bin
V:   0.0   0/  0 ??% ??% ??,?% 0 0
True
0
Calculating size for disk :divx
Creating window /usr/share/devede/wfile.ui
Chequeo /media/marco/Matt-drive/EEVblog #899 - Extreme 
Mailbag!-boahAP3Sf4s.mkv
Launching program:  mplayer -loop 1 -identify -ao null -vo null -frames 
0 /media/marco/Matt-drive/EEVblog #899 - Extreme Mailbag!-boahAP3Sf4s.mkv
elemento:  /usr/bin
Launching program:  mplayer -loop 1 -identify -ao null -vo null -frames 
1 /media/marco/Matt-drive/EEVblog #899 - Extreme Mailbag!-boahAP3Sf4s.mkv
elemento:  /usr/bin
V:   0.0   0/  0 ??% ??% ??,?% 0 0
Pongo nombre por propiedades
File changed to None
entro en parte critica
paso por set_lower
Activo ASPECT_RATIO
divx
Props: {'ismpeg': False, 'copy_audio': False, 'ofps': 25, 'fps': 25, 
'ofps2': '25.000'}
Props: {'ismpeg': False, 'copy_audio': False, 'ofps': 25, 'fps': 25, 
'ofps2': '25.000'}
Rotate: 0
Meto pista 0
Pista seleccionada: 0
Props: {'ismpeg': False, 'copy_audio': False, 'ofps': 25, 'fps': 25, 
'ofps2': '25.000'}
Anado filtro
Anado filtro
entro en parte critica
paso por set_lower
Activo ASPECT_RATIO
divx
Rotate: 0
Meto pista 0
Pista seleccionada: 0
Props: {'ismpeg': False, 'copy_audio': False, 'ofps': 25, 'fps': 25, 
'ofps2': '25.000'}
Modificando
Fin
File changed to /media/marco/Matt-drive/EEVblog #899 - Extreme 
Mailbag!-boahAP3Sf4s.mkv
entro en parte critica
paso por set_lower
Activo ASPECT_RATIO
divx
Rotate: 0
Meto pista 0
Pista seleccionada: 0
Props: {'ismpeg': False, 'copy_audio': False, 'ofps': 25, 'fps': 25, 
'ofps2': '25.000'}
Calculating size for disk :divx
Threads: 4
Launching program:  ffmpeg -codecs
elemento:  /usr/bin
error in launch program

elemento:  /usr/local/bin
error in launch program

elemento:  /usr/share/bin
error in launch program

elemento:  /usr/share/local/bin
error in launch program

elemento:  /bin
error in launch program

elemento:  /usr/lib/devede/bin
error in launch program

Traceback (most recent call last):
   File "/usr/lib/devede/devede_main.py", line 474, in on_main_go_clicked
conversor=devede_convert.create_all(self.gladefile,self.structure,self.global_vars,self.callback2)
   File "/usr/lib/devede/devede_convert.py", line 192, in __init__
 if (False==self.check_mp3lame()):
   File "/usr/lib/devede/devede_convert.py", line 158, in check_mp3lame
 runner.wait_end2()
   File "/usr/lib/devede/devede_executor.py", line 98, in wait_end2
 r1,r2=self.handle.communicate()
AttributeError: 'NoneType' object has no attribute 'communicate'
Creating window /usr/share/devede/wcancel_dialog.ui
Saving configuration
/home/marco/
Exiting
Have a nice day


$ devede
DeVeDe 3.23.0 beta1
Loc

Bug#839578: RFP: libcheck -- unit testing framework for C

[Daniel Stender]

Package: wnpp
Severity: wishlist

* Package name: libcheck
  Version : 0.10.0
  Upstream Author : Branden Archer 
* URL : https://libcheck.github.io/check/
* License : LGPL-2.1
  Programming Lang: C
  Description : unit testing framework for C

Check is a unit testing framework for C. It features a simple interface
for defining unit tests, putting little in the way of the developer. Tests
are run in a separate address space, so both assertion failures and code
errors that cause segmentation faults or other signals can be caught. Test
results are reportable in the following: Subunit, TAP, XML, and a generic 
logging format.

Cheers,
DS

Bug#838540: Bug #838540: Target portal group change at login not properly handled (logoutall skips session)

[Christian Seiler]

Control: forwarded -1 
https://groups.google.com/forum/#!topic/open-iscsi/XE0Q5TvwgGQ

Hi again,

I've now dug into the code a bit and forwarded the bug to the
upstream open-iscsi mailing list. Once a patch exists that
upstream is happy with as well, I'll push a new version to sid
with the patch for that included.

I've also found out where the problem in libvirt lies and will
report a bug for that as well.

Regards,
Christian

Bug#839579: auctex: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory)

[Santiago Vila]

Package: src:auctex
Version: 11.88-1.2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
/bin/bash: git: command not found
dh build-indep --exclude .eperl --with tex
   dh_testdir -i -O--exclude=.eperl
   dh_update_autotools_config -i -O--exclude=.eperl
   dh_auto_configure -i -O--exclude=.eperl
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libexecdir=\${prefix}/lib/auctex 
--disable-maintainer-mode --disable-dependency-tracking
checking for make... make
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for date in ChangeLog... 2014-11-01
checking for release in ChangeLog... not found, using 2014-11-01 instead
checking for date in ChangeLog... 2014-10-29

[... snipped ...]

config.status: creating Makefile
config.status: creating tex-site.el.out
config.status: creating preview/preview.el
config.status: creating doc/Makefile
config.status: creating auctex.el
=== configuring in preview (/<>/preview)
configure: running /bin/bash ./configure --disable-option-checking 
'--prefix=/usr'  '--build=x86_64-linux-gnu' '--includedir=${prefix}/include' 
'--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' 
'--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' 
'--libexecdir=${prefix}/lib/auctex' '--disable-maintainer-mode' 
'--disable-dependency-tracking' 'build_alias=x86_64-linux-gnu' 
--cache-file=/dev/null --srcdir=.
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for /usr/bin/emacs... /usr/bin/emacs
checking if /usr/bin/emacs is XEmacs... no
checking for Emacs prefix... "/usr"
checking if Emacs is recent enough... yes
checking if build directory is valid... yes
checking where lisp files go... ${datadir}/emacs/site-lisp
checking what file to use for preview startup... 
${datadir}/emacs/site-lisp/preview-latex.el
checking where the package lisp files go... ${datadir}/emacs/site-lisp/auctex
checking where the data files go... ${datadir}/emacs/site-lisp/auctex
checking for the location of AUCTeX's tex-site.el... ..
checking for gs... gs
checking for latex... /usr/bin/latex
checking for pdflatex... /usr/bin/pdflatex
checking for tex... /usr/bin/tex
checking for prefix from kpsepath... "/usr"
checking for TDS-compliant directory... ${datadir}/texmf
Preview will be placed in ${datadir}/texmf/tex/latex/preview
Preview docs will be placed in ${datadir}/texmf/doc/latex/styles
checking for texhash... /usr/bin/texhash
checking for initexmf... /usr/bin/texhash
checking for glaring installation conflicts... probably none
configure: creating ./config.status
config.status: creating Makefile
config.status: creating auto.el
config.status: creating latex/Makefile

Congratulations!  Configuration of preview is complete.


Congratulations!  Configuration of AUCTeX is complete.

Type "make" at the prompt to build.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/bin/bash: git: command not found
chmod a+x debian/elcc
chmod: cannot access 'debian/elcc': No such file or directory
debian/rules:43: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:52: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

Please note that there is both a "build" target and an
"override_dh_auto_build" target, but there are not build-arch or
build-indep targets.

This is not very orthodox and leads to funny failures like this one,
where "dpkg-buildpackage -A" and "dpkg-buildpackage" have different
results even if package is "Arch: all".

I would try removing the build target (and also fixing
override_dh_auto_build), since this package is supposed to have
switched to "dh".

While we are at it, we have now an "Arch: all" autobuilder. Please
consider uploading in source-only form so that these kind of bugs are
discovered earlier and do not propagate to testing.

Thanks.

Bug#839581: git-buildpackage: '~' expansion not working anymore

[Alessandro Ghedini]

Package: git-buildpackage
Version: 0.8.4
Severity: normal

Hello,

I have the following values in my gbp.conf:

[DEFAULT]
...
export-dir   = ~/devel/debian/build-area
tarball-dir  = ~/devel/debian/build-area

However when building a package I now get:

 % gbp buildpackage --git-ignore-branch --git-verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: true [] []
gbp:debug: ['git', 'status', '--porcelain']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/local']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'HEAD']
gbp:debug: ['git', 'ls-tree', 'HEAD']
gbp:debug: ['git', 'show', '--pretty=medium', 'HEAD:debian/changelog']
gbp:error: Cannot create output dir 
/home/ghedo/devel/debian/chromium-browser/~/devel/debian/build-area

as you can see the '~' expansion isn't working anymore. Downgrading to 0.8.3
"fixes" the problem.

Cheers

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts2.16.8
ii  git   1:2.9.3-1
ii  man-db2.7.5-1
ii  python-dateutil   2.5.3-2
ii  python-pkg-resources  28.0.0-1
ii  python-six1.10.0-3
pn  python:any

Versions of packages git-buildpackage recommends:
ii  pbuilder 0.226.1
ii  pristine-tar 1.37
ii  python-requests  2.11.1-1

Versions of packages git-buildpackage suggests:
pn  python-notify  
ii  sudo   1.8.17p1-2
pn  unzip  

-- no debconf information


signature.asc
Description: PGP signature

Bug#839580: request-tracker4: FTBFS in testing (failed tests)

[Santiago Vila]

Package: src:request-tracker4
Version: 4.2.13-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_testdir
# Update translations
debconf-updatepo
# Keep aside automatically generated files shipped in the upstream tarball
mkdir bak
find . -name '*.in' -print | egrep -v '\.pc|\.\/debian' | sed -e 's/\.in$//' | 
while read f; do mkdir -p bak/`dirname $f`; mv -v $f bak/$f; done
'./Makefile' -> 'bak/./Makefile'
'./etc/upgrade/shrink-cgm-table' -> 'bak/./etc/upgrade/shrink-cgm-table'
'./etc/upgrade/switch-templates-to' -> 'bak/./etc/upgrade/switch-templates-to'
'./etc/upgrade/time-worked-history' -> 'bak/./etc/upgrade/time-worked-history'
'./etc/upgrade/3.8-ical-extension' -> 'bak/./etc/upgrade/3.8-ical-extension'
'./etc/upgrade/4.0-customfield-checkbox-extension' -> 
'bak/./etc/upgrade/4.0-customfield-checkbox-extension'

[... snipped ...]

t/mail/gnupg-outgoing-signed_encrypted.t (Wstat: 3584 Tests: 68 
Failed: 14)
  Failed tests:  10-11, 18-19, 27-28, 35-36, 41, 43, 48
50, 67-68
  Non-zero exit status: 14
  Parse errors: Bad plan.  You planned 104 tests but ran 68.
t/mail/gnupg-special.t   (Wstat: 512 Tests: 19 
Failed: 2)
  Failed tests:  16, 19
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 26 tests but ran 19.
t/mail/gnupg-realmail.t  (Wstat: 11520 Tests: 199 
Failed: 45)
  Failed tests:  72-73, 80-81, 84, 90-91, 94, 100-101, 108-110
113, 119-121, 124, 130-132, 138-140, 143
149-151, 154, 160-162, 168-172, 175, 181-185
188, 199
  Non-zero exit status: 45
t/mail/gnupg-reverification.t(Wstat: 16896 Tests: 204 
Failed: 66)
  Failed tests:  16-17, 22, 25-26, 28-29, 34, 37-38, 40-41
46, 49-50, 52-53, 58, 61-62, 64-65, 70
73-74, 76-78, 83, 86-87, 89-91, 102-103
114-115, 126-127, 138-139, 150-152, 163-164
167-168, 170-171, 173-174, 176-177, 179-180
182-183, 185, 188, 191, 194, 197, 200, 203
  Non-zero exit status: 66
t/security/CVE-2012-4735-incoming-encryption-header.t (Wstat: 256 Tests: 12 
Failed: 1)
  Failed test:  7
  Non-zero exit status: 1
t/security/CVE-2012-4735-sign-any-key.t  (Wstat: 1792 Tests: 20 
Failed: 7)
  Failed tests:  4-9, 19
  Non-zero exit status: 7
t/web/admin_user.t   (Wstat: 256 Tests: 26 
Failed: 1)
  Failed test:  11
  Non-zero exit status: 1
t/web/crypt-gnupg.t  (Wstat: 4864 Tests: 103 
Failed: 19)
  Failed tests:  17-19, 45-48, 63, 66, 73, 75-77, 82-84
100-101, 103
  Non-zero exit status: 19
t/web/gnupg-select-keys-on-create.t  (Wstat: 3328 Tests: 75 
Failed: 13)
  Failed tests:  9, 18-21, 45, 60-62, 70-72, 75
  Non-zero exit status: 13
  Parse errors: Bad plan.  You planned 80 tests but ran 75.
t/web/gnupg-select-keys-on-update.t  (Wstat: 2816 Tests: 82 
Failed: 11)
  Failed tests:  12, 22-23, 49, 66-68, 77-79, 82
  Non-zero exit status: 11
  Parse errors: Bad plan.  You planned 87 tests but ran 82.
Files=362, Tests=25216, 699 wallclock secs ( 2.87 usr  0.30 sys + 655.21 cusr 
30.03 csys = 688.41 CPU)
Result: FAIL
Makefile:376: recipe for target 'test-parallel' failed
make[1]: *** [test-parallel] Error 1
make[1]: Leaving directory '/<>'
debian/rules:27: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I have quoted only part of the build log, but this should be easy to
reproduce in testing with sbuild. Please make sure you don't have any
gnupg flavour in the chroot before trying to reproduce it.

(If you need a build log anyway, just ask, I have two of them).

Maybe the recent gnupg transition may have something to do with this,
but I see that this package build-depends on gnupg1, so even if the
transition has not ended yet, it should work in testing too.

Thanks.

Bug#732587: Bug #732587: debian expert install on iscsi-device

[Christian Seiler]

Hi there,

I'm just doing a bit of cleanup with respect to the bugs reported
against open-iscsi and noticed this bug here.

With the point release of Jessie 8.6, there was an update to
open-iscsi that fixed issues with the installer and how iSCSI is
set up. Since a long time has passed since you reported this (sorry
about that), could you perhaps retest the current Jessie 8.6
installer and see if those issues are still present, before I dig
deeper? Thanks!

Regards,
Christian

Bug#777084: open-iscsi-udeb: please build the udeb on x32

[Christian Seiler]

Hi Adam,

since it's been 10 months and I haven't heard back, I'd like to gently
ping you on this?

On 11/12/2015 01:41 AM, Christian Seiler wrote:
> The problem I see is that if I add the string "x32" to the list of
> architectures for the udeb, src:open-iscsi will build a binary package
> on an architecture that is not installable at all (because dependencies
> can't be resolved). If x32 were to become an official release
> architecture tomorrow, this would immediately prevent testing migration
> of the open-iscsi package. Of course, it currently isn't, and solving
> the question about what to do with the kernel is probably a
> prerequisite to making it a release architecture, so the danger there
> is probably very slim.
> 
> Still, I'm kind of hesitant to add something to the package that could
> blow up some time in the future. On the other hand, I want to support
> porting efforts and do understand that sometimes things like this can
> be chicken-or-egg problems (i.e. you need to have a sufficiently
> diverse set of udebs to be actually able to work on d-i support for the
> specific port and test things).
> 
> Since I don't see a clear-cut answer, I'm going to defer to you here,
> since you are working on the port. If you say that it helps you in
> your efforts to just have this in the archive, even though on the not
> yet official x32 architecture the package is not installable, I'll
> add it to debian/control and close this bug. The other possibility
> would be to block this bug against some other bug that tracks x32 d-i
> work. Please tell me which way you'd prefer.

Regards,
Christian

Bug#839400: hplip: setup of HPLIP toolbox is faulty

[Didier 'OdyX' Raboud]

Control: severity -1 wishlist
Control: retitle -1 Make Debian install work over previous manual install

Le samedi, 1 octobre 2016, 09.00:39 h CEST WRMelgaard a écrit :
> Dear Maintainer,
> Previously installed version was done manually from HP website, decided to
> use the Debian packag system for upgrade Using Synaptic, installed the
> hplip package.

This is not a supported use-case, sorry. When installing Debian packages, the 
unpacking will only care about files that it knows about, that is the files 
that 
have previously been unpacked when installing other Debian packages.

Third-party package installer interfere with Debian packages installation, and 
it's not something we can really support. I'll keep this bug open, as a 
wishlist (because it's _possible_ to have some code in place to circumvent 
this, but not realistic.) Patches welcome.

-- 
Cheers,
OdyX

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

Bug#809201: rawtherapee: Crash with 'libpng error: incorrect data check'

[Philip Rinn]

Hi,

I could never reproduce this bug :(. But as I uploaded a new upstream snapshot (
aka beta for RT 5), could you please test if this bug is still present in
rawtherapee 4.2.1241?

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#830175: rawtherapee: System freezes during saving/processing

[Philip Rinn]

Hi,

I could never reproduce this bug :(. But as I uploaded a new upstream snapshot (
aka beta for RT 5), could you please test if this bug is still present in
rawtherapee 4.2.1241?

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#827894: Segfault on start

[Paul Gevers]

Control: tags -1 moreinfo

On 12-08-16 22:55, Paul Gevers wrote:
> Upstream is requesting a backtrace with debugging symbols (for now,
> rather than having the database) because it can be shared publicly. Are
> you in the position to create that? (If you are fine with it, please
> follow-up directly in the upstream bug report).

Ping?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#655976: queue-viewer: support binary debdiffs

[Julien Cristau]

Hi Adam,

thanks for getting this rolling.

On Tue, Sep 27, 2016 at 20:35:43 +0100, Adam D. Barratt wrote:

> - How should we invoke debdiff? We can avoid multiple debdiff
> invocations via "debdiff --show-moved --controlfiles=ALL --from
> base1.deb base2.deb --to new1.deb new2.deb" or, if we want to make the
> command line shorter, generate .changes files for the two sets of
> packages and then feed those to debdiff. In the latter case, we'd want
> to create symlink farms, as the .deb files would need to be in the same
> directory as the .changes files.
> 
I don't think length of the command line is a big concern?

> - Is there a way we can make the wdiff output easier to review? We need
> to consider both on-screen display (presumably primarily via a web
> browser) and the possibility of mailing the result, as we do for source
> uploads.
> 
If the html part could have some colors to show added/removed bits,
that'd be nice.

> - Should queue-viewer always display links to debdiffs for every
> architecture, or only those where those is an "interesting" difference?
> What would be a useful UI for that?
> 
> - What differences are we interested in? Some will always occur -
> version number changes from $old_source_ver to $new_source_ver (with
> adjustment for binNMUs); the addition of a "Source" header for a
> newly-binNMUed package; a change in Size / Installed-Size within a
> certain delta.

Also adjusting for epoch, and binary packages with different versioning
schemes from the source.  diffpackages doesn't quite deal with that,
yet...  I think it's ok to leave filtering to a later date though, if we
can get something it'll be better than the current "notice issues on the
point release Saturday".

> - What should happen if the list of binary packages is different between
> the two versions? While still an exception, this happens often enough
> with e.g. firefox updates, that we need to consider it.
> 
I think big fat "Removed binary package(s)" and "Added binary
package(s)" warnings together with the debdiff for common packages would
be enough, at least initially.  Otherwise you'd have to manually tell
the tool which binary package was renamed to show the debdiff between
old and new.

Cheers,
Julien

Bug#687663: g15daemon: Fail to install - /dev/input/uinput not found

[Chris]

Hi,

> The post-installation script failed to find /dev/input/uinput
> and left the package in partially installed state.
> Uinput module was loaded and available at /dev/uinput.

the issue is caused by a hardcoded /dev/input/uinput path in:

/etc/init.d/g15daemon

Changing:

load_uinput() {
if [ ! -e /dev/input/uinput ] ; then
modprobe -q uinput || true
wait_for_file /dev/input/uinput 3  ||  return 1
fi
}

to:

load_uinput() {
if [ ! -e /dev/uinput ] ; then
modprobe -q uinput || true
wait_for_file /dev/uinput 3  ||  return 1
fi
}

and a systemctl daemon-reload afterwards fixes the issue here.

Ref to the matching bugreport at ubuntu launchpad:
https://bugs.launchpad.net/debian/+source/g15daemon/+bug/570245

Bug#839531: jessie-pu: package asused/3.72-11

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Sun, 2016-10-02 at 02:05 +0200, Sebastien Badia wrote:
> Pff really sorry for the waste time… I was too fast on this one…

No problem.

> Just fixed the version number, and re-builded/uploaded to mentors.d.n
> https://mentors.debian.net/debian/pool/main/a/asused/asused_3.72-11+deb8u1.dsc
> (build and tested in a clean env on Debian jessie).
> 
> The debdiff against 3.72-11 version in jessie is now attached.

Thanks; please feel free to upload that (or get it uploaded via a
sponsor, if needed).

Regards,

Adam

Bug#780082: liferea: random crash (SIGABRT)

[Paul Gevers]

Control: tags -1 moreinfo

On Sun, 15 May 2016 18:26:49 -0500 David MichaelSmith
 wrote:
> forwarded 780082 https://github.com/lwindolf/liferea/issues/351

Upstream responded (a long time ago):
One small important detail is missing :-) This dump indicates an
assertion (first thread has g_assertion_message in it). There was a CLI
output that probably explains the dump. This would be really helpful

I don't assume you still have this info (if you had it at all). If not,
I propose we close this (and upstreams) bug report.

Thanks
Paul



signature.asc
Description: OpenPGP digital signature

Bug#839573: Patch that fixes the issue

[Lutz Müller]

--- sound-juicer-3.14.0/src/sj-main.c	2014-09-17 15:25:47.0 +0200
+++ sound-juicer-3.14.0-modified/src/sj-main.c	2016-10-02 13:34:29.918679563 +0200
@@ -888,7 +888,7 @@
  * "Released on " */
 details = g_strdup_printf (_("Released on %s"), label_text->str);
   } else {
-details = _("Release label, year & country unknown");
+details = g_strdup_printf (_("Release label, year & country unknown"));
   }
 
   if (label_text)

Bug#831378: USB Keyboard works with current daily image

[Bernhard]

Hello,

with the current U-Boot in the daily images, the USB keyboard works.
I used the daily image:
d-i.debian.org/daily-images/armhf/20161002-00:16/netboot/SD-card-images

From my point-of-view, this bug report can be closed.

Best regards
Bernhard


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

Bug#839573: Bug already fixed upstream

[Lutz Müller]

I just verified on
https://git.gnome.org/browse/sound-juicer/tree/src/sj-album-chooser-dialog.c: 
This bug does not exist there any more.

Bug#839582: USB-Keyboard don't work at Banana Pi

[Bernhard]

Package: installation-reports

Boot method: SD-Card image
Image version: Created SD-Card with these two images:

> https://d-i.debian.org/daily-images/armhf/20161002-00:16/netboot/SD-c
> ard-images/firmware.BananaPi.img.gz
https://d-i.debian.org/daily-images/armhf/20161002-00:16/netboot/SD-c
> ard-images/partition.img.gz

Date: 2016-10-02

Machine: Banana Pi
Processor: Allwinner A20
Memory: 1GB

Partitions: -

Output of lspci -knn: -

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[E]

Comments/Problems:

The initial boot with UBoot was successfully.
Within UBoot, the connected USB-Keyboard works.

After booting to the installer, the USB-Keyboard don't work anymore.

This looks like the behaviour described in bug report #809521.

Thank you.

Best regards
Bernhard


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

Bug#818484: thunar: Confirming segfault while moving files between 2 thunar instances

[xiscu]

Package: thunar
Version: 1.6.10-2
Followup-For: Bug #818484

Dear Maintainer,
I'm just confirming the segfaults while moving files between 2 thunar instances.

- Logs:
cat /var/log/messages | grep thunar
Oct  2 13:51:44 r5 kernel: [  662.691921] thunar[15833]: segfault at 0 ip 
0054fe92065c sp 038e9574f760 error 4 in thunar[54fe8e5000+b9000]

- Starting from the shell gives:
~$ thunar

(thunar:15833): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 
'GObject'

(thunar:15833): GLib-GObject-CRITICAL **: g_object_set_qdata: assertion 
'G_IS_OBJECT (object)' failed

(thunar:15833): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

(thunar:15833): GLib-GIO-CRITICAL **: g_file_query_info: assertion 'G_IS_FILE 
(file)' failed

(thunar:15833): GLib-GIO-CRITICAL **: g_file_get_basename: assertion 'G_IS_FILE 
(file)' failed
Segmentation fault


Thanks in advance!
xiscu


-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-3
ii  libcairo2   1.14.6-1+b1
ii  libdbus-1-3 1.10.10-1
ii  libdbus-glib-1-20.108-1
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.0-1
ii  libgtk2.0-0 2.24.31-1
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.40.3-2
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.10-2
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-2
ii  libxfconf-0-2   4.12.0-3
ii  shared-mime-info1.7-1
ii  thunar-data 1.6.10-2

Versions of packages thunar recommends:
ii  dbus-x11 1.10.10-1
ii  gvfs 1.30.0-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpangoft2-1.0-01.40.3-2
ii  thunar-volman0.8.1-2
ii  tumbler  0.1.31-2+b3
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.12.0-4

Versions of packages thunar suggests:
pn  thunar-archive-plugin 
pn  thunar-media-tags-plugin  

-- no debconf information

Bug#839583: debian-reference: short package description of chinese translations mentions portuguese

[Beatrice Torracca]

Source: debian-reference
Severity: minor

Hi!

the short package description of binary packages
debian-reference-zh-tw and debian-reference-zh-cn is " Debian system
administration guide, Portuguese translation".

In both packages "Portuguese" should be replaced with "Chinese".

Thanks a lot for the work on this package,

beatrice

Bug#204975: [Build-common-hackers] Bug#204975: cdbs: postrm and postinst have useless call to ldconfig

[Loïc Minier]

Hi,

Re-reading this bug – filed 12 years ago – I have to agree with Joey Hess (and 
I find my own tone from 12 years ago pretty bad, sorry about that!): it’s not a 
good idea to rely on the contents of /etc/ld.so.conf.

It’s less big a deal than it used to be because of /etc/ld.so.conf.d/* which is 
where other packages would change the search path, but it’s still an issue 
because an admin might have changed the local config and this will affect 
package builds.

> Le 30 sept. 2016 à 02:42, Olly Betts  a écrit :
> $ /sbin/ldconfig -N -X -v -f /dev/null 2>/dev/null|sed 's,^\(/.*\):\( 
> (.*)\)\?$,\1,p;d’

This approach looks very good to me; here’s perhaps a lighter sed:
sed -n '/^\//s#:$##p’
(match lines leading with slash, remove trailing colon and print them)

However it might be worth bringing this discussion to Debian Policy as this 
currently said that /etc/ld.so.conf contents must be used.
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-ldconfig 


Another perhaps smarter approach would be to do away with postinst requirements 
entirely by installing a ldconfig file-based trigger in libc for *.so files 
under interesting directories. This would let libc define when to run libc’s 
ldconfig rather than having each shared library package carry a build-time and 
install time snippet…

Cheers,
- Loïc Minier

Bug#839584: cryptsetup: cryptroot hook for initramfs doesn't detect root within RAID

[Chuck Mason]

Package: cryptsetup
Version: 2:1.7.0-2
Severity: important

Dear Maintainer,

* What led up to the situation?
Configuring a machine with RAID and encrypted disks.

* What exactly did you do (or not do) that was effective (or ineffective)?
Begin by encrypting entire disks:
cryptsetup luksFormat /dev/sdc
cryptsetup luksFormat /dev/sdd
cryptsetup luksOpen /dev/sdc sdc_encrypted
cryptsetup luksOpen /dev/sdd sdd_encrypted

Create a raid array on the whole encrypted disk:
mdadm --create --verbose --level=1 /dev/md/hdd_storage --raid-devices=2 
/dev/mapper/sdc_encrypted /dev/mapper/sdd_encrypted
/usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf

Partition the raid array:
fdisk /dev/md/hdd_storage
...
w (write changes)
* Linux immediately recognizes new partition /dev/md127p1

Create a filesystem:
mkfs.ext4 /dev/md127p1

Using blkid, add /dev/sdc -> sdc_encrypted and /dev/sdd -> sdd_encrypted 
targets to /etc/crypttab
# 
sdc_encrypted /dev/disk/by-uuid/58560717-94f7-4a57-ae88-d83e16948969 none 
luks,timeout=30
sdd_encrypted /dev/disk/by-uuid/fc6fa717-83dc-44a3-8a09-de7585f70809 none 
luks,timeout=30

Using blkid, set /dev/md127p1 to be the root (/) in /etc/fstab

Output of blkid | grep md127p1:
/dev/md127p1: UUID="e084a1e0-f5bd-4342-ae87-a014561fce0c" TYPE="ext4" 
PARTUUID="2e7f7afa-b579-4b1f-83a8-c755708b9051"

After mounting /dev/md127p1 (and necessary /proc, /sys, /dev, etc.), 
update-initramfs does NOT detect an encrypted root partition.

* What was the outcome of this action?
Cryptsetup was not included in initrd and the machine does not complete boot.

* What outcome did you expect instead?
Cryptsetup should be included in initrd.

* More information:
It seems that get_fs_devices() in /usr/share/initramfs-tools/hooks/cryptroot 
only looks at /etc/crypttab for device UUIDs, when there are
other device UUIDs available in "blkid" that are available for use as a root 
mount.

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.6.0-1-amd64 root=/dev/sda3 ro quiet

-- /etc/crypttab
# 
sdc_encrypted /dev/disk/by-uuid/58560717-94f7-4a57-ae88-d83e16948969 none 
luks,timeout=30
sdd_encrypted /dev/disk/by-uuid/fc6fa717-83dc-44a3-8a09-de7585f70809 none 
luks,timeout=30

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda3 during installation
UUID=e084a1e0-f5bd-4342-ae87-a014561fce0c /   ext4
errors=remount-ro 0   1
# /boot was on /dev/sda2 during installation
UUID=85c8ca98-b0c4-48cc-a5be-334ea4597de5 /boot   ext4defaults  
  0   2
# /boot/efi was on /dev/nvme0n1p2 during installation
UUID=7293-2005  /boot/efi   vfatumask=0077  0   3

-- lsmod
Module  Size  Used by
nls_utf8   16384  1
nls_cp437  20480  1
vfat   20480  1
fat69632  1 vfat
dm_crypt   24576  3
algif_skcipher 20480  0
af_alg 16384  1 algif_skcipher
joydev 20480  0
btusb  45056  0
btrtl  16384  1 btusb
btbcm  16384  1 btusb
btintel16384  1 btusb
bluetooth 516096  5 btbcm,btrtl,btusb,btintel
snd_hda_codec_hdmi 45056  3
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
dm_mod106496  7 dm_crypt
snd_hda_codec_realtek86016  1
nouveau  1486848  1
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
intel_rapl 20480  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 188416  0
mxm_wmi16384  1 nouveau
video  40960  1 nouveau
snd_hda_intel  36864  0
iwlwifi   147456  0
kvm   561152  1 kvm_intel
ttm94208  1 nouveau
snd_hda_codec 135168  4 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
drm_kms_helper147456  1 nouveau
irqbypass  16384  1 kvm
snd_hda_core   81920  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
cfg80211  573440  1 iwlwifi
crct10dif_pclmul   16384  0
efi_pstore 16384  0
drm   360448  4 ttm,drm_kms_helper,nouveau
snd_hwdep  16384  1 snd_hda_codec
crc32_pclmul   16384  0
snd_pcm   106496  4 
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
sb_edac32768  0
snd_timer  32768  1 snd_pcm
serio_raw  16384  0
pcspkr 16384  0
efivars20480  1 efi_pstore
edac_core

Bug#838956: manpages-dev: Inconsistent documentation in NOTES section of "man wcstombs"

[Michael Kerrisk (man-pages)]

tags 838956 fixed-upstream
thanks

Thanks for this report. I've applied the patch below to the upstream man page.

Cheers,

Michael


diff --git a/man3/wcstombs.3 b/man3/wcstombs.3
index c787250..1f189be 100644
--- a/man3/wcstombs.3
+++ b/man3/wcstombs.3
@@ -112,8 +112,7 @@ current locale.
 .PP
 The function
 .BR wcsrtombs (3)
-provides a thread safe interface to
-the same functionality.
+provides a better interface to the same functionality.
 .SH SEE ALSO
 .BR mblen (3),
 .BR mbstowcs (3),


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Bug#204975: [debhelper-devel] Bug#204975: [Build-common-hackers] Bug#204975: cdbs: postrm and postinst have useless call to ldconfig

[Niels Thykier]

Loïc Minier:
> Hi,
> 
> [...]
> Another perhaps smarter approach would be to do away with postinst 
> requirements entirely by installing
> a ldconfig file-based trigger in libc for *.so files under interesting
directories. This would let
> libc define when to run libc’s ldconfig rather than having each shared
library package carry a
> build-time and install time snippet…
> 
> Cheers,
> - Loïc Minier
> 
> [...]

At the current time, we have migrated to activation triggers.  They are
still in each package, but it does avoid the shell snippets (and all the
related prerm+postinst scripts).

As for using a path trigger, I believe that was ruled out as they are
recursive.  The libc-bin package would have to declare an interest in
*all* of /usr/lib, which will generate tons of false-positives.  I
suspect it may also be a bit heavy on the dpkg side.

Thanks,
~Niels

Bug#780082: liferea: random crash (SIGABRT)

[Paul Wise]

On Sun, 2016-10-02 at 13:23 +0200, Paul Gevers wrote:

> One small important detail is missing :-) This dump indicates an
> assertion (first thread has g_assertion_message in it). There was a CLI
> output that probably explains the dump. This would be really helpful
> 
> I don't assume you still have this info (if you had it at all). If not,
> I propose we close this (and upstreams) bug report.

Unfortunately I do not have this info as I don't run it in a terminal :(

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#204975: [debhelper-devel] Bug#204975: [Build-common-hackers] Bug#204975: cdbs: postrm and postinst have useless call to ldconfig

[Loïc Minier]

> Le 2 oct. 2016 à 14:25, Niels Thykier  a écrit :
> As for using a path trigger, I believe that was ruled out as they are
> recursive.  The libc-bin package would have to declare an interest in
> *all* of /usr/lib, which will generate tons of false-positives.  I
> suspect it may also be a bit heavy on the dpkg side.

Indeed, it seems one has to specify a dir or specific file and one can not use 
a regexp.

https://anonscm.debian.org/cgit/dpkg/dpkg.git/tree/doc/triggers.txt 


- Loïc Minier

Bug#839585: wiki.debian.org: LDAP + Kerberos doesn't link to single Kerberos server guide

[John Lewis]

Package: wiki.debian.org
Severity: normal

Dear Maintainer,

https://wiki.debian.org/LDAP/Kerberos say that there are plenty of
guides for setting up a Kerberos server on Debian but doesn't link to a
single one.

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#838876: debian-reference: .xesssion

[Osamu Aoki]

Hi,

On Sat, Oct 01, 2016 at 10:00:49PM +0900, Osamu Aoki wrote:
...
> IGNORED vs. RESPECTED
> 
> This is important!

It may be easier to check how I updated on the web now.

https://www.debian.org/doc/manuals/debian-reference/ch07.en.html#_starting_the_x_window_system

Please note that you need to read full the 7.5 section to make sense.
Notably the following is importanr.

  This is essentially an execution of the first program which is found in
  the following order by the exec builtin command.

Then "~/.xsession" or "~/.Xsession" and new method respecting
x-session-manager etc. are different.  The RESPECTING one is good for
me.

Regards,
 
> Osamu

Bug#839586: show sometimes wrong cursor, makes program temporarily unusable

[W. Martin Borgert]

Package: quodlibet
Version: 3.7.0-1

This behaviour is not present in Debian stable, only in testing:

During usage, e.g. when changing views sometimes the cursor type
changes. I.e. instead of the Arrow cursor, it is the Ibeam
(often) one or Sizeall (less often).

The cursor is not wrong for the complete window, but only for a
specific view, e.g. the Queue or the Search view.

This is not only a cosmetic problem, because not only the look
of the cursor changes, but also its behaviour. E.g. selecting
tracks is no longer possible with the wrong cursor type.

This does not happen every time on usage, only once in a while.
The cursor stays in the wrong way for some time and goes back to
normal after some minutes of usage.

Maybe it is a incompatibility between quodlibet and the current
GTK+3 in testing?

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

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

Versions of packages quodlibet depends on:
ii  exfalso 3.7.0-1
ii  gir1.2-gst-plugins-base-1.0 1.8.3-1
ii  gir1.2-gstreamer-1.01.8.3-1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-audiosink]   1.8.3-1+b2
ii  gstreamer1.0-plugins-base   1.8.3-1
ii  gstreamer1.0-plugins-good [gstreamer1.0-audiosink]  1.8.3-1+b1
ii  gstreamer1.0-plugins-ugly   1.8.3-1
ii  gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]1.8.3-1+b1
ii  python  2.7.11-2
pn  python:any  

Versions of packages quodlibet recommends:
ii  gir1.2-gtksource-3.0 3.22.0-1
ii  gir1.2-keybinder-3.0 0.3.1-1
ii  gir1.2-soup-2.4  2.56.0-1
ii  gnome-shell [notification-daemon]3.22.0-1
ii  libgpod4 0.8.3-8
ii  media-player-info22-3
ii  notification-daemon  3.20.0-1
ii  python-dbus  1.2.4-1
ii  python-feedparser5.1.3-3
ii  python-pyinotify 0.9.6-1
ii  udisks   1.0.5-1+b1
ii  udisks2  2.1.7-2
ii  xfce4-notifyd [notification-daemon]  0.3.2-1

Versions of packages quodlibet suggests:
ii  gstreamer1.0-plugins-bad  1.8.3-1+b2

-- no debconf information

Bug#839459: [Pkg-swan-devel] Bug#839459: strongswan: FTBFS: Tests failures

[Yves-Alexis Perez]

On Sat, 2016-10-01 at 16:17 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[6]: *** [check-recursive] Error 1
> > make[6]: Leaving directory '/<>/src/libstrongswan'
> > Makefile:2131: recipe for target 'check' failed
> > make[5]: *** [check] Error 2
> > make[5]: Leaving directory '/<>/src/libstrongswan'
> > Makefile:520: recipe for target 'check-recursive' failed
> > make[4]: *** [check-recursive] Error 1
> > make[4]: Leaving directory '/<>/src'
> > Makefile:580: recipe for target 'check-recursive' failed
> > make[3]: *** [check-recursive] Error 1
> > make[3]: Leaving directory '/<>'
> > Makefile:869: recipe for target 'check' failed
> > make[2]: *** [check] Error 2
> > make[2]: Leaving directory '/<>'
> > dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> > debian/rules:210: recipe for target 'override_dh_auto_test' failed
> 
> If the failure looks somehow time/timezone related:
> Note that this rebuild was performed without the 'tzdata' package
> installed in the chroot. tzdata used be (transitively) part of
> build-essential, but it no longer is. If this package requires it to
> build, it should be added to build-depends. For the release team's
> opinion on this, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

The (really) relevant part is here:

>  Running case 'printf_hooks': ++-+-+
>  Failure in 'test_time_printf_hook': buf != time_data[_i].out ("Jan 01 
> 00:00:01 1970" != "Jan 01 01:00:01 1970") (suites/test_utils.c:766, i = 2)
>  Failure in 'test_time_printf_hook': buf != time_data[_i].out ("Jul 01 
> 13:43:16 2012" != "Jul 01 15:43:16 2012") (suites/test_utils.c:766, i = 4)
>Running case 'mark_from_string': +
>Running case 'signature_schemes_for_key': ++
>  Passed 18/19 'utils' test cases

so it might be tzdata related. I'll purge tzdata from my pbuilder chroot and
retry locally to see if I can reproduce.

Regards,
-- 
Yves-Alexis

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

Bug#839586: show sometimes wrong cursor, makes program temporarily unusable

[Christoph Reiter]

On Sun, Oct 2, 2016 at 3:01 PM, W. Martin Borgert  wrote:
> Package: quodlibet
> Version: 3.7.0-1
>
> This behaviour is not present in Debian stable, only in testing:

I've never seen the described behaviour with debian sid + quodlibet
under gnome-shell. Which DE/WM are you using? Do you use a trackpad,
trackpoint or mouse?

Bug#839587: sympa: please make the build reproducible

[Chris Lamb]

Source: sympa
Version: 6.2.16~dfsg-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], I noticed
that sympa could not be built reproducibly due to the repeated
use of a value in the "order" attribute.

This resulted in non-deterministic ordering in the sympa_database(5)
manpage.


Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/src/lib/Sympa/DatabaseDescription.pm 
b/src/lib/Sympa/DatabaseDescription.pm
index e1a2954..7d34804 100644
--- a/src/lib/Sympa/DatabaseDescription.pm
+++ b/src/lib/Sympa/DatabaseDescription.pm
@@ -152,7 +152,7 @@ my %full_db_struct = (
 'custom_attribute_subscriber' => {
 'struct' => 'text',
 'doc'=> 'FIXME',
-'order'  => 10,
+'order'  => 20,
 },
 
 },

Bug#835866: Icedove silently failing to send messages when OAuth is used for SMTP

[Hauke Mehrtens]

I just installed icedove version 45.3.0-1 from sid and there the problem
is fixed for me.

Hauke

Bug#839588: debhelper: make: dh: Command not found

[Hideki Yamane]

package: debhelper
version: 10.1
severity: important

Hi,

 debhelper changes its behavior from 10 to 10.1 and some of my packages
 cannot build now.

> $ gbp buildpackage --git-pbuilder
> gbp:info: Tarballs 'fonts-vlgothic_20141206.orig.tar.xz' not found at 
> '../tarballs/'
> gbp:info: Creating fonts-vlgothic_20141206.orig.tar.xz from 
> 'upstream/20141206'
> gbp:info: Building with (cowbuilder) for sid
> gbp:info: Exporting 'HEAD' to '/tmp/build-area/fonts-vlgothic-tmp'
> gbp:info: Moving '/tmp/build-area/fonts-vlgothic-tmp' to 
> '/tmp/build-area/fonts-vlgothic-20141206'
> Building with cowbuilder for distribution sid
> I: using cowbuilder as pbuilder
> dpkg-buildpackage: info: source package fonts-vlgothic
> dpkg-buildpackage: info: source version 20141206-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Hideki Yamane 
>  dpkg-source --before-build fonts-vlgothic-20141206
>  fakeroot debian/rules clean
> dh  clean
> make: dh: Command not found
> debian/rules:5: recipe for target 'clean' failed
> make: *** [clean] Error 127
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> gbp:error: 'git-pbuilder' failed: it exited with 2

 Is there any suggestion for it?

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane

Bug#798080: mysql-server-5.6: service stop hangs forever on systemd

[Jérémie]

Any update on this issue ?

Bug#839588: [debhelper-devel] Bug#839588: debhelper: make: dh: Command not found

[Niels Thykier]

Control: forcemerge 839557 -1

Hideki Yamane:
> package: debhelper
> version: 10.1
> severity: important
> 
> Hi,
> 
>  debhelper changes its behavior from 10 to 10.1 and some of my packages
>  cannot build now.
> 
>> [...]
> 
>  Is there any suggestion for it?
> 

Hi,

Please use debhelper/10.2.1, which was uploaded to unstable earlier
today. :)

Thanks,
~Niels

Bug#839588: [debhelper-devel] Bug#839588: debhelper: make: dh: Command not found

[Axel Beckert]

Control: forcemerge 839557 -1

Hi,

Hideki Yamane wrote:
> package: debhelper
> version: 10.1
[...]
>  debhelper changes its behavior from 10 to 10.1 and some of my packages
>  cannot build now.
[...]
>  Is there any suggestion for it?

Please upgrade to debhelper/10.2.1.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#839511: zeroinstall-injector: FTBFS: Tests failures

[Thomas Leonard]

On 1 October 2016 at 15:17, Lucas Nussbaum  wrote:
> Source: zeroinstall-injector
> Version: 2.12-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161001 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>>
>> Error 'New feed's modification time is before old version!
>> Interface: http://foo/
>> Old time: 2013-09-25T11:57:28Z
>> New time: 2013-09-25T11:43:10Z
>> Refusing update.' does not match regexp 'New feed's modification time is 
>> before old version!
>> Interface: http://foo/
>> Old time: 2013-09-25T12:57:28Z
>> New time: 2013-09-25T12:43:10Z
>> Refusing update.'
>>
>> --
>> Ran: 295 tests in: 1.12 seconds.
>> FAILED: Cases: 295 Tried: 295 Errors: 1 Failures: 0 Skip:  4 Todo: 0 
>> Timeouts: 0.
>>
>> Makefile:29: recipe for target 'test' failed
>
> If the failure looks somehow time/timezone related:
> Note that this rebuild was performed without the 'tzdata' package
> installed in the chroot. tzdata used be (transitively) part of
> build-essential, but it no longer is. If this package requires it to
> build, it should be added to build-depends. For the release team's
> opinion on this, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

OK, I've added a build-dep on tzdata and uploaded a new version to mentors:

  https://mentors.debian.net/package/zeroinstall-injector

  
https://mentors.debian.net/debian/pool/main/z/zeroinstall-injector/zeroinstall-injector_2.12-2.dsc

I've also fixed the issue upstream (the Z suffix indicates that these
times are supposed to be UTC, not local time):

  
https://github.com/0install/0install/commit/3fd0b1f25bb8af402a9f44ce915fe9518df6af8d

Thanks,


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

Bug#839589: valgrind: callgrind: annoying and useless 'brk segment overflow' warning

[Eugene V. Lyubimkin]

Package: valgrind
Version: 1:3.12.0~svn20160714-1+b1
Severity: normal

Dear Maintainer,

I discovered that in latest version available in testing, Valgrind's Callgrind
started to output a lot of annoying warnings which practically hides out
the important information.

Does not happen in e.g. memcheck or DRD.

Consider the following:
---8<--
$ cat main.cpp
#include 
#include 

int main()
{
std::size_t total = 0;
std::vector v;
for (std::size_t i = 0; i < 1; ++i)
{
v.push_back(new char[i]);
total += i;
if (i % 1000 == 0)
std::cout << "Allocated: " << total << std::endl;
}
for (auto e: v)
{
delete[] e;
}
}

$ cat Makefile 
all:
g++ -O2 -Wall main.cpp -o main.e
$ valgrind --tool=callgrind ./main.e
==32597== Callgrind, a call-graph generating cache profiler
==32597== Copyright (C) 2002-2015, and GNU GPL'd, by Josef Weidendorfer et al.
==32597== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==32597== Command: ./main.e
==32597== 
==32597== For interactive control, run 'callgrind_control -h'.
Allocated: 0
Allocated: 500500
Allocated: 2001000
Allocated: 4501500
Allocated: 8002000
==32597== brk segment overflow in thread #1: can't grow to 0x4a3a000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
Allocated: 12502500
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
Allocated: 18003000
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
Allocated: 24503500
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
Allocated: 32004000
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3b000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3c000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3c000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3c000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3c000
==32597== (see section Limitations in user manual)
==32597== brk segment overflow in thread #1: can't grow to 0x4a3c000
==32597== (see section Limitations in user manual)
==32597== 

Bug#839590: Bus error when accessing MBR partition records

[James Clarke]

Package: mdadm
Version: 3.4-4
Tags: patch
Control: -1 forwarded http://marc.info/?l=linux-raid&m=147515212602202
X-Debbugs-Cc: debian-sp...@lists.debian.org
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hi,
When mdadm tries to examine MBR partition records (such as when creating
an array using already-formatted disks), it does so with an unaligned
pointer, which leads to a bus error (SIGBUS) on sparc64. Please see the
patch I have submitted upstream, which makes sure the accesses always go
through boot_sect, since it is of type `struct MBR', which is the packed
containing struct, and so the compiler will generate the correct code to
perform the unaligned accesses when needed.

Regards,
James


signature.asc
Description: PGP signature

Bug#837895: Having the same issue

[Gerald Anzalone]

I upgraded sid last night right before I shut the machine down. This
morning found it in the exact condition described here. xdm appears to work
fine.

Bug#839591: Update keytab-lilo to work on modern Debian systems

[Raphaël Halimi]

Package: lilo
Version: 1:24.2-2
Severity: minor
Tags: patch

Hi,

keytab-lilo is useful to people maintaining a PXE server, because
syslinux uses the lilo keytable format for its keymaps.

Here is a patch to make keytab-lilo work out-of-the-box (provided you
add a Recommends or Suggests on console-data).

Regards,

-- 
Raphaël Halimi

Description: Various fixes for keytab-lilo
 This patch updates keytab-lilo to work on modern Debian systems:
   - Support for kbd 2.0.3 format (from Olivier Brunel, see
 http://www.syslinux.org/archives/2015-December/024690.html)
   - Use new keymaps ".kmap" extension (from syslinux upstream)
   - Add headers (from syslinux upstream)
Author: Raphaël Halimi 
Origin: other
Last-Update: 2016-10-02
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/keytab-lilo.pl
+++ b/keytab-lilo.pl
@@ -1,4 +1,8 @@
 #!/usr/bin/perl
+
+eval { use bytes; };
+eval { binmode STDOUT; };
+
 $DEFAULT_MAP = "us";
 $DEFAULT_EXT = ".kmap";
 
@@ -6,8 +10,8 @@
 {
 print STDERR
   "usage: $0 [ -p old_code=new_code ] ...\n".
-  (" "x(8+length $0))."[path]default_layout[.map] ] ".
-  "[path]kbd_layout[.map]\n";
+  (" "x(8+length $0))."[path]default_layout[.kmap] ] ".
+  "[path]kbd_layout[.kmap]\n";
 exit 1;
 }
 
@@ -44,9 +48,9 @@
 $empty = 1;
 while () {
 	chop;
-	if (/^(static\s+)?u_short\s+(\S+)_map\[\S*\]\s+=\s+{\s*$/) {
+	if (/^(static\s+)?(u_|unsigned )short\s+(\S+)_map\[\S*\]\s+=\s+{\s*$/) {
 	die "active at beginning of map" if defined $current;
-	$current = $pfx.":".$2;
+	$current = $pfx.":".$3;
 	next;
 	}
 	undef $current if /^};\s*$/;



signature.asc
Description: OpenPGP digital signature

Bug#839593: cme: support (or switch to) UTF-8 encoding

[gregor herrmann]

Package: cme
Version: 1.014-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I just tried to help someone to add themselves to Uploaders
programmatically; unfortunately their first name contains a non-ascii
character (the following is a test name, just the 'í' is taken from
the real one).

Both

% cme modify dpkg-control 'source Uploaders:.insort("María Prueba 
")'

and

% perl -MConfig::Model=cme -e 'cme("dpkg-control")->modify("source 
Uploaders:.insort(\"María Prueba \")");'

result in a broken 'í', which gets mangled into 'Ã', probably because
perl's default encoding is still latin1.

The following works for me:

% perl -Mutf8 -MConfig::Model=cme -e 'cme("dpkg-control")->modify("source 
Uploaders:.insort(\"María Prueba \")");'

(also with utf8::all but apparently utf8 is enough).


IIRC, files in debian/ should be UTF-8 encoded, so I think it would
make sense to assume UTF-8 as the default encoding, or at least add a
switch to cme(1) or read the encoding from the terminal or something
like this.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX8Rc+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGqrIP/2cOm0SWq0M+ABmWLXIUj0rx
2IwceeaBVbfBlOTUbBR7GkkBkD80cnHQmJ9nI3t+RKwcK6Ey8hGLtvMqQLbiRaBg
Bg/zdlXsIac5YkDIU6/pLjnt3Kez8PWfQlvX8OkZmshXMjTq7XMycBN3UcBGgKnn
bqy8d+OhD3NlC6a/QElZ/4wa0uyUc+obYlXiEyHxfD7rUn4v0UwSlXC9vygylt0u
aVU49kgUWFZvy1ePcGpyrXdg2/Rk50KN+rxD+b/xJNTHOdUu5F80/EdKUWhfz1T7
SmND40RPEdtf3PVxIXoEDky1bRBZVkBWnD5u8eEVNCKfyOBNV+Osg32iJcBe3I9V
BTWCTdeX5Z+P9n7ZPqOAGG1Js2cAEabl0aJNZjHZ4ph8o1p+RtP63cIA2LiP3oFC
CX3RJmmjuYlnhGJZepsqSMmZ8D7ccFOHguKJ4l/0VEfVHV2Xtc3BL2QIHxE1PCIU
UW9j4YeLA7MI8PYwLfzm7eHMZJ/B+fPQvX2px8lzdJ/xn5rNdhUNtZvBZ5mk7SQS
/2tWrh5VT5RUk9MuSrOcVKFRgoYyG+x0eDn5MJJvfRuSyFGN2dqWRg/oXANOBTWQ
BF7h+QTvWaJlWEhFUW71E3PWeyif0LWsePLRCSOQmvwZggr1MaEqaoOnyaSoLD06
epMa2oGBZYa19YSF+VSu
=LNEo
-END PGP SIGNATURE-

Bug#839592: steam: Steam Fatal Error

[Brainwall]

Package: steam
Version: 1.0.0.52-5
Severity: important

Dear Maintainer,

Steam no start only show table FATAL ERROR: FAILED TO LOAD STEAMUI.SO

I try reinstall steam 4x, remove/delete all config file, but no helping me.

Here is screenshot: https://postimg.org/image/5qhbvzdkd/

Debian 9 stretch 'testing' 64bit



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

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

Versions of packages steam depends on:
ii  debconf [debconf-2.0] 1.5.59
ii  libc6 2.24-3
ii  libgl1-mesa-dri   12.0.3-1
ii  libgl1-mesa-glx   12.0.3-1
ii  libgpg-error0 1.24-1
ii  libstdc++66.1.1-11
ii  libtxc-dxtn-s2tc0 [libtxc-dxtn0]  0~git20131104-1.1
ii  libudev1  231-4
ii  libx11-6  2:1.6.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages steam recommends:
ii  fonts-liberation  1:1.07.4-2
ii  gnome-terminal [x-terminal-emulator]  3.22.0-2
ii  libxss1   1:1.2.2-1
ii  zenity3.22.0-1

Versions of packages steam suggests:
pn  steam-devices  

-- debconf information:
* steam/question: I AGREE
* steam/license:
  steam/purge:

Bug#839548: Reports "No certificate was found" on working server

[Philipp Kern]

severity -1 normal
thanks

On 2016-10-01 22:46, Pietro Battiston wrote:
Since I upgraded gobby to 0.5.0-8 (and some libraries with it), when I 
try to
connect to my server, it fails with the following error message: "The 
server

certificate is not trusted: No certificate was found.".

At the same time, in the terminal I see the following popping up:

** (gobby:31425): WARNING **: Failure during SRV record lookup: No 
address

associated with name
Will go on with normal A/ lookup

The server works perfectly with gobby 0.5.0 from a Windows machine, and 
used to

work perfectly with the previous version of the Debian package.


How did you start the infinote server? You might have turned off 
security there? Did you actually install a cert? The WARNING does not 
seem relevant to me.


Kind regards
Philipp Kern

Bug#838372: stterm: New upstream version

[Mark Nipper]

Package: stterm
Version: 0.6-1
Followup-For: Bug #838372

I'd like to second the request to package 0.7.

However, as the latest tmux (currently in unstable, 2.3) supports true
color with stterm, I'd like to vote against including the scrollback
patch in the base stterm, since it's antithetical to the design of
stterm.  If upstream includes it, then obviously this changes.  If it
was going to be considered, maybe a separate version of the package
would make the most sense (stterm-scroll or some such).

Bug#839594: linuxlogo requires root privs to read amount of system ram

[William L. DeRieux IV]

Package: linuxlogo
Version: 5.11-8.1
Severity: normal
Tags: upstream

Dear Maintainer,

when linuxlogo (5.11-8.1) is executed as a normal user it reports that the
system has 128TB of ram; when it is run as root it will show the correct
amount.

The issue resides in file (ibsysinfo-0.2.2/Linux/sysinfo_linux.c)
In function get_mem_size_iomem is tries to read from /proc/iomem.
As a normal user all of the values will be -.

It should read the value for MemTotal from /proc/meminfo as this does not
require root privalges.

I don't think runing linuxlogo as root is neccessary or a good idea.



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

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

Versions of packages linuxlogo depends on:
ii  libc6 2.24-3
ii  lsb-base  9.20160629

linuxlogo recommends no packages.

linuxlogo suggests no packages.

-- no debconf information

Bug#839548: Reports "No certificate was found" on working server

[Pietro Battiston]

Il giorno dom, 02/10/2016 alle 16.24 +0200, Philipp Kern ha scritto:
> [...]
> > The server works perfectly with gobby 0.5.0 from a Windows machine,
> > and 
> > used to
> > work perfectly with the previous version of the Debian package.
> 
> How did you start the infinote server? You might have turned off 
> security there? Did you actually install a cert? [...]
> 

The server was started with the following config file:

[infinoted]
security-policy=require-tls  # commenting this doesn't help
certificate-file=/home/pietro/.config/infinoted.cert
password=EDITED
key-file=/home/pietro/.config/infinoted.key


The cert was generated by the server itself (I tried to generate a new
one, no difference).

Then again, everything works smoothly with the same server from the
same (upstream) version of gobby ran in Windows.

Pietro

Bug#839595: flash-kernel: Please add support for SolidRun Clearfog

[Christoph Egger]

Package: flash-kernel
Version: 3.69
Severity: wishlist

Hi!

Please consider adding clearfog support. The system works fine with
mainline u-boot + kernel. Hopefully I have added all necessary
information below:

| Machine: SolidRun Clearfog A1
| Kernel-Flavors: armmp armmp-lpae
| DTB-Id: armada-388-clearfog.dtb
| Required-Packages: u-boot-tools

| # fw_printenv
| baudrate=115200
| bootargs=console=ttyS0,115200n8 rootdelay=10 bootwait=10 rootwait=10 
root=/dev/mmcblk0p1
| bootcmd=ext4load mmc 0:2 0x10 dtb ; ext4load mmc 0:2 0x80 
vmlinuz-4.7.0-1-armmp ; ext4load mmc 0:2 0x180 
initrd.img-4.7.0-1-armmp.uimage ; bootz 0x80 0x180 0x10
| dnsip=10.100.3.2
| eth1addr=48:5b:39:c9:ec:74
| eth2addr=48:5b:39:c9:ec:75
| eth3addr=48:5b:39:c9:ec:76
| ethact=ethernet@3
| ethprime=egiga1
| fdt_high=0x1000
| fdtcontroladdr=3fb51e58
| fileaddr=10
| filesize=4961
| gatewayip=10.100.3.1
| initrd_high=0x1000
| ipaddr=10.100.3.3
| netmask=255.255.255.224
| serverip=10.100.3.2
| stderr=serial@12000
| stdin=serial@12000
| stdout=serial@12000
| bootdelay=5

| # cat /etc/fw_env.config
| /dev/mmcblk0 0xf 0x1 0x1000

Regards

  Christoph

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

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

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  devio  1.2-1.2
ii  initramfs-tools0.125
ii  linux-base 4.5
ii  mtd-utils  1:1.5.2-1
ii  ucf3.0036

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2016.03+dfsg1-6

flash-kernel suggests no packages.

-- debconf information excluded

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

Bug#830997: release.debian.org: Permission to consider dpkg-buildpackage -A bugs as RC

[Emilio Pozuelo Monfort]

On 11/09/16 14:50, Santiago Vila wrote:
> On Sun, 11 Sep 2016, Niels Thykier wrote:
> 
>> On Mon, 1 Aug 2016 23:23:14 +0200 (CEST) Santiago Vila 
>> wrote:
>>> Greetings.
>>>
>>> I've finally raised to "serious" all the known bugs regarding
>>> "dpkg-buildpackage -A" that were still open.
>>>
>>> Thanks.
>>
>> AFAICT, this bug is now resolved - closing accordingly. :)
> 
> It is resolved in the sense it was agreed to make this RC,
> but I still expected the release policy to be updated accordingly:
> 
> https://release.debian.org/stretch/rc_policy.txt
> 
> before closing this report.

I looked at that when I acked this, but I concluded that the policy already
includes arch:all as there really is nothing arch:any specific. My attempts at
mentioning arch:all only made the text too complicated.

I think things are fine as is.

Cheers,
Emilio

Bug#839547: [pkg-gnupg-maint] Bug#839547: gnupg: unable to decrypt file

[Daniel Kahn Gillmor]

Hi Paul--

On Sat 2016-10-01 16:16:39 -0700, Paul Rogé wrote:
>
>>   dpkg -l 'pinentry-*'
>
> pinentry-gnome3 0.9.7-5 amd64
> pinentry-gtk2 0.9.7-5 amd64
>
>>   dpkg -S $(readlink -f $(which pinentry))
>
> pinentry-gnome3: /usr/bin/pinentry-gnome3
>
>> are you running this from a graphical environment (e.g. in an Xterm or
>> something), from a virtual terminal, or somewhere else?
>> 
> I am running this from a graphical environment (rxvt-unicode [9.22-1+b1
> amd64]), but the same problem occurs from the console.
>
>> If you do have pinentry installed, does it show you a prompt if you run
>> it directly?
>
> This is what I get following your instructions:
>
> OK Pleased to meet you
> getpin
> D asd
> OK
> bye
> OK closing connection

great, this all sounds reasonable and correct, so pinentry is *not* the
problem here.

the next step for debugging might be to see what's going on with your
gpg-agent, which is where the secret key gets used.

Please try increasing the logging in gpg-agent and seeing if there's a
clue in there.  You can do this by adding the following lines to
~/.gnupg/gpg-agent.conf (note that you should replace the "1000" below
with whatever your user id number is):

debug-level advanced
debug-pinentry
log-file /run/user/1000/gpg-agent.log

and then restarting the agent with this command:

gpg-connect-agent reloadagent /bye

Then retry the decryption operation:

gpg --decrypt file.gpg

and see what ends up in that log.  Feel free to send it to me privately
if you aren't sure if there's anything troubling in it, or to redact any
parts you don't want public (e.g. replace any string of
arbitrary-looking hexadecimal with XXX) and send it to this bug
report.

Thanks for bearing with this debugging process!

   --dkg




signature.asc
Description: PGP signature

Bug#839289: RFS: pnmixer/0.7-1 [ITP] -- Simple mixer application for system tray

[Gianfranco Costamagna]

tags 839289 moreinfo
thanks

Bug#833741: Sv: Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google.

[Kristian Klausen]

Hello


I have created a patch while implement this (see attachment).

This should also fix that it break 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839543), every time Google 
change something regarding the Chrome apt repository.


- Kristian Klausen



Fra: Bart Martens 
Sendt: 8. august 2016 18:48
Til: James C; 833...@bugs.debian.org
Emne: Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from 
Adobe instead of Google.

On Mon, Aug 08, 2016 at 11:11:57PM +1200, James C wrote:
> Package: pepperflashplugin-nonfree
> Version: 1.8.1
> Severity: wishlist
>
> Dear Maintainer,
>
> Apparently Adobe now has Pepper Flash available for download from their site.
> This is just Pepper Flash, not the whole Chrome browser.
> Also, an update to the 32-bit version seems to be available.
> See:
> http://forum.mepiscommunity.org/viewtopic.php?t=40254

Indeed.

>
> (This was mentioned in the discussion for #831058,
> but I think it deserves a new bug report.)

I agree, thanks.

>
> I'm not sure if this counts as a bug, so I've marked it wishlist,

Perfect.

> but if it was possible to switch to downloading from the Adobe site,
> it would speed up the download, and make the 32-bit version available again.

Yes, I'm considering that.

Regards,

Bart Martens

--- a/update-pepperflashplugin-nonfree	2016-10-02 16:05:04.678209065 +0200
+++ b/update-pepperflashplugin-nonfree	2016-10-02 16:48:31.644832357 +0200
@@ -30,7 +30,7 @@
 	exit 1
 }
 
-[ `id -u` = "0" ] || die_hard "must be root"
+[ "$(id -u)" = "0" ] || die_hard "must be root"
 
 show_usage() {
 	echo "Usage:"
@@ -43,18 +43,15 @@
 	exit 1
 }
 
-getopt_temp=`getopt -o iusfvq --long install,uninstall,status,fast,verbose,quiet,beta,unstable,unverified \
-	-n 'update-pepperflashplugin-nonfree' -- "$@"` || show_usage
+getopt_temp="$(getopt -o iusfvq --long install,uninstall,status,verbose,quiet \
+	-n 'update-pepperflashplugin-nonfree' -- "$@")" || show_usage
 eval set -- "$getopt_temp" || show_usage
 
 ACTION=none
-fast=no
 verbose=no
 quiet=no
-variant=stable
-verified=yes
 
-while [ true ]
+while true
 do
 	case "$1" in
 		-i|--install)
@@ -69,10 +66,6 @@
 			ACTION="--status"
 			shift
 			;;
-		-f|--fast)
-			fast=yes
-			shift
-			;;
 		-v|--verbose)
 			verbose=yes
 			shift
@@ -81,18 +74,6 @@
 			quiet=yes
 			shift
 			;;
-		--beta)
-			variant=beta
-			shift
-			;;
-		--unstable)
-			variant=unstable
-			shift
-			;;
-		--unverified)
-			verified=no
-			shift
-			;;
 		--)
 			shift
 			break
@@ -104,111 +85,31 @@
 	esac
 done
 
-[ "$ACTION" != "none" -a $# -eq 0 ] || show_usage
+([ "$ACTION" != "none" ] && [ $# -eq 0 ]) || show_usage
 [ "$quiet" != "yes" ] || verbose=no
 
 [ "$verbose" != "yes" ] || echo "options : $getopt_temp"
 
-latestfile=latest-$variant-verified.txt
-[ "$verified" != "no" ] || latestfile=latest-$variant.txt
-
-UNPACKDIR=`mktemp -d /tmp/pepperflashplugin-nonfree.XX` || die_hard "mktemp failed"
-echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia"
-cd "$UNPACKDIR" || die_hard "cd failed"
-
-[ "$verbose" != "yes" ] || echo "temporary directory: $UNPACKDIR"
-
-do_cleanup() {
-	[ "$verbose" != "yes" ] || echo "cleaning up temporary directory $UNPACKDIR ..."
-	cd /
-	echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia"
-	rm -rf "$UNPACKDIR"
-}
-
 die_hard_with_a_cleanup() {
 	return_0
-	do_cleanup
 	die_hard "$1"
 }
 
 trap "die_hard_with_a_cleanup interrupted" INT
 
-cachedir=/var/cache/pepperflashplugin-nonfree
-
-wgetquiet=' -q '
-wgetfast='-t 3 -T 15 '
-wgetalways=' -nd -P . '
-wgetprogress=' -v --progress=dot:default '
-
-if [ "$ACTION" = "--install" -o "$ACTION" = "--status" ]
+if [ "$ACTION" = "--install" ] || [ "$ACTION" = "--status" ]
 then
-	installed=`strings /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"`
-
-	[ ! -f $cachedir/$latestfile ] || [ `wc -l $cachedir/$latestfile | cut -f 1 -d ' '` -eq 2 ] || rm $cachedir/$latestfile
-
-	if [ -f $cachedir/$latestfile ]
-	then
-		chromeversion=`head -n 1 $cachedir/$latestfile`
-		flashversion=`tail -n 1 $cachedir/$latestfile`
+	arch=""
+	if [ "$(dpkg --print-architecture)" = "amd64" ]; then
+		arch="x86-64"
+	elif [ "$(dpkg --print-architecture)" = "i386" ]; then
+		arch="x86-32"
 	else
-		chromeversion=0
-		flashversion=0
+		die_hard_with_a_cleanup "unsupported architectures"
 	fi
 
-	mkdir -p var/lib/apt/lists var/cache/apt/archives etc/apt/apt.conf.d etc/apt/preferences.d
-
-	cat > apt.conf <<-EOF
-	Dir ".";
-	Dir::Etc::trusted "pubring.gpg";
-	Debug::NoLocking "true";
-	APT::Sandbox::User "root";
-	Dir::State::Status "/var/lib/dpkg/status";
-	EOF
-
-	arch=`dpkg --print-architecture`
-
-	cat > etc/apt/sources.list <<-EOF
-	deb [arch=$arch] http://dl.google.com/linux/chrome/deb/ stable main
-	EOF
-
-	gpg --quiet --no-permission-warning --homedir "etc/apt" --import /usr/lib/pepperflashplugin-nonf

Bug#839594: Update

[William L. DeRieux IV]

I just realized that the problem is not necessarily with 
get_mem_size_iomem()
-- but the issue still requires root privileges to be able to read the 
system ram.

Bug#839596: Please provide keytab-lilo in its own package

[Raphaël Halimi]

Package: lilo
Version: 1:24.2-2
Severity: wishlist
Tags: patch

Hi,

keytab-lilo is useful to people maintaining a PXE server, because
syslinux uses the lilo keytable format for its keymaps.

Installing LILO just to use the keytab-lilo script is far from
convenient, so here is a patch making keytab-lilo available in its own
package.

Regards,

-- 
Raphaël Halimi
diff --git a/debian/control b/debian/control
index 687ac31..ab494fb 100644
--- a/debian/control
+++ b/debian/control
@@ -36,3 +36,15 @@ Description: LInux LOader - Documentation for the classic OS boot loader
  .
  This package contains the old HTML and README documentations of lilo
  version 21.5 (of year 2000).
+
+Package: keytab-lilo
+Architecture: all
+Depends: perl, console-data, ${misc:Depends}
+Description: LInux LOader - compile keytables files for use with LILO
+ You can use LILO to manage your Master Boot Record (with a simple text 
+ screen, text menu or colorful splash graphics) or call LILO from other 
+ Boot-Loaders to jump-start the Linux kernel.
+ .
+ This package contains the keytab-lilo tool, which is a Perl script that can
+ compile keytable files to use with LILO and other tools (for example SYSLINUX,
+ which uses the same keytable format).
diff --git a/debian/keytab-lilo.dirs b/debian/keytab-lilo.dirs
new file mode 100644
index 000..236670a
--- /dev/null
+++ b/debian/keytab-lilo.dirs
@@ -0,0 +1 @@
+usr/sbin
diff --git a/debian/keytab-lilo.install b/debian/keytab-lilo.install
new file mode 100644
index 000..c7a73f8
--- /dev/null
+++ b/debian/keytab-lilo.install
@@ -0,0 +1 @@
+usr/sbin/keytab-lilo
diff --git a/debian/keytab-lilo.manpages b/debian/keytab-lilo.manpages
new file mode 100644
index 000..b53d61e
--- /dev/null
+++ b/debian/keytab-lilo.manpages
@@ -0,0 +1 @@
+man/keytab-lilo.8
diff --git a/debian/lilo.install b/debian/lilo.install
index fbbeb91..89b5eb1 100644
--- a/debian/lilo.install
+++ b/debian/lilo.install
@@ -1,6 +1,5 @@
 sbin/lilo
 usr/sbin/mkrescue
-usr/sbin/keytab-lilo
 usr/sbin/liloconfig
 usr/sbin/lilo-uuid-diskid
 etc/kernel/post*
diff --git a/debian/lilo.manpages b/debian/lilo.manpages
index 23864c9..2ac0e7e 100644
--- a/debian/lilo.manpages
+++ b/debian/lilo.manpages
@@ -1,4 +1,3 @@
-man/keytab-lilo.8
 man/lilo.8
 man/lilo.conf.5
 man/mkrescue.8


signature.asc
Description: OpenPGP digital signature

Bug#827894: Segfault on start

[Enrico Zini]

On Sun, Oct 02, 2016 at 01:14:47PM +0200, Paul Gevers wrote:

> On 12-08-16 22:55, Paul Gevers wrote:
> > Upstream is requesting a backtrace with debugging symbols (for now,
> > rather than having the database) because it can be shared publicly. Are
> > you in the position to create that? (If you are fine with it, please
> > follow-up directly in the upstream bug report).
> Ping?

Probably not. The liferea config directory I backed up back then was
~/.liferea-1.8 while now in testing I have liferea 1.10 with
configuration in .config/liferea and .cache/liferea.

I've restored what I thought were the right pieces from my backup in
those directories, and I couldn't reproduce the crash.

Feel free to close this bug then, I'm not anymore in a position to
reproduce it.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#839302: libfile-slurp-perl: FTBFS: Tests failures

[gregor herrmann]

Control: tag -1 + confirmed patch

On Sat, 01 Oct 2016 10:43:40 +0200, Lucas Nussbaum wrote:

> Relevant part (hopefully):
> > BEGIN failed--compilation aborted at t/utf8.t line 12.
> > # Looks like your test exited with 2 before it could output anything.
> > t/utf8.t .. 
> > Dubious, test returned 2 (wstat 512, 0x200)
> > Failed 4/4 subtests 
> > t/write_file_win32.t .. ok
> > 
> > Test Summary Report
> > ---
> > t/utf8.t(Wstat: 512 Tests: 0 Failed: 0)
> >   Non-zero exit status: 2
> >   Parse errors: Bad plan.  You planned 4 tests but ran 0.
> > Files=29, Tests=296,  3 wallclock secs ( 0.08 usr  0.02 sys +  1.04 cusr  
> > 0.14 csys =  1.28 CPU)
> > Result: FAIL
> > Failed 1/29 test programs. 0/296 subtests failed.
> > Makefile:823: recipe for target 'test_dynamic' failed

The relevant line was exactly one line before the quoted part :)

You tried to plan twice at t/utf8.t line 10.
BEGIN failed--compilation aborted at t/utf8.t line 12.
# Looks like your test exited with 2 before it could output anything.
t/utf8.t .. 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 4/4 subtests 

The problem seems to be that t/utf8.t (created in
debian/patches/01-binmode) has:

use Test::More tests => 4;
[..]
BEGIN {
   plan skip_all => "Newer Perl doesn't like sysread with utf8 binmode"
   if $] >= 5.024000;
}


After removing the test count from the use statement and adding a
plan later, this works. Alternatively done_testing() should work as
well.


Patch attached, which implements the former option.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Featuring The Dubliners, The Fureys And Davey Arthur Etc.: Spanish 
Lady, Paddy Reilly
diff -Nru libfile-slurp-perl-.19/debian/changelog libfile-slurp-perl-.19/debian/changelog
--- libfile-slurp-perl-.19/debian/changelog	2016-07-24 13:57:07.0 +0200
+++ libfile-slurp-perl-.19/debian/changelog	2016-10-02 17:06:17.0 +0200
@@ -1,3 +1,12 @@
+libfile-slurp-perl (.19-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS: Tests failures": update debian/patches/01-binmode to 'plan'
+only once.
+(Closes: #839302)
+
+ -- gregor herrmann   Sun, 02 Oct 2016 17:06:17 +0200
+
 libfile-slurp-perl (.19-5) unstable; urgency=medium
 
   * updated tests and docs to indicate that the combo of binmode :utf8
diff -Nru libfile-slurp-perl-.19/debian/patches/01-binmode libfile-slurp-perl-.19/debian/patches/01-binmode
--- libfile-slurp-perl-.19/debian/patches/01-binmode	2016-07-24 13:55:57.0 +0200
+++ libfile-slurp-perl-.19/debian/patches/01-binmode	2016-10-02 17:06:17.0 +0200
@@ -30,9 +30,9 @@
 +Arabic: ڐڡڠڟڞ
 --- /dev/null
 +++ b/t/utf8.t
-@@ -0,0 +1,45 @@
+@@ -0,0 +1,46 @@
 +#!/usr/bin/perl
-+use Test::More tests => 4;
++use Test::More;
 +use strict; 
 +use File::Slurp;
 +use Encode qw/encode_utf8/;
@@ -43,6 +43,7 @@
 +	plan skip_all => "Newer Perl doesn't like sysread with utf8 binmode"
 +			if $] >= 5.024000;
 +}
++plan tests => 4;
 +
 +my $digest = 'e30ffef9b0c5623bc1ddd1ba73302f14';
 +


signature.asc
Description: Digital Signature

Bug#839597: update golang-github-dgrijalva-jwt-go to new upstream release

[Pirate Praveen]

package: golang-github-dgrijalva-jwt-go
version: 2.6.0-1
severity: wishlist

I would like to use this package instead of the embedded copy in
gitlab-workhorse, but it needs 3.0.0 version. Please update the package.



signature.asc
Description: OpenPGP digital signature

Bug#839598: unable to build gitlab-workhorse with gccgo-6

[Pirate Praveen]

package: gccgo-6
version: 6.2.0-5
severity: serious
justification: this is causing ftbfs on powrpc

src/gitlab.com/gitlab-org/gitlab-workhorse/vendor/github.com/getsentry/raven-go/client.go:25:30:
error: import file 'github.com/certifi/gocertifi' not found
  "github.com/certifi/gocertifi"
  ^
src/gitlab.com/gitlab-org/gitlab-workhorse/vendor/github.com/getsentry/raven-go/client.go:307:18:
error: reference to undefined name 'gocertifi'
  rootCAs, err := gocertifi.CACerts()
  ^

See full build log
https://buildd.debian.org/status/fetch.php?pkg=gitlab-workhorse&arch=powerpc&ver=0.8.2-1&stamp=1475255726

If these libraries are present in system path they gets picked up
correctly, but they are not found when in vendor directory. golang-go
builds this without any errors.

1. 0.7.2 was built fine on powerpc
2. the same failure was reproduced on amd64 gccgo-6
3. this is building fine with golang-go



signature.asc
Description: OpenPGP digital signature

Bug#839599: powerline: plugin fails to load

[Alberto Fuentes]

Package: powerline
Version: 2.5-1
Severity: important

$ vim

Traceback (most recent call last):
  File "", line 4, in 
ImportError: No module named 'powerline'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "", line 9, in 
ImportError: No module named 'powerline'
An error occurred while importing powerline module.
This could be caused by invalid sys.path setting,
or by an incompatible Python version (powerline requires
Python 2.6, 2.7 or 3.2 and later to work). Please consult
the troubleshooting section in the documentation for
possible solutions.
Unable to import powerline, is it installed?
Press ENTER or type command to continue


$ apt install --reinstall powerline
$ mv .vimrc .vimrc.old
$ mv .vim .vim.old
$ vim-addon-manager install powerline

$ vim

Traceback (most recent call last):
  File "", line 4, in 
ImportError: No module named 'powerline'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "", line 9, in 
ImportError: No module named 'powerline'
An error occurred while importing powerline module.
This could be caused by invalid sys.path setting,
or by an incompatible Python version (powerline requires
Python 2.6, 2.7 or 3.2 and later to work). Please consult
the troubleshooting section in the documentation for
possible solutions.
Unable to import powerline, is it installed?
Press ENTER or type command to continue



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

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

Versions of packages powerline depends on:
ii  libc6 2.24-3
ii  python-powerline  2.5-1
pn  python:any

Versions of packages powerline recommends:
ii  fonts-powerline  2.5-1

Versions of packages powerline suggests:
pn  python-powerline-doc  
ii  vim-addon-manager 0.5.5

-- no debconf information

Bug#813910: My two cents

[Raphaël Halimi]

> I think the (long term?) goal is to remove console-common from Debian 
> and to leave console-data as merely a collection of fonts and keymaps 
> with no configuration scripts.
> 
> Isn't it possible to move the configuration scripts of console-data to 
> console-common or some other console package?

Personally I think this would be the best solution.

For example, the keytab-lilo tool (used to create keymaps for LILO or
SYSLINUX) only needs the keymaps contained in console-data; one might
need to install this package without needing to actually change the
configuration of the keyboard.

The "-data" part of the package name indicates that it should merely
contain data (here, keymaps and fonts), not configuration scripts to
change the console's keymap or font.

Plus, it would allow to get rid (at least partly) of a circular
dependency (console-common depends on console-data and kbd, console-data
recommends console-common and kbd, and kbd recommends console-setup |
console-data).

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#837700: gnutls: GNUTLS segfaults on initialization

[Andreas Metzler]

On 2016-09-15 Andreas Metzler  wrote:
> On 2016-09-14 J Phelps  wrote:
[...]
>> Instead, I had unresolved symbols (I don't remember which ones),

> Can you reproduce this and show the exact error message?

>> and I had
>> to go to Nettle's Git repository (https://git.lysator.liu.se/nettle/nettle)
>> to find source code that could produce a linkable library. The symbols
>> that were unresolved were only found in the "ecc-support" branch of that
>> repo. Compiling from the trunk led to the same symbols being unresolved.
> [...]

> I strongly suspect a local issue, e.g. locally built old version of
> gnutls or nettle in /usr/local. "ldd  /usr/lib/chromium/chromium" might
> point in the right direction.

Or is it the same issue as
https://bugs.debian.org/835342 which was caused by installation of
ancient packages from Debian multimedia?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#839242: jessie-pu: package linkchecker/9.3-1

[Antoine Beaupré]

On 2016-10-01 13:08:06, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
>
> On Fri, 2016-09-30 at 11:38 -0400, Antoine Beaupré wrote:
>> Attached is a debdiff between the -1 and -1.1 version.
>
> Apparently not.

Sorry.



linkchecker_9.3-1.1.debdiff
Description: Binary data

>> I suggest
>> uploading the -1.1 version straight to stable since newer releases
>> were done in stable. I am concerned by a subsequent QA upload that
>> fixed a related issue, however:
>> 
>> https://packages.qa.debian.org/l/linkchecker/news/20160723T130426Z.html
>> 
>> I am not sure this bugfix applies to jessie, however, as I am using
>> -1.1 here in jessie without problems.
>
> Confirming one way or the other would be appreciated.

At first glance, it seems unrelated.

A.
-- 
Prolétaires de tous les pays, qui lave vos chaussettes?
- Audrey Lorde

Bug#837728: RM: heimdal/1.7~git20150920+dfsg-4

[Emilio Pozuelo Monfort]

On 14/09/16 01:23, Jelmer Vernooij wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> Please remove the heimdal source package from testing. As maintainers,
> we believe that Heimdal is not in a good enough state to be included in
> a stable release.
> 
> There is still some activity in the upstream Git master branch. However:
> 
> * The last regular release (1.5) was in 2011, last RC was in 2012
> * No security releases since Jan 2012, despite various recent security
>   releases for MIT Kerberos since and occasional security releases while 
> Heimdal
>   was active
> * There is no noticeable QA happening upstream. Tests fail on 32 bit,
>   regressions have been introduced.
> * Nobody upstream is interested in release management; we have asked
>   about this on the development list multiple times.
> 
> I have filed bugs against the packages that depend on Heimdal to
> either switch to building against Heimdal OR MIT or to drop their
> Heimdal dependencies altogether.

The build dependency should prefer MIT kerberos in that case, as sbuild/buildds
only look at the first alternative.

Please make those bugs block this one so we can track progress.

Thanks,
Emilio

Bug#838992: mutt: using mutt, will not default to home mail directory: "c", "?" with "set folder" remains in /var/mail

[franck]

Package: mutt
Version: 1.7.0-6
Followup-For: Bug #838992

Hi Antonio,

Let me reply in behalf of jackson for

a) What directory do you expect instead?
the one set by 'set folder' in .muttrc

b) where is directory that you expect, set in .muttrc?
see a

I am not sure if this behavior was on purpose, but it used to work and be 
convenient.

For instance, see the difference between mutt <=1.6 & 1.7 when:
.muttrc contains 'set folder=~/my/mail/mailboxes'
~/my/mail/mailboxes contains following mailboxes
   mybox1 mybox2 ...
key 'c' is binded to change-folder (default)

[in mutt 1.6 or earlier]
pressing keys 'c' '?' open folder ~/my/mail/mailboxes
then it list mybox1 mybox2 ...
then it is very convenient to open those mailboxes: just move the cursor on 1 
of them and press enter. 

[from mutt 1.7]
pressing keys 'c' '?' open folder /var/mail
then one need to select with the cursor
..
..
home
myaccount
my
mail
mailboxes
then it list mybox1 mybox2 ...

Needless to say that this it much less convenient.

BR, Franck

-- Package-specific info:
NeoMutt 20160916 (1.7.0)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.7.0-1-amd64 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.2.0-4' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch -
 -with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.2.0 20160914 (Debian 6.2.0-4) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-WCcuvM/mutt-1.7.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security' 'LDFLAGS=-fPIE -pie 
-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORT
 IFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-WCcuvM/mutt-1.7.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security

Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME 
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK 
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_GETADDRINFO 
+HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR 
+HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR 
+HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS +USE_COMPRESSED +USE_DOTLOCK 
+USE_FCNTL -USE_FLOCK -USE_FMEMOPEN -USE_GNU_REGEX +USE_GSS +USE_HCACHE 
+USE_IMAP +USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL +USE_SETGID +USE_SIDEBAR 
+USE_SMTP +USE_SSL_GNUTLS -USE_SSL_OPENSSL 
-DOMAIN
MIXMASTER="mixmaster"
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"

patch-attach-headers-color-neomutt
patch-compress-neomutt
patch-cond-date-neomutt
patch-encrypt-to-self-neomutt
patch-fmemope

Bug#839242: jessie-pu: package linkchecker/9.3-1

[Adam D. Barratt]

On Sun, 2016-10-02 at 12:21 -0400, Antoine Beaupré wrote:
> On 2016-10-01 13:08:06, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> >
> > On Fri, 2016-09-30 at 11:38 -0400, Antoine Beaupré wrote:
> >> Attached is a debdiff between the -1 and -1.1 version.
> >
> > Apparently not.
> 
> Sorry.

Thanks.

At first glance, I'm rather confused by:

--- linkchecker-9.3/debian/source/include-binaries  1969-12-31 
19:00:00.0 -0500
+++ linkchecker-9.3/debian/source/include-binaries  2016-05-19 
14:33:11.0 -0400
@@ -0,0 +1,27 @@

particularly its appearance in an NMU. None of the paths sound like
files that you'd want to include in the source package, and indeed none
of them appear to have been included in the package in unstable; at
least most also appear to be automatically removed by upstream's clean
targets.

Regards,

Adam

Bug#839600: perl: concatenating string instead of sprintf takes all computation power of server

[Leszek Dubiel]

Package: perl
Version: 5.20.2-3+deb8u6
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

I am reading big string from file (2 megabytes), then add parentheses to
the beginning and end of that string, finally do parsing with regular
expressions using \G for continuation. 

>From time to time my server get locked, all computation power was
consumed by that perl script. 

I have asked question on perlmonks:
http://www.perlmonks.org/?node_id=1172994

People were testing program and didn't have the same effect. So it
appeared that this is problem only on my server. I have moved script to
another computer with the same version of Debian (jessie, stable), and
script still did run very slow. Problem dissapeared on new version
(stretch). I have tested on my ubuntu (run fast), and the same hardware
under VirtualBox with fresh installation of Debian Jessie -- script did
run very slow. 

So the problem exists on current debian stable version (jessie), and
doesn't exist on newer versions. 

Here is the test suite to reproduce error: 

https://drive.google.com/file/d/0B9GHvKh0yZKYY0pOUFc5V2hadTg/view?usp=sharing

If error is on your computer, then it runs about 30 seconds. 
If there is no error that it runs only half a second. 

Below there is a program. There are some lines commented out -- if you
uncomment them, then program runs very fast. Why? I don't understand.

###

use strict; 
use warnings; 

sub my_parse { 
my ($a) = @_; 
$$a =~ /\G\s*+\(/gc or die "paren expected"; 
while ($$a =~ /\G\s*+([[:alnum:]_]+)\s*+/gc) { 
if ($$a =~ /\G([-+._[:alnum:]]+|"(?:[^\\"]++|\\[\\"])*+")/gc) { 
1; 
} elsif ($$a =~ /\G(?=\()/gc) { 
my_parse($a); 
} else { 
die "wrong value"; 
}
}
$$a =~ /\G\s*+\)\s*+/gc or die "name expected"; 
return; 
}

my $inp = `cat input.txt`; 

# my $inp = `echo; cat input.txt`; # is fast
# my $inp = `cat input.txt; echo`; # is fast
# my $inp = `sed -n '1,9000p' input.txt`; # is slow
# my $inp = `sed -n '1,8000p' input.txt`; # is fast

my $par = "(" . $inp . ")"; 
# my $par = sprintf "(%s)", $inp; # is fast

my_parse(\$par); 

###

The problem seems very strange for me. I have tried to make smaller data
input, but if I cut some lines from input script runs very fast, cut
lines from the beginning, or end, or in the middle. Adding empty line
with "echo" makes it run fast. Sprintf istead of concatenation makes it
fast. 



*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages perl depends on:
ii  dpkg  1.17.27
ii  libbz2-1.01.0.6-7+b3
ii  libc6 2.19-18+deb8u6
ii  libdb5.3  5.3.28-9
ii  libgdbm3  1.8.3-13.1
ii  perl-base 5.20.2-3+deb8u6
ii  perl-modules  5.20.2-3+deb8u6
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages perl recommends:
ii  netbase  5.3
pn  rename   

Versions of packages perl suggests:
pn  libterm-readline-gnu-perl | libterm-readline-perl-perl  
pn  make
pn  perl-doc

-- no debconf information

Bug#839312: Pending fixes for bugs in the golang-github-prometheus-common package

[pkg-go-maintainers]

tag 839312 + pending
thanks

Some bugs in the golang-github-prometheus-common package are closed
in revision 65802be50d795aee208ce3099639c97b490ee0d2 in branch
'debian/sid' by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-prometheus-common.git/commit/?id=65802be

Commit message:

Rollback to 0+git20160801.0.ebdfc6d, as the last upload broke 
reverse-dependencies. Closes: #839312.

Bug#839586: show sometimes wrong cursor, makes program temporarily unusable

[W. Martin Borgert]

On 2016-10-02 15:12, Christoph Reiter wrote:
> I've never seen the described behaviour with debian sid + quodlibet
> under gnome-shell. Which DE/WM are you using? Do you use a trackpad,
> trackpoint or mouse?

Sorry for not giving this information right away in the bug report!

Here we go:

 - xfce4 and xfwm4 4.12.3 from Debian testing
 - focus follows mouse
 - no raise on focus, no raise on click
 - Lenovo ThinkPad touchpad with integrated buttons

I will try gnome-shell now and see wether the behaviour changes.