Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin
* Package name: pympress
Version : 1.4.1
Upstream Author : Cimbali
* URL : https://github.com/Cimbali/pympress/
* License : GPL-2+
Programming Lang: Python
Description : dual-screen PDF reader f
[trimming the cc]
> "Luke" == Luke Kenneth Casson Leighton writes:
Luke> On Mon, Aug 19, 2019 at 7:29 PM Sam Hartman
wrote:
>> Your entire argument is built on the premise that it is actually
>> desirable for these applications (compilers, linkers, etc) to
>> work in 32-bit
On Tue, Aug 20, 2019 at 1:17 PM Sam Hartman wrote:
> I'd ask you to reconsider your argument style.
that's very reasonable, and appreciated the way that you put it.
> I'm particularly frustrated that you spent your entire reply moralizing
> and ignored the technical points I made.
ah: i really
> "Luke" == Luke Kenneth Casson Leighton writes:
>> I even agree with you that we cannot address these challenges and
>> get to a point where we have confidence a large fraction of our
>> software will cross-build successfully.
Luke> sigh.
I don't really see the need for a s
Package: wnpp
Severity: wishlist
Owner: Jonathan Carter
* Package name: bcachefs-tools
Version : 0.1.0
Upstream Author : Kent Overstreet
* URL : https://evilpiepirate.org/git/bcachefs-tools.git
* License : GPL-2+
Programming Lang: C
Description : bcach
On Tue, Aug 20, 2019 at 2:52 PM Sam Hartman wrote:
> I think my concern about your approach is that you're trying to change
> how the entire world thinks.
that would be... how can i put it... an "incorrect" interpretation. i
think globally - i always have. i didn't start the NT Domains
Reverse
Hi,
I observed that lintian-brush is adding a file debian/upstream/metadata
if it finds the fields Upstream-Name and Upstream-Contact in
debian/copyright.
What is the sense to duplicate data that we can find in a well
established machine readable file in another file?
Kind regards
Andrea
> "\Luke" == Luke Kenneth Casson Leighton writes:
Hi.
First, thanks for working with you.
I'm seeing a lot more depth into where you're coming from, and it is
greatly appreciated.
\Luke> indeed.
\Luke> i do get it - i did say. i'm aware that software libre
\Luke> developers aren'
On Tue, Aug 20, 2019 at 3:31 PM Sam Hartman wrote:
>
> > "\Luke" == Luke Kenneth Casson Leighton writes:
> Hi.
> First, thanks for working with you.
> I'm seeing a lot more depth into where you're coming from, and it is
> greatly appreciated.
likewise.
> I'd like to better understand the tr
On Tue, Aug 20, 2019 at 04:21:43PM +0100, Luke Kenneth Casson Leighton wrote:
that 32-bit hardware is consigned to landfill. debian has a far
higher impact (as a leader, due to the number of ports) than i think
anyone realises. if debian says "we're dropping 32 bit hardware",
that's it, it's do
Hi Andreas,
On Tue, Aug 20, 2019 at 04:17:50PM +0200, Andreas Tille wrote:
> I observed that lintian-brush is adding a file debian/upstream/metadata
> if it finds the fields Upstream-Name and Upstream-Contact in
> debian/copyright.
> What is the sense to duplicate data that we can find in a well
Thanks for all the comments on the draft service architecture I posted
in late July. [1] I have made a v2, incorporating the various helpful
suggestions, and the information from the thread.
Some respondents raised archive integrity concerns. It seemed best to
address those more formally, and in
Hi Jelmer,
On Tue, Aug 20, 2019 at 04:46:23PM +, Jelmer Vernooij wrote:
>
> On Tue, Aug 20, 2019 at 04:17:50PM +0200, Andreas Tille wrote:
> > I observed that lintian-brush is adding a file debian/upstream/metadata
> > if it finds the fields Upstream-Name and Upstream-Contact in
> > debian/cop
13 matches
Mail list logo
