Re: unblocking e2fsprogs

[Adeodato Simó]

* Otavio Salvador [Wed, 23 Jul 2008 21:46:31 -0300]:

> Adeodato Simó <[EMAIL PROTECTED]> writes:

> > Ok, I trust you on this. Will unblock when I hear back from the d-i
> > people (because of the udeb).

> No objection.

Unblocked.

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Listening to: Pedro Guerra - Pasaba por aquí


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: unblocking e2fsprogs

[Otavio Salvador]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Adeodato Simó <[EMAIL PROTECTED]> writes:

> Ok, I trust you on this. Will unblock when I hear back from the d-i
> people (because of the udeb).

No objection.

- -- 
O T A V I OS A L V A D O R
- -
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
- -
"Microsoft sells you Windows ... Linux gives
 you the whole house."
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iEYEARECAAYFAkiH0OUACgkQLqiZQEml+FW37gCghrAmGhgPIkzYPWQddXnrDdVz
7KsAn2lMc9HOnWjrnlNeIXK16fp1QjQ8
=KZp0
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New release of uw-imap prepared and uploaded to experimental

[Adeodato Simó]

On other news...

> >binNMUs scheduled now.
> Thanks!

If you could take care of filing bugs against asterisk and prayer so
that they build-depend on libc-client-dev instead of libc-client2007-dev,
and upload quick/prompt NMUs if needed, I'd be very grateful.

If you really can't, please let me know so that I know somebody will
have to take care.

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
  Listening to: Andrés Calamaro - Paloma


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: openbabel-2.2 transition

[Adeodato Simó]

(JFTR: it was agreed with me on IRC to go forward with this.)

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Listening to: Andrés Calamaro - Nos volveremos a ver


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: please unblock libidn/1.9-1

[Adeodato Simó]

* Aníbal Monsalve Salazar [Wed, 23 Jul 2008 21:21:07 +1000]:

Hello, Aníbal.

> On Mon, Jul 21, 2008 at 10:23:31AM +1000, Anibal Monsalve Salazar wrote:
> >Please unblock libidn/1.9-1
> >It uses an upstream released tarball with a fix for the RC bug 484093
> >It has been in unstable for 10 days

As far as I can see, the version in testing (1.8+20080606-1) already
fixes #484093, so is there some *other* reason why 1.9 is needed in
testing?

Thanks,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
  Listening to: Andrés Calamaro - Estadio azteca


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Why you need not upload with urgency=high for the freeze

[Adeodato Simó]

* Sandro Tosi [Tue, 22 Jul 2008 16:47:00 +0200]:

> On Tue, Jul 22, 2008 at 02:13, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> >  | Packages that are present in unstable the day we freeze will be
> >  | automatically allowed into testing, that is, the freeze date (next
> >  | weekend) does not mean your package should be in testing by then,
> >  | but only in unstable.

> Thanks for clarifying this! I would have asked sooner or later if you
> hadn't said explicitly. Do you think worth write some sort of FAQ
> about these things, a document that can be published on
> release.debian.org to advertise us? We do not release so often, so
> something to "remind" how things go on could be helpful.

Well, the release updates have been the traditional place to document
this, but if we end up with many things to say, a document in release.d.o
may be indeed wiser. I'll keep it in mind!

> Additionally, how NEW packages are handled? Pkgs in NEW now, if
> accepted, would be allowed to migrate in testing?

Hm, good question, and I have not an answer ready at the moment, will
have to wait a few days. Though unless you're planning a NEW upload that
could be reduced to a non-NEW upoad, the answer doesn't really affect
you?

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
   Listening to: Andrés Calamaro - Vigilante medio argentino


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

unblocking e2fsprogs

[Adeodato Simó]

To -boot: ok to unblock e2fsprogs?

* Theodore Tso [Mon, 21 Jul 2008 23:43:53 -0400]:

> In any case, e2fsprogs has been in testing for six days now (seven by
> tomorrow morning :-), and I think it is ready for testing.  I
> understand that the freeze for libraries had already happened (I
> didn't realize that; I thought I had a little bit more time), but I
> would like to request an exception.  The libext2fs libraries are
> relied upon by very few programs, and 1.41 did not change any shared
> library ABI's; I'm *very* anal careful about only adding new
> interfaces, and not changing existing ones.

> In addition 1.41.0 closed a large number of bugs over 1.40.11, and is
> the first version to have ext4 support.  So I really would like to see
> e2fsprogs included, and would really appreciate it if the Debian
> Release Team would see fit to bend the library freeze slightly to
> allow the packages built by the e2fsprogs source package into testing.

Ok, I trust you on this. Will unblock when I hear back from the d-i
people (because of the udeb).

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Listening to: Andrés Calamaro - Loco


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: please unblock xulrunner

[Adeodato Simó]

* Nico Golde [Wed, 23 Jul 2008 15:03:34 +0200]:

> Hi,
> can someone please unblock xulrunner?
> 1.9.0.1-1 fixes CVE-2008-2785[0] which is a fairly important 
> security issue that allows arbitrary code execution by 
> overflowing a CSS reference counter.

Neil had an "age-days" set to 2, but that's not enough to unfreeze the
package, an "unblock" is needed. CCing so that he can take care.

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
 Listening to: Andrés Calamaro - Los aviones


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: noweb stuck in sid

[Adeodato Simó]

* Hubert Chathi [Sat, 19 Jul 2008 23:14:17 -0400]:

> On Sun, 20 Jul 2008 01:27:57 +0100 Adeodato Simó <[EMAIL PROTECTED]>
> wrote:

> > * Hubert Chathi [Sat, 19 Jul 2008 11:35:20 -0400]:

> > > How is that?  noweb just depends on gawk, iconx, and libc6, and the
> > > dependency on iconx is unversioned, so shouldn't it be satisfied
> > > with the version of icon that's in testing?

> > There is no noweb in armel in testing, though, so in order to migrate
> > noweb/2.11b-7/armel, britney wants to migrate iconx/9.4.3-1/armel
> > first. And see #475952 about that...

> > However, since noweb/armel is broken in testing anyway, migrating it
> > does not makes things worse, so I've added a force hint to let noweb
> > migrate.

> OK, thanks.  The main reason that I was asking is that noweb in sid
> fixes a bashism, which is a release goal.  None of the other changes is
> particularly important.

I see. I'm afraid I wasn't aware that the normal hint for these cases
is not able to force it through after all, so it'll have to wait for
icon.

If it was RC, I would go a bit out of my way to force it in, but I
rather not to that at this stage.

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
   Listening to: Andrés Calamaro - Las oportunidades


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#484121: fixed in tasksel 2.75

[Adeodato Simó]

* Josselin Mouette [Tue, 22 Jul 2008 11:52:45 +0200]:

> Le mardi 22 juillet 2008 à 04:32 +, Joey Hess a écrit :
> >Please note that this upload should not be allowed to reach testing 
> > before
> >meta-gnome2 2.22.2~2 does. However, I've been waiting on that for exactly
> >one month, and this version of tasksel does need to get into lenny for 
> > the
> >release.

> Thanks for the upload.

> Dear release team, could you please bump the urgency of cheese and
> meta-gnome2 to ensure they reach testing before tasksel ?

I've set cheese to need 8 days instead of 10; that should give a 2-day
padding for cheese and meta-gnome2 to migrate (in 6 days) before taskel
does (in 8). If you could check that in 6 or 7 days meta-gnome2 has
migrated, that'd be great -- if problems have arised, we can temporarily
block taskel until we get it sorted out.

Thanks,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
 Listening to: Andrés Calamaro - Te quiero igual


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: binNMU for gdal and then mapserver

[Adeodato Simó]

* Francesco P. Lovergine [Tue, 22 Jul 2008 10:21:08 +0200]:

> Ok, I found finally that GDAL 1.5.2 has problems with optimization and
> GCC 4.3, so I'm going to upload an -3 with optimization off to close
> #489124 which should be considered indeed a RC issue.

Sorry, I got a bit lost on the thread: is any action needed on our part?
(Just asking to get this off my plate.)

Thanks,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
 Listening to: Andrés Calamaro - Te quiero igual


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New release of uw-imap prepared and uploaded to experimental

[Adeodato Simó]

* Jonas Smedegaard [Wed, 23 Jul 2008 12:35:57 +0200]:

Hello, Jonas,

> On Tue, Jul 22, 2008 at 09:24:46PM +0100, Adeodato Simó wrote:
> >In case you weren't aware, you need to *tell* the release team you've 
> >gone forward if you want your transition managed in any way.

> Thanks for clarifying.

> I got no feedback (before now), and thought that perhaps your new 
> package blocking mechanisms made it less relevant for you to 
> coordinate each specific package transition.  So I went on and uploaded 
> to unstable...

> I am not writing this to excuse myself - I know that you must be busy 
> these days, and I should of course have had more (but how much?) 
> patience.

> I write it more to help give you a hint on how a package maintainer 
> might react (correct or not) on not getting a response on email sent to 
> your list.

Yeah. There are two issues here:

  * the fact that you went ahead and uploaded without an ack: this is in
my opinion perfectly fine, because we failed to get back to you at
all (we try that this doesn't happen too often, but I'm afraid it
really does :/)

  * the fact that once a soname-bumping package is uploaded to unstable,
-release must get notified so that we know of its existance; I
thought the need for this was common knowledge, and I may have
sounded a bit too harsh because of that.

Thanks,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
 Listening to: Andrés Calamaro - El cantante


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: imminent 2.6.26 sid upload

[Steve Langasek]

On Wed, Jul 23, 2008 at 08:07:25PM -0300, Otavio Salvador wrote:

> > That's just adding an arbitrary 5 days delay.  Uploading to experimental
> > won't uncover new issues, because nobody uses packages in experimental.

> Uploading it to sid, will make a revertion to .25 much harder if
> needed. Besides that, we'd need to know if it _at least_ builds on all
> architectures and then be ready to upload meta packages...

No, it really would be a waste of time.  2.6.25 is already in testing, so
t-p-u is still there as an update path; but no one on the kernel side is
really considering 2.6.25 to be an option for lenny, and the sooner we get
2.6.26 into unstable the sooner we can get everything smoothed out for
lenny.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mozilla in Lenny

[Philipp Kern]

On Wed, Jul 23, 2008 at 11:39:58PM +, Sam Morris wrote:
> There's also a bug unreported in Debian so far, but that affects epiphany 
> very badly. When a file is downloaded, instead of displaying the 
> 'download complete' notification, epiphany crashes. This doesn't happen 
> every time, but I hit the crash several times a day.

I had such a failure for quite some time with all xulrunner
applications, i.e. also with firefox 3.  Nowadays, with current
sid it didn't happen for me anymore, though...

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: Mozilla in Lenny

[Sam Morris]

On Wed, 23 Jul 2008 13:26:58 +0200, Josselin Mouette wrote:

> Le mercredi 23 juillet 2008 à 07:57 +0200, Mike Hommey a écrit :
>> (I may have forgotten some others, if you can think of some, please
>> followup. I'll also do that myself if I remember something important)
> 
> For epiphany, blockers are the following:
>   * #393837 which was flagged critical by the security team. It has
> been here for a long while and should probably be fixed on the
> gtkmozembed side, but it’s just a wild guess. We badly need HELP
> from someone with knowledge of the chrome internals to fix it.
>   * #486744 which is on the top list of crashes reported to GNOME
> bugzilla.
> 
> Cheers,

There's also a bug unreported in Debian so far, but that affects epiphany 
very badly. When a file is downloaded, instead of displaying the 
'download complete' notification, epiphany crashes. This doesn't happen 
every time, but I hit the crash several times a day.

This is filed upstream as .



-- 
Sam Morris
http://robots.org.uk/
 
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Preparation of the next stable Debian GNU/Linux update

[Philipp Kern]

On Thu, Jul 24, 2008 at 02:24:33AM +0300, Eugene V. Lyubimkin wrote:
> Philipp Kern wrote:
> > We are preparing the next revision of the current stable Debian
> > distribution (sarge) and will frequently send reports so people can
> You mean etch, don't you?

Sure.  Classical copy'n'paste mistake.

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: Preparation of the next stable Debian GNU/Linux update

[Eugene V. Lyubimkin]

Philipp Kern wrote:
> We are preparing the next revision of the current stable Debian
> distribution (sarge) and will frequently send reports so people can
You mean etch, don't you?

-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.



signature.asc
Description: OpenPGP digital signature

Preparation of the next stable Debian GNU/Linux update

[Philipp Kern]

[NB: This mail looks different from previous preparation mails.  Its ]
[concrete layout is still to be determined, though.  ]

Preparation of Debian GNU/Linux 4.0r4
=

An up-to-date version is at .

We are preparing the next revision of the current stable Debian
distribution (sarge) and will frequently send reports so people can
actually comment on it and intervene whenever this is required.

If you disagree with one bit or another, please reply to this mail and
explain why these things should be handled differently.

An ftpmaster still has to give the final approval for each package
since ftpmasters are responsible for the archive.  However, we are
trying to make their work as easy as possible in hope to get the next
revision out properly and without any hassle.

If you would like to get a package updated in the stable release, you
are advised to talk to the stable release managers first (see
).

Accepted Packages
-

These packages will be installed into the stable Debian distribution
and will be part of the next revision.

Sourceful update of speex:
 version in stable:  1.1.12-3
 version in updates: 1.1.12-3etch1
 Rationales:
  - 1.1.12-3etch1: DSA 1585 speex - Fix arbitrary code execution (#415327)

Sourceful update of peercast:
 version in stable:  0.1217.toots.20060314-1etch0
 version in updates: 0.1217.toots.20060314-1etch1
 Rationales:
  - 0.1217.toots.20060314-1etch1: DSA 1582 peercast - arbitrary code execution

New package linux-kbuild-2.6.24:
 version in updates: 2.6.24-1~etchnhalf.1
 Rationales:
  NO RATIONALES FOUND!

Sourceful update of libtk-img:
 version in stable:  1:1.3-15
 version in updates: 1:1.3-15etch2
 Rationales:
  - 1.3-15etch2: DSA 1598 libtk-img - buffer overflow

Sourceful update of sysvinit:
 version in stable:  2.86.ds1-38
 version in updates: 2.86.ds1-38+etchnhalf.1
 Rationales:
  - 2.86.ds1-38+etchnhalf.1: sysvinit - update shutdown to work w/ libata in 
linux >= 2.6.23

Sourceful update of moin:
 version in stable:  1.5.3-1.2
 version in updates: 1.5.3-1.2etch1
 Rationales:
  - 1.5.3-1.2etch1: DSA 1514 moin - Several vulnerabilities

Sourceful update of blender:
 version in stable:  2.42a-7
 version in updates: 2.42a-7.1+etch1
 Rationales:
  - 2.42a-7.1+etch1: DSA 1567 blender - Fix arbitrary code execution

Sourceful update of sympa:
 version in stable:  5.2.3-1.2
 version in updates: 5.2.3-1.2+etch1
 Rationales:
  - 5.2.3-1.2+etch1: DSA 1600 sympa - denial of service

Sourceful update of samba:
 version in stable:  3.0.24-6etch9
 version in updates: 3.0.24-6etch10
 Rationales:
  - 3.0.24-6etch10: DSA 1590 samba - arbitrary code execution

Sourceful update of hal:
 version in stable:  0.5.8.1-9
 version in updates: 0.5.8.1-9etch1
 Rationales:
  - 0.5.8.1-9etch1: hal - Allows mounting ntfs volumes from within KDE (#418176)

Sourceful update of fai-kernels:
 version in stable:  1.17+etch.18etch1
 version in updates: 1.17+etch.21
 Rationales:
  - 1.17+etch.18etch2: DSA 1565 fai-kernels - Fix several vulnerabilities 
(linux-2.6)
  - 1.17+etch.18etch3: DSA 1565 fai-kernels - Fix several vulnerabilities 
(linux-2.6)
  - 1.17+etch.18etch4: DSA 1575 fai-kernels - Fix denial of service (linux-2.6)
  - 1.17+etch.18etch5: DSA 1588 fai-kernels - several vulnerabilities 
(linux-2.6)
  - 1.17+etch.21: fai-kernels - Rebuild against linux-2.6_2.6.18.dfsg.1-21

Sourceful update of debian-installer:
 version in stable:  20070308etch2
 version in updates: 20070308etch3
 Rationales:
  - 20070308etch3: debian-installer - rebuild images containing network-console

Sourceful update of kronolith2:
 version in stable:  2.1.4-1
 version in updates: 2.1.4-1etch1
 Rationales:
  - 2.1.4-1etch1: DSA 1560 kronolith2 - Fix cross site scripting

Sourceful update of apache2:
 version in stable:  2.2.3-4+etch4
 version in updates: 2.2.3-4+etch5
 Rationales:
  - 2.2.3-4+etch5: apache2 - Fix possible segfault introduced by patch for 
CVE-2007-6421.

Sourceful update of user-mode-linux:
 version in stable:  2.6.18-1um-2etch.18etch1
 version in updates: 2.6.18-1um-2etch.21
 Rationales:
  - 2.6.18-1um-2etch.18etch2: DSA 1565 user-mode-linux - Fix several 
vulnerabilities (linux-2.6)
  - 2.6.18-1um-2etch.18etch3: DSA 1565 user-mode-linux - Fix several 
vulnerabilities (linux-2.6)
  - 2.6.18-1um-2etch.18etch4: DSA 1575 user-mode-linux - denial of service 
(linux-2.6)
  - 2.6.18-1um-2etch.18etch5: DSA 1588 fai-kernels - several vulnerabilities 
(linux-2.6)
  - 2.6.18-1um-2etch.21: user-mode-linux - Rebuild against 
linux-2.6_2.6.18.dfsg.1-21

Sourceful update of dns-flood-detector:
 version in stable:  1.12-1
 version in updates: 1.12-1etch1
 Rationales:
  - 1.12-1etch1: dns-flood-detector - Actually write a pid file for 
start-stop-daemon (#431676)

Sourceful update of dovecot:
 version in stable:  1.0.rc15-2etch3
 version in updates: 1.0.rc15-2etch4
 Rationale

Re: imminent 2.6.26 sid upload

[Otavio Salvador]

Julien Cristau <[EMAIL PROTECTED]> writes:

> On Wed, Jul 23, 2008 at 09:02:26 -0300, Otavio Salvador wrote:
>
>> I'd prefer to have it on experimental before upload it to unstable so
>> first and more urgent issues wouldn't bother us and users however this
>> is more up to you and RM team then me. My preference would be:
>> 
>>  - upload to experimental
>>  - wait for at least 5 days without issues
>
> That's just adding an arbitrary 5 days delay.  Uploading to experimental
> won't uncover new issues, because nobody uses packages in experimental.

Uploading it to sid, will make a revertion to .25 much harder if
needed. Besides that, we'd need to know if it _at least_ builds on all
architectures and then be ready to upload meta packages...

As I said, this is more up to kernel team and release management team
then me but it is the safest option IMO.

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
-
"Microsoft sells you Windows ... Linux gives
 you the whole house."


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

user-mode-linux 2.6.25 [was Re: imminent 2.6.26 sid upload]

[Mattia Dongili]

[d-boot probably not interested in this subtopic]

On Tue, Jul 22, 2008 at 11:48:20PM +0200, maximilian attems wrote:
> latest 2.6.25 stable release is in testing, we expect to keep it as backup
> plan for lenny.  release team wishes to have unstable coverage of 2.6.26
> before final ack on that release.

On a slightly separate but related note, I'm uploading
user-mode-linux_2.6.25-2 now to fix a build error on x84_64.

Uml 2.6.25 is not in testing yet (my fault, didn't have time to get on
top of that recently) so I was wondering what are the plans for
linux-source-2.6.25.
Are you going to remove it from unstable and eventually realize the
"backup plan" via tpu uploads?

The current version in testing is unmaintainable as it build-depends on
linux-source-2.6.24 which is not available anymore and it doesn't make
any sense to realease it in lenny. On the other hand what is the
scenario if 2.6.25 goes missing in unstable while uml is not in testing
yet?
I hope I've been able to explain my worries...

PS: once uml 2.6.25 is in testing I'll be able to upload 2.6.26 to stay
in sync with the current kernel sources.
-- 
mattia
:wq!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: imminent 2.6.26 sid upload

[Julien Cristau]

On Wed, Jul 23, 2008 at 09:02:26 -0300, Otavio Salvador wrote:

> I'd prefer to have it on experimental before upload it to unstable so
> first and more urgent issues wouldn't bother us and users however this
> is more up to you and RM team then me. My preference would be:
> 
>  - upload to experimental
>  - wait for at least 5 days without issues

That's just adding an arbitrary 5 days delay.  Uploading to experimental
won't uncover new issues, because nobody uses packages in experimental.

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Give back octave3.0 on sparc

[Julien Cristau]

On Wed, Jul 23, 2008 at 11:08:02 +0200, Rafael Laboissiere wrote:

> Please, give back octave3.0/3.0.1-6 on sparc.  The autobuild failed with a
> cryptic message [1]:
> 
> g++ -c  -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc 
> -DHAVE_CONFIG_H -Wall -W -Wshadow -Wold-style-cast -O2 -g 
> ./DLD-FUNCTIONS/fft2.cc -o pic/fft2.o
> /tmp/cc3m4XSW.s: Assembler messages:
> /tmp/cc3m4XSW.s:114060: Error: Unknown opcode: `byte'
> 
> Version 3.0.1-5 of the package built fine on sparc [2] and both the g++
> compiler version (4.3_4.3.1-6) and the fft2.cc file were the same in the
> octave3.0_3.0.1-6 autobuild.

What about binutils?

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#491601: madwifi-source fails to build against 2.6.24-etchnhalf.1-486

[dann frazier]

On Wed, Jul 23, 2008 at 08:42:20PM +0200, Michael Goetze wrote:
> Hi,
>
> On 21.07.2008, at 08:40, dann frazier wrote:
>>
>> Also note that the ath5k driver is included in the 2.6.24 kernel - I
>> don't personally know how much hardware works with madwifi but not
>> ath5k though.
>
> Well, for one thing, it's missing some exotic features like, say, Master 
> mode. ;)

Yep, that's a big one :) It also seems to not work well w/ WPA (at
least, not on the laptop I tried).

Again, we're open to adding a madwifi-etchnhalf package in a point
release. For 4.0r4, the window is closing very quickly since the
release is scheduled for this Friday, but a 4.0r5 can hopefully happen
~2 months later.

The requirements for such a package are:
 * module either adds new hardware support for etch, or achieves
   feature parity with the etch 2.6.18 kernel. etchnhalf is
   specifically targeted at adding hardware support, so adding things
   like new filesystems would be out-of-scope.
 * module must not be rc-buggy (obviously)
 * module version must be <= version in lenny
 * source and binary packages should have -etchnhalf appended
 * module source should get installed in /usr/src/etchnhalf (this
   lets the package coeexist w/ its etch counterpart)
 * Included documentation should explain how to point m-a at the new
   location (e.g., # MOD_SRCDIR=/usr/src/etchnhalf m-a b-i). Note
   that a-i and other commands that attempt to fetch source won't
   work - the -etchnhalf namespace breaks that :(
 * source package should omit any redundant packages
 * module has been tested in etch w/ etchnhalf kernel (i.e.,
   compatible with etch userspace)

squashfs-etchnhalf, atl2-etchnhalf and loop-aes-etchnhalf are examples
of this.

-- 
dann frazier


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#491601: madwifi-source fails to build against 2.6.24-etchnhalf.1-486

[Michael Goetze]

Hi,

On 21.07.2008, at 08:40, dann frazier wrote:


Also note that the ath5k driver is included in the 2.6.24 kernel - I
don't personally know how much hardware works with madwifi but not
ath5k though.


Well, for one thing, it's missing some exotic features like, say,  
Master mode. ;)


Regards,
Michael


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Selection of kernel for Lenny

[Steve Langasek]

Hi Aurelien,

On Mon, Jul 07, 2008 at 06:19:01PM +0200, Aurelien Jarno wrote:

> - The switch to linux-libc-dev 2.6.25 is the reason why glibc currently
> FTBFS on hppa (due to a timeout in a test). Unfortunately I don't know
> yet which change causes the problem, I am down to a 600 lines diff.

Have you gotten any closer to finding the cause of this regression?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: please unblock reportbug-ng

[Josselin Mouette]

Le mercredi 23 juillet 2008 à 16:05 +0200, Bastian Venthur a écrit :
> Josselin Mouette wrote:
> > Does it support /usr/share/bug/*/control files now ?
> 
> No, mainly because it is not obvious to me what the fields in this file
> mean.

Because of that, totem and epiphany-browser reports that were filed
using reportbug-ng are mostly useless, and I’m often tempted to ask the
user to report it using reportbug instead.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: please unblock reportbug-ng

[Sune Vuorela]

On 2008-07-23, Bastian Venthur <[EMAIL PROTECTED]> wrote:
> No, mainly because it is not obvious to me what the fields in this file
> mean.

Please read the README.developers shipped with reportbug. It documents
this and other issues, like usage of yesno and getkey commands in bug
scripts.

/Sune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: please unblock reportbug-ng

[Bastian Venthur]

Josselin Mouette wrote:
> Le mardi 22 juillet 2008 à 18:51 +0200, Bastian Venthur a écrit :
>> reportbug-ng now supports /usr/share/bug/*/script and sends the output
>> if the file is available. The lack of this feature rendered rng unfit
>> for release in the eyes of the release team, since it's implemented now
> 
> Does it support /usr/share/bug/*/control files now ?

No, mainly because it is not obvious to me what the fields in this file
mean.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [etch-and-half] release notes review

[Moritz Muehlenhoff]

On Wed, Jul 23, 2008 at 02:35:46PM +0200, Alexander Reichle-Schmehl wrote:
> [ dropping every ones but Moritz' and Andrea's personal e-mail address
>   from cc; adding [EMAIL PROTECTED] and [EMAIL PROTECTED]
>   to cc ]
> 
> Hi Moritz!
> 
> Moritz Muehlenhoff schrieb:
> 
> > Andreas Schuldei and I will work on a press release and pass it to the
> > press team (unless they've started something on their own already)
> 
> Didn't got anything, yet.  Could you please pass what you've done so far
> ASAP?

I didn't have time so far, but was planning this for tonight. If you
want to have it faster, please go ahead.

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

please unblock xulrunner

[Nico Golde]

Hi,
can someone please unblock xulrunner?
1.9.0.1-1 fixes CVE-2008-2785[0] which is a fairly important 
security issue that allows arbitrary code execution by 
overflowing a CSS reference counter.

Every iceweasel user who has not switched off java script 
could be affected by this. More about the vulnerability 
itself in the upstream advisory[1].

In Debian this does technically affect xulrunner and not 
iceweasel as discussed[2] with the maintainer so it would be 
nice if someone could unblock xulrunner 1.9.0.1-1 to enter lenny.

[0] http://security-tracker.debian.net/tracker/CVE-2008-2785
[1] http://www.mozilla.org/security/announce/2008/mfsa2008-34.html
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491161#17

Cheers
Nico

-- 
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.


pgpimfXd88Nv8.pgp
Description: PGP signature

Re: [etch-and-half] release notes review

[Alexander Reichle-Schmehl]

[ dropping every ones but Moritz' and Andrea's personal e-mail address
  from cc; adding [EMAIL PROTECTED] and [EMAIL PROTECTED]
  to cc ]


Hi Moritz!

Moritz Muehlenhoff schrieb:

> Andreas Schuldei and I will work on a press release and pass it to the
> press team (unless they've started something on their own already)

Didn't got anything, yet.  Could you please pass what you've done so far
ASAP?

yours sincerely,
  Alexander



signature.asc
Description: OpenPGP digital signature

Re: [SRM] etch-n-half late git-core update permission (Was: [PATCH 0/5] add pack index v2 reading capability to git v1.4.4.4)

[Pierre Habouzit]

On Wed, Jul 23, 2008 at 12:24:27PM +, Philipp Kern wrote:
> On Mon, Jul 21, 2008 at 12:12:17PM +0200, Pierre Habouzit wrote:
> >   Okay, I asked permission to some SRMs that weren't shocked by this
> > late update, and I'd be really glad if the updated git-core could sneak
> > in.
> 
> Please go ahead with the upload.

  Done, and thanks.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpHNL7VLfiaI.pgp
Description: PGP signature

Re: [SRM] etch-n-half late git-core update permission (Was: [PATCH 0/5] add pack index v2 reading capability to git v1.4.4.4)

[Philipp Kern]

On Mon, Jul 21, 2008 at 12:12:17PM +0200, Pierre Habouzit wrote:
>   Okay, I asked permission to some SRMs that weren't shocked by this
> late update, and I'd be really glad if the updated git-core could sneak
> in.

Please go ahead with the upload.

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: please unblock reportbug-ng

[Bastian Venthur]

Pierre Habouzit wrote:
> On Wed, Jul 23, 2008 at 10:19:23AM +, Bastian Venthur wrote:
>> Pierre Habouzit wrote:
>>> On Tue, Jul 22, 2008 at 04:51:08PM +, Bastian Venthur wrote:
 Hi,

 reportbug-ng now supports /usr/share/bug/*/script and sends the output
 if the file is available. The lack of this feature rendered rng unfit
 for release in the eyes of the release team, since it's implemented now
 I think rng should enter testing again.
>>> Does it supports presubjs and helps the user choosing a proper severity
>>> for bugs he reports ?
>> It does not show presubjs.
> 
>   This is a major stopper.
> 
>> What do you mean by helping to choose a proper severity? The default
>> severity is "normal" and the "what is this" help of the box where you
>> can select the severity explains every severity in detail.
> 
>   There is an RC bug about that (or at least the RM team consider it a
> blocker) where there is really sensible explanations on why this is not
> a good UI and that it leads to bad bug reports.

If I remember correctly Phillip blocked rng because it didn't sent the
output of /usr/share/bug/*/script. That's at least what I understood
when reading Phillip's mail and that is fixed now.

I never heard that it was blocked because the UI isn't good enough. I
don't want to have to guess what also has to be fixed until you decide
rng is good enough for lenny or lenny+1, so please give me an exact list
of the remaining open points which have to be fixed until rng is fit for
testing.

As a next step, I want that list and the fittnes of rng discussed on
tech-ctte. Frankly, I doubt that you are still deciding from a neutral
POV, especially regarding the discussion between you and me documented
in #422085.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: please unblock rdate/1:1.1.3-2

[Philipp Kern]

On Wed, Jul 23, 2008 at 09:28:47PM +1000, Aníbal Monsalve Salazar wrote:
> Release team please unblock it.

Done.

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: please unblock rdate/1:1.1.3-2

[Otavio Salvador]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Aníbal Monsalve Salazar <[EMAIL PROTECTED]> writes:

> Otavio please approve rdate/1:1.1.3-2
>
> Release team please unblock it.
>
> Changes: 
>  rdate (1:1.1.3-2) unstable; urgency=low
>  .
>[ Jérémy Bobbio ]
>* When "-vv" is specified, rdate now displays a dot each time it tries
>  to send a packet to the NTP server.  This is needed to implement
>  cancelation of time synchronisation in the debian-installer.
>  Closes: 491540.
>  .
>[ Anibal Monsalve Salazar ]
>* Standards-Version is 3.8.0

No objection

- -- 
O T A V I OS A L V A D O R
- -
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
- -
"Microsoft sells you Windows ... Linux gives
 you the whole house."
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iEYEARECAAYFAkiHHj4ACgkQLqiZQEml+FWsIwCfVJCJzU5cu8yiISHTtuZGd14/
Rl4AoIA3XKvF2bq4/wJR2xkPgg1pAg+b
=edpl
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: imminent 2.6.26 sid upload

[Otavio Salvador]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

maximilian attems <[EMAIL PROTECTED]> writes:

> latest 2.6.25 stable release is in testing, we expect to keep it as backup
> plan for lenny.  release team wishes to have unstable coverage of 2.6.26
> before final ack on that release.

If this is the desire of Release Team, I have no problem on that.

I'd prefer to have it on experimental before upload it to unstable so
first and more urgent issues wouldn't bother us and users however this
is more up to you and RM team then me. My preference would be:

 - upload to experimental
 - wait for at least 5 days without issues
 - check for any possible building issues with new libc headers
 - upload to sid (since it has been proven more or less stable) 

When uploading to sid, I believe that meta packages should go together
so we do get a nice coverage on that.

After sometime on sid, I believe we ought to move d-i for it if it
looks to be a real option for lenny and try to release a first RC of
installer as soon as possible after that.

Thank you by coordinating it with us.

- -- 
O T A V I OS A L V A D O R
- -
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
- -
"Microsoft sells you Windows ... Linux gives
 you the whole house."
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iEYEARECAAYFAkiHHbsACgkQLqiZQEml+FVv8wCcC66i++16PPZ/Rhuy5FUZ+zfK
z9sAn2HgW44ekPTKJIdvmq3sa1M4WMVg
=ZRaN
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

please unblock rdate/1:1.1.3-2

[Aníbal Monsalve Salazar]

Otavio please approve rdate/1:1.1.3-2

Release team please unblock it.

Changes: 
 rdate (1:1.1.3-2) unstable; urgency=low
 .
   [ Jérémy Bobbio ]
   * When "-vv" is specified, rdate now displays a dot each time it tries
 to send a packet to the NTP server.  This is needed to implement
 cancelation of time synchronisation in the debian-installer.
 Closes: 491540.
 .
   [ Anibal Monsalve Salazar ]
   * Standards-Version is 3.8.0


signature.asc
Description: Digital signature

Re: Mozilla in Lenny

[Josselin Mouette]

Le mercredi 23 juillet 2008 à 07:57 +0200, Mike Hommey a écrit :
> (I may have forgotten some others, if you can think of some, please
> followup. I'll also do that myself if I remember something important)

For epiphany, blockers are the following:
  * #393837 which was flagged critical by the security team. It has
been here for a long while and should probably be fixed on the
gtkmozembed side, but it’s just a wild guess. We badly need HELP
from someone with knowledge of the chrome internals to fix it.
  * #486744 which is on the top list of crashes reported to GNOME
bugzilla.

Cheers,
-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: please unblock reportbug-ng

[Pierre Habouzit]

On Wed, Jul 23, 2008 at 10:19:23AM +, Bastian Venthur wrote:
> Pierre Habouzit wrote:
> > On Tue, Jul 22, 2008 at 04:51:08PM +, Bastian Venthur wrote:
> >> Hi,
> >>
> >> reportbug-ng now supports /usr/share/bug/*/script and sends the output
> >> if the file is available. The lack of this feature rendered rng unfit
> >> for release in the eyes of the release team, since it's implemented now
> >> I think rng should enter testing again.
> > 
> > Does it supports presubjs and helps the user choosing a proper severity
> > for bugs he reports ?
> 
> It does not show presubjs.

  This is a major stopper.

> What do you mean by helping to choose a proper severity? The default
> severity is "normal" and the "what is this" help of the box where you
> can select the severity explains every severity in detail.

  There is an RC bug about that (or at least the RM team consider it a
blocker) where there is really sensible explanations on why this is not
a good UI and that it leads to bad bug reports.

  So no, I don't think we will lift the block right now.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpRiBoTsKE7z.pgp
Description: PGP signature

Re: please unblock libidn/1.9-1

[Aníbal Monsalve Salazar]

On Mon, Jul 21, 2008 at 10:23:31AM +1000, Anibal Monsalve Salazar wrote:
>Please unblock libidn/1.9-1
>
>It uses an upstream released tarball with a fix for the RC bug 484093
>
>It has been in unstable for 10 days


signature.asc
Description: Digital signature

Re: please unblock reportbug-ng

[Josselin Mouette]

Le mardi 22 juillet 2008 à 18:51 +0200, Bastian Venthur a écrit :
> reportbug-ng now supports /usr/share/bug/*/script and sends the output
> if the file is available. The lack of this feature rendered rng unfit
> for release in the eyes of the release team, since it's implemented now

Does it support /usr/share/bug/*/control files now ?

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: New release of uw-imap prepared and uploaded to experimental

[Jonas Smedegaard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jul 22, 2008 at 09:24:46PM +0100, Adeodato Simó wrote:
>In case you weren't aware, you need to *tell* the release team you've 
>gone forward if you want your transition managed in any way.

Thanks for clarifying.

I got no feedback (before now), and thought that perhaps your new 
package blocking mechanisms made it less relevant for you to 
coordinate each specific package transition.  So I went on and uploaded 
to unstable...

I am not writing this to excuse myself - I know that you must be busy 
these days, and I should of course have had more (but how much?) 
patience.

I write it more to help give you a hint on how a package maintainer 
might react (correct or not) on not getting a response on email sent to 
your list.


>binNMUs scheduled now.

Thanks!


And thanks for all the other work you do, especially this close to the 
release!


  - Jonas

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

  - Enden er nær: http://www.shibumi.org/eoti.htm
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiHCY0ACgkQn7DbMsAkQLg//ACfaspx/dj+O6uIeFDDsEWpoCft
8NsAoJrZ3XACIktek9VnNO5iB39Es1BK
=CS4O
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: please unblock reportbug-ng

[Bastian Venthur]

Pierre Habouzit wrote:
> On Tue, Jul 22, 2008 at 04:51:08PM +, Bastian Venthur wrote:
>> Hi,
>>
>> reportbug-ng now supports /usr/share/bug/*/script and sends the output
>> if the file is available. The lack of this feature rendered rng unfit
>> for release in the eyes of the release team, since it's implemented now
>> I think rng should enter testing again.
> 
> Does it supports presubjs and helps the user choosing a proper severity
> for bugs he reports ?

It does not show presubjs.

What do you mean by helping to choose a proper severity? The default
severity is "normal" and the "what is this" help of the box where you
can select the severity explains every severity in detail.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Give back octave3.0 on sparc

[Rafael Laboissiere]

Please, give back octave3.0/3.0.1-6 on sparc.  The autobuild failed with a
cryptic message [1]:

g++ -c  -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc 
-DHAVE_CONFIG_H -Wall -W -Wshadow -Wold-style-cast -O2 -g 
./DLD-FUNCTIONS/fft2.cc -o pic/fft2.o
/tmp/cc3m4XSW.s: Assembler messages:
/tmp/cc3m4XSW.s:114060: Error: Unknown opcode: `byte'

Version 3.0.1-5 of the package built fine on sparc [2] and both the g++
compiler version (4.3_4.3.1-6) and the fft2.cc file were the same in the
octave3.0_3.0.1-6 autobuild.  I suspect htis may be some random problem with
the autobuilder machine.

[1] 
http://buildd.debian.org/fetch.cgi?pkg=octave3.0;ver=1%3A3.0.1-6;arch=sparc;stamp=1215864408
[2] 
http://buildd.debian.org/fetch.cgi?pkg=octave3.0;ver=1%3A3.0.1-5;arch=sparc;stamp=1215566151

Thanks in advance,

-- 
Rafael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]