Bug#883573: Call for vote on waiving libpam-systemd dependencies' ordering

[Didier 'OdyX' Raboud]

I call for votes on the following resolution with regards to #883573.
The voting period lasts for one week or until the outcome is no longer
in doubt (§6.3.1).

=== Resolution ===

In 2014, it was resolved in #746578 that the libpam-systemd binary package 
alternative dependency on systemd-shim and systemd-sysv shall be set in that 
order, in order to avoid unwanted init system changes accross upgrades. Debian 
Stretch has since been released.

The Committee therefore resolves that:

1. The Technical Commitee decision from 2014-11-15 in bug #746578 is repealed.

This means Debian's normal policies and practices take over and the
libpam-systemd package's dependencies are set free from specific ordering 
constraints.  The migration should be managed according to Debian's usual 
backwards-compatibility arrangements.

=== End Resolution ===

R: Approve resolution and repeal the TC decision from 2014-11-15 in #746578.
F: Further Discussion

--
  OdyX

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

Bug#889924: Clarification

[KatolaZ]

I just wanted to clarify some of the things that were said above.

First of all, Devuan does not want to "extort" anything ;)

Second, OmegaPhil approached us on IRC saying that Devuan "had" to set
Origin, because having it blank was breaking "aptitude changelog",
which "verifies" the source of the repo. I pointed out that, according
to:

 https://wiki.debian.org/DebianRepository/Format#Origin

Origin is an "Optional field indicating the origin of the repository,
a single line of free form text". So, the check currently implemented
in aptitude, based on matching the optional "single line of free form
text" contained in Origin, is *not* useful to "verify" anything. It
can only verify that the distributor (whoever they are, not
necessarily Debian or Ubuntu or Devuan) has put that specific string
in Origin.

We all know that the only way to check that a repo is genuinely from
Debian is by verifying that the corresponding Release files were
signed with the release keys published at:

  https://ftp-master.debian.org/keys.html

so that specific check OmegaPhil is referring to is not adding any
extra level of security.

I personally think that a sane solution would be to have that check
configurable in aptitude, but I don't see it as a priority, TBH. My
personal take is that, if a fix is implemented, the users should be
warned that those extra checks based on Origin are only indicative,
and do not add any level of security. 

Hope this helps to clarify this matter.

Thanks again for your work on Debian and aptitude: it is very much
appreciated.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature

Bug#889859: chemps2: FTBFS on mipsel: test5 segfaults

[Sebastian Wouters]

Dear Aaron,

To be honest, I haven't got the fogiest.

On other architectures, it works fine. And test5 hasn't been individually
changed since v1.8 was released (24 Aug 2016):

https://github.com/SebWouters/CheMPS2/commits/master/tests/test5.cpp.in
https://github.com/SebWouters/CheMPS2/releases

Could it be that it was an individual accidental seg fault, which doesn't
re-occur upon running another time?

Best wishes,
Sebastian

Bug#889952: Imagemagick SIGABRT malformed image

[Johannes Wagner]

Package: imagemagick_6.9.7.4+dfsg-16ubuntu2.debian.tar.xz
Version: ImageMagick 6.9.7-4 Q16

Hello,

Several malformed sample images which crash ImageMagick are attached.

# convert sample1 /dev/null
convert: magick/quantum.c:216: QuantumInfo *DestroyQuantumInfo(QuantumInfo
*): Assertion `quantum_info != (QuantumInfo *) NULL' failed.

//output GDB
Stopped reason: SIGABRT
__GI_raise (sig=sig@entry=0x6) at ../sysdeps/unix/sysv/linux/raise.c:51

Regards,

Johannes Wagner


sample1
Description: Binary data


sample2
Description: Binary data


sample3
Description: Binary data


sample4
Description: Binary data


sample5
Description: Binary data


sample6
Description: Binary data


sample7
Description: Binary data


sample8
Description: Binary data


sample9
Description: Binary data


sample10
Description: Binary data


sample11
Description: Binary data

Bug#889953: libbpp-phyl FTBFS on 32bit: RegisterRatesSubstitutionModel.h:154:36: error: invalid covariant return type

[Adrian Bunk]

Source: libbpp-phyl
Version: 2.3.2-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libbpp-phyl&suite=sid

...
In file included from 
/<>/src/Bpp/Phyl/Io/BppOSubstitutionModelFormat.cpp:113:0:
/<>/src/Bpp/Phyl/Io/../Model/RegisterRatesSubstitutionModel.h:154:36:
 error: invalid covariant return type for 'virtual std::vector bpp::RegisterRatesSubstitutionModel::getModelStates(int) const'
 std::vector getModelStates(int i) const
^~
In file included from 
/<>/src/Bpp/Phyl/Io/../Model/Codon/../AbstractBiblioSubstitutionModel.h:44:0,
 from /<>/src/Bpp/Phyl/Io/../Model/Codon/MG94.h:43,
 from 
/<>/src/Bpp/Phyl/Io/BppOSubstitutionModelFormat.cpp:50:
/<>/src/Bpp/Phyl/Io/../Model/Codon/../AbstractWrappedModel.h:77:25:
 error:   overriding 'virtual std::vector 
bpp::AbstractWrappedModel::getModelStates(int) const'
 std::vector getModelStates(int code) const { return 
getModel().getModelStates(code); }
 ^~

Bug#889954: gajim: please play nicely with gajim-httpupload and gajim-omemo (i.e. break it ;))

[Dominik George]

Package: gajim
Version: 1.0.0~beta1-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As I understand it, Gajim >= 0.98.1~ implements OMEMO and HTTP File
Upload in the core and does not need external plugins for it anymore.
Both plugins are packaged in Debian.

While Gajim seems to ignore the plugins when they are enabled and does
not break, to be certain, I suggest conflicting with gajim-httpupload
and gajim-omemo (not sure if conflicting is the right thing, but you get
the point ;)).

I might as well be wrong with all of that…

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

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

Versions of packages gajim depends on:
ii  gir1.2-gtk-3.03.22.26-2
ii  python3   3.6.4-1
ii  python3-gi3.26.1-2
ii  python3-gi-cairo  3.26.1-2
ii  python3-idna  2.6-1
ii  python3-nbxmpp0.6.3-1
ii  python3-openssl   17.5.0-1
ii  python3-pyasn10.4.2-3

Versions of packages gajim recommends:
ii  alsa-utils  1.1.3-1
ii  aspell-en [aspell-dictionary]   2017.08.24-0-0.1
ii  ca-certificates 20170717
ii  dbus1.12.2-1
ii  fonts-noto-color-emoji  0~20180102-1
ii  gajim-omemo 2.5.4-1
ii  gajim-pgp   1.2.1-2
ii  gir1.2-farstream-0.20.2.8-2
ii  gir1.2-geoclue-2.0  2.4.7-1
ii  gir1.2-gspell-1 1.6.1-1
ii  gir1.2-gst-plugins-base-1.0 1.12.4-1
ii  gir1.2-gstreamer-1.01.12.4-1
ii  gir1.2-gupnpigd-1.0 0.2.4-2
ii  gir1.2-networkmanager-1.0   1.10.2-1
ii  gir1.2-secret-1 0.18.5-5
ii  gstreamer0.10-plugins-ugly  0.10.19-2.1+b3
ii  notification-daemon 3.20.0-2
ii  plasma-workspace [notification-daemon]  4:5.10.5-2+b1
ii  pulseaudio-utils11.1-4
ii  python3-crypto  2.6.1-8
ii  python3-dbus1.2.4-1+b4
ii  python3-gnupg   0.4.1-1
ii  python3-keyring 10.6.0-1
ii  python3-pil 5.0.0-1
pn  python3-precis-i18n 
ii  sox 14.4.2-3

Versions of packages gajim suggests:
ii  avahi-daemon  0.7-3
ii  libxss1   1:1.2.2-1+b2
pn  nautilus-sendto   
pn  python3-avahi 
pn  python3-gconf 
pn  python3-gnome2
ii  python3-kerberos  1.1.14-1
ii  python3-pycurl7.43.0-2+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlp9WtUxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pZf/BAAx5tPF5DF/vbSQEj5xla9oMCfGTTu
b3u7cnGwWTYcWfQFQXF1qqjqy86ySaKKwx6mJOgRO6+fNs2UsXWZkImnuBJOwbdO
CRvNehwvTdBRJqNxs6VarjiYiyWrxIKkvL0igk1f99DDrt35doMCBrTxfVDuybBZ
HnkowXWgoAMSErDzhCnCNEjDEYjqH0iMo6DJTHh7t5/Snd8lmxc0UhzCiFYvb98A
OmI18Jf0/WNAOX2m+l8Y87IYZTaWUsbJxVz6BbAyW8utTc7taKFXA8O4ul/DDpUT
/zHLAQx0CfFeUVD5A4kupAZlkI/+WmQc78+t8zzev348S7R6ipHr4E24Q3Srq2N5
3Qni6LOo+cVOlLmj1RJb60xZOL6BZ2ZF/RjKxTUV22zixL03GyF1/4TFxzizj4a0
F93P124tBufAW3pnK8Ccgpbry5FR7MMlIwiI3PxbItMzz9MVwJShcBhlZwsOaDQa
dbgNHpU/BexxOrw+Bt3RAkWfaq3kmAI5pyCoErB0wj4dKlB35QE8HUr9smUmwGis
TscO8N25k0FQgxuPMh8TgQuEXJlHDCKl/OtMX+DdqU2neTjarBwif39KsglmO6R8
mqk3TvSZC467kN9V8lKXj5XqprF3VIf7R7U490wwuWXv3982fuJeeJHjcdCx3PG5
xGH15VKnxbIrqkg=
=quNi
-END PGP SIGNATURE-

Bug#851868: patch - fix out-of-tree build (e.g. 'make distcheck') with automake >= 1.15

[Vlad Orlov]

Hi,

This is now fixed in all supported versions of Ubuntu [1].
Maybe it's time to fix it in Debian too?


[1] https://bugs.launchpad.net/intltool/+bug/1117944

Bug#889955: ITP: node-import-local -- Use a locally installed version if available

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-import-local
  Version : 1.0.0
  Upstream Author : Sindre Sorhus 
(sindresorhus.com)
* URL : https://github.com/sindresorhus/import-local#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Use a locally installed version if available

 This module lets a globally installed package use a locally installed
version
 of itself if available.
 .
 Useful for CLI tools that want to defer to the user's locally installed
 version when available, but still work if it's not installed locally. For
 example, AVA and XO uses this method.
 .
 Node.js is an event-based server-side JavaScript engine.

Dependency of ava, test framework used by a large number of modules.



signature.asc
Description: OpenPGP digital signature

Bug#889859: chemps2: FTBFS on mipsel: test5 segfaults

[Sebastian Wouters]

Dear Aaron,

Of the three build logs [1]:

First one:

Test project /<>/obj-mipsel-linux-gnu
Start 3: test3
1/3 Test #3: test3    Passed8.10 sec
Start 5: test5
2/3 Test #5: test5 ***Exception: SegFault  9.37
sec
Start 8: test8
3/3 Test #8: test8 ***Exception: SegFault  6.62
sec

33% tests passed, 2 tests failed out of 3

Total Test time (real) =  24.11 sec

The following tests FAILED:
  5 - test5 (SEGFAULT)
  8 - test8 (SEGFAULT)



Second one:

Test project /<>/obj-mipsel-linux-gnu
Start 3: test3
1/3 Test #3: test3    Passed8.38 sec
Start 5: test5
2/3 Test #5: test5    Passed   19.40 sec
Start 8: test8
3/3 Test #8: test8 ***Exception: SegFault  6.53
sec

67% tests passed, 1 tests failed out of 3

Total Test time (real) =  34.35 sec

The following tests FAILED:
  8 - test8 (SEGFAULT)



Third one:

Test project /<>/obj-mipsel-linux-gnu
Start 3: test3
1/3 Test #3: test3    Passed   19.01 sec
Start 5: test5
2/3 Test #5: test5 ***Exception: SegFault  1.75
sec
Start 8: test8
3/3 Test #8: test8    Passed   14.19 sec

67% tests passed, 1 tests failed out of 3

Total Test time (real) =  34.99 sec

The following tests FAILED:
  5 - test5 (SEGFAULT)


It seems that passing or seg fault seems to occur randomly.

Best wishes,
Sebastian

[1]
https://buildd.debian.org/status/logs.php?pkg=chemps2&ver=1.8.5-1&arch=mipsel

Bug#889956: dhex: segfault on save failure

[Peter Gervai]

Package: dhex
Version: 0.68-2+b2
Severity: minor

dhex crashes when file IO returns any error, smells like complete
lack of error handling.

Steps to reproduce:
echo oh-well > foo
chmod a-w foo
dhex foo
 .. edit
 .. try to save
segfault

Bug#889957: RM: rat -- RoQA; dead upstream since 2003, unused, alternatives exist

[Adam Borowski]

Package: ftp.debian.org
Severity: normal


Hi!
There's not exactly a dearth of voip programs, and rat is one that hasn't
seen an upstream release since 2003.  It's irresponsible to ship a networked
program processing untrusted data that's not maintained either upstream nor
in Debian for that long -- it's quite certain that the lack of CVEs is not
because this program is secure but because no one bothers looking.

Popcon 83 inst, 3 vote.

Bug#889958: RM: uclmmbase -- RoQA; dead upstream, RC-buggy, only rdep: rat

[Adam Borowski]

Package: ftp.debian.org
Severity: normal


Hi!
uclmmbase is a library that has last seen an upstream release in 2006, which
was also the last time it had a maintainer upload.  It doesn't look useful
(many alternatives exist), and its only rdep is rat, for which I've just
filed a RM.

Bug#889908: gitlab: missing gem in the Gemfile

[Pirate Praveen]

On വ്യാഴം 08 ഫെബ്രുവരി 2018 10:06 വൈകു, Leopold Palomo-Avellaneda wrote:
> Please, could you give me some workaround to solve this issue?

You will need to set environment variable DB. See
https://salsa.debian.org/ruby-team/gitlab/raw/debian/8.13.11+dfsg1-8/debian/README.Debian




signature.asc
Description: OpenPGP digital signature

Bug#889953: libbpp-phyl FTBFS on 32bit: RegisterRatesSubstitutionModel.h:154:36: error: invalid covariant return type

[Julien Yann Dutheil]

Hi,

I have committed a patch. But there are other errors like:

In file included from /usr/include/c++/7/bits/stl_algobase.h:67:0,
 from /usr/include/c++/7/bits/char_traits.h:39,
 from /usr/include/c++/7/string:40,
 from /usr/include/Bpp/Numeric/VectorExceptions.h:46,
 from /usr/include/Bpp/Numeric/VectorTools.h:43,
 from
/usr/include/Bpp/Numeric/Prob/DiscreteDistribution.h:43,
 from
/usr/include/Bpp/Io/IoDiscreteDistributionFactory.h:43,
 from
/usr/include/Bpp/Io/BppODiscreteDistributionFormat.h:43,
 from
/<>/src/Bpp/Phyl/Io/BppORateDistributionFormat.h:43,
 from
/<>/src/Bpp/Phyl/Io/BppORateDistributionFormat.cpp:40:
/usr/include/c++/7/bits/stl_iterator.h: In function 'decltype
(std::__miter_base(__it.base()))
std::__miter_base(std::move_iterator<_IteratorL>) [with _Iterator =
double*]':
/usr/include/c++/7/bits/stl_iterator.h:1241:5: note: parameter passing for
argument of type 'std::move_iterator' changed in GCC 7.1
 __miter_base(move_iterator<_Iterator> __it)
 ^~~~

which I am unsure how to handle...

Julien.

On Fri, Feb 9, 2018 at 8:41 AM, Adrian Bunk  wrote:

> Source: libbpp-phyl
> Version: 2.3.2-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=libbpp-phyl&suite=sid
>
> ...
> In file included from /<>/src/Bpp/Phyl/Io/
> BppOSubstitutionModelFormat.cpp:113:0:
> /<>/src/Bpp/Phyl/Io/../Model/RegisterRatesSubstitutionModel.h:154:36:
> error: invalid covariant return type for 'virtual std::vector int> bpp::RegisterRatesSubstitutionModel::getModelStates(int) const'
>  std::vector getModelStates(int i) const
> ^~
> In file included from /<>/src/Bpp/Phyl/Io/../Model/Codon/../
> AbstractBiblioSubstitutionModel.h:44:0,
>  from /<>/src/Bpp/Phyl/
> Io/../Model/Codon/MG94.h:43,
>  from /<>/src/Bpp/Phyl/Io/
> BppOSubstitutionModelFormat.cpp:50:
> /<>/src/Bpp/Phyl/Io/../Model/Codon/../AbstractWrappedModel.h:77:25:
> error:   overriding 'virtual std::vector
> bpp::AbstractWrappedModel::getModelStates(int) const'
>  std::vector getModelStates(int code) const { return
> getModel().getModelStates(code); }
>  ^~
>
>


-- 
Julien Y. Dutheil, Ph-D
0 (+49) 4522 763 298

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#882141: closed by Scott Kitterman (Bug#882141: fixed in postfix 3.2.4-1)

[Bastian Blank]

On Fri, Feb 09, 2018 at 01:50:29AM -0500, Scott Kitterman wrote:
> Because I don't get that error when I try to replicate the condition.

So postconf does not fail for you if inet_interfaces lists an ip the
system does not currently have?

> Feb 09 01:28:58 relay02 postmulti[3783]: fatal: parameter inet_interfaces: no 
> local interface found for 1.2.3.4

According to this, postmulti errors out.  And as postconf uses the same
code, I don't see how it would succeed.

> Not sure how to replicate the error you're having.

The problem is a failing postconf/postmulti if the ip does not exists.
And while the generator is called, apart from 127.0.0.1 and ::1, _none_
exist.

Bastian

-- 
Hailing frequencies open, Captain.

Bug#889935: RM: pnetcdf [armel armhf i386 mips mipsel powerpc] -- NBS; no longer built on 32bit architectures

[Alastair McKinstry]

thanks

On 08/02/2018 21:26, Adrian Bunk wrote:
> Package: ftp.debian.org
> Severity: normal
>
>
> pnetcdf (1.9.0-2) unstable; urgency=medium
>
>   * Only build on 64-bit archs. Needed as MPI_OFFSET must now be 8 bytes,
> and the same size as size_t. Closes: #889115
>
>  -- Alastair McKinstry   Thu, 08 Feb 2018 11:40:19 +

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
 believing the innocent had everything to fear, mostly from the guilty but in 
the longer term
 even more from those who say things like “The innocent have nothing to fear.”
 - T. Pratchett, Snuff

Bug#883573: Call for vote on waiving libpam-systemd dependencies' ordering

[Philip Hands]

On Fri, 09 Feb 2018, Didier 'OdyX' Raboud  wrote:
> I call for votes on the following resolution with regards to #883573.
> The voting period lasts for one week or until the outcome is no longer
> in doubt (§6.3.1).
>
> === Resolution ===
>
> In 2014, it was resolved in #746578 that the libpam-systemd binary package 
> alternative dependency on systemd-shim and systemd-sysv shall be set in that 
> order, in order to avoid unwanted init system changes accross upgrades. 
> Debian 
> Stretch has since been released.
>
> The Committee therefore resolves that:
>
> 1. The Technical Commitee decision from 2014-11-15 in bug #746578 is repealed.
>
> This means Debian's normal policies and practices take over and the
> libpam-systemd package's dependencies are set free from specific ordering 
> constraints.  The migration should be managed according to Debian's usual 
> backwards-compatibility arrangements.
>
> === End Resolution ===
>
> R: Approve resolution and repeal the TC decision from 2014-11-15 in #746578.
> F: Further Discussion

I vote:

  R > F

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#889915: libfaad2 in Wheezy contains patches for some security bugs. They were not backported to Jessie.

[Salvatore Bonaccorso]

Hi Fabian,

On Fri, Feb 09, 2018 at 08:26:10AM +0100, Fabian Greffrath wrote:
> tags 889915 +security +jessie
> thanks
> 
> Forwarding this to the security team.

The current issues which were fixed in DLA-1077-1 are all no-dsa, so
thei did not warrant a DSA via security.d.o. Can you fix those issues
via upcoming point releases?

Regards,
Salvatore

Bug#889959: RM: tkrat -- RoQA; dead upstream, 21/7 popcon

[Adam Borowski]

Package: ftp.debian.org
Severity: normal


Hi!
tkrat (ratatosk) is a mail client; these are especially vulnerable to
untrusted input.  This one hasn't seen an upstream release since 2006,
and VCS commit since 2010.  Being long orphaned in Debian, it doesn't look
like anyone will volunteer to port it to new openssl.

Popcon 21 inst, 7 vote.

(No relation to the other "rat" I just also filed RM on.)

Bug#712485:

[Nico Schlömer]

Perhaps it's useful to report which are the offending lines in the build
log. For Trilinos [1], for example, a hidden flags are reported, but I have
no idea why. Can you help me out?

Cheers,
Nico

[1]
https://buildd.debian.org/status/fetch.php?pkg=trilinos&arch=amd64&ver=12.12.1-5&stamp=1517856320&raw=0

Bug#889905: [Pkg-xfce-devel] Bug#889905: xfce4-notifyd: privacy-invasive logging of notification content

[Sergio Gelato]

* Yves-Alexis Perez [2018-02-08 20:38:01 +0100]:
> Hi, thanks for the bug report. Can you provide the upstream bug report on
> this? I can't reproduce with:
> 
> notify-send ' &this' on xfce4-notifyd 0.4.1-1 so maybe it's been
> fixed meanwhile.

The upstream bug numbers are #10027 and #14073. Yes, 0.4.1 includes some of
the associated fixes, although as noted in
https://bugzilla.xfce.org/show_bug.cgi?id=14073#c5
nothing short of xfce4-notifyd parsing the notification string itself will
actually solve the problem, and this planned for 0.4.2 at the earliest.

Apparently, only the body is subject to markup interpretation. Try
notify-send 'markup test' ' &this'
On Debian stretch, this yields:
  xfce4-notifyd[2039]: Failed to set text ' &this' from markup due 
to error parsing markup: Error on line 1 char 19: Odd character '>', expected a 
'=' after attribute name 'this' of element 'like'
(and the body isn't shown to the user, only logged).

> First, it's definitely not xfce4-notifyd sending this to syslog. More likely
> it's just output to stdout/stderr and systemd forwards it to journal and the
> syslog.

The systemd unit file is part of this Debian package, and the information is
being disclosed by xfce4-notifyd. That xfce4-notifyd doesn't call syslog()
directly is just an implementation detail as far as I'm concerned.


signature.asc
Description: PGP signature

Bug#889751: [pkg-gnupg-maint] Bug#889751: scdaemon: BAD PIN since 2.2.4-2 upgrade

[Yves-Alexis Perez]

On Thu, 2018-02-08 at 19:47 -0500, Daniel Kahn Gillmor wrote:
> Control: severity 889751 serious
> 
> Hi Corsac--
> 
> On Wed 2018-02-07 11:28:42 +0100, Yves-Alexis Perez wrote:
> > On Tue, 2018-02-06 at 20:42 +0100, Yves-Alexis Perez wrote:
> > 
> > > since the recent 2.2.4-2 upgrade, when trying to use my smartcard (auth
> > > key for SSH for example), I get:
> > > 
> > > févr. 06 20:37:35 scapa gpg-agent[1793]: scdaemon[26257]: verify CHV2
> > > failed: Bad PIN
> > > févr. 06 20:37:35 scapa gpg-agent[1793]: scdaemon[26257]: app_auth
> > > failed: Bad PIN
> > > févr. 06 20:37:35 scapa gpg-agent[1793]: smartcard signing failed: Bad
> > > PIN
> > > 
> > > even though I'm sure it's the right PIN.
> 
> ugh, i'm sorry to hear this.
> 
> > > At that point I'm a little reluctant in doing another try because it's
> > > the last one before I need to get my admin PIN.
> > 
> > Downgrading scdaemon, gpg-agent and gpgconf to 2.2.4-1 fixes the problem.
> > If
> > you need more information, please ask.
> 
> I think the main likely culprit is 
> debian/patches/scd-Support-KDF-Data-Object-of-OpenPGPcard-V3.3.patch,
> which was cherry-picked from upstream.
> 
> Can you give more detail about what specific smartcard you have?

It's the setup described on https://www.corsac.net/?rub=blog&post=1588 so a
JavaCard running the SmartPGP applet from https://github.com/ANSSI-FR/smartPGP

I'm adding Arnaud to the loop because he's the main developer, and I can
actually see that the last commit (https://github.com/ANSSI-FR/SmartPGP/commit
/78d769b671e429b6e3e7b2454b869a66f269741f) seems very relevant.

So maybe the bug actually lies here rather than in scdaemon.
> 
> can you try rebuilding with that patch removed and testing that?  If
> you'd prefer i upload something to experimental for you to try without
> having to rebuild, let me know and i'll do that.

Yes, I can try a rebuild and report back, but I'll first investigate SmartPGP.

Regards,
-- 
Yves-Alexis

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

Bug#889892: mpv: fix for CVE-2018-6360 breaks youtube playlists

[James Cowgill]

Hi,

Make sure you CC the bug number when you reply, so that other people can
see your comments.

On 08/02/18 14:26, Marc Becker wrote:
> Hello James,
> 
> newer upstream LUA code supports direct urls for playlists, v0.23 code does 
> not.
> To my knowledge our (base) code forces calls 'youtube-dl' again for each 
> playlist
> entry by adding a 'ytdl://'-prefix.
> So FOR THIS VERSION it should not be necessary to check a url when CREATING a
> playlist entry. It is certain to get to filter entries (again) due to their 
> prefix.
> 
> So in short, keep the original:
>> playlist = playlist .. "ytdl://" .. site .. "\n"
> and only filter urls that are returned directly (line 270 ff.) or added to 
> EDL playlists.
> 
> While I am aware this is against "fail early" practices it is closest
> in control flow logic to the original code and there might be cases/sites
> where the 'ytdl://' prefix is needed due to the older LUA logic.

[replied to lower down]

> Additionally:
> If somebody manages to slip in a multiline value for 'site' it's over anyway…
> Up-to-date upstream code does not really handle this either.
> Let's hope the downloader validates its input.

That probably warrants some investigation...

> Glad if I could help and please scream at me if I'm on the wrong track here.

You have been helpful - noone realized there was a regression until you
reported it :)

> Hi James,
> 
> needed too long to compose last message, and missed your
> mail(s), sorry 
> 
> The only problem would arise if there is some internal logic
> that decides to return links to some other protocol type but
> must, for some strange reason, again be handled by 'youtube-dl'.

My fix has already been uploaded now do it would be a bit of a pain to
change it :/  However, I think it is still correct. It effectively
incorporates this upstream commit, so if what I have done is wrong,
upstream has also made a mistake:
https://github.com/mpv-player/mpv/commit/1623430b200c7bf67ec19bcab13ccbe9a494d2c7

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#889859: [Debichem-devel] Bug#889859: chemps2: FTBFS on mipsel: test5 segfaults

[Michael Banck]

Hi,

On Fri, Feb 09, 2018 at 09:26:25AM +0100, Sebastian Wouters wrote:
> First one:
> 
> Test project /<>/obj-mipsel-linux-gnu
> Start 3: test3
> 1/3 Test #3: test3    Passed8.10 sec
> Start 5: test5
> 2/3 Test #5: test5 ***Exception: SegFault  9.37
> sec
> Start 8: test8
> 3/3 Test #8: test8 ***Exception: SegFault  6.62
> sec
> 
> 33% tests passed, 2 tests failed out of 3
> 
> Total Test time (real) =  24.11 sec
> 
> The following tests FAILED:
>   5 - test5 (SEGFAULT)
>   8 - test8 (SEGFAULT)
> 
> 
> 
> Second one:
> 
> Test project /<>/obj-mipsel-linux-gnu
> Start 3: test3
> 1/3 Test #3: test3    Passed8.38 sec
> Start 5: test5
> 2/3 Test #5: test5    Passed   19.40 sec
> Start 8: test8
> 3/3 Test #8: test8 ***Exception: SegFault  6.53
> sec
> 
> 67% tests passed, 1 tests failed out of 3
> 
> Total Test time (real) =  34.35 sec
> 
> The following tests FAILED:
>   8 - test8 (SEGFAULT)
> 
> 
> 
> Third one:
> 
> Test project /<>/obj-mipsel-linux-gnu
> Start 3: test3
> 1/3 Test #3: test3    Passed   19.01 sec
> Start 5: test5
> 2/3 Test #5: test5 ***Exception: SegFault  1.75
> sec
> Start 8: test8
> 3/3 Test #8: test8    Passed   14.19 sec
> 
> 67% tests passed, 1 tests failed out of 3
> 
> Total Test time (real) =  34.99 sec
> 
> The following tests FAILED:
>   5 - test5 (SEGFAULT)
> 
> 
> It seems that passing or seg fault seems to occur randomly.

Yeah, unfortunately, mipsel is not the most stable architecture. I am
not sure what we should do here, we can either agressively retry to
build on mipsel until all tests pass or alternatively ignore test
failures. I don't think it would be easy to just ignore them on mipsel,
so that'd mean we might not catch issues going forward on other arches.

We do ignore testsuite failures for several other packages, but I think
it is way better to fail on testsuite failures and to diagnose them. In
this case, there's probably just not much to diagnose.

The final alternative would be to remove the previous mipsel binaries so
the missing build here will not impact chemps2's testing migration.


Michael

Bug#889953: libbpp-phyl FTBFS on 32bit: RegisterRatesSubstitutionModel.h:154:36: error: invalid covariant return type

[Adrian Bunk]

On Fri, Feb 09, 2018 at 09:34:58AM +0100, Julien Yann Dutheil wrote:
> Hi,
> 
> I have committed a patch.

Thanks.

> But there are other errors like:
>...
> /usr/include/c++/7/bits/stl_iterator.h:1241:5: note: parameter passing for
> argument of type 'std::move_iterator' changed in GCC 7.1
>  __miter_base(move_iterator<_Iterator> __it)
>  ^~~~
> 
> which I am unsure how to handle...

This is not an error, this is a warning.

libbpp-phyl in unstable already has a different so-name than libbpp-phyl
in stable, so any potential stretch -> buster upgrade issues are already
covered.

> Julien.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#889915: libfaad2 in Wheezy contains patches for some security bugs. They were not backported to Jessie.

[Fabian Greffrath]

Hi Salvatore,

Salvatore Bonaccorso wrote:
> The current issues which were fixed in DLA-1077-1 are all no-dsa, so
> thei did not warrant a DSA via security.d.o. Can you fix those issues
> via upcoming point releases?

yes, probably. But I guess that's not Mikulas' point:

Both wheezy and jessie had package version 2.7-8. While wheezy got a fixed
package with 2.7-8+deb7u1, jessie didn't. The fix should be as straight as
uploading the same (source) package to jessie that got uploaded to wheezy.

CC:ing Markus Koschany  who did the upload to wheezy.

Thanks!

 - Fabian

Bug#889915: libfaad2 in Wheezy contains patches for some security bugs. They were not backported to Jessie.

[James Cowgill]

On 09/02/18 09:31, Fabian Greffrath wrote:
> Hi Salvatore,
> 
> Salvatore Bonaccorso wrote:
>> The current issues which were fixed in DLA-1077-1 are all no-dsa, so
>> thei did not warrant a DSA via security.d.o. Can you fix those issues
>> via upcoming point releases?
> 
> yes, probably. But I guess that's not Mikulas' point:
> 
> Both wheezy and jessie had package version 2.7-8. While wheezy got a fixed
> package with 2.7-8+deb7u1, jessie didn't. The fix should be as straight as
> uploading the same (source) package to jessie that got uploaded to wheezy.

... with changelog and version number adjustments (it can never be
exactly the same).

Also, the security tracker claims this affects stretch as well which
would need a separate update.

James



signature.asc
Description: OpenPGP digital signature

Bug#889859: [Debichem-devel] Bug#889859: chemps2: FTBFS on mipsel: test5 segfaults

[Sebastian Wouters]

Hi Michael,


> Yeah, unfortunately, mipsel is not the most stable architecture. I am
> not sure what we should do here, we can either agressively retry to
> build on mipsel until all tests pass or alternatively ignore test
> failures. I don't think it would be easy to just ignore them on mipsel,
> so that'd mean we might not catch issues going forward on other arches.
>
> We do ignore testsuite failures for several other packages, but I think
> it is way better to fail on testsuite failures and to diagnose them. In
> this case, there's probably just not much to diagnose.
>
> The final alternative would be to remove the previous mipsel binaries so
> the missing build here will not impact chemps2's testing migration.
>
>
If it's not too much trouble, I would suggest to retry the build until it
passes?

Seb

Bug#889954: [Pkg-xmpp-devel] Bug#889954: gajim: please play nicely with gajim-httpupload and gajim-omemo (i.e. break it ; ))

[W. Martin Borgert]

On 2018-02-09 09:25, Dominik George wrote:
> As I understand it, Gajim >= 0.98.1~ implements OMEMO and HTTP File
> Upload in the core and does not need external plugins for it anymore.

You are right about HTTP Upload, but OMEMO is still a plugin,
if I'm not mistaken.

> While Gajim seems to ignore the plugins when they are enabled and does
> not break, to be certain, I suggest conflicting with gajim-httpupload
> and gajim-omemo (not sure if conflicting is the right thing, but you get
> the point ;)).

Yes, Conflicts plus Provides and/or Replaces, I assume.

Please join the xmpp-team in salsa.d.o and fix it in the git! :~)
(Only if you like, no pressure intended!)

Bug#889960: debian-policy: stray line break at clean target in section 4.9

[Ferenc Wágner]

Package: debian-policy
Version: 4.1.3.0
Severity: minor

Dear Maintainers,

https://www.debian.org/doc/debian-policy/#main-building-script-debian-rules
reads:

clean (required) This must undo any effects that the build and binary targets
may have had [...]

I think the line break should happen after "clean (required)" not after
"targets".  Please consider fixing this for better flow if you agree.
-- 
Thanks,
Feri.

Bug#889751: [pkg-gnupg-maint] Bug#889751: scdaemon: BAD PIN since 2.2.4-2 upgrade

[Yves-Alexis Perez]

On Fri, 2018-02-09 at 10:10 +0100, Yves-Alexis Perez wrote:
> On Thu, 2018-02-08 at 19:47 -0500, Daniel Kahn Gillmor wrote:
> I'm adding Arnaud to the loop because he's the main developer, and I can
> actually see that the last commit (https://github.com/ANSSI-FR/SmartPGP/comm
> it
> /78d769b671e429b6e3e7b2454b869a66f269741f) seems very relevant.
> 
> So maybe the bug actually lies here rather than in scdaemon.
> > 
> > can you try rebuilding with that patch removed and testing that?  If
> > you'd prefer i upload something to experimental for you to try without
> > having to rebuild, let me know and i'll do that.
> 
> Yes, I can try a rebuild and report back, but I'll first investigate
> SmartPGP.
> 
After a quick chat with Arnaud, it seems that even though there might be fixes
to be done at the applet level, the GnuPG patch doesn't seem ready for prime
time and reverting it might be a good idea. See that thread on gnupg-devel:

https://lists.gnupg.org/pipermail/gnupg-devel/2018-February/033424.html

I did a rebuild with the patch disabled and I can confirm it fixes the issue
for me.

Regards,
-- 
Yves-Alexis

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

Bug#889961: courier-authdaemon: Upgrade failures in 0.68.0-4 package

[Amos Jeffries]

Package: courier-authdaemon
Version: 0.68.0-4+b1
Severity: critical
stop

The Courier authdaemon package is failing to configure during install.
Similar issue happened on the -3 package but I managed to get that to
install with manually stopping all courier processes before upgrading.
That workaround no longer has any effect.


aptitude upgrade
The following partially installed packages will be configured:
  courier-authdaemon courier-imap courier-pop
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up courier-pop (0.78.0-2+b1) ...
A dependency job for courier-pop.service failed. See 'journalctl -xe'
for details.
...


Setting up courier-imap (4.18.1+0.78.0-2+b1) ...
A dependency job for courier-imap.service failed. See 'journalctl -xe'
for details.
invoke-rc.d: initscript courier-imap, action "start" failed.
* courier-imap.service - Courier IMAP Daemon
   Loaded: loaded (/lib/systemd/system/courier-imap.service; enabled;
vendor preset: enabled)
   Active: inactive (dead) since Fri 2018-02-02 20:12:20 NZDT; 1 weeks 0
days ago
 Main PID: 705 (code=exited, status=0/SUCCESS)

Feb 09 21:44:44 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:44:44 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Feb 09 21:45:03 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:45:03 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Feb 09 21:45:09 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:45:09 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Feb 09 21:45:39 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:45:39 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
dpkg: error processing package courier-imap (--configure):
 installed courier-imap package post-installation script subprocess
returned error exit status 1
Setting up courier-authdaemon (0.68.0-4+b1) ...
Job for courier-authdaemon.service failed because the service did not
take the steps required by its unit configuration.
See "systemctl status courier-authdaemon.service" and "journalctl -xe"
for details.
invoke-rc.d: initscript courier-authdaemon, action "start" failed.
* courier-authdaemon.service - Courier Authentification Daemon
   Loaded: loaded (/lib/systemd/system/courier-authdaemon.service;
disabled; vendor preset: enabled)
   Active: failed (Result: protocol) since Fri 2018-02-09 21:45:39 NZDT;
8ms ago
  Process: 4623 ExecStart=/usr/sbin/authdaemond start (code=exited,
status=0/SUCCESS)
 Main PID: 667 (code=exited, status=0/SUCCESS)

Feb 09 21:45:39 rio systemd[1]: Starting Courier Authentification Daemon...
Feb 09 21:45:39 rio systemd[1]: courier-authdaemon.service: Can't open
PID file /run/courier/authdaemon/pid (yet?) after start: No such file or
directory
Feb 09 21:45:39 rio systemd[1]: courier-authdaemon.service: Failed with
result 'protocol'.
Feb 09 21:45:39 rio systemd[1]: Failed to start Courier Authentification
Daemon.
dpkg: error processing package courier-authdaemon (--configure):
 installed courier-authdaemon package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
 courier-pop
 courier-imap
 courier-authdaemon
E: Sub-process /usr/bin/dpkg returned an error code (1)

Setting up courier-pop (0.78.0-2+b1) ...
A dependency job for courier-pop.service failed. See 'journalctl -xe'
for details.
...

Setting up courier-authdaemon (0.68.0-4+b1) ...
Job for courier-authdaemon.service failed because the service did not
take the steps required by its unit configuration.
See "systemctl status courier-authdaemon.service" and "journalctl -xe"
for details.
invoke-rc.d: initscript courier-authdaemon, action "start" failed.
* courier-authdaemon.service - Courier Authentification Daemon
   Loaded: loaded (/lib/systemd/system/courier-authdaemon.service;
disabled; vendor preset: enabled)
   Active: failed (Result: protocol) since Fri 2018-02-09 21:45:41 NZDT;
7ms ago
  Process: 4821 ExecStart=/usr/sbin/authdaemond start (code=exited,
status=0/SUCCESS)
 Main PID: 667 (code=exited, status=0/SUCCESS)

Feb 09 21:45:41 rio systemd[1]: Starting Courier Authentification Daemon...
Feb 09 21:45:41 rio systemd[1]: courier-authdaemon.service: Can't open
PID file /run/courier/authdaemon/pid (yet?) after start: No such file or
directory
Feb 09 21:45:41 rio systemd[1]: courier-authdaemon.service: Failed with
result 'protocol'.
Feb 09 21:45:41 rio systemd[1]: Failed to start Courier Authentification
Daemon.
dpkg: error processing package courier-authdaemon (--configure):
 installed courier-authda

Bug#889963: Use iso_3166-1.mo filename instead of symlink

[Dr. Tobias Quathamer]

Package: localechooser
Version: 2.75
Severity: normal
Tags: patch

Hi,

I spotted a minor issue in localechooser, because I've renamed the
gettext domains in iso-codes to better match the ISO standard. The old
gettext domains are still provided as symlinks, but eventually I'll
remove them.

So long story short: here is a patch for localechooser you might want to
apply.

Regards,
Tobias
From 97f4156829aaea59817512be14ae34a72aeb778c Mon Sep 17 00:00:00 2001
From: "Dr. Tobias Quathamer" 
Date: Thu, 8 Feb 2018 21:04:44 +0100
Subject: [PATCH] Use iso_3166-1.mo filename instead of symlink

---
 get-iso-codes | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/get-iso-codes b/get-iso-codes
index 97e53900..72fba130 100755
--- a/get-iso-codes
+++ b/get-iso-codes
@@ -6,7 +6,7 @@ set -e
 rm -rf debian/iso-codes >/dev/null 2>&1
 mkdir debian/iso-codes
 
-for i in $(find /usr/share/locale/ -name iso_3166.mo); do
+for i in $(find /usr/share/locale/ -name iso_3166-1.mo); do
 	language=$(echo $i | cut -f5 -d/)
 	# If a file exists in iso-codes.updates, then use it
 	# else extract translations from the iso-codes package
-- 
2.11.0



signature.asc
Description: OpenPGP digital signature

Bug#889962: node-mapnik FTBFS with mapnik-vector-tile 1.6.0+dfsg-1

[Adrian Bunk]

Source: node-mapnik
Version: 3.6.2+dfsg-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mapnik.html

...
../src/mapnik_vector_tile.cpp: In static member function 'static 
v8::Local VectorTile::_compositeSync(Nan::NAN_METHOD_ARGS_TYPE)':
../src/mapnik_vector_tile.cpp:626:27: warning: comparison is always false due 
to limited range of data type [-Wtype-limits]
 if (fill_type < 0 || fill_type >= 
mapnik::vector_tile_impl::polygon_fill_type_max)
 ~~^~~
../src/mapnik_vector_tile.cpp: In static member function 'static 
Nan::NAN_METHOD_RETURN_TYPE VectorTile::composite(Nan::NAN_METHOD_ARGS_TYPE)':
../src/mapnik_vector_tile.cpp:1000:27: warning: comparison is always false due 
to limited range of data type [-Wtype-limits]
 if (fill_type < 0 || fill_type >= 
mapnik::vector_tile_impl::polygon_fill_type_max)
 ~~^~~
../src/mapnik_vector_tile.cpp: In static member function 'static 
Nan::NAN_METHOD_RETURN_TYPE VectorTile::addGeoJSON(Nan::NAN_METHOD_ARGS_TYPE)':
../src/mapnik_vector_tile.cpp:3261:27: warning: comparison is always false due 
to limited range of data type [-Wtype-limits]
 if (fill_type < 0 || fill_type >= 
mapnik::vector_tile_impl::polygon_fill_type_max)
 ~~^~~
../src/mapnik_vector_tile.cpp: In static member function 'static void 
VectorTile::EIO_RenderTile(uv_work_t*)':
../src/mapnik_vector_tile.cpp:5147:35: error: 'spherical_mercator' is not a 
member of 'mapnik::vector_tile_impl'
 mapnik::vector_tile_impl::spherical_mercator 
merc(closure->d->tile_size());
   ^~
../src/mapnik_vector_tile.cpp:5151:13: error: 'merc' was not declared in this 
scope
 merc.xyz(closure->x,closure->y,closure->z,minx,miny,maxx,maxy);
 ^~~~
../src/mapnik_vector_tile.cpp:5151:13: note: suggested alternative: 'getc'
 merc.xyz(closure->x,closure->y,closure->z,minx,miny,maxx,maxy);
 ^~~~
 getc
../src/mapnik_vector_tile.cpp:5155:13: error: 'merc' was not declared in this 
scope
 merc.xyz(closure->d->get_tile()->x(),
 ^~~~
../src/mapnik_vector_tile.cpp:5155:13: note: suggested alternative: 'getc'
 merc.xyz(closure->d->get_tile()->x(),
 ^~~~
 getc
mapnik.target.mk:220: recipe for target 
'Release/obj.target/mapnik/src/mapnik_vector_tile.o' failed
make[2]: *** [Release/obj.target/mapnik/src/mapnik_vector_tile.o] Error 1

Bug#886395: reassign to libqt5network5

[Sandro Knauß]

Control: reassign -1 libqt5network5 5.9.2+dfsg-9
Control: notfound -1 2.4.0+dfsg-1
Control: notfound -1 5.7.1+dfsg-3+b1
Control: affects -1 owncloud-client
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-64359

Hey,

I looks like this bug is actually a Qt bug, that's why reassigning the bug 
report. this outcome you can read in the forwarded bug report[1] They point to 
the actual fix:

https://bugreports.qt.io/browse/QTBUG-64359 

agaida used back ported owncloud-client, that do not show this issue.

hefee

[1] https://github.com/owncloud/client/issues/6285

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

Bug#889964: lintian: Don't emit spelling-error-in-patch-description for spelling error patches

[Bas Couwenberg]

Source: lintian
Version: 2.5.74
Severity: normal

Dear Maintainer,

Please tune the spelling-error-in-patch-description tag to not emit it
for spelling error patches (where the description mentions which
spelling errors were fixed).

Kind Regards,

Bas

Bug#889954: [Pkg-xmpp-devel] Bug#889954: gajim: please play nicely with gajim-httpupload and gajim-omemo (i.e. break it ; ))

[Dominik George]

Hi,

> Please join the xmpp-team in salsa.d.o and fix it in the git! :~)
> (Only if you like, no pressure intended!)

I had planned to not register a -guest account on salsa, given that I am
about to become a DD, but that plan was made 9 months ago and as my AM
has been entirely unresponsive for these 9 months, I will have to start
as -guest again and migrate stuff later, which I wanted to avoid…

So, yeah, I will do tonight ☺.

-nik


signature.asc
Description: PGP signature

Bug#889603: texlive-latex-extra: ucs support for Unicode character U+200A (hair space)?

[Petter Reinholdtsen]

Hi Andreas, and thank you for your swift response.  :)

[Andreas Hoenen]
> The problem in your example is telling dblatex to use the XeTeX backend,
> but using the LaTeX engine on the resulting XeTeX file.

Right.  So the fact that utf8 also
trigger the problem is irrelevant?  Is it not needed during build?

You can have a look at the source code in
https://gitlab.com/gunnarwolf/madewithcc-es > if you like.  The 
workaround for
hair space is in Makefile, look for the perl code filtering the tex output.

> You can fix this by replacing your last command with:
> 
> xelatex hairsp.tex

This did help, but the resulting PDF do not look as good as before.  The table
of content have too little space in it (actually the glyphs became bigger.

> or even simpler by replacing your last two commands with:
> 
> dblatex -b xetex hairsp.xml

Tried this, but we still need some editing of the LaTeX source, and thus
need the extra step.

> The resulting PDF document looks fine to me.  Do you agree?  Or can you
> explain your issue further?

I am rather confused about why a single unicode character should cause such
problems, and am unsure what more to say.

-- 
Happy hacking
Petter Reinholdtsen

Bug#889961: courier-authdaemon: Upgrade failures in 0.68.0-4 package

[Amos Jeffries]

It seems that the systemd/systemctl is removing the
/run/courier/authdaemon/pid file underneath courier.

Removing the line "PIDFile=/run/courier/authdaemon/pid" from the
installed .service file resolves this problem and upgrade works fine.

Amos

Bug#888985: [pkg-go] Bug#888985: RFS: irtt/0.9-1 [ITP] (#888985)

[Pete Heist]

> On Feb 9, 2018, at 8:15 AM, Michael Stapelberg  wrote:
> 
> On Fri, Feb 9, 2018 at 2:09 AM, Pete Heist  > wrote:
> 
> From the original warnings you sent I know I’ve fixed all except "I: irtt 
> source: testsuite-autopkgtest-missing”, but a) I’m not seeing that warning 
> and b) I’m seeing two others. So my questions are:
> 
> 1) What are your expectations for 'testsuite-autopkgtest-missing', and why am 
> I not seeing it? There are no unit tests to run.
> 
> Did you apply the ~/.lintianrc I provided? Not doing so would explain the 
> difference. autopkgtest is helpful even if it only compiles the package in 
> question. Why are there no unit tests for your code? :)

Yes I did, I should have included that...

$ lintian --version
Lintian v2.5.74
$ ls -al ~/.lintianrc 
-rw-r--r-- 1 pete pete 94 Feb  7 10:25 /home/pete/.lintianrc
$ cat ~/.lintianrc 
display-info = yes
display-experimental = yes
pedantic = yes
show-overrides = no
color = auto
$

What probably explains your seeing testsuite-autopkgtest-missing and my not is 
that I was previously using dh-make-golang from Debian stable. The current sid 
version of dh-make-golang has added a "Testsuite: autopkgtest-pkg-go” line to 
debian/control, which likely satisfies lintian.

BTW I manually bumped compat-version from 10 to 11 and standards-version from 
4.1.1 to 4.1.3 as recent changes to dh-make-golang which do this aren’t in sid 
yet.

As for unit tests, in short, I haven’t gotten there yet, though there’s a bit 
more to it than that. If you’d like, I can add a few basic ones to satisfy, 
otherwise they’ll go in after one more design issue is sorted out… :)

> 2) Do you care about 'debian-watch-does-not-check-gpg-signature' and 
> 'no-upstream-changelog’? I do not sign the upstream, and the changes are in 
> README.md, in case those should be split out...
> 
> They’re not important for the time being. Of course, if you could start 
> signing upstream and provide a separate changelog file, that would be great.
> 
> Thanks!

Ok, I’ll take a look at these if there’s time.

Thanks, almost there… :)

Bug#867699: fatal: transport 'ext' not allowed

[Ian Jackson]

Jakub Wilk writes ("Re: Bug#867699: fatal: transport 'ext' not allowed"):
> * Ian Jackson , 2017-07-08, 18:30:
> >if this change was done for security reasons, why has it not been done 
> >in stretch ?
> 
> This change was introduced in this commit:
> https://github.com/git/git/commit/f1762d772e9b415a3163abf5f217fc3b71a3b40e
> 
> The commit message doesn't mention any security implications. In fact, 
> it doesn't even explicitly say that it changes the default behavior. :-/
> 
> I suspect it was meant to be hardening, rather than a security fix.

Right.  Do you think we should backport this to stretch ?  I would be
inclined to say "no" because of the compatibility risk, but it seems
arguable to me.

IDK who else might be using ext:.  As for dgit, which is where I
noticed this, the breakage is in the dgit _test suite_.  dgit itself
does not use ext:.  I have no idea whether that's usefully indicative
of other callers' situations.

> See #840014 for a bug that was mitigated thanks to this change.
> Other security bugs that could be exploited via git-remote-ext:
> https://github.com/sociomantic-tsunami/git-hub/issues/197
> https://github.com/seveas/git-spindle/issues/154

Right.  This is why I'm not asking for this change to be reverted.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#889908: gitlab: missing gem in the Gemfile

[Leopold Palomo-Avellaneda]

On 09/02/18 09:32, Pirate Praveen wrote:
> On വ്യാഴം 08 ഫെബ്രുവരി 2018 10:06 വൈകു, Leopold Palomo-Avellaneda wrote:
>> Please, could you give me some workaround to solve this issue?
> 
> You will need to set environment variable DB. See
> https://salsa.debian.org/ruby-team/gitlab/raw/debian/8.13.11+dfsg1-8/debian/README.Debian
> 
> 

Running this:

runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && .
/etc/gitlab/gitlab-debian.conf && export DB RAILS_ENV && rake gitlab:check
RAILS_ENV=production'

I got this:

D, [2018-02-09T10:54:56.488801 #1412] DEBUG -- sentry: ** [Raven] Specified
'postgresql' for database adapter, but the gem is not loaded. Add `gem 'pg'` to
your Gemfile (and ensure its version is at the minimum required by
ActiveRecord). excluded from capture due to environment or should_capture 
callback
rake aborted!
Gem::LoadError: Specified 'postgresql' for database adapter, but the gem is not
loaded. Add `gem 'pg'` to your Gemfile (and ensure its version is at the minimum
required by ActiveRecord).
/usr/share/gitlab/config/environment.rb:5:in `'
Gem::LoadError: pg is not part of the bundle. Add it to Gemfile.
/usr/share/gitlab/config/environment.rb:5:in `'
Tasks: TOP => gitlab:check => gitlab:gitlab_shell:check => environment
(See full trace by running task with --trace)


But, if I run this:

runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && .
/etc/gitlab/gitlab-debian.conf && export DB=all RAILS_ENV && rake gitlab:check
RAILS_ENV=production'

if works.

Checking the Gemfile this part is problematic:


# Supported DBs
ENV["DB"] ||= "mysql"
gem "mysql2", '~> 0.3.16' if ENV["DB"] == "all" || ENV["DB"] == "mysql"
gem "pg", '~> 0.18.2' if ENV["DB"] == "all" || ENV["DB"] == "postgres"


changing this:

-ENV["DB"] ||= "mysql"
+ENV["DB"] ||= "all"

work is all cases.

I don't have sufficient knowledge to see if this is a bug or error from my own,
but there's something wrong here.

Leopold




-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?



signature.asc
Description: OpenPGP digital signature

Bug#889903: python-gnupg needs an explict b-d on 2to3

[Elena ``of Valhalla'']

On 2018-02-08 at 16:31:05 +0100, Matthias Klose wrote:
> python-gnupg needs an explict b-d on 2to3. The binary is now provided in a
> separate package.

will do it asap, thanks

> Please could you also run the testsuite with verbosity=2 ?

I can't think any reason why not, so I will probably also do this in the
same upload

-- 
Elena ``of Valhalla''

Bug#712485:

[Simon Ruderich]

On Fri, Feb 09, 2018 at 09:07:06AM +, Nico Schlömer wrote:
> Perhaps it's useful to report which are the offending lines in the build
> log. For Trilinos [1], for example, a hidden flags are reported, but I have
> no idea why. Can you help me out?

Hello,

Running blhc on the build log lists the offending lines:

NONVERBOSE BUILD: [ 76%] Building CXX object 
packages/nox/src/CMakeFiles/trilinos_nox.dir/NOX_Abstract_Vector.C.o
NONVERBOSE BUILD: [ 97%] Building CXX object 
packages/stokhos/test/UnitTest/CMakeFiles/Stokhos_TpetraCrsMatrixMPVectorUnitTest_Serial.dir/Stokhos_TpetraCrsMatrixMPVectorUnitTest_Serial.cpp.o

I'm not sure if the output can/should be added to the
lintian/build log parser as it can be quite big and I don't know
how the architecture handles custom output.

CCing Bernhard who I think is managing the build log parser.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#889964: lintian: Don't emit spelling-error-in-patch-description for spelling error patches

[Chris Lamb]

tags 889964 + moreinfo
thanks

Hi Bas,

> Please tune the spelling-error-in-patch-description tag to not emit it
> for spelling error patches

Thanks for the report. Could you provide the name of the package that is
triggering this for you so we can write a testcase?


Best wishes,

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

Bug#889964: lintian: Don't emit spelling-error-in-patch-description for spelling error patches

[Sebastiaan Couwenberg]

Control: tags -1 - moreinfo

Hi Chris,

On 02/09/2018 12:18 PM, Chris Lamb wrote:
>> Please tune the spelling-error-in-patch-description tag to not emit it
>> for spelling error patches
> 
> Thanks for the report. Could you provide the name of the package that is
> triggering this for you so we can write a testcase?

My latest grass build triggered this issue, see:

 https://anonscm.debian.org/cgit/pkg-grass/grass.git/tree/debian/patches

Kind Regards,

Bas

Bug#788014: does not start at bootup

[MAtteo HCE Valsasna]

I had a similar instance on wheezy, twice on the same machine.

the machine has many GRE interfaces, for each of them /etc/network/if-
up.d/ntpdate runs ntpdate, and each take 15-20s.
thanks to a lockfile mechanism, each instance of this script is run
sequentially, so they are all able to use the NTP socket.

when ntpd is finally launched, the last ntpdate[10802] is probably
still running, then ntpd finds the socket already bound and fails to
start.

/etc/network/if-up.d/ntpdate and /etc/init.d/ntp  apparently use a
lockfile to prevent this. I tested it by starting /etc/network/if-
up.d/ntpdate and /etc/init.d/ntp in parallel, and it seeems to
work: /etc/init.d/ntp blocks waiting for the lockfile to clear and then
starts successfully. 
but apparently it does not work at boot (failed to start ntpd 2 out of
2 reboots)



MAtteo



09:07:21 HOSTNAME kernel: [9.641010] e1000: eth0 NIC Link is Up
1000 Mbps Full Duplex, Flow Control: None
09:07:21 HOSTNAME kernel: [9.76] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.795365] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.819803] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.845117] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.869878] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.894190] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.918750] ipv6:
addrconf_gre_config(gre_)
09:07:21 HOSTNAME kernel: [9.943501] ipv6:
addrconf_gre_config(gre_) 
09:07:21 HOSTNAME kernel: [   11.016141] ip_tables: (C) 2000-2006
Netfilter Core Team
09:07:21 HOSTNAME kernel: [   11.029841] nf_conntrack version 0.5.0
(16384 buckets, 65536 max)
09:07:21 HOSTNAME kernel: [   11.410229] ip6_tables: (C) 2000-2006
Netfilter Core Team
09:07:27 HOSTNAME kernel: [   13.707481] device eth0 entered
promiscuous mode
09:07:33 HOSTNAME kernel: [   20.384946] eth0: no IPv6 routers present

09:07:34 HOSTNAME ntpdate[1722]: step time server 203.159.70.33 offset
-0.006063 sec
09:07:49 HOSTNAME ntpdate[3306]: adjust time server 203.159.70.33
offset 0.000123 sec
09:08:04 HOSTNAME ntpdate[3368]: adjust time server 203.159.70.33
offset 0.000171 sec
09:08:24 HOSTNAME ntpdate[4947]: adjust time server 203.159.70.33
offset 0.46 sec
09:08:49 HOSTNAME ntpdate[4967]: adjust time server 203.159.70.33
offset 0.000252 sec
09:09:19 HOSTNAME ntpdate[4997]: adjust time server 203.159.70.33
offset 0.000339 sec
09:09:54 HOSTNAME ntpdate[6570]: adjust time server 203.159.70.33
offset 0.000271 sec
09:10:35 HOSTNAME ntpdate[8935]: adjust time server 203.159.70.33
offset 0.000336 sec
09:11:13 HOSTNAME ntpd[10818]: ntpd 4.2.6p5@1.2349-o Wed Oct 28
20:18:41 UTC 2015 (1)
09:11:13 HOSTNAME ntpd[10819]: proto: precision = 0.160 usec
09:11:13 HOSTNAME ntpd[10819]: unable to bind to wildcard address
0.0.0.0 - another process may be running - EXITING
09:11:19 HOSTNAME ntpdate[10802]:  adjust time server 203.159.70.33
offset 0.000376 sec

Bug#889962: node-mapnik FTBFS with mapnik-vector-tile 1.6.0+dfsg-1

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/mapnik/node-mapnik/issues/843

Upsteam is working on 3.6.3 which will support mapnik-vector-tile 1.6.0.

Since node-mapnik is not in testing anyway breaking it with mvt is not
an issue for the time being.

Kind Regards,

Bas

Bug#883573: Call for vote on waiving libpam-systemd dependencies' ordering

[Didier 'OdyX' Raboud]

> R: Approve resolution and repeal the TC decision from 2014-11-15 in #746578.
> F: Further Discussion

I vote R > F

-- 
OdyX

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

Bug#889966: xserver-xorg-video-nouveau: X lockup (cursor still ok), often triggered by video/window resize

[Jonathan McDowell]

Package: xserver-xorg-video-nouveau
Version: 1:1.0.15-2
Severity: normal

I suspect this is going to be hard to diagnose, but I figured I should
report it somewhere. It looks a little like
https://bugs.freedesktop.org/show_bug.cgi?id=93629 but not close enough
that I felt I could follow up there (there's no SCHED_ERROR).

I get occasional freezes with my GF119 setup. It's in dual head mode,
1920x1080 on both monitors, and it seems like the freezes are most
likely to occur when windows containing large images or video are
resized. At that point X freezes with only the mouse cursor still
functional. It is possible to SSH into the machine and cleanly shut it
down, but a restart of X does not fix things. The kernel log contains
messages like the following:

[262263.364045] nouveau :02:00.0: gr: TRAP ch 6 [003fb28000 
systemd-logind[706]]
[262263.364058] nouveau :02:00.0: gr: GPC0/TPC0/TEX: 8049
[262263.364070] nouveau :02:00.0: fifo: read fault at 000472 engine 00 
[PGRAPH] client 01 [GPC0/TEX] reason 02 [PAGE_NOT_PRESENT] on channel 6 
[003fb28000 systemd-logind[706]]
[262263.364072] nouveau :02:00.0: fifo: gr engine fault on channel 6, 
recovering...

or

[330643.579349] nouveau :02:00.0: gr: TRAP ch 6 [003fb2a000 
systemd-logind[718]]
[330643.579363] nouveau :02:00.0: gr: GPC0/TPC0/TEX: 8049
[330643.579379] nouveau :02:00.0: fifo: read fault at 00060a engine 00 
[PGRAPH] client 01 [GPC0/TEX] reason 02 [PAGE_NOT_PRESENT] on channel 6 
[003fb2a000 systemd-logind[718]]
[330643.579382] nouveau :02:00.0: fifo: gr engine fault on channel 6, 
recovering...

(note these are from 2 entirely different boots over a week apart)


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 
520] [10de:1040] (rev a1)
05:03.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA 
G200eW WPCM450 [102b:0532] (rev 0a)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 jmcdowell TICS-User 63523 Feb  9 11:12 
/home/jmcdowell/.local/share/xorg/Xorg.1.log

Contents of most recent Xorg X server log file 
(/home/jmcdowell/.local/share/xorg/Xorg.1.log):
--
[66.832] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() 
failed
[66.832] _XSERVTransMakeAllCOTSServerListeners: server already running
[66.836] (--) Log file renamed from 
"/home/jmcdowell/.local/share/xorg/Xorg.pid-1197.log" to 
"/home/jmcdowell/.local/share/xorg/Xorg.1.log"
[66.836] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[66.836] X Protocol Version 11, Revision 0
[66.836] Build Operating System: Linux 4.9.0-5-amd64 x86_64 Debian
[66.836] Current Operating System: Linux apus 4.14.0-3-amd64 #1 SMP Debian 
4.14.13-1 (2018-01-14) x86_64
[66.836] Kernel command line: BOOT_IMAGE=/vmlinuz-4.14.0-3-amd64 
root=UUID=e8a05bf8-40d0-4082-9648-02b1ec5fe28c ro quiet
[66.836] Build Date: 26 January 2018  04:30:21PM
[66.836] xorg-server 2:1.19.6-1 (https://www.debian.org/support) 
[66.836] Current version of pixman: 0.34.0
[66.836]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[66.836] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[66.836] (==) Log file: "/home/jmcdowell/.local/share/xorg/Xorg.1.log", 
Time: Fri Feb  9 11:12:15 2018
[66.837] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[66.837] (==) No Layout section.  Using the first Screen section.
[66.837] (==) No screen section available. Using defaults.
[66.837] (**) |-->Screen "Default Screen Section" (0)
[66.837] (**) |   |-->Monitor ""
[66.837] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[66.837] (==) Automatically adding devices
[66.837] (==) Automatically enabling devices
[66.837] (==) Automatically adding GPU devices
[66.837] (==) Max clients allowed: 256, resource mask: 0x1f
[66.837] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[66.837]Entry deleted from font path.
[66.837] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[66.837]Entry delete

Bug#889964: lintian: Don't emit spelling-error-in-patch-description for spelling error patches

[Chris Lamb]

tags 889964 + pending
thanks

Thanks Bas. :)  Fixed in Git, pending upload:

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


Regards,

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

Bug#889924: aptitude: obtaining changelogs

[Ansgar Burchardt]

Hi,

FWIW we added a `Changelogs` field to Debian's Release files so tools
like apt or aptitude no longer have to hardcode the source URL for
changelogs for every distribution.  This was requested by the apt
maintainers.

See https://lists.debian.org/debian-dak/2015/08/msg00012.html

Ansgar

Bug#889829: ghc: error while loading shared libraries: libHShaskeline-0.7.3.0-ghc8.0.2.so

[James Clarke]

On 8 Feb 2018, at 19:46, Holger Levsen  wrote:
> 
> On Thu, Feb 08, 2018 at 03:04:22PM +0100, Petter Reinholdtsen wrote:
>> [Clint Adams]
>>> objdump -p /usr/lib/ghc/bin/ghc-pkg | grep RUNPATH
> 
> $ objdump -p /usr/lib/ghc/bin/ghc-pkg | grep RUNPATH
>   RUNPATH
>   
> $ORIGIN/../terminfo-0.4.0.2:$ORIGIN/../ghc-boot-8.0.2:$ORIGIN/../ghc-boot-th-8.0.2:$ORIGIN/../Cabal-1.24.2.0:$ORIGIN/../process-1.4.3.0:$ORIGIN/../pretty-1.1.3.3:$ORIGIN/../directory-1.3.0.0:$ORIGIN/../unix-2.7.2.1:$ORIGIN/../time-1.6.0.1:$ORIGIN/../filepath-1.4.1.1:$ORIGIN/../binary-0.8.3.0:$ORIGIN/../containers-0.5.7.1:$ORIGIN/../bytestring-0.10.8.1:$ORIGIN/../deepseq-1.4.2.0:$ORIGIN/../array-0.5.1.1:$ORIGIN/../base-4.9.1.0:$ORIGIN/../integer-gmp-1.0.0.1:$ORIGIN/../ghc-prim-0.5.0.0:$ORIGIN/../rts
> 
> is what I get. Do you need any more info? I still see this...

Well that's correct; you can see $ORIGIN/../terminfo-0.4.0.2 in there which is
where it should be getting libHSterminfo-0.4.0.2-ghc8.0.2.so, but for some
reason your ld.so is not looking at RUNPATH; once it fails to find it on the
system search path it's supposed to then print something like:

 15470:  search 
path=/usr/lib/ghc/bin/../terminfo-0.4.0.2:/usr/lib/ghc/bin/../ghc-boot-8.0.2:/usr/lib/ghc/bin/../ghc-boot-th-8.0.2:/usr/lib/ghc/bin/../Cabal-1.24.2.0:/usr/lib/ghc/bin/../process-1.4.3.0:/usr/lib/ghc/bin/../pretty-1.1.3.3:/usr/lib/ghc/bin/../directory-1.3.0.0:/usr/lib/ghc/bin/../unix-2.7.2.1:/usr/lib/ghc/bin/../time-1.6.0.1:/usr/lib/ghc/bin/../filepath-1.4.1.1:/usr/lib/ghc/bin/../binary-0.8.3.0:/usr/lib/ghc/bin/../containers-0.5.7.1:/usr/lib/ghc/bin/../bytestring-0.10.8.1:/usr/lib/ghc/bin/../deepseq-1.4.2.0:/usr/lib/ghc/bin/../array-0.5.1.1:/usr/lib/ghc/bin/../base-4.9.1.0:/usr/lib/ghc/bin/../integer-gmp-1.0.0.1:/usr/lib/ghc/bin/../ghc-prim-0.5.0.0:/usr/lib/ghc/bin/../rts/tls/x86_64/x86_64:/usr/lib/ghc/bin/../rts/tls/x86_64:/usr/lib/ghc/bin/../rts/tls/x86_64:/usr/lib/ghc/bin/../rts/tls:/usr/lib/ghc/bin/../rts/x86_64/x86_64:/usr/lib/ghc/bin/../rts/x86_64:/usr/lib/ghc/bin/../rts/x86_64:/usr/lib/ghc/bin/../rts
 (RUNPATH from file /usr/lib/ghc/bin/ghc-pkg)

What version of glibc do you have? Have you got any interesting (to ld.so)
environment variables exported or configuration files changed?

Regards,
James

Bug#889967: vmdebootstrap: Customize script failures are not recognized when running without tty

[Sunil Mohan Adapa]

Package: vmdebootstrap
Version: 1.7-1
Severity: normal
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

When running under a tty, vmdebootstrap fails when the customization script
fails and this is as expected. However, when not running under a tty (such as
when triggered by a CI server) vmdebootstrap does not fail when customization
script fails. This is a simple error in the way customization script is invoked
within vmdebootstrap and the attached patch fixes it.

PS: I know that we are supposed to be using vmdb2 instead but we have not
migrated yet as that needs quite some effort for us.



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

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

Versions of packages vmdebootstrap depends on:
ii  debootstrap 1.0.89
ii  kpartx  0.6.4-5
ii  libjs-sphinxdoc 1.4.9-2
ii  parted  3.2-17
ii  python  2.7.13-2
ii  python-cliapp   1.20160724-2
ii  python-distro-info  0.14
ii  python2.7   2.7.13-2+deb9u2
ii  qemu-utils  1:2.8+dfsg-6+deb9u3

Versions of packages vmdebootstrap recommends:
ii  dosfstools4.1-1
ii  extlinux  3:6.03+dfsg-14.1+deb9u1
ii  grub2-common  2.02~beta3-5
pn  python-guestfs
ii  qemu-system   1:2.8+dfsg-6+deb9u3
ii  qemu-user-static  1:2.8+dfsg-6+deb9u3
ii  squashfs-tools1:4.3-3+deb9u1

Versions of packages vmdebootstrap suggests:
pn  cmdtest  
pn  mbr  
ii  pandoc   1.17.2~dfsg-3
pn  u-boot   

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE5xPDY9ZyWnWupXSBQ+oc/wqnxfIFAlp9icQRHHN1bmlsQG1l
ZGhhcy5vcmcACgkQQ+oc/wqnxfIu9Q/+JIAzqLn6ZHibjFc9QVw+yIu9ylkVuntY
bGQHyCd538O3kajZSTs/Tivge0VKyVREIFI85pCaIuQcBhKl3q/rGU37LYQMVfhB
VOB+bMjLLqCamYmm3GYsBCAIXHXzsz4jJUOhqTC03oMRqVy0TwDeNItu+zrwYS+X
HONqvBakmbj8rUf7aecj+LXgP4nuA52IaRN50ZG/vlWwPP43PgPSD7AIzhFPsTuV
su3kG1q93e4t8TGjzvfc8MkOlF2GLqoeCDQFbD1FC2EZ+paCWAVLQY2Uz3S4+8xi
mZVM/ES6w8WTL17v84vb+q2IYFCXQpwvjxyh36sYSnQ2V6tsRzumG2tYdcvkagrD
Uys+3fkU90Hd/zLNYhluLiDIT0QlA+KfWB3hJ4BE1y0rhmfkXT0vRQVqlGU9oiBW
ioVsvqYfZJF1c+Gny/ld/K1XsI7V9eaOy8o1gsk5Qg6tICtiFKUZnj+4xMumuKNx
K6yUcsJW97BZLSNJk0iXbTlbgLt31OcozkW57po+5LNXK9gBCAbbap/d9xI0S7ZC
bf8oFCmkMcihoQEPTuebWkRcilDTiQuCDFOu1C1/qXAuqTOYkCUn8ek7nkcyal8e
J3qMjimvJPAmz44LSGjkm9AGXomGtPoy2+iDyJ9myDnI5PlPVfCN4nvUmK8Htukq
cipBReRpxn0=
=hDZj
-END PGP SIGNATURE-
>From 023be40b32d9ab1cee1ea84396c52b4f98022fcc Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Fri, 9 Feb 2018 17:00:59 +0530
Subject: [PATCH] Recognize customize script failures without tty

When customization script fails when not running under tty, don't ignore the
error.

Signed-off-by: Sunil Mohan Adapa 
---
 vmdebootstrap/base.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vmdebootstrap/base.py b/vmdebootstrap/base.py
index d090f0e..3ba58b3 100644
--- a/vmdebootstrap/base.py
+++ b/vmdebootstrap/base.py
@@ -164,7 +164,7 @@ class Base(object):
 cliapp.runcmd([script, rootdir, self.settings['image']], 
stdout=tty, stderr=tty)
 except IOError:
 logging.debug('tty unavailable, trying in headless mode.')
-subprocess.call([script, rootdir, self.settings['image']])
+subprocess.check_call([script, rootdir, self.settings['image']])
 
 def append_serial_console(self, rootdir):
 if self.settings['serial-console']:
-- 
2.11.0

Bug#889924: [aptitude] Re: [Aptitude-devel] Bug#889924: [aptitude] Feature request - For changelog download command, can acceptable Origins be configurable? Devuan

[OmegaPhil]

Package: aptitude
Version: 0.8.7-1

Just as a followup on this (despite opening the bug I didn't receive
mail from it after the first response??) -
src/cmdline/cmdline_changelog.cc:do_cmdline_changelog has the following
comment:



  // For real packages/versions, we can do a sanity check on the
  // version and warn the user if it looks like it doesn't have a
  // corresponding source package.



It then proceeds to use aptitude::apt::check_valid_origin shortly after
- so it isn't a security check etc.

The other usage is in src/view_changelog.cc:view_changelog, where it is
probably used as a crutch to avoid validating the changelog data directly:



  // check if we know the origin
  if ( ! aptitude::apt::check_valid_origin(ver) )
{
  check_apt_errors();
  return;
}

...





signature.asc
Description: OpenPGP digital signature

Bug#880014: Call for Votes for new TC member

[Didier 'OdyX' Raboud]

The current number of nominees is: 1
The current number of accepted nominations is: 0.

(The request for accept/decline has just been sent now.)

Cheers,
OdyX

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

Bug#889308: ITA: an

[Paride Legovini]

Control: retitle 889308 ITA: an -- very fast anagram generator
Control: owner 889308 !

I intend to adopt 'an', a package that gave me some good fun on several
occasions (people are strange...).

I prepared a new packaging repository here:

https://salsa.debian.org/paride-guest/an

but as you may guess from d/control I'd like to maintain the package
under salsa.debian.org/debian/, where I already maintain a couple of
packages. As I'm not a Debian Developer, I will need a DD to create a
repository for me and to sponsor the package upload.

The packaging structure follows DEP-14.

Lintian is quite happy about the package I prepared:

http://paste.debian.net/1009476/

but another review by a DD is always welcome.

Best regards,

Paride

Bug#889732: libconfig-model-dpkg-perl: Does not recognize Salsa platform in Vcs field

[Dominique Dumont]

On Friday, 9 February 2018 01:09:21 CET gregor herrmann wrote:
> Maybe accept alioth/anonscm and salsa for now, and remove the former
> once it's shut down.
> Or just switch to salsa. Or don't do nothing now and switch to salsa
> once alioth is history.

Currently cme warns if anonscm is not used and tries to provide default value 
for some known case. I.e the Vcds_Browser value is computed for pkg-perl, ruby 
javascript team.

Currently, I don't really know which are the convention that will be used by 
these teams.

I think I'll sit on this bug until some packaging have migrated on salsa.

All the best
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0

[Michael Hatzold]

Package: swami
Version: 2.0.0+svn389-5
Followup-For: Bug #874051

Dear Maintainer,

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

   * What led up to the situation?

Opening swami


   * 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?

"Speicherzugriffsfehler" which I think ist german for Segfault, but not sure.


dmesg shows on consecutive attempts to open it:

[ 3965.728274] swami[25701]: segfault at 315adf34 ip 7fdf11874d64 sp
7ffd3b177e68 error 4 in libgobject-2.0.so.0.5400.3[7fdf1184+52000]
[ 5635.507587] swami[5610]: segfault at 51b66034 ip 7f58c369dd64 sp
7ffc1ae92038 error 4 in libgobject-2.0.so.0.5400.3[7f58c3669000+52000]
[ 5664.362004] swami[6051]: segfault at fb09fa14 ip 7fda2546dd64 sp
7ffe427aac18 error 5 in libgobject-2.0.so.0.5400.3[7fda25439000+52000]
[ 5688.961412] swami[6316]: segfault at 1708d04 ip 7f96c8682d64 sp
7ffc6f135878 error 4 in libgobject-2.0.so.0.5400.3[7f96c864e000+52000]
[11559.981128] swami[14138]: segfault at 83b40d04 ip 7f4159ca2d64
sp 7ffc11195d88 error 5 in libgobject-2.0.so.0.5400.3[7f4159c6e000+52000]



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



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

Kernel: Linux 4.15.1-towo.2-siduction-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swami depends on:
ii  libc6   2.26-6
ii  libfftw3-single33.3.7-1
ii  libfluidsynth1  1.1.9-1
ii  libglib2.0-02.54.3-2
ii  libgnomecanvas2-0   2.30.3-3
ii  libgtk2.0-0 2.24.32-1
ii  libinstpatch-1.0-0  1.0.0-6
ii  libswami0   2.0.0+svn389-5

Versions of packages swami recommends:
ii  jackd  5

swami suggests no packages.

-- no debconf information

Bug#889968: RFS: inotify-tools/3.14-4

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "inotify-tools"

* Package name : inotify-tools
  Version  : 3.14-4
  Upstream Author  : Radu Voicilas 
* Url  : https://github.com/rvoicilas/inotify-tools/wiki/
* Licenses : GPL-2.1+,LGPL-2.1+
  Programming Lang : C
  Section  : misc

 Inotify is a Linux kernel feature enabling user space programs to
 monitor parts of the filesystem in a efficient way. libinotifytools
 is a thin layer on top of the kernel interface which makes it easy
 to set up watches on many files at once, read events without having
 to deal with low-level I/O, and several utility functions for inotify-
 related string formatting

It builds those binary packages:

  * libinotifytools0
  * libinotifytools0-dev
  * inotify-tools

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

https://mentors.debian.net/package/inotify-tools

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/i/inotify-tools/inotify-tools_3.14-4.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/iu-guest/inotify-tools.git

More information about inotify-tools can be obtained from
https://github.com/rvoicilas/inotify-tools/wiki/


Changes since last upload:

  * Upload to unstable
  * Enable all paranoid options of dpkg-buildflags(1)
  * Mark packages as multiarch-compatible (Closes: #875462)
  * Update Vcs-* fields in debian/control.
  * Update standards version to 4.1.3 (no changes needed)
  * Drop explicit dependency on autotools (implied by debhelper-10)
  * Use secure URL when referencing to copyright-format
  * Remove lintian-override about embedded javascript library.
Lintian now knows, that there is nothing can be done in case of
Doxygen.
  * Add sanity-check symbols into symbols file.

Regards,
  Dmitry Bogatov

Bug#889969: juce-modules-source: support LV2

[IOhannes m zmoelnig]

Package: juce-modules-source
Version: 5.2.1~repack-1
Severity: wishlist

there's preliminary support for LV2 support in debian/, but it seems that it
doesn't get included in the shipped packages.

Bug#889953: libbpp-phyl FTBFS on 32bit: RegisterRatesSubstitutionModel.h:154:36: error: invalid covariant return type

[Andreas Tille]

Hi Julien,

On Fri, Feb 09, 2018 at 09:34:58AM +0100, Julien Yann Dutheil wrote:
> I have committed a patch. But there are other errors like:

Thanks for the quick response.  For future pushes can you please make
sure two things:

   1. Add DEP3 headers to the patch - at least Author, Last-Updated and
  Description, if applicable Bug-Debian.
   2. Close fixed bugs in changelog

I've pushed my changes in case you have no idea what I mean.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#889924: aptitude: obtaining changelogs

[David Kalnischkies]

On Fri, Feb 09, 2018 at 12:42:12PM +0100, Ansgar Burchardt wrote:
> FWIW we added a `Changelogs` field to Debian's Release files so tools
> like apt or aptitude no longer have to hardcode the source URL for
> changelogs for every distribution.  This was requested by the apt

libapt has the pkgAcqChangelog class which can be used for this, e.g.

new pkgAcqChangelog(&Fetcher, Ver, ".");

to download the changelog file to the current directory – without giving
a path it will us a temporary file. See apt-private/private-download.cc
and especially DoChangelog for the implementation of "apt(-get)
changelog" as a complete example.

Perhaps this is another command aptitude could delegate entirely by
calling apt – but I don't know aptitude specifics.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#888605: [gajim] Regression: kwallet integration missing

[Charlemagne Lasse]

Source: gajim
Source-Version: 1.0.0~beta1-1

Seems to work here. Thanks

Bug#650519: No longer crashes with KJV

[Teus Benschop]

tags + fixed
thanks

Hi,

Sorry for the very late response to this bug report.

I have tried it on Bibletime version 2.11.1.
The crash described in this bug report does not occur in this version.
It must have been fixed along the way.

If it still happens on your system with this version, 2.11.1, may you
provide a crash log.

Thank you for reporting this and for your contribution to Debian.

Bug#889970: ITP: horizon-eda -- EDA layout and schematic package

[Wookey]

Package: wnpp
Severity: wishlist
Owner: Wookey 

* Package name: horizon-eda
  Version : 0.2018-02
  Upstream Author : Lukas Kramer 
* URL : https://github.com/carrotIndustries/horizon
* License : GPL-3
  Programming Lang: C++
  Description : EDA layout and schematic package

 Electronic design package, covering the complete design flow from 
 schematic entry to gerber export. Includes interactive routing,
 rule-based DRC, 3D board layout, and a unified, netlist-aware, editor
 from symbol to board. The fundamental difference from KiCAD is the
 modern library management based around actual part IDs. It's a C++
 application that runs on Linux and Windows.


This is a fairly new package, presented at FOSDEM 2018. It is still
early in development, but it's already quite useable. It is an
alternative to KiCAD differentiated by fundamentally different choices
about library management.

I've packaged it in order to try it :-)

Bug#889344: O: commons-vfs -- Java API for accessing various filesystems

[Emmanuel Bourg]

Control: Close -1

This package is team maintained.

Bug#673033: Confirmed

[Teus Benschop]

Control: tags + confirmed
thanks

Hi,

Sorry for the late response to this bug report.

The bug still occurs in version 1.7.3 of diatheke.

The symptoms as you describe still occur in this new version.

Bug#862397: (no subject)

[Ken Milmore]

I came across this bug when using the Unison file synchroniser.  I have 
been able to reproduce it reliably as follows: Simply open a directory 
with Thunar and then execute the following shell fragment inside the 
same directory:


# while true ; do touch a ; mv a b ; rm b ; done

The Thunar window will become unresponsive almost immediately.

I can confirm that the above mentioned patch from Xfce upstream does 
indeed fix the issue. The patch already seems to have been rolled out in 
Ubuntu.



I would strongly recommend applying this patch in the next stable point 
release of Debian - it has a major effect on usability of the Xfce desktop.

Bug#673033: Confirmed

[Teus Benschop]

tags + confirmed + upstream + fixed
thanks

The bug appears to be fixed upstream.
It was tested and confirmed to be fixed in upstream version 1.8.1.
The upstream version is available here:
http://www.crosswire.org/ftpmirror/pub/sword/source/v1.8/
Once the package maintainer will package this version, I expect this bug to
be fixed.

On Fri, 9 Feb 2018 at 14:41 Teus Benschop  wrote:

> Control: tags + confirmed
> thanks
>
> Hi,
>
> Sorry for the late response to this bug report.
>
> The bug still occurs in version 1.7.3 of diatheke.
>
> The symptoms as you describe still occur in this new version.
>
>

Bug#888073: Multiarch interpreter names for traditional architectures

[Aurelien Jarno]

On 2018-02-06 01:55, Javier Serrano Polo wrote:
> Debian glibc officially supports multiarch interpreter names, even for
> traditional architectures. For instance, the multiarch interpreter for
> x86_64 is /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 . There is
> consensus among Debian-based distros.

The notion of "multiarch interpreter" doesn't exist. On debian x86_64,
the program interpreter is /lib64/ld-linux-x86-64.so.2 just like any
other x86_64 distribution.

Aurelien

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

Bug#889961: courier-authdaemon: Upgrade failures in 0.68.0-4 package

[J Mo]

I was working on this yesterday. First noticed it about a week ago. Here 
are the upstream bugs:


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

https://github.com/systemd/systemd/issues/8085



And the money quotes:

"looking at the bigger picture here: This change in systemd, while with 
security in mind, changes the way PIDfiles have been handled for the 
last ... forever."


"and who will be blamed (again)? systemd of course, "breaking all the 
things again".


And rightfully so. This is systemd breaking shit again for fun.



On 02/09/2018 02:33 AM, Amos Jeffries wrote:

It seems that the systemd/systemctl is removing the
/run/courier/authdaemon/pid file underneath courier.

Removing the line "PIDFile=/run/courier/authdaemon/pid" from the
installed .service file resolves this problem and upgrade works fine.

Amos

Bug#887107: Bug #887107 https://i18n.debian.org/material/data/unstable.gz not updated since 2017-11-23

[Laura Arjona Reina]

Hi all

I see there are some packages excludes from the gen-material script, due to
different issues:

https://anonscm.debian.org/cgit/debian-l10n/dl10n.git/tree/etc/dl10n.conf

Maybe we can workaround the problem adding the packages that are problematic now
to the exclusion list.
I'll try to put some time on this later.

Cheers
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#888073: Multiarch interpreter names for traditional architectures

[Javier Serrano Polo]

El dv 09 de 02 de 2018 a les 15:02 +0100, Aurelien Jarno va escriure:
> The notion of "multiarch interpreter" doesn't exist.

It does exist, but you do not accept it. You are now denying the
official support that exists in Debian.
Use /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 as the program
interpreter and the program will work perfectly in Debian and
derivatives.


smime.p7s
Description: S/MIME cryptographic signature

Bug#853527: lmms: ftbfs with GCC-7

[Dmitry Eremin-Solenikov]

Package: src:lmms
Followup-For: Bug #853527

LMMS is out of testing for quite a long time. Any progress on uploading
1.1.3-8 or packaging 1.1.90?

-- 
With best wishes
Dmitry

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

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

Bug#889972: ITP: node-hullabaloo-config-manager -- Manages complex Babel config chains

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-hullabaloo-config-manager
  Version : 1.1.1
  Upstream Author : Mark Wubben (https://novemberborn.net/)
* URL :
https://github.com/novemberborn/hullabaloo-config-manager#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Manages complex Babel config chains

 This module manages complex Babel config chains, avoiding duplicated
work and
 enabling effective caching.
 .
 Config sources and plugin and preset dependencies can be hashed and used as
 cache keys. The cache keys and generated module can be verified to
avoid having
 to repeatedly resolve the config chains, and to be sure a previously
 transformation result can be reused.
 .
 This module is used by AVA, a futuristic test runner.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature

Bug#877388: s-nail adoption

[Paride Legovini]

Dear Hilko,

If you didn't change your mind, I would like to adopt s-nail. I used it
quite a few times when developing email sending scripts and it always
served me well. I would be happy to take care of its Debian package.

I took a look at the packaging and I see it's up-to-date with the latest
upstream release and you're using the classic branch structure I'm
already familiar with. I would like to move the repository to salsa
(under the "debian" group, the equivalent of collab-maint). I already
maintain a couple of packages there.

I am not a DD, so I will need support in creating the repository and
sponsorship for the upload.

Best regards,

Paride



signature.asc
Description: OpenPGP digital signature

Bug#889973: seahorse FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: seahorse
Version: 3.20.0-5
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap
Control: affects 889920 + src:seahorse
Control: affects 889925 + src:seahorse

seahorse fails to cross build from source, because it use the build
architecture pkg-config (via AC_PATH_PROG rather than AC_PATH_TOOL) and
thus fails to find relevant libraries. The attached patch fixes that.

Then it fails due to the general valac mess reported in #889920 and
#889925. Please just fix the pkg-config stuff here and close this bug.

Helmut
Index: seahorse-3.20.0/configure.ac
===
--- seahorse-3.20.0.orig/configure.ac
+++ seahorse-3.20.0/configure.ac
@@ -30,7 +30,7 @@
 AM_PROG_CC_C_O
 AC_PROG_INTLTOOL([0.35.0])
 AC_PROG_RANLIB
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+PKG_PROG_PKG_CONFIG
 
 GETTEXT_PACKAGE=seahorse
 AC_SUBST(GETTEXT_PACKAGE)

Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

[Peter Green]

Not a surprise as long as some dependencies are built against libmpfr4.

It looks like all dependencies are now rebuilt against libmpfr6 but sagemath is 
still failing.

https://buildd.debian.org/status/fetch.php?pkg=sagemath&arch=amd64&ver=8.1-2%2Bb2&stamp=1517950645&raw=0

Bug#889974: Sylpheed: adjust dependency

[Hideki Yamane]

Package: sylpheed
Severity: minor

Hi,

 In debian/control,

> Recommends: sylpheed-i18n, xfonts-100dpi | xfonts-75dpi |
>  xfonts-100dpi-transcoded | xfonts-75dpi-transcoded, aspell-en |
>  aspell-dictionary, ca-certificates

 Well, why sylpheed package recommends xfonts-* packages?
 Most of users use it under modern X with TrueType fonts, I guess.
 Can we remove or demote it?

> Suggests: jpilot, sylpheed-doc (>= 20020420-3), claws-mail-tools, bogofilter,
>  bsfilter, curl

 We should remove jpilot and put sylfilter | bogofilter | bsfilter to
 Recommends, IMO.


-- 
Regards,

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

Bug#853527: lmms: ftbfs with GCC-7

[Javier Serrano Polo]

El dv 09 de 02 de 2018 a les 17:22 +0300, Dmitry Eremin-Solenikov va
escriure:
> Any progress on uploading
> 1.1.3-8 or packaging 1.1.90?

Pending upload.


smime.p7s
Description: S/MIME cryptographic signature

Bug#876934: openorienteering-mapper FTBFS: test failures

[Sebastiaan Couwenberg]

On Mon, 9 Oct 2017 10:54:14 +0200 Graham Inggs wrote:
> I've just tried sbuild in an amd64 sid schroot and 
> openorienteering-mapper builds fine for me.
> 
> I noticed it also still builds in testing on the reproducible-builds 
> buildds.
> 
> Why don't co-maintainers (uploaders) receive bug by default?  I missed 
> this report.

In preparating of the proj transition openorienteering-mapper (0.7.0-1)
was rebuilt in my cowbuilder chroot where these tests caused FTBFS too.

I'll raise the severity of this issue to serious when the proj
transition starts.

Kind Regards,

Bas

Bug#888073: Multiarch interpreter names for traditional architectures

[Aurelien Jarno]

On 2018-02-09 15:20, Javier Serrano Polo wrote:
> El dv 09 de 02 de 2018 a les 15:02 +0100, Aurelien Jarno va escriure:
> > The notion of "multiarch interpreter" doesn't exist.
> 
> It does exist, but you do not accept it. You are now denying the
> official support that exists in Debian.

I love the way you use "official" here.

> Use /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 as the program
> interpreter and the program will work perfectly in Debian and
> derivatives.

I don't care about compatibility within Debian and derivatives. I care
about the compatibility within the whole GNU/Linux ecosystem.

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

Bug#863863: ITP: gmailieer -- Fast fetch and two-way tag synchronization between notmuch and GMail

[Julian Andres Klode]

Control: tag -1 pending

On Thu, Jun 01, 2017 at 09:13:09AM +0200, Julian Andres Klode wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Julian Andres Klode 
> 
> (gauteh: this is a Debian packaging intent)
> 
> * Package name: gmailieer
>   Version : 0.1+git
>   Upstream Author : Gaute Hope 
> * URL : https://github.com/gauteh/gmailieer
> * License : GPL-3+
>   Programming Lang: Python
>   Description : Fast fetch and two-way tag synchronization between 
> notmuch and GMail
> 
> This program can pull email and labels (and changes to labels) from your 
> GMail account
> and store them locally in a maildir with the labels synchronized with a 
> notmuch database.
> The changes to tags in the notmuch database may be pushed back remotely to 
> your GMail account.
> 
> It will not and can not:
> 
> - Add or delete messages on your remote account
> - Modify messages other than their labels

Uploaded to NEW. Packaging in Salsa. Sorry it took so long :(

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#889106: Multiarch interpreter names for traditional architectures

[Javier Serrano Polo]

El dv 09 de 02 de 2018 a les 16:03 +0100, Aurelien Jarno va escriure:
> I love the way you use "official" here.

Me too. It is precisely your policy not to include any unnecessary file
because "experience shows that users are very imaginative when you
provide a feature". You have taken steps to insure the existence of
multiarch interpreters and they have landed on stable releases.

> I don't care about compatibility within Debian and derivatives.

I do. Strange statement from a Debian developer.

> I care
> about the compatibility within the whole GNU/Linux ecosystem.

I do too. I even care about compatibility with non-Linux systems.

Give a solution like I do instead of complaining about the past.


smime.p7s
Description: S/MIME cryptographic signature

Bug#889975: roffit: debian/rules does not override targets as intended

[Chris Lamb]

Source: roffit
Version: 0.7~20120815+gitbbf62e6-1
Severity: minor
Tags: patch

Hi,

Your debian/rules contains:

  override_dh_auto_config, override_dh_auto_build, override_dh_auto_install:
 # Disable, see debian/install

I believe this should be:

  override_dh_auto_config:
  override_dh_auto_build:
  override_dh_auto_install:
 # Disable, see debian/install

Patch attached, although maybe this shows that you don't need such
overrides anyway given that they don't see to have any effect...?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/rules b/debian/rules
index 7e38255..baaee96 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,8 @@
 #!/usr/bin/make -f
 
-override_dh_auto_config, override_dh_auto_build, override_dh_auto_install:
+override_dh_auto_config:
+override_dh_auto_build:
+override_dh_auto_install:
# Disable, see debian/install
 
 %:

Bug#889977: mdadm: checkarray --all only processes one array if scheduling class not specified

[Tony]

Package: mdadm
Version: 3.4-4+b1
Severity: normal

Dear Maintainer,

If --all given but no scheduling class specified only one array is
checked. This appears to be because at lines 194-200 the variable ionice
is checked. If no class is given then this is blank and the script
exits.

I thing the correction is to change 'break' on line
199 to 'continue'

-- Package-specific info:
--- mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST 
MAILADDR failmessa...@roxburgh.net
ARRAY /dev/md1  metadata=1.0 UUID=a6fcec62:8151c509:d2bd0ab5:6b8e5c15 
name=thistle:1
ARRAY /dev/md3  metadata=1.2 UUID=6ba89e9a:1c2d0b18:aa28937c:8156ea9f 
name=thistle:3
ARRAY /dev/md4  metadata=1.2 UUID=e78fd9e3:0a57ee1e:307d639c:62a428f2 
name=thistle:4

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] 
[raid10] 
md4 : active raid1 sda4[2] sdb4[0]
  198135360 blocks super 1.2 [2/2] [UU]
resync=DELAYED
  bitmap: 0/2 pages [0KB], 65536KB chunk

md1 : active raid1 sda1[2] sdb1[0]
  511936 blocks super 1.0 [2/2] [UU]
  
md3 : active raid1 sda3[2] sdb3[0]
  31440896 blocks super 1.2 [2/2] [UU]
  [==>..]  check = 72.6% (22841984/31440896) finish=0.6min 
speed=206314K/sec
  
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   80  234431064 sda
   81 512000 sda1
   824194304 sda2
   83   31457280 sda3
   84  198266439 sda4
   8   16  234431064 sdb
   8   17 512000 sdb1
   8   184194304 sdb2
   8   19   31457280 sdb3
   8   20  198266439 sdb4
   93   31440896 md3
   91 511936 md1
   94  198135360 md4
 2530   26214400 dm-0
 2531  104857600 dm-1

--- LVM physical volumes:
  PV VG  Fmt  Attr PSize   PFree 
  /dev/md4   VGT lvm2 a--  188.00g 63.00g
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=1725424k,nr_inodes=431356,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=347472k,mode=755)
/dev/md3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9811)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/md1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/mapper/VGT-africa on /vol/africa type ext4 (rw,relatime,data=ordered)
/dev/mapper/VGT-offsite on /vol/offsite type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=347468k,mode=700)

--- initrd.img-4.9.0-5-amd64:
118486 blocks
192ccafcfe38eabf0f5184786764c4a9  ./scripts/local-bottom/mdadm
f3b648ca1c912da30940f0b821b7e9e6  ./scripts/local-block/mdadm
38a0d82d74715c1b647af1279c9e3b38  ./sbin/mdadm
a2bc3505926a2f2a745cc04dd5a2f485  
./lib/modules/4.9.0-5-amd64/kernel/drivers/md/dm-snapshot.ko
ff9457a2db3fe85981243e37438b5b40  
./lib/modules/4.9.0-5-amd64/kernel/drivers/md/md-mod.ko
92a77d664f5b69ee4dab75accedc0ee2  
./lib/

Bug#889978: mdadm: Monthly checkarray not run if machine not running overnight

[Tony]

Package: mdadm
Version: 3.4-4+b1
Severity: normal

Dear Maintainer,

mdadm schedules a run of checkarray once a month using an entry in
/etc/cron.d

However, if the machine is not running at the time this is scheduled it
will not be run, even when the machine is reloaded.

Perhaps this should be moved to /etc/cron.monthly so that anacron can
pick it up.



-- Package-specific info:
--- mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST 
MAILADDR failmessa...@roxburgh.net
ARRAY /dev/md1  metadata=1.0 UUID=a6fcec62:8151c509:d2bd0ab5:6b8e5c15 
name=thistle:1
ARRAY /dev/md3  metadata=1.2 UUID=6ba89e9a:1c2d0b18:aa28937c:8156ea9f 
name=thistle:3
ARRAY /dev/md4  metadata=1.2 UUID=e78fd9e3:0a57ee1e:307d639c:62a428f2 
name=thistle:4

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] 
[raid10] 
md4 : active raid1 sda4[2] sdb4[0]
  198135360 blocks super 1.2 [2/2] [UU]
  bitmap: 0/2 pages [0KB], 65536KB chunk

md1 : active raid1 sda1[2] sdb1[0]
  511936 blocks super 1.0 [2/2] [UU]
  
md3 : active raid1 sda3[2] sdb3[0]
  31440896 blocks super 1.2 [2/2] [UU]
  
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   80  234431064 sda
   81 512000 sda1
   824194304 sda2
   83   31457280 sda3
   84  198266439 sda4
   8   16  234431064 sdb
   8   17 512000 sdb1
   8   184194304 sdb2
   8   19   31457280 sdb3
   8   20  198266439 sdb4
   93   31440896 md3
   91 511936 md1
   94  198135360 md4
 2530   26214400 dm-0
 2531  104857600 dm-1

--- LVM physical volumes:
  PV VG  Fmt  Attr PSize   PFree 
  /dev/md4   VGT lvm2 a--  188.00g 63.00g
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=1725424k,nr_inodes=431356,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=347472k,mode=755)
/dev/md3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9811)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/md1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/mapper/VGT-africa on /vol/africa type ext4 (rw,relatime,data=ordered)
/dev/mapper/VGT-offsite on /vol/offsite type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=347468k,mode=700)

--- initrd.img-4.9.0-5-amd64:
118486 blocks
192ccafcfe38eabf0f5184786764c4a9  ./scripts/local-bottom/mdadm
f3b648ca1c912da30940f0b821b7e9e6  ./scripts/local-block/mdadm
38a0d82d74715c1b647af1279c9e3b38  ./sbin/mdadm
a2bc3505926a2f2a745cc04dd5a2f485  
./lib/modules/4.9.0-5-amd64/kernel/drivers/md/dm-snapshot.ko
ff9457a2db3fe85981243e37438b5b40  
./lib/modules/4.9.0-5-amd64/kernel/drivers/md/md-mod.ko
92a77d664f5b69ee4dab75accedc0ee2  
./lib/modules/4.9.0-5-amd64/kernel/drivers/md/linear.ko
99b3ac6028546e5df37afdcf15cd  
./lib/modules/4.9.0-5-amd64/kern

Bug#889976: ITP: node-package-hash -- hash for an installed npm package

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-package-hash
  Version : 2.0.0
  Upstream Author : Mark Wubben (https://novemberborn.net/)
* URL : https://github.com/novemberborn/package-hash#readme
* License : ISC
  Programming Lang: JavaScript
  Description : hash for an installed npm package

 This module generates a hash for an installed npm package, useful for
salting
 caches.
 .
 AVA for example caches precompiled test files. It generates a salt for its
 cache based on the various packages that are used when compiling the test
 files.
 .
 package-hash can generate an appropriate hash based on the package location
 (on disk) and the package.json file. This hash is salted with a hash
for the
 package-hash itself.
 .
 Node.js is an event-based server-side JavaScript engine.

Dependency of ava test framework.



signature.asc
Description: OpenPGP digital signature

Bug#888880: Hyvää päivää,

[Corporate Lenders]

Hyvää päivää,

     Olen Thomas Walter, joka on rahoitusalan edustaja tunnetusta
lainanantajasta, joka tunnetaan nimellä Corporate Lenders. Onko sinulla
huono luotto tai tarvitset rahaa maksamaan laskuja? korko on 3%.

  Täytä alla oleva lomake, jos olet kiinnostunut lainasta.

  Koko nimi:
  sukupuoli:
  Tarvittava summa:
  Kesto:

  Voit ottaa meihin yhteyttä sähköpostitse: i...@corporatelendersonline.com

  Terveiset,
  Herra Thomas Walter

--
Esta mensagem foi verificada pelo sistema de antivírus e
acredita-se estar livre de perigo.

Bug#859324: glade: eats unrelated key-repeat events

[Sébastien Villemot]

Control: severity -1 important
Control: tags -1 + upstream fixed-upstream patch
Control: fixed -1 3.20.2-1
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=763624

Dear Matthias, dear GNOME Maintainers,

On Sun, 02 Apr 2017 11:07:46 +0200 Matthias Urlichs  wrote:
> Package: glade
> Version: 3.20.0-2
> Severity: normal
> 
> Apparently, when a nontrivial Glade window is in the foreground, somehow
> key repeat events get clobbered.
> 
> $ x … (key repeats normally)
> $ glade FOO.glade
> xx (key repeats irregularly, every couple of seconds)
> < minimize Glade window or switch screens)
>  … (normal again)
> 
> The problem also disappears when Glade is interrupted or when the content
> it shows is empty. Thus this seems to be a problem with at least one of its 
> widgets.

This bug has been fixed upstream, and is no longer present in version
3.20.2 (in unstable). Here is the relevant commit:

 
https://git.gnome.org/browse/glade/commit/?id=ac55fa78566145ac44d48ba88ec1351db5b4a99d

I confirm that this patch, backported on 3.20.0, fixes the issue. I am
going to prepare a stable upload to fix it in stretch.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#889979: Composite extension broken

[Theodore Lytras]

Package: xserver-xephyr
Version: 1:1.19.6-1
Severity: important

I use Xephyr to play Sid Meier's Alpha Centauri (yes, people still play that), 
and this requires disabling its Composite extension (or the game hangs). 
Unfortunately, on my amd64 machine with Xephyr version 1.19.6 this throws an 
error (used to work with version 1.19.5):

$ Xephyr :1 -screen 800x600 -extension Composite

Xephyr: ../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key-
>initialized' failed.
(EE) 
(EE) Backtrace:
(EE) 0: Xephyr (xorg_backtrace+0x4d) [0x5608257337bd]
(EE) 1: Xephyr (0x56082556d000+0x1ca559) [0x560825737559]
(EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0b03af6000+0x12180) 
[0x7f0b03b08180]
(EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x110) [0x7f0b037746a0]
(EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x1c7) [0x7f0b03775cf7]
(EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f0b0374+0x2cfca) 
[0x7f0b0376cfca]
(EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f0b0374+0x2d042) 
[0x7f0b0376d042]
(EE) 7: Xephyr (0x56082556d000+0x3c252) [0x5608255a9252]
(EE) 8: Xephyr (0x56082556d000+0x1c1c1f) [0x56082572ec1f]
(EE) 9: Xephyr (0x56082556d000+0x12c667) [0x560825699667]
(EE) 10: Xephyr (0x56082556d000+0x12bcc5) [0x560825698cc5]
(EE) 11: Xephyr (0x56082556d000+0x12b115) [0x560825698115]
(EE) 12: Xephyr (InitExtensions+0x3d) [0x56082562ce2d]
(EE) 13: Xephyr (0x56082556d000+0x7c93f) [0x5608255e993f]
(EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xea) 
[0x7f0b03760f2a]
(EE) 15: Xephyr (_start+0x2a) [0x5608255a92fa]
(EE) 
(EE) 
Fatal server error:
(EE) Caught signal 6 (Aborted). Server aborting
(EE) 

Withour "-extension Composite" Xephyr starts, but unfortunately I can't play 
the game. Given that this is the only reason I use Xephyr (and I suspect that 
applies to many people as well), I think this bug qualifies as "important"...

Bug#889980: missing python3 autopkg test dependencies

[Matthias Klose]

Package: src:txzmq
Version: 0.7.4-2
Severity: important
Tags: sid buster patch

missing python autopkg test dependencies

patch at
http://launchpadlibrarian.net/356269392/txzmq_0.7.4-2ubuntu1_0.7.4-2ubuntu2.diff.gz

Maybe it's better to write a second test for the Python3 runs.

However, for me at least, the tests fail:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/t/txzmq/20180208_234021_24dbd@/log.gz

autopkgtest [20:53:31]: test unittests: [---
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/autopkgtest.15j71t/autopkgtest_tmp, inifile:
collected 36 items

. .....ss..ss.

= 28 passed, 8 skipped in 9.23 seconds =
= test session starts ==
platform linux -- Python 3.6.4, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/autopkgtest.15j71t/autopkgtest_tmp, inifile:
collected 38 items

. F...FFF.FFF....ss..FEautopkgtest [23:40:11]: ERROR: timed out on
command "su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile
>/dev/null 2>&1 || true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest.15j71t/build.iXO/src"; mkdir -p -m 1777 --
"/tmp/autopkgtest.15j71t/unittests-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest.15j71t/unittests-artifacts"; export
ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest.15j71t/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest.15j71t/autopkgtest_tmp"; export
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=1; unset LANGUAGE LC_CTYPE
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd
"$buildtree"; export 'ADT_TEST_TRIGGERS=txzmq/0.7.4-2ubuntu2'; chmod +x
/tmp/autopkgtest.15j71t/build.iXO/src/debian/tests/unittests; touch
/tmp/autopkgtest.15j71t/unittests-stdout
/tmp/autopkgtest.15j71t/unittests-stderr;
/tmp/autopkgtest.15j71t/build.iXO/src/debian/tests/unittests 2> >(tee -a
/tmp/autopkgtest.15j71t/unittests-stderr >&2) > >(tee -a
/tmp/autopkgtest.15j71t/unittests-stdout);" (kind: test)
autopkgtest [23:40:11]: test unittests: ---]
unittestsFAIL timed out
autopkgtest [23:40:11]: test unittests:  - - - - - - - - - - results - - - - - -
- - - -
autopkgtest [23:40:12]:  summary
unittestsFAIL timed out
Exit request sent.

Bug#882328: [Pkg-gauche-devel] Bug#882328: gauche-c-wrapper FTBFS with glibc 2.25

[Jens Thiele]

another idea would be to allow to skip macros via some keyword :skip-macro
example patch:

--- gauche-c-wrapper-0.6.1/lib/c-wrapper/c-parser.scm   2009-08-08 
16:44:52.0 +0200
+++ gauche-c-wrapper-0.6.1.new/lib/c-wrapper/c-parser.scm   2018-02-09 
16:56:03.390344967 +0100
@@ -1099,7 +1099,7 @@
 ;;:show-define? #f))
 ;;(start-macro-reset!)))
 
-(define (parse-macro include-dirs headers options)
+(define (parse-macro include-dirs headers options skip-macro)
   (unwind-protect
(guard (e (( e)
   (let ((errmsg (make-error-message (condition-ref e 'message
@@ -1115,7 +1115,10 @@
 (raise e
  (call-with-gcc-io include-dirs headers options
(lambda (in out)
- (let ((macro-list (queue->list (macro-queue
+ (let ((macro-list (filter
+   (lambda(m)
+ (not (skip-macro (car m
+   (queue->list (macro-queue)
(for-each (lambda (macro-def)
(display (car macro-def) out)
(newline out))
@@ -1152,11 +1155,11 @@
  (else
   (errorf "~s can't be used for :import argument." import-cond)
 
-(define (c-parse include-dirs headers options import-arg export? sandbox hides)
+(define (c-parse include-dirs headers options import-arg export? sandbox hides 
skip-macro)
   (with-parse-context
(lambda ()
  (parse-source include-dirs headers options)
- (parse-macro include-dirs headers options)
+ (parse-macro include-dirs headers options skip-macro)
 
  (let ((export-syms
 (if import-arg
--- gauche-c-wrapper-0.6.1/lib/c-wrapper.scm2009-08-08 16:44:52.0 
+0200
+++ gauche-c-wrapper-0.6.1.new/lib/c-wrapper.scm2018-02-09 
16:45:26.045654080 +0100
@@ -91,7 +91,8 @@
(module #t)
(export? #f)
(output #f)
-   (hide-symbols '()))
+   (hide-symbols '())
+  (skip-macro (lambda(m) #f)))
 (when (eq? module #t)
   (set! export? #t))
 (parameterize ((sandbox-module (make-sandbox curmod module)))
@@ -117,7 +118,8 @@
(lambda (expr)
  (push! output-list expr))
(sandbox-module))
-   hide-symbols)
+   hide-symbols
+  skip-macro)
   (if output
   (call-with-output-file output
 (lambda (out)
@@ -154,7 +156,8 @@
(module #t)
(export? #f)
(output #f)
-   (hide-symbols '()))
+   (hide-symbols '())
+  (skip-macro (lambda(m) #f)))
 (cond
  ((compiled-lib-exist? compiled-lib)
   `(begin
@@ -171,7 +174,7 @@
  " ")))
 `(begin
(c-ld ,ld-option)
-   (c-include ,headers :option ,cpp-option :import ,import-arg :output 
,output :module ,module :export? ,export? :hide-symbols ,hide-symbols)))
+   (c-include ,headers :option ,cpp-option :import ,import-arg :output 
,output :module ,module :export? ,export? :hide-symbols ,hide-symbols 
:skip-macro ,skip-macro)))
 
 (define-syntax define-enum
   (syntax-rules ()
--- gauche-c-wrapper-0.6.1/testsuite/cwrappertest.scm   2009-08-08 
16:44:51.0 +0200
+++ gauche-c-wrapper-0.6.1.new/testsuite/cwrappertest.scm   2018-02-09 
16:49:49.349893969 +0100
@@ -10,7 +10,7 @@
 (test-module 'c-wrapper)
 
 (c-load-library "./ffitest")
-(c-include "./ffitest.h")
+(c-include "./ffitest.h" :skip-macro (lambda(m) (#/^__glibc_macro_warning/ m)))
 
 (define-syntax test-cfunc
   (syntax-rules ()

Bug#675008: bash: should handle /etc/bashrc.d (or similar) for non-login interactive shell

[Laurent Bigonville]

Hello,

More and more packages are adding files to /etc/profile.d/ but nothing 
is sourcing them by default in debian.


$ apt-file search /etc/profile.d/|wc -l
23

Other distributions (RH-like) are sourcing files put in that directory 
for years now (but not /etc/profile itself)


From /etc/bashrc:

# Only display echos from profile.d scripts if we are no login shell
# and interactive - otherwise just process them to set envvars
for i in /etc/profile.d/*.sh; do
if [ -r "$i" ]; then
if [ "$PS1" ]; then
. "$i"
else
. "$i" >/dev/null
fi
fi
done

Wouldn't it make sense to follow what RH and already some packages in 
the archive are doing and source .sh files from /etc/profile.d/ in 
non-login shell as well?


Kind regards,

Laurent Bigonville

Bug#795593: systemsettings: Also happens with Alt+F1 Activate Application Launcher, but it also implicitly maps the Win key

[Vivia Nikolaidou]

Dear Maintainer,

The initial bug reported should be now fixed:
https://bugs.kde.org/show_bug.cgi?id=347352

My bug is actually a combination of two different issues, both
upstream, and both different from the one initially reported here.

One is this: https://bugs.kde.org/show_bug.cgi?id=346918 which is
still under discussion upstream.

The other is not a bug, just an undocumented feature:
https://forum.kde.org/viewtopic.php?t=137574

Dumping more information in case someone else runs into this bug:

chmod -w ~/.config/kglobalshortcutsrc doesn't work, the file still
manages to get overwritten.

Making a small shell script in .config/autostart-scripts that would
sed away the offending input in ~/.config/kglobalshortcutsrc also
doesn't work, because the substitution apparently happens after the
script is executed.

In any case, this bug can be closed. Maybe a different one can be
opened for the Alt+F1 shortcut.

Best regards,

Vivia Nikolaidou

On 8 February 2018 at 23:55, Vivia Nikolaidou  wrote:
> Package: systemsettings
> Version: 4:5.10.5-2
> Followup-For: Bug #795593
>
> Dear Maintainer,
>
> I have this with the Alt+F1 shortcut to Activate Application Launcher. 
> However, what I actually care about is the Left Win button. For some reason, 
> the Left Win button is also set to Activate Application Launcher even though 
> systemsettings claims it's Alt+F1. I go to systemsettings, set Activate 
> Application Launcher to None, then the Left Win key is also free for me to 
> use as Compose. I have tried setting it to a couple of other values apart 
> from Alt+F1 and they also seem to hijack my Left Win key without asking me.
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.14.0-3-amd64 (SMP w/20 CPU cores)
> Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages systemsettings depends on:
> pn  kio   
> ii  libc6 2.26-6
> pn  libkf5auth5   
> pn  libkf5completion5 
> pn  libkf5configcore5 
> pn  libkf5configgui5  
> pn  libkf5configwidgets5  
> ii  libkf5coreaddons5 5.37.0-3
> pn  libkf5dbusaddons5 
> pn  libkf5i18n5   
> pn  libkf5iconthemes5 
> pn  libkf5itemviews5  
> pn  libkf5kcmutils5   
> pn  libkf5khtml5  
> pn  libkf5kiowidgets5 
> pn  libkf5service-bin 
> pn  libkf5service5
> pn  libkf5widgetsaddons5  
> pn  libkf5windowsystem5   
> pn  libkf5xmlgui5 
> ii  libqt5core5a  5.9.2+dfsg-7
> ii  libqt5dbus5   5.9.2+dfsg-7
> ii  libqt5gui55.9.2+dfsg-7
> ii  libqt5widgets55.9.2+dfsg-7
> ii  libstdc++67.3.0-1
> pn  qml-module-org-kde-kirigami2  
> pn  qml-module-qtquick-controls   
> pn  qml-module-qtquick-layouts
> pn  qml-module-qtquick2   
>
> systemsettings recommends no packages.
>
> systemsettings suggests no packages.
>
> -- no debconf information

Bug#884865: Response?

[Brett Johnson]

Any chance of a response to this request?  If y'all think it's a bad idea,
or don't want to do it, that's OK, I'll go back to the drawing board and
try to figure out some sane way to package/version glslang and spirv-tools
independently (although that's going to be difficult, as they don't have
any kind of internal versioning).  But I'd sure appreciate some kind of
response.  Thanks!

Bug#889982: RFS: python3-metpx-sarracenia [put in ITP] - file transfer thingum.

[Peter Silva]

Package: sponsorhip-requests
Severity: wishlist

I am looking for a sponsor for my package python3-metpx-sarracenia.
It has been in development since 2013, and it is now getting stable
enough that putting it into a stable repository is starting to make sense.
currently alpha, should make it to beta soon.

Package name : python3-metpx-sarracenia
Version : 2.18.01a5 ? or later? maybe pull latest tag from git?
Upstream Author: ssc.hpc-chp@canada.ca,
peter_si...@sourceforge.net  ( Peter Silva is manager of a team at
Canadian government.)
URL: http://metpx.sf.net
License:   GPLv2
Section:python

Sarracenia is used to generate messages (called posts) about files,
which are then published to a rabbitmq AMQP broker.  Subscribers can
then do stuff with them. Usually one downloads them, thus doing a file
transfer.  Once downloaded, the files can also be published to another
broker, daisy chain style. Hence SARRA: Subscribe and Recusively
Re-Advertise.

Can be used to mirror large trees... and by large, I mean 27 million
files in a single tree large... and do so 72 times faster than
rsync... (explanation here:
http://metpx.sourceforge.net/mirroring_use_case.html )  mi

also can be used to download from the Canadian weather service's
public datamart ( http://dd.weather.gc.ca )

The debian building basically works, there is a PPA for it:
https://launchpad.net/metpx-sarracenia

One can obtain the source:

git clone git://git.code.sf.net/p/metpx/sarracenia metpx-sarracenia
cd metpx-sarracenia
git checkout v2.18.01a5
debuild

will build the python3-metpx-sarracenia_2.18.01a5_all.deb
package.

That's clean, and that's enough for now... If you are feeling kind/friendly,
 but there is also some (optional) C stuff in the c/ subdirectory.  if you do:

cd c
debuild

it will build:

libsarra-c_2.18.01a5_amd64.deb  libsarra-c-dev_2.18.01a5_amd64.deb
sarra-c_2.18.01a5_amd64.deb

The C stuff is needed for the large mirroring case, but most use cases
are fine with just the python.  I haven't figured out how to get
launchpad to do these builds automatically, and they require
librabbitmq4-0.8.0 which is too new from ubuntu 16.04, so have not
tried to build there, but current debian stable is OK (also 17.10, and
18.04) The c stuff is linux only (depends on INOTIFY kernel feature.)
likely won't work on alternate kernels.

Bug#857081: linux-image-rt-amd64-unsigned: NOHZ: local_softirq_pending 80

[Fernando Toledo]

On Thu, 29 Jun 2017 19:08:59 +0200 Laurent Bonnaud
 wrote:
> Hi,
> 
> this bug is still there in kernel 4.11.6 :
> 
> $ uname -a
> Linux irancy.iut2.upmf-grenoble.fr 4.11.0-1-rt-amd64 #1 SMP PREEMPT RT Debian 
> 4.11.6-1 (2017-06-19) x86_64 GNU/Linux
> 
> $ dmesg
> [...]
> [690935.587688] NOHZ: local_softirq_pending 80
> 
> When this error occurred the system was accessing a btrfs filesystem on a USB 
> disk.  Might the problem be in btrfs?
> 
> -- 
> Laurent.
> 
> 
i think that is not only for btrfs but general usb usage (in my case
this triggered when bluetooth and nfts usb stick  are detected)


[   24.865569] usb 1-1.1: Product: Bluetooth USB Host Controller
[   24.867168] usb 1-1.1: Manufacturer: Atheros Communications
[   24.868883] usb 1-1.1: SerialNumber: Alaska Day 2006
[   25.676408] NOHZ: local_softirq_pending 80
[   26.539786] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   26.541172] Bluetooth: BNEP filters: protocol multicast
[   26.542276] Bluetooth: BNEP socket layer initialized
[   28.008330] vboxdrv: loading out-of-tree module taints kernel.
[   28.016088] vboxdrv: Found 4 processor cores
[   28.036635] vboxdrv: TSC mode is Invariant, tentative frequency
1795918881 Hz
[   28.036641] vboxdrv: Successfully loaded version 5.2.6 (interface
0x0029)
[   28.369292] VBoxNetFlt: Successfully started.
[   28.558477] VBoxNetAdp: Successfully started.
[   28.678656] VBoxPciLinuxInit
[   28.753930] vboxpci: IOMMU not found (not registered)
[   30.074684] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   30.397299] Ebtables v2.0 registered
[   37.727019] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   37.785572] r8169 :01:00.0: firmware: direct-loading firmware
rtl_nic/rtl8168e-3.fw
[   37.877806] r8169 :01:00.0 eth0: link down
[   37.877939] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   37.910313] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   37.924810] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   38.044857] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   38.794066] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   82.628975] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   83.756930] wlan0: authenticate with 00:1e:58:c4:35:f1
[   83.777654] wlan0: send auth to 00:1e:58:c4:35:f1 (try 1/3)
[   83.779557] wlan0: authenticated
[   83.780797] wlan0: associate with 00:1e:58:c4:35:f1 (try 1/3)
[   83.784090] wlan0: RX AssocResp from 00:1e:58:c4:35:f1 (capab=0x431
status=0 aid=3)
[   83.784244] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   83.784331] wlan0: associated
[   90.498577] Bluetooth: RFCOMM TTY layer initialized
[   90.498594] Bluetooth: RFCOMM socket layer initialized
[   90.498604] Bluetooth: RFCOMM ver 1.11
[  457.091349] NOHZ: local_softirq_pending 80
[  496.428319] NOHZ: local_softirq_pending 80
[  555.387813] NOHZ: local_softirq_pending 80
[ 4372.311469] usb 2-3: new high-speed USB device number 3 using xhci_hcd
[ 4372.456280] usb 2-3: New USB device found, idVendor=0930, idProduct=6545
[ 4372.456288] usb 2-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4372.456290] usb 2-3: Product: DT 101 G2
[ 4372.456293] usb 2-3: Manufacturer: Kingston
[ 4372.456295] usb 2-3: SerialNumber: 0018F3A9A358EBB1C438082B
[ 4372.997748] usb-storage 2-3:1.0: USB Mass Storage device detected
[ 4372.997927] scsi host6: usb-storage 2-3:1.0
[ 4372.998073] usbcore: registered new interface driver usb-storage
[ 4373.021408] usbcore: registered new interface driver uas
[ 4374.088469] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2
PMAP PQ: 0 ANSI: 0 CCS
[ 4374.103872] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 4375.434426] sd 6:0:0:0: [sdc] 30481152 512-byte logical blocks: (15.6
GB/14.5 GiB)
[ 4375.434627] sd 6:0:0:0: [sdc] Write Protect is off
[ 4375.434630] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
[ 4375.434791] sd 6:0:0:0: [sdc] No Caching mode page found
[ 4375.434792] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 4375.457479]  sdc: sdc1
[ 4375.459023] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[ 4376.449338] fuse init (API version 7.26)
[ 4787.394613] NOHZ: local_softirq_pending 80
[ 5202.614069] perf: interrupt took too long (2512 > 2500), lowering
kernel.perf_event_max_sample_rate to 79500

-- 
Fernando Toledo
Dock Sud BBS
http://bbs.docksud.com.ar
telnet://bbs.docksud.com.ar

Bug#889983: stretch-pu: package glade/3.20.0-2+deb9u1

[Sébastien Villemot]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear Release Team,

I prepared a p-u for glade, fixing #859324 (basically glade eats a lot of CPU
as soon as a non-trivial UI is created).

The debdiff is attached. It also includes Vcs changes related to the
salsa move.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org
diff -Nru glade-3.20.0/debian/changelog glade-3.20.0/debian/changelog
--- glade-3.20.0/debian/changelog	2016-10-21 00:51:16.0 +0200
+++ glade-3.20.0/debian/changelog	2018-02-09 18:02:27.0 +0100
@@ -1,3 +1,16 @@
+glade (3.20.0-2+deb9u1) stretch; urgency=medium
+
+  * Team upload.
+
+  [ Sébastien Villemot ]
+  * fix-use-of-gtk-style-context-in-GladeDesignLayout.patch: new patch.
+Fixes high CPU usage. (Closes: #859324)
+
+  [ Jeremy Bicha ]
+  * Update Vcs fields and add debian/gbp.conf
+
+ -- Sébastien Villemot   Fri, 09 Feb 2018 18:02:27 +0100
+
 glade (3.20.0-2) unstable; urgency=medium
 
   [ Jeremy Bicha ]
diff -Nru glade-3.20.0/debian/control glade-3.20.0/debian/control
--- glade-3.20.0/debian/control	2016-10-21 00:51:16.0 +0200
+++ glade-3.20.0/debian/control	2018-02-09 18:02:27.0 +0100
@@ -7,8 +7,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 
 Uploaders: Andreas Henriksson , Emilio Pozuelo Monfort , Michael Biebl 
-Vcs-Browser: https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/glade
-Vcs-Svn: svn://anonscm.debian.org/pkg-gnome/desktop/unstable/glade
+Vcs-Git: https://salsa.debian.org/gnome-team/glade.git -B debian/stretch
+Vcs-Browser: https://salsa.debian.org/gnome-team/glade/tree/debian/stretch
 Build-Depends: debhelper (>= 10),
gnome-pkg-tools (>= 0.10),
gnome-common,
diff -Nru glade-3.20.0/debian/control.in glade-3.20.0/debian/control.in
--- glade-3.20.0/debian/control.in	2016-10-21 00:44:23.0 +0200
+++ glade-3.20.0/debian/control.in	2018-02-09 17:51:16.0 +0100
@@ -3,8 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 
 Uploaders: @GNOME_TEAM@
-Vcs-Browser: https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/glade
-Vcs-Svn: svn://anonscm.debian.org/pkg-gnome/desktop/unstable/glade
+Vcs-Git: https://salsa.debian.org/gnome-team/glade.git -B debian/stretch
+Vcs-Browser: https://salsa.debian.org/gnome-team/glade/tree/debian/stretch
 Build-Depends: debhelper (>= 10),
gnome-pkg-tools (>= 0.10),
gnome-common,
diff -Nru glade-3.20.0/debian/gbp.conf glade-3.20.0/debian/gbp.conf
--- glade-3.20.0/debian/gbp.conf	1970-01-01 01:00:00.0 +0100
+++ glade-3.20.0/debian/gbp.conf	2018-02-09 18:00:38.0 +0100
@@ -0,0 +1,4 @@
+[DEFAULT]
+pristine-tar = True
+debian-branch = debian/stretch
+upstream-branch = upstream/3.20.x
diff -Nru glade-3.20.0/debian/patches/fix-use-of-gtk-style-context-in-GladeDesignLayout.patch glade-3.20.0/debian/patches/fix-use-of-gtk-style-context-in-GladeDesignLayout.patch
--- glade-3.20.0/debian/patches/fix-use-of-gtk-style-context-in-GladeDesignLayout.patch	1970-01-01 01:00:00.0 +0100
+++ glade-3.20.0/debian/patches/fix-use-of-gtk-style-context-in-GladeDesignLayout.patch	2018-02-09 17:44:05.0 +0100
@@ -0,0 +1,52 @@
+Description: Fix use of GTK+ style context in GladeDesignLayout.
+ It seems like modifying the style context in the 'draw' handler is not
+ recommended, and we need to save/restore the context.
+ .
+ Otherwise, for some widgets (GtkButton, GtkComboBox), the
+ GladeDesignLayout gets trapped in draw-damage loop.
+ .
+ See 0c076cc8828cd80f1f156a08569199675bf35165 for reference.
+Author: Arnaud Rebillout 
+Origin: https://git.gnome.org/browse/glade/commit/?id=ac55fa78566145ac44d48ba88ec1351db5b4a99d
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=763624
+Bug-Debian: https://bugs.debian.org/859324
+Reviewed-By: Sébastien Villemot 
+Last-Updated: 2018-02-09
+--- a/gladeui/glade-design-layout.c
 b/gladeui/glade-design-layout.c
+@@ -1033,13 +1033,13 @@ draw_frame (GtkWidget *widget, cairo_t *cr, gboolean selected,
+   if (priv->widget_name)
+ {
+   GdkRectangle *rect = &priv->south_east;
+-
++  gtk_style_context_save (context);
+   gtk_style_context_add_class (context, "handle");
+   gtk_render_background (context, cr, rect->x, rect->y, rect->width, rect->height);
+   gtk_render_frame (context, cr, rect->x, rect->y, rect->width, rect->height);
+   gtk_render_layout (context, cr, rect->x + OUTLINE_WIDTH, rect->y + OUTLINE_WIDTH,
+  priv->widget_name);
+-  gtk_style_context_remove_class (context, "handle");
++  gtk_style_context_restore (context);
+ }
+ }
+ 
+@@ -1084,6 +1084,7 @@ draw_selection (cairo_t *cr,
+   if (alloc.x < 0 || alloc.y < 0) return;
+ 
+   context = gtk_widget_get_style_context (parent);
++  gtk_style_context_save (context);
+   gtk_styl