search for: dgits

Moritz Muehlenhoff writes ("Re: Xen package security updates for jessie 4.4, XSA-213, XSA-214"): > On Thu, May 04, 2017 at 05:59:18PM +0100, Ian Jackson wrote: > > Should I put jessie-security in the debian/changelog and dgit push it > > (ie, from many people's pov, dput it) ? > > Yes, the distribution line should be jessie-security, but please send > a

Summary: I have tried the packaging-only repo and I really don't like it at all. I don't know how anyone copes with this - such hard work! IMO we should switch to git-debrebase. (As an alternative, if you don't trust git-debrebase because it's my own tool, gbp pq would be better, too, even though it's not as good as git-debrebase.) Particularly, now that we have more people

I have now finished totally rewriting the Xen package in Debian, from scratch. Amazingly as soon as I got a package which was lintian-clean and would install, it worked first time ! I have generated 18 patches to go upstream which I have sent to xen-devel. There are two more, xenstore ABI patches, which need a bit of tidying up. There is still room for improvement but it is now clearly ready

Hans van Kranenburg writes ("Re: git workflow, redux"): > On 08/23/2018 08:07 PM, Ian Jackson wrote: > > I think git-debrebase is going to be easier for all these things than > > the current approach. > > Ok, let's try it! Thanks a lot for doing the above writeup. Great, thanks. (I hope it's OK that I have snipped most of your responses to the discussion,

Moritz Muehlenhoff writes ("Re: Xen package security updates for jessie 4.4, XSA-213, XSA-214"): > On Thu, May 04, 2017 at 05:06:07PM +0100, Ian Jackson wrote: > > I have fixed these in stretch but the jessie package remains unfixed. > > I think I may be able to find some backports somewhere. Would that be > > useful ? Is anyone else working on this ? > >

FYI I will have an upload ready RSN. Where should I send it ? Matthew Vernon has offered to test my amd64 binaries. I will test the i386 packages myself. Ian.

Hi Ian, team, In the week of Feb 23 (time flies!:), we had a very productive day \o/ working on the stretch security/stable package and some irc discussions in oftc #debian-xen which ended with an open end. Ian, you were a bit surprised that 1) my debian-xen repo started with an import of a 4.8 package 2) it was not a git-pbuilder style repo with upstream source included, and asked me to at

Moritz Muehlenhoff writes ("Re: Xen package security updates for jessie 4.4, XSA-213, XSA-214"): > Yes, the distribution line should be jessie-security, but please send > a debdiff to team at security.debian.org for a quick review before > uploading (I have no idea whether dgit supports security-master). Here is the proposed debdiff (actually, a git diff) for xen in jessie. My

This is awesome! What needs to be done before this can make it to unstable? I’d love to help if there’s anything I can do. Stephen On Fri, Oct 5, 2018 at 8:00 PM Hans van Kranenburg <hans at knorrie.org> wrote: > On 10/05/2018 08:04 PM, Ian Jackson wrote: > > I have now finished totally rewriting the Xen package in Debian, from > > scratch. Amazingly as soon as I got a

Ian Jackson writes ("64bit PV guest breakout [XSA-213]"): > Source: xen > Version: 4.4.1-9 > Severity: important > Tags: security upstream fixed-upstream > > See > https://xenbits.xen.org/xsa/advisory-213.html Ian Jackson writes ("grant transfer allows PV guest to elevate privileges [XSA-214]"): > Source: xen > Version: 4.4.1-9 > Severity:

Hi all I saw in the CDR stocked in mysql as well as those in the csv file that some time, the src field is the same as the dst field which is the extension. When does it happens. Here, we have 4 dgits extensions and most of the time the dst field is the extension and the src field is the 10 digit customer phone number. Do you know when does this happens ?? Thanks Ruddy Gbaguidi http://www.astblog.com

Hi All, Not sure exactly a memory leak or not. I was porting my nagios from Redhat 7.3 to CentOS 5.4 and I observed the memory usage was gradually increasing on the new centos box. When I ran all my perl plugins with Valgrind -3.2.1, all the plugins complained about a memory leak. Not sure if it's a leak or if its fault with valgrind way of evaluating things. I have attached