Bonjour Ben,
Le lun. 28 nov. 2022 à 17:36, Ben Westover a écrit :
>
> > I also reverted 2e079e6d because this change is not in 6.0.2-3.
>
> That commit was needed for the libraries to present the right version;
> without it, the their Debian revision is -3 which conflicts with the
> existing
Bonjour Dylan,
On 11/22/22 04:09, Dylan Aïssi wrote:
> I just uploaded ppm 6.0.2-3~bpo11+1 to bullseye-backports with a delay of
> 6 days to be sure 6.0.2-3 lands in bookworm first.
>
> I also reverted 2e079e6d because this change is not in 6.0.2-3.
That commit was needed for the libraries to
Bonjour Ben,
I just uploaded ppm 6.0.2-3~bpo11+1 to bullseye-backports with a delay of
6 days to be sure 6.0.2-3 lands in bookworm first.
I also reverted 2e079e6d because this change is not in 6.0.2-3.
Best,
Dylan
Bonjour Dylan,
On 11/14/22 09:41, Dylan Aïssi wrote:
>> I've elected to just build it with the nocheck profile.
>
> Currently, without adding at least python3-distutils (and maybe other?) in BD,
> pcm fails at the dh_auto_configure step with:
>
>> ModuleNotFoundError: No module named
Bonjour Ben,
Le sam. 12 nov. 2022 à 23:12, Ben Westover a écrit :
>
> Correct me if I'm wrong, but I that believe for backports, keeping it
> minimally different from the original package is prioritized over things
> like functional tests, docs, etc.
That is correct.
> Thus, instead of adding
Bonjour Dylan,
On 11/8/22 12:15 PM, Dylan Aïssi wrote:
> Thanks for preparing the package. I tried to build it with gbp buildpackage
> in a clean bullseye environment but it failed. It seems some build-deps are
> missing from the control file. At least python3-distutils needs to be added
> but
>
Hello Ben,
Le jeu. 3 nov. 2022 à 18:54, Ben Westover a écrit :
>
> Thanks for the link. I have uploaded my backport to Mentors [1] for your
> sponsorship, and it's also available in the debian/bullseye branch of my
> package repo [2]. Can you provide DM access after it passes NEW?
>
Thanks for
Hello Dylan,
On 11/3/22 10:30 AM, Dylan Aïssi wrote:
> The backport will have to go through the backport NEW queue, so you
> need a DD to sponsor the initial version. I can sponsor it if you
> want, I just need a git repo with a backport branch to build it :-).
> Meanwhile, you can request to
Hi,
> It's certainly possible with little to no modification of the package,
> as I have already backported pacman to bullseye in my personal repo [1].
> I could officially get it in Debian backports for bullseye once I learn
> more about how the process works (I'm only a DM at the moment).
The
Hello Christopher,
On 11/3/22 4:53 AM, Christopher Obbard wrote:> We need pacman to install
packages inside the built image, which is only
> available for >bookworm. Since it's not feasible to upgrade our container
> images to bookworm as it's still testing, would it be possible to backport
>
Source: pacman-package-manager
Version: 6.0.2-1
Severity: wishlist
Dear Maintainer,
In debos (https://github.com/go-debos/debos) we are enabling support for
building Arch images. As part of Debos upstream, we ship a container based on
Debian Bullseye which should support all of the features
11 matches
Mail list logo
