How many sarge packages are still in non-us? These are mainly crypto
and patented packages, arent't they? We should try to get as many into
main as possible.
Andrew Donnellan
On 5/19/05, Frans Pop [EMAIL PROTECTED] wrote:
Prompted by Jeroen van Wolffelaar I propose to include the following
I wouldn't call this important, as it's not a critical package or
anything. I would make it a normal or even minor severity bug.
Andrew Donnellan
On 5/21/05, Jereme Corrado [EMAIL PROTECTED] wrote:
Please consider faqomatic_2.721-6 for inclusion in sarge, in lieu of
2.721-4, which is currently
Please, allow the following package uploaded to t-p-u, as requested to
circunvent newer version uploaded to unstable.
Thanks,
- Mensaje reenviado
De: Debian Installer [EMAIL PROTECTED]
Para: Jose Carlos Garcia Sogo [EMAIL PROTECTED], Debian VoIP Team
[EMAIL PROTECTED]
The check shown below is almost complete (but for a couple of 2.2 patches
and per-arch patches).
I'm asking if mass bug report filing is opportune at this stage.
IMHO patches which cannot be applied to debian kernel-sources are almost
unuseful and should be removed from sarge...
- Forwarded
I have just submitted a serious bug against the elinks package.
(310035) It is to do with the fact that there is nonfree code in it,
the same code that was in prozilla. I'd like to know if any of the
release team can send DJ Bernstein (the code's author; author of
qmail) an official Debian team
[martin f krafft [EMAIL PROTECTED] - 22:07PM Friday May 20]:
Fluxbox just got an RC bug which caused me to elevate the
severity of another to merge the two: #308052, #309958
Sorry guys to cause this concern, but I don't feel that the bug Bas
has reported justifies a sarge-rc bug. The version
tags 308052 = sid confirmed
tags 309958 = sid confirmed
thanks
The fluxbox problem resolved itself, and it turns out that I was
overcomplicating stuff and getting confused. I apologise for the
noise and making my confusion be other people's problems.
It turns out that the two RC bugs #308052 and
tags 308052 sid
thanks
On Sat, May 21, 2005 at 07:17:38PM +1000, matt hope wrote:
[martin f krafft [EMAIL PROTECTED] - 22:07PM Friday May 20]:
Fluxbox just got an RC bug which caused me to elevate the
severity of another to merge the two: #308052, #309958
Sorry guys to cause this concern,
also sprach matt hope [EMAIL PROTECTED] [2005.05.21.1149 +0200]:
This has, however, highlighted a related (but different) problem -
bsetbg diverts should be cleaned up.
After some IRC discussion in #debian-bugs (that I wasn't privy to, so
I cannot quote here) Steve (vorlon) and Martin
ocamlgsl 0.3.5-3 has just been uploaded and fix a grave bug (#309844)
by a very small change. Could you allow it into sarge ?
source package is ocamlgsl, and binary packages are
libocamlgsl-ocaml-dev and libocamlgsl-ocaml.
Thannks
[matt hope [EMAIL PROTECTED] - 19:17PM Saturday May 21]:
Sorry guys to cause this concern, but I don't feel that the bug Bas
has reported justifies a sarge-rc bug. The version that he reported it
against, 0.9.12-1, is not a candate for the sarge release. 0.9.11-1 is
a candidate, however it
On Thu, May 19, 2005 at 05:26:50PM +0200, Alexis Sukrieh wrote:
* Joey Hess ([EMAIL PROTECTED]) disait :
Note this this hole has been assigned two CVE IDs:
CAN-2005-1564 post_bug.cgi in Bugzilla 2.10 through 2.18, 2.19.1, and
2.19.2 allows
CAN-2005-1563 Bugzilla 2.10 through 2.18,
On Sat, May 21, 2005 at 06:13:01PM +1000, Andrew Donnellan wrote:
I have just submitted a serious bug against the elinks package.
(310035) It is to do with the fact that there is nonfree code in it,
the same code that was in prozilla. I'd like to know if any of the
release team can send DJ
On Sat, May 21, 2005 at 11:15:11AM +0200, Remi Vanicat wrote:
ocamlgsl 0.3.5-3 has just been uploaded and fix a grave bug (#309844)
by a very small change. Could you allow it into sarge ?
source package is ocamlgsl, and binary packages are
libocamlgsl-ocaml-dev and libocamlgsl-ocaml.
Yep,
diff -urNp whois-4.7.4/debian/changelog whois-4.7.5/debian/changelog
--- whois-4.7.4/debian/changelog2005-04-29 00:55:58.0 +0200
+++ whois-4.7.5/debian/changelog2005-05-18 16:03:10.0 +0200
@@ -1,3 +1,10 @@
+whois (4.7.5) unstable; urgency=high
+
+ * Updated the .in
Hi Miguel,
Format: 1.7
Date: Thu, 19 May 2005 13:22:54 +0200
Source: libmatheval
Binary: libmatheval1 libmatheval1-dev
Architecture: source i386
Version: 1.1.2-2
Distribution: unstable
Urgency: high
Maintainer: Miguel Gea Milvaques [EMAIL PROTECTED]
Changed-By: Miguel Gea Milvaques
On Fri, May 20, 2005 at 10:07:48AM +0200, Sjoerd Simons wrote:
On Thu, May 19, 2005 at 10:09:00PM -0700, Steve Langasek wrote:
Hi Sjoerd,
On Thu, May 19, 2005 at 12:20:13AM +0200, Sjoerd Simons wrote:
Just uploaded hal 0.4.7-3sarge1 to testing-proposed-updates. This removes
the sync
On Fri, May 20, 2005 at 04:35:51PM +0400, Alexey Nezhdanov wrote:
20 2005 13:42 Steve Langasek
(a):
On Thu, May 19, 2005 at 05:23:41PM +0400, Alexey Nezhdanov wrote:
17 2005 19:05 Steve
Langasek (a):
Hi Alexey,
Hello Steve.
According to your recomendation normal
Hi,
On Fri, May 20, 2005 at 04:17:20AM +0200, Adeodato Simó wrote:
Since yesterday evening, the Kopete version in sarge is no longer able
to log into MSN Messenger accounts due to (it seems) an update in the
Microsoft servers.
Bug #309745 arrived to the Debian BTS this morning making
On Fri, May 20, 2005 at 08:59:21AM +0400, Alexey Nezhdanov wrote:
I'm sorry to bug you but you have not give neither ack nor nack reply
yet,
but as I can see, you are replying to more recent mails already. Probably my
mail was just lost, so I'm re-posting.
Since the package was not in
Hi Filippo,
On Fri, May 20, 2005 at 08:52:09AM +0200, Filippo Giunchedi wrote:
Hi,
I've uploaded autossh 1.2g-2 which fixes an important and annoying bug, the
two small changes are trivial and one is backported from autossh 1.3, here is
the relevant changelog:
autossh (1.2g-2) unstable;
Hi Roberto,
On Fri, May 20, 2005 at 03:11:31AM -0400, Roberto C. Sanchez wrote:
I have been checking out the RFA'd and O'd package lists.
I saw that multi-gnome-terminal [0] is on the RFA list. I
am wondering if it would not be better to simply remove it
from Debian. Here is why I think it
Hi
Ive just uploaded 1.0-8 of package dak.
It fixes a bunch of bugs, including 3 translations.
It also changes uma a bit to use gpg --with-colon, to not break with
newer gnupg thats on its way to sarge.
The last change is a modification to jennifer, to remove a today unused
function (which will
On Sat, May 21, 2005 at 06:28:03AM -0700, Steve Langasek wrote:
Hi,
On Fri, May 20, 2005 at 04:17:20AM +0200, Adeodato Simó wrote:
Since yesterday evening, the Kopete version in sarge is no longer able
to log into MSN Messenger accounts due to (it seems) an update in the
Microsoft
Hi everyone,
Just two sets of translation fixes requiring pushing. Please reset the
urgency on gnome-cpufreq-applet to medium if you feel it won't make it
into to testing in time for Sarge's release.
gnome-cpufreq-applet (0.3.1-6) unstable; urgency=low
* Czech Debconf template translation.
On Saturday 21 May 2005 09:13, Andrew Donnellan wrote:
How many sarge packages are still in non-us? These are mainly crypto
and patented packages, arent't they? We should try to get as many into
main as possible.
Currently 29 in non-us/main and 2 in non-us/non-free.
In main:
erlang,
On Sat, May 21, 2005 at 06:55:09PM +0200, Frans Pop wrote:
On Saturday 21 May 2005 09:13, Andrew Donnellan wrote:
How many sarge packages are still in non-us? These are mainly crypto
and patented packages, arent't they? We should try to get as many into
main as possible.
Currently 29 in
reassign 310088 docbook-xsl
severity 310088 grave
thanks
On Saturday 21 May 2005 21:09, you wrote:
reassign 310088 debian-installer-manual
severity 310088 normal
thanks
Reassigning right back to you and setting to grave again.
Please discuss this issue first _before_ arbitrarily reassigning.
On Fri, May 20, 2005 at 01:12:39PM +0100, Dafydd Harries wrote:
I've just uploaded Alexandria to unstable, including translation-only
changes. One of these changes fixes a format string which causes
Alexandria to crash for Japanese users. (#303714)
Approved.
Thanks,
--
Steve Langasek
Steve Langasek wrote:
If the maintainer agrees that this package should not be included with
sarge, then it is of course reasonable to drop it (preferably with a
transition package providing an upgrade path to gnome-terminal, if that's
the appropriate replacement).
It depends on the year, when
Hello Steve
On 2005-05-19 Steve Langasek wrote:
Thus BDB support could now complete been removed as luckily support for
BDB was not present on most architectures, disabled by default and
being warned at startup for a while now and will most likely be removed in
5.0 upstream anyway.
I
Please remove cantus3, RoM
--Jeroen
- Forwarded message from Igor Stroh [EMAIL PROTECTED] -
Subject: Bug#309854: RM: cantus3 -- RoM; no longer maintained upstream
Reply-To: Igor Stroh [EMAIL PROTECTED], [EMAIL PROTECTED]
Resent-From: Igor Stroh [EMAIL PROTECTED]
Date: Fri, 20 May 2005
Hi,
I've just uploaded binutils 2.15-6 to unstable. This fixes #308625,
an RC security bug. The only change from 2.15-5 (in testing and
unstable) is:
* 123_bfd_overflow_fix.dpatch: new patch from Alan Modra to fix BFD
overflows. Closes: #308625
The patch was applied to upstream
lør, 21,.05.2005 kl. 12.13 -0700, skrev Steve Langasek:
Hi Ove, Guus,
It looks like there are four versions of gmime in testing currently (gmime,
gmime1, gmime2, gmime2.1), only one of which is actually used by any other
packages. Is there any reason not to remove gmime{,1,2} from testing
Roberto C. Sanchez wrote:
Torsten Werner wrote:
It depends on the year, when sarge will be released. :-) Too many people
are still using MGT today because of some of its outstanding features
that are not implemented in gnome2's terminal emulator. I will MGT for
sarge and ask for removal from
On Wed, May 18, 2005 at 07:18:36PM +0200, Frans Pop wrote:
Prompted by Jeroen van Wolffelaar I propose to include the following
text in the Release Notes to make users aware that non-us is being
phased out.
*non-us being phased out*
For the sarge release most cryptographic packages that
Hi,
Andreas Barth wrote:
* Rene Engelhard ([EMAIL PROTECTED]) [050522 00:16]:
I just uploaded muttprint 0.72d-1. It's a new upstream release but only
contains the change to a new upstream maintainer and some documentation
spelling fixes. and it fixes the important #309892 which should not
On Sun, May 22, 2005 at 09:23:11AM +1000, Andrew Donnellan wrote:
The latest sarge elinks still has the code
Which is exactly what I have said...
On 5/21/05, Frank Lichtenheld [EMAIL PROTECTED] wrote:
Shouldn't this have been fixed by 0.10.4-1? This would leave the issue
open for sarge
On Wed, May 18, 2005 at 05:33:01PM -0400, sean finney wrote:
On Wed, May 18, 2005 at 11:00:29PM +0200, Adrian Bunk wrote:
...
Other issues like #308762 are also still possible on direct
mysql-server/woody - mysql-server-4.1/sarge upgrade paths - and
there will be users doing such upgrade
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
...
I see the same three options. Joey has said he is working on a final woody
point release for the last weekend in May; you'll probably need to
coordinate with him and get something uploaded soon if you want to try for
this
On Thu, May 19, 2005 at 08:35:03AM -0700, Steve Langasek wrote:
On Thu, May 19, 2005 at 05:08:28PM +0200, GOMBAS Gabor wrote:
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
3 does not sound so bad to me; it's arguably user error anyway to replace
a
package-provided
On Sunday 22 May 2005 01:23, you wrote:
Minus the typo you're already aware of, and s/non-us/non-US/: yeah,
looks fine. Sarge will definitely have no packages in non-US, and at a
certain moment the apt-get sources lines for non-US *may* start to give
errors (or may not, and just be empty).
If
On Sat, May 21, 2005 at 10:04:02AM +0200, Francesco Paolo Lovergine wrote:
The check shown below is almost complete (but for a couple of 2.2 patches
and per-arch patches).
I'm asking if mass bug report filing is opportune at this stage.
IMHO patches which cannot be applied to debian
On Sat, May 21, 2005 at 06:24:50PM -0400, Roberto C. Sanchez wrote:
Adrian Bunk wrote:
Repairing this issue by simply renaming the non-free package back to
unrar and giving the free program a different name should be pretty
straightforward and doable for sarge.
Package unrar
*
On Sun, May 22, 2005 at 12:01:58AM +0200, Adrian Bunk wrote:
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
...
I see the same three options. Joey has said he is working on a final woody
point release for the last weekend in May; you'll probably need to
coordinate with
On Sun, May 22, 2005 at 02:01:09AM +1000, Andrew Lau wrote:
Hi everyone,
Just two sets of translation fixes requiring pushing. Please reset the
urgency on gnome-cpufreq-applet to medium if you feel it won't make it
into to testing in time for Sarge's release.
...
tsclient (0.132-7)
Andrew Donnellan wrote:
I wouldn't call this important, as it's not a critical package or
anything. I would make it a normal or even minor severity bug.
It's very important if you run multiple FOM's. :) I think the
severity of the bug is appropriate.
No, it's not a critical package, most
Steve Langasek wrote:
On Sun, May 22, 2005 at 12:15:20AM +0200, Luigi Gangitano wrote:
Hi all,
I need help solving a licence issue with sarg. Tonight I found that sarg
upstream sources contain a font file that may not be free (Verdana.TTF).
I've contacted upstream a few minutes ago. In the
On Fri, May 20, 2005 at 12:09:09PM -0400, Eric Dorland wrote:
Alright, after a false start with 1.0.4-1, -2 has finished building on
m68k and is ready for inclusion in testing. 1.0.4 is security
fix release, no new features.
Approved.
Thanks,
--
Steve Langasek
postmodern programmer
49 matches
Mail list logo
