Bug#884903: libtesseract-dev: headers broken: missing std::; headers missing

2017-12-20 Thread Andreas Beckmann
Package: libtesseract-dev
Version: 4.00~git2174-3b62badd-5
Severity: serious
Control: affects -1 src:opencv

Hi,

tesseract 4 causes opencv/experimental to FTBFS:

In file included from /usr/include/tesseract/ltrresultiterator.h:26:0,
 from /usr/include/tesseract/resultiterator.h:26,
 from /usr/include/tesseract/baseapi.h:31,
 from 
/build/opencv-3.3.0+dfsg/contrib/modules/text/src/precomp.hpp:51,
 from 
/build/opencv-3.3.0+dfsg/contrib/modules/text/src/erfilter.cpp:43:
/usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; 
did you mean 'stdin'?
   static string UTF32ToUTF8(const std::vector& str32);
  ^~
  stdin
modules/text/CMakeFiles/opencv_text.dir/build.make:65: recipe for target 
'modules/text/CMakeFiles/opencv_text.dir/src/erfilter.cpp.o' failed
make[4]: *** [modules/text/CMakeFiles/opencv_text.dir/src/erfilter.cpp.o] Error 
1


Let's compile each tesseract header:

for header in /usr/include/tesseract/*.h ; do echo $header ; echo "#include 
<$(basename $header)>" | g++ -c -xc++ -o /tmp/o.o -I /usr/include/tesseract - ; 
done

I'll only list each error once:

In file included from :1:0:
/usr/include/tesseract/convolve.h:25:10: fatal error: matrix.h: No such file or 
directory
 #include "matrix.h"
  ^~
compilation terminated.

In file included from :1:0:
/usr/include/tesseract/functions.h:24:10: fatal error: tprintf.h: No such file 
or directory
 #include "tprintf.h"
  ^~~
compilation terminated.

In file included from /usr/include/tesseract/unicharset.h:29:0,
 from /usr/include/tesseract/osdetect.h:24,
 from :1:
/usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; 
did you mean 'stdin'?
   static string UTF32ToUTF8(const std::vector& str32);
  ^~
  stdin
In file included from /usr/include/tesseract/osdetect.h:24:0,
 from :1:
/usr/include/tesseract/unicharset.h:241:10: error: 'string' does not name a 
type; did you mean 'stdin'?
   static string CleanupString(const char* utf8_str) {
  ^~
  stdin
/usr/include/tesseract/unicharset.h:244:10: error: 'string' does not name a 
type; did you mean 'stdin'?
   static string CleanupString(const char* utf8_str, int length);
  ^~
  stdin
/usr/include/tesseract/unicharset.h: In member function 'void 
UNICHARSET::unichar_insert_backwards_compatible(const char*)':
/usr/include/tesseract/unicharset.h:265:5: error: 'string' was not declared in 
this scope
 string cleaned = CleanupString(unichar_repr);
 ^~

In file included from :1:0:
/usr/include/tesseract/renderer.h:215:29: error: 'Pix' has not been declared
   static bool imageToPDFObj(Pix *pix, char *filename, long int objnum,
 ^~~


Andreas



Bug#866137: Reopen

2017-12-20 Thread Andreas Tille
control: reopen -1

Seems some more files need to be copied into the test package.

...
gcc -O2 -fno-strict-aliasing -fno-code-hoisting -I. -Wdate-time 
-D_FORTIFY_SOURCE=2 -c -o hts_os.o hts_os.c
hts_os.c:28:10: fatal error: win/rand.c: No such file or directory
 #include "win/rand.c"
  ^~~~
compilation terminated.


Kind regards

   Andreas.


-- 
http://fam-tille.de



Bug#884902: autorandr: 1.3-1 crashes with config error when run

2017-12-20 Thread Rob Browning

Package: autorandr
Version: 1.3-1

$ autorandr
Failed to load profiles (line 642; /usr/lib/python2.7/ConfigParser.py):
  No section: 'config'

This upstream patch appears to fix it:

  
https://github.com/phillipberndt/autorandr/commit/e717470ee5d373935156abf7d187c39c348eaf94

Thanks for providing the package
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



Bug#884867: Package libspreadsheet-readsxc-perl is ready

2017-12-20 Thread Andrius Merkys
Dear Gregor,

thank you for reviewing my package! I will check the TODO list and fix
the package accordingly.

Many thanks,
Andrius


On 12/20/2017 08:20 PM, gregor herrmann wrote:
> On Wed, 20 Dec 2017 19:44:08 +0200, Andrius Merkys wrote:
>
>> I consider the package libspreadsheet-readsxc-perl ready to be uploaded
>> to Debian. I have prepared it in
>> https://anonscm.debian.org/git/pkg-perl/packages/libspreadsheet-readsxc-perl.git.
>> I would require the assistance of DD to review and upload the package.
> Thanks for your work, and welcome to your first package :)
>
> As per our usual procedures I've reviewed it and added some minor
> TODO items to its debian/changelog.
>
> tl;dr: You would have saved some work by using dh-make-perl
> --pkg-perl --cpan ... (from unstable) and starting from there :)
>
>
> Feel free to ask any questions if something is unclear!
>
>
> Cheers,
> gregor
>

-- 
Andrius Merkys
PhD student at Vilnius University Institute of Biotechnology, Saulėtekio al. 7, 
room V325
LT-10257 Vilnius, Lithuania




signature.asc
Description: OpenPGP digital signature


Bug#884003: FDT overlay support

2017-12-20 Thread Andre Heider

Hi Vagrant,

On 20/12/17 22:32, Vagrant Cascadian wrote:

On 2017-12-12, Andre Heider wrote:

I added the ability to concatenate multiple scripts/snippets for the
final boot script.
The new overlay handling snippet is supposed to be
used with this. But the feature itself also allows nice cleanups,
demonstrated on odroid-u3 and beaglebone (and there're quite some more
cleanups possible).


I very much like the idea of this; so many of the boot scripts
copy-and-paste a lot of code between them, which makes maintenence more
difficult as well as implementing features and changes across all the
boot scripts...


Yeah, the copypasta is the first thing I noticed after git cloning. I 
tried to make the overlay support universal. So the less duplication 
there is, the easier it'll get to reuse it.



Unfortunately, I haven't had a chance to do more than a very cursory
glance at your patches yet. Made some comments in-line on some of the
individual patches below.


Thanks for the first glance! There's no need to hurry, especially with 
xmas around the corner.



To test this, you need:
- u-boot with CONFIG_OF_LIBFDT_OVERLAY
- base dtb with symbols (-@)


Would the symbols (-@) be harmful to enable in Debian's kernels by
default?


That's the big question. I looked around and found 3 cases where 
distros/downstreams enable symbols, see [1], [2] and [3]. But those 3 
are in a different boat than debian: It's just per family of SoC.


I'm not sure if anything breaks if debian would enable it for its armhf 
multi platform build. I'm currently trying to find out with a solution 
appropriate for the upstream kernel [4], but I'm not sure if that pans out.



Is it feasible to use dtc to extract the .dts, rebuild it with -@, and
then use that .dtb instead... or does it need more information from the
original device tree(s)?


That's not going to work, without -@ the "__symbols__" node is missing. 
Without that an overlay can not reference e.g. the alias 'spi0'. You 
need the original dts to include these.



- your own overlays, again with symbols, in /boot/dtbs/overlays


Are there some very basic example overlays that would be feasible to just test 
that
this feature is working?

I don't have much experience with overlays, but have a beagleboneblack
and a CHIP that in theory support this, and some devices I can attach
that require overlays...

Will try to test myself sometime in the coming weeks.


Since I used a boneblack too, you can find my basic overlays attached. 
I'm not a device tree expert, so they might not be correct, but they're 
good enough to test this and see the results (especially since commit [5]).



From: Andre Heider 
Date: Tue, 12 Dec 2017 09:23:37 +0100
Subject: [PATCH 01/10] bootscr.uboot-generic: quote bootargs

Signed-off-by: Andre Heider 
---
  bootscript/all/bootscr.uboot-generic | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bootscript/all/bootscr.uboot-generic 
b/bootscript/all/bootscr.uboot-generic
index db4066a..bcf6e96 100644
--- a/bootscript/all/bootscr.uboot-generic
+++ b/bootscript/all/bootscr.uboot-generic
@@ -25,7 +25,7 @@ if test -n "${console}"; then
setenv bootargs "${bootargs} console=${console}"
  fi
  
-setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} @@LINUX_KERNEL_CMDLINE@@

+setenv bootargs "@@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} 
@@LINUX_KERNEL_CMDLINE@@"
  @@UBOOT_ENV_EXTRA@@
  
  if test -z "${fk_kvers}"; then


Why is this needed?


It's not, I did that just to be consistent (see 3 lines above). Patch 
can be dropped if you disagree.



From: Andre Heider 
Date: Tue, 12 Dec 2017 09:25:26 +0100
Subject: [PATCH 05/10] bootscr.uboot-generic: support multiple prefixes to
  load from

Allow custom boot scripts to set $fk_image_locations as a list of
directories to load boot files from.

If unset, $prefix will be the used - which is sufficient for all recent
u-boot versions.

This allows the clean up of various custom boot scripts. Code borrowed
form the sunxi script.

Signed-off-by: Andre Heider 
---
  bootscript/all/bootscr.uboot-generic | 38 +---
  1 file changed, 27 insertions(+), 11 deletions(-)

diff --git a/bootscript/all/bootscr.uboot-generic 
b/bootscript/all/bootscr.uboot-generic
index bcf6e96..509efe7 100644
--- a/bootscript/all/bootscr.uboot-generic
+++ b/bootscript/all/bootscr.uboot-generic
@@ -48,14 +48,30 @@ else
setenv partition ${distro_bootpart}
  fi
  
-load ${devtype} ${devnum}:${partition} ${kernel_addr_r} ${prefix}vmlinuz-${fk_kvers} \

-&& load ${devtype} ${devnum}:${partition} ${fdt_addr_r} ${prefix}${fdtpath} \
-&& load ${devtype} ${devnum}:${partition} ${ramdisk_addr_r} 
${prefix}initrd.img-${fk_kvers} \
-&& echo "Booting Debian ${fk_kvers} from ${devtype} ${devnum}:${partition}..." 
\
-&& bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}
-
-load ${devtype} 

Bug#884901: RM: libjs-jquery-dotdotdot -- RoM; Upstream changed to non-free license

2017-12-20 Thread Sergio Durigan Junior
Package: ftp.debian.org
Severity: normal

Hi,

I would like to request the removal of the "libjs-jquery-dotdotdot"
package from unstable.  Even though the official maintainer is listed as
the "Debian Javascript Maintainers", I was the person responsible for
packaging the software and have been monitoring it since it was
accepted.

The reason I am asking for the removal is because upstream has decided
to change the license of the software from Expat to CC-BY-NC-4.0, which
is non-free according to the DFSG.  With this change, I do not intend to
maintain this package anymore, and it is also not possible to upgrade it
due to the license change (please note that the current version shipped
by Debian is still free).  There are no reverse dependencies to this
software at the moment, which makes it a good time to remove it from the
archives.

I had packaged this software because it is a dependency for pagure,
another package that I am working on.  In the interest of removing
non-free dependencies from a Free Software project, I have also filed a
bug against upstream pagure asking the project to stop using the
"dotdotdot" library:

  https://pagure.io/pagure/issue/2844

Thank you in advance.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#884900: gnome-keysign: FTBFS on i386: Segmentation fault during tests

2017-12-20 Thread Andreas Beckmann
Source: gnome-keysign
Version: 0.9.6-1~exp1
Severity: serious
Justification: fails to build from source

Hi,

gnome-keysign/experimental FTBFS on i386:

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/gnome-keysign-0.9.6/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
gpg: keybox '/tmp/tmpih30Kw/pubring.kbx' created
gpg: /tmp/tmpih30Kw/trustdb.gpg: trustdb created
gpg: key 1D4E64C28F62260A: public key "Bruce Wayne (https://bruce.wayne) 
" imported
gpg: key 1D4E64C28F62260A: secret key imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
gpg: keybox '/tmp/tmpPlALvw/pubring.kbx' created
gpg: /tmp/tmpPlALvw/trustdb.gpg: trustdb created
gpg: key A5C89B8B383EE754: public key "Test Key " imported
gpg: key A5C89B8B383EE754: secret key imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
Segmentation fault
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=139: cd 
/build/gnome-keysign-0.9.6/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:20: recipe for target 'build' failed
make: *** [build] Error 25

This failure happens every time.
It builds fine on amd64.


Andreas


gnome-keysign_0.9.6-1~exp1.log.gz
Description: application/gzip


Bug#884899: piuparts-master: piuparts-report should validate Packages hashes against Release

2017-12-20 Thread Andreas Beckmann
Package: piuparts-master
Severity: important

As a protection against network problems piuparts-report should validate
the downloaded Packages and Sources files against the md5/sha* hashes in
the Release files. There is no point in verifying the Release signatures
(that is done by apt in the slave chroot anyway).

I had just observed that piuparts-report archived half a section after
it downloaded a partial Packages.xz due to some network problems. That
probably didn't result in a (ignored) download error.

piuparts-master could do the same, but the impact there will be much
smaller: it might not send out new work or discard the logfiles it
receives.

As a quick hack to limit the impact of network glitches we should limit
the archival to 1000 packages per section and piuparts-report run.


Andreas



Bug#884898: icu: fails to clean after build: parallel distclean race

2017-12-20 Thread Andreas Beckmann
Source: icu
Version: 60.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

during a pbuilder --twice test I noticed that icu failed to clean after
the first build. That cleaning is usually not performed during regular
builds since the build tree and chroot are discarded anyway.
I was not able to reproduce this failure with a sequential (parallel=1)
build, but with a paralle=2 and parallel=4 build it happened frequently:

 fakeroot debian/rules clean
dh clean --sourcedirectory=/build/icu-60.2/source/ --parallel
   dh_auto_clean -O--sourcedirectory=/build/icu-60.2/source/ -O--parallel
cd source && make -j2 distclean
make[1]: Entering directory '/build/icu-60.2/source'
test -z "*~" || rm -rf *~
rm -rf "test-*.xml"
rm -rf "perf-*.xml"
make[1]: Making `distclean' in `stubdata'
rm -rf ./config/icu-uc.pc ./config/icu-i18n.pc ./config/icu-lx.pc 
./config/icu-io.pc ./config/icuinfo.xml
rm -rf Doxyfile doc icu-docs.zip
make[2]: Entering directory '/build/icu-60.2/source/stubdata'
test -z "*~ stubdata.d   " || rm -rf *~ stubdata.d
rm -rf stubdata.o stubdata.ao libicudata.a libicudata.so.60.2 libicudata.so.60 
libicudata.so  libicudata.so.60.2
rm -rf ./config/Makefile.inc ./config/pkgdata.inc ./config/icu-config 
./config/icu.pc ./config/icu-uc.pc ./config/icu-i18n.pc ./config/icu-lx.pc 
./config/icu-io.pc
rm -rf Makefile
make[2]: Leaving directory '/build/icu-60.2/source/stubdata'
make[1]: Making `distclean' in `common'
rm -rf config.cache config.log config.status ./config/icucross.mk 
./config/icucross.inc autom4te.cache uconfig.h.prepend
make[2]: Entering directory '/build/icu-60.2/source/common'
make[2]: *** No rule to make target '../config.status', needed by 'Makefile'.  
Stop.
make[2]: Leaving directory '/build/icu-60.2/source/common'
Makefile:149: recipe for target 'distclean-recursive' failed
make[1]: *** [distclean-recursive] Error 2
make[1]: *** Waiting for unfinished jobs
rm -rf Makefile config/Makefile icudefs.mk ./lib ./bin
rm -rf dist
make[1]: Leaving directory '/build/icu-60.2/source'
dh_auto_clean: cd source && make -j2 distclean returned exit code 2
debian/rules:62: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2

 fakeroot debian/rules clean
dh clean --sourcedirectory=/build/icu-60.2/source/ --parallel
   dh_auto_clean -O--sourcedirectory=/build/icu-60.2/source/ -O--parallel
cd source && make -j4 distclean
make[1]: Entering directory '/build/icu-60.2/source'
test -z "*~" || rm -rf *~
rm -rf "test-*.xml"
make[1]: Making `distclean' in `stubdata'
rm -rf "perf-*.xml"
make[2]: Entering directory '/build/icu-60.2/source/stubdata'
test -z "*~ stubdata.d   " || rm -rf *~ stubdata.d   
rm -rf ./config/icu-uc.pc ./config/icu-i18n.pc ./config/icu-lx.pc 
./config/icu-io.pc ./config/icuinfo.xml
rm -rf stubdata.o stubdata.ao libicudata.a libicudata.so.60.2 libicudata.so.60 
libicudata.so  libicudata.so.60.2
rm -rf Doxyfile doc icu-docs.zip
rm -rf Makefile
make[2]: Leaving directory '/build/icu-60.2/source/stubdata'
make[1]: Making `distclean' in `common'
make[2]: Entering directory '/build/icu-60.2/source/common'
test -z "*~ errorcode.d putil.d umath.d utypes.d uinvchar.d umutex.d ucln_cmn.d 
uinit.d uobject.d cmemory.d charstr.d cstr.d udata.d ucmndata.d udatamem.d 
umapfile.d udataswp.d ucol_swp.d utrace.d uhash.d uhash_us
.d uenum.d ustrenum.d uvector.d ustack.d uvectr32.d uvectr64.d ucnv.d 
ucnv_bld.d ucnv_cnv.d ucnv_io.d ucnv_cb.d ucnv_err.d ucnvlat1.d ucnv_u7.d 
ucnv_u8.d ucnv_u16.d ucnv_u32.d ucnvscsu.d ucnvbocu.d ucnv_ext.d ucnv
mbcs.d ucnv2022.d ucnvhz.d ucnv_lmb.d ucnvisci.d ucnvdisp.d ucnv_set.d 
ucnv_ct.d resource.d uresbund.d ures_cnv.d uresdata.d resbund.d resbund_cnv.d 
ucurr.d messagepattern.d ucat.d locmap.d uloc.d locid.d locutil.
d locavailable.d locdispnames.d locdspnm.d loclikely.d locresdata.d 
bytestream.d stringpiece.d bytesinkutil.d stringtriebuilder.d 
bytestriebuilder.d bytestrie.d bytestrieiterator.d ucharstrie.d 
ucharstriebuilder.d
 ucharstrieiterator.d dictionarydata.d edits.d appendable.d ustr_cnv.d 
unistr_cnv.d unistr.d unistr_case.d unistr_props.d utf_impl.d ustring.d 
ustrcase.d ucasemap.d ucasemap_titlecase_brkiter.d cstring.d ustrfmt.d
 ustrtrns.d ustr_wcs.d utext.d unistr_case_locale.d ustrcase_locale.d 
unistr_titlecase_brkiter.d ustr_titlecase_brkiter.d normalizer2impl.d 
normalizer2.d filterednormalizer2.d normlzr.d unorm.d unormcmp.d loadedno
rmalizer2impl.d chariter.d schriter.d uchriter.d uiter.d patternprops.d uchar.d 
uprops.d ucase.d propname.d ubidi_props.d ubidi.d ubidiwrt.d ubidiln.d ushape.d 
uscript.d uscript_props.d usc_impl.d unames.d utrie.d
 utrie2.d utrie2_builder.d bmpset.d unisetspan.d uset_props.d uniset_props.d 
uniset_closure.d uset.d uniset.d usetiter.d ruleiter.d caniter.d unifilt.d 
unifunct.d uarrsort.d brkiter.d ubrk.d brkeng.d dictbe.d filt
eredbrk.d rbbi.d rbbidata.d 

Bug#839880: proftpd-basic: proftpd server instance crashed with signal 11

2017-12-20 Thread Мороз Олег

Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,


proftpd started successfully in my jessie system.  However after some day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
   pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch
[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch


--
Олег Мороз
Заместитель начальника отдела АО "Корпорация ВНИИЭМ"
+7-963-760-70-15



Bug#884897: dbus-x11: .xinitrc requires "dbus-update-activation-environment --all"

2017-12-20 Thread Carlos Eduardo M. Santos
Package: dbus-x11
Version: 1.12.2-1
Severity: normal

Dear Maintainer,

The following problems started after dist-upgrading from jessie to buster:
1. startx takes a lot of time to launch X;
2. gnome-terminal doesn't start.

The problems happen with a ~/.xinitrc as short as just "exec i3". In
journalctl, I found 2 famous messages:
- gnome-terminal-server[18005]: Unable to init server: Could not connect: 
Connection refused
- Failed to activate service 'org.gnome.Terminal': timed out 
(service_start_timeout=12ms)

After reading many search results, the best I could do was to add
"dbus-update-activation-environment --all" in the first line of
~/.xinitrc.  But it seems to be just a workaround. I also ran "sudo
dpkg-reconfigure locales" and rebooted as the first attempt. As to
problem #1, I have no clue.

Note: the workaround also made it possible to start redshift and dunst services
without changing their service files.

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

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

Versions of packages dbus-x11 depends on:
ii  dbus 1.12.2-1
ii  libc62.25-3
ii  libdbus-1-3  1.12.2-1
ii  libx11-6 2:1.6.4-3

dbus-x11 recommends no packages.

dbus-x11 suggests no packages.

-- Configuration Files:
/etc/X11/Xsession.d/95dbus_update-activation-env changed [not included]
Note: I just added some "echo"s for debugging.

-- no debconf information



Bug#884896: wmaker: Dock covers fullscreen in Firefox (dock is visible while video is fullscreen)

2017-12-20 Thread Alexandra Demos
Package: wmaker
Version: 0.95.7-8
Severity: normal

Hello, 
I am also encountering the same bug as #694825. However, I am sure I am running 
a version of wmaker higher than .95. In my case I am running .95.7 as 
downloaded from the Debian repositories. I ticked the "full screen 
maximization" in attributes as well, still no luck. What can I do on my end, 
what should I check for?

Thank you so much for maintaining this window mananger,
Alex 

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

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

Versions of packages wmaker depends on:
ii  libc62.24-11+deb9u1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgif7  5.1.4-0.4
ii  libjpeg62-turbo  1:1.5.1-2
ii  libpng16-16  1.6.28-1
ii  libtiff5 4.0.8-2+deb9u1
ii  libwings30.95.7-8
ii  libwraster5  0.95.7-8
ii  libwutil50.95.7-8
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxinerama1 2:1.1.3-1+b3
ii  libxpm4  1:3.5.12-1
ii  wmaker-common0.95.7-8

wmaker recommends no packages.

Versions of packages wmaker suggests:
ii  desktop-base  9.0.2+deb9u1
pn  menu  
ii  wmaker-data   0.9~3-4
pn  wmaker-utils  
ii  x11-apps  7.7+6+b1
ii  xfce4-terminal [x-terminal-emulator]  0.8.3-1
ii  xterm [x-terminal-emulator]   327-2

-- no debconf information



Bug#883689:

2017-12-20 Thread J. Smith


I think your expectation is incorrect, and that you should add the -c argument 
to get a new frame.



Bug#883683:

2017-12-20 Thread J. Smith


I'd guess that in a GTK Emacs, the GTK scrollbar ignores X resources. Try 
emacs25-lucid?



Bug#884895: newsboat: FTBFS on sparc64: Bus error running test

2017-12-20 Thread Aaron M. Ucko
Source: newsboat
Version: 2.10.1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-sp...@lists.debian.org
Usertags: sparc64

The build of newsboat for sparc64 (admittedly not a release
architecture) failed:

  cd test && LC_ALL=C.UTF-8 ./test --order rand
  Bus error
  debian/rules:23: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 138

"Bus error" typically indicates unaligned memory access, about which
sparc64 is notoriously strict.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#884894: newsboat: FTBFS on hurd-i386: MAXPATHLEN not declared

2017-12-20 Thread Aaron M. Ucko
Source: newsboat
Version: 2.10.1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org
Usertags: hurd-i386

Builds of newsboat for hurd-i386 (admittedly not a release architecture)
have been failing with a cascade of errors starting with

  src/utils.cpp: In static member function 'static std::__cxx11::string 
newsbeuter::utils::getcwd()':
  src/utils.cpp:1110:14: error: 'MAXPATHLEN' was not declared in this scope
char cwdtmp[MAXPATHLEN];

The Hurd famously has no static MAXPATHLEN (or PATH_MAX).  Best practice
is to work dynamically with what you encounter (for instance, with the
help of the glibc extension get_current_dir_name).  However, if that's
infeasible, you can also look up _PC_PATH_MAX via pathconf or supply a
fallback constant (traditionally 4096).

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#884893: newsboat: FTBFS: Error opening terminal: unknown.

2017-12-20 Thread Aaron M. Ucko
Source: newsboat
Version: 2.10.1-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of newsboat for most architectures on which it compiles at all
(still the majority, granted) have been failing:

  cd test && LC_ALL=C.UTF-8 ./test --order rand
  Error opening terminal: unknown.
  debian/rules:23: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#884892: newsboat: FTBFS on arm*: filter/Scanner.cpp: sign-compare errors

2017-12-20 Thread Aaron M. Ucko
Source: newsboat
Version: 2.10.1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-...@lists.debian.org
Usertags: arm64 armel armhf

Builds of newsboat for arm* have been failing:

  g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall -Wextra 
-Wunreachable-code -DLOCALEDIR=\"/usr/share/locale\" 
-I/usr/include/aarch64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
-D_GNU_SOURCE -D_DEFAULT_SOURCE -I/usr/include/ncursesw -o filter/Scanner.o -c 
filter/Scanner.cpp
  filter/Scanner.cpp: In member function 'Token* Scanner::NextToken()':
  filter/Scanner.cpp:588:12: error: comparison between signed and unsigned 
integer expressions [-Werror=sign-compare]
  if ((ch >= L'-' && ch <= L'.') || (ch >= L'A' && ch <= L'Z') || ch == 
L'_' || (ch >= L'a' && ch <= L'z')) {AddCh(); goto case_3;}
  [...]
  filter/Scanner.cpp:621:31: error: comparison between signed and unsigned 
integer expressions [-Werror=sign-compare]
  else if ((ch >= L'0' && ch <= L'9')) {AddCh(); goto case_6;}
  ~~~^~~
  cc1plus: all warnings being treated as errors
  Makefile:112: recipe for target 'filter/Scanner.o' failed

I presume wchar_t is unsigned on these architectures.  Could you
please take a look and account for this possibility (or whatever the
problem turns out to be)?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#884891: qemu-user-static: add a qemu-chroot script

2017-12-20 Thread Paul Wise
Package: qemu-user-static
Severity: wishlist

qemu-debootstrap is useful for creating foreign-arch chroots but when
you have the storage of an existing foreign-arch system mounted and
want to modify it, a script to setup qemu-user-static on the mounted
system would be helpful for modifying it (installing packages etc).

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#884889: lightdm: FTBFS twice in a row: No rule to make target 'liblightdm-gobject-1.deps'

2017-12-20 Thread Andreas Beckmann
Source: lightdm
Version: 1.18.3-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

lightdm/experimental fails to build twice in a row. (I didn't check the
version in sid). The first build succeeds, the subsequent
'debian/rules clean' runs 'make distclean' which deletes
'liblightdm-gobject/liblightdm-gobject-1.deps' but that file is not
regenerated during the second build, failing with

make[3]: *** No rule to make target 'liblightdm-gobject-1.deps', needed by 
'all-am'.  Stop.

In addition to that, also doc/html/ is cleaned up, probably resulting
in a similar problem as #884813 (xfce-panel).


Andreas


lightdm_1.18.3-5_twice.log.gz
Description: application/gzip


Bug#884888: education-common: Don't recommend python-vte

2017-12-20 Thread Jeremy Bicha
Package: education-common
Version: 1.933
Severity: important
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte

python-vte will be removed from Debian soon. It has been deprecated
and unmaintained for years. The replacement is to use gtk3 and
gobject-introspection (see the gir1.2-vte-2.91 package).

Therefore, please don't recommend python-vte.

While you're at it, please stop recommending python-gtk2 too.

On behalf of the Debian GNOME Team,
Jeremy Bicha



Bug#884816: RFS: frontaccounting/2.4.3-1 [ITA]

2017-12-20 Thread Paul Wise
On Wed, Dec 20, 2017 at 6:57 AM, Janusz Dobrowolski wrote:

>   This package was recently included in wheezy, but seems later was
> orphaned sometime back in 2013, and currently is absent from debian
> repositories. Now it is refreshed, and as one of upstream developers I'm
> ready to maintain it under kind supervision of some sponsor.

Please note the extra steps required when reintroducing removed packages:

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



Bug#884887: chromium: rejects access to microphone without prompt

2017-12-20 Thread Jeremy Lainé

Package: chromium
Version: 63.0.3239.84-1
Severity: normal

When trying to make use of any website which uses getUserMedia(),
including the reference WebRTC app, the request fails with a
NotAllowedError without prompting me at all. The expected behaviour is
for the usual prompt to appear, asking for access to the microphone.

I have checked that the "Block" and "Allow" lists in content settings
are both empty and the default action is "Ask before accessing".
Furthermore, manually adding websites to the "Allow" list makes no
difference, I still get the crossed out microphone icon to the right of
the URL bar indicating access to the microphone was denied.

This really seems to be a UX issue and not a problem accessing the
underlying hardware, as everything works fine if I start Chromium with
the –use-fake-ui-for-media-stream flag.

I have also tried the Google-provided .deb for Chrome (also M63) on the
same machine everything works out of the box, so it really looks like
this issue is specific to the Debian/Chromium build.

Let me know if there are any further tests I can perform to narrow down
the root cause of the issue.


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

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common  63.0.3239.84-1
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.26.1-1
ii  libavcodec57 7:3.4.1-1
ii  libavformat57    7:3.4.1-1
ii  libavutil55  7:3.4.1-1
ii  libc6    2.25-5
ii  libcairo2    1.15.8-2
ii  libcups2 2.2.6-3
ii  libdbus-1-3  1.12.2-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat1    2.2.5-3
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-0.1
ii  libgcc1  1:7.2.0-18
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.2-3
ii  libgtk-3-0   3.22.26-2
ii  libharfbuzz0b    1.7.2-1
ii  libicu57 57.1-8
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.16-1+b1
ii  libnss3  2:3.34-1
ii  libopus0 1.2.1-1
ii  libpango-1.0-0   1.40.13-2
ii  libpangocairo-1.0-0  1.40.13-2
ii  libpng16-16  1.6.34-1
ii  libpulse0    11.1-4
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   7.2.0-18
ii  libvpx4  1.6.1-3
ii  libwebp6 0.6.0-4
ii  libwebpdemux2    0.6.0-4
ii  libwebpmux3  0.6.0-4
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-5.2
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-5
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.8.dfsg-5

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

Versions of packages chromium suggests:
pn  chromium-driver    
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information



Bug#790185: pypar2: depends on vte which is deprecated

2017-12-20 Thread Jeremy Bicha
Control:  severity -1 serious
Control: tags -1 -stretch

The Debian GNOME Team does not intend to release python-vte with
Debian Buster. Therefore, I am raising the severity of this bug.

Please port your app to gtk3 and gobject-introspection. If that isn't
possible, please consider requesting the removal of this package.

On behalf of the Debian GNOME Team,
Jeremy Bicha



Bug#790176: guake: depends on vte which is deprecated

2017-12-20 Thread Jeremy Bicha
Control:  severity -1 serious
Control: tags -1 -stretch

The Debian GNOME Team does not intend to release python-vte with
Debian Buster. Therefore, I am raising the severity of this bug.

Please port your app to gtk3 and gobject-introspection. If that isn't
possible, please consider requesting the removal of this package.

On behalf of the Debian GNOME Team,
Jeremy Bicha



Bug#790179: hotssh: depends on vte which is deprecated

2017-12-20 Thread Jeremy Bicha
Control:  severity -1 serious
Control: tags -1 -stretch +buster

The Debian GNOME Team does not intend to release python-vte with
Debian Buster. Therefore, I am raising the severity of this bug.

Please port your app to gtk3 and gobject-introspection. If that isn't
possible, please consider requesting the removal of this package.

On behalf of the Debian GNOME Team,
Jeremy Bicha



Bug#884048: gnome-shell: /usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with segfault

2017-12-20 Thread Pino Toscano
Control: severity -1 important

In data sabato 16 dicembre 2017 23:25:16 CET, Adrian Bunk ha scritto:
> Control: severity -1 serious
> 
> On Sat, Dec 16, 2017 at 09:19:18PM +0100, Michael Biebl wrote:
> > Control: severity -1 important
> > 
> > > Dec 10 13:17:40 lavaine kernel: [ 3324.799650] gnome-shell-cal[2352]: 
> > > segfault at 10812 ip 7f2eeafd0324 sp 7ffd0bc3d6d0 error 4 in 
> > > libical.so.2.0.0[7f2eeaf8d000+5e000]
> > To explain what's happening here:
> > gnome-shell links directly against libical (here against v2) and also
> > against libecal (from evolution-data-server).
> > evolution-data-server was updated to link against libical v3. The result
> > is, that gnome-shell was now loading libical2 (directly) and libical3
> > (indirectly via libecal) into its address space. This is not supported
> > and leads to the crash.
> > 
> > I decided to add a Conflicts: libical2 to libecal (see #884012) to avoid
> > this situation.
> > 
> > So from my POV, this bug can be closed. Other DDs mentioned on
> > #debian-devel though, that this conflicts should be added directly to
> > libical3. I'm thus leaving this bug report open for further discussion
> > but downgrade the severity, as the immediate issue (the segfault in
> > gnome-shell) is addressed by #884012.
> 
> KDE has/had similar problems, setting back to RC to prevent testing 
> migration until this is sorted out.

What are the "similar problems" of "KDE"? Neither the kdelibs 4.x nor
the KF5 stacks support libical3, so everything uses libical2 for now.
The only exception is digikam, for which I just requested a rebuild
(since kcalcore was fixed to properly use libical2, see #883921).

Since I don't see any other message in this bug regarding problems,
nor I see any bug filed in any part of the KDE stack, then I'm lowering
the severity of this bug, so this rushed doko-transition can be finally
unblocked (unblocking the marble+libkipi transition too).

-- 
Pino Toscano

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


Bug#883921: Please rebuild digikam to pick old libical

2017-12-20 Thread Pino Toscano
Hi,

after I fixed kcalcore (#883960), now digikam should use libical2, just
like kcalcore did and still does, hence avoid loading both libical2 and
libical3.  Can you please rebuild digikam in unstable and experimental?

Thanks,
-- 
Pino Toscano

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


Bug#884870: lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree

2017-12-20 Thread Mattia Rizzolo
On Wed, Dec 20, 2017 at 08:11:23PM +0100, Christoph Berg wrote:
> Fwiw, the -b syntax was not invented by vcswatch, it was in use in the
> archive before I wrote the service. I can't find a place where it is
> documented (I thought it was debcheckout(1), but it's not in there),
> but the idea behind it is that you can you paste the Vcs-Git header
> content to "git clone" and it will do the right thing.

It's in Debian Policy of course! :)
https://www.debian.org/doc/debian-policy/#version-control-system-vcs-fields
|In the case of Git, the value consists of a URL, optionally followed
|by the word -b and the name of a branch in the indicated repository,
|following the syntax of the git clone command. If no branch is
|specified, the packaging should be on the default branch.


> (I'm still pondering how a syntax for "package is located in this
> subdirectory" should look like, but as that's not supported by "git
> clone", I couldn't think of anything yet that would at least look like
> the -b syntax. There's a need for it, though.)

There was a very long discussion about this in d-d@ some months (years
already, maybe!?) while discussing a detail from DEP-14.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#884886: live-boot: Installing live-boot (and devirates) into standard Stretch system gives boot problems

2017-12-20 Thread Christian Knoke
Package: live-boot
Severity: normal

Installing live* packages into a normal Installation of Debian Stable
can lead to boot problems on the host. Aptitude does not warn.

In the intend to build a Debian-Live system, I installed, besides
live-build, the following packages on the host:

live-boot-initramfs-tools:i386
live-boot:i386
live-config-systemd:i386
live-config:i386
live-config-doc:i386
live-image-cinnamon-desktop:i386
live-image-gnome-desktop:i386
live-image-kde-desktop:i386
live-image-lxde-desktop:i386
live-image-mate-desktop:i386
live-image-standard:i386
live-image-xfce-desktop:i386
live-images:i386
live-tools:i386

As a result, on host boot only 1 cpu core was recognized, systemd waited 90
sec for disk devices already up and running, and the firmware for the
graphics card was not loaded.

Deinstallation of the above packages and update-initramfs -k all -u solved it.

Christian

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

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

Versions of packages live-boot depends on:
pn  live-boot-initramfs-tools | live-boot-backend  

Versions of packages live-boot recommends:
ii  live-boot-doc  1:20170112
pn  live-tools 
ii  rsync  3.1.2-1+deb9u1
ii  uuid-runtime   2.29.2-1

Versions of packages live-boot suggests:
pn  cryptsetup  
ii  curlftpfs   0.9.2-9+b1
pn  httpfs2 
ii  wget1.18-5+deb9u1



Bug#884821: binutils-mipsel-linux-gnu: Can't find matching LO16 reloc against `.text' for R_MIPS_GOT16 at 0x1f8

2017-12-20 Thread Paul Boddie
On Wednesday 20. December 2017 14.46.12 James Cowgill wrote:
> 
> There are probably two bugs here. Firstly, ld shouldn't trigger an
> internal error when printing the error message...

Perhaps. I didn't know how to interpret that.

> > Relocation section '.rel.text.startup' at offset 0x5398 contains 24 
entries:
> >  Offset InfoTypeSym.Value  Sym. Name
> > 
> >   1f05 R_MIPS_HI16      _gp_disp
> > 0004  1f06 R_MIPS_LO16      _gp_disp
> > 0014  240b R_MIPS_CALL16    l4re_util_cap_alloc
> > 004c  2509 R_MIPS_GOT16     l4re_global_env
> > 0058  0409 R_MIPS_GOT16     .bss
> > 005c  2425 R_MIPS_JALR      l4re_util_cap_alloc
> > 0060  0406 R_MIPS_LO16      .bss
> > 0074  0406 R_MIPS_LO16      .bss
> > 0124  0406 R_MIPS_LO16      .bss
> > 01e0  0406 R_MIPS_LO16      .bss
> > 01f8  0209 R_MIPS_GOT16     .text
> > 0200  0409 R_MIPS_GOT16     .bss
> 
> ... and this relocation section is corrupt. It is illegal to use a GOT16
> relocation without a LO16 relocation somewhere after it (as the ld error
> says). Therefore the bug is in whatever created your main.o file (this
> is likely to be another part of binutils though).

I looked at other files of this nature - it is a specific example program that 
exhibits this problem, so I had a look at other examples - and they seem to 
have what you have described as being expected. For example:

Relocation section '.rel.text.startup' at offset 0x6ab0 contains 47 entries:
 Offset InfoTypeSym.Value  Sym. Name
  2105 R_MIPS_HI16      _gp_disp
0004  2106 R_MIPS_LO16      _gp_disp
0014  240b R_MIPS_CALL16    puts
0010  1609 R_MIPS_GOT16     $LC0
002c  1606 R_MIPS_LO16      $LC0
005c  2509 R_MIPS_GOT16     l4re_global_env
0070  2425 R_MIPS_JALR      puts
0088  1309 R_MIPS_GOT16  0018   $LC1
0094  1306 R_MIPS_LO16   0018   $LC1
0090  0209 R_MIPS_GOT16     .text
0098  0206 R_MIPS_LO16      .text

> It would be useful to have a reduced .c file which can reproduce this
> bug and then decide if its a bug in gcc or binutils.

The offending program is this one:

https://svn.l4re.org/repos/oc/l4re/trunk/l4/pkg/examples/sys/utcb-ipc/main.c

However, this is more for general reference given that it is something that 
gets built in a specific way and has plenty of its own baggage. I shall try 
and follow up with the L4Re people to see if they have any insights.

Thanks for taking a look!

Paul



Bug#884882: Acknowledgement (Please add python3-ldap)

2017-12-20 Thread Timo Aaltonen

Python3 support has been added upstream in 3.0.0b*. The attached diff
updates the packaging for the latest release, 3.0.0b3.

diff --git a/debian/changelog b/debian/changelog
index 1555050..37c286f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-ldap (3.0.0~b3-1) UNRELEASED; urgency=medium
+
+  * New upstream release.
+- drop 01_setup_cfg.diff, obsolete
+  * Package python3-ldap. (Closes: #884882)
+
+ -- Timo Aaltonen   Thu, 21 Dec 2017 00:31:37 +0200
+
 python-ldap (2.5.2-1) unstable; urgency=low
 
   * New maintainer (Closes: #868690).
diff --git a/debian/control b/debian/control
index e13137c..7a83e06 100644
--- a/debian/control
+++ b/debian/control
@@ -4,11 +4,18 @@ Priority: optional
 Maintainer: Willem van den Akker 
 Standards-Version: 4.1.1
 Build-Depends: debhelper (>= 10), python-all-dev (>= 2.6.6-3~), python-all-dbg,
- libldap2-dev, libsasl2-dev, dh-python
+ libldap2-dev, libsasl2-dev, dh-python,
+ python3-all-dev,
+ python3-all-dbg,
+ python-setuptools,
+ python3-setuptools,
+ python-pyasn1-modules,
+ python3-pyasn1-modules,
 Homepage: https://www.python-ldap.org
 Vcs-Browser: 
https://anonscm.debian.org/cgit/users/wvdakker-guest/python-ldap.git
 Vcs-Git: git://anonscm.debian.org/users/wvdakker-guest/python-ldap.git
 X-Python-Version: >= 2.3
+X-Python3-Version: >= 3.3
 
 Package: python-ldap
 Architecture: any
@@ -21,6 +28,15 @@ Description: LDAP interface module for Python
  This module provides a Python interface to the OpenLDAP client library
  (LDAP is the Lightweight Directory Access Protocol).
 
+Package: python3-ldap
+Architecture: any
+Depends: ${python3:Depends}, ${misc:Depends}, ${shlibs:Depends}
+Provides: ${python3:Provides}
+Suggests: python-ldap-doc, python3-pyasn1
+Description: LDAP interface module for Python3
+ This module provides a Python3 interface to the OpenLDAP client library
+ (LDAP is the Lightweight Directory Access Protocol).
+
 Package: python-ldap-dbg
 Section: debug
 Priority: optional
@@ -32,3 +48,15 @@ Description: LDAP interface module for Python (debug 
extension)
  (LDAP is the Lightweight Directory Access Protocol).
  .
  This package contains the extension built for the Python debug interpreter.
+
+Package: python3-ldap-dbg
+Section: debug
+Priority: optional
+Architecture: any
+Depends: python3-ldap (= ${binary:Version}), python3-dbg, ${python3:Depends}, 
${misc:Depends}, ${shlibs:Depends}
+Provides: ${python3:Provides}
+Description: LDAP interface module for Python3 (debug extension)
+ This module provides a Python3 interface to the OpenLDAP client library
+ (LDAP is the Lightweight Directory Access Protocol).
+ .
+ This package contains the extension built for the Python debug interpreter.
diff --git a/debian/patches/01_setup_cfg.diff b/debian/patches/01_setup_cfg.diff
deleted file mode 100644
index 8412614..000
--- a/debian/patches/01_setup_cfg.diff
+++ /dev/null
@@ -1,14 +0,0 @@
-Description: Adjust paths and libraries in setup.cfg
-Forwarded: non-needed
-Author: Matej Vela 
-Last-Update: 2011-04-30
-
 a/setup.cfg
-+++ b/setup.cfg
-@@ -1,5 +1,5 @@
- [_ldap]
--library_dirs = /usr/lib /usr/lib64 /usr/local/lib /usr/local/lib64
-+library_dirs =
- include_dirs = /usr/include /usr/include/sasl /usr/local/include 
/usr/local/include/sasl
- defines = HAVE_SASL HAVE_TLS HAVE_LIBLDAP_R
- extra_compile_args = 
diff --git a/debian/patches/series b/debian/patches/series
index 66c910f..a82d1b4 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1 @@
-01_setup_cfg.diff
+#placeholder
diff --git a/debian/python-ldap-dbg.install b/debian/python-ldap-dbg.install
deleted file mode 100644
index 9402eb7..000
--- a/debian/python-ldap-dbg.install
+++ /dev/null
@@ -1 +0,0 @@
-debian/tmp/usr/lib/python*/*-packages/_ldap_d.so
diff --git a/debian/python-ldap.install b/debian/python-ldap.install
deleted file mode 100644
index 96b7ca4..000
--- a/debian/python-ldap.install
+++ /dev/null
@@ -1,4 +0,0 @@
-debian/tmp/usr/lib/python*/*-packages/_ldap.so
-debian/tmp/usr/lib/python*/*-packages/*.egg-info
-debian/tmp/usr/lib/python*/*-packages/*.py
-debian/tmp/usr/lib/python*/*-packages/*/
diff --git a/debian/rules b/debian/rules
index 5bd7444..6516fb4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,10 +1,15 @@
 #!/usr/bin/make -f
 
+export PYBUILD_NAME = ldap
+
 %:
-   dh $@ --with python2
+   dh $@ --with python2,python3 --buildsystem=pybuild
 
 override_dh_installdocs:
dh_installdocs --link-doc=python-ldap
 
 override_dh_strip:
-   dh_strip --dbg-package=python-ldap-dbg
+   dh_strip -ppython-ldap --dbg-package=python-ldap-dbg
+   dh_strip -ppython3-ldap --dbg-package=python3-ldap-dbg
+
+#override_dh_auto_test:


Bug#884885: RFS: dvdisaster/0.79.6-1

2017-12-20 Thread Carlos Maddela
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: dvdisaster
   Version : 0.79.6-1
   Upstream Author : Carsten Gnörlich 
 * URL : http://dvdisaster.net/
 * License : GPL-3+
   Section : otherosfs

  It builds these binary packages:

dvdisaster - data loss/scratch/aging protection for CD/DVD media
 dvdisaster-doc - data loss/scratch/aging protection for CD/DVD media 
(documentatio

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/dvdisaster/dvdisaster_0.79.6-1.dsc

  Changes have been pushed to 
https://anonscm.debian.org/git/pkg-opt-media/dvdisaster.git/log/?h=experimental/master.

  Changes since the last upload:

  dvdisaster (0.79.6-1) experimental; urgency=medium

* New upstream development version [0.79.6].
* Rebase patches.

   -- Carlos Maddela   Thu, 21 Dec 2017 05:51:54 +1100


  Regards,
   Carlos Maddela


Bug#884884: RFS: dvdisaster/0.79.5-4

2017-12-20 Thread Carlos Maddela
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: dvdisaster
   Version : 0.79.5-4
   Upstream Author : Carsten Gnörlich 
 * URL : http://dvdisaster.net/
 * License : GPL-3+
   Section : otherosfs

  It builds these binary packages:

dvdisaster - data loss/scratch/aging protection for CD/DVD media
 dvdisaster-doc - data loss/scratch/aging protection for CD/DVD media 
(documentatio

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/dvdisaster/dvdisaster_0.79.5-4.dsc

  Changes have been pushed to 
https://anonscm.debian.org/git/pkg-opt-media/dvdisaster.git/log/.

  Changes since the last upload:

  dvdisaster (0.79.5-4) unstable; urgency=medium

* Use complete Debian revision number as build number, instead of
  just the numeric part.
* Re-implement scripts/time-stamper.bash without direct calls to
  dpkg-parsechangelog.
* Call ./configure script directly, instead of relying on debhelper,
  to resolve incompatibilities with Bash-based script.
* Use alternative way of installing icons to remove dependency on
  dh-exec.
* Drop redundant dependency on dpkg-dev.
* Reproducibly generate PDF documentation from TeX sources.
* Remove trailing white space from debian/changelog.
* Remove unnecessary Testsuite header from debian/control.
* Indicate compliance with Debian Policy 4.1.2.
* Suppress debian-watch-uses-insecure-uri Lintian warning.
* Honour LDFLAGS set by dpkg-buildflags in building all binaries.

 -- Carlos Maddela   Thu, 21 Dec 2017 03:14:14 +1100


  Regards,
   Carlos Maddela


Bug#860995: libpodofo: CVE-2017-8054 fix test and (for jessie) missing header attached

2017-12-20 Thread Matthias Brinke
Hello,

I'm sorry to have had missed attaching (in my earlier post to
this bug) what is now attached here: the source code of the test
program for verifying the fix (for both jessie and sid, but the
fix doesn't work with sid's g++-7/libstdc++6, a corrected fix
which I tested in a sid chroot in the meantime will be sent
shortly) and the workaround header for jessie to make available
the method PdfFontFactory::CreateBase14Font(), which the program
generating my PoC needs on jessie. That program also didn't build
on sid, an adapted version will also be provided in my next post.

Best regards, Matthias/***
 *   Copyright (C) 2007 by Dominik Seichter*
 *   domseich...@web.de*
 * *
 *   This program is free software; you can redistribute it and/or modify  *
 *   it under the terms of the GNU Library General Public License as   *
 *   published by the Free Software Foundation; either version 2 of the*
 *   License, or (at your option) any later version.   *
 * *
 *   This program is distributed in the hope that it will be useful,   *
 *   but WITHOUT ANY WARRANTY; without even the implied warranty of*
 *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the *
 *   GNU General Public License for more details.  *
 * *
 *   You should have received a copy of the GNU Library General Public *
 *   License along with this program; if not, write to the *
 *   Free Software Foundation, Inc.,   *
 *   59 Temple Place - Suite 330, Boston, MA  02111-1307, USA. *
 ***/

#ifndef _PDF_FONT_FACTORY_H_
#define _PDF_FONT_FACTORY_H_

#include 
#include 
#include 

namespace PoDoFo {

class PdfFontMetrics;
class PdfVecObjects;

enum EPdfFontFlags {
ePdfFont_Normal = 0x00,
ePdfFont_Embedded   = 0x01,
ePdfFont_Bold   = 0x02,
ePdfFont_Italic = 0x04,
ePdfFont_BoldItalic = ePdfFont_Bold | ePdfFont_Italic,
ePdfFont_Subsetting = 0x08
};

/** This is a factory class which knows
 *  which implementation of PdfFont is required
 *  for a certain font type with certain features (like encoding).
 */
class PODOFO_DOC_API PdfFontFactory {
 public:

/** Create a new PdfFont object.
 *
 *  \param pMetrics pointer to a font metrics object. The font in the PDF
 * file will match this fontmetrics object. The metrics object is 
 * deleted along with the created font. In case of an error, it is deleted
 * here.
 *  \param nFlags font flags or'ed together, specifying the font style and if it should be embedded
 *  \param pEncoding the encoding of this font.
 *  \param pParent the parent of the created font.
 *
 *  \returns a new PdfFont object or NULL
 */
static PdfFont* CreateFontObject( PdfFontMetrics* pMetrics, int nFlags, 
  const PdfEncoding* const pEncoding, PdfVecObjects* pParent );

/** Create a new PdfFont from an existing
 *  font in a PDF file.
 *
 *  \param pLibrary handle to the FreeType library, so that a PdfFontMetrics
 * can be constructed for this font
 *  \param pObject a PDF font object
 */
static PdfFont* CreateFont( FT_Library* pLibrary, PdfObject* pObject );

/** Create a new Base14 (PDF standard/reader built-in) font.
 *
 *  \param pszFontName the name of the font (ASCII)
 *  \param nFlags font flags or'ed together, specifying the font style
 *  \param pEncoding the font's encoding
 *  \param pvecObjects the vector of PDF objects the font is to belong to
 */
	static PdfFont* CreateBase14Font(const char* pszFontName, int nFlags,
  const PdfEncoding * const pEncoding, PdfVecObjects *pvecObjects);

/** Try to guess the fonttype from a the filename of a font file.
 * 
 *  \param pszFilename filename of a fontfile
 *  \returns the font type
 */
static EPdfFontType GetFontType( const char* pszFilename );

 private:
/** Actually creates the font object for the requested type.
 *  Throws an exception in case of an error.
 *
 *  \returns a new PdfFont object or NULL
 */
static PdfFont* CreateFontForType( EPdfFontType eType, PdfFontMetrics* pMetrics, 
   const PdfEncoding* const pEncoding, 
   bool bEmbed, bool bSubsetting, PdfVecObjects* pParent );

};

};
// Workaround for missing static method, copied from part of 

Bug#823373: audio leveller stuck

2017-12-20 Thread Chalilodimun Angel
Hello,

It's the same here.
The audio leveller is stuck, I can't move it at all. I can't work on my
karaoke, it's really annoying. (I'm on Mac, Aegisub 3.2.2)

Chalilo


Bug#863663: Letter to Santa

2017-12-20 Thread Francesco Poli
Dear Santa Claus,
I've been a good boy for the whole year and more.
I would like to receive a little present for this Christmas: I would
like to see GStreamer [bug 783267] solved once and for all.
I hope you can persuade GStreamer developers to devote some of their
time to the resolution of this issue.

Bye,
  Francesco Poli


[bug 783267]: 


;-)

Seriously: is there any progress (not documented on the bugzilla bug)?
Please let me know.


P.S.: Please keep the Debian bug address in Cc. Thanks!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpupsorsEFvE.pgp
Description: PGP signature


Bug#884798: lintian could complain about pkg-config uses that fail to use $ac_tool_prefix

2017-12-20 Thread Chris Lamb
Hi Helmut,

> If yes, what would be a good check? Should it just check the toplevel
> configure.ac and configure.in or any file found on any directory level?

This is my primary concern — warning about broken configure.{am,in} in
code copies etc. that are not used would just be annoying.

It might be safe to simply check ./configure.{am,in} or perhaps a
hardcoded list of subdirs such as src/configure.{am,in}. What do you
think?

> I haven't performed a whole archive-analysis yet, so I cannot tell
> about the amount of fpos to be expected.

Would this be easy for you to do? Please go ahead if so and let us know.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#884865: Working for LunarG

2017-12-20 Thread Brett Johnson
I submitted the original bug from my personal/permanent email address,
because I didn't want to submit it with a temporary address (this one will
disappear as soon as my contract with LunarG ends).  However, I think it's
relevant that I'm currently working for LunarG as a contractor, and debian
packaging is part of what I'm working on for them. So, I just wanted to add
this to the bug, so nobody is confused :)

-- 
Brett Johnson 


Bug#884883: /boot/grub not created, so grub-mkconfig fails

2017-12-20 Thread Joey Hess
Package: grub-coreboot
Version: 2.02-2
Severity: normal

Seems that while grub-pc creates /boot/grub in passing (before putting
some files in there), grub-coreboot and perhaps other grubs does not.
So, installing grub and then running grub-mkconfig may fail, due to the
directory not existing.

That seems like an inconsistency that's worth making consistent.
I noticed because propellor assumed it could do that for all grubs.
Probably d-i does something else that creates /boot/grub before grub-mkconfig
ever gets run, which is why this inconsistency has not been noticed.

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

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

Versions of packages grub-coreboot depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  dpkg   1.19.0.4
ii  grub-common2.02-2
pn  grub-coreboot-bin  
ii  grub2-common   2.02-2
ii  ucf3.0036

grub-coreboot recommends no packages.

grub-coreboot suggests no packages.

-- 
see shy jo


signature.asc
Description: PGP signature


Bug#767847: gworkspace: FTBFS on hurd-i386

2017-12-20 Thread Yavor Doganov
Ivan Vučica wrote:
> Also malloc(...)+1 should be malloc(...+1).

That's right, it is the latter in my patch.

> Also strncpy() IIRC doesn’t add a nul terminator.

Correct, it is added with a special assignment after the loop, so
this is already handled.

> How about calloc() to also zero the memory out, or at least
> newpath[newblen] = 0? (Or the equivalent in the new patch.)

Perhaps this is a good idea.

> Alternatively just use ObjC to manipulate strings of UTF8 text.

The usual approach in fixing arch-specific bugs, at least in Debian,
is to try not to diverge much from the existing code.  Of course ObjC
can be used, probably even SQLClient.



Bug#884881: apt-cacher-ng: Remap-... directives without TargetURLs are incompatible with ForceManaged

2017-12-20 Thread Alexander Cherepanov

Package: apt-cacher-ng
Version: 2-1~bpo8+1
Tags: security

It seems the conf line 'Remap-secdeb: security.debian.org' doesn't work 
with 'ForceManaged: 1'. It works without ForceManaged -- files are put 
in cache under secdeb. And it works with ForceManaged if you add 
'security.debian.org' once more time as TargetURLs.


Here is a test illustrating the problem:

--
# apt-get purge apt-cacher-ng -y && rm -r /etc/apt-cacher-ng/ && apt-get 
install apt-cacher-ng

[skip]
# echo 'Remap-secdeb: security.debian.org' > /etc/apt-cacher-ng/my.conf
# service apt-cacher-ng restart
# curl -I -x http://127.0.0.1:3142/ 
http://security.debian.org/dists/jessie/updates/InRelease

HTTP/1.1 200 OK
Content-Length: 63113
Last-Modified: Wed, 20 Dec 2017 21:47:45 GMT
Content-Type: application/octet-stream
Date: Wed Dec 20 21:55:39 2017
Server: Debian Apt-Cacher NG/0.8.0
X-Original-Source: http://security.debian.org/dists/jessie/updates/InRelease
Connection: Keep-Alive

# ls /var/cache/apt-cacher-ng/
secdeb
# echo 'ForceManaged: 1' >> /etc/apt-cacher-ng/my.conf
# service apt-cacher-ng restart
# curl -I -x http://127.0.0.1:3142/ 
http://security.debian.org/dists/jessie/updates/InRelease
HTTP/1.1 403 Forbidden file type or location: 
http://security.debian.org/dists/jessie/updates/InRelease

Content-Length: 186
Content-Type: text/html
Date: Wed Dec 20 21:55:39 2017
Server: Debian Apt-Cacher NG/0.8.0
Connection: Keep-Alive

# echo 'Remap-secdeb: security.debian.org ; security.debian.org' > 
/etc/apt-cacher-ng/my.conf

# echo 'ForceManaged: 1' >>  /etc/apt-cacher-ng/my.conf
# service apt-cacher-ng restart
# curl -I -x http://127.0.0.1:3142/ 
http://security.debian.org/dists/jessie/updates/InRelease

HTTP/1.1 200 OK
Content-Length: 63113
Last-Modified: Wed, 20 Dec 2017 21:47:45 GMT
Content-Type: application/octet-stream
Date: Wed Dec 20 21:55:39 2017
Server: Debian Apt-Cacher NG/0.8.0
X-Original-Source: http://security.debian.org/dists/jessie/updates/InRelease
Connection: Keep-Alive

--

Tested with apt-cacher-ng from jessie (0.8.0-3) and from 
jessie-backports (2-1~bpo8+1).


AIUI it should work without TargetURLs. The doc at [1] seems to imply it:

"If the ForceManaged option is set, only requests to URL matched in some 
Remap-... config is allowed."


[1] 
https://www.unix-ag.uni-kl.de/~bloch/acng/html/config-serv.html#remap-trickz


And a comment in /etc/apt-cacher-ng/acng.conf for Remap-secdeb without 
TargetURLs directly talks about ForceManaged use case:


# This is usually not needed for security.debian.org because it's always the
# same DNS hostname. However, it might be enabled in order to use hooks
# or ForceManaged mode or special flags in this context. Not set by default.
# Remap-secdeb: security.debian.org

I've put the 'security' tag on this bug as a straightforward and 
documented config will cause clients to miss security updates. A simple 
test from an admin of this setup would reveal the problem so the danger 
doesn't seem great:-)


--
Alexander Cherepanov



Bug#884882: Please add python3-ldap

2017-12-20 Thread Timo Aaltonen
Package: python-ldap
Severity: normal

Hi, please package a python3 version of the module.

t



Bug#505857: lintian: false positive debian-watch-file-should-mangle-version

2017-12-20 Thread Chris Lamb
clone 505857 -1
reassign -1 devscripts 2.17.11
severity -1 wishlist
retitle -1 [uscan] Please clarify that spaces in debian/watch "opts" are only 
valid in version 4
thanks

Hi Christoph,

> The warning goes away when I remove the space after the comma.
> 
> The version with the space is the syntax documented in uscan(1):
> 
>   Multiple options option1, option2, option3, ... can be set as
>   opts="option1, option2, option3,  ...  " .

Only for version=4. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#884784: systemd-network segfaults

2017-12-20 Thread Michael Biebl
Am 20.12.2017 um 17:35 schrieb Rémi Denis-Courmont:
> Le keskiviikkona 20. joulukuuta 2017, 0.05.02 EET Michael Biebl a écrit :

>> Please try to provide a backtrace of the crash.
> 
> eth0: Gained IPv6LL
> 
> Program received signal SIGSEGV, Segmentation fault.

...
>> That kernel is not provided by Debian. Can you reproduce the issue with
>> a Debian kernel as well?
> 
> Yes, it crashes the same with 4.12.0-1-amd64 *and* the configuration fixes 
> above.
> 

Ok, thanks for the additional information, Rémi.
If you have a github account, it would be great if you can file an
upstream bug report at https://github.com/systemd/systemd/issues with
the information you provided here.

You might check https://github.com/systemd/systemd/issues/7708 before
doing that though, as it might be related.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#884258: machinectl shell should use bash as a default

2017-12-20 Thread Michael Biebl
On Wed, 13 Dec 2017 01:26:00 +0100 Michael Biebl  wrote:
> Am 13.12.2017 um 00:30 schrieb Marco d'Itri:
> > Package: systemd-container
> > Version: 235-3
> > Severity: normal
> > 
> > Until https://github.com/systemd/systemd/issues/1395 will be fixed, 
> > machinectl should be patched to use /bin/bash as the default shell 
> > instead of /bin/sh.
> > While some people may favour a different interactive shell it is quite 
> > obvious that nobody wants to use dash as their interactive shell, so 
> > this saves the need to type "exec bash" every time.
> > 
> > This is a single line change in bus_machine_method_open_shell() in 
> > src/machine/machine-dbus.c.
> 
> Makes sense. Feel free to commit this change.

After the points raised upstream, I guess using /bin/bash is probably
not the best idea, as we can't know what's inside the container.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#882159: Bambi, your recent order 304578 ZU

2017-12-20 Thread Bambi Brusco
What is this about?

Bambi

On Nov 27, 2017 1:16 PM, "Amazon FinalNotice"  wrote:

Notice for Bambi


































































































Hello, Joachim Wiedorn schrob: > Hello Jan, FYI: >  original message
 > From: e...@users.sourceforge.net > Date: Sun, 26 Nov 2017 21:55:28
+0100 > To: Joachim Wiedorn , cont...@bugs.debian.org, >
882...@bugs.debian.org > > can the reporter maybe test the current
snapshot? it should fix the issue. > http://duply.net/wiki/index.
php/Duply-code#Latest_Development_Snapshot The "2.0.4dev" version I
downloaded just now from http://duply.net/tmp/duply.sh works for me,
outputs times like | --- Finished state OK at 19:34:48.724 - Runtime
00:00:00.075 --- and takes the "date_fix %s%N" branch (verified via debug
printf). The diff looks good to me as well. Thanks a lot for the quick fix!
I noticed two unrelated minor oddities: 1) On the first run (per profile)
with the new version, duply would re-sync all the metadata. That's because
of the bugfix for #117, which moved the metadata location from
"$ARCH_DIR/duply_$profile" to "$ARCH_DIR/$profile". That leaves around the
old, now-useless metadata folder. Not a big deal, but maybe it would have
been better to adjust the comment to match the code instead of the other
way around? 2) In line 2172, | # for sec�rity reasons, we url_encode
username to protect special chars there's some (for me undisplayable)
unicode (%EF%BF%BD) instead of the 'u' in "security". Funny, given the
context. :D HTH and thanks again, Jan


Bug#839880: proftpd-basic: proftpd server instance crashed with signal 11

2017-12-20 Thread Hilmar Preuße
On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,

> proftpd started successfully in my jessie system.  However after some day
> (it may be after a system-wide upgrade) the client failed to login.
> 
For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
  pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch
[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature


Bug#884003: FDT overlay support

2017-12-20 Thread Vagrant Cascadian
On 2017-12-12, Andre Heider wrote:
> Attached a patch series with an implementation.

Thanks for the patches!


> I added the ability to concatenate multiple scripts/snippets for the 
> final boot script.
> The new overlay handling snippet is supposed to be 
> used with this. But the feature itself also allows nice cleanups, 
> demonstrated on odroid-u3 and beaglebone (and there're quite some more 
> cleanups possible).

I very much like the idea of this; so many of the boot scripts
copy-and-paste a lot of code between them, which makes maintenence more
difficult as well as implementing features and changes across all the
boot scripts...

Unfortunately, I haven't had a chance to do more than a very cursory
glance at your patches yet. Made some comments in-line on some of the
individual patches below.


> To test this, you need:
> - u-boot with CONFIG_OF_LIBFDT_OVERLAY
> - base dtb with symbols (-@)

Would the symbols (-@) be harmful to enable in Debian's kernels by
default?

Is it feasible to use dtc to extract the .dts, rebuild it with -@, and
then use that .dtb instead... or does it need more information from the
original device tree(s)?


> - your own overlays, again with symbols, in /boot/dtbs/overlays

Are there some very basic example overlays that would be feasible to just test 
that
this feature is working?

I don't have much experience with overlays, but have a beagleboneblack
and a CHIP that in theory support this, and some devices I can attach
that require overlays...

Will try to test myself sometime in the coming weeks.


> With e.g. foo.dtb and bar.dtb in /boot/dtbs/overlays you can then set 
> either set $fk_overlays on the u-boot prompt or OVERLAYS in 
> /etc/defaults/flash-kernel to "foo bar".
>
> Testing on beaglebone looks promising so far ;)

This is great!


> From efaadbd96967674f2fb82eb530dd447a6b5c65ba Mon Sep 17 00:00:00 2001
> From: Andre Heider 
> Date: Tue, 12 Dec 2017 09:23:37 +0100
> Subject: [PATCH 01/10] bootscr.uboot-generic: quote bootargs
>
> Signed-off-by: Andre Heider 
> ---
>  bootscript/all/bootscr.uboot-generic | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bootscript/all/bootscr.uboot-generic 
> b/bootscript/all/bootscr.uboot-generic
> index db4066a..bcf6e96 100644
> --- a/bootscript/all/bootscr.uboot-generic
> +++ b/bootscript/all/bootscr.uboot-generic
> @@ -25,7 +25,7 @@ if test -n "${console}"; then
>setenv bootargs "${bootargs} console=${console}"
>  fi
>  
> -setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} 
> @@LINUX_KERNEL_CMDLINE@@
> +setenv bootargs "@@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} 
> @@LINUX_KERNEL_CMDLINE@@"
>  @@UBOOT_ENV_EXTRA@@
>  
>  if test -z "${fk_kvers}"; then

Why is this needed?


> From 8dd287741e23ea06c6a8e480ab1f24689d36bf9b Mon Sep 17 00:00:00 2001
> From: Andre Heider 
> Date: Tue, 12 Dec 2017 08:18:12 +0100
> Subject: [PATCH 03/10] Add support for multiple scripts sources
>
> Allow multiple entries in 'U-Boot-Script-Name' and concatenate them
> as the final boot script.
>
> Signed-off-by: Andre Heider 
> ---
>  functions | 6 +-
>  1 file changed, 5 insertions(+), 1 deletion(-)
...
> From 132dfdeb0e9a5a396ee543ee1386cb750929846f Mon Sep 17 00:00:00 2001
> From: Andre Heider 
> Date: Tue, 12 Dec 2017 09:12:28 +0100
> Subject: [PATCH 04/10] odroid-u3: clean up boot script
>
> bootscr.odroid first sets some compatibility variables and then contains
> a full copy of bootscr.uboot-generic.
>
> Get rid of the copy and use the multiple scripts feature instead. This
> results in the very same boot script.
>
> Signed-off-by: Andre Heider 
> ---
>  bootscript/armhf/bootscr.odroid | 63 
> -
>  db/all.db   |  2 +-
>  2 files changed, 1 insertion(+), 64 deletions(-)

Love these!


> From b29052bfe4deaf359635347e1e0fc559059067e9 Mon Sep 17 00:00:00 2001
> From: Andre Heider 
> Date: Tue, 12 Dec 2017 09:25:26 +0100
> Subject: [PATCH 05/10] bootscr.uboot-generic: support multiple prefixes to
>  load from
>
> Allow custom boot scripts to set $fk_image_locations as a list of
> directories to load boot files from.
>
> If unset, $prefix will be the used - which is sufficient for all recent
> u-boot versions.
>
> This allows the clean up of various custom boot scripts. Code borrowed
> form the sunxi script.
>
> Signed-off-by: Andre Heider 
> ---
>  bootscript/all/bootscr.uboot-generic | 38 
> +---
>  1 file changed, 27 insertions(+), 11 deletions(-)
>
> diff --git a/bootscript/all/bootscr.uboot-generic 
> b/bootscript/all/bootscr.uboot-generic
> index bcf6e96..509efe7 100644
> --- a/bootscript/all/bootscr.uboot-generic
> +++ b/bootscript/all/bootscr.uboot-generic
> @@ -48,14 +48,30 @@ else
>setenv partition ${distro_bootpart}
>  fi
>  
> -load 

Bug#884878: ruby2.5: CVE-2017-17790: fixed command injection

2017-12-20 Thread Salvatore Bonaccorso
Source: ruby2.5
Version: 2.5.0~preview1-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/ruby/ruby/pull/1777
Control: clone -1 -2
Control: reassign -2 ruby2.3 2.3.5-1
Control: found -2 2.3.3-1
Control: retitle -2 ruby2.3: CVE-2017-17790: fixed command injection

Hi,

the following vulnerability was published for ruby2.5.

CVE-2017-17790[0]:
| The lazy_initialize function in lib/resolv.rb in Ruby through 2.4.3
| uses Kernel#open, which might allow Command Injection attacks, as
| demonstrated by a Resolv::Hosts::new argument beginning with a '|'
| character, a different vulnerability than CVE-2017-17405. NOTE:
| situations with untrusted input may be highly unlikely.

As already mentioned in the CVE description, it's quite unlikely that
there is external input fed to Resolv::Hosts. But a fix can be
included in any future DSA as well.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-17790
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17790
[1] https://github.com/ruby/ruby/pull/1777
[2] https://github.com/ruby/ruby/commit/e7464561b5151501beb356fc750d5dd1a88014f7

Regards,
Salvatore



Bug#884776: libc6: pthread_cond_broadcast() blocks indefinitely on process-shared cond-var

2017-12-20 Thread Aurelien Jarno
Hi,

On 2017-12-19 16:41, Florian Schmidt wrote:
> Package: libc6
> Version: 2.25-3
> Severity: important
> Tags: upstream
> 
> TL;DR: pthread_cond_broadcast() on a process shared condition variable
> will block indefinitely when another process that
> pthread_cond_wait()'ed on this condition gets killed and restarted.
> 
> starting with libc6:armd64 version 2.25-3 from debian testing/buster, our
> in-house robotics communication middleware (links_and_nodes) does no
> longer behave as expected:
> 
> this middleware uses process shared mutex'es and condition variables
> in shared memory (pthread_mutex_t, pthread_cond_t, shm_open) for
> synchronization between processes.
> 
> attached is a simple self-contained test-case where a
> "publisher"-process repeatedly increments a counter in shm (while
> holding a pshared mutex) and then broadcasts the condition.

Thanks a lot for this testcase, it helps a lot to understand the issue
and will definitely help to get this issue solved.

> another process (lets call it "subscriber") is blocking waiting on
> that same condition variable (with the same mutex).
> 
> this works as expected. until the subscriber is killed/terminated by
> any signal while it is waiting.
> when the subscriber is then started a 2nd time, the publisher gets
> blocked in its call to pthread_cond_broadcast()!

In practice the issue is also there when there are two or more
subscribers, as soon as one subscriber is killed, the problem occurs.
It seems to that the condvar code is not able to detect that one of the
waiters got killed while the mutex is locked, though it's able to detect
that there are no waiter at all. That's why pthread_cond_broadcast waits
indefinitely in futex_wait.

> with glibc <= 2.24 this caused no problems. i saw that there is a new
> condvar impl in glibc 2.25 -- so this is probably something for
> upstream.

I confirm this is due to the new condvar implementation, more precisely
to the following commit:

| commit ed19993b5b0d05d62cc883571519a67dae481a14
| Author: Torvald Riegel 
| Date:   Wed May 25 23:43:36 2016 +0200
|
| New condvar implementation that provides stronger ordering guarantees.

Your test case works just before this commit and fail when it's applied.
 
> with the attached test case i can reproduce this problem with debians
> libc6 version 2.25-3 (buster), 2.25-5 (sid) and 2.26-0experimental2
> (experimental).

I have also tested that the problem is still present in upstream git
HEAD.

It looks to me the best is to take this issue upstream. Do you want me
to forward your bug report and your example in the upstream bugzilla [1] 
or do you prefer to do it yourself?

Aurelien

[1] https://sourceware.org/bugzilla

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net



Bug#884060: iproute2: Upgrade from 4.9.0-2 to 4.9.0-2.1 breaks wireless.

2017-12-20 Thread Van
I downgraded today from 4.13.0-1 to 4.9.0-2.1.  Initially, I wasn't able to 
connect via wireless.  Network manager made several attempts then just stopped 
trying.  I then restarted network manager service (systemctl restart 
network-manager.service), but network manager made several unsuccessful 
attempts to connect and then just stopped trying.  After a few more minutes, 
network manager successfully connected.  So, perhaps 4.9.0-2.1 just caused an 
issue(s) where it takes network manager longer to establish a wifi connection.

I'm including additional info below.  Again though, my belief is that whatever 
the issue is with 4.9.0-2.1, if there is an issue, appears to have been 
resolved with 4.13.0-1.  My wifi connection is established without issue upon 
bootup with 4.13.0-1.

I don't know if it's relevent, but when looking through the output of 
journalctl, a different MAC is set for my wireless card and then gets set to 
the real MAC.

*** Output of lspci -knn | grep -EiA2 net ***
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:8554]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Broadcom Limited BCM4352 802.11ac Wireless 
Network Adapter [14e4:43b1] (rev 03)
Subsystem: AzureWave BCM4352 802.11ac Wireless Network Adapter 
[1a3b:2123]
Kernel driver in use: wl
Kernel modules: bcma, wl

*** Output of dmesg | grep -Ei 'wlan|firmw|dhc' ***
[0.08] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.882349] sdhci: Secure Digital Host Controller Interface driver
[0.882350] sdhci: Copyright(c) Pierre Ossman
[6.941882] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[6.980463] ene_ir: Firmware regs: c1 00
[8.161860] wlan0: Broadcom BCM43b1 802.11 Hybrid Wireless Controller 
6.30.223.271 (r587334)
[8.468023] bluetooth hci0: firmware: failed to load 
brcm/BCM20702A1-13d3-3404.hcd (-2)
[8.468024] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-13d3-3404.hcd failed with error -2
[8.531524] wl :03:00.0 wlp3s0: renamed from wlan0
[   21.709869] r8169 :02:00.0: firmware: failed to load 
rtl_nic/rtl8168g-2.fw (-2)
[   21.709902] r8169 :02:00.0: Direct firmware load for 
rtl_nic/rtl8168g-2.fw failed with error -2
[   21.709904] r8169 :02:00.0 enp2s0: unable to load firmware patch 
rtl_nic/rtl8168g-2.fw (-2)

*** Output of journalctl | grep 'wlp3s0' ***
Dec 20 12:20:19 debian-unstable kernel: wl :03:00.0 wlp3s0: renamed from 
wlan0
Dec 20 12:20:31 debian-unstable NetworkManager[653]:   [1513790431.2725] 
devices added (path: 
/sys/devices/pci:00/:00:1c.3/:03:00.0/net/wlp3s0, iface: wlp3s0)
Dec 20 12:20:31 debian-unstable NetworkManager[653]:   [1513790431.2725] 
device added (path: 
/sys/devices/pci:00/:00:1c.3/:03:00.0/net/wlp3s0, iface: wlp3s0): 
no ifupdown configuration found.
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.4159] 
wifi-nl80211: (wlp3s0): using nl80211 for WiFi device control
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.4169] 
manager: (wlp3s0): new 802.11 WiFi device 
(/org/freedesktop/NetworkManager/Devices/3)
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.4178] 
device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
Dec 20 12:20:32 debian-unstable kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link 
is not ready
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.4934] 
device (wlp3s0): set-hw-addr: set MAC address to [redacted] (scanning)
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.5333] 
device (wlp3s0): supplicant interface state: init -> starting
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.7237] 
sup-iface[0x560a5a808990,wlp3s0]: supports 1 scan SSIDs
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.7269] 
device (wlp3s0): supplicant interface state: starting -> ready
Dec 20 12:20:32 debian-unstable NetworkManager[653]:   [1513790432.7270] 
device (wlp3s0): state change: unavailable -> disconnected (reason 
'supplicant-available', sys-iface-state: 'managed')
Dec 20 12:20:34 debian-unstable NetworkManager[653]:   [1513790434.4751] 
device (wlp3s0): Activation: starting connection [redacted]
Dec 20 12:20:34 debian-unstable NetworkManager[653]:   [1513790434.4753] 
device (wlp3s0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
Dec 20 12:20:34 debian-unstable NetworkManager[653]:   [1513790434.4759] 
device (wlp3s0): set-hw-addr: reset MAC address to [redacted] (preserve)
Dec 20 12:20:34 debian-unstable NetworkManager[653]:   [1513790434.4766] 
device (wlp3s0): state change: prepare -> config 

Bug#884835: [Pkg-mailman-hackers] Bug#884835: mailman3-suite: postinst fails if nginx is installed and apache2 is missing

2017-12-20 Thread Philip Frei
Hi,

Am Wed, 20 Dec 2017 17:50:42 +0100
schrieb Pierre-Elliott Bécue :

> Please provide a little more output to explain how the postinst will
> fail? Did you chose "none" for the webserver to configure?

Atfer the installation failed I removed and purged all related
packages. With a fresh install there's no question about choosing the
webserver.

This is the relevant output of the script:

+ [ -e /usr/share/apache2/apache2-maintscript-helper ]
+ settings_local_new=
+ hyperkitty_cfg_new=
+ django_admin_args=--verbosity 0 --no-color
--pythonpath /usr/share/mailman3-suite --settings settings
+ db_get mailman3-suite/reconfigure-webserver
+ _db_cmd GET mailman3-suite/reconfigure-webserver
+ _db_internal_IFS= 

+ IFS= 
+ printf %s\n GET mailman3-suite/reconfigure-webserver
+ IFS=  

+ IFS=
 read -r _db_internal_line
+ RET=apache2
+ return 0
+ webservers=apache2
+ restart=
+ webserver=apache2
+ apache_install
+ return 1
dpkg: error processing package mailman3-suite (--configure):
 subprocess installed post-installation script returned error exit
  status 1 Errors were encountered while processing:
 mailman3-suite


regards,
Phil



Bug#884877: setup-mysql: Could not open required defaults file: /etc/mysql/debian.cnf

2017-12-20 Thread Nick Aquina
Package: wordpress
Version: 4.7.5+dfsg-2+deb9u1
Severity: normal

Error occurs when running:
$ sudo ./setup-mysql -n wordpress example.org
PING example.org (93.184.216.34) 56(84) bytes of data.
64 bytes from 93.184.216.34 (93.184.216.34): icmp_seq=1 ttl=49 time=76.3
ms

--- example.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 76.340/76.340/76.340/0.000 ms
/etc/wordpress/config-example.org.php written
Could not open required defaults file: /etc/mysql/debian.cnf
Fatal error in defaults handling. Program aborted

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

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

Versions of packages wordpress depends on:
ii  apache2 [httpd] 2.4.25-3+deb9u3
ii  ca-certificates 20161130+nmu1
ii  default-mysql-client1.0.2
ii  libapache2-mod-php  1:7.0+49
ii  libapache2-mod-php7.0 [libapache2-mod-php]  7.0.19-1
ii  libjs-cropper   1.2.2-1
ii  libphp-phpmailer5.2.14+dfsg-2.3
ii  mariadb-client-10.1 [virtual-mysql-client]  10.1.26-0+deb9u1
ii  php-gd  1:7.0+49
ii  php-getid3  1.9.12+dfsg-1
ii  php-mysql   1:7.0+49
ii  php7.0-gd [php-gd]  7.0.19-1
ii  php7.0-mysql [php-mysqlnd]  7.0.19-1

Versions of packages wordpress recommends:
ii  wordpress-l10n   4.7.5+dfsg-2+deb9u1
ii  wordpress-theme-twentyseventeen  4.7.5+dfsg-2+deb9u1

Versions of packages wordpress suggests:
pn  default-mysql-server | virtual-mysql-server  
pn  php-ssh2 

-- no debconf information



Bug#767847: [Debian GNUstep maintainers] Bug#767847: gworkspace: FTBFS on hurd-i386

2017-12-20 Thread Ivan Vučica
sri, 20. pro 2017. u 20:33 Yavor Doganov  napisao je:

> Hi,
>
> On Sun, Nov 02, 2014 at 11:24:11PM +0100, Svante Signell wrote:
> > Source: gworkspace
> > Version: 0.9.2-1
>
> > Currently gworkspace FTBFS on GNU/Hurd due to usage of PATH_MAX, which
> > is not defined. It did build previously, latest Hurd version is
> > 0.8.8-1.2+b1. The attached patch solves this by allocating the newpath
> > string in GWMetadata/gmds/gmds/gmds.m and
> > GWMetadata/gmds/mdextractor/mdextractor.m dynamically.
>
> Many thanks for the patch and sorry for the belated response.
> However, IMHO the patch is not completely correct:
>
> > --- gworkspace-0.9.2.orig/GWMetadata/gmds/gmds/gmds.m
> > +++ gworkspace-0.9.2/GWMetadata/gmds/gmds/gmds.m
> > -  char newpath[PATH_MAX] = "";
> > +  char *newpath = NULL;
> >int i = newblen;
> >int j;
> >
> > -  strncpy(newpath, (const char *)newbase, newblen);
> > -
> > +  newpath = malloc(newblen) + 1;
> > +  strncpy(newpath, (const char *)newbase, newblen + 1);
>
> newblen is not sufficient size for the allocated string.  If oldbase
> is "/foo", newbase is "/frob" and oldpath is "/foo/bar", newpath
> should become "/frob/bar", so there would be an invalid write in the
> loop below.  If newbase is "/frobnication" it gets worse.


Also malloc(...)+1 should be malloc(...+1). (You addressed this differently
in your patch but I can't see enough context on my phone to judge if this
or other stuff is right.)

Also strncpy() IIRC doesn’t add a nul terminator.

How about calloc() to also zero the memory out, or at least
newpath[newblen] = 0? (Or the equivalent in the new patch.)

Alternatively just use ObjC to manipulate strings of UTF8 text.



>
> >for (j = oldblen; j < oldplen; j++) {
> >  newpath[i] = oldpath[j];
> >  i++;
>
> I plan to apply a slightly modified version of the patch (attached)
> that fixes the above problem, removes the unnecessary initial
> assignment and also frees the allocated string (these programs are
> daemons so memory leaks should be avoided).  Ideally, there should be
> a check for malloc failure as well but I'll leave that to upstream as
> I'm not sure what should be done -- silent return, abort, or let the
> program crash.
>
> OK?
> ___
> Debian GNUstep maintainers mailing list
> pkg-gnustep-maintain...@lists.alioth.debian.org
>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gnustep-maintainers

-- 
Sent from Gmail Mobile on iPad


Bug#884799: [Pkg-xfce-devel] Bug#884799: thunar: Shredding a file causes Thunar to block permanently. (USB)

2017-12-20 Thread Lorenzo Ancora
Hello,
let me clarify your doubts, so it will be easier to debug. :-)
> I'm sorry to hear that, but I don't think I can reproduce that (also it's
> unclear what “shredding” exactly means here).
It means standard secure deletion by using "shred" from the GNU Coreutils.
GNU shred:
https://www.gnu.org/software/coreutils/manual/html_node/shred-invocation.html
Command: $ shred -zu smallFileOnUSBkey.txt
> Also it's quite likely that you
> actually removed the USB key while the thunar process was still having
> open fd
> on the usb key, which is definitely the wrong thing to do.
The file was deleted from the key but did not disappear from Thunar,
because the GUI was totally frozen.
After a while the WM reported that Thunar was frozen and asked me to
terminate it.
After restarting Thunar, I managed to eject the USB key and the chain of
crashes and slowness began.

To further help you to reproduce the problem, this is the USB key entry
from "/etc/mtab":

/dev/sdb1 /media/lorenzo/36FD-4552 vfat
rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro
0 0

Regards,
Lorenzo

On Wed, 20 Dec 2017 14:46:40 +0100 Yves-Alexis Perez 
wrote:
> control: severity -1 important
> control: tag -1 unreproducible moreinfo
>
> On Tue, 2017-12-19 at 20:58 +0100, Lorenzo Ancora wrote:
> > Dear Maintainer,
> > shredding a file in a mounted USB key causes `Thunar 1.6.11 (Xfce
4.12)` to
> > block permanently.
> > The window with the key won't close and Thunar must be killed
manually; it can
> > be restarted (must wait 2 minutes on a Intel Core i5) but is very
slow and you
> > can just eject the USB device. After ejecting the USB device the
problem does
> > not disappear and gets even worse.
> > Logging out causes `lightdm 1.18.3` to restart... and it keeps
restarting
> > forever, in a loop.
> > From `lightdm` it becames impossible to reboot, shutdown etc. and it
must be
> > done from a VT.
> > Activating the rescue mode (single user mode) from `systemctl` and
going back
> > does not fix the problem.
> > Apparently the only way to fix the problem is to stop
lightdm.service and
> > reboot the system.
>
> Hi,
>
> I'm sorry to hear that, but I don't think I can reproduce that (also it's
> unclear what “shredding” exactly means here). Also it's quite likely
that you
> actually removed the USB key while the thunar process was still having
open fd
> on the usb key, which is definitely the wrong thing to do.
>
> Regards,
> --
> Yves-Alexis


Bug#884876: /usr/bin/zstd: statically linked against libzstd while depending on it

2017-12-20 Thread Shawn Landden
Package: zstd
Version: 1.3.2+dfsg2-1
Severity: normal
File: /usr/bin/zstd

Dear Maintainer,

shawn@t410s:~/git/distcc/build$ apt show zstd | grep libzstd
Source: libzstd
Depends: libzstd1 (= 1.3.2+dfsg2-1), libc6 (>= 2.17), libgcc1 (>= 1:3.0), 
libstdc++6 (>= 6)
shawn@t410s:~/git/distcc/build$ ldd /usr/bin/zstd
linux-vdso.so.1 (0x7fff63b89000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fea7539a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fea74ff7000)
/lib64/ld-linux-x86-64.so.2 (0x7fea75833000)

either use shared linking (-DZSTD_BUILD_STATIC:BOOL=OFF) or do not depend on 
libzstd1

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

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

Versions of packages zstd depends on:
ii  libc6   2.25-5
ii  libgcc1 1:7.2.0-18
ii  libstdc++6  7.2.0-18
ii  libzstd11.3.2+dfsg2-1

zstd recommends no packages.

zstd suggests no packages.

-- no debconf information



Bug#767847: gworkspace: FTBFS on hurd-i386

2017-12-20 Thread Yavor Doganov
Hi,

On Sun, Nov 02, 2014 at 11:24:11PM +0100, Svante Signell wrote:
> Source: gworkspace
> Version: 0.9.2-1

> Currently gworkspace FTBFS on GNU/Hurd due to usage of PATH_MAX, which
> is not defined. It did build previously, latest Hurd version is
> 0.8.8-1.2+b1. The attached patch solves this by allocating the newpath
> string in GWMetadata/gmds/gmds/gmds.m and
> GWMetadata/gmds/mdextractor/mdextractor.m dynamically.

Many thanks for the patch and sorry for the belated response.
However, IMHO the patch is not completely correct:

> --- gworkspace-0.9.2.orig/GWMetadata/gmds/gmds/gmds.m
> +++ gworkspace-0.9.2/GWMetadata/gmds/gmds/gmds.m
> -  char newpath[PATH_MAX] = "";
> +  char *newpath = NULL;
>int i = newblen;
>int j;
>
> -  strncpy(newpath, (const char *)newbase, newblen);  
> -  
> +  newpath = malloc(newblen) + 1;
> +  strncpy(newpath, (const char *)newbase, newblen + 1);

newblen is not sufficient size for the allocated string.  If oldbase
is "/foo", newbase is "/frob" and oldpath is "/foo/bar", newpath
should become "/frob/bar", so there would be an invalid write in the
loop below.  If newbase is "/frobnication" it gets worse.

>for (j = oldblen; j < oldplen; j++) {
>  newpath[i] = oldpath[j];
>  i++;

I plan to apply a slightly modified version of the patch (attached)
that fixes the above problem, removes the unnecessary initial
assignment and also frees the allocated string (these programs are
daemons so memory leaks should be avoided).  Ideally, there should be
a check for malloc failure as well but I'll leave that to upstream as
I'm not sure what should be done -- silent return, abort, or let the
program crash.

OK?
--- gworkspace-0.9.3.orig/GWMetadata/gmds/gmds/gmds.m
+++ gworkspace-0.9.3/GWMetadata/gmds/gmds/gmds.m
@@ -94,12 +94,13 @@
   int newblen = strlen((const char *)newbase);
   const unsigned char *oldpath = sqlite3_value_text(argv[2]);
   int oldplen = strlen((const char *)oldpath);
-  char newpath[PATH_MAX] = "";
+  char *newpath;
   int i = newblen;
   int j;
   
-  strncpy(newpath, (const char *)newbase, newblen);  
-  
+  newpath = malloc(newblen + oldplen - oldblen + 1);
+  strncpy(newpath, (const char *)newbase, newblen + oldplen - oldblen + 1);
+
   for (j = oldblen; j < oldplen; j++) {
 newpath[i] = oldpath[j];
 i++;
@@ -108,6 +109,8 @@
   newpath[i] = '\0';
   
   sqlite3_result_text(context, newpath, strlen(newpath), SQLITE_TRANSIENT);
+
+  free(newpath);
 }
 
 static void time_stamp(sqlite3_context *context, int argc, sqlite3_value **argv)
--- gworkspace-0.9.3.orig/GWMetadata/gmds/mdextractor/mdextractor.m
+++ gworkspace-0.9.3/GWMetadata/gmds/mdextractor/mdextractor.m
@@ -87,12 +87,13 @@
   int newblen = strlen((const char *)newbase);
   const unsigned char *oldpath = sqlite3_value_text(argv[2]);
   int oldplen = strlen((const char *)oldpath);
-  char newpath[PATH_MAX] = "";
+  char *newpath;
   int i = newblen;
   int j;
-  
-  strncpy(newpath, (const char *)newbase, newblen);  
-  
+
+  newpath = malloc(newblen + oldplen - oldblen + 1);
+  strncpy(newpath, (const char *)newbase, newblen + oldplen - oldblen + 1);
+
   for (j = oldblen; j < oldplen; j++) {
 newpath[i] = oldpath[j];
 i++;
@@ -101,6 +102,8 @@
   newpath[i] = '\0';
   
   sqlite3_result_text(context, newpath, strlen(newpath), SQLITE_TRANSIENT);
+
+  free(newpath);
 }
 
 static void time_stamp(sqlite3_context *context, int argc, sqlite3_value **argv)


Bug#884870: lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree

2017-12-20 Thread Chris Lamb
Hi Jeremy,

> Now, I think (lintian's website is recovering from a typo) that this
> now causes lintian to emit vcs-field-has-unexpected-spaces
> 
> I think the " -b BRANCHNAME" suffix should be considered valid syntax
> for Vcs-Git.

Something else must be going on as this is indeed supported. Here is the
code in question:

# git uri followed by optional " -b " + branchname:
git => sub { return shift =~ /^(.+?)(?:\s+-b\s+(\S*))?$/;},

… and I've even just committed a (passing) test for this:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=8e1ba53fa85469ab4f2e67e7514b3a800c0a6004

:)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#884874: phonon-backend-vlc: Application using phonon are crashing with vlc 3.0.0~rc2

2017-12-20 Thread Sandro Knauß
Source: phonon-backend-vlc
Version: 0.9.0-2
Severity: serious

with the upload of vlc 3.0.0~rc2-1 at unstable phonon applications like
amarok and kcmshell4 kcm_phonon are constanly crashing. For the moment I
switched to gstreamer backend.


Best Regards,

sandro

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

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



Bug#884875: cmd2: Drop import of gtk along with move of pyperclip to use gi (GTK+3)

2017-12-20 Thread Corey Bryant
Package: cmd2
Version: 0.7.7-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/drop-import-gtk.patch: Drop import of gtk now that pyperclip uses gi.
NOTE: This requires the corresponding patch to python-pyperclip in
Bug#884873 (python-pyperclip: move to gtk+3 to avoid use of mutual
exclusive gtk+2/gtk+3 modules).


Thanks for considering the patch.


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

Kernel: Linux 4.13.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cmd2-0.7.7/debian/patches/drop-import-gtk.patch 
cmd2-0.7.7/debian/patches/drop-import-gtk.patch
--- cmd2-0.7.7/debian/patches/drop-import-gtk.patch 1969-12-31 
19:00:00.0 -0500
+++ cmd2-0.7.7/debian/patches/drop-import-gtk.patch 2017-12-19 
16:47:30.0 -0500
@@ -0,0 +1,25 @@
+Description: Drop import of gtk now that pyperclip uses gi (GTK+3).
+Author: Corey Bryant 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1722553
+Origin: https://github.com/python-cmd2/cmd2/pull/242
+Forwarded: yes
+
+--- a/cmd2.py
 b/cmd2.py
+@@ -46,16 +46,6 @@
+ import pyparsing
+ import pyperclip
+ 
+-# On some systems, pyperclip will import gtk for its clipboard functionality.
+-# The following code is a workaround for gtk interfering with printing from a 
background
+-# thread while the CLI thread is blocking in raw_input() in Python 2 on Linux.
+-try:
+-# noinspection PyUnresolvedReferences
+-import gtk
+-gtk.set_interactive(0)
+-except ImportError:
+-pass
+-
+ # next(it) gets next item of iterator it. This is a replacement for calling 
it.next() in Python 2 and next(it) in Py3
+ from six import next
+ 
diff -Nru cmd2-0.7.7/debian/patches/series cmd2-0.7.7/debian/patches/series
--- cmd2-0.7.7/debian/patches/series2017-08-27 08:30:40.0 -0400
+++ cmd2-0.7.7/debian/patches/series2017-12-19 16:45:41.0 -0500
@@ -0,0 +1 @@
+drop-import-gtk.patch


Bug#884873: python-pyperclip: move to gtk+3 to avoid use of mutual exclusive gtk+2/gtk+3 modules

2017-12-20 Thread Corey Bryant
Package: python-pyperclip
Version: 1.5.32-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/move-to-gtk3.patch: Use GTK+3 instead of GTK+2 (LP: #1722553).

Thanks for considering the patch.


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

Kernel: Linux 4.13.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-pyperclip-1.5.32/debian/control 
python-pyperclip-1.5.32/debian/control
--- python-pyperclip-1.5.32/debian/control  2017-11-03 03:05:14.0 
-0400
+++ python-pyperclip-1.5.32/debian/control  2017-12-19 16:25:22.0 
-0500
@@ -13,7 +13,7 @@
 
 Package: python-pyperclip
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, xclip | xsel | 
python-gtk2 | python-qt4
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, xclip | xsel | 
python-gi | python-qt4
 Description: Cross-platform clipboard module for Python
  This module is a cross-platform Python module for copy and paste clipboard
  functions.
@@ -22,7 +22,7 @@
 
 Package: python3-pyperclip
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, xclip | xsel 
| python3-pyqt4
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, xclip | xsel 
| python3-gi | python3-pyqt4
 Description: Cross-platform clipboard module for Python3
  This module is a cross-platform Python3 module for copy and paste clipboard
  functions.
diff -Nru python-pyperclip-1.5.32/debian/patches/move-to-gtk3.patch 
python-pyperclip-1.5.32/debian/patches/move-to-gtk3.patch
--- python-pyperclip-1.5.32/debian/patches/move-to-gtk3.patch   1969-12-31 
19:00:00.0 -0500
+++ python-pyperclip-1.5.32/debian/patches/move-to-gtk3.patch   2017-12-19 
16:25:22.0 -0500
@@ -0,0 +1,97 @@
+Description: Switch from GTK+2 to GTK+3 to avoid import of mutually exclusive
+  modules that resulted in the following error:
+  AttributeError: When using gi.repository you must not import static modules 
like
+  "gobject". Please change all occurrences of "import gobject" to
+  "from gi.repository import GObject". See:
+  https://bugzilla.gnome.org/show_bug.cgi?id=709183
+Author: Corey Bryant 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1722553
+Origin: https://github.com/asweigart/pyperclip/pull/111
+Forwarded: yes
+
+--- a/pyperclip/__init__.py
 b/pyperclip/__init__.py
+@@ -20,12 +20,13 @@
+ sudo apt-get install xclip
+ sudo apt-get install xsel
+ 
+-Otherwise on Linux, you will need the gtk or PyQt5/PyQt4 modules installed.
++Otherwise on Linux, you will need the gi (GTK+ 3) or PyQt5/PyQt4 modules 
installed.
++gtk (GTK +2) is still supported as an older alternative to gi.
+ 
+ gtk and PyQt4 modules are not available for Python 3,
+ and this module does not work with PyGObject yet.
+ 
+-Note: There seem sto be a way to get gtk on Python 3, according to:
++Note: There seems to be a way to get gtk on Python 3, according to:
+ 
https://askubuntu.com/questions/697397/python3-is-not-supporting-gtk-module
+ 
+ Cygwin is currently not supported.
+@@ -104,11 +105,18 @@
+ # Setup for the LINUX platform:
+ if HAS_DISPLAY:
+ try:
+-import gtk  # check if gtk is installed
++import gi  # check if gi is installed (for GTK+ 3)
+ except ImportError:
+-pass # We want to fail fast for all non-ImportError exceptions.
++try:
++import gtk  # check if gtk is installed (fallback to GTK+ 2)
++except ImportError:
++pass # We want to fail fast for all non-ImportError 
exceptions.
++else:
++return init_gtk_clipboard()
+ else:
+-return init_gtk_clipboard()
++if gi.version_info[0] >= 3:
++return init_gi_clipboard()
++pass
+ 
+ if _executable_exists("xclip"):
+ return init_xclip_clipboard()
+@@ -161,6 +169,7 @@
+ clipboard_types = {'pbcopy': init_osx_pbcopy_clipboard,
+'pyobjc': init_osx_pyobjc_clipboard,
+'gtk': init_gtk_clipboard,
++   'gi': init_gi_clipboard,
+'qt': init_qt_clipboard, # TODO - split this into 
'qtpy', 'pyqt4', and 'pyqt5'
+'xclip': init_xclip_clipboard,
+'xsel': init_xsel_clipboard,
+--- a/pyperclip/clipboards.py
 b/pyperclip/clipboards.py
+@@ -57,7 +57,6 @@
+ import gtk
+ 
+ def copy_gtk(text):
+-global cb
+

Bug#884872: ITP: iem-plugin-suite -- IEM's spatialization suite

2017-12-20 Thread IOhannes m zmoelnig
Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig 

* Package name: iem-plugin-suite
  Version : 1.0.0
  Upstream Author : Daniel Rudrich 
* URL : https://plugins.iem.at
* License : GPL-3+
  Programming Lang: C++
  Description : IEM's spatialization suite

 The IEM Plug-in Suite is an audio plugin suite created at the Institute of
 Electronic Music and Acoustics (Graz, Austria).
 It features Higher-Order Ambisonic plug-ins (up to 7th order), among them a
 number of state of the art encoders, directional compressors, directivity
 shapers, delay and reverb effects and analysis tools.

The binary packages will include the plugins as Linux VST plugins and as
standalone applications.  
I intend to maintain this under the pkg-multimedia-maintainers umbrella.



Bug#884871: nfs-kernel-server: svcgssd starts anyways when "disabled" in /etc/default/nfs-kernel-server

2017-12-20 Thread Matt Weatherford
Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: important

Dear Maintainer,

First of all, thank you for all you do to support Debian


Heres my /etc/default/nfs-kernel-server  config file, it clearly "disables 
svcgssd" :


root@filer:/etc/default# vi nfs-kernel-server 
# Number of servers to start up
RPCNFSDCOUNT=8

# Runtime priority of server (see nice(1))
RPCNFSDPRIORITY=0

# Options for rpc.mountd.
# If you have a port-based firewall, you might want to set up
# a fixed port here using the --port option. For more information,
# see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS
# To disable NFSv4 on the server, specify '--no-nfs-version 4' here
#RPCMOUNTDOPTS="--manage-gids"

### TO DEBUG USE:

RPCMOUNTDOPTS="--manage-gids --debug all"



# Do you want to start the svcgssd daemon? It is only required for Kerberos
# exports. Valid alternatives are "yes" and "no"; the default is "no".
NEED_SVCGSSD=no

# Options for rpc.svcgssd.
#RPCSVCGSSDOPTS=""


RPCNFSDCOUNT="64  --no-nfs-version 3  --no-nfs-version 4"



~   
   
~   
   
~ 

But if I restart the nfs-server process, it errors out like this:


root@filer:/etc/default# 
root@filer:/etc/default# service nfs-server restart
Job for nfs-server.service failed because the control process exited with error 
code.
See "systemctl status nfs-server.service" and "journalctl -xe" for details.
root@filer:/etc/default# journalctl -xe
Dec 20 11:38:03 filer systemd[1]: Starting NFSv4 ID-name mapping service...
-- Subject: Unit nfs-idmapd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-idmapd.service has begun starting up.
Dec 20 11:38:03 filer systemd[1]: Starting RPC security service for NFS 
server...
-- Subject: Unit rpc-svcgssd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rpc-svcgssd.service has begun starting up.
Dec 20 11:38:03 filer systemd[1]: Started NFSv4 ID-name mapping service.
-- Subject: Unit nfs-idmapd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-idmapd.service has finished starting up.
-- 
-- The start-up result is done.
Dec 20 11:38:03 filer rpc.svcgssd[10651]: ERROR: GSS-API: error in 
gss_acquire_cred(): GSS_S_FAILURE (Unspecified GSS failure.  Minor code 
Dec 20 11:38:03 filer rpc.svcgssd[10651]: unable to obtain root (machine) 
credentials
Dec 20 11:38:03 filer rpc.svcgssd[10651]: do you have a keytab entry for 
nfs/@ in /etc/krb5.keytab?
Dec 20 11:38:03 filer systemd[1]: rpc-svcgssd.service: Control process exited, 
code=exited status=1
Dec 20 11:38:03 filer systemd[1]: Failed to start RPC security service for NFS 
server.
-- Subject: Unit rpc-svcgssd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rpc-svcgssd.service has failed.
-- 
-- The result is failed.
Dec 20 11:38:03 filer systemd[1]: rpc-svcgssd.service: Unit entered failed 
state.
Dec 20 11:38:03 filer systemd[1]: rpc-svcgssd.service: Failed with result 
'exit-code'.
Dec 20 11:38:03 filer rpc.mountd[10654]: Version 1.3.3 starting
Dec 20 11:38:03 filer systemd[1]: Started NFS Mount Daemon.
-- Subject: Unit nfs-mountd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-mountd.service has finished starting up.



I am trying to use nfs 4.1 (not 4) with no kerberos, but cant figure out how to 
start it up.
If I take out the " --no-nfs-version 4"  then nfs-server starts up ok, but I 
have version 4 enabled where I only want version 4.1 and higher working:
root@filer:~# cat /proc/fs/nfsd/versions
-2 -3 +4 +4.1 +4.2
root@filer:~# 



-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
133   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
1002273   udp   2049
1000241   udp  51907  status
1000241   tcp  59263  status
134   tcp   2049  nfs
134   udp   2049  nfs
1000211   udp  38357  nlockmgr
1000213   udp  38357  nlockmgr
1000214   udp  38357  nlockmgr
1000211   tcp  36441  nlockmgr
1000213   tcp  36441  nlockmgr
1000214   tcp  36441  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --debug all"
NEED_SVCGSSD=no

Bug#815037: firmware-iwlwifi: Bug also leads to kernel panic and freezes

2017-12-20 Thread Daniel M.
Bug message and freezes / panic is solved when I downgraded to stable.
So no HW problem.



Bug#884870: lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree

2017-12-20 Thread Christoph Berg
Re: Jeremy Bicha 2017-12-20 

> to
> Vcs-Git: https://anonscm.debian.org/git/pkg-webkit/webkit.git -b wk2/unstable

> I think the " -b BRANCHNAME" suffix should be considered valid syntax
> for Vcs-Git.

Fwiw, the -b syntax was not invented by vcswatch, it was in use in the
archive before I wrote the service. I can't find a place where it is
documented (I thought it was debcheckout(1), but it's not in there),
but the idea behind it is that you can you paste the Vcs-Git header
content to "git clone" and it will do the right thing.

(I'm still pondering how a syntax for "package is located in this
subdirectory" should look like, but as that's not supported by "git
clone", I couldn't think of anything yet that would at least look like
the -b syntax. There's a need for it, though.)

Christoph



Bug#884863: Support for Radeon R7 3rd generation (Merlin Falcon) in AMD A8-9600

2017-12-20 Thread Karsten
Hello Michel,

you found the heart of the problem!

Am 20.12.2017 um 18:18 schrieb Michel Dänzer:
> From the Xorg log file there, it looks like the drivers don't get the
> EDID from the monitor. Since you say it's a "VGA-TFT" monitor, but the
> drivers only detect a DisplayPort connection, are you using some kind of
> DisplayPort-to-other converter? Can you try connecting the monitor to an
> HDMI output instead?

No - there is no converter.
The mainboard supports 3 video outputs: VGA, DVI, HDMI
After i connected an additional DVI monitor with Full-HD resolution all was 
working perfect.
I got the 1920 resolution on the DVI and 1024 additional on the VGA monitor.

After the DVI Monitor was connected the compositor with OpenGL 2.0 was working 
too.
But it makes problems with only the VGA monitor connected. So a DVI monitor 
should be used.

So this can be classified as minor problem.
Hopefully other user will profit from this description.

Cheers
Karsten



Bug#873845: bug 873845

2017-12-20 Thread Mehturt
The regex in sshd-ddos.conf is:
^%(__prefix_line)sDid not receive identification string from \s*$
But the lines I see in auth.log are:
Did not receive identification string from A.B.C.D port 12345
So the regex need to be updated to something like:
...from .*$
m.


Bug#884870: lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree

2017-12-20 Thread Jeremy Bicha
Source: lintian
Version: 2.5.65

I changed webkit2gtk's Vcs-Git field from
Vcs-Git: https://anonscm.debian.org/git/pkg-webkit/webkit.git

to
Vcs-Git: https://anonscm.debian.org/git/pkg-webkit/webkit.git -b wk2/unstable

in order to satisfy
https://qa.debian.org/cgi-bin/vcswatch?package=webkit2gtk

which complained that it couldn't find the current debian/changelog in
HEAD. (Maybe it's time to change HEAD, but this bug is also a problem
for experimental and Stable Update branches.)

Now, I think (lintian's website is recovering from a typo) that this
now causes lintian to emit vcs-field-has-unexpected-spaces

I think the " -b BRANCHNAME" suffix should be considered valid syntax
for Vcs-Git.

Thanks,
Jeremy Bicha



Bug#884817: lintian: check for override_dh_clean target missing call to dh_clean

2017-12-20 Thread Chris Lamb
tags 884817 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=edd65158f2b8f02760cd2c5ef377b0e04188fb3f


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#884848: lintian: false positive for source-includes-file-in-files-excluded

2017-12-20 Thread Chris Lamb

Hi,

> lintian: false positive for source-includes-file-in-files-excluded

Indeed. The following patch *should* fix it IMHO:


  commit c807001cbbf101f74d227cde4482f535908e13a6
  Author: Chris Lamb 
  Date:   Wed Dec 20 18:17:11 2017 +
  
  collection/src-orig-index: Correct reference to generated filename.
  
   collection/src-orig-index | 6 +++---
   debian/changelog  | 3 +++
   2 files changed, 6 insertions(+), 3 deletions(-)
  
  commit 5c2a7611aaccc1ef835cca058ca1fd23abe7d1ed
  Author: Chris Lamb 
  Date:   Wed Dec 20 18:16:09 2017 +
  
  Use the list of files in the orig tarball rather than in the regular 
index to prevent false positives in the tag 
source-includes-file-in-files-excluded when a patch system adds files that have 
been removed. (Closes: #884848)
  
   checks/source-copyright.desc | 2 +-
   checks/source-copyright.pm   | 2 +-
   debian/changelog | 5 +
   3 files changed, 7 insertions(+), 2 deletions(-)


.. but it fails with:

warning: collect info file-info about package idlastro failed
warning: skipping check of source package idlastro
warning: collect info file-info about package gdl-astrolib failed
warning: skipping check of binary package gdl-astrolib
Can't 
readlink('/tmp/temp-lintian-lab-GwZNgZ4Df3/pool/i/idlastro/idlastro_2017.08.02+dfsg-1_source-all_changes/changes'):
 No such file or directory at 
/home/lamby/git/debian/lintian/lintian/checks/changes-file.pm line 192
internal error: cannot run changes-file check on package 
changes:idlastro/2017.08.02+dfsg-1/source_all
warning: skipping check of changes:idlastro/2017.08.02+dfsg-1/source_all

Presumably some kind of conflict between the two collection scripts.. Hm.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
From c807001cbbf101f74d227cde4482f535908e13a6 Mon Sep 17 00:00:00 2001
From: Chris Lamb 
Date: Wed, 20 Dec 2017 18:17:11 +
Subject: [PATCH 1/2] collection/src-orig-index: Correct reference to generated
 filename.

---
 collection/src-orig-index | 6 +++---
 debian/changelog  | 3 +++
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/collection/src-orig-index b/collection/src-orig-index
index 7799e1a2c..f4efcdd77 100755
--- a/collection/src-orig-index
+++ b/collection/src-orig-index
@@ -39,14 +39,14 @@ sub collect {
 my ($pkg, $type, $dir) = @_;
 my $info = Lintian::Collect->new($pkg, $type, $dir);
 
-if (-f "$dir/orig-index.gz") {
-unlink("$dir/orig-index.gz");
+if (-f "$dir/src-orig-index.gz") {
+unlink("$dir/src-orig-index.gz");
 }
 
 # Nothing to do for native packages where the two indices are
 # identical.
 if ($info->native) {
-link("$dir/index.gz", "$dir/orig-index.gz");
+link("$dir/index.gz", "$dir/src-orig-index.gz");
 return;
 }
 
diff --git a/debian/changelog b/debian/changelog
index b73da400d..7c91ad2b2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -19,6 +19,9 @@ lintian (2.5.66) UNRELEASED; urgency=medium
   (ie. "2017-11-30 < 2017-11-30"). Thanks to Andrea Bolognani
   e...@kiyuko.org> for the report.  (Closes: #884785)
 
+  * collection/src-orig-index:
++ [CL] Correct reference to generated filename.
+
   * data/debhelper/compat-level:
 + [MR] Bump the experimental debhelper compat level to 12.
   (Closes: #884678)
-- 
2.15.1

From 5c2a7611aaccc1ef835cca058ca1fd23abe7d1ed Mon Sep 17 00:00:00 2001
From: Chris Lamb 
Date: Wed, 20 Dec 2017 18:16:09 +
Subject: [PATCH 2/2] Use the list of files in the orig tarball rather than in
 the regular index to prevent false positives in the tag
 source-includes-file-in-files-excluded when a patch system adds files that
 have been removed. (Closes: #884848)

---
 checks/source-copyright.desc | 2 +-
 checks/source-copyright.pm   | 2 +-
 debian/changelog | 5 +
 3 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/checks/source-copyright.desc b/checks/source-copyright.desc
index 33666..8d47c5afb 100644
--- a/checks/source-copyright.desc
+++ b/checks/source-copyright.desc
@@ -2,7 +2,7 @@ Check-Script: source-copyright
 Author: Jakub Wilk 
 Abbrev: scpy
 Type: source
-Needs-Info: unpacked
+Needs-Info: unpacked, src-orig-index
 Info: This script checks if a source package conforms to policy
  with regard to copyright files.
  .
diff --git a/checks/source-copyright.pm b/checks/source-copyright.pm
index a5f66db47..352a391c0 100644
--- a/checks/source-copyright.pm
+++ b/checks/source-copyright.pm
@@ -615,7 +615,7 @@ sub get_all_files {
 
 sub check_files_excluded {
 my ($info, $excluded) = @_;
-my @files = get_all_files($info);
+my @files = grep { $_->is_file } $info->sorted_orig_index;
 my @wildcards = split /[\n\t ]+/, $excluded;
 for my $wildcard (@wildcards) {
 $wildcard =~ 

Bug#884867: Package libspreadsheet-readsxc-perl is ready

2017-12-20 Thread gregor herrmann
On Wed, 20 Dec 2017 19:44:08 +0200, Andrius Merkys wrote:

> I consider the package libspreadsheet-readsxc-perl ready to be uploaded
> to Debian. I have prepared it in
> https://anonscm.debian.org/git/pkg-perl/packages/libspreadsheet-readsxc-perl.git.
> I would require the assistance of DD to review and upload the package.

Thanks for your work, and welcome to your first package :)

As per our usual procedures I've reviewed it and added some minor
TODO items to its debian/changelog.

tl;dr: You would have saved some work by using dh-make-perl
--pkg-perl --cpan ... (from unstable) and starting from there :)


Feel free to ask any questions if something is unclear!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Tanita Tikaram: Trouble


signature.asc
Description: Digital Signature


Bug#884795: [Debian-med-packaging] Bug#884795: Bug#884795: patman: FTBFS on x32: final link failed: Nonrepresentable section

2017-12-20 Thread Aaron M. Ucko
Graham Inggs  writes:

>> Fixed in git:

Thanks!

> Any suggestions would be welcome.

I haven't looked at motif's build system, but I see that patman's
makefile doesn't honor CFLAGS or CXXFLAGS (which would be the normal
means of injecting relevant flags here), just CPPFLAGS (which is
supposed to be for the C PreProcessor).  It should properly consult both
CPPFLAGS and CXXFLAGS, and distribute its own flags across these two
variables as appropriate.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#884868: closed by "Adam D. Barratt" <a...@adam-barratt.org.uk> (Re: Bug#884868: unblock: fracplanet/0.5.1-2)

2017-12-20 Thread Innocent De Marchi
Hi Adam,

> This is an automatic notification regarding your Bug report
> which was filed against the release.debian.org package:
> 
> #884868: unblock: fracplanet/0.5.1-2
> 
> It has been closed by "Adam D. Barratt" .

Sorry for the mistake and and thanks for the information.

Regards!

I. De Marchi



Bug#884866: Package libspreadsheet-readsxc-perl is ready

2017-12-20 Thread Andrius Merkys
Dear all,

I consider the package libspreadsheet-readsxc-perl ready to be uploaded
to Debian. I have prepared it in
https://anonscm.debian.org/git/pkg-perl/packages/libspreadsheet-readsxc-perl.git.
I would require the assistance of DD to review and upload the package.

Best wishes,
Andrius

-- 
Andrius Merkys
PhD student at Vilnius University Institute of Biotechnology, Saulėtekio al. 7, 
room V325
LT-10257 Vilnius, Lithuania



Bug#884869: RM: fracplanet/0.5.1-2 unblock from unstable.

2017-12-20 Thread Innocent De Marchi
Package: ftp.debian.org
Severity: normal

Please remove old fracplanet version.

Migration from fracplanet to testing is blocked due to FTBFS on
armel/armhf [0].
This problem is derived from the different configuration in these two
architectures: on armel/armhf, Qt in Debian is configured to use OpenGL
ES instead of full OpenGL [1]. The bug #881943 is closed and now the bug
#882469 has been closed. This is why we have to removed the
old fracplanet 0.4.0-5 from armel/armhf to allow the migration of the
new version.

Thanks!

I. De Marchi



[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882469
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881943



Bug#884863: Support for Radeon R7 3rd generation (Merlin Falcon) in AMD A8-9600

2017-12-20 Thread Michel Dänzer
On 2017-12-20 04:50 PM, Karsten wrote:
> Package: x11-common
> Version: 1:7.7+19
> Severity: normal
> 
> Hello,
> 
> i have the problem that this GPU is not supported fully.
> http://www.cpu-world.com/CPUs/Bulldozer/AMD-A8-Series%20A8-9600.html
> 
> It is not possible to get more display resolution then 1024x768.
> 
> I discussed the problem already here:
> https://debianforum.de/forum/viewtopic.php?f=12=167981

I'm afraid you got some bad advice there; your GPU is only supported by
the amdgpu driver, not by radeon.

The best advice you got there was from rendegast, have you tried the
kernel and firmware from backports? If the problem persists with those,
please provide the full dmesg output and Xorg log file with them.

>From the Xorg log file there, it looks like the drivers don't get the
EDID from the monitor. Since you say it's a "VGA-TFT" monitor, but the
drivers only detect a DisplayPort connection, are you using some kind of
DisplayPort-to-other converter? Can you try connecting the monitor to an
HDMI output instead?


> It seems that AMD is not interested to support the newer GPU's in
> Linux anymore.

Speaking as somebody working for AMD on open source GPU driver support,
that's a demonstrably false statement. If you're interested, take a look
at articles this year on Phoronix and other sites about our drivers.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer



Bug#878221: linux-image-4.9.0-4-amd64: Screen flickers randomly with Radeon R9 270X since upgrade from 4.9.0-3 to 4.9.0-4

2017-12-20 Thread Vitus Jensen
Dell Latitude E6510
eDP-1 connected primary, internal display @1920x1080
HDMI-2 connected external Samsung 24" @1920x1200
00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 02)
Kernel driver in use: i915
Kernel modules: i915

* Screen flickers randomly when starting to click / type after a short break.
* Screen flickers everytime when mouse moves from one screen to another.
* Internal screen goes off when slowly moving from internal to external
  screen and stopping at the right spot.  Stays off until moving back to
  internal screen.

Downgrade from linux-image-4.9.0-4-amd64 to linux-image-4.9.0-3-amd64
fixes the issue.



Bug#884795: [Debian-med-packaging] Bug#884795: Bug#884795: patman: FTBFS on x32: final link failed: Nonrepresentable section

2017-12-20 Thread Graham Inggs
Hi Aaron

On 19 December 2017 at 21:30, Graham Inggs  wrote:
> Fixed in git:
> https://anonscm.debian.org/cgit/debian-med/patman.git/commit/?id=9e677022c3c9f3038a738efaa42fa8541fe3b8f6

So this worked, and a similar fix worked in motif [1].
I feel this is merely a workaround for the actual problem.

Should PIE be enabled by default for X32?
Should "DEB_BUILD_MAINT_OPTIONS=hardening=+all" not include PIE on
architectures where it is not enabled by default?

I have no idea where to start; X32 porters?  gcc maintainers?  dpkg maintainers?

Any suggestions would be welcome.

Regards
Graham


[1] 
https://anonscm.debian.org/cgit/collab-maint/motif.git/commit/?id=27d0d5d3a59c6ebf2fc99e04a687c73a45d9eb44



Bug#884867: Dependency of libspreadsheet-read-perl is being packaged for Debian

2017-12-20 Thread Andrius Merkys
block 884867 by 884866
thanks

Correct me if I am wrong, but I suppose that dependency on package
libspreadsheet-readsxc-perl which is not yet in the Debian could be
threated as being blocked by libspreadsheet-readsxc-perl ITP.

Best,
Andrius

-- 
Andrius Merkys
PhD student at Vilnius University Institute of Biotechnology, Saulėtekio al. 7, 
room V325
LT-10257 Vilnius, Lithuania



Bug#884867: libspreadsheet-read-perl: depends on Spreadsheet::ReadSXC, which is being packaged as libspreadsheet-readsxc-perl

2017-12-20 Thread Andrius Merkys
Package: libspreadsheet-read-perl
Version: 0.63-1
Severity: normal
Tags: newcomer

Dear Maintainer,

the package depends on Spreadsheet::ReadSXC, but the existence of
Spreadsheet::ReadSXC is not checked if parsing of ODS files is not
attempted.

I have prepared a Debian package for Spreadsheet::ReadSXC
(libspreadsheet-readsxc-perl). The bug could be fixed by adding
libspreadsheet-readsxc-perl to Debian and listing it as a dependency
of libspreadsheet-read-perl in its debian/control.

Best wishes,
Andrius Merkys

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

Kernel: Linux 4.10.0-40-generic (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 libspreadsheet-read-perl depends on:
ii  libdata-peek-perl   0.45-1
ii  libio-stringy-perl  2.110-5
ii  perl5.22.1-9ubuntu0.2

Versions of packages libspreadsheet-read-perl recommends:
ii  libspreadsheet-parseexcel-perl  0.6500-1
ii  libspreadsheet-xlsx-perl0.15-1
ii  libtext-csv-perl1.33-1
ii  libtext-csv-xs-perl 1.21-1

Versions of packages libspreadsheet-read-perl suggests:
pn  libtk-tablematrix-perl  
pn  perl-tk 

-- no debconf information



Bug#884868: unblock: fracplanet/0.5.1-2

2017-12-20 Thread Innocent De Marchi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package fracplanet.

Migration from fracplanet to testing is blocked due to FTBFS on
armel/armhf [0].
This problem is derived from the different configuration in these two
architectures: on armel/armhf, Qt in Debian is configured to use OpenGL
ES instead of full OpenGL [1]. The bug #881943 is closed and now the bug
#882469 has been closed. This is why we have to removed the
old fracplanet 0.4.0-5 from armel/armhf to allow the migration of the
new version.

Thanks!

I. De Marchi



[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882469
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881943



Bug#768073: [pkg-lxc-devel] LXD packaging

2017-12-20 Thread Clément Hermann
On 17/12/2017 21:39, Clément Hermann wrote:

> On 04/12/2017 21:40, Clément Hermann wrote:
>> So, I did some work on golang-gopkg-flosch-pongo2
>> 
>> (#839748), since I had no answer.
>> It should be fit for release but I would need someone (from the pkg-go
>> team) to review and upload.
>>
> 
> It's been completely reworked, hopefully it can be reviewed and uploaded
> soon.

It's in NEW right now.

>> I also started working on golang-gopkg-lxc-go-lxc.v2-dev (ITP: #883488).
>>
>> That's the last dependancy for LXD.
>>
> 
> And it's waiting for review and upload as well, in the pkg-go repository.
> 

I'm almost done, hopefully will have something ready for review this
weekend :)


>> So I started looking packaging LXD stable-2.0 as well, and asked to join
>> the pkg-lxc team (pending approval).
> 
> Unfortunately I had no response so far... Ping ? My Alioth username is
> nodens-guest.
> 

(Friendly) ping ?


Cheers,

\



Bug#884866: ITP: libspreadsheet-readsxc-perl -- Extract OpenOffice 1.x spreadsheet data

2017-12-20 Thread Andrius Merkys
Package: wnpp
Severity: wishlist
Owner: Andrius Merkys 

* Package name: libspreadsheet-readsxc-perl
  Version : 0.20
  Upstream Author : Christoph Terhechte 
* URL : https://metacpan.org/release/Spreadsheet-ReadSXC
* License : Perl
  Programming Lang: Perl
  Description : Extract OpenOffice 1.x spreadsheet data

The module parses OpenOffice 1.x spreadsheet files (.sxc) and returns Perl
data structure to access its values.

The package is a dependency of libspreadsheet-read-perl, but is silently
ignored if not used.

I plan to team-maintain the package in Debian Perl Group. I will need a
sponsor to upload the package once it is ready.



Bug#884865: vulkan: Please include glslang, spirv-tools, and spirv-headers in vulkan source package

2017-12-20 Thread Brett Johnson
Package: vulkan
Severity: normal

glslang and spirv-tools are needed for even the most trivial vulkan
development, so
they need to be packaged to make libvulkan-dev more useful.  However,
packaging
them independently is currently problematic because the upstream
repositories are not
versioned, and a given release of Vulkan contains a nasty hard dependency
on a
specific git commit ID from the glslang and spirv-* repositories.
Therefore, I'd like
to propose that these tools be packaged as part of the existing vulkan
source package.

Technically, this is easy, as the existing package already runs a
"get-external.sh" script
which fetches the appropriate git commit from the upstream repositories,
and builds the
tools in order to satisfy the dependency libVkLayer has on them.  So all
that's needed
is to copy the result of this build into new binary packages, rather than
throwing it away.
This also makes for a sane way to version the tools, by assigning them the
version of
the vulkan release they were built for.

I would suggest that new binary packages be created ("vulkan-glslang" and
"vulkan-spirv", for example), rather than simply including the binaries in
libvulkan-dev.
Although it's tempting/easier to simply include them in libvulkan-dev, it
turns out that
glslang and spirv-tools are not explicitly vulkan tools.  They can, in
theory, also be used
for OpenGL/CL, and someone may want to package them independently in the
future
(assuming the upstream versioning problems can be worked out), and this
could cause
a file conflict.  It would be better if that potential conflict wasn't
hidden inside the
libvulkan-dev package, but instead was inside a package which explicitly
names glslang
and spirv, and could make a clean "conflicts-with" target.

Thanks!
-- 
Brett Johnson 


Bug#839880: bug is still appears in 1.3.5d

2017-12-20 Thread Олег Мороз

I'm using 1.3.5d as sftp and has very similar behaviour:

cat proftpd.log

2017-12-20 19:37:24,213 sim-ng-data proftpd[15698] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-20 16:37:24,339 sim-ng-data proftpd[15698] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-20 16:37:24,339 sim-ng-data proftpd[15698] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-20 16:37:24,340 sim-ng-data proftpd[15698] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.




cat sftp.log

2017-12-20 19:37:24,213 mod_sftp/0.9.9[15698]: error using DisplayLogin 
'welcome.msg': No such file or directory
2017-12-20 19:37:24,214 mod_sftp/0.9.9[15698]: sent server version 
'SSH-2.0-mod_sftp/0.9.9'
2017-12-20 19:37:24,214 mod_sftp/0.9.9[15698]: received client version 
'SSH-2.0-FileZilla_3.29.0'
2017-12-20 19:37:24,214 mod_sftp/0.9.9[15698]: handling connection from 
SSH2 client 'FileZilla_3.29.0'
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session key exchange: 
ecdh-sha2-nistp256
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session server 
hostkey: ssh-rsa
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session 
client-to-server encryption: aes256-ctr
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session 
server-to-client encryption: aes256-ctr
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session 
client-to-server MAC: hmac-sha2-256
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session 
server-to-client MAC: hmac-sha2-256
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session 
client-to-server compression: none
2017-12-20 19:37:24,225 mod_sftp/0.9.9[15698]:  + Session 
server-to-client compression: none
2017-12-20 19:37:24,273 mod_sftp/0.9.9[15698]: sending acceptable 
userauth methods: keyboard-interactive,password

2017-12-20 19:37:24,335 mod_sftp/0.9.9[15698]: sending userauth banner
2017-12-20 19:37:24,336 mod_sftp/0.9.9[15698]: sending userauth banner
2017-12-20 16:37:24,339 mod_sftp/0.9.9[15698]: sending userauth success
2017-12-20 16:37:24,339 mod_sftp/0.9.9[15698]: user 'ftp' authenticated 
via 'keyboard-interactive' method



also looks like part of logging system working in UTC, but part is in 
local time




Bug#884835: [Pkg-mailman-hackers] Bug#884835: mailman3-suite: postinst fails if nginx is installed and apache2 is missing

2017-12-20 Thread Pierre-Elliott Bécue
Le mercredi 20 décembre 2017 à 10:17:36+0100, Philip Frei a écrit :
> Package: mailman3-suite
> Version: 0+20170523-6
> Severity: normal
> 
> Hi,
> 
> it's possible to use mailman3 with nginx. But without Apache2 installed
> the postinst will fail because there's no instruction how to proceed
> with nginx.

Hi,

Please provide a little more output to explain how the postinst will fail?
Did you chose "none" for the webserver to configure?

Give as much intel as you can.

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2


signature.asc
Description: PGP signature


Bug#884864: vlc: Convert/Save fails to copy a CD

2017-12-20 Thread Nick Manini
Package: src:vlc
Version: 3.0.0~rc2-1
Severity: normal

Hello,
vlc promises to be able to convert and save media.
It used to work on single files, but failed big time on multiple files, such
as the tracks of a CD.

Using vlc 2.2.8-2+b1, if one proceeds as described in
https://www.aimersoft.com/rip-dvd/vlc-rip-cd.html
to attempt to rip a CD, then after inserting the name of a "Destination
File" and clicking "Start", vlc attempts to overwrite repetedly all tracks
into this single file.

When proceeding to the next track vlc discovers that the file is there
already (!) and proposes to either overwrite it or skip the new track.
Eventually, one ends up with one track ripped only.
This should be corrected with the request to input a "Destination folder",
rather than a file name for output. vlc should then create in that folder
files with sensible names such as Track01.wav Track02.wav etc.
Comments to that aimersoft page report failure.


The current fresher vlc 3.0.0~rc2-1 has the further problem that, when one
clicks on "Start", it fails with the following error:

[55ed8e243b10] main playlist: playlist is empty
QXcbConnection: XCB error: 3 (BadWindow), sequence: 21090, resource id: 
9037074, major code: 40 (TranslateCoords), minor code: 0

and then simply starts playing the CD first track (!).  The selected file
remains empty.


This report refers to two likely unrelated bugs.
Correcting the newer QXcbConnection bug anyway would not make vlc any more
usable for ripping: please fix both problems.

Thanks in advance!

All the best,
Nick



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'stable'), (5, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages vlc depends on:
ii  vlc-bin  3.0.0~rc2-1
ii  vlc-l10n 3.0.0~rc2-1
ii  vlc-plugin-base  3.0.0~rc2-1
ii  vlc-plugin-qt3.0.0~rc2-1
ii  vlc-plugin-video-output  3.0.0~rc2-1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  3.0.0~rc2-1
pn  vlc-plugin-samba   
pn  vlc-plugin-skins2  
pn  vlc-plugin-video-splitter  
ii  vlc-plugin-visualization   2.2.8-2+b1

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.25-3
ii  libvlc5  3.0.0~rc2-1

Versions of packages libvlc5 depends on:
ii  libc62.25-3
ii  libvlccore9  3.0.0~rc2-1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.0~rc2-1

Versions of packages libvlccore8 depends on:
ii  libc62.25-3
ii  libdbus-1-3  1.12.2-1
ii  libidn11 1.33-2

Versions of packages libvlccore8 recommends:
ii  libproxy-tools  0.4.14-3

Versions of packages vlc-bin depends on:
ii  libc6   2.25-3
ii  libvlc-bin  3.0.0~rc2-1
ii  libvlc5 3.0.0~rc2-1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-19
ii  libarchive13 3.2.2-3.1
ii  libaribb24-0 1.0.3-1
ii  libasound2   1.1.3-5
ii  libass9  2:0.13.7-dmo1
ii  libavahi-client3 0.7-3
ii  libavahi-common3 0.7-3
ii  libavc1394-0 0.5.4-4+b1
ii  libavcodec57 7:3.4.1-1
ii  libavformat577:3.4.1-1
ii  libavutil55  7:3.4.1-1
ii  libbasicusageenvironment12:2017.07.18-dmo1
ii  libbluray2   2:1.0.1-dmo1
ii  libc62.25-3
ii  libcairo21.15.8-2
ii  libcddb2 1.3.2-5
ii  libchromaprint1  1.4.2-1
ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
ii  libdbus-1-3  1.12.2-1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.5-dmo2
ii  libdvbpsi10  1:1.3.1-dmo1
ii  libdvdnav4   5.0.3-3
ii  libdvdread4  5.0.3-2
ii  libebml4v5   1:1.3.5-dmo1
ii  libfaad2 2.8.6-1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-0.1
ii  libfribidi0  0.19.7-2
ii  libgcc1  1:7.2.0-17
ii  libgcrypt20  1.8.1-4
ii  libglib2.0-0 2.54.1-1
ii  libgnutls30  3.5.16-1
ii  libgpg-error01.27-5
ii  libgroupsock82:2017.07.18-dmo1
ii  libharfbuzz0b1.6.2-1
ii  

Bug#884863: Support for Radeon R7 3rd generation (Merlin Falcon) in AMD A8-9600

2017-12-20 Thread Karsten
Package: x11-common
Version: 1:7.7+19
Severity: normal

Hello,

i have the problem that this GPU is not supported fully.
http://www.cpu-world.com/CPUs/Bulldozer/AMD-A8-Series%20A8-9600.html

It is not possible to get more display resolution then 1024x768.

I discussed the problem already here:
https://debianforum.de/forum/viewtopic.php?f=12=167981

It seems that AMD is not interested to support the newer GPU's in Linux anymore.
The last Crimson / Catalyst only support up to XServer 1.1:
http://support.amd.com/en-us/download/desktop?os=Linux%20x86_64#
___
error: Detected X Server version 'XServer 1.19.2_64a' is not supported.
Supported versions are X.Org 6.9 or later, up to XServer 1.10 
(default:v2:x86_64:lib:XServer 1.19.2_64a:none:4.9.0-4-amd64:)
Installation will not proceed.
___


There is an package with an Kernel for Ubuntu at AMD:
http://support.amd.com/de-de/download/embedded?os=Linux_tmp%20x86_64
But it seems not to contain an driver i can use.

Any ideas to solve the problem?

I have written to the support of AMD.
If there will come any useful information i will report it here.

Best regards
Karsten



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

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

Versions of packages x11-common depends on:
ii  lsb-base  9.20161125

x11-common recommends no packages.

x11-common suggests no packages.

-- no debconf information



Bug#884862: gimp: CVE-2017-17786: OOB read in TGA

2017-12-20 Thread Salvatore Bonaccorso
Source: gimp
Version: 2.8.14-1
Severity: normal
Tags: security upstream
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=739134

Hi,

the following vulnerability was published for gimp.

CVE-2017-17786[0]:
| In GIMP 2.8.22, there is a heap-based buffer over-read in ReadImage in
| plug-ins/common/file-tga.c (related to bgr2rgb.part.1) via an
| unexpected bits-per-pixel value for an RGBA image.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-17786
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17786
[1] https://bugzilla.gnome.org/show_bug.cgi?id=739134

Regards,
Salvatore



Bug#884807: getmail: does not ship /usr/bin/getmail

2017-12-20 Thread Daniel Kahn Gillmor
Hi Osamu--

thanks very much for your packaging work for getmail!

On Thu 2017-12-21 00:48:44 +0900, Osamu Aoki wrote:
> On Tue, Dec 19, 2017 at 06:36:15PM -0500, Daniel Kahn Gillmor wrote:
>> On Tue 2017-12-19 16:47:01 -0500, Daniel Kahn Gillmor wrote:
>> > somehow /usr/bin/getmail got dropped from the getmail 5.5-1 packaging :/
>> 
>> I've pushed some changes to the master branch of
>> https://anonscm.debian.org/git/collab-maint/getmail.git that resolve
>> this matter for me.
>> 
>> they also do a little bit of packaging cleanup.  I hope they're useful!
>
> Thanks. I realized your change just before upload.  Good.
> Yes this cleans my rough edges.
>
> I had some changes locally with a bit different style too ;-) I have
> debian/rules with:
>
>   # Always use debian/getmail as destination (not debian/tmp)
>   # even when dummy getmail4 package exists
>   override_dh_auto_install:
>   dh_auto_install --destdir debian/getmail

ok, it looks like i tend to prefer the more declarative style, and you
prefer the imperative style.  You're the maintainer, so your decision
goes :)

Just so you know why i prefer the declarative style, though:

i think with your imperative changes to the debian/rules makefile, a new
upstreamversion that injects something funky into the filesystem will
just have it happen (possibly without the maintainer noticing).

With the declarative approach i'd outlined (that is, listing everything
explicitly in debian/getmail.{docs,install,manpages}, and including
dh_missing --fail-missing), the packager has to actively acknowledge
changes to the installed filesystem, which i like as a double-check
during packaging itself.

> So when we drop getmail4 transition package, migration needs only
> dropping it in the debian/control field.

I think that would happen either way :)

anyway, just thought i'd explain my reasoning.  I'm happy to follow your
lead on the package.

All the best,

 --dkg



Bug#884861: ITP: node-temp-write -- Write string/buffer/stream to a temporary file

2017-12-20 Thread Hilko Bengen
Package: wnpp
Owner: Hilko Bengen 
Severity: wishlist
Control: block 884840 by -1

* Package name: node-temp-write
  Version : 3.3.0
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/temp-write#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Write string/buffer/stream to a temporary file

This package is needed for gulp-closure-compiler which is needed building a new 
version of GRR.



Bug#860652: snap-aligner: FTBFS on i386: SNAPLib/SortedDataWriter.cpp:338:70: error: no matching function for call to 'max(long unsigned int, _int64)'

2017-12-20 Thread IOhannes m zmölnig
On Wed, 19 Apr 2017 10:51:40 +0200 Andreas Tille  wrote:
> 
> Anyway.  I try to tackle the first one which leaves me clueless.  Any
> idea why max() and min() are unknown now but were not before?

as to "why" i cannot say, but it's probably related to an update in g++
which comes with a different implementation of max() and min().

however, the fix is to make sure that the right instantiation of the
template is being called.
e.g. replacing "max(1UL << 17, bufferSpace / blocks.size())" with
"std::max(static_cast(1UL<<17), bufferSpace / blocks.size())"


fgamsdr
IOhannes



signature.asc
Description: OpenPGP digital signature


Bug#884860: fonts-fantasque-sans: some glyphs (H M N) are lower than the rest

2017-12-20 Thread Adam Borowski
Package: fonts-fantasque-sans
Version: 1.7.2~alpha.3~dfsg-1
Severity: normal

Hi!
In the new version, H, M and N (and possibly other less obvious ones, or
outside ASCII) are shorter than their neighbours.  Screenshot of
xfce4-terminal (GTK3's libvte) attached.

On my system, I have copied NoLoopK over other variants, as a crude
workaround for #884592 -- but even if it differs between variants, at least
NoLoopK exhitibts this bug.


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

Kernel: Linux 4.15.0-rc4-debug-00058-gde4caf464ca0 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/LargeLineHeight/OTF/FantasqueSansMono-Bold.otf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/LargeLineHeight/OTF/FantasqueSansMono-BoldItalic.otf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/LargeLineHeight/OTF/FantasqueSansMono-Italic.otf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/LargeLineHeight/OTF/FantasqueSansMono-Regular.otf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/Normal/OTF/FantasqueSansMono-Bold.otf 
(from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/Normal/OTF/FantasqueSansMono-BoldItalic.otf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/Normal/OTF/FantasqueSansMono-Italic.otf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/opentype/fantasque-sans/Normal/OTF/FantasqueSansMono-Regular.otf
 (from fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/svg/fantasque-sans/FantasqueSansMono-Bold.svg (from 
fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/svg/fantasque-sans/FantasqueSansMono-BoldItalic.svg (from 
fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/svg/fantasque-sans/FantasqueSansMono-Italic.svg (from 
fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/svg/fantasque-sans/FantasqueSansMono-Regular.svg (from 
fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/LargeLineHeight/TTF/FantasqueSansMono-Bold.ttf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/LargeLineHeight/TTF/FantasqueSansMono-BoldItalic.ttf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/LargeLineHeight/TTF/FantasqueSansMono-Italic.ttf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/LargeLineHeight/TTF/FantasqueSansMono-Regular.ttf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/Normal/TTF/FantasqueSansMono-Bold.ttf 
(from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/Normal/TTF/FantasqueSansMono-BoldItalic.ttf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/Normal/TTF/FantasqueSansMono-Italic.ttf
 (from fonts-fantasque-sans package)
debsums: changed file 
/usr/share/fonts/truetype/fantasque-sans/Normal/TTF/FantasqueSansMono-Regular.ttf
 (from fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/woff/fantasque-sans/FantasqueSansMono-Bold.woff (from 
fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/woff/fantasque-sans/FantasqueSansMono-BoldItalic.woff (from 
fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/woff/fantasque-sans/FantasqueSansMono-Italic.woff (from 
fonts-fantasque-sans package)
debsums: missing file 
/usr/share/fonts/woff/fantasque-sans/FantasqueSansMono-Regular.woff (from 
fonts-fantasque-sans package)


Bug#884436: xdg-open: wrongly handled file/URL in LXQt

2017-12-20 Thread Palo Kisa
On Wed, Dec 20, 2017 at 4:27 PM, Emilio Pozuelo Monfort 
wrote:
>
> "There's a patch for this problem at
> https://bugs.freedesktop.org/show_bug.cgi?id=81674, yet I don't think
> it's a
> correct fix"
>
> Don't expect busy maintainers to go read all your links and guess which
> patches
> are correct and which ones aren't. Instead, you should *attach* the
> appropriate
> patch, in git format, to the bug report, and clearly state the reasons why
> the
> patch should be accepted.
>

OK, submitted the patch to upstream. Yet I still don't think there will be
any activity soon (the bug was reported in 2017-07).

palo


Bug#884807: getmail: does not ship /usr/bin/getmail

2017-12-20 Thread Osamu Aoki
On Tue, Dec 19, 2017 at 06:36:15PM -0500, Daniel Kahn Gillmor wrote:
> On Tue 2017-12-19 16:47:01 -0500, Daniel Kahn Gillmor wrote:
> > somehow /usr/bin/getmail got dropped from the getmail 5.5-1 packaging :/
> 
> I've pushed some changes to the master branch of
> https://anonscm.debian.org/git/collab-maint/getmail.git that resolve
> this matter for me.
> 
> they also do a little bit of packaging cleanup.  I hope they're useful!

Thanks. I realized your change just before upload.  Good.
Yes this cleans my rough edges.

I had some changes locally with a bit different style too ;-) I have
debian/rules with:

  # Always use debian/getmail as destination (not debian/tmp)
  # even when dummy getmail4 package exists
  override_dh_auto_install:
  dh_auto_install --destdir debian/getmail

So when we drop getmail4 transition package, migration needs only
dropping it in the debian/control field.

So I made a bit more changes to simplify packaging.

Osamu



Bug#867749: I will adopt this package

2017-12-20 Thread Chris West
Control: retitle -1 ITA: keychain -- key manager for OpenSSH

I intend to adopt this package. I'm a DM and have uploaded previously,
but don't have permission to upload this package. I also don't have
access to push to the original collab-maint repo, so I've temporarily
mirrored it:
https://github.com/FauxFaux/keychain-deb

Chris.



Bug#884859: phonon-backend-vlc: FTBFS against vlc 3.0.0~rc2

2017-12-20 Thread Sebastian Ramacher
Source: phonon-backend-vlc
Version: 0.9.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid buster

phonon-backend-vlc failed to build while rebuilding reverse dependencies of
libvlccore:
| In file included from /<>/src/backend.cpp:45:0:
| /usr/include/vlc/plugins/vlc_common.h: At global scope:
| /<>/src/utils/libvlc.h:33:24: error: invalid use of 
qualified-name 'LibVLC::self'
|  #define libvlc LibVLC::self->vlc()

Full log is available at
https://buildd.debian.org/status/fetch.php?pkg=phonon-backend-vlc=amd64=0.9.0-2%2Bb1=1513777867=0

Please upload 0.9.1 to unstable.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#802026: bug still present with 2.1?

2017-12-20 Thread Martin-Éric Racine
2017-12-20 14:43 GMT+02:00 David Bremner :
>
> Control: tag -1 moreinfo
>
> Can you confirm this problem is still present in 2.1-*?

nullmailer.  Right. Had to look up the bug report to even know what
you were asking about.

Seems to work fine now.  Let's close this.

Cheers!
Martin-Éric



Bug#884858: mutt: q and $ fail with: rename: No such file or directory (errno = 2)

2017-12-20 Thread Adam Borowski
Package: mutt
Version: 1.7.2-1
Severity: normal

Hi!
Sometimes, quite rarely, operations that would commit operations on a
directory (such as q or $) fail with:
rename: No such file or directory (errno = 2)
with no way to save changes.  This results in doubled mails that were moved
elsewhere, restoration of deleted mails and similar loss of status updates.

I use Maildir; there's also a dovecot running on the server with Thunderbird
connected to it over IMAP, although it hasn't been interacted with in any
way (I use it as a glorified biff, and sometimes to handle broken HTML mails
from a business critter).

Attached strace says:
write(1, "\r\33[59dWriting /home/kilobyte/Mai"..., 39) = 39
stat("/home/kilobyte/Maildir/new", {st_mode=S_IFDIR|0700, st_size=0, ...}) = 0
stat("/home/kilobyte/Maildir/cur", {st_mode=S_IFDIR|0700, st_size=41524, ...}) 
= 0
lstat("/home", {st_mode=S_IFDIR|0755, st_size=68, ...}) = 0
lstat("/home/kilobyte", {st_mode=S_IFDIR|0755, st_size=2568, ...}) = 0
lstat("/home/kilobyte/Maildir", {st_mode=S_IFDIR|0700, st_size=1914, ...}) = 0
write(1, "\r\33[37m\33[40mWriting /home/kilobyt"..., 69) = 69
rename("/home/kilobyte/Maildir/new/1513779272.2794_0.tartarus", 
"/home/kilobyte/Maildir/cur/1513779272.2794_0.tartarus:2,") = -1 ENOENT (No 
such file or directory)
write(1, "\rrename: No such file or directo"..., 46) = 46

As Maildir is designed to allow concurrent access, changes from other
processes (such as dovecot here, another instance of mutt, etc) are
expected.  Thus, it's not reasonable to make the user lose any unrelated
modifications to other mails.


Meow!
-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages mutt depends on:
ii  libassuan02.4.3-2
ii  libc6 2.24-11+deb9u1
ii  libcomerr21.43.4-2
ii  libgnutls30   3.5.8-5+deb9u3
ii  libgpg-error0 1.26-2
ii  libgpgme111.8.0-3+b2
ii  libgssapi-krb5-2  1.15-1+deb9u1
ii  libidn11  1.33-1
ii  libk5crypto3  1.15-1+deb9u1
ii  libkrb5-3 1.15-1+deb9u1
ii  libncursesw5  6.0+20161126-1+deb9u1
ii  libnotmuch4   0.23.7-3
ii  libsasl2-22.1.27~101-g0780600+dfsg-3
ii  libtinfo5 6.0+20161126-1+deb9u1
ii  libtokyocabinet9  1.4.48-11+b1

Versions of packages mutt recommends:
ii  libsasl2-modules  2.1.27~101-g0780600+dfsg-3
ii  locales   2.24-11+deb9u1
ii  mime-support  3.60

Versions of packages mutt suggests:
pn  aspell | ispell
ii  ca-certificates20161130+nmu1
ii  exim4-daemon-heavy [mail-transport-agent]  4.89-2+deb9u2
ii  gnupg  2.1.18-8~deb9u1
pn  mixmaster  
ii  openssl1.1.0f-3+deb9u1
pn  urlview

Versions of packages mutt is related to:
ii  mutt  1.7.2-1

-- no debconf information



  1   2   >