Bug#866790: postfix rules yield error and fail
Antoine Beaupré: > PS: seems to me like a good example why profiles-extra should be > deployed straight to /etc :p One step at a time: I'd rather see AppArmor enabled by default with a small, robust policy first. And then we can think of extending this policy :) Cheers, -- intrigeri
Bug#862423: marked as done (pysvn ftbfs with more than one supported python3 version)
Your message dated Mon, 03 Jul 2017 05:06:43 + with message-id and subject line Bug#862423: fixed in pysvn 1.9.4-3 has caused the Debian Bug report #862423, regarding pysvn ftbfs with more than one supported python3 version 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.) -- 862423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pysvn Version: 1.9.4-2 Severity: important Tags: sid buster User: debian-pyt...@lists.debian.org Usertags: python3.6 pysvn ftbfs with more than one supported python3 version, when PYVERS3 expands to more than one version. So either build for only the default version (change the b-d's), or fix the build system to build for all supported versions. --- End Message --- --- Begin Message --- Source: pysvn Source-Version: 1.9.4-3 We believe that the bug you reported is fixed in the latest version of pysvn, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 862...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated pysvn 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: Sat, 01 Jul 2017 13:14:54 -0400 Source: pysvn Binary: python-svn python3-svn Architecture: source amd64 Version: 1.9.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Scott Kitterman Description: python-svn - A(nother) Python interface to Subversion python3-svn - A(nother) Python 3 interface to Subversion Closes: 862423 Changes: pysvn (1.9.4-3) unstable; urgency=medium . * Team upload. * Update to build python3-svn for all supported python3 versions (Closes: #862423) Checksums-Sha1: 474fa36bdfcaaa208958b9f8b5cd316ab9993380 2268 pysvn_1.9.4-3.dsc b83a1eca03a686c864e67aca9a6b6dc3fe0d7d40 8736 pysvn_1.9.4-3.debian.tar.xz d046a921ad3b1a3b4c689aa9694ce4cb8625c628 8811 pysvn_1.9.4-3_amd64.buildinfo c02aaa3043ff9f30a39dd23202f3563d3f8858c7 109028 python-svn-dbgsym_1.9.4-3_amd64.deb 4e385f9c73b591b391637a44ddc5d24af23f280d 435028 python-svn_1.9.4-3_amd64.deb 5b1b4549757faf80f0bf701a3ebeb35d391652db 109906 python3-svn-dbgsym_1.9.4-3_amd64.deb 26676692eb55221a2737a54f8ecbf22236a477e9 415132 python3-svn_1.9.4-3_amd64.deb Checksums-Sha256: 21d5381a8bfdeac78ac0ddb9c46f0646dbe373b73e215aa8d33c1923a40181e9 2268 pysvn_1.9.4-3.dsc 42438fa8c6fd2b741a77dad4799a1415d0332b6d23c000cb8c441cb37b8be8c2 8736 pysvn_1.9.4-3.debian.tar.xz 81a3d2efebf31e474ec00a0317429e875bef8a60d5081ac0dc84be0719e7607e 8811 pysvn_1.9.4-3_amd64.buildinfo fa22789c4683dee6563cf6e90a9d1e7a0351749a650e7717d0255a81f6225878 109028 python-svn-dbgsym_1.9.4-3_amd64.deb 1db4626a29e554cb0ca11030cb35024ef63cdbdc91b09300d2f13c69ece8c439 435028 python-svn_1.9.4-3_amd64.deb 509db3c8a15ad58308e5d864d909af64909ec0314e58c4d196e07f70ea22c5ec 109906 python3-svn-dbgsym_1.9.4-3_amd64.deb 02f435d3e966972b8b5f4886983b0a155c0c1d42f9ea0087ab171a745af39f7c 415132 python3-svn_1.9.4-3_amd64.deb Files: a7709eab80ca33027d22eb52db144980 2268 python optional pysvn_1.9.4-3.dsc ecda03f4ae9368add35459527210ef4f 8736 python optional pysvn_1.9.4-3.debian.tar.xz 848d74fa73713b75aafda10f1886eb65 8811 python optional pysvn_1.9.4-3_amd64.buildinfo 0b191b70b90280ef8e7f84d979d653b1 109028 debug extra python-svn-dbgsym_1.9.4-3_amd64.deb 71b485e0fe9c02d35bf98068366497db 435028 python optional python-svn_1.9.4-3_amd64.deb 018890b4abac9359e353400da79c195b 109906 debug extra python3-svn-dbgsym_1.9.4-3_amd64.deb 488ed066d98f363117b1454bcbbe02aa 415132 python optional python3-svn_1.9.4-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJZWcw3AAoJEHjX3vua1Zrxb5UQAIhoR5mwx8xLPIsSAf33kPAd KtTAL2MpbleFHgiEVZYw6JMrFZTH5Ovzg22UND/Vv7tEzDmKPxTfG7rgxlhhS/ng jbGIPIY0Xn2mKXNkx2TqF1qmmlICcUdtre5XTj0yfJu8ADk93FMvO0Ttp6bxRA75 Snh9+tpxPag9pgr3vGXPBnqyJ5pkBPTR9NfHWPWJKFLwQYi9MGohRNucWWxQc+/V LKQZ+Bfy54LOlL7FJqN6KWjn6ikojvj+BZOnanRy3Sw+wbq0nbSay/+tcfZUaIz6 MA7i9h/RwpII8QRTEEFn3QwRUW5LlF3X2TbYdA7ltceNvaZ+Sjib2O4J+BlXc0Ub Ymh1v7MeQ1Ev03sx5UUvpef5JGJdD41ulMZinw6Q8N4dyrKeQN0aJU7DywB+w9BV 1qNbHPKRhOV1kza
Bug#862423: marked as pending
tag 862423 pending thanks Hello, Bug #862423 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/pysvn.git/commit/?id=ba541dc --- commit ba541dc1cf1f2245fe9a0a11ec96a36d144c682f Author: Scott Kitterman Date: Mon Jul 3 00:47:40 2017 -0400 * Update to build python3-svn for all supported python3 versions (Closes: #862423) diff --git a/debian/changelog b/debian/changelog index 9ffc603..056d798 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +pysvn (1.9.4-3) unstable; urgency=medium + + * Team upload. + * Update to build python3-svn for all supported python3 versions +(Closes: #862423) + + -- Scott Kitterman Sat, 01 Jul 2017 13:14:54 -0400 + pysvn (1.9.4-2) unstable; urgency=medium * Adds patch 0001-fix-multiple-arch-support.patch to support
Processed: Bug#862423 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 862423 pending Bug #862423 [src:pysvn] pysvn ftbfs with more than one supported python3 version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 862423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866378: 3dchess: 100 % CPU consumption
在 2017年7月2日星期日 CST 下午4:32:22，Markus Koschany 写道： > Am 02.07.2017 um 16:26 schrieb Boyuan Yang: > > [cc me please, thanks] > > > > Hello all, > > > > Now that bug #866378 is fixed in unstable (and soon in testing), is it > > possible for anyone to make a stable update and have this RC bug fixed in > > Debian 9? I would like to see a 3dchess/0.8.1-19+deb9u1 in Debian > > Stretch. > > > > The patch seems simple and likely to be accepted by Stable Release > > Managers. Any idea? > > Hi, > > I will prepare a point update for Jessie and Stretch. Great. > Just out of curiosity, how did you notice this bug? I was hanging around on https://bugs.debian.org/release-critical/ . Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#866965: dosemu: DPMI unhandled exception instability back again
Package: dosemu Version: 1.4.0.7+2013 Severity: grave Justification: renders package unusable Identical symptoms were reported in https://bugs.debian.org/797378, but they're back again. That report stated that the problem was in the Linux kernel and was fixed in Linux 4.2-rc7. I'm running kernel 4.9.x, as installed from the Stretch repos. What's going on this time? -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.15-x86_64 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: sysvinit (via /sbin/init) Versions of packages dosemu depends on: pn libasound2 ii libc62.24-11+deb9u1 ii libgpm2 1.20.4-6.2+b1 pn libsdl1.2debian ii libslang22.3.1-5 pn libsndfile1 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 pn libxxf86vm1 pn xfonts-utils dosemu recommends no packages. dosemu suggests no packages.
Bug#866963: shellinabox: Not working. Had it installed on my NAS with Jessie and it was fully working. I did a "dist-upgrade" and it is no longer working. Suspecting that something with my old configu
Package: shellinabox Version: 2.20 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? dist-upgraded NAS * What exactly did you do (or not do) that was effective (or ineffective)? installed it on a VM * What was the outcome of this action? still not working * What outcome did you expect instead? was hoping it would be working *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.9.0-3-marvell Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages shellinabox depends on: ii adduser3.115 ii libc6 2.24-11+deb9u1 ii libpam0g 1.1.8-3.6 ii libssl1.1 1.1.0f-3 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-5 shellinabox recommends no packages. Versions of packages shellinabox suggests: ii openssl 1.1.0f-3 -- no debconf information
Bug#866769: keepassx fails to clear KDE clipboard history, leaving passwords visible
Control: tag -1 +help +upstream Control: severity -1 important Thank you very much for your bug report, Henrik. On 07/01/2017 11:22 AM, Henrik Størner wrote: > > keepassx 2.0.3-1 (in Debian "stretch") fails to clear the clipboard history > after a password has been copied to the clipboard. > > The keepassx security settings has "Clear clipboard after 10 seconds" enabled. > > To reproduce, > - select an entry with a stored password in the keepassx database > - press ctrl-C to copy the password to the clipboard > - after 10 seconds (default setting), the password should disappear from the > clipboard history > - click on the clipboard icon in the panel, the password is visible > > This is using the KDE Desktop installation, and hence the KDE clipboard. > > The KDE clipboard has a setting to prevent the clipboard from being emptied, > but this setting does not change the behaviour. I noticed that keepassx does ship with code that does look like it should do exactly that: http://sources.debian.net/src/keepassx/2.0.3-1/src/gui/Clipboard.cpp/ Unfortunately, I'm not familiar with that particular API so I can't comment on whether the API is being used correctly or not. However, I'm confident that it did work for the author, who may or may not have used KDE. I'd appreciate any help from KDE experts here. While I do agree that this can be viewed as be a security related issue, I disagree that this issue is "release critical". I'm therefore downgrading the severity of this bug. Best, Reinhard
Processed: Re: Bug#866769: keepassx fails to clear KDE clipboard history, leaving passwords visible
Processing control commands: > tag -1 +help +upstream Bug #866769 [keepassx] keepassx fails to clear KDE clipboard history, leaving passwords visible Added tag(s) help. Bug #866769 [keepassx] keepassx fails to clear KDE clipboard history, leaving passwords visible Added tag(s) upstream. > severity -1 important Bug #866769 [keepassx] keepassx fails to clear KDE clipboard history, leaving passwords visible Severity set to 'important' from 'grave' -- 866769: bugs.debian.org/cgi-bin/bugreport.cgi?bug=866769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): notfixed 863162 in 4.20150325+b1, notfixed 826959 in 4.9.18-1+rm, notfixed 734675 in 3.3.6p2 ...
Processing commands for cont...@bugs.debian.org:
> # fixing up bug metadata to allow archival
> notfixed 863162 4.20150325+b1
Bug #863162 {Done: Bernd Zeimetz } [ksmtuned] ksmtuned: Should
this be a native package?
No longer marked as fixed in versions 4.20150325+b1.
> notfixed 826959 4.9.18-1+rm
Bug #826959 {Done: Debian FTP Masters }
[src:linux-signed] linux-signed is not yet suitable for testing
The source 'linux-signed' and version '4.9.18-1+rm' do not appear to match any
binary packages
No longer marked as fixed in versions 4.9.18-1+rm.
> notfixed 734675 3.3.6p2
Bug #734675 {Done: Steffen Möller } [src:fftw3] fftw3:
Fix configury for neon support on arm64 (armv8)
The source 'fftw3' and version '3.3.6p2' do not appear to match any binary
packages
No longer marked as fixed in versions 3.3.6p2.
> fixed 734675 3.3.6p2-1
Bug #734675 {Done: Steffen Möller } [src:fftw3] fftw3:
Fix configury for neon support on arm64 (armv8)
Marked as fixed in versions fftw3/3.3.6p2-1.
> fixed 861731 3.17.6+repack0-1
Bug #861731 {Done: Didier Raboud } [hplip] hplip -
UnicodeDecodeError in /usr/share/hplip/base/sixext.py, impossible to print
certain files
Marked as fixed in versions hplip/3.17.6+repack0-1.
> fixed 803053 233-1
Bug #803053 {Done: Michael Biebl } [systemd-container]
/bin/machinectl: Failed to start a raw image using machinectl but was able to
start using systemd-nspawn
There is no source info for the package 'systemd-container' at version '233-1'
with architecture ''
Unable to make a source version for version '233-1'
Marked as fixed in versions 233-1.
> fixed 861269 0.10.2-1
Bug #861269 {Done: Harlan Lieberman-Berg } [certbot]
certbot: Fails to install on jessie-backports
Marked as fixed in versions python-certbot/0.10.2-1.
> notfixed 473008 1.12.0~rc3-1
Bug #473008 {Done: Paul Gevers } [liferea] liferea: key for
moving through articles not configurable
Bug #560305 {Done: Paul Gevers } [liferea] liferea: "Skim
through articles with:" "Space" no longer works
There is no source info for the package 'liferea' at version '1.12.0~rc3-1'
with architecture ''
Unable to make a source version for version '1.12.0~rc3-1'
No longer marked as fixed in versions 1.12.0~rc3-1.
No longer marked as fixed in versions 1.12.0~rc3-1.
> fixed 473008 1.12~rc3-1
Bug #473008 {Done: Paul Gevers } [liferea] liferea: key for
moving through articles not configurable
Bug #560305 {Done: Paul Gevers } [liferea] liferea: "Skim
through articles with:" "Space" no longer works
Marked as fixed in versions liferea/1.12~rc3-1.
Marked as fixed in versions liferea/1.12~rc3-1.
> notfixed 860559 3.76-1
Bug #860559 {Done: "Dr. Tobias Quathamer" } [manpages-dev]
timex.offset unit ambiguity
There is no source info for the package 'manpages-dev' at version '3.76-1' with
architecture ''
Unable to make a source version for version '3.76-1'
No longer marked as fixed in versions 3.76-1.
> fixed 860559 3.82-1
Bug #860559 {Done: "Dr. Tobias Quathamer" } [manpages-dev]
timex.offset unit ambiguity
There is no source info for the package 'manpages-dev' at version '3.82-1' with
architecture ''
Unable to make a source version for version '3.82-1'
Marked as fixed in versions 3.82-1.
> notfixed 854130 1.6.1
Bug #854130 {Done: "A. Jesse Jiryu Davis" } [src:libbson]
libbson FTBFS on mips/mipsel: test-results.json aborted
The source 'libbson' and version '1.6.1' do not appear to match any binary
packages
No longer marked as fixed in versions libbson/1.6.1.
> fixed 854130 1.6.1-1
Bug #854130 {Done: "A. Jesse Jiryu Davis" } [src:libbson]
libbson FTBFS on mips/mipsel: test-results.json aborted
Marked as fixed in versions libbson/1.6.1-1.
> tags 859915 + stretch
Bug #859915 {Done: Alastair McKinstry } [libmagplus3v5]
libmagplus3v5: please add Breaks: libmagplus3
Added tag(s) stretch.
> notfound 837641 9.20160814
Bug #837641 {Done: Niels Thykier } [debhelper] dh_auto_test:
dump testsuite logs upon failure
No longer marked as found in versions debhelper/9.20160814.
> notfixed 773108 1.8.2-1
Bug #773108 {Done: "Barak A. Pearlmutter" } [stopmotion]
stopmotion: Segmentation fault on startup
There is no source info for the package 'stopmotion' at version '1.8.2-1' with
architecture ''
Unable to make a source version for version '1.8.2-1'
No longer marked as fixed in versions stopmotion/1.8.2-1.
> fixed 773108 0.8.2-1
Bug #773108 {Done: "Barak A. Pearlmutter" } [stopmotion]
stopmotion: Segmentation fault on startup
Marked as fixed in versions stopmotion/0.8.2-1.
> notfixed 769983 2.7+dfsg-1
Bug #769983 {Done: Michael Tokarev } [qemu-user-static]
qemu-user multi-threaded issues
There is no source info for the package 'qemu-user-static' at version
'2.7+dfsg-1' with architecture ''
Unable to make a source version for version '2.7+dfsg-1'
No longer marked as fixed in versions 2.7+dfsg-1.
> fixed 769983 1:2.7+dfsg-1
Bug #769983 {Done: Michael Tokarev } [qemu-user-static]
qemu-user multi-threaded issues
Marked as fixed in versions qemu/1:2.7+dfsg-1.
> fixed
Processed: Re: Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII
Processing control commands:
> reassign -1 javahelper 0.60
Bug #866845 {Done: Emmanuel Bourg } [src:libidw-java]
libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for
encoding ASCII
Bug reassigned from package 'src:libidw-java' to 'javahelper'.
No longer marked as found in versions libidw-java/1.6.1-1.
No longer marked as fixed in versions javatools/0.61.
Bug #866845 {Done: Emmanuel Bourg } [javahelper] libidw-java
FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII
Marked as found in versions javatools/0.60.
> affects -1 libidw-java
Bug #866845 {Done: Emmanuel Bourg } [javahelper] libidw-java
FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII
Added indication that 866845 affects libidw-java
--
866845: bugs.debian.org/cgi-bin/bugreport.cgi?bug=866845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII
Control: reassign -1 javahelper 0.60 Control: affects -1 libidw-java Thank you Adrian. This issue was introduced by javahelper 0.60 that now uses the source/target level 1.7 by default. At this level the compiler becomes picky about the character encoding. javahelper must be modified to also specify a default encoding. ISO-8859-1 should be a good choice because any one byte character is considered valid. Emmanuel Bourg
Bug#770369: marked as done (Eterm: does not run shell)
Your message dated Sun, 02 Jul 2017 23:32:33 + with message-id and subject line Bug#770369: fixed in eterm 0.9.6-1+deb8u1 has caused the Debian Bug report #770369, regarding Eterm: does not run shell 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.) -- 770369: bugs.debian.org/cgi-bin/bugreport.cgi?bug=770369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: Eterm Version: 0.9.6-1 Severity: normal Hello, I did # apt-get install eterm $ Eterm A window opens with cursor but no shell starts. I can type in the window and characters appear as typed. There is no other response. Presumably if some poor user installed Eterm and their x-terminal-emulator got switched to Eterm it would seriously impair usability of their system. In the terminal where I start Eterm I get Eterm: Warning: Unable to resolve "bottom_right" as a color name. Falling back on "#00". Eterm: Warning: Unable to resolve "bottom_right" as a color name. Falling back on "#00". -- System Information: Distributor ID: Ubuntu Description:Ubuntu GNU/Linux testing (jessie) Release:testing Codename: jessie Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages Eterm depends on: ii libast20.7-7 ii libc6 2.19-13 ii libfreetype6 2.5.2-2 ii libice62:1.0.9-1 ii libimlib2 1.4.6-2+b3 ii libsm6 2:1.2.2-1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii multiarch-support 2.19-13 ii zlib1g 1:1.2.8.dfsg-2 Eterm recommends no packages. Eterm suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: eterm Source-Version: 0.9.6-1+deb8u1 We believe that the bug you reported is fixed in the latest version of eterm, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated eterm 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: Fri, 12 May 2017 19:52:47 +0300 Source: eterm Binary: eterm Architecture: source amd64 Version: 0.9.6-1+deb8u1 Distribution: jessie Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Description: eterm - Enlightened Terminal Emulator Closes: 770369 Changes: eterm (0.9.6-1+deb8u1) jessie; urgency=medium . * QA upload. * Apply patch from Arnaud Ceyrolle to fix problems when starting or stopping the shell caused by an integer overflow. (Closes: #770369) Checksums-Sha1: f52f45cd6e93a95f2933eb911173996e62fdde33 1861 eterm_0.9.6-1+deb8u1.dsc 2c6c56660e8ed1acd215b7e17e89e82e9e29a79c 11802 eterm_0.9.6-1+deb8u1.diff.gz 5f0c6c785658015860a637d24192084750e3cf1b 416696 eterm_0.9.6-1+deb8u1_amd64.deb Checksums-Sha256: c5cbef0ce97f457affe6489b5ad0e0ad05413471d4bd589289105dcad4d613cb 1861 eterm_0.9.6-1+deb8u1.dsc 2c3bd554086c512d4637b0ca497689da6371a33e083d9ce152a5019f8142a2c7 11802 eterm_0.9.6-1+deb8u1.diff.gz c5928291996e7cc5d276d286cdac9de9682c5d0f1afc124010dc8624934d2eb5 416696 eterm_0.9.6-1+deb8u1_amd64.deb Files: 814b8181c096cf2a3236b286eb9a4b58 1861 x11 optional eterm_0.9.6-1+deb8u1.dsc 469917907d6b8942137aadbfe99183a9 11802 x11 optional eterm_0.9.6-1+deb8u1.diff.gz d81edded36aa3024553573cb05534ea4 416696 x11 optional eterm_0.9.6-1+deb8u1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAllWcZUACgkQiNJCh6LY mLH1KA//SHVdyPuXR3ryBrFGRGneAiawZYopE3hsfW/ocLNVJ9WJcCV27jBwEQqT dETI/oUN7l2NkGWuHKG/KFBFnLe1QVYw4DFnz0NkidMdCI6E793h2hz4EJL6XXAT v/fnxxhmbAnMLSiHvYPrecfqFjAPd5scra3iSnN+3ZxosRPlT33mD/v3gpz17eRJ 2Bldh4UAW9U9djvUBtrSYkDDIcEtfVwI8jI8i7i43xV2qSJ3g5Gz87RXnyG1lePQ EHyp35eOGyAjMCEHgPQQg17bcm5Yn+GwIaXcDLhWX8gHF3IXUuhfDuCmRJjSHjC2 VLwhIrgOF4ThbNGwS8SWN1QCpNtLcOH0k9+gmpd1rvUO+Wo5ySyY+PGkZD6T58OJ caiICi3NERnqz4CCmi5qH4tT8Kg5V3mXE9+XVG/9MWLsvNTKKI78JkcgrbMfp+6O mdqO6lm9+JUudiIzwSTMqFAwTSfIFO1rcagkyfjMatHtlEaL++hZnVPRgL5fLs9M 6VRs8
Bug#866629: It seems to an issue with regular bootable non-free iso as well.
On Mon, Jul 03, 2017 at 04:19:40AM +0530, shirish शिरीष wrote: >Dear all, > >We were doing a release party for Stretch in Pune when we were hit >with this bug. Notice the UI, it seems even regular (not just live) is >also hit with the same bug. The picture was captured by Gaurav. As we >were in midst of things, I forgot to see what messages were coming on >the console. The one which we were using is amd64 iso-non-free (for >drivers) Hi Shirish, I've just tested locally using http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.0.0+nonfree/amd64/iso-cd/firmware-9.0.0-amd64-netinst.iso and I see no such issue. Are you *sure* you weren't using a live image? -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Bug#866506: marked as done (qtbase-opensource-src: either drop GLES2 defintions from public headers or pass the right flags)
Your message dated Sun, 02 Jul 2017 23:19:37 + with message-id and subject line Bug#866506: fixed in qtbase-opensource-src 5.7.1+dfsg-4 has caused the Debian Bug report #866506, regarding qtbase-opensource-src: either drop GLES2 defintions from public headers or pass the right flags 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.) -- 866506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nageru Version: 1.6.0-2 Severity: serious https://buildd.debian.org/status/package.php?p=nageru&suite=sid ... g++ -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++11 -fPIC -pthread -I/usr/include/arm-linux-gnueabihf/qt5/QtOpenGLExtensions -I/usr/include/arm-linux-gnueabihf/qt5 -I/usr/include/arm-linux-gnueabihf/qt5/QtOpenGL -I/usr/include/arm-linux-gnueabihf/qt5 -I/usr/include/arm-linux-gnueabihf/qt5/QtPrintSupport -I/usr/include/arm-linux-gnueabihf/qt5 -I/usr/include/arm-linux-gnueabihf/qt5/QtWidgets -I/usr/include/arm-linux-gnueabihf/qt5 -I/usr/include/arm-linux-gnueabihf/qt5/QtGui -I/usr/include/arm-linux-gnueabihf/qt5 -I/usr/include/arm-linux-gnueabihf/qt5/QtCore -I/usr/include/arm-linux-gnueabihf/qt5 -I/usr/include/movit -I/usr/include/lua5.2 -I/usr/include/p11-kit-1 -I/usr/include/libusb-1.0 -I/usr/include/eigen3 -pthread -DMOVIT_SHADER_DIR=\"/usr/share/movit\" -Idecklink/ -o analyzer.o -c analyzer.cpp In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglextrafunctions.h:47:0, from /usr/include/arm-linux-gnueabihf/qt5/QtGui/QtGui:55, from /usr/include/arm-linux-gnueabihf/qt5/QtPrintSupport/QtPrintSupportDepends:4, from /usr/include/arm-linux-gnueabihf/qt5/QtPrintSupport/QtPrintSupport:3, from /usr/include/qcustomplot.h:54, from ui_analyzer.h:27, from analyzer.cpp:15: /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h: In member function 'void QOpenGLFunctions::glBindTexture(GLenum, GLuint)': /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h:595:5: error: '::glBindTexture' has not been declared ::glBindTexture(target, texture); ^~ /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h: In member function 'void QOpenGLFunctions::glBlendFunc(GLenum, GLenum)': /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h:606:5: error: '::glBlendFunc' has not been declared ::glBlendFunc(sfactor, dfactor); ^~ /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h: In member function 'void QOpenGLFunctions::glClear(GLbitfield)': /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h:617:5: error: '::glClear' has not been declared ::glClear(mask); ^~ /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h: In member function 'void QOpenGLFunctions::glClearColor(GLclampf, GLclampf, GLclampf, GLclampf)': /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglfunctions.h:628:5: error: '::glClearColor' has not been declared ::glClearColor(red, green, blue, alpha); ^~ ... Am armel and armhf, Qt is compiled with OpenGL ES instead of full OpenGL. --- End Message --- --- Begin Message --- Source: qtbase-opensource-src Source-Version: 5.7.1+dfsg-4 We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated qtbase-opensource-src 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, 02 Jul 2017 20:07:11 -0300 Source: qtbase-opensource-src Binary: libqt5core5a libqt5gui5 qt5-gtk-platformtheme libqt5network5 libqt5opengl5 libqt5sql5 libqt5sql5-mysql libqt5sql5-odbc libqt5sql5-psql libqt5sql5-sqlite libqt5sql5-tds libqt5sql5-ibase libqt5xml5 libqt5dbus5 libqt5test5 libqt5concurrent5 libqt5widgets5 libqt5printsupport5 qtbase5-dev qtbase5-p
Bug#866200: marked as done (phpunit: CVE-2017-9841)
Your message dated Sun, 02 Jul 2017 23:17:09 + with message-id and subject line Bug#866200: fixed in phpunit 5.4.6-2~deb9u1 has caused the Debian Bug report #866200, regarding phpunit: CVE-2017-9841 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.) -- 866200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpunit Version: 5.4.6-1 Severity: grave Tags: patch upstream security fixed-upstream Hi, the following vulnerability was published for phpunit. CVE-2017-9841[0]: | Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 | allows remote attackers to execute arbitrary PHP code via HTTP POST | data beginning with a "
Bug#866845: marked as done (libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII)
Your message dated Sun, 02 Jul 2017 23:03:55 +
with message-id
and subject line Bug#866845: fixed in javatools 0.61
has caused the Debian Bug report #866845,
regarding libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable
character for encoding ASCII
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.)
--
866845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libidw-java
Version: 1.6.1-1
Severity: serious
Tags: buster sid
Some recent change in unstable makes libidw-java FTBFS:
https://tests.reproducible-builds.org/debian/history/libidw-java.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libidw-java.html
...
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
jh_build
find src -name *.java -and -type f -print0 | xargs -s 512000 -0
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.idw -d
debian/_jh_build.idw -source 1.7 -target 1.7
warning: [options] bootstrap class path not set in conjunction with -source 1.7
src/net/infonode/properties/propertymap/PropertyMapImpl.java:383: error:
unmappable character for encoding ASCII
throw new RuntimeException("Property group '" +
propertyObjectImpl.propertyGroup + "?' can't be assigned to group '" +
propertyGroup + "'!");
^
1 error
1 warning
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 123
--- End Message ---
--- Begin Message ---
Source: javatools
Source-Version: 0.61
We believe that the bug you reported is fixed in the latest version of
javatools, 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 866...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated javatools 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, 03 Jul 2017 00:18:51 +0200
Source: javatools
Binary: jarwrapper javahelper java-propose-classpath
Architecture: source
Version: 0.61
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Description:
jarwrapper - Run executable Java .jar files
java-propose-classpath - Helper script to suggest a classpath for jar files
javahelper - Helper scripts for packaging Java programs
Closes: 866845
Changes:
javatools (0.61) unstable; urgency=medium
.
* Team upload.
* jh_build: Use ISO8859-1 as the default encoding to avoid unmappable
character errors (Closes: #866845)
Checksums-Sha1:
519724e71335f14ab2a7cf2349db536ae8e8791c 1949 javatools_0.61.dsc
e4518042ebc6659959b7da0adc2504ff0f272d9d 50556 javatools_0.61.tar.xz
2cb136e5350b5560ea64d12dc1112023b2f44f45 11429 javatools_0.61_source.buildinfo
Checksums-Sha256:
f1cf09064b06ecb402227a074f0b449310c72eca9bf961aae7928c061f5f6c9b 1949
javatools_0.61.dsc
a808ce74c7509cf5bd088a73c6d68c1e66b3b5e72c36ec9a91f2fefb644bd0d2 50556
javatools_0.61.tar.xz
4fd0b70a916d220a0f356d8cf62a1053cb14c37b4c32f792528b74e3b43d9c3d 11429
javatools_0.61_source.buildinfo
Files:
abf43c3838eeaad9aaab224383ebe71f 1949 java optional javatools_0.61.dsc
19169e0ebc3a811dce32801bfff17df5 50556 java optional javatools_0.61.tar.xz
73e1fbc1d2f0b1c6ba6f6dea3056db50 11429 java optional
javatools_0.61_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCAAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAllZdtgSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsE9YQAIivljRneayXaq7j4qZ+r2V4/JQqH/RW
iZj6ZyPf/c+diI0gIaSR+MSilUyNoIzZ0wmXc8eiKsIybXALMfkAYqCGLYKJhDKQ
59zH+Jr4ujurMkX+PdmL++dxhV12AWvgRjc916wNdaAfFaIxmReX8SstoONUe91O
fBk++BHCOAbeEnDBMGerd10ahrfCUdpNNilSO4sskJnSM2O7/Ndfa8Rn0rv5iA8M
hCi7CPAAWVfNIsgjBTm6BxlGvs8AQ6b2d5LExJ9Z2HUsqcOgXMai9YQFtTEXoC4x
jInX7WXsf+UW2wnnHvnso1nntq9fQsRW2KD8J10msFUvdCm/+hDWQRvNnGsdne8J
hcX0IakZPJ+FMpAh79wJV7cl2UIY6wPlpzez4Yalduvab/+VR0MfCTjUnOVsZoiA
EWkEWTGD1EjZzZzsqJgfkHN+JBsaksP4xD72SMrgFfSKM9aLAHFqTpViJpvbxt6l
cfDgyi5jIdqolDewZ7GOFbR7zzj/fyoCWKrB/1/ogi97lagVM52wh9BWaHb1Y19C
9h+ZCekIYD8v+jxVEBzy684ZR/Uv5BeCMxhsXQplEIolzt5ZlmV2XJYj2ryQXa/M
8ETVslnCdQ8qD6fXjfEGmY1S
Bug#866629: debian-installer: Installer showes Debootstrap Error debian stretch live installation
On Fri, Jun 30, 2017 at 08:43:28PM +0530, user01 wrote: >Package: debian-installer >Version: 20170615 >Severity: important > >Dear Maintainer, > >>* What led up to the situation? > >Debian stretch installation without connection to internet gives debootstrap >error, >"failed to determine the codename for the release." and fails. You don't say explicitly, but from the symptoms you're describing you're trying to use the live installer? -- Steve McIntyre, Cambridge, UK.st...@einval.com We don't need no education. We don't need no thought control.
Bug#866629: It seems to an issue with regular bootable non-free iso as well.
Dear all, We were doing a release party for Stretch in Pune when we were hit with this bug. Notice the UI, it seems even regular (not just live) is also hit with the same bug. The picture was captured by Gaurav. As we were in midst of things, I forgot to see what messages were coming on the console. The one which we were using is amd64 iso-non-free (for drivers) Hope this is fixed ASAP. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot
Package: xen-system-amd64 Version: 4.8.1-1+deb9u1 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Initially an attempt was made to upgrade an existing Jessie Xen 4.4 system to Stretch Xen 4.8. When that failed I decided to start with a fresh Stretch install. * What exactly did you do (or not do) that was effective (or ineffective)? - First, I just replaced 'jessie' with 'stretch' in sources.list and ran 'apt-get dist-upgrade'. The resulting system crashed on boot. - Second, I installed a new stretch system, updated my puppet manifest to support Xen 4.8, ran puppet, and rebooted. The resulting system crashed on boot exactly the same as my first attempt. - Third, I installed a new stretch system and installed only the xen-system-amd64 package. The resulting system crashed on boot exactly the same as my first attempt. * What was the outcome of this action? Here is the output captured from a serial console connection. [0.00] Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gc) [0.00] Command line: placeholder root=UUID=54dcd810-baaf-4dfd-9442-4a728 [0.00] x86/fpu: Legacy x87 FPU detected. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] Released 0 page(s) [0.00] e820: BIOS-provided physical RAM map: [0.00] Xen: [mem 0x-0x0009dfff] usable [0.00] Xen: [mem 0x000a-0x000f] reserved [0.00] Xen: [mem 0x0010-0xcf378fff] usable [0.00] Xen: [mem 0xcf379000-0xcf38efff] reserved [0.00] Xen: [mem 0xcf38f000-0xcf3cdfff] ACPI data [0.00] Xen: [mem 0xcf3ce000-0xcfff] reserved [0.00] Xen: [mem 0xe000-0xefff] reserved [0.00] Xen: [mem 0xfe00-0x] reserved [0.00] Xen: [mem 0x0001-0x00062fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.6 present. [0.00] Hypervisor detected: Xen [0.00] e820: last_pfn = 0x63 max_arch_pfn = 0x4 [0.00] MTRR: Disabled [0.00] x86/PAT: MTRRs disabled, skipping PAT initialization too. [0.00] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC [0.00] e820: last_pfn = 0xcf379 max_arch_pfn = 0x4 [0.00] RAMDISK: [mem 0x0200-0x0325] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F1150 24 (v02 DELL ) [0.00] ACPI: XSDT 0x000F1254 9C (v01 DELL PE_SC3 00) [0.00] ACPI: FACP 0xCF3B3F9C F4 (v03 DELL PE_SC3 00) [0.00] ACPI: DSDT 0xCF38F000 003DD0 (v01 DELL PE_SC3 00) [0.00] ACPI: FACS 0xCF3B6000 40 [0.00] ACPI: FACS 0xCF3B6000 40 [0.00] ACPI: APIC 0xCF3B3478 00015E (v01 DELL PE_SC3 00) [0.00] ACPI: SPCR 0xCF3B35D8 50 (v01 DELL PE_SC3 00) [0.00] ACPI: HPET 0xCF3B362C 38 (v01 DELL PE_SC3 00) [0.00] ACPI: RMAD 0xCF3B3668 000198 (v01 DELL PE_SC3 00) [0.00] ACPI: MCFG 0xCF3B38C4 3C (v01 DELL PE_SC3 00) [0.00] ACPI: WD__ 0xCF3B3904 000134 (v01 DELL PE_SC3 00) [0.00] ACPI: SLIC 0xCF3B3A3C 000176 (v01 DELL PE_SC3 00) [0.00] ACPI: ERST 0xCF392F70 000270 (v01 DELL PE_SC3 00) [0.00] ACPI: HEST 0xCF3931E0 0003A8 (v01 DELL PE_SC3 00) [0.00] ACPI: BERT 0xCF392DD0 30 (v01 DELL PE_SC3 00) [0.00] ACPI: EINJ 0xCF392E00 000170 (v01 DELL PE_SC3 00) [0.00] ACPI: SRAT 0xCF3B3BC0 000370 (v01 DELL PE_SC3 00) [0.00] ACPI: TCPA 0xCF3B3F34 64 (v02 DELL PE_SC3 00) [0.00] ACPI: SSDT 0xCF3B7000 0043F4 (v01 INTEL PPM RCM 80) [0.00] Setting APIC routing to Xen PV. [0.00] NUMA turned off [0.00] Faking a node at [mem 0x-0x00062fff] [0.00] NODE_DATA(0) allocated [mem 0x5e6228000-0x5e622cfff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x0001-0x00062fff] [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009dfff] [0.00] node 0: [mem 0x0010-0xcf378fff] [0.00] node 0: [mem 0x0001
Bug#866845: Pending fixes for bugs in the javatools package
tag 866845 + pending thanks Some bugs in the javatools package are closed in revision baff5c885e1b7ce2033568f6da173ac25e72f741 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/javatools.git/commit/?id=baff5c8 Commit message: jh_build: Use ISO8859-1 as the default encoding to avoid unmappable character errors (Closes: #866845)
Processed: Pending fixes for bugs in the javatools package
Processing commands for cont...@bugs.debian.org: > tag 866845 + pending Bug #866845 [src:libidw-java] libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 866845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 851748 to menu-cache, fixed 851748 in 1.0.2-2, affects 851748, notfixed 495915 in 1.8.2-1 ...
Processing commands for cont...@bugs.debian.org:
> # fixing up bug metadata to allow archival
> reassign 851748 menu-cache
Bug #851748 {Done: Andriy Grytsenko } [libfm-extra4]
libfm-extra4 in debian/testing kills LXDE menus
Bug reassigned from package 'libfm-extra4' to 'menu-cache'.
No longer marked as found in versions libfm/1.2.5-1.
No longer marked as fixed in versions menu-cache/1.0.2-2.
> fixed 851748 1.0.2-2
Bug #851748 {Done: Andriy Grytsenko } [menu-cache]
libfm-extra4 in debian/testing kills LXDE menus
There is no source info for the package 'menu-cache' at version '1.0.2-2' with
architecture ''
Unable to make a source version for version '1.0.2-2'
Marked as fixed in versions 1.0.2-2.
> affects 851748 + libfm-extra4
Bug #851748 {Done: Andriy Grytsenko } [menu-cache]
libfm-extra4 in debian/testing kills LXDE menus
Added indication that 851748 affects libfm-extra4
> notfixed 495915 1.8.2-1
Bug #495915 {Done: "Barak A. Pearlmutter" } [stopmotion]
stopmotion: messagebox with a warning appears.
There is no source info for the package 'stopmotion' at version '1.8.2-1' with
architecture ''
Unable to make a source version for version '1.8.2-1'
No longer marked as fixed in versions stopmotion/1.8.2-1.
> fixed 495915 0.8.2-1
Bug #495915 {Done: "Barak A. Pearlmutter" } [stopmotion]
stopmotion: messagebox with a warning appears.
Marked as fixed in versions stopmotion/0.8.2-1.
> fixed 859502 3.0.2+ds-1~exp1
Bug #859502 {Done: Roger Shimizu } [shadowsocks-libev]
shadowsocks-libev: typos in manpages
Marked as fixed in versions shadowsocks-libev/3.0.2+ds-1~exp1.
> reassign 796490 texlive-bin
Bug #796490 {Done: Norbert Preining } [texlive-latex-base]
[texlive-latex-base] pdflatex does not create reproducible pdfs with multiple
images
Bug reassigned from package 'texlive-latex-base' to 'texlive-bin'.
No longer marked as found in versions texlive-base/2014.20141024-2.
No longer marked as fixed in versions texlive-bin/2016.20160513.41080.dfsg-2.
> fixed 796490 2016.20160513.41080.dfsg-2
Bug #796490 {Done: Norbert Preining } [texlive-bin]
[texlive-latex-base] pdflatex does not create reproducible pdfs with multiple
images
There is no source info for the package 'texlive-bin' at version
'2016.20160513.41080.dfsg-2' with architecture ''
Unable to make a source version for version '2016.20160513.41080.dfsg-2'
Marked as fixed in versions 2016.20160513.41080.dfsg-2.
> reassign 711470 src:open-ath9k-htc-firmware
Bug #711470 {Done: Oleksij Rempel }
[firmware-linux-free] ath9k_htc updated firmware for firmware-linux-free
Bug #810047 {Done: Oleksij Rempel }
[firmware-linux-free] firmware-linux-free: ath9k_htc firmware (now fully free)
not provided by package
Bug #810672 {Done: Oleksij Rempel }
[firmware-linux-free] firmware-linux-free should include the ath9k_htc firmware
Bug reassigned from package 'firmware-linux-free' to
'src:open-ath9k-htc-firmware'.
Bug reassigned from package 'firmware-linux-free' to
'src:open-ath9k-htc-firmware'.
Bug reassigned from package 'firmware-linux-free' to
'src:open-ath9k-htc-firmware'.
No longer marked as found in versions firmware-free/3.3, firmware-free/3.2, and
firmware-free/3.4.
No longer marked as found in versions firmware-free/3.2, firmware-free/3.4, and
firmware-free/3.3.
No longer marked as found in versions firmware-free/3.3, firmware-free/3.2, and
firmware-free/3.4.
No longer marked as fixed in versions
open-ath9k-htc-firmware/1.4.0-81-gf206e56+dfsg-1.
No longer marked as fixed in versions
open-ath9k-htc-firmware/1.4.0-81-gf206e56+dfsg-1.
No longer marked as fixed in versions
open-ath9k-htc-firmware/1.4.0-81-gf206e56+dfsg-1.
> fixed 711470 1.4.0-81-gf206e56+dfsg-1
Bug #711470 {Done: Oleksij Rempel }
[src:open-ath9k-htc-firmware] ath9k_htc updated firmware for firmware-linux-free
Bug #810047 {Done: Oleksij Rempel }
[src:open-ath9k-htc-firmware] firmware-linux-free: ath9k_htc firmware (now
fully free) not provided by package
Bug #810672 {Done: Oleksij Rempel }
[src:open-ath9k-htc-firmware] firmware-linux-free should include the ath9k_htc
firmware
Marked as fixed in versions open-ath9k-htc-firmware/1.4.0-81-gf206e56+dfsg-1.
Marked as fixed in versions open-ath9k-htc-firmware/1.4.0-81-gf206e56+dfsg-1.
Marked as fixed in versions open-ath9k-htc-firmware/1.4.0-81-gf206e56+dfsg-1.
> affects 711470 + firmware-linux-free
Bug #711470 {Done: Oleksij Rempel }
[src:open-ath9k-htc-firmware] ath9k_htc updated firmware for firmware-linux-free
Bug #810047 {Done: Oleksij Rempel }
[src:open-ath9k-htc-firmware] firmware-linux-free: ath9k_htc firmware (now
fully free) not provided by package
Bug #810672 {Done: Oleksij Rempel }
[src:open-ath9k-htc-firmware] firmware-linux-free should include the ath9k_htc
firmware
Added indication that 711470 affects firmware-linux-free
Added indication that 810047 affects firmware-linux-free
Added indication that 810672 affects firmware-linux-free
> reassign 688280 src:android-platform-system-core
Bug #688280 {Done: Hans-Christoph St
Bug#866858: marked as done (felix-main FTBFS: Failed to execute goal morg.apache.maven.plugins:maven-dependency-plugin:2.8:copy)
Your message dated Sun, 02 Jul 2017 22:19:07 + with message-id and subject line Bug#866858: fixed in felix-main 5.0.0-5 has caused the Debian Bug report #866858, regarding felix-main FTBFS: Failed to execute goal morg.apache.maven.plugins:maven-dependency-plugin:2.8:copy 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.) -- 866858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: felix-main Version: 5.0.0-4 Severity: serious Tags: buster sid Some recent change in unstable makes felix-main FTBFS: https://tests.reproducible-builds.org/debian/history/felix-main.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/felix-main.html ... [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1;31mBUILD FAILURE[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] Total time: 12.927 s [[1;34mINFO[m] Finished at: 2018-08-04T02:21:40-12:00 [[1;34mINFO[m] Final Memory: 29M/662M [[1;34mINFO[m] [1m[m [[1;31mERROR[m] Failed to execute goal [32morg.apache.maven.plugins:maven-dependency-plugin:2.8:copy[m [1m(copy)[m on project [36morg.apache.felix.main[m: [1;31mUnable to find artifact.[m: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.felix:org.apache.felix.bundlerepository:jar:2.0.8 has not been downloaded from it before. [[1;31mERROR[m] [[1;31mERROR[m] Try downloading the file manually from the project website. [[1;31mERROR[m] [[1;31mERROR[m] Then, install it using the command: [[1;31mERROR[m] mvn install:install-file -DgroupId=org.apache.felix -DartifactId=org.apache.felix.bundlerepository -Dversion=2.0.8 -Dpackaging=jar -Dfile=/path/to/file [[1;31mERROR[m] [[1;31mERROR[m] Alternatively, if you host your own repository you can deploy the file there: [[1;31mERROR[m] mvn deploy:deploy-file -DgroupId=org.apache.felix -DartifactId=org.apache.felix.bundlerepository -Dversion=2.0.8 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [[1;31mERROR[m] [[1;31mERROR[m] [[1;31mERROR[m] org.apache.felix:org.apache.felix.bundlerepository:jar:2.0.8 [[1;31mERROR[m] [[1;31mERROR[m] from the specified remote repositories: [[1;31mERROR[m] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false) [[1;31mERROR[m] -> [1m[Help 1][m [[1;31mERROR[m] [[1;31mERROR[m] To see the full stack trace of the errors, re-run Maven with the [1m-e[m switch. [[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full debug logging. [[1;31mERROR[m] [[1;31mERROR[m] For more information about the errors and possible solutions, please read the following articles: [[1;31mERROR[m] [1m[Help 1][m http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 --- End Message --- --- Begin Message --- Source: felix-main Source-Version: 5.0.0-5 We believe that the bug you reported is fixed in the latest version of felix-main, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated felix-main 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, 03 Jul 2017 00:08:45 +0200 Source: felix-main Binary: libfelix-main-java libfelix-main-java-doc felix-main Architecture: source Version: 5.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: felix-main - Execution environment for OSGi Felix Framework libfelix-main-java - Libraries to instantiate and execute the Felix Framework libfelix-main-java-doc - Libraries to instantiate and execute OSGi Felix Framework - doc Closes: 866858 Changes: felix-main (5.0.0-5) uns
Bug#866858: Pending fixes for bugs in the felix-main package
tag 866858 + pending thanks Some bugs in the felix-main package are closed in revision 0449b4805a6b257dea4f3f1dbf194ce6709a9d48 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/felix-main.git/commit/?id=0449b48 Commit message: Fixed the build failure cause by the update of felix-bundlerepository (Closes: #866858)
Processed: Pending fixes for bugs in the felix-main package
Processing commands for cont...@bugs.debian.org: > tag 866858 + pending Bug #866858 [src:felix-main] felix-main FTBFS: Failed to execute goal morg.apache.maven.plugins:maven-dependency-plugin:2.8:copy Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 866858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#865588 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 865588 pending Bug #865588 [src:djangorestframework] djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 865588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865588: marked as pending
tag 865588 pending thanks Hello, Bug #865588 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/djangorestframework.git/commit/?id=a32c05f --- commit a32c05f3f201b3e8e7913b5b3e8e3599a9c91c93 Author: Brian May Date: Mon Jul 3 08:03:09 2017 +1000 Updates for 3.6.3-1 diff --git a/debian/changelog b/debian/changelog index 8ab50b5..a7e3e2c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +djangorestframework (3.6.3-1) UNRELEASED; urgency=medium + + * New upstream version. Closes: #865588. + + -- Brian May Mon, 03 Jul 2017 08:00:12 +1000 + djangorestframework (3.4.0-2) unstable; urgency=medium * Don't move grid.png to wrong spot in python3 package. Closes: #858811.
Bug#866532: marked as done (inkscape: Fails to start because of libgsl.so.0 can't be found)
Your message dated Mon, 3 Jul 2017 00:06:12 +0200 with message-id <20170702220610.7l3key27dukkp...@mapreri.org> and subject line Re: Bug#866532: inkscape: Fails to start because of libgsl.so.0 can't be found has caused the Debian Bug report #866532, regarding inkscape: Fails to start because of libgsl.so.0 can't be found 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.) -- 866532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: inkscape Version: 0.92.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, Inkscape fails to start with the following error message: $ inkscape inkscape: error while loading shared libraries: libgsl.so.0: cannot open shared object file: No such file or directory The problem appeared after I upgraded my system from jessie to stretch. Best, Greg -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages inkscape depends on: ii libaspell150.60.7~20110707-3+b2 ii libatk1.0-02.22.0-1 ii libatkmm-1.6-1v5 2.24.2-2 ii libc6 2.24-11+deb9u1 ii libcairo2 1.14.8-1 ii libcairomm-1.0-1v5 1.12.0-1+b1 ii libcdr-0.1-1 0.1.3-3+b1 ii libdbus-1-31.10.18-1 ii libdbus-glib-1-2 0.108-2 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgc1c2 1:7.4.2-8 ii libgcc11:6.3.0-18 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libglibmm-2.4-1v5 2.50.0-1 ii libgomp1 6.3.0-18 ii libgsl22.3+dfsg-1 ii libgtk2.0-02.24.31-2 ii libgtkmm-2.4-1v5 1:2.24.5-1 ii libgtkspell0 2.0.16-1.1 ii libjpeg62-turbo1:1.5.1-2 ii liblcms2-2 2.8-4 ii libmagick++-6.q16-78:6.9.7.4+dfsg-11 ii libmagickcore-6.q16-3 8:6.9.7.4+dfsg-11 ii libmagickwand-6.q16-3 8:6.9.7.4+dfsg-11 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-01.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libpangomm-1.4-1v5 2.40.1-3 ii libpng16-161.6.28-1 ii libpoppler-glib8 0.48.0-2 ii libpoppler64 0.48.0-2 ii libpopt0 1.16-10+b2 ii libpotrace01.13-3 ii librevenge-0.0-0 0.0.4-6 ii libsigc++-2.0-0v5 2.10.0-1 ii libstdc++6 6.3.0-18 ii libvisio-0.1-1 0.1.5-4+b1 ii libwpg-0.3-3 0.3.1-3 ii libx11-6 2:1.6.4-3 ii libxml22.9.4+dfsg1-2.2 ii libxslt1.1 1.1.29-2.1 ii python 2.7.13-2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages inkscape recommends: ii aspell 0.60.7~20110707-3+b2 ii fig2dev [transfig] 1:3.2.6a-2 ii imagemagick 8:6.9.7.4+dfsg-11 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11 ii libimage-magick-perl 8:6.9.7.4+dfsg-11 ii libwmf-bin 0.2.8.4-10.6 ii python-lxml 3.7.1-1 ii python-numpy 1:1.12.1-3 ii python-scour 0.32-2 ii transfig 1:3.2.6a-2 Versions of packages inkscape suggests: pn dia | dia-gnome pn libsvg-perl pn libxml-xql-perl ii pstoedit 3.70-3+b2 pn python-uniconvertor ii ruby 1:2.3.3 -- no debconf information --- End Message --- --- Begin Message --- On Sun, Jul 02, 2017 at 11:55:44PM +0200, greg masliah wrote: > I was actually a bit hesitant to submit this report, and indeed I should > have investigated a bit more. Ah, don't broom over it too much :) > You were right: I wasn't executing version 0.92.1-1 from stretch, but a > self-compiled version, which was linked to libgsl.so.0. Everything works > fine now. All my apologies. Cool! Good to know there was nothing so bad going on :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/de
Bug#866856: marked as done (eclipse-aether FTBFS: Aether Implementation FAILURE)
Your message dated Sun, 02 Jul 2017 22:04:12 + with message-id and subject line Bug#866856: fixed in eclipse-aether 1.0.2-2 has caused the Debian Bug report #866856, regarding eclipse-aether FTBFS: Aether Implementation FAILURE 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.) -- 866856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eclipse-aether Version: 1.0.2-1 Severity: serious Tags: buster sid Some recent change in unstable makes eclipse-aether FTBFS: https://tests.reproducible-builds.org/debian/history/eclipse-aether.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/eclipse-aether.html ... [[1;34mINFO[m] Aether . [1;32mSUCCESS[m [ 0.487 s] [[1;34mINFO[m] Aether API . [1;32mSUCCESS[m [ 4.248 s] [[1;34mINFO[m] Aether SPI . [1;32mSUCCESS[m [ 0.418 s] [[1;34mINFO[m] Aether Test Utilities .. [1;32mSUCCESS[m [ 0.575 s] [[1;34mINFO[m] Aether Utilities ... [1;32mSUCCESS[m [ 1.030 s] [[1;34mINFO[m] Aether Implementation .. [1;31mFAILURE[m [ 0.002 s] [[1;34mINFO[m] Aether Connector Basic . [1;33mSKIPPED[m [[1;34mINFO[m] Aether Transport Classpath . [1;33mSKIPPED[m [[1;34mINFO[m] Aether Transport File .. [1;33mSKIPPED[m [[1;34mINFO[m] Aether Transport HTTP .. [1;33mSKIPPED[m [[1;34mINFO[m] Aether Transport Wagon . [1;33mSKIPPED[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1;31mBUILD FAILURE[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] Total time: 7.163 s [[1;34mINFO[m] Finished at: 2018-08-04T02:19:55-12:00 [[1;34mINFO[m] Final Memory: 26M/901M [[1;34mINFO[m] [1m[m [[1;31mERROR[m] Plugin org.sonatype.plugins:sisu-maven-plugin:1.1 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.sonatype.plugins:sisu-maven-plugin:jar:1.1 has not been downloaded from it before. -> [1m[Help 1][m [[1;31mERROR[m] [[1;31mERROR[m] To see the full stack trace of the errors, re-run Maven with the [1m-e[m switch. [[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full debug logging. [[1;31mERROR[m] [[1;31mERROR[m] For more information about the errors and possible solutions, please read the following articles: [[1;31mERROR[m] [1m[Help 1][m http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 --- End Message --- --- Begin Message --- Source: eclipse-aether Source-Version: 1.0.2-2 We believe that the bug you reported is fixed in the latest version of eclipse-aether, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated eclipse-aether 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, 02 Jul 2017 23:47:14 +0200 Source: eclipse-aether Binary: libeclipse-aether-java Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libeclipse-aether-java - Library to handle Java artifact repositories Closes: 866856 Changes: eclipse-aether (1.0.2-2) unstable; urgency=medium . * Team upload. * Fixed the build failure with tha latest version of sisu-maven-plugin (Closes: #866856) * Build with the DH sequencer instead of CDBS * Standards-Version updated to 4.0
Bug#865926:
retitle -1 fails tests with python 3.6 FWIW, 0.9.4 still fails tests with Python 3.6, I was initially confused because the package does not depend on python3-all and so only runs the 3.6 tests when 3.6 is default, not merely supported (another bug, I guess!)
Bug#866532: inkscape: Fails to start because of libgsl.so.0 can't be found
Hi Mattia, I was actually a bit hesitant to submit this report, and indeed I should have investigated a bit more. You were right: I wasn't executing version 0.92.1-1 from stretch, but a self-compiled version, which was linked to libgsl.so.0. Everything works fine now. All my apologies. Best, Greg On Sun, Jul 2, 2017 at 4:55 PM, Mattia Rizzolo wrote: > Control: tag -1 moreinfo unreproducible > > On Fri, Jun 30, 2017 at 12:33:44AM +0200, greggy wrote: > > Inkscape fails to start with the following error message: > > > > $ inkscape > > inkscape: error while loading shared libraries: libgsl.so.0: cannot open > shared object file: No such file or directory > > > > The problem appeared after I upgraded my system from jessie to stretch. > > Of course I can't reproduce it… > I given how widespread inkscape is and you're the only one reporting it > makes me believe there is something wrong on your side. > > For example, are you sure you are running the binary coming from the > Debian archive? > Our inkscape should be built against libgsl.so.19, not libgsl.so.0 as > your error message reports. > > It makes me believe you somehow have the binary coming from jessie, > which was built against libgsl.so.0 indeed. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- >
Bug#866551:
The attached patch does not work for two reasons. One, very boring, is that
there is more code that sets PYTHONPATH in translate/storage/test_mo.py.
The other reason, sadly, is that even once that's gone the tests still fail
like this:
_
test_po_to_xliff
_
@pytest.mark.skipif('TTKIT_SKIP_COMMANDS' in os.environ,
reason='Skip testing command line tools')
def test_po_to_xliff():
OUTPUT = 'af-pootle.xlf'
> assert call(['po2xliff', 'af-pootle.po', OUTPUT]) == 0
E assert 1 == 0
E+ where 1 = call(['po2xliff', 'af-pootle.po', 'af-pootle.xlf'])
test_xliff_conformance.py:64: AssertionError
---
Captured stderr call
---
Traceback (most recent call last):
File
"/build/translate-toolkit-ZSDMoF/translate-toolkit-2.0.0/debian/python3-translate/usr/bin/po2xliff",
line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3037, in
@_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3021, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3050, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
655, in _build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
969, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
855, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'translate-toolkit==2.0.0'
distribution was not found and is required by the application
This is not so surprising when you think about it, translate-toolkit for
the default version of Python 3 is not in any sense installed so how could
pkg_resources find it?
Short of going in to bat with upstream for PYTHON35PATH, PYTHON36PATH
environment variables I don't think there's much that can be done. There is
already a debian patch to add an environment variable to allow skipping the
CLI tools (TTKIT_SKIP_COMMANDS), I guess it should be set when testing
non-default versions of Python 3?
Cheers,
mwh
Bug#866856: Pending fixes for bugs in the eclipse-aether package
tag 866856 + pending thanks Some bugs in the eclipse-aether package are closed in revision b9549d4e74d269511961df920113bb5a21d5a0d1 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/eclipse-aether.git/commit/?id=b9549d4 Commit message: Fixed the build failure with tha latest version of sisu-maven-plugin (Closes: #866856)
Processed: Pending fixes for bugs in the eclipse-aether package
Processing commands for cont...@bugs.debian.org: > tag 866856 + pending Bug #866856 [src:eclipse-aether] eclipse-aether FTBFS: Aether Implementation FAILURE Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 866856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865802: marked as pending
tag 865802 pending thanks Hello, Bug #865802 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/django-filter.git/commit/?id=df7fa09 --- commit df7fa09c9cb9e381c1e6d2001ff05582fa89d7fe Author: Brian May Date: Mon Jul 3 07:35:41 2017 +1000 Update changelog entry for 1.0.4-1. diff --git a/debian/changelog b/debian/changelog index 34d3396..023bc53 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,9 +1,10 @@ -django-filter (0.13.0-2) UNRELEASED; urgency=medium +django-filter (1.0.4-1) UNRELEASED; urgency=medium * Remove broken symlink. Closes: #857825. * Fix minor lintian warnings. + * New upstream version. Closes: #865802, closes: #863024. - -- Brian May Sat, 18 Mar 2017 16:39:47 +1100 + -- Brian May Mon, 03 Jul 2017 07:34:00 +1000 django-filter (0.13.0-1) unstable; urgency=medium
Processed: Bug#865802 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 865802 pending Bug #865802 [src:django-filter] django-filter FTBFS with Django 1.11 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 865802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865252: marked as done (Please update dependencies from latex-xcolor to tl-latex-recommended)
Your message dated Sun, 02 Jul 2017 21:20:59 + with message-id and subject line Bug#865252: fixed in sdformat 4.2.0-2 has caused the Debian Bug report #865252, regarding Please update dependencies from latex-xcolor to tl-latex-recommended 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.) -- 865252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sdformat Version: 4.2.0-1 Severity: serious Justification: FTBFS X-Debbugs-CC: debian-tex-ma...@lists.debian.org Dear maintainer, latex-xcolor has been a dummy transitional package now since 2 releases (since oldstable), and has been dropped in current unstable. Please update your dependencies to texlive-latex-recommended. Thanks Norbert --- End Message --- --- Begin Message --- Source: sdformat Source-Version: 4.2.0-2 We believe that the bug you reported is fixed in the latest version of sdformat, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated sdformat 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, 02 Jul 2017 22:54:42 +0200 Source: sdformat Binary: libsdformat4 libsdformat4-dev sdformat-sdf sdformat-doc Architecture: source Version: 4.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Description: libsdformat4 - Simulation Description Format (SDF) parser - Shared library libsdformat4-dev - Simulation Description Format (SDF) parser - Development files sdformat-doc - Simulation Description Format (SDF) parser - Documentation sdformat-sdf - Simulation Description Format (SDF) parser - SDF files Closes: 865252 Changes: sdformat (4.2.0-2) unstable; urgency=medium . * [507060f] Use texlive-latex-recommended instead of latex-xcolor. (Closes: #865252) * [c2b854d] Remove myself from uploaders. Checksums-Sha1: 518e39bf1cefb8f88810b0aa01e87375419ab618 2545 sdformat_4.2.0-2.dsc 6b5e632b6fd7dc31c706d88a7d457489bf2d5b36 8392 sdformat_4.2.0-2.debian.tar.xz 6d506c64a8c843a23a682568f1b3eb898f30287c 10493 sdformat_4.2.0-2_source.buildinfo Checksums-Sha256: cdd028eede0761826f0f124f29ccf3a55e8872dc153fec2befdbdd40fef2ebd2 2545 sdformat_4.2.0-2.dsc 6522474bf144dc267f023103922a259cc8e68a1e9435fca426ba7114bcc09603 8392 sdformat_4.2.0-2.debian.tar.xz 7de85fbaa86201af18b524cafb0ee3f15cf5efb27132f2649d421676fd0ddd64 10493 sdformat_4.2.0-2_source.buildinfo Files: 2d71db8b1dd23963d8377c51db3d7c31 2545 science optional sdformat_4.2.0-2.dsc 62eef4e45cfe5ee90f657697ddfdaee1 8392 science optional sdformat_4.2.0-2.debian.tar.xz d84415c740ab7165d7887ec764e62123 10493 science optional sdformat_4.2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAllZXboACgkQ0+Fzg8+n /wavGA//Tj37kt96N9s1WL9de4/xjyDJNGfWzXHsAnGcWwBAI3YCHwYYfQ01AAex nT3Y1u0vxbS3ytD4sFAWxkMJONa/ZjQjEsMSXc005dZ9zMDN7lB2VtQvskfn7NET pve2hTHPKOIk0p1Sn2tR+tOcbLHHsgCp9X7vOHpy/tMIQOUta4+b4+/AjNTF9Vb/ vkwqbFBEaBhROfDzv+Y3eUYqbNMutvNCUBLWuj8EHMYAtsqSKHPq2IdsvzbG/Pka 0D7CHqEjhCCE7cR2QmnuVYuwbm1IRHuKlzcPnd9O4+Ocp5hhdIGsxI1rUMENpHmQ adgJw1X0mw6vlPZ7eHhMSUHjSrJiBHgKho9UMc8eQc9gKpeuUAPhwLn8Y3RpWHDg l7wGhxPKh2ooeMtyq/U9mUKwFLGcSxCkQkmX0VPL9y41S+xJiQ03MQXUX1d7FdaR X5NqPYJMvWmOs8b+QxA1TZybnUh5YENKmGFPzCL325YmYKkwbVAxMRgJ8kynCX0A g+7LdVB//cPNgbTeXuhyVGe+eaRZKli8buO62mJdBcR13b7jqauDxfmAUJsiTsGk gCwJQcJnwouDlmkqrW+P7+OluDd6Zy3qFV/xP97hU6hcxLUytaRxL4y8VabBA0I3 qXdjkOtM7TUBgyOLVgwTQx/qZlHpTsRvN0KGP3oR1LjIzzk/ZaQ= =+0uI -END PGP SIGNATURE End Message ---
Bug#866944: libmecab-perl: FTBFS: no such file or directory: /var/lib/mecab/dic/debian/dicrc
Package: libmecab-perl Version: 0.99.6-1 Severity: serious Tags: sid buster Control: block 866389 with -1 X-Debbugs-Cc: mecab-juman...@packages.debian.org, mecab-ut...@packages.debian.org This package fails to build on current sid/amd64. dh_auto_test make -j1 test TEST_VERBOSE=1 make[1]: Entering directory '/<>' Running Mkbootstrap for MeCab () chmod 644 "MeCab.bs" PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl RuntimeError param.cpp(69) [ifs] no such file or directory: /var/lib/mecab/dic/debian/dicrc 0.996 Makefile:985: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 This seems to have been broken by the new version of src:mecab-jumandic in unstable. It looks like the mecab-utils programs in /usr/lib/mecab/ need /var/lib/mecab/dic/debian/dicrc : # /usr/lib/mecab/mecab-dict-index dictionary_compiler.cpp(82) [param.load(DCONF(DICRC))] no such file or directory: ./dicrc # /usr/lib/mecab/mecab-dict-gen dictionary_generator.cpp(212) [param.load(DCONF(DICRC))] no such file or directory: ./dicrc Copying the maintainers. -- Niko Tyni nt...@debian.org
Processed: libmecab-perl: FTBFS: no such file or directory: /var/lib/mecab/dic/debian/dicrc
Processing control commands: > block 866389 with -1 Bug #866389 [release.debian.org] transition: perl 5.26 866389 was blocked by: 865045 826502 826497 866315 865033 865893 865888 865034 866317 827640 865380 865477 826505 865898 865482 865020 826489 809352 866389 was not blocking any bugs. Added blocking bug(s) of 866389: 866944 -- 866389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866389 866944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 866883
Processing commands for cont...@bugs.debian.org: > tags 866883 + sid buster Bug #866883 [python3-matplotlib] Matplotlib does not work with Python 3.6 Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 866883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866855: libgettext-commons-java FTBFS: Gettext Commons build failure
Le 2/07/2017 à 18:35, tony mancill a écrit : > All of these build failures have libmaven-assembly-plugin-java in > common, and after a rebuild of libmaven-assembly-plugin-java against the > newer libplexus-interpolation-java, I'm able to build > libgettext-commons-java locally. Therefore, I'm going to reassign this > bug and hopefully address it with an upload of maven-assembly. I'd add that most of the time maven-assembly-plugin isn't required for building our packages. So this could probably be solved by ignoring this plugin. Emmanuel Bourg
Processed: severity of 859535 is serious, tagging 859535
Processing commands for cont...@bugs.debian.org: > severity 859535 serious Bug #859535 [src:avr-libc] avr-libc: please drop the build-dependency on autoconf2.59 Severity set to 'serious' from 'important' > tags 859535 + sid buster Bug #859535 [src:avr-libc] avr-libc: please drop the build-dependency on autoconf2.59 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 859535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 855120 is serious, tagging 855120
Processing commands for cont...@bugs.debian.org: > severity 855120 serious Bug #855120 [src:opentk] opentk: Please disable OpenGL ES 1 support Severity set to 'serious' from 'normal' > tags 855120 + sid buster Bug #855120 [src:opentk] opentk: Please disable OpenGL ES 1 support Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 855120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 768604 is serious, tagging 768604
Processing commands for cont...@bugs.debian.org:
> severity 768604 serious
Bug #768604 {Done: Evgeni Golov } [sdl-ball-data]
sdl-ball-data -- depends on transitional package ttf-alee
Severity set to 'serious' from 'normal'
> tags 768604 + sid buster
Bug #768604 {Done: Evgeni Golov } [sdl-ball-data]
sdl-ball-data -- depends on transitional package ttf-alee
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
768604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#866925: nexus: switch B-D from libhdf4g-dev to libhdf4-dev
Source: nexus Version: 4.3.2-svn1921-5 Severity: serious The transitional libhdf4g-dev package is no longer built. Please switch to libhdf4-dev. Andreas
Bug#866920: prometheus: switch B-D from golang-goleveldb-dev to golang-github-syndtr-goleveldb-dev
Source: prometheus Version: 1.6.2+ds-2 Severity: serious golang-goleveldb-dev has been renamed to golang-github-syndtr-goleveldb-dev, the old name is no longer built/provided. Andreas
Bug#856645: docker.io: can't install in sid: docker.io 1.11 depends on runc which breaks docker < 1.12
Indeed, I now have 1.13.1~ds1-2 installed in sid. Thanks! On Tue, Jun 27, 2017 at 12:39 AM, Antoine Beaupre wrote: > Control: fixed -1 1.13.1~ds1-2 > > On Fri, Mar 03, 2017 at 11:11:36AM +0200, Dov Feldstern wrote: > > Current versions of docker.io and runc conflict; docker.io depends on > runc, but: > > > > runc : Breaks: docker.io (< 1.12) but 1.11.2~ds1-6 is to be installed > > I believe this is now fixed: I installed docker.io from sid in stretch > without problems. > > A. >
Processed: reassign 864953 to dpkg,shared-mime-info, found 864953 in 1.18.24, found 864953 in 1.8-1
Processing commands for cont...@bugs.debian.org: > reassign 864953 dpkg,shared-mime-info Bug #864953 [dpkg] dpkg: trigger problems with shared-mime-info while upgrading gnome-screensaver:i386 from jessie to stretch Bug reassigned from package 'dpkg' to 'dpkg,shared-mime-info'. No longer marked as found in versions dpkg/1.18.24. Ignoring request to alter fixed versions of bug #864953 to the same values previously set > found 864953 1.18.24 Bug #864953 [dpkg,shared-mime-info] dpkg: trigger problems with shared-mime-info while upgrading gnome-screensaver:i386 from jessie to stretch There is no source info for the package 'shared-mime-info' at version '1.18.24' with architecture '' Marked as found in versions dpkg/1.18.24. > found 864953 1.8-1 Bug #864953 [dpkg,shared-mime-info] dpkg: trigger problems with shared-mime-info while upgrading gnome-screensaver:i386 from jessie to stretch There is no source info for the package 'dpkg' at version '1.8-1' with architecture '' Marked as found in versions shared-mime-info/1.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 864953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: baloo: is this obsoleted by src:baloo-kf5?
Processing control commands: > tag -1 patch Bug #854884 [baloo4] baloo: is this obsoleted by src:baloo-kf5? Added tag(s) patch. -- 854884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#854884: baloo: is this obsoleted by src:baloo-kf5?
Followup-For: Bug #854884
Control: tag -1 patch
Hi,
based on Boyuan's comment
"In my understanding, perhaps baloo4 is completely useless in
Debian Stretch with Plasma 5"
I'm attaching patches for src:baloo and src:baloo-kf5 to
* turn baloo4 into a transitional package pulling in baloo (>= 4:5)
* let baloo-kf5 co-exist with the transitional baloo4
I tried to keep the changes minimal s.t. these packages should be
rebuildable for stretch-pu with versions 5.28.0-3~deb9u1 and
4.14.3-4~deb9u1. I'd expect simply dropping baloo4 from stretch
after it had been released would not be acceptable.
Andreas
diff -Nru baloo-4.14.3/debian/baloo4.install baloo-4.14.3/debian/baloo4.install
--- baloo-4.14.3/debian/baloo4.install 2014-08-02 08:09:41.0 +0200
+++ baloo-4.14.3/debian/baloo4.install 1970-01-01 01:00:00.0 +0100
@@ -1,6 +0,0 @@
-etc/dbus-1/system.d/org.kde.baloo.*
-usr/bin/baloo*
-usr/share/autostart/baloo_*
-usr/share/dbus-1/system-services/org.kde.baloo.*
-usr/share/icons/*/*/apps/baloo.png
-usr/share/polkit-1/actions/org.kde.baloo.*
diff -Nru baloo-4.14.3/debian/changelog baloo-4.14.3/debian/changelog
--- baloo-4.14.3/debian/changelog 2016-07-29 21:33:51.0 +0200
+++ baloo-4.14.3/debian/changelog 2017-07-02 11:41:43.0 +0200
@@ -1,3 +1,10 @@
+baloo (4:4.14.3-4) UNRELEASED; urgency=medium
+
+ * Turn baloo4 into a transitional package pulling in baloo-kf5.
+(Closes: #854884)
+
+ -- Andreas Beckmann Sun, 02 Jul 2017 11:41:43 +0200
+
baloo (4:4.14.3-3) unstable; urgency=medium
* Team upload.
diff -Nru baloo-4.14.3/debian/control baloo-4.14.3/debian/control
--- baloo-4.14.3/debian/control 2016-07-29 21:23:39.0 +0200
+++ baloo-4.14.3/debian/control 2017-07-02 11:41:43.0 +0200
@@ -26,21 +26,11 @@
Package: baloo4
Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends},
- baloo-utils,
- libqt4-sql-sqlite
-Replaces: baloo (<< 4:4.13.2-0ubuntu3),
- kde-runtime (<< 4:4.12.80),
- kde-runtime-data (<< 4:4.12.80)
-Breaks: baloo (<< 4:4.13.2-0ubuntu3),
-kde-runtime (<< 4:4.12.80),
-kde-runtime-data (<< 4:4.12.80)
-Conflicts: baloo-kf5, baloo-kf5-data
-Description: framework for searching and managing metadata
+Depends: ${misc:Depends}, baloo (>= 4:5)
+Description: transitional package for upgrading to baloo-kf5
A framework for searching and managing metadata in KDE.
.
- This package contains the kdelibs4 version of the binaries, it can also
- be replaced with baloo-kf5.
+ This is a transitional package for upgrading to baloo-kf5.
Package: baloo-utils
Architecture: any
diff -Nru baloo-kf5-5.28.0/debian/changelog baloo-kf5-5.28.0/debian/changelog
--- baloo-kf5-5.28.0/debian/changelog 2016-12-07 14:31:44.0 +0100
+++ baloo-kf5-5.28.0/debian/changelog 2017-07-02 12:20:02.0 +0200
@@ -1,3 +1,10 @@
+baloo-kf5 (5.28.0-3) UNRELEASED; urgency=medium
+
+ * baloo-kf5: Make Breaks+Replaces: baloo4 versioned, this was turned into a
+transitional package in 4.14.3-4.
+
+ -- Andreas Beckmann Sun, 02 Jul 2017 12:20:02 +0200
+
baloo-kf5 (5.28.0-2) unstable; urgency=medium
* Add new patch: Disable-the-file-indexer-by-default.patch
diff -Nru baloo-kf5-5.28.0/debian/control baloo-kf5-5.28.0/debian/control
--- baloo-kf5-5.28.0/debian/control 2016-12-07 14:31:44.0 +0100
+++ baloo-kf5-5.28.0/debian/control 2017-07-02 12:19:57.0 +0200
@@ -61,8 +61,8 @@
Section: utils
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
-Breaks: baloo (<< 4:5.0), baloo4, ${kde-l10n:all}
-Replaces: baloo (<< 4:5.0), baloo4, ${kde-l10n:all}
+Breaks: baloo (<< 4:5.0), baloo4 (<< 4.14.3-4~), ${kde-l10n:all}
+Replaces: baloo (<< 4:5.0), baloo4 (<< 4.14.3-4~), ${kde-l10n:all}
Description: framework for searching and managing metadata
A framework for searching and managing metadata in KDE Software.
.
Bug#866790: marked as done (postfix rules yield error and fail)
Your message dated Sun, 02 Jul 2017 14:09:35 -0400 with message-id <87r2xy1zj4@curie.anarc.at> and subject line Re: Bug#866790: postfix rules yield error and fail has caused the Debian Bug report #866790, regarding postfix rules yield error and fail 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.) -- 866790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apparmor Version: 2.11.0-3 Severity: grave Right now, in debian stretch, any apparmor command will yield: $ sudo aa-disable usr.bin.irssi ERROR: Include file /etc/apparmor.d/program-chunks/postfix-common not found ... if apparmor-profiles is installed. This, obviously, is an error in the postfix* apparmor profiles which try to include a non-existing file. The proper file to include is abstractions/postfix-common of course. This seems to have been fixed in unstable, but it should really be fixed in a point update in stretch. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages apparmor depends on: ii debconf [debconf-2.0] 1.5.61 ii init-system-helpers1.48 ii libapparmor-perl 2.11.0-3 ii libc6 2.24-11+deb9u1 ii lsb-base 9.20161125 ii python33.5.3-1 apparmor recommends no packages. Versions of packages apparmor suggests: ii apparmor-profiles2.11.0-3 ii apparmor-profiles-extra 1.11 ii apparmor-utils 2.11.0-3 -- debconf information excluded --- End Message --- --- Begin Message --- On 2017-07-02 10:17:08, intrigeri wrote: > Control: tag -1 + moreinfo > Control: tag -1 + unreproducible > > Hi, > > Antoine Beaupre: >> ERROR: Include file /etc/apparmor.d/program-chunks/postfix-common not found > >> ... if apparmor-profiles is installed. > >> This, obviously, is an error in the postfix* apparmor profiles which >> try to include a non-existing file. The proper file to include is >> abstractions/postfix-common of course. > > Thank you for this report. > > What are "the postfix* apparmor profiles" that include > program-chunks/postfix-common? I.e. where are they installed, and by > which package/version? > > I could not find any such thing in a Stretch chroot after installing > apparmor-profiles. I've looked in > /usr/share/doc/apparmor-profiles/extras/ and in /etc/apparmor.d/. > > Perhaps you copied stuff from /usr/share/doc/apparmor-profiles/extras/ > to /etc/apparmor.d/ in the past and your own copy needs an update? indeed, that looks like it. sorry for the noise. A. PS: seems to me like a good example why profiles-extra should be deployed straight to /etc :p -- I believe that love is a better teacher than a sense of duty. - Albert Einstein--- End Message ---
Bug#866758: solved (maybe)
Currently X will start again. As it seems, the modules for nVidia needed kernel headers to compile, which were not available for kernel 4.9.0-3. Changing kernel and header by hand to 4.11.0-1-amd64 and forcing a recompile of the nVidia kernel modules solved the issue -- at least temporarily. I think it is very important that, on error, the X server tries to boot into a default X server that works for all graphics adapters (vesa ... ?) so you get a graphical user interface at all. Text mode as fallback, especially in 80x24, is a little heavy-handed for all those inexperienced users out there.
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:05:03 + with message-id and subject line Bug#865109: fixed in tryton-modules-purchase-request 4.4.2-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-purchase-request Source-Version: 4.4.2-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-purchase-request, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-purchase-request 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: Sun, 02 Jul 2017 17:43:19 +0200 Source: tryton-modules-purchase-request Binary: tryton-modules-purchase-request Architecture: source all Version: 4.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-purchase-request - Tryton Application Platform (Purchase Request Module) Closes: 865109 Changes: tryton-modules-purchase-request (4.4.2-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.2. Checksums-Sha1: 6a01b3046fa7e44b2513225a25886a5f47cf60fd 2249 tryton-modules-purchase-request_4.4.2-1.dsc c33813ba15b4aae8f3dc909d83649a33e3db21be 35573 tryton-modules-purchase-request_4.4.2.orig.tar.gz 60d854a472cb291c0b1dde69b9ec7bf2ea38607a 30620 tryton-modules-purchase-request_4.4.2-1.debian.tar.xz 14a7d8306671ac27943040a22d7b7ea098b9530e 21218 tryton-modules-purchase-request_4.4.2-1_all.deb dbd72f7e6a9cd3408feeaa3163cc45498be57328 6704 tryton-modules-purchase-request_4.4.2-1_amd64.buildinfo Checksums-Sha256: de934723db4c194bdf19b07f36d08a8c6280438f3c147bf21db4ca16f4b80a1e 2249 tryton-modules-purchase-request_4.4.2-1.dsc 4f75ada2de72230ddc2c7aeb849a37c768777aca08ad3c27d468a7f7e1b2608e 35573 tryton-modules-purchase-request_4.4.2.orig.tar.gz 43c36cb7ff6b164c8261c97acfec0789579eaf1fe2a98ef34bbb22e059961cf1 30620 tryton-modules-purchase-request_4.4.2-1.debian.tar.xz c13fd2119a66388e14ab16b90877d030ae2125a377131e4af1bf305ed7a86b4b 212
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:04:55 + with message-id and subject line Bug#865109: fixed in tryton-modules-party 4.4.1-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-party Source-Version: 4.4.1-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-party, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-party 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: Sun, 02 Jul 2017 17:09:52 +0200 Source: tryton-modules-party Binary: tryton-modules-party Architecture: source all Version: 4.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-party - Tryton Application Platform (Party Module) Closes: 865109 Changes: tryton-modules-party (4.4.1-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.1. Checksums-Sha1: f9a70af6f0881088b85df23bc7f142a9f2decbcc 2128 tryton-modules-party_4.4.1-1.dsc 33faf9c95445ff139a7fab83b4334d768e38e4b0 86186 tryton-modules-party_4.4.1.orig.tar.gz f9e4127462b3f2ac61234486f3acb3d3e56520fd 34344 tryton-modules-party_4.4.1-1.debian.tar.xz 3c35bf09aaf7e2309585385cccbe3ccdcd28ea7a 67388 tryton-modules-party_4.4.1-1_all.deb 3a73a9def9f6e71e9d5175922bee9fc95bd01cc5 6594 tryton-modules-party_4.4.1-1_amd64.buildinfo Checksums-Sha256: 1e3b72964edf6679f0779070c3550064621166ccdd1b258ffca1979e9a9c7090 2128 tryton-modules-party_4.4.1-1.dsc 5cad348ce0aaf71a0cc3fe430cab40943b94ba25c874136f0e0f710ba17c7766 86186 tryton-modules-party_4.4.1.orig.tar.gz 471c288eafc5cee9cff71eda7a362524898e104d300acf256d5ec21fa4b4fc35 34344 tryton-modules-party_4.4.1-1.debian.tar.xz f586eafc7dfd6061c45908e456b03c3a1d1794192a3ad707f079bbe9bae9ecf6 67388 tryton-modules-party_4.4.1-1_all.deb dde1fdb5a487623487f02ee803fa41748b38b703f61e715fb4422500e043674e 6594 tryton-modules-party_4.4.1-1_amd64.buildinfo Files: c1a334863ce851147b226c19
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:05:28 + with message-id and subject line Bug#865109: fixed in tryton-modules-stock-supply-production 4.4.1-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-stock-supply-production Source-Version: 4.4.1-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-stock-supply-production, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-stock-supply-production 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: Sun, 02 Jul 2017 17:16:10 +0200 Source: tryton-modules-stock-supply-production Binary: tryton-modules-stock-supply-production Architecture: source all Version: 4.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-stock-supply-production - Tryton Application Platform (Stock Supply Production Module) Closes: 865109 Changes: tryton-modules-stock-supply-production (4.4.1-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.1. Checksums-Sha1: e832d23ffc87a7dc954a4dee9706612d4cd8fe43 2326 tryton-modules-stock-supply-production_4.4.1-1.dsc 55a1d886046d2dc3e8b7cf2ef972de512278f333 24473 tryton-modules-stock-supply-production_4.4.1.orig.tar.gz 0828c2bb1cd89151f1a300cd8c88f484d924f0de 31656 tryton-modules-stock-supply-production_4.4.1-1.debian.tar.xz 39b0990ba78211367bf59a0b7d43fe7775fd9157 13614 tryton-modules-stock-supply-production_4.4.1-1_all.deb cf13145f54ada0b2a718bdeeb07be571a972c054 6774 tryton-modules-stock-supply-production_4.4.1-1_amd64.buildinfo Checksums-Sha256: 94f37b785d7760d412b4d94fdd791d5d741fce81f3b3180bd60c38c6a63ccf77 2326 tryton-modules-stock-supply-production_4.4.1-1.dsc 51dd08f7c8f733bab8f18840587f6d6a6d1edd4735a93283379aba41bf9b2da6 24473 tryton-modules-stock-supply-production_4.4.1.orig.tar.gz ef5eef80495b40d190b8e558d44701067d3cab3902cbfbfb04c76a35d1a23d2f 31656 tryton-mod
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:05:20 + with message-id and subject line Bug#865109: fixed in tryton-modules-stock-package-shipping-ups 4.4.1-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-stock-package-shipping-ups Source-Version: 4.4.1-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-stock-package-shipping-ups, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-stock-package-shipping-ups 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: Sun, 02 Jul 2017 17:06:58 +0200 Source: tryton-modules-stock-package-shipping-ups Binary: tryton-modules-stock-package-shipping-ups Architecture: source all Version: 4.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-stock-package-shipping-ups - Tryton Application Platform (Stock Package Shipping UPS Module) Closes: 865109 Changes: tryton-modules-stock-package-shipping-ups (4.4.1-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.1. Checksums-Sha1: 839d186678e0ecf17c6e92c4ac093bc037233060 2359 tryton-modules-stock-package-shipping-ups_4.4.1-1.dsc a04fe01b9ecac715eb8dff1bd35e8dc57bcd3dde 32298 tryton-modules-stock-package-shipping-ups_4.4.1.orig.tar.gz f60fc2f5c33d856583b34f305e0bb5b7de96a9ba 30624 tryton-modules-stock-package-shipping-ups_4.4.1-1.debian.tar.xz bb9b8092c575679e51b69168247e65ca889ccf61 17792 tryton-modules-stock-package-shipping-ups_4.4.1-1_all.deb d592dbceb4499d1a69fd7d69eebc111a69fa114f 6804 tryton-modules-stock-package-shipping-ups_4.4.1-1_amd64.buildinfo Checksums-Sha256: d83e620c1d991b82391008384ebe276e87b5ceb72e008e4b8a6355854d27526e 2359 tryton-modules-stock-package-shipping-ups_4.4.1-1.dsc cee4c65a90b3cd45ec4b9ebf4905e2e7a9489d1336dc449de66052749d246d9b 32298 tryton-modules-stock-package-shipping-ups_4.4.1.orig.tar.gz b0a9d4c21668b555793e4cd62bdb6977dc
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:04:39 + with message-id and subject line Bug#865109: fixed in tryton-modules-account-statement 4.4.1-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-account-statement Source-Version: 4.4.1-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-account-statement, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-account-statement 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: Sun, 02 Jul 2017 17:25:19 +0200 Source: tryton-modules-account-statement Binary: tryton-modules-account-statement Architecture: source all Version: 4.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-account-statement - Tryton Application Platform (Account Statement Module) Closes: 865109 Changes: tryton-modules-account-statement (4.4.1-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.1. Checksums-Sha1: 7d8cd4d05e3d792c5aa08acbb95fc5774d039092 2260 tryton-modules-account-statement_4.4.1-1.dsc 41a0ac47e95abf23da2114f9ebaf67ac6e406779 61015 tryton-modules-account-statement_4.4.1.orig.tar.gz b1900ef5197848ccf375ed92406fcf9df4b72f75 32680 tryton-modules-account-statement_4.4.1-1.debian.tar.xz dcc194c23b41816d5a03095d9af656ae1a415eb2 45552 tryton-modules-account-statement_4.4.1-1_all.deb c44163cfdeb850fb04bbf5be48dc39c938631fcf 6714 tryton-modules-account-statement_4.4.1-1_amd64.buildinfo Checksums-Sha256: faee88c0822e62c8e3de32d41d2e62430ad87fc604d7b9ad9ec283de7ce80038 2260 tryton-modules-account-statement_4.4.1-1.dsc c0c48e111a138a756d2df215c371ac835ce1eb97a5232cc75abfce3ec681101f 61015 tryton-modules-account-statement_4.4.1.orig.tar.gz 971ab98a20ba4de6c4754138c193d7bd7ac2587cf83199e5d52dfa18a7b3b7ec 32680 tryton-modules-account-statement_4.4.1-1.debian.tar.xz 4ab1539fe4376a73a03517c1c8fa8eca2ce48270936a04b87f5
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:05:39 + with message-id and subject line Bug#865109: fixed in tryton-server 4.4.2-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-server Source-Version: 4.4.2-1 We believe that the bug you reported is fixed in the latest version of tryton-server, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-server 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: Sun, 02 Jul 2017 16:49:52 +0200 Source: tryton-server Binary: tryton-server tryton-server-doc Architecture: source all Version: 4.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-server - Tryton Application Platform (Server) tryton-server-doc - Tryton Application Platform (Server Documentation) Closes: 865109 Changes: tryton-server (4.4.2-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.2. Checksums-Sha1: 908b94c0109953b345ed322a6f759e5ebdf7989c 2303 tryton-server_4.4.2-1.dsc 46fccb9e9019e37ea46e65fdfff083cfbebde881 599358 tryton-server_4.4.2.orig.tar.gz 08ffcad500472baefceb15be700d50cd2898a404 47456 tryton-server_4.4.2-1.debian.tar.xz b3f6905eb11485568d5e2c233c6c4e5dd40071ee 127180 tryton-server-doc_4.4.2-1_all.deb f4336390d5918597b6ffd2eaa8a66d992e3e2915 380948 tryton-server_4.4.2-1_all.deb d7e9aeac0ab7291d683490743b0353169251c8d7 7772 tryton-server_4.4.2-1_amd64.buildinfo Checksums-Sha256: 27cc18668c8642d421898af3aa4a92cd724c108f89baa2c57fcc5d94c0e54e15 2303 tryton-server_4.4.2-1.dsc 9bc5b65d4314feb2186d30cbf0068f8396c97cfb12d770de05e8ff5fc2d047f8 599358 tryton-server_4.4.2.orig.tar.gz 7727342025c98fc5e9bf4e76881846cc9017dd3fdc01f46f268f79232e4f20e2 47456 tryton-server_4.4.2-1.debian.tar.xz 33d2d0c52dc44f387f9bc15748b24e0b2b4d33508ce2bc5718aa6135658dd64f 127180 tryton-server-doc_4.4.2-1_all.deb 3723531ae9e1daf721976db24cad90220b605d9ababd8bb44c95e83573ce1596 380948 tryton-server_4.4.2-1
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:04:23 + with message-id and subject line Bug#865109: fixed in tryton-modules-account-invoice 4.4.2-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-account-invoice Source-Version: 4.4.2-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-account-invoice, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-account-invoice 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: Sun, 02 Jul 2017 16:47:05 +0200 Source: tryton-modules-account-invoice Binary: tryton-modules-account-invoice Architecture: source all Version: 4.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-account-invoice - Tryton Application Platform (Account Invoice Module) Closes: 865109 Changes: tryton-modules-account-invoice (4.4.2-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.2. Checksums-Sha1: 03d8e9d4127ed7a9f57f05eba6d14853a9d41d91 2241 tryton-modules-account-invoice_4.4.2-1.dsc 10d556fa701384e70e01188a6f95319bbc65ebb5 151664 tryton-modules-account-invoice_4.4.2.orig.tar.gz 336c80b239df33af612bee8d943764f8eb39e141 32964 tryton-modules-account-invoice_4.4.2-1.debian.tar.xz 2c07f15d9073d6d78b48ce15e5600b61b40e503e 88292 tryton-modules-account-invoice_4.4.2-1_all.deb 767a805d798e0ee9810678ba3e995d78d5952e54 6694 tryton-modules-account-invoice_4.4.2-1_amd64.buildinfo Checksums-Sha256: 4386e133e71396dd729a19856901bc4d141725fd90c3e635d4e64ae579feb586 2241 tryton-modules-account-invoice_4.4.2-1.dsc c79801f8090c19e7d87291de880d051c7825295ceba49514b82cc142c6a608bc 151664 tryton-modules-account-invoice_4.4.2.orig.tar.gz 2dc7a22c33dfb9da4211dd53aabf3f1d30284b39294f13271ca3e58efdfe7da3 32964 tryton-modules-account-invoice_4.4.2-1.debian.tar.xz 9b124415f1a77b7c03a899ad0867a56317a9dd1ec02b14b3f9c6e010fc805a17 88292 tryton-modu
Bug#854278: marked as done (CVE-2017-5666)
Your message dated Mon, 3 Jul 2017 03:33:40 +0930 with message-id <20170702180340.gq12...@hex.shelbyville.oz> and subject line Re: CVE-2017-5666 has caused the Debian Bug report #854278, regarding CVE-2017-5666 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.) -- 854278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mp3splt Severity: grave Tags: security Please see https://blogs.gentoo.org/ago/2017/01/29/mp3splt-invalid-free-in-free_options-options_manager-c/ Cheers, Moritz --- End Message --- --- Begin Message --- On Sun, 05 Feb 2017 18:37:33 +0100, Moritz Muehlenhoff wrote: > Package: mp3splt > Severity: grave > Tags: security > > Please see > https://blogs.gentoo.org/ago/2017/01/29/mp3splt-invalid-free-in-free_options-options_manager-c/ >From what I can see in that thread and the upstream bug tracker, the backtrace seems to show it failing deep in libmad, and a lot of people seem to be failing to reproduce it, especially when testing on Debian systems. The best guess so far seems to be that it's actually this bug: https://bugs.debian.org/287519 Which has been elusive since 2004, but at latest update Kurt said he could no longer reproduce it in 2008 ... So I'm going to close it against this package - at least until someone can point at something concrete that's wrong in mp3splt itself to cause this. I've just adopted this package (and a new upload is waiting on binary NEW, which adds the mp3splt-gtk package back again in working order now too), so if someone has other information I'll look into this further - but I'm not seeing anything that warrants keeping mp3splt out of testing any longer because of this report if libmad is where it is actually failing and needs to be fixed. Cheers, Ron--- End Message ---
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:04:32 + with message-id and subject line Bug#865109: fixed in tryton-modules-account-payment-sepa 4.4.2-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-account-payment-sepa Source-Version: 4.4.2-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-account-payment-sepa, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-account-payment-sepa 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: Sun, 02 Jul 2017 17:18:08 +0200 Source: tryton-modules-account-payment-sepa Binary: tryton-modules-account-payment-sepa Architecture: source all Version: 4.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-account-payment-sepa - Tryton Application Platform (Account Payment SEPA Module) Closes: 865109 Changes: tryton-modules-account-payment-sepa (4.4.2-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.2. Checksums-Sha1: 5be6a70a6684f53963c5bad2e0ff43c48bd8460f 2296 tryton-modules-account-payment-sepa_4.4.2-1.dsc 6ec4500c98a0190f8b5d60fd8875609d303fb41c 113965 tryton-modules-account-payment-sepa_4.4.2.orig.tar.gz 033d8be61439f2e3df986fd4c9fb37fbc08c1efa 31228 tryton-modules-account-payment-sepa_4.4.2-1.debian.tar.xz cca7435aa20b524e4a709c6e3eb54d6d633a1b0d 68550 tryton-modules-account-payment-sepa_4.4.2-1_all.deb cbac9e354158d4fa3555b0202643253738e18931 6744 tryton-modules-account-payment-sepa_4.4.2-1_amd64.buildinfo Checksums-Sha256: 92bcf7ec962ef74d15f055f34d876835bda32009d575baeba87323ec792b9900 2296 tryton-modules-account-payment-sepa_4.4.2-1.dsc bbc09341d6e52cdfccfee9523b179bbe4c374a782a3e8b948769d0ea9323658e 113965 tryton-modules-account-payment-sepa_4.4.2.orig.tar.gz dbd8f8779afba3e60fb0fbf93c91c6d623b263890a20257b42f1573b51a024cd 31228 tryton-modules-account-payment-sepa_4.4.2-1.debian.tar.x
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:04:48 + with message-id and subject line Bug#865109: fixed in tryton-modules-account-stock-landed-cost 4.4.1-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-account-stock-landed-cost Source-Version: 4.4.1-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-account-stock-landed-cost, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-account-stock-landed-cost 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: Sun, 02 Jul 2017 17:37:34 +0200 Source: tryton-modules-account-stock-landed-cost Binary: tryton-modules-account-stock-landed-cost Architecture: source all Version: 4.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-account-stock-landed-cost - Tryton Application Platform (Account Stock Landed Cost Module) Closes: 865109 Changes: tryton-modules-account-stock-landed-cost (4.4.1-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.1. Checksums-Sha1: 21140cc58639acd3296d831f925aa4f2a8a57894 2348 tryton-modules-account-stock-landed-cost_4.4.1-1.dsc 657ed175046cbdbf71cc3c661b2fef4dd2c0e641 29354 tryton-modules-account-stock-landed-cost_4.4.1.orig.tar.gz 7983273616d7aef544d689f4d05445e7778b6e6c 30728 tryton-modules-account-stock-landed-cost_4.4.1-1.debian.tar.xz f7e73e66dcdc1066288fe8358b2aab74fa3a35d5 16836 tryton-modules-account-stock-landed-cost_4.4.1-1_all.deb 9087a4167874143718a1d09d8c99052a2b228462 6794 tryton-modules-account-stock-landed-cost_4.4.1-1_amd64.buildinfo Checksums-Sha256: da8f44a03ee0177b29b2eebeccdef5ddf9ecbb4a50d1b359581365bc9fccc35e 2348 tryton-modules-account-stock-landed-cost_4.4.1-1.dsc af8d432146ae380dd79e475ddf1a9171048e05bbddcdba9755dd367d9f1c718d 29354 tryton-modules-account-stock-landed-cost_4.4.1.orig.tar.gz 94ce61e6b9f0743e63b9423fc4d3d1225b11e5bfa772763264
Bug#865109: marked as done (tryton-*: maintainer address bounces)
Your message dated Sun, 02 Jul 2017 18:05:12 + with message-id and subject line Bug#865109: fixed in tryton-modules-stock 4.4.1-1 has caused the Debian Bug report #865109, regarding tryton-*: maintainer address bounces 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.) -- 865109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mail.alioth.debian.org[5.153.231.21] said: 550 Administrative prohibition (in reply to RCPT TO command) Reporting-MTA: dns; mail.virtual-things.org X-Postfix-Queue-ID: 87C301C00E81 X-Postfix-Sender: rfc822; ftpmaster@ftp-master.debian.org Arrival-Date: Mon, 19 Jun 2017 11:33:10 + (UTC) Final-Recipient: rfc822; tryton-debian@lists.alioth.debian.org Original-Recipient: rfc822;maintainers@debian.tryton.org Action: failed Status: 5.0.0 Remote-MTA: dns; mail.alioth.debian.org Diagnostic-Code: smtp; 550 Administrative prohibition --- Begin Message --- tryton-modules-production-routing_4.4.0-1_amd64.changes uploaded successfully to localhost along with the files: tryton-modules-production-routing_4.4.0-1.dsc tryton-modules-production-routing_4.4.0.orig.tar.gz tryton-modules-production-routing_4.4.0-1.debian.tar.xz tryton-modules-production-routing_4.4.0-1_all.deb tryton-modules-production-routing_4.4.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --- End Message --- --- End Message --- --- End Message --- --- Begin Message --- Source: tryton-modules-stock Source-Version: 4.4.1-1 We believe that the bug you reported is fixed in the latest version of tryton-modules-stock, 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 865...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated tryton-modules-stock 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: Sun, 02 Jul 2017 17:12:51 +0200 Source: tryton-modules-stock Binary: tryton-modules-stock Architecture: source all Version: 4.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Description: tryton-modules-stock - Tryton Application Platform (Stock Module) Closes: 865109 Changes: tryton-modules-stock (4.4.1-1) unstable; urgency=medium . * Change the maintainer address to tryton-deb...@lists.alioth.debian.org (Closes: #865109). * Merging upstream version 4.4.1. Checksums-Sha1: 4cee799ddf101de9162c840743044810ecb11fa3 2131 tryton-modules-stock_4.4.1-1.dsc 6d94f2129b11cbb62bcc6cf7c5fc1dfb0e3b5b40 242521 tryton-modules-stock_4.4.1.orig.tar.gz 412b51bfa5b4f5cce5af1a531d311533bd728986 34604 tryton-modules-stock_4.4.1-1.debian.tar.xz 4e7289fb05a73b95baa41894d53e4a017a0b9b7a 158376 tryton-modules-stock_4.4.1-1_all.deb a3cff39c359972e09b21797d3a6aae6e96dddb9d 6597 tryton-modules-stock_4.4.1-1_amd64.buildinfo Checksums-Sha256: 76018fb4b7b546c73073f32e9a3243ced6d8bdfbd27a70aac67fbc6f8f338067 2131 tryton-modules-stock_4.4.1-1.dsc 66bf13057504916b3e62ae578a2cf7048a1d3e58111c70593ab6d81489129ee3 242521 tryton-modules-stock_4.4.1.orig.tar.gz 3f26c1045e921ddca9584423ad6aabe3a3cdcd22096f77dfda0f9dfb9fce87e2 34604 tryton-modules-stock_4.4.1-1.debian.tar.xz 629e042bc7d32a68c75e7c32627874cc870b12552d4d752ae449878136fb4e9a 158376 tryton-modules-stock_4.4.1-1_all.deb 9f3a4c39226eb3adcdfb60bcf2dce13c358c587fd1c252389412ea6d480e2951 6597 tryton-modules-stock_4.4.1-1_amd64.buildinfo Files: 7e117ae21067bd6ea049
Bug#865015: There was a problem reading data from the CD-ROM - Issues with 9.0.1
On Thu, Jun 29, 2017 at 07:59:12PM -0700, First Last wrote: >Hi, > >This is my first post so I'll ask for your forbearance. I've read this bug and >experienced the issue with 9.0.0. I've now tried to use 9.0.1 and I am >experiencing similar issues. > >However, instead of presenting the CD-ROM error initially, the installation >makes it passed CD-ROM check and then when attempting to save files to disk at >approximately 24% (every time), the installer crashes. > >I have observed this in VM installs and local OS attempts using 9.0.1 non-free >firmware MATE versions. About to try it with Gnome (standard). All instances >use the full DVD image ~ 2.2Gb. Then you're most likely seeing a very different error, I'm afraid. If you switch to VT4 (Ctrl-Alt-F4), what error(s) do you see in the syslog? -- Steve McIntyre, Cambridge, UK.st...@einval.com "Yes, of course duct tape works in a near-vacuum. Duct tape works anywhere. Duct tape is magic and should be worshipped." -― Andy Weir, "The Martian"
Bug#865806: gnome-dictionary FTBFS: gdict-client-context.h:84:1: error: unknown type name 'GdictContext'
Control: tags -1 + patch upstream fixed-upstream On Sun, Jun 25, 2017 at 01:09:28AM +0300, Adrian Bunk wrote: > ... > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdict -I../libgdict > -DG_LOG_DOMAIN=\"Gdict\" -DDATADIR=\"/usr/share\" > -DLIBDIR=\"/usr/lib/i386-linux-gnu\" -DSYSCONFDIR=\"/etc\" -DPREFIX=\"/usr\" > -DGNOMELOCALEDIR=\"/usr/share/locale\" > -DGDICTSOURCESDIR=\"/usr/share/gdict-1.0/sources\" -DGDICT_ENABLE_INTERNALS=1 > -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -UGTK_DISABLE_DEPRECATED > -DPANGO_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES > -DGTK_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include > /glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DG_DISABLE_CAST_CHECKS > -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c > gdict-enum-types.c -fPIC -DPIC -o .libs/libgdict_1_0_la-gdict-enum-types.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdict -I../libgdict > -DG_LOG_DOMAIN=\"Gdict\" -DDATADIR=\"/usr/share\" > -DLIBDIR=\"/usr/lib/i386-linux-gnu\" -DSYSCONFDIR=\"/etc\" -DPREFIX=\"/usr\" > -DGNOMELOCALEDIR=\"/usr/share/locale\" > -DGDICTSOURCESDIR=\"/usr/share/gdict-1.0/sources\" -DGDICT_ENABLE_INTERNALS=1 > -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -UGTK_DISABLE_DEPRECATED > -DPANGO_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES > -DGTK_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include > /glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DG_DISABLE_CAST_CHECKS > -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c > gdict-utils.c -fPIC -DPIC -o .libs/libgdict_1_0_la-gdict-utils.o > In file included from gdict-enum-types.c:6:0: > ./gdict-client-context.h:84:1: error: unknown type name 'GdictContext' > GdictContext *gdict_client_context_new (const gchar > *hostname, > ^~~~ libgdict/gdict-enum-types.c has been rearranged so maybe this is caused by glib-mkenums generating this file in a different order. This is fixed in version 3.24.0 with commit https://git.gnome.org/browse/gnome-dictionary/commit/?id=d529e2dd056f05cb1115c2f68bb6f773b4b14948 commit d529e2dd056f05cb1115c2f68bb6f773b4b14948 Author: Emmanuele Bassi Date: Sun Mar 5 14:38:07 2017 + Include the right header in GdictClientContext GdictClientContext implements GdictContext, and since the header for the former references the latter, we need to include the correct header instead of a generic 'glib-object.h' one. diff --git a/libgdict/gdict-client-context.h b/libgdict/gdict-client-context.h index 9952434..d68b729 100644 --- a/libgdict/gdict-client-context.h +++ b/libgdict/gdict-client-context.h @@ -19,7 +19,7 @@ #ifndef __GDICT_CLIENT_CONTEXT_H__ #define __GDICT_CLIENT_CONTEXT_H__ -#include +#include "gdict-context.h" #define GDICT_TYPE_CLIENT_CONTEXT (gdict_client_context_get_type ()) #define GDICT_CLIENT_CONTEXT(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), GDICT_TYPE_CLIENT_CONTEXT, GdictClientContext))
Processed: Re: Bug#865806: gnome-dictionary FTBFS: gdict-client-context.h:84:1: error: unknown type name 'GdictContext'
Processing control commands: > tags -1 + patch upstream fixed-upstream Bug #865806 [src:gnome-dictionary] gnome-dictionary FTBFS: gdict-client-context.h:84:1: error: unknown type name 'GdictContext' Added tag(s) fixed-upstream, patch, and upstream. -- 865806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#824577: nautilus-actions: Uses deprecated libunique3
filemanager-actions doesn't use libunique3 either now. https://git.gnome.org/browse/filemanager-actions Thanks, Jeremy Bicha
Processed: Re: nautilus-actions: Uses deprecated libunique3
Processing control commands: > severity -1 serious Bug #844376 [src:caja-actions] caja-actions: Uses deprecated libunique3 Severity set to 'serious' from 'important' > tags -1 +sid +buster Bug #844376 [src:caja-actions] caja-actions: Uses deprecated libunique3 Added tag(s) sid. Bug #844376 [src:caja-actions] caja-actions: Uses deprecated libunique3 Added tag(s) buster. -- 844376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: nautilus-actions: Uses deprecated libunique3
Processing control commands: > severity -1 serious Bug #824577 [src:nautilus-actions] nautilus-actions: Uses deprecated libunique3 Severity set to 'serious' from 'important' > tags -1 +sid +buster Bug #824577 [src:nautilus-actions] nautilus-actions: Uses deprecated libunique3 Added tag(s) sid. Bug #824577 [src:nautilus-actions] nautilus-actions: Uses deprecated libunique3 Added tag(s) buster. -- 824577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: iok: Uses deprecated libunique3
Processing control commands: > severity -1 serious Bug #824579 [src:iok] iok: Uses deprecated libunique3 Severity set to 'serious' from 'important' > tags -1 +sid +buster Bug #824579 [src:iok] iok: Uses deprecated libunique3 Added tag(s) sid. Bug #824579 [src:iok] iok: Uses deprecated libunique3 Added tag(s) buster. -- 824579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866855: marked as done (libgettext-commons-java FTBFS: Gettext Commons build failure)
Your message dated Sun, 02 Jul 2017 17:06:29 + with message-id and subject line Bug#866855: fixed in maven-assembly-plugin 2.4.1-3 has caused the Debian Bug report #866855, regarding libgettext-commons-java FTBFS: Gettext Commons build failure 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.) -- 866855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgettext-commons-java Version: 0.9.6-3 Severity: serious Tags: buster sid Some recent change in unstable makes libgettext-commons-java FTBFS: https://tests.reproducible-builds.org/debian/history/libgettext-commons-java.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgettext-commons-java.html ... [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mBuilding Gettext Commons 0.9.6[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:2.6:resources[m [1m(default-resources)[m @ [36mgettext-commons[0;1m ---[m [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent! [[1;34mINFO[m] skip non existing resourceDirectory /build/1st/libgettext-commons-java-0.9.6/src/conf [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.2:compile[m [1m(default-compile)[m @ [36mgettext-commons[0;1m ---[m [[1;33mWARNING[m] The POM for org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [[1;33mWARNING[m] The POM for org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [[1;34mINFO[m] Changes detected - recompiling the module! [[1;33mWARNING[m] File encoding has not been set, using platform encoding ANSI_X3.4-1968, i.e. build is platform dependent! [[1;34mINFO[m] Compiling 7 source files to /build/1st/libgettext-commons-java-0.9.6/target/classes [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:2.6:testResources[m [1m(default-testResources)[m @ [36mgettext-commons[0;1m ---[m [[1;34mINFO[m] Not copying test resources [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.2:testCompile[m [1m(default-testCompile)[m @ [36mgettext-commons[0;1m ---[m [[1;34mINFO[m] Not compiling test sources [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-surefire-plugin:2.17:test[m [1m(default-test)[m @ [36mgettext-commons[0;1m ---[m [[1;34mINFO[m] Tests are skipped. [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-jar-plugin:2.4:jar[m [1m(default-jar)[m @ [36mgettext-commons[0;1m ---[m [[1;34mINFO[m] Building jar: /build/1st/libgettext-commons-java-0.9.6/target/gettext-commons-0.9.6.jar [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-assembly-plugin:2.4.1:attached[m [1m(make-assembly)[m @ [36mgettext-commons[0;1m ---[m [[1;34mINFO[m] Reading assembly descriptor: src/assembly/bin.xml [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1;31mBUILD FAILURE[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] Total time: 5.092 s [[1;34mINFO[m] Finished at: 2017-07-01T20:03:48-12:00 [[1;34mINFO[m] Final Memory: 20M/594M [[1;34mINFO[m] [1m[m [[1;31mERROR[m] Failed to execute goal [32morg.apache.maven.plugins:maven-assembly-plugin:2.4.1:attached[m [1m(make-assembly)[m on project [36mgettext-commons[m: [1;31mExecution make-assembly of goal org.apache.maven.plugins:maven-assembly-plugin:2.4.1:attached failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin:2.4.1:attached: java.lang.NoSuchMethodError: org.codehaus.plexus.interpolation.object.FieldBasedObjectInterpolator.interpolate(Ljava/lang/Object;Lorg/codehaus/plexus/interpolation/Interpolator;Lorg/codehaus/plexus/interpolation/RecursionInterceptor;)V[m [[1;31mERROR[m] [1;31m-[m [[1;31mERROR[m] [1;31mrealm = plugin>org.apache.maven.plugins:maven-assembly-plugin:2.4.1[m [[1;31mERROR[m] [1;31
Bug#865936: gnome-chess FTBFS: error: conflicting types for 'clock_type_changed_cb'
Control: forwarded -1 https://bugzilla.gnome.org/780452 Control: tags -1 + patch upstream fixed-upstream On Mon, Jun 26, 2017 at 02:51:45AM +0300, Adrian Bunk wrote: > Some recent change in unstable makes gnome-chess FTBFS: > > https://tests.reproducible-builds.org/debian/history/gnome-chess.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-chess.html > > ... > gnome-chess.c: In function 'chess_application_set_clock_type': > gnome-chess.c:6522:18: error: conflicting types for 'clock_type_changed_cb' > G_MODULE_EXPORT clock_type_changed_cb (_tmp18_, self); > ^ This is fixed upstream in version 3.24.1 with commit https://git.gnome.org/browse/gnome-chess/commit/?id=21b0df6.
Processed: Re: Bug#865936: gnome-chess FTBFS: error: conflicting types for 'clock_type_changed_cb'
Processing control commands: > forwarded -1 https://bugzilla.gnome.org/780452 Bug #865936 [src:gnome-chess] gnome-chess FTBFS: error: conflicting types for 'clock_type_changed_cb' Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/780452'. > tags -1 + patch upstream fixed-upstream Bug #865936 [src:gnome-chess] gnome-chess FTBFS: error: conflicting types for 'clock_type_changed_cb' Added tag(s) upstream, patch, and fixed-upstream. -- 865936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866855: libgettext-commons-java FTBFS: Gettext Commons build failure
On Sun, Jul 02, 2017 at 11:36:31AM +0300, Adrian Bunk wrote: > Source: libgettext-commons-java > Version: 0.9.6-3 > Severity: serious > Tags: buster sid > > Some recent change in unstable makes libgettext-commons-java FTBFS: > > https://tests.reproducible-builds.org/debian/history/libgettext-commons-java.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgettext-commons-java.html Hi Adrian, Thank you for this bug report. This problem and several other recent FTBFS issues you have identified appear to stem from an API change in a recent upload of plexus-interpolation [1]. The differences between 1.21 and 1.24, as generated with japi-compliance-checker, can be seen in [2]. All of these build failures have libmaven-assembly-plugin-java in common, and after a rebuild of libmaven-assembly-plugin-java against the newer libplexus-interpolation-java, I'm able to build libgettext-commons-java locally. Therefore, I'm going to reassign this bug and hopefully address it with an upload of maven-assembly. Thanks, tony [1] https://tracker.debian.org/news/848441 [2] https://people.debian.org/~tmancill/plexus-interpolation_1.21_to_1.24_compat_report.html signature.asc Description: PGP signature
Processed: reassign 866855 to libmaven-assembly-plugin-java
Processing commands for cont...@bugs.debian.org: > reassign 866855 libmaven-assembly-plugin-java 2.4.1-2 Bug #866855 [src:libgettext-commons-java] libgettext-commons-java FTBFS: Gettext Commons build failure Bug reassigned from package 'src:libgettext-commons-java' to 'libmaven-assembly-plugin-java'. No longer marked as found in versions libgettext-commons-java/0.9.6-3. Ignoring request to alter fixed versions of bug #866855 to the same values previously set Bug #866855 [libmaven-assembly-plugin-java] libgettext-commons-java FTBFS: Gettext Commons build failure Marked as found in versions maven-assembly-plugin/2.4.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 866855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862804: marked as done (aubio: fails to build when multiple python 3 versions are supported)
Your message dated Sun, 02 Jul 2017 16:34:42 +
with message-id
and subject line Bug#862804: fixed in aubio 0.4.3-4.1
has caused the Debian Bug report #862804,
regarding aubio: fails to build when multiple python 3 versions are supported
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.)
--
862804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aubio
Severity: normal
Tags: patch
User: debian-pyt...@lists.debian.org
Usertags: python3.6
Dear Maintainer,
Aubio fails to build when mutiple Python versions are supported, as is now the
case in Ubuntu. There are two problems: one is that the build-depends are kind
of silly and the other is that debian/rules always runs the tests with the
default version of Python 3, even when it should be testing a non-default one.
I'm attaching the patch I've applied in Ubuntu.
Cheers,
mwh
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-75-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru aubio-0.4.3/debian/changelog aubio-0.4.3/debian/changelog
--- aubio-0.4.3/debian/changelog 2017-05-15 14:47:30.0 +1200
+++ aubio-0.4.3/debian/changelog 2017-05-15 16:24:56.0 +1200
@@ -1,3 +1,15 @@
+aubio (0.4.3-4ubuntu4) artful; urgency=medium
+
+ * Fix d/rules to invoke tests with correct version of Python 3.
+
+ -- Michael Hudson-Doyle Mon, 15 May 2017 16:23:18 +1200
+
+aubio (0.4.3-4ubuntu3) artful; urgency=medium
+
+ * Remove python-related alternates from Build-Depends.
+
+ -- Michael Hudson-Doyle Mon, 15 May 2017 15:24:09 +1200
+
aubio (0.4.3-4ubuntu2) artful; urgency=medium
* No change rebuild to add Python 3.6 support.
diff -Nru aubio-0.4.3/debian/control aubio-0.4.3/debian/control
--- aubio-0.4.3/debian/control 2017-05-12 21:24:12.0 +1200
+++ aubio-0.4.3/debian/control 2017-05-15 15:24:45.0 +1200
@@ -15,11 +15,11 @@
libasound2-dev,
libfftw3-dev,
dh-python,
- python-all-dev | python-dev | python | python-all,
+ python-all-dev,
python-setuptools,
libpython2.7-dev,
python-numpy,
- python3-all-dev | python3-dev | python3 | python3-all,
+ python3-all-dev,
python3-setuptools,
libpython3-dev,
python3-numpy,
diff -Nru aubio-0.4.3/debian/rules aubio-0.4.3/debian/rules
--- aubio-0.4.3/debian/rules 2016-11-28 10:13:53.0 +1300
+++ aubio-0.4.3/debian/rules 2017-05-15 16:05:33.0 +1200
@@ -18,7 +18,7 @@
export PYBUILD_BEFORE_TEST=make create_test_sounds; cp -prv '{dir}/python/tests' '{build_dir}'
export PYBUILD_AFTER_TEST=rm -rf '{build_dir}/tests'; rm -rf '{dir}/python/tests/sounds'
export PYBUILD_TEST_ARGS_python2=cd '{build_dir}'; nose2-2.7 --verbose
-export PYBUILD_TEST_ARGS_python3=cd '{build_dir}'; nose2-3 --verbose
+export PYBUILD_TEST_ARGS_python3=cd '{build_dir}'; python{version} `which nose2-3` --verbose
%:
dh $@ --with python2,python3 --buildsystem=pybuild
--- End Message ---
--- Begin Message ---
Source: aubio
Source-Version: 0.4.3-4.1
We believe that the bug you reported is fixed in the latest version of
aubio, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 862...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dr. Tobias Quathamer (supplier of updated aubio 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, 02 Jul 2017 17:35:53 +0200
Source: aubio
Binary: libaubio-dev libaubio5 aubio-tools libaubio-doc python-aubio
python3-aubio
Architecture: all amd64 source
Version: 0.4.3-4.1
Distribution: unstable
Urgency: medium
Maintainer: Paul Brossier
Changed-By: Dr. Tobias Quathamer
Bug#866898: xorg: switching to a VT (with Ctrl-Alt-Fx) hangs entire system
Package: xorg Version: 1:7.7+19 Severity: serious Hi, Since upgrading to stretch, I can no longer switch to a VT - if I do Ctrl-Alt-F1 the mouse pointer briefly changes back to that of gdm3 (I think), then the entire machine locks up solid - unresponsive to ping or anything, and I have to power-cycle it. The only thing I see in the log at about the relevant time is: Jul 1 23:25:54 aragorn kernel: [ 164.494985] gnome-session-f[4309]: segfault at 0 ip b71c492d sp bf8128c4 error 4 in libgtk-3.so.0.2200.11[b6ee7000+803000] Jul 1 23:25:54 aragorn kernel: [ 164.497200] gnome-session-f[4318]: segfault at 0 ip b721a92d sp bfafd844 error 4 in libgtk-3.so.0.2200.11[b6f3d000+803000] ...and, when it happened again: Jul 1 23:57:54 aragorn kernel: [ 444.296161] traps: gnome-shell[4178] trap int3 ip:b62e8e40 sp:bfb24fb0 error:0 Jul 1 23:57:54 aragorn kernel: [ 444.296168] in libglib-2.0.so.0.5000.3[b629c000+12a000] For me, at least, this is entirely reproducible, and makes it impossible for me to use my virtual consoles any more (which I use, e.g. for root sessions) :( The manual x.org.conf is carried from previous releases - I still have a CRT, so need to tell Xorg about the monitor. Thanks, Matthew -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Mar 12 2011 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Mar 3 14:41 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300] [1002:5b60] Xorg X server configuration file status: -rw-r--r-- 1 root root 2148 Feb 28 2015 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- #Hopefully-minimal xorg.conf to cover things that X doesn't get right itself #use Xorg -configure to make new /root/xorg.conf.new which tells you what #it auto-detected #This should match the sleep and power buttons, and tell X to ignore them Section "InputClass" Identifier "Deathbuttons" MatchProduct "Power|Sleep" Option "Ignore" "true" EndSection #Hopefully match my PS/2 mouse and put emulate3buttons on Section "InputClass" Identifier "2 button mice" MatchProduct "PS/2" MatchIsPointer "on" Option "Emulate3Buttons" "true" Option "Emulate3Timeout" "25" #ms EndSection #Extracted from the auto-probe (you need a "Device" section to put into the Display section below) Section "Device" Identifier "Card0" Driver "radeon" BusID "PCI:1:0:0" EndSection #This bit done by hand Section "Monitor" Identifier "HP A4576A" #HorizSync 30-197 HorizSync 30-107 VertRefresh 50-160 #this taken from cvt 1600 1200 75 then reducing the 3rd and 4th numbers by 30 to move the LHS #of the display onto the screen ModeLine "1600x1200" 204.75 1600 1690 1858 2176 1200 1203 1207 1255 -hsync +vsync EndSection Section "Screen" Identifier "Screen0" Device "Card0" # Monitor"Monitor0" Monitor"HP A4576A" SubSection "Display" Viewport 0 0 Depth 1 Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 4 Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 8 Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 15 Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 24 Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Contents of /etc/X11/xorg.conf.d: - total 0 KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.9.0-3-686-pae (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) Xorg X server log files on system: ---
Bug#862804: NMU for aubio
Hi,
I've just uploaded an NMU for aubio, fixing this RC bug. Please find the
patch attached.
Regards,
Tobias
diff --git a/debian/changelog b/debian/changelog
index 2fdef26..f8d92ea 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+aubio (0.4.3-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove python-related alternates from Build-Depends.
+ * Fix d/rules to invoke tests with correct version of Python 3.
+Thanks to Michael Hudson-Doyle for
+the bug report and patch. Closes: #862804
+
+ -- Dr. Tobias Quathamer Sun, 02 Jul 2017 17:35:53 +0200
+
aubio (0.4.3-4) unstable; urgency=medium
* debian/control: aubio-tools now depends on python3-aubio
diff --git a/debian/control b/debian/control
index 0c17d37..4c0fca3 100644
--- a/debian/control
+++ b/debian/control
@@ -14,11 +14,11 @@ Build-Depends: debhelper (>= 9.0.0),
libasound2-dev,
libfftw3-dev,
dh-python,
- python | python-all | python-dev | python-all-dev,
+ python-all-dev,
python-setuptools,
libpython2.7-dev,
python-numpy,
- python3 | python3-all | python3-dev | python3-all-dev,
+ python3-all-dev,
python3-setuptools,
libpython3-dev,
python3-numpy,
diff --git a/debian/rules b/debian/rules
index 67b525c..4f2ff4d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -18,7 +18,7 @@ export PYBUILD_AFTER_INSTALL_python3=mv '{destdir}/usr/bin/aubiocut' '{dir}/debi
export PYBUILD_BEFORE_TEST=make create_test_sounds; cp -prv '{dir}/python/tests' '{build_dir}'
export PYBUILD_AFTER_TEST=rm -rf '{build_dir}/tests'; rm -rf '{dir}/python/tests/sounds'
export PYBUILD_TEST_ARGS_python2=cd '{build_dir}'; nose2-2.7 --verbose
-export PYBUILD_TEST_ARGS_python3=cd '{build_dir}'; nose2-3 --verbose
+export PYBUILD_TEST_ARGS_python3=cd '{build_dir}'; python{version} `which nose2-3` --verbose
%:
dh $@ --with python2,python3 --buildsystem=pybuild
signature.asc
Description: OpenPGP digital signature
Bug#858643: marked as done (desktop-base: File not found in the post-inst script)
Your message dated Sun, 02 Jul 2017 15:04:48 + with message-id and subject line Bug#858643: fixed in desktop-base 9.0.5 has caused the Debian Bug report #858643, regarding desktop-base: File not found in the post-inst script 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.) -- 858643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: desktop-base Version: 9.0.3 Severity: normal Tags: patch Dear Maintainer, Updating desktop-base complains that this file /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg does not exist. I did not find it with apt-file so I just edited /var/lib/dpkg/info/gconf2.postinst line 41 and changed svg into png. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/3 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages desktop-base depends on: ii dpkg 1.18.23 ii librsvg2-common 2.40.16-1+b1 desktop-base recommends no packages. Versions of packages desktop-base suggests: ii kde-standard 5:92 ii wmaker0.95.7-8 ii xfce4 4.12.3 -- no debconf information --- End Message --- --- Begin Message --- Source: desktop-base Source-Version: 9.0.5 We believe that the bug you reported is fixed in the latest version of desktop-base, 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 858...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated desktop-base 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, 02 Jul 2017 10:24:37 +0200 Source: desktop-base Binary: desktop-base Architecture: source all Version: 9.0.5 Distribution: unstable Urgency: medium Maintainer: Gustavo Franco Changed-By: Aurélien COUDERC Description: desktop-base - common files for the Debian Desktop Closes: 858643 Changes: desktop-base (9.0.5) unstable; urgency=medium . * Ensure postinst doesn’t fails on upgrade even when an incomplete theme pack is active. (Closes: #858643) * Various check-all-the-things fixes. Checksums-Sha1: ef85dc56d616d1f407cbbabf50ef4bf382a28f28 1995 desktop-base_9.0.5.dsc c40f650698aef09150510f161f3b19c8b427c450 2301444 desktop-base_9.0.5.tar.xz 4161adfeafd9f8f43f1cd3a19d54b492565a7602 3506998 desktop-base_9.0.5_all.deb 4e5f08fd233a48edbda5dcc0260c0ef1e732bde6 8802 desktop-base_9.0.5_amd64.buildinfo Checksums-Sha256: 4f3af565c63bbc59f3e879f5061348d390944d62b82dcf2caf6f75b555ed6b88 1995 desktop-base_9.0.5.dsc bfa03e8783bc73617d147d8ee737cf3f8401c18d2bf31a683c7a7efef0733226 2301444 desktop-base_9.0.5.tar.xz 5591b28855116c9093535eb6754953cb31265978835214d9a4e01a456497d1f3 3506998 desktop-base_9.0.5_all.deb 61bf315cc4c92080242c21c1852161cd29351d0971d5ada2984c7d4c4f7fe74a 8802 desktop-base_9.0.5_amd64.buildinfo Files: cb6bd051cd0242074d4c59a178570b72 1995 x11 optional desktop-base_9.0.5.dsc ecd16e5c74b9ece2dd6f08a586749bb8 2301444 x11 optional desktop-base_9.0.5.tar.xz 3030e17ce9e25d7dec34f19a85101338 3506998 x11 optional desktop-base_9.0.5_all.deb 37bb5099bc4861800cd9bb770794c280 8802 x11 optional desktop-base_9.0.5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAllYtdcRHHplY291Y291 QGZyZWUuZnIACgkQcaflM/KRoyRBTA//QHP/HJbLQZsX6FmlYVyhNFbIunQtEvKE 08hRGtDttPtOj96+xLPYcpkCKCqPKFQV95uSJmD/G4VtajewBiWX15rmqXY/Qaie VYZV9QdrogFx5sKiqyuQ1mD6Uyx+gGtiNwa6qcbfPPdUmsvfy3HSOrwgSz0BxDtg BMi6mbsItFN0ABXbRR193wRJFtpAH9CRPCDjQKd85kRa/fJRGv7/BTiHZDkAWOBz OiFU8NCBArKXrL3mUbnyzjbsjiCv84syxxOAzV4GFhf8ovokC0xZA4relve7n8qx JrtePwpU+2XqgixcoSBYYTzKlDJBP7Zzn1EKM+6bqDf0jqHbbb1XsjRUbtT52hr3 Fuko4SByT/cwwi6Vsh6PvkFhu6hsjy1buf2iMD/Kk5TkSYluIObVHyXwoNQ2BI19 YSvhE5iEE4k9aDWowumw4qranwWWdAdzpWrDHD+igMs2xJ0qMl3B2xTOqOuvrW4V cZiTkPT+0AHgDynibceheYsnJnewPGOjkU9VthWtNzNSslQAhsArqRijsN6xS1W0 EybFal0n+h5OibRCM6IM+2WHMpRhJnbJquVLhcbIKLlSEIl1TE923o99MQOCHooE +DIFkWmElGbFlWp
Bug#866532: inkscape: Fails to start because of libgsl.so.0 can't be found
Control: tag -1 moreinfo unreproducible On Fri, Jun 30, 2017 at 12:33:44AM +0200, greggy wrote: > Inkscape fails to start with the following error message: > > $ inkscape > inkscape: error while loading shared libraries: libgsl.so.0: cannot open > shared object file: No such file or directory > > The problem appeared after I upgraded my system from jessie to stretch. Of course I can't reproduce it… I given how widespread inkscape is and you're the only one reporting it makes me believe there is something wrong on your side. For example, are you sure you are running the binary coming from the Debian archive? Our inkscape should be built against libgsl.so.19, not libgsl.so.0 as your error message reports. It makes me believe you somehow have the binary coming from jessie, which was built against libgsl.so.0 indeed. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: Re: Bug#866532: inkscape: Fails to start because of libgsl.so.0 can't be found
Processing control commands: > tag -1 moreinfo unreproducible Bug #866532 [inkscape] inkscape: Fails to start because of libgsl.so.0 can't be found Added tag(s) unreproducible and moreinfo. -- 866532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866378: 3dchess: 100 % CPU consumption
Am 02.07.2017 um 16:26 schrieb Boyuan Yang: > [cc me please, thanks] > > Hello all, > > Now that bug #866378 is fixed in unstable (and soon in testing), is it > possible > for anyone to make a stable update and have this RC bug fixed in Debian 9? I > would like to see a 3dchess/0.8.1-19+deb9u1 in Debian Stretch. > > The patch seems simple and likely to be accepted by Stable Release Managers. > Any idea? Hi, I will prepare a point update for Jessie and Stretch. Just out of curiosity, how did you notice this bug? Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#866738: marked as done (vlc-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/cvlc)
Your message dated Sun, 2 Jul 2017 16:30:21 +0200 with message-id <8e00a4e3-7498-50e8-25ac-348b48c70...@debian.org> and subject line Re: Bug#866738: vlc-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/cvlc has caused the Debian Bug report #866738, regarding vlc-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/cvlc 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.) -- 866738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vlc-bin Version: 2.2.6-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + kmplayer Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' 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/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package vlc-bin. Preparing to unpack .../vlc-bin_2.2.6-2_amd64.deb ... Unpacking vlc-bin (2.2.6-2) ... dpkg: error processing archive /var/cache/apt/archives/vlc-bin_2.2.6-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/cvlc', which is also in package vlc-nox 2.2.5-1~deb8u1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas kmplayer_1:0.12.0b-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- On 2017-07-02 16:21, Sebastian Ramacher wrote: > No, the provided log installs jessie and then directly upgrades to buster/sid > and skips stretch. This isn't a supported upgrade path. Oops, my fault. That should have been an upgrade from stretch to sid, skipping buster. Andreas--- End Message ---
Bug#866378: 3dchess: 100 % CPU consumption
[cc me please, thanks] Hello all, Now that bug #866378 is fixed in unstable (and soon in testing), is it possible for anyone to make a stable update and have this RC bug fixed in Debian 9? I would like to see a 3dchess/0.8.1-19+deb9u1 in Debian Stretch. The patch seems simple and likely to be accepted by Stable Release Managers. Any idea? Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#866738: vlc-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/cvlc
Processing control commands: > tags -1 + moreinfo Bug #866738 [vlc-bin] vlc-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/cvlc Added tag(s) moreinfo. -- 866738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866738: vlc-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/cvlc
Control: tags -1 + moreinfo On 2017-07-01 13:23:16, Andreas Beckmann wrote: > Package: vlc-bin > Version: 2.2.6-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + kmplayer > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'stretch'. > It installed fine in 'stretch', then the upgrade to 'buster' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. No, the provided log installs jessie and then directly upgrades to buster/sid and skips stretch. This isn't a supported upgrade path. Did you attach an incorrect log? Cheers > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces > > >From the attached log (scroll to the bottom...): > > Selecting previously unselected package vlc-bin. > Preparing to unpack .../vlc-bin_2.2.6-2_amd64.deb ... > Unpacking vlc-bin (2.2.6-2) ... > dpkg: error processing archive > /var/cache/apt/archives/vlc-bin_2.2.6-2_amd64.deb (--unpack): >trying to overwrite '/usr/bin/cvlc', which is also in package vlc-nox > 2.2.5-1~deb8u1 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > > > cheers, > > Andreas > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: bumping severity
Processing commands for cont...@bugs.debian.org: > reassign 866629 live-installer Bug #866629 [debian-installer] debian-installer: Installer showes Debootstrap Error debian stretch live installation Bug reassigned from package 'debian-installer' to 'live-installer'. No longer marked as found in versions debian-installer/20170615. Ignoring request to alter fixed versions of bug #866629 to the same values previously set > severity 866629 grave Bug #866629 [live-installer] debian-installer: Installer showes Debootstrap Error debian stretch live installation Severity set to 'grave' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 866629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > severity 864365 serious Bug #864365 [python3-numba] A simple program ends up with SIGSEGV [amd64] Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 864365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866883: Matplotlib does not work with Python 3.6
Package: python3-matplotlib Version: 2.0.0+dfsg1-2 Severity: serious Affects: python3-astropy Dear maintainer, the matplotlib package does not work well with the upcoming Python 3.6: $ python3.6 Python 3.6.2rc1 (default, Jun 20 2017, 12:51:36) [GCC 6.3.0 20170516] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from matplotlib import pyplot Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 29, in import matplotlib.colorbar File "/usr/lib/python3/dist-packages/matplotlib/colorbar.py", line 32, in import matplotlib.artist as martist File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 15, in from .transforms import (Bbox, IdentityTransform, TransformedBbox, File "/usr/lib/python3/dist-packages/matplotlib/transforms.py", line 39, in from matplotlib._path import (affine_transform, count_bboxes_overlapping_bbox, ModuleNotFoundError: No module named 'matplotlib._path' This affects the upload of new packages for Python-astropy (and probably other python3 packages), since the built time tests fail.
Processed: found 782155 in 2.02-1, found 782156 in 2.02-1, tagging 866551, affects 832128
Processing commands for cont...@bugs.debian.org:
> found 782155 2.02-1
Bug #782155 [grub-pc] grub-pc: unowned files after purge (policy 6.8, 10.8):
/boot/grub/unicode.pf2
Marked as found in versions grub2/2.02-1.
> found 782156 2.02-1
Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8):
/boot/grub/{locale, x86_64-xen}/* and some more
Marked as found in versions grub2/2.02-1.
> tags 866551 + sid buster
Bug #866551 [src:translate-toolkit] translate-toolkit: ftbfs when multiple
python 3 versions are supported
Added tag(s) buster and sid.
> affects 832128 + freespace2-launcher-wxlauncher
Bug #832128 [freespace2] freespace2: Bad symlinks /usr/games/fs2_open{,_DEBUG}
Added indication that 832128 affects freespace2-launcher-wxlauncher
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
782155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782155
782156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156
832128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832128
866551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: block 866797 with 866723
Processing commands for cont...@bugs.debian.org: > block 866797 with 866723 Bug #866797 [release.debian.org] transition: gdal 866797 was not blocked by any bugs. 866797 was not blocking any bugs. Added blocking bug(s) of 866797: 866723 > thanks Stopping processing here. Please contact me if you need assistance. -- 866797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866877: diaspora: fails on being triggered
Package: diaspora Version: 0.6.0.1+debian-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed when triggered. >From the attached log (scroll to the bottom...): Processing triggers for libc-bin (2.24-12) ... Processing triggers for diaspora (0.6.0.1+debian-1) ... /var/lib/dpkg/info/diaspora.postinst: 38: /var/lib/dpkg/info/diaspora.postinst: -e: not found postinst called with unknown argument `triggered' dpkg: error processing package diaspora (--configure): subprocess installed post-installation script returned error exit status 1 cheers, Andreas diaspora_0.6.0.1+debian-1.log.gz Description: application/gzip
Bug#866870: marked as done (ruby-rspec-puppet FTBFS: test failures)
Your message dated Sun, 02 Jul 2017 12:21:46 +
with message-id
and subject line Bug#866870: fixed in ruby-rspec-puppet 2.6.1-1
has caused the Debian Bug report #866870,
regarding ruby-rspec-puppet FTBFS: test failures
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.)
--
866870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-puppet
Version: 2.4.0-1
Severity: serious
Some recent change in unstable makes ruby-rspec-puppet FTBFS:
https://tests.reproducible-builds.org/debian/history/ruby-rspec-puppet.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rspec-puppet.html
...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/build/1st/ruby-rspec-puppet-2.4.0/debian/ruby-rspec-puppet/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-rspec-puppet/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
...FF.
Total resources: 62
Touched resources: 34
Resource coverage: 54.84%
Untouched resources:
Class[Cycle::Bad]
Class[Cycle::Good]
Class[Export_resource]
Class[Relationships::Before]
Class[Relationships::Notify]
Class[Test::Classes_used]
Class[Test::Compile_error]
Class[Test::Hiera]
File[/tmp/deptest1]
File[/tmp/deptest2]
File[/tmp]
File[tmpdir]
Node[__node_regexp__testhost]
Node[bad_dep_host]
Node[default]
Node[facts.acme.com]
Node[good_dep_host]
Node[testhost_a]
Notify[["first", "second", ["third", "fourth"], 5, 6]]
Notify[["first", 1, "second", 2]]
Notify[["foo", "bar", "baz", "quux"]]
Notify[message-test define]
Notify[middle]
Notify[{"first"=>1, "second"=>2, "third"=>{"alpha"=>"a", "beta"=>"b"}}]
Notify[{"first"=>1, "second"=>2}]
Notify[{"foo"=>"bar", "baz"=>"quux"}]
Notify[{1=>"uno", 2=>"dos"}]
User[foo]
Failures:
1) split should run split("foo") and raise an ArgumentError with the message
matching /mis-matched arguments/
Failure/Error: it { should
run.with_params('foo').and_raise_error(expected_error, expected_error_message) }
expected split("foo") to have raised ArgumentError matching /mis-matched
arguments/ instead of ArgumentError('split' expects 2 arguments, got 1)
# ./spec/functions/split_spec.rb:23:in `block (2 levels) in '
2) split should run split("foo") and raise an Exception with the message
matching /mis-matched arguments/
Failure/Error: it { should
run.with_params('foo').and_raise_error(expected_error_message) }
expected split("foo") to have raised Exception matching /mis-matched
arguments/ instead of ArgumentError('split' expects 2 arguments, got 1)
# ./spec/functions/split_spec.rb:25:in `block (2 levels) in '
Finished in 10.46 seconds (files took 2.25 seconds to load)
1030 examples, 2 failures
Failed examples:
rspec ./spec/functions/split_spec.rb:23 # split should run split("foo") and
raise an ArgumentError with the message matching /mis-matched arguments/
rspec ./spec/functions/split_spec.rb:25 # split should run split("foo") and
raise an Exception with the message matching /mis-matched arguments/
/usr/bin/ruby2.3 /usr
Bug#866870: marked as pending
tag 866870 pending thanks Hello, Bug #866870 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-rspec-puppet.git/commit/?id=7097f0f --- commit 7097f0f41c46ee17016c34d739aee363b8d17242 Author: Sebastien Badia Date: Sun Jul 2 13:49:18 2017 +0200 Prepare Debian changelog diff --git a/debian/changelog b/debian/changelog index 8570b7a..0e20e77 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,16 @@ +ruby-rspec-puppet (2.6.1-1) unstable; urgency=medium + + * Team upload. + * New upstream version 2.6.1 (Closes: #866870) + * d/compat: Bump compat version to 10 + * d/control: ++ Update BD (puppet-common is now a meta package) ++ Bump Standard-Version to 4.0.0 (no changes needed) ++ Added testsuite to autopkgtest-pkg-ruby (debci) + * d/rules: Enable dependencies check during tests + + -- Sebastien Badia Sun, 02 Jul 2017 13:48:49 +0200 + ruby-rspec-puppet (2.4.0-1) unstable; urgency=medium * Team upload.
Processed: Bug#866870 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 866870 pending Bug #866870 [src:ruby-rspec-puppet] ruby-rspec-puppet FTBFS: test failures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 866870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865558: marked as done (django-pipeline FTBFS with Django 1.11)
Your message dated Sun, 02 Jul 2017 11:19:09 +
with message-id
and subject line Bug#865558: fixed in django-pipeline 1.6.13-1
has caused the Debian Bug report #865558,
regarding django-pipeline FTBFS with Django 1.11
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.)
--
865558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-pipeline
Version: 1.6.8-3
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-pipeline.html
...
Copying
'/usr/lib/python3/dist-packages/django/contrib/admin/static/admin/css/dashboard.css'
Copying
'/usr/lib/python3/dist-packages/django/contrib/admin/static/admin/css/changelists.css'
Copying
'/usr/lib/python3/dist-packages/django/contrib/admin/static/admin/css/base.css'
Post-processed 'screen.css' as 'screen.css'
Post-processed 'scripts_defer.js' as 'scripts_defer.js'
Post-processed 'scripts.js' as 'scripts.js'
Post-processed 'scripts_async.js' as 'scripts_async.js'
Post-processed 'scripts_async_defer.js' as 'scripts_async_defer.js'
100 static files copied to '/build/1st/django-pipeline-1.6.8/tests/static', 5
post-processed.
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. python{version}
/usr/bin/django-admin test --settings=tests.settings" dh_auto_test
I: pybuild base:184: PYTHONPATH=. python2.7 /usr/bin/django-admin test
--settings=tests.settings
Creating test database for alias 'default'...
Traceback (most recent call last):
File "/usr/bin/django-admin", line 21, in
management.execute_from_command_line()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 363, in execute_from_command_line
utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 355, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py",
line 29, in run_from_argv
super(Command, self).run_from_argv(argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
283, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
330, in execute
output = self.handle(*args, **options)
File
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py",
line 62, in handle
failures = test_runner.run_tests(test_labels)
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 602, in
run_tests
self.run_checks()
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 562, in
run_checks
call_command('check', verbosity=self.verbosity)
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 130, in call_command
return command.execute(*args, **defaults)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
330, in execute
output = self.handle(*args, **options)
File
"/usr/lib/python2.7/dist-packages/django/core/management/commands/check.py",
line 68, in handle
fail_level=getattr(checks, options['fail_level']),
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
359, in check
include_deployment_checks=include_deployment_checks,
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
346, in _run_checks
return checks.run_checks(**kwargs)
File "/usr/lib/python2.7/dist-packages/django/core/checks/registry.py", line
81, in run_checks
new_errors = check(app_configs=app_configs)
File "/usr/lib/python2.7/dist-packages/django/core/checks/urls.py", line 16,
in check_url_config
return check_resolver(resolver)
File "/usr/lib/python2.7/dist-packages/django/core/checks/urls.py", line 26,
in check_resolver
return check_method()
File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 254,
in check
for pattern in self.url_patterns:
File "/usr/lib/python2.7/dist-packages/django/utils/functional.py", line 35,
in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 405,
in url_patterns
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/usr/lib/python2.7/dist-packages/django/utils/functional.py", line 35,
in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 398,
in urlconf_mod
Processed: Add the tags I forgot
Processing commands for cont...@bugs.debian.org: > tags 866870 buster sid Bug #866870 [src:ruby-rspec-puppet] ruby-rspec-puppet FTBFS: test failures Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 866870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866871: golang-github-gopherjs-gopherjs FTBFS: undefined: ___GOPHERJS_REQUIRES_GO_VERSION_1_7___
Source: golang-github-gopherjs-gopherjs Version: 0.0~git20170216.0.d5c6ba6-1 Severity: serious Some recent change in unstable makes golang-github-gopherjs-gopherjs FTBFS: https://tests.reproducible-builds.org/debian/history/golang-github-gopherjs-gopherjs.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-gopherjs-gopherjs.html ... dh_auto_build -O--buildsystem=golang go install -v -p 16 github.com/gopherjs/gopherjs github.com/gopherjs/gopherjs/build github.com/gopherjs/gopherjs/compiler github.com/gopherjs/gopherjs/compiler/analysis github.com/gopherjs/gopherjs/compiler/astutil github.com/gopherjs/gopherjs/compiler/filter github.com/gopherjs/gopherjs/compiler/natives github.com/gopherjs/gopherjs/compiler/natives/src/sync github.com/gopherjs/gopherjs/compiler/natives/src/text/template github.com/gopherjs/gopherjs/compiler/prelude github.com/gopherjs/gopherjs/compiler/typesutil github.com/gopherjs/gopherjs/js github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests github.com/gopherjs/gopherjs/tests/main github.com/gopherjs/gopherjs/tests/otherpkg github.com/gopherjs/gopherjs/third_party/importer golang.org/x/sys/unix github.com/gopherjs/gopherjs/compiler/astutil github.com/gopherjs/gopherjs/compiler/typesutil github.com/gopherjs/gopherjs/third_party/importer github.com/gopherjs/gopherjs/compiler/prelude github.com/neelance/astrewrite golang.org/x/tools/go/types/typeutil github.com/kardianos/osext github.com/neelance/sourcemap github.com/spf13/pflag github.com/gopherjs/gopherjs/compiler/natives/src/sync golang.org/x/crypto/ssh/terminal github.com/gopherjs/gopherjs/compiler/natives github.com/gopherjs/gopherjs/compiler/natives/src/text/template github.com/gopherjs/gopherjs/js github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests github.com/gopherjs/gopherjs/tests/main github.com/gopherjs/gopherjs/tests/otherpkg github.com/gopherjs/gopherjs/compiler/analysis github.com/gopherjs/gopherjs/compiler/filter github.com/gopherjs/gopherjs/compiler # github.com/gopherjs/gopherjs/compiler src/github.com/gopherjs/gopherjs/compiler/compiler.go:20: undefined: ___GOPHERJS_REQUIRES_GO_VERSION_1_7___ github.com/fsnotify/fsnotify github.com/spf13/cobra dh_auto_build: go install -v -p 16 github.com/gopherjs/gopherjs github.com/gopherjs/gopherjs/build github.com/gopherjs/gopherjs/compiler github.com/gopherjs/gopherjs/compiler/analysis github.com/gopherjs/gopherjs/compiler/astutil github.com/gopherjs/gopherjs/compiler/filter github.com/gopherjs/gopherjs/compiler/natives github.com/gopherjs/gopherjs/compiler/natives/src/sync github.com/gopherjs/gopherjs/compiler/natives/src/text/template github.com/gopherjs/gopherjs/compiler/prelude github.com/gopherjs/gopherjs/compiler/typesutil github.com/gopherjs/gopherjs/js github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests github.com/gopherjs/gopherjs/tests/main github.com/gopherjs/gopherjs/tests/otherpkg github.com/gopherjs/gopherjs/third_party/importer returned exit code 2 debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 2
Bug#866870: ruby-rspec-puppet FTBFS: test failures
Source: ruby-rspec-puppet
Version: 2.4.0-1
Severity: serious
Some recent change in unstable makes ruby-rspec-puppet FTBFS:
https://tests.reproducible-builds.org/debian/history/ruby-rspec-puppet.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rspec-puppet.html
...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/build/1st/ruby-rspec-puppet-2.4.0/debian/ruby-rspec-puppet/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-rspec-puppet/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
...FF.
Total resources: 62
Touched resources: 34
Resource coverage: 54.84%
Untouched resources:
Class[Cycle::Bad]
Class[Cycle::Good]
Class[Export_resource]
Class[Relationships::Before]
Class[Relationships::Notify]
Class[Test::Classes_used]
Class[Test::Compile_error]
Class[Test::Hiera]
File[/tmp/deptest1]
File[/tmp/deptest2]
File[/tmp]
File[tmpdir]
Node[__node_regexp__testhost]
Node[bad_dep_host]
Node[default]
Node[facts.acme.com]
Node[good_dep_host]
Node[testhost_a]
Notify[["first", "second", ["third", "fourth"], 5, 6]]
Notify[["first", 1, "second", 2]]
Notify[["foo", "bar", "baz", "quux"]]
Notify[message-test define]
Notify[middle]
Notify[{"first"=>1, "second"=>2, "third"=>{"alpha"=>"a", "beta"=>"b"}}]
Notify[{"first"=>1, "second"=>2}]
Notify[{"foo"=>"bar", "baz"=>"quux"}]
Notify[{1=>"uno", 2=>"dos"}]
User[foo]
Failures:
1) split should run split("foo") and raise an ArgumentError with the message
matching /mis-matched arguments/
Failure/Error: it { should
run.with_params('foo').and_raise_error(expected_error, expected_error_message) }
expected split("foo") to have raised ArgumentError matching /mis-matched
arguments/ instead of ArgumentError('split' expects 2 arguments, got 1)
# ./spec/functions/split_spec.rb:23:in `block (2 levels) in '
2) split should run split("foo") and raise an Exception with the message
matching /mis-matched arguments/
Failure/Error: it { should
run.with_params('foo').and_raise_error(expected_error_message) }
expected split("foo") to have raised Exception matching /mis-matched
arguments/ instead of ArgumentError('split' expects 2 arguments, got 1)
# ./spec/functions/split_spec.rb:25:in `block (2 levels) in '
Finished in 10.46 seconds (files took 2.25 seconds to load)
1030 examples, 2 failures
Failed examples:
rspec ./spec/functions/split_spec.rb:23 # split should run split("foo") and
raise an ArgumentError with the message matching /mis-matched arguments/
rspec ./spec/functions/split_spec.rb:25 # split should run split("foo") and
raise an Exception with the message matching /mis-matched arguments/
/usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
failed
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install
/build/1st/ruby-rspec-puppet-2.4.0/debian/ruby-rspec-puppet returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
