Displaying 20 results from an estimated 10000 matches similar to: "xen_4.17.5+23-ga4e5191dc0-2_source.changes REJECTED"
2025 Feb 09
0
xen_4.17.5+23-ga4e5191dc0-2_source.changes ACCEPTED into proposed-updates->stable-new
Thank you for your contribution to Debian.
Mapping bookworm to stable.
Mapping stable to proposed-updates.
Accepted:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 26 Jan 2025 22:42:25 +0100
Source: xen
Architecture: source
Version: 4.17.5+23-ga4e5191dc0-2
Distribution: bookworm
Urgency: medium
Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org>
2025 Feb 09
0
Processing of xen_4.17.5+23-ga4e5191dc0-2_source.changes
xen_4.17.5+23-ga4e5191dc0-2_source.changes uploaded successfully to localhost
along with the files:
  xen_4.17.5+23-ga4e5191dc0-2.dsc
  xen_4.17.5+23-ga4e5191dc0-2.debian.tar.xz
Greetings,
	Your Debian queue daemon (running on host usper.debian.org)
2025 Feb 09
0
Bug#1095623: bookworm-pu: package xen/4.17.5+23-ga4e5191dc0-2
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian.org at packages.debian.org
Usertags: pu
X-Debbugs-Cc: xen at packages.debian.org, hans at knorrie.org, maxi at daemonizer.de
Control: affects -1 + src:xen
[ Reason ]
Linux 6.12 changed the way it xz compresses the kernel [1]. This broke direct
kernel boot in bookworm xen for kernels 6.12 or newer. It only affects
2024 Dec 29
0
xen_4.17.5-1~deb12u1_source.changes REJECTED
xen - superseded; maintainer's request
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL:
2013 Mar 15
0
[PATCH 4.1] Add DomU xz kernel decompression
I have just applied this to staging-4.1.  Since my own backport and
Bastian''s were entirely identical, I haven''t tested it other than to
compile it...
Thanks,
Ian.
commit 5e73e3548ce70e433a03843ac4fc21a49277baad
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date:   Fri Mar 15 18:09:51 2013 +0000
    Add DomU xz kernel decompression
    
    Signed-off-by: Jan Beulich
2023 Feb 05
1
xen_4.17.0+24-g2f8851c37f-1_multi.changes REJECTED
Hi Ian,
On 05-02-2023 14:06, Ian Jackson wrote:
> Sorry again for being an idiot, but where should we have checked, to
> avoid such a mistake in the future ?  I thought this kind of thing
> would appear on tracker but
>     https://tracker.debian.org/pkg/xen
> doesn't show it now.
ocaml is a bit weird, it has a permanent tracker: 
2024 Dec 21
0
xen_4.19.1-1~exp3_source.changes REJECTED
Source-only uploads to NEW are not allowed.
binary:libxencall1 is NEW.
binary:libxendevicemodel1 is NEW.
binary:libxenevtchn1 is NEW.
binary:libxenforeignmemory1 is NEW.
binary:libxengnttab1 is NEW.
binary:libxenhypfs1 is NEW.
binary:libxenstore4 is NEW.
binary:libxentoolcore1 is NEW.
binary:libxentoollog1 is NEW.
===
Please feel free to respond to this email if you don't understand why
2018 Aug 23
2
xen_4.11.1~pre+1.733450b39b-1~exp1_multi.changes REJECTED
xen source: lintian output: 'license-problem-gfdl-invariants stubdom/grub.patches/00cvs invariant part is: with no invariant sections, with the front-cover texts being a gnu manual, and with the back-cover texts as in (a) below', automatically rejected package.
xen source: If you have a good reason, you may override this lintian tag.
xen-utils-4.11: lintian output:
2025 May 24
0
Bug#1106420: xen-utils-common: block-iscsi script doesn't work when iqn is a prefix of an existing iqn
Package: xen-utils-common
Version: 4.17.5+23-ga4e5191dc0-1+deb12u1
Severity: normal
two issues with block-iscsi
1. If the iqn that is being used as a disk device is a prefix of an 
existing in use iqn then xl create will fail with
libxl: error: libxl_device.c:1337:device_hotplug_child_death_cb: script: Device already opened
My fix is to match a space before and after the iqn.
iscsiadm -m
2024 Dec 28
1
Your xen stable upload
Hi,
On 28/12/2024 22:43, Adam D. Barratt wrote:
> On Sun, 2024-08-25 at 15:59 +0200, Hans van Kranenburg wrote:
>> Hi Adam,
>>
>> On 8/25/24 15:26, Adam D. Barratt wrote:
>>>
>>> I noticed that there's a xen upload in the stable-new queue, which
>>> claims to have been uploaded by you.
>>>
>>> I'm afraid that we can't
2006 Mar 04
1
xen_3.0.1-2_i386.changes REJECTED
Rejected: xen_3.0.1-2.dsc refers to xen_3.0.1.orig.tar.gz, but I can't find it in the queue or in the pool.
===
If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.
2006 Apr 06
0
xen-3.0_3.0.1+hg8762-1_i386.changes REJECTED
Hi Maintainer,
rejected, due to incomplete debian/copyright file.
There is at least tools/xenstore which has a mixture of LGPL and GP
attached, but you never mention that.
Another example is tools/vtpm_manager.
Please list all different licenses used with their (C) holder.
-- 
bye Joerg
===
If you don't understand why your files were rejected, or if the
override file requires editing,
2006 Nov 02
0
xen-3.0_3.0.3-0-2_i386.changes REJECTED
Rejected: md5sum for /org/ftp.debian.org/ftp/pool/main/x/xen-3.0/xen-3.0_3.0.3-0.orig.tar.gz doesn't match xen-3.0_3.0.3-0-2.dsc.
Rejected: size for /org/ftp.debian.org/ftp/pool/main/x/xen-3.0/xen-3.0_3.0.3-0.orig.tar.gz doesn't match xen-3.0_3.0.3-0-2.dsc.
Rejected: 'dpkg-source -x' failed for xen-3.0_3.0.3-0-2.dsc [return code: 6400].
 [dpkg-source output:] dpkg-source: error:
2011 Apr 15
0
xen_4.1.0-2_amd64.changes REJECTED
Reject Reasons:
xen-utils-4.1: lintian output: 'statically-linked-binary ./usr/lib/xen-4.1/boot/hvmloader', automatically rejected package.
xen-utils-4.1: If you have a good reason, you may override this lintian tag.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
2012 Jan 04
0
xen-api_1.3-14_amd64.changes REJECTED
Reject Reasons:
xcp-xe_1.3-14_amd64.deb: deb contents timestamp check failed [<type 'exceptions.NameError'>: global name 'MTime' is not defined]
xcp-squeezed_1.3-14_amd64.deb: deb contents timestamp check failed [<type 'exceptions.NameError'>: global name 'MTime' is not defined]
python-xenapi_1.3-14_all.deb: deb contents timestamp check failed [<type
2012 Jan 08
0
xen-api_1.3-15_amd64.changes REJECTED
Reject Reasons:
xcp-xapi_1.3-15_amd64.deb: deb contents timestamp check failed [<type 'exceptions.NameError'>: global name 'Name' is not defined]
libxenapi-ocaml-dev_1.3-15_amd64.deb: deb contents timestamp check failed [<type 'exceptions.NameError'>: global name 'Name' is not defined]
xcp-v6d_1.3-15_amd64.deb: deb contents timestamp check failed
2012 Aug 18
0
xen_4.0.1-5.3_amd64.changes REJECTED
Version check failed (source=xen, version=4.0.1-5.3, other-version=4.0.1-5.3, suite=proposed-updates)
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
2013 Jun 15
0
xen_4.2.2-1_amd64.changes REJECTED
xen source: lintian output: 'missing-build-dependency dpkg-dev (>= 1.16.1~)', automatically rejected package.
xen source: If you have a good reason, you may override this lintian tag.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
2023 Feb 05
1
xen_4.17.0+24-g2f8851c37f-1_multi.changes REJECTED
Hi Maximilian,
there is an ocaml stack rebuild[1] at them moment, where xen is a part of.
So please upload to experimental.
Thanks!
 Thorsten
[1] https://release.debian.org/transitions/html/ocaml.html
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
2024 Dec 28
1
Your xen stable upload
On Sun, 2024-08-25 at 15:59 +0200, Hans van Kranenburg wrote:
> Hi Adam,
> 
> On 8/25/24 15:26, Adam D. Barratt wrote:
> > 
> > I noticed that there's a xen upload in the stable-new queue, which
> > claims to have been uploaded by you.
> > 
> > I'm afraid that we can't accept it currently, because it is a newer
> > version than is currently