Bug#832069: nfstrace: FTBFS on sparc64 and x32: most tests crash

[Steve Langasek]

Package: nfstrace
Version: 0.4.2-3
Followup-For: Bug #832069
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Hi Andrew,

This bug is also reproducible on armhf in some kernel configurations, so the
problem was reproduced in Ubuntu and I've prepared a patch to fix this as
well.  Please find attached a fix for the unaligned memory access problem.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru nfstrace-0.4.2/debian/patches/no-unaligned-access.patch nfstrace-0.4.2/debian/patches/no-unaligned-access.patch
--- nfstrace-0.4.2/debian/patches/no-unaligned-access.patch	1969-12-31 16:00:00.0 -0800
+++ nfstrace-0.4.2/debian/patches/no-unaligned-access.patch	2016-10-05 20:56:19.0 -0700
@@ -0,0 +1,27 @@
+Author: Steve Langasek 
+Description: Fix unaligned access in buffer copies
+ There's a TODO in the source about fixing alignment of the address being
+ copied.  This unaligned access is a problem on armhf with some kernel
+ configurations, and is generally slower even on other architectures due
+ to the fixups.  Just use memcpy instead which is bound to do the right
+ thing.
+
+Index: nfstrace-0.4.2/src/filtration/sessions_hash.h
+===
+--- nfstrace-0.4.2.orig/src/filtration/sessions_hash.h
 nfstrace-0.4.2/src/filtration/sessions_hash.h
+@@ -105,12 +105,8 @@
+ 
+ static inline void copy_ipv6(uint32_t dst[4], const uint8_t src[16])
+ {
+-// TODO:: fix alignment of src!
+-const uint32_t* s { reinterpret_cast(src) };
+-dst[0] = s[0];
+-dst[1] = s[1];
+-dst[2] = s[2];
+-dst[3] = s[3];
++uint8_t* d { reinterpret_cast(dst) };
++memcpy(d, src, sizeof(uint32_t) * 4);
+ }
+ 
+ struct IPv6PortsKeyHash
diff -Nru nfstrace-0.4.2/debian/patches/series nfstrace-0.4.2/debian/patches/series
--- nfstrace-0.4.2/debian/patches/series	2016-10-04 02:53:11.0 -0700
+++ nfstrace-0.4.2/debian/patches/series	2016-10-18 22:52:19.0 -0700
@@ -1,2 +1,3 @@
 reproducible_build.patch
 gcc6-ftbfs.patch
+no-unaligned-access.patch

Bug#841049: [debian-mysql] Bug#841049: Security fixes from the October 2016 CPU

[Lars Tangvald]

The following CVEs are noted as fixed since 5.6.30:
CVE-2016-3492 CVE-2016-5507 CVE-2016-5584 CVE-2016-5609
CVE-2016-5612 CVE-2016-5616 CVE-2016-5617 CVE-2016-5626
CVE-2016-5627 CVE-2016-5629 CVE-2016-5630 CVE-2016-6304
CVE-2016-6662 CVE-2016-7440 CVE-2016-8283 CVE-2016-8284

--
Lars

On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:

Source: mysql-5.6
Version: 5.6.30-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on 
Tuesday, October 18. According to the pre-release announcement [1], it 
will contain information about CVEs fixed in MySQL 5.6.34.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html


___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#841265: transition: cfitsio

[Aurelien Jarno]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

The cfitsio library changed its ABI in the latest release version.
The new version, including the package rename from libcfitsio4 to
libcfitsio5 is available in experimental. It has been built successfully
on all official architecture and most ports architectures.

The transition involves 37 packages, you can find the list on the
transition tracker in the auto-cfitsio entry. I have been able to
successfully rebuild all of them on amd64, so I don't expect any
issue.

Thanks for considering.


Ben file:

title = "cfitsio";
is_affected = .depends ~ "libcfitsio4" | .depends ~ "libcfitsio5";
is_good = .depends ~ "libcfitsio5";
is_bad = .depends ~ "libcfitsio4";


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

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

Bug#841253: libreoffice-base-drivers: should no longer recommend libreoffice-sdbc-firebird, which is no longer built

[Rene Engelhard]

On Wed, Oct 19, 2016 at 02:38:54AM +0200, Vincent Lefevre wrote:
> The package libreoffice-sdbc-firebird is no longer built.
> So, libreoffice-base-drivers should no longer recommend it

Yeah, didn't do that because it'll be back in 5.3 anyways.

> (which can partially block upgrades due to the broken
> Recommends).

Don't buy that. How do unavailable Recommends: block upgrades?

>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
> 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')

Maybe in broken mixes like this, but...

Regards,

Rene

Bug#841198: conky-all: please enable PulseAudio

[Vincent Cheng]

Control: tag -1 + pending

Hi Kevin,

On Tue, Oct 18, 2016 at 6:06 AM, Kevin Velghe  wrote:
> Please build conky-all, and maybe some other builds, with PulseAudio
> support enabled, which has been added in 1.10.3.

Thanks for the patch; I've committed it to svn and will be fixed in
the next upload.

Regards,
Vincent

Bug#730670: Unable to build

[Andreas Tille]

Hi Ghislain,

when tryining to build I get:

debian-science/git/packages/python-cartopy(debian/master) $ gbp-build 
--git-debian-branch=debian/master
Make sure we use sid config
gbp:info: Orig tarball 'python-cartopy_0.14.2.orig.tar.gz' not found at 
'../tarballs/'
pristine-tar: successfully generated 
/home/tillea/debian-maintain/alioth/debian-science/git/packages/build-area/python-cartopy_0.14.2.orig.tar.gz
gbp:info: Exporting 'WC' to 
'/home/tillea/debian-maintain/alioth/debian-science/git/packages/build-area/python-cartopy-tmp'
gbp:info: Moving 
'/home/tillea/debian-maintain/alioth/debian-science/git/packages/build-area/python-cartopy-tmp'
 to 
'/home/tillea/debian-maintain/alioth/debian-science/git/packages/build-area/python-cartopy-0.14.2'
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: Unmet build dependencies: cython3 libgeos-dev libproj-dev 
(>= 4.9.0) python-pyshp python-shapely (>= 1.5.6) python3-pyshp python3-shapely 
(>= 1.5.6)
W: Unmet build-dependency in source
dpkg-buildpackage: source package python-cartopy
dpkg-buildpackage: source version 0.14.2-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Ghislain Antony Vaillant 

 dpkg-source -i.git -I.git --before-build python-cartopy-0.14.2
 fakeroot debian/rules clean
dh clean --parallel --with python2,python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py clean 
setup.py:174: UserWarning: Unable to determine GEOS version. Ensure you have 
3.3.3 or later installed, or installation may fail.
  '.'.join(str(v) for v in GEOS_MIN_VERSION), ))
Proj4 version 4.8.0 is installed, but cartopy requires at least version 4.9.0.
E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 returned exit code 13
debian/rules:17: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
gbp:error: '~/bin/git-pbuilder ' failed: it exited with 2



BTW, if you are using some Git layout diverging from Debian Science
policy it would help if you use debian/gbp.conf.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#841241: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#841241: RFS: quark-sphinx-theme/0.4.0-1 [RC])

[Felix Krull]

>nice work, sponsored!

Great, thanks!

>

Bug#841264: cimg: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Source: cimg
Version: 1.6.5+dfsg-1
Severity: important
Justification: fails to build from source
Tags: patch

Dear Maintainer,

I am scheduled to transition of opencv.
This package is target to transition. I tested build with opencv 3.1.
As a result, this FTBFS with opencv 3.1.
Cause is that libopencv_imageio library is not specified at the time
of the library of the link.

I attached patch that revice this problem.
Could you check this patch and apply?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
Description: Fix build with Opencv 3.1

-

/usr/bin/ld: /tmp/ccuYcVc5.o: undefined reference to symbol 'cvWriteFrame'
//usr/lib/x86_64-linux-gnu/libopencv_videoio.so.3.1: error adding symbols: DSO
//missing from command line
collect2: error: ld returned 1 exit status
Makefile:248: recipe for target 'CImg_demo' failed
-

Author: Nobuhiro Iwamatsu 
Forwarded: no
Last-Update: 2016-10-17

--- cimg-1.6.5+dfsg.orig/examples/Makefile
+++ cimg-1.6.5+dfsg/examples/Makefile
@@ -142,7 +142,7 @@ endif
 
 # Flags to enable OpenCV support.
 CIMG_OPENCV_CFLAGS = -Dcimg_use_opencv -I/usr/include/opencv
-CIMG_OPENCV_LIBS = -lopencv_core -lopencv_highgui
+CIMG_OPENCV_LIBS = -lopencv_core -lopencv_highgui -lopencv_videoio
 #CIMG_OPENCV_LIBS = -lcv -lhighgui#-> Use this for OpenCV < 2.2.0
 
 # Flags used to disable display capablities of CImg


cimg_1.6.5+dfsg-1_amd64.build
Description: Binary data

Bug#841263: cimg: Please update Build-Depends

[Nobuhiro Iwamatsu]

Source: cimg
Version: 1.6.5+dfsg-1
Severity: important
Justification: fails to build from source
Tags: patch

Dear Maintainer,

I am scheduled to transition of opencv.
This package is target to transition. I tested build with opencv 3.1.
As a result, this FTBFS with opencv 3.1.

Because from opencv 3.1, libcv-dev and libhighgui-dev are removed,
we must specify the libopencv-dev instead.

Could you use libopencv-dev instead of libcv-dev and libhighgui-dev?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
diff --git a/debian/control b/debian/control
index abfb75d..7f40a81 100644
--- a/debian/control
+++ b/debian/control
@@ -10,8 +10,7 @@ Build-Depends-Indep: doxygen,
  libmagick++-dev,
  libfftw3-dev | fftw3-dev,
  libgimp2.0-dev,
- libcv-dev,
- libhighgui-dev,
+ libopencv-dev,
  libminc-dev,
  libtiff5-dev,
  libtiffxx5,

Bug#841262: erlang-lager: New upstream released (version 3.2.4)

[Nobuhiro Iwamatsu]

Package: erlang-lager
Version: 3.2.1-2
Severity: wishlist

Dear Maintainer,

erlang-lager released new version (3.2.4).
 https://github.com/basho/lager/releases/tag/3.2.4
Could you update to new versio?

Best regards,
  Nobuhiro

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

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

Versions of packages erlang-lager depends on:
ii  erlang-base [erlang-abi-17.0]  1:19.1.4+dfsg-1
ii  erlang-goldrush0.1.9-2

erlang-lager recommends no packages.

erlang-lager suggests no packages.

-- no debconf information

Bug#840849: [pkg-gnupg-maint] Bug#840849: gnupg2: pubkeyring and secretkey unusable

[Daniel Kahn Gillmor]

On Tue 2016-10-18 13:07:12 -0400, Mechtilde wrote:

> thanks for your help at IRC to solve the problem with my secret key.
>
> I still have problems with my public keyring. There aren't the
> information of trust.

i'm not sure specifically what you mean by "information of trust" -- do
you mean validity of user ids?  or knowledge of which keys are
"ultimately" or "fully" or "marginally" trusted as introducers (this is
known as "ownertrust")?

if you run "gpg --check-trustdb" it will show you how many keys have
certain ownertrust levels.  For example:

gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  19  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  19  signed:  58  trust: 18-, 0q, 0n, 0m, 0f, 0u

means that there is one key with ultimate ownertrust which has signed 19
keys, and no other keys have any ownertrust.

Do you recall having assigned ownertrust in the past to any keys?  how
many secret keys do you have that are your own?  Those keys should have
"ultimate" ownertrust.

> I only see the Name and E-Mail addresses from the mails I get since
> last Friday.

This sounds mail user agent specific to me; it seems that you're using
thunderbird (with enigmail?), but i'm not sure what it means to "only see
the Name and E-Mail addresses" -- can you clarify?

> What is the best solution to recover? Should I copy the file "trustdb"
> from the machine with Debian Stable?

if you have an older copy of your ~/.gnupg/ on a machine that has gpg1,
you should try using "gpg1 --homedir /path/to/.gnupg.backup
--export-ownertrust" and comparing its output with "gpg2
--export-ownertrust" (which looks at the current ~/.gnupg).

if they differ, you might try sending the old ownertrust into stdin of
"gpg2 --import-ownertrust" and seeing whether that resolves the issue.

the ownertrust should *not* have been cleared during the upgrade, but
maybe it somehow was?

  --dkg


signature.asc
Description: PGP signature

Bug#841261: ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard

[Paul Wise]

Package: ulogd2
Version: 2.0.4-2+deb8u1
Severity: important
X-Debbugs-CC: debian-ad...@lists.debian.org
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

On Debian's new arm64 nodes (acker and aagaard) ulogd2 always crashes
with SIGSEGV some time after startup. This does not happen on our other
arm64 nodes (asachi, arm-arm-03, arm-arm-04). Backtrace below:

pabs@acker:~$ sudo gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 
'thread apply all bt full' --args /usr/sbin/ulogd -v --uid ulog --pidfile 
/run/ulog/ulogd.pid
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
_interp_iphdr (pi=0x5557ab40, len=0) at ulogd_raw2packet_BASE.c:718
718 ulogd_raw2packet_BASE.c: No such file or directory.
#0  _interp_iphdr (pi=0x5557ab40, len=0) at ulogd_raw2packet_BASE.c:718
#1  0x9e38 in ulogd_propagate_results (pi=0x55578640, 
pi@entry=0x0) at ulogd.c:518
#2  0x7fffb7da31ac in interp_packet (ldata=0x7120, pf_family=68 
'D', upi=0x0) at ulogd_inppkt_NFLOG.c:400
#3  msg_cb (gh=, nfmsg=0x7fffb7bf0020, nfa=0x7120, 
data=0x0) at ulogd_inppkt_NFLOG.c:483
#4  0x7fffb7d8e3f4 in __nflog_rcv_pkt (nlh=, nfa=, data=) at libnetfilter_log.c:162
#5  0x7fffb7d79a88 in __nfnl_handle_msg (len=124, nlh=0x7fffb7bf0010, 
h=0x5557a210) at libnfnetlink.c:1236
#6  nfnl_handle_packet (h=0x5557a210, buf=0x7fffb7bf0010 "|", 
len=len@entry=124) at libnfnetlink.c:1256
#7  0x7fffb7d8e5f0 in nflog_handle_packet (h=, 
buf=, len=len@entry=124) at libnetfilter_log.c:325
#8  0x7fffb7da2b64 in nful_read_cb (fd=, what=, param=0x55578640) at ulogd_inppkt_NFLOG.c:463
#9  0xa340 in ulogd_select_main (tv=0x0) at select.c:105
#10 0x7f80 in ulogd_main_loop () at ulogd.c:934
#11 main (argc=, argv=) at ulogd.c:1477

Thread 1 (Thread 0x7fffb7ff2000 (LWP 9808)):
#0  _interp_iphdr (pi=0x5557ab40, len=0) at ulogd_raw2packet_BASE.c:718
ret = 0x5557acd8
nexthdr = 
#1  0x9e38 in ulogd_propagate_results (pi=0x55578640, 
pi@entry=0x0) at ulogd.c:518
ret = 
cur = 0x5557ab40
abort_stack = 0
#2  0x7fffb7da31ac in interp_packet (ldata=0x7120, pf_family=68 
'D', upi=0x0) at ulogd_inppkt_NFLOG.c:400
ph = 0x7fffb7bf0028
payload = 0x0
mark = 0
indev = 2
gid = 32767
ret = 0x555792b8
hw = 0x7fffb7bf0048
prefix = 0x7fffb7bf0030 "REJECT: "
outdev = 0
uid = 3086556916
payload_len = -1
ts = {tv_sec = 1476846114, tv_usec = 105901}
seq = 21845
#3  msg_cb (gh=, nfmsg=0x7fffb7bf0020, nfa=0x7120, 
data=0x0) at ulogd_inppkt_NFLOG.c:483
gh = 
data = 0x0
nfa = 0x7120
nfmsg = 0x7fffb7bf0020
upi = 0x0
npi = 
ret = 
#4  0x7fffb7d8e3f4 in __nflog_rcv_pkt (nlh=, nfa=, data=) at libnetfilter_log.c:162
nfmsg = 
h = 
group = 
nfldata = {nfa = 0x7130}
#5  0x7fffb7d79a88 in __nfnl_handle_msg (len=124, nlh=0x7fffb7bf0010, 
h=0x5557a210) at libnfnetlink.c:1236
nfa = 0x7130
ssh = 
type = 
subsys_id = 
err = 
#6  nfnl_handle_packet (h=0x5557a210, buf=0x7fffb7bf0010 "|", 
len=len@entry=124) at libnfnetlink.c:1256
rlen = 124
nlh = 0x7fffb7bf0010
#7  0x7fffb7d8e5f0 in nflog_handle_packet (h=, 
buf=, len=len@entry=124) at libnetfilter_log.c:325
No locals.
#8  0x7fffb7da2b64 in nful_read_cb (fd=, what=, param=0x55578640) at ulogd_inppkt_NFLOG.c:463
len = 124
what = 
param = 0x55578640
upi = 0x55578640
#9  0xa340 in ulogd_select_main (tv=0x0) at select.c:105
flags = 1
ufd = 0x555786d0
rds_tmp = {__fds_bits = {64, 0 }}
wrs_tmp = {__fds_bits = {0 }}
exs_tmp = {__fds_bits = {0 }}
i = 1
#10 0x7f80 in ulogd_main_loop () at ulogd.c:934
ret = 
next_alarm = {tv_sec = 1, tv_usec = 0}
next = 0x0
#11 main (argc=, argv=) at ulogd.c:1477
argch = 
daemonize = 0
change_uid = 1
user = 0x5556e030 "ulog"
pw = 
uid = 113
gid = 118
loglevel = 0

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.8.0-rc8-arm64 (SMP w/8 CPU cores)
LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ulogd2 depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u6
ii  libmnl0  1.0.3-5
ii  libnetfilter-acct1   

Bug#841193: qmmp: mplayer2 has gone away

[Matteo Cypriani]

Control: tag -1 pending

Le mardi 18 octobre 2016, 13:30:25 EDT James Cowgill a écrit :
> mplayer2 no longer exists in stretch, please can you remove it from the
> suggested packages.

Thanks for your report. I fixed that in the Git repository, it will be part of 
the next upload.

  Matteo

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

Bug#840424: Could you fix the error that is found by verilog-mode testing on Debian?

[Sean Whitton]

Hello Kiwamu,

On Wed, Oct 19, 2016 at 11:21:16AM +0900, Kiwamu Okabe wrote:
> OK. I should keep joining pkg-emacsen team.

It looks like you are already a member.

-- 
Sean Whitton

Bug#820036: Congratulations David , You have a new message from....z4w4retr

[Dave Home]

I already have direct tv

Sent from my iPhone

> On Oct 18, 2016, at 9:37 PM, Ian Jackson  
> wrote:
> 
> kiug 
> You've been UPGRADED! Get DIRECTV!
> 
> 
> Urgent! You need to activate your TV service
> 
> 
> Please claim also your $50 VISA gift card
> 
> 
> Confirm Now !
> 
> 
> 
> Unsubscribe 
> Opt Out 
> 
> 
> 
> 
> 
> 
> iwfyr

Bug#841257: sendmail: Privilege escalation from group smmsp to (user) root

[paul . szabo]

Hmm... you may also need to (once) do:
  chown smmsp /var/run/sendmail/stampdir/reload
when adopting my patch.

Cheers, Paul

Bug#841259: backport to jessie

[Hans-Christoph Steiner]

Package: gettext
Version: 0.19.6
Severity: wishlist


We are running into an issue building VLC for Android on jessie [1], we
need a newer version of gettext on jessie, which is what we use to build
apps.  I just built gettext from
stretch for testing, and it built fine.  Once there is a backport, I'll
happily test it for the various upgrade paths.

[1] https://gitlab.com/fdroid/fdroidserver/issues/224

Bug#840424: Could you fix the error that is found by verilog-mode testing on Debian?

[Kiwamu Okabe]

Hi Sean,

On Wed, Oct 19, 2016 at 11:19 AM, Sean Whitton  wrote:
>> I have a question. May I write "pkg-emacsen-add...@lists.alioth.debian.org"
>> at the "Maintainer" field in debian/control file?
>
> Yes.

OK. I should keep joining pkg-emacsen team.

Best regards,
-- 
Kiwamu Okabe at METASEPI DESIGN

Bug#841260: libfplll-dev: Please add -dev dependencies

[Jerome Benoit]

Package: libfplll-dev
Version: 4.0.4-2
Severity: normal

Dear Julien,

I have just noticed that libfplll-dev does not Depend[s] on libgmp-dev
and libmpfr-dev (and eventually on libqd-dev) whilt it should.

Thanks,
Jerome

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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libfplll-dev depends on:
ii  libfplll0  4.0.4-2

libfplll-dev recommends no packages.

libfplll-dev suggests no packages.

-- no debconf information

Bug#840424: Could you fix the error that is found by verilog-mode testing on Debian?

[Sean Whitton]

Hello Kiwamu,

On Tue, Oct 18, 2016 at 10:01:33PM +0900, Kiwamu Okabe wrote:
> On Mon, Oct 17, 2016 at 11:09 PM, Sean Whitton  
> wrote:
> > I didn't realise that you were trying to package verilog-mode for
> > xemacs.  dh_elpa supports only GNU Emacs.  Perhaps you need to revert to
> > your older packaging.  Apologies for leading you in circles somewhat.
> 
> Oh. so OK.
> 
> I have a question. May I write "pkg-emacsen-add...@lists.alioth.debian.org"
> at the "Maintainer" field in debian/control file?

Yes.

-- 
Sean Whitton

Bug#841081: [pkg-go] Bug#841081: RFP: golang-gopkg-dancannon-gorethink.v1 -- RethinkDB driver for Go

[Potter, Tim (HPE Linux Support)]

On 18 Oct 2016, at 1:21 AM, Guillem Jover  wrote:
> 
> Attached a working and tested packaging, where only the ITP bug number
> needs to be filled in the debian/changelog. The other patch is required
> to get the git repository back to a proper upstream version, because it
> was at v2 now.

Which repo were you looking at for the first patch?  The one at 
golang-gopkg-dancannon-gorethink.v1
was never at v2.  Maybe there was a split into v1 and v2 but that could have
happened before my time.

The second patch applies just fine.  I pushed it but the remark about changing
the build directory to _build that Martin Ferrari made about golang-dns applies
here as well.  Technically it could mess up multi-platform builds but I'm not 
aware
of packages that do this.

I added a missing build-dependency (why does v1 of the package require v2?
that's weird) and added a few tweaks.


Tim.

> 
> Thanks,
> Guillem
> <0001-Revert-import-of-v2.0.1-back-to-v1.4.1.patch><0002-Update-packaging.patch>___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#841121: [pkg-go] Bug#841121: RFP: golang-github-influxdata-config -- unified configuration management package

[Potter, Tim (HPE Linux Support)]

On 18 Oct 2016, at 6:06 AM, Guillem Jover  wrote:
> 
> The lack of license situation needs to be resolved before this can be
> uploaded (see the link in the License field above).

Yes.  (-:

> Attached a working and tested packaging, where only the ITP bug number
> needs to be filled in the debian/changelog, Maintainer changed, and Vcs
> fields added.

I've uploaded this to a new packaging repo and it builds just fine.

I took the liberty of setting the Maintainer to the team and uploaders to
sipwise.  Feel free to revert if that's not what you want.


Tim.

> 
> Thanks,
> Guillem
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#841258: golang: incorrect upgrade from 1.6 to 1.7 when gccgo is also present

[Eric Cooper]

Package: golang
Version: 2:1.7~1
Severity: normal

I had both gccgo and golang installed.  Before the recent upgrade to
golang 1.7, /usr/bin/go was the golang compiler.

After a recent apt-get upgrade, I noticed compilation failures and
found that /usr/bin/go was now gccgo-6, even though golang-1.7 had
been installed.

I had to purge and reinstall golang to fix the problem.

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

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

Versions of packages golang depends on:
ii  golang-1.7  1.7.1-2
ii  golang-doc  2:1.7~1
ii  golang-go   2:1.7~1
ii  golang-src  2:1.7~1

golang recommends no packages.

golang suggests no packages.

-- no debconf information

Bug#841120: [pkg-go] Bug#841120: RFP: golang-github-influxdata-toml -- TOML parser and encoder library for Golang

[Potter, Tim (HPE Linux Support)]

On 18 Oct 2016, at 6:00 AM, Guillem Jover  wrote:
> 
> There are two problems to be solved before this can be uploaded:
> 
>  * Uses a pre-built generated PEG output file, should be switched to
>use the newly packaged peg-go.
>  * Upstream has modified directly the pre-built generated PEG output
>file, tracked at ,
>but ITSM those changes could simply be dropped when the pre-generated
>file gets dropped.

I'm not sure that it's absolutely required that this be fixed but it's really
confusing to someone else coming along.  Technically you could document
this in debian/README.source but a better fix would be as you describe.

> Attached a working and tested packaging, where in addition to the above,
> only the ITP bug number needs to be filled in the debian/changelog,
> Maintainer changed, and Vcs fields added.

Uploaded to new package repo and it builds just fine.

I took the liberty of setting the Maintainer to the team and uploaders to
sipwise.  Feel free to revert if that's not what you want.


Tim.

> 
> Thanks,
> Guillem
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#841257: sendmail: Privilege escalation from group smmsp to (user) root

[Paul Szabo]

Package: sendmail
Version: 8.14.4-8+deb8u1
Severity: grave
Tags: patch security
Justification: user security hole


Supposing that due to some bug in sendmail, we were able to execute
commands as group smmsp, then that might be leveraged to cause root
to create any (empty) file.

The directory /var/run/sendmail/stampdir is group-smmsp-writable, so
we (as group smmsp) could create symlinks there pointing to any name.
Then when /etc/init.d/sendmail was run as root (to restart the daemon
maybe?), one or another of the symlinks

  /var/run/sendmail/stampdir/reload
  /var/run/sendmail/stampdir/cron_msp
  /var/run/sendmail/stampdir/cron_mta
  /var/run/sendmail/stampdir/cron_msp

might be followed to create an empty file.

Lines in /etc/init.d/sendmail:

   ...
   110  SENDMAIL_ROOT='/var/run/sendmail';
   ...
   144  STAMP_DIR="${SENDMAIL_ROOT}/stampdir";
   ...
   246  touch $STAMP_DIR/reload;
   ...
   367  touch $STAMP_DIR/reload;
   ...
   900  touch $STAMP_DIR/cron_msp;
   ...
   912  touch $STAMP_DIR/cron_mta;
   ...
   938  touch $STAMP_DIR/cron_msp;
   ...
  1130  if [ ! -d "${STAMP_DIR}" ]; then
  1131  mkdir -p "${STAMP_DIR}";
  1132  chown root:smmsp "${STAMP_DIR}";
  1133  chmod 02775 "${STAMP_DIR}";
  1134  fi;
   ...


Things missing to make a "convincing" exploit:
 - a way to "get" group smmsp: there have not been such issues for some
   years now;
 - how to trick the sysadmin into restarting sendmail;
 - under what conditions would any of those "touch" lines be run;
 - a way to "get root" by creating some empty file: damage can be done
   with /etc/nologin, maybe some exploitation with /etc/hosts.deny.
Seems this issue has low priority.


My suggested fix:

$ diff /etc/init.d/sendmail.bak <---> /etc/init.d/sendmail
246c246
<   touch $STAMP_DIR/reload;
---
>   su smmsp -s /bin/bash -c "touch $STAMP_DIR/reload";
367c367
<   touch $STAMP_DIR/reload;
---
>   su smmsp -s /bin/bash -c "touch $STAMP_DIR/reload";
900c900
<   touch $STAMP_DIR/cron_msp;
---
>   su smmsp -s /bin/bash -c "touch 
> $STAMP_DIR/cron_msp";
912c912
<   touch $STAMP_DIR/cron_mta;
---
>   su smmsp -s /bin/bash -c "touch $STAMP_DIR/cron_mta";
938c938
<   touch $STAMP_DIR/cron_msp;
---
>   su smmsp -s /bin/bash -c "touch 
> $STAMP_DIR/cron_msp";


Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Bug#841256: installation-report: successful stretch installation

[Gabor Nagy]

Package: installation-reports
Severity: normal
Tags: d-i

Dear Maintainer,

-- Package-specific info:

Boot method: USB stick
Image version: 
http://cdimage.debian.org/cdimage/stretch_di_alpha7/amd64/iso-cd/debian-stretch-DI-alpha7-amd64-netinst.iso
Date: 18/10/2016 22:30 BST

Machine: HP EliteBook 840
Partitions: 

Device Boot Start   End   Sectors   Size Id Type
/dev/sda1  * 2048 264478719 264476672 126.1G  7 HPFS/NTFS/exFAT
/dev/sda2   524290048 976771071 452481024 215.8G  7 HPFS/NTFS/exFAT
/dev/sda3   264478720 524290047 259811328 123.9G 83 Linux

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

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

Comments/Problems:



Installed in graphical expert mode. There were no problems, other than my WiFi
does not work without non-free firmware, so had to use wired ethernet.

After installation it boots, KDE starts, and there is sound. I am impressed.
Usually earlier Debian releases did not have sound after first installation, I
had to add various packages. Not needed this time. Well done.

when installing grub, the installer suggested force EFI removable. Chose not
to, and works without it.

When selecting tasks, there is a tree shown:
[x] Debian Desktop Environment
  [ ] Gnome
  [ ] Xfce
  [ ] KDE
etc.

This is a bit confusing. Desktop environment is selected by default but none of
the actual DEs. Based on my earlier Debian install experience, I assume by
default it would install Gnome.
If this is the case, I think Gnome should be selected too.

I can unselect Debian Desktop Environment and select a DE, for example KDE. It
is not clear if there is a difference between
[+] Debian Desktop Environment
  [+] KDE

 and

[ ] Debian Desktop Environment
  [+] KDE

I would prefer more explanation (what is Debian Desktop Environment task?), and
if there is a depencency (as indicated by the positioning of the checkboxes),
then a rule. For example if any of the DEs are selected, then Debian Desktop
Environment is selected. If Debian Desktop Environment is unselected, all DEs
are unselected.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20160630"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux hawk 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM 
Controller [8086:0a04] (rev 0b)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: Kernel driver in use: hsw_uncore
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
lspci -knn: DeviceName: 32
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 0b)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI 
HC [8086:9c31] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 8 Series 
HECI #0 [8086:9c3a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 8 Series HECI 
KT [8086:9c3d] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I218-LM [8086:155a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:198f]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio 
Controller [8086:9c20] (rev 04)
lspci 

Bug#841255: liferea: random crash: SIGABRT: assertion failed: (sqlite3_get_autocommit (db))

[Paul Wise]

Package: liferea
Version: 1.12~rc1-5
Severity: normal
Usertags: crash

I got a random crash (SIGABRT) in liferea. If the below gdb backtrace
isn't useful, please close this bug.

$ gdb -batch -n -ex 'set pagination off' -ex bt -ex 'thread apply all bt full' 
--core 
/var/crash/1000/31138-1000-1000-6-1476805337-chianamo--usr-bin-liferea.core 
/usr/bin/liferea
[New LWP 31138]
[New LWP 31155]
[New LWP 31150]
[New LWP 31154]
[New LWP 31156]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `liferea'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7fb261403400 (LWP 31138))]
#0  0x7fb25b8affdf in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:58
#1  0x7fb25b8b140a in __GI_abort () at abort.c:89
#2  0x7fb25bea94f5 in g_assertion_message (domain=domain@entry=0x0, 
file=file@entry=0x55b36b89ebb2 "db.c", line=line@entry=729, 
func=func@entry=0x55b36b89f600 <__func__.60456> "db_init", 
message=message@entry=0x55b36c6a2920 "assertion failed: (sqlite3_get_autocommit 
(db))") at ././glib/gtestutils.c:2429
#3  0x7fb25bea958a in g_assertion_message_expr (domain=domain@entry=0x0, 
file=file@entry=0x55b36b89ebb2 "db.c", line=line@entry=729, 
func=func@entry=0x55b36b89f600 <__func__.60456> "db_init", 
expr=expr@entry=0x55b36b89f032 "sqlite3_get_autocommit (db)") at 
././glib/gtestutils.c:2452
#4  0x55b36b861491 in db_init () at db.c:729
#5  0x55b36b85d185 in main (argc=, argv=) at 
main.c:240

Thread 5 (Thread 0x7fb243fff700 (LWP 31156)):
#0  0x7fb25b95c50d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb25be829d6 in g_main_context_iterate (priority=, 
n_fds=2, fds=0x7fb2380010c0, timeout=, context=0x7fb244011dc0) 
at ././glib/gmain.c:4228
poll_func = 0x7fb25be92820 
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 2
allocated_nfds = 2
fds = 0x7fb2380010c0
#2  0x7fb25be829d6 in g_main_context_iterate (context=0x7fb244011dc0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
././glib/gmain.c:3924
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 2
allocated_nfds = 2
fds = 0x7fb2380010c0
#3  0x7fb25be82d62 in g_main_loop_run (loop=0x7fb244011d50) at 
././glib/gmain.c:4125
__func__ = "g_main_loop_run"
#4  0x7fb25c69e4e6 in gdbus_shared_thread_func (user_data=0x7fb244011d90) 
at ././gio/gdbusprivate.c:247
data = 0x7fb244011d90
#5  0x7fb25beaa325 in g_thread_proxy (data=0x55b36c560720) at 
././glib/gthread.c:784
thread = 0x55b36c560720
#6  0x7fb25bc22464 in start_thread (arg=0x7fb243fff700) at 
pthread_create.c:333
__res = 
pd = 0x7fb243fff700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140403621754624, 
1729578137496448398, 0, 140403711854591, 0, 140404113477696, 
-1773233147832308338, -1773286154421146226}, mask_was_saved = 0}}, priv = {pad 
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#7  0x7fb25b96597f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7fb2495ed700 (LWP 31154)):
#0  0x7fb25b95c50d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb25be829d6 in g_main_context_iterate (priority=, 
n_fds=1, fds=0x7fb2440010e0, timeout=, context=0x55b36c565be0) 
at ././glib/gmain.c:4228
poll_func = 0x7fb25be92820 
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 1
allocated_nfds = 1
fds = 0x7fb2440010e0
#2  0x7fb25be829d6 in g_main_context_iterate 
(context=context@entry=0x55b36c565be0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 1
allocated_nfds = 1
fds = 0x7fb2440010e0
#3  0x7fb25be82aec in g_main_context_iteration 
(context=context@entry=0x55b36c565be0, may_block=may_block@entry=1) at 
././glib/gmain.c:3990
retval = 
#4  0x7fb2495f546d in dconf_gdbus_worker_thread (user_data=0x55b36c565be0) 
at dconf-gdbus-thread.c:82
context = 0x55b36c565be0
#5  0x7fb25beaa325 in g_thread_proxy (data=0x55b36c560140) at 
././glib/gthread.c:784
thread = 0x55b36c560140
#6  0x7fb25bc22464 in start_thread (arg=0x7fb2495ed700) at 
pthread_create.c:333
__res = 
pd = 0x7fb2495ed700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140403711858432, 
1729578137496448398, 0, 140735576066847, 0, 140404113477696, 

Bug#837895: [SOLVED] lightdm-gtk-greeter: GUI does not run, black screen, on startup

[Stephen Powell]

As of the last update of stretch, which I did just a few minutes ago,
this problem has been solved.  I suspect that the problem was gtk-related,
as the problems I was having with web (i.e. epiphany-browser) have been
fixed too.  However, since I am only subscribed to this bug report, and
did not open it myself, I will leave closure to the OP or to the package
maintainer.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Bug#841251: gdm3: Both Nautilas & Nemo Want to Manage Desktop

[Michael Biebl]

Am 19.10.2016 um 01:52 schrieb Stephen Allen:
> Package: gdm3
> Version: 3.22.1-1
> Severity: important
> 
> Dear Maintainer,
> 
> Hello.
> 
> I have both Gnome 3.22.x and Cinnamon installed. When logging in using
> GDM3 with Gnome specifically enabled, both Nautilas and Nemo are
> activated to manage my desktop, resulting in double overlapping icons.
> Once I forcequit Nemo, all is well.

Why is this bug filed against gdm3?
Sounds like a bug in nemo if it wants to manage a GNOME session.


-- 
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#841254: devscripts[bts]: cache 'bts status' output

[Daniel Shahaf]

Package: devscripts
Version: 2.16.8
Severity: wishlist

Dear Maintainer,

I propose to add to bts(1) a --cache-mode that caches 'bts status' output.

Use-case: I've taught zsh completion to show the bug subjects alongside
the bug numbers¹, but the implementation parses the  attribute
from the HTML cache files using Perl, and I'd like to simplify it to
parse 'bts status' output instead, without requiring online access.

Cheers,

Daniel

¹   % bts close symbol
> bug number
823043  - c++-annotations: FTBFS: `APATH' (symbol) multiply defined - 
Debian 
840482  - diffoscope: error at startup: AttributeError: undefined symbol: 
arc

Bug#841253: libreoffice-base-drivers: should no longer recommend libreoffice-sdbc-firebird, which is no longer built

[Vincent Lefevre]

Package: libreoffice-base-drivers
Version: 1:5.2.3~rc1-2
Severity: normal

The package libreoffice-sdbc-firebird is no longer built.
So, libreoffice-base-drivers should no longer recommend it
(which can partially block upgrades due to the broken
Recommends).

-- System Information:
Debian Release: stretch/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)

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 libreoffice-base-drivers depends on:
ii  dpkg  1.18.10
ii  libc6 2.24-4
ii  libgcc1   1:6.2.0-6
ii  libreoffice-core  1:5.2.3~rc1-2
ii  libstdc++66.2.0-6
ii  uno-libs3 5.2.2~rc2-2
ii  ure   5.2.2~rc2-2

Versions of packages libreoffice-base-drivers recommends:
pn  libreoffice-sdbc-firebird  
ii  libreoffice-sdbc-hsqldb1:5.2.3~rc1-2

Versions of packages libreoffice-base-drivers suggests:
pn  libjtds-java 
pn  libreoffice-mysql-connector | libmyodbc | libmysql-java  
ii  libreoffice-sdbc-postgresql  1:5.2.3~rc1-2
pn  libsqliteodbc | tdsodbc | mdbtools   

-- no debconf information

Bug#840153: Should have various tutorial manpages -- fixed patch submission

[Sean Whitton]

Hello,

On Tue, Oct 18, 2016 at 05:35:37PM -0700, Sean Whitton wrote:
> Please find attached git-am(1)-amenable patches adding some pod2man
> infrastructure, and dgit-maint-merge(7).
> 
> (I'm keen to retain the authorship information in the actual manpage,
> but you might not like how I've edited d/copyright, so I made that a
> separate patch.)

Sorry, screwed up the previous patch submission.  Here are the correct
four patches.

-- 
Sean Whitton
From c91d5c541983977bd7f6f796ce0b39c38bd12c25 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 18 Oct 2016 17:20:27 -0700
Subject: [PATCH 1/4] Makefile: build and clean *.7.pod

Signed-off-by: Sean Whitton 
---
 Makefile | 12 ++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 6fcc9bd..3f071e3 100644
--- a/Makefile
+++ b/Makefile
@@ -33,7 +33,7 @@ txtdocdir=$(prefix)/share/doc/dgit
 
 PROGRAMS=dgit
 MAN1PAGES=dgit.1
-MAN7PAGES=dgit.7
+MAN7PAGES=dgit.7 dgit-maint-merge.7
 TXTDOCS=README.dsc-import
 PERLMODULES=Debian/Dgit.pm
 
@@ -48,7 +48,7 @@ INFRA_PERLMODULES= \
 
 all:
 
-install:	installdirs
+install:	installdirs $(MAN7PAGES)
 	$(INSTALL_PROGRAM) $(PROGRAMS) $(DESTDIR)$(bindir)
 	$(INSTALL_DATA) $(MAN1PAGES) $(DESTDIR)$(man1dir)
 	$(INSTALL_DATA) $(MAN7PAGES) $(DESTDIR)$(man7dir)
@@ -80,3 +80,11 @@ check installcheck:
 
 clean distclean mostlyclean maintainer-clean:
 	rm -rf tests/tmp
+	set -e; for m in $(MAN7PAGES); do \
+		test -e $$m.pod && rm -f $$m; \
+	done
+
+%.7: %.7.pod
+	pod2man --section=7 --date="Debian Project" --center="dgit" \
+		--name=$(subst .7,,$@) \
+		$^ $@
-- 
2.9.3

From 7d9ab53f8b47815a62a4ff4e5c19facd70c57a90 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 18 Oct 2016 17:22:49 -0700
Subject: [PATCH 2/4] debian/copyright: add myself

Signed-off-by: Sean Whitton 
---
 debian/copyright | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/copyright b/debian/copyright
index 493b700..88a5e6d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -3,6 +3,8 @@ Integration between git and Debian-style archives
 
 Copyright (C)2013-2016 Ian Jackson
 
+dgit-maint-merge.7.pod is copyright (C)2016 Sean Whitton
+
 This program is free software: you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation, either version 3 of the License, or
-- 
2.9.3

From fdef83c4e1651315bda2fd86781cac136d148156 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 18 Oct 2016 17:23:11 -0700
Subject: [PATCH 3/4] Manpage: add dgit-maint-merge.7.pod

Signed-off-by: Sean Whitton 
---
 dgit-maint-merge.7.pod | 365 +
 1 file changed, 365 insertions(+)
 create mode 100644 dgit-maint-merge.7.pod

diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod
new file mode 100644
index 000..d9dcb51
--- /dev/null
+++ b/dgit-maint-merge.7.pod
@@ -0,0 +1,365 @@
+=head1 NAME
+
+dgit - tutorial for package maintainers, using a workflow centered around git-merge(1)
+
+=head1 INTRODUCTION
+
+This document describes elements of a workflow for maintaining a
+non-native Debian package using B.  The workflow makes the
+following opinionated assumptions:
+
+=over 4
+
+=item
+
+Git histories should be the non-linear histories produced by
+git-merge(1), preserving all information about divergent development
+that was later brought together.
+
+If you prefer linear histories, see dgit-maint-rebase(7).
+
+=item
+
+Maintaining convenient and powerful git workflows takes priority over
+the usefulness of the raw Debian source package.  The Debian archive
+is thought of as an output format.
+
+For example, we don't spend time curating a series of quilt patches.
+However, the information such a series would contain is readily
+available from B.
+
+=item
+
+It is more important to have the Debian package's git history be a
+descendent of upstream's git history than to use exactly the orig.tar
+that upstream makes available for download.
+
+=back
+
+=head1 GIT CONFIGURATION
+
+Add the following to your ~/.gitconfig to teach git-archive(1) how to
+compress orig tarballs:
+
+=over 4
+
+[tar "tar.xz"]
+	command = xz -c
+[tar "tar.gz"]
+	command = gzip -c
+
+=back
+
+=head1 INITIAL DEBIANISATION
+
+=head2 When upstream tags releases in git
+
+Suppose that the latest stable upstream release is 1.2.2, and this has
+been tagged '1.2.2' by upstream.
+
+=over 4
+
+% git clone -oupstream https://some.upstream/foo.git
+% cd foo
+% git verify-tag 1.2.2
+% git reset --hard 1.2.2
+% git branch --unset-upstream
+
+=back
+
+The final command detachs your master branch from the upstream remote,
+so that git doesn't try to push anything there, or merge unreleased
+upstream commits.  If you want to maintain a copy of your 

Bug#820036: Congratulations Don , You have a new message from....kPwcretr

[D S]

DON'T SEND THIS DISGUSTING TRASH HERE!

On Tue, Oct 18, 2016 at 12:30 PM, Ian Jackson <
ijack...@chiark.greenend.org.uk> wrote:

> kiug
>
> You've been UPGRADED! Get DIRECTV!
> Urgent! You need to activate your TV service
> Please claim also your $50 VISA gift card
> Confirm Now !
>
> Unsubscribe
> Opt Out
>
>
>
>
>
>
>  
> iwfyr
>
>

Bug#840153: Should have various tutorial manpages

[Sean Whitton]

control: tag -1 +patch

Please find attached git-am(1)-amenable patches adding some pod2man
infrastructure, and dgit-maint-merge(7).

(I'm keen to retain the authorship information in the actual manpage,
but you might not like how I've edited d/copyright, so I made that a
separate patch.)

-- 
Sean Whitton
From 45cc7d295cb818a2c236687d9d395d4712e500ce Mon Sep 17 00:00:00 2001
From: Ian Jackson 
Date: Mon, 17 Oct 2016 17:31:38 +0100
Subject: [PATCH 1/4] changelog: Finalise 2.2

Signed-off-by: Ian Jackson 
---
 debian/changelog | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 203a864..b8811e0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,7 +5,7 @@ dgit (2.2) unstable; urgency=low
   * Detect SIGPIPE (and SIGCHLD) being blocked or ignored.
 Closes:#841085.
 
- --
+ -- Ian Jackson   Mon, 17 Oct 2016 17:31:18 +0100
 
 dgit (2.1) unstable; urgency=low
 
-- 
2.9.3

From c91d5c541983977bd7f6f796ce0b39c38bd12c25 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 18 Oct 2016 17:20:27 -0700
Subject: [PATCH 2/4] Makefile: build and clean *.7.pod

Signed-off-by: Sean Whitton 
---
 Makefile | 12 ++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 6fcc9bd..3f071e3 100644
--- a/Makefile
+++ b/Makefile
@@ -33,7 +33,7 @@ txtdocdir=$(prefix)/share/doc/dgit
 
 PROGRAMS=dgit
 MAN1PAGES=dgit.1
-MAN7PAGES=dgit.7
+MAN7PAGES=dgit.7 dgit-maint-merge.7
 TXTDOCS=README.dsc-import
 PERLMODULES=Debian/Dgit.pm
 
@@ -48,7 +48,7 @@ INFRA_PERLMODULES= \
 
 all:
 
-install:	installdirs
+install:	installdirs $(MAN7PAGES)
 	$(INSTALL_PROGRAM) $(PROGRAMS) $(DESTDIR)$(bindir)
 	$(INSTALL_DATA) $(MAN1PAGES) $(DESTDIR)$(man1dir)
 	$(INSTALL_DATA) $(MAN7PAGES) $(DESTDIR)$(man7dir)
@@ -80,3 +80,11 @@ check installcheck:
 
 clean distclean mostlyclean maintainer-clean:
 	rm -rf tests/tmp
+	set -e; for m in $(MAN7PAGES); do \
+		test -e $$m.pod && rm -f $$m; \
+	done
+
+%.7: %.7.pod
+	pod2man --section=7 --date="Debian Project" --center="dgit" \
+		--name=$(subst .7,,$@) \
+		$^ $@
-- 
2.9.3

From 7d9ab53f8b47815a62a4ff4e5c19facd70c57a90 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 18 Oct 2016 17:22:49 -0700
Subject: [PATCH 3/4] debian/copyright: add myself

Signed-off-by: Sean Whitton 
---
 debian/copyright | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/copyright b/debian/copyright
index 493b700..88a5e6d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -3,6 +3,8 @@ Integration between git and Debian-style archives
 
 Copyright (C)2013-2016 Ian Jackson
 
+dgit-maint-merge.7.pod is copyright (C)2016 Sean Whitton
+
 This program is free software: you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation, either version 3 of the License, or
-- 
2.9.3

From fdef83c4e1651315bda2fd86781cac136d148156 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 18 Oct 2016 17:23:11 -0700
Subject: [PATCH 4/4] Manpage: add dgit-maint-merge.7.pod

Signed-off-by: Sean Whitton 
---
 dgit-maint-merge.7.pod | 365 +
 1 file changed, 365 insertions(+)
 create mode 100644 dgit-maint-merge.7.pod

diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod
new file mode 100644
index 000..d9dcb51
--- /dev/null
+++ b/dgit-maint-merge.7.pod
@@ -0,0 +1,365 @@
+=head1 NAME
+
+dgit - tutorial for package maintainers, using a workflow centered around git-merge(1)
+
+=head1 INTRODUCTION
+
+This document describes elements of a workflow for maintaining a
+non-native Debian package using B.  The workflow makes the
+following opinionated assumptions:
+
+=over 4
+
+=item
+
+Git histories should be the non-linear histories produced by
+git-merge(1), preserving all information about divergent development
+that was later brought together.
+
+If you prefer linear histories, see dgit-maint-rebase(7).
+
+=item
+
+Maintaining convenient and powerful git workflows takes priority over
+the usefulness of the raw Debian source package.  The Debian archive
+is thought of as an output format.
+
+For example, we don't spend time curating a series of quilt patches.
+However, the information such a series would contain is readily
+available from B.
+
+=item
+
+It is more important to have the Debian package's git history be a
+descendent of upstream's git history than to use exactly the orig.tar
+that upstream makes available for download.
+
+=back
+
+=head1 GIT CONFIGURATION
+
+Add the following to your ~/.gitconfig to teach git-archive(1) how to
+compress orig tarballs:
+
+=over 4
+
+[tar "tar.xz"]
+	command = xz -c
+[tar "tar.gz"]
+	

Bug#841235: /etc/vim/vimrc: Remove some obsolete comments from /etc/vim/vimrc

[James McCoy]

On Tue, Oct 18, 2016 at 07:55:43PM +0100, Sam Morris wrote:
> Here is a patch to remove some obsolete comments from /etc/vim/vimrc. I
> have removed the lines that suggest the user enable things that have
> already been enabled by defaults.vim.

Well, defaults.vim is _only_ loaded if a user vimrc isn't present, so if
a sysadmin wants to impose those settings, they should still be set in
the system-wide vimrc.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#841252: libtk-filedialog-perl: Control-W is deprecated in $W variable, needs to be changed to $^W with literal ^ character

[Carlo Segre]

Package: libtk-filedialog-perl
Version: 1.3-4
Severity: normal

Dear Maintainer,

When starting the "athena" program (from the horae package), the following 
error appears

Unrecognized character \x17; marked by <-- HERE after nSave) = $<-- HERE
near column 22 at /usr/share/perl5/Tk/FileDialog.pm line 610.
at /usr/lib/x86_64-linux-gnu/perl5/5.24/Tk/widgets.pm line 14.
Compilation failed in require at
/usr/lib/x86_64-linux-gnu/perl5/5.24/Tk/widgets.pm line 14.
at /usr/bin/athena line 76.
BEGIN failed--compilation aborted at /usr/bin/athena line 82.

It turns out that this is because of code in /usr/share/perl5/Tk/FileDialog.pm
which appears close to line 604:

  PRIVATE METHODS AND SUBROUTINES 
sub IsNum {
my($parm) = @_;
my($warnSave) = $^W;
$^W = 0;
my($res) = (($parm + 0) eq $parm);
$^W = $warnSave;
return $res;
}

The character "^W" is actually the single character Control-W instead of the 
"^" character followed by "W".  This use is deprecated and can be fixed by 
replacing the Control-W in the three lines above. 

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 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 libtk-filedialog-perl depends on:
ii  perl 5.24.1~rc3-3
ii  perl-tk  1:804.033-1+b3

libtk-filedialog-perl recommends no packages.

libtk-filedialog-perl suggests no packages.

-- no debconf information

Bug#841251: gdm3: Both Nautilas & Nemo Want to Manage Desktop

[Stephen Allen]

Package: gdm3
Version: 3.22.1-1
Severity: important

Dear Maintainer,

Hello.

I have both Gnome 3.22.x and Cinnamon installed. When logging in using
GDM3 with Gnome specifically enabled, both Nautilas and Nemo are
activated to manage my desktop, resulting in double overlapping icons.
Once I forcequit Nemo, all is well.

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

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

Versions of packages gdm3 depends on:
ii  accountsservice  0.6.40-3
ii  adduser  3.115
ii  cinnamon [x-window-manager]  3.0.7-2
ii  cinnamon-session [x-session-manager] 3.0.1-2
ii  dconf-cli0.26.0-2
ii  dconf-gsettings-backend  0.26.0-2
ii  debconf [debconf-2.0]1.5.59
ii  e17 [x-window-manager]   0.17.6-1.1
ii  gir1.2-gdm-1.0   3.22.1-1
ii  gnome-session [x-session-manager]3.22.1-1
ii  gnome-session-bin3.22.1-1
ii  gnome-session-flashback [x-session-manager]  3.22.0-2
ii  gnome-settings-daemon3.22.1-1
ii  gnome-shell  3.22.1-1
ii  gnome-terminal [x-terminal-emulator] 3.22.0-3
ii  gsettings-desktop-schemas3.22.0-1
ii  libaccountsservice0  0.6.40-3
ii  libaudit11:2.6.7-1
ii  libc62.24-4
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgdm1  3.22.1-1
ii  libglib2.0-0 2.50.1-1
ii  libglib2.0-bin   2.50.1-1
ii  libgtk-3-0   3.22.1-1
ii  libkeyutils1 1.5.9-9
ii  libpam-modules   1.1.8-3.3
ii  libpam-runtime   1.1.8-3.3
ii  libpam-systemd   231-9
ii  libpam0g 1.1.8-3.3
ii  librsvg2-common  2.40.16-1
ii  libselinux1  2.5-3
ii  libsystemd0  231-9
ii  libwrap0 7.6.q-25
ii  libx11-6 2:1.6.3-1
ii  libxau6  1:1.0.8-1
ii  libxdmcp61:1.1.2-1.1
ii  lsb-base 9.20161016
ii  metacity [x-window-manager]  1:3.22.0-1
ii  muffin [x-window-manager]3.0.5-2
ii  mutter [x-window-manager]3.22.1-2
ii  policykit-1  0.105-16
ii  ucf  3.0036
ii  x11-common   1:7.7+16
ii  x11-xserver-utils7.7+7
ii  xterm [x-terminal-emulator]  327-1

Versions of packages gdm3 recommends:
ii  at-spi2-core2.22.0-1
ii  desktop-base8.0.2
ii  x11-xkb-utils   7.7+3
ii  xserver-xephyr  2:1.18.4-2
ii  xserver-xorg1:7.7+16
ii  zenity  3.22.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.22.1-1
ii  libpam-gnome-keyring  3.20.0-3

-- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3

Bug#841213: chromium: Crash at startup

[Braiam Peguero]

The package has automatic debug symbols
generation. Follow the instructions at
https://wiki.debian.org/AutomaticDebugPackages
to enable the repository and install the
required packages.

On Tue, Oct 18, 2016 at 10:39 AM, Emil  wrote:
> Package: chromium
> Version: 53.0.2785.143-1
> Severity: important
>
> When I try to start chromium it crashes.
> There is no *-dbg package for this version so the only backtrace I have
> looks like this:
>
> #0  0xb32f699e in nettle_yarrow256_update ()
>from /usr/lib/i386-linux-gnu/libnettle.so.4
>#1  0xb3a69d01 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.30
>#2  0xb3a69e37 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.30
>#3  0xb39b7706 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.30
>#4  0xb39aab76 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.30
>#5  0xb3987b20 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.30
>#6  0xb7fea385 in call_init.part () from /lib/ld-linux.so.2
>#7  0xb7fea4ae in _dl_init () from /lib/ld-linux.so.2
>#8  0xb7fdbaff in _dl_start_user () from /lib/ld-linux.so.2
>
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.11-1-686-pae (SMP w/4 CPU cores)
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages chromium depends on:
> ii  libasound2   1.0.28-1
> ii  libatk1.0-0  2.16.0-2
> ii  libavcodec57 10:3.1.2-dmo2
> ii  libavformat5710:3.1.2-dmo2
> ii  libavutil55  10:3.1.2-dmo2
> ii  libc62.23-4
> ii  libcairo21.14.0-2.1
> ii  libcups2 1.7.2-1
> ii  libdbus-1-3  1.10.10-1
> ii  libexpat12.1.0-4
> ii  libfontconfig1   2.11.0-2
> ii  libfreetype6 2.5.1-1
> ii  libgcc1  1:5.2.1-14
> ii  libgdk-pixbuf2.0-0   2.31.4-2
> ii  libglib2.0-0 2.48.1-3
> ii  libgnome-keyring03.12.0-1
> ii  libgtk-3-0   3.20.7-1
> ii  libharfbuzz0b1.2.7-1+b1
> ii  libjpeg62-turbo  1:1.3.1-11
> ii  libnettle6   3.3-1
> ii  libnspr4 2:4.12-6
> ii  libnss3  2:3.26-2
> ii  libpango-1.0-0   1.40.1-1
> ii  libpangocairo-1.0-0  1.40.1-1
> ii  libpci3  1:3.3.1-1.1
> ii  libpulse05.0-13
> ii  libspeechd2  0.8-7
> ii  libstdc++6   6.1.1-12
> ii  libx11-6 2:1.6.2-1
> ii  libxcomposite1   1:0.4.4-1
> ii  libxcursor1  1:1.1.14-1
> ii  libxdamage1  1:1.1.4-1
> ii  libxext6 2:1.3.2-1
> ii  libxfixes3   1:5.0.1-1
> ii  libxi6   2:1.7.2-1
> ii  libxml2  2.9.2+dfsg1-1+b1
> ii  libxrandr2   2:1.5.0-1
> ii  libxrender1  1:0.9.8-1
> ii  libxslt1.1   1.1.28-2
> ii  libxss1  1:1.2.2-1
> ii  libxtst6 2:1.2.2-1
> ii  x11-utils7.7+2
> ii  xdg-utils1.1.0~rc1+git20111210-7
>
> Versions of packages chromium recommends:
> ii  fonts-liberation  1.07.3-3
>
> Versions of packages chromium suggests:
> pn  chromium-l10n  
>
> -- debconf information:
> Unescaped left brace in regex is deprecated, passed through in regex; marked
> by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/
> at /usr/share/perl5/Debconf/Question.pm line 72. Unescaped left brace in regex
> is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE
> ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 30.
>



-- 
Braiam Peguero

Bug#820036: Congratulations Joseph , You have a new message from....MIugretr

[joemmillz43]

Call me 


Sent from my MetroPCS 4G LTE Android device Original message 
From: Ian Jackson  Date: 10/18/2016  
3:40 PM  (GMT-06:00) To: joemmill...@gmail.com Cc: Ben Hutchings 
 Subject: Congratulations Joseph , You have a new message 
fromMIugretr 
kiug
 


You've been UPGRADED! Get DIRECTV!

Urgent! You need to activate your TV service

Please claim also your $50 VISA gift card

Confirm Now !





Unsubscribe


Opt Out

Bug#841250: php-facedetect: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Source: php-facedetect
Version: 1.1.0+git20160406-2
Severity: important
Justification: fails to build from source
Tags: patch

Dear Maintainer,

I am scheduled to transition of opencv.
This package is target to transition. I tested build with opencv 3.1.
As a result, this FTBFS with opencv 3.1.
Because libhighgui-dev and libcv-dev has been removed from opencv 3.1 package.
We need to use libopencv-dev instead of these package. And currenct
package disable
support of opencv 3 by patches/0002-Revert-opencv3-support.patch.

-
make[1]: Entering directory '/build/php-facedetect-1.1.0+git20160406'
/bin/bash /build/php-facedetect-1.1.0+git20160406/libtool
--mode=compile cc  -I. -I/build/php-facedetect-1.1.0+git20160406
-DPHP_ATOM_INC -I/build/php-facedetect-1.1.0+git20160406/include
-I/build/php-facedetect-1.1.0+git20160406/main
-I/build/php-facedetect-1.1.0+git20160406 -I/usr/include/php/20151012
-I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM
-I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext
-I/usr/include/php/20151012/ext/date/lib  -Wdate-time
-D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H  -g -O2
-fdebug-prefix-map=/build/php-facedetect-1.1.0+git20160406=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security   -c
/build/php-facedetect-1.1.0+git20160406/facedetect.c -o facedetect.lo
libtool: compile:  cc -I. -I/build/php-facedetect-1.1.0+git20160406
-DPHP_ATOM_INC -I/build/php-facedetect-1.1.0+git20160406/include
-I/build/php-facedetect-1.1.0+git20160406/main
-I/build/php-facedetect-1.1.0+git20160406 -I/usr/include/php/20151012
-I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM
-I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext
-I/usr/include/php/20151012/ext/date/lib -Wdate-time
-D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -g -O2
-fdebug-prefix-map=/build/php-facedetect-1.1.0+git20160406=.
-fstack-protector-strong -Wformat -Werror=format-security -c
/build/php-facedetect-1.1.0+git20160406/facedetect.c  -fPIC -DPIC -o
.libs/facedetect.o
/build/php-facedetect-1.1.0+git20160406/facedetect.c: In function
'zm_info_facedetect':
/build/php-facedetect-1.1.0+git20160406/facedetect.c:69:48: error:
'CV_VERSION' undeclared (first use in this function)
  php_info_print_table_row(2, "OpenCV version", CV_VERSION);
^~
/build/php-facedetect-1.1.0+git20160406/facedetect.c:69:48: note: each
undeclared identifier is reported only once for each function it
appears in
Makefile:194: recipe for target 'facedetect.lo' failed
-

I attached a patch that revice this problem.
Could you check this patch and apply?

Best regards,
  Nobuhiro
diff -Nru php-facedetect-1.1.0+git20160406/debian/changelog php-facedetect-1.1.0+git20160406/debian/changelog
--- php-facedetect-1.1.0+git20160406/debian/changelog	2016-04-20 04:23:11.0 +0900
+++ php-facedetect-1.1.0+git20160406/debian/changelog	2016-10-18 00:35:24.0 +0900
@@ -1,3 +1,13 @@
+php-facedetect (1.1.0+git20160406-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update B-D.
+Change from libhighgui-dev and libcv-dev to libopencv-dev.
+  * Support OpenCV 3.
+Remove 0002-Revert-opencv3-support.patch
+
+ -- Nobuhiro Iwamatsu   Tue, 18 Oct 2016 00:35:24 +0900
+
 php-facedetect (1.1.0+git20160406-2) unstable; urgency=medium
 
   * Add ${php:Depends} to d/control (Closes: #821824)
diff -Nru php-facedetect-1.1.0+git20160406/debian/control php-facedetect-1.1.0+git20160406/debian/control
--- php-facedetect-1.1.0+git20160406/debian/control	2016-04-20 04:23:11.0 +0900
+++ php-facedetect-1.1.0+git20160406/debian/control	2016-10-18 00:35:24.0 +0900
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian PHP PECL Maintainers 
 Uploaders: Mathieu Parent 
-Build-Depends: debhelper (>= 9), php-dev, dh-php, libhighgui-dev, libcv-dev
+Build-Depends: debhelper (>= 9), php-dev, dh-php, libopencv-dev
 Standards-Version: 3.9.7
 Vcs-Git: https://anonscm.debian.org/git/pkg-php/php-facedetect.git
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-php/php-facedetect.git
diff -Nru php-facedetect-1.1.0+git20160406/debian/patches/0002-Revert-opencv3-support.patch php-facedetect-1.1.0+git20160406/debian/patches/0002-Revert-opencv3-support.patch
--- php-facedetect-1.1.0+git20160406/debian/patches/0002-Revert-opencv3-support.patch	2016-04-20 04:23:11.0 +0900
+++ php-facedetect-1.1.0+git20160406/debian/patches/0002-Revert-opencv3-support.patch	1970-01-01 09:00:00.0 +0900
@@ -1,84 +0,0 @@
-From f84448f210b7999fd94a6dd76ee2eec0f2eab600 Mon Sep 17 00:00:00 2001
-From: Mathieu Parent 
-Date: Thu, 7 Apr 2016 06:40:27 +0200
-Subject: [PATCH] Revert "opencv3 support"
-
-This reverts commit 2a5056742a038f0de419376738fef81a184323a0.
-
-Until OpenCV 3 is in sid

- config.m4|  8 +++-
- config.w32   |  2 +-
- facedetect.c | 10 ++
- 3 

Bug#841249: calypso: Please add dependency on python-tz

[Jens Reyer]

Package: calypso
Version: 1.5-3
Severity: normal

Hi,

while trying to import the .ics of my old exported ownCloud calendar
calypso gave thousands of lines with:

No module named pytz

This was not critical, just spamming the terminal. I didn't explicitly
check the imported data.

Installing python-tz solved this. But again I haven't checked the data yet.

Do I need to investigate that further or send a test .ics?

Greets!
jre



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

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

Versions of packages calypso depends on:
ii  git  1:2.9.3-1
ii  python   2.7.11-2
ii  python-daemon2.1.1-1
ii  python-lockfile  1:0.12.2-2
ii  python-vobject   0.9.3-2

calypso recommends no packages.

calypso suggests no packages.

-- no debconf information

Bug#837095: dos2unix: Still you interested in maintain dos2unix?

[Jari Aalto]

On 2016-09-08 16:01, Joao Eriberto Mota Filho wrote:
| Package: dos2unix
| Severity: wishlist
| 
| Hi Jari,
| 
| dos2unix has no uploads from you since 2014. dos2unix is a very important tool
| in FOSS world.
| 
| I have interest in maintain dos2unix (and also blhc) in Debian. Please, let me
| to know what you think about it.

Hi Eriberto,

Help is always welcome. Would you like to co-maintain the package together?

The latest 7.3.4 has been uploaded to Git, so we can start from there.

  https://anonscm.debian.org/cgit/collab-maint/dos2unix.git/log/

Thanks,
Jari

Bug#841248: opencfu: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Source: opencfu
Version: 3.9.0-1
Severity: important
Justification: fails to build from source

Dear Maintainer,

I am scheduled to transition of opencv.
This package is target to transition. I tested build with opencv 3.1.
As a result, opencfu FTBFS with opencv 3.1.

-
src/processor/headers/Predictor.hpp: At global scope:
src/processor/headers/Predictor.hpp:23:9: error: 'CvRTrees' does not name a type
 CvRTrees m_trees;
 ^~~~
src/processor/headers/Predictor.hpp:24:9: error: 'CvRTParams' does not
name a type
 CvRTParams m_rt_params;
 ^~
Makefile:1038: recipe for target 'src/opencfu-main.o' failed
make[2]: *** [src/opencfu-main.o] Error 1
make[2]: Leaving directory
'/home/iwamatsu/priv/debian/ocv/opencfu/opencfu-3.9.0'
Makefile:655: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory
'/home/iwamatsu/priv/debian/ocv/opencfu/opencfu-3.9.0'
dh_auto_build: make -j1 returned exit code 2
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-

CvRTParams and CvRTrees are not provided in opencv 3.1.
We need to use the cv::Ptr instead.

This problem already fixed in upstream with following commit:
edecbbd6fa13304b6f6a39efd49426c22c164786
87bbe96fdbc0416351acbf6994493a2fd46aa933

Could you fix this problem?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


opencfu_3.9.0-1_amd64.build
Description: Binary data

Bug#841247: calypso: UnicodeDecodeError when importing an .ics

[Jens Reyer]

Package: calypso
Version: 1.5-3
Severity: normal

Hi,

I tried to import the .ics of my old exported ownCloud calendar,
but this failed with an UnicodeDecodeError. You may reproduce this
(note the accent in Café):

$ cat calypso-unicode-bug.ics
BEGIN:VCALENDAR
VERSION:2.0
BEGIN:VEVENT
SUMMARY:Café
END:VEVENT
END:VCALENDAR

$ calypso --import private/test calypso-unicode-bug.ics
Failed to import: calypso-unicode-bug.ics
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/calypso/webdav.py", line 524, in 
import_file
self.import_item(new_item, path)
  File "/usr/lib/python2.7/dist-packages/calypso/webdav.py", line 504, in 
import_item
self.create_file(new_item, context={})
  File "/usr/lib/python2.7/dist-packages/calypso/webdav.py", line 389, in 
create_file
context['action'] = u'Add %s'%item
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: ordinal 
not in range(128)


Greets!
jre



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

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

Versions of packages calypso depends on:
ii  git  1:2.9.3-1
ii  python   2.7.11-2
ii  python-daemon2.1.1-1
ii  python-lockfile  1:0.12.2-2
ii  python-vobject   0.9.3-2

calypso recommends no packages.

calypso suggests no packages.

-- no debconf information

Bug#841143: [pkg-gnupg-maint] Bug#841143: Suspected race in gpg1 to gpg2 conversion or agent startup

[Daniel Kahn Gillmor]

On Tue 2016-10-18 14:11:21 -0400, Ian Jackson wrote:
> Ian Jackson writes ("Re: [pkg-gnupg-maint] Bug#841143: Suspected race in gpg1 
> to gpg2 conversion or agent startup"):
>> This makes it somewhat surprising that it should fail occasionally.
>> Each of the individual tests is largely single-threaded.
>
> Also, watching tests by hand shows gpg pausing for a noticeable time
> (~500ms?) even on my extremely fast laptop, perhaps when converting
> the test gpg1 keys etc. to gpg2 keys etc.
>
> If I do this conversion once in the source, will the result be useable
> by gpg1 ?  (Since I want the test suite to still work on earlier
> versions of Debian.)

If you have a test suite that intends to use secret key material, and
you want it to work across different versions of GnuPG, your test suite
should not ship what it thinks is a GNUPGHOME.  GnuPG doesn't guarantee
that one version will necessarily work with the other's.

Instead, if you have public or secret key material that you want any
version of GnuPG to work with, you should ship that material in the
standard OpenPGP transferable formats (e.g. the output of "gpg
--export-keys" and "gpg --export-secret-keys"), and then import it at
the start of the test suite while building the GNUPGHOME for the test
suite to use.

The contents of any particular GNUPGHOME is not a part of the GnuPG API
contract.

  --dkg


signature.asc
Description: PGP signature

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: nginx: PHP 7 integration

[Michael Lustfield]

I agree that using a unix socket is better than using a tcp socket and
can support updating the ordering.

I also see no reason not to update the example to point at the newer
PHP socket location.

However, that other line is an example of connecting to a TCP socket
and I do not feel that it should be removed. I see (with painful
frequency) users uncommenting that line in order to use apache to
serve php (or worse). As much as I'd prefer people deploy more
robust/sane setups, I really don't want to field all of the extra
questions because the line went missing.

Bug#841149: devscripts: Improvements for debrepro script

[Guillem Jover]

Hi!

On Mon, 2016-10-17 at 23:14:01 -0400, James McCoy wrote:
> Thanks for the patches!  I think the first patch is straight forward
> enough.  I'll let Antonio comment on whether he wants to apply the other
> two.  I just had one comment, inline.

Perfect thanks!

> > @@ -83,13 +81,9 @@ create_build_script() {
> >  echo 'cd ../disorderfs'
> >fi
> >  
> > -  echo
> > -  echo 'dpkg-source --before-build .'
> > -  echo 'fakeroot debian/rules clean'
> > -
> >variation date
> > -  vary 'fakeroot debian/rules binary' \
> > -'faketime "+213days +7hours +13minutes" fakeroot debian/rules binary'
> > +  vary 'dpkg-buildpackage -b' \
> > +'dpkg-buildpackage -b -r"faketime +213days+7hours+13minutes fakeroot"'
> 
> Shouldn't these use "-us -uc" too?  The intention of debrepro is just to
> check for variance, not to produce something to upload, so I don't think
> it should default to signing.

Ah, indeed sorry, I've gotten used to not pass those anymore as I've
set them as default on my ~/.config/dpkg/buildpackage.conf file. :)

Attached rebased and fixed patches.

Thanks,
Guillem
From c9be0604cf10da3fbda6bec1b87f2905c80dcf7a Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 18 Oct 2016 03:54:21 +0200
Subject: [PATCH 1/2] debrepro: Use dpkg-buildpackage instead of ad-hoc code

Part of the reproducible machinery is handled already by
dpkg-buildpackage, so there's no need to duplicate it. We can also
pass faketime+fakeroot as a normal gain-root-command.
---
 scripts/debrepro.sh | 10 ++
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/scripts/debrepro.sh b/scripts/debrepro.sh
index 38dd14f..e1444fb 100755
--- a/scripts/debrepro.sh
+++ b/scripts/debrepro.sh
@@ -56,8 +56,6 @@ create_build_script() {
   echo "# package"
   echo
 
-  echo 'export SOURCE_DATE_EPOCH=$(date -d "$(dpkg-parsechangelog -SDate)" +%s)'
-
   variation PATH
   vary '' 'export PATH="$PATH":/i/capture/the/path'
 
@@ -83,13 +81,9 @@ create_build_script() {
 echo 'cd ../disorderfs'
   fi
 
-  echo
-  echo 'dpkg-source --before-build .'
-  echo 'fakeroot debian/rules clean'
-
   variation date
-  vary 'fakeroot debian/rules binary' \
-'faketime "+213days +7hours +13minutes" fakeroot debian/rules binary'
+  vary 'dpkg-buildpackage -b -us -uc' \
+'dpkg-buildpackage -b -us -uc -r"faketime +213days+7hours+13minutes fakeroot"'
 }
 
 
-- 
2.9.3

From 123cba54129187c45e3241c434f866921b19b10f Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 18 Oct 2016 04:29:43 +0200
Subject: [PATCH 2/2] debrepro: Compare .changes files and fallback to use
 debdiff

We should be checking all artifacts generated not just .deb files,
this includes .udebs and by-hand artifacts. This will also allow
adding support for source comparison.

If diffoscope is not present fallback to debdiff which is better than
a simple cmp(1).
---
 scripts/debrepro.sh | 35 +++
 1 file changed, 15 insertions(+), 20 deletions(-)

diff --git a/scripts/debrepro.sh b/scripts/debrepro.sh
index e1444fb..e7b19dd 100755
--- a/scripts/debrepro.sh
+++ b/scripts/debrepro.sh
@@ -3,6 +3,7 @@
 # debrepro: a reproducibility tester for Debian packages
 #
 # © 2016 Antonio Terceiro 
+# Copyright © 2016 Guillem Jover 
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -100,28 +101,22 @@ build() {
   mv "$tmpdir/build" "$tmpdir/$which_build"
 }
 
-binmatch() {
-  cmp --silent "$1" "$2"
-}
-
 compare() {
   rc=0
-  for first_deb in "$tmpdir"/first/*.deb; do
-deb="$(basename "$first_deb")"
-second_deb="$tmpdir"/second/"$deb"
-if binmatch "$first_deb" "$second_deb"; then
-  echo "✓ $deb: binaries match"
-else
-  echo ""
-  rc=1
-  if which diffoscope >/dev/null; then
-diffoscope "$first_deb" "$second_deb" || true
-  else
-echo "✗ $deb: binaries don't match"
-  fi
-fi
-  done
-  if [ "$rc" -ne 0 ]; then
+  first_changes=$(echo "$tmpdir"/first/*.changes)
+  changes="$(basename "$first_changes")"
+  second_changes="$tmpdir/second/$changes"
+
+  if which diffoscope >/dev/null; then
+diffoscope "$first_changes" "$second_changes" || rc=1
+  else
+debdiff -q -d --control --controlfiles ALL \
+  "$first_changes" "$second_changes" || rc=1
+  fi
+  if [ "$rc" -eq 0 ]; then
+echo "✓ $changes: artifacts match"
+  else
+echo "✗ $changes: artifacts do not match"
 echo "E: package is not reproducible."
 if ! which diffoscope >/dev/null; then
   echo "I: install diffoscope for a deeper comparison between binaries"
-- 
2.9.3

Bug#841246: gmic: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Source: gmic
Version: 1.6.8-3
Severity: important
Justification: fails to build from source
Tags: patch

Hi,

I am scheduled to transition of opencv.
This package is target to transition. I tested build with opencv 3.1.
As a result, FTBFS with opencv 3.1.
Because libcv-dev and libhighgui-dev has been removed from opencv 3.1 package.

I created a patch which revice this problem.
Could you check patch and apply?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
diff -Nru gmic-1.6.8/debian/control gmic-1.6.8/debian/control
--- gmic-1.6.8/debian/control   2016-01-17 01:12:03.0 +0900
+++ gmic-1.6.8/debian/control   2016-10-19 06:40:23.0 +0900
@@ -11,8 +11,6 @@
  libopenexr-dev,
  libqt4-dev,
  libilmbase-dev,
- libcv-dev,
- libhighgui-dev,
  libcurl4-openssl-dev
 Standards-Version: 3.9.4
 Homepage: http://gmic.sourceforge.net/

Bug#840674: Fixed by rebuilding libcrypto++, wxwidgets and amule

[Bram Senders]

As suggested in https://github.com/amule-project/amule/issues/77, I rebuilt
the source packages libcrypto++-5.6.3, wxwidgets3.0-3.0.2+dfsg and
amule-2.3.2 and the resulting aMule deb runs fine here.

Regards,
Bram Senders

Bug#841244: auto-multiple-choice: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Source: auto-multiple-choice
Version: 1.3.0-1
Severity: important
Justification: fails to build from source
Tags: patch

Dear Maintainer,

I am scheduled to transition of opecv.
This package is subject to transition. I tested build with opencv 3.1.
As a result, FTBFS with opencv 3.1.
Cause is that libopencv_imgcodecs library is not specified at the time
of the library of the link.

-
perl -p vars-subs.pl doc/sty/automultiplechoice.dtx.in >
doc/sty/automultiplechoice.dtx
gcc -o AMC-detect AMC-detect.cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/home/iwamatsu/priv/debian/ocv/auto-multiple-choice/auto-multiple-choice-1.3.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
 -lstdc++ -lm -I /usr/include/opencv -lopencv_core -lopencv_highgui
-lopencv_imgproc
/usr/bin/ld: /tmp/ccppjzVB.o: undefined reference to symbol 'cvLoadImage'
//usr/lib/x86_64-linux-gnu/libopencv_imgcodecs.so.3.1: error adding
symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:123: recipe for target 'AMC-detect' failed
make[1]: *** [AMC-detect] Error 1
-

I attached a patch that revice this problem.
Could you check this patch and apply?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


fix-build-with-opencv-3.1
Description: Binary data


auto-multiple-choice_1.3.0-1_amd64.build
Description: Binary data

Bug#821051: Need support for uploading and signing EFI executables

[Ben Hutchings]

On Tue, 2016-10-18 at 23:34 +0200, Ansgar Burchardt wrote:
> Ben Hutchings writes:
> > On Tue, 2016-10-18 at 22:55 +0200, Ansgar Burchardt wrote:
> > > Is there any documentation how this is supposed to work?
> > 
> > 
> > Nothing comprehensive as yet.  Where should it go?
> 
> 
> It doesn't need to be comprehensive.  I just would like to understand
> what needs to happen.
[...]

In brief:

1. A first source package (grub, linux, etc.) builds byhand tarballs
containing all the files that need signing, in addition to the usual
binary packages.

2. The byhand script on dak unpacks the tarball, generates detached
signatures using the appropriate key(s) and publishes another tarball
containing those signatures.

3. The maintainer prepares a second source package (grub-signed, linux-
signed, etc.) containing the detached signatures.  It build-depends on
the unsigned binary packages produces by the first source package, and
builds signed binary packages based on them.

I hope that answers all your questions.

Ben.

-- 
Ben Hutchings
To err is human; to really foul things up requires a computer.

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

Bug#840574: Please backport libgo fixes for sparc64

[James Clarke]

Control: tags -1 patch
(almost; explained below)

Hi Matthias,
On Tue, Oct 18, 2016 at 01:47:20PM +0200, Matthias Klose wrote:
> Control: tags -1 - patch
>
> James, based on your feedback, I tried to apply these revisions on the branch,
> had to update some of these, and got a failed build. I'm not intending to work
> on this, and would like to ask you to prepare a tested debdiff for a backport 
> or
> to get the backport upstream if you want to include the libgo port into the
> gcc-6 Debian packages.

Please find a debdiff attached; I have successfully built it on sparc64.

There is just *one* little detail which messes this up (and perhaps was
the cause of your failure?): libgo-elf-relocations-sparc64.diff
references a new binary file (for the test suite), but "svn diff"
doesn't include the actual data, nor does quilt seem to support
git-style binary diffs. Please either remove the hunks for
libgo/go/debug/elf/{file_test.go,testdata/go-relocation-test-gcc620-sparc64.obj}
or place a copy of the latter .obj in the source package and ensure it
gets copied to the same relative directory under src when
unpacking/patching.

Do let me know if I can do anything else to make this happen. I will
also see if I can get them backported upstream (though even with that
you'll still need to faff about with the .obj or drop the test...).

Thanks,
James

> On 16.10.2016 19:40, James Clarke wrote:
> > Control: tags -1 - help + patch
> >
> > Hi Matthias,
> > On Thu, Oct 13, 2016 at 01:50:43PM +0200, Matthias Klose wrote:
> >> Control: tags -1 + help
> >> Control: tags -1 - patch
> >>
> >> James, please could you name the revisions in the GCC subversion 
> >> repository?
> >> Afaics these are r241084, r241077, r241051.  Even better, could you test 
> >> and
> >> propose this backport upstream?
> >
> > To confirm, they are the following revisions:
> >
> > * r241171 (sparc64 relocations, e1fc2925 in go master, now also in
> >gofrontend/gccgo)
> > * r241084 (don't use pt_regs; unnecessary, and seemingly not defined by
> >the included headers on arm64)
> > * r241072 (make rawClone no_split_stack)
> > * r241051 (fix getrandom on sparc64 and clone on sparc*)
> > * r240457 (add getrandom for MIPS/SPARC)
> >
> > We've been using the latest gcc-6 package with these patches (other than
> > no_split_stack and pt_regs fixups) applied on top for sparc64 (uploaded
> > to unreleased) for the past few days, and the only packages which fail
> > to build seem to be because Debian currently has an out-of-date x/sys
> > package without sparc64 definitions. I haven't been aware of any
> > regressions.
> >
> > Ian: I imagine the getrandom and elf changes would be fine for gcc-6,
> > but what about the clone changes? I can understand if that's too
> > invasive, but backporting would be great.
> >
> > Regards,
> > James
> >
> >> On 12.10.2016 23:35, James Clarke wrote:
> >>> Source: gcc-6
> >>> Version: 6.2.0-6
> >>> User: debian-sp...@lists.debian.org
> >>> Usertags: sparc64
> >>> X-Debbugs-Cc: debian-sp...@lists.debian.org
> >>> Tags: patch fixed-upstream
> >>>
> >>> Hi,
> >>> Could you please backport the patches listed below so that we can have a
> >>> working gccgo? They fix the (minor) issue of using the wrong syscall
> >>> number for getrandom (if code uses it), add support for sparc64's
> >>> relocations, and also the following error when running go build:
> >>>
> >>> /usr/bin/sparc64-linux-gnu-gccgo-6: wait: no child processes
> >>> /usr/bin/sparc64-linux-gnu-gccgo-6: exit status 1
> >>>
> >>> The patches are:
> >>>
> >>> https://go.googlesource.com/go/+/e1fc292500aa70c265937aebad00ac010031cbaf
> >>> (not yet pulled into gofrontend's libgo)
> >>> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=a357a86a9f2772561454ce17ef13a89a51fc4a27
> >>> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=0509fa0eae193f8d99886e9b6a1feda4c6c16356
> >>> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3457370357929d70f26873e914fae6ea6f1a8ffd
> >>>
> >>> With all but the last patch (a minor fixup after my patches), I have
> >>> been able to successfully build and run go programs on sparc64.
> >>>
> >>> Regards,
> >>> James
> >>>
> >>
>
diff -u gcc-6-6.2.0/debian/changelog gcc-6-6.2.0/debian/changelog
--- gcc-6-6.2.0/debian/changelog
+++ gcc-6-6.2.0/debian/changelog
@@ -1,3 +1,16 

Bug#821051: Need support for uploading and signing EFI executables

[Julien Cristau]

On Tue, Oct 18, 2016 at 22:55:19 +0200, Ansgar Burchardt wrote:

> Is there a way to not pass the pin via command-line arguments as
> currently implemented in [1]?
> 
Linux's sign-file, which is used for kernel modules, reads the
KBUILD_SIGN_PIN environment variable.

Cheers,
Julien

Bug#841243: mate-desktop: Please change icon location for mate-color-select

[Jean-Philippe MENGUAL]

Package: mate-desktop
Version: 1.16.0-1
Severity: normal

Dear Maintainer,

Hi,

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

   * What led up to the situation?

I've seen a mate-color-select as a package in a previous testing. It has
disappeared. I realized it was included in mate-desktop now. In MATE 1.8,
we use gnome-choose-color tools, from Preferences menu (System menu).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Go to System -> Preferences -> Display. Nothing.

In Software -> Graphics, it is Colours selection.

   * What was the outcome of this action?

This icon should be in Preferences, as it's an appearance setting. It's not
a utility to tweak colours of something, it affects desktop colours.

   * What outcome did you expect instead?

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

Regards,


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

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

Versions of packages mate-desktop depends on:
ii  hicolor-icon-theme0.15-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-3
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.1-1
ii  libgtk-3-03.22.1-1
ii  libmate-desktop-2-17  1.16.0-1
ii  libpango-1.0-01.40.3-2
ii  libpangocairo-1.0-0   1.40.3-2
ii  libstartup-notification0  0.12-4
ii  libxrandr22:1.5.0-1
ii  mate-desktop-common   1.16.0-1
ii  python2.7.11-2
ii  python-requests   2.11.1-1

Versions of packages mate-desktop recommends:
ii  mate-user-guide  1.16.0-1

mate-desktop suggests no packages.

-- no debconf information

Bug#820036: Congratulations lashunda , You have a new message from....XVC2retr

[lawanda red]

-Original Message-
From: "Ian Jackson" 
Sent: ‎10/‎18/‎2016 3:40 PM
To: "tigerby...@gmail.com" 
Cc: "Ben Hutchings" 
Subject: Congratulations lashunda , You have a new message fromXVC2retr

kiug 

You've been UPGRADED! Get DIRECTV!

Urgent! You need to activate your TV service

Please claim also your $50 VISA gift card

Confirm Now !


Unsubscribe 
Opt Out 

Bug#821051: Need support for uploading and signing EFI executables

[Ansgar Burchardt]

Ben Hutchings writes:
> On Tue, 2016-10-18 at 22:55 +0200, Ansgar Burchardt wrote:
>> Is there any documentation how this is supposed to work?
>
> Nothing comprehensive as yet.  Where should it go?

It doesn't need to be comprehensive.  I just would like to understand
what needs to happen.

>> What uses the signatures the archive is planned to write to dists/*?
>
> Scripts for preparing the source packages that build signed binaries.
> (Which will probably be included in those source packages, but don't
> have to be.)

How does building signed binaries work? That sounds like the signature
gets merged into the binaries dak signed in some way?

>> It looks wrong to bypass embargoed for the signatures. We avoid showing
>> which packages will get security updates in the future.
>
> That's a fair point.  But they need to be findable by a maintainer who
> doesn't have access to embargoed packages in general.  How about using
> a hash of the changelog?

Wouldn't the maintainer need access to the embargoed binaries as well as
the signatures to prepare the signed version?

Ansgar

Bug#839869: transition: poppler 0.48.0

[Pino Toscano]

In data lunedì 17 ottobre 2016 21:11:00 CEST, Emilio Pozuelo Monfort ha scritto:
> On 08/10/16 20:34, Pino Toscano wrote:
> > In data giovedì 6 ottobre 2016 10:25:57 CEST, Rene Engelhard ha scritto:
> >> Hi,
> >>
> >> On Wed, Oct 05, 2016 at 10:13:14PM +0200, Pino Toscano wrote:
> >>> This transition impacts the existing poppler libraries in the following 
> >>> ways:
> >>> - libpoppler61 → libpoppler64
> >> [...]
> >>>   boomaga
> >>>   calligra
> >>>   cups-filters
> >>>   emacs-pdf-tools
> >>>   gambas3
> >>>   gdal
> >>>   gdcm
> >>>   inkscape
> >>>   ipe-tools
> >>>   pdf2djvu
> >>>   pdf2htmlex
> >>>   popplerkit.framework
> >>>   texlive-bin
> >>>   texworks
> >>>   xpdf
> >>
> >> I believe there's stuff missing there for whatever reason. E.g. libreoffice
> >> (via libreoffice-pdfimport, 
> >> https://packages.debian.org/sid/libreoffice-pdfimport).
> >>
> >> Was in your last transition bugs afaicr, so I wonder what went wrong this 
> >> time ;)
> > 
> > Oh right, sorry, it was indeed missing.  In the above list there is also:
> > 
> >   libreoffice
> >   openscenegraph
> >   openscenegraph-3.4
> 
> I see the new poppler is now in experimental. Do the rdeps build against the 
> new
> version?

I could test everything but LibreOffice: no failures.

Rene, could you please give LO + poppler/experimental a try? Thanks!

-- 
Pino Toscano

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

Bug#821051: Need support for uploading and signing EFI executables

[Ben Hutchings]

On Tue, 2016-10-18 at 22:55 +0200, Ansgar Burchardt wrote:
> Steve McIntyre writes:
> > As discussed with various people in the past, for UEFI Secure Boot to
> > work we'll need changes in dak (and elsewhere?) to support upload and
> > signing of EFI executables.
> > 
> > Colin has pointed at the code in launchpad as inspiration:
> > 
> > https://git.launchpad.net/launchpad/tree/lib/lp/archivepublisher/uefi.py
> > https://git.launchpad.net/launchpad/tree/lib/lp/archivepublisher/tests/test_uefi.py
> > 
> > We'd love to make this happen in time for stretch if at all possible.
> 
> 
> Is there any documentation how this is supposed to work?

Nothing comprehensive as yet.  Where should it go?

> Which files do need to be signed? And by what key?

EFI binaries and kernel modules.

EFI binaries need to be signed by a key for which the certificate is
embedded in shim, and kernel modules need to be signed by a key for
which the certificate is embedded in linux.

There is no need for those keys to be the same as each other.

> What uses the signatures the archive is planned to write to dists/*?

Scripts for preparing the source packages that build signed binaries. 
(Which will probably be included in those source packages, but don't
have to be.)

> It looks wrong to bypass embargoed for the signatures. We avoid showing
> which packages will get security updates in the future.

That's a fair point.  But they need to be findable by a maintainer who
doesn't have access to embargoed packages in general.  How about using
a hash of the changelog?

> Is there a way to not pass the pin via command-line arguments as
> currently implemented in [1]?

I don't know the answer to this.

Ben.

> Ansgar
> 
> >   [1] 
> 
-- 
Ben Hutchings
To err is human; to really foul things up requires a computer.



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

Bug#834755: apt-cacher-ng: please make the build reproducible

[Chris Lamb]

Eduard Bloch wrote:

> Ehm, it looks like you did not look up the meaning of the other
> tar parameters in the command line you patched ($TARARGS).

Sorry about that; and thank you.


Regards,

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

Bug#841241: RFS: quark-sphinx-theme/0.4.0-1 [RC]

[Felix Krull]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: debian-pyt...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "quark-sphinx-theme"

* Package name : quark-sphinx-theme
   Version : 0.4.0-1
   Upstream Author : Felix Krull 
* URL : https://pypi.python.org/pypi/quark-sphinx-theme
* License : BSD
  Section : python

It builds those binary packages:

  python-quark-sphinx-theme - Sphinx theme designed for QTextBrowser
(Python 2)
  python3-quark-sphinx-theme - Sphinx theme designed for QTextBrowser
(Python 3)

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

  https://mentors.debian.net/package/quark-sphinx-theme

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

  dget -x
https://mentors.debian.net/debian/pool/main/q/quark-sphinx-theme/quark-sphinx-theme_0.4.0-1.dsc

Changes since the last upload:
* Import quark-sphinx-theme_0.4.0.orig.tar.bz2
  - This fixes running the tests in certain situations. (Closes: #839299)
* debian/control: remove Sphinx dependency (it's in setup.py now).
* debian/copyright: adjust paths to new src directory.

--
This is mostly a new upstream release. As for the referenced bug (an FTBFS
due to some tests not running properly), it was fixed by this upstream
commit:
https://bitbucket.org/fk/quark-sphinx-theme/commits/3c76149f2600b029623e761df1083868b3349c1f
While, in retrospect, I'm not sure these tests ever tested correctly
before, I admit I don't know what caused them to fail here and now, but I
verified the above change fixes them.

Regards,
Felix

Bug#841181: debootstrap: Debootstrap fails to create new Ubuntu environment (Xenial, Yakety)

[Ansgar Burchardt]

Etienne Loks writes:
>* What led up to the situation?
>
> Installing an Ubuntu container fails with:

What is the command you run?  As you mention lxc below, is it
debootstrap or some lxc command?

> Aucune version du paquet lxcguest n'est disponible, mais il existe dans la
> base de données. Cela signifie en général que le paquet est manquant, qu'il
> est devenu obsolète ou qu'il n'est disponible que sur une autre source
>
> E: Le paquet « lxcguest » n'a pas de version susceptible d'être installée
> lxc_container: container creation template for osm failed
> lxc_container: Error creating container osm

Please use `export LC_ALL=C.UTF-8` when reporting bugs so error messages
are in English.

>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> After commenting the line installing the package lxcguest in
> /usr/share/lxc/templates/lxc-ubuntu the install is successful.

Ansgar

Bug#820036: Congratulations Sharrean , You have a new message from....mrxDretr

[Sharrean McCrimmon]

If this is going to renew my contract with direct tv, please cancel.

On Tue, Oct 18, 2016 at 3:36 PM, Ian Jackson <
ijack...@chiark.greenend.org.uk> wrote:

> kiug
>
> You've been UPGRADED! Get DIRECTV!
> Urgent! You need to activate your TV service
> Please claim also your $50 VISA gift card
> Confirm Now !
>
> Unsubscribe
> Opt Out
>
>
>
>
>
>
>  
> iwfyr
>
>


-- 
Have a Wonderful Day!

Bug#841242: [kwin-x11] Non-KDE Windows Titlebar Not Visible but Operational

[David Baron]

Package: kwin-x11
Version: 4:5.8.1-1
Severity: normal

--- Please enter the report below this line. ---
Non-KDE Windows, such as Firefox, Ace-Penguin games, etc., come  up without 
their title bar. The title bar's functionality is active, clicking at the 
appropriate place works. Dragging the window this area may drag background 
that would be behind the title bar.

This occurs on all compositor alternatives. Changing the compositor will 
restore the title bars but they are delayed. Next KDE session will have them 
not visible again.

KDE windows work fine.

(This might not be the correct package for this bug?)

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.7.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-
==
kwin-common  (= 4:5.8.1-1) | 4:5.8.1-1
libc6(>= 2.14) | 
libepoxy0 (>= 1.0) | 
libgcc1 (>= 1:3.4) | 
libkf5configcore5  (>= 4.97.0) | 
libkf5coreaddons5  (>= 5.11.0) | 
libkf5crash5   (>= 4.96.0) | 
libkf5i18n5(>= 4.97.0) | 
libkf5windowsystem5(>= 4.96.0) | 
libkwinglutils9  (>= 4:5.1.95+git20150122) | 
libkwinxrenderutils9 (>= 4:5.1.95+git20150122) | 
libqt5core5a   (>= 5.6.0~beta) | 
libqt5gui5 (>= 5.5.0~) | 
libqt5widgets5 (>= 5.5.0~) | 
libqt5x11extras5(>= 5.6.0) | 
libstdc++6  (>= 4.4.0) | 
libx11-6   | 
libxcb-cursor0 (>= 0.0.99) | 
libxcb-randr0 (>= 1.3) | 
libxcb-xfixes0 | 
libxcb1   (>= 1.6) | 
libxi6 (>= 2:1.2.99.4) | 


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#821051: Need support for uploading and signing EFI executables

[Ansgar Burchardt]

Steve McIntyre writes:
> As discussed with various people in the past, for UEFI Secure Boot to
> work we'll need changes in dak (and elsewhere?) to support upload and
> signing of EFI executables.
>
> Colin has pointed at the code in launchpad as inspiration:
>
> https://git.launchpad.net/launchpad/tree/lib/lp/archivepublisher/uefi.py
> https://git.launchpad.net/launchpad/tree/lib/lp/archivepublisher/tests/test_uefi.py
>
> We'd love to make this happen in time for stretch if at all possible.

Is there any documentation how this is supposed to work?

Which files do need to be signed? And by what key?

What uses the signatures the archive is planned to write to dists/*?

It looks wrong to bypass embargoed for the signatures. We avoid showing
which packages will get security updates in the future.

Is there a way to not pass the pin via command-line arguments as
currently implemented in [1]?

Ansgar

  [1] 

Bug#841239: json-simple: New version available

[Oliver Kopp]

Dear Emmanuel,

> Is this update required for another package?

Not yet. - Please feel free tho close the bug until someone really
needs the package. We are currently "just" evaluating alternatives.

> Do you know if the 2.x version is compatible with the version 1.x?

The code reads like that, but I did not do a thorough test.

Cheers,

Oliver

Bug#839299:

[Felix Krull]

owner  839299 !

Bug#841240: linux: x32 preadv/pwritev syscalls broken in kernel 4.7

[Aurelien Jarno]

Source: linux
Version: 4.7.6-1
Severity: normal

The x32 preadv/pwritev syscalls have been broken in kernel 4.7-rc1 by
this commit:

| commit 482dd2ef124484601adea82e5e806e81e2bc5521
| Author: Christoph Hellwig 
| Date:   Thu Apr 7 22:43:59 2016 +0200
|
| x86/syscalls: Wire up compat readv2/writev2 syscalls
|
| Reported-by: David Smith 
| Tested-by: David Smith 
| Signed-off-by: Christoph Hellwig 
| Cc: Andy Lutomirski 
| Cc: Borislav Petkov 
| Cc: Brian Gerst 
| Cc: Denys Vlasenko 
| Cc: H. Peter Anvin 
| Cc: Linus Torvalds 
| Cc: Peter Zijlstra 
| Cc: Thomas Gleixner 
| Link: http://lkml.kernel.org/r/20160407204359.ga3...@lst.de
| Signed-off-by: Ingo Molnar 

It causes the glibc testsuite to fail on x32 when running a 4.7 kernel,
and more precisely the misc/tst-preadvwritev and misc/tst-preadvwritev64
tests.

The syscalls have been fixed in kernel 4.8-rc1 by this commit, even if
neither the commit nor the mail it refers too talk about a breakage:

| commit 3ebfd81f7fb3e81a754e37283b7f38c62244641a
| Author: H.J. Lu 
| Date:   Thu Jul 14 12:31:53 2016 -0700
|
| x86/syscalls: Add compat_sys_preadv64v2/compat_sys_pwritev64v2
| 
| Don't use the same syscall numbers for 2 different syscalls:
| 
|  534x32 preadv  compat_sys_preadv64
|  535x32 pwritev compat_sys_pwritev64
|  534x32 preadv2 compat_sys_preadv2
|  535x32 pwritev2compat_sys_pwritev2
| 
| Add compat_sys_preadv64v2() and compat_sys_pwritev64v2() so that 64-bit 
offset
| is passed in one 64-bit register on x32, similar to compat_sys_preadv64()
| and compat_sys_pwritev64().
| 
| Signed-off-by: H.J. Lu 
|
| x86/syscalls: Add compat_sys_preadv64v2/compat_sys_pwritev64v2
| 
| Don't use the same syscall numbers for 2 different syscalls:
| 
|  534x32 preadv  compat_sys_preadv64
|  535x32 pwritev compat_sys_pwritev64
|  534x32 preadv2 compat_sys_preadv2
|  535x32 pwritev2compat_sys_pwritev2
| 
| Add compat_sys_preadv64v2() and compat_sys_pwritev64v2() so that 64-bit 
offset
| is passed in one 64-bit register on x32, similar to compat_sys_preadv64()
| and compat_sys_pwritev64().
| 
| Signed-off-by: H.J. Lu 
| Cc: Andy Lutomirski 
| Cc: Borislav Petkov 
| Cc: Brian Gerst 
| Cc: Christoph Hellwig 
| Cc: Denys Vlasenko 
| Cc: H. Peter Anvin 
| Cc: Josh Poimboeuf 
| Cc: Linus Torvalds 
| Cc: Peter Zijlstra 
| Cc: Thomas Gleixner 
| Link: 
http://lkml.kernel.org/r/came9roovcmf-rqfx_n1u_tu_dx1bykjtfr%3dq4-_pfvsj9bc...@mail.gmail.com
| Signed-off-by: Ingo Molnar 

Unfortunately this commit is not easily backportable as it completely
breaks the ABI. Nevertheless it should not be a big deal as we'll go to
kernel 4.8 soon. Given it is already available in experimental, I am
just going to close this bug in a few minutes. I just wanted to make
sure the issue is documented somewhere so that someone else do not spend
hours before finding the issue.

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

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

Bug#840669: [pkg-gnupg-maint] Bug#840669: Bug#840669: Beware of leftover gpg-agent processes

[Daniel Kahn Gillmor]

On Tue 2016-10-18 07:44:43 -0400, Ian Jackson wrote:
> Daniel Kahn Gillmor writes ("Re: [pkg-gnupg-maint] Bug#840669: Bug#840669: 
> Beware of leftover gpg-agent processes"):
>> On Sat 2016-10-15 11:21:29 -0400, Ian Jackson wrote:
>> > 1. gnupg1-compatible authorisation lifetime:
>> 
>> I believe this is a deliberate change in semantics from the upstream
>> GnuPG project.  In particular, authorization for the use of secret key
>> material is now the responsibility of the gpg-agent.  This is an overall
>> win, because it means that no process ever gets access to the secret key
>> in memory *except* for the gpg-agent.
>
> I think these properties about key material handling are good, but
> this is not the same question as the authorisation lifetime.  You are
> conflating two separate things.

I agree that these are distinct choices, but their implementation
details are closely linked.

>>  The gpg-agent is where these decisions are made.
>
> Actually, though, it just acts as an oracle, so it does not make any
> decisions.

It is making a decision about whether to grant use of a given key.  For
example, it's possible to ask gpg-agent to prompt the user to confirm
the use of any ssh-capable key.  (i'm unaware of how to ask it for user
confirmation for other, non-ssh keys, though)

If the current decision-making policy language isn't descriptive enough
for your goals, we should clarify what those goals are and try to figure
out a way that you can express them to the agent.  That's distinct from 

>> If you want an agent that never caches any passphrase (and therefore has
>> a one-use-per-authorization), this is an easy thing to do by adjusting
>> max-cache-ttl in gpg-agent.conf.  you can also set this dynamically with
>> gpgconf (see the --runtime option in gpgconf(1)).
>
> It sounds like this is very close to what I want for the authorisation
> lifetime qeustion (provided that it isn't racy).  Why is this not the
> default for command line users without a session-provided agent ?

I think the goal is to provide uniform behavior, regardless of whether
the agent is session-provided or otherwise, instead of having a subtle
difference between an auto-launched agent and an explicitly-initialized
agent.  Perhaps Werner can speak more to this decision, though.

 --dkg


signature.asc
Description: PGP signature

Bug#840354: src:pcre3: FTBFS on powerpc (G4 CPU)

[Matthew Vernon]

tags 840354 +help
forwarded 840354 
https://lists.exim.org/lurker/thread/20161015.160631.85f17c13.en.html

quit

On 10/10/16 21:37, Christoph Biedl wrote:


Rebuilding syslog-ng 3.7.3-3 on a PowerMac G4 failed with SIGILL,
debugging led to libpcre, and finally rebuilding src:pcre3 itself
fails with very similar symptoms:




I sent your report upstream, there's a small thread there:
https://lists.exim.org/lurker/thread/20161015.160631.85f17c13.en.html

Would you mind responding to Zoltan there? I don't think I have anything 
I can usefully add to the discussion, and it's clearly an upstream 
issue. Sorry!


Thanks,

Matthew

Bug#710696: severity of 710696 is serious, because it's a FTBFS bug

[Michael Biebl]

Am 18.10.2016 um 20:19 schrieb Santiago Vila:
> On Thu, 29 Sep 2016, Michael Biebl wrote:
> 
>> Sigh, you really like to argue [...]
> 
> No, I don't really like to argue.
> 

And I don't care anymore. I have better things to do then pointlessly
argue about nonimportant stuff.

If you think it's important to piss of maintainers instead of actually
helping addressing the bug report, feel free to go ahead.

This will be my last reply to this bug report and I will not further
look at it.



-- 
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#841239: json-simple: New version available

[Emmanuel Bourg]

Le 18/10/2016 à 22:14, Oliver Kopp a écrit :

> It seems that https://cliftonlabs.github.io/json-simple/ is the
> maintained fork of the library. It switched to 2.x to offer a clear
> distinction to the unmaintained 1.x branch. Could you update the
> library to 2.1.1?

Hi Oliver,

Is this update required for another package? Do you know if the 2.x
version is compatible with the version 1.x?

Emmanuel Bourg

Bug#841236: installation-reports: After install of Debian 8.6, Debian won't boot probably due to problem with nvidia

[Lennart Sorensen]

On Tue, Oct 18, 2016 at 08:59:35PM +0200, Remi Vanicat wrote:
> Package: installation-reports
> Severity: important
> 
> Dear Maintainer,
> 
> -- Package-specific info:

> 
> Boot method: CD
> Image version: 
> http://cdimage.debian.org/debian-cd/8.6.0/multi-arch/iso-cd/debian-8.6.0-amd64-i386-netinst.iso
> Date: 
> 
> Machine: ASUS ROG G752VM-GC006T

I believe that model ships with SSD RAID enabled, which currently makes
linux unable to see the SSD since the intel controller has hijacked the
NVMe device and hidden it behind the AHCI controller  (even though it
isn't a SATA device) in a weird mode.

You would have to turn off that mode in the BIOS (if possible, Lenovo
currently is unwilling to allow it on some of their modela for examples).

I imagine at some point intel will get around to adding support for
their crazy mode to linux but it hasn't happened so far.

It also makes backups and recovery for windows a nightmware since the
standard drivers don't see the SSD either and you have to somehow get
the intel raid drivers loaded before it shows up.

-- 
Len Sorensen

Bug#796994: New release with incorrect copyright/license

[Rémi Rampin]

Dear maintainer,

It looks like you cut out a new package for VisTrails yet didn't bother to
include the correct copyright file from the upstream release you pretend to
be packaging.

THIS IS A VIOLATION OF THE BSD LICENSE TERMS

Please consider updating your package to include the correct copyright
file, as found in upstream release, that mentions the correct copyright
holder (New York University). I will be happy to help with this task or
anything related to packaging if you would reply back.

Please acknowledge that you, the maintainer, are reading bug reports at
all, #796994 has been open for over a year. I don't see a reason to
escalate this when this is clearly a simple omission on your part, fixable
in a matter of seconds.

-- 
Rémi Rampin

Bug#841239: json-simple: New version available

[Oliver Kopp]

Source: json-simple
Severity: wishlist

It seems that https://cliftonlabs.github.io/json-simple/ is the
maintained fork of the library. It switched to 2.x to offer a clear
distinction to the unmaintained 1.x branch. Could you update the
library to 2.1.1?

Bug#840618: /etc/xdg/autostart/at-spi-dbus-bus.desktop: 90 second delay during login

[Samuel Thibault]

Hello,

Sam Morris, on Thu 13 Oct 2016 11:31:50 +0100, wrote:
> When logging into gnome-flashback there is a 90 second delay during
> which only a black screen is displayed, before nautilus/gnome-panel etc
> appear.

Which dm are you using? (lightdm, gdm, xdm, something else?)

Could you run 

ps axfu 

in a text console during that 90s delay?

Does it happen when using startx instead?

Samuel

Bug#824670: ITP: dnsdiag -- DNS Diagnostics and Performance Measurement Tools

[Antoine Beaupré]

On 2016-10-18 14:17:00, Ana C. Custura wrote:
> On Tue, Oct 18, 2016, at 03:30 PM, anarcat wrote:
>
>> I believe this removes the last blocker you have documented for
>> packaging this.
>> 
>> Good luck with the packaging, let me know if you need help!
>
> Great news, thanks! Aiming to get it done by the end of the week.
>
> If you don't mind you could check the package once I've uploaded it to
> mentors.debian.net and then you could be my sponsor for this one?

No problem, let me know.

A.

-- 
VBscript: la simplicité du C, la puissance du BASIC
- Mathieu Petit-Clair

Bug#841191: fcml: FTBFS on i386 and mips64el: fcml_internal_check segfaults

[Stephen Kitt]

Hi Daniel,

On Tue, 18 Oct 2016 12:24:23 +, Daniel Knezevic
 wrote:
> The reason of segmentation fault is a missing NULL in fcml_stf_test_case
> fctl_ti_symbols. With attached patch I was able to build ocaml-ctype
> successfully for i386 and mips64el.

Thank you so very much, this has been weighing on my mind but I hadn't taken
the time to figure it out properly. You've made things very easy for me! I
see your patch has even been merged upstream.

Regards,

Stephen


pgpK64zEB_Qj5.pgp
Description: OpenPGP digital signature

Bug#841146: diffoscope: Failure of test_superblock

[Leo Famulari]

On Tue, Oct 18, 2016 at 06:02:38PM +, Mattia Rizzolo wrote:
> > === FAILURES 
> > ===
> > ___ test_superblock 
> > 
> > 
> > differences = []
> > 
> > @skip_unless_tool_is_older_than('unsquashfs', unsquashfs_version, '4.3')
> > def test_superblock(differences):
> > expected_diff = 
> > open(data('squashfs_superblock_expected_diff')).read()
> > >   assert differences[0].unified_diff == expected_diff
> > E   IndexError: list index out of range
> > 
> > tests/comparators/test_squashfs.py:59: IndexError
> > === short test summary info 
> > 
> ...
> > SKIP [1] tests/comparators/test_squashfs.py:73: requires unsquashfs
> 
> so, it doesn't properly skip that test if unquashfs is not present,
> which is weird, since it's one thing we test in debci¹.
> 
> you said you're trying to build the released v61, not a git snapshot
> which happens to be a few commits after v61, right?

Correct, I see this test failure when building the v61 release from
PyPi.


signature.asc
Description: PGP signature

Bug#841238: acpidump: "turbostat" binary silently dropped?

[Андрей Василишин]

Package: acpica-tools
Version: 20140926-1

Hello!
Iam sorry,but there are no turbostat binary in acpica-tools package

Bug#841237: openssh-server: option to let openssh/sftp force the exact permissions on newly uploaded files

[Raphaël Droz]

Package: openssh-server
Version: 1:6.7p1-5+deb8u3
Severity: wishlist

Dear Maintainer,

Currently when setting up a shared sftp upload space between multiple
users/logins, you can force a proper umask with the -u switch.

This requires that the file at the origin has wide-permissions to start with.
In some cases, users are not skilled enough to set the permissions to be
correct (sigh).

While this could be solved via file/dir ACLs, it is also not entirely trivial
in most environments.

https://bugzilla.redhat.com/show_bug.cgi?id=1191055
https://bugzilla.mindrot.org/show_bug.cgi?id=1844
https://superuser.com/questions/1066554/



Thank you

Bug#841235: /etc/vim/vimrc: Remove some obsolete comments from /etc/vim/vimrc

[Sam Morris]

Package: vim-common
Version: 2:8.0.0022-1
Severity: wishlist
File: /etc/vim/vimrc
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Here is a patch to remove some obsolete comments from /etc/vim/vimrc. I
have removed the lines that suggest the user enable things that have
already been enabled by defaults.vim.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (550, 'testing-debug'), (550, 'testing'), (520, 
'unstable-debug'), (520, 'unstable'), (510, 'experimental-debug'), (510, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages vim-common depends on:
ii  xxd  2:8.0.0022-1

Versions of packages vim-common recommends:
ii  vim-gtk3 [vim]  2:8.0.0022-1

vim-common suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIvBAEBCAAZBQJYBnAqEhxzYW1Acm9ib3RzLm9yZy51awAKCRDSC0ICXNonuSpg
D/9dYvnvYNgP+GnUUWMr/DJQSaR2ADLwsPYa5+/VKuONMh0B068PH2fgA4BNi6gP
HABsIEKAMfkKKsQOwPZzv/tlcdwZXRMbEw124PVazcjt71iMn5iW3cyz72K1TE0K
QvJ1UMqSgHVtqq51Ozji3KfGwXC+94dVE6d56T903Q+e3HUrcjh25J09rDDx0w9p
9Mb0helETrq6TwT/Rshid7/FvHw2CWUcbQY3J8pYc1yhpfyt1hP09NaYHYBWD9qa
0l4uD+nYLX7jK0XfGDTBklaQIX+RQUft2Oxhxz5EllJSfrh99GTogp4pSHwQ1rr0
Ni/sRCqoGExeVIUdjdybZ9QD0cjtsawkmJnSm5loUKvEw2vUoJK+qXN6+Zpekt6v
UTPy3lO0zxXz67K3rIFtZUHTx7+JJmgSf0ApR5RSu38xbn38QaqYVWCzurcPoaEe
WWSt2Sbzi+zeoaiz7EeAnvJSdw4httflnqvCJJ9NXkmNapHQ/d9ahlz7F6VAgRr0
TRKUOc8NrT9+zxL59cBo1C+pNxNvYfkOgDZ6km5CvFNf4RFkd9nXYE/F2nRE2C87
YQRFn86LNwjREKs6Asxah0mzCm0KS4MaXQhO3Xsy0+s0Q8WWsYXTwGrWuG7NGHV+
qnuUaoaIEvl7f4TAySiS/oA2k1pZKMXEZ9yBGtrbV5ABQQ==
=xO5/
-END PGP SIGNATURE-
--- debian/runtime/vimrc.orig	2016-10-18 19:51:13.379015000 +0100
+++ debian/runtime/vimrc	2016-10-18 19:53:16.787015000 +0100
@@ -21,36 +21,17 @@
 " options, so any other options should be set AFTER setting 'compatible'.
 "set compatible
 
-" Vim5 and later versions support syntax highlighting. Uncommenting the next
-" line enables syntax highlighting by default.
-"syntax on
-
 " If using a dark background within the editing area and syntax highlighting
 " turn on this option as well
 "set background=dark
 
-" Uncomment the following to have Vim jump to the last position when
-" reopening a file
-"if has("autocmd")
-"  au BufReadPost * if line("'\"") > 1 && line("'\"") <= line("$") | exe "normal! g'\"" | endif
-"endif
-
-" Uncomment the following to have Vim load indentation rules and plugins
-" according to the detected filetype.
-"if has("autocmd")
-"  filetype plugin indent on
-"endif
-
 " The following are commented out as they cause vim to behave a lot
 " differently from regular Vi. They are highly recommended though.
-"set showcmd		" Show (partial) command in status line.
 "set showmatch		" Show matching brackets.
 "set ignorecase		" Do case insensitive matching
 "set smartcase		" Do smart case matching
-"set incsearch		" Incremental search
 "set autowrite		" Automatically save before commands like :next and :make
 "set hidden		" Hide buffers when they are abandoned
-"set mouse=a		" Enable mouse usage (all modes)
 
 " Source a global configuration file if available
 if filereadable("/etc/vim/vimrc.local")

Bug#841236: installation-reports: After install of Debian 8.6, Debian won't boot probably due to problem with nvidia

[Remi Vanicat]

Package: installation-reports
Severity: important

Dear Maintainer,

-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/debian-cd/8.6.0/multi-arch/iso-cd/debian-8.6.0-amd64-i386-netinst.iso
Date: 

Machine: ASUS ROG G752VM-GC006T
Partitions: 


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

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

Comments/Problems:

I've two disk on this, a SSD and a normal (sata) disk. The normal disk
is detected normally, but the SSD is not seen by the installer.

And then, after installation, Debian won't boot. Apparently the bug is
when setting the framebuffer. Installing the non-free nvidia driver fix
this.

Thanks.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u4+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux arkana 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 
(2016-09-03) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:1910] 
(rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:1901] 
(rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation 
Device [8086:1903] (rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a12f] 
(rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:201f]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Device [8086:a131] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:15.0 Signal processing controller [1180]: Intel Corporation 
Device [8086:a160] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:15.1 Signal processing controller [1180]: Intel Corporation 
Device [8086:a161] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Device 
[8086:a13a] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:17.0 RAID bus controller [0104]: Intel Corporation 82801 SATA 
Controller [RAID mode] [8086:2822] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a112] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Device [8086:a113] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:a114] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a150] 
(rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Device 
[8086:a121] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a170] 
(rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a123] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:1c60] (rev a1)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13f0]
lspci -knn: 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
lspci -knn: Subsystem: Intel Corporation Device [8086:0010]
lspci -knn: 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:200f]
lspci 

Bug#771790: Package broken

[Marcos Marado]

severity 771790 grave
thanks

I forgot about this, and have been bitten by it again, on another machine.
As a result, I suffered data loss from what was only in memory and
should be on disk.

Since this bug causes data loss, changing its severity to grave.
I'm not sure how much can I do to help solve this issue. I'm willing
to submit an nmu
(which I already did, actually, see a previous comment), if there's any sponsor.

Please deal with this soon, this is nasty, and there's no reason for
not having it fixed yet.

Thanks,
-- 
Marcos Marado

Bug#841232: marble: Does not follow symlinks

[Marcos Dione]

Package: marble
Version: 4:16.04.1-3
Severity: wishlist

Dear Maintainer,

marble has for ages disabled symlinks traversal in a great part of
the local cache code. I know for certain that developers have decided to
do so to avoid user reports related to dangling symlinks (sorry, I can't
find a reference now). This bug report is to see if the Debian
maintainers agree this is wrong. Attached you'll find a patch that
removes all the references to QDir::NoSymLinks from the code. I tested it
and it works fine now. I will keep having this patch around, but I hope
you find it useful too, so everyone else can profit from it, and I don't
have to recompile marble from time to time :)

Cheers,

-- Marcos.


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_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 marble depends on:
ii  libc6   2.24-3
ii  libgcc1 1:6.2.0-6
ii  libkf5configcore5   5.26.0-1
ii  libkf5configgui55.26.0-1
ii  libkf5configwidgets55.26.0-1
ii  libkf5coreaddons5   5.26.0-3
ii  libkf5i18n5 5.26.0-1
ii  libkf5kiowidgets5   5.26.0-1
ii  libkf5newstuff5 5.26.0-1
ii  libkf5parts55.26.0-1
ii  libkf5runner5   5.26.0-1
ii  libkf5widgetsaddons55.26.0-1
ii  libkf5xmlgui5   5.26.0-1
ii  libmarblewidget-qt5-24  4:16.04.1-3
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5dbus5 5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5network5  5.6.1+dfsg-3+b1
ii  libqt5printsupport5 5.6.1+dfsg-3+b1
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libqt5xml5  5.6.1+dfsg-3+b1
ii  libstdc++6  6.2.0-6
ii  marble-data 4:16.04.1-3
ii  marble-plugins  4:16.04.1-3

marble recommends no packages.

Versions of packages marble suggests:
pn  gosmore   
pn  monav-routing-daemon  
pn  routino   

-- no debconf information

-- 
(Not so) Random fortune:
Terrorism isn't a crime against people or property. It's a crime against
our minds, using the death of innocents and destruction of property to
make us fearful.
-- Bruce Schneier

Bug#834755: apt-cacher-ng: please make the build reproducible

[Eduard Bloch]

Control: tags 834755 +pending

Hallo,
* Eduard Bloch [Mon, Oct 17 2016, 09:12:56PM]:
> Hallo,
> * Chris Lamb [Mon, Oct 17 2016, 10:54:53AM]:
> > Dear Maintainer,
> > 
> > > Source: apt-cacher-ng
> > > Version: 0.5.1-3
> > > Tags: patch
> > 
> > There hasn't seem to be any update on this bug in 59 days, in which
> > time the Reproducible Builds effort has come on a long way. :)
> 
> *g*
> 
> > Would you consider applying this patch and uploading?
> 
> I do, I am preparing a new upstream version RSN.

Ehm, it looks like you did not look up the meaning of the other
tar parameters in the command line you patched ($TARARGS). The build has
been reproducible for a while until the translators decided to breakup
the line so the check for a new tar version started failing.

Will be fixed by more precise regexp now.

Regards,
Eduard.

Bug#841233: marble: Does not follow symlinks

[Marcos Dione]

Package: marble
Version: 4:16.04.1-3
Severity: wishlist

Dear Maintainer,

marble has for ages disabled symlinks traversal in a great part of
the local cache code. I know for certain that developers have decided to
do so to avoid user reports related to dangling symlinks (sorry, I can't
find a reference now). This bug report is to see if the Debian
maintainers agree this is wrong. Attached you'll find a patch that
removes all the references to QDir::NoSymLinks from the code. I tested it
and it works fine now. I will keep having this patch around, but I hope
you find it useful too, so everyone else can profit from it, and I don't
have to recompile marble from time to time :)

Cheers,

-- Marcos.


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_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 marble depends on:
ii  libc6   2.24-3
ii  libgcc1 1:6.2.0-6
ii  libkf5configcore5   5.26.0-1
ii  libkf5configgui55.26.0-1
ii  libkf5configwidgets55.26.0-1
ii  libkf5coreaddons5   5.26.0-3
ii  libkf5i18n5 5.26.0-1
ii  libkf5kiowidgets5   5.26.0-1
ii  libkf5newstuff5 5.26.0-1
ii  libkf5parts55.26.0-1
ii  libkf5runner5   5.26.0-1
ii  libkf5widgetsaddons55.26.0-1
ii  libkf5xmlgui5   5.26.0-1
ii  libmarblewidget-qt5-24  4:16.04.1-3
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5dbus5 5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5network5  5.6.1+dfsg-3+b1
ii  libqt5printsupport5 5.6.1+dfsg-3+b1
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libqt5xml5  5.6.1+dfsg-3+b1
ii  libstdc++6  6.2.0-6
ii  marble-data 4:16.04.1-3
ii  marble-plugins  4:16.04.1-3

marble recommends no packages.

Versions of packages marble suggests:
pn  gosmore   
pn  monav-routing-daemon  
pn  routino   

-- no debconf information

-- 
(Not so) Random fortune:
Terrorism isn't a crime against people or property. It's a crime against
our minds, using the death of innocents and destruction of property to
make us fearful.
-- Bruce Schneier
--- a/src/lib/marble/DataMigration.cpp
+++ b/src/lib/marble/DataMigration.cpp
@@ -130,10 +130,8 @@
 QDir sourceDir( sourceDirPath );
 // Creating child file/dir lists.
 QStringList files = sourceDir.entryList( QDir::Files
- | QDir::NoSymLinks
  | QDir::NoDotAndDotDot );
 QStringList childDirs = sourceDir.entryList( QDir::Dirs
- | QDir::NoSymLinks
  | 
QDir::NoDotAndDotDot );
 int childSliceSize = 0;
 if( !childDirs.isEmpty() ) {
--- a/src/lib/marble/FileStoragePolicy.cpp
+++ b/src/lib/marble/FileStoragePolicy.cpp
@@ -111,7 +111,7 @@
 continue;
 }
 
-QDirIterator itTile( tileDirectory, QDir::Files | 
QDir::NoSymLinks, QDirIterator::Subdirectories );
+QDirIterator itTile( tileDirectory, QDir::Files, 
QDirIterator::Subdirectories );
 while (itTile.hasNext()) {
 itTile.next();
 QString filePath = itTile.filePath();
--- a/src/lib/marble/MapThemeManager.cpp
+++ b/src/lib/marble/MapThemeManager.cpp
@@ -273,7 +273,6 @@
 
 QStringList mapPaths = paths.entryList( QStringList( "*" ),
 QDir::AllDirs
-| QDir::NoSymLinks
 | QDir::NoDotAndDotDot );
 QStringList mapDirs;
 
@@ -282,7 +281,6 @@
 QStringList themeMapPaths = themeDir.entryList(
  QStringList( "*" ),
  QDir::AllDirs |
- QDir::NoSymLinks |
  QDir::NoDotAndDotDot );
 for ( int theme = 0; theme < themeMapPaths.size(); ++theme ) {
 mapDirs << mapPathName + '/' + mapPaths.at( planet ) + '/'
@@ -296,7 +294,7 @@
 QString themeDir = it.next() + '/';
 QString themeDirName = QDir( themeDir ).path().section( '/', -2, -1 );
 QStringList tmp = QDir( themeDir ).entryList( QStringList( "*.dgml" ),
-  QDir::Files | 
QDir::NoSymLinks );
+  QDir::Files );
 if ( !tmp.isEmpty() ) {
 

Bug#797965: bs1770gain somehow "destroys" gapless playback on (at least) lame encoded MP3s

[Andreas Cadhalpun]

Control: tags -1 fixed-upstream

Hi Cris,

On 29.06.2016 21:56, Christoph Anton Mitterer wrote:
> Andreas, anything new on this? What happened to your proposed patch?

Jon Toohill managed to write a proper patch for this and it is now
fixed upstream [1].

Best regards,
Andreas


1: 
https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=3b02f6dd7be880fd6c1bcaf2fd0c1314dcee7aa6

Bug#710696: severity of 710696 is serious, because it's a FTBFS bug

[Santiago Vila]

On Thu, 29 Sep 2016, Michael Biebl wrote:

> Sigh, you really like to argue [...]

No, I don't really like to argue.

I was trying to be nice by explaining things with detail instead of
moving the discussion to -devel, the technical committee or the
release managers.

If you just "don't like to argue", no problem, I will ask release
managers to override your decision and everybody will be happy.


As I have already explained, we don't wait for bugs to happen in
buildd.debian.org before making them of serious severity.

Examples here:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?include=subject%3AFTBFS;submitter=lamby%40debian.org

or here:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?include=subject%3AFTBFS;submitter=lucas%40debian.org

or even here:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?include=subject%3AFTBFS;submitter=sanvila%40debian.org

Just count how many of those bugs have a reference to
buildd.debian.org and how many of them have a reference to our own
autobuilders (including the ones from reproducible builds).

If any of us had to wait for FTBFS bugs to happen in
buildd.debian.org, we would probably not file any bugs at all.

(Not to mention nobody would file bugs about Arch:all packages,
as many maintainers still do not upload in source-only form).

So what you propose contradicts common practice *completely*.

Instead, we file as "serious" any FTBFS which happens in a policy
compliant autobuilder, i.e. any autobuilder which builds packages in
the standard way (i.e. dpkg-buildpackage + fakeroot, not the weird
example you tried to put as an example that "whatever happens in
buildd.debian.org determines RC-ness").


Since you finally forwarded this upstream, I infer that you finally
managed to reproduce this, at least once.

Therefore, I ask again:

Can we already make this bug serious (as it should be) or do you
really need to check that my autobuilder is not misconfigured?


> instead of actually addressing the issue

The issue will be properly "addressed" when everybody can autobuild
this package without failures, as explained by release policy. Hiding
this problem by downgrading the severity is not "addressing the issue",
and it's also against the definition of sarge-ignore.

Thanks.

Bug#824670: ITP: dnsdiag -- DNS Diagnostics and Performance Measurement Tools

[Ana C. Custura]

On Tue, Oct 18, 2016, at 03:30 PM, anarcat wrote:

> I believe this removes the last blocker you have documented for
> packaging this.
> 
> Good luck with the packaging, let me know if you need help!

Great news, thanks! Aiming to get it done by the end of the week.

If you don't mind you could check the package once I've uploaded it to
mentors.debian.net and then you could be my sponsor for this one?

Regards,
Ana

Bug#841073: python-ruffus: Needs 18 GB of RAM to build

[Leo Goodstadt 顧維斌]

Dear Andreas,
I have no idea why this should be the case. Will try it on my end and see
what is happening!
Thanks
Leo

On 18 October 2016 at 11:17, Andreas Tille  wrote:

> Hi Leo,
>
> I've received a bug report which claims that ruffus probably consumes a
> lot of memory in its test suite.  While I do not really like to cut from
> the testing quality I wonder whether you are aware of this issue and
> could find a way to reduce the memory consumption of the test suite.
>
> Kind regards
>
>   Andreas.
>
> On Mon, Oct 17, 2016 at 02:23:50PM +0200, Santiago Vila wrote:
> > Package: src:python-ruffus
> > Version: 2.6.3+dfsg-4
> > Severity: wishlist
> >
> > Hello Andreas and debian-med.
> >
> > I noticed that this package requires 18 GB of RAM to build
> > (as measured by Committed_AS in /proc/meminfo).
> >
> > In theory, there is no limit at all regarding how much RAM a package
> > may need to be built (there is absolutely no policy about that).
> > [ This is the reason why I'm reporting this as wishlist ].
> >
> > In practice, packages like this one represent a real challenge.
> >
> > To put things in perspective: I routinely try to build all source
> > packages generating at least one "Arch: all" binary package.
> >
> > I have collected memory usage for 16500 of those, and currently I can
> > build all of them but this one and "axiom" with only 8 GB of RAM.
> >
> > This makes python-ruffus to be a real "outlier" (in statistical terms).
> >
> > Would be possible to change the build system slightly so that this big
> > amount of memory required to build is reduced significantly?
> > (say, reducing it to a half or a quarter).
> >
> > Note: I think it's not the build itself what uses so much memory but
> > the tests that are performed at the end.
> >
> > Thanks.
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> debian-med-packaging
> >
>
> --
> http://fam-tille.de
>

Bug#841100: dgit: gbp-build fails when on master branch

[Ian Jackson]

Control: tags -1 + pending

Sean Whitton writes ("Bug#841100: dgit: gbp-build fails when on master branch"):
> On Mon, Oct 17, 2016 at 06:13:37PM +0100, Ian Jackson wrote:
> > Sean Whitton writes ("Bug#841100: dgit: gbp-build fails when on master 
> > branch"):
> > > dgit passes --git-debian-branch=dgit/sid to gbp-buildpackage(1), which
> > > causes the build to fail when on a branch called 'master'.  Since
> > > 'master' is the maintainer view, it should be possible to build the
> > > package from it.
> > 
> > I think passing that option is probably a mistake.  Should I just
> > drop it ?
> 
> I think you can just drop it, yes.  The user should be able to set a
> Debian branch of their choice in debian/gbp.conf, but you're
> unconditionally overriding that.

Right.  I won't do an upload for this change right away, but it's in
my master branch.

Thanks,
Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#841109: (no subject)

[Lev Lamberov]

There is some activity in the GNU Emacs repository (but not on the
webpage of prolog-el package). As I can see there were 26 commits to
prolog.el from the beginning of 2014 [1]. When prolog.el was integrated
to the mainline GNU Emacs it had version 1.22. Seems no one cared about
bumping version of it in the GNU Emacs repository, so Emacs will not
object to install in fact older prolog.el from [2], because it has
version 1.25 (still released in 2013). It is misleading for Debian users.


[1] http://git.savannah.gnu.org/cgit/emacs.git/log/lisp/progmodes/prolog.el
[2] https://bruda.ca/emacs/prolog_mode_for_emacs



signature.asc
Description: OpenPGP digital signature

Bug#841143: [pkg-gnupg-maint] Bug#841143: Suspected race in gpg1 to gpg2 conversion or agent startup

[Ian Jackson]

Ian Jackson writes ("Re: [pkg-gnupg-maint] Bug#841143: Suspected race in gpg1 
to gpg2   conversion or agent startup"):
> This makes it somewhat surprising that it should fail occasionally.
> Each of the individual tests is largely single-threaded.

Also, watching tests by hand shows gpg pausing for a noticeable time
(~500ms?) even on my extremely fast laptop, perhaps when converting
the test gpg1 keys etc. to gpg2 keys etc.

If I do this conversion once in the source, will the result be useable
by gpg1 ?  (Since I want the test suite to still work on earlier
versions of Debian.)

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#834622: Patch at TDF

[Rene Engelhard]

tag 834622 + pending
thanks

On Tue, Oct 18, 2016 at 03:56:29PM +0200, Frédéric MASSOT wrote:
> Hi,
> 
> According to the bug report on TDF Caolan McNamara fixed the bug in
> master

so for 5.3.

Thanks for the info.

> will the backport to version 5.2.

Will wait for it, and if it doesn't land in 5.2.4 I guess we need to backport
it...

Regards,

Rene

Bug#841146: diffoscope: Failure of test_superblock

[Mattia Rizzolo]

control: found -1 61

On Tue, Oct 18, 2016 at 10:28:33AM -0400, Leo Famulari wrote:
> ...
> tests/comparators/test_squashfs.py::test_identification PASSED
> tests/comparators/test_squashfs.py::test_no_differences PASSED
> tests/comparators/test_squashfs.py::test_no_warnings PASSED
> tests/comparators/test_squashfs.py::test_superblock FAILED
> tests/comparators/test_squashfs.py::test_symlink SKIPPED
> tests/comparators/test_squashfs.py::test_compressed_files SKIPPED
> tests/comparators/test_squashfs.py::test_compare_non_existing SKIPPED
...
> === FAILURES 
> ===
> ___ test_superblock 
> 
> 
> differences = []
> 
> @skip_unless_tool_is_older_than('unsquashfs', unsquashfs_version, '4.3')
> def test_superblock(differences):
> expected_diff = open(data('squashfs_superblock_expected_diff')).read()
> >   assert differences[0].unified_diff == expected_diff
> E   IndexError: list index out of range
> 
> tests/comparators/test_squashfs.py:59: IndexError
> === short test summary info 
> 
...
> SKIP [1] tests/comparators/test_squashfs.py:73: requires unsquashfs

so, it doesn't properly skip that test if unquashfs is not present,
which is weird, since it's one thing we test in debci¹.

you said you're trying to build the released v61, not a git snapshot
which happens to be a few commits after v61, right?

¹ https://ci.debian.net/packages/d/diffoscope/
-- 
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#841222: Acknowledgement (RFS: patat)

[Félix Sipma]

I've updated patat to 0.3.0.0-1, see

With dget:

dget -x 
https://mentors.debian.net/debian/pool/main/p/patat/patat_0.3.0.0-1.dsc

With gbp:

gbp clone --pristine-tar https://git.gueux.org/patat.git
cd patat
gbp buildpackage


signature.asc
Description: PGP signature

Bug#841231: postfix: missing nameserver line in /var/spool/postfix/etc/resolv.conf

[Andrea Janna]

Package: postfix
Version: 3.1.0-5+b1
Severity: normal

Dear Maintainer,
in my /var/spool/postfix/etc/resolv.conf file "nameserver" line is missing, so 
Postfix cannot send emails and reports "delivery temporarily suspended: Host or 
domain name not found. Name service error ..." errors in mail queue.

/etc/resolv.conf content is:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.0.11.1

while /var/spool/postfix/etc/resolv.conf content is:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

Relevant /etc/network/interfaces content is:
auto br_adm
iface br_adm inet static
address 10.0.11.19
netmask 255.255.248.0
gateway 10.0.11.1
dns-nameservers 10.0.11.1
bridge_ports enp1s0f0
bridge_fd 0

If I restart Postfix using the command "systemctl restart postfix", 
/var/spool/postfix/etc/resolv.conf file get in sync with /etc/resolv.conf and 
Postfix starts working normally.
But after a system reboot "nameserver" line always disappears from 
/var/spool/postfix/etc/resolv.conf file.

If I modify the script /usr/lib/postfix/configure-instance.sh adding a delay 
everything works fine, /var/spool/postfix/etc/resolv.conf stays in sync with 
/etc/resolv.conf even after a reboot.
To add a delay I added the command "sleep 5" before the line 
"FILES="etc/localtime etc/services etc/resolv.conf etc/hosts \".

I know I could remove resolvconf package and use a static /etc/resolv.conf but 
I think this bug could affect other users that need resolvconf.


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

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

Versions of packages postfix depends on:
ii  adduser3.115
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.59
ii  dpkg   1.18.10
ii  init-system-helpers1.45
ii  libc6  2.24-3
ii  libdb5.3   5.3.28-12
ii  libicu57   57.1-4
ii  libsasl2-2 2.1.26.dfsg1-15
ii  libsqlite3-0   3.14.2-1+b1
ii  libssl1.0.21.0.2j-1
ii  lsb-base   9.20160629
ii  netbase5.3
ii  ssl-cert   1.0.38

Versions of packages postfix recommends:
ii  python3  3.5.1-4

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20160123cvs-3
pn  dovecot-common   
ii  libsasl2-modules 2.1.26.dfsg1-15
pn  postfix-cdb  
pn  postfix-doc  
pn  postfix-ldap 
pn  postfix-mysql
pn  postfix-pcre 
pn  postfix-pgsql
pn  procmail 
ii  resolvconf   1.79
pn  sasl2-bin
pn  ufw  

-- debconf information excluded

Bug#841143: [pkg-gnupg-maint] Bug#841143: Suspected race in gpg1 to gpg2 conversion or agent startup

[Ian Jackson]

Ian Jackson writes ("Re: [pkg-gnupg-maint] Bug#841143: Suspected race in gpg1 
to gpg2   conversion or agent startup"):
> Daniel Kahn Gillmor writes ("Re: [pkg-gnupg-maint] Bug#841143: Suspected race 
> in gpg1 to gpg2 conversion or agent startup"):
> > Is it possible to create this homedir with mode 0700 ?  aiui, gpg-agent
> > doesn't want to create its sockets in a directory that other users have
> > read and write access to.
...
> I can try if doing that works around the problem, but I guess even if
> it does there's a real bug here ?  I'm happy to try to help find it.

I tried this and it doesn't seem to have made any difference.
(I haven't done enough tests to know the failure probability
before-and-after but I have seen a failure after.)

I saw in netstat that there were a lot of programs using AF_UNIX
sockets in the tests' temporary GNUPGHOME directories.

This makes it somewhat surprising that it should fail occasionally.
Each of the individual tests is largely single-threaded.

I also tried it with unsetting GPG_AGENT_INFO, as well, and that made
no difference.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#841230: nginx: PHP 7 integration

[Olaf van der Spek]

Package: nginx
Severity: wishlist

Dear Maintainer,

> #   fastcgi_pass unix:/var/run/php5-fpm.sock;

Could you use PHP 7 in testing?
And move it above the TCP line..

> fastcgi_pass 127.0.0.1:9000;

Is the TCP line even needed / useful? It'd be simpler without it.

Gr,

Olaf

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

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

Bug#840849: [pkg-gnupg-maint] Bug#840849: gnupg2: pubkeyring and secretkey unusable

[Mechtilde]

Hello Daniel,

thanks for your help at IRC to solve the problem with my secret key.

I still have problems with my public keyring. There aren't the
information of trust. I only see the Name and E-Mail addresses from the
mails I get since last Friday.

What is the best solution to recover? Should I copy the file "trustdb"
from the machine with Debian Stable?

Kind regards

Mechtilde

Am 18.10.2016 um 07:11 schrieb Daniel Kahn Gillmor:
> Hi Mechtilde--
> 
> On Sat 2016-10-15 09:54:00 -0400, mechtilde wrote:
>> since last update on Friday 2016-10-14 I can't use my key(ring). As I try to
>> list the keys with 'gpg --list-public-keys' as using it with enigmail fails.
>>
>> So neither I can read crypted mails nor I can send cryted and/or signed mails
>> from this machine.
>>
>> The keyfiles themselves are the same as at an stable machine where gnupg and
>> enigmail works.
> 
> I think we managed to resolve this on IRC -- is this the same problem
> that was resolved with a second "gpg --import ~/.gnupg/secring.gpg" ?
> If so, do you have any more info about the differences between
> private-keys-v1.d before and after the import?
> 
>   --dkg
> 




signature.asc
Description: OpenPGP digital signature