test team these days, it'd be better to keep the
autopkgtest-devel list in the loop (I'm Cc:-ing it now). Autopkgtesters:
you might want to subscribe to this policy bug report and keep an eye on
this.
> Thanks for moving forward with this,
Same :)
Cheers.
--
Stefano Zacchiroli . . . . . . .
ANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From 8440fe8b2bef5f99bddf3deb141a8c4b4b0354f9 Mon Sep 17 00:00:00 2001
From: Stefano Zacchiroli
Date: Sun, 5 Oct 2014 23:41:40 +0200
Subject: [PATCH 1/2] autopk
Package: debian-policy
Severity: minor
File: /usr/share/doc/debian-policy/copyright-format-1.0.txt.gz
Heya,
in the short name license tables, shipped as part of the machine readable
copyright format specification and available online at
https://www.debian.org/doc/packaging-manuals/copyright-
nges (lintian cleanness, markup,
etc.), I'm struggling to find time to implement them, but they're on my
TODO list. I'll keep you posted.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . .
On Sun, Oct 05, 2014 at 11:52:14PM +0200, Stefano Zacchiroli wrote:
> It took me a bit longer than that (sorry about that), but you can now
> find attached to this mail my first attempt at adding the autopkgtest
> spec to the Debian Policy package.
Friendly ping to the -policy folks. Had
titled, whatever) please let me know.
Before preparing an updated patch, I'll wait for feedback from -policy
people, to avoid spamming the list(s) with too many versions of the
patch.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférenc
On Thu, Jul 31, 2014 at 01:53:50PM +0200, Stefano Zacchiroli wrote:
> It looks like we have found some middle ground and can proceed.
[...]
> I'll be intermittently on VAC/work in the next few weeks, but I'll
> complete this during DebConf14 the latest.
It took me a bit long
current status of
dep-8 into debian-policy (and send it as a patch to -policy); 2/ mark
dep-8 as accepted, freeze it, and point to the -policy repo for further
updates.
I'll be intermittently on VAC/work in the next few weeks, but I'll
complete this during DebConf14 the latest.
On Mon, Jul 28, 2014 at 06:32:35PM +0200, Martin Pitt wrote:
> Stefano Zacchiroli [2014-07-25 12:23 +0200]:
> > Antonio, would the approach/experiment proposed by Russ be good enough
> > to address your concerns? Personally, I'll be more than happy in moving
> > the auto
s will happen in the new sub-policy.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology cl
ryone --- DEP5 has told
me that that is not a good idea. It should be a place somehow
controlled, associated to a list where interested stakeholders can
discuss perspective changes before acting.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de co
lled autopkgtest, and coordinating changes in
a more neutral place would be preferable, IMO.
What do other autopkgtest-ers think of this idea?
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
s would be appropriate for those
packages.
FWIW, to increase awareness of this field, I've now reported #742787
against lintian, patches welcome!
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . .
of non-free-ness,
which as discussed elsewhere in this thread would be rather cool.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader . . @zack on identi.c
ave remained
around). None of them is M-A: same, so the above alleged APT issue is
only theoretical at this point. But it might become real with the
increasing popularity of multiarch-ed packages in the Debian archive.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . .
the above is a typo of mine :-). debian-*policy*@lists.d.o is
in fact what I wanted to propose. Sorry for the confusion.
Cheers.
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Debian Project
s at my discretion, but most likely in consultation
with current (co-)editors.
… and while I'm here, thanks to all this list participants for their
work on the Debian Policy: it is the cornerstone of Debian quality, and
that wouldn't be possible without the work you'
rently; and that was my personal
opinion: I think the dev-ref maints have the final say here, possibly
after having consulted people more broadly as they did with DEP-1).
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences .. http://upsilon.c
packages will adopt it for Squeeze, increasing the share of Debian
packages with machine parseable debian/copyright files...
Thanks for considering,
Cheers.
[1] assuming the other "couple of issues" mentioned by Lars as coming
from Steve are a subset of the language improvemen
trying to rebuild RT delegation history), but
I do hope we can solve this in ways where the time of everybody is
better spent than that.
/me takes off the formalities hat
Cheers.
[1] I'm adding both of them to Cc:, in case I've misunderstood them
--
Stefano Zacchiroli -o- PhD in Comput
Package: developers-reference
Version: 3.4.4
Severity: normal
There is a recurrent unpleasant topic on various Debian lists. From time to
time, we read complaints that specific maintainers are not fit to be Debian
Developers (anymore) because, allegedly, they are not doing job at maintaining
one o
ough consensus, we should be ready to accept the
result of that.
What else do you think we can learn from this exchange?
Please, everybody, let's try to keep active the development around
devref, as we really need it!
Thanks you all for your work.
--
Stefano Zacchiroli -o- PhD in Comput
ared
feeling among Debian Developer, although I've no data that back that.)
As the release process is shepherded by the release team, collaborating
with the release team and supporting their choices is a way to support
the release process.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer
this argument seems
to be orthogonal to my proposal, in the following sense. *If* ftpmaster
disallow too small packages, you need a technical way to coalesce
several small upstream tarballs into a single Debian source
package. That is something which you can do with source formats 3.0, so
you would
Package: debian-policy
Version: 3.9.1.0
Severity: wishlist
tar-in-tar source packages, i.e. Debian source packages which contains upstream
sources in compressed form and uncompress them on the fly during the build
process, are a bit of a PITA. They are particularly so for tools who want to do
sour
ield as well.
So be it.
I still don't get how the versioned Format URL will look like once DEP5
will be shipped by debian-policy though. Would it use the Vcs-Browser of
the debian-policy package or ...? Just curious.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Pa
t the
meeting. So, if you are interested, please contact me to volunteer. The
sooner, the better.
Cheers
PS full quote below of the initial mail, to the benefit of -project
readers
On Sun, Dec 12, 2010 at 04:43:01PM +0100, Stefano Zacchiroli wrote:
> Dear all,
> Vicent Untz has co
discussion about
the idea, we can have it separately and, more importantly, once we
have a clearer technical presentation of the idea. What we need here
are people interested in the topic who volunteer some time to
represent Debian.
- Forwarded message from Vincent Untz -
Fro
t Teams/DPL, i.e. "no vanity
certificates, please" as it takes anyhow some time to prepare them
TIA,
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande
of checksum used carved in stone.
Thanks for considering,
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoi
://lists.debian.org/debian-policy/2009/12/msg00051.html
Cheers.
- Forwarded message from Stefano Zacchiroli -
Dear policy list,
during various NMU, it happened to me that the maintainer of the NMUed
package reply with "thanks a lot, next time please also commit your
changes to ou
conditional wrt the existence of such info.
> Yes, please. Otherwise I'll lose it.
Will do forwarding the first post of this thread in a minute.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>-
is
also coherent with what we suggest to do for dpatch/quilt: not adding
the rules in all README.source, but factorize them out and point to
that.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http:
as a concept,
otherwise the reader will likely miss the point of this change.
> Have a nice day,
Thanks for the patch!
If the policy maintainers want a bug report to keep track of this,
please say so.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{
2009 11:56:19 +0900
From: Charles Plessy
To: Stefano Zacchiroli
Cc: 545...@bugs.debian.org
Subject: Re: [Debian-med-packaging] Bug#545515: mgltools-gle: diff for NMU
version 1.5.4.cvs.20090603-1.1
Le Mon, Dec 21, 2009 at 04:41:11PM +0100, Stefano Zacchiroli a écrit :
> On Mon, Dec
ich
one we can't.
Now that I think of it, probably a per-package data dir would help, but
that can be a tad more tricky due to single-instance of
multiple-instance nature of the webapp in question ...
> Of course, if the use of /usr/share/www/ is optional,
> everybody wins.
It is fo
plications are deployed on the filesystem. I found such
a goal worthwhile by itself and orthogonal to the other concern you
raise.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro
haven't
heard significant voices against, am I wrong? I'd personally proceed as
follow: write a draft document (even a very brief one!) which summarizes
the proposal so that people do not need to dig into the thread to follow
the evolution. Once we have it, re-post it to the relevant lists
olicy
If it were me to try to achieve this, I would go for a DEP to keep track
of consensus, ... but no, I'm not willing to drive this, at least not
now :-)
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<&
document in README.source.
Cheers
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...
e the two options which were discussed here
Andreas.
[1] http://blends.debian.net/rest-test/tasks/works#geordi
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e fixed by the individual packages (or pre-processed into some other
> character).
Full ACK.
FWIW, note that with the fix induced by the first of Bill reports, I
consider garlic-doc looking right. As it is not a Markdown list, it is
rendered as ordinary verbatim text.
Cheers.
--
Stefano Za
mware-loaders does indeed look better.
Thanks,
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sem
md64)
rendered as Markdown using render-dctrl is now available at
http://upsilon.cc/~zack/stuff/longdesc-mdwn/ . It is weekly
re-generated. Anybody who spots "absurd" long descriptions there,
please shout.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ.
Package: debian-policy
Version: 3.8.1.0
Severity: wishlist
[ submitting bug report as requested at
http://lists.debian.org/debian-policy/2009/04/msg00155.html ]
Andreas Tille, has recently (re-)raised the issue of consistent
formatting of lists in long descriptions [1,2].
[1] http://lists.deb
7;s definitely broken and should be fixed anyway.
Full ACK, so not a blocking problem.
>> If not, can you please submit it with references to the thread?
>> ... or else shout and I'll do that.
> Please go for it - as I said my spare time might be restricted.
> I'm no
[ Please Cc:-me on replies, I'm not subscribed to -policy.
Andreas: sorry for the Cc, but I've no idea if you follow -policy. ]
On Sun, Apr 26, 2009 at 08:53:51PM +0200, Stefano Zacchiroli wrote:
> Please find one attached as the script "render-dctrl". Sample usage:
Li
ebian.git;a=commit;h=b90ffafd6a1806ab7e3e7620d1675a53ae38e66e
PS mail like this one of mine should be better stored in the log of a
bug report against the policy, to keep track of the
status.
Andreas: do we have one already? If not, can you please
submit it with references to the thread?
On Wed, Apr 22, 2009 at 10:22:15AM -0500, Manoj Srivastava wrote:
> On Wed, Apr 22 2009, Stefano Zacchiroli wrote:
> > On Tue, Apr 21, 2009 at 11:36:31PM +0200, Vincent Danjean wrote:
> >> No. Adding blank lines before lists is also required.
> > ... so, agreed. The e
e on a single paragraphs, half are not.
> > Note that the only pre-processor needed seems to be the one which
> > separate paragraphs using the single dot we already use.
> No. Adding blank lines before lists is also required.
... so, agreed. The extra price to pay to use Markdown w
;thanks" to Andreas for digging into this discussion
:-) *If* we manage to have consensus on this, it will be mostly due
to him insisting on this topic!
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- htt
ementation
plan. Out of curiosity, would restructured text be immune to this
problem?
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne
On Sat, Oct 11, 2008 at 07:05:31PM +0200, Stefano Zacchiroli wrote:
> Interestingly enough, the Debian policy is ambiguous about what are
> the paragraph separators in debian/control. Section 5.1 first states
> that blank lines are separators (which is usually interpreted as &qu
hat looks like a major differences in the two positions
still.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas
can call
"uscan" with its parameters, but you cannot implement that API with
anything else. An API is something I expect to be able to implement
in different ways; get-orig-source enables individual DDs to do that.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ.
olution that will require
adding an "-include" to 15'000 thousands debian/rules; we will finish
doing that by Lenny+50, the earliest.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://ups
ncapsulation, in the sense that
you can use uscan to implement it, but you are not forced to. What is
the problem with that? It is like *the* point I'm missing in this
whole discussion.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,
question I have and that hasn't been addressed by the original
request is: what is the advantage to have BDF files in binary
packages? Comments and copyright notices don't look like a real
advantage to me.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ U
should be RC.
Then the override would be pointless to the end of letting RMs
*override* severities.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |.
ould also
enable to address needs such as the reported one: wishlist bug report,
marked with some RC-severity in the override.
I'm not claiming it would be a clean solution, I just got surprised
that the very same tool can address both needs.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer
in policy would be
helpful (note that at that point, whether spaces are accepted or not
will depend entirely on the RFC822 standard).
Cheers.
[1] here I'm implicitly assuming that RFC822 also describe mailbox
files, rather than only mail messages, but I haven't checked
that.
t;no architecture",
i.e. useless dependency
b) (polarity negative) hence empty arch list means "no excluded
architecture", i.e. always present dependency
We can start betting on this possibilities :-)
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science \ PostDo
Package: debian-policy
Version: 3.8.0.1
Severity: wishlist
Tags: patch
Section 7.1 of the policy includes a description of
architecture-specific dependencies, correctly adding the following
constraint:
> It is not permitted for some names to be prepended with exclamation
> marks while others aren
which should be improved rather than took as a proof of
concept that build-arch can't be detected that way. How many examples
are around there like yours? I think they should be fixed nevertheless,
and I don't even think there are many ...
Cheers.
--
Stefano Zacchiroli -*- PhD in Co
h python$*` ./configure
...
build-arch:
...
?
Cheers
--
Stefano Zacchiroli -*- PhD in Computer Science ... now what?
[EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48) Zack: e la demo dema ?/\All one has to do is hit the
(15:57:15
opriate element for this or where else
can be but a element, but something better then this should
be looked for.
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science ... now what?
[EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48) Zack: e la
sion example.
> + As another example, if the VCS being used is arch,
> + the corresponding field anme would be:
typo here
Thanks for taking care of this,
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science .
the various VCS.
Thanks for your feedback,
Cheers.
--
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48) Zack: e la demo dema ?/\All one has to do is hit the
(15:57:15) Bac: no, la demo sc
st specification mechanism in your
stanzas or you simplify it toward a minimum and describe a test-runner
script infrastructure. I don't see the advancates of any intermediate
approach.
Cheers.
--
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
[EMAIL PROTECTED],deb
cumentation
in one place. It's up to you, in a plural sense, to choose the right way
to reach this objective.
Thanks again.
Cheers.
--
Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it} - http://www.bononia.it/zack/
" I kno
how it goes from there. Any objections?
You mean "may" add the symlink, right? If so it will be a good solution
also in my opinion. But I think that the placement of documentation in
/usr/share/doc/ should be _mandated_ by the policy so that bugs
can be reported against packages having docume
nks, I'm interested.
Anyway that consensus isn't actually reflected in the current policy, is
it?
Cheers.
--
Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it} - http://www.bononia.it/zack/
" I know you believe you under
Hi all,
I've read the bug report and I'm interested to know if this bug is
being considered by the policy people or not. I've also read a bit of
the debian-policy archives but it seems that the issue hasn't been
resolved.
TIA.
Cheers.
--
Stefano Zacchiroli -- Master
lot o undocumented man pages exists only because the
maintainer has forgetten them or something like that, having bugs in the
BTS should increase the number of available manpages and improbe the
debian quality even more.
Cheers.
--
Stefano Zacchiroli - undergraduate student of CS @ Univ. Bologna,
74 matches
Mail list logo
