Bug#880426: Acknowledgement (libreoffice-sdbc-firebird: fails to upgrade jessie -> stretch -> buster)

[Andreas Beckmann]

Don't forget to bump the version in
debian/libreoffice-sdbc-firebird.maintscript
That should have been done when that file was reintroduced in 1:5.4.2-1

Please use "1:5.4.3~rc1-3~" (or whatever will be the version including
the fix plus a trailing "~").

It's always the version right before the (working) d-m-h call was added,
not the (older) version that removed/renamed/changed the
conffile/symlink/ (but ideally both versions are the same).

You can probably leave the version in
debian/libreoffice-common.maintscript alone.


Andreas

Bug#880217: ansible-tower-cli-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/ansible-tower-cli/CONFIG_CMD_OPTIONS.md.gz

[Evgeni Golov]

Hi,

On Mon, Oct 30, 2017 at 06:23:32PM +0100, Andreas Beckmann wrote:
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This should be
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

Where can I file a bug against your templates? ;)

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

I'll fix these asap, thanks!

Evgeni

Bug#880426: Acknowledgement (libreoffice-sdbc-firebird: fails to upgrade jessie -> stretch -> buster)

[Rene Engelhard]

Hi,

On Tue, Oct 31, 2017 at 02:37:53PM +0100, Andreas Beckmann wrote:
> Don't forget to bump the version in
> debian/libreoffice-sdbc-firebird.maintscript
> That should have been done when that file was reintroduced in 1:5.4.2-1

Indeed, with 1:5.2.3~rc1-1..

> Please use "1:5.4.3~rc1-3~" (or whatever will be the version including
> the fix plus a trailing "~").

sigh, ok. Changed.
(The next upload probably will be 1:5.4.3~rc2-1, though)

Regards,

Rene

Bug#880353: Pending fixes for bugs in the golang-github-gophercloud-gophercloud package

[pkg-go-maintainers]

tag 880353 + pending
thanks

Some bugs in the golang-github-gophercloud-gophercloud package are
closed in revision 4df038751447bef2303ef10edcb21daa0e404404 in branch
'master' by Shengjing Zhu

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-gophercloud-gophercloud.git/commit/?id=4df0387

Commit message:

d/control: add tzdata to Build-Depends (Closes: #880353).

Signed-off-by: Shengjing Zhu 

Processed: tagging 880426

[Debian Bug Tracking System]

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

> tags 880426 + pending
Bug #880426 [libreoffice-sdbc-firebird] libreoffice-sdbc-firebird: fails to 
upgrade jessie -> stretch -> buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Pending fixes for bugs in the golang-github-gophercloud-gophercloud package

[Debian Bug Tracking System]

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

> tag 880353 + pending
Bug #880353 [src:golang-github-gophercloud-gophercloud] 
golang-github-gophercloud-gophercloud: FTBFS: dh_auto_test: cd 
obj-x86_64-linux-gnu && go test -v -p 16 github.com/gophercloud/gophercloud 
github.com/gophercloud/gophercloud/acceptance/clients 
github.com/gophercloud/gophercloud/acceptance/openstack 
github.com/gophercloud/gophercloud/acceptance/openstack/blockstorage/extensions 
github.com/gophercloud/gophercloud/acceptance/openstack/blockstorage/v1 
github.com/gophercloud/gophercloud/acceptance/openstack/blockstorage/v2 
github.com/gophercloud/gophercloud/acceptance/openstack/compute/v2 
github.com/gophercloud/gophercloud/acceptance/openstack/db/v1 
github.com/gophercloud/gophercloud/acceptance/openstack/dns/v2 
github.com/gophercloud/gophercloud/acceptance/openstack/identity/v2 
github.com/gophercloud/gophercloud/acceptance/openstack/identity/v3 
github.com/gophercloud/gophercloud/acceptance/openstack/imageservice/v2 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2/extensions
 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2/extensions/fwaas
 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2/extensions/layer3
 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2/extensions/lbaas
 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2/extensions/lbaas_v2
 
github.com/gophercloud/gophercloud/acceptance/openstack/networking/v2/extensions/portsbinding
 github.com/gophercloud/gophercloud/acceptance/openstack/objectstorage/v1 
github.com/gophercloud/gophercloud/acceptance/openstack/orchestration/v1 
github.com/gophercloud/gophercloud/acceptance/openstack/sharedfilesystems/v2 
github.com/gophercloud/gophercloud/acceptance/tools 
github.com/gophercloud/gophercloud/internal 
github.com/gophercloud/gophercloud/openstack 
github.com/gophercloud/gophercloud/openstack/blockstorage/extensions/schedulerstats
 
github.com/gophercloud/gophercloud/openstack/blockstorage/extensions/schedulerstats/testing
 
github.com/gophercloud/gophercloud/openstack/blockstorage/extensions/volumeactions
 
github.com/gophercloud/gophercloud/openstack/blockstorage/extensions/volumeactions/testing
 
github.com/gophercloud/gophercloud/openstack/blockstorage/extensions/volumetenants
 github.com/gophercloud/gophercloud/openstack/blockstorage/v1/apiversions 
github.com/gophercloud/gophercloud/openstack/blockstorage/v1/apiversions/testing
 github.com/gophercloud/gophercloud/openstack/blockstorage/v1/snapshots 
github.com/gophercloud/gophercloud/openstack/blockstorage/v1/snapshots/testing 
github.com/gophercloud/gophercloud/openstack/blockstorage/v1/volumes 
github.com/gophercloud/gophercloud/openstack/blockstorage/v1/volumes/testing 
github.com/gophercloud/gophercloud/openstack/blockstorage/v1/volumetypes 
github.com/gophercloud/gophercloud/openstack/blockstorage/v1/volumetypes/testing
 github.com/gophercloud/gophercloud/openstack/blockstorage/v2/snapshots 
github.com/gophercloud/gophercloud/openstack/blockstorage/v2/snapshots/testing 
github.com/gophercloud/gophercloud/openstack/blockstorage/v2/volumes 
github.com/gophercloud/gophercloud/openstack/blockstorage/v2/volumes/testing 
github.com/gophercloud/gophercloud/openstack/cdn/v1/base 
github.com/gophercloud/gophercloud/openstack/cdn/v1/base/testing 
github.com/gophercloud/gophercloud/openstack/cdn/v1/flavors 
github.com/gophercloud/gophercloud/openstack/cdn/v1/flavors/testing 
github.com/gophercloud/gophercloud/openstack/cdn/v1/serviceassets 
github.com/gophercloud/gophercloud/openstack/cdn/v1/serviceassets/testing 
github.com/gophercloud/gophercloud/openstack/cdn/v1/services 
github.com/gophercloud/gophercloud/openstack/cdn/v1/services/testing 
github.com/gophercloud/gophercloud/openstack/common/extensions 
github.com/gophercloud/gophercloud/openstack/common/extensions/testing 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/attachinterfaces
 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/attachinterfaces/testing
 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/availabilityzones
 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/bootfromvolume
 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/bootfromvolume/testing
 github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/defsecrules 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/defsecrules/testing
 github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/diskconfig 
github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/diskconfig/testing
 github.com/gophercloud/gophercloud/openstack/compute/v2/extensions/floatingips 

Bug#868200: marked as pending

[Ondřej Nový]

tag 868200 pending
thanks

Hello,

Bug #868200 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/openstack/python/python-aioeventlet.git/commit/?id=4cbca0c

---
commit 4cbca0c9c2c8307d3cd1b1c5ab9a713dbab41b5d
Author: Ondřej Nový 
Date:   Tue Oct 31 15:09:20 2017 +0100

Drop build dependency on python3-trollius (Closes: #868200)

diff --git a/debian/changelog b/debian/changelog
index 4e5d284..35abdfb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,6 @@
 python-aioeventlet (0.5.1-2) UNRELEASED; urgency=medium
 
+  [ Daniel Baumann ]
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.
@@ -10,6 +11,9 @@ python-aioeventlet (0.5.1-2) UNRELEASED; urgency=medium
   * Updating standards version to 4.0.1.
   * Updating standards version to 4.1.0.
 
+  [ Ondřej Nový ]
+  * Drop build dependency on python3-trollius (Closes: #868200)
+
  -- Daniel Baumann   Fri, 04 Aug 2017 
21:59:18 +0200
 
 python-aioeventlet (0.5.1-1) unstable; urgency=medium

Processed: Bug#877298 marked as pending

[Debian Bug Tracking System]

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

> tag 877298 pending
Bug #877298 [src:swift] swift FTBFS FAIL: test_get 
(test.unit.common.test_db.TestDatabaseBroker)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877298: marked as pending

[Ondřej Nový]

tag 877298 pending
thanks

Hello,

Bug #877298 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/openstack/services/swift.git/commit/?id=361151b

---
commit 361151be5583524275f206261314ca37f6a51f52
Author: Ondřej Nový 
Date:   Tue Oct 31 15:17:10 2017 +0100

Closes: #877298

Change-Id: I249aacdc55b534a05af137f3285b96ffa9219345

diff --git a/debian/changelog b/debian/changelog
index c450398..7d10678 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,7 +5,7 @@ swift (2.15.1-1) experimental; urgency=medium
   * Bump required version of (build-)depends for new upstream release
   * d/p/syslog_log_name.patch: rebase
   * d/p/Be_more_tolerant_of_exception_messages_from_sqlite.patch:
-fix sqlite error
+fix sqlite error (Closes: #877298)
   * Don't restart rsyslog in postrm/postinst, it's done by trigger
   * d/copyright: Bump copyright years
   * Install swift-object-relinker

Processed: Bug#868200 marked as pending

[Debian Bug Tracking System]

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

> tag 868200 pending
Bug #868200 [src:python-aioeventlet] drop build dependency on python3-trollius
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#875688: libreoffice-report-builder: Design view is missing and existing reports won't run

[Rene Engelhard]

Hi,

On Tue, Oct 31, 2017 at 12:16:01PM +0100, MAG4 Piemonte wrote:
> thank you for the really fast solution.

Well, it's a "solution" to just wait, so I am not really sure thanking
_me_ is worthwile here ;-) I "just" tested it with 6.0, nothing more :)

> We will test version 6.0 as it will land in testing ...

That will take some time... - 6.0.0 will only be released next year
in February: https://wiki.documentfoundation.org/ReleasePlan/6.0#6.0.0_release

Regards,

Rene

Bug#880426: libreoffice-sdbc-firebird: fails to upgrade jessie -> stretch -> buster

[Andreas Beckmann]

Package: libreoffice-sdbc-firebird
Version: 1:5.4.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie' to 'stretch' to 'buster'.
It installed fine in 'jessie', and upgraded to 'stretch' successfully,
but then the upgrade to 'buster' failed.

In case the package was not part of an intermediate stable release,
the version from the preceding stable release was kept installed.

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

  Preparing to unpack .../112-libreoffice-sdbc-firebird_1%3a5.4.2-3_i386.deb ...
  dpkg-query: no packages found matching $DPKG_MAINTSCRIPT_PACKAGE
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-sdbc-firebird' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-sdbc-firebird/copyright' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-sdbc-firebird/changelog.Debian.gz' not owned by 
package '$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-sdbc-firebird/README.gz' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-maintscript-helper: error: directory 
'/usr/share/doc/libreoffice-sdbc-firebird' contains files not owned by package 
$DPKG_MAINTSCRIPT_PACKAGE, cannot switch to symlink
  dpkg: error processing archive 
/tmp/apt-dpkg-install-hwNvs8/112-libreoffice-sdbc-firebird_1%3a5.4.2-3_i386.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1


Looks like you just need to drop the '$DPKG_MAINTSCRIPT_PACKAGE' from
debian/*.maintscript - that gets escaped properly by dh_installdeb
in compat level 10. It has always been redundant anyway.


cheers,

Andreas


libreoffice-sdbc-firebird_1:5.4.2-3.log.gz
Description: application/gzip

Bug#880427: tinyproxy: If tinyproxy receives a SIGHUP, then the children exit without being restarted and tinyproxy hangs.

[Stephan Leemburg]

Package: tinyproxy
Version: 1.8.4-2
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
   
   Hanging tinyproxy, no proxied connections are handled anymore.

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

   Logrotate sends a SIGHUP, which triggers this problem.

   * What was the outcome of this action?

   Unusable tinyproxy.

   * What outcome did you expect instead?

   Usable tinyproxy


   Please see patch below

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

Kernel: Linux 4.4.19-1-pve (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tinyproxy depends on:
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  logrotate3.11.0-0.1
ii  lsb-base 9.20161125

tinyproxy recommends no packages.

tinyproxy suggests no packages.
-- no debconf information

### PATCH BELOW

--- tinyproxy-1.8.4/src/child.c 2015-12-07 15:19:00.0 +0100
+++ tinyproxy/src/child.c   2017-10-31 13:38:48.542095431 +0100
@@ -233,6 +233,9 @@
 
 ret = select(maxfd + 1, , NULL, NULL, NULL);
 if (ret == -1) {
+if (errno == EINTR) {
+continue;
+}
 log_message (LOG_ERR, "error calling select: %s",
  strerror(errno));
 exit(1);

Bug#880258: [Debian-med-packaging] Bug#880258: picard-tools: FTBFS: CollectRrbsMetricsTest.java:29: error: package org.testng does not exist

[Olivier Sallou]

testng maven definition needs to be modified in build.graddle to match
testng debian pom.

Following patch fix the compilation for tests:

--- a/build.gradle
+++ b/build.gradle
@@ -32,7 +32,7 @@
 compile 'com.github.samtools:htsjdk:' + htsjdkVersion
 //tools dependency for doclet requires sdk devel
 compile(files(((URLClassLoader)
ToolProvider.getSystemToolClassLoader()).getURLs()))
-    testCompile 'org.testng:testng:6.9.10'
+    testCompile 'org.testng:testng:debian'
 }
 
 sourceCompatibility = 1.8


however, all tests fail with the same issue than htsjdk when using
testng in graddle

Cannot nest operations in the same thread. Each nested operation must
run in its own thread.
java.lang.UnsupportedOperationException: Cannot nest operations in the
same thread. Each nested operation must run in its own thread.

I have no idea why (not using gradle), and asked to java team but got
not answer for the moment.

Olivier


On 10/30/2017 08:26 PM, Lucas Nussbaum wrote:
> Source: picard-tools
> Version: 2.8.1+dfsg-2
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20171030 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>> make[1]: Entering directory '/<>/picard-tools-2.8.1+dfsg'
>> # Tests do not work with locales with a different decimal separator
>> # (for example ',') 
>> env LC_ALL=C \
>> dh_auto_build -- test
>>  mkdir -p .gradle/init.d
>>  cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>>  gradle --info --console plain --offline --stacktrace --no-daemon 
>> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
>> -Duser.name=debian -Ddebian.package=picard-tools -Dfile.encoding=UTF-8 
>> --parallel --max-workers=16 test
>> Initialized native services in: 
>> /<>/picard-tools-2.8.1+dfsg/.gradle/native
>> To honour the JVM settings for this build a new JVM will be forked. Please 
>> consider using the daemon: 
>> https://docs.gradle.org/3.2.1/userguide/gradle_daemon.html.
>> Starting daemon process: workingDir = 
>> /<>/picard-tools-2.8.1+dfsg/.gradle/daemon/3.2.1, daemonArgs: 
>> [/usr/lib/jvm/java-8-openjdk-amd64/bin/java, -XX:MaxPermSize=256m, 
>> -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=UTF-8, 
>> -Duser.country=US, -Duser.language=en, -Duser.variant, -cp, 
>> /usr/share/gradle/lib/gradle-launcher-3.2.1.jar, 
>> org.gradle.launcher.daemon.bootstrap.GradleDaemon, 3.2.1]
>> Starting process 'Gradle build daemon'. Working directory: 
>> /<>/picard-tools-2.8.1+dfsg/.gradle/daemon/3.2.1 Command: 
>> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -XX:MaxPermSize=256m 
>> -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 
>> -Duser.country=US -Duser.language=en -Duser.variant -cp 
>> /usr/share/gradle/lib/gradle-launcher-3.2.1.jar 
>> org.gradle.launcher.daemon.bootstrap.GradleDaemon 3.2.1
>> Successfully started process 'Gradle build daemon'
>> An attempt to start the daemon took 0.62 secs.
>> Connected to daemon DaemonInfo{pid=103081, 
>> address=[2e268c2e-3c63-4337-afd4-2e65ac75aac2 port:38729, 
>> addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]], state=Busy, 
>> lastBusy=1509376996459, 
>> context=DefaultDaemonContext[uid=2cc7999a-a025-4898-ba87-3e84d29d2241,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/picard-tools-2.8.1+dfsg/.gradle/daemon,pid=103081,idleTimeout=12,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}.
>>  Dispatching request BuildAndStop{id=642d5534-8837-4bd9-b101-9d40666366dc.1, 
>> currentDir=/<>/picard-tools-2.8.1+dfsg}.
>> Received result org.gradle.launcher.daemon.protocol.BuildStarted@4a3631f8 
>> from daemon DaemonInfo{pid=103081, 
>> address=[2e268c2e-3c63-4337-afd4-2e65ac75aac2 port:38729, 
>> addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]], state=Busy, 
>> lastBusy=1509376996459, 
>> context=DefaultDaemonContext[uid=2cc7999a-a025-4898-ba87-3e84d29d2241,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/picard-tools-2.8.1+dfsg/.gradle/daemon,pid=103081,idleTimeout=12,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
>>  (build should be starting).
>> The client will now receive all logging from the daemon (pid: 103081). The 
>> daemon log file: 
>> /<>/picard-tools-2.8.1+dfsg/.gradle/daemon/3.2.1/daemon-103081.out.log
>> Closing daemon's stdin at end of input.
>> The daemon will no longer process any standard input.
>> Daemon will be stopped at the end of the build stopping after processing
>> Executing build with daemon context: 
>> 

Bug#880258: [Debian-med-packaging] Bug#880258: picard-tools: FTBFS: CollectRrbsMetricsTest.java:29: error: package org.testng does not exist

[Olivier Sallou]

htsjdk and picard-tools test issues are gradle related.
After some deeper tests and discussions with debian-java team, it
appears the errors faced in testing (after the patches I proposed on
testng) are related to the gradle version on debian.
Someone in java team should upgrade to an upper release I tested
manually with success (though 1 test failed for picard-tools and should
be investigated later on, but other tests are fine, and issue is not
build related).

New release should fix the issue.

In the meanwhile, to avoid packages removal, I suggest to apply my
proposed patches and to disable testing.
Once gradle is upgraded in repo, then we could go for test reactivation.

I can update code and upload both if everyone agrees with this strategy.

Only point is to not forget to follow gradle upgrade and which packages
should be updated to reintegrate tests. Could lower severity of those 2
bugs to keep track of the issue.

Olivier

-- 


gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#880449: unison: Uncaught exception Failure("input_value: bad bigarray kind")

[Vincent Lefevre]

Package: unison
Version: 2.48.4-1
Severity: grave
Justification: renders package unusable

Since the upgrade to 2.48.4-1, I get when synchronizing with
a Debian/stable server:

Unison failed: Uncaught exception Failure("input_value: bad bigarray kind")
Raised by primitive operation at file "/tmp/buildd/unison-2.48.3/remote.ml", 
line 453, characters 18-45
Called from file "/tmp/buildd/unison-2.48.3/remote.ml", line 459, characters 
23-61
Called from file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 75, characters 
20-23
Re-raised at file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 135, characters 
12-13
Called from file "list.ml", line 73, characters 12-15
Called from file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 31, characters 
2-37
Called from file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 83, characters 
17-46
Called from file "/tmp/buildd/unison-2.48.3/lwt/generic/lwt_unix_impl.ml", line 
147, characters 6-40
Called from file "/tmp/buildd/unison-2.48.3/main.ml", line 202, characters 6-24
Called from file "/tmp/buildd/unison-2.48.3/main.ml", line 131, characters 4-9

Fatal error: Lost connection with the server

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

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

Versions of packages unison depends on:
ii  libc6  2.24-17

Versions of packages unison recommends:
ii  openssh-client [ssh-client]  1:7.6p1-2

Versions of packages unison suggests:
ii  unison-all  2.48+2

-- no debconf information

Processed: severity of 854696 is grave

[Debian Bug Tracking System]

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

> severity 854696 grave
Bug #854696 [sanlock] sanlock: error in wdmd.service systemd unit file
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#880449: unison: Uncaught exception Failure("input_value: bad bigarray kind")

[Vincent Lefevre]

On 2017-10-31 18:33:36 +0100, Vincent Lefevre wrote:
> Since the upgrade to 2.48.4-1, I get when synchronizing with
> a Debian/stable server:
> 
> Unison failed: Uncaught exception Failure("input_value: bad bigarray kind")
[...]

https://github.com/bcpierce00/unison/issues/94 says:

"This happens when unison is not compiled with the same version of ocaml
on both machines. I don't know the ocaml version used in debian testing,
but you should install the same one to compile in debian wheezy."

The reporter used wheezy there, but in my case, this is between
unstable (this version) and stretch.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#880441: linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other programs

[Christoph Anton Mitterer]

Package: src:linux
Version: 4.13.10-1
Severity: critical
Justification: breaks unrelated software


Hi.

Apparently AppArmor was enabled per default in the last version.

While I'm usually in favour of anything that improves security
(leaving aside the question here whether SELinux wouldn't be the much
more powerful solution ;-) )... this happened too silent (e.g. no
NEWS entry)... peopl may not even have installed the userland tools.

Also it breaks unrelated software, e.g. tor no longer starts and some
more as well.


Cheers,
Chris.

Bug#880217: marked as done (ansible-tower-cli-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/ansible-tower-cli/CONFIG_CMD_OPTIONS.md.gz)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 15:04:49 +
with message-id 
and subject line Bug#880217: fixed in ansible-tower-cli 3.2.0-2
has caused the Debian Bug report #880217,
regarding ansible-tower-cli-doc: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/doc/ansible-tower-cli/CONFIG_CMD_OPTIONS.md.gz
to be marked as done.

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

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


-- 
880217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible-tower-cli-doc
Version: 3.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package ansible-tower-cli-doc.
  Preparing to unpack .../6-ansible-tower-cli-doc_3.2.0-1_all.deb ...
  Unpacking ansible-tower-cli-doc (3.2.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ZjLZ5A/6-ansible-tower-cli-doc_3.2.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/ansible-tower-cli/CONFIG_CMD_OPTIONS.md.gz', which is also in 
package ansible-tower-cli 3.1.4-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ZjLZ5A/6-ansible-tower-cli-doc_3.2.0-1_all.deb

There are similar problems in python3-tower-cli:

  Selecting previously unselected package python3-tower-cli.
  Preparing to unpack .../python3-tower-cli_3.2.0-1_all.deb ...
  Unpacking python3-tower-cli (3.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-tower-cli_3.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/tower_cli/VERSION', 
which is also in package ansible-tower-cli 3.1.4-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-tower-cli_3.2.0-1_all.deb


cheers,

Andreas


ansible-tower-cli=3.1.4-1_ansible-tower-cli-doc=3.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ansible-tower-cli
Source-Version: 3.2.0-2

We believe that the bug you reported is fixed in the latest version of
ansible-tower-cli, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Evgeni Golov  (supplier of updated ansible-tower-cli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Oct 2017 14:58:37 +0100
Source: ansible-tower-cli
Binary: ansible-tower-cli ansible-tower-cli-doc python-tower-cli 
python3-tower-cli
Architecture: source
Version: 3.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov 
Changed-By: Evgeni Golov 
Description:
 ansible-tower-cli - command line tool for Ansible Tower and AWX Project
 ansible-tower-cli-doc - documentation for tower-cli command line tool and 
library
 python-tower-cli - Python 2 client library for the Ansible Tower and AWX 
Project's R
 python3-tower-cli - Python 3 client library for the Ansible Tower and AWX 
Project's R
Closes: 880217
Changes:
 ansible-tower-cli (3.2.0-2) unstable; urgency=medium
 .
   * add replaces/breaks for ansible-tower-cli (<< 3.2.0-1~) (closes: #880217)
Checksums-Sha1:
 4ea9d0fc1958ee85b618f2d68c80badf75b0d49b 2465 ansible-tower-cli_3.2.0-2.dsc
 2c782c35cf1ab63a46db10b5008bf27446532895 3820 
ansible-tower-cli_3.2.0-2.debian.tar.xz
 85b18a3b8fc7c71f7aaba1527f6c29affe689ecd 7788 
ansible-tower-cli_3.2.0-2_source.buildinfo
Checksums-Sha256:
 c80447fe44bbc6b552938e24be6e13d2a2273828c5f07b38edbaf077eb7ef9c0 2465 
ansible-tower-cli_3.2.0-2.dsc
 620bf38fde2993d38c650621082533637ce36fd7d2551b53dafd11d7fec6f0fe 3820 
ansible-tower-cli_3.2.0-2.debian.tar.xz
 

Bug#880310: recoll: FTBFS: configure: error: qmake seems to be using Qt version 3 which is not supported any more

[Jean-Francois Dockes]

Lucas Nussbaum writes:
 > Source: recoll
 > Version: 1.23.2-1
 > Severity: serious
 > Tags: buster sid
 > User: debian...@lists.debian.org
 > Usertags: qa-ftbfs-20171030 qa-ftbfs
 > Justification: FTBFS on amd64
 > 
 > Hi,
 > 
 > During a rebuild of all packages in sid, your package failed to build on
 > amd64.
 > 
 > Relevant part (hopefully):
 > > checking for pthread_create in -lpthread... yes
 > > checking for dlopen in -ldl... yes
 > > checking for zlibVersion in -lz... yes
 > > checking for type of inbuf parameter to iconv... checking for type of 
 > > string parameter to putenv... checking for xapian-config... 
 > > /usr/bin/xapian-config
 > > checking for qmake... /usr/bin/qmake
 > > configure: error: qmake seems to be using Qt version 3 which is not 
 > > supported any more
 > > debian/rules:28: recipe for target 'config.status' failed
 > 
 > The full build log is available from:
 >http://aws-logs.debian.net/2017/10/30/recoll_1.23.2-1_unstable.log
 > 
 > A list of current common problems and possible solutions is available at
 > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
 > 
 > About the archive rebuild: The rebuild was done on EC2 VM instances from
 > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
 > failed build was retried once to eliminate random failures.


This seems to work fine for me (Build log on my Debian unstable VM follows).

The message about qt 3 is misleading, I'll change it. The part which fails
is the following: 


  # Check Qt version
  qmakevers="`${QMAKE} --version 2>&1`"
  #echo "qmake version: $qmakevers"
  v4=`expr "$qmakevers" : '.*Qt[ ][ ]*version[ ][ ]*4.*'`
  v5=`expr "$qmakevers" : '.*Qt[ ][ ]*version[ ][ ]*5.*'`
  if test X$v4 = X0 -a X$v5 = X0; then
 AC_MSG_ERROR([qmake seems to be using Qt version 3 which is not supported 
any more])
  else
if test X$v4 != X0 ; then
   AC_MSG_NOTICE([using qt version 4 user interface])
else
   AC_MSG_NOTICE([using qt version 5 user interface])
fi
QTGUI=qtgui
  fi



Have you got a way to print the output from:

/usr/bin/qmake --version 

in your build environment ?

Jf


deb-sid-64$ cat /etc/debian_version 
buster/sid

deb-sid-64$ cat /etc/apt/sources.list
deb http://debian.proxad.net/debian/ unstable main
deb-src http://debian.proxad.net/debian/ unstable main


deb-sid-64$ sudo apt update
Hit:1 http://debian.proxad.net/debian unstable InRelease
Hit:2 http://www.lesbonscomptes.com/upmpdcli/downloads/debian stretch InRelease
Reading package lists... Done
Building dependency tree   
Reading state information... Done
All packages are up to date.


deb-sid-64$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


deb-sid-64$ mkdir rclsrc
deb-sid-64$ cd rclsrc/
deb-sid-64$ apt-get source recoll
Reading package lists... Done
NOTICE: 'recoll' packaging is maintained in the 'Git' version control system at:
https://anonscm.debian.org/cgit/collab-maint/recoll.git
Please use:
git clone https://anonscm.debian.org/cgit/collab-maint/recoll.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 2559 kB of source archives.
Get:1 http://debian.proxad.net/debian unstable/main recoll 1.23.2-1 (dsc) [2132 
B]
Get:2 http://debian.proxad.net/debian unstable/main recoll 1.23.2-1 (tar) [2547 
kB]
Get:3 http://debian.proxad.net/debian unstable/main recoll 1.23.2-1 (diff) 
[9680 B]
Fetched 2559 kB in 4s (534 kB/s)
dpkg-source: info: extracting recoll in recoll-1.23.2
dpkg-source: info: unpacking recoll_1.23.2.orig.tar.gz
dpkg-source: info: unpacking recoll_1.23.2-1.debian.tar.xz



deb-sid-64$ cd recoll-1.23.2/
deb-sid-64$ debuild
 dpkg-buildpackage -rfakeroot -us -uc -ui
dpkg-buildpackage: info: source package recoll
dpkg-buildpackage: info: source version 1.23.2-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Kartik Mistry 
 dpkg-source --before-build recoll-1.23.2
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp config.log
[ ! -f Makefile ] || /usr/bin/make distclean
dh_clean Makefile
 dpkg-source -b recoll-1.23.2
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building recoll using existing ./recoll_1.23.2.orig.tar.gz
dpkg-source: warning: ignoring deletion of file filters/#rclpdf.py#, use 
--include-removal to override
dpkg-source: info: building recoll in recoll_1.23.2-1.debian.tar.xz
dpkg-source: info: building recoll in recoll_1.23.2-1.dsc
 debian/rules build
dh_testdir
./configure CFLAGS="-g -O2 
-fdebug-prefix-map=/home/dockes/rclsrc/recoll-1.23.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2" 
LDFLAGS="-Wl,-z,relro" \

Bug#877298: marked as done (swift FTBFS FAIL: test_get (test.unit.common.test_db.TestDatabaseBroker))

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 15:21:16 +
with message-id 
and subject line Bug#877298: fixed in swift 2.15.1-1
has caused the Debian Bug report #877298,
regarding swift FTBFS FAIL: test_get 
(test.unit.common.test_db.TestDatabaseBroker)
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.)


-- 
877298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift
Version: 2.10.2-1
Severity: serious

Some recent change in unstable makes swift FTBFS:

https://tests.reproducible-builds.org/debian/history/swift.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/swift.html

...
==
FAIL: test_get (test.unit.common.test_db.TestDatabaseBroker)
--
Traceback (most recent call last):
  File "/build/1st/swift-2.10.2/test/unit/common/test_db.py", line 792, in 
test_get
(dbpath, qpath))
AssertionError: 'DB connection error (/tmp/tmplHrR81/dev/dbs/par/pre/db/1.db, 
25):\nTraceback (most recent call last):\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 187, in get_db_connection\n  
  cur.execute(\'PRAGMA synchronous = NORMAL\')\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 134, in execute\n
self.timeout, self.db_file, lambda: sqlite3.Cursor.execute(\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 72, in _db_timeout\n
return call()\n  File "/build/1st/swift-2.10.2/swift/common/db.py", line 135, 
in \nself, *args, **kwargs))\nDatabaseError: file is not a 
database\n' != 'Quarantined /tmp/tmplHrR81/dev/dbs/par/pre/db to 
/tmp/tmplHrR81/dev/quarantined/tests/db due to corrupted database'
'\'DB connection error (/tmp/tmplHrR81/dev/dbs/par/pre/db/1.db, 
25):\\nTraceback (most recent call last):\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 187, in get_db_connection\\n 
   cur.execute(\\\'PRAGMA synchronous = NORMAL\\\')\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 134, in execute\\n
self.timeout, self.db_file, lambda: sqlite3.Cursor.execute(\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 72, in _db_timeout\\n
return call()\\n  File "/build/1st/swift-2.10.2/swift/common/db.py", line 135, 
in \\nself, *args, **kwargs))\\nDatabaseError: file is not a 
database\\n\' != \'Quarantined /tmp/tmplHrR81/dev/dbs/par/pre/db to 
/tmp/tmplHrR81/dev/quarantined/tests/db due to corrupted database\'' = '%s != 
%s' % (safe_repr('DB connection error (/tmp/tmplHrR81/dev/dbs/par/pre/db/1.db, 
25):\nTraceback (most recent call last):\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 187, in get_db_connection\n  
  cur.execute(
 \'PRAGMA synchronous = NORMAL\')\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 134, in execute\n
self.timeout, self.db_file, lambda: sqlite3.Cursor.execute(\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 72, in _db_timeout\n
return call()\n  File "/build/1st/swift-2.10.2/swift/common/db.py", line 135, 
in \nself, *args, **kwargs))\nDatabaseError: file is not a 
database\n'), safe_repr('Quarantined /tmp/tmplHrR81/dev/dbs/par/pre/db to 
/tmp/tmplHrR81/dev/quarantined/tests/db due to corrupted database'))
'\'DB connection error (/tmp/tmplHrR81/dev/dbs/par/pre/db/1.db, 
25):\\nTraceback (most recent call last):\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 187, in get_db_connection\\n 
   cur.execute(\\\'PRAGMA synchronous = NORMAL\\\')\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 134, in execute\\n
self.timeout, self.db_file, lambda: sqlite3.Cursor.execute(\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 72, in _db_timeout\\n
return call()\\n  File "/build/1st/swift-2.10.2/swift/common/db.py", line 135, 
in \\nself, *args, **kwargs))\\nDatabaseError: file is not a 
database\\n\' != \'Quarantined /tmp/tmplHrR81/dev/dbs/par/pre/db to 
/tmp/tmplHrR81/dev/quarantined/tests/db due to corrupted database\'' = 
self._formatMessage('\'DB connection error 
(/tmp/tmplHrR81/dev/dbs/par/pre/db/1.db, 25):\\nTraceback (most recent call 
last):\\n  File "/build/1st/swift-2.10.2/swift/common/db.py", line 187, in 
get_db_connection\\ncur.execute
 (\\\'PRAGMA synchronous = NORMAL\\\')\\n  File 
"/build/1st/swift-2.10.2/swift/common/db.py", line 134, in execute\\n
self.timeout, self.db_file, lambda: sqlite3.Cursor.execute(\\n  File 

Bug#880441: linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other programs

[Ben Hutchings]

Control: severity -1 important
Control: affects -1 tor

On Tue, 2017-10-31 at 16:07 +0100, Christoph Anton Mitterer wrote:
> Package: src:linux
> Version: 4.13.10-1
> Severity: critical
> Justification: breaks unrelated software
>
> Apparently AppArmor was enabled per default in the last version.

Although you can disable it (security=dac or apparmor=0) if you want.

> While I'm usually in favour of anything that improves security
> (leaving aside the question here whether SELinux wouldn't be the much
> more powerful solution ;-) )... this happened too silent (e.g. no
> NEWS entry)... peopl may not even have installed the userland tools.

The change was noted in the changelog, so it's not silent.

I intend to add a NEWS entry in the next linux-latest upload.  It
doesn't make sense to add NEWS to linux-image-* packages as that will
only be displayed for upgrades that don't involve an ABI bump

My understanding was that enabling AppArmor shouldn't do very much
until a policy is loaded (which it won't be if you don't install the
userland tools).  As you've found, that isn't entirely correct.

> Also it breaks unrelated software, e.g. tor no longer starts and some
> more as well.

Applications built for Linux are unrelated to Linux?  I don't think so.

Ben.

-- 
Ben Hutchings
It is a miracle that curiosity survives formal education. - Albert
Einstein



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

Processed: Re: Bug#880441: linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other programs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #880441 [src:linux] linux-image-4.13.0-1-amd64: silently enabled AppArmor 
breaks other programs
Severity set to 'important' from 'critical'
> affects -1 tor
Bug #880441 [src:linux] linux-image-4.13.0-1-amd64: silently enabled AppArmor 
breaks other programs
Added indication that 880441 affects tor

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

Bug#873860: [Pkg-ime-devel] Bug#873860: ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: illegal multibyte sequence

[Osamu Aoki]

Hi,

On Fri, Oct 27, 2017 at 04:38:08PM +0900, Takatsugu Nokubi wrote:
> On Fri, 22 Sep 2017 23:20:39 +0900 Osamu Aoki  wrote:
> > On Fri, Sep 22, 2017 at 09:14:22AM +0200, John Paul Adrian Glaubitz wrote:
> > > This FTBFS can be easily fixed with:
> > >
> > > --- ibus-anthy-1.5.9.orig/data/zipcode-textdic.py
> > > +++ ibus-anthy-1.5.9/data/zipcode-textdic.py
> > > @@ -21,7 +21,7 @@ if len(sys.argv) < 2:
> > >  anthy_zipfile = sys.argv[1]
> > >
> > >  try:
> > > -contents = codecs.open(anthy_zipfile, 'r', 'euc_jp').read()
> > > +contents = codecs.open(anthy_zipfile, 'r', 'utf-8').read()
> > >  except UnicodeDecodeError as e:
> > >  print('Your file is not eucJP? %s' % anthy_zipfile, file=sys.stderr)
> > >  contents = open(anthy_zipfile).read()
> 
> I think it seems right way.
> 
> > Question is how to coordinate with other anthy users and the latest
> > ibus.
> 
> I had to see the upstream code, and the script seems not there.
> https://github.com/phuang/ibus-anthy/tree/master/data
> 
> I think we can choose the 2 ways:
> 
> 1. just apply this patch
> It seems not come from the upstream, so we don't need to take
> care about it.
> 
> 2. fix to work with both encoding zipfile
> When the script get the exception, retry to open as utf-8, it may work
> both version of anthy.


I think 1 should be the way to move forward.

I thought about uploading ibus first but maybe I was wrong.  If you have
time, please upload fixed package.

The only thing to do maybe adding conflict to anthy in sid 1:0.3-6
to all the older non-UTF-8 compatible IM packages of
 ibus-anthy
 uim-anthy
 fcitx-anthy
as 1:0.3-7.  Then we can make all these packages move together from sid
to testing.  

Osamu

Bug#880258: [Debian-med-packaging] Bug#880258: Bug#880258: picard-tools: FTBFS: CollectRrbsMetricsTest.java:29: error: package org.testng does not exist

[Olivier Sallou]

On 10/31/2017 03:05 PM, Olivier Sallou wrote:
> testng maven definition needs to be modified in build.graddle to match
> testng debian pom.
>
> Following patch fix the compilation for tests:
>
> --- a/build.gradle
> +++ b/build.gradle
> @@ -32,7 +32,7 @@
>  compile 'com.github.samtools:htsjdk:' + htsjdkVersion
>  //tools dependency for doclet requires sdk devel
>  compile(files(((URLClassLoader)
> ToolProvider.getSystemToolClassLoader()).getURLs()))
> -    testCompile 'org.testng:testng:6.9.10'
> +    testCompile 'org.testng:testng:debian'
>  }
>  
>  sourceCompatibility = 1.8
>
>
> however, all tests fail with the same issue than htsjdk when using
> testng in graddle
>
> Cannot nest operations in the same thread. Each nested operation must
> run in its own thread.
> java.lang.UnsupportedOperationException: Cannot nest operations in the
> same thread. Each nested operation must run in its own thread.
of course, we could easilly (though need to add patch anyway) to skip
testing, and wait to find a way to fix this gradle+testng issue, but
could lead to invalid packages
>
> I have no idea why (not using gradle), and asked to java team but got
> not answer for the moment.
>
> Olivier
>
>
> On 10/30/2017 08:26 PM, Lucas Nussbaum wrote:
>> Source: picard-tools
>> Version: 2.8.1+dfsg-2
>> Severity: serious
>> Tags: buster sid
>> User: debian...@lists.debian.org
>> Usertags: qa-ftbfs-20171030 qa-ftbfs
>> Justification: FTBFS on amd64
>>
>> Hi,
>>
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64.
>>
>> Relevant part (hopefully):
>>> make[1]: Entering directory '/<>/picard-tools-2.8.1+dfsg'
>>> # Tests do not work with locales with a different decimal separator
>>> # (for example ',') 
>>> env LC_ALL=C \
>>> dh_auto_build -- test
>>> mkdir -p .gradle/init.d
>>> cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>>> gradle --info --console plain --offline --stacktrace --no-daemon 
>>> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
>>> -Duser.name=debian -Ddebian.package=picard-tools -Dfile.encoding=UTF-8 
>>> --parallel --max-workers=16 test
>>> Initialized native services in: 
>>> /<>/picard-tools-2.8.1+dfsg/.gradle/native
>>> To honour the JVM settings for this build a new JVM will be forked. Please 
>>> consider using the daemon: 
>>> https://docs.gradle.org/3.2.1/userguide/gradle_daemon.html.
>>> Starting daemon process: workingDir = 
>>> /<>/picard-tools-2.8.1+dfsg/.gradle/daemon/3.2.1, daemonArgs: 
>>> [/usr/lib/jvm/java-8-openjdk-amd64/bin/java, -XX:MaxPermSize=256m, 
>>> -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=UTF-8, 
>>> -Duser.country=US, -Duser.language=en, -Duser.variant, -cp, 
>>> /usr/share/gradle/lib/gradle-launcher-3.2.1.jar, 
>>> org.gradle.launcher.daemon.bootstrap.GradleDaemon, 3.2.1]
>>> Starting process 'Gradle build daemon'. Working directory: 
>>> /<>/picard-tools-2.8.1+dfsg/.gradle/daemon/3.2.1 Command: 
>>> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -XX:MaxPermSize=256m 
>>> -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 
>>> -Duser.country=US -Duser.language=en -Duser.variant -cp 
>>> /usr/share/gradle/lib/gradle-launcher-3.2.1.jar 
>>> org.gradle.launcher.daemon.bootstrap.GradleDaemon 3.2.1
>>> Successfully started process 'Gradle build daemon'
>>> An attempt to start the daemon took 0.62 secs.
>>> Connected to daemon DaemonInfo{pid=103081, 
>>> address=[2e268c2e-3c63-4337-afd4-2e65ac75aac2 port:38729, 
>>> addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]], state=Busy, 
>>> lastBusy=1509376996459, 
>>> context=DefaultDaemonContext[uid=2cc7999a-a025-4898-ba87-3e84d29d2241,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/picard-tools-2.8.1+dfsg/.gradle/daemon,pid=103081,idleTimeout=12,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}.
>>>  Dispatching request 
>>> BuildAndStop{id=642d5534-8837-4bd9-b101-9d40666366dc.1, 
>>> currentDir=/<>/picard-tools-2.8.1+dfsg}.
>>> Received result org.gradle.launcher.daemon.protocol.BuildStarted@4a3631f8 
>>> from daemon DaemonInfo{pid=103081, 
>>> address=[2e268c2e-3c63-4337-afd4-2e65ac75aac2 port:38729, 
>>> addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]], state=Busy, 
>>> lastBusy=1509376996459, 
>>> context=DefaultDaemonContext[uid=2cc7999a-a025-4898-ba87-3e84d29d2241,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/picard-tools-2.8.1+dfsg/.gradle/daemon,pid=103081,idleTimeout=12,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
>>>  (build should be starting).
>>> The client will now receive all logging from the daemon (pid: 103081). The 
>>> daemon log file: 
>>> /<>/picard-tools-2.8.1+dfsg/.gradle/daemon/3.2.1/daemon-103081.out.log
>>> Closing daemon's stdin at end of input.
>>> The daemon will 

Bug#868200: marked as done (drop build dependency on python3-trollius)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 15:19:46 +
with message-id 
and subject line Bug#868200: fixed in python-aioeventlet 0.5.1-2
has caused the Debian Bug report #868200,
regarding drop build dependency on python3-trollius
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.)


-- 
868200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aioeventlet
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: python3.6 no-more-python3-trollius

Hi,

I want to remove the python3-trollius package from Debian, and
python-aioeventlet only imports trollius if asyncio is not found, and
asyncio is part of all supported versions of Python 3 in Debian, so the
build-depends on python3-trollius can simply be dropped.

Cheers,
mwh
--- End Message ---
--- Begin Message ---
Source: python-aioeventlet
Source-Version: 0.5.1-2

We believe that the bug you reported is fixed in the latest version of
python-aioeventlet, 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 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-aioeventlet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Oct 2017 15:15:09 +0100
Source: python-aioeventlet
Binary: python-aioeventlet python-aioeventlet-doc python3-aioeventlet
Architecture: source
Version: 0.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Ondřej Nový 
Description:
 python-aioeventlet - asyncio event loop scheduling callbacks in eventlet - 
Python 2.x
 python-aioeventlet-doc - asyncio event loop scheduling callbacks in eventlet - 
doc
 python3-aioeventlet - asyncio event loop scheduling callbacks in eventlet - 
Python 3.x
Closes: 868200
Changes:
 python-aioeventlet (0.5.1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Baumann ]
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles.
 .
   [ Ondřej Nový ]
   * Drop build dependency on python3-trollius (Closes: #868200)
   * Updating standards version to 4.1.1.
Checksums-Sha1:
 6d835c86384e69269b4032a704780ef3ee9d8b2c 2389 python-aioeventlet_0.5.1-2.dsc
 9fe48e5e365eec0ac3e2811b192fc9a9a7ebeaca 2972 
python-aioeventlet_0.5.1-2.debian.tar.xz
 e8e72b60ecce56799eaf15714a54b2fae30128b3 8068 
python-aioeventlet_0.5.1-2_amd64.buildinfo
Checksums-Sha256:
 52d2b06e648b741a31d0c546c3bcab44e24521855214d5a6a43a216d00b3c788 2389 
python-aioeventlet_0.5.1-2.dsc
 54313d24ac945a8b82814f2a96b5f26824b2a60debb2dc0bd07403b4e7e21ebe 2972 
python-aioeventlet_0.5.1-2.debian.tar.xz
 209bdcc67f0513a593025c5f643027ecd677a68421dd66a805391d3d4b1f9380 8068 
python-aioeventlet_0.5.1-2_amd64.buildinfo
Files:
 3c948af27a841d6a05312798639f64e3 2389 python optional 
python-aioeventlet_0.5.1-2.dsc
 bc48e2e13c96e54b042d068bb96ecab7 2972 python optional 
python-aioeventlet_0.5.1-2.debian.tar.xz
 eef946ce9322721d781b00ef0d64c3b1 8068 python optional 
python-aioeventlet_0.5.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAln4hkQACgkQNXMSVZ0e
BksQlg/8CI43D4/z9DqMswwFXwr7AvjIw/MYeLxZx9HDu6cllmUS5BV/kWCDuG3f
pyCAPEH9LrJE18EL5tvIRpbVSoRWw/V7qhLRqfs5Lnc9OBR0044y6CmioCmBquKe
Y6JNRryeg9LaQz+GU6Ll6F7i0eddyJdrs87iTiQMMGKHQ1jtHV/eK5RDQ3a5rnXc
+ZvZ66Wfhqm7H4AnIQVKZWr3Pa0QpstPGjHzdM3auTftiXJ6vdLTW9iA9xuupaXS
ova1K/gO+ijaAtzuk5tR836i2nSYImpxQQEfiow7dd4Sea4azAiPjpqyUAKgybOp
EUvQY1wa/EIzpThMi7S8uJicKJXD/tBruL3pEbPUNswQU9D19kX8zOilTar7XaeC
XjbwdK7eT21bySQvm0LHmOFYpWYxxuKOSzbrmft57TGlueoGF6IJsyEOXx6G8/Ld
MEX9HxnVOjV66M1JFloCLRbwciMzQgh+qjPu0tgkApP1eq267sSLlnh/n18wVX3u
9Ivx1cB3/j9uyHjt7l64/hi14T96c7317Oid3PMLBc9lQLtmIyU0ruVM5jwDk58S
2NpCmsGKEdOrq+9mrt2wpFHpHUV3CPCkTNaGOXuv8w8t6iw6feJDOckYAuUAbLQy
3LzDYAxZN+6SmNFq66X5mhAeedMh2Qn9JOgei++oh8KkdUuOpAg=
=oWRh
-END PGP SIGNATURE End 

Bug#816570: marked as done (mrtrix: FTBFS with GCC 6: call overloaded is ambiguous)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 15:51:12 +
with message-id 
and subject line Bug#816570: fixed in mrtrix 0.2.12-2.1
has caused the Debian Bug report #816570,
regarding mrtrix: FTBFS with GCC 6: call overloaded is ambiguous
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.)


-- 
816570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mrtrix
Version: 0.2.12-2
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> ERROR: [CC] cmd/tracks2prob.o
> 
> g++ -c -Wall -pedantic -fPIC -fno-strict-aliasing -DGL_GLEXT_PROTOTYPES 
> -DUSE_TR1 -g -std=c++11 -pthread -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 
> -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Ilib -Isrc cmd/tracks2prob.cpp 
> -o cmd/tracks2prob.o
> 
> failed with output:
> 
> In file included from src/dwi/tractography/roi.h:28:0,
>  from src/dwi/tractography/properties.h:27,
>  from src/dwi/tractography/file.h:30,
>  from cmd/tracks2prob.cpp:43:
> lib/image/interp.h: In member function 'float MR::Image::Interp::re() const':
> lib/image/interp.h:238:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (faaa) val  = faaa * image.re (os); os += stride[2];
>   ^~
> lib/image/interp.h:238:7: note: ...this 'if' clause, but it is not
>if (faaa) val  = faaa * image.re (os); os += stride[2];
>^~
> lib/image/interp.h:239:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (faab) val += faab * image.re (os); os += stride[1];
>   ^~
> lib/image/interp.h:239:7: note: ...this 'if' clause, but it is not
>if (faab) val += faab * image.re (os); os += stride[1];
>^~
> lib/image/interp.h:240:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (fabb) val += fabb * image.re (os); os -= stride[2];
>   ^~
> lib/image/interp.h:240:7: note: ...this 'if' clause, but it is not
>if (fabb) val += fabb * image.re (os); os -= stride[2];
>^~
> lib/image/interp.h:241:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (faba) val += faba * image.re (os); os += stride[0];
>   ^~
> lib/image/interp.h:241:7: note: ...this 'if' clause, but it is not
>if (faba) val += faba * image.re (os); os += stride[0];
>^~
> lib/image/interp.h:242:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (fbba) val += fbba * image.re (os); os -= stride[1];
>   ^~
> lib/image/interp.h:242:7: note: ...this 'if' clause, but it is not
>if (fbba) val += fbba * image.re (os); os -= stride[1];
>^~
> lib/image/interp.h:243:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (fbaa) val += fbaa * image.re (os); os += stride[2];
>   ^~
> lib/image/interp.h:243:7: note: ...this 'if' clause, but it is not
>if (fbaa) val += fbaa * image.re (os); os += stride[2];
>^~
> lib/image/interp.h:244:46: warning: statement is indented as if it were 
> guarded by... [-Wmisleading-indentation]
>if (fbab) val += fbab * image.re (os); os += stride[1];
>   ^~
> lib/image/interp.h:244:7: note: ...this 'if' clause, but it is not
>if (fbab) val += fbab * image.re (os); os += stride[1];
>^~
> lib/image/interp.h: In member function 'float MR::Image::Interp::im() const':
> lib/image/interp.h:258:46: warning: statement is indented as if it were 
> 

Bug#877242: marked as pending

[Thomas Goirand]

tag 877242 pending
thanks

Hello,

Bug #877242 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/openstack/services/neutron-taas.git/commit/?id=da2ecb8

---
commit da2ecb8b25204512a3384c041b1e339840d6c521
Author: Thomas Goirand 
Date:   Tue Oct 31 18:55:33 2017 +

changelog closes #877242

diff --git a/debian/changelog b/debian/changelog
index 1940e3f..597e7b1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -12,7 +12,8 @@ neutron-taas (2.0.0-1) experimental; urgency=medium
   * Updating standards version to 4.1.0.
 
   [ Thomas Goirand ]
-  * New upstream release.
+  * New upstream release:
+- Fixes unit tests (Closes: #877242).
   * Fixed (build-)depends for this release.
   * neutron-taas-openvswitch-agent depends on lsb-base.
   * Standards-Version is now 4.1.1.

Processed: Bug#877242 marked as pending

[Debian Bug Tracking System]

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

> tag 877242 pending
Bug #877242 [src:neutron-taas] neutron-taas: FTBFS: Failed 23 tests
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Actually reassigning; fixing syntax

[Debian Bug Tracking System]

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

> reassign 880460 gnustep-gui-runtime 0.25.0-4
Bug #880460 [release.debian.org] gnustep-gui-runtime: Depends on 
gnustep-back0.25
Bug reassigned from package 'release.debian.org' to 'gnustep-gui-runtime'.
Ignoring request to alter found versions of bug #880460 to the same values 
previously set
Ignoring request to alter fixed versions of bug #880460 to the same values 
previously set
Bug #880460 [gnustep-gui-runtime] gnustep-gui-runtime: Depends on 
gnustep-back0.25
Marked as found in versions gnustep-gui/0.25.0-4.
> thanks
Stopping processing here.

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

Bug#877242: marked as done (neutron-taas: FTBFS: Failed 23 tests)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 19:19:31 +
with message-id 
and subject line Bug#877242: fixed in neutron-taas 2.0.0-1
has caused the Debian Bug report #877242,
regarding neutron-taas: FTBFS: Failed 23 tests
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.)


-- 
877242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neutron-taas
Version: 0.0.0+git20160808.c612a729-1
Severity: serious
Justification: fails to build from source

Hi,

neutron-taas FTBFS in a current sid+experimental environment. See the
attached build log for details.


Andreas


neutron-taas_0.0.0+git20160808.c612a729-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: neutron-taas
Source-Version: 2.0.0-1

We believe that the bug you reported is fixed in the latest version of
neutron-taas, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated neutron-taas package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 31 Oct 2017 12:15:23 +0100
Source: neutron-taas
Binary: neutron-taas-openvswitch-agent python-neutron-taas
Architecture: source all
Version: 2.0.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 neutron-taas-openvswitch-agent - OpenStack virtual network service - 
Tap-as-a-Service agent
 python-neutron-taas - OpenStack virtual network service - Tap-as-a-Service 
extension
Closes: 877242
Changes:
 neutron-taas (2.0.0-1) experimental; urgency=medium
 .
   [ Daniel Baumann ]
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Updating standards version to 4.0.0.
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles.
   * Updating standards version to 4.0.1.
   * Updating standards version to 4.1.0.
 .
   [ Thomas Goirand ]
   * New upstream release:
 - Fixes unit tests (Closes: #877242).
   * Fixed (build-)depends for this release.
   * neutron-taas-openvswitch-agent depends on lsb-base.
   * Standards-Version is now 4.1.1.
   * Added myself as uploader.
   * Do not define OSLO_PACKAGE_VERSION, defined in openstack-pkg-tools.
   * Using debhelper 10.
   * python-neutron-taas in section python.
Checksums-Sha1:
 2ff35c306f57e7754aafba1d195813a227e7e2f3 2538 neutron-taas_2.0.0-1.dsc
 3e86c9adf1bfd47b55a6201f9bc83d16a1247c37 50712 neutron-taas_2.0.0.orig.tar.xz
 126da7f059fe1384ac0dd25e0a404932a870b0b2 3352 
neutron-taas_2.0.0-1.debian.tar.xz
 1285ee4ce41f998a03aabe1e1e087c3f8bec5040 6044 
neutron-taas-openvswitch-agent_2.0.0-1_all.deb
 56299e561ec6f471787d97a5b4fe6d3af5a4311d 16364 
neutron-taas_2.0.0-1_amd64.buildinfo
 e17343702a32718d214fc7136465f6dec1584d19 39516 
python-neutron-taas_2.0.0-1_all.deb
Checksums-Sha256:
 2ad2367e0d1442f33b75a7758a3d10d4749f63393bfa35d0ff0b6a1232812b1b 2538 
neutron-taas_2.0.0-1.dsc
 94f1bbca49fe54b24d6f2854c146adb75b71bf589759bc50c7c968f35a5eb439 50712 
neutron-taas_2.0.0.orig.tar.xz
 fdd953d768c78610d9de14c96bf67526bd194bc50a92da563b3c1c64563fb586 3352 
neutron-taas_2.0.0-1.debian.tar.xz
 5bceb0ac57bb308718cca3661867e107208834cb5b662738e7f75c71ce8fd46e 6044 
neutron-taas-openvswitch-agent_2.0.0-1_all.deb
 391f5cbbabefecff58c2ce98644f4677216925739e84127671edd9222b36c3f1 16364 
neutron-taas_2.0.0-1_amd64.buildinfo
 c72916a0556e0e4960b4bf66abbcd3b2264774aece7ea77e1841ae495af74d0a 39516 
python-neutron-taas_2.0.0-1_all.deb
Files:
 1c9ae204f340e3bdbe72b41fa80fe748 2538 net optional neutron-taas_2.0.0-1.dsc
 1d1bc2e3a7a69ab568340c8ac3eb16dd 50712 net optional 
neutron-taas_2.0.0.orig.tar.xz
 48622c03a1e8f93220e4c4186e6b2060 3352 net optional 
neutron-taas_2.0.0-1.debian.tar.xz
 995991d3e452fefd0be1e90127796d25 6044 net optional 
neutron-taas-openvswitch-agent_2.0.0-1_all.deb
 6232879b40ba906163a4c11dc8a66655 16364 

Processed (with 1 error): Re: Bug#879738: transition: gnustep-base

[Debian Bug Tracking System]

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

> clone 879738 -1
Bug #879738 [release.debian.org] transition: gnustep-base
Bug 879738 cloned as bug 880460
> reassign -1 gnustep-gui-runtime/0.25.0-4
Unknown command or malformed arguments to command.
> retitle -1 gnustep-gui-runtime: Depends on gnustep-back0.25
Bug #880460 [release.debian.org] transition: gnustep-base
Changed Bug title to 'gnustep-gui-runtime: Depends on gnustep-back0.25' from 
'transition: gnustep-base'.
> severity -1 serious
Bug #880460 [release.debian.org] gnustep-gui-runtime: Depends on 
gnustep-back0.25
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#853410: galera-3: ftbfs with GCC-7

[Dimitri John Ledkov]

On Tue, 31 Jan 2017 09:31:28 + Matthias Klose  wrote:
> Package: src:galera-3
> Version: 25.3.19-2
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-7
>

Well, building without -Werror works...
Description: Build without Werror to resolve FTBFS with gcc 7. Closes: #853410
Author: Dimitri John Ledkov 
Bug-Debian: https://bugs.debian.org/853410

--- galera-3-25.3.20.orig/SConstruct
+++ galera-3-25.3.20/SConstruct
@@ -444,7 +444,7 @@ if ssl == 1:
 
 # these will be used only with our softaware
 if strict_build_flags == 1:
-conf.env.Append(CCFLAGS = ' -Werror -pedantic')
+conf.env.Append(CCFLAGS = ' -pedantic')
 if 'clang' not in conf.env['CXX']:
 conf.env.Prepend(CXXFLAGS = '-Weffc++ -Wold-style-cast ')
 else:
--- galera-3-25.3.20.orig/gcache/configure.ac
+++ galera-3-25.3.20/gcache/configure.ac
@@ -80,7 +80,7 @@ AC_CHECK_FUNCS([gettimeofday localtime_r
 AC_CONFIG_FILES([Makefile
  src/Makefile])
 
-AM_CFLAGS="$AM_CFLAGS -Wall -Werror -Wextra -pedantic -Wno-unused-parameter"
+AM_CFLAGS="$AM_CFLAGS -Wall -Wextra -pedantic -Wno-unused-parameter"
 AM_CXXFLAGS="$AM_CFLAGS -ansi -Weffc++ -Wold-style-cast -Wconversion"
 AM_CXXFLAGS="$AM_CXXFLAGS -fno-rtti -Wno-long-long"
 AM_CFLAGS="$AM_CFLAGS -std=c99"

Bug#880409: python-django: add Breaks: openstack-dashboard (<< 3:12)

[Chris Lamb]

Hi Andreas,

> Oh, #867254 was only filed for the "trivial" case in sid. But the
> problem also occurs on upgrades from stretch (openstack-dashboard gets
> triggered after python-django was upgraded and blows up), which is the
> case we need the Breaks for.
> 
> https://piuparts.debian.org/stretch2buster/fail/openstack-dashboard_None.log

Perhaps I'm missing something, but isn't there a solution in
openstack-dashboard itself? (Pre-Depends...?)

Again, it just feels really wrong to fix it here..


Regards,

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

Bug#880182: marked as pending

[Ondřej Nový]

tag 880182 pending
thanks

Hello,

Bug #880182 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/openstack/libs/python-os-api-ref.git/commit/?id=9c8d8d6

---
commit 9c8d8d60d1041add035ad412a819fe836b9cbce5
Author: Ondřej Nový 
Date:   Tue Oct 31 22:16:35 2017 +0100

Fix UnicodeDecodeError (Closes: #880182)

Change-Id: I942fec72f9fd486d39c55d5f56cb257d2da3094b

diff --git a/debian/changelog b/debian/changelog
index 497e1e9..4c958f8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-os-api-ref (1.4.0-2) UNRELEASED; urgency=medium
+
+  * Fix UnicodeDecodeError (Closes: #880182)
+
+ -- Ondřej Nový   Tue, 31 Oct 2017 22:16:11 +0100
+
 python-os-api-ref (1.4.0-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Bug#880182: marked as done (python-os-api-ref: FTBFS: tests fail with UnicodeDecodeError)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 21:48:51 +
with message-id 
and subject line Bug#880182: fixed in python-os-api-ref 1.4.0-2
has caused the Debian Bug report #880182,
regarding python-os-api-ref: FTBFS: tests fail with UnicodeDecodeError
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.)


-- 
880182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-os-api-ref
Version: 1.4.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-os-api-ref/experimental FTBFS in a clean minimal sid+experimental
environment:

==
FAIL: os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist
os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist
--
_StringException: Empty attachments:
  stderr
  stdout

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line 143, in 
decorator
func(*(args + (app, status, warning)), **kwargs)
  File "/build/python-os-api-ref-1.4.0/os_api_ref/tests/test_warnings.py", line 
41, in setUp
self.html = (app.outdir / 'index.html').read_text()
  File "/usr/lib/python3/dist-packages/sphinx_testing/path.py", line 161, in 
read_text
return f.read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 5094: 
ordinal not in range(128)


--
Ran 17 tests in 5.951s

FAILED (failures=16)
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Andreas


python-os-api-ref_1.4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-os-api-ref
Source-Version: 1.4.0-2

We believe that the bug you reported is fixed in the latest version of
python-os-api-ref, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-os-api-ref package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Oct 2017 22:16:45 +0100
Source: python-os-api-ref
Binary: python-os-api-ref python-os-api-ref-common python3-os-api-ref
Architecture: source
Version: 1.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Ondřej Nový 
Description:
 python-os-api-ref - Sphinx Extensions to support API reference sites in 
OpenStack - P
 python-os-api-ref-common - Sphinx Extensions to support API reference sites in 
OpenStack - c
 python3-os-api-ref - Sphinx Extensions to support API reference sites in 
OpenStack - P
Closes: 880182
Changes:
 python-os-api-ref (1.4.0-2) unstable; urgency=medium
 .
   * Uploading to unstable
   * Fix UnicodeDecodeError (Closes: #880182)
   * Updating standards version to 4.1.1.
Checksums-Sha1:
 479b4a7e8ee5679301753299643155a39c635e62 2976 python-os-api-ref_1.4.0-2.dsc
 40dca120ac54bcb2b8ecdc5c67861bf71a9a055e 3864 
python-os-api-ref_1.4.0-2.debian.tar.xz
 f4b419b671a57a2465e3e85159b64e48f3599cef 10819 
python-os-api-ref_1.4.0-2_amd64.buildinfo
Checksums-Sha256:
 a31552c759b196b54e4def1e5bb7154b10bc896953d06da6df5cc7796a64a628 2976 
python-os-api-ref_1.4.0-2.dsc
 26bc8db861faf42f199db5a91c20fab66aa6457efb8496a480930adb9764871a 3864 
python-os-api-ref_1.4.0-2.debian.tar.xz
 abfa8602048a8f363234544c548722dde4168b5aef36accc92408144ac034153 10819 
python-os-api-ref_1.4.0-2_amd64.buildinfo
Files:
 92e835de82c556a2bffedd8c96e1344c 2976 python optional 
python-os-api-ref_1.4.0-2.dsc
 19a6eec1b4977423925a3fb5124decda 3864 python optional 
python-os-api-ref_1.4.0-2.debian.tar.xz
 90c579de8cd4c6719cbb785f3821f9ae 10819 python optional 
python-os-api-ref_1.4.0-2_amd64.buildinfo

Processed: Forwarded

[Debian Bug Tracking System]

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

> forwarded 876921 https://github.com/hgrecco/pint/issues/577
Bug #876921 [src:python-pint] python-pint FTBFS with python-numpy 1.13.1: test 
failures
Set Bug forwarded-to-address to 'https://github.com/hgrecco/pint/issues/577'.
> thanks
Stopping processing here.

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

Processed: Bug#880182 marked as pending

[Debian Bug Tracking System]

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

> tag 880182 pending
Bug #880182 [src:python-os-api-ref] python-os-api-ref: FTBFS: tests fail with 
UnicodeDecodeError
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880470: libswt-webkit-gtk-3-jni: Depend on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

Package: libswt-webkit-gtk-3-jni
Version: 3.8.2-4.2
X-Debbugs-CC: b...@debian.org
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

The recent swt-gtk/3.8.2-4.2 NMU fixed an RC bug by introducing
another RC bug. I'm a bit upset because it also clobbered my 3.8.2-4.1
NMU one day before it was going to migrate to testing and I was not
CC'd on the 4.2 NMU notice ahead of time.

Because the 4.2 upload introduces a RC bug, it can't migrate to
testing unless this RC bug is ignored. So the question for the Release
Team will be which RC bug to ignore: https://bugs.debian.org/879170 or
this one.

Note that libswt-webkit-gtk-3-jni has only one direct reverse
dependency, eclipse-rcp. But my initial analysis at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681726#130 shows
that it isn't really practical to remove eclipse-rcp from testing
because of the huge number of reverse depends.

See also https://bugs.debian.org/879228 for libswt-webkit-gtk-4-jni
which only has one reverse-dependency, tuxguitar, so it is solvable by
either removing that library and tuxguitar or fixing its webkit2gtk
support. Either way, I don't think that needs to be a blocker to
webkitgtk's removal.



libswt-webkit-gtk-3-jni depends on libwebkitgtk-1.0-0, which is
deprecated in favor of libwebkit2gtk-4.0-37 (provided in Debian by
webkit2gtk). Please drop this dependency so that we can remove the
old, unmaintained one.

Please try to do soon as this is the final package blocking the
webkitgtk removal!

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

If you have any question don't hesitate to ask.

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Processed: block 879738 with 880460

[Debian Bug Tracking System]

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

> block 879738 with 880460
Bug #879738 [release.debian.org] transition: gnustep-base
879738 was not blocked by any bugs.
879738 was not blocking any bugs.
Added blocking bug(s) of 879738: 880460
> thanks
Stopping processing here.

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

Processed: forcibly merging 876592 880238

[Debian Bug Tracking System]

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

> forcemerge 876592 880238
Bug #876592 [src:gconf] gconf FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is 
no longer available
Bug #880238 [src:gconf] gconf: FTBFS: gconf.c:833: Error: GConf: encountered 
multiple return value parameters or tags for "gconf_engine_notify_add".
Merged 876592 880238
> thanks
Stopping processing here.

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

Bug#880236: python-biopython: FTBFS: Test failures

[Peter Cock]

The key part of the log
http://aws-logs.debian.net/2017/10/30/python-biopython_1.70+dfsg-2_unstable.log
is this bit:

==
FAIL: test_index (test_BWA_tool.BwaTestCase)
Test for creating index files for the reference genome fasta file
--
Traceback (most recent call last):
  File 
"/<>/python-biopython-1.70+dfsg/.pybuild/pythonX.Y_2.7/build/Tests/test_BWA_tool.py",
line 102, in test_index
% (cmdline, stdout))
AssertionError: FASTA indexing failed:
bwa index -a bwtsw BWA/human_g1k_v37_truncated.fasta
Stdout:

--

This has been reported upstream, and we suspect it is due to a change
in the command line tool bwa:

https://github.com/biopython/biopython/issues/1431

Bug#880449: unison: Uncaught exception Failure("input_value: bad bigarray kind")

[Leandro Noferini]

Package: unison
Version: 2.48.4-1
Followup-For: Bug #880449

I can confirm this bug

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

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

Versions of packages unison depends on:
ii  libc6  2.24-17

Versions of packages unison recommends:
ii  openssh-client [ssh-client]  1:7.6p1-2

Versions of packages unison suggests:
pn  unison-all  

-- no debconf information


signature.asc
Description: PGP signature

Processed: xiphos

[Debian Bug Tracking System]

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

> forwarded 866657 https://github.com/crosswire/xiphos/issues/834
Bug #866657 [src:xiphos] xiphos: depends on libwebkitgtk-3.0-0 which is 
deprecated
Changed Bug forwarded-to-address to 
'https://github.com/crosswire/xiphos/issues/834' from 
'https://github.com/crosswire/xiphos/issues/832'.
> thanks
Stopping processing here.

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

Bug#880404: quantlib-examples: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/CVAIRS

[Andreas Beckmann]

Package: quantlib-examples
Version: 1.11-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

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...):

  Preparing to unpack .../quantlib-examples_1.11-2_amd64.deb ...
  Unpacking quantlib-examples (1.11-2) over (1.9.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/quantlib-examples_1.11-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/CVAIRS', which is also in package 
libquantlib0v5 1.9.1-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../libquantlib0v5_1.11-2_amd64.deb ...
  Unpacking libquantlib0v5 (1.11-2) over (1.9.1-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/quantlib-examples_1.11-2_amd64.deb


cheers,

Andreas


quantlib-examples_1.11-2.log.gz
Description: application/gzip

Processed: affects 880216, affects 880217, affects 880214

[Debian Bug Tracking System]

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

> affects 880216 + simgrid-java
Bug #880216 [libsimgrid3.17] libsimgrid3.17: fails to upgrade from 'testing' - 
trying to overwrite /usr/bin/smpimain
Added indication that 880216 affects simgrid-java
> affects 880217 + ansible-tower-cli
Bug #880217 [ansible-tower-cli-doc] ansible-tower-cli-doc: fails to upgrade 
from 'testing' - trying to overwrite 
/usr/share/doc/ansible-tower-cli/CONFIG_CMD_OPTIONS.md.gz
Added indication that 880217 affects ansible-tower-cli
> affects 880214 + libgmsh-dev
Bug #880214 [libjava-gmsh3] libjava-gmsh3: fails to upgrade from 'testing' - 
trying to overwrite /usr/lib/x86_64-linux-gnu/libjava-gmsh.so
Added indication that 880214 affects libgmsh-dev
> thanks
Stopping processing here.

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

Bug#880313: marked as done (itools: FTBFS: make[2]: *** No rule to make target 'debinstall'. Stop.)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 09:20:33 +
with message-id 
and subject line Bug#880313: fixed in itools 1.0-6
has caused the Debian Bug report #880313,
regarding itools: FTBFS: make[2]: *** No rule to make target 'debinstall'. Stop.
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.)


-- 
880313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: itools
Version: 1.0-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary
> dh: Compatibility levels before 9 are deprecated (level 8 in use)
>dh_testroot
>dh_prep
>dh_installdirs
> dh_installdirs: Compatibility levels before 9 are deprecated (level 8 in use)
>debian/rules override_dh_auto_install
> make[1]: Entering directory '/<>'
> /usr/bin/make debinstall
> make[2]: Entering directory '/<>'
> make[2]: *** No rule to make target 'debinstall'.  Stop.
> make[2]: Leaving directory '/<>'
> debian/rules:11: recipe for target 'override_dh_auto_install' failed
> make[1]: *** [override_dh_auto_install] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/itools_1.0-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: itools
Source-Version: 1.0-6

We believe that the bug you reported is fixed in the latest version of
itools, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated itools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Oct 2017 09:33:42 +0100
Source: itools
Binary: itools
Architecture: source
Version: 1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Islamic Maintainers 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Description:
 itools - Islamic hijri date and prayer time utilities
Closes: 880313
Changes:
 itools (1.0-6) unstable; urgency=medium
 .
   * Bump compat level to 10
   * Update standards version to 4.1.1
   * Changed Vcs-* fields to secure  URLs
   * Added autoconf.diff patch to add autoconf tiles (Closes: #880313)
 + Removed fix_link_libs_placement.diff and use_CPPFLAGS.diff patches, no
   longer needed
 + debian/rules: removed overrides
   * Add fix_spelling.diff patch to fix spelling errors
Checksums-Sha1:
 f5efad00f58d3f2e39f2a0ae186ddc447c679ee5 1609 itools_1.0-6.dsc
 b5ab9f7dc457c7427b992aedd6ddfe1668dc8797 5288 itools_1.0-6.debian.tar.xz
Checksums-Sha256:
 fb0785998acf581c12fb11d65802fc12193a021fbd2237c1e3250fe5748b4a96 1609 
itools_1.0-6.dsc
 54972b9aa953e2da1ddb9fed0bdaec2a528060dd40b7d0dbed8b27e867d9150e 5288 
itools_1.0-6.debian.tar.xz
Files:
 4cfd407f4d1b2aa28cd80d978139a81f 1609 misc optional itools_1.0-6.dsc
 7c4352aa1965248a65a6f122a7820895 5288 misc optional itools_1.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJZ+DWUAAoJELwZapTt3aG3sW0IALpdXuPQEmJqMtavd/G2TIB1
/sBmJlXpPlPZRaK3uZQXTG9eBh8XPOjJLdFxpstSUlZ/N0pkD7zznDmlc/6beSIn
SwTqKcYeUiYbBA6tZARVzkTnEdxMBL6W8nU/BvkvIgvZvoinGovAvknpwZZ/BR+B
j+xXg6uR44x39XaTWAE+b1KUYgFTPicXA2OIQd0NtJTh+/II2lLVtqktL7qRZUeJ
YhjjmUE4xLRY6Wk2P7IOWcUDKbPms9HBs7eioPMU35iEqK5Lka1D0sr9IQ9A7+Oq
QBnn7zgBCaRhwmrnVos24Az7Co+Gvs3vE2eff9tUbiFgvGofTS9OFUKH9yyb2gA=
=G+qO
-END PGP SIGNATURE End Message ---

Bug#880399: python-oslo.vmware: FTBFS: exception: No module named openstackdocstheme

[Andreas Beckmann]

Source: python-oslo.vmware
Version: 2.23.0-3
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.vmware/experimental FTBFS in a minimal sid+experimental
environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.vmware-2.23.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
PYTHONPATH=. sphinx-build -b html doc/source 
debian/python-oslo.vmware-doc/usr/share/doc/python-oslo.vmware-doc/html
Running Sphinx v1.6.5
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt

Extension error:
Could not import extension openstackdocstheme (exception: No module named 
openstackdocstheme)
debian/rules:35: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 1
make[1]: Leaving directory '/build/python-oslo.vmware-2.23.0'


Andreas

PS: with this bug report I've finished processing my recent full
rebuild of experimental on amd64 and i386 :-)


python-oslo.vmware_2.23.0-3.log.gz
Description: application/gzip

Processed: Re-add the found version

[Debian Bug Tracking System]

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

> found 879063 1.8.18-4
Bug #879063 [ipmitool] [dh_system_enable] don't notice the debhelper naming 
convention
Marked as found in versions ipmitool/1.8.18-4.
> thanks
Stopping processing here.

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

Bug#879883: marked as done (libx32stdc++6-8-dbg: missing Conflicts: libx32stdc++6-7-dbg)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 09:02:20 +
with message-id <e1e9sra-000eei...@fasolo.debian.org>
and subject line Bug#879883: fixed in gcc-8 8-20171031-1
has caused the Debian Bug report #879883,
regarding libx32stdc++6-8-dbg: missing Conflicts: libx32stdc++6-7-dbg
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.)


-- 
879883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libx32stdc++6-8-dbg
Version: 8-20171023-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi doko,

the last round of adding Conflicts seems to have missed this one:

  Selecting previously unselected package libx32stdc++6-8-dbg.
  Preparing to unpack .../15-libx32stdc++6-8-dbg_8-20171023-1_amd64.deb ...
  Unpacking libx32stdc++6-8-dbg (8-20171023-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ntuDRD/15-libx32stdc++6-8-dbg_8-20171023-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/libx32/debug/libstdc++.a', which is also in 
package libx32stdc++6-7-dbg 7.2.0-12
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ntuDRD/15-libx32stdc++6-8-dbg_8-20171023-1_amd64.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: gcc-8
Source-Version: 8-20171031-1

We believe that the bug you reported is fixed in the latest version of
gcc-8, 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 879...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <d...@debian.org> (supplier of updated gcc-8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 31 Oct 2017 02:22:07 +0100
Source: gcc-8
Binary: gcc-8-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-8-dev libgcc4 
libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-8-dev lib32gcc1 lib32gcc1-dbg 
lib32gcc-8-dev libn32gcc1 libn32gcc1-dbg libn32gcc-8-dev libx32gcc1 
libx32gcc1-dbg libx32gcc-8-dev gcc-8 gcc-8-multilib gcc-8-test-results 
gcc-8-plugin-dev gcc-8-hppa64-linux-gnu cpp-8 gcc-8-locales g++-8 
g++-8-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 
lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 
libitm1-dbg lib32itm1 lib32itm1-dbg lib64itm1 lib64itm1-dbg libx32itm1 
libx32itm1-dbg libatomic1 libatomic1-dbg lib32atomic1 lib32atomic1-dbg 
lib64atomic1 lib64atomic1-dbg libn32atomic1 libn32atomic1-dbg libx32atomic1 
libx32atomic1-dbg libasan5 libasan5-dbg lib32asan5 lib32asan5-dbg lib64asan5 
lib64asan5-dbg libx32asan5 libx32asan5-dbg liblsan0 liblsan0-dbg lib32lsan0 
lib32lsan0-dbg libx32lsan0 libx32lsan0-dbg libtsan0 libtsan0-dbg libubsan1 
libubsan1-dbg lib32ubsan1
 lib32ubsan1-dbg lib64ubsan1 lib64ubsan1-dbg libx32ubsan1 libx32ubsan1-dbg 
libcilkrts5 libcilkrts5-dbg lib32cilkrts5 lib32cilkrts5-dbg lib64cilkrts5 
lib64cilkrts5-dbg libx32cilkrts5 libx32cilkrts5-dbg libmpx2 libmpx2-dbg 
lib32mpx2 lib32mpx2-dbg lib64mpx2 lib64mpx2-dbg libquadmath0 libquadmath0-dbg 
lib32quadmath0 lib32quadmath0-dbg lib64quadmath0 lib64quadmath0-dbg 
libx32quadmath0 libx32quadmath0-dbg libcc1-0 libgccjit0 libgccjit0-dbg 
libgccjit-8-doc libgccjit-8-dev gobjc++-8 gobjc++-8-multilib gobjc-8 
gobjc-8-multilib libobjc-8-dev lib64objc-8-dev lib32objc-8-dev libn32objc-8-dev 
libx32objc-8-dev libobjc4 libobjc4-dbg lib64objc4 lib64objc4-dbg lib32objc4 
lib32objc4-dbg libn32objc4 libn32objc4-dbg libx32objc4 libx32objc4-dbg 
gfortran-8 gfortran-8-multilib libgfortran-8-dev lib64gfortran-8-dev 
lib32gfortran-8-dev libn32gfortran-8-dev libx32gfortran-8-dev libgfortran5 
libgfortran5-dbg lib64gfortran5 lib64gfortran5-dbg lib32gfortran5 
lib32gfortran5-dbg libn32gfortran5
 libn32gfortran5-dbg libx32gfortran5 libx32gfortran5-dbg gccgo-8 
gccgo-8-multilib libgo12 libgo12-dbg lib64go12 lib64go12-dbg lib32go12 
lib32go12-dbg libn32go12 libn32go12-dbg libx32go12 libx32go12-dbg libstdc++6 
lib32stdc++6 lib64stdc++6 libn32stdc++6 libx32stdc++6 libstdc++-8-dev 
libstdc++-8-pic libstdc++6-8-dbg lib32stdc++-8-dev lib32stdc++6-8-dbg 
lib64stdc++-8-d

Bug#880403: libuim-dev: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libuim-dev
Version: 1:1.8.6+gh20161003.0.d63dadd-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an dangling symlink.

This was observed on the following upgrade paths:

  buster -> sid

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

0m22.1s ERROR: WARN: Inadequate results from running adequate!
  libuim-dev:amd64: broken-symlink /usr/share/doc/libuim-dev -> uim-common
  libuim-dev:amd64: missing-copyright-file /usr/share/doc/libuim-dev/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libuim-dev/copyright
  # ls -lad /usr/share/doc/libuim-dev
  lrwxrwxrwx 1 root root 10 Aug 16 10:10 /usr/share/doc/libuim-dev -> uim-common
  # ls -la /usr/share/doc/libuim-dev/
  ls: cannot access '/usr/share/doc/libuim-dev/': No such file or directory


In a fresh sid installation, the symlink is different:

  /usr/share/doc/libuim-dev -> libuim8

Looking at the maintainer scripts, there is only a dpkg-maintscript-helper call
in the postinst, but missing from the other scripts.

Please use debian/$PACKAGE.maintscript to generate these commands
in all maintainer scripts where needed, see dh_installdeb(1) for details.
Not sure if this would be sufficient to fix this bug.


cheers,

Andreas


libuim-dev_1:1.8.6+gh20161003.0.d63dadd-7+b1.log.gz
Description: application/gzip

Processed: Bug#880395 marked as pending

[Debian Bug Tracking System]

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

> tag 880395 pending
Bug #880395 [src:python-oslo.cache] python-oslo.cache: FTBFS: no theme named 
'openstackdocs' found (missing theme.conf?)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880396: python-oslo.policy: FTBFS: ModuleNotFoundError: No module named 'sphinx'

[Andreas Beckmann]

Source: python-oslo.policy
Version: 1.25.1-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.policy/experimental FTBFS in a minimal sid+experimental
environment:

==
FAIL: unittest2.loader._FailedTest.oslo_policy.tests.test_sphinxext
unittest2.loader._FailedTest.oslo_policy.tests.test_sphinxext
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: oslo_policy.tests.test_sphinxext
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "/build/python-oslo.policy-1.25.1/oslo_policy/tests/test_sphinxext.py", 
line 20, in 
from oslo_policy import sphinxext
  File "/build/python-oslo.policy-1.25.1/oslo_policy/sphinxext.py", line 24, in 

from sphinx.util.nodes import nested_parse_with_titles
ModuleNotFoundError: No module named 'sphinx'


--
Ran 219 tests in 2.255s

FAILED (failures=1)
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Andreas


python-oslo.policy_1.25.1-1.log.gz
Description: application/gzip

Bug#880398: python-oslo.reports: FTBFS: no theme named 'openstackdocs' found (missing theme.conf?)

[Andreas Beckmann]

Source: python-oslo.reports
Version: 1.22.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.reports/experimental FTBFS in a minimal sid+experimental
environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.reports-1.22.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
sphinx-build -b html doc/source 
debian/python-oslo.reports-doc/usr/share/doc/python-oslo.reports-doc/html
Running Sphinx v1.6.5
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt
loading pickled environment... not yet created

Theme error:
no theme named 'openstackdocs' found (missing theme.conf?)
debian/rules:29: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 1
make[1]: Leaving directory '/build/python-oslo.reports-1.22.0'


Andreas


python-oslo.reports_1.22.0-1.log.gz
Description: application/gzip

Bug#879063: ipmitool FTBFS with debhelper 10.9.2

[Niels Thykier]

Control: reassign -1 ipmitool

On Mon, 30 Oct 2017 22:57:22 +0100
=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?=  wrote:
> reassign 879063 debhelper 10.10.5
> retitle 879063 [dh_system_enable] don't notice the debhelper naming convention
> thanks
> 
> Hi,
> 
> this is not a ipitool bug.
> 
> Fakts: 
> 
> - the service file is debian/ipmitool.ipmievd.service.
>   This fulfill the debhelper naming convention[1].
> 
> - without "dh_systemd_enable --no-enable ipmievd.service" and / or with
>   "dh_systemd_start ipmievd.service" the service file is installed[2]. 
>   This will find the service file.
> 
> Result:
> 
> Its looks like dh_systemd_enable do not notice the debhelper naming
> convention. So I reassign this bug to debhelper.
> 
> CU
> Jörg
> 
> [...]

Hi,

Sorry, but I disagree with your assertion.  :)

While the facts as such are correct, there are two facts missing:

 * When "dh_systemd_enable --no-enable ipmievd.service" is called,
   the service is *not* present in the package directory[1].
   Accordingly, you get that error.

 * The service is currently installed by dh_installinit (see the first
   three lines of [2]).  By design, dh_systemd_enable is run *before*
   dh_installinit (and dh_systemd_start is run after dh_installinit).
   - I admit that this interaction between dh_installinit and
 dh_systemd_* is way more complex than it has to be and we are
 cleaning it up for compat 11. :)

Previously, dh_systemd_enable had a behaviour depending on whether it
could read the service file.  This lead to silent "fail-to-fail"
behaviour where you could end up with a service not being enabled
instead of the build failing.  I can see that ipmitool unfortunately
relied on this "failure to fail" in the build log for stable[3].

The consequences for ipmitool:
If I am reading dh_systemd_enable correctly, it will fail to deliver a
shell snippet for notifying the system that a new service file has been
installed (and re-enable on reinstall if it was enabled prior to
uninstall).

 * While this may sound scary, I /think/ dh_installinit happens to do
  that for you in compat 10.  (Did not check too deeply though)

 * Although, it is not clear to me that your --no-enable is respected at
   all.  If it is, then it is not because of something dh_systemd_enable
   does.

Thanks,
~Niels

[1]
"""
make[1]: Leaving directory '/ipmitool-1.8.18'
   dh_installdocs
   dh_installchangelogs
   dh_installman
   debian/rules override_dh_systemd_enable
make[1]: Entering directory '/ipmitool-1.8.18'
dh_systemd_enable -v --no-enable ipmievd.service
dh_systemd_enable: Requested unit "ipmievd.service" but it was not found
in any package acted on.
dh_systemd_enable: Could not handle all of the requested services
debian/rules:36: recipe for target 'override_dh_systemd_enable' failed
make[1]: *** [override_dh_systemd_enable] Error 2
make[1]: Leaving directory 'ipmitool-1.8.18'
debian/rules:24: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2
/ipmitool-1.8.18$ find debian/ipmitool -type f
debian/ipmitool/usr/bin/ipmitool
debian/ipmitool/usr/sbin/ipmievd
debian/ipmitool/usr/share/man/man1/ipmitool.1
debian/ipmitool/usr/share/man/man8/ipmievd.8
debian/ipmitool/usr/share/ipmitool/oem_ibm_sel_map
debian/ipmitool/usr/share/doc/ipmitool/README
debian/ipmitool/usr/share/doc/ipmitool/AUTHORS
debian/ipmitool/usr/share/doc/ipmitool/copyright
debian/ipmitool/usr/share/doc/ipmitool/changelog.Debian
debian/ipmitool/usr/share/doc/ipmitool/changelog
"""

[2]

"""
$ dh_installinit -v  --name ipmievd --error-handler=ipmievd_initd_failed
install -d debian/ipmitool/lib/systemd/system
install -p -m0644 debian/ipmitool.ipmievd.service
debian/ipmitool/lib/systemd/system/ipmievd.service
install -d debian/ipmitool/etc/default
install -p -m0644 debian/ipmitool.ipmievd.default
debian/ipmitool/etc/default/ipmievd
install -d debian/ipmitool/etc/init.d
install -p -m0755 debian/ipmitool.ipmievd.init
debian/ipmitool/etc/init.d/ipmievd
echo "# Automatically added by dh_installinit/10.10.5">>
debian/ipmitool.postinst.debhelper
sed
"s/#SCRIPT#/ipmievd/g;s/#INITPARMS#/defaults/g;s/#ERROR_HANDLER#/ipmievd_initd_failed/g"
/usr/share/debhelper/autoscripts/postinst-init-restart >>
debian/ipmitool.postinst.debhelper
echo '# End automatically added section' >>
debian/ipmitool.postinst.debhelper
echo "# Automatically added by dh_installinit/10.10.5">>
debian/ipmitool.prerm.debhelper
sed
"s/#SCRIPT#/ipmievd/g;s/#INITPARMS#/defaults/g;s/#ERROR_HANDLER#/ipmievd_initd_failed/g"
/usr/share/debhelper/autoscripts/prerm-init-norestart >>
debian/ipmitool.prerm.debhelper
echo '# End automatically added section' >>
debian/ipmitool.prerm.debhelper
echo "# Automatically added by dh_installinit/10.10.5">>
debian/ipmitool.postrm.debhelper
sed

Processed: Re: Bug#879063: ipmitool FTBFS with debhelper 10.9.2

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ipmitool
Bug #879063 [debhelper] [dh_system_enable] don't notice the debhelper naming 
convention
Bug reassigned from package 'debhelper' to 'ipmitool'.
No longer marked as found in versions debhelper/10.10.5.
Ignoring request to alter fixed versions of bug #879063 to the same values 
previously set

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

Bug#879170: marked as done (libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 07:49:30 +
with message-id 
and subject line Bug#879170: fixed in swt-gtk 3.8.2-4.2
has caused the Debian Bug report #879170,
regarding libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
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.)


-- 
879170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swt-gtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

swt-gtk Build-Depends on libwebkitgtk-dev, which is deprecated in favor of
libwebkit2gtk-4.0-dev (provided in Debian by webkit2gtk). Please drop
this Build-Depends so that we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

The package does build successfully without the libwebkitgtk-dev
build-dependency.

It feels to me like the libswt-webkit-gtk-3-jni was already broken
since it doesn't have a dependency on any webkitgtk library (I think
the correct one would be libwebkitgtk-3.0-0 but that is still part of
the deprecated libraries which are being removed.)

If you have any question don't hesitate to ask.

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: swt-gtk
Source-Version: 3.8.2-4.2

We believe that the bug you reported is fixed in the latest version of
swt-gtk, 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 879...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated swt-gtk 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, 29 Oct 2017 08:52:32 +0200
Source: swt-gtk
Binary: libswt-gtk-3-java libswt-gtk-3-jni libswt-gnome-gtk-3-jni 
libswt-cairo-gtk-3-jni libswt-glx-gtk-3-jni libswt-webkit-gtk-3-jni
Architecture: source
Version: 3.8.2-4.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Adrian Bunk 
Description:
 libswt-cairo-gtk-3-jni - Standard Widget Toolkit for GTK+ Cairo JNI library
 libswt-glx-gtk-3-jni - Standard Widget Toolkit for GTK+ GLX JNI library
 libswt-gnome-gtk-3-jni - Standard Widget Toolkit for GTK+ GNOME JNI library
 libswt-gtk-3-java - Standard Widget Toolkit for GTK+ Java library
 libswt-gtk-3-jni - Standard Widget Toolkit for GTK+ JNI library
 libswt-webkit-gtk-3-jni - Standard Widget Toolkit for GTK+ WebKit JNI library
Closes: 879170
Changes:
 swt-gtk (3.8.2-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * libswt-webkit-gtk-3-jni: Add the missing dependency
 on libwebkitgtk-1.0-0. (Closes: #879170)
Checksums-Sha1:
 bed09d4d924212b8808bcd4f1f00d7da075a29af 2665 swt-gtk_3.8.2-4.2.dsc
 8f9d5ef4e5148bc6e3f1569d0a5c8603c64fe683 263452 swt-gtk_3.8.2-4.2.debian.tar.xz
Checksums-Sha256:
 3188fffaa0ecf62c2861548e5aed2026db09b737c5f9b8093541997e1230760b 2665 
swt-gtk_3.8.2-4.2.dsc
 db2299906538b9e23dccd33350b5062528b070e26f9a1a3513d2c34c6ad2cda6 263452 
swt-gtk_3.8.2-4.2.debian.tar.xz
Files:
 74e28a66961f1fd8e7538a010b6beab9 2665 libs optional swt-gtk_3.8.2-4.2.dsc
 33e1f438e8ab6892e5ce937aa70845b3 263452 libs optional 
swt-gtk_3.8.2-4.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAln1fOgACgkQiNJCh6LY
mLEjPRAAqyptC/6tSAoSVy/PTBr2f7FaFxpmoV6BH9rvUcc4kaz9p9alSlROSLB6
Q6INBIklf+uAHfU8/YDdPbD6YtZKTTQWioKf8XPSUIYNknqyrZbd1MN6/NLBNPTZ
/eQ4Rz7jLoIeiwA8DJcllG1PN826INFzktSKJ/o4pljDlxCU00WzTjofSSc8TeL6
L70k58eWrTQ2OnfU1t6Sk3SgbUwqrxSHmkRToeO3tnc7dnQHzne4CBGoaSbRGDPG
vyIw+/GPyL4TmjJW9/n9JOxkssJJtFEtHXE3l/FTe1Eun43DQmMXnJSGq6DZbYv3
c8vjsnPsbpv84OoL9Ui4Oe7ObYOkqbLlqzXGo+FrzYH+2k6tKbqJ7Gwq2VkmKo+7
RFvznGJeDIorBM6F68Un0VlxU9UTl6KJzfU2xYzI4dVnu1N3JEFHm8jo0udhdO7Q
Udfhh0sj9stBxerRigGtmmifBSUMOs/tUy0VtzZishvFKg/pc/MH3hTila1ikRBJ

Bug#784462: marked as done ([fcitx-libpinyin] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 06:18:52 +
with message-id 
and subject line Bug#784462: fixed in fcitx-libpinyin 0.5.2-1~exp1
has caused the Debian Bug report #784462,
regarding [fcitx-libpinyin] Qt4's WebKit removal
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.)


-- 
784462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fcitx-libpinyin
Version: 0.3.1-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear IME Packaging Team ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: fcitx-libpinyin
Source-Version: 0.5.2-1~exp1

We believe that the bug you reported is fixed in the latest version of
fcitx-libpinyin, 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 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated fcitx-libpinyin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Sep 2017 22:22:25 +0800
Source: fcitx-libpinyin
Binary: fcitx-libpinyin
Architecture: source
Version: 0.5.2-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: Shengjing Zhu 
Description:
 fcitx-libpinyin - Fcitx wrapper for libpinyin
Closes: 784462
Changes:
 fcitx-libpinyin (0.5.2-1~exp1) experimental; urgency=medium
 .
   * Team upload
   * Import Upstream version 0.5.2
   * Update outdated url
   * d/control:
 + Update Build-Depends
   Drop libqtwebkit-dev, add qtwebengine5-dev (Closes: #784462)
   Bump to libpinyin13-dev
 + Update Standards-Version to 4.1.0
Checksums-Sha1:
 bc2f04f19104f78d95b50ada698905491b35fe01 1859 fcitx-libpinyin_0.5.2-1~exp1.dsc
 51976e8db061b33f609e284dd4b18ef9a9f87ba2 56726 
fcitx-libpinyin_0.5.2.orig.tar.gz
 456e25e03e6a0ea1ff237e5ab061f94c68d69390 2204 
fcitx-libpinyin_0.5.2-1~exp1.debian.tar.xz
 e9bf5f50a2516d3eefcd90e2d007396b14ca19ab 11276 
fcitx-libpinyin_0.5.2-1~exp1_source.buildinfo
Checksums-Sha256:
 f5dcf3bdf11b7539fe45de7480c2cf58149d90637aeeea8a3a883ce23c401dc7 1859 
fcitx-libpinyin_0.5.2-1~exp1.dsc
 43ad7746c8a46e8789664d415e99a382b0c8624936565b0312a4fac7a82c88b8 56726 
fcitx-libpinyin_0.5.2.orig.tar.gz
 

Processed: Re: Bug#878549: uprightdiff FTBFS with OpenCV 3.2

[Debian Bug Tracking System]

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

> tags 878549 + pending
Bug #878549 [src:uprightdiff] uprightdiff FTBFS with OpenCV 3.2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#878549: uprightdiff FTBFS with OpenCV 3.2

[Kunal Mehta]

tags 878549 + pending
thanks

This has been fixed upstream, and I've asked my sponsor to review and
upload the new version.

-- Kunal



signature.asc
Description: OpenPGP digital signature

Bug#880379: marked as done (texlive-latex-extra: must not have 'Recommends' for packages outside main)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 07:28:34 +
with message-id 
and subject line Bug#880379: fixed in texlive-extra 2017.20171031-1
has caused the Debian Bug report #880379,
regarding texlive-latex-extra: must not have 'Recommends' for packages outside 
main
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.)


-- 
880379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2017.20171004-1
Severity: serious
Justification: Policy 2.2.1: must not require or recommend a package outside of 
main for compilation or execution

Dear Maintainer,

texlive-latex-extra currently delcares the following relationship:

Package: texlive-latex-extra
Version: 2017.20171004-1
Recommends: icc-profiles, …

As per Policy §2.2.1, packages in main must not require or recommend a
package outside of main for compilation or execution (thus, the package
must not declare a Pre-Depends, Depends, Recommends, Build-Depends,
Build-Depends-Indep, or Build-Depends-Arch relationship on a non-main package
unless that package is only listed as a non-default alternative for a package
in main),

https://www.debian.org/doc/debian-policy/#the-main-archive-area

(this is a separate issue and different severity to dangling symlinks or
missing ICC profiles so filing a separate bug to track it)

With regards the ICC profile, if the only restriction on including the profile
is that it needs to be renamed if modified, then that is potentially fine
according to DSFG#4. Avoiding the inclusion of duplicate files in different
packages still has merits, obviously.

regards
Stuart
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2017.20171031-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Oct 2017 10:41:00 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-plain-generic texlive-latex-extra 
texlive-fonts-extra texlive-music texlive-games texlive-pstricks 
texlive-publishers texlive-humanities texlive-science texlive-fonts-extra-doc 
texlive-humanities-doc texlive-latex-extra-doc texlive-science-doc 
texlive-pstricks-doc texlive-publishers-doc
Architecture: source all
Version: 2017.20171031-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-generic - TeX Live: Plain (La)TeX packages
 texlive-pstricks - TeX Live: PSTricks
 texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
 texlive-publishers - TeX Live: Publisher styles, theses, etc.
 texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
 texlive-science - TeX Live: Mathematics, natural sciences, computer science 
package
 texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 877682 880379
Changes:
 texlive-extra (2017.20171031-1) unstable; urgency=medium
 .
   * new upstream checkout
  

Bug#880395: python-oslo.cache: FTBFS: no theme named 'openstackdocs' found (missing theme.conf?)

[Andreas Beckmann]

Source: python-oslo.cache
Version: 1.25.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.cache/experimental FTBFS in a minimal sid+experimental
environment:

   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/python-oslo.cache-1.25.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
sphinx-build -b html doc/source 
debian/python-oslo.cache-doc/usr/share/doc/python-oslo.cache-doc/html
Running Sphinx v1.6.5
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt
loading pickled environment... not yet created

Theme error:
no theme named 'openstackdocs' found (missing theme.conf?)
debian/rules:19: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 1
make[1]: Leaving directory '/build/python-oslo.cache-1.25.0'


Andreas


python-oslo.cache_1.25.0-1.log.gz
Description: application/gzip

Bug#880275: marked as pending

[Rene Engelhard]

tag 880275 pending
thanks

Hello,

Bug #880275 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-openoffice/libetonyek.git/commit/?id=3122e4a

---
commit 3122e4a729fd103d989632e82848bdf67ec4609a
Author: Rene Engelhard 
Date:   Tue Oct 31 11:38:40 2017 +0100

update changelog

diff --git a/debian/changelog b/debian/changelog
index df114f5..76acd01 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libetonyek (0.1.7-2) unstable; urgency=medium
+
+  * add liblangtag-dev to libetonyek-devs Depends: (closes: #880275)
+
+ -- Rene Engelhard   Tue, 31 Oct 2017 11:38:13 +0100
+
 libetonyek (0.1.7-1) unstable; urgency=medium
 
   * New upstream version 0.1.7

Processed: set git pushed bugs as pending

[Debian Bug Tracking System]

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

> tags 880180 +pending
Bug #880180 [src:python-searchlightclient] python-searchlightclient: missing 
B-D: openstack-pkg-tools
Added tag(s) pending.
> tags 880188 +pending
Bug #880188 [src:python-oslo.middleware] python-oslo.middleware: FTBFS: Could 
not import extension openstackdocstheme
Added tag(s) pending.
> tags 880190 +pending
Bug #880190 [src:python-karborclient] python-karborclient: missing B-D: 
openstack-pkg-tools
Added tag(s) pending.
> tags 880225 +pending
Bug #880225 [src:barbican] barbican: missing B-D: python{3,}-pep8
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: Bug#880275 marked as pending

[Debian Bug Tracking System]

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

> tag 880275 pending
Bug #880275 [libetonyek-dev] missing dependency on liblangtag-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880409: python-django: add Breaks: openstack-dashboard (<< 3:12)

[Andreas Beckmann]

Hi,

On 10/31/2017 11:09 AM, Chris Lamb wrote:
>> Please add a
>>
>> Breaks: openstack-dashboard (<< 3:12)
> 
> This seems like the wrong way around - can't openstack-dashboard (or
> something on "that" side, I'm avoiding the detials…) be changed instead? :)

> Kinda smells wrong to me to add the exception here.

Oh, #867254 was only filed for the "trivial" case in sid. But the
problem also occurs on upgrades from stretch (openstack-dashboard gets
triggered after python-django was upgraded and blows up), which is the
case we need the Breaks for.

https://piuparts.debian.org/stretch2buster/fail/openstack-dashboard_None.log


Andreas

Bug#785562: Status update

[Dr. Tobias Quathamer]

Hi,

I've just uploaded openshot-qt to Debian, it's sitting in the NEW queue.
Once it's accepted, I plan to remove openshot from Debian, so that this
bug can be resolved.

Also, as I understand it, pygoocanvas could then be removed as well.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#880222: marked as done (courier-imap: couriertcpd running as root while listening on port 143)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 11:51:02 +0100
with message-id 
and subject line Re: Bug#880222: courier-imap: couriertcpd running as root 
while listening on port 143
has caused the Debian Bug report #880222,
regarding courier-imap: couriertcpd running as root while listening on port 143
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.)


-- 
880222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-imap
Version: 4.17.2+0.76.3-5
Severity: grave
Tags: security
Justification: user security hole

Dear Marcus,

couriertcpd runs as root instead of the courier user for IMAP connections. 
I've not found (nor looked for) any exploit, but I think running as root while 
listening on a network socket is a security risk of its own.

Please have a look here: 
https://sourceforge.net/p/courier/mailman/message/36096805/

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (990, 'stable'), (600, 'unstable'), (400, 'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages courier-imap depends on:
ii  courier-authlib 0.66.4-9
ii  courier-base0.76.3-5
ii  courier-mta [mail-transport-agent]  0.76.3-5
ii  debconf [debconf-2.0]   1.5.61
ii  init-system-helpers 1.48
ii  libc6   2.24-11+deb9u1
ii  libcourier-unicode1 1.4-3+b1
ii  libgamin0 [libfam0] 0.1.10-5+b1
ii  libgdbm31.8.3-14
ii  libidn111.33-1
ii  sysvinit-utils  2.88dsf-59.9

courier-imap recommends no packages.

Versions of packages courier-imap suggests:
ii  courier-doc  0.76.3-5
pn  imap-client  

-- Configuration Files:
/etc/courier/imapd changed:
ADDRESS=0
PORT=143
MAXDAEMONS=120
MAXPERIP=200
PIDFILE=/run/courier/imapd.pid
TCPDOPTS="-nodnslookup -noidentlookup"
IMAPACCESSFILE=/etc/courier/imapaccess
LOGGEROPTS="-name=imapd"
IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT 
THREAD=REFERENCES SORT QUOTA IDLE"
IMAP_KEYWORDS=1
IMAP_ACL=1
IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 
AUTH=CRAM-SHA256 IDLE"
IMAP_PROXY=0
IMAP_PROXY_FOREIGN=0
IMAP_IDLE_TIMEOUT=60
IMAP_MAILBOX_SANITY_CHECK=1
IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"
IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"
IMAP_DISABLETHREADSORT=0
IMAP_CHECK_ALL_FOLDERS=0
IMAP_OBSOLETE_CLIENT=0
IMAP_UMASK=022
IMAP_ULIMITD=131072
IMAP_USELOCKS=1
IMAP_SHAREDINDEXFILE=/etc/courier/shared/index
IMAP_ENHANCEDIDLE=0
IMAP_TRASHFOLDERNAME=Trash
IMAP_EMPTYTRASH=Trash:7
IMAP_MOVE_EXPUNGE_TO_TRASH=0
SENDMAIL=/usr/sbin/sendmail
HEADERFROM=X-IMAP-Sender
IMAPDSTART=YES
MAILDIRPATH=Maildir

/etc/courier/imapd-ssl changed:
SSLPORT=993
SSLADDRESS=0
SSLPIDFILE=/run/courier/imapd-ssl.pid
SSLLOGGEROPTS="-name=imapd-ssl"
IMAPDSSLSTART=YES
IMAPDSTARTTLS=YES
IMAP_TLS_REQUIRED=0
COURIERTLS=/usr/bin/couriertls
TLS_CIPHER_LIST="ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES128-SHA:DES-CBC3-SHA"
TLS_CERTFILE=/etc/courier/imapd.pem
TLS_DHPARAMS=/etc/courier/dhparams.pem
TLS_TRUSTCERTS=/etc/ssl/cert.pem
TLS_VERIFYPEER=NONE
TLS_CACHEFILE=/var/lib/courier/couriersslcache
TLS_CACHESIZE=524288
MAILDIRPATH=Maildir

/etc/courier/imapd.cnf [Errno 13] Permission denied: '/etc/courier/imapd.cnf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 +wontfix
Control: notfound -1 0.76.3-5

On 10/30/2017 07:19 PM, Lucio Crusca wrote:
> couriertcpd runs as root instead of the courier user for IMAP
> connections.
> I've not found (nor looked for) any exploit, but I think running as
> root while listening on a network socket is a security risk of its
> own.

The first 1024 ports are privileged and reserved for the root user, so
only root can open them. Most services drop privileges after that.

On 10/31/2017 07:19 AM, Lucio Crusca wrote:
> Il 30/10/2017 22:59, Sam Varshavchik ha scritto:
>> The process UIDs are correct. The IMAP server 

Bug#880275: marked as done (missing dependency on liblangtag-dev)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 11:04:44 +
with message-id 
and subject line Bug#880275: fixed in libetonyek 0.1.7-2
has caused the Debian Bug report #880275,
regarding missing dependency on liblangtag-dev
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
> dh_install --sourcedir=debian/tmp
> dh_install: Cannot find (any matches for) "usr/bin/key2odp" (tried in 
> debian/tmp, debian/tmp)
> 
> dh_install: key2odp missing files: usr/bin/key2odp
> dh_install: Cannot find (any matches for) "usr/bin/pages2odt" (tried in 
> debian/tmp, debian/tmp)
> 
> dh_install: pages2odt missing files: usr/bin/pages2odt
> dh_install: Cannot find (any matches for) "usr/bin/numbers2ods" (tried in 
> debian/tmp, debian/tmp)
> 
> dh_install: numbers2ods missing files: usr/bin/numbers2ods
> dh_install: Cannot find (any matches for) "usr/bin/pages2epub" (tried in 
> debian/tmp, debian/tmp)
> 
> dh_install: pages2epub missing files: usr/bin/pages2epub
> dh_install: missing files, aborting
> debian/rules:49: recipe for target 'install' failed
> make: *** [install] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/writerperfect_0.9.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libetonyek
Source-Version: 0.1.7-2

We believe that the bug you reported is fixed in the latest version of
libetonyek, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libetonyek package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 31 Oct 2017 11:38:13 +0100
Source: libetonyek
Binary: libetonyek-dev libetonyek-0.1-1
Architecture: source
Version: 0.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Description:
 libetonyek-0.1-1 - library for reading and converting Apple Keynote 
presentations
 libetonyek-dev - library for reading and converting Apple Keynote presentations
Closes: 880275
Changes:
 libetonyek (0.1.7-2) unstable; urgency=medium
 .
   * add liblangtag-dev to libetonyek-devs Depends: (closes: #880275)
Checksums-Sha1:
 1b9241bb6e401d8c65ac918d5cebfc06f4337d0b 2081 libetonyek_0.1.7-2.dsc
 6f318f2cf16b361ec4761e10a6f14aae0e6fe6ca 7708 libetonyek_0.1.7-2.debian.tar.xz
 b755f02b7ab32ae3b36835559e50983b09b413dc 6670 
libetonyek_0.1.7-2_source.buildinfo
Checksums-Sha256:
 7a4b6bda33a087196171fe99fc72cabc4994425f74ddf68e96ad11c1e065792d 2081 
libetonyek_0.1.7-2.dsc
 35d5a69e00c69cfc8686ca3d1359fc01993941c2ba0011324f0f011aa09bdf3b 7708 
libetonyek_0.1.7-2.debian.tar.xz
 ea4b60c942ecaa19e13e997ec1ef95cd49024ad2620f7b1876641d915d4acbeb 6670 
libetonyek_0.1.7-2_source.buildinfo
Files:
 f7fb50341c0a212f01e32b225f5db773 2081 libs optional libetonyek_0.1.7-2.dsc
 f051bc8e3546f7442fcac5eed66b4d04 7708 libs optional 
libetonyek_0.1.7-2.debian.tar.xz
 ae07a0d6823412bbadff2c361044b834 6670 libs optional 
libetonyek_0.1.7-2_source.buildinfo

Bug#876578: marked as done (libykneomgr FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2017 11:04:49 +
with message-id 
and subject line Bug#876578: fixed in libykneomgr 0.1.8-2.1
has caused the Debian Bug report #876578,
regarding libykneomgr FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


-- 
876578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libykneomgr
Version: 0.1.8-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libykneomgr.html

...
Making all in gtk-doc
make[3]: Entering directory '/build/1st/libykneomgr-0.1.8/gtk-doc'
  DOC   Scanning header files
  DOC   Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:728: recipe for target 'tmpl-build.stamp' failed
make[3]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: libykneomgr
Source-Version: 0.1.8-2.1

We believe that the bug you reported is fixed in the latest version of
libykneomgr, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libykneomgr 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: Sat, 21 Oct 2017 13:08:23 +0300
Source: libykneomgr
Binary: libykneomgr0 libykneomgr-dev ykneomgr
Architecture: source
Version: 0.1.8-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Authentication Maintainers 

Changed-By: Adrian Bunk 
Description:
 libykneomgr-dev - Yubico YubiKey NEO CCID Manager library development files
 libykneomgr0 - Yubico YubiKey NEO CCID Manager library
 ykneomgr   - Yubico YubiKey NEO CCID Manager tool
Closes: 876578
Changes:
 libykneomgr (0.1.8-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Run gtkdocize to fix FTBFS with gtk-doc-tools 1.26. (Closes: #876578)
Checksums-Sha1:
 0a94457d952635f75fea8f0c9f4d1ba0f6081fef 2147 libykneomgr_0.1.8-2.1.dsc
 58eefa593130eb4c9bd0fae0d9e70eacdaa0fb69 60720 
libykneomgr_0.1.8-2.1.debian.tar.xz
Checksums-Sha256:
 aaf7ebe1b84ffc7e53a955c42680b5fcc713d58c6f1802652dd5502c99890e3e 2147 
libykneomgr_0.1.8-2.1.dsc
 a1fb276735bb8e369a11123d06f338fd72054f4ac337a2f9fb0962cf5ba54b0b 60720 
libykneomgr_0.1.8-2.1.debian.tar.xz
Files:
 cb14eb28bb3df8d932fb5745af1634f9 2147 utils extra libykneomgr_0.1.8-2.1.dsc
 af77ed78c61edcfe032f6a25e219dc89 60720 utils extra 
libykneomgr_0.1.8-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlnrHrIACgkQiNJCh6LY
mLGa7g//WhirU/i2Z60m8Kv5BLRpvXuSh/jESq6Xx6qdYiV8WHx1J2jlBZrzA3jZ
hyY2Cyq0tOxt9uymodGbztHCfPwPwebfJZ/yrlxQXXMkY74pJIwAm09jgQvZk4Rv
4fkAq+mr5Mbi+ahOnFN/DhFPrOYwaB7dQd5zZa7D6+9/S5ahbOBAEWqGcWm131JY
f5nZmZdH8wrtoVQNfVKVeyq7k8A0/heig2nEjemCTGRTGWsyqOmZgy5s31Z9EaUo
MlmlL7PE+WpUBGgUUl72/zY2eoHewbiR0OdQnZAaiVuBfo11oTV8oYoWa+vzpUOv
ESFSYMQ0Uvt4qMzjV1lMnOy+Yp2VGuTQvpSQZZKgoJVlRrHd69zPntUmiv0LPIYk
0o6mDTFwn4+SrMU5hCAfgt2CI4PjlQLgiheRdb+NJ1nZZKhhYYsSv/iEyKopSmVK
EI5xr9ty+opkcx8W+JdRz/fn99wwPViduuGzMcBNMnEEz+jJyQ+9r2aUL4NFuMOD
7PCQk5MBh+o/siqrxP9laChE4etNsCOJ2OxPfUuUbwMp3/oz0lrlVft3BCrCZmo1
LJSVhkETEtEvvjPLoAFasCOzSq447d5xGfqevKZ0ub7fisGDebIe0YzgzjjrC1lT
2meKStFPzZI6Ym3ZNyXx8n8FW47eZ5whhdWiCnUg7f2cl+jJGVQ=
=zRfS
-END PGP SIGNATURE End Message ---

Bug#880417: gir1.2-gpaste-1.0 is missing dependencies (gir sequence not called)

[Laurent Bigonville]

Source: gpaste
Version: 3.26.0-1
Severity: serious

Hi,

It seems that the gir1.2-gpaste-1.0 package is missing dependencies.

This is due to the fact that the build system is not calling the gir
sequence.

Adding '--with gir' to the dh invocation fixes this

Regards,

Laurent Bigonville

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

-- no debconf information

Bug#875688: libreoffice-report-builder: Design view is missing and existing reports won't run

[MAG4 Piemonte]

retitle 875688 Design view is missing and existing reports won't run
tag 875688 - unreproducible
thanks

Hi Rene,
thank you for the really fast solution.
We will test version 6.0 as it will land in testing ...
Regards!

Guido

Processed: Merging qtchooser bugs

[Debian Bug Tracking System]

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

> reassign 880322 qtchooser
Bug #880322 [qt5-qmake-bin] mkvtoolnix: FTBFS: dh_install: missing files, 
aborting
Bug reassigned from package 'qt5-qmake-bin' to 'qtchooser'.
Ignoring request to alter found versions of bug #880322 to the same values 
previously set
Ignoring request to alter fixed versions of bug #880322 to the same values 
previously set
> forcemerge 880159 880223 880322
Bug #880159 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[qtchooser] qtchooser: Make plain "qmake" invocation fail
Bug #880223 [qtchooser] broken setup - links qmake to itself
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 880223 affects qt5-qmake-bin
Marked as fixed in versions qtchooser/64-ga1b6736-4.
Marked as found in versions qtchooser/64-ga1b6736-3.
Added tag(s) buster and sid.
Bug #880322 [qtchooser] mkvtoolnix: FTBFS: dh_install: missing files, aborting
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 880322 affects qt5-qmake-bin
Marked as fixed in versions qtchooser/64-ga1b6736-4.
Marked as found in versions qtchooser/64-ga1b6736-3.
Bug #880159 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[qtchooser] qtchooser: Make plain "qmake" invocation fail
Added tag(s) sid and buster.
Merged 880159 880223 880322
> thanks
Stopping processing here.

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

Processed: forwarded 880396 https://bugs.launchpad.net/oslo.policy/+bug/1728865

[Debian Bug Tracking System]

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

> forwarded 880396 https://bugs.launchpad.net/oslo.policy/+bug/1728865
Bug #880396 [src:python-oslo.policy] python-oslo.policy: FTBFS: 
ModuleNotFoundError: No module named 'sphinx'
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/oslo.policy/+bug/1728865'.
>
End of message, stopping processing here.

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

Bug#880409: python-django: add Breaks: openstack-dashboard (<< 3:12)

[Andreas Beckmann]

Package: python-django
Version: 1:1.11.6-1
Severity: serious

Upgrading python-django from stretch to buster with openstack-dashboard
installed causes trigger processing in openstack-dashboard to fail
(#867254).

Please add a

Breaks: openstack-dashboard (<< 3:12)

to ensure openstack-dashboard gets removed/deconfigured/upgraded first.
The version in experimental (3:12.x) is supposed to work with the newer
python-django.


Andreas

Bug#880396: marked as pending

[Thomas Goirand]

tag 880396 pending
thanks

Hello,

Bug #880396 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/openstack/oslo/python-oslo.policy.git/commit/?id=6573ace

---
commit 6573acebeff7fff69f49093bc5be4d822afc
Author: Thomas Goirand 
Date:   Tue Oct 31 09:35:32 2017 +

Adds python{3,}-oslosphinx as build-depends (Closes: #880396).

diff --git a/debian/changelog b/debian/changelog
index ad06038..48e8974 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-oslo.policy (1.25.1-2) UNRELEASED; urgency=medium
+
+  * Adds python{3,}-oslosphinx as build-depends (Closes: #880396).
+
+ -- Thomas Goirand   Tue, 31 Oct 2017 09:35:06 +
+
 python-oslo.policy (1.25.1-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Processed: Bug#880396 marked as pending

[Debian Bug Tracking System]

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

> tag 880396 pending
Bug #880396 [src:python-oslo.policy] python-oslo.policy: FTBFS: 
ModuleNotFoundError: No module named 'sphinx'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#880398 marked as pending

[Debian Bug Tracking System]

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

> tag 880398 pending
Bug #880398 [src:python-oslo.reports] python-oslo.reports: FTBFS: no theme 
named 'openstackdocs' found (missing theme.conf?)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#880399 marked as pending

[Debian Bug Tracking System]

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

> tag 880399 pending
Bug #880399 [src:python-oslo.vmware] python-oslo.vmware: FTBFS: exception: No 
module named openstackdocstheme
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880399: marked as pending

[Thomas Goirand]

tag 880399 pending
thanks

Hello,

Bug #880399 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/openstack/oslo/python-oslo.vmware.git/commit/?id=0621062

---
commit 062106221da9304526a12c025b4bbebf561ce56a
Author: Thomas Goirand 
Date:   Tue Oct 31 09:49:38 2017 +

Add missing python-openstackdocstheme b-d (Closes: #880399).

diff --git a/debian/changelog b/debian/changelog
index f1839f1..a360c47 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-oslo.vmware (2.23.0-4) UNRELEASED; urgency=medium
+
+  * Add missing python-openstackdocstheme b-d (Closes: #880399).
+
+ -- Thomas Goirand   Tue, 31 Oct 2017 09:49:15 +
+
 python-oslo.vmware (2.23.0-3) experimental; urgency=medium
 
   * Add missing b-d: python3-ddt (Closes: #877614).

Bug#880398: marked as pending

[Thomas Goirand]

tag 880398 pending
thanks

Hello,

Bug #880398 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/openstack/oslo/python-oslo.reports.git/commit/?id=1ffb1be

---
commit 1ffb1be63e28100cc7116451c21fbaa4d985c8e8
Author: Thomas Goirand 
Date:   Tue Oct 31 09:48:22 2017 +

Fixed minimum version for openstackdocstheme (Closes: #880398).

diff --git a/debian/changelog b/debian/changelog
index 6564da0..bf422cf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-oslo.reports (1.22.0-2) UNRELEASED; urgency=medium
+
+  * Fixed minimum version for openstackdocstheme (Closes: #880398).
+
+ -- Thomas Goirand   Tue, 31 Oct 2017 09:47:43 +
+
 python-oslo.reports (1.22.0-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Bug#867254: openstack-dashboard: fails to install: django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 'openstack_auth.User' that has not been installed

[Andreas Beckmann]

Followup-For: Bug #867254

I just filed #880409 against python-django to add

  Breaks: openstack-dashboard (<< 3:12)

to (hopefully) make the upgrade paths work by
removing/deconfiguring/upgrading openstack-dashboard (the stretch
version) first before upgrading python-django (to buster).


Andreas

Processed: Bug#867468 marked as pending

[Debian Bug Tracking System]

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

> tag 867468 pending
Bug #867468 [glance-common] glance-common: purging glance-common deletes 
conffiles owned by glance-store-common
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867468: marked as pending

[Thomas Goirand]

tag 867468 pending
thanks

Hello,

Bug #867468 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/openstack/services/glance.git/commit/?id=1c80f56

---
commit 1c80f5603d6b79c71fb6900d94c9bf70b57511eb
Author: Thomas Goirand 
Date:   Tue Oct 31 10:02:26 2017 +

Do not rm -rf /etc/glance on purge (Closes: #867468).

diff --git a/debian/changelog b/debian/changelog
index 4540ce2..4043e16 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+glance (2:15.0.0-2) UNRELEASED; urgency=medium
+
+  * Do not rm -rf /etc/glance on purge (Closes: #867468).
+
+ -- Thomas Goirand   Tue, 31 Oct 2017 10:02:06 +
+
 glance (2:15.0.0-1) experimental; urgency=medium
 
   [ Daniel Baumann ]

Bug#852923: dojo package debian/watch file

[Robert J. Clay]

This is regarding the debian/watch issue but I am directing it here
because that bug [1] was merged into this one [2].

On Tue, Sep 12, 2017 at 1:07 PM, Robert J. Clay  wrote:
>  The bug is tagged as 'fixed-stream' and I was
> going to try a test build of 1.12.2 (which I had to download manually
> because the current d/watch doesn't appear to work) but that archive
> appears to be missing (at least) the utils directory.

   I did some more investigation (since none of the dojo bugs have had
any followup recently except from me) and found that the archive I
manually downloaded was the wrong one.  Investigating further I found
that the error being seen when the current debian/watch is used is
coming up because the uscan process is not checking in the
subdirectories of the download page and is therefore not finding the
correct archive. (Why it is then trying the 'shrinksafe' archive which
although still being referenced is no longer available, is unclear to
me.)

Further, what I found is that a change to the debian/watch file by the
then maintainer (who, btw, took himself out of the Uploaders list with
the most recent upload) has had the effect of no longer doing the
upstream search correctly and therefore not being able to find the
correct new upstream archive. The difference appearing to be changing
"/release-([\d\.]*)/"   to  "/release-(\d.*)/" in the URL template
part the command, apparently intended to "Support development
versions" according to the 1.11.0~rc3+dfsg-1  debian/changelog where
the change appears to have taken place.  Adding those square brackets
back in allows it to correctly find and then repack the correct new
version of the archive.



-- 
Robert J. Clay
rjc...@gmail.com, j...@rocasa.us
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869864
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852923

Processed: Bug#880087 marked as pending

[Debian Bug Tracking System]

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

> tag 880087 pending
Bug #880087 [glance-store-common] glance-store-common: fails to install: chown: 
cannot access '/etc/glance/rootwrap.conf': No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880087: marked as pending

[Thomas Goirand]

tag 880087 pending
thanks

Hello,

Bug #880087 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/openstack/libs/python-glance-store.git/commit/?id=8a06dd3

---
commit 8a06dd329785ffd0896fdd94101784feffd9b433
Author: Thomas Goirand 
Date:   Tue Oct 31 10:14:09 2017 +

Only modify /etc/glance if files/dirs exist (Closes: #880087).

diff --git a/debian/changelog b/debian/changelog
index ac0021b..2a09ed2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-glance-store (0.22.0-2) UNRELEASED; urgency=medium
+
+  * Only modify /etc/glance if files/dirs exist (Closes: #880087).
+
+ -- Thomas Goirand   Tue, 31 Oct 2017 10:13:46 +
+
 python-glance-store (0.22.0-1) experimental; urgency=medium
 
   [ James Page ]

Bug#866960: libfreetype6: blank line between characters (regression)

[Vincent Lefevre]

On 2017-10-09 04:31:29 +0200, Vincent Lefevre wrote:
> On 2017-10-08 13:38:10 -0700, Mike Miller wrote:
> > I scanned the upstream bug report. I don't really follow all the details
> > yet, but I guess a next step would be to identify packages that may be
> > affected by this change? So far that looks like Pango and Xft?
> 
> and possibly the applications themselves. In the case of xterm,
> it uses the inaccurate, rounded "ascent" and "descent" values of
> FT_Size_Metrics that are passed by FreeType via Xft (set up by
> XftFontOpenPattern). Instead, the accurate values from FT_Face
> should be used. [1] However, I don't know whether Xft provides
> them in some way. They are not in the XftFont structure. [2]
> 
> [1] https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html
> [2] https://linux.die.net/man/3/xft

I've reported bugs against xterm in Debian:

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

and GNU Emacs upstream:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29078

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Bug#873576 marked as pending

[Debian Bug Tracking System]

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

> tag 873576 pending
Bug #873576 [src:ruby-rest-client] ruby-rest-client: FTBFS without network 
access
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880275: writerperfect: FTBFS: dh_install: missing files, aborting

[Rene Engelhard]

tag 880275 + unreproducible
tag 880275 + moreinfo
thanks

Hi,

On Mon, Oct 30, 2017 at 09:05:37PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

Can't reproduce this...

> Relevant part (hopefully):
> > make[3]: Entering directory '/<>'
> > make[3]: Nothing to be done for 'install-exec-am'.
> > make[3]: Nothing to be done for 'install-data-am'.
> > make[3]: Leaving directory '/<>'
> > make[2]: Leaving directory '/<>'
> > make[1]: Leaving directory '/<>'
> > dh_install --sourcedir=debian/tmp
> > dh_install: Cannot find (any matches for) "usr/bin/key2odp" (tried in 
> > debian/tmp, debian/tmp)
> > 
> > dh_install: key2odp missing files: usr/bin/key2odp
> > dh_install: Cannot find (any matches for) "usr/bin/pages2odt" (tried in 
> > debian/tmp, debian/tmp)
> > 
> > dh_install: pages2odt missing files: usr/bin/pages2odt
> > dh_install: Cannot find (any matches for) "usr/bin/numbers2ods" (tried in 
> > debian/tmp, debian/tmp)
> > 
> > dh_install: numbers2ods missing files: usr/bin/numbers2ods
> > dh_install: Cannot find (any matches for) "usr/bin/pages2epub" (tried in 
> > debian/tmp, debian/tmp)
> > 
> > dh_install: pages2epub missing files: usr/bin/pages2epub
> > dh_install: missing files, aborting
> > debian/rules:49: recipe for target 'install' failed
> > make: *** [install] Error 25

So those tools are not built. This is because ..

> The full build log is available from:
>http://aws-logs.debian.net/2017/10/30/writerperfect_0.9.5-1_unstable.log

... this happens in the log:

[...]
checking for EBOOK... yes
checking for ETONYEK... no
checking for FREEHAND... yes
checking for MSPUB... yes
checking for MWAW... yes
checking for PAGEMAKER... yes
checking for STAROFFICE... no
checking for VISIO... yes
checking for WPD... yes
checking for WPG... yes
checking for WPS... yes
checking for ODFGEN... yes
checking for EPUBGEN... yes
checking for RVNGABW... no
[...]
Build configuration:
debug:   no
werror:  yes

Import:
libabw:  yes
libcdr:  yes
libe-book:   yes
libetonyek:  no
libfreehand: yes
[...]

That said, a build here in my uptodate unstable chroot works fine. Same version
of libetonyek:

$ dpkg -l libetonyek-dev
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
 Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name   Version  Architektur  Beschreibung
+++-==---=
ii  libetonyek-dev 0.1.7-1  amd64library for reading and convertin

which is the one installed in your build too, so...

Do you have the config.log output somewhere?

Regards,

Rene

Bug#873576: marked as pending

[Lucas Nussbaum]

tag 873576 pending
thanks

Hello,

Bug #873576 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-rest-client.git/commit/?id=3e029d5

---
commit 3e029d55a592602b94d5c82bf6a19c02ee22e25e
Author: Lucas Nussbaum 
Date:   Tue Oct 31 11:19:59 2017 +0100

Add patches from Steve Langasek  to fix 
network-dependent tests. Closes: 873576

diff --git a/debian/changelog b/debian/changelog
index ab75e5d..1e1802b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+ruby-rest-client (2.0.2-3) unstable; urgency=medium
+
+  * Add patches from Steve Langasek  to fix
+network-dependent tests. Closes: 873576
++ proxy-proof-tests.patch
++ disable-network-tests.patch
+
+ -- Lucas Nussbaum   Tue, 31 Oct 2017 11:21:55 +0100
+
 ruby-rest-client (2.0.2-2) unstable; urgency=medium
 
   [ Antonio Terceiro ]

Processed: Re: Bug#880275: writerperfect: FTBFS: dh_install: missing files, aborting

[Debian Bug Tracking System]

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

> tag 880275 - moreinfo
Bug #880275 [src:writerperfect] writerperfect: FTBFS: dh_install: missing 
files, aborting
Removed tag(s) moreinfo.
> tag 880275 - unreproducible
Bug #880275 [src:writerperfect] writerperfect: FTBFS: dh_install: missing 
files, aborting
Removed tag(s) unreproducible.
> reassign 880275 libetonyek-dev
Bug #880275 [src:writerperfect] writerperfect: FTBFS: dh_install: missing 
files, aborting
Bug reassigned from package 'src:writerperfect' to 'libetonyek-dev'.
No longer marked as found in versions writerperfect/0.9.5-1.
Ignoring request to alter fixed versions of bug #880275 to the same values 
previously set
> retitle 880275 missing dependency on liblangtag-dev
Bug #880275 [libetonyek-dev] writerperfect: FTBFS: dh_install: missing files, 
aborting
Changed Bug title to 'missing dependency on liblangtag-dev' from 
'writerperfect: FTBFS: dh_install: missing files, aborting'.
> affects 880275 src:writerperfect
Bug #880275 [libetonyek-dev] missing dependency on liblangtag-dev
Added indication that 880275 affects src:writerperfect
> found 880275 0.1.7-1
Bug #880275 [libetonyek-dev] missing dependency on liblangtag-dev
Marked as found in versions libetonyek/0.1.7-1.
> thanks
Stopping processing here.

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

Bug#880395: marked as pending

[Thomas Goirand]

tag 880395 pending
thanks

Hello,

Bug #880395 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/openstack/oslo/python-oslo.cache.git/commit/?id=0aaa402

---
commit 0aaa4024a0b2fc14f77dceb6f52419710716b5e3
Author: Thomas Goirand 
Date:   Tue Oct 31 09:34:16 2017 +

Fixed minimum version of openstackdocstheme (Closes: #880395).

diff --git a/debian/changelog b/debian/changelog
index b3e02cc..7d942dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-oslo.cache (1.25.0-2) UNRELEASED; urgency=medium
+
+  * Fixed minimum version of openstackdocstheme (Closes: #880395).
+
+ -- Thomas Goirand   Tue, 31 Oct 2017 09:32:59 +
+
 python-oslo.cache (1.25.0-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Processed: Bug#880374 marked as pending

[Debian Bug Tracking System]

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

> tag 880374 pending
Bug #880374 [manila-api] manila-api: fails to upgrade from 'sid' - trying to 
overwrite /usr/lib/python2.7/dist-packages/manila/__init__.py
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880374: marked as pending

[Thomas Goirand]

tag 880374 pending
thanks

Hello,

Bug #880374 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/openstack/services/manila.git/commit/?id=a17189e

---
commit a17189e41c9d57eba106f73b575a44de3aa5cf1e
Author: Thomas Goirand 
Date:   Tue Oct 31 09:50:23 2017 +

Changelog closes #880374

diff --git a/debian/changelog b/debian/changelog
index deaea3f..4222168 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,7 @@
 manila (1:5.0.1-2) UNRELEASED; urgency=medium
 
   * Do not delete search.html, making build reproducible (Closes: #861896).
-  * Remove /usr/lib from manila-api.
+  * Remove /usr/lib from manila-api (Closes: #880374).
   * Updated pt.po (Closes: #876175).
   * Uploading to unstable:
 - Fixed FTBFS (Closes: #871337).

Bug#880409: python-django: add Breaks: openstack-dashboard (<< 3:12)

[Chris Lamb]

Hi Andreas,

> Please add a
> 
> Breaks: openstack-dashboard (<< 3:12)

This seems like the wrong way around - can't openstack-dashboard (or
something on "that" side, I'm avoiding the detials…) be changed instead? :)

Kinda smells wrong to me to add the exception here.


Regards,

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

Processed: set git pushed bugs as pending

[Debian Bug Tracking System]

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

> tags 877840 +pending
Bug #877840 [src:python-magnumclient] python-magnumclient: FTBFS  ImportError: 
No module named oslo_log, openstackclient.tests.unit
Added tag(s) pending.
> tags 880094 +pending
Bug #880094 [python-zunclient] python-zunclient: missing B-D: 
openstack-pkg-tools
Added tag(s) pending.
> tags 880087 +pending
Bug #880087 [glance-store-common] glance-store-common: fails to install: chown: 
cannot access '/etc/glance/rootwrap.conf': No such file or directory
Ignoring request to alter tags of bug #880087 to the same tags previously set
> tags 880094 +pending
Bug #880094 [python-zunclient] python-zunclient: missing B-D: 
openstack-pkg-tools
Ignoring request to alter tags of bug #880094 to the same tags previously set
>
End of message, stopping processing here.

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

Processed: Re: Bug#880275: writerperfect: FTBFS: dh_install: missing files, aborting

[Debian Bug Tracking System]

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

> tag 880275 + unreproducible
Bug #880275 [src:writerperfect] writerperfect: FTBFS: dh_install: missing 
files, aborting
Added tag(s) unreproducible.
> tag 880275 + moreinfo
Bug #880275 [src:writerperfect] writerperfect: FTBFS: dh_install: missing 
files, aborting
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#880127: marked as pending

[Thomas Goirand]

tag 880127 pending
thanks

Hello,

Bug #880127 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/openstack/services/senlin.git/commit/?id=44ea37d

---
commit 44ea37d22644ba4a6a71178d9c32216ca4dc298f
Author: Thomas Goirand 
Date:   Tue Oct 31 10:38:06 2017 +

Fixed minimum version of python-docker (Closes: #880127).

diff --git a/debian/changelog b/debian/changelog
index 2bd2bbd..2fa6a9c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,11 @@
-senlin (4.0.0-2) UNRELEASED; urgency=medium
+senlin (4.0.0-3) UNRELEASED; urgency=medium
 
   * Added pt_BR.po (Closes: #861983).
   * Updated fr.po (Closes: #873469).
   * Updated pt.po (Closes: #876176).
+  * Fixed minimum version of python-docker (Closes: #880127).
 
- -- Thomas Goirand   Sat, 28 Oct 2017 10:03:43 +
+ -- Thomas Goirand   Tue, 31 Oct 2017 10:36:50 +
 
 senlin (4.0.0-1) experimental; urgency=medium