Bug#675060: amsn depends on libfarstream-0.1-0 but libgstfarsight0.10-0 has replaced it
Source: amsn Version: 0.98.3-2+b1 Severity: important Dear Maintainer, It seems that amsn can no longer be installed on wheezy due to libfarstream-0.1-0 being replaced by libgstfarsight0.10-0. I've noticed in debports they mark libgstfarsight0.10-0. as the dependency instead of libfarstream-0.1-0. Can this change be applied to the offical repos? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (750, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675060: amsn depends on libfarstream-0.1-0 but libgstfarsight0.10-0 has replaced it
Hi Kitty, Unfortunately the amsn package was dropped from Wheezy at the QA team and maintainer's request because of outstanding security issues, and there hadn't been a new upstream release since 2010. Having said that, it looks like upstream just this past week released 0.98.9... I wonder if the new release takes care of the previous concerns, or if it's not too late to package the new version before the freeze mid-June? I'd certainly like to see amsn stay around for a little longer; I'm not as happy with any other MSN/WLM client I've tried and the package still had ~3000 users on popcon. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675060: amsn depends on libfarstream-0.1-0 but libgstfarsight0.10-0 has replaced it
Hi Steven, I just talked to one of the devs in regards with the Denial of Service bug s/he said it has been fixed in SVN for two years and the new release does indeed have said fix. It'd be nice to have the new release packaged up and the dependency issue fixed. The dev I spoke to also said s/he was working on repackaging amsn for debian but due to lack of time has not done so yet, don't know if that information helps. On an unrelated note I can't seem to see this bug on the http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=amsn page yet. I've only made a few bug reports to debian bug tracker so far and they normally show up rather quickly. Thanks for your time. On 30 May 2012 03:24, Steven Chamberlain ste...@pyro.eu.org wrote: Hi Kitty, Unfortunately the amsn package was dropped from Wheezy at the QA team and maintainer's request because of outstanding security issues, and there hadn't been a new upstream release since 2010. Having said that, it looks like upstream just this past week released 0.98.9... I wonder if the new release takes care of the previous concerns, or if it's not too late to package the new version before the freeze mid-June? I'd certainly like to see amsn stay around for a little longer; I'm not as happy with any other MSN/WLM client I've tried and the package still had ~3000 users on popcon. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675060: amsn depends on libfarstream-0.1-0 but libgstfarsight0.10-0 has replaced it
Hi, On Wed, May 30, 2012 at 05:13:12AM +1000, Kitty PC wrote: Hi Steven, I just talked to one of the devs in regards with the Denial of Service bug s/he said it has been fixed in SVN for two years and the new release does indeed have said fix. It'd be nice to have the new I didn't know this. I was so busy that I wasn't able to look for this properly. release packaged up and the dependency issue fixed. The dev I spoke to also said s/he was working on repackaging amsn for debian but due to lack of time has not done so yet, don't know if that information helps. I still have the previous source code with the debian/ directory. On 30 May 2012 03:24, Steven Chamberlain ste...@pyro.eu.org wrote: Hi Kitty, Unfortunately the amsn package was dropped from Wheezy at the QA team and maintainer's request because of outstanding security issues, and there hadn't been a new upstream release since 2010. Having said that, it looks like upstream just this past week released 0.98.9... I wonder if the new release takes care of the previous concerns, or if it's not too late to package the new version before the freeze mid-June? I think it is a little late. For having aMSN again in the archive, it is needed to open an ITP report, then package it, upload it, and wait until it gets approved again by FTP masters. And given that on mid-June the freeze will happen, and the package needs to be 10 days in unstable to be eligible in testing. So I believe it is unlikely to be ready at time. I'd certainly like to see amsn stay around for a little longer; Â I'm not as happy with any other MSN/WLM client I've tried and the package still had ~3000 users on popcon. If there is still people interested, I can go through the procedure I wrote above and prepare a backport for wheezy later. It is quite difficult to keep working on a package which has many alternatives as this one for having compelling reasons about why we should keep it in Debian. By the way, does any of you have an idea of the status of aMSN2? Regards, -- Muammar El Khatib. Linux user: 403107. Key fingerprint = 90B8 BFC4 4A75 B881 39A3 1440 30EB 403B 1270 29F1 http://muammar.me | http://proyectociencia.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675060: amsn depends on libfarstream-0.1-0 but libgstfarsight0.10-0 has replaced it
Hi, On 29/05/12 20:13, Kitty PC wrote: I just talked to one of the devs in regards with the Denial of Service bug s/he said it has been fixed in SVN for two years I think I see the relevant commit in SVN; it might have been fixed but I don't think there was an actual release containing that fix until now. And it's not stated very clearly in the release announcement; it would really make things easier for package maintainers, QA and security teams (not just Debian but other distros too) if the release had a more detailed changelog ideally mentioning the CVE ID of that DoS vulnerability. Anyway, thanks a lot for passing along the info you got from upstream. [...] It'd be nice to have the new release packaged up and the dependency issue fixed. The dev I spoke to also said s/he was working on repackaging amsn for debian but due to lack of time has not done so yet If nobody else gets around to it I could *maybe* try to package the new upstream version myself; I could use some practice at this, and I would certainly use it personally. On an unrelated note I can't seem to see this bug on the http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=amsn page yet. Follow the link through to src:amsn and it's there (filed against the source package, which is probably correct since your report was about build dependencies). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675060: amsn depends on libfarstream-0.1-0 but libgstfarsight0.10-0 has replaced it
To Steven, Follow the link through to src:amsn and it's there (filed against the source package, which is probably correct since your report was about build dependencies). Ah thanks I think it was luck I got that right though, will remember it for the future. On 30 May 2012 05:41, Steven Chamberlain ste...@pyro.eu.org wrote: Hi, On 29/05/12 20:13, Kitty PC wrote: I just talked to one of the devs in regards with the Denial of Service bug s/he said it has been fixed in SVN for two years I think I see the relevant commit in SVN; it might have been fixed but I don't think there was an actual release containing that fix until now. And it's not stated very clearly in the release announcement; it would really make things easier for package maintainers, QA and security teams (not just Debian but other distros too) if the release had a more detailed changelog ideally mentioning the CVE ID of that DoS vulnerability. Anyway, thanks a lot for passing along the info you got from upstream. [...] It'd be nice to have the new release packaged up and the dependency issue fixed. The dev I spoke to also said s/he was working on repackaging amsn for debian but due to lack of time has not done so yet If nobody else gets around to it I could *maybe* try to package the new upstream version myself; I could use some practice at this, and I would certainly use it personally. On an unrelated note I can't seem to see this bug on the http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=amsn page yet. Follow the link through to src:amsn and it's there (filed against the source package, which is probably correct since your report was about build dependencies). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
