Bug#768022: mercurial: 3.2 has been released
Hi Faheem, On Tue, Nov 11, 2014 at 06:04:55PM +0530, Faheem Mitha wrote: On Thu, 6 Nov 2014, Javi Merino wrote: On Tue, Nov 04, 2014 at 02:58:31PM +0530, Faheem Mitha wrote: Package: mercurial Version: 3.1.2-1~bpo70+1 Severity: wishlist Dear Maintainer, Hi Faheem, Please consider packaging 3.2. I can build it myself, but the Debian patches have changed enough since the last release that they are no longer trivial to re-sync. If you could just refresh the patches, that would be helpful. Thanks. It's not as easy as refreshing the patches as you have seen. I'm working on it and I hope to upload it before Sunday. It will go to experimental though. I missed your email. I just saw it now. It looks like you have just uploaded to experimental. I've seen that you are using the backported version. As Jessie will release with 3.1.2, wheezy-backports will stay with 3.1.2. I can upload 3.2 (well, 3.2.1, which shall be uploaded soon) to wheezy-backports-sloppy if you are interested in it. If you need help with the Debian packaging, let the community know. There are people who can help. The package is team-maintained, I'm just the most regular uploader. Other people have uploaded mercurial when I was unavailable. So yes, I know there is a community and no, I'm not *the* maintainer but *a* maintainer. Cheers, Javi signature.asc Description: Digital signature
Bug#768022: mercurial: 3.2 has been released
On Fri, 14 Nov 2014, Javi Merino wrote: Hi Faheem, I've seen that you are using the backported version. As Jessie will release with 3.1.2, wheezy-backports will stay with 3.1.2. I can upload 3.2 (well, 3.2.1, which shall be uploaded soon) to wheezy-backports-sloppy if you are interested in it. Sure, I'm interested, and I expect other people are too. I think the Mercurial project has itself considered providing Debian backports, but that hasn't happened so far, presumably due to a lack of manpower. If you need help with the Debian packaging, let the community know. There are people who can help. The package is team-maintained, I'm just the most regular uploader. Other people have uploaded mercurial when I was unavailable. So yes, I know there is a community and no, I'm not *the* maintainer but *a* maintainer. Cheers, Ok. I don't know the current situation of the team. Just saying. Regards, Faheem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768022: mercurial: 3.2 has been released
Hi Javi, On Thu, 6 Nov 2014, Javi Merino wrote: On Tue, Nov 04, 2014 at 02:58:31PM +0530, Faheem Mitha wrote: Package: mercurial Version: 3.1.2-1~bpo70+1 Severity: wishlist Dear Maintainer, Hi Faheem, Please consider packaging 3.2. I can build it myself, but the Debian patches have changed enough since the last release that they are no longer trivial to re-sync. If you could just refresh the patches, that would be helpful. Thanks. It's not as easy as refreshing the patches as you have seen. I'm working on it and I hope to upload it before Sunday. It will go to experimental though. I missed your email. I just saw it now. It looks like you have just uploaded to experimental. If you need help with the Debian packaging, let the community know. There are people who can help. Regards, Faheem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768022: mercurial: 3.2 has been released
On Tue, Nov 04, 2014 at 02:58:31PM +0530, Faheem Mitha wrote: Package: mercurial Version: 3.1.2-1~bpo70+1 Severity: wishlist Dear Maintainer, Hi Faheem, Please consider packaging 3.2. I can build it myself, but the Debian patches have changed enough since the last release that they are no longer trivial to re-sync. If you could just refresh the patches, that would be helpful. Thanks. It's not as easy as refreshing the patches as you have seen. I'm working on it and I hope to upload it before Sunday. It will go to experimental though. Cheers, Javi signature.asc Description: Digital signature
Bug#768022: mercurial: 3.2 has been released
Package: mercurial Version: 3.1.2-1~bpo70+1 Severity: wishlist Dear Maintainer, Please consider packaging 3.2. I can build it myself, but the Debian patches have changed enough since the last release that they are no longer trivial to re-sync. If you could just refresh the patches, that would be helpful. Thanks. Regards, Faheem Mitha -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), (50, 'unstable'), (50, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mercurial depends on: ii libc6 2.13-38+deb7u6 ii mercurial-common 3.1.2-1~bpo70+1 ii python2.7.3-4+deb7u1 ii ucf 3.0025+nmu3 Versions of packages mercurial recommends: ii openssh-client 1:6.0p1-4+deb7u2 Versions of packages mercurial suggests: ii kdiff3 0.9.96-4 pn qct none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
