On Tue, Apr 19, 2011 at 09:43:45PM -0400, Yaroslav Halchenko wrote:
On Thu, 07 Apr 2011, Jan Hauke Rahm wrote:
No. Simply answer the question: Is this VCS used by derived distros,
too? If not, it's Debian only. Two examples: The git repository for
apt-mirror is used only for Debian
On Thu, 07 Apr 2011, Jan Hauke Rahm wrote:
No. Simply answer the question: Is this VCS used by derived distros,
too? If not, it's Debian only. Two examples: The git repository for
apt-mirror is used only for Debian (there's only the master branch). The
git repository for vlc is used for
On Sat, Apr 09, 2011 at 11:57:58AM +0900, Charles Plessy wrote:
YAML is also used in other Debian processes, like for instance some reports
generated by the FTP team. All in all, I do not have the impression that the
use of YAML would cause difficulties to Debian packages maintainers.
The
Le Thu, Apr 07, 2011 at 03:08:33PM +0200, Bernd Zeimetz a écrit :
On 04/07/2011 10:11 AM, Charles Plessy wrote:
http://wiki.debian.org/UpstreamMetadata
The key concept is to store ‘Field: value’ data in a file called
debian/upstream-metadata.yaml, and to access it from the VCS where
that needs to be put into the Sources file.
+1
And I'm not really keen on recognizing more Vcs-* fields in debian/control
as far as dpkg-dev is concerned.
There are lots of upstream-metadata that we might want to have available
and we need to find a proper solution that doesn't involve debian/control
Joey Hess jo...@debian.org writes:
I would instead suggest we deprecate packages not including upstream
source in their VCS. The weight of progress is against that practice;
It is? Where can I read about this supposed weight of progress? Keeping
the debian packaging files in a separate
Russ Allbery r...@debian.org writes:
If upstream is using some other weird thing like bzr or Mercurial or
whatnot, we're now getting into rather more effort than I'd personally
want to bother with.
If Bazaar and Mercurial are “some other weird thing”, that doesn't bode
well for the future of
Ben Finney ben+deb...@benfinney.id.au writes:
Russ Allbery r...@debian.org writes:
If upstream is using some other weird thing like bzr or Mercurial or
whatnot, we're now getting into rather more effort than I'd personally
want to bother with.
If Bazaar and Mercurial are “some other weird
Russ Allbery r...@debian.org writes:
You are both taking out of context a specific example within a larger
discussion that had nothing to do with your reply, and attributing to
me rather impressive and stunning power over Debian as a whole. :)
I object! How dare you call me short!
:-)
--
OoO En cette aube naissante du jeudi 07 avril 2011, vers 07:46, Joey
Hess jo...@debian.org disait :
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get to upstreams vcs history if it
Le Wed, Apr 06, 2011 at 10:53:55PM -0700, Russ Allbery a écrit :
However, is the control file really the right place for that? I guess we
don't have a better place right now, but this doesn't feel like package
metadata that needs to be put into the Sources file.
Hi,
there is my pet project
On Thu, Apr 7, 2011 at 1:46 PM, Joey Hess jo...@debian.org wrote:
I would instead suggest we deprecate packages not including upstream
source in their VCS. The weight of progress is against that practice;
tools have improved so there is little excuse to do it, it increasingly
violates
On Thu, Apr 07, 2011 at 08:22:06AM +0200, Raphael Hertzog wrote:
There are lots of upstream-metadata that we might want to have available
and we need to find a proper solution that doesn't involve debian/control.
In Debian Med and Debian Science we are just using
On 04/07/2011 10:11 AM, Charles Plessy wrote:
http://wiki.debian.org/UpstreamMetadata
The key concept is to store ‘Field: value’ data in a file called
debian/upstream-metadata.yaml, and to access it from the VCS where
the package is stored (that is, not from the source package itself).
Uh
On Thu, 2011-04-07 at 16:33 +1000, Ben Finney wrote:
Joey Hess jo...@debian.org writes:
* pristine-tar cannot be used
The assumptions of ‘pristine-tar’ seem very Git-centric and are quite at
odds with my chosen VCS (Bazaar). It demands a “treeish object”, I have
no idea what that relates
Hi -devel!
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get to upstreams vcs history if it is not imported in
debian's vcs (which is often the case when using svn-bp or git-bf with
Am Mittwoch, den 06.04.2011, 12:06 +0200 schrieb Evgeni Golov:
Hi -devel!
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get to upstreams vcs history if it is not imported in
debian's
On Wed, Apr 06, 2011 at 12:28:39PM +0200, Benjamin Drung wrote:
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get to upstreams vcs history if it is not imported in
debian's vcs
Am Mittwoch, den 06.04.2011, 11:39 -0700 schrieb Steve Langasek:
On Wed, Apr 06, 2011 at 12:28:39PM +0200, Benjamin Drung wrote:
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get
On Wed, Apr 06, 2011 at 08:55:05PM +0200, Benjamin Drung wrote:
Am Mittwoch, den 06.04.2011, 11:39 -0700 schrieb Steve Langasek:
On Wed, Apr 06, 2011 at 12:28:39PM +0200, Benjamin Drung wrote:
There should be a Vcs-Debian-* too and used in most cases. A package
should use Vcs-Debian-* if
Evgeni Golov wrote:
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get to upstreams vcs history if it is not imported in
debian's vcs (which is often the case when using svn-bp or git-bf
Joey Hess jo...@debian.org writes:
Evgeni Golov wrote:
We (lindi, liw and me) had just a short discussion in #-devel, that it
would be nice to have some sort of Vcs-Upstream-* in debian/control, to
be able to get to upstreams vcs history if it is not imported in
debian's vcs (which is often
22 matches
Mail list logo
