* Holger Levsen , 2014-11-18, 13:12:
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.
I don't believe this is currently the case, but I'd love to proven
wrong. Of course,
On Sat, Nov 15, 2014 at 12:19:32PM +0100, David Bremner wrote:
> I have only tested the first one. In all cases build-depends may need
> adjusting. I also noticed that the same hacking out of TeX stuff I did
> to README.org is needed for Process.org.
Thank for the tip, this resolve the remaining
Processing commands for cont...@bugs.debian.org:
> retitle 666726 debian-policy: Clarify if empty control fields are allowed or
> not
Bug #666726 [debian-policy] debian-policy: Clarify if empty control fields are
ollowed or not
Changed Bug title to 'debian-policy: Clarify if empty control fields
On 18/11/2014 17:39, Matthias Urlichs wrote:
Text emails, please.
I alway forget that in my company my mailer is configured for html as
outlook discussion cut is absurd...
You _can_ do
ExecStart=sudo -u $USER_MINIDLNA -g GROUP_MINIDLNA /usr/sbin/minidlnad -S
but that's not the o
Hi,
[ redirecting to debian-devel, as -policy isn't the correct list for this IMHO ]
Eric Valette:
>
Text emails, please.
> I've been fighting with some script conversion to systemd and I think
> a reasonnably complex exemple should be of great help. I've been
What's "reasonably compl
Hi,
Santiago Vila:
> As it has been pointed out by others, whenever we have a set of
> mutually conflicting packages performing the same task, the package
> having optional priority is the one that we recommend among them.
>
> It is a way to tell the user "in doubt, use this one".
>
… which also
I've been fighting with some script conversion to systemd and I
think a reasonnably complex exemple should be of great help. I've
been trying to convert minidlna sysv init file to systemd, managed
to have a working unit file but failed to split the configuration
mimicing
On Tue, 18 Nov 2014, Andrey Rahmatullin wrote:
> On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote:
> > I guess that it is implicit from the defintion of contrib that follows in
> > 2.2.2:
> >
> > The contrib archive area contains supplemental packages intended to work
> > with
>
On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote:
> I guess that it is implicit from the defintion of contrib that follows in
> 2.2.2:
>
> The contrib archive area contains supplemental packages intended to work
> with
> the Debian distribution, but which require software outsi
Le Tue, Nov 18, 2014 at 03:03:07PM +0600, Andrey Rahmatullin a écrit :
>
> 2.2.1 says "the packages in main
>
>must not require or recommend a package outside of main for compilation or
> execution (thus, the package must not declare a "Pre-Depends", "Depends",
> "Recommends", "Build-Depends"
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."
On Tue, 18 Nov 2014, Charles Plessy wrote:
> Le Mon, Nov 17, 2014 at 03:55:26PM +0100, Santiago Vila a écrit :
> Hi Santiago,
>
> practically speaking, how do you or others use the Optional priority
> to check that a package is not directly or transitively conflicting
> with another package ? Fi
Package: debian-policy
Severity: wishlist
2.2.1 says "the packages in main
must not require or recommend a package outside of main for compilation or
execution (thus, the package must not declare a "Pre-Depends", "Depends",
"Recommends", "Build-Depends", or "Build-Depends-Indep" relationship o
13 matches
Mail list logo
