Re: Wheezy update of libreoffice #2 (CVE-2016-1513)
Hi, On Thu, Aug 04, 2016 at 06:43:36AM +0200, Rene Engelhard wrote: > A (untested, except that the patch applies) source package is - as last time - > available on http://people.debian.org/~rene/libreoffice/wheezy I noticed Balint did some additional changes to deb7u7 (build-depends on fixed graphite2 - thanks for that), so this needs either be merged into my deb7u8 or I can redo it this evening... Regards, Rene
Re: Wheezy update of python-django?
Raphael Hertzog writes: > Yes, please. Wheezy security has version 1.4.5-1+deb7u17 Git has version 1.4.5-1+deb7u12 So far I haven't found the missing versions in between, however will keep looking. -- Brian May
Re: Wheezy update of python-django?
Brian May writes: > So far I haven't found the missing versions in between, however will > keep looking. It helps if you look in the correct place :-) http://snapshot.debian.org/package/python-django/ (I was getting confused and looking under archives.debian.org) -- Brian May
Security update of firefox-esr for Wheezy
Hello Mike, Thank you for preparing the security update of firefox-esr. I have just sent a security announcement for your update in Wheezy to the debian-lts-announce mailing list. If you want to take care of this next time, please follow our guidelines which we have outlined at [1]. If this is a burden for you, no problem, we will do our best and take care of the rest. In this case we would like to ask you to send a short reminder to debian-lts, so that we can prepare the announcement in a timely manner. Regards, Markus [1] https://wiki.debian.org/LTS/Development#Prepare_security_updates_for_Wheezy_LTS signature.asc Description: OpenPGP digital signature
Re: Security update of firefox-esr for Wheezy
On Thu, Aug 04, 2016 at 11:04:47AM +0200, Markus Koschany wrote: > Hello Mike, > > Thank you for preparing the security update of firefox-esr. I have just > sent a security announcement for your update in Wheezy to the > debian-lts-announce mailing list. If you want to take care of this next > time, please follow our guidelines which we have outlined at [1]. If > this is a burden for you, no problem, we will do our best and take care > of the rest. In this case we would like to ask you to send a short > reminder to debian-lts, so that we can prepare the announcement in a > timely manner. Heh, I hadn't realized that wasn't handled by standard DSAs, sorry about that. That these updates go through the same security-master doesn't help making it obvious they are different. Anyways, I'd rather not have more work to do, so if can send announcements, that works for me. Or you can deal with the backport from back to back. Please note that the next ESR bump (52) will require GCC 4.8, which is not in wheezy, so I won't be building ESR45 for wheezy past 45.8, presumably some time in April next year. Cheers, Mike
LTS version tracking
It looks (at least based on #833030) that the Debian BTS doesn't know about LTS version numbers of packages - since the graph thinks that all versions are affected when the submitter specifid the LTS release version in the report. If so, can this be fixed? (Please CC me on replies) Thanks, Dominic.
Re: LTS version tracking
On 04.08.2016 17:48, Dominic Hargreaves wrote: > It looks (at least based on #833030) that the Debian BTS doesn't know > about LTS version numbers of packages - since the graph thinks that all > versions are affected when the submitter specifid the LTS release > version in the report. > > If so, can this be fixed? > > (Please CC me on replies) Hello Dominic, thank you for raising this issue which I can confirm. The BTS administrators can probably give more insight into the inner workings of the BTS. Just off the top of my head you can mitigate this issue somehow by using found/notfound and fixed/notfixed commands. I know that we have a similar problem with DDPO and the PTS that don't list uploads to Wheezy LTS because they apparently don't know about them. I have no concrete solutions at the moment and I hope others on the list or the BTS admins can chime in here. Regards, Markus signature.asc Description: OpenPGP digital signature
Re: Security update of firefox-esr for Wheezy
Hi, On Thu, Aug 04, 2016 at 06:32:14PM +0900, Mike Hommey wrote: > On Thu, Aug 04, 2016 at 11:04:47AM +0200, Markus Koschany wrote: > > Hello Mike, > > > > Thank you for preparing the security update of firefox-esr. I have just > > sent a security announcement for your update in Wheezy to the > > debian-lts-announce mailing list. If you want to take care of this next > > time, please follow our guidelines which we have outlined at [1]. If > > this is a burden for you, no problem, we will do our best and take care > > of the rest. In this case we would like to ask you to send a short > > reminder to debian-lts, so that we can prepare the announcement in a > > timely manner. > > Heh, I hadn't realized that wasn't handled by standard DSAs, sorry about > that. That these updates go through the same security-master doesn't > help making it obvious they are different. > > Anyways, I'd rather not have more work to do, so if can send > announcements, that works for me. Or you can deal with the backport > from back to back. > > Please note that the next ESR bump (52) will require GCC 4.8, which is > not in wheezy, so I won't be building ESR45 for wheezy past 45.8, > presumably some time in April next year. The same is true for icedove. Since this is way before the end of Wheezy LTS (31st May 2018) I wonder if we should EOL Firefox/Icedove then or try to support this for longer? I have no idea what features of gcc-4.8 would be required, Mike do you know? Cheers, -- Guido
Re: Wheezy update of libreoffice #2 (CVE-2016-1513)
Hi, On Thu, Aug 04, 2016 at 09:12:04AM +0200, Rene Engelhard wrote: > I noticed Balint did some additional changes to deb7u7 (build-depends > on fixed graphite2 - thanks for that), so this needs > either be merged into my deb7u8 or I can redo it this evening... now done. Regards, Rene
Re: mysql and systemd
My apologies, this is incorrect. This is PEBKAC error. Sorry for the noise! - Chris On Thu, Aug 04, 2016 at 04:05:06PM -0400, Chris Frey wrote: > Hi, > > I noticed in the recent security updates that mysql-client-5.5 and > mysql-server-5.5 have a new dependency on systemd. > > Is this strictly required, or can these packages be rebuilt as they > were before? > > Thanks, > - Chris >
mysql and systemd
Hi, I noticed in the recent security updates that mysql-client-5.5 and mysql-server-5.5 have a new dependency on systemd. Is this strictly required, or can these packages be rebuilt as they were before? Thanks, - Chris
Re: Wheezy update of python-django?
> I have a version of python-django 1.4.22 for wheezy-security available > for testing at: > > https://people.debian.org/~bam/debian/pool/main/p/python-django/ I've had a quick play with this and everything seems to check out although I do not have any Django 1.4 (!) projects lying around to test against. Could you upload a debdiff too? Best wishes, -- Chris Lamb chris-lamb.co.uk / @lolamby
Re: Security update of firefox-esr for Wheezy
On Thu, Aug 04, 2016 at 07:50:28PM +0200, Guido Günther wrote: > Hi, > On Thu, Aug 04, 2016 at 06:32:14PM +0900, Mike Hommey wrote: > > On Thu, Aug 04, 2016 at 11:04:47AM +0200, Markus Koschany wrote: > > > Hello Mike, > > > > > > Thank you for preparing the security update of firefox-esr. I have just > > > sent a security announcement for your update in Wheezy to the > > > debian-lts-announce mailing list. If you want to take care of this next > > > time, please follow our guidelines which we have outlined at [1]. If > > > this is a burden for you, no problem, we will do our best and take care > > > of the rest. In this case we would like to ask you to send a short > > > reminder to debian-lts, so that we can prepare the announcement in a > > > timely manner. > > > > Heh, I hadn't realized that wasn't handled by standard DSAs, sorry about > > that. That these updates go through the same security-master doesn't > > help making it obvious they are different. > > > > Anyways, I'd rather not have more work to do, so if can send > > announcements, that works for me. Or you can deal with the backport > > from back to back. > > > > Please note that the next ESR bump (52) will require GCC 4.8, which is > > not in wheezy, so I won't be building ESR45 for wheezy past 45.8, > > presumably some time in April next year. > > The same is true for icedove. Since this is way before the end of Wheezy > LTS (31st May 2018) I wonder if we should EOL Firefox/Icedove then or > try to support this for longer? > > I have no idea what features of gcc-4.8 would be required, Mike do you > know? Some C++11 features it supports that GCC 4.7 doesn't. Mike
raphaelhertzog.com SEO Issues
Hi *raphaelhertzog.com*, My name is *Chris*, I'm a Search Specialist and was doing research for another client when I came across your site. I wanted to share a few major issues I discovered that are currently harming your website search rankings: 1• There are several 'bad' links pointing to your website. You can confirm this by searching your website on the major search engines search boxes - Google, Yahoo & Bing. You can simply search by inputting your link:raphaelhertzog.com 2• Your website has multiple undesirable technical errors such as HTML errors, broken links, missing image alt tags etc. Confirm this by searching your domain or website URL on validator.w3.org,brokenlinkcheck.com, feedthebot.com/tools/alt/ 3• Duplicate content has been found which can be adversely affecting your website. You can confirm this at copyscape.com 4• The number of high quality and/or authoritative links pointing to your site is extremely low. You can confirm this by visiting ahrefs.com We can help you fix these issues and get your website ranking on the 1st page of Google! *Let me know if you are interested and I'll send you a proposal with our prices, SEO strategy for raphaelhertzog.com, and results we have achieved for other clients. *Sounds interesting? Feel free to ask questions or you can provide your phone number for me to call you. Kind Regards, *Chris Pitts* *Search Specialist*
