[I'm having problems getting this through to the debian-release list;
resending through a different route. Apologies for any duplicates.]
On Mon, Aug 18, 2008 at 03:17:57PM +0300, Niko Tyni wrote:
On Sun, Aug 17, 2008 at 11:38:10PM +0100, Adeodato Simó wrote:
* Niko Tyni [Tue, 05 Aug 2008
Please allow gnucash 2.2.6-2 into testing; this has a minimally invasive
patch to avoid a dangerous data-loss bug in an unusual usage case.
(It turns out that sshfs returns ENOSYS on a link call. This is wildly
wrong; it has no business doing so, especially when EPERM is already the
documented
The -2 upload has only a couple of tiny changes for manpages:
proj (4.6.0-2) unstable; urgency=low
* proj.3 link moved in the right directory.
[ Note: I'm also co-maintainer and sponsor of initial packager of
python-django ]
On Thu, 28 Aug 2008, Steve Langasek wrote:
- Django 0.96.2 is already too far out of date for most applications (i.e.,
it's been too old for the past 6 months), and has been in
security-updates-only mode for
Please consider inclusion of dictionaries-common_0.98.12 into lenny
Is already more than 20 days in unstable and contains two changes:
* Korean debconf stuff update (closes: #491517)
* Documentation change in flyspell.el version doctring (through the
relevant patch) to make it more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Aug 26, 2008 at 10:33:00PM +0200, maximilian attems wrote:
On Mon, 25 Aug 2008, Jonas Smedegaard wrote:
+1021_new-style_firewire.patch
etch+half kernel has old ieee1394, no need for that one.
Thanks for your concern, Max.
I will wait for
Dear debian-release team,
Xorp in lenny and sid is at version 1.5~cvs.20080519-1, this version is
not however, a final release and has bugs that have been fixed in the
1.5 release which was released a few months later (22nd of July) but we were
not able to package+upload it in time for the
On Sun, Aug 24, 2008 at 9:16 PM, Luk Claes [EMAIL PROTECTED] wrote:
Martin-Éric Racine wrote:
Greetings,
A user reported a small packaging mistake that somewhat hampers
utilization of two of my dictionary packages:
ispell-et
rus-ispell
The mistake is that Hash-Name should use the syntax
Hello Release Team,
Could jhbuild but removed from testing ? It is too outdated to be
useful.
fredp lool: mind if I ask for jhbuild to be removed from testing?
lool fredp: That makes sense IMO
Thanks,
Frederic
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
http://incoming.debian.org/ggz-server_0.0.14.1-1.1_amd64.changes
closing 478812 (merged with 473350) and 490420:
debian/patches/database-m4.patch comes from upstream (isolated to only
fix the current problem), see:
http://hq.ggzgamingzone.org/~josef/diffs/0.0.14.1/
(package already uses the
http://incoming.debian.org/mailreader_2.3.36-3.1_amd64.changes
Closes: 484322
Interdiff:
diff -u mailreader-2.3.36/debian/postinst mailreader-2.3.36/debian/postinst
--- mailreader-2.3.36/debian/postinst
+++ mailreader-2.3.36/debian/postinst
@@ -1,4 +1,4 @@
-#! /bin/sh -e
+#! /bin/sh
#
Hey Luk,
Ok, please upload.
Okay, I've uploaded today, please unblock.
Greetings
Winnie
signature.asc
Description: This is a digitally signed message part.
On Tue, Jul 29, 2008 at 01:43:14AM +0100, Samuel Thibault wrote:
Hello,
Just to give an update on the status: I'm currently able to compile a
working loadlin.exe from source thanks to a patch against yasm 0.5. I
need to port that to 0.7 and submit upstream (actually it should be
easier for
On Fri, Aug 29, 2008 at 06:00:39PM +0100, Samuel Thibault wrote:
Robert Millan, le Fri 29 Aug 2008 18:46:23 +0200, a écrit :
On Tue, Jul 29, 2008 at 01:43:14AM +0100, Samuel Thibault wrote:
One sad piece of news is that I wasn't able to contact upstream again:
[EMAIL PROTECTED] doesn't
Robert Millan, le Fri 29 Aug 2008 18:46:23 +0200, a écrit :
On Tue, Jul 29, 2008 at 01:43:14AM +0100, Samuel Thibault wrote:
One sad piece of news is that I wasn't able to contact upstream again:
[EMAIL PROTECTED] doesn't work any more. However, if people confirm
that he has been lost in
Robert Millan, le Fri 29 Aug 2008 19:14:28 +0200, a écrit :
I don't know how intrusive is your patch, but if upstream is not responsive,
Oops, sorry, I meant loadlin upstream.
Samuel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Hi,
udns has the recent DNS problem in a pretty bad way (i.e. no random, not
even query IDs vs. not enough). And there is no indication that anyone
is working on getting it solved at the moment. (Last upstream release is
Jan 2007, the upstream mailing list archives have 2007 no activity
since
Hi,
Please could you unblock quesoglc 0.7.1-3 which has just been uploaded to
unstable and fixes the RC bug #496324.
Regards,
Bradley Smith
Debdiff:
diff -u quesoglc-0.7.1/debian/control quesoglc-0.7.1/debian/control
--- quesoglc-0.7.1/debian/control
+++ quesoglc-0.7.1/debian/control
@@ -25,7
I know it is the release team's policy not to allow new upstreams
during the freeze, but I'm hoping an exception can be made for ucarp.
The current version in testing is a snapshot and very little changed
between it and the official release. Backporting the changes necessary
to fix #496625
Hello Manoj,
Have you had a chance to look at this issue?
On Fri, Aug 15, 2008 at 5:19 AM, Manoj Srivastava [EMAIL PROTECTED] wrote:
Hi,
I'll be happy to look at this, but I am on a business trip after
debconf, and I will not be back home until the 25th of this month. And
since
* Matthias Klose:
Well, you know that there is a T2000 available and if the security team
needs a faster buildd they have to ask.
the estimate is wrong.
I what sense? I quoted the actual build time on lebrun. Is spontini
really faster than that?
the openjdk-6 package runs the testsuite.
Hi,
wbxml2_0.9.2-5 fixes #487217. Although filed only at important
severity, we have seen several users who were totally unable to use
libsyncml with their mobile, but where it worked fine for them after
upgrading to wbxml2_0.9.2-5. The patch was written by the libsyncml
upstream author;
On Fri, Aug 29, 2008 at 08:46:00PM +0200, Thomas Viehmann wrote:
Hi,
udns has the recent DNS problem in a pretty bad way (i.e. no random, not
even query IDs vs. not enough). And there is no indication that anyone
is working on getting it solved at the moment. (Last upstream release is
Jan
23 matches
Mail list logo
