Re: Bug#691780: RFS: imagemagick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Bastien, Le 04/11/2012 17:25, roucaries bastien a écrit : I could as a mainteners open artificially a bug on the bts This would not be artificial, this would be good practice (assuming the info is not embargoed by the security team). The BTS is a central place to communicate with sponsors, with the release team, with users. Regards, Thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQl39zAAoJEJOUU0jg3ChAm84P/jM+2aimxKseqvclOup7XgrC x4r5zP25bIdRMkdPVJyhy7J7pcrHaEnhnINXkRGONYKmLRfUXrf944LTqx2mDkOO u+byl9GPl506NGt7oL0UryU49DUlweMpLJrPTftpz/bjyZD3+BJhgIJLFJX944qA PP3YccP+qQUHU1IwbruZOCzL+Z9MzbhYowDfPoW1FGy1kTD589jnDPa1aEE8S3e7 wUe2YDHlqHuLs9Zm0C1fqItvskwG4wfnCdQwyH8vd+SK3lIjnK4FSGyCNTUB1yWO 1vld3o1m4sPS3zGX0/gej+m9NJuZFxqnTN8GBJVZ0QGzJBYVQMqBTL3xYNr5Ab4t VTDeohItgLO9DBMHPD7JhoNvvb8GhVjSfsZ0d9+PkTYeFYTqLmjs/DSKz1gVE+cb 5J5Bh2WmhgTF3WLE12fiqIiDY8y314wJI9n4P8SDfgoF08Oy1GYPC31hdXLnU263 nbwuOpMqjB35vGmNbZ0kGaGBs4BEWBMtg5rnOkFfoQHwP4PVM3gXX199N4Wc/KMm wwSuPFUySmUzE8oeKvYxF2sErBJw4bdKrRuKXEkPhJtVkla9yMbFP8RiDNWgBP+H yrftQFtLJIpLYmk1YnNiTxdf2Yt+2H6RH0r0g0wmaANwYB8333Dktq8SfE28bp67 R8/dNYnMhnXJMknSFImQ =yt8c -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/50977f84.1000...@debian.org
Bug#686070: libpam-ssh/1.92-15
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Jerome, - I would be much more comfortable if you asked the previous maintainer for comments on the ITP (even if he never answers!) - You could comment on #691988 explaining why you think the package should be accepted for Wheezy: + insist that two users already requested reintroduction; + explain why you only took action after the freeze (perhaps you used the squeeze version happily before that?); + explain that your RFS was filled in August and that you are not responsible for the 2 month delay since then. - That said, the package still contains non-minimalistic changes. You need to produce a debdiff on the source package in squeeze and your source package and comment on this debdiff. Every single change must relate to fixing a RC bug or a release goal. For instance, I don't get why you made those changes: + why introduce fix-debian-adhoc.patch, build-depend on du-autoreconf etc? This seems to be replacing this: $(MAKE) CFLAGS=$(cflags) -Wl,--version-script,debian/pam_ssh.version which I find simpler and more elegant. Perhaps some of these changes are to fix a bug, please undo whatever is unnecessary and explain (in this bug thread) what is necessary. + Why remove the VCS control field? You should use the repository instead. + the clean rule changes also seem unnecessary. - Perhaps your package will not be unblocked for wheezy. In any case you probably want to upload a new upstream soon enough. I would not upload a new upstream to unstable at this point because it would lower still the chances that the packages makes it into wheezy. However, you can prepare the best possible package with new upstream for experimental. In this package, you can do all the changes you want. I'm willing to sponsor your package (either 1.92 to unstable or 1.97 to experimental, or both) but please try contacting the previous maintainer for comments. Note: I'm subscribed to the RFS, the ITP, and the release.d.o bugs. no need to CC me. Regards, Thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQl4MmAAoJEJOUU0jg3ChAEaUP/iZhBeULC/yy5wGvyhTqZXn4 /YIhtTqTxOQA2rNwUMc2jyDYnAu6GpCrYjOz9wmWk2C356SehDkAAD/5rLoAbDKH /DG/ZEUjgjfTcQA2IIu01jnGdSIM3p/D3laq6xaeFXBOYeTQ1DMlmhFVAm8mc74u db+LE/teDlBJF8EQ1IBcOmOHq8xXQacLWngk08NhHwWdAPtMpoLhnuplDGEH3XFM uLH4gJSpPNhk6Py7FOKT7v5VTg90QwNgilPnoBXdOWsQUZLAxWLLnLjNHDB2m6Ed Y7CZfuL/TH3uqtWUR4jmECYbuiiNwtVoFgT537V/6fJD6DDj9K5pWxE3226vCjUL N6Ye3U50lLIdtd8c9D/0SHbPDMR2sMpOsm4Gb/Ko49rqzU9wZHbkbgGtdjXLNg3D A/f+j0cs2+Dj7uPXUXALhvhM92119ePTPPLDZ/Vnk5s3mva+pYEjgr6XT8TzLMUA XQq8/WTqwgrpFQjqcoRFSo7MHtm3eD+ZWeK3GzkDanVoxafmMN5z0GMLtSjSiE8e kjmdZkuqAf6p1Yp6gevtMx8MRUf2/IR/B1eyFdZI927O13MfdVbvZKotriy1KgR/ thVfNIlGMfw+6+tRRs5JyrGMK0grYVOPtW0++ZDiRid9mO0XreB78VU3DQVThOZh uyfjVwH1lhkNiVy8IOle =/ZWo -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/50978326.10...@debian.org
Bug#692240: RFS: poedit/1.5.4-1
Hi Norbert,
Thank you for your interest and comments. I've re-uploaded to mentors
a package which i think it solves both problems. The package was
correctly created on my running system and also on a pbuilder chroot.
Maybe you could take a look at it.
Best wishes,
Pedro m42 Ribeiro
On 3 November 2012 23:28, Norbert Preining prein...@logic.at wrote:
Hi Pedro,
On Sa, 03 Nov 2012, Pedro Ribeiro wrote:
http://mentors.debian.net/package/poedit
I am interested in that, since I have been building my own 1.5pre packages
since quite some time... but ..
* building in a clean cowbuilder does not succeed, could be a cowbuilder
issue:
$ sudo /usr/sbin/cowbuilder --build --buildresult . poedit_1.5.4-1.dsc
fakeroot is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I: Copying back the cached apt archive contents
I: Copying source file
I: copying [/home/norbert/Debian/poedit/poedit_1.5.4-1.dsc]
I: copying [/home/norbert/Debian/poedit/poedit_1.5.4.orig.tar.gz]
I: copying [/home/norbert/Debian/poedit/poedit_1.5.4-1.debian.tar.gz]
I: copying [/home/norbert/Debian/poedit/SIGNATURE-]
cp: cannot stat `/home/norbert/Debian/poedit/SIGNATURE-': No such
file or directory
* building in the running system also dies:
$ dpkg-buildpackage -us -uc -rfakeroot
...
dh_auto_clean
Buildfile: /home/norbert/Debian/poedit/poedit-1.5.4/build.xml
BUILD FAILED
Target clean does not exist in the project Poedit.
But I guess the same build failure would happen in the cowbuilder, too.
Can you fix that, please?
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
BOOKMeanwhile, the starship has landed on the surface
of Magrathea and Trillian is about to make one of the most
important statements of her life. Its importance is not
immediately recognised by her companions.
TRILL. Hey, my white mice have escaped.
ZAPHOD Nuts to your white mice.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
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/cakgfwzrw0g58tncbgsgm8oi5-ft_rwy3qrktisz9_zku0s5...@mail.gmail.com
Bug#692240: RFS: poedit/1.5.4-1
Hi Pedro,
On Mo, 05 Nov 2012, Pedro Ribeiro wrote:
Maybe you could take a look at it.
Still not optimal. Is it on purpose that you do build without
translation memory?
From my build process:
...
checking for Berkeley DB = 4.7 (C++)... not found
configure: WARNING: cannot find Berkeley DB = 4.7, Poedit will build w/o
translation memory feature
...
Debugging information: no
Translation memory: no
Spellchecking: yes
...
Doesn't that look like a missing build-dep? I see you are carrying the
libdb-dev
but it seems that nowadays poedit needs
libdb++-dev
because after installing that it works out nicely.
Please fix this in your repository and reupload, thanks a lot!
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
PITLOCHRY (n.)
The background gurgling noise heard in Wimby Bars caused by people
trying to get the last bubbles out of their milkshakes by slurping
loudly through their straws.
--- Douglas Adams, The Meaning of Liff
--
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/20121105115250.ga28...@gamma.logic.tuwien.ac.at
Any idea how to write watch file for codeplex hosted sources?
Hi, I have spent some time into writing a watch file for https://csb.codeplex.com/releases/ but failed and some research on mailing lists revealed some other failures. Any idea whether a clever mangling might help anyway? And yes, I will ask my sponsee to teach upstream to find more easy ways to download their sources. Thanks for any help Andreas. -- http://fam-tille.de -- 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/20121105142302.ga12...@an3as.eu
Re: Any idea how to write watch file for codeplex hosted sources?
On Mon, Nov 05, 2012 at 03:23:02PM +0100, Andreas Tille wrote: I have spent some time into writing a watch file for https://csb.codeplex.com/releases/ but failed and some research on mailing lists revealed some other failures. Any idea whether a clever mangling might help anyway? No, as you can't get a direct link to sources without JavaScript at all. All you can get is a list of name-version strings with links to individual download pages, and that won't help uscan. -- WBR, wRAR signature.asc Description: Digital signature
Bug#692240: RFS: poedit/1.5.4-1
Hi,
Sorry, my bad on the tm compilation. Re-uploaded with corrected dependencies...
Took the chance to also include dpkg-buildflags to avoid a few lintian
warnings
On 5 November 2012 11:52, Norbert Preining prein...@logic.at wrote:
Hi Pedro,
On Mo, 05 Nov 2012, Pedro Ribeiro wrote:
Maybe you could take a look at it.
Still not optimal. Is it on purpose that you do build without
translation memory?
From my build process:
...
checking for Berkeley DB = 4.7 (C++)... not found
configure: WARNING: cannot find Berkeley DB = 4.7, Poedit will build w/o
translation memory feature
...
Debugging information: no
Translation memory: no
Spellchecking: yes
...
Doesn't that look like a missing build-dep? I see you are carrying the
libdb-dev
but it seems that nowadays poedit needs
libdb++-dev
because after installing that it works out nicely.
Please fix this in your repository and reupload, thanks a lot!
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
PITLOCHRY (n.)
The background gurgling noise heard in Wimby Bars caused by people
trying to get the last bubbles out of their milkshakes by slurping
loudly through their straws.
--- Douglas Adams, The Meaning of Liff
--
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/cakgfwzsuptksuumm+gdbbp_pv2yf2sqsxvo51dsfthvprn6...@mail.gmail.com
Bug#683184: RFS: suckless-tools/39-1 [ITA]
On 20:33 Sun 04 Nov , Jakub Wilk wrote:
* Vasudev Kamath kamathvasu...@gmail.com, 2012-10-30, 20:32:
.hg_archival.txt is no longer in sprop tarball, so it should be
removed from the repository, too.
Done and changes back in the git.
I don't see any relevant changes in the repository…
Sorry forgot to push ;-). Now it is really in git :-D
Regards
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: Digital signature
Bug#684220: RFS: tinysvm/0.09-1 [ITP] -- SVM trainer and classifier toolkit
Hi, I can do everything using uscan, tar, sed and wget, so I think this is not a problem. During the process I need to create a temporary directory. Should I delete it at the end of get-orig-source? Should I delete it in clean? Yes, only tarball should be left as a result. See Debian Policy §4.9 for details. Best wishes, Boris -- http://wiki.debian.org/BorisPek -- 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/344931352127...@web3f.yandex.ru
debian/bug-control: report bug against unofficial debian packages
Hi, The situation: I have build a source package and send a RFS (#675532), and now it is available here: http://mentors.debian.net/package/bilibop. Since this package is not yet sponsored, I have set up a Debian-like repository with 'reprepro', and so source and binary packages are now available and can be managed by APT tools; people who trust my work or want to test it can add the following lines in their APT sources: deb https://un.poivron.org/~quidame/debian/ wheezy main deb-src https://blahblah The questions: what can happen if a user reports a bug against one of my packages by using 'reportbug' ? Must I explicitly add 'Send-To: quid...@poivron.org' in debian/bug-control to avoid conflicts with Debian BTS ? The .dsc and .tar.gz files in the personal repository are exactly the sames than those I have uploaded on mentors.debian.net. If the answer to the previous question is YES, must I send a different version on mentors, even if the package is not sponsored (because if it is sponsored a day, the source will be modified and the personal repository will disappear) ? Thanks, quidame -- 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/n1r-mqkdqga...@safe-mail.net
Re: debian/bug-control: report bug against unofficial debian packages
Hi, On 05.11.2012 17:43, bilibop project wrote: The questions: what can happen if a user reports a bug against one of my packages by using 'reportbug' ? Must I explicitly add 'Send-To: quid...@poivron.org' in debian/bug-control to avoid conflicts with Debian BTS ? If you want people to use reportbug to submit bugs to you, this is the way to go, yes. Alternatively you could tell people on the page where you inform about your repository where they are supposed to report bugs. The .dsc and .tar.gz files in the personal repository are exactly the sames than those I have uploaded on mentors.debian.net. If the answer to the previous question is YES, must I send a different version on mentors, even if the package is not sponsored (because if it is sponsored a day, the source will be modified and the personal repository will disappear) ? Yes, you may need to do so. Alternatively you can just upload the package including the debian/bug-control file you mentioned to mentors and hope your future sponsor will hopefully detect it and ask you to remove it by then. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Processed: RFS: kbibtex/0.4-3 [RC][ITA]
Processing commands for cont...@bugs.debian.org: retitle 692366 RFS: kbibtex/0.4-3 [RC][ITA] Bug #692366 [sponsorship-requests] Fwd: RFS: [RC][ITA] kbibtex/0.4-3 Changed Bug title to 'RFS: kbibtex/0.4-3 [RC][ITA]' from 'Fwd: RFS: [RC][ITA] kbibtex/0.4-3' stop Stopping processing here. Please contact me if you need assistance. -- 692366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135213516930723.transcr...@bugs.debian.org
Re: debian/bug-control: report bug against unofficial debian packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 05/11/2012 17:43, bilibop project a écrit : The .dsc and .tar.gz files in the personal repository are exactly the sames than those I have uploaded on mentors.debian.net. If the answer to the previous question is YES, must I send a different version on mentors, even if the package is not sponsored (because if it is sponsored a day, the source will be modified and the personal repository will disappear) ? Actually, I consider it a good idea for both packages to differ: the packages you provide on your personal repository can be considered pre-releases of the upcoming official Debian package and their version should perhaps be of the form: x.y.z-1~rc1 to sort strictly before x.y.z-1, which will be the first package in Debian. This way, when your package gets finally included in Debian, your users will automatically get it as a routine update. Regards, Thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQl/UrAAoJEJOUU0jg3ChA/WkP/ArdL4h2jjICSAI3gX8d2Jta ayAPbWVxR92ypaeGNUwE5t/9e6qvsuDKlDQ3+HFBSRqHv+V5kRW8xfLCXZeAli1a Dv+AuxQBQhzCroZijiTSxWSDMaWwsCM89DnoTUtP3v6WfCZIuC47ncPokGvwzuaR LHm6cDTQGy5PO83//nCpn4UDCFNcoY5f6VvZJ2Kq+xMuOp6JyLiORRvqywF4XkdN uyrWaCsOckUvYyd8nXtSsaLjNlkO8/71ack7DVjqi302mux4SFjrJ1lHpaTaM9La dtvm14cUA1TlRJ+7t75OHrh/MbkXcI2o2dyTH8k0qj/Abb+O4vwGiRyKb5b99opx 9T10IB0xbzdR9ScR/DHzOsurYBQgOYvY6g0Ng/B+psGY8kdBVllldSZyftcmNm2m DKzuLKOlANJXDIjGmAcC0Nei+n2Hx0WYU+x2VsISjKiZR9LWBfH1MxgQOEfgD+h2 HRJ4Pnx5rJWyEEg5ahlVaFpSxQnj1Ss0SauWiQLbwdG04D8MX91t/3NC5jqG1uuA 3gfyEXYEJ4hQKXXOlhrFJ8/ak55qfSkHz/vkXbYe2vyA34z//2vW5uB353ENS+SF ugRZQ/+50FXvfmB585IVhtEn9SphV5wjPWODPtEPRvGNfJTl6B/qi1usGqEbKaxT BuA2I/ai8AcTi9niKIKY =Aa/n -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/5097f52b.2030...@debian.org
Re: Any idea how to write watch file for codeplex hosted sources?
Hi, On Mon, Nov 05, 2012 at 08:29:24PM +0600, Andrey Rahmatullin wrote: On Mon, Nov 05, 2012 at 03:23:02PM +0100, Andreas Tille wrote: I have spent some time into writing a watch file for https://csb.codeplex.com/releases/ but failed and some research on mailing lists revealed some other failures. Any idea whether a clever mangling might help anyway? No, as you can't get a direct link to sources without JavaScript at all. All you can get is a list of name-version strings with links to individual download pages, and that won't help uscan. Sorry, but that's not true. The source of the https response above contains https://csb.codeplex.com/downloads/get/466454 as direct link and it delivers the tarball in question after some seconds of delay. The line of html code that contains this link also contains the version number as link content so finally some mangling should work. Kind regards Andreas. -- http://fam-tille.de -- 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/20121105184011.gb12...@an3as.eu
Re: debian/bug-control: report bug against unofficial debian packages
bilibop project quid...@safe-mail.net writes: The questions: what can happen if a user reports a bug against one of my packages by using 'reportbug' ? Must I explicitly add 'Send-To: quid...@poivron.org' in debian/bug-control to avoid conflicts with Debian BTS ? I use Bugs: mailto:address as a source package header in debian/control instead. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- 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/878vafu6ai@windlord.stanford.edu
Bug#684220: RFS: tinysvm/0.09-1 [ITP] -- SVM trainer and classifier toolkit
Hi Boris, Il 05/11/2012 16:02, Boris Pek ha scritto: During the process I need to create a temporary directory. Should I delete it at the end of get-orig-source? Should I delete it in clean? Yes, only tarball should be left as a result. See Debian Policy §4.9 for details. Thank you very much. I still have some doubts, however: 1) what should be the name of the generated tarball? 2) what does the original source tar file format described below in Debian Policy §4.9 means? (I was not able to find the format described anywhere) 3) what does This target may be invoked in any directory in Debian Policy §4.9 means? Does it mean, for example, that I cannot use the following command: uscan --download-current-version --destdir temporary? I just uploaded an updated version of the package on mentors: http://mentors.debian.net/debian/pool/main/t/tinysvm/tinysvm_0.09+dfsg-1.dsc This version includes a first attempt of a get-orig-source target. Bests, Giulio. -- 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/50983389.3010...@gmail.com
Bug#692240: marked as done (RFS: poedit/1.5.4-1)
Your message dated Tue, 6 Nov 2012 07:41:20 +0900
with message-id 20121105224120.gc12...@gamma.logic.tuwien.ac.at
and subject line Re: Bug#692240: RFS: poedit/1.5.4-1
has caused the Debian Bug report #692240,
regarding RFS: poedit/1.5.4-1
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.)
--
692240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package poedit. I upgraded to
the latest upstream release.
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/poedit
Changes since the last upload:
* New upstream release (Closes: #684924).
* Update to Standards-Version 3.9.3
* New homepage URL (Closes: #692048).
Regards,
Pedro Ribeiro
---End Message---
---BeginMessage---
On Mo, 05 Nov 2012, Pedro Ribeiro wrote:
Sorry, my bad on the tm compilation. Re-uploaded with corrected
dependencies...
Uploaded, thanks. Closing this bug
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
CLOVIS (q.v.)
One who actually looks forward to putting up the Christmas decorations
in the office.
--- Douglas Adams, The Meaning of Liff---End Message---
Re: Any idea how to write watch file for codeplex hosted sources?
On Tue, Nov 6, 2012 at 2:40 AM, Andreas Tille wrote: https://csb.codeplex.com/downloads/get/466454 as direct link and it delivers the tarball in question after some seconds of delay. The line of html code that contains this link also contains the version number as link content so finally some mangling should work. uscan deals only with a link URLs, not with text AFAIK. -- 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/CAKTje6FW0e7ahEgEMib5=NRXgFY-7kRwaibL_em=cl+fp59...@mail.gmail.com
Bug#691780: marked as done (RFS: imagemagick/8:6.7.7.10-5)
Your message dated Tue, 06 Nov 2012 04:20:30 + with message-id e1tvaem-00027j...@quantz.debian.org and subject line closing RFS: imagemagick/8:6.7.7.10-5 has caused the Debian Bug report #691780, regarding RFS: imagemagick/8:6.7.7.10-5 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.) -- 691780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package imagemagick. My usual sponsor vincent is on holidays Severity important because it fix a few security bug that I would like to be fixed before end of freeze. * Package name: imagemagick Version : 8:6.7.7.10-5 Upstream Author : [fill in name and email of upstream] * URL : www.imagemagick.org * License : imagemagick Section : graphics It builds those binary packages: imagemagick - image manipulation programs imagemagick-common - image manipulation programs -- infrastructure imagemagick-dbg - debugging symbols for ImageMagick imagemagick-doc - document files of ImageMagick libmagick++-dev - object-oriented C++ interface to ImageMagick - development files libmagick++5 - object-oriented C++ interface to ImageMagick libmagickcore-dev - low-level image manipulation library - development files libmagickcore5 - low-level image manipulation library libmagickcore5-extra - low-level image manipulation library - extra codecs libmagickwand-dev - image manipulation library - development files libmagickwand5 - image manipulation library perlmagick - Perl interface to the ImageMagick graphics routines To access further information about this package, please visit the following URL: http://mentors.debian.net/package/imagemagick Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/imagemagick/imagemagick_6.7.7.10-5.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Fix a memory leak: after setjmp used variable need to be volatile. Fix jpeg and png coder. * Fix a memory leak: in webp handling add a forgotten WebPPictureFree * Fix another memory leak in case of corrupted image in magick++ read method. Regards, bastien roucaries ---End Message--- ---BeginMessage--- Package imagemagick version 8:6.7.7.10-5 is in unstable now. http://packages.qa.debian.org/imagemagick---End Message---
