Hi all fellow Debian developers,
Duplicated work is silly and learning you've done it feels frustrating,
so let's try avoid that by a) communicating when initiating a work and
b) checking first if others have already begun same work.
For Debian packages, we have since long established a method to
Hi Andrey,
> On 6 Sep 2022, at 12:42, Andrey Rahmatullin wrote:
>
> On Tue, Sep 06, 2022 at 12:11:38PM +0300, Hakan Bayındır wrote:
>> While all looks good and feels sound from many aspects, I have some
>> reservations against treating changelogs as metadata.
>>
>> Current changelogs as files h
Hi,
in 2016 we filed our first DPKG_ROOT patch #824594 against base-files. The dpkg
version at the time just had included support for the DPKG_ROOT variable being
set for maintainer scripts and we were excited to try out this new feature for
creating foreign architecture chroots. At the time we th
On Sun, Sep 11, 2022 at 02:41:24PM +0300, Hakan Bayındır wrote:
> > On Tue, Sep 06, 2022 at 12:11:38PM +0300, Hakan Bayındır wrote:
> >> While all looks good and feels sound from many aspects, I have some
> >> reservations against treating changelogs as metadata.
> >>
> >> Current changelogs as fi
> On 11 Sep 2022, at 14:59, Andrey Rahmatullin wrote:
>
> On Sun, Sep 11, 2022 at 02:41:24PM +0300, Hakan Bayındır wrote:
>>> On Tue, Sep 06, 2022 at 12:11:38PM +0300, Hakan Bayındır wrote:
While all looks good and feels sound from many aspects, I have some
reservations against treat
On Sun, Sep 11, 2022 at 03:09:07PM +0300, Hakan Bayındır wrote:
> Stuffing them behind a command, possibly making them online only in the
> process will arguably make system troubleshooting and administration
> harder,
> esp. if the system has connectivity issues.
>
> >>>
Johannes Schauer Marin Rodrigues wrote:
> What do you think? Is this the right solution to the problem? A few more bits
> about DPKG_ROOT as well as alternative solution proposals (including rejected
> ones) can be found on this wiki page:
>
> https://wiki.debian.org/Teams/Dpkg/Spec/InstallBootstr
Hi,
Quoting Josh Triplett (2022-09-11 15:26:52)
> Johannes Schauer Marin Rodrigues wrote:
> > What do you think? Is this the right solution to the problem? A few more
> > bits
> > about DPKG_ROOT as well as alternative solution proposals (including
> > rejected
> > ones) can be found on this wik
Hello,
We have been discussing a bit on #debian-ports about packages that fail
to build on less-mainstream architectures.
The issue we see is that some DDs end up setting a hardcoded list in
the "Architecture" field, rather than just letting builds keep failing
on these archs (and then possibly s
* Ansgar [220910 09:37]:
> the transition to usrmerge as described in [1] is planned to start
> around 2022-09-15 (next Thursday).
[snip]
> We will send an announcement to debian-devel-announce@ once the upload
> to unstable happens.
What is the point in waiting until after the upload to send to
Package: wnpp
Severity: wishlist
Owner: ChangZhuo Chen (陳昌倬)
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: golang-github-bsm-go-vlq
Version : 0.0~git20150828.ec6e8d4
Upstream Author : Dimitrij Denissenko
* URL : https://github.com/bsm/go-vlq
* License
Hi Samuel,
On 11-09-2022 17:08, Samuel Thibault wrote:
We could for instance:
- Add an Architecture-FTBFS field to debian/control
- Add an environment variable to debian/rules so that on these archs dh
fails with a different exit code that buildds would notice.
- Add a Architecture-FTBFS fiel
Paul Gevers, le dim. 11 sept. 2022 21:16:08 +0200, a ecrit:
> On 11-09-2022 17:08, Samuel Thibault wrote:
> > We could for instance:
> > - Add an Architecture-FTBFS field to debian/control
> > - Add an environment variable to debian/rules so that on these archs dh
> >fails with a different exit
On Sun, Sep 11, 2022 at 09:25:40PM +0200, Samuel Thibault wrote:
> Paul Gevers, le dim. 11 sept. 2022 21:16:08 +0200, a ecrit:
> >
> > - color packages that "never" had a successful built on an architecture
> > different. That information is already available because that's what marks
> > the pack
On Sun, Sep 11, 2022 at 05:08:57PM +0200, Samuel Thibault wrote:
>...
> The issue we see is that some DDs end up setting a hardcoded list in
> the "Architecture" field, rather than just letting builds keep failing
> on these archs (and then possibly succeeding after some time whenever
> somebody co
Hi,
Am 11.09.22 um 22:07 schrieb Adrian Bunk:
On Sun, Sep 11, 2022 at 05:08:57PM +0200, Samuel Thibault wrote:
...
The issue we see is that some DDs end up setting a hardcoded list in
the "Architecture" field, rather than just letting builds keep failing
on these archs (and then possibly succe
On Sun, 2022-09-11 at 23:07 +0300, Adrian Bunk wrote:
> Architecture lists containing all 64bit ports or all little endian
> ports create much extra work for anyone adding support for a new
> 64bit little endian architecture.
Since dpkg already knows about the bits and endianness of ports,
perhap
On Sun, 11 Sep 2022 11:08:44 -0400, Marvin Renich
wrote:
>* Ansgar [220910 09:37]:
>> the transition to usrmerge as described in [1] is planned to start
>> around 2022-09-15 (next Thursday).
>[snip]
>> We will send an announcement to debian-devel-announce@ once the upload
>> to unstable happens.
18 matches
Mail list logo
