all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
	"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"pmg-devel@lists.proxmox.com" <pmg-devel@lists.proxmox.com>,
	"pbs-devel@lists.proxmox.com" <pbs-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [pmg-devel] Dropping mixed tab/space indentation for Perl and JavaScript and adopting perltidy and biome for auto-formatting.
Date: Thu, 3 Jul 2025 12:48:46 +0200	[thread overview]
Message-ID: <1e529aa4-7b75-4c7a-b381-4f1c789d996c@proxmox.com> (raw)
In-Reply-To: <6a2a92e26f64946716e24e568a8722613b60fd25.camel@groupe-cyllene.com>

Hi,

Am 03.07.25 um 12:11 schrieb DERUMIER, Alexandre:
> I Just notice this when rebasing my patches ^_^
> 
> (sorry my last patch serie was still tab+spaces)


Yeah, sorry for the fallout, but we needed to have a cut sooner or later.


git rebase --ignore-whitespace

or 

git am -3 --ignore-whitespace path/to/patches/*.patch

Should hopefully reduce the load here.

Else, you could run perltidy in a copy of the repo with your patches
applied and then copy over the files to the cleaned up repos and commit
them again, a bit more work but simple and should avoids handling
conflicts, if you prefer avoiding them.


> I'm trying to install proxmox-perltidy but it depend on perltidy
> 20250311.05
> 
> dpkg: dependency problems prevent configuration of proxmox-perltidy:
>  proxmox-perltidy depends on perltidy (>= 20250311.05-~~); however:
> 
> 
> and debian13 package is 20250105.
> 
> is this packge version of perltidy available somewhere ?
> 

We uploaded the newer perltidy to our devel repo, which is available for bookworm:

deb http://download.proxmox.com/debian/devel bookworm main

And trixie:

deb http://download.proxmox.com/debian/devel trixie main

Or in the newer deb822 based sources format that trixie prefers:

Types: deb
URIs: http://download.proxmox.com/debian/devel
Suites: trixie
Components: main
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
	"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"pmg-devel@lists.proxmox.com" <pmg-devel@lists.proxmox.com>,
	"pbs-devel@lists.proxmox.com" <pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [pmg-devel] [pve-devel] Dropping mixed tab/space indentation for Perl and JavaScript and adopting perltidy and biome for auto-formatting.
Date: Thu, 3 Jul 2025 12:48:46 +0200	[thread overview]
Message-ID: <1e529aa4-7b75-4c7a-b381-4f1c789d996c@proxmox.com> (raw)
In-Reply-To: <6a2a92e26f64946716e24e568a8722613b60fd25.camel@groupe-cyllene.com>

Hi,

Am 03.07.25 um 12:11 schrieb DERUMIER, Alexandre:
> I Just notice this when rebasing my patches ^_^
> 
> (sorry my last patch serie was still tab+spaces)


Yeah, sorry for the fallout, but we needed to have a cut sooner or later.


git rebase --ignore-whitespace

or 

git am -3 --ignore-whitespace path/to/patches/*.patch

Should hopefully reduce the load here.

Else, you could run perltidy in a copy of the repo with your patches
applied and then copy over the files to the cleaned up repos and commit
them again, a bit more work but simple and should avoids handling
conflicts, if you prefer avoiding them.


> I'm trying to install proxmox-perltidy but it depend on perltidy
> 20250311.05
> 
> dpkg: dependency problems prevent configuration of proxmox-perltidy:
>  proxmox-perltidy depends on perltidy (>= 20250311.05-~~); however:
> 
> 
> and debian13 package is 20250105.
> 
> is this packge version of perltidy available somewhere ?
> 

We uploaded the newer perltidy to our devel repo, which is available for bookworm:

deb http://download.proxmox.com/debian/devel bookworm main

And trixie:

deb http://download.proxmox.com/debian/devel trixie main

Or in the newer deb822 based sources format that trixie prefers:

Types: deb
URIs: http://download.proxmox.com/debian/devel
Suites: trixie
Components: main
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
	"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"pmg-devel@lists.proxmox.com" <pmg-devel@lists.proxmox.com>,
	"pbs-devel@lists.proxmox.com" <pbs-devel@lists.proxmox.com>
Subject: Re: [pmg-devel] [pve-devel] Dropping mixed tab/space indentation for Perl and JavaScript and adopting perltidy and biome for auto-formatting.
Date: Thu, 3 Jul 2025 12:48:46 +0200	[thread overview]
Message-ID: <1e529aa4-7b75-4c7a-b381-4f1c789d996c@proxmox.com> (raw)
In-Reply-To: <6a2a92e26f64946716e24e568a8722613b60fd25.camel@groupe-cyllene.com>

Hi,

Am 03.07.25 um 12:11 schrieb DERUMIER, Alexandre:
> I Just notice this when rebasing my patches ^_^
> 
> (sorry my last patch serie was still tab+spaces)


Yeah, sorry for the fallout, but we needed to have a cut sooner or later.


git rebase --ignore-whitespace

or 

git am -3 --ignore-whitespace path/to/patches/*.patch

Should hopefully reduce the load here.

Else, you could run perltidy in a copy of the repo with your patches
applied and then copy over the files to the cleaned up repos and commit
them again, a bit more work but simple and should avoids handling
conflicts, if you prefer avoiding them.


> I'm trying to install proxmox-perltidy but it depend on perltidy
> 20250311.05
> 
> dpkg: dependency problems prevent configuration of proxmox-perltidy:
>  proxmox-perltidy depends on perltidy (>= 20250311.05-~~); however:
> 
> 
> and debian13 package is 20250105.
> 
> is this packge version of perltidy available somewhere ?
> 

We uploaded the newer perltidy to our devel repo, which is available for bookworm:

deb http://download.proxmox.com/debian/devel bookworm main

And trixie:

deb http://download.proxmox.com/debian/devel trixie main

Or in the newer deb822 based sources format that trixie prefers:

Types: deb
URIs: http://download.proxmox.com/debian/devel
Suites: trixie
Components: main
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg


_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel


  reply	other threads:[~2025-07-03 10:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-01 11:25 Thomas Lamprecht
2025-06-01 11:25 ` [pve-devel] " Thomas Lamprecht
2025-06-01 11:25 ` [pbs-devel] " Thomas Lamprecht
2025-07-03 10:11 ` [pbs-devel] [pve-devel] " DERUMIER, Alexandre
2025-07-03 10:11   ` [pmg-devel] " DERUMIER, Alexandre
2025-07-03 10:48   ` Thomas Lamprecht [this message]
2025-07-03 10:48     ` Thomas Lamprecht
2025-07-03 10:48     ` [pbs-devel] " Thomas Lamprecht
2025-07-03 10:11 ` DERUMIER, Alexandre via pve-devel
2025-07-03 10:16   ` Fabian Grünbichler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1e529aa4-7b75-4c7a-b381-4f1c789d996c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=alexandre.derumier@groupe-cyllene.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal