patch from release 0.7.00-1.
+Fixes FTBFS bug. Closes: #1070757.
+
+ -- Santiago Vila Wed, 08 May 2024 16:40:00 +0200
+
bart-cuda (0.6.00-1) unstable; urgency=medium
* Initial upload of this cuda enabled bart version
diff -Nru bart-cuda-0.6.00/debian/patches/0005-relax-failing-unit-test.p
Package: src:bart-cuda
Version: 0.6.00-1
Severity: serious
Tags: ftbfs patch
Control: fixed -1 0.8.00-2
Control: owner -1 sanv...@debian.org
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
-0.6.00/debian/changelog2024-05-07 23:05:00.0 +0200
@@ -1,3 +1,11 @@
+bart (0.6.00-3+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * Cherry-pick 0004-relax-failing-unit-test.patch from
+release 0.7.00-1. Fixes FTBFS bug. Closes: #1026061.
+
+ -- Santiago Vila Tue, 07
El 7/5/24 a las 18:50, Uecker, Martin escribió:
Am Dienstag, dem 07.05.2024 um 17:59 +0200 schrieb Santiago Vila:
El 1/1/23 a las 16:55, Uecker, Martin escribió:
In the meantime, I became member of debian-med, so in theory,
I could fix this myself via team upload. Would you prefer
that I take
El 1/1/23 a las 16:55, Uecker, Martin escribió:
I can apply the patch, but I do not have much time now.
Is there some urgency?
Hello. A lot of time passed without activity on this bug.
In the meantime, I became member of debian-med, so in theory,
I could fix this myself via team upload. Would
Hi.
They finally enabled my account in gnome's gitlab and I have now offered them
hardware to reproduce it, if they need it.
Thanks.
El 7/5/24 a las 11:46, Thomas Goirand escribió:
Bug #1029657 in python-os-ken reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
would you also offer such a VM to gcr4 upstream?
Yes.
(Or just tell them that it fails 100% of the time on AWS
instances of type m6a.large and r6a.large, which are the
ones I tried).
(btw: I tried registering myself to gnome's gitlab right now,
but did not receive confirmation email, hope
Hello.
My plan for base-files is to stop overriding the PATH in /etc/profile.
Ubuntu did that a long time ago and it's probably the right thing to do.
I'd like to do this for trixie, but only after the t64 transition is finished
and the usr-merge patch from Helmut Grohne is implemented.
Also,
Package: src:mixxx
Version: 2.4.0+dfsg-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
--- LOG END ---
error:
Package: src:translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:uhttpmock0
Version: 0.5.5-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:psortb
Version: 3.0.6+dfsg-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:gxneur
Version: 0.20.0-2.2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with
Package: src:crystal
Version: 1.11.2+dfsg-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:ayatana-indicator-display
Version: 24.1.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh
retitle 1069357 cpp-httplib: FTBFS: Test SSLClientServerTest.ClientCertPresent
fails with timeout
thanks
El 26/4/24 a las 6:59, Julian Gilbey escribió:
It looks like it's just that arm64 is slow (as are several other archs).
Note: I can reproduce this on amd64 as well (using m6a.large
found 1064486 0.16.3-1
tags 1064486 + ftbfs bookworm trixie sid
thanks
El 20/4/24 a las 14:12, Andreas Metzler escribió:
FWIW I also get testsuite errors on current sid on amd64
The following tests FAILED:
83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed)
90 -
Package: src:pistache
Version: 0.0.5+ds-3
Severity: serious
Tags: bookworm ftbfs
Control: fixed -1 0.0.5+ds-4
Dear maintainer:
Please disable network tests in bookworm as well, as they have started to fail
even when network access is allowed during build:
[ RUN ] net_test.address_creation
El 4/5/24 a las 16:48, ca...@allfreemail.net escribió:
Package: base-files
Version: 13.2
Followup-For: Bug #885414
Dear Maintainer,
I'd like to point out that the "fix" doesn't actually fix the reported
problem. Variables that must be quoted in order to have a well-defined
behavior are still
Hi.
Since the t64 transition has not finished completely yet (and also
I'd like the dust to settle a little bit after it finish), I've made
another release with minor changes.
The rebased branch is now wip-20240504-usrmerge.
I've also created a rebased branch with changelog called
El 27/2/21 a las 9:48, g1 escribió:
Package: base-files
Version: 10.3+deb10u8
Severity: normal
In /usr/share/base-files/dot.bashrc (which is copied to /root/.bashrc
at package installation) the umask command is commented out, with this
explanation:
# Note: PS1 and umask are already set in
[ Replying to both ]
Richard Lewis wrote:
On Thu, 18 Apr 2024, 23:18 Santiago Vila, mailto:sanv...@debian.org>> wrote:
(I'd like to avoid spamming the users with non-important information)
[...]
- NEWS.Debian is "opt-in": if you install apt-listchanges you'll
El 20/4/24 a las 20:40, Guillem Jover escribió:
Hi!
On Mon, 2024-04-15 at 13:15:13 +0200, Santiago Vila wrote:
Hi. I'm scared about removing /etc/profile by accident.
Guillem: I see that dpkg contains some helper programs to remove
"obsolete conffiles".
Are they meant
# Fail the build if the tzdata package does not match TZVER.
grep -q '^# version 2023d$' /usr/share/zoneinfo/tzdata.zi
Yes, this is expected after each update to tzdata.
I'm curious: Does this package embed the information from tzdata into
javascript code,
in such a way that a change in
found 1051924 2.21.3+deb11u1
tags 1051924 + bullseye
thanks
Hello. The version in bullseye also fails in test test/test_debchange.
Thanks.
Sorry, I forgot to Cc the bug address. I wrote the rationale for the reassign
here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459664;msg=34#34
Also, please note that the following two addresses do not work anymore:
Joey Hess
Justin Pryzby
(In case you want to avoid bounces)
Package: src:toil
Version: 6.1.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:prometheus-process-exporter
Version: 0.7.10-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh
I have commented out a pair of test cases which attempted network access in the
upload of node-wikibase-cli 15.15.4-5. Could you please check whether FTBFS
continues?
Hello. Yes, it continues to fail.
You can tell by looking at the reproducible-builds page for the package:
El 17/10/22 a las 14:04, Michael Biebl escribió:
Source: networking-mlnx
Version: 1:16.0.0-3
Severity: serious
Tags: ftbfs
networking-mlnx FTBFS in unstable
It appears to be trigger lots of test suite failures and is killed
eventually
I think it's even worse than that: The test suite seems
Package: src:node-bunyan
Version: 2.0.5+~cs4.4.3-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
found 1069842 4.4.0-1
affects 1069842 + src:rjava
thanks
Thanks for the quick reply!
[ I'm adding the affects so that the bug is shown on the web page
for src:rjava. This helps to avoid duplicates, as there are more people
reporting FTBFS bugs ]
Thanks.
Package: src:python-icalendar
Version: 5.0.11-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:zarr
Version: 2.17.2+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:rjava
Version: 1.0-11-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --buildsystem R
Package: src:khard
Version: 0.19.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with python3
Package: src:libcommons-fileupload-java
Version: 1.5-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh
Package: src:maven-dependency-analyzer
Version: 1.13.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh
severity 1065660 serious
tags 1065660 + ftbfs
thanks
Hello.
I noticed that chemicaltagger currently FTBFS and I believe it is because
of this problem, so to avoid duplicate reports, I'm raising this one to serious.
A build log for chemicaltagger is available here:
Package: src:golang-github-aydinnyunus-blockchain
Version: 0.0~git20220623.647ebea-1
Severity: serious
Tags: ftbfs
Dear maintainer:
This package tries network access during build:
= TESTING ADDRESSES =
El 25/4/24 a las 7:15, Otto Kekäläinen escribió:
Bullseye oldstable update request filed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069802
You can +1 it if you want to show support.
Thanks a lot! We don't +1 because this is not twitter/facebook :-)
but I have just made a comment to
Dear Release Managers:
Since I reported bug #1053334, I'd like to emphasize on this item:
* New upstream release includes multiple Debian build and post-build test
failure fixes:
- Generate keys and certificates for SSL tests (Closes: #1053334)
This is a FTBFS bug due to
Jeremy Bícha wrote:
It was also marked as severity important instead of RC because it does not
affect official buildds.
Not true:
https://buildd.debian.org/status/logs.php?pkg=libsoup2.4=all
See also:
https://buildd.debian.org/status/logs.php?pkg=gcr=all
and also:
retitle 1069415 libsoup2.4: FTBFS: failing tests
thanks
El 24/4/24 a las 18:26, Andreas Metzler escribió:
On 2024-04-20 Lucas Nussbaum wrote:
Source: libsoup2.4
Version: 2.74.3-7
Severity: serious
Justification: FTBFS
[...]
(hsts-test:547071): GLib-Net-WARNING **: 04:03:06.247: Failed to
Package: lists.debian.org
Dear Debian listmasters:
Many people report that messages sent to certain n...@bugs.debian.org
addresses receive automatic replies from Apple Support China.
Apparently it does not happen with every bug report, but only with
those which are RC, which suggests that
I've updated my demo repository with your patch.
https://salsa.debian.org/helmutg/bootstrap-usrmerge-demo/-/commit/6425c8cde53596199cd37bb1625d1dfb2a4b74d0
Great. I'll take a look.
I'm happy to call it guest upload while I find team upload slightly
misleading.
I avoid patching changelogs in
El 22/4/24 a las 8:47, Otto Kekäläinen escribió:
I was able to reproduce this for Bookworm both locally and in CI at
https://salsa.debian.org/mariadb-team/galera-4/-/jobs/5620032
After importing latest upstream build/test passes:
https://salsa.debian.org/otto/galera/-/jobs/5624466
Stable
El 15/4/24 a las 22:26, Bill Allombert escribió:
On Tue, Jan 30, 2024 at 09:52:39AM +, MOESSBAUER, Felix wrote:
On Fri, 04 Aug 2023 10:44:38 + sohe4b+2fz7rb0ixc53g@cs.email wrote:
Package: base-files
Version: 12.4+deb12u1
Followup-For: Bug #1039979
Control: tags -1 patch
I attach a
El 25/3/24 a las 20:12, Chris Lamb escribió:
Alberto Bertogli wrote:
If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.
Alas, I can't actually be helpful here.
Hi.
I've added two commits, one to create symlinks with a "shell" for, and the last
one for a sample changelog (because this is really a "team upload" or a "guest
upload"
more than a NMU). I think for simplicity it's ok if you skip the changelog part
in your repo.
Thanks.
El 17/4/24 a las 20:07, Helmut Grohne escribió:
Please let me know when you did your editorial changes such that I can
replace my patch with yours and retest.
I did those minor changes in the branch wip-202404-usrmerge, just after your
patch.
(If you adopt those changes, I'll rewrite the
I saw in #604918 that /etc/profile is deliberately not treated as a
conffile. Is there any way to get the new version installed on package
upgrade, other than an external configuration management system such
as Ansible?
The way /etc/profile is handled changed slightly in version 6.10,
one year
tags 1012690 + patch
thanks
Hello Víctor.
I believe the attached patch will be enough to fix the build failure
(but you might want to update other things as well).
I would gladly be your sponsor if you still need it.
Thanks.diff --git a/debian/control b/debian/control
index 0e9a667..9b33160
El 19/4/24 a las 11:30, Dave Holland escribió:
Package: base-files
Version: 12.4+deb12u5
The fragment in /etc/profile (copied from
/usr/share/base-files/profile) does not enforce a particular locale
when generating the list of /etc/profile.d/*.sh files to load. This
means that the ordering of
Package: src:sendfile
Version: 2.1b.20080616-10
Dear maintainer:
The file /etc/profile.d/sendfile does not have .sh suffix,
so it's not sourced by /etc/profile at all.
I noticed this because I'm planning to improve the way
files at /etc/profile.d are read (see Bug#885414).
The plan is to use
El 18/4/24 a las 22:17, Richard Lewis escribió:
'^[a-zA-Z0-9_][a-zA-Z0-9._-]*\.sh$'
Hi. I confirm that this is appropriate for what we distribute:
What about local scripts added by users (which this change might
prevent loading): perhaps a NEWS.Debian entry would suffice?
Are there any
tags 885414 - help
thanks
Vincent Lefevre wrote:
'^[a-zA-Z0-9_][a-zA-Z0-9._-]*\.sh$'
Hi. I confirm that this is appropriate for what we distribute:
wget -q -O - http://deb.debian.org/debian/dists/unstable/main/Contents-amd64.gz
| gzip -d | awk '/etc\/profile.d/ { print $1 }'
yields:
So I think that the --regex argument should be
'^[a-zA-Z0-9_][a-zA-Z0-9._-]*\.sh$'
Thanks a lot! Yes, this is the kind of feedback I need.
Next I'd like to match such regexp with the files in /etc/profile.d
that may be obtained from the Contents.gz file in the archives to
be sure that the
severity 964941 normal
thanks
Hi.
I'm going to answer to all three here.
El 13/7/20 a las 4:30, Paul Wise escribió:
Source: base-files
Severity: wishlist
It would be great if you could maintain base-files in a VCS such as git
on salsa.d.o. If you would like to do that, please import the
This is actually explained in the last question here:
/usr/share/doc/base-files/FAQ
Isn't that quite unfortunate?
It leaves out any legacy installations (and many people never re-
install Debian, but just continuously upgrade it).
I mean I can fully understand if it's to fragile to
El 17/4/24 a las 23:16, Christoph Anton Mitterer escribió:
Hey.
FYI: I have upgraded to 13.1, but still didn't get a
/usr/local/libexec.
Guess that's because $2 in the script is not empty?
Yes. An empty $2 means that the package is installed for the
very first time, i.e. installed by
tags 885414 + help
thanks
Hello. Sorry for the late reply.
The problem, more than lack of quoting, is that there is no specification
anywhere about what should be allowed and what should not.
But we are not late to begin such specification.
Here is my current plan:
--- a/share/profile
+++
El 28/2/24 a las 21:19, Helmut Grohne escribió:
Niels Thykier made me aware of dh_installdeb -D. Using it avoids the
need for a pile of .in files in base-files. I hope you like this
refactoring. Let me know if not.
Nice feature indeed. To simplify the usr-merge patch, I've adopted
the -D
Package: openstack-dashboard
Version: 3:24.0.0-2
Affects: src:designate-dashboard
Severity: serious
Justification: Breaks other packages
Dear maintainer:
During an incremental rebuild of all packages in trixie, package
"designate-dashboard"
failed to build due to a postinst error in
Package: src:lua-mode
Version: 20210802-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with elpa
Package: src:totalopenstation
Version: 0.5.2-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with
reassign 1039979 debian-policy
thanks
Dear Policy editors:
In this bug I'm asked to make /var/run and /var/lock symlinks
to be relative.
Maybe it's the right thing to do, but last time I tried to do that,
this is what happened:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690345
[
found 1069059 239-1
found 1069059 287-1
tags 1069059 + bullseye bookworm
thanks
El 15/4/24 a las 19:28, Salvatore Bonaccorso escribió:
The update for cockpit in DSA 5655-1 had problems with the
test-sshbridge test, causing FTBFS:
For completeness: this was already happening in bullseye and
reassign 833319 adwaita-icon-theme
thanks
I don't think this is appropriate for base-files. Reassigning back.
Please find another package (not base-files) for that.
Thanks.
reassign 1055583 debian-installer
thanks
Dear debian-installer people:
In this bug report, I'm asked to provide /efi as a mount point for the EFI
partition.
Given that base-files does not even contain /boot/efi (the supposedly "old"
location),
I believe this is a decision for you to make,
btw: /var/local is still :staff owned ... while /usr/local is no
longer. Is that on purpose?
Historical reasons. There was also a time in which, by default,
/usr/local was also root:staff and writeable by staff.
The /var/local thing is already reported here:
It would be nice if it could be considered to add/create:
/etc/local
/usr/local/libexec
Thanks for the report.
I'll add /usr/local/libexec as the outcome for this bug report.
According to what I read, it should exist because /usr/libexec
also exists.
/etc/local is even kinda indirectly
El 27/5/20 a las 22:43, Adam Borowski escribió:
Package: base-files
Version: 11
Severity: wishlist
Tags: patch
Hi!
It would be good if /etc/issue set the window title appropriately.
While it might sound wrong (as /etc/issue is used only for local terminals),
serial consoles do count as local.
severity 931197 normal
thanks
I consider this to be a normal bug, and will try to discuss with Release
Managers
to see if we can change it for trixie.
Thanks.
Hi. I'm scared about removing /etc/profile by accident.
Guillem: I see that dpkg contains some helper programs to remove "obsolete
conffiles".
Are they meant to be used for conffiles which should no longer exist, or also
for
conffiles which are no longer conffiles but should continue to
Hi. Let's see what we should do to remove PATH from /etc/profile.
Ubuntu did that a lot of time ago and this is their changelog:
base-files (3.1.9ubuntu3) dapper; urgency=low
* Implement OneTruePathSpec:
* share/profile: Remove PATH setting.
* debian/control: Add dependency
El 14/4/24 a las 13:25, Sylvestre Ledru escribió:
I am sorry but I am not sure to see how it is actionable.
Without a test case, i don't think there is much I can do here.
The test case is that nvda2speechd fails to build from source.
With rust, cargo, custom build script, there are many
Package: src:debootstrap
Version: 1.0.128+nmu2+deb12u1
Dear maintainer:
Please make debootstrap in bookworm to follow the same rules as debootstrap in
trixie/sid
when creating a buildd chroot of trixie/sid (i.e. install only build-essential
packages).
Rationale and full explanation here:
Package: src:python-musicpd
Version: 0.8.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with
Package: src:circe
Version: 2.12-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with elpa
Package: src:moment-timezone.js
Version: 0.5.32+dfsg1-2+2021a
Severity: serious
Tags: bullseye bookworm trixie sid ftbfs
Dear maintainer:
This package currently fails to build from source in all supported
distributions.
make[1]: Leaving directory '/<>'
dh_clean
debian/rules binary
dh
) bookworm; urgency=medium
+
+ * Team upload.
+ * debian/rules: Add --no-parallel to avoid the effects of a Makefile bug
which
+makes the package to FTBFS randomly. Closes: #1068341.
+
+ -- Santiago Vila Mon, 08 Apr 2024 19:40:00 +0200
+
bioawk (1.0-4) unstable; urgency=medium
* d/p
Just for the record: I finally used this, in line with the original proposal:
Replaces: dialog (<< 1.3-20240307-1~)
Breaks: dialog (<< 1.3-20240307-1~)
Thanks.
Ok. This is a little bit subtle.
I naively tried to simplify the fields by using this:
Replaces: dialog (<< 1.3-20240307)
Breaks: dialog (<< 1.3-20240307)
But this actually means upstream version 1.3, debian revision 20240307,
not upstream 1.3-20240307.
I guess I should use 1.3-20240307-0 at
El 8/4/24 a las 9:18, Helmut Grohne escribió:
Package: libdialog-dev
Version: 1.3-20240307-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + dialog
libdialog-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.
The
tags 1024532 - moreinfo
close 1024532 1.79.3-1
thanks
I can verify that the version currently in trixie does not show this
behaviour anymore (maximum allocated memory is now below 1 GB).
Therefore I'm closing this bug myself.
(It would have been interesting maybe to know in which version it
Hi. I have made the upload.
But now I remember that this may get rejected for requiring
new binary packages (not sure if this has changed since the last
time), so wish me luck...
Thanks a lot for all the help!
El 6/4/24 a las 20:53, Sven Joachim escribió:
1. https://www.debian.org/doc/debian-policy/ch-relationships.html#id11
Ok, I had not read that part of Policy in a long time.
One minor last thing:
Assuming I make the changes and package the new available
upstream version at the same time, can I
Patch attached, I have tested that it builds on amd64 and i386. looked
at the generated Dependencies and verified that lintian does not go
crazy, but that's it. Note that I had to add libtool-bin rather than
just libtool to Build-Depends to prevent configure from complaining, and
also pacify
forwarded 1060939 https://github.com/workalendar/workalendar/issues/764
tags 1060939 + bookworm
thanks
Package: src:golang-github-antonini-golibjpegturbo
Version: 0.0~git20141208.c03a2fa-2
Severity: serious
Tags: ftbfs
[...]
github.com/antonini/golibjpegturbo
dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 20
El 23/12/23 a las 3:07, Otto Kekäläinen escribió:
Sure, this will be fixed (automatically) with uploading latest upstream minor
release as stable update, and I intend to do it in coming 1-2 weeks.
Hi. Can you elaborate on that? Release managers do not usually allow
new upstream releases in
El 4/4/24 a las 19:44, Johannes Schauer Marin Rodrigues escribió:
instead of doing that, you could've worked around this by just placing the
build log into a dedicated temporary directory and then copying it to where you
want it after the build is finished.
That would be an option, yes, but
El 4/4/24 a las 19:29, Johannes Schauer Marin Rodrigues escribió:
Also I'm curious: what is your motivation for using unshare mode if you are
creating your chroots using superuser privileges?
And are you really storing your chroots in /srv instead of letting them get
picked up automatically in
Nilesh: Would it help if I do a "team upload" to fix this?
(Using the proposed patch)
Or would you prefer to fix it yourself?
Just go ahead with a fix. I don't have much time these days. Please also drop
me from uploaders field for this package won't have time to maintain this.
Yes, I
El 4/4/24 a las 14:22, Johannes Schauer Marin Rodrigues escribió:
Since I don't think a tarball without ./ is really "wrong" to the point
that it needs to be recreated (this is in fact the very first in my life
that a tarball without ./ causes any kind of trouble), I think it would be
desirable
El 4/4/24 a las 14:07, Johannes Schauer Marin Rodrigues escribió:
well this is an old bug. How have you worked around it being open for the past
six years?
This is important for me, so I'm still patching my own sbuild version.
Yes, every single time.
Quoting Santiago Vila (2024-04-04 12:57
the filename that I want to use
for the build log.
[ If the environment variable name is not good enough, just use one
which makes sense. I will gladly adapt my scripts ]
Thanks.commit 36f4e780f4a6de6a1ebceaa4fcd6bc53fe952fcb
Author: Santiago Vila
Date: Thu Apr 4 12:30:00 2024 +0200
lib/Sbuild
d) supports tarballs with or
without ./ and at the same time simplifies the exclude
patterns to just two.
Thanks.commit d54e3303e4a212a790f736b2b9db072c6fe7b25e
Author: Santiago Vila
Date: Thu Apr 4 11:30:00 2024 +0200
lib/Sbuild/ChrootUnshare.pm:
Use tar's --anchored option to suppor
301 - 400 of 6104 matches
Mail list logo
