Bug#853034: patches Re: unar: Fuzzer-generated crashing testcases for a dozen identified file formats

[YOSHINO Yoshihito]

Package: unar
Followup-For: Bug #853034
Control: tags -1 + patch

Dear Maintainer,

I have refreshed the package repo's fix-crashes.patch to fully
include an upstream commit 59f5a49.

Then I have created two patches on top of those upstream fixes.
Now the uploaded files on the upstream issue page seems to work well.

BTW debian/rules calls some test programs with no arguments,
which actually do nothing.
Are you planning to include test archive files in the source package?

Regards,
-- 
YOSHINO Yoshihito 
Description: Import upstream's commits to fix crashes.
Forwarded: https://bitbucket.org/WAHa_06x36/theunarchiver/issues/933
Origin: upstream,
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/59f5a493ecfde7a74ab5cabce26e4ff6403eedc3
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/0dd444080021fc1e0d1af535a877298071bd8e97
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/c2df329bab6e9c8cffcefd19bad809c2b957d3fd
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/01766d7c47f38e9ef0af18d12fdd16ab1a051ced
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/411668fd77ee7b66bbdf33d84978c18ff550a9a9
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/b63593e649bd0d39d084890cbc9259be7e60f017
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/93d9c87ef611c4f466003b72fa55d9d9e449867d
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/80b6388262fa3d384b3754b1ff8ede142edff5eb
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/f022d13ea2a8ee23ccd6a35eb87be2346da3a9dc
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/a434c35e79717527ecaa9e1fec5d70dff1eb4fa7
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/9acc5e4d54c37cea95db65e3de70077535735d92
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/e6551148652ad44dfe0837bac29f6aa6caa78c60
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/424343b088321c23004b6bd13583736c5464b2c3
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/2dfc5d31f51b24237bedb8b4189d7aae5f730a4e
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/648b1b192113c98dbf191475c0ab5b6aed7bd119
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/cc0a3fde4f4f065e475fb0bab4c1ab64fa2f5ccd
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/dc791d9d4cb02b557885af8d13ec0522dc5274ae
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/a77f14b715c014a15ee6d4a6d42546d8d033eabd
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/f1a42c132896d9ce6d20a23b0939e4812ca09db3
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/893ff8545db7288523457d1d37aedd2c127c9e88
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/9e39d2c1e7dbe4a1e994bb3983660ead375077b4
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/a88d8d1f045ec895a083d98702f93242a45de210
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/cbd4c03ed01b942925fa051a325ee69b0e4811be
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/2529baec38b5621654abde299d19a34c50de26ea
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/c1c49487cb5ed571fa4ed834188538b0121f4a8f
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/a393f6d75b899a1fb3a220d9b002de3ce313763d
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/b42e91a8226986b1dc5f8f334a161b9d02f57c91
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/7eb8da6f1b2d68c483f2f123102cc3b3fcf1612e
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/8b5b9b93d1d2767c0444cb92e90477b921592b00
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/929cbd9124b70b7c5d4ad8c98085f9bd24823976
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/ebb43bc5ec0e31daee223dd729bbd5b1c69cf16d
 https://bitbucket.org/WAHa_06x36/theunarchiver/commits/da4adab4b9cf62b1766f3a72dd3f00a5a74d7701
Last-Update: 2017-03-23
Index: unar-1.10.1/UniversalDetector/universalchardet/Big5Freq.tab
===
--- unar-1.10.1.orig/UniversalDetector/universalchardet/Big5Freq.tab
+++ unar-1.10.1/UniversalDetector/universalchardet/Big5Freq.tab
@@ -55,9 +55,6 @@
 #define BIG5_TYPICAL_DISTRIBUTION_RATIO (float)0.75
 
 
-//Char to FreqOrder table , 
-#define BIG5_TABLE_SIZE  5376
-
 static const PRInt16 Big5CharToFreqOrder[] =
 {
1,1801,1506, 255,1431, 198,   9,  82,   6,5008, 177, 202,3681,1256,2821, 110, //   16
Index: unar-1.10.1/UniversalDetector/universalchardet/CharDistribution.cpp
===
--- unar-1.10.1.orig/UniversalDetector/universalchardet/CharDistribution.cpp
+++ unar-1.10.1/UniversalDetector/universalchardet/CharDistribution.cpp
@@ -70,42 +70,42 @@ float CharDistributionAnalysis::GetConfi
 EUCTWDistributionAnalysis::EUCTWDistributionAnalysis()
 {
   mCharToFreqOrder = EUCTWCharToFreqOrder;
-  mTableSize = EUCTW_TABLE_SIZE;
+  mTableSize = sizeof(EUCTWCharToFreqOrder)/sizeof(EUCTWCharToFreqOrder[0]);
   mTypicalDistributionRatio = EUCTW_TYPICAL_DISTRIBUTION_RATIO;
 }
 
 

Bug#863890: dblatex: postrm fails on jessie to stretch upgrade

[Andreas Hoenen]

Norbert Preining  wrote:

Hi Norbert,

thanks for your feedback.

> > > # A call to 'mktexlsr' is needed to register the dblatex TeX files
> > > # in the TeX database '/var/lib/texmf/ls-R-TEXMFMAIN'.
>
> There is a simple bug here:
> * no dependency on texlive-binaries, which provides mktexlsr

dblatex depends on texlive, which depends on texlive-latex-base, which
depends on texlive-binaries.  Is this indirect dependency too weak?
Would an explicit, direct dependency on texlive-binaries have led to
another apt order in the dist-upgrade?

> Furthermore, it would be much simpler to *NOT* do anything as mktexlsr
> is called automatically (trigger on /usr/share/texmf).

Sorry, didn't know this.

> Since the postinst script does nothing else TeX related, it would be
> the simplest solution to completly drop the code about mktexlsr.

This suggestion renders the discussion above about a direct dependency
on texlive-binaries obsolete.  I would be happy to drop the mktexlsr
calls in postrm/postinst.  In this case the postrm call failed, thus the
fix needs to be applied to *jessie* dblatex, doesn't it?

Regards, Andreas
-- 
Andreas Hoenen 
GPG: 1024D/B888D2CE
 A4A6 E8B5 593A E89B 496B
 82F0 728D 8B7E B888 D2CE


signature.asc
Description: PGP signature

Bug#862698: ITP: minecraft -- blocks to build anything you can imagine

[Nicholas D Steeves]

I merged the bugs so both ITPs are closed when the package on mentors
is uploaded.

Hi Carlos,

Sorry for the delay, I've been busy.

On Wed, May 17, 2017 at 04:36:51PM -0300, Carlos Donizete Froes wrote:
> Hi guys,
> 
> I struggled to fix this project, where I changed the name to
> "minecraft-installer".
> 
> https://github.com/coringao/minecraft-installer
> 
> About icon was mounted in inkscape by me.

Awesome! :-)

> I made it clear that this installer will download files from the official
> Mojang server and will not be for redistributing, respecting the copyright
> and wishes of the Minecraft authors.
> 
> This package does not contain the game itself that would breach copyright,
> laws and the wishes of authors of Minecraft/Mojang or Microsoft.
> 
> The package is on "mentors.debian.net" to rate.
> 
> https://mentors.debian.net/package/minecraft-installer

I gave it a quick look at to my eyes it looks good.  Unfortunately I'm
not yet able to sponsor uploads.  Would you please go to the mentors
page for this package, generate a template, and file an RFS bug if
you're ready for it to be uploaded?  After that, your sponsor might
ask you to change some things to make the package meet his or her
standards/preferences.

> About other projects mentioned here, I do not know, because I have not found
> any of them in Debian.
> 
> The reason that made me interested in the project, is because of my younger
> son asked to install the game this past weekend. :)

The best of reasons :-)

Sincerely,
Nicholas

Bug#863473: unblock: openssl1.0/1.0.2l-1

[Cyril Brulebois]

Niels Thykier  (2017-06-03):
> Kurt Roeckx:
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > Severity: normal
> > 
> > Hi,
> > 
> > I've uploaded a new upstream version of openssl1.0 that contains bug
> > fixes. The Debian changelog says:
> >* New upstream release
> >  - Properly detect features on the AMD Ryzen processor
> >(Closes: #861145)
> >* Refresh valgrind.patch
> > 
> > 
> > Kurt
> > 
> 
> Hi,
> 
> Fine by me.  CC'ing KiBi for a d-i ack assuming he is ok with this last
> minute change.

No symbols change here but see my reply to the openssl unblock
request.

FWIW, reverse dependencies for libcrypto1.0.2-udeb are:
  libdns-export162-udeb
  libirs-export141-udeb
  libssl1.0.2-udeb
  openssh-client-udeb
  openssh-server-udeb
  wpasupplicant-udeb

while libssl1.0.2-udeb seems to have no rev-deps.

The first two are bind udebs mainly used for non-Linux ports,
openssh-* are less in the middle of the way for a casual installation
than wget would be, but wpasupplicant-udeb is rather important to keep
functional. Therefore I'd suggest fixing the issue in src:openssl1.0
as well as in src:openssl, so that further updates of openssl1.0 seem
less risky…



For completeness, the 1.1 situation has fewer ramifications:

Rev-deps for libcrypto1.1-udeb:
  libssl1.1-udeb
  wget-udeb

Rev-deps for wget-udeb:
  libssl1.1-udeb



As for the d-i ACK for this package, I'd prefer waiting a bit until
I've made sure wpasupplicant-udeb still works fine with an updated
libcrypto1.0.2-udeb, with a few bare metal tests.


KiBi.


signature.asc
Description: Digital signature

Bug#863472: unblock: openssl/1.1.0f-1

[Cyril Brulebois]

Niels Thykier  (2017-06-03):
> Kurt Roeckx:
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > Severity: normal
> > 
> > Hi,
> > 
> > I've uploaded a new upstream version of openssl that contains bug
> > fixes. The Debian changelog says:
> >* New upstream version
> >  - Fix regression in req -x509 (Closes: #839575)
> >  - Properly detect features on the AMD Ryzen processor
> >(Closes: #861145)
> >  - Don't mention -tls1_3 in the manpage (Closes: #859191)
> >* Update libssl1.1.symbols for new symbols
> >* Update man-section.patch
> > 
> > 
> > Kurt
> > 
> 
> Hi,
> 
> Fine by me.  CC'ing KiBi for a d-i ack assuming he is ok with this
> last minute change.

Erm.

The libssl1.1-udeb package is broken, as it fails to depend on an
appropriate version of libcrypto1.1-udeb, which means I've just
successfully built a debian-installer against testing with this
addition: build/localudebs/libssl1.1-udeb_1.1.0f-1_amd64.udeb
and gotten a broken wget:
| wget: /usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_0f' not found (required 
by /usr/lib/libssl.so.1.1)

See the missing version here:
| $ dpkg --info build/localudebs/libssl1.1-udeb_1.1.0f-1_amd64.udeb|grep 
Depends:
|  Depends: libc6-udeb (>= 2.24), libcrypto1.1-udeb

One could argue they're from the same source and that this isn't a
practical problem since they're going to migrate at the same time and be
used together in debian-installer, but further fun could come up when
other packages start depending on particular symbols (hello wget), so I
think I'd be nice to have this fixed.

Maybe file this as an RC bug against openssl so that it isn't forgotten
about, but ignore it for r0?


That being said, an installer built against both updated udebs seem to
work fine with regular http and https test cases, which is better news.

Awaiting RT comments before d-i ACK'ing this update.


KiBi.


signature.asc
Description: Digital signature

Bug#864074: vim: 'set mouse=' in /etc/vim/vimrc.local is ignored unless ~/.vimrc exists

[James McCoy]

On Sun, Jun 04, 2017 at 02:10:08AM +0200, Andreas Beckmann wrote:
> for me the default of 'set mouse=a' is a misfeature, so I want to
> disable it globally (my mouse usage ends after marking +
> middle-click pasting of text in the terminal, that works fine
> without pressing shift).
> 
> Unfortunately 'set mouse=' does not work in /etc/vim/vimrc.local, it is
> just ignored. Other options work there.
> But it works if (even an empty) ~/.vimrc does exist.

Please see NEWS.Debian.gz and /etc/vim/vimrc which have similarly worded
descriptions of this:

  " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc.
  " This happens after /etc/vim/vimrc(.local) are loaded, so it will override
  " any settings in these files.
  " If you don't want that to happen, uncomment the below line to prevent
  " defaults.vim from being loaded.
  " let g:skip_defaults_vim = 1

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

Bug#863890: dblatex: postrm fails on jessie to stretch upgrade

[Norbert Preining]

Hi all,

> If I read the upgrade log correct, dblatex got first deconfigured and
> later *removed* during the distupgrade. Actually most of the texlive
> stack seems to get removed (including texlive-binaries, which ships
> mktexlsr). Why did this happen? What was the actual command you used to

That is normal. texlive-base breaks against all old packages to make
sure there is no mixture of 2014 and 2016 packages. This has been used
since about 2005(?)

> > # A call to 'mktexlsr' is needed to register the dblatex TeX files
> > # in the TeX database '/var/lib/texmf/ls-R-TEXMFMAIN'.

There is a simple bug here:
* no dependency on texlive-binaries, which provides mktexlsr

Furthermore, it would be much simpler to *NOT* do anything as mktexlsr
is called automatically (trigger on /usr/share/texmf).

Since the postinst script does nothing else TeX related, it would be
the simplest solution to completly drop the code about mktexlsr.

All the best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#863118: devscripts needs proper configuration file parsing

[James McCoy]

On Sun, Jun 04, 2017 at 10:21:39AM +0900, Osamu Aoki wrote:
> Hi,
> 
> On Sat, Jun 03, 2017 at 01:45:36PM -0400, James McCoy wrote:
> > On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote:
> > > OK, here is my try to do the following.  Ugly, yes.  But it seems to
> > > catch most errors in friendly way.
> > > 
> > >  * "egrep" test to catch space after "="
> > >  * "set -e" to detect command not found; 
> > >* space before "="
> > >* "false" in line
> > >  * "bash -n" test
> > >  * Report the file name if a bug is found as much.
> > > 
> > > If no objection, I will apply this patch to git.  
> > 
> > The concept looks like a step in the right direction.  However, uscan.pl
> > isn't the only script that does this type of config parsing.
> > 
> > Also, I would wait until after Stretch is released.
> 
> Certainly.
> 
> To be honest, I am not a fun of sourcing config file as BASH script.

Neither am I, but it's been that way for ~15 years now...  I'd also
prefer not to have /etc/devscripts manipulated in postinst to add new
config variables and for it to be a conffile (or not exist at all by
default).

> * Should we allow such bash config?

I think it's a bit too late to change that, unfortunately.

> * Should we consolidate and factorize such scripts to be shared among
>   all scripts to reduce maintenance burden?

Yes.  That's been something which has been discussed many times over the
years, but no one has done it.

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

Bug#864076: unblock: distro-info-data/0.36

[Stefano Rivera]

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

Please unblock package distro-info-data

This is a pre-upload unblock request for distro-info-data, now that the
Jessie release date has been announced.

While I was here, I realised that we didn't have EOL dates for Jessie or
Wheezy yet :( We have a long-standing bug of not including LTS dates
(#782685) so I've maintained the status-quo and did that for these two
as well. Alternatively, I could just extend the support dates out to
include LTS, but that seems like another bad idea :/

So, are you OK with this patch-set, and would you consider allowing it
in, for Stretch?

unblock distro-info-data/0.36

Thanks,

SR

diff --git a/debian.csv b/debian.csv
index c1f0962..b476031 100644
--- a/debian.csv
+++ b/debian.csv
@@ -10,10 +10,10 @@ version,codename,series,created,release,eol
 4.0,Etch,etch,2005-06-06,2007-04-08,2010-02-15
 5.0,Lenny,lenny,2007-04-08,2009-02-14,2012-02-06
 6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-31
-7,Wheezy,wheezy,2011-02-06,2013-05-04
-8,Jessie,jessie,2013-05-04,2015-04-25
-9,Stretch,stretch,2015-04-25
-10,Buster,buster,2018-07-01
+7,Wheezy,wheezy,2011-02-06,2013-05-04,2016-04-26
+8,Jessie,jessie,2013-05-04,2015-04-25,2018-06-06
+9,Stretch,stretch,2015-04-25,2017-06-17
+10,Buster,buster,2017-06-17
 11,Bullseye,bullseye,2020-11-05
 ,Sid,sid,1993-08-16
 ,Experimental,experimental,1993-08-16
diff --git a/debian/changelog b/debian/changelog
index cec721c..130df23 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+distro-info-data (0.36) UNRELEASED; urgency=medium
+
+  * Set EOL date for Debian Wheezy. This excludes LTS, which we haven't
+supported in distro-info yet, for Debian, but matches what we did for
+Squeeze.
+  * Set (provisional) EOL date for Debian Jessie.
+  * Set release date for Stretch (and matching creation date for Buster). It
+has been announced.
+
+ -- Stefano Rivera   Sat, 03 Jun 2017 18:07:40 -0700
+
 distro-info-data (0.35) unstable; urgency=medium
 
   * Correct Ubuntu Zesty release date.

Bug#863118: devscripts needs proper configuration file parsing

[Osamu Aoki]

Hi,

On Sat, Jun 03, 2017 at 01:45:36PM -0400, James McCoy wrote:
> On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote:
> > OK, here is my try to do the following.  Ugly, yes.  But it seems to
> > catch most errors in friendly way.
> > 
> >  * "egrep" test to catch space after "="
> >  * "set -e" to detect command not found; 
> >* space before "="
> >* "false" in line
> >  * "bash -n" test
> >  * Report the file name if a bug is found as much.
> > 
> > If no objection, I will apply this patch to git.  
> 
> The concept looks like a step in the right direction.  However, uscan.pl
> isn't the only script that does this type of config parsing.
> 
> Also, I would wait until after Stretch is released.

Certainly.

To be honest, I am not a fun of sourcing config file as BASH script.

Anyway here is a list of packages which needs attention:
$ fgrep ".devscripts'" *.pl
bts.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
dcontrol.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debchange.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debcheckout.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debcommit.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debc.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debdiff.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debi.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debsnap.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
debuild.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
dget.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
dpkg-depcheck.pl:my @config_files = ('/etc/devscripts.conf', 
'~/.devscripts');
dscverify.pl:   my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
grep-excuses.pl:my @config_files = ('/etc/devscripts.conf', 
'~/.devscripts');
mass-bug.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
mk-build-deps.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
plotchangelog.pl:my @config_files = ('/etc/devscripts.conf', 
'~/.devscripts');
rmadison.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');
uscan.pl:my @config_files = ('/etc/devscripts.conf', '~/.devscripts');

$ fgrep .devscripts *.sh
debclean.sh:for file in /etc/devscripts.conf ~/.devscripts
debrelease.sh:  for file in /etc/devscripts.conf ~/.devscripts
debrsign.sh:for file in /etc/devscripts.conf ~/.devscripts; do
debsign.sh: for file in /etc/devscripts.conf ~/.devscripts
nmudiff.sh: for file in /etc/devscripts.conf ~/.devscripts
pts-subscribe.sh:   for file in /etc/devscripts.conf ~/.devscripts
uupdate.sh: for file in /etc/devscripts.conf ~/.devscripts
who-uploads.sh: for file in /etc/devscripts.conf ~/.devscripts
wnpp-alert.sh:OLDCACHEDIR=~/.devscripts_cache

28 scripts.

Questions are:

* Should we allow such bash config?
* Should we consolidate and factorize such scripts to be shared among
  all scripts to reduce maintenance burden?

Osamu

Bug#844201:

[Patrick Griego]

Bug#862855: closed by Mike Gabriel <mike.gabr...@das-netzwerkteam.de> (Bug#862855: fixed in e2guardian 3.4.0.3-2)

[Jose Torres]

1. When do you expect to be available in the Debian FTP?
2. Is the Debian FTP the repository for the upgrades?
3. Will you provide a procedure to do the upgrade?


On Sat, Jun 3, 2017 at 5:21 PM, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the e2guardian package:
>
> #862855: e2guardian: Google Chrome changed certificate requirements making 
> mitm unusable
>
> It has been closed by Mike Gabriel .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Mike Gabriel 
>  by
> replying to this email.
>
>
> --
> 862855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862855
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Mike Gabriel 
> To: 862855-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 03 Jun 2017 21:19:36 +
> Subject: Bug#862855: fixed in e2guardian 3.4.0.3-2
> Source: e2guardian
> Source-Version: 3.4.0.3-2
>
> We believe that the bug you reported is fixed in the latest version of
> e2guardian, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 862...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Mike Gabriel  (supplier of updated 
> e2guardian package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>


https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=icon;
target="_blank">https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif;
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/>
Virus-free. https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=link;
target="_blank" style="color: #4453ea;">www.avast.com

Bug#863112: linux-image-4.9.0-3-686: controller of Video Games not Work fine,move the ANALOGICS move 2 AXIS same time instead 1 AXIS

[Ben Hutchings]

Control: tag -1 upstream

This sounds like the bug described and fixed in:
https://git.kernel.org/linus/18339f59c3a6698ee17d32970c9e1e450b16e7c3
(that was in Linux 4.4).

You have one of the affected devices:

> ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad

Unfortunately, it seems that this fix caused a regression for other
DragonRise controllers that use the same ID.  So that fix was reverted:
https://git.kernel.org/linus/1bcaa05ebee115213e34f1806cc6a4f7a6175a88
(that was in Linux 4.9).

Hopefully this will at some point be resolved with a better fix.

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.


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

Bug#864072: D-I: installer hangs on re-formatting ext3 partition (having grub in the partition boot record).

[Cyril Brulebois]

Hi,

Barry S. Newberger  (2017-06-03):
> Package: debian-installer
> Version: 8.8
> Severity: important
> Tags: d-i
> 
> It looks like the partman bug (#767682) is back in debian-8.8.0-amd64.
> The installer hangs when installing from debian-8.8.0-amd64-DVD-1.iso.
> 
> Using graphical expert install. Reformatting the boot partition on
> sda2 with ext3 filesystem.
> 
> Barry Newberger

According to the bug graph, it was fixed in version 86, while stable
only has 84. Should probably get an upload to p-u…

Can you please double check the output of the ps command, looking for
parameters to the mkfs command?


KiBi.


signature.asc
Description: Digital signature

Bug#800824:

[Chloe Allen]

Bug#863257: gdm3: stretch - login box displayed off-screen

[Ben Hutchings]

On Sat, 2017-05-27 at 21:19 +0200, Michael Biebl wrote:
> Control: reassign -1 linux-image-4.9.0-3-amd64
> Control: severity -1 important
> Control: retitle -1 internal display not turned off despite lid closed and 
> docked
> Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=195455
> 
> Am 27.05.2017 um 20:09 schrieb Michael Biebl:
> > I've narrowed this down. It seems to be a regression introduced by
> > 4.9.25-1, 4.9.18-1 still works fine for me.
> > 
> > Ben, were there any DRM related changes in 4.9.25 which seem like they
> > could be relevant?
> 
> I've found this
> https://bugzilla.redhat.com/show_bug.cgi?id=1430259
> 
> 
> I'm going to reassign this to the kernel for now, as it's not a gdm issue.
> 
> Ben, should we revert this commit for now?
[...]

That will leave other systems broken in different ways.  It's not clear
to me that we should override the upstream change here.  And there is a
workaround available (button.lid_init_state module=method).

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.



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

Bug#862218: mumble: spams console with "warning: Unknown speex_preprocess_ctl request: 26" (and 35)

[Chris Knadle]

Hello, Sascha.

Sorry for the delay in reponse, I wanted to look into the bug and find
some useful info before replying.

Sascha Silbe:
> Package: mumble
> Version: 1.2.8-2
> Severity: normal
> 
> Dear Maintainer,
> 
> on all the ARM based systems that I've tried (OLPC XO-1.75 (*), Wandboard
> Quad, OpenRD Base) mumble spams stdout or stderr with these lines:
> 
> === Begin ===
> warning: Unknown speex_preprocess_ctl request:  26
> warning: Unknown speex_preprocess_ctl request:  35
> === End ===

There's another report of this (#1834) which again was on an ARM:
https://github.com/mumble-voip/mumble/issues/1834

The fix in that case was to rebuild mumble with CONFIG+="bundled-speex".
(That would go into the "rules" file for the Debian source package.)

Let me know if you occasionally rebuild Debian packages for ARM; if not
then I can build a Mumble package for ARM on an amd64 system via qemu
for you with this fix.

> It's producing them at such a high rate that sshd consumes considerable
> CPU time when I run mumble over SSH.

If I understand correctly, this would involve using 'ssh -X' to do X
forwarding over ssh to be able to see the GUI, and presumably rerouting
the audio with something similar? (Or using something like x2go, which
is possible to do on ARM but a bit more difficult.)

Running the mumble client GUI over ssh is a bit unusual, I haven't heard
of that before... I'm a bit curious as to hear how well that works and
what situation that would be fitting for.

> At least on the Wandboard Quad it happens both with on-board audio and
> with a USB headset (Microsoft LifeChat LX-6000); OpenRD Base doesn't
> have on-board audio so I only tried the USB headset.

Yeah that's not surprising; this seems speex library related, which
would be independent of the audio device.

> On XO-1.75 it
> crashes before it can output more than a few of these lines; see my
> other bug report (which apparently ended up on
> debian-backpo...@lists.debian.org because I had the backports version
> installed when I reported the bug).

Yes and that's correct -- for backports bugs are supposed to be reported
to the backports mailing list (that's the policy for backports, listed
in the FAQ: : https://backports.debian.org/FAQ/ ) and there's a somewhat
obscure option that can be found in the manpages for deb-control(5),
deb-src-control(5), and deb-origin(5):

   Bugs: url
 The url of the bug tracking system for this package. The current
 used format is bts-type://bts-address, like
 debbugs://bugs.debian.org.

and the maintainer for the mumble backport set that (at my request) to:

   Bugs: mailto:debian-backpo...@lists.debian.org

The 'reportbug' program respects this control header, so that's why your
bug report for the backport went (correctly) to the backports mailing
list. ('reportbug-ng' does not respect this header and the maintainer
stated he won't be supporting it.)

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#864073: TCP offloads disabled by default

[Michael Biebl]

Hi Hans-Kristian

Am 04.06.2017 um 01:56 schrieb Hans-Kristian Bakke:

> Luckily the fix is already in 233 and it is only a simple one liner that
> I really think should be patched into Stretch to avoid people getting
> hard to diagnose distro specific performance issues when going from
> jessie to stretch or coming from other distros.

Thanks for making us aware of this issue and providing such a detailed
bug report. This looks indeed like something which should be fixed for
stretch.
I intend to pull the patch, I'm just not sure if it will still make it
into 9.0 given the impeding release or will have to wait for the first
point release 9.1


Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#864075: unblock: icoutils/0.31.2-1.1

[James Lu]

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

Hi Release Team,

Please consider unblocking package icoutils:

This upload fixes an important bug which caused icoutils' wrestool utility to
break completely, due to a regression in version 0.31.2. wrestool is a program
used to extract icons from Windows programs, and its breakage caused dependant
packages (e.g. kde-runtime, gnome-exe-thumbnailer, gextractwinicons) to fail at
icon extraction entirely.

The full debdiff is attached.

unblock icoutils/0.31.2-1.1

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable-debug'), (500, 'testing-
debug'), (500, 'unstable'), (101, 'experimental'), (1, 'experimental-debug')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
diff -Nru icoutils-0.31.2/debian/changelog icoutils-0.31.2/debian/changelog
--- icoutils-0.31.2/debian/changelog2017-03-07 14:18:53.0 -0800
+++ icoutils-0.31.2/debian/changelog2017-05-30 23:12:09.0 -0700
@@ -1,3 +1,13 @@
+icoutils (0.31.2-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add patch fix-wrestool.patch from upstream commit
+
http://git.savannah.nongnu.org/cgit/icoutils.git/commit/?id=3c990fcc754c81a02ab5981d59b01025f1596b2c
+to fix wrestool not extracting icons - this is a regression from 0.31.2.
+Closes: #860220
+
+ -- James Lu   Tue, 30 May 2017 23:12:09 -0700
+
 icoutils (0.31.2-1) unstable; urgency=high
 
   * New upstream release.
diff -Nru icoutils-0.31.2/debian/.git-dpm icoutils-0.31.2/debian/.git-dpm
--- icoutils-0.31.2/debian/.git-dpm 2017-03-07 09:30:30.0 -0800
+++ icoutils-0.31.2/debian/.git-dpm 2017-05-30 23:12:09.0 -0700
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-c50ee01e3bbbc846f7b17e7de1d7c092e7b950c9
-c50ee01e3bbbc846f7b17e7de1d7c092e7b950c9
+f06d6e83d1b3256a5b6a0d42b8fc5293e6005bab
+f06d6e83d1b3256a5b6a0d42b8fc5293e6005bab
 c50ee01e3bbbc846f7b17e7de1d7c092e7b950c9
 c50ee01e3bbbc846f7b17e7de1d7c092e7b950c9
 icoutils_0.31.2.orig.tar.bz2
diff -Nru icoutils-0.31.2/debian/patches/fix-wrestool.patch 
icoutils-0.31.2/debian/patches/fix-wrestool.patch
--- icoutils-0.31.2/debian/patches/fix-wrestool.patch   1969-12-31 
16:00:00.0 -0800
+++ icoutils-0.31.2/debian/patches/fix-wrestool.patch   2017-05-30 
23:12:09.0 -0700
@@ -0,0 +1,37 @@
+From f06d6e83d1b3256a5b6a0d42b8fc5293e6005bab Mon Sep 17 00:00:00 2001
+From: Frank Richter 
+Date: Sat, 11 Mar 2017 14:10:50 +0100
+Subject: Revert "Add additional sanity checks to do_resource(). Found by Jerzy
+ Kramarz ."
+
+That "sanity check" rather broke everything.
+Also, I couldn't reproduce the issue it this change was intended to catch from 
the files I have
+any more, so it's probably not needed anyway.
+
+Origin: upstream, 
http://git.savannah.nongnu.org/cgit/icoutils.git/commit/?id=3c990fcc754c81a02ab5981d59b01025f1596b2c
+Bug-Debian: https://bugs.debian.org/860220
+Last-Update: 2017-05-30
+
+Patch-Name: fix-wrestool.patch
+---
+ wrestool/restable.c | 4 
+ 1 file changed, 4 deletions(-)
+
+diff --git a/wrestool/restable.c b/wrestool/restable.c
+index c60806f..f568434 100644
+--- a/wrestool/restable.c
 b/wrestool/restable.c
+@@ -87,13 +87,9 @@ do_resources_recurs (WinLibrary *fi, WinResource *base, 
WinResource *type_wr,
+   wr = list_resources (fi, base, );
+   if (wr == NULL)
+   return;
+-  if (!check_offset(fi->memory, fi->total_size, fi->name, [0], 
sizeof(WinResource)))
+-  return;
+ 
+   /* process each resource listed */
+   for (c = 0 ; c < rescnt ; c++) {
+-  if (!check_offset(fi->memory, fi->total_size, fi->name, [c], 
sizeof(WinResource)))
+-  break;
+   /* (over)write the corresponding WinResource holder with the 
current */
+   memcpy(WINRESOURCE_BY_LEVEL(wr[c].level), wr+c, 
sizeof(WinResource));
+ 
diff -Nru icoutils-0.31.2/debian/patches/series 
icoutils-0.31.2/debian/patches/series
--- icoutils-0.31.2/debian/patches/series   1969-12-31 16:00:00.0 
-0800
+++ icoutils-0.31.2/debian/patches/series   2017-05-30 23:12:09.0 
-0700
@@ -0,0 +1 @@
+fix-wrestool.patch

Bug#864074: vim: 'set mouse=' in /etc/vim/vimrc.local is ignored unless ~/.vimrc exists

[Andreas Beckmann]

Package: vim
Version: 2:8.0.0197-4
Severity: important

Hi,

for me the default of 'set mouse=a' is a misfeature, so I want to
disable it globally (my mouse usage ends after marking +
middle-click pasting of text in the terminal, that works fine
without pressing shift).

Unfortunately 'set mouse=' does not work in /etc/vim/vimrc.local, it is
just ignored. Other options work there.
But it works if (even an empty) ~/.vimrc does exist.

This is with vim.basic, running as root, in a fresh stretch install,
three ssh hops, a screen and a su away (where I wouldn't expect a
mouse to be usable) in case it does matter.

While trying to debug this, I also noticed discrepancies in what is set
by default, depending on whether an (empty) ~/.vimrc exists:

* without ~/.vimrc:

:set

  
--- Options ---
  display=truncateincsearch nolangremap   mouse=a   
  ruler   showcmd ttimeoutlen=100 ttymouse=xterm
  history=200 langnoremap   nomodelinenrformats=bin,hex 
  scrolloff=5 ttimeoutttyfast wildmenu
  backspace=indent,eol,start
  fileencodings=ucs-bom,utf-8,default,latin1
  printoptions=paper:a4
  
runtimepath=~/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vim80,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,~/.vim/after
  
suffixes=.bak,~,.swp,.o,.info,.aux,.log,.dvi,.bbl,.blg,.brf,.cb,.ind,.idx,.ilg,.inx,.out,.toc

* after touching ~/.vimrc:

:set


--- Options ---
nomodelineruler   ttyfast ttymouse=xterm
  backspace=indent,eol,start
  fileencodings=ucs-bom,utf-8,default,latin1
  printoptions=paper:a4
  
runtimepath=~/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vim80,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,~/.vim/after
  
suffixes=.bak,~,.swp,.o,.info,.aux,.log,.dvi,.bbl,.blg,.brf,.cb,.ind,.idx,.ilg,.inx,.out,.toc

The set of defaults should not depend on merely the fact that ~/.vimrc exists.

I consider this a regression from jessie, since vimrc.local worked
there without ~/.vimrc for all options I needed (but that didn't
include 'set mouse=').

For reference: these are the options set in jessie by vim.basic
independent from the existence of ~/.vimrc:

:set


--- Options ---
nomodelineruler   ttyfast ttymouse=xterm
  backspace=indent,eol,start
  
runtimepath=/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vim74,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,/.vim/after
  
suffixes=.bak,~,.swp,.o,.info,.aux,.log,.dvi,.bbl,.blg,.brf,.cb,.ind,.idx,.ilg,.inx,.out,.toc


Andreas

Bug#539798: texlive: please suggest -doc packages

[Norbert Preining]

Umpf, morning Chris,

[...]
> Anyway, shall we all take a step back and try again with this bug? Perhaps
> try and explain your point of view to Michael in another way? I look

You should maybe have taken a look at the systemd bug, where there is
definitely more to do. 

Thanks for your inactivity.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#864073: TCP offloads disabled by default

[Hans-Kristian Bakke]

Package: systemd
Version: 232-23
​Severity: important​

With systemd 232 it got the ability to set the NIC offloads. These offloads
are not initialized correctly though, so the NIC ends up without fully
enabled TCP offloads.

Example from stretch defaults:
...
tcp-segmentation-offload: on
tx-tcp-segmentation: off < ???
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
...

If I do the following (default in 231 and earlier):

  ethtool -K  tx-tcp-segmentation on

I get the correct version
...
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
...

This causes major performance issues in high speed networks (1Gbit/s and
higher) or in weak embedded devices and it is going to be (by accident) the
default in Stretch!

Luckily the fix is already in 233 and it is only a simple one liner that I
really think should be patched into Stretch to avoid people getting hard to
diagnose distro specific performance issues when going from jessie to
stretch or coming from other distros.

Some links with info:
* https://github.com/systemd/systemd/issues/4650
* https://github.com/systemd/systemd/pull/4639
* https://sourceforge.net/p/e1000/mailman/message/35663858/

Regards,
Hans-Kristian Bakke

Bug#864072: D-I: installer hangs on re-formatting ext3 partition (having grub in the partition boot record).

[Barry S. Newberger]

Package: debian-installer

Version: 8.8

Severity: important

Tags: d-i

It looks like the partman bug (#767682) is back in debian-8.8.0-amd64. The 
installer hangs when installing from debian-8.8.0-amd64-DVD-1.iso.

Using graphical expert install. Reformatting the boot partition on sda2 with 
ext3 filesystem.

Barry Newberger

Bug#860274: This hit me to

[Hans-Kristian Bakke]

I just want to say that this hit my Stretch setup by surprise today after
rebooting also. Basically this is the default setup with dnsmasq so the
package is basically broken in Stretch at the moment. Any chance that this
will be fixed before Stretch goes stable?

Regards,
Hans-Kristian

Bug#860220: Sponsor request for icoutils 0.31.2-1.1 (NMU)

[Colin Watson]

On Fri, Jun 02, 2017 at 12:19:49AM -0700, James Lu wrote:
> I've uploaded an NMU of icoutils to mentors, which is available at
> https://mentors.debian.net/debian/pool/main/i/icoutils/icoutils_0.31.2-1.1.dsc

Thanks for hunting this down.  I've gone ahead and sponsored this myself
(so, um, I guess it's not strictly an NMU now, but whatever).  I
imported it into git-dpm for my own convenience, so it's not exactly
identical to your source package, but the differences are only in minor
details of patch formatting.

Can you deal with requesting the unblock from the release team?

-- 
Colin Watson   [cjwat...@debian.org]

Bug#864071: [Pkg-utopia-maintainers] Bug#864071: SIGSEGV when connecting to bluetooth network

[Michael Biebl]

Am 03.06.2017 um 13:18 schrieb chrysn:
> Package: network-manager
> Version: 1.8.0-2
> Severity: normal
> 
> When I connect to the Bluetooth connection to an Android cellphone I
> paired via bluetooth using blueman, network-manager segfaults.
> Backtrace:
> 
> (gdb) bt
> #0  0x55609794 in nm_ip6_config_capture (platform=, 
> ifindex=ifindex@entry=0,
> capture_resolv_conf=capture_resolv_conf@entry=0, 
> use_temporary=use_temporary@entry=NM_SETTING_IP6_CONFIG_PRIVACY_UNKNOWN)
> at src/nm-ip6-config.c:368
> #1  0x55659101 in act_stage3_ip6_config_start (self=0x55c3bce0, 
> out_config=,
> out_failure_reason=) at src/devices/nm-device.c:7727
> #2  0x55668f71 in nm_device_activate_stage3_ip6_start 
> (self=self@entry=0x55c3bce0) at src/devices/nm-device.c:7845
> #3  0x5566a2f0 in activate_stage3_ip_config_start 
> (self=0x55c3bce0) at src/devices/nm-device.c:7922
> #4  0x5564f1f2 in activation_source_handle_cb (self=0x55c3bce0, 
> family=family@entry=2)
> at src/devices/nm-device.c:4453
> #5  0x5564f2de in activation_source_handle_cb4 (user_data= out>) at src/devices/nm-device.c:4390
> #6  0x76b776aa in g_main_context_dispatch () from 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #7  0x76b77a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #8  0x76b77d82 in g_main_loop_run () from 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #9  0x55580de3 in main (argc=, argv=) 
> at src/main.c:435
> (gdb)
> 
> Based on the trace, I set IPv6 on that interface to "ignore"; the link
> then works as expected.

Probably https://bugzilla.gnome.org/show_bug.cgi?id=782545

Could you try the patch mentioned in the upstream bug tracker?


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



signature.asc
Description: OpenPGP digital signature

Bug#864071: SIGSEGV when connecting to bluetooth network

[chrysn]

Package: network-manager
Version: 1.8.0-2
Severity: normal

When I connect to the Bluetooth connection to an Android cellphone I
paired via bluetooth using blueman, network-manager segfaults.
Backtrace:

(gdb) bt
#0  0x55609794 in nm_ip6_config_capture (platform=, 
ifindex=ifindex@entry=0,
capture_resolv_conf=capture_resolv_conf@entry=0, 
use_temporary=use_temporary@entry=NM_SETTING_IP6_CONFIG_PRIVACY_UNKNOWN)
at src/nm-ip6-config.c:368
#1  0x55659101 in act_stage3_ip6_config_start (self=0x55c3bce0, 
out_config=,
out_failure_reason=) at src/devices/nm-device.c:7727
#2  0x55668f71 in nm_device_activate_stage3_ip6_start 
(self=self@entry=0x55c3bce0) at src/devices/nm-device.c:7845
#3  0x5566a2f0 in activate_stage3_ip_config_start (self=0x55c3bce0) 
at src/devices/nm-device.c:7922
#4  0x5564f1f2 in activation_source_handle_cb (self=0x55c3bce0, 
family=family@entry=2)
at src/devices/nm-device.c:4453
#5  0x5564f2de in activation_source_handle_cb4 (user_data=) at src/devices/nm-device.c:4390
#6  0x76b776aa in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x76b77a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x76b77d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x55580de3 in main (argc=, argv=) at 
src/main.c:435
(gdb)

Based on the trace, I set IPv6 on that interface to "ignore"; the link
then works as expected.

Please let me know if and which other debug information you might need.

-- System Information:
Debian Release: 9.0
  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.11.0-rc2+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages network-manager depends on:
ii  adduser3.115
ii  dbus   1.10.18-1
ii  init-system-helpers1.48
ii  libaudit1  1:2.6.7-2
ii  libbluetooth3  5.43-2
ii  libc6  2.24-11
ii  libcurl3-gnutls7.52.1-5
ii  libglib2.0-0   2.50.3-2
ii  libgnutls303.5.8-5
ii  libjansson42.9-1
ii  libmm-glib01.6.4-1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.20-1
ii  libnl-3-2003.2.27-2
ii  libnm0 1.8.0-2
ii  libpam-systemd 232-24
ii  libpolkit-agent-1-00.105-18
ii  libpolkit-gobject-1-0  0.105-18
ii  libpsl50.17.0-4
ii  libreadline7   7.0-3
ii  libselinux12.6-3+b1
ii  libsystemd0232-24
ii  libteamdctl0   1.26-1+b1
ii  libudev1   232-24
ii  libuuid1   2.29.2-1
ii  lsb-base   9.20161125
ii  policykit-10.105-18
ii  udev   232-24
ii  wpasupplicant  2:2.4-1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base 2.77-1
ii  iptables 1.6.0+snapshot20161117-6
ii  iputils-arping   3:20161105-1
ii  isc-dhcp-client  4.3.5-3
ii  modemmanager 1.6.4-1
ii  ppp  2.4.7-1+4

Versions of packages network-manager suggests:
pn  libteam-utils  

-- no debconf information

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature

Bug#855911: linux-image-4.9.0-1-armmp: MMC failure on A20-OLinuXIno-LIME2

[Ben Hutchings]

On Sat, 2017-06-03 at 22:56 +0200, Thibaut Girka wrote:
> I keep experiencing this issue even with a brand new board (same model, newer
> hw revision) and on linux-image-4.10.0-rc6-armmp.
> 
> I have been informed that this issue might have been fixed by:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers?id=2154d94b40ea2a5de05245521371d0461bb0d669

I don't think so.  That claims to fix a bug introduced in 4.10-rc1.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner



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

Bug#863890: dblatex: postrm fails on jessie to stretch upgrade

[Andreas Beckmann]

Adding Norbert (texlive maintainer) to the discussion, short summary:
   There was a jessie->stretch upgrade issue reported regarding
   dblatex: dblatex.postrm failed due to missing mktexlsr. See #863890
   for the discussion and logs.

As I did not observe such a problem during my piuparts tests, I have a
few questions.

If I read the upgrade log correct, dblatex got first deconfigured and
later *removed* during the distupgrade. Actually most of the texlive
stack seems to get removed (including texlive-binaries, which ships
mktexlsr). Why did this happen? What was the actual command you used to
perform the upgrade? What was the set of packages installed before the
upgrade?

dpkg spews a lot of warnings about dependency problems, so it's not
dblatex's fault if its postrm failed due to dependency violations.
More likely apt (from jessie) is at fault here for choosing a broken
upgrade path.

On Sat, 03 Jun 2017 19:27:10 +0200 Andreas Hoenen
 wrote:
> mktexlsr needs to be called in dblatex postrm/postinst, as documented
> there:
>
> # A call to 'mktexlsr' is needed to register the dblatex TeX files
> # in the TeX database '/var/lib/texmf/ls-R-TEXMFMAIN'.

That sounds like a very generic requirement for *all* tex packages.
dblatex doesn't seem to use dh_installtex? That creates maintainer
scripts capable of running mktexlsr etc. and maybe have automatic error
handling.

I don't see a point of updating dblatex in jessie to make its postrm
handle "invalid states", at least not until the underlying cause has
been identified.


Andreas

Bug#539798: texlive: please suggest -doc packages

[Chris Lamb]

Hi Norbert at al.,

> > this is a blatant violation of the Debian policy and such an RC bug.
> > I don't want to see stretch released with such a grave bug.
> 
> It seems Michael Biebl has lost contact to reality and is playing
> irrelevant games.

Regardless of my own opinion here as a Debian Developer on the
intepretation of the Policy, I worry this has been escalated too soon
with leader@ which, in itself, will not help us reach an equitable and
happy outcome for all.

Furthermore, claiming one's opponent has lost their grip on reality is,
alas, not an good example of "assuming good faith" in an argument. :)
We should strive to keep our discussions as objective and technical as
possible, no?

Anyway, shall we all take a step back and try again with this bug? Perhaps
try and explain your point of view to Michael in another way? I look
forward to this being resolved without me. :)


Best wishes,

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

Bug#864070: xserver-xorg-core: consistently crashing on startup, unable to start X

[Austin English]

Package: xserver-xorg-core
Version: 2:1.19.3-1
Severity: important

Dear Maintainer,

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

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

   Regular system updates. No changes were made to xorg.conf, but on
   next boot, the system has a black screen. Getting in to the system
   via SSH shows that X had crashed:

[41.199] (EE) Backtrace:
[41.200] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x561eb2e0141a]
[41.200] (EE) 1: /usr/lib/xorg/Xorg (0x561eb2c48000+0x1bd1c9)
[0x561eb2e051c9]
[41.200] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fa5e9e11000+0x110c0) [0x7fa5e9e220c0]
[41.200] (EE) 3: /usr/lib/xorg/Xorg (RRSetChanged+0x92) [0x561eb2d5ec42]
[41.200] (EE) 4: /usr/lib/xorg/Xorg (RRScreenSetSizeRange+0x54)
[0x561eb2d63804]
[41.200] (EE) 5: /usr/lib/xorg/Xorg
(xf86RandR12CreateScreenResources+0x310) [0x561eb2d1cf30]
[41.200] (EE) 6: /usr/lib/xorg/Xorg (0x561eb2c48000+0xc80c0)
[0x561eb2d100c0]
[41.200] (EE) 7: /usr/lib/xorg/Xorg (0x561eb2c48000+0x583b1)
[0x561eb2ca03b1]
[41.200] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf1) [0x7fa5e9a922b1]
[41.200] (EE) 9: /usr/lib/xorg/Xorg (_start+0x2a) [0x561eb2c8a21a]
[41.200] (EE)
[41.200] (EE) Segmentation fault at address 0xb8
[41.200] (EE)
Fatal server error:
[41.200] (EE) Caught signal 11 (Segmentation fault). Server aborting

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


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

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by
glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to
/usr/lib/mesa-diverted/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by
glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by
glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to
/usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so to
/usr/lib/mesa-diverted/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGL.so.1.2 to
/usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by
glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by
glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by
glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to
/usr/lib/mesa-diverted/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to

Bug#864026: seqan2: FTBFS when built with dpkg-buildpackage -A

[Chris Lamb]

Hi Andreas,

> since Santiago explicitly addressed you:  There is no point that you
> do another NMU - I'll care for it right now to safe you the work.

Thank you :)


Regards,

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

Bug#864069: unblock: piuparts/0.77

[Holger Levsen]

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

Please unblock package piuparts, mostly to update distro.conf for the wonderful
time when Stretch will be stable. I'll comment on the other changes now 
inbetween the changelog entries:

+piuparts (0.77) unstable; urgency=medium
+
+  [ Andreas Beckmann ]
+  * distros.conf:
+- Add aliases for oldstable and oldoldstable.

very nice to have.

+- Update aliases for stretch being released as stable.

this change is the reason why we want 0.77 in stretch.

+  * piuparts.py:
+- Add to ignored_files:
+  + /etc/rc.local
+  + /etc/X11/Xwrapper.config  (Closes: #859929)
+  + /var/lib/apt/daily_lock

trivial one liner changes, reducing some clear false negatives from piuparts 
runs.

+  * piuparts-analyze.py:
+- Do not ignore Ctrl-C.

regression fix compared to 0.76, also trivial one-liner.

+  * scripts/post_distupgrade_base_cleanup: Remove (transitional) sysvinit from
+stretch.  (Closes: #860819)
+  * scripts/pre_distupgrade_zz_database-server: Do not migrate manually from
+mysql-server to default-mysql-server (aka mariadb-server), there is now a
+transitional mysql-server package in stretch.

scripts are generally (+sadly) only used by a very very few users, until
#752256 will be fixed, as such, these are very low risk. OTOH they *are*
very helpful, when people try to reproduce piuparts.d.o logs by running
the commands from those logs.

+  [ Holger Levsen ]
+  * piuparts-report.py:
+- update navigation to point to piuparts.conf-template.pejacevic.

trivial change updating one URL…



$ diffstat piuparts_0.77.diff 
 .gitignore|2 
 conf/distros.conf |   28 --
 custom-scripts/scripts/post_distupgrade_base_cleanup  |1 
 custom-scripts/scripts/pre_distupgrade_zz_database-server |   62 --
 debian/.gitignore |5 -
 debian/changelog  |   25 +
 piuparts-analyze.py   |2 
 piuparts-report.py|2 
 piuparts.py   |3 
 9 files changed, 51 insertions(+), 79 deletions(-)

I don't know why the .gitignore files were included in the previous upload but
I think it's appropriate to drop them now.

The full debdiff is attached.

unblock piuparts/0.77


Thanks for your "endless" work on Stretch!

-- 
cheers,
Holger
diff -Nru piuparts-0.76/conf/distros.conf piuparts-0.77/conf/distros.conf
--- piuparts-0.76/conf/distros.conf	2017-03-12 17:55:07.0 +0100
+++ piuparts-0.77/conf/distros.conf	2017-06-03 19:01:54.0 +0200
@@ -127,25 +127,33 @@
 depends = sid
 
 
+[experimental]
+depends = sid
+target-release = experimental
+
+
 # alias
-[stable]
+[oldoldstable]
+distribution = wheezy
+
+# alias
+[oldstable]
 distribution = jessie
 
 # alias
-[testing]
+[stable]
 distribution = stretch
 
-
-[experimental]
-depends = sid
-target-release = experimental
+# alias
+[testing]
+distribution = buster
 
 
 # It's also possible to have "virtual" entries by setting uri to
 # the string "None". This allows e.g. to combine several partial
 # distributions. Such virtual distros can be used for standalone
-# piuparts runs, but not in master-slave setup.
-[squeeze-current]
+# piuparts runs, but not in master-slave setup (due to a missing
+# dependency on a full distro).
+[stretch-current]
 uri = None
-depends = squeeze/updates squeeze-updates
-
+depends = stretch/updates stretch-updates
diff -Nru piuparts-0.76/custom-scripts/scripts/post_distupgrade_base_cleanup piuparts-0.77/custom-scripts/scripts/post_distupgrade_base_cleanup
--- piuparts-0.76/custom-scripts/scripts/post_distupgrade_base_cleanup	2016-09-03 14:14:59.0 +0200
+++ piuparts-0.77/custom-scripts/scripts/post_distupgrade_base_cleanup	2017-06-03 19:16:02.0 +0200
@@ -66,6 +66,7 @@
 	[ "$PIUPARTS_DISTRIBUTION" = "stretch-proposed" ] ; then
 
 	mark_for_purge libprocps3
+	mark_for_purge sysvinit
 
 fi
 
diff -Nru piuparts-0.76/custom-scripts/scripts/pre_distupgrade_zz_database-server piuparts-0.77/custom-scripts/scripts/pre_distupgrade_zz_database-server
--- piuparts-0.76/custom-scripts/scripts/pre_distupgrade_zz_database-server	2017-03-12 17:55:07.0 +0100
+++ piuparts-0.77/custom-scripts/scripts/pre_distupgrade_zz_database-server	2017-06-03 21:55:00.0 +0200
@@ -26,6 +26,7 @@
 
 CANDIDATES=
 CANDIDATES="$CANDIDATES default-mysql-server"
+CANDIDATES="$CANDIDATES mysql-server"
 CANDIDATES="$CANDIDATES postgresql"
 CANDIDATES="$CANDIDATES postgresql-8.3"
 CANDIDATES="$CANDIDATES postgresql-8.4"
@@ -39,17 +40,7 @@
 		;;
 esac
 
-case "$PIUPARTS_DISTRIBUTION_NEXT" in
-	stretch)
-		: # no mysql-server
-		;;
-	*)
-		CANDIDATES="$CANDIDATES mysql-server"
-		;;
-esac
-
 PACKAGES=

Bug#864068: unblock: debian-edu-doc/1.921~20170603

[Holger Levsen]

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

Please unblock package debian-edu-doc, it just contains documentation and
translation updates (matching the change in debian-edu-install/1.916, among 
others).

$ debdiff debian-edu-doc_1.920~20170528.dsc 
debian-edu-doc_1.921~20170603.dsc|diffstat
 debian/changelog |   18 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.nb.po   |   36 -
 documentation/debian-edu-stretch/debian-edu-stretch-manual.da.po |   58 -
 documentation/debian-edu-stretch/debian-edu-stretch-manual.de.po |   59 -
 documentation/debian-edu-stretch/debian-edu-stretch-manual.es.po |   57 -
 documentation/debian-edu-stretch/debian-edu-stretch-manual.fr.po |   77 --
 documentation/debian-edu-stretch/debian-edu-stretch-manual.it.po |  116 +--
 documentation/debian-edu-stretch/debian-edu-stretch-manual.ja.po |   70 +-
 documentation/debian-edu-stretch/debian-edu-stretch-manual.nb.po |  305 
--
 documentation/debian-edu-stretch/debian-edu-stretch-manual.nl.po |  106 +--
 documentation/debian-edu-stretch/debian-edu-stretch-manual.pl.po |   26 
 documentation/debian-edu-stretch/debian-edu-stretch-manual.pot   |   26 
 documentation/debian-edu-stretch/debian-edu-stretch-manual.xml   |   12 
 documentation/debian-edu-stretch/debian-edu-stretch-manual.zh.po |   38 -
 documentation/rosegarden/rosegarden-manual.nb.po |   60 -
 15 files changed, 459 insertions(+), 605 deletions(-)

I've also attached this diff.

unblock debian-edu-doc/1.921~20170603


Thanks for your work on Stretch!

-- 
cheers,
Holger


debian-edu-doc_1.921~20170603.diff.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#864049: unblock: mate-desktop/1.16.2-2

[Mike Gabriel]

Control: tags -1 - moreinfo

Hi Ivo, Niels,

On  Sa 03 Jun 2017 23:28:45 CEST, Ivo De Decker wrote:


Hi,

On Sat, Jun 03, 2017 at 08:17:00PM +, Niels Thykier wrote:

>> Please consider unblocking a minor follow-up fix for package mate-desktop
>>
>> The DH call until mate-desktop 1.16.2-1 has been missing the "--with gir"
>> option. The proposed next upload of mate-desktop will fix that. A
>> .debdiff has been attached.
>>
>> unblock mate-desktop/1.16.2-2
>>
>> [...]
>
> Please go ahead.
>
> ~Niels
>

Unblocked, thanks.

~Niels



This bug was closed by mistake (and reopened). To be clear: this bug is still
waiting for the upload to unstable.

Cheers,

Ivo


Ah... not uploaded by me so far. Right. Dang. Just did so. Should  
appear in unstable soon.


Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpLqwqYMLTxq.pgp
Description: Digitale PGP-Signatur

Bug#862558: plasma-workspace: Freezes during login with fresh installed Stretch Japanese environment

[Nobuhiro Iwamatsu]

Followup-For: Bug #862558

Dear maintainer,

I plan to NMU  plasma-workspace if the release team approves the attached patch.
 (Unblock request #864067)

Best regards,
  Nobuhiro


2017-05-31 23:38 GMT+09:00 YOSHINO Yoshihito :
> Followup-For: Bug #862558
> Control: reassign -1 plasma-workspace
> Control: affects -1 uim-qt5 uim-mozc
> Control: tags -1 + patch
>
> Dear Maintainer,
>
> This is a bug in ksplashqml. An upstream commit
> https://cgit.kde.org/plasma-workspace.git/commit/?id=56d2c15b9acb9c4b57398b281685807c3191f622
> has caused this problem.
>
> x-session-manag,133,kdetest /usr/bin/x-session-manager
>   ├─(ksplashqml,232)
>   ├─ssh-agent,191 /usr/bin/im-launch x-session-manager
>   ├─uim-toolbar,220
>   │   ├─{llvmpipe-0},235
>   │   ├─{llvmpipe-1},236
>   │   ├─{llvmpipe-2},237
>   │   └─{llvmpipe-3},238
>   └─uim-xim,219
> ksplashqml,233,kdetest Breeze --pid
>   ├─mozc_server,239
>   │   ├─{IPCServer},244
>   │   ├─{QueueTimer},240
>   │   ├─{QueueTimer},243
>   │   └─{WatchDog},242
>   ├─uim-candwin-qt5,245 -v
>   │   ├─{QDBusConnection},249
>   │   └─{QXcbEventReader},248
>   ├─{QDBusConnection},255
>   ├─{QQmlThread},254
>   ├─{QXcbEventReader},234
>   ├─{llvmpipe-0},250
>   ├─{llvmpipe-1},251
>   ├─{llvmpipe-2},252
>   └─{llvmpipe-3},253
>
> # strace -f -p 133
> strace: Process 133 attached
> read(3, ^Cstrace: Process 133 detached
>  
>
> It looks like the parent process (133), x-session-manager (startkde
> script), is waiting for the stdout of the ksplashqml process (232),
> but which is now defunct. Its child process(es) may be writing to the
> same fd.
>
> # ls -l /proc/133/fd/3
> lr-x-- 1 kdetest kdetest 64 May 31 05:13 /proc/133/fd/3 -> pipe:[88694]
>
> The direct child of the ksplashqml process (233), the splash screen daemon,
> closes the file descriptor at ksplash/ksplashqml/main.cpp:97.
>
> # ls -l /proc/233/fd/1
> ls: cannot access '/proc/233/fd/1': No such file or directory
>
> One of the children of the process (239), mozc_server, is holding the fd:
>
> # ls -l /proc/239/fd/1
> l-wx-- 1 kdetest kdetest 64 May 31 05:14 /proc/239/fd/1 -> pipe:[88694]
>
> So the startkde process has finished reading the pid number string from
> the now-defunct process, but is still waiting for another write(s) until
> the (shared) fd has been closed.
>
> This mozc_server process has been started during uim-qt5
> (a QPlatformInputContext) startup in the SplashApp
> initialization phase at ksplash/ksplashqml/main.cpp:92.
>
> Due to the upstream commit the splash screen daemon does not close file
> descriptors before the SplashApp initialization, thus its subprocess
> shares the fds.
>
> The commit log states Wayland initialization of this daemon needs the
> channels. While it may require open file descriptors 0, 1 or 2,
> no one should expect the process to talk to the parent through the
> descriptors, since the splash screen is a daemon.
>
> An attached patch reverts the commit and redirects the file descriptors
> to /dev/null.
>
> Regards,
> --
> YOSHINO Yoshihito 



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


plasma-workspace_5.8.6-2.1.debdiff
Description: Binary data

Bug#864049: unblock: mate-desktop/1.16.2-2

[Ivo De Decker]

Hi,

On Sat, Jun 03, 2017 at 08:17:00PM +, Niels Thykier wrote:
> >> Please consider unblocking a minor follow-up fix for package mate-desktop
> >>
> >> The DH call until mate-desktop 1.16.2-1 has been missing the "--with gir"
> >> option. The proposed next upload of mate-desktop will fix that. A
> >> .debdiff has been attached.
> >>
> >> unblock mate-desktop/1.16.2-2
> >>
> >> [...]
> > 
> > Please go ahead.
> > 
> > ~Niels
> > 
> 
> Unblocked, thanks.
> 
> ~Niels
> 

This bug was closed by mistake (and reopened). To be clear: this bug is still
waiting for the upload to unstable.

Cheers,

Ivo

Bug#864067: unblock: plasma-workspace/5.8.6-2.1

[Nobuhiro Iwamatsu]

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

Hi,

I want to upload a NMU of plasma-workspace to unstable fixing an issue 
where processing stopped in ksplashqml on some environments(e.g. Japanese
environment), proposed patch attached.

unblock plasma-workspace/5.8.6-2.1.

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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru plasma-workspace-5.8.6/debian/changelog 
plasma-workspace-5.8.6/debian/changelog
--- plasma-workspace-5.8.6/debian/changelog 2017-03-16 03:45:10.0 
+0900
+++ plasma-workspace-5.8.6/debian/changelog 2017-06-02 22:17:22.0 
+0900
@@ -1,3 +1,12 @@
+plasma-workspace (4:5.8.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix problem where processing stopped in ksplashqml on some environments.
+(Closes: #862558)
+Add patches/replace-fds.patch.
+
+ -- Nobuhiro Iwamatsu   Fri, 02 Jun 2017 22:17:22 +0900
+
 plasma-workspace (4:5.8.6-2) unstable; urgency=medium
 
   * Release to unstable
diff -Nru plasma-workspace-5.8.6/debian/patches/replace-fds.patch 
plasma-workspace-5.8.6/debian/patches/replace-fds.patch
--- plasma-workspace-5.8.6/debian/patches/replace-fds.patch 1970-01-01 
09:00:00.0 +0900
+++ plasma-workspace-5.8.6/debian/patches/replace-fds.patch 2017-06-02 
22:17:22.0 +0900
@@ -0,0 +1,122 @@
+Description: Not close stdin,stdout,stderr, and redirects stdin,stdout,stderr 
to /dev/null
+ This fix a bug in ksplashqml. An upstream commit
+ 
https://cgit.kde.org/plasma-workspace.git/commit/?id=56d2c15b9acb9c4b57398b281685807c3191f622
+ has caused this problem.
+
+ x-session-manag,133,kdetest /usr/bin/x-session-manager
+   +-(ksplashqml,232)
+   +-ssh-agent,191 /usr/bin/im-launch x-session-manager
+   +-uim-toolbar,220
+   |   +-{llvmpipe-0},235
+   |   +-{llvmpipe-1},236
+   |   +-{llvmpipe-2},237
+   |   `-{llvmpipe-3},238
+   `-uim-xim,219
+ ksplashqml,233,kdetest Breeze --pid
+   +-mozc_server,239
+   |   +-{IPCServer},244
+   |   +-{QueueTimer},240
+   |   +-{QueueTimer},243
+   |   `-{WatchDog},242
+   +-uim-candwin-qt5,245 -v
+   |   +-{QDBusConnection},249
+   |   `-{QXcbEventReader},248
+   |-{QDBusConnection},255
+   |-{QQmlThread},254
+   |-{QXcbEventReader},234
+   |-{llvmpipe-0},250
+   |-{llvmpipe-1},251
+   |-{llvmpipe-2},252
+   `-{llvmpipe-3},253
+ 
+ # strace -f -p 133
+ strace: Process 133 attached
+ read(3, ^Cstrace: Process 133 detached
+  
+ 
+ It looks like the parent process (133), x-session-manager (startkde
+ script), is waiting for the stdout of the ksplashqml process (232),
+ but which is now defunct. Its child process(es) may be writing to the
+ same fd.
+ 
+ # ls -l /proc/133/fd/3
+ lr-x-- 1 kdetest kdetest 64 May 31 05:13 /proc/133/fd/3 -> pipe:[88694]
+ 
+ The direct child of the ksplashqml process (233), the splash screen daemon,
+ closes the file descriptor at ksplash/ksplashqml/main.cpp:97.
+ 
+ # ls -l /proc/233/fd/1
+ ls: cannot access '/proc/233/fd/1': No such file or directory
+ 
+ One of the children of the process (239), mozc_server, is holding the fd:
+ 
+ # ls -l /proc/239/fd/1
+ l-wx-- 1 kdetest kdetest 64 May 31 05:14 /proc/239/fd/1 -> pipe:[88694]
+ 
+ So the startkde process has finished reading the pid number string from
+ the now-defunct process, but is still waiting for another write(s) until
+ the (shared) fd has been closed.
+ 
+ This mozc_server process has been started during uim-qt5
+ (a QPlatformInputContext) startup in the SplashApp
+ initialization phase at ksplash/ksplashqml/main.cpp:92.
+ 
+ Due to the upstream commit the splash screen daemon does not close file
+ descriptors before the SplashApp initialization, thus its subprocess
+ shares the fds.
+ 
+ The commit log states Wayland initialization of this daemon needs the
+ channels. While it may require open file descriptors 0, 1 or 2,
+ no one should expect the process to talk to the parent through the
+ descriptors, since the splash screen is a daemon.
+ 
+ An attached patch reverts the commit and redirects the file descriptors
+ to /dev/null.
+Forwarded: https://bugs.kde.org/show_bug.cgi?id=380495
+Bug-Debian: https://bugs.debian.org/862558
+Author: YOSHINO Yoshihito 
+Last-Update: 2017-06-02
+
+--- plasma-workspace-5.8.6.orig/ksplash/ksplashqml/main.cpp
 plasma-workspace-5.8.6/ksplash/ksplashqml/main.cpp
+@@ -24,6 +24,9 @@
+ #include 
+ 
+ #include 
++#include 
++#include 
++#include 
+ #include 
+ 
+ void logMessageHandler(QtMsgType type, const char *msg)
+@@ -83,6 +86,16 @@ int main(int argc, char **argv)
+ 
+ return 0;
+ }
++
++  

Bug#864066: release-notes: proofreading sweep - release-notes.dbk

[Justin B Rye]

Package: release-notes
Severity: wishlist
Tags: patch

This case genuinely is only wishlist, and needn't go in until after
the release.  But it's already overdue - I commented on it in 2015
and put off doing anything about it.

The glossary section contains many entries explaining abbreviations
that are no longer present anywhere in the text:
 * ACPI
 * ALSA
 * APM
 * GPG
 * IDE
 * LDAP
 * LILO
 * LVM
 * NBD
 * NIC
 * NIS
 * OSS
 * RAID
 * RPC
 * SATA
 * UUID
 * VGA
 * WPA
Some of these have better odds of coming back than others, but I'd
vote to trim the entries for APM, IDE, LILO, OSS, RPC, and VGA this
time round (bringing the proportion of dead entries to below 50%!),
and look again next time.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Index: release-notes.dbk
===
--- release-notes.dbk	(revision 11526)
+++ release-notes.dbk	(working copy)
@@ -340,10 +340,6 @@
 Advanced Linux Sound Architecture
   
   
-APM
-Advanced Power Management
-  
-  
 BD
 Blu-ray Disc
   
@@ -384,18 +380,10 @@
 GNU Privacy Guard
   
   
-IDE
-Integrated Drive Electronics
-  
-  
 LDAP
 Lightweight Directory Access Protocol
   
   
-LILO
-LInux LOader
-  
-  
 LSB
 Linux Standard Base
   
@@ -424,10 +412,6 @@
 Network Information Service
   
   
-OSS
-Open Sound System
-  
-  
 PHP
 PHP: Hypertext Preprocessor
   
@@ -436,10 +420,6 @@
 Redundant Array of Independent Disks
   
   
-RPC
-Remote Procedure Call
-  
-  
 SATA
 Serial Advanced Technology Attachment
   
@@ -464,10 +444,6 @@
 Universally Unique Identifier
   
   
-VGA
-Video Graphics Array
-  
-  
 WPA
 Wi-Fi Protected Access
   

Bug#864048: unblock: marco/1.16.1-1

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Sa 03 Jun 2017 23:02:00 CEST, Niels Thykier wrote:


Mike Gabriel:

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

Please consider unblocking package marco ready for upload.


From upstream we received a last-minute fix for #828077 (mate-panel:

Mouse focus problem with stack of applications). The underlying cause has
been fixed in the MATE window manager aka marco.


unblock marco/1.16.1-1

[...]


Due to the short time left until the release and the minor risk of
breaking unrelated software, please go ahead and we will revisit it
later once it has had some time in unstable.

Thanks,
~Niels


Uploaded.

Thanks,
Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpSQWhFs_WbS.pgp
Description: Digitale PGP-Signatur

Bug#864065: unblock: mate-themes/3.22.11-1

[Mike Gabriel]

HI Niels, hi Ivo, hi all,

On  Sa 03 Jun 2017 23:10:46 CEST, Mike Gabriel wrote:


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

Please consider unblocking package mate-themes ready for upload.

With upstream I have been discussing the ideal solution for mate-themes
in Debian 9. Upstream highly recommends shipping mate-themes 3.22.11 as
there have been tons of fixes and improvements compared to what we have
in Debian 9 at the moment (mate-themes 3.22.6-1).

However, as the changeset is far from addressing issues atomically, I
have also prepared a mate-themes 3.22.6-2 cherry-picking one fix for an
issues with renaming files in Caja. See #853288 for details.

unblock mate-themes/3.22.11-1


I truely think that mate-themes/3.22.11-1 is the better theme for MATE  
in Debian 9. So I just uploaded it to unstable.


If you feel unwell with unblocking this, it is totally fine and I will  
look into fixing #853288 with the first point release via stretch-pu.


Thanks for your work, guys!!!
Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpAstaWbeCZ4.pgp
Description: Digitale PGP-Signatur

Bug#852963: almost NMU

[Geert Stappers]

Almost I did a NMU. Attached the nmu diff patch for it.

I hope this update to bugreport #852963
will trigger some reaction.
diff -Nru git-sh-1.1/debian/changelog git-sh-1.1/debian/changelog
--- git-sh-1.1/debian/changelog	2011-03-06 22:30:05.0 +0100
+++ git-sh-1.1/debian/changelog	2017-06-03 22:50:07.0 +0200
@@ -1,3 +1,16 @@
+git-sh (1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Mentions /usr/bin/git-shell in description. Closes: #852963
+  * First upload in more then six years.
+- Standards-Version from 3.9.1 to 3.9.8, no changes needed
+- Build-Depends on debhelper, it is version 10.x.y. these days
+- compat: version from 7 to 9
+- watch: deprecated githubredir replace with working content
+  this revealed that upstream has a new version for four years
+
+ -- Geert Stappers   Sat, 03 Jun 2017 22:50:07 +0200
+
 git-sh (1.1-1) unstable; urgency=low
 
   * Initial release (Closes: #590440)
diff -Nru git-sh-1.1/debian/compat git-sh-1.1/debian/compat
--- git-sh-1.1/debian/compat	2011-03-06 21:02:29.0 +0100
+++ git-sh-1.1/debian/compat	2017-06-03 21:58:45.0 +0200
@@ -1 +1 @@
-7
+9
diff -Nru git-sh-1.1/debian/control git-sh-1.1/debian/control
--- git-sh-1.1/debian/control	2011-03-06 22:30:05.0 +0100
+++ git-sh-1.1/debian/control	2017-06-03 22:36:06.0 +0200
@@ -2,15 +2,18 @@
 Maintainer: Alex Morega 
 Section: vcs
 Priority: optional
-Standards-Version: 3.9.1
-Build-Depends: debhelper (>= 7.3.8)
+Standards-Version: 3.9.8
+Build-Depends: debhelper
 Homepage: http://rtomayko.github.com/git-sh/
 
 Package: git-sh
 Architecture: all
 Depends: ${misc:Depends}, git
-Description: a git shell
+Description: customized bash environment suitable for git work
  git-sh starts an interactive bash(1) session modified for git-heavy
  workflows.  Typical usage is to change into the directory of a git work
  tree or bare repository and run the git-sh command to start an interactive
  shell session.
+ .
+ Not be confused with /usr/bin/git-shell for restricting SSH users.
+ /usr/bin/git-shell is in the default git package.
diff -Nru git-sh-1.1/debian/watch git-sh-1.1/debian/watch
--- git-sh-1.1/debian/watch	2011-03-06 22:30:05.0 +0100
+++ git-sh-1.1/debian/watch	2017-06-03 22:13:36.0 +0200
@@ -1,5 +1,9 @@
-# Compulsory line, this is a version 3 file
-version=3
+# Compulsory line, this is a uscan version 4 watch file
+version=4
 
 # github repository
-http://githubredir.debian.net/github/rtomayko/git-sh/ (.*)\.tar\.gz
+opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%git-sh-$1.tar.gz%" \
+https://github.com/rtomayko/git-sh/tags \
+(?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate
+
+# l l

Bug#863915: (no subject)

[Michael Catanzaro]

That all seems about right. Your description of recent major 
regressions is an accurate portrayal of the risk involved in updating 
WebKitGTK+ in Debian.


One minor correction: Berto mostly works on QEMU, not WebKit, though he 
maintains the WebKitGTK+ package in Debian. (Thanks Berto!)

Bug#863914: linux-libc-dev: Install separate from /usr/include

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 2017-06-01 at 17:14 -0400, Zack Weinberg wrote:
> Package: linux-libc-dev
> Version: 4.11-1~exp2
> Severity: wishlist
> 
> Certain low-level programs and libraries, notably glibc, would like to
> be able to make sure that they do *not* use any system headers during
> their build, other than the kernel's headers and the ones provided by
> the compiler (stddef.h, stdarg.h etc)  It would be much easier to arrange
> this if the kernel's headers were installed in a location separate from
> /usr/include and then symlinked into /usr/include.  (It would be fine to
> symlink just the directories.)

I don't understand how this would help.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner



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

Bug#864048: unblock: marco/1.16.1-1

[Niels Thykier]

Mike Gabriel:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please consider unblocking package marco ready for upload.
> 
>>From upstream we received a last-minute fix for #828077 (mate-panel:
> Mouse focus problem with stack of applications). The underlying cause has
> been fixed in the MATE window manager aka marco.
> 
> 
> unblock marco/1.16.1-1
> 
> [...]

Due to the short time left until the release and the minor risk of
breaking unrelated software, please go ahead and we will revisit it
later once it has had some time in unstable.

Thanks,
~Niels

Bug#863909: linux/a.out.h: should use #ifdef __linux__ not #ifdef linux, etc

[Ben Hutchings]

Control: severity -1 wishlist

On Thu, 2017-06-01 at 16:37 -0400, Zack Weinberg wrote:
> Package: linux-libc-dev
> Version: 4.11-1~exp2
> Severity: normal
> File: /usr/include/linux/a.out.h
> Tags: upstream, patch
> 
> linux/a.out.h contains a number of uses of "deprecated
> system-specific predefined macros" that will not be defined
> when the compiler is used in a strict conformance mode, see
> https://gcc.gnu.org/onlinedocs/gcc-6.3.0/cpp/System-specific-Predefined-Macros.html
> for details.
> 
> This would only be a minor problem, except that it causes the GCC build
> process to copy the header, "fix" it, and install the "fixed" copy in a
> private directory that is searched before /usr/include.  It is desirable
> for GCC not to do this to any headers, because it means updates to the
> original are silently ignored until the GCC package is itself updated.

The a.out format is obsolete and was replaced by ELF even before Debian
made its first release.  This header is unlikely to be updated upstream
in any interesting way.

> Please apply the attached patch.  It would be best if it were installed
> to all actively maintained Debian kernels.  I will submit it upstream.

I see no urgency in fixing this.  Downgrading it accordingly.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
 - Carolyn
Scheppner



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

Bug#864064: CVE-2017-9055 CVE-2017-9054 CVE-2017-9053 CVE-2017-9052

[Moritz Muehlenhoff]

Source: dwarfutils
Severity: important
Tags: security

Please see
https://security-tracker.debian.org/tracker/CVE-2017-9055
https://security-tracker.debian.org/tracker/CVE-2017-9054
https://security-tracker.debian.org/tracker/CVE-2017-9053
https://security-tracker.debian.org/tracker/CVE-2017-9052

Cheers,
Moritz

Bug#792307: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#863974: hplip should not require systemd)

[Christian Mueller]

Hi Brian,

I just realized that my bug report, #792307, got merged with #863974 
which may have the same underlying cause but a different interpretation 
of the results. Yes, just installing the systemd binary won't enable it 
as the active init system but another part of the dependency chain, 
libpam-systemd, already imports some of the systemd patterns (separate 
temp mount points for each user) which, apart from the incredible 
clutter in the list of mounted file systems, breaks my workflows (I need 
a single /tmp for all users).


Debian always maintained that systemd would be optional and I would hope 
for a little more flexibility when it comes to [reasonable] requests to 
allow setting up desktop systems without having systemd bits and pieces 
getting in the way. Just having a version of policykit-1 compiled 
without systemd dependencies would solve all our issues and it's a tiny 
little change in the rules file. We would simply have two alternatives 
for policykit-1, one with and one without systemd. Or dynamic support at 
runtime. If there's anything I can do to help getting this implemented, 
especially the runtime detection, please let me know - I'm more than 
happy to put this together but only if I this is not a lost cause 
because nobody is interested in accepting this as a patch, anyway.


Thanks,
--Christian

On 06/03/2017 09:57 PM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the policykit-1 package:

#792307: policykit-1: There should be a variant of policykit-1 which doesn't 
depend on systemd

It has been closed by Brian Potkin .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Brian Potkin 
 by
replying to this email.

Bug#864048: unblock: marco/1.16.1-1

[Ivo De Decker]

Control: tags -1 moreinfo

Hi,

On Sat, Jun 03, 2017 at 06:23:53PM +0200, Mike Gabriel wrote:
> Please consider unblocking package marco ready for upload.
> 
> From upstream we received a last-minute fix for #828077 (mate-panel:
> Mouse focus problem with stack of applications). The underlying cause has
> been fixed in the MATE window manager aka marco.
> 
> 
> unblock marco/1.16.1-1

We're quite close to the release date, so I suggest you upload it now, and
remove the moreinfo tag from this bug once it's in unstable. I'll take a
closer look at that point.

Cheers,

Ivo

Bug#864063: Icon size is too big in Mate "Run Application" dialog

[Sergey Alyoshin]

Package: amule
Version: 1:2.3.2-1+b2
Priority: wishlist

Please, see attached images.

Bug#864038: Troubleshooting section still refers to /dev/hd* devices

[Holger Wansing]

Control: tags -1 + pending

Adrian Bunk  wrote:
> Package: src:installation-guide
> Version: 20170525
> Severity: minor
> 
> 5.4.1.2. How to investigate and maybe solve issues
> 
>   Check that there is a device node for your CD-ROM drive under /dev/. In the 
> example above, this would be /dev/hdc. There should also be a /dev/cdrom.
> 
> This section should be updated to current reality.

Fixed in svn.
Thanks


Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#852275: hexchat: CVE-2016-2087

[Moritz Muehlenhoff]

On Mon, Jan 23, 2017 at 06:31:18AM +0100, Salvatore Bonaccorso wrote:
> Source: hexchat
> Version: 2.10.1-1
> Severity: important
> Tags: security
> 
> Hi,
> 
> the following vulnerability was published for hexchat. Opening a bug
> to have a BTS reference.
> 
> CVE-2016-2087[0]:
> | Directory traversal vulnerability in the client in HexChat 2.11.0
> | allows remote IRC servers to read or modify arbitrary files via a ..
> | (dot dot) in the server name.
> 
> As noted by Mattia Rizzolo already, the fixing commit is reverted in
> the Debian packaging due to regression for some usecases, and waiting
> for a better fix.

What's the status? Is there now a proper fix?

Cheers,
Moritz

Bug#855911: linux-image-4.9.0-1-armmp: MMC failure on A20-OLinuXIno-LIME2

[Thibaut Girka]

I keep experiencing this issue even with a brand new board (same model, newer
hw revision) and on linux-image-4.10.0-rc6-armmp.

I have been informed that this issue might have been fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers?id=2154d94b40ea2a5de05245521371d0461bb0d669

This change was not present in 4.10-0-rc6, and I will now try with
linux-image-4.11.0-trunk, which does include this patch.

Bug#864051: unblock: mate-terminal/1.16.3-1

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Sa 03 Jun 2017 19:19:00 CEST, Niels Thykier wrote:


Control: tags -1 confirmed moreinfo

Mike Gabriel:

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

Please consider unblocking package mate-terminal ready for upload.

It was discovered that a double click on the right mouse button inside a
mate terminal can freeze input on the complete X.org server.

The planned upload of mate-terminal 1.16.3-1 fixes this. This new
upstream release is esp. targeted for Debian 9, no other issue has been
solved since 1.16.2-1.

unblock mate-terminal/1.16.3-1

[...]



Ack, please go ahead.

~Niels


Uploaded and landed now.

Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpdn0stIGZSP.pgp
Description: Digitale PGP-Signatur

Bug#839894: Last chance for d-i changes in stretch

[Cyril Brulebois]

Cyril Brulebois  (2017-06-03):
> This looks good to me, I've uploaded it to unstable, and added a note on
> my d-i checklist to make sure I don't forget about it before the next
> release.

Except this doesn't work except for your JBOD use case…

Adding [a-z]* at the end of the pattern means we *need* an extra letter
(as opposed to regex syntax which means an extra letter would have been
optional). I'll switch this to restoring the earlier pattern and adding
the same with an extra letter as a second pattern, and double check the
results.

Sorry for not catching this sooner.


KiBi.


signature.asc
Description: Digital signature

Bug#863796: unblock: e2guardian/3.4.0.3-2

[Mike Gabriel]

HI Ivo,

On  Sa 03 Jun 2017 22:37:14 CEST, Ivo De Decker wrote:


Control: tags -1 moreinfo

Hi,

On Wed, May 31, 2017 at 11:58:16AM +0200, Mike Gabriel wrote:

Please consider unblocking not-yet-uploaded package e2guardian

Quite recently Google Chrome changed its policy regarding certificate
requirements. Certs without a subjectAltName field get now rejected.

In the e2guardian content filter system, there is support for filtering
SSL encrypted http traffic by decrypting, checking its content and then
re-encrypting SSL-encrypted content. Whereas some consider this as a
m-i-t-m attack, in some setups this makes good sense (e.g. in school
networks).

For re-encrypting the content, a self-signed set of certs gets used.
In previous versions, these certs lack the SAN field. With a patch
from upstream (that they backported to the 3.4 branch of e2guardian esp.
for Debian 9), this issue has now been fixed.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862855 for details.

unblock e2guardian/3.4.0.3-2


We're quite close to the release date, so I suggest you upload it now, and
remove the moreinfo tag from this bug once it's in unstable. I'll take a
closer look at that point.

Cheers,

Ivo


I just dput the package. Thanks so far, hope you find it worthy to  
migrate to stretch.


Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpNMwyWoYGgb.pgp
Description: Digitale PGP-Signatur

Bug#863796: unblock: e2guardian/3.4.0.3-2

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Sa 03 Jun 2017 22:37:14 CEST, Ivo De Decker wrote:


Control: tags -1 moreinfo

Hi,

On Wed, May 31, 2017 at 11:58:16AM +0200, Mike Gabriel wrote:

Please consider unblocking not-yet-uploaded package e2guardian

Quite recently Google Chrome changed its policy regarding certificate
requirements. Certs without a subjectAltName field get now rejected.

In the e2guardian content filter system, there is support for filtering
SSL encrypted http traffic by decrypting, checking its content and then
re-encrypting SSL-encrypted content. Whereas some consider this as a
m-i-t-m attack, in some setups this makes good sense (e.g. in school
networks).

For re-encrypting the content, a self-signed set of certs gets used.
In previous versions, these certs lack the SAN field. With a patch
from upstream (that they backported to the 3.4 branch of e2guardian esp.
for Debian 9), this issue has now been fixed.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862855 for details.

unblock e2guardian/3.4.0.3-2


We're quite close to the release date, so I suggest you upload it now, and
remove the moreinfo tag from this bug once it's in unstable. I'll take a
closer look at that point.

Cheers,

Ivo


+ removing the moreinfo tag now...

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgprF6Qjtnl_5.pgp
Description: Digitale PGP-Signatur

Bug#863838: unblock: debian-edu-install/1.926

[Ivo De Decker]

Control: tags -1 confirmed moreinfo d-i

Hi,

On Thu, Jun 01, 2017 at 10:48:21AM +, Holger Levsen wrote:
> On Thu, Jun 01, 2017 at 04:09:35AM +0200, Cyril Brulebois wrote:
> > I'm not sure why we're still having this hardcoded list of versions.
> 
> because: cruft in the way Debian Edu CDs are build/used…

Unblocked.

It still needs the d-i ack for the unblock-udeb.

Cheers,

Ivo

Bug#864062: python3-socketio-client: Incomplete handling of websocket closing

[Celelibi]

Package: python3-socketio-client
Version: 0.6.5-0.1
Severity: normal

Dear Maintainer,

When the websocket transport protocol receive a "CLOSE" opcode, then
WebSocket.recv return an empty string. That makes socketIO_client crash
later when WebSocketTransport.recv_packet calls parse_packet_text on an
empty string.

I am not sure whether empty strings should be ignored on the
socketIO_client side or if the WebSocket side should be more informative
about the connection closing. In any case, the current state doesn't
perform very well on that matter.


Best regards,
Celelibi

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages python3-socketio-client depends on:
ii  python3-requests   2.12.4-1
ii  python3-six1.10.0-3
ii  python3-websocket  0.37.0-2

python3-socketio-client recommends no packages.

python3-socketio-client suggests no packages.

-- no debconf information

Bug#864061: apt-mirror: Ignores return values of "close" on write handles

[Niels Thykier]

Package: apt-mirror
Severity: normal

Hi,

I noticed that apt-mirror ignores the return value of "close" on write
handles.  This means that the program will happy ignore "out of disk
space" issues (etc.) in some cases and continue without warning
despite having written incomplete or corrupt files.

Example:

"""
open FILES_ALL, ">" . get_variable("var_path") . "/ALL" or die("apt-mirror: 
can't write to intermediate file (ALL)");
open FILES_NEW, ">" . get_variable("var_path") . "/NEW" or die("apt-mirror: 
can't write to intermediate file (NEW)");
open FILES_MD5, ">" . get_variable("var_path") . "/MD5" or die("apt-mirror: 
can't write to intermediate file (MD5)");
open FILES_SHA1, ">" . get_variable("var_path") . "/SHA1" or die("apt-mirror: 
can't write to intermediate file (SHA1)");
open FILES_SHA256, ">" . get_variable("var_path") . "/SHA256" or 
die("apt-mirror: can't write to intermediate file (SHA256)");

[...]

close FILES_ALL;
close FILES_NEW;
close FILES_MD5;
close FILES_SHA1;
close FILES_SHA256;

"""



Thanks,
~Niels

Bug#863792: unblock: mate-desktop/1.16.2-1

[Mike Gabriel]

On  Sa 03 Jun 2017 10:33:00 CEST, Niels Thykier wrote:


Control: tags -1 confirmed moreinfo

Mike Gabriel:

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

Please consider unblocking of not-yet-uploaded package mate-desktop

This version will fix observed problems with solid background colors
currently existing in Debian 9's MATE desktop.

This unblock is needed for getting last minute caja/1.16.6-1 fixes in.
See: https://bugs.debian.org/863791 for further details.

unblock mate-desktop/1.16.2-1

[...]



Please go ahead.

~Niels


This one has been superseded by #864049 (mate-desktop/1.16.2-2) and  
can be closed, too.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpFNd28P4esK.pgp
Description: Digitale PGP-Signatur

Bug#639115: Memory leakes fixed in v3.1

[Joachim Nilsson]

Hi,

unfortunately the memory leak fixes never made it into the v3.0
release, but v3.1 has them.  (I've just released v3.2.)

All the best
 /Joachim

Bug#863796: unblock: e2guardian/3.4.0.3-2

[Ivo De Decker]

Control: tags -1 moreinfo

Hi,

On Wed, May 31, 2017 at 11:58:16AM +0200, Mike Gabriel wrote:
> Please consider unblocking not-yet-uploaded package e2guardian
> 
> Quite recently Google Chrome changed its policy regarding certificate
> requirements. Certs without a subjectAltName field get now rejected.
> 
> In the e2guardian content filter system, there is support for filtering
> SSL encrypted http traffic by decrypting, checking its content and then
> re-encrypting SSL-encrypted content. Whereas some consider this as a
> m-i-t-m attack, in some setups this makes good sense (e.g. in school
> networks).
> 
> For re-encrypting the content, a self-signed set of certs gets used.
> In previous versions, these certs lack the SAN field. With a patch
> from upstream (that they backported to the 3.4 branch of e2guardian esp.
> for Debian 9), this issue has now been fixed.
> 
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862855 for details.
> 
> unblock e2guardian/3.4.0.3-2

We're quite close to the release date, so I suggest you upload it now, and
remove the moreinfo tag from this bug once it's in unstable. I'll take a
closer look at that point.

Cheers,

Ivo

Bug#863890: postrm fails on jessie to stretch upgrade

[Andreas Hoenen]

Steinar H. Gunderson  wrote:

Hi release managers,

in order to fix an error that has happened on a number of systems when
dist-upgrading from jessie to stretch, I need to make a small change to
the postrm script of jessie dblatex: the call of the texlive command
"mktexlsr" must only happen if the command actually is available.

To be on the safe side, the same change needs to be applied to the
postinst script of stretch dblatex.  And in order to avoid this problem
when dist-upgrading from stretch to buster, the jessie postrm change
needs to be taken over to stretch dblatex.

However the jessie fix will avoid the observed error only if installed
*before* dist-upgrading to stretch. How to inform the dist-upgrading
users about this requirement?

> On Sat, Jun 03, 2017 at 07:27:10PM +0200, Andreas Hoenen wrote:
> > Or is it something that the users are told in the release notes?
> > The only requirement I'm able to find there is upgrading to the latest
> > stable point release [1].  Are there plans for a final jessie point
> > release?
>
> You'd have to ask the release managers for this.

Thus the question adressed to you: Are there plans for a final jessie
point release?  If this point release would include a new, fixed dblatex
jessie version 0.3.5-3, users would install it as part of the
recommended dist-upgrade preparation.

Your advice about how to proceed is appreciated.

Regards, Andreas
-- 
Andreas Hoenen 
GPG: 1024D/B888D2CE
 A4A6 E8B5 593A E89B 496B
 82F0 728D 8B7E B888 D2CE


signature.asc
Description: PGP signature

Bug#862295: unblock: v4l-utils/1.12.5-1

[Niels Thykier]

Niels Thykier:
> Control: tags -1 moreinfo
> 
> Gregor Jasny:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: unblock
>>
>> Please unblock package v4l-utils
>>
>> Hello,
>>
>> please unblock the latest stable version of v4l-utils 1.12. It fixes
>> a crash in the Digital Video Broadcasting (DVB) library that occurs
>> when a German DVB-T2 transport stream is parsed. Additionally it fixes
>> a bug where identical transport streams were not detected as such.
>>
>> Thanks,
>> Gregor
>>
>> [...]
> 
> Please clarify the possible ABI breakage situation and resolve the above
> issues.
> 
> Thanks,
> ~Niels
> 

Hi Gregor,

We haven't heard back from you in a while.

Unfortunately, the release is now just around the corner and this
changeset is a bit more than what we are happy with just up to the
upload deadline.

Thanks,
~Niels

Bug#864043: release-notes: proofreading sweep - moreinfo.dbk

[Justin B Rye]

Javier Fernandez-Sanguino wrote:
> Dear Justin,
> 
> Thank you for this review. Although I can agree to many of these changes, I do
> not think it is wise to make them so close to the release date, when
> translation teams have updated (or are in the process of updating) the
> translations in preparation of the Release.

The only way to avoid this situation would be for somebody to make an
announcement that translation work will need to start on such-and-such
a date, leaving enough time for finalising the English text *before*
that starts.  Do you think we can try that approach for Buster?

So far I've been dealing with the pages that don't change much from
release to release, suggesting changes that aren't particularly
urgent, but the pages I'm planning to get round to in the next couple
of days still contain factual inaccuracies that need fixing.

Meanwhile, my test upgrades so far (multiple trials on two different
machines) have consistently run into a couple of nasty undocumented
glitches - the upgrade disables my network connection (a restart of
networking.service that errors out), and the new version of X doesn't
respond to input devices until I install xserver-xorg-input-libinput.
I was hoping to find some mention of these issues in pending bug
reports, but it doesn't look like it.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

Bug#863868: USB Memory Stick: Issues with win32diskimager

[Steve McIntyre]

On Fri, Jun 02, 2017 at 06:45:33AM +0200, Cyril Brulebois wrote:
>Hi,
>
>and thanks for your report.
>
>Varanka Risto  (2017-06-01):
>> Package: installation-guide
>> Severity: important
>> Tags: security
>> 
>> The online installation guide for Debian Stable at
>> https://www.debian.org/releases/stable/i386/ch04s03.html.en recommends
>> the use of the win32diskimager utility for writing images to USB in
>> section "4.3.1. Preparing a USB stick using a hybrid CD or DVD image".
>> This software currently has issues, might compromise the security of
>> Debian users and probably should not be recommended by Debian:
>> 
>> 1) User comments on the main page
>> https://sourceforge.net/projects/win32diskimager/ report that the
>> current version 1.0.0 contains malware, or tries to install crapware
>> as part of the installation process. (If possible this should be
>> investigated and if indeed the project is compromised, Debian users
>> should be notified.)
>
>ISTR sf.net tends to do that for Windows binaries, and this might not be
>specific to win32diskimager.
>
>> 2) Some user comments also state the tool does not work on Windows 10
>> while others claim it does. I installed this on a Windows 10 system
>> and the software turned out not to function properly, indicating that
>> 1) might also be the case, and of course majorly impacting Debian
>> installation experience. Details below.
>> 
>> Navigate to Files->Archive and click on
>> win32diskimager-1.0.0-install.exe. On the following page download
>> starts automatically. Install the tool, run it and provide
>> administrator credentials. Try to select the file to write: the opened
>> file browser does not display almost any directories, and when an .img
>> file is copied to the directories available, it does not show up in
>> the file browser.
>> 
>> I suggest to replace the recommended tool for the time being and to
>> investigate the trustworthiness of the utility.
>
>Any recommendations for alternative software?

My own recommendation now would be Rufus, in dd mode.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Bug#864060: minetest: Please package the new upstream version 0.4.16

[Markus Koschany]

Am 03.06.2017 um 22:08 schrieb Martin Quinson:
> Package: minetest
> Version: 0.4.15+repack2-1
> Severity: normal
> 
> Hello people,
> 
> The new version of minetest was released today. I think we should package it 
> as
> soon as the current freeze period is over. I'm filling this bug to not forget
> about it.

Hey Martin,

I volunteer to package the new version because I'm about to start a new
Minetest world on my private server and some players asked me to do
that. I probably can do that in the course of the upcoming week.

However feel free to fix the next bug / package the next version. :)

Cheers,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#863945: fpm2: doubleclick to tray icon for main window popup

[Dr. Tobias Quathamer]

Am 02.06.2017 um 23:22 schrieb serge:

Hello.
Why?
I like fpm2)
  And pass is cli, keepassx is qt, keepass2 is mono.
I need fast gtk2 password manager for my old laptop with Xfce.
Can you pls fix this small bug or explain how to fix it in sources.
thnx


Hi serge,

I don't have the time and motivation to maintain a program that has been 
abandoned upstream already a couple of years ago.


If you like this program and want to keep using it, you're more than 
welcome to take over the upstream maintenance. You can easily get the 
source and start hacking on it.


Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#864060: minetest: Please package the new upstream version 0.4.16

[Martin Quinson]

Package: minetest
Version: 0.4.15+repack2-1
Severity: normal

Hello people,

The new version of minetest was released today. I think we should package it as
soon as the current freeze period is over. I'm filling this bug to not forget
about it.


Thanks, Mt.



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

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

Versions of packages minetest depends on:
ii  libc62.24-10
ii  libcurl3-gnutls  7.52.1-5
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-16
ii  libirrlicht1.8   1.8.4+dfsg1-1
ii  libjsoncpp1  1.7.4-3
ii  libleveldb1v51.18-5
ii  libluajit-5.1-2  2.0.4+dfsg-1+b1
ii  libopenal1   1:1.17.2-4+b2
ii  libsqlite3-0 3.16.2-3
ii  libstdc++6   6.3.0-16
ii  libvorbisfile3   1.3.5-4
ii  libx11-6 2:1.6.4-3
ii  minetest-data0.4.15+repack2-1
ii  zlib1g   1:1.2.8.dfsg-5

minetest recommends no packages.

Versions of packages minetest suggests:
pn  minetest-mod-moreblocks  
pn  minetest-mod-moreores
pn  minetest-mod-pipeworks   
pn  minetest-server  

-- no debconf information

-- 
Il n'y a pas de recherche appliquée, mais des applications de la recherche.
  -- Louis Pasteur


signature.asc
Description: PGP signature

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

[Guilhem Moulin]

On Sat, 03 Jun 2017 at 11:24:07 -0400, Felipe Sateler wrote:
> On Sat, Jun 3, 2017 at 4:31 AM, Guilhem Moulin  wrote:
>> On Mon, 29 May 2017 at 14:42:33 +0200, Michael Biebl wrote:
> This is an ugly fix.

Yes, but we're really far in the release cycle and as a cryptsetup
maintainer I want to try to limit the impact to users of packages I
maintain (even though as I clearly said this issue isn't a cryptsetup
one)…

> The correct one would be to have the udev initscript do the same the
> systemd units do: remove the socket on stop:

Thanks for the patch.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#863927: qtwebengine-opensource-src: FTBFS: memory exhausted

[Sandro Knauß]

Hey,

> No, the fix would be to not produce 1 GB of debug info for this library:

> The build log [1] confirms that -g is used in the i386 build.
> 
> -g0 instead of -g (or no -g option) would surely solve this problem.
> 
> -g1 would likely be sufficient to fix the problem on i386,
> while still providing enough debug information for backtraces.
> 
> A similar -g0/-g1 fix could also fix the armhf and mipsel builds (untested).

interessting point and a year ago I also ask for ideas and nothing came. I 
tested a lot to get it building on other platforms without success. At the 
moment I'm hardy using my computer, so I can't test it at the moment, sorry.

Best Regards,

sandro

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

Bug#862400: several bios updates exist since 2007

[Ivo De Decker]

Hi,

On Fri, May 19, 2017 at 01:58:31PM +0200, Arturo Borrero Gonzalez wrote:
> We managed to upgrade the BIOS (not the last one, though).
> 
> Still no luck, kernel 4.9 doesn't boot while 4.7 does.

Does it work with 4.11 (available in experimental)?

Cheers,

Ivo

Bug#864043: release-notes: proofreading sweep - moreinfo.dbk

[Javier Fernandez-Sanguino]

Dear Justin,

Thank you for this review. Although I can agree to many of these changes, I
do not think it is wise to make them so close to the release date, when
translation teams have updated (or are in the process of updating) the
translations in preparation of the Release.

Release Notes should be string frozen at some point, they should not be a
loving target. These type of stylistic changes ("" to "Debian"")
should in my opinion, be done post-release.

At the very least, translation teams should be informed (specially those
currently close to or at 100% [1]). So they are aware and have time to
do/plan a last review/update before $RELEASE.


Saludos

Javier

[1] https://www.debian.org/releases/testing/statistics.html
There are currently 9 (out of 19) translations which are over 90%)

Bug#863788: oolite: Please drop dependency against mozjs 1.8.5

[Nicolas Boulenguez]

Package: src:oolite
Followup-For: Bug #863788

Hello.

Upstream relies on a very old copy of the Mozilla javascript
interpreter (libmozjs/spidermonkey), downloaded during the build from
a private URL, without electronic signature.

This hack protects most users from the (frequent) API changes, but
does not fit Debian maintenance standards.  So I have migrated the
package to libmozjs-dev, then libmozjs185-dev.

libmozs-24-dev, or the more recent firefox-dev (= 52) use many C++
features. The .h files are incompatible with C, thus with Objective-C.

I am reluctant to invest the huge required efforts, while the only
sensible solution seems to me that upstream switch to a library giving
a bit of consideration to API consistence and stability. A quick
search gives two candidates, libjavascriptcoregtk and
plasma-scriptengine-javascript, both probably available in all major
systems like GTK and KDE.

I will probably have to remove Oolite from Debian after the freeze.

@Chris: I am CCing you because as far as I know you are the upstream
contact for Oolite on Linux systems. If you bring the discussion to
some Oolite public place, please inform me so that I can add a link to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863788.

Bug#313303: Should this bug be closed?

[Richard Owlett]

I have verified this bug does not appear in Debian Testing which has 
Tomboy 1.14.1 .


Upstream  reports 
it as not seen in Linux as of Feb 2013.

Bug#863791: unblock: caja/1.16.6-1

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Sa 03 Jun 2017 10:32:00 CEST, Niels Thykier wrote:


Control: tags -1 confirmed moreinfo

Mike Gabriel:

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

Please consider unblocking not-yet-uploaded package caja

Currently, it is not possible to modify the background image in MATE
desktop sessions running on Debian stretch. Also, there are various issues
open for caja on Debian BTS, that this version of caja could resolve.
[...]


Hi,

Thanks for bringing this up.  Honestly, I wish we had caught this a lot
earlier, but it is definitely better to catch it before the release than
after.

Please go ahead.

~Niels


Uploaded.

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpLhIpTKopTV.pgp
Description: Digitale PGP-Signatur

Bug#864059: unblock: seqan2/2.3.1+dfsg-4

[Andreas Tille]

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

Please unblock package seqan2

The last NMU introduced a bug that is fixed by a very simple patch.

Kind regards and thanks for your work as release team

 Andreas.

unblock seqan2/2.3.1+dfsg-4

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru seqan2-2.3.1+dfsg/debian/changelog seqan2-2.3.1+dfsg/debian/changelog
--- seqan2-2.3.1+dfsg/debian/changelog	2017-05-29 23:56:39.0 +0200
+++ seqan2-2.3.1+dfsg/debian/changelog	2017-06-03 16:15:29.0 +0200
@@ -1,3 +1,11 @@
+seqan2 (2.3.1+dfsg-4) unstable; urgency=medium
+
+  * Fix FTBFS when built with dpkg-buildpackage -A (thanks for the patch to
+Santiago Vila )
+Closes: #864026
+
+ -- Andreas Tille   Sat, 03 Jun 2017 16:15:29 +0200
+
 seqan2 (2.3.1+dfsg-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru seqan2-2.3.1+dfsg/debian/rules seqan2-2.3.1+dfsg/debian/rules
--- seqan2-2.3.1+dfsg/debian/rules	2017-05-29 23:56:39.0 +0200
+++ seqan2-2.3.1+dfsg/debian/rules	2017-06-03 16:15:29.0 +0200
@@ -96,7 +96,7 @@
 	# we generate only those manpages where binaries are linked to /usr/bin
 	dh_installman
 
-override_dh_link:
+override_dh_link-arch:
 	dh_link
 	# Some binaries (eg. splazer) are not built in 32-bit architectures so
 	# remove their (broken) symlinks.

Bug#847021: oolite: please make the build reproducible (locale)

[Nicolas Boulenguez]

Package: src:oolite
Followup-For: Bug #847021

Hello.
Thanks for your patch.
It is committed into the version control system, waiting for next upload.

Bug#844639: oolite: please switch to espeak-ng

[Nicolas Boulenguez]

Package: src:oolite
Followup-For: Bug #844639

Committed into the VCS, waiting for next upload.

Bug#864058: New wireshark issues

[Moritz Muehlenhoff]

Source: wireshark
Severity: important
Tags: security

Please see
https://www.wireshark.org/security/wnpa-sec-2017-22.html
https://www.wireshark.org/security/wnpa-sec-2017-23.html
https://www.wireshark.org/security/wnpa-sec-2017-24.html
https://www.wireshark.org/security/wnpa-sec-2017-25.html
https://www.wireshark.org/security/wnpa-sec-2017-26.html
https://www.wireshark.org/security/wnpa-sec-2017-27.html
https://www.wireshark.org/security/wnpa-sec-2017-28.html
https://www.wireshark.org/security/wnpa-sec-2017-29.html
https://www.wireshark.org/security/wnpa-sec-2017-30.html
https://www.wireshark.org/security/wnpa-sec-2017-31.html
https://www.wireshark.org/security/wnpa-sec-2017-32.html
https://www.wireshark.org/security/wnpa-sec-2017-33.html

Cheers,
Moritz

Bug#864057: new upstream (2.85.1)

[Daniel Baumann]

Package: calibre
Severity: wishlist

Hi,

it would be nice if you could upgrade to the current upstream version
(2.85.1) in experimental.

Regards,
Daniel

Bug#863890: postrm fails on jessie to stretch upgrade

[Steinar H. Gunderson]

On Sat, Jun 03, 2017 at 07:27:10PM +0200, Andreas Hoenen wrote:
> Changing this in stretch dblatex is easy (with a new version 0.3.9-3),
> but I'm not sure how a corresponding change in jessie dblatex (with a
> new version 0.3.5-3) would reach the jessie installations out there: is
> there any mechanism that upgrades jessie installations to the most
> recent jessie packages first before upgrading to stretch in a second
> step?

There's no mechanism for forcing upgrades through a middle version, no.
You can write something in the release notes asking to upgrade certain
packages before others, though.

> Or is it something that the users are told in the release notes?
> The only requirement I'm able to find there is upgrading to the latest
> stable point release [1].  Are there plans for a final jessie point
> release?

You'd have to ask the release managers for this.

> Another question: after releasing new dblatex jessie version 0.3.5-3, I
> need to incorporate the new jessie changelog entry into the changelog of
> the new dblatex stretch version 0.3.9-3, don't I?  Although this will
> add to the differences between 0.3.9-2 and 0.3.9-3, which the release
> managers request to keep as minimal as possible.

No, you don't need to do this. Packages can diverge, and the BTS understands
it.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

[Michael Biebl]

Am 03.06.2017 um 17:24 schrieb Felipe Sateler:

> diff --git a/debian/udev.init b/debian/udev.init
> index ffef3ea6a..dcc5c29d5 100644
> --- a/debian/udev.init
> +++ b/debian/udev.init
> @@ -208,6 +208,7 @@ case "$1" in
>  stop)
>  log_daemon_msg "Stopping $DESC" "$NAME"
>  if start-stop-daemon --stop --name $NAME --user root --quiet --oknodo 
> --retry 5; then
> + rm -f /run/udev/control

I think this is the correct fix, yes.

We need to keep in mind though, that udev currently does not install any
stop (K) symlinks in runlevel 0 and 6, but we rely on the killing spree
in sendsigs to kill the udev process on shutdown.

Which means, we'd need to start installing those K symlinks in 0 6.
For that, edit /etc/init.d/udev, add
# Default-Stop: 0 6
to the LSB header, then run

# rm /etc/rcS.d/???udev
# update-rc.d udev defaults





signature.asc
Description: OpenPGP digital signature

Bug#863118: devscripts needs proper configuration file parsing

[James McCoy]

On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote:
> OK, here is my try to do the following.  Ugly, yes.  But it seems to
> catch most errors in friendly way.
> 
>  * "egrep" test to catch space after "="
>  * "set -e" to detect command not found; 
>* space before "="
>* "false" in line
>  * "bash -n" test
>  * Report the file name if a bug is found as much.
> 
> If no objection, I will apply this patch to git.  

The concept looks like a step in the right direction.  However, uscan.pl
isn't the only script that does this type of config parsing.

Also, I would wait until after Stretch is released.

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

Bug#864056: RFS: icoutils/0.31.2-1.1 [NMU]

[James Lu]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for package "icoutils"

 * Package name: icoutils
   Version : 0.31.2-1.1
   Upstream Author : Frank Richter 
 * URL : http://www.nongnu.org/icoutils/
 * License : GPL-3+
   Section : graphics

It builds those binary packages:

  icoutils   - Create and extract MS Windows icons and cursors

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/i/icoutils/icoutils_0.31.2-1.1.dsc

Changes since the last upload:

icoutils (0.31.2-1.1) unstable; urgency=high

  * Non-maintainer upload.
  * Add patch fix-wrestool.patch from upstream commit
http://git.savannah.nongnu.org/cgit/icoutils.git/commit/?id=3c990fcc754c81a02ab5981d59b01025f1596b2c
to fix wrestool not extracting icons - this is a regression from 0.31.2.
Closes: #860220


I want to upload this low threshold NMU[1] because the bug being fixed
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860220) breaks
icoutils' wrestool entirely, and prevents gnome-exe-thumbnailer (which I
maintain) and likely others[2] from properly working. Per the regular
NMU guidelines[3], I've also waited 5 days before pushing a fix for this
severity 'important' bug. Although the stretch upload deadline is coming
up soon, I really want to fix this bug for stretch so that programs
depending on wrestool are fully functional.

[1]: https://wiki.debian.org/LowThresholdNmu
[2]: https://codesearch.debian.net/search?q=wrestool
[3]:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines

Regards,
James Lu



signature.asc
Description: OpenPGP digital signature

Bug#864055: bootstrap-vz: Should generate ed25519 host keys, should not generate dsa host keys

[Santiago Vila]

Package: bootstrap-vz
Version: 0.9.10+20170110git-1
Tags: patch

Dear maintainer:

The host keys generated by default on new systems by openssh-server
are rsa, ecdsa and ed25519.

Since this package will be used to generate images for Debian 9,
it should ideally generate the same set of keys.

I discovered this after upgrading a GCE machine to stretch
and modifying sshd_server to be closer to the Debian 9 default.
What happened is that even if I removed the DSA keys, they were
generated again. Thanks to codesearch.debian.net it was easy
to check where this came from.

Trivial patch follows.

[ If possible, please consider a freeze exception for this ]

Thanks.

--- a/bootstrapvz/common/assets/init.d/generate-ssh-hostkeys
+++ b/bootstrapvz/common/assets/init.d/generate-ssh-hostkeys
@@ -14,23 +14,23 @@ prog=$(basename $0)
 logger="logger -t $prog"
 
 rsa_key="/etc/ssh/ssh_host_rsa_key"
-dsa_key="/etc/ssh/ssh_host_dsa_key"
+ed25519_key="/etc/ssh/ssh_host_ed25519_key"
 ecdsa_key="/etc/ssh/ssh_host_ecdsa_key"
 
 # Exit if the hostkeys already exist
-if [ -f $rsa_key -a -f $dsa_key -a -f $ecdsa_key ]; then
+if [ -f $rsa_key -a -f $ed25519_key -a -f $ecdsa_key ]; then
exit
 fi
 
 # Generate the ssh host keys
 [ -f $rsa_key ] || ssh-keygen -f $rsa_key -t rsa -C 'host' -N ''
-[ -f $dsa_key ] || ssh-keygen -f $dsa_key -t dsa -C 'host' -N ''
+[ -f $ed25519_key ] || ssh-keygen -f $ed25519_key -t dsa -C 'host' -N ''
 [ -f $ecdsa_key ] || ssh-keygen -f $ecdsa_key -t ecdsa -C 'host' -N ''
 
 # Output the public keys to the console
 # This allows user to get host keys securely through console log
 echo "-BEGIN SSH HOST KEY FINGERPRINTS-" | $logger
 ssh-keygen -l -f $rsa_key.pub | $logger
-ssh-keygen -l -f $dsa_key.pub | $logger
+ssh-keygen -l -f $ed25519_key.pub | $logger
 ssh-keygen -l -f $ecdsa_key.pub | $logger
 echo "--END SSH HOST KEY FINGERPRINTS--" | $logger

Bug#863890: postrm fails on jessie to stretch upgrade

[Andreas Hoenen]

Steinar H. Gunderson  wrote:

> Package: dblatex
> Version: 0.3.5-2
> Severity: serious
>
> Hi,
>
> When dist-upgrading from jessie to stretch, I've seen this happen on a number
> of systems:
>
> Removing dblatex (0.3.5-2) ...
> /var/lib/dpkg/info/dblatex.postrm: 44: /var/lib/dpkg/info/dblatex.postrm: 
> mktexlsr: not found
> dpkg: error processing package dblatex (--remove):
>  subprocess installed post-removal script returned error exit status 127
> Removing texlive-math-extra (2014.20141024-1) ...
> Processing triggers for man-db (2.7.0.2-5) ...
> Errors were encountered while processing:
>  dblatex
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> This breaks the upgrade. It might be that we need a fix in jessie,
> but I don't honestly know the best fix, as it seems to be about
> removing the old package, not installing the new one. I've included a full

Hi,

mktexlsr needs to be called in dblatex postrm/postinst, as documented
there:

# A call to 'mktexlsr' is needed to register the dblatex TeX files
# in the TeX database '/var/lib/texmf/ls-R-TEXMFMAIN'.

Unfortunately in this special case the texlive packages (providing
mktexlsr) are not present when calling dblatex postrm:

> Versions of packages dblatex depends on:
> ii  docbook-xml   4.5-8
> ii  python2.7.13-2
> ii  python-apt1.4.0~beta3
> pn  texlive   
> pn  texlive-bibtex-extra  
> pn  texlive-extra-utils   
> pn  texlive-latex-extra   
> pn  texlive-math-extra
> ii  xsltproc  1.1.29-2.1

A possible solution would be to check for the availability of mktexlsr
in dblatex postrm/postinst and to call it only when found.

Changing this in stretch dblatex is easy (with a new version 0.3.9-3),
but I'm not sure how a corresponding change in jessie dblatex (with a
new version 0.3.5-3) would reach the jessie installations out there: is
there any mechanism that upgrades jessie installations to the most
recent jessie packages first before upgrading to stretch in a second
step?  Or is it something that the users are told in the release notes?
The only requirement I'm able to find there is upgrading to the latest
stable point release [1].  Are there plans for a final jessie point
release?

Another question: after releasing new dblatex jessie version 0.3.5-3, I
need to incorporate the new jessie changelog entry into the changelog of
the new dblatex stretch version 0.3.9-3, don't I?  Although this will
add to the differences between 0.3.9-2 and 0.3.9-3, which the release
managers request to keep as minimal as possible.

BTW, as usual I would need sponsorship for the two new releases as I
have no upload rights.

Any advice is highly appreciated.

[1] 
https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#system-status

Regards, Andreas
-- 
Andreas Hoenen 
GPG: 1024D/B888D2CE
 A4A6 E8B5 593A E89B 496B
 82F0 728D 8B7E B888 D2CE


signature.asc
Description: PGP signature

Bug#864054: RM: calypso/1.5-3

[Guido Günther]

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

Calypso currently has issues with UTF-8 encoding when using "recent"
python-vobject

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

My attempt to fix this upstream went uncommented which is related to the
fact that there wasn't much upstream activity in the last year.

I'd feel better if we'd pull calypso from stretch and rather not offer
any support for it at the moment given that there are other things
pending like strong password hash support.

I intend to push the changes I made and release a new version but given
the current number of users backports is likely good enough and easier
to keep updated.

cc'ing Jemer who also worked on the package in the past.
Cheers,
 -- Guido

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

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

Bug#864053: bootstrapvz: Should generate ed25519 host keys, should not generate dsa host keys

[Santiago Vila]

Package: bootstrapvz
Version: 0.9.10+20170110git-1
Tags: patch

Dear maintainer:

The host keys generated by default on new systems by openssh-server
are rsa, ecdsa and ed25519.

Since this package will be used to generate images for Debian 9,
it should ideally generate the same set of keys.

I discovered this after upgrading a GCE machine to stretch
and modifying sshd_server to be closer to the Debian 9 default.
What happened is that even if I removed the DSA keys, they were
generated again. Thanks to codesearch.debian.net it was easy
to check where this came from.

Trivial patch follows.

[ If possible, please consider a freeze exception for this ]

Thanks.

--- a/bootstrapvz/common/assets/init.d/generate-ssh-hostkeys
+++ b/bootstrapvz/common/assets/init.d/generate-ssh-hostkeys
@@ -14,23 +14,23 @@ prog=$(basename $0)
 logger="logger -t $prog"
 
 rsa_key="/etc/ssh/ssh_host_rsa_key"
-dsa_key="/etc/ssh/ssh_host_dsa_key"
+ed25519_key="/etc/ssh/ssh_host_ed25519_key"
 ecdsa_key="/etc/ssh/ssh_host_ecdsa_key"
 
 # Exit if the hostkeys already exist
-if [ -f $rsa_key -a -f $dsa_key -a -f $ecdsa_key ]; then
+if [ -f $rsa_key -a -f $ed25519_key -a -f $ecdsa_key ]; then
exit
 fi
 
 # Generate the ssh host keys
 [ -f $rsa_key ] || ssh-keygen -f $rsa_key -t rsa -C 'host' -N ''
-[ -f $dsa_key ] || ssh-keygen -f $dsa_key -t dsa -C 'host' -N ''
+[ -f $ed25519_key ] || ssh-keygen -f $ed25519_key -t dsa -C 'host' -N ''
 [ -f $ecdsa_key ] || ssh-keygen -f $ecdsa_key -t ecdsa -C 'host' -N ''
 
 # Output the public keys to the console
 # This allows user to get host keys securely through console log
 echo "-BEGIN SSH HOST KEY FINGERPRINTS-" | $logger
 ssh-keygen -l -f $rsa_key.pub | $logger
-ssh-keygen -l -f $dsa_key.pub | $logger
+ssh-keygen -l -f $ed25519_key.pub | $logger
 ssh-keygen -l -f $ecdsa_key.pub | $logger
 echo "--END SSH HOST KEY FINGERPRINTS--" | $logger

Bug#864051: unblock: mate-terminal/1.16.3-1

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Mike Gabriel:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please consider unblocking package mate-terminal ready for upload.
> 
> It was discovered that a double click on the right mouse button inside a
> mate terminal can freeze input on the complete X.org server.
> 
> The planned upload of mate-terminal 1.16.3-1 fixes this. This new
> upstream release is esp. targeted for Debian 9, no other issue has been
> solved since 1.16.2-1.
> 
> unblock mate-terminal/1.16.3-1
> 
> [...]


Ack, please go ahead.

~Niels

Bug#864052: opencryptoki: Please drop /etc/pkcs11 symlink

[Andreas Metzler]

Source: opencryptoki
Version: 3.6.1+dfsg-1
Severity: normal

Hello,

Could you please drop the /etc/pkcs11 symlink in opencryptoki? Afaik
opencryptoki used to place files in /etc/pkcs11 instead of
/var/lib/opencryptoki _a_ _long_ _time_ _ago_, up to version 2.1. Later
versions suggested to temporarily add a compatibilty symlink to ease
migration. The first version packaged for Debian was after the switch
(2.2.4, in 2007).

Nowadays this causes problems for p11-kit which uses /etc/pkcs11/ as
base configuration directory:

* I have been asked to ship a (empty) /etc/pkcs11/ directory in p11-kit
  which would require a Conflicts with opencryptoki.
* /var/lib/opencryptoki's access permissions are restrictive, therefore
  p11-kit cannot follow the /etc/pkcs11 symlink to check for config
  files.

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

Bug#864050: unblock: eom/1.16.1-1

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Mike Gabriel:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please consider unblocking planned upload of package eom.
> 
> This upload brings a new maintenance release of the eom component of the
> MATE 1.16 release series.
> 
> Other than closing open Debian bug #816914 (Eom auto reload file is
> broken), it brings in some other fixes cherry-picked to the 1.16 branch
> of eom (targetting Debian 9). See debian/changelog for details in
> attached .debdiff.
> 
> unblock eom/1.16.1-1
> 
> [...]

Ack, please go ahead.

~Niels

Bug#864051: unblock: mate-terminal/1.16.3-1

[Mike Gabriel]

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

Please consider unblocking package mate-terminal ready for upload.

It was discovered that a double click on the right mouse button inside a
mate terminal can freeze input on the complete X.org server.

The planned upload of mate-terminal 1.16.3-1 fixes this. This new
upstream release is esp. targeted for Debian 9, no other issue has been
solved since 1.16.2-1.

unblock mate-terminal/1.16.3-1

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mate-terminal-1.16.2/configure.ac mate-terminal-1.16.3/configure.ac
--- mate-terminal-1.16.2/configure.ac   2017-02-06 12:44:53.0 +0100
+++ mate-terminal-1.16.3/configure.ac   2017-05-05 13:03:09.0 +0200
@@ -1,6 +1,6 @@
 m4_define([gt_version_major],[1])
 m4_define([gt_version_minor],[16])
-m4_define([gt_version_micro],[2])
+m4_define([gt_version_micro],[3])
 m4_define([gt_version_extra],[])
 
m4_define([gt_version],[gt_version_major().gt_version_minor().gt_version_micro()gt_version_extra])
 
diff -Nru mate-terminal-1.16.2/debian/changelog 
mate-terminal-1.16.3/debian/changelog
--- mate-terminal-1.16.2/debian/changelog   2017-04-26 21:29:17.0 
+0200
+++ mate-terminal-1.16.3/debian/changelog   2017-06-03 18:29:04.0 
+0200
@@ -1,3 +1,11 @@
+mate-terminal (1.16.3-1) UNRELEASED; urgency=medium
+
+  * New upstream release.
+- Fix freezing Xorg on double click with right mouse button. (Closes:
+  #862035).
+
+ -- Mike Gabriel   Sat, 03 Jun 2017 18:29:04 +0200
+
 mate-terminal (1.16.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mate-terminal-1.16.2/NEWS mate-terminal-1.16.3/NEWS
--- mate-terminal-1.16.2/NEWS   2017-02-06 12:44:53.0 +0100
+++ mate-terminal-1.16.3/NEWS   2017-05-05 13:03:09.0 +0200
@@ -1,3 +1,7 @@
+1.16.3
+
+  * Fix freezing Xorg on double click with right mouse button
+
 1.16.2
 
   * Bring back exit confirmation when there's a process running
diff -Nru mate-terminal-1.16.2/src/terminal-window.c 
mate-terminal-1.16.3/src/terminal-window.c
--- mate-terminal-1.16.2/src/terminal-window.c  2017-02-06 12:44:53.0 
+0100
+++ mate-terminal-1.16.3/src/terminal-window.c  2017-05-05 13:03:09.0 
+0200
@@ -1535,9 +1535,9 @@
 if (info->button == 0)
 gtk_menu_shell_select_first (GTK_MENU_SHELL (popup_menu), FALSE);
 
-if (gtk_menu_get_attach_widget (GTK_MENU (popup_menu)))
-  gtk_menu_detach (GTK_MENU (popup_menu));
-gtk_menu_attach_to_widget (GTK_MENU (popup_menu), GTK_WIDGET (screen), 
NULL);
+if (!gtk_menu_get_attach_widget (GTK_MENU (popup_menu)))
+gtk_menu_attach_to_widget (GTK_MENU (popup_menu),GTK_WIDGET 
(screen),NULL);
+
 gtk_menu_popup (GTK_MENU (popup_menu),
 NULL, NULL,
 NULL, NULL,

Bug#864049: unblock: mate-desktop/1.16.2-2

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Mike Gabriel:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please consider unblocking a minor follow-up fix for package mate-desktop
> 
> The DH call until mate-desktop 1.16.2-1 has been missing the "--with gir"
> option. The proposed next upload of mate-desktop will fix that. A
> .debdiff has been attached.
> 
> unblock mate-desktop/1.16.2-2
> 
> [...]

Please go ahead.

~Niels

Bug#863860: Heĺlo

[Danny Hoult]

Cud i get  a copy of kali for my Android fone please

Bug#864049: unblock: mate-desktop/1.16.2-2

[Mike Gabriel]

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

Please consider unblocking a minor follow-up fix for package mate-desktop

The DH call until mate-desktop 1.16.2-1 has been missing the "--with gir"
option. The proposed next upload of mate-desktop will fix that. A
.debdiff has been attached.

unblock mate-desktop/1.16.2-2

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mate-desktop-1.16.2/debian/changelog 
mate-desktop-1.16.2/debian/changelog
--- mate-desktop-1.16.2/debian/changelog2017-04-28 22:28:53.0 
+0200
+++ mate-desktop-1.16.2/debian/changelog2017-06-03 16:14:34.0 
+0200
@@ -1,3 +1,11 @@
+mate-desktop (1.16.2-2) unstable; urgency=medium
+
+  * debian/rules:
++ Add --with gir to DH options. Fixes missing dependencies in
+  gir1.2-mate-desktop. (Closes: #862172).
+
+ -- Mike Gabriel   Sat, 03 Jun 2017 16:14:34 +0200
+
 mate-desktop (1.16.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mate-desktop-1.16.2/debian/rules mate-desktop-1.16.2/debian/rules
--- mate-desktop-1.16.2/debian/rules2016-09-30 09:46:02.0 +0200
+++ mate-desktop-1.16.2/debian/rules2017-06-03 16:12:32.0 +0200
@@ -7,7 +7,7 @@
 include /usr/share/dpkg/buildflags.mk
 
 %:
-   dh $@ $(DHFLAGS) --with python2
+   dh $@ $(DHFLAGS) --with gir,python2
 
 override_dh_install:
rm -f debian/tmp/usr/lib/*/*.la

Bug#864050: unblock: eom/1.16.1-1

[Mike Gabriel]

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

Please consider unblocking planned upload of package eom.

This upload brings a new maintenance release of the eom component of the
MATE 1.16 release series.

Other than closing open Debian bug #816914 (Eom auto reload file is
broken), it brings in some other fixes cherry-picked to the 1.16 branch
of eom (targetting Debian 9). See debian/changelog for details in
attached .debdiff.

unblock eom/1.16.1-1

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru eom-1.16.0/configure.ac eom-1.16.1/configure.ac
--- eom-1.16.0/configure.ac 2016-09-19 07:48:00.0 +0200
+++ eom-1.16.1/configure.ac 2017-01-26 13:34:31.0 +0100
@@ -3,7 +3,7 @@
 
 m4_define(eom_major_version, 1)
 m4_define(eom_minor_version, 16)
-m4_define(eom_micro_version, 0)
+m4_define(eom_micro_version, 1)
 m4_define(eom_version, eom_major_version.eom_minor_version.eom_micro_version)
 
 AC_INIT([eom], eom_version, [http://www.mate-desktop.org], [eom])
diff -Nru eom-1.16.0/debian/changelog eom-1.16.1/debian/changelog
--- eom-1.16.0/debian/changelog 2017-01-24 21:25:45.0 +0100
+++ eom-1.16.1/debian/changelog 2017-06-03 16:05:48.0 +0200
@@ -1,3 +1,14 @@
+eom (1.16.1-1) unstable; urgency=medium
+
+  * New upstream release.
+- Fix EOM auto reload of externally modified files.
+  (Closes: #816914).
+- Fix runtime warning.
+- Fix memleak when loading SVG fails.
+- GTK+3: force X11 backend.
+
+ -- Mike Gabriel   Sat, 03 Jun 2017 16:05:48 +0200
+
 eom (1.16.0-2) unstable; urgency=medium
 
   * debian/control:
diff -Nru eom-1.16.0/NEWS eom-1.16.1/NEWS
--- eom-1.16.0/NEWS 2016-09-19 07:48:00.0 +0200
+++ eom-1.16.1/NEWS 2017-01-26 13:34:31.0 +0100
@@ -1,3 +1,11 @@
+eom 1.16.1
+==
+
+ * Prefs dialog: fix runtime warning
+ * Fix auto-reload of externally modified image
+ * Fix memleak when loading SVG fails
+ * GTK+3: force X11 backend
+
 eom 1.16.0
 ==
 
diff -Nru eom-1.16.0/src/eom-image.c eom-1.16.1/src/eom-image.c
--- eom-1.16.0/src/eom-image.c  2016-09-19 07:48:00.0 +0200
+++ eom-1.16.1/src/eom-image.c  2017-01-26 13:34:31.0 +0100
@@ -1050,7 +1050,10 @@
}
 #ifdef HAVE_RSVG
if (eom_image_is_svg (img))
-   rsvg_handle_close (priv->svg, error);
+   /* Ignore the error if loading failed earlier
+* as the error will already be set in that case */
+   rsvg_handle_close (priv->svg,
+  (failed ? NULL : error));
 #endif
 }
 
diff -Nru eom-1.16.0/src/eom-list-store.c eom-1.16.1/src/eom-list-store.c
--- eom-1.16.0/src/eom-list-store.c 2016-09-19 07:48:00.0 +0200
+++ eom-1.16.1/src/eom-list-store.c 2017-01-26 13:34:31.0 +0100
@@ -392,7 +392,7 @@
EomImage *image;
 
switch (event) {
-   case G_FILE_MONITOR_EVENT_CHANGED:
+   case G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT:
file_info = g_file_query_info (file,
   
G_FILE_ATTRIBUTE_STANDARD_CONTENT_TYPE,
   0, NULL, NULL);
diff -Nru eom-1.16.0/src/eom-preferences-dialog.c 
eom-1.16.1/src/eom-preferences-dialog.c
--- eom-1.16.0/src/eom-preferences-dialog.c 2016-09-19 07:48:00.0 
+0200
+++ eom-1.16.1/src/eom-preferences-dialog.c 2017-01-26 13:34:31.0 
+0100
@@ -256,6 +256,7 @@
default:
// Log a warning and use EOM_TRANSP_BACKGROUND as fallback
g_warn_if_reached ();
+   case EOM_TRANSP_BACKGROUND:
gtk_toggle_button_set_active (GTK_TOGGLE_BUTTON 
(background_radio), TRUE);
break;
}
diff -Nru eom-1.16.0/src/main.c eom-1.16.1/src/main.c
--- eom-1.16.0/src/main.c   2016-09-19 07:48:00.0 +0200
+++ eom-1.16.1/src/main.c   2017-01-26 13:34:31.0 +0100
@@ -203,6 +203,10 @@
gtk_rc_parse (EOM_DATA_DIR G_DIR_SEPARATOR_S "gtkrc");
 #endif
 
+#if GTK_CHECK_VERSION (3, 0, 0)
+   gdk_set_allowed_backends ("x11");
+#endif
+
ctx = g_option_context_new (NULL);
g_option_context_add_main_entries (ctx, goption_options, PACKAGE);
/* Option groups are free'd together with the context 

Bug#832706: kubernetes: 1.5 is in the archive for a while

[Antonio Terceiro]

Thus closing this bug.


signature.asc
Description: PGP signature

Bug#864048: unblock: marco/1.16.1-1

[Mike Gabriel]

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

Please consider unblocking package marco ready for upload.

>From upstream we received a last-minute fix for #828077 (mate-panel:
Mouse focus problem with stack of applications). The underlying cause has
been fixed in the MATE window manager aka marco.


unblock marco/1.16.1-1

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru marco-1.16.0/configure.ac marco-1.16.1/configure.ac
--- marco-1.16.0/configure.ac   2016-09-19 06:14:56.0 +0200
+++ marco-1.16.1/configure.ac   2017-05-10 18:39:04.0 +0200
@@ -2,7 +2,7 @@
 
 m4_define([marco_major_version], [1])
 m4_define([marco_minor_version], [16])
-m4_define([marco_micro_version], [0])
+m4_define([marco_micro_version], [1])
 
 m4_define([marco_version],
   [marco_major_version.marco_minor_version.marco_micro_version])
diff -Nru marco-1.16.0/debian/changelog marco-1.16.1/debian/changelog
--- marco-1.16.0/debian/changelog   2016-10-01 16:07:35.0 +0200
+++ marco-1.16.1/debian/changelog   2017-06-03 18:20:27.0 +0200
@@ -1,3 +1,11 @@
+marco (1.16.1-1) unstable; urgency=medium
+
+  * New upstream release.
+- Fix strange window switching foreground/background behavior.
+  (Closes: #828077).
+
+ -- Mike Gabriel   Sat, 03 Jun 2017 18:20:27 +0200
+
 marco (1.16.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru marco-1.16.0/NEWS marco-1.16.1/NEWS
--- marco-1.16.0/NEWS   2016-09-19 06:14:56.0 +0200
+++ marco-1.16.1/NEWS   2017-05-10 18:39:04.0 +0200
@@ -1,3 +1,7 @@
+1.16.1
+
+* fix strange window switching foreground/background behavior
+
 1.16.0
 
 * Translations update
diff -Nru marco-1.16.0/src/compositor/compositor.c 
marco-1.16.1/src/compositor/compositor.c
--- marco-1.16.0/src/compositor/compositor.c2016-09-19 06:14:56.0 
+0200
+++ marco-1.16.1/src/compositor/compositor.c2017-05-10 18:39:04.0 
+0200
@@ -172,10 +172,6 @@
 void meta_compositor_free_window (MetaCompositor *compositor,
   MetaWindow *window)
 {
-#ifdef HAVE_COMPOSITE_EXTENSIONS
-  if (compositor && compositor->free_window)
-compositor->free_window (compositor, window);
-#endif
 }
 
 void
diff -Nru marco-1.16.0/src/compositor/compositor-private.h 
marco-1.16.1/src/compositor/compositor-private.h
--- marco-1.16.0/src/compositor/compositor-private.h2016-09-19 
06:14:56.0 +0200
+++ marco-1.16.1/src/compositor/compositor-private.h2017-05-10 
18:39:04.0 +0200
@@ -55,9 +55,6 @@
  MetaScreen *screen,
  MetaWindow *window);
 
-  void (*free_window) (MetaCompositor *compositor,
-   MetaWindow *window);
-
   void (*maximize_window)   (MetaCompositor *compositor,
  MetaWindow *window);
   void (*unmaximize_window) (MetaCompositor *compositor,
diff -Nru marco-1.16.0/src/compositor/compositor-xrender.c 
marco-1.16.1/src/compositor/compositor-xrender.c
--- marco-1.16.0/src/compositor/compositor-xrender.c2016-09-19 
06:14:56.0 +0200
+++ marco-1.16.1/src/compositor/compositor-xrender.c2017-05-10 
18:39:04.0 +0200
@@ -2694,38 +2694,23 @@
 #ifdef HAVE_COMPOSITE_EXTENSIONS
 #endif
 }
-#endif /* 0 */
 
 static void
 xrender_free_window (MetaCompositor *compositor,
  MetaWindow *window)
 {
 #ifdef HAVE_COMPOSITE_EXTENSIONS
-  MetaCompositorXRender *xrc;
-  MetaFrame *frame;
-  Window xwindow;
-
-  xrc = (MetaCompositorXRender *) compositor;
-  frame = meta_window_get_frame (window);
-  xwindow = None;
-
-  if (frame)
-{
-  xwindow = meta_frame_get_xwindow (frame);
-}
-  else
-{
-  /* FIXME: When an undecorated window is hidden this is called, but the
-   * window does not get readded if it is subsequentally shown again. See:
-   * http://bugzilla.gnome.org/show_bug.cgi?id=504876
-   */
-  /* xwindow = meta_window_get_xwindow (window); */
-}
-
-  if (xwindow != None)
-destroy_win (xrc->display, xwindow, FALSE);
+  /* FIXME: When an undecorated window is hidden this is called,
+ but the window does not get readded if it is subsequentally shown again
+ See http://bugzilla.gnome.org/show_bug.cgi?id=504876
+
+ I don't *think* theres any need for this call anyway, leaving it out
+ does not seem to cause any side effects so far, but I should check with
+ someone who understands more. */
+  /* destroy_win (compositor->display, window->xwindow, FALSE); */
 #endif
 }
+#endif /* 0 */
 
 static void