Re: Mandatory LC_ALL=C.UTF-8 during package building

On Thu, Jun 06, 2024 at 12:08:17PM +0200, Johannes Schauer Marin Rodrigues wrote: > Or whether we should switch the default and require that d/rules is run in an > environment (for example as set-up by dpkg-buildpackage) where these variables > are set? (a previous discussion on this: https://list

Enabling some -Werror=format* by default?

We recently increased the time_t size on certain architectures and some packages started failing to build because they were using a format specifier too narrow for the wider time_t, e.g. #1067829. But the only reason those package FTBFS is they enable either -Werror or some more specific non-defaul

Re: Illegal Instruction Using sudo in Bookworm on i686

On Sun, Jun 09, 2024 at 06:56:00AM -0500, rhys wrote: > The question right now is: Is this processor supported at all? No. > So given that these no longer fit the "old and busted" description, is Debian > going to stick with the decision to not support them? I'm sure we will, yes, though I'm not

Re: Suggestions about i386 support

On Sun, Jun 09, 2024 at 08:39:27PM -0500, r...@neoquasar.org wrote: > >> It's not just a matter of "buy something better." That's easy.  > > >Indeed, that is easier and cheaper. > > Of course, continuing to use a system I already have is cheaper still. > > > What's not easy is that a) that adds

Re: Enabling some -Werror=format* by default?

On Mon, Jun 10, 2024 at 07:48:59AM +0200, Helmut Grohne wrote: > > We recently increased the time_t size on certain architectures and some > > packages started failing to build because they were using a format > > specifier too narrow for the wider time_t, e.g. #1067829. > > But the only reason tho

Re: Enabling some -Werror=format* by default?

On Mon, Jun 10, 2024 at 04:24:54PM +0200, Guillem Jover wrote: > > > > We recently increased the time_t size on certain architectures and some > > > > packages started failing to build because they were using a format > > > > specifier too narrow for the wider time_t, e.g. #1067829. > > > > But the

Re: Enabling some -Werror=format* by default?

On Mon, Jun 10, 2024 at 04:24:54PM +0200, Guillem Jover wrote: > > Do you think it makes sense to add this a flag that enables -Werror=format > > to dpkg-buildflags(1), before, or after a test rebuild, before, or after > > the MBF if we do one? > > If by adding you mean adding a new feature flag t

Re: Suggestions about i386 support

On Mon, Jun 10, 2024 at 04:02:54PM +0100, Simon McVittie wrote: > On Mon, 10 Jun 2024 at 12:43:27 +, Stefano Rivera wrote: > > The point here is that the Debian project is not intending to support > > new hardware on the i386 architecture. The architecture is being kept > > around primarily to

Re: Seeking consensus on file conflict between python3-proto-plus and nanopb

On Mon, Jun 10, 2024 at 06:40:02PM -0400, Yogeswaran Umasankar wrote: > There is a file conflict between python3-proto-plus and nanopb. The > conflict arises due to both packages has a file at > /usr/lib/python3/dist-packages/proto/__init__.py [0]. I am maintaining > python3-proto-plus, and I am se

Re: Re: About i386 support

On Fri, Jun 14, 2024 at 05:53:42AM -0500, r...@neoquasar.org wrote: > A bug that can't be reproduced, effectively doesn't exist.  Wow. -- WBR, wRAR signature.asc Description: PGP signature

Re: WolfSSL and Netatalk

On Sun, Jun 23, 2024 at 05:58:54AM +, Daniel Markstedt wrote: > > wolfssl is packaged in Debian, did you try to build netatalk with the > > packaged version? > > > > Debian doesn't like code copies in sources, so if it builds fine with > > the packaged version, removing it from the source that

Re: dh_auto_clean, autoconf, and building packages twice (was: Potential MBF: packages failing to build twice in a row)

On Sun, Jun 23, 2024 at 02:06:04PM +0200, Magnus Holmgren wrote: > I'm very late to the party, but after reading the entire thread, I'd like to > discuss a more specific, but perhaps not uncommon, situation with regard to > cleaning and building again: > > We have a [still fairly] typical upstre

Re: Mini-DebConf in Cambridge, UK - October 10-13 2024

On Tue, Jun 25, 2024 at 06:14:54AM -0400, Roberto C. Sánchez wrote: > > The style of writing mail - everything in one line, CCing several lists is > > similar to how Luna writes it too. Freaky. > > > AI can already generate audio and video that convincingly imitate real > people. Why not the same

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 02:02:11PM +0100, Simon McVittie wrote: > > In this work, limitations with --chroot-mode=unshare became apparent and > > that lead to Johannes, Jochen and me sitting down in Berlin pondering > > ideas on how to improve the situation. That is a longer story, but > > eventuall

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 10:24:12AM -0700, Russ Allbery wrote: > Guillem Jover writes: > > > I manage my chroots with schroot (but not via sbuild, for dog fooding > > purposes :), and use type=directory and union-type=overlay so that I get > > a fast and persistent base, independent of the underly

Re: BIMI verified email logo for @debian.org addresses

On Thu, Jun 27, 2024 at 07:29:45PM +0800, Blair Noctis wrote: > Hi, > > [BIMI], or Brand Indicators for Message Identification, is a specification to > let supporting email clients show a brand's logo next to verified email > domains. > It would be great to have the Debian logo shown next to @deb

Re: How does lintian use groff to validate man pages?

On Fri, Jun 28, 2024 at 11:38:50AM +, c.bu...@posteo.jp wrote: > > lintian-explain-tags can provide you with extensive information > > ... > > N: LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ > > N: man --warnings -E UTF-8 -l -Tutf8 -Z >/dev/null > > Do I do something wro

Re: Urgent help with upload of netatalk to prevent being autoremoval from testing

On Sat, Jun 29, 2024 at 02:13:04PM +, Daniel Markstedt wrote: > Netatalk got dropped from Bookworm because there was a changing of the guards > of upstream maintainers during the freeze time. > So I'm just naturally anxious about missing the boat again for Trixie. Just make sure it's in testi

Re: Q: Ubuntu PPA induced version ordering mess.

On Mon, Jul 01, 2024 at 09:46:11PM +0200, Alec Leamas wrote: > On 01/07/2024 20:48, Alec Leamas wrote: > > Dear list, > > > > Still working with the opencpn package. Now trying to normalize the > > Ubuntu PPA builds so they can are based on the same debian/ directory > > and tools as the existing

Re: Q: Ubuntu PPA induced version ordering mess.

On Mon, Jul 01, 2024 at 11:59:00PM +0200, Alec Leamas wrote: > > > After some thought, I tend to think that adding an epoch is the right > > > thing > > > here. > > > > > > The Policy [1] says: > > > --- > > > Epochs can help when the upstream version numbering scheme changes, but > > > they > >

Re: Q: Ubuntu PPA induced version ordering mess.

(sorry, I replied thinking I've read the entire thread, I didn't notice that there is a second thread broken off of this one) -- WBR, wRAR signature.asc Description: PGP signature

Re: Q: Ubuntu PPA induced version ordering mess.

On Wed, Jul 03, 2024 at 09:27:03AM +0200, Philip Hands wrote: > IOhannes m zmölnig (Debian GNU|Linux) writes: > > > anyhow here's my 2¢: > > according to you¹, upstream have simply botched their package > > versioning, which i would consider *a bug*. > > bugs cause pain. > > AIUI the botching w

Re: DD's, Debian Mentors needs you!

On Sun, Jul 07, 2024 at 07:41:25AM +0800, xiao sheng wen(肖盛文) wrote: > Hi, > > Support this become a weekly thing or a monthly thing. > > Can mentors.debian.net sent package list to debian-devel automatically? The list of open RFSes is always available at https://bugs.debian.org/sponsorship-re

Re: DD's, Debian Mentors needs you!

On Sun, Jul 07, 2024 at 07:54:25AM +0200, Andreas Tille wrote: > Hi Phil, > > thanks for advertising Debian Mentors. > > Am Sat, Jul 06, 2024 at 02:45:33PM +0100 schrieb Phil Wyett: > > Hi all DD's > > > > Debian Mentors[1] always struggles to find available Debian Developers for > > final revi

Re: DD's, Debian Mentors needs you!

On Sun, Jul 07, 2024 at 10:10:55AM -0400, Jeremy Bícha wrote: > On Sat, Jul 6, 2024 at 9:46 AM Phil Wyett wrote: > > Debian Mentors[1] always struggles to find available Debian Developers for > > final reviewing and > > sponsoring of packages submitted too our part of the project. > > One thing

Re: Bug#1075905: ITP: python-fraction -- Fraction carries out all the fraction operations including addition, subtraction, multiplication, division, reciprocation

On Sun, Jul 07, 2024 at 07:00:57PM +0200, Daniele Nicolodi wrote: > On 07/07/24 17:43, Yogeswaran Umasankar wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Yogeswaran Umasankar > > X-Debbugs-Cc: debian-devel@lists.debian.org, y...@debian.org > > > > * Package name: python-fraction

Re: Bug#1075905: ITP: python-fraction -- Fraction carries out all the fraction operations including addition, subtraction, multiplication, division, reciprocation

On Sun, Jul 07, 2024 at 01:54:59PM -0400, Yogeswaran Umasankar wrote: > Yes, can use the standard library. This dependency chain starts with > moarchiving, which itself is a dependency for cma, and so on. I can > create a patch specifically for moarchiving. As reported elsewhere, moarchiving decla

Re: Ready stage for DD review/sponsoring - Too many DDs may spoil the broth. :-)

On Fri, Jul 12, 2024 at 05:54:59AM +0100, Phil Wyett wrote: > Morning all, > > As we embark on a new process where packages submitted to mentors are reviewed > and brought to a "Ready" stage for then busy DDs who are gracious enough to > give > their time to review and possibly sponsor into Debia

Re: Ready stage for DD review/sponsoring - Too many DDs may spoil the broth. :-)

On Fri, Jul 12, 2024 at 07:01:41AM +0100, Phil Wyett wrote: > > > As we embark on a new process where packages submitted to mentors are > > > reviewed > > > and brought to a "Ready" stage for then busy DDs who are gracious enough > > > to give > > > their time to review and possibly sponsor into

Re: what about Netplan?

On Sat, Jul 13, 2024 at 09:44:03PM +0200, Lukas Märdian wrote: > > However, I do not think it should be the default. First of all, only > > Ubuntu uses it, nobody else - as Simon says, we don't want the > > defaults to be super-special things that nobody else uses. And then > > Actually, I think t

Re: i686 require SSE4.1-capable processor?

On Mon, Jul 15, 2024 at 01:42:50PM +0200, Andreas Ronnquist wrote: > I'm maintaining a package (filezilla) which just got a bug report that > it simply crashes on program start - It gets a SIGILL - "Illegal > instruction". (#1076312 report [1]). > > After the reporter debugged it, it seems like i

Re: i686 require SSE4.1-capable processor?

On Tue, Jul 16, 2024 at 12:46:01PM +0100, Phil Wyett wrote: > > > > Packages built for the i386 arch need to conform to the i386 baseline, > > > > which is currently i686. If a package contains a newer instruction it's > > > > a > > > > bug in that package and gcc is not the cause of it, the packa

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

On Sat, Aug 03, 2024 at 10:37:42PM +0200, Salvo Tomaselli wrote: > > 2. Standardizing around a single (or small number of) workflows will make > > some people unhappy. But that is an acceptable price to pay because of the > > general benefit to the project *as long as the correct solution is > >

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

On Sat, Aug 03, 2024 at 04:15:33PM +0900, Charles Plessy wrote: > one problem I have with NMUs in team-maintained package is that they > often bypass Salsa… Would it make sense to add to the DEP a request > that NMUs are started from and pushed to the default branch? Only if DEP-18 also includes

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

On Sun, Aug 04, 2024 at 04:15:13PM +0200, Fabio Fantoni wrote: > Il 04/08/2024 15:36, Andrey Rakhmatullin ha scritto: > > On Sat, Aug 03, 2024 at 04:15:33PM +0900, Charles Plessy wrote: > > > one problem I have with NMUs in team-maintained package is that they > > > of

Re: Who is taking care of storm.debian.net?

On Mon, Aug 12, 2024 at 11:02:04AM +0200, Philipp Kern wrote: > On 12.08.24 10:57, Carsten Schoenert wrote: > > Am 12.08.24 um 10:27 schrieb Carsten Schoenert: > > > Hi, > > > > > > the certificate for the domain storm.debian.net has expired yesterday. > > > > > > The site is not listed on https:

Re: Porterbox - impossible efficient debugging?

On Tue, Aug 13, 2024 at 12:15:22PM +0200, julien.pu...@gmail.com wrote: > And of course, this is where I came to my wits' end: I can compile the > new elpi successfully... but I have no way to install this new elpi > binary packages in the schroot to test it against different coq-elpi! Yes, the us

Re: Porterbox - impossible efficient debugging?

On Tue, Aug 13, 2024 at 01:35:03PM +0200, julien.pu...@gmail.com wrote: > > > And of course, this is where I came to my wits' end: I can compile > > > the > > > new elpi successfully... but I have no way to install this new elpi > > > binary packages in the schroot to test it against different coq-

Re: Python2 idiosyncrasies in Python3 scripts

On Thu, Aug 15, 2024 at 12:11:55PM +0200, Jerome BENOIT wrote: > is there a reliable way to isolate Python2 idiosyncrasies in Python3 scripts ? Do you mean code that still works in Python 3 but can be simplified? Lots of linters do this in whole or in part, though I don't have suggestions for some

Re: Python2 idiosyncrasies in Python3 scripts

On Thu, Aug 15, 2024 at 01:11:23PM +0200, Jerome BENOIT wrote: > > > is there a reliable way to isolate Python2 idiosyncrasies in Python3 > > > scripts ? > > > > Do you mean code that still works in Python 3 but can be simplified? > > Lots of linters do this in whole or in part, though I don't ha

Re: Accepting DEP14?

On Fri, Aug 16, 2024 at 11:44:38AM +0200, Andreas Tille wrote: > > In #829444 it has been proposed the addition of a new "layout" option to > > gbp.conf, which would tell git-buildpackage which layout to follow, > > allowing for a graceful migration. > > > > I've been thinking about a different ap

Re: Accepting DEP14?

On Fri, Aug 16, 2024 at 03:59:07PM +0200, Andreas Tille wrote: > Am Fri, Aug 16, 2024 at 02:58:40PM +0500 schrieb Andrey Rakhmatullin: > > > > pristine-tar isn't the default either, so you need debian/gbp.conf if your > > team uses it. > > That's correct b

Re: Accepting DEP14?

On Sat, Aug 17, 2024 at 12:20:16PM +0200, Andreas Tille wrote: > My personal preference would be if we make a pristine-tar branch default > since this is what I observed in the wide majority of cases. Note that there are different opionons whether pristine-tar is needed/viable/useful. There is at

Re: Strange armel build error

On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > Hi Stephen, > > On 18/08/2024 09:04, Stephen Kitt wrote: > > On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas > > wrote: > > > Or just exclude that architecture i. e., list all archs but armel? > > If you can’t fix the build, you don’

Re: Removing more packages from unstable

On Tue, Aug 20, 2024 at 07:28:52AM +0200, Helmut Grohne wrote: > please allow me to open a can of worms. Package removal from unstable. > Deciding when it is time to remove a package from unstable is difficult. > There may be users still and it is unclear whether keeping the package > imposes a cos

Re: Removing more packages from unstable

On Tue, Aug 20, 2024 at 11:09:51AM +0200, Bastian Venthur wrote: > I think popcon does give a good approximation of how much percent of people > installed a certain package even if not everyone uses it, don't you agree? > > Last time I installed Debian it was still enabled by default. Was it? (t

Re: Removing more packages from unstable

On Tue, Aug 20, 2024 at 12:12:33PM +, Scott Kitterman wrote: > >Removing packages that aren't formally orphaned always sounds too bold to > >me, though it should be fine if we formalize a process (any process) for > >that. > > > The process currently is file an rm but against ftp.debian.org for

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

On Tue, Aug 20, 2024 at 06:35:52PM -0700, Otto Kekäläinen wrote: > Hi! > > In short: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? > > > Background: > We

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

On Tue, Aug 20, 2024 at 10:44:30PM -0700, Otto Kekäläinen wrote: > > Something that many developers are probably not aware of is that they > > can enable CI for a repository with no code changes at all and with > > a single command: > > > > salsa update_projects $NAMESPACE/$PROJECT \ > > --jobs

Re: Removing more packages from unstable

On Wed, Aug 21, 2024 at 10:06:38AM +, Holger Levsen wrote: > Hi, > > I also like us to remove more broken and unused packages from unstable. > > On Tue, Aug 20, 2024 at 11:20:10AM +0200, Lucas Nussbaum wrote: > > Maybe we could also reduce the cost of removals for users and potential > > new

Re: Removing more packages from unstable

On Wed, Aug 21, 2024 at 03:39:11PM +0200, Héctor Orón Martínez wrote: > I am surprised to not see more of those packages in the list, there > are many packages in those ecosystems with popcon between 1-10 users. popcon wasn't used when building this list though (even via the key packages condition

Re: Removing more packages from unstable

On Wed, Aug 21, 2024 at 08:40:15PM +, weepingclown wrote: > I believe at least some of these packages were probably packaged as > dependencies for packaging lazygit. I am not sure which all, but I > remember atleast gocui, pty and termbox-go to be needed by lazygit in > one way or another. Ther

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

On Fri, Aug 23, 2024 at 04:00:25PM -0400, Theodore Ts'o wrote: > On Fri, Aug 23, 2024 at 03:08:11PM +0200, Marco d'Itri wrote: > > > Salsa CI?) > > The effort needed to do so is so small that the question really should > > be "why should I NOT spend a few seconds enabling Salsa CI?". > > > > > 3)

Re: Please help me fix the build pipeline for apt-listchanges on Salsa, which is failing

On Sat, Aug 31, 2024 at 07:06:30PM -0400, Jonathan Kamens wrote: > Hey folks, > > I had to step away from working on apt-listchanges > for quite a while (nearly > a year), and upon stepping back into it today and pushing some changes to > Salsa, I

Re: Please help me fix the build pipeline for apt-listchanges on Salsa, which is failing

On Mon, Sep 02, 2024 at 11:15:50AM -0400, Jonathan Kamens wrote: > P.S. Wow, diffoscope has a /lot/ of dependencies. I understand why, but > still... wow. (Note that those are Recommends and that there is diffoscope-minimal) -- WBR, wRAR signature.asc Description: PGP signature

Re: Problem with detection of hard disks on a hub

On Sat, Apr 08, 2023 at 02:46:10PM +0200, Ralf Lehmeier wrote: > Apparently there is no solution to this - or no one cares. > That is a great pity. > Does no one use a hub with multiple external hard drives and has problems > with them being recognized? The user support list is debain-user@

Re: Problem with detection of hard disks on a hub

On Mon, Apr 10, 2023 at 08:18:59PM +0200, Ralf Lehmeier wrote: > > It will surely interest Debian developers -- but this is not the right > > list to ask. Please ask in one of the user support lists (where Debian > > developers will surely answer to your question). Your question is not > > about De

Re: AMD ryzen 5 2400G VGA drivers required for Debian 10 based linux OS

On Wed, Apr 26, 2023 at 07:11:00PM +0530, karans wrote: > Dear Debian Team > > We have Debian 10 buster based linux OS but we are facing issue after install > linux Please contact the support channels for your OS, not for Debian. > This e-mail is for the sole use of the intended recipient(s) and

Re: Dynamic linker support for FPC.

On Sun, May 28, 2023 at 06:53:51PM +0200, Abou Al Montacir wrote: > One year ago, glibc 2.32 2.32 was released in 2020 though? Unless you mean some Debian-specific changes, happened in 2021, in which case please be more specific? > introduced a change in the dynamic linker removing the functions

Re: [2016] client-side signature checking of Debian archives (Re: When should we https our mirrors?)

On Thu, Jun 01, 2023 at 07:07:04AM -0400, Michael Lazin wrote: > I realize it is work but it would be good if apt had an option for https. It does. > You can still update with FTP mirrors. Wouldn't it be a good idea to allow > using https and keep http as a fall back for those who need an http mi

Bug#1037017: ITP: python-seedir -- Package for creating, editing, and reading folder tree diagrams.

Package: wnpp Severity: wishlist Owner: Andrey Rakhmatullin X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-seedir Version : 0.4.2 Upstream Contact: Tom Earnest * URL : https://github.com/earnestt1234/seedir * License : MIT Programming

Re: Package name discord ITP: discord a modern voice & text chat app

On Mon, Jul 03, 2023 at 10:11:50AM +0200, Filippo Rusconi wrote: > I've never heard that Discord was Free Software. Of course it isn't.

Re: systmd-analyze security as a release goal

On Mon, Jul 03, 2023 at 11:40:18PM +0200, Marco d'Itri wrote: > This is a good example of what an almost fully sandboxed service looks > like: > > https://salsa.debian.org/md/rpki-client/-/blob/master/debian/rpki-client.service Cool but looks like a lot of work. Is it possible to do this without

Re: Debian 13 release schedule and Debian 15 codename announcement

On Wed, Jul 05, 2023 at 11:05:05PM +0200, Joaquín Rufo Gutierrez wrote: > No, Debian 13 will be released on 2024 occasionally. Who are you, sorry?

Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie

On Wed, Jul 12, 2023 at 12:26:52PM +0100, Simon McVittie wrote: > > From the discussions above, it seems that NetworkManager is relevant as > > well, > > though, and is being pulled in whenever a desktop task is installed (in > > addition to ifupdown or future systemd-networkd). > > What happens

Re: rejection of binary package based on file timestamp

On Thu, Jul 20, 2023 at 10:01:54AM +0200, PICCA Frederic-Emmanuel wrote: > Hello, > > I am working on two packages pyfai[4] and python-fabio[3], I have got a > rejection based on the file timestamp which seems too old. > > the bug report is here [1] and [2]. > > If you lool at python-fabio stat

Re: libgmp3c2 sources

On Mon, Jul 31, 2023 at 06:40:16AM -0400, Svetlana Karimova wrote: > Dear developers, > I work on a debian-like embedded system with quite an old kernel, so the > package libgmp3c2_2:4.3.2_armel.deb suited me perfectly. > The problem is that now I would really like to be able to build it from > sou

Re: Potential MBF: packages failing to build twice in a row

On Sat, Aug 05, 2023 at 08:10:35PM +0300, Adrian Bunk wrote: > Debian maintainers with proper git workflows are already exporting all > their changes from git to debian/patches/ as one file - currently the > preferred form of modification of a Debian package has to be in salsa > and not in our a

Re: Potential MBF: packages failing to build twice in a row

On Sat, Aug 05, 2023 at 07:20:19PM +0300, Adrian Bunk wrote: > What packages are failing, and why? > > I would expect some debhelper machinery being responsible for most of > these, e.g. perhaps some dh-whatever helper might be creating this > issue for all 1k packages in some language ecosystem

Re: Potential MBF: packages failing to build twice in a row

On Thu, Aug 10, 2023 at 02:22:30PM +0200, Lucas Nussbaum wrote: > > It might be worth to consider changing your workflow a bit and work with > > a git repository. It does not have to be a clone of the repository (if > > any) where the package is maintained, you can start with a fresh import, > > e.

Re: Bug#1052421: ITP: control -- Python Control Systems Library

On Thu, Sep 21, 2023 at 08:20:20PM +0200, Christoph Biedl wrote: > > * Package name: control > > Version : 0.9.4 > > Upstream Author : > > > > * URL : http://python-control.org/ > > While I cannot judge whether this package is a sensible addition to > Debian - I strong

Re: Bug#1052421: ITP: control -- Python Control Systems Library

On Thu, Sep 21, 2023 at 08:37:53PM +, Kurva Prashanth wrote: > It seems debian python team following certain convention when naming > packages for python modules, libraries prefixed with "python-" and > python3 packages are prefixed with "pyhton3-". python3- prefixes for binary packages are man

Re: Control header sent with done email didn't do what I expected, should it have?

On Mon, Sep 25, 2023 at 02:06:44PM +0100, Peter B wrote: > > I recently tried to close a bug, explain why, and set a "wontfix" tag > > all at once by sending my explanation to ###-d...@bugs.debian.org with > > "Control: tags ### wontfix" as the first line of my message body. The > > bug was closed

Re: Control header sent with done email didn't do what I expected, should it have?

On Mon, Sep 25, 2023 at 02:44:19PM +0100, Peter B wrote: > On 25/09/2023 14:25, Jonathan Kamens wrote: > > > > So putting a Control: line in the pseudo-header of a message sent to > > ###-d...@bugs.debian.org doesn't work at all? > > > > It should work if the syntax is correct. The + character

Re: Control header sent with done email didn't do what I expected, should it have?

On Mon, Sep 25, 2023 at 10:04:17AM -0400, Jonathan Kamens wrote: > I did find this here after I emailed > the list: > >QUESTION: Can you do all the control-server actions by using fields >in a pseudo header in an email to bugnumber@b.d.o >

Re: Control header sent with done email didn't do what I expected, should it have?

On Mon, Sep 25, 2023 at 07:16:56AM -0400, Jonathan Kamens wrote: > I recently tried to close a bug, explain why, and set a "wontfix" tag all at > once by sending my explanation to ###-d...@bugs.debian.org with "Control: > tags ### wontfix" as the first line of my message body. The bug was closed >

Re: Control header sent with done email didn't do what I expected, should it have?

On Mon, Sep 25, 2023 at 12:55:16PM -0400, Jonathan Kamens wrote: > All that aside, in this particular case I closed the bug because it wasn't > actually a bug, but rather a PEBKAC issue (user complaining that a program > wasn't respecting his locale when he had LC_ALL set to "C" so he was > essenti

Re: Control header sent with done email didn't do what I expected, should it have?

On Mon, Sep 25, 2023 at 01:55:22PM -0400, Jonathan Kamens wrote: > The documentation you inked to does not specify a tag that can be used > specifically to mark something as not actually a bug. Yes, we just close those. The Debian BTS is not as rich as e.g. a typical bugzilla installation in this r

Re: Illegal Instruction Using sudo in Bookworm on i686

On Tue, Oct 17, 2023 at 10:57:41AM -0500, Justin wrote: > Any other information I can provide that would help track this down? Track what down, sorry? It seems to me you already understand the reason for this error? Or are you asking how to make sure that your CPU indeed doesn't support this?

Re: Illegal Instruction Using sudo in Bookworm on i686

On Tue, Oct 17, 2023 at 02:38:40PM -0500, Justin wrote: > Okay, so because the VIA C3 Nehemaiah chip doesn't properly implement > ENDBR32, it falls outside of the supported hardware, despite being otherwise > an "i686 class chip," correct? Seems correct to me. > Or put another way, in classic Cy

Re: What would help the most?

On Fri, Oct 27, 2023 at 02:00:45PM -0500, Lukasz Szybalski wrote: > Hello > I wanted to understand better from people with y...@debian.org email address > on: > > Vision of Debian: > Create a free operating system, freely available for everyone. > > Goal: > Helping customers achieve outcome. Sorr

Re: What would help the most?

On Mon, Oct 30, 2023 at 07:03:38AM +0100, deb...@hyperborg.com wrote: > Hi, > > I have the feeling, that this is some kind of semi-AI generated chat. > I think we should stop it now. Makes sense.

Re: What would help the most?

On Mon, Oct 30, 2023 at 02:48:24PM -0500, Lukasz Szybalski wrote: > It's not an AI guy. > > This is a question of, as a debian developer @debian.org...what do you need > right now? What would help you? > > Example without giving direction..or inserting things... more cs grads > working bugs or mo

Re: reference Debian package of multiple binaries sharing one man page

On Fri, Nov 10, 2023 at 11:44:06AM -0800, Russ Allbery wrote: > The good news is that if you're using debhelper, you don't have to care > about how man handles these indirections and can just use a symlink. > Install the man page into usr/share/man/man1 under whatever name is > canonical (possibly

Re: bring a newer version of a package into stable (nsis-3.09-1 into Debian "bookworm")

On Fri, Dec 22, 2023 at 01:55:59PM +0100, Thomas Gaugler wrote: > Hi, > > I thought a package in Debian "bookworm" could be updated via a "bookworm > proposed updates request" . > > It looks like I did not fully understand the process. Therefore I kindly ask > for

Re: How to build debian transitional package without source code?

On Wed, Dec 27, 2023 at 04:36:01PM -0500, Kaiqi Z wrote: > Hello Debian Community, > > I need to define a transitional package like debian Renaming Packages Method > . > > Since it is transitional it should not contain any actual

Re: [Pkg-pascal-devel] Issue with fpc_3.2.2+dfsg-24 in Sid.

On Sat, Dec 30, 2023 at 10:58:58AM +0100, Abou Al Montacir wrote: > > I see only two possibilities, either upload manually fpc_3.2.2+dfsg-25 for > > each missing architecture, or get fpc_3.2.2+dfsg-24 removed from archive and > > replaced by fpc_3.2.2+dfsg-23 so that fpc_3.2.2+dfsg-25 can be built.

Re: DebGPT: how LLM can help debian development? demo available.

On Wed, Jan 03, 2024 at 09:58:33AM +0200, Andrius Merkys wrote: > To me the most time consuming task in Debian recently is the Python > transitions. I wonder whether DebGPT could help with them. Maybe there are > other, non-Debian-specific GPTs for this task, but I would prefer a Debian > one. As "

Re: DebGPT: how LLM can help debian development? demo available.

On Wed, Jan 03, 2024 at 11:33:06AM +0200, Andrius Merkys wrote: > On 2024-01-03 11:12, Andrey Rakhmatullin wrote: > > On Wed, Jan 03, 2024 at 09:58:33AM +0200, Andrius Merkys wrote: > > > To me the most time consuming task in Debian recently is the Python > > > transitio

Re: Drawbacks of lack of mandated packaging workflow (Was: Re: Bug#1036884: 64-bit time_t: updated archive analysis, proposed transition plan with timeline)

On Sun, Jan 07, 2024 at 02:23:32AM +0900, Simon Richter wrote: > > Aren't all these problems just inherent in Debian's lack of a mandated > > packaging tooling and workflow [1,2]? > > We have a mandated tooling and workflow. > > The tooling follows an interface that is defined in Policy. The inte

Re: lazarus is marked for autoremoval from testing

On Tue, Feb 13, 2024 at 08:06:55AM +0100, Abou Al Montacir wrote: > > It is affected by these RC bugs: > > 1061034: lcl-utils-3.0: lcl-utils-3.0 Missing dependencies for lazbuild > >  https://bugs.debian.org/1061034 > I really don't understand this message. > the bug was fixed and is marked as so i

Re: Re: time_t progress report

On Sat, Mar 23, 2024 at 04:50:48PM -0500, Steven Robbins wrote: > Wondering about the current state of this transition. It's still in the stage of re-bootstrapping armel and armhf. https://buildd.debian.org/stats/armel.png https://buildd.debian.org/stats/armhf.png https://buildd.debian.org/stats/g

Re: Validating tarballs against git repositories

On Sat, Mar 30, 2024 at 09:58:22AM +0100, Ingo Jürgensmann wrote: > > Yes. In that specific case, the original xz maintainer (Lasse Collin) > > was socially-pressed by a likely fake person (Jigar Kumar) to do the > > "right thing" and hand over maintenance. > > https://www.mail-archive.com/xz-devel

Re: xz backdoor

On Sat, Mar 30, 2024 at 10:49:33AM +0200, Jonathan Carter wrote: > Another big question for me is whether I should really still > package/upload/etc from an unstable machine. It seems that it may be prudent > to consider it best practice to work from stable machines where any private > keys are inv

Re: xz backdoor

On Sat, Mar 30, 2024 at 05:00:26PM +0100, Marco d'Itri wrote: > On Mar 30, Jonathan Carter wrote: > > > Another big question for me is whether I should really still > > package/upload/etc from an unstable machine. It seems that it may be prudent > If we do not use unstable for development then wh

Re: Validating tarballs against git repositories

On Sat, Mar 30, 2024 at 10:56:40AM +0100, Iustin Pop wrote: > > Now it is time to take a step forward: > > > > 1. new upstream release; > > 2. the DD/DM merges the upstream release VCS into the Debian VCS; > > 3. the buildd is notified of the new release; > > 4. the buildd creates and uploads the

Re: xz backdoor

On Sat, Mar 30, 2024 at 08:52:29PM +0100, Ansgar 🙀 wrote: > Hi, > > On Sun, 2024-03-31 at 00:40 +0500, Andrey Rakhmatullin wrote: > > On Sat, Mar 30, 2024 at 05:00:26PM +0100, Marco d'Itri wrote: > > > > > I think that the real question is whether we should

Re: Some t64 libraries already in testing; I'm confused

On Sat, Mar 30, 2024 at 10:41:55PM +, Julian Gilbey wrote: > My very limited understanding of this major transition was that the > t64 libraries are being held in unstable until (almost) everything is > ready, at which point there will be a coordinated migration into > testing. But I've now be

Re: xz backdoor

On Sat, Mar 30, 2024 at 11:22:33PM -0300, Santiago Ruano Rincón wrote: > > I agree that dogfooding is important for discovering quality issues, but > > I think it's a poor argument for discovering security issues, especially > > if it concerns a host which is used for building and signing packages.

Re: Some t64 libraries already in testing; I'm confused

On Sun, Mar 31, 2024 at 11:22:05AM +0200, Andreas Metzler wrote: > hdf5 1.10.10+repack-3.3 This one has an unanswered question from the maintainer in the NMU report, and I feel like the reason for the missing line is the package having debian/control.in. -- WBR, wRAR signature.asc Description:

  1   2   3   >