su, 2005-09-04 kello 11:32 -0400, Joey Hess kirjoitti:
Lars Wirzenius wrote:
That's what I wanted to say, but, alas, it doesn't work. debootstrap
fails to create an etch or sid chroot for me at the moment.
It does if you run it with --resolve-deps.
Indeed it does. Mea culpa. I have now
On Sat, Sep 03, 2005 at 11:53:35PM +0300, Lars Wirzenius wrote:
Reading piuparts logs en masse is tedious and I would be extremely
happy if all developers did it for their own packages. Go ahead,
please prevent me from becoming a top ten bug reporter. :)
Since you've already run it, are the
su, 2005-09-04 kello 16:25 +1000, Paul TBBle Hampson kirjoitti:
On Sat, Sep 03, 2005 at 11:53:35PM +0300, Lars Wirzenius wrote:
Reading piuparts logs en masse is tedious and I would be extremely
happy if all developers did it for their own packages. Go ahead,
please prevent me from becoming
On Sun, Sep 04, 2005 at 11:19:35AM +0300, Lars Wirzenius wrote:
su, 2005-09-04 kello 16:25 +1000, Paul TBBle Hampson kirjoitti:
On Sat, Sep 03, 2005 at 11:53:35PM +0300, Lars Wirzenius wrote:
Reading piuparts logs en masse is tedious and I would be extremely
happy if all developers did it for
On Sun, 04 Sep 2005, Marc 'HE' Brockschmidt wrote:
Lars Wirzenius [EMAIL PROTECTED] writes:
* Some packages still don't use debconf for prompting, and
instead do silly stuff that assumed it is OK to read and
write /dev/tty.
Actually, the policy explicitly
Lars Wirzenius wrote:
That's what I wanted to say, but, alas, it doesn't work. debootstrap
fails to create an etch or sid chroot for me at the moment.
It does if you run it with --resolve-deps.
Since this will remain true probably forever except during
freezes/releases, people might as well
I wrote piuparts, a package installation, upgrading, and removal
testing tool, in June, and have been running it over etch since.
Most packages succeed, and many that fail do so because something
they depend on fails. (If piuparts notices a file left behind on the
filesystem that dpkg did not know
On Sat, Sep 03, 2005 at 11:53:35PM +0300, Lars Wirzenius wrote:
* Unconditional use of non-essential packages in postrm when a
package is purged (policy, 7.2, description of Depends). One
of the most common reasons is because the package uses ucf.
Which is because
Lars Wirzenius [EMAIL PROTECTED] writes:
* Some packages still don't use debconf for prompting, and
instead do silly stuff that assumed it is OK to read and
write /dev/tty.
Actually, the policy explicitly allows this:
| The maintainer scripts are guaranteed to run
9 matches
Mail list logo
