Bug#675845: Re: Bug#675845: adanaxisgpl: FTBFS:
Hi! On Fri, 2012-11-30 at 03:26:49 +, Steven Chamberlain wrote: Control: found -1 1.2.5.dfsg.1-4.1 Control: tags -1 + patch The problem is a '#define off_t long', which causes a problem later when GNU/kFreeBSD headers include sys/types.h (again), and try to redefine off_t for some reason. That only happens because HAVE_OFF_T isn't being set in config.h. In fact it is hard-coded to 0 by default and set to 1 on certain supported platforms such as Mac OS X (in rubyconfigure.h). With the patch below, then running: $ aclocal-1.10 autoheader autoconf implements a proper detection for off_t and it builds now on kfreebsd-amd64. Also it still builds okay and runs on GNU/Linux amd64. --- a/configure.in 2007-10-25 21:38:55.0 +0100 +++ b/configure.in 2012-11-30 02:01:34.039114307 + @@ -288,6 +288,8 @@ ]) ]) +AC_CHECK_TYPES([off_t], [], [], [[#include sys/types.h]]) + I guess ideally the code would be using AC_TYPE_OFF_T, but as you mention that the code depends on HAVE_OFF_T, then this might be the smallest change to accomplish the same thing. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
On Sat, 24 Nov 2012 18:53:39 +0100 Michael Banck mba...@debian.org wrote: Not sure this is related, but gpa -d segfaults in libassuan for me on a wheezy system. See the attached backtrace, maybe it helps. I think this is not related. The crash you are observing is due to a missing call to assuan_sock_init() and was fixed upstream in http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpa.git;a=commitdiff;h=de5ed61012cfc76d8ef0ebff81625331d43b8b28#patch1 I think you should open a separate bugreport for that. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size
Hi Kevin, Michael Stapelberg stapelb...@debian.org writes: I'm on the road right now, but would be happy to upload a new version later tonight or early tomorrow morning. Thanks. Please let us know when you are done. Any news on that? If you need any help, please tell us. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694670: kscd does not play any CD
On Wed, 28 Nov 2012 22:25:27 +0100 Rainer Dorsch rdor...@web.de wrote: whatever CD I try to play with kscd player, it does not play anything. Since vlc can play all track, audex can rip them, I think it is a problem with kscd. kscd can still read out the track list. Since I am not aware that I have any special setup, there is a fair chance that the bug affects everybody and makes the package completely unusable. If that is not the case, please downgrade the bug. I can reproduce this: when just clicking on the play button in kscd, it immediately segfaults. After setting the environment variable KDE_DEBUG=1 and ulimit -c unlimited, I get a core dump: gdb $ thread apply all bt Thread 3 (Thread 0x7f3859c3d700 (LWP 9841)): #0 0x7f386a2b1a93 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f3867aa04d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3867aa05f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f386aeb52e6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f386ae8592f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f386ae85bb8 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f386ad88d70 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f386ae6623f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f386ad8bd0b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f3869fceb50 in start_thread (arg=optimized out) at pthread_create.c:304 #10 0x7f386a2bc6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f384fef3700 (LWP 9850)): #0 0x7f386a2b1a93 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f3868803e3f in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f38687f539c in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f38687f59f9 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f38687f5ab0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f3868803def in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f3865838443 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.0.so #7 0x7f3869fceb50 in start_thread (arg=optimized out) at pthread_create.c:304 #8 0x7f386a2bc6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 1 (Thread 0x7f386d851780 (LWP 9838)): #0 0x00418720 in _start () Hopefully that helps to further debug this problem. FYI: I’m using the latest pulseaudio packages (mentioning it because libpulse shows up in the backtrace, though maybe unrelated): $ dpkg -l | grep pulse ii gstreamer0.10-pulseaudio:amd64 0.10.31-3 GStreamer plugin for PulseAudio ii libpulse-dev:amd64 2.0-6 PulseAudio client development headers and libraries ii libpulse-mainloop-glib0:amd642.0-6 PulseAudio client libraries (glib support) ii libpulse0:amd64 2.0-6 PulseAudio client libraries ii pulseaudio 2.0-6 PulseAudio sound server ii pulseaudio-utils 2.0-6 Command line tools for the PulseAudio sound server -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694786: banshee: No playback when clicking on play button
Package: banshee Version: 2.6.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, when I press play button it quickly shows the pause symbol and revert to play 3 or 4 times and no music is played. here the log [1 Debug 11:15:41.794] Querying model for track to play in song:Next mode [1 Debug 11:15:41.823] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:41.831] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:41.984] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:41.984] Player state change: Loading - Idle [1 Error 11:15:41.985] GStreamer core error: StateChange [1 Debug 11:15:42.236] Querying model for track to play in song:Next mode [1 Debug 11:15:42.275] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.284] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.389] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:42.389] Player state change: Loading - Idle [1 Error 11:15:42.390] GStreamer core error: StateChange [1 Debug 11:15:42.641] Querying model for track to play in song:Next mode [1 Debug 11:15:42.672] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.678] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Warn 11:15:42.885] Seem to be stuck loading file:///home/michele/Music/Bassi%20Maestro/Background/07.%20Hip- Hop%20derelicts.mp3, so re-trying Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.964] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:42.964] Player state change: Loading - Idle [1 Error 11:15:42.967] GStreamer core error: StateChange [1 Debug 11:15:43.218] Querying model for track to play in song:Next mode [1 Debug 11:15:43.249] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:43.255] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:43.319] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:43.319] Player state change: Loading - Idle [1
Bug#694670: kscd does not play any CD
Hi, Alle venerdì 30 novembre 2012, Michael Stapelberg ha scritto: Rainer Dorsch rdor...@web.de wrote: whatever CD I try to play with kscd player, it does not play anything. Since vlc can play all track, audex can rip them, I think it is a problem with kscd. kscd can still read out the track list. Since I am not aware that I have any special setup, there is a fair chance that the bug affects everybody and makes the package completely unusable. If that is not the case, please downgrade the bug. I can reproduce this: when just clicking on the play button in kscd, it immediately segfaults. Well, this seems a different issue (does nothing vs click and crashes) than the reported one... After setting the environment variable KDE_DEBUG=1 and ulimit -c unlimited, I get a core dump: gdb $ thread apply all bt [...] Hopefully that helps to further debug this problem. Unfortunately it not not useful, since kscd is a unique instance application which forks right after the start, so the trace of the parent process is not useful. However, you can get a better one (and try to debug kscd) just by running kscd as $ kscd --nofork also, installing kdemultimedia-dbg will help providing a more useful stack trace. Also, you could please paste the output of $ dpkg -l | grep phonon ? Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#694786: [pkg-cli-apps-team] Bug#694786: banshee: No playback when clicking on play button
On Fri, Nov 30, 2012 at 11:16:38AM +0100, Michele Cane wrote: Package: banshee Version: 2.6.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, when I press play button it quickly shows the pause symbol and revert to play 3 or 4 times and no music is played. Ta for this. Do you use pulseaudio? If so, try installing gstreamer1.0-pulseaudio. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#694670: kscd does not play any CD
Hi Pino, Pino Toscano p...@debian.org writes: Well, this seems a different issue (does nothing vs click and crashes) than the reported one... Possibly, but the reporter was not very specific. Chances are that this might be the same issue, or at least related. However, you can get a better one (and try to debug kscd) just by running kscd as $ kscd --nofork also, installing kdemultimedia-dbg will help providing a more useful stack trace. Thanks for those hints. Here is the new backtrace: gdb $ thread apply all bt Thread 3 (Thread 0x7f1716647700 (LWP 11499)): #0 0x7f17270c8a93 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f17248b74d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f17248b75f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1727ccc276 in QEventDispatcherGlib::processEvents (this=0xcee660, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f1727c9c8af in QEventLoop::processEvents (this=this@entry=0x7f1716646df0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f1727c9cb38 in QEventLoop::exec (this=0x7f1716646df0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f1727b9fd70 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f1727c7d1bf in QInotifyFileSystemWatcherEngine::run (this=0x1467b40) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f1727ba2d0b in QThreadPrivate::start (arg=0x1467b40) at thread/qthread_unix.cpp:307 #9 0x7f1726de5b50 in start_thread (arg=optimized out) at pthread_create.c:304 #10 0x7f17270d36dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f170c8fd700 (LWP 11501)): #0 0x7f17270c8a93 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f172561ae3f in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f172560c39c in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f172560c9f9 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f172560cab0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f172561adef in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f172264f443 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.0.so #7 0x7f1726de5b50 in start_thread (arg=optimized out) at pthread_create.c:304 #8 0x7f17270d36dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 1 (Thread 0x7f172a667780 (LWP 11497)): #0 AudioCD::isCdInserted (this=0x0) at ../../kscd/audiocd.cpp:131 #1 0x00413d6e in KSCD::actionButton (this=0x77f6e0, name=...) at ../../kscd/kscd.cpp:500 #2 0x7f1727cb354f in QMetaObject::activate (sender=0x77f6e0, m=optimized out, local_signal_index=optimized out, argv=0x7fffb0594590) at kernel/qobject.cpp:3547 #3 0x0040f890 in KscdWindow::actionClicked (this=optimized out, _t1=...) at moc_kscdwindow.cpp:132 #4 0x7f1727cb354f in QMetaObject::activate (sender=0x99cd30, m=optimized out, local_signal_index=optimized out, argv=0x7fffb05946d0) at kernel/qobject.cpp:3547 #5 0x0040fb83 in KscdWidget::buttonClicked (this=optimized out, _t1=...) at moc_kscdwidget.cpp:115 #6 0x0041f56e in PlayButton::mouseReleaseEvent (this=0x99cd30, event=optimized out) at ../../kscd/gui/playbutton.cpp:65 #7 0x7f1728bd1e10 in QWidget::event (this=0x99cd30, event=0x7fffb0594f60) at kernel/qwidget.cpp:8371 #8 0x7f1728b8270c in QApplicationPrivate::notify_helper (this=this@entry=0x66ecc0, receiver=receiver@entry=0x99cd30, e=e@entry=0x7fffb0594f60) at kernel/qapplication.cpp:4556 #9 0x7f1728b873eb in QApplication::notify (this=optimized out, receiver=0x99cd30, e=0x7fffb0594f60) at kernel/qapplication.cpp:4099 #10 0x7f172a078886 in KApplication::notify (this=0x7fffb0595f80, receiver=0x99cd30, event=0x7fffb0594f60) at ../../kdeui/kernel/kapplication.cpp:311 #11 0x7f1727c9db5e in QCoreApplication::notifyInternal (this=0x7fffb0595f80, receiver=0x99cd30, event=0x7fffb0594f60) at kernel/qcoreapplication.cpp:915 #12 0x7f1728b8354b in sendEvent (event=optimized out, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #13 QApplicationPrivate::sendMouseEvent (receiver=0x99cd30, event=0x7fffb0594f60, alienWidget=0x99cd30, nativeWidget=0x77f6e0, buttonDown=0x7f17296582a8, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3167 #14 0x7f1728bfdfc4 in QETWidget::translateMouseEvent (this=this@entry=0x77f6e0, event=event@entry=0x7fffb05956d0) at kernel/qapplication_x11.cpp:4523 #15 0x7f1728bfcd51 in QApplication::x11ProcessEvent (this=0x7fffb0595f80, event=0x7fffb05956d0)
Bug#694670: kscd does not play any CD
Hi Michael and Rainer, Alle venerdì 30 novembre 2012, Michael Stapelberg ha scritto: However, you can get a better one (and try to debug kscd) just by running kscd as $ kscd --nofork also, installing kdemultimedia-dbg will help providing a more useful stack trace. Thanks for those hints. Here is the new backtrace: [...] Thanks, much better. Looking upstream, I found https://bugs.kde.org/show_bug.cgi?id=265597 which now leads me to the question: do you both have udisks installed? If not, does installing it and rerunning kscd changes the situation? Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
On Thu, 2012-11-29 at 08:48:04 -0800, Don Armstrong wrote: On Thu, 29 Nov 2012, Guillem Jover wrote: On Tue, 2012-11-13 at 13:18:37 -0800, Don Armstrong wrote: diff --git a/debian/ca-certificates.triggers b/debian/ca-certificates.triggers new file mode 100644 index 000..14dec6e --- /dev/null +++ b/debian/ca-certificates.triggers @@ -0,0 +1,4 @@ +interest-noawait update-ca-certificates +interest-noawait update-ca-certificates-fresh As these are not supported by squeeze's dpkg, this can cause upgrade problems (see below). +interest update-ca-certificates +interest update-ca-certificates-fresh (OOC why the duplicates?) They're not duplicated; it can handle both noawait and non-noawait triggers. dpkg does not handle them as different trigger directives if there's synchronous and asynchronous variants, they will just end up stomping over each other. Given the current implementation, the last directive wins, so I'd expect to see only the await variants in the dpkg database. («cat /var/lib/dpkg/triggers/update-ca-certificates».) In any case, regardless of this, semantics-wise I don't think it makes much sense to have both of them present. I'll be fixing the deb-triggers(5) man page to clarify this. diff --git a/debian/control b/debian/control index 5ef776e..8f84573 100644 --- a/debian/control +++ b/debian/control @@ -13,9 +13,11 @@ Vcs-Browser: http://git.debian.org/?p=collab-maint/ca-certificates.git Package: ca-certificates Architecture: all +Pre-Depends: dpkg (= 1.16.1) This only guarantees that this dpkg version will be configured before installing this package, but not that the currently running dpkg will be that one version, so the upgrade from squeeze can still fail due to parser errors for the unknown triggers directive. I've actually tested this, and it hasn't been a problem. I suppose the only way you could get it to be one is if you were manually using dpkg. I was thinking about non-apt frontends, not just using dpkg directly. The main issue here is that the metadata does not guarantee what you want to do, and as such other non-apt frontends are not required to prepare the upgrade transaction in the same way as apt (and I'm not even sure it would be safe to expect that behaviour from apt, even if it's what it's currently doing). It'd probably be a good idea to discuss and try to come up with a way to notify dpkg and/or frontends, that they might need to restart themselves because a package requires one of its new features, so that some of those can be deployed w/o having to wait a full release cycle. I've added this to my TODO list for after wheezy. If that's really the case, then it basically means that no package in wheezy can use the noawait triggers at all. Yes, that's always been the case for lots of dpkg features, that we have to wait for a new release cycle before being able to use them. And that's been the case for the noawait directives up to now, I've just checked the lintian lab, and this is the only package using them. Regards, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694670: kscd does not play any CD
clone 694670 -1 retitle -1 crash with no optical drive forwarded 694670 https://bugs.kde.org/show_bug.cgi?id=293766 thanks Hi, Alle venerdì 30 novembre 2012, Michael Stapelberg ha scritto: I think we are in fact dealing with two separate issues here: That's what I was saying, yes :-P 1. The segfault I reported happens when there is no optical drive recognized on the system. My ThinkPad X200 does not have an optical drive, but there is one in the docking station. Unfortunately, it only works correctly when the notebook is booted with the docking station attached. That is, when submitting the backtrace, I had not booted the notebook in the docking station, so that the optical drive was not detected. Simplifying this, I suppose the same crash will happen when you disconnect the OD in your computer on purpose, or rmmod the driver. This issue can be put into a separate bugreport. Should I file a separate issue or do you want to open it? I will just clone this bug, so backlog etc is preserved. Let's continue that issue on the new bug. 2. After rebooting my notebook in the docking station and inserting an audio CD into the optical drive, kscd does not crash anymore when I press the play button. However, neither does it actually play the CD. In the terminal in which I started it, I get: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Setting new source New source: QUrl( ) Transitioning to state playing State change Moving from null 0 to ready 1 1 Transitioning to state null And that’s it. The application itself shows the title of the first track scrolling by but remains at 00:00 and does not play anything, even after many minutes. I attached a screenshot. Using mplayer cdda://0 -cdrom-device /dev/sr0 works fine. I noticed that /dev/cdrom was not present on my system, so I used ln -s /dev/sr0 /dev/cdrom and that made kscd work. Its output in the terminal is now: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Setting new source New source: QUrl( ) Transitioning to state playing State change Moving from null 0 to ready 1 Duration message Duration message State change Stream changed to cdda:// Moving from ready 1 to paused 4 State change Moving from paused 4 to playing 2 Transitioning to state paused State change Moving from playing 2 to paused 4 Interesting; possibly it won't change much, but what if (without the symlink you just created) you install phonon-backend-vlc, make it the default in `kcmshell4 phonon` and try again? Also, you might want to enable the two debug areas for kscd in `kdebugdialog`, and rerun kscd. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#694670: kscd does not play any CD
Processing commands for cont...@bugs.debian.org: clone 694670 -1 Bug #694670 [kscd] kscd does not play any CD Bug 694670 cloned as bug 694796 retitle -1 crash with no optical drive Bug #694796 [kscd] kscd does not play any CD Changed Bug title to 'crash with no optical drive' from 'kscd does not play any CD' forwarded 694670 https://bugs.kde.org/show_bug.cgi?id=293766 Bug #694670 [kscd] kscd does not play any CD Ignoring request to change the forwarded-to-address of bug#694670 to the same value thanks Stopping processing here. Please contact me if you need assistance. -- 694670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694670 694796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694417: marked as done (bbdb: package installation creates /root/.gnupg/*)
Your message dated Fri, 30 Nov 2012 12:32:28 + with message-id e1teplc-00030o...@franck.debian.org and subject line Bug#694417: fixed in bbdb 2.36-3 has caused the Debian Bug report #694417, regarding bbdb: package installation creates /root/.gnupg/* 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.) -- 694417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bbdb Version: 2.36-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed that your package creates files in /root. From the attached log (scroll to the bottom): 1m4.7s ERROR: FAIL: Package purging left files on system: /root/.gnupg/ not owned /root/.gnupg/gpg.conf not owned /root/.gnupg/pubring.gpg not owned /root/.gnupg/secring.gpg not owned Creating stuff in /root is a FHS and policy violation. (And of course these files should not be deleted by maintainer scripts.) But it is also an indication that the package operation may depend on root's .gnupg configuration (and package installation might even fail if that configuration is broken). That would be a case for configuration files not in /etc. Cheers, Andreas bbdb_2.36-2.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: bbdb Source-Version: 2.36-3 We believe that the bug you reported is fixed in the latest version of bbdb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 694...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter b...@debian.org (supplier of updated bbdb 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, 30 Nov 2012 11:52:46 + Source: bbdb Binary: bbdb Architecture: source all Version: 2.36-3 Distribution: unstable Urgency: low Maintainer: Joerg Jaspert jo...@debian.org Changed-By: Barak A. Pearlmutter b...@debian.org Description: bbdb - The Insidious Big Brother Database (email rolodex) for Emacs Closes: 694417 Changes: bbdb (2.36-3) unstable; urgency=low . [ Sébastien Villemot ] * debian/bbdb.emacsen-install: no longer create /root/.gnupg during installation of the package. This is achieved by binding GNUPGHOME to a temporary directory during bytecode compilation (Closes: #694417) Checksums-Sha1: 996ad4cf9b4d9472abb5fb255c894d40a2e46b8e 1299 bbdb_2.36-3.dsc be31e431cfd78eecb4c3670febcd31cc7464acb8 59955 bbdb_2.36-3.debian.tar.gz c330c0952bc62ade6a44d2b88a59afb5a3676447 812414 bbdb_2.36-3_all.deb Checksums-Sha256: f728c1da30454a291ca888210f68a6cd7685c70d8b05e48923126a12617ae863 1299 bbdb_2.36-3.dsc 76337a250b18d3bbfaa6df29846cbaa42d2588296a445aba00dbf51d860231db 59955 bbdb_2.36-3.debian.tar.gz 7b57a0d2bf75e93de7702e9cbed57d034515f08e48b7cd4d24468b9ddae8dfdd 812414 bbdb_2.36-3_all.deb Files: bbd05e381e40027d32b5bd64f730982b 1299 mail optional bbdb_2.36-3.dsc 69c85da859fe2a2fcc9be9167be1a815 59955 mail optional bbdb_2.36-3.debian.tar.gz 7295bc62a61415310696dd9abcc9a21b 812414 mail optional bbdb_2.36-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlC4pGMACgkQLz4Gnv7CP7LYLQCgnOtcLibwYnxN/jsR07nQSPs6 kUEAoIwr4VfRoJCwh7PY5w5H8EhdrDLf =kWVk -END PGP SIGNATUREEnd Message---
Bug#694670: kscd does not play any CD
Hi Pino, Pino Toscano p...@debian.org writes: Interesting; possibly it won't change much, but what if (without the symlink you just created) you install phonon-backend-vlc, make it the default in `kcmshell4 phonon` and try again? I did that, and it leads to the same result (music not playing). The terminal output of kscd is now: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kscd(5531) HWControler::setEjectActivated: Eject at the end mode changed kscd(5531)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from /var/tmp/kdecache-michael/ksycoca4 [0x1682548] main services discovery error: no suitable services discovery module kscd(5531) Phonon::KdePlatformPlugin::createBackend: using backend: VLC kscd(5531) HWControler::configMedia: #o#o#o# Loading Optical Drive kscd(5531) HWControler::configMedia: Phonon Loaded Object::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) in ../../phonon/mediacontroller.cpp:64 Object::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) in ../../phonon/mediacontroller.cpp:65 kscd(5531) KsCD::PlayerDBusHandler::PlayerDBusHandler: Launching Player Handler kscd(5531) HWControler::setEjectActivated: Eject at the end mode changed kscd(5531) KSCD::actionButton: time total -1 kscd(5531) HWControler::play: 0 / 0 kscd(5531) KscdWindow::changePicture: play over [0x7f068c017678] main stream error: cannot pre fill buffer Also, you might want to enable the two debug areas for kscd in `kdebugdialog`, and rerun kscd. I also did that before starting kscd for the output above. I have noticed that I have a lot of CD-ROM drives in /etc/udev/rules.d/70-persistent-cd.rules due to various hardware being connected to my computer over time (such as UMTS modems which bring their driver by emulating a CD-ROM drive). The first one is /dev/cdrom, the second one cdrom1 and so on. Currently, the symlink which gets created is /dev/cdrom5. I am not sure whether kscd or some other component of the kde multimedia stack is supposed to look for /dev/cdrom* instead of /dev/cdrom or what is the best way of figuring out where to look. After googling a bit, I stumbled upon this bug report at RedHat, which concludes that 70-persistent-cd.rules should just be deleted by the sysadmin: https://bugzilla.redhat.com/show_bug.cgi?id=570561 Tackling this issue from a different angle: What happens when I have two optical drives? How will kscd chose which one it uses? Will it always use /dev/cdrom? -- Best regards, Michael -- 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#682873: ykclient: Don't require Internet for tests
Processing control commands: severity -1 serious Bug #682873 [ykclient] ykclient: Don't require Internet for tests Severity set to 'serious' from 'normal' -- 682873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size
I've got a package complete but just want to tidy it up and test it a little more. Thanks. Kevin On Fri, Nov 30, 2012 at 4:37 AM, Michael Stapelberg stapelb...@debian.orgwrote: Hi Kevin, Michael Stapelberg stapelb...@debian.org writes: I'm on the road right now, but would be happy to upload a new version later tonight or early tomorrow morning. Thanks. Please let us know when you are done. Any news on that? If you need any help, please tell us. -- Best regards, Michael -- -- Kevin Coyner GnuPG key: 2048R/C85D8F71 http://rustybear.com/publickey.html
Bug#694670: kscd does not play any CD
Hi, Alle venerdì 30 novembre 2012, Michael Stapelberg ha scritto: Pino Toscano p...@debian.org writes: Interesting; possibly it won't change much, but what if (without the symlink you just created) you install phonon-backend-vlc, make it the default in `kcmshell4 phonon` and try again? I did that, and it leads to the same result (music not playing). Hm ok, thanks for the test anyway. I have noticed that I have a lot of CD-ROM drives in /etc/udev/rules.d/70-persistent-cd.rules due to various hardware being connected to my computer over time (such as UMTS modems which bring their driver by emulating a CD-ROM drive). The first one is /dev/cdrom, the second one cdrom1 and so on. Currently, the symlink which gets created is /dev/cdrom5. I am not sure whether kscd or some other component of the kde multimedia stack is supposed to look for /dev/cdrom* instead of /dev/cdrom or what is the best way of figuring out where to look. After googling a bit, I stumbled upon this bug report at RedHat, which concludes that 70-persistent-cd.rules should just be deleted by the sysadmin: https://bugzilla.redhat.com/show_bug.cgi?id=570561 I don't have experience with udev and its rules, so I cannot comment about this, sorry. Tackling this issue from a different angle: What happens when I have two optical drives? How will kscd chose which one it uses? Will it always use /dev/cdrom? According to the code, it basically always chooses the first, and the possibility to switch drive has never been implemented... In any case, kscd basically queries the Solid library which in the end asks udisks about the supported drives; you can find out what is detected with $ solid-hardware query IS OpticalDrive and then you can get the details of the found devices with $ solid-hardware details /org/... -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#694804: ykclient: FTBFS: ykclient_set_client_hex (105): Error decoding hex string
Source: ykclient
Version: 2.8-1
Tags: patch
Severity: serious
Justification: fails to build from source
ykclient FTBFS on architectures that have char unsigned (arm*,
powerpc, s390*):
| Test ../../tests/selftest.c:146 (main): invalid client_id set(a), correct
client_key, expect HEX_DECODE_ERROR
| ykclient_set_client_hex (105): Error decoding hex string
|
| Test ../../tests/selftest.c:151 (main): invalid client_id set(xx), correct
client_key, expect HEX_DECODE_ERROR
| ykclient_set_client_hex (105): Error decoding hex string
|
| Test ../../tests/selftest.c:156 (main): hex client_id set, correct
client_key, expect OK
| ykclient_set_client_hex (0): Success
|
| Test ../../tests/selftest.c:162 (main): validation request, expect
REPLAYED_OTP
| ykclient_request (2): Yubikey OTP was replayed (REPLAYED_OTP)
| used url:
http://api.yubico.com/wsapi/2.0/verify?id=1851nonce=lhzubwgskfxlabuofqiacaxwvtuixywiotp=dteffujehknhfjbrjnlnldnhcujvddbikngjrtghh=fHYKL35B0y7kqG6%2Br3H05r1h1lM%3D
|
| Test ../../tests/selftest.c:171 (main): set deadbeef client_id, expect OK
| ykclient_set_client_hex (0): Success
|
| Test ../../tests/selftest.c:177 (main): validation request, expect
BAD_SIGNATURE
| ykclient_request (3): Request signature was invalid (BAD_SIGNATURE)
| used url:
http://api5.yubico.com/wsapi/2.0/verify?id=1851nonce=fxwrdrtljbstjcirudqhufidchjhdsokotp=dteffujehknhfjbrjnlnldnhcujvddbikngjrtghh=y%2BagFIxlRkO8PxklcmKl3VpCiPU%3D
|
| Test ../../tests/selftest.c:186 (main): b64 set deadbeef client_id, expect OK
| ykclient_set_client_b64 (0): Success
|
| Test ../../tests/selftest.c:196 (main): validation request, expect
BAD_SERVER_SIGNATURE
| ykclient_request (106): Server response signature was invalid
(BAD_SERVER_SIGNATURE)
| used url:
http://api5.yubico.com/wsapi/2.0/verify?id=1851nonce=qijyqyuxpcunudbyeilsxwzfanraxpxnotp=dteffujehknhfjbrjnlnldnhcujvddbikngjrtghh=haGYbmYaG78McoTstt%2FFgvK14IU%3D
|
| Test ../../tests/selftest.c:210 (main): validation request, expect
BAD_SIGNATURE
| ykclient_request (3): Request signature was invalid (BAD_SIGNATURE)
| used url:
http://api5.yubico.com/wsapi/2.0/verify?id=1851nonce=kbugwnngcvkkjypxyjpowekgbkscyukjotp=dteffujehknhfjbrjnlnldnhcujvddbikngjrtghh=XTOiRnKbNKmpUoYWVEriNpcnRCs%3D
|
| Test ../../tests/selftest.c:220 (main): b64 set client_b64key, expect OK
| ykclient_set_client_b64 (0): Success
|
| Test ../../tests/selftest.c:226 (main): validation request, expect
REPLAYED_OTP
| ykclient_request (106): Server response signature was invalid
(BAD_SERVER_SIGNATURE)
| used url:
http://api5.yubico.com/wsapi/2.0/verify?id=1851nonce=birkpjutyfkxlayvfcrxdcmzoeeqqtwtotp=dteffujehknhfjbrjnlnldnhcujvddbikngjrtghh=%2BIH11rdoY4o7lXf1%2FugRwAZ6y1o%3D
| /bin/bash: line 5: 21179 Aborted ${dir}$tst
| FAIL: selftest
Full build logs:
https://buildd.debian.org/status/fetch.php?pkg=ykclientarch=armelver=2.8-1stamp=1340955748
https://buildd.debian.org/status/fetch.php?pkg=ykclientarch=armhfver=2.8-1stamp=1340952606
https://buildd.debian.org/status/fetch.php?pkg=ykclientarch=powerpcver=2.8-1stamp=1340952559
https://buildd.debian.org/status/fetch.php?pkg=ykclientarch=s390ver=2.8-1stamp=1340993933
https://buildd.debian.org/status/fetch.php?pkg=ykclientarch=s390xver=2.8-1stamp=1346194901
I believe this is because libb64 decode is broken on these
architectures. See the upstream bug:
http://sourceforge.net/tracker/?func=detailaid=3591129group_id=152942atid=785907
Indeed, applying the attached patch fixed FTBFS at least on s390.
Once libb64 is packaged separately in Debian (#694724) you might want
use it instead of the embedded copy. It will have this bug fixed, of
course. :)
I see that the buggy code is also present in wheezy and squeeze versions
which have been built successfully on unsigned-char architectures. Does
it mean these versions are unusable the architectures in question?
--
Jakub Wilk
--- ykclient-2.8.orig/b64/cdecode.c
+++ ykclient-2.8/b64/cdecode.c
@@ -9,10 +9,11 @@
int base64_decode_value(char value_in)
{
- static const char decoding[] = {62,-1,-1,-1,63,52,53,54,55,56,57,58,59,60,61,-1,-1,-1,-2,-1,-1,-1,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,-1,-1,-1,-1,-1,-1,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51};
+ static const signed char decoding[] = {62,-1,-1,-1,63,52,53,54,55,56,57,58,59,60,61,-1,-1,-1,-2,-1,-1,-1,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,-1,-1,-1,-1,-1,-1,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51};
static const char decoding_size = sizeof(decoding);
+ if (value_in 43) return -1;
value_in -= 43;
- if (value_in 0 || value_in decoding_size) return -1;
+ if (value_in decoding_size) return -1;
return decoding[(int)value_in];
}
@@ -26,7 +27,7 @@
{
const char* codechar = code_in;
char* plainchar = plaintext_out;
- char fragment;
+ int fragment;
*plainchar = state_in-plainchar;
@@ -42,7 +43,7 @@
Bug#658739: Patch from Ubuntu
Hello, The patch from Ubuntu breaks other stuff. See https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1013798 and duplicates. Note that although this (LP 1013798) was fixed in 1.5.0-3ubuntu2 the patch had to be pulled again in 1.5.0-3ubuntu2.1 because of https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1076906 How about suggestion nr 22 suggested on https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/926350 Will that do any harm? I can confirm it makes sudo work again. Will test some more to see if it breaks anything else. Regards, martijn van brummelen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689314: perl: segfaults when echoing a very long string
On Wed, Oct 10, 2012 at 09:35:41PM +0300, Niko Tyni wrote: severity 689314 grave retitle 689314 perl: segfaults when echoing a very long string [CVE-2012-5195] tag 689314 upstream security patch thanks On Mon, Oct 01, 2012 at 04:11:00PM +0200, Thorsten Glaser wrote: Package: perl Version: 5.14.2-13 Severity: normal # perl -le 'print vx(2**31+1) .=1' Segmentation fault This has security impact and has been assigned CVE-2012-5195. See http://www.nntp.perl.org/group/perl.perl5.porters/2012/10/msg193886.html http://perl5.git.perl.org/perl.git/commit/b675304e3fdbcce3ef853b06b6ebe870d99faa7e It's not quite clear yet if 5.10.1 (squeeze) is affected. We are nevertheless planning to upload fix to stable-security shortly. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopen
Processing commands for cont...@bugs.debian.org:
reopen 689314
Bug #689314 {Done: Niko Tyni nt...@debian.org} [perl] perl: segfaults when
echoing a very long string [CVE-2012-5195]
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions perl/5.14.2-14.
fixed 689314 5.14.2-14
Bug #689314 [perl] perl: segfaults when echoing a very long string
[CVE-2012-5195]
Marked as fixed in versions perl/5.14.2-14.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
689314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694446: im-config should setting environment variable in 70im-config_launch instead of im-launch
The one in your branch works for me. Thx On Mon, Nov 26, 2012 at 10:04 PM, Weng Xuetian wen...@gmail.com wrote: Package: im-config Version: 0.18~quantal1 Severity: normal Tags: upstream (Sorry for report it from ubuntu) im-config 0.18 uses im-launch to fix some old problem, but also brought some new problem. in current initialization sequence, the final command will be: dbus-launch im-launch command-for-start-up This ignore the fact that dbus-daemon launched by dbus-launch is not covered under required im environment variable. In some case, dbus-daemon will be used to start process by dbus service name, those application can also be GUI application, and it will make those application running with no im environment variable set. For example, ktp-text-ui (kde telepathy text ui) is suffering from this problem. The fix to this problem is simple, keep the code that start input method in im-launch, but move the environment setting code to 70im-config_launch, so dbus-daemon will be also set with those environment variable, and so will those process started by dbus-daemon. -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal'), (100, 'quantal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-18-generic (SMP w/3 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages im-config depends on: ii dialog1.1-20120215-2ubuntu1 ii gettext-base 0.18.1.1-9ubuntu1 ii zenity3.4.0-2 Versions of packages im-config recommends: ii dialog 1.1-20120215-2ubuntu1 ii x11-common 1:7.7+1ubuntu4 im-config suggests no packages. -- no debconf information -- YunQiang Su
Bug#693460: Bug#694091: bcrypt: Tries to load whole file into memory regardless of the size
Hi Kevin, Kevin Coyner kcoy...@debian.org writes: I've got a package complete but just want to tidy it up and test it a little more. Thanks. Please keep in mind that packages should have minimal differences to their previous version if we want to get them into wheezy. The more changes you do, the smaller the chance of that succeeding. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691911: marked as done (libkohana3.1-php: FTBFS in Debian Sid)
Your message dated Fri, 30 Nov 2012 14:48:56 + with message-id e1tertg-0006du...@franck.debian.org and subject line Bug#691911: fixed in libkohana3.1-php 3.1.5-1.1 has caused the Debian Bug report #691911, regarding libkohana3.1-php: FTBFS in Debian Sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 691911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libkohana3.1-php Version: 3.1.5-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch Dear Maintainer, the package FTBFS in sid because install rule tries to overwrite a symlink with cp. Please see the patch. Cheers, In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: Remove shCore.js file before make a symlink, fix FTBFS Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal-proposed'), (500, 'quantal'), (100, 'quantal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-18-generic (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru libkohana3.1-php-3.1.5/debian/changelog libkohana3.1-php-3.1.5/debian/changelog diff -Nru libkohana3.1-php-3.1.5/debian/rules libkohana3.1-php-3.1.5/debian/rules --- libkohana3.1-php-3.1.5/debian/rules 2012-09-29 19:01:00.0 +0200 +++ libkohana3.1-php-3.1.5/debian/rules 2012-10-31 10:00:02.0 +0100 @@ -33,6 +33,7 @@ rm -f $(DESTDIR)/modules/image/media/guide/image/Thumbs.db rm -f $(DESTDIR)/modules/userguide/media/guide/js/jquery.cookie.js rm -f $(DESTDIR)/modules/userguide/media/guide/js/jquery.min.js + rm -f $(DESTDIR)/modules/userguide/media/guide/js/shCore.js rm -f $(DESTDIR)/modules/userguide/vendor/markdown/License.text dh_link -plibkohana$(MAJOR_VERSION)-mod-userguide-php \ /usr/share/javascript/jquery/jquery.min.js \ ---End Message--- ---BeginMessage--- Source: libkohana3.1-php Source-Version: 3.1.5-1.1 We believe that the bug you reported is fixed in the latest version of libkohana3.1-php, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 691...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Angel Abad an...@debian.org (supplier of updated libkohana3.1-php 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: Sun, 25 Nov 2012 14:46:53 +0100 Source: libkohana3.1-php Binary: libkohana-php libkohana3.1-php libkohana3.1-core-php libkohana3.1-mod-auth-php libkohana3.1-mod-cache-php libkohana3.1-mod-codebench-php libkohana3.1-mod-database-php libkohana3.1-mod-image-php libkohana3.1-mod-orm-php libkohana3.1-mod-unittest-php libkohana3.1-mod-userguide-php Architecture: source all Version: 3.1.5-1.1 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) g...@debian.hu Changed-By: Angel Abad an...@debian.org Description: libkohana-php - swift, secure, and small PHP 5 framework libkohana3.1-core-php - PHP5 framework core classes libkohana3.1-mod-auth-php - swift, secure, and small PHP 5 framework, auth module libkohana3.1-mod-cache-php - swift, secure, and small PHP 5 framework, cache module libkohana3.1-mod-codebench-php - swift, secure, and small PHP 5 framework, codebench module libkohana3.1-mod-database-php - swift, secure, and small PHP 5 framework, database module libkohana3.1-mod-image-php - swift, secure, and small PHP 5 framework, image module libkohana3.1-mod-orm-php - swift, secure, and small PHP 5 framework, ORM module libkohana3.1-mod-unittest-php - swift, secure, and small PHP 5 framework, unittest module libkohana3.1-mod-userguide-php - swift, secure, and small PHP 5 framework, userguide module libkohana3.1-php - PHP5 framework metapackage Closes: 691911 Changes: libkohana3.1-php (3.1.5-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/rules: Remove shCore.js file before make a symlink, fix FTBFS (Closes:
Bug#694786: marked as done (banshee: No playback when clicking on play button)
Your message dated Fri, 30 Nov 2012 14:47:44 + with message-id e1tersw-0004v3...@franck.debian.org and subject line Bug#694786: fixed in banshee 2.6.0-4 has caused the Debian Bug report #694786, regarding banshee: No playback when clicking on play button 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.) -- 694786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: banshee Version: 2.6.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, when I press play button it quickly shows the pause symbol and revert to play 3 or 4 times and no music is played. here the log [1 Debug 11:15:41.794] Querying model for track to play in song:Next mode [1 Debug 11:15:41.823] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:41.831] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:41.984] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:41.984] Player state change: Loading - Idle [1 Error 11:15:41.985] GStreamer core error: StateChange [1 Debug 11:15:42.236] Querying model for track to play in song:Next mode [1 Debug 11:15:42.275] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.284] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.389] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:42.389] Player state change: Loading - Idle [1 Error 11:15:42.390] GStreamer core error: StateChange [1 Debug 11:15:42.641] Querying model for track to play in song:Next mode [1 Debug 11:15:42.672] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.678] (libbanshee:player) Audiosink has volume: NO Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Warn 11:15:42.885] Seem to be stuck loading file:///home/michele/Music/Bassi%20Maestro/Background/07.%20Hip- Hop%20derelicts.mp3, so re-trying Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started [1 Debug 11:15:42.964] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [1 Debug 11:15:42.964] Player state change: Loading - Idle [1 Error 11:15:42.967] GStreamer core error: StateChange [1 Debug 11:15:43.218] Querying model for track to play in song:Next mode [1 Debug 11:15:43.249] Player state change: Idle - Loading Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or
Bug#694446: im-config should setting environment variable in 70im-config_launch instead of im-launch
Hi, On Fri, Nov 30, 2012 at 10:33:11PM +0800, YunQiang Su wrote: The one in your branch works for me. Good :-) I had uploaded this fixed version to experimental. If I here no problem on it, I will upload it to unstable sometime before Monday. Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694808: libv8: CVE-2012-5120 CVE-2012-5128
Package: libv8 Severity: grave Tags: security Justification: user security hole Please see http://googlechromereleases.blogspot.de/2012/11/stable-channel-release-and-beta-channel.html Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692899: zope2.12: [CVE-2012-5485 to 5508] Multiple vectors corrected within 20121106 fix
On Sun, Nov 25, 2012 at 11:07:38AM +0900, Arnaud Fontaine wrote: Hello, Luciano Bello luci...@debian.org writes: Hi, please see : http://seclists.org/oss-sec/2012/q4/249 Can you confirm if any of the Debian packages are affected? As far as I could find (not clear in the upstream changelog): version 2.12.26: * LP #1071067 fixes CVE 2012-5507, CVE 2012-5508. * LP #930812 fixes CVE 2012-5486. version 2.12.21: * LP #1079238 fixes CVE 2012-5489. According to the upstream changelog, LP #1047318 seems to fix a security bug, but I could not find it in zope2 launchpad nor anywhere else. The following CVEs are not affecting Zope2 package (Plone/Zope3/..) (within brackets is the Product/module/... affected along with the corresponding filename in Plone Hotfix): For clarification, so that I can update the Debian Security Tracker, none of these CVE IDs are packaged in Debian, right? (I can't find a Plone package, but these could be packaged through one of the many zope.* packages?) * CVE-2012-5485 (Plone: registerConfiglet.py) http://plone.org/products/plone/security/advisories/20121106/01 * CVE-2012-5488/CVE-2012-5494/CVE-2012-5495/CVE-2012-5499/CVE-2012-5506 (Plone-specific: python_scripts.py) http://plone.org/products/plone/security/advisories/20121106/04 http://plone.org/products/plone/security/advisories/20121106/10 http://plone.org/products/plone/security/advisories/20121106/11 http://plone.org/products/plone/security/advisories/20121106/15 http://plone.org/products/plone/security/advisories/20121106/22 * CVE-2012-5490 (kss: kssdevel.py) http://plone.org/products/plone/security/advisories/20121106/06 * CVE-2012-5491/CVE-2012-5504 (z3c.form (Zope3): widget_traversal.py) http://plone.org/products/plone/security/advisories/20121106/12 http://plone.org/products/plone/security/advisories/20121106/20 * CVE-2012-5492 (Plone: uid_catalog.py) http://plone.org/products/plone/security/advisories/20121106/08 * CVE-2012-5493 (CMFCore: gtbn.py) http://plone.org/products/plone/security/advisories/20121106/09 * CVE-2012-5496 (Plone: kupu_spellcheck.py) http://plone.org/products/plone/security/advisories/20121106/09 * CVE-2012-5497 (Plone: membership_tool.py) http://plone.org/products/plone/security/advisories/20121106/13 * CVE-2012-5498 (Plone: queryCatalog.py) http://plone.org/products/plone/security/advisories/20121106/14 * CVE-2012-5500 (Plone: renameObjectsByPaths.py) http://plone.org/products/plone/security/advisories/20121106/15 * CVE-2012-5501 (Plone: at_download.py) http://plone.org/products/plone/security/advisories/20121106/17 * CVE-2012-5502 (PortalTransforms: safe_html.py) http://plone.org/products/plone/security/advisories/20121106/18 * CVE-2012-5503 (Plone-specific: ObjectManager: ftp.py) http://plone.org/products/plone/security/advisories/20121106/19 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693026: Pre-approval request for t-p-u upload of weechat/0.3.8-2wheezy1
On Thu, Nov 15, 2012 at 09:17:49PM +0100, Emmanuel Bouthenot wrote: On Thu, Nov 15, 2012 at 08:27:29PM +0100, Julien Cristau wrote: [...] My opinion is you can wait more than a couple days. Anyway, I've learnt today that it has been discovered another security issue which will lead to another CVE soon, hence I suggest to wait until this one will be fixed in unstable. I'll come back to you for an upload in t-p-u which will fix these two bugs in a row. What's the status? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693026: Pre-approval request for t-p-u upload of weechat/0.3.8-2wheezy1
On Fri, Nov 30, 2012 at 04:06:41PM +0100, Moritz Muehlenhoff wrote:
[...]
Anyway, I've learnt today that it has been discovered another security
issue which will lead to another CVE soon, hence I suggest to wait until
this one will be fixed in unstable.
I'll come back to you for an upload in t-p-u which will fix these two
bugs in a row.
What's the status?
Following release team members, I filed a bug report.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693702
M.
--
Emmanuel Bouthenot
mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kolter@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694810: plib: CVE-2012-4552
Package: plib Severity: grave Tags: important http://www.openwall.com/lists/oss-security/2012/10/29/8 Please see the Red Hat bug for more details on the patch status: https://bugzilla.redhat.com/show_bug.cgi?id=871187 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694684: marked as done (cityhash: Fix for FTBFS on PowerPC, ARM, and S/390)
Your message dated Fri, 30 Nov 2012 15:17:29 + with message-id e1teslj-0004ll...@franck.debian.org and subject line Bug#694684: fixed in cityhash 1.1.0-2 has caused the Debian Bug report #694684, regarding cityhash: Fix for FTBFS on PowerPC, ARM, and S/390 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.) -- 694684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cityhash Version: 1.1.0-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch In Ubuntu, I've worked around the FTBFS on arches with unsigned chars with the following patch. The correct solution would be to hunt down everywhere in the source that incorrectly assumes char=uint, but this works as a quick fix to make the testsuite pass again. ... Adam -- System Information: Debian Release: wheezy/sid APT prefers raring-updates APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.0-4-generic (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru cityhash-1.1.0/debian/changelog cityhash-1.1.0/debian/changelog diff -Nru cityhash-1.1.0/debian/rules cityhash-1.1.0/debian/rules --- cityhash-1.1.0/debian/rules 2012-11-19 06:06:16.0 -0700 +++ cityhash-1.1.0/debian/rules 2012-11-28 17:57:09.0 -0700 @@ -2,6 +2,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +# The source assumes signed chars, apply quick hack: +export DEB_CXXFLAGS_MAINT_APPEND = -fsigned-char + %: dh $@ --with autotools-dev ---End Message--- ---BeginMessage--- Source: cityhash Source-Version: 1.1.0-2 We believe that the bug you reported is fixed in the latest version of cityhash, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 694...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessandro Ghedini gh...@debian.org (supplier of updated cityhash 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, 30 Nov 2012 16:04:58 +0100 Source: cityhash Binary: libcityhash0 libcityhash-dev libcityhash-dbg Architecture: source amd64 Version: 1.1.0-2 Distribution: unstable Urgency: low Maintainer: Alessandro Ghedini gh...@debian.org Changed-By: Alessandro Ghedini gh...@debian.org Description: libcityhash-dbg - debugging symbols for cityhash libcityhash-dev - development files and static library for cityhash libcityhash0 - family of non-cryptographic hash functions for strings Closes: 694684 Changes: cityhash (1.1.0-2) unstable; urgency=low . * Pass -fsigned-char compiler flag to fix FTBFS on PowerPC, ARM and S/390. Thanks to Adam Conrad for the patch (Closes: #694684) Checksums-Sha1: 8619b027decaa7deadde4a00a806d6c99f59ca8b 1965 cityhash_1.1.0-2.dsc 29bba594e560f3f17e31a068ca6c82dc543955d8 2813 cityhash_1.1.0-2.debian.tar.gz f20d85283af527296a2cbdb2adddef844c8a1016 12340 libcityhash0_1.1.0-2_amd64.deb 7a4b1a8b21a1b1a6a75b1c360f07922ec90d25a0 9118 libcityhash-dev_1.1.0-2_amd64.deb c1db1f43917b909ce9ea18419d22ecee9e94d026 18570 libcityhash-dbg_1.1.0-2_amd64.deb Checksums-Sha256: af5a0357ed9a46643992e086d0eff30f752f3394fd72d9195289f89e1771a711 1965 cityhash_1.1.0-2.dsc ff07315100d7d668c645600bafbb9fa6f5d232e83d579ee1745c54945d9d6119 2813 cityhash_1.1.0-2.debian.tar.gz 57c0d4660e96c93e6b8dba67d0a5c08176d12b131f24112e2160d27d638fd015 12340 libcityhash0_1.1.0-2_amd64.deb 3bcdef64d5a72345292b2bfa6d1a46983cfeea853578929554c7de7dbd951bb2 9118 libcityhash-dev_1.1.0-2_amd64.deb de8a110b632872e1051f22c0a5d3d64a418713f94ddfe983a807ff78b138893e 18570 libcityhash-dbg_1.1.0-2_amd64.deb Files: 0f12817f43410c64efe262aa2ee33ead 1965 libs optional cityhash_1.1.0-2.dsc 22a8ca475d72cdf9ee51fb45301a1eaa 2813 libs optional cityhash_1.1.0-2.debian.tar.gz 3e222c1063f95c8b1baf511e4402024f 12340 libs optional libcityhash0_1.1.0-2_amd64.deb 67450d05bd3617b6a0bb16a0795e5f95 9118 libdevel optional libcityhash-dev_1.1.0-2_amd64.deb
Bug#694748: marked as done (php5-ps segmentation fault on ps_setfont (64bit))
Your message dated Fri, 30 Nov 2012 15:32:54 +
with message-id e1tesae-0007rw...@franck.debian.org
and subject line Bug#694748: fixed in php-ps 1.3.7-1
has caused the Debian Bug report #694748,
regarding php5-ps segmentation fault on ps_setfont (64bit)
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.)
--
694748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: php5-ps
Version: 1.3.6-7
Severity: grave
Tags: patch upstream
Justification: renders package unusable
Forwarding Ubuntu bug report:
http://pad.lv/1024207
This was seen on Ubuntu and FreeBSD systems. Upstream has not acknowledged
the bug (perhaps dead upstream?)
-- System Information:
Debian Release: wheezy/sid
APT prefers quantal-updates
APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500,
'quantal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/ps.c 2007-11-27 03:40:14.0 -0600
+++ b/ps.c 2012-07-13 01:35:16.815241282 -0500
@@ -518,7 +518,8 @@
{
zval *zps;
char *text;
- int text_len, len;
+ int text_len;
+long len;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rsl, zps, text, text_len, len)) {
@@ -527,7 +528,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- PS_show2(ps, text, len);
+ PS_show2(ps, text, (int)len);
RETURN_TRUE;
}
@@ -561,7 +562,8 @@
{
zval *zps;
char *text;
- int text_len, len;
+ int text_len;
+long len;
double x, y;
PSDoc *ps;
@@ -571,7 +573,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- PS_show_xy2(ps, text, len, (float) x, (float) y);
+ PS_show_xy2(ps, text, (int)len, (float) x, (float) y);
RETURN_TRUE;
}
@@ -611,7 +613,7 @@
PHP_FUNCTION(ps_setfont) {
zval *zps;
double fontsize;
- int font;
+ long font;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rld, zps, font, fontsize)) {
@@ -620,7 +622,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- PS_setfont(ps, font, (float) fontsize);
+ PS_setfont(ps, (int)font, (float) fontsize);
RETURN_TRUE;
}
@@ -691,7 +693,7 @@
PHP_FUNCTION(ps_setoverprintmode)
{
zval *zps;
- int mode;
+ long mode;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rl, zps, mode)) {
@@ -700,7 +702,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- PS_setoverprintmode(ps, mode);
+ PS_setoverprintmode(ps, (int)mode);
RETURN_TRUE;
}
@@ -944,7 +946,7 @@
PHP_FUNCTION(ps_setlinejoin)
{
zval *zps;
- int value;
+ long value;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rl, zps, value)) {
@@ -953,7 +955,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- PS_setlinejoin(ps, value);
+ PS_setlinejoin(ps, (int)value);
RETURN_TRUE;
}
@@ -964,7 +966,7 @@
PHP_FUNCTION(ps_setlinecap)
{
zval *zps;
- int value;
+ long value;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rl, zps, value)) {
@@ -973,7 +975,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- PS_setlinecap(ps, value);
+ PS_setlinecap(ps, (int)value);
RETURN_TRUE;
}
@@ -1091,7 +1093,7 @@
char *text;
int text_len;
double width, size = 0.0;
- int font = 0;
+ long font = 0;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rs|ld, zps, text, text_len, font, size)) {
@@ -1100,7 +1102,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- width = (double) PS_stringwidth2(ps, text, text_len, font, (float)size);
+ width = (double) PS_stringwidth2(ps, text, text_len, (int)font, (float)size);
RETURN_DOUBLE((double) width);
}
@@ -1114,7 +1116,7 @@
char *text;
int text_len;
double width, size = 0.0;
- int font = 0;
+ long font = 0;
float dimension[3];
PSDoc *ps;
@@ -1124,7 +1126,7 @@
PSDOC_FROM_ZVAL(ps, zps);
- width = (double) PS_string_geometry(ps, text, text_len, font, (float) size, dimension);
+ width = (double) PS_string_geometry(ps, text, text_len, (int)font, (float) size, dimension);
array_init(return_value);
add_assoc_double(return_value, width, (double) dimension[0]);
@@ -1279,7 +1281,7 @@
zval *zps;
char *text;
int text_len;
- int parentid = 0, open = 0, id;
+ long parentid = 0, open = 0, id;
PSDoc *ps;
if (FAILURE == zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, rs|ll, zps, text, text_len, parentid, open)) {
@@ -1289,7 +1291,7 @@
PSDOC_FROM_ZVAL(ps, zps);
/* will never return 0 */
- id = PS_add_bookmark(ps, text, parentid, open);
+ id =
Bug#604234: marked as done (emacspeak-ss: dpkg hangs while preconfiguring packages)
Your message dated Fri, 30 Nov 2012 16:02:58 + with message-id e1tet3k-0006xe...@franck.debian.org and subject line Bug#604234: fixed in emacspeak-ss 1.12.1-2 has caused the Debian Bug report #604234, regarding emacspeak-ss: dpkg hangs while preconfiguring packages 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.) -- 604234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: emacspeak-ss Version: 1.12.1-1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20101120 instest Hi, While testing the installation of all packages in unstable, I ran into the following problem: (squeeze64-instest)root@parapluie-7:~# apt-get install emacspeak-ss Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: adduser anthy-common bsdmainutils cpp cpp-4.4 dbus defoma emacs23 emacs23-bin-common emacs23-common emacsen-common emacspeak file fontconfig fontconfig-config gconf2-common hicolor-icon-theme ifupdown libanthy0 libasound2 libatk1.0-0 libatk1.0-data libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-glib-1-2 libexpat1 libfont-freetype-perl libfontconfig1 libfontenc1 libfreetype6 libfribidi0 libgconf2-4 libgcrypt11 libgd2-noxpm libgdbm3 libgif4 libglib2.0-0 libglib2.0-data libgmp3c2 libgnutls26 libgpg-error0 libgpm2 libgsf-1-114 libgsf-1-common libgssapi-krb5-2 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libice6 libidl0 libjasper1 libjpeg62 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 liblockfile1 libm17n-0 libmagic1 libmpfr4 libnewt0.52 liborbit2 libotf0 libpango1.0-0 libpango1.0-common libpcre3 libpixman-1-0 libpng12-0 libpopt0 librsvg2-2 libsasl2-2 libsasl2-modules libsm6 libssl0.9.8 libtasn1-3 libthai-data libthai0 libtiff4 libx11-6 libx11-data libxau6 libxcb-render-util0 libxcb-render0 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxfont1 libxft2 libxi6 libxinerama1 libxml2 libxpm4 libxrandr2 libxrender1 libxt6 m17n-contrib m17n-db make net-tools netbase perl perl-modules sgml-base shared-mime-info tcl8.4 tclx8.4 ttf-dejavu-core ucf whiptail x-ttcidfont-conf x11-common xfonts-encodings xfonts-utils xml-core Suggested packages: wamerican wordlist whois vacation cpp-doc gcc-4.4-locales dbus-x11 defoma-doc psfontmgr dfontmgr emacs23-common-non-dfsg emacs23-el psgml xsltproc eflite espeak w3m-el iproute dhcp3-client dhcp-client ppp libasound2-plugins cups-common rng-tools libgd-tools gnutls-bin gpm krb5-doc krb5-user librsvg2-common gvfs libjasper-runtime m17n-docs ttf-japanese-gothic ttf-japanese-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp librsvg2-bin libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal gawk make-doc perl-doc libterm-readline-gnu-perl libterm-readline-perl-perl sgml-base-doc tclreadline tclx8.4-doc debhelper The following NEW packages will be installed: adduser anthy-common bsdmainutils cpp cpp-4.4 dbus defoma emacs23 emacs23-bin-common emacs23-common emacsen-common emacspeak emacspeak-ss file fontconfig fontconfig-config gconf2-common hicolor-icon-theme ifupdown libanthy0 libasound2 libatk1.0-0 libatk1.0-data libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-glib-1-2 libexpat1 libfont-freetype-perl libfontconfig1 libfontenc1 libfreetype6 libfribidi0 libgconf2-4 libgcrypt11 libgd2-noxpm libgdbm3 libgif4 libglib2.0-0 libglib2.0-data libgmp3c2 libgnutls26 libgpg-error0 libgpm2 libgsf-1-114 libgsf-1-common libgssapi-krb5-2 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libice6 libidl0 libjasper1 libjpeg62 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 liblockfile1 libm17n-0 libmagic1 libmpfr4 libnewt0.52 liborbit2 libotf0 libpango1.0-0 libpango1.0-common libpcre3 libpixman-1-0 libpng12-0 libpopt0 librsvg2-2 libsasl2-2 libsasl2-modules libsm6 libssl0.9.8 libtasn1-3 libthai-data libthai0 libtiff4 libx11-6 libx11-data libxau6 libxcb-render-util0 libxcb-render0 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxfont1 libxft2 libxi6 libxinerama1 libxml2 libxpm4 libxrandr2 libxrender1 libxt6 m17n-contrib m17n-db make net-tools netbase perl perl-modules
Bug#694670: kscd does not play any CD
Hi Pino,
Pino Toscano p...@debian.org writes:
In any case, kscd basically queries the Solid library which in the end
asks udisks about the supported drives; you can find out what is
detected with
$ solid-hardware query IS OpticalDrive
and then you can get the details of the found devices with
$ solid-hardware details /org/...
$ solid-hardware query IS OpticalDrive
udi = '/org/freedesktop/UDisks/devices/sr0'
$ solid-hardware details /org/freedesktop/UDisks/devices/sr0
udi = '/org/freedesktop/UDisks/devices/sr0'
parent = '/org/freedesktop/UDisks' (string)
vendor = 'HL-DT-ST' (string)
product = 'HL-DT-STCD-RW/DVD DRIVE MU10N' (string)
description = 'CD-RW/DVD-ROM Drive' (string)
Block.major = 11 (0xb) (int)
Block.minor = 0 (0x0) (int)
Block.device = '/dev/sr0' (string)
StorageDrive.bus = 'Scsi' (0x3) (enum)
StorageDrive.driveType = 'CdromDrive' (0x1) (enum)
StorageDrive.removable = true (bool)
StorageDrive.hotpluggable = false (bool)
StorageDrive.inUse = false (bool)
StorageDrive.size = 654350336 (0x27009800) (qulonglong)
OpticalDrive.supportedMedia = 'Cdr|Cdrw|Dvd' (0x7) (flag)
OpticalDrive.readSpeed = 0 (0x0) (int)
OpticalDrive.writeSpeed = 0 (0x0) (int)
OpticalDrive.writeSpeeds = {} (int list)
So, this works as expected. But we must still be missing something.
To figure out where the problem lies, I wrote a tiny example program:
#include iostream
#include phonon/phononnamespace.h
#include phonon/mediaobject.h
#include phonon/mediasource.h
#include phonon/mediacontroller.h
#include QApplication
int main(int argc, char *argv[]) {
QApplication app(argc, argv);
app.setOrganizationName(Trolltech);
app.setApplicationName(Application Example);
std::cout ohai std::endl;
Phonon::MediaObject *myMusic =
Phonon::createPlayer(Phonon::MusicCategory,Phonon::MediaSource(Phonon::Cd,
QString(/dev/sr0)));
Phonon::MediaController myMediaController(myMusic);
myMediaController.setAutoplayTitles(true);
myMusic-play();
}
(compile it with g++ -g -o test test.cpp $(pkg-config --cflags --libs phonon
QtCore))
This program exhibits the same symptom as kscd.
It turns out that there is at least one access to /dev/cdrom through
gstreamer, which implies for me that either phonon or gstreamer itself
is buggy:
gdb $ bt
#0 *__GI___xstat (vers=1, name=0xaab720 /dev/cdrom, buf=0x7fffd9a0)
at ../sysdeps/unix/sysv/linux/wordsize-64/xstat.c:37
#1 0x7fffe39ada82 in cdda_identify () from /usr/lib/libcdda_interface.so.0
#2 0x7fffe3df5aef in ?? () from
/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstcdparanoia.so
#3 0x7fffe3bbdcdc in ?? () from
/usr/lib/x86_64-linux-gnu/libgstcdda-0.10.so.0
#4 0x7fffeb6e5048 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0
#5 0x7fffeb6e5a88 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0
#6 0x7fffecc94c3b in gst_pad_activate_push () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#7 0x7fffecc956d7 in gst_pad_set_active () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#8 0x7fffecc749b0 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#9 0x7fffecc870be in gst_iterator_fold () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#10 0x7fffecc74921 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#11 0x7fffecc76f07 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#12 0x7fffecc77273 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#13 0x7fffeb6e7c44 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0
#14 0x7fffecc78fcc in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#15 0x7fffecc7904f in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#16 0x7fffecc79922 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#17 0x7fffecc6670a in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#18 0x7fffe400bada in ?? () from
/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstdecodebin2.so
#19 0x7fffecc78fcc in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#20 0x7fffecc79922 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#21 0x7fffecc6670a in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#22 0x7fffecc99528 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#23 0x7fffdf74cce0 in ?? () from
/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
#24 0x7fffecc78fcc in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#25 0x7fffecc7904f in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#26 0x7fffecc79922 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#27 0x7fffecf4e53a in
Bug#684633: marked as done (jless: hangs with 1MB file, and should consider its future)
Your message dated Fri, 30 Nov 2012 17:16:35 +0100 with message-id 20121130161635.ga14...@jadzia.comodo.priv.at and subject line Re: Bug#684633: jless: hangs with 1MB file, and should consider its future has caused the Debian Bug report #684633, regarding jless: hangs with 1MB file, and should consider its future 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.) -- 684633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jless Version: 382-iso262-2.1 Severity: important Hi, One user claims jless is buggy, it hangs with reading a bit large file (1MB or so). I confirmed it with chromium's copyright file. And I think it should be removed from next release. - It cannot be used under UTF-8 (default locale), needs ja_JP.EUC-JP locale. And we don't support EUC-JP locale. - Dead upstream (http://www.pobox.com/~jam/less/ redirects to auther's(?) blog. we can see it as http://web.archive.org/web/20070317201620/http://www25.big.jp/~jam/less/ ) - It's fork of less, but its base version is too old * less - 444 * jless - 382 - Now we have alternate pager lv, its upstream is still alive We should drop jless from testing and consider to maintain (rebase newer less version, at least) it or not. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane ---End Message--- ---BeginMessage--- Version: 382-iso262-3 On Sun, 12 Aug 2012 16:05:48 +0900, Hideki Yamane wrote: One user claims jless is buggy, it hangs with reading a bit large file (1MB or so). I confirmed it with chromium's copyright file. This bug is supposed to be fixed by the 382-iso262-3 upload; not sure why the information from the changelog didn't make it to the BTS. Cheers, gregor, doing a manual versioned close now -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Tom Waits: Closing Time signature.asc Description: Digital signature ---End Message---
Bug#680632: marked as done (jless: [regression] jless hangs if it reaches 524289 bytes)
Your message dated Fri, 30 Nov 2012 17:16:35 +0100
with message-id 20121130161635.ga14...@jadzia.comodo.priv.at
and subject line Re: Bug#684633: jless: hangs with 1MB file, and should
consider its future
has caused the Debian Bug report #684633,
regarding jless: [regression] jless hangs if it reaches 524289 bytes
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.)
--
684633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: jless
Version: 382-iso262-2.1
Severity: important
jless hangs if it reaches 524289 bytes. cpu is 100% and control-c
doesn't kill it. control-\ and kill(1) kill it. jless 382-iso262-2
works fine.
steps to reproduce:
$ awk 'BEGIN {for (i = 0; i 524288; ++i) print }' | jless
then enter G
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.5.0-rc5 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP)
Shell: /bin/sh linked to /bin/dash
Versions of packages jless depends on:
ii debianutils 4.3.2
ii libc62.13-34
ii libncurses5 5.9-10
ii libtinfo55.9-10
jless recommends no packages.
jless suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Version: 382-iso262-3
On Sun, 12 Aug 2012 16:05:48 +0900, Hideki Yamane wrote:
One user claims jless is buggy, it hangs with reading a bit large file (1MB
or so). I confirmed it with chromium's copyright file.
This bug is supposed to be fixed by the 382-iso262-3 upload; not sure
why the information from the changelog didn't make it to the BTS.
Cheers,
gregor, doing a manual versioned close now
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Tom Waits: Closing Time
signature.asc
Description: Digital signature
---End Message---
Bug#671297: isdnutils: diff for NMU version 1:3.25+dfsg1-3.1
tags 671297 + patch
tags 671297 + pending
thanks
Dear maintainer,
I've prepared an NMU for isdnutils (versioned as 1:3.25+dfsg1-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Melissa Etheridge: Sleep
diff -Nru isdnutils-3.25+dfsg1/debian/changelog isdnutils-3.25+dfsg1/debian/changelog
--- isdnutils-3.25+dfsg1/debian/changelog 2012-09-23 08:55:17.0 +0200
+++ isdnutils-3.25+dfsg1/debian/changelog 2012-11-30 17:26:13.0 +0100
@@ -1,3 +1,12 @@
+isdnutils (1:3.25+dfsg1-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix isdnutils-base and libcapi20-dev: error when trying to install
+together: add Breaks+Replaces to libcapi20-dev, thanks Andreas Beckmann.
+(Closes: #671297)
+
+ -- gregor herrmann gre...@debian.org Fri, 30 Nov 2012 17:26:07 +0100
+
isdnutils (1:3.25+dfsg1-3) unstable; urgency=low
* translation update. Closes: #686180
diff -Nru isdnutils-3.25+dfsg1/debian/control isdnutils-3.25+dfsg1/debian/control
--- isdnutils-3.25+dfsg1/debian/control 2012-09-23 08:24:48.0 +0200
+++ isdnutils-3.25+dfsg1/debian/control 2012-11-30 17:26:04.0 +0100
@@ -143,7 +143,9 @@
Section: libdevel
Multi-Arch: same
Depends: libcapi20-3 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
-Replaces: libcapi20-3 ( 1:3.9.20060704+dfsg.3-4)
+Breaks: isdnutils-base ( 1:3.22+dfsg1-4)
+Replaces: libcapi20-3 ( 1:3.9.20060704+dfsg.3-4),
+ isdnutils-base ( 1:3.22+dfsg1-4)
Suggests: isdnutils-doc
Description: ISDN utilities - CAPI development libraries
This package provides files needed for development of CAPI-aware software.
signature.asc
Description: Digital signature
Processed: isdnutils: diff for NMU version 1:3.25+dfsg1-3.1
Processing commands for cont...@bugs.debian.org: tags 671297 + patch Bug #671297 [libcapi20-dev,isdnutils-base] isdnutils-base and libcapi20-dev: error when trying to install together Added tag(s) patch. tags 671297 + pending Bug #671297 [libcapi20-dev,isdnutils-base] isdnutils-base and libcapi20-dev: error when trying to install together Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 671297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693653: marked as done (OpenGL function fails and blocks Pmv and Autodocktools)
Your message dated Fri, 30 Nov 2012 17:03:58 +
with message-id e1teu0m-0003n5...@franck.debian.org
and subject line Bug#693653: fixed in mgltools-opengltk 1.5.6~rc3~cvs.20120601-2
has caused the Debian Bug report #693653,
regarding OpenGL function fails and blocks Pmv and Autodocktools
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.)
--
693653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: mgltools-opengltk
Version: 1.5.6~rc3~cvs.20120601-1
Severity: serious
Tags: patch
It seems like some platform specific size specifications in
Swig wrappers have caused some issue. The patch below we
have locally tested to solve the issue for us and now we wait
for a confirmation by upstream.
SM+TA
Index: opengltk/extent/dejavu.i
===
RCS file: /opt/cvs/opengltkDIST/opengltk/extent/dejavu.i,v
retrieving revision 1.65
diff -u -r1.65 dejavu.i
--- opengltk/extent/dejavu.i16 Oct 2009 22:49:12 - 1.65
+++ opengltk/extent/dejavu.i18 Nov 2012 23:03:43 -
@@ -3222,7 +3222,7 @@
%typemap(in) const float *coords
{
- long buffer_len;
+ Py_ssize_t buffer_len;
if (PyObject_AsWriteBuffer( $input, (void**)$1, buffer_len))
return NULL;
if (! $1) return PyErr_Format( PyExc_ValueError,
Index: opengltk/extent/glArrayTypemap.i
===
RCS file: /opt/cvs/opengltkDIST/opengltk/extent/glArrayTypemap.i,v
retrieving revision 1.3
diff -u -r1.3 glArrayTypemap.i
--- opengltk/extent/glArrayTypemap.i30 Jul 2007 21:28:55 - 1.3
+++ opengltk/extent/glArrayTypemap.i18 Nov 2012 23:03:43 -
@@ -107,7 +107,7 @@
{
if (isContiguosBuffer((PyObject*)$input))
{
- int buffer_len;
+ Py_ssize_t buffer_len;
array = NULL;
if (PyObject_AsReadBuffer( $input, (const void**)$1, buffer_len))
return NULL;
@@ -124,7 +124,7 @@
}
else
{
-int buffer_len;
+Py_ssize_t buffer_len;
array = NULL;
if (PyObject_AsReadBuffer( $input, (const void**)$1, buffer_len))
return NULL;
@@ -153,7 +153,7 @@
{
if (isContiguosBuffer((PyObject*)$input))
{
- int buffer_len;
+ Py_ssize_t buffer_len;
array = NULL;
if (PyObject_AsReadBuffer( $input, (const void**)$1, buffer_len))
return NULL;
@@ -173,7 +173,7 @@
}
else
{
-int buffer_len;
+Py_ssize_t buffer_len;
array = NULL;
if (PyObject_AsReadBuffer( $input, (const void**)$1, buffer_len))
return NULL;
@@ -202,7 +202,7 @@
{
if (isContiguosBuffer((PyObject*)$input))
{
- int buffer_len;
+ Py_ssize_t buffer_len;
array = NULL;
if (PyObject_AsReadBuffer( $input, (const void**)$1, buffer_len))
return NULL;
@@ -222,7 +222,7 @@
}
else
{
-int buffer_len;
+Py_ssize_t buffer_len;
array = NULL;
if (PyObject_AsReadBuffer( $input, (const void**)$1, buffer_len))
return NULL;
Index: opengltk/extent/gltypemap.i
===
RCS file: /opt/cvs/opengltkDIST/opengltk/extent/gltypemap.i,v
retrieving revision 1.3
diff -u -r1.3 gltypemap.i
--- opengltk/extent/gltypemap.i 11 Jun 2009 22:45:13 - 1.3
+++ opengltk/extent/gltypemap.i 18 Nov 2012 23:03:43 -
@@ -63,7 +63,7 @@
GLvoid*,
GLint[ANY]
{
- long buffer_len;
+ Py_ssize_t buffer_len;
if (PyObject_AsWriteBuffer( $input, (void**)$1, buffer_len))
return NULL;
if (! $1) return PyErr_Format( PyExc_ValueError,
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mgltools-opengltk depends on:
ii libc6 2.13-36
ii libgl1-mesa-glx [libgl1] 8.0.5-1
ii libglu1-mesa 8.0.4-2
ii libx11-6 2:1.5.0-1
ii libxext6 2:1.3.1-2
ii libxmu6 2:1.1.1-1
ii libxt61:1.1.3-1
ii mgltools-gle 1.5.6~rc3+cvs.20121117-1
ii python2.7.3-3
ii python-numpy [python-numpy-abi9] 1:1.6.2-1
ii tk8.5.0-2
ii tk8.4
Bug#677762: package now in testing, not blocking
severity 677762 wishlist thanks The few packages that have still not migrated to M-A are no longer in the Depends line of ia32-libs-gtk and hence not a blocking issue anymore - this bug is hence no longer RC. Leaving open as wishlist because it still documents packages that have not converted. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: package now in testing, not blocking
Processing commands for cont...@bugs.debian.org: severity 677762 wishlist Bug #677762 [ia32-libs-gtk] Multiarch issues Severity set to 'wishlist' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 677762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692937: marked as done (openmpi1.6-doc and mpich2-doc: error when trying to install together)
Your message dated Fri, 30 Nov 2012 18:02:53 + with message-id e1teuvn-0007zz...@franck.debian.org and subject line Bug#692937: fixed in openmpi1.6 1.6.3-3 has caused the Debian Bug report #692937, regarding openmpi1.6-doc and mpich2-doc: error when trying to install together 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.) -- 692937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mpich2-doc,openmpi1.6-doc Version: mpich2-doc/1.4.01-4 Version: openmpi1.6-doc/1.6.3-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-11-11 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! mpich2-doc openmpi1.6-doc Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package mpich2-doc. (Reading database ... 10756 files and directories currently installed.) Unpacking mpich2-doc (from .../mpich2-doc_1.4.1-4_all.deb) ... Selecting previously unselected package openmpi1.6-doc. Unpacking openmpi1.6-doc (from .../openmpi1.6-doc_1.6.3-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/openmpi1.6-doc_1.6.3-2_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/MPI_Testany.3.gz', which is also in package mpich2-doc 1.4.1-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/openmpi1.6-doc_1.6.3-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/man/man3/MPI_Abort.3.gz /usr/share/man/man3/MPI_Accumulate.3.gz /usr/share/man/man3/MPI_Add_error_class.3.gz /usr/share/man/man3/MPI_Add_error_code.3.gz /usr/share/man/man3/MPI_Add_error_string.3.gz /usr/share/man/man3/MPI_Address.3.gz /usr/share/man/man3/MPI_Allgather.3.gz /usr/share/man/man3/MPI_Allgatherv.3.gz /usr/share/man/man3/MPI_Alloc_mem.3.gz /usr/share/man/man3/MPI_Allreduce.3.gz /usr/share/man/man3/MPI_Alltoall.3.gz /usr/share/man/man3/MPI_Alltoallv.3.gz /usr/share/man/man3/MPI_Alltoallw.3.gz /usr/share/man/man3/MPI_Attr_delete.3.gz /usr/share/man/man3/MPI_Attr_get.3.gz /usr/share/man/man3/MPI_Attr_put.3.gz /usr/share/man/man3/MPI_Barrier.3.gz /usr/share/man/man3/MPI_Bcast.3.gz /usr/share/man/man3/MPI_Bsend.3.gz /usr/share/man/man3/MPI_Bsend_init.3.gz /usr/share/man/man3/MPI_Buffer_attach.3.gz /usr/share/man/man3/MPI_Buffer_detach.3.gz /usr/share/man/man3/MPI_Cancel.3.gz /usr/share/man/man3/MPI_Cart_coords.3.gz /usr/share/man/man3/MPI_Cart_create.3.gz /usr/share/man/man3/MPI_Cart_get.3.gz /usr/share/man/man3/MPI_Cart_map.3.gz /usr/share/man/man3/MPI_Cart_rank.3.gz /usr/share/man/man3/MPI_Cart_shift.3.gz /usr/share/man/man3/MPI_Cart_sub.3.gz /usr/share/man/man3/MPI_Cartdim_get.3.gz /usr/share/man/man3/MPI_Close_port.3.gz /usr/share/man/man3/MPI_Comm_call_errhandler.3.gz /usr/share/man/man3/MPI_Comm_compare.3.gz /usr/share/man/man3/MPI_Comm_connect.3.gz /usr/share/man/man3/MPI_Comm_create.3.gz /usr/share/man/man3/MPI_Comm_create_errhandler.3.gz /usr/share/man/man3/MPI_Comm_create_keyval.3.gz /usr/share/man/man3/MPI_Comm_delete_attr.3.gz /usr/share/man/man3/MPI_Comm_disconnect.3.gz /usr/share/man/man3/MPI_Comm_dup.3.gz /usr/share/man/man3/MPI_Comm_free.3.gz /usr/share/man/man3/MPI_Comm_free_keyval.3.gz /usr/share/man/man3/MPI_Comm_get_attr.3.gz /usr/share/man/man3/MPI_Comm_get_errhandler.3.gz /usr/share/man/man3/MPI_Comm_get_name.3.gz
Bug#693147: ttytter: Package breaks against Twitter API 1.1
Hi, That basic functionality is breaking on February 1st. Kinda inappropriate to ship a version of a package that *will* be broken by then. Thanks. I'm aware of it. There are however two complicating factors: 1) Upstream release with support for this API is still in beta. 2) Debian is currently in freeze, which in principle prevents uploading new upstream releases let alone new branches. As it seems, (1) may be resolved soon. Perhaps when that's done, we can confer with the release team to see how to approch this issue best. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693147: ttytter: Package breaks against Twitter API 1.1
On 11/30/2012 01:25 PM, Thijs Kinkhorst wrote: Hi, That basic functionality is breaking on February 1st. Kinda inappropriate to ship a version of a package that *will* be broken by then. Thanks. I'm aware of it. There are however two complicating factors: 1) Upstream release with support for this API is still in beta. 2) Debian is currently in freeze, which in principle prevents uploading new upstream releases let alone new branches. As it seems, (1) may be resolved soon. Perhaps when that's done, we can confer with the release team to see how to approch this issue best. Cheers, Thijs I've pinged Dr. Kaiser and haven't heard back from him. With luck TTYtter comes out of beta soon. The version currently in repo will work just fine with Identica **but** that's still an off-label usage that isn't really fully supported and is supposed to start breaking with the API divergence. Cameron outlined what will stop working once Twitter goes to API 1.1 in February and it remains a significant chunk of functionality. For now, we wait... Stephen Michael Kellat -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694800: auctex: fails to upgrade or install
severity 694800 important thanks TK == Thomas Koch [2012-11-30] TK Package: auctex TK Version: 11.86-12 TK Severity: serious Downgrading to important (reread http://www.debian.org/Bugs/Developer: I fail to see how the serious level applies to this bug; feel free to educate me if you disagree). TK Hi, first I tried to upgrade auctex from 11.86-11 to 11.86-12. This TK failed with dpkg returning 1 from the configure step. I found a file TK /var/lib/auctex/emacs23'/CompilationLog TK containing: TK /usr/sbin/update-auctex-elisp: line 112: emacs23': command not found Looks interesting, thanks. TK Then I purged auctex and tried to install it again, what also failed: TK auctex/install: Byte-compiling for Emacs flavor emacs-snapshot (log to /usr/share/emacs-snapshot/site-lisp/auctex/CompilationLog)... done. TK Install auctex for emacs23 TK auctex/install: Byte-compiling for Emacs flavor emacs23 (log to /usr/share/emacs23/site-lisp/auctex/CompilationLog)... done. TK Install auctex for emacs24 TK auctex/install: Byte-compiling for Emacs flavor emacs24 (log to /usr/share/emacs24/site-lisp/auctex/CompilationLog)... done. TK Processing triggers for auctex ... TK dpkg: error processing auctex (--configure): TK subprocess installed post-installation script returned error exit status 1 This one too. TK Errors were encountered while processing: TK auctex -- Thanks, Davide -- 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#694800: auctex: fails to upgrade or install
Processing commands for cont...@bugs.debian.org: severity 694800 important Bug #694800 [auctex] auctex: fails to upgrade or install Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 694800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Friday 30 November 19:03:22 UTC 2012 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: spock tags 607388 + pending Bug #607388 [wnpp] ITP: spock -- testing and specification framework for Java and Groovy applications Added tag(s) pending. # Source package in NEW: classycle tags 686618 + pending Bug #686618 [wnpp] ITP: classycle -- Analysing tool for Java dependencies Added tag(s) pending. # Source package in NEW: polyglot-maven tags 686795 + pending Bug #686795 [wnpp] ITP: polyglot-maven -- modules to enable Maven usage in others JVM languages Added tag(s) pending. # Source package in NEW: lua-nginx-redis tags 693097 + pending Bug #693097 [wnpp] ITP: lua-nginx-redis -- Lua redis client driver for the ngx_lua based on the cosocket API Added tag(s) pending. # Source package in NEW: lua-nginx-memcached tags 693098 + pending Bug #693098 [wnpp] ITP: lua-nginx-memcached -- Pure Lua memcached client driver for the nginx embedded Lua language Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 666539 + pending Bug #666539 [clang] clang: Fails when trying to include chrono from C++11 Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 674155 + pending Bug #674155 [clang] clang: compiling with -faddress-sanitizer fails Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 685013 + pending Bug #685013 [clang] clang: please upgrade GCC-based dependencies to 4.7 Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 688811 + pending Bug #688811 [clang] clang: Register clang to /usr/bin/c89 /usr/bin/c99 Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 691989 + pending Bug #691989 [clang] clang: ICE when a class with multiple copy constructors is in a union Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 693208 + pending Bug #693208 [clang] clang unable to link trivial test program on armhf Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/clang;clang/a tags 693240 + pending Bug #693240 [clang] clang update needed to support c++ includes in multiarch location Added tag(s) pending. # Source package in NEW: libvistaio tags 694434 + pending Bug #694434 [wnpp] ITP: vistaio -- a library for generic data storage Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/python2.7;python2.7/a tags 683755 + pending Bug #683755 [python2.7] Multiarch support for python2.7 Added tag(s) pending. # Source package in NEW: php-horde-listheaders tags 694753 + pending Bug #694753 [wnpp] ITP: php-horde-listheaders -- Horde List Headers Parsing Library Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 607388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607388 666539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666539 674155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674155 683755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683755 685013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685013 686618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686618 686795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686795 688811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688811 691989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691989 693097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693097 693098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693098 693208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693208 693240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693240 694434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694434 694753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
On Fri, 30 Nov 2012, Guillem Jover wrote: In any case, regardless of this, semantics-wise I don't think it makes much sense to have both of them present. I'll be fixing the deb-triggers(5) man page to clarify this. I'm not sure I follow you here; allowing for both of them means that the triggering package can define whether the triggered feature is crucial, or not essential to its function. Doing it the other way around means that only the triggered package can define whether the feature is crucial or not essential. I was thinking about non-apt frontends, not just using dpkg directly. The main issue here is that the metadata does not guarantee what you want to do, and as such other non-apt frontends are not required to prepare the upgrade transaction in the same way as apt (and I'm not even sure it would be safe to expect that behaviour from apt, even if it's what it's currently doing). I'll test it again with aptitude and see if it also works. If it doesn't, the documentation in deb-triggers should really be updated, as it currently suggests the exact solution I implemented. It'd probably be a good idea to discuss and try to come up with a way to notify dpkg and/or frontends, that they might need to restart themselves because a package requires one of its new features, so that some of those can be deployed w/o having to wait a full release cycle. I've added this to my TODO list for after wheezy. That should actually be pretty easy for the frontends just to handle. If a package pre-depends on dpkg or some other essential package required for the upgrade, it should do those upgrades first, then do the rest of them. dpkg doesn't really need to do anything. If that's really the case, then it basically means that no package in wheezy can use the noawait triggers at all. Yes, that's always been the case for lots of dpkg features, that we have to wait for a new release cycle before being able to use them. And that's been the case for the noawait directives up to now, I've just checked the lintian lab, and this is the only package using them. Ok. However, noawait is the only way to solve this particular bug without doing nasty things in the preinst script because otherwise the trigger gets run before the new version of ca-certificates-java is configured. Don Armstrong -- You could say to the Universe this is not /fair/. And the Universe would say: Oh it isn't? Sorry. -- Terry Pratchett _Soul Music_ p357 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692624: Candidates for removal from testing (2012-11-30)
The patch for both of these bugs is to just replace
src/cson_amalgamation.{c,h}
by empty files in a +dfsg recombobulated upstream tarball.
I'll go ahead and do the machinations. Unless someone else does an NMU
first. A 0-day NMU. Which I totally wouldn't mind. Hint Hint.
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
--
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 694296 + pending Bug #694296 [python-mock-doc] python-mock-doc: missing Breaks+Replaces: python-mock ( 0.7.2) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 694296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
On Fri, 30 Nov 2012, Don Armstrong wrote: On Fri, 30 Nov 2012, Guillem Jover wrote: I was thinking about non-apt frontends, not just using dpkg directly. The main issue here is that the metadata does not guarantee what you want to do, and as such other non-apt frontends are not required to prepare the upgrade transaction in the same way as apt (and I'm not even sure it would be safe to expect that behaviour from apt, even if it's what it's currently doing). I'll test it again with aptitude and see if it also works. If it doesn't, the documentation in deb-triggers should really be updated, as it currently suggests the exact solution I implemented. I just tested it with aptitude, and it works fine. I haven't tested it with dselect or synaptic, but considering that the release notes either specify using apt-get or aptitude, I don't know if it's worth it to test more. If we discover a problem, it would certainly be possible to hack around the problem in the preinst and disable the noawait triggers, but since it fixes a slightly more problematic issue, I'd rather keep it if we possibly can. Don Armstrong -- They say when you embark on a journey of revenge dig two graves. They underestimate me. -- a softer world #560 http://www.asofterworld.com/index.php?id=560 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694296: python-mock-doc: missing Breaks+Replaces: python-mock ( 0.7.2)
Hi all, As this package is part of the Debian Python Modules Team, I've prepared a team upload to resolve this bug. I'll upload to DELAYED/3 just in case there is an objection from one of the listed uploaders. As the svn trunk has unreleased changes, I've put my changes into a branch: svn://svn.debian.org/svn/python-modules/packages/python-mock/branches/rc-bug-694296 Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Developer http://qa.debian.org/developer.php?login=asb PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694670: kscd does not play any CD
Hi Pino, Am Friday 30 November 2012 schrieben Sie: Hi Michael and Rainer, Alle venerdì 30 novembre 2012, Michael Stapelberg ha scritto: However, you can get a better one (and try to debug kscd) just by running kscd as $ kscd --nofork also, installing kdemultimedia-dbg will help providing a more useful stack trace. Thanks for those hints. Here is the new backtrace: [...] Thanks, much better. Looking upstream, I found https://bugs.kde.org/show_bug.cgi?id=265597 which now leads me to the question: do you both have udisks installed? If not, does installing it and rerunning kscd changes the situation? I have udisks installed rd@blackbox:~/tmp.nobackup/Maps$ apt-cache policy udisks udisks: Installiert: 1.0.4-7 Installationskandidat: 1.0.4-7 Versionstabelle: *** 1.0.4-7 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~/tmp.nobackup/Maps$ rd@blackbox:~/tmp.nobackup$ export KDE_DEBUG=1 rd@blackbox:~/tmp.nobackup$ ulimit -c unlimited rd@blackbox:~/tmp.nobackup$ kscd --nofork QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. [0x8f94f10] main services discovery error: no suitable services discovery module Object::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) in ../../phonon/mediacontroller.cpp:64 Object::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) in ../../phonon/mediacontroller.cpp:65 [0x901f680] main stream error: cannot pre fill buffer Segmentation fault (core dumped) rd@blackbox:~/tmp.nobackup$ ls -la core -rw--- 1 rd rd 28762112 Nov 30 22:34 core rd@blackbox:~/tmp.nobackup$ gdb /usr/bin/kscd core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/kscd...Reading symbols from /usr/lib/debug/usr/bin/kscd...done. done. [New LWP 29015] [New LWP 29021] [New LWP 29016] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux- gnu/i686/cmov/libthread_db.so.1. Core was generated by `kscd --nofork'. Program terminated with signal 11, Segmentation fault. #0 0xb5dd024a in malloc_consolidate (av=optimized out) at malloc.c:5161 5161malloc.c: No such file or directory. (gdb) thread apply all bt Thread 3 (Thread 0xb2107b70 (LWP 29016)): #0 0xb77a3424 in __kernel_vsyscall () #1 0xb5e26d96 in *__GI___poll (fds=0xb5ebdff4, fds@entry=0x8ccef30, nfds=nfds@entry=2, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb582213b in g_poll (fds=0x8ccef30, nfds=2, timeout=-1) at /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386- Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gpoll.c:132 #3 0xb58139f0 in g_main_context_poll (n_fds=2, fds=0x8ccef30, timeout=optimized out, context=0x8cd3988, priority=optimized out) at /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386- Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3440 #4 g_main_context_iterate (context=context@entry=0x8cd3988, block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: Unhandled dwarf expression opcode 0xfa) at /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386- Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3141 #5 0xb5813b51 in g_main_context_iteration (context=0x8cd3988, may_block=1) at /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386- Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3207 #6 0xb61a385f in QEventDispatcherGlib::processEvents (this=0x89ba9e8, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0xb617002c in QEventLoop::processEvents (this=this@entry=0xb2107288, flags=...) at kernel/qeventloop.cpp:149 #8 0xb6170321 in QEventLoop::exec (this=0xb2107288, flags=...) at kernel/qeventloop.cpp:204 #9 0xb605cb3c in QThread::exec (this=0x8cd4648) at thread/qthread.cpp:501 #10 0xb614e77d in QInotifyFileSystemWatcherEngine::run (this=0x8cd4648) at io/qfilesystemwatcher_inotify.cpp:248 #11 0xb605ff00 in QThreadPrivate::start (arg=0x8cd4648) at thread/qthread_unix.cpp:307 #12 0xb5d4bc39 in start_thread (arg=0xb2107b70) at pthread_create.c:304 #13 0xb5e3478e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb0fa6b70 (LWP 29021)): #0 0xb77a3424 in __kernel_vsyscall () #1 0xb5d5020a in __pthread_cond_wait (cond=0x8de8974, mutex=0x8de895c) at pthread_cond_wait.c:153 #2 0xb5e4187d in __pthread_cond_wait
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
On Fri, 2012-11-30 at 11:24:48 -0800, Don Armstrong wrote: On Fri, 30 Nov 2012, Guillem Jover wrote: In any case, regardless of this, semantics-wise I don't think it makes much sense to have both of them present. I'll be fixing the deb-triggers(5) man page to clarify this. I'm not sure I follow you here; allowing for both of them means that the triggering package can define whether the triggered feature is crucial, or not essential to its function. Doing it the other way around means that only the triggered package can define whether the feature is crucial or not essential. This is already supported, and now having rechecked the patch in more detail and having paid attention :), you are already making use of it by calling dpkg-trigger with --no-await, which activates a trigger w/o marking the activating package as needing to await processing. You have to think about the interest* directives as default behaviour, so if the directive is synchronous, you can still activate it asynchronously (with dpkg-trigger --noawait). If the interested package marks it as noawait then it means it's really never needed for triggering packages to await processing; an example of this latter case could be man page cache regeneration. Those default directives are also needed so that implicit triggering, like the ones activated via path changes by dpkg itself during unpack/remove/etc, can behave in a way or another, but there needs to be only one, two directives does not make sense, which one would apply then? So, it really looks like these packages were behaving like if they only had «interest foo» (due to the stomping I mentioned before) and the trigger was asynchronous anyway due to the dpkg-trigger call, so you don't really need to use interest-noawait support nor the dpkg Pre-Depends anyway, and the possible upgrade issues just disappear. It'd probably be a good idea to discuss and try to come up with a way to notify dpkg and/or frontends, that they might need to restart themselves because a package requires one of its new features, so that some of those can be deployed w/o having to wait a full release cycle. I've added this to my TODO list for after wheezy. That should actually be pretty easy for the frontends just to handle. If a package pre-depends on dpkg or some other essential package required for the upgrade, it should do those upgrades first, then do the rest of them. dpkg doesn't really need to do anything. That's one of the solutions that had crossed my mind too, but it might be too restritive in how frontends might need to prepare transactions, so it might be too heavy handed. The only problem here is just dpkg (perhaps the frontends itself too, but nothing else really), as the running process that gets out of sync with its own database, but asking frontends to hardcode a special case for the dpkg package might not be liked, and instead a metadata-based solution might be preferred, that's why I mentioned that this would need discussion. :) Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671297: marked as done (isdnutils-base and libcapi20-dev: error when trying to install together)
Your message dated Fri, 30 Nov 2012 22:32:44 + with message-id e1tez8w-0002g2...@franck.debian.org and subject line Bug#671297: fixed in isdnutils 1:3.25+dfsg1-3wheezy1 has caused the Debian Bug report #671297, regarding isdnutils-base and libcapi20-dev: error when trying to install together 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.) -- 671297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libcapi20-dev,isdnutils-base Version: libcapi20-dev/1:3.22+dfsg1-3 Version: isdnutils-base/1:3.22+dfsg1-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-05-03 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! isdnutils-base libcapi20-3 libcapi20-dev Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package isdnutils-base. (Reading database ... 10558 files and directories currently installed.) Unpacking isdnutils-base (from .../isdnutils-base_1%3a3.22+dfsg1-3_amd64.deb) ... Selecting previously unselected package libcapi20-3. Unpacking libcapi20-3 (from .../libcapi20-3_1%3a3.22+dfsg1-3_amd64.deb) ... Selecting previously unselected package libcapi20-dev. Unpacking libcapi20-dev (from .../libcapi20-dev_1%3a3.22+dfsg1-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libcapi20-dev_1%3a3.22+dfsg1-3_amd64.deb (--unpack): trying to overwrite '/usr/include/isdn_dwabclib.h', which is also in package isdnutils-base 1:3.22+dfsg1-3 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libcapi20-dev_1%3a3.22+dfsg1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) cow-shell unlink .ilist: No such file or directory This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/include/isdn_dwabclib.h -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: isdnutils Source-Version: 1:3.25+dfsg1-3wheezy1 We believe that the bug you reported is fixed in the latest version of isdnutils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rolf Leggewie f...@rolf.leggewie.biz (supplier of updated isdnutils 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, 26 Nov 2012 03:05:00 +0100 Source: isdnutils Binary: isdnutils-base isdnutils-xtools ipppd isdnlog isdnlog-data isdnutils-doc isdnvbox isdnvboxclient isdnvboxserver capiutils libcapi20-3 libcapi20-dev pppdcapiplugin Architecture: source i386 all Version: 1:3.25+dfsg1-3wheezy1 Distribution: unstable Urgency: low Maintainer: Rolf Leggewie f...@rolf.leggewie.biz Changed-By: Rolf Leggewie f...@rolf.leggewie.biz Description: capiutils - ISDN utilities - tools for CAPI-capable cards ipppd - ISDN utilities - PPP daemon isdnlog- ISDN utilities - connection logger isdnlog-data - ISDN utilities - connection logger data isdnutils-base - ISDN utilities - minimal set
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
On Fri, 30 Nov 2012, Guillem Jover wrote: This is already supported, and now having rechecked the patch in more detail and having paid attention :), you are already making use of it by calling dpkg-trigger with --no-await, which activates a trigger w/o marking the activating package as needing to await processing. Oh, ok. You have to think about the interest* directives as default behaviour, so if the directive is synchronous, you can still activate it asynchronously (with dpkg-trigger --noawait). Ah, awesome. Ok, this wasn't clear at all to me from reading the documentation. Let me try to rephrase to see if I've understood you correctly: interest triggername just means that by default a dpkg-trigger will be considered to be a synchronous trigger; if dpkg-trigger is called with --noawait, then it does it asynchronously. And interest-noawait triggername mean that the trigger will always be asynchronous no matter how dpkg-trigger is called or the activate trigger is listed. Assuming I understand this properly now, I think I'll whip up a patch to the git repository which explains this in more detail in the manpage. So, it really looks like these packages were behaving like if they only had «interest foo» (due to the stomping I mentioned before) and the trigger was asynchronous anyway due to the dpkg-trigger call, so you don't really need to use interest-noawait support nor the dpkg Pre-Depends anyway, and the possible upgrade issues just disappear. Ok. Do we still need a dependency for dpkg-trigger --no-await to work? That's one of the solutions that had crossed my mind too, but it might be too restritive in how frontends might need to prepare transactions, so it might be too heavy handed. The only problem here is just dpkg (perhaps the frontends itself too, but nothing else really), as the running process that gets out of sync with its own database, but asking frontends to hardcode a special case for the dpkg package might not be liked, and instead a metadata-based solution might be preferred, that's why I mentioned that this would need discussion. :) Yeah. Another crazy option would be for dpkg to recognize that it was upgrading itself, and rexec itself after upgrading itself if it has more thins to do. But that's probably even more kinds of crazy. Don Armstrong -- in Just- spring when the world is mud- luscious the little lame baloonman whistles far and wee -- e.e. cummings [in Just-] http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 694446 in 0.18, found 694446 in 0.3+squeeze1
Processing commands for cont...@bugs.debian.org:
found 694446 0.18
Bug #694446 {Done: Osamu Aoki os...@debian.org} [im-config] im-config should
setting environment variable in 70im-config_launch instead of im-launch
Marked as found in versions im-config/0.18.
found 694446 0.3+squeeze1
Bug #694446 {Done: Osamu Aoki os...@debian.org} [im-config] im-config should
setting environment variable in 70im-config_launch instead of im-launch
Marked as found in versions im-config/0.3+squeeze1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
On Fri, 2012-11-30 at 14:44:03 -0800, Don Armstrong wrote: On Fri, 30 Nov 2012, Guillem Jover wrote: You have to think about the interest* directives as default behaviour, so if the directive is synchronous, you can still activate it asynchronously (with dpkg-trigger --noawait). Ah, awesome. Ok, this wasn't clear at all to me from reading the documentation. Let me try to rephrase to see if I've understood you correctly: interest triggername just means that by default a dpkg-trigger will be considered to be a synchronous trigger; if dpkg-trigger is called with --noawait, then it does it asynchronously. And interest-noawait triggername mean that the trigger will always be asynchronous no matter how dpkg-trigger is called or the activate trigger is listed. Correct. Assuming I understand this properly now, I think I'll whip up a patch to the git repository which explains this in more detail in the manpage. Cool, that'd be wonderful, I'll happily queue it for 1.17.x. If you are going to mention dpkg-trigger (an explicit trigger) it would be nice to also mention implicit triggers too. And it probably also makes sense to avoid using the “(a)synchronous” language when talking about triggers as that is not used in any other place when talking about them. So, it really looks like these packages were behaving like if they only had «interest foo» (due to the stomping I mentioned before) and the trigger was asynchronous anyway due to the dpkg-trigger call, so you don't really need to use interest-noawait support nor the dpkg Pre-Depends anyway, and the possible upgrade issues just disappear. Ok. Do we still need a dependency for dpkg-trigger --no-await to work? Nope, «dpkg-trigger --no-await» is supported since dpkg 1.14.17, the version that introduced triggers. That's one of the solutions that had crossed my mind too, but it might be too restritive in how frontends might need to prepare transactions, so it might be too heavy handed. The only problem here is just dpkg (perhaps the frontends itself too, but nothing else really), as the running process that gets out of sync with its own database, but asking frontends to hardcode a special case for the dpkg package might not be liked, and instead a metadata-based solution might be preferred, that's why I mentioned that this would need discussion. :) Yeah. Another crazy option would be for dpkg to recognize that it was upgrading itself, and rexec itself after upgrading itself if it has more thins to do. But that's probably even more kinds of crazy. Yes, this also crossed my mind :). In principle it should not require that much code jugling, but I'd have to review the code paths to make sure how much state might need to be preserved (like status-fds) or flushed to disk if it's still not there, etc. It still might be too heavy handed, because a package Pre-Depending on dpkg might need features provided by one of the other tools (like dpkg-query), which would not require the dpkg process to restart, and we might still want to have control over when this happens. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686845: marked as done (upgrade fails when using sympa with sqlite3)
Your message dated Sat, 01 Dec 2012 00:02:50 + with message-id e1teaxi-0005ch...@franck.debian.org and subject line Bug#686845: fixed in sympa 6.1.11~dfsg-5 has caused the Debian Bug report #686845, regarding upgrade fails when using sympa with sqlite3 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.) -- 686845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sympa Version: 6.1.11~dfsg-4 Severity: grave When upgrading from squeeze, the postinst fails because exclusion_table does not exist. err Upgrade::probe_db() Table 'exclusion_table' not found in database '/var/lib/dbconfig-common/sqlite3/sympa/sympa' ; you should create it with create_db.SQLite script After creating that table with create_db.SQLite, it STILL fails, due to info Upgrade::probe_db() Field 'robot_exclusion' (table 'exclusion_table' ; database '/var/lib/dbconfig-common/sqlite3/sympa/sympa') was NOT found. Attempting to add it... DBD::SQLite::db do failed: Cannot add a NOT NULL column with default value NULL at /usr/share/sympa/lib/Upgrade.pm line 1271. err Upgrade::probe_db() Could not add field 'robot_exclusion' to table'exclusion_table'. This renders sympa unusable after upgrading to wheezy. ---End Message--- ---BeginMessage--- Source: sympa Source-Version: 6.1.11~dfsg-5 We believe that the bug you reported is fixed in the latest version of sympa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 686...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot kol...@debian.org (supplier of updated sympa 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: SHA512 Format: 1.8 Date: Fri, 30 Nov 2012 19:00:43 + Source: sympa Binary: sympa Architecture: source amd64 Version: 6.1.11~dfsg-5 Distribution: unstable Urgency: low Maintainer: Debian Sympa team pkg-sympa-de...@lists.alioth.debian.org Changed-By: Emmanuel Bouthenot kol...@debian.org Description: sympa - Modern mailing list manager Closes: 686845 Changes: sympa (6.1.11~dfsg-5) unstable; urgency=low . * Fix SQLite patch to avoid crash during installation from scratch and database schema updates failures on upgrade (Closes: #686845) Checksums-Sha1: 52e2b571bbd9aeb01db714a53c9eedca603a3f14 2542 sympa_6.1.11~dfsg-5.dsc 1a1fdd26554ef1bf7d763a4ac1148e5ad53ea22b 121142 sympa_6.1.11~dfsg-5.debian.tar.gz e1921cb71b87eb0b103e33251a0ae6b9d6534e18 3154460 sympa_6.1.11~dfsg-5_amd64.deb Checksums-Sha256: 1678d0ed359de1f6fd9a7f6fea92d89d7e455377a070c44e5042763ff9925885 2542 sympa_6.1.11~dfsg-5.dsc fbeb68b54371abbe3344385c6c67d3fdc0d592c882b0ad219526bc5680fd665e 121142 sympa_6.1.11~dfsg-5.debian.tar.gz 9724ecae215f7408bd7c35c99383fdf6fdc3812301c40c1490229ae92c927bfe 3154460 sympa_6.1.11~dfsg-5_amd64.deb Files: ea5d8b72db880bee964f3ce8a15e0abd 2542 mail optional sympa_6.1.11~dfsg-5.dsc 4040da440247c3649dddcc545c5a0675 121142 mail optional sympa_6.1.11~dfsg-5.debian.tar.gz 8524850356216f52a154f5f1a503c2f2 3154460 mail optional sympa_6.1.11~dfsg-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQuUX+AAoJEEsHdyOSnULDe5sP/1JCWYA3zGBc41H7GJhCxDWe 6Yot+2bvqi/b+HDhgwhbKdQ09LuigC336qiZOH13sTscoMgAc9JZv0qPvsyYfW3I N9d1fn9CRj7UYd31G+Mxz0LHxoInIh203MF11YNMcVYaFsBxHLbCxaMvWsUF9kEU PXvAsOid7YgUjfWSk+RpTypaXaH8N2d6iwJuoD3hJDAGaPzv04Wu6UAUSvrKFbBo TH7brd/a2W89giXkM+GDHdOkrX0l5U+dAmxzSJL+AB0KYeqfe1bVxcGEibIQbpmC 04Ct1DdMM0bWpvTCn+phC+gcHJFVD8krAcM+mX7JZhijPWAmNUFD7//c3Bb9anat 2qnBjs0GtlBUMFY8xe8wchMCSu2wHih0M2ktA4MIcyTxcwKEQJpM1LlRyW74euFC 38yQQZVtyra4l2N6ep06V8TQeyy57Sxi2P6bghhnkVB1yqyWI1w1bbeusYB3JMuO VIf7+doaOVp9+6J9GBisrJWnBG9SaY347X3x9M46FOqxTv6Kqhw6V+eFJln3ACVy yo2Y98vWjZoERUPx/1im6OM3gkmhlep8ow5c8yQaKqx4uAfNUUXrqeespEDhAn8n mUxYFcDy36F61TFFN29dqlaSeb/9D2XPPgRXd7snNoULfQYGFPzcU0kEVvQbXkHM Ls6FByyz3cRMnRAnGtw5 =U0T0 -END PGP SIGNATUREEnd Message---
Bug#686846: marked as done (sympa: upgrade script continues to provide fodder for kafka novel)
Your message dated Sat, 01 Dec 2012 00:02:50 + with message-id e1teaxi-0005ch...@franck.debian.org and subject line Bug#686845: fixed in sympa 6.1.11~dfsg-5 has caused the Debian Bug report #686845, regarding sympa: upgrade script continues to provide fodder for kafka novel 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.) -- 686845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sympa Version: 6.1.11~dfsg-4 Severity: grave When upgrading from squeeze with SQLite3, after fudging the exclusion_table by hand, this happens: err Upgrade::probe_db() Table 'list_table' not found in database '/var/lib/dbconfig-common/sqlite3/sympa/sympa' ; you should create it with create_db.SQLite script There is no list_table in any of the create_db scripts. ---End Message--- ---BeginMessage--- Source: sympa Source-Version: 6.1.11~dfsg-5 We believe that the bug you reported is fixed in the latest version of sympa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 686...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot kol...@debian.org (supplier of updated sympa 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: SHA512 Format: 1.8 Date: Fri, 30 Nov 2012 19:00:43 + Source: sympa Binary: sympa Architecture: source amd64 Version: 6.1.11~dfsg-5 Distribution: unstable Urgency: low Maintainer: Debian Sympa team pkg-sympa-de...@lists.alioth.debian.org Changed-By: Emmanuel Bouthenot kol...@debian.org Description: sympa - Modern mailing list manager Closes: 686845 Changes: sympa (6.1.11~dfsg-5) unstable; urgency=low . * Fix SQLite patch to avoid crash during installation from scratch and database schema updates failures on upgrade (Closes: #686845) Checksums-Sha1: 52e2b571bbd9aeb01db714a53c9eedca603a3f14 2542 sympa_6.1.11~dfsg-5.dsc 1a1fdd26554ef1bf7d763a4ac1148e5ad53ea22b 121142 sympa_6.1.11~dfsg-5.debian.tar.gz e1921cb71b87eb0b103e33251a0ae6b9d6534e18 3154460 sympa_6.1.11~dfsg-5_amd64.deb Checksums-Sha256: 1678d0ed359de1f6fd9a7f6fea92d89d7e455377a070c44e5042763ff9925885 2542 sympa_6.1.11~dfsg-5.dsc fbeb68b54371abbe3344385c6c67d3fdc0d592c882b0ad219526bc5680fd665e 121142 sympa_6.1.11~dfsg-5.debian.tar.gz 9724ecae215f7408bd7c35c99383fdf6fdc3812301c40c1490229ae92c927bfe 3154460 sympa_6.1.11~dfsg-5_amd64.deb Files: ea5d8b72db880bee964f3ce8a15e0abd 2542 mail optional sympa_6.1.11~dfsg-5.dsc 4040da440247c3649dddcc545c5a0675 121142 mail optional sympa_6.1.11~dfsg-5.debian.tar.gz 8524850356216f52a154f5f1a503c2f2 3154460 mail optional sympa_6.1.11~dfsg-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQuUX+AAoJEEsHdyOSnULDe5sP/1JCWYA3zGBc41H7GJhCxDWe 6Yot+2bvqi/b+HDhgwhbKdQ09LuigC336qiZOH13sTscoMgAc9JZv0qPvsyYfW3I N9d1fn9CRj7UYd31G+Mxz0LHxoInIh203MF11YNMcVYaFsBxHLbCxaMvWsUF9kEU PXvAsOid7YgUjfWSk+RpTypaXaH8N2d6iwJuoD3hJDAGaPzv04Wu6UAUSvrKFbBo TH7brd/a2W89giXkM+GDHdOkrX0l5U+dAmxzSJL+AB0KYeqfe1bVxcGEibIQbpmC 04Ct1DdMM0bWpvTCn+phC+gcHJFVD8krAcM+mX7JZhijPWAmNUFD7//c3Bb9anat 2qnBjs0GtlBUMFY8xe8wchMCSu2wHih0M2ktA4MIcyTxcwKEQJpM1LlRyW74euFC 38yQQZVtyra4l2N6ep06V8TQeyy57Sxi2P6bghhnkVB1yqyWI1w1bbeusYB3JMuO VIf7+doaOVp9+6J9GBisrJWnBG9SaY347X3x9M46FOqxTv6Kqhw6V+eFJln3ACVy yo2Y98vWjZoERUPx/1im6OM3gkmhlep8ow5c8yQaKqx4uAfNUUXrqeespEDhAn8n mUxYFcDy36F61TFFN29dqlaSeb/9D2XPPgRXd7snNoULfQYGFPzcU0kEVvQbXkHM Ls6FByyz3cRMnRAnGtw5 =U0T0 -END PGP SIGNATUREEnd Message---
Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories
Rob Browning r...@defaultvalue.org writes: (let* ((paths (mapcar copy-sequence dirs)) ; Ensure we have unique objects. In debian-run-directories? I suspect its rest makes dirs a fresh list anyway. Incidentally, one thing I never understood was why load-path has entries for both /usr/share/emacs24/site-lisp/emacs-goodies-el and /usr/share/emacs/24.2/site-lisp/emacs-goodies-el I see /usr/share/emacs/24.2/site-lisp is a symlink to /usr/share/emacs24/site-lisp, so I imagine the second doesn't add anything ... if that's true for all flavours etc etc. -- The sigfile covers series: I drank a slab and the slab won. (to the tune of I Fought the Law) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694841: harden-doc: Differing encodings cause LaTeX errors.
Package: harden-doc Version: 3.15.1 Severity: serious Tags: patch Justification: fails to build from source Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** LaTeX complained about misconstructed UTF-8 entities in the french translation. This was due to a mixture of Latin-1 and UTF-8-encoding. Apparently, most files are encoded in Latin-1, but fr.po is (in its translation part) UTF-8. po4a then mixed Latin-1 with UTF-8 into one file, so no matter how further processing went, something would go wrong. I have changed po4a.cfg to define local files as latin-1, too. The generated file is now entirely Latin-1 and not mixed. Further down the road, the debiandoc2latex-stuff scripts need to know that the files are Latin-1, not UTF. I have changed the mapping in the Makefile for that. Since changes in the po4a configuration file invalidate all derived documents, I added it to the prerequisites. Migration to UTF-8 would be a more perfect solution from my point of view, but I would take that on only after migration to DocBook. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- no debconf information From 3c3c1c268ecd11055718dc7dbb890598c91066c9 Mon Sep 17 00:00:00 2001 From: Felix Gatzemeier m...@gmx.net Date: Sat, 1 Dec 2012 02:54:14 +0100 Subject: [PATCH] Resolved Encoding to be Latin-1 all the way through --- Makefile |8 po4a/po4a.cfg |2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Makefile b/Makefile index 356bd9f..f04e40e 100644 --- a/Makefile +++ b/Makefile @@ -69,7 +69,7 @@ SGMLPOSRCS := $(foreach lang, $(LANGSPO), $(MANUAL).$(lang).sgml) $(MANUAL).%.html.stamp $(MANUAL).%.txt $(MANUAL).%.ps $(MANUAL).%.pdf: \ locale=$(subst pt-br,pt_BR,\ $(subst zh-cn,zh_CN,\ - $(subst fr,fr.UTF-8,\ + $(subst fr,fr_FR.ISO8859-1,\ $*))) ### Full guide @@ -127,9 +127,9 @@ $(SGMLNOPOSRCS): $(MANUAL).%.sgml: $(MANUAL0).sgml $ $(MANUAL).$*.sgml # Create starting SGML for each language handled with po4a - -$(SGMLPOSRCS): $(MANUAL).%.sgml: $(MANUAL).en.sgml $(MANUAL).en.ent po4a/po/%.po - po4a po4a/po4a.cfg +POACONFIG := po4a/po4a.cfg +$(SGMLPOSRCS): $(MANUAL).%.sgml: $(MANUAL).en.sgml $(MANUAL).en.ent po4a/po/%.po $(POACONFIG) + po4a $(POACONFIG) # HTML $(MANUAL).%.html.stamp: $(MANUAL).%.sgml $(MANUAL).%.ent $(SGMLSRCS) diff --git a/po4a/po4a.cfg b/po4a/po4a.cfg index 88dd444..e01b677 100644 --- a/po4a/po4a.cfg +++ b/po4a/po4a.cfg @@ -3,5 +3,5 @@ [type: sgml] securing-debian-howto.en.sgml \ $lang:securing-debian-howto.$lang.sgml \ add_$lang:?po4a/$lang.add \ - opt:-M ISO-8859-1 + opt:-M ISO-8859-1 -L ISO-8859-1 -- 1.7.10.4
Processed: limit source to vdkxdb2, tagging 693982
Processing commands for cont...@bugs.debian.org: #vdkxdb2 (2.4.0-3.4) unstable; urgency=low # # * libvdkxdb2-dev replaces and breaks libvdkxdb2-2c2 ( 2.4.0-3.2) to allow #smooth upgrades (files moved from libvdkxdb2-2c2 to libvdkxdb2-dev in the #intrusive 2.4.0-3.2 NMU). Closes: #693982 # limit source vdkxdb2 Limiting to bugs with field 'source' containing at least one of 'vdkxdb2' Limit currently set to 'source':'vdkxdb2' tags 693982 + pending Bug #693982 [libvdkxdb2-dev] libvdkxdb2-dev: fails to upgrade lenny - squeeze - wheezy - trying to overwrite /usr/lib/libvdkxdb2.a Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 693982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693982: vdkxdb2: diff for NMU version 2.4.0-3.4
tags 693982 + patch
thanks
Dear maintainer,
I've prepared an NMU for vdkxdb2 (versioned as 2.4.0-3.4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
David
diff -Nru vdkxdb2-2.4.0/debian/changelog vdkxdb2-2.4.0/debian/changelog
--- vdkxdb2-2.4.0/debian/changelog 2011-09-14 19:57:46.0 -0400
+++ vdkxdb2-2.4.0/debian/changelog 2012-11-30 23:06:09.0 -0400
@@ -1,3 +1,12 @@
+vdkxdb2 (2.4.0-3.4) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * libvdkxdb2-dev replaces and breaks libvdkxdb2-2c2 ( 2.4.0-3.2) to allow
+smooth upgrades (files moved from libvdkxdb2-2c2 to libvdkxdb2-dev in the
+intrusive 2.4.0-3.2 NMU). Closes: #693982
+
+ -- David Prévot taf...@debian.org Fri, 30 Nov 2012 23:05:34 -0400
+
vdkxdb2 (2.4.0-3.3) unstable; urgency=low
* Non-maintainer upload.
diff -Nru vdkxdb2-2.4.0/debian/control vdkxdb2-2.4.0/debian/control
--- vdkxdb2-2.4.0/debian/control 2011-09-14 19:56:16.0 -0400
+++ vdkxdb2-2.4.0/debian/control 2012-11-30 22:56:36.0 -0400
@@ -23,6 +23,8 @@
Package: libvdkxdb2-dev
Section: libdevel
Architecture: any
+Replaces: libvdkxdb2-2c2 ( 2.4.0-3.2)
+Breaks: libvdkxdb2-2c2 ( 2.4.0-3.2)
Depends: ${misc:Depends}, libvdkxdb2-2c2 (= ${binary:Version}), libxbase2.0-dev, libc6-dev
Description: development files for libvdkxdb
VDKXdb is a set of data-aware widgets made to build
signature.asc
Description: Digital signature
Processed: vdkxdb2: diff for NMU version 2.4.0-3.4
Processing commands for cont...@bugs.debian.org: tags 693982 + patch Bug #693982 [libvdkxdb2-dev] libvdkxdb2-dev: fails to upgrade lenny - squeeze - wheezy - trying to overwrite /usr/lib/libvdkxdb2.a Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 693982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692732: marked as done (src:ntop: non-free files in main (CC-BY-NC))
Your message dated Sat, 01 Dec 2012 06:17:33 + with message-id e1tegol-0003sz...@franck.debian.org and subject line Bug#692732: fixed in ntop 3:4.99.3+ndpi5517+dfsg2-1 has caused the Debian Bug report #692732, regarding src:ntop: non-free files in main (CC-BY-NC) 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.) -- 692732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:ntop Version: 3:4.99.3+ndpi5517+dfsg1-1 Severity: serious Files: countmin.h Copyright: 2003-2004, G. Cormode License: CC-BY-NC That is obviously a non-free, GPL-incompatible license. Ansgar ---End Message--- ---BeginMessage--- Source: ntop Source-Version: 3:4.99.3+ndpi5517+dfsg2-1 We believe that the bug you reported is fixed in the latest version of ntop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovico Cavedon cave...@debian.org (supplier of updated ntop 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: SHA512 Format: 1.8 Date: Fri, 30 Nov 2012 00:07:10 -0800 Source: ntop Binary: ntop ntop-dbg ntop-data Architecture: source amd64 all Version: 3:4.99.3+ndpi5517+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Ludovico Cavedon cave...@debian.org Changed-By: Ludovico Cavedon cave...@debian.org Description: ntop - display network usage in web browser ntop-data - display network usage in a web browser (data files) ntop-dbg - display network usage in web browser (debug symbols) Closes: 692732 Changes: ntop (3:4.99.3+ndpi5517+dfsg2-1) unstable; urgency=medium . * Repackage upstream source replacing non-DFSG countmin code with the GPL one (Closes: #692732). * Update Maintainer and Uploaders. Checksums-Sha1: 79bb9cc04859ba919163f7de551a6fb261b17c86 2182 ntop_4.99.3+ndpi5517+dfsg2-1.dsc dcdefb1e28e114b09bc702e01dc319557062e2b2 3675927 ntop_4.99.3+ndpi5517+dfsg2.orig.tar.gz 8a890b5156c96b61c8470486aee307d9ee60a2bf 60154 ntop_4.99.3+ndpi5517+dfsg2-1.debian.tar.gz 619daabda507fc8627b8b70c6c85605eafd5dc64 745662 ntop_4.99.3+ndpi5517+dfsg2-1_amd64.deb 02d569147216d17290f1c55d472ad147fb9c7b5f 1700444 ntop-dbg_4.99.3+ndpi5517+dfsg2-1_amd64.deb 37a3c9b9e517cd58aa223240d16283f71605a524 1625844 ntop-data_4.99.3+ndpi5517+dfsg2-1_all.deb Checksums-Sha256: 9cf619706c89e13092bc8f5baf3b6793d25ef03b3a834f787a84050d8dcbf605 2182 ntop_4.99.3+ndpi5517+dfsg2-1.dsc 178f53d34a581e950af08c0c03b60140c6a40ea136ed755c57978e77b1faec3c 3675927 ntop_4.99.3+ndpi5517+dfsg2.orig.tar.gz 89ea12894491272b2d373e8566284ed481b4f80c68dcbdc8a5c2ae5b0230d0e5 60154 ntop_4.99.3+ndpi5517+dfsg2-1.debian.tar.gz 46fb182b8465ec60279eb637aa8710119b73f5566fd39f5e4310974d74814c58 745662 ntop_4.99.3+ndpi5517+dfsg2-1_amd64.deb 1b0fd37366a86c73b4eabbc4ae64b657894ce34ba2c04e1bb8be831820ea4367 1700444 ntop-dbg_4.99.3+ndpi5517+dfsg2-1_amd64.deb a70715d922ffa1988722297b7064105ee6e330b74fd2fc8bbf914970c4cab83b 1625844 ntop-data_4.99.3+ndpi5517+dfsg2-1_all.deb Files: dfae1bc16b1b061ddb46524de710d9b2 2182 net optional ntop_4.99.3+ndpi5517+dfsg2-1.dsc b2df85540d616a0019fb338cca6f5fc1 3675927 net optional ntop_4.99.3+ndpi5517+dfsg2.orig.tar.gz 45f2d8b4d84d07d2cd38b171400fd1c0 60154 net optional ntop_4.99.3+ndpi5517+dfsg2-1.debian.tar.gz d13ca0a3316fde88e4231fa12e863b8c 745662 net optional ntop_4.99.3+ndpi5517+dfsg2-1_amd64.deb 7580fa48a72e016e545d7d6da2ec17cb 1700444 debug extra ntop-dbg_4.99.3+ndpi5517+dfsg2-1_amd64.deb bb2df838ab1cdefd45c75c2a51d6249b 1625844 net optional ntop-data_4.99.3+ndpi5517+dfsg2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQuZtgAAoJEBPAtWZ6OLCwxcwP/1wUB5imWlYQurtPaqGBFsX6 KhONkbISegqv8D62kSqvQcofJTYJBbsqahXQd1ir96yHxf/hs0wWzMGIrFK7UIht H/ukAQVeN9SwMOlgRCiI6FJ48YD/rqfII31CTZ82FkVtqjST+vlFFp0aAdTnUt3a hGmX/Y0pOnhpFWQgUFliccTSmwWSfHtK5g2pRI/YQBn96Y1G7k076tegP0/baudJ nBA9H33RQprT1TlswsnH5o0yvcIpc5s22cpX5WloxRn0XbG21tWDIoKojGdOzduK /uWdcPY9aQmiVHvtdZm9aiN6OJ4Zo0rYnpX9SLEmsWKQ0l6rEJXA727vRvwgHVpn KrjmxdzOoBwIx/HDrzeS6FFm4iJy5kwjYHg2i383ERkahR0V3AXYbEwso/EtbhWo
