Package: debian-policy
Version: 4.1.1.1
Severity: wishlist
Hello,
the question of how to tell in postinst whether this is an upgrade or a
first installation comes up every now and then. Again yesterday in
#debian-mentors. Therefore I'm asking for a clarifcation in
6.5. Summary of ways
Package: debian-policy
Version: 4.1.1.1
Severity: wishlist
Hello,
this is in the category of "It should be obvious to anybody but I'd
prefer things are well-defined in case anybody wishes to start an
argument over that". So rather nitpicking.
Version number re-usage happens, probably always by
Guillem Jover wrote...
> I think this is actually #542288? But I'll let the editors decide.
It is. So much for the feeling "It was hard to believe nobody came up
with this beforehand". Also, there's quite a lot to read now.
> > +nmu Non-maintainer upload for native packages
>
> I've actually
Package: debian-policy
Severity: normal
[
"version" is a horrible search term, hopefully I did not miss any
other report about this.
]
Hello,
Over time, several suffixes to version numbers have evolved to denote
uploads outside the regular, incremental upload to unstable. In my
opinion the
Package: debian-policy
Severity: normal
Following a recent discussion on debian-devel[0], I'd like to
formalize the (XS-)Build-Indep-Architecture: header mentioned there.
As an initial wording (probably 5.6.30):
This header is useful in the rare case where Architecture: all
packages cannot be
Package: debian-policy
Severity: normal
Hi,
recently I stumbled over the following paragraph in 10.6:
If a package needs any special device files that are not
included in the base system, it must call MAKEDEV in the
postinst script, after notifying the user.
and I think it needs an
Package: debian-policy
Version: 3.9.2.0
Severity: minor
Hi there,
just some nitpicking regarding upgrading-checklist:
| 9.1.1
| Packages installing to architecture-specific subdirectories of
| `/url/lib' must use the value returned by (...)
Obviously that should be
Salvatore Bonaccorso wrote...
This seems to be fixed in git repository, see
http://bugs.debian.org/626408
No idea how I could have missed that one when checking the BTS.
Sorry for the noise.
Christoph
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject
8 matches
Mail list logo
