Hi Fabio,
Fabio Fantoni writes:
> Il 24/01/2025 22:24, Xiyue Deng ha scritto:
>> Fabio Fantoni writes:
>>> ...
>>>
>>> There is also another thing to consider, if you keep a generic one as
>>> default it always points to the latest version, while a specific one
>>> might not be the latest versi
tho...@goirand.fr writes:
> On Jan 24, 2025 22:24, Xiyue Deng wrote:
>
>>
>
>> Fabio Fantoni writes:
>
>> >
>
>> > ...
>
>> >
>
>> > There is also another thing to consider, if you keep a generic one as
>
>> > default it always points to the latest version, while a specific one
>
>> > migh
Greetings,
"dpkg -R -i --refuse-downgrade --force-unsafe-io . "
"--force-unsafe-io" seems to be ignored - it still makes my HDD churn
the same way on each unpack.
I've tried the reverse --refuse-unsafe-io, exact same thing.
I have a list of 628 debian packages, totalling ~0.5 GB.
With an aver
On Fri, 2025-01-24 at 17:49 +0100, Fabio Fantoni wrote:
>
> If we want to continue to use mainly BTS I think you should have an
> integration with something that allows you to do more things from the
> web interface, in a simple and fast way.
>
> I recently saw this project that seems good to s
On 24/01/25 23:12, Soren Stoutner wrote:
I agree that we need one standard naming scheme. Based on the email
responses, it seems like debian/latest doesn’t convey the appropriate
meaning, with something like debian/unstable being more appropriate.
As pointed out in another subthread, DEP-14 d
Il 24/01/2025 23:12, Soren Stoutner ha scritto:
On Friday, January 24, 2025 9:50:10 AM MST Otto Kekäläinen wrote:
> Thanks everyone for sharing your viewpoints, it is interesting to read!
>
> I feel I need to clarify that I am not a native English speaker and my
> intent was to write a polit
Il 24/01/2025 22:24, Xiyue Deng ha scritto:
Fabio Fantoni writes:
...
There is also another thing to consider, if you keep a generic one as
default it always points to the latest version, while a specific one
might not be the latest version and if the contributors do not check
well the branche
On Friday, January 24, 2025 9:50:10 AM MST Otto Kekäläinen wrote:
> Thanks everyone for sharing your viewpoints, it is interesting to read!
>
> I feel I need to clarify that I am not a native English speaker and my
> intent was to write a polite and honest email. It does not say
> anywhere that "y
On 24/01/25 12:22, Johannes Schauer Marin Rodrigues wrote:
Quoting Gioele Barabucci (2025-01-24 09:49:27)
I disagree with this conclusion. Sometimes features are extensively
discussed in salsa merge requests or issues, and the entire discussion just
can't be summarized in a git commit message (a
On Jan 24, 2025 22:24, Xiyue Deng wrote:
>
> Fabio Fantoni writes:
> >
> > ...
> >
> > There is also another thing to consider, if you keep a generic one as
> > default it always points to the latest version, while a specific one
> > might not be the latest version and if the cont
Package: wnpp
Severity: wishlist
Owner: Arthur Diniz
* Package name: golang-k8s-kms
Version : 0.31.4-1
Upstream Author : Kubernetes
* URL : https://github.com/kubernetes/kms
* License : Apache-2.0
Programming Lang: Go
Description : Kubernetes KMS implem
Fabio Fantoni writes:
>
> ...
>
> There is also another thing to consider, if you keep a generic one as
> default it always points to the latest version, while a specific one
> might not be the latest version and if the contributors do not check
> well the branches they could risk wasting time
Hi Colin,
Colin Watson writes:
> On Thu, Jan 23, 2025 at 10:57:56PM -0800, Xiyue Deng wrote:
>> Actually there may be another reason to turn off MR feature: some
>> packaging workflows don't preserve a linear Git history and hence may
>> not work well with merging from MR on Salsa. For example,
Il 24/01/2025 15:26, Christoph J. Scherr ha scritto:
On Fri, 2025-01-24 at 13:05 +0100, Jonas Smedegaard wrote:
Hi Christoph,
Quoting Christoph J. Scherr (2025-01-24 12:13:16)
Hello,
As someone just starting out with Debian, I'd like to share my perspective
on
this discussion.
I only recentl
Hello,
I don't think there's a need to use a Debian-specific name for this
concept. 'master' or 'main' are fine.
debian/bookworm etc.. are a different story; I am glad we have those.
As there is much disagreement, maybe we could drop the default branch
name part of the DEP and mark the rest of
Package: wnpp
Severity: wishlist
Owner: Matthias Geiger
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-r...@lists.debian.org,
werdah...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: cxxbridge-cmd
Version : 1.0.137
Upstream Contact: David Tolnay
Package: wnpp
Severity: wishlist
Owner: Sylvestre Ledru
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: jj
* URL : https://github.com/jj-vcs/jj
* License : Apache 2
Programming Lang: Rust
Description : A Git-compatible VCS that is both simple and power
Hi Otto,
Quoting Otto Kekäläinen (2025-01-24 18:24:55)
> Hi Jonas!
>
> > > If you don't like using Salsa or don't like reviewing Merge Requests,
> > > then this call is probably not for you. However, if you want Debian to
> > > grow and you want to welcome new contributors, or in general work in
> Is there some way to drill down into groups and then set preferences on
> an individual repo that's not in one's own namespace?
Yes - you can for example open https://salsa.debian.org/debian/openqa
and in the top right corner click on the bell icon, and select
"Watch". That will make you get not
Le 2025-01-24 13:00, Andrea Pappacoda a écrit :
Same for me. In addition, on the topic of making things easier for new
contributors, when I first started using Salsa I felt lost in the
myriad
of features and options enabled by default. Not only 99% of projects
hosted on Salsa don't need featur
Hi Jonas!
> > If you don't like using Salsa or don't like reviewing Merge Requests,
> > then this call is probably not for you. However, if you want Debian to
> > grow and you want to welcome new contributors, or in general work in a
> > collaborative way towards ending single-maintainer packages,
Thanks everyone for sharing your viewpoints, it is interesting to read!
I feel I need to clarify that I am not a native English speaker and my
intent was to write a polite and honest email. It does not say
anywhere that "you must use debian/latest". I am happy with whatever
the convention is, as l
Quoting Christoph J. Scherr (2025-01-24 15:26:39)
> Writing a Pro/Con list might be a good idea, but I am not proficient
> enough in both the BTS and GitLab to do so.
That sounds like an excellent approach to me.
I will leave that for others, as I have lost my bearing on what is on
topic for this
Hi,
On Fri, 24 Jan 2025, Jonathan Dowland wrote:
> To some extent this is backwards. DEPs are supposed to codify best practice;
> DEP-14 suggests something that the majority of packages are not actually
> doing.
That's not correct. We have this requirement for Debian policy, it's
supposed to codi
> "Gioele" == Gioele Barabucci writes:
Gioele> On 24/01/25 13:18, Colin Watson wrote:
>> I agree with this. From Otto in another thread:
>>
>> "It is sad to see that in Debian usage of git is stifled by
>> simple things like people not agreeing to use a common branch
Package: wnpp
Severity: wishlist
Owner: Pete Ryland
X-Debbugs-Cc: debian-devel@lists.debian.org, p...@pdr.cx,
debian-hask...@lists.debian.org
* Package name: haskell-language-server
Version : 2.9.0.1
Upstream Contact: Alan Zimmerman
* URL : https://github.com/haskell
Emanuele Rocca writes:
> On 2025-01-24 12:08, Colin Watson wrote:
>> You can do this with preseed/late_command
>> (https://www.debian.org/releases/bookworm/amd64/apbs05.en.html#preseed-hooks,
>> and see https://www.debian.org/releases/bookworm/amd64/apb.en.html for
>> general advice on preseeding
Colin Watson writes:
> On Fri, Jan 24, 2025 at 09:40:50AM +0100, PICCA Frederic-Emmanuel wrote:
>> Hello, I would like to customize the debian-installer in order to allow root
>> access once installed via an authorize key.
>>
>> so I need to put something like this in the /root/.ssh/ during the
On Fri, 2025-01-24 at 13:05 +0100, Jonas Smedegaard wrote:
> Hi Christoph,
>
> Quoting Christoph J. Scherr (2025-01-24 12:13:16)
> > Hello,
> >
> > As someone just starting out with Debian, I'd like to share my perspective
> > on
> > this discussion.
> >
> > I only recently contacted the welcome
Il 24/01/2025 14:25, Tobias Frost ha scritto:
Am Fri, Jan 24, 2025 at 09:16:50AM +0300 schrieb Michael Tokarev:
24.01.2025 04:06, Otto Kekäläinen wrote:
3. "latest" is a misnomer (unlike "main" or "master"). For example, I often use
"experimental" branch which is more recent than "master",
On 1/24/25 14:25, Tobias Frost wrote:
Am Fri, Jan 24, 2025 at 09:16:50AM +0300 schrieb Michael Tokarev:
24.01.2025 04:06, Otto Kekäläinen wrote:
3. "latest" is a misnomer (unlike "main" or "master"). For example, I often use
"experimental" branch which is more recent than "master", yet the
On 2025-01-24 10:06:13 +0100 (+0100), Julien Plissonneau Duquène wrote:
> Le 2025-01-24 09:49, Gioele Barabucci a écrit :
[...]
> > True. This is why MR discussions should be automatically saved in git
> > notes attached to the merge commit. In this way the discussion will be
> > preserved and the
Sam Hartman writes:
>> "Otto" == Otto Kekäläinen writes:
>
>
> Otto> I would be curious to hear why people are *not* adopting
> Otto> 'debian/latest'?
>
> Because debian/latest is more to type and because until we adopt
> something I think has a chance of getting real conformity, I a
Am Fri, Jan 24, 2025 at 09:16:50AM +0300 schrieb Michael Tokarev:
> 24.01.2025 04:06, Otto Kekäläinen wrote:
>
> 3. "latest" is a misnomer (unlike "main" or "master"). For example, I often
> use
> "experimental" branch which is more recent than "master", yet the main
> development is happeni
On 2025-01-24 12:08, Colin Watson wrote:
> You can do this with preseed/late_command
> (https://www.debian.org/releases/bookworm/amd64/apbs05.en.html#preseed-hooks,
> and see https://www.debian.org/releases/bookworm/amd64/apb.en.html for
> general advice on preseeding if you haven't used it before)
On 24/01/25 13:18, Colin Watson wrote:
I agree with this. From Otto in another thread:
"It is sad to see that in Debian usage of git is stifled by simple
things like people not agreeing to use a common branch naming scheme
despite there being a proposal for 10+ years now."
I use git e
Hi,
On Fri, 24 Jan 2025, at 02:06, Otto Kekäläinen wrote:
> Why does the majority of Debian packages still use 'master' or
> 'debian/master' branch as the main development branch?
I’ve not really used debian/master or debian/latest because it does not seem to
convey what I’m intending by the bra
Quoting Antonio Terceiro (2025-01-24 13:09:10)
> On Fri, Jan 24, 2025 at 11:07:40AM +0100, Jonas Smedegaard wrote:
> > Quoting Otto Kek�l�inen (2025-01-24 01:32:34)
> > > If you don't like using Salsa or don't like reviewing Merge Requests,
> > > then this call is probably not for you. However, if
On Thu, Jan 23, 2025 at 07:35:23PM -0700, Sam Hartman wrote:
> > "Otto" == Otto Kekäläinen writes:
>
> Otto> Could you give it a try please? Salsa isn't that bad :)
>
> Can you please respect people who have different positions than you?
> I'm this close to turning off MRs for all my pac
On Thu, Jan 23, 2025 at 8:07 PM Otto Kekäläinen wrote:
> Git is a great tool for collaboration. It is sad to see that in Debian
> usage of git is stifled by simple things like people not agreeing to
> use a common branch naming scheme despite there being a proposal for
> 10+ years now.
Your timel
On Fri, Jan 24, 2025 at 12:18:18PM +, Colin Watson wrote:
> > Otto> Could you give it a try please? Salsa isn't that bad :)
> > Can you please respect people who have different positions than you?
> > I'm this close to turning off MRs for all my packages and promising to
> > be the last per
On Thu, Jan 23, 2025 at 10:57:56PM -0800, Xiyue Deng wrote:
> Actually there may be another reason to turn off MR feature: some
> packaging workflows don't preserve a linear Git history and hence may
> not work well with merging from MR on Salsa. For example, the "git-dpm"
> and "git-debrebase" wo
Hi all,
On Fri Jan 24, 2025 at 10:50 AM CET, Jonas Smedegaard wrote:
Quoting Chris Hofstaedtler (2025-01-24 01:51:27)
BTW, a lot of other gitlab features should probably be off for most
packaging repositories.
Currently, when I create a new project at Salsa, I do the following:
1. Among the
On Fri, Jan 24, 2025 at 11:07:40AM +0100, Jonas Smedegaard wrote:
> Quoting Otto Kekäläinen (2025-01-24 01:32:34)
> > If you don't like using Salsa or don't like reviewing Merge Requests,
> > then this call is probably not for you. However, if you want Debian to
> > grow and you want to welcome new
On Fri, Jan 24, 2025 at 09:40:50AM +0100, PICCA Frederic-Emmanuel wrote:
> Hello, I would like to customize the debian-installer in order to allow root
> access once installed via an authorize key.
>
> so I need to put something like this in the /root/.ssh/ during the
> installation
>
> echo "s
Hi Christoph,
Quoting Christoph J. Scherr (2025-01-24 12:13:16)
> On Fri, 2025-01-24 at 11:07 +0100, Jonas Smedegaard wrote:
> > Quoting Otto Kekäläinen (2025-01-24 01:32:34)
> > > If you don't like using Salsa or don't like reviewing Merge Requests,
> > > then this call is probably not for you. H
Il 24/01/2025 02:06, Otto Kekäläinen ha scritto:
Hi!
Current https://dep-team.pages.debian.net/deps/dep14/ states that the
default Debian branch name is 'debian/latest':
In Debian this means that uploads to unstable and experimental should be
prepared either in
the debian/latest branch or res
Hi,
Quoting Gioele Barabucci (2025-01-24 09:49:27)
> > I disagree with this conclusion. Sometimes features are extensively
> > discussed in salsa merge requests or issues, and the entire discussion just
> > can't be summarized in a git commit message (and it is not desirable to
> > even attempt th
On Fri, 2025-01-24 at 11:07 +0100, Jonas Smedegaard wrote:
> Quoting Otto Kekäläinen (2025-01-24 01:32:34)
> > If you don't like using Salsa or don't like reviewing Merge Requests,
> > then this call is probably not for you. However, if you want Debian to
> > grow and you want to welcome new contri
Quoting Otto Kekäläinen (2025-01-24 01:32:34)
> If you don't like using Salsa or don't like reviewing Merge Requests,
> then this call is probably not for you. However, if you want Debian to
> grow and you want to welcome new contributors, or in general work in a
> collaborative way towards ending
Quoting Chris Hofstaedtler (2025-01-24 01:51:27)
> * Sam Hartman [250123 23:47]:
> > > ...
> > >> > Numerous people are posting Merge Requests on Salsa. Please
> > >> help review them!
> >
> > I think it would improve collaboration a lot if we could make an effort
> > to get salsa project
Otto Kekäläinen writes:
> Hi!
>
>> I think it would improve collaboration a lot if we could make an effort
>> to get salsa projects into one of two states:
>>
>> * Merge requests are disabled for that project
>>
>> * Merge requests are actively watched at least as closely as the BTS
>
> We should
> debian/latest = UNRELEASED (may be unstable or experimental)
>
> debian/unstable = This will be uploaded to unstable.
I wouldn't think that is needed at all, since git tags exist.
so tags is what gets uploaded and the rest isn't already.
--
Salvo Tomaselli
"Io non mi sento obbligato a cred
On Fri Jan 24, 2025 at 1:06 AM GMT, Otto Kekäläinen wrote:
I would be curious to hear why people are *not* adopting
'debian/latest'?
Why does the majority of Debian packages still use 'master' or
'debian/master' branch as the main development branch?
In my case (not many packages, mostly solo
Le 2025-01-24 09:49, Gioele Barabucci a écrit :
On 24/01/25 09:00, Julien Plissonneau Duquène wrote:
Also note that the contents that really matter is the git
repositories
themselves.
I do not agree with this premise.
The Git repo is forever and `git log` is how you search its history.
Ext
Julien Plissonneau Duquène writes:
> Le 2025-01-24 09:37, Gioele Barabucci a écrit :
>> Even if we were to keep "master" instead of "latest", it's much better to use
>> "upstream/master" and "debian/master": no name clashes and no ambiguity about
>> which "master" one is referring to.
>
> Or may
Gioele Barabucci writes:
> On 24/01/25 09:30, Gard Spreemann wrote:
>>> I would be curious to hear why people are *not* adopting 'debian/latest'?
>> I call the branch debian/sid simply because sid is already what we call
>> the distribution where we by default do work on the "latest stuff".
>
>
Hello, I would like to customize the debian-installer in order to allow root
access once installed via an authorize key.
so I need to put something like this in the /root/.ssh/ during the installation
echo "ssh-rsa
B3NzaC1yc2EDAQABAAACAQDGkFpSsCIGpAJtsH4TWHCatHMkdGMS/PTG2M/7xeWz6Syw/JUr
Le 2025-01-24 09:37, Gioele Barabucci a écrit :
Even if we were to keep "master" instead of "latest", it's much better
to use "upstream/master" and "debian/master": no name clashes and no
ambiguity about which "master" one is referring to.
Or maybe `debian/main` to keep up with the popular t
On 24/01/25 09:00, Julien Plissonneau Duquène wrote:
Also note that the contents that really matter is the git repositories
themselves.
I do not agree with this premise.
The Git repo is forever and `git log` is how you search its history.
External websites will one day be gone. And are not a
On 24/01/25 09:30, Gard Spreemann wrote:
I would be curious to hear why people are *not* adopting 'debian/latest'?
I call the branch debian/sid simply because sid is already what we call
the distribution where we by default do work on the "latest stuff".
You mean debian/unstable, don't you? :
On 1/24/25 09:37, Gioele Barabucci wrote:
On 24/01/25 09:10, Julien Plissonneau Duquène wrote:
Since 2020/2021 the whole 'master' was deprecated in
favor of 'main' by most git services and tools, yet 'master' is still
the most popular one in Debian.
... precisely in 2020-11-29. Before that the
Otto Kekäläinen writes:
> Hi!
>
> Current https://dep-team.pages.debian.net/deps/dep14/ states that the
> default Debian branch name is 'debian/latest':
>
>> In Debian this means that uploads to unstable and experimental should be
>> prepared either in
>> the debian/latest branch or respectively
On 24/01/25 09:10, Julien Plissonneau Duquène wrote:
Since 2020/2021 the whole 'master' was deprecated in
favor of 'main' by most git services and tools, yet 'master' is still
the most popular one in Debian.
... precisely in 2020-11-29. Before that the DEP recommended
`debian/master`.
As a r
Le 2025-01-24 07:16, Michael Tokarev a écrit :
2. With debian/* I lose another convenient way to use debian/ as a path
name,
without adding "--" to the options.
As an alternative you may find `./` easier to type, depending on which
keyboard layout you are using.
Cheers,
--
Julien Plis
Le 2025-01-24 02:06, Otto Kekäläinen a écrit :
The DEP-14 has been around since November 2014 and one would think
that DDs would have adopted 'debian/latest' as the default branch and
git head now.
To be fair `debian/latest` was introduced much later in that DEP history
...
Since 2020/2021
Hi,
Le 2025-01-24 01:23, Otto Kekäläinen a écrit :
Also note that the contents that really matter is the git repositories
themselves.
I do not agree with this premise.
The Merge Request feature is not intended to be a place of
permanent documentation. It is just a tool to facilitate fast an
67 matches
Mail list logo
