On Wed, May 14, 2025 at 06:58:22PM +0200, Santiago Vila wrote:
> El 14/5/25 a las 12:50, Adrian Bunk escribió:
>...
> > How many of the packages that break with "make --shuffle" are currently
> > doing parallel building?
> > I am asking since these might be RC bugs for trixie.
>
> I believed (rega
El 14/5/25 a las 19:27, Adrian Bunk escribió:
On Wed, May 14, 2025 at 06:58:22PM +0200, Santiago Vila wrote:
El 14/5/25 a las 12:50, Adrian Bunk escribió:
...
How many of the packages that break with "make --shuffle" are currently
doing parallel building?
I am asking since these might be RC bug
+Jelmer, who is the maintainer of the metadata specification
> https://wiki.debian.org/UpstreamMetadata
>
> That's pretty much where we are now. This was done in the pre-Salsa time, and
> if people get excited about the concept, I guess that Salsa offers new
> opportunities to play with the conce
Am Wed, May 14, 2025 at 09:40:54AM +0200 schrieb Lucas Nussbaum:
> > * 37641 source packages in trixie/main
> > * of which 36083 declare a VCS URL
> > * of which 34644 point to a salsa project
> > * of which 34370 point to a salsa project that exists
> >
> > [...]
>
> This is now available at htt
Hello,
On Wed 14 May 2025 at 10:41am +02, PICCA Frederic-Emmanuel wrote:
Well, git-debrebase does, and is as compliant with DEP-14 as you'd like
it to be.
>>>
>>> There is gbp pq, which is probably more widely used.
>>
>> Right. Both are good.
>
> In fact my question was more.
>
> I wo
On 2025-05-14 12:29, Simon Josefsson wrote:
Indeed this is a mess. (I wouldn't count d/control Vcs-* though?)
d/control has Homepage as well.
Has there been any work towards a single-file declarative file syntax to
generate all the debian/ files?
Yes, there was such an effort advocated by
On Wed, 14 May 2025 at 09:47:18 +0100, Sean Whitton wrote:
On Wed 14 May 2025 at 10:41am +02, PICCA Frederic-Emmanuel wrote:
So where do we put the upstream git URL
If I read this part of DEP-14, I have the information that the remote should
be named 'upstreamvcs' but nothing about where to put
Hi,
On 14 May 2025 09:29:23 UTC, Simon Josefsson wrote:
>PICCA Frederic-Emmanuel
>writes:
>
>>> There is the Source field in d/copyright where you can put a git remote
>>> URL. Maybe that usage should go into DEP-14 ?
>>
>> So we have upstream informations in
>>
>> d/copyright
>> d/control (git
>>> Well, git-debrebase does, and is as compliant with DEP-14 as you'd like
>>> it to be.
>>
>> There is gbp pq, which is probably more widely used.
>
> Right. Both are good.
In fact my question was more.
I would like, something like
dgit clone
or
gbp clone
and get a a DEP-14 organized re
> There is the Source field in d/copyright where you can put a git remote
> URL. Maybe that usage should go into DEP-14 ?
So we have upstream informations in
d/copyright
d/control (git url of our VCS).
d/watch (in git mode)
d/upstream/metadata (what for ?). maybe we should standardize on this on
PICCA Frederic-Emmanuel
writes:
>> There is the Source field in d/copyright where you can put a git remote
>> URL. Maybe that usage should go into DEP-14 ?
>
> So we have upstream informations in
>
> d/copyright
> d/control (git url of our VCS).
> d/watch (in git mode)
> d/upstream/metadata (wha
Hello Debian Developer Team,
First of all, thank you for your amazing work and dedication to the Debian
project. As a Debian user and supporter, I would like to kindly ask a small
question.
Is there any planned or ongoing development for official Debian 12
(Bookworm) support for Raspberry Pi 5 ha
Hello,
On Wed 14 May 2025 at 11:29am +02, Simon Josefsson wrote:
> PICCA Frederic-Emmanuel
> writes:
>
>>> There is the Source field in d/copyright where you can put a git remote
>>> URL. Maybe that usage should go into DEP-14 ?
>>
>> So we have upstream informations in
>>
>> d/copyright
>> d/c
On 11/05/25 at 22:36 +0200, Lucas Nussbaum wrote:
> On 09/05/25 at 12:43 +0200, Lucas Nussbaum wrote:
> > I would love to see data about the actual acceptance of DEP-14 among
> > packages in the archive: my feeling is that it is currently being a bit
> > ignored by maintainers and teams (but maybe
On Wed, May 14, 2025 at 09:30:25AM +0200, Simon Josefsson wrote:
> Are there any guarantees on semantics for package removals? Will the
> user/group be removed from /etc/{passwd,group} or not? Will it remove
> the home directory? What happens if the home directory is not empty?
> Will it remove
Holger Levsen writes:
> On Wed, May 14, 2025 at 09:30:25AM +0200, Simon Josefsson wrote:
>> Are there any guarantees on semantics for package removals? Will the
>> user/group be removed from /etc/{passwd,group} or not? Will it remove
>> the home directory? What happens if the home directory is
Le Wed, May 14, 2025 at 10:59:48AM +0200, PICCA Frederic-Emmanuel a écrit :
>
> d/upstream/metadata (what for ?)
Hi!
When I created debian/upstream.metadata I intended that would contain metadata
that is not required for package building and that can change or grow
independently of the source co
On Wed, 14 May 2025 13:58:59 +0300, Odephus
wrote:
>First of all, thank you for your amazing work and dedication to the Debian
>project. As a Debian user and supporter, I would like to kindly ask a small
>question.
Your help is appreciated.
>Is there any planned or ongoing development for offici
On Wed, 14 May 2025 07:50:06 +, Holger Levsen
wrote:
>To quote Russ once again: 'I think Policy should say something like
>"created users and groups should not be removed by default, but may be
>removed on purge if the local administrator explicitly requests this, either
>for that package or
Hi Odephus,
[ cc-ing the historical pkg-raspi-maintainers@ list ]
Odephus (2025-05-14):
> Is there any planned or ongoing development for official Debian 12
> (Bookworm) support for Raspberry Pi 5 hardware? If there is a roadmap
> or an expected release date, I would be very grateful if you coul
Andrea Pappacoda writes:
> Hi Ahmad,
>
> Il 13 maggio 2025 00:30:09 CEST, Ahmad Khalifa ha scritto:
>> Relatively new perhaps. Needs a little fiddling to work with debhelper
>> compat level 13 (needs dh helper called from d/rules).
>
> You might want to build-depend on dh-sequence-sysusers inst
On Tue, May 06, 2025 at 08:48:29AM +0200, Lucas Nussbaum wrote:
> On 05/05/25 at 22:14 +0200, Santiago Vila wrote:
> > In some cases, the bug is already known, because debian/rules
> > has --max-parallel=1. Example: The alpine package.
> >
> > (I wonder how much feasible would be to skip those pac
Hi,
On 14/05/25 at 13:50 +0300, Adrian Bunk wrote:
> On Tue, May 06, 2025 at 08:48:29AM +0200, Lucas Nussbaum wrote:
> > On 05/05/25 at 22:14 +0200, Santiago Vila wrote:
> > > In some cases, the bug is already known, because debian/rules
> > > has --max-parallel=1. Example: The alpine package.
> >
On 14/05/2025 10:33, Andrius Merkys wrote:
Yes, there was such an effort advocated by one person, but I cannot
recall any details about it to help locating it.
Best,
Andrius
Was that debputy?
https://salsa.debian.org/debian/debputy
Regards,
Peter
On Wed, May 14, 2025 at 12:33:49PM +0300, Andrius Merkys wrote:
On 2025-05-14 12:29, Simon Josefsson wrote:
Indeed this is a mess. (I wouldn't count d/control Vcs-* though?)
d/control has Homepage as well.
Has there been any work towards a single-file declarative file syntax to
generate all
> debian/upstream/metadata, Repository field.
>
> For example try `gbp clone --add-upstream-vcs vcsgit:sdl2-compat` which
> uses this field. To make `gbp clone` do this automatically whenever this
> information is available, you can write
>
> [DEFAULT]
> add-upstream-vcs = True
>
> into ~/.gbp.c
On May 13, Guillem Jover wrote:
systemd's sysuser support is only apparently slightly better than
adduser (in that it is declarative), otherwise it feels rather
underwhelming in the package management context. It does not solve being
able to use such users in .deb files w/o maintainer scripts,
El 14/5/25 a las 12:50, Adrian Bunk escribió:
What is a maintainer supposed to do when the package already does
"dh --no-parallel" and the upstream Makefiles are basically unfixable?
Whether a Makefile is unfixable or not is subjective. Everything depends
on the amount of time that one is willi
28 matches
Mail list logo
