Processed: severity of 758688 is serious
Processing commands for cont...@bugs.debian.org: severity 758688 serious Bug #758688 [libvirt-daemon-system] libvirt-daemon-system (1.2.7-9) dist-upgrade failed Bug #758759 [libvirt-daemon-system] postinst fails if virtlockd.service is masked Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 758688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758688 758759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755562: libkolabxml: FTBFS on all non-x86 archs due to symbols errors
Source: libkolabxml Version: 1.0.1-3 Followup-For: Bug #755562 Hi, Your package FTBFS on all autobuilders (so far), this time including i386. It seems to be due to symbol changes. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758886: closing 758886, closing 758901
close 758886 close 758901 thanks Further information on #756449 shows that u-boot-tools has been reinstated so I think nothing needs to be done for sunxi-tools any more, hence closing both bugs. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 758886, closing 758901
Processing commands for cont...@bugs.debian.org:
close 758886
Bug #758886 [ftp.debian.org] RM: sunxi-tools [powerpc] -- RoM; ANAIS; build
dependency removed
Marked Bug as done
close 758901
Bug #758901 {Done: Vagrant Cascadian vagr...@debian.org} [src:u-boot] please
build u-boot-tools on all architectures.
Bug 758901 is already marked as done; not doing anything.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
758886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758886
758901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758759: postinst fails if virtlockd.service is masked
Package: libvirt-daemon-system Version: 1.2.7-10+b1 Followup-For: Bug #758759 Dear Maintainer, * What led up to the situation? First update of libvirt packages after vanilla installation of jessie. * What exactly did you do (or not do) that was effective (or ineffective)? aptitude update aptitude safe-upgrade * What was the outcome of this action? all packages updated successfully despite libvirt-daemon-system and libvirt-bin. * What outcome did you expect instead? all packages updated successfully including libvirt-daemon-system and libvirt-bin ;-) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-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 Versions of packages libvirt-daemon-system depends on: ii adduser 3.113+nmu3 ii gettext-base 0.19.2-1 ii init-system-helpers 1.20 ii libapparmor1 2.8.0-5.1+b1 ii libaudit11:2.3.7-1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libblkid12.20.1-5.8 ii libc62.19-9 ii libcap-ng0 0.7.3-1.1 ii libdbus-1-3 1.8.6-1 ii libdevmapper1.02.1 2:1.02.85-2 ii libgnutls-deb0-283.2.16-1 ii libnl-3-200 3.2.24-2 ii libnl-route-3-2003.2.24-2 ii libnuma1 2.0.9-1 ii librados20.80.5-1 ii librbd1 0.80.5-1 ii libsasl2-2 2.1.26.dfsg1-11 ii libselinux1 2.3-1 ii libssh2-11.4.3-3 ii libsystemd-daemon0 208-6 ii libvirt-clients 1.2.7-10+b1 ii libvirt-daemon 1.2.7-10+b1 ii libvirt0 1.2.7-10+b1 ii libxml2 2.9.1+dfsg1-4 ii libyajl2 2.1.0-1 ii logrotate3.8.7-1 Versions of packages libvirt-daemon-system recommends: ii bridge-utils 1.5-9 ii dmidecode 2.12-3 ii dnsmasq-base 2.71-1 ii ebtables 2.0.10.4-3 ii iproute2 3.16.0-1 ii iptables 1.4.21-2 ii parted3.2-4 ii pm-utils 1.4.1-15 Versions of packages libvirt-daemon-system suggests: pn apparmor none pn auditd none ii policykit-1 0.105-6.1 pn radvdnone ii systemd 208-6 pn systemtapnone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754617: units-filter: FTBFS on kfreebsd-amd64/s390x: mpfr::mpreal::mpreal declarations etc.
Hello Cyril, I could verify at https://buildd.debian.org/status/package.php?p=units-filter that the package builds again on kfreebsd-amd64 and s390x. Best regards, Georges. Cyril Brulebois a écrit : Source: units-filter Version: 3.6-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-amd64 and s390x. Build excerpt: | g++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -g -c -DRECODE_SUPPORT=1 unitesparser.cc | In file included from unites.h:5:0, | from unites.y:6: | /usr/include/mpreal.h:174:5: error: 'mpfr::mpreal::mpreal(uint64_t, mpfr_prec_t, mpfr_rnd_t)' cannot be overloaded | mpreal(const uint64_t u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:164:5: error: with 'mpfr::mpreal::mpreal(long unsigned int, mpfr_prec_t, mpfr_rnd_t)' | mpreal(const unsigned long int u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:175:5: error: 'mpfr::mpreal::mpreal(int64_t, mpfr_prec_t, mpfr_rnd_t)' cannot be overloaded | mpreal(const int64_t u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:166:5: error: with 'mpfr::mpreal::mpreal(long int, mpfr_prec_t, mpfr_rnd_t)' | mpreal(const long int u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:221:13: error: 'mpfr::mpreal mpfr::mpreal::operator+=(int64_t)' cannot be overloaded | mpreal operator+=(const int64_t u); | ^ | /usr/include/mpreal.h:217:13: error: with 'mpfr::mpreal mpfr::mpreal::operator+=(long int)' | mpreal operator+=(const long int u); | ^ | /usr/include/mpreal.h:222:13: error: 'mpfr::mpreal mpfr::mpreal::operator+=(uint64_t)' cannot be overloaded | mpreal operator+=(const uint64_t u); | ^ | /usr/include/mpreal.h:215:13: error: with 'mpfr::mpreal mpfr::mpreal::operator+=(long unsigned int)' | mpreal operator+=(const unsigned long int u); | ^ | /usr/include/mpreal.h:241:13: error: 'mpfr::mpreal mpfr::mpreal::operator-=(long unsigned int)' cannot be overloaded | mpreal operator-=(const unsigned long int u); | ^ | /usr/include/mpreal.h:224:13: error: with 'mpfr::mpreal mpfr::mpreal::operator-=(uint64_t)' | mpreal operator-=(const uint64_t u); | ^ | /usr/include/mpreal.h:243:13: error: 'mpfr::mpreal mpfr::mpreal::operator-=(long int)' cannot be overloaded | mpreal operator-=(const long int u); | ^ | /usr/include/mpreal.h:223:13: error: with 'mpfr::mpreal mpfr::mpreal::operator-=(int64_t)' | mpreal operator-=(const int64_t u); | ^ | /usr/include/mpreal.h:260:13: error: 'mpfr::mpreal mpfr::mpreal::operator*=(long unsigned int)' cannot be overloaded | mpreal operator*=(const unsigned long int v); | ^ | /usr/include/mpreal.h:226:13: error: with 'mpfr::mpreal mpfr::mpreal::operator*=(uint64_t)' | mpreal operator*=(const uint64_t u); | ^ | /usr/include/mpreal.h:262:13: error: 'mpfr::mpreal mpfr::mpreal::operator*=(long int)' cannot be overloaded | mpreal operator*=(const long int v); | ^ | /usr/include/mpreal.h:225:13: error: with 'mpfr::mpreal mpfr::mpreal::operator*=(int64_t)' | mpreal operator*=(const int64_t u); | ^ | /usr/include/mpreal.h:271:13: error: 'mpfr::mpreal mpfr::mpreal::operator/=(long unsigned int)' cannot be overloaded | mpreal operator/=(const unsigned long int v); | ^ | /usr/include/mpreal.h:228:13: error: with 'mpfr::mpreal mpfr::mpreal::operator/=(uint64_t)' | mpreal operator/=(const uint64_t u); | ^ | /usr/include/mpreal.h:273:13: error: 'mpfr::mpreal mpfr::mpreal::operator/=(long int)' cannot be overloaded | mpreal operator/=(const long int v); | ^ | /usr/include/mpreal.h:227:13: error: with 'mpfr::mpreal mpfr::mpreal::operator/=(int64_t)' | mpreal operator/=(const int64_t u); | ^ | /usr/include/mpreal.h:703:8: error: redefinition of 'mpfr::mpreal::mpreal(uint64_t, mpfr_prec_t, mpfr_rnd_t)' | inline mpreal::mpreal(const uint64_t u, mp_prec_t prec, mp_rnd_t mode) | ^ | /usr/include/mpreal.h:670:8: error: 'mpfr::mpreal::mpreal(long unsigned int, mpfr_prec_t, mpfr_rnd_t)' previously defined here | inline mpreal::mpreal(const unsigned long int u, mp_prec_t prec, mp_rnd_t mode) | ^ | /usr/include/mpreal.h:711:8: error: redefinition of 'mpfr::mpreal::mpreal(int64_t, mpfr_prec_t, mpfr_rnd_t)' | inline mpreal::mpreal(const int64_t u, mp_prec_t prec, mp_rnd_t
Bug#754617: marked as done (units-filter: FTBFS on kfreebsd-amd64/s390x: mpfr::mpreal::mpreal declarations etc.)
Your message dated Sat, 23 Aug 2014 12:50:15 +0200 with message-id 20140823105015.ga32...@georges.khaznadar.fr and subject line Re: Bug#754617: units-filter: FTBFS on kfreebsd-amd64/s390x: mpfr::mpreal::mpreal declarations etc. has caused the Debian Bug report #754617, regarding units-filter: FTBFS on kfreebsd-amd64/s390x: mpfr::mpreal::mpreal declarations etc. 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.) -- 754617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: units-filter Version: 3.6-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-amd64 and s390x. Build excerpt: | g++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -g -c -DRECODE_SUPPORT=1 unitesparser.cc | In file included from unites.h:5:0, | from unites.y:6: | /usr/include/mpreal.h:174:5: error: 'mpfr::mpreal::mpreal(uint64_t, mpfr_prec_t, mpfr_rnd_t)' cannot be overloaded | mpreal(const uint64_t u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:164:5: error: with 'mpfr::mpreal::mpreal(long unsigned int, mpfr_prec_t, mpfr_rnd_t)' | mpreal(const unsigned long int u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:175:5: error: 'mpfr::mpreal::mpreal(int64_t, mpfr_prec_t, mpfr_rnd_t)' cannot be overloaded | mpreal(const int64_t u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:166:5: error: with 'mpfr::mpreal::mpreal(long int, mpfr_prec_t, mpfr_rnd_t)' | mpreal(const long int u, mp_prec_t prec = mpreal::get_default_prec(), mp_rnd_t mode = mpreal::get_default_rnd()); | ^ | /usr/include/mpreal.h:221:13: error: 'mpfr::mpreal mpfr::mpreal::operator+=(int64_t)' cannot be overloaded | mpreal operator+=(const int64_t u); | ^ | /usr/include/mpreal.h:217:13: error: with 'mpfr::mpreal mpfr::mpreal::operator+=(long int)' | mpreal operator+=(const long int u); | ^ | /usr/include/mpreal.h:222:13: error: 'mpfr::mpreal mpfr::mpreal::operator+=(uint64_t)' cannot be overloaded | mpreal operator+=(const uint64_t u); | ^ | /usr/include/mpreal.h:215:13: error: with 'mpfr::mpreal mpfr::mpreal::operator+=(long unsigned int)' | mpreal operator+=(const unsigned long int u); | ^ | /usr/include/mpreal.h:241:13: error: 'mpfr::mpreal mpfr::mpreal::operator-=(long unsigned int)' cannot be overloaded | mpreal operator-=(const unsigned long int u); | ^ | /usr/include/mpreal.h:224:13: error: with 'mpfr::mpreal mpfr::mpreal::operator-=(uint64_t)' | mpreal operator-=(const uint64_t u); | ^ | /usr/include/mpreal.h:243:13: error: 'mpfr::mpreal mpfr::mpreal::operator-=(long int)' cannot be overloaded | mpreal operator-=(const long int u); | ^ | /usr/include/mpreal.h:223:13: error: with 'mpfr::mpreal mpfr::mpreal::operator-=(int64_t)' | mpreal operator-=(const int64_t u); | ^ | /usr/include/mpreal.h:260:13: error: 'mpfr::mpreal mpfr::mpreal::operator*=(long unsigned int)' cannot be overloaded | mpreal operator*=(const unsigned long int v); | ^ | /usr/include/mpreal.h:226:13: error: with 'mpfr::mpreal mpfr::mpreal::operator*=(uint64_t)' | mpreal operator*=(const uint64_t u); | ^ | /usr/include/mpreal.h:262:13: error: 'mpfr::mpreal mpfr::mpreal::operator*=(long int)' cannot be overloaded | mpreal operator*=(const long int v); | ^ | /usr/include/mpreal.h:225:13: error: with 'mpfr::mpreal mpfr::mpreal::operator*=(int64_t)' | mpreal operator*=(const int64_t u); | ^ | /usr/include/mpreal.h:271:13: error: 'mpfr::mpreal mpfr::mpreal::operator/=(long unsigned int)' cannot be overloaded | mpreal operator/=(const unsigned long int v); | ^ | /usr/include/mpreal.h:228:13: error: with 'mpfr::mpreal mpfr::mpreal::operator/=(uint64_t)' | mpreal operator/=(const uint64_t u); | ^ | /usr/include/mpreal.h:273:13: error: 'mpfr::mpreal mpfr::mpreal::operator/=(long int)' cannot be overloaded | mpreal operator/=(const long int v); | ^ | /usr/include/mpreal.h:227:13: error: with 'mpfr::mpreal mpfr::mpreal::operator/=(int64_t)' | mpreal operator/=(const int64_t u);
Bug#758759: postinst fails if virtlockd.service is masked
Starting vlockd.service did allow the affected libvirt-packages to be updated: -8 systemctl start virtlockd.service aptitude safe-upgrade The following partially installed packages will be configured: libvirt-bin libvirt-daemon-system No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up libvirt-daemon-system (1.2.7-10+b1) ... Setting up libvirt-bin (1.2.7-10+b1) ... -8 The original issue seems to apply to the current version of libvirt-daemon-system: -8 systemctl stop virtlockd.service dpkg-reconfigure libvirt-daemon-system Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. Aug 23 13:04:51 osmium systemd[1]: Stopping Virtual machine lock manager... -- Subject: Unit virtlockd.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit virtlockd.service has begun shutting down. Aug 23 13:04:51 osmium systemd[1]: Stopped Virtual machine lock manager. -- Subject: Unit virtlockd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit virtlockd.service has finished shutting down. Aug 23 13:04:52 osmium systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. -8 Regards, Linus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758972: Please remove mojarra
Package: mojarra Version: 2.0.3-3 Severity: critical Tags: security Please remove mojarra source package from Debian as it has been unmaintained and contains several unfixed security vulnerabilities with no replies from maintainer. https://packages.debian.org/source/sid/mojarra http://packages.qa.debian.org/m/mojarra.html https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mojarra CVE-2012-2672: https://bugs.debian.org/677194 Jun 2012 CVE-2013-5855: https://bugs.debian.org/740586 Mar 2014 Moritz commented to this in private email: Unmaintained packages should be removed, but spring build-depends on one of the libs from mojarra: jmm@pisco:~$ build-rdeps libjsf-api-java Reverse Build-depends in main: -- libspring-java So it needs to be checked whether that can be dropped from Spring. If maintainer shows some activity I could help to get these issues fixed. --- Henri Salo signature.asc Description: Digital signature
Bug#758973: [fontconfig-config] Stop breaking user configuration in /etc/fonts/conf.d/ after every upgrade
Package: fontconfig-config Version: 2.11.0-6.1 Severity: serious Every time I change fontconfig configuration by removing symlinks in /etc/fonts/conf.d/ you return it back after upgrade. This is /etc and you should preserve local changes during package upgrades per policy (10.7.3). Regards, Vedran --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid --- Package information. --- Depends (Version) | Installed =-+-=== debconf (= 0.5) | 1.5.53 OR debconf-2.0 | ucf (= 0.29) | 3.0030 fonts-dejavu-core | 2.34-1 OR ttf-bitstream-vera| OR fonts-liberation | 2.00.1-1 OR fonts-freefont| -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758896: witty: FTBFS on all buildds: fails to remove /usr/share/doc/libwt-doc/examples': Directory not empty
I have now reproduced the issue. It's caused by doxygen 1.8.8-3 leaving a stale doxygen_sqlite3.db file, which 1.8.7 did not. I have implemented a fix and the package is rebuilding.
Bug#758760: [Pkg-gmagick-im-team] Bug#758760: dpkg-maintscript-helper: error: original symlink target is not an absolute path
Le 21 août 2014 02:03, 積丹尼 Dan Jacobson jida...@jidanni.org a écrit : Jidani could you retest ? Package: imagemagick-doc Preparing to unpack .../imagemagick-doc_8%3a6.8.9.6-2_all.deb ... dpkg-maintscript-helper: error: original symlink target is not an absolute path dpkg: error processing archive /var/cache/apt/archives/imagemagick-doc_8%3a6.8.9.6-2_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 dpkg-maintscript-helper: error: original symlink target is not an absolute path dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 1 ___ Pkg-gmagick-im-team mailing list pkg-gmagick-im-t...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gmagick-im-team
Bug#758688: [Pkg-libvirt-maintainers] Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed
On Fri, Aug 22, 2014 at 11:20:58AM +0900, d...@debian.org wrote: Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-10); however: Package libvirt-daemon-system is not configured yet. Could you try to dig out where the postinst is failing? I checked the case with virtlockd masked/unmasked and enabled/disabled and it didn't fail here. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758972: Please remove mojarra
On 08/23/2014 04:28 AM, Henri Salo wrote: Package: mojarra Version: 2.0.3-3 Severity: critical Tags: security Please remove mojarra source package from Debian as it has been unmaintained and contains several unfixed security vulnerabilities with no replies from maintainer. https://packages.debian.org/source/sid/mojarra http://packages.qa.debian.org/m/mojarra.html https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mojarra CVE-2012-2672: https://bugs.debian.org/677194 Jun 2012 CVE-2013-5855: https://bugs.debian.org/740586 Mar 2014 Moritz commented to this in private email: Unmaintained packages should be removed, but spring build-depends on one of the libs from mojarra: jmm@pisco:~$ build-rdeps libjsf-api-java Reverse Build-depends in main: -- libspring-java So it needs to be checked whether that can be dropped from Spring. If maintainer shows some activity I could help to get these issues fixed. --- Henri Salo Hi Henri, I'm not claiming that we shouldn't consider removing this, but we should be aware that there will be a considerable cascade effect from this. Without mojarra in the archive, src:libspring-java will not build, and taking a look at just one of the libspring-java binary packages, we see: $ reverse-depends -b libspring-web-java Reverse-Build-Depends-Indep === * acegi-security * activemq * jenkins * libshib-common-java * libxbean-java * mule * red5 * tiles Reverse-Build-Depends = * jasypt * libspring-security-2.0-java * libspring-webflow-2.0-java Now, let's see what happens with libxbean-java: $ reverse-depends -b libxbean-java Reverse-Build-Depends-Indep === * activemq * maven-plugin-tools * plexus-containers * plexus-containers1.5 As you continue to pull the thread (try plexus-containers), the cascade widens. All of those would become FTBFS and thus should also be removed. (And maybe that's the right thing to do - we need to talk about how much can be reasonably supported by the Java Team.) My request would be that we give this revisit this bug in a week's time (after DebConf). DC14 will be the first time for some members of the Java Team to meet face-to-face and get to discuss the state of team maintenance. Zooming back down to the specific issue at hand, we may be able to resolve the current CVEs quickly with an upload of mojarra 2.2.8. Packaging help is always welcome. Thank you, tony signature.asc Description: OpenPGP digital signature
Processed: Re: [Pkg-anonymity-tools] Bug#758935: torbrowser-launcher: fails to start: exit code 127
Processing control commands: severity -1 important Bug #758935 [torbrowser-launcher] torbrowser-launcher: fails to start: exit code 127 Severity set to 'important' from 'grave' tags -1 + unreproducible moreinfo Bug #758935 [torbrowser-launcher] torbrowser-launcher: fails to start: exit code 127 Added tag(s) unreproducible and moreinfo. -- 758935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758935: [Pkg-anonymity-tools] Bug#758935: torbrowser-launcher: fails to start: exit code 127
control: severity -1 important control: tags -1 + unreproducible moreinfo Hi Daniel, On Freitag, 22. August 2014, Daniel Gonzalez Gasull wrote: torbrowser-launcher fails to start. thanks for your bug report, but sadly I cannot reproduce it here, thus downgrading and tagging accordingly. * What led up to the situation? Starging torbrowser-launcher. * What was the outcome of this action? Window that said Tor Browser exited abnormally. Exit code: 127 what was the output in the shell? (if you didnt start from shell, please do so.) did you simply try to start again? cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: your mail
Processing commands for cont...@bugs.debian.org: found 758865 0.3.2.1.2-1 Bug #758865 [r-cran-rcppeigen] r-cran-rcppeigen: embedded copy of eigen3-library Marked as found in versions r-cran-rcppeigen/0.3.2.1.2-1. thanks Stopping processing here. Please contact me if you need assistance. -- 758865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758688: [Pkg-libvirt-maintainers] Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed
Hello, Guido As it's reproducible on my laptop also, below is the postinst traces and full file is attached. # apt-get -f install Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: linux-image-3.11-1-amd64 linux-image-3.11-2-amd64 linux-image-3.12-1-amd64 linux-image-3.13-1-amd64 linux-image-3.13-1-amd64-dbg linux-image-3.14-1-amd64-dbg Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up libvirt-daemon-system (1.2.7-10+b1) ... + set -e [snip] + [ -d /run/systemd/system ] + systemctl is-enabled virtlockd.service + systemctl reload virtlockd.service Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-10+b1); however: Package libvirt-daemon-system is not configured yet. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libvirt-daemon-system libvirt-bin To reproduce this, make the virtlockd.service inactive (it's already inactive on my laptop on upgrade, not by this command) # systemctl stop virtlockd.service Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket # apt-get install --reinstall libvirt-daemon-system Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/142 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 192685 files and directories currently installed.) Preparing to unpack .../libvirt-daemon-system_1.2.7-10+b1_amd64.deb ... Unpacking libvirt-daemon-system (1.2.7-10+b1) over (1.2.7-10+b1) ... Setting up libvirt-daemon-system (1.2.7-10+b1) ... Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libvirt-daemon-system E: Sub-process /usr/bin/dpkg returned an error code (1) Therefore, The patch to fix this is proposed earlier. Cheers, Neutron Soutmun Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: linux-image-3.11-1-amd64 linux-image-3.11-2-amd64 linux-image-3.12-1-amd64 linux-image-3.13-1-amd64 linux-image-3.13-1-amd64-dbg linux-image-3.14-1-amd64-dbg Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up libvirt-daemon-system (1.2.7-10+b1) ... + set -e + add_users_groups + getent group libvirt + getent group kvm + getent passwd libvirt-qemu + getent group libvirt-qemu + add_statoverrides + ROOT_DIRS=/var/lib/libvirt/images/ /var/lib/libvirt/boot/ /var/cache/libvirt/ + QEMU_DIRS= /var/lib/libvirt/qemu//var/cache/libvirt/qemu/ /var/lib/libvirt/qemu/channel/ /var/lib/libvirt/qemu/channel/target/ + SANLOCK_DIR=/var/lib/libvirt/sanlock + QEMU_CONF=/etc/libvirt/qemu.conf + dpkg-statoverride --list /var/lib/libvirt/images/ + [ ! -e /var/lib/libvirt/images/ ] + chown root:root /var/lib/libvirt/images/ + [ ! -e /var/lib/libvirt/images/ ] + chmod 0711 /var/lib/libvirt/images/ + dpkg-statoverride --list /var/lib/libvirt/boot/ + [ ! -e /var/lib/libvirt/boot/ ] + chown root:root /var/lib/libvirt/boot/ + [ ! -e /var/lib/libvirt/boot/ ] + chmod 0711 /var/lib/libvirt/boot/ + dpkg-statoverride --list /var/cache/libvirt/ + [ ! -e /var/cache/libvirt/ ] + chown root:root /var/cache/libvirt/ + [ ! -e /var/cache/libvirt/ ] + chmod 0711 /var/cache/libvirt/ + dpkg-statoverride --list /var/lib/libvirt/qemu/ + [ ! -e /var/lib/libvirt/qemu/ ] + chown libvirt-qemu:libvirt-qemu /var/lib/libvirt/qemu/ + [ ! -e /var/lib/libvirt/qemu/ ] + chmod 0750 /var/lib/libvirt/qemu/ + dpkg-statoverride --list /var/cache/libvirt/qemu/ + [ ! -e /var/cache/libvirt/qemu/ ] + chown libvirt-qemu:libvirt-qemu /var/cache/libvirt/qemu/ + [ ! -e /var/cache/libvirt/qemu/ ] + chmod 0750 /var/cache/libvirt/qemu/ + dpkg-statoverride --list /var/lib/libvirt/qemu/channel/ + [ ! -e /var/lib/libvirt/qemu/channel/ ] + chown
Bug#758972: data
No need to remove if we can update it and definitely not suggesting that we remove all those dependencies (original email did also not suggest that). Please contact me in case you need help with those CVEs when you have spare time (off BTS preferred). All I want is to close those vulnerabilities. --- Henri Salo signature.asc Description: Digital signature
Processed: severity of 758510 is serious
Processing commands for cont...@bugs.debian.org: # mark it RC, as update for wheezy-security done severity 758510 serious Bug #758510 [src:mediawiki] mediawiki: 1.19.18 fixes security vulnerabilities (CVE-2014-5241 CVE-2014-5243) Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 758510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 758688 758994
Processing commands for cont...@bugs.debian.org: forcemerge 758688 758994 Bug #758688 [libvirt-daemon-system] libvirt-daemon-system (1.2.7-9) dist-upgrade failed Bug #758759 [libvirt-daemon-system] postinst fails if virtlockd.service is masked Bug #758994 [libvirt-daemon-system] Can't install package because Unit virtlockd.service cannot be reloaded because it is inactive Severity set to 'serious' from 'important' Marked as found in versions libvirt/1.2.7-9 and libvirt/1.2.7-6. Bug #758759 [libvirt-daemon-system] postinst fails if virtlockd.service is masked Merged 758688 758759 758994 thanks Stopping processing here. Please contact me if you need assistance. -- 758688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758688 758759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758759 758994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758688: [Pkg-libvirt-maintainers] Bug#758688: Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed
On Sat, Aug 23, 2014 at 10:22:46PM +0700, Neutron Soutmun wrote: To reproduce this, make the virtlockd.service inactive (it's already inactive on my laptop on upgrade, not by this command) # systemctl stop virtlockd.service Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket That's exactly what I did (see my other reply) and with systemctl stop virtlockd.service systemctl reload virtlockd.service ; echo $? it returns 0 with systemd 204. Can you confirm it behaves differently with another version? If so we should report this to the systemd maintainers since it's a important behviour change. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754182: chromium-browser: FTBFS on amd64
On 2014-07-08 Bill Allombert ballo...@debian.org wrote: Package: chromium-browser Version: 35.0.1916.153-2 Severity: serious Hello Debian Chromium Maintainers, chromium-browser FTBFS on amd64. [...] It nowadays FTFS on sid for another different reason: g++-4.8: error: unrecognized command line option '-fstack-protector-strong' See https://lists.debian.org/debian-devel/2014/06/msg00453.html for the reason and https://lists.debian.org/debian-devel/2014/06/msg00625.html for the workaround. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731374:
Can't reproduce the bug in Debian testing, is there anything I'm missing?
The following NEW packages will be installed:
libapache2-mod-mono mono-apache-server{a} mono-apache-server4{a}
mono-xsp4-base{a}
0 packages upgraded, 4 newly installed, 0 to remove and 70 not upgraded.
Need to get 252 kB of archives. After unpacking 564 kB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://cdn.debian.net/debian/ unstable/main libapache2-mod-mono
i386 2.11+git20130708.6b73e85-4 [53.8 kB]
Get: 2 http://http.debian.net/debian/ testing/main mono-xsp4-base all
3.0.11-1 [69.0 kB]
Get: 3 http://http.debian.net/debian/ testing/main mono-apache-server4
all 3.0.11-1 [85.1 kB]
Get: 4 http://http.debian.net/debian/ testing/main mono-apache-server
all 3.0.11-1 [44.2 kB]
Fetched 252 kB in 3s (65.1 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of libapache2-mod-mono (→ 2.11+git20130708.6b73e85-4) Outstanding
#731374 - libapache2-mod-mono: Installation with aptitude install
libapache2-mod-mono hangs restarting apache2.
Summary:
libapache2-mod-mono(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y
Preconfiguring packages ...
Selecting previously unselected package mono-xsp4-base.
(Reading database ... 269125 files and directories currently installed.)
Preparing to unpack .../mono-xsp4-base_3.0.11-1_all.deb ...
Unpacking mono-xsp4-base (3.0.11-1) ...
Selecting previously unselected package mono-apache-server4.
Preparing to unpack .../mono-apache-server4_3.0.11-1_all.deb ...
Unpacking mono-apache-server4 (3.0.11-1) ...
Selecting previously unselected package mono-apache-server.
Preparing to unpack .../mono-apache-server_3.0.11-1_all.deb ...
Unpacking mono-apache-server (3.0.11-1) ...
Selecting previously unselected package libapache2-mod-mono.
Preparing to unpack
.../libapache2-mod-mono_2.11+git20130708.6b73e85-4_i386.deb ...
Unpacking libapache2-mod-mono (2.11+git20130708.6b73e85-4) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up mono-xsp4-base (3.0.11-1) ...
Setting up mono-apache-server4 (3.0.11-1) ...
Setting up mono-apache-server (3.0.11-1) ...
Setting up libapache2-mod-mono (2.11+git20130708.6b73e85-4) ...
Using mono-apache-server4...
Processing triggers for libc-bin (2.19-9) ...
Current status: 0 new [-17].
--
Braiam Peguero
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758999: gjiten: FTBFS due to conflicting (transitive) b-d libgnutls-dev - libgnomevfs2-dev
Package: gjiten Version: 2.6-2.2 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Hello, gjiten build-depends on libgnutls-dev and libgnomeui-dev, the latter depends on libgnomevfs2-dev which depends on libgnutls28-dev. The two gnutls development packages conflict with each other. gjiten also has a unused b-d on libgcrypt-dev. - Please drop it. Find attached a straightforward patch to fix these issues. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' diff -u gjiten-2.6/debian/control gjiten-2.6/debian/control --- gjiten-2.6/debian/control +++ gjiten-2.6/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Botond Botyanszki b...@users.sourceforge.net Uploaders: Ludovic Drolez ldro...@debian.org -Build-Depends: cdbs, debhelper ( 4.2.0), libgnomeui-dev, scrollkeeper, libxml-parser-perl, libgnutls-dev, libgcrypt-dev, docbook-utils, xmlto, libglade2-dev +Build-Depends: cdbs, debhelper ( 4.2.0), libgnomeui-dev, scrollkeeper, libxml-parser-perl, libgnutls28-dev, docbook-utils, xmlto, libglade2-dev Standards-Version: 3.8.0 Package: gjiten diff -u gjiten-2.6/debian/changelog gjiten-2.6/debian/changelog --- gjiten-2.6/debian/changelog +++ gjiten-2.6/debian/changelog @@ -1,3 +1,10 @@ +gjiten (2.6-2.3) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build against libgnutls28-dev, drop b-d on libgcrypt-dev. + + -- Andreas Metzler ametz...@debian.org Sat, 23 Aug 2014 18:14:24 +0200 + gjiten (2.6-2.2) unstable; urgency=low * Non-maintainer upload.
Bug#759000: remmina: FTBFS due to conflicting b-d libgnutls-dev vs. libvncserver-dev
Source: remmina Version: 1.0.0-6 Severity: serious Justification: fails to build from source (but built successfully in the past) Hello, remmina FTBFS since it has build-dependencies on libgnutls-dev and libvncserver-dev. The latter has been upgraded to GnuTLS v3 (libgnutls28-dev). remmina should also switch to GnuTLS v3. BTW upgrading from libgcrypt11-dev to libgcrypt20-dev should also be done. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758688: [Pkg-libvirt-maintainers] Bug#758688: Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed
On Sat, Aug 23, 2014 at 10:56 PM, Guido Günther a...@sigxcpu.org wrote: On Sat, Aug 23, 2014 at 10:22:46PM +0700, Neutron Soutmun wrote: To reproduce this, make the virtlockd.service inactive (it's already inactive on my laptop on upgrade, not by this command) # systemctl stop virtlockd.service Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket That's exactly what I did (see my other reply) and with systemctl stop virtlockd.service systemctl reload virtlockd.service ; echo $? it returns 0 with systemd 204. Can you confirm it behaves differently with another version? If so we should report this to the systemd maintainers since it's a important behviour change. # systemctl stop virtlockd.service systemctl reload virtlockd.service ; echo $? Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. 1 It returns 1 with systemd 208-8 Cheers, Neutron Soutmun -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Mojarra update 2.2.8
Processing control commands: owner -1 ! Bug #758972 [mojarra] Please remove mojarra Owner recorded as Markus Koschany a...@gambaru.de. -- 758972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758972: Mojarra update 2.2.8
Control: owner -1 ! Hi, I will investigate whether an update to 2.2.8 can resolve the issues with mojarra. I'll report back as soon as it's done. Markus signature.asc Description: OpenPGP digital signature
Bug#756780: Status bowtie + tophat (Was: [Help] Need help for architecture specific code)
Hi, currently we have tophat: Depends: bowtie2 | bowtie bowtie2:Architecture: amd64 kfreebsd-amd64 bowtie/1.0.1-1: Builds only on amd64 kfreebsd-amd64 [1,2] bowtie/1.1.0-1: Does not build at all (as reported on debian-mentors[3]) What can we do to get tophat and bowtie into testing? tophat: 1. tophat only Recommends: bowtie2 | bowtie or 2. tophat Architecture: amd64 kfreebsd-amd64 I think 1. is the better option bowtie: 1. upload 1.0.1-1 for Architecture: amd64 kfreebsd-amd64 only or 2. find a volunteer to fix the build issue 1.1.0-1 (I guess also in this case we need to restrict to amd64 anyway) I think 2. is the better option but if there is no volunteer I'd go for 1. Any opinions? Kind regards Andreas. [1] https://buildd.debian.org/status/package.php?p=bowtie [2] https://bugs.debian.org/756780 [3] https://lists.debian.org/debian-mentors/2014/08/msg00348.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving 733517, found 733517 in 0.8.6-1
Processing commands for cont...@bugs.debian.org:
unarchive 733517
Bug #733517 {Done: Scott Kitterman sc...@kitterman.com} [python-cffi] FTBFS
on Sparc and S390x
Unarchived Bug 733517
# Failing again on sparc...
found 733517 0.8.6-1
Bug #733517 {Done: Scott Kitterman sc...@kitterman.com} [python-cffi] FTBFS
on Sparc and S390x
Marked as found in versions python-cffi/0.8.6-1 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
733517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750910: Status of sitplus (Was: Bug#750910: sitplus: Please update to use wxwidgets3.0)
2014-08-22 2:55 GMT-05:00 Andreas Tille andr...@fam-tille.de: Hi Luis, Hi, Andreas. I had another look into sitplus 1.1.0 upstream and it seems there is a split between libsitplus and sitplus. From the download file layout libsitplus looks similar to our packaged sitplus 1.0.3 and the upstream sitplus-1.1.0 has a structure which I would consider broken considering that the root of the source tree is featuring only the dir /usr. Luis, you have spent some time into packaging sitplus but did not responded to later pings. It would help if you could raise your voice about your future plans with sitplus. If you stopped your engagement I'm afraid we can not keep this software inside Debian which would be a shame. My familiar situation has changed a lot since I packaged sitplus for the first time. I'm afraid I have very little free time, and I don't feel I can commit into maintaining this package anymore. I'm very sorry about that, and I would like to volunteer for this, but I just don't have the time. I'm CCing César Mauri, the upstream developer, just in case he wants to add something to the discussion. I also noticed that upstream is providing packages targeting at Squeeze which is lagging a behind current Debian development. Perhaps there is some chance to join forces here with upstream to provide recent upstream versions on recent Debian releases. However, if nobody volunteers for this job I would ask ftpmaster for removal from Debian since I have neither time nor the required background to test for this package. Kind regards Andreas. Regards. -- If you can't be a good example, then you'll just have to serve as a horrible warning -- Catherine Aird -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 733517 to FTBFS on Sparc
Processing commands for cont...@bugs.debian.org: retitle 733517 FTBFS on Sparc Bug #733517 [python-cffi] FTBFS on Sparc and S390x Changed Bug title to 'FTBFS on Sparc' from 'FTBFS on Sparc and S390x' thanks Stopping processing here. Please contact me if you need assistance. -- 733517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750910: Status of sitplus (Was: Bug#750910: sitplus: Please update to use wxwidgets3.0)
Hi Luis, On Sat, Aug 23, 2014 at 12:54:21PM -0500, Luis Rivas wrote: I had another look into sitplus 1.1.0 upstream and it seems there is a split between libsitplus and sitplus. From the download file layout libsitplus looks similar to our packaged sitplus 1.0.3 and the upstream sitplus-1.1.0 has a structure which I would consider broken considering that the root of the source tree is featuring only the dir /usr. Luis, you have spent some time into packaging sitplus but did not responded to later pings. It would help if you could raise your voice about your future plans with sitplus. If you stopped your engagement I'm afraid we can not keep this software inside Debian which would be a shame. feel I can commit into maintaining this package anymore. I'm very sorry about that, and I would like to volunteer for this, but I just don't have the time. Thanks for the clarification which is helpful to draw a reasonable decision whether we can keep the package or not. I'm CCing César Mauri, the upstream developer, just in case he wants to add something to the discussion. César, if you would be willing to spent some time into the packaging for Debian while we would be happy to help you in packaging questions we would consider keeping the package inside Debian. Otherwise I'm afraid that we need to drop it from the Debian mirrors. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706482: marked as done (gcc-msp430: generated interrupt table for MSP430FR5xxx parts will blow security fuse)
Your message dated Sat, 23 Aug 2014 19:03:37 + with message-id e1xlgbb-og...@franck.debian.org and subject line Bug#706482: fixed in gcc-msp430 4.6.3~mspgcc-20120406-7 has caused the Debian Bug report #706482, regarding gcc-msp430: generated interrupt table for MSP430FR5xxx parts will blow security fuse 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.) -- 706482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gcc-msp430 Version: 4.6.3~mspgcc-20120406-3 Severity: critical Moin, The current interrupt table code definitions in the gcc-msp430 and msp430mcu packages will lead to generate tables that go far into a reserved region of the MSP430 devices in case of the MSP430FR5xxx devices. Apperantly this region contains the passwords and lock code for device. Ie once this region is written to and the device reset, access over JTAG becomes impossible. See http://thread.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10623/focus=10627 for an explenation. The current gcc-msp/msp430mcu should be either fixed to not overwrite the reserved regions or refuse to generate code for those devices with an appropriate error message. Otherwise people will brick there devices with a supposedly safe procedure. Attila Kinali -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.5.4 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages gcc-msp430 depends on: ii binutils-msp430 2.22~msp20120406-2 ii libc62.13-38 ii libgmp10 2:5.0.5+dfsg-2 ii libmpc2 0.9-4 ii libmpfr4 3.1.0-5 ii msp430mcu20120406-2 Versions of packages gcc-msp430 recommends: ii msp430-libc 20120224-1 gcc-msp430 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: gcc-msp430 Source-Version: 4.6.3~mspgcc-20120406-7 We believe that the bug you reported is fixed in the latest version of gcc-msp430, 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 706...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Bruno lu...@debian.org (supplier of updated gcc-msp430 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: Sat, 23 Aug 2014 19:38:20 +0200 Source: gcc-msp430 Binary: gcc-msp430 Architecture: source Version: 4.6.3~mspgcc-20120406-7 Distribution: unstable Urgency: medium Maintainer: Luca Bruno lu...@debian.org Changed-By: Luca Bruno lu...@debian.org Description: gcc-msp430 - GNU C compiler (cross compiler for MSP430) Closes: 706482 Changes: gcc-msp430 (4.6.3~mspgcc-20120406-7) unstable; urgency=medium . * Fix generation of wrong interrupt table for MSP430FR5xxx targets, resulting in security fuse blown (Closes: #706482) Checksums-Sha1: 63e5c241c33e96304311424a177a96c37197a5fc 1423 gcc-msp430_4.6.3~mspgcc-20120406-7.dsc d356bc96252b630809b789f9ba9a864c742e2431 5384 gcc-msp430_4.6.3~mspgcc-20120406-7.debian.tar.xz Checksums-Sha256: d5aa35182303da48554a24b4823195ae27acee7e3f998fc2bc91af9e0c54e292 1423 gcc-msp430_4.6.3~mspgcc-20120406-7.dsc 75446161c3721f9e43a788f7c38619a862f8f0a6bb8b934bcaabc24bf982df08 5384 gcc-msp430_4.6.3~mspgcc-20120406-7.debian.tar.xz Files: 784d23bfdcb7e9f3d744d2bc30d0a189 1423 devel extra gcc-msp430_4.6.3~mspgcc-20120406-7.dsc 99f5543cb908f39757475b5c1b307378 5384 devel extra gcc-msp430_4.6.3~mspgcc-20120406-7.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlP40eEACgkQRqobajv7n7O/qACdFH5V3+ro/KaqMKpEOAwTSwmC WtAAn3fAXPSM7ZCqA5Nvydi65awEChNV =TEyn -END PGP SIGNATUREEnd Message---
Bug#758972: Mojarra update 2.2.8
On Sat, Aug 23, 2014 at 07:22:37PM +0200, Markus Koschany wrote: Control: owner -1 ! Hi, I will investigate whether an update to 2.2.8 can resolve the issues with mojarra. I'll report back as soon as it's done. Markus Hi Markus, I just had a very quick chat with Tony today (here @DebConf) about this bug. I reviewed 2.2.8 release and its packaging looks simpler than 2.0.x releases. If you have a fix and need sponsoring just let me know. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Processed: bug 733517 is forwarded to https://bitbucket.org/cffi/cffi/issue/162/bus-error-on-sparc
Processing commands for cont...@bugs.debian.org: forwarded 733517 https://bitbucket.org/cffi/cffi/issue/162/bus-error-on-sparc Bug #733517 [python-cffi] FTBFS on Sparc Set Bug forwarded-to-address to 'https://bitbucket.org/cffi/cffi/issue/162/bus-error-on-sparc'. thanks Stopping processing here. Please contact me if you need assistance. -- 733517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758760: [Pkg-gmagick-im-team] Bug#758760: dpkg-maintscript-helper: error: original symlink target is not an absolute path
BR == Bastien ROUCARIES roucaries.bast...@gmail.com writes: BR Jidani could you retest ? Yes it installs with no errors now I recall. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Splitting bug in two, one for sparc and one for kFreeBSD
Processing commands for cont...@bugs.debian.org: clone 755093 -1 Bug #755093 [src:cjs] cjs: FTBFS on kfreebsd and sparc Bug 755093 cloned as bug 759023 retitle -1 cjs: FTBFS on kFreeBSD Bug #759023 [src:cjs] cjs: FTBFS on kfreebsd and sparc Changed Bug title to 'cjs: FTBFS on kFreeBSD' from 'cjs: FTBFS on kfreebsd and sparc' retitle 755093 cjd: FTBFS on sparc Bug #755093 [src:cjs] cjs: FTBFS on kfreebsd and sparc Changed Bug title to 'cjd: FTBFS on sparc' from 'cjs: FTBFS on kfreebsd and sparc' thanks Stopping processing here. Please contact me if you need assistance. -- 755093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755093 759023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755093: Splitting bug in two, one for sparc and one for kFreeBSD
clone 755093 -1 retitle -1 cjs: FTBFS on kFreeBSD retitle 755093 cjd: FTBFS on sparc thanks We've added more output to cjs tests and changed how the tests are run, and now it's failing in different ways on kFreeBSD and sparc, so I'm splitting this in two as well. This is how it fails on sparc: Running dbus-run-session --config-file=./uninstalled-test-bus.conf -- ./test/run-with-dbus --system gtester Created config file ./uninstalled-test-bus.conf with ./test-services servicedir Running dbus-daemon --fork --print-pid --config-file=./uninstalled-system-test-bus.conf Created config file ./uninstalled-system-test-bus.conf with ./test-system-services servicedir Started bus pid 18234 at unix:abstract=/tmp/dbus-buildd-18223-4664-system Running with dbus: gtester --verbose gjs-tests gjs-unit with stderr to test_user_data/logs/stderr.log TEST: gjs-tests... (pid=18237) PASS: gjs-tests TEST: gjs-unit... (pid=18258) /js/0010basic: OK /js/0020importer:OK /js/0030basicBoxed: OK /js/0040mainloop:OK /js/ByteArray: OK /js/Cairo: FAIL GTester: last random seed: R02Se9ac46920eb80ea3a294415c5983ad4d killing message bus 18234 ./test/run-with-dbus: script gtester failed This is how it fails on kFreeBSD (both amd64 and i386): Running dbus-run-session --config-file=./uninstalled-test-bus.conf -- ./test/run-with-dbus --system gtester Created config file ./uninstalled-test-bus.conf with ./test-services servicedir Failed to start message bus: Operating system does not support abstract socket namespace dbus-run-session: EOF reading address from bus daemon -- Regards, Marga -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743596: gimp still built with lcms1
Is this something that can be taken care of with a binNMU after liblcms1 is removed? I'm not sure there's much I can do at this point beyond patching upstream.
Bug#755176: marked as done (mozjs: broken interpreter on 64-bit big endian platforms)
Your message dated Sat, 23 Aug 2014 21:34:33 + with message-id e1xlixf-0004jr...@franck.debian.org and subject line Bug#755176: fixed in mozjs 1.8.5-1.0.0+dfsg-4.2 has caused the Debian Bug report #755176, regarding mozjs: broken interpreter on 64-bit big endian platforms 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.) -- 755176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cjs Version: 2.2.1-2 Severity: serious Your package failed to build on kfreebsd, s390x and sparc. Although it hasn't built on those architectures in the past (and thus this bug shouldn't be RC), this is a cinnamon package and src:cinnamon is available on s390x and now requires cjs, making it unbuildable and thus out of date on that architecture. There are two options here: - Fix the cjs FTBFS - Request the removal of cinnamon on s390x. Emilio ---End Message--- ---BeginMessage--- Source: mozjs Source-Version: 1.8.5-1.0.0+dfsg-4.2 We believe that the bug you reported is fixed in the latest version of mozjs, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Margarita Manterola ma...@debian.org (supplier of updated mozjs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Aug 2014 13:50:01 -0700 Source: mozjs Binary: libmozjs185-1.0 libmozjs185-dev Architecture: source amd64 Version: 1.8.5-1.0.0+dfsg-4.2 Distribution: unstable Urgency: medium Maintainer: Chris Coulson chrisccoul...@ubuntu.com Changed-By: Margarita Manterola ma...@debian.org Description: libmozjs185-1.0 - Spidermonkey javascript engine libmozjs185-dev - Spidermonkey javascript library - development headers Closes: 755176 Changes: mozjs (1.8.5-1.0.0+dfsg-4.2) unstable; urgency=medium . * Non-maintainer upload. * Update debian/patches/64bit-big-endian.patch, backported from newer versions, to correctly support 64-bit big endian platforms. Thanks to Aurelien Jarno for the fix (Closes: #755176). Checksums-Sha1: 75e0e78583c45c7ff725f01e1d997f005f61b05c 2021 mozjs_1.8.5-1.0.0+dfsg-4.2.dsc 3d1c5335e0f1b125a8aef8804bf32a4832dd9786 50040 mozjs_1.8.5-1.0.0+dfsg-4.2.debian.tar.xz 3109ebf161a3332a1b0fac4b3c7ce4cfd805f94d 1097800 libmozjs185-1.0_1.8.5-1.0.0+dfsg-4.2_amd64.deb cad9ad12cef91977e4bd708eff2bc3e050974e9d 1542200 libmozjs185-dev_1.8.5-1.0.0+dfsg-4.2_amd64.deb Checksums-Sha256: 4ba3b3c8f9254c9b5f24f7c7c9d3f12331e5f354b4a18a1d4df548664dbb043b 2021 mozjs_1.8.5-1.0.0+dfsg-4.2.dsc ad997608880d53266205fe5640b477102e1838e6c3a89da7a8979fa88e09033c 50040 mozjs_1.8.5-1.0.0+dfsg-4.2.debian.tar.xz d175190d9d54e41b049d526f1d6372838070bbfa3ec08d03703f35a5896e58e0 1097800 libmozjs185-1.0_1.8.5-1.0.0+dfsg-4.2_amd64.deb d12324fd41f9a77ba0ae990533dbf650f6db931f3a01461cc8bb34ce9013dde0 1542200 libmozjs185-dev_1.8.5-1.0.0+dfsg-4.2_amd64.deb Files: ebb3657195dbaa5e0b12ff1fdf68518a 1097800 libs extra libmozjs185-1.0_1.8.5-1.0.0+dfsg-4.2_amd64.deb 808ff0a17755518deced6d5cd8ec9574 1542200 libdevel extra libmozjs185-dev_1.8.5-1.0.0+dfsg-4.2_amd64.deb 3ad0f81751c5b7deeb27b36f55145173 2021 libs extra mozjs_1.8.5-1.0.0+dfsg-4.2.dsc 4322623dd31d286d8afd00bd256000fb 50040 libs extra mozjs_1.8.5-1.0.0+dfsg-4.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT+QKRAAoJEIDQpC/yyFDKhNkQAJOkHEmZobb8GaDkBStF9LgX uuBee+Y1m1fI8iPwshzKEXNqNorY2mV3MAVWgNFJUPnm565NZJ1BNfX1Kzjo6fRp o4vBlSQOsLc7xq/BAWBV9MOteuyOsgpt1oF67qjDqwn6loOp645/wJ7ROWPqIhCi DZglcsr22mRy2xcw8+4i/j88ESUxnbQfzn5AkQId3/Rf9HcujQ3YUacDFc7GRes7 7MXHPl2CSUALBSLjntXl+v71mkcAdrrKnG9WmHLMEEwgO7LoM+SnDz9HF/Z+i1y8 W8MWuFk2VuyLFZhJL3GJUNmxHSNzm7/ZNVL0gh9hWYMY1MegRYhRuffOfgofZG+5 XZ+Oo3cu4gPjK4JRxJdusbow4t37EpRAw5D5EoLPAhn580f1jBPFrNpL0klJpS2q QIfVjmJ8G0r1t8Qt/LuxrCUglLObxUzH6pNpvYRxwjMxKfapryyw5P8LBZ2MbIII jINHb6qBauPRoX+kWSOAATpl/X39pmIyiSq02MQcdWosXlpL0T+LMoU3CYLRpqnq Ro4j0y2pODBKXuQ0jFOLOiSF9NeVbUbOCcRKbrH8B1Pq/7fL23QVd61RK4AWpMbI 8iVpq9RaPUWT1NZ1LiOhRvhtiz6eBpWMphJ4ey2drU8zH5qOOVi9d2J/jGVo8C3X yiqiWKzy4kvkHvqBXH8h =L7+I -END PGP
Bug#759031: init-select: Offers not installed inits, confusing error messages, unhelpfull description
Package: init-select Version: 1.20140309 Severity: serious Dear Maintainer, I am sorry if this report comes too harsh but my impression is that this package is not suitable for a release and therefore I have set the Severity that way. Feel free to change but please with sufficient reasons. Things that make me not comfortable: a) the debconf selection was not displayed to me when I first installed the package. Why? No idea. Running dpkg-reconfigure init-select later has displayed that selection menu. b) the menu displays all four inits regardless of which is installed. This is utterly misleading. It should not display the not available ones or report visibly that they are not there and user has to do in order to fix it. c) the package does not do anything if you specify a wrong one d) it's not clear what to do with this package anyway. The description is almost worthless. The manual pages are hard to find (try apropos init-select) and don't explain much. Running with -h or --help or no option has weird results: # set-init /sbin/set-init: 3: /sbin/set-init: cannot create : Directory nonexistent Huh? # get-init -h So, sorry, that is by far not the user experience which I expect from a package which touches the essential parts of the system. Regards, Eduard. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages init-select depends on: ii debconf [debconf-2.0] 1.5.53 Versions of packages init-select recommends: ii grub-pc 2.02~beta2-11 Versions of packages init-select suggests: ii systemd 208-7 -- debconf information: * init-select/choose: sysvinit init-select/no-upstart: init-select/no-systemd: init-select/no-openrc: -- Rhonda Im Amazon find ich nur englische Thesauren, das ist ja krank Rhonda Thesaurüsse? Rhonda Ah! Thesauri. youam Thesaurier? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732697: /usr/sbin/dibbler-client: dibbler_client: segfaults in TClntCfgMgr::validateConfig
Hello, On Wed, Jul 02, 2014 at 09:26:33AM +0200, Raphael Hertzog wrote: Hello Tomasz, On Fri, 20 Dec 2013, Tomasz Mrugalski wrote: Thanks for this bug report. I'm an original Dibbler author, and used to be also Debian package maintainer (I'm not one anymore). There is a fix You're still listed as Maintainer of the Debian package. Is Bartosz Fenski fe...@debian.org the new Debian maintainer ? If yes, Bartosz, can you take care of uploading a new packages with your name as Maintainer and drop Tomasz ? Please package a new upstream snapshot fixing that bug unless a new upstream release is prepared soon (see questions below). Still no news about updating the package to 1.0.0RC2 from upstream? Benpro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758896: marked as done (witty: FTBFS on all buildds: fails to remove /usr/share/doc/libwt-doc/examples': Directory not empty)
Your message dated Sat, 23 Aug 2014 23:07:32 + with message-id e1xlkpe-0002vo...@franck.debian.org and subject line Bug#758896: fixed in witty 3.3.3+dfsg-4 has caused the Debian Bug report #758896, regarding witty: FTBFS on all buildds: fails to remove /usr/share/doc/libwt-doc/examples': Directory not empty 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.) -- 758896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: witty Version: 3.3.3+dfsg-3 Severity: serious Justification: FTBFS Hi, your package FTBFS everywhere so far due to: | make[1]: Leaving directory '/«BUILDDIR»/witty-3.3.3+dfsg/build-shared' | mkdir -p /«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/libwt-doc/ | mkdir -p /«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/witty-examples/ | cp -R /«BUILDDIR»/witty-3.3.3+dfsg/doc/* /«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/libwt-doc/ | mv /«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/libwt-doc/examples/html /«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/witty-examples/ | rmdir /«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/libwt-doc/examples | rmdir: failed to remove '/«BUILDDIR»/witty-3.3.3+dfsg/debian/tmp/usr/share/doc/libwt-doc/examples': Directory not empty | make: *** [install] Error 1 | debian/rules:181: recipe for target 'install' failed Full build logs linked from: https://buildd.debian.org/status/package.php?p=wittysuite=sid Probably reproducible locally by passing -B to dpkg-buildpackage. Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: witty Source-Version: 3.3.3+dfsg-4 We believe that the bug you reported is fixed in the latest version of witty, 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 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pau Garcia i Quiles pgqui...@elpauer.org (supplier of updated witty package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Aug 2014 13:49:34 +0200 Source: witty Binary: libwt-common libwt38 libwt-dev libwthttp38 libwthttp-dev libwtfcgi38 libwtfcgi-dev libwttest8 libwttest-dev libwtext38 libwtext-dev libwtdbo38 libwtdbo-dev libwtdbosqlite38 libwtdbosqlite-dev libwtdbopostgres38 libwtdbopostgres-dev libwtdbofirebird38 libwtdbofirebird-dev libwtdbomysql38 libwtdbomysql-dev libwt-dbg libwt-doc witty-examples witty witty-dbg witty-dev witty-doc Architecture: source all amd64 Version: 3.3.3+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Pau Garcia i Quiles pgqui...@elpauer.org Changed-By: Pau Garcia i Quiles pgqui...@elpauer.org Description: libwt-common - C++ library and application server for web applications [common] libwt-dbg - C++ library and application server for web applications [debug] libwt-dev - C++ library and application server for web applications [developm libwt-doc - C++ library and application server for web applications [doc] libwt38- C++ library and application server for web applications [runtime] libwtdbo-dev - Wt::Dbo ORM library for Wt [development] libwtdbo38 - Wt::Dbo ORM library for Wt [runtime] libwtdbofirebird-dev - Firebird backend for Wt::Dbo [development] libwtdbofirebird38 - Firebird backend for Wt::Dbo [runtime] libwtdbomysql-dev - MySQL/MariaDB backend for Wt::Dbo [development] libwtdbomysql38 - MySQL/MariaDB backend for Wt::Dbo [runtime] libwtdbopostgres-dev - PostgreSQL backend for Wt::Dbo [development] libwtdbopostgres38 - PostgreSQL backend for Wt::Dbo [runtime] libwtdbosqlite-dev - sqlite3 backend for Wt::Dbo [development] libwtdbosqlite38 - sqlite3 backend for Wt::Dbo [runtime] libwtext-dev - additional widgets for Wt, based on ExtJS 2.0.x [development] libwtext38 - additional widgets for Wt, based on ExtJS 2.0.x [runtime] libwtfcgi-dev - FastCGI connector library for Wt [development] libwtfcgi38 - FastCGI connector library for Wt [runtime] libwthttp-dev - HTTP(S) connector library for Wt [development] libwthttp38 - HTTP(S) connector library for Wt [runtime] libwttest-dev - test connector library for Wt [development] libwttest8 -
Bug#755705: cyrus-imapd-2.4: still not binNMU safe
Control: reopen -1 Hi, On Wed, Aug 06, 2014 at 08:47:23AM +0200, Ondřej Surý wrote: Subject: Closed in 2.4.17+caldav~beta10-1 The problem isn't solved yet: the transitional packages cyrus-admin-2.4, cyrus-dev-2.4 and libcyrus-imap-perl24 are arch all, but they have a strict versioned depend on cyrus-common, which is arch: any, and has a different version after a binnmu. I guess the misc::depends is not necessary for the transitional packages. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cyrus-imapd-2.4: still not binNMU safe
Processing control commands:
reopen -1
Bug #755705 {Done: Ondřej Surý ond...@sury.org} [src:cyrus-imapd-2.4]
cyrus-imapd-2.4: not binNMU safe
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions cyrus-imapd-2.4/2.4.17+caldav~beta10-1.
--
755705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759041: db5.3: not binNMU safe
package: db5.3 version: 5.3.28-5 severity: serious Hi, It seems db5.3 is not binnmu safe. On s390x, there was a binnmu, with version 5.3.28-5+b1. This makes libdb5.3-java uninstallable on s390x, as it depends on libdb5.3 5.3.28-5, which is no longer available (only 5.3.28-5+b1 is available). Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751277: python-biopython: FTBFS on mips* powerpc s390x
Hi Andreas, I was able to replicate this bug on a PowerPC with Python 2.7, but only if I replace the single character into a single unicode character (e.g. in line 212 of test_Cluster.py, if I replace method='a' by method=u'a'). Can you confirm that you get this bug with Python 2.7 even with simple strings rather than unicode? Thanks, -Michiel. On Sat, 8/16/14, Andreas Tille andr...@an3as.eu wrote: Subject: Re: Bug#751277: python-biopython: FTBFS on mips* powerpc s390x To: Peter Cock p.j.a.c...@googlemail.com Cc: Dejan Latinovic dejan.latino...@imgtec.com, Michiel de Hoon mjldeh...@yahoo.com, Biopython discussion list biopyt...@lists.open-bio.org, 751...@bugs.debian.org 751...@bugs.debian.org, biopython-...@biopython.org biopython-...@biopython.org Date: Saturday, August 16, 2014, 5:37 AM Hi Peter, On Thu, Aug 14, 2014 at 09:52:40AM +0100, Peter Cock wrote: 1. waiting for your confirmation / patch 2. deactivating the specific test 3. exclude mips for biopython 4. ? any better idea ? In the current state all the work we spent in biopython over the last monthes will not migrate to testing for the simple reason that the current package in testing just does not run the test suite at build time and moreover python3 is not supported. Kind regards Andreas. I would suggest (2), deactivate this test (at least for for mips) as the most practical short term solution for the Debian packages. Or if you prefer (3), don't target mips for the Biopython package (yet). Medium term, I hope we can fix the C code to handle either Endian platform - option (1). It seems after having fixed the issue caused by wise we have one remaining problem: On powerpc[1] and s390x[2] test_Cluster fails even with Python 2.7 with: == ERROR: test_clusterdistance (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 212, in test_clusterdistance method='a', transpose=0) ValueError: method should be a single character == ERROR: test_kcluster (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 141, in test_kcluster method='a', dist='e') ValueError: method should be a single character == ERROR: test_somcluster (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 557, in test_somcluster inittau=0.02, niter=100, dist='e') ValueError: distance should be a single character == ERROR: test_treecluster (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 290, in test_treecluster transpose=0, method='a', dist='e') ValueError: method should be a single character -- Ran 210 tests in 293.712 seconds FAILED (failures = 1) On sparc[3] there is a problem with dialign but sparc is no release architecture and wie might ignore this. It might be a helpful hint anyway. Any hint for the test_Cluster problem? If not I would also consider to hide it cowardly under the carpet for the moment. The new package is so much better tested than the one in the testing distribution which does not even dare about any unit tests and only for this reason reached the testing distribution. What do you think? Kind regards Andreas. scrool these links to the end to see the problem: [1] https://buildd.debian.org/status/fetch.php?pkg=python-biopythonarch=powerpcver=1.64%2Bdfsg-3stamp=1408116532 [2] https://buildd.debian.org/status/fetch.php?pkg=python-biopythonarch=s390xver=1.64%2Bdfsg-3stamp=1408107524 [3] https://buildd.debian.org/status/fetch.php?pkg=python-biopythonarch=sparcver=1.64%2Bdfsg-3stamp=1408130792 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749870: objcryst-fox: Please update to use wxwidgets3.0
On Fri, May 30, 2014 at 10:38:20PM +1200, Olly Betts wrote: We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. I've rebuilt your package using the attached patch. The fox binary runs, but I don't have the data required to usefully test much of its functionality. I'm happy to NMU this change if you wish me to - just let me know. This bug has been open with a patch attached for close to 3 months now without any comment, so I'm intending to NMU this patch. It really needs testing by people who actually use the application - if it's in unstable, that is more likely to happen then if the patch just sits here any longer. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741165: marked as done (libdolfin1.3: libdolfin.so.1.3.0 links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Sun, 24 Aug 2014 04:00:09 +
with message-id e1xloyp-0005su...@franck.debian.org
and subject line Bug#741165: fixed in dolfin 1.4.0+dfsg-1
has caused the Debian Bug report #741165,
regarding libdolfin1.3: libdolfin.so.1.3.0 links with both GPL-licensed and
GPL-incompatible libraries
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.)
--
741165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libdolfin1.3
Version: 1.3.0+dfsg-2
Severity: serious
Justification: Policy 2.3
User: debian-science-maintain...@lists.alioth.debian.org
Usertags: scotch-license-issues
Hello,
the library /usr/lib/x86_64-linux-gnu/libdolfin.so.1.3.0 links with:
= libumfpack.so.5.6.2, which is under the GNU GPL v2 or later
= libcholmod.so.2.1.2, which has parts under the GNU GPL v2 or later
= libptscotch-5.1.so and libptscotcherr-5.1.so, which are released
under the GPL-incompatible terms of the CeCILL-C v1.0 license
This seems to mean that package libdolfin1.3 includes a file which
links with both GPL-licensed and GPL-incompatible libraries.
Please refer to the almost identical bug #740463 for some further
details about the SCOTCH licensing issues.
I think the possible solutions to issue for dolfin are, in
descending order of desirability:
(A) SCOTCH copyright holders should be contacted and persuaded to
re-license (or dual-license) it under GPLv2-or-later-compatible terms
(B) SCOTCH should be substituted with a GPLv2-or-later-compatible
replacement, if any is available (METIS seems to be at least
GPLv3-or-later-compatible, see https://bugs.debian.org/740463#15 )
(C) GPL-licensed library (such as UMFPACK and CHOLMOD) copyright
holders should be asked to relax the copyleft (for instance by switching
the LGPL v2.1) or add license exceptions that give permission to link
their works with code released under CeCILL-C v1.0
Since the best solution is (A), I renew my call for help to push
in the direction of {re|dual}-licensing SCOTCH under the GNU LGPL v2.1:
again, please see https://bugs.debian.org/740463#5 for the full story.
Thanks for your time!
P.S.: binary package python-dolfin could also be possibly affected
by this same issue...
---End Message---
---BeginMessage---
Source: dolfin
Source-Version: 1.4.0+dfsg-1
We believe that the bug you reported is fixed in the latest version of
dolfin, 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 741...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Johannes Ring joha...@simula.no (supplier of updated dolfin 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 Aug 2014 09:57:36 +0200
Source: dolfin
Binary: libdolfin1.4-dev dolfin-dev libdolfin1.4 libdolfin1.4-dbg python-dolfin
python-dolfin-dbg dolfin-doc dolfin-bin
Architecture: source amd64 all
Version: 1.4.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Johannes Ring joha...@simula.no
Description:
dolfin-bin - Executable scripts for DOLFIN
dolfin-dev - Empty package depending on latest DOLFIN development package
dolfin-doc - Documentation and demo programs for DOLFIN
libdolfin1.4 - Shared libraries for DOLFIN
libdolfin1.4-dbg - Shared libraries with debugging symbols for DOLFIN
libdolfin1.4-dev - Shared links and header files for DOLFIN
python-dolfin - Python interface for DOLFIN
python-dolfin-dbg - Python extension modules for DOLFIN with debugging symbols
Closes: 741165 755727
Changes:
dolfin (1.4.0+dfsg-1) unstable; urgency=medium
.
* New upstream release.
* debian/control:
- Update package names for new SONAME 1.3 (libdolfin1.3 -
libdolfin1.4, libdolfin1.3-dbg - libdolfin1.4-dbg and
libdolfin1.3-dev - libdolfin1.4-dev).
- Bump minimum required version for python-instant, python-ufl and
python-ffc to 1.4.0.
- Add python-ffc (= 1.4.0) to Build-Depends.
- Replace swig2.0 with swig in Build-Depends.
- Remove ufc and python-ufc from Build-Depends and from
Bug#755727: marked as done (python-dolfin: not installable in sid)
Your message dated Sun, 24 Aug 2014 04:00:09 +
with message-id e1xloyp-0005sa...@franck.debian.org
and subject line Bug#755727: fixed in dolfin 1.4.0+dfsg-1
has caused the Debian Bug report #755727,
regarding python-dolfin: not installable in sid
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.)
--
755727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-dolfin
Version: 1.3.0+dfsg-2+b1
Severity: grave
User: trei...@debian.org
Usertags: edos-uninstallable
Hi, python-dolfin is not installable in sid on any architecture. This is the
case since 2014-05-12. The reason is that it depends both on python-ffc
and python-ufc, which are in conflict.
-Ralf.
---End Message---
---BeginMessage---
Source: dolfin
Source-Version: 1.4.0+dfsg-1
We believe that the bug you reported is fixed in the latest version of
dolfin, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Johannes Ring joha...@simula.no (supplier of updated dolfin 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 Aug 2014 09:57:36 +0200
Source: dolfin
Binary: libdolfin1.4-dev dolfin-dev libdolfin1.4 libdolfin1.4-dbg python-dolfin
python-dolfin-dbg dolfin-doc dolfin-bin
Architecture: source amd64 all
Version: 1.4.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Johannes Ring joha...@simula.no
Description:
dolfin-bin - Executable scripts for DOLFIN
dolfin-dev - Empty package depending on latest DOLFIN development package
dolfin-doc - Documentation and demo programs for DOLFIN
libdolfin1.4 - Shared libraries for DOLFIN
libdolfin1.4-dbg - Shared libraries with debugging symbols for DOLFIN
libdolfin1.4-dev - Shared links and header files for DOLFIN
python-dolfin - Python interface for DOLFIN
python-dolfin-dbg - Python extension modules for DOLFIN with debugging symbols
Closes: 741165 755727
Changes:
dolfin (1.4.0+dfsg-1) unstable; urgency=medium
.
* New upstream release.
* debian/control:
- Update package names for new SONAME 1.3 (libdolfin1.3 -
libdolfin1.4, libdolfin1.3-dbg - libdolfin1.4-dbg and
libdolfin1.3-dev - libdolfin1.4-dev).
- Bump minimum required version for python-instant, python-ufl and
python-ffc to 1.4.0.
- Add python-ffc (= 1.4.0) to Build-Depends.
- Replace swig2.0 with swig in Build-Depends.
- Remove ufc and python-ufc from Build-Depends and from Depends for
binary package libdolfin1.4-dev and python-dolfin (closes: #755727).
- Add libdolfin1.3-dev in Conflicts and Replaces for binary package
libdolfin1.4-dev.
- Remove libarmadillo-dev from {Build-}Depends.
- Remove libptscotch-dev from {Build-}Depends (closes: #741165).
* Move debian/libdolfin1.3.install - debian/libdolfin1.4.install
and debian/libdolfin1.3-dev.install - debian/libdolfin1.4-dev.install.
* debian/rules:
- Enable CGAL again (accidentally disabled in last upload).
- No longer needed to remove .pyc files in get-orig-source target.
- Add export PERL_LWP_SSL_VERIFY_HOSTNAME=0 to get-orig-source
target to help uscan download from Bitucket.
* Remove patch for bug in Boost (fixed).
* Add lintian override libdolfin1.4-dev: pkg-config-bad-directive.
Checksums-Sha1:
01b9cccf0f9b1d7d45fead99fec23611a021904e 3009 dolfin_1.4.0+dfsg-1.dsc
6f37dd8e2bb7ea0b96148aefe7640d861d683968 8601333 dolfin_1.4.0+dfsg.orig.tar.gz
8494312fe91769c76c8b503550e5db60cc5e2eed 115432
dolfin_1.4.0+dfsg-1.debian.tar.xz
28f19a676679dd2080457eb9cef561a1167c3f39 242516
libdolfin1.4-dev_1.4.0+dfsg-1_amd64.deb
968e24e918bd4e06885d41c899c0c6c7bc334ad1 38646 dolfin-dev_1.4.0+dfsg-1_all.deb
57b9a6dfbc50588e398851dfdd778698562a819f 3374126
libdolfin1.4_1.4.0+dfsg-1_amd64.deb
87b4aafaeb75005ec7f65ee559e197fbbd8e2309 50892800
libdolfin1.4-dbg_1.4.0+dfsg-1_amd64.deb
6c8822c56d09365b6664898297351fd39d3e0357 1233052
python-dolfin_1.4.0+dfsg-1_amd64.deb
Bug#749870: objcryst-fox: Please update to use wxwidgets3.0
Go ahead, I have not had any time to dedicate to my packages recently and I am not sure when that will change. Carlo On Sun, 24 Aug 2014, Olly Betts wrote: On Fri, May 30, 2014 at 10:38:20PM +1200, Olly Betts wrote: We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. I've rebuilt your package using the attached patch. The fox binary runs, but I don't have the data required to usefully test much of its functionality. I'm happy to NMU this change if you wish me to - just let me know. This bug has been open with a patch attached for close to 3 months now without any comment, so I'm intending to NMU this patch. It really needs testing by people who actually use the application - if it's in unstable, that is more likely to happen then if the patch just sits here any longer. Cheers, Olly -- Carlo U. Segre -- Duchossois Leadership Professor of Physics Director, Center for Synchrotron Radiation Research and Instrumentation Illinois Institute of Technology Voice: 312.567.3498Fax: 312.567.3494 se...@iit.edu http://phys.iit.edu/~segre se...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749870: objcryst-fox: diff for NMU version 1.9.6.0-2.1
Carlo Segre se...@iit.edu wrote:
Go ahead, I have not had any time to dedicate to my packages recently
and I am not sure when that will change.
OK, done - thanks for getting back to me.
Here's the NMU diff for what I actually uploaded (I just tweaked the
changelog entry).
Cheers,
Olly
diff -Nru objcryst-fox-1.9.6.0/debian/changelog objcryst-fox-1.9.6.0/debian/changelog
--- objcryst-fox-1.9.6.0/debian/changelog 2011-06-26 13:09:20.0 +1200
+++ objcryst-fox-1.9.6.0/debian/changelog 2014-08-24 15:56:59.0 +1200
@@ -1,3 +1,12 @@
+objcryst-fox (1.9.6.0-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxwidgets3.0 (new patch wx3.0-compat.patch) (Closes: #749870)
+ * debian/control: 'polyhedras' - 'polyhedra' in the description ('polyhedra'
+is the plural form of 'polyhedron').
+
+ -- Olly Betts o...@survex.com Sun, 24 Aug 2014 15:56:27 +1200
+
objcryst-fox (1.9.6.0-2) unstable; urgency=low
* Remove -march=native flag from Objcryst/rules-gnu.mak (Closes: #631653
diff -Nru objcryst-fox-1.9.6.0/debian/control objcryst-fox-1.9.6.0/debian/control
--- objcryst-fox-1.9.6.0/debian/control 2011-06-25 10:41:48.0 +1200
+++ objcryst-fox-1.9.6.0/debian/control 2013-11-25 08:20:07.0 +1300
@@ -2,7 +2,7 @@
Section: science
Priority: optional
Maintainer: Carlo Segre se...@debian.org
-Build-Depends: debhelper (= 7), bzip2, libwxgtk2.8-dev, freeglut3-dev,
+Build-Depends: debhelper (= 7), bzip2, libwxgtk3.0-dev, freeglut3-dev,
libfftw3-dev, libnewmat10-dev
Homepage: http://vincefn.net/Fox/
Standards-Version: 3.9.2
@@ -13,7 +13,7 @@
Description: Free Objects for Xtallography
FOX is a program for the ab initio structure determination from powder
diffraction (neutrons, X-Ray). The crystal structure can be described as any
- combination of atoms, molecules or polyhedras, without a priori information
+ combination of atoms, molecules or polyhedra, without a priori information
about the connectivity of these 'building block'. Fox can make multi-pattern
global optimizations, and automatically correct special positions.
.
diff -Nru objcryst-fox-1.9.6.0/debian/patches/series objcryst-fox-1.9.6.0/debian/patches/series
--- objcryst-fox-1.9.6.0/debian/patches/series 2011-06-26 13:06:35.0 +1200
+++ objcryst-fox-1.9.6.0/debian/patches/series 2014-05-30 15:12:41.0 +1200
@@ -1,2 +1,3 @@
install-in-build-directory
revert-march-flag
+wx3.0-compat.patch
diff -Nru objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch
--- objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch 2014-05-30 22:23:06.0 +1200
@@ -0,0 +1,453 @@
+Description: Fix to build with wxwidgets3.0
+Author: Olly Betts o...@survex.com
+Last-Update: 2014-05-30
+
+--- a/ObjCryst/wxCryst/wxMultiGraph.cpp
b/ObjCryst/wxCryst/wxMultiGraph.cpp
+@@ -202,7 +202,6 @@
+wxBufferedPaintDC dc(this);
+this-PrepareDC(dc);
+mpParentFrame-PrepareDC(dc);
+- dc.BeginDrawing();
+
+dc.DestroyClippingRegion();
+dc.SetBackground(wxBrush(_T(white), wxSOLID));
+@@ -289,11 +288,10 @@
+ ix++;
+ VFN_DEBUG_MESSAGE(WXMultiGraph::OnPaint():Data#ix,3)
+ if((pos-second.vx.size()1)||(pos-second.vx.size()!=pos-second.vy.size())) continue;
+- wxColour *pc;//=dynamic_castwxColour*(wxTheColourDatabase-Item(ix++)-GetData());
+
+- pc=wxTheColourDatabase-FindColour(wxString::FromAscii(swxColourNameList[ix]));
+- if(pc==0) dc.SetPen(*wxGREY_PEN);
+- else dc.SetPen(wxPen(*pc,1,wxSOLID));
++ wxColour colour=wxTheColourDatabase-Find(wxString::FromAscii(swxColourNameList[ix]));
++ if(!colour.IsOk()) dc.SetPen(*wxGREY_PEN);
++ else dc.SetPen(wxPen(colour,1,wxSOLID));
+ float x1,y1,x2,y2;
+ x2=pos-second.vx[0];
+ y2=pos-second.vy[0];
+@@ -310,8 +308,8 @@
+ dc.DrawLine(wxCoord(x1),wxCoord(y1),wxCoord(x2),wxCoord(y2));
+ }
+ // Print Name
+- if(pc==0) dc.SetTextForeground(wxGREY_PEN-GetColour());
+- else dc.SetTextForeground(wxPen(*pc,1,wxSOLID).GetColour());
++ if(!colour.IsOk()) dc.SetTextForeground(wxGREY_PEN-GetColour());
++ else dc.SetTextForeground(wxPen(colour,1,wxSOLID).GetColour());
+ wxCoord tmpW,tmpH;
+ fontInfo.Printf(wxString::FromAscii(pos-second.name.c_str()));
+ dc.GetTextExtent(fontInfo, tmpW, tmpH);
+--- a/ObjCryst/wxCryst/wxPowderPattern.cpp
b/ObjCryst/wxCryst/wxPowderPattern.cpp
+@@ -713,7 +713,7 @@
+ {
+VFN_DEBUG_MESSAGE(WXPowderPattern::OnMenuSaveText(),6)
+WXCrystValidateAllUserInput();
+- wxFileDialog save(this,_T(Choose a file),_T(),_T(),_T(*.txt),wxSAVE | wxOVERWRITE_PROMPT);
++ wxFileDialog save(this,_T(Choose a file),_T(),_T(),_T(*.txt),wxFD_SAVE | wxFD_OVERWRITE_PROMPT);
+if(save.ShowModal() != wxID_OK) return;
+
+ofstream
Bug#749870: marked as done (objcryst-fox: Please update to use wxwidgets3.0)
Your message dated Sun, 24 Aug 2014 05:04:46 +
with message-id e1xlpyw-0007f5...@franck.debian.org
and subject line Bug#749870: fixed in objcryst-fox 1.9.6.0-2.1
has caused the Debian Bug report #749870,
regarding objcryst-fox: Please update to use wxwidgets3.0
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.)
--
749870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: objcryst-fox
Version: 1.9.6.0-2
Severity: normal
Tags: patch
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released.
I've rebuilt your package using the attached patch. The fox binary
runs, but I don't have the data required to usefully test much of its
functionality.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru objcryst-fox-1.9.6.0/debian/changelog objcryst-fox-1.9.6.0/debian/changelog
--- objcryst-fox-1.9.6.0/debian/changelog 2011-06-26 13:09:20.0 +1200
+++ objcryst-fox-1.9.6.0/debian/changelog 2014-05-30 21:37:32.0 +1200
@@ -1,3 +1,12 @@
+objcryst-fox (1.9.6.0-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxwidgets3.0 (new patch wx3.0-compat.patch)
+ * debian/control: 'polyhedras' - 'polyhedra' in the description ('polyhedra'
+is the plural form of 'polyhedron').
+
+ -- Olly Betts o...@survex.com Fri, 30 May 2014 21:37:27 +1200
+
objcryst-fox (1.9.6.0-2) unstable; urgency=low
* Remove -march=native flag from Objcryst/rules-gnu.mak (Closes: #631653
diff -Nru objcryst-fox-1.9.6.0/debian/control objcryst-fox-1.9.6.0/debian/control
--- objcryst-fox-1.9.6.0/debian/control 2011-06-25 10:41:48.0 +1200
+++ objcryst-fox-1.9.6.0/debian/control 2013-11-25 08:20:07.0 +1300
@@ -2,7 +2,7 @@
Section: science
Priority: optional
Maintainer: Carlo Segre se...@debian.org
-Build-Depends: debhelper (= 7), bzip2, libwxgtk2.8-dev, freeglut3-dev,
+Build-Depends: debhelper (= 7), bzip2, libwxgtk3.0-dev, freeglut3-dev,
libfftw3-dev, libnewmat10-dev
Homepage: http://vincefn.net/Fox/
Standards-Version: 3.9.2
@@ -13,7 +13,7 @@
Description: Free Objects for Xtallography
FOX is a program for the ab initio structure determination from powder
diffraction (neutrons, X-Ray). The crystal structure can be described as any
- combination of atoms, molecules or polyhedras, without a priori information
+ combination of atoms, molecules or polyhedra, without a priori information
about the connectivity of these 'building block'. Fox can make multi-pattern
global optimizations, and automatically correct special positions.
.
diff -Nru objcryst-fox-1.9.6.0/debian/patches/series objcryst-fox-1.9.6.0/debian/patches/series
--- objcryst-fox-1.9.6.0/debian/patches/series 2011-06-26 13:06:35.0 +1200
+++ objcryst-fox-1.9.6.0/debian/patches/series 2014-05-30 15:12:41.0 +1200
@@ -1,2 +1,3 @@
install-in-build-directory
revert-march-flag
+wx3.0-compat.patch
diff -Nru objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch
--- objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ objcryst-fox-1.9.6.0/debian/patches/wx3.0-compat.patch 2014-05-30 22:23:06.0 +1200
@@ -0,0 +1,453 @@
+Description: Fix to build with wxwidgets3.0
+Author: Olly Betts o...@survex.com
+Last-Update: 2014-05-30
+
+--- a/ObjCryst/wxCryst/wxMultiGraph.cpp
b/ObjCryst/wxCryst/wxMultiGraph.cpp
+@@ -202,7 +202,6 @@
+wxBufferedPaintDC dc(this);
+this-PrepareDC(dc);
+mpParentFrame-PrepareDC(dc);
+- dc.BeginDrawing();
+
+dc.DestroyClippingRegion();
+dc.SetBackground(wxBrush(_T(white), wxSOLID));
+@@ -289,11 +288,10 @@
+ ix++;
+ VFN_DEBUG_MESSAGE(WXMultiGraph::OnPaint():Data#ix,3)
+ if((pos-second.vx.size()1)||(pos-second.vx.size()!=pos-second.vy.size())) continue;
+- wxColour *pc;//=dynamic_castwxColour*(wxTheColourDatabase-Item(ix++)-GetData());
+
+- pc=wxTheColourDatabase-FindColour(wxString::FromAscii(swxColourNameList[ix]));
+- if(pc==0) dc.SetPen(*wxGREY_PEN);
+- else dc.SetPen(wxPen(*pc,1,wxSOLID));
++ wxColour colour=wxTheColourDatabase-Find(wxString::FromAscii(swxColourNameList[ix]));
++ if(!colour.IsOk()) dc.SetPen(*wxGREY_PEN);
++ else dc.SetPen(wxPen(colour,1,wxSOLID));
+ float x1,y1,x2,y2;
+
Bug#758510: marked as done (mediawiki: 1.19.18 fixes security vulnerabilities (CVE-2014-5241 CVE-2014-5243))
Your message dated Sun, 24 Aug 2014 05:19:58 + with message-id e1xlqde-hn...@franck.debian.org and subject line Bug#758510: fixed in mediawiki 1:1.19.18+dfsg-0.1 has caused the Debian Bug report #758510, regarding mediawiki: 1.19.18 fixes security vulnerabilities (CVE-2014-5241 CVE-2014-5243) 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.) -- 758510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mediawiki Version: 1:1.19.17+dfsg-1 Severity: important Tags: security upstream fixed-upstream Control: found -1 1:1.19.16+dfsg-0+deb7u1 Hi See https://marc.info/?l=oss-securitym=140800398132695w=2 and https://www.mediawiki.org/wiki/Release_notes/1.19#Changes_since_1.19.17 https://lists.wikimedia.org/pipermail/mediawiki-announce/2014-July/000157.html Regards, Salvatore ---End Message--- ---BeginMessage--- Source: mediawiki Source-Version: 1:1.19.18+dfsg-0.1 We believe that the bug you reported is fixed in the latest version of mediawiki, 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 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso car...@debian.org (supplier of updated mediawiki package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 24 Aug 2014 06:47:35 +0200 Source: mediawiki Binary: mediawiki mediawiki-classes Architecture: source all Version: 1:1.19.18+dfsg-0.1 Distribution: unstable Urgency: high Maintainer: Mediawiki Maintenance Team pkg-mediawiki-de...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: mediawiki - website engine for collaborative work mediawiki-classes - website engine for collaborative work - standalone classes Closes: 758510 Changes: mediawiki (1:1.19.18+dfsg-0.1) unstable; urgency=high . * Non-maintainer upload with maintainers approval. * Imported Upstream version 1.19.18+dfsg (Closes: #758510) - CVE-2014-5241 (bug 68187) SECURITY: Prepend jsonp callback with comment. - CVE-2014-5243 (bug 65778) SECURITY: Copy prevent-clickjacking between OutputPage and ParserOutput. Checksums-Sha1: b211f8ce4c53de9629d62ac1a798d7bd3088b733 2203 mediawiki_1.19.18+dfsg-0.1.dsc 1c594a9ce796288cf27a8eba1d40fc871c0d554c 18200184 mediawiki_1.19.18+dfsg.orig.tar.gz 732cfae5c23ee3c279c40b3a15b5416e74202a7d 61032 mediawiki_1.19.18+dfsg-0.1.debian.tar.xz 81164d18f71e526e5b454734149319efb8b97b67 11752730 mediawiki_1.19.18+dfsg-0.1_all.deb a0e656a97c258b3034c3e41ca76d485a65b370cc 238356 mediawiki-classes_1.19.18+dfsg-0.1_all.deb Checksums-Sha256: 90969078a2a7d3f1cd2d7734870842b9c7eb09fd38961430585b9e83810ad885 2203 mediawiki_1.19.18+dfsg-0.1.dsc 080709401f2ddea6127cd77d5e28b9e5c13b0db32a7848791f097b5d6c56c7a8 18200184 mediawiki_1.19.18+dfsg.orig.tar.gz 1e1e3177974afd6d0409325f56e9a1c9d8452f5e4d5e4479313410a13b49d694 61032 mediawiki_1.19.18+dfsg-0.1.debian.tar.xz 7cf13fc97a0ce90ce4e779e6cad873d4dd4af424d7779ba8ec9808729b344920 11752730 mediawiki_1.19.18+dfsg-0.1_all.deb 1fddcca2a4b7330fc4cfb0a9bcb1d4ab51744c8efaa8a26ff359a07ff8c46d09 238356 mediawiki-classes_1.19.18+dfsg-0.1_all.deb Files: 6e08840eeb3733cc7a9ddab38d2ef99c 11752730 web optional mediawiki_1.19.18+dfsg-0.1_all.deb dfde1d836b82bb020803078adc57f04a 238356 web optional mediawiki-classes_1.19.18+dfsg-0.1_all.deb 67e444fee68d240b93221f5780fac2ce 2203 web optional mediawiki_1.19.18+dfsg-0.1.dsc 3601fc9c9f802d3071164c590ce31312 18200184 web optional mediawiki_1.19.18+dfsg.orig.tar.gz 3ce18a16d66977750421c82a9a776790 61032 web optional mediawiki_1.19.18+dfsg-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT+XCQAAoJEAVMuPMTQ89EAToP/1Nagur3nOYmJu48McYLOGpB QjE+HydG03xZD2aOE9BL38L8YDGwxqT37d3RmSpL6gaLWqqmEgZAnkBENx9cE9XZ 5SZZ8+F3iffUuFWl8g1VTH2ZkWL32cFAX9MKVNi9Lhrl4ycsF14TdqaL+OKu1cFH 72TGosaTs1Lm3QE6eUwq2/xtOppALBj98jElxQ1HPTh3CziAz3tCQV2BJy0U+DBp Ug63Ta9t1PqOlHd05VG107qil65JKh3ITDjkhM/nfdSdbfGFtuiLQbtHMFi9WjL/ U2lLMzG6UVyj9i2+IRT+YFihwKSLYfhhwMHOj6YnqRvkCwoW+HWWNiZRHDWodJ/J
Bug#368297: Re: Bug#368297: Does OpenLDAP has any GPLv2 dependency?
[odd: I didn't see your message on pkg-openldap-devel, nor can I find it in the archive. I wonder if it's stuck in a mod queue somewhere...] On 03/08/14 03:29 PM, Simon McVittie wrote: On Tue, 05 Nov 2013 at 15:45:07 +0100, Carlos Alberto Lopez Perez wrote: On 24/04/12 17:25, Thorsten Glaser wrote: this bug has been brought to my attention by my boss today. If I understand the situation correctly, the problem is: • OpenLDAP links against GnuTLS (gnutls26) • gnutls26 links against gcrypt, which has the bug • gnutls28 links against nettle, but also gmp which is LGPLv3+ • OpenLDAP thus can’t link against gnutls28, as it has reverse dependencies that are not LGPLv3-/GPLv3-compatible • the package affected is libnss-ldap though If there isn't any GPLv2 reverse dependency, then OpenLDAP can be just recompiled to link against gnutls28 and this long standing bug will be fixed. As far as I understand it, this became simpler in recent months: * gnutls28 links against gmp, which was relicensed to LGPL-3+ or GPL-2+, making it possible to link GPL-2 (only) code to gnutls28 So would linking OpenLDAP to gnutls28 (#745231, tagged pending) close this RC bug as a side-effect? I believe so, yes. For example, with openldap built from what's currently in git, sudo as an LDAP user works, while in current sid it still fails like it always has. thanks, Ryan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737395: xkill.1 Copyright
Hi Claudio Calvelli, There have been some concerns on Debian that the 'xkill.1' manpage which you have written was not released under a DFSG-compatible license. Would you please be able to release it under a free license so that we don't have to remove it? If you need any help, just ask. Yours thankfully, Riley Baird -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
