Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
X-Debbugs-Cc: debian-devel@lists.debian.org, g...@nonempty.org
* Package name: python-multiurl
Version : 0.3.1
Upstream Contact: European Centre for Medium-Range Weather Forecasts
* URL : https://github.com/ecmwf
Hi!
Thomas Goirand writes:
> Dear friends,
>
> Together with a bunch of people during debcamp, we decided to package
> homeassistant. This is a huge task, with hundreds of
> dependencies. Since there's too many, we've been told to no Cc:
> debian-devel@l.d.o when filing the ITPs, and instead wri
On 31 March 2024 12:39:55 CEST, Johannes Schauer Marin Rodrigues
wrote:
>
>Another example is when I wanted to run a GUI program inside an unshared chroot
>environment. Wayland does not seem to be happy about that and I didn't find a
>way to test my GUI application successfully. But maybe my co
Hello.
Paul Wise writes:
> On Thu, 2024-01-25 at 00:24 +, Wookey wrote:
>
>> People keep telling us (@ARM) how marvellous Rust is, and we keep
>> telling them that it's useless in the real world until it sorts out
>> the stable ABI/dynamic linking problem.
>
> IIRC that has been worked on fo
On October 16, 2023 2:41:08 AM GMT+02:00, "Trent W. Buck"
wrote:
>FWIW, there are lighter alternatives than pandoc:
>
>pandoc:After this operation, 174 MB of
> additional disk space will be used.
>sphinx-doc (sphinx-build -b man): After this operation, 140 MB
Hi Johannes,
Johannes Schauer Marin Rodrigues writes:
> Quoting Gard Spreemann (2023-09-20 09:26:58)
>> Paul Wise writes:
>> > […] since the Rust packages are basically only used as build-deps and
>> > therefore have no human users.
>> I just wanted to raise aw
Hi,
Paul Wise writes:
> […] since the Rust packages are basically only used as build-deps and
> therefore have no human users.
I just wanted to raise awareness that some of us humans do use
librust-*-dev packages directly, having put cargo in permanent offline
mode and having swapped out its ca
"M. Zhou" writes:
> On Sat, 2022-08-27 at 09:50 +0200, Gard Spreemann wrote:
>>
>> I humbly disagree. Even from my own point of view, I may well be very
>> motivated to package something I use seriously all the time,
>> seriously. But then I see its depen
Gard Spreemann writes:
> Oh no, then we instead insist that related work stops
Sorry, this was imprecise of me. We of course don't insist that related
work stops. But I really fear that that is the consequence in a great
many cases.
-- Gard
Paul Wise writes:
> There are a lot of examples of busywork in Debian, such as documenting
> licenses, packaging dependencies, removing non-free files that are only
> in source packages, runtime selection of correct CPU instructions,
> fixing build failures, porting reverse dependencies to newer
"M. Zhou" writes:
> To be honest, in terms of volunteered reviewing work, waiting
> for several months is not something new. In academia, it may
> take several months to years to get a journal paper response.
Sure, but
(1) that situation isn't popular in academia either,
(2) at least you can
Jonas Smedegaard writes:
> Quoting Gard Spreemann (2022-08-26 08:49:21)
>> On August 25, 2022 10:52:56 AM GMT+02:00, "Sebastian Dröge"
>> wrote:
>> >PS: To preempt any questions as for why, the background for my decision
>> >to stop maintaining a
On August 25, 2022 10:52:56 AM GMT+02:00, "Sebastian Dröge"
wrote:
>PS: To preempt any questions as for why, the background for my decision
>to stop maintaining any packages is this thread, but it's really just
>the straw that broke the camel's back
>
> https://alioth-lists.debian.net/pipermail
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: Gard Spreemann
Severity: wishlist
* Package name: zigpy
Version : 0.50.1
Upstream Author : Russell Cloran and contributors
* URL : https://github.com/zigpy/zigpy
* License : GPL-3+
Programming
Georges Khaznadar writes:
> Package: wnpp
> Severity: wishlist
> Owner: Georges Khaznadar
> X-Debbugs-Cc: debian-devel@lists.debian.org
>
> * Package name: ai
> Version : 0.03
> Upstream Author : François Élie
> * URL : https://gitlab.adullact.net/felie/ai
> * Licen
Bastian Blank writes:
> On Sun, Apr 03, 2022 at 02:17:15PM +0300, Adrian Bunk wrote:
>> SIMDe (or similar approaches) could be used to build variant(s) of the
>> library that have compile-time emulation of SIMD instructions in the
>> lower baseline builds of vectorscan.
>
> But why? Who in th
Julien Puydt writes:
> Hi,
>
> one of my package has a failure on mips64el and upstream is ready to
> help me find the cause and debug the issue.
>
> Unfortunately, on https://db.debian.org/machines.cgi I only see five
> developer machines on this architecture -- all buildd!
>
> Is there really
Adam Borowski writes:
> Guys, once again we had a complaint about forcing people to waste their time
> on copyright matters then wait months or years for review of said matters
> -- just for the discussion degenerate into a proposal to bring even MORE
> copyright into our life!
>
>> - What is RE
Andreas Tille writes:
> Hi again,
>
> I've just created a preliminary Sprint page[2]. At the top I've added a
> table to summarise first responses of participants about the date.
> Seems we have a vague preference for the date 2022-02-18 - 2021-02-20.
>
> I'd be really happy if more interested
Adam Borowski writes:
> On Tue, Jan 25, 2022 at 09:38:01PM +0100, Vincent Bernat wrote:
>> For me, the copyright check is just a bad excuse. People upload
>> non-distributable stuff everywhere and it seems the world continue to go
>> round. What amount of non-distributable packages is stopped by
Jonas Smedegaard writes:
> Quoting Vincent Bernat (2022-01-25 21:38:01)
>> I didn't comment at first because I thought someone else would raise
>> the idea. But it seems people still like the idea of a NEW queue. Not
>> me. The NEW queue is a hindrance.
>
> For the record, I don't "like" the N
Sébastien Delafond writes:
> Hello,
>
> As part of an upcoming survey that we are preparing, we plan to ask
> Debian developers to rank, by order of importance, the most popular
> ideas of improvements for Debian.
>
> However, there's no easy way to identify what are the most popular ideas
> of
Jonas Smedegaard writes:
> Quoting Gard Spreemann (2021-12-02 13:09:17)
>>
>> Jonas Smedegaard writes:
>>
>> > Quoting Gard Spreemann (2021-12-02 12:31:30)
>> >>
>> >> Paul Wise writes:
>> >>
>> >> > I also
Jonas Smedegaard writes:
> Quoting Gard Spreemann (2021-12-02 12:31:30)
>>
>> Paul Wise writes:
>>
>> > I also wonder if it is time to split debian/watch out of Debian
>> > source packages, since upstream download locations generally change
>>
Paul Wise writes:
> I also wonder if it is time to split debian/watch out of Debian source
> packages, since upstream download locations generally change
> independently of the Debian package and so information about upstream
> download locations probably should be maintained independently.
I v
On November 22, 2021 5:24:57 PM GMT+01:00, Marius Gripsgard
wrote:
>Hi,
>
>
>I am looking for someone to sign my keys, but due to covid this has not
>been easy to do, so im looking for someone in my local area that would
>be up to do a key signing. I have already looked at the offering page,
>
Andrey Rahmatullin writes:
> On Thu, Nov 18, 2021 at 04:08:23PM +0100, Stephan Lachnit wrote:
>> > > I don't know if that has been proposed before, but how about waiving
>> > > the NEW queue requirement for experimental packages as a start?
>> > > [...] Since packages in experimental will never
Simon Richter writes:
> Hi,
>
> On 11/18/21 4:08 PM, Stephan Lachnit wrote:
>
>> I guess this raises the (maybe already answered) question if the
>> additional license QA from NEW is for the end-product (i.e. Debian
>> stable) or for the servers that run the Debian infrastructure, which
>> of co
Hi all.
Johannes Schauer Marin Rodrigues writes:
> slightly related question: if I upload a new version to NEW, will the Age of
> the package be reset? I'm asking because my package has been in NEW for four
> months already and I'd like to avoid loosing that place by an upload of a new
> upstrea
Mattia Rizzolo writes:
> On Mon, Aug 23, 2021 at 12:59:39PM +0200, Gard Spreemann wrote:
>> Have the uscan watch file checks that feed qa.debian.org stopped? Is it
>> on purpose? Perhaps a consequence of the recent release?
>
> That's one part that's included in
Hi list,
Have the uscan watch file checks that feed qa.debian.org stopped? Is it
on purpose? Perhaps a consequence of the recent release?
Best,
Gard
signature.asc
Description: PGP signature
Dmitry Smirnov writes:
> Nobody is perfect. Everybody said a foolish thing at least once in a
> lifetime. If we cancel those who love what they do, those who are good
> with what they do, those who are passionate and caring for what they do
> for something they have said somewhere else then even
Phil Morrell writes:
> Sounds like you're asking for a new github redirector on qa.debian.org
> as there is for sf.net, which could use the official api for stability.
This got me thinking: the version checking mechanism of d/watch files is
useless if the outside world changes, i.e. if upstream
Timothy M Butterworth writes:
> The FSF with out RMS would be like the Linux Foundations with out
> Linus.
To me, and I dare guess, to most people, the actions of RMS are not
being weighted against the important contributions he has made. Many of
us believe that he has crossed certain lines tha
Adrian Bunk writes:
> On Sun, Feb 07, 2021 at 05:19:17PM +0100, Gard Spreemann wrote:
>> and instead try to track positive attributes like fitness for
>> release, though?
>
> Can you provide a less lofty description of what you want to implement?
I didn't suggest th
Andrey Rahmatullin writes:
> On Sun, Feb 07, 2021 at 02:20:28PM +0100, Samuel Thibault wrote:
>> > the packages being untouched for a long time in some cases meaning there is
>> > no guarantee for quality.
>>
>> Sure, but if there is no serious issue left with the package, we can as
>> well shi
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
X-Debbugs-Cc: debian-devel@lists.debian.org, g...@nonempty.org
* Package name: CLBlast
Version : 1.5.1
Upstream Author : Cedric Nugteren and others
* URL : https://cnugteren.github.io/clblast/clblast.html
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
X-Debbugs-Cc: debian-devel@lists.debian.org, g...@nonempty.org
* Package name: eagerpy
Version : 0.29.0
Upstream Author : Jonas Rauber
* URL : https://eagerpy.jonasrauber.de/
* License : MIT
Programming
pe pi writes:
> 1) Open Terminal
>
> 2) Type: sudo nano /etc/default/grub
>
> 3) Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT, and add
> video=hyperv_fb:[the resolution you want].
>So my line ends up looking like this:
> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=hyperv_fb:136
Hi,
I must admit I don't know much about the CI/autopkgtest infrastructure,
but I've noticed over summer that the frequency at which my packages are
being tested has decreased a lot, especially when it comes to ordinary
tests in unstable (as opposed to tests that pick a few packages from
experimen
Zlatan Todorić writes:
> I saw there was mention of GNUK and Yubikeys but I didn't see anyone
> mentioned Nitrokey.
>
> https://www.nitrokey.com/
>
> They are a small German-based vendor, producing some nice products
> (among other "keys") and they (AFAIK) are doing it all in FLOSS spirit
> (aka
Michael Biebl writes:
> there has been a lot of talk recently about how master is a loaded term
> that should be avoided.
> If I read the news correctly, github and others are going to change the
> default master branch to main.
> I don't really have any strong opinion on that matter myself.
>
Hello list,
It seems to me that the "Lintian E+W" column on the QA packages overview
page currently incorrectly shows a checkmark even when there are Lintian
warnings for a package. Is this a known bug?
Best,
Gard
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: hera
Version : 0~git20200309
Upstream Author : Arnur Nigmetov
* URL : https://github.com/grey-narn/hera
* License : BSD-3-clause
Programming Lang: C++
Description : Library for
Adam Borowski writes:
> If, for whatever reason, you feel urgency, the ftpmasters are very good at
> prioritizing your needs. There's just no information attached to packages
> normally -- you need to let them know. One way is popping up in #debian-ftp
> and whining.
>
> I've never had them r
Wookey writes:
> On 2020-05-20 13:42 +0200, Gard Spreemann wrote:
>>
>> Wookey writes:
>
>> Is there any community consensus on putting the bundling in place
>> temporarily while the separate package is held up in NEW? Being the
>> maintainer of both, I w
will
>use the libblas.so.3 in the global scope:
> /usr/lib//libblas.so.3 (a symlink)
>
> --- end solution ---
>
> That's it, much simpler and much more efficient than my first version.
>
> Comments please?
Would it make sense for DH to acquire functionality to automat
Wookey writes:
> On 2020-05-20 10:16 +0200, Gard Spreemann wrote:
>> Hi list,
>>
>> Upstream for a package I maintain has as of its latest release started
>> bundling and requiring a third-party header-only library. I am
>> considering packaging that third-par
Hi list,
Upstream for a package I maintain has as of its latest release started
bundling and requiring a third-party header-only library. I am
considering packaging that third-party library (it's useful to me, at
the very least) but I think it's a borderline case of whether it
warrants being a pac
Mo Zhou writes:
> Please comment:
> 1. Do we have a better solution where we can retain high performance and
> avoid threading trouble at the same time?
> 2. If we don't have a better solution, is my proposal acceptable?
> 3. In which way can my proposal be improved?
Hi Mo,
Your proposal
Bernd Zeimetz writes:
> On 4/25/20 10:05 PM, IOhannes m zmölnig (Debian/GNU) wrote:
>> On 4/25/20 8:34 PM, Bernd Zeimetz wrote:
>>> Hi,
>>>
>>> https://docs.gitlab.com/ee/security/two_factor_authentication.html
>>>
>>> Enforce that (if Salsa is doing that in the meantime, ignore me).
>>
>>
Mo Zhou writes:
> On Wed, Apr 01, 2020 at 10:37:07AM +0200, Gard Spreemann wrote:
>> Or, another example that I can imagine plausibly arising in practice:
>> suppose a terrabyte of raw data was collected from a scientific
>> experiment or simulation in order to produce (
Jeremy Bicha writes:
> Let's say I take a photo of myself to include in an app so that users
> can appreciate what I look like. What is the "preferred form of
> modification"? If it's 15 years later and I no longer look the same,
> would I edit the photo with free software to make it look like
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: python-cdsapi
Version : 0.2.5
Upstream Author : ECMWF
* URL : https://pypi.org/project/cdsapi
* License : Apache-2.0
Programming Lang: Python
Description : Python interface for the
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: python-pot
Version : 0.6.0
Upstream Author : Rémi Flamary
* URL : https://github.com/rflamary/POT/
* License : MIT
Programming Lang: Python, C++
Description : Python optimal
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: ripser
Version : 1.1
Upstream Author : Ulrich Bauer
* URL : http://ripser.org
* License : MIT
Programming Lang: C++
Description : Fast computation of persistent homology of flag
Hi,
Paolo Greppi writes:
> The 10 remaining packages all fail with latex-related errors.
> Unfortunately I know nothing about latex so I cant' help with those.
> But I filed bugs or updated the existing open bug:
> - ccfits, "Overfull \hbox" latex error, see: https://bugs.debian.org/943423
> - f
Colin Watson writes:
> On Tue, Sep 24, 2019 at 10:41:07AM +0200, Gard Spreemann wrote:
>> A package I maintain (src:gudhi) was mostly under GPL-3+ up to and
>> including the current version in the archives. Since then, upstream has
>> switched to an MIT license, but with
Filippo Rusconi writes:
> Greetings,
>
> On Tue, Sep 24, 2019 at 10:41:07AM +0200, Gard Spreemann wrote:
>>Hello,
>>
>>A package I maintain (src:gudhi) was mostly under GPL-3+ up to and
>>including the current version in the archives. Since then, upstream has
Hello,
A package I maintain (src:gudhi) was mostly under GPL-3+ up to and
including the current version in the archives. Since then, upstream has
switched to an MIT license, but with the caveat that many parts of the
code has GPL dependencies and that "for practical purposes this code is
GPL-3 for
Scott Kitterman writes:
> On September 5, 2019 7:36:01 AM UTC, Gard Spreemann wrote:
>>Can someone help clarify why the Qt 4 removal causes all of
>>src:libqglviewer to be marked for removal? Surely its Qt 5 binaries
>>could stay?
>
> All binaries from a source p
Hi,
I maintain src:gudhi, which build-depends on libqglviewer-dev-qt5 and
depends on libqglviewer2-qt5. Because of the Qt 4 removal,
src:libqglviewer, which provides the two aforementioned binaries, seems
to be marked for autoremoval (#875036), and thus src:gudhi too has been
marked for autoremova
Scott Kitterman writes:
> Several time people have said they feel it's important to be able to verify
> from contents of the archive.
Hi all,
Please forgive my ignorance if this is stupid, or if it's already been
discussed and I overlooked it. I'm not posing this as a suggestion, but
rather a
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: python-pyspike
Version : 0.6.0
Upstream Author : Mario Mulansky
* URL : https://mariomulansky.github.io/PySpike/
* License : BSD-2-clause
Programming Lang: Python, C
Description
Bagas Sanjaya writes:
> Regarding freedom, yes it can be affected by CRS because CRS can limit
> freedom to use programs for some users
> (particularly non-adults). But CRS limit such freedom in order to protect
> psychology users for long term from negative
> impacts of programs they used.
Hi,
Incidentally, and somewhat off-topic: Do you know if a similar effort is
being made for the PETSc and SLEPc packages (src petsc and slepc)?
Best,
Gard
My initial question resulted in a lot of useful advice and opinions, and
spurred quite an interesting discussion. Thanks to everyone who
contributed, and apologies for not contributing myself.
Hi,
For one of my packages, I maintain two public git branches: one is
upstream/latest, where I've been importing upstream's released tarballs,
and the other is debian/sid that contains the packaging.
Recently, upstream has finally started using git. What is the
recommended way for me to maintain
Ian Jackson writes:
> Julien Cristau writes ("Re: Reusing source package name of long-removed,
> unrelated package"):
>> I would say reusing binary package names is usually worse than reusing
>> source package names, in that it's a lot more likely to affect users.
>> Sometimes it happens anywa
(Apologies if you receive this message twice; I dropped a ball juggling
e-mail identities).
Ian Jackson writes:
> Julien Cristau writes ("Re: Reusing source package name of long-removed,
> unrelated package"):
>> I would say reusing binary package names is usually worse than reusing
>> source p
Ian Jackson writes:
> Gard Spreemann writes ("Reusing source package name of long-removed,
> unrelated package"):
>> I understand that 3.3.2 of the policy mandates that I at least bump the
>> epoch, but I wanted to ask the list to make sure: is reusing the
Hello,
I filed an ITP (#920912) regarding a package I'm preparing. The upstream
name for this package is "phat", which doesn't appear in the archives
from jessie to the present day. After filing the ITP and uploading my
package to mentors, I realized that there was an unrelated "phat" with a
diffe
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: phat
Version : 1.5
Upstream Author : Ulrich Bauer, Michael Kerber, Jan Reininghaus
* URL : https://bitbucket.org/phat-code/phat
* License : LGPL-3+
Programming Lang: C++
Description
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: tikzit
Version : 1.0
Upstream Author : Aleks Kissinger
* URL : http://tikzit.sourceforge.net/
* License : Mostly GPL-3+, some LGPL-2+
Programming Lang: Mostly Objective C
Description
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: gudhi
Version : 1.3.1
Upstream Author : Gudhi project / INRIA
* URL : http://gudhi.gforge.inria.fr/
* License : GPL-3+
Programming Lang: C++
Description : C++ template library for
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: ripser
Version : 1.0.1
Upstream Author : Ulrich Bauer
* URL : http://ripser.org
* License : LGPL-3.0+
Programming Lang: C++
Description : Software for computing persistent homology
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann
* Package name: lbfgsb
Version : 3.0
Upstream Author : Ciyou Zhu, Richard Byrd, Jorge Nocedal, Jose Luis Morales
* URL : http://users.iems.northwestern.edu/~nocedal/lbfgsb.html
* License : BSD-3-clause
77 matches
Mail list logo
