Re: StrongARM tactics

2005-12-07 Thread Ryan Schultz
On Tuesday 06 December 2005 05:51 am, Thomas Viehmann wrote:
>+%libopenspc: i386 kfreebsd-i386  
# i386 assembler
>+%xmms-openspc: i386 kfreebsd-i386# i386 
dependency (libopenspc)
>+pcsx: i386  # i386 
assembly

I've tried to contact the maintainers (listed in the file) of the 
packages-arch-specific file for two of my packages in your patch, 
xmms-openspc and libopenspc, and have never received a response -- my sponsor 
said that the maints were very busy, so I've not mailed them since. Neither 
of these packages are going to work on non-i386 in the future, so certainly 
feel free to add them!

I'm also the maintainer of PCSX and its associated plugins, which will all 
likely go Arch: i386 in my sponsor's next upload of them. They *might* all 
build on other arches, but whether they will *work* is questionable. PCSX has 
terrifying code (to me), and I'm not sure which C routines dropping the ASM 
would reactivate, which could cause it to have even more random segfaults -- 
I have most of those on i386 fixed, but I can't test on other arches. Having 
said that, I'd prefer that it not be added to p-a-s yet, because I intend to 
somehow ensure that it works on other arches soon, and then I'll redo the 
Arch line.

Summary: please add xmms-openspc and libopenspc, but not yet pcsx or psemu-*, 
if you can.

-- 
Ryan Schultz
YOU RPN LOVE IF THEN HONK


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



Re: StrongARM tactics

2005-12-08 Thread Ryan Schultz
On Thursday 08 December 2005 04:41 am, you wrote:
> [EMAIL PROTECTED] (Aaron M. Ucko) writes:
> > Thomas Viehmann <[EMAIL PROTECTED]> writes:
> >> +pcsx: i386 # 
> >> i386 assembly
> >
> > AFAICT, this is only because its Linux/Makefile forces CPU to ix86
> > unconditionally.
>
> Write patch. At a minimum the package should be "i386 amd64". In
> general anything with "Arch: i386" should add amd64.

PCSX 1.6 does not compile with GCC4 when the ix86 flag is not specified, even 
on i386. I don't know about amd64, but my other partially-ASM (using NASM 
like PCSX) package (libopenspc) will not build on amd64, so I'm assuming that 
the same is true here -- I'll change it if someone can confirm that it will 
build and work.

-- 
Ryan Schultz
YOU RPN LOVE IF THEN HONK


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



Re: StrongARM tactics

2005-12-08 Thread Ryan Schultz
On Thursday 08 December 2005 01:44 pm, Aaron M. Ucko wrote:
> Ryan Schultz <[EMAIL PROTECTED]> writes:
> > PCSX 1.6 does not compile with GCC4 when the ix86 flag is not specified,
> > even on i386. I don't know about amd64, but my other partially-ASM (using
> > NASM like PCSX) package (libopenspc) will not build on amd64, so I'm
> > assuming that the same is true here -- I'll change it if someone can
> > confirm that it will build and work.
>
> It built on my AMD64 system with a crude patch (attached, along with
> the resulting log) that drops the CPU setting unconditionally, but I
> haven't actually tested the result -- I built it mainly because I'm a
> packrat. ;-)

I can't get a clean pdebuild[1] on i386 with that setting dropped, which seems 
unusual -- it fails during linking. I'll hack something up for the rules 
file, in any case, and contact my sponsor; I have a new upload ready anyway.

[1]
../PsxMem.o: In function `psxMemWrite8':PsxMem.c:(.text+0x530): undefined 
reference to `psxRecLUT'
../PsxMem.o: In function `psxMemWrite16':PsxMem.c:(.text+0x5b1): undefined 
reference to `psxRecLUT'
../PsxMem.o: In function `psxMemWrite32':PsxMem.c:(.text+0x656): undefined 
reference to `psxRecLUT'
:PsxMem.c:(.text+0x691): undefined reference to `psxRecLUT'
../Misc.o: In function `RecvPcsxInfo':Misc.c:(.text+0x1856): undefined 
reference to `psxRec'
../R3000A.o: In function `psxInit':R3000A.c:(.text+0x1c): undefined reference 
to `psxRec'
Gtk2Gui.o: In function `OnCpu_Ok':Gtk2Gui.c:(.text+0x1af6): undefined 
reference to `psxRec'

-- 
Ryan Schultz
YOU RPN LOVE IF THEN HONK


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



Bug#317602: ITP: xmms-openspc -- SPC file player plugin for XMMS

2005-07-09 Thread Ryan Schultz
Package: wnpp
Owner: Ryan Schultz <[EMAIL PROTECTED]>
Severity: wishlist

* Package name: xmms-openspc
  Version : 0.0.3
  Upstream Author : Zinx Verituse <[EMAIL PROTECTED]>
* URL : http://staff.xmms.org/zinx/misc/tmp
* License : GPL
  Description : SPC file player plugin for XMMS

 XMMS-OpenSPC is an XMMS plugin that allows you to play SNES audio
 files in the .spc format. This plugin can also read the id666 tags
 used by SPC files.

Note: upstream doesn't compile with gcc-4.0, and also segfaults XMMS --
the segfault is fixed in CVS but it won't autoconf for me, so I've fixed
both problems myself. CVS hasn't been touched for over a year, as well.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12-ck3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


pgpHuCd8DwFzT.pgp
Description: PGP signature


Re: (no subject)

2005-07-22 Thread Ryan Schultz
On Saturday 23 July 2005 12:07 am, [EMAIL PROTECTED] wrote:
> can u please remove the call waves from my computer please Thnk you very 
> much
Hello Shorty550,
This is debian-devel, a mailing list for developers of the Debian GNU/Linux 
system, which doesn't relate to the Windows program Callwave in any way.
Please see:

http://www.mail-archive.com/debian-devel%40lists.debian.org/msg10770.html

for instructions on removing Callwave from your computer

---
For -devel... does anyone know why this list receives so many questions about 
Callwave? A sample:

http://lists.debian.org/debian-devel/2005/06/msg01421.html
http://lists.debian.org/debian-devel/2004/08/msg00724.html
http://lists.debian.org/debian-devel/2004/08/msg00864.html
http://lists.debian.org/debian-devel/2004/08/msg01826.html
http://lists.debian.org/debian-devel/2004/08/msg00467.html
http://www.mail-archive.com/debian-devel%40lists.debian.org/msg07400.html

I mean, a -devel post is the first answer for a Google search for 'howto 
uninstall callwave'...

-- 
Ryan Schultz
-> floating point exception: divide by cucumber


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



Re: (no subject)

2005-07-23 Thread Ryan Schultz
On Saturday 23 July 2005 02:16 pm, Daniel Burrows wrote:
> On Friday 22 July 2005 10:00 pm, Ryan Schultz wrote:
> > For -devel... does anyone know why this list receives so many questions
> > about [REDACTED]?
> >
> > [long list of links into -devel archives]
>
>   Because you just told Google that we're a good source for information
> about you-know-what :P.
>
>   Daniel

Ah... crap. Well, perhaps this will secure me a future job in SEO :- D

-- 
Ryan Schultz
-> floating point exception: divide by cucumber


pgpef3UZMC8wD.pgp
Description: PGP signature


Re: New appearance of bugs on BTS web pages

2005-08-13 Thread Ryan Schultz
On Saturday 13 August 2005 11:55 am, martin f krafft wrote:
> also sprach Darren Salt <[EMAIL PROTECTED]> [2005.08.13.1537 
+0200]:
> > >>> HTML 4.01.  Is this a bug?  Should I file a bug agains the b.d.o
> > >>> psuedo
> > >>
> > >> Shouldn't it be XHTML nowadays?
> > >
> > > I personally would like to see them XHTML1.0 at least. [...]
> >
> > That or HTML 4.01; there's no real difference.
>
> HTML 4.01 is not yet deprecated, but it will be sooner or later.
> Let's just do it right now rather than expecting someone to migrate
> later. I vote for XHTML 1.1 Strict. Should be trivial in this case.

This W3C validation page[1] for a sample bug, setting it to enforce XHTML 1.1, 
gives 40 errors, mostly broken tags (XHTML does not like capitalized tags, 
and there are some that don't self close). The file with code to be modified 
is debbugs/cgi/bugreport.cgi. I'd like to help with this, I have some 
experience with CGI scripts and XHTML/CSS and have already started making 
fixes in bugreport.cgi. Has this bug been filed so I have somewhere to start 
dropping patches?

[1] 
http://validator.w3.org/check?uri=http%3A%2F%2Fbugs.debian.org%2Fcgi-bin%2Fbugreport.cgi%3Fbug%3D322812&charset=%28detect+automatically%29&doctype=XHTML+1.1
-- 
Ryan Schultz
-> The meek shall indeed inherit the Earth -- the rest of us will take to the 
stars.


pgpBmrMjKR0mO.pgp
Description: PGP signature


Re: New appearance of bugs on BTS web pages

2005-08-13 Thread Ryan Schultz
On Friday 12 August 2005 04:26 pm, Roberto C. Sanchez wrote:
> I just saw that the bugs viewed via the BTS webpage look much nicer.
> The cleaning up of the headers from the email messages was a
> particularly nice touch.
>
> However, I am wondering if it is a bug that the pages are not even valid
> HTML 4.01.  Is this a bug?  Should I file a bug agains the b.d.o psuedo
> package?  If so what is the appropriate severity?
>
> -Roberto

It looks like someone filed a minor bug for this yesterday: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322763

-- 
Ryan Schultz
-> The meek shall indeed inherit the Earth -- the rest of us will take to the 
stars.


pgpRmxxEyt8Ac.pgp
Description: PGP signature


Bug#329996: ITP: xmms-oggre -- ogg disk output plugin for XMMS

2005-09-24 Thread Ryan Schultz
Package: wnpp
Owner: Ryan Schultz <[EMAIL PROTECTED]>
Severity: wishlist

* Package name: xmms-oggre
  Version : 0.3
  Upstream Author : Lars Siebold <[EMAIL PROTECTED]>
* URL : http://sourceforge.net/projects/my-xmms-plugs/
* License : GPL
  Description : ogg disk output plugin for XMMS

 Oggre allows you to directly output Ogg Vorbis files from XMMS,
 in the same style as the standard Disk Writer plugin. You can
 also specify output quality. Oggre is a fast way to transcode
 all of the items in a playlist to Vorbis, or to convert a file
 type that XMMS can play into a Vorbis file for other media
 players.

Package is complete and available from:

deb http://rschultz.ath.cx/debian unstable/i386/
deb-src http://rschultz.ath.cx/debian unstable/source/

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


pgp2QVkoJGNzN.pgp
Description: PGP signature


ITP, RFH: pcsx -- Sony PlayStation emulator

2005-10-02 Thread Ryan Schultz
reopen 137355
retitle 137355 ITP: pcsx -- Sony PlayStation emulator
owner 137355 !
thanks bts, daisuki da yo

Package: wnpp
Owner: Ryan Schultz <[EMAIL PROTECTED]>
Severity: wishlist

* Package name: pcsx
  Version : 1.6f
  Upstream Authors : Ryan Schultz <[EMAIL PROTECTED]>
Linuzappz <[EMAIL PROTECTED]>
Shadow<[EMAIL PROTECTED]>
Pete Bernett  <[EMAIL PROTECTED]>
NoComp<[EMAIL PROTECTED]>
Nik3d
Akumax<[EMAIL PROTECTED]>

* URL : http://www.pcsx.net, http://rschultz.ath.cx/code.php
* License : GPL
  Description : Sony PlayStation emulator
 PCSX is an advanced PlayStation (PSX) emulator, which uses a plugin
 architecture to provide full support for all components of the PSX.
 It has full emulation support for gamepads, videos, sound, memory cards,
 and other important PSX components, and is able to play most games.
 .
 You will need to install packages providing psemu-plugin-video,
 psemu-plugin-sound, psemu-plugin-input, and psemu-plugin-drive
 in order to use PCSX.

-- Summary & Notes --

debian-legal:
   PCSX is a quagmire, legally -- many of the files are copyrighted to authors 
that are missing, etc. -- however, investigative work :- ) by Matthew Dempsky 
and Frederic Briere has helped to track down the owners of nearly all of the 
files and proper license info is available (see especially 
http://www.ngemu.com/forums/showthread.php?t=45525 as well as the earlier 
discussion in this bug). Please take a look and I'll try to clarify ownership 
on any of the files, if I can. Please CC me or the bug, as I'm not subscribed 
to -legal.

RFP and ITP (-devel and CCs):
   The program itself is also a nightmare. Upstream is busy with PCSX2, a 
PlayStation 2 emulator, and has left PCSX with just a beta release. The 
emulator code does not compile with GCC 4, due mostly to invalid lvalues -- 
which aren't easily fixed, as they're buried in uncommented #define macros. 
Most of the code is uncommented, in fact. 

   The GTK2 frontend works well, but makes bad assumptions about where it is 
running, dumps files in the directory it runs from, doesn't search any 
specific system directory for plugins, and is generally unkind. Much of this 
has been alleviated by some clever wrapper scripting by F. Briere in his 
packages, but this shouldn't be required. 

   I'm not a C or a GTK programmer (not a good one, at least), and I'm not 
familiar with system emulation. However, I'm trying to beat this program into 
shape for Debian. I've already got it to search a system directory for 
plugins (but it's a hardcoded hack at the moment) and I've made the GUI a bit 
nicer to use. I gave the lvalue problems a shot but I couldn't get them fixed 
without causing more errors, and I have a -2 to my pointer casting skills 
anyway (from being a Python programmer). The version I'm working on is called 
'pcsx-df' where 'df' is 'Debian fork' (fork is not a dirty word). I'm 
maintaining my own version until I get something less hackish to send back 
upstream. 

Enough about the code. The Debian package I'm working on is based 
primarily on the work done by F. Briere, and I've already gotten all of the 
lintian warnings squashed. You'll want to add his archive if you're using my 
package, since it still needs the psemu plugins, which I've not yet started 
working on. Additionally, they cannot be configured from the GTK2 GUI with 
the pcsx-df 1.6f codebase, because the routine that launches the 
configuration program makes location assumptions (grrr...), and I've not been 
able to find it to fix these. You'll also want to run pcsx.real, as the pcsx 
wrapper script is now partly redundant. mkdir -p ~/.pcsx/memcards before 
running pcsx.real or you'll have problems configuring.

---

   Now, some information about the where to get code and packages:

Upstream:
   http://www.pcsx.net

F. Briere's work, including the psemu plugins:
   deb http://www.fbriere.net/debian/dists/unstable psx-emu/
   deb-src http://www.fbriere.net/debian/dists/unstable psx-emu/

My (temporary) Darcs repository, better one coming soon, but you can 'get' the 
pcsx-df 1.6f source:
http://rschultz.ath.cx/cgi-bin/darcs.cgi/pcsx-df/?c=browse
darcs get http://rschultz.ath.cx/repos/pcsx-df

A snapshot of the darcs repo:
http://rschultz.ath.cx/files/pcsx-df.tar.gz

My (only marginally functional, at the moment) PCSX-df package (it is named 
pcsx, not pcsx-df)
deb http://rschultz.ath.cx/debian unstable/i386/
deb-src http://rschultz.ath.cx/debian unstable/source/

- Final Notes --

Anyone l

Bug#334809: ITP: psemu-drive-cdrmooby -- ISO plugin for PSX emulators

2005-10-19 Thread Ryan Schultz
Package: wnpp
Owner: Ryan Schultz <[EMAIL PROTECTED]>
Severity: wishlist

* Package name: ISO plugin for PSX emulators
  Version : 2.8
  Upstream Author : Mooby
* URL : http://mooby.psxfanatics.com
* License : GPL
  Description : ISO plugin for PSX emulators

 This plugin provides ISO support for PSX emulators.  With it, you can rip
 a PlayStation CD directly to your hard drive or play a CDROM image from disk.
 Images can be automatically decompressed or compressed as needed.

The version I am packaging has been modified to remove non-DFSG compliant RAR 
code. This plugin is for PCSX, see bug  #137355 for more on that. There are a 
number of other psemu plugins.

Please ignore invalid ITP numbers in the changelogs for now, if any are 
reported. I'll upload fixed versions shortly after I get all of the ITPs 
filed.

Potential sponsors: lintian/pbuilder clean packages available from:

deb http://rschultz.ath.cx/debian unstable/i386/
deb-src http://rschultz.ath.cx/debian unstable/source/

-- 
Ryan Schultz
 "Pleased to meet you, e^x," says the Differential Operator. "I'm d/dt."


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