On Sun, May 22, 2005 at 06:27:57PM +0200, Adeodato Simó wrote:
> please allow mutt 1.5.9-2 into sarge, it fixes an RC bug (FTBFS) and
> contains a translation update.
> Changelog entry follows, thanks.
> mutt (1.5.9-2) unstable; urgency=high
> * Added a missing Build-Depend on ma
Matthias Klose <[EMAIL PROTECTED]> writes:
> * Append the GCC version to the fastjar/grepjar version string.
> Closes: #296567.
This is a severity: minor bug.
> * On powerpc, configure using --enable-targets to build a biarch compiler.
> Disabled by default.
> * Fixed java build fo
Aurelien Jarno wrote:
> > It sounds ok to upload, but I make no promises about it getting in before
> > seeing the code. :)
>
> I have just uploaded a new version to testing-proposed-update. Please
> find the changes between the current version in Sarge and this new one
> below.
Oops, I probably
Hi Mattia,
On Sun, May 22, 2005 at 06:16:15PM +0200, Mattia Dongili wrote:
> On Mon, May 16, 2005 at 11:54:54PM +0200, Frank Lichtenheld wrote:
> > On Sun, May 15, 2005 at 07:08:26PM +0200, Mattia Dongili wrote:
> > > I uploaded a new upstream (oh well, upstream is me) of cpufreqd. It
> > > fixes
On Sun, May 22, 2005 at 02:08:48PM +0200, Alexander Sack wrote:
> > The question is, how can we be proactive about identifying the classes of
> > changes that do or don't break these packages, so that mozilla can be
> > checked for compatibility at the time of upload instead of having kazehakase
>
On Mon, May 23, 2005 at 01:39:55AM +0200, Matthias Klose wrote:
> Not sure, if that's RC, at least it enables one specific ISDN card to
> work with capi4hylafax. I am unable to test this card myself. The bug
> fix has been confirmed by another user.
> capi4hylafax (1:01.02.03-11) unstable; urgency
Not sure, if that's RC, at least it enables one specific ISDN card to
work with capi4hylafax. I am unable to test this card myself. The bug
fix has been confirmed by another user.
capi4hylafax (1:01.02.03-11) unstable; urgency=medium
* Patch fixing c4h for Eicon cards (Sergio Chersovani):
-
the last architecture did build 3.4.3-13 ten days before, no new
problems were reported.
gcc-3.4 (3.4.3-13) unstable; urgency=medium
* Don't call dh_shlibdeps on 64bit libraries (closes: #307625).
same fix as for gcc-3.3, may or may not be relevant on an updated
buildd.
* Append the GCC ver
On Mon, May 23, 2005 at 01:22:46AM +0200, Matthias Klose wrote:
> * Rename icu-doc to icu21-doc. icu-doc is built by the icu28 package
> as well.
> patch at #310127.
Approved.
Thanks,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
* src/translator_ca.h: Revert accidental conversion to unicode.
Patch by Maximiliano Pin (closes: #309913).
the patch can be found in the bug report. The encoding was correct in
1.4.1 and is corrected in 1.4.3. Although one source file is affected,
the changes are limited to the message stri
* Rename icu-doc to icu21-doc. icu-doc is built by the icu28 package
as well.
patch at #310127.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Steve Langasek writes:
> Hi Matthias,
>
> On Sat, May 14, 2005 at 10:52:23PM +0200, Matthias Klose wrote:
> Content-Description: message body text
> > I'm proposing the following updates for gcc-3.3 for testing:
>
> > gcc-3.3 (1:3.3.5-13) testing-proposed-updates; urgency=low
>
> > * Disable r
Reviewing this for sarge because of the security fixes..
Bdale Garbee wrote:
>* remove PAGER reference from zmore.1, closes: #263792
--- gzip-1.3.5.orig/zmore.1
+++ gzip-1.3.5/zmore.1
@@ -33,9 +33,6 @@
On a terminal capable of displaying 24 lines,
the default window size is 22 lines.
To us
On Mon, May 23, 2005 at 01:42:30AM +0200, Luigi Gangitano wrote:
> I need to upload a new orig.tar.gz and don't know how to do that for
> sarge.
You will need to upload a fixed package to testing-proposed-updates
since the version in unstable differs from the one in testing.
Which part do you don
Il giorno sab, 21/05/2005 alle 21.12 -0700, Steve Langasek ha scritto:
> 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.T
On Tue, May 10, 2005 at 01:00:53AM -0700, Steve Langasek wrote:
> On Tue, May 10, 2005 at 09:27:52AM +0200, Frederic Peters wrote:
> > Adalbert Dawid wrote:
> > > Package: libgphoto2-2
> > > Version: 2.1.5-5.0
> > > Followup-For: Bug #308290
>
> > > Indeed, after installing the three debs everythi
Hi,
I uploaded a new revision of somaplayer which fixes #309093 (RC) and
#297963 (FTBFS on amd64).
I simply sponsored this upload, the actual work was done by the
maintainer, Riccardo Setti <[EMAIL PROTECTED]>. Please CC: him on
replies.
Thanks.
ciao,
ema
--
To UNSUBSCRIBE, email t
On Sat, May 21, 2005 at 09:27:42PM +0100, James Troup wrote:
> 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
> ove
Hey Lawrence,
On Sat, May 21, 2005 at 10:02:26AM -0400, Lawrence Walton wrote:
>* New upstream release
> This package is necessary to sync up with evolution 2.0.4,
> Evolution and evolution-exchange should match up, and the 2.0.4
> package fixes many bugs.
> Closes #299504
>
This release fixes #309937, an important bug that *might* be on the
borderline of grave (there's some user data loss, or at least something
that could be taken that way). I *fully* understand if you feel this is
just too late for this sort of fix; alas, it was only found on Friday.
I thought I'd
On Sat, May 21, 2005 at 09:08:34PM +0200, Christian Hammers wrote:
> 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 n
On Sun, May 22, 2005 at 09:51:47AM -0700, Steve Langasek wrote:
> Release team,
>
> Please review zaptel 1:1.0.7-4.1 for sarge.
Approved
Gruesse,
--
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
On Sun, May 22, 2005 at 12:35:59AM +0200, Adrian Bunk wrote:
> 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
On Sun, May 22, 2005 at 12:40:26AM -0700, Steve Langasek wrote:
> 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
> Format: 1.7
> Date: Sun, 22 May 2005 13:57:06 -0400
> Source: fltk1.1
> Binary: fltk1.1-doc
> Architecture: source all
> Version: 1.1.6-5
> Distribution: unstable
> Urgency: medium
> Maintainer: Aaron M. Ucko <[EMAIL PROTECTED]>
> Changed-By: Aaron M. Ucko <[EMAIL PROTECTED]>
> Description:
> f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
#310151 (fltk1.1 build bug) has now been fixed, and it's now
autobuilding correctly. Please could you approve this for sarge.
Thanks,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
On Sun, May 22, 2005 at 07:20:52PM +0200, Samuel Mimram wrote:
> Steve Langasek wrote:
> >On Sun, May 22, 2005 at 05:09:58PM +0200, Samuel Mimram wrote:
> >>I've just made an NMU for gkrellm to close the RC-bug #309089. I've only
> >>added a patch to make gkrellm use gnutls instead of (GPL-incomp
Hi,
On Sun, May 22, 2005, Steve Langasek wrote:
> The question is, how can we be proactive about identifying the classes of
> changes that do or don't break these packages, so that mozilla can be
> checked for compatibility at the time of upload instead of having kazehakase
> and enigmail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
Rene Engelhard wrote:
> Frank Lichtenheld wrote:
> > On Sun, May 22, 2005 at 01:26:46AM +0200, Rene Engelhard wrote:
> > > > Also, I couldn't locate the place where the upstream maintainer changed,
> > > > nor the place where MAINT_SEARCH wa
Steve Langasek wrote:
On Sun, May 22, 2005 at 05:09:58PM +0200, Samuel Mimram wrote:
I've just made an NMU for gkrellm to close the RC-bug #309089. I've only
added a patch to make gkrellm use gnutls instead of (GPL-incompatible)
openssl.
I've been able to get my mail count (it's the only use o
I'm the (previous) maintainer of unrar. Jose Carlos Medeiros has offered to
adopt it.
On Sun, May 22, 2005 at 02:36:50PM +0200, Jeroen van Wolffelaar wrote:
> On Sun, May 22, 2005 at 12:41:11AM +0200, Adrian Bunk wrote:
> > - rename the unrar-nonfree package back to unrar
> > - rename the free unn
Hi Chad,
On Sat, May 21, 2005 at 02:01:06PM -0500, Chad Walstrom wrote:
> tags 309648 pending patch sarge
> thanks
> Kenshi Muto <[EMAIL PROTECTED]> submitted a patch he pulled from
> cheetah's CVS upstream repository that fixes this security hole. This
> is an RC bug against sarge's version of
søn, 22,.05.2005 kl. 00.10 -0700, skrev Steve Langasek:
> Having four versions of gmime in a stable release means a four-fold increase
> in the security team's workload if a security bug is found. (This is true
> even if the bug only applies to one version, because the security team still
> has to
On Mon, May 16, 2005 at 11:54:54PM +0200, Frank Lichtenheld wrote:
> On Sun, May 15, 2005 at 07:08:26PM +0200, Mattia Dongili wrote:
> > I uploaded a new upstream (oh well, upstream is me) of cpufreqd. It
> > fixes 3 memomry leaks and a segfault, changes are really trivial (diff
> > is included bel
On Sat, May 21, 2005 at 05:53:26PM +0200, Pierre HABOUZIT wrote:
> On Sat, May 21, 2005 at 06:28:03AM -0700, Steve Langasek wrote:
> > 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 MS
On Sun, May 22, 2005 at 05:09:58PM +0200, Samuel Mimram wrote:
> I've just made an NMU for gkrellm to close the RC-bug #309089. I've only
> added a patch to make gkrellm use gnutls instead of (GPL-incompatible)
> openssl.
> I've been able to get my mail count (it's the only use of ssl in
> gkrel
On Sun, May 22, 2005 at 05:26:35PM +0100, Roger Leigh wrote:
>
> Both RC bugs in clearsilver have been fixed in NMUs (#310073 and
> #310231). I can't judge whether the package as a whole is
> release-worthy (I don't use it, but there are other non-RC bugs), but
> the RC issues are fixed at least.
Release team,
Please review zaptel 1:1.0.7-4.1 for sarge.
Thanks,
--
Steve Langasek
postmodern programmer
- Forwarded message from Steve Langasek <[EMAIL PROTECTED]> -
Date: Sun, 22 May 2005 04:19:03 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTEC
On Sun, May 22, 2005 at 12:20:39PM -0400, Ove Kaaven wrote:
> søn, 22,.05.2005 kl. 00.10 -0700, skrev Steve Langasek:
> > Having four versions of gmime in a stable release means a four-fold increase
> > in the security team's workload if a security bug is found. (This is true
> > even if the bug o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
Both RC bugs in clearsilver have been fixed in NMUs (#310073 and
#310231). I can't judge whether the package as a whole is
release-worthy (I don't use it, but there are other non-RC bugs), but
the RC issues are fixed at least.
Regards,
Ro
Hi,
I've just made an NMU for gkrellm to close the RC-bug #309089. I've only
added a patch to make gkrellm use gnutls instead of (GPL-incompatible)
openssl.
I've been able to get my mail count (it's the only use of ssl in
gkrellm) over imaps and some people told me that they have been able to
Hello,
please allow mutt 1.5.9-2 into sarge, it fixes an RC bug (FTBFS) and
contains a translation update.
Changelog entry follows, thanks.
mutt (1.5.9-2) unstable; urgency=high
* Added a missing Build-Depend on mawk. (Closes: #310039)
* Updated the Swedish translation.
-
Hello team,
The just uploaded mailutils 0.6.1-3 should go in Sarge as soon as it's
built, as it fixes 4 security vulnerabilities.
Thanks,
Jordi
--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sindominio.net/
GnuPG pub
On Sun, May 22, 2005 at 04:16:17PM +0200, Frank Lichtenheld wrote:
> > tsclient (0.132-7) unstable; urgency=medium
>
> Hmm, could you please use the changelog entry for -6 it was uploaded
> with? (At least with the correct person, I don't care about funny
> remarks ;))
On second thought, approved
On Thu, 19 May 2005, Henrique de Moraes Holschuh wrote:
> hplip (0.9.2-2) unstable; urgency=low
Ooops! Version is 0.9.2-*2*, and not 0.9.2-3 as I wrote in the subject :(
Excuse for hplip
* 12 days old (needed 10 days)
* Unblock request by joeyh ignored due to version mismatch: 0.9.2-3
On Sunday 22 May 2005 11:51, Joerg Jaspert wrote:
> On 10297 March 1977, Frans Pop wrote:
> > For the &releasename; release, all packages that were formerly in
> > the non-US part of the archive have been moved into the regular
> > archive. If you have any lines referring to "non-us" in your
> > /e
On Sun, May 22, 2005 at 02:01:09AM +1000, Andrew Lau wrote:
> 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;
On Sun, May 22, 2005 at 01:26:46AM +0200, Rene Engelhard wrote:
> > Also, I couldn't locate the place where the upstream maintainer changed,
> > nor the place where MAINT_SEARCH was disabled. (And the diff is a bit
> > verbose due to changing the path of the diffs - well, I don't mind too
> > much
On Wed, May 18, 2005 at 10:59:26PM +0200, [EMAIL PROTECTED] wrote:
> Hi and my kuddos to the Release Team. I'm not an XChat maintainer, rather
> a user. This package has been in uploaded in unstable for two weeks now
> and it fixes some serious bugs. Here is the changelog:
Sorry, but the diff betw
Steve Langasek wrote:
>
> The question is, how can we be proactive about identifying the classes of
> changes that do or don't break these packages, so that mozilla can be
> checked for compatibility at the time of upload instead of having kazehakase
> and enigmail update their conflicts: after th
The version in Sid of mozilla-firefox-locale-all fixes an important bug, as I
failed to include the postint and postrm files for
mozilla-firefox-theme-rtlclassic in the version in sarge (this bug is not in
DBTS, though, as I created the new package as soon as I realised on the
mistake).
This v
On Sun, May 22, 2005 at 12:41:11AM +0200, Adrian Bunk wrote:
> - rename the unrar-nonfree package back to unrar
> - rename the free unnrar package to unrar-free (it can even be left out
> of sarge (version 0.0.1 that is the one year old latest upstream
> version...))
> - get the non-free pack
On Sun, May 22, 2005 at 02:12:56PM +0200, Alexander Sack <[EMAIL PROTECTED]>
wrote:
> Mike Hommey wrote:
> >
> > This time, the version update is supposed to be security only, and not
> > to break stuff. Thus, theorically, just changing the Conflicts: in the
> > control file is enough to have the
Mike Hommey wrote:
>
> This time, the version update is supposed to be security only, and not
> to break stuff. Thus, theorically, just changing the Conflicts: in the
> control file is enough to have these programs depending on
> mozilla-browser be able to use the security fix release.
>
> Note t
Steve Langasek wrote:
>
>
> The question is, how can we be proactive about identifying the classes of
> changes that do or don't break these packages, so that mozilla can be
> checked for compatibility at the time of upload instead of having kazehakase
> and enigmail update their conflicts: afte
On Sun, May 22, 2005 at 10:20:18AM +0100, Martin Michlmayr wrote:
> Please remove cantus from testing.
> While I don't feel comfortable removing it from the archive altogether
> because someone has indicated some interest in adopting it (but that
> was a long time ago), it should not ship with sar
Steve Langasek <[EMAIL PROTECTED]> writes:
>> g-wrap (1.9.6-1) unstable; urgency=high
>>
>> * New upstream version. This nevertheless means no real changes against
>> 1.9.5-2, since we already had all of the upstream fixes applied.
>> * Ship g-wrap-config in libgwrap-runtime0-dev and make
On 10297 March 1977, Frans Pop wrote:
> If it is certain that non-US is empty on release date, lets make the text
> a bit stronger:
> non-US obsoleted
> For the &releasename; release, all packages that were formerly in the
> non-US part of the archive have been moved into the regular archive.
>
Please remove cantus from testing.
While I don't feel comfortable removing it from the archive altogether
because someone has indicated some interest in adopting it (but that
was a long time ago), it should not ship with sarge. FWIW, cantus3
has just been removed from unstable. Both cantus and c
On Sun, May 22, 2005 at 10:39:50AM +0200, Mike Hommey wrote:
> > It looks like the security-fix-only new upstream version of mozilla, 1.7.8,
> > has blocked again on kazehakase and enigmail (and probably on locale
> > packages, but I haven't gotten there yet) because the sarge versions of
> > these
On Sun, May 22, 2005 at 01:16:50AM -0700, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> Hi folks,
>
> It looks like the security-fix-only new upstream version of mozilla, 1.7.8,
> has blocked again on kazehakase and enigmail (and probably on locale
> packages, but I haven't gotten there yet) becaus
On Sat, May 21, 2005 at 01:37:42PM +0200, Marco d'Itri wrote:
> diff -urNp whois-4.7.4/debian/changelog whois-4.7.5/debian/changelog
> --- whois-4.7.4/debian/changelog 2005-04-29 00:55:58.0 +0200
> +++ whois-4.7.5/debian/changelog 2005-05-18 16:03:10.0 +0200
> @@ -1,3 +1,1
Hi folks,
It looks like the security-fix-only new upstream version of mozilla, 1.7.8,
has blocked again on kazehakase and enigmail (and probably on locale
packages, but I haven't gotten there yet) because the sarge versions of
these packages conflict with mozilla-browser (>= 2:1.7.8).
The solutio
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 kernel-
On Sat, May 21, 2005 at 09:44:36AM +0200, Jose Carlos Garcia Sogo wrote:
> Please, allow the following package uploaded to t-p-u, as requested to
> circunvent newer version uploaded to unstable.
Approved, although this upload seems to include a gratuitous addition of a
dpatch build-dependency.
I
On Sat, May 21, 2005 at 03:50:39AM +0200, Andreas Rottmann wrote:
> I uploaded g-wrap 1.9.6-2, and it got built on all architectures
> (except on ia64, due to a Guile bug, but it has never built on ia64
> anyway). I'd like this version to go into Sarge, which currently has
> 1.9.5-2. Note that even
On Sun, May 22, 2005 at 12:01:26AM +0200, Guus Sliepen wrote:
> On Sat, May 21, 2005 at 03:43:24PM -0400, Ove Kaaven wrote:
> > lør, 21,.05.2005 kl. 12.13 -0700, skrev Steve Langasek:
> > > It looks like there are four versions of gmime in testing currently
> > > (gmime,
> > > gmime1, gmime2, gmi
67 matches
Mail list logo
