Bug#749461: nmu: dolfin_1.3.0+dfsg-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Hi, python-dolfin is currently not installable in sid since it depends
on swig2.0 ( 2.0.12~), and we have swig2.0 version 2.0.12-1 in sid.
This dependency seems to be generated by this fragment of debian/control:
Package: python-dolfin
Depends: ${swig:Depends},
nmu dolfin_1.3.0+dfsg-2 . ALL . -m rebuild against swig2.0 2.0.12-1
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744717: Confirmed that the patch deb is working for iOS 7.1.1
FYI for anyone else who might be reading this, Openswan is no longer being maintained: https://www.debian.org/security/2014/dsa-2893 Since the Openswan package is not maintained anymore in the Debian distribution and is not available in testing and unstable suites, **it is recommended for IKE/IPsec users to switch to a supported implementation like strongSwan**. This is great advice. The transition to strongSwan was relatively seamless, and strongSwan works perfectly with OS X and iOS clients. Josh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512804: synaptic: still a bug in 0.81.2
Package: synaptic Version: 0.81.2 Followup-For: Bug #512804 This is still a bug in the current version of synaptic (0.81.2) in unstable. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages synaptic depends on: ii hicolor-icon-theme 0.13-1 ii libapt-inst1.5 1.0.3 ii libapt-pkg4.12 1.0.3 ii libatk1.0-0 2.12.0-1 ii libc62.18-7 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libept1.4.12 1.0.12 ii libgcc1 1:4.9.0-4 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk-3-0 3.12.2-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libstdc++6 4.9.0-4 ii libvte-2.90-91:0.36.2-1 ii libx11-6 2:1.6.2-2 ii libxapian22 1.2.17-1 ii libxext6 2:1.3.2-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages synaptic recommends: ii gksu 2.0.2-6 ii libgtk2-perl 2:1.2491-2 ii policykit-10.105-6 ii rarian-compat 0.8.1-5 Versions of packages synaptic suggests: ii apt-xapian-index 0.46 ii deborphan1.7.28.8 pn dwww none ii menu 2.1.46 ii software-properties-gtk 0.92.25debian1 ii tasksel 3.20 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749462: pcp-gui-testsuite: not installable in sid
Package: pcp-gui-testsuite Version: 1.5.13 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, pcp-gui-testsuite is no longer installable in sid as it depends on pcp-gui (= 1.5.13). Since pcp-gui moved into the pcp source package we have pcp-gui version 3.9.4 in sid. Shouldn't the pcp-gui-testsuite package be removed from sid (or rather the whole pcp-gui source package)? -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749463: scorched3d: Please update to use wxwidgets3.0
Package: scorched3d
Version: 43.3.d+dfsg-1
Severity: normal
Tags: patch
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8.
I've rebuilt your package using the attached patch, and done some simple
testing, and everything looks good to me.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru scorched3d-43.3.d+dfsg/debian/changelog scorched3d-43.3.d+dfsg/debian/changelog
--- scorched3d-43.3.d+dfsg/debian/changelog 2014-01-29 08:18:17.0 +1300
+++ scorched3d-43.3.d+dfsg/debian/changelog 2014-05-27 14:48:01.0 +1200
@@ -1,3 +1,10 @@
+scorched3d (43.3.d+dfsg-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0 (new patch 0008-wx3.0-compat.patch).
+
+ -- Olly Betts o...@survex.com Tue, 27 May 2014 14:47:53 +1200
+
scorched3d (43.3.d+dfsg-1) unstable; urgency=medium
[ Juhani Numminen ]
diff -Nru scorched3d-43.3.d+dfsg/debian/control scorched3d-43.3.d+dfsg/debian/control
--- scorched3d-43.3.d+dfsg/debian/control 2014-01-29 03:17:03.0 +1300
+++ scorched3d-43.3.d+dfsg/debian/control 2014-05-01 20:33:06.0 +1200
@@ -22,7 +22,7 @@
libsdl-net1.2-dev,
libsdl1.2-dev,
libvorbis-dev,
- libwxgtk2.8-dev,
+ libwxgtk3.0-dev,
pkg-config
Build-Conflicts: nvidia-glx
Standards-Version: 3.9.5
diff -Nru scorched3d-43.3.d+dfsg/debian/patches/0008-wx3.0-compat.patch scorched3d-43.3.d+dfsg/debian/patches/0008-wx3.0-compat.patch
--- scorched3d-43.3.d+dfsg/debian/patches/0008-wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ scorched3d-43.3.d+dfsg/debian/patches/0008-wx3.0-compat.patch 2014-05-27 17:44:20.0 +1200
@@ -0,0 +1,166 @@
+Description: Fix to build with wxWidgets 3.0
+Author: Olly Betts o...@survex.com
+Last-Update: 2014-05-01
+
+--- a/src/launcher/wxdialogs/Display.cpp
b/src/launcher/wxdialogs/Display.cpp
+@@ -26,7 +26,7 @@
+ // Display settings
+ wxStaticBox *displayBox = new wxStaticBox(parent, -1, wxT(Display));
+ wxStaticBoxSizer *displaySizer = new wxStaticBoxSizer(displayBox, wxVERTICAL);
+- wxFlexGridSizer *displaySizer2 = new wxFlexGridSizer(2, 3, 5, 5);
++ wxFlexGridSizer *displaySizer2 = new wxFlexGridSizer(0, 3, 5, 5);
+ wxStaticText *resText = new wxStaticText(parent, -1, wxT(Resolution :));
+ IDC_DISPLAY_CTRL =
+ new wxComboBox(parent, -1,
+@@ -88,7 +88,7 @@
+ // Sound settings
+ wxStaticBox *soundBox = new wxStaticBox(parent, -1, wxT(Sound));
+ wxStaticBoxSizer *soundSizerMain = new wxStaticBoxSizer(soundBox, wxVERTICAL);
+- wxFlexGridSizer *soundSizer1 = new wxFlexGridSizer(4, 2);
++ wxFlexGridSizer *soundSizer1 = new wxFlexGridSizer(0, 4, 2, 0);
+ wxStaticText *volumeText = new wxStaticText(parent, -1, wxT(Sound Volume :));
+ wxStaticText *musicVolumeText = new wxStaticText(parent, -1, wxT(Music Volume :));
+ wxStaticText *ambientVolumeText = new wxStaticText(parent, -1, wxT(Ambient Volume :));
+@@ -137,7 +137,7 @@
+ wxT(Game Detail Options));
+ wxStaticBoxSizer *speedSizer = new wxStaticBoxSizer(speedBox, wxHORIZONTAL);
+
+- wxGridSizer *loadSizer = new wxFlexGridSizer(2, 2);
++ wxGridSizer *loadSizer = new wxFlexGridSizer(0, 2, 2, 0);
+ IDC_LOADULTRA_CTRL = new wxButton(parent, ID_LOADULTRA, wxT(Ultra Detail), wxDefaultPosition, wxSize(120,-1));
+ IDC_LOADDEFAULTS_CTRL = new wxButton(parent, ID_LOADDEFAULTS, wxT(Normal Detail), wxDefaultPosition, wxSize(120,-1));
+ IDC_LOADMEDIUM_CTRL = new wxButton(parent, ID_LOADMEDIUM, wxT(Faster Detail), wxDefaultPosition, wxSize(120,-1));
+@@ -256,7 +256,7 @@
+ wxStaticBox *waterDetailBox = new wxStaticBox(parent, -1,
+ wxT(Graphics Detail));
+ wxStaticBoxSizer *waterDetailSizer = new wxStaticBoxSizer(waterDetailBox, wxHORIZONTAL);
+- wxGridSizer *waterDetailSizer2 = new wxGridSizer(3, 1, 10, 10);
++ wxGridSizer *waterDetailSizer2 = new wxGridSizer(0, 1, 10, 10);
+
+ IDC_NOWATERREF_CTRL =
+ new wxCheckBox(parent, -1, wxT(Don't draw water reflections - Large Framerate Improvement));
+@@ -471,7 +471,7 @@
+ {
+ wxScrolledWindow *scrolledWindow = new wxScrolledWindow(parent, -1,
+ wxDefaultPosition, wxSize(480, 250));
+- wxSizer *sizer = new wxFlexGridSizer(5, 1);
++ wxSizer *sizer = new wxFlexGridSizer(0, 5, 1, 0);
+
+ keyboardKeyList.clear();
+ if (!Keyboard::instance()-loadKeyFile())
+--- a/src/launcher/wxdialogs/DisplayDialog.cpp
b/src/launcher/wxdialogs/DisplayDialog.cpp
+@@ -449,15 +449,15 @@
+ IDC_SLIDER1_CTRL-SetValue(OptionsDisplay::instance()-getBrightness());
+ IDC_SLIDER1_CTRL-SetToolTip(wxString(OptionsDisplay::instance()-getBrightnessEntry().getDescription(), wxConvUTF8));
+ IDC_VOLUME_CTRL-SetRange(0, 128);
+- IDC_VOLUME_CTRL-SetTickFreq(4, 0);
++ IDC_VOLUME_CTRL-SetTickFreq(4);
+ IDC_VOLUME_CTRL-SetValue(OptionsDisplay::instance()-getSoundVolume());
+
Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11
The above mentioned patch did not do it for me, sub-windows/dialogs
were still CSD'd on WindowMaker at least. However, after some work,
I came up with the attached patch.
It's not very clean, but provides an environment variable-togglable
setting to disable CSD and headerbars. There are also some things missed
by it at the moment, some dialogs may still get a CSD close button.
It's also possible that this patch breaks something, due to my very
limited testing (I basically only use Transmission-GTK, Gnumeric and
Abiword with Gtk+3) ...
To enable, set environment variable GTK_DISABLE_CSD=1
I'll probably continue work on the remaining inconsistencies at
some point, but maybe this patch will help some other people in
the meanwhile.
--
] ccr/TNSP ^ pWp :: ccr tnsp org :: http://tnsp.org/~ccr/
] PGP key: 7BED 62DE 898D D1A4 FC4A F392 B705 E735 307B AAE3diff -r 8f959a652e16 gtk/gtkdialog.c
--- a/gtk/gtkdialog.c Tue May 27 08:15:40 2014 +0300
+++ b/gtk/gtkdialog.c Tue May 27 09:40:36 2014 +0300
@@ -288,10 +288,11 @@
apply_use_header_bar (GtkDialog *dialog)
{
GtkDialogPrivate *priv = dialog-priv;
+ gboolean disable_csd = g_strcmp0 (g_getenv (GTK_DISABLE_CSD), 1) == 0;
gtk_widget_set_visible (priv-action_area, !priv-use_header_bar);
gtk_widget_set_visible (priv-headerbar, priv-use_header_bar);
- if (!priv-use_header_bar)
+ if (!priv-use_header_bar !disable_csd)
{
GtkWidget *box = NULL;
@@ -312,6 +313,7 @@
gtk_window_set_titlebar (GTK_WINDOW (dialog), box);
}
+
if (priv-use_header_bar)
g_signal_connect (priv-action_area, add, G_CALLBACK (add_cb), dialog);
}
diff -r 8f959a652e16 gtk/gtkwindow.c
--- a/gtk/gtkwindow.c Tue May 27 08:15:40 2014 +0300
+++ b/gtk/gtkwindow.c Tue May 27 09:40:36 2014 +0300
@@ -3607,9 +3607,13 @@
#ifdef GDK_WINDOWING_X11
if (GDK_IS_X11_DISPLAY (gtk_widget_get_display (widget)))
{
+ gboolean disable_csd = g_strcmp0 (g_getenv (GTK_DISABLE_CSD), 1) == 0;
GdkScreen *screen;
GdkVisual *visual;
+ if (disable_csd)
+return FALSE;
+
screen = gtk_widget_get_screen (widget);
if (!gdk_screen_is_composited (screen))
@@ -3788,11 +3792,12 @@
gdk_window = gtk_widget_get_window (GTK_WIDGET (window));
if (gdk_window)
{
+ gboolean disable_csd = g_strcmp0 (g_getenv (GTK_DISABLE_CSD), 1) == 0;
if (priv-decorated)
{
- if (priv-client_decorated)
+ if (priv-client_decorated !disable_csd)
gdk_window_set_decorations (gdk_window, 0);
- else if (priv-custom_title)
+ else if (priv-custom_title !disable_csd)
gdk_window_set_decorations (gdk_window, GDK_DECOR_BORDER);
else
gdk_window_set_decorations (gdk_window, GDK_DECOR_ALL);
@@ -5379,6 +5384,10 @@
{
GtkWindowPrivate *priv = window-priv;
const gchar *csd_env;
+ gboolean disable_csd = g_strcmp0 (g_getenv (GTK_DISABLE_CSD), 1) == 0;
+
+ if (disable_csd)
+return FALSE;
if (!priv-decorated)
return FALSE;
@@ -6008,6 +6017,7 @@
gint i;
int old_scale;
GList *link;
+ gboolean disable_csd = g_strcmp0 (g_getenv (GTK_DISABLE_CSD), 1) == 0;
window = GTK_WINDOW (widget);
priv = window-priv;
@@ -6186,10 +6196,13 @@
if (priv-wm_role)
gdk_window_set_role (gdk_window, priv-wm_role);
- if (!priv-decorated || priv-client_decorated)
-gdk_window_set_decorations (gdk_window, 0);
- else if (priv-custom_title)
-gdk_window_set_decorations (gdk_window, GDK_DECOR_BORDER);
+ if (!disable_csd)
+{
+ if (!priv-decorated || priv-client_decorated)
+gdk_window_set_decorations (gdk_window, 0);
+ else if (priv-custom_title)
+gdk_window_set_decorations (gdk_window, GDK_DECOR_BORDER);
+}
if (!priv-deletable)
gdk_window_set_functions (gdk_window, GDK_FUNC_ALL | GDK_FUNC_CLOSE);
Bug#749464: debian-maintainers: Annual ping for Luke Cycon
Package: debian-maintainers Severity: normal My annual ping is here. Bit late, but better late than never. Thanks! ~ Luke signature.asc Description: PGP signature
Bug#749462: [pcp] Bug#749462: pcp-gui-testsuite: not installable in sid
Hi Ralf, - Original Message - Package: pcp-gui-testsuite Version: 1.5.13 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, pcp-gui-testsuite is no longer installable in sid as it depends on pcp-gui (= 1.5.13). Since pcp-gui moved into the pcp source package we have pcp-gui version 3.9.4 in sid. Shouldn't the pcp-gui-testsuite package be removed from sid (or rather the whole pcp-gui source package)? Yep, the whole pcp-gui source package should be removed - just looking into how to do that. thanks. -- Nathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749465: debian-maintainers: Annual ping for Matteo F. Vescovi
Package: debian-maintainers Severity: normal Hi, this is my annual ping as Debian Maintainer. I'm still actively maintaining packages in Debian, as reported at [1]. So, please keep my key in the DM keyring. Cheers. [1] http://qa.debian.org/developer.php?login=mfv -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A signature.asc Description: Digital signature
Bug#677865: Re: Bug#677865: dpkg-gencontrol warns about 'File::FcntlLock not available'
Hi, I realized that I can install a 32-bit version of Debian in a virtual box also on an 64-bit machine and that allowed me to find the reason for the failing tests. As you already may have suspected, it was a rather stupid mistake: I had forgotten to pass the CFLAGS Perl was build with to the C compiler when creating the program that determines what format string to pass to pack/unpack. And since the Debian version of Perl seems to be build with large file and 64-bit offset enabled on 32-bit machines, but this isn't the com- pilers default setting, a mismatch between the flock struct Perl uses and what my program thinks it is resulted. This hopefully is now corrected in the new 0.19 version I just uploaded to CPAN. Thank you for your patience and help! Best regards, Jens -- \ Jens Thoms Toerring j...@toerring.de \___ http://toerring.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711833: Preparing new package upload
Hello, I propose to write a simple man page in order to have a clean package. Regards, Yoann 2014-05-26 20:35 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: Hei, I fixed all the errors reported by lintian, sorry for not giving notice that I was working on them. As far as I can see the remaining message from lintian is: W: postr: binary-without-manpage usr/bin/postr I have not written a manpage before so the warning is not that important to me. I will publish the package soon, after cleaning up the changelog. I have set PAPT as the maintainer and both of us as uploaders.
Bug#725925: Can I get my $500 now, please? ;-)
Hi Thorsten, Thanks for the patch. I am not entirely convinced it is correct though, as it does change what gets gets passed into realtime_ldap_base_ap (two arguments have been already been consumed). An alternative patch was suggested in the upstream issue which instead makes a copy of the variadic list: https://issues.asterisk.org/jira/browse/ASTERISK-19941 Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
reopen 746994 found 746994 3.9.4 thanks On Tue, May 27, 2014 at 01:09:50AM -0400, Nathan Scott wrote: Closing this bug, as it appears to be a problem specific to the bug reporters machine, and no further information has been forthcoming. Since /bin/systemd is the location of systemd from the systemd deb, the bug report appears self-contradictory... not alot to work with here I'm afraid. Please reopen if additional information comes to hand - thanks! This is not a problem with my machine, this is something fully reproducible, even with version 3.9.4. The configure script tries to find systemd in /bin/systemd, while ps -ef show a different path: $ ps -ef | grep systemd root 1 0 0 avril30 ? 00:00:01 /lib/systemd/systemd --system --deserialize 22 root 155 1 0 avril30 ? 00:00:02 /lib/systemd/systemd-journald root 167 1 0 avril30 ? 00:00:00 /lib/systemd/systemd-udevd root 634 1 0 avril30 ? 00:00:00 /lib/systemd/systemd-logind I am therefore reopening the bug. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749266: wheezy-pu: package eglibc/2.13-38+deb7u2
On Mon, May 26, 2014 at 12:38:05PM +0100, Adam D. Barratt wrote: Control: tags -1 + confirmed On Sun, 2014-05-25 at 20:37 +0200, Aurelien Jarno wrote: We would like to fix a some issues that have been identified in the eglibc version included in wheezy. The best is probably to describe the changelog: [...] | * debian/patches/any/cvs-CVE-2013-4458.diff: backport a new part from | upstream to fix a regression introduced in 2.13-38+deb7u1 in IPv6 name | resolution. Closes: #738652. This fixes a regression caused by the deb7u1 upload. We had to backport some patches to be able to fix the CVE-2013-4458 issue, and it occurs that one of the patches introduced a bug fixed around one year after. Therefore cvs-CVE-2013-4458.diff has been modified to also include this patch, which is already included in upstream and jessie/sid for quite some time. #738652 has rather confused version information, claiming that it affects 2.17-97 and above. Assuming that's entirely wrong, please fix it. :-) This is indeed wrong, I have fixed it. Other than the above note, please go ahead; thanks. Great, thanks for the review. I have just uploaded the package. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745550: May be related to systemd
On 05/27/2014 01:25 AM, Felipe Sateler wrote: On Mon, May 19, 2014 at 10:33 AM, Eric Valette eric.vale...@free.fr wrote: When I saw problem with dbus and as I moved recently to systemd init, I suspected systemd changes/init system chnage might be related. Switched back to sysv init and problem is gone. I now have my analog audio device back, pulseaudio does no more hange same thing for Phonon. Are you sure this is the correct bug? I think this is meant for #748651 Absolutely. It is while I tried to debug this one that I discovered #748651 by trying to launch pulseaudio in debug mode and it was stuck for 2 mins. For the record, I also suffered #745550 on my home main computer: no sound, kde multimedia pulseaudio config hanging at launch, but had to leave home for work before fixing it. Then on my professional computer, I discovered I had no sound too and that the analog audio device indeed disappeared as per this bug. Bug #74865, led me to dbus and as moving to systemd was one of the main change I did recently on both computers and I know it heavily uses dbus/udev, I tried to switch back to sysv init and it solved the problem right away on both machines. I have no clue on the reason and anyway, the number of bug I have found already using systemd is huge enough and I will wait a bit it stabilize. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746996: pcp ships an upstream binary without rebuilding it
On Thu, May 15, 2014 at 11:41:36PM -0400, Nathan Scott wrote: Hi Aurelien, | On i386, pcp ships the upstream binary src/pmdas/mmv/mmvdump into | /var/lib/pcp/pmdas/mmv/mmvdump without rebuilding it. This violates | Debian policy and might be used by upstream to introduce backdoors or | other security issues. What gives that impression? It seems to not be the case to me, there is clearly code, makefile and no binary in the source tar ball... $ tar tzf ~/SOURCES/pcp-3.9.2.src.tar.gz | grep mmvdump pcp-3.9.2/src/pmdas/mmv/mmvdump.c You are looking at the upstream tarball. Given you repackage it (which probably warrants another bug report), you include some additionbal binaries. wget http://snapshot.debian.org/archive/debian/20140416T053134Z/pool/main/p/pcp/pcp_3.9.2.tar.xz $ tar tvfJ pcp_3.9.2.tar.xz | grep mmvdump -rwxr-xr-x 0/0 27908 2014-03-28 10:28 pcp-3.9.2/src/pmdas/mmv/mmvdump -rw-r--r-- 0/08951 2014-01-09 00:29 pcp-3.9.2/src/pmdas/mmv/mmvdump.c Of course, this has silently been fixed in version 3.9.4 without any mention in the changelog. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749163: handbrake: minor rewording in description
Am Dienstag, den 27.05.2014, 05:40 +0530 schrieb Faheem Mitha: Ok, if the paragraph no longer applies, then removing it is clearly the correct thing to do. Are you planning to do so for the next Debian release? It's changed in GIT and will be part of the next upload. Thank you again, Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746996: pcp ships an upstream binary without rebuilding it
- Original Message - On Thu, May 15, 2014 at 11:41:36PM -0400, Nathan Scott wrote: Hi Aurelien, | On i386, pcp ships the upstream binary src/pmdas/mmv/mmvdump into | /var/lib/pcp/pmdas/mmv/mmvdump without rebuilding it. This violates | Debian policy and might be used by upstream to introduce backdoors or | other security issues. What gives that impression? It seems to not be the case to me, there is clearly code, makefile and no binary in the source tar ball... $ tar tzf ~/SOURCES/pcp-3.9.2.src.tar.gz | grep mmvdump pcp-3.9.2/src/pmdas/mmv/mmvdump.c You are looking at the upstream tarball. Given you repackage it (which probably warrants another bug report), you include some additionbal binaries. *nod* - before 3.9.4 this was sort-of the case (the source tarball is generated during the build from makefiles) and this is now done differently again (3.9.4+), using git to generate the src.tar.gz, but anyway ... ultimately, there was never any intention to ship binaries accidentally this way, and it was accidentally resolved by the git-archive transition in 3.9.4. And confusion on my end resulted from looking at the 3.9.2 source tarball generated from a different build - you are correct. wget http://snapshot.debian.org/archive/debian/20140416T053134Z/pool/main/p/pcp/pcp_3.9.2.tar.xz *nod*, my mistake - and as mentioned, 3.9.4 has kindly fixed this up for us as a by-product of other changes. Of course, this has silently been fixed in version 3.9.4 without any mention in the changelog. *nod* - it was not a known issue at that time. Hope this helps sort things out; I guess at the end of the day, on this bug at least, alls well that ends well. thanks Aurelien. -- Nathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749466: ITP: 3dldf-doc -- 3D drawing with MetaPost output -- documentation
Package: wnpp Severity: wishlist Owner: Jerome Benoit calcu...@rezozer.net * Package name: 3dldf-doc Version : 2.0.3 Upstream Author : Laurence D. Finston laurence.fins...@gmx.de * URL : http://www.gnu.org/software/3dldf * License : GFDL Programming Lang: TeXinfo Description : 3D drawing with MetaPost output -- documentation GNU 3DLDF implements an interpreter for a METAFONT-like language for three-dimensional drawing with MetaPost output. GNU 3DLDF is mainly intended to provide a convenient way of creating 3D graphics for inclusion in TeX documents; it can also be used for creating animations, which can contain text typeset using TeX. This package contains the documentation for 3dldf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746925: glib2.0 FTBFS on alpha: test-suite failure in async-splice-output-stream
It's not possible to bisect the failed glib2.0 test (async-splice-output-stream) on alpha as the commit that brings in the new test is the first one to fail. Looks like the bug was always there but never trapped by the test suite until a test was introduced. Interestingly the async-splice-output-steam test only fails when run under an SMP kernel. It always passes on a single CPU system. I note the test does a call to the pthread code; that's probably the problem --- there is definitely something occassionly racey in the Alpha pthread library that is only exposed when running under a multi-CPU system. For the time being I have put glib2.0 into the do-not-take-for-building list of the multi-cpu buildd, thus hopefully the next upload should build successfully on the other (UP) buildd. Cheers Michael. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749467: Duplicate close command to imap server
Package: imapfilter Version: 1:2.5.2-2 Severity: normal Hi regularly see errors BAD Command received in Invalid state. Doing an imapfilter -v I see a duplicate CLOSE command is sent (thus the Invalid state for the second CLOSE) eg : C (4): 1081 UID FETCH 949 BODY.PEEK[TEXT] S (4): 1081 OK FETCH completed. C (4): 1082 CLOSE S (4): 1082 OK CLOSE completed. C (4): 1083 CLOSE S (4): 1083 BAD Command received in Invalid state. -- System Information: Debian Release: jessie/sid APT prefers testing-proposed-updates APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (600, 'stable'), (500, 'proposed-updates'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 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 imapfilter depends on: ii libc62.18-7 ii liblua5.2-0 5.2.3-1 ii libpcre3 1:8.31-5 ii libssl1.0.0 1.0.1g-4 imapfilter recommends no packages. imapfilter suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
Hi Aurelien, - Original Message - The configure script tries to find systemd in /bin/systemd, while ps -ef show a different path: $ ps -ef | grep systemd root 1 0 0 avril30 ? 00:00:01 /lib/systemd/systemd --system --deserialize 22 Ah, there's that information I was looking for - thanks! I don't run systemd on my primary machine yet, so had been looking here as a poor source of second-hand information: https://packages.debian.org/sid/amd64/systemd/filelist ... which fooled me into thinking we're doing the same thing as Fedora with the /bin/systemd listed there. I am therefore reopening the bug. Thanks! Will address this in pcp-3.9.5 shortly - sorry about closing prematurely, I thought you'd lost interest / found the source of that incorrectly-suspected-misconfiguration when I didn't hear back before. cheers. -- Nathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749468: pep8 manpage is outdated for current versions of pep8
Package: pep8 Version: 1.4.6-1.1 Severity: minor Options that are supported by pep8 but are missing in the pep8 manpage include e.g.: --config=path --first --format=format --hang-closing --max-line-length=n --select=errors --version Whereas there exist options in the manpage that aren't actually supported by pep8 any longer, e.g.: --doctest --testsuite=dir I'll provide a patch which takes care of those changes. regards, -mika- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2014-05-27t09-31...@devnull.michael-prokop.at
Bug#749469: Please add home page URL in control file
Package: src:libmpeg3 Version: 1.5.4-5 Severity: minor Tags: patch The control file lack a link to the upstream project homepage. Please apply this patch: diff -ur libmpeg3-1.5.4.old/debian/control libmpeg3-1.5.4/debian/control --- libmpeg3-1.5.4.old/debian/control 2014-05-27 09:58:49.0 +0200 +++ libmpeg3-1.5.4/debian/control 2014-05-27 09:58:31.667078457 +0200 @@ -4,6 +4,7 @@ Maintainer: David Martínez Moreno en...@debian.org Standards-Version: 3.6.2.2 Build-Depends: debhelper (= 4.0.0), liba52-dev +Homepage: http://heroines.sourceforge.net/libmpeg3.php Package: mpeg3-utils Architecture: any -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749470: Modify the control file for bootstrapping without texlive and dh-autoreconf
Source: flex Severity: wishlist Tags: patch Hi, As noted in #749344, here's the follow-up patch that modifies the control file with build profiles support. Of course, applying it will have to wait until #744246 is resolved (actual build infrastructure support for build profiles), until then an uploaded package would fail to build. G'luck, Peter -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-1-686-pae (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- Peter Pentchev r...@ringlet.net r...@freebsd.org p.penc...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 yields falsehood, when appended to its quotation. yields falsehood, when appended to its quotation. signature.asc Description: Digital signature
Bug#677865: Re: Bug#677865: dpkg-gencontrol warns about 'File::FcntlLock not available'
-=| Jens Thoms Toerring, 27.05.2014 09:21:42 +0200 |=- I realized that I can install a 32-bit version of Debian in a virtual box also on an 64-bit machine and that allowed me to find the reason for the failing tests. As you already may have suspected, it was a rather stupid mistake: I had forgotten to pass the CFLAGS Perl was build with to the C compiler when creating the program that determines what format string to pass to pack/unpack. Ah, good catch! And since the Debian version of Perl seems to be build with large file and 64-bit offset enabled on 32-bit machines, but this isn't the com- pilers default setting, a mismatch between the flock struct Perl uses and what my program thinks it is resulted. This hopefully is now corrected in the new 0.19 version I just uploaded to CPAN. Package updated and uploaded to unstable. I tested it in a 32-bit chroot and it built fine there. Should appear in the build network soon. https://buildd.debian.org/status/logs.php?pkg=libfile-fcntllock-perl Cheers, dam signature.asc Description: Digital signature
Bug#749471: ghc: changeWorkingDirectory systematically fails
Package: ghc Version: 7.6.3-10 Severity: normal Dear Maintainer, :cd'ind in GHCi is not possible anymore: bdaix@nephtys:~$ pwd /home/bdaix bdaix@nephtys:~$ ghci GHCi, version 7.6.3: http://www.haskell.org/ghc/ :? for help Loading package ghc-prim ... linking ... done. Loading package integer-gmp ... linking ... done. Loading package base ... linking ... done. Prelude :cd .. *** Exception: ..: changeWorkingDirectory: does not exist (No such file or directory) Prelude This issue also breaks haskell-mode. Cheers, -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ghc depends on: ii gcc 4:4.8.2-4 ii libbsd-dev 0.6.0-2 ii libc6 2.18-7 ii libc6-dev 2.18-7 ii libffi-dev 3.1~rc1+r3.0.13-12 ii libffi6 3.1~rc1+r3.0.13-12 ii libgmp-dev 2:6.0.0+dfsg-4 ii libgmp102:6.0.0+dfsg-4 ii libtinfo5 5.9+20140118-1 ghc recommends no packages. Versions of packages ghc suggests: pn ghc-doc none pn ghc-prof none pn haskell-doc none pn llvm none ii perl 5.18.2-4 -- no debconf information -- Boris Daix -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
On Tue, May 27, 2014 at 03:46:37AM -0400, Nathan Scott wrote: Hi Aurelien, - Original Message - The configure script tries to find systemd in /bin/systemd, while ps -ef show a different path: $ ps -ef | grep systemd root 1 0 0 avril30 ? 00:00:01 /lib/systemd/systemd --system --deserialize 22 Ah, there's that information I was looking for - thanks! I don't run systemd on my primary machine yet, so had been looking here as a poor source of second-hand information: https://packages.debian.org/sid/amd64/systemd/filelist ... which fooled me into thinking we're doing the same thing as Fedora with the /bin/systemd listed there. I am therefore reopening the bug. Thanks! Will address this in pcp-3.9.5 shortly - sorry about closing prematurely, I thought you'd lost interest / found the source of that incorrectly-suspected-misconfiguration when I didn't hear back before. The problem is that you answered the bug only to the BTS, without putting me in Cc:. Thus I never received your email. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749468: [PATCH] Update and extend pep8 manpage
Several options have been introduced since pep8 0.4.2 and some of them are gone. List of options as presented by `pep8 --help` output, and while at it also include some useful usage examples. Closes: #749468 --- pep8.1 | 56 1 file changed, 44 insertions(+), 12 deletions(-) diff --git a/pep8.1 b/pep8.1 index 376f0f4..9a17236 100644 --- a/pep8.1 +++ b/pep8.1 @@ -1,4 +1,4 @@ -.TH PEP8 1 October 2009 pep8 0.4.2 User Commands +.TH PEP8 1 May 2014 pep8 1.4.6 User Commands .SH NAME pep8 \- A tool to check your Python code against some of the style conventions in PEP 8. .SH SYNOPSIS @@ -6,6 +6,9 @@ pep8 \- A tool to check your Python code against some of the style conventions i [\fIoptions\fR] \fIinput \fR... .SH OPTIONS .TP +\fB\--version\fR +show program's version number and exit +.TP \fB\-h\fR, \fB\-\-help\fR show this help message and exit .TP @@ -15,34 +18,63 @@ print status messages, or debug with \fB\-vv\fR \fB\-q\fR, \fB\-\-quiet\fR report only file names, or nothing with \fB\-qq\fR .TP +\fB\-r\fR, \fB\-\-repeat\fR +(obsolete) show all occurrences of the same error +.TP +\fB\--first\fR +show first occurrence of each error +.TP \fB\-\-exclude\fR=\fIpatterns\fR -skip matches (default .svn,CVS,*.pyc,*.pyo) +exclude files or directories which match these comma separated patterns (default: .svn,CVS,.bzr,.hg,.git,__pycache__) .TP \fB\-\-filename\fR=\fIpatterns\fR -only check matching files (e.g. *.py) +when parsing directories, only check filenames matching these comma separated patterns (default: *.py) +.TP +\fB\-\-select\fR=\fIerrors\fR +select errors and warnings (e.g. E,W6) .TP \fB\-\-ignore\fR=\fIerrors\fR skip errors and warnings (e.g. E4,W) .TP -\fB\-\-repeat\fR -show all occurrences of the same error -.TP \fB\-\-show\-source\fR show source code for each error .TP \fB\-\-show\-pep8\fR -show text of PEP 8 for each error +show text of PEP 8 for each error (implies --first) .TP \fB\-\-statistics\fR count errors and warnings .TP +\fB\-\-count\fR +print total number of errors and warnings to standard error and set exit code to 1 if total is not null +.TP +\fB\-\-max\-line\-length\fR=\fIn\fR +set maximum allowed line length (default: 79) +.TP +\fB\-\-hang-closing\fR +hang closing bracket instead of matching indentation of opening bracket's line +.TP +\fB\-\-format\fR=\fIformat\fR +set the error format [default|pylint|custom] +.TP +\fB\-\-diff\fR +report only lines changed according to the unified diff received on STDIN +.TP \fB\-\-benchmark\fR measure processing speed .TP -\fB\-\-testsuite\fR=\fIdir\fR -run regression tests from dir +\fB\-\-config\fR=\fIpath\fR +user config file location (default: $HOME/.config/pep8) +.TP +.SH USAGE EXAMPLES +.TP +Display how often each error was found: +.sp +% pep8 --statistics -qq example/lib/ +.TP +Show source code and more verbose explanation from PEP 8: +.sp +% pep8 --show-source --show-pep8 foo.py .TP -\fB\-\-doctest\fR -run doctest on myself .SH AUTHOR -This manual page was written by David Watson da...@bashton.com. +This manual page was written by David Watson da...@bashton.com and Michael Prokop m...@debian.org. -- 1.9.0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749472: openssh-server: openssl restart failure when upgrading from wheezy: OpenSSL version mismatch. Built against 1000105f, you have 10001080
Package: openssh-server Version: 1:6.6p1-5 Severity: important When I upgrade from wheezy to jessie on a machine with openssh-server installed, the openssl package tries to restart openssh but fails: # apt-get update ... # apt-get -y upgrade ... Preparing to unpack .../libssl1.0.0_1.0.1g-4_amd64.deb ... Unpacking libssl1.0.0:amd64 (1.0.1g-4) over (1.0.1e-2+deb7u9) ... Setting up libssl1.0.0:amd64 (1.0.1g-4) ... Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... Restarting services possibly affected by the upgrade: OpenSSL version mismatch. Built against 1000105f, you have 10001080 invoke-rc.d: initscript ssh, action restart failed. Configuring libssl1.0.0:amd64 - Failure restarting some services for OpenSSL upgrade The following services could not be restarted for the OpenSSL library upgrade: ssh You will need to start these manually by running '/etc/init.d/service start'. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-server depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii dpkg 1.17.9 ii init-system-helpers1.18 ii libc6 2.18-7 ii libcomerr2 1.42.10-1 ii libgssapi-krb5-2 1.12.1+dfsg-1 ii libkrb5-3 1.12.1+dfsg-1 ii libpam-modules 1.1.8-3 ii libpam-runtime 1.1.8-3 ii libpam0g 1.1.8-3 ii libselinux12.3-1 ii libssl1.0.01.0.1g-4 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian12 ii openssh-client 1:6.6p1-5 ii openssh-sftp-server1:6.6p1-5 ii procps 1:3.3.9-2 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages openssh-server recommends: ii ncurses-term 5.9+20140118-1 ii xauth 1:1.0.7-1 Versions of packages openssh-server suggests: pn molly-guard none pn monkeysphere none pn rssh none ii ssh-askpass-gnome [ssh-askpass] 1:6.6p1-5 pn ufw none -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#749473: libssl1.0.0: postinst recommends using /etc/init.d/ instead of service or invoke-rc.d
Package: libssl1.0.0 Version: 1.0.1g-4 Severity: normal The postinst of libssl1.0.0 recommends using /etc/init.d/ instead of service or invoke-rc.d for restarting services. Using /etc/init.d/ directly instead of via service or invoke-rc.d has all sorts of possibly nasty consequences due to environment variable leakage. Please adjust the error message to print a list of service or invoke-rc.d commands that administrators should use when restarting services fails. http://bugs.debian.org/749472 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libssl1.0.0 depends on: ii debconf [debconf-2.0] 1.5.53 ii libc6 2.18-7 ii multiarch-support 2.18-7 libssl1.0.0 recommends no packages. libssl1.0.0 suggests no packages. -- debconf information excluded -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#749474: [polipo] example config.example file not work
Package: polipo Version: 1.0.4.1-6 Severity: normal --- Please enter the report below this line. --- The example config file under example doesn't supply log entry, and it doesn't work. It will work by adding the two log config entries in default /etc/polipo/config to config.example --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 990 unstableftp.debian.org 500 testing-updates ftp.debian.org 500 testing security.debian.org 500 testing ftp.debian.org 1 experimentalftp.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== lsb-base| 4.1+Debian12 libc6 (= 2.8) | Package's Recommends field is empty. Package's Suggests field is empty. -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683731:
Would be great, if this bug could be fixed and closed. Like #54 said: It is in backupninja upstream since ~ 6 month - https://git.sarava.org/?p=backupninja.git;a=commitdiff;h=b8b8b46fbaf9acbdc769d311a064ab89bb670ef7 Thanks and regards Jan
Bug#742942: Bug#749438: gparted stuck at searching /dev/sdc partitions
On Mon, May 26, 2014 at 06:52:11PM -0400, Phillip Susi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ok, I have been able to reproduce this and diagnose the problem. Your 3 1/2 inch floppy link file contains the 1/2 character, which in code page 437 ( the original IBM PC character set ) is 0xBD. In UTF-8, this is an incomplete multi byte sequence. Dosfsck therefore, is emitting invalid UTF-8 character sequences by blindly spitting out the characters as they appear on disk. It should be translating them to the current system character set ( normally UTF-8 ) using the iconv library, and assuming the characters on disk are CP-437 unless otherwise directed. I am therefore cloning this bug and assigning it to dosfstools. In addition, when using iconv to convert this character to valid UTF-8, it maps it to U+255C instead of U+00BD, so I'm cloning the bug there as well. That is wrong. 0xBD in CP437 or CP850 page code is '╜' which corresponds to character U+255C as iconv says. 0xBD is the '½' character (U+00BD) in the CP1252 page code usually used by Windows. I therefore think this bug is invalid, please close it if you agree. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749427: isql fails to load multi-arched odbc drivers
Re: To Debian Bug Tracking System 2014-05-26 20140526212058.ga1...@msgid.df7cb.de Package: libiodbc2 Version: 3.52.9-1 Severity: grave When running the psqlodbc testsuite, I found that isql no longer loads psqlodbca.so correctly: 1: SQLDriverConnect = [iODBC][Driver Manager]psqlodbca.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden (0) SQLSTATE=0 2: SQLDriverConnect = [iODBC][Driver Manager]Specified driver could not be loaded (0) SQLSTATE=IM003 strace: open(/usr/lib/x86_64-linux-gnu/psqlodbca.so, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) The correct location includes an extra odbc/ in the path: odbc-postgresql:amd64: /usr/lib/x86_64-linux-gnu/odbc/psqlodbca.so Steps to reproduce: sudo apt-get install odbc-postgresql postgresql, unixodbc, iodbc apt-get source psqlodbc cd */ debian/tests/isql Fwiw, the bug seems to be in iodbc, not libiodbc2 - I ran into the bug after upgrading only iodbc. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749475: icewm: New 1.3.8 version available
Package: icewm
Version: 1.3.7-5
Severity: wishlist
Dear Maintainer,
Seems that a new icewm version is available from
http://sourceforge.net/projects/icewm/files/icewm-1.3/1.3.8/
According to its changes file, these are the relevant news
stable:
1.3.8pre1: 2011-11-19
- fix focus issues with JDK7
- compile fix with deprecated
- Qt5 compatibility
- partial support for _NET_WM_STRUT_PARTIAL
Besides that, looking at its git repo,
http://sourceforge.net/p/icewm/git/ci/master/tree/
seems that other changes were included, like (at least part of)
debian/patches/{package_build_fixes,safe_get_argument}
Regards,
--
Agustin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725925: Can I get my $500 now, please? ;-)
Jeremy Lainé dixit: Thanks for the patch. I am not entirely convinced it is correct though, as it does change what gets gets passed into realtime_ldap_base_ap (two arguments have been already been consumed). Right, I had been wondering about that, too. The other modules’ functions do not consume them at all, they rather dereference the result of the consumer function. An alternative patch was suggested in the upstream issue which instead makes a copy of the variadic list: That is probably a sound fix, yes. https://issues.asterisk.org/jira/browse/ASTERISK-19941 I cannot access that, unfortunately: │Looking up issues.asterisk.org │Making HTTPS connection to issues.asterisk.org │SSL callback:ok, preverify_ok=1, ssl_okay=0 │SSL callback:ok, preverify_ok=1, ssl_okay=0 │SSL callback:ok, preverify_ok=1, ssl_okay=0 │Verified connection to issues.asterisk.org (cert=*.asterisk.org) │Certificate issued by: /C=US/O=GeoTrust, Inc./CN=RapidSSL CA │Secure 256-bit TLSv1/SSLv3 (DHE-RSA-AES256-SHA) HTTP connection │Sending HTTP request. │HTTP request sent; waiting for response. │Alert!: Unexpected network read error; connection aborted. │Can't Access `https://issues.asterisk.org/jira/browse/ASTERISK-19941' │Alert!: Unable to access document. But judging from your description of the patch, I’d say, go for it. Nik can probably test a fix on his server. (A bit unfortunate for all of us, a new major version was uploaded to sid at the time we finally got around to debug this. I have no idea how to best handle this (also since I don’t use Asterisk myself).) bye, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour” -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749476: spice-gtk: Please backport latest spice-gtk to Wheezy
Source: spice-gtk Severity: normal Recently I'm using remove-viewer (part of virt-viewer) with spice-gtk 0.23 on Sid. In comparison to last year when I was using wheezy the problems are almost completely gone and there are significant improvements. Yesterday I also tried spice-server 0.12.5-1 which includes opus and finally the sound problems I had from the end of 2011 when I started using spice are gone. Various dependencies including usbredir and opus are already available updated in wheezy-backports, should miss only spice-gtk and virt-viewer which I'll ask the backports. Can you please backports the last spice-gtk to use it on production systems with reliable Wheezy? Thanks for any reply and sorry for my bad english. -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749477: cuba: Conflicting declarations of function Vegas
Package: cuba Version: 3.0+2024-2 Severity: wishlist Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DHAVE_CONFIG_H -I./src/common -I. -I. -fPIC -o demo-c ./demo/demo-c.c libcuba.a -lm error: conflicting function declarations Vegas old definition in module demo-c file ./cuba.h line 24 void (const signed int, const signed int, signed int (*)(const signed int *ndim, const double *x, const signed int *ncomp, double *f, void *userdata), void *, const double, const double, const signed int, const signed int, const signed int, const signed int, const signed int, const signed int, const signed int, const signed int, const char *, signed int *, signed int *, double *, double *, double *) new definition in module Vegas file ./src/vegas/Vegas.c line 22 void (const signed int ndim, const signed int ncomp, signed int (*integrand)(const signed int *, const double *, const signed int *, double *, void *, const double *, const signed int *), void *userdata, const double epsrel, const double epsabs, const signed int flags, const signed int seed, const signed int mineval, const signed int maxeval, const signed int nstart, const signed int nincrease, const signed int nbatch, const signed int gridno, const char *statefile, signed int *pneval, signed int *pfail, double *integral, double *error, double *prob) makefile:225: recipe for target 'demo-c' failed make[2]: *** [demo-c] Error 64 make[2]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-cuba/cuba-3.0+2024' dh_auto_build: make -j1 returned exit code 2 debian/rules:20: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 So the issue here is the number of parameters of the function pointer integrand (the third parameter of Vegas). cuba.h exports this declaration towards demo-c: http://sources.debian.net/src/cuba/3.0+2024-2/cuba.h?hl=18#L18 But Vegas.c uses http://sources.debian.net/src/cuba/3.0+2024-2/src/vegas/decl.h?hl=31#L31 Hence demo-c appears to pass in a function of wrong type. Best, Michael pgpzk9lyQBQ2m.pgp Description: PGP signature
Bug#749478: please enable support for python3 bindings
Package: src:babeltrace
Version: 1.2.1-2
Tags: patch
Severity: wishlist
Please enable python3 bindings in the babeltrace package. Patch
attached.
Sebastian
From 52db172006200d97e3da7e3b87d1f29af0a9 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior sebast...@breakpoint.cc
Date: Tue, 27 May 2014 10:45:20 +0200
Subject: [PATCH] enable build of the python3 bindings
It does not work with python2 at all (it compiles but this is it). The
readme says that python3.0+ is required. Therefore I specified the
python intepreter and config in the configure run instead of using a
build-conflict on python2.7, 2.6 and so on.
Signed-off-by: Sebastian Andrzej Siewior sebast...@breakpoint.cc
---
debian/control| 15 ++-
debian/python3-babeltrace.install | 1 +
debian/rules | 5 -
3 files changed, 19 insertions(+), 2 deletions(-)
create mode 100644 debian/python3-babeltrace.install
diff --git a/debian/control b/debian/control
index 68fc9f8..9101c0c 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,8 @@ Section: libs
Priority: extra
Maintainer: Jon Bernard jbern...@debian.org
Build-Depends: debhelper (= 9~), libglib2.0-dev (= 2.16), uuid-dev,
- libpopt-dev, dh-autoreconf
+ libpopt-dev, dh-autoreconf, python3-dev, swig
+X-Python3-Version: = 3.0
Standards-Version: 3.9.5
Vcs-Git: git://anonscm.debian.org/collab-maint/babeltrace.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/babeltrace.git;a=summary
@@ -75,3 +76,15 @@ Description: Common Trace Format (CTF) development files
.
This package provides the development headers to link applications directly
against libbabeltrace-ctf.
+
+Package: python3-babeltrace
+Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Description: Babeltrace conversion libraries
+ Babeltrace provides trace reading and writing libraries, as well as a trace
+ converter. Plugins can be created for any trace format to allow its conversion
+ to/from any other supported format.
+ .
+ This package provides the python bindings for babeltrace.
diff --git a/debian/python3-babeltrace.install b/debian/python3-babeltrace.install
new file mode 100644
index 000..4606faa
--- /dev/null
+++ b/debian/python3-babeltrace.install
@@ -0,0 +1 @@
+usr/lib/python3*
diff --git a/debian/rules b/debian/rules
index 47b025c..bd0aae3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,10 @@
export DEB_BUILD_MAINT_OPTIONS := hardening=+all
%:
- dh $@ --with autoreconf
+ dh $@ --with autoreconf --with python3
+
+override_dh_auto_configure:
+ PYTHON=python3 PYTHON_CONFIG=/usr/bin/python3-config dh_auto_configure -- --enable-python-bindings
override_dh_auto_build:
dh_auto_build -- V=1
--
2.0.0.rc4
Bug#749479: Please include puppet into backports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: puppet Version: 3.6.1-1 Severity: wishlist As Puppet is doing the backward compatibility the wrong way, there is the problem that for the clients is always a current version of puppet available but for the server, that would most likely run on stable, only a old version is available that is not compatible anymore with the puppet client version in sid and testing. So please add puppet and puppetmaster to backports to have a working setup also with mixed environments. - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (800, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.10 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Versions of packages puppet depends on: ii init-system-helpers 1.18 ii puppet-common 3.6.1-1 ii ruby 1:2.1.0.1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 ii ruby2.0 [ruby-interpreter]2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter]2.1.2-2 puppet recommends no packages. Versions of packages puppet suggests: ii etckeeper 1.11 pn puppet-el none ii vim-puppet 3.6.1-1 - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJThFQbAAoJEKZ8CrGAGfasmVoL/0H/40D938/oNGS5I/aoRPWw kXbZKVfdxOQ63ZsrlrDJzZmt2jVeDtaD/BWXOT2JCItxQVDm0uJpQH9e43f9C5s3 Sop2mrp1CEfjanv8ymR5LxxDB4biLSAuQKWn7b8L029bQqIQq5fPJUxaXvE1+npz cNthIP08JewWKCAUJ9kXkXqvgwsEHcGEZbkPrNdr4IbvBCs4pEBj9oY6xYZoH7+g SDSQyc/ynlh5uaE1zFh8pZEe/ilBVn1UdtACnCT/fjvwOITxLtZNzcMeWo2t76oX jWrkGjsoDMx8HiMAYQoQSS4ZNROBS5eOfXonf8z4Xde165J/PbuA5kReSl3IdDKh kA5H1UY5iJ/dqnMUnb1tBb9Z4FDc7f2DGBPnm+o8Gs00UqMNAi2ukzJ2XuNY2iMP kx8NAZUHHNNcAN0fT1ZgdLiW1qXeuwTsUqa/TKIXab+RxUm27V6ox6dmspgWzw/F fSTfT/Ln/mAOm+sK+nseuY8BNM6AYjoIRwPGVGY3rA== =T3x1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743903:
Bad commit here: http://anonscm.debian.org/gitweb/?p=collab-maint/lsb.git;a=commitdiff;h=f4ed7f08600d633c3daba9f494997f1c3aed StringIO.StringIO and io.StringIO do not have identical API. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749480: cairo: Wrong conversion from double to enum
Package: cairo
Version: 1.12.16-2
Severity: minor
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. Please note that we
use our research compiler tool-chain (using tools from the cbmc package), which
permits extended reporting on type inconsistencies at link time.
[...]
gcc -DHAVE_CONFIG_H -I.
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/test -I..
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/test
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/test/pdiff
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/boilerplate
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/util/cairo-missing
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/util/cairo-script
-I/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/src -I../src
-D_REENTRANT -I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/freetype2-I/usr/include/libdrm -I/usr/include/libdrm
-I/usr/include/libpng12-Wall -Wextra -Wold-style-definition
-Wdeclaration-after-statement -Wmissing-declarations
-Werror-implicit-function-declaration -Wnested-externs -Wpointer-arith
-Wwrite-strings -Wsign-compare -Wstrict-prototypes -Wmissing-prototypes
-Wpacked -Wswitch-enum -Wmissing-format-attribute -Wbad-function-cast
-Wvolatile-register-var -Wstrict-aliasing=2 -Winit-self
-Wunsafe-loop-optimizations -Wno-missing-field-initializers
-Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline
-fno-strict-aliasing -fno-common -Wp,-D_FORTIFY_SOURCE=2
-Wno-unused-but-set-variable -D_FORTIFY_SOURCE=2
-D_REENTRANT -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -Wall -MT cairo_test_suite-path-precision.o -MD -MP -MF
.deps/cairo_test_suite-path-precision.Tpo -c -o
cairo_test_suite-path-precision.o `test -f 'path-precision.c' || echo
'/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/test/'`path-precision.c
file
/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/test/path-precision.c
line 40 function draw: in expression `95.00':
conversion from `double' to `int': implicit conversion not permitted
CONVERSION ERROR
Makefile:5710: recipe for target 'cairo_test_suite-path-precision.o' failed
make[5]: *** [cairo_test_suite-path-precision.o] Error 64
make[5]: Leaving directory
'/srv/jenkins-slave/workspace/sid-goto-cc-cairo/cairo-1.12.16/debian/build/main/test'
Makefile:8060: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
Review the code here:
http://sources.debian.net/src/cairo/1.12.16-2/test/path-precision.c?hl=40#L38
The issue is that cairo_path_data_t is a union, and such compound literals will
always use the first component of the union for initialisation. Hence double
values like 95.0 are necessarily converted to whatever the representation of the
enum is, such as int. Use the attached extracted test to convince yourself.
The net result is that this test (path-precision.c) will possibly fail for the
entirely wrong reason (it is expected to fail), providing zero test value.
Best,
Michael
#include assert.h
#include stdio.h
typedef enum _cairo_path_data_type {
CAIRO_PATH_MOVE_TO,
CAIRO_PATH_LINE_TO,
CAIRO_PATH_CURVE_TO,
CAIRO_PATH_CLOSE_PATH
} cairo_path_data_type_t;
typedef union _cairo_path_data_t cairo_path_data_t;
union _cairo_path_data_t {
struct {
cairo_path_data_type_t type;
int length;
} header;
struct {
double x, y;
} point;
};
int main()
{
cairo_path_data_t path_data[] = {
{ { CAIRO_PATH_MOVE_TO, 2 }, },
{ { 95.00, 40.00 }, },
{ { CAIRO_PATH_LINE_TO, 2 }, },
{ { 94.960533, 41.255810 }, },
{ { CAIRO_PATH_LINE_TO, 2 }, },
{ { 94.842293, 42.50666 }, },
{ { CAIRO_PATH_LINE_TO, 2 }, },
{ { 94.645744, 43.747627 }, },
{ { CAIRO_PATH_LINE_TO, 2 }, },
{ { 94.371666, 44.973797 }, },
};
printf(path_data[1].point.x=%f\n, path_data[1].point.x);
assert(path_data[1].point.x==95.0);
return 0;
}
pgpO5IbltHgT0.pgp
Description: PGP signature
Bug#743634: LO 4.2 now in sid - bug now RC
Hello, I'll try to upload it the upcoming weekend. Sebastian signature.asc Description: Digital signature
Bug#749481: ITP: node-with -- compile-time `with` statement - Node.js module
Subject: ITP: node-with -- compile-time `with` statement - Node.js module Package: wnpp Severity: wishlist Owner: Leo Iannacone l...@ubuntu.com * Package name: node-with Version : 3.0.0 Upstream Author : ForbesLindesay * URL : https://github.com/ForbesLindesay/with * License : Expat Programming Lang: JavaScript Description : compile-time `with` statement - Node.js module This module allows compilation of a JavaScript statement with a given scope object, as if it was in a `with` statement. . The `width` statement is deprecated and forbidden in ECMAScript 5 strict mode. . Node.js is an event-based server-side JavaScript engine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749462: [pcp] Bug#749462: pcp-gui-testsuite: not installable in sid
Hi Nathan, On Tue, May 27, 2014 at 03:13:04AM -0400, Nathan Scott wrote: we have pcp-gui version 3.9.4 in sid. Shouldn't the pcp-gui-testsuite package be removed from sid (or rather the whole pcp-gui source package)? Yep, the whole pcp-gui source package should be removed - just looking into how to do that. it ususally should happen automatically, but it probably didn't in this case since pcp-gui-testsuite isn't provided by the pcp source package. See [1] for how to request removals. -Ralf. [1] https://wiki.debian.org/ftpmaster_Removals -- Ralf Treinen Laboratoire Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.pps.univ-paris-diderot.fr/~treinen/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749482: ITP: node-constantinople -- determine if an expression evaluates to a constant - Node.js module
Subject: ITP: node-constantinople -- determine if an expression evaluates to a constant - Node.js module Package: wnpp Severity: wishlist Owner: Leo Iannacone l...@ubuntu.com * Package name: node-constantinople Version : 2.0.0 Upstream Author : ForbesLindesay * URL : https://github.com/ForbesLindesay/constantinople * License : Expat Programming Lang: JavaScript Description : determine if an expression evaluates to a constant - Node.js module . This module parses a JavaScript expression and determine if it evaluates to a constant, relative to a given scope object. It also checks for syntax errors. . Node.js is a ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749355: parallel: /usr/bin/parallel conflicts with moreutils' parallel
Rogério Brito rbr...@ime.usp.br writes: Given the state of the discussions at the time when I decided that the conflicts was the path of least resistance and that I am sincerely not sure how things have evolved, I would, yes, appreciate your help with the social side of things. BTW, be warned that in current versions of parallel (which I have not yet packaged, but will soon) the compatibility option with moreutils was pending to be removed or is removed already, which would make things even harder. Wouldn't it be possible to let the user decide by himself via `update-alternatives`? The discussion may converge as well on the default symlink, but at least one could use some moreutil's tools in pair with gnu parallel. For example, consider the following use case: $ cat foo.txt | parallel ./bar.sh | sponge foo.txt Which is right now not possible in debian jessie. -- m. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749483: mutt: Conflicting types of generated variable conststrings
Package: mutt Version: 1.5.23-1 Severity: wishlist Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wl,-z,relro -o mutt addrbook.o alias.o attach.o base64.o browser.o buffy.o color.o crypt.o cryptglue.o compress.o commands.o complete.o compose.o copy.o curs_lib.o curs_main.o date.o edit.o enter.o flags.o init.o filter.o from.o getdomain.o group.o handler.o hash.o hdrline.o headers.o help.o hook.o keymap.o main.o mbox.o menu.o mh.o mx.o pager.o parse.o pattern.o postpone.o query.o recvattach.o recvcmd.o rfc822.o rfc1524.o rfc2047.o rfc2231.o rfc3676.o score.o send.o sendlib.o signal.o sort.o status.o system.o thread.o charset.o history.o lib.o sidebar.o muttlib.o editmsg.o mbyte.o url.o ascii.o crypt-mod.o safe_asprintf.o patchlist.o conststrings.o crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o nntp.o newsrc.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o -Limap -limap -lncursesw -lncursesw -Wl,-z,relro -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -ltokyocabinet-L/usr/lib/x86_64-linux-gnu -lgpgme -lassuan -lgpg-error -lidn muttlib.o: In function `mutt_adv_mktemp': /srv/jenkins-slave/workspace/sid-goto-cc-mutt/mutt-1.5.23/obj-x86_64-linux-gnu-patched/../muttlib.c:78: warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp' error: conflicting types for variable cc_version old definition in module main file ../main.c line 165 const char [] new definition in module conststrings file conststrings.c line 1 unsigned char [1347l] Makefile:633: recipe for target 'mutt' failed make[3]: *** [mutt] Error 64 make[3]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-mutt/mutt-1.5.23/obj-x86_64-linux-gnu-patched' Makefile:849: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 If all values actually fit into a positive signed char, the above may be harmless - but it does keep the compiler from reporting potential risks. Thus the declaration here should be changed to const char: http://sources.debian.net/src/mutt/1.5.23-1/txt2c.sh?hl=7#L7 Best, Michael pgpunxTDL7aVj.pgp Description: PGP signature
Bug#745447: povray: FTBFS on kFreeBSD: Unix detected, but flavor not identified
On 2014-05-26 12:54, Graham Inggs wrote: The attached patch allows kFreeBSD to detected as a BSD-style Unix and for the build to proceed. That was a really trivial one (if someone has ever looked into kFreeBSD porting - unlike me) :-) Many thanks! I have just rewritten the git history to remove the non-redistributible bits from the 3.7~beta releases. I was not aware of this issue when I took over the old packaging history and imported the complete release history ... So in case you have a git clone: throw it away and get a new one, many tags and all branch heads have been rewritten. Andreas PS: I'll followup on your other mails later on -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358:
I ran into this problem and the patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358#20 fixed it. Commenting out my NFS mounts worked also, but I couldn't figure out how to get to an editor short of using a rescue CD. (i.e. even in a recovery mode boot, I'd get stuck at Raise network interfaces.) I have br0 in /etc/network/interfaces, I have NetworkManager running for whatever reason, I have by-default NFS mounts in /etc/fstab, and the systemd package is version 204-10.
Bug#749484: linux: Please backport Cubietruck (sunxi) MMC driver/dt
Package: linux Version: 3.15~rc5-1~exp1 Severity: wishlist Dear Maintainer, (I've already discussed this with ijc on IRC, but...) Please consider backporting the MMC / SD driver for the Cubietruck (sunxi) board. This driver is the last missing piece to have a usable kernel for a headless system. The MMC driver has gone through many iterations of review on the linux-arm-kernel mailing list and should now be sitting in maintainers trees waiting for the 3.16 merge window to open. For more information see: https://plus.google.com/107357811086496166266/posts/guhz5rXz8Ef http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/252881.html I've gathered a list of commits I think are the ones you'll need. First two patches in Mike Turquettes clk-next branch: https://git.linaro.org/people/mike.turquette/linux.git/commitdiff/862b728387aef3a3776ad2a261e484aff36c5e67 https://git.linaro.org/people/mike.turquette/linux.git/commitdiff/95713978b0a2929b72933235bb07c0a793e71afa The actual driver is in Ulf Hanssons mmc-next_for_chris_3.16_take3 branch: https://git.linaro.org/people/ulf.hansson/mmc.git/commitdiff/f3f0976c92e0ce5b93bc64d231dce096045a44f7 DeviceTree patches in Maxime Ripards dt-for-3.16 branch (all of these should also be available in the arm-soc tree): https://github.com/mripard/linux/commit/b258b369e8ec4b6f544265aea52bb74476185b12 https://github.com/mripard/linux/commit/b5f86a3a719d2defb6b4144f75bfd92342f01aaa https://github.com/mripard/linux/commit/c0955a86f4af4fef7965bfcd41a9642a3f67486b https://github.com/mripard/linux/commit/d3aed1dfbd2e66ff2eca14897fa141a989a36fb0 https://github.com/mripard/linux/commit/31064bbd6dc3d49fe18f97d81e6ef2cb0358c9c8 https://github.com/mripard/linux/commit/adc54c858499436f049cc7252de617314e7bacf2 https://github.com/mripard/linux/commit/5b753f0e27da2b0a29142be0833784475bc29366 https://github.com/mripard/linux/commit/0ff1ffd3fe86840c80458ea45c2379014c86b660 https://github.com/mripard/linux/commit/dd29ce53b2a48bbb29eaa4a0c86a7a5f36c3d9c0 https://github.com/mripard/linux/commit/11fbedf4dd960db39b40aa59253bb7375df54241 https://github.com/mripard/linux/commit/c621183c203affa526c15e46432c24f31afed997 (Not mmc related, but was part of same review thread and also something we want if we don't already have it...) https://github.com/mripard/linux/commit/3906c0a688587408fa37a411d5e79778039e9dc3 (These additional changes on top of the mailing list thread looks like they are also needed because of final review driver changes...) https://github.com/mripard/linux/commit/e509e4044b1c2d44abead8ccd152c956890bf5dd https://github.com/mripard/linux/commit/a4da476b6c712bce10beddd342111d346a526caa https://github.com/mripard/linux/commit/b4d6c77e3c64c1d1c097db1baa9c12126a4f583d https://github.com/mripard/linux/commit/e6879d190d0ccd02d60b24ff9e49c0e105d135a6 https://github.com/mripard/linux/commit/0ed9eab3030a337d803a0eaefd70fc254a1ae1c8 (and a last minute fixup...) https://github.com/mripard/linux/commit/c5b7261cae14ada86f5823659664fade0bcefa20 Maybe also needed: https://github.com/mripard/linux/commit/5b9c49bea11ac5a02deeda1b737f02c5865243e5 Finally, the sunxi driver(s) needs to be enabled in the config (as apparently the defconfig hasn't been updated according to the G+ post linked to above.) Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743903:
Le mardi, 27 mai 2014, 11.07:15 Aaron Sowry a écrit : Bad commit here: http://anonscm.debian.org/gitweb/?p=collab-maint/lsb.git;a=commitdiff; h=f4ed7f08600d633c3daba9f494997f1c3aed StringIO.StringIO and io.StringIO do not have identical API. Nice catch, thanks. Can you suggest an alternative patch? Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749485: postfwd1: size limits (quotas) ignore number of recipients
Package: postfwd
Version: 1.35-2
Severity: normal
Postfwd1 counts the size of a message only once even if the number
of recipients is 1. For example
May 15 20:21:48 iac postfix/qmgr[5056]: CB2141329:
from=syl...@example.com, size=12229263, nrcpt=69 (queue active)
will add only 12229263 for a rule like
id=QUOTA ; action=size(sasl_username/2/86400/WARN ...)
It seems that in /usr/sbin/postfwd1 in %postfwd_actions at the line
my($rcount) = ( ($mycmd =~ /^size/) ? $request{size} :
(($mycmd =~ /^rcpt/) ? $request{recipient_count} : 1 ) );
recipient_count is ignored, i.e. it is always assumed to be 1 for
($mycmd =~ /^size/).
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages postfwd depends on:
ii adduser 3.113+nmu3
ii libnet-dns-perl 0.66-2+b2
ii libnet-server-perl 2.006-1+deb7u1
ii perl5.14.2-21+deb7u1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732690: acpi-support: Adding support for i3lock
Thus wrote Andre-Patrick Bubel (deb...@andre-bubel.de): I'm sorry I couldn't include a patch, as I couldn't figure out how to create one for a patch file. simple patch attached to detect and run i3lock Regards, Martin --- screenblank.orig 2014-05-27 11:23:31.418026452 +0200 +++ screenblank 2014-05-25 13:00:25.859910337 +0200 @@ -23,6 +23,8 @@ su $XUSER -s /bin/sh -c /usr/bin/xlock -mode blank elif [ -x /usr/bin/xtrlock ]; then su $XUSER -s /bin/sh -c /usr/bin/xtrlock + elif [ -x /usr/bin/i3lock ]; then + su $XUSER -s /bin/sh -c /usr/bin/i3lock fi fi
Bug#749486: fortunes-es: Error in attributed quote
Package: fortunes-es Version: 1.32 Severity: normal There is an error in the attribution of a quote in the package. In the sabiduria.fortunes file the quote La superstición trae mala suerte is incorrectly attributed to Umberto Eco. This quote appears in his novel Foucault's Pendulum (an opening quote) but it should be attributed instead to Raymond Smullyan. (1919-) Matemático norteamericano. Eco himself attributes it to Smullyan. The problem seems to come from the fact that the quote is included in his novel. The specific page with the quote can be seen here: http://books.google.es/books?id=r0XtPZleMKwClpg=PT3hl=es; pg=PT3#v=onepageqf=false Regards Javier
Bug#739911: RFS: gtk-theme-switch/2.1.0-4
dget -x http://mentors.debian.net/debian/pool/main/g/gtk-theme-switch/gtk-theme-switch_2.1.0-4.dsc please do not change upstream tarball yours: 1658aff453319536f20019fc0fe1f74e 18539 the one in the archive (which matches upstream): a9e7e62701cd4fba4d277dc210cd4317 18914 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749330: systemd: The sysctl service is not started correctly at boot
Am 26.05.2014 20:50, schrieb Patrick Häcker: I guess the value dirty_writeback_centisecs defaults to 500. Other values defined via sysctl have their (suspected) default value, too. Which other values? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#749487: ginkgocadx: Please update to use wxwidgets3.0
Source: ginkgocadx Version: 3.6.0.1228.33+dfsg-1 Severity: normal Tags: patch User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8. Upstream's changelog.txt indicates that 3.6.1 is compatible with wxwidgets3.0: Version 3.6.1 (2014-02-27) --- * UI migrated to wxWidgets 3.0.0 all forms has changed Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749384: gutenprint: No Epson Stylus Photo R220 or R200 drivers
Control: tags -1 +confirmed +pending Le lundi, 26 mai 2014, 17.18:27 Cameron Norman a écrit : Package: printer-driver-gutenprint Version: 5.2.10~pre2-2 The gutenprint website says that they still support these two models, but the package only ships drivers for the R240 and up. Is this a regression, or purposeful? I think you're now only seeing the printer-driver-escpr driver entries: gutenprint 5.2.10~pre* versions failed to propose any available driver: /usr/lib/cups/driver/gutenprint.5.2 list ^ That should give a list of more than 2000 printer entries. I have a fix pending that I'll upload with the final version of 5.2.10. Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728287: ITA: iwatch -- realtime filesystem monitoring program using inotify
Hi all, What is the current iwatch situation? I use iwatch in several scenaries and I can adopt it immediately. I like iwatch and I taught about it in my Brazilian book about network traffic analysis. Thanks in advanced. Regards, Eriberto pgpV3RPRyIDxr.pgp Description: PGP signature
Bug#749366: squeeze-pu: package suds/0.3.9-1+deb6u2 Bug#749073
* Adam D. Barratt: Bug#749366: squeeze-pu: package suds/0.3.9-1+deb6u2 Bug#749073 (Mon, 26 May 2014 19:57:33 +0100): Control: tags -1 + confirmed On Mon, 2014-05-26 at 18:08 +0200, Mathias Behrle wrote: the original fix for CVE-2013-2217 was missing a proper cleanup of the cache directories in tmp (#749073), which can lead to saturation of the subdirectory limit (~32000 on ext3). I would like to upload suds_0.3.9-1+deb6u2 with this patch backported from https://bitbucket.org/jurko/suds/issue/15/insecure-temporary-directory-use https://bitbucket.org/jurko/suds/commits/3126ac3a406c37f9982f01ad0ca4ed42cf9a47cb https://bitbucket.org/jurko/suds/commits/aee4b2f0318f4b4545a1da826149edaa2c047460 Please go ahead; thanks. Uploaded by sponsor Raphael Hertzog. BTW: Do I need to confirm this? ftpmaster already sent 'suds_0.3.9-1+deb6u2_amd64.changes ACCEPTED into oldstable-proposed-updates-oldstable-new' Cheers -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 signature.asc Description: PGP signature
Bug#749368: wheezy-pu: package suds/0.4.1-5+deb7u1 Bugs #749073 + #714340
* Adam D. Barratt: Bug#749368: wheezy-pu: package suds/0.4.1-5+deb7u1 Bugs #749073 + #714340 (Mon, 26 May 2014 19:55:53 +0100): Control: tags -1 + confirmed On Mon, 2014-05-26 at 18:14 +0200, Mathias Behrle wrote: somehow the original fix for CVE-2013-2217 never got into wheezy. This patch fixes the CVE. Please go ahead. Uploaded by sponsor Raphael Hertzog. Cheers, Mathias -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 signature.asc Description: PGP signature
Bug#711833: Preparing new package upload
On Tue, May 27, 2014 at 09:24:20AM +0200, Yoann Gauthier wrote: Hello, I propose to write a simple man page in order to have a clean package. Regards, Yoann If you want to write one good :) After uploading to mentors I recieved some other warnings. I will be looking at them later. I am currently using a different machine and do not have the warnings here, but will add them in a later email. 2014-05-26 20:35 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no: Hei, I fixed all the errors reported by lintian, sorry for not giving notice that I was working on them. As far as I can see the remaining message from lintian is: W: postr: binary-without-manpage usr/bin/postr I have not written a manpage before so the warning is not that important to me. I will publish the package soon, after cleaning up the changelog. I have set PAPT as the maintainer and both of us as uploaders. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749330: systemd: The sysctl service is not started correctly at boot
Am 26.05.2014 20:50, schrieb Patrick Häcker: I guess the value dirty_writeback_centisecs defaults to 500. Other values defined via sysctl have their (suspected) default value, too, after boot and only change to the desired value after restarting the service manually as described. Thus, I guess that the sysctl service is not started correctly, although I cannot explain why systemctl should state otherwise (active, success) in this case. I suspect that systemd-sysctl set's the value correctly during boot, but it is later reset by some other component. Could you try the following: (as root) mkdir /etc/systemd/system/systemd-sysctl.service.d/ echo -e [Service]\nExecStartPost=/sbin/sysctl vm.dirty_writeback_centisecs /etc/systemd/system/systemd-sysctl.service.d/debug.conf Then reboot and check the journal. The ExecStartPost command will dump the sysctl value after it has been set by systemd-sysctl: journalctl -b | grep sysctl If that turns up the correct vm.dirty_writeback_centisecs value, you need to find the component which is responsible for changing it *after* systemd-sysctl.service has run. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#748770: diff NMU for 0.6.1-2.2
Hi Anton, Thanks very much for the repair. The package can be uploaded without delay. Again, thanks for the effort. Many greetings, Gerber On 05/26/2014 08:55 PM, Anton Gladky wrote: tags 748770 +pending +patch thanks Dear maintainer, I have prepared an NMU (versioned as 0.6.1-2.2) and uploaded to DELAYED/5. Please fell free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best regards Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749451: libgtk-3-dev introduces dependency on C++ library
On 27/05/14 01:43, Jamin Hoggard wrote: Details: libgtk-3-dev depends on libglib2.0-dev, which depends on libpcre3-dev. However, libpcre3-dev depends on libpcrecpp0, which introduces dependencies on C++ libraries (libstdc++). These libraries must be installed during compilation due to the way libpcre is packaged, but do not introduce extra dependencies for applications compiled against Gtk3 (for instance, gnome-terminal uses Gtk3 but does not depend on libpcrecpp0, even indirectly). So, the impact is developers' systems have slightly more libraries installed. The build-essential metapackage depends on a C++ compiler (and hence libstdc++) anyway, so this has basically no effect on the build-dependencies of any Debian package (libpcrecpp0 itself is small). Is there a concrete situation in which it is a practical problem that a developer's system must have libpcrecpp0 and libstdc++? If there is a real practical problem, splitting libpcre3-dev into C and C++ parts is likely to be a better solution. However, libstdc++ is used by build-essential and apt, so this seems likely to be mostly a theoretical concern: in practice, Debian systems in general, and developer systems in particular, are going to have it. According to the documentation at https://developer.gnome.org/glib/stable/glib-building.html GLib can, and is indeed recommended to, be compiled using GLib's internal version of PCRE (i.e. using the configure script option --with-pcre=internal). Debian policy is to avoid embedded code copies unless there is a compelling technical reason to use them, and ensure that the system libpcre remains compatible with GLib's usage. This ensures that if there is a security vulnerability in PCRE (which has happened in the past), patching PCRE is sufficient to fix that vulnerability. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749488: plplot: Please update to use wxwidgets3.0
Source: plplot Version: 5.9.9-5 Severity: normal User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8. I've been unable to test rebuilding the current package with wxwidgets3.0 as it FTBFS (as noted in other bugs), but given the age of 5.9.9, it's probably not compatible with wx3.0. However, upstream's release notes suggest that 5.10.0 is: http://sourceforge.net/projects/plplot/files/plplot/5.10.0%20Source/ Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
Hi Jim, On 27.05.2014 07:18, Jim Barber wrote: The ClamAV daemon hung again after rolling back to 0.98.3. You could try it with 0.98.1, but I'm not sure if that would help. It went longer than a day this time, but still less than 2 days. Here's the havp log (with URL removed). 25/05/2014 08:51:59 === Starting HAVP Version: 0.92 25/05/2014 08:51:59 Running as user: havp, group: havp 25/05/2014 08:51:59 Use parent proxy: localhost:3130 25/05/2014 08:51:59 --- Initializing Clamd Socket Scanner 25/05/2014 08:51:59 Clamd Socket Scanner passed EICAR virus test (Eicar-Test-Signature) 25/05/2014 08:51:59 --- All scanners initialized 25/05/2014 08:51:59 Process ID: 23108 26/05/2014 23:20:04 Error: Some scanner has timed out! (lasturl: url removed) The complete ClamAV log from when I started it after backing out to the older version, to when I restarted it when I noticed it was hung is as follows: Sun May 25 08:51:01 2014 - +++ Started at Sun May 25 08:51:01 2014 [...] Mon May 26 15:59:42 2014 - SelfCheck: Database status OK. Mon May 26 16:52:08 2014 - Restarting on-access scan Mon May 26 16:52:09 2014 - Reading databases from /var/lib/clamav Mon May 26 16:52:13 2014 - Database correctly reloaded (3387113 signatures) Mon May 26 16:52:13 2014 - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted Mon May 26 16:52:13 2014 - ScanOnAccess: clamd must be started by root Mon May 26 17:52:13 2014 - SelfCheck: Database status OK. Mon May 26 18:52:13 2014 - SelfCheck: Database status OK. Mon May 26 19:52:13 2014 - SelfCheck: Database status OK. Mon May 26 21:52:05 2014 - SelfCheck: Database status OK. Mon May 26 22:52:19 2014 - SelfCheck: Database modification detected. Forcing reload. Mon May 26 22:52:19 2014 - Restarting on-access scan Mon May 26 22:52:19 2014 - Reading databases from /var/lib/clamav Mon May 26 22:52:23 2014 - Database correctly reloaded (3387525 signatures) Mon May 26 22:52:23 2014 - Restarting on-access scan Tue May 27 06:39:04 2014 - +++ Started at Tue May 27 06:39:04 2014 It looks like it hung on 'Restarting on-access scan'. It didn't follow up with the following messages that usually happen seconds after: - Reading databases from /var/lib/clamav - Database correctly reloaded ([0-9]+ signatures) I think the problem here is that there is a second 'Restarting on-access scan' message only 4 seconds after another one and without the usual 'ERROR: ScanOnAccess: fanotify_init [...]' between them. This looks as if the reload is started again, while the previous reload is not yet finished. Probably this should not happen, as it seems to cause a deadlock. I used to run this version of the ClamAV daemon without issue. So maybe it is something to do with getting freshclam updates working again. I went back through my freshclam logs and it was fine up until the evening of Thu Apr 24th where I started getting the freshclam update error. Prior to that I wasn't getting hangs either though. Actually, when I ran 'dpkg-reconfigure clamav-freshclam' to fix the freshclam update errors, one of the questions asked was: Should clamd be notified after updates? I think this may have been 'No' before as I thought that was strange I would leave it set that way and I selected 'Yes'. So it is likely to be this that is now causing my hangs I guess. This may be, as the hang happens precisely when clamd itself notices a 'Database modification' and triggers a reload, likely just before freshclam triggers a reload. Nonetheless I think this is a bug in clamd, as it should handle this gracefully. Looking back over my past logs, the 'Restarting on-access scan' message used to happen infrequently: Fri Apr 25 00:01:13 2014 - Restarting on-access scan Tue Apr 29 13:41:24 2014 - Restarting on-access scan Mon May 5 00:07:08 2014 - Restarting on-access scan Thu May 8 19:46:58 2014 - Restarting on-access scan Sun May 11 18:47:52 2014 - Restarting on-access scan Fri May 16 17:48:07 2014 - Restarting on-access scan Mon May 19 23:15:10 2014 - Restarting on-access scan Then after the reconfigure of clamav-freshclam it is regular: Tue May 20 23:49:57 2014 - Restarting on-access scan Wed May 21 00:50:01 2014 - Restarting on-access scan Wed May 21 01:50:07 2014 - Restarting on-access scan Wed May 21 01:50:12 2014 - Restarting on-access scan Wed May 21 22:44:12 2014 - Restarting on-access scan Wed May 21 23:44:06 2014 - Restarting on-access scan Thu May 22 04:44:15 2014 - Restarting on-access scan Thu May 22 04:44:19 2014 - Restarting on-access scan Thu May 22 06:44:23 2014 - Restarting on-access scan Thu May 22 06:44:28 2014 - Restarting on-access scan Thu May 22 18:03:34 2014 - Restarting on-access scan Thu May 22 18:03:38 2014 - Restarting on-access scan Thu
Bug#749489: pycuda: incorrect Vcs-Browser URL
Source: pycuda Version: 2013.1.1+git20140310-1 Severity: normal Tags: patch Dear Maintainer The patch below fixes the incorrect Vcs-Browser URL in debian/control. Regards Graham --- a/debian/control +++ b/debian/control @@ -25,7 +25,7 @@ X-Python-Version: = 2.5 X-Python3-Version: = 3.3 Homepage: http://mathema.tician.de/software/pycuda Vcs-Git: git://anonscm.debian.org/collab-maint/python-pycuda.git -Vcs-Browser: http://anonscm.debian.org/git/collab-maint/python-pycuda.git +Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/python-pycuda.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747697: [RFR] templates://debian-security-support/{debian-security-support.templates}
Christoph Biedl wrote: Justin B Rye wrote... [...] CHECK-SUPPORT-STATUS(1) === NAME check-support-status - check installed packages for ended security support (Should that perhaps be reduced security support?) Remainder of an early development phase when there was only the ended check. So it should be rather check installed packages for ended or reduced security support. But | check-support-status - check installed packages for ended or reduced security support | 11+2+3+4+5+6+7+8+ this should fit into 80 characters if possible. I was thinking of reduced as a cover-term for ended or limited, but it doesn't really work. We could I suppose invert the implied return value of the check and say just: check-support-status - check installed packages for security support [...] So your proposal is OK, except the optional attribute is missing. I'd write: | * the rest (optional): details, and/or a URL for further information. Yes, I suppose that's the solution. BUGS (More of a wontfix LIMITATIONS, really) Yes, it's just BUGS is a well-established name for that section. Using mixed distribution like half-stable, half-testing is not supported. Mixed distributions (or perhaps a mixed distribution). I tend to something like | Installations with mixed distributions like half-stable, half-testing | are not supported. but should leave the last word to you. Yes, that's grammatical. Of course, it's the subtly odd Debian use of distribution to mean OS development branch, but it's decades too late to worry about that one. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747697: [RFR] templates://debian-security-support/{debian-security-support.templates}
Christoph Biedl wrote: Justin B Rye wrote... Talking about the regular security maintenance life cycle worked in the templates, but here it's not clear what life cycle you're talking about - it might be the software life cycle (from proof-of-concept to mature project to death-by-bitrot) of the packages. And besides, once we start setting things up to allow an oldstable-LTS with incomplete security coverage, surely that *is* the planned security maintenance life cycle? This *is* mostly about squeeze-lts actually. So for that one, the life cycle will end in spring 2016. Should we add the Debian word to the regular security maintenance life cycle to clarify? The trouble is, once this package becomes part of the standard security support system, the claim that maintaining security support is not feasible for the planned life cycle becomes confusing. Does that mean even after taking this package into account? Also, this use of life cycle to mean support period strikes me as an unhelpful piece of IT industry jargon. Saying that Windows XP has a ten year life cycle ought to imply that homes and businesses would be full of baby Windows XPs just now... Still, I don't know why I'm still talking about this when your amended version of my patch with restored Debian branding looks okay. [...] Upstream has no control here. It's the Debian security team who decides to end support, but of course upstream's moves have some influence on that. If such a decision is made, the team will also release a new version of debian-security-support with an updated list. The part that still hasn't been made absolutely explicit is: is there a security announcement for it, and does the new version of d-s-s go into security.debian.org? That would make sense, but if so you'd need to update https://www.debian.org/security/faq#policy;... -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748514: RM: haskell-diagrams-lib [armel armhf mips mipsel s390x sparc] -- ROM; Requires TemplateHaskell
Control: tag -1 - moreinfo Hi, Am Montag, den 26.05.2014, 18:15 -0400 schrieb Scott Kitterman: On Monday, May 26, 2014 17:41:16 Joachim Breitner wrote: Dear FTP-Team, may I nudge you about #748514? It seems that this is the remaining outstanding issue that prevents a large number of Haskell packages to migrate to testing. There are reverse-depends that need tending to as well. Please remove the moreinfo tag once they've been addressed. as I mentioned in the original bug report: These rev-deps need to be removed as well. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#749471: [Pkg-haskell-maintainers] Bug#749471: ghc: changeWorkingDirectory systematically fails
Hi, Am Dienstag, den 27.05.2014, 10:02 +0200 schrieb Boris Daix: Package: ghc Version: 7.6.3-10 Severity: normal Dear Maintainer, :cd'ind in GHCi is not possible anymore: bdaix@nephtys:~$ pwd /home/bdaix bdaix@nephtys:~$ ghci GHCi, version 7.6.3: http://www.haskell.org/ghc/ :? for help Loading package ghc-prim ... linking ... done. Loading package integer-gmp ... linking ... done. Loading package base ... linking ... done. Prelude :cd .. *** Exception: ..: changeWorkingDirectory: does not exist (No such file or directory) Prelude works here, just drop the quotes: Prelude :!pwd /home/jojo Prelude :cd .. Prelude :!pwd /home Prelude (please close the bug if you agree) Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#430770: please upgrade to version 1.8 of libmpeg3-dev as the current version (1.5.4) is too old
[Petter Reinholdtsen]
Are you still maintaining this package? Last maintainer upload was
in 2006.
To try to help getting a new version into Debian, I created a git
repository for the package and made it available as
URL: http://anonscm.debian.org/gitweb/?p=collab-maint/libmpeg3.git;a=summary .
I fetched old upstream tarballs from version 1.5.0 to version 1.8, and
debian versions from version 1.5.4-4 to version 1.5.4-5.1, and
imported these using git-import-orig and git-import-dsc. I've tried
my best to keep the fixes and changes that was already present in
versoin 1.5.4-5.1.
This is the changelog for the source in git. What should we do now?
NMU? Handover? You do an upload based on the git version? I'll do
an NMU if I do not hear anything.
libmpeg3 (1.8-0.1) UNRELEASED; urgency=low
* Update to debhelper 9 support.
* Move source patches to debian/patches/ and package format to 3.0
(quilt).
* Update upstream source to version 1.8 (Closes: #430770).
- Split relevant parts of the patch used in 1.5.4-5.1 info new
patches alpha-largefile.patch and debian-build-rules.patch
- Drop patches to fix bugs #287422 and #729275, as these problems
are fixed differently upstream.
- Change shared library major number from 1 to 2, as the new library have
a new API and ABI.
- No longer have typo in Makefile (Closes: #374504).
* Add patch prototype-free.patch to make sure stdlib.h is included
before free() is used.
* Change encoding of debian/copyright to UTF-8.
* Update standards-version from 3.6.2.2 to 3.9.5.
* Add missing dependency on ${misc:Depends}. Thank you lintian.
* Adjust copyright file to document upstream copyright 2003-2008.
* Change debian/rules to use dh_prep instead of the obsolete
dh_clean -k. Thank you, lintian.
* Enable hardening flags during build and linking.
* New patch fix-format-security-error.patch to make code buildable
with hardening enabled.
* Add homepage URL to control file (Closes: #749469).
* Reorder shared library linking rule to work with the --as-needed
linker flag (Closes: #63). Patch from Sebastian Carneiro and
Ubuntu.
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749490: caja: please make selinux build-dep [linux-any]
Package: caja Version: 1.8.1-1 Severity: important Tags: patch User: debian-...@lists.debian.org Usertags: kfreebsd Hi, Please limit caja's build-dep of libselinux1-dev to [linux-any], because it can be built fine on at least kfreebsd without it. Thanks! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- caja-1.8.1/debian/control.orig 2014-04-05 22:31:11.0 +0100 +++ caja-1.8.1/debian/control 2014-05-27 11:46:05.952689000 +0100 @@ -20,7 +20,7 @@ gtk-doc-tools, libxt-dev, libx11-dev, - libselinux1-dev, + libselinux1-dev [linux-any], libxrender-dev, libxext-dev, x11proto-core-dev,
Bug#745988: gthumb window doesn't have a title bar (NoTitle is Yes in fvwm)
Control: severity -1 important On 2014-04-27 00:22:25 +0200, Vincent Lefevre wrote: I've reverted to gthumb 3:3.2.6-1+b1, and this problem doesn't occur with this version. I've done again some search with Google, and found http://www.webupd8.org/2014/05/install-gthumb-332-in-ubuntu-gnome-1404.html (published on 2014-05-19), which says: Ubuntu 14.04 had gThumb 3.3.1 in its official repositories at some point but because starting with version 3.3.0, the application uses header bars (also known as client side decorations) and they don't work properly under Unity, gThumb was downgraded to version 3.2.7. and If you try to use it under other desktop environments, you'll encounter various visual glitches This is about Ubuntu/Unity, but there are the same problems with Debian for non-GNOME users. So basically, the changes for GNOME made gThumb partly incompatible with other desktop environments. Note that gThumb is still described as a generic application: Description: image viewer and browser not a GNOME-only application. There are other problems related to that: once gThumb has been put below other windows, it remains below them since the window manager operations set up by the user are no longer available (in my case, a left click on the title bar raises the window, but this doesn't work with gThumb's header bars). I'm increasing the severity since it badly interferes with the environment and this makes gThumb hardly usable. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732920: When this patch can be adopted by Testing?
On Mon, May 26, 2014 at 10:14:21PM +0800, Bai Shi wrote: I have same question here. I has been 3 months after the patch submitted.A I've looked into it again. Bug #743758 was blocking the transistion because the buildd didn't work for mips (which then just worked by itself) and powerpc (which didnt fix itself). I've put in a fix now that should make the powerpc happy by just ignoring one of the tests. No doubt one of the buildds will complain about one of the other things randomly, but I won't know what in advance. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694494: [Pkg-alsa-devel] Bug#694494: libasound2-plugins: Installing i386 version on amd64 causes JACK 1 removal
On Δευ, 2014-05-26 at 19:36 +0200, Elimar Riesebieter wrote: * Apostolos a...@freemail.gr [2014-05-25 21:29 +0300]: Package: libasound2-plugins Version: 1.0.27-2.1 Followup-For: Bug #694494 Manually installing libjack0:i386 before instalilng libasound2-plugins:i386 does work as expected. unfortunatelly this does not work on Jessie $ sudo apt-get install libjack0:i386 Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: Did you do this? I did!!! and apt-get wanted to remove all i386 packages!!! The following packages have unmet dependencies: libjack0 : Breaks: libjack0:i386 (!= 1:0.124.1+20140122git5013bed0-2+b1) but 1:0.124.1+20140122git5013bed0-2 is to be installed libjack0:i386 : Breaks: libjack0 (!= 1:0.124.1+20140122git5013bed0-2) but 1:0.124.1+20140122git5013bed0-2+b1 is to be installed Elimar I don't know if someone tweaked any dependencies but today it worked like a charm thanks please close!! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745988: gthumb window doesn't have a title bar (NoTitle is Yes in fvwm)
Control: retitle -1 gthumb 3.3.x uses header bars, breaking compatibility with non-GNOME environments The bug title had to be changed too... FYI, here's what https://wiki.gnome.org/Initiatives/GnomeGoals/HeaderBars says: Since 3.10, many applications have switched to use header bars rather than the traditional combination of titlebar, toolbar and menu bar. and This GNOME goal aims to make header bar usage consistant across GNOME applications. This unconditional use of header bars is a clear break of compatibility with non-GNOME environments and is only focused to GNOME. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745088: Java 8 incompatibility fixed
I have released a new version of caveconverter which passes all regressions on Java 6,7 and 8. Build 20140520 just needs packaging to replace the current build. Footleg
Bug#749392: miniupnd: Conflicting types of getifaddr
It has been fixed uptream : https://github.com/miniupnp/miniupnp/commit/b9daf5cc27aa180b4d8fde6e32043f01125ae161 it should be included in miniupnpd-1.8.20131216.tar.gz http://miniupnp.free.fr/files/download.php?file=miniupnpd-1.8.20131216.tar.gz Regards, Thomas Bernard Le 26/05/2014 20:06, Michael Tautschnig a écrit : Package: miniupnpd Version: 1.8.20130730-2 Severity: wishlist Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] cc -Wl,-z,relrotestupnpdescgen.o upnpdescgen.o -o testupnpdescgen error: conflicting function declarations getifaddr old definition in module testupnpdescgen file testupnpdescgen.c line 37 signed int (const char *ifname, char *buf, signed int len) new definition in module upnpdescgen file getifaddr.h line 18 signed int (const char *, char *, signed int, struct in_addr *, struct in_addr *) builtin: recipe for target 'testupnpdescgen' failed make[2]: *** [testupnpdescgen] Error 64 As getifaddr supposedly takes 5 arguments http://sources.debian.net/src/miniupnpd/1.8.20130730-2/getifaddr.c?hl=29#L29 the stub code should likely be fixed to take the same, even though these might be unused. Best, Michael
Bug#749491: libpython2.7-dev hmac.py: cannot import name _compare_digest
Package: libpython2.7-dev Version: 2.7.7~rc1-1 Severity: normal Dear Maintainer, Any package that import hmac fail with: File /usr/lib/python2.7/hmac.py, line 8, in module from operator import _compare_digest as compare_digest ImportError: cannot import name _compare_digest It seems the error is introduced by python2.7 (2.7.7~rc1-1) with these changes in upstream [1] [1] http://bugs.python.org/issue21306 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (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 libpython2.7-dev depends on: ii libexpat1-dev2.1.0-5 ii libpython2.7 2.7.7~rc1-1 ii libpython2.7-stdlib 2.7.7~rc1-1 ii multiarch-support2.18-7 Versions of packages libpython2.7-dev recommends: ii libc6-dev [libc-dev] 2.18-7 libpython2.7-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745670: lxc.service systemd exec paths do not exist
Package: lxc Version: 1.0.3-1 Followup-For: Bug #745670 Control: tags -1 patch The issue still presents in 1.0.3-1 due to wrong patch and sh compatibility. The patches can solve the issues. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 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 lxc depends on: ii libapparmor1 2.8.0-5+b1 ii libc6 2.18-7 ii libcap21:2.22-1.2 ii libseccomp22.1.1-1 ii libselinux12.3-1 ii multiarch-support 2.18-7 Versions of packages lxc recommends: ii lua5.2 5.2.3-1 ii python3 3.3.4-1 ii rsync3.1.0-3 Versions of packages lxc suggests: pn lxc-stuff none -- no debconf information -- ChangZhuo Chen (陳昌倬) czc...@gmail.com http://czchen.info/ Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D From c1a0cc1b845ed7d48bb08fbd72b9e5ca341e9456 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?ChangZhuo=20Chen=20=28=E9=99=B3=E6=98=8C=E5=80=AC=29?= czc...@gmail.com Date: Tue, 20 May 2014 23:44:37 +0800 Subject: [PATCH 1/2] Fix lxc-devsetup path --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index f53f915..454a28a 100755 --- a/debian/rules +++ b/debian/rules @@ -34,7 +34,7 @@ override_dh_auto_install: mv debian/tmp/usr/bin/lxc-test-* debian/lxc-dev/usr/bin # fix systemd service - sed -i -e s|/usr/libexec/lxc/lxc-devsetup|/usr/lib/$(DEB_HOST_MULTIARCH)/lxc| \ + sed -i -e s|/usr/libexec/lxc/lxc-devsetup|/usr/lib/$(DEB_HOST_MULTIARCH)/lxc/lxc-devsetup| \ -e s|/usr/libexec/lxc/lxc-startup start|/usr/bin/lxc-autostart| \ -e s|/usr/libexec/lxc/lxc-startup stop|/usr/bin/lxc-autostart --shutdown| \ debian/tmp/lib/systemd/system/lxc.service -- 2.0.0.rc4 From f8f86658e77ef109f24db1b942972ea05063cc4a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?ChangZhuo=20Chen=20=28=E9=99=B3=E6=98=8C=E5=80=AC=29?= czc...@gmail.com Date: Tue, 20 May 2014 23:48:36 +0800 Subject: [PATCH 2/2] Fix sh compatibility --- debian/patches/0009-sh-compatibility.patch | 23 +++ debian/patches/series | 1 + 2 files changed, 24 insertions(+) create mode 100644 debian/patches/0009-sh-compatibility.patch diff --git a/debian/patches/0009-sh-compatibility.patch b/debian/patches/0009-sh-compatibility.patch new file mode 100644 index 000..8695a61 --- /dev/null +++ b/debian/patches/0009-sh-compatibility.patch @@ -0,0 +1,23 @@ +Description: Fix for sh compatibility +--- +Origin: upstream, https://github.com/lxc/lxc/commit/e702123afe1a318c41cb7eb96223ae6ba5d21751 +--- lxc-1.0.3.orig/config/init/systemd/lxc-devsetup lxc-1.0.3/config/init/systemd/lxc-devsetup +@@ -2,7 +2,7 @@ + + # lxc.devsetup - Setup host /dev for container /dev subdirectories. + +-if [[ ! -d /dev/.lxc ]] ++if [ ! -d /dev/.lxc ] + then + echo Creating /dev/.lxc + mkdir /dev/.lxc +@@ -17,7 +17,7 @@ else + mount -t tmpfs tmpfs /dev/.lxc + fi + +-if [[ ! -d /dev/.lxc/user ]] ++if [ ! -d /dev/.lxc/user ] + then + echo Creating /dev/.lxc/user + mkdir /dev/.lxc/user diff --git a/debian/patches/series b/debian/patches/series index 95fd90e..fc28e35 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -6,3 +6,4 @@ 0006-lxc-sigint.patch 0007-lxc-patch-shebang.patch 0008-debian-config.patch +0009-sh-compatibility.patch -- 2.0.0.rc4 signature.asc Description: Digital signature
Bug#745670: lxc.service systemd exec paths do not exist
Package: lxc Version: 1.0.3-1 Followup-For: Bug #745670 Control: tags -1 patch Hi, The problem still presents in 1.0.3-1 due to wrong path and sh compatibility. The attached patches can solve the issues. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 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 lxc depends on: ii libapparmor1 2.8.0-5+b1 ii libc6 2.18-7 ii libcap21:2.22-1.2 ii libseccomp22.1.1-1 ii libselinux12.3-1 ii multiarch-support 2.18-7 Versions of packages lxc recommends: ii lua5.2 5.2.3-1 ii python3 3.3.4-1 ii rsync3.1.0-3 Versions of packages lxc suggests: pn lxc-stuff none -- no debconf information -- ChangZhuo Chen (陳昌倬) czc...@gmail.com http://czchen.info/ Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D From c1a0cc1b845ed7d48bb08fbd72b9e5ca341e9456 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?ChangZhuo=20Chen=20=28=E9=99=B3=E6=98=8C=E5=80=AC=29?= czc...@gmail.com Date: Tue, 20 May 2014 23:44:37 +0800 Subject: [PATCH 1/2] Fix lxc-devsetup path --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index f53f915..454a28a 100755 --- a/debian/rules +++ b/debian/rules @@ -34,7 +34,7 @@ override_dh_auto_install: mv debian/tmp/usr/bin/lxc-test-* debian/lxc-dev/usr/bin # fix systemd service - sed -i -e s|/usr/libexec/lxc/lxc-devsetup|/usr/lib/$(DEB_HOST_MULTIARCH)/lxc| \ + sed -i -e s|/usr/libexec/lxc/lxc-devsetup|/usr/lib/$(DEB_HOST_MULTIARCH)/lxc/lxc-devsetup| \ -e s|/usr/libexec/lxc/lxc-startup start|/usr/bin/lxc-autostart| \ -e s|/usr/libexec/lxc/lxc-startup stop|/usr/bin/lxc-autostart --shutdown| \ debian/tmp/lib/systemd/system/lxc.service -- 2.0.0.rc4 From f8f86658e77ef109f24db1b942972ea05063cc4a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?ChangZhuo=20Chen=20=28=E9=99=B3=E6=98=8C=E5=80=AC=29?= czc...@gmail.com Date: Tue, 20 May 2014 23:48:36 +0800 Subject: [PATCH 2/2] Fix sh compatibility --- debian/patches/0009-sh-compatibility.patch | 23 +++ debian/patches/series | 1 + 2 files changed, 24 insertions(+) create mode 100644 debian/patches/0009-sh-compatibility.patch diff --git a/debian/patches/0009-sh-compatibility.patch b/debian/patches/0009-sh-compatibility.patch new file mode 100644 index 000..8695a61 --- /dev/null +++ b/debian/patches/0009-sh-compatibility.patch @@ -0,0 +1,23 @@ +Description: Fix for sh compatibility +--- +Origin: upstream, https://github.com/lxc/lxc/commit/e702123afe1a318c41cb7eb96223ae6ba5d21751 +--- lxc-1.0.3.orig/config/init/systemd/lxc-devsetup lxc-1.0.3/config/init/systemd/lxc-devsetup +@@ -2,7 +2,7 @@ + + # lxc.devsetup - Setup host /dev for container /dev subdirectories. + +-if [[ ! -d /dev/.lxc ]] ++if [ ! -d /dev/.lxc ] + then + echo Creating /dev/.lxc + mkdir /dev/.lxc +@@ -17,7 +17,7 @@ else + mount -t tmpfs tmpfs /dev/.lxc + fi + +-if [[ ! -d /dev/.lxc/user ]] ++if [ ! -d /dev/.lxc/user ] + then + echo Creating /dev/.lxc/user + mkdir /dev/.lxc/user diff --git a/debian/patches/series b/debian/patches/series index 95fd90e..fc28e35 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -6,3 +6,4 @@ 0006-lxc-sigint.patch 0007-lxc-patch-shebang.patch 0008-debian-config.patch +0009-sh-compatibility.patch -- 2.0.0.rc4 signature.asc Description: Digital signature
Bug#745088: Java 8 incompatibility fixed
+++ Footleg [2014-05-27 07:19 -0400]: I have released a new version of caveconverter which passes all regressions on Java 6,7 and 8. Excellent - thanks for that. Build 20140520 just needs packaging to replace the current build. Which has a dependency on packaging that science library. How invasive is backporting the java 8 fixes to the existing version of caveconverter? (just wondering which of these is less work). I have no cycles for caveconverter right now so I'm not sure when I'll get to either of these. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747174: NMU debdiff for cmake_2.8.12.1-1.4
Hello Modestas,
Please find below the NMU debdiff for cmake_2.8.12.1-1.4. It adds
support for mips64 mips64el mipsn32 mipsn32el in Modules/FindJNI.cmake.
Regards,
Aníbal
--
anibal.monsalvesala...@imgtec.com
debdiff cmake_2.8.12.1-1.3.dsc cmake_2.8.12.1-1.4.dsc
diff -Nru cmake-2.8.12.1/debian/changelog cmake-2.8.12.1/debian/changelog
--- cmake-2.8.12.1/debian/changelog 2014-05-23 09:26:23.0 +0100
+++ cmake-2.8.12.1/debian/changelog 2014-05-26 12:36:01.0 +0100
@@ -1,3 +1,14 @@
+cmake (2.8.12.1-1.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add support for mips64 mips64el mipsn32 mipsn32el in
+Modules/FindJNI.cmake.
+Add FindJNI.cmake.mips.patch.
+Patch by Yunqiang Su.
+Closes: #747174.
+
+ -- Anibal Monsalve Salazar ani...@debian.org Mon, 26 May 2014 12:34:45
+0100
+
cmake (2.8.12.1-1.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru cmake-2.8.12.1/debian/patches/FindJNI.cmake.mips.patch
cmake-2.8.12.1/debian/patches/FindJNI.cmake.mips.patch
--- cmake-2.8.12.1/debian/patches/FindJNI.cmake.mips.patch 1970-01-01
01:00:00.0 +0100
+++ cmake-2.8.12.1/debian/patches/FindJNI.cmake.mips.patch 2014-05-26
12:27:02.0 +0100
@@ -0,0 +1,20 @@
+From: Yunqiang Su wzss...@gmail.com
+Subject: cmake - FindJNI add mips64(el) mipsn32(el) support
+Date: Tue, 6 May 2014 16:06:45 +0800
+
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747174
+
+Add support for mips64 mips64el mipsn32 mipsn32el in
+Modules/FindJNI.cmake.
+
+--- a/Modules/FindJNI.cmake2014-05-23 09:26:39.0 +0100
b/Modules/FindJNI.cmake2014-05-26 12:19:53.275844095 +0100
+@@ -44,7 +44,7 @@ macro(java_append_library_directories _v
+ elseif(CMAKE_SYSTEM_PROCESSOR MATCHES ^mips)
+ # mips* machines are bi-endian mostly so processor does not tell
+ # endianess of the underlying system.
+-set(_java_libarch ${CMAKE_SYSTEM_PROCESSOR} mips mipsel
mipseb)
++set(_java_libarch ${CMAKE_SYSTEM_PROCESSOR} mips mipsel
mipseb mips64 mips64el mipsn32 mipsn32el)
+ elseif(CMAKE_SYSTEM_PROCESSOR MATCHES ^(powerpc|ppc)64)
+ set(_java_libarch ppc64 ppc)
+ elseif(CMAKE_SYSTEM_PROCESSOR MATCHES ^(powerpc|ppc))
diff -Nru cmake-2.8.12.1/debian/patches/series
cmake-2.8.12.1/debian/patches/series
--- cmake-2.8.12.1/debian/patches/series2014-05-23 09:23:12.0
+0100
+++ cmake-2.8.12.1/debian/patches/series2014-05-26 12:31:59.0
+0100
@@ -7,3 +7,4 @@
fix-ftbfs-on-kfreebsd.patch
fix-FindFreetype.diff
FindRuby_support_Ruby_2.diff
+FindJNI.cmake.mips.patch
signature.asc
Description: Digital signature
Bug#749492: pcp-gui-testsuite: uninstallable in sid
Package: pcp-gui-testsuite Version: 1.5.13 Severity: serious Tags: jessie sid Hi, pcp-gui-testsuite cannot be installed in sid because of a wrongly versioned dependency on pcp-gui: root@sid:~# apt-get install pcp-gui-testsuite Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcp-gui-testsuite : Depends: pcp-gui (= 1.5.13) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Note that src:pcp-gui version 1.5.13 builds a binary package pcp-gui with version 3.9.4: root@sid:~# apt-cache madison pcp-gui pcp-gui | 3.9.4 | http://http.debian.net/debian/ sid/main kfreebsd-amd64 Packages pcp | 3.9.4 | http://http.debian.net/debian/ sid/main Sources pcp-gui | 1.5.13 | http://http.debian.net/debian/ sid/main Sources Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745988: gthumb window doesn't have a title bar (NoTitle is Yes in fvwm)
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=724238 Control: tags -1 upstream In the mean time, shouldn't Debian downgrade to 3.2.x like what Ubuntu has done? https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1290691 -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749493: gambit: Please update to use wxwidgets3.0
Source: gambit Version: 0.2010.09.01-1.1 Severity: normal User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8. There's a newer upstream version of gambit which apparently supports wx2.9 (which was the development series leading up to 3.0), so updating the package to the latest upstream release is probably all that's needed to allow it to be built with wxwidgets3.0. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741628: rsync dies with inflate returned -3
I have similar experience. I dumped a subversion repository and rsynced it. This is practically append only data. It worked for several days than it stopped with the error mentioned in this thread: receiving incremental file list repo-dump 2.19G 99% 31.53MB/s0:00:00 inflate returned -3 (422 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(548) [receiver=3.0.9] rsync: connection unexpectedly closed (62 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [generator=3.0.9] Versions (rsync --version): local (Ubuntu 13.10 saucy): : rsync version 3.0.9 protocol version 30 remote (Ubuntu 14.04 trusty): rsync version 3.1.0 protocol version 31 After adding --compress-level=0 to the original --compress option, so effectively turning off compression, the problem ceases. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727481: opus-tools: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4
On Mon, May 26, 2014 at 10:29:20PM +0100, Manuel A. Fernandez Montecelo wrote: 2014-05-26 20:09 GMT+01:00 Ron r...@debian.org: Well it's certainly always going to take much longer for upstream to do that if nobody ever tells them about it ... But that is kind of exactly my point, for some of these packages it will be a trigger to make a real new upstream release, for others we may just re-roll the existing release with a regenerated build system as a new point release. Which is why I asked about timelines for when this might really become a bottleneck for proceeding with getting the port(s) that you care about into Debian. With arm64 and one of your packages: http://buildd.debian-ports.org/status/fetch.php?pkg=mingw32-binutilsarch=arm64ver=2.20-0.2stamp=1397413026 I'm pretty sure that one isn't terribly interesting for the new ports in question here, and it's essentially been obsoleted by the w64 toolchain now anyway and living on borrowed time before its complete removal. You can fairly safely blacklist it for new ports. The timelines is: the sooner that new architectures can get libogg compiling cleanly the better, so the reverse build-deps are also compiled, and then use time to fix other integration issues and be ready for Jessie or Jessie+1 (or do some kind of unofficial release in the meantime). That's why we've filed bug reports a while ago, they became blockers previous to that point. That's not a *timeline* for when this needs to be in sid. It's a todo list. Many of these packages will already naturally get an update which makes this no longer a problem, long before these ports are ready to be added to the buildd's tracking sid. If you can't give me an even rough date for when you expect that to happen, I can only assume it is still a long way into the future. ... and so we have plenty of time to wait for the next actually planned update of them. and to deal with other actually urgent things that are on a known and short deadline. If you don't like the approach, you will then better start to convince the rest of Debian developers, Anyone who needs convincing that one size fits all is a poor answer to just about any problem can argue with someone else. There are plenty of actually soluble problems that need that time more urgently. Nah, I don't need a patch for this. I just need to have a chat with the affected upstreams about whether we have something new to push out, or whether we'll just reroll a point release with the build updates. If you have a definite list of the packages of mine that you're stuck behind, that will help me not miss any, (or know for sure what version of autoconf/libtool added the support you need) - but otherwise I can probably figure that out too. I pointed initially to the place where it explains which packages are problematic: https://wiki.debian.org/qa.debian.org/FTBFS#A2014-01-21_using_dh-autoreconf_during_the_build That's not a list of the packages holding up your port. I know how to manually check them all myself - I was asking if you had already done that, and if you had to share that information. If you haven't that's fine, I have a fair idea which a new port will need before the others. Personally, I don't consider paying a bit of attention to a brand new build, with untested source, on a brand new architecture to be a waste of time. It's hardly unusual for interesting things to shake out on them. And if you don't have time to do that personally, then maybe what we need is better tools, and more scalable ways to get attentive maintainers access to ports in the early bootstrap stages - rather than filing bugs about automating away things that actually do need some sort of informed human attention more times than not. It seems to work ok is not the same as there's some interesting warnings here that someone ought to look at. I don't think it is good value for our efforts for the latter to be completely ignored in pursuit of the former. And so far just about every bug I've ever had which said please add dh_auto_something has done exactly that. I'm not asking you to care about fixing those, I'm just pointing out that taking away the warning I get about them currently so that I can care about them also comes with a cost. The problem is not to ignore autoconf warnings, the problem is that the builds stop completely because the machine is not recognised by the script configure, as I explained you above. You're still missing the point. You're saying I don't care about the potential for other problems in the package so long as it seems to build on my new port. I'm telling you that there are maintainers and upstreams who very much do care about those things. And that saying Don't worry about that to them, or worse, hiding from them the normal cues to learn about that, is counterproductive in the long run. Only when we are past that point
Bug#749494: ITP: cryptocat-extension -- An experimental browser-based chat client for easy to use, encrypted conversations.
Package: wnpp Severity: wishlist Owner: Ulrike Uhlig u...@451f.org * Package name: wnpp Version: 2.2.1 Upstream Author: Nadim Kobeissi i...@crypto.cat * URL: https://github.com/cryptocat/cryptocat/tree/master/src/firefox * License: AGPL v3 Programming Lang: Javascript Browser-based app for easy to use, accessible encrypted chat. Cryptocat is an experimental browser-based chat client for easy to use, encrypted conversations. It aims to make encrypted, private chat easy to use and accessible. Cryptocat wants to break down the barrier that prevents the general public from having an accessible privacy alternative that they already know how to use. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737387: please support multi-arch
Package: libmpfi0
Version: 1.5.1-3
Followup-For: Bug #737387
Dear Maintainer,
following https://wiki.debian.org/Multiarch/Implementation
it seems that the attached patch (hopefully reportbug will have managed
to attach it, otherwise I'll try some other way) is sufficient to
support multi-arch.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf
powerpc
Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libmpfi0 depends on:
ii libc6 2.18-7
ii libgmp10 2:6.0.0+dfsg-4
ii libmpfr4 3.1.2-1
libmpfi0 recommends no packages.
libmpfi0 suggests no packages.
-- no debconf information
diff -ru mpfi-1.5.1/debian/compat mpfi-1.5.1.MARC/debian/compat
--- mpfi-1.5.1/debian/compat 2014-02-09 22:46:29.0 +0100
+++ mpfi-1.5.1.MARC/debian/compat 2014-05-27 13:54:20.496748793 +0200
@@ -1 +1 @@
-7
+9
diff -ru mpfi-1.5.1/debian/control mpfi-1.5.1.MARC/debian/control
--- mpfi-1.5.1/debian/control 2014-02-09 22:49:47.0 +0100
+++ mpfi-1.5.1.MARC/debian/control 2014-05-27 13:55:46.195982800 +0200
@@ -1,7 +1,7 @@
Source: mpfi
Priority: optional
Maintainer: Laurent Fousse lfou...@debian.org
-Build-Depends: debhelper (= 7.0.0), dh-autoreconf, libmpfr-dev (= 2.2.0.dfsg.1), libgmp-dev, texinfo
+Build-Depends: debhelper (= 9), dh-autoreconf, libmpfr-dev (= 2.2.0.dfsg.1), libgmp-dev, texinfo
Standards-Version: 3.9.0
Section: math
Homepage: http://mpfi.gforge.inria.fr/
@@ -12,6 +12,7 @@
Section: libdevel
Architecture: any
Depends: libgmp-dev, libmpfr-dev (= 2.2.0.dfsg.1-1), libmpfi0 (= ${binary:Version}), ${misc:Depends}
+Multi-Arch: same
Description: multiple precision floating-point interval computation library
This package provides a C library of functions for interval arithmetic
computations with arbitrary precision.
@@ -35,6 +36,8 @@
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
+Pre-Depends: ${misc:Pre-Depends}
+Multi-Arch: same
Description: multiple precision floating-point interval computation library
This package provides a C library of functions for interval arithmetic
computations with arbitrary precision.
diff -ru mpfi-1.5.1/debian/libmpfi-dev.install mpfi-1.5.1.MARC/debian/libmpfi-dev.install
--- mpfi-1.5.1/debian/libmpfi-dev.install 2014-02-09 22:46:29.0 +0100
+++ mpfi-1.5.1.MARC/debian/libmpfi-dev.install 2014-05-27 13:54:50.345875385 +0200
@@ -1,3 +1,3 @@
-usr/lib/libmpfi.so usr/lib/
-usr/lib/libmpfi.a usr/lib/
+usr/lib/*/libmpfi.so
+usr/lib/*/libmpfi.a
usr/include/*.h usr/include/
diff -ru mpfi-1.5.1/debian/libmpfi0.install mpfi-1.5.1.MARC/debian/libmpfi0.install
--- mpfi-1.5.1/debian/libmpfi0.install 2014-02-09 22:46:29.0 +0100
+++ mpfi-1.5.1.MARC/debian/libmpfi0.install 2014-05-27 13:55:03.978390088 +0200
@@ -1 +1 @@
-usr/lib/libmpfi.so.*usr/lib/
+usr/lib/*/libmpfi.so.*
Bug#749495: jugglemaster: Please update to use wxwidgets3.0
Package: jugglemaster
Version: 0.4-6.3
Severity: normal
Tags: patch
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8.
I've rebuilt your package using the attached patch, and done some
testing, and everything looks good to me.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru jugglemaster-0.4/debian/changelog jugglemaster-0.4/debian/changelog
--- jugglemaster-0.4/debian/changelog 2014-03-15 22:05:17.0 +1300
+++ jugglemaster-0.4/debian/changelog 2014-05-27 23:24:27.0 +1200
@@ -1,3 +1,12 @@
+jugglemaster (0.4-6.4) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0 (new patch wx3.0-compat.patch).
+ * Fix warning due to not including string.h (new patch
+include-header-for-memset.patch).
+
+ -- Olly Betts o...@survex.com Tue, 27 May 2014 23:01:08 +1200
+
jugglemaster (0.4-6.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru jugglemaster-0.4/debian/control jugglemaster-0.4/debian/control
--- jugglemaster-0.4/debian/control 2011-11-11 16:18:51.0 +1300
+++ jugglemaster-0.4/debian/control 2014-05-27 23:01:20.0 +1200
@@ -6,7 +6,7 @@
Build-Depends: debhelper (= 7.0.50~),
libaa1-dev,
libavcodec-dev,
- libwxgtk2.8-dev
+ libwxgtk3.0-dev
Standards-Version: 3.9.2
Homepage: http://icculus.org/jugglemaster/
Vcs-Svn: svn://svn.debian.org/svn/pkg-games/packages/trunk/jugglemaster/
diff -Nru jugglemaster-0.4/debian/patches/include-header-for-memset.patch jugglemaster-0.4/debian/patches/include-header-for-memset.patch
--- jugglemaster-0.4/debian/patches/include-header-for-memset.patch 1970-01-01 12:00:00.0 +1200
+++ jugglemaster-0.4/debian/patches/include-header-for-memset.patch 2014-05-27 23:23:18.0 +1200
@@ -0,0 +1,15 @@
+Description: Include string.h for memset()
+ Fixes a compiler warning.
+Author: Olly Betts o...@survex.com
+Last-Update: 2014-05-27
+
+--- jugglemaster-0.4.orig/src/aajm/aa_drawline.c
jugglemaster-0.4/src/aajm/aa_drawline.c
+@@ -15,6 +15,7 @@
+
+ #include ./aa_drawline.h
+
++#include string.h
+
+ /*
+ * Draws a line in octant 0 or 3 ( |xlen| = ylen ).
diff -Nru jugglemaster-0.4/debian/patches/series jugglemaster-0.4/debian/patches/series
--- jugglemaster-0.4/debian/patches/series 2014-03-15 22:02:50.0 +1300
+++ jugglemaster-0.4/debian/patches/series 2014-05-27 23:22:13.0 +1200
@@ -12,3 +12,5 @@
libav9.patch
loadavg.patch
libav10.patch
+include-header-for-memset.patch
+wx3.0-compat.patch
diff -Nru jugglemaster-0.4/debian/patches/wx3.0-compat.patch jugglemaster-0.4/debian/patches/wx3.0-compat.patch
--- jugglemaster-0.4/debian/patches/wx3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ jugglemaster-0.4/debian/patches/wx3.0-compat.patch 2014-05-28 00:04:43.0 +1200
@@ -0,0 +1,47 @@
+Description: Fix to build with wxwidgets3.0
+Author: Olly Betts o...@survex.com
+Last-Update: 2014-05-27
+
+--- a/src/jmdlx/jmdlx.h
b/src/jmdlx/jmdlx.h
+@@ -92,11 +92,11 @@
+
+ static const wxCmdLineEntryDesc cmdLineDesc[] =
+ {
+-{ wxCMD_LINE_SWITCH, wxT(h), wxT(help), wxT(help) },
+-{ wxCMD_LINE_OPTION, wxT(p), wxT(pattern), wxT(named pattern), wxCMD_LINE_VAL_STRING},
+-{ wxCMD_LINE_OPTION, wxT(s), wxT(style), wxT(style), wxCMD_LINE_VAL_STRING },
+-{ wxCMD_LINE_OPTION, wxT(m), wxT(semaphore), wxT(semaphore), wxCMD_LINE_VAL_STRING },
+-{ wxCMD_LINE_PARAM, NULL, NULL, wxT(siteswap), wxCMD_LINE_VAL_STRING, wxCMD_LINE_PARAM_OPTIONAL},
++{ wxCMD_LINE_SWITCH, h, help, help },
++{ wxCMD_LINE_OPTION, p, pattern, named pattern, wxCMD_LINE_VAL_STRING},
++{ wxCMD_LINE_OPTION, s, style, style, wxCMD_LINE_VAL_STRING },
++{ wxCMD_LINE_OPTION, m, semaphore, semaphore, wxCMD_LINE_VAL_STRING },
++{ wxCMD_LINE_PARAM, NULL, NULL, siteswap, wxCMD_LINE_VAL_STRING, wxCMD_LINE_PARAM_OPTIONAL},
+ { wxCMD_LINE_NONE }
+ };
+
+--- a/src/jmdlx/print.cpp
b/src/jmdlx/print.cpp
+@@ -235,7 +235,7 @@
+ wxFileDialog filedialog(this, _(Choose a File to Print to),
+ lastpath, wxT(),
+ wxT(All Files|*),
+- wxSAVE);
++ wxFD_SAVE);
+
+ if(filedialog.ShowModal() != wxID_OK) return;
+
+--- a/src/jmdlx/jmdlx.cpp
b/src/jmdlx/jmdlx.cpp
+@@ -114,7 +114,9 @@
+ JMFrame::JMFrame(wxWindow* parent, wxWindowID id, const wxString title,
+const wxPoint pos, const wxSize size) :
+wxFrame(parent,id,title,pos,size) {
+- SetIcon(wxIcon(wxT(IDI_WIZICON)));
++ // This icon doesn't seem to be defined anywhere, and setting it results in a
++ // wx log message.
++ // SetIcon(wxIcon(wxT(IDI_WIZICON)));
+
+ fileMenu = new wxMenu();
+ optionsMenu = new wxMenu();
Bug#749491:
if you are using virtualenv then you have to rebuild your virtual environment e.g. $ virtualenv /path/to/your/virtualenv/ -- Davor
Bug#749347: ledgersmb: fails to install - issue confirmed
tags 749347 + confirmed owner 749347 Robert James Clay j...@rocasa.us thanks On 05/26/2014 11:17 AM, Holger Levsen wrote: From the attached log (scroll to the bottom...): Selecting previously unselected package ledgersmb. (Reading database ... 13616 files and directories currently installed.) Preparing to unpack .../ledgersmb_1.3.39-1_all.deb ... Unpacking ledgersmb (1.3.39-1) ... Setting up ledgersmb (1.3.39-1) ... cp: cannot stat '/usr/share/ledgersmb/ledgersmb-http-2.4.conf.template': No such file or directory Attempting to run essentially the same piuparts command as that used in the bug report had a failure from piuparts (currently, v.56) in my usual development environment. However, I was able to run it in a jessie chroot (using the current v0.58) and there confirmed the error that is coming up as shown in the bug report. Robert Jame Clay j...@rocosa.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749496: Version requirement for python-six dependency is missing
Package: python-w3lib Version: 1.5-1 Caught the following exception in my first run, and upgrading python-six from 1.3.0-1 to 1.6.1-2 fixes it. File /usr/lib/python2.7/dist-packages/w3lib/form.py, line 2, in module if six.PY2: AttributeError: 'module' object has no attribute 'PY2'
Bug#740070: O: sendmail -- powerful, efficient, and scalable Mail Transport Agent
Hi! I use Sendmail since 1997 and all my network run well over it. I think that I can help to maintain this package but not alone. This is a very hard package and I suggest to create a team for it. I am concerned about the Sendmail situation in Debian. Thanks, Eriberto pgpu2Fg2SV8h8.pgp Description: PGP signature
Bug#747710: amanda: FTBFS on sid/amd64: configure: error: Cannot build the Amazon S3 device
Hi, On Mon, 26 May 2014 12:26:44 +0300 Damyan Ivanov d...@debian.org wrote: Control: -1 patch tags! :) Adding libssl-dev to the build-dependencies makes the configure step pass, but here's what I get during compilation: I've also tried but got no error, so would upload it with 3 days-delayed queue. # and upstream provides 3.3.5 now, it is worth to update. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
