Bug#524127: [uscan] 'x509_user' not valid URI scheme at /usr/bin/uscan line 389
On Thu, 2009-04-16 at 02:45 +0200, Steffen Moeller wrote: Hello, the issue seems to be invariant of the watch file used. It still occurs. [...] $ set | grep -i proxy X509_USER_PROXY=/home/moeller/myproxy Aha! This seems to be due to a change made upstream in libwww-perl in version 5.821: croak on bad proxy args [RT#39919] This is easily confirmable by checking whether the following also fails for you: #! /usr/bin/perl use LWP::UserAgent; my $ua = LWP::UserAgent-new(env_proxy = 1); env_proxy is documented as reading environment variables of the form *_proxy. LWP maintainers - any thoughts? Should clients (e.g. uscan) be attempting to sanitise the proxy variables in the environment to only include those they specifically care about before using env_proxy? (or wrapping the call in an eval() and ignoring the specific error) That's obviously doable, but would need doing in every client individually, which seems somewhat overkill. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523514: marked as done (Compiz fails to load due to wrong ABI version)
Your message dated Thu, 16 Apr 2009 07:57:18 +0200 with message-id 20090416055718.ga22...@loulous.org and subject line Re: Bug#523514: compiz has caused the Debian Bug report #523514, regarding Compiz fails to load due to wrong ABI version 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.) -- 523514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: Compiz Version: 0.8.2-2 Severity: serious After upgrading compiz I get the following error on startup: Starting gtk-window-decorator /usr/bin/compiz.real (core) - Error: Plugin 'core' has ABI version '20090207', expected ABI version '20080424'. /usr/bin/compiz.real (ccp) - Error: InitObject failed /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'ccp' -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages compiz depends on: ii compiz-core 0.8.2-2OpenGL window and compositing mana ii compiz-gnome 0.8.2-2OpenGL window and compositing mana ii compiz-gtk0.8.2-2OpenGL window and compositing mana ii compiz-plugins0.8.2-2OpenGL window and compositing mana compiz recommends no packages. Versions of packages compiz suggests: ii compizconfig-settings-manager 0.8.2-1Compizconfig Settings Manager -- no debconf information ---End Message--- ---BeginMessage--- On Sun, Apr 12, 2009 at 07:36:06PM +0100, Immolo wrote: This bug can be fixed by purging compiz and reinstalling so I guess if during the upgrade the config file is removed this problem won't happen. Don't know what happened, cannot reproduce, let's just close this... Brice ---End Message---
Bug#524305: open-iscsi: iSCSI device hangs on high load
Hi John, On Thursday 16 Apr 2009 11:20:18 John Lepikhin wrote: tid:1 lun:0 by sid:844424967684608 (Function Complete) Apr 15 05:07:50 c1 kernel: [1127304.719482] iscsi_trgt: cmnd_abort(1148) 3b20 1 0 0 0 0 0 Apr 15 05:07:50 c1 kernel: [1127304.719482] iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by sid:844424967684608 (Function Complete) Apr 15 05:07:50 c1 kernel: [1127304.723482] connection2:0: detected conn error (1011) Apr 15 05:09:34 c1 kernel: [1127440.726777] INFO: task pdflush:194 blocked for more than 120 seconds. Apr 15 05:09:34 c1 kernel: [1127440.730770] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 15 05:09:34 c1 kernel: [1127440.730770] pdflush D 0 194 2 ... This doesn't look to be an initiator side problem. Looks like there is an Abort Task from the target. That then leads to Connection Termination. (I wonder why it is not re- establishing) And the hang is obvious because of the above things happening. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: This is a digitally signed message part.
Bug#524233: console-setup should conflict with console-data
Quoting Anton Zinoviev (an...@lml.bas.bg): merge 524233 524239 thanks On Wed, Apr 15, 2009 at 07:14:34PM +0200, Kurt Roeckx wrote: console-setup and console-data both allow you to setup the keyboard layout but they do not take each other settings into account. Why this should be considered a bug? Normaly the users don't have to install both packages but perhaps there are many reasons why they might want to install them both. Console-data and console-cyrillic have happily coexisted for a decade and now this can continue with console-setup (exept that it seems console-data and console-cyrillic are going to become obsolete). As the de facto maintainer of console-data, I agree with this. I have to add that I unfortunately am entirely unable to implement in c-d something to have it grab keymap definitions from console-setup. Moreover, as both use different origins for the keymaps (c-s uses X.org keymaps while c-d provides the old-style Linux console keymaps, crafted by generation of Linux users over yearsturning into a giant mess), it is very likely that many keymaps do not necessarily correspond. I would be delighted to obsolete console-data, as many people know. There are however several steps to achieve before that happens (one of those being d-i uing console-setup). An I indeed have no idea about how to turn console-data into a completely obsolete package and then offer users a decent transition to console-setup signature.asc Description: Digital signature
Bug#524295: marked as done (liblpsolve55-dev should depend on libsuitesparse-dev due to libcolamd linkage)
Your message dated Thu, 16 Apr 2009 08:41:08 +0200
with message-id 20090416064108.ga1...@rene-engelhard.de
and subject line Re: Bug#524295: liblpsolve55-dev should depend on
libsuitesparse-dev due to libcolamd linkage
has caused the Debian Bug report #524295,
regarding liblpsolve55-dev should depend on libsuitesparse-dev due to libcolamd
linkage
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.)
--
524295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: liblpsolve55-dev
Severity: Serious
liblpsolve55-dev should depend on libsuitesparse-dev since it uses
libcolamd and programs linking will need to link against it as well.
NEEDED libcolamd.so.3.2.0
Chris
---End Message---
---BeginMessage---
Hi,
Chris Cheney wrote:
liblpsolve55-dev should depend on libsuitesparse-dev since it uses
libcolamd {...}
No. lp_solveheaders include no colamd headers, so why should the -dev package
depend on it?
and programs linking will need to link against it as well.
afair not, and even if this was the case, if you use colamd, build-depend
on the package you need yourself: libsuitesparse-dev.
NEEDED libcolamd.so.3.2.0
That's why lp_solve depends on libcolamd-3.2.0.
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' r...@debian.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
---End Message---
Bug#524189:
In previous post there are about 22000bytes missing, ie. cca 25% of data for combination KDE Konsole,Ctrl+c,Ctrl+v. When using aterm instead of KDE Konsole and copy is done by middle mouse, then there are 64000bytes missing, ie. cca 76% of data lost. Because the aterm paste took much longer time than Konsole and lost is also higher coudn't be this somehow related to terminal speed/baudrate?? (sorry if nonsence i'm just proud BFU ;) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 523179, tagging 524163
Processing commands for cont...@bugs.debian.org: tags 523179 pending Bug#523179: php5: libaprutil1-dev's libdb4.7-dev conflicts with libdb4.6-dev There were no tags set. Tags added: pending tags 524163 pending Bug#524163: PhP5-dev build dir points to incorrect locations There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524308: FTBFS: capplet-stock-icons.c:28:19: error: gnome.h: No such file or directory
Package: control-center Version: 1:2.24.0.1-3 Severity: serious As seen on at least alpha, armel and amd64 buildd's. Possibly not the fault of control-center itself, but the dependency -chain is too complex for my mind to follow.. cc -DHAVE_CONFIG_H -I. -I../.. -DGNOMECC_DATA_DIR=\/usr/share/gnome-control-center\ -DGNOMELOCALEDIR=\/usr/share/locale\ -DGTK_ENGINE_DIR=\/usr/lib/gtk-2.0/2.10.0/engines\ -DG_LOG_DOMAIN=\capplet-common\ -DINSTALL_PREFIX=\/usr\ -I../.. -I../../libwindow-settings -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_REENTRANT -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -D_REENTRANT -I/usr/include/metacity-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-settings-daemon-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O2 -c capplet-stock-icons.c -fPIC -DPIC -o .libs/capplet-stock-icons.o capplet-stock-icons.c:28:19: error: gnome.h: No such file or directory capplet-stock-icons.c: In function 'capplet_register_stock_icons': capplet-stock-icons.c:64: warning: implicit declaration of function 'gnome_program_locate_file' capplet-stock-icons.c:64: error: 'GNOME_FILE_DOMAIN_APP_PIXMAP' undeclared (first use in this function) capplet-stock-icons.c:64: error: (Each undeclared identifier is reported only once capplet-stock-icons.c:64: error: for each function it appears in.) capplet-stock-icons.c:64: warning: assignment makes pointer from integer without a cast capplet-stock-icons.c:67: warning: implicit declaration of function '_' capplet-stock-icons.c:67: warning: passing argument 3 of 'g_log' makes pointer from integer without a cast make[4]: *** [capplet-stock-icons.lo] Error 1 make[4]: Leaving directory `/build/buildd/control-center-2.24.0.1/capplets/common' make[3]: *** [all-recursive] Error 1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
Package: sysv-rc Version: 2.86.ds1-61 Severity: critical Sysv-rc always reports that actions failed even if they are successfully accomplished. This breaks reconfiguration of every package that call invoke-rc.d during upgrade, remove, purge, install or reinstall. --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-2-686 Debian Release: squeeze/sid 990 testing www.debian-multimedia.org 990 testing security.debian.org 990 testing ftp.it.debian.org 650 unstablewww.debian-multimedia.org 650 unstableftp.it.debian.org 600 experimentalwww.debian-multimedia.org 600 experimentalftp.it.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
tags 524314 moreinfo thanks On Thursday 16 April 2009 18:04:27 Carlo Aquilini wrote: Package: sysv-rc Version: 2.86.ds1-61 Severity: critical Sysv-rc always reports that actions failed even if they are successfully accomplished. This breaks reconfiguration of every package that call invoke-rc.d during upgrade, remove, purge, install or reinstall. You need to provide actual data to support this claim, such as commands which reproduce the problem described. Thanks, Kel.
Processed: Re: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
Processing commands for cont...@bugs.debian.org: tags 524314 moreinfo Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524303: python-elementtree: Should depend on python-support = 0.90
Package: python-elementtree Version: 1.2.6-13 Severity: normal I also experienced this problem. It seems that python-support implemented the .public files only starting with 0.90.0... so I guess a dependency is wrong here :( FWIW : dpkg -l python-support gives : 0.8.7 Hope this helps, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-elementtree depends on: ii python2.5.4-2An interactive high-level object-o ii python-support0.8.7 automated rebuilding support for P python-elementtree recommends no packages. Versions of packages python-elementtree suggests: pn python-elementtree-docnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518521: FTBFS on lenny/ia64
I just tried re-building in merulo's lenny chroot and got the same error as in the build log from buildd.debian.org: [0] 10:27 m...@lenny.merulo:~/lam/lam-7.1.2/share/etc 2s $ if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../share/include -DLAM_SYSCONFDIR=\/usr/lib/lam/etc\ -DLAM_PREFIX=\/usr/lib/lam\ -I../../share/include -DLAM_BUILDING=1 -O3 -pthread -MT rev.lo -MD -MP -MF .deps/rev.Tpo -c -o rev.lo rev.c; \ then mv -f .deps/rev.Tpo .deps/rev.Plo; else rm -f .deps/rev.Tpo; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I../../share/include -DLAM_SYSCONFDIR=\/usr/lib/lam/etc\ -DLAM_PREFIX=\/usr/lib/lam\ -I../../share/include -DLAM_BUILDING=1 -O3 -pthread -MT rev.lo -MD -MP -MF .deps/rev.Tpo -c rev.c -o rev.o rev.c: In function 'mrev4': rev.c:131: internal compiler error: in trunc_int_for_mode, at explow.c:55 Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.3/README.Bugs for instructions. Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
Hello, I discovered it during acpid upgrade that failed claiming that it couldn't stop and restart the service (solved by momentarily renaming /etc/init.d/acpid and then upgrading). One example could be freepops: $ ps aux | grep freepops carlo 8052 0.0 0.0 3212 752 pts/0S+ 10:28 0:00 grep freepops nobody 15771 0.4 0.3 27936 7448 ?S09:48 0:11 /usr/bin/freepopsd -p 110 -n -s nobody.nogroup $ sudo invoke-rc.d freepops stop * Stopping freepops daemon freepopsd [ OK ] invoke-rc.d: initscript freepops, action stop failed. $ ps aux | grep freepops carlo11644 0.0 0.0 3212 752 pts/0R+ 10:34 0:00 grep freepops $ sudo invoke-rc.d freepops start * Starting freepops daemon freepopsd [ OK ] invoke-rc.d: initscript freepops, action start failed. $ ps aux | grep freepops nobody 12303 0.0 0.0 5980 1708 ?S10:35 0:00 /usr/bin/freepopsd -p 110 -n -s nobody.nogroup carlo12690 0.0 0.0 3212 752 pts/0R+ 10:36 0:00 grep freepops So that package freepops is stopped and started successfully, but invoke-rc.d claims that the actions failed. This happens with every service in /etc/init.d/ Please, ask for further informations if needed. Regards, CA Il giorno gio, 16/04/2009 alle 18.15 +1000, Kel Modderman ha scritto: tags 524314 moreinfo thanks On Thursday 16 April 2009 18:04:27 Carlo Aquilini wrote: Package: sysv-rc Version: 2.86.ds1-61 Severity: critical Sysv-rc always reports that actions failed even if they are successfully accomplished. This breaks reconfiguration of every package that call invoke-rc.d during upgrade, remove, purge, install or reinstall. You need to provide actual data to support this claim, such as commands which reproduce the problem described. Thanks, Kel. -- 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 524303 is grave
Processing commands for cont...@bugs.debian.org: severity 524303 grave Bug#524303: python-elementtree: Fails to configure properly in Testing Severity set to `grave' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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 524303 + pending Bug#524303: python-elementtree: Fails to configure properly in Testing There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524303: (no subject)
Same here.. From a fresh install of Lenny upgrading to Squeeze. Errors were encountered while processing: python-elementtree E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up python-elementtree (1.2.6-13) ... Usage: update-python-modules [-v] [-c] package_directory [...] update-python-modules [-v] [-c] package.dirs [...] update-python-modules [-v] [-a|-f|-p] update-python-modules: error: /usr/share/python-support/python-elementtree.public is not a directory dpkg: error processing python-elementtree (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: python-elementtree -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524303: python-elementtree: same here
Package: python-elementtree Version: 1.2.6-12 Followup-For: Bug #524303 Errors were encountered while processing: python-elementtree E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up python-elementtree (1.2.6-13) ... Usage: update-python-modules [-v] [-c] package_directory [...] update-python-modules [-v] [-c] package.dirs [...] update-python-modules [-v] [-a|-f|-p] update-python-modules: error: /usr/share/python-support/python-elementtree.public is not a directory dpkg: error processing python-elementtree (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: python-elementtree Sorry for the duplicate report. I wanted to report this the proper way. Daryl -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-elementtree depends on: ii python2.5.2-3An interactive high-level object-o ii python-support0.8.4 automated rebuilding support for P python-elementtree recommends no packages. Versions of packages python-elementtree suggests: pn python-elementtree-docnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
On Thursday 16 April 2009 18:42:39 Carlo Aquilini wrote: Hello, I discovered it during acpid upgrade that failed claiming that it couldn't stop and restart the service (solved by momentarily renaming /etc/init.d/acpid and then upgrading). The output of the upgrade should be provided. One example could be freepops: $ ps aux | grep freepops carlo 8052 0.0 0.0 3212 752 pts/0S+ 10:28 0:00 grep freepops nobody 15771 0.4 0.3 27936 7448 ?S09:48 0:11 /usr/bin/freepopsd -p 110 -n -s nobody.nogroup $ sudo invoke-rc.d freepops stop * Stopping freepops daemon freepopsd [ OK ] invoke-rc.d: initscript freepops, action stop failed. $ ps aux | grep freepops carlo11644 0.0 0.0 3212 752 pts/0R+ 10:34 0:00 grep freepops $ sudo invoke-rc.d freepops start * Starting freepops daemon freepopsd [ OK ] invoke-rc.d: initscript freepops, action start failed. $ ps aux | grep freepops nobody 12303 0.0 0.0 5980 1708 ?S10:35 0:00 /usr/bin/freepopsd -p 110 -n -s nobody.nogroup carlo12690 0.0 0.0 3212 752 pts/0R+ 10:36 0:00 grep freepops So that package freepops is stopped and started successfully, but invoke-rc.d claims that the actions failed. This happens with every service in /etc/init.d/ I installed the freepops package to investigate, and then run the following commands: r...@nomad:/home/kelmo# invoke-rc.d freepops start Starting freepops daemon: freepopsd. r...@nomad:/home/kelmo# invoke-rc.d freepops stop Stopping freepops daemon: freepopsd. r...@nomad:/home/kelmo# The output look a little different to yours, and I cannot reproduce the failure. Thanks, Kel.
Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
Il giorno gio, 16/04/2009 alle 19.18 +1000, Kel Modderman ha scritto: The output of the upgrade should be provided. The output of the upgrade was identical to this one: Mi preparo a sostituire acpid 1.0.8-7 (con .../acpid_1.0.8-7_i386.deb) ... * Stopping ACPI services...[ OK ] invoke-rc.d: initscript acpid, action stop failed. dpkg: attenzione - il vecchio script di pre-removal ha restituito un codice di errore 1 dpkg - provo quindi lo script dal nuovo pacchetto ... * Stopping ACPI services...[ OK ] invoke-rc.d: initscript acpid, action stop failed. dpkg: errore processando /var/cache/apt/archives/acpid_1.0.8-7_i386.deb (--unpack): il sottoprocesso nuovo script di pre-removal ha restituito un codice di errore 1 * Starting ACPI services...[ OK ] invoke-rc.d: initscript acpid, action start failed. dpkg: errore durante la pulizia: il sottoprocesso post-installation script ha restituito un codice di errore 1 Sono occorsi degli errori processando: /var/cache/apt/archives/acpid_1.0.8-7_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Errore durante l'installazione di un pacchetto. Tentativo di ripristino: dpkg: errore processando acpid (--configure): Il pacchetto si trova in uno stato di inconsistenza grave - dovresti reinstallarlo prima di tentare la configurazione. Sono occorsi degli errori processando: acpid Lettura della lista dei pacchetti in corso... Fatto Generazione dell'albero delle dipendenze in corso Lettura informazioni sullo stato... Fatto Lettura delle informazioni sullo stato esteso Inizializzazione dello stato dei pacchetti... Fatto Lettura delle descrizioni dei task... Fatto I installed the freepops package to investigate, and then run the following commands: r...@nomad:/home/kelmo# invoke-rc.d freepops start Starting freepops daemon: freepopsd. r...@nomad:/home/kelmo# invoke-rc.d freepops stop Stopping freepops daemon: freepopsd. r...@nomad:/home/kelmo# The output look a little different to yours, and I cannot reproduce the failure. Sysv-rc worked well till today when I discovered this problem. Maybe this bug is related to some other package in squeeze. I'll try to investigate. Thanks, CA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524303: wrong python-support dependency
Same here, but solved thanks to Olivier's remark, the dependency in python-support seems to be wrong, it only states Depends: python (= 2.3), python-support whereas updating to py-support 1.0.2 in unstable solves the problem apt-get -s install python-support/unstable -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524253: marked as done (gnome-settings-daemon: FTBFS: too few arguments to function 'gnome_rr_config_apply_stored')
Your message dated Thu, 16 Apr 2009 09:03:01 + with message-id e1lunur-0002mb...@ries.debian.org and subject line Bug#524253: fixed in gnome-settings-daemon 2.24.1-3 has caused the Debian Bug report #524253, regarding gnome-settings-daemon: FTBFS: too few arguments to function 'gnome_rr_config_apply_stored' 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.) -- 524253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnome-settings-daemon Version: 2.24.1-2 Severity: serious Hi, Your package is failing to build with the following error: gsd-xrandr-manager.c: In function 'on_client_message': gsd-xrandr-manager.c:121: error: too few arguments to function 'gnome_rr_config_apply_stored' gsd-xrandr-manager.c: In function 'event_filter': gsd-xrandr-manager.c:149: error: too few arguments to function 'gnome_rr_config_apply_stored' gsd-xrandr-manager.c: In function 'get_allowed_rotations_for_output': gsd-xrandr-manager.c:394: error: too few arguments to function 'gnome_rr_config_applicable' gsd-xrandr-manager.c: In function 'output_rotation_item_activate_cb': gsd-xrandr-manager.c:459: error: too few arguments to function 'gnome_rr_config_apply_stored' gsd-xrandr-manager.c: In function 'gsd_xrandr_manager_start': gsd-xrandr-manager.c:697: error: too few arguments to function 'gnome_rr_screen_new' gsd-xrandr-manager.c:731: error: too few arguments to function 'gnome_rr_config_apply_stored' make[4]: *** [libxrandr_la-gsd-xrandr-manager.lo] Error 1 Kurt ---End Message--- ---BeginMessage--- Source: gnome-settings-daemon Source-Version: 2.24.1-3 We believe that the bug you reported is fixed in the latest version of gnome-settings-daemon, which is due to be installed in the Debian FTP archive: gnome-settings-daemon-dev_2.24.1-3_amd64.deb to pool/main/g/gnome-settings-daemon/gnome-settings-daemon-dev_2.24.1-3_amd64.deb gnome-settings-daemon_2.24.1-3.diff.gz to pool/main/g/gnome-settings-daemon/gnome-settings-daemon_2.24.1-3.diff.gz gnome-settings-daemon_2.24.1-3.dsc to pool/main/g/gnome-settings-daemon/gnome-settings-daemon_2.24.1-3.dsc gnome-settings-daemon_2.24.1-3_amd64.deb to pool/main/g/gnome-settings-daemon/gnome-settings-daemon_2.24.1-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 524...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josselin Mouette j...@debian.org (supplier of updated gnome-settings-daemon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 16 Apr 2009 10:15:45 +0200 Source: gnome-settings-daemon Binary: gnome-settings-daemon gnome-settings-daemon-dev Architecture: source amd64 Version: 2.24.1-3 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome-settings-daemon - daemon handling the GNOME session settings gnome-settings-daemon-dev - Headers for building applications communicating with gnome-settin Closes: 524253 Changes: gnome-settings-daemon (2.24.1-3) unstable; urgency=low . * 03_gnomedesktop_api.patch: patch to cope with the API changes in GnomeRR 2.26. Closes: #524253. * Bump build-dependency on gnome-desktop to 2.26. Checksums-Sha1: 447d3f9057553a5f6fc2fe5db488d4b0ab76413b 1798 gnome-settings-daemon_2.24.1-3.dsc 06683d1aede988f51eb7511c9bb7ac7e0675cbba 489233 gnome-settings-daemon_2.24.1-3.diff.gz 74947bd219b673d082d45121f5d94b4a2f801a66 625328 gnome-settings-daemon_2.24.1-3_amd64.deb b746d2c29da943624a049352aac06662b7f0a0f2 4 gnome-settings-daemon-dev_2.24.1-3_amd64.deb Checksums-Sha256: 74c1200688aa985b385f98a7944eba45f7dcbfd1e9d19819a9d4585da13a63f3 1798 gnome-settings-daemon_2.24.1-3.dsc a9ed9f298c310e90f407d7fe47227c531b08187630e376b97522c25c5ecafa00 489233 gnome-settings-daemon_2.24.1-3.diff.gz a753f9ca073fa75bba40eaf894b70e8f87cd082fbb3c2c13e613a92e275dc9e0 625328 gnome-settings-daemon_2.24.1-3_amd64.deb 9f93d234f50cbf12f3d68be162eafa2097650edcddcff0db3bce78a03860d074 4 gnome-settings-daemon-dev_2.24.1-3_amd64.deb Files: 3bed190285aff8bb4d88aba0cc39713a 1798
Bug#518673: libidn_1.12-2(hppa/experimental): FTBFS: java not available on hppa
Adeodato Simó d...@net.com.org.es writes: * Simon Josefsson [Mon, 09 Mar 2009 10:39:48 +0100]: Hi. Thanks for the report. This patch may help: -Build-Depends: debhelper (= 6), autotools-dev, gcj, fastjar +Build-Depends: debhelper (= 6), autotools-dev, gcj [!alpha !arm !hppa !hurd-i386 !sh3 !sh4], fastjar Yes, that patch should help. In the common case, Build-Depending on gcj will just prevent the package from being tried on arches that do not have java/gcj. But TTBOMK the experimental autobuilders don't include the patch that manages to do that, hence it was tried. AFAICS, libidn provides other binaries than java package, so you really need to apply your patch above. Otherwise, those other parts won't be built on arches without java (and would be eternally out-of-date). Right, I have made this change in the 1.14-2 upload. I ended up using: Build-Depends: debhelper (= 6), autotools-dev, gcj [!arm !hppa !hurd-i386], fastjar Because only arm, hppa, and hurd-i386 are official debian architectures that lack gcj packages in unstable. The libidn11-java package is Architecture: all, so the libidn11-java package built on hppa will never be installed in the archive, right? If you creates -java packages that are arch:any, in addition to debian/control, you must modify your debian/rules to handle gracefully being built on a system without gcj. The result should be that the libidn11-java is not built at all; you can do that with the -N switch of debhelper. You should be able to find example code. I didn't find any example code, but I worked out something that worked on local testing. I'm not sure how to test whether the above patch is enough, other than to upload a new package. Rebuilding the package on my i386 machine will likely just work fine. Ideas? I suggest that you do the following test. Apply the following version of the patch in a test package: - Build-Depends: debhelper (= 6), autotools-dev, gcj, fastjar + Build-Depends: debhelper (= 6), autotools-dev, xxx [!i386], fastjar And then build your package on pbuilder passing -B. That should simulate what the hppa buildd is going to do. Do you see it? Yup, I was able to reproduce things this way. I'm not sure exactly what the buildd's will do when it has built the package, and there is no libidn11-java package though? Hopefully it will upload the binary packages it generated, and ignore the missing package. Anibal, what do you think? https://buildd.debian.org/quinn-diff/Packages-arch-specific Maybe list libidn11-java in Packages-arch-specific to only exclude hppa? P-a-s would be relevant here if libidn11-java was arch:any, and only because libidn provides some non-java packages. I didn't understand the purpose of that file -- is it still something that we should consider? If we can solve things in the local debian/ directory, that seems preferable to me. Maybe a better solution is to Build-Depend on 'default-jdk' rather than depending on 'gcj' explicitly? I believe the libidn java port should build with any compliant java compiler. I have no idea about this, and you should ask debian-java. But I'll note that there is no default-jdk on hppa either. I kept using gcj since that it is the preferred java compiler anyway. But this could be changed in the future if someone cares. I hope this mail cleared things for you. Yes thank you! Hopefully it will work better with this upload, but if it doesn't I hope you still have some patience to help me make it work. /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524331: compiz: 0.8.2 only in amd64
Package: compiz Version: 1:0.7.9+git20080918.shame-0 Severity: grave Justification: renders package unusable Compiz 0.8.2 is only available for amd64. All other archs are stuck with 0.7. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages compiz depends on: ii compiz-core 1:0.7.9+git20080918.shame-0 OpenGL window and compositing mana ii compiz-gnome 1:0.7.9+git20080918.shame-0 OpenGL window and compositing mana ii compiz-plugi 1:0.7.9+git20080918.shame-0 OpenGL window and compositing mana compiz recommends no packages. compiz suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523953: xserver-xorg-video-intel: Experimental version seems to work
Hi, I've just upgraded to version 2.7.0 and experience still the crashes. So no improvement on this aspect (though other, smaller bugs seem to have been fixed). Bye Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518673: marked as done (libidn_1.12-2(hppa/experimental): FTBFS: java not available on hppa)
Your message dated Thu, 16 Apr 2009 10:02:08 + with message-id e1luoq4-0006uu...@ries.debian.org and subject line Bug#518673: fixed in libidn 1.14-2 has caused the Debian Bug report #518673, regarding libidn_1.12-2(hppa/experimental): FTBFS: java not available on hppa 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.) -- 518673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libidn Version: 1.12-2 Severity: serious Hi, your package failed to build from source. Please only try to build the -java package on architectures that have a working java. | Automatic build of libidn_1.12-2 on meitner by sbuild/hppa 98-farm | Build started at 20090307-2122 | ** | Checking available source versions... | Fetching source files... | Reading package lists... | Building dependency tree... | Reading state information... | Need to get 2571kB of source archives. | Get:1 http://ftp2.de.debian.org experimental/main libidn 1.12-2 (dsc) [1262B] | Get:2 http://ftp2.de.debian.org experimental/main libidn 1.12-2 (tar) [2562kB] | Get:3 http://ftp2.de.debian.org experimental/main libidn 1.12-2 (diff) [7551B] | Fetched 2571kB in 8s (291kB/s) | Download complete and in download only mode | ** Using build dependencies supplied by package: | Build-Depends: debhelper (= 6), autotools-dev, gcj, fastjar | Checking for already installed source dependencies... | debhelper: missing | Using default version 7.2.2 (Priority: 500) | autotools-dev: missing | Using default version 20080123.2 (Priority: 500) | gcj: missing | No default version. Virtual package? | fastjar: missing | Using default version 2:0.97-3 (Priority: 500) | Checking for source dependency conflicts... | /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper autotools-dev gcj fastjar | Reading package lists... | Building dependency tree... | Reading state information... | Package gcj is not available, but is referred to by another package. | This may mean that the package is missing, has been obsoleted, or | is only available from another source | However the following packages replace it: | gcj-doc | E: Package gcj has no installation candidate | apt-get failed. | Package installation failed | Trying to reinstall removed packages: | Trying to uninstall newly installed packages: | Source-dependencies not satisfied; skipping libidn | ** | Finished at 20090307-2123 | Build needed 00:05:16, 0k disk space Full build log(s): http://experimental.ftbfs.de/build.php?ver=1.12-2pkg=libidnarch=hppa Gruesse, -- Frank Lichtenheld dj...@debian.org www: http://www.djpig.de/ ---End Message--- ---BeginMessage--- Source: libidn Source-Version: 1.14-2 We believe that the bug you reported is fixed in the latest version of libidn, which is due to be installed in the Debian FTP archive: idn_1.14-2_i386.deb to pool/main/libi/libidn/idn_1.14-2_i386.deb libidn11-dev_1.14-2_i386.deb to pool/main/libi/libidn/libidn11-dev_1.14-2_i386.deb libidn11-java_1.14-2_all.deb to pool/main/libi/libidn/libidn11-java_1.14-2_all.deb libidn11_1.14-2_i386.deb to pool/main/libi/libidn/libidn11_1.14-2_i386.deb libidn_1.14-2.diff.gz to pool/main/libi/libidn/libidn_1.14-2.diff.gz libidn_1.14-2.dsc to pool/main/libi/libidn/libidn_1.14-2.dsc 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 518...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Josefsson si...@josefsson.org (supplier of updated libidn package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 16 Apr 2009 09:07:32 +0200 Source: libidn Binary: idn libidn11-dev libidn11 libidn11-java Architecture: source i386 all Version: 1.14-2 Distribution: experimental Urgency: low Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Simon Josefsson si...@josefsson.org Description: idn- Command line and Emacs interface to GNU Libidn libidn11 - GNU Libidn library, implementation of IETF IDN specifications libidn11-dev - Development files for GNU
Bug#524308: marked as done (FTBFS: capplet-stock-icons.c:28:19: error: gnome.h: No such file or directory)
Your message dated Thu, 16 Apr 2009 09:32:07 + with message-id e1lunx1-0004kj...@ries.debian.org and subject line Bug#524308: fixed in control-center 1:2.24.0.1-4 has caused the Debian Bug report #524308, regarding FTBFS: capplet-stock-icons.c:28:19: error: gnome.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.) -- 524308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: control-center Version: 1:2.24.0.1-3 Severity: serious As seen on at least alpha, armel and amd64 buildd's. Possibly not the fault of control-center itself, but the dependency -chain is too complex for my mind to follow.. cc -DHAVE_CONFIG_H -I. -I../.. -DGNOMECC_DATA_DIR=\/usr/share/gnome-control-center\ -DGNOMELOCALEDIR=\/usr/share/locale\ -DGTK_ENGINE_DIR=\/usr/lib/gtk-2.0/2.10.0/engines\ -DG_LOG_DOMAIN=\capplet-common\ -DINSTALL_PREFIX=\/usr\ -I../.. -I../../libwindow-settings -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_REENTRANT -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -D_REENTRANT -I/usr/include/metacity-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-settings-daemon-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O2 -c capplet-stock-icons.c -fPIC -DPIC -o .libs/capplet-stock-icons.o capplet-stock-icons.c:28:19: error: gnome.h: No such file or directory capplet-stock-icons.c: In function 'capplet_register_stock_icons': capplet-stock-icons.c:64: warning: implicit declaration of function 'gnome_program_locate_file' capplet-stock-icons.c:64: error: 'GNOME_FILE_DOMAIN_APP_PIXMAP' undeclared (first use in this function) capplet-stock-icons.c:64: error: (Each undeclared identifier is reported only once capplet-stock-icons.c:64: error: for each function it appears in.) capplet-stock-icons.c:64: warning: assignment makes pointer from integer without a cast capplet-stock-icons.c:67: warning: implicit declaration of function '_' capplet-stock-icons.c:67: warning: passing argument 3 of 'g_log' makes pointer from integer without a cast make[4]: *** [capplet-stock-icons.lo] Error 1 make[4]: Leaving directory `/build/buildd/control-center-2.24.0.1/capplets/common' make[3]: *** [all-recursive] Error 1 ---End Message--- ---BeginMessage--- Source: control-center Source-Version: 1:2.24.0.1-4 We believe that the bug you reported is fixed in the latest version of control-center, which is due to be installed in the Debian FTP archive: capplets-data_2.24.0.1-4_all.deb to pool/main/c/control-center/capplets-data_2.24.0.1-4_all.deb control-center_2.24.0.1-4.diff.gz to pool/main/c/control-center/control-center_2.24.0.1-4.diff.gz control-center_2.24.0.1-4.dsc to pool/main/c/control-center/control-center_2.24.0.1-4.dsc gnome-control-center-dev_2.24.0.1-4_all.deb to pool/main/c/control-center/gnome-control-center-dev_2.24.0.1-4_all.deb gnome-control-center_2.24.0.1-4_amd64.deb to pool/main/c/control-center/gnome-control-center_2.24.0.1-4_amd64.deb libgnome-window-settings-dev_2.24.0.1-4_all.deb to pool/main/c/control-center/libgnome-window-settings-dev_2.24.0.1-4_all.deb libgnome-window-settings1_2.24.0.1-4_amd64.deb to pool/main/c/control-center/libgnome-window-settings1_2.24.0.1-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 524...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josselin Mouette j...@debian.org (supplier of updated control-center 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
Processed: found 523953 in 2:2.7.0-1
Processing commands for cont...@bugs.debian.org: found 523953 2:2.7.0-1 Bug#523953: xserver-xorg-video-intel: Xserver crash whenever playing high resolution video Bug marked as found in version 2:2.7.0-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524303: marked as done (python-elementtree: Fails to configure properly in Testing)
Your message dated Thu, 16 Apr 2009 11:47:02 +
with message-id e1luq3a-0006e8...@ries.debian.org
and subject line Bug#524303: fixed in elementtree 1.2.6-14
has caused the Debian Bug report #524303,
regarding python-elementtree: Fails to configure properly in 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.)
--
524303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-elementtree
Version: 1.2.6-13
Severity: normal
I'm upgrading python-elementtree in Testing from 1.2.6-12. I get this from
apt-get at the end:
Ställer in python-elementtree (1.2.6-13) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
update-python-modules [-v] [-c] package.dirs [...]
update-python-modules [-v] [-a|-f|-p]
update-python-modules: error:
/usr/share/python-support/python-elementtree.public is not a directory
dpkg: fel vid hantering av python-elementtree (--configure):
underprocess post-installation script gav felkod 2
Translated into English that's roughly:
Configuring python-elementtree (1.2.6-13) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
update-python-modules [-v] [-c] package.dirs [...]
update-python-modules [-v] [-a|-f|-p]
update-python-modules: error:
/usr/share/python-support/python-elementtree.public is not a directory
dpkg: error handling python-elementtree (--configure):
sub process post-installation script exited with error code 2
Regards //Johan
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-elementtree depends on:
ii python2.5.4-2An interactive high-level object-o
ii python-support0.8.7 automated rebuilding support for P
python-elementtree recommends no packages.
Versions of packages python-elementtree suggests:
pn python-elementtree-docnone (no description available)
-- no debconf information
---End Message---
---BeginMessage---
Source: elementtree
Source-Version: 1.2.6-14
We believe that the bug you reported is fixed in the latest version of
elementtree, which is due to be installed in the Debian FTP archive:
elementtree_1.2.6-14.diff.gz
to pool/main/e/elementtree/elementtree_1.2.6-14.diff.gz
elementtree_1.2.6-14.dsc
to pool/main/e/elementtree/elementtree_1.2.6-14.dsc
python-elementtree-doc_1.2.6-14_all.deb
to pool/main/e/elementtree/python-elementtree-doc_1.2.6-14_all.deb
python-elementtree_1.2.6-14_all.deb
to pool/main/e/elementtree/python-elementtree_1.2.6-14_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 524...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bernd Zeimetz b...@debian.org (supplier of updated elementtree package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 16 Apr 2009 12:12:02 +0200
Source: elementtree
Binary: python-elementtree python-elementtree-doc
Architecture: source all
Version: 1.2.6-14
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Bernd Zeimetz b...@debian.org
Description:
python-elementtree - Light-weight toolkit for XML processing
python-elementtree-doc - Documentation for ElementTree
Closes: 524303
Changes:
elementtree (1.2.6-14) unstable; urgency=high
.
[ Josselin Mouette ]
* Manually bump build-dependency and dependency on python-support to
1.0. The dependencies stay manual since ${python:Depends} would add
a dependency on python ( 2.5). Closes: #524303.
.
[ Bernd Zeimetz ]
* High urgency as the package can't be upgraded in testing.
* debian/rules, debian/control:
- Create python-support version dependency automatically.
- Replace CDBS by dh(7).
* debian/control:
- Lower build-dep on python-support again, as the proper Dependency
will be created automatically again.
Checksums-Sha1:
Bug#520410: uploading texlive new packages build with tex-common 1.18
On Di, 14 Apr 2009, Norbert Preining wrote: deb http://people.debian.org/~preining/TeX/ pool/ deb-src http://people.debian.org/~preining/TeX/ pool/ Ok, uploading now as anyway what we have now is much better than what we have currently in the archive, and FTBFS is a pain for others. We can fix more bugs on the way. Best wishes Norbert --- Dr. Norbert Preining prein...@logic.atVienna University of Technology Debian Developer prein...@debian.org Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- RUNCORN (n.) A peeble (q.v.) which is larger that a belper (q.v.) --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524331: marked as done (compiz: 0.8.2 only in amd64)
Your message dated Thu, 16 Apr 2009 13:47:41 +0200 with message-id 49e71add.6050...@ens-lyon.org and subject line Re: Bug#524331: compiz: 0.8.2 only in amd64 has caused the Debian Bug report #524331, regarding compiz: 0.8.2 only in amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 524331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: compiz Version: 1:0.7.9+git20080918.shame-0 Severity: grave Justification: renders package unusable Compiz 0.8.2 is only available for amd64. All other archs are stuck with 0.7. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages compiz depends on: ii compiz-core 1:0.7.9+git20080918.shame-0 OpenGL window and compositing mana ii compiz-gnome 1:0.7.9+git20080918.shame-0 OpenGL window and compositing mana ii compiz-plugi 1:0.7.9+git20080918.shame-0 OpenGL window and compositing mana compiz recommends no packages. compiz suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- notfound 524331 1:0.7.9+git20080918.shame-0 thank you Goncalo Marrafa wrote: Package: compiz Version: 1:0.7.9+git20080918.shame-0 Severity: grave Justification: renders package unusable Compiz 0.8.2 is only available for amd64. All other archs are stuck with 0.7. That's not a bug. Brice ---End Message---
Processed: Re: Bug#524331: compiz: 0.8.2 only in amd64
Processing commands for cont...@bugs.debian.org: notfound 524331 1:0.7.9+git20080918.shame-0 Bug#524331: compiz: 0.8.2 only in amd64 Bug no longer marked as found in version 1:0.7.9+git20080918.shame-0. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524127: [uscan] 'x509_user' not valid URI scheme at /usr/bin/uscan line 389
Hi Adam, Adam D. Barratt wrote: On Thu, 2009-04-16 at 02:45 +0200, Steffen Moeller wrote: the issue seems to be invariant of the watch file used. It still occurs. [...] $ set | grep -i proxy X509_USER_PROXY=/home/moeller/myproxy Aha! This seems to be due to a change made upstream in libwww-perl in version 5.821: croak on bad proxy args [RT#39919] This is easily confirmable by checking whether the following also fails for you: #! /usr/bin/perl use LWP::UserAgent; my $ua = LWP::UserAgent-new(env_proxy = 1); env_proxy is documented as reading environment variables of the form *_proxy. Your hunch did not fool you. $ perl a.pl 'x509_user' is not a valid URI scheme at a.pl line 3 It (including uscan) works with env_proxy = 0, but this obviously is not what you want. LWP maintainers - any thoughts? Should clients (e.g. uscan) be attempting to sanitise the proxy variables in the environment to only include those they specifically care about before using env_proxy? (or wrapping the call in an eval() and ignoring the specific error) That's obviously doable, but would need doing in every client individually, which seems somewhat overkill. Somehow it seems strange to reserve all _PROXY variably for oneself. Best, Steffen -- 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: clone 521027 -1 -2 Bug#521027: missing depends on net-tools in fai-client and fai-server Bug 521027 cloned as bugs 524346-524347. retitle -2 fai-client: replace ifconfig calls with ip command Bug#524347: missing depends on net-tools in fai-client and fai-server Changed Bug title to `fai-client: replace ifconfig calls with ip command' from `missing depends on net-tools in fai-client and fai-server'. severity -2 wishlist Bug#524347: fai-client: replace ifconfig calls with ip command Severity set to `wishlist' from `serious' -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520410: marked as done (texlive: pdflatex uses bitmap (Type 3) fonts in math formulas (bad pdftex.map?))
Your message dated Thu, 16 Apr 2009 12:32:54 +
with message-id e1luqly-0001lp...@ries.debian.org
and subject line Bug#520410: fixed in texlive-bin 2007.dfsg.2-6
has caused the Debian Bug report #520410,
regarding texlive: pdflatex uses bitmap (Type 3) fonts in math formulas (bad
pdftex.map?)
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.)
--
520410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: texlive
Version: 2007.dfsg.2-2
Severity: grave
Justification: renders package unusable
Since a recent upgrade, pdflatex now uses bitmap (Type 3) fonts in
math formulas (see very simple example under minimal input file).
As this is a serious regression (bitmap fonts look awful with some
tools), I've set the severity to grave.
FYI, here's the pdflatex and pdffonts output on this machine:
$ pdflatex bitmap-fonts.tex
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%-line parsing enabled.
entering extended mode
(./bitmap-fonts.tex
LaTeX2e 2005/12/01
Babel v3.8h and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, ukrainian, russian, bulgarian, basque, french, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo)) (./bitmap-fonts.aux)
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./bitmap-fonts.aux) )
/usr/share/texmf-texlive/fonts/pk/ljfour/public/cm/dpi600/cmmi10.pk
Output written on bitmap-fonts.pdf (1 page, 1752 bytes).
Transcript written on bitmap-fonts.log.
$ pdffonts bitmap-fonts.pdf
name type emb sub uni object ID
- --- --- --- -
[none] Type 3yes no no 4 0
On a Debian 4.0 machine, I get:
$ pdflatex bitmap-fonts.tex
This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5)
entering extended mode
(./bitmap-fonts.tex
LaTeX2e 2003/12/01
Babel v3.8g and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, croatian, ukrainian, russian, bulgarian, czech, slovak, danish, dut
ch, finnish, french, basque, german, ngerman, greek, monogreek, ancientgreek, i
bycus, hungarian, italian, latin, mongolian, norsk, slovene, estonian, welsh, i
nterlingua, icelandic, uppersorbian, romanian, indonesian, coptic, turkish, ser
bian, polish, portuguese, spanish, catalan, swedish, ukenglish, pinyin, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2004/02/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo)) (./bitmap-fonts.aux)
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./bitmap-fonts.aux) )/
usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmmi10.pfb
Output written on bitmap-fonts.pdf (1 page, 3302 bytes).
Transcript written on bitmap-fonts.log.
$ pdffonts bitmap-fonts.pdf
name type emb sub uni object ID
--- --- --- -
EENSUD+CMMI10Type 1 yes yes no 6 0
I wonder if there's a problem with the file
/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map
In case this matters:
$ grep -i cmmi10 /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map
aicmmi10 CMMI10 AITeXMathItalicEncoding ReEncodeFont aicmmi.enc cmmi10.pfb
cmmi10o CMMI10 .167 SlantFont cmmi10.pfb
and on the Debian 4.0 machine (where there are no problems):
$ grep -i cmmi10 /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map
aicmmi10 CMMI10 AITeXMathItalicEncoding ReEncodeFont aicmmi.enc cmmi10.pfb
cmmi10 CMMI10 cmmi10.pfb
cmmi10o CMMI10 .167 SlantFont cmmi10.pfb
Is it normal that the cmmi10 line is missing on the Debian/unstable
machine?
-- Package-specific info:
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report. Don't forget to also include minimal examples of
other files that are needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
Bug#520042: marked as done (texlive-base: Fails to generate formats on new installation(?))
Your message dated Thu, 16 Apr 2009 12:32:30 + with message-id e1luqla-0001iw...@ries.debian.org and subject line Bug#520042: fixed in texlive-base 2007.dfsg.2-3 has caused the Debian Bug report #520042, regarding texlive-base: Fails to generate formats on new installation(?) 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.) -- 520042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: texlive-base Version: 2007.dfsg.2-1 Severity: serious Justification: breaks package builds Since the upload of texlive-base version 2007.dfsg.2-1, I've started getting numerous build failures in packages that built before that upload (in particular, after the tex-common and texlive-extra updates last week, things were still working). For example, from my pbuilder build log for autogen: /usr/bin/make -C doc autogen.ps info make[1]: Entering directory `/tmp/buildd/autogen-5.9.7/doc' TEXINPUTS=../config:$TEXINPUTS \ MAKEINFO='/bin/sh /tmp/buildd/autogen-5.9.7/config/missing --run makeinfo -I../autoopts -I../autoopts -I .' \ texi2dvi autogen.texi This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) %-line parsing enabled. I can't find the format file `etex.fmt'! kpathsea: Running mktexfmt etex.fmt /usr/bin/texi2dvi: texinfo.tex appears to be broken, quitting. make[1]: *** [autogen.dvi] Error 1 make[1]: Leaving directory `/tmp/buildd/autogen-5.9.7/doc' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 (Never mind the local versions I have with +pb1 etc. -- I've verified this in a vanilla pbuilder chroot as well.) -- Daniel Schepler -- Package-specific info: If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.latex-einfuehrung.de/mini-en.html (english) or http://www.latex-einfuehrung.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 842 2009-03-16 16:45 /var/lib/texmf/ls-R -rw-rw-r-- 1 root staff 79 2009-03-16 16:44 /usr/local/share/texmf/ls-R lrwxrwxrwx 1 root root 29 2009-03-14 19:37 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 27 2009-03-16 16:44 /usr/share/texmf-texlive/ls-R - /var/lib/texmf/ls-R-TEXLIVE lrwxrwxrwx 1 root root 27 2009-03-16 16:44 /usr/share/texmf-texlive/ls-R - /var/lib/texmf/ls-R-TEXLIVE ## Config files lrwxrwxrwx 1 root root 20 2009-03-14 19:37 /usr/share/texmf/web2c/texmf.cnf - /etc/texmf/texmf.cnf -rw-r--r-- 1 root root 2866 2009-03-16 16:44 /var/lib/texmf/web2c/fmtutil.cnf -rw-r--r-- 1 root root 6272 2009-03-16 16:44 /var/lib/texmf/web2c/updmap.cfg -rw-r--r-- 1 root root 2092 2009-03-16 16:44 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 4 -rw-r--r-- 1 root root 283 2008-11-09 22:43 mktex.cnf ## md5sums of texmf.d 42c20d7e8bd343542772b5a145bf8ad8 /etc/texmf/texmf.d/05TeXMF.cnf 5f7f6652cc8b8071c9e4ea6ba9e9f0a1 /etc/texmf/texmf.d/15Plain.cnf f68e5add6afd6585b982f2f78e2e6a92 /etc/texmf/texmf.d/45TeXinputs.cnf ea33127256c6a9f37145ae5b16fdb80c /etc/texmf/texmf.d/55Fonts.cnf afccf1d3f87057411166a77c58e00bd1 /etc/texmf/texmf.d/65BibTeX.cnf 9da7c1c7b1eaf06f941af91f48a23068 /etc/texmf/texmf.d/75DviPS.cnf 7ae52efac46feb97010986e57877d12e /etc/texmf/texmf.d/80DVIPDFMx.cnf 37329819f1109e8a457e64b8b58fecdb /etc/texmf/texmf.d/85Misc.cnf a8952d594677235951d447665ec46e9c /etc/texmf/texmf.d/90TeXDoc.cnf 30f4f13357c2761ed01a6a15f28725a5 /etc/texmf/texmf.d/95NonPath.cnf -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Bug#520410: marked as done (texlive: pdflatex uses bitmap (Type 3) fonts in math formulas (bad pdftex.map?))
Your message dated Thu, 16 Apr 2009 12:32:30 +
with message-id e1luqla-0001iy...@ries.debian.org
and subject line Bug#520410: fixed in texlive-base 2007.dfsg.2-3
has caused the Debian Bug report #520410,
regarding texlive: pdflatex uses bitmap (Type 3) fonts in math formulas (bad
pdftex.map?)
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.)
--
520410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: texlive
Version: 2007.dfsg.2-2
Severity: grave
Justification: renders package unusable
Since a recent upgrade, pdflatex now uses bitmap (Type 3) fonts in
math formulas (see very simple example under minimal input file).
As this is a serious regression (bitmap fonts look awful with some
tools), I've set the severity to grave.
FYI, here's the pdflatex and pdffonts output on this machine:
$ pdflatex bitmap-fonts.tex
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%-line parsing enabled.
entering extended mode
(./bitmap-fonts.tex
LaTeX2e 2005/12/01
Babel v3.8h and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, ukrainian, russian, bulgarian, basque, french, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo)) (./bitmap-fonts.aux)
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./bitmap-fonts.aux) )
/usr/share/texmf-texlive/fonts/pk/ljfour/public/cm/dpi600/cmmi10.pk
Output written on bitmap-fonts.pdf (1 page, 1752 bytes).
Transcript written on bitmap-fonts.log.
$ pdffonts bitmap-fonts.pdf
name type emb sub uni object ID
- --- --- --- -
[none] Type 3yes no no 4 0
On a Debian 4.0 machine, I get:
$ pdflatex bitmap-fonts.tex
This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5)
entering extended mode
(./bitmap-fonts.tex
LaTeX2e 2003/12/01
Babel v3.8g and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, croatian, ukrainian, russian, bulgarian, czech, slovak, danish, dut
ch, finnish, french, basque, german, ngerman, greek, monogreek, ancientgreek, i
bycus, hungarian, italian, latin, mongolian, norsk, slovene, estonian, welsh, i
nterlingua, icelandic, uppersorbian, romanian, indonesian, coptic, turkish, ser
bian, polish, portuguese, spanish, catalan, swedish, ukenglish, pinyin, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2004/02/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo)) (./bitmap-fonts.aux)
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./bitmap-fonts.aux) )/
usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmmi10.pfb
Output written on bitmap-fonts.pdf (1 page, 3302 bytes).
Transcript written on bitmap-fonts.log.
$ pdffonts bitmap-fonts.pdf
name type emb sub uni object ID
--- --- --- -
EENSUD+CMMI10Type 1 yes yes no 6 0
I wonder if there's a problem with the file
/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map
In case this matters:
$ grep -i cmmi10 /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map
aicmmi10 CMMI10 AITeXMathItalicEncoding ReEncodeFont aicmmi.enc cmmi10.pfb
cmmi10o CMMI10 .167 SlantFont cmmi10.pfb
and on the Debian 4.0 machine (where there are no problems):
$ grep -i cmmi10 /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map
aicmmi10 CMMI10 AITeXMathItalicEncoding ReEncodeFont aicmmi.enc cmmi10.pfb
cmmi10 CMMI10 cmmi10.pfb
cmmi10o CMMI10 .167 SlantFont cmmi10.pfb
Is it normal that the cmmi10 line is missing on the Debian/unstable
machine?
-- Package-specific info:
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report. Don't forget to also include minimal examples of
other files that are needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
Bug#524314: [sysv-rc] Same problem
Package: sysv-rc Version: 2.86.ds1-61 --- Please enter the report below this line. --- I have the same problem: Preparando para reemplazar acpid 1.0.8-6 (usando .../acpid_1.0.8-7_i386.deb) ... * Stopping ACPI services... [ OK ] invoke-rc.d: initscript acpid, action stop failed. dpkg: aviso - script de `pre-removal' antiguo devolvió código de error 1 dpkg - probando el script del nuevo paquete en su lugar... * Stopping ACPI services... [ OK ] invoke-rc.d: initscript acpid, action stop failed. dpkg: error al procesar /var/cache/apt/archives/acpid_1.0.8-7_i386.deb (--unpack): el subproceso script pre-removal nuevo devolvió el código de salida de error 1 * Starting ACPI services... [ OK ] invoke-rc.d: initscript acpid, action start failed. dpkg: error al reorganizar: el subproceso post-installation script devolvió el código de salida de error 1 Se encontraron errores al procesar: /var/cache/apt/archives/acpid_1.0.8-7_i386.deb Then i rename /etc/init.d/acpid and tried again: Configurando acpid (1.0.8-7) ... * Stopping Hardware abstraction layer hald [ OK ] invoke-rc.d: initscript hal, action stop failed. dpkg: error al procesar acpid (--configure): el subproceso post-installation script devolvió el código de salida de error 1 Finally i also rename /etc/init.d/hal and it works. --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-2-686 Debian Release: squeeze/sid 500 testing ftp.us.debian.org 500 etch-wx apt.wxwidgets.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== |
Bug#523903: marked as done (arandr only works with RandR 1.2 while unstable has RandR 1.3)
Your message dated Thu, 16 Apr 2009 13:32:03 + with message-id e1lurhd-0005tf...@ries.debian.org and subject line Bug#523903: fixed in arandr 0.1.2-1 has caused the Debian Bug report #523903, regarding arandr only works with RandR 1.2 while unstable has RandR 1.3 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.) -- 523903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: arandr Version: 0.1.1-2 Severity: grave Justification: renders package unusable Hey, this package is mostly useless now that we have RandR 1.3: cor...@hidalgo: arandr Traceback (most recent call last): File /usr/bin/arandr, line 5, in module main() File /usr/lib/python2.5/site-packages/screenlayout/gui.py, line 296, in main Application(file=file_to_open, randr_display=options.randr_display).run() File /usr/lib/python2.5/site-packages/screenlayout/gui.py, line 135, in __init__ self.widget = widget.ARandRWidget(display=randr_display) File /usr/lib/python2.5/site-packages/screenlayout/widget.py, line 30, in __init__ self._xrandr = XRandR(display=display) File /usr/lib/python2.5/site-packages/screenlayout/xrandr.py, line 22, in __init__ raise Exception(XRandR 1.2 required; for newer versions please adapt the code) Exception: XRandR 1.2 required; for newer versions please adapt the code I'm not sure how much the code needs to be adapted, but at the moment it's just useless, and upstream doesn't seem really aware of that (no new upstream version for the moment). Should arandr just be dropped? It was a nice tool, but… Cheers, -- Yves-Alexis -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages arandr depends on: ii python2.5.4-2An interactive high-level object-o ii python-gtk2 2.14.1-2 Python bindings for the GTK+ widge ii x11-xserver-utils 7.4+2 X server utilities arandr recommends no packages. arandr suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: arandr Source-Version: 0.1.2-1 We believe that the bug you reported is fixed in the latest version of arandr, which is due to be installed in the Debian FTP archive: arandr_0.1.2-1.diff.gz to pool/main/a/arandr/arandr_0.1.2-1.diff.gz arandr_0.1.2-1.dsc to pool/main/a/arandr/arandr_0.1.2-1.dsc arandr_0.1.2-1_all.deb to pool/main/a/arandr/arandr_0.1.2-1_all.deb arandr_0.1.2.orig.tar.gz to pool/main/a/arandr/arandr_0.1.2.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 523...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian M. Amsüss chr...@fsfe.org (supplier of updated arandr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 13 Apr 2009 17:00:17 +0200 Source: arandr Binary: arandr Architecture: source all Version: 0.1.2-1 Distribution: unstable Urgency: low Maintainer: Christian M. Amsüss chr...@fsfe.org Changed-By: Christian M. Amsüss chr...@fsfe.org Description: arandr - Simple visual front end for XRandR 1.2 Closes: 523903 Changes: arandr (0.1.2-1) unstable; urgency=low . * New release (closes: #523903) + Accepts XRandR version 1.3 + New command line switch to accept untested versions * Change Standards-Version to 3.8.1 (no changes) Checksums-Sha1: 93930bff8497fad5fdcb726b16dd885483777378 1025 arandr_0.1.2-1.dsc 9d74fe4f664b31cfb668b7e3da8bb4f5889e5198 42288 arandr_0.1.2.orig.tar.gz f06548722dfde7ac6949313d1861981c3da6b359 1722 arandr_0.1.2-1.diff.gz 5ae20251b54620e40f71b37254f9578e96cd8b45 31038 arandr_0.1.2-1_all.deb Checksums-Sha256: ebc66001d941118f60bf74e89e849563b5b109f87bd487941879f26db0b8f4d2 1025 arandr_0.1.2-1.dsc dc3a1061238784192f35917643b2d63b44b85810a160bf75f711149923ad8142 42288 arandr_0.1.2.orig.tar.gz dc89bb56414b23e40df55612e274b2d6b11d9e06543ea46c7e7e3b5ea4842895
Bug#520338: Resolution
It looks like the sqlite3 change that introduced these issues was reverted in a later version; INDEXED is no longer a keyword. Thus, a bumped dependency should take care of this problem; I'll try to track down exactly what version is required later today, and get a fixed version uploaded ASAP. -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524346: marked as done (missing depends on net-tools in fai-client and fai-server)
Your message dated Thu, 16 Apr 2009 16:26:07 +0200 with message-id 18919.16383.81401.555...@suenner.informatik.uni-koeln.de and subject line error during cloning has caused the Debian Bug report #524346, regarding missing depends on net-tools in fai-client and fai-server 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.) -- 524346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: fai-client severity: serious tags patch Hi, memory is faulty, the bts not. On Samstag, 21. März 2009, Luk Claes wrote: Below a list of packages/maintainers that use ifconfig/route/netstat: How did you create that list? You seem to be missing a few.. fai uses it in three binary packages: fai-server, fai-client and fai-doc. I'll follow up on this on the fai-list. regards, Holger Index: debian/control === --- debian/control (Revision 5292) +++ debian/control (Arbeitskopie) @@ -13,7 +13,7 @@ Package: fai-client Architecture: all Section: admin -Depends: perl, file, libapt-pkg-perl, libparse-recdescent-perl, liblinux-lvm-perl +Depends: perl, file, libapt-pkg-perl, libparse-recdescent-perl, liblinux-lvm-perl, net-tools Recommends: debconf-utils, cfengine2 Suggests: ntfsprogs, dmsetup, cryptsetup Conflicts: fai, fai-kernels @@ -46,7 +46,7 @@ Architecture: all Section: admin Depends: fai-client, debootstrap -Recommends: nfs-kernel-server, dhcp3-server | bootp, tftpd-hpa | tftpd, openssh-server, openssh-client, syslinux-common, openbsd-inetd | inet-superserver +Recommends: nfs-kernel-server, dhcp3-server | bootp, tftpd-hpa | tftpd, openssh-server, openssh-client, syslinux-common, openbsd-inetd | inet-superserver, net-tools Suggests: debmirror, apt-move, genisoimage, grub, aptitude, perl-tk, libproc-daemon-perl Conflicts: fai Replaces: fai Index: debian/changelog === --- debian/changelog (Revision 5292) +++ debian/changelog (Arbeitskopie) @@ -54,6 +54,9 @@ initialization of encrypted partitions configurable * setup-storage.8: Document new encryption possibilities + [ Holger Levsen ] + * Add depends to net-tools to fai-server and fai-client. + -- Thomas Lange la...@debian.org Sun, 23 Feb 2009 15:55:55 +0100 (3.2.17) unstable; urgency=medium signature.asc Description: This is a digitally signed message part. ---End Message--- ---BeginMessage--- I made a mistake during cloning. I created one clone to many, genetics is dangerous :-) -- regards Thomas ---End Message---
Processed: forcibly merging 523187 524316
Processing commands for cont...@bugs.debian.org: forcemerge 523187 524316 Bug#523187: invoke-rc.d: initscript, action start failed on install Bug#524316: acpid fails to upgrade Bug#523823: [hal] Upgrade of hal fails Forcibly Merged 523187 523823 524316. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 523187 524317
Processing commands for cont...@bugs.debian.org: forcemerge 523187 524317 Bug#523187: invoke-rc.d: initscript, action start failed on install Bug#524317: acpid: Won't upgrade Bug#523823: [hal] Upgrade of hal fails Bug#524316: acpid fails to upgrade Forcibly Merged 523187 523823 524316 524317. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481786: ttf2tex: freetype1 deprecation
Rafael, My apologies but I cannot see keeping freetype1 in Debian just for ttf2tex. Especially since ttf2tex has not been part of any recent stable releases. Do you have any other thoughts or options before I request removal of freetype1 and probably ttf2tex? Thanks and sorry, Barry deFreese Debian QA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524371: Starting pbbuttonsd:ERROR: The object '/etc/power/pmcs-pbbuttonsd' doesn't exist.
Package: pbbuttonsd Version: 0.7.9-2 Severity: grave Justification: renders package unusable pbbuttonsd no longer works: Starting pbbuttonsd:ERROR: The object '/etc/power/pmcs-pbbuttonsd' doesn't exist. failed! Indeed: ay:/home/lefevre# ls -l /etc/power total 8 drwxr-xr-x 2 root root 4096 2009-04-16 17:40:23 event.d drwxr-xr-x 2 root root 4096 2009-04-16 17:40:43 scripts.d -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (500, 'oldstable'), (200, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.26-1-powerpc Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages pbbuttonsd depends on: ii hdparm8.9-3 tune hard disk parameters for high ii libasound21.0.19-1 shared library for ALSA applicatio ii libc6 2.9-4 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-3 GCC support library ii libglib2.0-0 2.20.0-2 The GLib library of C routines ii libstdc++64.3.3-3The GNU Standard C++ Library v3 ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-88 creates device files in /dev ii udev 0.125-7+lenny1 /dev/ and hotplug management daemo Versions of packages pbbuttonsd recommends: pn laptop-mode-tools none (no description available) pbbuttonsd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523903: arandr only works with RandR 1.2 while unstable has RandR 1.3
On Mon, 2009-04-13 at 16:27 +0200, Christian M.Amsüss wrote: On Mon, Apr 13, 2009 at 02:28:20PM +0200, Yves-Alexis Perez wrote: I'm not sure how much the code needs to be adapted, but at the moment it's just useless, and upstream doesn't seem really aware of that (no new upstream version for the moment). Should arandr just be dropped? It was a nice tool, but… i have just upgraded myself and seen this. i am in the progress of writing a patch, which i expect to be just a line or two since 1.3 seems to be fully compatible. erroring out on any 1.x version is braindead. incompatible changes won't happen as long as the major stays the same. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524295: why the dep is needed...
As far as I can tell OOo does not use any headers from colamd either but the mere fact that it is linked to by lpsolve seems to make it needed to be linked further up the chain. At least according to this patch, which afaik you wrote, including the reason for the change: patches/dev300/system-lpsolve-link-with-colamd.diff Index: makefile.mk === RCS file: /cvs/sc/sccomp/source/solver/makefile.mk,v retrieving revision 1.3 diff -u -u -r1.3 makefile.mk --- sccomp/source/solver/makefile.mk11 Apr 2008 10:47:12 - 1.3 +++ sccomp/source/solver/makefile.mk23 Apr 2008 19:24:41 - @@ -70,6 +70,12 @@ RESLIB1LIST=$(SRS)$/solver.srs +# DebianBaseOnly; we build lp_solve without colamd included but with system-colamd +# (which is not linked into the .a...) so we need -lcolamd here, too +.IF $(SYSTEM_LPSOLVE) == YES +SHL1STDLIBS += -lcolamd +.ENDIF + RESLIB1NAME=solver RESLIB1SRSFILES=$(RESLIB1LIST) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506009: marked as done (maq: gzopen64 implicitly converted to pointer)
Your message dated Thu, 16 Apr 2009 15:17:37 + with message-id e1lutln-0005r9...@ries.debian.org and subject line Bug#506009: fixed in maq 0.7.1-2 has caused the Debian Bug report #506009, regarding maq: gzopen64 implicitly converted to pointer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: maq Version: 0.7.1-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `gzopen64' implicitly converted to pointer at fastq2bfq.c:30 Function `gzopen64' implicitly converted to pointer at maqmap_conv.c:57 Function `gzopen64' implicitly converted to pointer at simulate.c:83 Function `gzopen64' implicitly converted to pointer at break_pair.c:16 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions ---End Message--- ---BeginMessage--- Source: maq Source-Version: 0.7.1-2 We believe that the bug you reported is fixed in the latest version of maq, which is due to be installed in the Debian FTP archive: maq_0.7.1-2.diff.gz to pool/main/m/maq/maq_0.7.1-2.diff.gz maq_0.7.1-2.dsc to pool/main/m/maq/maq_0.7.1-2.dsc maq_0.7.1-2_i386.deb to pool/main/m/maq/maq_0.7.1-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 506...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated maq package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 16 Apr 2009 15:56:09 +0200 Source: maq Binary: maq Architecture: source i386 Version: 0.7.1-2 Distribution: unstable Urgency: low Maintainer: Debian-Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: maq- maps short fixed-length polymorphic DNA sequence reads to referen Closes: 506009 Changes: maq (0.7.1-2) unstable; urgency=low . * Enable LARGEFILE64_SOURCE to prevent a problem with zlib on 64bit archs (Thanks to Peter Green plugw...@p10link.net for the patch) Closes: #506009 * Standards-Version: 3.8.1 (no changes needed) Checksums-Sha1: 9892e9aadc439869ed10f81fd46e5a3317b54aa3 1280 maq_0.7.1-2.dsc f78698879046f6286e1f6cdf814cee54e955c2e3 5039 maq_0.7.1-2.diff.gz ff084477b39643dece418fcb108eb51e663ebfbe 326510 maq_0.7.1-2_i386.deb Checksums-Sha256: d65ee50bc355d2e3e968dac67cf4e23d83d94ebb6100116f56e8cf44fe9fa8cd 1280 maq_0.7.1-2.dsc 52b88ded35f79b10ca74db5dd5e5c50596ae58e699a8e0d12da98ae7a033420b 5039 maq_0.7.1-2.diff.gz d8353373cad0111d575c5d659d2c7022644e6970cb617cf0530e6e243b373d53 326510 maq_0.7.1-2_i386.deb Files: a1ff0203f99fee61e840de0d633c50b9 1280 science optional maq_0.7.1-2.dsc ca2e914451e7501cd469f5b526722be1 5039 science optional maq_0.7.1-2.diff.gz 29fe97ca84aaf984b40f98135d454c84 326510 science optional maq_0.7.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ5zn0YDBbMcCf01oRAuj+AJ9EAHDwJU7daSs4OuaD0jKeAZ10dACgkMkb 8WTcmtIQI7swR34SjLtLJd8= =TLXW -END PGP SIGNATURE- ---End Message---
Bug#524373: linux-2.6: /dev/mem rootkit vulnerability
package: linux-2.6 severity: grave tags: security as seen in recent articles and discussions, the linux kernel is currently vulnerable to rootkit attacks via the /dev/mem device. one article [1] mentions that there is an existing patch for the problem, but does not link to it. perhaps this fix can be found in the kernel mailing lists. [1] http://www.darkreading.com/security/vulnerabilities/showArticle.jhtml?articleID=216500687 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 521027
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 521027 + pending Bug#521027: missing depends on net-tools in fai-client and fai-server There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merge powerpc bug
Processing commands for cont...@bugs.debian.org: reassign 522666 linux-2.6 Bug#522666: linux-image-2.6.29-1-powerpc: run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Bug reassigned from package `linux-image-2.6.29-1-powerpc' to `linux-2.6'. forcemerge 518231 522666 Bug#518231: linux-image-2.6.28-1-powerpc: Fails to configure due to a debconf error Bug#522666: linux-image-2.6.29-1-powerpc: run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Forcibly Merged 518231 522666. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: this bug does not seem to be present in version 1.2.6-12
Processing commands for cont...@bugs.debian.org: notfound 524303 1.2.6-12 Bug#524303: python-elementtree: Fails to configure properly in Testing Bug no longer marked as found in version 1.2.6-12. (By the way, this Bug is currently marked as done.) thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524373: marked as done (linux-2.6: /dev/mem rootkit vulnerability)
Your message dated Thu, 16 Apr 2009 09:36:50 -0700 with message-id 20090416163650.ga28...@dario.dodds.net and subject line Re: Bug#524373: linux-2.6: /dev/mem rootkit vulnerability has caused the Debian Bug report #524373, regarding linux-2.6: /dev/mem rootkit vulnerability 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.) -- 524373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: linux-2.6 severity: grave tags: security as seen in recent articles and discussions, the linux kernel is currently vulnerable to rootkit attacks via the /dev/mem device. one article [1] mentions that there is an existing patch for the problem, but does not link to it. perhaps this fix can be found in the kernel mailing lists. [1] http://www.darkreading.com/security/vulnerabilities/showArticle.jhtml?articleID=216500687 ---End Message--- ---BeginMessage--- On Thu, Apr 16, 2009 at 11:55:05AM -0400, Michael S. Gilbert wrote: package: linux-2.6 severity: grave tags: security as seen in recent articles and discussions, the linux kernel is currently vulnerable to rootkit attacks via the /dev/mem device. one article [1] mentions that there is an existing patch for the problem, but does not link to it. perhaps this fix can be found in the kernel mailing lists. There is no security bug here. /dev/mem functions as designed. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org ---End Message---
Bug#524373: linux-2.6: /dev/mem rootkit vulnerability
On Thu, Apr 16, 2009 at 11:55:05AM -0400, Michael S. Gilbert wrote: as seen in recent articles and discussions, the linux kernel is currently vulnerable to rootkit attacks via the /dev/mem device. one article [1] mentions that there is an existing patch for the problem, but does not link to it. perhaps this fix can be found in the kernel mailing lists. There's no vulnerability there. /dev/mem is only writable by root. The research (if there's really any research involved) just shows how you could hide files or processes by manipulating /dev/mem. That's been known for ages. That's why you don't let your users write to /dev/mem. If the attacker has root, who cares what means they use to hide their precese, you've already lost. noah signature.asc Description: Digital signature
Bug#524373: linux-2.6: /dev/mem rootkit vulnerability
severity 524373 wishlist thanks On Thu, Apr 16, 2009 at 11:55:05AM -0400, Michael S. Gilbert wrote: package: linux-2.6 severity: grave tags: security as seen in recent articles and discussions, the linux kernel is currently vulnerable to rootkit attacks via the /dev/mem device. one article [1] mentions that there is an existing patch for the problem, but does not link to it. perhaps this fix can be found in the kernel mailing lists. This isn't a hole - it just describes a proof of concept of an already-known way to hide yourself once you've already gained escalated privileges on a system. The fix referred to is presumably the CONFIG_STRICT_DEVMEM option (formally CONFIG_NONPROMISC_DEVMEM). This option is included, but not enabled, in the Debian 5.0.0 kernel. It is unlikely to get enabled within a stable release because it will be disabling an interface that existing applications may rely upon (the crash application is one I can think of, off the top of my head). However, this option is enabled in the 2.6.29 kernel available in sid. -- dann frazier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
Processing commands for cont...@bugs.debian.org: reassign 524314 splashy Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed Bug reassigned from package `sysv-rc' to `splashy'. retitle 524314 splashy causes init scripts to exit with error Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed Changed Bug title to `splashy causes init scripts to exit with error' from `[sysv-rc] Sysv-rc always reports that actions failed'. tags 524314 - moreinfo Bug#524314: splashy causes init scripts to exit with error Tags were: moreinfo Tags removed: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed
reassign 524314 splashy retitle 524314 splashy causes init scripts to exit with error tags 524314 - moreinfo thanks On Thursday 16 April 2009 19:50:38 Carlo Aquilini wrote: Il giorno gio, 16/04/2009 alle 19.18 +1000, Kel Modderman ha scritto: I installed the freepops package to investigate, and then run the following commands: r...@nomad:/home/kelmo# invoke-rc.d freepops start Starting freepops daemon: freepopsd. r...@nomad:/home/kelmo# invoke-rc.d freepops stop Stopping freepops daemon: freepopsd. r...@nomad:/home/kelmo# The output look a little different to yours, and I cannot reproduce the failure. Thanks, Kel. Looking to your output (without the [OK]) I realized which is the problem...splashy. Purging splashy the problem is gone and the upgrade is perfect. This information needs to be on the bug report, CC'ing. Please can you reassign this bug to splashy? I can't do it. Ok. Thanks, Kel.
Bug#524247: marked as done (cryptokit_1.3-11(mips/unstable):)
Your message dated Thu, 16 Apr 2009 16:47:03 + with message-id e1luujv-0003te...@ries.debian.org and subject line Bug#524247: fixed in cryptokit 1.3-12 has caused the Debian Bug report #524247, regarding cryptokit_1.3-11(mips/unstable): to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 524247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cryptokit Version: 1.3-11 Severity: serious There was an error while trying to autobuild your package: Automatic build of cryptokit_1.3-11 on mayr by sbuild/mips 99.999 Build started at 20090412-1619 [...] ** Using build dependencies supplied by package: Build-Depends: cdbs (= 0.4.23-1.1), ocaml-nox (= 3.11), debhelper (= 7), zlib1g-dev, dpkg-dev (= 1.13.19), dh-ocaml [...] ocamlc -g -c -ccopt -g -O2 -g -Wall -O2 -DHAVE_ZLIB stubs-misc.c ocamlc -g -c -ccopt -g -O2 -g -Wall -O2 -DHAVE_ZLIB stubs-rng.c ocamlmklib -o cryptokit rijndael-alg-fst.o stubs-aes.o d3des.o stubs-des.o arcfour.o stubs-arcfour.o sha1.o stubs-sha1.o sha256.o stubs-sha256.o ripemd160.o stubs-ripemd160.o stubs-md5.o stubs-zlib.o stubs-misc.o stubs-rng.o -L/usr/lib -lz ocamlc -g -c cryptokit.mli ocamlc -g -c cryptokit.ml File cryptokit.ml, line 2076, characters 10-19: Warning Y: unused variable avail_out. ocamlmklib -o cryptokit cryptokit.cmo -L/usr/lib -lz make[1]: Leaving directory `/build/buildd/cryptokit-1.3' touch debian/stamp-makefile-build DEB_MAKE_CHECK_TARGET unset, not running checks ocamlopt -I . -shared -linkall -o cryptokit.cmxs cryptokit.cmxa make: ocamlopt: Command not found make: *** [build/libcryptokit-ocaml] Error 127 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=mipspkg=cryptokitver=1.3-11 ---End Message--- ---BeginMessage--- Source: cryptokit Source-Version: 1.3-12 We believe that the bug you reported is fixed in the latest version of cryptokit, which is due to be installed in the Debian FTP archive: cryptokit_1.3-12.diff.gz to pool/main/c/cryptokit/cryptokit_1.3-12.diff.gz cryptokit_1.3-12.dsc to pool/main/c/cryptokit/cryptokit_1.3-12.dsc libcryptokit-ocaml-dev_1.3-12_i386.deb to pool/main/c/cryptokit/libcryptokit-ocaml-dev_1.3-12_i386.deb libcryptokit-ocaml_1.3-12_i386.deb to pool/main/c/cryptokit/libcryptokit-ocaml_1.3-12_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 524...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mehdi Dogguy dog...@pps.jussieu.fr (supplier of updated cryptokit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 15 Apr 2009 22:31:51 +0200 Source: cryptokit Binary: libcryptokit-ocaml libcryptokit-ocaml-dev Architecture: source i386 Version: 1.3-12 Distribution: unstable Urgency: low Maintainer: Debian OCaml Maintainers debian-ocaml-ma...@lists.debian.org Changed-By: Mehdi Dogguy dog...@pps.jussieu.fr Description: libcryptokit-ocaml - cryptographic algorithm library for OCaml - runtime libcryptokit-ocaml-dev - cryptographic algorithm library for OCaml - development Closes: 524247 Changes: cryptokit (1.3-12) unstable; urgency=low . * Used ifeq instead of ifdef in debian/rules: a variable can be defined and empty. Fixes FTBFS on non-native archs, Closes: #524247. * Add myself to Uploaders. Checksums-Sha1: 36e6dcd33d312d6636c21e78345ab53d354ee897 1636 cryptokit_1.3-12.dsc 35ed87ca526fd4f0b4526eeb87c94ffd4035758e 5680 cryptokit_1.3-12.diff.gz a1dc54d1b2a0e8db484bd5940397449b523a58e1 283166 libcryptokit-ocaml_1.3-12_i386.deb bd42e0109bb4a237e5164a0d36898092ca530eeb 110520 libcryptokit-ocaml-dev_1.3-12_i386.deb Checksums-Sha256: aaeb1eba2a0b4a9ab6d9e6ee18578169907ff0963904b314fc5e369192ad4bb9 1636 cryptokit_1.3-12.dsc 69e7c560adc475667893ad80508c85e3ead46b6a47e2e74968529e060640196f 5680 cryptokit_1.3-12.diff.gz 3716823542064379c410deaf04a2de9ac1f5353e2fc38221725b24d46cd0078e 283166 libcryptokit-ocaml_1.3-12_i386.deb ccea70fedea12f73fee875574206bb46ec5ffc590f37cbe81da4bb38bd3f0b0c 110520 libcryptokit-ocaml-dev_1.3-12_i386.deb Files:
Bug#523675: r-base: FTBFS on alpha
On Sat, Apr 11, 2009 at 04:31:35PM -0500, Dirk Eddelbuettel wrote: | | I guess you mean albeniz. I'm now there building a patches gcc. Patched gcc -- so you have a suspected fix for gcc? Cool! A fixed gcc has been uploaded now. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524385: tetradraw: FTBFS: ld: cannot find -lncurses
Source: tetradraw Version: 2.0.3-6 Severity: serious Hi, Your package is failing to build with the following error: /bin/sh ../libtool --mode=link gcc -g -O2 -D_GNU_SOURCE -L../src -o tetradraw block.o editor.o interface.o internal.o load.o multidraw.o network.o options_io.o sauce.o save.o term.o tetradraw.o -lncurses -lmenu mkdir .libs gcc -g -O2 -D_GNU_SOURCE -o tetradraw block.o editor.o interface.o internal.o load.o multidraw.o network.o options_io.o sauce.o save.o term.o tetradraw.o -L/build/buildd/tetradraw-2.0.3/src -lncurses -lmenu /usr/bin/ld: cannot find -lncurses collect2: ld returned 1 exit status Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523953: Subject: xserver-xorg-video-intel: New unstable version does not solve bug
Package: xserver-xorg-video-intel Version: 2:2.7.0-1 Hi, on my 945GM problem is fixed with 2.7.0-1. mplayer/vlc/totem plays the HD videos fine. No full-screen slowness as Apelete mentioned. Thanks. -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524386: apt-watch: FTBFS: error: glade/glade-xml.h: No such file or directory
Source: apt-watch Version: 0.3.2-10 Severity: serious Hi, Your package is failing to build with the following error: apt-watch-gnome.cc:9:29: error: glade/glade-xml.h: No such file or directory apt-watch-gnome.cc: In function 'void bonobo_about(BonoboUIComponent*, void*, const char*)': apt-watch-gnome.cc:274: error: 'GladeXML' was not declared in this scope apt-watch-gnome.cc:274: error: 'xml' was not declared in this scope apt-watch-gnome.cc:276: error: 'glade_xml_new' was not declared in this scope apt-watch-gnome.cc:278: error: 'glade_xml_signal_autoconnect' was not declared in this scope apt-watch-gnome.cc: In function 'void do_notify(PanelApplet*)': apt-watch-gnome.cc:737: error: 'GladeXML' was not declared in this scope apt-watch-gnome.cc:737: error: 'xml' was not declared in this scope apt-watch-gnome.cc:740: error: 'glade_xml_new' was not declared in this scope apt-watch-gnome.cc:742: error: 'glade_xml_signal_autoconnect' was not declared in this scope apt-watch-gnome.cc:744: error: 'glade_xml_get_widget' was not declared in this scope make[4]: *** [apt-watch-gnome.o] Error 1 Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524387: gnuradio: FTBFS: gr_local_sighandler.cc:38: error: 'memset' was not declared in this scope
Source: gnuradio Version: 3.0.4-2 Severity: serious Hi, Your package is failing to build with the following error: gr_local_sighandler.cc: In constructor 'gr_local_sighandler::gr_local_sighandler(int, void (*)(int))': gr_local_sighandler.cc:38: error: 'memset' was not declared in this scope make[6]: *** [gr_local_sighandler.lo] Error 1 Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523213: marked as done (/etc/cron.daily/apt does not check return code of date)
Your message dated Thu, 16 Apr 2009 20:43:12 +0200 with message-id 200904162043.14305.th...@debian.org and subject line fixed in 0.7.21 has caused the Debian Bug report #523213, regarding /etc/cron.daily/apt does not check return code of date 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.) -- 523213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apt Version: 0.7.20.2 Severity: grave Tags: security patch Justification: user security hole The following is also being sent to oss-secur...@lists.openwall.com for a CVE request. Summary --- Systems in certain timezones with automatic updates enabled won't be upgraded on the first day of DST and some systems in affected timezones could end up with automatic updates being disabled permanently. Normal usage of apt is not affected. Discovery credited to: Alexandre Martani Public bug: https://launchpad.net/bugs/354793 The Problem --- The problem arises because the date command errors out on dates/times that are invalid. Eg, DST starts at 03:00 in the Central time zone of the US: $ date --date=2009-03-08 02:00:00 date: invalid date `2009-03-08 02:00:00' This is fine and in and of itself not a problem. However, /etc/cron.daily/apt has: stamp=$(date --date=$(date -r $stamp --iso-8601) +%s) now=$(date --date=$(date --iso-8601) +%s) '--iso-8601' creates dates of the form -MM-DD. Since this is then fed into the date command, the hour, minute and second all default to 0. Some timezones start their DST at midnight, with America/Sao_Paulo as one example. Eg, on a system configured to use the America/Sao_Paulo timezone: $ date --date=2009-10-18 date: invalid date `2009-10-18' This condition causes 'delta=$(($now-$stamp))' in check_stamp() to fail when $stamp is empty (returning non-zero) or for when $now is empty, '$delta -ge $interval' evaluates to false because delta is negative (return non-zero). Either condition results in all or part of the automatic update process to not be performed. Affected Users -- For users in timezones with DST starting at midnight with automatic updates enabled, this can lead to the following error conditions: 1. /etc/cron.daily/apt is run on the first day of the DST, resulting in '$delta -ge $interval' being negative because 'now' is empty and the automatic update is not run. The timestamps are not updated, so the automatic update will occur normally the following day. 2. /etc/cron.daily/apt is run late in the day on the day prior to DST (eg 23:59 on 2009-10-17) and finishes on the day of DST (eg one minute later, at 01:00 on 2009-10-18). This will update the stamp files to have the date of the DST. At this point, apt cannot recover and automatic updates are disabled until manually updating/removing the stamp files. 3. A user using a non-affected timezone and has /etc/cron.daily/apt run normally on the day of the DST. Sometime after that, but before /etc/cron.daily/apt runs again, the user changes her timezone to an affected timezone. At this point, apt cannot recover and automatic updates are disabled until manually updating/removing the stamp files. While all users in scenario '1' are affected, they will eventually get their updates. Though the number of users in '2' and especially '3' are presumed low, the impact for these users is very high, since the expected, automatic security updates will never be applied. The Fix --- The fix is simply to check the return codes of date, and return '0' if the date for 'now' fails, and remove the bad stamp file and return '0' if the date for 'stamp' fails. A patch is attached to the Ubuntu bug, though I have contacted the Debian and Ubuntu maintainer directly and he is working on an update for the development releases of Debian and Ubuntu. Thanks, Jamie -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-11-generic (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages apt depends on: ii debian-archive-keyring2009.01.31 GnuPG archive keys of the Debian a ii libc6 2.9-7 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-5 GCC support library ii libstdc++64.3.3-5The GNU Standard
Bug#516964: marked as done (jaula_1.3.0-4(mips/unstable): FTBFS - documentation fails to build)
Your message dated Thu, 16 Apr 2009 18:32:07 + with message-id e1luwnb-0003eo...@ries.debian.org and subject line Bug#516964: fixed in jaula 1.4.0-2 has caused the Debian Bug report #516964, regarding jaula_1.3.0-4(mips/unstable): FTBFS - documentation fails to build 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.) -- 516964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jaula Version: 1.3.0-4 Severity: serious There was an error while trying to autobuild your package: Automatic build of jaula_1.3.0-4 on mayr by sbuild/mips 99.999 Build started at 20090224-0211 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5), flex, doxygen, texlive, ghostscript, texinfo [...] ! == Fatal error occurred, no output PDF file produced! Transcript written on refman.log. make[5]: *** [refman.pdf] Error 1 make[5]: Leaving directory `/build/buildd/jaula-1.3.0/doc/latex' make[4]: *** [doc] Error 2 make[4]: Leaving directory `/build/buildd/jaula-1.3.0/doc' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd/jaula-1.3.0/doc' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/jaula-1.3.0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/jaula-1.3.0' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=mipspkg=jaulaver=1.3.0-4 ---End Message--- ---BeginMessage--- Source: jaula Source-Version: 1.4.0-2 We believe that the bug you reported is fixed in the latest version of jaula, which is due to be installed in the Debian FTP archive: jaula_1.4.0-2.diff.gz to pool/main/j/jaula/jaula_1.4.0-2.diff.gz jaula_1.4.0-2.dsc to pool/main/j/jaula/jaula_1.4.0-2.dsc jparse_1.4.0-2_i386.deb to pool/main/j/jaula/jparse_1.4.0-2_i386.deb libjaula-dev_1.4.0-2_i386.deb to pool/main/j/jaula/libjaula-dev_1.4.0-2_i386.deb libjaula-doc_1.4.0-2_i386.deb to pool/main/j/jaula/libjaula-doc_1.4.0-2_i386.deb libjaula1_1.4.0-2_i386.deb to pool/main/j/jaula/libjaula1_1.4.0-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 516...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Loic Dachary (OuoU) l...@debian.org (supplier of updated jaula package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 16 Apr 2009 15:25:37 +0200 Source: jaula Binary: libjaula1 libjaula-dev libjaula-doc jparse Architecture: source i386 Version: 1.4.0-2 Distribution: unstable Urgency: low Maintainer: Loic Dachary (OuoU) l...@debian.org Changed-By: Loic Dachary (OuoU) l...@debian.org Description: jparse - JSON parser utility libjaula-dev - JSON parser/writer library for C++ (development files) libjaula-doc - JSON parser/writer library for C++ (documentation) libjaula1 - JSON parser/writer library for C++ Closes: 516964 Changes: jaula (1.4.0-2) unstable; urgency=low . * only generate HTML documentation (Closes: #516964) * remove texlive, ghostscript, texinfo * upgrade standards to 3.8.1 Checksums-Sha1: 5b861793d313e0031d3e3eaf74e22b720af24542 1027 jaula_1.4.0-2.dsc 1533533d14bde95c45d1ffe886c02956b14e3471 4645 jaula_1.4.0-2.diff.gz 2cf85d6ebe79a5b02b6a23d425acf4fe3fcc5515 45822 libjaula1_1.4.0-2_i386.deb 8727eaf30473cb2db5930fd2a261842990b9af5c 65956 libjaula-dev_1.4.0-2_i386.deb 9aca349989dbe0713b2234854f948c25defd3e87 156958 libjaula-doc_1.4.0-2_i386.deb 8ebed816b1335e4847b30e40f0c83371894be93f 9510 jparse_1.4.0-2_i386.deb Checksums-Sha256: 93f861437a643a9b2c9824084291a72b638744bcc2db4b53af2c865ace0cffc7 1027 jaula_1.4.0-2.dsc e84bb4a21c9f159781275fbecb5b44e2ea7edeaa2c706d1e269a1809af0527e9 4645 jaula_1.4.0-2.diff.gz 22a38ef9f5118eee6aae4134a552ec8a02cd2d0673f6be3e8266bde1a57a3dd8 45822 libjaula1_1.4.0-2_i386.deb 0b9e52a9679871ad574fa7d785a798fe3d0f529128919c8e97c865aea7e2eaaf 65956 libjaula-dev_1.4.0-2_i386.deb 3dc4ecde53b129cca2e8c8d7390e9dfd8d932fe2c1d90876b61a11d314cb078e 156958 libjaula-doc_1.4.0-2_i386.deb
Bug#523508: marked as done (juala: FTBFS: make[4]: *** [refman.pdf] Error 1)
Your message dated Thu, 16 Apr 2009 18:32:07 + with message-id e1luwnb-0003eo...@ries.debian.org and subject line Bug#516964: fixed in jaula 1.4.0-2 has caused the Debian Bug report #516964, regarding juala: FTBFS: make[4]: *** [refman.pdf] Error 1 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.) -- 516964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: juala Version: 1.4.0-1 Severity: serious Hi, Your package is failing to build with the following error: Chapter 8. (./classJAULA_1_1Bad__Data__Type.tex ! LaTeX Error: File `classJAULA_1_1Bad__Data__Type' not found. [...] ! == Fatal error occurred, no output PDF file produced! Transcript written on refman.log. make[4]: *** [refman.pdf] Error 1 [...] test -n doxygen -a -f latex/refman.pdf /usr/bin/install -c -m 644 latex/refman.pdf //build/buildd/jaula-1.4.0/debian/tmp/usr/share/doc/jaula/jaula_API_reference.pdf make[4]: *** [install-data-local] Error 1 Kurt ---End Message--- ---BeginMessage--- Source: jaula Source-Version: 1.4.0-2 We believe that the bug you reported is fixed in the latest version of jaula, which is due to be installed in the Debian FTP archive: jaula_1.4.0-2.diff.gz to pool/main/j/jaula/jaula_1.4.0-2.diff.gz jaula_1.4.0-2.dsc to pool/main/j/jaula/jaula_1.4.0-2.dsc jparse_1.4.0-2_i386.deb to pool/main/j/jaula/jparse_1.4.0-2_i386.deb libjaula-dev_1.4.0-2_i386.deb to pool/main/j/jaula/libjaula-dev_1.4.0-2_i386.deb libjaula-doc_1.4.0-2_i386.deb to pool/main/j/jaula/libjaula-doc_1.4.0-2_i386.deb libjaula1_1.4.0-2_i386.deb to pool/main/j/jaula/libjaula1_1.4.0-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 516...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Loic Dachary (OuoU) l...@debian.org (supplier of updated jaula package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 16 Apr 2009 15:25:37 +0200 Source: jaula Binary: libjaula1 libjaula-dev libjaula-doc jparse Architecture: source i386 Version: 1.4.0-2 Distribution: unstable Urgency: low Maintainer: Loic Dachary (OuoU) l...@debian.org Changed-By: Loic Dachary (OuoU) l...@debian.org Description: jparse - JSON parser utility libjaula-dev - JSON parser/writer library for C++ (development files) libjaula-doc - JSON parser/writer library for C++ (documentation) libjaula1 - JSON parser/writer library for C++ Closes: 516964 Changes: jaula (1.4.0-2) unstable; urgency=low . * only generate HTML documentation (Closes: #516964) * remove texlive, ghostscript, texinfo * upgrade standards to 3.8.1 Checksums-Sha1: 5b861793d313e0031d3e3eaf74e22b720af24542 1027 jaula_1.4.0-2.dsc 1533533d14bde95c45d1ffe886c02956b14e3471 4645 jaula_1.4.0-2.diff.gz 2cf85d6ebe79a5b02b6a23d425acf4fe3fcc5515 45822 libjaula1_1.4.0-2_i386.deb 8727eaf30473cb2db5930fd2a261842990b9af5c 65956 libjaula-dev_1.4.0-2_i386.deb 9aca349989dbe0713b2234854f948c25defd3e87 156958 libjaula-doc_1.4.0-2_i386.deb 8ebed816b1335e4847b30e40f0c83371894be93f 9510 jparse_1.4.0-2_i386.deb Checksums-Sha256: 93f861437a643a9b2c9824084291a72b638744bcc2db4b53af2c865ace0cffc7 1027 jaula_1.4.0-2.dsc e84bb4a21c9f159781275fbecb5b44e2ea7edeaa2c706d1e269a1809af0527e9 4645 jaula_1.4.0-2.diff.gz 22a38ef9f5118eee6aae4134a552ec8a02cd2d0673f6be3e8266bde1a57a3dd8 45822 libjaula1_1.4.0-2_i386.deb 0b9e52a9679871ad574fa7d785a798fe3d0f529128919c8e97c865aea7e2eaaf 65956 libjaula-dev_1.4.0-2_i386.deb 3dc4ecde53b129cca2e8c8d7390e9dfd8d932fe2c1d90876b61a11d314cb078e 156958 libjaula-doc_1.4.0-2_i386.deb 25af5d398804eb3ade95505e912c035640850d9b2a40f1400d326e036ba84f58 9510 jparse_1.4.0-2_i386.deb Files: 11b4dda0b0bed6b09e6452a99faff774 1027 libs extra jaula_1.4.0-2.dsc a1196fefc78c0508360a3b5f68fc0c5a 4645 libs extra jaula_1.4.0-2.diff.gz 601967bf834b27de7969c613625fa99e 45822 libs extra libjaula1_1.4.0-2_i386.deb 5b5697e930dd766ca42f4d1e46b09e43 65956 libdevel extra libjaula-dev_1.4.0-2_i386.deb d1c4f8a31c177f21cb44cae0c9d987df 156958 doc extra libjaula-doc_1.4.0-2_i386.deb 6dd298484c9704105b46321d93a4179c 9510 utils extra jparse_1.4.0-2_i386.deb -BEGIN PGP SIGNATURE- Version:
Processed: forgot to reopen earlier
Processing commands for cont...@bugs.debian.org: reopen 524295 Bug#524295: liblpsolve55-dev should depend on libsuitesparse-dev due to libcolamd linkage Bug reopened, originator not changed. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522729: notification-daemon version
Hi, Could you post the version of notification-daemon installed? Also, could you try to reproduce the bug with the Notification Area Icon extension disabled? Also, does this happen with all media files, or just all video files, or just that particular video? Thanks. -- Regards, Chow Loong Jin signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#520042: marked as done (texlive-base: Fails to generate formats on new installation(?))
Processing commands for cont...@bugs.debian.org: found 520042 2007.dfsg.2-2 Bug#520042: texlive-base: Fails to generate formats on new installation(?) Bug marked as found in version 2007.dfsg.2-2. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522104: do you use uswsusp?
To speed thing up, let me reply. I also found this problem, after the updating session yesterday. Similar things happen, pressing Alt-F8 does not help me to get out of the black screen, only a reset does. Right now I have just uninstalled splashy, as the other critical bug of not starting/stopping init scripts affected me too. This led to hal not starting properly (I guess), touchpad not working etc. Purging splashy (or better, moving /etc/lsb-base-logging.sh out of the way) solved all these problems. Sjoerd signature.asc Description: OpenPGP digital signature
Bug#518673: libidn_1.12-2(hppa/experimental): FTBFS: java not available on hppa
Hello, Right, I have made this change in the 1.14-2 upload. I ended up using: Build-Depends: debhelper (= 6), autotools-dev, gcj [!arm !hppa !hurd-i386], fastjar Because only arm, hppa, and hurd-i386 are official debian architectures that lack gcj packages in unstable. Okay. If you creates -java packages that are arch:any, in addition to debian/control, you must modify your debian/rules to handle gracefully being built on a system without gcj. The result should be that the libidn11-java is not built at all; you can do that with the -N switch of debhelper. You should be able to find example code. I didn't find any example code, but I worked out something that worked on local testing. I’ve looked at what you did. It indeed does the job, and that’s the basic idea to use, debhelper’s -N. A bit more idiomatic code is: | NO_JAVA_ARCHES := arm hppa hurd-i386 | DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) | | ifeq (,$(filter $(DEB_HOST_ARCH),$(NO_JAVA_ARCHES))) | ENABLE_JAVA := --enable-java | else | export DH_OPTIONS=-Nlibidn11-java | endif And then, you can lose all the $(DH_NO_JAVA) part when calling the dh_ commands, because debhelper picks it up via DH_OPTIONS from the environment. Anyway, your version worked, as you can see in: http://buildd.ayous.org/fetch.php?pkg=libidnver=1.14-2arch=hppastamp=1239910858file=logas=raw You can see in the resulting .changes file that the libidn11-java package was not built. P-a-s would be relevant here if libidn11-java was arch:any, and only because libidn provides some non-java packages. I didn't understand the purpose of that file -- is it still something that we should consider? If we can solve things in the local debian/ directory, that seems preferable to me. No, you don’t need P-a-s. I hope this mail cleared things for you. Yes thank you! Hopefully it will work better with this upload, but if it doesn't I hope you still have some patience to help me make it work. Sure. :-) Thanks for your work, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524396: Installation fails
Package: python-elementtree Severity: serious Version: 1.2.6-13 Hi This happens when I update the package. I assume it is an easy fix. Setting up python-elementtree (1.2.6-13) ... Usage: update-python-modules [-v] [-c] package_directory [...] update-python-modules [-v] [-c] package.dirs [...] update-python-modules [-v] [-a|-f|-p] update-python-modules: error: /usr/share/python-support/python-elementtree.public is not a directory dpkg: error processing python-elementtree (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: python-elementtree E: Sub-process /usr/bin/dpkg returned an error code (1) Best regards, // Ola -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524373: linux-2.6: /dev/mem rootkit vulnerability
On Thu, 16 Apr 2009 12:43:07 -0400, Noah Meyerhans wrote: On Thu, Apr 16, 2009 at 11:55:05AM -0400, Michael S. Gilbert wrote: as seen in recent articles and discussions, the linux kernel is currently vulnerable to rootkit attacks via the /dev/mem device. one article [1] mentions that there is an existing patch for the problem, but does not link to it. perhaps this fix can be found in the kernel mailing lists. There's no vulnerability there. /dev/mem is only writable by root. The research (if there's really any research involved) just shows how you could hide files or processes by manipulating /dev/mem. That's been known for ages. That's why you don't let your users write to /dev/mem. If the attacker has root, who cares what means they use to hide their precese, you've already lost. i believe that the if they've got root, you've already lost consensus is a logical fallacy. an aspect of security is being able to detect when you have been compromised. hence, it is a lot worse when the attacker is able to mask their presence. at least when they only have root they leave tracks and you can detect files, configs, and utilities that differ from the norm or are out of place. i think that any flaw that allows an attacker to elevate his pwnage from root to hidden should always be considered a grave security issue. best regards, mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524373: linux-2.6: /dev/mem rootkit vulnerability
On Thu, Apr 16, 2009 at 04:21:10PM -0400, Michael S. Gilbert wrote: i think that any flaw that allows an attacker to elevate his pwnage from root to hidden should always be considered a grave security issue. Your argument sounds like the one used by RIAA, MPAA etc, based on the DMCA's anti-circumvention clause, to keep things like open source dvd players illegal. Just because something can be used for malicious purposes, doesn't mean its existance is a bad thing. There are reasons for /dev/mem to exist, and why you might want to manipulate kernel state through it. Many of these do not involve rootkits. The support for dynamically loadable kernel modules in Linux can be abuses similarly. Does that make it a grave security issue? But as Dann pointed out, we'll have CONFIG_STRICT_DEVMEM in the future to help minimize exposure. If you want to continue this discussion, I propose to do it outside the BTS. noah signature.asc Description: Digital signature
Bug#524239: Bug#524233: console-setup should conflict with console-data
On Thu, Apr 16, 2009 at 07:13:36AM +0200, Christian Perrier wrote: Quoting Anton Zinoviev (an...@lml.bas.bg): merge 524233 524239 thanks On Wed, Apr 15, 2009 at 07:14:34PM +0200, Kurt Roeckx wrote: console-setup and console-data both allow you to setup the keyboard layout but they do not take each other settings into account. Why this should be considered a bug? Normaly the users don't have to install both packages but perhaps there are many reasons why they might want to install them both. Console-data and console-cyrillic have happily coexisted for a decade and now this can continue with console-setup (exept that it seems console-data and console-cyrillic are going to become obsolete). As the de facto maintainer of console-data, I agree with this. I have to add that I unfortunately am entirely unable to implement in c-d something to have it grab keymap definitions from console-setup. Moreover, as both use different origins for the keymaps (c-s uses X.org keymaps while c-d provides the old-style Linux console keymaps, crafted by generation of Linux users over yearsturning into a giant mess), it is very likely that many keymaps do not necessarily correspond. I would be delighted to obsolete console-data, as many people know. There are however several steps to achieve before that happens (one of those being d-i uing console-setup). Well, X now Depends on console-setup, so you're atleast going to get more people install this. An I indeed have no idea about how to turn console-data into a completely obsolete package and then offer users a decent transition to console-setup I think there are a few things that console-setup doesn't do that atleast console-tools does: - calling setterm to set powersaving mode. - Set keyboard rate - Being able to set numlock on boot I got a little confused about console-data being the package that ask the debconf questions, but it seems that console-common is actually the package that set up keyboard. So you can argue where the second bug belongs to. I have no idea if console-setup does anything more than console-common / console-data. Anyway, my problem with the current situation is that there are 2 config files where I can set the same thing, and it's not obvious which of the 2 is going to win. In general, it would be better that there was only 1 source of keyboard layouts. And I have no problem going with those of X, but I have no idea if the quality of both are the same or not. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: setting package to devscripts, user devscri...@packages.debian.org, usertagging 524127 ...
Processing commands for cont...@bugs.debian.org: package devscripts Ignoring bugs not assigned to: devscripts user devscri...@packages.debian.org Setting user to devscri...@packages.debian.org (was a...@adam-barratt.org.uk). usertags 524127 uscan Bug#524127: [uscan] 'x509_user' not valid URI scheme at /usr/bin/uscan line 389 There were no usertags set. Usertags are now: uscan. tags 524127 - moreinfo unreproducible Bug#524127: [uscan] 'x509_user' not valid URI scheme at /usr/bin/uscan line 389 Tags were: unreproducible moreinfo Tags removed: moreinfo, unreproducible usertags 523677 checkbashisms Bug#523677: checkbashisms does not support redirected output There were no usertags set. Usertags are now: checkbashisms. retitle 523677 [checkbashisms] Doesn't support redirected output Bug#523677: checkbashisms does not support redirected output Changed Bug title to `[checkbashisms] Doesn't support redirected output' from `checkbashisms does not support redirected output'. usertags 524393 debchange Bug#524393: [debchange] dch -r without editing no longer modifies the changelog There were no usertags set. Usertags are now: debchange. usertags 523982 getbuildlog Bug#523982: getbuildlog $pkg last fails due to missing 'use lib' There were no usertags set. Usertags are now: getbuildlog. retitle 523982 [getbuildlog] Missing 'use lib' makes last fail Bug#523982: getbuildlog $pkg last fails due to missing 'use lib' Changed Bug title to `[getbuildlog] Missing 'use lib' makes last fail' from `getbuildlog $pkg last fails due to missing 'use lib''. usertags 523523 rc-alert Bug#523523: [rc-alert] add debtags functionality There were no usertags set. Usertags are now: rc-alert. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523187: acpid upgarade problem
Hi, I'm not able to upgrade acpid because I installed splashy, but I do not enable it, I do not pass the splashy options in the boot parameters. The upgrade scripts try to stop acpid but it fails because in the log_end_msg functions it fails in the line 341 of /etc/lsb-base-logging.sh 338 [ -x $SPL_UPD ] || return 1; 339 [ ! -d $STEPS_DIR ] mkdir -p $STEPS_DIR 340 SPL_PRG=$STEPS_DIR/$RUNLEVEL-progress 341 [ -f $SPL_PRG ] || return 1; It cause also the problem that my system was not able to automatically load the kernel modules. To solve all the problems, I have to enable splashy, remove it, and then upgrade acpid. Thanks, Luca
Bug#518673: libidn_1.12-2(hppa/experimental): FTBFS: java not available on hppa
Adeodato Simó d...@net.com.org.es writes: Hello, Right, I have made this change in the 1.14-2 upload. I ended up using: Build-Depends: debhelper (= 6), autotools-dev, gcj [!arm !hppa !hurd-i386], fastjar Because only arm, hppa, and hurd-i386 are official debian architectures that lack gcj packages in unstable. Okay. The sparc experimental buildd has failed to build the latest upload, since the buildd doesn't seem to have gcj. As far as I can tell, that would be a problem with the sparc buildd. There are gcj packages for sparc in the archive. I’ve looked at what you did. It indeed does the job, and that’s the basic idea to use, debhelper’s -N. A bit more idiomatic code is: | NO_JAVA_ARCHES := arm hppa hurd-i386 | DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) | | ifeq (,$(filter $(DEB_HOST_ARCH),$(NO_JAVA_ARCHES))) | ENABLE_JAVA := --enable-java | else | export DH_OPTIONS=-Nlibidn11-java | endif And then, you can lose all the $(DH_NO_JAVA) part when calling the dh_ commands, because debhelper picks it up via DH_OPTIONS from the environment. Oh, much nicer, thank you. I'm using it now. I'm going to wait some days to see if any experimental buildd's fail unexpectedly, but then I'll upload to unstable. Anyway, your version worked, as you can see in: http://buildd.ayous.org/fetch.php?pkg=libidnver=1.14-2arch=hppastamp=1239910858file=logas=raw You can see in the resulting .changes file that the libidn11-java package was not built. Great. /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478030: About the patch ...
Hi!
The Bastian's patch works but there is a mistake; we must use
sqlite_freemem(errmsg) for slite 2.x, the sqlite_free() function does not
exist. Edit Build-Depends in debian/control and replace libsqlite3-dev with
libsqlite0-dev, apply the patch, and you will get an FTBFS.
I'm attaching the proper fix. Thank you very much for your patch, Bastian.
Lets talk about the status of krecipes in pkg-kde-talk mailing list:
http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2009-April/001247.html
--- krecqsqlitedb.cpp 2006-09-02 03:52:17.0 +0200
+++ krecipes-1.0~beta1/krecipes/src/backends/SQLite/libqsqlite/krecqsqlitedb.cpp 2009-01-06 18:08:32.0 +0100
@@ -106,7 +106,11 @@
\t (Query: query ) endl;
res.setError( errmsg );
res.setStatus( QSQLiteResult::Failure );
- free( errmsg );
+#if HAVE_SQLITE
+ sqlite_freemem( errmsg );
+#elif HAVE_SQLITE3
+ sqlite3_free( errmsg );
+#endif
}
if ( lastID ) {
signature.asc
Description: This is a digitally signed message part.
Bug#524415: dbench_4.0-1(mips/unstable): FTBFS on mips: autoheader missing.
Package: dbench Version: 4.0-1 Severity: serious There was an error while trying to autobuild your package: Automatic build of dbench_4.0-1 on mayr by sbuild/mips 99.999 Build started at 20090415-1924 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper ( 5.0.0) [...] dpkg-source: info: unpacking dbench_4.0.orig.tar.gz dpkg-source: info: applying dbench_4.0-1.diff.gz dpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package dbench dpkg-buildpackage: source version 4.0-1 dpkg-buildpackage: host architecture mips /usr/bin/fakeroot debian/rules clean ./autogen.sh ./autogen.sh: line 3: autoheader: command not found make: *** [configure] Error 1 dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules clean gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=mipspkg=dbenchver=4.0-1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524416: gcc-4.3_4.3.3-8(mips/unstable): FTBFS on mips. doc patching fails.
Package: gcc-4.3 Version: 4.3.3-8 Severity: serious There was an error while trying to autobuild your package: Automatic build of gcc-4.3_4.3.3-8 on mayr by sbuild/mips 99.999 Build started at 20090416-1609 [...] ** Using build dependencies supplied by package: Build-Depends: dpkg-dev (= 1.14.15), debhelper (= 5.0.62), gcc-multilib [amd64 i386 mips mipsel powerpc ppc64 s390 sparc kfreebsd-amd64], libc6.1-dev (= 2.5) [alpha ia64] | libc0.3-dev (= 2.5) [hurd-i386] | libc0.1-dev (= 2.5) [kfreebsd-i386 kfreebsd-amd64] | libc6-dev (= 2.5), libc6-dev-amd64 [i386], libc6-dev-sparc64 [sparc], libc6-dev-s390x [s390], libc6-dev-i386 [amd64], libc6-dev-powerpc [ppc64], libc6-dev-ppc64 [powerpc], libc0.1-dev-i386 [kfreebsd-amd64], lib32gcc1 [amd64 ppc64 kfreebsd-amd64], lib64gcc1 [i386 powerpc sparc s390], libc6-dev-mips64 [mips mipsel], libc6-dev-mipsn32 [mips mipsel], autogen, libunwind7-dev (= 0.98.5-6) [ia64], libatomic-ops-dev [ia64], m4, autoconf (= 2.50), autoconf2.59, automake1.9, libtool, gawk, expect-tcl8.3 [hppa], dejagnu [!none !hurd-i386], lzma, binutils (= 2.19.1) | binutils-multiarch (= 2.19.1), binutils-hppa64 (= 2.19.1) [hppa], gperf (= 3.0.1), bison (= 1:2.3), flex, gettext, texinfo (= 4.3), libmpfr-dev (= 2.3.0), locales [!hurd-i386 !m68k], procps [!hurd-i386], sharutils, binutils-spu (= 2.19.1) [powerpc ppc64], newlib-spu (= 1.16.0) [powerpc ppc64], realpath (= 1.9.12), chrpath, lsb-release, make (= 3.81) [...] PATH=/build/buildd/gcc-4.3-4.3.3/bin:/usr/lib/gcc/bin:$PATH sh -e debian/patches/pr39431.dpatch -patch -d /build/buildd/gcc-4.3-4.3.3/src patching file gcc/config/i386/predicates.md Hunk #1 succeeded at 859 (offset -28 lines). patching file gcc/config/i386/sync.md patching file gcc/testsuite/gcc.target/i386/pr39431.c PATH=/build/buildd/gcc-4.3-4.3.3/bin:/usr/lib/gcc/bin:$PATH sh -e debian/patches/gcc-default-format-security.dpatch -patch -d /build/buildd/gcc-4.3-4.3.3/src patching file gcc/c-common.c Hunk #1 succeeded at 278 (offset 1 line). patching file gcc/c.opt patching file gcc/doc/invoke.texi Hunk #1 FAILED at 2802. Hunk #2 FAILED at 2852. 2 out of 2 hunks FAILED -- saving rejects to file gcc/doc/invoke.texi.rej make: *** [stamps/02-patch-stamp-gcc-default-format-security] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=mipspkg=gcc-4.3ver=4.3.3-8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524417: libmodplug_1:0.8.4-4(mips/unstable): FTBFS on mips: missing autotools info.
Package: libmodplug Version: 1:0.8.4-4 Severity: serious There was an error while trying to autobuild your package: Automatic build of libmodplug_1:0.8.4-4 on mayr by sbuild/mips 99.999 Build started at 20090416-0105 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5.0.0), autoconf, automake, autotools-dev, libtool [...] aclocal libtoolize -f libtoolize: putting auxiliary files in `.'. libtoolize: linking file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. autoheader automake configure.in:20: required file `./config.guess' not found configure.in:20: `automake --add-missing' can install `config.guess' configure.in:20: required file `./config.sub' not found configure.in:20: `automake --add-missing' can install `config.sub' make: *** [configure-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=mipspkg=libmodplugver=1:0.8.4-4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524418: googleearth-package: relocation error: /usr/lib32/i686/cmov/libssl.so.0.9.8: symbol BIO_test_flags, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference
Package: googleearth-package Version: 0.5.4 Severity: grave Justification: renders package unusable When running googleearth 5.0.11337.1968+0.5.4-1, I get this error: /usr/lib/googleearth/googleearth-bin: relocation error: /usr/lib32/i686/cmov/libssl.so.0.9.8: symbol BIO_test_flags, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference If I delete /usr/lib/googleearth/libcrypto.so.0.9.8 then the program runs. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages googleearth-package depends on: ii bzip2 1.0.5-1high-quality block-sorting file co ii curl 7.18.2-8.1 Get a file from an HTTP, HTTPS or ii dpkg-dev 1.14.25Debian package development tools ii fakeroot 1.12.2 Gives a fake root environment ii file 5.00-1 Determines file type using magic ii wget 1.11.4-2 retrieves files from the web ii x11-common1:7.4+1X Window System (X.Org) infrastruc googleearth-package recommends no packages. googleearth-package suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524419: pure-ftpd-postgresql: Pure-ftpd-postgresql don't want to start. pure-ftpd missing
Package: pure-ftpd-postgresql Version: 1.0.21-11.4 Severity: grave Justification: renders package unusable The program pure-ftpd is deleted when pure-ftpd-postgresql is installed. But, the pure-ftpd-wrapper needs (pure-ftpd) to work. This problem cause all the Pure-ftpd program to don't work with the postgresql package installed. pure-ftpd-wrapper Can't exec /usr/sbin/pure-ftpd: Aucun fichier ou répertoire de ce type at /usr/sbin/pure-ftpd-wrapper line 174. /usr/sbin/pure-ftpd-wrapper: Cannot exec /usr/sbin/pure-ftpd: Aucun fichier ou répertoire de ce type at /usr/sbin/pure-ftpd-wrapper line 174. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27.10-grsec--grs-ipv6-64 (SMP w/1 CPU core) Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages pure-ftpd-postgresql depends on: ii libc6 2.7-18GNU C Library: Shared libraries ii libcap11:1.10-14 support for getting/setting POSIX. ii libpam0g 1.0.1-5+lenny1Pluggable Authentication Modules l ii libpq5 8.3.7-0lenny1 PostgreSQL C client library ii libssl0.9.80.9.8g-15+lenny1 SSL shared libraries ii pure-ftpd-common 1.0.21-11.4 Pure-FTPd FTP server (Common Files ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime pure-ftpd-postgresql recommends no packages. pure-ftpd-postgresql suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523187: [Splashy-devel] Bug#523187: acpid upgarade problem
Ouch. Time to revert our last update I guess. -- A bug magnet On Apr 16, 2009, at 17:09, luca boncompagni lbo...@gmail.com wrote: Hi, I'm not able to upgrade acpid because I installed splashy, but I do not enable it, I do not pass the splashy options in the boot parameters. The upgrade scripts try to stop acpid but it fails because in the log_end_msg functions it fails in the line 341 of / etc/lsb-base-logging.sh 338 [ -x $SPL_UPD ] || return 1; 339 [ ! -d $STEPS_DIR ] mkdir -p $STEPS_DIR 340 SPL_PRG=$STEPS_DIR/$RUNLEVEL-progress 341 [ -f $SPL_PRG ] || return 1; It cause also the problem that my system was not able to automatically load the kernel modules. To solve all the problems, I have to enable splashy, remove it, and then upgrade acpid. Thanks, Luca ___ Splashy-devel mailing list splashy-de...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/splashy-devel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 524241 in 2.0.3-2
Processing commands for cont...@bugs.debian.org: fixed 524241 2.0.3-2 Bug#524241: FTBFS: dh_pysupport: Command not found Bug marked as fixed in version 2.0.3-2. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524241: marked as done (FTBFS: dh_pysupport: Command not found)
Your message dated Fri, 17 Apr 2009 01:41:03 +0200 with message-id 20090416234103.ga4...@teal.hq.k1024.org and subject line Fixed in 2.0.3-2 has caused the Debian Bug report #524241, regarding FTBFS: dh_pysupport: Command not found 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.) -- 524241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: protobuf Version: 2.0.3-1 Severity: serious dh_link dh_strip dh_compress dh_fixperms dh_pysupport make[1]: dh_pysupport: Command not found make[1]: *** [binary-common] Error 127 make[1]: Leaving directory `/build/buildd/protobuf-2.0.3' make: *** [binary-arch] Error 2 dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2 ---End Message--- ---BeginMessage--- The upload of 2.0.3-2 should have fixed this (I also checked the buildd logs and they are fine so far). regards, iustin ---End Message---
Bug#524314: Backtrace
Hi, I'm seeing the same problem. Here's the trace of `bash -x /etc/init.d/acpid start`: + set -e + ACPID=/usr/sbin/acpid + DEFAULTS=/etc/default/acpid + '[' -x /usr/sbin/acpid ']' + OPTIONS= + MODULES= + '[' -r /etc/default/acpid ']' + . /etc/default/acpid + . /lib/lsb/init-functions ++ FANCYTTY= ++ '[' -e /etc/lsb-base-logging.sh ']' ++ . /etc/lsb-base-logging.sh + . /etc/default/rcS ++ TMPTIME=0 ++ SULOGIN=no ++ DELAYLOGIN=no ++ UTC=no ++ VERBOSE=no ++ FSCKFIX=no ++ RAMRUN=no ++ RAMLOCK=no ++ HWCLOCKPARS=--directisa + case $1 in + load_modules + '[' -f /proc/modules ']' + '[' '' = all ']' + '[' -z '' ']' + return + log_begin_msg 'Starting ACPI services...' + log_daemon_msg 'Starting ACPI services...' + '[' -z 'Starting ACPI services...' ']' + SPL_UPD=/sbin/splashy_update + '[' -r /etc/default/splashy ']' + . /etc/default/splashy ++ CHVT_TTY=auto ++ ENABLE_INITRAMFS=1 ++ DEBUG=0 + log_use_splashy + '[' n = y ']' + pidof splashy + log_to_console log_daemon_msg 'Starting ACPI services...' + '[' n '!=' y ']' + '[' no '!=' yes ']' ++ readlink /proc/self/fd/0 + stdin=/dev/pts/2 + '[' /dev/pts/2 '!=' /dev/pts/2 ']' + return 0 + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + '[' -t 1 ']' + '[' xxterm '!=' '' ']' + '[' xxterm '!=' xdumb ']' + '[' -x /usr/bin/tput ']' + '[' -x /usr/bin/expr ']' + /usr/bin/tput hpa 60 + /usr/bin/tput setaf 1 + '[' -z ']' + FANCYTTY=1 + case $FANCYTTY in + true + /usr/bin/tput xenl ++ /usr/bin/tput cols + COLS=80 + '[' 80 ']' + '[' 80 -gt 6 ']' ++ /usr/bin/expr 80 - 7 + COL=73 + printf ' * Starting ACPI services... ' * Starting ACPI services... ++ /usr/bin/expr 80 - 1 + /usr/bin/tput hpa 79 + printf ' ' + '[' -x /sbin/splashy_update ']' + '[' -z '' ']' ++ runlevel ++ sed 's/^. //' + RUNLEVEL=2 + '[' -z 2 ']' + '[' x2 = x6 ']' + '[' x2 = x0 ']' + '[' '!' -z '' ']' + start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/acpid -- + log_end_msg 0
Bug#524386: apt-watch: FTBFS: error: glade/glade-xml.h: No such file or, directory
tags 524386 +patch sid squeeze thanks The package uses glade/glade-xml.h but does not depend on libglade2-dev . In lenny the package gets away with this because it is pulled in indirectly by libpanel-applet2-dev. In sid it does not get away with it. The situation in squeeze seems to be the same as in lenny right now but I suspect it won't stay that way so this bug is probablly relavent for squeeze. The fix is trivial, just add libglade2-dev to the build-depends -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: re:apt-watch: FTBFS: error: glade/glade-xml.h: No such file or, directory
Processing commands for cont...@bugs.debian.org: tags 524386 +patch sid squeeze Bug#524386: apt-watch: FTBFS: error: glade/glade-xml.h: No such file or directory There were no tags set. Tags added: patch, sid, squeeze thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524418: marked as done (googleearth-package: relocation error: /usr/lib32/i686/cmov/libssl.so.0.9.8: symbol BIO_test_flags, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link
Your message dated Thu, 16 Apr 2009 19:06:28 -0600 with message-id 200904161906.28478@icecavern.net and subject line Re: Bug#524418: googleearth-package: relocation error: /usr/lib32/i686/cmov/libssl.so.0.9.8: symbol BIO_test_flags, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference has caused the Debian Bug report #524418, regarding googleearth-package: relocation error: /usr/lib32/i686/cmov/libssl.so.0.9.8: symbol BIO_test_flags, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 524418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: googleearth-package Version: 0.5.4 Severity: grave Justification: renders package unusable When running googleearth 5.0.11337.1968+0.5.4-1, I get this error: /usr/lib/googleearth/googleearth-bin: relocation error: /usr/lib32/i686/cmov/libssl.so.0.9.8: symbol BIO_test_flags, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference If I delete /usr/lib/googleearth/libcrypto.so.0.9.8 then the program runs. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages googleearth-package depends on: ii bzip2 1.0.5-1high-quality block-sorting file co ii curl 7.18.2-8.1 Get a file from an HTTP, HTTPS or ii dpkg-dev 1.14.25Debian package development tools ii fakeroot 1.12.2 Gives a fake root environment ii file 5.00-1 Determines file type using magic ii wget 1.11.4-2 retrieves files from the web ii x11-common1:7.4+1X Window System (X.Org) infrastruc googleearth-package recommends no packages. googleearth-package suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Thursday 16 April 2009 17:25:51 Sam Morris wrote: Package: googleearth-package Version: 0.5.4 Severity: grave Justification: renders package unusable When running googleearth 5.0.11337.1968+0.5.4-1, I get this error: I do appreciate bug reports, but: 1) You couldn't have used 0.5.4 to make a package for 5.0 without using the --force flag, so this bug is invalid, and 2) This is a known upstream problem, not a problem with googleearth-package itself, so this bug is also invalid, however 3) There is already workaround for this problem in 0.5.6 which I just uploaded earlier today. =) So upgrade to 0.5.6 when it hits the archive (if it hasn't already) and you should have better luck. Otherwise, you can google for that error message and see what the workaround is. ---End Message---
Bug#524161: marked as done (network-manager: FTBFS on alpha: nm-serial-device.c:366: error: array subscript is above array bounds)
Your message dated Fri, 17 Apr 2009 01:02:04 + with message-id e1lucsy-00074y...@ries.debian.org and subject line Bug#524161: fixed in network-manager 0.7.1-1 has caused the Debian Bug report #524161, regarding network-manager: FTBFS on alpha: nm-serial-device.c:366: error: array subscript is above array bounds 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.) -- 524161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: network-manager Version: 0.7.0.100-1 Severity: serious Hello, there was an error while trying to autobuild network-manager on alpha: | cc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../marshallers -I../src/named-manager -I../src/vpn-manager -I../src/dhcp-manager -I../src/supplicant-manager -I../src/dnsmasq-manager -I../libnm-util -I../callouts -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE -DG_DISABLE_DEPRECATED -DBINDIR=\/usr/bin\ -DSBINDIR=\/usr/sbin\ -DLIBEXECDIR=\/usr/lib/NetworkManager\ -DDATADIR=\/usr/share\ -DSYSCONFDIR=\/etc\ -DLOCALSTATEDIR=\/var\ -DNM_RUN_DIR=\/var/run/NetworkManager\ -DNMLOCALEDIR=\/usr/share/locale\ -DARP_DEBUG -Wall -Werror -std=gnu89 -g -O2 -g -Wall -O2 -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -fno-strict-aliasing -c -o NetworkManager-nm-serial-device.o `test -f 'nm-serial-device.c' || echo './'`nm-serial-device.c | cc1: warnings being treated as errors | nm-serial-device.c: In function 'nm_serial_device_open': | nm-serial-device.c:366: error: array subscript is above array bounds | nm-serial-device.c:367: error: array subscript is above array bounds | make[5]: *** [NetworkManager-nm-serial-device.o] Error 1 | make[5]: Leaving directory `/build/buildd-network-manager_0.7.0.100-1-alpha-QRYpUb/network-manager-0.7.0.100/src' The full log can be read at [1]. I wanted to migrate network-manager to testing already, playing some tricks with gnome-main-menu, but this failure is preventing me from doing so, and I won’t be able to hold gnome-main-menu for much longer. Cheers, [1]: https://buildd.debian.org/fetch.cgi?pkg=network-managerver=0.7.0.100-1arch=alphastamp=1239731697file=log -- - Are you sure we're good? - Always. -- Rory and Lorelai ---End Message--- ---BeginMessage--- Source: network-manager Source-Version: 0.7.1-1 We believe that the bug you reported is fixed in the latest version of network-manager, which is due to be installed in the Debian FTP archive: libnm-glib-dev_0.7.1-1_i386.deb to pool/main/n/network-manager/libnm-glib-dev_0.7.1-1_i386.deb libnm-glib-vpn-dev_0.7.1-1_i386.deb to pool/main/n/network-manager/libnm-glib-vpn-dev_0.7.1-1_i386.deb libnm-glib-vpn0_0.7.1-1_i386.deb to pool/main/n/network-manager/libnm-glib-vpn0_0.7.1-1_i386.deb libnm-glib0_0.7.1-1_i386.deb to pool/main/n/network-manager/libnm-glib0_0.7.1-1_i386.deb libnm-util-dev_0.7.1-1_i386.deb to pool/main/n/network-manager/libnm-util-dev_0.7.1-1_i386.deb libnm-util1_0.7.1-1_i386.deb to pool/main/n/network-manager/libnm-util1_0.7.1-1_i386.deb network-manager-dev_0.7.1-1_i386.deb to pool/main/n/network-manager/network-manager-dev_0.7.1-1_i386.deb network-manager_0.7.1-1.diff.gz to pool/main/n/network-manager/network-manager_0.7.1-1.diff.gz network-manager_0.7.1-1.dsc to pool/main/n/network-manager/network-manager_0.7.1-1.dsc network-manager_0.7.1-1_i386.deb to pool/main/n/network-manager/network-manager_0.7.1-1_i386.deb network-manager_0.7.1.orig.tar.gz to pool/main/n/network-manager/network-manager_0.7.1.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 524...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated network-manager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Apr 2009 00:47:03
Bug#524387: gnuradio: FTBFS: gr_local_sighandler.cc:38: error: 'memset' was not declared in this scope
On Thu, 2009-04-16 at 19:58 +0200, Kurt Roeckx wrote: Source: gnuradio Version: 3.0.4-2 Severity: serious This package has fallen seriously out of date, thanks in large part to the recently-resolved long-standing license issue with the 8051 assembler in the sdcc package version 3.1.3-1, which is a significantly newer version. I do not expect to do any further work on the 3.0.4 packages, but will tag this bug for closure when 3.1.3 is uploaded. Bdale -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503591: [TZInfo-users] Ruby and timezones
On Thu, Nov 06, 2008 at 11:26:10PM +, Philip Ross wrote: I'll release a core API package with an addon containing the data. You'll be able to use the core API for the Debian package. Hi Phil, I saw tonight that a new release of tzinfo-ruby is available. I was wondering if your plan to split the data and the core API is coming soon, or if you are planning it for further down the road. I ask because I'd really like to see this make it into Debian Squeeze. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Processed: re: gnuradio: FTBFS: gr_local_sighandler.cc:38: error: 'memset' was, not declared in this scope
Processing commands for cont...@bugs.debian.org: tags 524387 +patch Bug#524387: gnuradio: FTBFS: gr_local_sighandler.cc:38: error: 'memset' was not declared in this scope There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524427: kolab-cyrus-imapd: Please update to newer libdb
Package: kolab-cyrus-imapd Version: 2.2.13-5 Severity: Serious Hi, I will very shortly be removing any libdb versions prior to libdb4.6. Please update the build-depends for kolab-cyrus-imapd to build with libdb-dev or if a specific version is needed, libdb4.6-dev or libdb4.7-dev. Thank you, Barry deFreese Debian QA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524387: gnuradio: FTBFS: gr_local_sighandler.cc:38: error: 'memset' was, not declared in this scope
tags 524387 +patch thanks patch is attatched Only in gnuradio-3.0.4: config.guess Only in gnuradio-3.0.4: config.sub diff -ur gnuradio-3.0.4/debian/rules gnuradio-3.0.4.new/debian/rules --- gnuradio-3.0.4/debian/rules 2009-04-17 02:36:10.0 + +++ gnuradio-3.0.4.new/debian/rules 2009-04-17 02:39:34.0 + @@ -26,6 +26,11 @@ configure: configure-stamp configure-stamp: + -test -r /usr/share/misc/config.sub \ + cp -f /usr/share/misc/config.sub config.sub + -test -r /usr/share/misc/config.guess \ + cp -f /usr/share/misc/config.guess config.guess + dh_testdir # running bootstrap shouldn't be necessary when working from released tarballs # ./bootstrap @@ -51,12 +56,10 @@ [ ! -f Makefile ] || $(MAKE) distclean - -test -r /usr/share/misc/config.sub \ - cp -f /usr/share/misc/config.sub config.sub - -test -r /usr/share/misc/config.guess \ - cp -f /usr/share/misc/config.guess config.guess dh_clean --exclude ./gr-gsm-fr-vocoder/src/lib/gsm/README.orig + rm -f gnuradio-core/src/python/*.pyc + rm -f config.sub config.guess install: dh_testdir diff -ur gnuradio-3.0.4/gnuradio-core/src/lib/filter/gr_fft_filter_ccc.cc gnuradio-3.0.4.new/gnuradio-core/src/lib/filter/gr_fft_filter_ccc.cc --- gnuradio-3.0.4/gnuradio-core/src/lib/filter/gr_fft_filter_ccc.cc 2007-07-26 21:20:00.0 + +++ gnuradio-3.0.4.new/gnuradio-core/src/lib/filter/gr_fft_filter_ccc.cc 2009-04-17 01:17:16.0 + @@ -34,6 +34,7 @@ #include gri_fft.h #include math.h #include assert.h +#include string.h #include stdexcept #include gr_firdes.h diff -ur gnuradio-3.0.4/gnuradio-core/src/lib/filter/gr_fft_filter_fff.cc gnuradio-3.0.4.new/gnuradio-core/src/lib/filter/gr_fft_filter_fff.cc --- gnuradio-3.0.4/gnuradio-core/src/lib/filter/gr_fft_filter_fff.cc 2007-07-26 21:20:00.0 + +++ gnuradio-3.0.4.new/gnuradio-core/src/lib/filter/gr_fft_filter_fff.cc 2009-04-17 01:17:44.0 + @@ -29,6 +29,7 @@ #include gri_fft.h #include math.h #include assert.h +#include string.h #include stdexcept #include gr_firdes.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccc.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccc_generic.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccc_generic.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccc.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccf.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccf_generic.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccf_generic.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_ccf.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fcc.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fcc_generic.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fcc_generic.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fcc.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fff.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fff_generic.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fff_generic.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fff.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_ccc.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_ccc.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_ccc.i Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_ccf.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_ccf.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_ccf.i Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fcc.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fcc.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fcc.i Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fff.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fff.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fff.i Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fsf.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fsf.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_fsf.i Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_scc.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_scc.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_filter_scc.i Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fsf.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fsf_generic.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fsf_generic.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_fsf.h Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_scc.cc Only in gnuradio-3.0.4/gnuradio-core/src/lib/filter: gr_fir_scc_generic.cc Only in
Bug#524373: linux-2.6: /dev/mem rootkit vulnerability
reopen 524373 thanks On Thu, 16 Apr 2009 16:53:38 -0400 Noah Meyerhans wrote: On Thu, Apr 16, 2009 at 04:21:10PM -0400, Michael S. Gilbert wrote: i think that any flaw that allows an attacker to elevate his pwnage from root to hidden should always be considered a grave security issue. Your argument sounds like the one used by RIAA, MPAA etc, based on the DMCA's anti-circumvention clause, to keep things like open source dvd players illegal. Just because something can be used for malicious purposes, doesn't mean its existance is a bad thing. There are reasons for /dev/mem to exist, and why you might want to manipulate kernel state through it. Many of these do not involve rootkits. this is a strawman argument. i never said that /dev/mem needed to go away. my point was that it needed to be secured against these newly discovered attacks, and it sounds like CONFIG_STRICT_DEVMEM does this. The support for dynamically loadable kernel modules in Linux can be abuses similarly. Does that make it a grave security issue? probably...at least until someone comes up with a secure way to do it. But as Dann pointed out, we'll have CONFIG_STRICT_DEVMEM in the future to help minimize exposure. this is a very good thing, and i understand that it would cause a lot of hassle to backport this kind of change to stable since it could potentially break compatibility. however, that doesn't mean that the issue shouldn't be tracked. and it certainly doesn't mean that the bug should be closed. i thought that one of debian's tenants was we will not hide problems. If you want to continue this discussion, I propose to do it outside the BTS. why? isn't the bts a perfectly good place for discussion? mike -- 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#524373: linux-2.6: /dev/mem rootkit vulnerability
Processing commands for cont...@bugs.debian.org: reopen 524373 Bug#524373: linux-2.6: /dev/mem rootkit vulnerability Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524429: lastfm FTBFS with qt45 because VolumeSlider header is generated as phonon/Phonon::VolumeSlider
Package: lastfm Version: 1:1.5.1.31879.dfsg-1 Severity: serious Tags: patch Justification: no longer builds from source User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jaunty ubuntu-patch Hi, This are the errors that I get when rebuilding lastfm with qt45: .../build/ui_playcontrols.h:34: error: ISO C++ forbids declaration of 'VolumeSlider' with no type .../build/ui_playcontrols.h:34: error: expected ';' before '*' token .../build/ui_playcontrols.h: In member function 'void Ui_PlayControls::setupUi(QWidget*)': .../build/ui_playcontrols.h:62: error: 'volume' was not declared in this scope .../build/ui_playcontrols.h:62: error: expected type-specifier before 'VolumeSlider' .../build/ui_playcontrols.h:62: error: expected `;' before 'VolumeSlider' This is because the header VolumeSlider.h is generated as phonon/Phonon::VolumeSlider instead of VolumeSlider.h. Adding a point before header name fix that. *** /tmp/tmprCxiEe In Ubuntu, we've applied the attached patch to achieve the following: * debian/patches/qt45.diff: fix the volumeslider header name to avoid qt45 to generate phonon/Phonon::VolumeSlider as header name (LP: #337862) We thought you might be interested in doing the same. -- System Information: Debian Release: 5.0 APT prefers jaunty-updates APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty') Architecture: i386 (x86_64) Kernel: Linux 2.6.27-11-generic (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash diff -u lastfm-1.5.1.31879.dfsg/debian/patches/series lastfm-1.5.1.31879.dfsg/debian/patches/series --- lastfm-1.5.1.31879.dfsg/debian/patches/series +++ lastfm-1.5.1.31879.dfsg/debian/patches/series @@ -15,0 +16 @@ +qt45.diff only in patch2: unchanged: --- lastfm-1.5.1.31879.dfsg.orig/debian/patches/qt45.diff +++ lastfm-1.5.1.31879.dfsg/debian/patches/qt45.diff @@ -0,0 +1,12 @@ +--- lastfm-1.5.1.31879.dfsg.orig/src/playcontrols.ui lastfm-1.5.1.31879.dfsg/src/playcontrols.ui +@@ -146,7 +146,7 @@ + customwidget +classVolumeSlider/class +extendsQFrame/extends +- headervolumeslider.h/header ++ header./volumeslider.h/header +container1/container + /customwidget + /customwidgets +
