similar to: Debian Buster 4.11 packages (almost)..

Hai, Well.. :-(( no.. Not yet. Boehoee :-( There are multiple things still going on which needs to be fixed first. Today i fixed a few more, and a new test build is currently running (again).. Pff. Done over 30 test builds already... And we are still finding more things atm. So i have to hold on with the 'almost', well its almost but time wise, I cant say anything atm. Sorry,

Knorrie and I just discussed our plans for sid and buster, on the phone. Here's my notes of the discussion. Plan is to upload Knorrie's 4.11 packages to experimental, to make them more public, while we fix the bugs in them. There's a list of Salsa issues and the BTS bugs list. This duplication is not ideal. We agreed that new things should go to the BTS. For now we'll keep

Hans van Kranenburg writes ("Re: Plans for buster"): > This can be done from tag debian/4.11.1_pre+1.733450b39b-1_exp1 (which > is right now the same as the master branch). Thanks for doing all this work. I have just sent it to experimental. I did some reviewing and diffing. I have some comments, or, at least, things I noticed. None of them were IMO blockers for experimental.

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: Plans for buster"): > On 08/23/2018 07:12 PM, Ian Jackson wrote: > > IDK if this > > should have its own deb. Putting it in the libxenstore one is > > probably tolerable. > > Yes, shipping a 4.x specific file in libxenstore3.0 (which happens now) > is not right. But, if the library ABI is independent from the 4.x >

On Mon, Jan 07, 2019 at 08:44:50AM +0000, Colin Watson wrote: > On Mon, Jan 07, 2019 at 01:58:19AM +0100, Hans van Kranenburg wrote: > > Ok great. Since I'm not using (and probably not going to use) the > > multi-stage multiboot things, this is harder for me to help with. > > With any luck I should be able to work that bit out myself, since I > think stable's Xen

Hi Debian Grub maintainer, In december, Xen PVH support has been committed in grub master: https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html The last pieces needed in the Linux kernel to boot PVH with grub2 landed in Linux 4.20. I asked our kernel team to carry those patches on top of the Linux 4.19 kernel that is going to ship in Buster, and that wish was granted:

Source: xen Severity: normal User: debian-lts at lists.debian.org Usertags: upstream-trixie X-Debbugs-Cc: debian-lts at lists.debian.org Dear xen maintainers, Testing (trixie) currently ships xen 4.17, which, according to the upstream support matrix [x], will get security support until 2025-12-12. The latest upstream release (4.19) will get security support until 2027-07-29. I believe it would

On 1/6/19 11:21 AM, Colin Watson wrote: > On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote: >> On 1/5/19 8:04 PM, Colin Watson wrote: >>> I think I'm OK with cherry-picking the relevant patch stack. Presumably >>> this would need to be in new grub-xen-pvh-bin / grub-xen-pvh binary >>> packages, as is usual for separate platform builds?

Hi Colin, Thanks for the quick reply. On 1/5/19 8:04 PM, Colin Watson wrote: > On Thu, Jan 03, 2019 at 01:02:47AM +0100, Hans van Kranenburg wrote: >> In december, Xen PVH support has been committed in grub master: >> https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html >> >> The last pieces needed in the Linux kernel to boot PVH with grub2 landed >>

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

Package: src:xen Version: 4.14.1+11-gb0b734a8b3-1 Severity: critical Justification: causes serious data loss X-Debbugs-Cc: debianbts at virtualzone.hu Dear Maintainer, after a clean install of bullseye/testing the xen dmesg shows the following message: (XEN) AMD-Vi: IO_PAGE_FAULT: 0000:01:00.1 d0 addr fffffffdf8000000 flags 0x8 I this is the sata device: 01:00.1 SATA controller: Advanced Micro

Hai Guys, ? The following has been done:?4.10.6?for Debian Buster (10) is ready. Short version of the changes: The settings are updated with latest Official Debian Samba packages, and its more focused on builds with python3. ? The changes logs of these changes, including the debian changes. ( see below ) Repo Info?: http://apt.van-belle.nl/ Buildlogs?: http://downloads.van-belle.nl/ ? ---?

Hai, The latest update is now online. Debian Buster Samba 4.12.5 + extra patches for amd64/i386/armhf. samba (2:4.12.5+dfsg-2.1buster1) buster; urgency=medium * Rebuild from Debian Sid for Debian Buster * d/control, re-added acl as Recommands to samba package * d/control added libicu-dev,add Missing support for Unicode normalisation. * d/patches, fix debian bug #964165 with

Package: xen-utils-4.11 Severity: important Dear Maintainer, We have discovered that the `pygrub` binaries, expected under `/usr/lib/xen-4.11/bin`, are no longer present in the xen-utils-4.11 package. Reviewing the source package reveals that the binary is still present under `tools/pygrub/src/pygrub`, however it is not referenced anywhere obvious in the package build configurations, nor is

Hello, I have found out that a domain administrator is always mapped to root in the UNIX filesystem: drwx------ 2 jive smbguests 1024 2004-12-23 18:59 jive drwx------ 13 salsa smbusers 1024 2004-12-23 18:58 salsa drwx------ 13 root smbadmins 1024 2004-12-23 18:56 tango jive is a domain guest user, salsa a domain user and tango a domain administrator. Is it possible to change the root

On 02/12/2019 15:21, Sylvestre Ledru wrote: > yaml-bench is shipping in libclang-common-9-dev Ok possible. Though, it adds an unnecessary 46MB to my docker image. > It should be indeed in llvm-9-dev instead. This would hide the problem, right. I am not sure it's is a good solution. Where can we review the build process for the apt packages? On 02/12/2019 15:21, Sylvestre Ledru wrote:

Hai Sam, Try the following, 1 ) ignore these messages : > If I create a new GPO The "samba-tool ntacl sysvolcheck" command return > this error : >root at S4:~# samba-tool ntacl sysvolcheck > ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - > ..... 2) add this line to you sysvol share acl_xattr:ignore system acls =

Hello, Some time ago I created some merge request on salsa for debian-xen: https://salsa.debian.org/xen-team/debian-xen/-/merge_requests?scope=all&state=opened Created 8 months ago, it's seem it's doesn't get merged, I would like to know how merge request are handled on salsa.d.o for debian-xen ? Thanks. Ps: I'm not registered on this mailings lists.

On Mon, Nov 11, 2024 at 06:03:22PM +0100, Alexandre GRIVEAUX wrote: > Hello, > > Some time ago I created some merge request on salsa for debian-xen: > > https://salsa.debian.org/xen-team/debian-xen/-/merge_requests?scope=all&state=opened These looks like you want to send them upstream instead. -- WBR, wRAR -------------- next part -------------- A non-text attachment was