Bug#678500: marked as done (RFS: cppreference-doc/20120620-1 [ITP] -- C and C++ standard library reference manual for English language.)

2012-11-25 Thread Reinhard Tartler
On Sun, Nov 11, 2012 at 5:24 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Your message dated Sun, 11 Nov 2012 04:20:30 + with message-id e1txp26-0004o3...@quantz.debian.org and subject line closing RFS: cppreference-doc/20120620-1 [ITP] -- C and C++ standard library

Re: wmtime 1.0b2-14 2012-11-23 22:50

2012-11-25 Thread Bart Martens
Hi Doug, On Sun, Nov 25, 2012 at 06:16:08AM +, Doug Torrance wrote: I've combined all of the changelog entries. This has the effect of the changelog skipping from 1.0b2-10 straight to 1.0b2-15. Is this okay? It's not a problem. Please let me know if you have any more suggestions! You

Bug#694164: RFS: redmine/1.4.4+dfsg1-2 [NMU] [RC]

2012-11-25 Thread Dominik George
Hi, Thank you all for this work - Dominik, would you work directly on the git repository of the redmine package ? That would allow much easier maintenance. Currently, I do not really plan on doing more work on the package, just RC bug fixing. Michael, please send follow-ups directly

Bug#694164: RFS: redmine/1.4.4+dfsg1-2 [NMU] [RC]

2012-11-25 Thread Dominik George
Hi Michael, I incorporated the changes you requested. Cheers, Nik -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#693335: RFS: pymarkups/0.2.3-1

2012-11-25 Thread Dmitry Shachnev
Control: retitle -1 RFS: pymarkups/0.2.4-1 Fixed these two issues, uploaded updated package to mentors.debian.net. Can anybody upload it now please? The new .dsc file can be found at: http://mentors.debian.net/debian/pool/main/p/pymarkups/pymarkups_0.2.4-1.dsc. On Sun, Nov 18, 2012 at 4:12 PM,

Processed: Re: Bug#693335: RFS: pymarkups/0.2.3-1

2012-11-25 Thread Debian Bug Tracking System
Processing control commands: retitle -1 RFS: pymarkups/0.2.4-1 Bug #693335 [sponsorship-requests] RFS: pymarkups/0.2.3-1 [ITP] Changed Bug title to 'RFS: pymarkups/0.2.4-1' from 'RFS: pymarkups/0.2.3-1 [ITP]' -- 693335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693335 Debian Bug

Bug#693335: RFS: pymarkups/0.2.3-1

2012-11-25 Thread Andrew Starr-Bochicchio
On Sun, Nov 25, 2012 at 9:29 AM, Dmitry Shachnev mity...@gmail.com wrote: Control: retitle -1 RFS: pymarkups/0.2.4-1 Fixed these two issues, uploaded updated package to mentors.debian.net. Can anybody upload it now please? The new .dsc file can be found at:

Processed: retitle to RFS: wmtime/1.0b2-15 [ITA]

2012-11-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: retitle 693495 RFS: wmtime/1.0b2-15 [ITA] Bug #693495 [sponsorship-requests] RFS: wmtime/1.0b2-14 [ITA] Changed Bug title to 'RFS: wmtime/1.0b2-15 [ITA]' from 'RFS: wmtime/1.0b2-14 [ITA]' stop Stopping processing here. Please contact me if you

Processed: RFS: pymarkups/0.2.4-1 [ITP]

2012-11-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: retitle 693335 RFS: pymarkups/0.2.4-1 [ITP] Bug #693335 [sponsorship-requests] RFS: pymarkups/0.2.4-1 Changed Bug title to 'RFS: pymarkups/0.2.4-1 [ITP]' from 'RFS: pymarkups/0.2.4-1' stop Stopping processing here. Please contact me if you need

Bug#693335: marked as done (RFS: pymarkups/0.2.4-1 [ITP])

2012-11-25 Thread Debian Bug Tracking System
Your message dated Sun, 25 Nov 2012 11:33:46 -0500 with message-id cal6k_ayahoqlned0gdgd4j-ay9bfayu9npbhss9uw_riqhy...@mail.gmail.com and subject line Re: Bug#693335: RFS: pymarkups/0.2.3-1 has caused the Debian Bug report #693335, regarding RFS: pymarkups/0.2.4-1 [ITP] to be marked as done.

Bug#688289: Uploaders

2012-11-25 Thread Eric
Sure, I'll upload a new version to mentors. Eric -- 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/50b24800.90...@azrockets.org

Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools

2012-11-25 Thread Andrew Starr-Bochicchio
On Fri, Sep 21, 2012 at 2:16 AM, Eric e...@azrockets.org wrote: I am looking for a sponsor for the package bzrtools, which I have recently adopted. Hi Eric, Sorry for taking so long to get back to you about sponsoring this package. I'm part of the Debian Bazaar maintenance team, [1] but have

Bug#694387: RFS: pidgin-skype/20121121+svn646+dfsg-1 [DM but packages in NEW]

2012-11-25 Thread Gabriele Giacone
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package pidgin-skype * Package name: pidgin-skype Version : 20121121+svn646+dfsg-1 Upstream Author : Eion Robb eionr...@gmail.com * URL :

Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools

2012-11-25 Thread Eric
Ok, I've done everything you've asked me to, including joining the mailing list. I think that team maintenance is a good idea for this package. Eric -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools

2012-11-25 Thread Eric
Also, I uploaded the new version to mentors. However, it still has the lintian warning about the debian/copyright file. Eric -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools

2012-11-25 Thread Andrew Starr-Bochicchio
On Sun, Nov 25, 2012 at 7:58 PM, Eric e...@azrockets.org wrote: Also, I uploaded the new version to mentors. However, it still has the lintian warning about the debian/copyright file. Ah... I actually misread the lintian warning. W: bzrtools source: syntax-error-in-dep5-copyright line 8:

Bug#688289: marked as done (RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools)

2012-11-25 Thread Debian Bug Tracking System
Your message dated Sun, 25 Nov 2012 22:59:29 -0500 with message-id cal6k_aw5n1madukbrlxt2_ybwme9ylpqj4p00s6gcbg4oqq...@mail.gmail.com and subject line Re: Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools has caused the Debian Bug report #688289, regarding RFS:

Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools

2012-11-25 Thread Eric
Thanks for uploading the package. How should I contribute now? Should I keep checking for bug reports and new upstream releases? Also, any idea on when the package will be visible in Debian unstable? Eric -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of

Bug#688289: RFS: bzrtools/2.5+bzr786-3 [ITA] -- Bazaar VCS tools

2012-11-25 Thread Eric
Nevermind, I saw the messages on the mailing list. Eric -- 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/50b2f191.8090...@azrockets.org

How to specify a = X Y Depends (Was: Packaging GNU Health)

2012-11-25 Thread Andreas Tille
Hi Emilien, On Sat, Nov 24, 2012 at 11:54:59AM +0100, Emilien Klein wrote: ... As a general question: If package A depends on a specific set of releases (like in this case Tryton 2.4.X), how do we usually handle the case where the libraries are updated before the package depending on the

Re: How to specify a = X Y Depends (Was: Packaging GNU Health)

2012-11-25 Thread Michael Tautschnig
Hi all, Hi Emilien, On Sat, Nov 24, 2012 at 11:54:59AM +0100, Emilien Klein wrote: ... As a general question: If package A depends on a specific set of releases (like in this case Tryton 2.4.X), how do we usually handle the case where the libraries are updated before the package

Re: How to specify a = X Y Depends (Was: Packaging GNU Health)

2012-11-25 Thread Niels Thykier
On 2012-11-26 08:24, Michael Tautschnig wrote: Hi all, Hi Emilien, On Sat, Nov 24, 2012 at 11:54:59AM +0100, Emilien Klein wrote: ... As a general question: If package A depends on a specific set of releases (like in this case Tryton 2.4.X), how do we usually handle the case where the