Bug#904241: RFA: xml-rpc-el

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the xml-rpc-el package.

This is a reverse-dependency for another package for which I am
requesting an adopter, debpaste-el.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This is an XML-RPC client library for Emacs Lisp, capable of both
 synchronous and asynchronous method calls.
 .
 An XML-RPC client sends and receives data over HTTP.  The request and
 the response are both described using XML.
 .
 xml-rpc.el represents XML-RPC datatypes as lisp values, automatically
 converting to and from the XML datastructures as needed, both for
 method parameters and return values.  This makes using XML-RPC
 methods transparent to the lisp code.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904242: RFA: debpaste-el

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the debpaste-el package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This package provides an Emacs interface for receiving, posting and
 deleting pastes from .
 .
 Basic interactive commands:
 .
   - `debpaste-display-paste',
   - `debpaste-paste-region',
   - `debpaste-delete-paste'.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904243: RFA: paredit-everywhere -- cut-down version of paredit for non-lisp buffers

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adopter for the paredit-everywhere package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.  FAOD, at
the time of writing, I am not requesting an adopter for paredit-el and I
continue to use paredit-el.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This Emacs addon extends Paredit to non-lisp buffers by providing a
 new minor mode, `paredit-everywhere-mode'.  This works because many
 major modes provide reasonable sexp-oriented navigation.
 .
 Paredit bindings that do not work well outside of lisp buffers are
 not enabled.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904240: RFA: flycheck

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the flycheck package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 Flycheck uses various syntax checking and linting tools to
 automatically check the contents of buffers while the user types, and
 reports warnings and errors directly in the buffer, or in an optional
 error list.
 .
 This package includes flycheck's HTML documentation.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904236: RFA: emacs-world-time-mode

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the emacs-world-time-mode package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This package provides an Emacs major mode to compare timezones.
 After customising a variable to specify the timezones you are
 interested, invoking `M-x world-time-mode` will display comparative
 times in each timezone for a 24-hour period, including the current
 time.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904238: RFA: cycle-quotes

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the cycle-quotes package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This package provides the `cycle-quotes' command to cycle between
 different string quote styles.
 .
 For example, in JavaScript, there are three string quote characters:
 ", ` and '.  In a JavaScript buffer, with point located someplace
 within the string, `cycle-quotes' will cycle between the following
 quote styles each time it's called:
 .
 --> "Hi, it's me!" --> `Hi, it's me!` --> 'Hi, it\'s me!'
 .
 As seen in the above example, `cycle-quotes' tries to escape and
 unescape quote characters intelligently.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904237: RFA: emacs-highlight-indentation

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the emacs-highlight-indentation package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This package provides two Emacs minor modes:
 .
 * highlight-indentation-mode displays guides at each indentation
   level
 * highlight-indentation-current-column-mode displays guides
   indicating other lines indented to the same level as the line
   containing point
 .
 These modes are useful for programming in language like Python which
 use semantic indentation.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904239: RFA: deft

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the deft package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 Deft is an Emacs mode for quickly browsing, filtering, and editing
 directories of plain text notes, inspired by Notational Velocity.
 .
 It was designed for increased productivity when writing and taking
 notes, by making it fast and simple to find the right file at the
 right time, and by automating many of the usual tasks such as
 creating new files and saving files.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904235: RFA: helm-projectile -- Helm integration for Projectile

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adopter for the helm-projectile package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it (though
FAOD, at the time of writing I do not seek an adopter for either helm or
projectile and continue to use both).

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 With this library, Projectile can use Helm for completion.
 .
 See the documentation of elpa-helm and elpa-projectile for more
 details.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904234: RFA: let-alist -- let-bind values of an assoc-list by their names in Emacs Lisp

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adopter for the let-alist package.

The package is a reverse dependency for another package for which I am
seeking an adopter.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This package provides the let-alist macro for use in Emacs Lisp.
 .
 The macro allows the programmer to concisely and efficiently access
 the contents of an association list.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904232: RFA: pointback

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the pointback package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 When you have two windows X and Y showing different sections of the
 same buffer B, then switch to a different buffer in X, and then
 show B in X again, the new point in X will be the same as in Y.
 .
 With pointback-mode (or global-pointback-mode), window points are
 preserved instead, and point will be where it originally was in X for
 B when you return to B.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904231: RFA: wc-mode

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the wc-mode package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 This package provides an Emacs minor mode to display a word, line
 and/or character count in the Emacs modeline.
 .
 In addition, the user can set goals for adding or deleting a given
 number of words.  You can use this to set daily writing or editing
 goals.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904233: RFA: persp-projectile

[Sean Whitton]

Package: wnpp
Severity: normal

I request an adoptor for the persp-projectile package.

This package is no longer in my ~/.emacs.d/init.el and it would be
better if someone who actually uses the package maintains it.

This is a team-maintained package, so the adoptor should either replace
me in Uploaders:, or alternatively take the package out of the team's
hands.

The package description is:
 With this library, Emacs will create a separate perspective for each
 Projectile project.
 .
 See the documentation for elpa-persp and elpa-projectile for more
 details.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#889056: [update] Re: Bug#889056: replace apache-mode.el with elpa package

[Lev Lamberov]

Сб 21 июл 2018 @ 15:41 Nicholas D Steeves :

> https://github.com/emacs-php/apache-mode/
>  + more up-to-date
>  + tags releases
>  + could also become the version people come to expect, because it's
>on MELPA
>  - no description or documentation beyond the short description
>and a code snippet for how to auto-enable the mode.
>
> Ftpmasters would prefer martenjj's copy, because it has a LICENSE
> file.  I've filed an upstream issue to investigate if martenjj would be
> willing to tag a stable release, and reveal plans for future updates:
>   https://github.com/martenjj/apachemode/issues/1

It contains an excerpt from GPL-2 in the code, stating that it is
licensed under GPL-2+. Why do you think FTPMaster will require a LICENSE
file in this case?

Regards,
Lev

Bug#459427: Patch seeking seconds on changelog vs. NEWS handling

[David Bremner]

Sean Whitton  writes:


>> diff --git a/policy/ch-docs.rst b/policy/ch-docs.rst
>> index 1de221f..1503ed8 100644
>> --- a/policy/ch-docs.rst
>> +++ b/policy/ch-docs.rst
>> @@ -255,32 +255,48 @@ files may be installed into ``/usr/share/doc/package``.
>>
>>  .. _s-changelogs:
>>
>> -Changelog files
>> 
>> +Changelog files and release notes
>> +-
>>
>>  Packages that are not Debian-native must contain a compressed copy of
>>  the ``debian/changelog`` file from the Debian source tree in
>>  ``/usr/share/doc/package`` with the name ``changelog.Debian.gz``.
>>
>> -If an upstream changelog is available, it should be accessible as
>> -``/usr/share/doc/package/changelog.gz`` in plain text. If the upstream
>> -changelog is distributed in HTML, it should be made available in that
>> -form as ``/usr/share/doc/package/changelog.html.gz`` and a plain text
>> -``changelog.gz`` should be generated from it using, for example,
>> -``lynx -dump -nolist``. If the upstream changelog files do not already
>> -conform to this naming convention, then this may be achieved either by
>> -renaming the files, or by adding a symbolic link, at the maintainer's
>> +If an upstream release notes file is available, containing a summary
>> +of changes between upstream releases intended for end users of the
>> +package and often called ``NEWS``, it should be accessible as
>> +``/usr/share/doc/package/NEWS.gz``.  An older practice of installing
>> +the upstream release notes as ``/usr/share/doc/package/changelog.gz``
>> +is permitted but deprecated.
>> +
>> +If there is no release notes file available, but there is an upstream
>> +changelog, it should be accessible as
>> +``/usr/share/doc/package/changelog.gz``.  If there are both upstream
>> +release notes and an upstream changelog available, it is recommended
>> +to install the former but not the latter.
>> +
>> +If either of these files are distributed in HTML, they should be made
>> +available at ``/usr/share/doc/package/NEWS.html.gz`` and
>> +``/usr/share/doc/package/changelog.html.gz`` respectively, and plain
>> +text versions ``NEWS.gz`` and ``changelog.gz`` should be generated
>> +from them, using, for example, ``lynx -dump -nolist``.
>> +
>> +If the upstream release notes or changelog do not already conform to
>> +this naming convention, then this may be achieved either by renaming
>> +the files, or by adding a symbolic link, at the maintainer's
>>  discretion.  [#]_
>>
>>  All of these files should be installed compressed using ``gzip -9``, as
>>  they will become large with time even if they start out small.
>>
>> -If the package has only one changelog which is used both as the Debian
>> -changelog and the upstream one because there is no separate upstream
>> -maintainer then that changelog should usually be installed as
>> -``/usr/share/doc/package/changelog.gz``; if there is a separate upstream
>> -maintainer, but no upstream changelog, then the Debian changelog should
>> -still be called ``changelog.Debian.gz``.
>> +If the package has only one file which is used both as the Debian
>> +changelog and the upstream release notes or changelog, because there
>> +is no separate upstream maintainer, then that file should usually be
>> +installed as ``/usr/share/doc/package/NEWS.gz`` or
>> +``/usr/share/doc/package/changelog.gz`` (depending on whether the file
>> +is release notes or a changelog); if there is a separate upstream
>> +maintainer, but no upstream release notes or changelog, then the
>> +Debian changelog should still be called ``changelog.Debian.gz``.
>>
>>  For details about the format and contents of the Debian changelog file,
>>  please see :ref:`s-dpkgchangelog`.

Seconded.

d


signature.asc
Description: PGP signature

Bug#904230: RFS: deepin-deb-installer/1.2.5-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "deepin-deb-installer"

 * Package name: deepin-deb-installer
   Version : 1.2.5-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/deepin-deb-installer
 * License : GPL-3+
   Section : utils

  It builds those binary packages:

deepin-deb-installer - Deepin Package Manager

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

  https://mentors.debian.net/package/deepin-deb-installer


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-deb-installer/deepin-deb-installer_1.2.5-1.dsc

  More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-deb-installer

  Changes since the last upload:

  deepin-deb-installer (1.2.5-1) unstable; urgency=medium

  * New upstream version 1.2.5
  * Bump Standards-Version to 4.1.5 (no changes needed).
  * d/control: Add new uploader Yanhao Mo .
  * d/rules: Drop debian/deepin-deb-installer/usr/share/dman/ relevant part
because the upstream doesn't produce that any more.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#877041: O: ublock-origin -- general-purpose lightweight ads, malware, trackers blocker

[Sean Whitton]

control: retitle -1 O: ublock-origin -- general-purpose lightweight ads, 
malware, trackers blocker

This package is de facto orphaned; see .

Let's update wnpp: I hereby orphan ublock-origin.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#897745: etl: ftbfs with GCC-8

[Philip Chung]

Control: tags -1 fixed-upstream

On Fri, 04 May 2018 12:21:30 + Matthias Klose  wrote:
> Package: src:etl
> Version: 1.2.1-0.1
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
> 
> [...]
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
> severity of this report will be raised before the buster release.
> 
> The full build log can be found at:
> http://aws-logs.debian.net/2018/05/01/gcc8/etl_1.2.1-0.1_unstable_gcc8.log.gz
> The last lines of the build log are at the end of this report.
> 

The error is here:

> In file included from ../ETL/pen:32,
>  from pen.cpp:31:
> ../ETL/_pen.h: In member function 'etl::generic_pen AT>::difference_type::value_type& etl::generic_pen AT>::difference_type::operator[](int) const':
> ../ETL/_pen.h:139:51: error: binding reference of type 'etl::generic_pen AT>::difference_type::value_type&' {aka 'int&'} to 'const value_type' {aka 
> 'const int'} discards qualifiers
>value_type [](int i)const { return i?y:x; }
>^
The error has been fixed upstream with this commit:
https://github.com/synfig/synfig/commit/cb05b072fe6fffb4433140c631f422bdbc036722

It adds overloads for operator[] for const-correctness.

Philip Chung

Bug#459427: Patch seeking seconds on changelog vs. NEWS handling

[Sean Whitton]

control: tag -1 +patch

Hello all,

David Bremner and I took a look at this bug this morning at DebCamp
and I realised that I had been missing something (which Russ had
actually pointed out in an older message): lots of packages already
install a package's NEWS file as /usr/share/doc/foo/NEWS.gz.

This means that making this change would be documenting an existing
practice rather than having Policy drive a change to practice.  So
this removes the reasons that I had for thinking that debhelper should
change first.

We still have the problem that packages installing the NEWS file to
/usr/share/doc/foo/changelog.gz would be made buggy by a change that
simply required the NEWS file to be installed to
/usr/share/doc/foo/NEWS.gz.  But Bill pointed the way to a solution to
this: word Policy to allow both practices, but mark one as deprecated.

Looking through some of the messages to this bug, I think that the
following change is minimal enough to avoid too much controversy and
bikeshedding, so I'm seeking seconds for it.  Two further notes about my
patch:

- The patch defines what release notes are, but does not define what a
  changelog is.  This is not a regression, because Policy does not
  currently define what a changelog is.  And in fact the problem is
  hard, because the way that dev.ref. recommends we use debian/changelog
  makes it sound like it is a release notes file, not a changelog.  So I
  think we should put the issue aside as a separate change and not try
  to address it in this bug.

- I have chosen to include the recommendation not to install both the
  changelog and the release notes if both are available.  I've done this
  using the term 'recommended', which is the weakest requirement Policy
  can impose; maintainer discretion is allowed.  We do seem to have
  something of a consensus on this, and maintainers who do disagree can
  ignore the recommendation.

  The argument for including the recommendation is that a changelog is
  not very useful in a binary package, except as a fallback when no
  release notes are available.  If you're going to dig into an upstream
  changelog you will do so alongside a copy of the upstream source.  So
  distributing the upstream changelog in only the source package, and
  not the binary package(s), makes most sense.

> diff --git a/policy/ch-docs.rst b/policy/ch-docs.rst
> index 1de221f..1503ed8 100644
> --- a/policy/ch-docs.rst
> +++ b/policy/ch-docs.rst
> @@ -255,32 +255,48 @@ files may be installed into ``/usr/share/doc/package``.
>
>  .. _s-changelogs:
>
> -Changelog files
> 
> +Changelog files and release notes
> +-
>
>  Packages that are not Debian-native must contain a compressed copy of
>  the ``debian/changelog`` file from the Debian source tree in
>  ``/usr/share/doc/package`` with the name ``changelog.Debian.gz``.
>
> -If an upstream changelog is available, it should be accessible as
> -``/usr/share/doc/package/changelog.gz`` in plain text. If the upstream
> -changelog is distributed in HTML, it should be made available in that
> -form as ``/usr/share/doc/package/changelog.html.gz`` and a plain text
> -``changelog.gz`` should be generated from it using, for example,
> -``lynx -dump -nolist``. If the upstream changelog files do not already
> -conform to this naming convention, then this may be achieved either by
> -renaming the files, or by adding a symbolic link, at the maintainer's
> +If an upstream release notes file is available, containing a summary
> +of changes between upstream releases intended for end users of the
> +package and often called ``NEWS``, it should be accessible as
> +``/usr/share/doc/package/NEWS.gz``.  An older practice of installing
> +the upstream release notes as ``/usr/share/doc/package/changelog.gz``
> +is permitted but deprecated.
> +
> +If there is no release notes file available, but there is an upstream
> +changelog, it should be accessible as
> +``/usr/share/doc/package/changelog.gz``.  If there are both upstream
> +release notes and an upstream changelog available, it is recommended
> +to install the former but not the latter.
> +
> +If either of these files are distributed in HTML, they should be made
> +available at ``/usr/share/doc/package/NEWS.html.gz`` and
> +``/usr/share/doc/package/changelog.html.gz`` respectively, and plain
> +text versions ``NEWS.gz`` and ``changelog.gz`` should be generated
> +from them, using, for example, ``lynx -dump -nolist``.
> +
> +If the upstream release notes or changelog do not already conform to
> +this naming convention, then this may be achieved either by renaming
> +the files, or by adding a symbolic link, at the maintainer's
>  discretion.  [#]_
>
>  All of these files should be installed compressed using ``gzip -9``, as
>  they will become large with time even if they start out small.
>
> -If the package has only one changelog which is used both as the Debian
> -changelog and the upstream one because there is no separate 

Bug#900977: ITP: python-murmurhash -- Cython bindings for MurmurHash2 [spaCy deps]

[Lumin]

control: retitle -1 RFP: python-murmurhash -- Cython bindings for MurmurHash2 
[spaCy deps]
control: noowner -1

In most cases installing spaCy with pip is enough. spaCy depends on yet
another specific machine learning library "thinc" which I think I don't
have enough energy to take care of in long run.

package available here: 
https://salsa.debian.org/python-team/modules/python-murmurhash

Bug#900945: ITP: python-preshed -- Cython Hash Table for Pre-Hashed Keys [spaCy dependency]

[Lumin]

control: retitle -1 RFP: python-preshed -- Cython Hash Table for Pre-Hashed 
Keys [spaCy dependency]
control: noowner -1

In most cases installing spaCy with pip is enough. spaCy depends on yet
another specific machine learning library "thinc" which I think I don't
have enough energy to take care of in long run.

package available here
https://salsa.debian.org/python-team/modules/python-preshed

Bug#901201: ITP: python-plac -- Smartest command line arguments parser in the world [spaCy deps]

[Lumin]

control: retitle -1 RFP: python-plac -- Smartest command line arguments parser 
in the world [spaCy deps]
control: noowner -1

In most cases installing spaCy with pip is enough. spaCy depends on yet
another specific machine learning library "thinc" which I think I don't
have enough energy to take care of in long run.

package available here: https://salsa.debian.org/python-team/modules/python-plac

Bug#901231: ITP: python-thinc -- Practical Machine Learning for NLP in Python [spaCy deps]

[Lumin]

control: retitle -1 RFP: python-thinc -- Practical Machine Learning for NLP in 
Python [spaCy deps]
control: noowner -1

In most cases installing spaCy with pip is enough. spaCy depends on yet
another specific machine learning library "thinc" which I think I don't
have enough energy to take care of in long run.

package available here
https://salsa.debian.org/science-team/python-thinc

Bug#891074: ITP: you-get/0.4.1025 -- command-line utility to download media contents (videos, audios, images) from the Web

[Lumin]

control: retitle -1 RFP: you-get/0.4.1025 -- command-line utility to download 
media contents (videos, audios, images) from the Web
control: noowner -1

initial packaging is available here
https://salsa.debian.org/lumin-guest/you-get

but anyone who wants to download video from internet must be able to
  pip install you-get

and pip doesn't lag behind upstream.

Bug#900941: ITP: python-cymem -- Cython Memory Helper [SpaCy dependency]

[Lumin]

control: retitle -1 RFP: python-cymem -- Cython Memory Helper [SpaCy dependency]
control: noowner -1

In most cases installing spaCy with pip is enough. spaCy depends on yet
another specific machine learning library "thinc" which I think I don't
have enough energy to take care of in long run.

Packaging avaiable here
https://salsa.debian.org/python-team/modules/python-cymem

Bug#904184: Acknowledgement (Partman(-lvm) claims all disk when it shouldn't)

[Sven Mueller]

I created a pull request on salsa for this:
https://salsa.debian.org/installer-team/partman-auto-lvm/merge_requests/1
Am So., 22. Juli 2018 um 11:01 Uhr schrieb Sven Mueller
:
>
> As far as the feature request goes, the submits I found in Ubuntu to
> implement guided_size (i.e. limiting the space in the VG that gets
> used) were:
> https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/partman-auto-lvm/trusty/revision/19
> https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/partman-auto-lvm/trusty/revision/21
>
> However, I do consider it a bug that (a) maximum size is exceeded and
> (b) the last partition/LV gets all remaining space, irrespective of
> priorities.

Bug#904229: RFS: highwayhash/0~20180209-g14dedec-5 [RC]

[Lumin]

Package: sponsorship-requests
Severity: important

  Dear mentors,

  I am looking for a sponsor for my package "highwayhash"

 * Package name: highwayhash
   Version : 0~20180209-g14dedec-5
   Upstream Author : [fill in name and email of upstream]
 * URL : [fill in URL of upstreams web site]
 * License : [fill in]
   Section : science

  It builds those binary packages:

libhighwayhash-dev - Fast strong hash functions: SipHash/HighwayHash 
(development)
libhighwayhash0 - Fast strong hash functions: SipHash/HighwayHash (library)

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

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

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

dget -x 
https://mentors.debian.net/debian/pool/main/h/highwayhash/highwayhash_0~20180209-g14dedec-5.dsc

  More information about hello can be obtained from https://www.example.com.


http://debomatic-amd64.debian.net/distribution#unstable/highwayhash/0~20180209-g14dedec-5/autopkgtest

  Changes since the last upload:


highwayhash (0~20180209-g14dedec-5) unstable; urgency=medium

  * Refresh symbols to avoid FTBFS with GCC-8 (Closes: #897767)
  * Bump Standards-Version to 4.1.5 (no change).

Bug#904228: ITP: python-certbot-dns-sakuracloud -- SakuraCloud plugin for Certbot

[Harlan Lieberman-Berg]

Package: wnpp
Severity: wishlist
Owner: Harlan Lieberman-Berg 

* Package name: python-certbot-dns-sakuracloud
  Version : 0.26.1
  Upstream Author : Electronic Frontier Foundation
* URL : https://certbot.eff.org
* License : Apache-2.0
  Programming Lang: Python
  Description : SakuraCloud plugin for Certbot

This is the SakuraCloud DNS plugin for Certbot.  It will be managed
under the auspices of the Debian Let's Encrypt Team.

Bug#904227: ITP: python-certbot-dns-gehirn -- Gehirn DNS plugin for Certbot

[Harlan Lieberman-Berg]

Package: wnpp
Severity: wishlist
Owner: Harlan Lieberman-Berg 

* Package name: python-certbot-dns-gehirn
  Version : 0.21.1
  Upstream Author : Electronic Frontier Foundation
* URL : https://certbot.eff.org
* License : Apache-2.0
  Programming Lang: Python
  Description : Gehirn DNS plugin for Certbot

 This plugin will be maintained under the auspices of the Debian Let's
 Encrypt team.

Bug#892514: libdbd-mysql-perl: 4.046-1 SSL certificate validation failure

[Corey Hickey]

I filed a bug against mariadb-client-core-10.1 for this:

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

I don't know if there is anything that can be done for 
libdbd-mysql-perl, since the problem seems to be in the underlying 
mariadb library.


-Corey

Bug#903966: wine-development: FTBFS on most architectures

[Michael Gardner]

Probably related to https://bugs.winehq.org/show_bug.cgi?id=41436

Bug#904184: Acknowledgement (Partman(-lvm) claims all disk when it shouldn't)

[Sven Mueller]

As far as the feature request goes, the submits I found in Ubuntu to
implement guided_size (i.e. limiting the space in the VG that gets
used) were:
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/partman-auto-lvm/trusty/revision/19
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/partman-auto-lvm/trusty/revision/21

However, I do consider it a bug that (a) maximum size is exceeded and
(b) the last partition/LV gets all remaining space, irrespective of
priorities.

Bug#892077: rakarrack: Segfaults after jackd upgrade

[Stefan Potyra]

Hi,

this time, I won't forget to attach the patch.

Cheers,
  Stefan.
diff -Nru rakarrack-0.6.1/debian/changelog rakarrack-0.6.1/debian/changelog
--- rakarrack-0.6.1/debian/changelog2011-12-27 17:53:47.0 +0100
+++ rakarrack-0.6.1/debian/changelog2018-07-22 01:36:05.0 +0200
@@ -1,3 +1,11 @@
+rakarrack (0.6.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add debian/patches/05_fix_segfault.diff to fix a segfault on
+startup (Closes: #892077)
+
+ -- Stefan Potyra   Sun, 22 Jul 2018 01:36:05 +0200
+
 rakarrack (0.6.1-4) unstable; urgency=low
 
   * Switch to dpkg-source 3.0 (quilt) format
diff -Nru rakarrack-0.6.1/debian/patches/05_fix_segfault.diff 
rakarrack-0.6.1/debian/patches/05_fix_segfault.diff
--- rakarrack-0.6.1/debian/patches/05_fix_segfault.diff 1970-01-01 
01:00:00.0 +0100
+++ rakarrack-0.6.1/debian/patches/05_fix_segfault.diff 2018-07-22 
01:36:05.0 +0200
@@ -0,0 +1,22 @@
+Description: Fix segfault with uninitialiized variable
+ Ppreset is uninitialized in this function, which leads to a 
+ segfault later on.
+
+ Thanks to Ben Wiederhake for finding the details.
+
+ The bug was forwarded to Ryan via private mail on 10 Mar 2018.
+
+Author: Stefan Potyra 
+Bug-Debian: https://bugs.debian.org/892077
+
+--- rakarrack-0.6.1.orig/src/Looper.C
 rakarrack-0.6.1/src/Looper.C
+@@ -28,7 +28,7 @@
+ #include 
+ #include "Looper.h"
+ 
+-Looper::Looper (float * efxoutl_, float * efxoutr_, float size)
++Looper::Looper (float * efxoutl_, float * efxoutr_, float size) : Ppreset(0)
+ {
+   efxoutl = efxoutl_;
+   efxoutr = efxoutr_;
diff -Nru rakarrack-0.6.1/debian/patches/series 
rakarrack-0.6.1/debian/patches/series
--- rakarrack-0.6.1/debian/patches/series   2011-12-27 17:14:22.0 
+0100
+++ rakarrack-0.6.1/debian/patches/series   2018-07-22 01:36:05.0 
+0200
@@ -1,2 +1,3 @@
 04_fix_manpage.diff
 format-security.diff
+05_fix_segfault.diff


signature.asc
Description: PGP signature

Bug#904226: RFS: lxml/4.2.3-1~bpo9+1

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my continued support of a "lxml"
backport.  I believe this update from 4.2.1 because of the following
fix:

  4.2.2 (2018-06-22)
  Bugs fixed
GH#266: Fix sporadic crash during GC when parse-time schema validation
is used and the parser participates in a reference cycle. Original
patch by Julien Greard.

Package name: lxml
Version : 4.2.3-1~bpo9+1
Upstream Author : Stefan Behnel 
URL : http://lxml.de/
License : PSF, BSD, MIT, and GPL
Section : python

It builds these binary packages:

  python-lxml - pythonic binding for the libxml2 and libxslt libraries
  python-lxml-dbg - pythonic binding for the libxml2 and libxslt libraries 
(debug ext
  python-lxml-doc - pythonic binding for the libxml2 and libxslt libraries 
(documenta
  python3-lxml - pythonic binding for the libxml2 and libxslt libraries
  python3-lxml-dbg - pythonic binding for the libxml2 and libxslt libraries 
(debug ext

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lxml/lxml_4.2.3-1~bpo9+1.dsc

Alternatively, sponsor from this git repo:

  git clone https://salsa.debian.org/sten-guest/lxml.git
  cd lxml
  git checkout stretch-backports

Changes since the last upload:

lxml (4.2.3-1~bpo9+1) stretch-backports; urgency=medium

  * Rebuild for stretch-backports.

 -- Nicholas D Steeves   Mon, 16 Jul 2018 18:56:54 -0400

lxml (4.2.3-1) unstable; urgency=medium

  * New upstream version 4.2.3.

 -- Matthias Klose   Wed, 11 Jul 2018 14:43:51 +0200

lxml (4.2.1-1) unstable; urgency=medium


Regards,
Nicholas D Steeves

Bug#904204: openjdk-11: Please update patch for m68k support

[John Paul Adrian Glaubitz]

On 07/21/2018 04:48 PM, John Paul Adrian Glaubitz wrote:
> Please replace the patch with the attached version for the next upload.

The patch was unfortunately incomplete, it missed the size adjustments
for make/gensrc/GensrcX11Wrappers.gmk. Attaching an updated one.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
# HG changeset patch
# User glaubitz
# Date 1532184301 -7200
#  Sat Jul 21 16:45:01 2018 +0200
# Node ID b34e9e0ef820b0b0a0eb55d97f41281fc8db2793
# Parent  b0fcf59be3918afcaa13d1f97343968c2c467ffe
JDK-NNN: Zero needs alignment fixes for linux-m68k

diff -r b0fcf59be391 -r b34e9e0ef820 make/data/x11wrappergen/sizes-32-linux-m68k.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +
+++ b/make/data/x11wrappergen/sizes-32-linux-m68k.txt	Sat Jul 21 16:45:01 2018 +0200
@@ -0,0 +1,1017 @@
+long	4
+int	4
+short	2
+ptr	4
+Bool	4
+Atom	4
+Window	4
+XExtData.number	0
+XExtData.next	4
+XExtData.free_private	8
+XExtData.private_data	12
+XExtData	16
+XIMStringConversionCallbackStruct.position	0
+XIMStringConversionCallbackStruct.direction	2
+XIMStringConversionCallbackStruct.operation	6
+XIMStringConversionCallbackStruct.factor	8
+XIMStringConversionCallbackStruct.text	10
+XIMStringConversionCallbackStruct	14
+XkbNewKeyboardNotifyEvent.type	0
+XkbNewKeyboardNotifyEvent.serial	4
+XkbNewKeyboardNotifyEvent.send_event	8
+XkbNewKeyboardNotifyEvent.display	12
+XkbNewKeyboardNotifyEvent.time	16
+XkbNewKeyboardNotifyEvent.xkb_type	20
+XkbNewKeyboardNotifyEvent.device	24
+XkbNewKeyboardNotifyEvent.old_device	28
+XkbNewKeyboardNotifyEvent.min_key_code	32
+XkbNewKeyboardNotifyEvent.max_key_code	36
+XkbNewKeyboardNotifyEvent.old_min_key_code	40
+XkbNewKeyboardNotifyEvent.old_max_key_code	44
+XkbNewKeyboardNotifyEvent.changed	48
+XkbNewKeyboardNotifyEvent.req_major	52
+XkbNewKeyboardNotifyEvent.req_minor	53
+XkbNewKeyboardNotifyEvent	54
+XTimeCoord.time	0
+XTimeCoord.x	4
+XTimeCoord.y	6
+XTimeCoord	8
+XkbCompatMapNotifyEvent.type	0
+XkbCompatMapNotifyEvent.serial	4
+XkbCompatMapNotifyEvent.send_event	8
+XkbCompatMapNotifyEvent.display	12
+XkbCompatMapNotifyEvent.time	16
+XkbCompatMapNotifyEvent.xkb_type	20
+XkbCompatMapNotifyEvent.device	24
+XkbCompatMapNotifyEvent.changed_groups	28
+XkbCompatMapNotifyEvent.first_si	32
+XkbCompatMapNotifyEvent.num_si	36
+XkbCompatMapNotifyEvent.num_total_si	40
+XkbCompatMapNotifyEvent	44
+XIMStatusDrawCallbackStruct.type	0
+XIMStatusDrawCallbackStruct.data	4
+XIMStatusDrawCallbackStruct	8
+XKeyboardControl.key_click_percent	0
+XKeyboardControl.bell_percent	4
+XKeyboardControl.bell_pitch	8
+XKeyboardControl.bell_duration	12
+XKeyboardControl.led	16
+XKeyboardControl.led_mode	20
+XKeyboardControl.key	24
+XKeyboardControl.auto_repeat_mode	28
+XKeyboardControl	32
+XSelectionClearEvent.type	0
+XSelectionClearEvent.serial	4
+XSelectionClearEvent.send_event	8
+XSelectionClearEvent.display	12
+XSelectionClearEvent.window	16
+XSelectionClearEvent.selection	20
+XSelectionClearEvent.time	24
+XSelectionClearEvent	28
+XWindowChanges.x	0
+XWindowChanges.y	4
+XWindowChanges.width	8
+XWindowChanges.height	12
+XWindowChanges.border_width	16
+XWindowChanges.sibling	20
+XWindowChanges.stack_mode	24
+XWindowChanges	28
+XIMPreeditCaretCallbackStruct.position	0
+XIMPreeditCaretCallbackStruct.direction	4
+XIMPreeditCaretCallbackStruct.style	8
+XIMPreeditCaretCallbackStruct	12
+XOMCharSetList.charset_count	0
+XOMCharSetList.charset_list	4
+XOMCharSetList	8
+XOMFontInfo.num_font	0
+XOMFontInfo.font_struct_list	4
+XOMFontInfo.font_name_list	8
+XOMFontInfo	12
+AwtScreenData.numConfigs	0
+AwtScreenData.root	4
+AwtScreenData.whitepixel	8
+AwtScreenData.blackpixel	12
+AwtScreenData.defaultConfig	16
+AwtScreenData.configs	20
+AwtScreenData	24
+XIMHotKeyTrigger.keysym	0
+XIMHotKeyTrigger.modifier	4
+XIMHotKeyTrigger.modifier_mask	8
+XIMHotKeyTrigger	12
+XCirculateEvent.type	0
+XCirculateEvent.serial	4
+XCirculateEvent.send_event	8
+XCirculateEvent.display	12
+XCirculateEvent.event	16
+XCirculateEvent.window	20
+XCirculateEvent.place	24
+XCirculateEvent	28
+Screen.ext_data	0
+Screen.display	4
+Screen.root	8
+Screen.width	12
+Screen.height	16
+Screen.mwidth	20
+Screen.mheight	24
+Screen.ndepths	28
+Screen.depths	32
+Screen.root_depth	36
+Screen.root_visual	40
+Screen.default_gc	44
+Screen.cmap	48
+Screen.white_pixel	52
+Screen.black_pixel	56
+Screen.max_maps	60
+Screen.min_maps	64
+Screen.backing_store	68
+Screen.save_unders	72
+Screen.root_input_mask	76
+Screen	80
+XMapRequestEvent.type	0
+XMapRequestEvent.serial	4
+XMapRequestEvent.send_event	8
+XMapRequestEvent.display	12
+XMapRequestEvent.parent	16
+XMapRequestEvent.window	20
+XMapRequestEvent	24
+XIMText.length	0
+XIMText.feedback	2
+XIMText.encoding_is_wchar	6
+XIMText.string	10
+XIMText	14
+XGraphicsExposeEvent.type	0
+XGraphicsExposeEvent.serial	4
+XGraphicsExposeEvent.send_event	8

Bug#629405: [Debconf-devel] Bug#629405: debconf: libqtgui4-perl based frontend might need to be removed

[Colin Watson]

On Sat, Jul 21, 2018 at 02:22:16PM +0200, gregor herrmann wrote:
> On Sat, 21 Jul 2018 15:13:30 +0300, Niko Tyni wrote:
> > Not quite but we're close now (thanks again Colin!). The old Qt frontend
> > and the corresponding build dependency on libqtgui4-perl are still there
> > as Colin is seeking testers for the new frontend.  See #631769 .
> 
> Oh, I see. Seems I was confused by (the various bugs and) the
> changelog entry "libqtcore4-perl and libqtgui4-perl packages are no
> longer necessary and can be safely removed."

Right, sorry, that's specifically if you're using the new Kde frontend.
But hopefully soon I'll get some test reports and be confident in
actually removing the old Kde (now Qt) frontend ...

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

Bug#672180: emacs-goodies-el: pod-mode.el xemacs21 *Warnings* min-colors

[Nicholas D Steeves]

Control: retitle -1 replace pod-mode.el with elpa-pod-mode
Control: severity -1 normal

Our own Florian Ragwitz is now the upstream maintainer for POD mode:
  https://github.com/renormalist/emacs-pod-mode

Florian, are you interested in maintaining this Debian package on the
Debian Emacsen team?  With dh-elpa it's really easy, and also much
easier to maintain long-term--see 'man dh-make-elpa'.  I'd be happy to
help out with any questions you might have.

Cheers,
Nicholas



signature.asc
Description: PGP signature

Bug#904225: Loading a game from within a game loads the wrong save file

[Josh Triplett]

Package: singularity
Version: 0.30c-1
Severity: normal

Loading a game from the main menu works fine. However, from within a
game, if you use the menu to load a game, the wrong save file gets
loaded.

To reproduce:

- Create multiple save files with visibly distinct states (for instance,
  bases built in different locations).
- Start a new game.
- From within that game, load the second save in the list.
- Notice that the state doesn't correspond to that saved game.



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

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

Versions of packages singularity depends on:
ii  python-numpy 1:1.14.5-1+b1
ii  python-pygame1.9.3+dfsg2-2
ii  ttf-dejavu-core  2.37-1

Versions of packages singularity recommends:
ii  singularity-music  007-1

Versions of packages singularity suggests:
pn  timidity  

-- no debconf information

Bug#903256: ITA: mktorrent

[Peter Pentchev]

package wnpp
retitle 903256 ITA: mktorrent -- simple command line utility to create 
BitTorrent metainfo files
owner 903256 !
thanks

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#891872: transition: curl

[Sebastian Andrzej Siewior]

On 2018-07-19 00:39:27 [+0200], To Emilio Pozuelo Monfort wrote:
> - scilab
>   rebuilt everywhere except for i386. Plus
>   #891351 [G|  |  ] [scilab] scilab segfaults at startup
>   #875790 [S|⛺+|  ] [src:scilab] scilab: depends on openjdk-8
>   #884033 [S|  |☣] [scilab] scilab segfaults building 
> scilab-{ann,celestlab,plotlib}
>   #902826 [S|  |  ] [src:scilab] scilab: FTBFS on i386 - seg. fault during 
> build
> 
>   Building currently without all (#902826).  Assuming it works, would it
>   make sense to NMU+2d it? We would get rid of one RC bug for curl but…

This one got worse since gcc-8 is the default[0], this is amd64:

|/bin/bash ../../libtool  --tag=F77   --mode=compile gfortran -DNDEBUG -m64 
-fPIC -I../../modules/core/includes/ -g -O2 -c -o src/fortran/twodq.lo 
src/fortran/twodq.f
| /bin/bash ../../libtool  --tag=F77   --mode=compile gfortran -DNDEBUG -m64 
-fPIC -I../../modules/core/includes/ -g -O2 -c -o src/fortran/dqagse.lo 
src/fortran/dqagse.f
| libtool: compile:  gfortran -DNDEBUG -m64 -fPIC 
-I../../modules/core/includes/ -g -O2 -c src/fortran/xerrwv.f  -fPIC -o 
src/fortran/.libs/xerrwv.o
| /bin/bash ../../libtool  --tag=F77   --mode=compile gfortran -DNDEBUG -m64 
-fPIC -I../../modules/core/includes/ -g -O2 -c -o src/fortran/greatr.lo 
src/fortran/greatr.f
| libtool: compile:  gfortran -DNDEBUG -m64 -fPIC 
-I../../modules/core/includes/ -g -O2 -c src/fortran/twodq.f  -fPIC -o 
src/fortran/.libs/twodq.o
| libtool: compile:  gfortran -DNDEBUG -m64 -fPIC 
-I../../modules/core/includes/ -g -O2 -c src/fortran/dqagse.f  -fPIC -o 
src/fortran/.libs/dqagse.o
| libtool: compile:  gfortran -DNDEBUG -m64 -fPIC 
-I../../modules/core/includes/ -g -O2 -c src/fortran/greatr.f  -fPIC -o 
src/fortran/.libs/greatr.o
| /bin/bash ../../libtool  --tag=F77   --mode=compile gfortran -DNDEBUG -m64 
-fPIC -I../../modules/core/includes/ -g -O2 -c -o src/fortran/hpdel.lo 
src/fortran/hpdel.f
| src/fortran/twodq.f:373:17:
|
|call tridv(node,node1,node2,0.5d0,1)
|  1
| Error: Actual argument contains too few elements for dummy argument 'node' 
(9/10) at (1)
| make[3]: *** [Makefile:1444: src/fortran/twodq.lo] Error 1

I am not fluent in fortran so I can't tell if this is a temporary glitch
or a new permant FTBFS.
Any suggestions from the D-Science folks?

[0] I *think* it is gcc-8 because I built it recently and it built on
amd64 but today it doesn't anymore.

Sebastian

Bug#904224: ITP: feathernotes -- FeatherNotes is a lightweight Qt5 hierarchical notes-manager for Linux. It is independent of any desktop environment.

[Alf Gaida]

Package: wnpp
Severity: wishlist
Owner: Alf Gaida 

* Package name: feathernotes
  Version : 0.4.5
  Upstream Author : Pedram Pourang, a.k.a. Tsu Jan tsujan2...@gmail.com
* URL : https://github.com/tsujan/FeatherNotes
* License : GPL
  Programming Lang: C++
  Description : FeatherNotes is a lightweight Qt5 hierarchical 
notes-manager for Linux.

FeatherNotes (by Pedram Pourang, a.k.a. Tsu Jan tsujan2...@gmail.com) is a 
lightweight Qt5
hierarchical notes-manager for Linux. It is independent of any desktop 
environment and has:

* Support for rich text formatting, image embedding and inserting editable 
tables;
* Drag-and-drop capability for moving nodes and also for embedding images;
* A tray icon for quick access on any desktop;
* Correct position/size saving and restoring with most window managers;
* Compact but complete search and replacement widgets;
* The ability to include searchable tags (hidden info on each node);
* Support for local and remote hyperlinks (bookmarks);
* Text zooming;
* Printing and exporting to HTML and PDF;
* Password protection;
* Auto-saving; and

Other features that can be found in its settings, on its menus or when it is 
actually used.

Usefulness: We don't have a Qt based note taking application right now, so 
FeatherNotes will
a great enhenchment of the LXQt and Qt portfolio at all. The LXQt packaging 
team will maintain
it.

Bug#897471: python-magic: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Christoph Biedl]

Control: tags 897471 confirmed upstream pending

Lucas Nussbaum wrote...

> During a rebuild of all packages in sid, your package failed to build on
> amd64.

> > ==
> > FAIL: test_descriptions (test.test.MagicTest)
> > --
> > Traceback (most recent call last):
> >   File "/<>/test/test.py", line 73, in test_descriptions
> > 'text.txt': 'ASCII text',
> >   File "/<>/test/test.py", line 32, in assert_values
> > self.assertTrue(False, "no match for " + repr(expected_value))
> > AssertionError: no match for ('gzip compressed data, was "test", from Unix, 
> > last modified: Sun Jun 29 01:32:52 2008', 'gzip compressed data, was 
> > "test", last modified: Sun Jun 29 01:32:52 2008, from Unix')
> > 
> > --

That's actually in libmagic, and a fairly nasty mis-feature. I'll
disable that particular check for the time being as python-magic is just
the bringer of the news.

Christoph


signature.asc
Description: PGP signature

Bug#473227: less displaying BOM

[Paul Hardy]

> BOM is a piece of binary junk that most programs don't accept

I agree that it does not make sense philosophically for a "byte order
mark" to be in a file encoded in a way that is byte-order independent.
The Unicode Standard does not recommend its use in a UTF-8 file
because it is not necessary.

However, it is a bug for programs not to accept the BOM at the start
of a UTF-8 file, because the Unicode Standard explicitly allows its
presence in a UTF-8 file as a byte order mark.  See Table 2.4, "The
Seven Unicode Encoding Schemes", which has been in the Unicode
Standard for more than a decade (Table 2.4 was in Unicode version 5.0
and it is still in Unicode version 11.0, released in June 2018).

I use "od" (for example, "od -t c my-file | head -1" or "od -t x1
my-file | head -1") to see if a file starts with a BOM, or have a
program I wrote check for it.  I would not trust "less" or some other
program besides "od" to display it.

I think "less" should display printable characters the way they are
expected to be viewed unless viewing a file in raw mode.  The formal
rendering of the BOM is as a "zero-width no-break space".  That was
its original purpose as a word joiner, and that is how the Unicode
Standard says it still should be rendered for backward-compatibility
with earlier versions of Unicode (see Unicode Standard 11.0, Section
23.2, Layout Controls).

Even in raw mode, I still would not trust less to find out if a file
started with a BOM--I use od.

Thanks,


Paul Hardy

Bug#904222: ITP: puppet-module-voxpupuli-corosync -- Puppet module for corosync / pacemaker

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: puppet-module-voxpupuli-corosync
  Version : 5.0.0
  Upstream Author : Puppet Labs Inc
* URL : https://github.com/voxpupuli/puppet-corosync
* License : Apache-2.0
  Programming Lang: Puppet
  Description : Puppet module for corosync / pacemaker

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 puppet-corosync manages things like virtual IP shared in a cluster.

Bug#897856: FWIW build error

[Geert Stappers]

For What Its Worth: example of build error

uc51.cc: In member function 'virtual const char* cl_51core::disass(t_addr, 
const char*)':
uc51.cc:335:37: error: unable to find string literal operator 'operator""_A_' 
with 'const char [5]', 'long 
unsigned int' arguments
   sprintf(temp, "%04"_A_"x",
 ^~~
uc51.cc:341:37: error: unable to find string literal operator 'operator""_A_' 
with 'const char [5]', 'long 
unsigned int' arguments
   sprintf(temp, "%04"_A_"x",
 ^~~
uc51.cc:347:39: error: unable to find string literal operator 'operator""_M_' 
with 'const char [5]', 'long 
unsigned int' arguments
 sprintf(temp, "%02"_M_"x", rom->get(addr+1));
   ^~~
uc51.cc:351:39: error: unable to find string literal operator 'operator""_M_' 
with 'const char [5]', 'long 
unsigned int' arguments
 sprintf(temp, "%02"_M_"x", rom->get(addr+2));
   ^~~

Bug#803744: Still not fixed in Raspbian GNU/Linux 9 (stretch)

[Theodore Y. Ts'o]

On Fri, Jul 20, 2018 at 09:35:53PM +0200, Alexander Dahl wrote:
> Hei hei,
> 
> I can confirm that behaviour for Raspbian GNU/Linux 9 (stretch), quote
> from syslog:
> 
> Jul 20 17:17:04 darcy systemd-fsck[96]: fsck.f2fs: invalid option -- 'y'
>
> If you have any hints on how to solve that, I would happily test it.
> 

f2fs-tools in Debian Stretch is version 1.07 (released July 2016).

This was fixed in f2fs-tools version 1.10, which is in Debian Testing
and Debian Unstable.  f2fs-tools version 1.10 is also available in
Debian Backports, if you want to use it with Debian Stretch.

For information, please see:

https://backports.debian.org/Instructions/

- Ted

Bug#904220: Acknowledgement (apache2: ALPN protocol: http/1.1, instead of h2. This occured on my server after updating.)

[Mike Rotondo]

Here's the fix, which is a downgrade to 2.4.25-3+deb9u4, with dependencies:
apt-get install apache2=2.4.25-3+deb9u4 apache2-bin=2.4.25-3+deb9u4
apache2-utils=2.4.25-3+deb9u4 apache2-data=2.4.25-3+deb9u4


Here it is:
root@hostname:/home/username# dpkg-query -l apache2
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version Architecture
Description
+++-=-===-===-===
ii  apache2   2.4.25-3+deb9u5 amd64
 Apache HTTP Server
root@hostname:/home/username#


$ echo | openssl s_client -alpn h2 -connect ServerInQuestion:443 | grep ALPN
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = ServerInQuestion
verify return:1
DONE
ALPN protocol: http/1.1

root@hostname:/home/username# apt-get install apache2=2.4.25-3+deb9u4
apache2-bin=2.4.25-3+deb9u4 apache2-utils=2.4.25-3+deb9u4
apache2-data=2.4.25-3+deb9u4
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  www-browser apache2-doc apache2-suexec-pristine | apache2-suexec-custom
The following packages will be DOWNGRADED:
  apache2 apache2-bin apache2-data apache2-utils
0 upgraded, 0 newly installed, 4 downgraded, 0 to remove and 4 not upgraded.
Need to get 1797 kB of archives.
After this operation, 9216 B disk space will be freed.
Do you want to continue? [Y/n] y

$ echo | openssl s_client -alpn h2 -connect ServerInQuestion:443 | grep
ALPN
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = ServerInQuestion
verify return:1
ALPN protocol: h2
DONE

Bug#904156: [Pkg-openssl-devel] Bug#904156: openssl: ALPN protocol: http/1.1, instead of h2. This occured on my server after updating.

[Mike Rotondo]

Downgrading to apache2 2.4.25-3+deb9u4 restores http2 functionality, and a
new report has been opened to reflect this, so this issue has been moved
here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904220

Bug#904221: ITP: srs-lte -- Open source SDR LTE software suite

[Ruben Undheim]

Package: wnpp
Owner: Ruben Undheim 
Severity: wishlist

* Package name: srs-lte (upstream: srsLTE)
  Version : 18.06.1
  Upstream Author : Software Radio Systems Limited
* URL : www.softwareradiosystems.com/tag/srslte/
* License : AGPL-3+
  Programming Lang: C++/C
  Description : Open source SDR LTE software suite

This package allows using a software radio as an LTE (4G) PHY.

srsLTE is a free and open-source LTE software suite developed by SRS
(www.softwareradiosystems.com).

It includes:

srsUE - a complete SDR LTE UE application featuring all layers from PHY to IP
srsENB - a complete SDR LTE eNodeB application
srsEPC - a light-weight LTE core network implementation with MME, HSS and S/P-GW
a highly modular set of common libraries for PHY, MAC, RLC, PDCP, RRC,
NAS, S1AP and GW layers.

It can be used together with nextepc.

It will be maintained in the Debian Mobcom team.

Bug#904220: apache2: ALPN protocol: http/1.1, instead of h2. This occured on my server after updating.

[Mike Rotondo]

Package: apache2
Version: 2.4.25-3+deb9u5
Severity: important

Dear Maintainer,

   * What led up to the situation?
Updating to apache 2.4.25-3+deb9u5 amd64
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgrading to apache 2.4.25-3+deb9u4; see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904156 which incorrectly
states the bug as a problem with openssl.
   * What was the outcome of this action?
Http2 works again.
   * What outcome did you expect instead?
No particular outcome expected.



-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.25-3+deb9u5
ii  apache2-data 2.4.25-3+deb9u5
ii  apache2-utils2.4.25-3+deb9u5
ii  dpkg 1.18.25
ii  init-system-helpers  1.48
ii  lsb-base 9.20161125
ii  mime-support 3.60
ii  perl 5.24.1-3+deb9u4
ii  procps   2:3.3.12-3+deb9u1

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.39

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-5
ii  libaprutil1  1.5.4-3
ii  libaprutil1-dbd-sqlite3  1.5.4-3
ii  libaprutil1-ldap 1.5.4-3
ii  libc62.24-11+deb9u3
ii  libldap-2.4-22.4.44+dfsg-5+deb9u2
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libnghttp2-141.18.1-1
ii  libpcre3 2:8.39-3
ii  libssl1.0.2  1.0.2l-2+deb9u3
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2
ii  perl 5.24.1-3+deb9u4
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2 is related to:
ii  apache2  2.4.25-3+deb9u5
ii  apache2-bin  2.4.25-3+deb9u5

-- Configuration Files:
/etc/apache2/sites-available/000-default.conf changed:

# The ServerName directive sets the request scheme, hostname and
port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header
to
# match this virtual host. For the default virtual host (this file)
this
# value is not decisive as it is used as a last resort host
regardless.
# However, you must set it for any further virtual host explicitly
ServerName ServerWebAddress
ServerAlias www.ServerWebAddress
ServerAlias Hostname.ServerWebAddress
SetOutputFilter DEFLATE
DeflateCompressionLevel 9
HostnameLookups Off

SetHandler application/x-httpd-php


LogLevel http2:info

Protocols h2 h2c http/1.1
ServerAdmin m.j.roto...@gmail.com
DocumentRoot /var/www/html/ServerWebAddress
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# Available loglevels: trace8, ..., trace1, debug, info, notice,
warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn

Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example
the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
RewriteEngine on
RewriteCond %{SERVER_NAME} =ServerWebAddress [OR]
RewriteCond %{SERVER_NAME} =Hostname.ServerWebAddress [OR]
RewriteCond %{SERVER_NAME} =www.ServerWebAddress
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]



-- no debconf information

Bug#904218: Wrong version

[Ruben Undheim]

I entered wrong version. It should be  0.3.9

Bug#897737: ddcutil: ftbfs with GCC-8

[Nicholas D Steeves]

Control: forwarded -1 https://github.com/rockowitz/ddcutil/issues/57


signature.asc
Description: PGP signature

Bug#904219: ITP: freediameter -- Diameter protocol implementation

[Ruben Undheim]

Package: wnpp
Owner: Ruben Undheim 
Severity: wishlist

* Package name: freediameter
  Version : 1.2.1
  Upstream Author : Freediameter developers (Sebastien Decugis, )
* URL : http://www.freediameter.net/trac/
* License : BSD-3-clause
  Programming Lang: C
  Description : Diameter protocol implementation


freeDiameter is an implementation of the Diameter protocol specified
in RFC3588. Diameter is a protocol for carrying Authentication,
Authorization and Accounting information. It is an evolution of the
widely-deployed RADIUS protocol. freeDiameter also implements the
changes to the Diameter protocol introduced by the rfc3588bis Internet
Draft (work in progress).

It is a dependency of nextepc and therefore required to get software for
4G cellular network infrastructure into Debian.

There is a package called erlang-diameter already in Debian, but this
is the first
C implementation of Diameter to be added to Debain AFAIK.

It will be maintained in the Debian Mobcom team.

Bug#892869: pkg sdcc git repository

[Geert Stappers]

Hello Bastien,

In March you wrote https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892869#5
a wishlist BR for packaging new upstream version of sdcc


If you a git clone of previous sdcc  packaging ( for Alioth days )
then please push it to Salsa.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897856#12
for additional information.


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: PGP signature

Bug#904217: debmake: typos in man page

[Paul Hardy]

Package: debmake
Version: 4.3.0
Severity: minor
Tags: patch

Here are patches for the debmake man page.  These could also be
applied to the debmake man page that appears at the end of the "Guide
for Debian Maintainers" document and to the description of the
"-x[0-4]" flags in the main body of that guide.

The first change is "program to make the Debian source package" -->
"program to make a Debian source package"; it can also be changed in
the Description field in debian/control.

It looks like this man page might have been created from Docbook.  If
so, I do not know how to apply the typographic changes to Docbook
source, but I will describe them below.

Ellipses (three periods in a row) look better in troff/groff typeset
output if there is more space between each period than ordinarily
surrounds a period.  In nroff/troff, the traditional way of
accomplishing this has been to put a "thick space" between the periods
by typing "\|.\|.\|." instead of "...".  I made those changes.

There were also instances of "\&.\&.\&.".  If what was intended was a
thin space, that would be "\^" and not "\&".  "\&" can do weird things
with alignment if you don't know how to use it, and it appeared
throughout the file.  The file seems to have been generated by a
Docbook style sheet, so there might be a bug in whatever style sheet
was used.

In nroff, if in the middle of a line you temporarily switch to a
different font style and then switch back to what you were using, it
is preferable to use the "\fP" markup to return to the previous font
style ("P" is for "previous", as in the previous font style).  For
example, you can change "\fB-x0\fR" to "\fB-x0\fP".  See where I did
that as I mention in the next paragraph...

The "-x[0-4]" options had ",," (two commas) to represent a quote mark,
to mean that everything in the preceding line applied.  The symbol for
a quote is locale-dependent though.  For example, in the U.S. we would
use '' instead of ,,.  I added "same as \fB-x[0-3]\fP"... to avoid the
whole quote/locale issue (you can look at the result to see what I
did.

For the "-y" option, where you say doubled option = "force no", does
that mean "-y -y" will force a "no" response?  That was the one part I
wasn't sure about.

In the CAVEAT section, it says: "You must remove or edit such comment
lines...".  I changed that to "You should remove or edit such comment
lines..." because I think "must" would imply a policy violation.
"Should" implies a recommendation.  If it truly is a policy violation,
then I need to remove or edit the comments in my debian/watch files.
:-)

You might want to change the copyright from "2014-2015" to
"2014-2018", but I didn't change that in case "2014-2018" is what you
intended.

I am also attaching the PDFs, so you can see the before and after
results.  I created them with, for example:

 groff debmake.1 > debmake.1.ps
 ps2pdf debmake.1.ps

Please let me know if you have any questions or comments.

Thank you,


Paul Hardy


debmake.1.patch.sig
Description: PGP signature
--- debmake.1	2018-07-10 06:11:11.0 -0700
+++ debmake-new.1	2018-07-21 12:36:59.495053451 -0700
@@ -28,13 +28,13 @@
 .\" * MAIN CONTENT STARTS HERE *
 .\" -
 .SH "NAME"
-debmake \- program to make the Debian source package
+debmake \- program to make a Debian source package
 .SH "SYNOPSIS"
 .sp
-\fBdebmake\fR [\fB\-h\fR] [\fB\-c\fR | \fB\-k\fR] [\fB\-n\fR | \fB\-a\fR \fIpackage\-version\fR\fB\&.orig\&.tar\&.gz\fR | \fB\-d\fR | \fB\-t\fR ] [\fB\-p\fR \fIpackage\fR] [\fB\-u\fR \fIversion\fR] [\fB\-r\fR \fIrevision\fR] [\fB\-z\fR \fIextension\fR] [\fB\-b\fR "\fIbinarypackage\fR\fI, \&...\fR]" [\fB\-e\fR \fIfoo@example\&.org\fR] [\fB\-f\fR "\fIfirstname lastname\fR"] [\fB\-i\fR "\fIbuildtool\fR" | \fB\-j\fR] [\fB\-l\fR \fIlicense_file\fR] [\fB\-m\fR] [\fB\-o\fR \fIfile\fR] [\fB\-q\fR] [\fB\-s\fR] [\fB\-v\fR] [\fB\-w\fR "\fIaddon, \&...\fR"] [\fB\-x\fR [01234]] [\fB\-y\fR] [\fB\-L\fR] [\fB\-P\fR] [\fB\-T\fR]
+\fBdebmake\fR [\fB\-h\fR] [\fB\-c\fR | \fB\-k\fR] [\fB\-n\fR | \fB\-a\fR \fIpackage\-version\fR\fB\&.orig\&.tar\&.gz\fR | \fB\-d\fR | \fB\-t\fR ] [\fB\-p\fR \fIpackage\fR] [\fB\-u\fR \fIversion\fR] [\fB\-r\fR \fIrevision\fR] [\fB\-z\fR \fIextension\fR] [\fB\-b\fR "\fIbinarypackage\fR\fI, \&\|.\|.\|.\fR]" [\fB\-e\fR \fIfoo@example\&.org\fR] [\fB\-f\fR "\fIfirstname lastname\fR"] [\fB\-i\fR "\fIbuildtool\fR" | \fB\-j\fR] [\fB\-l\fR \fIlicense_file\fR] [\fB\-m\fR] [\fB\-o\fR \fIfile\fR] [\fB\-q\fR] [\fB\-s\fR] [\fB\-v\fR] [\fB\-w\fR "\fIaddon, \&\|.\|.\|.\fR"] [\fB\-x\fR [01234]] [\fB\-y\fR] [\fB\-L\fR] [\fB\-P\fR] [\fB\-T\fR]
 .SH "DESCRIPTION"
 .sp
-\fBdebmake\fR helps to build the Debian package from the upstream source\&. Normally, this is done as follows:
+\fBdebmake\fR helps to build a Debian package from the upstream source\&. Normally, this is done as follows:
 .sp
 .RS 4
 .ie n \{\
@@ -57,7 +57,7 @@
 .sp -1
 .IP \(bu 2.3
 .\}
-It is untared to create 

Bug#904218: ITP: nextepc -- Implementation of the Evolved Packet Core for LTE (4G)

[Ruben Undheim]

Package: wnpp
Owner: Ruben Undheim 
Severity: wishlist

* Package name: nextepc
  Version : 1.2.1
  Upstream Author : Sukchan Lee (acetcom)
* URL : http://nextepc.org/
* License : AGPL-3+
  Programming Lang: C
  Description : Implementation of the Evolved Packet Core for LTE (4G)

nextepc is an implementation of the infrastructure for a 4G cellular
network. This
infrastructure is called the "Evolved Packet Core".
It is similar to packages such as openbsc, osmo-bsc, osmo-msc for 2G (3G).

It will be maintained in the Debian Mobcom team.

Bug#889056: [update] Re: Bug#889056: replace apache-mode.el with elpa package

[Nicholas D Steeves]

On Wed, Jul 04, 2018 at 07:08:26AM -0300, David Bremner wrote:
> Nicholas D Steeves  writes:
> 
> > https://github.com/martenjj/apachemode is also by Jonathan Marten
> >   - Notes that it merges the features of three forks back into the
> > original.
> > https://github.com/emacs-php/apache-mode/ is a fork by Karl Chen, and
> > I wonder if it would be as smooth of a transition.  The fork would
> > be new to Debian...
> >
> > At any rate, the RFC: Do we want the version by the original author,
> > which merges the features from three forks, or do we want the version
> > on MELPA.  If necessary, I'd be happy to contact Jonathan Marten to
> > ask him if he would be willing to push his package to MELPA.
> 
> Being on melpa is not a prerequisite for being in Debian, as long as the
> upstream seems maintained.
> 
> I don't use apache so I can't really comment on the merits of the two
> modes. I do notice that the emacs-php one has tags, and is more recently
> active (2017 vs 2016). So I guess go for that one if you don't find a
> better way to break the tie.

https://github.com/martenjj/apachemode
 + original author
 + merges features from three forks
 + has a LICENSE file
 + has an issue tracker
 + easier to extend by patching keyword lists--CSVs

https://github.com/emacs-php/apache-mode/
 + more up-to-date
 + tags releases
 + could also become the version people come to expect, because it's
   on MELPA
 - no description or documentation beyond the short description
   and a code snippet for how to auto-enable the mode.

Ftpmasters would prefer martenjj's copy, because it has a LICENSE
file.  I've filed an upstream issue to investigate if martenjj would be
willing to tag a stable release, and reveal plans for future updates:
  https://github.com/martenjj/apachemode/issues/1

and have emailed Karl Chen (CCed our list) to address the issues on
his copy.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#794410: Installer hangs during 'select and install software'

[Jean-Louis Deniest]

Hello, I have the same issue.

Installing debian 9 stretch, both cd (debian-9.5.0-amd64-xfce-CD-1.iso) 
and the dvd versions.


Hangs at 12% : at the phase of installing "discover (amd64)"

I tried about 10 times.

Laptop is Packard Bell ENLG71BM-C05U

I used the additional drivers (from 
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/stretch/20180714/), 
and I put these .deb packages on another usb key : the effect is that I 
don't have the step where they search for firmware for 
rtlwifi/rtl8723befw.bin and rtl_nic/rtl8168g-2.fw


I don't have options to disable APCI in the bios.

I managed to install Opensuse on this computer, and there was Windows 10 
working properly.


Any suggestion is welcome...

Bug#904216: ITP: fuse3 -- Filesystem in Userspace (3.x version)

[Laszlo Boszormenyi (GCS)]

Package: wnpp
Severity: wishlist
Owner: Laszlo Boszormenyi (GCS) 

* Package name: fuse3
  Version : 3.2.4
  Upstream Author : Nikolaus Rath 
* URL : https://github.com/libfuse/libfuse/wiki
* License : GPL-2, LGPL-2.1
  Programming Lang: C
  Description : Filesystem in Userspace (3.x version)

 Filesystem in Userspace (FUSE) is a simple interface for userspace
 programs to export a virtual filesystem to the Linux kernel. It also
 aims to provide a secure method for non privileged users to create
 and mount their own filesystem implementations.

Bug#904215: civicrm: CIVI-SA-2018-07: Remote Code Execution in Quickform

[Salvatore Bonaccorso]

Source: civicrm
Version: 4.7.30+dfsg-1
Severity: grave
Tags: security upstream
Control: fixed -1 5.3.1+dfsg-1

https://civicrm.org/advisory/civi-sa-2018-07-remote-code-execution-in-quickform

This is already fixed, so this bug is to track the issue in the BTS.
No CVEs seem to be assigned for the CIVI advisories.

Speaking of that, might you convince upstream to request CVE
identifiers when they plan to release a CiviCRM security advisory?

Regards,
Salvatore

Bug#904164: Text of some PDF invisible: some font thing failed

[Jason Crain]

On Sat, Jul 21, 2018 at 07:31:51PM +0200, Mathias Brodala wrote:
> Jason Crain schrieb am 21.07.2018 um 01:03:
> > What version of poppler and cairo are you using?
> 
> Currently installed are libpoppler74 (0.63.0-2) and libcairo2 (1.15.10-3).

That's weird because it's working fine for me using those versions.

How does it look if you run `pdftocairo -png in.pdf out` to convert to
png images? pdftocairo is in the poppler-utils package. Evince uses
poppler for PDF rendering so that should get the same result as Evince.

Is there some reason Evince would not be able to read font files, like
maybe you've moved them out of /usr/share/fonts?

AppArmor sometimes causes issues so try temporarily disabling apparmor
with `aa-disable /etc/apparmor.d/usr.bin.evince`. aa-disable is in the
apparmor-utils package.

Bug#889075: ITP: qt5-engines-kvantum -- SVG-based theme engine for Qt5

[Alf Gaida]

Btw: https://github.com/tsujan/Kvantum/issues/229

Bug#884073: ITA: libical3 -- iCalendar library implementation in C

[Nicolas Mora]

signature.asc
Description: OpenPGP digital signature

Bug#879863: developer-reference conflicts with Policy on priority "extra" vs "optional"

[Nicholas D Steeves]

Control: retitle -1 developer-reference conflicts with Policy on priority 
"extra" vs "optional"
Control: severity -1 important
Control: tags -1 patch

Merge request filed here:
  https://salsa.debian.org/debian/developers-reference/merge_requests/1

Bumping priority because it contradicts a "should" directive in Policy
§2.5.


signature.asc
Description: PGP signature

Bug#884073: ITA: libical -- iCalendar library implementation in C (development)

[Nicolas Mora]

signature.asc
Description: OpenPGP digital signature

Bug#889075: ITP: qt5-engines-kvantum -- SVG-based theme engine for Qt5

[Alf Gaida]

Hi Franciscarlos,

the packaging is almost finsished - the only thing needed is a new
release. There was a lot of changes lately, some kind of polishing and
introduce the first translations - thats the only reason why it took so
long. Will talk with tsujan about tagging a new release.

We can co-maintain the package, let's talk about in OFTC #debian-lxqt

Cheers Alf

Bug#904214: zoneminder: After last zoneminder upgrade, it doesn't start anymore

[BERTRAND Joël]

Package: zoneminder
Version: 1.30.4+dfsg1-4
Severity: important

Dear Maintainer,

I use Zoneminder for a long time. My first installation was a clean installation
without debian package as zoneminder wasn't packaged, but since debian team
has provided deb package, I use it.

Thus I have reinstall my zoneminder server with debian Buster. This server
ran without any trouble during several months. Last week, I have done a
dist-upgrade and I have seen that zoneminder was upgraded.

I have rebooted my server this afternoon and zoneminder refuses to start.

Logs :
2018-07-21 20:03:05.330840 zmwatch  4680 INF Restarting capture daemon for Rue, 
shared data not valid zmwatch.pl
2018-07-21 20:03:05.329790 zmwatch  4680 ERR Memory map file 
'/dev/shm/zm.mmap.2' does not exist. zmc might not be running. zmwatch.pl
2018-07-21 20:02:49.239550 zmdc  4634 ERR 'zma -m 2' exited abnormally, exit 
status 255 zmdc.pl
2018-07-21 20:02:49.236504 undef  4708 ERR Attempt to fetch boolean value for 
ZM_WEB_EVENT_DISK_SPACE, actual type is string. Try running 'zmupdate.pl -f' to 
reload config. zm_config.cpp 204
2018-07-21 20:02:49.230420 zmdc  4634 ERR 'zmc -d /dev/video0' exited 
abnormally, exit status 255 zmdc.pl
2018-07-21 20:02:49.227190 undef  4707 ERR Attempt to fetch boolean value for 
ZM_WEB_EVENT_DISK_SPACE, actual type is string. Try running 'zmupdate.pl -f' to 
reload config. zm_config.cpp 204
2018-07-21 20:02:49.029600 zmdc  4708 INF 'zma -m 2' started at 18/07/21 
20:02:49 zmdc.pl
2018-07-21 20:02:49.028660 zmdc  4634 INF 'zma -m 2' starting at 18/07/21 
20:02:49, pid = 4708 zmdc.pl
2018-07-21 20:02:49.025030 zmdc  4634 INF Starting pending process, zma -m 2 
zmdc.pl
2018-07-21 20:02:49.023730 zmdc  4707 INF 'zmc -d /dev/video0' started at 
18/07/21 20:02:49 zmdc.pl
2018-07-21 20:02:49.023720 zmdc  4634 INF 'zmc -d /dev/video0' starting at 
18/07/21 20:02:49, pid = 4707 zmdc.pl
2018-07-21 20:02:49.018660 zmdc  4634 INF Starting pending process, zmc -d 
/dev/video0 zmdc.pl
2018-07-21 20:02:39.205110 zmdc  4634 ERR 'zma -m 2' exited abnormally, exit 
status 255 zmdc.pl
2018-07-21 20:02:39.201951 undef  4705 ERR Attempt to fetch boolean value for 
ZM_WEB_EVENT_DISK_SPACE, actual type is string. Try running 'zmupdate.pl -f' to 
reload config. zm_config.cpp 204
2018-07-21 20:02:39.198070 zmdc  4634 ERR 'zmc -d /dev/video0' exited 
abnormally, exit status 255 zmdc.pl
2018-07-21 20:02:39.194731 undef  4704 ERR Attempt to fetch boolean value for 
ZM_WEB_EVENT_DISK_SPACE, actual type is string. Try running 'zmupdate.pl -f' to 
reload config. zm_config.cpp 204

Shared memory segment is not created as zmc -d /dev/video0 aborts without
any message (maybe 'Attempt to fetch boolean value for ZM_WEB_EVENT_DISK_SPACE'
is related to this bug but I'm not sure, I have tried to modify this parameter
without success).

Faulty package is 1.30.4+dfsg1-4. On a second server that runs Debian/Buster
and zoneminder 1.30.4+dfsg-2+b2, I haven't this kind of trouble.

Best regards,

JB

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

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

Versions of packages zoneminder depends on:
ii  cakephp 2.10.11-2
ii  fonts-glewlwyd  1.4.4-3
ii  javascript-common   11
ii  libarchive-zip-perl 1.60-1
ii  libavcodec577:3.4.3-1
ii  libavformat57   7:3.4.3-1
ii  libavutil55 7:3.4.3-1
ii  libc6   2.27-3
ii  libclass-std-fast-perl  0.0.8-2
ii  libcurl3-gnutls 7.60.0-2
ii  libdata-dump-perl   1.23-1
ii  libdate-manip-perl  6.72-1
ii  libdbd-mysql-perl   4.046-1
ii  libdevice-serialport-perl   1.04-3+b5
pn  libdigest-sha-perl  
ii  libgcc1 1:8.1.0-10
ii  libgcrypt20 1.8.3-1
ii  libgnutls-openssl27 3.5.18-1
ii  libimage-info-perl  1.41-1
ii  libio-socket-multicast-perl 1.12-2+b4
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libjson-any-perl1.39-1
ii  libmariadbclient18  1:10.1.29-6+b1
ii  libmime-lite-perl   3.030-2
ii  libmime-tools-perl  5.509-1
ii  libnet-sftp-foreign-perl1.89+dfsg-1
ii  

Bug#904213: stretch-pu: package libclamunrar/0.99-3+deb9u1

[Sebastian Andrzej Siewior]

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

This is my proposed update libclamunrar in Stretch. I updated from old
version + patches to the latest clamav release and was able to drop all
patches. The changelog for 0.100.1 stated:

  Buffer over-read in unRAR code due to missing max value checks in table
  initialization. Reported by Rui Reis.

I don't know if this "just" an over read and nothing bad happens or if a
segfault is possible. The 0.100.0 changelog did not state any unrar
related changes but they made a few changes with no explanation. I feel
more comfortable to sychnronize with latest version as released by
clamav.

Please find a debdiff attached which has the autoconf and m4 changes
removed.

Sebastian
diff --git a/configure.ac b/configure.ac
index 85aa6a7604e1..4994c10e66f1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -20,7 +20,7 @@ dnl   MA 02110-1301, USA.
 AC_PREREQ([2.59])
 dnl For a release change [devel] to the real version [0.xy]
 dnl also change VERSION below
-AC_INIT([ClamAV], [0.99], [http://bugs.clamav.net/], [clamav], [http://www.clamav.net/])
+AC_INIT([ClamAV], [0.100.1], [https://bugzilla.clamav.net/], [clamav], [https://www.clamav.net/])
 
 AH_BOTTOM([#include "platform.h"])
 dnl put configure auxiliary into config
@@ -74,6 +74,7 @@ m4_include([m4/reorganization/code_checks/coverage.m4])
 
 dnl libclamav dependencies
 m4_include([m4/reorganization/libs/xml.m4])
+m4_include([m4/reorganization/libs/openssl.m4])
 m4_include([m4/reorganization/libs/json.m4])
 m4_include([m4/reorganization/libs/pcre.m4])
 
@@ -81,6 +82,7 @@ AM_MAINTAINER_MODE
 m4_include([m4/reorganization/libs/libz.m4])
 m4_include([m4/reorganization/libs/bzip.m4])
 m4_include([m4/reorganization/libs/unrar.m4])
+m4_include([m4/reorganization/libs/systemd.m4])
 m4_include([m4/reorganization/code_checks/ipv6.m4])
 m4_include([m4/reorganization/code_checks/dns.m4])
 m4_include([m4/reorganization/code_checks/fanotify.m4])
@@ -115,18 +117,26 @@ m4_include([m4/reorganization/code_checks/shift.m4])
 m4_include([m4/reorganization/code_checks/features.m4])
 m4_include([m4/reorganization/clamdtop.m4])
 m4_include([m4/reorganization/distcheck.m4])
-m4_include([m4/reorganization/llvm.m4])
 m4_include([m4/reorganization/sha_collect.m4])
 m4_include([m4/reorganization/yara.m4])
-
+m4_include([m4/reorganization/code_checks/fts.m4])
+m4_include([m4/reorganization/libfreshclam.m4])
+m4_include([m4/reorganization/prelude.m4])
 m4_include([m4/reorganization/bsd.m4])
 
 dnl Freshclam dependencies
 m4_include([m4/reorganization/libs/curl.m4])
-
 m4_include([m4/reorganization/substitutions.m4])
+m4_include([m4/reorganization/strni.m4])
+
+if test "x$use_internal_mspack" = "xyes"; then
+mspack_msg="Internal"
+AC_CONFIG_SUBDIRS([libclamav/libmspack-0.5alpha])
+AC_SYS_LARGEFILE
+else
+mspack_msg="External, $LIBMSPACK_CFLAGS $LIBMSPACK_LIBS"
+fi
 
-AM_CONDITIONAL([ENABLE_CLAMSUBMIT], [test "$have_curl" = "yes"])
 
 AC_CONFIG_FILES([
 libclamunrar_iface/Makefile
@@ -148,6 +158,8 @@ AM_CONDITIONAL([ENABLE_LLVM],
 	   [test "$subdirfailed" != "yes" && test "$enable_llvm" != "no"])
 AM_CONDITIONAL([ENABLE_YARA],
 	   [test "$enable_yara" != "no"])
+AM_CONDITIONAL([ENABLE_CLAMSUBMIT],
+	   [test "X$have_curl" = "Xyes" && test "X$have_json" = "Xyes"])
 no_recursion="yes";
 
 
@@ -166,7 +178,7 @@ else
 check_libs="$CHECK_LIBS"
 fi
 CL_MSG_STATUS([check   ],[$check_libs],[$enable_check_ut])
-CL_MSG_STATUS([fanotify],[$want_fanotify],[$want_fanotify])
+CL_MSG_STATUS([fanotify],[$have_fanotify],[$have_fanotify])
 if test "x$ac_cv_have_control_in_msghdr" = "xyes"; then
 CL_MSG_STATUS([fdpassing   ],[$have_fdpass],[$want_fdpassing])
 else
@@ -177,7 +189,19 @@ CL_MSG_STATUS([IPv6],[$have_cv_ipv6],[$want_ipv6])
 AC_MSG_NOTICE([Summary of optional tools])
 CL_MSG_STATUS([clamdtop],[$CURSES_LIBS],[$enable_clamdtop])
 CL_MSG_STATUS([milter  ],[yes],[$have_milter])
-CL_MSG_STATUS([clamsubmit  ],[$have_curl],[$curl_msg])
+if test "X$have_curl" = "Xyes" && test "X$have_json" = "Xyes"; then
+CL_MSG_STATUS([clamsubmit  ], [yes (libjson-c-dev found at $LIBJSON_HOME), libcurl-devel found at $LIBCURL_HOME)], [yes])
+else
+if test "X$have_curl" != "Xyes" && test "X$have_json" != "Xyes"; then
+CL_MSG_STATUS([clamsubmit  ], [no (missing libjson-c-dev AND libcurl-devel. Use the website to submit FPs/FNs.)], [no])
+else
+if test "X$have_curl" = "Xyes"; then 
+CL_MSG_STATUS([clamsubmit  ], [no (missing libjson-c-dev. Use the website to submit FPs/FNs.)], [no])
+else
+CL_MSG_STATUS([clamsubmit  ], [no (missing libcurl-devel. Use the website to submit FPs/FNs.)], [no])
+fi
+fi
+fi
 
 AC_MSG_NOTICE([Summary of engine performance features])
 if test "x$enable_debug" = "xyes"; then
@@ -189,10 +213,12 @@ have_jit="no"
 if test "$subdirfailed" = "no"; then
 

Bug#810608: systemd-sysv: on shutdown, fails to inform users that the system is going down

[Francesco Poli]

On Sat, 21 Jul 2018 01:21:52 +0200 Michael Biebl wrote:

[...]
> For remote logins, it might be useful.

Exactly: it is useful to figure out why your SSH connection got closed...

> 
> Anyway, iff you want to see this behaviour changed for non-delayed
> reboot/poweroff, feel free to raise this issue upstream at
> https://github.com/systemd/systemd.

I do not have a github account.
Could you please forward my bug report upstream?

Thanks for your time and understanding.

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


pgpwGCdo1Yokm.pgp
Description: PGP signature

Bug#902449: cryptsetup-initramfs: auto-detection of zfs pool(s)

[Guilhem Moulin]

Hi,

On Sat, 21 Jul 2018 at 19:27:54 +0200, Michal Humpula wrote:
> Since the ZFS is not strictly speaking alien in Debian (it's in
> contrib, though), it would be nice if cryptsetup-initramfs would
> support it.

Just to be clear, it's only *auto-detection* that's not supported.  It's
still possible to format your root device as ZFS (or any other file
system) held by encrypted disks.  Adding the ‘initramfs’ option to the
crypttab(5) entries for the underlying devices should do the trick, cf.
https://bugs.debian.org/820888#32 .

> So, any other ideas how to integrate the ZFS support?

Not beside parsing `zpool`'s output, which I'm afraid I still object to.

That being said, I don't mind implementing an option to silence the
warning that the root FS can't be found.  At least since 2:2.0.3-5 there
should be only one warning (like with ≤2:2.0.3-1), cf.
https://bugs.debian.org/902449#21 .

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#903969:

[John Scott]

reassign 903969 python3-reportbug
tags 903969 patch
thanks

Here's a merge request.
https://salsa.debian.org/reportbug-team/reportbug/merge_requests/4

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

Bug#904211: Please switch to pybuild

[Picca Frédéric-Emmanuel]

Package: cython
Version: 0.28.2-4
Severity: wishlist

Hello,

It would be great if cython could use pybuild. It seems to me that it
should ease the packaging and avoid these -dbg issues.

thanks for considering.

Frederic


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

Kernel: Linux 4.17.0-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cython depends on:
ii  libc6   2.27-5
ii  python  2.7.15-3

Versions of packages cython recommends:
ii  gcc 4:8.1.0-1
ii  python-dev  2.7.15-3

Versions of packages cython suggests:
pn  cython-doc  

-- no debconf information

Bug#904212: bluez: Consider adding details to change the default "Name" of device in bluetooth/main.conf

[Sébastien Grenier]

Package: bluez
Version: 5.49-4
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
 I was trying to change the default name of the device.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I edited the bluetooth/main.conf under the variable "Name ="

   * What was the outcome of this action?
 No change resulted after the restart of the service.

   * What outcome did you expect instead?
 That the new name became effective.

Please consider adding more details to guide the user in changing the default 
name of device.
By default the name the of device is not BlueZ X.YZ when the hostname plugin is 
loaded. The variable PRETTY_HOSTNAME is a resonable option for user but they 
have to know where to configure it. So if you add the following lines above the 
"Name = Bluez" in /etc/bluetooth/main.conf that would clarify the situation.

# Defaults to 'BlueZ X.YZ', if Name is not set here and plugin 'hostname' is 
not loaded.
# The plugin 'hostname' is loaded by default and overides the Name set here so
# consider modifying /etc/machine-info with variable PRETTY_HOSTNAME= 
instead.
#Name = BlueZ




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

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

Versions of packages bluez depends on:
ii  dbus  1.12.8-3
ii  kmod  25-1
ii  libasound21.1.6-1
ii  libc6 2.27-3
ii  libdbus-1-3   1.12.8-3
ii  libdw10.170-0.5
ii  libglib2.0-0  2.56.1-2
ii  libreadline7  7.0-5
ii  libudev1  239-5
ii  lsb-base  9.20170808
ii  udev  239-5

bluez recommends no packages.

Versions of packages bluez suggests:
ii  pulseaudio-module-bluetooth  11.1-5

-- Configuration Files:
/etc/bluetooth/main.conf changed:
[General]
Name = BoomBoom
Class = 0x000100
DiscoverableTimeout = 0
PairableTimeout = 0
[GATT]
[Policy]
AutoEnable=true


-- no debconf information

Bug#895345: https://salsa.debian.org/electronics-team/sdcc.git

[Geert Stappers]

There is now an empty git repository
at https://salsa.debian.org/electronics-team/sdcc.git
which is intended for Debian packaging of sdcc


Convenience links for the both bugreports in the To:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895345
 Title:  sdcc recent git repository

and

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897856
 Title: sdcc: ftbfs with GCC-8


Explanation of the people in the Cc:

 - Gudjon,  maintainer of sdcc
 - Bdale, uploader of sdcc
 - Tobias, wrote a patch that fixed a recent sdcc bug
( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894619#12 )
 - Adrian Bunk, did the upload of  -2.1


My hope is that they have content for sdcc packaging git repository.


Cheers
Geert Stappers
Who loves to see that sigrok stays in testing. sigrok depends on sdcc

Bug#904164: Text of some PDF invisible: some font thing failed

[Mathias Brodala]

Hi,

Jason Crain schrieb am 21.07.2018 um 01:03:

On Sat, Jul 21, 2018 at 12:22:47AM +0200, Mathias Brodala wrote:

today I noticed that Evince suddenly fails to render some PDF files properly
which however worked fine before. When launching from a terminal there are a
lot of lines repeated like this:


some font thing failed


Take the attached PDF as an example whose text is invisible (but can be
selected and copied) in Evince. The rendering is fine in Chromium however.


What version of poppler and cairo are you using?


Currently installed are libpoppler74 (0.63.0-2) and libcairo2 (1.15.10-3).

Please let me know if you need something else/specific.

Regards, Mathias

Bug#902449: cryptsetup-initramfs: auto-detection of zfs pool(s)

[Michal Humpula]

Hi Guilhem,

I may have found the answer to the question, why there is still no sysfs 
interface for the ZFS. Kernel object representing the `/sys/fs` directory is 
exported as GPL only, so it's not possible to use it in non GPL module, which 
unfortunately ZFS is (CDDL).

Since the ZFS is not strictly speaking alien in Debian (it's in contrib, 
though), it would be nice if cryptsetup-initramfs would support it. So, any 
other ideas how to integrate the ZFS support?

Cheers
Michal

Bug#840075: How to help getting libfuse updated?

[GCS]

Hi,

On Wed, Jun 27, 2018 at 1:09 PM Nikolaus Rath  wrote:
> > > Please let me know if there is anything I can do.
> >
> > I've a bug report and a feature request. Will post it on your Git 
> > repository.
>
> Are you still working on this, or am I looking in the wrong place for it? I 
> checked https://github.com/libfuse/libfuse/issues.
 Sent a pull request and you merged most of the changes already.
Package update is available[1], but not yet uploaded. I'll do it
tomorrow, after filing the ITP for the separate fuse3 source. Tested
that the library and development packages can be co-installed with the
2.9.7 version of fuse. Builds on amd64 and i386, other architectures
not yet checked.
Some dependent packages don't use pkg-config but include files
directly, those fail building with fuse3 - but otherwise it seems to
be API compatible with the 2.x version.

Cheers,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/fuse3_3.2.4-1.dsc

Bug#902817: fail2ban: SyntaxError when run with python3.7

[Andrey Rahmatullin]

Note that the bug title is misleading as the package cannot be installed
if python3.7 is installed, even though python3.7 is not the default
python3 yet.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#904052: ffmpeg: FTBFS on hurd-i386: wrong value for --target-os at configure

[James Cowgill]

Hi,

On 18/07/18 22:18, Pino Toscano wrote:
> Source: ffmpeg
> Version: 7:4.0-3
> Severity: important
> Tags: patch
> User: debian-h...@lists.debian.org
> Usertags: hurd
> 
> Hi,
> 
> ffmpeg fails to build on hurd-i386 [1].
> 
> Since version 7:4.0-3 (commit d3d378eb963734f2d330754300a63eb440f2d676
> in the packaging Git) --target-os is passed in all the cases to
> configure, using $DEB_HOST_ARCH_OS as value.  The problem is that
> configure expects for --target-os a (lowercase) value among the
> possible ones returned by `uname -s`, which is "GNU" for Hurd.  OTOH,
> $DEB_HOST_ARCH for hurd-* archs is "hurd", and thus configure fails
> with "Unknown OS".
> 
> Attached there is a patch to use a custom variable for --target-os,
> using the mapping needed (so far for hurd-* only).

I think I'll just move the --target-os option back into the cross
compilation block which will at least fix the native build. In the above
commit it was only the --arch option which was important to always specify.

Maybe upstream FFmpeg could be taught to accept "hurd" as an alternate
name for "gnu" in --target-os?

Jame



signature.asc
Description: OpenPGP digital signature

Bug#904052: ffmpeg: FTBFS on hurd-i386: wrong value for --target-os at configure

[James Cowgill]

Hi,

On 21/07/18 17:26, Pino Toscano wrote:
> In data sabato 21 luglio 2018 17:59:13 CEST, James Cowgill ha scritto:
>> Maybe upstream FFmpeg could be taught to accept "hurd" as an alternate
>> name for "gnu" in --target-os?
> 
> I'm not sure about this: since the default value is taken from the
> output of $(uname -s), that returns "GNU" and not "hurd". I'd be like
> adding eg "gnulinux" as alternate name for "linux", which IMHO does not
> make sense.

I'm asking on the basis that upstream FFmpeg already accepts Debian's
architecture names in the --arch option (even though they're different
to the output of uname -m). It would be nice if it also accept Debian's
architecture names for --target-os as well.

James



signature.asc
Description: OpenPGP digital signature

Bug#904210: restrictedpython: autopkgtest regression: probably missing test depends python3-all

[Paul Gevers]

Source: restrictedpython
Version: 4.0~b3-1
User: debian...@lists.debian.org
Usertags: needs-update

Dear maintainers,

Currently the python3.7 transition¹ is going on, which means that
python3.7 is added to the supported python3 versions. However, since
python3-defaults added python3.7 support, your autopkgtest has been
failing. I copied the error below.

Could you please investigate? I think you want to test depend on
python3-all.

Paul

¹ https://release.debian.org/transitions/html/python3.7.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/restrictedpython/644589/log.gz

autopkgtest [04:42:26]: test all: [---
/usr/share/python3-zope.testrunner/test_helper_3: line 17: python3.7:
command not found
autopkgtest [04:42:26]: test all: ---]



signature.asc
Description: OpenPGP digital signature

Bug#904052: ffmpeg: FTBFS on hurd-i386: wrong value for --target-os at configure

[Pino Toscano]

In data sabato 21 luglio 2018 17:59:13 CEST, James Cowgill ha scritto:
> Hi,
> 
> On 18/07/18 22:18, Pino Toscano wrote:
> > Source: ffmpeg
> > Version: 7:4.0-3
> > Severity: important
> > Tags: patch
> > User: debian-h...@lists.debian.org
> > Usertags: hurd
> > 
> > Hi,
> > 
> > ffmpeg fails to build on hurd-i386 [1].
> > 
> > Since version 7:4.0-3 (commit d3d378eb963734f2d330754300a63eb440f2d676
> > in the packaging Git) --target-os is passed in all the cases to
> > configure, using $DEB_HOST_ARCH_OS as value.  The problem is that
> > configure expects for --target-os a (lowercase) value among the
> > possible ones returned by `uname -s`, which is "GNU" for Hurd.  OTOH,
> > $DEB_HOST_ARCH for hurd-* archs is "hurd", and thus configure fails
> > with "Unknown OS".
> > 
> > Attached there is a patch to use a custom variable for --target-os,
> > using the mapping needed (so far for hurd-* only).
> 
> I think I'll just move the --target-os option back into the cross
> compilation block which will at least fix the native build. In the above
> commit it was only the --arch option which was important to always specify.

OK, thanks -- this solution LGTM.

> Maybe upstream FFmpeg could be taught to accept "hurd" as an alternate
> name for "gnu" in --target-os?

I'm not sure about this: since the default value is taken from the
output of $(uname -s), that returns "GNU" and not "hurd". I'd be like
adding eg "gnulinux" as alternate name for "linux", which IMHO does not
make sense.

-- 
Pino Toscano

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

Bug#897852: [Rsbackup-maint] Bug#897852: rsbackup: ftbfs with GCC-8

[Richard Kettlewell]

On 2018-07-21 13:56, Matthew Vernon wrote:
> On 21/07/18 13:22, Richard Kettlewell wrote:
>> In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897852:
>>> I think this is a pangomm bug - see the errors below about incompatible
>>> function type casts.
>>
>> To me it looks like a sigc++ bug, and one that is being addressed
>> upstream:
>>
>> https://github.com/libsigcplusplus/libsigcplusplus/issues/1
> 
> Yes, I'd forgotten I'd already cloned this bug and assigned the clone
> appropriately; I've added this link to that blocking bug ( 897895 ).

https://github.com/ewxrjk/rsbackup/issues/47 has a patch now.

ttfn/rjk

Bug#889075: ITP: qt5-engines-kvantum -- SVG-based theme engine for Qt5

[Franciscarlos Santos Soares]

Hi Alf Gaida,

A few months ago you filed a ITP bug, stating that you intended to
package the qt5-engines-kvantum.

As far as I can see, this hasn't happened yet.

Adapta-kde, a package I'm releasing now and depends on kavantum, then I
already packaged it because I needed it for my project.

I think it would make sense upload the package I have ready.
You are of course welcome to collaborate with me.

What do you think?

-- 

Att,
*prof. Franciscarlos Soares*
prof.franciscar...@gmail.com
CEIN Raimundo Araújo
CE Dr. Otávio Vieira Passos
Chapadinha - Ma
Currículo Lattes/CNPq:
http://lattes.cnpq.br/3288394995423768

Bug#904178: ffmpeg: fix mips r6 build

[James Cowgill]

Control: notfound -1 4.0.1-2
Control: found -1 7:4.0.1-2

Hi Yunqiang,

On 21/07/18 05:46, YunQiang Su wrote:
> Package: src:ffmpeg
> Version: 4.0.1-2
> 
> We are working on MIPS r6 ports.
> 
> Please change the lines about mips options in debian/rules to the below.
> # Disable some optimizations on mips*, because they are not always
> available on these architectures
> ifneq (,$(filter mips%r6 mips%r6el, $(DEB_HOST_ARCH)))
> MIPS_NO_R6_OPTION = --disable-mips32r2 \
> --disable-mips64r2 \
> --disable-mips32r5

Is this line intentional (given that --disable-mips32r5 is used below as
well)?

I don't think the name of that variable explains itself very well,
especially since one of the options enables R6. Maybe MIPS_R2_R6_CONFIG
is better?

James



signature.asc
Description: OpenPGP digital signature

Bug#904178: ffmpeg: fix mips r6 build

[YunQiang Su]

James Cowgill  于2018年7月21日周六 下午11:43写道：
>
> Hi,
>
> On 21/07/18 16:38, YunQiang Su wrote:
> > James Cowgill  于2018年7月21日周六 下午11:16写道：
> >> On 21/07/18 05:46, YunQiang Su wrote:
> >>> Please change the lines about mips options in debian/rules to the below.
> >>> # Disable some optimizations on mips*, because they are not always
> >>> available on these architectures
> >>> ifneq (,$(filter mips%r6 mips%r6el, $(DEB_HOST_ARCH)))
> >>> MIPS_NO_R6_OPTION = --disable-mips32r2 \
> >>> --disable-mips64r2 \
> >>> --disable-mips32r5
> >>
> >> Is this line intentional (given that --disable-mips32r5 is used below as
> >> well)?
> >>
> >
> > yes. when the first try, I don't add --disable-mips32r5, then it
> > failed to build,
> > when link r2/r6 objects.
>
> I still don't understand. In your new code, the --disable-mips32r5
> option is passed unconditionally in the main config block so this extra
> option in the r6 block should have no effect.

Ohh. you are right.
The current version disable mips32r5 unconditionally, and I pass it
twice for r6.
So, just remove that line in the condition of r6 will be OK.

ifneq (,$(filter mips%r6 mips%r6el, $(DEB_HOST_ARCH)))
MIPS_NO_R6_OPTION = --disable-mips32r2 \
--disable-mips64r2
else
MIPS_NO_R6_OPTION = --disable-mips32r6 \
--disable-mips64r6
endif

ifneq (,$(filter mips%, $(DEB_HOST_ARCH)))
CONFIG += --disable-mipsdsp \
--disable-mipsdspr2 \
--disable-loongson2 \
--disable-loongson3 \
--disable-mmi \
--disable-mips32r5 \
$(MIPS_NO_R6_OPTION) \
--disable-msa
endif



>
> >> I don't think the name of that variable explains itself very well,
> >> especially since one of the options enables R6. Maybe MIPS_R2_R6_CONFIG
> >> is better?
>
> James
>


-- 
YunQiang Su

Bug#867886: (no subject)

[Víctor Cuadrado Juan]

reopen 867886
thanks

There it is again, reopening.


-- 
Víctor Cuadrado Juan   m...@viccuad.me

PGP key ID: 4096R: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature

Bug#904209: libsass1: libsass regression wrt @import

[Jan Matějka]

Package: libsass1
Version: 3.5.4-1
Severity: normal
Tags: upstream

Dear Maintainer,

libsass 3.5.3 introduced regression by removing support for @importing .css 
files [1] which broke
a widespread use case. With the community disgruntled, the change was reverted 
[2]. At the moment,
upstream releases >=3.5.3 are broken.

[1]: https://github.com/sass/libsass/pull/2615
[2]: https://github.com/sass/libsass/pull/2684


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable'), (40, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages libsass1 depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-10
ii  libstdc++6  8.1.0-10

libsass1 recommends no packages.

libsass1 suggests no packages.

-- no debconf information

Bug#904208: itop crashes when option -n is used

[sfahbj]

Package: itop
Version: 0.1-4+b2

running as "itop -n 1"  same as "itop -n 5" etc crashes it.

Also it leaves the terminal in a really fucked up state, when even "reset" 
command does not restore normal terminal behavior.


as root: itop -a -n 1   shows once the output then crashes:

INTNAME  RATE MAX
  0 [0  0  ] 0 Ints/s (max: 0)

readline: warning: turning off output flushing
  root@myhostname:~#

The fact that there are only zeroes shown is related to the other itop bug I 
just reported.
But on other machine the result is same, it once show the output, then crashes:


INTNAME  RATE MAX
  0 [   0  0   ] 0 Ints/s (max: 0)
  1 [   0  0   ] 0 Ints/s (max: 0)
  5 [   0  0   ] 0 Ints/s (max: 0)
  8 [   0  0   ] 0 Ints/s (max: 0)
  9 [   0  0   ] 0 Ints/s (max: 0)
 12 [   0  0   ] 0 Ints/s (max: 0)
 16 [8324  0   ] 0 Ints/s (max: 0)
 18 [   0  0   ] 0 Ints/s (max: 0)
 23 [   0  0   ] 0 Ints/s (max: 0)
 24 [   0  0   ] 0 Ints/s (max: 0)
 25 [1717  0   ] 0 Ints/s (max: 0)
 26 [7221  0   ] 0 Ints/s (max: 0)
 27 [   0   13131943   ] 0 Ints/s (max: 0)
 28 [8445  0   ] 0 Ints/s (max: 0)
 29 [6980  0   ] 0 Ints/s (max: 0)
 30 [   0  0   ] 0 Ints/s (max: 0)
 31 [   3  0   ] 0 Ints/s (max: 0)
 32 [   0  0   ] 0 Ints/s (max: 0)
 33 [   0  0   ] 0 Ints/s (max: 0)
 34 [   0  0   ] 0 Ints/s (max: 0)
 35 [   0  0   ] 0 Ints/s (max: 0)
 36 [6625   1439   ] 0 Ints/s (max: 0)
 37 [   0  0   ] 0 Ints/s (max: 0)

readline: warning: turning off output flushing
user@myhostname



also the output seems wrong (nonsense names of interrupts) which is another bug 
(good job, itop :)

Bug#904207: itop output names are nonsense

[sfahbj]

Package: itop
Version: 0.1-4+b2

on amd64 (smp)


The 3rd bug in itop I'm seeing now, on the computer where itop shows any 
interrupts at all, the output is messed up, as if the lines are wrongly parsed.


INT NAME RATE MAX
 0 [ 0 0 ] 0 Ints/s (max: 0)
 1 [ 0 0 ] 0 Ints/s (max: 0)
 5 [ 0 0 ] 0 Ints/s (max: 0)
 8 [ 0 0 ] 0 Ints/s (max: 0)
 9 [ 0 0 ] 0 Ints/s (max: 0)
12 [ 0 0 ] 0 Ints/s (max: 0)
16 [8324 0 ] 0 Ints/s (max: 0)
18 [ 0 0 ] 0 Ints/s (max: 0)
23 [ 0 0 ] 0 Ints/s (max: 0)
24 [ 0 0 ] 0 Ints/s (max: 0)
25 [1717 0 ] 0 Ints/s (max: 0)
26 [7221 0 ] 0 Ints/s (max: 0)
27 [ 0 13131943 ] 0 Ints/s (max: 0)
28 [8445 0 ] 0 Ints/s (max: 0)
29 [6980 0 ] 0 Ints/s (max: 0)
30 [ 0 0 ] 0 Ints/s (max: 0)
31 [ 3 0 ] 0 Ints/s (max: 0)
32 [ 0 0 ] 0 Ints/s (max: 0)
33 [ 0 0 ] 0 Ints/s (max: 0)
34 [ 0 0 ] 0 Ints/s (max: 0)
35 [ 0 0 ] 0 Ints/s (max: 0)
36 [6625 1439 ] 0 Ints/s (max: 0)
37 [ 0 0 ] 0 Ints/s (max: 0)

there is no NAME, and the RATE seems to be in the NAME column.

For comparsion, on this machine:

$ cat /proc/interrupts 
 CPU0 CPU1 CPU2 CPU3 
 0: 17 0 0 0 IO-APIC 2-edge timer
 1: 3 0 0 0 IO-APIC 1-edge i8042
 5: 0 0 0 0 IO-APIC 5-edge parport0
 8: 1 0 0 0 IO-APIC 8-edge rtc0
 9: 4 0 0 0 IO-APIC 9-fasteoi acpi
12: 4 0 0 0 IO-APIC 12-edge i8042
16: 103 3922 28324 0 IO-APIC 16-fasteoi ehci_hcd:usb1
18: 0 0 0 0 IO-APIC 18-fasteoi i801_smbus
23: 35 0 0 0 IO-APIC 23-fasteoi ehci_hcd:usb2
24: 0 0 0 0 PCI-MSI 458752-edge PCIe PME
25: 3 520 7571266 0 PCI-MSI 409600-edge enp0s25
26: 3217 0 87414 0 PCI-MSI 512000-edge ahci[:00:1f.2]
27: 4 0 0 13132729 PCI-MSI 524288-edge enp1s0f0[0]
28: 41520 0 868445 0 PCI-MSI 524289-edge enp1s0f0[1]
29: 42171 0 776980 0 PCI-MSI 524290-edge enp1s0f0[2]
30: 1 1 0 0 PCI-MSI 524291-edge enp1s0f0[3]
31: 4 0 3 0 PCI-MSI 526336-edge enp1s0f1[0]
32: 0 0 0 0 PCI-MSI 526337-edge enp1s0f1[1]
33: 0 0 0 0 PCI-MSI 526338-edge enp1s0f1[2]
34: 0 0 0 0 PCI-MSI 526339-edge enp1s0f1[3]
35: 19 0 0 0 PCI-MSI 360448-edge mei_me
36: 961 0 16625 1439 PCI-MSI 32768-edge i915
37: 443 421 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
NMI: 177 172 155 147 Non-maskable interrupts
LOC: 12787164 11707993 6734860 9371360 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 177 172 155 147 Performance monitoring interrupts
IWI: 2 0 0 0 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 297237 284693 237510 223174 Rescheduling interrupts
CAL: 60935 67982 57994 88198 Function call interrupts
TLB: 57223 63139 54516 82649 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 264 264 264 264 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 Posted-interrupt notification event
PIW: 0 0 0 0 Posted-interrupt wakeup event

Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

[James Cowgill]

Control: tags -1 - moreinfo

Hi,

On 21/07/18 16:23, Mattia Rizzolo wrote:
> On Sat, Jul 21, 2018 at 02:41:32PM +0100, James Cowgill wrote:
>> If versioned provides was working properly everywhere then
>> possibly it could be used, but I don't think it does yet (although I'm
>> happy to be corrected!).
> 
> They do.  In the past 2 years many bugs around the infrastructure were
> fixed and versioned provides can now be fully used (in particular, there
> were some last pieces regarding wanna-build and britney, that have been
> fixed ~1 year ago IIRC).
> 
> The only thing is that they may be confusing to some, as it's not so
> straightforward to find a virtual package compared to a plain `apt show`
> :>

OK thanks. I'll see what I can do about this after the ffmpeg 4.0
transition has completed.

James



signature.asc
Description: OpenPGP digital signature

Bug#904178: ffmpeg: fix mips r6 build

[James Cowgill]

Hi,

On 21/07/18 16:38, YunQiang Su wrote:
> James Cowgill  于2018年7月21日周六 下午11:16写道：
>> On 21/07/18 05:46, YunQiang Su wrote:
>>> Please change the lines about mips options in debian/rules to the below.
>>> # Disable some optimizations on mips*, because they are not always
>>> available on these architectures
>>> ifneq (,$(filter mips%r6 mips%r6el, $(DEB_HOST_ARCH)))
>>> MIPS_NO_R6_OPTION = --disable-mips32r2 \
>>> --disable-mips64r2 \
>>> --disable-mips32r5
>>
>> Is this line intentional (given that --disable-mips32r5 is used below as
>> well)?
>>
> 
> yes. when the first try, I don't add --disable-mips32r5, then it
> failed to build,
> when link r2/r6 objects.

I still don't understand. In your new code, the --disable-mips32r5
option is passed unconditionally in the main config block so this extra
option in the r6 block should have no effect.

>> I don't think the name of that variable explains itself very well,
>> especially since one of the options enables R6. Maybe MIPS_R2_R6_CONFIG
>> is better?

James



signature.asc
Description: OpenPGP digital signature

Bug#904206: itop shows 0 interrupts, on amd64 SMP

[sfahbj]

Package: itop
Version: 0.1-4+b2

running as "itop -a" it shows only 0, after running for even a minute

INTNAME  RATE MAX
  0 [0  0  ] 0 Ints/s (max: 0)

on CPU model name  : AMD FX(tm)-6300 Six-Core Processor

$ uname -a
Linux xxx 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.5 (stretch)
Release:9.5
Codename:   stretch

$ cat /proc/interrupts 
CPU0   CPU1   CPU2   CPU3   CPU4   CPU5   
   0: 46  0  0  0  0  0  
IR-IO-APIC2-edge  timer
   1:  1  0  0  0  0  1  
IR-IO-APIC1-edge  i8042
   8:  0  0  2  1  2  8  
IR-IO-APIC8-edge  rtc0
   9:  0  0  0  0  0  0  
IR-IO-APIC9-fasteoi   acpi
  12:  0  1  1  0  1  1  
IR-IO-APIC   12-edge  i8042
[...]
 NMI:   4576   3850   4491   3235   4362   4338   
Non-maskable interrupts 
  
 LOC:   79802757   38989023   91878071   54345626   79404978   57705477   Local 
timer interrupts

 SPU:  0  0  0  0  0  0   
Spurious interrupts 
  
 PMI:   4576   3850   4491   3235   4362   4338   
Performance monitoring interrupts   
  
 IWI:  0  0  4  0  2  6   IRQ 
work interrupts 
  
 RTR:  0  0  0  0  0  0   APIC 
ICR read retries
 
 RES:  123267589   91279982  108142748   91374192  113543056   73375822   
Rescheduling interrupts 
  
 CAL:857335278191917567869741840484058627427276   
Function call interrupts
  
 TLB:855983178055137553932740438583918547398230   TLB 
shootdowns  
  
 TRM:  0  0  0  0  0  0   
Thermal event interrupts
  
 THR:  0  0  0  0  0  0   
Threshold APIC interrupts   
  
 DFR:  0  0  0  0  0  0   
Deferred Error APIC interrupts  
  
 MCE:  0  0  0  0  0  0   
Machine check exceptions
  
 MCP:   1152   1152   1152   1152   1152   1152   
Machine check polls 
  
 ERR:  1


 MIS:  0


 PIN:  0  0  0  0  0  0   
Posted-interrupt notification event 
  
 PIW:  0  0  0  0  0  0   
Posted-interrupt wakeup event



It does show some values that make more sense on another AMD64 SMP Debian 9.5, 
on another machine.

Bug#904178: ffmpeg: fix mips r6 build

[YunQiang Su]

James Cowgill  于2018年7月21日周六 下午11:16写道：
>
> Control: notfound -1 4.0.1-2
> Control: found -1 7:4.0.1-2
>
> Hi Yunqiang,
>
> On 21/07/18 05:46, YunQiang Su wrote:
> > Package: src:ffmpeg
> > Version: 4.0.1-2
> >
> > We are working on MIPS r6 ports.
> >
> > Please change the lines about mips options in debian/rules to the below.
> > # Disable some optimizations on mips*, because they are not always
> > available on these architectures
> > ifneq (,$(filter mips%r6 mips%r6el, $(DEB_HOST_ARCH)))
> > MIPS_NO_R6_OPTION = --disable-mips32r2 \
> > --disable-mips64r2 \
> > --disable-mips32r5
>
> Is this line intentional (given that --disable-mips32r5 is used below as
> well)?
>

yes. when the first try, I don't add --disable-mips32r5, then it
failed to build,
when link r2/r6 objects.

> I don't think the name of that variable explains itself very well,
> especially since one of the options enables R6. Maybe MIPS_R2_R6_CONFIG
> is better?
>
> James
>


-- 
YunQiang Su

Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

[Mattia Rizzolo]

On Sat, Jul 21, 2018 at 02:41:32PM +0100, James Cowgill wrote:
> If versioned provides was working properly everywhere then
> possibly it could be used, but I don't think it does yet (although I'm
> happy to be corrected!).

They do.  In the past 2 years many bugs around the infrastructure were
fixed and versioned provides can now be fully used (in particular, there
were some last pieces regarding wanna-build and britney, that have been
fixed ~1 year ago IIRC).

The only thing is that they may be confusing to some, as it's not so
straightforward to find a virtual package compared to a plain `apt show`
:>

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#904205: ITP: adapta-kde -- Port of the popular Gtk theme Adapta for Plasma 5 desktop

[Franciscarlos Soares]

Package: wnpp
Severity: wishlist
Owner: Franciscarlos Soares 

* Package name: adapta-kde
  Version : 20180618
  Upstream Author : Alexey Varfolomeev 
* URL : https://github.com/PapirusDevelopmentTeam/adapta-kde
* License : (GPL-3.0+
  Programming Lang: N/A
  Description : Port of the popular Gtk theme Adapta for Plasma 5 desktop

  adapta-kde is a port of the popular Gtk theme Adapta for Plasma 5 desktop with
  a few additions and extras.
  .
  In this repository you'll find:
  .
   * Aurorae Theme
   * Konsole Color Schemes
   * Kvantum Themes
   * Plasma Color Schemes
   * Plasma Desktop Theme
   * Plasma Look-and-Feel Settings
   * Wallpaper
   * Yakuake Skins

Bug#904204: openjdk-11: Please update patch for m68k support

[John Paul Adrian Glaubitz]

Source: openjdk-11
Version: 11~23-1
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hello!

In order to make openjdk-11 build on m68k, the m68k-support.diff patch
needs to be updated. The current version doesn't apply anymore which
is why it was disabled in the past.

Please replace the patch with the attached version for the next upload.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
# HG changeset patch
# User glaubitz
# Date 1532184301 -7200
#  Sat Jul 21 16:45:01 2018 +0200
# Node ID 7acf28c3e4edd6d66f809828f0ec4122daf8f157
# Parent  b0fcf59be3918afcaa13d1f97343968c2c467ffe
JDK-NNN: Zero needs alignment fixes for linux-m68k

diff -r b0fcf59be391 -r 7acf28c3e4ed src/hotspot/share/memory/allocation.hpp
--- a/src/hotspot/share/memory/allocation.hpp   Fri Jul 20 14:48:41 2018 -0700
+++ b/src/hotspot/share/memory/allocation.hpp   Sat Jul 21 16:45:01 2018 +0200
@@ -209,7 +209,7 @@
 
   void  operator delete(void* p) { FreeHeap(p); }
   void  operator delete [] (void* p) { FreeHeap(p); }
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for objects allocated on the stack only.
 // Calling new or delete will result in fatal error.
@@ -223,7 +223,7 @@
 #endif
   void  operator delete(void* p);
   void  operator delete [](void* p);
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for objects stored in Metaspace.
 // Calling delete will result in fatal error.
@@ -311,7 +311,7 @@
   // that should be read-only by default. See symbol.hpp for an example. This 
function
   // is used by the templates in metaspaceClosure.hpp
   static bool is_read_only_by_default() { return false; }
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for classes that constitute name spaces.
 
@@ -401,7 +401,7 @@
 
   void  operator delete(void* p);
   void  operator delete [](void* p);
-};
+} __attribute__ ((aligned (4)));
 
 // One of the following macros must be used when allocating an array
 // or object to determine whether it should reside in the C heap on in
diff -r b0fcf59be391 -r 7acf28c3e4ed src/hotspot/share/oops/constMethod.hpp
--- a/src/hotspot/share/oops/constMethod.hppFri Jul 20 14:48:41 2018 -0700
+++ b/src/hotspot/share/oops/constMethod.hppSat Jul 21 16:45:01 2018 +0200
@@ -559,6 +559,6 @@
 
   // Verify
   void verify_on(outputStream* st);
-};
+} __attribute__ ((aligned (4)));
 
 #endif // SHARE_VM_OOPS_CONSTMETHODOOP_HPP
diff -r b0fcf59be391 -r 7acf28c3e4ed src/hotspot/share/oops/oop.hpp
--- a/src/hotspot/share/oops/oop.hppFri Jul 20 14:48:41 2018 -0700
+++ b/src/hotspot/share/oops/oop.hppSat Jul 21 16:45:01 2018 +0200
@@ -331,6 +331,6 @@
 assert(has_klass_gap(), "only applicable to compressed klass pointers");
 return klass_offset_in_bytes() + sizeof(narrowKlass);
   }
-};
+} __attribute__ ((aligned (4)));
 
 #endif // SHARE_VM_OOPS_OOP_HPP
diff -r b0fcf59be391 -r 7acf28c3e4ed 
src/java.base/unix/native/libjli/java_md_solinux.c
--- a/src/java.base/unix/native/libjli/java_md_solinux.cFri Jul 20 
14:48:41 2018 -0700
+++ b/src/java.base/unix/native/libjli/java_md_solinux.cSat Jul 21 
16:45:01 2018 +0200
@@ -727,12 +727,24 @@
 }
 }
 
+struct call_continuation_args {
+  int (JNICALL *continuation)(void *);
+  void *args;
+};
+
+static void *call_continuation(void *_args)
+{
+  struct call_continuation_args *args = _args;
+  return (void *)args->continuation(args->args);
+}
+
 /*
  * Block current thread and continue execution in a new thread
  */
 int
 ContinueInNewThread0(int (JNICALL *continuation)(void *), jlong stack_size, 
void * args) {
 int rslt;
+struct call_continuation_args ccargs = { continuation, args };
 #ifndef __solaris__
 pthread_t tid;
 pthread_attr_t attr;
@@ -744,7 +756,7 @@
 }
 pthread_attr_setguardsize(, 0); // no pthread guard page on java 
threads
 
-if (pthread_create(, , (void *(*)(void*))continuation, 
(void*)args) == 0) {
+if (pthread_create(, , call_continuation, ) == 0) {
   void * tmp;
   pthread_join(tid, );
   rslt = (int)(intptr_t)tmp;
@@ -762,7 +774,7 @@
 #else /* __solaris__ */
 thread_t tid;
 long flags = 0;
-if (thr_create(NULL, stack_size, (void *(*)(void *))continuation, args, 
flags, ) == 0) {
+if (thr_create(NULL, stack_size, call_continuation, , flags, ) 
== 0) {
   void * tmp;
   thr_join(tid, NULL, );
   rslt = (int)(intptr_t)tmp;

Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

[James Cowgill]

Control: tags -1 moreinfo

Hi,

On 20/07/18 23:14, Dirk Lehmann wrote:
> Package: libavcodec-extra57
> Version: 7:3.4.3-1
> Severity: normal
> Tags: d-i
> 
> Dear Maintainer,
> 
> I try to install a backport package which is depending on package
> 'libavcodec57'.  But I have installed the package libavcodec-extra57
> on my machine.  If I try to install it, I get the following error:
> 
> --
> root$> apt-get install jitsi
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  jitsi : Depends: libavcodec57 but it is not going to be installed or
>   libavcodec-ffmpeg56 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> --

Where is this package from? There is no "jitsi" in Debian (anymore) so
it must be unofficial. When packages are built against ffmpeg they
should get a dependency like this which should work with libavcodec-extra:
 libavcodec57 (>= 7:3.4.3) | libavcodec-extra57 (>= 7:3.4.3)

Probably the jitsi packages itself is at fault, or something else is
preventing the installation.

> I'm not really familiar with DPKG, but I think it could be solved if
> the manifest of dpkg-archive from 'libavcodec-extra57' includes a
> 
> --
> [...]
> Provides: libavcodec57
> [...]
> --

Unfortunately this won't work because it won't satisfy versioned
dependencies. If versioned provides was working properly everywhere then
possibly it could be used, but I don't think it does yet (although I'm
happy to be corrected!).

James



signature.asc
Description: OpenPGP digital signature

Bug#803744: Info received (Still not fixed in Raspbian GNU/Linux 9 (stretch))

[Alexander Dahl]

Hei hei,

meanwhile I found Debian bug report #883026 which addresses the same
underlying problem. I'm not familiar with managing those reports,
maybe someone can set this as duplicate?

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

Greets
Alex


signature.asc
Description: PGP signature

Bug#904123: mpv: Screenshot always crashes with Segmentation fault

[James Cowgill]

Control: reassign -1 src:ffmpeg 7:3.4.3-1
Control: found -1 7:3.2.11-1~deb9u1
Control: fixed -1 7:4.0-1
Control: tags -1 fixed-upstream

Hi,

On 21/07/18 14:54, S Andreason wrote:
> James Cowgill wrote:
>> Can you confirm that it's this bug you're seeing?
>> https://github.com/mpv-player/mpv/issues/5989
>>
>> The segfault should only happen for PNG screenshots and not JPEG
>> screenshots.
>>
>> If so then yes it's an FFmpeg bug. It should be fixed when 3.2.12 is
>> uploaded. AFAIKT, 3.4.3 in testing is also affected, but the 4.0 branch
>> (including 4.0.1 in unstable) is not.
>>
>>
> 
> Hi James,
> Yes my backtrace looks like the same bug.
> 
> Thread 1 "mpv" received signal SIGSEGV, Segmentation fault.
> 0xb6ea4240 in avcodec_find_best_pix_fmt_of_list ()
>    from /usr/lib/i386-linux-gnu/libavcodec.so.57
> (gdb) bt
> #0  0xb6ea4240 in avcodec_find_best_pix_fmt_of_list ()
>    from /usr/lib/i386-linux-gnu/libavcodec.so.57
> #1  0x004c3bbd in ?? ()
> 
> No debug symbols installed to see anything further.
> Thank you for the info. Is there anyplace I can visit to see current
> status, or expected time for updates?

Thanks.

This page has most of the public information about ffmpeg (although it's
geared up for developers):
https://tracker.debian.org/pkg/ffmpeg

There isn't really an expected time for the update. It will get updated
when I get around to preparing the update and the security team
processes it.

James



signature.asc
Description: OpenPGP digital signature