Author: branden
Date: 2004-04-28 21:15:52 -0500 (Wed, 28 Apr 2004)
New Revision: 1339
Modified:
trunk/debian/CHANGESETS
Log:
Add item.
Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-04-28 21:22:08 UTC
Author: branden
Revision: 1336
Property Name: svn:log
New Property Value:
Reduce Fabio's middle name to an initial. Writing it out in full makes a
the last line of a changelog entry exceed 80 columns, and the Debian
archive software falsely flags uploads as NMUs if the email address used
matches a
Author: branden
Revision: 1337
Property Name: svn:log
New Property Value:
Tag 4.3.0.dfsg.1-1 release.
No problem. It was also affecting Knoppix and Kanotix and would have
been a shame if somebody popped a bootable CD in only to see that Linux didn't
even display correctly :0
You wrote:
> On Wed, Apr 28, 2004 at 03:58:31AM -0700, CE wrote:
> > I recieved an e-mail from Thomas Winis
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86
X server symlink status:
lrwxrwxrwx1 root root 20 2002-05-28 21:39 /etc/X11/X ->
/usr/bin/X11/XFree86
-rwxr-xr-x1 root root 1742316 2004-03-18 13:42 /usr/bin/X11/XFree86
/etc/X11/X target unchanged from checksum
On Wed, Apr 28, 2004 at 10:17:03PM +0200, Denis Barbier wrote:
> On Wed, Apr 28, 2004 at 04:33:29AM -0500, Branden Robinson wrote:
> > Fabio,
> >
> > As of r1325 (which was too huge a commit message to make it past the
> > mailing list filters) branches/4.3.0/sid should be all ready to go.
> >
>
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
On Sat, Apr 24, 2004 at 02:43:25PM -0700, Don Armstrong wrote:
> On Sat, 24 Apr 2004, Denis Barbier wrote:
> > When a package is reconfigured, the new debconf settings and current
> > configuration files are available, but previous debconf settings are
> > not and you cannot determine that there ha
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Processing commands for [EMAIL PROTECTED]:
> tag 207543 - fixed
Bug#207543: xserver-xfree86: [pci] add option to restrict PCI resets to one
detected device
Tags were: fixed pending upstream patch
Tags removed: fixed
> tag 216806 - fixed
Bug#216806: xserver-xfree86: [module loader] aout.h should
Processing commands for [EMAIL PROTECTED]:
> tag 207543 + fixed
Bug#207543: xserver-xfree86: [pci] add option to restrict PCI resets to one
detected device
Tags were: pending upstream patch
Tags added: fixed
> tag 216806 + fixed
Bug#216806: xserver-xfree86: [module loader] aout.h should #include
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 28 Apr 2004 22:39:05 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs after 4.3.0.dfsg.1-1 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Author: fabbione
Date: 2004-04-28 16:22:08 -0500 (Wed, 28 Apr 2004)
New Revision: 1338
Modified:
NEWS.xhtml
Log:
Add item announcing 4.3.0.dfsg.1-1 release.
Modified: NEWS.xhtml
===
--- NEWS.xhtml 2004-04-28 21:05:22 UTC (rev 13
On Wed, Apr 28, 2004 at 08:39:03PM +0200, Chipzz wrote:
> On Wed, 28 Apr 2004, Branden Robinson wrote:
> > On Wed, Apr 28, 2004 at 05:16:10PM +0200, Chipzz wrote:
> > > On Wed, 28 Apr 2004, Branden Robinson wrote:
> > > > Can you guys do a couple of things for this bug?:
> > > >
> > > > 1) Report y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 28 Apr 2004 18:55:17 +0200
Source: xfree86
Binary: libx11-6-dbg libxtst6-dbg xserver-common xlibs-static-dev libxp6-dbg
xbase-clients xlibmesa3-dbg libxtrap6-dbg xfonts-75dpi libxt6 libice6-dbg xmh
libxaw6-dbg x-dev libxv1 libx
On Wed, Apr 28, 2004 at 04:33:29AM -0500, Branden Robinson wrote:
> Fabio,
>
> As of r1325 (which was too huge a commit message to make it past the
> mailing list filters) branches/4.3.0/sid should be all ready to go.
>
> Please let me know if there is anything else you need for the release.
#24
Accepted:
lbxproxy_4.3.0.dfsg.1-1_i386.deb
to pool/main/x/xfree86/lbxproxy_4.3.0.dfsg.1-1_i386.deb
libdps-dev_4.3.0.dfsg.1-1_i386.deb
to pool/main/x/xfree86/libdps-dev_4.3.0.dfsg.1-1_i386.deb
libdps1-dbg_4.3.0.dfsg.1-1_i386.deb
to pool/main/x/xfree86/libdps1-dbg_4.3.0.dfsg.1-1_i386.deb
libdp
There are disparities between your recently accepted upload and the
override file for the following file(s):
x-window-system-dev_4.3.0.dfsg.1-1_i386.deb: package says priority is extra,
override says optional.
Either the package or the override file is incorrect. If you think
the override is co
xfree86_4.3.0.dfsg.1-1_i386.changes uploaded successfully to localhost
along with the files:
xfree86_4.3.0.dfsg.1-1.dsc
xfree86_4.3.0.dfsg.1.orig.tar.gz
xfree86_4.3.0.dfsg.1-1.diff.gz
lbxproxy_4.3.0.dfsg.1-1_i386.deb
libdps1_4.3.0.dfsg.1-1_i386.deb
libdps1-dbg_4.3.0.dfsg.1-1_i386.deb
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
xfree86_4.3.0.dfsg.1-1.diff.gz
xfree86_4.3.0.dfsg.1-1.dsc
xfree86_4.3.0.dfsg.1.orig.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .changes fi
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 246019 - help upstream
Bug#246019: jpilot: Printing the contacts doesn't honor l10n
Tags were: upstream help l10n
Tags removed: help, upstream
> # sorry about that
> tags 246
tag 207543 + fixed
tag 216806 + fixed
tag 219311 + fixed
tag 222804 + fixed
tag 224909 + fixed
tag 231589 + fixed
tag 233818 + fixed
tag 233933 + fixed
tag 234081 + fixed
tag 234575 + fixed
tag 236604 + fixed
tag 237046 + fixed
tag 238276 + fixed
tag 238340 + fixed
tag 238407 + fixed
tag 238555 + f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi ftp-masters,
On Wed, 28 Apr 2004, Debian Installer wrote:
> There are disparities between your recently accepted upload and the
> override file for the following file(s):
>
> x-window-system-dev_4.3.0.dfsg.1-1_i386.deb: package says priority is e
Author: fabbione
Date: 2004-04-28 15:13:35 -0500 (Wed, 28 Apr 2004)
New Revision: 1336
Modified:
trunk/debian/control
Log:
Short second name. Massimo does not fit within 80 colomuns in changelog
file. Avoid to NMU
Modified: trunk/debian/control
Author: fabbione
Date: 2004-04-28 16:05:22 -0500 (Wed, 28 Apr 2004)
New Revision: 1337
Added:
tags/4.3.0.dfsg.1-1/
Log:
Tag 4.3.0.dfsg.1-1 release (from rev 1334, branch)
Copied: tags/4.3.0.dfsg.1-1 (from rev 1336, branches/4.3.0/sid)
On Wed, Apr 28, 2004 at 02:38:57AM -0500, Branden Robinson wrote:
[...]
> I'd call the option and local variable "ignoreserver" instead of
> "noserver". ("noserver" could lead to thoughts like as "What? I don't
> *have* an X server? What am I doing running an X client, then?")
>
> Other than th
On Wed, 28 Apr 2004, Branden Robinson wrote:
> From: Branden Robinson <[EMAIL PROTECTED]>
> Subject: Re: Bug#240656: xserver-xfree86: 5 second lock when switching
> from console to X with XFree 4.3
>
> On Wed, Apr 28, 2004 at 05:16:10PM +0200, Chipzz wrote:
> > On Wed, 28 Apr 2004, Branden Rob
On Wed, Apr 28, 2004 at 02:34:01PM +, Andreas Metzler wrote:
> Hello,
> On http://www.logic.univie.ac.at/~ametzler/.x/FAQ.xhtml you can find an
> initial shot at conversion of the FAQ to xhtml. It validates
>
> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.logic.univie.ac.at%2F%7Eametzler
I'm looking for a kind soul to help me get X working
on my ATI Mobility Radeon 9000 IGP card in my HP
Pavilion zv5120us laptop. I'm running Debian Sid with
XFree 4.4.0 (I'd happily go back to 4.3.x if I knew
how and knew it would get my card working better).
I'm currently running X with the built
Your message dated Wed, 28 Apr 2004 12:25:10 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#246207: xserver-xfree86: [debconf] Typo in
debconf-generated XF86Config-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 245978 xserver-xfree86
Bug#245978: xli on this png file crashes entire xserver
Warning: Unknown package 'when'
Warning: Unknown package 'viewing'
Warning: Unknown package '
Processing commands for [EMAIL PROTECTED]:
> reassign 246267 xfree86
Bug#246267: xserver-xfree86: [directfb] Driver not supported.
Bug reassigned from package `xserver-xfree86' to `xfree86'.
> merge 227005 246267
Bug#227005: xfree86: build XDirectFB X server
Bug#246267: xserver-xfree86: [directfb
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> # same version of package is in sarge, so this bug is not 'specific' to sid
> -- man, how I wish people would learn how to use tags :(
> tags 245246 - sid
Bug#245246: xserver-xfre
Processing commands for [EMAIL PROTECTED]:
> tag 234535 = upstream security help
Bug#234535: xserver-xfree86: crashes when starting the GIMP and other apps with
LANG=no_NO.UTF-8
Tags were: moreinfo
Tags set to: upstream, security, help
> retitle 234535 xserver-xfree86: X server can be crashed by
On Wed, Apr 28, 2004 at 03:58:31AM -0700, CE wrote:
> I recieved an e-mail from Thomas Winischhofer regarding this
> problem. After trying a few things X was working once again,
> but with an updated sis_drv.o file from his site. I've pasted
> in the e-mail below. In shor
reassign 246267 xfree86
merge 227005 246267
thanks
On Wed, Apr 28, 2004 at 12:41:25AM -0500, Mike Mestnik wrote:
> Package: xserver-xfree86
> Version: 4.3.0-7
> Severity: wishlist
>
> There is a patch on the DirectFB page that enables Xfree86 to use the
> DirectFB lib(allready pkgd in Debian). I
On Wed, Apr 28, 2004 at 05:16:10PM +0200, Chipzz wrote:
> On Wed, 28 Apr 2004, Branden Robinson wrote:
> > Can you guys do a couple of things for this bug?:
> >
> > 1) Report your gpm configuration by mailing your /etc/gpm.conf (I think
> > that's what it's called -- I don't have it installed) to t
On Tue, Apr 27, 2004 at 03:17:29PM -0500, Michael Olson wrote:
> I'll try removing the xlibmesa-dri package and reinstalling
> xscreensaver-gl. I'll let you know when I have another crash, or in
> two weeks otherwise.
Great, thanks!
--
G. Branden Robinson| Good judgement com
tag 234535 = upstream security help
retitle 234535 xserver-xfree86: X server can be crashed by xfstt font server
(DoS attack)
severity 234535 important
thanks
On Wed, Apr 28, 2004 at 03:47:54PM +0200, Helge Hafting wrote:
> Michel Dänzer wrote:
> >On Wed, 2004-04-28 at 12:04, Helge Hafting wrote:
[debian-laptop CCed so people know not to redirect questions like this
to -x except as a very last resort.]
[I am not subscribed to -laptop.]
On Tue, Apr 27, 2004 at 03:54:43PM -0500, Diego Enrique Rodriguez wrote:
> Hi lists,
> I have a compaq laptop armada v300 with debian sarge, and I'm wanted
On Wed, Apr 28, 2004 at 06:06:20AM +0200, Fabio Massimo Di Nitto wrote:
> On Wed, 28 Apr 2004, Daniel Stone wrote:
> > Err, why not just re-define it to NO in host.def if you need to?
>
> Because host.def is generated dynamically at build time. That means apply
> 2 or 3 patches to the tree if you
Processing commands for [EMAIL PROTECTED]:
> tag 243288 + moreinfo
Bug#243288: xfree86-common: [rgb.txt] add color definition for DebianRed
Tags were: patch
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Author: branden
Date: 2004-04-28 12:15:20 -0500 (Wed, 28 Apr 2004)
New Revision: 1335
Modified:
trunk/debian/TODO
Log:
Add item.
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-04-28 16:59:16 UTC (rev 1334)
+++ trunk
tag 243288 + moreinfo
thanks
On Fri, Apr 16, 2004 at 09:11:48PM -0500, Branden Robinson wrote:
> On Tue, Apr 13, 2004 at 11:57:31PM +0200, Alexander Schmehl wrote:
> [...]
> > I didn't found the RGB value, so I took a look at the eps and xcf files
> > at http://www.debian.org/logos/ with gimp.
> >
Author: fabbione
Date: 2004-04-28 11:59:16 -0500 (Wed, 28 Apr 2004)
New Revision: 1334
Modified:
branches/4.3.0/sid/debian/changelog
Log:
Change name for the upload.
Modified: branches/4.3.0/sid/debian/changelog
===
--- branches/
Author: branden
Date: 2004-04-28 11:59:00 -0500 (Wed, 28 Apr 2004)
New Revision: 1333
Modified:
trunk/debian/TODO
Log:
Update item status.
Update Vim modeline.
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-04-28 1
Author: branden
Date: 2004-04-28 11:39:04 -0500 (Wed, 28 Apr 2004)
New Revision: 1332
Modified:
trunk/debian/CHANGESETS
Log:
Explain why we don't use CHANGESETS file to document changes in itself or
the TODO file.
Modified: trunk/debian/CHANGESETS
=
Author: branden
Date: 2004-04-28 11:36:00 -0500 (Wed, 28 Apr 2004)
New Revision: 1331
Added:
trunk/debian/CHANGESETS
Modified:
trunk/debian/TODO
Log:
Add CHANGESETS file to make package release manager's life easier.
Describe relationship between TODO and CHANGESETS file.
(cosmetic) Restru
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> # fixed in Debian X Strike Force XFree86 repository; to view, run "svn diff
> -r 1327:1328 svn://necrotic.deadbeast.net/xfree86"
> tags 242485 + pending
Bug#242485: xfree86-common
Author: branden
Date: 2004-04-28 11:22:56 -0500 (Wed, 28 Apr 2004)
New Revision: 1330
Modified:
trunk/debian/TODO
Log:
Remove completed item.
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-04-28 16:16:44 UTC (rev 13
Author: branden
Date: 2004-04-28 11:16:44 -0500 (Wed, 28 Apr 2004)
New Revision: 1329
Modified:
trunk/debian/changelog
trunk/debian/local/Xsession.d/20xfree86-common_process-args
trunk/debian/local/Xsession.d/90xfree86-common_ssh-agent
Log:
Fix shell scriptlets in Xsession.d to use shell'
Author: branden
Date: 2004-04-28 11:12:46 -0500 (Wed, 28 Apr 2004)
New Revision: 1328
Modified:
trunk/debian/changelog
trunk/debian/local/Xsession.d/30xfree86-common_xresources
Log:
Fix 30xfree86-common_xresources Xsession script to check for existence of
xrdb command before attempting to ex
On Wed, 28 Apr 2004, Branden Robinson wrote:
> From: Branden Robinson <[EMAIL PROTECTED]>
> Subject: Re: Bug#240656: (no subject)
>
> On Fri, Apr 23, 2004 at 12:13:03AM +0200, Chipzz wrote:
> > Some additional information:
> >
> > I have a ATI 3D Rage Pro, and it has the same symptoms. I'm using t
Author: branden
Date: 2004-04-28 10:46:17 -0500 (Wed, 28 Apr 2004)
New Revision: 1327
Modified:
trunk/debian/local/Xsession.d/20xfree86-common_process-args
trunk/debian/local/Xsession.d/30xfree86-common_xresources
trunk/debian/local/Xsession.d/50xfree86-common_determine-startup
trunk/d
Author: branden
Date: 2004-04-28 10:38:49 -0500 (Wed, 28 Apr 2004)
New Revision: 1326
Modified:
trunk/debian/changelog
Log:
Start new changelog entry for post-4.3.0.dfsg.1-1 release.
(Using Debian revision of "-SVN" so that there will be ample evidence of
people using builds from the trunk when
Hello,
On http://www.logic.univie.ac.at/~ametzler/.x/FAQ.xhtml you can find an
initial shot at conversion of the FAQ to xhtml. It validates
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.logic.univie.ac.at%2F%7Eametzler%2F.x%2FFAQ.xhtml
as XHTML 1.0 Strict. It could be beautified with proper
Michel Dänzer wrote:
On Wed, 2004-04-28 at 12:04, Helge Hafting wrote:
[...] the debug server froze my machine to the point where even sysrq+B
(instant boot) didn't work. I tried a couple of times, using synchronous
mounts to limit the filesystem damage. I managed to open an xterm and
type
On Wed, 2004-04-28 at 12:04, Helge Hafting wrote:
>
> [...] the debug server froze my machine to the point where even sysrq+B
> (instant boot) didn't work. I tried a couple of times, using synchronous
> mounts to limit the filesystem damage. I managed to open an xterm and
> type "gimp", but t
I recieved an e-mail from Thomas Winischhofer regarding this problem.
After trying a few things X was working once again, but with an updated
sis_drv.o file from his site. I've pasted in the e-mail below. In short the
solution seems to be to incorporate Thomas' updated driver. I'll a
On Wed, Apr 28, 2004 at 10:00:20AM +0200, Branden Robinson wrote:
> tag 245093 + moreinfo upstream
> thanks
>
> On Wed, Apr 21, 2004 at 02:27:04PM +0200, Vincent Fourmond wrote:
> > Package: xterm
> > Version: 4.3.0-7
> > Severity: normal
> >
> > Hello !
> >
> > As my zsh ctrl+left or right
On Wed, 28 Apr 2004, Branden Robinson wrote:
> Fabio,
>
> As of r1325 (which was too huge a commit message to make it past the
> mailing list filters) branches/4.3.0/sid should be all ready to go.
>
> Please let me know if there is anything else you need for the release.
Ok, i went trough the com
Branden Robinson wrote:
On Thu, Apr 22, 2004 at 02:19:01PM +0200, Michel Dänzer wrote:
On Thu, 2004-04-22 at 11:27, Helge Hafting wrote:
Branden Robinson wrote:
On Wed, Apr 21, 2004 at 01:28:00PM +0200, Helge Hafting wrote:
Branden Robinson wrote:
Core was generated by `/usr/bin/X11/X
Branden Robinson wrote:
Dear bug submitter,
Can you please get back to us about this?
One more thing. I re-tried gimp while logged in as a normal user
without xfstt in the font path. It worked, and now the
nonascii characters seems to be correct too, unlike
the test I did with startx as r
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 234025 normal
Bug#234025: xserver-xfree86: [ati/radeon] display brightness too high when X
server started with S-Video cable connected on Radeon RV200 QW [Radeon 7500]
re
Fabio,
As of r1325 (which was too huge a commit message to make it past the
mailing list filters) branches/4.3.0/sid should be all ready to go.
Please let me know if there is anything else you need for the release.
--
G. Branden Robinson| You could wire up a dead rat to a
De
1 - 100 of 134 matches
Mail list logo
