Your message dated Sat, 25 May 2013 11:54:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#676694: piuparts: [install-upgrade] should first
install from distribution
has caused the Debian Bug report #676694,
regarding piuparts: [install-upgrade] should first install from distribution
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 [email protected]
immediately.)
--
676694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676694
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: piuparts
Version: 0.44
Severity: normal
File: /usr/sbin/piuparts
Tags: patch
Usertags: debian-packaging
User: [email protected]
Usertags: piuparts
Hi there!
I tried to look at the piuparts documentation, but I was unable to find
a solution to the problem below, so I am sorry if it is a mistake from
my side.
When doing an install-upgrade test, the apt-get package installation
should be forced from the first distribution set via -d (using the
apt-get -t option). Otherwise, if the package being tested depends on
the same binary version of other packages, then installation from
official sources is not possible. Git patch attached.
I encountered this bug while testing the new bacula-console package,
which depends on "bacula-common (= ${binary:Version})". I setup a local
APT repository (managed via mini-dinstall and bindmounted in the
pbuilder chroot) for the packages to be tested. But after installation,
piuparts always resolved the problem removing bacula-console instead of
installing the new bacula-common version.
Piuparts logs are available upon request or simply grab the testing
package at <http://pkg-bacula.alioth.debian.org/tmp/> ;-)
Thx, bye,
Gismo / Luca
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages piuparts depends on:
ii apt 0.9.5.1
ii debootstrap 1.0.40
ii lsb-release 4.1+Debian6
ii lsof 4.86+dfsg-1
ii python 2.7.3~rc2-1
ii python-apt 0.8.4
ii python-debian 0.1.21
ii python-debianbts 1.11
ii python2.6 2.6.7-4
ii python2.7 2.7.3~rc2-2.1
piuparts recommends no packages.
Versions of packages piuparts suggests:
ii ghostscript 9.05~dfsg-6
pn python-rpy <none>
-- no debconf information
From 165f988754af80a3ebb21599a9d9179d48c30eab Mon Sep 17 00:00:00 2001
From: Luca Capello <[email protected]>
Date: Fri, 8 Jun 2012 22:58:41 +0200
Subject: [PATCH] piuparts.py: install from distribution before upgrading
When doing an install-upgrade-purge test, force the apt-get package
installation from the first distribution set.
Closes: #nnnnnn
---
piuparts.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/piuparts.py b/piuparts.py
index 9015aa4..41b528c 100644
--- a/piuparts.py
+++ b/piuparts.py
@@ -1184,10 +1184,10 @@ class Chroot:
if settings.list_installed_files:
pre_info = self.save_meta_data()
- self.run(["apt-get", "-y", "install"] + packages)
+ self.run(["apt-get", "-t", settings.debian_distros[0], "-y", "install"] + packages)
self.list_installed_files (pre_info, self.save_meta_data())
else:
- self.run(["apt-get", "-y", "install"] + packages)
+ self.run(["apt-get", "-t", settings.debian_distros[0], "-y", "install"] + packages)
self.run_scripts("post_install")
--
1.7.10
pgpAhcVXnRxoh.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.49
On 2012-06-13 12:58, Andreas Beckmann wrote:
> So you provide a new package source that contains all the packages from
> new.changes, but that repository is only to be used when new.deb is to
> be installed. I'll use the codename 'target' for this partial repository
> (and the repository I'll call target-repository):
There are now the --testdebs-repo and --distupgrade-to-testdebs options
that should help to accomplish these test paths.
Andreas
--- End Message ---
