Bug#670064: (no subject)

[Dylan Borg]

the logs may be removed.
The binaries in the 2.0 and 4.0 directories may not since they are used in the 
build to remake them.
As for the log,the latest version is an adaptation of a previous version 
released in a ppa. The full log can be found in the package.

Regards,
  Dylan Borg
  borgdy...@hotmail.com
  borgdyl...@gmail.com
  dbor0...@um.edu.mt
  +0035699214902

Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

[Fabian Greffrath]

Am Sonntag, den 22.04.2012, 17:16 +0100 schrieb Brian Potkin:
> From comment #55 in bug report #662660 I'd expect a text file to be printed 
> with
> the mono-spaced Liberation font. Using a backend similar to the one described 
> in
> the cups-filters README the output file in /tmp was empty and the error_log 
> (which
> is attached) reported "No usable font available". Adding the ttf-dejavu-core 
> package
> restores the capability to print text files.

Indeed, it is expected to print the page with LiberationSans. I assume
that we are talking about regular text here, with no "special" or e.g.
Chinese glyphs?

What does "fc-match -s FreeMono" give on your system?

 - Fabian





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

Bug#669951: Obsolete conffile /etc/bash_completion.d/systemctl-bash-completion.sh not cleaned up on upgrade

[Raphael Hertzog]

Hi,

On Sun, 22 Apr 2012, Michael Biebl wrote:
> Personally, I would prefer, if dpkg-maintscript would use
> first-fixed-version instead of priorversion (i.e. < instead <=), as you
> know exactly the version when the conffile was (re)moved, but you can't
> be sure about value of priorversion, since this might change (e.g. by a
> binNMU).
> 
> Raphael, what was the reasoning for choosing the current syntax?

The difference between the two is dim and the latest version of the manual
page already advises to build up the biggest possible unfixed version for
similar reasons:


priorversion defines the latest version of the package whose upgrade
should  trigger the  removal.  It is important to calculate priorversion
correctly so that conffiles are correctly removed even if the user rebuilt
the package with a local version. For example,  for  a conffile removed in
version 2.0-1 of a package, priorversion should be set to 2.0-1~. This
will cause the conffile  to  be  removed  even  if  the  user rebuilt the
previous version 1.0-1 as 1.0-1local1.


> Maybe should have used 43-1~~ instead of 37-1. This is ugly, but it
> would have avoided this particular problem and it even would be
> backport-safe.

"43-1~ < 43-1~bpo60" so "43-1~" should be enough

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/liberation/



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

Bug#669059: webkit-1.8.0-2: FTBFS on hurd-*

[Guillem Jover]

On Wed, 2012-04-18 at 08:35:23 +0200, Svante Signell wrote:
> Attached is an updated patch. This patch together with the one in
> #664810 would enable a successful build of webkit-1.8.0 for GNU/Hurd.

> --- a/Source/JavaScriptCore/wtf/gobject/GlibUtilities.cpp 2012-02-19 
> 18:45:45.0 +0100
> +++ b/Source/JavaScriptCore/wtf/gobject/GlibUtilities.cpp 2012-04-18 
> 08:18:39.0 +0200
> @@ -40,11 +42,21 @@
>  #elif OS(UNIX)
>  CString getCurrentExecutablePath()
>  {
> -static char readLinkBuffer[PATH_MAX];
> -ssize_t result = readlink("/proc/curproc/file", readLinkBuffer, 
> PATH_MAX);
> -if (result == -1)
> -return CString();
> -return CString(readLinkBuffer, result);
> +struct stat sb;
> +char *readLinkBuffer;
> +ssize_t result;
> +result = lstat("/proc/curproc/file", &sb);
> +readLinkBuffer = (char*)malloc(sb.st_size + 1);
> +if (readLinkBuffer == NULL)
> +  return CString();
> +result = readlink("/proc/curproc/file", readLinkBuffer, sb.st_size + 1);
> +CString resultString;
> +if (result >= 0 && result < sb.st_size)
> +  resultString = CString(readLinkBuffer, result);
> +else
> +  resultString = CString();
> +free(readLinkBuffer);
> +return resultString;
>  }
>  #elif OS(WINDOWS)
>  CString getCurrentExecutablePath()

As mentioned on the list this code will not work on the Hurd, a new
implementation needs to be done for OS(HURD) just before OS(UNIX),
because OS(UNIX) will match for the Hurd too. I gave a hint on how
this can be implemented on the list.

thanks,
guillem



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

Bug#670046: [Pkg-xfce-devel] Bug#670046: hddtemp error launching xfce4sensors

[Yves-Alexis Perez]

On dim., 2012-04-22 at 18:13 +0200, Cesare Leonardi wrote:
> In the initial message i wrote:
> > Since few days ago the popup error was single, for sda. Now it pops up
> > also for /dev/sdb that it is neither present on my system:
> 
> Ok, i think this behaviour is explainable (even if not that clear to me) 
> and reproducible: i often use this laptop to recharge my smartphone. 
> Even if it's not seen as mass storage (Android 2.3: i have to activate 
> this on the device), whenever i attach it to the laptop usb's port, 
> xfce4-sensors show also a /dev/sdb popup error, even if it's not 
> mentioned in /proc/partitions. When i detach it, xfce4-sensors returns 
> to show only the /dev/sda error.
> 
> Tell me if i should file a new bug for this or can be ignored.

Well, hddtemp doesn't care about partitions, so that one doesn't look
like a bug.

-- 
Yves-Alexis


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

Bug#670046: [Pkg-xfce-devel] Bug#670046: hddtemp error launching xfce4sensors

[Yves-Alexis Perez]

On dim., 2012-04-22 at 18:13 +0200, Cesare Leonardi wrote:
> In the initial message i wrote:
> > Since few days ago the popup error was single, for sda. Now it pops up
> > also for /dev/sdb that it is neither present on my system:
> 
> Ok, i think this behaviour is explainable (even if not that clear to me) 
> and reproducible: i often use this laptop to recharge my smartphone. 
> Even if it's not seen as mass storage (Android 2.3: i have to activate 
> this on the device), whenever i attach it to the laptop usb's port, 
> xfce4-sensors show also a /dev/sdb popup error, even if it's not 
> mentioned in /proc/partitions. When i detach it, xfce4-sensors returns 
> to show only the /dev/sda error.

> 
> Tell me if i should file a new bug for this or can be ignored.
> 


-- 
Yves-Alexis



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

Bug#666360: [3.2.6 -> 3.2.7 regression] i915: HDMI/DVI output broken on Dell Latitude E6410 (Re: fixed in 3.3.3 and 3.2.16)

[Jonathan Nieder]

Brice Goglin wrote:

> In you missed it, the fix has been backported to 3.3.3 and 3.2.16.

Thanks for making it happen.

Sincerely,
Jonathan



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

Bug#666360: fixed in 3.3.3 and 3.2.16

[Ben Hutchings]

On Mon, 2012-04-23 at 07:19 +0200, Brice Goglin wrote:
> In you missed it, the fix has been backported to 3.3.3 and 3.2.16.

Noted, thanks.

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


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

Bug#670118: [PATCH] Add support for logging cron job output to syslog

[Josh Triplett]

Package: cron
Version: 3.0pl1-121
Severity: wishlist
Tags: patch

The attached patches make it possible for cron to log cron job output to
syslog.

Patch 1 adds a new log level 16, which unconditionally logs cron job
output.

Patch 2 adds a new log level 32, which logs cron job output if and only
if the output will not get mailed, such as if the system has no MTA.
Using this log level will ensure that cron job output won't get
discarded.

Patch 3 enables log level 32 by default in the Debian package via
/etc/default/cron.  This will ensure that the Debian package of cron
automatically uses an MTA if available, or syslog if not.

Patch 4 updates the Suggests and Recommends of the Debian packages, to
suggest both a syslog daemon and a mail-transport-agent, but recommend
just one or the other; thus, the recommended configuration will always
capture cron job output in one way or another.  This patch also updates
cron to use default-mta rather than hardcoded MTAs.

I included corresponding updates to debian/changelog for convenience,
but if updates occur to the changelog before the application of these
patches, they'll probably fail to apply; however, merging should prove
trivial if so.

Please consider applying these patches.

Thanks,
Josh Triplett
>From acb04be1e5d49f72b6bf6513b294c393b68f18f9 Mon Sep 17 00:00:00 2001
From: Josh Triplett 
Date: Sun, 22 Apr 2012 19:20:54 -0700
Subject: [PATCH 1/4] Add a new log level to log all cron job output.

---
 cron.8  |5 ++--
 cron.h  |1 +
 debian/changelog|4 +++
 debian/cron.default |1 +
 do_command.c|   70 ++-
 5 files changed, 45 insertions(+), 36 deletions(-)

diff --git a/cron.8 b/cron.8
index 586d9e5..5985700 100644
--- a/cron.8
+++ b/cron.8
@@ -54,11 +54,12 @@ will log the end of all cron jobs
 will log all failed jobs (exit status != 0)
 .IP \fB8\fR
 will log the process number of all cron jobs
+.IP \fB16\fR
+will log the full output of all cron jobs
 .RE
 .IP
 The default is to log the start of all jobs (1). Logging will be disabled
-if \fIlevels\fR is set to zero (0). A value of fifteen (15) will select all
-options.
+if \fIlevels\fR is set to zero (0). A value of 31 will select all options.
 .SH NOTES
 .PP
 .I cron
diff --git a/cron.h b/cron.h
index d1b2bcf..d0cf070 100644
--- a/cron.h
+++ b/cron.h
@@ -139,6 +139,7 @@ typedef int time_min;
 #define	CRON_LOG_JOBEND		0x02
 #define	CRON_LOG_JOBFAILED	0x04
 #define	CRON_LOG_JOBPID		0x08
+#define	CRON_LOG_JOBOUTPUT	0x10
 
 #define SECONDS_PER_MINUTE 60
 
diff --git a/debian/changelog b/debian/changelog
index 139c800..99891b5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,15 @@
 cron (3.0pl1-122) UNRELEASED; urgency=low
 
+  [ Javier Fernández-Sanguino Peña ]
   * debian/standard.daily: Apply patch from Steve Allison to prevent checking
  two times the same filesystem. This prevents bogus warnings about missing
  lost+found in schroot bind mounts (Closes: #660879)
   * debian/rules: Apply patch from Steve Langasek to add cross compiler support to
 cron (Closes: #666892)
 
+  [ Josh Triplett ]
+  * Add a new log level to log all cron job output.
+
  -- Javier Fernández-Sanguino Peña   Mon, 09 Apr 2012 17:23:01 +0200
 
 cron (3.0pl1-121) unstable; urgency=low
diff --git a/debian/cron.default b/debian/cron.default
index c69934f..ed4383d 100644
--- a/debian/cron.default
+++ b/debian/cron.default
@@ -23,6 +23,7 @@ READ_ENV="yes"
 #   2   log end of jobs
 #   4   log jobs with exit status != 0
 #   8   log the process identifier of child process (in all logs)
+#   16  log the full output of all cron jobs
 #
 #EXTRA_OPTS=""
 
diff --git a/do_command.c b/do_command.c
index 18d097d..c2fc9f7 100644
--- a/do_command.c
+++ b/do_command.c
@@ -511,6 +511,7 @@ child_process(e, u)
 // since sendmail may time out, and to write info about the exit
 // status.
 	
+	register FILE	*mail = NULL;
 	long pos;
 	struct stat	mcsb;
 	int		statret;	
@@ -522,26 +523,25 @@ child_process(e, u)
 	Debug(DPROC|DEXT, ("[%d] got %ld bytes data from grandchild tmpfile\n",
 getpid(), (long) pos))
 	if (pos == 0)
-		goto mail_finished;
+		goto output_finished;
 
 	// get name of recipient.
 	if (mailto == NULL)
 		mailto = usernm;
 	else if (!*mailto)
-goto mail_finished;
+goto mail_headers_finished;
 
 	/* Don't send mail if MAILCMD is not available */
 	if ((statret = stat(MAILCMD, &mcsb)) != 0) {
 		Debug(DPROC|DEXT, ("%s not found, not sending mail\n", MAILCMD))
 		if (pos > 0) {
-			log_it("CRON", getpid(), "info", "No MTA installed, discarding output");
+			log_it("CRON", getpid(), "info", "No MTA installed, not mailing output");
 		}
-		goto mail_finished;
+		goto mail_headers_finished;
 	} else {
 		Debug(DPROC|DEXT, ("%s found, will send mail\n", MAILCMD))
 	}
 
-	register FILE	*mail = NULL;
 	register int	bytes = 1;
 
 	register char	**env;
@@ -556,7 +556,7 @@ child_process(e, u)

Bug#644767: patch away npm routines instead of depending on npm

[Jonas Smedegaard]

Hi,

I noticed that the dependencies are almost satisfied by now.  Very 
exciting!

Your packaging at git.debian.org:/git/pkg-grass/tilemill declare a 
dependency on npm which I found odd and looking closely it seems the 
only use of npm is for checking if tilemill itself is up-to-date and 
allowing self-update and removal from within the application.  That will 
most likely fail due to the application not being installed with npm in 
the first place, and I recommend to at least dorp that dependency and 
better to also patch the code to not offer those npm-specific features.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: Digital signature

Bug#666360: fixed in 3.3.3 and 3.2.16

[Brice Goglin]

In you missed it, the fix has been backported to 3.3.3 and 3.2.16.
Brice




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

Bug#670066: python-openturns is unusable

[Christophe Prud'homme]

Denis

This work(debian packaging)  is also done by Phimeca who maintains
openturns, or did you use their work ?

I do not have preferences for the soname

see ya
C.

On Mon, Apr 23, 2012 at 12:06 AM, D. Barbier  wrote:

> Le 22 avril 2012 22:11, D. Barbier  a écrit :
> > Le 22 avril 2012 20:31, D. Barbier  a écrit :
> >> Le 22 avril 2012 20:19, Christophe Prud'homme  a
> écrit :
> >>> Denis
> >>>
> >>> I received some patches for openturns from J. Schueller.
> >>>
> >>> I will apply them and upload a new version for 0.15 then work on 1.0
> >>
> >> Christophe, I already almost finished packaging for 1.0, the only
> >> issue is with python.  But I do not know where to push these changes
> >> so that you can review them.
> >> BTW, we should IMHO change the SONAME, do you have any preference?
> >
> > Christophe, I just created a git repository to publish my changes:
> >  https://github.com/dbarbier/deb-ot
> >
> > There are instructions at
> >  https://github.com/dbarbier/deb-ot/wiki
> > to transform it into a git-svn repository.
>
> Hi again,
>
> I do not know why, but it seems that this is due to python extensions
> being linked against python2.7 library.  It now works fine in my CMake
> build.
>
> Denis
>

Bug#668780: pu: package nvidia-graphics-drivers/195.36.31-6squeeze1

[Adam D. Barratt]

On Thu, 2012-04-19 at 11:00 +0200, Andreas Beckmann wrote:
> On 2012-04-14 13:59, Adam D. Barratt wrote:
> > Thanks for working on fixing this in stable.  fwiw, "-6+squeeze1" is
> > more conventional, although it's unlikely to make a difference in this
> > case.  Please feel free to go ahead with the upload.
> 
> I'm not exactly sure whether the nvidia-graphics-modules packages in
> squeeze would work with "-6+squeeze1", but it does work with "-6squeeze1".

I didn't immediately spot a reason why it shouldn't, but you know the
package better, so okay.

> I'm hesitating with an upload because Nvidia recommends not to use the
> patch for a lot of older GPUs due to regressions:
> 
> http://www.nvnews.net/vbulletin/showthread.php?t=178460

Yay. :-/

> PS: will I be able to do the upload myself or does it need to be
> sponsored? I'm DM and have DMUA in the packages in sid, but there are a
> few transitional packages in squeeze that are no longer built.

I think it works, as long as the latest unstable/experimental upload has
the flag set.  There's one way to find out for sure... ;-)

Regards,

Adam




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

Bug#669949: [Pkg-sysvinit-devel] Bug#669949: sysvinit: Break X11: no more mouse and keyboard

[Henrique de Moraes Holschuh]

On Mon, 23 Apr 2012, Henrique de Moraes Holschuh wrote:
> On Sun, 22 Apr 2012, Roger Leigh wrote:
> > I'm not sure that this is definitely a sysvinit issue.  The mouse
> > and keyboard are entirely functional right up until X11 starts up.
> 
> This may well be a red herring, but you're all using the latest 3.2
> kernel, aren't you?  A Debian user went straight to LKML with an udev
> issue related to the later 3.2 kernels (which was a _lot_ worse than
> just input devices disappearing, I think.  I will have to hunt down that
> message).

Hmm, found it and it is a very different issue, related to udevadm
settle and event filtering.  It is unlikely to be related to this
problem.

> It is not impossible that an interaction of the latest sysvinit with the
> later 3.2 kernels is causing problems if we changed _anything_ that has
> direct interaction with the kernel (such as an ioctl, signal masks...)
> in the latest sysvinit that could trigger a kernel issue.
> 
> Did we?

That's still a question worth considering.

-- 
  "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#669949: [Pkg-sysvinit-devel] Bug#669949: sysvinit: Break X11: no more mouse and keyboard

[Henrique de Moraes Holschuh]

On Sun, 22 Apr 2012, Roger Leigh wrote:
> I'm not sure that this is definitely a sysvinit issue.  The mouse
> and keyboard are entirely functional right up until X11 starts up.

This may well be a red herring, but you're all using the latest 3.2
kernel, aren't you?  A Debian user went straight to LKML with an udev
issue related to the later 3.2 kernels (which was a _lot_ worse than
just input devices disappearing, I think.  I will have to hunt down that
message).

It is not impossible that an interaction of the latest sysvinit with the
later 3.2 kernels is causing problems if we changed _anything_ that has
direct interaction with the kernel (such as an ioctl, signal masks...)
in the latest sysvinit that could trigger a kernel issue.

Did we?

Can anyone that is reproducing this bug try an older kernel (preferably
not the latest 3.0, as all longterm kernels are somewhat sync'd and if
something caused a regression in 3.2-stable, changes are high it is
already in 3.0-stable too).

> I've tested this in single user mode, running the init scripts by
> hand.  It's all working perfectly up until kdm/gdm starts, and it
> can be triggered by hand with xinit.
> 
> All of the tmpfses, including /dev, are mounted and functional.

X.org makes use of several input-layer features/ioctls/etc that very
few/no other programs would during boot.

-- 
  "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#670054: [Debichem-devel] Bug#670054: rdkit: FTFBS on powerpc / s390x / sparc (test suite failures)

[Greg Landrum]

This is almost certainly a problem with byte-ordering and the RDKit's
method of handling serialization.

I'm sure it's not that tough to fix, and I will happily do the work,
but I don't have access to a big-endian machine to do the development
work and testing. Is there a straightforward solution to this?

-greg

On Sun, Apr 22, 2012 at 6:14 PM, Adam D. Barratt
 wrote:
> Source: rdkit
> Version: 201112-1
> Severity: serious
> Tags: wheezy sid
>
> Hi,
>
> rdkit FTBFS on powerpc, s390x and sparc due to test suite failures.
> From the powerpc build log:
>
> 88% tests passed, 9 tests failed out of 76
>
> Total Test time (real) = 113.88 sec
>
> The following tests FAILED:
>          2 - testDataStructs (OTHER_FAULT)
>          4 - pyDiscreteValueVect (Failed)
>          5 - pySparseIntVect (Failed)
>          7 - testGrid (OTHER_FAULT)
>         22 - graphmoltestPickler (OTHER_FAULT)
>         42 - pyMolDescriptors (Failed)
>         66 - pyCMIM (Failed)
>         67 - pyRanker (Failed)
>         69 - pyFeatures (Failed)
> Errors while running CTest
> make[2]: *** [test] Error 8
> make[2]: Leaving directory 
> `/build/buildd-rdkit_201112-1-powerpc-PES4nC/rdkit-201112/obj-powerpc-linux-gnu'
> dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2
> make[1]: *** [override_dh_auto_test] Error 29
> make[1]: Leaving directory 
> `/build/buildd-rdkit_201112-1-powerpc-PES4nC/rdkit-201112'
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
> Full logs available via
> https://buildd.debian.org/status/package.php?p=rdkit
>
> Regards,
>
> Adam
>
>
>
>
> ___
> Debichem-devel mailing list
> debichem-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debichem-devel



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

Bug#670116: linux-image-2.6.32-5-amd64: Kernel BUG at [...] fs/inode.c:330 when using glusterfs/fuse

[Ben Hutchings]

On Mon, 2012-04-23 at 10:42 +0800, James Andrewartha wrote:
> Package: linux-2.6
> Version: 2.6.32-41squeeze2
> Severity: normal
> 
> 
> I'm running glusterfs 3.2.4 from backports, and am seeing occasional hangs 
> when
> rsyncing. It might possibly be related to 
> https://bugzilla.kernel.org/show_bug.cgi?id=15927
[...]

It does look similar.

Can you test whether Linux 3.2 (currently in testing, unstable and
squeeze-backports) also has this problem?

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


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

Bug#670117: carto: should recommend or suggest node-millstone

[Jonas Smedegaard]

Package: carto
Version: 0.4.6+ds1-1
Severity: normal

Documentation describes millstone as being somewhat a companion tool, so
should probably be suggested (if not recommended).

Similarly node-millstone should probably enhance carto.

 - Jonas



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

Bug#661844: please respect sys admin set perms in /var/lib/shorewall

[Roberto C . Sánchez]

On Sun, Apr 22, 2012 at 05:21:53PM -0400, Jeffrey Sheinberg wrote:
> On Sat, Apr 21, 2012 at 08:28:19PM -0400, Roberto C. S?nchez wrote:
> 
> > These files are regenerated everytime Shorewall is started/restarted.
> > The only way to achieve the behavior you describe is to change the umask
> > prior to starting/restarting Shorewall.  Because this is external to
> > Shorewall, I am closing this report.
> 
> Hi Roberto,
> 
> This is a shorewall problem - the files are being "regenerated", this is
> the problem.
> 
> The files in question should simply be truncated when opened.  This is normal
> behavior of most unix programs, unless they have a good reason to do
> otherwise.
> 

Except that would result in a wiping out known good configurations
before it is known that the new configuration is good (in the chase of a
restart).  This would not be acceptable, as it could eliminate the
administrators capability to safely restart.  What Shorewall does is to
create the new files under temporary names, and on successful completion
removing the old file and moving the new file into place.  Truncation
would not work in that case.

I recommend that you look at placing any 'chmod' commands that you
require into /etc/shorewall/started.

Please see http://shorewall.net/shorewall_extension_scripts.htm for
additional information.

Regards,

-Roberto
-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Bug#670100: e2fsprogs: Please don't use blocksize of 1024 in usage-type 'small'

[Ted Ts'o]

On Mon, Apr 23, 2012 at 01:17:34AM +0300, Touko Korpela wrote:
> Package: e2fsprogs
> Version: 1.42.2-2
> Severity: normal
> 
> I noticed that mke2fs has a default blocksize of 1024 bytes when it uses
> filesystem type 'small' (3-512MB) from mke2fs.conf.
> It's a bad thing for performance (more so now when 4K sector HDDs and SDDs
> are common). Also space savings are quite small.

You can always override the blocksize if you feel strongly about this.

The performance problem is only true on very new disks --- and it's
rare that someone would be formatted a file system so small on such
disks.  I'll also note that many SDD's can handle 512 byte mis-aligned
blocks (i.e., Windows XP formatting) just fine.  It doesn't make any
difference at all on Intel SSD's, for example.

Secondly, mke2fs will use 4k blocks if the drive requires it (i.e.,
for Advanced Format disks with 4k sectors).  So the problem you're
worried about only occurs for Advanced Format drives with 512e
emulation.

Finally, the only file system where someone is likely to be creating
that is this small in this day and age is the /boot filesystem --- and
there, even if the drive using 512-byte emulation, performance isn't
an issue since no one is executing out of /boot, or even modifying it
very often.

- Ted



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

Bug#670115: powertop: 32-bit powertop does not work properly with 64-bit kernel

[David Gibson]

Package: powertop
Version: 1.97-2
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

I am running i386 (32-bit) Debian, but using the 64-bit x86_64 kernel
package.  If I install and run the normal i386 powertop, most of
information is missing: on the main screen the 'Description' field is
empty for nearly all entries.  Other fields may also be incorrect,
without the description, it is difficult to tell.

If I use the new multiarch support to install powertop:amd64, then the
'Description' field appears correctly, showing the various processes
causing wakeups.

*** End of the template - remove these lines ***


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 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 powertop depends on:
ii  libc6 2.13-27
ii  libgcc1   1:4.7.0-3
ii  libncursesw5  5.9-6
ii  libnl22.0-1
ii  libpci3   1:3.1.9-2
ii  libstdc++64.7.0-3
ii  zlib1g1:1.2.6.dfsg-2

powertop recommends no packages.

Versions of packages powertop suggests:
pn  cpufrequtils   007-2
pn  laptop-mode-tools  

-- 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#670114: nmu: shogun_1.1.0-4

[Yaroslav Halchenko]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu shogun_1.1.0-4 . ALL . -m "Binary rebuild against numpy 1.6.1 in sid"


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



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

Bug#669949: sysvinit breaks X11: no more mouse and keyboard

[Jos van Wolput]

Package: sysvinit
Version: 2.88dsf-23

I too can confirm this bug.

-- System Information:
Debian Release: wheezy/sid + experimental
Architecture: amd64
Kernel~3.3.0-2.dmz.1-liquorix-amd64





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

Bug#655643: pymvpa: FTBFS: AttributeError: classify

[Yaroslav Halchenko]

block 655643 by 669005
thanks

Hi Colin, Hi Jakub

thanks for the report and sorry for lousy handling of this issue.
Apparently I have fixed that upstream months ago but we never pushed out
a bugfix 0.4.8 -- I will do that in upcoming days and it would close
this issue... the only problem is that shogun-python-modular is
uninstallable on sid (#669005) which would preclude closing this
issue -- I guess I will just request a binNMU first on behalf of Soeren.

Cheers,

On Fri, 20 Apr 2012, Colin Watson wrote:
> > |   File "/usr/lib/python2.7/dist-packages/modshogun.py", line 59, in 
> > _swig_getattr
> > | raise AttributeError(name)
> > | AttributeError: classify

> This was due to an API change in shogun 1.0.0.  From src/ChangeLog:

>   rename classify / classify_example to more generic apply() - to be used
>   in all machines. adjust examples accordingly.

> Here's a patch to handle both the old and the new API.

>   * Adjust for API change in Shogun 1.0.0 (closes: #655643).

-- 
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic



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

Bug#645193: pbs-drmaa-dev and libdrmaa-dev: error when trying to install together

[Dominique Belhachemi]

I updated pbs-drmaa and slurm-drmaa to use Debian's alternative system.

I would like to do the same with the current libdrmaa1.0 package which
is gridengine specific. To stay compatible to the other
implementations I would like to change some binary package names as
well.

libdrmaa1.0 -> gridengine-drmaa1.0
libdrmaa-dev - > gridengine-drmaa-dev

Please let me know if this causes any problems.

-Dominique



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

Bug#670113: Wrong pkg-config file causes other packages to FTBFS

[Alessio Treglia]

Package: libflowcanvas-dev
Version: 0.7.1+dfsg0-0.1+b1
Severity: serious
Tags: patch

Hi,

flowcanvas.pc contains hard-coded flags/libraries which causes ladish
to fail to build from source:

> [ 30/142] c: gui/control.c -> build/gui/control.c.10.o
> In file included from /usr/include/gtkmm-2.4/gtkmm.h:87:0,
>  from /usr/include/libgnomecanvasmm-2.6/libgnomecanvasmm.h:29,
>  from /usr/include/flowcanvas/Canvas.hpp:27,
>  from ../gui/canvas.cpp:28:
> /usr/include/glibmm-2.4/glibmm.h:82:26: fatal error: glibmmconfig.h: No such 
> file or directory
> compilation terminated.

The header "glibmmconfig.h" has moved into the multiarch path and the pkg-config
file should set a proper Requires field instead of providing a list of 
hard-coded
paths of dependencies in Libs and Cflags.

A patch is appended below, thanks for considering.

--- flowcanvas.pc.in2010-06-13 20:06:42.0 +0200
+++ flowcanvas.pc.in.new2012-04-23 03:23:16.037664855 +0200
@@ -6,5 +6,6 @@
 Name: flowcanvas
 Version: @FLOWCANVAS_VERSION@
 Description: A Gtkmm canvas widget for graph based interfaces
-Libs: -L${libdir} -lflowcanvas @GNOMECANVASMM_LIBS@
-Cflags: -I${includedir} @GNOMECANVASMM_CFLAGS@
+Requires: libgnomecanvasmm-2.6
+Libs: -L${libdir} -lflowcanvas
+Cflags: -I${includedir}


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libflowcanvas-dev depends on:
ii  libflowcanvas5  0.7.1+dfsg0-0.1+b1

libflowcanvas-dev recommends no packages.

libflowcanvas-dev suggests no packages.

-- no debconf information



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

Bug#501134: RAW-pictures break down after copied on a crypted raid5

[Ben Hutchings]

On Sat, 2008-10-04 at 17:01 +0200, daniel starzmann wrote:
> Package:  linux-image-2.6.24-etchnhalf.1-486
> Version:  ?
> 
> 
> Hello,
> I have an extra-ordinary problem or perhaps an Kernel bug:

I'm very sorry that we haven't responded to your bug report.  It is
clearly a serious bug, but your report seems to have been missed due to
changes in package names.

> My Server: 
> * Debian Etch (Kernel: Etch-n-half), Samba 3.0.24
> * 500gb harddisk with a system and a data partition. Both are crypted
> with Luks (cipher:serpent-cbc-essiv:sha256)
> * Raid 5 crypted with Luks (cipher:  serpent-cbc-essiv:sha256)
> * All partitions have the ext3 filesystem
> 
> Client1: Notebook (Windows XP and Fedora)
> Client2: Desktop (Fedora)
> I did all tests from both clients
> 
> My problem:
> I tried to copy RAW pictures (*.cr2 files) from a client to the raid5
> partition with the following 4 different ways.
> 
> 1. I exported the raid partition with samba and copied the pictures with
> Windows XP and the Windows Explorer
> 2. I copied the pictures through an smb-mount with Fedora with the
> "cp"-command
> 3. I copied the pictures with the "scp"-command (first initiiated from
> the client and then from the server)
> 4. I copied the pictures with the "rsync"-command (first initiiated from
> the client and then from the server)

Thank you for the thorough testing.

> I checked the files after I had copied them with "md5sum" and I saw that
> the values where different to the values of the original files.
> The pictures where broken. They had lila stribes and where cutted in the
> half.
> I tried the same 4 methods and copied the pictures on the 500gb data
> partition and there where no failures or md5sum differences.
> Then I copied the pictures in an ssh shell with an normal cp-command
> from the local-partition to the raid5-partition. The md5sum values where
> the same, so this worked well.

It might just be that in this case the files were read back from the
cache (memory) instead of from the disk.

> So in my opinion the problem has to do with the crypted raid5.
> I tried to reproduce this failures with other files but i had this
> problem only with RAW (*.cr2 Canon) picture files.

Perhaps related to the size of the files?

> I tried to repair my system with these 3 Methods:
> 1. fsck.ext3 -y /dev/mapper/md0_crypt
> 2. fsck.ext3 -c -p  /dev/mapper/md0_crypt
> 3. server rebooted a few times
> I couldn't find out any failure messages in the log-files or at the
> booting.
> 
> 
> After many hours I found this out:
> With Kernel 2.6.24-etchnhalf.1-686, Kernel 2.6.24-etchnhalf.1-486 and
> Kernel 2.6.26-bpo.1-486 I could reproduce my Image-copy-problem. 
> As I booted the older Kernel 2.6.18-6-486 I where able to copy the
> pictures with any of the methods above and the md5sum values where OK.
> Because of this I think its an Kernel problem.
[...]

That certainly seems to be the case.  Do you know whether a later
version (e.g. Linux 2.6.32 in Debian 6.0 'squeeze') fixed this bug?

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


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

Bug#657413:

[Dominique Belhachemi]

I am going to upload a simple workaround very soon. I just have to
update patches/110-kernel.diff .

-Dominique



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

Bug#661844: please respect sys admin set perms in /var/lib/shorewall

[Jeffrey Sheinberg]

On Sat, Apr 21, 2012 at 08:28:19PM -0400, Roberto C. S?nchez wrote:

> These files are regenerated everytime Shorewall is started/restarted.
> The only way to achieve the behavior you describe is to change the umask
> prior to starting/restarting Shorewall.  Because this is external to
> Shorewall, I am closing this report.

Hi Roberto,

This is a shorewall problem - the files are being "regenerated", this is
the problem.

The files in question should simply be truncated when opened.  This is normal
behavior of most unix programs, unless they have a good reason to do
otherwise.

>From the open(2) man page,

   O_TRUNC
  If the file already exists and is a regular file  and  the  open
  mode  allows  writing  (i.e.,  is O_RDWR or O_WRONLY) it will be
  truncated to length 0.  If the file is a FIFO or terminal device
  file,  the  O_TRUNC  flag  is  ignored.  Otherwise the effect of
  O_TRUNC is unspecified.

   creat() is equivalent to open() with flags equal to O_CREAT|O_WRONLY|O_TRUNC.

Using the shell, it works like this,

$ umask
0022

$ touch aa

$ ls -l aa
-rw-r--r-- 1 jeff jeff 0 Apr 22 17:05 aa

$ umask 777

$ : >| aa

$ ls -l aa
-rw-r--r-- 1 jeff jeff 0 Apr 22 17:06 aa

$ touch bb

$ ls -l bb
-- 1 jeff jeff 0 Apr 22 17:06 bb

$ umask 022

For open(2), the umask has no effect unless the file being created did not
originally exist.

This means that shorewall is deleting these files, then creating them,
rather than just opening with O_CREAT|O_WRONLY|O_TRUNC flags.

This is a bug in shorewall.  Please re-open.

Thanks,
-- 
Jeffrey Sheinberg




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

Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

[Jonathan Nieder]

Teodor MICU wrote:

> I just tested this (linux image from stable-proposed-updates) and
> there is no change: the console is fuzzy during boot.

Great, thanks for testing.  How about the second question --- is the
radeon firmware installed?  You can find out with

dpkg -l firmware-linux

Just to be clear, if the bug is only reproducible when the radeon
firmware is not installed, it would still be an important bug.  That
would just help us to know where to look.



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

Bug#670112: jackd2: Jackd will not start if X not running.

[S. Massy]

Package: jackd2
Version: 1.9.8~dfsg.3+20120418gitf82ec715-1
Severity: important

Dear Maintainer,

While previous versions of jackdmp with dbus support merely printed an
error when unable to connect to X, this one will actually fail to start
as discussed here:
http://permalink.gmane.org/gmane.comp.audio.jackit/25430

This makes it impossible to use the current debian package of jackd2 on
any system which doesn't have X installe or is not currently running it
and requires rebuilding the package without the --dbus configure flag. 

As I see it, the only way to solve this problem is either revert back to
the old behaviour or have two packages for jackd2, one with dbus support
and one without.

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

Kernel: Linux 2.6.33.7.2-rt30.110905 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages jackd2 depends on:
ii  coreutils  8.13-3.1
ii  debconf [debconf-2.0]  1.5.42
ii  libasound2 1.0.25-2
ii  libc6  2.13-27
ii  libcelt0-0 0.7.1-1
ii  libgcc11:4.7.0-3
ii  libjack-jackd2-0   1.9.8~dfsg.3+20120418gitf82ec715-1
ii  libsamplerate0 0.1.8-4
ii  libsndfile11.0.25-4
ii  libstdc++6 4.7.0-3
ii  python 2.7.2-10
ii  python-dbus0.84.0-3

Versions of packages jackd2 recommends:
pn  jackd2-firewire  1.9.8~dfsg.3+20120418gitf82ec715-1
pn  libpam-modules   1.1.3-7
pn  qjackctl 

Versions of packages jackd2 suggests:
pn  jack-tools   20101210-2
pn  meterbridge  

-- debconf information:
* jackd/tweak_rt_limits: true

-- 



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

Bug#635345: alacarte should depend on gnome-panel

[Alejandro Carrazzoni]

Package: alacarte
Version: 0.13.2-3
Followup-For: Bug #635345

This patch allows alacarte to work without gnome-panel by using exo-desktop-
item-edit instead of gnome-desktop-item-edit. I tried it (using XFCE) and it
works fine.



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

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

Versions of packages alacarte depends on:
ii  gnome-menus 3.2.0.1-2
ii  python  2.7.2-10
ii  python-gmenu3.0.1-4
ii  python-gobject  3.2.0-3
ii  python-gtk2 2.24.0-3
ii  python-support  1.0.14

Versions of packages alacarte recommends:
pn  gnome-panel  

alacarte suggests no packages.

-- no debconf information
--- MainWindow.py	2011-10-14 04:19:55.0 -0300
+++ MainWindow.py	2012-04-22 21:31:26.0 -0300
@@ -259,7 +259,7 @@
 			self.item_store.append((show, icon, name, item))
 
 	#this is a little timeout callback to insert new items after
-	#gnome-desktop-item-edit has finished running
+	#exo-desktop-item-edit has finished running
 	def waitForNewItemProcess(self, process, parent, file_path):
 		if process.poll() != None:
 			if os.path.isfile(file_path):
@@ -269,7 +269,7 @@
 
 	def waitForNewMenuProcess(self, process, parent_id, file_path):
 		if process.poll() != None:
-			#hack for broken gnome-desktop-item-edit
+			#hack for broken exo-desktop-item-edit
 			broken_path = os.path.join(os.path.split(file_path)[0], '.directory')
 			if os.path.isfile(broken_path):
 os.rename(broken_path, file_path)
@@ -295,7 +295,7 @@
 		else:
 			parent = menus[iter][2]
 		file_path = os.path.join(util.getUserDirectoryPath(), util.getUniqueFileId('alacarte-made', '.directory'))
-		process = subprocess.Popen(['gnome-desktop-item-edit', file_path], env=os.environ)
+		process = subprocess.Popen(['exo-desktop-item-edit', file_path], env=os.environ)
 		gobject.timeout_add(100, self.waitForNewMenuProcess, process, parent.menu_id, file_path)
 
 	def on_new_item_button_clicked(self, button):
@@ -308,7 +308,7 @@
 		else:
 			parent = menus[iter][2]
 		file_path = os.path.join(util.getUserItemPath(), util.getUniqueFileId('alacarte-made', '.desktop'))
-		process = subprocess.Popen(['gnome-desktop-item-edit', file_path], env=os.environ)
+		process = subprocess.Popen(['exo-desktop-item-edit', file_path], env=os.environ)
 		gobject.timeout_add(100, self.waitForNewItemProcess, process, parent, file_path)
 
 	def on_new_separator_button_clicked(self, button):
@@ -379,7 +379,7 @@
 			self.editor._MenuEditor__addUndo([item,])
 		if file_path not in self.edit_pool:
 			self.edit_pool.append(file_path)
-			process = subprocess.Popen(['gnome-desktop-item-edit', file_path], env=os.environ)
+			process = subprocess.Popen(['exo-desktop-item-edit', file_path], env=os.environ)
 			gobject.timeout_add(100, self.waitForEditProcess, process, file_path)
 
 	def on_menu_tree_cursor_changed(self, treeview):

Bug#670111: libreadline-gplv2-dev: error when trying to install together with libreadline6-dev/squeeze (6.1-3)

[Andreas Beckmann]

Package: libreadline-gplv2-dev
Version: 5.2-11
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2012-04-23
Architecture: amd64
Distribution: squeeze->wheezy (partial) upgrade

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


  Selecting previously deselected package libreadline-gplv2-dev.
  Unpacking libreadline-gplv2-dev (from 
.../libreadline-gplv2-dev_5.2-11_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/libreadline-gplv2-dev_5.2-11_amd64.deb (--unpack):
   trying to overwrite '/usr/share/info/readline.info.gz', which is also in 
package libreadline6-dev 6.1-3


This is a serious bug as it makes installation/upgrade fail, and
violates sections 7.6.1 and 10.1 of the policy.

As this problem can be demonstrated during partial upgrades from squeeze
to wheezy (but not within squeeze or wheezy itself), this indicates a
missing or insufficiently versioned Replaces/Breaks relationship.
But since this particular upgrade ordering is not forbidden by any
dependency relationships, it is possible that apt (or $PACKAGE_MANAGER)
will use this erroneus path on squeeze->wheezy upgrades.

Here is a list of files that are known to be shared by both packages
(according to the Contents files for amd64, which may be
slightly out of sync):

  usr/include/readline/chardefs.h
  usr/include/readline/history.h
  usr/include/readline/keymaps.h
  usr/include/readline/readline.h
  usr/include/readline/rlconf.h
  usr/include/readline/rlstdc.h
  usr/include/readline/rltypedefs.h
  usr/include/readline/tilde.h
  usr/share/info/history.info.gz
  usr/share/info/readline.info.gz

The following relationships are currently defined:

Package: libreadline-gplv2-dev
Source: readline5
Version: 5.2-11
Replaces: libreadline5-dev
Depends: libreadline5 (= 5.2-11), libtinfo-dev, dpkg (>= 1.15.4) | install-info
Conflicts: libreadline-dev, libreadline5-dev


-Andreas

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


libreadline6-dev=6.1-3_libreadline-gplv2-dev=5.2-11.log.gz
Description: GNU Zip compressed data

Bug#670110: Several security issues

[David Prévot]

Package: spip
Version: 2.1.12-1
Severity: grave
Tags: security upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

Upstream, just released a new version, fixing several security issues,
most of them being XSS injection vulnerabilities.

http://article.gmane.org/gmane.comp.web.spip.devel/62536

I'm also preparing the stable security update.

Regards

David

- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages spip depends on:
ii  apache22.4.2-1
ii  apache2-bin [httpd]2.4.2-1
ii  cherokee [httpd]   1.2.101-1
ii  debconf [debconf-2.0]  1.5.42
ii  fonts-dustin   20030517-9
ii  libjs-jquery   1.7.2-1
ii  libjs-jquery-cookie4-1
ii  libjs-jquery-form  4-1
ii  php-html-safe  0.10.1-1
ii  php5   5.4.1~rc1-1
ii  php5-mysql 5.4.1~rc1-1

Versions of packages spip recommends:
ii  imagemagick  8:6.7.4.0-5
ii  mysql-server 5.1.61-3
ii  mysql-server-5.1 [mysql-server]  5.1.61-3
ii  netpbm   2:10.0-15+b1

spip suggests no packages.

- -- debconf information excluded

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

iQIcBAEBCAAGBQJPlKO0AAoJELgqIXr9/gnyTxMP/AmQRrhWEc1d7Ds5KVVU2nkk
E8+c7TcOQf7Y/oS5IOiWWX1TmlprURJiAjNkTBhQMSbajUUKpsSWVsHNXFnauFK8
PeGeHZr6BQ5ZZm+6Er8OpAFP3dMof+BKHPlJZF0x9MfY6aOHdbgltYF7hY9492MS
0Yo22zxf88QNkg8O74jdDtbu9VQ3iu+xrOG2eeyD9NuK5eCfm21UI14Sau09L8Al
Da9IkDQ31zzZi908ouyjusdStyZC16V63ci4CNg//jtrO627H6lheVQ+awiXmDOe
7CoHuN5QRxQGC8Ame03Dr63anpO9i8A800rjPPFBFikbBgOhOnGP9VQXkXvIYt7R
2JP2GwQ4823CBbn49k0IGtGQQvMiGSl5/jCRkLzmQc8sekd7/ZGcRkZTITXrwEG2
gsLK8gsD1d5lHqnLvF8uRq+0cScvi/4lkYXB3dBZ7gbVx8lOecdqhSYA7s0wIqL2
5xblEqVmsstib/V2wJ5GF0fWpuS2QUvyAFhP7MkyPDviKuwhVw8572oZG2Rm7XJz
HZpDt4RCC0m51qHyAUZ9k3GtJOanF47qh/Ixq58ZB675vtq7XNmkHZKvcsGOqeoY
5c961X0Lxe66hC4UrVnCj5x+Sxx2z+vjLOxSdCmh/KBq2jrvN4219f11ndYrIoe5
h98+VeDFaVoAkGMmsLLh
=v/Z6
-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#637106: still more typos.

[A. Costa]

Attached is a revised 'diff' file with the previous typos, plus several
others.  Most of the typos are grammatical, e.g. 's/have equal/be the same/'.

HTH...
--- -	2012-04-22 15:54:36.820306692 -0400
+++ /tmp/bbe.1_v2	2012-04-22 15:52:39.215724702 -0400
@@ -44,7 +44,7 @@
 Add the COMMAND to the commands to be executed.
 .TP 
 .BR  \-f ", " \-\-file=\fIscript\-file\fP
-Add the contest of script\-file to commands.
+Add the contents of script\-file to commands.
 .TP 
 .BR  \-o ", " \-\-output=\fIname\fP
 Write output to \fIname\fP instead of standard output.
@@ -71,10 +71,10 @@
 String \fIstart\fP starts \fIM\fR bytes long block.
 .TP 
 /start/:/stop/
-String \fIstart\fP starts the block and block ends to string \fIstop\fR.
+String \fIstart\fP starts the block and block ends at string \fIstop\fR.
 .TP 
 /start/:
-String \fIstart\fR starts the block and block will end at next occurence of \fIstart\fR. Only the first \fIstart\fR is included to the block.
+String \fIstart\fR starts the block and block will end at next occurrence of \fIstart\fR. Only the first \fIstart\fR is included to the block.
 .TP 
 :/stop/
 Block starts at the beginning of input stream (or at the end of previous block) and ends at the next occurrence of \fIstop\fR. String \fIstop\fR will be included to the block.
@@ -83,7 +83,7 @@
 .PP 
 Default value for block is 0:$, meaning the whole input stream.
 .PP 
-Both \fIstart\fR and \fIstop\fR strings are included to block. Nonprintable characters can be escaped as
+Both \fIstart\fR and \fIstop\fR strings are included in block. Nonprintable characters can be escaped as
 .TP 
 \ennn
 decimal 
@@ -96,9 +96,9 @@
 .PP 
 Character '\e' can be escaped as '\e\e'. Escape codes '\ea','\eb','\et','\en','\ev','\ef','\er' and '\e;' can also be used.
 .PP 
-Length (\fIN\fR and \fIM\fR) can be defined as decimal (n), hexadecimal (xn) or octal (0n) value.
+Length (\fIN\fR and \fIM\fR) can be defined as a decimal (n), a hexadecimal (xn) or an octal (0n) value.
 .SH "COMMAND SYNOPSIS"
-\fBbbe\fR has two type of commands: block and byte commands, both are allways related to current block. That means that the input stream outside of block remains untouched. 
+\fBbbe\fR has two type of commands: block and byte commands, both are always related to current block. That means that the input stream outside of the blocks remains untouched. 
 .SS Block commands
 .TP 
 D [\fIn\fR]
@@ -111,7 +111,7 @@
 Append the string \fIstring\fR at the end of block.
 .TP 
 J \fIn\fR
-Skip \fIn\fR blocks before executing commands after this command.
+Skip \fIn\fR blocks, before executing commands after this command.
 .TP 
 L \fIn\fR
 Leave all blocks unmodified starting from block number \fIn\fR. Affects only commands after this command.
@@ -120,7 +120,7 @@
 Before printing a block, the file name in which the block starts is printed.
 .TP 
 F \fIf\fR
-Before printing a block, the input stream offset at the begining of the block is printed.
+Before printing a block, the input stream offset at the beginning of the block is printed.
 \fIf\fR can be H, D or O for Hexadecimal, Decimal or Octal format of offset.
 .TP 
 B \fIf\fR
@@ -128,12 +128,12 @@
 \fIf\fR can be H, D or O for Hexadecimal, Decimal or Octal format of block number.
 .TP 
 > \fIfile\fR
-Before printing a block, the contents of file \fIfile\fR is printed.
+Before printing a block, the contents of file \fIfile\fR are printed.
 .TP 
 < \fIfile\fR
-After printing a block, the contents of file \fIfile\fR is printed.
+After printing a block, the contents of file \fIfile\fR are printed.
 .SS Byte commands
-\fIn\fR in byte commands is offset from the beginning of current block (starts from zero).
+\fIn\fR in byte commands is the offset from the beginning of current block (starts from zero).
 .TP 
 r \fIn\fR \fIstring\fR
 Replace bytes starting at position \fIn\fR with string \fIstring\fR.
@@ -143,13 +143,13 @@
 .TP 
 p \fIformat\fR
 The contents of block is printed in format defined by \fIformat\fR. \fIformat\fR
-can have any of the formats H, D, O, A and B for Hexadecimal, Decimal, Octal, Asciii and Binary.
+can have any of the formats H, D, O, A and B for Hexadecimal, Decimal, Octal, Ascii and Binary.
 .TP 
 s/\fIsearch\fR/\fIreplace\fR/
 Replace all occurrences of \fIsearch\fR with \fIreplace\fR.
 .TP 
 y/\fIsource\fR/\fIdest\fR/
-Translate bytes in \fIsource\fR to the corresponding bytes in \fIdest\fR. \fISource\fR and \fIdest\fR must have equal length.
+Translate bytes in \fIsource\fR to the corresponding bytes in \fIdest\fR. \fISource\fR and \fIdest\fR must be the same length.
 .TP 
 d \fIn\fR \fIm\fR|*
 Delete \fIm\fR bytes starting from the offset \fIn\fR. If * is defined instead of \fIm\fR, then all bytes starting from \fIn\fR are deleted.
@@ -170,17 +170,17 @@
 Commands after the l\-command are ignored from \fIn\fR'th byte of the block.
 .TP 
 w \fIfile\fR
-Write bytes from the current block to file \fIfile\fR. Commands before w\-command have effect to what will be written. 

Bug#637276: Version 3.0p is now available

[Rod Smith]

GNU-EFI 3.0i was released in September of 2009, so it's getting VERY 
OLD! The current version is 3.0p, released in December of 2011.


FWIW, I've recently forked rEFIt to create a new project, rEFInd, and 
rEFInd 0.2.7 and later require features not found in GNU-EFI 3.0i. I'm 
not sure when the required features were added, but GNU-EFI 3.0p is 
sufficient.


--
Rod Smith
rodsm...@rodsbooks.com
http://www.rodsbooks.com



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

Bug#639854: sidebar: fix when sidebar_delim is null

[Víctor Manuel Jáquez Leal]

Package: mutt-patched
Version: 1.5.21-5
Followup-For: Bug #639854

When running this comment got a segmentation fault:

~ $ mutt -e "set sidebar_delim="
Sorting mailbox...Segmentation fault

This because the sidebardelim string is not validated before doing a strlen,
which causes a segmentation fault.

This patch ensure that the variable is not null.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mutt-patched depends on:
ii  libc6 2.13-27
ii  libcomerr21.42.2-2
ii  libgnutls26   2.12.18-1
ii  libgpg-error0 1.10-3
ii  libgpgme111.2.0-1.4
ii  libgssapi-krb5-2  1.10+dfsg~beta1-2
ii  libidn11  1.24-2
ii  libk5crypto3  1.10+dfsg~beta1-2
ii  libkrb5-3 1.10+dfsg~beta1-2
ii  libncursesw5  5.9-6
ii  libnotmuch2   0.12-1
ii  libsasl2-22.1.25.dfsg1-4
ii  libtinfo5 5.9-6
ii  libtokyocabinet9  1.4.47-1
ii  mutt  1.5.21-5

mutt-patched recommends no packages.

mutt-patched suggests no packages.

-- no debconf information
>From dec9e02d322bc410b1a1f82604127573b760f1bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?V=C3=ADctor=20Manuel=20J=C3=A1quez=20Leal?=
 
Date: Mon, 23 Apr 2012 00:38:03 +0200
Subject: [PATCH] sidebar: fix null string segmentation fault

When running this comment got a segmentation fault:

~ $ mutt -e "set sidebar_delim="
Sorting mailbox...Segmentation fault

This because the sidebardelim string is not validated before doing a strlen,
which causes a segmentation fault.

This patch ensure that the variable is not null.

Conflicts:

	debian/patches/series
---
 debian/patches/mutt-patched/sidebar-delim |   22 ++
 debian/patches/series |1 +
 2 files changed, 23 insertions(+)
 create mode 100644 debian/patches/mutt-patched/sidebar-delim

diff --git a/debian/patches/mutt-patched/sidebar-delim b/debian/patches/mutt-patched/sidebar-delim
new file mode 100644
index 000..8a749ff
--- /dev/null
+++ b/debian/patches/mutt-patched/sidebar-delim
@@ -0,0 +1,22 @@
+Index: mutt/sidebar.c
+===
+--- mutt.orig/sidebar.c	2012-04-23 00:26:47.0 +0200
 mutt/sidebar.c	2012-04-23 00:29:18.0 +0200
+@@ -117,7 +117,7 @@
+ int box_len, box_bytes;
+ int int_len;
+ int right_offset = 0;
+-int delim_len = strlen(SidebarDelim);
++int delim_len = strlen(NONULL(SidebarDelim));
+ static char *entry;
+ 
+ right_width = left_width = 0;
+@@ -209,7 +209,7 @@
+ #ifndef USE_SLANG_CURSES
+ attr_t attrs;
+ #endif
+-short delim_len = strlen(SidebarDelim);
++short delim_len = strlen(NONULL(SidebarDelim));
+ short color_pair;
+ 
+ static bool initialized = false;
diff --git a/debian/patches/series b/debian/patches/series
index 49dac3d..d458178 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -61,6 +61,7 @@ mutt-patched/sidebar-dotted
 mutt-patched/sidebar-sorted
 mutt-patched/sidebar-utf8
 mutt-patched/multiple-fcc
+mutt-patched/sidebar-delim
 
 # not applying cleanly at the moment
 #mutt-patched/nntp
-- 
1.7.9.5

Bug#668240: guitarix: FTBFS(kfreebsd-i386): hangs during waf build

[Steven Chamberlain]

reassign 668240 src:python2.7
found 668240 2.7.2-8
close 668240 2.7.3~rc2-2.1
thanks

On 11/04/12 13:30, Roland Stigge wrote:
> ... #668240 can just be closed when
> the kfreebsd-i386 autobuilder built guitarix successfully.

The latest guitarix upload built successfully on kFreeBSD (maybe just
lucky that #668240 didn't cause FTBFS this time?)

Anyway Robert Millan has prepared a python2.7 NMU which means the
original cause of this is now fixed in sid, therefore closing this.  Thanks!

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org



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

Bug#670109: texlive-xetex: removal of texlive-xetex makes files disappear from texlive-math-extra

[Norbert Preining]

Hi Andreas,

Alas, there we go again ... funny games on Debian again.

Will upload enjoyable pacakges sooner or later.
Now I just don't want to care for these peculiarities.


You know what, I am planning to merge ALL the texlive packages
into *ONE* source package of 2.6 Gb, and then ignore all bugs
about size etc. And in addition it will be all arch-dep so that
duplicates the 2.6G for each and every arch, because keeping
these kind of things in tune for 2.6G packages is sisyphus work.

That will make packaging TL much more fun and easy, no breaking
of package, no upgrade path problems, uaaahhh how nice!!!

And there will be also *ONE* binary package, called
texlive
that will install each and everything in one go -- buildds be happy.
Embedded ones be happy. Everyone be happy.


Good night and good luck.

Best wishes

Norbert

Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094

`She hit me on the head with the rock again.'
`I think I can confirm that that was my daughter.'
`Sweet kid.'
`You have to get to know her,' said Arthur.
`She eases up does she?'
but you get a better sense of when to
duck.'
 --- Ford and Arthur on Random.
 --- Douglas Adams, The Hitchhikers Guide to the Galaxy



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

Bug#658230: fping 3.1~rc1-1 available in the git repo (was: Re: Do you need a co-maintainer for fping?)

[Axel Beckert]

Hi,

Axel Beckert wrote:
> I started my work with that today, but unfortunately ran into a bug
> with git-import-dsc(s) triggered by an anomality in
> fping_2.2b1.orig.tar.gz: http://bugs.debian.org/670099
> 
> I'll try to work around #670099 unless it's fixed very quickly.

Done. Importing 2.2b1-1 manually worked, the remainder could be
imported via git-import-dscs plus using debsnap manually,

> The (currently still empty) git repo has been created at
> http://anonscm.debian.org/gitweb/?p=collab-maint/fping.git

The prospective new package is now checked in there. Just cloning that
repo and saying "debuild -uc -us -b" inside should build you a binary
package.

I'll test it for a day or so and then build it in pbuilder and upload
it.

Lintian also found some minor issues man page and spelling issues
which should be tackled upstream. I'll inform David in a separate mail
about the details.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5



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

Bug#670109: texlive-xetex: removal of texlive-xetex makes files disappear from texlive-math-extra

[Andreas Beckmann]

Package: texlive-xetex
Version: 2011.20120410-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and EDOS tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install texlive-math-extra
  # (1)
  apt-get install texlive-xetex
  apt-get remove texlive-xetex
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/doc/texlive-doc/latex/realscripts/README
  /usr/share/doc/texlive-doc/latex/realscripts/realscripts.pdf
  /usr/share/texlive/texmf-dist/tex/latex/realscripts/realscripts.sty

This is a serious bug violating policy 7.6, see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
http://www.debian.org/doc/debian-policy/footnotes.html#f53

The texlive-xetex package has the following relationships with 
texlive-math-extra:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  texlive-math-extra (<= 2011.20120322-1)

>From the attached log (scroll to the bottom...):

1m46.5s INFO: Warning: Package purging left files on system:
  /var/lib/texmf/web2c/xetex/not owned

1m46.5s ERROR: FAIL: After purging files have disappeared:
  /usr/share/doc/texlive-doc/latex/realscripts/READMEowned by: texlive-xetex
  /usr/share/doc/texlive-doc/latex/realscripts/realscripts.pdf   owned by: 
texlive-xetex
  /usr/share/texlive/texmf-dist/tex/latex/realscripts/realscripts.styowned 
by: texlive-xetex

1m46.5s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/texlive-math-extra.list not owned
  /var/lib/texmf/ls-Rnot owned
  /var/lib/texmf/ls-R-TEXLIVEDISTnot owned
  /var/lib/texmf/web2c/fmtutil.cnf   not owned

The modified files are a consequence of the disappeared ones.

cheers,

Andreas


texlive-math-extra=2011.20120322-1_texlive-xetex=2011.20120410-1.log.gz
Description: GNU Zip compressed data

Bug#670108: dose3: formatting errors in manpages

[Jakub Wilk]

Source: dose3
Version: 2.9.15-1
Severity: minor
Tags: patch

The attached patch fixes some formatting errors in the manual pages.

--
Jakub Wilk
--- a/doc/manpages/challenged.pod
+++ b/doc/manpages/challenged.pod
@@ -84,6 +84,7 @@
 Pietro Abate and Roberto Di Cosmo 
 
 =head1 SEE ALSO
+
 L(1)B<>>
 L(1)B<>> 
 
--- a/doc/manpages/buildcheck.pod
+++ b/doc/manpages/buildcheck.pod
@@ -100,6 +100,7 @@
 =cut
 
 =head1 SEE ALSO
+
 L(5)>, 
 L(1)> 
 
--- a/doc/manpages/strongdeps.pod
+++ b/doc/manpages/strongdeps.pod
@@ -99,6 +99,7 @@
 =cut
 
 =head1 SEE ALSO
+
  is the home page of the Mancoosi project. 
 
 For a comprehensive explanation of the notion of strong dependency
--- a/doc/manpages/distcheck.pod
+++ b/doc/manpages/distcheck.pod
@@ -259,6 +259,7 @@
 =cut
 
 =head1 SEE ALSO
+
 L(5)> 
 
  is the home page of the EDOS project. 

Bug#670107: [bts] -m undocumented

[Jakub Wilk]

Package: devscripts
Version: 2.11.6
Severity: minor
Tags: patch
User: devscri...@packages.debian.org
Usertags: bts

-m is an alias for --mbox, but this is not documented in the manual 
page. Patch attached.


--
Jakub Wilk
diff --git a/scripts/bts.pl b/scripts/bts.pl
--- a/scripts/bts.pl
+++ b/scripts/bts.pl
@@ -258,7 +258,7 @@
 Time in seconds to delay between each download, to avoid hammering the BTS
 web server. Default is 5 seconds.
 
-=item B<--mbox>
+=item B<-m>, B<--mbox>
 
 Open a mail reader to read the mbox corresponding to a given bug number
 for B and B commands.

Bug#670040: pax do not work at all

[Norbert Preining]

Dear Heiko, 

(now to the right email adr of Heiko)

we got a bug report in Debian that pax does not work, and the 
reason is that pdfbox is much newer in Debian, namely 1.6.0 from
Apache:

On So, 22 Apr 2012, Hilmar Preusse wrote:
> http://ftp3.gwdg.de/pub/ctan/macros/latex/contrib/pax/README (I'm

Interesting ... pdfbox in Debian is the one from apache
http://pdfbox.apache.org/index.html
while pax uses the one from
pdfbox.org
which is an empty wordpress, and one download. I don't know what the
history of that is, maybe pdfbox was later taken over into apache
and further developped. 

I am quite sure that the pdfbox from pdfbox.org will not be
packaged in Debian.

Heiko, do you see any problem in porting your pax to the recent
pdfbox by apache?

Best wishes

Norbert

Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094

HIBBING (n.)
The marks left on the outside breast pocket of a storekeeper's overall
where he has put away his pen and missed.
--- Douglas Adams, The Meaning of Liff



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

Bug#505205: xchat: "show marker line" not always work as expected

[Gabriele Giacone]

On Thu, Jun 04, 2009 at 04:04:38PM +0200, Sandro Tosi wrote:
> Very often, the line is not there, even in very busy channels (like
> #d-devel), and it will be never shown. Other times (very few) after
> some "time" (undefined, can be very fast after xchat opening, or even
> days after) the marker line is shown.

Not sure this can help you but I couldn't see any marker line at all since many
months, then I just played with its color (Settings - Preferences - Interface -
Color - Interface color - Marker line) and it magically reappeared.



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

Bug#670106: initscripts: please ignore noauto sysfs entries in fstab

[Carsten Hey]

Package: initscripts


Bug summary:

Please ignore noauto sysfs entries in fstab.  Not mounting sysfs to /sys
if such a line is present in fstab leads to udev not starting.

If this bug is not fixed, this problems will show up after upgrading to
Wheezy on some systems.


Bug details:

Gregor Thill noted:
| When bootstrapping Wheezy, the (grml-debootstrap) script creates an
| fstab including a line for sysfs with the mount option noauto. During
| boot of the resulting Debian system, sysfs won't be mounted and as
| udev depends on it, udev does not run. Removing the line or the noauto
| option fixes this behaviour.

Only changing grml-debootstrap to not to create this line, as already
reported in Debian bug #670074, won't solve this problem for all those
pre-Wheezy systems created using "buggy" grml-debootstrap versions.  The
problem will be noticed after an upgrade to Wheezy since
initscripts/Squeeze (or less likely, anything else installed by default
on Squeeze) mounts sysfs despite a noauto sysfs fstab entry.

The line added to /etc/fstab is:
  /sys   /sys   sysfs   noauto,rw,nosuid,nodev,noexec   0   0

I don't think such an entry will only occur on systems installed using
grml-debootstrap, and I think initscripts should be adapted to ignore
a noauto fstab entry for /sys, even if you might consider such and line
to be buggy.

The initscript responsible for mounting sysfs to /sys seems to be
/etc/init.d/mountkernfs.sh, which uses a function in
/lib/init/mount-functions.sh to do so.


Regards
Carsten



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

Bug#670040: pax do not work at all

[Norbert Preining]

Dear Heiko, 

we got a bug report in Debian that pax does not work, and the 
reason is that pdfbox is much newer in Debian, namely 1.6.0 from
Apache:

On So, 22 Apr 2012, Hilmar Preusse wrote:
> http://ftp3.gwdg.de/pub/ctan/macros/latex/contrib/pax/README (I'm

Interesting ... pdfbox in Debian is the one from apache
http://pdfbox.apache.org/index.html
while pax uses the one from
pdfbox.org
which is an empty wordpress, and one download. I don't know what the
history of that is, maybe pdfbox was later taken over into apache
and further developped. 

I am quite sure that the pdfbox from pdfbox.org will not be
packaged in Debian.

Heiko, do you see any problem in porting your pax to the recent
pdfbox by apache?

Best wishes

Norbert

Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094

HIBBING (n.)
The marks left on the outside breast pocket of a storekeeper's overall
where he has put away his pen and missed.
--- Douglas Adams, The Meaning of Liff



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

Bug#670064: RFS: dylandotnet/11.2.9.2-1 [ITP] -- dylandotnet compiler

[Ansgar Burchardt]

tag 670064 + moreinfo
block 626078 with 670064

Dylan Borg  writes:
> dget -x 
> http://mentors.debian.net/debian/pool/main/d/dylandotnet/dylandotnet_11.2.9.2-1.dsc

Half of the comments from [1] still seem to apply to the current
package.  In addition there are many file in the upstream tarball that
should not be there such as backup copies or log files.

Also the following is not a useful changelog entry:

>   dylandotnet (11.2.9.2-1) experimental; urgency=low
>   
> * (Closes:626078)
>   
>-- Dylan Borg   Sun, 21 Apr 2012 18:57:04 +0100

Please take a look at section 6.3 of the developer reference[2].  Please
also read the part about the package description (6.2.1-3).

Is the language the compiler is written for used anywhere?

Regards,
Ansgar

[1] 
[2] 



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

Bug#659083: RFS: xmoto -- 2D motocross platform game

[Stephen Kitt]

tag 659083 - moreinfo
thanks

Hi Ansgar,

It's been ages, but I've finally finished getting everything ready.

On Sun, 26 Feb 2012 15:52:56 +0100, Ansgar Burchardt 
wrote:
> Stephen Kitt  writes:
> >   dget -x
> > http://mentors.debian.net/debian/pool/main/x/xmoto/xmoto_0.5.9-1.dsc
> 
> You do not include the full license text for src/glext.h in the
> copyright information.

I should have noticed that... It was actually not DFSG-free, but it's easy
enough to patch out so I've repacked the upstream tarball without it (and
with the small, necessary patch; I added a README.dfsg file to explain
everything). I filed a bug upstream too.

> Have the patches been forwarded upstream?

They have now, see the updated patch headers for details.

> You use debhelper compat level 9, so why don't you build-depend on
> debhelper (>= 9)?

When I initially switched to compat level 9, debhelper 9 wasn't available
yet. I changed the build-dependency to (>= 9).

> Please update at least config.{guess,sub}, see [1] for details, or just
> use dh-autoreconf (my personal preference).

I like dh-autoreconf too, that's what I went for.

> The source for bin/xmoto.bin seems to be missing, compare with
> upstream's SVN repository[2].  I have filed a bug[3] as it is also
> the case for the version currently inthe archive.  Please ask upstream
> to include the source and ideally built xmoto.bin instead of including
> it, see also [4] for more details.

Indeed; I took the opportunity of repacking the upstream tarball to add the
missing files and remove xmoto.bin. (The resulting build still produces an
identical xmoto.bin.) I also forwarded your bug upstream.

All this (and more) is available in the subversion repository and at
http://mentors.debian.net/debian/pool/main/x/xmoto/xmoto_0.5.9+dfsg-1.dsc

The changelog is as follows:

xmoto (0.5.9+dfsg-1) unstable; urgency=low

  * New upstream release (closes: #644234):
+ builds with libpng 1.5 (closes: #649797);
+ uses libxml2;
+ uses DejaVuSansMono (add link and make ttf-dejavu-core a dependency
  of xmoto-data).
  * Repacked to avoid licensing problems:
+ remove src/glext.h, licensed under SGI License B version 1.1;
+ add the missing contents in bin (closes: #661340).
(I'm hoping that both issues will be fixed upstream, so I haven't
added a get-orig-source target to debian/rules. README.dfsg in the
repacked source explains the changes.)
  * Update debian/watch accordingly.
  * Update patches:
+ fix_segfault.patch: refresh, add DEP-3 header, forward upstream;
+ desktop.patch: re-apply, add German translation (closes: #641822),
  forward upstream;
+ spelling.patch: refresh, forward upstream;
+ manpage.patch: forward upstream;
+ gcc44-ftbfs.patch: no longer used, delete.
  * Switch to dh 9 with simple rules.
  * Use source format "3.0 (quilt)".
  * Add ${misc:Depends} where appropriate.
  * Patch the manpage to fix hyphens and a few spelling mistakes.
  * Add myself to uploaders.
  * Update debian/copyright.
  * Standards-Version 3.9.3 (no further change required).
  * Fix spelling mistakes spotted by Lintian.
  * Use dh-autoreconf to update config.{guess,sub} (thanks to Ansgar
Burchardt for the hint).
  * wrap-and-sort control files.
  * Build-depend on libpng-dev only, dropping the libpng12-dev alternative
(closes: #662565).
  * Fix "ftbfs with GCC-4.7" by including unistd.h where appropriate
(closes: #667422; thanks to Cyril Brulebois for his patch for another
gcc-4.7-related issue, which was already included upstream).
  * Fix the Vcs-Browser URL.

 -- Stephen Kitt   Mon, 23 Apr 2012 00:19:42 +0200

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#670105: libdrmaa-dev and slurm-drmaa-dev: error when trying to install together

[Andreas Beckmann]

Package: libdrmaa-dev,slurm-drmaa-dev
Version: slurm-drmaa-dev/1.0.4-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2012-04-23
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


  Selecting previously unselected package slurm-drmaa-dev.
  Unpacking slurm-drmaa-dev (from .../slurm-drmaa-dev_1.0.4-2_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/slurm-drmaa-dev_1.0.4-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/drmaa.h', which is also in package 
libdrmaa-dev 6.2u5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/slurm-drmaa-dev_1.0.4-2_amd64.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/include/drmaa.h
  usr/lib/libdrmaa.so

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

-Andreas

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


libdrmaa-dev=6.2u5-4_slurm-drmaa-dev=1.0.4-2.log.gz
Description: GNU Zip compressed data

Bug#670104: surfraw: name collision with googlecl package

[Dallas E. Legan]

Package: surfraw
Version: 2.2.8-1
Severity: minor

If you add the surfraw elvi directory to your PATH,
there is a name collision with the 'google' command
from the 'googlecl' package.
Personnally, I've solved this with some aliases,
but maybe there should be some co-ordination between
the package managers to come up with something.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages surfraw depends on:
ii  conkeror [www-browser] 0.9.1-1   keyboard focused web browser with 
ii  edbrowse [www-browser] 3.4.1-1+b1A /bin/ed-alike webbrowser written
ii  elinks [www-browser]   0.12~pre5-7   advanced text-mode WWW browser
ii  iceweasel [www-browser]8.0-3+b1  Web browser based on Firefox
ii  links2 [www-browser]   2.2-1+b1  Web browser running in both graphi
ii  lynx-cur [www-browser] 2.8.8dev.10-1 Text-mode WWW Browser with NLS sup
ii  netrik [www-browser]   1.16.1-1  text mode WWW browser with vi like
ii  w3m [www-browser]  0.5.3-2+b1WWW browsable pager with excellent

Versions of packages surfraw recommends:
ii  curl 7.25.0-1command line tool for transferring
ii  elinks   0.12~pre5-7 advanced text-mode WWW browser
ii  libwww-perl  6.02-1  simple and consistent interface to
ii  surfraw-extra2.2.8-1 extra surfraw search tools with he
ii  w3m  0.5.3-2+b1  WWW browsable pager with excellent
ii  wget 1.13.4-2retrieves files from the web

Versions of packages surfraw suggests:
ii  screen4.0.3-14   terminal multiplexor with VT100/AN

-- 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#670103: googlecl: name collision with the surfraw package

[Dallas E. Legan]

Package: googlecl
Version: 0.9.13-1
Severity: minor

When both surfraw and googlecl are installed,
there can be a name collision of commands
if the surfraw 'elvi' directory is added to a
users PATH directory, both providing a 'google' command.
Personally, I've solved this with some aliases,
but a coordinated solution from the package managers
might be good.
Thanks for any consideration to this minor problem.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages googlecl depends on:
ii  python2.6.7-2interactive high-level object-orie
ii  python-gdata  2.0.8-1.1  Google Data Python client library
ii  python-support1.0.14 automated rebuilding support for P

googlecl recommends no packages.

googlecl suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: missing file /usr/share/doc/googlecl/changelog.Debian.gz (from 
googlecl package)
debsums: missing file /usr/share/doc/googlecl/changelog.gz (from googlecl 
package)



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

Bug#670102: ninja-ide: El recuadro de Preferencias de Ninja-IDE no se despliega correctamente en OpenBox

[Jose Maldonado]

Package: ninja-ide
Version: 2.0~b-2
Severity: normal
Tags: upstream

Probando Ninja IDE en OpenBOX, me he encontrado con este bug, que impide
observar el recuadro de Preferencias de Ninja IDE. He iniciado la aplicación
desde una consola, con lo que se arroja el siguiente traceback:

successfuly initialized (snippets.plugin)
successfuly initialized (ppaste.plugin)
Traceback (most recent call last):
  File "/usr/share/ninja-ide/ninja_ide/gui/menus/menu_edit.py", line 141, in
_show_preferences
pref = preferences.PreferencesWidget(main_container.MainContainer())
  File "/usr/share/ninja-ide/ninja_ide/gui/dialogs/preferences.py", line 66, in
__init__
self._plugins = plugin_preferences.PluginPreferences()
  File "/usr/share/ninja-ide/ninja_ide/gui/misc/plugin_preferences.py", line
22, in __init__
self._load_widgets()
  File "/usr/share/ninja-ide/ninja_ide/gui/misc/plugin_preferences.py", line
27, in _load_widgets
preferences_widget = plugin.get_preferences_widget()
  File "/home/yukiteru/.ninja_ide/addins/plugins/snippets/snippets.py", line
696, in get_preferences_widget
confFrame = SnippetConfigurationFrame(self.snippets)
  File "/home/yukiteru/.ninja_ide/addins/plugins/snippets/snippets.py", line
181, in __init__
self.editor.register_syntax(syntax=constants.SYNTAX)
TypeError: register_syntax() got an unexpected keyword argument 'syntax'



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

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

Versions of packages ninja-ide depends on:
ii  libjs-jquery  1.7.1-1
ii  pyflakes  0.5.0-1
ii  python2.7.2-10
ii  python-qt44.9.1-1

ninja-ide recommends no packages.

ninja-ide 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#659363: Hibernate freezes on HP dc7900 with Linux 3.2 (regression)

[Jonathan Nieder]

Per Olofsson wrote:

> Here is the final patch which fixes the bug:

Thanks, Pelle.  This is e9cbc5a6270b from the linux-next branch of
Rafael's linux-pm tree[1] and should be part of linux-next when
Stephen next rebuilds it.  It applies without change to the 3.2.y
tree, so I'm attaching a patch for the packaging repo that applies the
fix for convenience.

Hope that helps,
Jonathan

[1] git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Index: debian/changelog
===
--- debian/changelog(revision 18944)
+++ debian/changelog(working copy)
@@ -4,6 +4,10 @@
   * [ia64] Fix futex_atomic_cmpxchg_inatomic() (Closes: #659485)
   * rt2x00: Identify rt2800usb chipsets. (Closes: #658067)
 
+  [ Jonathan Nieder ]
+  * PM / Hibernate: fix the number of pages used for hibernate/thaw
+buffering (Closes: #659363)
+
  -- Ben Hutchings   Mon, 16 Apr 2012 02:27:29 +0100
 
 linux-2.6 (3.2.15-1) unstable; urgency=high
Index: 
debian/patches/bugfix/all/PM-Hibernate-fix-the-number-of-pages-used-for-hibern.patch
===
--- 
debian/patches/bugfix/all/PM-Hibernate-fix-the-number-of-pages-used-for-hibern.patch
(revision 0)
+++ 
debian/patches/bugfix/all/PM-Hibernate-fix-the-number-of-pages-used-for-hibern.patch
(working copy)
@@ -0,0 +1,221 @@
+From: Bojan Smojver 
+Date: Sun, 22 Apr 2012 22:32:32 +0200
+Subject: PM / Hibernate: fix the number of pages used for hibernate/thaw 
buffering
+
+commit e9cbc5a6270be7aa9c42d9b15293ba9ac7161262 upstream.
+
+Hibernation/thaw fixes/improvements:
+
+1. Calculate the number of required free pages based on non-high memory
+pages only, because that is where the buffers will come from.
+
+2. Do not allocate memory for buffers from emergency pools, unless
+absolutely required. Do not warn about and do not retry non-essential
+failed allocations.
+
+3. Do not check the amount of free pages left on every single page
+write, but wait until one map is completely populated and then check.
+
+4. Set maximum number of pages for read buffering consistently, instead
+of inadvertently depending on the size of the sector type.
+
+5. Fix copyright line, which I missed when I submitted the hibernation
+threading patch.
+
+6. Dispense with bit shifting arithmetic to improve readability.
+
+Signed-off-by: Bojan Smojver 
+Reviewed-by: Per Olofsson 
+Cc: sta...@vger.kernel.org
+Signed-off-by: Rafael J. Wysocki 
+Signed-off-by: Jonathan Nieder 
+---
+ kernel/power/swap.c |   84 +++
+ 1 file changed, 58 insertions(+), 26 deletions(-)
+
+diff --git a/kernel/power/swap.c b/kernel/power/swap.c
+index 11a594c4ba25..64f8f973674b 100644
+--- a/kernel/power/swap.c
 b/kernel/power/swap.c
+@@ -6,7 +6,7 @@
+  *
+  * Copyright (C) 1998,2001-2005 Pavel Machek 
+  * Copyright (C) 2006 Rafael J. Wysocki 
+- * Copyright (C) 2010 Bojan Smojver 
++ * Copyright (C) 2010-2012 Bojan Smojver 
+  *
+  * This file is released under the GPLv2.
+  *
+@@ -52,6 +52,23 @@
+ 
+ #define MAP_PAGE_ENTRIES  (PAGE_SIZE / sizeof(sector_t) - 1)
+ 
++/*
++ * Number of free pages that are not high.
++ */
++static inline unsigned long low_free_pages(void)
++{
++  return nr_free_pages() - nr_free_highpages();
++}
++
++/*
++ * Number of pages required to be kept free while writing the image. Always
++ * half of all available low pages before the writing starts.
++ */
++static inline unsigned long reqd_free_pages(void)
++{
++  return low_free_pages() / 2;
++}
++
+ struct swap_map_page {
+   sector_t entries[MAP_PAGE_ENTRIES];
+   sector_t next_swap;
+@@ -73,7 +90,7 @@ struct swap_map_handle {
+   sector_t cur_swap;
+   sector_t first_sector;
+   unsigned int k;
+-  unsigned long nr_free_pages, written;
++  unsigned long reqd_free_pages;
+   u32 crc32;
+ };
+ 
+@@ -266,14 +283,17 @@ static int write_page(void *buf, sector_t offset, struct 
bio **bio_chain)
+   return -ENOSPC;
+ 
+   if (bio_chain) {
+-  src = (void *)__get_free_page(__GFP_WAIT | __GFP_HIGH);
++  src = (void *)__get_free_page(__GFP_WAIT | __GFP_NOWARN |
++__GFP_NORETRY);
+   if (src) {
+   copy_page(src, buf);
+   } else {
+   ret = hib_wait_on_bio_chain(bio_chain); /* Free pages */
+   if (ret)
+   return ret;
+-  src = (void *)__get_free_page(__GFP_WAIT | __GFP_HIGH);
++  src = (void *)__get_free_page(__GFP_WAIT |
++__GFP_NOWARN |
++__GFP_NORETRY);
+   if (src) {
+   copy_page(src, buf);
+   } else {
+@@ -317,8 +337,7 @@ static int get_sw

Bug#662432: minetest: diff for NMU version 0.3.1+dfsg-2.1

[gregor herrmann]

On Sun, 22 Apr 2012 17:08:41 -0400, Michael Gilbert wrote:

> Would you mind canceling this upload?  

Sure, I just sent the dcut commands.

> I've uploaded 0.3.1+dfsg-3
> yesterday fixing these issues and may take longer than your delay to
> reach unstable since it entered NEW (it also adds new packages since I
> also fixed another bug which requested a split of the client and
> server packages).

I saw your upload but wasn't sure if you want the NMU as a fallback
or not; now it's clear :)
 

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Hildegard Knef: Tapetenwechsel


signature.asc
Description: Digital signature

Bug#669951: Obsolete conffile /etc/bash_completion.d/systemctl-bash-completion.sh not cleaned up on upgrade

[Josh Triplett]

On Sun, Apr 22, 2012 at 11:41:50PM +0200, Michael Biebl wrote:
> On 22.04.2012 16:42, Josh Triplett wrote:
> > On Sun, Apr 22, 2012 at 04:13:22PM +0200, Michael Biebl wrote:
> >> On 22.04.2012 11:40, Josh Triplett wrote:
> >>> Package: systemd
> >>> Version: 44-1
> >>> Severity: normal
> >>> File: /etc/bash_completion.d/systemctl-bash-completion.sh
> >>>
> >>> dpkg does not automatically remove conffiles on upgrade when a package
> >>> stops shipping them.  systemd needs to clean up the obsolete conffile
> >>> /etc/bash_completion.d/systemctl-bash-completion.sh in its
> >>> maintainer scripts, using dpkg-maintscript-helper.  Please see the
> >>> manpage of dpkg-maintscript-helper for details.
> >>>
> >>
> >> The systemd bash_completion file was renamed/moved and systemd already
> >> uses a dh_installdeb maintscript helper to move the conffile.
> >>
> >> See /var/lib/dpkg/info/systemd.p*
> > 
> > However, I noticed something interesting: the mv_conffile operation in
> > the maintainer scripts uses version 37-1, so it'll only occur on
> > upgrades from that version or before, but 37-1.1 had the same conffile.
> > So, anyone who upgrades from 37-1 to 37-1.1 before upgrading to 43-1 or
> > later will not have the conffile migrated.
> > 
> > I checked the history of systemd on my system via dpkg.log, and sure
> > enough I upgraded to 37-1.1 before upgrading to a later version.
> 
> That's an unpleasant side-effect of the dpkg-maintscript syntax. It uses
> 
>  mv_conffile oldconffile newconffile [priorversion [package]]
> 
> Where priorversion is the last unfixed version.
> 
> When 43-1 was uploaded to experimental, the last unfixed version was
> 37-1. Later on, *after* 43-1 had been uploaded, the version in
> experimental received another update, which broke the versioning
> information in the maintscript file.
> 
> Personally, I would prefer, if dpkg-maintscript would use
> first-fixed-version instead of priorversion (i.e. < instead <=), as you
> know exactly the version when the conffile was (re)moved, but you can't
> be sure about value of priorversion, since this might change (e.g. by a
> binNMU).
> 
> Raphael, what was the reasoning for choosing the current syntax?
> 
> Maybe should have used 43-1~~ instead of 37-1. This is ugly, but it
> would have avoided this particular problem and it even would be
> backport-safe.

Using a ~ seems sensible, though 43-1~~ doesn't quite seem
backport-safe; I think you want 43-~~ , so that a version like
43-0squeeze1 will sort later:

~$ dpkg --compare-versions '43-0squeeze1' '<<' '43-~~' ; echo $?
1
~$ dpkg --compare-versions '43-0squeeze1' '<<' '43-1~~' ; echo $?
0

- Josh Triplett



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

Bug#658230: Do you need a co-maintainer for fping?

[Axel Beckert]

Hi,

Axel Beckert wrote:
> > Please add yourself as co-maintainer and upload a new upstream version
> > of fping.
[...]
> For doing so, I'll create a collab-maint git repository for fping on
> Alioth (unless you object). I think with several potential
> contributors to the package a VCS repo is vital.

I started my work with that today, but unfortunately ran into a bug
with git-import-dsc(s) triggered by an anomality in
fping_2.2b1.orig.tar.gz: http://bugs.debian.org/670099

I'll try to work around #670099 unless it's fixed very quickly.

The (currently still empty) git repo has been created at
http://anonscm.debian.org/gitweb/?p=collab-maint/fping.git

> Since 3.1 is still a release candidate and may need packaging changes
> due due different handling of linux and non-linux arches, I'll first
> start with 3.0 and then base a 3.1[rc] package on that.

David reminded me that while 3.1 could be packaged without the need to
install it setuid on linux-any it's not necessary to do so, so I'll
likely start with 3.1, but without extra work on the linux-only
capabilities stuff (yet).

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5



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

Bug#573719: limit source to python-flickrapi, tagging 573719

[Thomas Schmidt]

Hi,

sorry for the inconvenience, i disabled gitweb a few weeks ago while
searching the reason of some performance issues with my server and
forgot to re-enable it.

The git-daemon itself was also unusable, i guess since i upgraded my
server to Squeeze, because of a wrong base-path.

I just re-enabled gitweb and fixed the configuration of git-daemon, so
you should be able to access the lastest source of the package.


Regards,
Thomas

Am Samstag, den 21.04.2012, 14:29 +0200 schrieb Olivier Berger:
> Hi.
> 
> On Mon, Dec 13, 2010 at 06:14:57PM +0100, Thomas Schmidt wrote:
> > #python-flickrapi (1.4.1-1) experimental; urgency=low
> > #
> > #  * New upstream release (closes: #573719)
> > #
> > 
> > limit source python-flickrapi
> > tags 573719 + pending
> > thanks
> > 
> 
> This version doesn't seem to still be in experimental.
> 
> Also, the git tree where you used to host sources is no longer accessible :-(
> 
> Is there any place one may find your latest version of the package sources ?
> 
> Thanks in advance.
> 
> Best regards,

-- 
Thomas Schmidt, Debian VDR Team
http://pkg-vdr-dvb.alioth.debian.org/


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

Bug#670101: 'bind -e' disables the editline functionality

[Toni Mueller]

Package: libedit2
Version: 2.11-20080614-2
Severity: minor


Hi,

I wanted to explicitly configure emacs-style editing, and put this into
my .editrc:

bind -e

The result is that (at least) tab-completion stopped working. I tried
with "edit on" before and after this statement, but to no avail.

Also, searching needs to be bound specifically, instead of being bound
automatically, as one could expect from trying the 'emacs mode'.


Kind regards,
--Toni++


-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates'), (450, 'testing'), (250, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-openvz-686 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libedit2 depends on:
ii  libbsd0   0.2.0-1utility functions from BSD systems
ii  libc6 2.11.3-2   Embedded GNU C Library: Shared lib
ii  libncurses5   5.7+20100313-5 shared libraries for terminal hand

libedit2 recommends no packages.

libedit2 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#670100: e2fsprogs: Please don't use blocksize of 1024 in usage-type 'small'

[Touko Korpela]

Package: e2fsprogs
Version: 1.42.2-2
Severity: normal

I noticed that mke2fs has a default blocksize of 1024 bytes when it uses
filesystem type 'small' (3-512MB) from mke2fs.conf.
It's a bad thing for performance (more so now when 4K sector HDDs and SDDs
are common). Also space savings are quite small.



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

Bug#662856: pitivi: Same problem here with H264 video

[Richard Scherping]

Package: pitivi
Version: 0.15.0-1
Followup-For: Bug #662856

Dear Maintainer,

I am encountering very similar symptoms (waveform works, but no thumbnails
and stalled rendering) once I add a video from my Canon Ixus 100 camera.
These videos are .MOV with H264 720p30 video and Mono 44.1 kHz PCM audio.

Recoding the audio part and/or remuxing to .MP4 or .AVI (with Avidemux) did
not help. Recoding the video might help, but this should not be necessary
IMHO...

Regards,

Richard

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (101, 'unstable'), (30, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages pitivi depends on:
ii  gnome-icon-theme  3.4.0-2
ii  gstreamer0.10-alsa [gstreamer0.10-audiosink]  0.10.36-1
ii  gstreamer0.10-gconf [gstreamer0.10-videosink] 0.10.31-1+b1
ii  gstreamer0.10-gnonlin 0.10.17-2
ii  gstreamer0.10-plugins-bad [gstreamer0.10-videosink]   0.10.23-1+b1
ii  gstreamer0.10-plugins-base0.10.36-1
ii  gstreamer0.10-plugins-good [gstreamer0.10-videosink]  0.10.31-1+b1
ii  gstreamer0.10-pulseaudio [gstreamer0.10-audiosink]0.10.31-1+b1
ii  gstreamer0.10-x [gstreamer0.10-videosink] 0.10.36-1
ii  libgstreamer-plugins-base0.10-0   0.10.36-1
ii  libgstreamer0.10-00.10.36-1
ii  python2.7.2-10
ii  python-cairo  1.8.8-1+b2
ii  python-central0.6.17
ii  python-dbus   0.84.0-3
ii  python-gconf  2.28.1+dfsg-1
ii  python-glade2 2.24.0-3
ii  python-gst0.100.10.22-3
ii  python-gtk2   2.24.0-3
ii  python-pkg-resources  0.6.24-1
ii  python-pygoocanvas0.14.1-1+b3
ii  python-xdg0.19-4
ii  python-zope.interface 3.6.1-1

Versions of packages pitivi recommends:
ii  python-numpy  1:1.5.1-4

Versions of packages pitivi suggests:
ii  frei0r-plugins  
ii  gstreamer0.10-ffmpeg1:0.10.13-0.2
ii  gstreamer0.10-plugins-bad   0.10.23-1+b1
ii  gstreamer0.10-plugins-ugly  0.10.19-1

-- 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#670047: radeon card no longer detects connected TV

[Jonathan Nieder]

# regression introduced in 3.2.14
severity 670047 important
found 670047 linux-2.6/3.2.14-1
tags 670047 + upstream patch fixed-upstream
quit

Arno Schuring wrote:

> Fix is already queued as e3632507, to be found here:

Thanks, Arno.  The patch has been queued for 3.2.16.



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

Bug#670066: python-openturns is unusable

[D. Barbier]

Le 22 avril 2012 22:11, D. Barbier  a écrit :
> Le 22 avril 2012 20:31, D. Barbier  a écrit :
>> Le 22 avril 2012 20:19, Christophe Prud'homme  a écrit :
>>> Denis
>>>
>>> I received some patches for openturns from J. Schueller.
>>>
>>> I will apply them and upload a new version for 0.15 then work on 1.0
>>
>> Christophe, I already almost finished packaging for 1.0, the only
>> issue is with python.  But I do not know where to push these changes
>> so that you can review them.
>> BTW, we should IMHO change the SONAME, do you have any preference?
>
> Christophe, I just created a git repository to publish my changes:
>  https://github.com/dbarbier/deb-ot
>
> There are instructions at
>  https://github.com/dbarbier/deb-ot/wiki
> to transform it into a git-svn repository.

Hi again,

I do not know why, but it seems that this is due to python extensions
being linked against python2.7 library.  It now works fine in my CMake
build.

Denis



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

Bug#654198: still found

[Sami Liedes]

found 654198 0.29-1
thanks

On Sun, Apr 22, 2012 at 03:32:46PM +0100, Lars Wirzenius wrote:
> close 654198 0.26-1
> thanks
> 
> the corruption when obnam is terminated with control-c should be fixed
> as of version 0.26-1, but I forgot to include the bug in the changelog.

Reopening per IRC discussion. I still get an assertion failure with
obnam+larch 0.29-1 if I interrupt obnam before the first checkpoint
(after 13.10 MiB), then run obnam fsck:


$ obnam fsck
Checking 3/5: B-tree chunklistTraceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 144, in _run
self.process_args(args)
  File "/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 157, in 
process_args
cliapp.Application.process_args(self, args)
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 348, in 
process_args
method(args[1:])
  File "/usr/lib/python2.7/dist-packages/obnamlib/plugins/fsck_plugin.py", line 
293, in fsck
for more in work.do() or []:
  File "/usr/lib/python2.7/dist-packages/obnamlib/plugins/fsck_plugin.py", line 
241, in do
forest = larch.open_forest(dirname=self.dirname, vfs=self.repo.fs)
  File "/usr/lib/python2.7/dist-packages/larch/forest.py", line 181, in 
open_forest
assert 'key_size' in ns_temp.get_metadata_keys()
AssertionError


After finishing the backup by rerunning the same obnam backup command,
obnam fsck seems to be happy.

Sami


signature.asc
Description: Digital signature

Bug#670099: git-buildpackage: git-import-dsc fails if file to patch is read-only in tarball

[Axel Beckert]

Package: git-buildpackage
Version: 0.6.0~git20120415
Severity: normal

Hi,

while I understand the reasoning in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637126 that strange
stuff in upstream tarballs should cause a big warning if it happens
while preparing a new package to upload, it's very annoying if it
happens with "git-import-dscs --debsnap" (reduced to the failed
git-import-dsc call for debugging purposes):

$ git-import-dsc -v /tmp/tmpCyNukV/source-fping/fping_2.2b1-1.dsc
gbp:debug: Upstream version: 2.2b1
gbp:debug: Debian version: 1
gbp:debug: Upstream tarball: /tmp/tmpCyNukV/source-fping/fping_2.2b1.orig.tar.gz
gbp:debug: Debian patch: /tmp/tmpCyNukV/source-fping/fping_2.2b1-1.diff.gz
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/master']
gbp:debug: ['git', 'status']
gbp:debug: tar ['-C', '/home/abe/fping/tmpKIsTeX', '-a', '-xf', 
'/tmp/tmpCyNukV/source-fping/fping_2.2b1.orig.tar.gz'] []
gbp:debug: ['git', 'tag', '-l', 'debian/2.2b1-1']
gbp:debug: ['git', 'tag', '-l', 'debian/2.2b1-1']
gbp:debug: ['git', 'tag', '-l', 'upstream/2.2b1']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'upstream/2.2b1^0']
File fping.c is read-only; refusing to patch
3 out of 3 hunks ignored -- saving rejects to file fping.c.rej
gbp:error: Error import /tmp/tmpCyNukV/source-fping/fping_2.2b1-1.diff.gz: 256
gbp:debug: rm ['-rf', '/home/abe/fping/tmpKIsTeX'] []
$

Reason is that fping.c in the tarball has permissions 444:

-r--r--r-- 1 abe abe 50692 Jan  8  1997 fping.c

But interestingly just git-import-dsc fails because it unpacks the
orig.tar.gz manually with tar while git-import-orig seems to have fixed
this error in some way for the git repo:

-rw-r--r-- 1 abe abe 50692 Apr 22 23:33 fping.c

"dpkg-source -x" works fine on the affected .dsc and fixed the issue,
too:

$ dpkg-source -x /tmp/tmpCyNukV/source-fping/fping_2.2b1-1.dsc
gpgv: Signature made Sat 30 Oct 1999 09:40:42 AM CEST using RSA key ID F9033421
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on 
/tmp/tmpCyNukV/source-fping/fping_2.2b1-1.dsc
dpkg-source: info: extracting fping in fping-2.2b1
dpkg-source: info: unpacking fping_2.2b1.orig.tar.gz
dpkg-source: info: applying fping_2.2b1-1.diff.gz
dpkg-source: info: upstream files that have been modified:
 fping-2.2b1/fping.c
$  ls -l fping-2.2b1/fping.c
-rw-r--r-- 1 abe abe 50761 Apr 22 23:46 fping-2.2b1/fping.c
$

So while I understand the reasoning for the wontfix in #637126, I think
we have a) some inconsistency between git-import-dsc and
git-import-orig/dpkg-source here and b) that git-import-dscs --debsnap
really should accept most strange but doable things it finds in the
snapshot archive.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (900, 'testing'), (600, 'stable'), (200, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.3.0-trunk-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages git-buildpackage depends on:
ii  devscripts   2.11.6
ii  git  1:1.7.10-1
ii  python   2.7.2-10
ii  python-dateutil  1.5-1
ii  python2.72.7.3~rc2-2

Versions of packages git-buildpackage recommends:
ii  cowbuilder
ii  pristine-tar  1.24

Versions of packages git-buildpackage suggests:
ii  python-notify  0.1.1-3
ii  unzip  6.0-6

-- 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#670081: dpkg-source: expected [ +-] at start of line

[Jonathan Nieder]

jaalto wrote:
> On 2012-04-22 21:52, Guillem Jover wrote:

> | but it seems
> | to me those are just somewhat bogus anyway, did you manually create
> | that patch or maybe it was extracted from a mail client that mangles
> | the body (evolution for example)?
>
> It was straight diff from git 1.7.10:
>
>git COMMIT COMMIT -- FILE > output.patch

Are you sure?  Can you send the exact command line and "git config -l |
grep diff" output?

Thanks,
Jonathan



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

Bug#669674: [LCFC] po://debian-history/fr.po

[Filipus Klutiero]

Hi David,

On 2012-04-20 19:21, David Prévot wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Filipus,

Le 20/04/2012 17:55, Filipus Klutiero a écrit :


/usr/share/doc/debian-history/fr/ch-leaders.fr.html contains:


Stefano Zachhiroli a été élu en avril 2010 et est notre chef de projet
actuel.

In "Zachhiroli", "chh" should read "c*c*h".
This problem does not affect the English version.

As already written in #668475: Filipus, please address similar issues
directly to the debian-l10n-french list so we can handle them properly
(package maintainers may not be in the best place to fix them), or at
least X-Debbugs-CC the list.

Since you failed to understand the previous sentence, let me translate
it to you…


It might help me understand English to make sure I read it, say by 
reaching me via the To field of English messages which address me  ;-)
I don't think intervention from translators is required in this specific 
case, but thanks, I will try to remember copying debian-l10n-french in 
future reports about French language issues. You can't expect me to do 
so though, my poor brain is aging very rapidly. Do we have some ticket 
requesting some automated solution for this, perhaps Bugzilla-like 
components?


Filipus, les problèmes de traduction française doivent être signalés
directement à la liste debian-l10n-french. C'est contre-productif
d'ouvrir un rapport de bogue pour des problèmes de traduction qui
peuvent être directement traités par les personnes concernées, c'est à
dire les traducteurs, et que les responsables de paquets ne peuvent
généralement pas corriger eux-mêmes. Par exemple dans ce cas précis,
Steve est en train de finaliser la mise à jour de cette traduction, si
cette simple typo avait été corrigée par le responsables du paquet sans
prévenir le traducteur, elle aurait été écrasée par la mise à jour
imminente.


This shouldn't happen. If it would have, either it's because maintainers 
were supposed to tell translators, or there's something wrong with the 
workflow. An updated version of a file should only overwrite another 
version if the overwriting version is a descendant of the overwritten 
version, or if improvements in the overwritten version were merged in 
the overwriting version.




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

Bug#670081: dpkg: dpkg-source: expected [ +-] at start of line

[jaalto]

On 2012-04-22 21:52, Guillem Jover wrote:
| > dpkg-source: error: expected [ +-] at start of line 14 of diff
| > `bcrypt.git/debian/patches/20-makefile.patch'
| > 
| > Both quilt and plain "patch -p1" accept the file as is without any
| > messages. Files below.
| 
| Hmm, well quilt just makes use of patch. And yes, patch seems to
| assume that when there's a '\t' or '\n' on the first line character
| the space got eaten, in pch.c (another_hunk():1646), so given this I
| guess I'll be adding support for these kinds of patches,

Thanks

| but it seems
| to me those are just somewhat bogus anyway, did you manually create
| that patch or maybe it was extracted from a mail client that mangles
| the body (evolution for example)?

It was straight diff from git 1.7.10:

   git COMMIT COMMIT -- FILE > output.patch

Jari



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

Bug#669951: Obsolete conffile /etc/bash_completion.d/systemctl-bash-completion.sh not cleaned up on upgrade

[Michael Biebl]

On 22.04.2012 16:42, Josh Triplett wrote:
> On Sun, Apr 22, 2012 at 04:13:22PM +0200, Michael Biebl wrote:
>> On 22.04.2012 11:40, Josh Triplett wrote:
>>> Package: systemd
>>> Version: 44-1
>>> Severity: normal
>>> File: /etc/bash_completion.d/systemctl-bash-completion.sh
>>>
>>> dpkg does not automatically remove conffiles on upgrade when a package
>>> stops shipping them.  systemd needs to clean up the obsolete conffile
>>> /etc/bash_completion.d/systemctl-bash-completion.sh in its
>>> maintainer scripts, using dpkg-maintscript-helper.  Please see the
>>> manpage of dpkg-maintscript-helper for details.
>>>
>>
>> The systemd bash_completion file was renamed/moved and systemd already
>> uses a dh_installdeb maintscript helper to move the conffile.
>>
>> See /var/lib/dpkg/info/systemd.p*
> 
> However, I noticed something interesting: the mv_conffile operation in
> the maintainer scripts uses version 37-1, so it'll only occur on
> upgrades from that version or before, but 37-1.1 had the same conffile.
> So, anyone who upgrades from 37-1 to 37-1.1 before upgrading to 43-1 or
> later will not have the conffile migrated.
> 
> I checked the history of systemd on my system via dpkg.log, and sure
> enough I upgraded to 37-1.1 before upgrading to a later version.

That's an unpleasant side-effect of the dpkg-maintscript syntax. It uses

 mv_conffile oldconffile newconffile [priorversion [package]]

Where priorversion is the last unfixed version.

When 43-1 was uploaded to experimental, the last unfixed version was
37-1. Later on, *after* 43-1 had been uploaded, the version in
experimental received another update, which broke the versioning
information in the maintscript file.

Personally, I would prefer, if dpkg-maintscript would use
first-fixed-version instead of priorversion (i.e. < instead <=), as you
know exactly the version when the conffile was (re)moved, but you can't
be sure about value of priorversion, since this might change (e.g. by a
binNMU).

Raphael, what was the reasoning for choosing the current syntax?

Maybe should have used 43-1~~ instead of 37-1. This is ugly, but it
would have avoided this particular problem and it even would be
backport-safe.

Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#654926: manpages-dev: inotify_rm_watch(2) incorrectly lists the type of the second argument

[Michael Kerrisk (man-pages)]

tags 654926 fixed-upstream
thanks

On Sat, Jan 7, 2012 at 10:54 AM, Tom Fogal  wrote:
> Package: manpages-dev
> Version: 3.27-1
> Severity: minor
>
>
> The man page for inotify_rm_watch(2) indicates that the second argument
> should be of type uint32_t.  In /usr/include/sys/inotify.h, the
> argument is listed as being of type integer.
>
> The 'int'eger argument makes more sense anyway, as the argument
> should take what inotify_add_watch(2) returns, and that function
> returns an integer.

This was fixed in upstream 3.29.

Thanks,

Michael


> -- System Information:
> Debian Release: 6.0.3
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'stable')
> 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/bash
>
> Versions of packages manpages-dev depends on:
> ii  manpages                      3.27-1     Manual pages about using a 
> GNU/Lin
>
> manpages-dev recommends no packages.
>
> Versions of packages manpages-dev suggests:
> ii  elvis-console [man-browser]   2.2.0-11.1 powerful clone of the vi/ex text 
> e
> ii  konqueror [man-browser]       4:4.4.5-2  advanced file manager, web 
> browser
> ii  man-db [man-browser]          2.5.7-8    on-line manual pager
>
> -- no debconf information
>
>
>



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/



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

Bug#644379: [checks/files] false-positive package-installs-python-bytecode

[Niels Thykier]

On 2012-04-22 22:19, Nicolas Duboc wrote:
>Hi,
> 

Hi, :)

>  As the maintainer of the jython package, I agree that these three
> files should not be installed.  My next upload of the package will
> remove them and all jython tests, mainly because it will save space.
> 
>  Indeed I think this check is a bit too strict anyway for two reasons:
> 
>   1. These files are actually test data for the Python object file
> parsers of Jython.  I think they are out of scope of the Python
> policy. [...]
> 

Personally, I think that (e.g.) autopkgtest might be a better
alternative than shipping the tests in the binary package.

>  So this check should at least be overridable.
>

The FTP-masters are the authoritative source of overridable tags, we
merely import their lists and mark affected tags accordingly.

>   2. The Python policy section "2.6 Modules Byte-Compilation" reads
>  """If a binary package provides any binary-independent modules (foo.py
>  files), the corresponding byte-compiled modules (foo.pyc files) and
>  optimized modules (foo.pyo files) must not ship in the package."""
> But there is no associated source file (*.py) installed alongside
> these *.pyc files.  So I think they should have been ignored by the
> check.
> 
>  Regards,
> 

By your argument, wouldn't that allow shipping a package where only
".pyo" or/and ".pyc" files are shipped without any .py at all?  If so,
it sounds more like an undesired loop-hole that should be closed to me.
  Anyhow, python is not my strong suit and I can be convinced to update
Lintian if there is a conseus for it.  However, I would like to see the
Python Policy clarify such an exception to its §2.6.

~Niels





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

Bug#669130: April 22: Still not fixed

[Michael Biebl]

On 22.04.2012 22:52, Douglas Mencken wrote:
>> No, you don't
> 
> Of course. So it was not me who reported
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667529 

While the initial bug report was helpful and appreciated, your bitching
about the package not being updated yet, was definitely not helpful.

EOT


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#670093: [Pkg-utopia-maintainers] Bug#670093: policykit-1: console-kit-daemon tries to call CheckAuthorization for org.freedesktop.PolicyKit1.Authority

[Michael Biebl]

On 22.04.2012 22:54, Vincent Bernat wrote:
> Package: policykit-1
> Version: 0.104-2
> Severity: normal
> 
> Dear Maintainer,
> 
> I am still a bit lost with *kit stuff. I am unsure if this bugs is in
> console-kit or in policy-kit. Please, reassign as needed. I have
> assigned the bug to policy-kit because there is nothing in the source
> code of console-kit that call the culprit method. I suppose that
> console-kit relies on a lib provided by policy-kit.
> 
> Here is my error message:
> 
> Apr 22 21:51:39 xbmc dbus-daemon[1008]: dbus[1008]: [system] Rejected send 
> message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=1104 
> comm="/usr/sbin/console-kit-daemon --no-daemon ") 
> interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
> error name="(unset)" requested_reply="0" destination=":1.127" (uid=0 pid=7563 
> comm="/usr/lib/policykit-1/polkitd --no-debug ")
> 
> So, console-kit-daemon running as root tries to invoke some method of
> polkitd running as root. And it is denied. I suppose there is
> something missing in dbus configuration provided by policykit. There
> are authorizations for
> "org.freedesktop.PolicyKit1.AuthenticationAgent" but not for
> "org.freedesktop.PolicyKit1.Authority".
> 

Sounds like an application in your desktop session requested special
(admin) privileges, but you don't have a policykit authentication agent
running in your session.

what kind of desktop are you using?

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#669299: rubber: URL of home page is outdated

[Hilmar Preuße]

On 20.04.12 Emmanuel Beffara (emmanuel.beff...@univ-amu.fr) wrote:
> De Hilmar Preuße le 19/04/2012 à 22:22:

Hi,

> I too would be happy to hand over maintenance to someone actually
> willing to do it, and in fact that is why the code and home page have
> been migrated to launchpad. Sadly there has not been much improvement
> since then...
> 
Well, I could try it. I guess the best way would be to package the
latest snapshot, make the package lintian clean and try to implement
the dh_python -> dh_python2 migration (optional). For the last thing
I'd need some help.

Another question: the Debian package has two patches for upstream
code.

1. fix for #591533 (not in snapshot AFAICS), could you apply it?
2.   Quote file names in rules/latex/__init__.py to stop crashes on
 files with spaces in the file name -> 1.1-2.2
   The patch in the Debian package does not apply any more. Could you
tell me if it is still needed?

> I you feel like contributing to this task, please do!
> 
I'll think about it. I'll open the ITA/RFA bug once I succeeded in
package a new version.

H.
-- 
sigmentation fault



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

Bug#670098: hotot: Does not integrate with notification system

[Alan Collier]

Package: hotot
Version: 1:0.9.7.32+git20111213.1d89daf-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
System installed package normally with no errors reported using
software-center.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Website contained no information. No twitter either.




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

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

Versions of packages hotot depends on:
ii  libjs-jquery  1.7.1-1
ii  python2.7.2-10
ii  python-gobject3.1.0-2
ii  python-gtk2   2.24.0-3
ii  python-keybinder  0.2.2-3
ii  python-notify 0.1.1-3
ii  python-webkit 1.1.8-2

hotot recommends no packages.

hotot 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#662432: minetest: diff for NMU version 0.3.1+dfsg-2.1

[Michael Gilbert]

Hi,

Would you mind canceling this upload?  I've uploaded 0.3.1+dfsg-3
yesterday fixing these issues and may take longer than your delay to
reach unstable since it entered NEW (it also adds new packages since I
also fixed another bug which requested a split of the client and
server packages).

http://ftp-master.debian.org/new/minetest_0.3.1+dfsg-3.html

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#670097: gnome-shell: random hang causes data loss

[Teodor]

Package: gnome-shell
Version: 3.2.2.1-3
Severity: grave
Justification: causes data loss

Hi,

>From time to time the Gnome shell will just freeze/hang and not accept any 
>input
(keyboard or mouse) and all I can do is restart gdm3 or the laptop. Now I'm in
the same situation and the latest changes made in a document I'm writting are
going to be lost as I have no way to save them.

This is the second most annoying thing for me in Debian 7.0 (wheezy). I cannot
tell what causes this, there is nothing in the syslog.
I've attached the current process listing - maybe you can spot something.

Thanks

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

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.10.0-3
ii  gconf-service3.2.3-4
ii  gir1.2-accountsservice-1.0   0.6.15-4
ii  gir1.2-atk-1.0   2.4.0-2
ii  gir1.2-caribou-1.0   0.4.2-2
ii  gir1.2-clutter-1.0   1.8.4-1
ii  gir1.2-cogl-1.0  1.8.2-1
ii  gir1.2-coglpango-1.0 1.8.2-1
ii  gir1.2-folks-0.6 0.6.8-2
ii  gir1.2-freedesktop   1.32.1-1
ii  gir1.2-gconf-2.0 3.2.3-4
ii  gir1.2-gdkpixbuf-2.0 2.26.1-1
ii  gir1.2-gee-1.0   0.6.4-1
ii  gir1.2-gkbd-3.0  3.4.0.2-1
ii  gir1.2-glib-2.0  1.32.1-1
ii  gir1.2-gmenu-3.0 3.2.0.1-2
ii  gir1.2-gnomebluetooth-1.03.2.2-1
ii  gir1.2-gtk-3.0   3.4.1-2
ii  gir1.2-json-1.0  0.14.2-1
ii  gir1.2-mutter-3.03.2.2-1
ii  gir1.2-networkmanager-1.00.9.4.0-3
ii  gir1.2-pango-1.0 1.30.0-1
ii  gir1.2-polkit-1.00.104-2
ii  gir1.2-soup-2.4  2.38.1-2
ii  gir1.2-telepathyglib-0.120.18.1-1
ii  gir1.2-telepathylogger-0.2   0.2.12-1
ii  gir1.2-upowerglib-1.00.9.15-3
ii  gjs  1.30.1-1
ii  gnome-bluetooth  3.2.2-1
ii  gnome-icon-theme-symbolic3.4.0-2
ii  gnome-settings-daemon3.2.2-3
ii  gnome-shell-common   3.2.2.1-3
ii  gsettings-desktop-schemas3.4.1-2
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-30
ii  libcairo-gobject21.10.2-7
ii  libcairo21.10.2-7
ii  libcamel-1.2-29  3.2.2-3
ii  libcanberra0 0.28-4
ii  libclutter-1.0-0 1.8.4-1
ii  libcogl-pango0   1.8.2-1
ii  libcogl5 1.8.2-1
ii  libcroco30.6.5-1
ii  libdbus-1-3  1.5.12-1
ii  libdbus-glib-1-2 0.98-1
ii  libdrm2  2.4.33-1
ii  libebook-1.2-12  3.2.2-3
ii  libecal-1.2-10   3.2.2-3
ii  libedataserver-1.2-153.2.2-3
ii  libedataserverui-3.0-1   3.2.2-3
ii  libffi5  3.0.10-3
ii  libfolks25   0.6.8-2
ii  libfontconfig1   2.8.0-3.1
ii  libfreetype6 2.4.9-1
ii  libgconf-2-4 3.2.3-4
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libgee2  0.6.4-1
ii  libgirepository-1.0-11.32.1-1
ii  libgjs0b [libgjs0-libmozjs185-1.0]   1.30.1-1
ii  libgl1-mesa-glx [libgl1] 7.11.2-1
ii  libglib2.0-0 2.32.0-4
ii  libgnome-desktop-3-2 3.4.1-2
ii  libgnome-keyring03.4.1-1
ii  libgnome-menu-3-03.2.0.1-2
ii  libgstreamer0.10-0   0.10.36-1
ii  libgtk-3-0   3.4.1-2
ii  libical0 0.48-1
ii  libjson-glib-1.0-0   0.14.2-1
ii  libmozjs185-1.0  1.8.5-1.0.0+dfsg-3
ii  libmutter0   3.

Bug#668619: evince-gtk: Crash with segmentation fault

[Torquil Macdonald Sørensen]

Package: evince-gtk
Version: 3.3.90-1
Followup-For: Bug #668619

Thanks! Downgrading libcairo2 fixes both segfaults. I'm wondering
if you also know how long it will be necessary to use the "testing"
version of libcairo2?

Best regards,
Torquil Sørensen

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

Kernel: Linux 3.3.2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages evince-gtk depends on:
ii  evince-common   3.3.90-1
ii  gnome-icon-theme3.4.0-2
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-30
ii  libcairo-gobject2   1.12.0-2
ii  libcairo2   1.10.2-7
ii  libevince3-33.3.90-1
ii  libfontconfig1  2.8.0-3.1
ii  libfreetype62.4.9-1
ii  libgail-3-0 3.4.1-2
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.32.0-4
ii  libgtk-3-0  3.4.1-2
ii  libice6 2:1.0.8-2
ii  libpango1.0-0   1.30.0-1
ii  libsm6  2:1.2.1-2
ii  libx11-62:1.4.99.901-1
ii  libxml2 2.7.8.dfsg-8
ii  shared-mime-info0.90-1
ii  zlib1g  1:1.2.6.dfsg-2

Versions of packages evince-gtk recommends:
ii  dbus-x11  1.5.12-1

Versions of packages evince-gtk suggests:
ii  gvfs  
ii  nautilus  
ii  poppler-data  
ii  unrar 1:4.1.4-1

-- 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#670094: Please hook the halt sequence directly, rather than relying on /etc/init.d/halt

[Josh Triplett]

Package: apcupsd
Severity: normal

Currently, /etc/init.d/halt contains the following:

# See if we need to cut the power.
if [ "$INIT_HALT" = "POWEROFF" ] && [ -x /etc/init.d/ups-monitor ]
then
/etc/init.d/ups-monitor poweroff
fi

Rather than requiring a special case in /etc/init.d/halt, please have
/etc/init.d/ups-monitor hook into the shutdown sequence directly and run
right before /etc/init.d/halt.  That would allow /etc/init.d/halt to
drop this special case.

Thanks,
Josh Triplett

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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



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

Bug#669949: sysvinit: Break X11: no more mouse and keyboard

[Eric Valette]

On 22/04/2012 19:49, Roger Leigh wrote:

On Sun, Apr 22, 2012 at 05:04:28PM +0200, Eric Valette wrote:

On 22/04/2012 12:57, Roger Leigh wrote:


Does this alter the behaviour at all?

probably not as from what I read the /tmp fs will be correctly
mounted afterward.

I'm not sure that this is definitely a sysvinit issue.  The mouse
and keyboard are entirely functional right up until X11 starts up.
I've tested this in single user mode, running the init scripts by
hand.  It's all working perfectly up until kdm/gdm starts, and it
can be triggered by hand with xinit.

I'm sure it is beause reverting *only* sysvinit (and all related 
packages) makes the problem vanish.


--eric



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

Bug#669130: April 22: Still not fixed

[Douglas Mencken]

> No, you don't

Of course. So it was not me who reported
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667529 being
absolutely ignorant. It was not me who reported
https://bugzilla.gnome.org/show_bug.cgi?id=674220
Yes, that's me who don't care, not you, Debian maintainers. Sorry. I
love to kiss your feet, your Magistry.



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

Bug#670093: policykit-1: console-kit-daemon tries to call CheckAuthorization for org.freedesktop.PolicyKit1.Authority

[Vincent Bernat]

Package: policykit-1
Version: 0.104-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

I am still a bit lost with *kit stuff. I am unsure if this bugs is in
console-kit or in policy-kit. Please, reassign as needed. I have
assigned the bug to policy-kit because there is nothing in the source
code of console-kit that call the culprit method. I suppose that
console-kit relies on a lib provided by policy-kit.

Here is my error message:

Apr 22 21:51:39 xbmc dbus-daemon[1008]: dbus[1008]: [system] Rejected send 
message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=1104 
comm="/usr/sbin/console-kit-daemon --no-daemon ") 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
error name="(unset)" requested_reply="0" destination=":1.127" (uid=0 pid=7563 
comm="/usr/lib/policykit-1/polkitd --no-debug ")

So, console-kit-daemon running as root tries to invoke some method of
polkitd running as root. And it is denied. I suppose there is
something missing in dbus configuration provided by policykit. There
are authorizations for
"org.freedesktop.PolicyKit1.AuthenticationAgent" but not for
"org.freedesktop.PolicyKit1.Authority".

- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages policykit-1 depends on:
ii  consolekit 0.4.5-3
ii  dbus   1.5.12-1
ii  libc6  2.13-30
ii  libexpat1  2.1.0-1
ii  libglib2.0-0   2.32.0-4
ii  libpam0g   1.1.3-7
ii  libpolkit-agent-1-00.104-2
ii  libpolkit-backend-1-0  0.104-2
ii  libpolkit-gobject-1-0  0.104-2

policykit-1 recommends no packages.

policykit-1 suggests no packages.

- -- no debconf information

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

iEYEARECAAYFAk+Ub/QACgkQKFvXofIqeU4bngCfcpRIGGy6YCkLJ2w/v5u95+It
9i8AoIPrzTuX+VWSot+av4Fq4vb01OFZ
=vMlg
-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#585642: Occuring on my machine as well

[Brian Paterni]

Hi

I seem to be experiencing the same problem here as well. X seems not
able to detect my input devices since nothing is being logged in Xorg
log. Also as Cyril pointed out, my devices are missing ID_INPUT
attributes as well.

My xserver-xorg-corg script output follows. Let me know if I can provide
more info.

X server symlink status:

lrwxrwxrwx 1 root root 13 Apr  9 19:13 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2056560 Mar  4 17:44 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI 
RV770 [Radeon HD 4850] [1002:9442]

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1356 Apr 22 10:16 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg
Section "ServerLayout"
Identifier  "Layout0"
Screen  "Screen0"
EndSection

#Section "Files"
##  ModulePath  "/usr/local/lib/xorg/modules"
#   ModulePath  "/usr/lib/xorg/modules/"
#EndSection

Section "ServerFlags"
Option  "DefaultServerLayout"   "Layout0"
Option  "DontZap"   "off"
Option  "DRI2"  "on"
EndSection

Section "Device"
Identifier  "ATI Radeon HD 4850"
Driver  "radeon"
Option  "Monitor-DVI-0" "dvi-0"
Option  "Monitor-DVI-1" "dvi-1"
EndSection

Section "Screen"
Identifier  "Screen0"
Monitor "dvi-0"
Device  "ATI Radeon HD 4850"
SubSection "Display"
Virtual 4096 4096
EndSubSection
EndSection

Section "Monitor"
Identifier  "dvi-0"
EndSection
Section "Monitor"
Identifier  "dvi-1"
Option  "RightOf"   "dvi-0"
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/radeon-kms.conf:
  #options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.3.0-trunk-amd64 (Debian 3.3.2-1~experimental.1) 
(debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP 
Mon Apr 16 01:06:59 UTC 2012

Xorg X server log files on system:
--
-rw-r--r-- 1 root root  6428 Feb 25  2011 /var/log/Xorg.3.log
-rw-r--r-- 1 root root 44211 Oct 20  2011 /var/log/Xorg.12.log
-rw-r--r-- 1 root root 42164 Dec 15 09:15 /var/log/Xorg.1exit.log
-rw-r--r-- 1 root root 46268 Apr 21 08:47 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 38047 Apr 22 09:00 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 38253 Apr 22 15:09 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  1686.999] 
X.Org X Server 1.11.4
Release Date: 2012-01-27
[  1687.002] X Protocol Version 11, Revision 0
[  1687.003] Build Operating System: Linux 3.2.0-1-amd64 x86_64 Debian
[  1687.005] Current Operating System: Linux robocomp 3.3.0-trunk-amd64 #1 SMP 
Mon Apr 16 01:06:59 UTC 2012 x86_64
[  1687.006] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.3.0-trunk-amd64 
root=UUID=4f6d38d8-8e1c-4a9e-a932-c5014ec2f75f ro
[  1687.007] Build Date: 04 March 2012  11:42:13PM
[  1687.009] xorg-server 2:1.11.4-1 (Cyril Brulebois ) 
[  1687.010] Current version of pixman: 0.25.2
[  1687.011]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1687.014] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1687.017] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 22 15:08:49 
2012
[  1687.018] (==) Using config file: "/etc/X11/xorg.conf"
[  1687.019] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1687.021] (**) Option "defaultserverlayout" "Layout0"
[  1687.021] (**) ServerLayout "Layout0"
[  1687.021] (**) |-->Screen "Screen0" (0)
[  1687.021] (**) |   |-->Monitor "dvi-0"
[  1687.021] (**) |   |-->Device "ATI Radeon HD 4850"
[  1687.021] (**) Option "DontZap" "off"
[  1687.021] (**) Option "DRI2" "on"
[  1687.021] (==) Automatical

Bug#670074: grml-debootstrap: please remove the noauto sysfs entry from, generated/copied fstab

[Gregor Thill]

Thanks to Carsten for filing this bug in my name and leading me to 
commit this patch.


This patch solves the problem of udev not loading in a freshly 
bootstrapped Wheezy because of a not mounted /sys. Debian Lenny and 
Squeeze aren't influenced in a negative way as both of them mount /sys 
automatically, even if there is no entry in /etc/fstab.


Regards
Gregor
>From 833e8e64d55de1c13f0b81ce15dd6c0ba99c9f0b Mon Sep 17 00:00:00 2001
From: Gregor Thill 
Date: Sun, 22 Apr 2012 21:35:31 +0200
Subject: [PATCH] Remove the sysfs noauto entry from the installed fstab. This
 entry causes udev not to be loaded on current Debian
 Wheezy. Closes: #67007

---
 chroot-script |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/chroot-script b/chroot-script
index 4f10c54..2512b95 100755
--- a/chroot-script
+++ b/chroot-script
@@ -362,7 +362,6 @@ fi
 
 cat >> /etc/fstab << EOF
 proc   /procprocdefaults  0   0
-/sys   /sys sysfs   noauto,rw,nosuid,nodev,noexec 0   0
 /dev/cdrom /mnt/cdrom0  iso9660 ro,user,noauto0   0
 # some other examples:
 # /dev/sda2   none swapsw,pri=0 0   0
-- 
1.7.9

Bug#670085: insserv: update-rc.d is a dangling symlink

[Eddy Petrișor]

On 22.04.2012 23:03, Eddy Petrișor wrote:

On 22.04.2012 22:58, Eddy Petrișor wrote:

Subject: insserv: update-rc.d is a dangling symlink
Package: insserv
Version: 1.14.0-3


I forgot to add this info:

heidi:/home/eddy# ls -l /usr/sbin/update-rc*
lrwxrwxrwx 1 root root 29 Sep 22 2009 /usr/sbin/update-rc.d ->
/usr/sbin/update-rc.d-insserv
-rwxr-xr-x 1 root root 16894 Mar 13 09:14 /usr/sbin/update-rc.d.distrib
heidi:/home/eddy# dpkg -S /usr/sbin/update-rc.d.distrib
diversion by insserv from: /usr/sbin/update-rc.d
diversion by insserv to: /usr/sbin/update-rc.d.distrib



After trying to reinstall sysv-rc and insserv a few times to no avail, I 
looked into sysv-rc's postinst and suspected the problem was that the 
divert will be removed if only /var/run/sysv-rc.upgrade existed, so I 
manually ran these commands


dpkg-divert --package insserv --remove /usr/sbin/update-rc.d

mv /usr/sbin/update-rc.d{.distrib,}

and later reinstalled sysv-rc. I seem to have fixed the problem on my 
system.


--
Regards,
EddyP
=
"Imagination is more important than knowledge" A.Einstein




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

Bug#666350: mpg321: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.

[Lucas Nussbaum]

On 21/04/12 at 13:21 +0300, Nanakos Chrysostomos wrote:
> Dear Lucas,
> bug fixed and package re-uploaded [0]. I would be gratefull if you 
> could sponsor the package.

Sorry, I don't have time for that. Please ask -mentors@.

Lucas



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

Bug#669935: Debian Installer does apply keymap used during installation to resulting initramfs

[Sebastian Pipping]

Thanks for that explanation.


For that keyboard hook to do its work, KEYMAP=y needs to be set in the
initramfs configuration (see the code of the hook itself).

What can be done to set KEYMAP=y in a controlled manner from within the
installer?  The currently resulting KEYMAP=n does not work.

Thanks,



Sebastian



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

Bug#670092: Please warn about any reference to /lib/init in init.d scripts

[Josh Triplett]

Package: lintian
Version: 2.5.6
Severity: normal

/lib/init/rw has gone away, and the scripts in /lib/init/*.sh represent
internal implementation details of initscripts, *not* public API for
other packages to use.  Nonetheless, some packages incorrectly reference
those scripts, notably /lib/init/vars.sh.  Please consider adding a
warning for any reference to /lib/init in an init.d script.

Thanks,
Josh Triplett

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages lintian depends on:
ii  binutils   2.22-6
ii  bzip2  1.0.6-1
ii  diffstat   1.55-2
ii  file   5.11-1
ii  gettext0.18.1.1-5
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.26+b1
ii  libc-bin   2.13-30
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.31-1+b2
ii  libdpkg-perl   1.16.2
ii  libemail-valid-perl0.190-1
ii  libipc-run-perl0.91-1
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtimedate-perl   1.2000-1
ii  liburi-perl1.60-1
ii  man-db 2.6.1-2
ii  patchutils 0.3.2-1.1
ii  perl [libdigest-sha-perl]  5.14.2-9
ii  unzip  6.0-6

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch 
ii  dpkg-dev   1.16.2
ii  libhtml-parser-perl3.69-2
ii  libtext-template-perl  1.45-2
ii  man-db 2.6.1-2
ii  xz-utils   5.1.1alpha+20110809-3

-- 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#670091: Please ship /sys

[Josh Triplett]

Package: base-files
Version: 6.7
Severity: normal

Currently, only the initscripts package ships the empty /sys directory,
which made sense since initscripts contains the script to mount /sys.
However, new init systems don't necessarily need to depend on
initscripts, and systemd has almost reached the point where it no longer
needs to do so.  I think it would make sense for base-files to ship
/sys, just as it currently ships many other top-level directories.

- Josh Triplett

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.0.1+dfsg-1

base-files recommends no packages.

base-files 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#670090: Please ship the /sys directory

[Josh Triplett]

Package: systemd
Version: 44-1
Severity: normal

Currently, only initscripts ships the /sys directory.  However, systemd
mounts /sys itself without relying on initscripts to do so, and systemd
has almost reached the point where it won't need to depend on
initscripts anymore.  In preparation for that, please ship the /sys
directory in systemd, to ensure that it exists as a mountpoint.

Thanks,
Josh Triplett

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages systemd depends on:
ii  dpkg 1.16.2
ii  initscripts  2.88dsf-22.1
ii  libacl1  2.2.51-5
ii  libaudit01:1.7.18-1.1
ii  libc62.13-30
ii  libcap2  1:2.22-1
ii  libcryptsetup4   2:1.4.1-3
ii  libdbus-1-3  1.5.12-1
ii  libkmod2 6-2
ii  liblzma5 5.1.1alpha+20110809-3
ii  libpam0g 1.1.3-7
ii  libselinux1  2.1.9-4
ii  libsystemd-daemon0   44-1
ii  libsystemd-id128-0   44-1
ii  libsystemd-journal0  44-1
ii  libsystemd-login044-1
ii  libudev0 175-3.1
ii  libwrap0 7.6.q-23
ii  udev 175-3.1
ii  util-linux   2.20.1-4

Versions of packages systemd recommends:
pn  libpam-systemd  

Versions of packages systemd suggests:
pn  python   2.7.2-10
pn  systemd-gui  

-- Configuration Files:
/etc/bash_completion.d/systemctl-bash-completion.sh [Errno 2] No such file or 
directory: u'/etc/bash_completion.d/systemctl-bash-completion.sh'

-- 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#668562: XeLaTeX fails to work if babel/french is used

[Hilmar Preuße]

On 19.04.12 Hilmar Preuße (hill...@web.de) wrote:

> Many thanks for analysis!
> 
Just a remark: we should check if #666569 and #666578 still occur if
this problem is solved.

H.
-- 
sigmentation fault



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

Bug#669593: Your bug report

[Tom Reynolds]

Hi Alberto,

On 22.04.2012 16:57 malpen...@gmail.com wrote:
> I have installed the current Debian testing version, with three desktop
> enviroment that are the following: xFce4, Gnome Classic and Gnome3.
> After to configure all I have downloaded the lastest stable version of the
> Megaglest game from their web site. The Megaglest version is the
> following: 3.6.0.3.

so you downloaded (and are reporting about) the upstream version of
MegaGlest, not the Debian package? If this is so, please report any
upstream MegaGlest bugs at http://bugs.megaglest.org (one-time
registration is required).

For a more detailed list of information that is useful in determining
what the problem is, please have a look at this (upstream) forum post
which is dedicated to the topic of effective bug reporting:
http://glest.org/glest_board/?topic=5332.0

> I have tested the game in all desktops and it works fine in all minus
> in Gnome3. In that desktop the screen, after exit the game, plays crazy,
> it behaves like flashing lights, at one time I can see the desktop at
> other time not.
> 
> I must say that I had experienced the same result a year ago, in that
> time I had tried Fedora 15, while I wanted to see how Gnome3 works. And I
> gave him the blame that it was to early for that desktop. I also must 
> say that this installation was in another Laptop, not my current Laptop.
> But now that the problem persists I think is a problem of Gnome3.

When you say you "experienced the same result" of the screen "[playing]
crazy" testing with Gnome 3 on Fedora 15 and on Debian Wheezy, are you
saying that this happened after using MegaGlest 3.6.0.3 on both
platforms? I.e. were you really running MegaGlest 3.6.0.3 on Fedora 15?
Or a different version of MegaGlest, or yet another application which
triggered the same or similar behaviour?

> I am ready to help and give more info about the problem, if you tell
> me how to do this, in particular which error files I must look for.

I'll try to sum up the information you have provided so far, please
verify it is correct or provide corrections as needed:

* You are experiencing an issue on your Debian Wheezy installation on
your current laptop which you describe as the "screen [playing] crazy"
as soon as you exit MegaGlest.

* You state that this issue occurs with Gnome 3 but not with XFCE 4 and
Gnome 2.

* You state that this (or a similar) issue affected your earlier Fedora
Core 15 installation (also running Gnome 3) on a different laptop.

* It is unclear whether this behavior is only triggered by MegaGlest or
can be triggered by other OpenGL based applications, too.

* It is unclear which, if any, versions of MegaGlest was triggering this
behavior on Fedora Core 15, and whether that was a Fedora package or an
upstream installer.

* It is unclear which hardware your current laptop (running Debian
Wheezy) and your earlier laptop (running Fedora Core 15) are/were using.



A better description of "the screen [..] plays crazy" may be helpful.

Surely more information on the (mostly video) hardware on both systems
can be of interest here, as well as taking a look at ~/.xsession-errors*
and /var/log/Xorg* at the time when the screen started to "[play] crazy".

Please also read http://www.debian.org/Bugs/Reporting - especially the
section titled "The body of the report".

Most likely the issue you are reporting is one of the following:
* A bug in a compositing window manager such as Mutter/Compiz
* A bug in your video drivers
* A hardware or firmware issue (video or memory are most likely candidates)

Based on the (few) additional details you have provided this issue is
probably not caused by the "megaglest" package in Debian GNU/Linux
Wheezy. Please try to reproduce this issue using other complex OpenGL
applications to confirm. If you can, please reassign your bug to the
proper package as explained at
http://www.debian.org/Bugs/Developer#requestserv
If you cannot reproduce this issue with any other OpenGL software, are
convinced it is a Megaglest bug, but are actually reporting an issue
with the upstream version of MegaGlest, please report this issue
upstream instead and close this bug report (or ask for it to be closed)
'unreproducible':
http://www.debian.org/Bugs/Developer#closing

Thanks,

Tom



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

Bug#644379: [checks/files] false-positive package-installs-python-bytecode

[Nicolas Duboc]

   Hi,

 As the maintainer of the jython package, I agree that these three
files should not be installed.  My next upload of the package will
remove them and all jython tests, mainly because it will save space.

 Indeed I think this check is a bit too strict anyway for two reasons:

  1. These files are actually test data for the Python object file
parsers of Jython.  I think they are out of scope of the Python
policy.  So this check should at least be overridable.

  2. The Python policy section "2.6 Modules Byte-Compilation" reads
 """If a binary package provides any binary-independent modules (foo.py
 files), the corresponding byte-compiled modules (foo.pyc files) and
 optimized modules (foo.pyo files) must not ship in the package."""
But there is no associated source file (*.py) installed alongside
these *.pyc files.  So I think they should have been ignored by the
check.

 Regards,

-- 
Nicolas Duboc 


signature.asc
Description: Digital signature

Bug#670089: kolab-cyrus-common: fails to upgrade from squeeze: missing dependency on db4.7-util, db5.1-util

[Andreas Beckmann]

Package: kolab-cyrus-common
Version: 2.2.13p1-0.4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

  Setting up kolab-cyrus-common (2.2.13p1-0.4) ...
  Installing new version of config file /etc/init.d/kolab-cyrus ...
  Creating/updating cyrus user account...
  The user `cyrus' is already a member of `sasl'.
  /usr/sbin/cyrus-upgrade-db: db4.7-util not installed
  /usr/sbin/cyrus-upgrade-db: please do: [sudo] apt-get install db4.7-util 
package
  /usr/sbin/cyrus-upgrade-db: and rerun the upgrade again
  /usr/sbin/cyrus-upgrade-db: db5.1-util not installed
  /usr/sbin/cyrus-upgrade-db: please do: [sudo] apt-get install db5.1-util 
package
  /usr/sbin/cyrus-upgrade-db: and rerun the upgrade again
  dpkg: error processing kolab-cyrus-common (--configure):
   subprocess installed post-installation script returned error exit status 2
  configured to not write apport reports
  Errors were encountered while processing:
   kolab-cyrus-common

Please follow the approach taken by the regular cyrus packages that have
added these dependencies.

cheers,

Andreas


kolab-cyrus-common_2.2.13p1-0.4.log.gz
Description: GNU Zip compressed data

Bug#670088: [wxmaxima] hel/build info menu suppresses its output

[Mate Miklos]

Package: wxmaxima
Version: 12.01.0-1
Severity: normal

--- Please enter the report below this line. ---
Selecting help/build info enters 'build_info()$' into the worksheet, which 
gives no output.

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.3.1fxa

Debian Release: wheezy/sid
  500 unstableftp.uni-kl.de 
  500 unstableftp.de.debian.org 
1 experimentalftp.hu.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-==
libc6 (>= 2.2.5) | 2.13-30
libgcc1 (>= 1:4.1.1) | 1:4.7.0-3
libstdc++6(>= 4.1.1) | 4.7.0-3
libwxbase2.8-0 (>= 2.8.12.1) | 2.8.12.1-7
libwxgtk2.8-0  (>= 2.8.12.1) | 2.8.12.1-7
maxima (>= 5.18) | 5.27.0-2
maxima-doc   (>= 5.10.0) | 5.27.0-2


Recommends(Version) | Installed
===-+-===
ttf-jsmath  | 0.090709+0-1
libgnomeprintui2.2-0| 2.18.6-3


Package's Suggests field is empty.



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

Bug#669658: Acknowledgement ([plasma-desktop] plasma-desktop segfaults when Notebook wakes up from suspend-to-ram)

[Karsten Kruse]

kde-workspace-dbg is installed, now i wait for the problem to return.

MFG,

Karsten Kruse

-- 

  ()
 <\/>
 _/\_   Do we live and fight for power and not justice?



signature.asc
Description: OpenPGP digital signature

Bug#670087: [PATCH] mailcheck: Helping to update to packaging format 3.0

[jari . aalto]

Package: mailcheck
Severity: wishlist
Tags: patch

Hi,

The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:

http://wiki.debian.org/Projects/DebSrc3.0

I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.

Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.

Thanks,
Jari

>From 6bea36a55118137050b9b89f47814feee1f70d7a Mon Sep 17 00:00:00 2001
From: Jari Aalto 
Date: Sun, 22 Apr 2012 23:16:03 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Signed-off-by: Jari Aalto 
---
 debian/changelog   |   14 +
 debian/compat  |2 +-
 debian/control |9 
 debian/copyright   |   11 +-
 .../{001_username.dpatch => 001-username.patch}|   16 ++
 ...counting.dpatch => 002-advanced-counting.patch} |9 +++-
 ..._no_stripping.dpatch => 003-no-stripping.patch} |7 ++-
 debian/patches/00list  |3 ---
 debian/patches/series  |3 +++
 debian/rules   |   22 +++-
 debian/source/format   |1 +
 11 files changed, 47 insertions(+), 50 deletions(-)
 rename debian/patches/{001_username.dpatch => 001-username.patch} (68%)
 rename debian/patches/{002_advanced_counting.dpatch => 002-advanced-counting.patch} (99%)
 rename debian/patches/{003_no_stripping.dpatch => 003-no-stripping.patch} (72%)
 delete mode 100644 debian/patches/00list
 create mode 100644 debian/patches/series
 create mode 100644 debian/source/format

diff --git a/debian/changelog b/debian/changelog
index 4582914..33d46e2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+mailcheck (1.91.2-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+  * Update to Standards-Version to 3.9.3 and debhelper to 9.
+  * Add build-arch and build-indep targets; use dh_prep in rules file.
+  * Fix copyright-refers-to-symlink-license (Lintian).
+  * Fix no-upstream-changelog (Lintian).
+  * Fix copyright-with-old-dh-make-debian-copyright (Lintian).
+  * Fix description-contains-homepage (Lintian)
+  
+
+ -- Jari Aalto   Sun, 22 Apr 2012 23:13:03 +0300
+
 mailcheck (1.91.2-2) unstable; urgency=low
 
   * Added advanced_counting patch from Tomas Hoger .
diff --git a/debian/compat b/debian/compat
index 7ed6ff8..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-5
+9
diff --git a/debian/control b/debian/control
index dc6ce6f..b4aa0f9 100644
--- a/debian/control
+++ b/debian/control
@@ -2,16 +2,15 @@ Source: mailcheck
 Section: mail
 Priority: extra
 Maintainer: Kevin Coyner 
-Build-Depends: debhelper (>= 5.0), dpatch
-Standards-Version: 3.7.2
+Build-Depends: debhelper (>= 9)
+Standards-Version: 3.9.3
+Homepage: http://mailcheck.sourceforge.net
 
 Package: mailcheck
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Check multiple mailboxes/maildirs for mail
+Description: check multiple mailboxes/maildirs for mail
  Mailcheck is a simple, configurable tool that allows multiple mailboxes
  to be checked for the existence of new mail messages.  It supports both
  mbox and maildir-style mailboxes for compatibility with most mail
  transport agents.  It also supports remote POP3 and IMAP mailboxes.
- .
-  Homepage: http://mailcheck.sourceforge.net/
diff --git a/debian/copyright b/debian/copyright
index 1a44811..edcc99f 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -28,7 +28,7 @@ License (except netrc.h, netrc.c, and socket.c):
 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
 
 On Debian systems, the complete text of the GNU General Public License
-can be found in /usr/share/common-licenses/GPL file.
+can be found in /usr/share/common-licenses/GPL-2 file.
 
 License (netrc.c):
 
@@ -49,7 +49,7 @@ License (netrc.c):
 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
 
 On Debian systems, the complete text of the GNU General Public License
-can be found in /usr/share/common-licenses/GPL file.
+can be found in /usr/share/common-licenses/GPL-2 file.
 
 License (netrc.h):
 
@@ -71,7 +71,7 @@ License (netrc.h):
 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
 
 On Debian systems, the complete text of the GNU General Public License
-can be found in /usr/share/common-licenses/GPL file.
+can be found 

Bug#670066: python-openturns is unusable

[D. Barbier]

Le 22 avril 2012 20:31, D. Barbier  a écrit :
> Le 22 avril 2012 20:19, Christophe Prud'homme  a écrit :
>> Denis
>>
>> I received some patches for openturns from J. Schueller.
>>
>> I will apply them and upload a new version for 0.15 then work on 1.0
>
> Christophe, I already almost finished packaging for 1.0, the only
> issue is with python.  But I do not know where to push these changes
> so that you can review them.
> BTW, we should IMHO change the SONAME, do you have any preference?

Christophe, I just created a git repository to publish my changes:
  https://github.com/dbarbier/deb-ot

There are instructions at
  https://github.com/dbarbier/deb-ot/wiki
to transform it into a git-svn repository.

Denis



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

Bug#669130: April 22: Still not fixed

[Michael Biebl]

On 22.04.2012 22:09, Douglas Mencken wrote:

> I'm just trying to help.

No, you don't

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#669130: April 22: Still not fixed

[Douglas Mencken]

> This bug has been filed just a few days ago?

Can you follow the bug? ``Michel Dänzer [reporter] 2012-04-03 07:29:45
UT'' (~20 days ago)
Can you follow it has been fixed in upstream?
(https://bugzilla.gnome.org/show_bug.cgi?id=673409#c17)
No, I don't think it would speed up anything. But I have a working one
from upstream's svn. And you do not. (You do test only on x86, do you?
hehehe)
I'm just trying to help.



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