date:20110919

Timo Juhani Lindfors wrote:

> Michael Gilbert  writes:
> > Is there any reason to keep this bug open just for an innocuous
> > message?
> 
> Not sure but hmm, what makes you think this is innocuous?  Now that I
> grep the code I find only two fragments that mention it but both have
> exit(1) after them:
> 
> void *gmallocn(int nObjs, int objSize) GMEM_EXCEP {
>   int n;
> 
>   if (nObjs == 0) {
> return NULL;
>   }
>   n = nObjs * objSize;
>   if (objSize <= 0 || nObjs < 0 || nObjs >= INT_MAX / objSize) {
> #if USE_EXCEPTIONS
> throw GMemException();
> #else
> fprintf(stderr, "Bogus memory allocation size\n");
> exit(1);
> #endif
>   }
>   return gmalloc(n);
> }
> 
> void *greallocn(void *p, int nObjs, int objSize) GMEM_EXCEP {
>   int n;
> 
>   if (nObjs == 0) {
> if (p) {
>   gfree(p);
> }
> return NULL;
>   }
>   n = nObjs * objSize;
>   if (objSize <= 0 || nObjs < 0 || nObjs >= INT_MAX / objSize) {
> #if USE_EXCEPTIONS
> throw GMemException();
> #else
> fprintf(stderr, "Bogus memory allocation size\n");
> exit(1);
> #endif
>   }
>   return grealloc(p, n);
> }
> 
> strace does not show exit(1) so this warning must be coming from
> something else?

poppler.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#504489: xpdf: "Bogus memory allocation size"

2011-09-19 Thread Timo Juhani Lindfors

Michael Gilbert  writes:
> Is there any reason to keep this bug open just for an innocuous
> message?

Not sure but hmm, what makes you think this is innocuous?  Now that I
grep the code I find only two fragments that mention it but both have
exit(1) after them:

void *gmallocn(int nObjs, int objSize) GMEM_EXCEP {
  int n;

  if (nObjs == 0) {
return NULL;
  }
  n = nObjs * objSize;
  if (objSize <= 0 || nObjs < 0 || nObjs >= INT_MAX / objSize) {
#if USE_EXCEPTIONS
throw GMemException();
#else
fprintf(stderr, "Bogus memory allocation size\n");
exit(1);
#endif
  }
  return gmalloc(n);
}

void *greallocn(void *p, int nObjs, int objSize) GMEM_EXCEP {
  int n;

  if (nObjs == 0) {
if (p) {
  gfree(p);
}
return NULL;
  }
  n = nObjs * objSize;
  if (objSize <= 0 || nObjs < 0 || nObjs >= INT_MAX / objSize) {
#if USE_EXCEPTIONS
throw GMemException();
#else
fprintf(stderr, "Bogus memory allocation size\n");
exit(1);
#endif
  }
  return grealloc(p, n);
}

strace does not show exit(1) so this warning must be coming from
something else?

-Timo



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642188: ITP: libtravel-routing-de-vrr-perl -- unofficial interface to the efa.vrr.de German itinerary service

2011-09-19 Thread Maximilian Gass

Package: wnpp
Owner: Maximilian Gass 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: libtravel-routing-de-vrr-perl
  Version : 1.06
  Upstream Author : Daniel Friesel 
* URL : http://search.cpan.org/dist/Travel-Routing-DE-VRR/
* License : WTFPL
  Programming Lang: Perl
  Description : unofficial interface to the efa.vrr.de German itinerary 
service

Travel::Routing::DE::VRR is a client for the efa.vrr.de web interface. You
pass it the start/stop of your journey, maybe a time and a date and more
details, and it returns the up-to-date scheduled connections between those
two stops.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#504489: xpdf: "Bogus memory allocation size"

Timo Juhani Lindfors wrote:

> Michael Gilbert  writes:
> > I do get the "Bogus memory allocation size" message, but I just don't
> > get a crash afterward (tested on amd64 and i386).  Can you capture a
> > backtrace?  Also, can you send updated system information for your
> > machine (easiest to generate with reportbug)?
> 
> Ah that's true, it only prints the error message but does not actually
> crash.

Is there any reason to keep this bug open just for an innocuous message?

Thanks,
Mike



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642005: general: maximum size of SHM memory blocks to low

2011-09-19 Thread Henrique de Moraes Holschuh

reassign 642005 linux-2.6
thanks

On Mon, 19 Sep 2011, Evgeni Golov wrote:
> On 09/19/2011 03:12 AM, Henrique de Moraes Holschuh wrote:
> > On Sun, 18 Sep 2011, Evgeni Golov wrote:
> >> On 09/18/2011 04:46 PM, Henrique de Moraes Holschuh wrote:
> >>> Reassigning to Debian live-config, please reassign elsewhere if
> >>> innapropriate.  Note that non-live Debian installs have fairly large SHM
> >>> limits (kernel default, which is half your RAM on Linux), don't reassign
> >>> this to initscripts.
> >>
> >> 32MiB is not half of my 8GB RAM :)
> > 
> > Since it was not the kernel who set it to 32MiB, that's hardly surprising, I
> > should say :-p
> > 
> > Squeeze's initscripts use the kernel default (50% of your RAM).  unstable's
> > initscripts will set it to 20% of your RAM.  If it is not live-config which
> > is forcing it to 32MiB, please track down whatever is doing it, and reassign
> > the bug...
> 
> Mhh, I can't find *any* reference to shmmax in /etc (neither on Squeeze,
> nor Sid). Are we talking the *same* SHM? Roger pointed out there are two
> kinds of it.

Good call!  The kernel limits for the ipc-based shm is entirely
untouched by Debian, and the kernel defaults are to limit it to
32MiB-wide chunks (shmmax) out of a system-wide limit of 8GiB (pagesize
* shmmax).

It is that low because that memory is _NOT_ freed on process exit, and
therefore it can leak way too easily.  It has also a long tradition of
being really small by default on all Unixen.

Meh.  I doubt we will touch that default, but I don't really care
strongly in one way or the other.  Reassigning to the kernel.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#504489: xpdf: "Bogus memory allocation size"

2011-09-19 Thread Timo Juhani Lindfors

Michael Gilbert  writes:
> I do get the "Bogus memory allocation size" message, but I just don't
> get a crash afterward (tested on amd64 and i386).  Can you capture a
> backtrace?  Also, can you send updated system information for your
> machine (easiest to generate with reportbug)?

Ah that's true, it only prints the error message but does not actually
crash.

-Timo



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642187: [vlc] Should recommend package libdvdcss2cd

2011-09-19 Thread Alex Henry

Package: vlc
Version: 1.1.3-1squeeze6
Severity: normal

--- Please enter the report below this line. ---
Should recommend package libdvdcss2 to allow DVD playback (as stated
in the description).


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.32-5-686

Debian Release: 6.0.2
  500 stable-updates  ftp.br.debian.org
  500 stable  www.las.ic.unicamp.br
  500 stable  security.debian.org
  500 stable  debian.las.ic.unicamp.br

--- Package information. ---
Depends(Version) | Installed
-+-===
ttf-freefont | 20090104-7
vlc-nox  (= 1.1.3-1squeeze6) | 1.1.3-1squeeze6
libaa1(>= 1.4p5) | 1.4p5-38
libc6   (>= 2.8) | 2.11.2-10
libfreetype6  (>= 2.2.1) | 2.4.2-2.1+squeeze1
libfribidi0  (>= 0.19.2) | 0.19.2-1
libgcc1 (>= 1:4.1.1) | 1:4.4.5-8
libgl1-mesa-glx  | 7.7.1-4
 OR libgl1   |
libqtcore4  (>= 4:4.6.1) | 4:4.6.3-4+squeeze1
libqtgui4   (>= 4:4.5.3) | 4:4.6.3-4+squeeze1
libsdl-image1.2  (>= 1.2.10) | 1.2.10-2+b2
libsdl1.2debian(>= 1.2.10-1) | 1.2.14-6.1
libstdc++6(>= 4.2.1) | 4.4.5-8
libtar   | 1.2.11-6
libvlccore4   (>= 1.1.0) | 1.1.3-1squeeze6
libx11-6 | 2:1.3.3-4
libx11-xcb1  | 2:1.3.3-4
libxcb-keysyms1   (>= 0.3.6) | 0.3.6-1
libxcb-randr0   (>= 1.1) | 1.6-1
libxcb-shm0  | 1.6-1
libxcb-xv0  (>= 1.2) | 1.6-1
libxcb1  | 1.6-1
libxext6 | 2:1.1.2-1
zlib1g   (>= 1:1.2.3.3.dfsg) | 1:1.2.3.4.dfsg-3
ttf-freefont | 20090104-7
vlc-nox  (= 1.1.3-1squeeze6) | 1.1.3-1squeeze6
libaa1(>= 1.4p5) | 1.4p5-38
libc6   (>= 2.8) | 2.11.2-10
libfreetype6  (>= 2.2.1) | 2.4.2-2.1+squeeze1
libfribidi0  (>= 0.19.2) | 0.19.2-1
libgcc1 (>= 1:4.1.1) | 1:4.4.5-8
libgl1-mesa-glx  | 7.7.1-4
 OR libgl1   |
libqtcore4  (>= 4:4.6.1) | 4:4.6.3-4+squeeze1
libqtgui4   (>= 4:4.5.3) | 4:4.6.3-4+squeeze1
libsdl-image1.2  (>= 1.2.10) | 1.2.10-2+b2
libsdl1.2debian(>= 1.2.10-1) | 1.2.14-6.1
libstdc++6(>= 4.2.1) | 4.4.5-8
libtar   | 1.2.11-6
libvlccore4   (>= 1.1.0) | 1.1.3-1squeeze6
libx11-6 | 2:1.3.3-4
libx11-xcb1  | 2:1.3.3-4
libxcb-keysyms1   (>= 0.3.6) | 0.3.6-1
libxcb-randr0   (>= 1.1) | 1.6-1
libxcb-shm0  | 1.6-1
libxcb-xv0  (>= 1.2) | 1.6-1
libxcb1  | 1.6-1
libxext6 | 2:1.1.2-1
zlib1g   (>= 1:1.2.3.3.dfsg) | 1:1.2.3.4.dfsg-3
liba52-0.7.4 | 0.7.4-14
libasound2   (>> 1.0.18) | 1.0.23-2.1
libass4   (>= 0.9.7) | 0.9.9-1
libavahi-client3 (>= 0.6.16) | 0.6.27-2+squeeze1
libavahi-common3 (>= 0.6.16) | 0.6.27-2+squeeze1
libavc1394-0  (>= 0.5.3) | 0.5.3-1+b2
libavcodec52 (>= 4:0.5.1-1)  | 5:0.6.1+svn20101128-0.2
 OR libavcodec-extra-52   (>= 4:0.5.1-1) |
libavformat52(>= 4:0.5.1-1)  | 5:0.6.1+svn20101128-0.2
 OR libavformat-extra-52  (>= 4:0.5.1-1) |
libavutil49  (>= 4:0.5.1-1)  | 4:0.5.2-6
 OR libavutil-extra-49(>= 4:0.5.1-1) |
libc6   (>= 2.8) | 2.11.2-10
libcaca0  (>= 0.99.beta17-1) | 0.99.beta17-1
libcddb2 | 1.3.2-2
libcdio10| 0.81-4
libdbus-1-3   (>= 1.0.2) | 1.2.24-4+squeeze1
libdc1394-22 | 2.1.2-3
libdca0  | 0.0.5-3
libdirac-encoder0| 1.0.2-3
libdvbpsi6(>= 0.1.

Bug#617943: debian-installer: isolated "make build_netboot" fails due to missing 2.6.32 modules

Otavio Salvador wrote:
> The installer itself, sometimes, need modifications or fixes to be able to
> handle newer kernel versions so the version that is hard-coded on those is
> the version that is supported by the installer. It is not only a matter of
> recompile installer against the new kernel (sometimes this works by this is
> not guaranteed). Another important point is that there are architectures
> that use different kernels depending on the subarch (e.g armel uses iop32x,
> kirkwood and others) and dynamically it is more difficult to handle this.
> 
> Specifically about the patch it is incomplete since it doesn't handle all
> the architectures thus we can't take it.

Hi,

Sorry I haven't had time to get back to this until just now.  

So, I don't have any of the subarch's to test this, but I believe they
are already handled appropriately in the "UDEBS =" line in my patch.
I'm concluding this based on the .cfg files, for example iop32x.cfg
would produce 2.6.32-5 for the KERNELIMAGEVERSION var, and that is what
I would automatically return from the automatic processing of the
Packages file.

Will it ever be the case that the kernel version as stated in the
debian-installer_binary-ARCH_Packages file will differ from the
hard-coded value in the cfg files?  It seems like they would have to be
the same, otherwise d-i would fail trying to download non-existent
files, but I may be missing something.

Best wishes,
Mike

-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642186: nunit: FTBFS: "net-1.1" is not a valid framework identifier

2011-09-19 Thread Daniel Schepler

Source: nunit
Version: 2.4.7+dfsg-6
Severity: serious

From my pbuilder build log:

...
 fakeroot debian/rules clean
dpatch  deapply-all  
07_disable_trace_listener not applied to ./ .
06_use_default_encoding not applied to ./ .
05_build_xml_doc_for_nunit.core not applied to ./ .
04_enable_building_gui_runner not applied to ./ .
03_disable_building_fit_fixtures not applied to ./ .
02_gui not applied to ./ .
rm -rf patch-stamp patch-stampT debian/patched
rm -rf build
rm -f build-stamp
nant /f:src/nunit.build mono-2.0 clean-all
NAnt 0.91 (Build 0.91.3881.0; alpha2; 08/17/2010)
Copyright (C) 2001-2010 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///tmp/nunit/nunit-2.4.7+dfsg/src/nunit.build
Target framework: Mono 2.0 Profile
Target(s) specified: mono-2.0 clean-all 

Function platform::is-win32 is deprecated.  Use the is-windows function instead.
Function platform::is-win32 is deprecated.  Use the is-windows function instead.

BUILD FAILED - 0 non-fatal error(s), 2 warning(s)

Function call failed.
Expression: ${framework::sdk-exists( framework )}
  ^^
"net-1.1" is not a valid framework identifier.

Total time: 0.2 seconds.

make: *** [clean] Error 1
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
-- 
Daniel Schepler



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641769: [apt] fetches InRelease file, problematic on several mirrors (aka "Packages Hash Sum mismatch")

2011-09-19 Thread Filipus Klutiero


Le 2011-09-17 05:18, David Kalnischkies a écrit :

On Fri, Sep 16, 2011 at 19:44, Filipus Klutiero  wrote:

If you decrease the time between the dinstall (or equivalent) runs to lets
say
an hour as e.g. ubuntu does you get far more likely in situations in which
Release and Release.gpg doesn't belong together. Thats specifically one of
the reasons ftpmasters implemented it in 2009.

So, you are currently experience mirror-problems because we want to
protect you from mirror problems in the future. Crazy, heh? ;)

Could you clarify what incoherence scenario InRelease avoids? It is true
that Release and Release.gpg need to be either versioned or updated
simultaneously, but this problem applies to all files used to fetch indices,
which are all updated during stage 1 (except for InRelease). Therefore the
duration of incoherence should be insignificant in comparison to the problem
with InRelease.

Be careful with your guesses. If it would be that insignificant, why was it
implemented by ftpmasters?
I did specify "in comparison to the problem with InRelease", and as 
previously discussed, eliminating an HTTP request improves performance. 
This might also have more long-term advantages.

Also you are just looking at mirror sync,
the world consists of more than just mirror syncs! We have the creation
of these files for example which is far from being atomic at the moment.
So, could you show a scenario where non-atomatic creation of these files 
constitutes a problem?

Also, if you want to follow this route, from a security point is an InRelease
file better as a man-in-the-middle could drop the request for Release.gpg -
the archive has no signature then and APT will cry for an extra-yes, but
many users are pretty fast in pressing yes -- especially as they are
used to having these questions as not every thirdparty archive provides
a good signature… But for a real attack he would properly send modified
Release and co and doesn't respond to Release.gpg. Try that with
InRelease - sure, as we need to support the "old" way for a while these
kind of attacks can still be executed and dropping all requests for files
related to Release is a possibility, too, but one step at the time.
The problem of users getting used to this kind of prompts can be tackled 
by either {encouraging,making it easy for} third-party repositories to 
provide signatures, or by preventing users from needing third-party 
repositories.


If you still think administrators are too dumb for these prompts to be 
worth the security risk they pose, you could either request APT to 
simply fail when no signature is provided (at least for official 
sources), or to have prompts which get more attention (red text, "Yes, 
/do as I say/!", etc.).


Anyway, this issue is hopefully a short-term one.



So with disabling InRelease we would just hide the underlying problem,
this can't be a solution, especially not that early in the releasecycle.
After all, we are talking about unstable-only here.

I'm not sure what problem we would be "hiding" here. Mirrors using ftpsync
versions that don't handle InRelease correctly is only a problem insofar as
APT uses InRelease with problematic ftpsync versions...

That's a pretty short view. Forget InRelease for a moment: Are you really
willing to use a mirror there the admins didn't care? I am not.
If they are that sloppy to use old update-scripts, can i be sure that they
are not going to silently stop running their old scripts all together?
I am not using any specific mirror. Before I had to debug this issue, I 
was using my country's official mirrors round-robin. It may be a sad 
state of affairs that official mirrors do not have better 
administration, but that is the way it currently is.


I am not sure that my mirror won't stop updating, but that is the case 
for [almost] all Debian systems. APT is still in development and does 
not yet behave appropriately with mirrors.


As I said, there is not even a definition of what is an "old" ftpsync 
version. To a mirror administrator, using ftpsync 80286 may not appear 
worst than using apt 0.8.10.

You are later talking about versioning and co, how should it be possible
to use that if we are unable to use a single file after three years - or if
we want to be a bit more fair after eight months?

Not every damn feature should need six years before it can be used,
at least the last time i checked the file isn't called MultiRelease…
6 months is nothing in Debian development. Even if InRelease usage is 
reintroduced in this release cycle, it won't be generally used before at 
least another year.


I am not arguing that any specific time should be waited. I'm hoping 
that mirrors are updated quickly and that InRelease can be used quickly, 
but this needs works. I don't know how long it can take.


It is easy to add versioned indices even with non-cooperative mirrors. 
If several versions are kept, APT can just use the latest index version 
which has a complete set of index files.



As I

Bug#642185: remove Documentation.html symlink from /usr/share/phpmyadmin

2011-09-19 Thread Moonwalker

Package: phpmyadmin
Version: 3.4.5-1

Documentation.html page of any phpMyAdmin installation discloses its version 
number to any user. Meanwhile, most of the documentation contents are actually 
useless for ordinary database users. I think you should consider removing it 
from public access through HTTP server.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642184: init.d status support

2011-09-19 Thread Peter Eisentraut

Package: unattended-upgrades
Version: 0.72.3
Severity: wishlist
Tags: patch

Here is a patch to add the "status" action to the init script.  Even
though it's trivial, please consider including it so we can uniformly
support the "status" action across all packages.
diff -Nru unattended-upgrades-0.72.3/debian/changelog unattended-upgrades-0.72.3+nmu1/debian/changelog
--- unattended-upgrades-0.72.3/debian/changelog	2011-06-16 10:13:49.0 +0300
+++ unattended-upgrades-0.72.3+nmu1/debian/changelog	2011-09-20 06:27:24.0 +0300
@@ -1,3 +1,10 @@
+unattended-upgrades (0.72.3+nmu1) unstable; urgency=low
+
+  * debian/unattended-upgrade.init:
+- add support for "status" action
+
+ -- Peter Eisentraut   Tue, 20 Sep 2011 06:26:29 +0300
+
 unattended-upgrades (0.72.3) unstable; urgency=low
 
   * debian/rules:
diff -Nru unattended-upgrades-0.72.3/debian/unattended-upgrades.init unattended-upgrades-0.72.3+nmu1/debian/unattended-upgrades.init
--- unattended-upgrades-0.72.3/debian/unattended-upgrades.init	2011-03-04 14:15:27.0 +0200
+++ unattended-upgrades-0.72.3+nmu1/debian/unattended-upgrades.init	2011-09-20 06:26:24.0 +0300
@@ -26,9 +26,12 @@
   restart|force-reload)
 	# nothing
 	;;
+  status)
+	exit 0
+	;;
   *)
 N=/etc/init.d/$NAME
-echo "Usage: $N {start|stop|restart|force-reload}" >&2
+echo "Usage: $N {start|stop|restart|force-reload|status}" >&2
 exit 1
 ;;
 esac

Bug#642183: debian-installer: hybrid iso sizing issue for unstable build

package: debian-installer
version: 20110106
severity: important
tags: patch

d-i fails to build unstable x86 netboot images (see below), which
will become a problem as d-i development moves forward with newer
kernels/packages coming in from unstable.  I've attached a patch
that fixes this by using the default last sector for the msdos
partition instead of a size offset.  This certainly works, but I'm
not sure if its an ideal solution.

Best wishes,
Mike

$ cd build && USE_UDEBS_FROM=unstable make build_netboot
geniso_hybrid_plus_firmware_partition ./tmp/netboot/mini.iso
mkfs.msdos 3.0.9 (31 Jan 2010)

Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4, default 2): First sector (24576-36863, default 24576): 
Using default value 24576
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Value out 
of range.
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Last 
sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Value out of 
range.
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Value out 
of range.
Last sector, +sectors or +size{K,M,G} (24576-36863, default 36863): Last 
sector, +sectors or +size{K,M,G} (24576-36863, default 36863): 
make[2]: *** [arch_miniiso] Error 1
make[1]: *** [_build] Error 2
make: *** [build_netboot] Error 2
--- util/geniso_hybrid_plus_firmware_partition.orig	2011-09-19 23:27:56.0 -0400
+++ util/geniso_hybrid_plus_firmware_partition	2011-09-19 23:28:06.0 -0400
@@ -49,7 +49,7 @@
 echo p
 echo 2
 echo 
-echo +"$firmware_volume_size_M"M
+echo
 
 # Pedantically, set partition type to 1: FAT 16
 echo t

Bug#642117:

2011-09-19 Thread Simon

Just to confirm this bug, I'm having the same issue on Wheezy with AIM,
MSN and XMPP accounts.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641981: midori: The "return" arrow in the URL address bar exits the browser rather than fetching the web address.

2011-09-19 Thread Yves-Alexis Perez

On lun., 2011-09-19 at 21:18 +0100, Alan Lucas wrote:
> Hi Yves
> The version I have is 0.2.4-3 

Oh, that likely means it's fixed in later version.
-- 
Yves-Alexis


signature.asc
Description: This is a digitally signed message part

Bug#641069: [ehci_hcd] reset high speed USB device using ehci_hcd

2011-09-19 Thread Laurent Besson


Le 16/09/2011 23:40, Jonathan Nieder a écrit :

retitle 641069 ehci_hcd resets when copying data to/from Samsung Wave II, 
copying stalls (USB1 works ok)
tags 641069 - moreinfo
quit

Hi Laurent,

Laurent Besson wrote:


There's some freeze when copied data from or to this storage (Samsung Wave
II)
But a friend of mine had the same message for his mouse, and when it hapened
the mouse stop moving during 1-2-3-4 seconds...
It's difficult to produce this, because it's erratic (sometimes work and
after not... ?)

A solution on debian is to remove module when I plug my smartphone (then I
copied with 1-2Mb/s) , when it's finished I remove my smartphone and reload
module... It's not really clean... but works !

Quick questions:

  - can you reproduce this with your friend's mouse (or any other
mouse)?  If not, could your friend file a separate report so we can
get to know his hardware?
  - please attach output from

/usr/share/bug/linux-image-$(uname -r)/script 3>&1
  - please also test a recent kernel (3.x) from sid or experimental.  It
should not require any other packages from sid except for
linux-base and initramfs-tools.

If this is reproducible with a recent kernel, we should pass this
upstream (I guess that is linux-...@vger.kernel.org, cc-ing Alan Stern
  and this bug log).  Otherwise, we can try
to find the fix and backport it.

Thanks,
Jonathan

Hi

Thank's for your response, I can reproduce this with the friend's mouse 
because I could take on my PC and have the same bug !
I will send (today at job) output when i plug this, and 
/usr/share/bug/linux-image-$(uname -r)/script


Ok



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#636292: Bug#641769: [apt] fetches InRelease file, problematic on several mirrors (aka "Packages Hash Sum mismatch")

2011-09-19 Thread Filipus Klutiero


Le 2011-09-17 11:34, Henrique de Moraes Holschuh a écrit :

retitle 636292 dak/apt: deficiencies at handling out-of-sync metadata
summary 636292 87
thanks

If anyone disagrees with the above triage, please change the summary
and/or title.  Thank you.

On Sat, 17 Sep 2011, Filipus Klutiero wrote:

#636292 is labelled as being about round-robin mirrors and problems
APT has with those, even though that is probably not the actual
cause of the reporter's problem.

You're expected to read the entire thing when refered to a bug report in
a thread you're replying to.

I was unaware of that.

[...]

But indeed, there would be room for a general bug "unreliable
package indices fetching protocol" :-S

That misses the point, IMO.  To me, it looks like what's "broken" is
that the repository format _and_ the front-ends have deficiencies at
handling metadata which is unsyncronized either in-mirror or across
mirrors.  And these deficiencies are a lot more important nowadays than
they once were, as we have now many dinstall runs per day, lots of users
tracking testing and unstable, a larger set of metadata files, a larger
and more diverse set of mirrors... I.e: a lot more chances to hit
unsyncronized metadata windows.


I don't think increasing dinstall frequency worsens these issues 
significantly if dinstalls get shorter (unless previous dinstalls ran 
during the night). I also think archive size growth should have been 
compensated by performance increases. I think the time spent 
synchronizing a mirror must not have increased a lot. What did change 
here (dramatically) is the proportion of that time where APT indices 
updates fail. Round-robin mirrors might also have worsened.


Anyway, the repository format is not a problem per se, it's the 
combination of what's on a mirror and how APT fetches it that's a 
problem. If you assume the communication protocol is HTTP-like, then 
indeed there should be mechanisms to cope with race conditions - i.e. 
file versioning and/or having APT retry or report desynchronizations.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#610722: should be fixed now

2011-09-19 Thread Victor Mataré

I've just put thinkfan 0.7.3 on sf.net, which (I hope) will eliminate all 
problems with 
using 127 or -2147483648 as a fan level.

signature.asc
Description: This is a digitally signed message part.

Bug#641886: Fixed upstream


package mdadm
tag 641886 +fixed-upstream
thanks

Upstream commit 3f555346fb26b7ee7447b004ecb2c2d57f243867




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#635356: pychess: diff for NMU version 0.10-1.1

2011-09-19 Thread Varun Hiremath

On Sat, 17 Sep, 2011 at 06:03:22PM +0200, Luca Falavigna wrote:
> Dear Varun,
> 
> I've prepared an NMU for pychess (versioned as 0.10-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Dear Luca,

Thanks for the NMU! There was a new upstream release, so I just now
uploaded a new version to sid which should take care of this.

Thanks for your time, and sorry for the delay.

Thanks,
Varun

-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#637068: Proper patch





package mdadm
tag 637068  +patch
thanks

Proper patch attached



diff --git a/debian/FAQ b/debian/FAQ
index 189f0e7..6ec1c11 100644
--- a/debian/FAQ
+++ b/debian/FAQ
@@ -140,7 +140,7 @@ The latest version of this FAQ is available here:
   In two thirds of the cases, yes[0], and it does not matter which layout you
   use. When you assemble 4 disks into a RAID10, you essentially stripe a RAID0
   across two RAID1, so the four disks A,B,C,D become two pairs: A,B and C,D.
-  If A fails, the RAID6 can only survive if the second failing disk is either
+  If A fails, the RAID10 can only survive if the second failing disk is either
   C or D; If B fails, your array is dead.
 
   Thus, if you see a disk failing, replace it as soon as possible!

Bug#300486: no easy way to wait until uim-xim is ready

2011-09-19 Thread d+deb

severity 300486 minor
thanks

sorry for my misspelling.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature

Bug#607375: Revised patch

Revised patch vs latest upstream git commit, and emailed direct to Neil 
Brown.


He has been 1-2 steps ahead of me on others, and yet no response from 
him on this one; I am assuming he just missed it.
Description: mdadm -e 1 incorrectly treated as 1.2 ("default")
Forwarded: 2011-09-19
Origin: vendor, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607375
Bug-Debian: http://bugs.debian.org/607375
Author: Scott Schaefer  
Last-Update: 2011-09-19

diff --git a/super1.c b/super1.c
index 0cd4124..f66e8e5 100644
--- a/super1.c
+++ b/super1.c
@@ -1398,7 +1398,8 @@ static struct supertype *match_metadata_desc1(char *arg)
 	/* leading zeros can be safely ignored.  --detail generates them. */
 	while (*arg == '0')
 		arg++;
-	if (strcmp(arg, "1.0") == 0 ||
+	if (strcmp(arg, "1") == 0 ||
+	strcmp(arg, "1.0") == 0 ||
 	strcmp(arg, "1.00") == 0) {
 		st->minor_version = 0;
 		return st;
@@ -1417,8 +1418,7 @@ static struct supertype *match_metadata_desc1(char *arg)
 		st->minor_version = 2;
 		return st;
 	}
-	if (strcmp(arg, "1") == 0 ||
-	strcmp(arg, "default") == 0) {
+	if (strcmp(arg, "default") == 0) {
 		st->minor_version = -1;
 		return st;
 	}

Bug#642182: libqwt6: zoomer widget returns to incorrect axis division upon reset

2011-09-19 Thread H. S.

Package: libqwt6
Version: 6.0.0-1
Severity: normal


Hello.

While using the QwtPlotZoomer widget to zoom into and then out of a plot,
 upon zoom reset the axis divisions are not the same as they were before
starting the zooming operations.

In effect, although the zoomer reset comes back to the original
axis ranges, but it forgets the major and minor divisions.

How to reproduce:
1. Use a qwt plot widget and customize its major and minor ticks
on its axis.
2. Apply a zoomer to that widget.
3. Do a few zoom operations and then reset the zoom. The axis
divisions are not the same as they were set in the beginning.

What should happen: when a zoomer is reset, the plot axis divisions
should be exactly the same as it was before the zooming operations.

If more information is needed, please let me know.

Thanks.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libqwt6 depends on:
ii  libc6 2.13-18Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.6.1-4  GCC support library
ii  libqt4-svg4:4.7.3-5  Qt 4 SVG module
ii  libqt4-xml4:4.7.3-5  Qt 4 XML module
ii  libqtcore44:4.7.3-5  Qt 4 core module
ii  libqtgui4 4:4.7.3-5  Qt 4 GUI module
ii  libstdc++64.6.1-4GNU Standard C++ Library v3

libqwt6 recommends no packages.

libqwt6 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#642039: Problem direction

I should also mention that the problem only seems to happen as I move 
from right (Linux server) to left (MacOS client).


--
Moshe Yudkowsky * mo...@pobox.com * www.pobox.com/~moshe
  signature v1.0



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#300486: no easy way to wait until uim-xim is ready

2011-09-19 Thread d+deb

severty 300486 minor
thanks
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature

Bug#642181: Bind9 fails to start when "-u bind" is present as an OPTION in /etc/default/bind9

2011-09-19 Thread Matt

Package: bind9
Version: 1:9.7.3.dfsg-1~squeeze3
Severity: important



-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bind9 depends on:
ii  adduser  3.112+nmu2  add and remove users and groups
ii  bind9utils   1:9.7.3.dfsg-1~squeeze3 Utilities for BIND
ii  debconf [debconf 1.5.36.1Debian configuration management sy
ii  libbind9-60  1:9.7.3.dfsg-1~squeeze3 BIND9 Shared Library used by BIND
ii  libc62.11.2-10   Embedded GNU C Library: Shared lib
ii  libcap2  1:2.19-3support for getting/setting POSIX.
ii  libdb4.8 4.8.30-2Berkeley v4.8 Database Libraries [
ii  libdns69 1:9.7.3.dfsg-1~squeeze3 DNS Shared Library used by BIND
ii  libgssapi-krb5-2 1.8.3+dfsg-4squeeze1MIT Kerberos runtime libraries - k
ii  libisc62 1:9.7.3.dfsg-1~squeeze3 ISC Shared Library used by BIND
ii  libisccc60   1:9.7.3.dfsg-1~squeeze3 Command Channel Library used by BI
ii  libisccfg62  1:9.7.3.dfsg-1~squeeze3 Config File Handling Library used 
ii  libldap-2.4-22.4.23-7.2  OpenLDAP libraries
ii  liblwres60   1:9.7.3.dfsg-1~squeeze3 Lightweight Resolver Library used 
ii  libssl0.9.8  0.9.8o-4squeeze1SSL shared libraries
ii  libxml2  2.7.8.dfsg-2+squeeze1   GNOME XML library
ii  lsb-base 3.2-23.2squeeze1Linux Standard Base 3.2 init scrip
ii  net-tools1.60-23 The NET-3 networking toolkit
ii  netbase  4.45Basic TCP/IP networking system

bind9 recommends no packages.

Versions of packages bind9 suggests:
ii  bind9-doc1:9.7.3.dfsg-1~squeeze3 Documentation for BIND
ii  dnsutils 1:9.7.3.dfsg-1~squeeze3 Clients provided with BIND
pn  resolvconf (no description available)
pn  ufw(no description available)

-- Configuration Files:
/etc/bind/named.conf.local changed:
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
include "/etc/bind/h2n.out/named.conf.matt";

/etc/bind/named.conf.options changed:
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk.  See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable 
// nameservers, you probably want to use them as forwarders.  
// Uncomment the following block, and insert the addresses replacing 
// the all-0's placeholder.
forwarders {
139.130.4.4;
};
// Set the forwarded query source port to 53 - rather than random
// query-source address * port 53;
auth-nxdomain no;# conform to RFC1035
listen-on-v6 { any; };
};

/etc/init.d/bind9 changed:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
RESOLVCONF=no
test -f /etc/default/bind9 && . /etc/default/bind9
test -x /usr/sbin/rndc || exit 0
. /lib/lsb/init-functions
PIDFILE=/var/run/named/named.pid
check_network() {
if [ -x /usr/bin/uname ] && [ "X$(/usr/bin/uname -o)" = XSolaris ]; then
IFCONFIG_OPTS="-au"
else
IFCONFIG_OPTS=""
fi
if [ -z "$(/sbin/ifconfig $IFCONFIG_OPTS)" ]; then
   #log_action_msg "No networks configured."
   return 1
fi
return 0
}
case "$1" in
start)
log_daemon_msg "Starting domain name service..." "bind9"
modprobe capability >/dev/null 2>&1 || true
# dirs under /var/run can go away on reboots.
mkdir -p /var/run/named
chmod 775 /var/run/named
chown root:bind /var/run/named >/dev/null 2>&1 || true
if [ ! -x /usr/sbin/named ]; then
log_action_msg "named binary missing - not starting"
log_end_msg 1
fi
if ! check_network; then
log_action_msg "no networks configured"
log_end_msg 1
fi
if start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/named \
--pidfile ${PIDFILE} -- $OPTIONS; then
if [ "X$RESOLVCONF" != "Xno" ] && [ -x /sbin/resolvconf ] ; then
echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.named
fi
log_end_msg 0
else
log_end_msg 1
fi
;;
stop)
log_daemon_msg "Stopping domain name service..." "bind9"
if ! check_network; then
log_action_msg "no networks configured"
log_end_msg 1

Bug#635504: ITP: flashcache -- write back block device cache for Linux

2011-09-19 Thread onlyjob

Hi Arno,

Thank you very much for your feedback.
Much appreciated.
I well relicense files in debian/* as GPLv2+

> * You provide no mechanism to setup a flashcache volume on boot.

Well, even if this functionality might be nice to have, it is not
required and it is not in upstream.
So it is not a flaw in my package. Providing extra functionality
should not be a blocker for package release.
For example cryptsetup package (which is also managing device mapper
pass-through devices) do not have this functionality.
This functionality arguably may be considered a separate job, which
might be packaged separately.
As Antoine de Saint-Exupéry once said: "A designer knows he has
achieved perfection not when there is nothing left to add, but when
there is nothing left to take away."

> * You close an ITP bug you don't own ... mine.

OK, I'd like to get the better understanding of what's the problem here.
Am I expected to file a duplicate ITP if I already have a solution?
Do we allow competition in Debian,
or does whoever filed ITP first, get a monopoly over packaging?
At least anyone is free to fix someone else's bugs even though someone
might be already working on it.

> Fair enough. Please note this is not how we work in Debian, though. I am
> the owner of the ITP bug and I made visible progress since I filed the
> ITP. You will very likely have a hard time in finding a sponsor while
> trying to hijack someone else's packages.
> This does not give you very much alternatives to my offer, besides of
> stepping down as maintainer (in Debian) completely. Your approach wasn't
> exactly polite and yet I offered you to form a team together with me.

I understand the importance and benefits of collaboration.
Visibility of your progress is questionable since in the ITP had no
information about location of your effort
or the progress you've made.
I was ready to file my own ITP but yours was already there, for over a
month without update.
I'm not sure if I should care about finding a sponsor - if you have
one, your work will get a better chance to be included when you
finish.
Meanwhile my package make sense.
I'm not sure what's the meaning of hijacking in this context.
I made all the work by my own independently.
To some extent there is a duplication of effort which we could avoid
if I were able to find your work.
Whatever I do you are in better position to have your work to be
accepted into Debian, so there is probably nothing for you to worry
about.

> This does not give you very much alternatives to my offer, besides of
> stepping down as maintainer (in Debian) completely. Your approach wasn't
> exactly polite and yet I offered you to form a team together with me.

I never meant to be impolite and I am sorry if I happen to do
something rude accidentally.
I see no drama if one of us will not be maintainer for flashcache
package  - there are plenty of other opportunities to contribute.
I'm OK to be a co-maintainer (two brains always better than one) and I
appreciate your offer.
What I don't understand is what exactly your offer is.
You're already free to take whatever you need for your package from
mine - my understanding is that you don't even need permission for it.
There are some minor concerns of mine like package version numbers:
for example my numbering may not be exactly orthodox, but it can be
translated directly into upstream checkout version.
But my biggest concern is package availability.
If my estimation is accurate, without usable outcome you spent about
4x times more time working on your package than I spent on mine.
This is probably because I desperately need working package.
Would teaming with you would require for me to work on both packages
until you will be ready to release yours?
Probably yes and I'm not sure if I want it or understand why it is
worth it. (Or should I do it merely for not hurting your feelings?)
I believe I did little wrong by doing work on the package and I refuse
to feel guilty about it.
Even though co-maintaining seems reasonable, you made it sound like a
favor to me, which is fine because I'm not proud.
But at this point I think someone else (a Debian Developer) should
tell us who should merge with who according to our work and not
according to who logged an ITP first.

I'm not in position to compare the quality of our packages.
Of course both of us eager to do the best work possible.
Having said this I understand that perfect work takes forever to finish.
We need to release something now, and I believe I'm a little bit ahead
of you in that regards (quite accidentally though).
In the end it doesn't matter who's package will remain the one as long
it will be available.

Please feel free to merge whatever you find useful.
I hope you'll excuse me for my lack of understanding (and experience)
of what it is to be a co-maintainer.
Please let me know of any procedures you believe we should agree on.

All the best,
Dmitry.

On 19 September 2011 20:45, Arno Töll  wrote:
> -BEGIN PGP SIGN

Bug#642039: speed is an issue


Jeff Licquia wrote, On 09/19/2011 08:35 PM:

I should have mentioned this before, too, but could you run synergys 
with "-d DEBUG1 -l " and send me the resulting log once it 
crashes again?


In progress.


I know it would be painful to your current mode of working, but it might also help if you 
could run a "standard" GNOME desktop, with the default workspace layout and no 
edge limits on synergy.  If you got through, say, a whole day without crashing, that 
might tell us something


I'm desperate enough to do that next.



--
Moshe Yudkowsky * mo...@pobox.com * www.pobox.com/~moshe
"So many of them, and so few of us, how are we ever going to bury them all?"
Robert Frezza, _Fire in a Faraway Place_



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642039: speed is an issue

2011-09-19 Thread Jeff Licquia


On 09/19/2011 06:51 PM, Moshe Yudkowsky wrote:

I'd switch to a different window manager if I could find one that
switches between virtual desktops when I hit the edge of the current
desktop. In fact no others seem to allow virtual desktops inside a
workspace, or perhaps I'm reading the documentation incorrectly.


I know it would be painful to your current mode of working, but it might 
also help if you could run a "standard" GNOME desktop, with the default 
workspace layout and no edge limits on synergy.  If you got through, 
say, a whole day without crashing, that might tell us something.


I should have mentioned this before, too, but could you run synergys 
with "-d DEBUG1 -l " and send me the resulting log once it 
crashes again?




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#581607: fdisk does not see the partitions of 2.0 tera

2011-09-19 Thread Karl Schmidt

I've also come across this problem. I'm not clear if it is a bug in fdisk/sfdisk or the result of an
older BIOS.

I was able to move an install to a larger disk - grow the partition, but on a kernel update it would
no longer boot.

This might have to do with the 2.19TB limitation of MBR - which means a move to GUID Partition Table
(GPT) and possibly the need for a BIOS's that supports GUID. (See:
http://en.wikipedia.org/wiki/GUID_Partition_Table )

In the mean time Debian installer fails to give any warning about larger drives and fdisk/sfdisk
also fail to warn.

The current kernels support GPT, but it is less than clear how older bios interact. It might be that
just the boot disk needs to be smaller than 2.19TB and that storage disks formatted with GPT will
work fine on machines with BIOS's that don't support GPT? It is also possible that
fdisk/cfdisk/sfdisk are failing without warning if one tries to use these large drives.

gparted supports EFI/GPT.

I have more questions than answers - in the mean time I am hoping that someone with a better
understanding of using large drives with Debian (with both new and older BIOS's) would write this up
as there are now 3TB drives on the market and installs and updates fail without clear indication as
of why.

Karl Schmidt EMail k...@xtronics.com
Transtronics, Inc. WEB http://xtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049 FAX (785) 841-0434

Happiness is a Swedish sunset; it is there for all,
but most of us look the other way and lose it.--Mark Twain

--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642180: debian-maintainers: Please add Paul Tagliamonte as a Debian Maintainer

2011-09-19 Thread Paul Tagliamonte

Howdy, folks,

Sorry, I messed up my headers in the last post (data was before advocation data)

Fixed and real change attached.

Cheers!
Paul

On Mon, Sep 19, 2011 at 9:23 PM, Paul Tagliamonte  wrote:
> Package: debian-maintainers
> Severity: normal
> kthxbye
>
> Please add Paul Tagliamonte to the Debian Maintainer keyring.
>
> Not sure if the third person is usually used or not. Figure I'll just
> go with convention.
>
> Thanks so much!
> Paul
>
> --
> All programmers are playwrights, and all computers are lousy actors.
>
> #define sizeof(x) rand()
> :wq
>



-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


add-7B585B30807C2A87
Description: Binary data

Bug#601198: Reclassifying ...


tag 601998 -wontfix
tag 601998 +fixed-upstream
thanks

Based on Neil's response, I am moving this from "Won't Fix" to "Fixed 
Upstream".





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642039: crash with 1.4.4


1.4.4 crashed after about 4 hours. I am now running Debian unstable, 1.3.6.

I'm trying switchDelay=500 to see if that helps slow things down. I 
don't see any visible effect from using the option when I test it -- 
that is, I don't see any delay in switching between screens.



--
Moshe Yudkowsky * mo...@pobox.com * www.pobox.com/~moshe




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589071: netatalk: Fails to serve root volume

2011-09-19 Thread Mason Mark

I have now had a chance to test this against netatalk 2.2.1, and it is still 
broken. (Fresh netatalk install in a fresh Ubuntu 11.4 VM.)

I would be interested to hear what exactly Alan's workaround (earlier in this 
bug's thread) breaks, because we'd like to try it.



On Aug 31, 2011, at 5:33 PM, Mason Mark wrote:

> This is still broken for me in 2.2.0. (Haven't had time to try with git HEAD 
> yet.
> 
> 
> On 2011/08/17, at 21:42, Frank Lahm wrote:
> 
>> 2011/7/5 Alan Snelgrove :
>>> I found a work around for this Bug, which works for me.
>>> in source package netatalk/etc/afpd/directory.c
>>> there are the lines
>>> 
>>>if ((ret = lchdir(cfrombstr(dir->d_fullpath))) != 0 ) {
>>>LOG(log_debug, logtype_afpd, "movecwd('%s'): ret: %u, %s",
>>>cfrombstr(dir->d_fullpath), ret, strerror(errno));
>>> The fix is to replace lchdir with chdir.
>>> There is only one occurrence of  lchdir  in the source file.
>> 
>> Bah! This breaks certain semantics.
>> Also can't reproduce with git master HEAD which means it should work
>> in 2.2.1, it's probably already working in 2.2.0.
>> 
>> -f
>> 
>> 
>> 
>> --
>> To unsubscribe, send mail to 589071-unsubscr...@bugs.debian.org.
> 
> 
> 
> 
> --
> To unsubscribe, send mail to 589071-unsubscr...@bugs.debian.org.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642180: debian-maintainers: Please add Paul Tagliamonte as a Debian Maintainer

2011-09-19 Thread Paul Tagliamonte

Package: debian-maintainers
Severity: normal
kthxbye

Please add Paul Tagliamonte to the Debian Maintainer keyring.

Not sure if the third person is usually used or not. Figure I'll just
go with convention.

Thanks so much!
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


add-7B585B30807C2A87
Description: Binary data

Bug#639521: swig: file conflict with swig2.0 (2.0.4-1.1)

2011-09-19 Thread Jonathan Nieder

Luca Falavigna wrote:

>  swig2.0 (2.0.4-3.1) unstable; urgency=low
>  .
>* Non-maintainer upload.
>  .
>[ Jonathan Nieder ]
>* Put swig2.0(1) manpage in the swig2.0 package, instead of whatever
>  architecture-dependent package happened to be processed first.
>* swig2.0 Breaks and Replaces swig (<< 2.0.4-3.1) (Closes: #639521).

Looks good to me.  Thanks, Luca!



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios

2011-09-19 Thread Karl Schmidt

Package: debian-installer
Version: 20110106+squeeze3
Severity: normal
Tags: d-i squeeze



-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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


Install attempts on a Tyan S7002 failed with a drive larger than 2.19TB (would 
fail at the grub installation)

I was able to move an install to a 1TB drive then move to a larger disk - grow 
the partition, but on a kernel update it would no longer boot.

This might have to do with the 2.19TB limitation of MBR - which means a move to 
GUID Partition Table (GPT) and possibly the need for 
a BIOS's that supports GUID. (See: 
http://en.wikipedia.org/wiki/GUID_Partition_Table )

In the mean time Debian installer fails to give any warning about larger drives 
and fdisk/sfdisk also fail to warn.


The current kernels support GPT, but it is less than clear how older bios 
interact. It might be that just the boot disk 
needs to be smaller than 2.19TB and that storage disks formatted with GPT will 
work fine on machines with BIOS's that don't support GPT? 
It is also possible that fdisk/cfdisk/sfdisk are failing without warning if one 
tries to use these large drives.

gparted supports EFI/GPT.

I'm thinking that D-i needs to detect the large drive size, possible the 
ability of the bios to work with this drive size and give a warning.

There might be problems supporting 2TB drives with the partioner in D-I that is 
independent to the BIOS. Sadly I have more questions than 
answers and hope someone with a better understanding of this issue writes it up.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642153: Confirmed: Qt-related (4.7.2) issue

2011-09-19 Thread Adam Majer

On Tue, Sep 20, 2011 at 12:17:00AM +0200, Émeric Maschino wrote:
> Thanks to snapshot.debian.org, I can confirm that qtcreator 1.3.1-3
> currently in Debian "Wheezy" Testing can be run successfully with Qt
> packages up to 4.7.1-2. Starting with Qt packages 4.7.2-1, Qt Creator
> crashes with a bus error.

Yes, it is in Qt. Applications don't touch internal Qt structures and
don't deal with direct rendering of fonts (area where backtrace is
pointing to)

- Adam

-- 
Adam Majer
ad...@zombino.com



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#594684: Package

2011-09-19 Thread Panayiotis Karabassis

Hi Julien,

On 09/20/2011 12:55 AM, Julien Cristau wrote:
> On Mon, Sep 19, 2011 at 16:35:37 +0300, Panayiotis Karabassis wrote:
> 
>> Is this dictated by Debian Policy? Just curious.
>>
> It's dictated by wanting to remain sane, as much as possible.  Which
> implies not forking X with random feature patches.
> 
> Cheers,
> Julien

It's not a random feature patch. X is unusable on Yeelong without this
patch.( So I am told, I have not tried ). Recompiling X takes about 3
hours on Yeelong. And nothing prevents you to drop the patch when it's
included upstream. Quilt will just tell about it.

What do others think?

-- 
Best regards,
Panayiotis Karabassis

-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#290937: hearse doesn't support 64-bit platforms

2011-09-19 Thread PJ Weisberg

I was certainly disappointed when Hearse failed to get retrieve bones
on my newly set-up 64-bit system.  This being 2011, I'll probably
never set up a new 32-bit system again.

I don't know how difficult it would be to add this ability to the
server.  I would take a crack at a patch myself, but there's no source
code on Hearse's website. :-(

>From a Debian perspective, is there any way to convince apt to install
a 32-bit Nethack on an otherwise 64-bit system?

-PJ



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#625756: electric-fence: FTBFS due to OOM with gcc-4.5

2011-09-19 Thread brian m. carlson

On Mon, Sep 19, 2011 at 03:55:57PM +0100, Colin Watson wrote:
> On Thu, Sep 08, 2011 at 06:14:49PM +0100, Colin Watson wrote:
> >   * Build with -fno-tree-dse, since otherwise GCC >= 4.5 misoptimises
> > allocateMoreSlots() (closes: #625756, LP: #749139).
> 
> In fact, as GCC upstream pointed out, a more targeted - and I think more
> correct - fix is -fno-builtin-malloc.  -fno-tree-dse won't really hurt
> much, but it will probably lose out on a bit of optimisation.

Honestly, I don't see why GCC treats malloc as a built-in.  Whatever
implementation of malloc is provided by the system is the one to use,
and I can't see why for the life of me GCC thinks it can do anything
better with a built-in function than the system one does.

Therefore, unless there's a very compelling reason I haven't thought of,
this is a GCC bug; GCC shouldn't treat malloc specially at all.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

signature.asc
Description: Digital signature

Bug#642178: package ftbfs with ld --as-needed

Package: seqan
Version: 1.2-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
User: debian-...@lists.debian.org
Usertags: ld-as-needed

see http://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries

patch at
http://launchpadlibrarian.net/80377414/seqan_1.2-1_1.2-1ubuntu1.diff.gz

failed build
https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2711287




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642177: package always builds with -O0

Package: seed
Version: 3.0.0-2

CFLAGS is always overwritten in configure.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#504489: xpdf: "Bogus memory allocation size"

retitle 504489 user-specific crash with fullcircle pdf file
severity 504489 minor
tag 504489 moreinfo, unreproducible
thanks

Timo Juhani Lindfors wrote:
> I still see the error message in 3.03-4
> 
> $ xpdf fullcircle-issue18eng.pdf 19
> Bogus memory allocation size

I do get the "Bogus memory allocation size" message, but I just don't
get a crash afterward (tested on amd64 and i386).  Can you capture a
backtrace?  Also, can you send updated system information for your
machine (easiest to generate with reportbug)?

Best wishes,
Mike

-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#470496: Graphs not available anymore after upgrade

2011-09-19 Thread Bernhard Schmidt


tags #470496 wontfix
thanks


after the update to version 1.0.6 I do not see certain grahps anymore.
E.g. the Interface statistics for hosts are not shown anymore.
Instead, I see line like the following in the log:
[11-Mar-2008 16:40:11*] Datasource exists in RRD file, but it is not
updated: ifInOctets in
/var/lib/torrus/collector_rrd/calimero_eth0_if-mib.rrd

and

[11-Mar-2008 16:40:11*] Datasource being updated does not exist:
ifHCOutUcastPkts in
/var/lib/torrus/collector_rrd/calimero_eth0_if-mib.rrd

Is there a way to convert the rrd files? Or any other procedure to make
the graphs work again (preferable without data loss)?


This is unfortunately a design issue in Torrus. Datasources are 
referenced by name (usually the name in the SNMP MIB) in the RRD file. 
With new versions of Torrus, some names might change (i.e. in your case 
ifInOctets -> ifHCOutUcastPkts indicating the move from 32bit to 64bit 
SNMP counters), some might be removed or added, but the datasources 
present in the RRD are not changed.


If you value your data you can try to export it using rrdtool dump, 
change the DS names and reimport it using rrdtool import, but that is 
quite cumbersome. If you don't, just delete the corresponding .rrd-File.


Best Regards,
Bernhard



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642176: g++-4.6: libreoffice/mozilla build fails with gcc >= 4.6.1-10 due to gcc PR 50442

2011-09-19 Thread Rene Engelhard

Package: g++-4.6
Version: 4.6.1-10
Severity: important
Tags: patch
Forwarded: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50442 

Hi,

libreoffices (and apparently also mozilla, see below) build fails since
4.6.1-10.

Build log details in 
http://lists.freedesktop.org/archives/libreoffice/2011-September/018386.html:

[ build CXX ] vcl/unx/gtk/a11y/atkutil
R=/home/luc/git && S=$R/core && O=$S/solver/unxlngx6.pro &&
W=$S/workdir/unxlngx6.pro &&  mkdir -p $W/CxxObject/vcl/unx/gtk/a11y/
$W/Dep/CxxObject/vcl/unx/gtk/a11y/ && ccache g++ -DCPPU_ENV=gcc3 -DCUI
-DENABLE_GRAPHITE -DENABLE_GTK -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -DGCC -DGXX_INCLUDE_PATH=/usr/include/c++/4.6
-DHAVE_GCC_VISIBILITY_FEATURE -DLINUX -DNDEBUG -DOPTIMIZE
-DOSL_DEBUG_LEVEL=0 -DPRODUCT -DPRODUCT_FULL -DSOLAR_JAVA -DSUPD=350 -DUNIX
-
DUNX -DVCL -DX86_64 -D_PTHREADS -D_REENTRANT   -DVCLPLUG_GTK_IMPLEMENTATION
-DVERSION=\"350m1\"   -Wall -Wendif-labels -Wextra -Wshadow
-Woverloaded-virtual -Wno-non-virtual-dtor -fPIC -fmessage-length=0
-fno-common -pipe  -fvisibility=hidden  -fvisibility-inlines-hidden 
-std=c++0x -Wno-deprecated-declarations   -DEXCEPTIONS_ON -fexceptions
-fno-enforce-eh-specs  -O2 -c $S/vcl/unx/gtk/a11y/atkutil.cxx -o
$W/CxxObject/vcl/unx/gtk/a11y/atkutil.o -MMD -MT $W/
CxxObject/vcl/unx/gtk/a11y/atkutil.o -MP -MF
$W/Dep/CxxObject/vcl/unx/gtk/a11y/atkutil.d -I$S/vcl/unx/gtk/a11y/
-I$O/inc/stl -I$O/inc/external -I$O/inc -I$S/solenv/unxlngx6/inc
-I$S/solenv/inc -I$S/res -I$S/solenv/inc/Xp31
-I/usr/lib/jvm/java-6-openjdk-amd64/include
-I/usr/lib/jvm/java-6-openjdk-amd64/include/linux
-I/usr/lib/jvm/java-6-openjdk-amd64/include/native_threads/include
-I$S/vcl/inc -I$S/vcl/inc/pch -I$S/solenv/inc -I$O/inc  -I$O/inc/offapi
-I$O/
inc/udkapi -pthread -I/usr/include/gtk-2.0
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12
-I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include  
/home/luc/git/core/vcl/unx/gtk/a11y/atkutil.cxx: In member function ‘void
DocumentFocusListener::attachRecursive(const
com::sun::star::uno::Reference&,
const
com::sun::star::uno::Reference&,
const
com::sun::star::uno::Reference&)’:
/home/luc/git/core/vcl/unx/gtk/a11y/atkutil.cxx:322:60: error: call of
overloaded
‘insert(com::sun::star::uno::Reference&)’
is ambiguous
/home/luc/git/core/vcl/unx/gtk/a11y/atkutil.cxx:322:60: note: candidates
are:
/usr/include/c++/4.6/bits/stl_set.h:407:7: note: std::pair, _Compare, typename
_Alloc::rebind<_Key>::other>::const_iterator, bool> std::set<_Key, _Compare,
_Alloc>::insert(const value_type&) [with _Key =
com::sun::star::uno::Reference, _Compare =
std::less
>, _Alloc = std::allocator >, typename std::_Rb_tree<_Key,
_Key, std::_Identity<_Key>, _Compare, typename
_Alloc::rebind<_Key>::other>::const_iterator =
std::_Rb_tree_const_iterator
>, std::set<_Key, _Compare, _Alloc>::value_type =
com::sun::star::uno::Reference]
/usr/include/c++/4.6/bits/stl_set.h:416:7: note: std::pair, _Compare, typename
_Alloc::rebind<_Key>::other>::const_iterator, bool> std::set<_Key, _Compare,
_Alloc>::insert(std::set<_Key, _Compare, _Alloc>::value_type&&) [with _Key =
com::sun::star::uno::Reference, _Compare =
std::less
>, _Alloc = std::
allocator
>, typename std::_Rb_tree<_Key, _Key, std::_Identity<_Key>, _Compare,
typename _Alloc::rebind<_Key>::other>::const_iterator =
std::_Rb_tree_const_iterator
>, std::set<_Key, _Compare, _Alloc>::value_type =
com::sun::star::uno::Reference]

I reverted to gcc-4.5 for now but that of course fails with gcj-using
archs..

see 
http://lists.freedesktop.org/archives/libreoffice/2011-September/018423.html 
and the attached
complete interdiff for the fix.

Grüße/Regards,

René
diff -u gcc-4.6-4.6.1/debian/rules.patch gcc-4.6-4.6.1/debian/rules.patch
--- gcc-4.6-4.6.1/debian/rules.patch
+++ gcc-4.6-4.6.1/debian/rules.patch
@@ -81,6 +81,7 @@
 	pr49944 \
 	libjava-r176199 \
 	gcc-cloog-dl \
+	pr50442 \
 	$(if $(filter yes, $(DEB_CROSS)),,gcc-print-file-name) \
 
 #	libstdc++-nothumb-check \
diff -u gcc-4.6-4.6.1/debian/changelog gcc-4.6-4.6.1/debian/changelog
--- gcc-4.6-4.6.1/debian/changelog
+++ gcc-4.6-4.6.1/debian/changelog
@@ -1,3 +1,11 @@
+gcc-4.6 (4.6.1-11.1) unstable; urgency=low
+
+  [ Rene Engelhard ]
+  * Non-maintainer upload.
+  * Add patch for PR c++/50442, reverting fix for PR c++/49267
+
+ -- Rene Engelhard   Mon, 19 Sep 2011 17:57:52 +0200
+
 gcc-4.6 (4.6.1-11) unstable; urgency=low
 
   * Update to SVN 20110917 (r178926) from the gcc-4_6-branch.
diff -u gcc-4.6-4.6.1/debian/patches/svn

Bug#553884: xtrs: diff for NMU version 4.9c-3.3

2011-09-19 Thread Hector Oron



Dear maintainer,

Resending with proper NMU diff. Apologies for inconveniences.

I've prepared an NMU for xtrs (versioned as 4.9c-3.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar System, 
which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html
diff -u xtrs-4.9c/debian/changelog xtrs-4.9c/debian/changelog
--- xtrs-4.9c/debian/changelog
+++ xtrs-4.9c/debian/changelog
@@ -1,3 +1,13 @@
+xtrs (4.9c-3.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix "replacing libreadline5-dev build dependency with libreadline-
+dev" (Closes: #553884)
+  * Build using -Wno-error=unused-but-set-variable.
+  * debian/rules: use DEB_HOST_ARCH_ENDIAN to guess host endianness.
+
+ -- Hector Oron   Sun, 18 Sep 2011 22:31:19 +
+
 xtrs (4.9c-3.2) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u xtrs-4.9c/debian/control xtrs-4.9c/debian/control
--- xtrs-4.9c/debian/control
+++ xtrs-4.9c/debian/control
@@ -2,7 +2,7 @@
 Section: contrib/otherosfs
 Priority: extra
 Maintainer: Branden Robinson 
-Build-Depends: libncurses5-dev, libreadline5-dev, libx11-dev, groff, debhelper (>= 5), po-debconf, html2text
+Build-Depends: libncurses5-dev, libreadline-dev, libx11-dev, groff, debhelper (>= 5), po-debconf, html2text
 Standards-Version: 3.7.3
 
 Package: xtrs
diff -u xtrs-4.9c/debian/rules xtrs-4.9c/debian/rules
--- xtrs-4.9c/debian/rules
+++ xtrs-4.9c/debian/rules
@@ -13,14 +13,7 @@
 HTML2TEXT=html2text -nobs -style pretty
 
 ARCH=$(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
-
-ifneq (,$(findstring $(ARCH),alpha amd64 arm i386 ia64 mipsel sh3 sh4))
-ENDIANNESS=little
-endif
-
-ifneq (,$(findstring $(ARCH),armeb hppa m68k mips powerpc ppc64 sparc s390))
-ENDIANNESS=big
-endif
+ENDIANNESS=$(shell dpkg-architecture -qDEB_HOST_ARCH_ENDIAN)
 
 ifeq ($(ENDIANNESS),)
 $(error endianness of $(ARCH) architecture is unknown\; cannot continue)
@@ -54,10 +47,10 @@
 	touch "$$F"; \
 	done
 ifeq ($(ENDIANNESS),big)
-	$(MAKE) DEBUG="-Wall -Werror $(OPTIMIZE) -g -D_REENTRANT" PREFIX=/usr \
+	$(MAKE) DEBUG="-Wall -Werror -Wno-error=unused-but-set-variable $(OPTIMIZE) -g -D_REENTRANT" PREFIX=/usr \
 	  ENDIAN=-Dbig_endian
 else
-	$(MAKE) DEBUG="-Wall -Werror $(OPTIMIZE) -g -D_REENTRANT" PREFIX=/usr
+	$(MAKE) DEBUG="-Wall -Werror -Wno-error=unused-but-set-variable $(OPTIMIZE) -g -D_REENTRANT" PREFIX=/usr
 endif
 
 	: >$@


signature.asc
Description: Digital signature

Bug#642175: remove RPM spec file generator, 02_spec.dpatch

2011-09-19 Thread Allison Randal

Package: libnet-server-perl
Version: 0.99-2
Severity: normal

Downstream in Ubuntu, we've had an FTBFS in libnet-server-perl (version
0.99-2ubuntu1) in Oneiric, caused by a missing value for $version in the
file Net-Server.spec.PL. This appears to be related to changes in the
behavior of MakeMaker.

https://launchpadlibrarian.net/79887943/buildlog_ubuntu-oneiric-i386.libnet-server-perl_0.99-2ubuntu1_FAILEDTOBUILD.txt.gz

The weird thing about the file Net-Server.spec.PL, is that it's a script
to automatically generate an RPM spec file. This file is not in the
upstream Perl module, it is added by the patch 02_spec.dpatch, which
first appeared in the Debian packages in version 0.87-1 in 2004. In this
same release 0.87, the same file was removed from the upstream Perl
module (it was in the Perl module tarball in version 0.86
http://cpansearch.perl.org/src/BBB/Net-Server-0.86/, and removed in
version 0.87 http://cpansearch.perl.org/src/BBB/Net-Server-0.87/).

It looks suspiciously like the patch 02_spec.dpatch may be unnecessary.
I rebuilt the packages without the patch, and have encountered no
problems. The only output from the spec file generator is the RPM spec
file, so it's not affecting other parts of build process. The patch was
added during a fairly chaotic period for libnet-server-perl, involving a
changeover in upstream maintainers for the module in CPAN, and a
changeover in Debian maintainers.

I reviewed the FTBFS in Ubuntu at Scott Kitterman's request, and am
recommending the solution of removing the patch 02_spec.dpatch, rather
than continuing to maintain an RPM spec file generator that the upstream
developers abandoned 6 years ago. Debian may want to consider the same fix.

HTH,
Allison

--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#553853: Upload

2011-09-19 Thread Hector Oron

Hello,

On Mon, Sep 19, 2011 at 03:30:07PM -0700, Chris Taylor wrote:
 
> I have this queued for upload on my end, however my key expired and I
> am awaiting the new keyring push for my updated key.

Thanks! Just let me know if you want me to cancel the NMU, otherwise I'll
let it proceed normally.

Best regards,
-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar System, 
which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html


signature.asc
Description: Digital signature

Bug#553853: socat: diff for NMU version 1.7.1.3-1.2

2011-09-19 Thread Hector Oron



Dear maintainer,

Following Julien's comments I've prepared an NMU for socat
(versioned as 1.7.1.3-1.2) and uploaded it to DELAYED/5.
Please feel free to tell me if I should delay it longer.

Regards.

-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar System, 
which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html
diff -Nru socat-1.7.1.3/debian/changelog socat-1.7.1.3/debian/changelog
--- socat-1.7.1.3/debian/changelog	2011-07-02 19:03:48.0 +0100
+++ socat-1.7.1.3/debian/changelog	2011-09-20 00:23:50.0 +0100
@@ -1,3 +1,11 @@
+socat (1.7.1.3-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Replace libreadline5-dev build dependency with libreadline-
+gplv2-dev" (Closes: #553853)
+
+ -- Hector Oron   Tue, 20 Sep 2011 00:22:41 +0100
+
 socat (1.7.1.3-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru socat-1.7.1.3/debian/control socat-1.7.1.3/debian/control
--- socat-1.7.1.3/debian/control	2010-08-03 07:08:31.0 +0100
+++ socat-1.7.1.3/debian/control	2011-09-18 23:15:18.0 +0100
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Chris Taylor 
 Homepage: http://www.dest-unreach.org/socat/
-Build-Depends: debhelper (>= 7.0.50~), libreadline5-dev, libssl-dev,
+Build-Depends: debhelper (>= 7.0.50~), libreadline-gplv2-dev, libssl-dev,
libwrap0-dev, quilt
 Standards-Version: 3.9.1
 


signature.asc
Description: Digital signature

Bug#642174: dkms: please provide templates for dh_make

2011-09-19 Thread Andreas Beckmann

Package: dkms
Severity: wishlist

Hi,

it would be nice if dh_make would provide templates for a "dkms kernel
module" package class with example dkms.conf, control, rules, maintainer
scripts, ... which represents the recommended practice of creating a
dkms module package.

This wishlist report actually targets the dh-make package, but since the
dkms maintainers are the most suitable to create a patch for dh-make I'm
first assigning the bug to dkms. Please attach a patch for dh-make and
reassign there.

Thanks

Andreas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642108: dialog: Tab does not visit inputs

2011-09-19 Thread Thomas Dickey


On Mon, 19 Sep 2011, Michal Suchanek wrote:


Package: dialog
Version: 1.1-20110707-1
Severity: wishlist

The behaviour of dialog forms is inconsistent with most other forms
available today. You need to use arrows to move between form inputs
while normally tab would move to next input.


again, it is configurable.  The KEY BINDINGS section of the manpage
could for instance provide an example illustrating this case.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642105: dialog: return value diagnostics suck

2011-09-19 Thread Thomas Dickey


On Mon, 19 Sep 2011, Michal Suchanek wrote:


Package: dialog
Version: 1.1-20110707-1
Severity: normal


From the man page:


read further, it is configurable (look for DIALOG_ESC).

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)

2011-09-19 Thread Miguel Martínez

I'm quite sure  I loaded the module with debug information. It is not in the 
beginning of the debug log, since it connected to Eduroam before I rmmod'ed 
and modprobed iwlagn with the debug symbols enabled. 

Anyway, I'll try again tomorrow.


-- 

Dr. Miguel Martinez Canales
   Department of Physics & Astronomy
   University College London
   Gower Street, London, WC1E 6BT (UK)
Fax:  +44 207 679 0595
Tlf:  +44 207 678 3476


 "If you have an apple and I have an apple and
 we exchange these apples then you and I will
 still each have one apple. But if you have an
 idea and I have an idea and we exchange these
 ideas, then each of us will have two ideas."

 George Bernard Shaw 




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642042: cron: Maintainer's name typo

2011-09-19 Thread Vincent Blut

Le 19/09/2011 22:51, Javier Fernandez-Sanguino a écrit :
> On 19 September 2011 23:07, Vincent Blut  wrote:
>   
>> Ok I see, sorry for the noise Javier!
>> 
> It's quite alright. It's actually a good reminder, as I should move
> debian/control over to UTF-8 to keep things clean anyway :)
>
> Regards
>
> Javier
>   

Sure. By the way I closed the bug, do you want me to reopen it in case
you'd be affected by a memory leak? ;-}

Cheers,
Vincent
 



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538694: screensaver it's not reliable - sometimes it doesn't lock my session after 1 minute idle as expected

2011-09-19 Thread Giulio Turetta

Package: gnome-screensaver
Version: 2.30.0-2squeeze1
Severity: normal

The screensaver does not always start.
It's a security problem because screen is not locked as expected (and so user
data/session isn't protected as should be).



-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-screensaver depends on:
ii  dbus-x11   1.2.24-4+squeeze1 simple interprocess messaging syst
ii  gconf2 2.28.1-6  GNOME configuration database syste
ii  gnome-icon-theme   2.30.3-2  GNOME Desktop icon theme
ii  gnome-session-bin  2.30.2-3  The GNOME Session Manager - Minima
ii  libc6  2.11.2-10 Embedded GNU C Library: Shared lib
ii  libcairo2  1.8.10-6  The Cairo 2D vector graphics libra
ii  libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst
ii  libdbus-glib-1-2   0.88-2.1  simple interprocess messaging syst
ii  libgconf2-42.28.1-6  GNOME configuration database syste
ii  libgl1-mesa-glx [libgl 7.7.1-4   A free implementation of the OpenG
ii  libglib2.0-0   2.24.2-1  The GLib library of C routines
ii  libgnome-desktop-2-17  2.30.2-2  Utility library for loading .deskt
ii  libgnome-menu2 2.30.3-1  an implementation of the freedeskt
ii  libgnomekbd4   2.30.2-2  GNOME library to manage keyboard c
ii  libgtk2.0-02.20.1-2  The GTK+ graphical user interface 
ii  libpam0g   1.1.1-6.1 Pluggable Authentication Modules l
ii  libpango1.0-0  1.28.3-1+squeeze2 Layout and rendering of internatio
ii  libx11-6   2:1.3.3-4 X11 client-side library
ii  libxext6   2:1.1.2-1 X11 miscellaneous extension librar
ii  libxklavier16  5.0-2 X Keyboard Extension high-level AP
ii  libxxf86vm11:1.1.0-2 X11 XFree86 video mode extension l

Versions of packages gnome-screensaver recommends:
ii  gnome-power-manager   2.32.0-2   power management tool for the GNOM
ii  libpam-gnome-keyring  2.30.3-5   PAM module to unlock the GNOME key

Versions of packages gnome-screensaver suggests:
pn  rss-glx(no description available)
pn  xscreensaver-data  (no description available)

-- 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#642173: iptables -S --line-numbers does not work

2011-09-19 Thread Regid Ichira

Package: iptables
Version: 1.4.12
Severity: normal

# iptables -S --line-numbers
iptables v1.4.12: Illegal option `-0' with this command

Try `iptables -h' or 'iptables --help' for more information.
#

iptables -L --line-numbers does work.  Is:

$ zgrep -B4 line-numbers /usr/share/doc/iptables/changelog.gz
iptables v1.4.1.1 Changelog
=

Henrik Nordstrom (1):
iptables: fix printing of line numbers with --line-numbers arg

related?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642172: ITP: likewise-open -- Authentication services for Active Directory Domains

2011-09-19 Thread lenios

Package: wnpp
Severity: wishlist
Owner: Richard Sellam 


* Package name: likewise-open
  Version : 6.1.0.406
* URL : http://www.likewiseopen.org/
* License : GPL version 3
  Description : Authentication services for Active Directory Domains
 Likewise Open 6.1 provides a means of integrating Unix desktops and servers
 into an Active Directory (AD) environment by providing a means for hosts
 to join the domain as member servers and make the Windows users and groups
 available to other Unix applications and services via the PAM and Name
 Service Switch libraries.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642039: speed is an issue


Jeff Licquia wrote, On 09/19/2011 05:05 PM:

On 09/19/2011 04:01 PM, Moshe Yudkowsky wrote:

I should mention that in each case when there was a crash, I moved the
mouse very rapidly from one screen to the other.


Thanks for all the testing; it's very helpful.

When you move the mouse rapidly between screens, does it crash every 
time?  If not, does it seem to make crashes happen more quickly?


Rapid movement does _not_ cause a problem each time, but it seems that 
each time there is a problem, it was during rapid movement.


Right now I'm testing the Synergy 1.4.x deb - I'm trying hard to avoid 
removing the limits because of my setup here.


It suddenly occurs to me that my setup here may be an additional issue 
-- conflict over what the edge hit means. I have GNOME on top of 
elightenment window manager, with multiple workspaces/desktops (3 
workspaces in a 3x1 array, each workspace contains a 2x2 array of 
virtual desktops). When inside a workspace I like to mouse between each 
set of 2x2 desktops and I'd wouldn't have access to my left windows if I 
were to remove the limits - any movement to the left would push me onto 
the other screen.


So the issue might be contention between enlightenment and synergy over 
the meaning of the mouse hit at the left edge...?


I'd switch to a different window manager if I could find one that 
switches between virtual desktops when I hit the edge of the current 
desktop. In fact no others seem to allow virtual desktops inside a 
workspace, or perhaps I'm reading the documentation incorrectly.


Thanks for your patience. I'll report back when I have further details.




--
Moshe Yudkowsky * mo...@pobox.com * www.pobox.com/~moshe
 "Don't blame the rainbows for the rain."
-- The Moody Blues



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642042: cron: Maintainer's name typo

2011-09-19 Thread Javier Fernandez-Sanguino

On 19 September 2011 23:07, Vincent Blut  wrote:
> Ok I see, sorry for the noise Javier!

It's quite alright. It's actually a good reminder, as I should move
debian/control over to UTF-8 to keep things clean anyway :)

Regards

Javier



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)

2011-09-19 Thread Venkataraman, Meenakshi

Hi Miguel,

>I have already built kernel 3.0.0-1-amd64 with the required debugging
>symbols.
>I've rebooted into the debug kernel, and loaded the iwlagn module with
>debugging symbols enabled. Or so I think.

[MV] I don't see much iwlagn debugging information in the log you sent me. Can 
you please load the iwlagn module with the following parameters:

modprobe iwlagn debug=0x43FFF

Thanks,
Meenakshi



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641919: linux-image-3.0.0-1-amd64: VIA-Rhine II resetting: network connectivity lost

2011-09-19 Thread Antonio Marcos López Alonso

El Lunes, 19 de Septiembre de 2011, Ben Hutchings escribió:
> On Sat, 2011-09-17 at 15:59 +0100, Antonio Marcos López Alonso wrote:
> > Package: linux-2.6
> > Version: 3.0.0-3
> > Severity: normal
> > Tags: upstream
> > 
> > This is the same behavior as bug #549606. Network connection is lost
> > somehow and dmesg outputs lots of:
> > 
> > via-rhine :00:12.0: eth0: Transmit timed out, status 0003, PHY status
> > 786d, resetting...
> > via-rhine :00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
> > 
> > Resetting the machine fixes the issue.
> > 
> > This behavior has been happening now and then since the previous bug was
> > closed.
> 
> [...]
> 
> I think bug #549606 was closed in error, as the supposed fix is related
> to behaviour after a transmit timeout and not the cause of timeouts.
> Before it was closed, you found that the kernel parameter 'noapic' was a
> workaround for the problem on your system, which means it probably isn't
> a bug in the driver).  I notice that you are currently *not* using that
> parameter.

Hi Ben:

I effectively used noapic to apparently workaround the problem but in the long 
run I found it just minimized the problem somehow (occurrences were less). 

> 
> I asked you to report this bug at ,
> including the fact that 'noapic' works around it.  The product should be
> 'Platform Specific/Hardware' and the component 'i386'.
> 
> You won't be able to do that at the moment because that server is done,
> but please try to do that in a week or so.  Then let us know the
> bug number so we can keep track of it.

OK, I'll do it so and let you know.
Antonio



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#415397: speedometer: Linear scale (Debian Bug#415397)

2011-09-19 Thread jari

On 2011-09-19 17:19, Ian Ward wrote:
| Jari Aalto wrote on 2011-09-19 16:56:
| > 
| > Hi Ian,
| > 
| > Could you revit this bug in Debiam:
| > 
| > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415397
| 
| Not sure why you mention the urwid version, but yes I am aware of this
| feature request.

I probably mistook that it was related to speedometer.

| I note that speedometer 2.7 released 10 months ago isn't packaged yet.

It is, see:

   http://packages.debian.org/speedometer

| It doesn't have the feature you mention, but it does fix some other issues.

Ok. If you find the time to work on it, let me know[*]

Jari

[*] would you consider a http://freshmeat.net/ account
too. Benefits:

   -  It's a low maintenence for developer: after initial setup
  only release announcements need to be posted.
- It does not move. One yellow pages to rule them all.
- Presents project information in a standard and uniform manner (at a
  glance).
- Users can subscribe to the project announcements (real helpful for 
packagers)
- Users can find other related software.
- Provides statistics and popularity.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#553853: Upload

2011-09-19 Thread Chris Taylor


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I have this queued for upload on my end, however my key expired and I
am awaiting the new keyring push for my updated key.


- -Chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk53wmoACgkQLpNUoan9SCGDJQCdGjVMlj62GoE9FODi7Zl/0DXK
l2MAn0DLEeinlhiAjsCVvs472NT3C86B
=jgHO
-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#642171: liblockfile1: Unnessesary macro "ppsh" in the manual of "dotlockfile"

2011-09-19 Thread Bjarni Ingi Gislason

Package: liblockfile1
Version: 1.08-4
Severity: minor

  Warning from "mandb": 

/usr/bin/mandb: warning: /usr/share/man/man1/dotlockfile.1.gz: whatis parse for 
dotlockfile(1) failed

  The "PP" macro in the "ppsh" macro is not neccessary
for manuals displayed by "groff".  "SH" provides the space
between sections.

  Start of manual page:

.TH DOTLOCKFILE 1 "September 8, 2009" "" "Cistron Utilities"
.\"
.\" Macro for adjustment of spaces between sections at a single location:
.de ppsh
.  PP
.  SH \\$*
..
.\" hyphenation language, soft hyphen character, hyphenation space
.hla us
.shc \(hy
.hys 1
.\"
.ppsh NAME
dotlockfile \- Utility to manage lockfiles
.ppsh SYNOPSIS

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 2.6.32-35squeeze2
Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages liblockfile1 depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib

liblockfile1 recommends no packages.

liblockfile1 suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#561389: bug#561389 forwarded upstream

2011-09-19 Thread Jari Aalto


Date: Mon, 19 Sep 2011 23:11:51 +0300
From: Jari Aalto 
To: Felipe Augusto van de Wiel , Miguel Anxotero
, f...@users.sf.net
Subject: desproxy: [PATCH] Debian and source is still not in the sources

Hi,

Could you take a look at this patchs at sourceforge and Debian:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561389

http://sourceforge.net/tracker/?func=detail&aid=2915806&group_id=30464&atid=399232

It would be nice if this were integrated to sources and made a new release.

Thanks,
Jari



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642154: BUG: unable to handle kernel paging request at ffff8803bb6ad000

2011-09-19 Thread Jonathan Nieder

Hi,

rush wrote:

>  I have some suspicious activities on my server: i've continiously repeated
>  messages in dmesg about "BUG: unable to handle kernel paging request"

Yes, if this server is open to the public (especially if it has
untrusted local users), you should probably take it down.  A kernel
BUG means that something happened the kernel did not expect, and after
that point, all bets (including security bets) are off.

Of course we would be happiest if you can make it happen again, in
order to track it down and fix it, though. :)

[...]
> I've checked memory: they are fine

Thanks!

[...]
>  * Kernel has oopsed before.
[...]
> [430009.960980] RIP  [] __sanitize_i387_state+0x23/0xe1

Can you recover a trace of the first oops (for example from
/var/log/message*)?  Instead of a "Tainted" line containing a "D" (has
oopsed before), it should have a "Not tainted" line.

Thanks for writing,
Jonathan

-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642153: Confirmed: Qt-related (4.7.2) issue

2011-09-19 Thread Émeric Maschino

Thanks to snapshot.debian.org, I can confirm that qtcreator 1.3.1-3
currently in Debian "Wheezy" Testing can be run successfully with Qt
packages up to 4.7.1-2. Starting with Qt packages 4.7.2-1, Qt Creator
crashes with a bus error.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642039: speed is an issue

2011-09-19 Thread Jeff Licquia


On 09/19/2011 04:01 PM, Moshe Yudkowsky wrote:

I should mention that in each case when there was a crash, I moved the
mouse very rapidly from one screen to the other.


Thanks for all the testing; it's very helpful.

When you move the mouse rapidly between screens, does it crash every 
time?  If not, does it seem to make crashes happen more quickly?




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#642039: Crash with 1.3.7

Deb from the Synergy web site, 1.3.7, crashed after about 7 hours, a new 
record. synergy.conf as above (no switchCorners, yes limits).


--
Moshe Yudkowsky * mo...@pobox.com * www.pobox.com/~moshe



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641759: gimp: Gimp 2.6.11 crashes X session when opening a image

2011-09-19 Thread Noel David Torres Taño

So, your closing means that GIMP is not culprit at all of the failure? Is it 
completely a responsability of the nvidia driver?


signature.asc
Description: This is a digitally signed message part.

Bug#641836: Fails to hide internal symbols

2011-09-19 Thread Daniel Kobras

Hi!

Am 16.09.2011 um 18:45 schrieb Reinhard Tartler:

> Von: Yuriy Kaminskiy 
> Betreff: Re: [MPlayer-cvslog] r34099 - in trunk/libass: ass.c ass.h 
> ass_bitmap.c ass_bitmap.h ass_cache.c ass_cache.h ass_drawing.c ass_font.c 
> ass_font.h ass_fontconfig.c ass_fontconfig.h ass_library.c ass_library.h 
> ass_parse.c...
> Datum: 16. September 2011 07:20:20 MESZ
> An: mplayer-dev-...@mplayerhq.hu
> Antwort an: mplayer-dev-...@mplayerhq.hu
(...)
> libmpg123 package 1.12.1-3.2 on debian/sid is broken (it fails to hide 
> internal
> symbols, they overridden by symbols from MPlayer/mp3lib [with different ABI],
> resulting in crash).
> As package from squeeze (same upstream version) is *not* broken in same way, 
> and
> changes in packaging looks minor and unrelated, have no idea why it is broken.
> Likely ./configure --disable-mp3lib also will fix this crash :-)

Which architecture have you been looking at? On amd64 in sid, libmpg123 only 
exports the 84 symbols that are meant to be visible.

Regards,

Daniel.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#632225: Cod review

2011-09-19 Thread Jelmer Vernooij


Hi Barry,

Thanks again for having a look at these. I don't think any of these are 
likely to cause issues in practice, but they're still good to fix.


On Mon 19 Sep 2011 10:16:33 PM CEST, Barry Warsaw wrote:


I did a very quick review of the C code here (branched from
debianlp:subvertpy
on Launchpad, so should be the sid package), and found a number of
questionable things. I don't know the library code or the svn API very
well,
so it's entirely possible that some or all of these are false alarms. It's
also possible I missed some things. I list them here because they made
me go
"hmm" and I think they're worth a second look.

Most issues I think are not that serious, e.g. leaking a refcount in a
rare
error condition, either by not decref'ing an object in a short-circuit
exit,
or not checking return values for Python API calls. I'll list these
farther
down. The most serious issue appears to be in util.c in
config_hash_from_object().

Potentially serious:

Notice how when config is a dictionary, you set `dict = config` but
when it's
not, you PyObject_GetAttrString() the config's __dict__. This sets up a
situation where outside this conditional, you are inconsistent with dict's
refcount. The if-clause has one lower reference than the else-clause
because
PyObject_GetAttrString returns a new reference. Thus it's possible that
PyDict_Check and PyDict_Next are operating on an object for which the
client
doesn't hold sufficient references. You're also leaking dict when
you've gone
through the else-clause. Suggestion: incref dict in the if-clause and
add a
decref of dict before the return at the end of the function.
This is dead code. configs as dictionaries have never worked and aren't 
used anywhere. We always just pass in None as the config so the default 
config gets used. I've removed this bit of code.




client.c:318 client_set_notify_funct() where notify_baton2 has
inconsistent
refcounting between the if-clause and else-clause. When you go through the
if-clause, notify_baton2 steals a reference to Py_None, which is going
to get
decref'd in client_dealloc(). The Py_XDECREF there does not protect
you from
the extra decref of Py_None! You can see that if you go through the
else-clause, func will get incref'd, but if you go through the
if-clause, you
actually leak func! Suggestion: incref notify_baton2 instead of func.
I don't follow - further down in that function we Py_INCREF func, so we 
always increment the reference count of func if we assign it to 
notify_baton2.




client_proplist, inside the props->nelts loop, the PyList_Append
return value
is not checked. Not likely to fail, but more seriously, `value` is leaked.
Py_BuildValue returns a new reference, but PyList_Append does not
steal its
reference. Thus you leak every `value`.

fixed.



editor.c:58, new_editor_object: you (probably, haven't checked the
call-sites)
need to incref commit_callback, since it gets decref'd in
py_editor_dealloc.
Looks like the refcounts are unmatched.

The caller is responsible for increasing the ref counter of commit_callback.


Other problems:

* wrap_py_commit_items(): leaks ret when the PyList_SetItem returns on
line
118.


Fixed.



* client.c:145: PyList_Append return value unchecked, probably
harmless though
a (void) should be added.


Fixed.



* client.c:167: similar for PyDict_SetItemString


Fixed.



* client.c:256: py_cancel_check should be incref'd?


It's a C function, I don't see why it could go away.



* client.c, multiple locations: PyArg_Parse* does not incref 'O'
arguments, so
be careful about calling back into Python with any such parsed object. You
need to ensure your library increfs such objects before a potential call
back into Python, and then decrefs it when you're done with the Python
call. I haven't audited all the places this happens, so this could be a
false alarm (i.e. you don't call back into Python).

I'm not aware of any places where we do that in client.c.



* client.c:925: prop_list leaks in the error condition return
* client.c:1037: leaks ret when PyList_SetItem returns non-zero.

fixed.

* client.c:1086: leaks entry_dict in the error return path






* client.c:1251: PyList_SetItem return value not checked


fixed.



* client.c:1279: PyDict_SetItemString return value not checked


fixed.




* client.c:1473: leaks `data` when data->pool is NULL.


Fixed.

Cheers,

Jelmer



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#629883: e2fsprogs: FTBFS: parse.c:56:20: error: 'errno' undeclared (first use in this function)

2011-09-19 Thread Ted Ts'o

tag 629883 +pending
thanks

I recently was able to reproduce this.  It looks like some shellutil
program used by configure has a 4k line length problem.  The problem
doesn't show up on Ubuntu 10.04/x86_64, and it doesn't show up in my
sid/i386 chroot (which is what I normally upload to the ftp archives)
and apparently it doesn't show up in the official x86_64/buildd's

But it did show up in your (Didier's) test builds, and it recently
popped for me as well when I created a sid/x86_64 chroot to do some
unrelated development/test work.  The problem is that there is this
line in MCONFIG.in:

DEFS = @DEFS@

which gets pulled into all of the make files.  @DEFS@ is about 4200
bytes.  This resulted in a corrupted line in the generated MCONFIG
file, and hence in all of the Makefiles.  This caused all of the
autoconf-generated declarations (e.g., -DHAVE_ERRNO_H, et. al) to get
lost, and that's what caused the 'errno' undeclared compilation error.

Why the problem doesn't show up the 32-bit sid environment, but only
the 64-bit sid environment (and as a regression to boot since Ubuntu
10.04 doesn't exhibit this bug) is an interesting one, but I'll leave
that for another day or another developer to figure out.  I've worked
around the problem in e2fsprogs by using a config.h file instead of
passing all of the defines on the command-line -- a better solution
anyway.

- Ted



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#556172: Final reminder to connect with Ian Carson on Ecademy

2011-09-19 Thread Ian Carson

Ecademy - Exclusive business networking for the digital age
___

Join me on Ecademy
http://www.ecademy.com/account.php?op=signup&xref=615472

 Connect to the right people
 Market your business
 Grow revenue

Ian Carson
iancar...@live.com
___
This email was sent to 556...@bugs.debian.org
To avoid receiving these emails in the future go to
http://www.ecademy.com/blockinvites.php?e=556...@bugs.debian.org  
The Ecademy Limited. Registered in England and Wales.
Company Registration:3651083 VAT:718037736

Bug#624967: fix ftbfs with g++-4.6


patch at
http://launchpadlibrarian.net/80358432/linpsk_1.1-1_1.1-1ubuntu1.diff.gz




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#624967: fix ftbfs with g++-4.6