Bug#831993: libcommons-codec-java: accesses the internet during build
Source: libcommons-codec-java Version: 1.10-1 Severity: serious Justification: Policy 4.9 User: la...@debian.org Usertags: network-access Dear Maintainer, Whilst libcommons-codec-java builds successfully on unstable/amd64, according to Debian Policy 4.9 packages may not attempt network access during a build. 00:00:00.00 IP 927730abfc42.59882 > 192.168.43.1.domain: 28043+ A? download.oracle.com. (37) 00:00:00.57 IP 927730abfc42.59882 > 192.168.43.1.domain: 58907+ ? download.oracle.com. (37) 00:00:00.367740 IP 192.168.43.1.domain > 927730abfc42.59882: 28043 4/0/1 CNAME download.oracle.com.edgesuite.net., CNAME a1961.d.akamai.net., A 2.21.71.90, A 2.21.71.80 (156) 00:00:00.372237 IP 192.168.43.1.domain > 927730abfc42.59882: 58907 2/1/1 CNAME download.oracle.com.edgesuite.net., CNAME a1961.d.akamai.net. (182) 00:00:00.375308 IP 927730abfc42.58862 > 2.21.71.90.http: Flags [S], seq 807871607, win 29200, options [mss 1460,sackOK,TS val 5743965 ecr 0,nop,wscale 7], length 0 00:00:00.415639 IP 2.21.71.90.http > 927730abfc42.58862: Flags [S.], seq 1375254780, ack 807871608, win 13080, options [mss 1320,sackOK,TS val 3348374771 ecr 5743965,nop,wscale 9], length 0 [..] The full build log (including tcpdump output) is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- libcommons-codec-java.1.10-1.unstable.amd64.log.txt.gz Description: Binary data
Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php
> Well, you don't edit shipped files. Neither conffiles nor normal files.
> Instead, you put these values into a new file (not a shipped file!,
> maybe ship a template in /usr/share/$pkg) in either /etc or /var (with a
> symlink in /usr pointing to it) that is solely managed by the maintainer
> scripts.
Something like the attached patch? (Untested)
> * upon initial installation only?
Yes, as otherwise you're invalidating all user sessions (or even all
passwords!)
> > I guess you guys can have an interesting discussion about clash between
> > #830979 and #831984.
This seems an odd.attitude to have as the maintainer.. :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/rules b/debian/rules
index f4a187f..f7a120c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,6 +11,8 @@ ifeq ($(DEB_BUILD_ARCH_OS),hurd)
ARGS:= -DZM_NO_MMAP=ON
endif
+CORE_PHP =
$(CURDIR)/debian/tmp/usr/share/zoneminder/www/api/app/Config/core.php
+
%:
dh $@ --parallel --buildsystem=cmake --builddirectory=dbuild \
--with systemd,sphinxdoc,apache2,linktree
@@ -64,6 +66,10 @@ override_dh_auto_install:
dh_auto_install --arch --destdir=$(CURDIR)/debian/tmp
# remove empty directories:
-find $(CURDIR)/debian/tmp/usr -mindepth 1 -type d -empty -delete
-printf 'removed %p\n'
+
+ # Don't ship core.php as it contains pre-generated/static salts. We
+ # keep core.php.default as a template for the postinst.
+ rm -f $(CORE_PHP)
override_dh_install:
dh_install -XLICENSE -XLICENSE.txt -X.gitignore
diff --git a/debian/zoneminder.postinst b/debian/zoneminder.postinst
index b50b38a..ec33890 100644
--- a/debian/zoneminder.postinst
+++ b/debian/zoneminder.postinst
@@ -2,6 +2,9 @@
set -e
+TARGET="/etc/zm/core.php"
+SOURCE="/usr/share/zoneminder/www/api/app/Config/core.php.default"
+
Generate_random () {
tr -dc $1 < /dev/urandom | head -c $2
}
@@ -13,10 +16,13 @@ if [ "$1" = "configure" ]; then
chown www-data:www-data -R /var/cache/zoneminder
fi
- sed -i \
- -e "s@__ZM_API_SALT__@$(Generate_random A-Za-z0-9
29)@g" \
- -e "s@__ZM_API_SEED__@$(Generate_random 0-9 40)@g" \
- /usr/share/zoneminder/www/api/app/Config/core.php
+ if [ ! -e "${TARGET}" ]
+ then
+ sed \
+ -e "s@__ZM_API_SALT__@$(Generate_random
A-Za-z0-9 29)@g" \
+ -e "s@__ZM_API_SEED__@$(Generate_random 0-9
40)@g" \
+ ${SOURCE} > ${TARGET}
+ fi
fi
#DEBHELPER#
Processed: bumping severity to serious
Processing commands for cont...@bugs.debian.org: > severity 831918 serious Bug #831918 [src:bglibs] bglibs: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831921 serious Bug #831921 [src:daemontools] daemontools: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831933 serious Bug #831933 [src:mono] mono: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831944 serious Bug #831944 [src:pyorbit] pyorbit: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831945 serious Bug #831945 [src:pygtk] pygtk: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831950 serious Bug #831950 [src:gnome-python] gnome-python: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831960 serious Bug #831960 [src:pygobject-2] pygobject-2: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831961 serious Bug #831961 [src:proftpd-dfsg] proftpd-dfsg: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > severity 831963 serious Bug #831963 [src:netqmail] netqmail: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 831918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831918 831921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831921 831933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831933 831944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831944 831945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831945 831950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831950 831960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831960 831961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831961 831963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831993: libcommons-codec-java: accesses the internet during build
Le 21/07/2016 à 09:12, Chris Lamb a écrit : > Whilst libcommons-codec-java builds successfully on unstable/amd64, according > to > Debian Policy 4.9 packages may not attempt network access during > a build. Hi Chris, Thank you for reporting this issue. This happens because the Javadoc is linked to the JDK API hosted on download.oracle.com [1]. The connection isn't required for the build though, if it fails the javadoc generated won't contain links to the documentation of the standard API. My understanding of the "no network access" rule was that the build must not require a network connection to complete, nor pull into the package external elements not found in the source tarball at build time. I guess the intent is to ensure that the source packages are self contained. Here the javadoc tool merely checks the existence of the remote documentation to add href links in the generated files. This is optional and doesn't break the build if it doesn't work. So for these reasons I think this is a rather minor policy violation, the package is indeed self contained and doesn't fail to build without network access. I'm more concerned about the reproducibility issue induced though, because this means the package generated will be different when built with or without network access. libcommons-codec-java is still built with Ant. Switching to maven-debian-helper should fix this issue. Emmanuel Bourg [1] https://sources.debian.net/src/libcommons-codec-java/1.10-1/build.xml/#L93
Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php
> Something like the attached patch? (Untested)
Had more time than I thought; updated and (quickly) tested patch
attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/rules b/debian/rules
index f4a187f..9bf025b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -64,6 +64,10 @@ override_dh_auto_install:
dh_auto_install --arch --destdir=$(CURDIR)/debian/tmp
# remove empty directories:
-find $(CURDIR)/debian/tmp/usr -mindepth 1 -type d -empty -delete
-printf 'removed %p\n'
+
+ # Don't ship core.php as it contains pre-generated/static salts. We
+ # keep core.php.default as a template for the postinst.
+ rm -f
$(CURDIR)/debian/tmp/usr/share/zoneminder/www/api/app/Config/core.php
override_dh_install:
dh_install -XLICENSE -XLICENSE.txt -X.gitignore
diff --git a/debian/zoneminder.links b/debian/zoneminder.links
index 06dd74e..b1e1e96 100644
--- a/debian/zoneminder.links
+++ b/debian/zoneminder.links
@@ -8,3 +8,5 @@
/usr/share/man/man8/zoneminder-zmf.8.gz
/usr/share/man/man8/zmf.8.gz
/usr/share/man/man8/zoneminder-zmstreamer.8.gz
/usr/share/man/man8/zmstreamer.8.gz
/usr/share/man/man8/zoneminder-zmu.8.gz
/usr/share/man/man8/zmu.8.gz
+
+/etc/zm/core.php /usr/share/zoneminder/www/api/app/Config/core.php
diff --git a/debian/zoneminder.postinst b/debian/zoneminder.postinst
index b50b38a..a5700e5 100644
--- a/debian/zoneminder.postinst
+++ b/debian/zoneminder.postinst
@@ -2,6 +2,9 @@
set -e
+TARGET="/etc/zm/core.php"
+SOURCE="/usr/share/zoneminder/www/api/app/Config/core.php.default"
+
Generate_random () {
tr -dc $1 < /dev/urandom | head -c $2
}
@@ -13,10 +16,15 @@ if [ "$1" = "configure" ]; then
chown www-data:www-data -R /var/cache/zoneminder
fi
- sed -i \
- -e "s@__ZM_API_SALT__@$(Generate_random A-Za-z0-9
29)@g" \
- -e "s@__ZM_API_SEED__@$(Generate_random 0-9 40)@g" \
- /usr/share/zoneminder/www/api/app/Config/core.php
+ if [ ! -e "${TARGET}" ]
+ then
+ echo "I: Generating ${TARGET} from ${SOURCE} ..." >&2
+
+ sed \
+ -e "s@__ZM_API_SALT__@$(Generate_random
A-Za-z0-9 29)@g" \
+ -e "s@__ZM_API_SEED__@$(Generate_random 0-9
40)@g" \
+ ${SOURCE} > ${TARGET}
+ fi
fi
#DEBHELPER#
Processed: Re: Bug#830955: keepalived: Segfault - keepalived doesn't work without CONFIG_IP_VS
Processing commands for cont...@bugs.debian.org: > severity 830955 normal Bug #830955 [keepalived] keepalived: Segfault - keepalived doesn't work without CONFIG_IP_VS Severity set to 'normal' from 'critical' > merge 830955 544700 Bug #830955 [keepalived] keepalived: Segfault - keepalived doesn't work without CONFIG_IP_VS Bug #544700 [keepalived] keepalived doesn't work without CONFIG_IP_VS There is no source info for the package 'keepalived' at version '1.2.20-1' with architecture '' Unable to make a source version for version '1.2.20-1' Marked as found in versions 1.2.20-1. Bug #830955 [keepalived] keepalived: Segfault - keepalived doesn't work without CONFIG_IP_VS There is no source info for the package 'keepalived' at version '1.2.20-1' with architecture '' Unable to make a source version for version '1.2.20-1' Marked as found in versions keepalived/1.1.15-1. Merged 544700 830955 > thanks Stopping processing here. Please contact me if you need assistance. -- 544700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544700 830955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830955: keepalived: Segfault - keepalived doesn't work without CONFIG_IP_VS
severity 830955 normal merge 830955 544700 thanks On Wed, 13 Jul 2016, Mathieu Ruellan wrote: > Package: keepalived > Version: 1.2.20-1 > Severity: critical > Justification: causes serious data loss > > Dear Maintainer, > > Could you please update the keepalived to fix this issue? > > > https://github.com/acassen/keepalived/issues/313 We never supported non-default kernels with strange options. However, I am currently preparing an update to 1.2.23. Whilst reading the issue above, I can't see where it relates to your bug. The issue talks about a segfault when there are not VIPs configured. You are talking about CONFIG_IP_VS. Keepalived never supported running it on kernels without CONFIG_IP_VS So, are you sure the above issue is about your bug? Alex
Bug#831993: libcommons-codec-java: accesses the internet during build
> the javadoc tool merely checks the existence of the remote > documentation to add href links in the generated files. Mm. This also happens with Python's "Sphinx" documentation framework. > This is optional and doesn't break the build if it doesn't work. Builds may not even _attempt_ access IMHO - whether it FTBFS or not is irrelevant from this point of view. This is for many reasons, including leaking the privacy of anyone rebuilding our packages and, as you mention, reproducibility. > I think this is a rather minor policy violation I'm afraid not. Policy actually explicitly agrees with my own opinion here for once (am not wielding it as a stick!). Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php
On 2016-07-21 10:05, Chris Lamb wrote: >> Something like the attached patch? (Untested) > > Had more time than I thought; updated and (quickly) tested patch > attached. postrm purge should delete /etc/zm/core.php, shouldn't it? What should happen if core.php.default changes its content? There are a lot of options, maybe a new one is added some day ... Andreas
Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php
> postrm purge should delete /etc/zm/core.php, shouldn't it? Probably. Patches are proof of concept, am not the maintainer/user here. :) > What should happen if core.php.default changes its content? There are a > lot of options, maybe a new one is added some day ... Good point. So maybe the maintainer should ship a patched core.php under /etc so it gets all the conffile upgrade/diff magic which includes another file with the generated security stuff.. Anyway, probably given you both enough rope for now :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831993: libcommons-codec-java: accesses the internet during build
On Thu, 21 Jul 2016 10:00:06 +0200, Emmanuel Bourg wrote: > My understanding of the "no network access" rule was that the build must > not require a network connection to complete, nor pull into the package > external elements not found in the source tarball at build time. I guess > the intent is to ensure that the source packages are self contained. In my understanding, this has changed in 3.9.7 (emphasis mine): * Policy: [4.9] debian/rules: required targets _must not attempt_ network [..] Closes: #770016 > Here the javadoc tool merely checks the existence of the remote > documentation to add href links in the generated files. This is optional > and doesn't break the build if it doesn't work. So for these reasons I > think this is a rather minor policy violation, the package is indeed > self contained and doesn't fail to build without network access. As the discussion in #770016 shows, the new wording is not about "packages mustn't fail to build without network" but indeed "packages aren't even _allowed to try_ to reach beyond localhost during build." PS1: I can't say that I'm 100% convinced by this policy change. PS2: I'm surprised that it took so long after the release of policy 3.9.7 before someone started a mass bug filing :) Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #374: It's the InterNIC's fault.
Bug#831993: libcommons-codec-java: accesses the internet during build
> PS1: I can't say that I'm 100% convinced by this policy change. This may not be the appropriate venue for a protracted discussion as it's liable to get hidden but can you briefly outline why? > PS2: I'm surprised that it took so long after the release of policy > 3.9.7 before someone started a mass bug filing :) Oh, I haven't started a systematic filing yet. Just filing them as I come across them. ;) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831993: libcommons-codec-java: accesses the internet during build
> Interesting, thank you for the reference. libcommons-codec-java > currently declares a compliance to the version 3.9.6 of the policy. Does > it mean the new rule doesn't apply to it yet? :) Oh, now /that's/ a very cute argument :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831993: libcommons-codec-java: accesses the internet during build
Le 21/07/2016 à 10:24, gregor herrmann a écrit : > In my understanding, this has changed in 3.9.7 (emphasis mine): > > * Policy: [4.9] debian/rules: required targets _must not attempt_ network > [..] > Closes: #770016 Interesting, thank you for the reference. libcommons-codec-java currently declares a compliance to the version 3.9.6 of the policy. Does it mean the new rule doesn't apply to it yet? :) Emmanuel Bourg
Bug#831984: Bug#830979: Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php
On Thursday, 21 July 2016 9:31:47 AM AEST Chris Lamb wrote: > This seems an odd.attitude to have as the maintainer.. :) Sorry if I didn't make it clear: I'm not blaming anyone, it was a oversight on my side which will be fixed. Chris, since I applied your patch I wanted you to get a feedback of its consequences. I hope it is not "odd.attitude". Do I have to recognize the problem as problem every time I respond to bug to avoid "odd.attitude" perception? You know, I'm not denying the problem (or I would have probably tagged it as "wontfix")... -- Regards, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#831993: libcommons-codec-java: accesses the internet during build
Le 21/07/2016 à 10:41, Chris Lamb a écrit : > Oh, now /that's/ a very cute argument :) I'm fine with fixing the package so I won't defend this argument too much, but I'd be curious to know. Because if the compliance level declared by the package doesn't matter, it would mean the Standards-Version field could be deprecated (and considering the time we spend bumping the value of this field twice a year for ~500 packages actively maintained by the Java team, such a simplification would be welcome). Emmanuel Bourg
Bug#831993: libcommons-codec-java: accesses the internet during build
> I won't defend this argument too much, but I'd be curious to know. Same here. Alas I'm not a Policy "wonk" (and try to avoid being one as it tends to devolve technical discussions into ones of intepretative legal-like arguments that focus on the minutae of language rather than on, well, what is best for Debian) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831993: libcommons-codec-java: accesses the internet during build
On Thu, 21 Jul 2016 10:33:35 +0200, Chris Lamb wrote: > > PS1: I can't say that I'm 100% convinced by this policy change. > This may not be the appropriate venue for a protracted discussion as > it's liable to get hidden but can you briefly outline why? My experience with perl packages shows that: - internet access doesn't happen during the build itself but in the test suite; - usually in modules whose purpose is to do something net-related; - by disabling them, even if they fail gracefully, in order to follow policy, we effectively castrate the tests, which doesn't seem right from a QA POV. In those cases the argument "builds differently/produces a different binary package/doesn't build reproducibly" with vs. without internet doesn't hold; still, the privacy/phoning-home aspect is true here as well, so I'm ambivalent. Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #315: The recent proliferation of Nuclear Testing
Bug#831993: libcommons-codec-java: accesses the internet during build
Thanks :) > - by disabling them, even if they fail gracefully, in order to follow > policy, we effectively castrate the tests, which doesn't seem right > from a QA POV. Mm, agreed. Moving these tests to the autopkgtest infrastructure is one fix but it's not "that" clean a solution.. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831240: marked as done (google-perftools: FTBFS: Running death test 0 hangs)
Your message dated Thu, 21 Jul 2016 11:16:28 +0200 with message-id <20160721091628.gc10...@xanadu.blop.info> and subject line Re: Bug#831240: google-perftools: FTBFS: Running death test 0 hangs has caused the Debian Bug report #831240, regarding google-perftools: FTBFS: Running death test 0 hangs 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.) -- 831240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: google-perftools Version: 2.2.1-0.3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160714 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): > PASS: malloc_extension_debug_test > PASS > PASS: memalign_debug_unittest > PASS > PASS: realloc_debug_unittest > make[2]: *** wait: No child processes. Stop. > make[2]: *** Waiting for unfinished jobs > make[2]: *** wait: No child processes. Stop. > make[1]: *** wait: No child processes. Stop. > make[1]: *** Waiting for unfinished jobs > make[1]: *** wait: No child processes. Stop. > make: *** wait: No child processes. Stop. > make: *** Waiting for unfinished jobs > make: *** wait: No child processes. Stop. > E: Caught signal ‘Terminated’: terminating immediately > Running death test 0Build killed with signal TERM after 150 minutes of > inactivity The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/14/google-perftools_2.2.1-0.3_unstable_gcc5.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 --- On 20/07/16 at 15:43 -0700, Aliaksey Kandratsenka wrote: > On Tue, Jul 19, 2016 at 1:29 PM, Lucas Nussbaum wrote: > > Hi Aliaksey, > > > > On 16/07/16 at 12:28 +0200, Santiago Vila wrote: > >> On Fri, 15 Jul 2016, Aliaksey Kandratsenka wrote: > >> > >> > Thanks for reporting the issue. I just tried to reproduce the problem > >> > on my sid laptop in cleanly deboostrap-ed sid chroot and was unable to > >> > hit this issue. This maybe indicates that kernel matters or maybe > >> > there is something else in the host that is relevant. > >> > >> For the record: While checking for "dpkg-buildpackage -A", I was also > >> able to reproduce this problem in the past: > >> > >> Running death test 0...make[2]: *** wait: No child processes. Stop. > >> make[2]: *** Waiting for unfinished jobs > >> make[2]: *** wait: No child processes. Stop. > >> make[1]: *** wait: No child processes. Stop. > >> make[1]: *** Waiting for unfinished jobs > >> make[1]: *** wait: No child processes. Stop. > >> make: *** wait: No child processes. Stop. > >> make: *** Waiting for unfinished jobs > >> make: *** wait: No child processes. Stop. > >> Build killed with signal TERM after 150 minutes of inactivity > >> > >> I'm also using sbuild, triggered by a cron job. > > > > Do you still need help to reproduce the issue? Indeed it was the > > equivalent of dpkg-buildpackage -A that triggered it. > > I got sbuild set up on my box (via instructions at > https://wiki.debian.org/sbuild) and even under sbuild I am unable to > reproduce the problem. > > So maybe this is something with kernel? Should I try to get, say > recent stable installed under KVM? I am running on fairly up-to-date > unstable distro. Hi, I recently discovered that the official Debian images on AWS EC2 include some sysctl tunings (see https://github.com/andsens/bootstrap-vz/pull/256/commits/06da309895f69573996a4c1ff027f999155b876b#diff-43081b58ccf1565f80325d26c36d7c57R18 ) It seems that one of those caused that failure, because, now that I have them disabled, it does not fail anymore. I'm closing this bug, sorry for the noise. Lucas--- End Message ---
Bug#831993: libcommons-codec-java: accesses the internet during build
On Thu, 21 Jul 2016 11:19:46 +0200, Chris Lamb wrote: > > - by disabling them, even if they fail gracefully, in order to follow > > policy, we effectively castrate the tests, which doesn't seem right > > from a QA POV. > Mm, agreed. Moving these tests to the autopkgtest infrastructure is one > fix but it's not "that" clean a solution.. Well, right, autopkgtest is the next question. If a test is forbidden to leak to external parties the fact that it's being run during build, the same is probably true by analogy for autopkgtests? (Recently I disabled the same tests for both build + autopkgtests.) Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #211: Lightning strikes.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 831067 pending Bug #831067 [src:openvdb] openvdb: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 831067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831993: libcommons-codec-java: accesses the internet during build
I believe there is a control field for autopkgtest for this purpose. gregor herrmann wrote: > On Thu, 21 Jul 2016 11:19:46 +0200, Chris Lamb wrote: > > > > - by disabling them, even if they fail gracefully, in order to follow > > > policy, we effectively castrate the tests, which doesn't seem right > > > from a QA POV. > > Mm, agreed. Moving these tests to the autopkgtest infrastructure is one > > fix but it's not "that" clean a solution.. > > Well, right, autopkgtest is the next question. If a test is forbidden > to leak to external parties the fact that it's being run during > build, the same is probably true by analogy for autopkgtests? > > (Recently I disabled the same tests for both build + autopkgtests.) > > > Cheers, > gregor > > -- > .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 > : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ > `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe >`- BOFH excuse #211: Lightning strikes. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831181: marked as done (odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: call of overloaded 'sqrt(funcMode&)' is ambiguous)
Your message dated Thu, 21 Jul 2016 09:56:24 +
with message-id
and subject line Bug#831181: fixed in odin 2.0.2-0.2
has caused the Debian Bug report #831181,
regarding odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: call of
overloaded 'sqrt(funcMode&)' 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.)
--
831181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odin
Version: 2.0.2-0.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64
Hi,
During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
Relevant part (hopefully):
> /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
> -I../tjutils -I.. -I/«PKGBUILDDIR» -I/usr/include/qwt-qt4
> -I/usr/share/qt4/include/QtGui -I/usr/share/qt4/include/QtCore
> -I/usr/share/qt4/include -I. -I/usr/include/dcmtk
> -I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/ofstd
> -I/usr/include/vtk-6.3 -I/usr/include/nifti -Wdate-time -D_FORTIFY_SOURCE=2
> -O3 -fno-tree-vectorize -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -c -o odinpulse.lo odinpulse.cpp
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../tjutils -I.. -I/«PKGBUILDDIR»
> -I/usr/include/qwt-qt4 -I/usr/share/qt4/include/QtGui
> -I/usr/share/qt4/include/QtCore -I/usr/share/qt4/include -I.
> -I/usr/include/dcmtk -I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/ofstd
> -I/usr/include/vtk-6.3 -I/usr/include/nifti -Wdate-time -D_FORTIFY_SOURCE=2
> -O3 -fno-tree-vectorize -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -c odinpulse.cpp -fPIC -DPIC -o .libs/odinpulse.o
> In file included from ../odinseq/seqplatform.h:24:0,
> from ../odinseq/seqdriver.h:23,
> from ../odinseq/seqphase.h:26,
> from ../odinseq/seqfreq.h:25,
> from ../odinseq/seqpuls.h:22,
> from odinpulse.h:24,
> from odinpulse.cpp:1:
> ../odinseq/seqplot.h:39:87: warning: invalid suffix on literal; C++11
> requires a space between literal and string macro [-Wliteral-suffix]
> static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, ODIN_GRAD_UNIT,
> ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2",
> "rad/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};
>
> ^
> ../odinseq/seqplot.h:39:106: warning: invalid suffix on literal; C++11
> requires a space between literal and string macro [-Wliteral-suffix]
> static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, ODIN_GRAD_UNIT,
> ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2",
> "rad/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};
>
> ^
> ../odinseq/seqplot.h:39:128: warning: invalid suffix on literal; C++11
> requires a space between literal and string macro [-Wliteral-suffix]
> static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, ODIN_GRAD_UNIT,
> ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2",
> "rad/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};
>
> ^
> ../odinseq/seqplot.h:39:148: warning: invalid suffix on literal; C++11
> requires a space between literal and string macro [-Wliteral-suffix]
> static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, ODIN_GRAD_UNIT,
> ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT,
> "rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2",
> "rad/"ODIN_SPAT_UNIT, ODIN_TIME_UNIT"/"ODIN_SP
Bug#831240: google-perftools: FTBFS: Running death test 0 hangs
severity 831240 important reopen 831240 On Thu, 21 Jul 2016, Lucas Nussbaum wrote: > I recently discovered that the official Debian images on AWS EC2 include > some sysctl tunings (see > https://github.com/andsens/bootstrap-vz/pull/256/commits/06da309895f69573996a4c1ff027f999155b876b#diff-43081b58ccf1565f80325d26c36d7c57R18 > ) > > It seems that one of those caused that failure, because, now that I have > them disabled, it does not fail anymore. > > I'm closing this bug, sorry for the noise. Hmm. Failure to build from source is still a bug. Ok, some people do not consider a FTBFS to be serious if the failure does not happen in the official buildds, but this fact should only make the bug non-RC, not make it a non-bug. OTOH, if there is really a good reason to fail in this non-standard environment, then the bug should be reassigned to whatever package setups the non-standard environment (bootstrap-vz?), not just closed. Thanks.
Processed (with 5 errors): Re: Bug#831240: google-perftools: FTBFS: Running death test 0 hangs
Processing commands for cont...@bugs.debian.org:
> severity 831240 important
Bug #831240 {Done: Lucas Nussbaum } [src:google-perftools]
google-perftools: FTBFS: Running death test 0 hangs
Severity set to 'important' from 'serious'
> reopen 831240
Bug #831240 {Done: Lucas Nussbaum } [src:google-perftools]
google-perftools: FTBFS: Running death test 0 hangs
Bug reopened
Ignoring request to alter fixed versions of bug #831240 to the same values
previously set
> On Thu, 21 Jul 2016, Lucas Nussbaum wrote:
Unknown command or malformed arguments to command.
> > I recently discovered that the official Debian images on AWS EC2 include
Unknown command or malformed arguments to command.
> > some sysctl tunings (see
Unknown command or malformed arguments to command.
> > https://github.com/andsens/bootstrap-vz/pull/256/commits/06da309895f69573996a4c1ff027f999155b876b#diff-43081b58ccf1565f80325d26c36d7c57R18
Unknown command or malformed arguments to command.
> > )
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
831240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#412185: Multiple RC issues identified in atftpd
Processing control commands: > tags -1 + patch Bug #412185 [atftpd] Upgrade overwrites /etc/default/atftpd, inetd.conf Added tag(s) patch. -- 412185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#412185: Multiple RC issues identified in atftpd
Control: tags -1 + patch
[Ludovic Drolez]
> Yes proper auto-configuration of this package is a nightmare, maybe the
> better is to drop all auto-config and suggest people to manually
> configure it.
Probably not. Here is a draft patch (untested) which make sure the
atftpd.config script load the current settings from /etc/ before
asking during installation and upgrades, to ensure the current
settings on disk do not change.
I'm a but unsure how robust the inetd option loading is, but suspect it
should work. I disabled the rewrite of /etc/logrotate.d/atftpd, as I am not
quite sure how to do that best. It might be good to print a warning if the
log file name is changed.
--
Happy hacking
Petter Reinholdtsen
diff --git a/debian/atftpd.config b/debian/atftpd.config
index 46acf03..b19ae22 100644
--- a/debian/atftpd.config
+++ b/debian/atftpd.config
@@ -3,6 +3,46 @@
. /usr/share/debconf/confmodule
db_version 2.0
+opts2debconf() {
+while "$1" ; do
+ case "$opt" in
+ --daemon) ;;
+ --port) db_set atftpd/port "$2"; shift ;;
+ --tftpd-timeout) db_set atftpd/tftpd-timeout "$2"; shift ;;
+--retry-timeout) db_set atftpd/retry-timeout "$2"; shift ;;
+--maxthread) db_set atftpd/maxthread "$2"; shift ;;
+ --no-timeout)db_set atftpd/timeout "false"; shift ;;
+ --no-tsize) db_set atftpd/tsize "false"; shift ;;
+ --no-blksize)db_set atftpd/blksize "false"; shift ;;
+ --no-multicast) db_set atftpd/multicast "false"; shift ;;
+ --mcast-port)db_set atftpd/mcast_port "$2"; shift ;;
+ --mcast-addr)db_set atftpd/mcast_addr "$2"; shift ;;
+ --mcast-ttl) db_set atftpd/ttl "$2"; shift ;;
+ --verbose=*)
+ db_set atftpd/verbosity $(echo "$1" | cut -d= -f2-)
+ ;;
+ --logfile)
+ db_set atftpd/logtofile true
+ db_set atftpd/logfile "$2"
+ ;;
+ /*) db_set atftpd/basedir "$1" ;;
+ esac
+ shift
+done
+}
+
+# Load current settings from file
+if [ -f /etc/default/atftpd ]; then
+. /etc/default/atftpd
+db_set atftpd/use_inetd "$USE_INETD"
+if [ "$USE_INETD" = "false" ]; then
+ opts2debconf $OPTIONS
+else
+ # FIXME should work with xinetd too
+ INETOPTS="$(grep /usr/sbin/in.tftpd /etc/inetd.conf | sed 's%.*/usr/sbin/in.tftpd %%')"
+ opts2debconf $INETOPTS
+fi
+fi
# Do not ask if you need to configure atftp (Bug#266329)
#db_beginblock
diff --git a/debian/atftpd.postinst b/debian/atftpd.postinst
index 6a8d0cc..c07dbc6 100644
--- a/debian/atftpd.postinst
+++ b/debian/atftpd.postinst
@@ -94,8 +94,9 @@ db_version 2.0
chown nobody:nogroup $RET
chmod 640 $RET
fi
- # modify the logrotate file
- cat >/etc/logrotate.d/atftpd
Processed: The package already exists!
Processing commands for cont...@bugs.debian.org:
> close 831994
Bug #831994 [sponsorship-requests] RFS: python-prompt-toolkit/1.0.3-1 (ITP)
Marked Bug as done
> close 821990
Bug #821990 [gworldclock] gworldclock: Build arch:all+arch:any but is missing
build-{arch,indep} targets
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
821990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821990
831994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: liblog4cplus-1.1-9: C++11 methods missing from the binary
Processing control commands: > severity -1 critical Bug #814905 [liblog4cplus-1.1-9] liblog4cplus-1.1-9: C++11 methods missing from the binary Severity set to 'critical' from 'normal' > block 831118 by -1 Bug #831118 [src:openalpr] openalpr: FTBFS with GCC 6: daemon.cpp:153: undefined reference to `log4cplus::Logger::operator=(log4cplus::Logger&&)' 831118 was not blocked by any bugs. 831118 was not blocking any bugs. Added blocking bug(s) of 831118: 814905 -- 814905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814905 831118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
debian-bugs-rc@lists.debian.org
[Petter Reinholdtsen] > As far as I can see, this can not be fixed in openalpr, but must be fixed in > liblog4cplus. Perhaps this bug should be reassigned? No need, as it is already reported as bug #814905. -- Happy hacking Petter Reinholdtsen
Bug#825095: marked as pending
tag 825095 pending thanks Hello, Bug #825095 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: http://git.debian.org/?p=python-modules/packages/python-backports-shutil-get-terminal-size.git;a=commitdiff;h=3dacd27 --- commit 3dacd27fe8387865f4e2b81bf4582802c1b73281 Author: Julien Puydt Date: Thu Jul 21 13:11:08 2016 +0200 Fixed file conflict with other python-backports-* packages. (Closes: 825095) diff --git a/debian/changelog b/debian/changelog index e9160a9..19e4c24 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-backports-shutil-get-terminal-size (1.0.0-2) UNRELEASED; urgency=medium + + * Fixed file conflict with other python-backports-* packages. (Closes: 825095) + + -- Julien Puydt Thu, 21 Jul 2016 13:10:12 +0200 + python-backports-shutil-get-terminal-size (1.0.0-1) unstable; urgency=medium * Initial release. (Closes: #824984)
Processed: Bug#825095 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 825095 pending Bug #825095 [python-backports-shutil-get-terminal-size] python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 825095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811717: marked as done (ivtools: FTBFS with GCC 6: narrowing conversion)
Your message dated Thu, 21 Jul 2016 11:19:21 +
with message-id
and subject line Bug#811717: fixed in ivtools 1.2.11a1-7
has caused the Debian Bug report #811717,
regarding ivtools: FTBFS with GCC 6: narrowing conversion
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.)
--
811717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ivtools
Version: 1.2.11a1-5
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing
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.
Note that only the first error is reported; there might be more. 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.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -Dcplusplus_2_1 -DUnidrawCommon
> -Isrc -Isrc/include -Isrc/include/ivstd -Wdate-time -D_FORTIFY_SOURCE=2
> -Wno-write-strings -Wno-deprecated -g -O2 -fstack-protector-strong -c
> src/Unidraw/ulist.cc -o src/Unidraw/libUnidraw_common_la-ulist.o >/dev/null
> 2>&1
> In file included from src/IV-2_6/adjuster2_6.cc:36:0:
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '238' from 'int' to 'char' inside { } [-Wnarrowing]
> 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
> ^
>
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -Dcplusplus_2_1 -DUnidrawCommon
> -Isrc -Isrc/include -Isrc/include/ivstd -Wdate-time -D_FORTIFY_SOURCE=2
> -Wno-write-strings -Wno-deprecated -g -O2 -fstack-protector-strong -c
> src/Unidraw/uarray.cc -o src/Unidraw/libUnidraw_common_la-uarray.o >/dev/null
> 2>&1
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '192' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '240' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '131' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '240' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '128' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '128' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeHit.bm:10:74: error: narrowing
> conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing]
> In file included from src/IV-2_6/adjuster2_6.cc:37:0:
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '254' from 'int' to 'char' inside { } [-Wnarrowing]
> 0xc0, 0xff, 0x07, 0x00, 0xc0, 0xff, 0x07, 0x00, 0xc0, 0xff, 0x07, 0x00};
> ^
>
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '192' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '240' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '240' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '248' from 'int' to 'char' inside { } [-Wnarrowing]
> src/include/InterViews/Bitmaps/enlargeMask.bm:10:74: error: narrowing
> conversion of '255' from 'int' to 'c
Bug#825095: marked as done (python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname)
Your message dated Thu, 21 Jul 2016 11:48:34 + with message-id and subject line Bug#825095: fixed in python-backports-shutil-get-terminal-size 1.0.0-2 has caused the Debian Bug report #825095, regarding python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname 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.) -- 825095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-backports-shutil-get-terminal-size Version: 1.0.0-1 Severity: serious Justification: Policy 6.6(4) python-backports-shutil-get-terminal-size is impossible to install alongside python-backports.ssl-match-hostname: Unpacking python-backports-shutil-get-terminal-size (1.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python-backports-shutil-get-terminal-size_1.0.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/backports/__init__.py', which is also in package python-backports.ssl-match-hostname 3.4.0.2-1 Could you please take a look? Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: python-backports-shutil-get-terminal-size Source-Version: 1.0.0-2 We believe that the bug you reported is fixed in the latest version of python-backports-shutil-get-terminal-size, 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 825...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated python-backports-shutil-get-terminal-size 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: Thu, 21 Jul 2016 13:13:26 +0200 Source: python-backports-shutil-get-terminal-size Binary: python-backports-shutil-get-terminal-size Architecture: source Version: 1.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Julien Puydt Description: python-backports-shutil-get-terminal-size - Backport of the "shutil.get_terminal_size" function (Python 2) Closes: 825095 Changes: python-backports-shutil-get-terminal-size (1.0.0-2) unstable; urgency=medium . * Fixed file conflict with other python-backports-* packages. (Closes: 825095) * Fixed Vcs-* fields. Checksums-Sha1: 5d56958fc8794f029ef99c3e4f36579e26027890 2364 python-backports-shutil-get-terminal-size_1.0.0-2.dsc b23149c23d40c0e9ec3efe9ed373f2e447cc7434 1968 python-backports-shutil-get-terminal-size_1.0.0-2.debian.tar.xz Checksums-Sha256: cc0171e324f618eec1800b65cc458343aa89abd580d7b3c33bbadbacf4dfb05e 2364 python-backports-shutil-get-terminal-size_1.0.0-2.dsc 029df8971956dfa3fa995fe2ed40af0025d0f386ca48100cb98f42e60e2d8304 1968 python-backports-shutil-get-terminal-size_1.0.0-2.debian.tar.xz Files: f7c259082f428626d106210a5d1c0d6d 2364 python optional python-backports-shutil-get-terminal-size_1.0.0-2.dsc 6146d872b882c4344582cddf547ecf0e 1968 python optional python-backports-shutil-get-terminal-size_1.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXkLTGAAoJEPNPCXROn13ZbE8QANORECH0/uaGtd6bSCq3y3+t DpgEG6Q2KqgncuQwGPeqs2LWacGXLoymlupVUkGvMbZaf4m+R1zu4qa72rWKkBy8 gpkFSBDJJUhQENuk121yLIR0BonLc2Blki9l2fUR0YiL8sjTWetYVgObuVlkfGsM HjwVXnqC89aiLHDQ7qP4C5xVbjMHnrblTE94e+A6cBkSzS+xwqThSS91bOA47oXN oFpVROF6kvu5/e3F3fKdzv0Jf/qASLm06i6jFUCKvE1gPEbxJqAGLV0MNjQZbdoR 9BCmnu8/Hmp2SPkNeUA38lnirnASHCEPycgJzLXAEqECJUKRL5CCGMu5owCdCptU AHQS2KsNEVN2iXH5FBsHXfSEhR+bNkgqKLgnT1XeSYml1weS0eKTZCB0EU3VjM6K 7I5nqPA9EscqBtahV9vNJVbaaYQ21YurigOa68qUK4z2W4gOkRdkOs4rYPJAwP6O lhoPzQhBpBt6hc91TSTYarioFL15IZuA6tL9Vae8VhcPjYA4FycbcLu8M9KQ/vfY 1AqowJDcSh2QzYcvCr/2n5L1815H0rBr9HuTakqeBmope66V58gFkEaysfZ16m1q zPjFNnl0USG/wsi/zwMsRBMUPXrY3AwQ3tiAdilBZj2DxU8vJaw9
Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade
On Wed, 20 Jul 2016 22:06:05 +0300 Faidon Liambotis wrote: > Stack trace of thread 4122: > #0 0x7fa47ae7f1c8 raise (libc.so.6) > #1 0x7fa47ae8064a abort (libc.so.6) > #2 0x7fa4719b8f5b n/a (libavcodec.so.57) > #3 0x7fa4719b9026 avcodec_alloc_context3 >(libavcodec.so.57) > #4 0x7fa473360540 n/a (libgstlibav.so) > #5 0x7fa473356e53 n/a (libgstlibav.so) > #6 0x7fa47b74b22d g_type_class_ref (libgobject-2.0.so.0) > #7 0x7fa47b9c8da4 gst_element_register >(libgstreamer-1.0.so.0) > #8 0x7fa4733575b3 n/a (libgstlibav.so) > #9 0x7fa473349e20 n/a (libgstlibav.so) > #10 0x7fa47b9ea537 n/a (libgstreamer-1.0.so.0) > #11 0x7fa47b9ec425 n/a (libgstreamer-1.0.so.0) > #12 0x7fa47b9ed12c gst_plugin_load_by_name >(libgstreamer-1.0.so.0) > #13 0x7fa47b9eda8d gst_plugin_feature_load >(libgstreamer-1.0.so.0) > #14 0x7fa47ba137e3 gst_type_find_factory_call_function >(libgstreamer-1.0.so.0) > #15 0x7fa479c48421 gst_type_find_helper_for_data >(libgstbase-1.0.so.0) > #16 0x7fa479c485a4 gst_type_find_helper_for_buffer >(libgstbase-1.0.so.0) > #17 0x7fa4799f446a n/a (libgstwavparse.so) > #18 0x7fa4799f4b47 n/a (libgstwavparse.so) > #19 0x7fa4799fabb1 n/a (libgstwavparse.so) > #20 0x7fa47ba0ee71 n/a (libgstreamer-1.0.so.0) > #21 0x7fa47b47b55e n/a (libglib-2.0.so.0) > #22 0x7fa47b47abc5 n/a (libglib-2.0.so.0) > #23 0x7fa47b1f4464 start_thread (libpthread.so.0) Thanks for the report. Can you install debug symbols for libavcodec57 and get another backtrace? Also what's the assertion you see on the terminal that causes the abort()? Do you have the same problem with gstreamer1.0-libav from experimental (version 1.9.1-1)? I can't reproduce this here with either 1.8.2-1 or 1.9.1-1 unfortunately. signature.asc Description: This is a digitally signed message part
Bug#811620: marked as done (FTBFS with GCC 6: cannot convert x to y)
Your message dated Thu, 21 Jul 2016 12:05:30 + with message-id and subject line Bug#811620: fixed in xml-security-c 1.7.3-2 has caused the Debian Bug report #811620, regarding FTBFS with GCC 6: cannot convert x to y 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.) -- 811620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xml-security-c Version: 1.7.3-1 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-cannot-convert 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. Note that only the first error is reported; there might be more. 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. > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > /bin/bash ../libtool --tag=CXX --mode=link g++ -Wall -g -O2 -fPIE > -fstack-protector-strong -Wformat -Werror=format-security -O2 -DNDEBUG > -pthread -DXSEC_LIBRARY_BUILD -fPIE -pie -Wl,-z,relro -Wl,-z,now > -Wl,--as-needed -o xsec-c14n tools/c14n/c14n.o libxml-security-c.la > -lxerces-c -lm -lssl -lcrypto > libtool: link: g++ -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat > -Werror=format-security -O2 -DNDEBUG -pthread -DXSEC_LIBRARY_BUILD -fPIE -pie > -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/xsec-c14n tools/c14n/c14n.o > -Wl,--as-needed ./.libs/libxml-security-c.so -lxerces-c -lm -lssl -lcrypto > -pthread > g++ -DHAVE_CONFIG_H -I. -I.. -I../xsec/framework -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat > -Werror=format-security -O2 -DNDEBUG -pthread -DXSEC_LIBRARY_BUILD -c -o > tools/checksig/checksig.o tools/checksig/checksig.cpp > In file included from ../xsec/enc/XSECCryptoProvider.hpp:42:0, > from ../xsec/utils/XSECPlatformUtils.hpp:39, > from ../xsec/utils/XSECDOMUtils.hpp:36, > from ../xsec/dsig/DSIGKeyInfo.hpp:36, > from ../xsec/dsig/DSIGKeyInfoList.hpp:35, > from ../xsec/enc/XSECKeyInfoResolver.hpp:36, > from tools/checksig/InteropResolver.hpp:35, > from tools/checksig/checksig.cpp:30: > ../xsec/enc/XSECCryptoSymmetricKey.hpp:188:52: warning: converting to > non-pointer type 'unsigned int' from NULL [-Wconversion-null] > unsigned int taglen = NULL) = 0; > ^~~~ > > g++ -DHAVE_CONFIG_H -I. -I.. -I../xsec/framework -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat > -Werror=format-security -O2 -DNDEBUG -pthread -DXSEC_LIBRARY_BUILD -c -o > tools/checksig/AnonymousResolver.o tools/checksig/AnonymousResolver.cpp > In file included from ../xsec/enc/XSECCryptoProvider.hpp:42:0, > from ../xsec/utils/XSECPlatformUtils.hpp:39, > from ../xsec/utils/XSECDOMUtils.hpp:36, > from tools/checksig/AnonymousResolver.cpp:36: > ../xsec/enc/XSECCryptoSymmetricKey.hpp:188:52: warning: converting to > non-pointer type 'unsigned int' from NULL [-Wconversion-null] > unsigned int taglen = NULL) = 0; > ^~~~ > > g++ -DHAVE_CONFIG_H -I. -I.. -I../xsec/framework -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat > -Werror=format-security -O2 -DNDEBUG -pthread -DXSEC_LIBRARY_BUILD -c -o > tools/checksig/InteropResolver.o tools/checksig/InteropResolver.cpp > In file included from ../xsec/enc/XSECCryptoProvider.hpp:42:0, > from ../xsec/utils/XSECPlatformUtils.hpp:39, > from ../xsec/utils/XSECDOMUtils.hpp:36, > from ../xsec/dsig/DSIGKeyInfo.hpp:36, > from ../xsec/dsig/DSIGKeyInfoList.hpp:35, > from ../xsec/enc/XSECKeyInfoResolver.hpp:36, > from tools/checksig/InteropResolver.hpp:35, > from tools/checksig/InteropResolver.cpp:32: > ../xsec/enc/XSECCryptoSymmetricKey.hpp:188:52: warning: converting to > non-pointer type 'unsigned int' from NULL [-Wconversion-null] > unsigned int taglen = NULL) = 0; > ^~~~ > > tools/checksig/InteropResolver.cpp: In member function 'virtual > XSECCryptoKey* InteropResolver::res
Processed: discount: FTBFS on many architectures: 1 test failed
Processing commands for cont...@bugs.debian.org: > tags 826197 + fixed-upstream patch Bug #826197 [src:discount] discount: FTBFS on many architectures: 1 test failed Added tag(s) fixed-upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 826197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#826197: discount: FTBFS on many architectures: 1 test failed
tags 826197 + fixed-upstream patch thanks This issue was fixed upstream (and the bug is actually on those arches where the tests did NOT fail...): https://github.com/Orc/discount/commit/0d71ce77859c44aad7379d70c9024d5047577100 https://github.com/Orc/discount/commit/aa9a54bddb3211204625c1eb6a2656e0f4b4e59c It would be nice to have these fixes included in Debian. It does not look like upstream is planing to have a new release just for this. Cheers, Uli
Bug#831804: marked as done (Fails to build on arch:all buildd)
Your message dated Thu, 21 Jul 2016 12:18:28 + with message-id and subject line Bug#831804: fixed in apcupsd 3.14.14-0.2 has caused the Debian Bug report #831804, regarding Fails to build on arch:all buildd 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.) -- 831804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:apcupsd Version: 3.14.14-0.1 Severity: serious buildlog excerpt: dh_fixperms chmod 0755 debian/apcupsd/etc/apcupsd/killpower chmod: cannot access 'debian/apcupsd/etc/apcupsd/killpower': No such file or directory debian/rules:46: recipe for target 'override_dh_fixperms' failed make[1]: *** [override_dh_fixperms] Error 1 make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules:11: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 --- End Message --- --- Begin Message --- Source: apcupsd Source-Version: 3.14.14-0.2 We believe that the bug you reported is fixed in the latest version of apcupsd, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hofstaedtler (supplier of updated apcupsd 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: Thu, 21 Jul 2016 12:03:26 + Source: apcupsd Binary: apcupsd apcupsd-cgi apcupsd-doc Architecture: source Version: 3.14.14-0.2 Distribution: unstable Urgency: medium Maintainer: Giuseppe Iuculano Changed-By: Christian Hofstaedtler Description: apcupsd- APC UPS Power Management (daemon) apcupsd-cgi - APC UPS Power Management (web interface) apcupsd-doc - APC UPS Power Management (documentation/examples) Closes: 831804 Changes: apcupsd (3.14.14-0.2) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS on arch:all buildd, patch from Santiago Vila. (Closes: #831804) Checksums-Sha1: 522bcde12c32a0a6fabf322947215109f54dcb77 2043 apcupsd_3.14.14-0.2.dsc e3c755874e877ed451912298f9aa45bcbfaf69fc 16724 apcupsd_3.14.14-0.2.debian.tar.xz Checksums-Sha256: 8491850f0d48500e9ce0187e70586c7b0818c7a46b4ee074eb64852d73fdfa5a 2043 apcupsd_3.14.14-0.2.dsc 390e05c820b1a43fb52d61690b37100cf9d16ba84eb6cfdd92ae4090de076f0a 16724 apcupsd_3.14.14-0.2.debian.tar.xz Files: a704b577d3deb5aa8333acb92830759b 2043 admin extra apcupsd_3.14.14-0.2.dsc d0c135bce47b912a7aa699f503b83d6f 16724 admin extra apcupsd_3.14.14-0.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJXkLs+AAoJEFwT1tuTBS4DupoQAJFgVFhumQHfVtHUXf6853ZZ tJGhELPv3dDUEbyrLa2JQovLuzy9PB4tNBDHPfLit1hywWjofIu9lhG1Zd7zIX8+ pEB6UX05JlKyDU62+VWZycvtIMHF2YbRUtNrYAKOWYO/i6xH/hrhmM7NAcdKzrH/ +ZwCDapJ7hUktYTCrVJEC0fI53h9QcBZMJYN5yzvJgTRaXwoY8xsELzGK37X1Sz2 3ILBr/Dv9Ae0lmmuscrBX8+Ythlu4ZjT7boJpJBu2y3Ro2dndzJct0iVBCmsv1r+ 6YRy0XstYuRLxa8+pJ2ovC5bfofvMLZ7qPS94KawU0N2ivwa19HjO+tYapEUMjxI iQxaX1mBP6FrVB9QpU5sUsRH/7F530K3kwJQYz4SH4yMJyhnQAZUDFSO4GcuzIYZ Fv2/joMvhmrSl9St32XjdcIj5Sq9Tc6pc0bQj6u/9uhWCbOSEDqhMk/bbLlvUPkX dnmQtcncTmy5S72mkiDH/LYB34Bq90FPujDYisIWP2leNvYMk1QqXxw+l3fB+5ZP MuoD5WdnuvY7RF2PMrA/ovMWrkgangsx7J3uaVT78eyw6DOBdD4ek4v6traPMRyt /6DuXCCa8SryIMMCln1RGeATaHooowzQzSvS0t2+u4hfr4GO+x+nEFgOcS27iqRf PfuEiZkFmnGvcAa8NJuH =o/V5 -END PGP SIGNATURE End Message ---
Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade
If the issue is reproducible, please someone test if it disappears once you recompile GStreamer against the installed libavcodec headers.
Bug#831741: marked as done (pdns-backend-pgsql: new pdns spams postgres log until disk fills up)
Your message dated Thu, 21 Jul 2016 13:03:39 + with message-id and subject line Bug#831741: fixed in pdns 4.0.0-5 has caused the Debian Bug report #831741, regarding pdns-backend-pgsql: new pdns spams postgres log until disk fills up 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.) -- 831741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdns-backend-pgsql Version: 4.0.0-4 Severity: grave Justification: renders package unusable The pg log gets spammed with: 2016-07-18 20:45:26 GMT ERROR: syntax error at end of input at character 12 2016-07-18 20:45:26 GMT STATEMENT: DEALLOCATE constantly, hundreds of times per second. I had to set log_min_messages and log_min_error_statement to fatal to avoid it. Something is wrong with the sql pdns sends to pg. This is a recent regression. I did not notice with with the first 4.0 pres in sid. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages pdns-backend-pgsql depends on: ii dbconfig-common2.0.4 ii dbconfig-pgsql 2.0.4 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.23-1 ii libgcc11:6.1.1-9 ii libpq5 9.5.3-1 ii libstdc++6 6.1.1-9 ii pdns-server4.0.0-4 ii ucf3.0036 pdns-backend-pgsql recommends no packages. Versions of packages pdns-backend-pgsql suggests: pn postgresql -- debconf information: pdns-backend-pgsql/remove-error: abort pdns-backend-pgsql/pgsql/changeconf: false pdns-backend-pgsql/dbconfig-remove: pdns-backend-pgsql/upgrade-backup: true pdns-backend-pgsql/db/dbname: pdns pdns-backend-pgsql/internal/reconfiguring: false * pdns-backend-pgsql/dbconfig-upgrade: true pdns-backend-pgsql/install-error: abort pdns-backend-pgsql/database-type: pgsql pdns-backend-pgsql/pgsql/manualconf: pdns-backend-pgsql/purge: false pdns-backend-pgsql/pgsql/no-empty-passwords: pdns-backend-pgsql/dbconfig-reinstall: false pdns-backend-pgsql/remote/newhost: pdns-backend-pgsql/upgrade-error: abort pdns-backend-pgsql/pgsql/authmethod-admin: ident pdns-backend-pgsql/remote/host: localhost pdns-backend-pgsql/remote/port: pdns-backend-pgsql/missing-db-package-error: abort pdns-backend-pgsql/pgsql/method: Unix socket pdns-backend-pgsql/pgsql/authmethod-user: ident pdns-backend-pgsql/passwords-do-not-match: pdns-backend-pgsql/internal/skip-preseed: false pdns-backend-pgsql/db/app-user: pdns * pdns-backend-pgsql/dbconfig-install: true pdns-backend-pgsql/pgsql/admin-user: postgres --- End Message --- --- Begin Message --- Source: pdns Source-Version: 4.0.0-5 We believe that the bug you reported is fixed in the latest version of pdns, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hofstaedtler (supplier of updated pdns 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: Thu, 21 Jul 2016 12:57:45 + Source: pdns Binary: pdns-server pdns-tools pdns-backend-bind pdns-backend-pipe pdns-backend-ldap pdns-backend-geoip pdns-backend-mysql pdns-backend-odbc pdns-backend-pgsql pdns-backend-sqlite3 pdns-backend-lua pdns-backend-remote pdns-backend-opendbx pdns-backend-mydns pdns-backend-tinydns Architecture: source Version: 4.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian DNS Packaging Changed-By: Christian Hofstaedtler Description: pdns-backend-bind - BIND backend for PowerDNS pdns-backend-geoip - geoip backend for PowerDNS pdns-backend-ldap - LDAP backend for PowerDNS pdns-backend-lua - Lua backend for PowerDNS pdns-backend-mydns - MyDNS compatibility backend for PowerDNS pdns-backend-mysql - generic MySQL backend for PowerDNS
Bug#831733: tomcat6: Don't include in Stretch
resteasy has been updated and I triaged the remaining tomcat6 bugs. I think we can proceed with the removal now.
Bug#831067: marked as done (openvdb: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)
Your message dated Thu, 21 Jul 2016 13:36:44 + with message-id and subject line Bug#831067: fixed in openvdb 3.1.0-4 has caused the Debian Bug report #831067, regarding openvdb: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory 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.) -- 831067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openvdb Version: 3.1.0-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): > g++ -c -DOPENVDB_PRIVATE -g -O2 -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden > -fvisibility-inlines-hidden -pthread -g -I . -I .. -isystem /usr/include > -isystem /usr/include/OpenEXR -isystem /usr/include -isystem /usr/include > -isystem /usr/include -DOPENVDB_USE_BLOSC -DOPENVDB_USE_LOG4CPLUS > -DOPENVDB_USE_GLFW_3 -fPIC -o Grid.o Grid.cc > In file included from /usr/include/c++/6/ext/string_conversions.h:41:0, > from /usr/include/c++/6/bits/basic_string.h:5402, > from /usr/include/c++/6/string:52, > from /usr/include/c++/6/bits/locale_classes.h:40, > from /usr/include/c++/6/bits/ios_base.h:41, > from /usr/include/c++/6/ios:42, > from /usr/include/c++/6/ostream:38, > from /usr/include/c++/6/iostream:39, > from Grid.h:34, > from Grid.cc:31: > /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or > directory > #include_next > ^ > compilation terminated. > make[2]: *** [Grid.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/openvdb_3.1.0-3_unstable_gcc6.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: openvdb Source-Version: 3.1.0-4 We believe that the bug you reported is fixed in the latest version of openvdb, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated openvdb 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: SHA1 Format: 1.8 Date: Thu, 21 Jul 2016 11:37:42 +0200 Source: openvdb Binary: libopenvdb3.1 libopenvdb-dev libopenvdb-doc libopenvdb-tools python-openvdb Architecture: source Version: 3.1.0-4 Distribution: unstable Urgency: medium Maintainer: Mathieu Malaterre Changed-By: Mathieu Malaterre Description: libopenvdb-dev - Sparse Volume Processing toolkit - dev libopenvdb-doc - Sparse Volume Processing toolkit - doc libopenvdb-tools - Sparse Volume Processing toolkit - runtime libopenvdb3.1 - Sparse Volume Processing toolkit - lib python-openvdb - Sparse Volume Processing toolkit - Python binding Closes: 831067 Changes: openvdb (3.1.0-4) unstable; urgency=medium . * Fix compilation with GCC6. Closes: #831067 * Bump Std-Vers to 3.9.8, no changes needed Checksums-Sha1: 1c72b6ce4666c90d360949d45e2577163d26388e 2518 openvdb_3.1.0-4.dsc 99b1b4d41403c584211399c5b721b6595aaea0d1 15864 openvdb_3.1.0-4.debian.tar.xz Checksums-Sha256: 5783a6039d6880a625bc64fffe5a6de917bc820f9f9f02d1bf82a35fcc4c0de7 2518 openvdb_3.1.0-4.dsc f86999b8c6b0880b8efb8dfc6d289a29f53ae5014b1b580be3f30c77f868430f 15
Bug#812040: marked as done (gelemental: FTBFS with GCC 6: operands to ?: have different)
Your message dated Thu, 21 Jul 2016 13:48:33 + with message-id and subject line Bug#812040: fixed in gelemental 1.2.0-10 has caused the Debian Bug report #812040, regarding gelemental: FTBFS with GCC 6: operands to ?: have different 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.) -- 812040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gelemental Version: 1.2.0-9 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 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. Note that only the first error is reported; there might be more. 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.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > .0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 > -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unused -g -O2 > -fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.cc > dialogs.cc: In member function 'bool > gElemental::PropertiesDialog::is_selectable(const > Glib::RefPtr&, const Gtk::TreePath&, bool)': > dialogs.cc:258:14: error: operands to ?: have different types > 'Elemental::PropertyBase*' and 'bool' > return iter ? iter->get_value (cols.property) : false; > ~^ > > Makefile:348: recipe for target 'dialogs.o' failed > make[3]: *** [dialogs.o] Error 1 -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise --- End Message --- --- Begin Message --- Source: gelemental Source-Version: 1.2.0-10 We believe that the bug you reported is fixed in the latest version of gelemental, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated gelemental 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: Thu, 21 Jul 2016 15:33:06 +0200 Source: gelemental Binary: gelemental libelemental0 libelemental-dev libelemental-doc Architecture: source Version: 1.2.0-10 Distribution: unstable Urgency: low Maintainer: Debichem Team Changed-By: Graham Inggs Description: gelemental - Periodic Table viewer libelemental-dev - Periodic Table viewer (development files) libelemental-doc - Periodic Table viewer (API documentation) libelemental0 - Periodic Table viewer (data and shared library) Closes: 755721 812040 Changes: gelemental (1.2.0-10) unstable; urgency=low . * debian/patches/ftbfs_gcc6_812040.patch: Added (Closes: #812040). - Fix FTBFS with GCC 6. * debian/control,rules: Switch from autotools-dev to dh-autoreconf, add build dependency on intltool (Closes: #755721). * debian/compat,control,*.install: Bump to debhelper compat level 9. * debian/*.menu,*.xpm: Remove gelemental menu file, see #741573. * debian/copyright: Machine readable, update copyright years. * debian/control: - Use secure URI for Vcs-Browser. - Add myself to Uploaders. - Bump Standards-Version to 3.9.8, no further changes. Checksums-Sha1: 5f06d67c5c5f967a81799869ac17bffe02bd886c 2363 gelemental_1.2.0-10.dsc d79bfa8b3e078f6c38dfcf5c10c8d527825c6b12 27988 gelemental_1.2.0-10.debian.tar.xz Checksums-Sha256: 6aa8e1988c46f3b30adbe9ac7de0b91b800eaace8d5bab0893ac23c19d07749c 2363 gelemental_1.2.0-10.dsc 65a46483b8f1bc1776c72b091e3cb5a451f54180a1293694f11eaedb51f0b6e8 27988 gelemental_1.2.0-10.debian.tar.xz Files: 4738d480009ea976972e05fe3700652f 2363 science optional gelemental_1.2.0-10.dsc d79b5d2bc983104985f7e4f544cd99c3 27988 science optional gelemental_1.2.0-10.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXkNFOAAoJEK/P7I5mnOHCgqAP/AutcLlZrR7/nhoSHxyoSZsF fMf1Uzc+4RBkAR6BZUQnbQGcaOM47MA9kSzOgiHo
Bug#830554: musicbrainzngs: accesses the internet during build
Tracked upstream in https://github.com/alastair/python-musicbrainzngs/issues/201 However, this is rather a debian packaging issue than an issue upstream. The internet access is needed for the docs (sphinx/intersphinx) see also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830186 The solution for debian is to either not build the documentation, which is available online anyways http://python-musicbrainzngs.readthedocs.io/ or patch the documentation build files to either not use intersphinx or to not use the discid mapping. This would be done here: https://github.com/alastair/python-musicbrainzngs/blob/master/docs/conf.py#L99 I am not sure ATM why the python and python2 mappings don't need internet access, but that might also be a debian patch in sphinx or similar. I didn't follow #830186 and related patches closely. Regards JonnyJD PS: It would be technically possible for sphinx to not make any web requests during build when package/class lists are provided in the build files (like for javadoc linkoffline).
Bug#831863: [pkg-go] Bug#831863: Bug#831863: monkeytail, mtail: both ship /usr/bin/mtail
Martyn, On 20/07/16 19:31, Martyn Smith wrote: > Yeah, I'm not sure if anyone uses it, but it seems pretty pointless now, > I'd be quite happy for it to just disappear :-) Thanks for replying. I will make mtail conclict on monkeytail, so the bug can be closed. Would you file the removal bug with ftp.debian.org, or should I do it? Tincho. -- Martín Ferrari (Tincho)
Bug#831863: Pending fixes for bugs in the mtail package
tag 831863 + pending thanks Some bugs in the mtail package are closed in revision 870c98c509101470bd90710abc26c5afa1aa3c22 in branch 'debian/sid' by Martín Ferrari The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/mtail.git/commit/?id=870c98c Commit message: Conflict with monkeytail, which provides a binary with the same name. Closes: #831863.
Processed: Pending fixes for bugs in the mtail package
Processing commands for cont...@bugs.debian.org: > tag 831863 + pending Bug #831863 [monkeytail,mtail] monkeytail,mtail: both ship /usr/bin/mtail Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 831863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831176: marked as done (gazebo: FTBFS with GCC 6: physics/libgazebo_physics.so.7.0.0: undefined reference to `boost::re_detail::cpp_regex_traits_implementation::transform[abi:cxx11](char con
Your message dated Thu, 21 Jul 2016 16:21:29 + with message-id and subject line Bug#831176: fixed in gazebo 7.3.0+dfsg-2 has caused the Debian Bug report #831176, regarding gazebo: FTBFS with GCC 6: physics/libgazebo_physics.so.7.0.0: undefined reference to `boost::re_detail::cpp_regex_traits_implementation::transform[abi:cxx11](char const*, char const*) const' 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.) -- 831176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gazebo Version: 7.0.0+dfsg-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): > /usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra > -Wno-long-long -Wno-unused-value -Wno-unused-value -Wno-unused-value > -Wno-unused-value -Wfloat-equal -Wshadow -Winit-self -Wswitch-default > -Wmissing-include-dirs -pedantic -fvisibility=hidden > -fvisibility-inlines-hidden -std=c++11 -mfpmath=sse -msse -msse2 -msse3 > -mssse3 -DSSE -Wl,-z,relro CMakeFiles/gzserver.dir/server_main.cc.o -o > gzserver-7.0.0 -L/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/test > -rdynamic libgazebo.so.7.0.0 sensors/libgazebo_sensors.so.7.0.0 > rendering/libgazebo_rendering.so.7.0.0 -lfreeimage -ltbb -latomic -lpthread > physics/libgazebo_physics.so.7.0.0 util/libgazebo_util.so.7.0.0 -ltinyxml2 > ../deps/opende/libgazebo_ode.so.7.0.0 > ../deps/opende/GIMPACT/libgazebo_gimpact.so.7.0.0 > ../deps/opende/ou/libgazebo_opende_ou.so.7.0.0 > ../deps/libccd/libgazebo_ccd.so.7.0.0 > ../deps/opende/OPCODE/libgazebo_opcode.so.7.0.0 -lBulletSoftBody > -lBulletDynamics -lBulletCollision -lLinearMath -lSimTKsimbody -lSimTKmath > -lSimTKcommon -lblas -llapack -lblas -llapack -ldl -lOgreRTShaderSystem > -lOgreMain -lpthread -lOgreTerrain -lOgrePaging -lOgreOverlay -lOgreMain > -lpthread -lOgreTerrain -lOgrePaging -lOgreOverlay > transport/libgazebo_transport.so.7.0.0 -lOgreRTShaderSystem -lOgreMain > -lOgreTerrain -lOgrePaging -lOgreOverlay -lOgreMain -lOgreTerrain > -lOgrePaging -lOgreOverlay -lGLU -lGL -lX11 msgs/libgazebo_msgs.so.7.0.0 > common/libgazebo_common.so.7.0.0 -ldl -lfreeimage -ltinyxml -lavcodec > -lavformat -lavutil -lcurl -lswscale -ltar -ltbb -latomic -lsdformat -lrt > -lgts -lm -lgthread-2.0 -lgmodule-2.0 -lglib-2.0 -lgdal -lprotobuf -lpthread > math/libgazebo_math.so.7.0.0 > /usr/lib/x86_64-linux-gnu/libignition-math2.so.2.3.0 -lboost_thread > -lboost_signals -lboost_system -lboost_filesystem -lboost_program_options > -lboost_regex -lboost_iostreams -lboost_date_time -lboost_chrono > -lboost_atomic -lpthread > -Wl,-rpath,/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/test:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/sensors:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/rendering:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/physics:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/util:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/deps/opende:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/deps/opende/GIMPACT:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/deps/opende/ou:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/deps/libccd:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/deps/opende/OPCODE:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/transport:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/msgs:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/common:/«BUILDDIR»/gazebo-7.0.0+dfsg/obj-x86_64-linux-gnu/gazebo/math: > > physics/libgazebo_physics.so.7.0.0: undefined reference to > `boost::re_detail::cpp_regex_traits_implementation::transform[abi:cxx11](char > const*, char const*) const' > physics/libgazebo_physics.so.7.0.0: undefined reference to > `boost::re_detail::cpp_regex_traits_implementation::transform_primary[abi:cxx11](char > const*, char const*) const' > collect2: error: ld returned 1 exit status The full build log is available from: http://people.debia
Bug#830227: xdffileio: FTBFS: install: cannot change permissions of 'debian/libxdffileio-dev/usr/share/doc/libxdffileio-dev': No such file or directory
reassign 830227 debhelper 9.20160702 forcemerge 830309 830227 affects 830227 src:xdffileio thanks The build fails because of debhelper because xdffileio use dh_installdocs --link-doc The bug has already been fixed in debhelper 9.20160709 This should close the bug Cheers, Nicolas Bourdaud
Processed: Re: Bug#830227: xdffileio: FTBFS: install: cannot change permissions of 'debian/libxdffileio-dev/usr/share/doc/libxdffileio-dev': No such file or directory
Processing commands for cont...@bugs.debian.org:
> reassign 830227 debhelper 9.20160702
Bug #830227 [src:xdffileio] xdffileio: FTBFS: install: cannot change
permissions of 'debian/libxdffileio-dev/usr/share/doc/libxdffileio-dev': No
such file or directory
Bug reassigned from package 'src:xdffileio' to 'debhelper'.
No longer marked as found in versions xdffileio/0.3-1.
Ignoring request to alter fixed versions of bug #830227 to the same values
previously set
Bug #830227 [debhelper] xdffileio: FTBFS: install: cannot change permissions of
'debian/libxdffileio-dev/usr/share/doc/libxdffileio-dev': No such file or
directory
Marked as found in versions debhelper/9.20160702.
> forcemerge 830309 830227
Bug #830309 {Done: Niels Thykier } [debhelper] freetype
FTBFS: install: cannot change permissions of
'debian/libfreetype6-dev/usr/share/doc/libfreetype6-dev': No such file or
directory
Bug #830330 {Done: Niels Thykier } [debhelper] re2: FTBFS:
install: cannot change permissions of
'debian/libre2-dev/usr/share/doc/libre2-dev': No such file or directory
Bug #830339 {Done: Niels Thykier } [debhelper] serf: FTBFS:
install: cannot change permissions of
'debian/libserf-dev/usr/share/doc/libserf-dev': No such file or directory
Bug #830361 {Done: Niels Thykier } [debhelper] monotone:
FTBFS: install: cannot change permissions of
'debian/monotone-doc/usr/share/doc/monotone-doc': No such file or directory
Bug #830374 {Done: Niels Thykier } [debhelper] rtfilter:
FTBFS: install: cannot change permissions of
'debian/librtfilter-dev/usr/share/doc/librtfilter-dev': No such file or
directory
Bug #830382 {Done: Niels Thykier } [debhelper]
riemann-c-client: FTBFS: install: cannot change permissions of
'debian/libriemann-client-dev/usr/share/doc/libriemann-client-dev': No such
file or directory
Bug #830391 {Done: Niels Thykier } [debhelper] linux-atm:
FTBFS: install: cannot change permissions of
'debian/atm-tools/usr/share/doc/atm-tools': No such file or directory
Bug #830393 {Done: Niels Thykier } [debhelper] p7zip: FTBFS:
install: cannot change permissions of
'debian/p7zip-full/usr/share/doc/p7zip-full': No such file or directory
Bug #830398 {Done: Niels Thykier } [debhelper] pmw: FTBFS:
install: cannot change permissions of 'debian/pmw-doc/usr/share/doc/pmw-doc':
No such file or directory
Bug #830405 {Done: Niels Thykier } [debhelper]
libnetfilter-cttimeout: FTBFS: install: cannot change permissions of
'debian/libnetfilter-cttimeout-dev/usr/share/doc/libnetfilter-cttimeout-dev':
No such file or directory
Bug #830408 {Done: Niels Thykier } [debhelper] zsh: FTBFS:
install: cannot change permissions of 'debian/zsh-doc/usr/share/doc/zsh-doc':
No such file or directory
Bug #830427 {Done: Niels Thykier } [debhelper] libgfshare:
FTBFS: install: cannot change permissions of
'debian/libgfshare-dev/usr/share/doc/libgfshare-dev': No such file or directory
Bug #830431 {Done: Niels Thykier } [debhelper] geda-gaf:
FTBFS: install: cannot change permissions of
'debian/libgeda-dev/usr/share/doc/libgeda-dev': No such file or directory
Bug #830442 {Done: Niels Thykier } [debhelper] cigi-ccl:
FTBFS: install: cannot change permissions of
'debian/libcigicl-dev/usr/share/doc/libcigicl-dev': No such file or directory
Bug #830443 {Done: Niels Thykier } [debhelper] keepass2:
FTBFS: install: cannot change permissions of
'debian/keepass2-doc/usr/share/doc/keepass2-doc': No such file or directory
Bug #830450 {Done: Niels Thykier } [debhelper] kyototycoon:
FTBFS: install: cannot change permissions of
'debian/kyototycoon-doc/usr/share/doc/kyototycoon-doc': No such file or
directory
Bug #830451 {Done: Niels Thykier } [debhelper] ekg2: FTBFS:
install: cannot change permissions of
'debian/ekg2-scripting-perl/usr/share/doc/ekg2-scripting-perl': No such file or
directory
Bug #830453 {Done: Niels Thykier } [debhelper] freetype:
FTBFS: install: cannot change permissions of
'debian/libfreetype6-dev/usr/share/doc/libfreetype6-dev': No such file or
directory
Bug #830466 {Done: Niels Thykier } [debhelper] eegdev:
FTBFS: install: cannot change permissions of
'debian/libeegdev-dev/usr/share/doc/libeegdev-dev': No such file or directory
Bug #830484 {Done: Niels Thykier } [debhelper] ekg2: FTBFS:
install: cannot change permissions of
'debian/ekg2-scripting-perl/usr/share/doc/ekg2-scripting-perl': No such file or
directory
Bug #830520 {Done: Niels Thykier } [debhelper] ekg2: FTBFS:
install: cannot change permissions of
'debian/ekg2-scripting-perl/usr/share/doc/ekg2-scripting-perl': No such file or
directory
Bug #830227 [debhelper] xdffileio: FTBFS: install: cannot change permissions of
'debian/libxdffileio-dev/usr/share/doc/libxdffileio-dev': No such file or
directory
Marked Bug as done
Added indication that 830227 affects
src:rtfilter,src:zsh,src:keepass2,src:monotone,src:freetype,src:eegdev,src:pmw,src:ekg2,src:re2,src:libgfshare,src:kyototycoon,src:linux-atm,src:serf,src:geda-gaf,src:libnetfilter-cttimeout,src:cigi-ccl
Bug#830681: marked as done (trilinos-all-dev: Updating binutils breaks trilinos)
Your message dated Thu, 21 Jul 2016 16:29:04 + with message-id and subject line Bug#830681: fixed in trilinos 12.6.3-2 has caused the Debian Bug report #830681, regarding trilinos-all-dev: Updating binutils breaks trilinos 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.) -- 830681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: trilinos-all-dev Version: 12.6.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, The latest update of binutils to version 2.26.1-1 makes it imopssible to compile against trilinos. The linker complains /usr/bin/ld: warning: libbfd-2.26-system.so, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so, not found (try using -rpath or -rpath-link) /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so: undefined reference to "bfd_openr" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so: riferimento non definito a "bfd_map_over_sections" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so: riferimento non definito a "bfd_close" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so: riferimento non definito a "bfd_check_format" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so: riferimento non definito a "bfd_check_format_matches" /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libtrilinos_teuchoscore.so: riferimento non definito a "bfd_init" collect2: error: ld returned 1 exit status The new target library is $apt-file search libbfd-2.26 binutils: /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so A similar problem was solved for PETSc package recently, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828987 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages trilinos-all-dev depends on: ii libtrilinos-amesos-dev 12.6.3-1 ii libtrilinos-amesos2-dev12.6.3-1 ii libtrilinos-anasazi-dev12.6.3-1 ii libtrilinos-aztecoo-dev12.6.3-1 ii libtrilinos-belos-dev 12.6.3-1 ii libtrilinos-epetra-dev 12.6.3-1 ii libtrilinos-epetraext-dev 12.6.3-1 ii libtrilinos-galeri-dev 12.6.3-1 ii libtrilinos-globipack-dev 12.6.3-1 ii libtrilinos-ifpack-dev 12.6.3-1 ii libtrilinos-ifpack2-dev12.6.3-1 ii libtrilinos-intrepid-dev 12.6.3-1 ii libtrilinos-isorropia-dev 12.6.3-1 ii libtrilinos-kokkos-dev 12.6.3-1 ii libtrilinos-komplex-dev12.6.3-1 ii libtrilinos-ml-dev 12.6.3-1 ii libtrilinos-moertel-dev12.6.3-1 ii libtrilinos-muelu-dev 12.6.3-1 ii libtrilinos-nox-dev12.6.3-1 ii libtrilinos-optipack-dev 12.6.3-1 ii libtrilinos-pamgen-dev 12.6.3-1 ii libtrilinos-phalanx-dev12.6.3-1 ii libtrilinos-pike-dev 12.6.3-1 ii libtrilinos-piro-dev 12.6.3-1 ii libtrilinos-pliris-dev 12.6.3-1 ii libtrilinos-rol-dev12.6.3-1 ii libtrilinos-rtop-dev 12.6.3-1 ii libtrilinos-rythmos-dev12.6.3-1 ii libtrilinos-sacado-dev 12.6.3-1 ii libtrilinos-shards-dev 12.6.3-1 ii libtrilinos-shylu-dev 12.6.3-1 ii libtrilinos-stokhos-dev12.6.3-1 ii libtrilinos-stratimikos-dev12.6.3-1 ii libtrilinos-teko-dev 12.6.3-1 ii libtrilinos-teuchos-dev12.6.3-1 ii libtrilinos-thyra-dev 12.6.3-1 ii libtrilinos-tpetra-dev 12.6.3-1 ii libtrilinos-tr
Processed: most: diff for NMU version 5.0.0a-2.4
Processing control commands: > tags 817586 + patch Bug #817586 [src:most] most: Removal of debhelper compat 4 Added tag(s) patch. > tags 817586 + pending Bug #817586 [src:most] most: Removal of debhelper compat 4 Added tag(s) pending. -- 817586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817586: most: diff for NMU version 5.0.0a-2.4
Control: tags 817586 + patch Control: tags 817586 + pending Dear maintainer, I've prepared an NMU for most (versioned as 5.0.0a-2.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Blind Blake and Charlie Spand: Hastings Street diff -u most-5.0.0a/debian/changelog most-5.0.0a/debian/changelog --- most-5.0.0a/debian/changelog +++ most-5.0.0a/debian/changelog @@ -1,3 +1,12 @@ +most (5.0.0a-2.4) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "Removal of debhelper compat 4": switch to debhelper compatibility +level 9. +(Closes: #817586) + + -- gregor herrmann Thu, 21 Jul 2016 18:32:49 +0200 + most (5.0.0a-2.3) unstable; urgency=low * Non-maintainer upload. diff -u most-5.0.0a/debian/compat most-5.0.0a/debian/compat --- most-5.0.0a/debian/compat +++ most-5.0.0a/debian/compat @@ -1 +1 @@ -4 +9 diff -u most-5.0.0a/debian/control most-5.0.0a/debian/control --- most-5.0.0a/debian/control +++ most-5.0.0a/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Benjamin Mako Hill Standards-Version: 3.9.1.0 -Build-Depends: debhelper (>=4), libslang2-dev, dpkg-dev (>= 1.16.0), chrpath +Build-Depends: debhelper (>= 9), libslang2-dev, dpkg-dev (>= 1.16.0), chrpath Package: most Architecture: any signature.asc Description: Digital Signature
Bug#829360: marked as done (dqcache-run: priority is standard but depends on optional packages)
Your message dated Thu, 21 Jul 2016 16:53:24 + with message-id and subject line Bug#829360: fixed in dq 20160720-1 has caused the Debian Bug report #829360, regarding dqcache-run: priority is standard but depends on optional packages 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.) -- 829360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dqcache-run Version: 20160621-1 Severity: serious Justification: Policy 2.5 Dear Maintainer, The dqcache-run package includes daemontools-run (Priority: optional) in Depends, but is Priority: standard. This is a violation of policy §2.5. I wonder why any of dq, dqcache, or dqcache-run are Priority: standard. Please consider reassigning all 3 packages to Priority: optional. Thanks. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: dq Source-Version: 20160720-1 We believe that the bug you reported is fixed in the latest version of dq, 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 829...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Mojžíš (supplier of updated dq 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: Wed, 20 Jul 2016 10:47:33 +0200 Source: dq Binary: dq dqcache dqcache-run Architecture: source Version: 20160720-1 Distribution: unstable Urgency: medium Maintainer: Jan Mojžíš Changed-By: Jan Mojžíš Description: dq - DNS/DNSCurve query tool dqcache- DNS/DNSCurve recursive server - binaries dqcache-run - DNS/DNSCurve recursive server - running under daemontools Closes: 829360 Changes: dq (20160720-1) unstable; urgency=medium . * New upstream version 20160720: - added strict forwardonly patch - removed inet_pton.* files * Priority: standard -> optional. (Closes: #829360) * dqcache-run: daemontools service renamed to dqcache Checksums-Sha1: 850b191ff3307998f0c23031b095eee3024b1be2 1907 dq_20160720-1.dsc 004940fdd10f40de781d9d2946726f12715f86d1 141822 dq_20160720.orig.tar.gz 36f37c19311fd660a3ab3620b63bd1aa5d6554c4 5484 dq_20160720-1.debian.tar.xz Checksums-Sha256: c01cfcac5172aacea53c753313cf4794b0f4d91b4b26b694b27bbfa9706b3156 1907 dq_20160720-1.dsc a5df8f02ba263b20a8e6f86658cd15a77fe388364582c92696da05b72c7ee036 141822 dq_20160720.orig.tar.gz 9fb61f7989c55e5e2ef68a5ee1bd3bfac11533bdcf4037fb125b3517e66bb98e 5484 dq_20160720-1.debian.tar.xz Files: 1090fc5c4464d1de1754b408f9fc1ed8 1907 net optional dq_20160720-1.dsc 630d4932b3edcae0df65c54fb19e7654 141822 net optional dq_20160720.orig.tar.gz cb8da3e0d5f625458133b88d55901283 5484 net optional dq_20160720-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXkPfSAAoJEDVzElWdHgZLIe8P/0GxelBlm9Og8Ze97V5XfzuO W4OClnlEJMN13O1a8xSI7ilUyvTPNYQUAKL02myf/EeSW2d7xEiqswYXrPOkJoKX TnQHlA60IzxfBsWlLh1ZP7RSLGfaD1sKnNZ7RA/KbWxJFoKXN+J5fpbzX3zRE4jz dapv6q/bM/A/cBMNainSiPblhvxATK6AvJ8u87bmC4zBPS6ANlHOJt3M7pUxDFcj 5EowBx/QMLpRI1r1/c/LTWCG8n/s2sKYvXY04Tkd1e71YyVbb040uvx+lJh8lWbG 582XbckLNTqH9k2lgIsCtHlhGCkAB3S2iiUqMkX55AeQefuYdwWj7Dm01K11BgC9 HH9drpQbJKMA42y5eWqDzkcUpVSxkltpUsnvqNfGGRs/30yTHQU//o6WCbyeGEzc 9xRraCgBJb/7ECubb7VFrY3NKSazAtg6fXERHtS/rYYHnsL079G9r/mvAMV/+Aj4 DH5/KujMIhMn5jFsUFbWte7j2DBdD5mhBtknrkUfouaPG5GESx1KlVxdcpeDyzdS 2eatXmr8duoBLAVtu0VxakNBorvaUeH2f2cauJ7InMBnCqPVzi0LgrP85i68fc/D XIW2yBHwuAjzt+xg0h7Zeug2QBP8U3cjoiD4/DxmcWbCMUy1/WvAxxIQASJRkDJ6 I3DpU6gz2o40qE4yVxBL =s9vt -END PGP SIGNATURE End Message ---
Bug#831863: marked as done (monkeytail,mtail: both ship /usr/bin/mtail)
Your message dated Thu, 21 Jul 2016 16:55:45 + with message-id and subject line Bug#831863: fixed in mtail 0.0+git20160716.f911b02-1 has caused the Debian Bug report #831863, regarding monkeytail,mtail: both ship /usr/bin/mtail 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.) -- 831863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: monkeytail,mtail Severity: serious Tags: sid User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 0.0+git20160704.35c4023-1 Control: found -1 0.3.2-3 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package mtail. Preparing to unpack .../mtail_0.0+git20160704.35c4023-1_amd64.deb ... Unpacking mtail (0.0+git20160704.35c4023-1) ... dpkg: error processing archive /var/cache/apt/archives/mtail_0.0+git20160704.35c4023-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/mtail', which is also in package monkeytail 0.3.2-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/mtail_0.0+git20160704.35c4023-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/mtail This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html monkeytail=0.3.2-3_mtail=0.0+git20160704.35c4023-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mtail Source-Version: 0.0+git20160716.f911b02-1 We believe that the bug you reported is fixed in the latest version of mtail, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated mtail 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: Thu, 21 Jul 2016 16:27:55 + Source: mtail Binary: mtail Architecture: source amd64 Version: 0.0+git20160716.f911b02-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Description: mtail - Extract monitoring data from logs for collection in a timeseries Closes: 831724 831863 Changes: mtail (0.0+git20160716.f911b02-1) unstable; urgency=medium . * Don't run race tests on any arch except amd64. Closes: #831724. * New upstream snapshot. * Conflict with monkeytail, which provides a binary with the same name. Closes: #831863. Checksums-Sha1: e8942e83805f0cd3b02b626bf46ad5f22aabf7fd 2168 mtail_0.0+git20160716.f911b02-1.dsc 7e76eba15f2feaa263dfbd24a328d81548d1fbc2 379350 mtail_0.0+git20160716.f911b02.orig.tar.gz 2600245c3510878b78a838786d8cc18b9e1471d4 5244 mtail_0.0+git20160716.f911b02-1.debian.tar.xz 1d343e193d6b245de0bd6d823b86bf43370e8007 1790690 mtail_0.0+git20160716.f911b02-1_amd64.deb Checksums-Sha256: 282b561129cef0c8c5837685728cf918299c0f838e785dc5a763d4d8f44fbd69 2
Bug#826807: blender: OpenJPEG removal
On Thu, 09 Jun 2016 10:29:23 +0200 "Mathieu Malaterre" wrote: > This is a continued operation since src:jasper removal for stretch > release. > > src:openjpeg will be removed from Debian for the stretch release (and > following that, the archive in general). For more information see: > http://bugs.debian.org/826805 > > It has been superseeded by src:openjpeg2 > > Your package uses src:openjpeg, so please either remove the JPEG2000 > functionality or move to the new API. You seem to use libjpeg-turbo already, and openjpeg support seems to be optional. If this can't get ported to openjpeg2 in time for Stretch, you could drop the openjpeg support. Cheers, Emilio
Bug#826814: gpac: OpenJPEG removal
On Thu, 09 Jun 2016 10:30:01 +0200 "Mathieu Malaterre" wrote: > This is a continued operation since src:jasper removal for stretch > release. > > src:openjpeg will be removed from Debian for the stretch release (and > following that, the archive in general). For more information see: > http://bugs.debian.org/826805 > > It has been superseeded by src:openjpeg2 > > Your package uses src:openjpeg, so please either remove the JPEG2000 > functionality or move to the new API. Ping? It looks like your package already uses libjpeg-turbo. Can we just drop the openjpeg support? If not, can you forward this upstream? This is the last key package still depending on openjpeg, and it is going to block its removal from Stretch. Thanks, Emilio
Bug#830333: marked as done (topal: FTBFS: build-dependency not installable: gnat-4.9)
Your message dated Thu, 21 Jul 2016 17:22:19 + with message-id and subject line Bug#830333: fixed in topal 75-2.1 has caused the Debian Bug report #830333, regarding topal: FTBFS: build-dependency not installable: gnat-4.9 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.) -- 830333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: topal Version: 75-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160707 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): > ┌──┐ > │ Install topal build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-topal-dummy : Depends: gnat-4.9 but it is not going to > be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/07/topal_75-2_unstable_reb.normal.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: topal Source-Version: 75-2.1 We believe that the bug you reported is fixed in the latest version of topal, 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 830...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated topal 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 Jul 2016 18:12:06 +0200 Source: topal Binary: topal Architecture: source Version: 75-2.1 Distribution: unstable Urgency: medium Maintainer: Phil Brooke Changed-By: Nicolas Boulenguez Description: topal - Links Pine and GnuPG together Closes: 830333 Changes: topal (75-2.1) unstable; urgency=medium . * Non maintainer upload. * Rebuild with gnat-6 and bump ALI version. Closes: #830333. Select gnatgcc (currently gcc-6) instead of gcc (currently gcc-5). Checksums-Sha1: c5789173adee79a4b33e18d3337a41c8d64c50fd 1668 topal_75-2.1.dsc 1bff62905ce16964df56e5ff3b832908b2a3c550 6329 topal_75-2.1.diff.gz Checksums-Sha256: a242b510196d8d89d2cc44ff1e941ef7393d909b911c11322676d8a8cc5e8d82 1668 topal_75-2.1.dsc 58fc2725f310e850c11201d6a4b4885b1a44b4cab6ca08bfb58e24ba413bc92b 6329 topal_75-2.1.diff.gz Files: f2d729eaf4564a803930ab412deaa446 1668 mail optional topal_75-2.1.dsc a73496b843642f5012699e81644b1146 6329 mail optional topal_75-2.1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJXg8u/AAoJELUqnPRJDfyNlp0QAIqHOuJPUk2p9i7uqV9RWsTU MiYK6eE0lA/WYJER6TzX7F2j1JnU1wrLwVZSvGScN1tsqPRj2b3oSXTjwhVqWUz/ Ue0HLmA3Pe6bHimksXztgVwASNkOXerDiz9CJsC9csHfqHWqGZiInMFVy6GQaqve H1Tv+v9RhCFjeezi3wyXmoZ8mEcwoz5kXN6pCJB7pdLE42exrdR93Y2Gxa2s5rr0 m2pKkbziUs3gW67gEyltPf75zsvCopW7OawlDPpSYpobxDRcTcf4n6eQ0dn9Bgsp RnyOHl69i7EGsjyiAxyXjuPt1idJIwnaYO2n/LGK1V1Udm44a8TA9bi4lw/B8DvN 8KsrKJAcisdY72al6Plj6EtstsKCxdRHk2fDNVxgoOigFrM4YhO2lnIlJTE3IsWO WXDYo9zM+gxLawwuqrSAL628l30/vj0g1qE2XjmJIu0sFZoHrILCB88kZurR3IcX QF7UBhK2YwRwGx7gVBxUKhrwti6bLoLyr3RuBGr0IKmA2qhMPzTgWM/0MotH02to OpRwGK4d1yEL9X1jo/3ErFS9D6XXT1U8t1kUuxSQ
Processed: RM: tidy -- RoQA; abandoned; superseded by tidy-html5
Processing control commands: > block -1 by 829178 829409 Bug #832045 [ftp.debian.org] RM: tidy -- RoQA; abandoned; superseded by tidy-html5 832045 was not blocked by any bugs. 832045 was not blocking any bugs. Added blocking bug(s) of 832045: 829409 and 829178 -- 832045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817373: bb: Removal of debhelper compat 4
Control: tag -1 + pending patch
Hi Logan and Uwe,
Logan Rosen wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
Logan: Thanks!
> * debian/compat: Bump to 9.
> * debian/control:
> - Build-depend on debhelper (>= 9).
> - Depend on ${misc:Depends}.
> * debian/rules:
> - Add recommended build-arch and build-indep targets.
> - Replace dh_clean -k with dh_prep.
I've had an unpublished and not yet uploaded NMU laying around with
these (and some more) changes, too.
> * debian/rules:
> - Don't ignore all distclean errors.
[...]
> * debian/copyright: Don't point to symlink GPL.
I've merged in these additional changes from Logan, too, and uploaded
it to DELAYED/10.
Uwe: Feel free to tell me if I should fast-forward it or if I should
delay it longer.
Full debdiff attached. It's 86kB unpacked due to the removal of
config.guess and config.sub from the .diff.gz (they were originating
from there).
Here's the relevant debdiff without the file removals:
diff -u bb-1.3rc1/debian/changelog bb-1.3rc1/debian/changelog
--- bb-1.3rc1/debian/changelog
+++ bb-1.3rc1/debian/changelog
@@ -1,3 +1,27 @@
+bb (1.3rc1-8.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Axel Beckert ]
+ * Move from no more supported debhelper compatibility level 4 to
+currently recommended level 9 and make debian/rules and debian/control
+more future-proof:
++ Change "dh_clean -k" to "dh_prep".
++ Remove explicit argument from dh_installchangelogs. (No more needed.)
++ Add recommended targets build-indep and build-arch.
++ Add ${misc:Depends} to Depends
++ Closes: #817373
+ * Remove config.guess and config.sub from Debian's .diff.gz and use
+dh_autotools-dev_{restore,update}config to provide up-to-date files at
+build time.
++ Add build-dependency on autotools-dev.
+
+ [ Logan Rosen ]
+ * debian/rules: Don't ignore all distclean errors.
+ * debian/copyright: Don't point to symlink GPL.
+
+ -- Axel Beckert Thu, 21 Jul 2016 19:21:48 +0200
+
bb (1.3rc1-8.4) unstable; urgency=medium
* Non-maintainer upload.
diff -u bb-1.3rc1/debian/compat bb-1.3rc1/debian/compat
--- bb-1.3rc1/debian/compat
+++ bb-1.3rc1/debian/compat
@@ -1 +1 @@
-4
+9
diff -u bb-1.3rc1/debian/control bb-1.3rc1/debian/control
--- bb-1.3rc1/debian/control
+++ bb-1.3rc1/debian/control
@@ -2,13 +2,13 @@
Section: games
Priority: optional
Maintainer: Uwe Hermann
-Build-Depends: debhelper (>> 4.0.0), libmikmod-dev, libaa1-dev (>= 1.4p5-28)
+Build-Depends: debhelper (>> 9), libmikmod-dev, libaa1-dev (>= 1.4p5-28),
autotools-dev
Standards-Version: 3.7.2.2
Homepage: http://aa-project.sourceforge.net/bb/
Package: bb
Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
Description: ASCII-art demo based on AAlib
This package contains a 'high quality audio-visual demonstration'
of ASCII-art using AAlib, a portable ASCII-art graphics library.
diff -u bb-1.3rc1/debian/copyright bb-1.3rc1/debian/copyright
--- bb-1.3rc1/debian/copyright
+++ bb-1.3rc1/debian/copyright
@@ -26,7 +26,7 @@
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
On Debian systems, the complete text of the GNU General
-Public License can be found in `/usr/share/common-licenses/GPL'.
+Public License can be found in `/usr/share/common-licenses/GPL-2'.
---
diff -u bb-1.3rc1/debian/rules bb-1.3rc1/debian/rules
--- bb-1.3rc1/debian/rules
+++ bb-1.3rc1/debian/rules
@@ -25,15 +25,17 @@
config.status: configure
dh_testdir
+ dh_autotools-dev_updateconfig
./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE)
--prefix=/usr --mandir=\$${prefix}/share/man --bindir=\$${prefix}/games
--datadir=\$${prefix}/share
# Don't use -rpath...
cat Makefile | sed 's/-Wl,-rpath,\/usr\/lib//g' > Makefile.new; sleep 1
mv Makefile.new Makefile
-build: build-stamp
-
-build-stamp: config.status
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
+build-stamp: config.status
dh_testdir
$(MAKE)
touch build-stamp
@@ -42,19 +44,14 @@
dh_testdir
dh_testroot
rm -f build-stamp
- -$(MAKE) distclean
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
- cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
- cp -f /usr/share/misc/config.guess config.guess
-endif
+ [ ! -f Makefile ] || $(MAKE) distclean
+ dh_autotools-dev_restoreconfig
dh_clean
install: build
dh_testdir
dh_testroot
- dh_clean -k
+ dh_prep
dh_installdirs
$(MAKE) install prefix=$(CURDIR)/debian/bb/usr
@@ -66,7 +63,7 @@
binary-arch: build install
dh_testdir
dh_testroot
- dh_installchangelogs ChangeLog
+ dh_installch
Processed: Re: Bug#817373: bb: Removal of debhelper compat 4
Processing control commands: > tag -1 + pending patch Bug #817373 [src:bb] bb: Removal of debhelper compat 4 Added tag(s) patch and pending. -- 817373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#829022: python-libarchive-c: FTBFS: tests/test_entry.py::test_check_archiveentry_with_unicode_and_binary_entries_zip2 FAILED
This test failure seems to be caused by a new libarchive version. According to ci.debian.net this test started first failing on 2016-06-01. The difference between this test run and the previous one (where this specific test still passed) is the version of libarchive13: 3.1.2-11.1 vs. 3.2.0-2. signature.asc Description: Digital signature
Processed: bug 829022 is forwarded to https://github.com/Changaco/python-libarchive-c/issues/34, tagging 829022
Processing commands for cont...@bugs.debian.org: > forwarded 829022 https://github.com/Changaco/python-libarchive-c/issues/34 Bug #829022 [src:python-libarchive-c] python-libarchive-c: FTBFS: tests/test_entry.py::test_check_archiveentry_with_unicode_and_binary_entries_zip2 FAILED Set Bug forwarded-to-address to 'https://github.com/Changaco/python-libarchive-c/issues/34'. > tags 829022 + upstream Bug #829022 [src:python-libarchive-c] python-libarchive-c: FTBFS: tests/test_entry.py::test_check_archiveentry_with_unicode_and_binary_entries_zip2 FAILED Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 829022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822476: python-django-authority: Package is useless
On Thu, 16 Jun 2016 16:00:02 -0300 Herbert Fortes wrote: > We have to wait a next release: > > https://github.com/jazzband/django-authority/issues/50#issuecomment-226319945 > > About Django 1.9. It seems that one will do a 'Pull Request' and the upstream will do the merge . regards, -- Herbert Parentes Fortes Neto (hpfn) signature.asc Description: This is a digitally signed message part
Bug#831768: radiotray stops at start a radiostream
Hi,
Firstly thanks for your report.
Could you provide what is your radiostream? and send please the complete
log again.
Are you using gnome 3 shell? if so, there's a bug about it #687007.
Best regards.
Elías Alejandro
On Tue, Jul 19, 2016 at 5:06 AM, Jörg Frings-Fürst
wrote:
> Package: radiotray
> Version: 0.7.3-6
> Severity: grave
>
>
> I get the console-messages:
>
> $ radiotray
> /usr/lib/python2.7/dist-packages/radiotray/XmlDataProvider.py:23:
> PyGIWarning: Gtk was imported without specifying a version first. Use
> gi.require_version('Gtk', '3.0') before import to ensure that the right
> version gets loaded.
> from gi.repository import Gtk
> /usr/lib/python2.7/dist-packages/radiotray/AudioPlayerGStreamer.py:64:
> FutureWarning: The behavior of this method will change in future versions.
> Use specific 'len(elem)' or 'elem is not None' test instead.
> if(cfg_provider._settingExists("buffer_size")):
> Sleep Timer, Stops playing after a predefined time, SleepTimerPlugin.py,
> Carlos Ribeiro
> StationSwitcher, Allows cycling through stations,
> StationSwitcherPlugin.py, Mark F
> HelloWorld, This is a test plugin, HelloWorld.py, Carlos Ribeiro
> started
> Notifications, Shows message notifications on the desktop,
> NotificationPlugin.py, Carlos Ribeiro
> /usr/share/radiotray/plugins/NotificationPlugin.py:25: PyGIWarning: Notify
> was imported without specifying a version first. Use
> gi.require_version('Notify', '0.7') before import to ensure that the right
> version gets loaded.
> from gi.repository import Notify
> Mate Media Keys, Controls Radio Tray through keyboard multimedia keys,
> MateMediaKeysPlugin.py, Ken
> Gnome Media Keys, Controls Radio Tray through keyboard multimedia keys,
> GnomeMediaKeysPlugin.py, Carlos Ribeiro
> History, Shows song history, HistoryPlugin.py, Carlos Ribeiro
> Could not bind to Gnome for Media Keys
> Abgebrochen
>
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages radiotray depends on:
> ii gir1.2-gtk-3.0 3.20.6-2
> ii gir1.2-keybinder-3.0 0.3.1-1
> ii gir1.2-notify-0.7 0.7.6-2
> ii gstreamer1.0-plugins-bad 1.8.2-1+b1
> ii gstreamer1.0-plugins-base 1.8.2-1
> ii gstreamer1.0-plugins-good 1.8.2-1
> ii gstreamer1.0-plugins-ugly 1.8.2-1
> ii python-dbus1.2.4-1
> ii python-gi 3.20.1-1
> ii python-glade2 2.24.0-4
> ii python-gst-1.0 1.8.2-1
> ii python-lxml3.6.0-1
> ii python-xdg 0.25-4
> pn python:any
>
> radiotray recommends no packages.
>
> radiotray suggests no packages.
>
> -- no debconf information
>
Bug#831863: [pkg-go] Bug#831863: Bug#831863: monkeytail, mtail: both ship /usr/bin/mtail
To be honest, I don't even know how to go about doing it. If you could file it that'd be great! Thanks, Martyn Smith On Fri, 22 Jul 2016 at 3:50 AM "Martín Ferrari" < mailto: > wrote: Martyn, On 20/07/16 19:31, Martyn Smith wrote: > Yeah, I'm not sure if anyone uses it, but it seems pretty pointless now, > I'd be quite happy for it to just disappear :-) Thanks for replying. I will make mtail conclict on monkeytail, so the bug can be closed. Would you file the removal bug with ftp.debian.org, or should I do it? Tincho. -- Martín Ferrari (Tincho)
Bug#831863: [pkg-go] Bug#831863: Bug#831863: monkeytail, mtail: both ship /usr/bin/mtail
On 21/07/16 19:35, Martyn Smith wrote: > To be honest, I don't even know how to go about doing it. > > If you could file it that'd be great! The simplest way is to run reportbug "ftp.debian.org" and follow the instructions. I can do it for you :) -- Martín Ferrari (Tincho)
Processed: Bug#830555 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 830555 pending Bug #830555 [src:foolscap] foolscap: accesses the internet during build Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830555: marked as pending
tag 830555 pending thanks Hello, Bug #830555 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: http://git.debian.org/?p=python-modules/packages/foolscap.git;a=commitdiff;h=6bae4dc --- commit 6bae4dc17b96e0619e4f5724ac1423521d4d0875 Author: Julian Taylor Date: Thu Jul 21 19:16:43 2016 +0200 New ustream release (Closes: #830555) diff --git a/debian/changelog b/debian/changelog index 338e146..7550a66 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,12 @@ -foolscap (0.10.1-3) UNRELEASED; urgency=medium +foolscap (0.12.0-1) unstable; urgency=medium + [ Ondřej Nový ] * Fixed VCS URL (https) - -- Ondřej Nový Tue, 29 Mar 2016 21:37:17 +0200 + [ Julian Taylor ] + * New ustream release (Closes: #830555) + + -- Julian Taylor Thu, 21 Jul 2016 19:16:05 +0200 foolscap (0.10.1-2) unstable; urgency=medium
Bug#830555: new Foolscap release available
On 21.07.2016 05:00, Brian Warner wrote: I've just released foolscap-0.12.0 to PyPI, which should fix this. We've deprecated a function that talks to the root nameservers, and this release removes the test that used to exercise that function. I think that was the only place which should be doing off-box network access (there's plenty of localhost access, of course, this being a networking package). I hope that will resolve the issue. Please let me know if there's anything I can do to help get this packaged and (most importantly) the auto-removal of Foolscap and Tahoe-LAFS resolved. hi, thanks for the quick release, the network access appears to be fixed in this release. I have pushed it to the debian git. Ramakrishnan, as there are a couple changes can you verify that tahoelafs still works correctly? I tried building the tahoe package but to my surprise it doesn't run any tests. Does tahoe have none or are they not run in the package build? cheers, Julian
Bug#812046: marked as done (open-vm-tools: FTBFS with GCC 6: dereferencing pointer)
Your message dated Thu, 21 Jul 2016 18:53:52 + with message-id and subject line Bug#812046: fixed in open-vm-tools 2:10.0.7-3227872-4.1 has caused the Debian Bug report #812046, regarding open-vm-tools: FTBFS with GCC 6: dereferencing pointer 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.) -- 812046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: open-vm-tools Version: 2:10.0.5-3227872-2 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 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. Note that only the first error is reported; there might be more. 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.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > UILDDIR>>/lib/include -I/<>/lib/include -Wdate-time > -D_FORTIFY_SOURCE=2 -DUSING_AUTOCONF=1 -DOPEN_VM_TOOLS -DUSE_VGAUTH > -I/usr/include -DUSE_ICU -DHAVE_ICU_38 -DVMX86_TOOLS -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE > -D_DEFAULT_SOURCE -DUSE_SSL_DIRECT -fPIC -Wno-deprecated-declarations -g -O2 > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror > -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas > -Wno-uninitialized -Wno-deprecated-declarations -Wno-unused-but-set-variable > -c asyncsocket.c -fPIC -DPIC -o .libs/asyncsocket.o > In file included from /<>/lib/include/hostinfo.h:35:0, > from asyncsocket.c:58: > /<>/lib/include/x86cpuid.h:912:51: error: result of '-2147483648 > << 1' requires 33 bits to represent, but 'int' only has 32 bits > [-Werror=shift-overflow=] > #define VMW_BIT_MASK(shift) (((1 << (shift - 1)) << 1) - 1) >^ > > /<>/lib/include/x86cpuid.h:916:34: note: in expansion of macro > 'VMW_BIT_MASK' > CPUID_##name##_MASK = VMW_BIT_MASK(size) << bitpos, \ > ^~~~ > > /<>/lib/include/x86cpuid.h:292:1: note: in expansion of macro > 'FIELD' > FIELD( 0, 0, EAX, 0, 32, NUMLEVELS, ANY, > FALSE) \ > ^ > > /<>/lib/include/x86cpuid.h:870:4: note: in expansion of macro > 'CPUID_FIELD_DATA_LEVEL_0' > CPUID_FIELD_DATA_LEVEL_0 \ > ^~~~ > > /<>/lib/include/x86cpuid.h:927:4: note: in expansion of macro > 'CPUID_FIELD_DATA' > CPUID_FIELD_DATA > ^~~~ > > /<>/lib/include/x86cpuid.h:912:51: error: result of '-2147483648 > << 1' requires 33 bits to represent, but 'int' only has 32 bits > [-Werror=shift-overflow=] > #define VMW_BIT_MASK(shift) (((1 << (shift - 1)) << 1) - 1) >^ > > /<>/lib/include/x86cpuid.h:918:34: note: in expansion of macro > 'VMW_BIT_MASK' > CPUID_INTERNAL_MASK_##name = VMW_BIT_MASK(size) << bitpos, \ > ^~~~ > > /<>/lib/include/x86cpuid.h:292:1: note: in expansion of macro > 'FIELD' > FIELD( 0, 0, EAX, 0, 32, NUMLEVELS, ANY, > FALSE) \ > ^ > > /<>/lib/include/x86cpuid.h:870:4: note: in expansion of macro > 'CPUID_FIELD_DATA_LEVEL_0' > CPUID_FIELD_DATA_LEVEL_0 \ > ^~~~ > > /<>/lib/include/x86cpuid.h:927:4: note: in expansion of macro > 'CPUID_FIELD_DATA' > CPUID_FIELD_DATA > ^~~~ > > /<>/lib/include/x86cpuid.h:912:51: error: result of '-2147483648 > << 1' requires 33 bits to represent, but 'int' only has 32 bits > [-Werror=shift-overflow=] > #define VMW_BIT_MASK(shift) (((1 << (shift - 1)) << 1) - 1) >^ > > /<>/lib/include/x86cpuid.h:916:34: note: in expansion of macro > 'VMW_BIT_MASK' > CPUID_##name##_MASK = VMW_BIT_MASK(size) << bitpos, \ > ^~~~ > > /<>/lib/include/x86cpuid.h:293:1: note: in expansion of macro > 'FIELD' > FIELD( 0, 0, EBX, 0, 32, VENDOR1, YES, > TRUE) \ > ^ > > /<>/lib/include/x86cpuid.h:870:4: note: in expansion of macro > 'CPUID_FIELD_DATA_LEVEL_0' > CPUID_FIELD_DATA_LEVEL_0
Bug#831221: marked as done (sqlobject-admin: fails to upgrade from 'testing' - trying to overwrite /usr/bin/sqlobject-admin)
Your message dated Thu, 21 Jul 2016 19:36:38 + with message-id and subject line Bug#831221: fixed in sqlobject 3.0.0+dfsg-2 has caused the Debian Bug report #831221, regarding sqlobject-admin: fails to upgrade from 'testing' - trying to overwrite /usr/bin/sqlobject-admin 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.) -- 831221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sqlobject-admin,python-sqlobject-doc Version: 3.0.0+dfsg-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 sqlobject-admin. Preparing to unpack .../sqlobject-admin_3.0.0+dfsg-1_all.deb ... Unpacking sqlobject-admin (3.0.0+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/sqlobject-admin_3.0.0+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/bin/sqlobject-admin', which is also in package python-sqlobject 2.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/sqlobject-admin_3.0.0+dfsg-1_all.deb Similar problems in python-sqlobject-doc: Selecting previously unselected package python-sqlobject-doc. Preparing to unpack .../python-sqlobject-doc_3.0.0+dfsg-1_all.deb ... Unpacking python-sqlobject-doc (3.0.0+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/python-sqlobject-doc_3.0.0+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/python-sqlobject', which is also in package python-sqlobject 2.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/python-sqlobject-doc_3.0.0+dfsg-1_all.deb cheers, Andreas python-sqlobject=2.2.1-1_sqlobject-admin=3.0.0+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sqlobject Source-Version: 3.0.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of sqlobject, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Nový (supplier of updated sqlobject 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: Thu, 21 Jul 2016 21:27:34 +0200 Source: sqlobject Binary: python-sqlobject python3-sqlobject python-sqlobject-doc sqlobject-admin Architecture: source Version: 3.0.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Ondřej Nový Description: python-sqlobject - Python 2 object relational manager providing an object interface python-sqlobject-doc - Documentation for SQLObject, a Python object relational manager f python3-sqlobject - Python 3 object relational manager providing an object interface sqlobject-admin - Helper applications for SQLObject, a Python ORM for databases Closes: 831221 Changes: sqlobject (3.0.0+dfsg-2) unstable; urgency=medium . * Team upload. * Added breaks+replaces of older python-sqlobject version (Closes: #831221) Checksums-Sha1: 39be960a79c00d88a18fb0f92c232291c268ac41 2376 sqlobject_3.0.0+dfsg-2.dsc ceea80cc9225426bae12d11263169c1019d08673 49936 sqlobject_3.0.0+dfsg-2.debian.tar.xz Checksums-Sha256: 25ef721f30e6b5715d7597742ada66fe49b868995093cc1523788438a9a46536 2376 sqlobject_3.0.0+dfsg-2.dsc 5c480a6551b327cb25b46fd7ade87314669ebe3dfabdaa12a0fbc9efd3c8ba12 49936 sqlobject_3.0.0+dfsg-2.debian.tar.xz Files: f8792026a56b36d7419665f61e09d103 2376 python optional sqlobject_3.0.0+dfsg-2.dsc 5d0cfeab05527834140736d05dbbd803 49936 python optional sqlobject_3.0.0+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXkSKoAAoJEDVzElWdHgZL0a4P/2vUUElj2k6UQiyPfog6d7i0 y0H1fI5rWI2rceUGNf+9UWvkuqHGJnfWfBfR+BO0FlnAJsY9ei8bDcTEUejh
Processed: Re-opening : wrong bug number!
Processing commands for cont...@bugs.debian.org:
> reopen 821990
Bug #821990 {Done: Julien Puydt } [gworldclock]
gworldclock: Build arch:all+arch:any but is missing build-{arch,indep} targets
Bug reopened
Ignoring request to alter fixed versions of bug #821990 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
821990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#832062: supertuxkart: source for GPL song Boom_boom_boom.ogg missing
Source: supertuxkart Version: 0.9.2-1 Severity: serious Justification: does not include source code of GPL licensed work Supertuxkart contains a song called "Boom boom boom" in Ogg Vorbis format. According to the credits and debian/copyright, this song is created by Matt Thomas, and is licensed under the GNU GPL v3 or later. The source of the .ogg file is missing. Although what consists the source of media assets can be unclear, I would like to point out that there is also a module tracker version of this song, which can reasonably considered the source, as it contains the score, the samples used and can be editted in any module editor: https://modarchive.org/index.php?request=view_by_moduleid&query=38184 This module contains the following text: > -kbx128- march 1993 > music for a crap amos > game written by my > brother.(only joking) There is also some doubt that Matt Thomas and kbx128 are the same person: http://forum.freegamedev.net/viewtopic.php?t=6562&p=66000 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Processed: tagging 831192
Processing commands for cont...@bugs.debian.org: > tags 831192 + pending Bug #831192 [src:icedove] icedove: FTBFS with GCC 6: ../../dist/include/mozilla/mozalloc.h:192:28: error: 'malloc' was not declared in this scope Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 831192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1
Package: intel-microcode Followup-For: Bug #828819 Dear Maintainer, thanks for clearing this up so quickly :). Just as a follow up, Tuxedo released a new BIOS version including microcode 0x8a and I tested that 3.20160607.1 doesn't fail with that anymore. Cheers Jochen
Bug#828883: marked as done (zope.interface: FTBFS: E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) for details)
Your message dated Thu, 21 Jul 2016 22:05:47 + with message-id and subject line Bug#828883: fixed in dh-python 2.20160721 has caused the Debian Bug report #828883, regarding zope.interface: FTBFS: E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) for details 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.) -- 828883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.interface Version: 4.1.3-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, zope.interface fails to build from source in unstable/amd64: [..] ** ** Starting build ** ** Package: zope.interface Version: 4.1.3-1 Build architecture: amd64 Date: Tue, 28 Jun 2016 20:59:21 +0200 Hostname: 294f62997282 Uname:Linux 294f62997282 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 (2016-05-16) x86_64 GNU/Linux /etc/timezone:Africa/Johannesburg ** ** Installing build dependencies ** ** dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'zope.interface-build-deps' in '../zope.interface-build-deps_4.1.3-1_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! Selecting previously unselected package zope.interface-build-deps. (Reading database ... 23073 files and directories currently installed.) Preparing to unpack zope.interface-build-deps_4.1.3-1_all.deb ... Unpacking zope.interface-build-deps (4.1.3-1) ... Reading package lists... Building dependency tree... Reading state information... Correcting dependencies... Done The following additional packages will be installed: libexpat1-dev libpython-all-dbg libpython-all-dev libpython-dbg libpython-dev libpython2.7 libpython2.7-dbg libpython2.7-dev libpython3-all-dbg libpython3-all-dev libpython3-dbg libpython3-dev libpython3.5 libpython3.5-dbg libpython3.5-dev python-all python-all-dbg python-all-dev python-dbg python-dev python-setuptools python-zope.event python2.7-dbg python2.7-dev python3-all python3-all-dbg python3-all-dev python3-dbg python3-dev python3-pkg-resources python3-setuptools python3-zope.event python3.5-dbg python3.5-dev Suggested packages: python2.7-gdbm-dbg python2.7-tk-dbg python-setuptools-doc python-gdbm-dbg python-tk-dbg python3-gdbm-dbg python3-tk-dbg Recommended packages: gdb The following NEW packages will be installed: libexpat1-dev libpython-all-dbg libpython-all-dev libpython-dbg libpython-dev libpython2.7 libpython2.7-dbg libpython2.7-dev libpython3-all-dbg libpython3-all-dev libpython3-dbg libpython3-dev libpython3.5 libpython3.5-dbg libpython3.5-dev python-all python-all-dbg python-all-dev python-dbg python-dev python-setuptools python-zope.event python2.7-dbg python2.7-dev python3-all python3-all-dbg python3-all-dev python3-dbg python3-dev python3-pkg-resources python3-setuptools python3-zope.event python3.5-dbg python3.5-dev 0 upgraded, 34 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 97.1 MB of archives. After this operation, 206 MB of additional disk space will be used. Get:1 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dbg amd64 2.7.12~rc1-2 [4409 kB] Get:2 http://httpredir.debian.org/debian sid/main amd64 libpython-dbg amd64 2.7.11-2 [19.8 kB] Get:3 http://httpredir.debian.org/debian sid/main amd64 libpython-all-dbg amd64 2.7.11-2 [1074 B] Get:4 http://httpredir.debian.org/debian sid/main amd64 libpython2.7 amd64 2.7.12~rc1-2 [1068 kB] Get:5 http://httpredir.debian.org/debi
Bug#831868: marked as done (python-jwt: ships /usr/lib/python2.7/dist-packages/.coverage)
Your message dated Thu, 21 Jul 2016 22:11:34 +
with message-id
and subject line Bug#831868: fixed in pyjwt 1.4.1-1
has caused the Debian Bug report #831868,
regarding python-jwt: ships /usr/lib/python2.7/dist-packages/.coverage
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.)
--
831868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-rows
Version: 0.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: clone -1 -2
Control: reassign -2 python-jwt 1.4.0-1
Control: retitle -2 python-jwt: ships /usr/lib/python2.7/dist-packages/.coverage
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
I do not know what this file is about, but it clearly does not belong
into a package, at least at this location.
(Maybe a bug against the python packaging helpers would be appropriate
to exclude it automatically?)
>From the attached log (scroll to the bottom...):
Selecting previously unselected package python-rows.
Preparing to unpack .../python-rows_0.2.0-1_all.deb ...
Unpacking python-rows (0.2.0-1) ...
dpkg: error processing archive
/var/cache/apt/archives/python-rows_0.2.0-1_all.deb (--unpack):
trying to overwrite '/usr/lib/python2.7/dist-packages/.coverage', which is
also in package python-jwt 1.4.0-1
Errors were encountered while processing:
/var/cache/apt/archives/python-rows_0.2.0-1_all.deb
cheers,
Andreas
python-jwt=1.4.0-1_python-rows=0.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pyjwt
Source-Version: 1.4.1-1
We believe that the bug you reported is fixed in the latest version of
pyjwt, 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 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniele Tricoli (supplier of updated pyjwt 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: Thu, 21 Jul 2016 00:07:43 +0200
Source: pyjwt
Binary: python-jwt python3-jwt
Architecture: source all
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Daniele Tricoli
Description:
python-jwt - Python implementation of JSON Web Token
python3-jwt - Python 3 implementation of JSON Web Token
Closes: 828131 831868
Changes:
pyjwt (1.4.1-1) unstable; urgency=medium
.
* New upstream release.
* Run "as-installed" tests (DEP8).
* debian/patches/01_do-not-use-pytest-runner.patch
- Drop since python{,3}-pytest-runner is in Debian.
* debian/rules
- Make the build reproducible. (Closes: #828131, #831868)
Thanks to Chris Lamb for report and patch.
Checksums-Sha1:
689288eee3e735377530fdcfac8eb0d3f6cc8db6 2448 pyjwt_1.4.1-1.dsc
034b4b5c449d7f8e72b73df9cd27a63b49b16a9d 30215 pyjwt_1.4.1.orig.tar.gz
33dd4e54ee3babc7b46d8b0b77ab2710de31258e 3808 pyjwt_1.4.1-1.debian.tar.xz
851c9ed02bf9b55d508fb564d1a8b4549229ee0a 14934 python-jwt_1.4.1-1_all.deb
2fe80aea6358fe98ff12639962d61d5472633f5f 14884 python3-jwt_1.4.1-1_all.deb
Checksums-Sha256:
963cb5daa3f0f554a545525b08cfc08fdc241cf2d90268facbe190ff137c1638 2448
pyjwt_1.4.1-1.dsc
74c1f43913fda2afd107bcee8b70b8d8d4f4936e640d42635bacc380aa9c8178 30215
pyjwt_1.4.1.orig.tar.gz
4f20c5eba66e3b972bbf201547aba8ca28fd941f6e12f026fbf5b56f19b2ad22 3808
pyjwt_1.4.1-1.debian.tar.xz
6a1e019d2b8f9168794b45a28085e3c854122af4ba3e15aefe184ed4c4f92a6a 14934
python-jwt_1.4.1-1_all.deb
1167898969ac94cb15307e3635289384c114f919d840abdf3dda6572176bc897 14884
python3-jwt_1.4.1-1_all.deb
Files:
d2d9f95baaa5565ed8d0ed69d2d91e35 2448 python optional pyjwt_1.4.1-1.dsc
4d3973dff8c791986200b3fdc2f46eac 30215 python optional pyjwt_1.4.1.orig.tar.gz
70895e74ecd7d90535705ee03d6bb89b 3808 python optional
pyjwt_1.4.1-1.debian.tar.xz
0abf21fad7b07d9959f3fc38d21f83c2 14934 python optional
python-jwt_1.4.1-1_all.deb
ec82db4da35b5465d06cd7573fb1dc4f 14884 python optional
python3-jwt_1.4.1-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJXkSxBAAoJEK728aKnR
Processed: Re: radiotray stops at start a radiostream
Processing commands for cont...@bugs.debian.org: > tag 831768 moreinfo Bug #831768 [radiotray] radiotray stops at start a radiostream Added tag(s) moreinfo. > tag 831768 = moreinfo Bug #831768 [radiotray] radiotray stops at start a radiostream Ignoring request to alter tags of bug #831768 to the same tags previously set > thanks. Stopping processing here. Please contact me if you need assistance. -- 831768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817586: most: diff for NMU version 5.0.0a-2.4
Hi Mako,
I've prepared an NMU for most (versioned as 5.0.0a-2.4) and
uploaded it to DELAYED/10.
This is not a minimal bugfix NMU, as this package has not been touched
by the maintainer since 2010 and could clearly do with an update, so
I've updated it. Mako - if you want to keep it all old and crufty then
feel free to override, or argue about the details if any of it offends
your sensibilities :-)
The patch looks fat because it reverts the patched (but still old)
config.{sub,guess} updates for proper use of dh_autoreconf (as
recommended on https://wiki.debian.org/Autoreconf), but this actually
results in a much smaller patch overall.
Changes made:
* Update the debhelper compat level (to get most back in the archive)
* Add build-arch/indep targets to stop it getting thrown out again for that
reason
* The above dh_autoreconf so it works with new arches
* Update to current policy (use dpkg-buildflags, misc:Depends,
remove uneeded dpkg-dev dependency)
* Split the 1.0-format patch into 4 quilt-format patches. This is most
controversial perhaps, but unless you hate the quilt format for some
reason, this seems helpful to me. This puts back a fix done this way
in the -2.2 NMU then reverted in the -2.3 NMU.
* Remove $CC=gcc forcing which breaks crossbuilding and is just poor form
* Remove out-of-date specific version mention in copyright file, and make
source reference generic, (as this wasn't really made from v4.7 source
anymore.)
If you don't like any of these things I'm happy to do a different upload.
Here is the 'meaningful' diff. Attached is the full diff, dominated by
config.* reversion changes.
HTH (I can't live without most on all my machines, hence being prompted to give
it some love :-)
diff -Nru most-5.0.0a/debian/changelog most-5.0.0a/debian/changelog
--- most-5.0.0a/debian/changelog2016-07-22 01:42:16.0 +0100
+++ most-5.0.0a/debian/changelog2016-07-22 01:27:30.0 +0100
@@ -1,3 +1,16 @@
+most (5.0.0a-2.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Bump debhelper compat to 9 (Closes: #817586)
+ * Update to policy 3.9.8 (use dpkg-buildflags,
+add build-arch/build-indep targets)
+ * Fix lintian issues (above plus missing misc:depends)
+ * Don't force $CC=gcc (breaks cross-building)
+ * Use dh_autoreconf to support new architectures
+ * Reinstate quiltification from 5.0.0a-2.2 NMU
+
+ -- Wookey Fri, 22 Jul 2016 01:26:53 +0100
+
most (5.0.0a-2.3) unstable; urgency=low
* Non-maintainer upload.
diff -Nru most-5.0.0a/debian/compat most-5.0.0a/debian/compat
--- most-5.0.0a/debian/compat 2016-07-22 01:42:16.0 +0100
+++ most-5.0.0a/debian/compat 2016-07-21 22:03:05.0 +0100
@@ -1 +1 @@
-4
+9
diff -Nru most-5.0.0a/debian/control most-5.0.0a/debian/control
--- most-5.0.0a/debian/control 2016-07-22 01:42:16.0 +0100
+++ most-5.0.0a/debian/control 2016-07-21 23:56:40.0 +0100
@@ -2,12 +2,12 @@
Section: text
Priority: optional
Maintainer: Benjamin Mako Hill
-Standards-Version: 3.9.1.0
-Build-Depends: debhelper (>=4), libslang2-dev, dpkg-dev (>= 1.16.0), chrpath
+Standards-Version: 3.9.8.0
+Build-Depends: debhelper (>=9), autotools-dev, dh-autoreconf, libslang2-dev,
chrpath
Package: most
Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Pager program similar to more and less
Most is a paging program that displays, one windowful at a time, the
contents of a file on a terminal. A status line at the bottom of the
diff -Nru most-5.0.0a/debian/copyright most-5.0.0a/debian/copyright
--- most-5.0.0a/debian/copyright2016-07-22 01:42:16.0 +0100
+++ most-5.0.0a/debian/copyright2016-07-21 22:22:44.0 +0100
@@ -3,7 +3,7 @@
This package was put together by Chris Fearnley ,
from the GNU sources, which I obtained from
- ftp://space.mit.edu/pub/davis/most/most4.7.tar.gz.
+ ftp://space.mit.edu/pub/davis/most/
Modifications for Debian GNU/Linux Copyright (C) 1995 Chris Fearnley.
diff -Nru most-5.0.0a/debian/patches/keys.patch
most-5.0.0a/debian/patches/keys.patch
--- most-5.0.0a/debian/patches/keys.patch 1970-01-01 01:00:00.0
+0100
+++ most-5.0.0a/debian/patches/keys.patch 2016-07-21 23:48:55.0
+0100
@@ -0,0 +1,11 @@
+--- most-5.0.0a.orig/lesskeys.rc
most-5.0.0a/lesskeys.rc
+@@ -57,3 +57,8 @@ setkey bob "p"
+ setkey goto_mark "'"
+ setkey find_file "E"
+ setkey edit "v"
++setkey bob "^[[7~"
++setkey eob "^[[8~"
++setkey bob "^[OH"
++setkey eob "^[OF"
++
diff -Nru most-5.0.0a/debian/patches/lzma-support.patch
most-5.0.0a/debian/patches/lzma-support.patch
--- most-5.0.0a/debian/patches/lzma-support.patch 1970-01-01
01:00:00.0 +0100
+++ most-5.0.0a/debian/patches/lzma-support.patch 2016-07-21
23:50:23.0 +0100
@@ -0,0 +1,44 @@
+--- most-5.0.0a.orig/src/file.c
most-5.0.0a/src/file.c
+@@ -77,7 +77,7 @@ static int create_gunzip_cmd (char
Bug#831733: marked as done (tomcat6: Don't include in Stretch)
Your message dated Fri, 22 Jul 2016 01:19:18 + with message-id and subject line Bug#832023: Removed package(s) from unstable has caused the Debian Bug report #831733, regarding tomcat6: Don't include in Stretch 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.) -- 831733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tomcat6 Version: 6.0.45+dfsg-1 Severity: serious Tags: stretch sid Tomcat 6 should not be included in Stretch since it reaches end-of-life on 31 December 2016. [1] There is now only one package that depends on libservlet2.5-java, libfreemarker-java. [2] I think it is realistic that we can resolve this issue too in the near future and the removal of src:tomcat6 should be doable. I suggest that we investigate whether bugs in src:tomcat6 and src:tomcat7 also apply to src:tomcat8 before we request the removal. Markus [1] https://tomcat.apache.org/tomcat-60-eol.html [2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-java-maintain...@lists.alioth.debian.org;tag=libservlet2.5-java --- End Message --- --- Begin Message --- Version: 6.0.45+dfsg-1+rm Dear submitter, as the package tomcat6 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/832023 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817316: marked as done (clean-crypto: Mandatory debian/compat for debhelper)
Your message dated Fri, 22 Jul 2016 01:20:54 + with message-id and subject line Bug#832065: Removed package(s) from unstable has caused the Debian Bug report #817316, regarding clean-crypto: Mandatory debian/compat for debhelper 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.) -- 817316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clean-crypto Severity: important Usertags: mandatory-debian-compat Hi, The package clean-crypto uses debhelper but does not have a debian/compat file. * Please add a debian/compat file at your earliest convenience. * This will become mandatory in the first debhelper upload after 15th of April. If your package is *also* affected by any of the following debhelper related deprecations, please consider fixing them at the same time: * debhelper compat 4 is deprecated and is expected to be removed on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Version: 1-1+rm Dear submitter, as the package clean-crypto has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/832065 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: 831878
Processing commands for cont...@bugs.debian.org: > tags 831878 pending Bug #831878 [cyphesis-cpp] cyphesis-cpp: fails to install in chroot: update-rc.d: error: no runlevel symlinks to modify, aborting! Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 831878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817586: most: diff for NMU version 5.0.0a-2.4
On Fri, 22 Jul 2016 02:09:52 +0100, Wookey wrote: > Hi Mako, Hi Wookey and Mako, > I've prepared an NMU for most (versioned as 5.0.0a-2.4) and > uploaded it to DELAYED/10. Good to see so much interest in most; I did an NMU (to DELAYED/2) a couple of hours before :) > This is not a minimal bugfix NMU, as this package has not been touched > by the maintainer since 2010 and could clearly do with an update, so > I've updated it. Mako - if you want to keep it all old and crufty then > feel free to override, or argue about the details if any of it offends > your sensibilities :-) I'd love to see your NMU with all those fixes get into the archive (compared to my minimal "just bump debhelper compat level"), so I've reschedule my NMU to DELAYED/12 (as a hopefully not needed fallback). > HTH (I can't live without most on all my machines, hence being prompted to > give it some love :-) Heh, same here :) Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Janis Joplin: Me And Bobby Mc Gee signature.asc Description: Digital Signature
Bug#817586: most: diff for NMU version 5.0.0a-2.4
On Fri, 22 Jul 2016 03:24:45 +0200, gregor herrmann wrote: > I'd love to see your NMU with all those fixes get into the archive > (compared to my minimal "just bump debhelper compat level"), so I've > reschedule my NMU to DELAYED/12 (as a hopefully not needed fallback). Or did I reschedule your NMU? Or was your NMU rejected and I rescheduled mine? Or something else? https://ftp-master.debian.org/deferred/ currently shows my .changes -- and nothing more from me or you :/ Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Joan Baez: No Woman No Cry signature.asc Description: Digital Signature
Bug#831814: [Pkg-phototools-devel] Bug#831814: lepton: CVE-2016-6234 CVE-2016-6235 CVE-2016-6236 CVE-2016-6237 CVE-2016-6238
On Tue, Jul 19, 2016 at 07:48:33PM +0200, Salvatore Bonaccorso wrote: > Source: lepton > Version: 1.0-2 > Severity: grave > Tags: security upstream > Justification: user security hole > > Hi, > > Multiple issues were found in lepton. The CVE request was at > http://www.openwall.com/lists/oss-security/2016/07/17/1 referencing > https://github.com/dropbox/lepton/issues/26 (note to compile with > address sanitizer to reproduce the issues). > > lepton got several CVE assigned in subsequent > http://www.openwall.com/lists/oss-security/2016/07/17/6 > > I'm not sure if current master fixes all the reported cases from #26. Hi, I tested all samples in GitHub #26 and the error outputs change from ASSERTION_FAILURE to UNSUPPORTED_JPEG in 1.2.1, so I think the issue is solved in that version. % lepton global_bof.jpeg lepton v1.0- header information is incomplete6556934 bytes needed to decompress this file BILL EXP1_EDGE: 268435456.0 vs 0.0 = 0.0% SIGN_EDGE: 268435456.0 vs 0.0 = 0.0% EXP1_DC: 268435456.0 vs 0.0 = 0.0% SIGN_DC: 268435456.0 vs 0.0 = 0.0% Overall 7x7: 0.0 vs 0.0 = 0.0% Overall Edge: 536870912.0 vs 0.0 = 0.0% Overall DC: 536870912.0 vs 0.0 = 0.0% Overall Misc: 0.0 vs 0.0 = 0.0% Total: 1073741824.0 vs 0.0 = 0.0% ASSERTION_FAILURE SHORT_READ% % ~/src/debian/lepton/lepton global_bof.jpeg lepton v1.0- 14882054 bytes needed to decompress this file UNSUPPORTED_JPEG SHORT_READ -- ChangZhuo Chen (陳昌倬) Debian Developer (https://nm.debian.org/public/person/czchen) Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature
Bug#831878: cyphesis-cpp: fails to install in chroot: update-rc.d: error: no runlevel symlinks to modify, aborting!
Hi Andreas, On 07/20/2016 08:50 AM, Andreas Beckmann wrote: Package: cyphesis-cpp Version: 0.6.0-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package cyphesis-cpp. (Reading database ... (Reading database ... 9077 files and directories currently installed.) Preparing to unpack .../cyphesis-cpp_0.6.0-4_amd64.deb ... Unpacking cyphesis-cpp (0.6.0-4) ... Setting up cyphesis-cpp (0.6.0-4) ... update-rc.d: error: no runlevel symlinks to modify, aborting! dpkg: error processing package cyphesis-cpp (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: cyphesis-cpp This may be related to the fact that piuparts installs the package in a minimal chroot, but I've never seen this error message from update-rc.d (but there have been quite some changes w.r.t. the initscript helpers recnetly) and most packages behave "sanely" in such a setup. You're right, it was a minor problem related to a change in update-rc.d. It's fixed now and pending upload. Thank you for reporting! -Olek
Bug#832075: libsvm: triggers ci file contains unknown directive 'activate-nowait'
Source: libsvm Version: 3.21+ds-1 Severity: serious Justification: renders package unusable Hi! While updating libsvm from 3.12-1.1 to 3.21+ds-1: = Preparing to unpack .../libsvm3_3.21+ds-1_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libsvm3_3.21+ds-1_amd64.deb (--unpack): triggers ci file contains unknown directive 'activate-nowait' Errors were encountered while processing: /var/cache/apt/archives/libsvm3_3.21+ds-1_amd64.deb = Thank you! Best regards, Nelson -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1
On Fri, 22 Jul 2016, Jochen Sprickerhof wrote: > thanks for clearing this up so quickly :). Just as a follow up, Tuxedo > released > a new BIOS version including microcode 0x8a and I tested that 3.20160607.1 > doesn't fail with that anymore. Yeah, information about their BIOS update was forwarded to this bug report :-) Also, Intel just issued a public update with microcode 0x9e, which apparently fixes the whole issue (intel microcode upstream release 20160714). Since Fedora has uploaded it already to their experimental branch, I am waiting for a day or two to see if anyone complains, and then uploading it to unstable. If anyone that is paying attention to this bug report would be willing to test the new microcode update on a i7-6500U or m3-6Y30, please contact me directly. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 832062 https://github.com/supertuxkart/stk-code/issues/2577 Bug #832062 [src:supertuxkart] supertuxkart: source for GPL song Boom_boom_boom.ogg missing Set Bug forwarded-to-address to 'https://github.com/supertuxkart/stk-code/issues/2577'. > End of message, stopping processing here. Please contact me if you need assistance. -- 832062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 831145 in 5.22.0-1
Processing commands for cont...@bugs.debian.org: > found 831145 5.22.0-1 Bug #831145 [src:kjsembed] kjsembed: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors Marked as found in versions kjsembed/5.22.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 831145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830727: Pending fixes for bugs in the golang-github-magiconair-properties package
tag 830727 + pending thanks Some bugs in the golang-github-magiconair-properties package are closed in revision 190f7cf864eda22eda8e652c3f7c9569acbc1c1a in branch 'master' by Dmitry Smirnov The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-magiconair-properties.git/commit/?id=190f7cf Commit message: Set "USER=nobody" in override_dh_auto_test to fix FTBFS (Closes: #830727).
Processed: Pending fixes for bugs in the golang-github-magiconair-properties package
Processing commands for cont...@bugs.debian.org: > tag 830727 + pending Bug #830727 [src:golang-github-magiconair-properties] golang-github-magiconair-properties: FTBFS: go test -v github.com/magiconair/properties [..] circular reference Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#830727: marked as done (golang-github-magiconair-properties: FTBFS: go test -v github.com/magiconair/properties [..] circular reference)
Your message dated Fri, 22 Jul 2016 05:18:31 + with message-id and subject line Bug#830727: fixed in golang-github-magiconair-properties 1.7.0-2 has caused the Debian Bug report #830727, regarding golang-github-magiconair-properties: FTBFS: go test -v github.com/magiconair/properties [..] circular reference 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.) -- 830727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-magiconair-properties Version: 1.7.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, golang-github-magiconair-properties fails to build from source in unstable/amd64: [..] ** ** Starting build ** ** Package: golang-github-magiconair-properties Version: 1.7.0-1 Build architecture: amd64 Date: Sun, 10 Jul 2016 22:25:55 +0200 Hostname: b6fcc713193c Uname:Linux b6fcc713193c 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 GNU/Linux /etc/timezone:Africa/Johannesburg ** ** Installing build dependencies ** ** dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'golang-github-magiconair-properties-build-deps' in '../golang-github-magiconair-properties-build-deps_1.7.0-1_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! Selecting previously unselected package golang-github-magiconair-properties-build-deps. (Reading database ... 23116 files and directories currently installed.) Preparing to unpack golang-github-magiconair-properties-build-deps_1.7.0-1_all.deb ... Unpacking golang-github-magiconair-properties-build-deps (1.7.0-1) ... Reading package lists... Building dependency tree... Reading state information... Correcting dependencies... Done The following additional packages will be installed: dh-golang golang-1.6-go golang-1.6-src golang-any golang-check.v1-dev golang-go golang-gopkg-check.v1-dev golang-src Suggested packages: bzr ca-certificates mercurial subversion Recommended packages: pkg-config The following NEW packages will be installed: dh-golang golang-1.6-go golang-1.6-src golang-any golang-check.v1-dev golang-go golang-gopkg-check.v1-dev golang-src 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 26.6 MB of archives. After this operation, 191 MB of additional disk space will be used. Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.18 [9278 B] Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-src amd64 1.6.2-2 [6784 kB] Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-go amd64 1.6.2-2 [19.7 MB] Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 2:1.6.1+1 [2974 B] Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 2:1.6.1+1 [21.9 kB] Get:6 http://httpredir.debian.org/debian sid/main amd64 golang-any amd64 2:1.6.1+1 [3100 B] Get:7 http://httpredir.debian.org/debian sid/main amd64 golang-gopkg-check.v1-dev all 0.0+git20160105.0.4f90aea-2 [29.9 kB] Get:8 http://httpredir.debian.org/debian sid/main amd64 golang-check.v1-dev all 0.0+git20160105.0.4f90aea-2 [3068 B] Fetched 26.6 MB in 0s (101 MB/s) Selecting previously unselected package dh-golang. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (R
Bug#832087: mps-youtube: Missing dependency python-pkg-resources
Package: mps-youtube Version: 0.01.46-3 Severity: serious Justification: 3 Dear Maintainer, I installed mps-youtube and tried to run it: $ mpsyt Traceback (most recent call last): File "/usr/bin/mpsyt", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources After debug it find out, that package python-pkg-resources is required to use mpsyt, and it is not listed as dependency in mps-youtube package. -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mps-youtube depends on: ii mplayer2 2.0-728-g2c378c7-4+b1 ii python 2.7.9-1 ii python-pafy 0.3.62-1 mps-youtube recommends no packages. mps-youtube suggests no packages. -- no debconf information
