Bug#868358: mate-screensaver thinks it's activated but doesn't appear to have locked the screen
Package: mate-screensaver Version: 1.20.0-1 Followup-For: Bug #868358 Dear Maintainer, * What led up to the situation? Enabled mate-screensaver as part of session... * What exactly did you do (or not do) that was effective (or ineffective)? Locked the screen, came back and it was not locked, however: $ mate-screensaver-command --query The screensaver is active The screensaver is not inhibited $ * What was the outcome of this action? On first lock, the screensaver appears and runs with locking for some period of time, however after around an hour (maybe less) it stops actually locking the screen, and the screensaver entirely disappears, but mate-screensaver-command --query thinks that it's still active. * What outcome did you expect instead? That when mate-screensaver-command thought the screensaver was active that, err, the screen would actually be locked. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-screensaver depends on: ii dbus-x11 1.12.8-2 ii libatk1.0-0 2.28.1-1 ii libc6 2.27-3 ii libcairo-gobject2 1.15.10-3 ii libcairo2 1.15.10-3 ii libdbus-1-3 1.12.8-2 ii libdbus-glib-1-2 0.110-2 ii libgdk-pixbuf2.0-02.36.11-2 ii libgl11.0.0+git20180308-3 ii libglib2.0-0 2.56.1-2 ii libgtk-3-03.22.29-3 ii libice6 2:1.0.9-2 ii libmate-desktop-2-17 1.20.1-2 ii libmate-menu2 1.20.0-2 ii libmatekbd4 1.20.1-1 ii libnotify40.7.7-3 ii libpam0g 1.1.8-3.7 ii libpango-1.0-01.42.0-1 ii libpangocairo-1.0-0 1.42.0-1 ii libsm62:1.2.2-1+b3 ii libstartup-notification0 0.12-5 ii libsystemd0 238-5 ii libx11-6 2:1.6.5-1 ii libxext6 2:1.3.3-1+b2 ii libxklavier16 5.4-3 ii libxss1 1:1.2.2-1+b2 ii libxxf86vm1 1:1.1.4-1+b2 ii mate-desktop-common 1.20.1-2 ii mate-screensaver-common 1.20.0-1 ii mate-session-manager 1.20.0-1 Versions of packages mate-screensaver recommends: ii mate-power-manager 1.20.1-1 Versions of packages mate-screensaver suggests: pn rss-glx pn xscreensaver-data -- no debconf information
Bug#884919: ITA quagga
control: retitle -1 ITA: quagga -- network routing daemons (metapackage) Thanks, -- Brett Parker signature.asc Description: PGP signature
Bug#798440: New Upstream Version 2.7
On 04 Nov 16:10, Johannes Schauer wrote: > Hi Brett, > > On Wed, 9 Sep 2015 13:24:54 +0200 Jonas Genannt <gena...@debian.org> wrote: > > could you please package pound version 2.7 into debian? > > > > If you have no time, I could help. > > would you mind if we do an NMU of the new pound version? > > Or do you have time packaging the new version in the near future? Please do, I've not got time for the next couple of weeks at least :/ Thanks, -- Brett Parker
Bug#750002: debian-maintainers: Please add Brett Parker to the Debian Maintainers keyring
Package: debian-maintainers Severity: normal Please add my key to the debian maintainers keyring, the jetring changeset is attached. -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Brett Parker Comment: Add Brett Parker idu...@sommitrealweird.co.uk as a Debian Maintainer Date: Sat, 31 May 2014 14:11:40 +0100 Action: import Recommended-By: Jonathan McDowell nood...@earth.li Agreement: https://lists.debian.org/debian-newmaint/2014/03/msg7.html Advocates: https://lists.debian.org/debian-newmaint/2014/03/msg00015.html Data: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.12 (GNU/Linux) mQINBEqanN4BEAC7vt4yjA1k5vcyqJu9jIzKY4eNbDbp/saBUuGWNIrtHSpTUFfS LuK5cb6hIMQNE7/o5bLSCeERjx9lgPM7A2GJwQDgpOU6XYOvDJx3PnMoaeLMvzKV johe4ZuYx/ioCgzPmzcKZ9DXB45BLLERXe5njodgMn7mg6nd1M2goi98rBLm9GFc B8jb35E5Niu9LlrEXnPX51Fxwh0nqrtGl4xj0Ucqlk5Qq+qr8E7sSHqBwfVWccpz x+0RUYkVEmytFnw7gWOO5nHnNMN32m0d/H5KfA0KkJk1J/xBZwKn7NzviSH9RKDu CJRltkMQB4l111d4cIip2PnVI2vk3jQyP3NUyWuAqFRQFn/4CzSDjIlKJ+ikWPEW WvON94MhE2Vb3Lv/D6mfoSrvIvgzh9+PhJDfdw9nTLTUZnjRLvP/u5+NfmCc1HBF qrxkDxbTK+dA4FXrPH5OJDoAmQ58NrpdnvbHO0XqQ/cTM9t1hh7JBX1OZDYVoLYj 5K5j2Vz3r+0pgI5Sfz2dlZVdGCqx5NwOxS8SZ0HGTjVB5HqFJbgP7dihdeuVNB/k wriZ5z7j7KLjak77O4ayEwirhS9icg0YCmZcFwT8GNdrJIX306jxOa7ZfKnuao9h SdSYG77CzEFvuNZBQS3H4F9l1xxoWpwUbc7J9uFQct3Zy/b8p06vWGjx4QARAQAB tCtCcmV0dCBQYXJrZXIgPGlEdW5ub0Bzb21taXRyZWFsd2VpcmQuY28udWs+iQI3 BBMBCAAhBQJKmpzeAhsDBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEEeewk+V xx1hyCoP/ia8FnpibnsnyQb22VKTdUtp1OT3IXLiP4JGkM4mmsLm4H0X2gMejHvs ez99J9hYwQxV5v2Ilep+cg669wtFW/TshtRq7+6kMmGEIPV4SecjwDRdDqFg6pzM xxGGxK/whC5zc0fKcxtQG17hQbpf0Sq0oEo34CEBfgkdWlLMLDm2a6AXVFbwSxKt VxyLOx9uMMGmYM3Ap8w+rTY79Vinj/xURCn1v3IeideZ34HF7owNLBUYjdrsmulN FF7y8cHBygH2gjifRMrsA77IkQmoKmiSHchke2rb5Qkp4vIhbzrmH30hQ93XW16I wEezN5ht7W22+iJIh7YpAWL5Ml02xoJqKisztvwddXptr+DGKBL+GhFvvOZInGtC kd5rTXRiKIj7+Fba8eAbOKlVdpaSd5k8fh+7GociqK1MXdZtg/8JPNsRTMm62TMT mAgVjYZQXlwkx1h5MKS4OjHzs6+RBmVxGrwg35FYf86N83LxDZXeNbHrP8Chwdo8 HgM89mxmpN7450n0ECmGR3ZU5HSmdh7cvuRsO0ElaxA8zLprg5dhI87n5zg3oOLy lcQ9x9+178hWdQMYWWe5kUCqnzCrg6ctyZa/uSuV/FqtyukOHbTTlLtwyH1braTS lmHjI4PVH7EwkXXk2UD5UaFscoqEnJ22ghV3kKO0S4wilSKNnBB3iQIcBBABCAAG BQJKnEn8AAoJEJT6NystqLmFsXEP/0GWgEl1bSiUKrH6JlYmsDw4Wow5C9cTg4uc jtyUMTaIOUNhDlIZ4yx6Or4Gv8WRBa7FeVCO+5in4sGvK1mgKU9J2x0szZtLR7e3 E6FxxwX1RYdPdQTqAiymDqWP/v3QkSKgjg3Hun6f+F5e+SOv+mKh/xtSMbUMef95 qOSOWGUd8P/rOpqvBINi3rC118jGRZeo3NN9tHkj/mUR5fMT8zTUlmANDqEU3X15 r89aeKQzsJzn5GXK+LP1VdPjlj1WXUcukPLsaeBYgMlc+jWMitD9Ie05AU/rmEF1 mQc34iWwFaFJJeFpVYWj9KjJTqhCsE48YGN9BDGQ2t3wR+I8sA+uBSk5AlOsqCP/ 0M6WcPYGlxnIaQfQ2DJrOjPJc0HsjXVLrhAoHJI7bxzsTNzyDRRcGCHvqmuUnEzw rMqwmhofBahDBUDHUENGWRLEm78SOlDGF0dPfYxiorlSHkpMZnzaNIrA6O/FvQzb YYAOW9mzY+wdrmbb6D7A35ZjWaaop3nZMFAnJrusYTX+kbwR+H4OodP7rTKHgwDt MsNxzUPUNDz+XSZEAjFT9m7IXQUMGn3drbyxrkMsI0HtBb17qK+lo/mmIrtmVWCe pJ2L2+Okz4Cn3SoXCxDOmg7f1P1VK/rbDX919LCAVJ6PgL6bh8gXCUbn9cG6wqHI WRoq60CtiEYEExEIAAYFAkqdKAgACgkQfDt5cIjHwfciCgCgmBYY81Mt639hPH9F tQkwTcigs1YAn0tHjQc8lyNRZa3Prrg8rLmYKhMyiQIcBBMBCAAGBQJKnSjqAAoJ EFh5eVc0QmhOE2MP/iNp0Ro0NdnL3skAxkneB4Cy52xyOOulMEydBcdMTWvCMFQw RPfj95Xry+8J0c0qmh36yl1TZ0wTZZc0gedPWQ+Hets426wXKK2R1E8qwzXGphAi ubDpUPXmaOu504Q3mjVudbsaqLMhliozOf0psldA+fUx+qLavz2qkWOAmcVB/E/H J8Y1G3LSSIGgLyvIpRsuYp6ih8gZ7CvEQw8vq3Vo5+07hPPRdGYf7XOikexiDYWs dvjsw8K2GByt11Egr0Ie1DtAAuGZZQvSrjzGL1P2YMukqCbcKJ4gL1gGV4LIbxCq ghbr8p059d0BaSCGNmQb53YmDkxaZtwDhuxGCDVN8hn5RtcSeu0WEiWNcQ3jRH1k wqKpfUT7xA1ydGnSdMr7fgS8GeWa8hlxY+h1UHYJZ7MVQFZn4liQ/0r+p/agH+VX UJr2ipHyGQ2EIGmtcQbi50761kQgWH2HVyXRLPj/aozSHJV7FTOOGSz2RP54At/c D1mv5Q6HIqIMYzdZdYDpr/Hja330FGDCNqkyx4lYLL/ZZOBaPpkkRjfeVUiLz15l ag/NZYuutwJHnG04yPWiJPx5LWvFhkrFaHex1P5daGd6xYpjYlaRwC3Qe4saVI1F JXNZK5sqBOKggA1nJOEplwg/Ja8bfEtXXGqQwJuFQzQACHhkD74JXmHV5MMfiQIc BBABCgAGBQJMe46tAAoJEE3o/ypjx8yQprMP/iCsFJhA23nqnQYbatWQM6uMFYQ+ 0sUtr6ACLJXCHkE0nUflajytSlkd6UvkjZplrllbz1qBXK1JOz+DEdnheatbfkxN 6OVmZkE1QKfEbzzC9yQiMO3HWjPoe4qyPixjbpnK63Mo5rA41Ki4WcK8f0DhOZMr yjSsRHiMJgY1eZgOR6X/4qfSg3cWWntqIZGtOl6phBgqxq5q7JdPI+FbmyhWEcRs c2tC6j66py430eF0+Ro2BH01wYRoDCkYoiO5VK0wPieCDTgnKmjUhCUdzkwzrLdT HkbvvQeq0UgYcQWEwBtu6TtNsJHfrsaozx/3gRBEINTQNrouxM0Ul6gYECSgLCsm J64HNPyUK8nON7IwlbnRk/j8AOwb5KbBGfKzeWnKO1l3BkrRd4laC8lBL3ZhaiTM SPhA/QmsElq+CuVZu0aQOycjtP0/848QiiwyGD1RPBQRFKsQwU61mYhs/h5srbV6 8O+kaBuHWEOQj1n93W1kov4xMK+cNVqu1pbKcoN2Eacwd/Ms8Elfaam6KrRo7POX k2K5FoxziGjMyzaEfpuJ68nbX5jv20Svs3HKXuBaL1raf0FHMJH8t5GF3XKdcXRu kIx0Z0JlaPdBqgsr/pqwr3PRj5FOYQlKcDqiIGAKWr/ir6ePNZIPy+DbJxyWk/Ld VK+z+MQixFra5eRTiQIcBBABCAAGBQJMe4l5AAoJENBLo6ABJdXAIY4P+wWf1KBz crbfQlAq2qC/x4Jv6/7ZMGc9UkXf188dTnuxxcnU2dGNiREUNbZZM8IgPHioKp+s 9Q6wr
Bug#742488: No MKCALENDAR possible with pound
On 24 Mar 12:05, Bernd Krüger-Knauber wrote: Package: pound Version: 2.6-2 Tags: patch It is not possible to use MKCALENDAR as http request. It is not included in the sourcecode. I think there is also a problem with PATCH which is added already in 2.7b PATCH support should be in the current package, but the other changes are in the 2.7 releases of pound, which is still labelled as their Experimental tree. I'll take a closer look at what's changed between 2.6 and 2.7 over the next week, it may be that 2.7b is stable enough that we can just move to that (and make sure that the current extra patches still apply cleanly). I'll take a look in the coming week and see what the best plan is, appears that upstream is a bit quiet these days. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723731: Patch to xss_redirect_fix
Hi,
The attached patch fixes the redirect code to not break the query string
by re-encoding the = character.
Thanks,
Brett.
diff -ru4 orig/pound-2.6/debian/patches/xss_redirect_fix.patch new/pound-2.6/debian/patches/xss_redirect_fix.patch
--- orig/pound-2.6/debian/patches/xss_redirect_fix.patch2012-02-03 09:46:07.0 +
+++ new/pound-2.6/debian/patches/xss_redirect_fix.patch 2013-12-23 13:35:39.0 +
@@ -42,9 +42,9 @@
+ if (
+ (ch= 'A' ch ='Z') ||
+ (ch= 'a' ch ='z') ||
+ (ch= '0' ch ='9') ||
-+ch == '-' || ch == '_' || ch == '.' || ch == ':' || ch == '/' || ch == '?' || ch == '' || ch == ';') {
++ch == '-' || ch == '_' || ch == '.' || ch == ':' || ch == '/' || ch == '?' || ch == '' || ch == ';' || ch == '=') {
+
+ urlbuf[j++] = ch;
+ continue;
+ }
diff -ru4 orig/pound-2.6/http.c new/pound-2.6/http.c
--- orig/pound-2.6/http.c 2013-12-23 13:54:00.0 +
+++ new/pound-2.6/http.c2013-12-23 13:52:56.0 +
@@ -81,9 +81,9 @@
if (
(ch= 'A' ch ='Z') ||
(ch= 'a' ch ='z') ||
(ch= '0' ch ='9') ||
-ch == '-' || ch == '_' || ch == '.' || ch == ':' || ch == '/' || ch == '?' || ch == '' || ch == ';') {
+ch == '-' || ch == '_' || ch == '.' || ch == ':' || ch == '/' || ch == '?' || ch == '' || ch == ';' || ch == '=') {
urlbuf[j++] = ch;
continue;
}
Bug#717805: Patch for dealing with newer initramfs images with microcode headers
Hi,
Here's a patch to lsinitramfs to deal with initramfs images that start
with the microcode archive and then a real archive afterwards.
--
Brett Parker
diff -rU4 initramfs-tools/lsinitramfs initramfs-tools-0.109.1.new/lsinitramfs
--- initramfs-tools/lsinitramfs 2012-03-25 05:12:23.0 +0100
+++ initramfs-tools-0.109.1.new/lsinitramfs 2013-09-24 16:05:13.024780933 +0100
@@ -53,8 +53,25 @@
elif bzip2 -t $initramfs /dev/null 21 ; then
bzip2 -c -d $initramfs | cpio ${cpio_args}
elif lzop -t $initramfs /dev/null 21 ; then
lzop -c -d $initramfs | cpio ${cpio_args}
+ elif cpio ${cpio_args} $initramfs /dev/null 21; then
+ # this is a straight cpio archive followed by a compressed one, yay!
+ cpio ${cpio_args} $initramfs
+ real_offset=$(cpio --io-size=1 --extract --list $initramfs 21 /dev/null | sed -e '$ { s# .*$##; p; }; d;')
+ # now we need to find the beginning of the actual archive, this is
+ # going to be the number of bytes from above + 8
+
+ # use same logic as above to loop through the potentials
+ if (dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | zcat -t /dev/null 21); then
+dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | zcat | cpio ${cpio_args}
+ elif (dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | xzcat -t /dev/null 21); then
+dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | xzcat | cpio ${cpio_args}
+ fi
+ elif (dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | bzip2 -t /dev/null 21); then
+dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | bzip2 -c -d | cpio ${cpio_args}
+ elif (dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | lzop -t /dev/null 21); then
+dd if=$initramfs bs=$((real_offset+8)) skip=1 status=noxfer 2/dev/null | lzop -c -d | cpio ${cpio_args}
fi
fi
done
Bug#522196: #522196 - RFP: gnu icecat - the GNU version of Mozilla Firefox
On 03 Apr 15:42, Nico Golde wrote: Hi, * Raphael Geissert atom...@gmail.com [2009-04-02 19:45]: [Security team BCC'ed] Hi, Do we really need another mozilla browser around? Last time I heard the iceweasel maintainers were looking for other people to help them. I don't think yet another clone of firefox is going to do any good in any sense (including the security POV). As providing security support for the ice* suite is already PITA and I see no reason why we should include this given that we have ice* I strongly oppose to include this to Debian. I thought they all now dynamically linked against xulrunner so that security support was much simpler than before, so it's really just a frontend more than a clone of firefox, no? Cheers, -- Brett Parker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517816: monit: Fails to start on some VPSes
Package: monit
Version: 1:4.10.1-4
Severity: important
Under certain circumstances on some VPSes monit can't do process
monitoring due to a zero cpu count - this is now fixed upstream, and I
have attached a patch that fixes the debian package for this issue.
Thanks,
--
Brett Parker
diff -rNU4 debian/monit-4.10.1/debian/changelog mine/monit-4.10.1/debian/changelog
--- debian/monit-4.10.1/debian/changelog 2009-03-02 09:49:47.0 +
+++ mine/monit-4.10.1/debian/changelog 2009-03-02 09:47:03.0 +
@@ -1,4 +1,17 @@
+monit (1:4.10.1-4+lenny0.1) stable; urgency=low
+
+ * Real fix for the CPU count bug - if we get 0 CPUs report 1.
+
+ -- Brett Parker idu...@sommitrealweird.co.uk Sat, 28 Feb 2009 16:32:34 +
+
+monit (1:4.10.1-4+lenny0) stable; urgency=low
+
+ * Adds patch to stop divide by zero bug taken from the trunk
+
+ -- Brett Parker idu...@sommitrealweird.co.uk Wed, 25 Feb 2009 15:38:10 +
+
+
monit (1:4.10.1-4) unstable; urgency=low
* Patch for config file location was not applied (Closes: #479357)
(thanks to DVZ-Team dv-zent...@fh-giessen.de)
diff -rNU4 debian/monit-4.10.1/debian/patches/00list mine/monit-4.10.1/debian/patches/00list
--- debian/monit-4.10.1/debian/patches/00list 2009-03-02 09:49:47.0 +
+++ mine/monit-4.10.1/debian/patches/00list 2009-03-02 09:47:03.0 +
@@ -1,2 +1,3 @@
config_file_relocation
monit.1-debian-path
+cpu_count_fix
diff -rNU4 debian/monit-4.10.1/debian/patches/cpu_count_fix.dpatch mine/monit-4.10.1/debian/patches/cpu_count_fix.dpatch
--- debian/monit-4.10.1/debian/patches/cpu_count_fix.dpatch 1970-01-01 01:00:00.0 +0100
+++ mine/monit-4.10.1/debian/patches/cpu_count_fix.dpatch 2009-03-02 09:47:03.0 +
@@ -0,0 +1,26 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## cpu_count_fix.dpatch nicked from the 5.0 beta branch
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: No description.
+
+...@dpatch@
+--- monit-4.10.1.a/process/sysdep_LINUX.c 2007-07-29 21:23:26.0 +0100
monit-4.10.1.b/process/sysdep_LINUX.c 2009-02-28 16:22:54.910031274 +
+@@ -134,12 +134,15 @@
+ DEBUG(system statistic error -- cannot get real memory amount\n);
+ return FALSE;
+ }
+
+- if((num_cpus = sysconf(_SC_NPROCESSORS_CONF)) == -1)
++ if((num_cpus = sysconf(_SC_NPROCESSORS_CONF)) 0)
+ {
+ DEBUG(system statistic error -- cannot get cpu count: %s\n, STRERROR);
+ return FALSE;
++ } else if (num_cpus == 0) {
++DEBUG(system reports cpu count 0, setting dummy cpu count 1\n);
++num_cpus = 1;
+ }
+
+ if((page_size = sysconf(_SC_PAGESIZE)) = 0) {
+ DEBUG(system statistic error -- cannot get page size: %s\n, STRERROR);
Bug#498999: Every Morning's Email
On 19 Feb 07:53, Kent West wrote: Scratch the quotation of the body below: somehow in my copy/pasting I got the lines reversed. Here's the real body: exim paniclog /var/log/exim4/paniclog on goshen.campus.acu.edu has non-zero size, mail system might be broken. The last 10 lines are quoted below. 2009-02-15 22:20:20 Exim configuration error in line 28 of /var/lib/exim4/config.autogenerated.tmp: malformed macro definition When you upgraded exim did you let it upgrade the conf file snippets, or just some of them - I'd guess that it's a missing part of the config, you're getting the mail because it'll try to do a reload as part of cron.daily, and that's going to trigger the automatic configuration again. See what you get out of update-exim4.conf which should tell you more. -- Brett Parker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508829: ITP: surefire -- Surefire test framework for Java
On 15 Dec 21:02, Torsten Werner wrote: Package: wnpp Severity: wishlist Owner: Torsten Werner twer...@debian.org * Package name: surefire Version : 2.4.3 Upstream Author : Apache Software Foundation * URL : http://maven.apache.org/surefire/ * License : Apache-2.0 Programming Lang: Java Description : Surefire test framework for Java Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. . Maven's primary goal is to allow a developer to comprehend the complete state of a development effort in the shortest period of time. In order to attain this goal there are several areas of concern that Maven attempts to deal with: . * Making the build process easy * Providing a uniform build system * Providing quality project information * Providing guidelines for best practices development * Allowing transparent migration to new features . This package ships the surefire test framework and the maven-surefire-plugin. The long description, other than the last line, seems to be a description of maven rather than surefire. -- Brett Parker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481164: Bad tarball for Django 0.96.2
On 16 May 23:12, James Bennett wrote: Raphael Hertzog wrote: I wanted to prepare an upload of the Django 0.96.2 to Debian unstable but the package doesn't build without modifications because the new tarball lacks quite a few files compared to the previous 0.96.1 tarball. Hrm. Looks like the setup.py script on 0.96 doesn't pull that stuff in. I can't really go back and tweak that for something that isn't really a security fix, but an svn export from the 0.96-bugfixes branch in the Django repo should get you want you want, after which it's easy enough to make the tarball manually. Further to this, it appears that the 0.96.2 release wasn't actually tagged in svn... Is there any reason for that? Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481164: patch for python-django XSS
On 14 May 17:42, Raphael Hertzog wrote: On Wed, 14 May 2008, Steffen Joeris wrote: Attached you will find the patch from upstream. Please let me know, if you have time for it or want me to upload. Don't worry, I will wait a few days. I'll let some time to Brett first... but for unstable, we'll simply package 0.96.2 I think. Yeah - knowing that it's only security updates means that the upload will be very simple. The question is for etch. Can we upload 0.95.2 instead of 0.95.1-1etch1 provided that the upstream release adds nothing else except the security fix? (I haven't checked that yet) I'm also not sure if the issue would be high enough priority for a security release for it, more likely that it wouldn't get in until a point release (although, I believe that we're coming close to one). There's also an experimental upload to do, but this one will require a new SVN snapshot. Need to track through the svn log - I lost my dev environment for the packages on my laptop a few weeks ago and am still recreating it, should be able to get that sorted over the weekend. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477338: lowercase X does not function in command terminals
Sounds like you've got a bind statement in your ~/.bashrc or ~/.bash_profile. -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#450913: bash completion script breaks normal file completion
On 25 Feb 13:42, James Bennett wrote: This has been fixed upstream in Django trunk, as changeset 7156[1]. [1] http://code.djangoproject.com/changeset/7156 Because we've already got a different patch to the bash completion (for the rename) this is going to take a bit more work! I'll prepare a new patch and should be able to get it in to both the trunk code (for experimental) and the 0.96 code sometime tomorrow. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462058: [SPAM?] Bug#462058: Acknowledgement (python-django: problem when extracting PostgreSQL's version number)
On 06 Feb 08:55, Raphael Hertzog wrote: On Tue, 05 Feb 2008, Brett Parker wrote: On 05 Feb 20:49, Brett Parker wrote: On 03 Feb 23:09, Raphael Hertzog wrote: Any progress? Well, I've nearly finished a patch for the 0.96 branch, just tidying it a bit now... should be commited to SVN this evening. I've commited a fix to svn that's working for me, keeps previous behaviour for full numerical version numbers and seems to be the least nasty way of doing it that I could find. Ok, I'll review and upload later. Did you forward it to upstream already? Does it concern the experimental version too? It also concerns the experimental version, but as things were moved around, I need to generate a (slightly different) patch for that which I'll forward upstream and add to the ticket open there. -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462058: [SPAM?] Bug#462058: Acknowledgement (python-django: problem when extracting PostgreSQL's version number)
On 03 Feb 23:09, Raphael Hertzog wrote: On Wed, 23 Jan 2008, Brett Parker wrote: This has been reported already upstream at http://code.djangoproject.com/ticket/6433. Unfortunately both patches (yours and the one on that ticket) have slightly interesting bugs... For example, the patch on that ticket would parse 8.3RC3 - [8, 33] which is (clearly) wrong. Yours has an issue that isn't currently a problem in postgres, but maybe at sometime in the future, if you had the string 10.1RC3 your version would end up with [1, 0, 1] which is obviously not the desired effect! I'm looking in to this bug, and will be tracking upstreams dealings with it. Any progress? Well, I've nearly finished a patch for the 0.96 branch, just tidying it a bit now... should be commited to SVN this evening. -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462058: [SPAM?] Bug#462058: Acknowledgement (python-django: problem when extracting PostgreSQL's version number)
On 05 Feb 20:49, Brett Parker wrote: On 03 Feb 23:09, Raphael Hertzog wrote: Any progress? Well, I've nearly finished a patch for the 0.96 branch, just tidying it a bit now... should be commited to SVN this evening. I've commited a fix to svn that's working for me, keeps previous behaviour for full numerical version numbers and seems to be the least nasty way of doing it that I could find. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462058: [SPAM?] Bug#462058: Acknowledgement (python-django: problem when extracting PostgreSQL's version number)
This has been reported already upstream at http://code.djangoproject.com/ticket/6433. Unfortunately both patches (yours and the one on that ticket) have slightly interesting bugs... For example, the patch on that ticket would parse 8.3RC3 - [8, 33] which is (clearly) wrong. Yours has an issue that isn't currently a problem in postgres, but maybe at sometime in the future, if you had the string 10.1RC3 your version would end up with [1, 0, 1] which is obviously not the desired effect! I'm looking in to this bug, and will be tracking upstreams dealings with it. Thanks! -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460662: django-admin doesn't create manage.py with the right python interpreter
On 14 Jan 18:37, Raphael Hertzog wrote: On Mon, 14 Jan 2008, Filippo Giunchedi wrote: It's not automatic since you have to change the invocation of django-admin to give a special interpreter. :) And if you're doing something explicit like that you might as well just edit the generated file. Indeed, thinking about this I am more inclined to think about it as an upstream bug than a distribution one, how does this sound? Of course, the django-admin script is not Debian-specific at all, it's provided by upstream. Feel free to forward in the upstream trac instance: http://code.djangoproject.com/simpleticket Nothing like that seems to be open: http://code.djangoproject.com/query?status=newstatus=assignedstatus=reopenedcomponent=django-admin.pyorder=priority How do you expect django-admin to know that it has been called by python or by python2.4 (when they are the same in Debian currently) ? Would it be necessary to know if django-admin is called by the standard interpreter? Anyway, how about something like this? Well, in fact using sys.executable seems to be enough: $ cat test.py #!/usr/bin/env python import sys print sys.executable $ ./test.py /usr/bin/python $ python2.5 ./test.py /usr/bin/python2.5 $ python2.4 ./test.py /usr/bin/python2.4 So django-admin should update the shebang of manage.py with the value of sys.executable. We previously had a patched django-admin that did this, and went back to putting the shebang to the default python... I'd rather it was left as using the default python, and if people want to use a non default one they either edit the files or run it using the other python. Open to suggestion though. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444093: Acknowledgement (xmms-scrobbler: plugin has problems with umlauts in UTF-8 encoded tags)
On Wed, Sep 26, 2007 at 05:29:49AM +0300, Wouter Van Hemel wrote: I don't know if it shows up correctly this way, but the one on 16 Sep has an up-right accent on the 'o' in Solstafir (correct), while the one on 19 Sep has two weird symbols instead of the accented 'o'. I have not changed locale or edited the tags. I have updated Debian (unstable) a few times since then though. Hmm, the last upload of the package happened on 2007-07-01, that changed over to using taglib instead of the other code that we had for tag reading. taglib (in theory) should be giving me utf-8 and determining the character set of the tags for us. I'll need to set up a test set of tags and see if I can reproduce the issue, but it definately won't be in the gtk1 broken utf-8 handling (we never touch that chunk of code!). Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413762: Fix for config structure using dynamic backends... better this time!
OK - rather than using -rdynamic, which as you rightly point out means
that we clobber some other parts of the namespace, here's a slightly
different approach, this time we look up the struct in the library and
then assign it's parts to that of the real config object at the point of
library load.
diff -rU4 onak-0.3.3/keydb_dynamic.c onak-dev/keydb_dynamic.c
--- onak-0.3.3/keydb_dynamic.c 2007-03-04 23:11:31.0 +
+++ onak-dev/keydb_dynamic.c 2007-08-14 08:43:55.518194786 +0100
@@ -33,8 +33,9 @@
{
char *soname = NULL;
void *handle;
struct dynamic_backend *backend = get_backend();
+ struct onak_config *backend_config;
if (backend-loaded) {
close_backend();
}
@@ -97,11 +98,34 @@
backend-handle = handle;
backend-loaded = true;
+ backend_config = (struct onak_config *)dlsym(handle, config);
+ if (backend_config != NULL) {
+ configure_backend(backend_config);
+ }
+
return true;
}
+void configure_backend(struct onak_config *backend_config) {
+ /* Because we can't use -rdynamic and therefore use global symbols, we need
+ * to use the symbol for the backends config variable and then assign the
+ * real config values to it
+ */
+ backend_config.maxkeys = config.maxkeys;
+ backend_config.thissite = config.thissite;
+ backend_config.adminemail = config.adminemail;
+ backend_config.mta = config.mta;
+ backend_config.syncsites = config.syncsites;
+ backend_config.logfile = config.logfile;
+ backend_config.db_dir = config.db_dir;
+ backend_config.pg_dbhost = config.pg_dbhost;
+ backend_config.pg_dbname = config.pg_dbname;
+ backend_config.pg_dbuser = config.pg_dbuser;
+ backend_config.pg_dbpass = config.pg_dbpass;
+}
+
bool close_backend(void)
{
struct dynamic_backend *backend;
backend = get_backend();
diff -rU4 onak-0.3.3/keydb_dynamic.h onak-dev/keydb_dynamic.h
--- onak-0.3.3/keydb_dynamic.h 2007-03-04 23:11:29.0 +
+++ onak-dev/keydb_dynamic.h 2007-08-14 08:16:23.920075573 +0100
@@ -88,8 +88,9 @@
0 /* loaded */
};
bool load_backend(void);
+void configure_backend(struct onak_config *);
bool close_backend(void);
bool backend_loaded(void);
struct dynamic_backend *get_backend(void);
signature.asc
Description: Digital signature
Bug#413762: Fix for config structure using dynamic backends...
The attached patch fixes the config structure when dynamic backends are used - the basic issue is that when the backend was loaded, it wouldn't (neccessarily) share the config structure with the program that called it (and had therefore read the config). Cheers, Brett Parker --- onak-0.3.3/Makefile.in 2007-03-04 23:11:30.0 + +++ onak-dev/Makefile.in 2007-08-11 16:08:55.605202941 +0100 @@ -25,8 +25,10 @@ gpgwww.c onak-conf.c charfuncs.c sendsync.c log.c photoid.c \ wordlist.c cleankey.c cleanup.c keyarray.c \ $(foreach be,@BACKENDS@,keydb_$(be).c) +PROGS_LDFLAGS_EXTRA= + ifeq ([EMAIL PROTECTED]@, xyes) PROGS += keyd KEYDB_OBJ = keydb_keyd.o SRCS += keyd.c keydb_keyd.c @@ -37,8 +39,9 @@ ifeq ([EMAIL PROTECTED]@, xdynamic) LIBS += -ldl BACKENDS = $(foreach be,@BACKENDS@,libkeydb_$(be).so) PROGS += keyd +PROGS_LDFLAGS_EXTRA=-rdynamic SRCS += keyd.c endif OBJS = stats.o cleankey.o $(CORE_OBJS) $(KEYDB_OBJ) @@ -46,9 +49,10 @@ all: .depend $(PROGS) testparse maxpath sixdegrees splitkeys onak.conf \ $(BACKENDS) keyd: keyd.o $(CORE_OBJS) keydb_$(DBTYPE).o - $(CC) $(LDFLAGS) -o keyd keyd.o $(CORE_OBJS) keydb_$(DBTYPE).o $(LIBS) + $(CC) $(LDFLAGS) $(PROGS_LDFLAGS_EXTRA) \ + -o keyd keyd.o $(CORE_OBJS) keydb_$(DBTYPE).o $(LIBS) libkeydb_db4.so: keydb_db4.o $(CC) -shared $(DB4LIBS) -o libkeydb_db4.so keydb_db4.o $(CORE_OBJS) @@ -62,36 +66,41 @@ $(CC) -c -fPIC $(LDFLAGS) -o $@ $ splitkeys: splitkeys.o $(CORE_OBJS) $(KEYDB_OBJ) $(CC) $(LDFLAGS) -o splitkeys splitkeys.o $(CORE_OBJS) $(KEYDB_OBJ) \ - $(LIBS) + $(LIBS) $(PROGS_LDFLAGS_EXTRA) testparse: main.o $(OBJS) - $(CC) $(LDFLAGS) -o testparse main.o $(OBJS) $(LIBS) + $(CC) $(LDFLAGS) -o testparse main.o $(OBJS) $(LIBS) \ + $(PROGS_LDFLAGS_EXTRA) maxpath: maxpath.o $(OBJS) - $(CC) $(LDFLAGS) -o maxpath maxpath.o $(OBJS) $(LIBS) + $(CC) $(LDFLAGS) -o maxpath maxpath.o $(OBJS) $(LIBS) \ + $(PROGS_LDFLAGS_EXTRA) sixdegrees: sixdegrees.o $(OBJS) - $(CC) $(LDFLAGS) -o sixdegrees sixdegrees.o $(OBJS) $(LIBS) + $(CC) $(LDFLAGS) -o sixdegrees sixdegrees.o $(OBJS) $(LIBS) \ + $(PROGS_LDFLAGS_EXTRA) stripkey: stripkey.o $(OBJS) - $(CC) $(LDFLAGS) -o stripkey stripkey.o $(OBJS) $(LIBS) + $(CC) $(LDFLAGS) -o stripkey stripkey.o $(OBJS) $(LIBS) \ + $(PROGS_LDFLAGS_EXTRA) gpgwww: gpgwww.o $(OBJS) - $(CC) $(LDFLAGS) -o gpgwww gpgwww.o $(OBJS) $(LIBS) + $(CC) $(LDFLAGS) -o gpgwww gpgwww.o $(OBJS) $(LIBS) \ + $(PROGS_LDFLAGS_EXTRA) lookup: lookup.o cleankey.o $(CORE_OBJS) $(KEYDB_OBJ) $(CC) $(LDFLAGS) -o lookup lookup.o cleankey.o $(CORE_OBJS) \ - $(KEYDB_OBJ) $(LIBS) + $(KEYDB_OBJ) $(LIBS) $(PROGS_LDFLAGS_EXTRA) add: add.o cleankey.o $(CORE_OBJS) $(KEYDB_OBJ) $(CC) $(LDFLAGS) -o add add.o cleankey.o \ - $(CORE_OBJS) $(KEYDB_OBJ) $(LIBS) + $(CORE_OBJS) $(KEYDB_OBJ) $(LIBS) $(PROGS_LDFLAGS_EXTRA) onak: onak.o cleankey.o $(CORE_OBJS) $(KEYDB_OBJ) $(CC) $(LDFLAGS) -o onak onak.o cleankey.o \ - $(CORE_OBJS) $(KEYDB_OBJ) $(LIBS) + $(CORE_OBJS) $(KEYDB_OBJ) $(LIBS) $(PROGS_LDFLAGS_EXTRA) onak-conf.o: onak-conf.c onak-conf.h $(CC) $(CFLAGS) -DCONFIGFILE=\@sysconfdir@/onak.conf\ -c onak-conf.c signature.asc Description: Digital signature
Bug#436983: python-django: pydoc django.db blows up
On Fri, Aug 10, 2007 at 08:59:04PM +0200, Raphael Hertzog wrote: On Fri, 10 Aug 2007, Mark Eichin wrote: As long as it stays open as a bug, that's fine; I suspect there *is* a way to work around it on the django side (for example, can it tell that pydoc is importing it?) There probably is (via the inspect package), but I wouldn't want to patch django.db to detect this corner use case. This module is a central one in Django and if I were the upstream author, I'd rather not put such hacks in it. Hmmm. Yes, it's central, but a lot of the rest of it works with pydoc - I can see why this particular use case doesn't, but I'll take a looksee tomorrow incase there is an easy solution (I don't think there is, I think Raphael is spot on...) or else there needs to be a way to fix it from the pydoc side... Even more ugly. :-) Patching pydoc for a specific library isn't really a choice. Very messy and would end up with pydoc having far too many overrides. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414399: Adding bash completion
A modified version of the patch (only needed the install file, debhelper.mk sorts out the dh_install), and a patch to the django_bash_completion file to take in to account the renaming of django-admin.py - django-admin are now in svn, along with a new upstream version (0.96). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411249: python-django: please package the documentation
The next upload will include the documentation - the patch to install it is in svn. -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409565: python-django: SVN version?
On Sun, Feb 04, 2007 at 01:01:47AM +0100, Vedran Fura?? wrote: Package: python-django Version: 0.95.1-1 Severity: wishlist Could you please package a SVN version and possibly upload it to experimental? It contains many new interesting features (newforms...). newforms is in the newforms branch, which is seperate - the recent 0.96 release, however, has newforms - I've commited the necessary files to svn and am just waiting for Raphael to check it over and upload the new version. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368557: Small Patch for Files bug in doc-base
Attached is a small patch to stop false positives from the documentation
check when Files: is over more than one line - it just uses strip to
remove the linefeed from the end of the line.
Cheers,
--
Brett Parker
--- linda-0.3.24/checks/documentation.py2006-04-26 06:23:33.0
+0100
+++ linda-0.3.24-new/checks/documentation.py2006-12-31 12:53:35.497176316
+
@@ -120,8 +120,9 @@
if stanza.has_key('files'):
for f in stanza['files'].split(' '):
fp = os.path.join(self.information['dir'], \
'unpacked', f[1:])
+fp = fp.strip()
if not glob.glob(fp) and not os.path.exists(fp):
self.signal_error('doc-base-file-not-found', \
['Files', f])
def check_devhelp(self):
Bug#401616: Info received (Bug#401616: python-django: manage.py is not executable and has no shebang)
It's now fixed in svn. -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401616: python-django: manage.py is not executable and has no shebang
On Mon, Dec 04, 2006 at 10:46:46PM +0100, Jonathan Ballet wrote: Package: python-django Version: 0.95-1 Severity: normal Hello, I just noticed that, when a new project is created, the 'manage.py' file created is not executable, and it has no shebang. The diff file of python-django's package seems to remove the shebang, I don't know for the executable flag. Why this behavior ? Hadn't noticed this behaviour, will try to fix in svn tomorrow and get a new upload ASAP. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354774: Django packaging
On Mon, Sep 18, 2006 at 03:16:07PM +0200, Raphael Hertzog wrote: Hello, On Wed, 17 May 2006, Brett Parker wrote: On Wed, May 17, 2006 at 07:13:48PM +0200, Matthias Urlichs wrote: Hello, you both indicated (Debian bugs #335246 and #354774) that you want to package Django. Well, I need it ... Questions: - progress? - any interim packages? - are you two aware of each other / working together? I plan on updating the trunk snapshots in the next week, and then I'll get back to making the packaging as nice as possible, at the moment it's reasonably good, and passes linda and lintian checks, but there's still more to do. I also would like to see Django integrated into Debian proper. Django is getting more and more press and the package deserves to be in unstable or experimental. I would strongly suggest that you start maintining this package in the python-modules subversion repository: http://python-modules.alioth.debian.org/ I can add you to the team if you agree. Just indicate me your Alioth login. I currently don't have one! Then, the first task will be to update the package to follow the new Python policy as even Brett's latest 0.95 package do not seem to be ready for release in unstable without that. I was looking at that this weekend, I should be able to sort the packaging on tuesday/wednesday evening and have new packages available then. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335246: Django packaging
On Mon, Sep 18, 2006 at 10:19:12PM +0200, Raphael Hertzog wrote: On Mon, 18 Sep 2006, Brett Parker wrote: I would strongly suggest that you start maintining this package in the python-modules subversion repository: http://python-modules.alioth.debian.org/ I can add you to the team if you agree. Just indicate me your Alioth login. I currently don't have one! http://alioth.debian.org/account/register.php Will do that tomorrow :) Then, the first task will be to update the package to follow the new Python policy as even Brett's latest 0.95 package do not seem to be ready for release in unstable without that. I was looking at that this weekend, I should be able to sort the packaging on tuesday/wednesday evening and have new packages available then. I have created an updated package already for my need: http://people.debian.org/~hertzog/packages/ Will check that out tomorrow! This package is compliant to the new policy. I removed the useless split between the media and the rest. The package is architecture all AFAICT, there was no good reason to split it. The origional split was because of the different versions of python and how old python policy worked, without the python-foo style directory, this would have needed a seperate package as otherwise you duplicate the admin media, which seemed a bit wasteful. I improved/extended the description. I added recommends of python-psycopg, python-sqlite and python-mysqldb. I used CDBS as it's very common within the Debian Python Modules Team and it simplifies a lot the work. Cool! I think the package is mostly ready as is, but you're welcome to further enhance it and to double check everything. I'll take a look tomorrow/wednesday - thanks for your assisstance! -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297698: Still relevant?
On Wed, Jun 07, 2006 at 02:44:46PM +0100, Dominic Hargreaves wrote: Hi, I don't use xmms-scrobbler any more, but just going through my old bug submissions. Did this get fixed or should the bug still be open? I don't think I've fixed it, and upstream appears to have gone quiet for a while, so leave it open for now and (hopefully) sometime in the next few weeks I'll find a suitable shaped tuit. Cheers, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354774: Django packaging
On Wed, May 17, 2006 at 07:13:48PM +0200, Matthias Urlichs wrote:
Hello,
you both indicated (Debian bugs #335246 and #354774) that you want to
package Django.
Well, I need it ...
Questions:
- progress?
- any interim packages?
- are you two aware of each other / working together?
I've got some preliminary packages sitting in a debian repository at:
http://www.sommitrealweird.co.uk/debian/ {sid,sarge,unstable,stable}
django
There are packages there of python-django-svn-trunk, python-django (the
last stable release, 0.91), a historical couple from the magic removal
branch and one snapshot package of trunk before magic removal was merged
in.
I plan on updating the trunk snapshots in the next week, and then I'll
get back to making the packaging as nice as possible, at the moment it's
reasonably good, and passes linda and lintian checks, but there's still
more to do.
Thanks,
--
Brett Parker
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353277: ndiswrapper in main
On Sat, Feb 18, 2006 at 05:36:37PM +0100, Mike Hommey wrote: On Sat, Feb 18, 2006 at 05:04:54PM +0100, Goswin von Brederlow The availability to do this is enough even if there are other (possibly better) ways to do the same. One free driver _in_ Debian and the package should stay in main. But does the cipe-source build or ship the windows driver for use with ndiswraper? I doubt that. Which means you need some software (even if it is free) from outside Debian for ndiswraper. That makes it contrib imho. Are there any free MSWord files in main ? No ? Then please move antiword and similar tools to contrib. *points at abiword and openoffice.org* -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335246: ITP: python-django -- A high-level Python Web framework
Package: wnpp Severity: wishlist Owner: Brett Parker [EMAIL PROTECTED] * Package name: python-django Version : 1.0.0 (when it's released) * URL : http://www.djangoproject.com/ * License : BSD Description : A high-level Python Web framework Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-9-amd64-k8 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#325603: beep-media-player-scrobbler: both beep media player and xmms crash on a certain song when trying to submit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Bruenggel [EMAIL PROTECTED] wrote: it works fine w/o the plugin. i can send u the mp3 if u need it. I also saw that there is another bug which looks simliar to my problem, but it is 174 days old (). So it would be cool if you could fix it Hmmm, can you try with 0.3.8.1-4, it's heading towards the official debian archive soon (once my sponser can build it on all the archs he has, which will be after beep-media-player has completed compiling on them), it's currently available from my repository on: deb http://www.sommitrealweird.co.uk/debian/ unstable scrobbler Or download the deb file from: http://www.sommitrealweird.co.uk/debian/dists/unstable/scrobbler/binary-i386/beep-media-player-scrobbler_0.3.8.1-4_i386.deb Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDE1blEh8oWxevnjQRAoN/AKCSaEfbc5kdYwngriPdiuV0UTAaGACffS4y wCNShNeatt1pIZM3vQrnVYY= =uLTQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322418: xmms-scrobbler: XMMS hangs when Scrobbler is enabled
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 William R Thomas [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.8.1-3 Severity: normal It seems that since libmusicbrainz4c2 has become available, xmms-scrobbler has started locking up xmms. At least as near as I can tell that is what is happening. If I disable the xmms-scrobbler plugin, xmms does not lock up, if it is enabled, xmms locks up within a couple of songs. Ahh, I can't currently recreate this problem, but it might not be libmusicbrainz4c2 at fault, as such... There's a potential race condition in xmms-scrobbler when used with a 2.6.x kernel which I'm currently working on, there have been other reports of this to the upstream maintainer, and there is a patch that I'll apply ready for the next release. I'll try to dig it out this evening for you, and build a test package. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC+z5zEh8oWxevnjQRAviLAJ4ogrfji3zlr1M5eR5eYOhqKjTYQQCePFRk 1Wy7wRLYdN6wo5BPDNWc2T4= =sEbF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292930: xmms-scrobbler locking up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baruch Even [EMAIL PROTECTED] wrote: Hi, I had similar problems and I believe the two bugs are actually one and the same. I've solved my problems with the two patches attached. One will change the mutexes, I fear they are done badly in the original code. I'll take a look around and see what I can see, I'll take a look at the patch over the next week. The other will fix the id3v2 tag reading, it will not find such a tag if it's not right at the start, but I don't think we should replicate the logic and just find some library to do this correctly. Agreed, I've been meaning to talk to Pipian about using other libraries to read the tags, I'll look around when I've got some spare time. There's been numerous bugs in the handling of various tags so far, so we really should use a neater method. This second patch solved my problems and is the prime suspect for the two bugs this mail is sent to. Right, I'll look as soon as I've got some spare time, and check that the patch is sane. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCdoRGEh8oWxevnjQRAo/yAJ4rruoskV7UlqgJq7a+MkbDk3CzzACgpH3Z pIjubrmFuUgaLqAVtsR0RIo= =n7Ue -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298578: xmms-scrobbler: makes xmms crash with certain songs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brett Parker [EMAIL PROTECTED] wrote: Pieter Naaijkens [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.7-1 Severity: important I have some songs that make XMMS crash when the audioscrobbler plugin is trying to read the tag information. When I disable the plugin, everything works fine. The audioscrobbler debug messages aren't of any help. Here is a backtrace: Thanks, I think that's on upstreams list for 0.3.8, I'll take a look and double check. I'll be building the new plugin very shortly. Right, 0.3.8.1 is now in the unstable tree (it's waiting on the arm buildd to get in to testing), can you test and confirm if the bug still exists in the new plugin? Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCUGoGEh8oWxevnjQRAkWuAKC+Pkwneq1xufGnIK6CtBpJcFe7cQCeNjq1 fmzqJAaZGVA9sZicSqDa+ZM= =Aczb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300915: First Playlist Track
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.7-1 The plugin repeatedly reports the first track in my playlist to audioscrobbler.com, though I never play it. I've seen mention of this on the forums, I'll take a look about and see what I can spot, Pipian is getting close to another release, so I'll take a look at his new version to see what's changed. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCQHenEh8oWxevnjQRAroxAJsHCdqkOPfCmRghL7+NSXIzUMcuMACghByl RLcb+0W2T8zWBzaZMLGD+6I= =XrfJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292930: Hung XMMS when disabling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anthony DeRobertis [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.6-1asd3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I attempted to disable the plugin using XMMS's preferences, and when I clicked the checkbox XMMS hung (though music kept playing until the current ogg was over). Is this fixed in 0.3.7-1? If not I'll take a look at it in the next few days, certainly upstream noticed this with 0.3.6 and they were hoping that it had been cleared by 0.3.7. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCOuoGEh8oWxevnjQRAiq/AKC+YQVr0RH/Jlpj2bGm+IPf9NJt1ACfcnWH s6j7uJ3ksCR//epJdthjXLw= =qDQk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298578: xmms-scrobbler: makes xmms crash with certain songs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pieter Naaijkens [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.7-1 Severity: important I have some songs that make XMMS crash when the audioscrobbler plugin is trying to read the tag information. When I disable the plugin, everything works fine. The audioscrobbler debug messages aren't of any help. Here is a backtrace: Thanks, I think that's on upstreams list for 0.3.8, I'll take a look and double check. I'll be building the new plugin very shortly. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCOut6Eh8oWxevnjQRAmEzAJ9HggCklQ67RXoQfvpB83r1Lkr9OwCglZ9J ASXoSuHSOFV1bL07xwPw3JQ= =wrwx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300226: xmms-scrobbler: Won't load in sarge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reuben Thomas [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.6-1 Severity: important xmms-scrobbler seems to have a linking problem: I get the error: /usr/lib/libcurl.so.3: undefined symbol: tld_strerror when I run xmms with xmms-scrobbler installed, and xmms-scrobbler doesn't show up anywhere in the plugins list. I'll look in to this, unless it's started working for you now? Alternatively, in the next week or so, version 0.3.7-1 should filter through to testing. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCOuv0Eh8oWxevnjQRAo8GAJ46v27/ic3cwI+p2Tny+VA2gpNQywCeIVoI 0WpEp/l/Wsj32TZ4LL3jD1o= =KUak -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297698: xmms-scrobbler: Does not behave sensibly when username/password is wrong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dominic Hargreaves [EMAIL PROTECTED] wrote: Package: xmms-scrobbler Version: 0.3.6-1 Severity: normal When an incorrect username/password is supplied to the plugin, it continues to resubmit apparently indefinitely (at a rate of once every 1-2 seconds) until xmms is stopped. Extract of log file: Hadn't noticed that, I'll take a look, I'm not sure if it got fixed in the latest 0.3.7 that just got in to unstable. I should be able to have a proper look sometime over the next week. Thanks, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCKyqAEh8oWxevnjQRAtyMAJ91M4Q56RVM8DXL0NnoEG/chSb7/ACffAXW ri2gcUxjcUZRr3H7XDQt3Qc= =siW3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#294340: xmms-scrobbler: plugin doesn't work
Hi Thomas, On Thu, Feb 10, 2005 at 06:50:34AM +0100, Thomas Labourdette wrote: me-audioscrobbler : GET /?hs=truep=1.1c=xmsv=0.3.7u=tlabourdette HTTP/1.1 Host: post.audioscrobbler.com Pragma: no-cache Accept: */* That just looks like a handshake to get the cookie returned below... it's not trying to submit anything there. audioscrobbler-me : HTTP/1.0 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=16BC56DA9F3CFCF9CFC012C4B72654D2; Path=/ Content-Type: text/plain;charset=ISO-8859-1 Date: Thu, 10 Feb 2005 05:37:39 GMT X-Cache: MISS from proxy.labourdette.homelinux.com X-Cache-Lookup: MISS from proxy.labourdette.homelinux.com:3128 Connection: close UPTODATE 16BC56DA9F3CFCF9CFC012C4B72654D2 http://post.audioscrobbler.com:80/protocol_1.1 INTERVAL 1 That looks like a usual type response to me. So I find it odd that it's not working for you. The plugin will not submit any track data until it is either 2 mins or half way through (which ever comes first), and will not submit data about tracks that are 30 seconds or shorter. Also, be aware that it will not submit data about radio streams, even ones with correct meta data, as this is not allowed by AudioScrobbler. Only local (on your filesystem) mp3 and ogg files, and wma files will be submitted, as well as CD Audio. Can you confirm that you are playing from a local music source? (gnump3d does not count here, as it uses http to send the data to the client, which xmms-scrobbler would then ignore). Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#294340: xmms-scrobbler: plugin doesn't work
On Wed, Feb 09, 2005 at 11:04:00AM +0100, Thomas Labourdette wrote: Package: xmms-scrobbler Version: 0.3.6-1 Severity: important The plugin doesn't seems to work at all. It's exactly like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285377 There's a new version of the plugin in my repository, that's just headed towards my uploader for uploading to unstable (though, we're currently stuck in the NEW queue again as we're moving scrobbler to main). Could you test with the new package and get back to me? My repository can be used by adding the following to /etc/apt/sources.list: deb http://www.sommitrealweird.co.uk/debian/ unstable scrobbler Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290128: I suspect this is the broken endian.h file
On Wed, Jan 26, 2005 at 07:33:45PM -0500, Anthony DeRobertis wrote: Package: xmms-scrobbler Followup-For: Bug #290128 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The broken macros in endian.h create absurd results when dealing with numbers 127 due to assuming char is unsigned. Basically, it returns a really large number (e.g., several gigs), which is then passed to malloc. malloc (naturally) returns NULL on 32-bit archs. The result of malloc is not tested (ugh...), and then a memcpy to NULL is attempted. [The results would be different, possibly worse, on a 64-bit arch where the malloc could succeed.] Thanks for the info, I'll try to work on it shortly, I'm currently still waiting for xmms-scrobbler to come back out of NEW (it's moving to main), but I'll work on it as soon as I've got some time. If you change debian/rules to do: CFLAGS=$(CFLAGS) configure ... (you should probably do this anyway) and then export DEB_BUILD_OPTS='noopt,nostrip' dpkg-buildpackage -rfakeroot -b -uc install the resulting package, and you can easily watch the crash by running xmms (or I assume bmp) under ddd. The backtrace the reporter provided is wrong due to compiling with optimizations (ok, not wrong, but misleading). See my post on the AudioScrobbler forums: http://www.audioscrobbler.com/forum/4/_/18676 I've patched it locally as shown in that post; that's the only reason most of my music doesn't crash xmms. PS: glib provides, I believe, endian conversion functions; any reason not to use those? I'll have to think about this one. PS(2): ALWAYS check the result of malloc. malloc hates you. malloc will fail when you least expect it. Agreed, I'm still going through the code and trying to make sure that there are checks in place, it seems insane to kill xmms when we could just discard the tag in a neat manner. PS(3): Doesn't libvorbis or libvorbisfile already have things for reading Vorbis tags? Any reason not to use it? It appears that the upstream guys use as few external libraries as is humanly possible for the plugin, which is probably why that's not linked in. I'll take a look when I get some time. -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
