date:20160519

Package: icedove-l10n-de
Version: 1:38.0.1-1
Severity: important
Tags: l10n

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

icedove-l10n-de recommends either myspell or hunspell dictionaries, but
lists myspell ones first, which causes those to be tried first.

As I understand it, hunspell is the successor to myspell (e.g. has
better support for combined words which is common in german).  Despite
the dictionary _format_ being superior, some myspell dictionary _data_
is of better quality (e.g. the danish one has far more words, and
licensing blocks them from being reused in the hunspell project), but
german data seems to be from same source for both hunspell and myspell
so should not be a concern here:

Please list hunspell packages before myspell packages in Recommends.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXPW/rAAoJECx8MUbBoAEhUuAP+QHF/yd8QhxR35mCszkNeaRC
uxSX1qrCIvbLi83OqGcqI5c/uytrt6UY0/Af6uQssX3unhLg9yu4txhGqyRxSS6E
3K4bKAkM/CVLWvz/r5fHDkhr+StidSba/VLxkny6nApFixcbsY4Z2Hogko7p4ZSH
pu62EaN+GiYFKRKUVHaE3C7ilzNmsgVZd6660Cj86O7Ee3KPy5xcwqdmUERb/B0l
7IiOpJgnU12wtVHW4RfKaOhg25IE5/I2H4SdlGujh8IazeVgi7u8T4DPjc2QB7jL
/GoY7cwsG3b7LbN1iTXcQ9FncZ348z8txXuFIaVLvVSHOueoHDGpV0yGyIj9KqpO
uHnPSF++P+/IAlwlUekVrrFOK6M3Msmpm89h2B+8wZBvdbICrQKBMGkBFQk8UdwE
9K5OFWwyQ5N3M2Z9Nt4MxYR/1WQxTNKrOouQtN/j0RmK2DlpqgPUvHROuA+q39ov
tCxqaUhFWUN40j+hZ3s43HIkQwJ9k+XVEQPgWQ2GP1oX0sGmEHLqnA0mWEK4NVl5
dJGWGIkt2jJq+RlXOODdmr62IvQTdKahVG/MhCOldRcyuVjSSMCs57HK1alfARd2
gzJwRjBh+eh9/OFgzBMFGGtOLF35m9NvgYBMZlZ7Y3MAVv1Pds1H5yX3tt7MuGbe
tYT4HcqxTUhcCsRC2XdJ
=AYXE
-END PGP SIGNATURE-

Bug#804079: Kernel panic on Xen virtualisation in Debian on 4.5.0-0.bpo.1-amd64 too

2016-05-19 Thread Ingo Jürgensmann

Hi!

In an effort to avoid crashes due to this bug, I installed 4.5.0-0.bpo.1-amd64
last week. The server ran in the last week quite well with activated IPv6,
but today it crashed two times within 30 mins. 

Please find attached the syslog output send out via netconsole... 


-- 
Ciao...//  Fon: 0381-2744150 
  Ingo   \X/   http://blog.windfluechter.net
Please don't share this address with Facebook or Google!
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
May 19 09:07:45 31.172.31.251 [300350.696476] BUG: unable to handle kernel 
May 19 09:07:45 31.172.31.251  at 880279ba40e6
May 19 09:07:45 31.172.31.251 [300350.696525] IP:
May 19 09:07:45 31.172.31.251  [] 
ndisc_send_redirect+0x44c/0x4d0
May 19 09:07:45 31.172.31.251 [300350.696557] PGD 1a0d067 
May 19 09:07:45 31.172.31.251  
May 19 09:07:45 31.172.31.251 [300350.696587] Oops:  [#1] 
May 19 09:07:45 31.172.31.251  
May 19 09:07:45 31.172.31.251 [300350.696605] Modules linked in:
May 19 09:07:45 31.172.31.251  xt_policy(E)
May 19 09:07:45 31.172.31.251  authenc(E)
May 19 09:07:45 31.172.31.251  echainiv(E)
May 19 09:07:45 31.172.31.251  xfrm6_mode_tunnel(E)
May 19 09:07:45 31.172.31.251  xfrm4_mode_tunnel(E)
May 19 09:07:45 31.172.31.251  xt_physdev(E)
May 19 09:07:45 31.172.31.251  br_netfilter(E)
May 19 09:07:45 31.172.31.251  xen_netback(E)
May 19 09:07:45 31.172.31.251  tun(E)
May 19 09:07:45 31.172.31.251  xen_blkback(E)
May 19 09:07:45 31.172.31.251  xt_multiport(E)
May 19 09:07:45 31.172.31.251  xen_gntdev(E)
May 19 09:07:45 31.172.31.251  xen_evtchn(E)
May 19 09:07:45 31.172.31.251  xenfs(E)
May 19 09:07:45 31.172.31.251  xfrm_user(E)
May 19 09:07:45 31.172.31.251  xen_privcmd(E)
May 19 09:07:45 31.172.31.251  xfrm4_tunnel(E)
May 19 09:07:45 31.172.31.251  tunnel4(E)
May 19 09:07:45 31.172.31.251  ipcomp(E)
May 19 09:07:45 31.172.31.251  xfrm_ipcomp(E)
May 19 09:07:45 31.172.31.251  esp4(E)
May 19 09:07:45 31.172.31.251  ah4(E)
May 19 09:07:45 31.172.31.251  af_key(E)
May 19 09:07:45 31.172.31.251  xfrm_algo(E)
May 19 09:07:45 31.172.31.251  ipmi_poweroff(E)
May 19 09:07:45 31.172.31.251  video(E)
May 19 09:07:45 31.172.31.251  thermal(E)
May 19 09:07:45 31.172.31.251  fan(E)
May 19 09:07:45 31.172.31.251  ac(E)
May 19 09:07:45 31.172.31.251  battery(E)
May 19 09:07:45 31.172.31.251  ip6t_REJECT(E)
May 19 09:07:45 31.172.31.251  nf_reject_ipv6(E)
May 19 09:07:45 31.172.31.251  ip6table_filter(E)
May 19 09:07:45 31.172.31.251  ip6_tables(E)
May 19 09:07:45 31.172.31.251  bridge(E)
May 19 09:07:45 31.172.31.251  stp(E)
May 19 09:07:45 31.172.31.251  llc(E)
May 19 09:07:45 31.172.31.251  ipt_REJECT(E)
May 19 09:07:45 31.172.31.251  nf_reject_ipv4(E)
May 19 09:07:45 31.172.31.251  xt_tcpudp(E)
May 19 09:07:45 31.172.31.251  iptable_filter(E)
May 19 09:07:45 31.172.31.251  ip_tables(E)
May 19 09:07:45 31.172.31.251  x_tables(E)
May 19 09:07:45 31.172.31.251  ext4(E)
May 19 09:07:45 31.172.31.251  crc16(E)
May 19 09:07:45 31.172.31.251  mbcache(E)
May 19 09:07:45 31.172.31.251  jbd2(E)
May 19 09:07:45 31.172.31.251  crc32c_generic(E)
May 19 09:07:45 31.172.31.251  ipmi_devintf(E)
May 19 09:07:45 31.172.31.251  ipmi_watchdog(E)
May 19 09:07:45 31.172.31.251  w83627ehf(E)
May 19 09:07:45 31.172.31.251  hwmon_vid(E)
May 19 09:07:45 31.172.31.251  nf_conntrack_ipv4(E)
May 19 09:07:45 31.172.31.251  nf_defrag_ipv4(E)
May 19 09:07:45 31.172.31.251  nf_conntrack(E)
May 19 09:07:45 31.172.31.251  loop(E)
May 19 09:07:45 31.172.31.251  fuse(E)
May 19 09:07:45 31.172.31.251  x86_pkg_temp_thermal(E)
May 19 09:07:45 31.172.31.251  intel_powerclamp(E)
May 19 09:07:45 31.172.31.251  coretemp(E)
May 19 09:07:45 31.172.31.251  crct10dif_pclmul(E)
May 19 09:07:45 31.172.31.251  crc32_pclmul(E)
May 19 09:07:45 31.172.31.251  ghash_clmulni_intel(E)
May 19 09:07:45 31.172.31.251  hmac(E)
May 19 09:07:45 31.172.31.251  drbg(E)
May 19 09:07:45 31.172.31.251  ansi_cprng(E)
May 19 09:07:45 31.172.31.251  mgag200(E)
May 19 09:07:45 31.172.31.251  ttm(E)
May 19 09:07:45 31.172.31.251  joydev(E)
May 19 09:07:45 31.172.31.251  evdev(E)
May 19 09:07:45 31.172.31.251  pcspkr(E)
May 19 09:07:45 31.172.31.251  drm_kms_helper(E)
May 19 09:07:45 31.172.31.251  drm(E)
May 19 09:07:45 31.172.31.251  aesni_intel(E)
May 19 09:07:45 31.172.31.251  aes_x86_64(E)
May 19 09:07:45 31.172.31.251  lrw(E)
May 19 09:07:45 31.172.31.251  gf128mul(E)
May 19 09:07:45 31.172.31.251  glue_helper(E)
May 19 09:07:45 31.172.31.251  ablk_helper(E)
May 19 09:07:45 31.172.31.251  cryptd(E)
May 19 09:07:45 31.172.31.251  iTCO_wdt(E)
May 19 09:07:45 31.172.31.251  iTCO_vendor_support(E)
May 19 09:07:45 31.172.31.251  sb_edac(E)
May 19 09:07:45 31.172.31.251  edac_core(E)
May 19 09:07:45 31.172.31.251  8250_fintek(E)
May 19 09:07:45 31.172.31.251  i2c_i801(E)
May 19 09:07:45 31.172.31.251  wmi(E)
May 19 09:07:45 31.172.31.251  ipmi_si(E)
May 19 09:07:45 31.172.31.251  ipmi_msghandler(E)
May 19 09:07:45 31.172.31.251  tpm_tis(E)
May 19 09:07:45 31.172.31.251  tpm(E)

Bug#824719: swh-lv2 : new upstream release

2016-05-19 Thread trebmuh


The debian/watch will need to be updated.

Bug#824722: icedove-l10n-de: should favor hunspell dictionaries over myspell ones

Quoting Jonas Smedegaard (2016-05-19 09:49:02)
> Severity: important

Sorry, the high severity is possibly unreasonable: I found this issue 
when chasing why "apt install parl-desktop-eu" fails. I suspect this bug 
is related but have not found strong proof of that.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#796476: ftp.debian.org: valid-until for stable

2016-05-19 Thread Julien Cristau

On Sat, Aug 22, 2015 at 01:28:22 +0200, Raphael Geissert wrote:

> Package: ftp.debian.org
> Tags: security
> X-Debbugs-CC: debian-rele...@lists.debian.org
> 
> Hi,
> 
> Nowadays the Release files for the *stable releases do not have a
> Valid-Until field.
> >From a security POV, this could allow a replay attack to be performed
> on the main stable repositories, which could prevent a user from
> getting some security updates.
> 
> Would it be possible to have such a valid-until field with a duration
> of, say, four months?
> Given the trend of doing point updates every few months, the date
> could be renewed only at point release time.
> 
> Release team: would that be ok for you?
> 
I think it would have to be 6 months, at which point I don't see that it
buys you much in the way of security, and it breaks archive.debian.org
further.  So I'm not wild about that idea.

Cheers,
Julien

Bug#824706: RM: pepperflashplugin-nonfree [i386] -- RoQA; ANAIS

2016-05-19 Thread Gianfranco Costamagna

Hi ftpmasters

>you could please remove i386 from unstable.

>I'm not aware of any reverse dependencies.


yes please.

Gianfranco

Bug#800654: patch ready?

2016-05-19 Thread Holger Levsen

Hi Wolfgang,

I'm slightly surprised to "only" find a patch in the BTS (hurra
actually!), but not in git. Was that because you weren't that confident
in commiting to git master at that time or do you think there are any
issues with that patch?

Or, to rephrase in a more relevant way: is the patch from #800654 ready?
If so, could you please commit it to the master branch of d-e-config?!

Thanks!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#824723: rhythmbox: after one minute skips the song

2016-05-19 Thread Lawrence Nuyts

Package: rhythmbox
Version: 3.1-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



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

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

Versions of packages rhythmbox depends on:
ii  dbus1.8.20-0+deb8u1
ii  gnome-icon-theme3.12.0-1
ii  gstreamer1.0-plugins-base   1.4.4-2
ii  gstreamer1.0-plugins-good   1.4.4-2
ii  gstreamer1.0-x  1.4.4-2
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-18+deb8u4
ii  libcairo-gobject2   1.14.0-2.1+deb8u1
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u4
ii  libgirepository-1.0-1   1.42.0-2.2
ii  libglib2.0-02.42.1-1+b1
ii  libgstreamer-plugins-base1.0-0  1.4.4-2
ii  libgstreamer1.0-0   1.4.4-2
ii  libgtk-3-0  3.14.5-1+deb8u1
ii  libgudev-1.0-0  215-17+deb8u4
ii  libjavascriptcoregtk-3.0-0  2.4.9-1~deb8u1
ii  libjson-glib-1.0-0  1.0.2-1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libpeas-1.0-0   1.12.1-2
ii  librhythmbox-core8  3.1-1
ii  libsoup2.4-12.48.0-1
ii  libtdb1 1.3.6-0+deb8u1
ii  libtotem-plparser18 3.10.3-1
ii  libwebkitgtk-3.0-0  2.4.9-1~deb8u1
ii  libx11-62:1.6.2-3
ii  libxml2 2.9.1+dfsg1-5+deb8u1
ii  media-player-info   22-2
ii  rhythmbox-data  3.1-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages rhythmbox recommends:
ii  avahi-daemon0.6.31-5
ii  cinnamon [notification-daemon]  2.2.16-5
ii  gstreamer1.0-plugins-ugly   1.4.4-2+b1
ii  gstreamer1.0-pulseaudio 1.4.4-2
ii  gvfs-backends   1.22.2-1
ii  rhythmbox-plugins   3.1-1
ii  yelp3.14.1-1

Versions of packages rhythmbox suggests:
pn  gnome-codec-install  
ii  gnome-control-center 1:3.14.2-3
ii  gstreamer1.0-plugins-bad 1.4.4-2.1+b1
ii  rhythmbox-plugin-cdrecorder  3.1-1

-- no debconf information

Bug#821532: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

2016-05-19 Thread Ondřej Surý

The code is postinst is correct. This should switch to prefork when
a2query -M returns anything else then prefork or itk:

mpm=$(a2query -M)
case "$(a2query -M)" in
prefork|itk) return 0;;
*) if apache2_switch_mpm prefork; then return 0; fi;;
esac

Could you check your apt.log for:

ERROR: $PHP_MODULE module already enabled, not enabling PHP
@PHP_VERSION@

or

ERROR: Could not switch to prefork MPM, not enabling PHP @PHP_VERSION@

?

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Thu, May 19, 2016, at 04:47, Chris Knadle wrote:
> I have a patch to switch mlmmj to use PHP 7.0 instead of PHP 5 (that
> change
> is trivial -- literally php5 -> php), but I'm running into a snag testing
> the resulting binary packages: trying to load Apache2 with PHP 7.0 fails
> to
> start with the error message:
> 
>   "Apache is running as threaded MPM, but your PHP module is not compiled
>to be threadsafe.  You need to recompile PHP."
> 
> and looking at the README.Debian.gz for libapache2-mod-php7.0, the
> document
> only discusses PHP 5.  :-/  I'm having a look at the php7.0 source
> package... libapache2-mod-php.postinst.extra seems to test for mpm but
> I'm
> suspecting that this needs tweaking for how Apache2 is currently packaged
> in
> Sid.  ('a2query -M' returns 'event' which is not a case that's being
> looked
> for, and Apache2 isn't split into mpm/prefork packages anymore.)
> 
>-- Chris
> 
> -- 
> Chris Knadle
> chris.kna...@coredump.us
> 
> 
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

Bug#824657: libpam-abl: Fatal system lockout with libpam-abl installed

2016-05-19 Thread Alex Mestiashvili

Thank you for the report! the upload of the fixed version is in progress.

Best regards,
Alex

Bug#824724: ninja-build: Please package the new upstream release (1.7.1)

2016-05-19 Thread Sylvestre Ledru

Package: ninja-build
Version: 1.6.0-1
Severity: wishlist

Hello,

The title says all. It would be great to have ninja 1.7.1 in Debian!

Thanks,
Sylvestre

Bug#824683: [PKG-Openstack-devel] Bug#824683: keystone: CVE-2016-4911: Incorrect Audit IDs in Keystone Fernet Tokens can result in revocation bypass

2016-05-19 Thread Thomas Goirand

On 05/19/2016 06:18 AM, Salvatore Bonaccorso wrote:
> Hi Thomas,
> 
> On Thu, May 19, 2016 at 12:21:28AM +0200, Thomas Goirand wrote:
>> On 05/18/2016 06:55 PM, Salvatore Bonaccorso wrote:
>>> Source: keystone
>>> Version: 2:9.0.0-1
>>> Severity: grave
>>> Tags: security patch upstream
>>>
>>> Hi,
>>>
>>> the following vulnerability was published for keystone.
>>>
>>> CVE-2016-4911[0]:
>>> Incorrect Audit IDs in Keystone Fernet Tokens can result in revocation 
>>> bypass
>>>
>>> If you fix the vulnerability please also make sure to include the
>>> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>>>
>>> For further information see:
>>>
>>> [0] https://security-tracker.debian.org/tracker/CVE-2016-4911
>>> [1] https://bugs.launchpad.net/keystone/+bug/1577558
>>>
>>> Regards,
>>> Salvatore
>>
>> Hi Salvatore,
>>
>> It is my view that this bug doesn't deserve Severity: grave, as Fernet
>> Tokens aren't the default in Keystone (it defaults to UUID tokens, and
>> Fernet Tokens are a very new thing).
>>
>> Your thoughts?
> 
> Thanks for your feedback. Wanted to be rather safe than sorry.
> 
>> Anyway, Keystone in Stable isn't affected (it doesn't have the feature),
>> and never the less, I'll update the package in Sid/Testing.
> 
> I can confirm that it should only affect 9.0.0, so sid. Could you
> upload the isolated fix? I will then update the tracker information
> once it enters the archive.
> 
> Thanks!
> 
> Regards,
> Salvatore

Hi Salvatore,

I have uploaded Keystone 9.0.0-2 with the upstream patch. Upstream also
confirmed that previous version, currently in jessie-backports, isn't
affected by this issue. So, once Keystone migrates to Testing, we're
good to go.

Cheers,

Thomas Goirand (zigo)




signature.asc
Description: OpenPGP digital signature

Bug#800654: patch ready?

2016-05-19 Thread Holger Levsen

Hi,

this patch is only needed for the jessie version as in stretch squid3
has become squid again…

(while in jessie squid was dropped and squid3 was the only available
squid…)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#815409: qemu-img still segfaults

2016-05-19 Thread Hilko Bengen

Control: found -1 1:2.6+dfsg-1

I just tried with the latest qemu version, the problem still persists:

,
| (sid_mips-dchroot)bengen@minkus:~$ qemu-img --version
| qemu-img version 2.6.0 (Debian 1:2.6+dfsg-1), Copyright (c) 2004-2008 Fabrice 
Bellard
| (sid_mips-dchroot)bengen@minkus:~$ qemu-img create -f qcow2 
blank-disk-1s.qcow2 10
| Formatting 'blank-disk-1s.qcow2', fmt=qcow2 size=10 encryption=off 
cluster_size=65536 lazy_refcounts=off refcount_bits=16
| Segmentation fault
`

Cheers,
-Hilko

Bug#824725: libffcall1-dev: arch-dependent files in "Multi-Arch: same" package

2016-05-19 Thread Jakub Wilk


Package: libffcall1-dev
Version: 1.10+cvs20100619-4
Severity: important
User: multiarch-de...@lists.alioth.debian.org
Usertags: multiarch

libffcall1-dev is marked as "Multi-Arch: same", but the following files 
are architecture-dependent:


/usr/include/avcall.h
/usr/include/vacall.h
/usr/include/vacall_r.h

An example diff between i386 and amd64 is attached.

--
Jakub Wilk
diff -ur libffcall1-dev_1.10+cvs20100619-4_i386/usr/include/avcall.h 
libffcall1-dev_1.10+cvs20100619-4_amd64/usr/include/avcall.h
--- libffcall1-dev_1.10+cvs20100619-4_i386/usr/include/avcall.h 2016-05-19 
02:31:34.0 +0200
+++ libffcall1-dev_1.10+cvs20100619-4_amd64/usr/include/avcall.h
2016-05-19 02:27:12.0 +0200
@@ -26,7 +26,7 @@
 
 /* CPU */
 #ifndef __i386__
-#define __i386__ 1
+/* #undef __i386__ */
 #endif
 #ifndef __m68k__
 /* #undef __m68k__ */
@@ -74,7 +74,7 @@
 /* #undef __ia64__ */
 #endif
 #ifndef __x86_64__
-/* #undef __x86_64__ */
+#define __x86_64__ 1
 #endif
 
 /* Calling convention */
diff -ur libffcall1-dev_1.10+cvs20100619-4_i386/usr/include/vacall.h 
libffcall1-dev_1.10+cvs20100619-4_amd64/usr/include/vacall.h
--- libffcall1-dev_1.10+cvs20100619-4_i386/usr/include/vacall.h 2016-05-19 
02:31:35.0 +0200
+++ libffcall1-dev_1.10+cvs20100619-4_amd64/usr/include/vacall.h
2016-05-19 02:27:12.0 +0200
@@ -19,7 +19,7 @@
 
 /* CPU */
 #ifndef __i386__
-#define __i386__ 1
+/* #undef __i386__ */
 #endif
 #ifndef __m68k__
 /* #undef __m68k__ */
@@ -67,7 +67,7 @@
 /* #undef __ia64__ */
 #endif
 #ifndef __x86_64__
-/* #undef __x86_64__ */
+#define __x86_64__ 1
 #endif
 
 /* Calling convention */
diff -ur libffcall1-dev_1.10+cvs20100619-4_i386/usr/include/vacall_r.h 
libffcall1-dev_1.10+cvs20100619-4_amd64/usr/include/vacall_r.h
--- libffcall1-dev_1.10+cvs20100619-4_i386/usr/include/vacall_r.h   
2016-05-19 02:31:35.0 +0200
+++ libffcall1-dev_1.10+cvs20100619-4_amd64/usr/include/vacall_r.h  
2016-05-19 02:27:12.0 +0200
@@ -19,7 +19,7 @@
 
 /* CPU */
 #ifndef __i386__
-#define __i386__ 1
+/* #undef __i386__ */
 #endif
 #ifndef __m68k__
 /* #undef __m68k__ */
@@ -67,7 +67,7 @@
 /* #undef __ia64__ */
 #endif
 #ifndef __x86_64__
-/* #undef __x86_64__ */
+#define __x86_64__ 1
 #endif
 
 /* Calling convention */

Bug#824111: ExpatError: syntax error

On Mon, 2016-05-16 at 17:06 +0200, Gaetano Guerriero wrote:
> 
> There are reproducible errors when calling get_bug_log() on same bug reports
> (799939, 818360).
> 
> This is not thread related, it happens even with on thread.
> 
> Server is responding with 500, pysimplesoap tries to parse response body
> anyway
> and it breaks. We can't fix this at debianbts level, except maybe by raising a
> generic "DebianBtsError".

Thanks Gaetano. I'm doing the same accordingly in my application now. In apt-
offline, now, if the bug reports fail we'll not term it a fatal error.


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


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

Bug#824712: RFH: smokeping

2016-05-19 Thread Iain R. Learmonth

Hi,

In 18/05/16 23:22, Antoine Beaupré wrote:
> I need help maintaining the smokeping package. I do not really use it
> anymore and i'd be happy to help people to sponsor it. There's a bunch
> of obscure bugs all over the place, and while I think the package
> mostly works, it's just a wild guess since well, I'm not using it
> right now.

Looks like a candidate for the Internet Measurement Packaging Team. (:

https://qa.debian.org/developer.php?login=pkg-netmeasure-disc...@lists.alioth.debian.org

Would be happy to be a co-maintainer for this package.

If this sounds good I'll add you to the team and we can update the
maintainer/uploaders fields on the next upload. (:

Thanks,
Iain.

Bug#824726: libaspell15: should only suggest (not recommend) dictionary

Package: libaspell15
Version: 0.60.7~20110707-3+b1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

libaspell15 recommends aspell dictionary.

I believe that is wrong, and that instead the library should only
suggest a dictionary: Recommending is for relationships relevant for
_most_ users - and linking against libaspell15 do not imply it being
used a lot.  A suggestion by the library can be strengthened by the
consuming application declaring a recommendation, but the opposite is
not possible - library recommendation cannot be weakened by a
consuming application declaring a suggestion (that is simply ignored).

Any application linking against libenchant effectively pulls in
aspell-en, no matter if aspell support is considered an exotic fringe
feature of said application.

Please make it easier to mix and match, by leaving it to consuming
applications to choose eventual strong relationship with dictionaries.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXPYpTAAoJECx8MUbBoAEh7bUP/RGApJeX6oLWIqLFwXbMU0qq
6EGUJecCDqcK7jiVrJx1ajLyNXs75hvKK+/G3agghC5cwOLG/uaGX+Eh95e5SCRI
e+1SRSYlvnD3OqvS82tAMQN7HT8jk6wuvZGeP0V35FAJ0EtYXt3VI2s1fV4Bh7wY
mDhB+HYdq7pw+kUEN/rZOq9mVrClvfUAbPquwhXndS3db8dI8yYIlAhmp0WAHJ3H
1leGmWd/SsAcGvxsr0jUz10lw9lhD6IYAlqg2jWUgxXKGTqhhIJjUmz8T4yW2fRX
+KAiyQRMwJYeqwLA3hukyaj9cJQrQ5WTYOXUWeUL5TEpXq4vydX3h+0UilWJ7mVp
uPVRDENawTqvJTSSVaMkZ6FA2YhzvsSfLwim85nUKEqrHe6XZaocegZ27/5rgF4h
w0zOQ1qMajpUtYJHFpNcH3QD9u5yxPOe5+F9KjYK00KgBDvBmqwXbD0MomFNuC87
biaQiI0hBLBQz+mGmEIBkTb17wgviTZoO+x6T/k8SuKoJBZjDydDutaPWZ///Z72
81qYVIPA+3psBm5wTN2EAqLt0fwEkcERqrfKjMkD27IrmmXvYeapMZCwj48CipWW
URpDWPlybZuzhZBhGWz7SX5Bn+5OgTgyciBo/UOUBnxxobyvGw5WdYaOBheVxi+W
RBOe7JCn8tj36NCx2Nuu
=yog4
-END PGP SIGNATURE-

Bug#824594: please support DPKG_ROOT in base-files' postinst

2016-05-19 Thread Santiago Vila

On Wed, 18 May 2016, Helmut Grohne wrote:

> How about another approach to chown? Since user ids are never changed to
> base-passwd and we know that base-passwd is available during package
> build, we could do the name -> id lookup at package build time. Would
> you like a patch implementing that?

I'd like to see that the idea is useful first. That's why I suggest
to make a private repository with modified packages.

Please don't concentrate your efforts on this package alone. I said
that I would keep the bug open for reference, but I don't plan to
apply the patch very soon. Maybe I apply only to experimental, or
maybe I just add the DPKG_ROOT variable for a start so that you don't
have to modify it a lot for your private repository.

Thanks.

Bug#824727: iceowl-l10n-bg: please recommend hunspell-bg as (preferred?) alternative to myspell-bg

Package: iceowl-l10n-bg
Version: 4.0.0.1-1
Severity: normal
Tags: l10n

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

iceowl-l10n-bg recommends myspell-bg but not the alternative hunspell-bg.

Please recommend hunspell-bg as alternative to myspell-bg.

As I understand it, hunspell has features not in myspell (e.g. related
to combining words which is very common in danish).  If there are no
particular reason to favor myspell-bg (e.g. bigger wordlist) then
hunspell-bg should probably be listed first, i.e. be favored.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXPYySAAoJECx8MUbBoAEhJR0QAIjnrPrZfDggQh9+jCW1rcb8
FtH6REQpisMtqgPvY7mnMzFCzXbNe6DV0CfVQ0dUk0VIzEqlLvNo7FJNcgzPMYCw
CqYmEQJQ87gTCjIeIy/BWn/o2cbqdvAgXolRZziD4a1tYe2jMlZ431DRi+WWS1C/
QDYwAtZPdi32+AUvItNBMqZsL/BfgOLYOrSkhc2tmi40odNCfVAcFjFM5IA2Cqi+
ox8nVSzV5LOZ4drSFK6LiPBQePf+fYGXKcbkTpfT6MwOrlwXc9q3ceFUH10Cz5fm
AOsJpB/ydfl+eW/Ew2t39dRx+oUA1Yyt1J76qK2A3g0/OUISIvnj8+Ylyu/zNicM
GO9J4GvmYPNv6B3l8tLOAwD9NwDDHXfv+ULLOvzHqg9UZ175PekhRyaqFavxxgqv
sZDN82APaN8kK5WUQHv+foS8Q7eT3400wCGANsFLQh0EEcB9Lv/XKOwT6L9nCwGH
UTmkMuhwAPephEiXMkfyazecC7inIPzTi2Ck0lGdPFi9LgV4ksd1frMumIvRHaCi
eRPn3Da/v4rFh8dGES5mKpxrNKKHhPieYL4Z/Lu0dIsN1L6ogz9gAETXiRmW9IRL
KW5L7CjNlkKlpbbQjXlOo+TWKE6LXuYhriwSGHgC7LrMTk5SrDoaznC4FuYT9Cmm
WIjhqv6BRLy0B6s1Z3Fk
=jC8p
-END PGP SIGNATURE-

Bug#824048: Any change in blastp? (Was: Bug#824048: python-biopython: FTBFS: AssertionError: 10 != 1)

2016-05-19 Thread Andreas Tille

Hi Peter,

since some time the blastp test fails when building the Debian BioPython
package.  I've got  no answer what might be wrong here.  Do you have any
idea which is better than deactivating this specific test for the monent
which would be the only poor idea I'd have?

Please let me know if you need more information.

Kind regards

   Andreas.

On Wed, May 11, 2016 at 10:08:49PM +0200, Andreas Tille wrote:
> On Wed, May 11, 2016 at 05:35:27PM +0100, Chris Lamb wrote:
> > ...
> >   Bio.PDB.Selection docstring test ... ok
> >   ==
> >   FAIL: test_blastp (test_NCBI_BLAST_tools.Pairwise)
> >   Pairwise BLASTP search
> >   --
> >   Traceback (most recent call last):
> > File 
> > "/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Tests/test_NCBI_BLAST_tools.py",
> >  line 103, in test_blastp
> >   self.assertEqual(10, stdoutdata.count("Query= "))
> >   AssertionError: 10 != 1
> >   
> >   --
> >   Ran 228 tests in 101.627 seconds
> >   
> >   FAILED (failures = 1)
> 
> Does any body know about a recent change in blastp?
> 
> Kind regards
> 
>Andreas.
> 
> -- 
> http://fam-tille.de
> 
> ___
> 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#669856: iptotal: transition towards Apache 2.4

2016-05-19 Thread Jean-Michel Vourgère

Control: tags -1 + patch

Hello Ignace

Attached is a patch for #669856

Also available  at https://github.com/ghantoos/debian-iptotal/pull/1
(Beware postrm is removed and not emptied)

Ping me if you need a sponsor.
commit 728020da9537f720cefff974d1fcb2289faec362
Author: Jean-Michel Vourgère 
Date:   Thu May 19 11:23:16 2016 +0200

Migate to apache2.4 (#669856)

diff --git a/debian/README.debian b/debian/README.debian
index 2968c93..c7ab309 100644
--- a/debian/README.debian
+++ b/debian/README.debian
@@ -1,11 +1,3 @@
-Using iptotal with Apache2:

-An apache configuration file template is shipped with this package. In order to
-use it, it should be symlinked inside apache2's configuration folder:
-  $ sudo ln -s /etc/iptotal/apache.conf /etc/apache2/conf.d/
-Then reload apache2 configuration:
-  $ sudo /etc/init.d/apache2 reload
-
 Note concerning iptotal's data directory:
 -
 Some important changes have been applied to iptotal's data directory over the
diff --git a/debian/apache.conf b/debian/apache.conf
deleted file mode 100644
index 0fd7805..000
--- a/debian/apache.conf
+++ /dev/null
@@ -1,9 +0,0 @@
-Alias /iptotal /var/lib/iptotal/
-
-
-Options +FollowSymLinks
-AllowOverride None
-order allow,deny
-allow from all
-DirectoryIndex template.html
-
diff --git a/debian/control b/debian/control
index fc81377..b8b635e 100644
--- a/debian/control
+++ b/debian/control
@@ -3,20 +3,25 @@ Section: admin
 Priority: extra
 Maintainer: Ignace Mouzannar 
 DM-Upload-Allowed: yes
-Build-Depends: debhelper (>= 7.0.50~), libpcap-dev, rrdtool, autotools-dev 
(>=20100122.1)
+Build-Depends: autotools-dev (>=20100122.1),
+   debhelper (>= 7.0.50~),
+   dh-apache2,
+   libpcap-dev,
+   rrdtool
 Standards-Version: 3.9.2
 Homepage: http://sourceforge.net/projects/iptotal
 
 Package: iptotal
 Architecture: any
-Depends: rrdtool, tcpdump, apache2 | httpd, ${shlibs:Depends}, ${misc:Depends}
+Depends: rrdtool, tcpdump, ${misc:Depends}, ${shlibs:Depends}
+Recommends: ${misc:Recommends}
 Description: monitor for IP traffic, not requiring SNMP
  iptotal is yet another IP traffic monitor. It listens to a network interface 
in
  non-promiscuous mode, and measures IP bandwidth usage. After the specified
  number of seconds, the average throughput is printed at total, input and 
output
  usage.
- . 
+ .
  The utility can be used to measure bandwidth usage without the need for an 
SNMP
  daemon.  In combination with a simple script and rrdtool it can be used to
  present the measured data in graphical format e.g. through a web interface.
- The package contains www + CGI sample files. 
+ The package contains www + CGI sample files.
diff --git a/debian/install b/debian/install
index 2344372..47e35c7 100644
--- a/debian/install
+++ b/debian/install
@@ -1,3 +1,2 @@
-debian/apache.conf /etc/iptotal/
 debian/iptotal/var/lib/iptotal/template.html /usr/share/iptotal/www/
 debian/iptotal/var/lib/iptotal/images/ /usr/share/iptotal/www/
diff --git a/debian/iptotal.apache2 b/debian/iptotal.apache2
new file mode 100644
index 000..db3cf62
--- /dev/null
+++ b/debian/iptotal.apache2
@@ -0,0 +1 @@
+conf debian/iptotal.conf
diff --git a/debian/iptotal.conf b/debian/iptotal.conf
new file mode 100644
index 000..4e2c0b8
--- /dev/null
+++ b/debian/iptotal.conf
@@ -0,0 +1,8 @@
+Alias /iptotal /var/lib/iptotal/
+
+
+Options +FollowSymLinks
+AllowOverride None
+Require all granted
+DirectoryIndex template.html
+
diff --git a/debian/postinst b/debian/postinst
index e382ae8..fb67bf7 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -47,7 +47,13 @@ case "$1" in
 done
 
 # change ownership to www-data
-   chown -R www-data:www-data /var/lib/iptotal/*
+chown -R www-data:www-data /var/lib/iptotal/*
+
+# enable cgi
+if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
+. /usr/share/apache2/apache2-maintscript-helper
+apache2_invoke enmod cgi
+fi
;;
 
abort-upgrade|abort-remove|abort-deconfigure)
diff --git a/debian/postrm b/debian/postrm
deleted file mode 100644
index 1719405..000
--- a/debian/postrm
+++ /dev/null
@@ -1,23 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case "$1" in
-   purge|remove)
-   # reload apache2 configuration
-   invoke-rc.d apache2 reload
-   ;;
-
-   upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
-
-   ;;
-
-   *) 
-   echo "postrm called with unknown argument \`$1'" >&2
-   exit 1
-   ;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff --git a/debian/rules b/debian/rules
index dca67c1..68a0e33 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-   dh --with autotools_dev $@
+   dh $@ --with autotools_dev,apache2
 
 override_dh_auto_configure:
dh_auto_configure -- --datadir=/

Bug#824728: icedove-l10n-bg: please recommend hunspell-bg as (preferred?) alternative to myspell-bg

Package: icedove-l10n-bg
Version: 1:38.0.1-1
Severity: normal
Tags: l10n

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

icedove-l10n-bg recommends myspell-bg but not the alternative hunspell-bg.

Please recommend hunspell-bg as alternative to myspell-bg.

As I understand it, hunspell has features not in myspell (e.g. related
to combining words which is very common in danish).  If there are no
particular reason to favor myspell-bg (e.g. bigger wordlist) then
hunspell-bg should probably be listed first, i.e. be favored.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXPY+zAAoJECx8MUbBoAEhW7EP/iNPbSttKc1ixc9P1C58tx21
aLDDlWJJEBb6wFAUIp8vKiSNvdmJqDqNPwEpzX9XihB1SC03IknQbnwk8X1PEXVK
UjGMaG+2IKxUDsgykulZh5PmaJWZUAb1vLl+jqTcE4beEnAyxYroz/OM9OuDJbY3
knxpIp7WKbu7v+zBoEq6VlGze/ryjzNsxWQQG2gw0EHwsUQ8rrhWY+WTwiOLdjTJ
lW3bWWNK29HEJfJ7H1bqq/Ej4HhTZxYJmckOEhN4NtZ/5DkFdTNhd8X/nk1JbGMa
VEglKUabkIdhMy+mo5cVfgEn/RC3DzDc2Z+H04GFf9hs0CmyN+Qsra1jgTzi2Wwl
SgxFLQe4VRUxN24zPzIOa6dhcFCmpsnG0qy9tyY9H/faU4OnQ0l2AeNc7KOXtipN
rQUqmkrlyqg9S0BNHqETOM5d+HSp3CPcEhSUWQvl9707N4sY7dM7jeIdcPTZr8GM
kYUXl26PVmlxErTEzuwmVi6yYuQ8zxmspsh0rJVshk437dklKArLP9Mt4VZDSkD6
NQTYcAmoTgdVp7hNYPKxrVZEtyVtNX4eAs3UnmipspGFuykv06ZqggXJHPTNafgD
qFiQi/ahSBCtBPouDF8pnrv+WVyGhcRrImvymi9PY1DJQO8/PfNGafNzSDHA4Cqt
c479E/Gw6K+JOiAI9SCB
=qlvR
-END PGP SIGNATURE-

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

2016-05-19 Thread lumin

On Thu, 2016-05-19 at 06:32 +, Gianfranco Costamagna wrote:
> Hi Lumin,

> >Why should runtime deps be added into build-dep, which are useless
> >unless I provide python-caffe-* testsuite.
> 
> 
> not sure then, it should be fine that way!

An update to this, according to
https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html
Even if I want to add some testsuite for python-caffe, I don't need
to add those runtime deps in control, I can add them in tests/control
instead, by adding "Depends" field that supprted by d/tests/control.

> >Really ready?
> >I looked into the packaging repo, both master and package-3.x branch
> >and I see no python3-protobuf package listed there.
> >
> >http://anonscm.debian.org/cgit/pkg-protobuf/pkg-protobuf.git/tree/debian/control?h=master
> >http://anonscm.debian.org/cgit/pkg-protobuf/pkg-protobuf.git/tree/debian/control?h=packaging-3.x
> 
> I mean: "protobuf code is declared to be python3 ready"
> 
> so I guess it is a matter of adding a package in control file, adding python3 
> in rules and some little overrides.
> my request was: can you please share that trivial patch at least on the bug 
> report?
> maybe somebody will pick it up and NMU the package

OpenCV 3.0 can yield python3-opencv package with just a small patch,
which is provided by a user in an opencv debian bug.
Protobuf might be similar.

> >The caffe package was ever blocked by 
> >* the GCC-4 -> GCC-5 transition and dependency library ABI bump
> >* CUDA 6.5 -> 7.0 bump
> >* CUDA 7.0 -> 7.5 bump
> >and now it is blocked by
> >* python3-protobuf
> >if python3 is really required.
> 
> 
> no, this isn't a blocker, but keep in mind that our goal is stretch, and 
> python2 code doesn't fit too much in it.
> I guess in case the dependencies will become python3 ready, you will add a 
> new python3-caffe-cpu package, right?

And I agree, on behalf of the release team I should make python3-*
packages in the initial upload. I decide to bump python from
2 to 3. python3-caffe can be built easily with packages outside
of Debian archive. One of the unapplied patches I removed
is for python3->python2 downgrade reversal.

opencv and protobuf is still on the way of 2 to 3, in Debian.

> can two python packages be produced by caffe or just one at each time?

One each time. Cmake requires a option PYTHON_VERSION=X where X can be
either "2" or "3".

> in the latter case you will need to drop python-caffe-cpu, add 
> python3-caffe-cpu and breaks+replaces to ensure an
> upgrade path from the python2 to the python3 version.

let's bump python version for this package.

> For sure if having the python3 dependencies in place is a matter of some 
> days, we should consider that, but
> no, this isn't a blocker right now.
> (I'm more worried about the whole breakage that comes at gcc and cuda 
> updates, will you be able to keep the package
> "installable and buildable" in unstable at each transition?)

CPU version is safe. and
no need to worry about GCC and CUDA, the source of trouble
is the compatibility between NVCC and GCC. 
That's exactly why I'm now a maintainer of CUDA 
I helped the 6.5->7.0 and 7.0->7.5 bump of CUDA, and the NVCC
usability got into a better situation, where caffe-cuda
survived.

CUDA 8.0 is comming soon, if NVCC 8.x fails to work with GCC-6,
we just lock build-dep at GCC-5. Safe too.

Actually I guess CUDA 8.5 release date is prior to stretch freeze.

> >It seems that skimage is not a blocker of Caffe.
> 
> 
> it is, the package is not in testing, so I guess caffe won't be able to 
> migrate.
> Don't forget that the goal is Stretch, not unstable, so you need to fix/help 
> in fixing the dependencies if you want
> your package to be buildable/installable on Stretch too.

Well one more bad news...

> the maintainer already did some work there
> https://github.com/scikit-image/scikit-image/issues/2091#issuecomment-220156849
> 
> so you think you can help him?
> (I could, if you ask me)

I'm not familiar with that package, and I think if I'm going
to help caffe's recursive dependency package maintainers,
I intend to first have a look at opencv or protobuf.

Stretch freeze is Q1 2017, I'm afraid whether caffe can
be uploaded into stretch in time.

* python3-opencv upload
* python3-protobuf upload
* python3-skimage NON-DFSG bugs

> Gianfranco

Thank you.

Bug#823478: python3-protobuf3

2016-05-19 Thread Mattia Rizzolo

On Thu, May 19, 2016 at 02:52:27PM +1000, Jonathon Love wrote:
> so the advice i received regarding the name was that i must get it renamed
> upstream[1]. i don't think this will be possible because:
> 
>  - upstream is an established package, present in PYPI and macports
>  - the developer is MIA

this "developer is MIA" should be a good reason by itself.  It's never
great to introduce in the archive a software where the development
stopped.

> (additionally, the official Protocol Buffers 3 supports Python 3 [2] and
> should be coming to debian soon[3]. as the main point of this package was to
> allow the use of protocol buffers with Python 3, this reduces the need for
> this package).

Agree.
Also, introducing both would mean having in the archive 2 things that do
the exact same thing.

> hence, i propose to withdraw the package, the RFS and the ITP.

This seems the better solution, yes.

> also happy to
> proceed, the work is basically done, but i can't see a way to make it work.

For all the reason you exponed, I think the best way is to withdraw the
package.

-- 
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#824675: WebKit: System volume gets too loud automatically

2016-05-19 Thread Francisco Gómez García

On Thu, 19 May 2016 09:52:48 +0200 Alberto Garcia 
wrote:

> Long answer:
> 
>By default (with flat-volumes = yes) if an application increases
>the volume then Pulseaudio will increase the master system volume
>as well.
> 
>In your case, if a web page increases the volume to 100% the
system
>volume will also be set to 100%.
> 
> Please refer to these links for more information:
> 
> https://bugs.webkit.org/show_bug.cgi?id=118974
> 
> https://wiki.archlinux.org/index.php/PulseAudio#daemon.conf
> 

Pretty odd to see this as the default behaviour (you can be totally
sure that I did not modify the PulseAudio settings). And from what I
can tell...

http://forums.debian.net/viewtopic.php?t=116252

https://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_
volumes_in_pulseaudio_a/

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541538

...I am not the only one unhappy with this. Why is this the default
setting? It's actually a risk for users' health!

Thank you for pointing out this odd situation. At least I can keep *my*
ears safe.

Bug#824729: task-bulgarian-desktop: please recommend hunspell-bg as (preferred?) alternative to myspell-bg

Package: task-bulgarian-desktop
Version: 3.34
Severity: normal
Tags: l10n

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

task-bulgarian-desktop recommends myspell-bg but not hunspell-bg.

Please recommend hunspell-bg as alternative to myspell-bg.

As I understand it, hunspell has features not in myspell (e.g. related
to combining words which is very common in danish).  If there are no
particular reason to favor myspell-bg (e.g. bigger wordlist) then
hunspell-bg should probably be listed first.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXPZLXAAoJECx8MUbBoAEhJwgP/0NmbtTk8cK+dRaSDkneHMAH
uymluwe6CmgaacAylIE5yk2Cdnp4LGxFd3BeJEc96UUoj/Gflcg3DVONiFqsyQR4
2jSHZ4KrNh7gxMYbDrXZ+lh3uIboGxTw58RY9FcHTa1FPD2EqB6xxEGYPPNsEaU8
+efQ++/x2+L5jOx2OkwbNxnHV++txh7DELBrf+FBdzwi3TCbKBporUUyHhYHWWIG
BERpgsD0J58Zec7gjaXmRoNDUzqx9/0LQ5Uhi7LuJYQqH1nlo0vZ9Y2IVPneaZ9a
cwK0Cz891lAACRXzkV/qAs+tyDsyuFTHFhf4qo1hWkA4sLsytLE3xWDdaGQOZmsS
bdcDrb5gbFEDW/KbKGFsFc5zgfzcF0s+Pt+oeqlesBrtn+SG1PdbAyL8Hwi9OBs+
JGKHyS7S5bUPy1yVMPBntLBgnaIAFNEZuQybYRnZ/DeVYiB9FQGm3MntiM1cKhPX
VVjstN5iDp1130UbSXOH6e31Zuj0zZQtpUti9cv/EHgDVa3ypwbA5Sgdvtn3N6Ue
XWE9oH4aIJHCl0np5cJP3VHSMRSVOPuoSljMdVr+J26fxpuuFCmhyQcC/rlBkrT7
E6exjaA0WTq9LfZElB3yajIyqVxW1NhcBClR6p3s7qxGGWOThqr01MNeaqVOaome
96aKF3z5Vw9LtEG9jhJL
=xF4d
-END PGP SIGNATURE-

Bug#805901: cmake: suggest cmake-doc

2016-05-19 Thread Yuri D'Elia


Package: cmake
Version: 3.5.2-1
Followup-For: Bug #805901

Yes, it would be nice if every package suggested it's own documentation when 
available.

Thanks

Bug#824730: u-boot: Please add a package for DRA7xx systems

2016-05-19 Thread Ben Hutchings

Source: u-boot
Version: 2016.03+dfsg1-4
Severity: wishlist

u-boot 2016.03 works for me on a DRA74 EVM (aka Vayu) board.  Please
apply the attached patch to add a package for this platform.

The master branch of u-boot.git currently doesn't build because the
patch "board: ti: AM57xx: Add detection logic for AM57xx-evm" refers to
files in board/ti/common/ which does not exist.  I based this patch on
the last unstable version.

Ben.

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

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

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

From: Ben Hutchings 
Date: Wed, 18 May 2016 15:38:53 +0100
Subject: [PATCH] Build dra7 package, with dra74_evm as the initial target

---
 debian/control   | 14 ++
 debian/targets   |  3 +++
 debian/u-boot-dra7.install   |  2 ++
 debian/u-boot-dra7.lintian-overrides | 14 ++
 4 files changed, 33 insertions(+)
 create mode 100755 debian/u-boot-dra7.install
 create mode 100644 debian/u-boot-dra7.lintian-overrides

diff --git a/debian/control b/debian/control
index 7d8c621ae123..aad0e16103f1 100644
--- a/debian/control
+++ b/debian/control
@@ -131,6 +131,20 @@ Description: A boot loader for Raspberry PI systems
  platforms.
  ${uboot:platforms}
 
+Package: u-boot-dra7
+Architecture: armhf
+Multi-Arch: same
+Depends: ${misc:Depends}
+Description: A boot loader for dra7 systems
+ Das U-Boot is a cross-platform bootloader for embedded systems,
+ used as the default boot loader by several board vendors.  It is
+ intended to be easy to port and to debug, and runs on many
+ supported architectures, including PPC, ARM, MIPS, x86, m68k,
+ NIOS, and Microblaze.
+ .
+ This package includes boot loaders for various TI DRA7xx platforms.
+ ${uboot:platforms}
+
 Package: u-boot-tools
 Architecture: linux-any
 Multi-Arch: foreign
diff --git a/debian/targets b/debian/targets
index 29c4cd0700f5..2b1a2c67ea4c 100644
--- a/debian/targets
+++ b/debian/targets
@@ -26,6 +26,9 @@ armel	rpi		rpi		u-boot.bin
 # Rick Thomas 
 armel	-		sheevaplug	u-boot.kwb
 
+# Ben Hutchings 
+armhf	dra7		dra74_evm	u-boot.img spl/u-boot-spl.bin MLO
+
 # Ian Campbell 
 armhf	exynos		arndale		u-boot-dtb.bin spl/arndale-spl.bin
 
diff --git a/debian/u-boot-dra7.install b/debian/u-boot-dra7.install
new file mode 100755
index ..df53d1b4c09a
--- /dev/null
+++ b/debian/u-boot-dra7.install
@@ -0,0 +1,2 @@
+#!/bin/sh
+debian/bin/u-boot-install-targets dra7
diff --git a/debian/u-boot-dra7.lintian-overrides b/debian/u-boot-dra7.lintian-overrides
new file mode 100644
index ..cacba5b8b25f
--- /dev/null
+++ b/debian/u-boot-dra7.lintian-overrides
@@ -0,0 +1,14 @@
+
+# There are no file conflicts across architectures for u-boot, as each
+# target is only installed on a single architecture. In theory, some
+# targets could be built on multiple architectures, but could instead install
+# the package for the architecture needed.
+u-boot-dra7 [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u-boot/dra74_evm/uboot.elf
+
+# These bootloaders need to be statically linked.
+u-boot-dra7 [armhf]: statically-linked-binary usr/lib/u-boot/dra74_evm/uboot.elf
+
+u-boot-dra7: description-synopsis-starts-with-article
+
+# Synopsys is the name of a company, not a misspelling.
+u-boot-dra7: spelling-error-in-copyright Synopsys Synopsis
-- 
2.8.1

Bug#823147: Fixed in 1.3.0-2

2016-05-19 Thread Jonathan McDowell

I've just upgraded libinput10 to 1.3.0-2 (from 1.3.0-1, which wasn't
working), pulling in libinput-bin and the associated udev rules. This
has fixed middle button emulation for me on my E7420 with ALPS
Glidepoint.

J.

-- 
Revd Jonathan McDowell, ULC | If they can't take a jokefuck 'em.

Bug#785770: RM: xserver-xorg-video-siliconmotion [arm64] -- RoP; FTBFS; out-of-date; uninstallable; quite possiblly never worked, little if any utility

2016-05-19 Thread Steven Chamberlain

Control: tags -1 - moreinfo

Hi FTP masters,

Please could you action this removal on arm64, since:

  * no arm64 systems are known to use this chipset:
https://bugs.debian.org/785770#17

  * the driver does not support that arch, and not being able to build
any more is expected:  https://bugs.debian.org/785491#15

  * arm64 porters requested its removal there

  * on mipsel systems having this chipset, it is reported to be working
recently in sid:  https://bugs.debian.org/771387#25

  * the package is meanwhile RC-buggy and not in stretch, now *only* due
to this out-of-date binary on arm64

Thanks very much,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Bug#824732: bluez: Wishlist Package 5.39 Significant improvements for low power devices

2016-05-19 Thread Mark Dickie

Package: bluez
Version: 5.37-0ubuntu1~awe5
Severity: wishlist

Dear Maintainer,

On purchasing new low power bluetooth mouse found it not supported under 5.36
debian packages (MS 3600)

Installed Ubuntu packages 5.37 with partial success.

Reent improvements for low power devices in 5.37, 5.38 and 5.39

from www.bluez.org :  v5.39 Release notes : This is almost entirely a bug fix
release with important fixes to GATT, HoG, AVRCP & A2DP. It is recommended to
upgrade if you were previously using 5.38.

Many thanks

Mark




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

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

Versions of packages bluez depends on:
ii  dbus 1.10.8-1
ii  init-system-helpers  1.33
ii  kmod 22-1.1
ii  libc62.22-7
ii  libdbus-1-3  1.10.8-1
ii  libglib2.0-0 2.48.1-1
ii  libreadline6 6.3-8+b4
ii  libudev1 229-5
ii  lsb-base 9.20160110
ii  udev 229-5

bluez recommends no packages.

bluez suggests no packages.

-- no debconf information

Bug#824734: omnievents: FTBFS: cp: cannot stat './TODOdoc/omnievents.docbook.css': No such file or directory

Source: omnievents
Version: 1:2.6.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

omnievents fails to build from source in unstable/amd64:

[..]

Transferring function references...
Combining using relations...
Adding members to index pages...
Generating style sheet...
Generating search indices...
Generating example documentation...
Generating file sources...
Generating code for file Callback.h...
Generating code for file channel.cc...
Generating code for file config.h...
Generating code for file ConsumerAdmin.cc...
Generating code for file ConsumerAdmin.h...
Generating code for file daemon.h...
Generating code for file daemon_unix.cc...
Generating code for file daemon_unix.h...
Generating code for file daemon_windows.cc...
Generating code for file daemon_windows.h...
Generating code for file defaults.h...
Generating code for file eventc.cc...
Generating code for file EventChannel.cc...
Generating code for file EventChannel.h...
Generating code for file EventChannelFactory.cc...
Generating code for file EventChannelFactory.h...
Generating code for file eventf.cc...
Generating code for file EventQueue.cc...
Generating code for file EventQueue.h...
Generating code for file events.cc...
Generating code for file Filter.cc...
Generating code for file
F/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/defaults.h:82:
warning: Found unknown command `\TEMP'

/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
warning: Unsupported xml/html tag found

/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
warning: Unsupported xml/html tag found
ilter.h...
Generating code for file gethostname.h...
Generating code for file getopt.cc...
Generating code for file getopt.h...
Generating code for file main.cc...
Generating code for file main.h...
Generating code for file Mapper.h...
Generating code for file naming.cc...
Generating code for file naming.h...
Generating code for file omniEvents.cc...
Generating code for file omniEvents.h...
Generating code for file omniEventsLog.cc...
Generating code for file omniEventsLog.h...
Generating code for file Orb.cc...
Generating code for file Orb.h...
Generating code for file PersistNode.cc...
Generating code for file PersistNode.h...
Generating code for file ProxyManager.cc...
Generating code for file ProxyManager.h...
Generating code for file ProxyPullConsumer.cc...
Generating code for file ProxyPullConsumer.h...
Generating code for file ProxyPullSupplier.cc...
Generating code for file ProxyPullSupplier.h...
Generating code for file ProxyPushConsumer.cc...
Generating code for file ProxyPushConsumer.h...
Generating code for file ProxyPushSupplier.cc...
Generating code for file ProxyPushSupplier.h...
Generating code for file pullcons.cc...
Generating code for file pullsupp.cc...
Generating code for file pushcons.cc...
Generating code for file pushsupp.cc...
Generating code for file rmeventc.cc...
Generating code for file scour.h...
Generating code for file Servant.cc...
Generating code for file Servant.h...
Generating code for file SupplierAdmin.cc...
Generating code for file SupplierAdmin.h...
Generating code for file version.cc...
Generating code for file version.h...
Generating file documentation...
Generating docs for file Callback.h...
Generating docs for file channel.cc...
Generating docs for file config.h...
Generating docs for file ConsumerAdmin.cc...
Generating docs for file ConsumerAdmin.h...
Generating docs for file daemon.h...
Generating docs for file daemon_unix.cc...
Generating docs for file daemon_unix.h...
Generating docs for file daemon_windows.cc...
Generating docs for file daemon_windows.h...
Generating docs for file defaults.h...
Generating docs for file eventc.cc...
Generating docs for file EventChannel.cc...
Generating d

Bug#824733: abtransfers: FTBFS: Project ERROR: Package gwengui-qt4 not found

Source: abtransfers
Version: 0.0.5.0-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

abtransfers fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../pkg-config_0.29-4_amd64.deb ...
  Unpacking pkg-config (0.29-4) ...
  Selecting previously unselected package qtchooser.
  Preparing to unpack .../qtchooser_52-gae5eeef-2_amd64.deb ...
  Unpacking qtchooser (52-gae5eeef-2) ...
  Selecting previously unselected package qt4-qmake.
  Preparing to unpack .../qt4-qmake_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking qt4-qmake (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libdbus-1-3:amd64.
  Preparing to unpack .../libdbus-1-3_1.10.8-1_amd64.deb ...
  Unpacking libdbus-1-3:amd64 (1.10.8-1) ...
  Selecting previously unselected package qtcore4-l10n.
  Preparing to unpack .../qtcore4-l10n_4%3a4.8.7+dfsg-6_all.deb ...
  Unpacking qtcore4-l10n (4:4.8.7+dfsg-6) ...
  Selecting previously unselected package libqtcore4:amd64.
  Preparing to unpack .../libqtcore4_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqt4-xml:amd64.
  Preparing to unpack .../libqt4-xml_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqt4-xml:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqtdbus4:amd64.
  Preparing to unpack .../libqtdbus4_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqtdbus4:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package qdbus.
  Preparing to unpack .../qdbus_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking qdbus (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqt4-dbus:amd64.
  Preparing to unpack .../libqt4-dbus_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqt4-dbus:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqt4-network:amd64.
  Preparing to unpack .../libqt4-network_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqt4-network:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqt4-script:amd64.
  Preparing to unpack .../libqt4-script_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqt4-script:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqt4-sql:amd64.
  Preparing to unpack .../libqt4-sql_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqt4-sql:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libqt4-xmlpatterns:amd64.
  Preparing to unpack .../libqt4-xmlpatterns_4%3a4.8.7+dfsg-6+b1_amd64.deb ...
  Unpacking libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-6+b1) ...
  Selecting previously unselected package libpng16-16:amd64.
  Preparing to unpack .../libpng16-16_1.6.21-5_amd64.deb ...
  Unpacking libpng16-16:amd64 (1.6.21-5) ...
  Selecting previously unselected package libfreetype6:amd64.
  Preparing to unpack .../libfreetype6_2.6.3-3+b1_amd64.deb ...
  Unpacking libfreetype6:amd64 (2.6.3-3+b1) ...
  Selecting previously unselected package ucf.
  Preparing to unpack .../archives/ucf_3.0036_all.deb ...
  Moving old data out of the way
  Unpacking ucf (3.0036) ...
  Selecting previously unselected package fonts-dejavu-core.
  Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
  Unpacking fonts-dejavu-core (2.35-1) ...
  Selecting previously unselected package fontconfig-config.
  Preparing to unpack .../fontconfig-config_2.11.0-6.4_all.deb ...
  Unpacking fontconfig-config (2.11.0-6.4) ...
  Selecting previously unselected package libfontconfig1:amd64.
  Preparing to unpack .../libfontconfig1_2.11.0-6.4_amd64.deb ...
  Unpacking libfontconfig1:amd64 (2.11.0-6.4) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libxau6:amd64.
  Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
  Unpacking libxau6:amd64 (1:1.0.8-1) ...
  Selecting previously unselected package x11-common.
  Preparing to unpack .../x11-common_1%3a7.7+15_all.deb ...
  Unpacking x11-common (1:7.7+15) ...
  Selecting previously unselected package libice6:amd64.
  Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libxdmcp6:amd64.
  Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
  Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Selecting previously unselected package libxcb1:amd64.
  Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
  Unpacking libxcb1:amd64 (1.11.1-1) ...
  Selecting previously unselected package libx11-data.
  Preparing to unpack .../libx11-data_2%3a1.6.3-1_a

Bug#824738: simpleparse: FTBFS: ImportError: No module named simpleparse.stt.TextTools

Source: simpleparse
Version: 2.1.0a1-7
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

simpleparse fails to build from source in unstable/amd64:

  [..]

 static void *mxDebugPrintf_used;
  ^
  stt/TextTools/mxTextTools/mxTextTools.c: In function 
'mxTextSearch_SearchBuffer':
  stt/TextTools/mxTextTools/mxTextTools.c:483:56: warning: passing argument 3 
of 'PyObject_AsCharBuffer' from incompatible pointer type 
[-Wincompatible-pointer-types]
else if (PyObject_AsCharBuffer(so->match, &match, &match_len))
  ^
  In file included from /usr/include/python2.7/Python.h:133:0,
   from stt/TextTools/mxTextTools/mx.h:60,
   from stt/TextTools/mxTextTools/mxTextTools.c:16:
  /usr/include/python2.7/abstract.h:476:22: note: expected 'Py_ssize_t * {aka 
long int *}' but argument is of type 'int *'
PyAPI_FUNC(int) PyObject_AsCharBuffer(PyObject *obj,
^
  stt/TextTools/mxTextTools/mxTextTools.c: At top level:
  stt/TextTools/mxTextTools/mxTextTools.c:2045:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
   (inquiry)0,/*sq_length*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2045:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_length')
  stt/TextTools/mxTextTools/mxTextTools.c:2047:5: warning: 'intargfunc' is 
deprecated [-Wdeprecated-declarations]
   (intargfunc)0,   /*sq_repeat*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2047:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
  stt/TextTools/mxTextTools/mxTextTools.c:2047:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_repeat')
  stt/TextTools/mxTextTools/mxTextTools.c:2048:5: warning: 'intargfunc' is 
deprecated [-Wdeprecated-declarations]
   (intargfunc)0,   /*sq_item*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2048:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
  stt/TextTools/mxTextTools/mxTextTools.c:2048:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_item')
  stt/TextTools/mxTextTools/mxTextTools.c:2049:5: warning: 'intintargfunc' is 
deprecated [-Wdeprecated-declarations]
   (intintargfunc)0,   /*sq_slice*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2049:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
  stt/TextTools/mxTextTools/mxTextTools.c:2049:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_slice')
  stt/TextTools/mxTextTools/mxTextTools.c:2050:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
   (intobjargproc)0,   /*sq_ass_item*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2050:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_ass_item')
  stt/TextTools/mxTextTools/mxTextTools.c:2051:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
   (intintobjargproc)0,  /*sq_ass_slice*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2051:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_ass_slice')
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-Istt/TextTools/mxTextTools -I/usr/include/python2.7 -c 
stt/TextTools/mxTextTools/mxte.c -o 
/home/lamby/temp/cdt.20160519114504.pfnZ1hQqMU.simpleparse/simpleparse-2.1.0a1/./build/temp.linux-x86_64-2.7/stt/TextTools/mxTextTools/mxte.o
  In file included from stt/TextTools/mxTextTools/mx.h:63:0,
   from stt/TextTools/mxTextTools/mxte.c:17:
  stt/TextTools/mxTextTools/mxstdlib.h: In function 'mxDebugPrintf':
  stt/TextTools/mxTextTools/mxstdlib.h:177:16: warning: variable 
'mxDebugPrintf_used' set but not used [-Wunused-but-set-variable]
 static void *mxDebugPrintf_used;
  ^
  In file included from /usr/include/python2.7/Python.h:94:0,
   from stt/TextTools/mxTextTools/mx.h:60,
   from stt/TextTools/mxTextTools/mxte.c:17:
  stt/TextTools/mxTextTools/lowlevelcommands.h: In function 
'mxTextTools_TaggingEngine':
  /usr/include/python2.7/stringobject.h:91:32: warning: pointer targets in 
initialization differ in signedness [-Wpointer-sign]
   #define PyString_AS_STRING(op) (((PyStringObject *)(op))->ob_sval)
  ^
  stt/TextTools/mxTextTools/lowlevelcommands.h:214:22: note: in expansion of 
macro 'PyString_AS_STRING'
 unsigned char *m = PyString_AS_STRING(match);
^
  /usr/include/python2.7/stringobject.h:91:32: warning: pointer targets in 
initialization di

Bug#824735: raptor2: FTBFS: cp: cannot stat 'NOTICEUPGRADING.html': No such file or directory

Source: raptor2
Version: 2.0.14-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

raptor2 fails to build from source in unstable/amd64:

  [..]

  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/src'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/src'
  Making install in utils
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/utils'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/utils'
   /bin/mkdir -p 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/debian/tmp//usr/bin'
/bin/bash ../libtool   --mode=install /usr/bin/install -c rapper 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/debian/tmp//usr/bin'
  libtool: warning: '../src/libraptor2.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
  libtool: install: /usr/bin/install -c .libs/rapper 
/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/debian/tmp//usr/bin/rapper
   /bin/mkdir -p 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/debian/tmp//usr/share/man/man1'
   /usr/bin/install -c -m 644 rapper.1 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/debian/tmp//usr/share/man/man1'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/utils'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/utils'
  Making install in docs
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/docs'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160519114130.EKHN2RbwCo.raptor2/raptor2-2.0.14/docs'
  make[3]: Nothing to be done for 'install-exec-am'.
   /usr/bin/install -c -m 644 ./html/home.png
   /usr/bin/install -c -m 644 ./html/index.html
   /usr/bin/install -c -m 644 ./html/index.sgml
   /usr/bin/install -c -m 644 ./html/introduction.html
   /usr/bin/install -c -m 644 ./html/ix01.html
   /usr/bin/install -c -m 644 ./html/left.png
   /usr/bin/install -c -m 644 ./html/parser-grddl.html
   /usr/bin/install -c -m 644 ./html/parser-guess.html
   /usr/bin/install -c -m 644 ./html/parser-json.html
   /usr/bin/install -c -m 644 ./html/parser-ntriples.html
   /usr/bin/install -c -m 644 ./html/parser-rdfa.html
   /usr/bin/install -c -m 644 ./html/parser-rdfxml.html
   /usr/bin/install -c -m 644 ./html/parser-rss-tag-soup.html
   /usr/bin/install -c -m 644 ./html/parser-trig.html
   /usr/bin/install -c -m 644 ./html/parser-turtle.html
   /usr/bin/install -c -m 644 ./html/raptor-formats-types-by-parser.html
   /usr/bin/install -c -m 644 ./html/raptor-formats-types-by-serializer.html
   /usr/bin/install -c -m 644 ./html/raptor-formats-types-index.html
   /usr/bin/install -c -m 644 ./html/raptor-formats.html
   /usr/bin/install -c -m 644 ./html/raptor-parsers.html
   /usr/bin/install -c -m 644 ./html/raptor-serializers.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-1-4-21-to-2-0-0.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-10-to-2-0-11.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-11-to-2-0-12.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-13-to-2-0-14.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-3-to-2-0-4.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-4-to-2-0-5.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-5-to-2-0-6.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-6-to-2-0-7.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-7-to-2-0-8.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes-2-0-9-to-2-0-10.html
   /usr/bin/install -c -m 644 ./html/raptor2-changes.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-avltree.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-constants.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-general.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-iostream.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-locator.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-memory.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-option.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-parser.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-sax2.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-sequence.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-serializer.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-stringbuffer.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-triples.html
   /usr/bin/install -c -m 644 ./html/raptor2-section-unicode.html
   /usr/bin/install -c -m 644 ./ht

Bug#824736: rjava: FTBFS: Makefile.all:38: recipe for target 'libjri.so' failed

Source: rjava
Version: 0.9-8-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

rjava fails to build from source in unstable/amd64:

  [..]

  Adding debian:Root_CA_Generalitat_Valenciana.pem
  Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
  Adding debian:S-TRUST_Universal_Root_CA.pem
  Adding debian:SecureSign_RootCA11.pem
  Adding debian:SecureTrust_CA.pem
  Adding debian:Secure_Global_CA.pem
  Adding debian:Security_Communication_EV_RootCA1.pem
  Adding debian:Security_Communication_RootCA2.pem
  Adding debian:Security_Communication_Root_CA.pem
  Adding debian:Sonera_Class_1_Root_CA.pem
  Adding debian:Sonera_Class_2_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:Starfield_Class_2_CA.pem
  Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
  Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
  Adding debian:StartCom_Certification_Authority.pem
  Adding debian:StartCom_Certification_Authority_2.pem
  Adding debian:StartCom_Certification_Authority_G2.pem
  Adding debian:SwissSign_Gold_CA_-_G2.pem
  Adding debian:SwissSign_Platinum_CA_-_G2.pem
  Adding debian:SwissSign_Silver_CA_-_G2.pem
  Adding debian:Swisscom_Root_CA_1.pem
  Adding debian:Swisscom_Root_CA_2.pem
  Adding debian:Swisscom_Root_EV_CA_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
  Adding debian:TC_TrustCenter_Class_3_CA_II.pem
  Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
  Adding debian:TWCA_Global_Root_CA.pem
  Adding debian:TWCA_Root_Certification_Authority.pem
  Adding debian:Taiwan_GRCA.pem
  Adding debian:TeliaSonera_Root_CA_v1.pem
  Adding debian:Trustis_FPS_Root_CA.pem
  Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
  Adding debian:USERTrust_ECC_Certification_Authority.pem
  Adding debian:USERTrust_RSA_Certification_Authority.pem
  Adding debian:UTN_USERFirst_Email_Root_CA.pem
  Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
  Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_2.pem
  Adding debian:Visa_eCommerce_Root.pem
  Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
  Adding debian:WoSign.pem
  Adding debian:WoSign_China.pem
  Adding debian:XRamp_Global_CA_Root.pem
  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package rjava
  dpkg-buildpackage: info: source version 0.9-8-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Dirk Eddelbuettel 
   dpkg-source --before-build rjava-0.9-8
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
  test -x debian/rules
  /usr/bin/make -f debian/rules reverse-config
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160519114259.i7R4hRYI37.rjava/rjava-0.9-8'
  CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
  set -e;
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160519114259.i7R4hRYI37.rjava/rjava-0.9-8'
  if [ "reverse-patches" = "reverse-patches" ]; then rm -f 
debian/stamp-patched; fi
  patches: 
  if [ "reverse-patches" != "reverse-patches" ]; then

Bug#824737: ruby-albino: FTBFS: expected to not match

Source: ruby-albino
Version: 1.3.3-4
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-albino fails to build from source in unstable/amd64:

  [..]

  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
ca-certificates gem2deb gem2deb-test-runner libgmp-dev libgmpxx4ldbl
libruby2.3 libyaml-0-2 openssl python-pygments python3-chardet
python3-debian python3-pkg-resources python3-six rake ruby ruby-all-dev
ruby-did-you-mean ruby-metaclass ruby-minitest ruby-mocha ruby-net-telnet
ruby-posix-spawn ruby-power-assert ruby-setup ruby-test-unit ruby2.3
ruby2.3-dev rubygems-integration
  Suggested packages:
gmp-doc libgmp10-doc libmpfr-dev ttf-bitstream-vera python3-setuptools ri
ruby-dev ruby-mocha-doc bundler
  Recommended packages:
apt-file python-chardet python3-apt zip fonts-lato libjs-jquery
  The following NEW packages will be installed:
ca-certificates gem2deb gem2deb-test-runner libgmp-dev libgmpxx4ldbl
libruby2.3 libyaml-0-2 openssl python-pygments python3-chardet
python3-debian python3-pkg-resources python3-six rake ruby ruby-all-dev
ruby-did-you-mean ruby-metaclass ruby-minitest ruby-mocha ruby-net-telnet
ruby-posix-spawn ruby-power-assert ruby-setup ruby-test-unit ruby2.3
ruby2.3-dev rubygems-integration
  0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 7249 kB of archives.
  After this operation, 28.8 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 openssl amd64 
1.0.2h-1 [681 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 ca-certificates all 
20160104 [200 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 rubygems-integration 
all 1.10 [4882 B]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 ruby-did-you-mean all 
1.0.0-2 [11.2 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 ruby-minitest all 
5.8.4-2 [50.3 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 ruby-net-telnet all 
0.1.1-2 [12.5 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 ruby-power-assert all 
0.2.7-1 [7578 B]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 ruby-test-unit all 
3.1.7-2 [69.6 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 libyaml-0-2 amd64 
0.1.6-3 [50.4 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libruby2.3 amd64 
2.3.1-1 [3098 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 ruby2.3 amd64 
2.3.1-1 [177 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 ruby amd64 1:2.3.0+4 
[10.5 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 rake all 10.5.0-2 
[49.4 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 gem2deb-test-runner 
all 0.30.1 [19.4 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 
python3-pkg-resources all 20.10.1-1 [112 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 python3-chardet all 
2.3.0-2 [96.0 kB]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 python3-six all 
1.10.0-3 [14.4 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 python3-debian all 
0.1.27 [50.9 kB]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 libgmpxx4ldbl amd64 
2:6.1.0+dfsg-2 [22.2 kB]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 libgmp-dev amd64 
2:6.1.0+dfsg-2 [628 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 ruby2.3-dev amd64 
2.3.1-1 [1169 kB]
  Get:22 http://httpredir.debian.org/debian sid/main amd64 ruby-all-dev amd64 
1:2.3.0+4 [9996 B]
  Get:23 http://httpredir.debian.org/debian sid/main amd64 ruby-setup all 
3.4.1-9 [34.2 kB]
  Get:24 http://httpredir.debian.org/debian sid/main amd64 gem2deb all 0.30.1 
[55.3 kB]
  Get:25 http://httpredir.debian.org/debian sid/main amd64 python-pygments all 
2.1.3+dfsg-1 [535 kB]
  Get:26 http://httpredir.debian.org/debian sid/main amd64 ruby-metaclass all 
0.0.4-1 [3768 B]
  Get:27 http://httpredir.debian.org/debian sid/main amd64 ruby-mocha all 
1.1.0-2 [52.7 kB]
  Get:28 http://httpredir.debian.org/debian sid/main amd64 ruby-posix-spawn 
amd64 0.3.11-1+b2 [24.6 kB]
  Fetched 7249 kB in 0s (54.1 MB/s)
  Selecting previously unselected package openssl.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 9

Bug#824740: telepathy-ring: FTBFS: cp: cannot stat './AUTHORS--no-act': No such file or directory

Source: telepathy-ring
Version: 2.1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

telepathy-ring fails to build from source in unstable/amd64:

  [..]

  # source='ring-conference-channel.c' object='ring-conference-channel.lo' 
libtool=yes 
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I.. -I../tests -I..  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o ring-conference-channel.lo 
ring-conference-channel.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../tests -I.. 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c ring-conference-channel.c -o 
ring-conference-channel.o
  ring-conference-channel.c: In function 'ring_mergeable_conference_merge':
  ring-conference-channel.c:208:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   error = g_error_new(TP_ERRORS, TP_ERROR_INVALID_ARGUMENT,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel.h:35,
   from ring-conference-channel.c:40:
  /usr/include/telepathy-1.0/telepathy-glib/errors.h:39:8: note: declared here
   GQuark tp_errors_quark (void);
  ^
  ring-conference-channel.c: In function 
'ring_conference_channel_remove_member_with_reason':
  ring-conference-channel.c:630:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   g_set_error(error, TP_ERRORS, TP_ERROR_PERMISSION_DENIED,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel.h:35,
   from ring-conference-channel.c:40:
  /usr/include/telepathy-1.0/telepathy-glib/errors.h:39:8: note: declared here
   GQuark tp_errors_quark (void);
  ^
  ring-conference-channel.c: In function 'ring_conference_channel_join':
  ring-conference-channel.c:921:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   g_set_error(error, TP_ERRORS, TP_ERROR_INVALID_ARGUMENT,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel.h:35,
   from ring-conference-channel.c:40:
  /usr/include/telepathy-1.0/telepathy-glib/errors.h:39:8: note: declared here
   GQuark tp_errors_quark (void);
  ^
  ring-conference-channel.c: In function 'ring_conference_channel_release':
  ring-conference-channel.c:1039:10: warning: variable 'details' set but not 
used [-Wunused-but-set-variable]
 int i, details;
^
  ring-conference-channel.c: In function 
'ring_conference_channel_validate_media_handle':
  ring-conference-channel.c:1150:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   g_set_error(error, TP_ERRORS, TP_ERROR_INVALID_ARGUMENT,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel

Bug#824739: telepathy-haze: FTBFS: media-stream.c:1079:20: error: 'PURPLE_MEDIA_NETWORK_PROTOCOL_TCP' undeclared

Source: telepathy-haze
Version: 0.8.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

telepathy-haze fails to build from source in unstable/amd64:

  [..]

  Setting up gir1.2-telepathyglib-0.12 (0.24.1-1.1) ...
  Setting up libtelepathy-glib-dev (0.24.1-1.1) ...
  Setting up libxslt1.1:amd64 (1.1.28-3) ...
  Setting up xsltproc (1.1.28-3) ...
  Setting up libgtk-3-bin (3.20.4-1) ...
  Setting up adwaita-icon-theme (3.20-2) ...
  update-alternatives: using /usr/share/icons/Adwaita/cursor.theme to provide 
/usr/share/icons/default/index.theme (x-cursor-theme) in auto mode
  Setting up libgtk-3-common (3.20.4-1) ...
  Setting up libgtk-3-0:amd64 (3.20.4-1) ...
  Setting up gstreamer1.0-plugins-bad:amd64 (1.8.1-2) ...
  Setting up libfarstream-0.2-5:amd64 (0.2.7-1) ...
  Setting up libpurple0 (2.10.12-1) ...
  Setting up libpurple-dev (2.10.12-1) ...
  Setting up telepathy-haze-build-deps (0.8.0-2) ...
  Processing triggers for libc-bin (2.22-9) ...
  Processing triggers for systemd (229-6) ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package telepathy-haze
  dpkg-buildpackage: info: source version 0.8.0-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Simon McVittie 
   dpkg-source --before-build telepathy-haze-0.8.0
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with autoreconf --parallel
 dh_testdir -O--parallel
 dh_auto_clean -O--parallel
 dh_autoreconf_clean -O--parallel
 dh_clean -O--parallel
   debian/rules build
  dh build --with autoreconf --parallel
 dh_testdir -O--parallel
 dh_update_autotools_config -O--parallel
 dh_autoreconf -O--parallel
  libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
  libtoolize: copying file 'build-aux/ltmain.sh'
  libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
  libtoolize: copying file 'm4/libtool.m4'
  libtoolize: copying file 'm4/ltoptions.m4'
  libtoolize: copying file 'm4/ltsugar.m4'
  libtoolize: copying file 'm4/ltversion.m4'
  libtoolize: copying file 'm4/lt~obsolete.m4'
  configure.ac:42: installing 'build-aux/compile'
  configure.ac:27: installing 'build-aux/missing'
  extensions/Makefile.am:13: warning: source file '_gen/signals-marshal.c' is 
in a subdirectory,
  extensions/Makefile.am:13: but option 'subdir-objects' is disabled
  automake: warning: possible forward-incompatibility.
  automake: At least a source file is in a subdirectory, but the 
'subdir-objects'
  automake: automake option hasn't been enabled.  For now, the corresponding 
output
  automake: object file(s) will be placed in the top-level directory.  However,
  automake: this behaviour will change in future Automake versions: they will
  automake: unconditionally cause object files to be placed in the same 
subdirectory
  automake: of the corresponding sources.
  automake: You are advised to start using 'subdir-objects' option throughout 
your
  automake: project, to avoid future incompatibilities.
  extensions/Makefile.am:13: warning: source file '_gen/svc.c' is in a 
subdirectory,
  extensions/Makefile.am:13: but option 'subdir-objects' is disabled
  extensions/Makefile.am: installing 'build-aux/depcomp'
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160519114732.70HUuJxhub.telepathy-haze/telepathy-haze-0.8.0'
  dh_auto_configure -- \
--libexecdir="\${prefix}/lib/telepathy" \

./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --libexecdir=\${prefix}/lib/telepathy
  configure: WARNING: unrecognized options: --disable-maintainer-mode
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking whether make supports nested variables... (cached) yes
  checking for gcc... gcc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether we are using the GNU C compiler... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to

Bug#824741: xpdf: some keysyms (0xe9 eacute and 0xdb Ucircumflex) are ignored in text input fields

Package: xpdf
Version: 3.04-1
Severity: normal

In text input fields, such as in the Find and Save As dialog boxes,
some keysyms are ignored. This is at least the case of:
  * 0xe9 eacute (é)
  * 0xdb Ucircumflex (Û)

However this is no such problem with: èêëâîôûàùïç ÉÈÊËÂÎÔÀÙÏÇ

Note: The problem is at the keysym level, as if I change my keyboard
configuration to use other keysyms for the same physical keys, the
characters appear as expected. Moreover, I can enter these characters
é and Û with dead keys (dead_acute + e and dead_circumflex + U).

-- 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)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/12 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 xpdf depends on:
ii  libc6 2.22-9
ii  libgcc1   1:6.1.1-3
ii  libpoppler57  0.38.0-3
ii  libstdc++66.1.1-3
ii  libx11-6  2:1.6.3-1
ii  libxm42.3.4-10+b1
ii  libxt61:1.1.5-1

Versions of packages xpdf recommends:
ii  cups-bsd   2.1.3-5
ii  gsfonts-x110.24
ii  poppler-data   0.4.7-7
ii  poppler-utils  0.38.0-3

xpdf suggests no packages.

-- no debconf information

Bug#806889: [pkg-wpa-devel] Bug#806889: wpasupplicant: New upstream version (2.5)

2016-05-19 Thread Faidon Liambotis

Hi,

On Sun, May 01, 2016 at 07:04:56PM +0200, Stefan Lippers-Hollmann wrote:
> I'm still debugging the 4addr regression mentioned in my previous mail,
> given the rather unfortunate approach to reproduce it, testing takes
> about a week for each iteration (unless it fails early by chance, so
> far I've seen time to failure up to 3-4 days, even though it often 
> within hours). Replacing one bug with another doesn't sound like a good
> tradeoff to me.

Another ~20 days passed by -- any news about uploading an updated
package to unstable?

Thanks,
Faidon

Bug#824453: gtk-gnutella: please make the build reproducible

forwarded 824453 https://github.com/gtk-gnutella/gtk-gnutella/pull/17
thanks

> Thanks both for working on this! I'd like to remove myself as a middleman 
> here: can you submit this directly to upstream to get it merged there?

No problem. :)


Regards,

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

Bug#824743: hfsplus: Lower/Uppercase issue, remembering casing after removal

2016-05-19 Thread Tim Ruehsen

Package: hfsplus
Version: 1.0.4-13
Severity: normal

Dear Maintainer,

in freshly created directory on a HFS+ mount, I experience the following:

$ mkdir xxx && cd xxx
$ touch DUMMY.TXT
$ ls
DUMMY.TXT
$ rm DUMMY.TXT
$ touch dummy.txt
$ ls
DUMMY.TXT

This should be dummy.txt, looks like HFS+ 'remembers' old casing.
Now the other way round:

$ cd ..
$ rm -rf xxx
$ mkdir xxx && cd xxx
$ touch dummy.txt
$ ls
dummy.txt
$ rm dummy.txt
$ touch DUMMY.TXT
$ ls
dummy.txt

This issue disturbs a test suite here (Wget2 development, testing 
uppercase/lowercase stuff).
I could work around it by re-creating a new temp directory for each test, but
I find this HFS+ behaviour somewhat unexpected.

How I created my HFS+ mount:
$ sudo apt-get install hfsprogs
$ dd if=/dev/zero of=hfsimage bs=512 count=500k
$ sudo losetup /dev/loop0 hfsimage
$ sudo mkfs -t hfsplus /dev/loop0
$ sudo mount -t hfsplus /dev/loop0 /mnt
$ cd /mnt
$ sudo mkdir test
$ sudo chown tim:users test
$ cd test

(amend 'tim:users' to your environment)

Regards, Tim

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

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

Versions of packages hfsplus depends on:
ii  libc6 2.22-9
ii  libhfsp0  1.0.4-13

hfsplus recommends no packages.

hfsplus suggests no packages.

-- no debconf information

Bug#824742: dpkg: Please add arm64ilp32 to cputable

2016-05-19 Thread Wookey

Package: dpkg
Version: 1.18.7
Severity: wishlist

There is a new ABI for arm64 which is the equivalent of x32 on amd64.
It uses the armv8 instruction set for a 32-bit ABI (32-bit
instructions, longs and pointers). Generally referred-to is 'ILP32' in
comparison to the 'LP64' standard arm64 ABI.

This is only expected to be used in quite rare circumstances, but we
do want to make it possible to build in a debian or debian-derived
context, which needs dpkg support.

Attached is a patch to provide that. It also add existing arm64
big-endian so that people can 'easily' build that too if need be.

diff -Nru dpkg-1.18.1/cputable dpkg-1.18.1+nmu1/cputable
--- dpkg-1.18.1/cputable2015-05-22 01:17:44.0 +0100
+++ dpkg-1.18.1+nmu1/cputable   2015-06-18 02:12:22.0 +0100
@@ -21,6 +21,8 @@
 armeb  armeb   arm.*b  32  big
 armarm arm.*   32  little
 arm64  aarch64 aarch64 64  little
+arm64beaarch64_be  aarch64_be  64  big
+arm64ilp32 aarch64 aarch64_ilp32   32  little
+arm64ilp32be   aarch64_be  aarch64_be_ilp3232  big
 avr32  avr32   avr32   32  big
 hppa   hppahppa.*  32  big
 m32r   m32rm32r32  big

Bug#822210: sdl2-config.cmake: extra leading / trailing whitespace

2016-05-19 Thread Manuel A. Fernandez Montecelo


Hi!

2016-05-01 15:42 Manuel A. Fernandez Montecelo:


If it needs this change, I think that my solution is not very robust
and that the assumptions made don't work and can fail in other cases.


So I've been fighting with this for a while this morning and couldn't
get it to work as originally intended.  In the end, I uploaded a new
version of the package with the patch stripping only the SDL2_LIBRARIES
variable.

If other vars contain whitespace in the future it will not work, but
that's fundamentally a problem with upstream...  I submitted the patch
for their consideration in any case.

It would be great if you can verify that this works fine in your system,
but I am quite confident that it does so I published the new release to
the archive already -- lest it slips through the cracks and it's delayed
for a few more weeks.


Cheers.
--
Manuel A. Fernandez Montecelo

Bug#824744: pg_createcluster should set "cluster_name"

2016-05-19 Thread Christoph Berg

Package: postgresql-common
Version: 174
Severity: wishlist

pg_createcluster should set "cluster_name":

#cluster_name = ''  # added to process titles if nonempty
# (change requires rest

Bug#824745: gv: segmentation fault when zooming on an empty document

Package: gv
Version: 1:3.7.4-1
Severity: normal

gv crashes (segmentation fault) when zooming on an empty document.
To reproduce:

1. Start gv with no arguments.
2. Over the white area, click with the left button.
3. Click oon any item of the zoom menu, e.g. on 2.

Debugging information:

Program received signal SIGSEGV, Segmentation fault.
0x0042e989 in ?? ()
(gdb) bt full
#0  0x0042e989 in ?? ()
No symbol table info available.
#1  0x0041b22e in ?? ()
No symbol table info available.
#2  0x7752daad in HandleActions (w=w@entry=0x6fadc0, 
event=0x7fffcda0, accelWidget=, procs=0x6fafb8, 
actions=actions@entry=0x6d0da0, stateTree=)
at ../../src/TMstate.c:644
actionHookList = 0x0
bindWidget = 
#3  0x7752df15 in HandleSimpleState (w=w@entry=0x6fadc0, 
tmRecPtr=tmRecPtr@entry=0x6fae08, 
curEventPtr=curEventPtr@entry=0x7fffc9b0) at ../../src/TMstate.c:883
bindData = 
procs = 
accelWidget = 
xlations = 0x6e79d0
stateTree = 
contextPtr = 0x6fae18
i = 1
actions = 0x6d0da0
matchExact = 1 '\001'
match = 
complexMatchState = 0x0
currIndex = -2
typeIndex = 76
modIndex = 0
matchTreeIndex = 
#4  0x7752ebdd in _XtTranslateEvent (w=w@entry=0x6fadc0, 
event=event@entry=0x7fffcda0) at ../../src/TMstate.c:1101
tmRecPtr = 0x6fae08
curEvent = {xev = 0x7fffcda0, event = {modifiers = 0, 
modifierMask = 0, lateModifiers = 0x0, eventType = 4, 
eventCode = 1, eventCodeMask = 0, matchEvent = 0x0, 
standard = 0 '\000'}}
current_state = 
#5  0x77506ef2 in XtDispatchEventToWidget (
widget=widget@entry=0x6fadc0, event=event@entry=0x7fffcda0)
at ../../src/Event.c:906
p = 
was_dispatched = 0 '\000'
call_tm = 
cont_to_disp = 1 '\001'
mask = 
app = 
#6  0x775078dd in _XtDefaultDispatcher (event=0x7fffcda0)
at ../../src/Event.c:1367
mask = 4
dspWidget = 0x6fadc0
was_filtered = 
widget = 0x6fadc0
grabType = remap
pdi = 0x676130
grabList = 0x6faf80
was_dispatched = 0 '\000'
app = 
#7  0x775079b9 in XtDispatchEvent (event=event@entry=0x7fffcda0)
at ../../src/Event.c:1423
was_dispatched = 
safe = 
dispatch_level = 1
starting_count = 0
pd = 
time = 
dispatch = 
app = 0x665550
#8  0x7751366f in XtAppProcessEvent (app=app@entry=0x665550, 
mask=mask@entry=15) at ../../src/NextEvent.c:1397
i = 
cur_time = {tv_sec = 0, tv_usec = 6706512}
d = 0
event = {type = 4, xany = {type = 4, serial = 2677, send_event = 0, 
display = 0x666a90, window = 60817846}, xkey = {type = 4, 
serial = 2677, send_event = 0, display = 0x666a90, 
window = 60817846, root = 678, subwindow = 0, time = 10226550, 
x = 47, y = 17, x_root = 1773, y_root = 320, state = 0, 
keycode = 1, same_screen = 1}, xbutton = {type = 4, serial = 2677, 
send_event = 0, display = 0x666a90, window = 60817846, root = 678, 
subwindow = 0, time = 10226550, x = 47, y = 17, x_root = 1773, 
y_root = 320, state = 0, button = 1, same_screen = 1}, xmotion = {
type = 4, serial = 2677, send_event = 0, display = 0x666a90, 
window = 60817846, root = 678, subwindow = 0, time = 10226550, 
x = 47, y = 17, x_root = 1773, y_root = 320, state = 0, 
is_hint = 1 '\001', same_screen = 1}, xcrossing = {type = 4, 
serial = 2677, send_event = 0, display = 0x666a90, 
window = 60817846, root = 678, subwindow = 0, time = 10226550, 
x = 47, y = 17, x_root = 1773, y_root = 320, mode = 0, detail = 1, 
same_screen = 1, focus = 0, state = 0}, xfocus = {type = 4, 
serial = 2677, send_event = 0, display = 0x666a90, 
window = 60817846, mode = 678, detail = 0}, xexpose = {type = 4, 
serial = 2677, send_event = 0, display = 0x666a90, 
window = 60817846, x = 678, y = 0, width = 0, height = 0, 
count = 10226550}, xgraphicsexpose = {type = 4, serial = 2677, 
send_event = 0, display = 0x666a90, drawable = 60817846, x = 678, 
y = 0, width = 0, height = 0, count = 10226550, major_code = 0, 
minor_code = 47}, xnoexpose = {type = 4, serial = 2677, 
send_event = 0, display = 0x666a90, drawable = 60817846, 
major_code = 678, minor_code = 0}, xvisibility = {type = 4, 
serial = 2677, send_event = 0, display = 0x666a90, 
window = 60817846, state = 678}, xcreatewindow = {type = 4, 
serial = 2677, send_event = 0, display = 0x666a90, 
parent = 6081784

Bug#824746: ITP: Munipack -- An astronomical photometry software package

2016-05-19 Thread Filip Hroch

Package: wnpp
Owner: Filip Hroch 
Severity: wishlist
X-Debbugs-Cc:debian-de...@lists.debian.org,debian-as...@lists.debian.org

* Package name: Munipack
  Version : 0.5.7
  Upstream Author : Filip Hroch 
* URL : http://munipack.physics.muni.cz/
* License : GPL-3
  Programming Lang: Fortran, C++
  Description : An astronomical photometry software package
   Munipack is a general astronomical photometry software package
   designed for both batch and interactive processing of large
   amount of data. One currently implements functions for image
   preprocessing, aperture and  growth-curve photometry, astrometry 
   and photometry calibration, merge of images, light-curves, 
   partial support for Virtual observatory access, FITS files tool 
   and a graphical interface.

It will be maintained within the Debian Astronomy Working Group. A git
repository will be created on alioth [1].

Best regards,
FH

---
[1] https://anonscm.debian.org/cgit/debian-astro/packages/munipack.git

-- 
F. Hroch  e-mail, jabber: hr...@physics.muni.cz, tel.: +420549494470
Dept. of theor. physics and astrophysics, MU Brno, Kotlarska 2,CZ-611 37

Bug#820344: python-oslo.privsep: FTBFS: _StringException: Empty attachments:

Hi,

>  lamby: I tried, but can't reproduce 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820344

I can still reproduce this. I am using an up-to-date sid chroot, with no 
reproducible "gotchas".

(Please prefer to keep this and future pings on the BTS itself - IRC is 
ephemeral in the sense that clients can quit, etc. and its powered by email so 
a much better workflow. Thanks!)


Regards,

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

Bug#823818: debdelta: scale threads on multiple cores

On Wed, 2016-05-18 at 13:55 +0200, A Mennucc1 wrote:
> > As it stands now, it looks like debdelta is threaded only to parallelize
> > download and patching of deltas. Other than that, it seems to be a
> > single thread application.
> >
> > This really shows up when you have multiple cores waiting, while
> > debdelta only utilizes a single core to patch a giant deb package.
> >
> > It would be nicer to have debdelta (or maybe attack the underneath
> > archive library) spawn and utilize all available logical CPUs.
> >
> yes it would be nice and not really difficult to implement. Altough I am
> afraid that debdelta is mostly HD bound, so there may be only marginal
> benefits.

Are you sure about this ?

From the looks, it seems you are using xz for deltas. When patching, I see only
one xz process running, and it consumes only 1 core. The same is reflected in
the output below. I don't think this part of debdelta's operation is bound by
disk.


But then reading xz-util's manpage, I don't think they have multithread support.


rrs@chutzpah:~$ dstat -c -C 0,1,2,3,total -d
   
---cpu0-usage--cpu1-usage--cpu2-usage--cpu3-usage---total-cpu-usage
 -dsk/total-
usr sys idl wai hiq siq:usr sys idl wai hiq siq:usr sys idl wai hiq siq:usr sys 
idl wai hiq siq:usr sys idl wai hiq siq| read  writ
 73   1  23   3   0   0:  3   1  87   9   0   0: 15   1  80   4   0   0:  2   1 
 96   1   0   0: 23   1  71   4   0   0|  10M0 
100   0   0   0   0   0:  1   0  99   0   0   0:  1   1  98   0   0   0:  1   1 
 97   1   0   0: 26   1  73   1   0   0|  64k0 
100   0   0   0   0   0:  1   1  97   0   0   1:  2   0  98   0   0   0:  1   0 
 99   0   0   0: 26   1  74   0   0   0|   0 0 
100   0   0   0   0   0:  0   0 100   0   0   0:  1   1  95   3   0   0:  2   1 
 97   0   0   0: 26   0  73   1   0   0|   016k
 90   1   9   0   0   0:  0   2  94   4   0   0:  5   1  88   6   0   0:  1   2 
 97   0   0   0: 24   2  72   2   0   0|6144k0 
  2   0  98   0   0   0:  1   0  99   0   0   0:100   0   0   0   0   0:  2   1 
 97   0   0   0: 26   1  73   0   0   0|   0 0 
  2   1  78  19   0   0:  8   0  92   0   0   0: 99   1   0   0   0   0:  1   1 
 98   0   0   0: 28   1  67   5   0   0| 240k0 
  1   0  99   0   0   0:  1   1  97   1   0   0:100   0   0   0   0   0:  1   2 
 97   0   0   0: 26   1  73   0   0   0|  96k0 
  0   2  98   0   0   0:  0   1  97   2   0   0:100   0   0   0   0   0:  1   1 
 96   2   0   0: 26   1  72   1   0   0|  64k   12k
 35   0  57   8   0   0:  2   1  96   0   0   1: 56   1  39   4   0   0:  4   2 
 94   0   0   0: 24   1  72   3   0   0|8312k0 
100   0   0   0   0   0:  0   1  99   0   0   0:  1   0  99   0   0   0:  0   2 
 95   3   0   0: 26   1  73   1   0   0| 128k   64k
100   0   0   0   0   0:  3   0  97   0   0   0:  1   1  98   0   0   0:  0   1 
 98   1   0   0: 26   1  73   0   0   0|   0 0 
100   0   0   0   0   0:  0   0 100   0   0   0:  2   1  97   0   0   0:  2   1 
 97   0   0   0: 26   1  74   0   0   0| 128k0 
100   0   0   0   0   0:  1   0  99   0   0   0:  2   0  98   0   0   0:  0   1 
 99   0   0   0: 26   0  74   0   0   0|   0 0 
 85   0  12   3   0   0:  2   2  91   5   0   0:  1   2  94   3   0   0:  3   5 
 90   2   0   0: 22   2  72   3   0   0|8008k0 
100   0   0   0   0   0:  1   1  98   0   0   0:  0   1  99   0   0   0:  1   1 
 97   1   0   0: 25   1  73   1   0   0|   060k
 99   1   0   0   0   0:  2   1  97   0   0   0:  1   0  99   0   0   0:  0   1 
 99   0   0   0: 26   1  73   0   0   0|   0 0 
100   0   0   0   0   0:  1   1  98   0   0   0:  0   0 100   0   0   0:  2   0 
 98   0   0   0: 26   0  74   0   0   0|   0 0 
100   0   0   0   0   0:  0   0 100   0   0   0:  0   1  97   2   0   0:  3   0 
 97   0   0   0: 26   1  73   1   0   0|  64k0 
 71   1  14  14   0   0:  2   3  77  17   0   1:  1   3  96   0   0   0:  1   3 
 95   1   0   0: 19   2  71   8   0   0|  14M0 
100   0   0   0   0   0:  1   0  99   0   0   0:  1   1  95   3   0   0:  3   2 
 95   0   0   0: 26   1  73   0   0   0|   028k
100   0   0   0   0   0:  1   1  98   0   0   0:  1   0  99   0   0   0:  1   1 
 98   0   0   0: 26   1  73   0   0   0|   0 0 
100   0   0   0   0   0:  1   1  96   0   0   2:  0   1  99   0   0   0:  3   2 
 95   0   0   0: 26   1  73   0   0   0|   0 0 
 89   1   8   2   0   0:  6   2  92   0   0   0:  4   1  90   4   0   1:  1   1 
 98   0   0   0: 25   1  72   2   0   0|4480k  104k
100   0   0   0   0   0:  1   2  97   0   0   0:  0   1  99   0   0   0:  2   3 
 95   0   0   0: 26   1  73   0   0   0|   0 0 
100   0   0   0   0   0:  0   1  98   0   0   1:  1   1  96   2   0   0:  2   1 
 97   0   0   0: 26   1  73   1   0   0|   016k
100   0   0   0   0   0:  2   0  98   0   0   0:  1   0  99   0   0   0:  0   1 
 99   0   0   0: 26   1  74   0   0   0| 128k0 
100   0

Bug#824551: cinnamon-settings-daemon: please consider to cherry-pick 0677dbf4e9fead24b6dbbf2465ee3f0609c54865

Hey.

You may want to have a look at:
https://github.com/linuxmint/Cinnamon/issues/5316

I basically proposed what you did already for Debian at upstream, so if
they accept you could drop the debian specific patch :)

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#824747: gv: incorrect input of non-ASCII characters in the file selector

Package: gv
Version: 1:3.7.4-1
Severity: normal

In the file selector, when a non-ASCII character is typed, its byte
sequence is interpreted as ISO-8859-1, which is incorrect in UTF-8
locales. To reproduce, using UTF-8 locales:

1. Start gv.
2. File -> Open ...
3. Type a non-ASCII character, e.g. é

"Ã©" appears instead of "é". In ISO-8859-1, this corresponds to the
bytes c3 a9, which is the encoding of é in UTF-8.

-- 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)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/12 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 gv depends on:
ii  ghostscript-x  9.19~dfsg-1+b1
ii  libc6  2.22-9
ii  libx11-6   2:1.6.3-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxmu62:1.1.2-2
ii  libxt6 1:1.1.5-1
ii  xaw3dg 1.5+E-18.2

Versions of packages gv recommends:
ii  xaw3dg  1.5+E-18.2

gv suggests no packages.

-- no debconf information

Bug#823864: [pkg-lxc-devel] Bug#823864: libpam-cgfs: installing libpam-cgfs from backport on stable prevent session from opening

2016-05-19 Thread Xavier Quost

Hi Evgeni

Sorry for this late answer.

> Strictly speaking bugs about backports should go to
> debian-backports@l.d.o and not the BTS, but I personally do not care, so
> lets keep it here for now.

Ok I will keep this in mind.


> Could you still provide stippets of auth.log and messages around that
> time? Just to crosscheck.

Here are auth.log with libpam-cgfs installed

May 19 11:37:31 pc251270 saslauthd[1938]: detach_tty  : master pid is: 1938
May 19 11:37:31 pc251270 saslauthd[1938]: ipc_init: listening on 
socket: /var/run/saslauthd/mux
May 19 11:37:31 pc251270 sshd[2371]: Server listening on 0.0.0.0 port 22.
May 19 11:37:31 pc251270 sshd[2371]: Server listening on :: port 22.
May 19 11:37:32 pc251270 sshd[2371]: Received signal 15; terminating.
May 19 11:37:32 pc251270 sshd[3058]: Server listening on 0.0.0.0 port 22.
May 19 11:37:32 pc251270 sshd[3058]: Server listening on :: port 22.
May 19 11:37:49 pc251270 kdm: :0[3246]: pam_unix(kdm:session): session opened 
for user xquost by (uid=0)
May 19 11:37:55 pc251270 login[3763]: pam_unix(login:session): session opened 
for user root by LOGIN(uid=0)
May 19 11:37:55 pc251270 login[3801]: ROOT LOGIN  on '/dev/tty1'
May 19 11:38:01 pc251270 login[3804]: pam_unix(login:session): session opened 
for user xquost by LOGIN(uid=0)
May 19 11:38:05 pc251270 login[3814]: pam_unix(login:auth): authentication 
failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost=  user=root
May 19 11:38:08 pc251270 login[3814]: FAILED LOGIN (1) on '/dev/tty1' FOR 
'root', Authentication failure
May 19 11:38:14 pc251270 login[3814]: FAILED LOGIN (2) on '/dev/tty1' FOR 
'root', Authentication failure
May 19 11:38:19 pc251270 login[3814]: pam_unix(login:session): session opened 
for user root by LOGIN(uid=0)
May 19 11:38:19 pc251270 login[3823]: ROOT LOGIN  on '/dev/tty1'
May 19 11:38:29 pc251270 saslauthd[1938]: server_exit : master exited: 1938
May 19 11:38:30 pc251270 sshd[3058]: Received signal 15; terminating.

As I was saying auth.log shows normal login (NB 2 false password as root to 
eased the research in log file)

Here are auth.log with libpam-cgfs uninstalled
May 19 11:40:00 pc251270 saslauthd[2063]: detach_tty  : master pid is: 2063
May 19 11:40:00 pc251270 saslauthd[2063]: ipc_init: listening on 
socket: /var/run/saslauthd/mux
May 19 11:40:00 pc251270 sshd[2416]: Server listening on 0.0.0.0 port 22.
May 19 11:40:00 pc251270 sshd[2416]: Server listening on :: port 22.
May 19 11:40:00 pc251270 sshd[2416]: Received signal 15; terminating.
May 19 11:40:00 pc251270 sshd[3110]: Server listening on 0.0.0.0 port 22.
May 19 11:40:00 pc251270 sshd[3110]: Server listening on :: port 22.
May 19 11:40:12 pc251270 kdm: :0[3298]: pam_unix(kdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=  user=xquost
May 19 11:40:22 pc251270 kdm: :0[3298]: pam_unix(kdm:session): session opened 
for user xquost by (uid=0)
May 19 11:40:31 pc251270 polkitd(authority=local): Registered Authentication 
Agent for unix-session:1 (system bus name :1.28 
[/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path 
/org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
May 19 11:40:39 pc251270 su[4207]: Successful su for root by xquost
May 19 11:40:39 pc251270 su[4207]: + /dev/pts/0 xquost:root
May 19 11:40:39 pc251270 su[4207]: pam_unix(su:session): session opened for 
user root by xquost(uid=1000)


> Do you mean you have other Jessie systems where libpam-cgfs does not
> trigger this behaviour?
Yes, but on those systems, there was no attempt to install lxc

> Do you by any chance have SELinux or AppArmor enabled on these boxes?
Yes, apparmor comes as a requirement of lxc



# apt-get install -t jessie-backports  lxc 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus 
nécessaires :
 linux-headers-4.4.0-0.bpo.1-amd64 linux-headers-4.4.0-0.bpo.1-common 
linux-image-4.4.0-0.bpo.1-amd64 linux-kbuild-4.4
Veuillez utiliser « apt-get autoremove » pour les supprimer.
Les paquets supplémentaires suivants seront installés : 
 apparmor libapparmor-perl libapparmor1 liblxc1 libpam-cgfs libseccomp2 lxcfs
Paquets suggérés :
 apparmor-profiles apparmor-profiles-extra apparmor-docs apparmor-utils 
btrfs-tools lua5.2 lvm2
Les NOUVEAUX paquets suivants seront installés :
 apparmor libapparmor-perl libapparmor1 liblxc1 libpam-cgfs libseccomp2 lxc 
lxcfs
0 mis à jour, 8 nouvellement installés, 0 à enlever et 25 non mis à jour.
Il est nécessaire de prendre 37,0 ko/1 506 ko dans les archives.
Après cette opération, 4 891 ko d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] n

however before filling this bug report, lxc and apparmor were removed

dpkg -l |grep appar 
rc  apparmor  2.9.0-3  
amd64User-space parser ut

Bug#812708: ca-certificates: on fresh debian install typical ssl session fails on Thawte certificates

2016-05-19 Thread Andreas Sewe

FYI, removal of the "Thawte Premium Server CA" causes problems not only
with openssl, but also when Java verifies certificates (e.g., when
installing signed plugins in the Eclipse IDE).

Here's the output of jarsigner:

> jarsigner -verify -certs -verbose 
> ./eclipse/plugins/com.codetrails.aether_1.14.0.v20160518-2203-b207.jar
...
>   [entry was signed on 5/19/16 12:08 AM]
>   X.509, CN=Codetrails GmbH, OU=IT Department, O=Codetrails GmbH, 
> L=Darmstadt, ST=Hessen, C=DE
>   [certificate is valid from 3/1/16 1:00 AM to 5/1/17 1:59 AM]
>   X.509, CN=thawte SHA256 Code Signing CA, O="thawte, Inc.", C=US
>   [certificate is valid from 12/10/13 1:00 AM to 12/10/23 12:59 AM]
>   X.509, CN=thawte Primary Root CA, OU="(c) 2006 thawte, Inc. - For 
> authorized use only", OU=Certification Services Division, O="thawte, Inc.", 
> C=US
>   [certificate is valid from 11/17/06 1:00 AM to 12/31/20 12:59 AM]
>   X.509, EMAILADDRESS=premium-ser...@thawte.com, CN=Thawte Premium Server 
> CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, 
> ST=Western Cape, C=ZA
>   [certificate is valid from 8/1/96 2:00 AM to 1/2/21 12:59 AM]
>   [CertPath not validated: Path does not chain with any of the trust 
> anchors]

With the keystore Oracle ships with Java 1.8.0_91 this verifies fine:

> jarsigner -keystore cacerts.original -verify -certs -verbose 
> ./eclipse/plugins/com.codetrails.aether_1.14.0.v20160518-2203-b207.jar
...
>   [entry was signed on 5/19/16 12:08 AM]
>   X.509, CN=Codetrails GmbH, OU=IT Department, O=Codetrails GmbH, 
> L=Darmstadt, ST=Hessen, C=DE
>   [certificate is valid from 3/1/16 1:00 AM to 5/1/17 1:59 AM]
>   X.509, CN=thawte SHA256 Code Signing CA, O="thawte, Inc.", C=US
>   [certificate is valid from 12/10/13 1:00 AM to 12/10/23 12:59 AM]
>   X.509, CN=thawte Primary Root CA, OU="(c) 2006 thawte, Inc. - For 
> authorized use only", OU=Certification Services Division, O="thawte, Inc.", 
> C=US
>   [certificate is valid from 11/17/06 1:00 AM to 12/31/20 12:59 AM]
>   X.509, EMAILADDRESS=premium-ser...@thawte.com, CN=Thawte Premium Server 
> CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, 
> ST=Western Cape, C=ZA (thawtepremiumserverca)
>   [certificate is valid from 8/1/96 2:00 AM to 1/2/21 12:59 AM]

Note, however, that it doesn't find the "thawte Primary Root CA"
*intermediate* certificate in its keystore, as no alias (like for
"(thawtepremiumserverca)") is shown.

However, the keystore shipped with Debian 8.4 *does* contain that
intermediate certificate:

> keytool -list -alias debian:thawte_primary_root_ca.pem -v -keystore 
> /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/security/cacerts
...
> Alias name: debian:thawte_primary_root_ca.pem
> Creation date: Apr 6, 2016
> Entry type: trustedCertEntry
> 
> Owner: CN=thawte Primary Root CA, OU="(c) 2006 thawte, Inc. - For authorized 
> use only", OU=Certification Services Division, O="thawte, Inc.", C=US
> Issuer: CN=thawte Primary Root CA, OU="(c) 2006 thawte, Inc. - For authorized 
> use only", OU=Certification Services Division, O="thawte, Inc.", C=US
> Serial number: 344ed55720d5edec49f42fce37db2b6d

If this were found by jarsigner, then everything would be fine; that the
root certificate is not trusted is immaterial, as an intermediate
certificate already is. But unfortunately that's not the case. :-(

Hope that helps.

Andreas

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

Bug#824740: [Pkg-telepathy-maintainers] Bug#824740: telepathy-ring: FTBFS: cp: cannot stat './AUTHORS--no-act': No such file or directory

2016-05-19 Thread Emilio Pozuelo Monfort

Control: reassign -1 cdbs 0.4.136

On 19/05/16 12:57, Chris Lamb wrote:
> Source: telepathy-ring
> Version: 2.1.0-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> telepathy-ring fails to build from source in unstable/amd64:
> 
>   [..]

>   dh_installdocs -ptelepathy-ring-dbg ./README ./AUTHORS--no-act
>   cp: cannot stat './AUTHORS--no-act': No such file or directory
>   dh_installdocs: cp --reflink=auto -a ./AUTHORS--no-act 
> debian/telepathy-ring-dbg/usr/share/doc/telepathy-ring-dbg returned exit code 
> 1
>   /usr/share/cdbs/1/rules/debhelper.mk:240: recipe for target 
> 'binary-install/telepathy-ring-dbg' failed
>   make: *** [binary-install/telepathy-ring-dbg] Error 2

telepathy-ring does:

# this has a tight dependency, so we can symlink the doc directories together
DEB_INSTALL_DOCS_telepathy-ring-dbg := --no-act
DEB_INSTALL_CHANGELOGS_telepathy-ring-dbg := --no-act

Looks like a regression in CDBS. Reassigning.

Please reassign back and let us know if this actually is a bug in telepathy-ring
and it is misusing CDBS.

Cheers,
Emilio

Bug#824615: gtk3-nocsd should nest bash completions

Control: tags -1 + fixed-upstream

On 05/18/2016 04:46 AM, Christoph Anton Mitterer wrote:
> Would be nice if the gtk-nocsd binary could continue with
> normal completions (if that's possible), or at least
> with binaries from the search path, e.g.:
> 
> $ gtk-nocsd nauti[TAB] => nautilus
> and if natuilus would have option completion like --help, it would
> be nice if that works as well (but as said, not sure whether
> this is easily possible in bash).

This bug is now fixed upstream:
https://github.com/PCMan/gtk3-nocsd/commit/3861bc89b4df3618b358fbc9359ddd9ddd796a9a

Regards,
Christian

Bug#824614: gtk3-nocsd: doesn't add window decorations to all windows

Control: tags -1 + fixed-upstream

This bug is now fixed upstream:
https://github.com/PCMan/gtk3-nocsd/commit/e9a1e5bf186f2d650ef724b3861d337b7270a400

Regards,
Christian

Bug#824620: gtk3-nocsd: ship /etc/X11/Xsession.d/01-gtk3-nocsd + debconf it?

Control: tags -1 + pending

On 05/18/2016 05:04 AM, Christoph Anton Mitterer wrote:
> As stated in /u/s/d/gtk3-nocsd there are several
> ways to configure gtk3-nocsd.
> 
> a) I think it would perhaps make sense to ship
>/etc/X11/Xsession.d/01-gtk3-nocsd
>(01-dont-disable-gtk-csd is a somewhat misleading name, obviously
>README.Debian should be adapted to the new name)
>with some documentation (as comments) and the respective
>options (i.e. GTK_CSD and GTK3_NOCSD_IGNORE) as a conf file.
>The advantage over letting the user create this is, that
>it get's also cleaned up when the package is purged and does't
>remain forgotten :)

This is fixed in git on collab-maint, and will be part of the next
upload:

https://anonscm.debian.org/cgit/collab-maint/gtk3-nocsd.git/commit/?id=3d6537753dabfd8eb6f6f8fea54549a795b4e398

Regards,
Christian

Bug#824748: tracker.debian.org: VCS link for linux-base is outdated

2016-05-19 Thread Bob Ham

Package: tracker.debian.org
Severity: normal

Dear Maintainer,

The VCS links[0] for the linux-base source package[1] are outdated.
The Debian sources are now kept in a git repository[2].

[0] http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux-base/
[1] https://tracker.debian.org/pkg/linux-base
[2] http://anonscm.debian.org/cgit/kernel/linux.git/

Regards,

Bob Ham


--
Bob Ham 
Software Engineer
Collabora


Open First
Collabora is hiring!
Please check out our latest opportunities here:
http://bit.ly/Collabora-Careers

Bug#824749: RFA: libstoragemgmt

Package: wnpp
Severity: normal

I intend to orphan this package, but my hope is to find a maintainer
whom I could transition this to.

libstoragemgmt is a vendor agnostic library to manage your enterprise
storage needs. It can talk to Enterprise SAN arrays.

The upstream for it is accessible at:
https://github.com/libstorage/libstoragemgmt

For this package, there isn't much install base in Debian, at this time.

Bug#824276: Another one "Something has gone wrong" bug with xrdp

2016-05-19 Thread Vincent Bernat

 ❦ 18 mai 2016 04:09 +0300, Maxim K  :

> xrdp-sesman.log
>
> [20160518-03:56:32] [CORE ] starting sesman with pid 20469
> [20160518-03:56:32] [INFO ] listening...
> [20160518-03:56:41] [INFO ] scp thread on sck 7 started successfully
> [20160518-03:56:41] [INFO ] ++ created session (access granted):
> username max, ip 192.168.0.2:27048 - socket: 7
> [20160518-03:56:42] [INFO ] starting Xvnc session...
> [20160518-03:56:42] [INFO ] starting xrdp-sessvc - xpid=20504 - wmpid=20503
>
>
> Honestly I have no idia which logs to look either. According to this
> one everything is fine with xrdp itself and the problem on the gnome
> side or something.

The bug is unlikely in xrdp since it doesn't contain the string "gone
wrong". You could look at ~/.xsession which may contains more
appropriate logs.

You also need to reaffect the bug properly to an existing package as it
is currently assigned to no package due to the way the Package field was
filed.
-- 
Many pages make a thick book.


signature.asc
Description: PGP signature

Bug#824736: rjava: FTBFS: Makefile.all:38: recipe for target 'libjri.so' failed

2016-05-19 Thread Dirk Eddelbuettel


On 19 May 2016 at 11:56, Chris Lamb wrote:
| Source: rjava
| Version: 0.9-8-2
| Severity: serious
| Justification: fails to build from source
| User: reproducible-bui...@lists.alioth.debian.org
| Usertags: ftbfs
| X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
| 
| Dear Maintainer,
| 
| rjava fails to build from source in unstable/amd64:
| 
|   [..]
[...]
|   gcc -std=gnu99 -o libjri.so Rengine.o jri.o Rcallbacks.o Rinit.o globals.o 
rjava.o  -shared -L/usr/lib/jvm/default-java/jre/lib/amd64/server -ljvm 
-Wl,--export-dynamic -fopenmp  -L/usr/lib/R/lib -lR -lpcre -llzma -lbz2 -lz 
-lrt -ldl -lm -licuuc -licui18n
|   /usr/bin/ld: cannot find -licuuc
|   /usr/bin/ld: cannot find -licui18n
|   collect2: error: ld returned 1 exit status

It is a case of expanded dependencies for icu in R itself which I have not
yet added to the quasi-virtual package r-base-dev to ensure build-time
dependencies.

We are "just" missing some Build-Depends. Will fix.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#824048: Any change in blastp? (Was: Bug#824048: python-biopython: FTBFS: AssertionError: 10 != 1)

2016-05-19 Thread Andreas Tille

Hi Peter

On Thu, May 19, 2016 at 12:32:17PM +0100, Peter Cock wrote:
> Thanks Andreas,

Thanks for your very quick response.
 
> Ah, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824048
> 
> It looks like yet another minor change to the plain text human
> readable output with the latest NCBI BLAST+ v2.3.0 release is to
> blame,
> 
> $ ~/ncbi_blast/2.2.31+/blastp -query Fasta/rose.pro -evalue 1 -subject
> GenBank/NC_005816.faa | grep "Query= "
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> $ ~/ncbi_blast/2.3.0+/blastp -query Fasta/rose.pro -evalue 1 -subject
> GenBank/NC_005816.faa | grep "Query= "
> Query= gi|4959044|gb|AAD34209.1|AF069992_1 LIM domain interacting RING
> 
> The Biopython test was expecting 10 lines with this pattern, but there
> is now only 1. This may or may not break the parser - I've not yet
> checked:
> 
> https://github.com/biopython/biopython/issues/827

This sounds like a very probable explanation for the effect.  It would
be great if you could come up with a patch (or a new release) so I could
update the Debian package.
 
Thanks a lot for the perfect cooperation

  Andreas.

-- 
http://fam-tille.de

Bug#824750: iceowl-l10n: should recommend hunspell-* as alternative to myspell-*

Source: iceowl-l10n
Version: 4.0.0.1-1
Severity: normal
Tags: l10n

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Iceowl locale packages recommend myspell but not hunspell dictionary for
the following locales:

bg ca cs da de-* el es fr he hr hu is it lt nl no pl ru sk sl sv-se uk vi

Please recommend hunspell-* as alternative to myspell-*.

As I understand it, hunspell has features not in myspell (e.g. related
to combining words common in germanic languages), and hunspell-* should
therefore probably be listed first in general.

NB! Please favor myspell-da over hunspell-da: The former contains far
more words (the latter is less strong copyleft which makes sense in
Debian to respect but not to prioritize over technical qualities IMO).

NB! Both hunspell-sv-se and hunspell-sv exist - the former should likely
be favored over the latter (sister project to the myspell-da so likely
similar size and licensing).

NB! hunspell-no is alternative to both myspell-nb-no and myspell-nn-no
(no is country code, not language code).

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXPa8fAAoJECx8MUbBoAEhaigQAJySRQvKeRUmfQEpw4vuBwGn
P4vpI5bok8wRk24bA/xenxvp/gA8dimhGVFDdgedReWeWu1kOYJhmfz2oJ1xa2o4
NwN5tRJj+UfGOAMnjGI6jqb9EhDoVL6ZeZdyG3p2wq6stnqywh6bydF6iHu3f3aX
Sh+EeyzhEmco0b1+WVv8tGf+I7bvJueiSMyuBV5XPYRoShHFOL0BfsMSwSRBkibt
kpI4l+9GDXADpcFYnfaDWgi9GKn0B2II0Q89ayrybOX5rWpOXwfloC1fIoDYCscu
JgkDnk+eGWJOJgKYrRXNI0ijUhBIkQmOLZoLyTByhyytzUCXuJ8QHRXhWxocPMKq
e9K85YG44+6WY49gfH3BmsaQlTjSrjoYAhBdHscY7+xbJiOefNeFdfrFa1Q1tgyS
ZsabSfKKqqzxNJRzCBPlEINm/nV6SwRLdSULu3ykyB1HftRh8cbGI3kPM23/g733
b6gyE5qUCa8giG0x6e7Gh04BZA77Y6rtjBMbBaqu9MlEiXDlWjZ2W1sW/vr/hqJF
ezxrHBDS2MHqFPIN9y8UcczqasxLdzqXPb6h+guJ2CXD3qenaofwtykSHVV4kUg2
WsgM8QcRtKXntZbZ7prnBawwcB1M4nD+y0YtIv//XwbSyIoMWjPvnFVSxBuuBaTB
MU/wr+e9kPG5gMBzEmXt
=EOea
-END PGP SIGNATURE-

Bug#824611: Nagstamon bug

2016-05-19 Thread Dmitry Shachnev

Control: reassign -1 nagstamon 1.0.1-1

Hi Florian,

On Wed, May 18, 2016 at 04:13:46PM +0200, Florian Bruhin wrote:
> This is actually a bug in Nagstamon, discovered by PyQt getting
> stricter about correct @pyqtSlot signatures.

Thanks for tracking down this issue, I am reassigning the bug accordingly.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#824617: gtk3-nocsd: in some cases widget borders are drawn to thick

Control: tags -1 - moreinfo

On Wed, 2016-05-18 at 11:09 +0200, Christian Seiler wrote:
> I cannot reproduce this. Could you provide screenshots with and
> without
> gtk3-nocsd?
Attached... 


> Could you also tell me:
Basically everything I have is a most recent state of Debian sid.

>  - what desktop environment / window manager?
cinnamon / not sure what it actually uses as WM... cinnamon itself?
muffin *is* installed, but no muffin process runs.


>  - what Gtk theme?
Window broders: TraditionalOk (from mate-themes; couldn't test Adwaita
                here, since it doesn't show up in the most recent
                cinnamon version aymore)
Controls: Adwaita (clearlook-phenix is unfortunately broken since the
          most recent gtk3 updates)

>  - any Gtk-related environment variables / special configuration?
not really I think, as mentioned before, I have configured gtk3-nocsd
not to start globally, but run it on the command line.
Also since cinnamon 3.0.2 of today, I have disabled the overlay
scrollbars, which is done via a GTK env var, AFAIK, but the issue
happened before as well.

>  - the exact versions of gtk, glib, gobject, gdk and e.g. nautilus
>    you're using?
$ apt-cache show libgtk-3-0 | grep Version
Version: 3.20.4-1
$ apt-cache show libglib2.0-0 | grep Version
Version: 2.48.1-1
$ apt-cache show gobject-introspection | grep Version
Version: 1.48.0-2
$ apt-cache show libgdk-pixbuf2.0-0 | grep Version
Version: 2.34.0-1
$ apt-cache show nautilus | grep Version
Version: 3.20.1-2


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#824751: zfsutils-linux,zutils: error when trying to install together

Package: zfsutils-linux,zutils
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.6.5.6-2
Control: found -1 1.4-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../zutils_1.4-2_amd64.deb ...
  Unpacking zutils (1.4-2) ...
  dpkg: error processing archive /var/cache/apt/archives/zutils_1.4-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man1/ztest.1.gz', which is also in 
package zfsutils-linux 0.6.5.6-2

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/man/man1/ztest.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


zfsutils-linux=0.6.5.6-2_zutils=1.4-2.log.gz
Description: application/gzip

Bug#823818: debdelta: scale threads on multiple cores

On Thu, 2016-05-19 at 16:54 +0530, Ritesh Raj Sarraf wrote:
> From the looks, it seems you are using xz for deltas. When patching, I see
> only
> one xz process running, and it consumes only 1 core. The same is reflected in
> the output below. I don't think this part of debdelta's operation is bound by
> disk.
> 
> 
> But then reading xz-util's manpage, I don't think they have multithread
> support.

For the completeness of this bug report, the performance issue is only
noticeable on huge deb packages, like the debug symbol ones.

For standard packages, this is not really an issue.

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


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

Bug#824741: keysyms associated with F1 and Shift-F8 are ignored in text input fields

Control: reassign -1 libxm4 2.3.4-10
Control: retitle -1 libxm4 (motif): keysyms associated with F1 and Shift-F8 are 
ignored in text input fields

On 2016-05-19 12:59:21 +0200, Vincent Lefevre wrote:
> In text input fields, such as in the Find and Save As dialog boxes,
> some keysyms are ignored. This is at least the case of:
>   * 0xe9 eacute (é)
>   * 0xdb Ucircumflex (Û)
> 
> However this is no such problem with: èêëâîôûàùïç ÉÈÊËÂÎÔÀÙÏÇ
> 
> Note: The problem is at the keysym level, as if I change my keyboard
> configuration to use other keysyms for the same physical keys, the
> characters appear as expected. Moreover, I can enter these characters
> é and Û with dead keys (dead_acute + e and dead_circumflex + U).

Well, after doing more tests, this is actually more complex.
The problem is that keysyms that correspond to F1 and Shift-F8
*when xpdf is started* do not work.

If I remap the keyboard with xkbcomp while xpdf is running, then the
new mapping is taken into account, except that the keysyms mentioned
above still do not work. For instance, if I swap the F1 & F2 settings
and the F7 & F8 settings while xpdf is running, then this is F2 and
Shift-F7 that do not work.

I reassign this bug to libxm4 since the bug probably occurs at the
Motif level. I notice that libmotif-common provides bindings files
(/usr/share/X11/bindings directory), where one can see settings for
F1 and Shift-F8, but also F10 and Shift-F10. However:
  * I don't have any problem with F10 and Shift-F10.
  * No such bindings files are read when running xpdf, as shown
by strace -f.

I suspect that Motif may have default bindings for F1 and Shift-F8
(the string "_MOTIF_DEFAULT_BINDINGS" appears in strace output).

It is wrong to override the user's keyboard mapping.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#824712: RFH: smokeping

2016-05-19 Thread Antoine Beaupré

On 2016-05-19 05:26:53, Iain R. Learmonth wrote:
> Hi,
>
> In 18/05/16 23:22, Antoine Beaupré wrote:
>> I need help maintaining the smokeping package. I do not really use it
>> anymore and i'd be happy to help people to sponsor it. There's a bunch
>> of obscure bugs all over the place, and while I think the package
>> mostly works, it's just a wild guess since well, I'm not using it
>> right now.
>
> Looks like a candidate for the Internet Measurement Packaging Team. (:
>
> https://qa.debian.org/developer.php?login=pkg-netmeasure-disc...@lists.alioth.debian.org
>
> Would be happy to be a co-maintainer for this package.
>
> If this sounds good I'll add you to the team and we can update the
> maintainer/uploaders fields on the next upload. (:

Hmm... I'm hesitant in joining yet another team here, too much mail. :)

But i'd be happy to share maintenance or even delegate responsability
completely if people are up to it.

Thanks!

A.
-- 
One of the things the Web teaches us is that everything is connected
(hyperlinks) and we all should work together (standards). Too often
school teaches us that everything is separate (many different
'subjects') and that we should all work alone.- Aaron Swartz

Bug#824752: gridengine-client,qtile: error when trying to install together

Package: gridengine-client,qtile
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 8.1.8+dfsg-5
Control: found -1 0.10.5-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package qtile.
  Preparing to unpack .../qtile_0.10.5-1_all.deb ...
  Unpacking qtile (0.10.5-1) ...
  dpkg: error processing archive /var/cache/apt/archives/qtile_0.10.5-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/qsh', which is also in package 
gridengine-client 8.1.8+dfsg-5

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/qsh

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


gridengine-client=8.1.8+dfsg-5_qtile=0.10.5-1.log.gz
Description: application/gzip

Bug#824753: po4a: Please add full nowrap support for strict Text handling

2016-05-19 Thread Sergey Korobitsin

Package: po4a
Version: 0.47-2
Severity: wishlist

Dear Maintainer,
I'm trying to use po4a for translating text documents
written using Markdown markup. po4a has markdown support
in Text module, but I use pandoc flavour of Markdown 
language, and there are some cases where wrapping of
paragraphs in POT (and thus PO) breaks output.

So, I use `nobullets` option and patch I've found here:

https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314748&group_id=30267

In particular, this, the latest one: 

https://alioth.debian.org/tracker/download.php/30267/410622/314748/6576/Text-add-no-wrapoptions-2.patch

And my use case is fully covered: I get no changes to 
text formatting (unless translator will make ones).
It will be convenient for me and possibly others
to get it included to po4a.

P.S. I've already patched Text.pm on my system,
so debsums worries about that.

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

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

Versions of packages po4a depends on:
ii  gettext0.18.1.1-9
ii  libsgmls-perl  1.03ii-32
ii  opensp 1.5.2-10
ii  perl   5.20.2-3+deb8u1
ii  perl-modules   5.20.2-3+deb8u1

Versions of packages po4a recommends:
ii  liblocale-gettext-perl 1.05-8+b1
ii  libterm-readkey-perl   2.32-1+b1
ii  libtext-wrapi18n-perl  0.06-7
ii  libunicode-linebreak-perl  0.0.20140601-2

po4a suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/perl5/Locale/Po4a/Text.pm (from po4a package)

-- 
Bright regards, Sergey Korobitsin,
Chief Research Officer
Arta Software, http://arta.kz/
xmpp:underta...@jabber.arta.kz

--
Information on Derby's internals is scattered over a number of locations:

  1. The code, describes exactly how it works. B)

  -- http://wiki.apache.org/db-derby/HowItWorks

Bug#824754: ITP: r-cran-princurve -- fit a principal curve in arbitrary dimension

2016-05-19 Thread Andreas Tille

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-princurve
  Version : 1.1-12-1
  Upstream Author : Andreas Weingessel 
* URL : http://cran.r-project.org/web/packages/princurve/
* License : GPL
  Programming Lang: GNU R
  Description : fit a principal curve in arbitrary dimension
 GNU R package to fit a principal curve to a data matrix in arbitrary
 dimensions.

Remark: This package is used in the test suite of r-bioc-aroma.light
 and will be maintained by the Debian Med team at
svn://anonscm.debian.org/debian-med/trunk/packages/R/r-cran-princurve/trunk/

Bug#824755: libqglviewer-headers: fails to upgrade from 'sid' - trying to overwrite /usr/include/QGLViewer/config.h

Package: libqglviewer-headers
Version: 2.6.3+dfsg2-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libqglviewer-headers.
  Preparing to unpack .../libqglviewer-headers_2.6.3+dfsg2-1~exp1_all.deb ...
  Unpacking libqglviewer-headers (2.6.3+dfsg2-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libqglviewer-headers_2.6.3+dfsg2-1~exp1_all.deb 
(--unpack):
   trying to overwrite '/usr/include/QGLViewer/config.h', which is also in 
package libqglviewer-dev-qt4 2.6.3+dfsg1-1
  Processing triggers for fontconfig (2.11.0-6.4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libqglviewer-headers_2.6.3+dfsg2-1~exp1_all.deb


cheers,

Andreas


libqglviewer-dev-qt4=2.6.3+dfsg1-1_libqglviewer-headers=2.6.3+dfsg2-1~exp1.log.gz
Description: application/gzip

Bug#824615: gtk3-nocsd should nest bash completions

On Thu, 2016-05-19 at 13:48 +0200, Christian Seiler wrote:
> This bug is now fixed upstream:
> https://github.com/PCMan/gtk3-nocsd/commit/3861bc89b4df3618b358fbc935
> 9ddd9ddd796a9a

Thumbs up :) Thanks for implementing it.

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#824614: gtk3-nocsd: doesn't add window decorations to all windows

On Wed, 2016-05-18 at 10:08 +0200, Christian Seiler wrote:
> I can confirm that, this is weird, I'm pretty sure this wasn't always
> the case. Maybe there was some internal change in gtk3. I'll
> investigate.
Thanks :)


> PS: I dislike CSDs too (which is why I maintain this package), but
> could you please not use language such as "crap"? Thanks!
Well, the problem isn't when people like to add new things like CSDs,
as long as they make it optional, and keep what works with everything
else in the FLOSS world and follows standards and/or long-grown
conventions.
GNOME's behaviour in many ways (not just CSDs) breaks with all these
things (e.g. CSD programs cannot be sanely used in non GNOME Shell
envs), and while things are de jure still "open source", that makes
them IMHO de facto actually quite hostile towards any other free
software, especially when a project of the size as GNOME simply has the
power to passively pressure other fractions enough to follow their
agenda.
And examples like gnome terminal show that it shouldn't be too
difficult to simply support both, CSD / non-CSD envs.
Yes I know, it's for free and one cannot strictly demand anything from
GNOME, but if all projects in the FLOSS world would behave like this,
the whole ecosystem would simply break apart.

I guess that's the simple reason why there are quite a lot people who
have a very strong opinion about things like CSDs, etc..
Since GNOME always showed extremely uncooperative in supporting other
ways, many people are probably beyond the point where they feel that
diplomatic friendliness does anything good for the FLOSS ecosystem as a
whole, which is also the reason why strong language is used.

Apart from that, I don't think that "crap" is really that strong
language,... what would be next? That one wouldn't be allowed to use a
term like "misfeature"? :-(


On Thu, 2016-05-19 at 13:47 +0200, Christian Seiler wrote:
> This bug is now fixed upstream:
> https://github.com/PCMan/gtk3-nocsd/commit/e9a1e5bf186f2d650ef724b386
> 1d337b7270a400

Awesome, thanks for taking care :)


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#824620: gtk3-nocsd: ship /etc/X11/Xsession.d/01-gtk3-nocsd + debconf it?

On Wed, 2016-05-18 at 10:07 +0200, Christian Seiler wrote:
> b) It would perhaps be nice if this was even configurable by
> > debconf,
> >    i.e. the two options GTK_CSD and GTK3_NOCSD_IGNORE.
> I'm a bit skeptical at that - because it would only qualify for a
> debconf prompt with a very low priority (I really wouldn't want to
> show this to everyone installing the package)
Well I have not real strong need for it... so if you say "no", I won't
star to cry ;-)

I don't think "low" would strictly necessary... gtk3-nocsd is probably
mostly installed on desktop systems, or at least something with GUI, so
interactive installation is anyway likely.

But even if it's "low" and doesn't show up per default then,... (see
below)

> , and then people
> would either have to select to show tons of debconf prompts or
> explicitly run dpkg-reconfigure gtk3-nocsd.
- novice users may not even know that it can be configured in the
config file, nor may they stumble over README.Debian (which, btw, I
think can be dropped, if you ship a conf file with inline
documentation).
debconf would be a convenient way to get them notice that feature
- since it's only two options that we control, I'd have expected the
debconf dialogue to be rather simple


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#824756: libhdf4-alt-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/hdf/H4api_adpt.h

Package: libhdf4-alt-dev
Version: 4.2.11-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libhdf4-alt-dev.
  Preparing to unpack .../libhdf4-alt-dev_4.2.11-1~exp1_amd64.deb ...
  Unpacking libhdf4-alt-dev (4.2.11-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libhdf4-alt-dev_4.2.11-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/hdf/H4api_adpt.h', which is also in 
package libhdf4-dev 4.2.10-3.2
  Processing triggers for libc-bin (2.22-7) ...
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libhdf4-alt-dev_4.2.11-1~exp1_amd64.deb


cheers,

Andreas


libhdf4-dev=4.2.10-3.2_libhdf4-alt-dev=4.2.11-1~exp1.log.gz
Description: application/gzip

Bug#824757: supercollider-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/mime/packages/supercollider.xml

Package: supercollider-common
Version: 1:3.7.0~repack-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../supercollider-common_1%3a3.7.0~repack-1_all.deb ...
  Unpacking supercollider-common (1:3.7.0~repack-1) over (1:3.6.6~repack-2-2) 
...
  dpkg: error processing archive 
/var/cache/apt/archives/supercollider-common_1%3a3.7.0~repack-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/mime/packages/supercollider.xml', which is 
also in package supercollider-gedit 1:3.6.6~repack-2-2
  Preparing to unpack .../supercollider-server_1%3a3.7.0~repack-1_amd64.deb ...
  Unpacking supercollider-server (1:3.7.0~repack-1) over (1:3.6.6~repack-2-2) 
...
  Processing triggers for libc-bin (2.22-7) ...
  Processing triggers for shared-mime-info (1.6-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/supercollider-common_1%3a3.7.0~repack-1_all.deb


cheers,

Andreas


supercollider-gedit=1%3.6.6~repack-2-2_supercollider-common=1%3.7.0~repack-1.log.gz
Description: application/gzip

Bug#824759: slepc: Please make (at least experimental) packages with the new upstream version 3.7

2016-05-19 Thread Giacomo Mulas

Source: slepc
Version: 3.6.3.dfsg1-3+b1
Severity: wishlist

Dear Maintainers,

the new slepc major version 3.7 has been released, with quite relevant 
new functionality (i.e. from the changes " Now most solvers allow a 
user-defined criterion to stop iterating based on a callback function").
It will need the new version of petsc to be simultaneously packaged, since
it is not compatible with older petsc versions and cannot be compiled 
against them.
Any chance to have them quickly packaged, at least for experimental? 
I am very much willing to test them, if testers are needed.

Thanks in advance
Giacomo Mulas

Bug#824741: keysyms associated with F1 and Shift-F8 are ignored in text input fields

On 2016-05-19 14:34:06 +0200, Vincent Lefevre wrote:
> I reassign this bug to libxm4 since the bug probably occurs at the
> Motif level. I notice that libmotif-common provides bindings files
> (/usr/share/X11/bindings directory), where one can see settings for
> F1 and Shift-F8, but also F10 and Shift-F10. However:
>   * I don't have any problem with F10 and Shift-F10.
>   * No such bindings files are read when running xpdf, as shown
> by strace -f.
> 
> I suspect that Motif may have default bindings for F1 and Shift-F8
> (the string "_MOTIF_DEFAULT_BINDINGS" appears in strace output).

$ xprop -root _MOTIF_DEFAULT_BINDINGS
_MOTIF_DEFAULT_BINDINGS(STRING) = 
"osfCancel:Escape,Cancel\nosfLeft:Left,KP_Left\nosfUp:Up,KP_Up\nosfRight:Right,KP_Right\nosfDown:Down,KP_Down\nosfEndLine:End,KP_End\nosfBeginLine:Home,Begin,KP_Home\nosfPageUp:Prior,KP_Prior\nosfPageDown:Next,KP_Next\nosfBackSpace:BackSpace\nosfDelete:Delete,KP_Delete\nosfInsert:Insert,KP_Insert\nosfAddMode:ShiftF8\nosfHelp:F1,Help\nosfMenu:ShiftF10,Menu\nosfMenuBar:F10,ShiftMenu\nosfSelect:Select\nosfActivate:KP_Enter,Execute\nosfClear:Clear\nosfUndo:Undo\nosfSwitchDirection:AltReturn,AltKP_Enter"

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#821078: docker.io: install fails when group docker already exists

2016-05-19 Thread Ben Finney

Package: docker.io
Version: 1.8.3~ds1-2
Followup-For: Bug #821078
Control: tags -1 + confirmed

I confirm the same behaviour in version 1.8.3~ds1-2.

=
Setting up docker.io (1.8.3~ds1-2) ...
addgroup: The group `docker' already exists as a system group.
Exiting.
Job for docker.service failed because the control process exited with
error code. See "systemctl status docker.service" and "journalctl -xe"
for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker.io (--configure):
 subprocess installed post-installation script returned error exit
 status 1
Errors were encountered while processing:
 docker.io
Press Return to continue.
=

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

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

Versions of packages docker.io depends on:
ii  adduser  3.114
ii  init-system-helpers  1.33
ii  iptables 1.6.0-2
ii  libapparmor1 2.10-4
ii  libc62.22-7
ii  libdevmapper1.02.1   2:1.02.124-1
ii  libsqlite3-0 3.12.2-1
ii  perl 5.22.2-1

Versions of packages docker.io recommends:
ii  ca-certificates  20160104
ii  cgroupfs-mount   1.2
ii  git  1:2.8.1-1
ii  xz-utils 5.1.1alpha+20120614-2.1

Versions of packages docker.io suggests:
pn  aufs-tools   
pn  btrfs-tools  
ii  debootstrap  1.0.81
ii  lxc  1:2.0.0-3
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information

-- 
 \   “All progress has resulted from people who took unpopular |
  `\  positions.” —Adlai Stevenson |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#824748: tracker.debian.org: VCS link for linux-base is outdated

2016-05-19 Thread Bob Ham

On Thu, 2016-05-19 at 14:10 +0200, Raphael Hertzog wrote:
> Hello,
> 
> On Thu, 19 May 2016, Bob Ham wrote:
> > The VCS links[0] for the linux-base source package[1] are outdated.
> > The Debian sources are now kept in a git repository[2].
> > 
> > [0] http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux-base/
> > [1] https://tracker.debian.org/pkg/linux-base
> > [2] http://anonscm.debian.org/cgit/kernel/linux.git/
> 
> You are mixing up linux and linux-base.

I was indeed but it seems the linux-base package has still been moved to
git and still has the wrong link in its Vcs fields:

http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux-base/README?revision=22946&view=co

https://anonscm.debian.org/cgit/kernel/linux-base.git

Perhaps this bug should be reassigned to linux-base?

-- 
Bob Ham 
Software Engineer
Collabora

Open First
Collabora is hiring!
Please check out our latest opportunities here:
http://bit.ly/Collabora-Careers

Bug#824758: gtk3-nocsd: shows additional widgets that doesn't appear without gtk3-nocsd

Package: gtk3-nocsd
Version: 2-1
Severity: important


Hi.

Settings/versions/drivers/etc. as in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824616#27

I just noted another issue, when running e.g. nautilus with and without
gtk3-nocsd:
With, there is a white field with the text "Application" that goes over the 
whole
width of the window.
Without, there isn't.

Similar things may of course happen in other apps...


Cheers,
Chris.

(same screenshots used as from the tooltip flickering bug)

Bug#824620: gtk3-nocsd: ship /etc/X11/Xsession.d/01-gtk3-nocsd + debconf it?

On 05/19/2016 02:58 PM, Christoph Anton Mitterer wrote:
> [...]
> - since it's only two options that we control, I'd have expected the
> debconf dialogue to be rather simple

Actually, it's just one setting that you need, because LD_PRELOAD
will not be set if GTK_CSD=1 in ~/.xsessionrc or the 01gtk3-nocsd
configuration file in /etc - GTK3_NOCSD_IGNORE is only there to
allow people to set GTK_CSD=0 without having LD_PRELOAD set. It's
actually an option for some very funny corner cases. For just
disabling CSDs by default, just set GTK_CSD=1. I don't think
GTK3_NOCSD_IGNORE should be exposed by debconf at all. If at all,
only GTK_CSD should be exposed.

That said: while I'm still not convinced enough that I will put
in the work to add the debconf stuff, I'll accept a patch for
that if you provide one.

Regards,
Christian

signature.asc
Description: OpenPGP digital signature

Bug#824760: librocksdb4.5: fails to upgrade from 'testing' - trying to overwrite /usr/lib/librocksdb.so.4

Package: librocksdb4.5
Version: 4.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package librocksdb4.5.
  Preparing to unpack .../librocksdb4.5_4.5.1-1_amd64.deb ...
  Unpacking librocksdb4.5 (4.5.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocksdb4.5_4.5.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/librocksdb.so.4', which is also in package 
librocksdb4.1 4.1-1
  Processing triggers for libc-bin (2.22-7) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/librocksdb4.5_4.5.1-1_amd64.deb


cheers,

Andreas


librocksdb4.1=4.1-1_librocksdb4.5=4.5.1-1.log.gz
Description: application/gzip

Bug#760308: add https for additional, optional security layer

2016-05-19 Thread Nicolas Braud-Santoni

Control: tags -1 moreinfo

Holger, what is the expected security improvement?

It's not as if a self-signed cert would make impersonating the onion service
  harder, and forward-secrecy on the exchange is provided by the Tor circuit
  (using the ntor KEX on Curve25519, if I'm not mistaken).


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#824758: gtk3-nocsd: shows additional widgets that doesn't appear without gtk3-nocsd

Control: tags -1 + confirmed

On 05/19/2016 03:05 PM, Christoph Anton Mitterer wrote:
> Settings/versions/drivers/etc. as in:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824616#27
> 
> I just noted another issue, when running e.g. nautilus with and without
> gtk3-nocsd:
> With, there is a white field with the text "Application" that goes over the 
> whole
> width of the window.
> Without, there isn't.

That's actually a menu bar, I've noticed. (Try clicking on it.) Hmmm,
weird, if you try that with older versions of gtk3/Nautilus (e.g.
from Jessie), that doesn't happen. And I'm very sure I did test with
Nautilus earlier in the Stretch cycle, and I don't remember that from
there either, so something has changed.

Will look into it.

Regards,
Christian

signature.asc
Description: OpenPGP digital signature

Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

2016-05-19 Thread Pierre Ynard

I've successfully downgraded most of my system from unstable to jessie,
so this seems to be workable.

Among the things I run, there's only MySQL that can't be downgraded just
like that from unstable's 5.6 to jessie's 5.5, and for which there is
no backport of 5.6; and also libstdc++6 that I can't downgrade from GCC
5 to GCC 4.9 because mysql binaries depend on it. An unsupported MySQL
server is a nice attack vector.

Is that kind of downgrade supposed to be supported? I encountered
configuration migration problems for apt and postfix, shall I file bugs
for these?

I still think this bug should be marked as wontfix because "enjoy 4
years of jessie" is not a real fix to the problem.

Thanks for the guidance,

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."

Bug#820963: Backup with XferMethod smb and Samba 4.2 impossible in Debian Jessie

2016-05-19 Thread Axel Beckert

Hi,

Axel Beckert wrote:
> Ludovic Drolez wrote:
> > Yes, a full fix won't be easy because smbclient output has changed
> > since samba 4.2.
> 
> There seems to be a rather small patch in RedHat's Bugzilla:
> https://bugzilla.redhat.com/show_bug.cgi?id=1294761
> https://bugzilla.redhat.com/attachment.cgi?id=264
[...]

The patch applies without issues to Debian's backuppc package in
Jessie and works fine for me so far.

> Additionally, $Conf{BackupZeroFilesIsFatal} = 1 seems to be necessary.
> Untested yet, but will test it tomorrow together with the Debian
> package of BackupPC.

This is what was written on
https://github.com/backuppc/backuppc/issues/14, but according to
https://bugzilla.redhat.com/show_bug.cgi?id=1294761#c3 the opposite is
the case and it needs to be set to "0", not to "1":

  $Conf{BackupZeroFilesIsFatal} = 0;

That also makes more sense since it previously was "1", at least on
our boxes.

But before we can upload a patched package to stable-proposed-updates,
a fixed package needs to be uploaded to Unstable first.

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

Bug#824617: gtk3-nocsd: in some cases widget borders are drawn to thick

On 05/19/2016 02:20 PM, Christoph Anton Mitterer wrote:
> On Wed, 2016-05-18 at 11:09 +0200, Christian Seiler wrote:
>> I cannot reproduce this. Could you provide screenshots with and
>> without
>> gtk3-nocsd?
> Attached... 

Yikes, those black borders definitely don't happen on my Stretch
laptop.

>>  - what desktop environment / window manager?
> cinnamon

I'm currently installing a VM with cinnamon to try to reproduce this.

Regards,
Christian



signature.asc
Description: OpenPGP digital signature

Bug#815409: qemu-img still segfaults

2016-05-19 Thread Michael Tokarev

19.05.2016 12:01, Hilko Bengen wrote:
> Control: found -1 1:2.6+dfsg-1
> 
> I just tried with the latest qemu version, the problem still persists:

I tried it before uploading 2.6, and marked the bug as found in 2.6+dfsg-1
yesterday.

Thanks,

/mjt

Bug#824761: RM: tuskar-ui -- ROM; FTBFS, deprecated, not maintained upstream

2016-05-19 Thread Thomas Goirand

Package: ftp.debian.org
Severity: normal


Dear FTP masters,

Please remove tuskar-ui from Debian, as it's not maintained upstream, and
it doesn't even work anymore with Django 1.9.

Cheers,

Thomas Goirand (zigo)

Bug#824715: wine32-tools: wineg++ does not link with stdc++

2016-05-19 Thread Jens Reyer

control: tags -1 + patch

Right, a broken /usr/bin/wineg++ is probably not better than no
/usr/bin/wineg++ at all. So let's fix that...
Thanks for testing the tools, since I personally don't use them at all.

The following as /usr/bin/winegcc should work:


#!/bin/sh -e

name=$(basename $0 | cut -d- -f1)

# wineg++ fails to find winebuild in Wine's bindir
# See https://bugs.winehq.org/show_bug.cgi?id=40245
if test -z "$WINEBUILD"; then
export WINEBUILD="/BINDIR/winebuild"
fi

exec /usr/lib/wine/$name $@


I'll commit the fix for wine-development) soon. Given it turns out well
I'll apply it to the wine packaging a bit later.

Greets
jre

Bug#824620: gtk3-nocsd: ship /etc/X11/Xsession.d/01-gtk3-nocsd + debconf it?