we do recommend workflows (Re: Why Vcs-* fields are not at least recommended ?)

2020-08-19 Thread Holger Levsen
On Wed, Aug 19, 2020 at 02:18:08AM +0500, Andrey Rahmatullin wrote: > And we cannot recommend using a VCS because we don't usually recommend > workflows. [...] > I don't think anything is "supposed" here. We don't recommend workflows yes, we do. workflows and tools. i'm not sure why you think we

Re: we do recommend workflows (Re: Why Vcs-* fields are not at least recommended ?)

2020-08-19 Thread Andrey Rahmatullin
On Wed, Aug 19, 2020 at 09:56:49AM +, Holger Levsen wrote: > > And we cannot recommend using a VCS because we don't usually recommend > > workflows. > [...] > > I don't think anything is "supposed" here. We don't recommend workflows > > yes, we do. workflows and tools. i'm not sure why you th

Re: we do recommend workflows (Re: Why Vcs-* fields are not at least recommended ?)

2020-08-19 Thread Mattia Rizzolo
On Wed, Aug 19, 2020 at 09:56:49AM +, Holger Levsen wrote: > On Wed, Aug 19, 2020 at 02:18:08AM +0500, Andrey Rahmatullin wrote: > > And we cannot recommend using a VCS because we don't usually recommend > > workflows. > [...] > > I don't think anything is "supposed" here. We don't recommend w

Re: we do recommend workflows (Re: Why Vcs-* fields are not at least recommended ?)

2020-08-19 Thread Andrey Rahmatullin
On Wed, Aug 19, 2020 at 12:19:42PM +0200, Mattia Rizzolo wrote: > > > And we cannot recommend using a VCS because we don't usually recommend > > > workflows. > > [...] > > > I don't think anything is "supposed" here. We don't recommend workflows > > > > yes, we do. workflows and tools. i'm not su

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Ulrike Uhlig
Hi Alexis, On 18.08.20 23:10, Alexis Murzeau wrote: > I'm wondering why Vcs-* fields in debian/control (Vcs-Browser and/or > Vcs-) > are not recommended (or maybe even strongly recommended) ? (I mean here that > I think > having Vcs-* fields should be recommended for active packages) > There i

Re: introducing an epoch for src:debian-security-support

2020-08-19 Thread Emilio Pozuelo Monfort
On 17/08/2020 12:01, Holger Levsen wrote: > hi, > > debian-security-support | 2019.12.12~deb8u2 | jessie-security | > source, all > debian-security-support | 2020.06.21~deb9u1 | stretch | > source, all > debian-security-support | 2020.06.21~deb10u1 | buster

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Roberto C . Sánchez
On Wed, Aug 19, 2020 at 12:49:11PM +0200, Ulrike Uhlig wrote: > Hi Alexis, > > On 18.08.20 23:10, Alexis Murzeau wrote: > > > I'm wondering why Vcs-* fields in debian/control (Vcs-Browser and/or > > Vcs-) > > are not recommended (or maybe even strongly recommended) ? (I mean here > > that I thi

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Andrey Rahmatullin
On Wed, Aug 19, 2020 at 07:31:08AM -0400, Roberto C. Sánchez wrote: > > For non actively maintained packages on could check them into Git > > oneself and then start a history from there, and potentially update the > > package. > > > I have had good results with snapshot.debian.org. On a few occa

Bug#968662: ITP: libinput-touch-translator -- System service translating gesture to shortcut

2020-08-19 Thread handsome_feng
Package: wnpp Severity: wishlist Owner: handsome_feng X-Debbugs-Cc: debian-devel@lists.debian.org, jianfen...@ubuntukylin.com * Package name: libinput-touch-translator Version : 1.0.0 Upstream Author : larue * URL : http://github.com/ukui/libinput-touch-translator * L

Is Vcs-Browser necessary? [was: Why Vcs-* fields are not at least recommended ?]

2020-08-19 Thread Gordon Ball
Related question: is it useful (in most cases) to recommend having Vcs-Browser where Vcs-* is also provided? As the parent noted, policy doesn't make any strong recommendation here, as to whether any Vcs-* field should be present or whether Vcs-Browser should be present also, however lintian does

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Roberto C . Sánchez
On Wed, Aug 19, 2020 at 04:33:28PM +0500, Andrey Rahmatullin wrote: > On Wed, Aug 19, 2020 at 07:31:08AM -0400, Roberto C. Sánchez wrote: > > > For non actively maintained packages on could check them into Git > > > oneself and then start a history from there, and potentially update the > > > pack

Re: The "which -s" flag

2020-08-19 Thread Clint Adams
On Tue, Aug 18, 2020 at 10:55:41AM -0400, Boyuan Yang wrote: > In theory any Debian Developers may merge, but the debianutils package is > maintained by clint@ and srivasta@ so they are responsible for this package. I > am adding them to the email receiver list explicitly. Now that `command -v` is

Re: The "which -s" flag

2020-08-19 Thread Antonio Terceiro
On Wed, Aug 19, 2020 at 01:45:05PM +, Clint Adams wrote: > On Tue, Aug 18, 2020 at 10:55:41AM -0400, Boyuan Yang wrote: > > In theory any Debian Developers may merge, but the debianutils package is > > maintained by clint@ and srivasta@ so they are responsible for this > > package. I > > am ad

Re: Tagging in Salsa -> upload: status?

2020-08-19 Thread Sean Whitton
Hello Holger, On Thu 13 Aug 2020 at 10:27PM GMT, Holger Levsen wrote: > hi Sean, > > On Thu, Aug 13, 2020 at 02:22:15PM -0700, Sean Whitton wrote: >> (It's worth noting that unlike salsa tags, the tags on dgit.debian.org >> are immutable. The maintainer pushes a tag to salsa but tag2upload >> co

Re: Tagging in Salsa -> upload: status?

2020-08-19 Thread Sean Whitton
Hello Ansgar, On Fri 14 Aug 2020 at 09:04AM +02, Ansgar wrote: > There are also other issues such as the system seeming to accepting > uploads from known-compromised keys last I looked at it, though maybe > security experts disagree how much of an issue this is in practice. If what you say about

Re: Tagging in Salsa -> upload: status?

2020-08-19 Thread Ansgar
On Wed, 2020-08-19 at 10:15 -0700, Sean Whitton wrote: > On Fri 14 Aug 2020 at 09:04AM +02, Ansgar wrote: > > There are also other issues such as the system seeming to accepting > > uploads from known-compromised keys last I looked at it, though > > maybe security experts disagree how much of an is

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Sean Whitton
Hello, On Wed 19 Aug 2020 at 12:49PM +02, Ulrike Uhlig wrote: > For actively maintained packages I personally do not understand that > people in 2020 develop code without using a VCS and still put out only > tarballs. But I might be unaware of some corner cases where this is the > only way to do

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Ulrike Uhlig
Hi! On 19.08.20 19:28, Sean Whitton wrote: > On Wed 19 Aug 2020 at 12:49PM +02, Ulrike Uhlig wrote: > >> For actively maintained packages I personally do not understand that >> people in 2020 develop code without using a VCS and still put out only >> tarballs. But I might be unaware of some corne

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Jérémy Lal
Le mer. 19 août 2020 à 19:29, Sean Whitton a écrit : > Hello, > > On Wed 19 Aug 2020 at 12:49PM +02, Ulrike Uhlig wrote: > > > For actively maintained packages I personally do not understand that > > people in 2020 develop code without using a VCS and still put out only > > tarballs. But I might

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Simon McVittie
On Wed, 19 Aug 2020 at 10:28:51 -0700, Sean Whitton wrote: > On Wed 19 Aug 2020 at 12:49PM +02, Ulrike Uhlig wrote: > > For actively maintained packages I personally do not understand that > > people in 2020 develop code without using a VCS and still put out only > > tarballs. But I might be unawar

Re: Why Vcs-* fields are not at least recommended ?

2020-08-19 Thread Wookey
On 2020-08-19 07:47 +0200, Geert Stappers wrote: > > > Please, pretty please, make `debcheckout ` possible 'dgit checkout ' is possible. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature