Bug#899720: marked as done (user-mode-linux: Invalid maintainer address pkg-uml-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jun 2018 05:49:45 +
with message-id 
and subject line Bug#899720: fixed in user-mode-linux 4.16-1um-1
has caused the Debian Bug report #899720,
regarding user-mode-linux: Invalid maintainer address 
pkg-uml-p...@lists.alioth.debian.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
899720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:user-mode-linux
Version: 4.15-1um-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of user-mode-linux,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package user-mode-linux since the list address
pkg-uml-p...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-uml-p...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: user-mode-linux
Source-Version: 4.16-1um-1

We believe that the bug you reported is fixed in the latest version of
user-mode-linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated user-mode-linux 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 12 Jun 2018 10:24:43 +0545
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source amd64
Version: 4.16-1um-1
Distribution: unstable
Urgency: medium
Maintainer: User Mode Linux Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 user-mode-linux - User-mode Linux (kernel)
Closes: 899720
Changes:
 user-mode-linux (4.16-1um-1) unstable; urgency=medium
 .
   * [4f0e0a8] Switch packaging repository to Salsa
   * [94e916a] Switch Maintainer email address (Closes: #899720)
   * [0e56bcc] Use tracker as maintainer email address
   * [0f68dd3] Update to Linux 4.16
   * [98f3862] Drop patch 08-use-posix-ucontext.patch
 Merged in Linux 4.16
   * [38116f5] Add bison to build dependency
   * [e5ae8d8] Add flex to build dependency
Checksums-Sha1:
 7864ea39a4940a8011c1425d703c75bf9988ec39 1892 user-mode-linux_4.16-1um-1.dsc
 0f0e1055429a3043733f1ecb610ad880e5b87c54 363179 
user-mode-linux_4.16-1um-1.tar.gz
 380ea6e786db46a85050dfb7a47b3226ab830641 385464 
user-mode-linux-dbgsym_4.16-1um-1_amd64.deb
 849935fcdca0366bb8f94fbbd7ff08595c70b451 6493 
user-mode-linux_4.16-1um-1_amd64.buildinfo
 b1d9052bcf31b4d61b431a22bc54ff4dc03aa033 9814072 
user-mode-linux_4.16-1um-1_amd64.deb

Bug#901185: [Debconf-devel] Bug#901185: me too

[Colin Watson]

On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> On 2018-06-11 Colin Watson  wrote:
> > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > yes, resetting IFS to its default value in confmodule helps.
> 
> > Thanks.  For completeness, could you try this variant patch?  If shells
> > are going to be unreliable about setting IFS in this way, then I'd
> > rather just separate out the assignments altogether.
> [snip]
> 
> Yes, this variant of the patch also works.
> 
> Thanks to your handholding we now have a minimal reproducer for the
> issue:

Thanks.  Now that you have a reproducer that doesn't involve debconf and
so I won't be interfering with debugging, I've uploaded debconf 1.5.67
with that confmodule patch.  I know it's a bash5 bug and will hopefully
be fixed, but we might as well be conservative in debconf when it's easy
to do so.

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

Bug#886065:

[Willem van den Akker]

Hi,

Please remove Gyrus from unstable.

The package is abadoned upstream so there will be
never any new versions.

/Willem

Bug#899721: marked as done (user-mode-linux-doc: Invalid maintainer address pkg-uml-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jun 2018 04:52:28 +
with message-id 
and subject line Bug#899721: fixed in user-mode-linux-doc 20060501-3
has caused the Debian Bug report #899721,
regarding user-mode-linux-doc: Invalid maintainer address 
pkg-uml-p...@lists.alioth.debian.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
899721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:user-mode-linux-doc
Version: 20060501-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of user-mode-linux-doc,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package user-mode-linux-doc since the list address
pkg-uml-p...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-uml-p...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: user-mode-linux-doc
Source-Version: 20060501-3

We believe that the bug you reported is fixed in the latest version of
user-mode-linux-doc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated user-mode-linux-doc 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 12 Jun 2018 10:15:11 +0545
Source: user-mode-linux-doc
Binary: user-mode-linux-doc
Architecture: source all
Version: 20060501-3
Distribution: unstable
Urgency: medium
Maintainer: User Mode Linux Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 user-mode-linux-doc - User-mode Linux (Documentation)
Closes: 899721
Changes:
 user-mode-linux-doc (20060501-3) unstable; urgency=medium
 .
   * Switch packaging to Salsa
   * Switch Maintainer email address (Closes: #899721)
   * Use tracker as maintainer email address
Checksums-Sha1:
 471a0877a24b39ff28746877b3454dabac2c0ef3 1774 
user-mode-linux-doc_20060501-3.dsc
 66ff6dbceff8798143cc61cb6ba761bdf520b7ee 1576491 
user-mode-linux-doc_20060501-3.tar.gz
 1ce172ab6e59e1f69643818103d37e90bfcc9eb2 538328 
user-mode-linux-doc_20060501-3_all.deb
 cf22c291e3b18d31c7d10703746ff44dc8227208 5554 
user-mode-linux-doc_20060501-3_amd64.buildinfo
Checksums-Sha256:
 a438108566fe918c8e2c074176f091d8ae968a170c376c51eeff5158ce552e12 1774 
user-mode-linux-doc_20060501-3.dsc
 ccb729f48ce73d0c621b597885747c9c8af37148d911c37e760101ac2a420f9b 1576491 
user-mode-linux-doc_20060501-3.tar.gz
 

Bug#899717: marked as done (uml-utilities: Invalid maintainer address pkg-uml-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jun 2018 04:52:20 +
with message-id 
and subject line Bug#899717: fixed in uml-utilities 20070815.1-3
has caused the Debian Bug report #899717,
regarding uml-utilities: Invalid maintainer address 
pkg-uml-p...@lists.alioth.debian.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
899717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uml-utilities
Version: 20070815.1-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of uml-utilities,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package uml-utilities since the list address
pkg-uml-p...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-uml-p...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: uml-utilities
Source-Version: 20070815.1-3

We believe that the bug you reported is fixed in the latest version of
uml-utilities, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated uml-utilities package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 12 Jun 2018 10:10:31 +0545
Source: uml-utilities
Binary: uml-utilities
Architecture: source amd64
Version: 20070815.1-3
Distribution: unstable
Urgency: medium
Maintainer: User Mode Linux Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 uml-utilities - User-mode Linux (utility programs)
Closes: 899717
Changes:
 uml-utilities (20070815.1-3) unstable; urgency=medium
 .
   * Switch packaging repository to Salsa
   * Switch Maintainer email address (Closes: #899717)
   * Use tracker as maintainer email address
Checksums-Sha1:
 b16720d16486adff1b132016f0b7cad7eea23cd1 2089 uml-utilities_20070815.1-3.dsc
 b4c676c315c63096b42070e7e563aaa68995b837 16352 
uml-utilities_20070815.1-3.debian.tar.xz
 59db30962c87257d5a7fb976b8bcb584bb963399 6041 
uml-utilities_20070815.1-3_amd64.buildinfo
 1b9cf53511e3782941d8097d793e2b080708a44a 52764 
uml-utilities_20070815.1-3_amd64.deb
Checksums-Sha256:
 db299012e2df580792ff08c3e1601d0ef17a584e33e833bbf09ee5b947b78166 2089 
uml-utilities_20070815.1-3.dsc
 69e638e50ef47860478fd9254d74877672f0ea1891b05ea2b2f5e33558cce5a3 16352 
uml-utilities_20070815.1-3.debian.tar.xz
 2702ced3bae337a90ec8b9710ae386afa5d69fc582aa6da003c87f274ae476e4 6041 

Bug#901225: marked as done (libell-dev: missing dependency on libell0)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jun 2018 00:04:49 +
with message-id 
and subject line Bug#901225: fixed in ell 0.4-2
has caused the Debian Bug report #901225,
regarding libell-dev: missing dependency on libell0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libell-dev
Version: 0.4-1
Severity: serious

Your package is lacking a dependency on libell0 (= ${binary:Version}),
without it dynamic linking is not going to work:

,
| $ sudo aptitude install libell-dev
| [...]   
| $ file /usr/lib/i386-linux-gnu/libell.so
| /usr/lib/i386-linux-gnu/libell.so: broken symbolic link to libell.so.0.0.1
`


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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ell
Source-Version: 0.4-2

We believe that the bug you reported is fixed in the latest version of
ell, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated ell package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Jun 2018 08:26:45 +0900
Source: ell
Binary: libell0 libell-dev
Architecture: source amd64
Version: 0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Description:
 libell-dev - development files for the Embedded Linux library
 libell0- Embedded Linux library
Closes: 901225
Changes:
 ell (0.4-2) unstable; urgency=medium
 .
   * Add libell0 to Depends of libell-dev. (Closes: #901225)
Checksums-Sha1:
 d80eaf6987d8283ef5a2f75b9afd25fd41017728 1833 ell_0.4-2.dsc
 0204978aebcc7e8af6c91ca27e8f6394c5795f01 3616 ell_0.4-2.debian.tar.xz
 d87dbc329b3a3ac1005ee2b0b67bef1f55240f51 6610 ell_0.4-2_amd64.buildinfo
 d4f75215d8dc72d7fe2973de4335f81837a6b0e4 115112 libell-dev_0.4-2_amd64.deb
 dc67af21793bbbc7bbb278bd06f988e6be5a2dcd 268208 libell0-dbgsym_0.4-2_amd64.deb
 0d5c3663975b2d9b7c4768905aa4f47a4a9375a5 93664 libell0_0.4-2_amd64.deb
Checksums-Sha256:
 97162d9059c2119725ed69ac02d6984e9aa1b71986e7ff42f5fd7da12f423510 1833 
ell_0.4-2.dsc
 0026c67f755dd2463e2955688cb7f41e521613992beb6e2decde71924dfd1f86 3616 
ell_0.4-2.debian.tar.xz
 59ed324e69f567e9a013baec875653cd08ddbcbe16b257c6b8635694d88ef918 6610 
ell_0.4-2_amd64.buildinfo
 980123b528a63cfa9d6c10b0092269aeb04f170802b031ace12545723dc34613 115112 
libell-dev_0.4-2_amd64.deb
 a1b611a490a2c28a46fd43745072e30da70aea22138569996dd3c3c951943d27 268208 
libell0-dbgsym_0.4-2_amd64.deb
 94d4dc137516df70e831166f7528008aa722c3719cdf07283d2f4c4c46a4742e 93664 
libell0_0.4-2_amd64.deb
Files:
 25fcaf347336142b4a65bedd4bf29df4 1833 devel optional ell_0.4-2.dsc
 216406b653b5b59191fb470dcb6aa624 3616 devel optional ell_0.4-2.debian.tar.xz
 cc4898121be82fec67b44b480806d5a9 6610 devel optional ell_0.4-2_amd64.buildinfo
 c78cd02f484fefd6880dfde98b2c7a31 115112 libdevel optional 
libell-dev_0.4-2_amd64.deb
 e93411226c3734d8a70b93d456df0b5b 268208 debug optional 
libell0-dbgsym_0.4-2_amd64.deb
 e7cba7db2440298a8255cc01c2b61f8b 93664 libs optional libell0_0.4-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlsfCGcACgkQMiR/u0Ct
H6aUkA/9HafLqR7onmXY5niBOCywckHYAeV68QEsIqOZ0Wjr7qNMIurPZCJIByme
9FoODwoZaRt7HlOSUts1FddPeezQdKdyrnZjKWK169s9ugFvswJ/FZ5+vT6qEB+x
3sre/01tkVG9gPMl1zPSqvUzYYeLRE6/4gSFY+1xRXyLOItrAcNwICBa91tqbnWr
d4VoldsdO6meHj2UQVPDxoM5iCwup0zcguDCerKsXhjWysTfX1YzKOvd690iAAUT
+tqZlsJH+YWmWQP+fZKj5l1mpmOX3vX8lHUtFjWogwSOHgCyi5+xm3udxRV7b1+D
f2IXdibEs7WukEIghyAsi4J4BDehDuF5Pn79SHWRQ9KtNHnlwYg0WtwcpN6ItEAe

Bug#900822: marked as done (needs magit 2.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 22:50:12 +
with message-id 
and subject line Bug#900822: fixed in magithub 0.1.7-1
has caused the Debian Bug report #900822,
regarding needs magit 2.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
900822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-magithub
Version: 0.1.5-2
Severity: serious

Thanks to my upload, elpa-magithub is now uninstallable in sid.

I think it should also get a versioned depends to help with upgrades / 
migrations


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

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

Versions of packages elpa-magithub depends on:
ii  elpa-ghub+  0.2.1-2
ii  elpa-git-commit 2.11.0-1
ii  elpa-magit  2.11.0-1
ii  elpa-markdown-mode  2.3+154-1
ii  elpa-s  1.12.0-1
ii  emacsen-common  2.0.8

Versions of packages elpa-magithub recommends:
ii  emacs  47.0

elpa-magithub suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: magithub
Source-Version: 0.1.7-1

We believe that the bug you reported is fixed in the latest version of
magithub, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated magithub package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 12 Jun 2018 00:23:49 +0200
Source: magithub
Binary: elpa-magithub
Architecture: source
Version: 0.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Matteo F. Vescovi 
Description:
 elpa-magithub - Magit interfaces for GitHub
Closes: 900822
Changes:
 magithub (0.1.7-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #900822)
   * debian/patches/: patchset dropped
   * debian/control:
 - drop Depends on elpa-s (already managed)
 - Vcs-* fields updated pointing to salsa
 - Maintainer field updated
 - Build-Depends updated (texinfo and texlive added)
 - S-V bump 4.1.3 -> 4.1.4 (no changes needed)
Checksums-Sha1:
 135004407cebdbec74a0ce9b1c8d7cd97167f0ef 2125 magithub_0.1.7-1.dsc
 f880715682c68987f7bbcda2eb10fb1186bf1955 1378264 magithub_0.1.7.orig.tar.xz
 d68b7c69c3956b64c3473076b683ba80afb5ab85 2456 magithub_0.1.7-1.debian.tar.xz
 a2c370d8bd08bdea51e0bd8f3c2c680ac105c47d 12826 
magithub_0.1.7-1_source.buildinfo
Checksums-Sha256:
 e4d92f224c5412faeb3b94bf5e30a8320c4b70094626d38a0243ef16048189ff 2125 
magithub_0.1.7-1.dsc
 6880ab650c20e3b824572c81642805046cd48a965b59fde77944780a7b1bb7e2 1378264 
magithub_0.1.7.orig.tar.xz
 770102f84eb87ca6bb9820a99e3fb0b708bbd62721b7451246b5fe97cfb25832 2456 
magithub_0.1.7-1.debian.tar.xz
 059c79ceca4348189f9e90543ce1119784eea444a115a36a0066b10bb6ab74ae 12826 
magithub_0.1.7-1_source.buildinfo
Files:
 6b7cfd301b59e85f2f95aaa4b3d78dfc 2125 lisp optional magithub_0.1.7-1.dsc
 568fda5f305cbde7728d7845ee58 1378264 lisp optional 
magithub_0.1.7.orig.tar.xz
 de327bcd6204908d04122c9138a8dfca 2456 lisp optional 
magithub_0.1.7-1.debian.tar.xz
 3e630f49ea2b02a2953c6c213f52b5a9 12826 lisp optional 
magithub_0.1.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAlse9vFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz
REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N
zVqVyRAAtrAnBsUSCAd5dt81xF9u2fEFxJm7GxfEf5QTzBFNTaeb0QXzS3vINcB+
XL9Jf+mIrLQxBnk3/ICqsE8kDgc7B5no2FdmnnFV/Fscs1j90qqLZbPuXSPxJW+r
2/jM6DQsk9YZ5wrN5CU/ehF2JHET5B33MslVzK6B/iwgvGjuDlk7rviRP9UZ9/B9
VVgSvyvTL0201xphRsaadNVF6970Y2XkHbe+L9FFPkYUmeEoDuwmF16wZZ7QLCii
7hf1Ddd5I8OGYEh7OQjpgj/JlCG59jIZ6KO3u2Vx/+ihz5xnrRkULWUIUZ4vP1Zj

Processed (with 1 error): unblock 787080 with 894119, forcibly merging 787080 894119

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 787080 with 894119
Bug #787080 [wnpp] ITP: libreoffice-online -- LibreOffice on-line
787080 was blocked by: 804633 794890 856192 870460 857986 786498
787080 was blocking: 894119
Removed blocking bug(s) of 787080: 894119
> forcemerge 787080 894119
Bug #787080 [wnpp] ITP: libreoffice-online -- LibreOffice on-line
Bug #787080 [wnpp] ITP: libreoffice-online -- LibreOffice on-line
894119 was blocked by: 787080
894119 was not blocking any bugs.
Removed blocking bug(s) of 894119: 787080
Bug #894119 [wnpp] RFP: libreoffice-online
894119 was not blocked by any bugs.
894119 was not blocking any bugs.
Added blocking bug(s) of 894119: 857986
No valid blocking bug(s) given; not doing anything
Failed to forcibly merge 787080: Failure while trying to adjust bugs, please 
report this as a bug: Unknown/archived blocking bug(s):856192.
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787080
894119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#859838: marked as done (yubico-piv-tool: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 21:05:02 +
with message-id 
and subject line Bug#859838: fixed in yubico-piv-tool 1.5.0-1
has caused the Debian Bug report #859838,
regarding yubico-piv-tool: Please migrate to openssl1.1 in Buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
859838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yubico-piv-tool
Version: 1.4.2-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
control: forwarded -1 https://github.com/Yubico/yubico-piv-tool/issues/104

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828616. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/yubico-piv-tool_1.0.3-1_amd64-20160529-1559

Sebastian
--- End Message ---
--- Begin Message ---
Source: yubico-piv-tool
Source-Version: 1.5.0-1

We believe that the bug you reported is fixed in the latest version of
yubico-piv-tool, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon Josefsson  (supplier of updated yubico-piv-tool 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Jun 2018 21:56:06 +0200
Source: yubico-piv-tool
Binary: libykpiv1 libykpiv-dev yubico-piv-tool ykcs11
Architecture: source amd64
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Authentication Maintainers 

Changed-By: Simon Josefsson 
Description:
 libykpiv-dev - Development files for the YubiKey PIV Library
 libykpiv1  - Library for communication with the YubiKey PIV smartcard
 ykcs11 - PKCS#11 module for the YubiKey PIV applet
 yubico-piv-tool - Command line tool for the YubiKey PIV applet
Closes: 810284 859838
Changes:
 yubico-piv-tool (1.5.0-1) unstable; urgency=medium
 .
   * New upstream version.  Closes: #810284.
 - Replace libssl1.0 with libssl1.1.  Closes: #859838.
 - Depend on check.
   * Use https URLs in debian/copyright.
   * Update Standards-Version from 3.9.8 to 4.1.4.
 - Priority optional instead of extra.
   * Use compat level 11.
 - Drop no longer needed --parallel.
 - Drop no longer needed --with autoreconf.
 - Drop no longer needed --disable-silent-rules.
 - Drop no longer needed --builddirectory.
 - Drop no longer needed dh-autoreconf.
Checksums-Sha1:
 cfb98e70e3af1a6d804acb2d1e8970154e18eb62 1990 yubico-piv-tool_1.5.0-1.dsc
 9d34a99bcd6ddc98140fb15cf893853cc10ef0ae 573453 
yubico-piv-tool_1.5.0.orig.tar.gz
 6f7828fc57b1054b363866b24f8d4994e32468b8 74272 
yubico-piv-tool_1.5.0-1.debian.tar.xz
 a4d3d0fd6a288ef47a6283b9dd001d81569fef42 53848 libykpiv-dev_1.5.0-1_amd64.deb
 b3f85ff38fdf1abd6bc66309a82ad3a1849db7e4 48636 
libykpiv1-dbgsym_1.5.0-1_amd64.deb
 bc98cf52244a867bd7c4b1b05db5ff853a2061b4 49088 libykpiv1_1.5.0-1_amd64.deb
 23fdcf454f496df7a7ae448f3c1bd609f653fe31 70664 ykcs11-dbgsym_1.5.0-1_amd64.deb
 6669be5c6a44b81695f5444b80fc708fb1f7b44b 53092 ykcs11_1.5.0-1_amd64.deb
 bd1829d25480fd27ca86cd640416a382ef543599 66504 
yubico-piv-tool-dbgsym_1.5.0-1_amd64.deb
 059bdd6f66b8fd716865d53e7f4606050eef0f72 7011 
yubico-piv-tool_1.5.0-1_amd64.buildinfo
 e08a98c73a73a0fdf1c705a219f53cfffec12ca0 56316 
yubico-piv-tool_1.5.0-1_amd64.deb
Checksums-Sha256:
 23578f5bdd98565f8c2970fbde73775c9b4121c0ba96f18ea34449e4457c9e85 1990 
yubico-piv-tool_1.5.0-1.dsc
 c18375179ba25bf9d61365b3903f033f112897bbd54ca63c62fa153f2d05aaab 573453 
yubico-piv-tool_1.5.0.orig.tar.gz
 1ea67b165c42f9f2f0533472ad107507c9f36ca843e1f857708353c3a780748b 74272 
yubico-piv-tool_1.5.0-1.debian.tar.xz
 e3ade3d8d97caf3078985ba14b2871b8fa55b36ab0b2bf5534f570cb382cfc25 53848 
libykpiv-dev_1.5.0-1_amd64.deb
 71100df88b25bdd271ead9be9d77d5dfaae8ad66a1e0ebd62cc116aadd8498c2 48636 
libykpiv1-dbgsym_1.5.0-1_amd64.deb
 dddbf01c101b487417dd410303a90c98ae0d543d3a23746c291df71416aa5d6a 49088 
libykpiv1_1.5.0-1_amd64.deb
 eb0bff164d1a0b3e452eaeac0813e6ab539507e40722d76dfee930c020f3c988 70664 

Bug#810284: marked as done (yubico-piv-tool: newer upstream release 1.4.3, needed by yubikey-piv-manager)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 21:05:02 +
with message-id 
and subject line Bug#810284: fixed in yubico-piv-tool 1.5.0-1
has caused the Debian Bug report #810284,
regarding yubico-piv-tool: newer upstream release 1.4.3, needed by 
yubikey-piv-manager
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
810284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yubico-piv-tool
Version: 1.0.3-1
Severity: wishlist

Since 1.0.3, upstream has released both the 1.1 series and 1.2
(currently at 1.2.2) -- any chance of getting something a little newer
in the archive? :)

(Docker's support for yubikeys requires at least 1.1.0, which is why
I'm asking.)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
--- End Message ---
--- Begin Message ---
Source: yubico-piv-tool
Source-Version: 1.5.0-1

We believe that the bug you reported is fixed in the latest version of
yubico-piv-tool, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 810...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon Josefsson  (supplier of updated yubico-piv-tool 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Jun 2018 21:56:06 +0200
Source: yubico-piv-tool
Binary: libykpiv1 libykpiv-dev yubico-piv-tool ykcs11
Architecture: source amd64
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Authentication Maintainers 

Changed-By: Simon Josefsson 
Description:
 libykpiv-dev - Development files for the YubiKey PIV Library
 libykpiv1  - Library for communication with the YubiKey PIV smartcard
 ykcs11 - PKCS#11 module for the YubiKey PIV applet
 yubico-piv-tool - Command line tool for the YubiKey PIV applet
Closes: 810284 859838
Changes:
 yubico-piv-tool (1.5.0-1) unstable; urgency=medium
 .
   * New upstream version.  Closes: #810284.
 - Replace libssl1.0 with libssl1.1.  Closes: #859838.
 - Depend on check.
   * Use https URLs in debian/copyright.
   * Update Standards-Version from 3.9.8 to 4.1.4.
 - Priority optional instead of extra.
   * Use compat level 11.
 - Drop no longer needed --parallel.
 - Drop no longer needed --with autoreconf.
 - Drop no longer needed --disable-silent-rules.
 - Drop no longer needed --builddirectory.
 - Drop no longer needed dh-autoreconf.
Checksums-Sha1:
 cfb98e70e3af1a6d804acb2d1e8970154e18eb62 1990 yubico-piv-tool_1.5.0-1.dsc
 9d34a99bcd6ddc98140fb15cf893853cc10ef0ae 573453 
yubico-piv-tool_1.5.0.orig.tar.gz
 6f7828fc57b1054b363866b24f8d4994e32468b8 74272 
yubico-piv-tool_1.5.0-1.debian.tar.xz
 a4d3d0fd6a288ef47a6283b9dd001d81569fef42 53848 libykpiv-dev_1.5.0-1_amd64.deb
 b3f85ff38fdf1abd6bc66309a82ad3a1849db7e4 48636 
libykpiv1-dbgsym_1.5.0-1_amd64.deb
 bc98cf52244a867bd7c4b1b05db5ff853a2061b4 49088 libykpiv1_1.5.0-1_amd64.deb
 23fdcf454f496df7a7ae448f3c1bd609f653fe31 70664 ykcs11-dbgsym_1.5.0-1_amd64.deb
 6669be5c6a44b81695f5444b80fc708fb1f7b44b 53092 ykcs11_1.5.0-1_amd64.deb
 bd1829d25480fd27ca86cd640416a382ef543599 66504 
yubico-piv-tool-dbgsym_1.5.0-1_amd64.deb
 059bdd6f66b8fd716865d53e7f4606050eef0f72 7011 
yubico-piv-tool_1.5.0-1_amd64.buildinfo
 e08a98c73a73a0fdf1c705a219f53cfffec12ca0 56316 
yubico-piv-tool_1.5.0-1_amd64.deb
Checksums-Sha256:
 23578f5bdd98565f8c2970fbde73775c9b4121c0ba96f18ea34449e4457c9e85 1990 
yubico-piv-tool_1.5.0-1.dsc
 c18375179ba25bf9d61365b3903f033f112897bbd54ca63c62fa153f2d05aaab 573453 
yubico-piv-tool_1.5.0.orig.tar.gz
 1ea67b165c42f9f2f0533472ad107507c9f36ca843e1f857708353c3a780748b 74272 
yubico-piv-tool_1.5.0-1.debian.tar.xz
 e3ade3d8d97caf3078985ba14b2871b8fa55b36ab0b2bf5534f570cb382cfc25 53848 
libykpiv-dev_1.5.0-1_amd64.deb
 71100df88b25bdd271ead9be9d77d5dfaae8ad66a1e0ebd62cc116aadd8498c2 48636 
libykpiv1-dbgsym_1.5.0-1_amd64.deb
 dddbf01c101b487417dd410303a90c98ae0d543d3a23746c291df71416aa5d6a 49088 
libykpiv1_1.5.0-1_amd64.deb
 eb0bff164d1a0b3e452eaeac0813e6ab539507e40722d76dfee930c020f3c988 70664 
ykcs11-dbgsym_1.5.0-1_amd64.deb
 3fe5593c0fe7788024d55f56ac518cbbef8691dc7c0cab157a790a3db666d054 

Bug#895469: marked as done (openjfx FTBFS on armel: invalid instructions)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 20:39:15 +
with message-id 
and subject line Bug#895469: fixed in openjfx 8u171-b11-1
has caused the Debian Bug report #895469,
regarding openjfx FTBFS on armel: invalid instructions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
895469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjfx
Version: 8u141-b14-3
Severity: serious
Tags: buster sid patch

https://buildd.debian.org/status/fetch.php?pkg=openjfx=armel=8u161-b12-1=1523051663=0

...
/tmp/ccxxsDUf.s: Assembler messages:
/tmp/ccxxsDUf.s:311: Error: selected processor does not support `movw 
r8,#:lower16:.Lllint_op_enter-.LrelativePCBase' in ARM mode
/tmp/ccxxsDUf.s:312: Error: selected processor does not support `movt 
r8,#:upper16:.Lllint_op_enter-.LrelativePCBase' in ARM mode
/tmp/ccxxsDUf.s:316: Error: selected processor does not support `movw 
r8,#:lower16:.Lllint_op_get_scope-.LrelativePCBase' in ARM mode
/tmp/ccxxsDUf.s:317: Error: selected processor does not support `movt 
r8,#:upper16:.Lllint_op_get_scope-.LrelativePCBase' in ARM mode
...


The baseline of the armel port was raised a few months ago,
this can be fixed with:

debian/patches/26-disable-webkit-jit-for-armv4.patch
-+#if CPU(ARM) && WTF_ARM_ARCH_VERSION < 5
++#if CPU(ARM) && WTF_ARM_ARCH_VERSION <= 5
--- End Message ---
--- Begin Message ---
Source: openjfx
Source-Version: 8u171-b11-1

We believe that the bug you reported is fixed in the latest version of
openjfx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated openjfx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jun 2018 22:05:32 +0200
Source: openjfx
Binary: openjfx libopenjfx-java libopenjfx-jni libopenjfx-java-doc 
openjfx-source
Architecture: source
Version: 8u171-b11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libopenjfx-java - JavaFX/OpenJFX 8 - Rich client application platform for Java 
(Jav
 libopenjfx-java-doc - JavaFX/OpenJFX 8 - Rich client application platform for 
Java (Jav
 libopenjfx-jni - JavaFX/OpenJFX 8 - Rich client application platform for Java 
(nat
 openjfx- JavaFX/OpenJFX 8 - Rich client application platform for Java
 openjfx-source - JavaFX/OpenJFX 8 - Rich client application platform for Java 
(sou
Closes: 895469
Changes:
 openjfx (8u171-b11-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Emmanuel Bourg ]
   * New upstream release:
 - Refreshed the patches
   * Standards-Version updated to 4.1.4
   * Use salsa.debian.org Vcs-* URLs
 .
   [ Peter Michael Green ]
   * Disable JIT on sub-armv7 (armel/raspbian), it fails to build
 there with assembler errors (Closes: #895469)
   * Fix some uint16/char16 issues in javascriptcore
Checksums-Sha1:
 5a5ff59a9d6767e6e28638d70b847cc209f0c3ac 2748 openjfx_8u171-b11-1.dsc
 57e736c7c91e119c931d9d323c2f1ea01685ab54 61153184 openjfx_8u171-b11.orig.tar.xz
 9c2a5200c8d19a145f8991f93631281ae5c29322 16824 
openjfx_8u171-b11-1.debian.tar.xz
 cfbf80b99403a61e98ef296b2dba0afb83c08a1b 22729 
openjfx_8u171-b11-1_source.buildinfo
Checksums-Sha256:
 bb3ccffbc56ccda34b92fc846014f5d02eee9c7a20bd1452ed899aa761e9753b 2748 
openjfx_8u171-b11-1.dsc
 904d6b8bf276a60e7c9a387f124cba9399cd427b359097f3cd75dad790f3ca91 61153184 
openjfx_8u171-b11.orig.tar.xz
 10194594afaeebbce0a689709ee453c7431d805f3f5c78380e80cdc649e4c817 16824 
openjfx_8u171-b11-1.debian.tar.xz
 c7581e80e66677e94e773aca1a294a9b7f816392803ed6f9556f581fe6337a6f 22729 
openjfx_8u171-b11-1_source.buildinfo
Files:
 7dc1affe9e66730c210802572a959ca5 2748 java optional openjfx_8u171-b11-1.dsc
 0acf43b99f4227c12e4820ea7abc6788 61153184 java optional 
openjfx_8u171-b11.orig.tar.xz
 85e35ccb628acadb38d77e6228475068 16824 java optional 
openjfx_8u171-b11-1.debian.tar.xz
 e2eb7d6759bd91d9324c7ea4f7a244d5 22729 java optional 
openjfx_8u171-b11-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#901185: me too

[Eduardo Bustamante]

On Mon, Jun 11, 2018 at 1:52 PM, Andreas Metzler  wrote:
[..]
> Looking at the Open Group Base Specifications Issue 7 I also think this
> behavior is a bug, since "read" is not a "a special built-in utility or
> function".

FWIW, this is a bug in bash5, and has been reported to upstream
already: https://lists.gnu.org/archive/html/bug-bash/2018-05/msg00077.html

Processed: Bug #895469 in openjfx marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895469 [src:openjfx] openjfx FTBFS on armel: invalid instructions
Added tag(s) pending.

-- 
895469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#895469: Bug #895469 in openjfx marked as pending

[plugwash]

Control: tag -1 pending

Hello,

Bug #895469 in openjfx reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/java-team/openjfx/commit/ee1b27a562c3fd384b7bfc2883e4add6f986da3b


Disable JIT on sub-armv7 (armel/raspbian) since it fails to build with 
assembler errors (Closes: #895469)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895469

Bug#893861: thawab: Intent to remove from Debian

[Jeremy Bicha]

On Mon, Jun 11, 2018 at 9:28 AM, أحمد المحمودي (Ahmed El-Mahmoudy)
 wrote:
> On Thu, May 03, 2018 at 07:49:18AM -0400, Jeremy Bicha wrote:
>> If we don't hear back immediately, I will be converting this bug into
>> a Debian removal bug for thawab very soon.
> ---end quoted text---
>
> Sorry for the late reply.
> I have filed a bug upstream about this months ago. Still waiting for the
> reply.

Thank you for replying.

We're still blocked on eclipse. Someone needs to see how bad it breaks
if the webkitgtk support is disabled (probably with a hacky patch).
I'm hoping we can get this done this year.

So until eclipse is handled, there is no urgent need to remove thawab
from Debian, if removing thawab will cause you too much inconvenience.
(It's already been removed from Testing.)

But once eclipse is handled, I expect we will try to remove thawab
promptly if it's still not ported away from the old webkitgtk.

Thanks,
Jeremy Bicha

Bug#897512: marked as done (haskell-wreq: FTBFS: Could not find module `Build_doctests')

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 19:04:55 +
with message-id 
and subject line Bug#897512: fixed in haskell-wreq 0.5.2.1-2
has caused the Debian Bug report #897512,
regarding haskell-wreq: FTBFS: Could not find module `Build_doctests'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
897512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-wreq
Version: 0.5.2.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
> make_setup_recipe
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> 
> Setup.hs:23:2: error:
>  warning: #warning You are configuring this package without cabal-doctest 
> installed. The doctests test-suite will not work as a result. To fix this, 
> install cabal-doctest before configuring. [-Wcpp]
>  #warning You are configuring this package without cabal-doctest 
> installed. \
>   ^~~
>|
> 23 | #warning You are configuring this package without cabal-doctest 
> installed. \
>|  ^
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
> configure_recipe
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/wreq-0.5.2.1/ --datasubdir=wreq 
> --htmldir=/usr/share/doc/libghc-wreq-doc/html/ --enable-library-profiling 
> --enable-tests
> Configuring wreq-0.5.2.1...
> Flags chosen: developer=False, httpbin=False, aws=False, doctest=True
> Dependency HUnit -any: using HUnit-1.6.0.0
> Dependency QuickCheck >=2.7: using QuickCheck-2.10.1
> Dependency aeson >=0.7.0.3: using aeson-1.2.4.0
> Dependency aeson-pretty >=0.8.0: using aeson-pretty-0.8.5
> Dependency attoparsec >=0.11.1.0: using attoparsec-0.13.2.2
> Dependency authenticate-oauth >=1.5: using authenticate-oauth-1.6
> Dependency base >=4.5 && <5: using base-4.10.1.0
> Dependency base16-bytestring -any: using base16-bytestring-0.1.1.6
> Dependency base64-bytestring -any: using base64-bytestring-1.0.0.1
> Dependency bytestring >=0.9: using bytestring-0.10.8.2
> Dependency case-insensitive -any: using case-insensitive-1.2.0.11
> Dependency containers -any: using containers-0.5.10.2
> Dependency cryptonite -any: using cryptonite-0.25
> Dependency directory -any: using directory-1.3.0.2
> Dependency doctest -any: using doctest-0.13.0
> Dependency exceptions >=0.5: using exceptions-0.8.3
> Dependency filepath -any: using filepath-1.4.1.2
> Dependency ghc-prim -any: using ghc-prim-0.5.1.1
> Dependency hashable -any: using hashable-1.2.7.0
> Dependency http-client >=0.5.3.2: using http-client-0.5.12
> Dependency http-client-tls >=0.3.3: using http-client-tls-0.3.5.3
> Dependency http-types >=0.8: using http-types-0.12.1
> Dependency lens >=4.5: using lens-4.16.1
> Dependency lens-aeson -any: using lens-aeson-1.0.2
> Dependency memory -any: using memory-0.14.16
> Dependency mime-types -any: using mime-types-0.1.0.7
> Dependency network-info -any: using network-info-0.2.0.10
> Dependency psqueues >=0.2: using psqueues-0.2.6.0
> Dependency snap-core >=1.0.0.0: using snap-core-1.0.3.2
> Dependency snap-server >=0.9.4.4: using snap-server-1.1.0.0
> Dependency template-haskell -any: using template-haskell-2.12.0.0
> Dependency temporary -any: using temporary-1.2.1.1
> Dependency test-framework -any: using test-framework-0.8.2.0
> Dependency test-framework-hunit -any: using test-framework-hunit-0.3.0.2
> Dependency test-framework-quickcheck2 -any: using
> test-framework-quickcheck2-0.3.0.4
> Dependency text -any: using text-1.2.3.0
> Dependency time >=1.5: using time-1.8.0.2
> Dependency time-locale-compat -any: using time-locale-compat-0.1.1.4
> Dependency transformers -any: using transformers-0.5.2.0
> Dependency unix-compat -any: using unix-compat-0.5.0.1
> Dependency unordered-containers -any: using unordered-containers-0.2.9.0
> Dependency uuid -any: using uuid-1.3.13
> Dependency 

Bug#901185: remove unlisted bash dependecy

[Andreas Metzler]

On 2018-06-11 積丹尼 Dan Jacobson  wrote:
> Why use bash at all if e.g.,

> $ checkbashisms /usr/sbin/update-exim4.conf.template
> could not find any possible bashisms in bash script 
> /usr/sbin/update-exim4.conf.template

> means one can just use #!/bin/sh ?

Hello,

Exim, does use #!/bin/sh. However bash can provide /bin/sh (Run
"dpkg-reconfigure dash" to enable or disable), and bash5 is afaict
buggy, it is not /bin/sh-compliant. This specific bug severly breaks
scripting. It is not limited to exim, e.g. any debconf using package
has a good chance of breaking. 

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

Bug#901185: me too

[Andreas Metzler]

On 2018-06-11 Colin Watson  wrote:
> On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
[...] 
> > yes, resetting IFS to its default value in confmodule helps.

> Thanks.  For completeness, could you try this variant patch?  If shells
> are going to be unreliable about setting IFS in this way, then I'd
> rather just separate out the assignments altogether.
[snip]

Yes, this variant of the patch also works.

Thanks to your handholding we now have a minimal reproducer for the
issue:

(sid)ametzler@argenau:~$ cat /tmp/reproducer.sh
#!/bin/sh
set -e

list="item1 item2"

ls -l /bin/sh
printf "IFS=[%s]" "$IFS" | od -a

IFS='
' read -r dummy

printf "IFS=[%s]" "$IFS" | od -a
for i in $list ; do
echo $i
done
# Error with bash5:
(sid)ametzler@argenau:~$ echo xxx | /tmp/reproducer.sh
lrwxrwxrwx 1 root root 4 Jun 11 18:41 /bin/sh -> bash
000   I   F   S   =   [  sp  ht  nl   ]
011
000   I   F   S   =   [  nl   ]
007
item1 item2
#normal behavior with bash4 or dash:
(sid)ametzler@argenau:~$ echo xxx | /tmp/reproducer.sh
lrwxrwxrwx 1 root root 4 Jun 11 18:41 /bin/sh -> bash
000   I   F   S   =   [  sp  ht  nl   ]
011
000   I   F   S   =   [  sp  ht  nl   ]
011
item1
item2


> (This does still seem like a bash bug though, unless there's some arcane
> interpretation of the standards that I'm unaware of.)

Looking at the Open Group Base Specifications Issue 7 I also think this
behavior is a bug, since "read" is not a "a special built-in utility or
function".

cu Andreas

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

Bug#901041: marked as done (libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libviennacl-dev/README.gz)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 18:20:26 +
with message-id 
and subject line Bug#901041: fixed in viennacl 1.7.1+dfsg1-5
has caused the Debian Bug report #901041,
regarding libviennacl-doc: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/doc/libviennacl-dev/README.gz
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libviennacl-doc
Version: 1.7.1+dfsg1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libviennacl-doc.
  Preparing to unpack .../libviennacl-doc_1.7.1+dfsg1-3_all.deb ...
  Unpacking libviennacl-doc (1.7.1+dfsg1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libviennacl-doc_1.7.1+dfsg1-3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libviennacl-dev/README.gz', which is 
also in package libviennacl-dev 1.7.1+dfsg1-2

This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libviennacl-dev=1.7.1+dfsg1-2_libviennacl-doc=1.7.1+dfsg1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: viennacl
Source-Version: 1.7.1+dfsg1-5

We believe that the bug you reported is fixed in the latest version of
viennacl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated viennacl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jun 2018 19:57:01 +0200
Source: viennacl
Binary: libviennacl-dev libviennacl-doc
Architecture: source
Version: 1.7.1+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libviennacl-dev - Scientific computing library written in C++ based on OpenCL
 libviennacl-doc - ViennaCL API and user documentation
Closes: 901041
Changes:
 viennacl (1.7.1+dfsg1-5) unstable; urgency=medium
 .
   * [02bf939] Do not install README and changelog in -dev package. (Closes: 
#901041)
   * [394bb54] Remove changelog-file from -doc
   * [a549661] Update versions in Breaks/Replaces
Checksums-Sha1:
 79860829138d933a771c802d4dbc1c64a0b50ad1 2429 viennacl_1.7.1+dfsg1-5.dsc
 4f1082bcf664d187b7a7420ac022205097d0a951 1299640 
viennacl_1.7.1+dfsg1-5.debian.tar.xz
 41460bac3bdbb55bb95384b1ba2e7250f43b2a6c 10435 
viennacl_1.7.1+dfsg1-5_source.buildinfo
Checksums-Sha256:
 c874effbe7a267e70e2cf2271f01e17b9c6830226545b7821f184f47183ad4b1 2429 
viennacl_1.7.1+dfsg1-5.dsc
 f9179ce1e94a3761a0e987f00def73aa9482e2e21bcc1f7b45a83f94d0aff1c8 1299640 
viennacl_1.7.1+dfsg1-5.debian.tar.xz
 6e0c38fd5bb828f01f5a8719aa5498d17c366f8a1e196a08b99937dc2d6a8038 10435 
viennacl_1.7.1+dfsg1-5_source.buildinfo
Files:
 a28a79f0d627164c331dd2fa085cb970 2429 science optional 
viennacl_1.7.1+dfsg1-5.dsc
 6ede039a85c4065d92555fda96a936c0 1299640 science optional 
viennacl_1.7.1+dfsg1-5.debian.tar.xz
 e978496cc0230db40d4b7be5ae94b106 10435 science optional 
viennacl_1.7.1+dfsg1-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlseuEwACgkQ0+Fzg8+n
/wbdEg//cG++VW6psbrDK9pSuMVczvR7DGGa5TdsAZDwoDYrTQ2iYpV1P7E06qsm
+1oxe6LD3TrG6Sy7u/Xhjvux6P7DhosQBfF+rPbAOP5LULqSs/db5zVraeeR6p7S
S7XvmSmQDjiTIKjSg4Yyog79HUzDWS2Orye1ZOq8QO22oVssBaToS4eiyxvhmS5w
+hyszD/zdi0nd3qSmIp9k7KnfZXKfApPzotsnF1kgjQRUr4nFgNeepiKx3r45PLz
9T/h5oIGQC4zSPGdzW2H85LbKDAc9aWhemi73jXrtp7VFqKvcCq+pnG+TOgioaOy
sp63D+mhjc7ydY4Ytnp9GW34yCgBq58c9MuYb5iaTk6ij/51GwPhv6NolEA0lpU2

Bug#901041: libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libviennacl-dev/README.gz

[Anton Gladky]

Thanks, Andreas. My fault.

I hope the next upload will fix the issue. At least I can upgrade
the both packages without problem now.

Regards

Anton


2018-06-11 5:35 GMT+02:00 Andreas Beckmann :
> Followup-For: Bug #901041
> Control: found -1 1.7.1+dfsg1-4
>
> You fixed the wrong problem. The Breaks+Replaces may still be needed,
> but the underlying problem is not fixed - both libviennacl-dev and
> libviennacl-doc ship these files:
>
>   usr/share/doc/libviennacl-dev/README.gz
>   usr/share/doc/libviennacl-dev/changelog.gz
>
> This is most likely caused by a behavioral change in dh_installdocs
> in debhelper compat level 11.
>
> (Due to upload+testing timing I saw the buster->sid failure before the
> sid+sid failure).
>
>
> Andreas
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#901323: marked as done (pkg-haskell-tools: unsatisfiable build dependency: libghc-shake-dev (<< 0.16))

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 17:49:23 +
with message-id 
and subject line Bug#901323: fixed in pkg-haskell-tools 0.12
has caused the Debian Bug report #901323,
regarding pkg-haskell-tools: unsatisfiable build dependency: libghc-shake-dev 
(<< 0.16)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-haskell-tools
Version: 0.11.1
Severity: serious

This package can't be built from source on current sid/amd64: it build
depends on libghc-shake-dev (< 0.16) but sid has 0.16.4-2.

  # apt build-dep pkg-haskell-tools
  Reading package lists... Done
  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:
   builddeps:pkg-haskell-tools : Depends: libghc-shake-dev (< 0.16) but 
0.16.4-2 is to be installed
  E: Unable to correct problems, you have held broken packages.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: pkg-haskell-tools
Source-Version: 0.12

We believe that the bug you reported is fixed in the latest version of
pkg-haskell-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated pkg-haskell-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jun 2018 13:29:32 -0400
Source: pkg-haskell-tools
Binary: pkg-haskell-tools
Architecture: source
Version: 0.12
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 pkg-haskell-tools - Debian Haskell Group tools
Closes: 901323
Changes:
 pkg-haskell-tools (0.12) unstable; urgency=medium
 .
   * Port to shake 0.16.  closes: #901323.
Checksums-Sha1:
 3d1360c542f6f2d01ea9bddfc695b682f01bd957 2266 pkg-haskell-tools_0.12.dsc
 e16da1fdc52eb84e6a4c55b04e05369c243f62a4 20588 pkg-haskell-tools_0.12.tar.xz
 86526974c2b18e7c4fd18ee39f31050e363cc11a 7393 
pkg-haskell-tools_0.12_source.buildinfo
Checksums-Sha256:
 a721d81fa2e3075ea9e3b22dd6449519497485e00d1fdad92ceb8cc5d3a0e89b 2266 
pkg-haskell-tools_0.12.dsc
 08f9b33a99ebff5e1af2da534feaee51e1122c0c161f8ef50d08274b36eb7379 20588 
pkg-haskell-tools_0.12.tar.xz
 fd088afe338ba3f6705f6e0407b6e26eaba54a8bcae93d7b5be8dd2dc30734dc 7393 
pkg-haskell-tools_0.12_source.buildinfo
Files:
 4fa18a3d767747bc701e4b35c50ef7dd 2266 haskell optional 
pkg-haskell-tools_0.12.dsc
 7f3c81a57323a46c4690e0b8f73f53fa 20588 haskell optional 
pkg-haskell-tools_0.12.tar.xz
 1b0d57cc72b34a120ca9f7edf11b8575 7393 haskell optional 
pkg-haskell-tools_0.12_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian!

iQKlBAEBCgCPFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAlsesapfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1
ODFFQzg3NDA1M0U2QzgwNzc5MUI5QjU1OTIzMzFFMTk5RDM4QTgRHGNsaW50QGRl
Ymlhbi5vcmcACgkQVZIzHhmdOKiNJA/8D2JsGoG5OdtxN5FeIzlZUQYw+/fgG3xl
jxXwihopOCsM+fG+D8lfW/iIc2Z9ZtpGLhaYGpN95N8t1unMoqBWnlu30Jv3fOr2
2iuTxulGjOpjPnlfYe46llHqwA3Rr/Zunm/MlvdVhCFI/QxnPNlZZfBIPNymua5N
z/FQl4JtYJJf5mFv8DrlelqZeUhPGb5CKZLeNF7NrkTkNtpuzQOSMh9bh20T1Kpj
nZ/Zm2bb8lAyJunJclXk4OinE8uXWgyafgEgaFlZ2xEDivhgdpVRX96guRk+tIAz
90YCdXUPC2WlEql3yTDp60jM6x19Bum8vp7UZy9V4c7Mi6dfceTFhxm/+imCQq7X
YNP5KhfgY5G4Np05Biptw9T8LLkGV8BgGLek9oJDGUJAgWSHgSQMHvvi8zoZTI0C
XmWD71lZ8ubPn0gjMPTkOlbax+jEW2qNZHe+8RMxBCRwSYjNIbH/sI4xUWGPZP0a
EjiD66cEv7i3dD7J9SjBSMoGWRFDRcPl+0rHon2KbmxXxBvnNGp2SYaIUFhXWAjN
ImNLi+GbEyP1X9mmDM9nwONzMN6X5F/hpiPR5owMkmxPB6fgnXwJmGKFpYSCwnFc
SIQKRrQ3Gk/9TB3mre/dLFeSq2ViIgmXaJA/uRDY445xPqWFglC+zOfdSkLJXrE5
RO9dEfwURUg=
=RE1F
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package src:node-growl

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:node-growl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #900868 (http://bugs.debian.org/900868)
> # Bug title: node-growl: CVE-2017-16042: Does not properly sanitize input 
> before passing it to exec
> #  * https://github.com/tj/node-growl/issues/60
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 900868 + fixed-upstream
Bug #900868 [src:node-growl] node-growl: CVE-2017-16042: Does not properly 
sanitize input before passing it to exec
Added tag(s) fixed-upstream.
> usertags 900868 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
900868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2018-06-11 17:52:55)
> Quoting Guido Günther (2018-06-11 16:05:46)
> > On Mon, Jun 11, 2018 at 03:52:55PM +0200, Jonas Smedegaard wrote:
> > > Quoting Guido Günther (2018-06-11 15:02:06)
> > > > Hi,
> > > > On Mon, Jun 11, 2018 at 02:10:52PM +0200, Jonas Smedegaard wrote:
> > > > > Quoting Guido Günther (2018-06-11 13:32:34)
> > > > > > Hi,
> > > > > > On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> > > > > > > Quoting Guido Günther (2018-06-11 11:07:33)
> > > > > > > > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > > > > > > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard 
> > > > > > > > > wrote:
> > > > > > > > > > "gbp import-orig --uscan" seems to choke on tarballs 
> > > > > > > > > > repacked by uscan.
> > > > > > > > > > 
> > > > > > > > > > With the attached debian files - changelog, copyright, and 
> > > > > > > > > > watch, in an freshly created git project (i.e. just "git 
> > > > > > > > > > init"), doing "gbp import-orig --uscan" will succeed but 
> > > > > > > > > > the resulting project wil be missing the subdirectories 
> > > > > > > > > > translations and utils.
> > > > > > > > > > 
> > > > > > > > > > Doing same without the copyright file will have all files 
> > > > > > > > > > imported.
> > > > > > > > > > 
> > > > > > > > > > The repacked tarball do contain the subdirectories, so it 
> > > > > > > > > > seems gbp chokes on it for some reason.
> > > [...]
> > > > > > The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" 
> > > > > > does
> > > > > > not contain the directories you mention. When I run this:
> > > > > > 
> > > > > > $ git branch upstream
> > > > > > $ gbp import-orig -v --merge-mode=replace 
> > > > > > --postimport=/bin/true --no-pristine-tar --no-sign --uscan
> > > > > > … 
> > > > > > $ DIRS='translations|utils' ; tar -list -af 
> > > > > > monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo 
> > > > > > "${DIRS} not found"
> > > > > > translations|utils not found
> > > > > > 
> > > > > > Can you show me what I'm missing to reproduce this?
> > > > > 
> > > > > Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
> > > > > apparently that can parse tarballs that tar cannot.
> > > > > 
> > > > > Seems this is an issue of corrupted tarball, then.
> > > > > 
> > > > > I now found a commandline tool that confirms that the dirs exist:  
> > > > > Can 
> > > > > you try confirm by installing package pax and running this command:
> > > > > 
> > > > >   paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'
> > > > > 
> > > > > At my end, that outputs the following:
> > > > > 
> > > > > -rw-rw-r--  1 root root195575 Jun  3 18:41 
> > > > > monero-0.12.2.0/translations/monero.ts
> > > > > -rw-rw-r--  1 root root230673 Jun  3 18:41 
> > > > > monero-0.12.2.0/translations/monero_fr.ts
> > > > > -rw-rw-r--  1 root root204343 Jun  3 18:41 
> > > > > monero-0.12.2.0/translations/monero_it.ts
> > > > > -rw-rw-r--  1 root root224691 Jun  3 18:41 
> > > > > monero-0.12.2.0/translations/monero_sv.ts
> > > >
> > > > Yeah, I see these with paxtar
> > > 
> > > Good, so I am not dreaming here.  That's progress!
> > > 
> > > 
> > > > but given that dpkg (AFAIK) uses plain tar I wonder if there's a bug 
> > > > here?
> > > 
> > > I see potentially two bugs:
> > > 
> > >  a) Creating a tarball that is unparsable by Debian /bin/tar
> > > 
> > >  b) Wrongly parsing tarball with /bin/tar which other tools can parse.
> > > 
> > > Since git-buildpackage does not create any tarball here (uscan did it), 
> > > I suggest that we reuse this bugreport for b) and create a new bugreport 
> > > for a).
> > > 
> > > 
> > > > Can you dig out what makes these files different and if these are 
> > > > allowed by policy? I tried several of tar's -H options but this did 
> > > > not change anything and did not find anything related in Debian policy 
> > > > either.
> > > 
> > > Sorry, I don't understand your question.  Also, if it relates to a) then 
> > > please wait and I will file a separate bugreport for that.
> > > 
> > > 
> > > > What is monero using to create the tarball? I quick grep in the 
> > > > sources didn't bring anything up.
> > > 
> > > How upstream tarball was created might or might not matter - in any case 
> > > it is related to a), so please let me create another bugreport for that.
> > > 
> > > 
> > > First, do you agree it makes sense to separate a) into another separate 
> > > bugreport?  And discuss only b) here (and possibly reassign to tar)?
> > 
> > Yes. As I read it a) would need to be assigned to uscan (with affects:
> > git-buildpackage) and b) stays with gbp.
> >  -- Guido
> 
> Seems the bug was reported already: 831870
> 
> A workaround is mentioned - I will try if that works here too...

No, workaround seemingly only "worked" by shrinking the tarball to the 
part that didn't get mangled by 

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Quoting Guido Günther (2018-06-11 16:05:46)
> On Mon, Jun 11, 2018 at 03:52:55PM +0200, Jonas Smedegaard wrote:
> > Quoting Guido Günther (2018-06-11 15:02:06)
> > > Hi,
> > > On Mon, Jun 11, 2018 at 02:10:52PM +0200, Jonas Smedegaard wrote:
> > > > Quoting Guido Günther (2018-06-11 13:32:34)
> > > > > Hi,
> > > > > On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> > > > > > Quoting Guido Günther (2018-06-11 11:07:33)
> > > > > > > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > > > > > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard 
> > > > > > > > wrote:
> > > > > > > > > "gbp import-orig --uscan" seems to choke on tarballs 
> > > > > > > > > repacked by uscan.
> > > > > > > > > 
> > > > > > > > > With the attached debian files - changelog, copyright, and 
> > > > > > > > > watch, in an freshly created git project (i.e. just "git 
> > > > > > > > > init"), doing "gbp import-orig --uscan" will succeed but 
> > > > > > > > > the resulting project wil be missing the subdirectories 
> > > > > > > > > translations and utils.
> > > > > > > > > 
> > > > > > > > > Doing same without the copyright file will have all files 
> > > > > > > > > imported.
> > > > > > > > > 
> > > > > > > > > The repacked tarball do contain the subdirectories, so it 
> > > > > > > > > seems gbp chokes on it for some reason.
> > [...]
> > > > > The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" does
> > > > > not contain the directories you mention. When I run this:
> > > > > 
> > > > > $ git branch upstream
> > > > > $ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
> > > > > --no-pristine-tar --no-sign --uscan
> > > > > … 
> > > > > $ DIRS='translations|utils' ; tar -list -af 
> > > > > monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo 
> > > > > "${DIRS} not found"
> > > > > translations|utils not found
> > > > > 
> > > > > Can you show me what I'm missing to reproduce this?
> > > > 
> > > > Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
> > > > apparently that can parse tarballs that tar cannot.
> > > > 
> > > > Seems this is an issue of corrupted tarball, then.
> > > > 
> > > > I now found a commandline tool that confirms that the dirs exist:  Can 
> > > > you try confirm by installing package pax and running this command:
> > > > 
> > > >   paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'
> > > > 
> > > > At my end, that outputs the following:
> > > > 
> > > > -rw-rw-r--  1 root root195575 Jun  3 18:41 
> > > > monero-0.12.2.0/translations/monero.ts
> > > > -rw-rw-r--  1 root root230673 Jun  3 18:41 
> > > > monero-0.12.2.0/translations/monero_fr.ts
> > > > -rw-rw-r--  1 root root204343 Jun  3 18:41 
> > > > monero-0.12.2.0/translations/monero_it.ts
> > > > -rw-rw-r--  1 root root224691 Jun  3 18:41 
> > > > monero-0.12.2.0/translations/monero_sv.ts
> > >
> > > Yeah, I see these with paxtar
> > 
> > Good, so I am not dreaming here.  That's progress!
> > 
> > 
> > > but given that dpkg (AFAIK) uses plain tar I wonder if there's a bug 
> > > here?
> > 
> > I see potentially two bugs:
> > 
> >  a) Creating a tarball that is unparsable by Debian /bin/tar
> > 
> >  b) Wrongly parsing tarball with /bin/tar which other tools can parse.
> > 
> > Since git-buildpackage does not create any tarball here (uscan did it), 
> > I suggest that we reuse this bugreport for b) and create a new bugreport 
> > for a).
> > 
> > 
> > > Can you dig out what makes these files different and if these are 
> > > allowed by policy? I tried several of tar's -H options but this did 
> > > not change anything and did not find anything related in Debian policy 
> > > either.
> > 
> > Sorry, I don't understand your question.  Also, if it relates to a) then 
> > please wait and I will file a separate bugreport for that.
> > 
> > 
> > > What is monero using to create the tarball? I quick grep in the 
> > > sources didn't bring anything up.
> > 
> > How upstream tarball was created might or might not matter - in any case 
> > it is related to a), so please let me create another bugreport for that.
> > 
> > 
> > First, do you agree it makes sense to separate a) into another separate 
> > bugreport?  And discuss only b) here (and possibly reassign to tar)?
> 
> Yes. As I read it a) would need to be assigned to uscan (with affects:
> git-buildpackage) and b) stays with gbp.
>  -- Guido

Seems the bug was reported already: 831870

A workaround is mentioned - I will try if that works here too...


 - Jonas

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

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


signature.asc
Description: signature

Bug#895469: openjfx FTBFS on armel: invalid instructions

[Emmanuel Bourg]

Le 11/06/2018 à 15:10, peter green a écrit :

> Debdiff for what I uploaded to raspbian is available at
> http://debdiffs.raspbian.org/main/o/openjfx/openjfx_8u141-b14-3%2brpi1.debdiff

Thanks a lot for the help Peter!

It looks like JSStringRef.cpp was eventually fixed upstream (at least in
OpenJFX 9.0.1+11 [1], but not on the 8u-dev branch yet).

I'll try to upload OpenJFX 8u171 with this patch before upgrading to
OpenJFX 11.

[1]
https://salsa.debian.org/java-team/openjfx9/blob/master/modules/javafx.web/src/main/native/Source/JavaScriptCore/API/JSStringRef.cpp#L65

Bug#901306: pandoc: FTBFS on armhf: ghc: panic

[John MacFarlane]

It would be worth reporting this as a bug to the ghc
tracker, as requested in the message.

Emilio Pozuelo Monfort  writes:

> Source: pandoc
> Version: 2.2.1-1
> Severity: serious
>
> pandoc now FTBFS on armhf with a ghc panic:
>
> [112 of 131] Compiling Text.Pandoc.Readers.HTML ( 
> src/Text/Pandoc/Readers/HTML.hs, dist-ghc/build/Text/Pandoc/Readers/HTML.p_o )
> ghc: panic! (the 'impossible' happened)
>   (GHC version 8.2.2 for arm-unknown-linux):
>   piResultTy
>   Addr#
>   String
>   Call stack:
>   CallStack (from HasCallStack):
> prettyCurrentCallStack, called at 
> compiler/utils/Outputable.hs:1133:58 in ghc:Outputable
> callStackDoc, called at compiler/utils/Outputable.hs:1137:37 in 
> ghc:Outputable
> pprPanic, called at compiler/types/Type.hs:949:35 in ghc:Type
>
> Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
>
> Full logs at https://buildd.debian.org/status/logs.php?pkg=pandoc=armhf
>
> Emilio

Bug#900912: openjdk-10: Accessibility does not get loaded

[Samuel Thibault]

Control: tags -1 + patch

Samuel Thibault, le lun. 11 juin 2018 15:17:05 +0200, a ecrit:
> be it a hardcoded classpath to java-atk-wrapper.jar.

For instance the attached patch works fine (and doesn't disturb the
headless case).

Samuel
Index: openjdk-10-10.0.1+10/src/hotspot/os/linux/os_linux.cpp
===
--- openjdk-10-10.0.1+10.orig/src/hotspot/os/linux/os_linux.cpp
+++ openjdk-10-10.0.1+10/src/hotspot/os/linux/os_linux.cpp
@@ -369,6 +369,7 @@ void os::init_system_properties_values()
 }
 Arguments::set_java_home(buf);
 set_boot_path('/', ':');
+Arguments::append_sysclasspath("/usr/share/java/java-atk-wrapper.jar");
   }
 
   // Where to look for native libraries.

Processed: Re: Bug#900912: openjdk-10: Accessibility does not get loaded

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #900912 [src:openjdk-10] openjdk-10: Accessibility does not get loaded
Added tag(s) patch.

-- 
900912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901103: marked as done (adios: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 14:39:24 +
with message-id 
and subject line Bug#901103: fixed in adios 1.13.1-3
has caused the Debian Bug report #901103,
regarding adios: FTBFS when built with dpkg-buildpackage -A
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:adios
Version: 1.13.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4'
configure.ac:20: installing 'config/compile'
configure.ac:14: installing 'config/missing'

[... snipped ...]

cp -a /<>/debian/tmpp/lib/$p/site-packages/* 
debian/tmp/usr/lib/python3/dist-packages ; \
done
mv 
/<>/debian/tmp/usr/lib/python2.7/dist-packages/adios_mpi/adios_mpi.so
 \
   
debian/tmp/usr/lib/python2.7/dist-packages/adios_mpi/adios_mpi.x86_64-linux-gnu.so
mv /<>/debian/tmp/usr/lib/python2.7/dist-packages/adios/adios.so \
   
debian/tmp/usr/lib/python2.7/dist-packages/adios/adios.x86_64-linux-gnu.so
# remove due to it not working in multi-arch;
rm -f  /<>/debian/tmp/usr/bin/adios_config.flags
# renamed as per Adios CCS issue #118716, Debbug #639257
mv /<>/debian/tmp/usr/bin/gpp.py 
/<>/debian/tmp/usr/bin/adiosxml2h
mv /<>/debian/tmp/usr/bin/skel_cat.py 
/<>/debian/tmp/usr/bin/skel_cat
mv /<>/debian/tmp/usr/bin/skel_extract.py 
/<>/debian/tmp/usr/bin/skel_extract
cp debian/adios_config /<>/debian/tmp/usr/bin/adios_config
rm -rf 
debian/libadios-examples/usr/share/doc/libadios-examples/examples/C/attributes/.libs
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples
if test -d debian/libadios-examples/usr/share/doc/libadios-examples/examples ; 
then \
find debian/libadios-examples/usr/share/doc/libadios-examples/examples 
-name '*.o' -delete  ; \
find 
debian/libadios-examples/usr/share/doc/libadios-examples/examples/C -type f 
-exec chmod -x {} \; ; \
fi 
make[1]: Leaving directory '/<>'
   dh_python2 -i
E: dh_python2 dh_python2:408: no package to act on (python-foo or one with 
${python:Depends} in Depends)
   dh_python3 -i
E: dh_python3 dh_python3:176: no package to act on (python3-foo or one with 
${python3:Depends} in Depends)
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod +x debian/libadios-bin/etc/adios/skel/templates/submit*.tpl
chmod: cannot access 
'debian/libadios-bin/etc/adios/skel/templates/submit*.tpl': No such file or 
directory
debian/rules:118: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
debian/rules:39: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_fixperms into override_dh_fixperms-indep and 
override_dh_fixperms-arch.

Thanks.
--- End Message ---
--- Begin Message ---
Source: adios
Source-Version: 1.13.1-3

We believe that the bug you reported is fixed in the latest version of
adios, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated adios package)

(This message was generated automatically at their request; if you
believe that there is a 

Bug#901327: tigervnc: FTBFS: Hunk #1 FAILED

[Niko Tyni]

Source: tigervnc
Version: 1.7.0+dfsg-8
Severity: serious

This package fails to build from source on current sid/amd64.

>From the build log:

  touch debian/stamp-patched
  /usr/bin/make -f debian/rules update-config
  make[1]: Entering directory '/<>/tigervnc-1.7.0+dfsg'
  make[1]: 'update-config' is up to date.
  make[1]: Leaving directory '/<>/tigervnc-1.7.0+dfsg'
  cd ./unix/xserver && \
{ tar --strip-components 1 -xvJf /usr/src/xorg-server.tar.xz | \
sed -e 's@^[^/]*/@@' > .apply-patches-unify-xorg-and-vnc-tree.files; } 
&& \
touch .apply-patches-unify-xorg-and-vnc-tree.stamp
  cd ./unix/xserver && { \
patch --no-backup-if-mismatch -p1 < 
/<>/tigervnc-1.7.0+dfsg/debian/xserver119.patch && \
touch .apply-patches-vnc-patch-xorg.stamp; \
  }
  patching file configure.ac
  Hunk #2 succeeded at 1778 (offset -86 lines).
  Hunk #3 succeeded at 1817 (offset -86 lines).
  Hunk #4 succeeded at 2036 (offset -87 lines).
  Hunk #5 succeeded at 2571 (offset -126 lines).
  patching file hw/Makefile.am
  patching file mi/miinitext.c
  Hunk #1 FAILED at 114.
  Hunk #2 succeeded at 109 (offset -129 lines).
  1 out of 2 hunks FAILED -- saving rejects to file mi/miinitext.c.rej
  patching file include/os.h
  Hunk #1 succeeded at 633 (offset 12 lines).
  make: *** [debian/rules:129: 
unix/xserver/.apply-patches-vnc-patch-xorg.stamp] Error 1
 
-- 
Niko Tyni   nt...@debian.org

Bug#892175: pycryptodome FTBFS on 32bit big endian: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' failed

[Petter Reinholdtsen]

The assert failure is in mont_mult(), which according to its own comment 
implements
https://en.wikipedia.org/wiki/Montgomery_modular_multiplication >.  If the
patch mentioned by James, which seem to add testing of the suspected functions 
and
modify their implementation quite a bit, do solve the problem, I notice a new
upstream version has been released since the commit was applied in March.

Perhaps upgrading to the latest upstream version will solve the problem?  Anyone
working on updating the package?

-- 
Happy hacking
Petter Reinholdtsen

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Guido Günther]

On Mon, Jun 11, 2018 at 03:52:55PM +0200, Jonas Smedegaard wrote:
> Quoting Guido Günther (2018-06-11 15:02:06)
> > Hi,
> > On Mon, Jun 11, 2018 at 02:10:52PM +0200, Jonas Smedegaard wrote:
> > > Quoting Guido Günther (2018-06-11 13:32:34)
> > > > Hi,
> > > > On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> > > > > Quoting Guido Günther (2018-06-11 11:07:33)
> > > > > > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > > > > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > > > > > > > "gbp import-orig --uscan" seems to choke on tarballs 
> > > > > > > > repacked by uscan.
> > > > > > > > 
> > > > > > > > With the attached debian files - changelog, copyright, and 
> > > > > > > > watch, in an freshly created git project (i.e. just "git 
> > > > > > > > init"), doing "gbp import-orig --uscan" will succeed but 
> > > > > > > > the resulting project wil be missing the subdirectories 
> > > > > > > > translations and utils.
> > > > > > > > 
> > > > > > > > Doing same without the copyright file will have all files 
> > > > > > > > imported.
> > > > > > > > 
> > > > > > > > The repacked tarball do contain the subdirectories, so it 
> > > > > > > > seems gbp chokes on it for some reason.
> [...]
> > > > The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" does
> > > > not contain the directories you mention. When I run this:
> > > > 
> > > > $ git branch upstream
> > > > $ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
> > > > --no-pristine-tar --no-sign --uscan
> > > > … 
> > > > $ DIRS='translations|utils' ; tar -list -af 
> > > > monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo 
> > > > "${DIRS} not found"
> > > > translations|utils not found
> > > > 
> > > > Can you show me what I'm missing to reproduce this?
> > > 
> > > Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
> > > apparently that can parse tarballs that tar cannot.
> > > 
> > > Seems this is an issue of corrupted tarball, then.
> > > 
> > > I now found a commandline tool that confirms that the dirs exist:  Can 
> > > you try confirm by installing package pax and running this command:
> > > 
> > >   paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'
> > > 
> > > At my end, that outputs the following:
> > > 
> > > -rw-rw-r--  1 root root195575 Jun  3 18:41 
> > > monero-0.12.2.0/translations/monero.ts
> > > -rw-rw-r--  1 root root230673 Jun  3 18:41 
> > > monero-0.12.2.0/translations/monero_fr.ts
> > > -rw-rw-r--  1 root root204343 Jun  3 18:41 
> > > monero-0.12.2.0/translations/monero_it.ts
> > > -rw-rw-r--  1 root root224691 Jun  3 18:41 
> > > monero-0.12.2.0/translations/monero_sv.ts
> >
> > Yeah, I see these with paxtar
> 
> Good, so I am not dreaming here.  That's progress!
> 
> 
> > but given that dpkg (AFAIK) uses plain tar I wonder if there's a bug 
> > here?
> 
> I see potentially two bugs:
> 
>  a) Creating a tarball that is unparsable by Debian /bin/tar
> 
>  b) Wrongly parsing tarball with /bin/tar which other tools can parse.
> 
> Since git-buildpackage does not create any tarball here (uscan did it), 
> I suggest that we reuse this bugreport for b) and create a new bugreport 
> for a).
> 
> 
> > Can you dig out what makes these files different and if these are 
> > allowed by policy? I tried several of tar's -H options but this did 
> > not change anything and did not find anything related in Debian policy 
> > either.
> 
> Sorry, I don't understand your question.  Also, if it relates to a) then 
> please wait and I will file a separate bugreport for that.
> 
> 
> > What is monero using to create the tarball? I quick grep in the 
> > sources didn't bring anything up.
> 
> How upstream tarball was created might or might not matter - in any case 
> it is related to a), so please let me create another bugreport for that.
> 
> 
> First, do you agree it makes sense to separate a) into another separate 
> bugreport?  And discuss only b) here (and possibly reassign to tar)?

Yes. As I read it a) would need to be assigned to uscan (with affects:
git-buildpackage) and b) stays with gbp.
 -- Guido

Bug#901323: pkg-haskell-tools: unsatisfiable build dependency: libghc-shake-dev (<< 0.16)

[Niko Tyni]

Package: pkg-haskell-tools
Version: 0.11.1
Severity: serious

This package can't be built from source on current sid/amd64: it build
depends on libghc-shake-dev (< 0.16) but sid has 0.16.4-2.

  # apt build-dep pkg-haskell-tools
  Reading package lists... Done
  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:
   builddeps:pkg-haskell-tools : Depends: libghc-shake-dev (< 0.16) but 
0.16.4-2 is to be installed
  E: Unable to correct problems, you have held broken packages.

-- 
Niko Tyni   nt...@debian.org

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Quoting Guido Günther (2018-06-11 15:02:06)
> Hi,
> On Mon, Jun 11, 2018 at 02:10:52PM +0200, Jonas Smedegaard wrote:
> > Quoting Guido Günther (2018-06-11 13:32:34)
> > > Hi,
> > > On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> > > > Quoting Guido Günther (2018-06-11 11:07:33)
> > > > > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > > > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > > > > > > "gbp import-orig --uscan" seems to choke on tarballs 
> > > > > > > repacked by uscan.
> > > > > > > 
> > > > > > > With the attached debian files - changelog, copyright, and 
> > > > > > > watch, in an freshly created git project (i.e. just "git 
> > > > > > > init"), doing "gbp import-orig --uscan" will succeed but 
> > > > > > > the resulting project wil be missing the subdirectories 
> > > > > > > translations and utils.
> > > > > > > 
> > > > > > > Doing same without the copyright file will have all files 
> > > > > > > imported.
> > > > > > > 
> > > > > > > The repacked tarball do contain the subdirectories, so it 
> > > > > > > seems gbp chokes on it for some reason.
[...]
> > > The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" does
> > > not contain the directories you mention. When I run this:
> > > 
> > > $ git branch upstream
> > > $ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
> > > --no-pristine-tar --no-sign --uscan
> > > … 
> > > $ DIRS='translations|utils' ; tar -list -af 
> > > monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo 
> > > "${DIRS} not found"
> > > translations|utils not found
> > > 
> > > Can you show me what I'm missing to reproduce this?
> > 
> > Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
> > apparently that can parse tarballs that tar cannot.
> > 
> > Seems this is an issue of corrupted tarball, then.
> > 
> > I now found a commandline tool that confirms that the dirs exist:  Can 
> > you try confirm by installing package pax and running this command:
> > 
> >   paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'
> > 
> > At my end, that outputs the following:
> > 
> > -rw-rw-r--  1 root root195575 Jun  3 18:41 
> > monero-0.12.2.0/translations/monero.ts
> > -rw-rw-r--  1 root root230673 Jun  3 18:41 
> > monero-0.12.2.0/translations/monero_fr.ts
> > -rw-rw-r--  1 root root204343 Jun  3 18:41 
> > monero-0.12.2.0/translations/monero_it.ts
> > -rw-rw-r--  1 root root224691 Jun  3 18:41 
> > monero-0.12.2.0/translations/monero_sv.ts
>
> Yeah, I see these with paxtar

Good, so I am not dreaming here.  That's progress!


> but given that dpkg (AFAIK) uses plain tar I wonder if there's a bug 
> here?

I see potentially two bugs:

 a) Creating a tarball that is unparsable by Debian /bin/tar

 b) Wrongly parsing tarball with /bin/tar which other tools can parse.

Since git-buildpackage does not create any tarball here (uscan did it), 
I suggest that we reuse this bugreport for b) and create a new bugreport 
for a).


> Can you dig out what makes these files different and if these are 
> allowed by policy? I tried several of tar's -H options but this did 
> not change anything and did not find anything related in Debian policy 
> either.

Sorry, I don't understand your question.  Also, if it relates to a) then 
please wait and I will file a separate bugreport for that.


> What is monero using to create the tarball? I quick grep in the 
> sources didn't bring anything up.

How upstream tarball was created might or might not matter - in any case 
it is related to a), so please let me create another bugreport for that.


First, do you agree it makes sense to separate a) into another separate 
bugreport?  And discuss only b) here (and possibly reassign to tar)?


 - Jonas

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

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


signature.asc
Description: signature

Bug#893861: thawab: Intent to remove from Debian

[Ahmed El-Mahmoudy]

On Thu, May 03, 2018 at 07:49:18AM -0400, Jeremy Bicha wrote:
> If we don't hear back immediately, I will be converting this bug into
> a Debian removal bug for thawab very soon.
---end quoted text---

Sorry for the late reply.
I have filed a bug upstream about this months ago. Still waiting for the 
reply.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Processed: Re: Bug#900912: openjdk-10: Accessibility does not get loaded

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #900912 [src:openjdk-10] openjdk-10: Accessibility does not get loaded
Severity set to 'serious' from 'important'

-- 
900912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#895469: openjfx FTBFS on armel: invalid instructions

[peter green]

movw and movt are armv7 only, so this is also affecting Raspbian. To fix both 
armel and raspbian the conditional should be <7

I whipped up a patch for that. I then ran into another issue, the compiler was 
bitching about uint16_t vs char16_t issues so I whipped up a patch for that too.

Debdiff for what I uploaded to raspbian is available at 
http://debdiffs.raspbian.org/main/o/openjfx/openjfx_8u141-b14-3%2brpi1.debdiff 
. No intent to NMU in Debian.

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2018-06-11 14:10:52)
> Quoting Guido Günther (2018-06-11 13:32:34)
>> On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
>>> Quoting Guido Günther (2018-06-11 11:07:33)
 On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
>> "gbp import-orig --uscan" seems to choke on tarballs repacked by 
>> uscan.
[...]
>> The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" 
>> does not contain the directories you mention. When I run this:
>> 
>> $ git branch upstream
>> $ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
>> --no-pristine-tar --no-sign --uscan
>> … 
>> $ DIRS='translations|utils' ; tar -list -af 
>> monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo "${DIRS} 
>> not found"
>> translations|utils not found
>> 
>> Can you show me what I'm missing to reproduce this?
>
> Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
> apparently that can parse tarballs that tar cannot.
> 
> Seems this is an issue of corrupted tarball, then.
> 
> I now found a commandline tool that confirms that the dirs exist: Can 
> you try confirm by installing package pax and running this command:
> 
>   paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'

Another options: Install libarchive-extract-perl and run this:

  perl -MArchive::Extract -e '$ae = Archive::Extract->new( archive => 
"monero_0.12.2.0~dfsg.orig.tar.gz" ); $ae->extract(to => "outdir")'
  ls outdir/monero-0.12.2.0/translations/


 - Jonas

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

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


signature.asc
Description: signature

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Guido Günther]

Hi,
On Mon, Jun 11, 2018 at 02:10:52PM +0200, Jonas Smedegaard wrote:
> Quoting Guido Günther (2018-06-11 13:32:34)
> > Hi,
> > On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> > > Quoting Guido Günther (2018-06-11 11:07:33)
> > > > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > > > > > Package: git-buildpackage
> > > > > > Version: 0.9.9
> > > > > > Severity: grave
> > > > > > Justification: causes non-serious data loss
> > > > > > 
> > > > > > -BEGIN PGP SIGNED MESSAGE-
> > > > > > Hash: SHA512
> > > > > > 
> > > > > > "gbp import-orig --uscan" seems to choke on tarballs repacked by 
> > > > > > uscan.
> > > > > > 
> > > > > > With the attached debian files - changelog, copyright, and watch, 
> > > > > > in an freshly created git project (i.e. just "git init"), doing 
> > > > > > "gbp import-orig --uscan" will succeed but the resulting project 
> > > > > > wil be missing the subdirectories translations and utils.
> > > > > > 
> > > > > > Doing same without the copyright file will have all files 
> > > > > > imported.
> > > > > > 
> > > > > > The repacked tarball do contain the subdirectories, so it seems 
> > > > > > gbp chokes on it for some reason.
> > > > > 
> > > > > I rather assume thath the copyright file instructs uscan to filter 
> > > > > these out?
> > > > 
> > > > Oh...and as always: please provide data to reproduce the problem. Your 
> > > > package is certainly not the first to be imported with --uscan and 
> > > > since it works for some setups it would be good to have your test case 
> > > > to find out what's different.
> > > 
> > > I believe I did exactly that: Provide files to reproduce the problem.
> > 
> > I was expecting a git URL and overread the "attached", found the files
> > now, sorry for the confusion.
> > 
> > > Could you elaborate which kind of files you would like me to provide?
> > 
> > The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" does
> > not contain the directories you mention. When I run this:
> > 
> > $ git branch upstream
> > $ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
> > --no-pristine-tar --no-sign --uscan
> > … 
> > $ DIRS='translations|utils' ; tar -list -af 
> > monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo 
> > "${DIRS} not found"
> > translations|utils not found
> > 
> > Can you show me what I'm missing to reproduce this?
> 
> Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
> apparently that can parse tarballs that tar cannot.
> 
> Seems this is an issue of corrupted tarball, then.
> 
> I now found a commandline tool that confirms that the dirs exist:  Can 
> you try confirm by installing package pax and running this command:
> 
>   paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'
> 
> At my end, that outputs the following:
> 
> -rw-rw-r--  1 root root195575 Jun  3 18:41 
> monero-0.12.2.0/translations/monero.ts
> -rw-rw-r--  1 root root230673 Jun  3 18:41 
> monero-0.12.2.0/translations/monero_fr.ts
> -rw-rw-r--  1 root root204343 Jun  3 18:41 
> monero-0.12.2.0/translations/monero_it.ts
> -rw-rw-r--  1 root root224691 Jun  3 18:41 
> monero-0.12.2.0/translations/monero_sv.ts

Yeah, I see these with paxtar but given that dpkg (AFAIK) uses plain tar
I wonder if there's a bug here? Can you dig out what makes these files
different and if these are allowed by policy? I tried several of tar's
-H options but this did not change anything and did not find anything
related in Debian policy either.

What is monero using to create the tarball? I quick grep in the sources
didn't bring anything up.

 -- Guido

Processed: patch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 899959 + patch
Bug #899959 [src:bind9] bind9: Invalid maintainer address 
pkg-dns-de...@lists.alioth.debian.org
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
899959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899959: bind9: Invalid maintainer address pkg-dns-de...@lists.alioth.debian.org

[Robie Basak]

Fix proposed in:

https://salsa.debian.org/dns-team/bind9/merge_requests/3


signature.asc
Description: PGP signature

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Quoting Guido Günther (2018-06-11 13:32:34)
> Hi,
> On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> > Quoting Guido Günther (2018-06-11 11:07:33)
> > > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > > > > Package: git-buildpackage
> > > > > Version: 0.9.9
> > > > > Severity: grave
> > > > > Justification: causes non-serious data loss
> > > > > 
> > > > > -BEGIN PGP SIGNED MESSAGE-
> > > > > Hash: SHA512
> > > > > 
> > > > > "gbp import-orig --uscan" seems to choke on tarballs repacked by 
> > > > > uscan.
> > > > > 
> > > > > With the attached debian files - changelog, copyright, and watch, 
> > > > > in an freshly created git project (i.e. just "git init"), doing 
> > > > > "gbp import-orig --uscan" will succeed but the resulting project 
> > > > > wil be missing the subdirectories translations and utils.
> > > > > 
> > > > > Doing same without the copyright file will have all files 
> > > > > imported.
> > > > > 
> > > > > The repacked tarball do contain the subdirectories, so it seems 
> > > > > gbp chokes on it for some reason.
> > > > 
> > > > I rather assume thath the copyright file instructs uscan to filter 
> > > > these out?
> > > 
> > > Oh...and as always: please provide data to reproduce the problem. Your 
> > > package is certainly not the first to be imported with --uscan and 
> > > since it works for some setups it would be good to have your test case 
> > > to find out what's different.
> > 
> > I believe I did exactly that: Provide files to reproduce the problem.
> 
> I was expecting a git URL and overread the "attached", found the files
> now, sorry for the confusion.
> 
> > Could you elaborate which kind of files you would like me to provide?
> 
> The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" does
> not contain the directories you mention. When I run this:
> 
> $ git branch upstream
> $ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
> --no-pristine-tar --no-sign --uscan
> … 
> $ DIRS='translations|utils' ; tar -list -af 
> monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo "${DIRS} 
> not found"
> translations|utils not found
> 
> Can you show me what I'm missing to reproduce this?

Oh - I use Midnight Commander (package mc) to inspect tarballs, and 
apparently that can parse tarballs that tar cannot.

Seems this is an issue of corrupted tarball, then.

I now found a commandline tool that confirms that the dirs exist:  Can 
you try confirm by installing package pax and running this command:

  paxtar tvzf monero_0.12.2.0~dfsg.orig.tar.gz '*.ts'

At my end, that outputs the following:

-rw-rw-r--  1 root root195575 Jun  3 18:41 
monero-0.12.2.0/translations/monero.ts
-rw-rw-r--  1 root root230673 Jun  3 18:41 
monero-0.12.2.0/translations/monero_fr.ts
-rw-rw-r--  1 root root204343 Jun  3 18:41 
monero-0.12.2.0/translations/monero_it.ts
-rw-rw-r--  1 root root224691 Jun  3 18:41 
monero-0.12.2.0/translations/monero_sv.ts


Using Midnight Commander, I can copy out those files, so it is not bogus 
listings.  I just don't know how to do that with commandline tools.


> (Note that I've specified the merge mode explicitly since your package 
> does not provide a debian/source/format and so 1.0 is assumed which 
> merges upstream to master thereby (correctly) reverting your debian/ 
> dir (since is not contained in upsream/ and they have the same parent) 
> - but this is unrelated to your issue).

Thanks for mentioning!

 - Jonas

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

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


signature.asc
Description: signature

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Guido Günther]

Hi,
On Mon, Jun 11, 2018 at 11:59:58AM +0200, Jonas Smedegaard wrote:
> Quoting Guido Günther (2018-06-11 11:07:33)
> > On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> > > On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > > > Package: git-buildpackage
> > > > Version: 0.9.9
> > > > Severity: grave
> > > > Justification: causes non-serious data loss
> > > > 
> > > > -BEGIN PGP SIGNED MESSAGE-
> > > > Hash: SHA512
> > > > 
> > > > "gbp import-orig --uscan" seems to choke on tarballs repacked by 
> > > > uscan.
> > > > 
> > > > With the attached debian files - changelog, copyright, and watch, 
> > > > in an freshly created git project (i.e. just "git init"), doing 
> > > > "gbp import-orig --uscan" will succeed but the resulting project 
> > > > wil be missing the subdirectories translations and utils.
> > > > 
> > > > Doing same without the copyright file will have all files 
> > > > imported.
> > > > 
> > > > The repacked tarball do contain the subdirectories, so it seems 
> > > > gbp chokes on it for some reason.
> > > 
> > > I rather assume thath the copyright file instructs uscan to filter 
> > > these out?
> > 
> > Oh...and as always: please provide data to reproduce the problem. Your 
> > package is certainly not the first to be imported with --uscan and 
> > since it works for some setups it would be good to have your test case 
> > to find out what's different.
> 
> I believe I did exactly that: Provide files to reproduce the problem.

I was expecting a git URL and overread the "attached", found the files
now, sorry for the confusion.

> Could you elaborate which kind of files you would like me to provide?

The tarball generated by uscan "monero_0.12.2.0~dfsg.orig.tar.gz" does
not contain the directories you mention. When I run this:

$ git branch upstream
$ gbp import-orig -v --merge-mode=replace --postimport=/bin/true 
--no-pristine-tar --no-sign --uscan
… 
$ DIRS='translations|utils' ; tar -list -af 
monero_0.12.2.0~dfsg.orig.tar.gz | grep -qs -E "(${DIRS})/" || echo "${DIRS} 
not found"
translations|utils not found

Can you show me what I'm missing to reproduce this?

(Note that I've specified the merge mode explicitly since your package
does not provide a debian/source/format and so 1.0 is assumed which
merges upstream to master thereby (correctly) reverting your debian/ dir
(since is not contained in upsream/ and they have the same parent) - but
this is unrelated to your issue).

Cheers,
 -- Guido

Processed: Re: Bug#901312: elastix does not start: symbol lookup error: elastix: undefined symbol: _ZN8vnl_math5hypotEd

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.8-12
Bug #901312 [elastix] elastix does not start: symbol lookup error: elastix: 
undefined symbol: _ZN8vnl_math5hypotEd
Marked as fixed in versions elastix/4.8-12.
> retitle -1 elastix does not start: symbol lookup error: elastix: undefined 
> symbol: _ZN8vnl_math5hypotEdd
Bug #901312 [elastix] elastix does not start: symbol lookup error: elastix: 
undefined symbol: _ZN8vnl_math5hypotEd
Changed Bug title to 'elastix does not start: symbol lookup error: elastix: 
undefined symbol: _ZN8vnl_math5hypotEdd' from 'elastix does not start: symbol 
lookup error: elastix: undefined symbol: _ZN8vnl_math5hypotEd'.

-- 
901312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901312: elastix does not start: symbol lookup error: elastix: undefined symbol: _ZN8vnl_math5hypotEd

[Juhani Numminen]

Control: fixed -1 4.8-12
Control: retitle -1 elastix does not start: symbol lookup error: elastix: 
undefined symbol: _ZN8vnl_math5hypotEdd

Hi,

I'm not seeing this failure in buster (with the the newer ITK-4.12).
Unfortunately I don't know how to test if the program actually works
beyond not crashing at startup.

Bug retitled because on stretch, I am seeing the error, but I get
two d's in the error message: "...Edd" instead of "...Ed".

--
Juhani


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

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

Versions of packages elastix depends on:
ii  libc6  2.27-3
ii  libgcc11:8.1.0-5
ii  libgdcm2.8 2.8.6-2
ii  libgomp1   8.1.0-5
ii  libinsighttoolkit4.12  4.12.2-dfsg1-2
ii  libstdc++6 8.1.0-5
ii  zlib1g 1:1.2.11.dfsg-1

elastix recommends no packages.

Versions of packages elastix suggests:
pn  elastix-doc  

-- no debconf information

Bug#897239: What about new upstream version of relion?

[Andreas Tille]

Hi folks,

when I tried to fix this bug I realised that new upstream versions are
out.  I downloaded the latest one and imported it into Git[1].  Since I
don't know the software I would like to ask you about your reasons you
might have to stick to version 1.4.  There are some patches to fix and
may be some tests to do which I can't.  So may be if I do not hear from
you I'd probably only go with the restriction of architectures to
amd64/i386 to fix #897239.

Kind regards

  Andreas.

[1] https://salsa.debian.org/med-team/relion

-- 
http://fam-tille.de

Bug#900533: chromium: Still exits in 68.0.3440.7-1

[Justin P.]

Package: chromium
Version: 68.0.3440.7-1
Followup-For: Bug #900533

--- Chromium debug log browsing youtube ---

Setting up chromium (68.0.3440.7-1) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
s0m3f00l@Cumulus-deb:~$ chromium
[5140:5346:0611/061317.394966:ERROR:object_proxy.cc(616)] Failed to call 
method: org.freedesktop.Notifications.GetCapabilities: object_path= 
/org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.Notifications was not provided by any .service files
[5140:5140:0611/061317.839680:ERROR:background_mode_manager_aura.cc(14)] Not 
implemented reached in virtual void 
BackgroundModeManager::EnableLaunchOnStartup(bool)
[5140:5170:0611/061318.462403:ERROR:connection.cc(1890)] Passwords sqlite error 
2067, errno 0: UNIQUE constraint failed: logins.origin_url, 
logins.username_element, logins.username_value, logins.password_element, 
logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url, 
username_element, username_value, password_element, password_value, 
submit_element, signon_realm, preferred, date_created, blacklisted_by_user, 
scheme, password_type, times_used, form_data, date_synced, display_name, 
icon_url, federation_url, skip_zero_click, generation_upload_status, 
possible_username_pairs) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
[5140:5140:0611/061319.441272:ERROR:display_info_provider.cc(175)] Not 
implemented reached in virtual void 
extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const 
display::Display&, extensions::api::system_display::DisplayUnitInfo*)
[98:136:0611/061326.971352:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:136:0611/061326.971603:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/061326.972184:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:98:0611/061326.973008:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:136:0611/061326.979177:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/061326.979617:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[121:151:0611/061335.811354:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[121:121:0611/061335.867090:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[121:151:0611/061336.600994:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[121:121:0611/061336.603162:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  68.0.3440.7-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libavcodec57 7:3.4.2-2+b1
ii  libavformat577:3.4.2-2+b1
ii  libavutil55  7:3.4.2-2+b1
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcups2 2.2.8-2
ii  libdbus-1-3  1.12.8-3
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-5
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libharfbuzz0b1.7.6-1+b1
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.37.1-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libpng16-16  1.6.34-1
ii  libpulse011.1-5
ii  libre2-4 20180301+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.1.0-5
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1   

Bug#812243: marked as done (zypper symbol not defined: symbol _ZN4zypp5CpeId11NoThrowType13lastMalformedE)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 10:19:56 +
with message-id 
and subject line Bug#812243: fixed in zypper 1.14.6-1
has caused the Debian Bug report #812243,
regarding zypper symbol not defined: symbol 
_ZN4zypp5CpeId11NoThrowType13lastMalformedE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
812243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zypper
Version: 1.12.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Installing zypper.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Simply running zypper fails:

mcgrof@garbanzo ~ $ zypper
zypper: relocation error: zypper: symbol 
_ZN4zypp5CpeId11NoThrowType13lastMalformedE, version ZYPP_plain not
defined in file libzypp.so.1503 with link time reference

   * What was the outcome of this action?

zypper fails to run.

   * What outcome did you expect instead?

For it to work.


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

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

Versions of packages zypper depends on:
ii  libaugeas0 1.2.0-0.2
ii  libc6  2.19-22
ii  libgcc11:5.2.1-21
ii  libreadline6   6.3-8+b3
ii  libstdc++6 5.2.1-21
ii  libzypp15.3.0-1+b1
ii  python 2.7.9-1
ii  zypper-common  1.12.4-1

zypper recommends no packages.

zypper suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: zypper
Source-Version: 1.14.6-1

We believe that the bug you reported is fixed in the latest version of
zypper, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated zypper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Jun 2018 11:35:49 +0200
Source: zypper
Binary: zypper zypper-common zypper-doc
Architecture: source
Version: 1.14.6-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Mike Gabriel 
Description:
 zypper - command line software manager using libzypp
 zypper-common - command line software manager using libzypp (common files)
 zypper-doc - command line software manager using libzypp (documentation)
Closes: 812243 849982
Changes:
 zypper (1.14.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control:
 + Bump Standards-Version: to 4.1.4. No changes needed.
 + Update Vcs-*: fields. Packaging Git has been migrated to 
salsa.debian.org.
 + Add S (zypper): zypper-doc. (Closes: 849982).
 + Switch to versioned B-D on libzypp (>= 17.0.2). (Closes: #812243).
 + Switch from Priority: extra to optional.
 + Add B-D: asciidoctor.
   * debian/{control,compat}:
 + Bump to DH compat level 10.
   * debian/rules: Create orig tarball in ../ rather then $(CURDIR).
 + Enable unit testing at build time.
 + Avoid using dpkg-parsechangelog.
 + Enable all hardening flags.
 + Move bash completion files to /usr/share/bash-completion/completions/.
   Drop .sh file suffix.
   * debian/{rules,zypper.examples}:
 + Don't install zypper wrapper scripts to replace APT to /usr/bin, rather
   ship them as examples.
   * debian/copyright:
 + Use secure URI to obtain copyright references.
 + Update copyright attributions.
 + Regenerate copyright.in for this upstream release.
   * debian/patches:
 + Drop 1003_fix-spelling-errors.patch. Applied upstream.
 + Add 2001_build-tests-with-all.patch. Upstream's ctest build target does
   not trigger the test code build. Dirty work around is building test code
   with the all target.
 + Add 2002_locale-workaround-in-unit-tests.patch. Work around failing unit
   test (Test #3: text_test) due to non-configured locales in sbuild build
   

Bug#900533: chromium: This Bug still exits in Source-Version: 67.0.3396.79-2 I get the same errors

[Justin P.]

Package: chromium
Version: 67.0.3396.79-1
Followup-For: Bug #900533

Dear Maintainer,

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

   * What led up to the situation?
Upgraded from upgrading from 66.0.3359.181-1 to 67.0.3396.79-1

Can't use video on youtube. Gif's no longer work. And I cannot get media to 
play.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Reverted to 66.0.3359.181-1

   * What was the outcome of this action?

Media works again

   * What outcome did you expect instead?

Media should work in 66.0.3359.181-1

--Chromium Bug Log browsing youtube-- 

Debian@PC-deb:~$ chromium
[3314:3521:0611/060922.753881:ERROR:object_proxy.cc(617)] Failed to call 
method: org.freedesktop.Notifications.GetCapabilities: object_path= 
/org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.Notifications was not provided by any .service files
[3314:3314:0611/060923.089406:ERROR:background_mode_manager_aura.cc(13)] Not 
implemented reached in virtual void 
BackgroundModeManager::EnableLaunchOnStartup(bool)
[3314:3343:0611/060923.676483:ERROR:connection.cc(1888)] Passwords sqlite error 
2067, errno 0: UNIQUE constraint failed: logins.origin_url, 
logins.username_element, logins.username_value, logins.password_element, 
logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url, 
username_element, username_value, password_element, password_value, 
submit_element, signon_realm, preferred, date_created, blacklisted_by_user, 
scheme, password_type, times_used, form_data, date_synced, display_name, 
icon_url, federation_url, skip_zero_click, generation_upload_status, 
possible_username_pairs) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
[3314:3314:0611/060924.411617:ERROR:display_info_provider.cc(189)] Not 
implemented reached in virtual void 
extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const 
display::Display&, extensions::api::system_display::DisplayUnitInfo*)
[98:144:0611/060931.047056:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/060931.047624:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:144:0611/060931.053916:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/060931.054403:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:144:0611/060931.054651:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/060931.055432:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[127:160:0611/060936.821264:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[127:127:0611/060936.876064:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[127:160:0611/060937.479760:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[127:127:0611/060937.481080:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  67.0.3396.79-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libavcodec57 7:3.4.2-2+b1
ii  libavformat577:3.4.2-2+b1
ii  libavutil55  7:3.4.2-2+b1
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcups2 2.2.8-2
ii  libdbus-1-3  1.12.8-3
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-5
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libharfbuzz0b1.7.6-1+b1
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.37.1-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libpng16-16  1.6.34-1
ii  libpulse011.1-5
ii  libre2-4 

Bug#812243: Bug #812243 in zypper marked as pending

[mike . gabriel]

Control: tag -1 pending

Hello,

Bug #812243 in zypper reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/debian/zypper/commit/c4992a481395d1683ba2ab2069867ff0444f5d48


debian/control: Switch to versioned B-D on libzypp (>= 17.0.2). (Closes: 
#812243).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/812243

Processed: Bug #812243 in zypper marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #812243 [zypper] zypper symbol not defined: symbol 
_ZN4zypp5CpeId11NoThrowType13lastMalformedE
Added tag(s) pending.

-- 
812243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901243: nm-applet

[Mike Gabriel]

Hi,

On  Mo 11 Jun 2018 00:17:40 CEST, Le Déchaîné wrote:


I'm guessing it's the same for nm-applet. I got no network manager
applet and trash applet either. System/Preferences is kinda empty too.

It may be the reason why I have to login and "startx" now (well...
sudo ifconfig eth0 up, sudo dhclient, and then startx).

Some interesting logs/crash.

Syslog:
Jun 10 06:48:26 symphony systemd[1]: Reloading.
Jun 10 06:48:27 symphony systemd[1]: Stopping Light Display Manager...
Jun 10 06:48:27 symphony at-spi-bus-launcher[1407]: XIO:  fatal IO
error 11 (Resource temporarily unavailable) on X server ":0"
Jun 10 06:48:27 symphony at-spi-bus-launcher[1407]:   after 82277
requests (82277 known processed) with 0 events remaining.
Jun 10 06:48:27 symphony pulseaudio[1446]: ICE default IO error
handler doing an exit(), pid = 1446, errno = 11
Jun 10 06:48:27 symphony trashapplet[1468]: trashapplet: Fatal IO
error 11 (Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Main
process exited, code=exited, status=1/FAILURE
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Failed
with result 'exit-code'.
Jun 10 06:48:27 symphony [1469]: wnck-applet: Fatal IO error 11
(Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony mate-multiload-[1559]: mate-multiload-applet:
Fatal IO error 11 (Ressource temporairement non disponible) on X
server :0.
Jun 10 06:48:27 symphony notification-ar[1560]:
notification-area-applet: Fatal IO error 11 (Ressource temporairement
non disponible) on X server :0.
Jun 10 06:48:27 symphony clock-applet[1561]: clock-applet: Fatal IO
error 11 (Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Service
hold-off time over, scheduling restart.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Scheduled
restart job, restart counter is at 1.
Jun 10 06:48:27 symphony systemd[1361]: Stopped Sound Service.
Jun 10 06:48:27 symphony systemd[1361]: Starting Sound Service...
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15179 of process 15179 (n/a) owned by '1000' high priority at nice
level -11.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 1 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony pulseaudio[15179]: W: [pulseaudio] pid.c:
Stale PID file, overwriting.
Jun 10 06:48:27 symphony systemd[1]: Stopped Light Display Manager.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 1 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15180 of process 15179 (n/a) owned by '1000' RT at priority 5.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 2 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 2 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15181 of process 15179 (n/a) owned by '1000' RT at priority 5.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 3 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony pulseaudio[15179]: E: [pulseaudio]
bluez5-util.c: GetManagedObjects() failed:
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2
matched rules; type="method_call", sender=":1.338" (uid=1000 pid=15179
comm="/usr/bin/pulseaudio --daemonize=no ")
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" error name="(unset)" requested_reply="0"
destination="org.bluez" (bus)
Jun 10 06:48:27 symphony systemd[1361]: Started Sound Service.
(...)
Messages:
Jun 10 06:49:49 symphony NetworkManager[764]: 
[1528627789.7842] caught SIGTERM, shutting down normally.
Jun 10 06:49:49 symphony NetworkManager[764]: 
[1528627789.8243] exiting (success)

(Also in syslog...)
Jun 10 10:37:20 symphony dhclient[18150]: execve
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): No such file or
directory
(...)
Jun 10 16:56:52 symphony kernel: [196727.991463] traps:
mate-settings-d[18477] trap int3 ip:7f4e5abb1c41 sp:7ffcaa1aa750
error:0 in libglib-2.0.so.0.5600.1[7f4e5ab6+113000]
Jun 10 16:56:53 symphony kernel: [196728.900334] traps:
mate-settings-d[18495] trap int3 ip:7f2a4f869c41 sp:7ffe5a9e7d00
error:0 in libglib-2.0.so.0.5600.1[7f2a4f818000+113000]
Jun 10 16:56:54 symphony wnck-applet[18502]: g_object_set: assertion
'G_IS_OBJECT (object)' failed
Jun 10 16:56:54 symphony clock-applet[18575]: Negative content width
-1 (allocation 1, extents 1x1) while allocating gadget (node button,
owner GtkToggleButton)
Jun 10 16:56:56 symphony notification-ar[18576]:
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object
path '/NO_DBUSMENU'


Sorry, this doesn't sound related to mate-indicator-applet to the  
asked-for build-dependency of this bug.


Please investigate a bit more ($HOME/.xsession-errors is your friend)  
and file a new bug. Not sure against what package, though.


Greets,
Mike
--

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Quoting Guido Günther (2018-06-11 11:04:51)
> On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > Package: git-buildpackage
> > Version: 0.9.9
> > Severity: grave
> > Justification: causes non-serious data loss
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > "gbp import-orig --uscan" seems to choke on tarballs repacked by uscan.
> > 
> > With the attached debian files - changelog, copyright, and watch, in an
> > freshly created git project (i.e. just "git init"), doing
> > "gbp import-orig --uscan" will succeed but the resulting project wil be
> > missing the subdirectories translations and utils.
> > 
> > Doing same without the copyright file will have all files imported.
> > 
> > The repacked tarball do contain the subdirectories, so it seems gbp
> > chokes on it for some reason.
> 
> I rather assume thath the copyright file instructs uscan to filter 
> these out?

No, the result of uscan filtering - the repacked tarball - still contain 
the subdirectories.  As I mention in my last sentence above.


 - Jonas

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

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


signature.asc
Description: signature

Bug#901118: marked as done (udunits: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 09:36:05 +
with message-id 
and subject line Bug#901118: fixed in udunits 2.2.26-5
has caused the Debian Bug report #901118,
regarding udunits: FTBFS when built with dpkg-buildpackage -A
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:udunits
Version: 2.2.26-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:78: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/missing'

[... snipped ...]

Output written on udunits2.pdf (13 pages, 168679 bytes).
Transcript written on udunits2.log.
make[3]: Leaving directory '/<>'
Making html in lib
make[3]: Entering directory '/<>/lib'
make[4]: Entering directory '/<>/lib'
make[4]: Nothing to be done for 'html-am'.
make[4]: Leaving directory '/<>/lib'
make[3]: Leaving directory '/<>/lib'
Making html in prog
make[3]: Entering directory '/<>/prog'
make[3]: Nothing to be done for 'html'.
make[3]: Leaving directory '/<>/prog'
make[3]: Entering directory '/<>'
rm -rf udunits2.htp
if /bin/bash /<>/build-aux/missing makeinfo --html --no-split  -I 
. \
 -o udunits2.htp udunits2.texi; \
then \
  rm -rf udunits2.html && mv udunits2.htp udunits2.html; \
else \
  rm -rf udunits2.htp; exit 1; \
fi
make[3]: Leaving directory '/<>'
Making info in lib
make[3]: Entering directory '/<>/lib'
make[4]: Entering directory '/<>/lib'
make[4]: Nothing to be done for 'info-am'.
make[4]: Leaving directory '/<>/lib'
make[3]: Leaving directory '/<>/lib'
Making info in prog
make[3]: Entering directory '/<>/prog'
make[3]: Nothing to be done for 'info'.
make[3]: Leaving directory '/<>/prog'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'info-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
cp udunits2.info debian/udunits-bin/usr/share/info
cp: cannot create regular file 'debian/udunits-bin/usr/share/info': No such 
file or directory
debian/rules:22: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.
--- End Message ---
--- Begin Message ---
Source: udunits
Source-Version: 2.2.26-5

We believe that the bug you reported is fixed in the latest version of
udunits, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated udunits package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Jun 2018 10:05:18 +0100
Source: udunits
Binary: libudunits2-0 libudunits2-data libudunits2-dev udunits-bin
Architecture: source amd64 all
Version: 2.2.26-5
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libudunits2-0 - Library for handling of units of physical quantities
 libudunits2-data - Data for handling of units of physical quantities
 libudunits2-dev - Development files for the libunits physical units package
 udunits-bin - Utility 

Bug#901312: elastix does not start: symbol lookup error: elastix: undefined symbol: _ZN8vnl_math5hypotEd

[Dietrich, Olaf Prof. Dr.rer.nat.]

Package: elastix
Version: 4.8-10
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Apparently, elastix cannot be run anymore:

  ~$ elastix
  elastix: symbol lookup error: elastix: undefined symbol: _ZN8vnl_math5hypotEd

There appears to be a problem with "vnl_math:hypot(double, double)".
vnl_math seems to be part of ITK-4.10 (libinsighttoolkit4).


   * What led up to the situation?

 installing and trying to run elastix

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 tried to re-install elastix and insighttoolkit-4.10
 (did not help, error still there)



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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_US:en 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages elastix depends on:
ii  libc6  2.24-11+deb9u3
ii  libgcc11:6.3.0-18+deb9u1
ii  libgomp1   6.3.0-18+deb9u1
ii  libinsighttoolkit4.10  4.10.1-dfsg1-1.1+b1
ii  libstdc++6 6.3.0-18+deb9u1
ii  zlib1g 1:1.2.8.dfsg-5

elastix recommends no packages.

Versions of packages elastix suggests:
pn  elastix-doc  

-- no debconf information

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Guido Günther]

On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> Package: git-buildpackage
> Version: 0.9.9
> Severity: grave
> Justification: causes non-serious data loss
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> "gbp import-orig --uscan" seems to choke on tarballs repacked by uscan.
> 
> With the attached debian files - changelog, copyright, and watch, in an
> freshly created git project (i.e. just "git init"), doing
> "gbp import-orig --uscan" will succeed but the resulting project wil be
> missing the subdirectories translations and utils.
> 
> Doing same without the copyright file will have all files imported.
> 
> The repacked tarball do contain the subdirectories, so it seems gbp
> chokes on it for some reason.

I rather assume thath the copyright file instructs uscan to filter these
out?
 -- Guido

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Guido Günther]

On Mon, Jun 11, 2018 at 11:04:51AM +0200, Guido Günther wrote:
> On Mon, Jun 11, 2018 at 10:01:44AM +0200, Jonas Smedegaard wrote:
> > Package: git-buildpackage
> > Version: 0.9.9
> > Severity: grave
> > Justification: causes non-serious data loss
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > "gbp import-orig --uscan" seems to choke on tarballs repacked by uscan.
> > 
> > With the attached debian files - changelog, copyright, and watch, in an
> > freshly created git project (i.e. just "git init"), doing
> > "gbp import-orig --uscan" will succeed but the resulting project wil be
> > missing the subdirectories translations and utils.
> > 
> > Doing same without the copyright file will have all files imported.
> > 
> > The repacked tarball do contain the subdirectories, so it seems gbp
> > chokes on it for some reason.
> 
> I rather assume thath the copyright file instructs uscan to filter these
> out?

Oh...and as always: please provide data to reproduce the problem. Your
package is certainly not the first to be imported with --uscan and since
it works for some setups it would be good to have your test case to find
out what's different.

 -- Guido

Bug#901185: OK downgraded bash

[積丹尼 Dan Jacobson]

OK downgraded to bash4, restored /etc/exim4/update-exim4.conf.conf from
backups, and was able to upgrade exim4.

Processed: severity of 901303 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 901303 serious
Bug #901303 [git-buildpackage] git-buildpackage: gbp import-orig --uscan skips 
unrelated files importing repacked tarball
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
901303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901306: pandoc: FTBFS on armhf: ghc: panic

[Emilio Pozuelo Monfort]

Source: pandoc
Version: 2.2.1-1
Severity: serious

pandoc now FTBFS on armhf with a ghc panic:

[112 of 131] Compiling Text.Pandoc.Readers.HTML ( 
src/Text/Pandoc/Readers/HTML.hs, dist-ghc/build/Text/Pandoc/Readers/HTML.p_o )
ghc: panic! (the 'impossible' happened)
  (GHC version 8.2.2 for arm-unknown-linux):
piResultTy
  Addr#
  String
  Call stack:
  CallStack (from HasCallStack):
prettyCurrentCallStack, called at compiler/utils/Outputable.hs:1133:58 
in ghc:Outputable
callStackDoc, called at compiler/utils/Outputable.hs:1137:37 in 
ghc:Outputable
pprPanic, called at compiler/types/Type.hs:949:35 in ghc:Type

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

Full logs at https://buildd.debian.org/status/logs.php?pkg=pandoc=armhf

Emilio

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

[Jonas Smedegaard]

Package: git-buildpackage
Version: 0.9.9
Severity: grave
Justification: causes non-serious data loss

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

"gbp import-orig --uscan" seems to choke on tarballs repacked by uscan.

With the attached debian files - changelog, copyright, and watch, in an
freshly created git project (i.e. just "git init"), doing
"gbp import-orig --uscan" will succeed but the resulting project wil be
missing the subdirectories translations and utils.

Doing same without the copyright file will have all files imported.

The repacked tarball do contain the subdirectories, so it seems gbp
chokes on it for some reason.


 - Jonas


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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.18.3
ii  git1:2.17.1-1
ii  man-db 2.8.3-2
ii  python33.6.5-3
ii  python3-dateutil   2.6.1-1
ii  python3-pkg-resources  39.1.0-1

Versions of packages git-buildpackage recommends:
ii  cowbuilder0.87+b1
ii  pbuilder  0.229.2
ii  pristine-tar  1.44
ii  python3-requests  2.18.4-2

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.8.23-1
ii  unzip6.0-21

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlseLGUACgkQLHwxRsGg
ASEolg//bIurcEnS3ZXHUyixn14DIbveCWJsn2GFLSyJGa0lNRX07lXGJfFF80Yu
8bQ21U+Xg+Mr3VQiz2Ia8YlkZNjsso/BY6PmdGAxjtV5hjLEcLklg+yGL6tUsBo9
N0T7MWC6/r2cWgdysVnwFkCsRUB6BnHIpThOLDOB0dmyLDkjcu1HEFjVd2d8utoM
JKS68nvKzcibSkf1On1zLAU7So6h0CxrNkjX+4lgRiSh89vehMg7oVBFiG8iz0eb
CPulT3R7aHqcMM1XiDlMBstGybMKyejsZGBOShTP7J2q21HleKCeAj4m8PBzM3Uq
lOc/PgSWcxcd/5dvuCsMvTgvcYfMOLp3r55Du04JWVjNEmWnmypyliBnabmehXZU
dFK38GQ88Ids9rCyWSdiG2sUQTwju1U0XInz5LX2RT7Fb+SieILKrwdSIokiii4I
1st3laTxyoVgialMwDJ/1tTNHuZjxRy9plPBdE4l6prLy/XRA365O74PF8BSWhd0
ZNCGOHNHMiywevu0OsJuj9maR+WRUVLPV/k+gfLMRAcHqFnE1CtANjWpBYoWA8U/
YmNVuoZVXZVWyk7qw+Mmqo+UsfZ88gcdkprVKVqoC01hDDDm32q/YWj47WSvZVB+
fNMCWBbSenCbwdUBo8XdC61lrPzYNWfUuyoHrBMA1+qb6tQS874=
=gf2H
-END PGP SIGNATURE-
monero (0.0) UNRELEASED; urgency=medium

  * Initial release. (Closes: #XX)

 -- Jonas Smedegaard   Mon, 11 Jun 2018 09:35:08 +0200
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Monero
Source: https://github.com/monero/monero-core
 Repackaged, excluding non-DFSG files:
  * Non-free licensed RFC document

  * Image file with embedded non-free licensed ICC profile

Files-Excluded:
 contrib/snap/setup/gui/icon.png
 src/crypto/crypto_ops_builder/ietf.txt
# run "uscan --report" to check or "gpb import-orig --uscan" to update
version=4
opts="filenamemangle=s%(?:.*?)?v?(@ANY_VERSION@@ARCHIVE_EXT@)%@PACKAGE@-$1%,dversionmangle=s/~dfsg\d*$//,repacksuffix=~dfsg"
 \
 https://github.com/monero-project/monero/tags \
 (?:.*?/)?v?@ANY_VERSION@@ARCHIVE_EXT@
$ gbp import-orig --uscan --verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'for-each-ref', '--format=%(refname:short)', 'refs/heads/']
gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream']
gbp:debug: ['git', 'status', '--porcelain']
gbp:debug: ['git', 'status']
gbp:info: Launching uscan...
uscan: Newest version of monero on remote site is 0.12.2.0, local version is 0.0
uscan:=> Newer package available from
  https://github.com/monero-project/monero/archive/v0.12.2.0.tar.gz
gbp:info: Using uscan downloaded tarball ../monero_0.12.2.0~dfsg.orig.tar.gz
What is the upstream version? [0.12.2.0~dfsg] 
gbp:debug: ['git', 'tag', '-l', 'upstream/0.12.2.0_dfsg']
gbp:debug: tar ['-C', '../tmpi7jo5e3w', '-a', '-xf', 
'../monero_0.12.2.0~dfsg.orig.tar.gz'] []
gbp:debug: Unpacked '../monero_0.12.2.0~dfsg.orig.tar.gz' to 
'../tmpi7jo5e3w/monero-0.12.2.0'
gbp:info: Importing '../monero_0.12.2.0~dfsg.orig.tar.gz' to branch 
'upstream'...
gbp:info: Source package is monero
gbp:info: Upstream version is 0.12.2.0~dfsg
gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream']
gbp:debug: ['git', 'add', '-f', '.']
gbp:debug: ['git', 'write-tree']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'upstream']
gbp:debug: Will create missing branch 'upstream'...
gbp:debug: ['git', 'commit-tree', '55a13a0bd88d5372053a75702dddfc90a2788b18']
gbp:debug: ['git', 'update-ref', 

Bug#890691: ruby-bio FTBFS with ruby 2.5

[Andreas Tille]

Hi,

I confirm that this bug persists also for the latest upstream version I
injected in Git[1] has the same issue.  I bet some Ruby programmer could
easily fix the cause:

./build/ruby-bio-1.5.1/lib/bio/util/restriction_enzyme/range/sequence_range/calculated_cuts.rb:154:
 warning: constant ::Fixnum is deprecated
/build/ruby-bio-1.5.1/lib/bio/util/restriction_enzyme/range/sequence_range/calculated_cuts.rb:154:
 warning: constant ::Fixnum is deprecated

...
../build/ruby-bio-1.5.1/lib/bio/db/soft.rb:220:
 warning: constant ::Fixnum is deprecated
/build/ruby-bio-1.5.1/lib/bio/db/soft.rb:226: warning: constant ::Fixnum is 
deprecated
.
...
.O
===
Omission: test randomly failing skipped 
[test_randomize_equiprobability(Bio::TestSequenceCommon::TestSequenceCommonRandomizeChi2)]
/build/ruby-bio-1.5.1/test/unit/bio/sequence/test_common.rb:324:in 
`test_randomize_equiprobability'
===
O
===
Omission: test randomly failing skipped 
[test_randomize_with_hash_equiprobability(Bio::TestSequenceCommon::TestSequenceCommonRandomizeChi2)]
/build/ruby-bio-1.5.1/test/unit/bio/sequence/test_common.rb:330:in 
`test_randomize_with_hash_equiprobability'
===
...
E
===
Error: test_na_seqstat(Bio::TestShellPluginSeq): ArgumentError: incomplete 
format specifier; use %% (double %) instead
/build/ruby-bio-1.5.1/lib/bio/shell/plugin/seq.rb:85:in `format'
/build/ruby-bio-1.5.1/lib/bio/shell/plugin/seq.rb:85:in `block in seqstat'
/build/ruby-bio-1.5.1/lib/bio/shell/plugin/seq.rb:84:in `each'
/build/ruby-bio-1.5.1/lib/bio/shell/plugin/seq.rb:84:in `seqstat'
/build/ruby-bio-1.5.1/test/unit/bio/shell/plugin/test_seq.rb:118:in 
`test_na_seqstat'


The error message looks pretty clear and should be no big deal but I simply
do not speak Ruby.

Kind regards

   Andreas.

[1] https://salsa.debian.org/ruby-team/ruby-bio

-- 
http://fam-tille.de

Processed: Re: Bug#901218: libgrpc-dev: libgpr.a, libgpr.so are already shipped by libgpr1-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #901218 [libgrpc-dev] libgrpc-dev: libgpr.a, libgpr.so are already shipped 
by libgpr1-dev
Added tag(s) pending.

-- 
901218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901218: libgrpc-dev: libgpr.a, libgpr.so are already shipped by libgpr1-dev

[GCS]

Control: tags -1 +pending

Hi Andreas,

On Sun, Jun 10, 2018 at 10:51 AM Andreas Beckmann  wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files.
[...]
> Is this a typo in libgrpc to ship libgpr files?
 If it would be a typo to ship libgpr files, the package build would
have been failed for no such library built.
It's a name collision. For GNAT it's (probably) Gnat PRoject (build
tool set and its library) and for gRPC it's Google Portable Runtime
(for C). All I can do is a simple conflict between the mentioned
packages.

Regards,
Laszlo/GCS

Bug#900539: marked as done (Can no longer watch any YouTube movie)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 07:07:09 +
with message-id 
and subject line Bug#900533: fixed in chromium-browser 67.0.3396.79-2
has caused the Debian Bug report #900533,
regarding Can no longer watch any YouTube movie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
900533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 67.0.3396.62-1

Can no longer watch any YouTube movie

[12124:12562:0601/093720.859119:ERROR:object_proxy.cc(617)] Failed to call 
method: org.freedesktop.DBus.Properties.Get: object_path= 
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.UPower was not provided by any .service files
[12124:12562:0601/093720.859690:ERROR:object_proxy.cc(617)] Failed to call 
method: org.freedesktop.UPower.GetDisplayDevice: object_path= 
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.UPower was not provided by any .service files
[12124:12562:0601/093720.859985:ERROR:object_proxy.cc(617)] Failed to call 
method: org.freedesktop.UPower.EnumerateDevices: object_path= 
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.UPower was not provided by any .service files
[96:111:0601/093721.548419:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[96:96:0601/093721.549182:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[96:111:0601/093722.346231:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[96:96:0601/093722.347816:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 67.0.3396.79-2

We believe that the bug you reported is fixed in the latest version of
chromium-browser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jun 2018 00:33:39 +
Source: chromium-browser
Binary: chromium chromium-l10n chromium-shell chromium-driver chromium-common
Architecture: source
Version: 67.0.3396.79-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Description:
 chromium   - web browser
 chromium-common - web browser - common resources used by the chromium packages
 chromium-driver - web browser - WebDriver support
 chromium-l10n - web browser - language packs
 chromium-shell - web browser - minimal shell
Closes: 900533
Changes:
 chromium-browser (67.0.3396.79-2) unstable; urgency=medium
 .
   * Use embedded ffmpeg code copy (closes: #900533).
Checksums-Sha1:
 9d20ad3e7cfa8cb19d7936e986ef50069a9838f1 4188 
chromium-browser_67.0.3396.79-2.dsc
 738bb91f2c3b0868d65680b451c699c6e2f94c04 144756 
chromium-browser_67.0.3396.79-2.debian.tar.xz
 42165457dd287d16039dc05177251610002ca62e 19592 
chromium-browser_67.0.3396.79-2_source.buildinfo
Checksums-Sha256:
 2382da7d236a22bfa84eaca4cc150aed7079c888df21dae9d0049e76a2d77058 4188 
chromium-browser_67.0.3396.79-2.dsc
 5ba06c84cec80bd50a47137a216669225248b15c9d7a9e038dfb3fc444667379 144756 
chromium-browser_67.0.3396.79-2.debian.tar.xz
 ebe5e7e4013be79d801848e319cb518b364db7837cf2c2ed6d0d76389b46d332 19592 
chromium-browser_67.0.3396.79-2_source.buildinfo
Files:
 2246f915f36ac423490048e8a1cd8ff8 4188 web optional 
chromium-browser_67.0.3396.79-2.dsc
 fd5df1e3b54be08b1d0b93851b78d129 144756 web optional 
chromium-browser_67.0.3396.79-2.debian.tar.xz
 9bb8ff2a31b09c51f96250fa3f28f314 19592 web optional 
chromium-browser_67.0.3396.79-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAlseG2MACgkQuNayzQLW
9HMR8R//WN4f6MYghIrXUXycZFxV84S6jEVoSExkP28yXSrAgQrLWVpQh2VwYBhE

Bug#900533: marked as done (chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jun 2018 07:07:09 +
with message-id 
and subject line Bug#900533: fixed in chromium-browser 67.0.3396.79-2
has caused the Debian Bug report #900533,
regarding chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no 
longer work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
900533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 67.0.3396.62-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Can't use video on youtube. Gif's no longer work. And I cannot get media to 
play. This started after upgrading from 66.0.3359.181-1 to 67.0.3396.62-1

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Reverting the package was the only solution I could find. It appears the app 
build may be missing some flags in the build. I found this that had similar 
errors to my situation 
https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ

   * What was the outcome of this action?

chromium 66.0.3359.181-1 was reinstalled, video is working again.

   * What outcome did you expect instead?

chromium 67.0.3396.62-1 video should work after install.

Chromium Log while trying to play files
[129:160:0531/181749.318090:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.320645:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.352209:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.354280:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.551754:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181749.559473:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[129:160:0531/181750.431299:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181750.433293:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
libpng warning: iCCP: known incorrect sRGB profile


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  67.0.3396.62-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libavcodec57 7:3.4.2-2+b1
ii  libavformat577:3.4.2-2+b1
ii  libavutil55  7:3.4.2-2+b1
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcups2 2.2.7-5
ii  libdbus-1-3  1.12.8-2
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-4
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libharfbuzz0b1.7.6-1+b1
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.37.1-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libpng16-16  1.6.34-1
ii  libpulse011.1-5
ii  libre2-4 20180301+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.1.0-4
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  

Processed: tagging 899846, tagging 899809, tagging 899822, tagging 899827, tagging 899831, tagging 899828 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 899846 + sid buster
Bug #899846 [src:literki] literki: Invalid maintainer address 
pkg-fso-ma...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899809 + sid buster
Bug #899809 [src:mod-authz-securepass] mod-authz-securepass: Invalid maintainer 
address pkg-securepass-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899822 + sid buster
Bug #899822 [src:rpmlint] rpmlint: Invalid maintainer address 
pkg-rpm-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899827 + sid buster
Bug #899827 [src:tideways] tideways: Invalid maintainer address 
pkg-php-p...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899831 + sid buster
Bug #899831 [src:deborphan] deborphan: Invalid maintainer address 
deborphan-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899828 + sid buster
Bug #899828 [src:ibus-m17n] ibus-m17n: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899833 + sid buster
Bug #899833 [src:db-defaults] db-defaults: Invalid maintainer address 
pkg-db-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899834 + sid buster
Bug #899834 [src:cipux-task] cipux-task: Invalid maintainer address 
cipux-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899837 + sid buster
Bug #899837 [src:xfce4-datetime-plugin] xfce4-datetime-plugin: Invalid 
maintainer address pkg-xfce-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899840 + sid buster
Bug #899840 [src:module-build-cipux] module-build-cipux: Invalid maintainer 
address cipux-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899841 + sid buster
Bug #899841 [src:sugar-irc-activity] sugar-irc-activity: Invalid maintainer 
address debian-olpc-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899848 + sid buster
Bug #899848 [src:xfce4-dev-tools] xfce4-dev-tools: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899855 + sid buster
Bug #899855 [src:fcitx-googlepinyin] fcitx-googlepinyin: Invalid maintainer 
address pkg-ime-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899865 + sid buster
Bug #899865 [src:libxfce4util] libxfce4util: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899870 + sid buster
Bug #899870 [src:pycangjie] pycangjie: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899874 + sid buster
Bug #899874 [src:xfce4-mpc-plugin] xfce4-mpc-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899877 + sid buster
Bug #899877 [src:php-libsodium] php-libsodium: Invalid maintainer address 
pkg-php-p...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899881 + sid buster
Bug #899881 [src:idm-console-framework] idm-console-framework: Invalid 
maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899885 + sid buster
Bug #899885 [src:pyrfc3339] pyrfc3339: Invalid maintainer address 
letsencrypt-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899896 + sid buster
Bug #899896 [src:euca2ools] euca2ools: Invalid maintainer address 
pkg-eucalyptus-maintain...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899898 + sid buster
Bug #899898 [src:gauche] gauche: Invalid maintainer address 
pkg-gauche-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899900 + sid buster
Bug #899900 [src:python-elements] python-elements: Invalid maintainer address 
debian-olpc-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899903 + sid buster
Bug #899903 [src:fso-audiod] fso-audiod: Invalid maintainer address 
pkg-fso-ma...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899908 + sid buster
Bug #899908 [src:opennebula-context] opennebula-context: Invalid maintainer 
address pkg-opennebula-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899912 + sid buster
Bug #899912 [src:xfce4-appfinder] xfce4-appfinder: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899913 + sid buster
Bug #899913 [src:php-mailparse] php-mailparse: Invalid maintainer address 
pkg-php-ma...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899914 + sid buster
Bug #899914 [src:mp4h] mp4h: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899915 + sid buster
Bug #899915 [src:dctrl-tools] dctrl-tools: Invalid maintainer address 
dctrl-tools-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899918 + sid buster
Bug #899918 [src:fso-specs] fso-specs: Invalid maintainer address 
pkg-fso-ma...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899922 +