Hi, I am tracking down a bug that regards upgrades from wheezy. The code that I have to add will only run when upgrading from wheezy, not from a version in unstable. That means, when using -d stable -d unstable test-package.deb will not work, since it first upgrades to unstable and then to the new package. I think it makes sense to have also an option where first the stable variant is installed, and then with gdebi or similar the package on the commandline including its dependencies from unstable and necessary chagnes. Thanks Norbert
put debs into a local repository, e.g. /tmp/repo, run dpkg-scanpackages > Packages there and add this to piuparts:
control: tags -1 + moreinfo thanks Hi Norbert, thank you for using piuparts! what do you expect it to do? (I also dont understand the bug title, care to explain?) Do you want to test your package from wheezy to your new package to unstable? Or do you want to test your package from wheezy to your new package? cheers, Holger
Hi Andreas, hi Holger, Yes, thanks, that is what I was searching for. I did exactely this manually in a cowbuilder chroot, but having piuparts doing some of these things automatically would be great. Please, yes. Sorry, the bug title was rubbish. What I want is * install <pkg> in wheezy * dist-upgrade to sid but use <pkg> from the command line instead of unstable The reason is that some code in the postinst scripts is only triggered on upgrades from wheezy, and not from unstable. So an upgrade path wheezy -> sid -> testpackage will not help. Thanks Norbert
tags 717125 + gift retitle 717125 document how to test upgrades from wheezy to sid using local pacḱages thanks Hi, [...] It would be great if someone could update the documentation to explain this use case better. This is *your* chance to become part of the small circle of piuparts contributors! :-) cheers, Holger
Hi, https://wiki.debian.org/piuparts/HowTos#Setup_a_private_repo_using_reprepro is the other obvious place to document this... cheers, Holger