Re: Release notes addition for Xen support in Debian
Hi, On Tue Dec 28, 2010 at 15:34:21 +0800, Thomas Goirand wrote: Hi, I intend to have the attached document added to the Squeeze release notes. Also, what's the way to have it included? Should I send it as a wishlist bug to the release-notes package, or something like that? In general I support this. Those are changes worth mentioning. On the other hand your text reads more like a howto, which IMHO should be content for wiki.debian.org. Maybe have the release notes linking a wiki document instead? Could others please give me comments on this? Also, some correction for my (poor) English would be welcome when/if you spot issues. You are aware that we have debian-l10n-engl...@l.d.o for exactly that reason? Also i spotted that some of your wording is quite negative (Unfortunaly, As a consequence, Another thing that you have to take care about, ...). I would like to suggest we come up with at least a neutral wording here. As I am not a native english speaker either, I took the liberty to Cc debian-l10n-engl...@l.d.o for a help of rewording the whole text. Cheers, Martin | 4.7.4. Upgrading with Xen installed, and Kernel enumeration order issue with | Xen | | In Lenny, using grub legacy, the following kernel order was respected: - Xen | hypervisor with Xen dom0 kernel - Normal (eg: without dom0 support) kernel - | Xen dom0 kernel (without they hypervisor) | | This order was the natural expected one, because if you installed Xen, it will | simply boot the hypervisor and it's dom0 by default as expected. | | Unfortunately, in Squeeze, when running with Grub2, this isn't what is | happening. By default, the order is the exact opposite: - Xen dom0 kernel | (without they hypervisor) - Normal (eg: without dom0 support) kernel - Xen | hypervisor with Xen dom0 kernel | | As a consequence, if you have Xen installed and expect to boot with it by | default, you have to tweak grub2 configuration. One of the way to hack before | the grub maintainers can fix it the proper way could be to simply do: | | ln -s 20_linux_xen /etc/grub.d/09_linux_xen_first dpkg-reconfigure grub-pc | | so that Xen is loaded first, by default, when using Grub2. | | Another thing that you have to take care about when upgrading from Lenny, is | that currently, Xen isn't upgraded to the 4.0 version that you should be | expecting in Squeeze. So, after you finished the dist-upgrade, it is advised to | check that Xen 4.0 and the corresponding dom0 kernel are installed. Under the | 64 bits architecture, the following command will fix this: | | apt-get install xen-utils-common xen-utils-4.0 xenstore-utils libxenstore3.0 | xen-hypervisor-4.0-amd64 linux-image-2.6.32-5-xen-amd64 | | Here is the corresponding for 32 bits: | | apt-get install xen-utils-common xen-utils-4.0 xenstore-utils libxenstore3.0 | xen-hypervisor-4.0-i686 linux-image-2.6.32-5-xen-i686 | | Also, if you require HVM support, you will need to install the Xen Qemu device | model, which is now a separate package: | | apt-get install xen-qemu-dm-4.0 | | It is also important to notice that your domU wont be able to use sda1 (for | example) as device name for their HDD. This naming scheme has been removed from | Xen because of a request from the mainline kernel maintainers. Instead, you | should use xvda1 (as a corresponding example) instead. | | -- Martin Zobel-Helas zo...@debian.org | Debian System Administrator Debian GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101228082316.ga17...@ftbfs.de
Re: amavisd-new maintainer
On 17 December 2010 08:10, Adam D. Barratt a...@adam-barratt.org.uk wrote: Unblocked; thanks. Ok, looks like that got in. Thank you everybody. -- Brian May br...@microcomaustralia.com.au -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikbede8wfwtravepoq351apavi+tsg9g8pmm...@mail.gmail.com
Bug#608174: unblock: modemmanager/0.4+git.20100624t180933.6e79d15-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package modemmanager
I contains a single fix for Nokia N900. (#607982)
The patch is cherry-picked from upstream Git. [1]
Debdiff is attached.
unblock modemmanager/0.4+git.20100624t180933.6e79d15-2
[1]
http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=56665c1
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog
--- modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog
+++ modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog
@@ -1,3 +1,10 @@
+modemmanager (0.4+git.20100624t180933.6e79d15-2) unstable; urgency=low
+
+ * Nokia N900 appears to need a longer port delay.
+Patch cherry-picked from upstream Git. (Closes: #607982)
+
+ -- Michael Biebl bi...@debian.org Tue, 28 Dec 2010 10:24:52 +0100
+
modemmanager (0.4+git.20100624t180933.6e79d15-1) unstable; urgency=low
[ Michael Biebl ]
diff -u modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series
--- modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series
+++ modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series
@@ -1,0 +2 @@
+01-nokia-n900-longer-port-delay.patch
only in patch2:
unchanged:
--- modemmanager-0.4+git.20100624t180933.6e79d15.orig/debian/patches/01-nokia-n900-longer-port-delay.patch
+++ modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/01-nokia-n900-longer-port-delay.patch
@@ -0,0 +1,30 @@
+From 56665c19af431234ebe1b22cff9f0f9b9fb3d02f Mon Sep 17 00:00:00 2001
+From: Dan Williams d...@redhat.com
+Date: Fri, 09 Jul 2010 19:35:36 +
+Subject: nokia: N900 appears to need a longer port delay (rh #583691)
+
+---
+diff --git a/plugins/mm-modem-nokia.c b/plugins/mm-modem-nokia.c
+index eb90287..3cbea00 100644
+--- a/plugins/mm-modem-nokia.c
b/plugins/mm-modem-nokia.c
+@@ -54,6 +54,7 @@ grab_port (MMModem *modem,
+ MMGenericGsm *gsm = MM_GENERIC_GSM (modem);
+ MMPortType ptype = MM_PORT_TYPE_IGNORED;
+ MMPort *port = NULL;
++gulong send_delay = 5000;
+
+ if (suggested_type == MM_PORT_TYPE_UNKNOWN) {
+ if (!mm_generic_gsm_get_at_port (gsm, MM_PORT_TYPE_PRIMARY))
+@@ -71,6 +72,9 @@ grab_port (MMModem *modem,
+mm_serial_parser_v1_e1_destroy);
+ }
+
++/* N900 appears to need longer delay between port bytes */
++g_object_set (G_OBJECT (port), MM_SERIAL_PORT_SEND_DELAY, send_delay, NULL);
++
+ return !!port;
+ }
+
+--
+cgit v0.8.3-6-g21f6
Bug#608147: unblock: k3b/2.0.1-1
On 12/27/2010 11:02 PM, Modestas Vainius wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package k3b In the diff, I read the following: +++ k3b-2.0.1/debian/k3b.bug-script 2010-07-04 07:49:00.0 + @@ -0,0 +1,7 @@ +#!/bin/sh -e + +echo +echo Gathering system configuration viai `wodim -checkdrive` (please wait)... +/usr/bin/wodim -checkdrive 3 2%3 I guess you meant 23 at the end? Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d19bd40.4040...@dogguy.org
Your openturns upload
Hi Christophe, I was just reviewing the diff of your openturns upload fixing #606870, to check that it was suitable for unblocking. Firstly, thanks for fixing the RC bug on the package. I noticed that you also fixed #604605 at the same time, dropping the dependencies on python-qt3. None of the source appears to use Qt3, so that should be okay. However, at least the python-openturns binary package does appear to use Qt4 and I can't see anywhere in the dependency chain that ensures that python-qt4 will be installed. Apologies if I'm simply missing something due to a lack of coffee, but is there a missing dependency on python-qt4 here? Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293539099.3459.4445.ca...@hathi.jungle.funky-badger.org
Bug#608182: unblock: openoffice.org/1:3.2.1-11
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package openoffice.org fixes FTBFS in rare conditions... unblock openoffice.org/1:3.2.1-11 Diff: http://lists.debian.org/debian-openoffice/2010/12/msg00106.html (and the obvious s/UNRELEASED/unstable/) -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Grüße/Regards, Rene -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101228123122.ga9...@rene-engelhard.de
Re: Your openturns upload
Hello Adam, you are absolutely right: the python-qt4 dependency is missing. It is a very mild one and should not be a big issue for the user who does not wish to use the python graphical interface. I am fixing this at the moment and I submit -8 Best regards and thanks for your help! C. On Tue, Dec 28, 2010 at 1:24 PM, Adam D. Barratt a...@adam-barratt.org.ukwrote: Hi Christophe, I was just reviewing the diff of your openturns upload fixing #606870, to check that it was suitable for unblocking. Firstly, thanks for fixing the RC bug on the package. I noticed that you also fixed #604605 at the same time, dropping the dependencies on python-qt3. None of the source appears to use Qt3, so that should be okay. However, at least the python-openturns binary package does appear to use Qt4 and I can't see anywhere in the dependency chain that ensures that python-qt4 will be installed. Apologies if I'm simply missing something due to a lack of coffee, but is there a missing dependency on python-qt4 here? Regards, Adam -- Debian Developer - member of Debian Science http://wiki.debian.org/DebianScience Prof. at Univ. Grenoble in Applied Math. http://ljk.imag.fr/membres/Christophe.Prudhomme/
Re: Release notes addition for Xen support in Debian
Hi, Thanks Martin, for your comments. On 12/28/2010 04:23 PM, Martin Zobel-Helas wrote: In general I support this. Those are changes worth mentioning. On the other hand your text reads more like a howto, which IMHO should be content for wiki.debian.org. Maybe have the release notes linking a wiki document instead? I did accordingly. I also added few things to the wiki (like what packages to apt-get install if you run on 32 bits, plus few words on dtc-xen, a bit about the antispoof=yes thing, and other stuff). Could others please give me comments on this? Also, some correction for my (poor) English would be welcome when/if you spot issues. You are aware that we have debian-l10n-engl...@l.d.o for exactly that reason? Yes, but maybe we shall make sure that we agree with the *content* before we send it to them for correction, right? Your comments on the tone (which should be neutral) and the fact that it shouldn't be a howto was helpful. Also i spotted that some of your wording is quite negative (Unfortunaly, As a consequence, Another thing that you have to take care about, ...). I would like to suggest we come up with at least a neutral wording here. Right. Changed. Attached is the new text, please re-read and let me know what you think. Thomas 4.7.4. Upgrading with Xen installed, and Kernel enumeration order issue with Xen In Lenny, using grub legacy, the default kernel that would start after installing Xen packages was the Xen hypervisor and the dom0 capable Linux kernel. But in Squeeze (and SID), when running with Grub2, this isn't what is happening. By default, the non-Xen kernel will boot. If you have Xen installed and expect to boot with it by default, you have to tweak grub2 configuration as explained at: http://wiki.debian.org/Xen#Installationandconfiguration Also, when upgrading from Lenny, Xen isn't upgraded to the 4.0 version of Squeeze. So, after you finished the dist-upgrade, it is advised to check that Xen 4.0 and the corresponding dom0 kernel are installed with dpkg -l, and eventually, install them with aptitude install. See the same address (eg: http://wiki.debian.org/Xen#Installationandconfiguration) to see how to install the Xen hypervisor and the Xen dom0 kernel under Squeeze. It is also important to notice that your domU wont be able to use HDD devices of the type sda1 (for example). This naming scheme has been removed from Xen because of a request from the mainline kernel maintainers. Instead, you should use xvda1 (as a corresponding example) instead.
Bug#608174: marked as done (unblock: modemmanager/0.4+git.20100624t180933.6e79d15-2)
Your message dated Tue, 28 Dec 2010 16:41:54 +0100
with message-id 20101228154154.gg2...@radis.liafa.jussieu.fr
and subject line Re: Bug#608174: unblock:
modemmanager/0.4+git.20100624t180933.6e79d15-2
has caused the Debian Bug report #608174,
regarding unblock: modemmanager/0.4+git.20100624t180933.6e79d15-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
608174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package modemmanager
I contains a single fix for Nokia N900. (#607982)
The patch is cherry-picked from upstream Git. [1]
Debdiff is attached.
unblock modemmanager/0.4+git.20100624t180933.6e79d15-2
[1]
http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=56665c1
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog
--- modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog
+++ modemmanager-0.4+git.20100624t180933.6e79d15/debian/changelog
@@ -1,3 +1,10 @@
+modemmanager (0.4+git.20100624t180933.6e79d15-2) unstable; urgency=low
+
+ * Nokia N900 appears to need a longer port delay.
+Patch cherry-picked from upstream Git. (Closes: #607982)
+
+ -- Michael Biebl bi...@debian.org Tue, 28 Dec 2010 10:24:52 +0100
+
modemmanager (0.4+git.20100624t180933.6e79d15-1) unstable; urgency=low
[ Michael Biebl ]
diff -u modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series
--- modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series
+++ modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/series
@@ -1,0 +2 @@
+01-nokia-n900-longer-port-delay.patch
only in patch2:
unchanged:
--- modemmanager-0.4+git.20100624t180933.6e79d15.orig/debian/patches/01-nokia-n900-longer-port-delay.patch
+++ modemmanager-0.4+git.20100624t180933.6e79d15/debian/patches/01-nokia-n900-longer-port-delay.patch
@@ -0,0 +1,30 @@
+From 56665c19af431234ebe1b22cff9f0f9b9fb3d02f Mon Sep 17 00:00:00 2001
+From: Dan Williams d...@redhat.com
+Date: Fri, 09 Jul 2010 19:35:36 +
+Subject: nokia: N900 appears to need a longer port delay (rh #583691)
+
+---
+diff --git a/plugins/mm-modem-nokia.c b/plugins/mm-modem-nokia.c
+index eb90287..3cbea00 100644
+--- a/plugins/mm-modem-nokia.c
b/plugins/mm-modem-nokia.c
+@@ -54,6 +54,7 @@ grab_port (MMModem *modem,
+ MMGenericGsm *gsm = MM_GENERIC_GSM (modem);
+ MMPortType ptype = MM_PORT_TYPE_IGNORED;
+ MMPort *port = NULL;
++gulong send_delay = 5000;
+
+ if (suggested_type == MM_PORT_TYPE_UNKNOWN) {
+ if (!mm_generic_gsm_get_at_port (gsm, MM_PORT_TYPE_PRIMARY))
+@@ -71,6 +72,9 @@ grab_port (MMModem *modem,
+mm_serial_parser_v1_e1_destroy);
+ }
+
++/* N900 appears to need longer delay between port bytes */
++g_object_set (G_OBJECT (port), MM_SERIAL_PORT_SEND_DELAY, send_delay, NULL);
++
+ return !!port;
+ }
+
+--
+cgit v0.8.3-6-g21f6
---End Message---
---BeginMessage---
On Tue, Dec 28, 2010 at 10:52:35 +0100, Michael Biebl wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package modemmanager
Done, thanks.
Cheers,
Julien
signature.asc
Description: Digital signature
---End Message---
Re: Your openturns upload
Adam, I just uploaded -8 which fixes the python-qt4 depends you found. I think it is pretty safe to unblock openturns as you can see here https://buildd.debian.org/pkg.cgi?pkg=openturns https://buildd.debian.org/pkg.cgi?pkg=openturns-7 got built already on a few platforms (-6 was built on all of them). Best regards C. On Tue, Dec 28, 2010 at 4:03 PM, Christophe Prud'homme prudh...@debian.orgwrote: Hello Adam, you are absolutely right: the python-qt4 dependency is missing. It is a very mild one and should not be a big issue for the user who does not wish to use the python graphical interface. I am fixing this at the moment and I submit -8 Best regards and thanks for your help! C. On Tue, Dec 28, 2010 at 1:24 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Hi Christophe, I was just reviewing the diff of your openturns upload fixing #606870, to check that it was suitable for unblocking. Firstly, thanks for fixing the RC bug on the package. I noticed that you also fixed #604605 at the same time, dropping the dependencies on python-qt3. None of the source appears to use Qt3, so that should be okay. However, at least the python-openturns binary package does appear to use Qt4 and I can't see anywhere in the dependency chain that ensures that python-qt4 will be installed. Apologies if I'm simply missing something due to a lack of coffee, but is there a missing dependency on python-qt4 here? Regards, Adam -- Debian Developer - member of Debian Science http://wiki.debian.org/DebianScience Prof. at Univ. Grenoble in Applied Math. http://ljk.imag.fr/membres/Christophe.Prudhomme/ -- Debian Developer - member of Debian Science http://wiki.debian.org/DebianScience Prof. at Univ. Grenoble in Applied Math. http://ljk.imag.fr/membres/Christophe.Prudhomme/
Re: [Pkg-xen-devel] Release notes addition for Xen support in Debian
On Tue, Dec 28, 2010 at 10:47:56PM +0800, Thomas Goirand wrote: Hi, Thanks Martin, for your comments. On 12/28/2010 04:23 PM, Martin Zobel-Helas wrote: In general I support this. Those are changes worth mentioning. On the other hand your text reads more like a howto, which IMHO should be content for wiki.debian.org. Maybe have the release notes linking a wiki document instead? I did accordingly. I also added few things to the wiki (like what packages to apt-get install if you run on 32 bits, plus few words on dtc-xen, a bit about the antispoof=yes thing, and other stuff). Could others please give me comments on this? Also, some correction for my (poor) English would be welcome when/if you spot issues. You are aware that we have debian-l10n-engl...@l.d.o for exactly that reason? Yes, but maybe we shall make sure that we agree with the *content* before we send it to them for correction, right? Your comments on the tone (which should be neutral) and the fact that it shouldn't be a howto was helpful. Also i spotted that some of your wording is quite negative (Unfortunaly, As a consequence, Another thing that you have to take care about, ...). I would like to suggest we come up with at least a neutral wording here. Right. Changed. Attached is the new text, please re-read and let me know what you think. Thomas 4.7.4. Upgrading with Xen installed, and Kernel enumeration order issue with Xen In Lenny, using grub legacy, the default kernel that would start after installing Xen packages was the Xen hypervisor and the dom0 capable Linux kernel. But in Squeeze (and SID), when running with Grub2, this isn't what is happening. By default, the non-Xen kernel will boot. If you have Xen installed and expect to boot with it by default, you have to tweak grub2 configuration as explained at: http://wiki.debian.org/Xen#Installationandconfiguration Also, when upgrading from Lenny, Xen isn't upgraded to the 4.0 version of Squeeze. So, after you finished the dist-upgrade, it is advised to check that Xen 4.0 and the corresponding dom0 kernel are installed with dpkg -l, and eventually, install them with aptitude install. See the same address (eg: http://wiki.debian.org/Xen#Installationandconfiguration) to see how to install the Xen hypervisor and the Xen dom0 kernel under Squeeze. It is also important to notice that your domU wont be able to use HDD devices of the type sda1 (for example). This naming scheme has been removed from Xen because of a request from the mainline kernel maintainers. Instead, you should use xvda1 (as a corresponding example) instead. Actually if you need to change to xvda1 naming doesn't depend on Xen version! Xen 4.0 supports using sda1 naming, it's the domU kernel version that matters! If you're using pvops (upstream kernel.org) kernel in the domU (squeeze 2.6.32), then you can *only* use xvd* naming. If you're using old kernel with Xenlinux patches (for example lenny 2.6.26-2-xen), then you can use both xvd* and sd* naming. It's recommended to use the xvd* naming to make life easier! (it works with both types of kernels). -- Pasi -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101228154003.go2...@reaktio.net
Re: Release notes addition for Xen support in Debian
On Tue, Dec 28, 2010 at 15:34:21 +0800, Thomas Goirand wrote: Hi, I intend to have the attached document added to the Squeeze release notes. Also, what's the way to have it included? Should I send it as a wishlist bug to the release-notes package, or something like that? Yes, see http://www.debian.org/releases/squeeze/amd64/release-notes/ch-about.en.html sections 1.1 and 1.3. Cheers, Julien signature.asc Description: Digital signature
Bug#607608: unblock: wordpress/3.0.3-1
On 12/24/2010 12:48 PM, Mehdi Dogguy wrote: re-package? I just uploaded 3.0.3.dfsg-1: wordpress (3.0.3.dfsg-1) unstable; urgency=high * [e113893] Imported Upstream version 3.0.3.dfsg - Re-packaged without the hello dolly plugin (Closes: #607240) * [9d62cfd] Removed hello.patch -- Giuseppe Iuculano iucul...@debian.org Tue, 28 Dec 2010 17:22:34 +0100 signature.asc Description: OpenPGP digital signature
Bug#607608: marked as done (unblock: wordpress/3.0.3-1)
Your message dated Tue, 28 Dec 2010 18:20:19 +0100
with message-id 4d1a1c53.7040...@debian.org
and subject line Re: Bug#607608: unblock: wordpress/3.0.3-1
has caused the Debian Bug report #607608,
regarding unblock: wordpress/3.0.3-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
607608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please unblock package wordpress, 3.0.3 is a security release.
unblock wordpress/3.0.3-1
Cheers,
Giuseppe.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk0PEkIACgkQNxpp46476arRiACdFhRsBbCqzbgCbGAtpLsnkK3V
+lMAoJqZ4iDxkseH1S9T/IbaxPZ8u2R2
=xuD4
-END PGP SIGNATURE-
---End Message---
---BeginMessage---
On 28/12/2010 18:11, Giuseppe Iuculano wrote:
On 12/24/2010 12:48 PM, Mehdi Dogguy wrote:
re-package?
I just uploaded 3.0.3.dfsg-1:
wordpress (3.0.3.dfsg-1) unstable; urgency=high
Thanks, I unblocked it.
* [e113893] Imported Upstream version 3.0.3.dfsg
- Re-packaged without the hello dolly plugin (Closes: #607240)
* [9d62cfd] Removed hello.patch
-- Giuseppe Iuculanoiucul...@debian.org Tue, 28 Dec 2010 17:22:34 +0100
Regards,
--
Mehdi Dogguy مهدي الدڤي
me...@{dogguy.org,debian.org}
---End Message---
Re: [Pkg-freevo-maint] Bug#607921: freevo: (unowned) files in /home (after purge (policy 6.8))
On Tue, Dec 28, 2010 at 18:41:47 +0100, A Mennucc wrote: Il 28/12/2010 00:20, Julien Cristau ha scritto: On Mon, Dec 27, 2010 at 23:24:27 +0100, A Mennucc wrote: this bug has been cloned in two, #489328 #608035 freevo: doesnt cleanup on purge #607921 freevo messes with /home please check again, which one do you refer to The one I tagged and mailed. hi, I fixed that one, please let freevo 1.9.0-8 into squeeze The python2.6 stuff doesn't fix a RC bug, as far as I can tell. The freevo-lirc.postinst change is not documented. Why are pycentral errors ignored? Cheers, Julien signature.asc Description: Digital signature
Bug#608147: unblock: k3b/2.0.1-1
Hello, On antradienis 28 Gruodis 2010 12:34:40 Mehdi Dogguy wrote: +++ k3b-2.0.1/debian/k3b.bug-script 2010-07-04 07:49:00.0 + @@ -0,0 +1,7 @@ +#!/bin/sh -e + +echo +echo Gathering system configuration viai `wodim -checkdrive` (please wait)... +/usr/bin/wodim -checkdrive 3 2%3 I guess you meant 23 at the end? Unfortunately, yes :( Therefore `reportbug k3b` creates %3 file in current directory. Shall I fix it? -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part.
Re: Your openturns upload
On Tue, 2010-12-28 at 17:18 +0100, Christophe Prud'homme wrote: I just uploaded -8 which fixes the python-qt4 depends you found. I think it is pretty safe to unblock openturns Unblocked; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293564736.3459.6357.ca...@hathi.jungle.funky-badger.org
Bug#608147: unblock: k3b/2.0.1-1
On 12/28/2010 08:00 PM, Modestas Vainius wrote: Hello, On antradienis 28 Gruodis 2010 12:34:40 Mehdi Dogguy wrote: +++ k3b-2.0.1/debian/k3b.bug-script 2010-07-04 07:49:00.0 + @@ -0,0 +1,7 @@ +#!/bin/sh -e + +echo +echo Gathering system configuration viai `wodim -checkdrive` (please wait)... +/usr/bin/wodim -checkdrive 3 2%3 I guess you meant 23 at the end? Unfortunately, yes :( Therefore `reportbug k3b` creates %3 file in current directory. Shall I fix it? Of course, yes! -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1a3a99.2040...@dogguy.org
Bug#608182: marked as done (unblock: openoffice.org/1:3.2.1-11)
Your message dated Tue, 28 Dec 2010 19:39:39 + with message-id 1293565179.3459.6400.ca...@hathi.jungle.funky-badger.org and subject line Re: Bug#608182: unblock: openoffice.org/1:3.2.1-11 has caused the Debian Bug report #608182, regarding unblock: openoffice.org/1:3.2.1-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 608182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package openoffice.org fixes FTBFS in rare conditions... unblock openoffice.org/1:3.2.1-11 Diff: http://lists.debian.org/debian-openoffice/2010/12/msg00106.html (and the obvious s/UNRELEASED/unstable/) -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Grüße/Regards, Rene ---End Message--- ---BeginMessage--- On Tue, 2010-12-28 at 13:31 +0100, Rene Engelhard wrote: Please unblock package openoffice.org fixes FTBFS in rare conditions... Relying on the ordering of entries in another package's Depends and Suggests seems somewhat brittle. Still, at least the change in -11 removes one potential source of failure; unblocked. Regards, Adam ---End Message---
Re: [RFC] subversion upload for squeeze - what to include
On Thu, 2010-12-23 at 09:08 -0600, Peter Samuelson wrote: [Adam D. Barratt] We're working on determining what's happening with neon27; please bear with us while that's in progress. OK, I see the neon27 situation has been resolved - thanks, all. I didn't notice earlier, but subversion sid-squeeze migration would also block on the shlibs bump in sqlite3. I see you, Julien and GCS are already talking about that one too, so I'll wait. sqlite3 has also been resolved and is just waiting for uploads on a couple of architectures, so we should be able to go ahead with subversion now; sorry for the delays. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293566300.3459.6498.ca...@hathi.jungle.funky-badger.org
Re: freeze exception -- bugzilla3 3.6.3.0-1
On 12/26/2010 01:22 PM, Mehdi Dogguy wrote:
I'll wait for your comments before uploading.
FTR, I've uploaded Bugzilla to testing-proposed-updates.
(debdiff is attached, fixed an issue found by Julien).
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
diff -Nru bugzilla-3.6.2.0/debian/bugzilla3.config bugzilla-3.6.2.0/debian/bugzilla3.config
--- bugzilla-3.6.2.0/debian/bugzilla3.config 2010-08-27 09:51:13.0 +0200
+++ bugzilla-3.6.2.0/debian/bugzilla3.config 2010-12-25 21:25:38.0 +0100
@@ -138,6 +138,11 @@
ask_again bugzilla3/bugzilla_admin_pwd bugzilla3/pwd_check
fi
db_endblock
+
+# Do not repeat if we are in non-interactive mode.
+if [ $DEBIAN_FRONTEND = noninteractive ]; then
+break
+fi
done
# vim:ts=4 et sw=4
diff -Nru bugzilla-3.6.2.0/debian/bugzilla3.postinst bugzilla-3.6.2.0/debian/bugzilla3.postinst
--- bugzilla-3.6.2.0/debian/bugzilla3.postinst 2010-10-27 13:46:06.0 +0200
+++ bugzilla-3.6.2.0/debian/bugzilla3.postinst 2010-12-25 21:29:28.0 +0100
@@ -137,9 +137,9 @@
if [ $mode = configure ]; then
# Fix file/directory permissions.
-run_script $BUGZILLA_ETCDIR/post-checksetup.d/10setdefaultdpkgstatoverride 21 /dev/null \
+run_script $BUGZILLA_ETCDIR/post-checksetup.d/10setdefaultdpkgstatoverride /dev/null 21 \
|| true
-run_script $BUGZILLA_ETCDIR/post-checksetup.d/15restoredpkgstatoverride 21 /dev/null \
+run_script $BUGZILLA_ETCDIR/post-checksetup.d/15restoredpkgstatoverride /dev/null 21 \
|| true
# Setup a preleminary /etc/bugzilla3/params file.
diff -Nru bugzilla-3.6.2.0/debian/changelog bugzilla-3.6.2.0/debian/changelog
--- bugzilla-3.6.2.0/debian/changelog 2010-12-05 18:55:32.0 +0100
+++ bugzilla-3.6.2.0/debian/changelog 2010-12-26 01:06:06.0 +0100
@@ -1,3 +1,13 @@
+bugzilla (3.6.2.0-4.2) testing-proposed-updates; urgency=low
+
+ * Non-maintainer upload.
+ * Support for noninteractive mode in Debconf (Closes: #602738)
+ * Add security patches (Closes: #602420):
+- 50_cve-2010-3172.sh fixes CVE-2010-3172
+- 70_cve-2010-3764.sh fixes CVE-2010-3764 (and remove 50_graphdir.sh)
+
+ -- Mehdi Dogguy me...@debian.org Sat, 25 Dec 2010 22:25:55 +0100
+
bugzilla (3.6.2.0-4.1) testing-proposed-updates; urgency=low
* Non-maintainer upload.
diff -Nru bugzilla-3.6.2.0/debian/maintenance/50_graphdir.sh bugzilla-3.6.2.0/debian/maintenance/50_graphdir.sh
--- bugzilla-3.6.2.0/debian/maintenance/50_graphdir.sh 2010-08-08 18:49:32.0 +0200
+++ bugzilla-3.6.2.0/debian/maintenance/50_graphdir.sh 1970-01-01 01:00:00.0 +0100
@@ -1,69 +0,0 @@
-#!/bin/sh
-# https://bugs.launchpad.net/ubuntu/+source/bugzilla/+bug/419335
-set -e
-
-echo $0 $*
-
-cd $1 patch -p1 $0
-
-exit 0
-
-diff -Naur a/Bugzilla/Install/Filesystem.pm b/Bugzilla/Install/Filesystem.pm
a/Bugzilla/Install/Filesystem.pm 2010-07-14 01:09:27.0 +0200
-+++ b/Bugzilla/Install/Filesystem.pm 2010-08-08 18:13:35.534125065 +0200
-@@ -176,7 +176,7 @@
- dirs = $ws_dir_writeable },
- $webdotdir = { files = $ws_writeable,
- dirs = $ws_dir_writeable },
-- graphs = { files = $ws_writeable,
-+ $datadir/graphs = { files = $ws_writeable,
- dirs = $ws_dir_writeable },
-
- # Readable directories
-@@ -228,7 +228,7 @@
- $datadir/extensions = $ws_dir_readable,
- $attachdir = $ws_dir_writeable,
- $extensionsdir = $ws_dir_readable,
--graphs = $ws_dir_writeable,
-+$datadir/graphs = $ws_dir_writeable,
- $webdotdir = $ws_dir_writeable,
- $skinsdir/custom = $ws_dir_readable,
- $skinsdir/contrib = $ws_dir_readable,
-@@ -358,10 +358,10 @@
- my %files = %{$fs-{create_files}};
-
- my $datadir = bz_locations-{'datadir'};
--# If the graphs/ directory doesn't exist, we're upgrading from
-+# If the $datadir/graphs/ directory doesn't exist, we're upgrading from
- # a version old enough that we need to update the $datadir/mining
- # format.
--if (-d $datadir/mining !-d 'graphs') {
-+if (-d $datadir/mining !-d $datadir/graphs) {
- _update_old_charts($datadir);
- }
-
-diff -Naur a/collectstats.pl b/collectstats.pl
a/collectstats.pl 2010-07-06 20:20:12.0 +0200
-+++ b/collectstats.pl 2010-08-08 18:17:23.746133772 +0200
-@@ -49,9 +49,11 @@
- # in the regenerate mode).
- $| = 1;
-
-+my $datadir = bz_locations()-{'datadir'};
-+
- # Tidy up after graphing module
- my $cwd = Cwd::getcwd();
--if (chdir(graphs)) {
-+if (chdir($datadir/graphs)) {
- unlink ./*.gif;
- unlink ./*.png;
- # chdir(..) doesn't work if graphs is a symlink, see bug 429378
-@@ -68,8 +70,6 @@
- $regenerate = 1;
- }
-
--my $datadir = bz_locations()-{'datadir'};
--
- my @myproducts =
Re: Release notes addition for Xen support in Debian
Thomas Goirand wrote: Right. Changed. Attached is the new text, please re-read and let me know what you think. Thomas 4.7.4. Upgrading with Xen installed, and Kernel enumeration order issue with Xen What you mean is: 4.7.4. Xen upgrades In Lenny, using grub legacy, the default kernel that would start after installing Xen packages was the Xen hypervisor and the dom0 capable Linux kernel. Before I read this I thought I understood it, but now... the Xen hypervisor is a kernel that starts after installing itself? Or, wait, the Xen hypervisor plus a Linux kernel, considered together, constitute the default kernel? I imagine you mean: In Lenny, if you installed Xen, the kernel that grub-legacy would boot by default was the one providing a Xen hypervisor and dom0 support. But in Squeeze (and SID), when running with Grub2, this isn't what is happening. These are *release* notes - forget Sid. To steal Ben's phrasing: This does not happen under GRUB 2 in Squeeze. By default, the non-Xen kernel will boot. Instead, the non-Xen kernel will boot by default. Or perhaps run it together as This does not happen under GRUB 2 in Squeeze - instead, the non-Xen kernel will boot by default. If you have Xen installed and expect to boot with it by default, you have to tweak grub2 configuration as explained at: http://wiki.debian.org/Xen#Installationandconfiguration s/have to/need to/ and s/grub2/the GRUB 2/ Also, when upgrading from Lenny, Xen isn't upgraded to the 4.0 version of Squeeze. I didn't know there was a 4.0 version of Squeeze! http://packages.debian.org/changelogs/pool/main/s/squeeze/ I *think* you mean: Also, upgrading from the Lenny version of Xen does not automatically install the current 4.0 version. So, after you finished the dist-upgrade, it is advised to check that Xen 4.0 and the corresponding dom0 kernel are installed with dpkg -l, and eventually, install them with aptitude install. Dist-upgrade is obsolete jargon. There's no particular reason to use dpkg rather than aptitude show, or indeed just trying the install anyway - how would it miraculously have got installed without the sysadmin's knowledge if there's no dependency pathway from xen-hypervisor-3.2.1 to -4.0? Also, false friend s/eventually/if appropriate/, but just drop this pointless check: So, after you finish the dist-upgrade, you should use an explicit aptitude install for Xen 4.0 and a corresponding dom0 kernel. I'm sorely tempted to add or give up on xen altogether. See the same address (eg: http://wiki.debian.org/Xen#Installationandconfiguration) to see how to install the Xen hypervisor and the Xen dom0 kernel under Squeeze. You don't mean e.g. here. (I suppose it's better than ibid.) See the wiki page for instructions on how to set up the Xen hypervisor and dom0 kernel under Squeeze. It is also important to notice that your domU wont be able to use HDD devices of the type sda1 (for example). This naming scheme has been removed from Xen because of a request from the mainline kernel maintainers. Instead, you should use xvda1 (as a corresponding example) instead. Be aware that your domU won't be able to use (for example) sda1 as a device name for its hard drive. This naming scheme has been removed from Xen because of a request from the mainline kernel maintainers. Instead you should use (as a corresponding example) xvda1. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101228201833.ga12...@xibalba.demon.co.uk
Bug#608221: RM: youtube-dl/2010.12.09-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please hint youtube-dl out of testing as the maintainer has stated it not suitable for release (see #608176, which has been opened to stop it migrating to testing again). - -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJNGky9AAoJEFOUR53TUkxRCZUP/256kDDNLvfs8x24yi3/Ev2M 0G91Y0YMMWHoKG8pGV/+5rKKxdCsvZITjotC5Z/Dg7PgKCEpyr1iZHnSihSy9F9V l8gMUxLIDyxDApvbhNgv5osaX6SvUyl78AVQC927RCn+b468Frqgif5PYmEXk9Zt VRJKq1oHSNr/g2JqYMR0Ud/993XGNaqTabmXtMzHJIQu8Bo78XppWEvNwTTcTj9P qGzZkecdOPiokj10W8eKZVkJMp4S1h/WoAeiyEZ7SGX3jbr4g5WwLFD7rlmcFuTH PbCz0A+LIw9vegNbW6AIzHVZwpg+b6VuPAwmxyLgYFRP9O2N2em0bWWZORDAnM2Z JhpEr4Bfn8aGqMEt7o6ux3y1shDQaJTN09y16O62IfCBCZMgjPAC+L5HlLUBqOfG NhzxXlchnX7kQFjQVZsLTmS0jUclwfgNmC0Oi2N40WBMvDFM1hFROZhJOGNihDg1 sJ2Gf0OPb5Io06XAE6zyJXhHN9R3J1OytwtlrYpLVNUlonSX+Bp/iWocuDOz1VeW Q7iWfE/UcFl8PzLX9RrKemTO1BuMdUiOfgEKgTXE/P2RuyVAtPhOOJTcqMAD2ThB VKcKn5U4PUJNe7TDN9yRrulFjwmcc4lhaHxAA1fMIg7jvxYGuEtyZ+x9zGx/EKjH vxQfHFBJ4FYzc9WoL24l =9Kjm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101228204656.27983.86762.report...@lupin
Re: Release notes addition for Xen support in Debian
I'll treat this and Thomas Goirand's rewrite as separate requests for review and let someone else decide how to merge them. Ben Finney wrote: Martin Zobel-Helas zo...@debian.org writes: | 4.7.4. Upgrading with Xen installed, and Kernel enumeration order issue with | Xen For a section title in the context of this document, I think “issue” is redundant. Also, the capitalisation is a bit random. | In Lenny, using grub legacy, the following kernel order was respected: - Xen | hypervisor with Xen dom0 kernel - Normal (eg: without dom0 support) kernel - | Xen dom0 kernel (without they hypervisor) s/they hypervisor/the hypervisor/ I am fairly sure “eg: without dom0 support” is meant to be “i.e., without dom0 support”. The original author should explain whether this is meant to be “for example” (“e.g.”), or “that is” (“i.e.”). Those are supposed to be a bulleted list, I presume? Perhaps editing has collapsed the paragraph. Here it is as a bulleted list: […] the following kernel order was respected: * Xen hypervisor with Xen dom0 kernel * Normal (i.e., without dom0 support) kernel * Xen dom0 kernel (without the hypervisor) And to avoid further abbreviatory confusion, make the middle one * Normal kernel (without dom0 support) (Here and later.) | This order was the natural expected one, because if you installed Xen, it will | simply boot the hypervisor and it's dom0 by default as expected. Maybe easier to scan: This was the default order, because Xen's default configuration was to boot the hypervisor and it's dom0. Whoops, you mean its (possessive). Otherwise, agreed. Maybe you could put back some of the natural expected bit like this: This made a natural default order, because Xen's default configuration was to boot the hypervisor and its dom0. | Unfortunately, in Squeeze, when running with Grub2, this isn't what is | happening. By default, the order is the exact opposite: - Xen dom0 kernel | (without they hypervisor) - Normal (eg: without dom0 support) kernel - Xen | hypervisor with Xen dom0 kernel Briefer and perhaps more neutral (and again assuming a bulleted list was the intent): This does not happen under GRUB 2 in Squeeze. Instead, the order is the exact opposite: * Xen dom0 kernel (without the hypervisor) * Normal (i.e., without dom0 support) kernel * Xen hypervisor with Xen dom0 kernel The spelling and capitalisation of “GRUB 2” should be as I have written it there, to conform with URL:http://www.gnu.org/software/grub/. (In Lenny someone might have argued for the packagename grub2, all lowercase, but that's a dummy package in Squeeze anyway.) | As a consequence, if you have Xen installed and expect to boot with it by | default, you have to tweak grub2 configuration. One of the way to hack before | the grub maintainers can fix it the proper way could be to simply do: My suggestion: As a consequence, if you have Xen installed and expect to boot with it by default, you have to either wait for the GRUB 2 maintainers to fix the sequence or tweak the GRUB 2 configuration. One work-around is to simply do: (In fact I find workaround in more dictionaries than work-around, presumably because it was never a work around) | ln -s 20_linux_xen /etc/grub.d/09_linux_xen_first dpkg-reconfigure grub-pc | | so that Xen is loaded first, by default, when using Grub2. s/Grub2/GRUB 2/ | Another thing that you have to take care about when upgrading from Lenny, is | that currently, Xen isn't upgraded to the 4.0 version that you should be | expecting in Squeeze. So, after you finished the dist-upgrade, it is advised to | check that Xen 4.0 and the corresponding dom0 kernel are installed. Under the | 64 bits architecture, the following command will fix this: The ‘dist-upgrade’ subcommand is deprecated; ‘full-upgrade’ is now recommended. Here is my suggestion: Also, when upgrading from Lenny, Xen is not upgraded to the 4.0 version that you should be expecting in Squeeze. So, after the ‘full-upgrade’ is complete, you are advised to check that Xen 4.0 and the corresponding dom0 kernel are installed. The official recommended package installation tool is ‘aptitude’, so that's what our official notes should be recommending: It's not clear that that's true for this release; it's what I've always used (and its full-screen mode has given me some painless test Lenny-to-Squeeze upgrades), but I've seen claims on debian-devel or somewhere that apt's resolver is currently more robust. * For the ‘amd64’ architecture, use the following command: aptitude install xen-utils-common xen-utils-4.0 xenstore-utils libxenstore3.0 xen-hypervisor-4.0-amd64 linux-image-2.6.32-5-xen-amd64 * For the ‘i686’ architecture, use the following command: The i386 architecture or the i686 CPU architecture?
Re: Release notes addition for Xen support in Debian
On Tue, 2010-12-28 at 20:17 +, Justin B Rye wrote: [...] Ben Finney wrote: The official recommended package installation tool is ‘aptitude’, so that's what our official notes should be recommending: It's not clear that that's true for this release; it's what I've always used (and its full-screen mode has given me some painless test Lenny-to-Squeeze upgrades), but I've seen claims on debian-devel or somewhere that apt's resolver is currently more robust. The Squeeze release notes recommend aptitude for interactive package management and apt-get for non-interactive use and release upgrades; see http://www.debian.org/releases/testing/amd64/release-notes/ch-whats-new.en.html#pkgmgmt Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293570695.3459.6867.ca...@hathi.jungle.funky-badger.org
Re: Bug#603710: root and swap devices on lvm do not correctly show up in udev (missing symlinks)
user release.debian@packages.debian.org usertag 603710 squeeze-can-defer tag 603710 squeeze-ignore kthxbye On Fri, Dec 24, 2010 at 00:57:21 +0100, Marco d'Itri wrote: On Dec 24, Julien Cristau jcris...@debian.org wrote: I don't know. You say there's a RC bug in our lvm package, so you could provide a patch or NMU, or at least give some details about this since you seem to know what this is about and there's no details in the bug log... This is what the upstream maintainer had to say on the matter: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590665#20 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593625#25 I had to revert the change discussed in #593625 because the LVM rules have not been updated. I do not know lvm enough to provide a reasonably safe patch. Then unless waldi reappears or someone does provide a patch, it doesn't seem like there's anything we can do about this. Tagging accordingly. Cheers, Julien signature.asc Description: Digital signature
Re: Release notes addition for Xen support in Debian
Adam D. Barratt wrote: It's not clear that that's true for this release; it's what I've always used (and its full-screen mode has given me some painless test Lenny-to-Squeeze upgrades), but I've seen claims on debian-devel or somewhere that apt's resolver is currently more robust. The Squeeze release notes recommend aptitude for interactive package management and apt-get for non-interactive use and release upgrades; see http://www.debian.org/releases/testing/amd64/release-notes/ch-whats-new.en.html#pkgmgmt And that's a genuine what's-new, not a vestigial Lennyism. It would be nice to know the reasoning, but okay; for the upgrade itself we should be quoting apt-get commands, while for the immediately subsequent xen 4.0 install we should be telling them to switch back to aptitude. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101228222401.ga17...@xibalba.demon.co.uk
Re: Bug#608210: wiliki: empty package after rebuild
On Tue, Dec 28, 2010 at 07:59:50PM +0100, Jakub Wilk wrote: I rebuilt wiliki in a clean sid i386 chroot. The resulting package was mostly empty: It's also not had an upload since 2005, and has a popcon of inst:15, vote:3, so unless this bug is fixed very soon I suggest it's a good candidate for removal. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: [Pkg-xen-devel] Release notes addition for Xen support in Debian
On 12/29/2010 04:18 AM, Justin B Rye wrote: [...many English corrections...] Thanks a lot for all these changes. I've attached the new version modified with you advice. Now, I did download the release-notes from SVN, as per the link Julien provided. But I failed to understand what file I should modify in it (I've searched...). This information is missing at http://www.debian.org/releases/squeeze/amd64/release-notes/ch-about.en.html (it only tells about SVN). Please help me to get this addition in. Cheers, Thomas Goirand (zigo) 4.7.4. Xen upgrades In Lenny, if you installed Xen, the kernel that grub-legacy would boot by default was the one providing a Xen hypervisor and dom0 support. This does not happen under GRUB 2 in Squeeze. Instead, the non-Xen kernel will boot by default. If you need Xen and expect to boot with it by default, you have to tweak the GRUB 2 configuration as explained at: http://wiki.debian.org/Xen#Installationandconfiguration Also, upgrading from the Lenny version of Xen does not automatically install the current 4.0 version. So, after you finish the dist-upgrade, you should use an explicit aptitude install for Xen 4.0 and a corresponding dom0 kernel. See the wiki page for instructions on how to set up the Xen hypervisor and dom0 kernel under Squeeze. Be aware that, if you run a pvops kernel for your domU, like the Xen kernel 2.6.32 of Squeeze, your domU won't be able to use (for example) sda1 as a device name for its hard drive. This naming scheme has been removed from Xen because of a request from the mainline kernel maintainers. Instead you should use (as a corresponding example) xvda1, which always work, including when running Lenny 2.6.26 forward ported Xen patch.
Re: Bug#608190: /etc/gnumed/gnumed-client.conf has wrong database name
On Tue, Dec 28, 2010 at 04:24:10PM +0100, Mehdi Dogguy wrote: It looks ok (from the bug log) but I'd like to see a debdiff first. I attached a proposed diff which is in principle a sed -i 's/14/13/g' gnumed-client-0.7.10/debian/conf/gnumed-client.conf P.S.: CC'ing debian-rele...@l.d.o would have been appreciated, but well… Done. Thanks for the work of the release team Andreas. -- http://fam-tille.de diff -ubrN gnumed-client-0.7.10.orig/debian/changelog gnumed-client-0.7.10/debian/changelog --- gnumed-client-0.7.10.orig/debian/changelog 2010-12-05 20:47:27.0 +0100 +++ gnumed-client-0.7.10/debian/changelog 2010-12-29 08:31:20.0 +0100 @@ -1,3 +1,17 @@ +gnumed-client (0.7.10-2) unstable; urgency=low + + * Fix /etc/gnumed/gnumed-client.conf which was referencing a future +database version (v14) instead of v13 which fits gnumed-client +version 0.7.x + + -- Andreas Tille ti...@debian.org Wed, 29 Dec 2010 08:29:27 +0100 + +gnumed-client (0.8.5-1) unstable; urgency=low + + * Upstream bugfix release. + + -- Andreas Tille ti...@debian.org Sun, 05 Dec 2010 23:37:38 +0100 + gnumed-client (0.7.10-1) testing-proposed-updates; urgency=low * New upstream release. diff -ubrN gnumed-client-0.7.10.orig/debian/conf/gnumed-client.conf gnumed-client-0.7.10/debian/conf/gnumed-client.conf --- gnumed-client-0.7.10.orig/debian/conf/gnumed-client.conf 2010-09-14 08:03:55.0 +0200 +++ gnumed-client-0.7.10/debian/conf/gnumed-client.conf 2010-12-29 08:27:43.0 +0100 @@ -6,7 +6,7 @@ # - [preferences] -profile = GNUmed database on this machine (Debian GNU/Linux) (gnumed_v14@) +profile = GNUmed database on this machine (Debian GNU/Linux) (gnumed_v13@) login = any-doc @@ -53,7 +53,7 @@ [profile public GNUmed database at salaam.homeunix.com] host = salaam.homeunix.com port = 5432 -database = gnumed_v14 +database = gnumed_v13 #encoding = UTF8 @@ -77,7 +77,7 @@ [profile GNUmed database on this machine] host = port = 5432 -database = gnumed_v14 +database = gnumed_v13 public/open access = 0 #encoding = UTF8 help desk = Your own IT support needs configuration
