NAK
Please use the --testdebs-repo approach for complex¹ upgrade scenarios.
The 'pass multiple .deb files' and 'pass .changes' approaches are not
able to do realistic updates (or even installation). So let's not add
another hack to a broken feature (using dpkg to manually install packages)
¹
On Freitag, 21. November 2014, Andreas Beckmann wrote:
Please use the --testdebs-repo approach for complex¹ upgrade scenarios.
The 'pass multiple .deb files' and 'pass .changes' approaches are not
able to do realistic updates (or even installation). So let's not add
another hack to a broken
On 2014-11-21 16:03, Holger Levsen wrote:
On Freitag, 21. November 2014, Andreas Beckmann wrote:
Please use the --testdebs-repo approach for complex¹ upgrade scenarios.
The 'pass multiple .deb files' and 'pass .changes' approaches are not
able to do realistic updates (or even installation). So
On Freitag, 21. November 2014, Andreas Beckmann wrote:
b), and offer an easy way to do this:
[...]
PS: I sometimes use something based on this script, but it is in no way
automatic
more+better documentation is the answer, I guess. And your script should
probably be included in either the
control: tags -1 - patch
signature.asc
Description: This is a digitally signed message part.
control: severity -1 normal
Hi Helmut,
thanks for your bug report with patch, much appreciated! (That said, a patch
in git format would be preferred even more! (And reading the NMU bits in it
feels a bit strange.. with non-NMU intend ;) as an NMU it would have been
totally fine...))
On
Package: piuparts
Version: 0.59
Severity: wishlist
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
When testing the fix for #761449 with piuparts, the result is a failure.
It fails upgrading the packages, because piuparts does not allow dpkg to
deconfigure packages. Since one package
7 matches
Mail list logo