Re: Incomplete ben file for libav9 transition?
Hello Reinhard, Reinhard Tartler > On Wed, May 29, 2013 at 12:18 AM, José Manuel Santamaría Lema > > wrote: > > Hello, > > > > unless I'm missing something, I think in the ben file you may have > > missed: > > > > - In Bad: packages depending on libavcodec-extra-53, libavcodec-extra-53 > > and libavutil-extra-51 > > > > - In Good: packages depending on libavcodec-extra-54, libavcodec-extra-54 > > and libavutil-extra-52 > > Packages are not supposed to depend on libavcodec-extra-53 or > libavcodec-extra-54, unless really really necessary. Can you show > examples that explicitly depend on the -extra- variants, and only > them? > > I only know of devede, and would like to know if they are more offenders. With this ben query; ben query ".depends ~/libavcodec-extra-53/ & ! .depends ~/libavcodec53/" -s Package,Version,Source,Architecture,Depends * I found out that dvd-slideshow is also affected. I tried similar queries for avformat and avutil but I found nothing. Also I would like to mention some things more, which you may find interesting: for some reason when you build a package with sbuild and the aptitude resolver you don't get a depend on libavcodec53 | libavcodec-extra-53, but a depend on the extra package and only the extra package. See for instance amarok in experimental for amd64. This happens when the sbuild aptitude resolver doesn't install libavcodec53. It also happened to me randomly when building other KDE 4.10 packages, such as src:nepomuk-core and src:ffmpegthumbs. I realized about this problem because I'm maintaining an unofficial repository with KDE packages for debian similar to the old qt-kde.debian.net. A couple of users told me that their upgrades wanted to remove amarok and other stuff. This problem happened only with apt-get, but not with aptitude, but since official debian KDE 4.10 packages from experimental are difficult to install/upgrade with apt-get, and the current debian qt/kde team stopped using qt-kde.debian.net (which would made the upgrades easier with apt-get and easier in general), nobody in debian realized about this problem. To workaround the problem I added libavcodec53 to the build depends of my customized packages amarok, nepomuk-core and ffmpegthumbs, thus I'm getting the correct depends, even while I'm building my packages with sbuild and the aptitude resolver. Cheers. signature.asc Description: This is a digitally signed message part.
NEW changes in stable-new
Processing changes file: libnss-myhostname_0.3-5~deb7u1_armhf.changes ACCEPT Processing changes file: libnss-myhostname_0.3-5~deb7u1_s390x.changes ACCEPT -- 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/e1uhuwz-0001is...@franck.debian.org
NEW changes in stable-new
Processing changes file: libnss-myhostname_0.3-5~deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: libnss-myhostname_0.3-5~deb7u1_mips.changes ACCEPT Processing changes file: libnss-myhostname_0.3-5~deb7u1_mipsel.changes ACCEPT Processing changes file: libnss-myhostname_0.3-5~deb7u1_powerpc.changes ACCEPT Processing changes file: libnss-myhostname_0.3-5~deb7u1_s390.changes ACCEPT -- 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/e1uhuiv-0005gb...@franck.debian.org
NEW changes in stable-new
Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_armel.changes ACCEPT -- 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/e1uhtpt-0006et...@franck.debian.org
NEW changes in stable-new
Processing changes file: clutter-gst_1.5.4-1+build0_armel.changes ACCEPT -- 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/e1uhs4x-0005ph...@franck.debian.org
NEW changes in stable-new
Processing changes file: nbd_3.2-4~deb7u3_armel.changes ACCEPT -- 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/e1uhrin-0006ax...@franck.debian.org
NEW changes in stable-new
Processing changes file: nbd_3.2-4~deb7u3_s390x.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_s390.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_s390x.changes ACCEPT Processing changes file: smcroute_0.95-1+deb7u1_s390x.changes ACCEPT -- 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/e1uhqml-00058i...@franck.debian.org
NEW changes in stable-new
Processing changes file: atlas_3.8.4-9+deb7u1_s390x.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_s390.changes ACCEPT -- 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/e1uhqye-lo...@franck.debian.org
Bug#704566: unblock: isc-dhcp/4.2.2.dfsg.1-5+deb70u4
On Sun, May 26, 2013 at 6:59 AM, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sun, 2013-05-12 at 12:58 -0400, Michael Gilbert wrote: >> On Tue, Apr 16, 2013 at 8:08 AM, Adam D. Barratt wrote: >> It's now after. How would you like me to approach this? Do I need to >> do a new upload to spu? If so, should the version be +deb70u5 or >> +deb70u6? It looks like the tpu didn't get automatically moved over >> to spu [0]? > > Yes, the latter and no, in that order. :-) > > There is one issue, which is that testing still has +deb70u3, as there > doesn't seem to be any movement on #692808; that'll need resolving > somehow before the point release. Here is a proposed spu patch addressing all of the above. Please let me know if it is ok to upload. Best wishes, Mike isc-dhcp.patch Description: Binary data
NEW changes in stable-new
Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_mips.changes ACCEPT -- 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/e1uhq5c-0008vu...@franck.debian.org
Bug#710329: transition: libxml-security-c17
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello folks, I'm preparing a new version of the Shibboleth packages, which as usual involves three library transitions, although they're all used only by this package set. libxml-security-c is the lowest-level, but this also involves libxmltooling (5 -> 6) and libsaml (7 -> 8). These versions are required for the new upstream version of the shibboleth-sp2 source package, which in turn is required for Apache 2.4 support, so from that you can see why I'm working on this now. :) Unfortunately, and this is the part about which I wanted to give you advance warning, the new versions of these packages add a dependency on Boost. I'm therefore worried that, as well as being its own mini-transition, I may end up entangling the Apache transition with the Boost transition if I just push this stuff to unstable. I'm staging the packages in experimental and have everything done except for the actual shibboleth-sp2 package and its Apache module, which I'm going to work on tomorrow. But I will hold off on uploading this package set to unstable (that is xml-security-c, xmltooling, opensaml2, and shibboleth-sp2 as source packages) until I hear from you about how you want to time this with everything else. Ben file: title = "libxml-security-c17"; is_affected = .depends ~ "libxml-security-c16" | .depends ~ "libxml-security-c17"; is_good = .depends ~ "libxml-security-c17"; is_bad = .depends ~ "libxml-security-c16"; -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.8-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130529234819.3607.18168.report...@windlord.stanford.edu
NEW changes in stable-new
Processing changes file: nbd_3.2-4~deb7u3_armhf.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_kfreebsd-amd64.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_kfreebsd-i386.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_mips.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_mipsel.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_powerpc.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_armhf.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_kfreebsd-amd64.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_mipsel.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_powerpc.changes ACCEPT -- 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/e1uhpcf-ra...@franck.debian.org
NEW changes in stable-new
Processing changes file: chromium-browser_27.0.1453.93-1~deb7u1_amd64.changes ACCEPT Processing changes file: chromium-browser_27.0.1453.93-1~deb7u1_i386.changes ACCEPT Processing changes file: atlas_3.8.4-9+deb7u1_mipsel.changes ACCEPT -- 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/e1uhovi-0003ow...@franck.debian.org
NEW changes in stable-new
Processing changes file: libnss-myhostname_0.3-5~deb7u1_amd64.changes ACCEPT -- 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/e1uhnyy-0001cy...@franck.debian.org
Re: Upcoming stable point release (7.1)
El 29/05/13 20:59, Adam D. Barratt escribió:
On Thu, 2013-05-16 at 10:36 +0200, Santiago Vila wrote:
On Thu, 16 May 2013, Adam D. Barratt wrote:
The first point release for "wheezy" (7.1) is scheduled for Saturday
June 15th. Stable NEW will be frozen during the preceding weekend.
As usual, base-files can be uploaded at any point before the freeze.
Before I go ahead, I'd like to confirm the opinion of release managers
about this minor issue: Currently, the only file which fully reflects
the version number, including the point release, is /etc/debian_version.
(i.e. it will become "7.0.1", while issue{.net} would still be "7.0")
We were planning on this being 7.1, rather than 7.0.1. (Major versions
are always X.0 now, so hard-coding the second component to "0" for point
releases is simply a waste.)
Q1. Do we still want to exclude /etc/issue and /etc/issue.net?
Q2. There is a new file containing the version number, namely, /etc/os-release.
Do we want to exclude it as well, as we usually do with issue and issue.net?
Do we know if anything parses any of these files, rather than simply
displaying them to users? If we're not sure then I'm tending towards
leaving them as-is for now and investigating for the next point release;
I have "fond" memories of undertaking a similar exercise a few years ago
before we started updating /etc/debian_version.
Well, if the next release is 7.1 and we want to mimic what we did in
squeeze (i.e. update /etc/debian_version only), we should better remove
the ".0" part from every version number, as it should be just "7".
Keeping "7.0" in "7.1" would be clearly a bug.
--
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/51a66de3.6040...@unex.es
Bug#709286: pu: package libnss-myhostname/0.3-4
Control: tags -1 + pending On Wed, 2013-05-29 at 20:11 +0200, Joachim Breitner wrote: > Am Montag, den 27.05.2013, 21:23 +0100 schrieb Adam D. Barratt: > > Alternatively, the patch could just be applied to the existing stable > > package. That might not play nicely with automating the build from git, > > but it would produce a minimal diff. > > done that, and uploaded. Thanks; flagged for acceptance. 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/1369857944.28736.15.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#709286: pu: package libnss-myhostname/0.3-4
Processing control commands: > tags -1 + pending Bug #709286 [release.debian.org] pu: package libnss-myhostname/0.3-4 Added tag(s) pending. -- 709286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b709286.136985795523086.transcr...@bugs.debian.org
NEW changes in stable-new
Processing changes file: keystone_2012.1.1-13+wheezy1_amd64.changes ACCEPT Processing changes file: cyrus-imapd-2.4_2.4.16-4+deb7u1_amd64.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u2_amd64.changes ACCEPT Processing changes file: nbd_3.2-4~deb7u3_amd64.changes ACCEPT Processing changes file: otrs2_3.1.7+dfsg1-8+deb7u1_amd64.changes ACCEPT -- 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/e1uhlry-0001ea...@franck.debian.org
Processed: Re: Bug#710234: pu: package libvirt/0.9.12-11+wheezy1
Processing control commands: > tags -1 +confirmed -moreinfo Bug #710234 [release.debian.org] pu: package libvirt/0.9.12-12 Added tag(s) confirmed. Bug #710234 [release.debian.org] pu: package libvirt/0.9.12-12 Removed tag(s) moreinfo. -- 710234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b710234.136985461629296.transcr...@bugs.debian.org
Bug#710234: pu: package libvirt/0.9.12-11+wheezy1
Control: tags -1 +confirmed -moreinfo On Wed, 2013-05-29 at 15:58 +0200, Guido Günther wrote: > On Wed, May 29, 2013 at 10:34:59AM +0100, Adam D. Barratt wrote: > > On 2013-05-29 10:22, Guido Günther wrote: > > >I'd like to update libvirt with wheezy's first point release since it > > >misses two important bug fixes. The first one addresses xen pv > > >support (#685749) while the other one adresses a leak (#705205). > > > > The bug logs suggest that those bugs are not yet fixed in unstable. > > Please could you clarify, and update their statuses if required? > > This kind of overlapped with the upload of 1.0.5 to unstable so it > should be o.k. now. New full debdiff attached. I've changed the version > number to 0.9.12-11+wheezy1 as well. Thanks. Please go ahead, using 0.9.12-11+deb7u1 as the version number. 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/1369854608.28736.14.ca...@jacala.jungle.funky-badger.org
Bug#708631: pu: package cyrus-imapd-2.4/2.4.16-4+deb7u1
Control: tags -1 + pending On Wed, 2013-05-29 at 18:40 +0200, Ondřej Surý wrote: > I have uploaded a version to ftp-master, but nothing much has > happened. I was hoping that the version in unstable would manage to migrate in the meantime; unfortunately it's stuck behind net-snmp. :-( I've just flagged the upload for acceptance in to p-u; 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/1369854278.28736.12.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#708631: pu: package cyrus-imapd-2.4/2.4.16-4+deb7u1
Processing control commands: > tags -1 + pending Bug #708631 [release.debian.org] pu: package cyrus-imapd-2.4/2.4.16-4+deb7u1 Added tag(s) pending. -- 708631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b708631.136985428827107.transcr...@bugs.debian.org
Re: Upcoming stable point release (7.1)
On Thu, 2013-05-16 at 10:36 +0200, Santiago Vila wrote:
> On Thu, 16 May 2013, Adam D. Barratt wrote:
> > The first point release for "wheezy" (7.1) is scheduled for Saturday
> > June 15th. Stable NEW will be frozen during the preceding weekend.
> >
> > As usual, base-files can be uploaded at any point before the freeze.
>
> Before I go ahead, I'd like to confirm the opinion of release managers
> about this minor issue: Currently, the only file which fully reflects
> the version number, including the point release, is /etc/debian_version.
> (i.e. it will become "7.0.1", while issue{.net} would still be "7.0")
We were planning on this being 7.1, rather than 7.0.1. (Major versions
are always X.0 now, so hard-coding the second component to "0" for point
releases is simply a waste.)
> Q1. Do we still want to exclude /etc/issue and /etc/issue.net?
> Q2. There is a new file containing the version number, namely,
> /etc/os-release.
> Do we want to exclude it as well, as we usually do with issue and issue.net?
Do we know if anything parses any of these files, rather than simply
displaying them to users? If we're not sure then I'm tending towards
leaving them as-is for now and investigating for the next point release;
I have "fond" memories of undertaking a similar exercise a few years ago
before we started updating /etc/debian_version.
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/1369853981.28736.10.ca...@jacala.jungle.funky-badger.org
NEW changes in stable-new
Processing changes file: linux_3.2.41-2+deb7u1_multi.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u1_amd64.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u1_i386.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u1_ia64.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u1_powerpc.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_multi.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_armel.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_armhf.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_i386.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_ia64.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_mips.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_mipsel.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_powerpc.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_s390.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_s390x.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_amd64.changes ACCEPT Processing changes file: linux_3.2.41-2+deb7u2_sparc.changes ACCEPT Processing changes file: user-mode-linux_3.2-2um-1+deb7u1_amd64.changes ACCEPT Processing changes file: user-mode-linux_3.2-2um-1+deb7u1_i386.changes ACCEPT -- 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/e1uhkzt-00020h...@franck.debian.org
Bug#709286: pu: package libnss-myhostname/0.3-4
Hi,
Am Montag, den 27.05.2013, 21:23 +0100 schrieb Adam D. Barratt:
> Alternatively, the patch could just be applied to the existing stable
> package. That might not play nicely with automating the build from git,
> but it would produce a minimal diff.
done that, and uploaded.
Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
diff -Nru libnss-myhostname-0.3/debian/changelog libnss-myhostname-0.3/debian/changelog
--- libnss-myhostname-0.3/debian/changelog 2012-01-17 22:08:50.0 +0100
+++ libnss-myhostname-0.3/debian/changelog 2013-05-29 20:06:49.0 +0200
@@ -1,3 +1,9 @@
+libnss-myhostname (0.3-5~deb7u1) stable; urgency=low
+
+ * Ignore link-local addresses (Closes: #705900)
+
+ -- Joachim Breitner Wed, 29 May 2013 20:05:35 +0200
+
libnss-myhostname (0.3-4) unstable; urgency=low
* Fix Package's description to reflect changed behaviour. (Closes: #656218)
diff -Nru libnss-myhostname-0.3/debian/patches/0005-Ignore-link-local-addresses.patch libnss-myhostname-0.3/debian/patches/0005-Ignore-link-local-addresses.patch
--- libnss-myhostname-0.3/debian/patches/0005-Ignore-link-local-addresses.patch 1970-01-01 01:00:00.0 +0100
+++ libnss-myhostname-0.3/debian/patches/0005-Ignore-link-local-addresses.patch 2013-05-29 20:07:00.0 +0200
@@ -0,0 +1,27 @@
+From cce547eac7d27b4476e646bfead3ba14b57a6ccc Mon Sep 17 00:00:00 2001
+From: Joachim Breitner
+Date: Mon, 13 May 2013 10:34:57 +0200
+Subject: Ignore link-local addresses
+
+Closes: #705900
+---
+ netlink.c | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/netlink.c b/netlink.c
+index 29f38e3..9bbed7e 100644
+--- a/netlink.c
b/netlink.c
+@@ -178,6 +178,12 @@ int ifconf_acquire_addresses(struct address **_list, unsigned *_n_list) {
+ if (!address)
+ continue;
+
++ // Avoid link-local address
++ // http://bugs.debian.org/705900
++ if (ifaddrmsg->ifa_family == AF_INET6 &&
++ IN6_IS_ADDR_LINKLOCAL((const struct in6_addr *)address))
++ continue;
++
+ list = realloc(list, (n_list+1) * sizeof(struct address));
+ if (!list) {
+ r = -ENOMEM;
diff -Nru libnss-myhostname-0.3/debian/patches/series libnss-myhostname-0.3/debian/patches/series
--- libnss-myhostname-0.3/debian/patches/series 2011-06-28 12:52:53.0 +0200
+++ libnss-myhostname-0.3/debian/patches/series 2013-05-29 20:07:00.0 +0200
@@ -2,3 +2,4 @@
0002-Use-172.0.1.1.patch
0003-Use-legacy-getifaddrs-on-GNU-kFreeBSD.patch
0004-Ensure-a-LANG-independent-generated-README.patch
+0005-Ignore-link-local-addresses.patch
signature.asc
Description: This is a digitally signed message part
Bug#703602: unblock: libreoffice/3.5.4+dfsg2-1
On Wed, 2013-05-29 at 19:16 +0200, Rene Engelhard wrote: > +libreoffice (1:3.5.4+dfsg2-0+deb7u2) stable; urgency=low > + > + * debian/rules: > +- work around possible failure install-common target with missing > + ca-XV .dirs/.install... (closes: #685723) > +- hack around broken "*" directory in debian/tmp/pkg on kfreebsd-* > + extremely slowing down the install target... Please go ahead; I'll keep my fingers crossed. :) > After this the test failure on mips[1] remains, but I *hope* this is > one-time-off. Should I disable tests > on mips* (or better: make them non-fatal there which is already the case in > sid/jessie) or should I upload > with the above and let's hope? For now I'd prefer to leave the tests as-is and see how it goes. 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/1369850903.28736.5.ca...@jacala.jungle.funky-badger.org
Bug#703602: unblock: libreoffice/3.5.4+dfsg2-1
Hi, On Mon, May 27, 2013 at 12:44:39PM +0100, Adam D. Barratt wrote: > Control: tags -1 + pending > > On Thu, 2013-03-21 at 19:40 +0100, Rene Engelhard wrote: > > 19:28 < jcristau> i could live with having that fixed in r1 > > 19:28 < jcristau> if it can't go through unstable anyway > > 19:29 < _rene_> ok, so I'll do both in r1.. *sigh* > > Flagged for acceptance. Unfortunately it failed to build because questionable assumptions about the build environment (yes, I know, but it was back then to save *hours* of build time on the buildds, now it's binary-arch/binary-indep and that issue is gone) fail: See e.g. https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=kfreebsd-i386&ver=1%3A3.5.4%2Bdfsg2-0%2Bdeb7u1&stamp=1369823022 and http://bugs.debian.org/685723 I'd upload with the following (everything was already in 3.6 packages upwards and just backported to the 3.5 packages now) if you agree: diff --git a/changelog b/changelog index 9937d7b..e5a79f3 100644 --- a/changelog +++ b/changelog @@ -1,3 +1,13 @@ +libreoffice (1:3.5.4+dfsg2-0+deb7u2) stable; urgency=low + + * debian/rules: +- work around possible failure install-common target with missing + ca-XV .dirs/.install... (closes: #685723) +- hack around broken "*" directory in debian/tmp/pkg on kfreebsd-* + extremely slowing down the install target... + + -- Rene Engelhard Wed, 29 May 2013 18:31:38 +0200 + libreoffice (1:3.5.4+dfsg2-0+deb7u1) stable; urgency=low * src/17410483b5b5f267aa18b7e00b65e6e0-hsqldb_1_8_0.zip: remove diff --git a/rules b/rules index da5bb06..08c2d43 100755 --- a/rules +++ b/rules @@ -1671,6 +1671,11 @@ $(STAMP_DIR)/install: $(STAMP_DIR)/build export OOINSTBASE=$(OODIR); \ export OOO_LANGS_LIST="$(ISOS)"; \ $(CURDIR)/debian/scripts/gid2pkgdirs.sh + + # FIXME + if echo $(DEB_HOST_ARCH) | grep -q kfreebsd; then \ + cd $(CURDIR)/debian/tmp/pkg && rm -rf \*; \ + fi # prepare install/dir files for dh for i in `cd $(CURDIR)/debian/tmp/pkg; ls -1 | xargs`; do \ @@ -1689,14 +1694,18 @@ $(STAMP_DIR)/install: $(STAMP_DIR)/build # and ca-XV in -ca... ifeq (ca-XV,$(findstring ca-XV,$(LANGPACKISOS))) - cat debian/libreoffice-l10n-ca-XV.dirs >> debian/libreoffice-l10n-ca.dirs - cat debian/libreoffice-l10n-ca-XV.install >> debian/libreoffice-l10n-ca.install - rm -f debian/libreoffice-l10n-ca-XV.dirs debian/libreoffice-l10n-ca-XV.install + if [ -f debian/libreoffice-l10n-ca-XV.dirs -a -f debian/libreoffice-l10n-ca-XV.install ]; then \ + cat debian/libreoffice-l10n-ca-XV.dirs >> debian/libreoffice-l10n-ca.dirs; \ + cat debian/libreoffice-l10n-ca-XV.install >> debian/libreoffice-l10n-ca.install; \ + rm -f debian/libreoffice-l10n-ca-XV.dirs debian/libreoffice-l10n-ca-XV.install; \ + fi endif ifeq (ca-XV,$(findstring ca-XV,$(HELPISOS))) - cat debian/libreoffice-help-ca-XV.dirs >> debian/libreoffice-help-ca.dirs - cat debian/libreoffice-help-ca-XV.install >> debian/libreoffice-help-ca.install - rm -f debian/libreoffice-help-ca-XV.dirs debian/libreoffice-help-ca-XV.install + if [ -f debian/libreoffice-help-ca-XV.dirs -a -f debian/libreoffice-help-ca-XV.install ]; then \ + cat debian/libreoffice-help-ca-XV.dirs >> debian/libreoffice-help-ca.dirs; \ + cat debian/libreoffice-help-ca-XV.install >> debian/libreoffice-help-ca.install; \ + rm -f debian/libreoffice-help-ca-XV.dirs debian/libreoffice-help-ca-XV.install; \ + fi endif # fixup case (-l10n-pt-BR -> l10n-pt-br etc.) After this the test failure on mips[1] remains, but I *hope* this is one-time-off. Should I disable tests on mips* (or better: make them non-fatal there which is already the case in sid/jessie) or should I upload with the above and let's hope? Regards, Rene [1] https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=mips&ver=1%3A3.5.4%2Bdfsg2-0%2Bdeb7u1&stamp=1369797883 I see it's been requeued, though. -- 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/20130529171613.gi5...@rene-engelhard.de
Bug#708631: pu: package cyrus-imapd-2.4/2.4.16-4+deb7u1
I have uploaded a version to ftp-master, but nothing much has happened. Has something went wrong? O. On Tue, May 21, 2013 at 11:24 PM, Cyril Brulebois wrote: > Control: tag -1 confirmed > > Ondřej Surý (17/05/2013): > > Thanks for the review. > > > > Attached is fixed debdiff. > > Looks good to me; feel free to downgrade urgency to "low" though, it > doesn't make much sense for spu. > > Mraw, > KiBi. > -- Ondřej Surý
Bug#710234: Bug#685749: pygrub
Hi Guido, I just checked the latest patch you added to this bugreport and I didn't found the patch for the pygrub binary path. Maybe is missed something? Take care, Oliver -- 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/20130529161717.ga1...@webmail.seufer.de
Bug#710108: marked as done (nmu: dynare_4.3.3-2)
Your message dated Wed, 29 May 2013 18:30:27 +0200 with message-id <1369845027.1476.59.ca...@rama.villemot.name> and subject line Re: Bug#710108: nmu: dynare_4.3.3-2 has caused the Debian Bug report #710108, regarding nmu: dynare_4.3.3-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.) -- 710108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Dear Release Team, A new major version of libmatio has been uploaded, which involves a SONAME bump. The package dynare needs to be recompiled (a sourceful upload should not be needed, see #706803). I included a dep-wait in the following commands, to make sure that dynare is recompiled against the new libmatio. Sorry for the noise if this is not needed. nmu dynare_4.3.3-2 . ALL . -m "rebuild against libmatio 1.5" dw dynare_4.3.3-2 . ALL . -m "libmatio2" Cheers, -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Le mardi 28 mai 2013 à 12:53 +0200, Sébastien Villemot a écrit : > A new major version of libmatio has been uploaded, which involves a SONAME > bump. The package dynare needs to be recompiled (a sourceful upload should not > be needed, see #706803). A new sourceful upload of dynare is on its way, for unrelated reasons. Closing. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#710234: Bug#685749: pygrub
On Wed, May 29, 2013 at 06:17:17PM +0200, Oliver wrote: > Hi Guido, > > I just checked the latest patch you added to this bugreport and I didn't found > the patch for the pygrub binary path. Maybe is missed something? The patch in the bugreport was applied. _Please_ folks test this stuff and don't assume it works out of the box when the maintainer states he doesn't run xen. Cheers, -- Guido > > Take care, > > Oliver > -- 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/20130529162953.ga15...@bogon.sigxcpu.org
NEW changes in stable-new
Processing changes file: nbd_3.2-4~deb7u1_mips.changes ACCEPT -- 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/e1uhipq-0005bq...@franck.debian.org
Bug#710234: pu: package libvirt/0.9.12-11+wheezy1
Hi Adam,
On Wed, May 29, 2013 at 10:34:59AM +0100, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo wheezy
>
> Hi,
>
> On 2013-05-29 10:22, Guido Günther wrote:
> >I'd like to update libvirt with wheezy's first point release since it
> >misses two important bug fixes. The first one addresses xen pv
> >support
> >(#685749) while the other one adresses a leak (#705205).
>
> The bug logs suggest that those bugs are not yet fixed in unstable.
> Please could you clarify, and update their statuses if required?
This kind of overlapped with the upload of 1.0.5 to unstable so it
should be o.k. now. New full debdiff attached. I've changed the version
number to 0.9.12-11+wheezy1 as well.
Cheers,
-- Guido
diff --git a/debian/changelog b/debian/changelog
index 14ccdb6..853b2d0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+libvirt (0.9.12-11+wheezy1) wheezy-proposed-updates; urgency=low
+
+ [ Guido Günther ]
+ * [af660e5] Allow xen toolstack to find it's binaries.
+Thanks to George Dunlap for the patch. (Closes: #685749)
+
+ [ Luca Tettamanti ]
+ * [90d8287] Fix leak in virStorageBackendLogicalMakeVol
+(Closes: #705205)
+
+ -- Guido Günther Wed, 29 May 2013 13:42:44 +0200
+
libvirt (0.9.12-11) unstable; urgency=low
* [422c506] Use "getent passwd" instead of the non existing "getent user"
diff --git a/debian/patches/debian/Allow-xen-toolstack-to-find-it-s-binaries.patch b/debian/patches/debian/Allow-xen-toolstack-to-find-it-s-binaries.patch
new file mode 100644
index 000..3ea255d
--- /dev/null
+++ b/debian/patches/debian/Allow-xen-toolstack-to-find-it-s-binaries.patch
@@ -0,0 +1,243 @@
+From: George Dunlap
+Date: Tue, 2 Oct 2012 19:19:04 +0200
+Subject: Allow xen toolstack to find it's binaries
+
+Closes: #685749
+---
+ docs/schemas/capability.rng|4 ++--
+ src/xen/xen_hypervisor.c |6 +++---
+ tests/xencapsdata/xen-i686-pae-hvm.xml |6 +++---
+ tests/xencapsdata/xen-i686-pae.xml |2 +-
+ tests/xencapsdata/xen-i686.xml |2 +-
+ tests/xencapsdata/xen-ia64-be-hvm.xml |6 +++---
+ tests/xencapsdata/xen-ia64-be.xml |2 +-
+ tests/xencapsdata/xen-ia64-hvm.xml |6 +++---
+ tests/xencapsdata/xen-ia64.xml |2 +-
+ tests/xencapsdata/xen-ppc64.xml|2 +-
+ tests/xencapsdata/xen-x86_64-hvm.xml | 10 +-
+ tests/xencapsdata/xen-x86_64.xml |2 +-
+ 12 files changed, 25 insertions(+), 25 deletions(-)
+
+diff --git a/docs/schemas/capability.rng b/docs/schemas/capability.rng
+index 8c928bc..b1930ba 100644
+--- a/docs/schemas/capability.rng
b/docs/schemas/capability.rng
+@@ -241,13 +241,13 @@
+
+
+
+-
++
+
+
+
+
+
+-
++
+
+
+
+diff --git a/src/xen/xen_hypervisor.c b/src/xen/xen_hypervisor.c
+index 86f64f1..85ebcda 100644
+--- a/src/xen/xen_hypervisor.c
b/src/xen/xen_hypervisor.c
+@@ -2347,10 +2347,10 @@ xenHypervisorBuildCapabilities(virConnectPtr conn,
+ guest_archs[i].model,
+ guest_archs[i].bits,
+ (STREQ(hostmachine, "x86_64") ?
+- "/usr/lib64/xen/bin/qemu-dm" :
+- "/usr/lib/xen/bin/qemu-dm"),
++ "qemu-dm" :
++ "qemu-dm"),
+ (guest_archs[i].hvm ?
+- "/usr/lib/xen-default/boot/hvmloader" :
++ "hvmloader" :
+ NULL),
+ 1,
+ machines)) == NULL) {
+diff --git a/tests/xencapsdata/xen-i686-pae-hvm.xml b/tests/xencapsdata/xen-i686-pae-hvm.xml
+index 7cde6df..cf1953d 100644
+--- a/tests/xencapsdata/xen-i686-pae-hvm.xml
b/tests/xencapsdata/xen-i686-pae-hvm.xml
+@@ -20,7 +20,7 @@
+ xen
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
++ qemu-dm
+ xenpv
+
+
+@@ -34,8 +34,8 @@
+ hvm
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
+- /usr/lib/xen-default/boot/hvmloader
++ qemu-dm
++ hvmloader
+ xenfv
+
+
+diff --git a/tests/xencapsdata/xen-i686-pae.xml b/tests/xencapsdata/xen-i686-pae.xml
+index 3dba6eb..c774d6c 100644
+--- a/tests/xencapsdata/xen-i686-pae.xml
b/tests/xencapsdata/xen-i686-pae.xml
+@@ -20,7 +20,7 @@
+ xen
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
++ qemu-dm
+ xenpv
+
+
+diff --git a/tests/xencapsdata/xen-i686.xml b/tests/xencapsdata/xen-i686.xml
+index 22d7685..bc36cbf 100644
+--- a/tests/xencapsdata/xen-i686.xml
b/tests/xencapsdata/xen-i686.xml
+@@ -17,7 +17,7 @@
+ xen
+
+ 32
+-
Bug#673538: libobjc3 -> libobjc4 transition
Hello,
Any news about this transition?.
I am thinking in upload my gnustep package but I am waiting for it.
In advance thank you so much.
Kind regards,
--
Julián Moreno Patiño
Debian Developer
.''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `' http://debian.org/
`- GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513
NEW changes in stable-new
Processing changes file: lapack_3.4.1+dfsg-1+deb70u1_s390x.changes ACCEPT Processing changes file: clutter-gst_1.5.4-1+build0_s390x.changes ACCEPT -- 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/e1uheqq-0001dh...@franck.debian.org
Processed: Re: Bug#710234: pu: package libvirt/0.9.12-12
Processing control commands: > tags -1 + moreinfo wheezy Bug #710234 [release.debian.org] pu: package libvirt/0.9.12-12 Added tag(s) wheezy. -- 710234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b710234.13698201097790.transcr...@bugs.debian.org
Bug#710234: pu: package libvirt/0.9.12-12
Control: tags -1 + moreinfo wheezy Hi, On 2013-05-29 10:22, Guido Günther wrote: I'd like to update libvirt with wheezy's first point release since it misses two important bug fixes. The first one addresses xen pv support (#685749) while the other one adresses a leak (#705205). The bug logs suggest that those bugs are not yet fixed in unstable. Please could you clarify, and update their statuses if required? 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/d69246416f1a402616bf8aef3c48e...@mail.adsl.funky-badger.org
Processed: Re: Bug#710234: pu: package libvirt/0.9.12-12
Processing control commands: > tag -1 moreinfo Bug #710234 [release.debian.org] pu: package libvirt/0.9.12-12 Added tag(s) moreinfo. -- 710234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b710234.13698201047756.transcr...@bugs.debian.org
Bug#710234: pu: package libvirt/0.9.12-12
Control: tag -1 moreinfo Guido Günther (29/05/2013): > I'd like to update libvirt with wheezy's first point release since it > misses two important bug fixes. The first one addresses xen pv support > (#685749) while the other one adresses a leak (#705205). > > Diff attached. O.k. to uplaod to wheezy-proposed-updates? Hello, from the version info in the BTS, both bugs need fixing in unstable too. We usually like getting bugfixes tested, and uploading there helps. Also, please send a source debdiff, so that we can check things like versioning and target distribution. Mraw, KiBi. signature.asc Description: Digital signature
Bug#710234: pu: package libvirt/0.9.12-12
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
Hi,
I'd like to update libvirt with wheezy's first point release since it
misses two important bug fixes. The first one addresses xen pv support
(#685749) while the other one adresses a leak (#705205).
Diff attached. O.k. to uplaod to wheezy-proposed-updates?
Cheers,
-- Guido
-- System Information:
Debian Release: jessie/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing'), (50, 'unstable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (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/dash
diff --git a/debian/patches/debian/Allow-xen-toolstack-to-find-it-s-binaries.patch b/debian/patches/debian/Allow-xen-toolstack-to-find-it-s-binaries.patch
new file mode 100644
index 000..3ea255d
--- /dev/null
+++ b/debian/patches/debian/Allow-xen-toolstack-to-find-it-s-binaries.patch
@@ -0,0 +1,243 @@
+From: George Dunlap
+Date: Tue, 2 Oct 2012 19:19:04 +0200
+Subject: Allow xen toolstack to find it's binaries
+
+Closes: #685749
+---
+ docs/schemas/capability.rng|4 ++--
+ src/xen/xen_hypervisor.c |6 +++---
+ tests/xencapsdata/xen-i686-pae-hvm.xml |6 +++---
+ tests/xencapsdata/xen-i686-pae.xml |2 +-
+ tests/xencapsdata/xen-i686.xml |2 +-
+ tests/xencapsdata/xen-ia64-be-hvm.xml |6 +++---
+ tests/xencapsdata/xen-ia64-be.xml |2 +-
+ tests/xencapsdata/xen-ia64-hvm.xml |6 +++---
+ tests/xencapsdata/xen-ia64.xml |2 +-
+ tests/xencapsdata/xen-ppc64.xml|2 +-
+ tests/xencapsdata/xen-x86_64-hvm.xml | 10 +-
+ tests/xencapsdata/xen-x86_64.xml |2 +-
+ 12 files changed, 25 insertions(+), 25 deletions(-)
+
+diff --git a/docs/schemas/capability.rng b/docs/schemas/capability.rng
+index 8c928bc..b1930ba 100644
+--- a/docs/schemas/capability.rng
b/docs/schemas/capability.rng
+@@ -241,13 +241,13 @@
+
+
+
+-
++
+
+
+
+
+
+-
++
+
+
+
+diff --git a/src/xen/xen_hypervisor.c b/src/xen/xen_hypervisor.c
+index 86f64f1..85ebcda 100644
+--- a/src/xen/xen_hypervisor.c
b/src/xen/xen_hypervisor.c
+@@ -2347,10 +2347,10 @@ xenHypervisorBuildCapabilities(virConnectPtr conn,
+ guest_archs[i].model,
+ guest_archs[i].bits,
+ (STREQ(hostmachine, "x86_64") ?
+- "/usr/lib64/xen/bin/qemu-dm" :
+- "/usr/lib/xen/bin/qemu-dm"),
++ "qemu-dm" :
++ "qemu-dm"),
+ (guest_archs[i].hvm ?
+- "/usr/lib/xen-default/boot/hvmloader" :
++ "hvmloader" :
+ NULL),
+ 1,
+ machines)) == NULL) {
+diff --git a/tests/xencapsdata/xen-i686-pae-hvm.xml b/tests/xencapsdata/xen-i686-pae-hvm.xml
+index 7cde6df..cf1953d 100644
+--- a/tests/xencapsdata/xen-i686-pae-hvm.xml
b/tests/xencapsdata/xen-i686-pae-hvm.xml
+@@ -20,7 +20,7 @@
+ xen
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
++ qemu-dm
+ xenpv
+
+
+@@ -34,8 +34,8 @@
+ hvm
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
+- /usr/lib/xen-default/boot/hvmloader
++ qemu-dm
++ hvmloader
+ xenfv
+
+
+diff --git a/tests/xencapsdata/xen-i686-pae.xml b/tests/xencapsdata/xen-i686-pae.xml
+index 3dba6eb..c774d6c 100644
+--- a/tests/xencapsdata/xen-i686-pae.xml
b/tests/xencapsdata/xen-i686-pae.xml
+@@ -20,7 +20,7 @@
+ xen
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
++ qemu-dm
+ xenpv
+
+
+diff --git a/tests/xencapsdata/xen-i686.xml b/tests/xencapsdata/xen-i686.xml
+index 22d7685..bc36cbf 100644
+--- a/tests/xencapsdata/xen-i686.xml
b/tests/xencapsdata/xen-i686.xml
+@@ -17,7 +17,7 @@
+ xen
+
+ 32
+- /usr/lib/xen/bin/qemu-dm
++ qemu-dm
+ xenpv
+
+
+diff --git a/tests/xencapsdata/xen-ia64-be-hvm.xml b/tests/xencapsdata/xen-ia64-be-hvm.xml
+index e56e306..ddab377 100644
+--- a/tests/xencapsdata/xen-ia64-be-hvm.xml
b/tests/xencapsdata/xen-ia64-be-hvm.xml
+@@ -17,7 +17,7 @@
+ xen
+
+ 64
+- /usr/lib/xen/bin/qemu-dm
++ qemu-dm
+ xenpv
+
+
+@@ -31,8 +31,8 @@
+ hvm
+
+ 64
+- /usr/lib/xen/bin/qemu-dm
+- /usr/lib/xen-default/boot/hvmloader
++ qemu-dm
++ hvmloader
+ xenfv
+
+
+diff --git a/tests/xenca
NEW changes in stable-new
Processing changes file: clutter-gst_1.5.4-1+build0_kfreebsd-amd64.changes ACCEPT -- 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/e1uhard-0002io...@franck.debian.org
