Package: src:arduino-builder
Version: 1.3.25-2
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary-arch
dh bin
El 29/12/22 a las 11:24, Lajos Veres escribió:
Does this fail frequently for you?
Hi.
Building the package on Hetzner cloud machines of type cx21 and cx31
(having 2 CPUs) fails for me approximately 50% of the time in bookworm.
I also tried with machines with only one CPU, but then it does not
Hello. I was going to report this but I see it's already reported.
Here is another false positive:
lintian believes that the file testdir/t.a in original-awk
source is an ar archive and produces this output:
E: original-awk source: unpack-message-for-orig
original-awk_2022-01-22.orig.tar.gz .
El 27/12/22 a las 18:16, Bernhard Schmidt escribió:
Source: bind-dyndb-ldap
Version: 11.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: team+...@tracker.debian.org
bind-dyndb-ldap has a tight dependency on the upstre
reopen 1025096
found 1025096 4.11.23-1
fixed 1025096 4.12.14-1
thanks
Please consider fixing this in stable as well.
I attach a proposal for a 4.11.23-1+deb11u1 version,
which is just a backport of the fix applied in 4.12.14-1.
Thanks.diff -Nru nanoc-4.11.23/debian/changelog nanoc-4.11.23/debia
Package: src:hello
Version: 2.10-2
Severity: wishlist
This is to let everyone know that I'm aware that there
is a new hello (2.12.1) available here:
https://ftp.gnu.org/gnu/hello/
El 26/12/22 a las 17:30, Raphael Hertzog escribió:
Hello,
On Fri, 23 Dec 2022, Santiago Vila wrote:
For example, this one:
I have just imported version 2.10-2. Now dpkg-buildpackage
does not work because it expects some timestamps to be the ones in the
orig.tar.gz where upstream maintainer
Hi. I'm working on this now.
After considering available options, I'm going to host it under my
"sanvila" namespace for now.
My work in progress is here:
https://salsa.debian.org/sanvila/hello-alpha
But there are some technical and philosophical issues unsolved yet.
For example, this one:
I
found 1010120 0.13.0-6
thanks
reopen 1011863
found 1011863 1.2.0-4
fixed 1011863 1.3.0-5
retitle 1011863 guix: FTBFS in bullseye because of expired certificates used in
tests
tags 1011863 + patch
thanks
Hello.
Reopening because packages in bullseye must build in bullseye.
I attach an upload proposal for bullseye, it's just
Dear maintainers:
This package FTBFS for me on bullseye, tried several times on different
machines.
(I'm attaching a build log)
I think it is the same bug reported by Lucas back in October 2021 (i.e. this
one),
which was fixed only in bookworm.
Unfortunately, I'm not 100% sure, because I trie
El 22/12/22 a las 9:20, Helmut Grohne escribió:
I don't think having me test your branches is an efficient process. Can
I propose the following alternatives?
* If you are using sbuild, add --host=somearch.
* If you are using pbuilder, add --host-arch somearch.
* If you are using salsa, ena
El 23/2/19 a las 7:29, Helmut Grohne escribió:
Source: original-awk
Version: 2012-12-20-6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
original-awk fails to cross build from source, because the packaging
forces the build architecture compiler "gcc". Using a triplet-prefixed
compile
Package: devscripts
Version: 2.22.2
Dear maintainers:
When I run uscan using a watch file like this:
version=4
https://ftp.gnu.org/gnu/hello hello-(.*).tar.gz
I see this:
uscan: => Newer package available from:
=> https://ftp.gnu.org/gnu/hello-2.12.1.tar.gz
But this URL is really wr
Sorry, forgot the debdiff. Here it is.
Thanks.diff -Nru thrift-0.13.0/debian/changelog thrift-0.13.0/debian/changelog
--- thrift-0.13.0/debian/changelog 2021-02-14 19:50:04.0 +0100
+++ thrift-0.13.0/debian/changelog 2022-12-18 12:00:00.0 +0100
@@ -1,3 +1,9 @@
+thrift (0.
Hi. Please consider an upload for bullseye, as
packages in stable must build in stable.
The procedure for stable uploads is explained here:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
I attach a proposal which might help, it's a debdiff against 0.13.0-6,
the
Package: src:go-gir-generator
Version: 2.0.2-1
Severity: serious
Tags: bullseye ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
dh_auto_build -a
make -j2 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
Hi. I have a failed build for this package.
The log contains this:
=== RUN TestPollingSRVRecordsSpec/Remove_all
polling_srv_records_test.go:134:
Error Trace:
/<>/_build/src/go.mongodb.org/mongo-driver/x/mongo/driver/topology/polling_srv_records_test.go:134
El 16/12/22 a las 5:17, 张丹丹 escribió:
Hi，maintainers,
Hello. I believe you need a similar change for m4.
Please submit a bug for m4 as well.
I have added a change for m4.
Please consider it.
I meant "please submit a bug to the Debian bug system".
I don't see your bug report here:
https://bu
Package: src:ruby-webpack-rails
Version: 0.9.11+git-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules bu
Package: src:ruby-webpacker
Version: 5.4.3-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-inde
Package: src:ruby-voight-kampff
Version: 1.1.3-4
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-
Package: src:ruby-sprockets-rails
Version: 3.4.1-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binar
Package: src:ruby-sassc-rails
Version: 2.1.2-6
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-in
Package: src:ruby-rails-controller-testing
Version: 1.0.5-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/ru
Package: src:ruby-pry-rails
Version: 0.3.9-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-inde
Package: src:ruby-omniauth-rails-csrf-protection
Version: 1.0.1-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
deb
Package: src:ruby-joiner
Version: 0.6.0-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
d
Package: src:ruby-invisible-captcha
Version: 1.1.0-5
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules bin
Package: src:ruby-haml
Version: 5.2.2-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh
Package: src:ruby-globalid
Version: 0.6.0-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
Package: src:ruby-factory-bot-rails
Version: 6.2.0-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules bin
Package: src:ruby-enumerize
Version: 2.5.0-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-inde
Package: src:ruby-combustion
Version: 1.3.7-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-ind
Package: src:ruby-coffee-rails
Version: 5.0.0-3
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-in
Package: src:ruby-browser
Version: 4.2.0-3
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-indep
d
Package: src:ruby-arbre
Version: 1.4.0-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh
Package: src:ruby-ahoy-email
Version: 1.1.1-2
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-ind
Package: src:ruby-active-model-serializers
Version: 0.10.12-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/
Package: src:redmine
Version: 5.0.0-1
Severity: serious
Tags: bookworm ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh bi
El 13/12/22 a las 16:03, Bastian Germann escribió:
I guess the rule was to use a wildcard when it is possible.
You can certainly list every file but then the copyright file will be much
bigger.
Note: What I finally did was to keep the lib/* and m4/* wildcards and expand
the others.
> How di
Package: src:bart
Version: 0.6.00-3
Fixed: 0.8.00-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary-indep
dh bin
Package: lintian-brush
Version: 0.144
Dear maintainer:
Running lintian-brush on a package not having any Build-Depends at all
results in a KeyError:
Fixer 'unused-build-dependency-on-cdbs' failed to run.
Script
/usr/share/lintian-brush/fixers/unused-build-dependency-on-cdbs.py
failed with e
El 30/11/22 a las 8:54, zhangdandan escribió:
Package: diffutils
Version: 3.8-1
Severity: wishlist
Tags: patch
User: debian-de...@lists.debian.org
Usertags: loongarch64
Dear diffutils maintainers,
I have defined SIGSEGV_FAULT_STACKPOINTER for loongarch.
Please consider the patch attac
Package: src:xmltoman
Version: 0.6-1
Severity: important
Tags: ftbfs patch upstream
Dear maintainer:
During a mass rebuild of all packages in bookworm, your package failed
to build in this way:
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
dh_auto_configure -i
dh_a
Hi.
I'm looking at the proposed copyright file and found this:
gnulib-tests/h*
gnulib-tests/ioctl.c
What rule is being followed to use wildcards sometimes and sometimes
not? This is a little bit crazy. How did you generate the file?
And more important, because without this I ca
Hi.
This package now FTBFS in bookworm:
Compiling resource ./magnifier.or
Linking ./vmg
/usr/bin/ld.bfd: cannot find -lgdk-x11-2.0: No such file or directory
/usr/bin/ld.bfd: cannot find -lgtk-x11-2.0: No such file or directory
/usr/bin/ld.bfd: cannot find -lX11: No such file or directory
/usr/b
El 11/12/22 a las 16:25, Geert Stappers escribió:
I'm fine with deleting the current repo at Salsa
to make room for a repository that has more history.
Please do so. It's not only about the history but about the conventions,
there is a DEP document which recommends a layout for branches and so
reopen 991647
found 991647 1.2.3-1
retitle 991647 libisocodes: FTBFS in bullseye
thanks
Reopening because packages in stable must build in stable.
I know this removes the version tracking info that this was fixed in
1.2.4-1, but that's ok, because (after the package was removed from
instable)
reopen 997580
found 997580 1.3-2
fixed 997580 1.3-3
thanks
This is a FTBFS bug but it's still unfixed in stable.
Follows a proposal to fix it in stable. I believe it may be used "as
is". I merely took the patch from debian/patches in 1.3-3 and applied it
over the version in bullseye). I can co
reopen 991650
found 991650 4.0.2-3
fixed 991650 4.0.2-4
thanks
Hi. I attach a proposal to fix this in bullseye. I merely applied the
patch to the stable version and added a changelog entry (and tested that
it works as expected).
Thanks.diff -Nru python-django-imagekit-4.0.2/debian/changelog
reopen 1013578
found 1013578 0.5.1-2
found 1013578 0.7.1-3
fixed 1013578 0.7.1-4
thanks
Hi. Could somebody (not necessarily Martina) take care of this?
The proposed debdiff is in the previous message.
[ I'm not a big fan of NMUs, so I'm actually considering to apply to
join the team just for QA
affects 1025714 src:octave-vrml
thanks
Rafael Laboissière escribió:
The issue is caused by a bug in the dh_octave_substvar script, from the
dh-octave package. I am looking at it. More to come soon.
Great. I'm using affects so that people can see this bug in the page for
octave-vrml as well.
reopen 1013554
found 1013554 0.0~git20210309.652d3b4-1
fixed 1013554 0.0~git20210309.652d3b4-2
thanks
Hello. Please consider an upload for bullseye, as packages in stable
must build in stable.
The attached debdiff may help (I've merely applied the patch from
bookworm and added a changelog ent
Version: 0.81.2+deb11u1
El 8/12/22 a las 10:45, Johannes Schauer Marin Rodrigues escribió:
I'm not able to reproduce your problem when building src:neutron. At which
point is the build attempting to remove the sudo package?
When it was happening, it happened at the end of the package build, wh
Package: src:octave-vrml
Version: 1.0.13-7
Tags: ftbfs
Dear Maintainer:
Today I tried to build this package from source and this is what happened:
dh_missing -i -O--buildsystem=octave
dh_octave_substvar -i -O--buildsystem=octave
dh_installdeb -i -O--buildsystem=octave
dh_gencontrol
r has if_frad.h, from Ubuntu. Closes: #997222
+ - Patch: termiox removed since kernel 5.12, from ALT Linux.
+
+ -- Santiago Vila Wed, 07 Dec 2022 19:10:00 +0100
+
libexplain (1.4.D001-11) unstable; urgency=medium
* QA upload.
diff -Nru libexplain-1.4.D001/debian/patches/linux5.11.patch
libex
patch requires raising debhelper compatibility level to 13,
+which should not be a problem because debhelper 13 is in bullseye.
+
+ -- Santiago Vila Tue, 06 Dec 2022 17:50:00 +0100
+
x4d-icons (1.2-2) unstable; urgency=medium
* QA upload.
diff -Nru x4d-icons-1.2/debian/compat x4d-icons-1.
Hi.
I've just made a QA upload (1.2-5) which replaces the workaround for the
FTBFS problem by a proper fix based on the patch by Dennis Filder.
(The debhelper feature allowing this is really great)
I plan to do an upload for stable as well.
[ CC to all involved parties ]
Thanks.
Hi.
I'm considering to make an upload to fix this in bullseye.
Am I right to think that the termiox patch with the following changelog
entry is also desirable to be able to build from bullseye+recent kernel?
- Patch: termiox removed since kernel 5.12, from ALT Linux.
Thanks.
Jérôme Charaoui wrote:
> I'm not opposed to uploading it but I'm curious to know why this is
> needed now, because the next stable release is also "around the
> corner", in relative terms...
I explained that here (sorry for the mistake in the email address).
https://bugs.debian.org/cgi-bin/bugre
Hi.
I attach an upload proposal for bullseye, in debdiff format against
version 1.3.610-4 (stable version), so you can upload it "as is" if
everything else is ok.
There is a stable point release around the corner, it would be wonderful
if this could be fixed by then.
Thanks.diff -Nru core-
El 5/12/22 a las 7:46, Stéphane Glondu escribió:
Did you try the supplied patch?
Good question.
I've just checked and yes, the supplied patch works.
So, here is my proposal to fix this in bullseye (debdiff against
0.8.2-4, the stable version).
Thanks.diff -Nru mlpost-0.8.2/debian/changelog
retitle 981600 nghttp2: missing build-depends on tzdata
tags 981600 + patch
severity 981600 serious
thanks
Helmut Grohne wrote:
> An arch-only build (but not a full build) of nghttp2 seems to reliably
> fail at test util_localtime_date:
This happens because there is a missing build-dependency on
reopen 991060
found 991060 0.8.1-8
fixed 991060 0.9-1
thanks
Hi.
Please, let us fix this for stable.
I would gladly backport the fix from unstable but since the fix was
included in a new upstream release I'm in doubt about what would have to
be done and would definitely need help.
Thanks.
Version: 3.13.1+dfsg-2
El 4/12/22 a las 10:22, Andreas Tille escribió:
I admit we did not put any effort on this bug report. Since this bug is
now five years old and there are several upstreams versions released I
wonder whether this problem persists or whether we can close this bug
report.
T
Package: src:nanoc
Version: 4.11.23-1
Severity: serious
Tags: ftbfs, patch
Dear maintainer:
During a rebuild of all packages in bullseye I noticed that this package
does not build from source anymore:
1) Nanoc::Core has up-to-date version information
Failure/Error: expect(described_cla
Package: sbuild
Version: 0.81.2+deb11u1
X-Debbugs-Cc: sanv...@debian.org
Dear maintainer:
During a rebuild of all packages in bookworm I noticed that setting
SUDO_FORCE_REMOVE=yes in the environment does not seem to have any
effect anymore.
This happens, for example, when building "neutron":
Package: src:libsoup2.4
Version: 2.74.3-1
Tags: ftbfs
X-Debbugs-Cc: sanv...@debian.org,jo...@debian.org
Dear maintainer:
During a rebuild of all packages in bookworm I noticed that sbuild
(bullseye version) is unable to install the build-dependencies of
libsoup2.4:
Installing build dependenc
El 22/11/22 a las 0:40, Jeremy Bicha escribió:
On Mon, Nov 21, 2022 at 7:54 AM Santiago Vila wrote:
Not exactly. As explained, I am intentionally measuring the allocated
memory as a completely safe upper bound for the required memory, and I
am aware that they are not the same. Nevertheless, I
Hi.
I confirm that the huge memory allocation happens during the
override_dh_auto_test target of debian/rules, not during the build itself.
This is at least double the amount of *any other* of the 33785 source
packages in Debian bookworm, so yes, I think it is more than fair to
call it an an
El 22/11/22 a las 18:44, Marco Trevisan escribió:
On nov 21 2022, at 1:51 pm, Santiago Vila wrote:
I am reporting this as an anomaly (a very big anomaly indeed).
With the gjs upstream hat, I have sadly to say that this is probably
something expected: gjs eavily uses complex templates to
[ Adding 837...@bugs.debian.org and the submitter to Cc for the reasons
explained below ].
El 22/11/22 a las 13:09, Guillem Jover escribió:
So it seems to me we have a bunch of packages that are prio:required
but not Essential (some have switched to Protected:yes), that should
get their priori
El 21/11/22 a las 11:20, Simon McVittie escribió:
When I upload it, I do my test-build in a VM with 2G of RAM, and that
works fine. I'm using a bullseye VM containing bullseye's sbuild and
schroot, with gjs built in a sid chroot by that copy of sbuild. This
is intended to replicate Debian's produ
Package: src:gjs
Version: 1.74.1-1
X-Debbugs-Cc: sanv...@debian.org
Dear maintainer:
During a mass rebuild of all packages in bookworm, I noticed that gjs
allocates up to 237 GB of memory.
I measure this by monitoring Committed_AS parameter in /proc/meminfo at
every second during the build.
Hello. This is my proposal to fix the bug in stable, in debdiff format
against version 0.5.1-2, the version currently in bullseye.
Martina: Could you please take a look at it, since you were the one to
fix this in unstable?
I merely backported your patch to stable, i.e. added a Sleep call
bef
I see you have reverted, thanks a lot.
El 20/11/22 a las 20:51, Geert Stappers escribió:
Which way will it be?
The opposite of "forced" would be "voluntary" and "consensual".
I have experience with git and github, but there are a lot of things
about salsa which I would like to ask somewhere
El 20/11/22 a las 18:27, Geert Stappers escribió:
user debian-rele...@lists.debian.org
usertag 893083 + bsp-2022-11-nl-tilburg
tag 893083 + pending
thank you
Please don't. While I agree that it would be better to use git, forcing
it via NMUs is unwelcome.
Thanks for the patch. I'm going to see if I can also upgrade to 0.21.1.
If it's not easy (and I suspect it might not be), I'll just apply the
patch and defer the new version to a later upload.
El 23/9/22 a las 11:34, Bastian Germann escribió:
Source: diffutils
Severity: important
Version: 1:3.8-1
Hi,
diffutils has an incomplete copyright file. At least LGPL-2.1+ and
GPL-2+ licenses are missing even though they are applicable to some
files. While they can be distributed as GPL-3+, i
El 6/11/22 a las 2:01, Witold Baryluk escribió:
I am somehow confused by the current solution in base-files 12.3.
Please note that what I did in 12.3 does not try to solve everything,
only what it was feasible to do in base-files. I do not claim that the
situation may not improve, only that s
El 12/10/22 a las 17:42, Gioele Barabucci escribió:
Package: base-files
Version: 12.3
Dear base-files maintainer,
this is a followup to #1008735 to provide 3rd-party software authors
with better clarity (and confirmations) about Debian's approach to the
information shipped in `os-release`.
reassign 1009343 debian-policy
thanks
El 12/4/22 a las 5:41, Daniel Kahn Gillmor escribió:
Package: base-files
Severity: wishlist
Version: 12.2
Expat and Boost-1.0 are both fairly common licenses in debian. I
believe they are both well-defined, stable, and reasonably
well-understood variants o
reassign 924094 debian-policy
thanks
El 9/3/19 a las 15:13, Steffen Moeller escribió:
Package: base-files
Version: 10.1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I was packaging a tool with that license without shipping it.
* What outcome did you expect instea
reassign 1013195 debian-policy
thanks
El 18/6/22 a las 23:45, Salvo 'LtWorf' Tomaselli escribió:
Package: base-files
Version: 12.2
Severity: normal
X-Debbugs-Cc: tipos...@tiscali.it
Dear Maintainer,
AGPL-3 license is not present in the base files.
This forces me to include verbatim the very lo
El 3/10/22 a las 11:55, Sedat Dilek escribió:
VERSION_ID=sid
VERSION_CODENAME=bookworm
This is "schizophrenic", so to speak, and I don't think it is a good idea.
I've simply added VERSION_CODENAME=bookworm.
The only caveat is that testing and unstable are sides of the same coin,
but this is a
Thanks for the report.
For completeness: Do you have any idea about what we could do with the
non-GNU licenses? (regarding copyright, that is).
El 31/3/22 a las 13:42, Marc Haber escribió:
Package: base-files
Version: 12.2
Severity: wishlist
Hi,
/etc/os-release in testing and unstable does not set VERSION, VERSION_ID
and VERSION_CODENAME, which causes, for example, ansible to just emit
"NA" as distribution version, which forces me to s
Hi. Could we have this fixed in stable for the next point release
(11.5), please? (The window for uploads closes this weekend).
Please tell me if you need help (for example, doing an upload and/or
submitting a bug to release.debian.org asking for the upload to be
accepted).
Thanks.
El 27/8/22 a las 17:24, Michael Tokarev escribió:
27.08.2022 03:35, Santiago Vila пишет:
Hi. Now that this is finally fixed in sid, here is a proposed diff for
bullseye, including changelog.
Heh. The changelog includes entry by me.. it is not fair for your
contribution, I think.. :)
I
Hi. Now that this is finally fixed in sid, here is a proposed diff for
bullseye, including changelog.
It's the same fix which is now in sid. I've tested and it works for me.
Thanks.
diff -Nru cifs-utils-6.11/debian/changelog cifs-utils-6.11/debian/changelog
--- cifs-utils-6.11/debian/changelog
El 17/8/22 a las 20:10, Santiago Vila escribió:
However, before doing so, I wonder if it would be possible for you to
try the current gettext in unstable with nojava profile, just to be sure
that it will work when I upload the version using --list-missing.
Nevermind.
After fixing debian/not
Package: src:gettext
Version: 0.21-9
X-Debbugs-CC: sanv...@debian.org,debian-h...@lists.debian.org
After applying the patch proposed in Bug#982085 (with minor changes),
the build-dependencies of gettext now allow building under hurd-i386,
but currently it fails some tests. Example:
FAIL: msgcat
reopen 993014
found 993014 2:7.0-1
thanks
This is still happening in both bullseye and sid.
I'm attaching the full build log for sid on a system with only one CPU.
This may be reproduced easily on any system by booting with this
option:
GRUB_CMDLINE_LINUX="nr_cpus=1"
in /etc/default/grub (and
El 20/8/22 a las 14:40, Santiago Vila escribió:
So I wonder if reversing the dependency created by debhelper:
systemd | systemd-tmpfiles
would improve this state of things.
Sorry, the above is confusing. I mean reversing the *order*, so that it
becomes this:
systemd-tmpfiles | systemd
Hello.
As of today, upgrading a sid chroot containing debhelper to the sid of
today, systemd, mount, and several other packages are installed into the
chroot. This is usually undesired because we want build chroots to be as
minimal as possible.
Users of debootstrap can certainly use --includ
Note: emacs-nox seems also to be affected, as I get a similar error when
installing the build-dependencies of gettext:
Setting up emacs-nox (1:28.1+1-1) ...
update-alternatives: using /usr/bin/emacs-nox to provide /usr/bin/emacs
(emacs) in auto mode
Install emacsen-common for emacs
emacsen-com
El 17/8/22 a las 20:27, Jessica Clarke escribió:
Sorry for the oversight in my patch. You could list it twice, once with
the arch restriction and once with the profile restriction?
Good idea! Yes, I believe that should work, as far as not-installed
allows for duplicate entries. I'll try that a
Hi. I'm trying to make gettext buildable on hppa (and every other
non-java arch), but there is a subtle problem with debhelper, maybe you
can help.
After accepting the modifications proposed in Bug#982085 (with minor
changes), this is what I have in debian/gettext.install
[!hppa !hurd-i386 !
El 19/6/22 a las 0:09, Hilmar Preusse escribió:
Package: gettext
Version: 0.21-6
Severity: minor
Dear Maintainer,
The package declare a dep on "install-info". However this dep should only
be needed for info viewers, as they have to care about updating the info index.
Hi. I don't remember well
1501 - 1600 of 6685 matches
Mail list logo
