On Mon, Aug 04, 2025 at 03:26:14PM -0400, Sergio Durigan Junior wrote:
> On Monday, August 04 2025, Bill Allombert wrote:
>
> > Le Mon, Aug 04, 2025 at 12:57:08PM -0400, Sergio Durigan Junior a écrit :
> >> This bug is more than 10 years old; GDB has suffered significant ch
addii_sign(GEN x, long sx, GEN y, long sy)
62 {
63long lx,ly;
64GEN z;
65
66if (!sx) return sy? icopy_sign(y, sy): gen_0;
so I can confirm this bug was fixed.
Thanks for being the first person to reply at this bug report despite my attempt
at make it easily repr
Debian 6.12.38-1 (2025-07-16) x86_64 GNU/Linux
> Method: apt upgrade --without-new-pkgs ; apt full-upgrade
>
> Contents of /etc/apt/sources.list:
> Empty - removed by apt modernize-sources which provoked the bug in
> synaptic
Hi Neil,
For the record, you should specify the version of synaptic you are using.
Cheers,
Bill.
Package: wine
Version: 10.0~repack-6
Severity: important
X-Debbugs-Cc: bill+t...@eclectichouston.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
On trixie installed wine, added i386 arch and installed wine32
clearly not an issue in this
> case because the cleartext is being saved as /var/log/popularity-contest
> anyway, so the warning is really pointless in this case.
Thanks, I also have plans to allow different programs than gpg once trixie is
released.
Cheers,
--
Bill.
Imagine a large red swirl here.
th, packages.debian.org and the BTS send email to the
package maintainer according to the Maintainer field.
They do not support multiple email addresses.
Cheers,
--
Bill.
Imagine a large red swirl here.
they
> like it or not. Virtually nothing else requires to install cron-cruft
> anymore.
Well, then please address my request:
" Provide a patch that does not break backward compatibility with the fact that
/etc/cron.daily/popularity-contest is a conffile. "
Cheers,
--
Bill.
Imagine a large red swirl here.
arly Maintainer and
> Uploaders ought to be in the same syntax.
Do you have a list of all tools and services that assume that Maintainer is a
single email address ? Before that, I consider any changes to be dangerous.
Cheers,
--
Bill.
Imagine a large red swirl here.
ng packages multiple time. Consider
% apt-file find /lib/ | grep '/bin/' |cut -d: -f1|sort -u|wc -l
439
vs
% apt-file find /lib/x86_64-linux-gnu | grep '/bin/' |cut -d: -f1|sort -u|wc -l
60
If we make changes to GAP, we need to be able to justify them. So we need a
real usecase.
Cheers,
Bill.
u need to deviate from the Debian policy ?
Where does policy mandates /usr/libexec/ ?
$apt-file -l search /usr/libexec/x86_64-linux-gnu|wc
9 9 106
$seventeen - ~#apt-file -l search /usr/libexec|wc
465 4656538
So overwhelmingly, /usr/libexec/ is not used.
Cheers,
--
Bill.
Imagine a large red swirl here.
TIARCH for Debian
> systems) follows the way that GAP implements
> and uses GAPInfo.Architecture.
But it seems to me the normal place for such binary should be /usr/bin with a
prefix, as it is done with gap-nq, or alternatively in /usr/libexec/gap without
a triplet.
Why do you need to deviate from that ?
Cheers,
Bill.
Note the the patch apply to the Debian source gap-4.140-3, namely the one
> currently in Sid.
> Second, after applying the patch, the `configure' and `src/config.h.in' files
> must be regenerated.
> This can be done by launching `autogen.sh'.
Hello Jerome, could you describe the use case ? This is unclear to me.
Cheers,
Bill.
et/#source-formats). So the discussion in
> "past 10 years" you refer to already had a clear outcome.
You are confusing 'unpopular' and 'deprecated'.
Cheers,
--
Bill.
Imagine a large red swirl here.
the ABI of the Xeus packages, see
#1106511.
At this point of the freeze there is no purpose uploading new xeus packages to
bump the Xeus ABI.
Thanks for your understanding,
Cheers,
--
Bill.
Imagine a large red swirl here.
ally work ?
Thanks!
At some point GMail and GMail users should be made to pay for the work they
inflict on others.
Cheers,
--
Bill.
Imagine a large red swirl here.
page[kindabroken]: https://www
Homepage[github]: https://github
Cheers,
--
Bill.
Imagine a large red swirl here.
ould really like to see the buildlog for xeus itself, if you have it.
Cheers,
--
Bill.
Imagine a large red swirl here.
1.3
to allow xeus to build correctly with the right ABI.
Cheers,
--
Bill.
Imagine a large red swirl here.
after coordinating with all packages that
build-depend on it.
For example by waiting until there is upstream soname bump for libxeus.
The only solution is to rename nlohmann-json3-dev to nlohmann-json3.12.0-dev so
that uploading a
nex upstream version does not remove the old one from the archive.
Cheers,
--
Bill.
Imagine a large red swirl here.
| all
So I am unsure what to do. How are we supposed to deal with RC bug in unstable
that do not affect stable ?
Cheers,
--
Bill.
Imagine a large red swirl here.
On Wed, May 07, 2025 at 08:39:58PM +0100, Simon McVittie wrote:
> On Wed, 07 May 2025 at 20:57:15 +0200, Bill Allombert wrote:
> > By changing SOURCE_DATE_EPOCH in what is purported to be a 'binary-only
> > upload'
> > we are breaking the reproducible build semant
n so that the generated documents are identical to the one in the
upstream tarballs.
Having reproducible builds allow for meaningful date and timestamp, and is not
a rationale to remove them.
Cheers,
--
Bill.
Imagine a large red swirl here.
tion long term is to introduce a new variable
BUILD_DATE_EPOCH as suggested by Andrea Pappacoda, that would be identical to
SOURCE_DATE_EPOCH except for binNMU.
If only dpkg need to understand BUILD_DATE_EPOCH at first, then it is doable.
Cheers,
--
Bill.
Imagine a large red swirl here.
cess.
autopkgtest has an option to allow network access, so you can use that.
If you need the test to be performed as part of the build, propose a new
DEB_BUILD_OPTION 'allownetworktest' and make your tests conditional on that.
Cheers,
--
Bill.
Imagine a large red swirl here.
being tracked
via
server logs. In your case building the package with internet access
- fails if timestamp.digicert.com is down
- leaks the system IP to DIGICERT
Completly disabling access to internet during a build is harder than it sound.
Cheers,
--
Bill.
Imagine a large red swirl here.
eported a bug that suggest some package were calling
x-terminal-emulator with -name
which is not supported ?
Cheers,
--
Bill.
Imagine a large red swirl here.
s not autogenerated, but DEBIAN/control is
(by dpkg-gencontrol). This difference should be made clear in the rationale.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Fri, Mar 28, 2025 at 01:23:19PM +0100, Guillem Jover wrote:
> Hi!
>
> On Fri, 2025-03-28 at 13:01:47 +0100, Chris Hofstaedtler wrote:
> > * Bill Allombert [250328 10:33]:
> > > On Fri, Mar 28, 2025 at 10:02:46AM +0100, Guillem Jover wrote:
> > > > Sourc
> debian-popcon.gpg file.
Hi Guillem,
This is intended. You can get this file from the Debian source package.
This way, there is only one official source.
Cheers,
--
Bill.
Imagine a large red swirl here.
Package: luanti
Severity: normal
Version: 5.10.0+dfsg-3
Hello Debian game team,
luanti recommends luanti-game-minetest which is not available, not
even in the NEW queue.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Mon, Mar 10, 2025 at 03:18:07PM +0100, Bill Allombert wrote:
> In that spirit, please find a third one, which fail with both libc,
> but in a different way.
>
> About 10% of the time, it hangs in 'exit' after all threads have terminated.
(This is an aside to this bug re
On Tue, Mar 11, 2025 at 11:29:46PM +0100, Aurelien Jarno wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=32782
>
> Hi Bill,
> >
> > I join a simplified test-case.
>
> Thanks, I have been able to simplify it a tiny bit more, please f
On Mon, Mar 10, 2025 at 12:24:43PM +0100, Bill Allombert wrote:
> On Fri, Mar 07, 2025 at 11:45:10AM +0100, Bill Allombert wrote:
> > I am still unsure wether there is a race condition in PARI or not, however
> > if
> > there is, it is clear that 2.41 makes the issue m
On Mon, Mar 10, 2025 at 12:24:43PM +0100, Bill Allombert wrote:
> On Fri, Mar 07, 2025 at 11:45:10AM +0100, Bill Allombert wrote:
> > I am still unsure wether there is a race condition in PARI or not, however
> > if
> > there is, it is clear that 2.41 makes the issue m
On Tue, Mar 11, 2025 at 09:12:15AM +0100, Bill Allombert wrote:
> On Mon, Mar 10, 2025 at 11:49:39PM +0100, Aurelien Jarno wrote:
> > I also noticed it failed the same way on arm64.
>
> Thanks for confirming!
>
> > > > Please tell me if you would like me to do mor
one!
29 30 31 Done!
32 33 34 Done!
35 36 37 38 39 40 Done!
41 42 43 44 45 46 Done!
47 48 49 50 51 52 53 Done!
54 55 56 57 58 59 60 61 62 63 64 65 ^C%
I join a simplified test-case.
Cheers,
--
Bill.
Imagine a large red swirl here.
/* Copyright (C) 2013 The PARI group.
This file is part of t
On Fri, Mar 07, 2025 at 11:45:10AM +0100, Bill Allombert wrote:
> I am still unsure wether there is a race condition in PARI or not, however if
> there is, it is clear that 2.41 makes the issue much worse.
Hello Aurélien,
I have made some progress. I have made a test program that does n
On Thu, Mar 06, 2025 at 07:02:25AM +0100, Aurelien Jarno wrote:
> Hi Bill,
>
> On 2025-03-05 21:30, Bill Allombert wrote:
> > Package: libc6
> > Version: 2.41-7
> > Severity: normal
> >
> > Hello Aurelien,
> >
> > During a test bui
On Fri, Mar 07, 2025 at 03:57:42PM +, Ian Jackson wrote:
> Bill Allombert writes ("Re: Bug#1092193: option (or env) to request
> <=bookworm r-r-r behaviour"):
> > 2/ I consider --rules-requires-root to be a sufficient work-around
> > _provided_ it is clearly
On Thu, Mar 06, 2025 at 02:17:46PM +0100, Bill Allombert wrote:
> On Thu, Mar 06, 2025 at 09:50:35AM +0100, Bill Allombert wrote:
> > On Thu, Mar 06, 2025 at 07:02:25AM +0100, Aurelien Jarno wrote:
> > > Hi Bill,
> > >
> > > On 2025-03-05 21:30, Bill All
ld not have been
added, and we could argue that the best way to avoid noise and complexity
is to avoid breaking backward compatibility.
What we should not do, in any case, is to ignore the transition problem.
Cheers
--
Bill.
Imagine a large red swirl here.
default value binary-targets (since dpkg 1.19.1).
which is a bit confusing for packages that do not have a Rules-Requires-Root
field.
Cheers,
--
Bill.
Imagine a large red swirl here.
"((thr->slot)) != (0)" (0x0, 0x0) (tid=1455863)
but only with glibc 2.41.
I am still unsure wether there is a race condition in PARI or not, however if
there is, it is clear that 2.41 makes the issue much worse.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Thu, Mar 06, 2025 at 07:02:25AM +0100, Aurelien Jarno wrote:
> Hi Bill,
>
> On 2025-03-05 21:30, Bill Allombert wrote:
> > Package: libc6
> > Version: 2.41-7
> > Severity: normal
> >
> > Hello Aurelien,
> >
> > During a test bui
On Thu, Mar 06, 2025 at 07:17:25PM +0100, Aurelien Jarno wrote:
> On 2025-03-06 19:03, Bill Allombert wrote:
> > >
> > > Do you have more details about that? I have tried to build pari locally,
> > > and it builds fine. On which architecture is that? In which versi
On Thu, Mar 06, 2025 at 09:50:35AM +0100, Bill Allombert wrote:
> On Thu, Mar 06, 2025 at 07:02:25AM +0100, Aurelien Jarno wrote:
> > Hi Bill,
> >
> > On 2025-03-05 21:30, Bill Allombert wrote:
> > > Package: libc6
> > > Version: 2.41-7
> > &
course I cannot rule out that pari has a race condition that only triggers
with libc6 2.41,
but the test is very simple, the code has been working fine for a long time
and the failure mode are multiples.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Wed, Mar 05, 2025 at 04:14:50PM +0100, Niels Thykier wrote:
> Bill Allombert:
> > [...]
> >
> > Users are using dpkg to build packages that are not part of unstable and
> > testing,
> > and so have not beed considered by the November tests.
> >
> >
ll correct.
>
> I was exercising my authority as DPL Delegate to go ahead and undo the
> change quickly despite opposition, because I saw the violation of
> procedural norms to be so significant.
You have my full support. Changes that are unintentionnal, inadvertent or
erroneous need to be reverted quickly not to create a precedent, otherwise
this jeopardizes the process.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Tue, Mar 04, 2025 at 07:57:28PM +0100, Niels Thykier wrote:
> Bill Allombert:
> > On Mon, Mar 03, 2025 at 08:55:38PM +0100, Niels Thykier wrote:
> > > Control: severity -1 normal
> > >
> > > When Guillem and I analyzed the numbers in November, we concluded
of the packages would need a change.
What about packages that are not in unstable or testing ?
Cheers,
--
Bill.
Imagine a large red swirl here.
On Sat, Jul 16, 2022 at 10:18:11AM +0200, Ansgar wrote:
> On Thu, 2022-07-14 at 19:59 +0200, Bill Allombert wrote:
> > On Thu, Jul 14, 2022 at 06:29:55PM +0200, Ansgar wrote:
> > > > From man:machine-id(5):
> > >
> > > +---
> > > > The machine
On Sun, Nov 20, 2022 at 08:08:53AM +0800, Paul Wise wrote:
> On Fri, 2022-11-18 at 16:06 +0100, Bill Allombert wrote:
>
> > But then the user would not be able to configure it anymore,
> > so I do not see the upside.
>
> I just discovered an alternative that preserves th
:
> cron-daily-popularity-contest.service: Consumed 2.512s CPU time.
Hello Martin-Éric,
Did you find you what happened ? Did it happen again ?
Was /var/log/ full ? Are there two containers instance sharing the same
/var/log by mistake.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Tue, Feb 25, 2025 at 11:17:37PM +0100, Bill Allombert wrote:
> Package: libchart-perl
> Version: 2.403.9-1
> Severity: normal
>
> Hello Debian Perl Group,
>
> Upgrading popcon.debian.org to bookworm breaks the graphics due to an issue in
> libchart-perl. I join a very
x27; is an unknown color name, please check
Graphics::Toolkit::Color::Constant::all_names(). at
/usr/share/perl5/Chart/Base.pm line 1165.
Unrecognized color for dataset73
at test.pl line 10.
with bullseye, it works for at least 374.
Cheers,
--
Bill.
Imagine a large red swirl here.
#! /usr/bin/pe
Package: libfinance-quote-perl
Version: 1.64-2
Severity: normal
Dear Maintainer,
While running the Tools > Price Database > Get Quotes command, I got the
following error:
Unable to retrieve quotes for these items:
I use the YahooJSON source.
I'm running bookworm, but had updated libfinance
in the first 512 bytes of the file, otherwise
> ldconfig will be unhappy.
For what is worth,
% cat /usr/lib/x86_64-linux-gnu/libncurses.so
INPUT(libncurses.so.6 -ltinfo)
Cheers,
--
Bill.
Imagine a large red swirl here.
.so to libgdbm.so.3.0.0, or a linker script that
> achieves the same effect. This symlink or linker script is needed by
> the linker (ld) when compiling packages, as it will only look for
> libgdbm.so when compiling dynamically.
Hello Aurelien,
Maybe a footnote explaining when a linker sc
ather depressing both from
the Debian point of view and the upstream point of view.
I anticipate the problem is only going to become worse.
I do not know what we can do about it.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Sat, Jan 25, 2025 at 10:23:01AM -0500, Jeremy Bícha wrote:
> On Sat, Jan 25, 2025 at 5:21 AM Bill Allombert wrote:
> > The man page provides a link between the executable name and the app.
> > This is useful in a lot of situation. Writing such a manpage is not
> > a waste
e we need a tool dh_help2man that would automatically build man pages.
using ---help and the synopsis in debian/control.
Cheers,
--
Bill.
Imagine a large red swirl here.
ntainer to fix all similar bugs in a single
upload.
In that spirit, do you have other bugs related to menu manpage to report ?
Thanks,
--
Bill.
Imagine a large red swirl here.
I set WINEDEBUG=-all
This causes the output of wine to be broken and break the build.
Cheers,
Bill.
Hi Salvatore,
On Thu Jan 16 2025 at 09:30 AM +0100, Salvatore Bonaccorso wrote:
> On Wed, Jan 15, 2025 at 08:02:18AM -0800, Bill Brelsford wrote:
> > [ 40.980166] kernel BUG at fs/nfsd/nfs4recover.c:534!
> > [ 40.984266] Oops: invalid opcode: [#1] PREEMPT SMP PTI
>
s which do not work please?
Attached is dmesg from trixie.
Bill
[0.00] Linux version 6.12.6-amd64 (debian-ker...@lists.debian.org)
(x86_64-linux-gnu-gcc-14 (Debian 14.2.0-11) 14.2.0, GNU ld (GNU Binutils for
Debian) 2.43.50.20241215) #1 SMP PREEMPT_DYNAMIC Debian 6.12.6-1 (2024-12-21)
[
gards.. Bill
quot;"
Except for packages in the non-free archive with the Autobuild control field
unset or set to no, required targets must not attempt network access to other
hosts.
Only access via the loopback interface to services on the build host that have
been started by the build are allowed.
"""
Cheers,
--
Bill.
Imagine a large red swirl here.
t the equivalent: "Autobuild: no" become "Autobuild: yes" in your
version...
Also it is awkward to put the exception before the rule.
I feel this is less clear than the original version.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Sat, Jan 04, 2025 at 12:54:20PM +0100, Chris Hofstaedtler wrote:
> * Bill Allombert [250104 12:21]:
> > > > Secondly, I just found a package that fails if /usr/share/doc is
> > > > removed, so I wonder how far we can actually validate this.
> > >
> >
Precisely, the package in question was not changed since that policy was in
effect. Debian was not able to detect this problem for so long so policy
promising otherwise might not quite reflect the state of the distribution.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Tue, Dec 31, 2024 at 11:45:49PM -0800, Don Armstrong wrote:
> On Sun, 29 Dec 2024, Bill Allombert wrote:n
> > Do you have a preference how to fix this bug ?
>
> My personal preference is to fix debbugsconfig to not copy those files
> at all. The example config is needlessly
r/share/doc/$pkg, it is easy to move the files to /usr/share/$pkg.
But for /usr/share/man and /usr/share/info, what to do ?
Secondly, I just found a package that fails if /usr/share/doc is removed, so I
wonder how far we can actually validate this.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Sun, Dec 29, 2024 at 07:49:24PM +0100, Bill Allombert wrote:
> Hello Don,
> Do you have a preference how to fix this bug ?
I join a minimal patch that fixes this.
Cheers,
--
Bill.
Imagine a large red swirl here.
diff --git a/Makefile b/Makefile
index 93ed796..5cb29cf 100644
On Sun, Dec 22, 2024 at 12:43:25AM +0100, Bill Allombert wrote:
> Package: debbugs
> Version: 2.6.3
> Severity: normal
>
> Hello Don,
>
> debbugsconfig does
> system("cp /usr/share/doc/debbugs/examples/$name $destdir/$name") == 0
>
> However policy pr
/html/server-request.html.in
If debbugs-web is not installed, then debbugsconfig fails with
cp: cannot create regular file '/etc/debbugs/config
Cheers,
Bill.
is not particularly recent, the layered override was
implemented for TeX in kpathsea in 1993.
I always considered to be the best scheme for handling upgrade, I am glad
to see it is more widely used.
Cheers,
--
Bill.
Imagine a large red swirl here.
> For kdesu, the
> program path has changed.
Thanks! It changes frequently... What is the new path ?
Does it work with su-to-root ?
What about wayland ?
Cheers,
--
Bill.
Imagine a large red swirl here.
On Mon, Dec 23, 2024 at 08:56:43AM +0100, Chris Hofstaedtler wrote:
> On Fri, Mar 08, 2024 at 06:15:16PM +0100, Bill Allombert wrote:
> > On Sun, Feb 25, 2024 at 11:21:26PM +, ca...@allfreemail.net wrote:
> > > your package installs the filenames `install-menu` and `su-to-ro
s/ used by
debbugsconfig should probably be moved to /usr/share/debbugs/examples.
This would also fix the issue that file in /usr/share/doc/ are sometime
compressed.
Cheers,
Bill.
On Sun, Dec 15, 2024 at 03:21:06PM -0800, Don Armstrong wrote:
> On Sun, 15 Dec 2024, Bill Allombert wrote:n
> > Package: debbugs
> > Version: 2.6.3
> > Severity: normal
> >
> > Hello Don,
> >
> > This is from #644242.
> >
> > the file cg
On Wed Dec 18 2024 at 09:43 PM -0800, Bill Brelsford wrote:
> > > > Can you additionally please test to downgrade to the 2.8.1-2 version
> > > > and please report back if you see the problem there was well? For us
> > > > it should behave actually same a
fsdctl commands work:
# nfsdctl status
# nfsdctl threads
gracetime: 90
leasetime: 90
scope: k2ww
pool-threads: 16
# nfsdctl listener
tcp:[::]:2049
tcp:0.0.0.0:2049
# nfsdctl version
+3.0 +4.0 +4.1 +4.2
Hope this helps. Thanks.. Bill
gs stand, I will not do
that unless I have an explicit authorization from the TC.
Sorry...
Cheers,
--
Bill.
Imagine a large red swirl here.
grading (to 2.8.2-1), there is no
problem -- I can start and stop the daemon, export/unexport
filesystems, etc. Everything seems normal -- until the system is
rebooted and rpc.nfsd is invoked.
Regards.. Bill
again (or, e.g., exportfs -r)
hangs and can't be killed.
The same failure occurs on another similarly-configured system.
Thanks.. Bill
Package: debbugs
Version: 2.6.3
Severity: normal
Hello Don,
This is from #644242.
the file cgi/search.cgi links to http://bugs.debian.org/css/bugs.css instead
of linking to $gWebHostBugDir/css/bugs.css or maybe
/$gWebHostBugDir/css/bugs.css
Cheers,
Bill.
is in examples/debian/misc/bugspam.cgi in the source, but this is not
included in any binary packages.
Should bugspam.cgi be moved to cgi and installed in ./var/lib/debbugs/www/cgi/ ?
Cheers,
Bill.
usr/sbin/rpc.nfsd
./nfs-kernel-server: line 61: 3694 Segmentation fault start-stop-daemon
--start --oknodo --quiet --nicelevel $RPCNFSDPRIORITY --exec
$PREFIX/sbin/rpc.nfs
Downgrading to 1:2.8.1-1 (from trixie; also nfs-common and
libnfsidmap1) resolves the problem.
Thanks.. Bill
-- Pack
ause it is missing from the 'globals' EXPORT_TAGS in
Debbugs/Config.pm
Does that makes sense ?
Cheers,
Bill.
migrate the cron job to a systemd timer on Linux ports. The
> cron job remains desirable on the Hurd port, however, since that port has no
> systemd unit support.
Could you provide a patch that does not break backward compatibility with the
fact that /etc/cron.daily/popularity-contest is a c
systems?
What is a graceful failure for some script is a crash for another...
Cheers,
Bill.
bly pick a more explicit Debian package name,
since there is already a package libpaper-utils in Debian, so
this might lead to confusion.
Cheers,
--
Bill.
Imagine a large red swirl here.
atively, following the feedback on this bug report, ask devscript
to
change "pretty" not to include the %h part ?
But in general policy should refrain to be normative when there is no sound
technical reason. Popularity is not sufficient. One could even argue that
there are more technical reasons not to include the hash.
Cheers,
--
Bill.
Imagine a large red swirl here.
dentifier in debian/changelog instead.
This bug report makes a good point that version should be kept to be
copy-pastable and
comparable by humans.
By itself, the git commit hash does not provide any information without a copy
of the git repository. debian/changelog should be sufficient for that purpose.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Wed, Nov 27, 2024 at 05:43:04PM +, Holger Levsen wrote:
> On Wed, Nov 27, 2024 at 06:31:22PM +0100, Bill Allombert wrote:
> > Replace dh_buildinfo by a script that just print a warning but does not
> > actually
> > generate the file, then ask for binNMU ?
> >
while 100%
> of the packages build with dpkg produce .buildinfo files outside the
> packages built.
>
> It's not the greatest bug in the world, yet it is a bug.
Replace dh_buildinfo by a script that just print a warning but does not actually
generate the file, then ask for binNMU ?
Update the description to mention the problem.
Cheers,
--
Bill.
Imagine a large red swirl here.
ebian-devel@ though I'd be very happy if someone else would do it!)
Upload a version of dh_buildinfo that does nothing be output a warning
'warning: db_buildinfo is obsolete, please remove from Build-Depends'.
This would gives time to maintainers to fix the issue before a MBF.
Add a lin
nefit? People used to typing
> 'less debian/README.source' would need to retrain their fingers.
This is my concern too:
the whole point of this policy is to specify the filename.
Beside this file is only useful in limited circumstances which are less
and less frequent due to improvement to dpkg and uupdate. It is unclear
why anyone would need markdown for it.
Cheers,
--
Bill.
Imagine a large red swirl here.
rkdown specifically as it has become an industry
> standard for ASCII markup and use on README.md files is very common.
Are there tools that automatically locate README.source and would need to be
adapted to
find README.source.md instead ?
Cheers,
--
Bill.
Imagine a large red swirl here.
1 - 100 of 2514 matches
Mail list logo
