Chipping in my 2 cents here...
On the "policy"/legal question of whether it's permissible to package
the internal open source in this larger source for the Debian project,
I have no specific opinion but it sounds complicated. You might
I do. Remember the GPL's mantra: "Free as in speech".
On Tue, 30 Aug 2022 16:44:38 -0400, Thomas Ward wrote:
> On 8/30/22 16:11, Philippe SWARTVAGHER wrote:
> > - how can I know who sponsored this package? (if I knew it, I would send
> > the access request directly to him)
> This will show on the Tracker once it updates. You can then take a look at
On 8/30/22 16:11, Philippe SWARTVAGHER wrote:
Le 22/08/2022 à 04:44, Bo YU a écrit :
On Sun, Aug 21, 2022 at 12:15:30PM +0200, Philippe SWARTVAGHER wrote:
Hello,
I’m adopting the package libcdio-paranoia. I did the work in a fork:
https://salsa.debian.org/phsw/libcdio-paranoia. Now it’s
Le 22/08/2022 à 04:44, Bo YU a écrit :
On Sun, Aug 21, 2022 at 12:15:30PM +0200, Philippe SWARTVAGHER wrote:
Hello,
I’m adopting the package libcdio-paranoia. I did the work in a fork:
https://salsa.debian.org/phsw/libcdio-paranoia. Now it’s almost ready
for upload, could someone give to me
On Tue, Aug 30, 2022 at 12:00:39PM -0500, Ryan Pavlik wrote:
> The easiest way to do the tarball cleaning is with Files-Excluded in the
> copyright file, uscan will involve something (mkorigtargz?) that uses it to
> repack. That's a technical answer to the technical side of the question.
Even
Control: tags -1 moreinfo
On Tue, 30 Aug 2022 00:00:02 -0300 Gabriel M Dutra <0xdu...@gmail.com> wrote:
* Initial release (Closes: TODO)
Please file an ITP and fill this TODO. Have you read on how to hand in a
package?
When you are done, please untag moreinfo from this bug.
The easiest way to do the tarball cleaning is with Files-Excluded in the
copyright file, uscan will involve something (mkorigtargz?) that uses it to
repack. That's a technical answer to the technical side of the question.
On the "policy"/legal question of whether it's permissible to package the
Thank you for your suggestions. I'll give it a try.
Fab
Le 24 août 2022 20:52:25 GMT+02:00, Ryan Pavlik a écrit
:
>Better yet, if you use the REUSE tool to extract an SPDX file, this
>utility I wrote can coalesce it into a more human-usable DEP5-format
>debian/copyright file:
>
On Mon, Aug 29, 2022 at 08:31:44PM -0700, Steve M wrote:
> > Quite interestingly, all these 3 uploads caused the service to be killed
> > by the OOM killer
> > https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143
> >
> > So I guess that's why you are not seeing any answer
Hi Niels,
Thanks for prompt reply.
On 2022-08-30 17:40, Niels Thykier wrote:
> From the description you have provided, I would assume yes with the
> following assumptions:
>
> 1) By "Extract AmberTools" you mean repackage the orig tarball.
Yes, that is what I meant.
> 2) AmberTools consists
Andrius Merkys:
Hello,
[...]
My question: Is it OK to extract AmberTools from Amber tarball and
package for Debian main?
[1] https://ambermd.org/AmberTools.php
[2] https://ambermd.org/GetAmber.php#ambertools
Best,
Andrius
From the description you have provided, I would assume yes with the
Hello,
I am looking into packaging AmberTools [1], suite of tools for molecular
dynamics simulation. AmberTools is GPL, but it is shipped inside a
tarball of a larger piece of software called Amber [2]. To get the
tarball one has to put in their name and institution in a form [2], but
there is no
Hi Mentors:
Sorry for the vague subject, but I have several questions that don't
fit neatly into a subject line. The situation is I recently had to
prepare a new upstream version of a package in Debian for a client
minetest to 5.6.0. I haven't touched Debian packaging in 7.5 years or
so.
13 matches
Mail list logo
