On October 15, 2024 12:20:27 PM UTC, Guillem Jover wrote:
>Hi!
>
>On Tue, 2024-10-08 at 09:01:06 +0200, Simon Josefsson wrote:
>> 1) Take current non-OpenBSD 'signify' source package and upload NEW
>> 'signify-mail' with d/control modified as:
>>
>> Source: signify-mail
>> ...
>> Package: sign
On September 5, 2024 3:39:35 PM UTC, Andreas Tille wrote:
>Hi,
>
>Am Wed, Sep 04, 2024 at 11:29:39PM -0400 schrieb Scott Kitterman:
>> On Wednesday, September 4, 2024 6:22:14 PM EDT Pierre-Elliott Bécue wrote:
>> >
>> > OoC, what is your point, especially
On Wednesday, September 4, 2024 6:22:14 PM EDT Pierre-Elliott Bécue wrote:
> Scott Kitterman wrote on 04/09/2024 at 06:23:50+0200:
> > On Monday, September 2, 2024 11:23:30 AM EDT Andreas Tille wrote:
> > ...
> >
> >> While I’ve read several emails in agreement, Sco
On Monday, September 2, 2024 11:23:30 AM EDT Andreas Tille wrote:
...
> While I’ve read several emails in agreement, Scott Kitterman made a
> valid point[ru4]: "I don't think we need more process. We just need
> someone to do the work of finding the packages and filing the bu
On August 20, 2024 12:16:47 PM UTC, Andrey Rakhmatullin wrote:
>On Tue, Aug 20, 2024 at 12:12:33PM +0000, 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
On August 20, 2024 7:46:05 AM UTC, Andrey Rakhmatullin wrote:
>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 use
On July 2, 2024 12:26:49 AM UTC, Soren Stoutner wrote:
>Alec,
>
>On Monday, July 1, 2024 5:19:37 PM MST Alec Leamas wrote:
>> For Debian users we backport opencpn which works well. However, the
>> Ubuntu backport process is, well, interesting (been there, done that).
>>
>> The PPA represents a
On July 1, 2024 11:25:59 PM UTC, Alec Leamas wrote:
>On 02/07/2024 01:19, Alec Leamas wrote:
>
>> Let's drop this subthread, keeping eyes on the ball: what is a sane version?
>
>Looking at this from another point of view: is there any situation where an
>epoch is appropriate?
Yes. I don't th
On Monday, July 1, 2024 7:07:16 PM EDT Alec Leamas wrote:
> On 02/07/2024 00:54, Scott Kitterman wrote:
> > On Monday, July 1, 2024 6:46:06 PM EDT Alec Leamas wrote:
> >> If you switch hats for a moment: have you any advice for upstream in
> >> this situation?
> >
On Monday, July 1, 2024 6:46:06 PM EDT Alec Leamas wrote:
> On 02/07/2024 00:31, Scott Kitterman wrote:
>
> HI again
>
> > On July 1, 2024 10:18:07 PM UTC, Alec Leamas
wrote:
> >> But here the situation is that upstream do care and wants to fix it. But
> >&
On July 1, 2024 10:18:07 PM UTC, Alec Leamas wrote:
>On 02/07/2024 00:10, Scott Kitterman wrote:
>
>Hi Scott,
>
>> Upstream can change the versioning however they want. They are upstream. If
>> they don't care to fix it, then I think we assume they are fine
On Monday, July 1, 2024 5:59:00 PM EDT Alec Leamas wrote:
> On 01/07/2024 21:51, Andrey Rakhmatullin wrote:
>
> Hi Andrey.
>
> Thanks for input.
>
> > On Mon, Jul 01, 2024 at 09:46:11PM +0200, Alec Leamas wrote:
> >> After some thought, I tend to think that adding an epoch is the right
> >> thin
On May 26, 2024 6:14:40 PM UTC, Bastian Blank wrote:
>On Sun, May 26, 2024 at 05:43:54PM +0000, Scott Kitterman wrote:
>> On May 26, 2024 5:35:27 PM UTC, Santiago Vila wrote:
>> >https://people.debian.org/~sanvila/build-logs/trixie-time-bomb/
>> The clamav issue loo
On May 26, 2024 5:35:27 PM UTC, Santiago Vila wrote:
>Greetings.
>
>After we make a stable release, there is usually a constant flow
>of packages which start to FTBFS due to "time bombs", i.e. expired
>SSL certificates used in tests and other similar reasons.
>
>This is not fun for anybody tryi
On May 20, 2024 7:54:46 PM UTC, Bernd Zeimetz wrote:
>Hi,
>
>On Sun, 2024-04-07 at 16:44 +0200, Andreas Tille wrote:
>>
>> Do you think that mandating Salsa is a sensible step in this
>> direction?
>
>
>Absolutely.
>
>Also I think requiring a common git layout and the usage of recent
>versions
On May 19, 2024 11:00:23 AM UTC, Andrey Rakhmatullin wrote:
>On Sun, May 19, 2024 at 12:49:29PM +0200, Andreas Tille wrote:
>> > It also fails as an archive QA tool in my view since the FTP masters have
>> > been unwilling to upgrade to any recent version of lintian.
>>
>> Perhaps a ftpmaster
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-gfloat
Version : 0.1
Upstream Contact: Andrew Fitzgibbon
* URL : https://github.com/graphcore-research/gfloat
* License : Expat
On April 9, 2024 6:37:23 PM UTC, Holger Levsen wrote:
>hi,
>
>just adding some random data points to this thread:
>
>- I love git.
>- I very much dislike git-buildpackage, too much magic. I try to avoid it
> where I can.
>- I like salsa. (though I think for many new contributors this is rather
On Monday, April 8, 2024 12:48:13 PM EDT Marc Haber wrote:
> > > "we replace exim with postfix as the default MTA",
> >
> > A, this question always makes me wonder: If our default MTA is exim
> > why do I have such a hard time to find documents about exim in wiki.d.o
> > while there is always
On March 15, 2024 3:54:05 AM UTC, Steven Robbins wrote:
>According to the "action needed" section for nifticlib [1], it is:
>
>Marked for autoremoval on 31 March: #1063178
>
>But that bug is fixed for the version in unstable.
>Why does that cause the package to be removed?
>
>[1] https://trac
On February 16, 2024 1:11:34 AM UTC, "Marcos Rodrigues de Carvalho (aka oday)"
wrote:
>Package: wnpp
>Severity: wishlist
>Owner: "Marcos Rodrigues de Carvalho (aka oday)"
>X-Debbugs-Cc: debian-devel@lists.debian.org, marcosrcarvalh...@gmail.com
>
>* Package name: asn
> Version :
On February 2, 2024 4:43:52 PM UTC, Steve Langasek wrote:
>Hello,
>
>debian-devel-announce wouldn't let me attach the file, but for those on
>debian-devel at least, you can find the dd-list of to-be-NMUed source
>packages attached.
Thanks,
How are you handling the case where there's already a
On January 7, 2024 7:39:57 PM UTC, Ansgar wrote:
>Hi,
>
>I would like to extend Debian Policy on libraries depending on services
>(daemons) that they can speak to.
>
>Let me bring to examples, one made up,, one for which I filed a bug
>recently. But as far as I can tell this question comes up f
On September 29, 2023 10:01:45 AM UTC, Adam Borowski
wrote:
>On Thu, Sep 28, 2023 at 03:45:14PM +0000, Scott Kitterman wrote:
>> On September 28, 2023 3:22:20 PM UTC, Bastian Germann
>> wrote:
>> >Okay. What do you suggest for "team maintained" packages
On September 28, 2023 3:22:20 PM UTC, Bastian Germann wrote:
>Okay. What do you suggest for "team maintained" packages where there is no
>active team member?
>File MIA processes for each of the uploaders? And then? The MIA team's bugs
>are not RC bugs,
>so you cannot even NMU them based on th
On Thursday, September 14, 2023 11:03:07 PM EDT Paul Wise wrote:
Several packages ...
> Recommends: xml2rfc
...
For IETF RFC development, there are specific fonts that are required for the
PDF format (these are Recommends not Depends because very few RFCs need to be
in the PDF format, so most pe
On August 13, 2023 8:28:08 PM UTC, Johannes Schauer Marin Rodrigues
wrote:
>Hi,
>
>Quoting Simon McVittie (2023-08-06 12:27:04)
>> On Sat, 05 Aug 2023 at 21:29:08 +0200, Andrey Rakhmatullin wrote:
>> > I expect all Python packages that ship
>> > $name.egg-info and don't remove it in clean and
On August 9, 2023 5:55:41 PM UTC, Johannes Schauer Marin Rodrigues
wrote:
>Hi,
>
>Quoting Stefano Rivera (2023-08-09 14:38:56)
>> Personally, I have my sbuild configured to build a source package after the
>> build, so that I can be sure that I don't regress my own packages' clean
>> target. I
On August 5, 2023 7:07:34 PM UTC, "Timo Röhling" wrote:
>Hi Lucas,
>
>* Lucas Nussbaum [2023-08-05 17:06]:
>> An example sbuild invocation to reproduce failures is:
>[omitted the command line equivalent of Tolstoy's War and Peace]
>
>If we decide that this issue is important enough that people
On August 5, 2023 5:40:36 PM UTC, Andrey Rakhmatullin wrote:
>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 mo
On Saturday, August 5, 2023 11:06:27 AM EDT Lucas Nussbaum wrote:
> Hi,
>
> Debian Policy section 4.9 says:
> clean (required)
> This must undo any effects that the build and binary targets may
> have had, except that it should leave alone any output files
> created in the parent
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: aioquic
Version : 0.9.21
Upstream Author : Jeremy Lainé
* URL : https://github.com/aiortc/aioquic
* License
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: pylsqpack
Version : 0.3.17
Upstream Author : Jeremy Lainé
* URL : https://github.com/aiortc/pylsqpack
* License
On Thursday, June 29, 2023 3:55:11 PM EDT Matthew Vernon wrote:
> Hi,
>
> On 13/11/2021 11:41, Matthew Vernon wrote:
> > TL;DR> pcre3 is obsolete and upstream don't want to fix it any more. I
> > propose a MBF to track our progress in getting rid of it for Bookworm
>
> Bookworm is now out; I will
On Monday, June 26, 2023 2:02:24 PM EDT Bastian Blank wrote:
> On Mon, Jun 26, 2023 at 01:22:38PM -0400, Scott Kitterman wrote:
> > > Less prone to errors than a manual process might be to watch
> > > automatically where legacy startup scripts disappear anyway; it's not
On Monday, June 26, 2023 11:52:05 AM EDT Wouter Verhelst wrote:
> On Sun, Jun 25, 2023 at 10:31:35PM +0100, Luca Boccassi wrote:
> > On Sun, 25 Jun 2023 at 22:29, Luca Boccassi wrote:
> > > Hi,
> > >
> > > According to Lintian there are 314 packages shipping init scripts
> > > without a correspon
On Monday, June 26, 2023 12:45:11 PM EDT Ansgar wrote:
> On Sun, 2023-06-25 at 11:15 -0700, Russ Allbery wrote:
> > Bastian Blank writes:
> > > Sorry no. Please add a conversion layer that adopts service and
> > > maybe other systemd units to initrc if you care about it. This is
> > > what syste
On Saturday, June 10, 2023 2:49:29 AM EDT Paul Wise wrote:
> On Fri, 2023-06-09 at 12:46 +0200, Gürkan Myczko wrote:
> >Description : Update and verify unofficial Clam Anti-Virus
> > signatures This is a sibling of the Clam Anti-Virus freshclam utility. It
> > allows downloading virus defin
On Friday, June 9, 2023 6:46:01 AM EDT Gürkan Myczko wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Gürkan Myczko
> X-Debbugs-Cc: debian-devel@lists.debian.org, maeg...@ee.ethz.ch,
> car...@debian.org
>
> * Package name: fangfrisch
>Version : 1.6.1
>Upstream Authors: Ral
On March 4, 2023 5:25:35 PM UTC, Adrian Bunk wrote:
>On Wed, Mar 01, 2023 at 05:54:38PM -0700, Sean Whitton wrote:
>> Hello,
>
>Hi Sean,
>
>> On Sun 26 Feb 2023 at 11:38PM +02, Adrian Bunk wrote:
>>
>> > On Sun, Feb 26, 2023 at 09:57:34PM +0100, Diederik de Haas wrote:
>> >> On Sunday, 26 Febr
On February 22, 2023 9:38:48 PM UTC, Sam Hartman wrote:
>> "Peter" == Peter Pentchev writes:
>
>Peter> 3. Now, what about the `Files: debian/*` section of the
>Peter> debian/copyright file? The common wisdom seems to be that, if
>Peter> only to make it easier to submit patches
On February 22, 2023 2:29:08 PM UTC, Jonas Smedegaard wrote:
>Quoting Peter Pentchev (2023-02-22 14:26:47)
>> On Wed, Feb 22, 2023 at 01:55:02PM +0100, Jonas Smedegaard wrote:
>> > Quoting Peter Pentchev (2023-02-22 10:49:30)
>> > > So I've seen this idea floating around in the past couple of y
On February 22, 2023 9:49:30 AM UTC, Peter Pentchev wrote:
>Hi,
>
>So I've seen this idea floating around in the past couple of years
>(and in some places even earlier), but I started doing it for
>the couple of pieces of software that I am upstream for after reading
>Daniel Stenberg's blog ent
On January 17, 2023 2:39:32 PM UTC, Helmut Grohne wrote:
>Hi Jonathan,
>
>Thanks for your review.
>
>On Tue, Jan 17, 2023 at 02:12:10PM +, Jonathan Dowland wrote:
>> I'm not sure that alternatives is appropriate, if the commands are not
>> interchangeable. And they are not: if you have 1 &
On Tuesday, November 22, 2022 2:32:11 PM EST Sandro-Alessio Gierens wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Sandro-Alessio Gierens
>
> * Package name: ranges
> Version : 1.0.0
> Upstream Author : Sandro-Alessio Gierens
> * URL : https://github.com/gierens
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: python-noseofyeti
Version : 2.3.1
Upstream Author : Stephen Moore
* URL : https://github.com/delfick/nose-of-yeti
On Sunday, August 28, 2022 11:53:50 PM EDT Russ Allbery wrote:
> Scott Kitterman writes:
> > Sean Whitton wrote:
> >> I think we still want the binary package namespace checking?
> >>
> >> I.e., a GR just saying "ftpteam should not do a full
> >>
On August 28, 2022 8:58:24 PM UTC, Sean Whitton
wrote:
>Hello,
>
>On Sun 28 Aug 2022 at 07:45AM +02, Andreas Tille wrote:
>
>>
>> Am Sat, Aug 27, 2022 at 09:53:40AM -0400 schrieb M. Zhou:
>>> In my fuzzy memory, the last discussion on NEW queue improvement
>>> involves the disadvantages by all
On July 30, 2022 6:15:30 PM UTC, Dima Kogan wrote:
>Hi. This probably has been covered before, but it's so consistently
>annoying that I'd like to bring it up again.
>
>Currently the Debian build tools strongly encourage packages to have
>exactly
>
> Build-Depends: debhelper-compat (= 13)
>
>T
On June 27, 2022 1:06:10 AM UTC, Russ Allbery wrote:
>Ben Finney writes:
>
>> My guess is that this is something to do with an update to the signing
>> GnuPG key expiry date. I can get into that in a different thread if
>> needed. The trouble is, I can only guess, because there are no messages
On May 1, 2022 4:44:21 PM UTC, "Timo Röhling" wrote:
>* Scott Kitterman [2022-04-29 23:32]:
>> I don't understand why this is any better than just rejecting the
>> package? Once it's been determined that the upload won't be
>> accepted, I don&
On April 29, 2022 11:44:54 PM UTC, Paul Wise wrote:
>On Fri, 2022-04-29 at 23:32 +0000, Scott Kitterman wrote:
>
>> I don't understand why this is any better than just rejecting the
>> package? Once it's been determined that the upload won't be
>> accep
On April 29, 2022 11:04:57 PM UTC, Paul Wise wrote:
>On Fri, 2022-04-29 at 13:36 +0100, Steve McIntyre wrote:
>
>> Just to clarify: is this suggesting that packages from NEW would end
>> up in the archive even with serious bugs? If not, what's the point of
>> the "eventual removal" above? I'm n
On Friday, April 29, 2022 12:08:21 PM EDT Andreas Tille wrote:
> Hi Scott,
>
> thanks a lot for becoming involved into this discussion.
>
> Am Fri, Apr 29, 2022 at 11:26:33AM -0400 schrieb Scott Kitterman:
> > 2. Not rejecting packages with serious defects:
> >
&g
On Wednesday, April 27, 2022 8:54:05 PM EDT Paul Wise wrote:
> Hi all,
>
> During the discussions about NEW on debian-devel in recent times, I had
> the idea that instead of the current mechanism of sending REJECT mails,
> Debian could switch to using the BTS for most feedback on NEW packages.
>
On Monday, February 21, 2022 12:40:26 PM EST Peter Pentchev wrote:
> On Mon, Feb 21, 2022 at 11:40:36AM +0100, Andreas Tille wrote:
> > Hi,
> >
> > there was a (private) request to upgrade libzstd to latest 1.5.2.
> >
> > I'd like to repeat that I'm really convinced that libzstd should *not*
> >
On Thursday, February 10, 2022 9:13:29 AM EST The Wanderer wrote:
> On 2022-02-10 at 09:06, Scott Kitterman wrote:
> > On Thursday, February 10, 2022 8:26:23 AM EST Simon McVittie wrote:
> >> I think the copyright file is doing several things which are perhaps in
> >> co
On Thursday, February 10, 2022 8:26:23 AM EST Simon McVittie wrote:
> On Tue, 08 Feb 2022 at 08:59:23 -0500, Scott Kitterman wrote:
> > From my point of view, treating something like other common classes of RC
> > bugs means that the project is producing tools and processes to mak
On Tuesday, February 8, 2022 2:45:18 PM EST Paul Gevers wrote:
> Hi,
>
> Release Team member hat on, but not speaking on behalf of the team. I
> haven't consulted anybody on the idea I mention below.
>
> On 08-02-2022 14:59, Scott Kitterman wrote:
>
> > If peo
On Tuesday, February 8, 2022 2:38:29 PM EST Russ Allbery wrote:
> Scott Kitterman writes:
> > Technically it would be the simplest, but there's a process for policy
> > changes that's more involved than writing emails to d-devel. I'm
> > suggesting you enga
1:27:19 PM EST Stephan Lachnit wrote:
> The easy solution would just be allow both. Either only a single file with
> verbatim text or an SPDX document with licenses in a separate folder.
>
> Regards,
> Stephan
>
> On Tue, 8 Feb 2022, 19:12 Scott Kitterman, wrote:
> >
On Tuesday, February 8, 2022 12:53:22 PM EST Stephan Lachnit wrote:
> On Tue, Feb 8, 2022 at 5:00 PM Scott Kitterman wrote:
> > Since Debian policy requires verbatim copies of licenses (or links to
> > /usr/
> > share/common-licenses), I think any policy compliant debian/co
On Tuesday, February 8, 2022 10:39:36 AM EST Jonas Smedegaard wrote:
> Quoting Stephan Lachnit (2022-01-26 12:49:34)
>
> > - What is an SPDX bill of materials?
> > It is a machine-readable format that specifies the licenses of each
> > file in tag/value style like DEP-5. However compared to DEP-5
On Tuesday, February 8, 2022 8:23:36 AM EST Andreas Tille wrote:
> Am Fri, Feb 04, 2022 at 09:39:09AM -0800 schrieb Russ Allbery:
> > Various people have different reactions to and opinions about the
> > necessity of this review, which I understand and which is great for
> > broadening the discussi
On February 8, 2022 2:38:48 AM UTC, Holger Levsen wrote:
>On Mon, Feb 07, 2022 at 09:28:16PM -0500, Theodore Ts'o wrote:
>> The argument why a package which has an upstream-induced shared
>> library version bump, has to go through the entire NEW gauntlet [...]
>
>I hear your frustration but don
On February 7, 2022 6:00:16 PM UTC, John Goerzen wrote:
>
>On Mon, Feb 07 2022, Theodore Ts'o wrote:
>
>> If we can't do anything else, I suspect we can reduce project a
>> friction a lot of we only subject packages to copyright hazing when it
>> is a NEW source package, and not when there is a
On Friday, February 4, 2022 6:24:56 PM EST Philip Hands wrote:
> Scott Kitterman writes:
>
> ...
>
> > Currently the only answer is join the FTP Team as a trainee when there
> > is a call for volunteers. I totally get the frustration.
>
> People could always just
On Friday, February 4, 2022 2:48:50 PM EST Russ Allbery wrote:
> Scott Kitterman writes:
> > Since we're doing strawman arguments in this thread: I disagree with the
> > notion that it's not a problem to put crap packages in the archive and
> > fix them later if an
On Friday, February 4, 2022 12:39:09 PM EST Russ Allbery wrote:
> The Wanderer writes:
> > What I read Scott as having been suggesting, by contrast, is that people
> > instead do copyright review for packages already in Debian, which may
> > well have had changes that did not have to pass through
On Friday, February 4, 2022 4:00:44 AM EST Philip Hands wrote:
> Scott Kitterman writes:
>
> ...
>
> > My impression is that people are tired of waiting on New, but no one
> > really seems to be interested in doing any work on any alternative
> > other than more
On Thursday, February 3, 2022 2:40:08 PM EST Phil Morrell wrote:
> On Thu, Feb 03, 2022 at 09:43:16AM -0500, Scott Kitterman wrote:
> > I am a member of the FTP Team and have been participating, at least a bit,
> > in this thread. I am not, however, speaking for the team.
>
&g
On Wednesday, February 2, 2022 1:21:38 PM EST Alec Leamas wrote:
> Dear list,
>
> On 02/02/2022 18:46, Michael Stone wrote:
> > On Wed, Feb 02, 2022 at 10:16:36PM +0500, Andrey Rahmatullin wrote:
> >> On Wed, Feb 02, 2022 at 12:12:30PM -0500, Michael Stone wrote:
> >>> On Wed, Feb 02, 2022 at 11:3
On Tuesday, February 1, 2022 12:18:07 PM EST Russ Allbery wrote:
> Wookey writes:
> > For what it is worth I concur with everything that Russ has written, and
> > would like to have us look at this again (and that's honestly not
> > particularly because I currenly have the honour of the 6th-oldest
On Monday, January 31, 2022 12:32:18 PM EST Russ Allbery wrote:
...
> A lawyer cannot make that risk trade-off decision for us. We'll have to
> make it as a project. But my hope would be that they could help put a
> number on the likely legal cost in the worst-case scenario and provide
> some inp
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: python-rangehttpserver
Version : 1.2.0
Upstream Author : Dan Vanderkam
* URL : https://github.com/danvk/RangeHTTPServer
* License : Apache 2.0
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: clamav-cvdupdate
Version : 1.0.2
Upstream Author : The Clamav Team
* URL : https://github.com/Cisco-Talos/cvdupdate
* License : Apache 2.0
Programming Lang: Python
Description
On Friday, January 21, 2022 1:33:07 PM EST Adam Borowski wrote:
> On Fri, Jan 21, 2022 at 01:28:54PM -0500, Scott Kitterman wrote:
> > 2. New binary package "steals" binary from another source. This is
> > sometimes OK. Sometimes it's accidental. It could
On Friday, January 21, 2022 12:19:12 PM EST Andreas Tille wrote:
> Hi Mo,
>
> Am Fri, Jan 21, 2022 at 09:51:12AM -0500 schrieb M. Zhou:
> > I'd rather propose choice C. Because I to some extent understand
> > both sides who support either A or B. I maintain bulky C++ packages,
> > and I also had a
On Thursday, December 30, 2021 9:01:07 AM EST David Bremner wrote:
> Scott Kitterman writes:
> > I believe I can solve this problem by adding Recommends: resolvconf if
> > that's the only way. I had hoped there would be some "modern" way to do
> > it from
On Thursday, December 30, 2021 8:50:48 AM EST Bjørn Mork wrote:
> Scott Kitterman writes:
> > I believe I can solve this problem by adding Recommends: resolvconf if
> > that's the only way. I had hoped there would be some "modern" way to do
> > it from
On Thursday, December 30, 2021 2:36:45 AM EST Bastian Blank wrote:
> On Thu, Dec 30, 2021 at 01:48:49AM +0000, Scott Kitterman wrote:
> > It does. My question is on the other end of the problem. Once
> > resolv.conf is updated, how do I trigger an action for another package?
&
On Thursday, December 30, 2021 2:35:56 AM EST Bastian Blank wrote:
> On Wed, Dec 29, 2021 at 04:35:22PM -0500, Scott Kitterman wrote:
> > The postfix package ships a script in /etc/resolvconf/update-libc.d/ to
> > restart postfix when resolv.conf is updated. As far as I know, that
On December 30, 2021 1:19:45 AM UTC, Adam Borowski wrote:
>On Wed, Dec 29, 2021 at 04:35:22PM -0500, Scott Kitterman wrote:
>> The postfix package ships a script in /etc/resolvconf/update-libc.d/ to
>> restart
>> postfix when resolv.conf is updated. As far as I know
The postfix package ships a script in /etc/resolvconf/update-libc.d/ to restart
postfix when resolv.conf is updated. As far as I know, that still works if the
resolvconf package is installed, but if not (i.e. Debian default), what's the
equivalent? Does systemd-resolved have an equivalent? Sh
On Wednesday, December 22, 2021 11:07:51 PM EST Sandro Tosi wrote:
> > It's not an either or.
> >
> > Generally, the Release Team should coordinate timing of transitions. New
> > libraries should be staged in Experimental first. Maintainers of rdpends
> > should be alerted to the impending trans
On December 23, 2021 12:24:16 AM UTC, Sandro Tosi wrote:
>> People are expected to do so (coordination/testing etc).
>>
>>
>> - Mistakes happen.
>>
>>
>> BUT:
>>
>>
>> - Apparently some people forgot this and deliberately don't follow (and
>> I don't mean the can-happen accidents).
>>
>> (In th
On Monday, December 6, 2021 8:58:15 AM EST Andreas Tille wrote:
> Hi Jonas,
>
> I've thought that it is probably not my turn to answer your questions
> but since there was no answer yet I'd like to report from my experience.
>
> Am Thu, Nov 18, 2021 at 05:21:45PM +0100 schrieb Jonas Smedegaard:
>
On December 5, 2021 1:51:48 AM UTC, Paul Wise wrote:
>On Sat, 2021-12-04 at 02:43 +0000, Scott Kitterman wrote:
>
>> I think that there's a security consideration associated with all these
>> proposals for externalizing finding upstream updates.
>
>Good point.
On December 3, 2021 12:12:47 PM UTC, Stephan Lachnit
wrote:
>On Thu, Dec 2, 2021 at 11:52 PM Paul Wise wrote:
>>
>> On Thu, 2021-12-02 at 23:36 +0100, Stephan Lachnit wrote:
>>
>> > If I understand correctly, release-monitoring already offers such a
>> > mapping [1].
>>
>> It seems like the A
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: python-tomli-w
Version : 0.4.0
Upstream Author : Taneli Hukkinen
* URL : https://github.com/hukkin/tomli-w
* License : Expat
Programming Lang: Python
Description : lil' TOML
On Tuesday, November 23, 2021 3:49:17 PM EST Simon Josefsson wrote:
> Michael Biebl writes:
> > Hi,
> >
> > we are early in the bookworm release cycle, so I guess it's the
> > perfect time to bring up this topic.
>
> Sorry for hijacking the thread, but perhaps now is a good time to stop
> using
On September 14, 2021 5:16:51 PM UTC, Johannes Schauer Marin Rodrigues
wrote:
>Quoting Mattia Rizzolo (2021-09-14 15:34:36)
>> On Tue, Sep 14, 2021 at 10:05:01AM +0200, Johannes Schauer Marin Rodrigues
>> wrote:
>> > Hi,
>> >
>> > Quoting Mattia Rizzolo (2021-09-06 16:39:39)
>> > > As the pb
On Wednesday, June 10, 2020 12:49:01 AM EDT Nicholas D Steeves wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Nicholas D Steeves
>
> Package name: dephell
> Version : 0.8.3
> Upstream Author : Gram
> URL : http://www.example.org/
Should be https://github.com/dephell
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: python-commentjson
Version : 0.8.3
Upstream Author : Vaidik Kapoor <https://vaidik.in/>
* URL : https://pypi.org/project/commentjson
* License : Expat
Programming Lang:
On Thursday, May 21, 2020 12:08:44 AM EDT Andreas Tille wrote:
> Hi,
>
> On Wed, May 20, 2020 at 04:30:47PM -0400, Scott Kitterman wrote:
> > On Wednesday, May 20, 2020 4:23:41 PM EDT Pierre Gruet wrote:
> > > Package: wnpp
> > > Severity: wishlis
On Wednesday, May 20, 2020 4:23:41 PM EDT Pierre Gruet wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Debian-med project
>
> * Package name: distlib
> Version : 0.9.1
> Upstream Author : Peter N. Steinmetz
> * URL : https://sourceforge.net/projects/statdistlib
>
On Monday, May 11, 2020 9:25:20 PM EDT Paul Wise wrote:
> > Should we also be triaging the bugs filed against removed versioned
> > source packages like golang-1.9 or python3.6?
>
> No response on this yet.
In cases like this, maintainers that want them moved can do it reasonably
easily. I woul
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: python-tomlkit
Version : 0.6.0
Upstream Author : Sébastien Eustace
* URL : https://pypi.org/project/tomlkit
* License : Expat
Programming Lang: Python
Description : style
On Saturday, May 2, 2020 11:53:26 AM EDT Andreas Metzler wrote:
> In gmane.linux.debian.devel.general Niels Thykier wrote:
> [...]
>
> > 3) We followed up with an [update to the proposal] were debhelper would
> >
> > optionally expose some of the relevant directories (some by default,
> >
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: python-resolvelib
Version : 0.3.0
Upstream Author : Tzu-ping Chung
* URL : https://github.com/sarugaku/resolvelib
* License : ISC
Programming Lang: Python
Description : module to
1 - 100 of 508 matches
Mail list logo
