Hello,
the release notes need to contain a note to users using the german
locale along the lines:
The Debian Project apologies for the unfortunate german quoting on the
command line interface. A solution is worked on, but unfortunately
hasn't made it into Sarge. As a workaround, switching to a
Helge Kreutzmann [EMAIL PROTECTED] writes:
The Debian Project apologies for the unfortunate german quoting on the
command line interface. A solution is worked on, but unfortunately
hasn't made it into Sarge. As a workaround, switching to a UTF-8 based
locale will avoid the problem.
Um, why
Hello
dia2code has now been uploaded (again). Hope this really fix the
problem.
Regards,
// Ola
On Mon, Aug 30, 2004 at 04:02:36PM -0700, Thomas Bushnell BSG wrote:
For a while I've been tracking the sarge inclusion of QA-managed
packages. Here is a status report. Some of you are getting
On Tue, Aug 31, 2004 at 12:26:28PM +0200, you wrote:
A) Using the same quotes as in english, i.e.,
Once again, the english quotes are also stupid:
mv -iv foo bar
`foo' - `bar'
It is not clear why german users are the only ones who need an apology
because they get stupid-looking quotes.
The following packages should be removed from testing on RoM:
rrdcollect (see #267585)
omlcs (see #269192)
xsim (see #267291)
removal requests filed for unstable
(but perhaps we want to remove them from testing faster)
vis5d
talksoup
Gruesse,
--
Frank Lichtenheld [EMAIL PROTECTED]
www:
* Thomas Bushnell BSG ([EMAIL PROTECTED]) [040831 12:55]:
Helge Kreutzmann [EMAIL PROTECTED] writes:
The Debian Project apologies for the unfortunate german quoting on the
command line interface. A solution is worked on, but unfortunately
hasn't made it into Sarge. As a workaround,
On Tue, Aug 31, 2004 at 12:26:28PM +0200, Helge Kreutzmann wrote:
the release notes need to contain a note to users using the german
locale along the lines:
The contact address for the release notes is
[EMAIL PROTECTED]
--
Colin Watson [EMAIL PROTECTED]
Hi.
AFAICT the only thing nagios and nagios-plugins need to migrate to
testing is hinting them together in.
Gruesse,
--
Frank Lichtenheld [EMAIL PROTECTED]
www: http://www.djpig.de/
* Michael Stone [EMAIL PROTECTED] [2004-08-31 06:59]:
On Tue, Aug 31, 2004 at 12:26:28PM +0200, you wrote:
A) Using the same quotes as in english, i.e.,
Once again, the english quotes are also stupid:
mv -iv foo bar
`foo' - `bar'
It is not clear why german users are the only ones who need
On Tue, Aug 31, 2004 at 04:10:02PM +0200, Andreas Jochens wrote:
On 04-Aug-31 15:47, Frank Lichtenheld wrote:
On Tue, Aug 31, 2004 at 06:33:04AM -0700, Debian Bug Tracking System wrote:
severity 262236 serious
Bug#262236: apsfilter: FTBFS: Please replace 'exim' with 'exim4' in
severity 262236 normal
thanks
On Tue, Aug 31, 2004 at 04:17:00PM +0200, Frank Lichtenheld wrote:
On Tue, Aug 31, 2004 at 04:10:02PM +0200, Andreas Jochens wrote:
Maybe I am misinterpreting something, but in
http://release.debian.org/sarge_rc_policy.txt
it says:
Release
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 12:26:28PM +0200, you wrote:
A) Using the same quotes as in english, i.e.,
Once again, the english quotes are also stupid:
mv -iv foo bar
`foo' - `bar'
It is not clear why german users are the only ones who need an apology
On 04-Aug-31 15:25, Colin Watson wrote:
Normally, build daemons have a package that provides
mail-transport-agent already installed; ssmtp is the usual choice.
Andreas, I suggest you configure your build daemon this way. I don't
think this is RC for sarge.
Thank you for the clarification
Package: tetex-bin
Version: 2.0.2-20
Severity: important
Hello,
I have just made a woody to sarge upgrade. At this point
it is not possible to remove dvipdfm:
meli# apt-get remove dvipdfm
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
hi :)
On Mon, Aug 30, 2004 at 11:30:20AM -0700, Steve Langasek wrote:
No, qt needs to be in sync on all architectures first. Currently, we're
only waiting on an upload of the m68k build.
Does anyone know what's the matter with the arm build?
All 3.3 versions failed for various reasons.
The
On Tue, Aug 31, 2004 at 04:59:05PM +0200, Mario Lang wrote:
Michael Stone [EMAIL PROTECTED] writes:
Once again, the english quotes are also stupid:
mv -iv foo bar
`foo' - `bar'
It is not clear why german users are the only ones who need an apology
because they get stupid-looking quotes.
On 2004-08-31 Martin Waitz [EMAIL PROTECTED] wrote:
On Mon, Aug 30, 2004 at 11:30:20AM -0700, Steve Langasek wrote:
No, qt needs to be in sync on all architectures first. Currently, we're
only waiting on an upload of the m68k build.
Does anyone know what's the matter with the arm build?
At Tue, 31 Aug 2004 12:26:28 +0200,
Helge Kreutzmann wrote:
The Debian Project apologies for the unfortunate german quoting on the
command line interface. A solution is worked on, but unfortunately
hasn't made it into Sarge. As a workaround, switching to a UTF-8 based
locale will avoid the
Andreas Barth [EMAIL PROTECTED] writes:
It's hardly a workaround--it seems to me that we should encourage
UTF-8 wherever we can. So we do support German, we even support it
correctly, with correct quoting, and the way to get it is to turn on
the UTF-8 based locale.
In my opinion, this
Andreas Jochens [EMAIL PROTECTED] writes:
What would be the correct bug severity for 'Arch: all' packages which do
not autobuild because of missing or incorrect Build-Depends?
My understanding is that these are release critical bugs according to
the published release criteria, if they are
Daniel Burrows [EMAIL PROTECTED] writes:
I just noticed a mail in the debian-release archive regarding noteedit.
I'm glad to know someone else is keeping an eye on this.
That was me. :)
The situation with noteedit is that it's frozen out of sarge by KDE. I
have uploaded 2.7.1-1 to
On Mon, Aug 30, 2004 at 04:02:36PM -0700, Thomas Bushnell BSG wrote:
The noteedit package is waiting on four autobuilds, but also on
kdelibs, which has release critical bugs. This is presumable the KDE
3.3 problem. However, the new version should get in (at least one of
the 2.7.1 packages,
On Tue, Aug 31, 2004 at 01:30:53PM +0200, Frank Lichtenheld wrote:
AFAICT these two removals seems not to have worked or the packages
propagated back to testing...
# 20040823; done 20040824
remove libapache-mod-dtcl/1.0.1-2
remove oftc-hybrid/1.1.1-4
Re-hinted. No idea how they got back
Bill Allombert [EMAIL PROTECTED] wrote:
Package: tetex-bin
Version: 2.0.2-20
Severity: important
Hello,
I have just made a woody to sarge upgrade. At this point
it is not possible to remove dvipdfm
[...]
Since this affect the sarge release, I have X-D-CC: debian-release.
It seems we are
On Tue, Aug 31, 2004 at 01:58:36PM +0200, Frank Lichtenheld wrote:
The following packages should be removed from testing on RoM:
rrdcollect (see #267585)
omlcs (see #269192)
xsim (see #267291)
removal requests filed for unstable
(but perhaps we want to remove them from testing faster)
On Tue, Aug 31, 2004 at 02:58:26PM +0200, Frank Lichtenheld wrote:
AFAICT the only thing nagios and nagios-plugins need to migrate to
testing is hinting them together in.
Hinted.
Thanks,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
Daniel Burrows [EMAIL PROTECTED] writes:
Do you have a strategy for fixing the problems, or in your judgment
would it be better to just drop noteedit from sarge?
I don't think I can fix the problems myself -- they look to me like
problems in the various buildds/archs (for instance, it
It's not good idea to enforce your opinion to the release
announcements because even some German guys do not think it's
acceptable currently.
Can you give some pointers to this? If you follow the long bug report
[1], you'll see that there is agreement that the current ,, quoting is
by far
On Tue, Aug 31, 2004 at 08:28:14PM +0200, Mario Lang wrote:
It feels to me as if you are intentionally failing to get my point.
Likewise. :)
I have no problems reading ``this'' as double quotes, but ,,this is just
a double comma.
Well, `` isn't a double quote any more than ,, is--it's a
Jens Nachtigall [EMAIL PROTECTED] writes:
Can you give some pointers to this? If you follow the long bug report
[1], you'll see that there is agreement that the current ,, quoting is
by far the worst transliteration. 2 opinions stated that the
transliteration towards »« might be
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 08:28:14PM +0200, Mario Lang wrote:
It feels to me as if you are intentionally failing to get my point.
Likewise. :)
I have no problems reading ``this'' as double quotes, but ,,this is just
a double comma.
Well, `` isn't a
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 04:59:05PM +0200, Mario Lang wrote:
Michael Stone [EMAIL PROTECTED] writes:
Once again, the english quotes are also stupid:
mv -iv foo bar
`foo' - `bar'
It is not clear why german users are the only ones who need an apology
Mario Lang [EMAIL PROTECTED] writes:
It feels to me as if you are intentionally failing to get my point.
I have no problems reading ``this'' as double quotes, but ,,this is just
a double comma.
Can you explain the difference? Both seem ugly to me. Though:
,,this is inconsistent. It should
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 12:35:58PM -0700, Thomas Bushnell BSG wrote:
No apology is necessary, because of (1).
No apology is necessary because it's a ridiculous concept.
Are you just trying to make it as difficult as possible to solve the
problem? If
Michael Stone [EMAIL PROTECTED] writes:
No, I'm aghast that the concept of including an *apology* in the release
notes for a typographical ugliness is being given any consideration at
all. Talking about solutions is fine, but singling something like this
out for an apology is ludicrous.
Michael Stone [EMAIL PROTECTED] writes:
Don't be an ass. I replied with a real technical reason why you might
not want hordes of people switching to UTF-8 and you suggest *that* as a
reasonable response? I had thought better of you.
Actually that's not a real technical reason. If you could
On Tue, Aug 31, 2004 at 01:33:00PM -0700, Thomas Bushnell BSG wrote:
Are you just trying to make it as difficult as possible to solve the
problem?
No, I'm aghast that the concept of including an *apology* in the release
notes for a typographical ugliness is being given any consideration at
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 02:09:36PM -0700, Thomas Bushnell BSG wrote:
Are you willing to compromise?
What is there for me to compromise about? I pointed out a potential
*technical* problem with your proposal and you jumped all over me and
suggested
Michael Stone [EMAIL PROTECTED] writes:
I didn't say it did. I pointed to a potential problem. For all I know,
in an exclusively german context UTF-8 won't cause problems at all. What
I did say is that full multibyte compliance isn't guaranteed.
So how about a release note that describes the
Thomas Bushnell BSG wrote:
The XXX locale for German unfortunately uses a bad way of
representing open quotation marks. We have retained it this way in
order to preserve compatibility with other Linux distributions, and
we hope that in the future it will be fixed. Meanwhile, the YYY
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 02:29:21PM -0700, Thomas Bushnell BSG wrote:
But the problem here is that you seem totally unable to seek
compromise. I'll try again.
Good grief, this isn't personal. Maybe you should just relax and come
back tomorrow.
I
Roland Bauerschmidt [EMAIL PROTECTED] writes:
Thomas Bushnell BSG wrote:
The XXX locale for German unfortunately uses a bad way of
representing open quotation marks. We have retained it this way in
order to preserve compatibility with other Linux distributions, and
we hope that
On Tue, Aug 31, 2004 at 02:14:48PM -0700, Thomas Bushnell BSG wrote:
Actually that's not a real technical reason. If you could point to
a package with a bug that would be a serious problem if people used
UTF-8, then that would be a real technical reason. But saying it
isn't required for sarge
On Tue, Aug 31, 2004 at 02:29:21PM -0700, Thomas Bushnell BSG wrote:
But the problem here is that you seem totally unable to seek
compromise. I'll try again.
Good grief, this isn't personal. Maybe you should just relax and come
back tomorrow.
Mike Stone
Michael Stone [EMAIL PROTECTED] writes:
On Tue, Aug 31, 2004 at 02:36:25PM -0700, Thomas Bushnell BSG wrote:
I agree that an apology isn't necessary, but *some* kind of advice,
given that sarge will be *removing* support for a large class of users,
That's not true. Something is changing,
On Tue, Aug 31, 2004 at 02:36:25PM -0700, Thomas Bushnell BSG wrote:
I agree that an apology isn't necessary, but *some* kind of advice,
given that sarge will be *removing* support for a large class of users,
That's not true. Something is changing, arguably for the worse. Nobody
is being
On Tue, Aug 31, 2004 at 03:21:05PM -0700, Thomas Bushnell BSG wrote:
Perhaps you could write down some of the more frequent problems that
users with UTF-8 might expect to see
No. I have no interest in this problem and don't care to work with you.
I've reassigned the coreutils bug to libc6 and
47 matches
Mail list logo
