Package: wnpp
Severity: wishlist
Owner: Cordell Bloor
X-Debbugs-Cc: debian-devel@lists.debian.org, c...@slerp.xyz,
debian...@lists.debian.org
* Package name: hipfort
Version : 5.4.3
Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftware
debain os will support for veeam backup using network storage
regards,
nijamudeen
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 entry:
https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/
Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias
X-Debbugs-Cc: debian-devel@lists.debian.org, j...@nahmias.net,
debian-j...@lists.debian.org, supp...@connect2id.com, v...@connect2id.com
* Package name: oauth2-oidc-sdk
Version : 9.43.1
Upstream Author : Connect2id Ltd
Ups
Quoting Peter Pentchev (2023-02-22 10:49:30)
> 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 entry:
> https://danie
On Feb 22, Peter Pentchev wrote:
> 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 entry:
> https://daniel.haxx.se/
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 years
> > (and in some places even earlier), but I started doing it for
> > the couple of pieces of software that I am up
On 2/22/23 13:55, Jonas Smedegaard wrote:
> As a redistributor I find it a good practice to include most possible
> copyright and licensing information provided by upstream authors,
> exactly because we are doing a service for our users
while having copyright information centrally available per pa
On 2/22/23 14:26, Peter Pentchev wrote:
> Wait, I may have been unclear. I did not mean that I want to omit
> the upstream copyright years *when they are there*.
I know you didn't mean that, nevertheless, it's imho good idea. I'd be
in favour of dropping them from d/copyright an let people have a
It is also not required to put an author name or any other information,
either. Copyright will still apply.
But it makes it really a lot easier for anyone who wants to re-use the
work or parts of it if they know who to contact. This matters even more
for computer programs than for fiction novels o
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
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 years
> > > (and in some places even earlier), but I started doing it
> "Peter" == Peter Pentchev writes:
Peter> Hi, So I've seen this idea floating around in the past couple
Peter> of years (and in some places even earlier), but I started
Peter> doing it for the couple of pieces of software that I am
Peter> upstream for after reading Daniel Ste
Quoting Daniel Baumann (2023-02-22 14:30:11)
> On 2/22/23 13:55, Jonas Smedegaard wrote:
> > As a redistributor I find it a good practice to include most possible
> > copyright and licensing information provided by upstream authors,
> > exactly because we are doing a service for our users
>
> whil
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 Wed, 22 Feb 2023 15:40:49 +0100, Jonas Smedegaard
wrote:
>Quoting Daniel Baumann (2023-02-22 14:30:11)
>> while having copyright information centrally available per package in
>> d/copyright is definitly a usefull service, is providing the *years*
>> really a service worth providing?
>>
>> per
Le mer. 22 févr. 2023 à 15:39, Sam Hartman a écrit :
> > "Peter" == Peter Pentchev writes:
>
> Peter> Hi, So I've seen this idea floating around in the past couple
> Peter> of years (and in some places even earlier), but I started
> Peter> doing it for the couple of pieces of sof
Daniel Baumann writes:
> On 2/22/23 14:26, Peter Pentchev wrote:
>> Wait, I may have been unclear. I did not mean that I want to omit the
>> upstream copyright years *when they are there*.
> I know you didn't mean that, nevertheless, it's imho good idea.
Unfortunately, it's often against the up
On 2/21/23 15:03, Ryan Kavanagh wrote:
On Sun, Feb 19, 2023 at 09:01:56AM -0700, Scarlett Moore wrote:
Description : A tool for glamourous shell scripts
A tool for glamorous shell scripts. Leverage the power of Bubbles and
Lip Gloss in your scripts and aliases without writing any Go cod
On Wed, Feb 22, 2023 at 03:26:47PM +0200, Peter Pentchev wrote:
> 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 years
> > > (and in some places even earlier), but
On Wed, Feb 22, 2023 at 09:24:29AM -0700, Scarlett Moore wrote:
>
> On 2/21/23 15:03, Ryan Kavanagh wrote:
> > On Sun, Feb 19, 2023 at 09:01:56AM -0700, Scarlett Moore wrote:
> > >Description : A tool for glamourous shell scripts
> > >
> > > A tool for glamorous shell scripts. Leverage th
Not an ftp team member or anything, so this is just my personal opinion.
Peter Pentchev writes:
> 1. Does the Debian Project consider it okay for an upstream package to
>include one or more (or all) files with clear license grants (either
>included or referred to in the files), and with
On Wed, 2023-02-22 at 07:39 -0700, Sam Hartman wrote:
> > > > >
> As Jonas mentions, including the years allows people to know when works
> enter the public domain and the license becomes more liberal.
> I think our users are better served by knowing when the Debian packaging
> would enter the pub
I maintain a package where upstream has dropped the years. I was told
that multiple big tech companies with serious lawyers looked at this and
felt it was fine.
I fully support:
- upstreams dropping years from copyright notices
- Debian not requiring maintainers to preserve years in
deb
> "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 to the upstream
Peter> project, the debian/* files ought to b
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
> "Antonio" == Antonio Terceiro writes:
Antonio> On Wed, Feb 22, 2023 at 09:24:29AM -0700, Scarlett Moore wrote:
>>
>> On 2/21/23 15:03, Ryan Kavanagh wrote:
>> > On Sun, Feb 19, 2023 at 09:01:56AM -0700, Scarlett Moore wrote:
>> > > Description : A tool for glamourous sh
Quoting Jérémy Lal (2023-02-22 17:04:01)
> Le mer. 22 févr. 2023 à 15:39, Sam Hartman a écrit :
>
> > > "Peter" == Peter Pentchev writes:
> >
> > Peter> Hi, So I've seen this idea floating around in the past couple
> > Peter> of years (and in some places even earlier), but I started
* Sam Hartman [2023-02-22 23:33]:
[...]
> >> A tool for glamorous shell scripts. Leverage the power of
> >> Bubbles (https://github.com/charmbracelet/bubbles) and Lip
> >> Gloss (https://github.com/charmbracelet/lipgloss) in your
> >> scripts and aliases without writing any Go code
Quoting Richard Laager (2023-02-22 21:47:49)
> I maintain a package where upstream has dropped the years. I was told
> that multiple big tech companies with serious lawyers looked at this and
> felt it was fine.
Big tech companies typically don't use free software licensing for the
same reasons
On Wed, 2023-02-22 at 09:47 -0800, Russ Allbery wrote:
> People doing this should be aware that you're probably waiving certain
> damage provisions in US copyright law should you ever sue someone in the
> US for violating the license on the Debian packaging, at least so far as I
> understand US co
On Wed, 2023-02-22 at 12:16 +0300, Nijam Deen wrote:
> debain os will support for veeam backup using network storage
Since Veeam is proprietary software, please ask their support team:
https://www.veeam.com/support.html
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description
Paul Wise writes:
> On Wed, 2023-02-22 at 09:47 -0800, Russ Allbery wrote:
>> People doing this should be aware that you're probably waiving certain
>> damage provisions in US copyright law should you ever sue someone in
>> the US for violating the license on the Debian packaging, at least so
>>
Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-j...@lists.debian.org,
debian-security-to...@lists.debian.org, j...@nahmias.net, d...@shibboleth.net
Control: block 1031769 by -1
* Package name: java-opensaml
Version : 4.3.0
Hi,
the version of python3-xlrd 1.2.0-3 in unstable/testing is too old to
be used with pandas 1.5.3. (See Bug #1031701). As it is a really common
workflow to use pandas to read excel files, it'd be nice if the version
of xlrd in bookworm was compatible.
Because of the freeze I wanted to check if
35 matches
Mail list logo
