similar to: Current status of Xen 3.0 package

Package: ftp.debian.org Severity: normal Hello, Please consider removing xen. New xen-3.0 splited packages are upcoming, making this one obsolete. Cheers, -- Julien Danjou // <julien@danjou.info> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // The more we fly, the more we climb, the more we know that heaven is a lie. -------------- next part

xcb-util 0.3.2 is available git tag 0.3.2 Changelog ========= Jonathan Landis (1): Fix copyright statement Julien Danjou (4): build: add check for xproto >= 7.0.8 keysyms: use xcb_key_lookup_t type for col paramter icccm: fix gravity proto Release xcb-util 0.3.2 Peter Harris (2): Don't call exit() in xcb_aux_get_depth; return 0 instead. Fix the

xcb-util 0.3.1 is now available git tag 0.3.1 Changelog ========= Henning Sten (2): introduce function xcb_atom_get (essentially a synchronous xcb_intern_atom, use it only on non-performance critical execution paths) add more verbose explanation of the purpose of "encoding" parameter in doxygen documentation tag Julien Danjou (5): icccm: add some comment on text

libxcb 1.2 is now available, lucky you. git tag 1.2 Changelog ========= Julien Danjou (2): Stop providing autogenerated files in tarball Release libxcb 1.2 Download ======== http://xcb.freedesktop.org/dist/libxcb-1.2.tar.gz md5: f55c731d32ec1a555c77ebbbc8f386aa sha1: 9c1c256b9bcfe78cb99a15b567ca00ffb9a45c1e http://xcb.freedesktop.org/dist/libxcb-1.2.tar.bz2 md5:

Hi, I'd like to know if the following is normal. I've a setup with 2 namespace (private/public) where each user can use subscriptions. This problem is triggered by claws-mail, which uses LSUB to get subscribed mailboxes: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. . login user password . namespace * NAMESPACE (("INBOX."

Hello, I have set up a build machine for Xen. Currently it builds the version checked out from Subversion with the latest testing version from Xen repository for Sarge every night. deb http://naquadah.org/~jd/debian/xen stable main I plan to upload real and official backports to backports.org as soon as we will upload a version to sid. Any comment welcome, Cheers, -- Julien Danjou

Hello, I asked Aurelien Jarno from the Debian glibc team about our /lib/tls problem. It gave me a little help: # ldd /bin/echo libc.so.6 => /lib/tls/libc.so.6 (0x40021000) # touch /etc/ld.so.hwnocap # ldd /bin/echo libc.so.6 => /lib/libc.so.6 (0x40021000) I think this could help us. -- Julien Danjou .''`. Debian Developer : :' :

On Tue, Feb 14, 2006 at 10:17:14AM +0100, Guido Trotter wrote: Hello, > Do you mean svn or some other new revision control system, right? Yes, please, use subversion, not CVS anymore :) Reading http://svn.debian.org/, we should ask for a repository. I think the project admin should do this ;) > Anyway, yeah, I think the debian directory should be fine! We can still use > dpatch if we

Hello, So, I just built our packages. Everything seems to be fine. I plan to do an upgrade from Xen 2.0.6 this week end. Is there anything that we have to do before uploading this package? Some point we haven't treated yet? -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C

reassign 381481 aptitude thanks > On Fri, Aug 11, 2006 at 06:54:43AM -0700, Daniel Burrows wrote: > > > | ...................... > > > | rval == -1080447064 > > > | > > > | now2.tv_sec == 1155053066 > > > | now.tv_sec + 2 == 1155053066 > > > | now2.tv_usec == 882203 > > > | now.tv_usec == 887661 > > >

Hello, We [the Debian Xen package team] are currently working on Xen packages, and are planning to include them into Debian. A current issue in Xen, is the libc problem. From the Xen wiki [1]: "Xen uses segmentation to provide protection of the memory used for the hypervisor. This results in some performance issues since wrap-around segments as used by glibc need expensive extra handling.

Hello, The current dependancy on hotplug|udev (>= 0.59) seems bad. As far as I remember, last week, when I tried to install Ralph packages, I got an error from hotplug/udev and I had to use udev from backports.org Anyone know which version of udev/hotplug we will have to depends on ? Maybe we could simply rely on a recent udev dependancy, because afaik udev now provides hotplug. -- Julien

Hi, First, thanks for this awesome piece of software. I've just upgraded to latest dovecot, aka 1.2. I've a problem. I've started using Sieve, and everything works fine, I already received a thousand of mails without any problem. However, there's one mail which is stuck in the postfix queue because of that: Jul 8 18:47:51 prometheus dovecot: deliver(jd at danjou.info):

Package: xen-3.0 Version: 3.0.2+hg9697-1 Severity: important Hello, There was a problem while autobuilding your package: > Automatic build of xen-3.0_3.0.2+hg9697-1 on avidan by sbuild/i386 0.49 > Build started at 20060725-0410 > ****************************************************************************** ... > CFLAGS="-O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall

Hi everybody! At least xen 3.0 packages seem to be working, tested, and in a pretty good shape... (I haven't personally tested xen-unstable, so I cannot say) I propose releasing rev150 in unstable or at least experimental in the next few days... No, this is not a late april's fool... :D Comments? Ideas? Suggestions? Rants? Guido

Hello, We''ve recently started seeing several domUs on multiple machines losing all network connectivity. At least one of these machines (since they are customer machines I can''t verify it for all of them) give the error: $ sudo ifup eth0 eth0: full queue wasn''t stopped! About the only Google hit for this message is:

As a release manager asked us to do that, we should remove the kernel patch from the packaging... As I said I'm not completely against removing it, if we distribute it on our website and point people to it in some documentation! The internet is just there, so what would the matter be? If nobody is against this course of action I'm going to move the patch outside of the debian directory,

Hi folks With the lack of responses to my restructuring the last weeks, it looks like pkg-xen is dead. Now, what to do? My favorite is to merge it into the kernel repository where I have my infrastructure (archive and autobuilders for snapshots for example) to properly work on it. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5204 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060927/7204cce9/smime.bin

Hi! Can anybody explain how Xen deals with time? On traditional, non-virtualized systems I run an ntpd on every system to keep the time accurate. But what to do on xenified systems? Do all the domU''s get the time from dom0 meaning it is sufficient to run an ntpd there or do I have it to setup in every domU? Thanks for your help! Kind regards, Stephan