On Wed, Oct 09, 2019 at 08:30:03PM +0200, Guillem Jover wrote:
> > thanks for that information! do you agree there's nothing to be added to
> > dev-ref?
> Yeah, looks like it.
& thanks for confirming this too! :)
--
cheers,
Holger
---
package: developers-reference
severity: wishlist
- Forwarded message from "Adam D. Barratt" -
Date: Tue, 22 Oct 2019 05:59:08 +0100
From: "Adam D. Barratt"
To: debian-devel-annou...@lists.debian.org
Subject: debian.org mail handling updates
Message-ID: <21e81b9e413c3b7c36ba271adbcf400b3
On Wed, Oct 23, 2019 at 12:13:00PM -0700, Russ Allbery wrote:
> > From d5895ca185fa1d678a098697d9e1c601c84f45dd Mon Sep 17 00:00:00 2001
> > From: Stephen Kitt
> > Date: Mon, 7 Oct 2019 21:09:52 +0200
> > Subject: [PATCH] Allow strong dependencies on X font packages
>
> > The X server shipped in
control: tags +1 moreinfo
On Sun, Aug 11, 2019 at 11:27:46PM +, Osamu Aoki wrote:
> Source: developers-reference
> Please mention email gate
> https://lists.debian.org/debian-devel/1999/12/msg00627.html
does that even still work today? and if so, how?
--
cheers,
Holger
--
On Thu, Oct 31, 2019 at 09:10:42PM +0100, Ansgar wrote:
> Sure, changes@db.d.o still works and is the only way to configure some
> settings. It is documented here: https://db.debian.org/doc-mail.html
aaah! I even use that regulary via a script in ~/bin here :)
So I guess for developers-reference
On Fri, Nov 01, 2019 at 11:20:59AM -0700, Russ Allbery wrote:
> > I think there is already a lintian warning:
> >
> > https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script.html
> Oh! I should have checked rather than assuming. It would ideally be nice
> to make it a warning
hi Sean,
On Sun, Jul 22, 2018 at 03:54:05PM +0800, Sean Whitton wrote:
> Section 6.4 should perhaps recommend `command -v` not `which`, because
> Debian Policy 4.1.5.0 allows maintainer scripts to assume SUSv4, which
> requires support for `command -v`.
three comments:
a.) 'should perhaps' is a
On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote:
> Changes:
>
> * Add "prohibited" to the terms for requirements
> * Add another tier (Policy advice) using encouraged and discouraged
> * Stop confusing may and optional with wishlist bugs
> * Add terms for the collective set of Policy
Hi,
thanks for your feedback, I've now rewritten the paragraph in question
to simply read:
If you need to check for the existence of a command, you should use
something like
::
if command -v install-docs > /dev/null; then ...
You can use this function to search ``$PATH`` for a command
Hi Simon, everyone:
On Fri, Mar 13, 2020 at 11:32:00AM +, Simon McVittie wrote:
> To be completely clear about this for those using this bug report as a
> stand-in for the requested documentation in devref (like me), it's now at:
> https://auth.buildd.debian.org/auth/giveback.cgi?pkg=&suite=&a
Hi Daniel,
On Sat, Mar 14, 2020 at 06:14:02PM +, Daniel Shahaf wrote:
> The documentation of the "Closes: #NN" changelog syntax describes
> the syntax in terms of a Perl regular expression. However, not all
> readers know Perl. I suggest to describe the semantics in English,
> in additio
Hi Moritz,
On Thu, Apr 09, 2020 at 08:32:58AM +0200, Moritz Mühlenhoff wrote:
> The current version in unstable (11.0.10) again reads:
> | If it's an upstream problem, you have to forward it to the upstream author.
> | Forwarding a bug is not enough, you have to check at each release if the
> | bu
On Wed, Apr 15, 2020 at 06:33:29PM +0200, Bill Allombert wrote:
> > In section 5.6.1, it is mentioned that the dcut command can be used to
> > remove packages from the upload queue.
> > However, section 5.9.2.1 states that it is no longer possible to remove
> > packages from incoming.
> > This seem
control: tags -1 + pending
thanks
On Fri, Apr 24, 2020 at 05:46:06AM +0700, Judit Foglszinger wrote:
> Added a patch for clarifying removability from upload queue.
thank you very much! merged to master and updated .po files. (I vaguely plan an
upload before the end of the month.)
> Subject: [PAT
ssbaum
+ (c) 2015 - 2020 Hideki Yamane
+ (c) 2019 - 2020 Holger Levsen
This manual is free software; you may redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
diff --git a/source/index.rst b/source/index.rst
index a3d04b9..
On Mon, May 18, 2020 at 03:46:05PM +0200, Raphael Hertzog wrote:
> > I'd appreciate a quick review and possible corrections from you!
> Fine for me.
:) thanks!
--
cheers,
Holger
---
holger@(debia
hi,
I'm not fully sure if people really intend to change the 1.0 format, but if so,
I'm against it. If you do it, please call it 1.1 or whatever, but please don't
change 1.0, too many tools rely on it's decade old behavior.
Besides that it's also my opinion that we should get rid off native packa
On Tue, Jun 30, 2020 at 07:07:50PM +0200, Michael Biebl wrote:
> It's my understanding, that there is no clear consensus what should
> happen on package purge. Some packages do manually remove system users
> and go to some length to find files/directories owned by a system
> user/group and remove t
On Mon, Nov 09, 2020 at 12:12:18PM +0100, Mattia Rizzolo wrote:
> On Sat, Nov 07, 2020 at 01:01:28PM -0700, Sean Whitton wrote:
> > diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
> > index 0d7a3e9..a21a510 100644
> > --- a/policy/ch-controlfields.rst
> > +++ b/policy/ch-cont
On Mon, Nov 16, 2020 at 04:02:54AM -0800, Vagrant Cascadian wrote:
> While a consistent time was returned, depending on the timezone
> the package was built in can cause the date to vary:
> diff --git a/Makefile b/Makefile
> -DATE := $(shell date -d '@$(TIMESTAMP)' +'%Y-%m-%d')
> +DATE :=
mostly only
the last year as that might be used to calculate when a project becomes
public domain after the dead of an author.
So if I have contributed to something in 2018 and 2020 I find it ok to claim
'Copyright 2018-2020 Holger Levsen'. (Also because I might not have commited
something
On Tue, Dec 01, 2020 at 02:03:59PM -0500, Sam Hartman wrote:
> My rationale is that debian/copyright is a summary, it's not the license
> text in the files.
> I absolutely agree we shouldn't go change people's actual copyright
> notices in the files.
that. and what Bill said.
> As a copyright hol
Hi Russ,
On Thu, Apr 01, 2021 at 06:17:59PM -0700, Russ Allbery wrote:
> Here is an updated diff that documents the most well-understood version
> conventions in the Debian archive. More could certainly be added; this is
> just a first start that addresses this specific bug.
thank you for this,
On Fri, Apr 02, 2021 at 10:26:47AM -0700, Russ Allbery wrote:
> I'll therefore propose that we move the discussion of whether to give
> stronger advice on when to use native packages to a separate bug. Once
> this is merged, there will be some text in Policy defining native
> packages, so it will
On Fri, Jun 18, 2021 at 04:56:25PM -0400, Boyuan Yang wrote:
> According to
> https://lists.debian.org/debian-devel-announce/2021/06/msg2.html ,
> Debian's presence on Freenode has ceased. However,
> https://www.debian.org/doc/manuals/developers-reference/resources.html#irc-channels
> still men
Hi Marco,
On Mon, Aug 30, 2021 at 09:48:50PM -0500, Marco Villegas wrote:
> It seems like the mentioned link[1] is not working anymore, and looking
> around a bit it seems to be at [2] now instead.
agreed.
> I was thinking about the right place to add the link to.
> Even if there are some sectio
On Fri, Oct 29, 2021 at 10:51:44AM +0100, Simon McVittie wrote:
> Here are some updated patches for Policy, incorporating this requirement.
thanks for your work on this, Simon.
> I have not attempted to incorporate the corner case involving
> build-profiles. I think if we were going to do that,
hi,
(leaving full context for debian-policy@l.d.o)
On Sat, Nov 13, 2021 at 06:56:24AM +0100, Petter Reinholdtsen wrote:
> Package: dpkg-dev
> Version: 1.20.9
>
> Dear dpkg-dev developers,
>
> One feature that is deeply missed, and which disappered when we moved to
> source only uploads, is the
On Wed, Nov 17, 2021 at 03:11:55PM +0100, Johannes Schauer Marin Rodrigues
wrote:
> > This footnote might not be the best place to document the precise behaviour
> > of autobuilders (which currently is outside the scope of policy). On the
> > other hand, having a fully specified build process coul
On Sun, Dec 12, 2021 at 06:47:21PM +0100, Mattia Rizzolo wrote:
> On Sun, Oct 31, 2021 at 11:18:35AM +0100, Mattia Rizzolo wrote:
> > If I get no pushbacks I'll also propose some text later on when I'm
> > freer (unless somebody beats me to it!).
>
> I'm hereby seeking seconds (or, well, suggestio
control: tags -1 + pending
thanks
Hi Philippe,
On Fri, Feb 11, 2022 at 11:01:29PM +0100, Philippe SWARTVAGHER wrote:
> (first bug report and patch to Debian here ! :) )
whhooo, congrats! And thank you very much!
> I attach a patch fixing some minor formatting issues in the French
> transla
Hi Marc,
On Fri, Mar 11, 2022 at 08:15:37PM +0100, Marc Haber wrote:
> This is my patch.
I like your patch. :) I just have one comment:
> +``Dynamic local`` allocated ids should by default be arranged in some
> +sensible order, but the behavior should be configurable.
unpredictable or non-deter
On Sat, Mar 12, 2022 at 01:21:24PM +0100, Marc Haber wrote:
> > unpredictable or non-deterministic allocation of such ids is a cause of non-
> > reproducibiliy for Debian images and installations, so us reproducible folks
> > would like to see "sensible" to be expanded to take reproducible builds i
On Wed, Mar 02, 2022 at 02:21:20PM +0100, kaliko wrote:
> On Sat, 15 Jun 2019 16:26:33 +0000 Holger Levsen
> wrote:
> > […]
> > and then for bullseye we should use distro-info(-data). (wondering how
> > to do this sensibly at run time and not at build time...)
> What is
On Mon, May 09, 2022 at 07:16:59PM -0700, Jonathan Nieder wrote:
> > Even if that consensus does not exist, there is probably consensus
> > that native packages are a poor match for large packages (because of
> > the inefficiency of making small updates to the packaging of native
> > packages),
> D
On Mon, Jun 20, 2022 at 07:43:45PM +0700, Teukumif tahulziran wrote:
> > There is already a section about reproducibility in the debian-policy,
> > but it only mentions the binary packages. It might be a good idea to
> > add a new requirement that repeatedly building the source package in
> > the s
control: tags -1 wishlist
thanks
On Thu, Jul 21, 2022 at 10:44:26AM +0200, Marc Haber wrote:
> for a few years now, the Debian archive wants to see source-only
> uploads. This is not documented in the Developer's Reference and also
> now in the New Maintainer's Guide. It should be there.
I agree
On Mon, Sep 19, 2022 at 09:29:36PM -0700, Russ Allbery wrote:
> I'm fine with this change, but as Sam points out, the deeper point here is
> that Policy doesn't apply to udebs. This is the whole point of udebs.
When you say it like this, it sounds to strong to me, if it were written in
-policy.
On Tue, Sep 20, 2022 at 06:39:11PM -0700, Russ Allbery wrote:
> Here is proposed wording that I think is ready for seconds.
>
> From: Russ Allbery
> Date: Tue, 20 Sep 2022 18:35:55 -0700
> Subject: [PATCH] Clarify udeb-only source packages are out of scope
>
> Note that source packages that only
On Tue, Sep 20, 2022 at 07:17:17PM -0700, Russ Allbery wrote:
> +The autobuilders for the Debian backports suite do not perform this
> +transformation and instead use the full alternatives list to resolve
> +dependencies.
this sounds like they install all build depends, incl alternative ones?!
is
On Fri, Sep 23, 2022 at 04:17:04PM +0100, Simon McVittie wrote:
> On Thu, 22 Sep 2022 at 19:11:38 -0700, Russ Allbery wrote:
> > I also reworded the paragraph about backports to hopefully address
> > Holger's reading. It's just trying to say that backports uses aptitude in
> > the normal way and d
On Mon, Sep 26, 2022 at 10:15:07AM +0200, Wouter Verhelst wrote:
> Experimental is different because it is an incomplete distribution,
> which needs to default to using packages from unstable except if
> build-depends explicitly lists versions that are only available in
> experimental.
[...]
Thank
hi Simon,
On Sun, Nov 13, 2022 at 03:49:13PM +, Simon McVittie wrote:
> I've had the attached sitting in my outbox for a while and I think it's at
> least a good start towards what Marc requests?
yes, thanks a lot!
> I have deliberately not documented the precise meaning of needing to
> incl
hi,
do you plan to release a new version of debian-policy before the freeze
in January?
I'm wondering whether I should start polishing uploads now or better
wait.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35
On Thu, Dec 15, 2022 at 01:25:10PM -0700, Sean Whitton wrote:
> Thanks Holger for pointing this out. I'll cut a release today or
> tomorrow.
\o/ & thank you!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026
On Thu, Jan 19, 2023 at 11:28:41AM -0600, Gunnar Wolf wrote:
> diff --git a/policy/ch-archive.rst b/policy/ch-archive.rst
> index ab04261..15b9343 100644
> --- a/policy/ch-archive.rst
> +++ b/policy/ch-archive.rst
> @@ -24,11 +24,11 @@ The aims of this are:
>
> The *main* archive area forms the
hi,
the bug got closed, but not in vain:
commit 61a395888206b5ef45beb3d47d5ae81471f85c78
Author: Holger Levsen
Date: Mon Feb 6 20:11:22 2023 +0100
tools: add a pointer to https://wiki.debian.org/debian/watch
when watch files are mentioned. Thanks to #660193
Signed-off-by
control: tags -1 +moreinfo
thanks
hi,
I don't think there has been consent on the issue, thus I'm tagging it
moreinfo.
I'm also wondering whether to mark this bug as wontfix (until there is
consent) or to reassign to debian-policy or simply to close it.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁
hi,
annex.debconf.org is gone, the slides are at
https://salsa.debian.org/debconf-team/public/share/debconf16/-/raw/master/slides/13-we-need-you-to-release-debian.pdf
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B0
control: tags -1 +moreinfo
control: affects -1 debtags
thanks
hi,
https://lists.debian.org/msgid-search/20221019132043.d4c4liyt6s6qe...@enricozini.org
and
https://lists.debian.org/msgid-search/bb7064071ebd838a9e045a1916bba49a9b960d80.ca...@debian.org
indicate that debtags.debian.org might be shut
On Wed, Feb 08, 2023 at 08:39:36AM -0700, Sam Hartman wrote:
> >>>>> "Holger" == Holger Levsen writes:
> Holger> I don't think there has been consent on the issue, thus I'm
> Holger> tagging it moreinfo.
> My reading of the TC and d
hi,
btw, as pointed out on irc: I ment consensus, not consent. :)
On Wed, Feb 08, 2023 at 10:36:02AM -0500, Marvin Renich wrote:
> > I don't think there has been consent on the issue, thus I'm tagging it
> > moreinfo.
> >
> > I'm also wondering whether to mark this bug as wontfix (until there is
retitle -1 turn #904558 into advice - how postinst should deal with failures
thanks
On Wed, Feb 08, 2023 at 09:26:58AM -0700, Sam Hartman wrote:
> The TC bug is 904558.
thank you very much for this pointer, that's a pretty good discussion,
which resulted in
-
So, the
On Wed, Feb 08, 2023 at 06:13:32PM +0100, Bill Allombert wrote:
> > not only based on that, but way more importantly that this would change
> > *years* of existing practice.
> Could you clarify which 'existing practices' ?
how Debian packages behaved in the last decades.
--
cheers,
Hol
On Wed, Feb 08, 2023 at 06:39:08PM +0100, Bill Allombert wrote:
> Note that the TC declining to rule on an issue does not override the policy
> group right to make
> a determination on that issue. So we are back to the situation before the
> referral to the TC.
do you think #801065 should be as
hi,
some updates on this bug:
- the issue seems to have nothing to do with the single page html format,
it's also present in the multi page html version, and the cause seems
to be https://github.com/sphinx-doc/sphinx/issues/6614
- the issue is visible annoying in the generated package descrip
control: tags -1 +moreinfo
thanks
hi,
(originally sent to the wrong (but archived) bug number...)
we're not shipping the manual in .info format, so I'm wondering whether this
bug should simply be closed, or why not?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-bui
hi,
actually I found the info version now, but it seems complete to me:
$ sudo apt install info
$ info developers-reference
# voila. /usr/share/info/developers-reference.info.gz is where the file is.
So I'm still inclined to close this bug.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holge
On Sun, Feb 12, 2023 at 06:56:28AM +0900, Osamu Aoki wrote:
> Yes, info version is included and it contains appendix, too.
> So closing this bug is right action.
thanks for confirming!
> Thanks for your effort.
:) thanks.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproduci
On Mon, Feb 20, 2023 at 01:59:21PM +, Jelmer Vernooij wrote:
> I've created a PR for devref -
> https://salsa.debian.org/debian/developers-reference/-/merge_requests/41
fwiw, merged into developers-reference 12.16 in sid.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reprod
On Sun, Feb 26, 2023 at 10:25:21AM -0700, Sean Whitton wrote:
> Why don't we just fix all those packacges, instead of changing any
> documents? Is there anyone who actually wants to introduce new packages
> not using git? I'm not so sure.
mostly agreed, i'm just sure there will be very few peopl
hi,
someone on irc wondered about icons and Debian packages so I noticed
https://www.debian.org/doc/packaging-manuals/menu-policy/
prominently linked from https://www.debian.org/doc/devel-manuals#policy
But then I though the menu system has been deprecated as eg noted in
#975631:
On Tue, Nov 24,
severity 606790 important
thanks
Hi Lucas,
On Mittwoch, 15. Dezember 2010, Christian Welzel wrote:
> Am 11.12.2010 18:50, schrieb Lucas Nussbaum:
> > While testing the installation of all packages in squeeze, I ran
> > into the following problem:
>
> This doesn't seem to be a problem of typo3-dum
reopen 618885
reassign 618885 tech-ctte
thanks
Hi,
please read #618885 which is about whether sasl2-bin can kept files on the
system after purging it.
Policy 6.8 says that files must be removed on purge, Roberto says sasl2-bin is
an exception. I disagree.
There are some packages in the archi
Hi Steve,
On Samstag, 30. April 2011, Steve Langasek wrote:
> 10.7.3: If the existence of a [configuration] file is required for the
> package to be sensibly configured it is the responsibility of the package
> maintainer to provide maintainer scripts which correctly create, update and
> maintain
Hi Neil,
applause, thanks & good luck to making grip official!
just one tiny comment:
On Sonntag, 7. August 2011, Neil Williams wrote:
> 9.8 Keyboard configuration - Note that many Emdebian devices will not
> have a keyboard of any kind (except on-screen after installation), so
> packages should
Hi,
any news on how to solve this issue?
Anything I could do?
cheers,
Holger
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201201141258.05187.hol...@la
Hi Bertrand,
On Sonntag, 20. Mai 2012, Bertrand Marc wrote:
> I am trying to make up my mind about using or not dpkg-statoverride. The
> most useful info I found is in bug #568313 [1].
Indeed, thats a good discussion, which actually changed my mind a bit :)
> They seem to conclude 2
> things app
Hi,
this has also already been documented as best practice (to say at least) in
https://wiki.debian.org/buildd which says: "most buildds will have no network
access available. Your package build+test process must not attempt to use the
network or assume that any network interface is available."
package: debian-policy
affects: simutrans-pak128.britain
x-debbugs-cc: ans...@debian.org, reproducible-bui...@lists.alioth.debian.org
Hi,
I've just noticed and filed "#780724: simutrans-pak128.britain ftbfs if PATH
does not contain /usr/games" which made me notice that PATH is not specified
in
Hi,
#780724 is the bug about simutrans-pak128.britain failing to build if PATH
does not contain /usr/games,
#780725 is the bug about debian-policy not defining PATH.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
Mittwoch, 18. März 2015, Bill Allombert wrote:
> On Wed, Mar 18, 2015 at 12:48:13PM +0100, Holger Levsen wrote:
> > package: debian-policy
> > affects: simutrans-pak128.britain
> > x-debbugs-cc: ans...@debian.org,
> > reproducible-bui...@lists.alioth.debian.org
> >
>
block 687900 by 621050
block 687900 by 684672
block 687900 by 650974
block 687900 by 636383
thanks
Hi,
filing these as blockers for #687900 so that there is one place to track all
the bits to be documented.
cheers,
Holger
signature.asc
Description: This is a digitally signed message
This is an automated email from the git hooks/post-receive script.
holger pushed a change to branch master
in repository developers-reference.
from 5393ab0 changed »Paketverfolgung« to »Paketverfolgungssystem«
new 9bb10f0 rephrase to be less inviting to send private mails
(ins
This is an automated email from the git hooks/post-receive script.
holger pushed a commit to branch master
in repository developers-reference.
commit 9bb10f08a1dae9791413931420bf78ffcd916734
Author: Holger Levsen
Date: Tue May 10 17:06:26 2016 +0200
rephrase to be less inviting to send
Hi Marc, hi Andreas,
On Freitag, 27. Februar 2009, Steve Langasek wrote:
> Also, I haven't seen the exim4 maintainers comment on this proposal until
> now. Obviously we would want to get that package to Provide: default-mta
> before filing bugs on other packages.
Could you please take a look at
Hi,
On Sonntag, 1. März 2009, Carsten Hey wrote:
> In my opinion it is a way better practise to first update the policy and
> then adapt n packages instead of first change them in a way which is
> possibly against the policy and expect the policy to be updated
> accordingly.
There is nothing _aga
Hi,
On Sonntag, 1. März 2009, Carsten Hey wrote:
> And using stable and testing repositories together, e.g. during
> dist-upgrades, will be forbidden? If not, it can't be avoided.
So what? It's not supported and the user has to fix manually. No big deal.
regards,
Holger
signature.as
Hi,
sadly this didden happen in 2003-2009, but I'd like this to become a reality
for our next release sometime in 2010 or hopefully not 2011 ;-)
Any takers? (To propose this as a release goal & bringing this into policy.)
Sadly I'm too busy for this, but I thought I'd at least remark it.
rega
Hi,
On Donnerstag, 19. März 2009, Russ Allbery wrote:
> > Package maintainer scripts may prompt the user if necessary.
> > Prompting must be done by communicating through a program, such
> > as debconf, which conforms to the Debian Configuration
> > Management Speci
On Freitag, 20. März 2009, Russ Allbery wrote:
> > Here's an updated patch to apply the following wording:
> Seconded.
me too.
(not quoted as this aint a GR. :-)
signature.asc
Description: This is a digitally signed message part.
Hi,
while testing the archive with piuparts I found a failure reported by
piuparts, that after purge /var/games existed on the system while it wasnt
there before installing+purging the package.
See http://piuparts.debian.org/squeeze/fail/slashem-common_0.0.7E7F3-1.3.log
(at the end..)
http:/
Hi Russ,
On Montag, 6. April 2009, Russ Allbery wrote:
> We'd then have a similar problem with any other /var directory that holds
> files mostly created at runtime and only deleted on purge, such as
> /var/log, except that the rest are always in existence.
According to the FHS the other 4 direct
Hi,
On Dienstag, 7. April 2009, Paul Wise wrote:
> A single rmdir in every game using /var/games isn't that hard,
> especially since they have to remove the files from there.
I agree and plan to file RC bugs on this.
(There have been 24781 binary packages been successfully tested in sid and
sq
Hi,
On Mittwoch, 8. April 2009, Paul Wise wrote:
> How about this:
>
> Game a gets installed and ships /var/games
> Game b gets installed and ships /var/games
> Game a gets purged and removes /var/games
> User starts game b and gets a high score
> Game b tries to save the high score but fails beca
Hi,
On Mittwoch, 8. April 2009, Adeodato Simó wrote:
> Additionally, what happens if package A and B both ship an empty
> /var/games (they both write their score files directly there, rather
> than a subdirectory), get both installed, then B gets purged and its
> postinst removes /var/games, and t
Hi Bill,
On Mittwoch, 8. April 2009, Bill Allombert wrote:
> Unless policy is changed to make clear that /var/games can be removed
> at any time, and thus that package cannot just ship /var/games in the
> deb and expect it to be available when running the postinst, or at any
> latter time, I have
Hi,
On Montag, 6. April 2009, Russ Allbery wrote:
> I don't see much real benefit in going out of our way to remove /var/games
> and it looks like it would be a bit annoying (at the least, require adding
> purge code to all games that put files in /var/games that would usually
> never be triggered
package: debian-policy
x-debbugs-cc: debian...@lists.debian.org, debian-policy@lists.debian.org
On Donnerstag, 9. April 2009, Holger Levsen wrote:
> On Montag, 6. April 2009, Russ Allbery wrote:
> > I don't see much real benefit in going out of our way to remove
> > /var/gam
package: debian-policy
x-debbugs-cc: debian...@lists.debian.org, debian-policy@lists.debian.org
sorry for post to the wrong address...
On Donnerstag, 9. April 2009, Holger Levsen wrote:
> On Montag, 6. April 2009, Russ Allbery wrote:
> > I don't see much real benefit in going out
Hi,
it seems we missed on legacy advice in the fix #206684:
See http://www.debian.org/doc/debian-policy/ch-binary.html#s-maintscripts and
there the last but one paragraph of 3.9.1, which #206684 does not suggest to
change:
--quote-
If a package has a vitally important piece of information
Hi Russ,
On Montag, 4. Mai 2009, Russ Allbery wrote:
> How about:
> it should display this in the config or postinst script and prompt
> the user for acknowledgement. See .
Great!
> We don't require that the program use debconf, only that it use
> something that complies with the Debian
reassign 528021 debian-policy
severity 528021 important
thanks
Hi Norbert,
On Sonntag, 10. Mai 2009, Norbert Preining wrote:
> The problem is that it seems you don't have an idea about what ls-R files
> are and how they are created.
I wouldnt call it _the_ problem here, but it surely has been p
Hi Bill,
On Montag, 11. Mai 2009, Bill Allombert wrote:
> But policy allows creating directory like /usr/local/share/texmf in the
> postinst.
[...]
> It seems to me that mktexlsr could honour policy if
> /usr/local/share/texmf/ls-R was only created when it would be not empty
> (i.e. the user insta
Hi,
On Sonntag, 9. August 2009, Manoj Srivastava wrote:
> The link to the wiki page was missing
> http://wiki.debian.org/AutomaticDebugPackages
this link was also missing in #508585.
regards,
Holger
signature.asc
Description: This is a digitally signed message part.
[resent, added cc: to debian-policy@, feedback welcome on how piuparts should
treat certain left over files after purging a package..]
Hi Helge,
thank you for bringing up this issue here.
On Mittwoch, 25. November 2009, Helge Kreutzmann wrote:
> Package purging left files on system:
> /var/ca
Hi Guillem, Collin,
On Sonntag, 29. November 2009, Colin Watson wrote:
> > Ignoring /var/cache/man/ seems the most reasonable course of action to
> > me. The man-db package is the one handling those databases, it just
> > seems logical to me that it should be the one in charge of removing it
> > w
package: man-db
x-debbugs-cc: debian...@lists.debian.org>, debian-policy@lists.debian.org
On Sonntag, 29. November 2009, Colin Watson wrote:
> It makes sense for mandb to observe that a hierarchy of manual pages has
> gone away entirely (e.g. no more /usr/share/man/pt) and remove the
> correspond
Hi,
On Montag, 4. Januar 2010, Russ Allbery wrote:
> >> and what the requirements of a package are around preserving or
> >> removing its data other than log files and configuration files on
> >> purge? If so, that would be the relevant place to talk about whether
> >> or not directories like /va
Hi,
On Montag, 4. Januar 2010, Russ Allbery wrote:
> There are several arguments that say that such data shouldn't be deleted
> on purge. I don't know how persuasive they are.
I'll answer them in reverse order :-)
> * Whether it makes sense given Debian semantics or not, users just don't
> ex
101 - 200 of 250 matches
Mail list logo
