On Tue, Jul 23, 2019 at 1:31 PM Thomas Goirand wrote:
> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
> packaging.
While I personally don't have a problem with this, I'm not sure how
/necessary/ it is. Though inconvenient, if we have source-only
uploads as mandatory, we
On July 24, 2019 12:34:13 AM UTC, Adam Borowski wrote:
>On Wed, Jul 24, 2019 at 02:14:38AM +0200, Guillem Jover wrote:
>> On Wed, 2019-07-24 at 00:49:24 +0200, Adam Borowski wrote:
>> > ##
>> > I do not consider a flat tarball to be a preferred form for
>modification.
>> > Thus
Norbert Preining writes:
...
> Fine with me, strongly recommend git - anyway, it is already a fact that
> it is the de-facto standard, so this is a non-argument. My argument is
> for those developers who might have other ways/interests.
Would it not be worth waiting for them to respond to this i
Hi Thomas,
> Then use one?
I do use, but several people I know don't.
> The idea is to be able to use unified tooling. Currently, we can't for
> example easily do a mass-commit on all packages. Or apply a new CI test
How do you want to handle permissions? So there is a super user on salsa
who c
Hi,
On Wed, Jul 24, 2019 at 12:49:24AM +0200, Adam Borowski wrote:
> ##
> I do not consider a flat tarball to be a preferred form for modification.
> Thus, like any non-source form, it must be accompanied by a way to obtain
> the actual form for modification. There are many such
On Wed, Jul 24, 2019 at 02:14:38AM +0200, Guillem Jover wrote:
> On Wed, 2019-07-24 at 00:49:24 +0200, Adam Borowski wrote:
> > ##
> > I do not consider a flat tarball to be a preferred form for modification.
> > Thus, like any non-source form, it must be accompanied by a way to ob
On Wed, 2019-07-24 at 00:49:24 +0200, Adam Borowski wrote:
> ##
> I do not consider a flat tarball to be a preferred form for modification.
> Thus, like any non-source form, it must be accompanied by a way to obtain
> the actual form for modification. There are many such ways -- u
On 7/23/19 11:59 PM, Adam Borowski wrote:
> On Tue, Jul 23, 2019 at 07:31:11PM +0200, Thomas Goirand wrote:
>> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
>> packaging.
>
> Good. Especially if we can then drop quilt.
>
>> 2- Mandating using the "gbp patches unapplied
On 2019/07/23 19:49, Adam Borowski wrote:
> ##
> I do not consider a flat tarball to be a preferred form for modification.
> Thus, like any non-source form, it must be accompanied by a way to obtain
> the actual form for modification. There are many such ways -- unless you
> distr
Steve McIntyre writes:
>>3- Mandating using Salsa as a Git repository.
>>
>>I do believe #1 will pass easily, but that it's useless without #2, and
>>there is some kind of uncertainty. For #3, I'm not even sure we should
>>vote for that, I probably even prefer it not to be voted for myself,
>>tho
Hi!
In the light of the currently discussed GR proposal, I wonder if the
following license clause would be considered DFSG-free and GPL-compatible:
##
I do not consider a flat tarball to be a preferred form for modification.
Thus, like any non-source form, it must be accompanied b
On Tue, Jul 23, 2019 at 11:59:59PM +0200, Adam Borowski wrote:
> On Tue, Jul 23, 2019 at 07:31:11PM +0200, Thomas Goirand wrote:
> > 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
> > packaging.
>
> Good. Especially if we can then drop quilt.
>
> > 2- Mandating using th
On Tue, Jul 23, 2019 at 07:31:11PM +0200, Thomas Goirand wrote:
> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
> packaging.
Good. Especially if we can then drop quilt.
> 2- Mandating using the "gbp patches unapplied" layout for Git, as this
> seems to be the most popu
Michael Banck writes:
> On Tue, Jul 23, 2019 at 07:31:11PM +0200, Thomas Goirand wrote:
>> This probably has been floating around for some time. IMO, enough time
>> so that we start to discuss $subject.
> Why is this a GR and not a policy proposal?
Policy changes require strong consensus, and i
On Tue, Jul 23, 2019 at 04:47:32PM -0300, Michael Banck wrote:
> > This probably has been floating around for some time. IMO, enough time
> > so that we start to discuss $subject.
>
> Why is this a GR and not a policy proposal?
The policy documents the majority practices, which I think cannot be s
Hi,
On Tue, Jul 23, 2019 at 07:31:11PM +0200, Thomas Goirand wrote:
> This probably has been floating around for some time. IMO, enough time
> so that we start to discuss $subject.
Why is this a GR and not a policy proposal?
Michael
> Most other distributions I know about seem to have only the packaging
> information (debian/*) and not the upstream source in their version
> control system. So more people might be familiar with this; it also
> also makes tree-wide changes to packaging much easier ;-)
Is there a tooling around
Thomas Goirand writes:
> The idea is to be able to use unified tooling. Currently, we can't for
> example easily do a mass-commit on all packages. Or apply a new CI test
> to all packages.
That wouldn't be changed by having all repositories on Salsa. You would
need to require the same permissions
On 7/23/19 8:05 PM, Steve McIntyre wrote:
> There are genuinely good reasons for *not* using salsa. If the debian
> packaging is directly included as part of the upstream git repo(s)
> somewhere else, for example.
I just has a very interesting conversation with Tollef. If you use a
native package,
> On 23 Jul 2019, at 15:11, Thomas Goirand wrote:
>
>
> The idea is to be able to use unified tooling. Currently, we can't for
> example easily do a mass-commit on all packages. Or apply a new CI test
> to all packages. And that's even without considering the entry barrier
> for contributing t
On 7/23/19 7:55 PM, Norbert Preining wrote:
> Hi
>
> On Tue, 23 Jul 2019, Thomas Goirand wrote:
>> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
>> packaging.
>
> I don't see how we can mandate git. What if I do *not* use any vcs at
> all?
Then use one?
> I don't see t
❦ 23 juillet 2019 19:05 +01, Steve McIntyre :
>>3- Mandating using Salsa as a Git repository.
>>
>>I do believe #1 will pass easily, but that it's useless without #2, and
>>there is some kind of uncertainty. For #3, I'm not even sure we should
>>vote for that, I probably even prefer it not to be
Hey Thomas!
On Tue, Jul 23, 2019 at 07:31:11PM +0200, Thomas Goirand wrote:
>
>This probably has been floating around for some time. IMO, enough time
>so that we start to discuss $subject.
>
>Before starting any type of text for such a GR, I'd like to hear you
>folks. What are your thougts about a
On Wed, 24 Jul 2019, Norbert Preining wrote:
> > 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
> > packaging.
I forgot to add. If you ever want to go there, you also have to add
mandate that the maintainer pushes the most recent versions
to the VcsGit spec
Hi
On Tue, 23 Jul 2019, Thomas Goirand wrote:
> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using Git for
> packaging.
I don't see how we can mandate git. What if I do *not* use any vcs at
all? And I know enough projects that run on svn, hg, and other vcs.
I don't see that mandating
On Mon, 2019-07-22 at 19:56 -0700, Mo Zhou wrote:
> Hi Marc,
>
> Sorry to hear that. In fact I have some similar feelings.
>
> On 2019-07-23 01:22, Marc Munro wrote:
> > [ . . .]
> I always fail to find a better free and independent replacement to
> Debian.
> Even if the current stable release
I'll say there is something really unfortunate with the
unattended-upgrades packagekit ecosystem.
I keep finding that unattended-upgrades takes up 100% of my CPU until
I kill it.
I have not had a chance to debug enough to submit a bug, but it is
infuriating.
--Sam
Hi there!
This probably has been floating around for some time. IMO, enough time
so that we start to discuss $subject.
Before starting any type of text for such a GR, I'd like to hear you
folks. What are your thougts about all this? Especially, I'd like to
hear others that would be *AGAINST* such
Marc Munro writes:
> I feel bad about this, but I'm breaking up with you.
>
> I've been using Debian for 20 years and in that time I've never strayed
> to other distributions. But Buster is too much.
Hi Marc,
I certainly sympathise with several of you comments. I'm currently
doing my biannual
Dear Marc.
I can certainly relate to your frustration. Also with Plasma certain
things are broken, like some applications that use Qt WebEngine, IMHO
partly due to only a few people dedicating their time to do all the
packaging for Qt/KDE, which is a lot, a huge lot of work.
Marc Munro - 23.07
Hi Marc,
Love love love!
I reply to you in private to make sure that my comments are not seen as
uttered within the Debian project, which could bring me into just
another difficult situation.
But in short, I agree with lots of your comments, but Debian is still
the best distribution, so I really
On 23.07.19 08:32, Aron Xu wrote:
On Tue, Jul 23, 2019 at 11:16 AM Ximin Luo wrote:
Mo Zhou:
[..]
Oh, Gnome.
It's a pity that the "software stores" started to think they know
"what the user want" [..]
Just use XFCE. I ditched GNOME years ago and am much happier for it.
The GNOME desi
32 matches
Mail list logo
