bug to branch (i don't know if
they do this)
But there seems to have at least Bridges with GitHub and GitLab
Regards
Christian
Le 24/05/2025 à 09:51, Pirate Praveen a écrit :
If we're at that point of "considering" having a second system to the
BTS (or to augment) what
On 2025-05-19 14:18, Christian Kastner wrote:
> I'm guessing that this isn't a dh_installalternatives limitation but a
> limitation of the underlying system bubbling up.
Huh, my guess was wrong. `update-alternatives --install` has no problem
with the directory, so this appears to
st manage this as a symlink in
/etc/.
Best,
Christian
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: sphinx-data-viewer
Version : 0.1.5
Upstream Contact: https://github.com/useblocks/sphinx-data-
viewer/graphs/contributors
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: sphinx-needs
Version : 5.1.0
Upstream Contact: https://github.com/useblocks/sphinx-
needs/graphs/contributors
* URL : https://github.com/useblocks
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: doxysphinx
Version : 3.3.12
Upstream Contact: Robert Bosch GmbH
* URL : https://github.com/boschglobal/doxysphinx
* License : MIT
Programming
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: mpire
Version : 2.10.2
Upstream Contact: Sybren Jansen / https://github.com/sybrenjansen
* URL : https://github.com/sybrenjansen/mpire
* License
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: sphinx-external-toc
Version : 1.0.1
Upstream Contact: https://github.com/orgs/executablebooks/people
* URL : https://github.com/executablebooks/sphinx
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: gitlab-buildpkg-tools
Version : no versionning
Upstream Contact: Christian Bayle
* URL : https://gitlab.com/Orange-OpenSource/gitlab-buildpkg-tools
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: rocm-docs-core
Version : v1.17.1
Upstream Contact: Advanced Micro Devices, Inc.
* URL : https://github.com/ROCm/rocm-docs-core
* License
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: jfree-demos
Version : 2.0
Upstream Contact: David Gilbert
* URL : https://github.com/jfree/jfree-demos
* License : BSD-3-Clause
Programming
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: liborson-charts-java
Version : 2.1.0
Upstream Contact: David Gilbert
* URL : https://github.com/jfree/orson-charts
* License : GPL-3
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: libjfreesvg-java
Version : 5.0.6
Upstream Contact: David Gilbert
* URL : https://github.com/jfree/jfreesvg
* License : GPL-3
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Christian Bayle
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: libjfreepdf-java
Version : 2.0.1
Upstream Contact: David Gilbert
* URL : https://github.com/jfree/jfreepdf
* License : GPL-3
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: libggml
* Version : 0.0+git
* Upstream Contact: The ggml authors
* URL : https://github.com/ggml-org/ggml
* License
On 2025-02-15 23:13, Simon McVittie wrote:
> On Sat, 15 Feb 2025 at 21:08:03 +0100, Christian Kastner wrote:
>> I read somewhere that Fedora can do full rollbacks because the make use
>> of "ostree". See [1] for example. We have ostree in our Archive [2].
>>
>&
r example. We have ostree in our Archive [2].
I'm not familiar with it yet, but had this bookmarked as something to
look into at some point.
Best,
Christian
[1]:
https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/
[2]: https://packages.debian.org/sid/ostree
and moving anything "merely" supplemental to a
separate section or document.
This, of course, only once discussion has produced the clarity that you
seek. I assume that at that point, others (including myself) might be
able to help contribute to improving the draft.
Best,
Christian
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org,
pkg-systemd-maintain...@lists.alioth.debian.org
Owner: Christian Göttsche
Severity: wishlist
* Package name: systemd-netlogd
Version : 1.4.2
Upstream Contact: Susant Sahani
* URL : https://github.com/systemd
you add a note on how to best run things in experimental?
For src:rocminfo, we have pipelines that fail [1,2,3] because rocminfo
depends on bin:libhsa-runtime64-1 also from experimental.
Best,
Christian
[1]: https://salsa.debian.org/rocm-team/rocminfo/-/jobs/6342778
[2]: https://salsa.debian.
hy install it?
On those systems, if people want to explicitly configure and make use of
netplan, why wouldn't they just `apt-get install netplan.io`?
Best,
Christian
oper gidmaps. I documented my findings here [1].
Though this latter issue shouldn't be a problem on buildds, where
devices aren't passed in.
Best,
Christian
[1]:
https://salsa.debian.org/rocm-team/community/team-project/-/blob/master/doc/rocm-autopkgtests-in-containers.md?ref_type=heads
Hi Hakan!
Sure.
I hope attaching the files to this mail works.
On Tue, 4 Jun 2024 10:20:34 +0300 =?UTF-8?Q?Hakan_Bay=C4=B1nd=C4=B1r?=
wrote:
> Dear Christian,
>
> Can you please share the outputs "lspci -vvv" and "dmidecode" commands
> (please run them as th
On Mon, 3 Jun 2024 12:42:17 +0200 Andrius Merkys wrote:
> Hi Christian,
>
> On 2024-06-03 11:38, Christian Böck wrote:
> > when using headphones with my laptop (Thinkpad W550s) I get a repeating
> > cracking (~1sec intervalls) when nothing is playing.
>
> I have a sim
Package: general
Severity: normal
X-Debbugs-Cc: deb...@funtech.org
Dear Maintainer,
when using headphones with my laptop (Thinkpad W550s) I get a repeating
cracking (~1sec intervalls) when nothing is playing.
*** Reporter, please consider answering these questions, where appropriate ***
* Wh
On Tue, 2 Apr 2024 at 02:30, Colin Watson wrote:
>
> [I've CCed openssh-unix-dev for awareness, but set Mail-Followup-To to
> just debian-devel and debian-ssh to avoid potentially spamming them with
> a long discussion. If you choose to override this then that's your
> call, but please be mindful
inalizing our upgrade to ROCm 5.7+ (also on Ubuntu), and a proper
write-up will follow on Debian Planet.
Best,
Christian
PS: Our intention is of course to feed back all our changes to debci,
Policy and so on, but some of these are entirely novel and require
experimentation first, followed by discussion.
n example, setting up/tearing down complex
environments emulating multiple hosts.
A more obvious example is developing for any environment that is not
unstable. With containers, basically all you have to do is swap the name
of the base image.
Best,
Christian
(Santiago, sorry for sending it twice)
ink containers are one good way to have
almost the best of both worlds. One can do anything one could do on
host, all while being isolated from that host, and with very little
overhead but also a ton of useful extra features.
Best,
Christian
containers, and/or connected to containers running services...)
> (This is an analysis specific to me, not general advice, and relies
> heavily on the fact that I'm very good at working around weird problems
> that transiently arise in unstable.)
Best,
Christian
nce (I want my workstation to be based on
stable) and precisely because of the afforded isolation.
Best,
Christian
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: llama.cpp
Version : b2116
Upstream Author : Georgi Gerganov
* URL : https://github.com/ggerganov/llama.cpp
* License
gument. DEP-3 hails from a time where we
had (IIRC) 6 VCS supported on alioth, with svn being the dominant one.
Today, practically everyone uses git, so the reasonable thing to do
would be to optimize for that case.
Best,
Christian
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: composable-kernel
Version : 0+git20230816
Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftwarePlatform
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: half
Version : 2.2.0
Upstream Author : Christian Rau
* URL : https://sourceforge.net/projects/half/
* License
; and
> it should work better than it does right now.
I second this, snapshot.d.o pas proven to be an invaluable tool for
reproducing issues.
Is there any way we can help resolve the open issues?
Best,
Christian
gt; XdSzZxiBr9nx+j+I4owJpG8lBqt72lEytKNvdy14Wos/Fl/jspIE3gjcH+Y1xM8o
>> DcrCRDZG+r4qGfUf2XWfPU6niiQepA+iET8osBHX+FblgSl00nGQ0kp9GTEnBXlV
>> DgbczjRUtqVWnW0VFeQpFatfNeqQI6K7u1cP5cFgST8IIWFLVGUAxe8y1HFzYwu2
>> rm0dp96h1fU7IQ1KZlajHhfaGf/4Nqr8hgEKJiI8/z5GO1UfujO6yGwrR7n3unON
>> UouXv43T5h1P1ZU8QQJN2YG/izNHNykRy/7axC6g+laUv3gMMis=
>> =HLqN
>> -END PGP SIGNATURE-
>>
>> --
Christian Nzhie.
greatly reduced set of dependencies but with grown size).
>
> This is - hopefully - the long-term goal, because upstream is
> slowly thinking about building qemu-system as a single binary
> which provides emulation of everything available, - obviously
> we won't try to split such binary into multiple packages :)
> But this goal seems to be too far in the future to be plannable.
>
> Without such merge into single binary, the package will be large
> (see full list of emulator binaries above), but hdd space is
> much cheaper nowadays..
>
> What do you think?
>
> /mjt
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-recipe-scrapers
Version : 14.31.0
Upstream Contact: Hristo Harsev
* URL : https://github.com/hhursev/recipe-scrapers/
* License : MIT
Package: wnpp
Severity: wishlist
Owner: "Christian T. Steigies"
* Package name: gle-graphics-manual
Version : 0~20221108
Upstream Author : Vincent LaBella
* URL : https://github.com/vlabella/gle-manual.git
* License : BSD-2-clause
Programming L
Package: wnpp
Severity: wishlist
Owner: "Christian T. Steigies"
* Package name: gle-graphics-library
Version : 0~20221105
Upstream Author : Vincent LaBella
* URL : https://github.com/vlabella/gle-library.git
* License : BSD-2-clause
Programming
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python3-scrape-schema-recipe
Version : 0.2.0
Upstream Contact: Micah Cochra
* URL : https://github.com/micahcochran/scrape-schema-recipe
* License
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-extruct
Version : 0.14.0
Upstream Author : Scrapinghub
* URL : https://github.com/scrapinghub/extruct
* License : BSD-3
Programming
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-jstyleson
Version : 0.0.2
Upstream Author : linjackson
* URL : https://pypi.org/project/jstyleson/
* License : MIT
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-html-text
Version : 0.5.2
Upstream Author : Scrapinghub Inc
* URL : https://github.com/TeamHG-Memex/html-text
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-mf2py
Version : 1.1.2
Upstream Author : Tom Morris
* URL : https://github.com/microformats/mf2py
* License : MIT
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: displaycal
Version : 3.9.6
Upstream Author : Erkan Ozgur Yilmaz
* URL : https://github.com/eoyilmaz/displaycal-py3/
* License : GPL-3
online.
>>
>> Thanks,
>>
>> --
>> Sergio
>> GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
>> Please send encrypted e-mail if possible
>> https://sergiodj.net/
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
On 2022-04-19 12:41, Jonas Smedegaard wrote:
> Quoting Christian Kastner (2022-04-19 11:33:30)
>> Here's a somewhat radical idea: I propose that we make option (1) and
>> (2) conditional on all Debian infra switching to hardware entirely
>> free of binary firmware/micr
c exception
> only to allow inclusion of those packages on our official media. We would
> then generate only one set of official media, including those non-free
> firmware packages.
I'd vote for option 5, and alternatively option 3.
Best,
Christian
On 2022-03-13 01:07, Simon McVittie wrote:
> - reserving an environment variable like SKIP_CRON_JOB_UNDER_SYSTEMD=1
> to act as a request to skip parsing this cron job on systemd systems
> (it would also be set like any other environment variable when the cron
> job is executed on a non-syste
On 2022-03-14 08:48, Marc Haber wrote:
> On Sun, 13 Mar 2022 18:02:55 +0100, Christian Kastner
>> I don't think that's a very constructive line of argument. As a former
>> maintainer, it was evident that user crontabs (crontab -e) are still
>> very popular,
d to make cronie the new
default cron daemon.
Best,
Christian
ainer (#984736), I don't think either of
these are going to happen.
Best,
Christian
Package: wnpp
Severity: wishlist
Owner: Christian Britz
X-Debbugs-Cc: debian-devel@lists.debian.org,mike.gabr...@das-netzwerkteam.de,
cbr...@t-online.de
* Package name: cutefish-statusbar
Version : 0.8-git1
Upstream Author : supp...@cutefishos.com
* URL : https
Package: wnpp
Severity: wishlist
Owner: Christian Britz
X-Debbugs-Cc: debian-devel@lists.debian.org, cbr...@t-online.de
* Package name: cutefish
Version : 0.8
Upstream Author : supp...@cutefishos.com
* URL : https://github.com/cutefishos/ | https://en.cutefishos.com
eed to hack
the sbuild-qemu-boot script to include a '-cpu' option for
qemu-system-i386 with a model that is somewhat similar to the Geode LX.
Best,
Christian
On 2022-02-05 16:07, Andrew M.A. Cater wrote:
> Just because someone else can't be bothered to do licence review checking
> doesn't mean that Debian shouldn't.
I wasn't advocating against license review checking in general, though.
We expect and trust all contributors to do that.
The question as
On 2022-02-04 18:39, Russ Allbery wrote:
> In other words, this thread is once again drifting into a discussion of
> how to do copyright review *better*, when my original point is that we
> should seriously consider not doing the current type of incredibly tedious
> and nit-picky copyright review *
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python3-recipe-scrapers
Version : 13.8.0
Upstream Author : Hristo Harsev
* URL : https://github.com/hhursev/recipe-scrapers/
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Christian Marillat
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: gourmand
Version : 1.0.0
Upstream Author : Thomas Mills Hinkle
* URL : https://github.com/GourmandRecipeManager/gourmand
* License : GPL-2
of my builds failing to this
commit [1] that has to land into debhelper to resolve it.
[1]: https://salsa.debian.org/debian/debhelper/-/commit/d70caa69c64b
> So, which one of these paths should be used and why?
> - /lib/systemd/system/
> - /usr/lib/systemd/system/
>
> Thanks!
&g
In case anyone missed it, the most recent release is now distributed
under the Apache 2.0 license:
https://lwn.net/Articles/868536/
On 30.08.21 15:49, Jelmer Vernooij wrote:
> I think one of the main challenges here is to make sure that the
> dependencies for packages in unstable/testing are correct.
Why wouldn't they be correct, though? If it's less strict than it should
be, then that is a bug. And if it's too strict, experime
debusine in the meantime, which seems to be ideal
solution to my build problem.
However, If anyone with wanna-build experience is interested in
collaborating to get this launched sooner, please ping me.
I'll try to finalize the first draft of apt-derive as soon as possible
in the hopes that something can come of it.
Best,
Christian
t page, but the site in general has interesting stuff):
http://en.techinfodepot.shoutwiki.com/wiki/Wireless_Adapters/Chipset_table
The page seems to be somewhat up-to-date, too.
Best,
Christian
Hi Bastian,
On 18.12.20 10:16, Bastian Blank wrote:
> On Fri, Dec 18, 2020 at 09:56:23AM +0100, Christian Kastner wrote:
>> Description : Sphinx directive to add unselectable prompt
>
> I'm trying to decipher what this (short) description is trying to tell
> me. &
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: sphinx-prompt
Version : 1.3.0
Upstream Author : Stéphane Brunner
* URL : https://github.com/sbrunner/sphinx-prompt
* License : BSD-3-Clause
Programming Lang: Python
Description
On 15.12.20 01:55, Russ Allbery wrote:
> Increasingly most of the people who work on Debian don't have i386
> hardware lying around, particularly i386 hardware that requires an i386
> kernel or that exercises the full range of older boot processes. If you
> do, testing and reporting good bugs woul
The NEW queue length is down a single digit, from ~500 not all too long
ago. That's an amazing effort by ftp-master that must have consumed a
*lot* of energy.
THANK YOU!
https://ftp-master.debian.org/new.html
On 2020-10-02 09:34, Stéphane Glondu wrote:
> 2.33.1-0.1 has "Extra-Source-Only: yes", so one if its binaries is
> mentioned in "Built-Using" of some other package.
>
> Same for 2.34-0.1.
Could this perhaps be a Release-specific attribute that's not present in
every Source index?
I've stumbled a
Stéphane, thanks for the fast reply!
On 2020-10-02 09:34, Stéphane Glondu wrote:
> Le 02/10/2020 à 08:57, Christian Kastner a écrit :
>> numerous versions of some of the packages.
>>
>> Those three versions happen to be the current versions from stable,
>> testing, and
I happened to stumble over the fact that bullseye Sources files contain
numerous versions of some of the packages.
For example:
$ wget http://ftp.debian.org/debian/dists/bullseye/main/source/Sources.gz
$ zgrep -A 2 'Package: util-linux' Sources.gz | grep -v Binary
Package: util-linux
Ver
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: sktime
Version : 0.4.1
Upstream Author : sktime developers
* URL : https://github.com/alan-turing-institute/sktime
* License : BSD-3-clause
Programming Lang: Python
Description
On 2020-09-08 17:43, Helmut Grohne wrote:
> On Tue, Sep 08, 2020 at 12:33:07PM +0200, Christian Kastner wrote:
>> nocheck
>> ---
>>
>> A recipe such as
>>
>> override_dh_auto_test:
>> ifeq (,$(filter nocheck,$(DEB_BUILD_PROFILES)))
On 2020-09-08 14:34, Peter Pentchev wrote:
> Just as a data point: for some time now I've been checking both
> variables with a single check :)
>
> ifeq (,$(filter nodoc,${DEB_BUILD_OPTIONS} ${DEB_BUILD_PROFILES}))
> ...
> endif
>
> ...does the job, with some possible overkill, but, hey, it works
dh_auto_build
ifeq (,$(filter nodoc,$(DEB_BUILD_PROFILES)))
build-docs-command
endif
DEB_BUILD_OPTIONS=nodoc gets ignored.
vice versa
---
And the same applies when _OPTIONS is filtered instead of _PROFILES.
Did I get that right?
Christian
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: python-multipledispatch
Version : 0.6.0
Upstream Author : Matthew Rocklin
* URL : https://github.com/mrocklin/multipledispatch/
* License : BSD-3-clause
Programming Lang: Python
On 2020-09-06 23:27, Mattia Rizzolo wrote:
> On Sun, Sep 06, 2020 at 10:53:05PM +0200, Christian Kastner wrote:
> The thing is, according to the build profile spec, if you specify nodoc
> or nocheck in _PROFILES you *MUST* also specify it on _OPTIONS (talking
> about when you do th
It seems that "nocheck" and "nodoc" can be used with both variables.
However, which one is to be used in debian/rules recipes? Or both, as
suggested here [1]?
Looking at random packages, newer packages seem to favor just checking
DEB_BUILD_PROFILES to conditionally build documentation, but that w
On 2020-08-29 01:05, Raphael Hertzog wrote:
> But given that we recommend upstream/latest for the upstream branch, I'm now
> leaning towards using debian/latest as default as well.
I like this! There's a nice symmetry to it that makes it very intuitive,
I think.
Unless I'm grievously misremembering something, there was a discussion a
while ago about automatically generating a source package and uploading
it whenever a Debian release is (signed-)tagged in Salsa.
If I did remember correctly: may I kindly inquire what the status on
that is?
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: python-iniconfig
Version : 1.0.1
Upstream Author : Ronny Pfannschmidt
* URL : https://github.com/RonnyPfannschmidt/iniconfig
* License : MIT
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: python-xmlschema
Version : 1.2.2
Upstream Author : SISSA (Scuola Internazionale Superiore di Studi Avanzati)
* URL : https://github.com/sissaschool/xmlschema/
* License : MIT
On 2020-07-17 18:30, Pirate Praveen wrote:
> On 2020, ജൂലൈ 17 8:14:24 PM IST, Marvin Renich wrote:
>> The intended purpose is to ensure that the recipient has every
>> reasonable opportunity to modify the software in any reasonable way the
>> recipient desires. The sole purpose of the requirement
On 2020-07-16 12:53, Pirate Praveen wrote:
>> Generally speaking, I think it's a mistake to apply the question of
>> "preferred form for modification" to unit test payloads. Unit tests are
>> purely about functionality. The original source to a payload is an
>> arbitrary choice (possibly even rando
On 2020-07-15 09:45, Philipp Hahn wrote:
> if a *previous* version of a software generated a *buggy* binary
> database, that bug got fixed in a *newer* version and also some
> *recovery* mechanism was added to allow reading that broken format
> *once*, but there is no code the write the *broken* fi
On 2020-06-23 08:14, Christian Kastner wrote:
> If it's not, then it's just about utility, and then honestly I don't see
> enough of it to merit the head-ache of breaking with the conventional name.
Having thought about that part some more, I realized I need to retract it.
On 2020-06-23 02:12, Colin Watson wrote:
> On Tue, Jun 23, 2020 at 01:10:31AM +0200, Ansgar wrote:
>> On Mon, 2020-06-22 at 22:13 +0100, Colin Watson wrote:
>>> [1]
>>> https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html
>>
>> You might be interested in [2] as well. Specul
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: python-threadpoolctl
Version : 2.0.0
Upstream Author : Olivier Grisel
* URL : https://github.com/joblib/threadpoolctl
* License : BSD-3-Clause
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: pyswarms
Version : 1.1.0
Upstream Author : pyswarms developers
* URL : https://github.com/ljvmiranda921/pyswarms
* License : MIT
Programming Lang: Python
Description : research
On 27.03.20 01:57, Paul Wise wrote:
> On Thu, Mar 26, 2020 at 8:30 PM Christian Kastner wrote:
>
>> [Well, technically, you could use your own lawyer to perform the due
>> diligence and have them submit any necessary changes to the BTS, but I
>> think it's
On 26.03.20 19:57, Andrej Shadura wrote:
> An example: commercial users. They need to know *exactly* what they
> are running and under which licenses.
The only way to know that is by performing your own due diligence.
> They are often bound by regulations with heavy fines for violating
> them, an
with
upstream (again, thanks to GitHub et al.), I'm all but certain that any
legal issues with the original source would first be filed upstream,
rather than for all downstreams individually.
I think we investing far too much time in a problem that no longer
exists, and probably wasn'
On 25.03.20 15:14, Tomas Pospisek wrote:
> I can be sure that if stuff lands in Debian then I won't get screwed
> by weird, dirty, missleading, underhanded licensing rules, which
> seems to be the standard outside the Open Source world and even on
> its fringes.
The only thing you can be sure about
Russ,
On 25.03.20 03:25, Russ Allbery wrote:
> I'll repeat a point that I made earlier but put a bit of a sharper point
> on it: We should thoughtfully question whether the current approach to
> license review that we as a project ask ftpmasters to do is a correct
> investment of project resources
adjustments
out of the way right now instead of raising this question again in the future.
Christian
.6.12.
Christian
On Wed, Feb 5, 2020 at 12:57 PM Sudip Mukherjee
wrote:
>
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "libbpf"
>
> * Package name: libbpf
>Version
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: TPOT
Version : 0.11.1
Upstream Author : Epistasis Lab, Inst.for Biomedical Informatics, UPenn
* URL : https://epistasislab.github.io/
* License : GPL-3+
Programming Lang: Python
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
* Package name: python-configspace
Version : 0.4.12
Upstream Author : ConfigSpace developers
* URL : https://github.com/automl/ConfigSpace
* License : BSD-3-Clause
Programming Lang: Python
1 - 100 of 1708 matches
Mail list logo
