Bug#653125: Farsi characters problem
Package: debian-i18n Severity: grave Tags: l10n Justification: renders package unusable Dear Maintainer, Farsi layout is working system wide without any problem, but using terminal or vim or gvim, farsi characters are just bunch of question marks. I tried to change terminal profile's font but no success. Even no success with BiCON. I reconfigured locale package and even tried to set some env. Here is my locale output: LANG=fa_IR:fa LANGUAGE=en_US:en LC_CTYPE=fa_IR:fa LC_NUMERIC=fa_IR:fa LC_TIME=fa_IR:fa LC_COLLATE=fa_IR:fa LC_MONETARY=fa_IR:fa LC_MESSAGES=fa_IR:fa LC_PAPER=fa_IR:fa LC_NAME=fa_IR:fa LC_ADDRESS=fa_IR:fa LC_TELEPHONE=fa_IR:fa LC_MEASUREMENT=fa_IR:fa LC_IDENTIFICATION=fa_IR:fa LC_ALL=fa_IR:fa As I told not all the applications are affected for example gedit is working fine, but the annoying part happens when I want to use services that are run from terminal. For example kannel. When I call the api and send a Farsi string, it receives all of them as question marks and send sms as just bunch of question marks. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653127: sflphone: FTBFS on s390 (#error Please specify target machine)
Source: sflphone Version: 1.0.1-4 Severity: serious Justification: fails to build from source (but built successfully in the past) sflphone fails to build on the s390 build daemons: https://buildd.debian.org/status/fetch.php?pkg=sflphonearch=s390ver=1.0.1-4stamp=1322213694 libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -I../../libs -I../../libs/iax2 -I../../libs/pjproject -I../../src -I../../src/config -I../../test -I../../libs/pjproject/pjsip/include -I../../libs/pjproject/pjlib/include -I../../libs/pjproject/pjlib-util/include -I../../libs/pjproject/pjmedia/include -I../../libs/pjproject/pjnath/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/dbus-1.0 -I/usr/lib/s390-linux-gnu/dbus-1.0/include -I/usr/include/dbus-c++-1 -DPREFIX=\/usr\ -DPROGSHAREDIR=\/usr/share/sflphone\ -DCODECS_DIR=\/usr/lib/sflphone/codecs\ -DPLUGINS_DIR=\/usr/lib/sflphone/plugins\ -DENABLE_TRACE -DHAVE_SPEEX_CODEC -DHAVE_GSM_CODEC -DPREFIX=\/usr\ -DPROGSHAREDIR=\/usr/share/sflphone\ -DUSE_NETWORKMANAGER -g -O2 -g -Wno-return-type -Wall -Wextra -Wnon-virtual-dtor -Weffc++ -Wfatal-errors -MT libdbus_la-callmanager.lo -MD -MP -MF .deps/libdbus_la-callmanager.Tpo -c callmanager.cpp -fPIC -DPIC -o .libs/libdbus_la-callmanager.o In file included from ../../libs/pjproject/pjmedia/include/pjmedia/config.h:27:0, from ../../libs/pjproject/pjmedia/include/pjmedia/types.h:28, from ../../libs/pjproject/pjmedia/include/pjmedia/echo.h:28, from ../../src/audio/echosuppress.h:11, from ../../src/audio/audiortp/audio_rtp_record_handler.h:45, from ../../src/audio/audiortp/audio_rtp_session.h:37, from ../../src/audio/audiortp/audio_rtp_factory.h:37, from ../../src/sip/sipcall.h:36, from callmanager.cpp:36: ../../libs/pjproject/pjlib/include/pj/config.h:269:5: error: #error Please specify target machine. compilation terminated due to -Wfatal-errors. make[6]: *** [libdbus_la-callmanager.lo] Error 1 A quick fix would be nice as sflphone is involved of the current evolution-data-server transition. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644826: ace: Ace FTBFS on armel with ICE
On Fri, Dec 9, 2011 at 10:52:33 +0100, Thomas Girard wrote: The only way to work around this is to use gcc-4.4 on armel. Is this an acceptable work-around, i.e. how long will gcc 4.4 be in unstable? Yes please, it looks like using 4.4 is the way to go for now. Thanks, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653131: amsn: FTBFS during rebuild with /bin/sh: 1: autoreconf: not found
Package: amsn Version: 0.98.4-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, We were recompiling amsn as a part of the gssdp/gupnp transition and it failed to build on several architectures. The last part of the amd64 log on the buildd[1]: [...] DEBUG: no STATIC : no FARSIGHT : yes LIBV4L : yes GUPNP-IGD: yes dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory `/build/buildd-amsn_0.98.4-4+b1-amd64-IekHIN/amsn-0.98.4' (cd .; autoreconf -i) /bin/sh: 1: autoreconf: not found make[1]: *** [configure] Error 127 make[1]: Leaving directory `/build/buildd-amsn_0.98.4-4+b1-amd64-IekHIN/amsn-0.98.4' make: *** [build-stamp] Error 2 [1] https://buildd.debian.org/status/package.php?p=amsnsuite=sid ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653009: every firmware postrm scripts deletes files that were not installed by the package
Hi, Fabrizio Regalli wrote (23 Dec 2011 11:04:55 GMT) : Right but in any case, if you want to purge or remove the package, directory /lib/firmware/b43 needs to be removed regardless of the firmware installed. I seems to me the implicit logics behind both your reply and the current behaviour of these packages boils down to I need to do dpkg's job myself, sorry if I cannot do it as well as dpkg. I don't understand why this makes sense. So in the first place, why is that directory managed by hand^Wmaintainer scripts instead of letting dpkg deal with it (I mean, install / remove it as part of the binary packages)? Cheers, -- intrigeri intrig...@boum.org | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc | Every now and then I get a little bit restless | and I dream of something wild. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 650050 in 0.2.90~20111111-2
Processing commands for cont...@bugs.debian.org:
fixed 650050 0.2.90~2011-2
Bug #650050 {Done: Josselin Mouette j...@debian.org} [src:evolution-rss]
FTBFS: e-shell-taskbar.h:62:2: error: unknown type name 'GtkHBox'
The source evolution-rss and version do not appear to match any binary packages
Bug Marked as fixed in versions evolution-rss/0.2.90~2011-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
650050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650050
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#653003: closed by Fabrizio Regalli fab...@fabreg.it (Bug#653003: fixed in requestpolicy 0.5.23-3)
Hi,
Debian Bug Tracking System wrote (22 Dec 2011 21:36:59 GMT) :
#653003: xul-ext-requestpolicy: Need update for Iceweasel/Firefox 9
It has been closed by Fabrizio Regalli fab...@fabreg.it.
Thank you for taking care of this.
+-em:maxVersion9.0a1/em:maxVersion
++em:maxVersion*/em:maxVersion
I'm a bit surprised this bug was fixed by optimistically betting the
extension will work with any future iceweasel version; I understood
the introduction of ${xpi:Breaks} as a way to express in a more formal
and strict way the guaranteed fact that extension X works fine with
this set of versions of iceweasel; therefore, the s/9\.0a1/*/ patch
introduced in requestpolicy/0.5.23-3 seems like a step backward to me.
So this makes me curious: is that commonly considered good practice
among the Debian Mozilla Extension team? Do we patch other XUL
extensions this way in Debian? Is there a project of doing this
consistently to all XUL extensions packaged in Debian, or merely to go
on doing this on a case by case basis, only when needed?
Cheers,
--
intrigeri intrig...@boum.org
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
| The impossible just takes a bit longer.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653135: xul-ext-add-in-one-sidebar: not compatible with Iceweasel 9.0
Package: xul-ext-all-in-one-sidebar Version: 0.7.14-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since iceweasel 9.0.1-1 is now in unstable it's not possible to install xul-ext-add-in-one-sidebar in unstable anymore: # apt-get install iceweasel xul-ext-all-in-one-sidebar 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: xul-ext-all-in-one-sidebar : Breaks: iceweasel (= 8.+) but 9.0.1-1 is to be installed E: Broken packages -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJO9bs3AAoJEGny/FFupxmTXz4P/0FnVUHiYcA1vzMTraLYY6C5 o0lny1s4+4mGSkhwSL+kuo5ssOLgy2bAQp2DCGiA05sMqpANg2bDABv63ZlI8RCw DC8isChA87g6wCxWPF+wq4YOZuO/FYi8M65MS7z6vsBoQ7oEsEZ+uyXn0Etll0XP uu23fJH+fVSG4YBoBKd2Lz/b3M8nuGBeuCLZ3Qi5qvvIEW+geG9DQSFY3GLzc4pv oSXcPrwiLvYIGP6cBzva3dfM0eB4x+cQ8fo4aIarRX/u5B9fMxrTmqVx/x187JsL VTTVUvNHWhIBhFKrJbem8MCfe28ckFi2JZiWG6cw4zByHnfp+UP0mHgkuX0kPGJb zw09PV8JEDnIp/7D3qTqrVK+KU1RpT6dlvQDg5+aWJLtgLOWwa+UaaM+s28FgGsG FhMKQdZvc7xq8RnfGHYKfMLyaNFFV4alhgLn1J31Kk8jxr9zeftGOdvS7sr3jQSC mlXIdBxD/ekORaRbz0uigmDWcitTaDfk0WlHWteloH6HTlUWFKLkGcxQTtDI/FiF 7idjfOTDmCGn/cCHGRzfigYAcEl8VkXtskfVDF2am+ftlPZoVwwi9Ar1FbvlOP+E 7n7U2nrpNqXgLgDjKyGuEtNqcGA/8UQpJNyYun3fWDysgDFT/8H/gvbAY42pghoF gA0maGEbkbRWqgOpk9Vc =bcGo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639590: marked as done (binutils-z80: unbuildable in unstable)
Your message dated Sat, 24 Dec 2011 11:47:30 + with message-id e1req4y-0004rn...@franck.debian.org and subject line Bug#639590: fixed in binutils-z80 2.22-1 has caused the Debian Bug report #639590, regarding binutils-z80: unbuildable in unstable 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.) -- 639590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: binutils-z80 Version: 2.21.52-2 Severity: serious Hi, binutils-z80 build-depends on binutils-source ( 2.21.53), but unstable now has 2.21.53.20110823-3 thus rendering -z80 unbuildable. Regards, Adam ---End Message--- ---BeginMessage--- Source: binutils-z80 Source-Version: 2.22-1 We believe that the bug you reported is fixed in the latest version of binutils-z80, which is due to be installed in the Debian FTP archive: binutils-z80_2.22-1.debian.tar.gz to main/b/binutils-z80/binutils-z80_2.22-1.debian.tar.gz binutils-z80_2.22-1.dsc to main/b/binutils-z80/binutils-z80_2.22-1.dsc binutils-z80_2.22-1_amd64.deb to main/b/binutils-z80/binutils-z80_2.22-1_amd64.deb binutils-z80_2.22.orig.tar.gz to main/b/binutils-z80/binutils-z80_2.22.orig.tar.gz 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 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Garcia agar...@igalia.com (supplier of updated binutils-z80 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Dec 2011 03:39:10 +0100 Source: binutils-z80 Binary: binutils-z80 Architecture: source amd64 Version: 2.22-1 Distribution: unstable Urgency: low Maintainer: Alberto Garcia agar...@igalia.com Changed-By: Alberto Garcia agar...@igalia.com Description: binutils-z80 - GNU binary utilities for the z80-unknown-coff target Closes: 634060 639590 652451 Changes: binutils-z80 (2.22-1) unstable; urgency=low . * Update to binutils 2.22 (Closes: #639590): - debian/rules: change version of tar.gz file. - debian/control: update build dependency. * Take over maintainership (Closes: #634060, #652451): - debian/control: update Maintainer field. * debian/control: update Standards-Version to 3.9.2. * debian/control: remove redundant fields from the binary paragraph. * debian/control: fix 'description-synopsis-starts-with-article'. * debian/rules: add build-indep and build-arch targets. * debian/rules: patch tc-z80.c instead of shipping an entire copy of the file. * debian/watch: new file. * debian/copyright: rewrite using the machine-readable format. Checksums-Sha1: 1f7ca2a7e4f1d2bbe777529a4c6bc7e22c62f1b3 1933 binutils-z80_2.22-1.dsc cc180d127ad6cbce1a1e2112bc127b01b7968dec 244 binutils-z80_2.22.orig.tar.gz 68dbfc6dd6f64938206bff82233d2f26764b2d2e 4064 binutils-z80_2.22-1.debian.tar.gz 826b1ee2a8a3c79ac0516a5e2b88623652f02e62 2632528 binutils-z80_2.22-1_amd64.deb Checksums-Sha256: 43407fc94b802d2ad78a81f056fd9c4426f37ed760a9438271d04f787e79bdff 1933 binutils-z80_2.22-1.dsc 9beffa8c8eb605d2639deb9039517798a61cba9b167451cf0725eee45fa1be69 244 binutils-z80_2.22.orig.tar.gz e2cf79343d5a444be347e45f963b68d5bea1bf88da93cb7e26f623393ae69aa6 4064 binutils-z80_2.22-1.debian.tar.gz e612c9a450dca14b329ae07965a1f2232513ba173ad546a86810433092ab3cdd 2632528 binutils-z80_2.22-1_amd64.deb Files: 3bd33f41d5da3fe062646d3c5d80d92f 1933 devel extra binutils-z80_2.22-1.dsc 17547a64e10449d71227099295661a23 244 devel extra binutils-z80_2.22.orig.tar.gz ac8002db4b72578002f2be328f9d4e56 4064 devel extra binutils-z80_2.22-1.debian.tar.gz 76adcee714cb020c9bd7c65a6c29f48d 2632528 devel extra binutils-z80_2.22-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJO9blxAAoJEEkIatPr4vMfvaoP/3/4X2YqatjwiBs0T/S5u2J+ dtvq0QDPudvkDqev30pkle0+IFoMplrfXdZFUX8sDa3jTdcyBBX9XXTilxFubFN1 bJgyoGIVYmL5Ke7FPJlv4OMPI7U1K7bglAcn2E5hF6LsCv3Xck3Ad2nToccszHfB qMBKWHdPJFXxjdiyqGIUwdWY3QuqFWUvbI1xK9XAAbSBu3TPtZJfD6Ql54EN3gv6 m9nGxIVrYyKgpRgGvdvU1Lrs6KnISMMA0IG82Q8KBNyWF+5oh24pvnwEtMjzXlZC 4s1kPqzc2tA9aDPDe59N79oquz30GyaSKFYXHUtNRcrGyxwGrNh2hCGlvGdhdv41 OKxu1EIz+3gvWCegdwHeXvff6fxS9e0y3QyjgA67IUC8ha1yfVdxEeFx+55nP56I
Bug#652842: marked as done (Depends on obsolete libgdata1.8-cil)
Your message dated Sat, 24 Dec 2011 11:47:45 + with message-id e1req4n-0004ty...@franck.debian.org and subject line Bug#652842: fixed in gnome-do-plugins 0.8.4-3 has caused the Debian Bug report #652842, regarding Depends on obsolete libgdata1.8-cil 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.) -- 652842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-do-plugins Version: 0.8.4-2 Severity: serious Your package depends on libgdata1.8-cil, which is no longer built on top of gdata-sharp. A no-change sourceful upload should be enough to pick the correct dependency. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: gnome-do-plugins Source-Version: 0.8.4-3 We believe that the bug you reported is fixed in the latest version of gnome-do-plugins, which is due to be installed in the Debian FTP archive: gnome-do-plugins_0.8.4-3.diff.gz to main/g/gnome-do-plugins/gnome-do-plugins_0.8.4-3.diff.gz gnome-do-plugins_0.8.4-3.dsc to main/g/gnome-do-plugins/gnome-do-plugins_0.8.4-3.dsc gnome-do-plugins_0.8.4-3_all.deb to main/g/gnome-do-plugins/gnome-do-plugins_0.8.4-3_all.deb 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 652...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iain Lane la...@debian.org (supplier of updated gnome-do-plugins 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Dec 2011 11:23:12 + Source: gnome-do-plugins Binary: gnome-do-plugins Architecture: source all Version: 0.8.4-3 Distribution: unstable Urgency: low Maintainer: Debian CLI Applications Team pkg-cli-apps-t...@lists.alioth.debian.org Changed-By: Iain Lane la...@debian.org Description: gnome-do-plugins - Extra functionality for GNOME Do Closes: 652842 Changes: gnome-do-plugins (0.8.4-3) unstable; urgency=low . * No-change rebuild for new gdata-sharp ABI (Closes: #652842) Checksums-Sha1: d023bf92390f39d2760fd18bdc249959a7d8 2709 gnome-do-plugins_0.8.4-3.dsc 3838e8723532511343b79a4489034361f9770fbd 11372 gnome-do-plugins_0.8.4-3.diff.gz 9dd3f63633c08bfc74a7f310a4f266caa6bb0068 2547594 gnome-do-plugins_0.8.4-3_all.deb Checksums-Sha256: e6745f574a1f6b10a2b134d48f19e4efd175f59be1c327fba04172b92328e18a 2709 gnome-do-plugins_0.8.4-3.dsc b206a74b6ee91908a95e1bcf395d3aa3cc6b61549bcfde2ec8fa31baf7ac0c81 11372 gnome-do-plugins_0.8.4-3.diff.gz 656d54778c4663882e7bf848a288c59aaa62426d18164994cda04fa90dece59a 2547594 gnome-do-plugins_0.8.4-3_all.deb Files: 5b2973fab4e8089ba4eeb4f4a6594006 2709 gnome optional gnome-do-plugins_0.8.4-3.dsc a2bc9d0a885b75b23835b797f7545566 11372 gnome optional gnome-do-plugins_0.8.4-3.diff.gz a6a7b968a3f802c9ffdb163c50b3aa25 2547594 gnome optional gnome-do-plugins_0.8.4-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJO9bhFAAoJEONS1cUcUEHUGc4QAIFiz0f4CY2sCT0+lisDkc2Z 5ewFBudOs4PSFDAuwGmNu1stCB3F0VWtp170l16m0N35HGSVwZgRTVWy51QzVpwU 2bPZf+y9d5ForTs+FaRW1MA9y0pFEFz78EQPVZahjXma7GyJ/4/xxcQMIEJaHqPX bFy2czj+OOLLTq+7bpA59MO9ToAoHsI7gHj0voIXaLb5YW9gkCtC/BMaRY8qG64w n66g0DmODx6tLYXH5uGGDSP7vWQadVgnmpmv1IbnGBs3fivLsLha/ZmxM8DJrL7Q ubIghn/bl1PhjQF+5UI8vfb8yLe8yZoEVo0vAxzMA514N5dPt0iCI4dbRUuI1MMf 5Ov6PGApusuMIBjL4DaAStk2wza03/CxKEw2nEdVhJEAluAjIGgRsNZJ1m0NEjK5 zbWZSsTK2eWgeNBA9jGwffd3I/oUUdS6yvQcreGS+U+vtlxo6dntcNoTwsMtYxQa xynr6tg1DzUllF+VK0/Y5sDDCgMQ3sl1Z2fw6Uu2mn6jMKm9WturObHw6s0/CsS1 1YgtHmyIi0+acV6LZqA3UQokLF/wnNbkmhEA7R8FzT8+C7v8EnUf4H8aH07tk5fp aRehku7tTbj2j42UmG0jDR2AGXfrYMrLrmg1UsWWDVxDr4vuKHgdbmRt9R9RHjMY LMjkQh+hk3MD6UpHHKaf =ezPb -END PGP SIGNATURE- ---End Message---
Processed: block 642639 with 642640
Processing commands for cont...@bugs.debian.org: block 642639 with 642640 Bug #642639 [src:libalog] libalog: FTBFS: unsatisfiable build-dependencies: gnat, libaws2.7-dev Was not blocked by any bugs. Added blocking bug(s) of 642639: 642640 thanks Stopping processing here. Please contact me if you need assistance. -- 642639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642639 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#652769: gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv
clone 652769 -1 reassign -1 python-opencv 2.3.1-1 retitle -1 python-opencv does not provide LoadHaarClassifierCascade any more block 652769 with -1 kthxbye On Tue, Dec 20, 2011 at 21:34:34 +0100, Samuel Thibault wrote: clone 652769 reassign 652769 python-opencv 2.3.1-1 retitle 652769 python-opencv does not provide LoadHaarClassifierCascade any more thanks Lucas Nussbaum, le Tue 20 Dec 2011 16:00:07 +0100, a écrit : During a rebuild of all packages in sid, your package failed to build on amd64. checking for python module opencv... no It seems the newer upstream of opencv has completely broken the python-opencv API, making gnome-mousetrap completely broken (not only build-, but also run-time). I've tried to patch it, but have come across an issue: LoadHaarClassifierCascade is not exported in the python-opencv API any more (even though it still exists in the C library)... Fixing the bts commands... Cheers, Julien -- 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#652769: gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv
Processing commands for cont...@bugs.debian.org: clone 652769 -1 Bug#652769: gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv Bug 652769 cloned as bug 653157. reassign -1 python-opencv 2.3.1-1 Bug #653157 [src:gnome-mousetrap] gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv Bug reassigned from package 'src:gnome-mousetrap' to 'python-opencv'. Bug No longer marked as found in versions gnome-mousetrap/0.4-2. Bug #653157 [python-opencv] gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv Bug Marked as found in versions opencv/2.3.1-1. retitle -1 python-opencv does not provide LoadHaarClassifierCascade any more Bug #653157 [python-opencv] gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv Changed Bug title to 'python-opencv does not provide LoadHaarClassifierCascade any more' from 'gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv' block 652769 with -1 Bug #652769 [src:gnome-mousetrap] gnome-mousetrap: FTBFS: configure: error: Could not find python module opencv Was not blocked by any bugs. Added blocking bug(s) of 652769: 653157 kthxbye Stopping processing here. Please contact me if you need assistance. -- 652769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652769 653157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653157 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 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#640319: jed: diff for NMU version 1:0.99.19-2.1
tags 640319 + pending thanks Dear maintainer, I've prepared an NMU for jed (versioned as 1:0.99.19-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key ID: 0x8649AA06 : :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of Free Software Foundation Europe `-NP: Sophie Hunger: Citylights Forever diff -u jed-0.99.19/debian/changelog jed-0.99.19/debian/changelog --- jed-0.99.19/debian/changelog +++ jed-0.99.19/debian/changelog @@ -1,3 +1,16 @@ +jed (1:0.99.19-2.1) unstable; urgency=low + + * Non-maintainer upload. + + [ peter green ] + * Make debian/rules pass in the include and library paths of the multi-arched +slang and make it strip the rpaths out of the built executables. Also add +appropriate build-dependencies (multiarch slang, dpkg-dev that supports +multiarch variables and chrpath). +(Closes: #640319) + + -- gregor herrmann gre...@debian.org Sat, 24 Dec 2011 14:22:36 +0100 + jed (1:0.99.19-2) unstable; urgency=low * Dropped install-info from the Depends field of jed and xjed. This diff -u jed-0.99.19/debian/rules jed-0.99.19/debian/rules --- jed-0.99.19/debian/rules +++ jed-0.99.19/debian/rules @@ -35,6 +35,12 @@ configure_flags += --disable-xft endif +DEB_HOST_MULTIARCH ?=$(shell dpgk-architecture -qDEB_HOST_MULTIARCH) + +#to successfully build with a multiarch slang we need to explicitly specify +#include and library directories. +configure_flags += --with-slanglib=/usr/lib/$(DEB_HOST_MULTIARCH) --with-slanginc=/usr/include + export DEB_BUILD_HARDENING=1 include /usr/share/dpatch/dpatch.make @@ -81,6 +87,10 @@ $(MAKE) -C src runtests endif + #unfortunately passing the multiarch dir for slang results in the + #upstream build system adding a rpath. Remove this with chrpath + chrpath -d src/objs/jed + chrpath -d src/objs/xjed touch build-stamp binary-indep: config.status diff -u jed-0.99.19/debian/control jed-0.99.19/debian/control --- jed-0.99.19/debian/control +++ jed-0.99.19/debian/control @@ -9,7 +9,7 @@ Build-Depends: debhelper (= 7), dpatch (= 2.0.30), libxft-dev, libgpm-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], libxt-dev, pkg-config, hardening-wrapper, autotools-dev, slsh, - libslang2-dev (= 2.0.7-2) + libslang2-dev (= 2.2.4-3), dpkg-dev (= 1.16.0), chrpath Homepage: http://www.jedsoft.org/jed/ Vcs-Git: git://git.debian.org/git/pkg-jed/jed.git Vcs-Browser: http://git.debian.org/?p=pkg-jed/jed.git signature.asc Description: Digital signature
Processed: jed: diff for NMU version 1:0.99.19-2.1
Processing commands for cont...@bugs.debian.org: tags 640319 + pending Bug #640319 [src:jed] jed: FTBFS: gcc-4.6.real: error: unrecognized option '-V' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 640319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640319 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#633856: Patch to fix Resource Not Found errors
Hi,
The attached patch fixes the Resource Not Found errors for me, which
makes gracie usable.
--
Matt Kraai
https://ftbfs.org/kraai
diff -ru gracie-0.2.11~/gracie/httprequest.py gracie-0.2.11/gracie/httprequest.py
--- gracie-0.2.11~/gracie/httprequest.py 2011-12-24 06:57:53.0 -0800
+++ gracie-0.2.11/gracie/httprequest.py 2011-12-24 06:58:12.0 -0800
@@ -37,12 +37,12 @@
mapper = routes.Mapper()
-mapper.connect('root', '', controller='about', action='view')
-mapper.connect('openid', 'openidserver', controller='openid')
-mapper.connect('identity', 'id/:name',
+mapper.connect('root', '/', controller='about', action='view')
+mapper.connect('openid', '/openidserver', controller='openid')
+mapper.connect('identity', '/id/:name',
controller='identity', action='view')
-mapper.connect('login', 'login', controller='login', action='view')
-mapper.connect('logout', 'logout', controller='logout', action='view')
+mapper.connect('login', '/login', controller='login', action='view')
+mapper.connect('logout', '/logout', controller='logout', action='view')
class HTTPRequestHandler(BaseHTTPRequestHandler):
Handler for individual HTTP requests
Bug#653168: Should this package be removed?
Source: oprofile Severity: serious oprofile seems like a candidate for removal: - Last maintainer upload in 2009 - No followup to security or RC bugs from the maintainers - Low popcon - Alternatives exist (perf) - Depends on legacy libs (604366) - Broken wih current kernels (615964) Unless there're objections/fixes, I'll file a removal bug in a month. Cheers, Moritz -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645963: closed by Martin Pitt mp...@debian.org (Re: Bug#640467: gnome-tweak-tool: Will not start due to undefined symbol: g_callable_info_skip_return)
On Mon, 21 Nov 2011 09:58:46 +0100 Vincent Lefevre wrote: On 2011-11-09 13:39:24 +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the python-gobject package: #640467: gnome-tweak-tool no start It has been closed by Martin Pitt mp...@debian.org. [...] Date: Wed, 9 Nov 2011 14:35:04 +0100 From: Martin Pitt mp...@debian.org To: Dean Loros debianmainu...@gmail.com, 640467-d...@bugs.debian.org Subject: Re: Bug#640467: gnome-tweak-tool: Will not start due to undefined symbol: g_callable_info_skip_return X-Spam-Status: No, score=-14.2 required=4.0 tests=BAYES_00,FROMDEVELOPER, HAS_BUG_NUMBER,PGPSIGNATURE,RDNS_NONE,VERSION autolearn=ham version=3.3.1-bugs.debian.org_2005_01_02 User-Agent: Mutt/1.5.21 (2010-09-15) Version: 1.30.0-1 This bug was marked as fixed in 1.30.0-1, but this is not a valid version for the python-gobject package, and apt-listbugs complains: grave bugs of python-gobject (2.28.6-5 - 3.0.2-3) marked as done in some version #640823 - Insufficient requirement on gobject-introspection (Fixed: 1.30.0-1) Merged with: 640467 644026 645963 Summary: python-gobject(1 bug) It seems that there was a confusion with the versions of gobject-introspection. Dear Martin, could you please clarify? Which is the package that should be upgraded in order to have this bug fixed? Which version should this package be upgraded to? By reading your message [1] to one of the merged bug reports, it seems that upgrading package gobject-introspection to version 1.30.0-1 (or later) is known to fix the bug. Do I understand correctly? Could you please confirm this? [1] http://bugs.debian.org/640467#62 Thanks for your time and your precious insight. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpe0abj5rzGA.pgp Description: PGP signature
Processed: severity of 639400 is serious
Processing commands for cont...@bugs.debian.org: severity 639400 serious Bug #639400 [src:network-manager-strongswan] Please update for network-manager 0.9 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 639400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639400 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#653107: Should this package be removed?
On Fri, 23 Dec 2011 23:40:20 +0100, Moritz Muehlenhoff j...@debian.org wrote: Package: util-vserver Severity: serious util-vserver hasn't seen an upload since 1.5 years and vserver support has been dropped from the Debian kernels post-Squeeze. Should util-vserver be removed as well? I'm not sure. Before the kernel team started providing vserver kernels, I was providing a kernel source patch set, which still require the user-space utilities to exist. I haven't decided if I will do that again, it depends on lxc maturing enough to be a usable alternative, which so far it has not and until it does, I'm not convinced that vservers should go away in debian. pgpIFbRGLaoDp.pgp Description: PGP signature
Bug#614610: echo mia crashes
On Friday 23 December 2011 21:05:05 Jonathan Nieder wrote: tags 614610 - moreinfo quit Hi again, Elimar Riesebieter wrote: * Ed Abbott [111211 13:12 -0500]: The Alsa Project has a package called alsa-firmware. This package made the error message that appeared on bootup go away. I'm referring to the missing firmware error message. In the end, though, the result is the same. My Echo Mia Midi Sound Card produces no sound in my speakers. [...] tags 614610 wontfix [...] Well, AFAIK Echo MI needs firmwrae licated ind the alsa-firmware package which is not distributed by Drbian yet. Looking over Ed's message, it seems that he said installing the firmware was not enough to get sound working. Did I miss something? A little puzzled, Jonathan Hi all, Sorry if I'm using the wrong protocol to answer this email. I'm using a reply all. I'm not used to reporting bugs so I don't know the right way to do it. I need to take some more time in the next few days and try again. I'm not sure that the alsa software and the firmware are properly matched in terms of version number. I may have confused the issue by using the most recent versions of alsa to try to get Echo Mia to work. Here's what I'll try when I get the opportunity: 1 -- uninstall everything from the alsa website that I've previously installed from source code packages. 2 -- Reinstall the current Debian Squeeze version of alsa 3 -- Reinstall the firmware from the alsa site. Two things I need to be careful of is to get the matching version number for the firmware and to use the correct version of the gcc compiler that goes with my kernel. Last time I worked on the Echo Mia problem, I was able to get the missing firmware message to go away when booting up. However, I did not get the Echo Mia card to actually work. My sound card is still silent when trying to play YouTube videos. I'll try to get all version numbers to match up perfectly before trying anything else. I don't do this sort of thing very often so I'm somewhat inexperienced. Ed . -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652888: marked as done (iceweasel: https support broken)
Your message dated Sat, 24 Dec 2011 17:29:42 + with message-id 20111224172942.ga15...@reptile.pseudorandom.co.uk and subject line Re: Bug#652888: bad dependencies in xulrunner-9.0 cause failed https has caused the Debian Bug report #652888, regarding iceweasel: https support broken 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.) -- 652888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: iceweasel Version: 9.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** I was trying to access github to see chnage ins packages and was unable to access any https page. Konqueror on the same machine and same url works as expected. Was working with 0.8. https://github.com/elupus/xbmc/commit/b10a1ea453e8603c62d60071e32fa073a159384b -- Package-specific info: -- Addons package information -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.5 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Versions of packages iceweasel depends on: ii debianutils 4.1 ii fontconfig 2.8.0-3 ii libc6 2.13-23 ii libgdk-pixbuf2.0-0 2.24.0-2 ii libglib2.0-02.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libnspr4-0d 4.8.9-1 ii libstdc++6 4.6.2-9 ii procps 1:3.3.1-1 ii xulrunner-9.0 9.0-1 iceweasel recommends no packages. Versions of packages iceweasel suggests: ii libgssapi-krb5-21.10+dfsg~alpha1-6 ii mathematica-fonts [ttf-mathematica4.1] 13 ii mozplugger none ii ttf-lyx 2.0.2-1 ii ttf-mathematica4.1 13 ii xfonts-mathml 4 Versions of packages xulrunner-9.0 depends on: ii libasound21.0.24.1-4 ii libatk1.0-0 2.2.0-2 ii libbz2-1.01.0.6-1 ii libc6 2.13-23 ii libcairo2 1.10.2-6.2 ii libdbus-1-3 1.5.8-1 ii libevent-2.0-52.0.16-stable-1 ii libfontconfig12.8.0-3 ii libfreetype6 2.4.8-1 ii libgcc1 1:4.6.2-9 ii libgdk-pixbuf2.0-02.24.0-2 ii libglib2.0-0 2.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8c-2 ii libmozjs9d9.0-1 ii libnotify40.7.4-1 ii libnspr4-0d 4.8.9-1 ii libnss3-1dnone ii libpango1.0-0 1.29.4-2 ii libpixman-1-0 0.24.0-1 ii libreadline6 6.2-8 ii libsqlite3-0 3.7.9-2 ii libstartup-notification0 0.12-1 ii libstdc++64.6.2-9 ii libvpx0 0.9.7.p1-2 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxrender1 1:0.9.6-2 ii libxt61:1.1.1-2 ii zlib1g1:1.2.5.dfsg-1 Versions of packages xulrunner-9.0 suggests: ii libcanberra0 0.28-3 ii libdbus-glib-1-2 0.98-1 ii libgnomeui-0 2.24.5-2 -- Configuration Files: /etc/iceweasel/iceweaselrc changed: ICEWEASEL_DSP=padsp /etc/iceweasel/profile/prefs.js changed: /* Do not edit this file. * * If you make changes to this file while the browser is running, * the changes will be overwritten when the browser exits. * * To make a manual change to preferences, you can visit the URL about:config * For more information, see http://www.mozilla.org/unix/customizing.html#prefs */ user_pref(browser.preferences.lastpanel, 0); user_pref(browser.search.selectedEngine, Google); user_pref(browser.startup.homepage, http://netrd.rd.francetelecom.fr;); user_pref(browser.startup.homepage_override.mstone, rv:1.7.10); user_pref(extensions.disabledObsolete, true); user_pref(extensions.lastAppVersion, 1.0); user_pref(extensions.update.lastUpdateDate, 1126090478); user_pref(intl.charsetmenu.browser.cache, ISO-8859-1, UTF-8); user_pref(network.cookie.prefsMigrated, true); user_pref(network.negotiate-auth.trusted-uris, https://,francetelecom.fr,itn.ftgroup;); user_pref(network.proxy.autoconfig_url, http://proxyconf.rd.francetelecom.fr/;); user_pref(network.proxy.type, 2);
Bug#653178: coreutils: /bin/cat does not work on my nas after upgrading today (segfaults)
Package: coreutils Version: 8.13-3 Severity: critical Justification: breaks unrelated software /bin/cat whatever just segfaults breaking several init scripts (like hostname.sh) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: armel (armv5tel) Kernel: Linux 3.1.0-1-orion5x 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 coreutils depends on: ii dpkg 1.16.1.2 ii install-info 4.13a.dfsg.1-8 ii libacl1 2.2.51-5 ii libattr1 1:2.4.46-5 ii libc6 2.13-23 ii libgcc1 1:4.6.2-9 ii libselinux1 2.1.0-4 coreutils recommends no packages. coreutils suggests no packages. -- 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#653178: Reinstalling hit resolves the pb = problem is probably more a box problem
You can close it. Will fsck the NAS. will take quite some time. --eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653178: Well, its reappears. cat /proc/cmdline always segfault
The fsck found nothing -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614610: echo mia crashes
Hi Ed, Ed Abbott wrote: I need to take some more time in the next few days and try again. I'm not sure that the alsa software and the firmware are properly matched in terms of version number. Honestly I don't suspect that is needed. What would be useful is - for someone to summarize the current status of packaging ALSA firmware and what remains to be done in that direction - for someone to test the latest ALSA driver and let us know how it behaves. Please consider using the checkinstall program if using the upstream sources directly without packaging. - if a newer version of the ALSA kernelspace or userspace driver fixes this, for someone to package it for Debian. Sorry for the trouble, and hope that helps. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653168: Should this package be removed?
On Sat, Dec 24, 2011 at 04:56:55PM +0100, Moritz Muehlenhoff wrote: Source: oprofile Severity: serious oprofile seems like a candidate for removal: - Last maintainer upload in 2009 - No followup to security or RC bugs from the maintainers - Low popcon - Alternatives exist (perf) - Depends on legacy libs (604366) - Broken wih current kernels (615964) Unless there're objections/fixes, I'll file a removal bug in a month. Moritz, I have no objection. I become co-maintainer of oprofile a little over two years ago because one of my clients was using it and needed some work done on the package. The maintainer was not especially responsive at that time, so I did what needed to be done. However, my client has since moved away from using oprofile and when I asked to be removed as co-maintainer I heard nothing at all. Based on that, I think that the maintainer is probably MIA, and removal seems like the right thing. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#650961: libsqlite3-tcl: pkgIndex.tcl is empty and can not be generated
Any news? -- Alexander Galanin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652164: FTBFS: ../../src/rakarrack.cxx:22892:37: error: format not a string literal and no format arguments [-Werror=format-security]
Package: rakarrack
Version: 0.6.1-3
Followup-For: Bug #652164
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu precise ubuntu-patch
In Ubuntu Precise, the following patch was applied to resolve the FTBFS.
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers oneiric-updates
APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500,
'oneiric-proposed'), (500, 'oneiric')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-14-generic (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
*** format-security.debdiff.diff.2
diff -u rakarrack-0.6.1/debian/patches/series
rakarrack-0.6.1/debian/patches/series
--- rakarrack-0.6.1/debian/patches/series
+++ rakarrack-0.6.1/debian/patches/series
@@ -1,0 +2 @@
+format-security.diff
only in patch2:
unchanged:
--- rakarrack-0.6.1.orig/debian/patches/format-security.diff
+++ rakarrack-0.6.1/debian/patches/format-security.diff
@@ -0,0 +1,71 @@
+Index: rakarrack-0.6.1/src/rakarrack.cxx
+===
+--- rakarrack-0.6.1.orig/src/rakarrack.cxx 2011-12-24 15:31:22.0
-0500
rakarrack-0.6.1/src/rakarrack.cxx 2011-12-24 15:31:24.0 -0500
+@@ -22889,7 +22889,7 @@
+ Fl_Widget *m = fl_message_icon();
+ m-parent()-copy_label(rkr-jackcliname);
+ sprintf(temp2,Overwrite? \%s\,w-label());
+- ok=fl_choice(temp2,No,Yes,NULL);
++ ok=fl_choice(%s,temp2,No,Yes,NULL);
+ if (!ok)
+ {
+ o-value(0);
+@@ -24142,7 +24142,7 @@
+ w-parent()-copy_label(rkr-jackcliname);
+
+
+- ok=fl_choice(Bank was modified, but not saved,Discard,Save,NULL);
++ ok=fl_choice(%s,Bank was modified, but not saved,Discard,Save,NULL);
+
+
+
+@@ -27243,7 +27243,7 @@
+ }
+
+ sprintf(temp2,Delete? \%s\,s-text());
+-ok=fl_choice(temp2,No,Yes,NULL);
++ok=fl_choice(%s,temp2,No,Yes,NULL);
+ if (!ok) return;
+ memset(Rname,0,sizeof(Rname));
+ sprintf(Rname,%s,s-text());
+Index: rakarrack-0.6.1/src/fileio.C
+===
+--- rakarrack-0.6.1.orig/src/fileio.C 2011-12-24 15:31:22.0 -0500
rakarrack-0.6.1/src/fileio.C 2011-12-24 15:31:24.0 -0500
+@@ -1641,7 +1641,7 @@
+
+case 3:
+ memset (temp, 0, sizeof (temp));
+-sprintf (temp, BankFilename);
++sprintf (temp, %s, BankFilename);
+ break;
+
+}
+@@ -2786,4 +2786,4 @@
+
+ }
+
+-
+\ No newline at end of file
++
+Index: rakarrack-0.6.1/src/varios.C
+===
+--- rakarrack-0.6.1.orig/src/varios.C 2011-12-24 16:36:58.0 -0500
rakarrack-0.6.1/src/varios.C 2011-12-24 16:37:49.0 -0500
+@@ -41,7 +41,7 @@
+ w-image (a);
+ w-align (FL_ALIGN_TOP | FL_ALIGN_INSIDE);
+ w-parent ()-copy_label (labelwin);
+- fl_message (message_text);
++ fl_message (%s, message_text);
+ return (0);
+
+ };
+@@ -399,4 +399,4 @@
+
+
+
+-
+\ No newline at end of file
++
-- System Information:
Debian Release: wheezy/sid
APT prefers oneiric-updates
APT policy: (900, 'oneiric-updates'), (800, 'oneiric'), (10, 'precise')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-14-generic (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
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: rakarrack: FTBFS: ../../src/rakarrack.cxx:22892:37: error: format not a string literal and no format arguments [-Werror=format-security]
Processing commands for cont...@bugs.debian.org: tags 652164 + patch Bug #652164 [src:rakarrack] rakarrack: FTBFS: ../../src/rakarrack.cxx:22892:37: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 652164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652164 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#649703: marked as done (Please Build-Depend on ghostscript, not gs-common.)
Your message dated Sat, 24 Dec 2011 22:04:40 + with message-id e1rezho-0005gg...@franck.debian.org and subject line Bug#649703: fixed in fpc 2.4.4-3.1 has caused the Debian Bug report #649703, regarding Please Build-Depend on ghostscript, not gs-common. 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.) -- 649703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fpc Version: 2.4.4-3 Severity: important Hi, fpc currently Build-Depends on gs-common, which is a transitional package. The next upload of ghostscript (currently) plans to drop both gs-common and the ghostscript Provides: gs-common. As soon as that upload happens, it will make fpc FTBFS. Please replace the Build-Depends on gs-common to a Build-Depends on ghostscript. (The severity of this bug will be raised after the ghostscript upload.) Cheers, OdyX ---End Message--- ---BeginMessage--- Source: fpc Source-Version: 2.4.4-3.1 We believe that the bug you reported is fixed in the latest version of fpc, which is due to be installed in the Debian FTP archive: fp-compiler-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-compiler-2.4.4_2.4.4-3.1_i386.deb fp-compiler_2.4.4-3.1_i386.deb to main/f/fpc/fp-compiler_2.4.4-3.1_i386.deb fp-docs-2.4.4_2.4.4-3.1_all.deb to main/f/fpc/fp-docs-2.4.4_2.4.4-3.1_all.deb fp-docs_2.4.4-3.1_all.deb to main/f/fpc/fp-docs_2.4.4-3.1_all.deb fp-ide-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-ide-2.4.4_2.4.4-3.1_i386.deb fp-ide_2.4.4-3.1_i386.deb to main/f/fpc/fp-ide_2.4.4-3.1_i386.deb fp-units-base-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-base-2.4.4_2.4.4-3.1_i386.deb fp-units-base_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-base_2.4.4-3.1_i386.deb fp-units-db-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-db-2.4.4_2.4.4-3.1_i386.deb fp-units-db_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-db_2.4.4-3.1_i386.deb fp-units-fcl-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-fcl-2.4.4_2.4.4-3.1_i386.deb fp-units-fcl_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-fcl_2.4.4-3.1_i386.deb fp-units-fv-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-fv-2.4.4_2.4.4-3.1_i386.deb fp-units-fv_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-fv_2.4.4-3.1_i386.deb fp-units-gfx-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gfx-2.4.4_2.4.4-3.1_i386.deb fp-units-gfx_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gfx_2.4.4-3.1_i386.deb fp-units-gnome1-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gnome1-2.4.4_2.4.4-3.1_i386.deb fp-units-gnome1_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gnome1_2.4.4-3.1_i386.deb fp-units-gtk-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gtk-2.4.4_2.4.4-3.1_i386.deb fp-units-gtk2-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gtk2-2.4.4_2.4.4-3.1_i386.deb fp-units-gtk2_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gtk2_2.4.4-3.1_i386.deb fp-units-gtk_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-gtk_2.4.4-3.1_i386.deb fp-units-i386-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-i386-2.4.4_2.4.4-3.1_i386.deb fp-units-i386_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-i386_2.4.4-3.1_i386.deb fp-units-math-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-math-2.4.4_2.4.4-3.1_i386.deb fp-units-math_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-math_2.4.4-3.1_i386.deb fp-units-misc-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-misc-2.4.4_2.4.4-3.1_i386.deb fp-units-misc_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-misc_2.4.4-3.1_i386.deb fp-units-multimedia-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-multimedia-2.4.4_2.4.4-3.1_i386.deb fp-units-multimedia_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-multimedia_2.4.4-3.1_i386.deb fp-units-net-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-net-2.4.4_2.4.4-3.1_i386.deb fp-units-net_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-net_2.4.4-3.1_i386.deb fp-units-rtl-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-rtl-2.4.4_2.4.4-3.1_i386.deb fp-units-rtl_2.4.4-3.1_i386.deb to main/f/fpc/fp-units-rtl_2.4.4-3.1_i386.deb fp-utils-2.4.4_2.4.4-3.1_i386.deb to main/f/fpc/fp-utils-2.4.4_2.4.4-3.1_i386.deb fp-utils_2.4.4-3.1_i386.deb to main/f/fpc/fp-utils_2.4.4-3.1_i386.deb fpc-2.4.4_2.4.4-3.1_all.deb to main/f/fpc/fpc-2.4.4_2.4.4-3.1_all.deb fpc-source-2.4.4_2.4.4-3.1_all.deb to main/f/fpc/fpc-source-2.4.4_2.4.4-3.1_all.deb fpc-source_2.4.4-3.1_all.deb to main/f/fpc/fpc-source_2.4.4-3.1_all.deb fpc_2.4.4-3.1.debian.tar.gz to main/f/fpc/fpc_2.4.4-3.1.debian.tar.gz fpc_2.4.4-3.1.dsc to main/f/fpc/fpc_2.4.4-3.1.dsc fpc_2.4.4-3.1_all.deb to
Bug#653192: linux 3.2~rc4-1~experimental.1: Intel X-25M SSD destroyed
Package: src:linux-2.6 Version: 3.2~rc4-1~experimental.1 Severity: critical Justification: causes serious data loss Hi, My system has run Debian 2.6.32 kernels for 21 months, with two RAID-1s spanning a pair of Intel X-25M 80GiB SSDs; one RAID (sd[ab]1) is for a /boot filesystem, and another (sd[ab]2) contains an encrypted LVM with everything else, all reiserfs filesystems. There was also an unformatted partition sda3 and an ntfs partition sdb3. Today I tried booting 3.2~rc4-1~experimental.1, which seemed fine until after a few minutes various programs in a graphical desktop environment started to hang, apparently when trying to load anything from disk that was not already in cache. Ctrl+Alt+F1-6 wasn't working. After a SysRq-S,U,B forced reboot, one of my SSDs (sdb) now seems to be toast. I'm only able to read the first 16KiB of data from it, which still contains the original intact partition table and embedded GRUB. The rest is neither readable nor writable, with these errors: [ 749.427493] end_request: I/O error, dev sdb, sector 32 [ 749.427501] __ratelimit: 2619 callbacks suppressed [ 749.427508] Buffer I/O error on device sdb, logical block 4 [ 757.362967] sd 4:0:0:0: [sdb] Unhandled error code [ 757.362979] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK printk is flooded on startup with many other errors that I'm unable to retrieve from dmesg, for about 5 minutes until the system eventually boots 2.6.32 from the degraded RAID using the other apparently intact SSD. Other errors I noticed include: * sector reallocation failures * nv SATA controller resetting the port I don't imagine my bug report is of much help fixing the issue, but I at least wanted to warn anyone before trying it. I don't exactly have a shelf full of spare ~£120 SSDs for further testing/debugging. In the meantime I'll see if I can somehow fix the 'broken' SSD. I would have suspected that this was an underlying drive firmware bug, triggered by linux-3.2 or 3.0 implementing the SSD TRIM/discard feature, but actually I don't think that feature is enabled in the 02G9 firmware of these drives, and also I doubt reiserfs would make use of those features, especially on top of encrypted LVM. I'd previously tested 3.0 kernels from unstable but given up on them due to similar hangs on disk reads, possibly related to reiserfs. I didn't suffer any loss of data or destruction of hardware until now though. I'd rebuilt 3.2.0-rc4-rt-amd64 with the custom DSDT I normally use on 2.6.32 to enable powernow-k8, and since this is an RT-patched kernel flavour I'd exported some GPL-only symbols to be able to build the nvidia module with DKMS. Kernel log leading up to the crash: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-rc4-rt-amd64 (Debian 3.2~rc4-1~experimental.1+dsdt1) (ste...@pyro.eu.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP PREEMPT RT Sat Dec 24 18:42:30 GMT 2011 [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.2.0-rc4-rt-amd64 root=/dev/mapper/acidbath-root ro single clocksource=acpi_pm iommu=memaper=1 threadirqs [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009d400 (usable) [0.00] BIOS-e820: 0009d400 - 000a (reserved) [0.00] BIOS-e820: 000e8000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 7fff9300 (usable) [0.00] BIOS-e820: 7fff9300 - 8000 (reserved) [0.00] BIOS-e820: fec0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00018000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.3 present. [0.00] No AGP bridge found [0.00] last_pfn = 0x18 max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] last_pfn = 0x7fff9 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [880f9bf0] f9bf0 [0.00] init_memory_mapping: -7fff9000 [0.00] init_memory_mapping: 0001-00018000 [0.00] RAMDISK: 37431000 - 37ff [0.00] ACPI: RSDP 000e8010 00024 (v02 HP) [0.00] ACPI: XSDT 7fff94fc 0003C (v01 HP CPQ0062 20061128 ) [0.00] ACPI: FACP 7fff96a4 0010C (v03 HP VIPER 0001 ) [0.00] ACPI Warning: FADT (revision 3) is longer than ACPI 2.0 version, truncating length 268 to 244 (20110623/tbfadt-288) [0.00] ACPI: Override [DSDT-DSDT], this is unsafe: tainting kernel [0.00] Disabling lock debugging due to kernel taint [0.00] ACPI: DSDT @ 0x7fff989a Table override, replaced with: [0.00] ACPI: DSDT 8164c890 04BF8 (v01 HP DSDT 0001 INTL 20100528) [
Bug#653194: cryptsetup: cryptroot hook for update-initramfs silently ignores the key file listed in crypttab
Package: cryptsetup Version: 2:1.1.3-4squeeze2 Severity: critical Justification: breaks the whole system When update-initramfs is run, an initrd is built including my keyscript, but *not* my key file. This rendered the system unbootable without warning. I was able to recover from a rescue cd by unpacking the initrd, adding my key file, and repacking the initrd - everything then worked as expected. This should be trivially reproduceable by using `cat` as a keyscript with a key file. -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/sda5_crypt ro quiet -- /etc/crypttab sda5_crypt UUID=179b33c0-bb72-4ad3-ad32-ec7fe4521404 /boot/key.tcy luks,keyscript=/usr/local/bin/threshcrypt_static -- /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/sda5_crypt / ext3errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=6d60dcfa-6afd-4d3f-a8e9-9fc8f31ce93b /boot ext3defaults 0 2 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 -- lsmod Module Size Used by loop 11799 0 snd_ens137116938 0 gameport7416 1 snd_ens1371 snd_rawmidi15515 1 snd_ens1371 snd_seq_device 4493 1 snd_rawmidi snd_ac97_codec 99186 1 snd_ens1371 ac97_bus1086 1 snd_ac97_codec snd_pcm60487 2 snd_ens1371,snd_ac97_codec snd_timer 15598 1 snd_pcm snd46526 6 snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer parport_pc 18855 0 soundcore 4598 1 snd joydev 8459 0 parport27954 1 parport_pc snd_page_alloc 6249 1 snd_pcm i2c_piix4 8328 0 evdev 7352 2 pcspkr 1699 0 container 2389 0 psmouse49937 0 processor 29935 0 ac 2192 0 shpchp 26264 0 serio_raw 3752 0 button 4650 0 i2c_core 15819 1 i2c_piix4 pci_hotplug21587 1 shpchp ext3 106710 2 jbd37221 1 ext3 mbcache 5050 1 ext3 sha256_generic 8692 2 aes_x86_64 7340 2 aes_generic25714 1 aes_x86_64 cbc 2539 1 usbhid 33292 0 hid63257 1 usbhid dm_crypt 10664 1 dm_mod 53898 3 dm_crypt sg 24069 0 sd_mod 29921 3 crc_t10dif 1276 1 sd_mod sr_mod 12602 0 cdrom 29415 1 sr_mod uhci_hcd 18521 0 ata_generic 3239 0 mptspi 11185 2 mptscsih 16360 1 mptspi mptbase48382 2 mptspi,mptscsih scsi_transport_spi 18774 1 mptspi ata_piix 21124 0 ehci_hcd 32081 0 libata133776 2 ata_generic,ata_piix floppy 49087 0 e1000 85517 0 usbcore 122674 4 usbhid,uhci_hcd,ehci_hcd nls_base6377 1 usbcore scsi_mod 126533 7 sg,sd_mod,sr_mod,mptspi,mptscsih,scsi_transport_spi,libata thermal11674 0 thermal_sys11942 2 processor,thermal -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) 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 cryptsetup depends on: ii dmsetup 2:1.02.48-5 The Linux Kernel Device Mapper use ii libc62.11.2-10 Embedded GNU C Library: Shared lib ii libdevmapper1.02.1 2:1.02.48-5 The Linux Kernel Device Mapper use ii libpopt0 1.16-1 lib for parsing cmdline parameters ii libuuid1 2.17.2-9Universally Unique ID library cryptsetup recommends no packages. Versions of packages cryptsetup suggests: ii busybox 1:1.17.1-8 Tiny utilities for small and embed pn dosfstoolsnone (no description available) ii initramfs-tools [linux-initra 0.98.8 tools for generating an initramfs ii udev 164-3 /dev/ and hotplug
Bug#638339: blur on linux =2.6.39 - was: Re: [Checkpoint] Announcing the release of BLCR 0.8.4
Hi Alan, We are aware of 2 non-trivial issues in 2.6.39 That seems to match what I've seen too, as these issues are the only big things I've encountered so far and I have a building, semi-working module. I had some trouble with it reporting unmatched System.map between running kernel and compiled module which I'm reasonably sure is a false positive although I've not tracked it down. + removal of the BKL I worked around this with a B BLCR L. It's too early though to say if that's sufficient given I currently can't pass all the testsuite. Would you mind sharing your current patch for testing? If it already helps getting the blcr kernel module build on = 2.6.39, I'd be very glad to try it out myself and provide feedback as well. We've got a larger cluster running here and want to use blcr there with more recent kernels. Regards, Adrian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 639871 with 653131
Processing commands for cont...@bugs.debian.org: block 639871 with 653131 Bug #639871 [release.debian.org] transition: gssdp/gupnp Was blocked by: 652783 593023 Added blocking bug(s) of 639871: 653131 thanks Stopping processing here. Please contact me if you need assistance. -- 639871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639871 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#644297: Package is installable on amd64
tag 644297 + unreproducible thanks Hi, I built the package tonight with pbuilder and could install it with pbuilder --login. Cheers, Martin $ uname -a Linux malioth 2.6.32-5-amd64 #1 SMP Thu Nov 3 03:41:26 UTC 2011 x86_64 GNU/Linux $ dpkg --info pysieved_1.1-0.1_all.deb new debian package, version 2.0. size 21294 bytes: control archive= 1696 bytes. 57 bytes, 2 lines conffiles 638 bytes,16 lines control 1519 bytes,22 lines md5sums 599 bytes,29 lines * postinst #!/bin/sh 514 bytes,29 lines * prerm#!/bin/sh Package: pysieved Version: 1.1-0.1 Architecture: all Maintainer: Christoph Haas h...@debian.org Installed-Size: 133 Depends: python ( 2.8), python (= 2.7), python-support (= 0.90.0), update-inetd, openbsd-inetd Recommends: python-tlslite Suggests: python-mysqldb, python-pam Section: mail Priority: extra Homepage: http://www.gitorious.net/pysieved/pages/Home Description: managesieve server pysieved is a Python-based managesieve server. It uses a plug-in architecture to support different authentication (Dovecot, PAM, SASL, MySQL), homedir lookup (Dovecot, /etc/passwd, MySQL, simple virtual hosting), and storage back-ends. $ dpkg -l pysieved Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++--- ii pysieved 1.1-0.1 managesieve server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Package is installable on amd64
Processing commands for cont...@bugs.debian.org: tag 644297 + unreproducible Bug #644297 [pysieved] pysieved: uninstallable: Depends: python ( 2.7) but 2.7.2-7 is to be installed Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 644297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644297 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#653194: Acknowledgement (cryptsetup: cryptroot hook for update-initramfs silently ignores the key file listed in crypttab)
Here's a patch that fixes the problem, but I think further discussion on how to handle this in a way that is safe/correct is needed. Since there's no *requirement* that the key file used with a keyscript is an actual file, it's hard to know for sure whether the intent is to use a file or just give and argument to the keyscript. My solution assumes that anything with a leading / is a file, but this will give spurious warnings if someone sets something like /dev/ttyS0 or /dev/sdXX as the key file. It also might be best if some attempt was made not to copy a file from an encrypted filesystem to an unencrypted initramfs image. -Ryan --- cryptroot.dist 2011-12-24 16:50:11.0 -0800 +++ cryptroot 2011-12-24 17:07:33.0 -0800 @@ -211,7 +211,7 @@ fi # We have all the basic options, let's go trough them - OPTIONS=target=$target,source=$source,key=$key + OPTIONS=target=$target,source=$source local IFS=, unset HASH_FOUND unset LUKS_FOUND @@ -262,10 +262,23 @@ echo the correct hash option to your /etc/crypttab. 2 fi - # If keyscript is set, the key is just an argument to the script - if [ $key != none ] [ -z $KEYSCRIPT ]; then - echo cryptsetup: WARNING: target $target uses a key file, skipped 2 - return 1 + # A key is only supported if it is being used with a keyscript + if [ $key != none ]; then + if [ -n $KEYSCRIPT ]; then + # Include the key if it is a regular file + if [ -f $key ]; then +KEYFILE=$key +key=/lib/cryptsetup/keys/$(basename $key) + elif [ $(echo $key | cut -c 1) = / ]; then +# Not sure if this should be fatal +echo cryptsetup: WARNING: key file $key for target $target cannot be copied 2 + fi + OPTIONS=$OPTIONS,key=$key + else + OPTIONS=$OPTIONS,key=$key + echo cryptsetup: WARNING: target $target uses a key file, skipped 2 + return 1 + fi fi } @@ -408,6 +421,12 @@ echo cryptsetup: WARNING: failed to find keyscript $KEYSCRIPT 2 continue fi + if [ -n $KEYFILE ]; then +if [ ! -d $DESTDIR/lib/cryptsetup/keys ]; then + mkdir -p $DESTDIR/lib/cryptsetup/keys +fi +cp $KEYFILE $DESTDIR/lib/cryptsetup/keys + fi fi # Calculate needed modules
Bug#644297: Package is installable on amd64
tag 644297 - unreproducible thanks I was to quick. Actually the downloaded package is *not* installable as reported initially, but recompiling it hopefully does the trick. Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Package is installable on amd64
Processing commands for cont...@bugs.debian.org: tag 644297 - unreproducible Bug #644297 [pysieved] pysieved: uninstallable: Depends: python ( 2.7) but 2.7.2-7 is to be installed Removed tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 644297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644297 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#650961: libsqlite3-tcl: pkgIndex.tcl is empty and can not be generated
On Sun, 2011-12-04 at 19:51 +0300, Alexander Galanin wrote: File /usr/lib/tcltk/sqlite3/pkgIndex.tcl is empty, so package sqlite3 can not be loaded in Tcl programs. Indeed. On all platforms, it doesn't contain the package ifneeded ... line. A simple rebuild fixes this issue. I've asked the release team for a binary NMU, but they are on hold at the moment. I'm not home ATM and will arrive back on 30th only. Will ask them for a binNMU again. Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653204: FTBFS: regex-posix -any dependency missing
Package: ghc-mod Version: 1.0.4-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu precise ubuntu-patch *** /tmp/tmpZB0472/bug_body In Ubuntu, the attached patch was applied to achieve the following: * Add build dependency on libghc-regex-posix-dev, fixes FTBFS - update debian/control Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric-proposed'), (500, 'oneiric'), (100, 'oneiric-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-13-generic (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 diff -u ghc-mod-1.0.4/debian/control ghc-mod-1.0.4/debian/control --- ghc-mod-1.0.4/debian/control +++ ghc-mod-1.0.4/debian/control @@ -13,6 +13,7 @@ libghc-ghc-paths-dev, libghc-hlint-dev (= 1.7.1), libghc-transformers-dev, + libghc-regex-posix-dev, libghc-filemanip-dev Standards-Version: 3.9.2 Homepage: http://www.mew.org/~kazu/proj/ghc-mod/ diff -u ghc-mod-1.0.4/debian/changelog ghc-mod-1.0.4/debian/changelog
Bug#653125: Farsi characters problem
severity 653125 normal thanks Quoting Sasan Rose (sasan.r...@gmail.com): Package: debian-i18n Severity: grave Tags: l10n Justification: renders package unusable In this case, no package is even mentioned, so no reason to use an RC severity. Dear Maintainer, Farsi layout is working system wide without any problem, but using terminal or vim or gvim, farsi characters are just bunch of question marks. I tried to change terminal profile's font but no success. Even no success with BiCON. I reconfigured locale package and even tried to set some env. You should mention which terminal, in what graphical environment, with which font(s). Does the problem also happen with other RTL languages such as Arabic or Hebrew (yeah, I understand you might not be able to read those, but I see no other way to narrow down the problem). I suspect this to be related to the terminal program you're using. signature.asc Description: Digital signature
Processed: Re: Bug#653125: Farsi characters problem
Processing commands for cont...@bugs.debian.org: severity 653125 normal Bug #653125 [debian-i18n] Farsi characters problem Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 653125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653125 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
