Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org,
debian-as...@lists.debian.org, debian-scie...@lists.debian.org
* Package name: unyt
Version : 2.8.0
Upstream Author : Nathan Goldbaum
* URL
Today's update, Debian test can't read my windows partition. I fix it
inside the bios configuration.
El mié, 25 de ago. de 2021 a la(s) 15:27, Aurelien Jarno (
aurel...@aurel32.net) escribió:
> On 2021-08-20 23:15, Simon Richter wrote:
> > I think that one of the release goals should be that any
On 0825, Simon Richter wrote:
>Hi,
>
>On 8/25/21 1:21 AM, Sean Whitton wrote:
>
>> From my point of view, signing git tags is no less well established a
>>best practice than signing tarballs -- in fact, to me, it seems *more*
>>well established.
>
>That is ecosystem dependent.
>
>FWIW, I'd love to
Hi!
On Sun, 2021-08-22 at 09:18:25 +0200, Andreas Metzler wrote:
> Afaict we have still no idea on how to move on.
>
> 1 I think you agree that there is a significant number of usrmerged Debian
> installations out there. It does not really matter whether there are 7% or
> 40%. They exist and
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-spinners
Version : 0.0~git20200220.a73d561
Upstream Author : Manraj Singh
* URL : https://github.com/manrajgrover/py-spinners
* License
> "Simon" == Simon Richter writes:
Simon> Hi,
Simon> On 8/16/21 3:18 AM, Paul Wise wrote:
>> I'd like to suggest that we standardise on the upstream VCS for
>> our orig.tar.gz files and phase out use of upstream packaging
>> ecosystems.
Simon> This is also an additio
Package: wnpp
Severity: wishlist
Owner: James Valleroy
X-Debbugs-Cc: debian-devel@lists.debian.org, jvalle...@mailbox.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: erlang-poolboy
Version : 1.5.2
Upstream Author : Devin Torres
* URL : https://git
Simon Richter:
> Hi,
>
> On 25.08.21 21:45, Sam Hartman wrote:
>
>> The dpkg maintainer hasn't been happy with the discussions here, and
>> I think facilitating to a level where Guillem is part of the
>> consensus is beyond my skill.
>
> The discussion so far has been around the question whether
Sam Hartman:
>> "Niels" == Niels Thykier writes:
>
> Niels> As I understand it, the issue does not depend on whether
> Niels> "usrmerge" is run before or after installing the "/lib"
> Niels> version of "foo". On that assumption, running "usrmerge" as
> Niels> a part of the up
Hi,
On 25.08.21 21:45, Sam Hartman wrote:
The dpkg maintainer hasn't been happy with the discussions here, and
I think facilitating to a level where Guillem is part of the
consensus is beyond my skill.
The discussion so far has been around the question whether there is
actually a problem and
Guillem Jover writes:
> The fact that the supporters of a *filesystem layout* have been happy to
> dismiss and ignore this and have been pushing for what I think can be
> easily described as the worst ever "transition" done in Debian, very
> sadly, for me this whole topic marks a before and after
Simon Richter writes:
> I'd expand the definition of Conflicts/Replaces though: packages that
> use names that conflict because of usrmerge would need to declare it,
> because as soon as we teach dpkg to recognize these conflicts, the
> packages would fail to install on stable.
Yes, that's proba
> "Niels" == Niels Thykier writes:
Niels> As I understand it, the issue does not depend on whether
Niels> "usrmerge" is run before or after installing the "/lib"
Niels> version of "foo". On that assumption, running "usrmerge" as
Niels> a part of the upgrade and "cleaning up"
Hi,
On 25.08.21 18:57, Russ Allbery wrote:
The problem here is also that if there are two packages like that, on an
usrmerge system, we would not know this is happening.
I agree, of course, but I don't see a way in which Policy can help with
that problem unless this packaging decision was in
On Wed, Aug 25, 2021 at 09:57:09AM -0700, Russ Allbery wrote:
> Wouter Verhelst writes:
> > On Mon, Aug 23, 2021 at 08:23:50AM -0700, Russ Allbery wrote:
>
> >> If we tried to document every random bit of buggy packaging behavior
> >> anyone thought of in Policy, Policy would become unwieldy, so
On 2021-08-20 23:15, Simon Richter wrote:
> I think that one of the release goals should be that any freshly installed
> or upgraded system should have a dpkg database that is consistent with
> reality, and I'd prioritize that higher than actually finishing the
> transition, because as long as we c
Hi,
On 25.08.21 18:42, Phil Morrell wrote:
"git archive" is reproducible, for simplicity I wouldn't use a prefix
though.
For simplicity I *would* use a prefix, purely because that's what
github/gitlab uses, so upstream can still choose to additionally sign
the distributed tarball if they wis
Sam Hartman:
>
> TL;DR: Should we hold off on moving stuff from / to /usr in packages
> until we develop our plan?
> If so, how do we communicate that to people?
>
>> "Russ" == Russ Allbery writes:
>
> Russ> Simon Richter writes:
> >> It is less nonsensical because usrmerge exists,
On Wed, 2021-08-25 at 09:57:09 -0700, Russ Allbery wrote:
> Wouter Verhelst writes:
> > The problem here is also that if there are two packages like that, on an
> > usrmerge system, we would not know this is happening.
Also this does not need to come from "buggy" packaging practices.
> I agree,
X-Debbugs-Cc: debian-devel@lists.debian.org chrom...@packages.debian.org
在 2021-08-25星期三的 19:12 +0200，Romain Porte写道：
> Package: wnpp
> Severity: wishlist
> Owner: Romain Porte
> X-Debbugs-Cc: debian-devel@lists.debian.org, deb...@microjoe.org, Debian
> Chromium Team
>
> * Package name : gn
Package: wnpp
Severity: wishlist
Owner: Romain Porte
X-Debbugs-Cc: debian-devel@lists.debian.org, deb...@microjoe.org, Debian
Chromium Team
* Package name: gn
Version : 0+git20210811
Upstream Author : Google
* URL : https://gn.googlesource.com/gn/
* License :
On 8/25/21 5:01 PM, Theodore Ts'o wrote:
> On Wed, Aug 25, 2021 at 04:11:37PM +0200, Thomas Goirand wrote:
>>
>> It's been *years* since I encounter a PyPi package that doesn't have a
>> Git repo as its homepage (and unfortunately, 99% on Github).
>>
>> I wrote this many times, but I don't see why
Wouter Verhelst writes:
> On Mon, Aug 23, 2021 at 08:23:50AM -0700, Russ Allbery wrote:
>> If we tried to document every random bit of buggy packaging behavior
>> anyone thought of in Policy, Policy would become unwieldy, so I want to
>> verify here that someone really thought having one package
On Wed, Aug 25, 2021 at 04:35:51PM +0200, Simon Richter wrote:
> > I wrote this many times, but I don't see why we should use any "upstream
> > tarball" when the Git repository itself contains the tarball with:
>
> > git archive --prefix=$(DEBPKGNAME)-$(VERSION)/ $(GIT_TAG) \
> > | xz >../$(DE
On Mon, Aug 23, 2021 at 08:23:50AM -0700, Russ Allbery wrote:
> Luca Boccassi writes:
>
> > Thank you - it has been brought up in this thread as an example of a
> > valid setup, so if it is not, I think it could be good to be extra clear
> > in the policy? How about the following:
>
> If we trie
Hi Wouter,
On 8/25/21 8:36 PM, Wouter Verhelst wrote:
> On Mon, Aug 23, 2021 at 04:12:43AM +, Paul Wise wrote:
>> On Sun, Aug 22, 2021 at 2:31 PM Aivar Annamaa wrote:
>>
>>> Is here someone, who can meet me in Tartu, Estonia or is willing to
>>> arrange this over the internet? Perhaps I could
Wouter Verhelst, le mer. 25 août 2021 17:06:39 +0200, a ecrit:
> On Mon, Aug 23, 2021 at 04:12:43AM +, Paul Wise wrote:
> > On Sun, Aug 22, 2021 at 2:31 PM Aivar Annamaa wrote:
> >
> > > Is here someone, who can meet me in Tartu, Estonia or is willing to
> > > arrange this over the internet? P
On Mon, Aug 23, 2021 at 04:12:43AM +, Paul Wise wrote:
> On Sun, Aug 22, 2021 at 2:31 PM Aivar Annamaa wrote:
>
> > Is here someone, who can meet me in Tartu, Estonia or is willing to
> > arrange this over the internet? Perhaps I could sign a statement about
> > my identity with Estonian ID ca
On Wed, Aug 25, 2021 at 04:11:37PM +0200, Thomas Goirand wrote:
>
> It's been *years* since I encounter a PyPi package that doesn't have a
> Git repo as its homepage (and unfortunately, 99% on Github).
>
> I wrote this many times, but I don't see why we should use any "upstream
> tarball" when th
On 2021-08-25 16:11:37 +0200 (+0200), Thomas Goirand wrote:
[...]
> I wrote this many times, but I don't see why we should use any "upstream
> tarball" when the Git repository itself contains the tarball with:
>
> git archive --prefix=$(DEBPKGNAME)-$(VERSION)/ $(GIT_TAG) \
> | xz >../$(DEBPK
On Wed, Aug 25, 2021 at 04:07:02PM +0200, Tomas Pospisek wrote:
> >> Is there any reasonable way to get this spelling error corrected in the
> >> changelogs across all these packages?
> > As those are specifically binNMU changelogs, I don't think so.
>
> You still can do a NMU or send a patch to t
Hi,
I wrote this many times, but I don't see why we should use any "upstream
tarball" when the Git repository itself contains the tarball with:
git archive --prefix=$(DEBPKGNAME)-$(VERSION)/ $(GIT_TAG) \
| xz >../$(DEBPKGNAME)_$(VERSION).orig.tar.xz
(which leads to a .xz, which is
On 2021-08-25 at 10:22, Sebastian Ramacher wrote:
> On 2021-08-25 16:07:02, Tomas Pospisek wrote:
>> You still can do a NMU or send a patch to the maintainer...
>
> Any future upload or binNMU will get rid of my typo without any
> additional action.
So no action is needed, this will resolve ev
On 2021-08-25 16:07:02, Tomas Pospisek wrote:
> On 25.08.21 15:23, Andrey Rahmatullin wrote:
> > On Wed, Aug 25, 2021 at 09:19:34AM -0400, The Wanderer wrote:
> >> Is there any reasonable way to get this spelling error corrected in the
> >> changelogs across all these packages?
> > As those are spe
On 8/16/21 3:18 AM, Paul Wise wrote:
> Hi all,
>
> I noticed that sometimes Debian's choice of upstream source for
> packaging can be suboptimal. This is especially apparent for the
> different per-language upstream packaging ecosystems[1], where the
> upstream packaging differs from the upstream
On 25.08.21 15:23, Andrey Rahmatullin wrote:
> On Wed, Aug 25, 2021 at 09:19:34AM -0400, The Wanderer wrote:
>> Is there any reasonable way to get this spelling error corrected in the
>> changelogs across all these packages?
> As those are specifically binNMU changelogs, I don't think so.
You sti
On Sat, Aug 21, 2021 at 10:28:04AM +0200, Wouter Verhelst wrote:
> On Thu, Aug 19, 2021 at 10:11:33PM +, Jeremy Stanley wrote:
> > On 2021-08-19 16:37:13 -0400 (-0400), Kyle Edwards wrote:
> > > On 8/19/21 3:46 PM, Simon Richter wrote:
> > > > For the most part, users would configure https if t
On Wed, Aug 25, 2021 at 09:19:34AM -0400, The Wanderer wrote:
> Is there any reasonable way to get this spelling error corrected in the
> changelogs across all these packages?
As those are specifically binNMU changelogs, I don't think so.
> Or is this too minor to be worth bothering with, and some
I'm not sure if this is worth giving any attention to, but it's the sort
of thing that's going to keep bothering me at a mild level if nothing is
done about it, so I figure I might as well at least ask.
Over the period since the release, I've seen quite a few packages show
up in testing with an a
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-redbaron
Version : 0.9.2
Upstream Author : Tin Tvrtković
* URL : https://github.com/PyCQA/redba
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-baron
Version : 0.9
Upstream Author : Tin Tvrtković
* URL : https://github.com/PyCQA/baron
* Li
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-autopage
Version : 0.4.0
Upstream Author : Zane Bitter
* URL : https://github.com/zaneb/autopage
* License : Apache-2.0
Programming Lang
On Wed, Aug 25, 2021 at 12:11:17PM +, Thiago Pezzo (tico) wrote:
> Hi, Sean,
>
> > Please consider Debian Policy too! We've got po4a infra set up.
> That would be great too. Today we'll have our team's BoF at DebConf, I'll
> talk about translating the Debian Policy.
That's all nice and dandy
Hi, Sean,
> Please consider Debian Policy too! We've got po4a infra set up.
That would be great too. Today we'll have our team's BoF at DebConf, I'll talk
about translating the Debian Policy.
Thanks!
Thiago Pezzo (Tico)
August 24, 2021 8:24 PM, "Sean Whitton" wrote:
> Hello,
>
> On Wed 18 Au
On 2021-08-23 07:43:07 +0100, Tim Woodall wrote:
> On Mon, 23 Aug 2021, Holger Wansing wrote:
> > Am 23. August 2021 07:19:26 MESZ schrieb Tomas Pospisek
> > :
> > >
> > > The thing is, if you close a bug report via `Bcc:
> > > -cl...@bugs.debian.org` then the mail that arrives at the
Hi,
On 8/25/21 1:21 AM, Sean Whitton wrote:
From my point of view, signing git tags is no less well established a
best practice than signing tarballs -- in fact, to me, it seems *more*
well established.
That is ecosystem dependent.
FWIW, I'd love to see git bundles as a source archive forma
46 matches
Mail list logo
