Re: Someone with access to non-i386 architecture needed.
On Thu, Jun 10, 2004 at 12:11:58AM +0200, Bartosz Fenski aka fEnIo wrote: > I prepared package of imgseek for Debian (it's now in unstable), but > unfortunatelly it fails to build on every non-i386 architecture. > > I tested it with pbuilder on my i386 box, but seems that it's not > enough. It works fine in pbuilder but unfortunatelly it doesn't work at > buildd. > > I don't have access to non-i386 archs (well I have but without Debian), > so I can't make further tests. You can reproduce the problem on i386 with dpkg-buildpackage -B. -- - mdz
Request for sponsor
Greetings, i am looking for sponsor for this package. Source: yaffa-alpha Package: yaffa-alpha Version: 0.9-1 Section: net Priority: optional Upstream Authors: Magnus Ekdahl, Joacim Häggmark, Anton Persson, Johan Thim. [EMAIL PROTECTED] Maintainer: Mark Wilson <[EMAIL PROTECTED]> Standards-Version: 3.6.0 Build-Depends: debhelper (>= 4.0.0), libgtk1.2-dev (>= 1.2.0), libreadline4-dev Description: YAFFA, or Yet Another F* FTP Application is a filemanager and a FTP client with support for secure FTP. It includes a GTK front end, and console mode, this version also includes http support. The development is still going on, and version 1.0 will be released sometime this summer. I am in contact with upstream developers, they have no problems with packaging. Licence: GNU General Public License The package is lintian clean, except the following : yaffa-alpha: binary-without-manpage yaffa_askpass (I will contact authors about this). Package available from: http://members.aon.at/wilswilson Any help/suggestions very welcome. Regards Wils
Re: Request for sponsor
On Thu, Jun 10, 2004 at 02:33:44PM +0200, Mark Wilson wrote:
> Greetings, i am looking for sponsor for this package.
[...]
> The package is lintian clean, except the following :
> yaffa-alpha: binary-without-manpage yaffa_askpass
> (I will contact authors about this).
You should probably write this manual yourself and send them. They
probably won't write it themself cause they don't need it ;)
> Package available from: http://members.aon.at/wilswilson
>
> Any help/suggestions very welcome.
Here goes my suggestions:
debian/*:
- Please remove those templates (*.ex files) if you don't use them.
debian/changelog:
- You should fill ITP bug first and then close it with your changelog entry
(http://www.debian.org/devel/wnpp/)
- Why do you want to call this package yaffa-alpha? Simple yaffa would
be enough imho. You can include word alpha in version number if you
really want to show users that it is still alpha.
debian/control:
- The newest Standard-Version is 3.6.1, you should bump your version.
- Short description should not include name of application.
- Remove ${misc:Depends} cause you don't use it.
- Add autotools-dev if you use configure.(sub|guess) in your rules file.
- That's not necesarry but please include URL to homepage in description.
debian/copyright:
- Copyrights belongs to authors and not to license.
http://lists.debian.org/debian-devel/2004/debian-devel-200403/msg02190.html
debian/dirs:
- Are you sure you need both of those directories?
debian/menu.ex:
- You probably want to use it so rename it to menu and adjust.
debian/rules:
- Make it look as your rules and not template. Remove unneded comments
and dh_*'s
That's all for now ;)
I hope it'll help you somehow.
regards
fEnIo
--
_ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 |
IRC:fEnIo
_|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska
(0 0) phone:+48602383548 | Slackware - the weakest link
ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001
signature.asc
Description: Digital signature
Re: Request for sponsor
Mark Wilson <[EMAIL PROTECTED]> writes: > Greetings, i am looking for sponsor for this package. > > Source: yaffa-alpha > Package: yaffa-alpha > Version: 0.9-1 > Section: net > Priority: optional > Upstream Authors: Magnus Ekdahl, Joacim Häggmark, Anton Persson, Johan Thim. > [EMAIL PROTECTED] > Maintainer: Mark Wilson <[EMAIL PROTECTED]> > Standards-Version: 3.6.0 > Build-Depends: debhelper (>= 4.0.0), libgtk1.2-dev (>= 1.2.0), > libreadline4-dev > > Description: YAFFA, or Yet Another F* FTP Application is a filemanager > and a FTP client with support for secure FTP. It includes a GTK front > end, and console mode, this version also includes http support. > The development is still going on, and version 1.0 will be released > sometime this summer. > > I am in contact with upstream developers, they have no problems with > packaging. > Licence: GNU General Public License > > The package is lintian clean, except the following : > yaffa-alpha: binary-without-manpage yaffa_askpass > (I will contact authors about this). > > Package available from: http://members.aon.at/wilswilson > > Any help/suggestions very welcome. > > Regards > >Wils SSL support? FXP support? MfG Goswin
Re: Someone with access to non-i386 architecture needed.
Hallo Bartosz, * Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> [2004-06-10 15:22]: [...] > I don't have access to non-i386 archs (well I have but without Debian), > so I can't make further tests. Something like Knoppix available? regards nico -- Nico Golde - [EMAIL PROTECTED] [EMAIL PROTECTED] | [EMAIL PROTECTED] | http://www.ngolde.de GPG: FF46 E565 5CC1 E2E5 3F69 C739 1D87 E549 7364 7CFF Is there life after /sbin/halt -p? pgpZBnf7FHkqE.pgp Description: PGP signature
Re: Request for sponsor
Hallo Mark, * Mark Wilson <[EMAIL PROTECTED]> [2004-06-10 15:22]: > Greetings, i am looking for sponsor for this package. [...] > I am in contact with upstream developers, they have no problems with > packaging. > Licence: GNU General Public License > > The package is lintian clean, except the following : > yaffa-alpha: binary-without-manpage yaffa_askpass > (I will contact authors about this). > > Package available from: http://members.aon.at/wilswilson > > Any help/suggestions very welcome. i have no time to check the package, but you have to build the package once again, if there is a manpage available. a debian package without a manpage is a bug, every program in debian have to include a manpage. regards nico -- Nico Golde - [EMAIL PROTECTED] [EMAIL PROTECTED] | [EMAIL PROTECTED] | http://www.ngolde.de GPG: FF46 E565 5CC1 E2E5 3F69 C739 1D87 E549 7364 7CFF Is there life after /sbin/halt -p? pgp6Q9TRGQjwH.pgp Description: PGP signature
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Mon, Jun 07, 2004 at 12:56:50PM +0200, Andreas Metzler wrote: > On 2004-06-07 Mattia Dongili <[EMAIL PROTECTED]> wrote: > > On Tue, May 11, 2004 at 10:03:04AM +0200, Andreas Metzler wrote: > [...] > > > Personally I'd immediately change the architecture field and change it > > > back once there is a xserver for s390. - You'll probably have to > > > pester ftp-master to remove the old s390 binary, otherwise > > > xfree86-driver-synaptics will be blocked by "out of date on s390". > > > I finally opted for this solution. The package is ready to be uploaded, > > but how am I supposed to proceed now? ask for removal first and then > > upload or the opposite? > > Do both instead of waiting. There is no problem if the s390 buildd > tries to build xfree86-driver-synaptics before the binary has been > removed (and xfree86-driver-synaptics has been added to > http://buildd.debian.org/quinn-diff/Packages-arch-specific), the build > will simply fail because dpkg-buildpackage (or is it sbuild?) checks > the architecture field. sorry for being so pedantic. Today a bug has been submitted (#253616) regarding this issue. The submitter states that the control file for xfree86 states xserver-xfree86 is Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel netbsd-i386 powerpc sh3 sh4 sparc but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k mips mipsel powerpc sparc [1] so removing only s390 from the Architecture field of xfree86-driver-synaptics may not be enough, right? So the correct solution would be to only Suggest: xserver-xfree86 (>> 4.1.0) [1]: http://packages.debian.org/unstable/x11/xserver-xfree86 -- mattia :wq!
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Thu, Jun 10, 2004 at 05:09:53PM +0200, Mattia Dongili wrote: > On Mon, Jun 07, 2004 at 12:56:50PM +0200, Andreas Metzler wrote: > > On 2004-06-07 Mattia Dongili <[EMAIL PROTECTED]> wrote: > > > On Tue, May 11, 2004 at 10:03:04AM +0200, Andreas Metzler wrote: > > [...] > > > > Personally I'd immediately change the architecture field and change it > > > > back once there is a xserver for s390. - You'll probably have to > > > > pester ftp-master to remove the old s390 binary, otherwise > > > > xfree86-driver-synaptics will be blocked by "out of date on s390". > > > I finally opted for this solution. The package is ready to be uploaded, > > > but how am I supposed to proceed now? ask for removal first and then > > > upload or the opposite? > > Do both instead of waiting. There is no problem if the s390 buildd > > tries to build xfree86-driver-synaptics before the binary has been > > removed (and xfree86-driver-synaptics has been added to > > http://buildd.debian.org/quinn-diff/Packages-arch-specific), the build > > will simply fail because dpkg-buildpackage (or is it sbuild?) checks > > the architecture field. > sorry for being so pedantic. Today a bug has been submitted (#253616) > regarding this issue. The submitter states that the control file for > xfree86 states xserver-xfree86 is > Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel >netbsd-i386 powerpc sh3 sh4 sparc > but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k > mips mipsel powerpc sparc [1] > so removing only s390 from the Architecture field of > xfree86-driver-synaptics may not be enough, right? So the correct > solution would be to only Suggest: xserver-xfree86 (>> 4.1.0) No, the correct solution is to ensure the xfree86-driver-synaptics package isn't built on architectures where it's known to be useless. Has this package been added to the packages-architecture-specific list for the autobuilders? If not, it's my understanding that it should be; and then the package that's already been built on s390 should be removed. The other architectures in the xfree86 control file can be ignored -- they don't have autobuilders that are uploading to the archive. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Someone with access to non-i386 architecture needed.
On Thu, Jun 10, 2004 at 04:16:28PM +0200, Nico Golde wrote: > [...] > > I don't have access to non-i386 archs (well I have but without Debian), > > so I can't make further tests. > > Something like Knoppix available? Sure I know what Knoppix is but unfortunatelly the only non-i386 machine which I have access to is over 100km from me... so I can't boot it this way ;) Anyway problem has been solved with the help of this mailing list. That was silly mistake overlooked by me. Thanks once again for every comments. regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On 2004-06-10 Mattia Dongili <[EMAIL PROTECTED]> wrote: [...] > xfree86 states xserver-xfree86 is > Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel >netbsd-i386 powerpc sh3 sh4 sparc > but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k > mips mipsel powerpc sparc [1] > so removing only s390 from the Architecture field of > xfree86-driver-synaptics may not be enough, right? [...] The other archs (hurd-i386, netbsd-i386, sh3, sh4) are not releasable and ignored for testing migration. cu andreas -- "See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in "Snow Crash"
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Thu, Jun 10, 2004 at 10:20:58AM -0500, Steve Langasek wrote: > On Thu, Jun 10, 2004 at 05:09:53PM +0200, Mattia Dongili wrote: [...] > > sorry for being so pedantic. Today a bug has been submitted (#253616) > > regarding this issue. The submitter states that the control file for > > xfree86 states xserver-xfree86 is > > Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel > >netbsd-i386 powerpc sh3 sh4 sparc > > > but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k > > mips mipsel powerpc sparc [1] > > > so removing only s390 from the Architecture field of > > xfree86-driver-synaptics may not be enough, right? So the correct > > solution would be to only Suggest: xserver-xfree86 (>> 4.1.0) > > No, the correct solution is to ensure the xfree86-driver-synaptics > package isn't built on architectures where it's known to be useless. I understand this. [...] > The other architectures in the xfree86 control file can be ignored -- > they don't have autobuilders that are uploading to the archive. ok. My question was mainly due to the fact that I wasn't aware of the fact that some architectures are ignored. I was worried by the fact a missing xserver-xfree86 on let's say amd64 would raise the same problem I'm having here with s390. I hope I've been clearer, thanks :) -- mattia :wq! signature.asc Description: Digital signature
RFS: libparagui1.0 - a real crossplatform widget set based on SDL
Hello. Usualy Aurelien Jarno was uploading this package for me, but unfortunatelly he don't respond for my mails. I would really want to see this package uploaded. It will hopefully fix FTBFS[1] on s390 architecture and will allow me to fix another bug[2] with the game which utilizes this library. I have sponsor for that game. It's Joe Wreschnig. But I don't want to ask him for another upload, cause he is very helpful with my other packages, and I don't want to abuse his help ;) Anyway if someone is interested in sponsoring this upload for me, then he/she can find package on my homepage[3]. Here goes rest information about this package: ParaGUI is a cross-platform high-level application framework and GUI (graphical user interface) library. ParaGUI's is completely based on the Simple DirectMedia Layer. Version: 1.0.4 Author: Alexander Pipelka <[EMAIL PROTECTED]> Homepage: http://www.paragui.org License: GPL regards fEnIo [1] - http://bugs.debian.org/248281 [2] - http://bugs.debian.org/253699 [3] - http://skawina.eu.org/paragui/ -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: Sponsor for GEthWake (Graphical PC-Switcher using Wake-ON-LAN) wanted
On Wed, 2004-06-09 at 11:34, Pavel Kustov wrote: > Hello, debian-mentors! > I am looking for a sponsor for gethwake I'm currently developing and > packaging. > > Description: > GEthWake is a graphical (GTK+ 2) tool used to send "Magic > > Wake-On-LAN" over the local network to switch on the computers. > > Current project page: > [http://linux.iatp.by/projects/gethwake/] > > The package is apt-getable from my repository: > deb http://linux.iatp.by/debian ./ > > I hope that somebody accepts my offer to place my package in the Debian > repository. > Thanks everyone. > > -- > Pavel Kustov mailto:[EMAIL PROTECTED] And where I can find the .diff.gz file? -- " In this life we are Kings or Pawns. Emperors or Fools " signature.asc Description: This is a digitally signed message part
Re: Someone with access to non-i386 architecture needed.
On Thu, Jun 10, 2004 at 12:11:58AM +0200, Bartosz Fenski aka fEnIo wrote: > I prepared package of imgseek for Debian (it's now in unstable), but > unfortunatelly it fails to build on every non-i386 architecture. > > I tested it with pbuilder on my i386 box, but seems that it's not > enough. It works fine in pbuilder but unfortunatelly it doesn't work at > buildd. > > I don't have access to non-i386 archs (well I have but without Debian), > so I can't make further tests. You can reproduce the problem on i386 with dpkg-buildpackage -B. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Request for sponsor
Greetings, i am looking for sponsor for this package. Source: yaffa-alpha Package: yaffa-alpha Version: 0.9-1 Section: net Priority: optional Upstream Authors: Magnus Ekdahl, Joacim Häggmark, Anton Persson, Johan Thim. [EMAIL PROTECTED] Maintainer: Mark Wilson <[EMAIL PROTECTED]> Standards-Version: 3.6.0 Build-Depends: debhelper (>= 4.0.0), libgtk1.2-dev (>= 1.2.0), libreadline4-dev Description: YAFFA, or Yet Another F* FTP Application is a filemanager and a FTP client with support for secure FTP. It includes a GTK front end, and console mode, this version also includes http support. The development is still going on, and version 1.0 will be released sometime this summer. I am in contact with upstream developers, they have no problems with packaging. Licence: GNU General Public License The package is lintian clean, except the following : yaffa-alpha: binary-without-manpage yaffa_askpass (I will contact authors about this). Package available from: http://members.aon.at/wilswilson Any help/suggestions very welcome. Regards Wils -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Request for sponsor
On Thu, Jun 10, 2004 at 02:33:44PM +0200, Mark Wilson wrote:
> Greetings, i am looking for sponsor for this package.
[...]
> The package is lintian clean, except the following :
> yaffa-alpha: binary-without-manpage yaffa_askpass
> (I will contact authors about this).
You should probably write this manual yourself and send them. They
probably won't write it themself cause they don't need it ;)
> Package available from: http://members.aon.at/wilswilson
>
> Any help/suggestions very welcome.
Here goes my suggestions:
debian/*:
- Please remove those templates (*.ex files) if you don't use them.
debian/changelog:
- You should fill ITP bug first and then close it with your changelog entry
(http://www.debian.org/devel/wnpp/)
- Why do you want to call this package yaffa-alpha? Simple yaffa would
be enough imho. You can include word alpha in version number if you
really want to show users that it is still alpha.
debian/control:
- The newest Standard-Version is 3.6.1, you should bump your version.
- Short description should not include name of application.
- Remove ${misc:Depends} cause you don't use it.
- Add autotools-dev if you use configure.(sub|guess) in your rules file.
- That's not necesarry but please include URL to homepage in description.
debian/copyright:
- Copyrights belongs to authors and not to license.
http://lists.debian.org/debian-devel/2004/debian-devel-200403/msg02190.html
debian/dirs:
- Are you sure you need both of those directories?
debian/menu.ex:
- You probably want to use it so rename it to menu and adjust.
debian/rules:
- Make it look as your rules and not template. Remove unneded comments
and dh_*'s
That's all for now ;)
I hope it'll help you somehow.
regards
fEnIo
--
_ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo
_|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska
(0 0) phone:+48602383548 | Slackware - the weakest link
ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001
signature.asc
Description: Digital signature
Re: Request for sponsor
Mark Wilson <[EMAIL PROTECTED]> writes: > Greetings, i am looking for sponsor for this package. > > Source: yaffa-alpha > Package: yaffa-alpha > Version: 0.9-1 > Section: net > Priority: optional > Upstream Authors: Magnus Ekdahl, Joacim Häggmark, Anton Persson, Johan Thim. > [EMAIL PROTECTED] > Maintainer: Mark Wilson <[EMAIL PROTECTED]> > Standards-Version: 3.6.0 > Build-Depends: debhelper (>= 4.0.0), libgtk1.2-dev (>= 1.2.0), > libreadline4-dev > > Description: YAFFA, or Yet Another F* FTP Application is a filemanager > and a FTP client with support for secure FTP. It includes a GTK front > end, and console mode, this version also includes http support. > The development is still going on, and version 1.0 will be released > sometime this summer. > > I am in contact with upstream developers, they have no problems with > packaging. > Licence: GNU General Public License > > The package is lintian clean, except the following : > yaffa-alpha: binary-without-manpage yaffa_askpass > (I will contact authors about this). > > Package available from: http://members.aon.at/wilswilson > > Any help/suggestions very welcome. > > Regards > >Wils SSL support? FXP support? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Someone with access to non-i386 architecture needed.
Hallo Bartosz, * Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> [2004-06-10 15:22]: [...] > I don't have access to non-i386 archs (well I have but without Debian), > so I can't make further tests. Something like Knoppix available? regards nico -- Nico Golde - [EMAIL PROTECTED] [EMAIL PROTECTED] | [EMAIL PROTECTED] | http://www.ngolde.de GPG: FF46 E565 5CC1 E2E5 3F69 C739 1D87 E549 7364 7CFF Is there life after /sbin/halt -p? pgpIcAhIcWXZd.pgp Description: PGP signature
Re: Request for sponsor
Hallo Mark, * Mark Wilson <[EMAIL PROTECTED]> [2004-06-10 15:22]: > Greetings, i am looking for sponsor for this package. [...] > I am in contact with upstream developers, they have no problems with > packaging. > Licence: GNU General Public License > > The package is lintian clean, except the following : > yaffa-alpha: binary-without-manpage yaffa_askpass > (I will contact authors about this). > > Package available from: http://members.aon.at/wilswilson > > Any help/suggestions very welcome. i have no time to check the package, but you have to build the package once again, if there is a manpage available. a debian package without a manpage is a bug, every program in debian have to include a manpage. regards nico -- Nico Golde - [EMAIL PROTECTED] [EMAIL PROTECTED] | [EMAIL PROTECTED] | http://www.ngolde.de GPG: FF46 E565 5CC1 E2E5 3F69 C739 1D87 E549 7364 7CFF Is there life after /sbin/halt -p? pgpB4Q3XsPDnH.pgp Description: PGP signature
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Mon, Jun 07, 2004 at 12:56:50PM +0200, Andreas Metzler wrote: > On 2004-06-07 Mattia Dongili <[EMAIL PROTECTED]> wrote: > > On Tue, May 11, 2004 at 10:03:04AM +0200, Andreas Metzler wrote: > [...] > > > Personally I'd immediately change the architecture field and change it > > > back once there is a xserver for s390. - You'll probably have to > > > pester ftp-master to remove the old s390 binary, otherwise > > > xfree86-driver-synaptics will be blocked by "out of date on s390". > > > I finally opted for this solution. The package is ready to be uploaded, > > but how am I supposed to proceed now? ask for removal first and then > > upload or the opposite? > > Do both instead of waiting. There is no problem if the s390 buildd > tries to build xfree86-driver-synaptics before the binary has been > removed (and xfree86-driver-synaptics has been added to > http://buildd.debian.org/quinn-diff/Packages-arch-specific), the build > will simply fail because dpkg-buildpackage (or is it sbuild?) checks > the architecture field. sorry for being so pedantic. Today a bug has been submitted (#253616) regarding this issue. The submitter states that the control file for xfree86 states xserver-xfree86 is Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel netbsd-i386 powerpc sh3 sh4 sparc but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k mips mipsel powerpc sparc [1] so removing only s390 from the Architecture field of xfree86-driver-synaptics may not be enough, right? So the correct solution would be to only Suggest: xserver-xfree86 (>> 4.1.0) [1]: http://packages.debian.org/unstable/x11/xserver-xfree86 -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Thu, Jun 10, 2004 at 05:09:53PM +0200, Mattia Dongili wrote: > On Mon, Jun 07, 2004 at 12:56:50PM +0200, Andreas Metzler wrote: > > On 2004-06-07 Mattia Dongili <[EMAIL PROTECTED]> wrote: > > > On Tue, May 11, 2004 at 10:03:04AM +0200, Andreas Metzler wrote: > > [...] > > > > Personally I'd immediately change the architecture field and change it > > > > back once there is a xserver for s390. - You'll probably have to > > > > pester ftp-master to remove the old s390 binary, otherwise > > > > xfree86-driver-synaptics will be blocked by "out of date on s390". > > > I finally opted for this solution. The package is ready to be uploaded, > > > but how am I supposed to proceed now? ask for removal first and then > > > upload or the opposite? > > Do both instead of waiting. There is no problem if the s390 buildd > > tries to build xfree86-driver-synaptics before the binary has been > > removed (and xfree86-driver-synaptics has been added to > > http://buildd.debian.org/quinn-diff/Packages-arch-specific), the build > > will simply fail because dpkg-buildpackage (or is it sbuild?) checks > > the architecture field. > sorry for being so pedantic. Today a bug has been submitted (#253616) > regarding this issue. The submitter states that the control file for > xfree86 states xserver-xfree86 is > Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel >netbsd-i386 powerpc sh3 sh4 sparc > but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k > mips mipsel powerpc sparc [1] > so removing only s390 from the Architecture field of > xfree86-driver-synaptics may not be enough, right? So the correct > solution would be to only Suggest: xserver-xfree86 (>> 4.1.0) No, the correct solution is to ensure the xfree86-driver-synaptics package isn't built on architectures where it's known to be useless. Has this package been added to the packages-architecture-specific list for the autobuilders? If not, it's my understanding that it should be; and then the package that's already been built on s390 should be removed. The other architectures in the xfree86 control file can be ignored -- they don't have autobuilders that are uploading to the archive. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Someone with access to non-i386 architecture needed.
On Thu, Jun 10, 2004 at 04:16:28PM +0200, Nico Golde wrote: > [...] > > I don't have access to non-i386 archs (well I have but without Debian), > > so I can't make further tests. > > Something like Knoppix available? Sure I know what Knoppix is but unfortunatelly the only non-i386 machine which I have access to is over 100km from me... so I can't boot it this way ;) Anyway problem has been solved with the help of this mailing list. That was silly mistake overlooked by me. Thanks once again for every comments. regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On 2004-06-10 Mattia Dongili <[EMAIL PROTECTED]> wrote: [...] > xfree86 states xserver-xfree86 is > Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel >netbsd-i386 powerpc sh3 sh4 sparc > but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k > mips mipsel powerpc sparc [1] > so removing only s390 from the Architecture field of > xfree86-driver-synaptics may not be enough, right? [...] The other archs (hurd-i386, netbsd-i386, sh3, sh4) are not releasable and ignored for testing migration. cu andreas -- "See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in "Snow Crash" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Thu, Jun 10, 2004 at 10:20:58AM -0500, Steve Langasek wrote: > On Thu, Jun 10, 2004 at 05:09:53PM +0200, Mattia Dongili wrote: [...] > > sorry for being so pedantic. Today a bug has been submitted (#253616) > > regarding this issue. The submitter states that the control file for > > xfree86 states xserver-xfree86 is > > Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel > >netbsd-i386 powerpc sh3 sh4 sparc > > > but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k > > mips mipsel powerpc sparc [1] > > > so removing only s390 from the Architecture field of > > xfree86-driver-synaptics may not be enough, right? So the correct > > solution would be to only Suggest: xserver-xfree86 (>> 4.1.0) > > No, the correct solution is to ensure the xfree86-driver-synaptics > package isn't built on architectures where it's known to be useless. I understand this. [...] > The other architectures in the xfree86 control file can be ignored -- > they don't have autobuilders that are uploading to the archive. ok. My question was mainly due to the fact that I wasn't aware of the fact that some architectures are ignored. I was worried by the fact a missing xserver-xfree86 on let's say amd64 would raise the same problem I'm having here with s390. I hope I've been clearer, thanks :) -- mattia :wq! signature.asc Description: Digital signature
RFS: libparagui1.0 - a real crossplatform widget set based on SDL
Hello. Usualy Aurelien Jarno was uploading this package for me, but unfortunatelly he don't respond for my mails. I would really want to see this package uploaded. It will hopefully fix FTBFS[1] on s390 architecture and will allow me to fix another bug[2] with the game which utilizes this library. I have sponsor for that game. It's Joe Wreschnig. But I don't want to ask him for another upload, cause he is very helpful with my other packages, and I don't want to abuse his help ;) Anyway if someone is interested in sponsoring this upload for me, then he/she can find package on my homepage[3]. Here goes rest information about this package: ParaGUI is a cross-platform high-level application framework and GUI (graphical user interface) library. ParaGUI's is completely based on the Simple DirectMedia Layer. Version: 1.0.4 Author: Alexander Pipelka <[EMAIL PROTECTED]> Homepage: http://www.paragui.org License: GPL regards fEnIo [1] - http://bugs.debian.org/248281 [2] - http://bugs.debian.org/253699 [3] - http://skawina.eu.org/paragui/ -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: Sponsor for GEthWake (Graphical PC-Switcher using Wake-ON-LAN) wanted
On Wed, 2004-06-09 at 11:34, Pavel Kustov wrote: > Hello, debian-mentors! > I am looking for a sponsor for gethwake I'm currently developing and > packaging. > > Description: > GEthWake is a graphical (GTK+ 2) tool used to send "Magic > Wake-On-LAN" over the local network to switch on the computers. > > Current project page: > [http://linux.iatp.by/projects/gethwake/] > > The package is apt-getable from my repository: > deb http://linux.iatp.by/debian ./ > > I hope that somebody accepts my offer to place my package in the Debian > repository. > Thanks everyone. > > -- > Pavel Kustov mailto:[EMAIL PROTECTED] And where I can find the .diff.gz file? -- " In this life we are Kings or Pawns. Emperors or Fools " signature.asc Description: This is a digitally signed message part
