Bug#755984: util-linux: Packaging conflict with bash-completion
Package: util-linux Version: 2.24.2-1 Severity: serious Hi A conflict is detected upon installation of util-linux : Unpacking util-linux (2.25-2) over (2.24.2-1) ... dpkg: error processing archive /var/cache/apt/archives/util- linux_2.25-2_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/dmesg', which is also in package bash-completion 1:2.1-4 Regards Ludovic -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages util-linux depends on: ii debconf [debconf-2.0] 1.5.53 ii dpkg 1.17.10 ii initscripts2.88dsf-55.2 ii install-info 5.2.0.dfsg.1-4 ii libblkid1 2.25-2 ii libc6 2.19-7 ii libmount1 2.25-2 ii libncurses55.9+20140712-2 ii libpam0g 1.1.8-3 ii libselinux12.3-1 ii libslang2 2.2.4-17 ii libtinfo5 5.9+20140712-2 ii libuuid1 2.25-2 ii lsb-base 4.1+Debian13 ii tzdata 2014e-1 ii zlib1g 1:1.2.8.dfsg-1 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.26-2 ii kbd 1.15.5-1 ii util-linux-locales 2.24.2-1 signature.asc Description: This is a digitally signed message part
Bug#746884: Fwd: [src:molds] Fix FTBFS with GCC-4.9
Hi,
I am one of upstream authors, and I've prepared the patch that fixes
this bug. (https://bugs.debian.org/746884)
I'm glad if you maintainers could take your time to merge this patch
into the package.
FYI, this patch is already in the trunk of upstream repository (rev 1697).
Thanks!
--
Katsuhiko Nishimra
ktns...@gmail.com
Fix boost serialization compile error.
Index: molds-0.3.0/src/base/MolDSException.cpp
===
--- molds-0.3.0.orig/src/base/MolDSException.cpp
+++ molds-0.3.0/src/base/MolDSException.cpp
@@ -161,7 +161,7 @@ void MolDSException::serialize(Archive
void MolDSException::Serialize(std::ostream os){
boost::archive::text_oarchive oa(os);
- oa this;
+ oa (*this);
}
MolDSException MolDSException::Deserialize(std::istream is){
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 746884 + patch Bug #746884 [src:molds] molds: ftbfs with GCC-4.9 Added tag(s) patch. End of message, stopping processing here. Please contact me if you need assistance. -- 746884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746884 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#755985: transmission: CVE-2014-4909
Source: transmission Version: 2.52-3+nmu1 Severity: grave Tags: security upstream fixed-upstream Justification: user security hole Control: fixed -1 2.52-3+nmu2 Hi, Opening this bugreport, since this was already fixed by Moritz in DSA-2988-1. The following vulnerability was published for transmission. CVE-2014-4909[0]: peer communication vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-4909 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: transmission: CVE-2014-4909
Processing control commands: fixed -1 2.52-3+nmu2 Bug #755985 [src:transmission] transmission: CVE-2014-4909 Marked as fixed in versions transmission/2.52-3+nmu2. -- 755985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755985 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#755362: marked as done (sysdig: FTBFS on kfreebsd-*: scap.c:1015: undefined reference to `scap_readbuf')
Your message dated Fri, 25 Jul 2014 06:48:27 + with message-id e1xazip-0006vy...@franck.debian.org and subject line Bug#755362: fixed in sysdig 0.1.86-2 has caused the Debian Bug report #755362, regarding sysdig: FTBFS on kfreebsd-*: scap.c:1015: undefined reference to `scap_readbuf' 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.) -- 755362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sysdig Version: 0.1.85-2 Severity: serious Justification: FTBFS Hi Evgeni, your package no longer builds on kfreebsd-*: | [100%] [100%] Building CXX object userspace/sysdig/CMakeFiles/sysdig.dir/fields_info.cpp.o | cd /«PKGBUILDDIR»/obj-i486-kfreebsd-gnu/userspace/sysdig /usr/bin/c++ -DPLATFORM_NAME=\kFreeBSD\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wall -ggdb --std=c++0x -I/usr/include/jsoncpp -I/«PKGBUILDDIR»/common -I/«PKGBUILDDIR»/userspace/libscap -I/«PKGBUILDDIR»/userspace/libsinsp -I/«PKGBUILDDIR»/obj-i486-kfreebsd-gnu/userspace/sysdig -I/«PKGBUILDDIR»/userspace/sysdig/.-o CMakeFiles/sysdig.dir/fields_info.cpp.o -c /«PKGBUILDDIR»/userspace/sysdig/fields_info.cpp | Building CXX object userspace/sysdig/CMakeFiles/sysdig.dir/sysdig.cpp.o | cd /«PKGBUILDDIR»/obj-i486-kfreebsd-gnu/userspace/sysdig /usr/bin/c++ -DPLATFORM_NAME=\kFreeBSD\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wall -ggdb --std=c++0x -I/usr/include/jsoncpp -I/«PKGBUILDDIR»/common -I/«PKGBUILDDIR»/userspace/libscap -I/«PKGBUILDDIR»/userspace/libsinsp -I/«PKGBUILDDIR»/obj-i486-kfreebsd-gnu/userspace/sysdig -I/«PKGBUILDDIR»/userspace/sysdig/.-o CMakeFiles/sysdig.dir/sysdig.cpp.o -c /«PKGBUILDDIR»/userspace/sysdig/sysdig.cpp | /«PKGBUILDDIR»/userspace/sysdig/sysdig.cpp: In function 'int main(int, char**)': | /«PKGBUILDDIR»/userspace/sysdig/sysdig.cpp:1001:62: warning: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result [-Wunused-result] | system(modprobe sysdig-probe /dev/null 2 /dev/null); | ^ | Linking CXX executable sysdig | cd /«PKGBUILDDIR»/obj-i486-kfreebsd-gnu/userspace/sysdig /usr/bin/cmake -E cmake_link_script CMakeFiles/sysdig.dir/link.txt --verbose=1 | /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wall -ggdb --std=c++0x -Wl,-z,relro CMakeFiles/sysdig.dir/fields_info.cpp.o CMakeFiles/sysdig.dir/sysdig.cpp.o -o sysdig ../libsinsp/libsinsp.a ../libscap/libscap.a -lz -ljsoncpp -lluajit-5.1 -ldl | ../libscap/libscap.a(scap.c.o): In function `scap_handle_eventmask': | /«PKGBUILDDIR»/userspace/libscap/scap.c:1015: undefined reference to `scap_readbuf' | collect2: error: ld returned 1 exit status | make[3]: *** [userspace/sysdig/sysdig] Error 1 | userspace/sysdig/CMakeFiles/sysdig.dir/build.make:118: recipe for target 'userspace/sysdig/sysdig' failed Full build logs: https://buildd.debian.org/status/fetch.php?pkg=sysdigarch=kfreebsd-amd64ver=0.1.85-2stamp=1405266480 https://buildd.debian.org/status/fetch.php?pkg=sysdigarch=kfreebsd-i386ver=0.1.85-2stamp=1405258294 Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: sysdig Source-Version: 0.1.86-2 We believe that the bug you reported is fixed in the latest version of sysdig, 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. Evgeni Golov evg...@debian.org (supplier of updated sysdig package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Jul 2014 08:38:36 +0200 Source: sysdig Binary: sysdig sysdig-dkms Architecture: source amd64 all Version: 0.1.86-2 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov evg...@debian.org Changed-By: Evgeni Golov evg...@debian.org Description: sysdig - system-level exploration and troubleshooting
Processed: found 755985 in 2.52-1
Processing commands for cont...@bugs.debian.org: found 755985 2.52-1 Bug #755985 [src:transmission] transmission: CVE-2014-4909 Marked as found in versions transmission/2.52-1. thanks Stopping processing here. Please contact me if you need assistance. -- 755985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755985 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#755167: marked as done (cmor: FTBFS - missing build-depends)
Your message dated Fri, 25 Jul 2014 07:18:33 + with message-id e1xazlx-0004zq...@franck.debian.org and subject line Bug#755167: fixed in cmor 2.9.1-4 has caused the Debian Bug report #755167, regarding cmor: FTBFS - missing build-depends 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.) -- 755167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cmor Version: 2.9.1-3 Severity: serious Justification: FTBFS on amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, While preparing the hdf5-8 transition I experienced a FTBFS for the package cmor, which seems missing a few build dependencies: libgcrypt-dev, libgnutls-dev, libgpg-error-dev, libtasn1-dev, libp11-kit-dev The FTBFS occurs on an up to date unstable chroot as well (with hdf5-7). The failure occurs during the configure step while checking for netcdf: configure:4269: checking for nc_inq_var_deflate in -lnetcdf configure:4294: gcc -o conftest -lnetcdf -D_FORTIFY_SOURCE=2 -lhdf5 -lm -lcurl -L/usr/lib/x86_64-linux-gnu/heimdal -lgssapi -lnetcdf -lffi -lz -lidn -lrtmp -lgcrypt-lgnutls -lgssapi_krb5 -llber -lldap_r -lgpg-error -ltasn1 -lp11-kit -lk5crypto -lkrb5support -lsasl2 -lkeyutils -lsqlite3 conftest.c -lnetcdf -lhdf5 -lm -lcurl -L/usr/lib/x86_64-linux-gnu/heimdal -lgssapi -lnetcdf -lffi -lz -lidn -lrtmp -lgcrypt -lgnutls -lgssapi_krb5 -llber -lldap_r -lgpg-erro r -ltasn1 -lp11-kit-lk5crypto -lkrb5support -lsasl2 -lkeyutils -lsqlite3 5 /usr/bin/ld: cannot find -lgcrypt /usr/bin/ld: cannot find -lgnutls /usr/bin/ld: cannot find -lgpg-error /usr/bin/ld: cannot find -ltasn1 /usr/bin/ld: cannot find -lp11-kit /usr/bin/ld: cannot find -lgcrypt /usr/bin/ld: cannot find -lgnutls /usr/bin/ld: cannot find -lgpg-error /usr/bin/ld: cannot find -ltasn1 /usr/bin/ld: cannot find -lp11-kit Full build log attached. Thanks, _g. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTyRqsAAoJEO/obGx//s+D8coH/2jgHrJaD7HTPeAbiNx0kQKQ AngEvENSwfreL13TrxwGCwqyMQBJ4cwQ07+jGMIW7vgAdi87qKlMPSN4UGQYM3l+ LLP8qtQS+ieskzTfEpFw239yd7IAuWDFTQTnXk369NlWUe3lQd9GQ/Ec89UNuA4V 69ojAz683RZApQMnHqM1W+t8Ubj6U1Co++rwrYhbHH1apNOlmMCC9LzxiOzdBTBO sbAZrkUTqmD5Ez6zdTj/Bts3P6ggkJ68WNynF9Irp/mmQpkVJs8JqFh7zOaxEvWr +JN4qH0Ir8sg4XsB08+YR16brRzTi8c1AZSOyaAyl1+axMQtgjD/QR2+LF3RKgw= =v2Ey -END PGP SIGNATURE- dpkg-checkbuilddeps: Unmet build dependencies: dh-buildinfo libossp-uuid-dev libudunits2-dev libnetcdf-dev uuid-dev python-all-dev (= 2.6.6-3~) python-setuptools (= 0.6b3) libcurl4-gnutls-dev libldap2-dev heimdal-multidev libsqlite3-dev libsasl2-dev libkeyutils-dev libffi-dev libhdf5-mpi-dev | libhdf5-dev librtmp-dev libidn11-dev libkrb5-dev W: Unmet build-dependency in source dpkg-buildpackage: source package cmor dpkg-buildpackage: source version 2.9.1-3 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Alastair McKinstry mckins...@debian.org dpkg-source --before-build cmor-2.9.1 dpkg-source: info: using options from cmor-2.9.1/debian/source/options: --compression=xz dpkg-checkbuilddeps: Unmet build dependencies: dh-buildinfo libossp-uuid-dev libudunits2-dev libnetcdf-dev uuid-dev python-all-dev (= 2.6.6-3~) python-setuptools (= 0.6b3) libcurl4-gnutls-dev libldap2-dev heimdal-multidev libsqlite3-dev libsasl2-dev libkeyutils-dev libffi-dev libhdf5-mpi-dev | libhdf5-dev librtmp-dev libidn11-dev libkrb5-dev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future fakeroot debian/rules clean dh clean --with python2 dh_testdir debian/rules override_dh_auto_clean make[1]: Entering directory '/home/pini/hdf5-transition/cmor-2.9.1' rm -rf config.sub config.log config.status libcmor.a libcmor.so.2 build test_grid configure CMIP5 rm -f ipcc_test_code Makefile setup.py *.mod compile_line.txt include/cmor_locale.h cmor.pc find . -name '*.nc' -delete find . -name '*.o' -delete find . -name '*.pic_o' -delete find . -name '*.pyc' -delete make[1]: Leaving directory '/home/pini/hdf5-transition/cmor-2.9.1' dh_clean rm -f debian/libcmor2.substvars rm -f debian/libcmor2.*.debhelper rm -rf debian/libcmor2/ rm -f debian/libcmor-dev.substvars rm -f debian/libcmor-dev.*.debhelper rm -rf debian/libcmor-dev/ rm -f debian/python-cmor.substvars rm -f
Bug#754640: marked as done (cmor: no longer buildable on kfreebsd-amd64)
Your message dated Fri, 25 Jul 2014 07:18:33 + with message-id e1xazlx-0004zk...@franck.debian.org and subject line Bug#754640: fixed in cmor 2.9.1-4 has caused the Debian Bug report #754640, regarding cmor: no longer buildable on kfreebsd-amd64 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.) -- 754640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cmor Version: 2.9.1-3 Severity: serious Justification: FTBFS Hi, your package can no longer be built on kfreebsd-amd64 since it build-depends on libkeyutils-dev which is no longer built: https://buildd.debian.org/status/package.php?p=cmorsuite=sid https://buildd.debian.org/status/package.php?p=keyutilssuite=sid The latter says: kfreebsd-amd64 is not present in the architecture list set by the maintainer kfreebsd-i386 is not present in the architecture list set by the maintainer If you want your package to migrate to testing, you may want to either use a conditional build-dependency, or get the existing binaries removed from unstable: https://wiki.debian.org/ftpmaster_Removals Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: cmor Source-Version: 2.9.1-4 We believe that the bug you reported is fixed in the latest version of cmor, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry mckins...@debian.org (supplier of updated cmor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 24 Jul 2014 19:05:11 +0100 Source: cmor Binary: libcmor2 libcmor-dev python-cmor Architecture: source amd64 Version: 2.9.1-4 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Alastair McKinstry mckins...@debian.org Description: libcmor-dev - Development files for Climate Model Output Rewriter libcmor2 - Climate Model Output Rewriter library python-cmor - Python interface to CMOR Closes: 754640 755167 Changes: cmor (2.9.1-4) unstable; urgency=medium . * Make additional flags and pkgs a requirement for ppc64el only. Closes: #755167, #754640. Checksums-Sha1: 7adc8e9a8511a9b0a3d5e2f38a3834f0837a967d 2318 cmor_2.9.1-4.dsc 6e7e56f5af97788c5766772595914152c6f98863 31880 cmor_2.9.1-4.debian.tar.xz 0bd7cbb386c451c5a07232f695473446505f6d5f 126126 libcmor2_2.9.1-4_amd64.deb 59f048d9f3afab2fc421e4a7c3ab5e0f2e4a2c72 4494132 libcmor-dev_2.9.1-4_amd64.deb 1b0db2488b8584913ffdf3cf6aaadcf44cedcace 128066 python-cmor_2.9.1-4_amd64.deb Checksums-Sha256: a3bbe100e0a7623cf80fa519cc8df1a8f30a32e90e9c255d57409e02b3d8aa3f 2318 cmor_2.9.1-4.dsc 6fb713503033c8b23f1567fda0ead4aacea7fa069a020ad2e4a34aee9b285aa3 31880 cmor_2.9.1-4.debian.tar.xz e2b1db2ea5a44809ae1a3d2aec90e67df7f98096b5d38669432fa3b2ec78e8ac 126126 libcmor2_2.9.1-4_amd64.deb 3e02c8ff0130e23e3a219c53a445f4c2ede6b055e1c814d5ba0adaca0b88bd32 4494132 libcmor-dev_2.9.1-4_amd64.deb 39393a96b2bc4ecf1ed6a44833adc289fb8d06aaed3a1a8f1397b82b2146aba4 128066 python-cmor_2.9.1-4_amd64.deb Files: d9ee45fb54bd531828ba954eacf21967 126126 libs extra libcmor2_2.9.1-4_amd64.deb 03b4202888d0a4776d4f090b64cfbba5 4494132 libdevel extra libcmor-dev_2.9.1-4_amd64.deb de02f4d0818c5a1a2b3ed78f35fe9e1c 128066 python extra python-cmor_2.9.1-4_amd64.deb 7a6d03ba0fde7a2f3fd14c7753f32f02 2318 utils extra cmor_2.9.1-4.dsc 2235aa8851f273afe703ef0a57851f6a 31880 utils extra cmor_2.9.1-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT0gF4AAoJEN9LdrZRJ3QshGEP/2Dv5zm7QzooTi+2kd+0rsJj 9eIP0WCYDUa36xaR1zMfY6yOa2rLkF5T70hueyl5Mr/FTT2NeWgyMYlWdTAKjsc7 9Q7BS5cSNx9atZIK+bE6x8dB2vRs+RM+C4UH5TXXEZ0/vreos7Gm98yV4WV/X7XC vuLzAKjFJdmGHE7bltQsBuxBAmKicKhPOwSatc7BaqiKjytRbBSY4kNJHOh47Lyx Wzt03MH+OjLoLJiQRQZn6pYk4qEaJTOACM/X3e3tdWgdet22TNh3Iwxl2veYCTR5 3ftYlXal5zWns8NOaAJ+HTQHUQumYECrLfGFZeHHbqBbCnW/VDsJtJlYMG5KMspk JXwp1S+W5mfrs4w9MaVn8xM3gjwB2uR0q8zXY43p11a02mwVt6+WmyqTroZaDaZv DtKWStvkaCs3q1ev45YabAxrOwCjvSrxdJ3pro014ZZQil7YY4yEkEiI2EJFah51 ozLHyrg9OEMqJf0EdqAwksyBZY/PrDgR4S9487hwvLNWay3ZfCA1rwegOemjVxH1
Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18
On 14/07/14 23:17, Niko Tyni wrote: I've just uploaded perl_5.18.2-7 providing only perlapi-5.18.2d on s390x and closing this bug (#753444). FWIW, this had some trouble migrating because there were a few packages that were still depending on perlapi-5.18.2 on testing, and the rebuilds were not migrating for one reason or another. These are the packages I had to remove: remove libsereal-encoder-perl/2.04-1 libsereal-decoder-perl/2.12-3 libsession-storage-secure-perl/0.010-1 libdancer-session-cookie-perl/0.22-1 libimager-perl/0.98+dfsg-2 libimager-qrcode-perl/0.033-1.2 libmojomojo-perl/1.10+dfsg1-3 libxml-saxon-xslt2-perl/0.007-3 libinline-java-perl/0.53-1 remove inn/1:1.7.2q-41 uucpsend/1.1-4 remove pilot-manager/1.107.0pre108-5 syncbbdb/2.6-2 As you can see, most of those are perl modules that had no (non-perl-modules) rdeps in the archive. They can get back when they are fixed. inn has been fixed already, so it and uucpsend should get back in very soon. pilot-manager and syncbbdb are RC-buggy, as they depend on libpda-pilot-perl which is gone. Thanks to gregor who fixed libio-interface-perl, preventing me from removing a few more packages. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merge file conflict bugs
Processing commands for cont...@bugs.debian.org: forcemerge 755982 755984 Bug #755982 [util-linux] file conflict with bash-completion: dmesg and pgrep completion Bug #755984 [util-linux] util-linux: Packaging conflict with bash-completion Merged 755982 755984 thanks Stopping processing here. Please contact me if you need assistance. -- 755982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755982 755984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755984 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#755982: file conflict with bash-completion: dmesg and pgrep completion
Hello! On Fri, Jul 25, 2014 at 06:55:00AM +0200, Michael Biebl wrote: [...] trying to overwrite '/usr/share/bash-completion/completions/dmesg', which is also in package bash-completion 1:2.1-4 [...] Another file-conflict is bash-completion: /usr/share/bash-completion/completions/pgrep Sigh, I was apparently too tired yesterday to get my apt-file check correct. Arguably, the package shipping the actual tool should be the one shipping the bash-completion file. So this bug should be clone for bash-completion, to get those files removed and then util-linux should get an appropriate Breaks/Replaces. I've filed a Bug#755986 requesting this against bash-completion. I'll drop the files in the next util-linux package revision pending the above bug being closed, where I can do a proper versioned Conflicts/Replaces. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718624: Bug#742626: transmission-daemon: SEGFAULT on first run, breaks installation
On 08/04/2014 13:09, Markus Koschany wrote: Updated patch is attached. It works for me and fixed the problem. Even if my configuration is a modified settings.json with not the default download directory. -- François Bobot -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751558: marked as done (crystalspace: Please update to use wxwidgets3.0)
Your message dated Fri, 25 Jul 2014 10:24:00 +0200
with message-id 53d21420.8080...@gambaru.de
and subject line crystalspace: Please update to use wxwidgets3.0
has caused the Debian Bug report #751558,
regarding crystalspace: 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.)
--
751558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: crystalspace
Version: 2.0+dfsg-1
Tags: patch sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Control: block 748169 by -1
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 successfully built crystalspace with the attached patch. I haven't
tested the patched package as there seem to be a large number of
programs installed, and I couldn't see an easy way to work out which
ones actually use wxwidgets (none of the binaries depend directly, it's
all through the crystalspace library).
Incidentally, I think this patch would also be compatible with wx2.8,
though I've not tested that.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru crystalspace-2.0+dfsg/debian/changelog crystalspace-2.0+dfsg/debian/changelog
--- crystalspace-2.0+dfsg/debian/changelog 2013-05-27 19:59:29.0 +1200
+++ crystalspace-2.0+dfsg/debian/changelog 2014-06-14 21:03:58.0 +1200
@@ -1,3 +1,10 @@
+crystalspace (2.0+dfsg-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0 (new patch: wx3.0-compat.patch).
+
+ -- Olly Betts o...@survex.com Sat, 14 Jun 2014 21:03:37 +1200
+
crystalspace (2.0+dfsg-1) unstable; urgency=low
* Team upload.
diff -Nru crystalspace-2.0+dfsg/debian/control crystalspace-2.0+dfsg/debian/control
--- crystalspace-2.0+dfsg/debian/control 2013-05-25 23:50:58.0 +1200
+++ crystalspace-2.0+dfsg/debian/control 2014-03-21 11:45:57.0 +1300
@@ -7,7 +7,7 @@
Build-Depends: debhelper (= 7.2.6), dpkg-dev (= 1.16.1~), lib3ds-dev, autoconf,
libogg-dev, libjpeg-dev, libfreetype6-dev, zlib1g-dev, libode-dev
| libode0-dev, libopenal-dev, libcal3d-dev, swig, flex, bison, doxygen,
- libmng-dev, libsdl1.2-dev, libx11-dev, libcaca-dev, libwxgtk2.8-dev,
+ libmng-dev, libsdl1.2-dev, libx11-dev, libcaca-dev, libwxgtk3.0-dev,
libcegui-mk2-dev, python-dev, libcppunit-dev,
libasound-dev [ linux-any ], liblcms-dev, libcairo-dev, libcairomm-1.0-dev,
libgtk2.0-dev, jam, libgl1-mesa-dev | libgl-dev, libvorbis-dev,
diff -Nru crystalspace-2.0+dfsg/debian/patches/series crystalspace-2.0+dfsg/debian/patches/series
--- crystalspace-2.0+dfsg/debian/patches/series 2013-05-25 23:50:58.0 +1200
+++ crystalspace-2.0+dfsg/debian/patches/series 2014-06-14 21:05:00.0 +1200
@@ -3,3 +3,4 @@
sparc_defined_prev_in_CompareAndSet.diff
default_walktest_parallaxtest.diff
csstartme_startme_cfg_programs.diff
+wx3.0-compat.patch
diff -Nru crystalspace-2.0+dfsg/debian/patches/wx3.0-compat.patch crystalspace-2.0+dfsg/debian/patches/wx3.0-compat.patch
--- crystalspace-2.0+dfsg/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ crystalspace-2.0+dfsg/debian/patches/wx3.0-compat.patch 2014-06-14 21:05:21.0 +1200
@@ -0,0 +1,48 @@
+Description: Fix to build with wxwidgets3.0
+Author: Olly Betts o...@survex.com
+Last-Update: 2014-06-14
+
+--- crystalspace-2.0+dfsg.orig/plugins/video/canvas/wxgl/GLWXDriver2D.cpp
crystalspace-2.0+dfsg/plugins/video/canvas/wxgl/GLWXDriver2D.cpp
+@@ -292,7 +292,7 @@ bool csGraphics2DWX::Open()
+ {
+ Display* dpy = (Display*) wxGetDisplay ();
+ GLXContext active_GLContext = glXGetCurrentContext();
+-XVisualInfo *xvis = (XVisualInfo*)theCanvas-m_vi;
++XVisualInfo *xvis = theCanvas-GetXVisualInfo();
+
+ Report (CS_REPORTER_SEVERITY_NOTIFY, Video driver GL/X version %s,
+ glXIsDirect (dpy, active_GLContext) ? (direct renderer) :
+@@ -705,8 +705,8 @@ static bool wxCodeToCSCode(int wxkey, ut
+ MAP (MENU,CONTEXT, CONTEXT)
+ MAP (PAUSE, PAUSE,PAUSE)
+ MAP (CAPITAL, CAPSLOCK, CAPSLOCK)
+-MAP (PRIOR, PGUP, PGUP)
+-MAP (NEXT,PGDN, PGDN)
++MAP (PAGEUP, PGUP, PGUP)
++MAP (PAGEDOWN,PGDN, PGDN)
+ MAP (END, END, END)
+ MAP (HOME,HOME, HOME)
+ MAP (LEFT,LEFT, LEFT)
+@@ -722,10 +722,7 @@
Processed: Re: ganeti-2.11 - gnt-cluster upgrade writes config backup in /var/lib
Processing control commands: severity -1 serious Bug #754280 [ganeti-2.11] ganeti-2.11 - gnt-cluster upgrade writes config backup in /var/lib Severity set to 'serious' from 'normal' -- 754280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754280 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#755987: util-linux: FTBFS in the test suite on all architectures
Source: util-linux Version: 2.25-2 Severity: serious Justification: FTBFS Hi, your package still FTBFS on all buildds. This time it's due to different test failures across architectures. The full build summary is still at: https://buildd.debian.org/status/package.php?p=util-linuxsuite=experimental Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755846: libroar2: no multiarch possible
affects 755846 libopenal1 thanks On Thu, 24 Jul 2014 at 19:26:27 +0200, Patrick Matthäi wrote: Am 24.07.2014 um 12:14 schrieb Philipp Schafft: upstream speaking, I think this is a bug in the way OpenAL and/or roaraudio is packaged in Debian, not in upstream code, so there isn't a great deal of relevance for upstream here. I will have a look in the next days if it is possible with the current upstream code base. I think the most appropriate answer would be for libopenal1 to either drop the libroar-compat2 dependency again, or turn it into a dynamically-loaded plugin that can be dropped to Suggests (like its dependency on libportaudio2). I would say ... or Recommends, like libpulse0, but according to popcon, roaraudio is several orders of magnitude less widely used than pulseaudio, and only 0.45% of libroar-compat2 installations actually have roaraudio installed. Looking into libopenal1 in more detail, it doesn't actually have a backend to support roaraudio: what it supports is (among other things) libsndio, which as far as I can tell is the OpenBSD audio API. In OpenAL 1.14 this *was* dlopened, but in 1.15 it was changed upstream to use ordinary library linking. That makes perfect sense if you're on OpenBSD and libsndio is the audio API, but doesn't really make sense on Debian where sndio is really roaraudio. OpenAL maintainers, please consider reverting the sndio backend to use dlopen like 1.14 did, or dropping roaraudio-via-fake-sndio support until/unless someone provides an actual roaraudio backend analogous to the pulseaudio backend. A real roaraudio backend would make configuration make more sense, too: it seems more reasonable to enable roaraudio via drivers=roaraudio than to use drivers=sndio and rely on knowing that sndio is really roaraudio. I notice this isn't the first time libopenal1 has had an undesirable dependency chain from libroar-compat2: #673178. Looking at the multiarch situation anyway, for completeness: The libraries in libroar-compat2, which are all that OpenAL actually needs right now, look superficially OK for marking as multiarch. However, libroar-compat2 also contains /usr/bin/roarify which differs between architectures (it contains absolute paths to libroar.so.2, libroaross.so.2, /usr/lib/x86_64-linux-gnu/roaraudio/complibs, etc.). If libroar-compat2 is meant to be for manual use, more like aoss, pulsedsp, socksify etc., then nothing should be normal-library-linked to it. I notice that OpenAL seems to be the only thing using its libsndio, and the fact that it provides libsndio at all seems like an abuse of the fact that (a) OpenAL happens to have a libsndio backend, and (b) Debian happens to not have the real libsndio. On the other hand, if the intention is that other packages should be able to depend on the fake libsndio like libopenal1 does, I would suggest either: - generating a real libsndio2 package and having libopenal1 use that; or - making roarify a separate package that is Architecture:any, not multiarch, and depends on libroar-compat2 of the same architecture. Further down the stack, libroar-compat2 depends on libroar2. libroar2 also looks OK for multiarch: it only contains architecture-prefixed libraries. However, libroar2 depends on libdnet (#755934, etc.) which is not ready for multiarch: it contains /usr/lib/librms.so.2 which you will notice is not architecture-prefixed; so making libroar-compat2 and libroar2 multiarch while libdnet is used would just move this bug a couple of steps down the stack, to I can't install both libdnet:i386 and libdnet:amd64. The rest of the libraries that libroar2 depends on are already multiarch. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#755846: libroar2: no multiarch possible
Processing commands for cont...@bugs.debian.org: affects 755846 libopenal1 Bug #755846 [libroar2] libroar2: no multiarch possible Added indication that 755846 affects libopenal1 thanks Stopping processing here. Please contact me if you need assistance. -- 755846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755846 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#750870: Upstream issue
I've lodged an issue upstream asking for an OpenSSL linking exception. https://github.com/FreeRDP/Remmina/issues/286 Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor
Package: proftpd-mod-clamav Version: 0.10-1 Severity: critical Dear Maintainer, mod_clamav.c doesn't work and reports error: Can not stat file (9): Bad file descriptor on a new file coming to ftp folder. As I discovered with strace it closes a file descriptor before it tries to stat that descriptor. Best regards, Stanislav
Bug#755993: node-express-generator: uninstallable because of version number
Package: node-express-generator Version: 4.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, There's only one version ofthis package, and it depends on an inexistant version of another package, node-express (it breaks 4.1.1-1 and the only version available is 4.1.1~dfsg-1). I was unable to install it, apparently it's just a minor problem with version numbers. Thanks, Xav -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754326: gtick.desktop placed into wrong folder
[Mike Gabriel] the gtick.desktop file gets installed to /usr/share/application. It should be the plural form: /usr/share/applications. A misplaced desktop file do not seem like a release critical problem to me. Why do you believe the bug should have severity serious? -- Happy hacking Petter REinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755814: marked as done (kde4libs: CVE-2014-5033)
Your message dated Fri, 25 Jul 2014 10:50:58 + with message-id e1xad5w-0006qh...@franck.debian.org and subject line Bug#755814: fixed in kde4libs 4:4.13.3-2 has caused the Debian Bug report #755814, regarding kde4libs: CVE-2014-5033 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.) -- 755814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kde4libs Severity: grave Tags: security Justification: user security hole Hi, please see https://bugzilla.novell.com/show_bug.cgi?id=864716 for the original bug report. The upstream fix is available here: http://quickgit.kde.org/?p=kdelibs.gita=commith=e4e7b53b71e2659adaf52691d4accc3594203b23 We should also fix this in Wheezy. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: kde4libs Source-Version: 4:4.13.3-2 We believe that the bug you reported is fixed in the latest version of kde4libs, 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. Maximiliano Curia m...@debian.org (supplier of updated kde4libs 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: Fri, 25 Jul 2014 11:36:21 +0200 Source: kde4libs Binary: libkdecore5 libkdeui5 libkpty4 libkdesu5 libkjsapi4 libkjsembed4 libkio5 libkntlm4 libsolid4 libkde3support4 libkfile4 libknewstuff2-4 libknewstuff3-4 libkparts4 libkutils4 libthreadweaver4 libkhtml5 libkimproxy4 libkmediaplayer4 libktexteditor4 libknotifyconfig4 libkdnssd4 libkrosscore4 libkrossui4 libnepomuk4 libnepomukutils4 libnepomukquery4a libplasma3 libkunitconversion4 libkdewebkit5 libkcmutils4 libkemoticons4 libkidletime4 libkprintutils4 libkdeclarative5 kdelibs-bin kdelibs5-plugins kdelibs5-data kdoctools kdelibs5-dev kdelibs5-dbg Architecture: source amd64 all Version: 4:4.13.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Maximiliano Curia m...@debian.org Description: kdelibs-bin - core executables for KDE Applications kdelibs5-data - core shared data for all KDE Applications kdelibs5-dbg - debugging symbols for the KDE Development Platform libraries kdelibs5-dev - development files for the KDE Development Platform libraries kdelibs5-plugins - core plugins for KDE Applications kdoctools - various tools for accessing application documentation libkcmutils4 - utility classes for using KCM modules libkde3support4 - KDE 3 Support Library for the KDE 4 Platform libkdeclarative5 - declarative library for plasma libkdecore5 - KDE Platform Core Library libkdesu5 - Console-mode Authentication Library for the KDE Platform libkdeui5 - KDE Platform User Interface Library libkdewebkit5 - KDE WebKit Library libkdnssd4 - DNS-SD Protocol Library for the KDE Platform libkemoticons4 - utility classes to deal with emoticon themes libkfile4 - File Selection Dialog Library for KDE Platform libkhtml5 - KHTML Web Content Rendering Engine libkidletime4 - library to provide information about idle time libkimproxy4 - Instant Messaging Interface Library for the KDE Platform libkio5- Network-enabled File Management Library for the KDE Platform libkjsapi4 - KJS API Library for the KDE Development Platform libkjsembed4 - library for binding JavaScript objects to QObjects libkmediaplayer4 - KMediaPlayer Interface for the KDE Platform libknewstuff2-4 - Get Hot New Stuff v2 Library for the KDE Platform libknewstuff3-4 - Get Hot New Stuff v3 Library for the KDE Platform libknotifyconfig4 - library for configuring KDE Notifications libkntlm4 - NTLM Authentication Library for the KDE Platform libkparts4 - Framework for the KDE Platform Graphical Components libkprintutils4 - utility classes to deal with printing libkpty4 - Pseudo Terminal Library for the KDE Platform libkrosscore4 - Kross Core Library libkrossui4 - Kross UI Library libktexteditor4 - KTextEditor interfaces for the KDE Platform libkunitconversion4 - Unit Conversion library for the KDE Platform libkutils4 - dummy transitional library libnepomuk4 - Nepomuk
Bug#755993: [Pkg-javascript-devel] Bug#755993: node-express-generator: uninstallable because of version number
On 25 July 2014 11:44, Xavier Bestel xavier.bes...@free.fr wrote: I was unable to install it, apparently it's just a minor problem with version numbers. Hi Xavier, I can't reproduce this bug in a fresh installation of unstable (I was able to install, remove, purge it). Even piuparts reports no error about node-express-generator... are you sure about that? Regards, L. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: missing license in debian/copyright
Processing control commands: severity -1 important Bug #754863 [metacity] missing license in debian/copyright Severity set to 'important' from 'serious' tags -1 moreinfo Bug #754863 [metacity] missing license in debian/copyright Added tag(s) moreinfo. -- 754863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754863 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#754863: missing license in debian/copyright
Control: severity -1 important Control: tags -1 moreinfo Hi Thorsten, On Tue, 15 Jul 2014 12:44:17 +0200, Thorsten Alteholz wrote: [...] please add the missing licenses of: doc/creating_themes/* to debian/copyright. Was this bug report generated automatically? I think it is false positive. Indeed, creating_themes/C/index.docbook mentions the LGPL, but the context is: [...] Would it be useful to spin off Metacity's theme parsing code into a separate, LGPL-licensed library so that other applications could use it more easily? Licensecheck does not find any non-GPL files as well. I am lowering the severity of this bug to let the current version migrate from unstable to testing. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#755993: [Pkg-javascript-devel] Bug#755993: node-express-generator: uninstallable because of version number
Le vendredi 25 juillet 2014 à 12:52 +0200, Leo Iannacone a écrit :
On 25 July 2014 11:44, Xavier Bestel xavier.bes...@free.fr wrote:
I was unable to install it, apparently it's just a minor problem with
version numbers.
Hi Xavier,
I can't reproduce this bug in a fresh installation of unstable (I was
able to install, remove, purge it).
Even piuparts reports no error about node-express-generator... are you
sure about that?
OK, the bug report was a bit wrong: it's impossible to install alongside
node-express, which makes it a bit useless.
[root@awak:~]$ LANG=C aptitude install node-express-generator
The following NEW packages will be installed:
node-express-generator{b}
0 packages upgraded, 1 newly installed, 0 to remove and 103 not upgraded.
Need to get 0 B/7338 B of archives. After unpacking 97.3 kB will be used.
The following packages have unmet dependencies:
node-express-generator : Breaks: node-express ( 4.1.1-1) but 4.1.1~dfsg-1 is
installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) node-express
Accept this solution? [Y/n/q/?] ^C
[root@awak:~]$
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 755982 in 2.24.2-1, found 755982 in 2.25-2
Processing commands for cont...@bugs.debian.org: notfound 755982 2.24.2-1 Bug #755982 [util-linux] file conflict with bash-completion: dmesg and pgrep completion Bug #755984 [util-linux] util-linux: Packaging conflict with bash-completion No longer marked as found in versions util-linux/2.24.2-1. No longer marked as found in versions util-linux/2.24.2-1. found 755982 2.25-2 Bug #755982 [util-linux] file conflict with bash-completion: dmesg and pgrep completion Bug #755984 [util-linux] util-linux: Packaging conflict with bash-completion Marked as found in versions util-linux/2.25-2. Marked as found in versions util-linux/2.25-2. thanks Stopping processing here. Please contact me if you need assistance. -- 755982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755982 755984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755984 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#754619: works for me
I just tried building sdformat on MIPS and it build successfully with all tests passing. I suppose we should try building it again. signature.asc Description: Digital signature
Bug#753575: texlive-bin: FTBFS on s390x, test suite errors
Am 04.07.2014 08:03, schrieb Norbert Preining: Hi Matthias, you posted on debian-ports and some others about the 4.9 transition. I have now the problem with building texlive-bin on s390x. The resulting binaries segfault on various occasions during the tests. Switching to gcc/g++ 4.8 fixes this problem. Do you have any suggestion on how to fix that? I posted a lengthy description to the TeX Live builder list: https://www.tug.org/pipermail/tlbuild/2014q3/003012.html The problem is that compilation works, but the generated binaries are just not working in some cases. Before uploading a package which specifically selects the 4.8 compiler on s390x, I wanted to ask if you have any suggestion. we did have some offline communication, but the discussion died. So to summarize: - please use 4.9 with -O1 if the issue persists - please find out the subproject which needs to be built with -O1, don't build everything with -O1. thanks, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754326: gtick.desktop placed into wrong folder
On 07/25/2014 12:17 PM, Petter Reinholdtsen wrote: A misplaced desktop file do not seem like a release critical problem to me. Why do you believe the bug should have severity serious? Don't worry anyway, will upload a fix during the weekend. Sorry for the delay. Roland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: missing license in debian/copyright
Processing control commands: severity -1 serious Bug #754863 [metacity] missing license in debian/copyright Severity set to 'serious' from 'important' -- 754863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754863 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#754641: marked as done (qlandkartegt: FTBFS on kfreebsd-*: linking issues)
Your message dated Fri, 25 Jul 2014 12:22:14 + with message-id e1xaevq-0008v1...@franck.debian.org and subject line Bug#754641: fixed in qlandkartegt 1.7.7-2 has caused the Debian Bug report #754641, regarding qlandkartegt: FTBFS on kfreebsd-*: linking issues 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.) -- 754641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: qlandkartegt Version: 1.7.7-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-* due to linking issues: | Linking CXX executable ../bin/qlandkartegt | cd /«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu/src /usr/bin/cmake -E cmake_link_script CMakeFiles/qlandkartegt.dir/link.txt --verbose=1 | /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DGDALWARP=\gdalwarp\ -DGDALTRANSLATE=\gdal_translate\ -DGDALADDO=\gdaladdo\ -DGPSBABEL=\/usr/bin/gpsbabel\ -DMAP2JNX=\map2jnx\ -Wl,-z,relro CMakeFiles/qlandkartegt.dir/main.cpp.o CMakeFiles/qlandkartegt.dir/mitab.cpp.o CMakeFiles/qlandkartegt.dir/tcxreader.cpp.o CMakeFiles/qlandkartegt.dir/CActions.cpp.o CMakeFiles/qlandkartegt.dir/CMenus.cpp.o CMakeFiles/qlandkartegt.dir/GeoMath.cpp.o CMakeFiles/qlandkartegt.dir/WptIcons.cpp.o CMakeFiles/qlandkartegt.dir/CResources.cpp.o CMakeFiles/qlandkartegt.dir/CCopyright.cpp.o CMakeFiles/qlandkartegt.dir/CApplication.cpp.o CMakeFiles/qlandkartegt.dir/CMainWindow.cpp.o CMakeFiles/qlandkartegt.dir/CCanvas.cpp.o CMakeFiles/qlandkartegt.dir/CCanvasUndoCommandZoom.cpp.o CMakeFiles/qlandkartegt.dir/CStatusDEM.cpp.o CMakeFiles/qlandkartegt.dir/IMouse.cpp.o CMakeFiles/qlandkartegt.dir/CMouseMoveMap.cpp.o CMakeFiles/qlan dkartegt.dir/CMouseZoomMap.cpp.o CMakeFiles/qlandkartegt.dir/CMouseSelMap.cpp.o CMakeFiles/qlandkartegt.dir/CMouseAddWpt.cpp.o CMakeFiles/qlandkartegt.dir/CMouseMoveWpt.cpp.o CMakeFiles/qlandkartegt.dir/CMouseEditWpt.cpp.o CMakeFiles/qlandkartegt.dir/CMouseRefPoint.cpp.o CMakeFiles/qlandkartegt.dir/CMouseCutTrack.cpp.o CMakeFiles/qlandkartegt.dir/CMouseSelTrack.cpp.o CMakeFiles/qlandkartegt.dir/CMouseAddText.cpp.o CMakeFiles/qlandkartegt.dir/CMouseAddTextBox.cpp.o CMakeFiles/qlandkartegt.dir/CMouseAddDistance.cpp.o CMakeFiles/qlandkartegt.dir/CMouseAddArea.cpp.o CMakeFiles/qlandkartegt.dir/CMouseOverlay.cpp.o CMakeFiles/qlandkartegt.dir/CMouseColorPicker.cpp.o CMakeFiles/qlandkartegt.dir/CMouseSelWpt.cpp.o CMakeFiles/qlandkartegt.dir/IMap.cpp.o CMakeFiles/qlandkartegt.dir/CMapNoMap.cpp.o CMakeFiles/qlandkartegt.dir/CMapDEM.cpp.o CMakeFiles/qlandkartegt.dir/CMapFile.cpp.o CMakeFiles/qlandkartegt.dir/CMapLevel.cpp.o CMakeFiles/qlandkartegt.dir/CMapQMAP.cpp.o CMakeFiles/qlandkartegt.di r/CMapQMAPExport.cpp.o CMakeFiles/qlandkartegt.dir/CMapRaster.cpp.o CMakeFiles/qlandkartegt.dir/CMapGeoTiff.cpp.o CMakeFiles/qlandkartegt.dir/CMapWms.cpp.o CMakeFiles/qlandkartegt.dir/CMapTms.cpp.o CMakeFiles/qlandkartegt.dir/CMapJnx.cpp.o CMakeFiles/qlandkartegt.dir/CMapRmap.cpp.o CMakeFiles/qlandkartegt.dir/CMap3D.cpp.o CMakeFiles/qlandkartegt.dir/IMapSelection.cpp.o CMakeFiles/qlandkartegt.dir/CMapSelectionRaster.cpp.o CMakeFiles/qlandkartegt.dir/CMapSelectionGarmin.cpp.o CMakeFiles/qlandkartegt.dir/CMapSearchWidget.cpp.o CMakeFiles/qlandkartegt.dir/CMapSearchCanvas.cpp.o CMakeFiles/qlandkartegt.dir/CMapSearchThread.cpp.o CMakeFiles/qlandkartegt.dir/CMegaMenu.cpp.o CMakeFiles/qlandkartegt.dir/IDB.cpp.o CMakeFiles/qlandkartegt.dir/CWpt.cpp.o CMakeFiles/qlandkartegt.dir/CWptDB.cpp.o CMakeFiles/qlandkartegt.dir/CWptToolWidget.cpp.o CMakeFiles/qlandkartegt.dir/CSearch.cpp.o CMakeFiles/qlandkartegt.dir/CSearchDB.cpp.o CMakeFiles/qlandkartegt.dir/CSearchToolWidget.cpp.o CMakeFiles/qlan dkartegt.dir/CDlgConfig.cpp.o CMakeFiles/qlandkartegt.dir/CDlgEditWpt.cpp.o CMakeFiles/qlandkartegt.dir/CDlgWptIcon.cpp.o CMakeFiles/qlandkartegt.dir/CDlgEditMapLevel.cpp.o CMakeFiles/qlandkartegt.dir/CDlgCombineTracks.cpp.o CMakeFiles/qlandkartegt.dir/CDlgCombineDistOvl.cpp.o CMakeFiles/qlandkartegt.dir/CDlgProjWizzard.cpp.o CMakeFiles/qlandkartegt.dir/CDlgEditText.cpp.o CMakeFiles/qlandkartegt.dir/CDlgDelWpt.cpp.o CMakeFiles/qlandkartegt.dir/CDlgConvertToTrack.cpp.o CMakeFiles/qlandkartegt.dir/CDlgEditRoute.cpp.o CMakeFiles/qlandkartegt.dir/CDlgLoadOnlineMap.cpp.o CMakeFiles/qlandkartegt.dir/CDlgMapTDBConfig.cpp.o CMakeFiles/qlandkartegt.dir/CDlgMapQMAPConfig.cpp.o CMakeFiles/qlandkartegt.dir/CDlgMapJNXConfig.cpp.o
Bug#754863: missing license in debian/copyright
Hi, On Fri, 25 Jul 2014 14:12:50 +0200, Thorsten Alteholz wrote: This doesn't look like GPL and has no corresponding entry in your debian/copyright. There might be other files/licenses you forgot to mention ... Indeed you are right. I have now updated debian/copyright in Svn and asked for sponsorship. I also found some GPL-3+ and Expat-licensed files, included them to debian/copyright as well. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#754220: Re: virtualbox: FTBFS with GCC 4.9 as default
On 07/22/2014 04:06 PM, Vlad Orlov wrote: I see there's a new fixed version waiting at http://mentors.debian.net/package/virtualbox All RC bugs of virtualbox have been fixed by Gianfranco in git[1]. (Thanks! :-)) Gianfranco, do you plan a release in the next days? Cheers, Balint [1] http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755846: libroar2: no multiarch possible
reflum, On Fri, 2014-07-25 at 09:47 +0100, Simon McVittie wrote: affects 755846 libopenal1 thanks On Thu, 24 Jul 2014 at 19:26:27 +0200, Patrick Matthäi wrote: Am 24.07.2014 um 12:14 schrieb Philipp Schafft: upstream speaking, I think this is a bug in the way OpenAL and/or roaraudio is packaged in Debian, not in upstream code, so there isn't a great deal of relevance for upstream here. I just answerd because this report hit our mailinglist's spam filter somehow. I will have a look in the next days if it is possible with the current upstream code base. I think the most appropriate answer would be for libopenal1 to either drop the libroar-compat2 dependency again, or turn it into a dynamically-loaded plugin that can be dropped to Suggests (like its dependency on libportaudio2). I would say ... or Recommends, like libpulse0, but according to popcon, roaraudio is several orders of magnitude less widely used than pulseaudio, and only 0.45% of libroar-compat2 installations actually have roaraudio installed. RoarAudio isn't used in Debian *because* Ron Lee droped all the useful dependencies to it while his personal vendeta (see the archives). Droping dependencies is what broke the package. And Debian seems to be all about 'drop it, NEVER fix it!'. This bug report supports this. It's no longer about fixing but went directly into a droping request. As upstream I often hear from people that they wonder why RoarAudio isn't working when they install the debian package: The answer is because Debian decided (see archives) NOT to support RoarAudio because of in fact I never heared about any technical reason for that. I will consider to recommend Patrick Matthäi to send a removal request for RoarAudio as this ongoing drama is more harming the RoarAudio project than bringing anyone forward. Btw. as you also pointed to the DECnet support: It's perfectly the same: Dependencies to it were drop not fixed so it became useless while I see people worring about it on the project's mailinglist as they actually use it to make money. It's said to see such a grate project as Debian being no longer interesting in fixing problems. Looking into libopenal1 in more detail, it doesn't actually have a backend to support roaraudio: what it supports is (among other things) libsndio, which as far as I can tell is the OpenBSD audio API. In OpenAL 1.14 this *was* dlopened, but in 1.15 it was changed upstream to use ordinary library linking. That makes perfect sense if you're on OpenBSD and libsndio is the audio API, but doesn't really make sense on Debian where sndio is really roaraudio. OpenAL maintainers, please consider reverting the sndio backend to use dlopen like 1.14 did, or dropping roaraudio-via-fake-sndio support until/unless someone provides an actual roaraudio backend analogous to the pulseaudio backend. A real roaraudio backend would make configuration make more sense, too: it seems more reasonable to enable roaraudio via drivers=roaraudio than to use drivers=sndio and rely on knowing that sndio is really roaraudio. If someone is going to work on this, please let me know. I'm sure this can be done in a nice and smooth way! I notice this isn't the first time libopenal1 has had an undesirable dependency chain from libroar-compat2: #673178. Looking at the multiarch situation anyway, for completeness: The libraries in libroar-compat2, which are all that OpenAL actually needs right now, look superficially OK for marking as multiarch. However, libroar-compat2 also contains /usr/bin/roarify which differs between architectures (it contains absolute paths to libroar.so.2, libroaross.so.2, /usr/lib/x86_64-linux-gnu/roaraudio/complibs, etc.). If libroar-compat2 is meant to be for manual use, more like aoss, pulsedsp, socksify etc., then nothing should be normal-library-linked to it. It's consider to be useful for the user. That includes *both* manual use and direct linking. This is why directlinking works at all. Because it is designed to do so. I notice that OpenAL seems to be the only thing using its libsndio, and the fact that it provides libsndio at all seems like an abuse of the fact that (a) OpenAL happens to have a libsndio backend, and (b) Debian happens to not have the real libsndio. On the other hand, if the intention is that other packages should be able to depend on the fake libsndio like libopenal1 does, I would suggest either: - generating a real libsndio2 package and having libopenal1 use that; or As there is currently no other implementation I consider libroarsndio the non-openbsd port of libsndio. - making roarify a separate package that is Architecture:any, not multiarch, and depends on libroar-compat2 of the same architecture. Further down the stack, libroar-compat2 depends on libroar2. libroar2 also looks OK for multiarch: it only contains architecture-prefixed libraries. Please see roar-config --list-path. It will
Bug#754220: Re: virtualbox: FTBFS with GCC 4.9 as default
Hi to all, unfortunately I'm just a DM, not a DD and I cannot upload anything :( The major showstopper is that somebody should give a test try to the new package, to be sure it works with xorg-server 1.16 and the mesa showliness (with 3D acceleration) has been fixed Also the guest-additions needs to be tested with the new xorg. I did the tests by myself, and all was good, but I think some more feedbacks would be nice, in order to speedup the upload :) cheers, Gianfranco Il Venerdì 25 Luglio 2014 14:53, Balint Reczey bal...@balintreczey.hu ha scritto: On 07/22/2014 04:06 PM, Vlad Orlov wrote: I see there's a new fixed version waiting at http://mentors.debian.net/package/virtualbox All RC bugs of virtualbox have been fixed by Gianfranco in git[1]. (Thanks! :-)) Gianfranco, do you plan a release in the next days? Cheers, Balint [1] http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755846: libroar2: no multiarch possible
Hey there... an openal-soft maintainer here (who also works closely with openal-soft upstream), On Fri, Jul 25, 2014 at 3:20 PM, Philipp Schafft l...@lion.leolix.org wrote: reflum, On Fri, 2014-07-25 at 09:47 +0100, Simon McVittie wrote: affects 755846 libopenal1 thanks I will have a look in the next days if it is possible with the current upstream code base. I think the most appropriate answer would be for libopenal1 to either drop the libroar-compat2 dependency again, or turn it into a dynamically-loaded plugin that can be dropped to Suggests (like its dependency on libportaudio2). I would say ... or Recommends, like libpulse0, but according to popcon, roaraudio is several orders of magnitude less widely used than pulseaudio, and only 0.45% of libroar-compat2 installations actually have roaraudio installed. RoarAudio isn't used in Debian *because* Ron Lee droped all the useful dependencies to it while his personal vendeta (see the archives). Droping dependencies is what broke the package. And Debian seems to be all about 'drop it, NEVER fix it!'. This bug report supports this. It's no longer about fixing but went directly into a droping request. As upstream I often hear from people that they wonder why RoarAudio isn't working when they install the debian package: The answer is because Debian decided (see archives) NOT to support RoarAudio because of in fact I never heared about any technical reason for that. If someone wants to pick it up, dust it off, fix it up and upload it, I doubt anyone would stop them. The problem now is finding someone willing to do that. I will consider to recommend Patrick Matthäi to send a removal request for RoarAudio as this ongoing drama is more harming the RoarAudio project than bringing anyone forward. Btw. as you also pointed to the DECnet support: It's perfectly the same: Dependencies to it were drop not fixed so it became useless while I see people worring about it on the project's mailinglist as they actually use it to make money. It's said to see such a grate project as Debian being no longer interesting in fixing problems. If no one is interested in fixing the problem, then yeah, the problem gets dropped for the sake of expediency in solving a larger problem. Looking into libopenal1 in more detail, it doesn't actually have a backend to support roaraudio: what it supports is (among other things) libsndio, which as far as I can tell is the OpenBSD audio API. In OpenAL 1.14 this *was* dlopened, but in 1.15 it was changed upstream to use ordinary library linking. That makes perfect sense if you're on OpenBSD and libsndio is the audio API, but doesn't really make sense on Debian where sndio is really roaraudio. OpenAL maintainers, please consider reverting the sndio backend to use dlopen like 1.14 did, or dropping roaraudio-via-fake-sndio support until/unless someone provides an actual roaraudio backend analogous to the pulseaudio backend. Roger that, I'll get on this. I plan on keeping with upstream so it is likely that we'll go with option 2 until someone takes up the roaraudio packages. At this point, unless someone takes up that torch, we'll drop roaraudio-via-fake-sndio support until this gets fixed. (See below as to the real problem.) A real roaraudio backend would make configuration make more sense, too: it seems more reasonable to enable roaraudio via drivers=roaraudio than to use drivers=sndio and rely on knowing that sndio is really roaraudio. If someone is going to work on this, please let me know. I'm sure this can be done in a nice and smooth way! If someone would be so kind as to provide a patch upstream for Chris, I'm sure he would take it. It would eliminate our roaraudio-via-fake-sndio problem. However, libroar2 depends on libdnet (#755934, etc.) which is not ready for multiarch: it contains /usr/lib/librms.so.2 which you will notice is not architecture-prefixed; so making libroar-compat2 and libroar2 multiarch while libdnet is used would just move this bug a couple of steps down the stack, to I can't install both libdnet:i386 and libdnet:amd64. This is what I meant above: a sub-sub-sub-sub-sub depneds of a is not ready (but could be fixed) so let's drop a direct depends. Yay. Why is there no one working on getting librms fixed? At least upstream wasn't informed about any problem so it's debian internal again? Is there already a bug filed for librms? If this is the root of all evil and drama, then it should be handled. Cheers, Bret -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756023: init: Please drop Essential:yes from init metapackage
Package: init Version: 1.20 Severity: serious Tags: patch Dear Maintainer, init metapackage is marked essential, even though none of the inits are currently essential. There are environments in which no init is needed, e.g. chroots and minimal/exec-only containers (like docker). Also one shouldn't be making 3 inits transitively essential, when they currently are not. Patch attached. From 99cde7b65ed839df2250f9278847ca20c64e6fd6 Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov x...@ubuntu.com Date: Fri, 25 Jul 2014 15:15:33 +0100 Subject: [PATCH] Drop Essential: yes from init metapackage. None of the init's are currently essential, and there is no use for init in many environments, e.g. chroots / exec-only containers (docker). --- debian/changelog | 8 debian/control | 1 - 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index e01de73..8d68f82 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +init-system-helpers (1.21) UNRELEASED; urgency=medium + + * Drop Essential: yes from init metapackage. None of the init's are +currently essential, and there is no use for init in many +environments, e.g. chroots / exec-only containers (docker). + + -- Dimitri John Ledkov x...@ubuntu.com Fri, 25 Jul 2014 15:14:34 +0100 + init-system-helpers (1.20) unstable; urgency=medium [ Michael Stapelberg ] diff --git a/debian/control b/debian/control index c9fe0df..ef8beec 100644 --- a/debian/control +++ b/debian/control @@ -41,7 +41,6 @@ Description: debhelper add-on to handle systemd unit files Package: init Section: metapackages Architecture: any -Essential: yes Priority: required Pre-Depends: sysvinit-core | systemd-sysv [linux-any] | upstart [linux-any] Description: System-V-like init utilities - metapackage -- 2.0.1 Regards, Dimitri.
Bug#755846: libroar2: no multiarch possible
On 25/07/14 14:20, Philipp Schafft wrote: I just answerd because this report hit our mailinglist's spam filter somehow. As I said, this is entirely about how roaraudio's packaging in Debian (and that of its dependencies, and that of things that depend on it) is set up - the optional features that are enabled, the library installation paths, and how the binary packages are divided up. The only upstream code that's relevant to this particular issue is in OpenAL, where the sndio backend changed from using dlopen to using direct linking, which moved libroar-compat2 from a weak dependency (Suggests) to a mandatory dependency (Depends). That's why I suggested that it's the Debian maintainers of libopenal1 who should deal with this in the first instance. OpenAL can also output to PulseAudio, but libpulse0 is, appropriately, a weak dependency (Recommends); if you want to have libopenal1 installed, but libpulse0 or one of its dependencies is problematic, then that is entirely possible to do. A real roaraudio backend would make configuration make more sense, too: it seems more reasonable to enable roaraudio via drivers=roaraudio than to use drivers=sndio and rely on knowing that sndio is really roaraudio. If someone is going to work on this, please let me know. I'm sure this can be done in a nice and smooth way! That would be part of the ideal solution. However, I'm not going to work on that myself, because I have never used roaraudio, or had any reason to use it. My only interactions with roaraudio have been when it breaks the ability to install something that I do care about. If someone *does* care about roaraudio in Debian, it's up to them to make it not break other things. There is no cabal - there is no central dictator saying roaraudio must be removed from Debian now or Debian wants to use (pulseaudio|roaraudio|ALSA|OSS|printf '\a') as its preferred audio subsystem or anything like that. There are only cooperating maintainers making the best distribution we can, and sometimes that means a judgement call on sacrificing less-used functionality that is breaking things elsewhere. Why is there no one working on getting librms fixed? Yes, ideally libdnet would be set up to be multiarch too. Again, I have no interest in being able to network to obsolete Digital machines, so I don't plan to contribute to libdnet; anyone who does care about DECnet is welcome to do so. My only interaction with libdnet is this thing I have never wanted to use is a mandatory dependency, and is causing tangible problems for things I do use. At least upstream wasn't informed about any problem so it's debian internal again? Yes, this Debian bug report in the Debian bug tracking system is internal to Debian, and AIUI nobody has asked you to do anything about it. If roaraudio's Debian bugmail goes to you and you don't want it to, I suggest changing that. Users normally don't want features to be droped when they can be fixed. No, they don't; but please look at this from the point of view of someone who has no interest whatsoever in roaraudio. I tried to upgrade libopenal1. Because I occasionally use Wine for Windows binaries, I need both libopenal1:amd64 and libopenal1:i386 installed. At the moment, I can't have the current version of libopenal1 (and new installations would be impossible), for the benefit of an optional feature that makes libopenal1 able to output through a sound daemon that I don't even have. wine's popcon report says it has about a thousand times as many installations as roaraudio, and right now, it's uninstallable in unstable because of this bug. Ideally, libopenal1 would hook up to roaraudio in a way that does not introduce a hard dependency. But the world is not perfect, and until or unless that happens, it's a matter of least harm - I would rather break (libopenal1 output to) roaraudio for some people, if the alternative is breaking wine for a thousand times that many people. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 752195 normal Bug #752195 [apcupsd] apcupsd is not started via script Severity set to 'normal' from 'grave' quit Stopping processing here. Please contact me if you need assistance. -- 752195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752195 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#756023: init: Please drop Essential:yes from init metapackage
Control: severity -1 wishlist On 07/25/2014 16:19, Dimitri John Ledkov wrote: init metapackage is marked essential, even though none of the inits are currently essential. There are environments in which no init is needed, e.g. chroots and minimal/exec-only containers (like docker). Also one shouldn't be making 3 inits transitively essential, when they currently are not. They are already transitively essential: Package: sysvinit Version: 2.88dsf-53.2 Essential: yes [...] Pre-Depends: sysvinit-core | upstart | systemd-sysv init is intended to replace the sysvinit package; it doesn't change anything about init systems being essential or not. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#756023: init: Please drop Essential:yes from init metapackage
Processing control commands: severity -1 wishlist Bug #756023 [init] init: Please drop Essential:yes from init metapackage Severity set to 'wishlist' from 'serious' -- 756023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756023 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#755846: libroar2: no multiarch possible
On 25/07/14 15:07, bret curtis wrote: Is there already a bug filed for librms? If this is the root of all evil and drama, then it should be handled. It does not prevent libroar* from being made multiarch-compatible, but unless libroar* stops depending on it, it does prevent the entire stack from libroar* downwards from being multiarch. The necessary condition for being able to install :amd64 and :i386 flavours of a library is every library dependency, recursively, is multiarch. I'll file that bug, but in practice, it is not going to be fixed. libdnet is unmaintained (its maintainer is the Debian QA Group). In practice, this means anyone who cares about it enough is welcome to pick it up, but until or unless they do so, it will rot. I am really not surprised that it is unmaintained: from the package description, it appears to be there to communicate with Ultrix and VMS systems. I have a hard time caring much about such systems! S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block #745409 by #745454
Processing commands for cont...@bugs.debian.org: block 745409 by 745454 Bug #745409 [grub2] [grub2] Non free RFC 745409 was blocked by: 745453 745409 was not blocking any bugs. Added blocking bug(s) of 745409: 745454 End of message, stopping processing here. Please contact me if you need assistance. -- 745409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745409 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#755982: file conflict with bash-completion: dmesg and pgrep completion
Another file-conflict is bash-completion: /usr/share/bash-completion/completions/pgrep AFAIK pgrep have nothing to do with util-linux. Sorry if there is something i missed
Bug#755846: libroar2: no multiarch possible
block 755846 by 756032 thanks On Fri, 25 Jul 2014 at 15:26:33 +0100, Simon McVittie wrote: On 25/07/14 15:07, bret curtis wrote: Is there already a bug filed for librms? If this is the root of all evil and drama, then it should be handled. It does not prevent libroar* from being made multiarch-compatible, but unless libroar* stops depending on it, it does prevent the entire stack from libroar* downwards from being multiarch. Opened http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756032 roaraudio maintainers: if you disable the libdnet feature of roaraudio, please feel free to unblock 755846 by 756032. Similarly, if you know why roaraudio has any interest in DECnet, you're welcome to retitle 756032 to something more accurate and explain on that bug why it is desirable. Either making libdnet multiarch or dropping that dependency (whichever you prefer) is necessary, but not sufficient, for being able to install more than one architecture flavour of libroar* at a time. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#755846: libroar2: no multiarch possible
Processing commands for cont...@bugs.debian.org: block 755846 by 756032 Bug #755846 [libroar2] libroar2: no multiarch possible 755846 was not blocked by any bugs. 755846 was not blocking any bugs. Added blocking bug(s) of 755846: 756032 thanks Stopping processing here. Please contact me if you need assistance. -- 755846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755846 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#753184: marked as done (foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch')
Your message dated Fri, 25 Jul 2014 11:58:21 -0300 with message-id 20140725145821.GA3768@hesperos and subject line Closing reopened bug has caused the Debian Bug report #753184, regarding foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch' 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.) -- 753184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: foremost Version: 1.5.7-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140628 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Unpack source ─ gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file open error gpgv: Signature made Fri Jul 20 14:05:33 2012 UTC using RSA key ID EED3BC0D gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./foremost_1.5.7-4.dsc dpkg-source: info: extracting foremost in foremost-1.5.7 dpkg-source: info: unpacking foremost_1.5.7.orig.tar.gz dpkg-source: info: unpacking foremost_1.5.7-4.debian.tar.gz dpkg-source: info: applying fix-config-file-path.patch dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch' dpkg-source: info: applying fix-lintian-hardening-warnings.patch dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch 'fix-lintian-hardening-warnings.patch' is correctly applied by quilt, use 'quilt refresh' to update it FAILED [dpkg-source died] The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/28/foremost_1.5.7-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: foremost Source-Version: 1.5.7-5 Closing the bug. It was my bad for reopening in the first place. signature.asc Description: Digital signature ---End Message---
Processed: found 755038 in 7.14-2
Processing commands for cont...@bugs.debian.org:
# mark found in common anchestor
found 755038 7.14-2
Bug #755038 {Done: Gunnar Wolf gw...@debian.org} [src:drupal7] drupal7:
SA-CORE-2014-003 - Drupal core - Multiple vulnerabilities
Marked as found in versions drupal7/7.14-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
755038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755038
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#749974: new maitreya push
Hi Paul, On 23/07/14 12:46, Paul Elliott wrote: The presure to have a release ready is intense. I am worried about all this. Sorry if I pushed you too much, that wasn't my intention. What I wanted to say is that this doesn't seem to be a regression. maitreya would be getting these assertions with wxwidgets2.8 if those weren't hidden as they are. So hiding them on 3.0 would preserve the status quo. Anyway since you said upstream is working on this, there is no problem in waiting a bit for a fixed package. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754941: marked as done (mysql-5.5: Multiple security from July 2014 CPU)
Your message dated Fri, 25 Jul 2014 15:32:22 + with message-id e1xahtq-000899...@franck.debian.org and subject line Bug#754941: fixed in mysql-5.5 5.5.38-0+wheezy1 has caused the Debian Bug report #754941, regarding mysql-5.5: Multiple security from July 2014 CPU 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.) -- 754941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mysql-5.5 Severity: grave Tags: security Justification: user security hole Hi, please see http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html Cheers, Moritz ---End Message--- ---BeginMessage--- Source: mysql-5.5 Source-Version: 5.5.38-0+wheezy1 We believe that the bug you reported is fixed in the latest version of mysql-5.5, 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 754...@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 mysql-5.5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Jul 2014 16:15:21 +0200 Source: mysql-5.5 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite-5.5 mysql-source-5.5 Architecture: source all amd64 Version: 5.5.38-0+wheezy1 Distribution: wheezy-security Urgency: high Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.5 - MySQL database client binaries mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.5 - MySQL database server binaries and system database setup mysql-server-core-5.5 - MySQL database server binaries mysql-source-5.5 - MySQL source mysql-testsuite-5.5 - MySQL testsuite Closes: 754941 Changes: mysql-5.5 (5.5.38-0+wheezy1) wheezy-security; urgency=high . * Non-maintainer upload by the Security Team. * Imported Upstream version 5.5.38 fo fix security issues: - http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html - CVE-2014-2494 - CVE-2014-4207 - CVE-2014-4258 - CVE-2014-4260 (Closes: #754941) * Update copyright years for upstream files Checksums-Sha1: 383b3cecfdab8178c3d109d25efaf7fdb1cff9b3 2938 mysql-5.5_5.5.38-0+wheezy1.dsc 569c76385b24b981df35e703eefd34f9f76a2ee2 21739681 mysql-5.5_5.5.38.orig.tar.gz 8fc276bcdef617d2f11d8f123b749b555f7aa9bb 376907 mysql-5.5_5.5.38-0+wheezy1.debian.tar.gz 0d0d15142f7f267711f46eec0c83c4111e899cff 78574 mysql-common_5.5.38-0+wheezy1_all.deb b1ce0b482ffa0d23f2da954bf456382b4aad9e11 76860 mysql-server_5.5.38-0+wheezy1_all.deb c0e2f51a0a291f36c475fe2da2b77cbf0b7b10bc 76736 mysql-client_5.5.38-0+wheezy1_all.deb 0e253ba5a86f78b14bd5ac8e0c2c3ba80e0292c7 679972 libmysqlclient18_5.5.38-0+wheezy1_amd64.deb 5d3b01813e37db782f1de1f36a0971a921521583 3169042 libmysqld-pic_5.5.38-0+wheezy1_amd64.deb 7e7af31ef37cbc96a61b91458ce3dc6957d47c98 3164876 libmysqld-dev_5.5.38-0+wheezy1_amd64.deb 9cdfd7697b94baf9be4884a0db25c5990d93089e 948452 libmysqlclient-dev_5.5.38-0+wheezy1_amd64.deb 955e3226e13ab99e899023040604a45347e8ba45 1886316 mysql-client-5.5_5.5.38-0+wheezy1_amd64.deb 748607fe3c9401b2f0fdb0ecbbb89563d5c38b12 3777054 mysql-server-core-5.5_5.5.38-0+wheezy1_amd64.deb 0aa5cf1c80376b5795d3efa2a5eb61c379b67834 2097964 mysql-server-5.5_5.5.38-0+wheezy1_amd64.deb ee3dd938f52b0661e05f05178ea844431e6c5ea6 4247560 mysql-testsuite-5.5_5.5.38-0+wheezy1_amd64.deb 1d2af793caae54c8bef056c7618fa21e9a98ad53 22935164 mysql-source-5.5_5.5.38-0+wheezy1_amd64.deb
Bug#755059: marked as done (redmine: Unable to install backported version of Redmine (2.5.1-2~bpo70+1) due to missing deps)
Your message dated Fri, 25 Jul 2014 12:37:12 -0300 with message-id 20140725153712.ga32...@debian.org and subject line Re: Bug#755059: redmine: Unable to install backported version of Redmine (2.5.1-2~bpo70+1) due to missing deps has caused the Debian Bug report #755059, regarding redmine: Unable to install backported version of Redmine (2.5.1-2~bpo70+1) due to missing deps 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.) -- 755059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install the wheezy-backport version of Redmine since today due to the new uploaded debian version of redmine. Some dependencies are unavailable in backport but only in jessie/sid/exp. I'm not sure but I guess that dependencies for Redmine should be at least in backport too. Here are the apt error: # apt-get install redmine Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: redmine : Depends: ruby-railties-3.2 (= 3.2.16-1~) but it is not going to be installed Depends: ruby-rack (= 1.4.5~) but 1.4.1-2.1 is to be installed or ruby-rack1.4 but it is not installable Depends: ruby-awesome-nested-set but it is not installable E: Unable to correct problems, you have held broken packages. $ cat /etc/apt/sources.list.d/* deb http://pkg.jenkins-ci.org/debian binary/ deb http://security.debian.org/ wheezy/updates main deb http://http.debian.net/debian wheezy-updates main deb http://http.debian.net/debian wheezy-backports main $ cat /etc/apt/sources.list deb http://http.debian.net/debian wheezy main Cheers, Fabien -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.54-fbo (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Hello, On Thu, Jul 17, 2014 at 10:20:54AM +, Fabien Boucher wrote: Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install the wheezy-backport version of Redmine since today due to the new uploaded debian version of redmine. Some dependencies are unavailable in backport but only in jessie/sid/exp. I'm not sure but I guess that dependencies for Redmine should be at least in backport too. Here are the apt error: # apt-get install redmine Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: redmine : Depends: ruby-railties-3.2 (= 3.2.16-1~) but it is not going to be installed Depends: ruby-rack (= 1.4.5~) but 1.4.1-2.1 is to be installed or ruby-rack1.4 but it is not installable Depends: ruby-awesome-nested-set but it is not installable E: Unable to correct problems, you have held broken packages. $ cat /etc/apt/sources.list.d/* deb http://pkg.jenkins-ci.org/debian binary/ deb http://security.debian.org/ wheezy/updates main deb http://http.debian.net/debian wheezy-updates main deb http://http.debian.net/debian wheezy-backports main $ cat /etc/apt/sources.list deb http://http.debian.net/debian wheezy main Cheers, Fabien Since then, a new redmine version with corrected dependencies was uploaded, and ruby-awesome-nested-set was accepted
Bug#755982: file conflict with bash-completion: dmesg and pgrep completion
retitle 755982 file conflict with bash-completion: dmesg completion thanks Am 25.07.2014 16:42, schrieb Matías Z: Another file-conflict is bash-completion: /usr/share/bash-completion/completions/pgrep AFAIK pgrep have nothing to do with util-linux. Sorry if there is something i missed You are absolutely right of course. This was a mistake on my part, my grep-foo was too weak and I matched bash-completion: /usr/share/bash-completion/completions/pgrep util-linux: /usr/share/bash-completion/completions/pg which is of course non-sense. The only conflicting file is /usr/share/bash-completion/completions/dmesg I've also CCed the bash-completion bug. Dear bash-completion maintainers, please only drop /usr/share/bash-completion/completions/dmesg from the bash-completion package. Sorry for the confusion, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#755982: file conflict with bash-completion: dmesg and pgrep completion
Processing commands for cont...@bugs.debian.org: retitle 755982 file conflict with bash-completion: dmesg completion Bug #755982 [util-linux] file conflict with bash-completion: dmesg and pgrep completion Bug #755984 [util-linux] util-linux: Packaging conflict with bash-completion Changed Bug title to 'file conflict with bash-completion: dmesg completion' from 'file conflict with bash-completion: dmesg and pgrep completion' Changed Bug title to 'file conflict with bash-completion: dmesg completion' from 'util-linux: Packaging conflict with bash-completion' thanks Stopping processing here. Please contact me if you need assistance. -- 755982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755982 755984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755984 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#756038: gespeaker: missing dependency on python-xdg
Package: gespeaker Version: 0.8.2-1 Severity: serious Justification: Policy 3.5 Dependencies Hi, I just installed gespeaker and got: , | $ gespeaker | Traceback (most recent call last): | File gespeaker.py, line 28, in module | import gespeakerUI | File /usr/share/gespeaker/src/gespeakerUI.py, line 35, in module | import PreferencesWindow | File /usr/share/gespeaker/src/PreferencesWindow.py, line 21, in module | import Settings | File /usr/share/gespeaker/src/Settings.py, line 22, in module | from xdg.BaseDirectory import xdg_config_home | ImportError: No module named xdg.BaseDirectory ` Please add a dependency on python-xdg to solve this problem. Thanks, Dirk -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.15.6 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gespeaker depends on: ii alsa-utils 1.0.28-1 ii espeak 1.48.04+dfsg-1 ii espeak-data 1.48.04+dfsg-1 ii librsvg2-common 2.40.2-1 ii python-glade22.24.0-3+b1 ii python-gobject 3.12.1-1 ii python-gtk2 2.24.0-3+b1 pn python:any none gespeaker recommends no packages. Versions of packages gespeaker suggests: pn mbrola none -- 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#753184: Bug#755850: wheezy-pu: package foremost/1.5.7-5
Hello, On Wed, Jul 23, 2014 at 10:59:54PM +0100, Adam D. Barratt wrote: Control: tags -1 + confirmed On Wed, 2014-07-23 at 18:46 -0300, Raúl Benencia wrote: I would like to see foremost 1.5.7-5 in wheezy in order to fix #753184, You can't do that as described, as -5 is already in unstable/testing. However... Uh-oh, my bad. which is causing a FTBFS. The fix is quite trivial, and it's been in unstable since a couple of weeks. ... 1.5.7-5~deb7u1 would be fine, using wheezy as the upload target and assuming the resulting package has been built and tested on a wheezy system. Attached you'll find a debdiff with these changes. Also, here[0] is the link to the package DSC. [0] http://mentors.debian.net/debian/pool/main/f/foremost/foremost_1.5.7-5~deb7u1.dsc Please also fix the version metadata for #753184. As Guillem noted, re-opening the bug was not necessary. More specifically, it was wrong, as you've now told the BTS that the bug is not fixed in any version. I've fixed the metadata, thanks for pointing this out. Cheers, Raúl Benencia diff -Nru foremost-1.5.7/debian/changelog foremost-1.5.7/debian/changelog --- foremost-1.5.7/debian/changelog 2012-07-12 10:17:32.0 -0300 +++ foremost-1.5.7/debian/changelog 2014-07-25 13:06:56.0 -0300 @@ -1,3 +1,12 @@ +foremost (1.5.7-5~deb7u1) wheezy; urgency=medium + + * Update maintainer email address. + * Include new VCS control fields. + * Fix FTBFS caused by dpkg update. Thanks Juhani Numminen. (Closes: #753184) + * Bump standards version to 3.9.5, no changes. + + -- Raúl Benencia r...@kalgan.cc Fri, 25 Jul 2014 12:00:45 -0300 + foremost (1.5.7-4) unstable; urgency=low * Fix FTBFS on hurd by defining missing PATH_MAX macro diff -Nru foremost-1.5.7/debian/control foremost-1.5.7/debian/control --- foremost-1.5.7/debian/control 2012-07-09 21:28:07.0 -0300 +++ foremost-1.5.7/debian/control 2014-07-25 13:06:56.0 -0300 @@ -1,10 +1,12 @@ Source: foremost Section: admin Priority: optional -Maintainer: Raúl Benencia rbenen...@linti.unlp.edu.ar +Maintainer: Raúl Benencia r...@kalgan.cc Build-Depends: debhelper (= 9) -Standards-Version: 3.9.3 +Standards-Version: 3.9.5 Homepage: http://foremost.sourceforge.net/ +Vcs-Git: git://git.kalgan.cc/debian-pkg-foremost.git +Vcs-Browser: http://git.kalgan.cc/?p=debian-pkg-foremost.git Package: foremost Architecture: any diff -Nru foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch --- foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch 2012-07-10 01:46:30.0 -0300 +++ foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch 2014-07-25 13:06:56.0 -0300 @@ -1,5 +1,6 @@ Add hardening flags to compilation. Fix a format string in order to do -so.--- a/Makefile +so. +--- a/Makefile +++ b/Makefile @@ -37,7 +37,9 @@ WINCC = $(RAW_CC) $(RAW_FLAGS) -D__WIN32 signature.asc Description: Digital signature
Bug#752939: marked as done (Needs to be updated for the single cgroup manager changes in systemd v205)
Your message dated Fri, 25 Jul 2014 17:05:03 + with message-id e1xaivx-0006ee...@franck.debian.org and subject line Bug#752939: fixed in systemd-shim 6-4 has caused the Debian Bug report #752939, regarding Needs to be updated for the single cgroup manager changes in systemd v205 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.) -- 752939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-shim Version: 6-3 Severity: important systemd-shim is supposed to provide an environment where services from systemd, specifically timedated, localed, hostnamed and logind, are able to run without systemd being PID 1. Starting with version 205, the cgroup handling was moved into systemd exclusively [1], i.e. logind no longer creates any cgroup hierarchies on its own but relies on org.freedesktop.systemd1 to create it. The current version of systemd-shim doesn't provide this functionality. As a result, the logind version from experimental, atm this is v208, is no longer able to run standalone, i.e. with a PID 1 != systemd. systemd-shim needs to be updated to provide that functionality. For a non-systemd environment this functionality is most likely to be provided by cgmanager [2]. systemd-shim will either have to utilise a service like cgmanager or implement this functionality itself. For the time being, as systemd-shim does no longer provide the environment to run systemd-logind standaolone, libpam-systemd will drop the alternative dependency on systemd-shim and will rely on systemd-sysv exclusively. [1] http://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/ [2] https://cgmanager.linuxcontainers.org/ -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-shim depends on: ii libc6 2.19-4 ii libglib2.0-0 2.40.0-3 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-14 -- no debconf information ---End Message--- ---BeginMessage--- Source: systemd-shim Source-Version: 6-4 We believe that the bug you reported is fixed in the latest version of systemd-shim, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated systemd-shim 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: Fri, 25 Jul 2014 16:48:09 + Source: systemd-shim Binary: systemd-shim Architecture: source amd64 Version: 6-4 Distribution: unstable Urgency: medium Maintainer: Steve Langasek vor...@debian.org Changed-By: Steve Langasek vor...@debian.org Description: systemd-shim - shim for systemd Closes: 748791 752939 Changes: systemd-shim (6-4) unstable; urgency=medium . * Merge cgmanager support from Ubuntu; thanks to Serge Hallyn and Martin Pitt. Closes: #752939. * Fix wrong path used in the .maintscript file. Closes: #748791. Checksums-Sha1: 800efc8548e13461c1b8326707a1f479388ca565 1864 systemd-shim_6-4.dsc fcecd9f309ee856d8aa0e071f00406868f8e9974 9520 systemd-shim_6-4.debian.tar.xz fb28b89764bdd484cdde3f72cf6d12180bb94f39 14224 systemd-shim_6-4_amd64.deb Checksums-Sha256: a40f5a8393dd96a23cb2bf81576dedae99ec7d883419ba50f1fc78e26c1a3096 1864 systemd-shim_6-4.dsc 8aeb0f7c620f7908cfa4039d5d13693b6eedfd1118e983822c435aa69e1a8336 9520 systemd-shim_6-4.debian.tar.xz 0181c47e3402e012f4dbc2f974352c3224160c099411afa8550291209f529dbb 14224 systemd-shim_6-4_amd64.deb Files: dbc4e0fa28fc70f191632a44b3511d53 14224 admin extra systemd-shim_6-4_amd64.deb 0f05519fe65cdc219f36882b143c1cf9 1864 admin extra systemd-shim_6-4.dsc 05ed07045e36ab413c30de86de8e739b 9520 admin extra systemd-shim_6-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1
Bug#754538: marked as done (sqwebmail fails to install due to non-existant /var/www directory)
Your message dated Fri, 25 Jul 2014 17:33:43 + with message-id e1xajnh-0002cd...@franck.debian.org and subject line Bug#754538: fixed in courier 0.73.1-1.3 has caused the Debian Bug report #754538, regarding sqwebmail fails to install due to non-existant /var/www directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 754538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sqwebmail Version: 0.73.1-1.2 Severity: serious Justification: fails to install Hi Racke, sqwebmail fails to install if the directory /var/www does not exist (which apparently does not exist if nginx is installed as httpd-cgi): Entpacken von sqwebmail (0.73.1-1.2) ... Trigger für man-db (2.6.7.1-1) werden verarbeitet ... sqwebmail (0.73.1-1.2) wird eingerichtet ... ln: die symbolische Verknüpfung „/var/www/sqwebmail“ konnte nicht angelegt werden: Datei oder Verzeichnis nicht gefunden dpkg: Fehler beim Bearbeiten des Paketes sqwebmail (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: sqwebmail Should be easy to fix - I guess (but am not sure) the most proper way to fix this is to ship /var/www as part of the sqwebmail package. If you create it in the maintainer script, it is problematic to decide whether to delete it on package removal. Bye Willi -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sqwebmail depends on: ii courier-authlib 0.66.1-1 ii courier-base0.73.1-1.2 ii courier-maildrop0.73.1-1.2 ii cron3.0pl1-124.1 ii debconf [debconf-2.0] 1.5.53 ii expect 5.45-5 ii ingerman [ispell-dictionary]20131206-5 ii ispell 3.3.02-6 ii libc6 2.19-4 ii libfam0 2.7.0-17.1 ii libgdbm31.8.3-12+b1 ii libldap-2.4-2 2.4.39-1 ii libpcre31:8.31-5 ii nginx-full [httpd-cgi] 1.6.0-1 ii postfix [mail-transport-agent] 2.11.1-1 sqwebmail recommends no packages. Versions of packages sqwebmail suggests: pn courier-doc none pn courier-pcp none ii gnupg1.4.16-1.2 -- debconf information: sqwebmail/install-www-backup: symlink sqwebmail/install-www: symlink sqwebmail/calendarmode: local sqwebmail/dictionary: default ---End Message--- ---BeginMessage--- Source: courier Source-Version: 0.73.1-1.3 We believe that the bug you reported is fixed in the latest version of courier, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Willi Mann wi...@debian.org (supplier of updated courier 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: Fri, 25 Jul 2014 19:05:24 +0200 Source: courier Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl Architecture: source all amd64 Version: 0.73.1-1.3 Distribution: unstable Urgency: medium Maintainer: Stefan Hornburg (Racke) ra...@linuxia.de Changed-By: Willi Mann wi...@debian.org Description: courier-base - Courier mail server - base system courier-doc - Courier mail server - additional documentation courier-faxmail - Courier mail server - Fax-mail gateway courier-imap - Courier mail server - IMAP server courier-imap-ssl - Courier mail server - IMAP over SSL courier-ldap - Courier mail server - LDAP support courier-maildrop - Courier mail server - mail delivery agent courier-mlm - Courier mail server - mailing list manager courier-mta - Courier
Bug#753238: marked as done (ppl: FTBFS: Latex errors)
Your message dated Fri, 25 Jul 2014 20:38:46 +0200 with message-id 53d2a436.9020...@debian.org and subject line Re: Bug#753238: ppl: FTBFS: Latex errors has caused the Debian Bug report #753238, regarding ppl: FTBFS: Latex errors 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.) -- 753238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ppl Version: 1:1.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140628 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»/doc/user-configured-c-interface.latex-dir' rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl refman.pdf pdflatex refman This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e 2014/05/01 Babel 3.9k and hyphenation patterns for 2 languages loaded. (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2007/10/19 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/a4wide/a4wide.sty (/usr/share/texlive/texmf-dist/tex/latex/ntgclass/a4.sty)) (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty) (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg) (/usr/share/texlive/texmf-dist/tex/latex/pdftex-def/pdftex.def (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty) (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def)) (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty) (/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty) (/usr/share/texlive/texmf-dist/tex/latex/tocloft/tocloft.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg) (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty)) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/backref.sty (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)) (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)) Package hyperref Message: Driver: hpdftex. (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def) (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu) (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu) (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu) (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu))) (./doxygen.sty (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty) (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) (/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty) (/usr/share/texlive/texmf-dist/tex/latex/xtab/xtab.sty)) (/«PKGBUILDDIR»/doc/ppl.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty For additional information on amsmath, use the `?' option. (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi,
Thanks for your report.
2014-07-19 22:20 GMT+09:00 Andriy Martynets martyn...@volia.ua:
Package: bluez
Version: 5.21-1
Severity: serious
Justification: Policy 9.1.1
Dear Maintainer,
The issue appeared after upgrade to version 5.21.
The udev rule 50-bluetooth-hci-auto-poweron.rules tries to run
/usr/bin/hciconfig tool.
This rule is executed at early stage of boot process (/etc/rcS.d/S02udev)
when /usr is mounted later (/etc/rcS.d/S09mountall.sh).
In my understanding this tool must be installed in /sbin directory as one
needed at boot time. Alternatively this must be managed somehow
at later stage (e.g. 'udevadm trigger --verbose --action=add
--subsystem-match=bluetooth --sysname-match=hci*' command in
/etc/init.d/bluetooth)
I see.
I enabled the hciX in bluetooth.init in earlier versions.
I will revert this and remove 50-bluetooth-hci-auto-poweron.rules
from bluez package
I tried the mentioned above udevadm command and it helped. See modified file
below. It also contains alterations to fix bug #754830.
Best regards,
Andriy
Best regards,
Nobuhiro
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bluez depends on:
ii dbus 1.8.6-1
ii init-system-helpers 1.19
ii kmod 18-1
ii libc62.19-7
ii libdbus-1-3 1.8.6-1
ii libglib2.0-0 2.40.0-3
ii libreadline6 6.3-6
ii libudev1 208-6
ii lsb-base 4.1+Debian13
ii udev 208-6
bluez recommends no packages.
bluez suggests no packages.
-- Configuration Files:
/etc/init.d/bluetooth changed:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC=bluetooth
DAEMON=/usr/sbin/bluetoothd
HCIATTACH=/usr/sbin/hciattach
HID2HCI_ENABLED=1
HID2HCI_UNDO=1
UART_CONF=/etc/bluetooth/uart
RFCOMM_NAME=rfcomm
RFCOMM=/usr/bin/$RFCOMM_NAME
RFCOMM_CONF=/etc/bluetooth/$RFCOMM_NAME.conf
SDPTOOL=/usr/bin/sdptool
NOPLUGIN_OPTION=
SSD_OPTIONS=--oknodo --quiet --exec $DAEMON -- $NOPLUGIN_OPTION
test -f $DAEMON || exit 0
test -f /etc/default/bluetooth . /etc/default/bluetooth
test -f /etc/default/rcS . /etc/default/rcS
.. /lib/lsb/init-functions
set -e
run_sdptool()
{
# declaring IFS local in this function, removes the need to
# save/restore it
local IFS o
test -x $SDPTOOL || return 1
if ! test -z $SDPTOOL_OPTIONS ; then
IFS=;
for o in $SDPTOOL_OPTIONS ; do
#echo execing $SDPTOOL $o
IFS=
if [ $VERBOSE != no ]; then
$SDPTOOL $o
else
$SDPTOOL $o /dev/null 21
fi
done
fi
}
hci_input()
{
log_progress_msg switching to HID/HCI no longer done in init script, see
/usr/share/doc/bluez/NEWS.Debian.gz || :
}
alias enable_hci_input=hci_input
alias disable_hci_input=hci_input
start_uarts()
{
[ -f $HCIATTACH ] [ -f $UART_CONF ] || return
grep -v '^#' $UART_CONF | while read i; do
if [ $VERBOSE != no ]; then
$HCIATTACH $i
else
$HCIATTACH $i /dev/null 21
fi
done
}
stop_uarts()
{
killall ${HCIATTACH##*/} /dev/null 21 || :
}
start_rfcomm()
{
if [ -x $RFCOMM ] [ -f $RFCOMM_CONF ] ; then
# rfcomm must always succeed for now: users
# may not yet have an rfcomm-enabled kernel
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM bind all || :
else
$RFCOMM bind all /dev/null 21 || :
fi
fi
}
stop_rfcomm()
{
if [ -x $RFCOMM ] ; then
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM unbind all || :
else
$RFCOMM unbind all /dev/null 21 || :
fi
fi
}
restart_rfcomm()
{
if [ -x $RFCOMM ] [ -f $RFCOMM_CONF ] ; then
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM unbind all || :
$RFCOMM bind all || :
else
$RFCOMM unbind all /dev/null 21|| :
$RFCOMM bind all /dev/null 21 || :
fi
fi
}
case $1 in
start)
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi, Michael.
Thanks for your infomation.
I enabled the hciX in bluetooth.init in previous versions.
I will revert this function and remove udev rules in next version.
For systemd , I will enable using the ExecStartPre in bluetooth UNIT.
Please let me know if there is a better way other.
Best regards,
Nobuhiro
2014-07-22 22:39 GMT+09:00 Michael Biebl bi...@debian.org:
Instead of having each udev rule having to work around this issue, it
would be much better to simply mount /usr via the initramfs and
discourage the use of a separate /usr partition.
dracut can already do that, for initramfs-tools there is [1].
As a reality check you might be interested in the attached list.
Cheers,
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
Pkg-bluetooth-maintainers mailing list
pkg-bluetooth-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bluetooth-maintainers
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: PATCH: glob2: ftbfs with GCC-4.9
Processing commands for cont...@bugs.debian.org: tags 746854 patch Bug #746854 [src:glob2] glob2: ftbfs with GCC-4.9 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 746854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746854 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#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Am 25.07.2014 21:59, schrieb Nobuhiro Iwamatsu: Hi, Michael. Thanks for your infomation. I enabled the hciX in bluetooth.init in previous versions. I will revert this function and remove udev rules in next version. For systemd , I will enable using the ExecStartPre in bluetooth UNIT. Please let me know if there is a better way other. Well, you could just move hcitool to /bin. It seems all it's library dependencies are already in /lib. Are there any ressources hcitool needs from /usr? Fwiw, I don't think running udevadm trigger from the .service file (or sysvinit init script) is such a great idea. Even if it is limited to the bluetooth subsystem. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#756061: Lack of time by maintainer
Package: barry Version: 0.18.5-1 Severity: serious Tags: moreinfo upstream confirmed sid jessie As the maintainer of the package, I don't have enough time to handle important bugs like the recent wxWidgets 3.0 transition. This time situation may change in the near future, but until then, Barry is not suitable for a stable release. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754665: tatan: FTBFS on armel/armhf: error: module string is in file 'std/string.d' which cannot be read
Control: severity -1 normal Control: tags -1 confirmed pending I have requested a give-back for tatan on debian-wb-t...@lists.debian.org since the build-dependency, libphobos-4.9-dev, is now installable on armel/armhf. Markus signature.asc Description: OpenPGP digital signature
Processed: tatan: FTBFS on armel/armhf: error: module string is in file 'std/string.d' which cannot be read
Processing control commands: severity -1 normal Bug #754665 [src:tatan] tatan: FTBFS on armel/armhf: error: module string is in file 'std/string.d' which cannot be read Severity set to 'normal' from 'serious' tags -1 confirmed pending Bug #754665 [src:tatan] tatan: FTBFS on armel/armhf: error: module string is in file 'std/string.d' which cannot be read Added tag(s) confirmed and pending. -- 754665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754665 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#749974: new maitreya push
On Fri, Jul 25, 2014 at 05:14:15PM +0200, Emilio Pozuelo Monfort wrote: What I wanted to say is that this doesn't seem to be a regression. maitreya would be getting these assertions with wxwidgets2.8 if those weren't hidden as they are. So hiding them on 3.0 would preserve the status quo. The libwxgtk2.8-dbg package contains a build of wxwidgets2.8 with WXDEBUG enabled (like wxwidgets3.0 has by default) if you want to confirm this for yourself. You will need to rebuild wxsqlite3 against this first though, as the WXDEBUG build is ABI incompatible with the standard build, so mixing the two won't work. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: dbusada: Increase gnat version on dependencies
Processing control commands: retitle -1 dbusada: uninstallable on sid, needs update for gnat-4.9 Bug #755076 [src:dbusada] dbusada: Increase gnat version on dependencies Changed Bug title to 'dbusada: uninstallable on sid, needs update for gnat-4.9' from 'dbusada: Increase gnat version on dependencies' severity -1 grave Bug #755076 [src:dbusada] dbusada: uninstallable on sid, needs update for gnat-4.9 Severity set to 'grave' from 'normal' block 756078 by -1 Bug #756078 [release.debian.org] transition: gnat 756078 was blocked by: 755014 755009 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 755076 -- 755076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755076 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 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: apq: uninstallable on sid, needs update for gnat-4.9
Processing control commands: retitle -1 apq: uninstallable on sid, needs update for gnat-4.9 Bug #755014 [apq] apq: Increase gnat version on dependencies Changed Bug title to 'apq: uninstallable on sid, needs update for gnat-4.9' from 'apq: Increase gnat version on dependencies' severity -1 grave Bug #755014 [apq] apq: uninstallable on sid, needs update for gnat-4.9 Severity set to 'grave' from 'normal' block 756078 by -1 Bug #756078 [release.debian.org] transition: gnat 756078 was blocked by: 755009 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 755014 -- 755014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755014 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 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: adasockets: uninstallable on sid, needs update for gnat-4.9
Processing control commands: retitle -1 adasockets: uninstallable on sid, needs update for gnat-4.9 Bug #755009 [src:adasockets] adasockets: Increase gnat version on dependencies Changed Bug title to 'adasockets: uninstallable on sid, needs update for gnat-4.9' from 'adasockets: Increase gnat version on dependencies' severity -1 grave Bug #755009 [src:adasockets] adasockets: uninstallable on sid, needs update for gnat-4.9 Severity set to 'grave' from 'normal' block 756078 by -1 Bug #756078 [release.debian.org] transition: gnat 756078 was not blocked by any bugs. 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 755009 -- 755009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755009 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 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: your mail
Processing commands for cont...@bugs.debian.org: block 756078 by 753957 Bug #756078 [release.debian.org] transition: gnat 756078 was blocked by: 755014 755076 755009 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 753957 End of message, stopping processing here. Please contact me if you need assistance. -- 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 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: apq-postgresql: uninstallable on sid, needs update for gnat-4.9
Processing control commands: retitle -1 apq-postgresql: uninstallable on sid, needs update for gnat-4.9 Bug #755016 [apq-postgresql] apq-postgresql: Increase gnat version on dependencies Changed Bug title to 'apq-postgresql: uninstallable on sid, needs update for gnat-4.9' from 'apq-postgresql: Increase gnat version on dependencies' severity -1 grave Bug #755016 [apq-postgresql] apq-postgresql: uninstallable on sid, needs update for gnat-4.9 Severity set to 'grave' from 'normal' block 756078 by -1 Bug #756078 [release.debian.org] transition: gnat 756078 was blocked by: 755014 755009 755076 753957 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 755016 -- 755016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755016 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 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#756081: libanet0.1: uninstallable on sid, needs update for gnat-4.9
Package: libanet0.1 Version: 0.1-3 Severity: grave Control: block 756078 by -1 Your package is uninstallable because it depends on both gnat and gnat-4.6, but gnat depends on gnat-4.9, and gnat-4.6 and gnat-4.9 are not coinstallable. You need to update it to depend on gnat-4.9 instead of gnat-4.6. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: libanet0.1: uninstallable on sid, needs update for gnat-4.9
Processing control commands: block 756078 by -1 Bug #756078 [release.debian.org] transition: gnat 756078 was blocked by: 755014 755016 755076 755009 753957 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 756081 -- 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 756081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756081 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: your mail
Processing commands for cont...@bugs.debian.org: reassign 755007 adacgi1 Bug #755007 [src:adacgi] adacgi: Increase gnat version on dependencies Bug reassigned from package 'src:adacgi' to 'adacgi1'. No longer marked as found in versions adacgi/1.6-17. Ignoring request to alter fixed versions of bug #755007 to the same values previously set forcemerge 753955 753955 Bug #753955 [adacgi1] adacgi1: not installable in sid Merged 753955 block 756078 by 753955 Bug #756078 [release.debian.org] transition: gnat 756078 was blocked by: 756081 755014 755009 755076 755016 753957 756078 was not blocking any bugs. Added blocking bug(s) of 756078: 753955 thanks Stopping processing here. Please contact me if you need assistance. -- 753955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753955 755007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755007 756078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756078 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#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi, Michael.
Thanks for your comment.
2014-07-26 5:12 GMT+09:00 Michael Biebl bi...@debian.org:
Am 25.07.2014 21:59, schrieb Nobuhiro Iwamatsu:
Hi, Michael.
Thanks for your infomation.
I enabled the hciX in bluetooth.init in previous versions.
I will revert this function and remove udev rules in next version.
For systemd , I will enable using the ExecStartPre in bluetooth UNIT.
Please let me know if there is a better way other.
Well, you could just move hcitool to /bin. It seems all it's library
dependencies are already in /lib.
I see.
Are there any ressources hcitool needs from /usr?
No, there are any resources.
Fwiw, I don't think running udevadm trigger from the .service file (or
sysvinit init script) is such a great idea. Even if it is limited to the
bluetooth subsystem.
OK, I will think about move hcitool to /bin.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Thanks again.
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
