Paul Wise writes ("Re: Upstream metadata to help our users contribute back to
projects we redistribute."):
> https://wiki.debian.org/UpstreamMetadata
Alex Muntada writes ("Re: Upstream metadata to help our users contribute back
to projects we redistribute."):
> We us
Package: dgit
Version: 9.0
Felipe Sateler writes ("Re: Upstream metadata to help our users contribute back
to projects we redistribute."):
> On Thu, 25 Jul 2019 16:26:02 +0200, Xavier wrote:
> > pkg-js-tools embeds a tool that generates debian/upstream/metadata for
>
Felipe Sateler writes:
> Are there tools that are actively using this information? Unfortunately,
> the links you quote below do not provide much information about where
> this information is used (other than bibref table in UDD).
For the (science) Pure Blends, this information is displayed in
On Thu, Jul 25, 2019 at 3:34 PM Jelmer Vernooij wrote:
>
>
> On 25 July 2019 15:17:13 GMT+01:00, Felipe Sateler
> wrote:
> >On Thu, 25 Jul 2019 17:27:51 +0900, Charles Plessy wrote:
> >
> >> Hello everybody,
> >
> >Hello Charles,
> >
> >>
> >> (posted on -project because of the context, but answ
Hi Chris,
> With the current state of the upstream metadata docs, I was
> about to abandon the effort of adding metadata. It's not clear
> at all which fields are useful, how a "normal" file looks like,
> what it contains, ...
> Skimming the wiki gives me the impression its only useful for
> acade
On Mon, Jul 29, 2019 at 5:18 PM Chris Hofstaedtler wrote:
> http://upstream-metadata.debian.net appears to be dead.
>From the wiki:
Help! there is a bug that I do not manage to solve by myself. -- Charles
https://lists.debian.org/debian-qa/2014/06/msg00022.html
> Is there a canonical documentat
* Charles Plessy [190725 10:28]:
> For many of you, I am sure that it is only a reminder. But in any case
> please have a look at https://wiki.debian.org/debian/upstream and
> https://wiki.debian.org/AppStream for details.
Someone else has asked me recently to ship a
debian/upstream/metadata fil
On Thu, Jul 25, 2019 at 05:27:51PM +0900, Charles Plessy wrote:
> (posted on -project because of the context, but answers probably
> belong to -devel, where I am not subscribed...)
I understand we live in strange times, but pleaaase, if your
content belongs on -devel, but you are neither s
On Thu, Jul 25, 2019 at 4:28 PM Charles Plessy wrote:
> This is why some packges are shipping metadata indicating where to find
> the upstream sources, send upstream bugs, or even where to dontate
> money, in order to help our users contribute back to the developement
> of the software that Debian
On 25 July 2019 15:17:13 GMT+01:00, Felipe Sateler wrote:
>On Thu, 25 Jul 2019 17:27:51 +0900, Charles Plessy wrote:
>
>> Hello everybody,
>
>Hello Charles,
>
>>
>> (posted on -project because of the context, but answers probably
>belong
>> to -devel, where I am not subscribed...)
>>
>> there
On Thu, 25 Jul 2019 16:26:02 +0200, Xavier wrote:
> Hi,
>
> pkg-js-tools embeds a tool that generates debian/upstream/metadata for
> Github repositories (github-missing-upstream).
Thanks, this is useful. It's named github-debian-upstream though ;)
>
> dpt from pkg-perl-tools uses this file to
Hi,
pkg-js-tools embeds a tool that generates debian/upstream/metadata for Github
repositories (github-missing-upstream).
dpt from pkg-perl-tools uses this file to link locally upstream repo in "git
remote"
Le 25 juillet 2019 16:17:13 GMT+02:00, Felipe Sateler a
écrit :
>On Thu, 25 Jul 201
On Thu, 25 Jul 2019 17:27:51 +0900, Charles Plessy wrote:
> Hello everybody,
Hello Charles,
>
> (posted on -project because of the context, but answers probably belong
> to -devel, where I am not subscribed...)
>
> there is an intersting discussion going on about Git and the preferred
> form f
Hello everybody,
(posted on -project because of the context, but answers probably
belong to -devel, where I am not subscribed...)
there is an intersting discussion going on about Git and the preferred
form for modification of the programs we redistribute.
Indeed, as of today would be hard to say
14 matches
Mail list logo