RFS: ruby-fftw3 - Ruby interface to the FFTW Ver.3 library
Dear mentors, Debian-Ruby members. Dear mentors, I am looking for a sponsor for my package ruby-fftw3. * Package name: ruby-fftw3 Version : 0.2-1 Upstream Author : Takeshi Horinouchi hourinout_(at)_gfd-dennou.org * URL : http://www.gfd-dennou.org/arch/ruby/products/ruby-fftw3/ * License : Ruby's Section : ruby It builds these binary packages: libfftw3-ruby - Ruby interface to the FFTW Ver.3 library libfftw3-ruby1.8 - Ruby FFT library using FFTW Ver.3 libfftw3-ruby1.8-dbg - Ruby FFT library using FFTW Ver.3 libfftw3-ruby1.9.1 - Ruby FFT library using FFTW Ver.3 libfftw3-ruby1.9.1-dbg - Ruby FFT library using FFTW Ver.3 The package appears to be lintian clean. The upload would fix these bugs: 546748 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/r/ruby-fftw3 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/r/ruby-fftw3/ruby-fftw3_0.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards, --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@math.kyoto-u.ac.jp Department of Mathematics, Kyoto University GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874o7wo2kv.wl%uwab...@gfd-dennou.org
RFS: bluefeather - Extended MarkDown converter
Dear mentors, Debian-Ruby members. I am looking for a sponsor for my package bluefeather. * Package name: bluefeather Version : 0.40-1 Upstream Author : Dice tetradice_(at)_gmail.com * URL : http://ruby.morphball.net/bluefeather/ * License : GPL 2 Section : ruby It builds these binary packages: bluefeather - Extended MarkDown converter The package appears to be lintian clean. The upload would fix these bugs: 590816 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/bluefeather - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/bluefeather/bluefeather_0.40-1.dsc I would be glad if someone uploaded this package for me. Kind regards, --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@math.kyoto-u.ac.jp Department of Mathematics, Kyoto University GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762sco2oh.wl%uwab...@gfd-dennou.org
Help with mantis package
Hi, i have been waiting for some time to see new 1.2.x branch package of the mantis bug tracking software in debian. I have also tried to contact responsible maintainers (as visible on the QA page) offering some help but probably some filter caought my email as no response had arrived. During last week i was trying to prepare package of the latest release (currently 1.2.4) on my own and finally today it seems to be working. I have briefly tested clean install and upgrade from the 1.1.8 version (with mysql DB) on my project and it looks working. I am completely noob to the debian packaging and development so i do not suppose it is ready for general use (i am sure i missed several important items) but i would like to offer my patch of tha package directory to someone who knows how to do it in a right way or even try to finish packaging. My goal is to see latest mantis in debian testing. As i had a bad luck sending an email to maintainers previously i would like to ask someone for help what should be my next step. Thanks for advices. Regards, Michal Navratil -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTim-G6mFSQoBD8u35TafCmQb+_O77-Y--3UpYr=y...@mail.gmail.com
Re: RFS: openteacher
On Fri, Jan 7, 2011 at 10:09 PM, Arvind S Raj sraj.arv...@gmail.com wrote: Dear mentors, I am looking for a sponsor for my package openteacher. Package name: openteacher Version : 2.0beta2-1 Upstream Author : Milan Boersmilan.bo...@gmail.com URL : http://launchpad.net/openteacher License : GPL Section : misc It builds these binary packages: openteacher - Learn words in a foreign language The package appears to be lintian clean. The upload would fix these bugs: 608163 My motivation for maintaining this package is the fact that it can be a very useful aid in learning foreign languages. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/o/openteacher - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/openteacher/openteacher_2.0beta2-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Arvind S Raj. Would anyone take a look and see if any more changes are required and if not, kindly upload it? The packaging lives here http://git.debian.org/?p=collab-maint/openteacher.git. -- Arvind S Raj
Autotools, CDBS, and handling generated files
Hi, /usr/share/doc/autotools-dev/README.Debian.gz says that the best practice for handling files generated by Autoconf, Automake, and Libtool is to generate these files during the build process and make the clean target remove them. /usr/share/doc/cdbs/cdbs-doc.html provides a facility for generating these files during the build process, but it says that use of this facility is *strongly* discouraged. What is the best practice for a package that uses CDBS? -- Matt Kraai https://ftbfs.org/kraai -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110222120148.gb17...@ftbfs.org
Re: RFS: spice-protocol - SPICE protocol headers
a small bug: $ cat debian/control | grep ^Home Homepage: http://http://www.spice-space.org/ On Sun, Feb 20, 2011 at 09:39, liang bluestonech...@gmail.com wrote: Dear mentors, I am looking for a sponsor for my package spice-protocol. * Package name : spice-protocol Version : 0.6.4-1 Upstream Author : Red Hat, Inc * URL : http://www.spice-space.org/ * License : BSD Section : libs It builds these binary packages: libspice-protocol-dev - SPICE protocol headers The package appears to be lintian clean. The upload would fix these bugs: 603697 My motivation for maintaining this package is: SPICE is an interesting desktop virtulization project, I want Debian can act as a guest or hypervisor with SPICE support. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/spice-protocol - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.6.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Liang Guo http://bluestone.cublog.cn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJNYHDAAAoJEIK1tAhowJe8KdMP/0zXzwbWx9Sm40FJOPbjb9+8 AimNaYOISecYFEftccJ1cv/tKUXehlCpPQNfNxeIVunojBV2rvlo4WlFR/qLvRQD b0P7Z9nEcuCJKou/VpzP3ymERVwYmlar18cPexF8c7pwfG2BWbAIi6eeciUORGPk VcWsoL4PTt53bxLUFZ2zFIC4IKodIMsQadENf+kyARq8QQDUwhWK3klQJCYRdXKz JtOaM8efkrPm+I4zOenAH9YxOV55Y9uOe7qwVZgGHmljqgmIXzD/eEX4bGlBWwq5 kIu/U1u7+9kCYo+tsoVJP9TZOpiTghyeI1WWcNVfS3u62SOpDIDNyG2HATRC34L0 t8iDF96twW3XXJqELzFX5BsHW86j3Y7JBkc4lYMgVAVparm9yUn8BNB7KTZubhb0 bKVxiA4TM//FnsagjDRCb3A+wAZTrldx2e2KRJhK8A0jK5CqgFznEtCordi6YTPy 5xRx7EKRJvLF0SWUx/iN63t0GvoSL7KH3C6RU+/cxwLUD7HfWBhtoeVK2/cmVZNL 4wz4omqrBafM3eRd4FiwUkFvPMv15zNvr+Dc7MqfPcoVYW5syC0qgqn5emUpj+lq jaiykEG8X7z8fCimH/TaXNHPjfjAsPbb3R7OnBGBCLmha/l+Cq1waynuWbMwZIXs FtVJ+RteSkxVJm4DgQmn =+Foo -END PGP SIGNATURE- -- Best Regards LI Daobing -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=4+7v0dykdaq-gpspkozp1v2cgwo8dsxebe...@mail.gmail.com
Re: RFS: spice-protocol - SPICE protocol headers
packager have fixed this bug and reuploaded to mentors. this package have been uploaded to ftp-master by me On Tue, Feb 22, 2011 at 22:20, LI Daobing lidaob...@gmail.com wrote: a small bug: $ cat debian/control | grep ^Home Homepage: http://http://www.spice-space.org/ On Sun, Feb 20, 2011 at 09:39, liang bluestonech...@gmail.com wrote: Dear mentors, I am looking for a sponsor for my package spice-protocol. * Package name : spice-protocol Version : 0.6.4-1 Upstream Author : Red Hat, Inc * URL : http://www.spice-space.org/ * License : BSD Section : libs It builds these binary packages: libspice-protocol-dev - SPICE protocol headers The package appears to be lintian clean. The upload would fix these bugs: 603697 My motivation for maintaining this package is: SPICE is an interesting desktop virtulization project, I want Debian can act as a guest or hypervisor with SPICE support. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/spice-protocol - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.6.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Liang Guo http://bluestone.cublog.cn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJNYHDAAAoJEIK1tAhowJe8KdMP/0zXzwbWx9Sm40FJOPbjb9+8 AimNaYOISecYFEftccJ1cv/tKUXehlCpPQNfNxeIVunojBV2rvlo4WlFR/qLvRQD b0P7Z9nEcuCJKou/VpzP3ymERVwYmlar18cPexF8c7pwfG2BWbAIi6eeciUORGPk VcWsoL4PTt53bxLUFZ2zFIC4IKodIMsQadENf+kyARq8QQDUwhWK3klQJCYRdXKz JtOaM8efkrPm+I4zOenAH9YxOV55Y9uOe7qwVZgGHmljqgmIXzD/eEX4bGlBWwq5 kIu/U1u7+9kCYo+tsoVJP9TZOpiTghyeI1WWcNVfS3u62SOpDIDNyG2HATRC34L0 t8iDF96twW3XXJqELzFX5BsHW86j3Y7JBkc4lYMgVAVparm9yUn8BNB7KTZubhb0 bKVxiA4TM//FnsagjDRCb3A+wAZTrldx2e2KRJhK8A0jK5CqgFznEtCordi6YTPy 5xRx7EKRJvLF0SWUx/iN63t0GvoSL7KH3C6RU+/cxwLUD7HfWBhtoeVK2/cmVZNL 4wz4omqrBafM3eRd4FiwUkFvPMv15zNvr+Dc7MqfPcoVYW5syC0qgqn5emUpj+lq jaiykEG8X7z8fCimH/TaXNHPjfjAsPbb3R7OnBGBCLmha/l+Cq1waynuWbMwZIXs FtVJ+RteSkxVJm4DgQmn =+Foo -END PGP SIGNATURE- -- Best Regards LI Daobing -- Best Regards LI Daobing -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTinpUkPxG=hk+jpgehpfaglujzfnca+oznisw...@mail.gmail.com
Re: RFS: mobile-broadband-provider-info (updated package)
On Mon, Feb 21, 2011 at 10:15 PM, Bhavani Shankar R bh...@ubuntu.com wrote: Reuploaded with the correct version number The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/m/mobile-broadband-provider-info/mobile-broadband-provider-info_20110218-1.dsc Built, signed and uploaded. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTintMS=YCAgkFsiiG1tbHpCQd=esubxakqrnr...@mail.gmail.com
RFS: spice-protocol - SPICE protocol headers
Dear mentors, I am looking for a sponsor for my package spice-protocol. * Package name: spice-protocol Version : 0.6.4-1 Upstream Author : Red Hat, Inc * URL : http://www.spice-space.org/ * License : BSD Section : libs It builds these binary packages: libspice-protocol-dev - SPICE protocol headers The package appears to be lintian clean. The upload would fix these bugs: 603697 My motivation for maintaining this package is: SPICE is an interesting desktop virtualization project, I want Debian can act as a guest or hypervisor with SPICE support. I made some minor change and reupload it to mentors.d.n. For it never exist in Debian, I have not increase Debian version number. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/spice-protocol - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.6.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: Autotools, CDBS, and handling generated files
Am 22.02.2011 13:01, schrieb Matt Kraai: Hi, /usr/share/doc/autotools-dev/README.Debian.gz says that the best practice for handling files generated by Autoconf, Automake, and Libtool is to generate these files during the build process and make the clean target remove them. /usr/share/doc/cdbs/cdbs-doc.html provides a facility for generating these files during the build process, but it says that use of this facility is *strongly* discouraged. What is the best practice for a package that uses CDBS? You might be interested in dh-autoreconf if you need to regenerate the build system. It ships both a dh addon and a cdbs rules file. It also can take care of cleaning up the generated files. Question is, why do you need to regenerate the build system? Are you patching configure.ac/Makefile.am? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Help with mantis package
On Tuesday 22 February 2011 03:56:45 Michal Navratil wrote: i have been waiting for some time to see new 1.2.x branch package of the mantis bug tracking software in debian. I have also tried to contact responsible maintainers (as visible on the QA page) offering some help but probably some filter caought my email as no response had arrived. During last week i was trying to prepare package of the latest release (currently 1.2.4) on my own and finally today it seems to be working. I have briefly tested clean install and upgrade from the 1.1.8 version (with mysql DB) on my project and it looks working. Prepare a source package, upload to mentors.d.n and let us know it is available. At the same time, open a wishlist bug against the existing package and attach your patch (debian/ directory only, not the changes to the upstream tarball) to the bug. After the bug is filed, start the MIA process to determine if the maintainer is really missing. At the same time, there will likely be feedback on this list about further changes you might need to make to the package. After some period of time, if the maintainer is really MIA and your packaging is acceptable, one of the helpful DDs on the list can perform an NMU to get mantis 1.2 in the archive. Alternatively, the maintainer may be around but just not concentrating on your package--if they are amicable, a friendly NMU can be done by one of the DDs on the list. Most maintainers are appreciative of extra help, as long as it is done is such a way that their efforts aren't wasted. Establishing communication or documenting attempts to do so is key. HTH PS Please correct me if any of these instruction is incorrect or otherwise ill- advised. I've not have to go through this process, so I'm speaking from a position of theory and study, not practice and action. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: RFS: xnbd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 21.02.2011 13:39, Wouter Verhelst wrote: Please talk to your upstream to get them to clarify this; and while you're at it, might want to let them know that I'm always interested in taking useful patches for vanilla nbd :-) I talked to the upstream author and he adapted my suggestions. Now the upstream source clearly exposes GPL-2+ [1] which in turn is reflected within my latest package as well. He also included my improvements for Debian (e.g. man pages). As far as my work is concerned I am still looking for a sponsor. Below I linked the new package revision, available at m.d.n. The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/x/xnbd - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/x/xnbd/xnbd_0.0.3+hg20110222-1.dsc [1] https://bitbucket.org/hirofuchi/xnbd/changeset/f981da5d3884 - -- with kind regards, Arno Töll GnuPG Key-ID: 0x8408D4C4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNZALqAAoJELBdpXvEXpo9eWEQAKrbMtHSCVksjL6Vx5JOk/3d zhATeeSvNjsfaSTJv/tkYITwJPDGn3D8H0h/XzTDxyPLwR6nXzlz61egPsPxCLvp cpHD3jwA6ubRiO4pIHcmtWxRZ1crCGFttRG3EKHEFrGXvD2VrpGMWK3VV0jw/jfu iMBnqEkaKm9MBBwrm63A0/kOlFaqMyjODmo6JWivH9SyIxUCGrweLTDQia7Shc1O FCA0b3B28pdbXO8GN/S+lXbCsaji1kaMQZRB8+6uTg/EQj4exasuAooJOhuw1Nxw P0sCbfHXtegiFAltISsWGf2m1JFARIDGrXQ9a4U6iEsl4ehGxyOJWjhCKua+w7sO vZBMRY8VF4LBqwYr/bkRynMbA/FEPhcqXdxGNd5rJvkj/G6Ac4F312WpNt0i1X3Y H52EEj5UdrBfWbtBZZiv65u4mjNokRRXMVbgUIiiYOTFn6bJ1yZ0+SId8fCTNX3U ycPJvZFgTqnPKMfevVbOtghfXQG+6GkGXyVuHtmBz9ODvlFyfTwNoGvXdTlQl8VH e4VWYyvbDgIlckCpOqXiJmavWdpwBPukNQZh35GO/kzPiVUXwUjFv6tpF686D63/ gW4v3u5mHit+c17z8XteFJEnIxcBTrN5YrQzjxBD5lTFfLpkZqNsLWGSlF/eUPjZ VIq2e7e1Mdjxswe+5pQi =jyK9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6402ea.30...@toell.net
Re: RFS: xnbd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22.02.2011 19:39, Arno Töll wrote: I talked to the upstream author and he adapted my suggestions. Now the upstream source clearly exposes GPL-2+ [1] which in turn is reflected within my latest package as well. Uhm, one thing I forgot to mention: He removed all legacy parts as well, i.e. xNBD does not share any code with your source anymore. So he is free to license the code as he wants, and he told me to prefer GPL-2+ over GPL-2. - -- mit freundlichen Grüßen, Arno Töll GnuPG Key-ID: 0x8408D4C4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNZAPFAAoJELBdpXvEXpo9gOAQAIgBgJxLULayxu+sNPGW+dre AXbN+8zKVAJFprTAWsyTvAdbIImuMLznci77r9TPNRh/ZphkqgarV5b7DqkDdmVg ONCgJZCv9A+YkSyTv2PXGsc44MTEvBJiCdGJFLjtaF6oyIDtDjoKIHAwzXH+vLlM hnsZeWKzBf9VDC00cLlJk5zNGGqNm2p1GFENFuwGWas6rlP+WZd/ats2Yc2ETgt7 bgXtDBzXGbdyABatX3Gy2uXOIamBmUYXF3AwHJANtuFU3Xj1+Tf6Jeofv/N+MZdr H4b1oGRLdiEiOmPlDsep/R3wmZOoZZB6lnbL7ewOjI7L7RMMn6P/ji5pjr7PQ+kD M24tQ0GGVxPV5Y+Oxr0zXhD8x7IghNXLeIfwOrzMEVMM3VXwuZdabzZbZtEa4JXl IoLtOzwHCLVG9z0OgglJRb6ohPuQ6TzXqdd6XUVRBIv2ILK5b0C3pxUwJJ60hNFD U+cRdkycsG00CSmdCoAMdfQ1TlTwwJFz79Bq31WoPNsScpe/1BnXxyb2nhD0LAvh BzvauUUEZc31TPcDNGRPRFaCGZHhWRgq06oHuaAfyMqWVY3+W5KRU1gbThMlJ4hC JKmdBAUci0hWoRUgMpAYqfoqtmVpdYaytM0xb9kAjubLnJnCNWVHLkqC+vnkvkUE XsrqEeZ8Nac6NQQF0Pnn =sJbT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6403c5.2000...@toell.net
${xviddriver:Provides} broken?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
I am running my own NVidia graphics package. Problem: After the most
recent upgrade of xorg the ${xviddriver:Provides} macro in the
Provides: line expands to
xserver-xorg-video-
instead of
xserver-xorg-video-6.0
or
xserver-xorg-video-8.0
How comes? Any helpful comment would be highly appreciated.
Regards
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1kEtYACgkQUTlbRTxpHjeTFQCeLZq6+ryjhovtwAqP1rVPjNyc
jX8An2QwCXoNsGUgvCMUWMtuR/tNlfHK
=a8Zb
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d6412d6.3080...@afaics.de
Re: ${xviddriver:Provides} broken?
On 2011-02-22 20:47 +0100, Harald Dunkel wrote:
Hi folks,
I am running my own NVidia graphics package. Problem: After the most
recent upgrade of xorg the ${xviddriver:Provides} macro in the
Provides: line expands to
xserver-xorg-video-
Are you using xsfbs? If so, this is probably because the
/usr/share/xserver-xorg/videoabiver file is gone.
instead of
xserver-xorg-video-6.0
or
xserver-xorg-video-8.0
How comes? Any helpful comment would be highly appreciated.
You should just provide xserver-xorg-video and not any particular ABI.
In xserver-org-dev 2:1.9.4-1 and later, dh_xsf_substvars will expand
${xviddriver:Provides} accordingly.
Regards,
Sven
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bp23rey8@turtle.gmx.de
upstream source with debian directory
Dear list members, I'm currently uploader for openswan were upstream ships it's own version of a debian directory as they provide debs themselves (no chance to change this). As the upstream source did contain non-free docs we had to repackage it anyway so removing the debian directory too was not an extra step. But now upstream has cleaned up their documentation and also removed the non-free parts so there is no need anymore to do any repacking. The problem is that when importing the upstream tar.gz with git-import-orig into the git repository the merge failes as both the upstream and the master branch now contain a debian directory. How can this problem be solved the best way? Continue the repackaging to remove the debian directory? Apply a filter to git-import-orig? Just resolve the conflicts and then continue the merge (and how)? Any help is greatly appreciated! Thanks and kind regards Harald Jenny -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2011014519.gd14...@harald-has.a-little-linux-box.at
Re: ${xviddriver:Provides} broken?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sven,
On 02/22/11 21:29, Sven Joachim wrote:
Are you using xsfbs? If so, this is probably because the
/usr/share/xserver-xorg/videoabiver file is gone.
instead of
xserver-xorg-video-6.0
or
xserver-xorg-video-8.0
How comes? Any helpful comment would be highly appreciated.
You should just provide xserver-xorg-video and not any particular ABI.
In xserver-org-dev 2:1.9.4-1 and later, dh_xsf_substvars will expand
${xviddriver:Provides} accordingly.
I have xserver-xorg-dev 2:1.9.4-3 installed, so instead of
xserver-xorg-video-
it should have set xserver-xorg-video, right? The ${xinpdriver:Provides}
seems to have the same problem.
Bug report?
Regards
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1kM+YACgkQUTlbRTxpHjfptACgiaOrbWTnRUgr117UECPR0Ihp
XgEAn14rskipCUI+u4uFd3EhnhegtBis
=dcA9
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d6433e6.1040...@afaics.de
Re: packaging a new qt application with 2 components
On Tue, 2011-02-22 at 00:23 +0100, Lars Buitinck wrote: 2011/2/22 Steven redalert.comman...@gmail.com: Yes, looking in the directory, I see a single .a file, starting with 'lib' (also the largest file in there). I guess this means it would be easiest to create 2 separate packages, while changing the *.pro file for the gui? If you want to keep them separate, that would be the easiest. If the 'kernel' is named libfoo.a, make a package called foo-dev or libfoo-dev containing it and the necessary headers, then make sure the gui package Build-Depends: on it. (No need to have it around at runtime.) Hmm.. Sounds good, I'll have a look at it. So the libfoo-dev (or foo-dev) would contain the 'kernel' and the dependency only exists when building if I understand correctly. Thus only linking to the 'kernel' instead of making a single binary. Linking to a static library (.a) in fact will produce a single binary: elements of the library are copied at link time. (You could build a shared library out of the 'kernel' library, but that's not for the faint-of-heart.) That is definitely not necessary at this time, the 'kernel' would only be used in combination with the Qt gui, although I guess I could change it later if other applications start using it. Changing the build procedures shouldn't be a problem for upstream. I'm a bit confused here. Is upstream distributing everything in a single package, or in two packages? In the former case, you'd want to build both the library (assuming it's generally useful) and the GUI from the single upstream package. In any case, there's no need for upstream to modify anything; just skip the top-level makefile in the debian/rules script using the --sourcedir argument to debhelper and point to the library in /usr/lib instead of in the source directory. Upstream doesn't distribute anything but a Windows application and the code with custom build script from SVN. I'm not sure about how this would work in practice, but I'll try to figure it out. While I see why one would use only build-depends, I'm not sure how to accomplish the compile, as the make file is generated from qmake. Or should I direct the Debian/rules file to run qmake instead of/after make? (Always willing to learn) Actually I think I should ignore the custom build script entirely for building the Debian packages, and just edit that script a bit for general *nix installs. It only executes qmake and make a couple of times with some parameters to enable debugging, the rest of the script checks the directories where to find the sources and uses 'echo' to output some information about the progress and/or failures ((q)make commands are redirected to a file, so you don't 'see' the compile process) Here is some background history on the application which might help you understand my position in this. The application was originally developed for Windows, but after some time a community member did the necessary work to make the 'kernel' (almost) compile on Linux and Mac OSX systems. He then started writing a basic Qt gui to replace the native Windows gui. Both the Windows and Linux branches exist in SVN, and so does the Qt gui. For a while nothing really happened, but there was still interest in a Linux version, I picked things up and my first patches made the whole thing compile without manually editing source files (build script did exist) I'm currently fixing translations (still some hard coded German strings in there) and doing some bugfixes. So if you look at it like this, I do have some liberty to play with the build script a bit, as long as I don't make it Debian specific so it can still compile on other systems without issue. Thank you very much for your help, I hope I'm not too much of an inconvenience with all this text. Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: ${xviddriver:Provides} broken?
On 2011-02-22 23:08 +0100, Harald Dunkel wrote:
On 02/22/11 21:29, Sven Joachim wrote:
Are you using xsfbs? If so, this is probably because the
/usr/share/xserver-xorg/videoabiver file is gone.
instead of
xserver-xorg-video-6.0
or
xserver-xorg-video-8.0
How comes? Any helpful comment would be highly appreciated.
You should just provide xserver-xorg-video and not any particular ABI.
In xserver-org-dev 2:1.9.4-1 and later, dh_xsf_substvars will expand
${xviddriver:Provides} accordingly.
I have xserver-xorg-dev 2:1.9.4-3 installed, so instead of
xserver-xorg-video-
it should have set xserver-xorg-video, right?
If you are using dh_xsf_substvars. But I suspect you don't, and
${xviddriver:Provides} gets expanded by a makefile snippet in your
source tree instead which tries to read a non-existent file.
The ${xinpdriver:Provides} seems to have the same problem.
Quite possible.
Bug report?
Not without seeing the source of your package.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87pqqjog8m@turtle.gmx.de
Re: upstream source with debian directory
If you weren't using git I would say use dpkg-source v3 which removes any upstream debian/ dir during the unpack process. With git I'm not sure but I'd be inclined to just resolve conflicts, continue the merge and maybe send upstream some patches. Now that upstream is also using git you can probably just switch from git-import-orig to git pull and pristine-tar. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimd01kbfjejcy8jgdvzov7thhvyp+prv2m_t...@mail.gmail.com
Re: packaging a new qt application with 2 components
2011/2/22 Steven redalert.comman...@gmail.com: Hmm.. Sounds good, I'll have a look at it. So the libfoo-dev (or foo-dev) would contain the 'kernel' and the dependency only exists when building if I understand correctly. [snip] That is definitely not necessary at this time, the 'kernel' would only be used in combination with the Qt gui, although I guess I could change it later if other applications start using it. You understand correctly. But I'm not sure Debian would benefit much from a -dev package that only exists to build a single other package. I'll leave it to the Debian Developers on this list to comment on that, though. Upstream doesn't distribute anything but a Windows application and the code with custom build script from SVN. But does checking out the SVN get you the entire application? Or does that require two checkouts to get both kernel and gui branches? (Long time since I last used SVN...) I'm not sure about how this would work in practice, but I'll try to figure it out. While I see why one would use only build-depends, I'm not sure how to accomplish the compile, as the make file is generated from qmake. Or should I direct the Debian/rules file to run qmake instead of/after make? (Always willing to learn) I'm not intimately familiar with the Qt build system (I've only used someone else's CMake script for Qt builds), but I believe qmake handles some magic regarding the Qt meta-object compiler. If the top-level Makefile is also generated from qmake, I'd try to get debian/rules to execute qmake. Again, someone else may have more experience with this. Actually I think I should ignore the custom build script entirely for building the Debian packages, and just edit that script a bit for general *nix installs. It only executes qmake and make a couple of times with some parameters to enable debugging, the rest of the script checks the directories where to find the sources and uses 'echo' to output some information about the progress and/or failures ((q)make commands are redirected to a file, so you don't 'see' the compile process) The more automated the build is, the easier the Debian packaging, as long as some parameters such as installation dir can be set without too much of a hassle. Do realise that if you make a debian/rules that bypasses large parts of the upstream build system, you're going to have to maintain it. If you can get upstream to maintain a generic Unix build script that is fit to be called from debian/rules, it saves work, even if it means you get to maintain it for them. The application was originally developed for Windows, but after some time a community member did the necessary work to make the 'kernel' (almost) compile on Linux and Mac OSX systems. He then started writing a basic Qt gui to replace the native Windows gui. Both the Windows and Linux branches exist in SVN, and so does the Qt gui. I'm getting very curious. What is this application? Regards, Lars -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTim_NELaDptg3+Zxus=8vtjfniswmzej8fzes...@mail.gmail.com
Re: Help with mantis package
Hy Boyd and Michal, On 02/22/2011 04:53 PM, Boyd Stephen Smith Jr. wrote: On Tuesday 22 February 2011 03:56:45 Michal Navratil wrote: i have been waiting for some time to see new 1.2.x branch package of the mantis bug tracking software in debian. I have also tried to contact responsible maintainers (as visible on the QA page) offering some help but probably some filter caought my email as no response had arrived. Sorry for the inconvenience, but probably there were a problem with the email, the best way would have been the bugtracker, as Boyd explained to you. Just FYI we have done a lot of work on the new package version, including the possibility to implement PostgreSQL, solving some important outstanding bugs and working on a DFSG changes and resolving some problems with new licenses on upstream version, and finally finding a solution with the new implementation of external pluggins on mantisBT ... during the frezze state, as probably Michal will know, mantisBT released 3 new upstream packages, and we couldn't upload any of them because the stage of the moment, and there were some CVE that took precedence over new implementations... probably we could upload to experimental some of them, but as you know upstream were patching over patching on this time, and we thought it would be better to release on squeeze the more stable at this moment (it tooks 5 versions, including stable one)... maybe a mistaken decision ... but that's done. Now, we are finishing the work with the 1.2.4 release and it would be greatly appreciated some help, particularly in tests with the new version we are working around. During last week i was trying to prepare package of the latest release (currently 1.2.4) on my own and finally today it seems to be working. I have briefly tested clean install and upgrade from the 1.1.8 version (with mysql DB) on my project and it looks working. Michal, if you're interested on help us I will agree to talk|contact to you directly in some days for do some collab, if you feel better you can upload your work by your own following the directions Boyd explained to you, but I honestly would much appreciate that we can collaborate on some way, specially not to waste our commonly effort. Most maintainers are appreciative of extra help, as long as it is done is such a way that their efforts aren't wasted. Establishing communication or documenting attempts to do so is key. Sure, thanks Boyd. Best regards, Sils signature.asc Description: OpenPGP digital signature
