Bug#710752: pxe-pdhcp: eats 100% of CPU
Package: pxe-pdhcp Version: 0.1-1 Severity: serious After uploading this package, I realize this is eating 100% of CPU. Just because single thread and I am using multicore system, it is usable but it waistes CPU. As I see the all the use records on the web, people are mostly running this when the need this. So maybe it was OK. But to be Debian package, this daemon needs to be updated by using poll(2). I guess adding PID file support was not good enough to be good Debian package. Sigh... my fault. Also, just like tftp-hpa bug, this is not started by sysv init. Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710718: marked as done (python-heatclient: Fails to build from source: depends on python-argparse)
Your message dated Sun, 02 Jun 2013 06:17:56 + with message-id e1uj1c4-00033w...@franck.debian.org and subject line Bug#710718: fixed in python-heatclient 0.2.2-3 has caused the Debian Bug report #710718, regarding python-heatclient: Fails to build from source: depends on python-argparse 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.) -- 710718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-heatclient Version: 0.2.2-2 Severity: serious Justification: fails to build from source User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy python-heatclient 0.2.2-2 fails to build from source in a clean chroot since it depends on python-argparse which no longer exists in either unstable or testing. http://packages.qa.debian.org/a/argparse/news/20130521T072110Z.html says that apparently that functionality is built into python 2.7. Thanks, Jeremy - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'raring'), (100, 'saucy-backports') ---End Message--- ---BeginMessage--- Source: python-heatclient Source-Version: 0.2.2-3 We believe that the bug you reported is fixed in the latest version of python-heatclient, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Prach Pongpanich prach...@gmail.com (supplier of updated python-heatclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 07:01:12 +0700 Source: python-heatclient Binary: python-heatclient Architecture: source all Version: 0.2.2-3 Distribution: unstable Urgency: low Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Prach Pongpanich prach...@gmail.com Description: python-heatclient - client library and CLI for OpenStack Heat Closes: 710718 Changes: python-heatclient (0.2.2-3) unstable; urgency=low . [ Prach Pongpanich ] * Drop dependency on python-argparse (Closes: #710718) . [ Thomas Goirand ] * Make the drop of the python-argparse conditional (eg: it don't drop the dependency if building in Wheezy). * Allow the unit tests to fail if running in Wheezy (because of the lack of the python-argparse build-depends). Checksums-Sha1: bef771b086c4c52b66fac8e694cce7d212d4fbe6 1748 python-heatclient_0.2.2-3.dsc 0e7e5899b9a6f7d0cedbe29131f1e81c4a6114d8 9736 python-heatclient_0.2.2-3.debian.tar.gz 32173e76f8f2391ab06aaeecad31a157d1fc6211 29146 python-heatclient_0.2.2-3_all.deb Checksums-Sha256: f9eb38e6fe39ffadf6b287520180b4a39ca9d64c295dce1dac12c4d4ee299415 1748 python-heatclient_0.2.2-3.dsc f17af5169c84783b97785cab23054afcd334a5bff31d3f8caa3ebbc4f87f5435 9736 python-heatclient_0.2.2-3.debian.tar.gz e486c9b2a8ecef7681faccb156eb570453575dc83fff5ba4d7b4a49e18ebf758 29146 python-heatclient_0.2.2-3_all.deb Files: 16393ea74559882c44722b67e75d4b0e 1748 python optional python-heatclient_0.2.2-3.dsc d2ab30b82ba962c8045bee981409a60d 9736 python optional python-heatclient_0.2.2-3.debian.tar.gz b6deba6bc13229ec10963c4ffc9257f9 29146 python optional python-heatclient_0.2.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGq4/IACgkQl4M9yZjvmkk5awCg2yECw1EX9rqfHuziJeP7nhKz OCwAnixwhsBhm+qHe61QJ0pHxBGYZFzP =OreK -END PGP SIGNATUREEnd Message---
Processed: Re: Bug#710728: cacti-spine: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/cacti-spine/spine.conf.dbconfig
Processing control commands: tag -1 confirmed Bug #710728 [cacti-spine] cacti-spine: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/cacti-spine/spine.conf.dbconfig Added tag(s) confirmed. -- 710728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710728 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#710728: cacti-spine: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/cacti-spine/spine.conf.dbconfig
Control: tag -1 confirmed This very same bug was indeed also in cacti, where I fixed it in one of the latest uploads. We should apply the same logic in cacti-spine as well. Paul signature.asc Description: OpenPGP digital signature
Bug#710757: tortoisehg: not installable in sid
Package: tortoisehg Version: 2.4-2 Severity: serious Affects: tortoisehg-nautilus User: trei...@debian.org Usertags: edos-outdated Hi, tortoisehg is not installable in sid since it depends on mercurial (= 2.1~), mercurial ( 2.3~) However, the version of mercurial available in sid is 2.6.1-1. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710759: tdiary-contrib: not installable in sid
Package: tdiary-contrib Version: 3.1.20120506-3 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, tdiary-contrib is not installable in sid since it depends on tdiary (= 3.1), tdiary ( 3.2) However, the version of tdiary available in sid is 3.2.2-2. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710761: monodevelop-debugger-gdb: not installable in sid
Package: monodevelop-debugger-gdb Version: 3.0.3.2-1 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, monodevelop-debugger-gdb is not installable in sid since it depends on monodevelop (= 3.0.3.2), monodevelop ( 3.0.3.2.) However, the version of monodevelop available in sid is 4.0.5+dfsg-1. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710760: monodevelop-monogame: not installable in sid
Package: monodevelop-monogame Version: 2.5.1+dfsg-3 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, monodevelop-monogame is not installable in sid since it depends on monodevelop (= 3.0.3.2), monodevelop ( 3.0.3.2.), However, the version of monodevelop available in sid is 4.0.5+dfsg-1. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710763: monodevelop-database: not installable in sid
Package: monodevelop-database Version: 3.0.3.2+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, monodevelop-database is not installable in sid since it depends on monodevelop (= 3.0.3.2), monodevelop ( 3.0.3.2.) However, the version of monodevelop available in sid is 4.0.5+dfsg-1 -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710622: comedilib: FTBFS: ./calib_yacc.h:119:5: error: conflicting types for 'calib_yyparse'
Control: tags -1 + upstream On Fri, May 31, 2013 at 06:56:00PM +0200, David Suárez wrote: In file included from calib_lex.l:32:0: ./calib_yacc.h:119:5: error: conflicting types for 'calib_yyparse' In file included from calib_lex.l:31:0: libinternal.h:150:5: note: previous declaration of 'calib_yyparse' was here bison 2.6 declares yyparse in the generated header. -- WBR, wRAR signature.asc Description: Digital signature
Bug#710607: ruby-gnome2: FTBFS: glib-enum-types.c:499:10: error: expected expression before ',' token
Control: tags -1 + upstream fixed-upstream
On Sat, Jun 01, 2013 at 12:31:36AM +0200, David Suárez wrote:
glib-enum-types.c:499:10: error: expected expression before ',' token
The code:
static const GEnumValue values[] = {
{ {, {, { },
Looks like it's caused by the /* flags */ comment on GIOCondition in
/usr/include/glib-2.0/glib/gmain.h and fixed in upstream
ba2cf2051daaf45b7e63998190ef4f8672cc180b.
--
WBR, wRAR
signature.asc
Description: Digital signature
Processed: Re: Bug#710622: comedilib: FTBFS: ./calib_yacc.h:119:5: error: conflicting types for 'calib_yyparse'
Processing control commands: tags -1 + upstream Bug #710622 [src:comedilib] comedilib: FTBFS: ./calib_yacc.h:119:5: error: conflicting types for 'calib_yyparse' Added tag(s) upstream. -- 710622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710622 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: Re: Bug#710607: ruby-gnome2: FTBFS: glib-enum-types.c:499:10: error: expected expression before ',' token
Processing control commands: tags -1 + upstream fixed-upstream Bug #710607 [src:ruby-gnome2] ruby-gnome2: FTBFS: glib-enum-types.c:499:10: error: expected expression before ',' token Added tag(s) upstream and fixed-upstream. -- 710607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710607 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: Re: Bug#710614: bip: FTBFS: lex.l:19:6: error: conflicting types for 'yyparse'
Processing control commands: tags -1 + upstream Bug #710614 [src:bip] bip: FTBFS: lex.l:19:6: error: conflicting types for 'yyparse' Added tag(s) upstream. -- 710614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710614 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#710734: libgmsh2: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libjava-gmsh.so.2
Hi Andreas, thanks for bugreport, it will be fixed today. The only question about piuparts. How can I reproduce this failure with piuparts? sudo piuparts -d testing -d sid gmsh_2.7.1.dfsg-1_amd64.changes returns PASS: All tests What do I do wrong? Thanks, Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709050: [pkg-GD-devel] Bug#709050: mscgen: fails to build with current libgd2
And in case anyone's keeping track, this was introduced by the fix for this bug: https://bitbucket.org/libgd/gd-libgd/issue/51/crash-in-master-with-ft-function Well, it was forgotten in this commit: https://bitbucket.org/libgd/gd-libgd/commits/20015feb2daaab43b641b21fc88fc59cacb824fc Anyway it's fixed upstream now. Many thanks to Colin for catching this. O. -- Ondřej Surý ond...@sury.org
Bug#709050: [pkg-GD-devel] Bug#709050: mscgen: fails to build with current libgd2
On Sun, Jun 02, 2013 at 10:18:07AM +0200, Ondřej Surý wrote: Well, it was forgotten in this commit: https://bitbucket.org/libgd/gd-libgd/commits/20015feb2daaab43b641b21fc88fc59cacb824fc Ah yes, quite right, I misattributed. Thanks. -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710734: libgmsh2: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libjava-gmsh.so.2
On 2013-06-02 09:28, Anton Gladky wrote: Hi Andreas, thanks for bugreport, it will be fixed today. The only question about piuparts. How can I reproduce this failure with piuparts? sudo piuparts -d testing -d sid gmsh_2.7.1.dfsg-1_amd64.changes returns PASS: All tests What do I do wrong? put the .debs in a local repository, e.g. /tmp/gmshrepo, together with a Packages file and add --bindmounts /tmp/gmshrepo --testdebs-repo /tmp/gmshrepo --distupgrade-to-testdebs Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710614: bip: FTBFS: lex.l:19:6: error: conflicting types for 'yyparse'
Control: tags -1 + upstream On Fri, May 31, 2013 at 06:55:35PM +0200, David Suárez wrote: lex.l:19:6: error: conflicting types for 'yyparse' In file included from lex.l:15:0: src/conf.h:201:5: note: previous declaration of 'yyparse' was here bison 2.6 declares yyparse in the generated header. -- WBR, wRAR signature.asc Description: Digital signature
Bug#710752: pxe-pdhcp: eats 100% of CPU
On Du, 02 iun 13, 15:07:02, Osamu Aoki wrote: Package: pxe-pdhcp Is this package still in NEW or somewhere? apt-cache can't find it. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Bug#707226: [pkg-wine-party] package wine does not install wine on amd64
If you believe in that solution, please feel free to provide a patch. Complaints without action tend to be counter-productive time wasters. Exactly. That would surely be the answer if filing this for packages that depend on wine. Exept, wine-party is resposible for a package that currently suffers from not being able to fulfill the dependency and simply hasn't put the workaround's (hello world message) in the right place yet. Sorry, I won't bother other packages' devs that are not in the position to throw in a debconf question in the right place, to make sure all *admins* are getting informed properly. Nevermind, as an admin I reported the issue after having gone through troubles, and it is the pkg-wine-party decision to appreciate it or not. The thing is as simple as package wine does not install wine on amd64. Install time informations would surely be appreciated if only an incomplete installation happened. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710767: libreoffice-dev: fails to upgrade from 'sid' - trying to overwrite /usr/lib/libreoffice/program/gengal.bin
Package: libreoffice-dev Version: 1:4.1.0~beta1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace libreoffice-dev 1:4.0.3-3 (using .../libreoffice-dev_1%3a4.1.0~beta1-2_amd64.deb) ... Unpacking replacement libreoffice-dev ... dpkg: error processing /var/cache/apt/archives/libreoffice-dev_1%3a4.1.0~beta1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/libreoffice/program/gengal.bin', which is also in package libreoffice-core 1:4.0.3-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas libreoffice-dev_1:4.1.0~beta1-2.log.gz Description: GNU Zip compressed data
Processed: Re: Bug#710501: avinfo: FTBFS: ass.tab.h:104:5: error: conflicting types for 'yyparse'
Processing control commands: tags -1 + upstream Bug #710501 [src:avinfo] avinfo: FTBFS: ass.tab.h:104:5: error: conflicting types for 'yyparse' Added tag(s) upstream. -- 710501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710501 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#707226: [pkg-wine-party] package wine does not install wine on amd64
Michael, somehow I misread your response, as if you wanted me to patch other packages, but reconsidering I think you have rather expressed you'd consider a patch from me. Thanks for being willing to accept an improvement. I would certainly send a patch if I were able to. So please leave the bug open, to reflect the status and point other admins and users to the solution. Have a nice weekend. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Am I correct? $ im-config -d + shift + '[' -n '' ']' + '[' X = X ']' + '[' '!' -x /usr/bin/zenity ']' + '[' x:0 = x ']' ++ active_im ++ '[' '!' -r /home/aron/.xinputrc ']' ++ check_md5sum /home/aron/.xinputrc ++ '[' -r /home/aron/.xinputrc ']' +++ head -n -1 /home/aron/.xinputrc +++ md5sum +++ tail -n 1 /home/aron/.xinputrc ++ '[' '# im-config signiture: 714704ce7c216b2637069531e1e21e72 -' = '# im-config signiture: 714704ce7c216b2637069531e1e21e72 -' ']' ++ true +++ sed -n -e 's/^run_im \([^ ]*\) *$/\1/p' ++ IM_CONFIG_ACTIVE_IM=fcitx ++ '[' -z fcitx ']' ++ '[' -r /usr/share/im-config/data/22_fcitx.conf ']' ++ echo fcitx + IM_CONFIG_ACTIVE=fcitx + '[' fcitx = custom ']' + IM_CONFIG_NUMBER=0 + IM_CONFIG_AVAIL= + for IM_CONFIG_PATH in '$IM_CONFIG_DATA/[12345678][0123456789]_*.rc' ++ name_im /usr/share/im-config/data/20_ibus.rc ++ local x ++ x=ibus.rc ++ x=ibus ++ x=ibus ++ echo -n ibus + IM_CONFIG_NAME=ibus + avail_menu ibus + '[' -r /usr/share/im-config/data/20_ibus.conf ']' + . /usr/share/im-config/data/20_ibus.conf +++ gettext 'activate Intelligent Input Bus (IBus)' ++ IM_CONFIG_SHORT='activate Intelligent Input Bus (IBus)' +++ gettext 'Intelligent Input Bus (IBus) * Required for all: ibus * Language specific input conversion support: * Japanese: ibus-mozc (best) or ibus-anthy or ibus-skk * Korean: ibus-hangul * Simplified Chinese: ibus-pinyin or ibus-sunpinyin or ibus-googlepinyin * Traditional Chinese: ibus-chewing * Thai: ibus-table-thai * Vietnamese: ibus-unikey or ibus-table-viqr * X Keyboard emulation: ibus-xkbc * Generic keyboard translation table: ibus-m17n or ibus-table* packages * Application platform support: * GNOME/GTK+: ibus-gtk and ibus-gtk3 (both) * KDE/Qt: ibus-qt4 * Clutter: ibus-clutter * EMACS: ibus-el' ++ IM_CONFIG_LONG='Intelligent Input Bus (IBus) * Required for all: ibus * Language specific input conversion support: * Japanese: ibus-mozc (best) or ibus-anthy or ibus-skk * Korean: ibus-hangul * Simplified Chinese: ibus-pinyin or ibus-sunpinyin or ibus-googlepinyin * Traditional Chinese: ibus-chewing * Thai: ibus-table-thai * Vietnamese: ibus-unikey or ibus-table-viqr * X Keyboard emulation: ibus-xkbc * Generic keyboard translation table: ibus-m17n or ibus-table* packages * Application platform support: * GNOME/GTK+: ibus-gtk and ibus-gtk3 (both) * KDE/Qt: ibus-qt4 * Clutter: ibus-clutter * EMACS: ibus-el' + package_menu + package_status ibus + PACKAGE_NAME=ibus ++ LANG=C ++ dpkg-query -l ibus ++ sed -n '6s/\([^ ]*\) .*$/\1/p' + '[' '' = ii ']' + return 1 + for IM_CONFIG_PATH in '$IM_CONFIG_DATA/[12345678][0123456789]_*.rc' ++ name_im /usr/share/im-config/data/22_fcitx.rc ++ local x ++ x=fcitx.rc ++ x=fcitx ++ x=fcitx ++ echo -n fcitx + IM_CONFIG_NAME=fcitx + avail_menu fcitx + '[' -r /usr/share/im-config/data/22_fcitx.conf ']' + . /usr/share/im-config/data/22_fcitx.conf +++ gettext 'activate Flexible Input Method Framework (fcitx)' ++ IM_CONFIG_SHORT='activate Flexible Input Method Framework (fcitx)' +++ gettext 'Flexible Input Method Framework (fcitx) * Required for all: fcitx * Language specific input conversion support: * Simplified Chinese: fcitx-pinyin or fcitx-sunpinyin or fcitx-googlepinyin * Generic keyboard translation table: fcitx-table* packages * Application platform support: * GNOME/GTK+: fcitx-frontend-gtk2 and fcitx-frontend-gtk3 (both) * KDE/Qt4: fcitx-frontend-qt4' ++ IM_CONFIG_LONG='Flexible Input Method Framework (fcitx) * Required for all: fcitx * Language specific input conversion support: * Simplified Chinese: fcitx-pinyin or fcitx-sunpinyin or fcitx-googlepinyin * Generic keyboard translation table: fcitx-table* packages * Application platform support: * GNOME/GTK+: fcitx-frontend-gtk2 and fcitx-frontend-gtk3 (both) * KDE/Qt4: fcitx-frontend-qt4' + package_menu + package_status fcitx-bin + PACKAGE_NAME=fcitx-bin ++ LANG=C ++ sed -n '6s/\([^ ]*\) .*$/\1/p' ++ dpkg-query -l fcitx-bin + '[' ii = ii ']' + return 0 + '[' fcitx '!=' none ']' + IM_CONFIG_NUMBER=1 + IM_CONFIG_AVAIL=' fcitx' + for IM_CONFIG_PATH in '$IM_CONFIG_DATA/[12345678][0123456789]_*.rc' ++ name_im /usr/share/im-config/data/24_uim.rc ++ local x ++ x=uim.rc ++ x=uim ++ x=uim ++ echo -n uim + IM_CONFIG_NAME=uim + avail_menu uim + '[' -r /usr/share/im-config/data/24_uim.conf ']' + . /usr/share/im-config/data/24_uim.conf +++ gettext 'activate universal input method (uim)' ++ IM_CONFIG_SHORT='activate universal input method (uim)' +++ gettext 'universal input method (uim) * Required for all: uim * Language specific input conversion support: * Japanese: uim-mozc (best) or uim-anthy or uim-skk * Korean: uim-byeoru * Simplified Chinese: uim-pinyin * Traditional Chinese: uim-chewing * Vietnamese: uim-viqr * General-purpose M17n: uim-m17nlib * Application platform support: * XIM: uim-xim * GNOME/GTK+: uim-gtk2.0 and uim-gtk3 (both) * KDE/Qt4: uim-qt * EMACS:
Bug#710501: avinfo: FTBFS: ass.tab.h:104:5: error: conflicting types for 'yyparse'
Control: tags -1 + upstream On Thu, May 30, 2013 at 07:58:03PM +0200, David Suárez wrote: In file included from ass.y:26:0: ass.tab.h:104:5: error: conflicting types for 'yyparse' In file included from avinfo.h:75:0, from ass.y:24: ass.h:29:5: note: previous declaration of 'yyparse' was here bison 2.6 declares yyparse in the generated header. -- WBR, wRAR signature.asc Description: Digital signature
Bug#710615: openmeeg: FTBFS: MatlabIO.H:116:100: error: 'BY_NAME' was not declared in this scope
Control: tags -1 + upstream On Fri, May 31, 2013 at 11:36:28PM +0200, David Suárez wrote: /«PKGBUILDDIR»/libs/MatLib/MatLib/MatlabIO.H: In static member function 'static matvar_t* OpenMEEG::maths::details::helperOpenMEEG::SymMatrix::set_type(matvar_t*, OpenMEEG::LinOpInfo)': /«PKGBUILDDIR»/libs/MatLib/MatLib/MatlabIO.H:116:100: error: 'BY_NAME' was not declared in this scope Looks like BY_NAME was renamed to MAT_BY_NAME between libmatio-dev 1.3.4-4 and 1.5.1-1. -- WBR, wRAR signature.asc Description: Digital signature
Processed: Re: Bug#710615: openmeeg: FTBFS: MatlabIO.H:116:100: error: 'BY_NAME' was not declared in this scope
Processing control commands: tags -1 + upstream Bug #710615 [src:openmeeg] openmeeg: FTBFS: MatlabIO.H:116:100: error: 'BY_NAME' was not declared in this scope Added tag(s) upstream. -- 710615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710615 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: package wine does not install wine on amd64
Processing commands for cont...@bugs.debian.org:
reopen 707226
Bug #707226 {Done: Michael Gilbert mgilb...@debian.org} [wine] package wine
does not insall wine on amd64
Bug reopened
Ignoring request to alter fixed versions of bug #707226 to the same values
previously set
retitle 707226 package wine does not install wine on amd64
Bug #707226 [wine] package wine does not insall wine on amd64
Changed Bug title to 'package wine does not install wine on amd64' from
'package wine does not insall wine on amd64'
End of message, stopping processing here.
Please contact me if you need assistance.
--
707226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707226
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#707560: libucommon6-dbg and libucommon5-dbg: error when trying to install together
On Thu, 9 May 2013 14:23:36 Ralf Treinen wrote: Version: libucommon5-dbg/5.2.2-4 Version: libucommon6-dbg/6.0.4-1 Jonas, Could I suggest that do not version the -dbg package. Whilst there is a use to have the library package versioned, there is little to be gained by versioning the -dbg package, and it does lead to ongoing conflicts like this one. Mark signature.asc Description: This is a digitally signed message part.
Bug#710757: tortoisehg: not installable in sid
package tortoisehg tags 710757 + confirmed pending sid thanks On Sun, Jun 2, 2013 at 12:20 AM, Ralf Treinen trei...@free.fr wrote: tortoisehg is not installable in sid since it depends on mercurial (= 2.1~), mercurial ( 2.3~) However, the version of mercurial available in sid is 2.6.1-1. Thank you for the report. I will upload tortoisehg 2.8 soon. Ludovico -- 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#710757: tortoisehg: not installable in sid
Processing commands for cont...@bugs.debian.org: package tortoisehg Limiting to bugs with field 'package' containing at least one of 'tortoisehg' Limit currently set to 'package':'tortoisehg' tags 710757 + confirmed pending sid Bug #710757 [tortoisehg] tortoisehg: not installable in sid Added tag(s) sid, confirmed, and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 710757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710757 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#708111: marked as done (libgd2-xpm-dev, libgd2-noxpm-dev: copyright file missing after upgrade (policy 12.5))
Your message dated Sun, 02 Jun 2013 09:20:31 + with message-id e1uj4sl-00042v...@franck.debian.org and subject line Bug#708111: fixed in libgd2 2.1.0~rc1-2 has caused the Debian Bug report #708111, regarding libgd2-xpm-dev, libgd2-noxpm-dev: copyright file missing after upgrade (policy 12.5) 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.) -- 708111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgd2-xpm-dev,libgd2-noxpm-dev Version: 2.1.0~alpha~8+ecc535-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: sid - experimental From the attached log (scroll to the bottom...): MISSING COPYRIGHT FILE: /usr/share/doc/libgd2-noxpm-dev/copyright # ls -lad /usr/share/doc/libgd2-noxpm-dev drwxr-xr-x 2 root root 40 May 11 21:30 /usr/share/doc/libgd2-noxpm-dev # ls -la /usr/share/doc/libgd2-noxpm-dev/ total 0 drwxr-xr-x 2 root root 40 May 11 21:30 . drwxr-xr-x 133 root root 2760 May 11 21:30 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a directory to a symlink the *postinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ DOCLINK=@@OTHERPACKAGE@@ if [ -d $DOCDIR ] [ ! -L $DOCDIR ]; then rmdir $DOCDIR ln -s $DOCLINK $DOCDIR fi For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi cheers, Andreas libgd2-xpm-dev_2.1.0~alpha~8+ecc535-2.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: libgd2 Source-Version: 2.1.0~rc1-2 We believe that the bug you reported is fixed in the latest version of libgd2, 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 708...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated libgd2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 25 May 2013 19:43:22 +0200 Source: libgd2 Binary: libgd-tools libgd-dev libgd3 libgd-dbg libgd2-xpm-dev libgd2-noxpm-dev Architecture: source amd64 all Version: 2.1.0~rc1-2 Distribution: unstable Urgency: low Maintainer: GD team pkg-gd-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libgd-dbg - Debug symbols for GD Graphics Library libgd-dev - GD Graphics Library (development version) libgd-tools - GD command line tools and example code libgd2-noxpm-dev - GD Graphics Library (transitional package) libgd2-xpm-dev - GD Graphics Library (transitional package) libgd3 - GD Graphics Library Closes: 708111 709050 Changes: libgd2 (2.1.0~rc1-2) unstable; urgency=low . [ Colin Watson ] * Add missing pointer dereference in font_pattern (closes: #709050). . [ Ondřej Surý ] * I will test my changes with piuparts release (Closes: #708111) Checksums-Sha1: 720dbd203dacd82b48ff42a0e2c666cc7e5608bb 1702 libgd2_2.1.0~rc1-2.dsc 45d558cb78a29df5908b465bd8297b9acc40ef2d 25477 libgd2_2.1.0~rc1-2.debian.tar.gz 7425c54c7b910f3a1ca8ef622841aaa77ca129c8 47366 libgd-tools_2.1.0~rc1-2_amd64.deb 8fb47bf9f09e0afd1603cea76d7194ed4a954bc3 324688 libgd-dev_2.1.0~rc1-2_amd64.deb 6f4be260d91d6771db858a3ddcfe7c190a578bd7 171330 libgd3_2.1.0~rc1-2_amd64.deb 8103ec20b5002b50e7349da0ccc54632d2cc2193 356258 libgd-dbg_2.1.0~rc1-2_amd64.deb
Bug#709050: marked as done (mscgen: fails to build with current libgd2)
Your message dated Sun, 02 Jun 2013 09:20:31 + with message-id e1uj4sl-000432...@franck.debian.org and subject line Bug#709050: fixed in libgd2 2.1.0~rc1-2 has caused the Debian Bug report #709050, regarding mscgen: fails to build with current libgd2 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.) -- 709050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mscgen Version: 0.20-2 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy mscgen fails to build in unstable as follows: make check-TESTS make[3]: Entering directory `/«PKGBUILDDIR»/build/test' testinput0.msc Error: gdoTextHeight: Could not read font (GDFONTPATH=) FAIL: renderercheck.sh 1 of 1 test failed Please report to michael.mcternan.2...@cs.bris.ac.uk make[3]: *** [check-TESTS] Error 1 If it helps, you can see a corresponding Ubuntu build log here: https://launchpadlibrarian.net/140264375/buildlog_ubuntu-saucy-i386.mscgen_0.20-2build2_FAILEDTOBUILD.txt.gz I don't quite know what's happening here, as running the tests by hand seems to succeed. Thanks, -- Colin Watson [cjwat...@ubuntu.com] ---End Message--- ---BeginMessage--- Source: libgd2 Source-Version: 2.1.0~rc1-2 We believe that the bug you reported is fixed in the latest version of libgd2, 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 709...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated libgd2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 25 May 2013 19:43:22 +0200 Source: libgd2 Binary: libgd-tools libgd-dev libgd3 libgd-dbg libgd2-xpm-dev libgd2-noxpm-dev Architecture: source amd64 all Version: 2.1.0~rc1-2 Distribution: unstable Urgency: low Maintainer: GD team pkg-gd-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libgd-dbg - Debug symbols for GD Graphics Library libgd-dev - GD Graphics Library (development version) libgd-tools - GD command line tools and example code libgd2-noxpm-dev - GD Graphics Library (transitional package) libgd2-xpm-dev - GD Graphics Library (transitional package) libgd3 - GD Graphics Library Closes: 708111 709050 Changes: libgd2 (2.1.0~rc1-2) unstable; urgency=low . [ Colin Watson ] * Add missing pointer dereference in font_pattern (closes: #709050). . [ Ondřej Surý ] * I will test my changes with piuparts release (Closes: #708111) Checksums-Sha1: 720dbd203dacd82b48ff42a0e2c666cc7e5608bb 1702 libgd2_2.1.0~rc1-2.dsc 45d558cb78a29df5908b465bd8297b9acc40ef2d 25477 libgd2_2.1.0~rc1-2.debian.tar.gz 7425c54c7b910f3a1ca8ef622841aaa77ca129c8 47366 libgd-tools_2.1.0~rc1-2_amd64.deb 8fb47bf9f09e0afd1603cea76d7194ed4a954bc3 324688 libgd-dev_2.1.0~rc1-2_amd64.deb 6f4be260d91d6771db858a3ddcfe7c190a578bd7 171330 libgd3_2.1.0~rc1-2_amd64.deb 8103ec20b5002b50e7349da0ccc54632d2cc2193 356258 libgd-dbg_2.1.0~rc1-2_amd64.deb 91f24de5d0314f95dbdb629929baa122437b9fb6 1098 libgd2-xpm-dev_2.1.0~rc1-2_all.deb 36b93e7899fe326657483ebec03d39eee287488c 1102 libgd2-noxpm-dev_2.1.0~rc1-2_all.deb Checksums-Sha256: b88b1da51fcaeade212fc3b1f76e3c7bb26b16f331d46a2b6cafa3147898ba88 1702 libgd2_2.1.0~rc1-2.dsc a84f69bd52d98ffcdc28b668ae849cbc08a9842bfa356de13c4168225330a210 25477 libgd2_2.1.0~rc1-2.debian.tar.gz 6f6b6fd5635ba0093a97c01f6428161ab0896f0e2b9082e6a702378b1c6722ff 47366 libgd-tools_2.1.0~rc1-2_amd64.deb 262f54adad530557153af040f3c05e4d444ef1e44ecbc1afeaa3231705a9ae95 324688 libgd-dev_2.1.0~rc1-2_amd64.deb 3d5fff148f3759cb8974dbbe3d316b69fde3327afe15f37823994711132844ed 171330 libgd3_2.1.0~rc1-2_amd64.deb 1a490b0328ad9e696071356e0856777667ef71bf70df4e65f628442a31d9a76b 356258 libgd-dbg_2.1.0~rc1-2_amd64.deb ecc7de4dff55c290b92f691adacf9650f0daee3c4151f9e30c52cc741c75af73 1098 libgd2-xpm-dev_2.1.0~rc1-2_all.deb
Bug#707404: marked as done (libsocialweb: FTBFS: SocialWebClient-0.25.gir:20.11-20.32: error: expected start element of `parameter')
Your message dated Sun, 02 Jun 2013 09:21:00 + with message-id e1uj4te-0004a9...@franck.debian.org and subject line Bug#707404: fixed in libsocialweb 0.25.20-5 has caused the Debian Bug report #707404, regarding libsocialweb: FTBFS: SocialWebClient-0.25.gir:20.11-20.32: error: expected start element of `parameter' 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.) -- 707404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libsocialweb Version: 0.25.20-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/vala' /usr/bin/vapigen \ --library libsocialweb-client \ --pkg gio-2.0 \ ../libsocialweb-client/SocialWebClient-0.25.gir \ SocialWebClient-0.25.gir:20.11-20.32: error: expected start element of `parameter' instance-parameter name=client transfer-ownership=none ^^ SocialWebClient-0.25.gir:22.11-22.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:33.11-33.32: error: expected start element of `parameter' instance-parameter name=client transfer-ownership=none ^^ SocialWebClient-0.25.gir:35.11-35.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:49.11-49.32: error: expected start element of `parameter' instance-parameter name=client transfer-ownership=none ^^ SocialWebClient-0.25.gir:51.11-51.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:130.11-130.44: error: expected start element of `parameter' instance-parameter name=contact_view transfer-ownership=none ^^ SocialWebClient-0.25.gir:132.11-132.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:140.11-140.44: error: expected start element of `parameter' instance-parameter name=contact_view transfer-ownership=none ^^ SocialWebClient-0.25.gir:142.11-142.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:150.11-150.44: error: expected start element of `parameter' instance-parameter name=contact_view transfer-ownership=none ^^ SocialWebClient-0.25.gir:152.11-152.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:160.11-160.44: error: expected start element of `parameter' instance-parameter name=contact_view transfer-ownership=none ^^ SocialWebClient-0.25.gir:162.11-162.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:316.11-316.38: error: expected start element of `parameter' instance-parameter name=item_view transfer-ownership=none SocialWebClient-0.25.gir:318.11-318.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:326.11-326.38: error: expected start element of `parameter' instance-parameter name=item_view transfer-ownership=none SocialWebClient-0.25.gir:328.11-328.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:336.11-336.38: error: expected start element of `parameter' instance-parameter name=item_view transfer-ownership=none SocialWebClient-0.25.gir:338.11-338.10: error: expected end element of `parameter' /instance-parameter SocialWebClient-0.25.gir:346.11-346.38: error: expected start element of `parameter' instance-parameter name=item_view transfer-ownership=none SocialWebClient-0.25.gir:348.11-348.10: error: expected end element of `parameter' /instance-parameter
Bug#710613: libvirt-glib: FTBFS: LibvirtGConfig-1.0.gir:109.11-109.32: error: expected start element of `parameter'
On Fri, May 31, 2013 at 10:17:59PM +0200, David Suárez wrote: Source: libvirt-glib Version: 0.0.8-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. It's a vala bug and is fixed in 0.20, you should update your Build-Depends to 'valac (= 0.20)'. Already fixed with 0.1.6 in unstable -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710722: marked as done (xtables-addons: module build fails for kernel 3.8)
Your message dated Sun, 02 Jun 2013 09:23:13 + with message-id e1uj4vn-0005t5...@franck.debian.org and subject line Bug#710722: fixed in xtables-addons 2.2-1 has caused the Debian Bug report #710722, regarding xtables-addons: module build fails for kernel 3.8 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.) -- 710722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xtables-addons Version: 1.47.1-1 Severity: serious DKMS make.log for xtables-addons-1.47.1 for kernel 3.8-2-amd64 (x86_64) Sat Jun 1 21:13:32 UTC 2013 make: Entering directory `/usr/src/linux-headers-3.8-2-amd64' CC [M] /usr/src/xtables-addons-1.47.1/compat_xtables.o CC [M] /usr/src/xtables-addons-1.47.1/xt_CHAOS.o CC [M] /usr/src/xtables-addons-1.47.1/xt_DELUDE.o CC [M] /usr/src/xtables-addons-1.47.1/xt_DHCPMAC.o CC [M] /usr/src/xtables-addons-1.47.1/xt_DNETMAP.o /usr/src/xtables-addons-1.47.1/xt_DNETMAP.c:30:39: fatal error: net/netfilter/nf_nat_rule.h: No such file or directory compilation terminated. make[3]: *** [/usr/src/xtables-addons-1.47.1/xt_DNETMAP.o] Error 1 make[2]: *** [_module_/usr/src/xtables-addons-1.47.1] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 make: Leaving directory `/usr/src/linux-headers-3.8-2-amd64' ---End Message--- ---BeginMessage--- Source: xtables-addons Source-Version: 2.2-1 We believe that the bug you reported is fixed in the latest version of xtables-addons, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov only...@debian.org (supplier of updated xtables-addons package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 18:16:23 +1000 Source: xtables-addons Binary: xtables-addons-common xtables-addons-dkms xtables-addons-source Architecture: source amd64 all Version: 2.2-1 Distribution: unstable Urgency: low Maintainer: Pierre Chifflier pol...@debian.org Changed-By: Dmitry Smirnov only...@debian.org Description: xtables-addons-common - Extensions targets and matches for iptables [tools, libs] xtables-addons-dkms - Extensions targets and matches for iptables xtables-addons-source - Extensions targets and matches for iptables [modules sources] Closes: 710379 710722 710725 Changes: xtables-addons (2.2-1) unstable; urgency=low . * New upstream version [March 2013]. + compatible with kernels 3.7+ (Closes: #710722). * Standards to version 3.9.4. * Dropped unknown package linux-headers-generic from Recommends. * Removed unnecessary versioned (Build-)Depends. * Updated DKMS rules to build modules in DKMS build directory and not to leave un-owned files behind (Closes: #710725). * New patches: + to fix invalid quota2 record on iptables-save (Closes: #710379), thanks to Denis Ustimenko. + to avoid duplication in man pages. + to lintianise man pages and correct spelling. * bashism_xt_geoip_dl.patch is renamed and refreshed; DEP-3 headers added. * Updated my email address; bumped copyright years. Checksums-Sha1: 33cbdafaf37c01920bba6685be1c0811e0976b89 2136 xtables-addons_2.2-1.dsc 589f7e27866e108dc44ad60b6f321e14eb707ae5 316840 xtables-addons_2.2.orig.tar.xz 560d134846a5f883bd00eed97ebedc1eb3beb39f 12852 xtables-addons_2.2-1.debian.tar.xz 321bbff4cff31a4e8dc335bbcaa4bd235c3d472d 85290 xtables-addons-common_2.2-1_amd64.deb 3c021018db6f787ed925c25f36ed557919a1f20a 157590 xtables-addons-dkms_2.2-1_all.deb c6564c754bed13c92a0d4cb0f052c70638839a78 119922 xtables-addons-source_2.2-1_all.deb Checksums-Sha256: cac640e3b4ab698e2780ce4d1f37685916dc5ba94b09baa6d3dc630332d11469 2136 xtables-addons_2.2-1.dsc bafaf53b896272adcf17f240339c866eff07d30b51be8893a08deaf69f8f13ef 316840 xtables-addons_2.2.orig.tar.xz 75b56474561b942d3d4cfa39013d53bcb5c85f047c1af2679e15a5286b773898 12852 xtables-addons_2.2-1.debian.tar.xz 682736fc9475ebbd19337fea5a165cf3d9e8b7bca9e34d81351c995f9c72bb10 85290 xtables-addons-common_2.2-1_amd64.deb
Bug#710613: marked as done (libvirt-glib: FTBFS: LibvirtGConfig-1.0.gir:109.11-109.32: error: expected start element of `parameter')
Your message dated Sat, 1 Jun 2013 11:58:13 +0200 with message-id 20130601095813.ga27...@bogon.sigxcpu.org and subject line Re: Bug#710613: libvirt-glib: FTBFS: LibvirtGConfig-1.0.gir:109.11-109.32: error: expected start element of `parameter' has caused the Debian Bug report #710613, regarding libvirt-glib: FTBFS: LibvirtGConfig-1.0.gir:109.11-109.32: error: expected start element of `parameter' 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.) -- 710613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libvirt-glib Version: 0.0.8-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. It's a vala bug and is fixed in 0.20, you should update your Build-Depends to 'valac (= 0.20)'. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/vapi' GENlibvirt-gconfig-1.0.vapi LibvirtGConfig-1.0.gir:109.11-109.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:111.11-111.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:123.11-123.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:125.11-125.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:137.11-137.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:139.11-139.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:151.11-151.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:153.11-153.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:164.11-164.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:166.11-166.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:175.11-175.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:178.11-178.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:186.11-186.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:188.11-188.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:196.11-196.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:198.11-198.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:206.11-206.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:208.11-208.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:221.11-221.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:223.11-223.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:241.11-241.32: error: expected start element of `parameter' instance-parameter name=domain transfer-ownership=none ^^ LibvirtGConfig-1.0.gir:243.11-243.10: error: expected end element of `parameter' /instance-parameter LibvirtGConfig-1.0.gir:254.11-254.32: error: expected start element of `parameter'
Bug#702715: tortoisehg: broken pyqt4 version check
package tortoisehg forcemerge 702715 710453 tags 702715 + confirmed pending jessie sid thanks Hi, On Wed, May 29, 2013 at 7:58 AM, Matthew Gabeler-Lee chee...@fastcat.org wrote: This bug has now landed. As the packages in testing / unstable now stand, you cannot use tortoisehg. Thank you for the report and for looking into the issue. I am about to upload the latest version (2.8) which is not affected by this bug. Thanks, Ludovico -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710774: qiime: FTBFS: ghc6 no longer exists, use ghc
Package: qiime Version: 1.5.0-2 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch saucy ghc6 has been a transitional package for over two years, and has now been removed from unstable. As a result, qiime fails to build. Please apply this patch to fix it. * Build-depend on ghc rather than ghc6. diff -Nru qiime-1.5.0/debian/control qiime-1.5.0/debian/control --- qiime-1.5.0/debian/control 2012-08-06 08:25:40.0 +0100 +++ qiime-1.5.0/debian/control 2013-06-02 10:22:38.0 +0100 @@ -6,7 +6,7 @@ Andreas Tille ti...@debian.org DM-Upload-Allowed: yes Build-Depends: debhelper (= 9), python-all-dev (= 2.7), python-cogent ( = 1.5.1 ), - python-numpy, python-matplotlib, ghc6, python-sphinx + python-numpy, python-matplotlib, ghc, python-sphinx Standards-Version: 3.9.3 Homepage: http://www.qiime.org/ Vcs-Browser: http://svn.debian.org/wsvn/debian-med/trunk/packages/qiime/trunk/ Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fwd: Bug#710453: Bug#702715: tortoisehg: broken pyqt4 version check
Processing commands for cont...@bugs.debian.org: package tortoisehg Limiting to bugs with field 'package' containing at least one of 'tortoisehg' Limit currently set to 'package':'tortoisehg' forcemerge 702715 710453 Bug #702715 [tortoisehg] tortoisehg: broken pyqt4 version check Bug #710453 [tortoisehg] tortoisehg: does not start Set Bug forwarded-to-address to 'https://bitbucket.org/tortoisehg/thg/issue/2467'. Severity set to 'serious' from 'grave' Added tag(s) fixed-upstream. Merged 702715 710453 tags 702715 + confirmed pending jessie sid Bug #702715 [tortoisehg] tortoisehg: broken pyqt4 version check Bug #710453 [tortoisehg] tortoisehg: does not start Added tag(s) sid, confirmed, jessie, and pending. Added tag(s) sid, confirmed, jessie, and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 702715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702715 710453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710453 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#710633: orafce: FTBFS: plvlex.c:209:3: error: too many arguments to function 'orafce_sql_yyparse'
Control: tags -1 + upstream On Fri, May 31, 2013 at 06:56:30PM +0200, David Suárez wrote: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -fPIC -pie -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -fpic -I. -I/«PKGBUILDDIR» -I/usr/include/postgresql/9.1/server -I/usr/include/postgresql/internal -D_FORTIFY_SOURCE=2 -DLINUX_OOM_ADJ=0 -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include/tcl8.5 -I.. -c -o plvlex.o /«PKGBUILDDIR»/plvlex.c /«PKGBUILDDIR»/plvlex.c: In function 'plvlex_tokens': /«PKGBUILDDIR»/plvlex.c:209:3: error: too many arguments to function 'orafce_sql_yyparse' In file included from /«PKGBUILDDIR»/plvlex.c:23:0: /«PKGBUILDDIR»/sqlparse.h:115:5: note: declared here YYPARSE_PARAM is defined only in sqlparse.c so when sqlparse.h is included without defining this symbol first the orafce_sql_yyparse signature will be different. Though I don't know bison enough to tell how this should have been used (also note that YYPARSE_PARAM is deprecated). -- WBR, wRAR signature.asc Description: Digital signature
Processed: Re: Bug#710633: orafce: FTBFS: plvlex.c:209:3: error: too many arguments to function 'orafce_sql_yyparse'
Processing control commands: tags -1 + upstream Bug #710633 [src:orafce] orafce: FTBFS: plvlex.c:209:3: error: too many arguments to function 'orafce_sql_yyparse' Added tag(s) upstream. -- 710633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633 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#706909: marked as done (smartmontools: updated drivedb.h should go to /var)
Your message dated Sun, 02 Jun 2013 09:49:55 + with message-id e1uj4vd-cd...@franck.debian.org and subject line Bug#706909: fixed in smartmontools 6.1+svn3812-1 has caused the Debian Bug report #706909, regarding smartmontools: updated drivedb.h should go to /var 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.) -- 706909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smartmontools Version: 5.41+svn3365-1 Severity: serious Usertags: fhs The update-smart-drivedb program writes to a file in the package instead of to a file in /var, please change it to use the proper location. pabs@chianamo ~ $ debsums -s smartmontools pabs@chianamo ~ $ sudo update-smart-drivedb /usr/share/smartmontools/drivedb.h updated from branches/RELEASE_5_43_DRIVEDB pabs@chianamo ~ $ debsums -s smartmontools debsums: changed file /usr/share/smartmontools/drivedb.h (from smartmontools package) -- Package-specific info: Output of /usr/share/bug/smartmontools: -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smartmontools depends on: ii debianutils 4.3.2 ii libc62.13-38 ii libcap-ng0 0.6.6-2 ii libgcc1 1:4.7.2-5 ii libselinux1 2.1.9-5 ii libstdc++6 4.7.2-5 ii lsb-base 4.1+Debian8 Versions of packages smartmontools recommends: ii bsd-mailx [mailx] 8.1.2-0.2006cvs-1 Versions of packages smartmontools suggests: pn gsmartcontrol none ii smart-notifier 0.28-5 -- Configuration Files: /etc/default/smartmontools changed: start_smartd=yes -- debsums errors found: debsums: changed file /usr/share/smartmontools/drivedb.h (from smartmontools package) -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: smartmontools Source-Version: 6.1+svn3812-1 We believe that the bug you reported is fixed in the latest version of smartmontools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 706...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Giuseppe Iuculano iucul...@debian.org (supplier of updated smartmontools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 11:14:02 +0200 Source: smartmontools Binary: smartmontools Architecture: source i386 Version: 6.1+svn3812-1 Distribution: unstable Urgency: low Maintainer: Giuseppe Iuculano iucul...@debian.org Changed-By: Giuseppe Iuculano iucul...@debian.org Description: smartmontools - control and monitor storage systems using S.M.A.R.T. Closes: 621411 633724 643928 684617 691646 704081 706909 708433 Changes: smartmontools (6.1+svn3812-1) unstable; urgency=low . * [ee38a43] Imported Upstream version 6.1+svn3812 (Closes: #691646) - Support for WD MyBook Essential 0x1058:0x0910 (Closes: #633724) - Added USB bridge to known IDs (Closes: #643928) - Added support for Seagate Expansion Desk external (usb) disks (Closes: #621411) * [1855d63] Refreshed patches and removed patches applied upstream * [d3fc9d1] Remove quilt from depends * [841c1a8] CHANGELOG file has been renamed, install Changelog * [3502e16] Updated VCS control fields * [8f14e44] debian/rules: Provide build-arch and build-indep * [0f1c16c] Harden smartmontools binaries * [555346e] Bump to 3.9.4 standards version * [5ae3fa9] Use /var/lib/smartmontools/drivedb for drivedb.h updates (Closes: #706909) * [c16ffdc] Create /var/lib/smartmontools/drivedb dir * [79a3dc2] Trigger the removal of /etc/init.d/smartd when upgrading (Closes: #684617, #704081) * [a0a5725] Also remove /etc/init.d/smartd in preinst script * [a26a490] Added man page for update-smart-drivedb. Thanks to Hannes von Haugwitz (Closes: #708433) Checksums-Sha1:
Bug#701409: marked as done (openscap: ftbfs with eglibc-2.17)
Your message dated Sun, 02 Jun 2013 09:49:39 + with message-id e1uj4ux-qx...@franck.debian.org and subject line Bug#701409: fixed in openscap 0.9.7-1 has caused the Debian Bug report #701409, regarding openscap: ftbfs with eglibc-2.17 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.) -- 701409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:openscap Version: 0.8.0-4 Severity: important Tags: sid jessie User: debian-gl...@lists.debian.org Usertags: ftbfs-glibc-2.17 The package fails to build in a test rebuild on at least amd64 with eglibc-2.17, but succeeds to build with eglibc-2.13. The severity of this report may be raised before the jessie release. The test rebuild was done together with GCC-4.8, so some issues might be caused by the updated GCC as well. ./stdio.h:1048:1: error: 'gets' undeclared here (not in a function) The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/openscap_0.8.0-4_unstable_gcc48.log The last lines of the build log are at the end of this report. To install eglibc from experimental, apt-get -t experimental install libc6-dev To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev [...] /«PKGBUILDDIR»/lib/vasnprintf.c:4692:6: warning: NEED_PRINTF_FLAG_LEFTADJUST is not defined [-Wundef] #if !NEED_PRINTF_FLAG_LEFTADJUST (!DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION) ^ /«PKGBUILDDIR»/lib/vasnprintf.c:4692:57: warning: ENABLE_UNISTDIO is not defined [-Wundef] #if !NEED_PRINTF_FLAG_LEFTADJUST (!DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION) ^ /«PKGBUILDDIR»/lib/vasnprintf.c:4692:76: warning: NEED_PRINTF_FLAG_ZERO is not defined [-Wundef] #if !NEED_PRINTF_FLAG_LEFTADJUST (!DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION) ^ /«PKGBUILDDIR»/lib/vasnprintf.c:4692:101: warning: NEED_PRINTF_UNBOUNDED_PRECISION is not defined [-Wundef] #if !NEED_PRINTF_FLAG_LEFTADJUST (!DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION) ^ /«PKGBUILDDIR»/lib/vasnprintf.c:4742:5: warning: NEED_PRINTF_FLAG_GROUPING is not defined [-Wundef] #if NEED_PRINTF_FLAG_GROUPING ^ /«PKGBUILDDIR»/lib/vasnprintf.c:4838:5: warning: NEED_PRINTF_DIRECTIVE_F is not defined [-Wundef] #if NEED_PRINTF_DIRECTIVE_F ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5091:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (count maxlen ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5217:5: warning: NEED_PRINTF_UNBOUNDED_PRECISION is not defined [-Wundef] #if NEED_PRINTF_UNBOUNDED_PRECISION ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5386:24: warning: ENABLE_UNISTDIO is not defined [-Wundef] #if !DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_LEFTADJUST || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5386:43: warning: NEED_PRINTF_FLAG_LEFTADJUST is not defined [-Wundef] #if !DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_LEFTADJUST || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5386:74: warning: NEED_PRINTF_FLAG_ZERO is not defined [-Wundef] #if !DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_LEFTADJUST || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5386:99: warning: NEED_PRINTF_UNBOUNDED_PRECISION is not defined [-Wundef] #if !DCHAR_IS_TCHAR || ENABLE_UNISTDIO || NEED_PRINTF_FLAG_LEFTADJUST || NEED_PRINTF_FLAG_ZERO || NEED_PRINTF_UNBOUNDED_PRECISION ^ /«PKGBUILDDIR»/lib/vasnprintf.c:5496:5: warning: NEED_PRINTF_DIRECTIVE_F is not defined [-Wundef] #if NEED_PRINTF_DIRECTIVE_F ^ make[5]: ***
Bug#680311: marked as done (Depends on obsoleted package sugar-hulahop)
Your message dated Sun, 02 Jun 2013 09:48:23 + with message-id e1uj4tj-00081b...@franck.debian.org and subject line Bug#710033: Removed package(s) from unstable has caused the Debian Bug report #680311, regarding Depends on obsoleted package sugar-hulahop 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.) -- 680311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ftp.debian.org Severity: normal As subject says: sugar-hulahop is too difficult to adapt to recent PyXPCOM and is dead upstream. - Jonas ---End Message--- ---BeginMessage--- Version: 0.7-1+rm Dear submitter, as the package pyjamas has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/710033 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)---End Message---
Bug#710033: marked as done (RM: pyjamas -- RoQA,)
Your message dated Sun, 02 Jun 2013 09:48:18 + with message-id e1uj4te-0007zq...@franck.debian.org and subject line Bug#710033: Removed package(s) from unstable has caused the Debian Bug report #710033, regarding RM: pyjamas -- RoQA, 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.) -- 710033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ftp.debian.org Severity: normal As subject says: sugar-hulahop is too difficult to adapt to recent PyXPCOM and is dead upstream. - Jonas ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: pyjamas | 0.7-1 | source, all pyjamas-canvas | 0.7-1 | all pyjamas-desktop | 0.7-1 | all pyjamas-doc | 0.7-1 | all pyjamas-gchart | 0.7-1 | all pyjamas-gmap | 0.7-1 | all pyjamas-pyjs | 0.7-1 | all pyjamas-ui | 0.7-1 | all --- Reason --- RoQA, depends on obsoleted package sugar-hulahop -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors (ftp.debian.org included) until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 710...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/710033 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)---End Message---
Bug#709885: marked as done (RM: gnutls-bin [mips mipsel] -- ROM; blocks gnutls26 propagation to testing)
Your message dated Sun, 02 Jun 2013 09:58:01 + with message-id e1uj533-0004wi...@franck.debian.org and subject line Bug#709885: Removed package(s) from unstable has caused the Debian Bug report #709885, regarding RM: gnutls-bin [mips mipsel] -- ROM; blocks gnutls26 propagation to testing 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.) -- 709885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ftp.debian.org Severity: normal Hello, I do not know for sure whether it is possible to selectivly remove two binary packages on specific architectures while keeping the source packages and the other binaries built from the source. I assume it is possible, please tell me if I am wrong. Please remove these two *binary* packages from both unstable and testing: gnutls-bin [mips mipsel] 3.0.22-3+really2.12.20-6 guile-gnutls [mips mipsel] 3.0.22-3+really2.12.20-6 Rationale I want gnutls26/2.12.23-5 to propagate to testing ASAP due to #709301. This is currently blocked by the missing build of gnutls28/3.0.22-4 on mips/mipsel which would provide up to date gnutls-bin and guile-gnutls binary packages. mips/mipsel therefore currently only has the old version of gnutls-bin and guile-gnutls (3.0.22-3+really2.12.20-6, built from gnutls26/2.12.20-6) and the transition is blocked. After the package removal the following should happen automatically: * libtasn1-3 2.14-3 enters testing, * gnutls28 3.0.22-4 enters testing, * gnutls26 2.12.23-5 enters testing. The build error on mips/mipsel is caused by toolchain breakage on these archs. See http://article.gmane.org/gmane.linux.debian.ports.mips/7506 thanks, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gnutls-bin | 3.0.22-3+really2.12.20-6 | mips, mipsel --- Reason --- ROM; blocks gnutls26 propagation to testing -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors (ftp.debian.org included) until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 709...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/709885 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)---End Message---
Bug#666835: marked as done (libapache-mod-random: sourceful transition towards Apache 2.4)
Your message dated Sun, 02 Jun 2013 10:03:07 + with message-id e1uj57z-0006il...@franck.debian.org and subject line Bug#710771: Removed package(s) from unstable has caused the Debian Bug report #666835, regarding libapache-mod-random: sourceful transition towards Apache 2.4 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.) -- 666835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libapache-mod-random Severity: important User: debian-apa...@lists.debian.org Usertags: apache24transition Dear maintainer, your package libapache-mod-random is provding an Apache2 web server module. We're upgrading Apache to the new upstream version 2.4 [1] (tracked as transition bug #661958). This requires all modules to be rebuilt due to ABI changes. Thus, you need to rebuild and reupload your Apache2 module package in a version compatible to our new package available in experimental [2]. Please note it is not enough to simply rebuild the module - it needs some adaptions in the module package metadata. We have written packaging guidelines for our reverse dependencies [3]. Please read it carefully, it should be able to answer most of your questions. Do also look at dh_apache2 (available through the dh-apache2 package) which can simplify packaging Apache2 modules. In short, we want to highlight these changes you need to be aware of. * APIs changed for some cases [3]. Chances are your module needs some adaptions, please get in touch with upstream or us if you need help to port your module to Apache 2.4. * MPM packages are gone. You cannot depend or conflict with a particular MPM anymore. If your module does not work with a particular module, make sure to make it abort with an error if loaded together with an incompatible MPM. You can use our apache2-maintscript-helper [4] to switch to the MPM of your choice in your maintainer scripts. * Do not build-depend on apache2-threaded-dev or apache2-prefork-dev anymore. Just like MPMs are gone, are our MPM -dev packages as well. All modules need to simply build-depend on apache2-dev. * Do NOT depend on apache2, apache2-common or any other real apache2 package in your binary module package. Depend on our virtual apache2-api-20120211 package only! * Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our apache2-maintscript-helper [3] instead. This is required to get a uniform and stateful handling of all Apache2 modules. You can look at our Apache 2.4 packaging hints [5] for hands-on tutorials. Please note: This bug is filed as important for now. As the time goes by we plan make it a release critical severity. In the consequences your module either needs an update or is going to be removed from Wheezy. For the time being please tag the bug as pending as soon as you have a package ready. We strongly recommend that at least maintainers of complex module packages make an upload to experimental as well. Of course, uploading simple modules to experimental is welcome, too. [1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html [2] http://packages.debian.org/search?keywords=apache2searchon=sourcenamesexact=1suite=allsection=all [3] http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next [4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html [5] http://wiki.debian.org/Apache/PackagingFor24 ---End Message--- ---BeginMessage--- Version: 2.1-1+rm Dear submitter, as the package libapache-mod-random has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/710771 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)---End Message---
Bug#666857: marked as done (libapache-mod-layout: sourceful transition towards Apache 2.4)
Your message dated Sun, 02 Jun 2013 10:05:18 + with message-id e1uj5a6-0006yd...@franck.debian.org and subject line Bug#710772: Removed package(s) from unstable has caused the Debian Bug report #666857, regarding libapache-mod-layout: sourceful transition towards Apache 2.4 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.) -- 666857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libapache-mod-layout Severity: important User: debian-apa...@lists.debian.org Usertags: apache24transition Dear maintainer, your package libapache-mod-layout is provding an Apache2 web server module. We're upgrading Apache to the new upstream version 2.4 [1] (tracked as transition bug #661958). This requires all modules to be rebuilt due to ABI changes. Thus, you need to rebuild and reupload your Apache2 module package in a version compatible to our new package available in experimental [2]. Please note it is not enough to simply rebuild the module - it needs some adaptions in the module package metadata. We have written packaging guidelines for our reverse dependencies [3]. Please read it carefully, it should be able to answer most of your questions. Do also look at dh_apache2 (available through the dh-apache2 package) which can simplify packaging Apache2 modules. In short, we want to highlight these changes you need to be aware of. * APIs changed for some cases [3]. Chances are your module needs some adaptions, please get in touch with upstream or us if you need help to port your module to Apache 2.4. * MPM packages are gone. You cannot depend or conflict with a particular MPM anymore. If your module does not work with a particular module, make sure to make it abort with an error if loaded together with an incompatible MPM. You can use our apache2-maintscript-helper [4] to switch to the MPM of your choice in your maintainer scripts. * Do not build-depend on apache2-threaded-dev or apache2-prefork-dev anymore. Just like MPMs are gone, are our MPM -dev packages as well. All modules need to simply build-depend on apache2-dev. * Do NOT depend on apache2, apache2-common or any other real apache2 package in your binary module package. Depend on our virtual apache2-api-20120211 package only! * Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our apache2-maintscript-helper [3] instead. This is required to get a uniform and stateful handling of all Apache2 modules. You can look at our Apache 2.4 packaging hints [5] for hands-on tutorials. Please note: This bug is filed as important for now. As the time goes by we plan make it a release critical severity. In the consequences your module either needs an update or is going to be removed from Wheezy. For the time being please tag the bug as pending as soon as you have a package ready. We strongly recommend that at least maintainers of complex module packages make an upload to experimental as well. Of course, uploading simple modules to experimental is welcome, too. [1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html [2] http://packages.debian.org/search?keywords=apache2searchon=sourcenamesexact=1suite=allsection=all [3] http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next [4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html [5] http://wiki.debian.org/Apache/PackagingFor24 ---End Message--- ---BeginMessage--- Version: 5.1-1+rm Dear submitter, as the package libapache-mod-layout has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/710772 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)---End Message---
Bug#709854: marked as done (libewf: FTBFS: possibly undefined macro: AC_CHECK_HEADERS)
Your message dated Sun, 02 Jun 2013 10:19:58 + with message-id e1uj5oi-00041m...@franck.debian.org and subject line Bug#709854: fixed in libewf 20130416-2 has caused the Debian Bug report #709854, regarding libewf: FTBFS: possibly undefined macro: AC_CHECK_HEADERS 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.) -- 709854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libewf Version: 20130416-1 Severity: serious Justification: fails to build from source Builds of libewf in minimal environments (as on the autobuilders) have been failing when trying to refresh the generated portions of its build system: libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' configure.ac:217: error: possibly undefined macro: AC_CHECK_HEADERS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1 dh_autoreconf: autoreconf -f -i returned exit code 1 make: *** [build-arch] Error 2 This error is very odd, as AC_CHECK_HEADERS is a standard Autoconf macro. A quick search for it suggests that the real problem may be failing to declare a build dependency on pkg-config: http://lists.freedesktop.org/archives/harfbuzz/2012-June/002086.html Could you please look into it? You can use pbuilder or the like to obtain suitably minimal build environments. Thanks! ---End Message--- ---BeginMessage--- Source: libewf Source-Version: 20130416-2 We believe that the bug you reported is fixed in the latest version of libewf, 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 709...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Chifflier pol...@debian.org (supplier of updated libewf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 11:52:16 +0200 Source: libewf Binary: libewf2 libewf-dbg libewf-dev ewf-tools Architecture: source amd64 Version: 20130416-2 Distribution: unstable Urgency: low Maintainer: Debian Forensics forensics-de...@lists.alioth.debian.org Changed-By: Pierre Chifflier pol...@debian.org Description: ewf-tools - collection of tools for reading and writing EWF files libewf-dbg - library with support for Expert Witness Compression Format (debug libewf-dev - support for Expert Witness Compression format (development) libewf2- library with support for Expert Witness Compression Format Closes: 691530 709854 Changes: libewf (20130416-2) unstable; urgency=low . * Add pkg-config to build-depends (Closes: #709854) * This is the most recent version (Closes: #691530) Checksums-Sha1: 800f4b89780e426dacefc877a6b2353b5553ab2f 1903 libewf_20130416-2.dsc 963ebd695bbc6793fbad279f05976befdd12395f 11667 libewf_20130416-2.debian.tar.gz 1d85df861297fb1f1257392449f7ba76f4f91f63 596382 libewf2_20130416-2_amd64.deb 9e40521109c3a96e5604c73b449b3d2dfe6e18c4 2794454 libewf-dbg_20130416-2_amd64.deb 857a94abd16aa042a9840e196dd246ab9eb1b1ab 682680 libewf-dev_20130416-2_amd64.deb 12fc08858d750a4fdd8696efe6f84a9182190983 3028518 ewf-tools_20130416-2_amd64.deb Checksums-Sha256: 4031364e4bcbccfa46a7856a5ac07ebc3a00a230bd8a20c6114c8602f28cf396 1903 libewf_20130416-2.dsc 0e1cf8c37d1615784280bfa10ca60560674b87306295be5587a3212c2b2eae77 11667 libewf_20130416-2.debian.tar.gz 9448490180f3d7f1b9dda9031f942c79cb46769a6c38013b90969a9056ba8079 596382 libewf2_20130416-2_amd64.deb 97540b1949cdbcb701f25c1cf3bb17760aec0d1ea4044e1764d3f1249d606aee 2794454 libewf-dbg_20130416-2_amd64.deb f1a0e77ea7d3491f3db9b7da5778ff8ceb2769fff8011abfc594fb11d679035e 682680 libewf-dev_20130416-2_amd64.deb 97ea2dd710ef1e0cc6a03cb5c187294fe1b637c6e41a6d5288dfcc7a79186755 3028518 ewf-tools_20130416-2_amd64.deb Files:
Bug#701381: busybox: diff for NMU version 1:1.20.0-8.1
tags 701381 + pending
thanks
Dear maintainer,
I've prepared an NMU for busybox (versioned as 1:1.20.0-8.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards,
Aron
diff -Nru busybox-1.20.0/debian/changelog busybox-1.20.0/debian/changelog
--- busybox-1.20.0/debian/changelog 2013-03-02 20:42:49.0 +0800
+++ busybox-1.20.0/debian/changelog 2013-06-02 18:04:24.0 +0800
@@ -1,3 +1,10 @@
+busybox (1:1.20.0-8.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * eglibc-2.17.patch - backport upstream patch (Closes: #701381)
+
+ -- Aron Xu a...@debian.org Sun, 02 Jun 2013 17:59:36 +0800
+
busybox (1:1.20.0-8) unstable; urgency=low
* grep-fix-grep--Fw-not-respecting-the--w-option.patch - implement
diff -Nru busybox-1.20.0/debian/patches/eglibc-2.17.patch busybox-1.20.0/debian/patches/eglibc-2.17.patch
--- busybox-1.20.0/debian/patches/eglibc-2.17.patch 1970-01-01 08:00:00.0 +0800
+++ busybox-1.20.0/debian/patches/eglibc-2.17.patch 2013-06-02 17:56:16.0 +0800
@@ -0,0 +1,81 @@
+From c5fe9f7b723f949457263ef8e22ab807d5b549ce Mon Sep 17 00:00:00 2001
+From: Mike Frysinger vap...@gentoo.org
+Date: Fri, 06 Jul 2012 03:19:09 +
+Subject: include sys/resource.h where needed
+
+We use functions from sys/resource.h in misc applets, but don't include
+the header. This breaks building with newer glibc versions, so add the
+include where needed.
+
+Signed-off-by: Mike Frysinger vap...@gentoo.org
+---
+--- a/loginutils/passwd.c
b/loginutils/passwd.c
+@@ -15,6 +15,7 @@
+
+ #include libbb.h
+ #include syslog.h
++#include sys/resource.h /* setrlimit */
+
+ static void nuke_str(char *str)
+ {
+--- a/miscutils/time.c
b/miscutils/time.c
+@@ -16,6 +16,7 @@
+ //usage: \n -v Verbose
+
+ #include libbb.h
++#include sys/resource.h /* getrusage */
+
+ /* Information on the resources used by a child process. */
+ typedef struct {
+--- a/networking/inetd.c
b/networking/inetd.c
+@@ -165,6 +165,7 @@
+ //usage: \n (default: 0 - disabled)
+
+ #include syslog.h
++#include sys/resource.h /* setrlimit */
+ #include sys/un.h
+
+ #include libbb.h
+--- a/networking/ntpd.c
b/networking/ntpd.c
+@@ -46,6 +46,7 @@
+ #include libbb.h
+ #include math.h
+ #include netinet/ip.h /* For IPTOS_LOWDELAY definition */
++#include sys/resource.h /* setpriority */
+ #include sys/timex.h
+ #ifndef IPTOS_LOWDELAY
+ # define IPTOS_LOWDELAY 0x10
+--- a/networking/ntpd_simple.c
b/networking/ntpd_simple.c
+@@ -7,6 +7,7 @@
+ */
+ #include libbb.h
+ #include netinet/ip.h /* For IPTOS_LOWDELAY definition */
++#include sys/resource.h /* setpriority */
+ #ifndef IPTOS_LOWDELAY
+ # define IPTOS_LOWDELAY 0x10
+ #endif
+--- a/runit/chpst.c
b/runit/chpst.c
+@@ -91,6 +91,7 @@
+ //usage: \n a SIGXCPU after N seconds
+
+ #include libbb.h
++#include sys/resource.h /* getrlimit */
+
+ /*
+ Five applets here: chpst, envdir, envuidgid, setuidgid, softlimit.
+--- a/shell/shell_common.c
b/shell/shell_common.c
+@@ -18,6 +18,7 @@
+ */
+ #include libbb.h
+ #include shell_common.h
++#include sys/resource.h /* getrlimit */
+
+ const char defifsvar[] ALIGN1 = IFS= \t\n;
+
diff -Nru busybox-1.20.0/debian/patches/series busybox-1.20.0/debian/patches/series
--- busybox-1.20.0/debian/patches/series 2013-03-01 16:54:07.0 +0800
+++ busybox-1.20.0/debian/patches/series 2013-06-02 17:51:44.0 +0800
@@ -33,3 +33,5 @@
dont-force-no-alignment-for-s390.patch
stop-checking-ancient-kernel-version.patch
+
+eglibc-2.17.patch
signature.asc
Description: Digital signature
Bug#701744: frag is bigger than frame on 3.2.0-4-amd64
Also seeing this bug on wheezy 3.2.0-4-amd64. It ended up completely killing the Xen stack, not just the vif it disabled. New vifs couldn't be created, Xen couldn't create any new VMs (out of memory despite having 50G free). Jun 2 07:06:16 fifi kernel: [5078695.913503] vif vif-14-0: Xa9feca42: Frag is bigger than frame. Jun 2 07:06:16 fifi kernel: [5078695.913518] vif vif-14-0: Xa9feca42: fatal error; disabling device Jun 2 07:06:16 fifi kernel: [5078695.913566] BUG: unable to handle kernel NULL pointer dereference at 08b8 Jun 2 07:06:16 fifi kernel: [5078695.913600] IP: [8134d981] _raw_spin_lock_irqsave+0xe/0x25 Jun 2 07:06:16 fifi kernel: [5078695.913623] PGD f1d4ed067 PUD a8faf5067 PMD 0 Jun 2 07:06:16 fifi kernel: [5078695.913687] Oops: 0002 [#1] SMP Jun 2 07:06:16 fifi kernel: [5078695.913712] CPU 3 Marek Isalski Technical Director, Faelix Limited, http://faelix.net/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: busybox: diff for NMU version 1:1.20.0-8.1
Processing commands for cont...@bugs.debian.org: tags 701381 + pending Bug #701381 [src:busybox] busybox: ftbfs with eglibc-2.17 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 701381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701381 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: tagging 710591, tagging 710767
Processing commands for cont...@bugs.debian.org: tags 710591 + pending Bug #710591 [libreoffice] libreoffice: Missing .desktop files for all LibreOffice programs. Added tag(s) pending. tags 710767 + pending Bug #710767 [libreoffice-dev] libreoffice-dev: fails to upgrade from 'sid' - trying to overwrite /usr/lib/libreoffice/program/gengal.bin Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 710591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710591 710767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710767 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#701381: busybox: diff for NMU version 1:1.20.0-8.1
02.06.2013 14:25, Aron Xu wrote: Dear maintainer, I've prepared an NMU for busybox (versioned as 1:1.20.0-8.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I'm still waiting for the stable updates for busybox which is currently in testing, see #702278. It is more important at this time to get things fixed for wheezy than for the next release of debian. Thanks, /mjt\ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 710597 in 1.7-1
Processing commands for cont...@bugs.debian.org: notfound 710597 1.7-1 Bug #710597 [pymongo] pymongo: CVE-2013-2132: null pointer when decoding invalid DBRef There is no source info for the package 'pymongo' at version '1.7-1' with architecture '' Unable to make a source version for version '1.7-1' No longer marked as found in versions 1.7-1. thanks Stopping processing here. Please contact me if you need assistance. -- 710597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710597 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#707350: marked as done (indicator-messages: FTBFS: messages-service.c:1524:2: error: 'g_type_init' is deprecated (declared at /usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declara
Your message dated Sun, 02 Jun 2013 10:34:27 + with message-id e1uj5cj-0003tk...@franck.debian.org and subject line Bug#707350: fixed in indicator-messages 0.6.0-1.1 has caused the Debian Bug report #707350, regarding indicator-messages: FTBFS: messages-service.c:1524:2: error: 'g_type_init' is deprecated (declared at /usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declarations] 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.) -- 707350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: indicator-messages Version: 0.6.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./src -I.. -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/libdbusmenu-gtk-0.4 -I/usr/include/libindicator-0.4 -I/usr/include/libindicate-0.7-Wall -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -Werror -DG_LOG_DOMAIN=\Indicator-Messages\ -DSTATUS_PROVIDER_DIR=\/usr/lib/indicator-messages/status-providers/1\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o indicator_messages_service-messages-service.o `test -f 'messages-service.c' || echo '/«PKGBUILDDIR»/./src/'`messages-service.c /«PKGBUILDDIR»/./src/messages-service.c: In function 'main': /«PKGBUILDDIR»/./src/messages-service.c:1524:2: error: 'g_type_init' is deprecated (declared at /usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[4]: *** [indicator_messages_service-messages-service.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/indicator-messages_0.6.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: indicator-messages Source-Version: 0.6.0-1.1 We believe that the bug you reported is fixed in the latest version of indicator-messages, 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 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher sramac...@debian.org (supplier of updated indicator-messages package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Jun 2013 12:09:30 +0200 Source: indicator-messages Binary: indicator-messages indicator-messages-gtk2 libindicator-messages-status-provider1 libindicator-messages-status-provider-dev indicator-status-provider-mc5 indicator-status-provider-pidgin indicator-status-provider-telepathy indicator-status-provider-emesene Architecture: source amd64 Version: 0.6.0-1.1 Distribution: unstable Urgency: low Maintainer: The Ayatana Packagers pkg-ayatana-de...@lists.alioth.debian.org Changed-By: Sebastian Ramacher sramac...@debian.org Description: indicator-messages - indicator that collects messages that need a response indicator-messages-gtk2 - indicator that collects messages that need a response indicator-status-provider-emesene - indicator-messages status provider for emesene indicator-status-provider-mc5 - indicator-messages status provider for telepathy mission-control- indicator-status-provider-pidgin - indicator-messages status provider
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 710163 + pending Bug #710163 [python-pip] CVE-2013-1629: Man in the middle possibility Added tag(s) pending. tag 710134 + pending Bug #710134 [python-pip] python-pip: Please include the CHANGES.txt in /usr/share/doc/python-pip Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 710134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710134 710163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710163 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#706764: marked as done (assaultcube-data: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man6/assaultcube-server.6.gz)
Your message dated Sun, 02 Jun 2013 11:02:05 + with message-id e1uj633-0003ob...@franck.debian.org and subject line Bug#706764: fixed in assaultcube-data 1.1.0.4+repack1-2.1~deb7u1 has caused the Debian Bug report #706764, regarding assaultcube-data: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man6/assaultcube-server.6.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: assaultcube-data Version: 1.1.0.4+repack1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace assaultcube-data 1.0.4+repack1-1 (using .../assaultcube-data_1.1.0.4+repack1-2_all.deb) ... Unpacking replacement assaultcube-data ... dpkg: error processing /var/cache/apt/archives/assaultcube-data_1.1.0.4+repack1-2_all.deb (--unpack): trying to overwrite '/usr/share/man/man6/assaultcube-server.6.gz', which is also in package assaultcube 1.0.4repack1-3 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to replace assaultcube 1.0.4repack1-3 (using .../assaultcube_1.1.0.4+dfsg2-1_i386.deb) ... Unpacking replacement assaultcube ... Adding Breaks: assaultcube ( 1.1.0.4+dfsg2-1) Replaces: assaultcube ( 1.1.0.4+dfsg2-1) should fix this issue. cheers, Andreas assaultcube_None.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: assaultcube-data Source-Version: 1.1.0.4+repack1-2.1~deb7u1 We believe that the bug you reported is fixed in the latest version of assaultcube-data, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 706...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated assaultcube-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Jun 2013 22:48:53 +0200 Source: assaultcube-data Binary: assaultcube-data Architecture: source all Version: 1.1.0.4+repack1-2.1~deb7u1 Distribution: wheezy Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: assaultcube-data - data files and documentation for AssaultCube Closes: 706764 Changes: assaultcube-data (1.1.0.4+repack1-2.1~deb7u1) wheezy; urgency=low . * Non-maintainer upload. * Rebuild for wheezy. . assaultcube-data (1.1.0.4+repack1-2.1) unstable; urgency=low . * Non-maintainer upload. * Fix fails to upgrade from squeeze - trying to overwrite /usr/share/man/man6/assaultcube-server.6.gz: Add versioned Breaks/Replaces on assaultcube. Thanks to Andreas Beckmann for the bug report and patch. (Closes: #706764) Checksums-Sha1: efc09880c3b0150725e66c1c41037f58efcd37f5 2171 assaultcube-data_1.1.0.4+repack1-2.1~deb7u1.dsc dc8e7ca31b03f7dc47a80d84dd63ea12c6ec70e1 25478 assaultcube-data_1.1.0.4+repack1-2.1~deb7u1.debian.tar.gz 15e039f21a33e9ff6164392e82e212209145465a 45852852 assaultcube-data_1.1.0.4+repack1-2.1~deb7u1_all.deb Checksums-Sha256: f7363b61dca968027873984942ad556b8fdb416db6bb6baa85c330286a0c8c81 2171 assaultcube-data_1.1.0.4+repack1-2.1~deb7u1.dsc f8bfad945cfb5455dc3ea2c289df6fef4030a60557bab09dca76990eed71c5ef 25478 assaultcube-data_1.1.0.4+repack1-2.1~deb7u1.debian.tar.gz b924bd1c8616945fd2e08869b8b7a8a009522f33a07c4d7bc00973ce9c8f9efc 45852852 assaultcube-data_1.1.0.4+repack1-2.1~deb7u1_all.deb Files: f23a70709baf9f9314d514d0b07a3c6f 2171 non-free/games optional assaultcube-data_1.1.0.4+repack1-2.1~deb7u1.dsc 5cbc74e19d2fdc114492c3840e752a72 25478 non-free/games optional
Bug#709382: Built-Using, libgcc, and libc_nonshared
* Russ Allbery: Clearly no one else in the world is worrying about this; there's lots of GPLv2-only software out there and all the distributions are happily distributing binaries built with current GCC without worrying about this. I'm not sure to what extent we can use that as an excuse, though. FYI, this is [gnu.org #435945], filed about three years ago. I haven't received any substantiated reaction from the FSF. A similar thing must happened during the transition from GPLv1 to GPLv2 and would still apply to GPLv1 software. Nowadays, we could switch to compiler-rt after porting it to more architectures. Or we could branch the old version of libgcc with the permissive linking exception and maintain that, asking subsequent FSF contributors to relicense their patches under the old terms (which they can do under their copyright assignment contract with the FSF, I think). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707226: [pkg-wine-party] Bug#707226: package wine does not install wine on amd64
* email@arcor.de: Exept, wine-party is resposible for a package that currently suffers from not being able to fulfill the dependency and simply hasn't put the workaround's (hello world message) in the right place yet. As long as we don't have cross-architecture dependencies, perhaps a Breaks: q4wine header would be an improvement. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libnet-server-perl package
Processing commands for cont...@bugs.debian.org: tag 708180 + pending Bug #708180 [libnet-server-perl] applications die() because of SIGCHLD vs. SIGCLD confusion Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 708180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708180 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#708180: Pending fixes for bugs in the libnet-server-perl package
tag 708180 + pending thanks Some bugs in the libnet-server-perl package are closed in revision e1293a51d216474c06d52a9468825073bc968ea7 in branch 'master' by Xavier Guimard The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libnet-server-perl.git;a=commitdiff;h=e1293a5 Commit message: Fix applications die() because of SIGCHLD vs. SIGCLD confusion using a patch Closes: #708180 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710784: webalizer: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/webalizer/examples/sample.conf.gz
Package: webalizer Version: 2.23.05-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package webalizer. (Reading database ... 6727 files and directories currently installed.) Unpacking webalizer (from .../webalizer_2.23.05-1_amd64.deb) ... Setting up webalizer (2.23.05-1) ... /var/www/webalizer created gzip: /usr/share/doc/webalizer/examples/sample.conf.gz: No such file or directory dpkg: error processing webalizer (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: webalizer Cheers, Andreas webalizer_2.23.05-1.log.gz Description: GNU Zip compressed data
Processed: tagging 709048
Processing commands for cont...@bugs.debian.org: tags 709048 + patch Bug #709048 [libgd-gd2-perl] libgd-gd2-perl: fails tests with current libgd2 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 709048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709048 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#710597: marked as done (pymongo: CVE-2013-2132: null pointer when decoding invalid DBRef)
Your message dated Sun, 02 Jun 2013 11:48:19 + with message-id e1uj6ln-0007my...@franck.debian.org and subject line Bug#710597: fixed in pymongo 2.5.2-1 has caused the Debian Bug report #710597, regarding pymongo: CVE-2013-2132: null pointer when decoding invalid DBRef 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.) -- 710597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pymongo Severity: grave Tags: security upstream patch Hi, the following vulnerability was published for pymongo. CVE-2013-2132[0]: null pointer when decoding invalid DBRef See [1] for details and upstream bugreport including reproducer for the issue. A patch was applied upstream in [2]. 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] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2132 http://security-tracker.debian.org/tracker/CVE-2013-2132 [1] https://jira.mongodb.org/browse/PYTHON-532 [2] https://github.com/mongodb/mongo-python-driver/commit/a060c15ef87e0f0e72974c7c0e57fe811bbd06a2 I have checked 2.2-4, which seem affected. Please adjust the affected versions in the BTS as needed. Thanks for your work and regards, Salvatore ---End Message--- ---BeginMessage--- Source: pymongo Source-Version: 2.5.2-1 We believe that the bug you reported is fixed in the latest version of pymongo, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Ceratto federico.cera...@gmail.com (supplier of updated pymongo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 11:11:10 +0100 Source: pymongo Binary: python-pymongo python3-pymongo python-pymongo-ext python-pymongo-doc python-gridfs python3-gridfs python-bson python3-bson python-bson-ext Architecture: source amd64 all Version: 2.5.2-1 Distribution: unstable Urgency: high Maintainer: Federico Ceratto federico.cera...@gmail.com Changed-By: Federico Ceratto federico.cera...@gmail.com Description: python-bson - Python implementation of BSON for MongoDB python-bson-ext - C-coded extension to the python-bson package python-gridfs - Python implementation of GridFS for MongoDB python-pymongo - Python interface to the MongoDB document-oriented database python-pymongo-doc - Python interface to the MongoDB document-oriented database (docum python-pymongo-ext - C-coded extension to the python-pymongo package python3-bson - Python3 implementation of BSON for MongoDB python3-gridfs - Python3 implementation of GridFS for MongoDB python3-pymongo - Python3 interface to the MongoDB document-oriented database Closes: 710597 Changes: pymongo (2.5.2-1) unstable; urgency=high . * New upstream release. (Closes: #710597) * Releasing to unstable. Checksums-Sha1: 0f4919a56f10793834e9f49e8f8f08e6c7298d21 1793 pymongo_2.5.2-1.dsc 2ef234fcae46328e95d8dfbc9fb08fbe50893a68 305155 pymongo_2.5.2.orig.tar.gz 4c0507a78a33052b4a5459002545a52066682c39 4317 pymongo_2.5.2-1.debian.tar.gz 8d22a8fcfe77eb48a116a6f49a4bded1be00685c 110042 python-pymongo_2.5.2-1_amd64.deb adaee6b08f05f8d7efe27f89e7afb41a6c9d5d3e 107872 python3-pymongo_2.5.2-1_amd64.deb 18fdf1c9beb6519909efb7548d6d67bf84864f50 25086 python-pymongo-ext_2.5.2-1_amd64.deb bc83719c0ba9ff9cd3e57caec7ff54fe0b8a507e 1096406 python-pymongo-doc_2.5.2-1_all.deb 77192b0e1e63040c4f73737df5df6a4f6834c3f5 24364 python-gridfs_2.5.2-1_all.deb a5010c16c5512cfd4392831ed6f7fcad453c6372 24618 python3-gridfs_2.5.2-1_all.deb 40f21c96e6fb26c65abc8768914479941800d780 32964 python-bson_2.5.2-1_amd64.deb d169dfe1f7652c0ef5385bac15d1cbdb5ca9 33058 python3-bson_2.5.2-1_amd64.deb 7b37dc6d7714dbba75912a802acf1c2baf12e561 66524 python-bson-ext_2.5.2-1_amd64.deb Checksums-Sha256: 0b299aea8393351379319fc1b58c6dca2dc19b74fffdd9ce2e0269fde1b127ed 1793 pymongo_2.5.2-1.dsc 641e8e7d19abdd43d5e8ee2f14b82632d7d1deb6cb1b05a82b68b0711b31c307 305155 pymongo_2.5.2.orig.tar.gz
Bug#707821: sl-modem-source: fails to upgrade from squeeze [i386]
On Sun, Jun 02, 2013 at 01:06:52AM +0200, Andreas Beckmann wrote: If that gets approved, I would upload a NMU with a delay up to approximately Wednesday evening. Of course you are welcome to do a maintainer upload instead. Please go ahead with the upload. I have all my changes in git in a wheezy branch - shall I push that to the repository? (cherry-picked two of your commits + a changelog entry) Sure. Could you also upload an i386 build for unstable ? Since I am a DM, I cannot do binary only uploads. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Processed: [5ae3fa9] Fix for Bug#706909 committed to git
Processing commands for cont...@bugs.debian.org:
tags 706909 + pending
Bug #706909 {Done: Giuseppe Iuculano iucul...@debian.org} [smartmontools]
smartmontools: updated drivedb.h should go to /var
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
706909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706909
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#706909: [5ae3fa9] Fix for Bug#706909 committed to git
tags 706909 + pending thanks Hello, The following change has been committed for this bug by Giuseppe Iuculano iucul...@debian.org on Sun, 2 Jun 2013 10:08:14 +0200. The fix will be in the next upload. = Use /var/lib/smartmontools/drivedb for drivedb.h updates Closes: #706909 = You can check the diff of the fix at: http://git.debian.org/?p=collab-maint/smartmontools.git;a=commitdiff;h=5ae3fa9 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
HI, II think I figured out. On Sat, Jun 01, 2013 at 01:21:57AM +0800, Aron Xu wrote: On Wed, May 29, 2013 at 8:47 PM, Osamu Aoki os...@debian.org wrote: I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu Seems GTK_IM_MODULE still show up as xim, and QT4_IM_MODULE is correct. But I don't know what's wrong with GTK. I tried to add some echo to 22_fcitx.rc and it shows that the two `ls` command returns nothing to the variable, while it works for Qt... Sorry, I overlooked important message here. What im-config does. $ ls /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.sols /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so ls: cannot access /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.sols: No such file or directory /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so $ ls /usr/lib/gtk-3.0/*/immodules/im-fcitx.so ls: cannot access /usr/lib/gtk-3.0/*/immodules/im-fcitx.so: No such file or directory But where are they really $ dpkg -L fcitx-frontend-gtk2 /. /usr /usr/share /usr/share/doc /usr/share/doc/fcitx-frontend-gtk2 /usr/share/doc/fcitx-frontend-gtk2/changelog.Debian.gz /usr/share/doc/fcitx-frontend-gtk2/changelog.gz /usr/share/doc/fcitx-frontend-gtk2/copyright /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/gtk-2.0 /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0 /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so $ dpkg -L fcitx-frontend-gtk3 /. /usr /usr/share /usr/share/doc /usr/share/doc/fcitx-frontend-gtk3 /usr/share/doc/fcitx-frontend-gtk3/changelog.Debian.gz /usr/share/doc/fcitx-frontend-gtk3/changelog.gz /usr/share/doc/fcitx-frontend-gtk3/copyright /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/gtk-3.0 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to request-tracker4, tagging 708950, tagging 708101
Processing commands for cont...@bugs.debian.org: #request-tracker4 (4.0.13-1) UNRELEASED; urgency=low # # * Add Build-Depends on libterm-readkey-perl, and don't run #t/web/installer.t (tests functionality not used in the Debian #package (Closes: #708950) # * Remove rt-validate-aliases alternative in prerm (Closes: #708101) # limit source request-tracker4 Limiting to bugs with field 'source' containing at least one of 'request-tracker4' Limit currently set to 'source':'request-tracker4' tags 708950 + pending Bug #708950 [request-tracker4] request-tracker4: fails to build (failing test suite) Added tag(s) pending. tags 708101 + pending Bug #708101 [request-tracker4] request-tracker4: leaves alternatives after purge: /usr/sbin/rt-validate-aliases Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 708101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708101 708950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708950 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#710651: [Pkg-gnupg-maint] Bug#710651: gnupg: FTBFS: ../../util/regcomp.c:528:20: error: unknown type name 'preg'
On Sat, June 1, 2013 18:38, Andrey Rahmatullin wrote:
On Fri, May 31, 2013 at 08:37:24PM +0200, David Suárez wrote:
i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../../util -I.. -I..
-I../../include -I../../intl-g -Os -fno-omit-frame-pointer -Wall
-Wno-pointer-sign -MT regex.o -MD -MP -MF .deps/regex.Tpo -c -o
regex.o ../../util/regex.c
In file included from ../../util/regex.c:50:0:
../../util/regcomp.c:528:20: error: unknown type name 'preg'
../../util/regcomp.c:528:26: error: unknown type name 'errbuf'
../../util/regcomp.c:528:34: error: unknown type name 'errbuf_size'
../../util/regcomp.c:533:1: error: expected identifier or '(' before
'{' token
The code:
size_t
regerror (errcode, preg, errbuf, errbuf_size)
int errcode;
const regex_t *preg;
char *errbuf;
size_t errbuf_size;
{
So it looks like the i686-w64-mingw32-gcc used doesn't support KR
function
definitions?
I'm adding Didier to Cc.
Thijs
Didier Raboud o...@debian.org
--
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: tag 710790 + pending Bug #710790 [src:pythonmagick] pythonmagick: FTBFS: wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 710790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710790 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: lxc
Processing commands for cont...@bugs.debian.org:
found 709454 0.9.0-5
Bug #709454 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[lxc] ftbfs on sparc
Marked as found in versions lxc/0.9.0-5.
notfound 709454 0.9.0~alpha3-2
Bug #709454 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[lxc] ftbfs on sparc
No longer marked as found in versions lxc/0.9.0~alpha3-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
709454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709454
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#701381: busybox: diff for NMU version 1:1.20.0-8.1
On Sun, Jun 2, 2013 at 6:29 PM, Michael Tokarev m...@tls.msk.ru wrote: 02.06.2013 14:25, Aron Xu wrote: Dear maintainer, I've prepared an NMU for busybox (versioned as 1:1.20.0-8.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I'm still waiting for the stable updates for busybox which is currently in testing, see #702278. It is more important at this time to get things fixed for wheezy than for the next release of debian. Thanks, /mjt\ 1:1.20.0-8 has migrated to testing, do you think it's okay to keep -8.1 in unstable by keeping #701381 open until the pu is worked out, or you prefer to remove it from DELAYED? Regards, Aron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. Regards, Aron -- 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: tag 710790 + pending Bug #710790 [src:pythonmagick] pythonmagick: FTBFS: wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory Ignoring request to alter tags of bug #710790 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 710790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710790 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#710797: FTBFS on hurd-i386 because MAXHOSTNAMELEN is undefined
Package: bzflag Version: 2.4.2+ds1-2 Severity: serious Tags: upstream confirmed Justification: fails to build from source (but built successfully in the past) bzflag doesn't build on hurd-i386 because MAXHOSTNAMELEN is undefined. https://buildd.debian.org/status/fetch.php?pkg=bzflagarch=hurd-i386ver=2.4.2+ds1-2stamp=1369627289 (This bug is reported to help me keep track of it). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bzflag depends on: ii bzflag-client 2.4.2+ds1-2 ii bzflag-server 2.4.2+ds1-2 bzflag recommends no packages. bzflag suggests no packages. -- no debconf information signature.asc Description: Digital signature
Bug#710590: A local rebuild of the ufraw source package solved the problem for me
I was hit by this bug too. It affects ufraw as well as gimp-ufraw. It may also affect ufraw-batch but I haven't tested. I have rebuild the packages from source on my amd64 box, reinstalled with dpkg -i, and there's no more segmentation fault. Thierry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 683502
Processing commands for cont...@bugs.debian.org: tags 683502 + pending Bug #683502 [jedit] jedit: Fix FTBFS when default java implementation changes Bug #706777 [jedit] jedit should depend on Java 7 if available Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 683502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683502 706777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706777 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: severity of 710797 is important
Processing commands for cont...@bugs.debian.org: severity 710797 important Bug #710797 [bzflag] FTBFS on hurd-i386 because MAXHOSTNAMELEN is undefined Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 710797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710797 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#709921: im-config: cannot detect IM module files correctly
Hi, On Sun, Jun 02, 2013 at 09:57:46PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. I see but as I look again carefully, I may have jumped on conclusion too early. Do you have both fcitx-frontend-gtk2 and fcitx-frontend-gtk3 installed? Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
On Sun, Jun 2, 2013 at 10:31 PM, Osamu Aoki os...@debian.org wrote: Hi, On Sun, Jun 02, 2013 at 09:57:46PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. I see but as I look again carefully, I may have jumped on conclusion too early. Do you have both fcitx-frontend-gtk2 and fcitx-frontend-gtk3 installed? Of course: $ ls /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so $ ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so $ ls /usr/lib/*/qt4/plugins/inputmethods/qtim-fcitx.so /usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so $ dpkg -l | grep fcitx-frontend ii fcitx-frontend-all 1:4.2.4.1-7 all Flexible Input Method Framework - frontends metapackage ii fcitx-frontend-gtk2:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 2 IM Module frontend ii fcitx-frontend-gtk3:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 3 IM Module frontend ii fcitx-frontend-qt4:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - QT 4 IM Module frontend Thanks, Aron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701348: ftbfs not due to compiler?
Hi, according to the log file within this bug report, the failure was due to some segmentation fault in target override_dh_auto_test: and not due to an issue with gcc or eglibc. The warnings already exist in buildlogs with other versions of gcc. I could build the package with gcc4.8 and eglibc 2.17 without problem in a local VM. Do I miss anything? Best regards Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710805: eclipse-wtp: fails to build from source
Package: eclipse-wtp Version: 3.4.2-2 Severity: serious Justification: fails to build from source User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy eclipse-wtp 3.4.2-2 fails to build from source in a clean chroot. BUILD FAILED /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:111: Processing inclusion from feature org.eclipse.wst.xsl.feature: Unable to find plug-in: org.apache.commons.logging_1.0.4.qualifier. Please check the error log for more details. Thanks, Jeremy - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'raring'), (100, 'saucy-backports') -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, On Sun, Jun 02, 2013 at 10:36:25PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 10:31 PM, Osamu Aoki os...@debian.org wrote: Hi, On Sun, Jun 02, 2013 at 09:57:46PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. I see but as I look again carefully, I may have jumped on conclusion too early. Do you have both fcitx-frontend-gtk2 and fcitx-frontend-gtk3 installed? Of course: $ ls /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so $ ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so $ ls /usr/lib/*/qt4/plugins/inputmethods/qtim-fcitx.so /usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so $ dpkg -l | grep fcitx-frontend ii fcitx-frontend-all 1:4.2.4.1-7 all Flexible Input Method Framework - frontends metapackage ii fcitx-frontend-gtk2:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 2 IM Module frontend ii fcitx-frontend-gtk3:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 3 IM Module frontend ii fcitx-frontend-qt4:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - QT 4 IM Module frontend Here, I installed fcitx to wheezy while installing 0.22-2 of im-config. I do not see the problem. $ set|grep GTK GTK_IM_MODULE=fcitx $ set|grep fcitx GTK_IM_MODULE=fcitx QT4_IM_MODULE=fcitx XMODIFIERS=@im=fcitx $ dpkg -l im-config 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 Architecture Description +++-==---= ii im-config 0.22-2 all Input method configuration framew Did you restarted X session before testing? I am a bit lost Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 710805
Processing commands for cont...@bugs.debian.org: #interesting that it built before tags 710805 + confirmed Bug #710805 [eclipse-wtp] eclipse-wtp: fails to build from source Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 710805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710805 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#710790: marked as done (pythonmagick: FTBFS: wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory)
Your message dated Sun, 02 Jun 2013 15:23:40 + with message-id e1uja8c-0007x8...@franck.debian.org and subject line Bug#710790: fixed in pythonmagick 0.9.8-1 has caused the Debian Bug report #710790, regarding pythonmagick: FTBFS: wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 710790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pythonmagick Version: 0.9.7-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../../pythonmagick_src -I../config -D_FORTIFY_SOURCE=2 -IUsage: -I/usr/include -fopenmp -I/usr/include/ImageMagick -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DBOOST_PYTHON_DYNAMIC_LIB -c -o libpymagick_la-_DrawableFillRule.lo `test -f '_DrawableFillRule.cpp' || echo '../../../pythonmagick_src/'`_DrawableFillRule.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../pythonmagick_src -I../config -D_FORTIFY_SOURCE=2 -IUsage: -I/usr/include -fopenmp -I/usr/include/ImageMagick -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DBOOST_PYTHON_DYNAMIC_LIB -c ../../../pythonmagick_src/_DrawableFillRule.cpp -fPIC -DPIC -o .libs/libpymagick_la-_DrawableFillRule.o In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, from /usr/include/boost/python/args.hpp:8, from /usr/include/boost/python.hpp:11, from ../../../pythonmagick_src/_DrawableFillRule.cpp:3: /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory compilation terminated. make[3]: *** [libpymagick_la-_DrawableFillRule.lo] Error 1 The full build log is available from: http://deiv.vzpla.net/logs/2013/05/29/pythonmagick_0.9.7-2_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: pythonmagick Source-Version: 0.9.8-1 We believe that the bug you reported is fixed in the latest version of pythonmagick, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher sramac...@debian.org (supplier of updated pythonmagick 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: Sun, 02 Jun 2013 15:59:18 +0200 Source: pythonmagick Binary: python-pythonmagick Architecture: source amd64 Version: 0.9.8-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Sebastian Ramacher sramac...@debian.org Description: python-pythonmagick - Object-oriented Python interface to ImageMagick Closes: 710790 Changes: pythonmagick (0.9.8-1) unstable; urgency=low . * Team upload. . [ Sebastian Ramacher ] * New upstream release. * debian/control: - Bump Standards-Version to 3.9.4. - Bump debhelper to (= 9) for arch and indep targets. - Remove unnecessary Build-Depends autotools-dev and dpkg-dev. * debian/compat: Bump to 9. * debian/rules: - Run loops with set -e. - Call dh correctly. - No need to include /usr/share/dpkg/buildflags.mk anymore. * debian/copyright: - Update Format URL. - Merge the two debian/* sections. - Fix formatting of the ImageMagick license. - Update copyright years * debian/patches: - 001_autofoo_fixes.diff: Use python-config --includes to fix build failure. (Closes:
Bug#706777: marked as done (jedit should depend on Java 7 if available)
Your message dated Sun, 02 Jun 2013 15:20:32 + with message-id e1uja5a-0006tr...@franck.debian.org and subject line Bug#683502: fixed in jedit 5.0.0+dfsg-2 has caused the Debian Bug report #683502, regarding jedit should depend on Java 7 if available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jedit Version: 5.0~pre1+dfsg-1ubuntu1 Severity: wishlist Dear Maintainer, The jedit package (= 4.5) requires Java 6 or later to work, but now there is no choice and openjdk-6-jre must be installed. As the openjdk-7-jre is available (except Squeeze release), it should depend on it or provide alternative for both JRE versions. We can see the same situation in Ubuntu packages: https://bugs.launchpad.net/ubuntu/+source/jedit/+bug/1154951 -- System Information: Debian Release: wheezy/sid APT prefers raring-updates APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring'), (100, 'raring-backports') Architecture: i386 (i686) Kernel: Linux 3.8.0-19-generic (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages jedit depends on: ii dpkg 1.16.10ubuntu1 ii java-wrappers 0.1.25 ii openjdk-6-jre 6b27-1.12.4-1ubuntu1 jedit recommends no packages. jedit suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: jedit Source-Version: 5.0.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of jedit, 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 683...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated jedit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 07:27:24 -0700 Source: jedit Binary: jedit Architecture: source all Version: 5.0.0+dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: tony mancill tmanc...@debian.org Description: jedit - Plugin-based editor for programmers Closes: 606662 683502 Changes: jedit (5.0.0+dfsg-2) unstable; urgency=low . [ Gabriele Giacone ] * Team upload. * B-D: Replace openjdk|sunjdk with default-jdk (Closes: #683502). * Fix icons gamma correction. . [ tony mancill ] * Bump Standards-Version to 3.9.4. * Remove deprectated DMUA flag field. * No longer ask java-wrappers to search for java5 (Closes: #606662) - Note, this bug was addressed in a previous upload, but it's not clear from the changelog or VCS history when. Checksums-Sha1: 41ad33d280e4ce39d2cc067b43aaa46a39b45fd5 2168 jedit_5.0.0+dfsg-2.dsc 5dd3ae6e42039df9e5b5d4156552ee7b6b40da46 21624 jedit_5.0.0+dfsg-2.debian.tar.xz d7b6d321d085a4f93d8c75743ff5c8565f8829d3 2182878 jedit_5.0.0+dfsg-2_all.deb Checksums-Sha256: ddc593a17348ee705c468d2e58187826bf17790da529df103bda58a3387e640d 2168 jedit_5.0.0+dfsg-2.dsc 81453032f6bf6c8326f54a84b0dfe2e70d7a45e1a5b146043c6b8087adc22ff6 21624 jedit_5.0.0+dfsg-2.debian.tar.xz 31f224365b6c9af435bd50d1efdc498118f75893b4c327315cebc1e383f448ea 2182878 jedit_5.0.0+dfsg-2_all.deb Files: 5411688595886a545824a199da319229 2168 editors optional jedit_5.0.0+dfsg-2.dsc d9e228dc560cc63788127977b63cdc09 21624 editors optional jedit_5.0.0+dfsg-2.debian.tar.xz 8ff89681f376107a73a8cf9c0db37275 2182878 editors optional jedit_5.0.0+dfsg-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJRq1wkAAoJECHSBYmXSz6WGtQQAIR9iR6U6VihBk6rVBxOsd4l 3jw8doureAMLSD2SpR2J0HmMJHkYKn2O/80QauBDPiMvCKqtltArLzjfRrlU6AnM KH6FVbBD65zz0c0wNdpBcrZXALziqFR9f6CYImbWguOYjFP/6QntwS1CAPeln0vz DFO/bQOeahF+BX6yrzAjnRVjnV46iMCobUSZ/grvvr1GMBKidpY5KVp46a0Bc/lc Gdx1UfrHUl4NBuLHKDk9T0YH9mwvdVFew4dkWYewnqC+r6GpZRfsqskZUDrQHul+ DmcRsK5CUiv5Bz38z3Eb1xgaL/04ukvCfH3kxp1HN3zGB01VTo++dRzcl5mvInBS g2J1uwBET0PjI471Eh3bFCM47ovA/Sf8VoEVsTk69RAUTx20RzjEhmzY+0MXdCEI
Bug#683502: marked as done (jedit: Fix FTBFS when default java implementation changes)
Your message dated Sun, 02 Jun 2013 15:20:32 + with message-id e1uja5a-0006tr...@franck.debian.org and subject line Bug#683502: fixed in jedit 5.0.0+dfsg-2 has caused the Debian Bug report #683502, regarding jedit: Fix FTBFS when default java implementation changes 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.) -- 683502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jedit Version: 5.0~pre1+dfsg-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu quantal ubuntu-patch openjdk-7-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS: - d/control: Switch to using default-jdk for build, don't use BDI's. In Ubuntu the default-java implementation has switched from openjdk-6 to openjdk-7; as a result this package FTBFS as d/rules refers to /usr/lib/jvm/default-java which does not actually get installed as the package BD's on openjdk-6. Thanks for considering the patch. - -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-7-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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJQGQMgAAoJEL/srsug59jD9DYQAL9gRhqhEqEHpscP9YcwW/kL A655u5TpJLLrGj+qG9PJCu4RYJHT6u16RiVy2wsJJ1gaFtS7G3ys0ciygVDweU5C Izt0Z1KIfVM784LHW8qr/8JLSPVga+nfi5tnO1IWt/8J1pty7Mg1nLeEXnRPAAAD xJMeMHrTXoMQ2opo6W+ChH8P/Zte7wMcAN3LwZDI7gOLeDLQ0/SLP+ey0RyVblfU vOiCgUlcx7no71UzcPvujII1C5I5jZT8jNg84qITgf1m9TWvpMrOZ2Ss6tUeuE+E hj5If6gv4lOUX6PredpeVZqCilSc7DJ1ZBhW4vRKQBsl5nz00Ze5AIhy/9vl+4FC l7I2JPxT3rO8co/E8Ks9kkPEZ6kD+24YVrUEsRPdsTyVY5MiDbiRfhwWQX69ZFvf pGtKxwnV7ypJjPlGV0kZ2iAi7/DPbm/WyNlg99xSAv9EcV2gubfGFQLcnT/z6tl9 mv2iHNJtltrpBVaQVadClM1LE08PQCou3pGJhkXFiO4fP9cJbqxuqu6ENIO3R/Qe ovJ0vsJJ77sCnfXs7rNCvPNB2wUBYlSSuxpQvEOY59Lo5HVU+EZusN40riVGmib2 5Xw0H46Iyr9ACTjz0J6yr9avqdqnCmrnw8/DvqpZjlEyuMFzQoUFuHwOaD4ykO9K UsqWkf1ABKJ6NXvtAAnC =P5DV -END PGP SIGNATURE- diff -Nru jedit-5.0~pre1+dfsg/debian/changelog jedit-5.0~pre1+dfsg/debian/changelog diff -Nru jedit-5.0~pre1+dfsg/debian/control jedit-5.0~pre1+dfsg/debian/control --- jedit-5.0~pre1+dfsg/debian/control 2012-06-16 12:54:27.0 +0100 +++ jedit-5.0~pre1+dfsg/debian/control 2012-08-01 11:18:39.0 +0100 @@ -6,8 +6,7 @@ Build-Depends: debhelper (= 7.0.50~), javahelper (= 0.24), ant, ant-optional, docbook-xsl, xsltproc, imagemagick, quilt (= 0.46-7~), bsh-src (= 2.0b4-11), docbook-xml, ant-contrib, bsh, docbook-xsl-saxon, libbsf-java, libcommons-logging-java, - junit -Build-Depends-Indep: openjdk-6-jdk | sun-java6-jdk + junit, default-jdk Standards-Version: 3.9.3 DM-Upload-Allowed: yes Vcs-Git: git://git.debian.org/pkg-java/jedit.git ---End Message--- ---BeginMessage--- Source: jedit Source-Version: 5.0.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of jedit, 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 683...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated jedit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 07:27:24 -0700 Source: jedit Binary: jedit Architecture: source all Version: 5.0.0+dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: tony mancill tmanc...@debian.org Description: jedit - Plugin-based editor for programmers Closes: 606662 683502 Changes: jedit (5.0.0+dfsg-2) unstable; urgency=low . [ Gabriele Giacone ] * Team upload. * B-D: Replace openjdk|sunjdk with default-jdk (Closes: #683502). * Fix icons gamma correction. . [ tony mancill ] * Bump Standards-Version to 3.9.4. * Remove
Bug#710807: ncbi-blast+: FTBFS on mipsel: project_tree_builder does not work
Source: ncbi-blast+ Version: 2.2.28-1 Severity: serious Justification: fails to build from source The mipsel build of ncbi-blast+ is failing because project_tree_builder (an internal tool used to streamline the build) segfaults: /.../ncbi-blast+-2.2.28/c++/scripts/common/impl/create_flat_makefile.sh: line 201: 15504 Segmentation fault $ptb -version /dev/null 21 ERROR: ./build-system/project_tree_builder/project_tree_builder does not work I am investigating this failure on eder, and will follow up as I learn more. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710315: marked as done (python2.7: 2.7.5 has bug in regexp engine)
Your message dated Sun, 02 Jun 2013 15:49:56 +
with message-id e1ujaxc-0006on...@franck.debian.org
and subject line Bug#710315: fixed in python2.7 2.7.5-5
has caused the Debian Bug report #710315,
regarding python2.7: 2.7.5 has bug in regexp engine
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.)
--
710315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python2.7
Version: 2.7.5-4
Severity: important
Dear Maintainer,
Python 2.7.5 has a bug in the regexp engine that kicks up RuntimeErrors.
The Python bug report is here:
http://bugs.python.org/issue17998
It seems to affect a good number of Python libraries.
Asheesh says to file this as a release critical bug, but I didn't see that as
an option.
Hope that's enough information!
/will
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python2.7 depends on:
ii libpython2.7-stdlib 2.7.5-4
ii mime-support 3.54
ii python2.7-minimal2.7.5-4
python2.7 recommends no packages.
Versions of packages python2.7 suggests:
ii binutils 2.22-8
pn python2.7-doc none
-- no debconf information
---End Message---
---BeginMessage---
Source: python2.7
Source-Version: 2.7.5-5
We believe that the bug you reported is fixed in the latest version of
python2.7, 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 710...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python2.7 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 02 Jun 2013 15:11:19 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg
libpython2.7-dbg
Architecture: source all amd64
Version: 2.7.5-5
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
idle-python2.7 - IDE for Python (v2.7) using Tkinter
libpython2.7 - Shared Python runtime library (version 2.7)
libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
libpython2.7-dev - Header files and a static library for Python (v2.7)
libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
libpython2.7-stdlib - Interactive high-level object-oriented language (version
2.7)
libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
python2.7 - Interactive high-level object-oriented language (version 2.7)
python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
python2.7-dev - Header files and a static library for Python (v2.7)
python2.7-doc - Documentation for the high-level object-oriented language
Python
python2.7-examples - Examples for the Python language (v2.7)
python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 709066 709157 709964 710315
Changes:
python2.7 (2.7.5-5) unstable; urgency=low
.
* Update to 20130602, taken from the 2.7 branch.
* Fix possible abuse of ssl.match_hostname() for denial of service
using certificates with many wildcards (CVE-2013-2099). Closes: #709066.
* Don't try to byte-compile sitecustomize.py if the target of the
symlink doesn't exist anymore. Closes: #709157.
* Handle byte compilation in python2.7{-minimal,}, byte removal in
libpython2.7{-minimal,-stdlib}. Closes: #709964.
* Backport patch to fix issue #13146, possible race conditions when writing
.pyc/.pyo files in py_compile.py (Barry Warsaw). LP: #1058884.
* Fix issue #17988, internal error in regular expression engine on 32bit
targets (closes: #710315).
Checksums-Sha1:
e51599032f3edf37ecf4efe3c153e63f966ad01c 2372 python2.7_2.7.5-5.dsc
811c05c7dd44f53f6488455866e9eba23eaaa0bc
Bug#709964: marked as done (python2.7-minimal: purging deletes /etc/python2.7/sitecustomize.py (owned by libpython2.7-minimal))
Your message dated Sun, 02 Jun 2013 15:49:56 +
with message-id e1ujaxc-0006og...@franck.debian.org
and subject line Bug#709964: fixed in python2.7 2.7.5-5
has caused the Debian Bug report #709964,
regarding python2.7-minimal: purging deletes /etc/python2.7/sitecustomize.py
(owned by libpython2.7-minimal)
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.)
--
709964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python2.7-minimal
Version: 2.7.5-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.
This could be a violation of policy 10.7.4 (Sharing configuration
files), see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.4
or policy chapter 6 (Package maintainer scripts...), see
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
or policy 7.6 (Overwriting files...), see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
From the attached log (scroll to the bottom...):
0m23.1s ERROR: FAIL: debsums reports modifications inside the chroot:
debsums: missing file /etc/python2.7/sitecustomize.py (from
libpython2.7-minimal package)
This test more or less did
apt-get install python2.7-minimal
dpkg --purge python2.7-minimal
debsums -a -c
cheers,
Andreas
python2.7-minimal_2.7.5-4.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: python2.7
Source-Version: 2.7.5-5
We believe that the bug you reported is fixed in the latest version of
python2.7, 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 709...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python2.7 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 02 Jun 2013 15:11:19 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg
libpython2.7-dbg
Architecture: source all amd64
Version: 2.7.5-5
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
idle-python2.7 - IDE for Python (v2.7) using Tkinter
libpython2.7 - Shared Python runtime library (version 2.7)
libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
libpython2.7-dev - Header files and a static library for Python (v2.7)
libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
libpython2.7-stdlib - Interactive high-level object-oriented language (version
2.7)
libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
python2.7 - Interactive high-level object-oriented language (version 2.7)
python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
python2.7-dev - Header files and a static library for Python (v2.7)
python2.7-doc - Documentation for the high-level object-oriented language
Python
python2.7-examples - Examples for the Python language (v2.7)
python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 709066 709157 709964 710315
Changes:
python2.7 (2.7.5-5) unstable; urgency=low
.
* Update to 20130602, taken from the 2.7 branch.
* Fix possible abuse of ssl.match_hostname() for denial of service
using certificates with many wildcards (CVE-2013-2099). Closes: #709066.
* Don't try to byte-compile sitecustomize.py if the target of the
symlink doesn't exist anymore. Closes: #709157.
* Handle byte compilation in python2.7{-minimal,}, byte removal in
libpython2.7{-minimal,-stdlib}. Closes: #709964.
* Backport patch to fix issue #13146, possible race conditions when writing
.pyc/.pyo files in py_compile.py (Barry Warsaw). LP: #1058884
Bug#710205: Please binNMU njplot against Motif-using libvibrant6
I recently switched Vibrant from Lesstif to Motif per the latter's move to main, and reuploaded its sole reverse dependency, njplot, accordingly (per #710205). However, njplot accidentally hit several autobuilders ahead of ncbi-tools6; could you please schedule rebuilds for the affected architectures? (Some of these will have to wait further for dependencies to catch up.) By my reading of http://release.debian.org/wanna-build.txt, the following syntax should DTRT; please feel free to tweak the NMU message as desired. nmu njplot_2.4-2 . armel armhf mips s390 s390x sparc . -m 'Really pick up libvibrant6; see #710205.' dw njplot_2.4-2 . armhf mips s390 sparc . -m 'libvibrant6' Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 710204 is forwarded to https://sourceforge.net/p/itpp/bugs/222/
Processing commands for cont...@bugs.debian.org: forwarded 710204 https://sourceforge.net/p/itpp/bugs/222/ Bug #710204 [src:libitpp] src:libitpp: FTBFS on several architectures Set Bug forwarded-to-address to 'https://sourceforge.net/p/itpp/bugs/222/'. thanks Stopping processing here. Please contact me if you need assistance. -- 710204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710204 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: bug 710204 is forwarded to https://sourceforge.net/p/itpp/bugs/222/, tagging 710204, tagging 710338 ...
Processing commands for cont...@bugs.debian.org: forwarded 710204 https://sourceforge.net/p/itpp/bugs/222/ Bug #710204 [src:libitpp] src:libitpp: FTBFS on several architectures Ignoring request to change the forwarded-to-address of bug#710204 to the same value tags 710204 + fixed-upstream Bug #710204 [src:libitpp] src:libitpp: FTBFS on several architectures Added tag(s) fixed-upstream. tags 710338 + pending Bug #710338 [src:libitpp] libitpp: FTBFS on mips: docs too slow to generate Added tag(s) pending. tags 710337 + fixed-upstream Bug #710337 [src:libitpp] libitpp: FTBFS on armhf - multiple typeinfo definitions linking itpp_gtests Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 710204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710204 710337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710337 710338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710338 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#709002: marked as done ([pdfsam] unable to load java after upgrade)
Your message dated Sun, 02 Jun 2013 16:33:07 + with message-id e1ujbdp-0001dl...@franck.debian.org and subject line Bug#709002: fixed in libjgoodies-looks-java 2.5.2-3 has caused the Debian Bug report #709002, regarding [pdfsam] unable to load java after upgrade 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.) -- 709002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pdfsam Version: 1.1.4-2 Severity: grave --- Please enter the report below this line. --- Command 507 of 10 $pdfsam = pdfsam JAVA: /usr/lib/jvm/java-6-openjdk-amd64/bin/java JAVA_OPTS: -Xmx256m CLASSPATH: /usr/share/pdfsam/pdfsam-1.1.4.jar:/usr/share/pdfsam/lib/dom4j.jar:/usr/share/pdfsam/lib/emp4j-1.0.1.jar:/usr/share/pdfsam/lib/itext.jar:/usr/share/pdfsam/lib/jaxen.jar:/usr/share/pdfsam/lib/log4j-1.2.jar:/usr/share/pdfsam/lib/looks.jar:/usr/share/pdfsam/lib/pdfsam-console-2.0.6e.jar:/usr/share/pdfsam/lib/pdfsam-jcmdline-1.0.3.jar:/usr/share/pdfsam/lib/pdfsam-langpack.jar = 08:35:07,483 INFO JMainFrame Starting PDF Split and Merge basic Ver. 1.1.4 08:35:08,491 INFO Configuration Loading configuration.. 08:35:09,152 INFO Configuration Getting language... 08:35:09,281 INFO Configuration Setting look and feel... 08:35:09,411 FATAL GuiClient Error: java.lang.NoClassDefFoundError: com/jgoodies/common/base/SystemUtils at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at com.jgoodies.looks.plastic.PlasticLookAndFeel.clinit(PlasticLookAndFeel.java:137) at org.pdfsam.guiclient.utils.ThemeUtility.setTheme(ThemeUtility.java:160) at org.pdfsam.guiclient.configuration.Configuration.setLookAndFeel(Configuration.java:192) at org.pdfsam.guiclient.configuration.Configuration.init(Configuration.java:169) at org.pdfsam.guiclient.configuration.Configuration.init(Configuration.java:54) at org.pdfsam.guiclient.configuration.Configuration.getInstance(Configuration.java:59) at org.pdfsam.guiclient.gui.frames.JMainFrame.init(JMainFrame.java:90) at org.pdfsam.guiclient.GuiClient.main(GuiClient.java:61) Caused by: java.lang.ClassNotFoundException: com.jgoodies.common.base.SystemUtils at java.net.URLClassLoader$1.run(URLClassLoader.java:217) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) ... 19 more --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing http.us.debian.org 500 testing ftp2.de.debian.org 500 testing ftp.fr.debian.org 500 testing ftp.deb-multimedia.org 500 testing apt.jenslody.de 500 stable repo.wuala.com 500 stable apt.spideroak.com 500 oneiric ppa.launchpad.net 500 debian packages.linuxmint.com --- Package information. --- Depends (Version) | Installed =-+-=== openjdk-6-jre | 6b27-1.12.5-1 OR java2-runtime | libdom4j-java | 1.6.1+dfsg.2-6 libitext-java | 2.1.7-3+deb7u1 libjaxen-java | 1.1.3-1 libjgoodies-looks-java| 2.5.2-2 liblog4j1.2-java |
Bug#701260: marked as done (clementine: ftbfs with GCC-4.8)
Your message dated Sun, 02 Jun 2013 17:03:03 + with message-id e1ujbgn-0001go...@franck.debian.org and subject line Bug#701260: fixed in clementine 1.1.1+dfsg-2 has caused the Debian Bug report #701260, regarding clementine: ftbfs with GCC-4.8 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.) -- 701260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:clementine Version: 1.0.1+dfsg-2 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. qtconcurrentfilter.h:108:47: error: typedef 'Iterator' locally defined but not used [-Werror=unused-local-typedefs] The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/clementine_1.0.1+dfsg-2_unstable_gcc48.log The last lines of the build log are at the end of this report. To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues might be caused by the updated glibc. [...] cd /«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu/src /usr/bin/c++ -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_NO_CAST_TO_ASCII -DQT_STRICT_ITERATORS -DQT_NO_DEBUG_OUTPUT -DQT_NO_WARNING_OUTPUT -Woverloaded-virtual -Wall -Wno-sign-compare -Werror -I/usr/include/qt4 -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/usr/include/taglib -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/«BUILDDIR»/clementine-1.0.1+dfsg/3rdparty/universalchardet -I/«BUILDDIR»/clementine-1.0.1+dfsg -I/«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu/src -I/«BUILDDIR»/clementine-1.0.1+dfsg/src -I/«BUILDDIR»/clementine-1.0.1+dfsg/src/../3rdparty/gmock/gtest/include -I/«BUILDDIR»/clementin e-1.0.1+dfsg/src/../3rdparty/sha2 -I/«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu -I/«BUILDDIR»/clementine-1.0.1+dfsg/3rdparty/qtsingleapplication -I/«BUILDDIR»/clementine-1.0.1+dfsg/3rdparty/qtiocompressor -I/usr/include/qxt/QxtCore -I/usr/include/qxt/QxtGui -I/usr/include/libindicate-qt -I/usr/include/gpod-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/p11-kit-1 -I/usr/include/libusb-1.0-o CMakeFiles/clementine_lib.dir/core/commandlineoptions.cpp.o -c /«BUILDDIR»/clementine-1.0.1+dfsg/src/core/commandlineoptions.cpp /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles [ 46%] Building CXX object src/CMakeFiles/clementine_lib.dir/core/crashreporting.cpp.o cd /«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu/src /usr/bin/c++ -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_NO_CAST_TO_ASCII -DQT_STRICT_ITERATORS -DQT_NO_DEBUG_OUTPUT -DQT_NO_WARNING_OUTPUT -Woverloaded-virtual -Wall -Wno-sign-compare -Werror -I/usr/include/qt4 -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/usr/include/taglib -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/«BUILDDIR»/clementine-1.0.1+dfsg/3rdparty/universalchardet -I/«BUILDDIR»/clementine-1.0.1+dfsg -I/«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu/src -I/«BUILDDIR»/clementine-1.0.1+dfsg/src -I/«BUILDDIR»/clementine-1.0.1+dfsg/src/../3rdparty/gmock/gtest/include -I/«BUILDDIR»/clementin e-1.0.1+dfsg/src/../3rdparty/sha2 -I/«BUILDDIR»/clementine-1.0.1+dfsg/obj-x86_64-linux-gnu -I/«BUILDDIR»/clementine-1.0.1+dfsg/3rdparty/qtsingleapplication -I/«BUILDDIR»/clementine-1.0.1+dfsg/3rdparty/qtiocompressor -I/usr/include/qxt/QxtCore -I/usr/include/qxt/QxtGui -I/usr/include/libindicate-qt -I/usr/include/gpod-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12
Bug#710750: marked as done (rhythmbox: FTBFS on non-Linux: no mtpdevice plugin to install)
Your message dated Sun, 02 Jun 2013 17:05:13 + with message-id e1ujbit-0002em...@franck.debian.org and subject line Bug#710750: fixed in rhythmbox 2.99.1-3 has caused the Debian Bug report #710750, regarding rhythmbox: FTBFS on non-Linux: no mtpdevice plugin to install 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.) -- 710750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rhythmbox Version: 2.99.1-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of rhythmbox on kFreeBSD (and presumably also the Hurd if and when its build dependencies become satisfiable) have been failing because there's no mtpdevice plugin to install: dh_install -prhythmbox-plugins -Xfmradio cp: cannot stat `debian/tmp/usr/lib/rhythmbox/plugins/mtpdevice': No such file or directory dh_install: cp -a debian/tmp/usr/lib/rhythmbox/plugins/mtpdevice debian/rhythmbox-plugins//usr/lib/rhythmbox/plugins/ returned exit code 1 make: *** [binary-install/rhythmbox-plugins] Error 2 Could you please take a look? Thanks! ---End Message--- ---BeginMessage--- Source: rhythmbox Source-Version: 2.99.1-3 We believe that the bug you reported is fixed in the latest version of rhythmbox, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort po...@debian.org (supplier of updated rhythmbox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 Jun 2013 18:39:24 +0200 Source: rhythmbox Binary: rhythmbox rhythmbox-data rhythmbox-dbg rhythmbox-plugins rhythmbox-plugin-cdrecorder librhythmbox-core7 rhythmbox-dev rhythmbox-doc gir1.2-rb-3.0 Architecture: source all amd64 Version: 2.99.1-3 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Emilio Pozuelo Monfort po...@debian.org Description: gir1.2-rb-3.0 - GObject introspection data for the rhythmbox music player librhythmbox-core7 - support library for the rhythmbox music player rhythmbox - music player and organizer for GNOME rhythmbox-data - data files for rhythmbox rhythmbox-dbg - debugging symbols for rhythmbox rhythmbox-dev - development files for the rhythmbox music player rhythmbox-doc - documentation files for the rhythmbox music player rhythmbox-plugin-cdrecorder - burning plugin for rhythmbox music player rhythmbox-plugins - plugins for rhythmbox music player Closes: 710750 Changes: rhythmbox (2.99.1-3) unstable; urgency=low . * debian/rules: + Use DEB_DH_INSTALL_ARGS_rhythmbox-plugins as that's supported nowadays. + Install the frmradio plugin on !linux as it builds there now. + Disable the mtpdevice plugin on !linux as it needs gudev or hal and we don't build with hal anymore. Closes: #710750. Checksums-Sha1: d8f6ce93be5d232c51ca17fc6e89f7c49ed39468 3054 rhythmbox_2.99.1-3.dsc db040bf509d21cf7e2375fb46b320042ce777f64 40521 rhythmbox_2.99.1-3.debian.tar.gz fd3e2527b1d9cdb8263460d6e0ac2918619ff4de 4284694 rhythmbox-data_2.99.1-3_all.deb a9782bbcb5765a6b91454208a2552a43e17c39c1 526304 rhythmbox-doc_2.99.1-3_all.deb baaeafa2d80b734e1192bdb2a6a2e00c10a01db3 420538 rhythmbox_2.99.1-3_amd64.deb b197c51e65793b33a4a0227104047a41cffd7317 3278252 rhythmbox-dbg_2.99.1-3_amd64.deb a9f6af3ea986668e061a9082b22bb459a7e24bce 672860 rhythmbox-plugins_2.99.1-3_amd64.deb 6c012d254d1400167aa47be0e0e1f98cb4985fc2 384528 rhythmbox-plugin-cdrecorder_2.99.1-3_amd64.deb 2617b84fc829ffe440b341010f749f1564ccb666 794142 librhythmbox-core7_2.99.1-3_amd64.deb b9bf15faec7f60c6533989bf572215b7aae70d45 482704 rhythmbox-dev_2.99.1-3_amd64.deb 9c76dd67e24a76cfba061d6bac6cd08442650a7d 406286 gir1.2-rb-3.0_2.99.1-3_amd64.deb Checksums-Sha256: e789d3da469ce24c772cbfc35dc71121a822331e83bf9a0d6f36a8ea40157253 3054 rhythmbox_2.99.1-3.dsc f9e99e95effd60437ee51791106f36dac70e509aa9200bf7a0d2030eda22dcfa 40521 rhythmbox_2.99.1-3.debian.tar.gz
