Bug#665926: RFS: mail-notification/5.4.dfsg.1-4 -- mail notification in system tray
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my updated package "mail-notification". This is still just a bug-fix update, I haven't finished the various changes I'm working on upstream. The source builds those binary packages: mail-notification - mail notification in system tray mail-notification-evolution - evolution support for mail notification To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mail-notification Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mail-notification/mail-notification_5.4.dfsg.1-4.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: mail-notification (5.4.dfsg.1-4) unstable; urgency=low * Build with gmime 2.6 rather than gmime 2.4 (patch provided by Michael Biebl; closes: #664000). * Refresh patch providing Evolution 3.0 (from upstream, based on work by Erik van Pienbroek for Fedora; closes: #657558). * Depend on gstreamer0.10-tools which is required to play sounds (thanks to Sergio Cipolla for pointing this out; closes: #658607). * Ignore default values which can no longer be found (patch provided by Gunnar Hjalmarsson; closes: #641937). * Standards-Version 3.9.3, no change required. -- Stephen Kitt Tue, 27 Mar 2012 00:06:19 +0200 Regards, Stephen Kitt -- 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/20120327052207.10036.75570.report...@heffalump.sk2.org
Bug#665823: RFS: libapache2-mod-geoip/1.2.7-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nigel, On 27.03.2012 00:52, Nigel Jones wrote: > The database stanzas are commented out completely (and I'm not > going to change this behaviour), and not having them installed will > not cause issues for Apache installations. Well, but letting it commented out or not, mod_geoip relies on that that database and not having any database around makes mod_geoip a void no-op module. That should be expressed by means of package relations. I guess that could be a fairly unsettled user experience otherwise. Everything else I mentioned are fairly nitpicking suggestions I admit. Moreover you can ignore me anyway, as you don't need to convince me as I can't sponsor you after all. :) - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPcQDMAAoJEMcrUe6dgPNtxCkQAMQy2cUh08a/KwyKRKHpKkZv XbWoOzdFAxPQlQkVc7smHRlRj/Racj9nwrvo0S/L+lktR5jv4FskQqUee28dp81z 1EcHKUnDxB9NSlGEU3yb8UiUrnGOF7h05UGdEoIiapukA1LUVIruU3QdhbxDV56E a6TQkynYULZmhSQErYKodEx8l7vvYS77vItsjCVmmrkUR6BV100SnAZz2oV3zK6B 59TJVefl2IfR8+yaE43BIuQsAg6PG/rdRWJtnnc47DNc2X6iZeXVlD1wvEX1eWan Y76FebWysH1g5nuJ77RxWZojSbEieX6pcpz0UZfUXsRbBq5R/MH+D4TDLXx+Qicp r8QdSqXSHbSiz/YdK3wJedgXItKmUnb906Y2ZbUs+fy6GhY0rKYlRBSTt8069kJg C7xifSMqhrpgNp58/ZzaDRS/V94hixuwIYpAhPL6iuoAqiKFkIw3p/IgcnNjLtxH 9Xp2Sf2ZxItWtl0q47W4KbS2pJl1z/hOX0rjCx7FbpUTzznj1Dlneu4k4fgYC+b7 UZqMe3iwfKJgu0lQ+sDotTB6BSeuCmVCJ5E+ZtkB5MIKmb2RUa+vISxoqE7ORg6D uLSpcBCY6FlEL25xNwJYbm0RP5jdf2xMfNALcspr6XEfNnBrGPiv7e6URFk2N/dY 11Z6ObToRQFwHOYRd6cb =4zcu -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/4f7100cc.2040...@toell.net
Re: Bug#665823: RFS: libapache2-mod-geoip/1.2.7-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nigel, On 27.03.2012 00:52, Nigel Jones wrote: > The database stanzas are commented out completely (and I'm not > going to change this behaviour), and not having them installed > will not cause issues for Apache installations. Well, but letting it commented out or not, mod_geoip relies on that that database and not having any database around makes mod_geoip a void no-op module. That should be expressed by means of package relations. I guess that could be a fairly unsettled user experience otherwise. Everything else I mentioned are fairly nitpicking suggestions I admit. Moreover you can ignore me anyway, as you don't need to convince me as I can't sponsor you after all. :) - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPcQCLAAoJEMcrUe6dgPNtY44P/RPog/KNpzXIt5orG9H9w7FG Z5cyaBaA3IMUAgnPBoukoU755Uyh4xISZfx9PidsxL0EZK1AyUOqC5eCEwdhgFBY 2maLsl7+FEN/WtoClp/Ug7AZ58dKpZ3+aodnweAprwiaE8iet8PNSYlO0SkSKc/6 8JP+2d8N+GZlANogeejsWGZBveE+hLGhXaNlZ2p9cylI/cgPsyKjB4F3LXaYhTLF kfoxzkLZDNMNeRQrDOa/Fi9UpmzfJZWiic1HtLvO/9NSiwWSXeuzJzvqED3HovoZ L3Q1AzFVJR5yCZfGfrkzKThiNm4xF5dt3WmvKH2ifFtKcUb+l+pBVn9LbQ+uetzn lUgrurYI5aaFaFoak/CsweznM5eXTdYmwv4vPaUN5nyHDxq+axGEL/eyT1VDXiwy Nu/SZkC01owmVk9GzU3YDv/21be/DhXtCRJIrbtRjbMkzQAtLYJJpIvgDMSywBJ1 16ohHk+Pzkt/PL0al2/AAn+Hsv0/A6b10a5Z3Ed0wgZugjitfTDv/GiG8b6ncggW 5Gs4mDumARDYHUyrXem5Vr/kwiMegUOiRqu4Irvco6TQE8EFfgjo+h7QfCI6TduF 5Q8T+ytlqNDiwMOyT5TTD4pYnc9vkvG1ibMfBhIyhhsqrZ7Emn8PK3ASr4CItUYi mxB4Y4i4NvwvjImymAus =xh16 -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/4f71008b.9060...@toell.net
Re: [RFR] - Multiple (4) PEAR packages needed by PHPUnit - Was: [RFR] - PHP_Timer (Needed by phpunit)
Hi Thomas, On Tue, Mar 27, 2012 at 01:56:08AM +0800, Thomas Goirand wrote: > Thanks a lot for this effort, I really need it myself for testing my own > (numerous) PEAR packages, and I'm really willing to help here. Are you > ok if we work *together*, meaning, I'd be co-maintaining? Sure! I _really_ appreciate your help. > Do you mind if we use Git and Alioth to do these packaging? If you are > ok to do like this, then please checkout the Git repository under > /git/pkg-php/pear-phpunit-channel.git on Alioth. Of course. I also have repositories for the rest of PEAR packages in Alioth. And i'm already a member of PKG-PHP. > Let me start a quick review of this one, then we'll be able to talk > about the others once this first one will be sponsored. > ... > ... > ... > I have made corrections for all the above. If you agree with this, then > I'll upload. Let me know if there are some points you do not agree with > (I don't pretend to be the best at everything, and you might have > reasons for things you did...). I think you changes are correct. I just made a copy of the PEAR packages template and add the channel definition file, that's why is using pkg-php-tools and all the stuff you've removed. I just pushed a new debian/control version fixing the long and short description (As pointed by Ansgard in the bug). > If you don't mind, I'd like to make sure that the pear-phpunit-channel > package is in good shape and uploaded before moving to the others. > Experience showed me that this is the best way to save time. It's fine for me. > Thanks for your interest in doing these (very useful) packages, Regards, and thank you again for your help -- Luis Uribe http://eviled.org signature.asc Description: Digital signature
Bug#665658: marked as done (RFS: org-mode/7.8.06-1.0 [put in ITP, ITA, RC, NMU if applicable])
Your message dated Tue, 27 Mar 2012 01:06:24 +0200 with message-id <874ntbt11r@eisei.43-1.org> and subject line Re: Bug#665658: RFS: org-mode/7.8.06-1.0 has caused the Debian Bug report #665658, regarding RFS: org-mode/7.8.06-1.0 [put in ITP, ITA, RC, NMU if applicable] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 665658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "org-mode" Package name: org-mode Version : 7.8.06-1.0 Upstream Author : Carsten Dominik URL : http://orgmode.org/ License : GNU GPL v3 Section : misc It builds those binary packages: org-mode - keep notes, maintain ToDo lists, and do project planning in emacs To access further information about this package, please visit the following URL: http://mentors.debian.net/package/org-mode Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/org-mode/org-mode_7.8.06-1.0.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Non-maintainer upload. * New upstream release * Fix lack of odt export styles (Closes: #655652) Regards, Yury Bulka --- End Message --- --- Begin Message --- Hi, Yury Bulka writes: > Package name: org-mode > Version : 7.8.06-1.0 I'm closing this request as a newer version is already available in unstable. Regards, Ansgar --- End Message ---
Bug#665823: RFS: libapache2-mod-geoip/1.2.7-1
On 27/03/12 02:41, Arno Töll wrote: First, let me inform you, you should prepare another version of your package which works with Apache 2.4, available in experimental. That one is going to replace Apache 2.2 in Debian Sid pretty soon. However, this breaks all module packages and they need some source tweaks. Please read [1][2][3] for more information about this as this is going to affect you really soon. Yes, I'm aware that 2.4 is out, and will work on a 2.4 package later (likely mid-next month). mod_geoip probably does not work without GeoIP database installed. You should recommend the geoip-database at least. I realize there are proprietary databases available, thus my suggestion to use a weaker recommends constraint. The database stanzas are commented out completely (and I'm not going to change this behaviour), and not having them installed will not cause issues for Apache installations. The main reason that I didn't when I took up the package last year, the database was provided by the GeoIP source package, in addition, the behaviour hasn't seemed to confuse people so far... ...however, since the geoip-database is now it's own source package I will include it for the 2.4 update in experimental. Do you have any public version control system to maintain your package? If yes, add Vcs-Browser and Vcs-(Git|Svn|...) fields to your control file. Not yet, when I've tried to find info on the Debian places for hosting it, I've thrown my hands up in disgust at not finding anything/the right info, and decided to stick with what I know, especially since it is such a small, single maintainer package. In your maintainer script you should call a2enmod/a2dismod with the -q argument. And while you're at it you could perhaps safe some CPU cycles by changing the shell to /bin/sh (you need to avoid bashisms then of course). Your debian/rules file looks fairly ok, but wasn't updated in this century. Maybe upgrade to the newer short dh format which makes it much less probably that you're forgetting something or your package breaks in a unforeseeable future. In re: to both, (and please note I'm not trying to take the lazy approach), I agree, but I doubt there will be another update before Apache 2.4 lands in unstable (and I also note that this seems to be targeted for Wheezy as it is), that requires changing the pre/post scripts completely, I'd sooner go the full hog and start the packaging from scratch (while retaining the changelog) at that point, than making small cosmetic changes now. (a2enmod/a2dismod -q seems to save 1 printed line, it's an undocumented option so please correct me if I'm wrong). Maybe you could also omit the last sentence in the package description as we're not shipping anything but Apache 2 since almost a decade or so. Ha, I'd never noticed that line in the control file, it's still true I guess, but I've removed it locally as a reminder that it is completely out of date. - Nigel -- 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/4f70f33e.1060...@nigelj.com
Re: [RFR] - Multiple (4) PEAR packages needed by PHPUnit - Was: [RFR] - PHP_Timer (Needed by phpunit)
On 03/27/2012 12:59 AM, Luis Uribe wrote:
> Hi Thomas,
>
> It's me again! Trying to upgrade PHPUnit into Debian.
Hi,
Thanks a lot for this effort, I really need it myself for testing my own
(numerous) PEAR packages, and I'm really willing to help here. Are you
ok if we work *together*, meaning, I'd be co-maintaining?
Do you mind if we use Git and Alioth to do these packaging? If you are
ok to do like this, then please checkout the Git repository under
/git/pkg-php/pear-phpunit-channel.git on Alioth. I have added,
accordingly, the Vcs fields:
Vcs-Browser: http://git.debian.org/?p=pkg-php/pear-phpunit-channel.git
Vcs-Git: http://git.debian.org/git/pkg-php/pear-phpunit-channel.git
If it isn't done already, please register to the PKG-PHP Alioth group,
and if you're not a PEAR packager yet, I can give you these rights (I'm
admin of the PKG-PHP group on Alioth). Let me know when done.
> After our last [0]email i just [1]ask Mathieu for the best way to install
> PEAR packages from a different PEAR channel with pkg-php-tools and i
> decided that the best way is to to create a new package:
> pear-phpunit-channel, because there are many PEAR packages in that
> channel.
I think that this is a good idea and a good approach to the problem.
> So i fill an [2]ITP and [3]upload a new native package for
> pear-phpunit-channel.
Let me start a quick review of this one, then we'll be able to talk
about the others once this first one will be sponsored.
1/ dh_phppear substitution variables in debian/control
First of all, you are using the things for dh_phppear, with your control
file having:
Depends: ${misc:Depends}, php-pear, ${phppear:Debian-Depends}
Recommends: ${phppear:Debian-Recommends}
Breaks: ${phppear:Debian-Breaks}
But this is *not* a PEAR package that you are packaging here. It's a
single file (eg: the pear.phpunit.de.reg and nothing else, if I
understood correctly your package). So there's no reason at all to use
pkg-php-tools, which by the way, you do not even depend on, even with
the variable substitution above.
2/ The use of dh 8 sequencer
While it's "ok" to use the dh 8 sequencer, in fact, your package only
needs to install a single unique file. Frankly, that's a bit overkill to
have all these calls for nothing.
3/ Build-Depends: and Depends: on php-pear
I don't think these are even needed. What we are packaging here is a
single file, which doesn't need pear to get installed or "run". So why
would we [Build-]Depends on php-pear? To me, it's not needed.
4/ Native package
You decided to use a native package. But how did you get the
pear.phpunit.de.reg file? Isn't it coming from upstream?
I have made corrections for all the above. If you agree with this, then
I'll upload. Let me know if there are some points you do not agree with
(I don't pretend to be the best at everything, and you might have
reasons for things you did...).
> Also i create new packages for [4]php-file-iterator,
> [5]php-timer, [6]php-text-template and [7]php-token-stream. All of them
> depends of pear-phpunit-channel and install their .reg file so PEAR
> didn't install a new version of the same package.
>
> Could you (or someone else) take a look at it?
If you don't mind, I'd like to make sure that the pear-phpunit-channel
package is in good shape and uploaded before moving to the others.
Experience showed me that this is the best way to save time.
Thanks for your interest in doing these (very useful) packages,
Thomas Goirand (zigo)
--
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/4f70adb8.9020...@debian.org
Re: [php-maint] Bug#380731: I would like to support this effort to package phc and php-embedded in debian
On Mon, Mar 26, 2012 at 10:08 AM, Ondřej Surý wrote: > You would > double the work required > by security team. Every security issue which hit the PHP would need > two updates - one in > main php5 package and second in php5-embedded. That would be bad, I agree. I did not think that far. Right now i am still fighting with hiphop for php, when i have that package done nicely I will look at phc. maybe we can make a separate php embedded package that uses the same sources, and is built at the same time. mike -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org -- 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/caf0qkv3h5tvk+x1qeu-fz2cevgnmuw9nfuou43p4zief8dm...@mail.gmail.com
[RFR] - Multiple (4) PEAR packages needed by PHPUnit - Was: [RFR] - PHP_Timer (Needed by phpunit)
Hi Thomas, It's me again! Trying to upgrade PHPUnit into Debian. After our last [0]email i just [1]ask Mathieu for the best way to install PEAR packages from a different PEAR channel with pkg-php-tools and i decided that the best way is to to create a new package: pear-phpunit-channel, because there are many PEAR packages in that channel. So i fill an [2]ITP and [3]upload a new native package for pear-phpunit-channel. Also i create new packages for [4]php-file-iterator, [5]php-timer, [6]php-text-template and [7]php-token-stream. All of them depends of pear-phpunit-channel and install their .reg file so PEAR didn't install a new version of the same package. Could you (or someone else) take a look at it? Those are the first set of packages needed by [8]PHPUnit. The packages are lintian clean and builds correctly in a pbuilder (sid, i didn't check on testing or stable yet). [0] http://lists.debian.org/debian-mentors/2012/01/msg00268.html [1] http://lists.alioth.debian.org/pipermail/pkg-php-pear/2012-January/000238.html [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665846 [3] http://mentors.debian.net/debian/pool/main/p/pear-phpunit-channel/pear-phpunit-channel_1.1.dsc [4] http://mentors.debian.net/debian/pool/main/p/php-file-iterator/php-file-iterator_1.3.1-1.dsc [5] http://mentors.debian.net/debian/pool/main/p/php-timer/php-timer_1.0.2-1.dsc [6] http://mentors.debian.net/debian/pool/main/p/php-token-stream/php-token-stream_1.1.3-1.dsc [7] http://mentors.debian.net/debian/pool/main/p/php-text-template/php-text-template_1.1.1-1.dsc [8] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607393 After that, i expect to continue with the other set of dependences and finally adopt PHPUnit, hopefully the new version will be in testing before the freeze. Regards. On Sat, Jan 14, 2012 at 03:32:34PM +0800, Thomas Goirand wrote: > On 01/14/2012 07:29 AM, Luis Uribe wrote: > > Hi Thomas > > > > It's been a few months since i wrote you asking for help with php-timer, > > well > > finally i have time to send you a new package with all of your points fixed. > > > > I will be happy if you (or someone else) could take a look at it. Thanks. > > > > http://mentors.debian.net/debian/pool/main/p/php-timer/php-timer_1.0.2-1.dsc > > Hi, > > Let me review it. > > 1/ debian/README.source > This file talks about dpatch, however, you are using quilt. Please fix > it, or simply remove the file. > > >> 6/ Once installed, your package creates: > >> /usr/share/php/PHP/Timer.php > >> /usr/share/php/PHP/Timer/Autoload.php > >> > >> IMHO, it should rather install: > >> /usr/share/php/Timer/Timer.php > >> /usr/share/php/Timer/Timer/Autoload.php > > > > Done, i change the dir's name in override_dh_install because i don't know > > (and > > i don't think it's possible) how to represent a new dir in a patch. Let me > > know > > if that approach is wrong. > > > > I also add override_dh_auto_install because dh_auto_install > > -O--buildsystem=phppear > > didn't work when i build it on pbuilder. It seems to happen because > > php-timer > > is a PEAR package from another channel, also i'd like to know what do you > > think > > about it. > > I think you should talk about it with Mathieu Parent, who wrote > pkg-php-tools. I've put him as Cc: to this mail. > > >> 7/ Do you know why your package doesn't build in Squeeze? :) > > > > Ehhm ... it is necessary? I always build it on sid. > > It's not mandatory, but it's better if it does, so that you can > eventually write a backport. Never mind, forget it. > > Cheers, > > Thomas -- Luis Uribe http://eviled.org signature.asc Description: Digital signature
Bug#665331: marked as done (RFS: glipper/2.3-2 [RC])
Your message dated Mon, 26 Mar 2012 23:23:33 +0800 with message-id and subject line Re: Bug #665331: RFS: glipper/2.3-2 [RC] has caused the Debian Bug report #665331, regarding RFS: glipper/2.3-2 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 665331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "glipper" * Package name: glipper Version : 2.3-2 Upstream Author : Laszlo Pandy * URL : https://edge.launchpad.net/glipper * License : GNU GPL v2 Section : utils It builds those binary packages: glipper- Clipboard manager for GNOME To access further information about this package, please visit the following URL: http://mentors.debian.net/package/glipper Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/g/glipper/glipper_2.3-2.dsc Changes since the last upload: * debian/rules: - Removed dependency on python-gnomeapplet (Closes: #659806), thanks to Sebastian Ramacher for the patch. * debian/control: - Bump Standars-Version to 3.9.3. Regards, Jose Ernesto Davila Pantoja --- End Message --- --- Begin Message --- The package has been uploaded, closing. -- Regards, Aron Xu --- End Message ---
Bug#665823: RFS: libapache2-mod-geoip/1.2.7-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Nigel, On 26.03.2012 14:05, Nigel Jones wrote: > I am looking for a sponsor for my package "libapache2-mod-geoip" thanks for your contribution. As I can't sponsor packages, take the following hints as a review only: First, let me inform you, you should prepare another version of your package which works with Apache 2.4, available in experimental. That one is going to replace Apache 2.2 in Debian Sid pretty soon. However, this breaks all module packages and they need some source tweaks. Please read [1][2][3] for more information about this as this is going to affect you really soon. I think it would be best to get this version into Wheezy now, and focus on the 2.4 module package afterwards, perhaps even by doing an upload to experimental. mod_geoip probably does not work without GeoIP database installed. You should recommend the geoip-database at least. I realize there are proprietary databases available, thus my suggestion to use a weaker recommends constraint. Do you have any public version control system to maintain your package? If yes, add Vcs-Browser and Vcs-(Git|Svn|...) fields to your control file. In your maintainer script you should call a2enmod/a2dismod with the -q argument. And while you're at it you could perhaps safe some CPU cycles by changing the shell to /bin/sh (you need to avoid bashisms then of course). Your debian/rules file looks fairly ok, but wasn't updated in this century. Maybe upgrade to the newer short dh format which makes it much less probably that you're forgetting something or your package breaks in a unforeseeable future. Maybe you could also omit the last sentence in the package description as we're not shipping anything but Apache 2 since almost a decade or so. [1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html [2] http://wiki.debian.org/Apache/PackagingFor24 [3] http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPcHIeAAoJEMcrUe6dgPNtDeIQAM535PKtLP0gf3SiktOHX6bo NjlSN7jpz9FSihZ929lsmtbafW/SLe9H48RKjlEk691jFw6KvJXhs5l+ga2VPisv lRSj+0QNi46J03iCnqvlCqt2OKP2hw48fyllPmHzW0O8ZnRPt61ITvEwLLcRc1+I KAMrPaZnZkbpLvQMrXthjvyeV4VyHTjgxsWyoIwgJURQjevv61WhSMbzu5xFCqGu WVgdikswLXkwRZQoBDMtwdZ5fQxJ7TITRqBiMFiVOcRZkCaM77yEDEfe+Fj5uEDf WAU3f6qPYVjpM3niGfCp15NKyUF23wktpwcRd+kn51WfjXZ5jeeWKXVrbodGlxI4 TeSOZpjWfw5JAnksn8rmMt3glcyI3JNLxnumMnCQSyPu0KD8XFf3sj57p0OIWVFv /7v+dGjjs8Gui7cSYlqCFn0fnCZzQKGIMHiNLgzFiNPddcoEL++15gFXrt7+EZI9 Vw/yNRKQVrbrKd8IkAS7RPOIjE+/4Q/8AMYgAkQRzme/dLui4q/Ovqduus9FjLAf PuwiDoFUFn/S4h4zGFGcjjrF+xHoZS/HvBE5C0TKJ+Tt+CTBXVB3kSlaWB4PZQcP TsKE28suYrypKFVGEyeiCcjUD+zh0SITiZiNQMvun2BOuuJgBsRInyRyasoG7waI RqDrECJaljsypevyO4C2 =CjWl -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/4f70721e.2040...@toell.net
Bug#665826: RFS: mydumper/0.5.1-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mydumper" Package name: mydumper Version : 0.5.1-2 Upstream Author : Domas Mituzas, Andrew Hutchings, Mark Leith URL : http://www.mydumper.org License : GPL v3 Section : database It builds those binary packages: mydumper - High-performance MySQL backup tool To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mydumper Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mydumper/mydumper_0.5.1-2.dsc More information about mydumper can be obtained from http://www.mydumper.org Changes since the last upload: * fixed watch file * updated standards version * patch 0005-zlib-file-type-change-fixes.patch added fix FTBFS from zlib > 1.2.4 (Closes: #662582) (LP: #948122) Regards, Mateusz Kijowski -- 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/CAOvFzeXK-XdSebonJL_b5wspYi9-=8owonnuxukg-78x+mw...@mail.gmail.com
Bug#665823: RFS: libapache2-mod-geoip/1.2.7-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libapache2-mod-geoip" * Package name: libapache2-mod-geoip Version : 1.2.7-1 Upstream Author : Maxmind * URL : http://www.maxmind.com/app/mod_geoip * License : Apache Software License v1.1 Section : httpd It builds those binary packages: libapache2-mod-geoip - GeoIP support for apache2 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libapache2-mod-geoip Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/liba/libapache2-mod-geoip/libapache2-mod-geoip_1.2.7-1.dsc More information about hello can be obtained from http://www.maxmind.com/app/mod_geoip. Changes since the last upload: libapache2-mod-geoip (1.2.7-1) unstable; urgency=low . * New upstream release (Closes: #655492) - Includes support for newer APIs from upstream - Includes IPv6 support, as a result, now requires GeoIP >= 1.4.8 Regards, Nigel Jones -- 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/4f705b77.2000...@nigelj.com
Bug#665658: RFS: org-mode/7.8.06-1.0 [put in ITP, ITA, RC, NMU if applicable]
Sébastien Delafond writes:
> On Mar/25, Yury Bulka wrote:
>> Thank you for accepting my contribution.
> I actually didn't use your NMU (package 7.8.06 myself), but it did
> serve as a notice there was a new upstream version anyway :)
I just installed the new org-mode from repositories and found that the
style files are still missing (emacs reports an error and dpkg -L doesn't list
them).
There are two files I needed to change tho files in the debian/
directory to make this work. The rules (the install target):
cp -r etc $(CURDIR)/debian/org-mode/usr/share/emacs/site-lisp/org-mode
And the emacsen-install file:
DATAFILES="/usr/share/emacs/site-lisp/${PACKAGE}/etc/styles/*.xml"
DATADIR=/usr/share/${FLAVOR}/site-lisp/${PACKAGE}/etc/styles
cd ${DATADIR}
for i in ${DATAFILES}; do
ln -fs $i
done
All best,
Yury
--
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/86r4wfbvn6@gmail.com
Re: Elegant Debhelper way to specify files between runtime and debug library packages
Ben Finney writes: > What is the recommended way to specify packaging for a library package > and its corresponding debug symbols package? I use the following line at the top of my debian/rules: export DH_OPTIONS += --dbg-package=foo-dbg This appears to do the right thing with dh compat level >= 8, havent tested with earlier, but should work there too. Though, the few places I use this, are pure C libraries, which are, I assume, a bit different from what you're doing. > With a previous Debhelper (7.x), I could specify it with ‘debian/rules’ > in the ‘install’ and ‘override_dh_auto_install’ target: > > install: build > dh $@ > > override_dh_strip: > dh_strip --dbg-package=foo-dbg > > With the current Debhelper (in version 8 mode), that fails to put the > files in the right place AFAICT. I am now resorting to this less-elegant > solution: > > install: build > dh $@ --package=foo --exclude "*_d.so" > dh $@ --package=foo-dbg > > override_dh_strip: > dh_strip --dbg-package=foo-dbg Are you sure dh7 excluded _d.so? I failed to find anything in debhelper's git history that did that. > That's a step backward, because if I need more packages, the ‘install’ > rule starts to grow more special cases, defeating some of the > auto-detect features of Debhelper. You could do something like: install: build dh $@ --package=foo-dbg dh $@ --exclude "*_d.so" debhelper should know that it did install foo-dbg already, so in the second case, it won't install that again. (AFAIK, haven't tested, so I might be wrong here). -- |8] -- 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/87398vzs12.fsf@algernon.balabit
Re: [php-maint] Bug#380731: I would like to support this effort to package phc and php-embedded in debian
On Sun, Mar 25, 2012 at 10:58, Mike Dupont wrote: > For the packaging of phc in debian, which I would like to have > packaged, we need some way to allow the embedding of php. > I will look into packaging of them both together and uploading them to > debian mentors. Really php embedded could be it own package like > discussed. That's the worst idea I have ever heard in this case. You would double the work required by security team. Every security issue which hit the PHP would need two updates - one in main php5 package and second in php5-embedded. I am strongly opposed to uploading php-mebedded as separate package just to circumvent the (later) things which was said about embedded SAPI (still experimental in the upstream, no motivation to support yet another SAPI from maintainers). > it should be possible to host the debs produced on debian mentors > server or somewhere else until we have a final solution. I have a much better proposal. Join the PHP5 packaging team (#664595), help with bug squashing in the main package and also dedicate yourself to support php5-embedded. There are already too many "sort-of-orphaned" packages in the Debian where the original maintainer lost the interest in the software and in the package and forgot that he made the upload. O. -- Ondřej Surý -- 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/caljhhg_mziss0gpqq53sxhddr-uwozoxownmfzyi9h4p9ip...@mail.gmail.com
