Hello Otto,
On Sat 08 Feb 2020 at 10:07PM +02, Otto Kekäläinen wrote:
> I've ended up in being both the maintainer in Debian and an upstream
> developer for a couple of packages and I have been fantasizing about
> how to optimize my workflow so that I primarily fix all bugs and do QA
> directly o
On Thu, Feb 06, 2020 at 01:10:36PM +0900, Norbert Preining wrote:
> What do you mean "packages involved". The core ML related package is by
> now not completely free (snowboy) thus we have prepared a project that
> also tries to incorporate Mycroft or some other OSS hotword module
> which allows fo
Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij
* Package name: python3-xdelta3
Version : 0.0.6a1
Upstream Author : Samuel Colvin
* URL : https://github.com/samuelcolvin/xdelta3-python
* License : Apachev2
Programming Lang: Python
Description :
Hi Otto,
i'm doing this for years now (LXQt)
To sum it up:
* there are no special rules, but i suggest to keep your hats strictly
separated
* if there are some doubts upstream - just think how you would feel with
a release with your downstream hat on
* if you release something upstream and have t
Hi,
On 08.02.20 21:07, Otto Kekäläinen wrote:
> I've ended up in being both the maintainer in Debian and an upstream
> developer for a couple of packages and I have been fantasizing about
> how to optimize my workflow so that I primarily fix all bugs and do QA
> directly on the upstream developme
On 08.02.20 22:39, Steve McIntyre wrote:
> +1. A reasonable patch to allow this kind of thing would of course be
> considered. It could even be pre-seeded to allow for easy control of
> it.
> I *think* we said something like that ages ago, but no sign of
> patches.
The installer patches are triv
Otto Kekäläinen writes:
> Hi!
>
> Thanks for the example. I see you even maintain the changelog in upstream:
> https://git.notmuchmail.org/git?p=notmuch;a=blob;f=debian/changelog;h=4f7457cd7f588e6d3a821bf1530cc1f8742c8d6f;hb=refs/heads/master
Yes.
>
> But apparently "upstream" releases are deco
Hi!
Thanks for the example. I see you even maintain the changelog in upstream:
https://git.notmuchmail.org/git?p=notmuch;a=blob;f=debian/changelog;h=4f7457cd7f588e6d3a821bf1530cc1f8742c8d6f;hb=refs/heads/master
But apparently "upstream" releases are decoupled from also bumping the
Debian version?
Arg, typo in the list address. Sorry. :-(
On Sat, Feb 08, 2020 at 09:28:50PM +, Steve McIntyre wrote:
>Hey Michael!
>
>Sorry for leaving you hanging here. Really busy week...
>
>Michael Biebl wrote:
>>Am 01.02.20 um 14:36 schrieb Steve McIntyre:
>>> Michael Biebl wrote:
with today's
In article <20200208121622.lu4vla6sasagven2@function> you write:
>Svante Signell, le sam. 08 févr. 2020 13:03:20 +0100, a ecrit:
>> On Thu, 2020-02-06 at 21:12 +, Sam Hartman wrote:
>> > Unfortunately, I think that Debian has decided that's not directly our
>> > focus.
>>
>> Just to make sure
Otto Kekäläinen writes:
> Hello!
>
> I've ended up in being both the maintainer in Debian and an upstream
> developer for a couple of packages and I have been fantasizing about
> how to optimize my workflow so that I primarily fix all bugs and do QA
> directly on the upstream development version
Hello!
I've ended up in being both the maintainer in Debian and an upstream
developer for a couple of packages and I have been fantasizing about
how to optimize my workflow so that I primarily fix all bugs and do QA
directly on the upstream development version (=upstream git master)
and then have
Hello,
Alf Gaida, le sam. 08 févr. 2020 17:18:09 +0100, a ecrit:
> Am 08.02.20 um 16:15 schrieb Svante Signell:
> > Anything else?
> >
> Yes, you forget something - as long the discussion culture in Debian
> stays this way i'm not motivated to start my NM process again.
Please really do not take
Am 08.02.20 um 16:15 schrieb Svante Signell:
>
> Anything else?
>
Yes, you forget something - as long the discussion culture in Debian
stays this way i'm not motivated to start my NM process again. Waste of
time to join a bunch of unripe kids. Sorry, but i find no other words
with my limited en
This thread has served its purpose.
Continuing this thread is neither consistent with our Code of Conduct
nor with the idea of facilitating a productive on-topic discussion
within the scope of the debian-devel mailing list.
Among other reasons, the discussion is starting to repeat itself and to
Le samedi, 8 février 2020, 16.15:13 h CET Svante Signell a écrit :
> On Sat, 2020-02-08 at 14:51 +0100, Samuel Thibault wrote:
> > Sam Hartman, le sam. 08 févr. 2020 08:27:24 -0500, a ecrit:
> > > It sounds like you were suggesting that people should leave as a way of
> > > pressuring or punishing
Svante Signell, le sam. 08 févr. 2020 16:15:13 +0100, a ecrit:
> On Sat, 2020-02-08 at 14:51 +0100, Samuel Thibault wrote:
> > Sam Hartman, le sam. 08 févr. 2020 08:27:24 -0500, a ecrit:
> > > Svante> Perhaps all [...] ought to leave the project, including
> > > Svante> those having package not bei
On Sat, 2020-02-08 at 14:51 +0100, Samuel Thibault wrote:
> Hello Sam,
>
> Sam Hartman, le sam. 08 févr. 2020 08:27:24 -0500, a ecrit:
> > Svante> Perhaps all [...] ought to leave the project, including
> > Svante> those having package not being dependent on systemd.
> >
> > I am frustrated readi
Package: wnpp
Severity: wishlist
Owner: Samuel Thibault
* Package name: pocketsphinx-python
Version : 0.1.15
Upstream Author : Dmitry Prazdnichnov
* URL : https://github.com/bambocher/pocketsphinx-python/
* License : BSD
Programming Lang: Python
Descriptio
Hello Sam,
Sam Hartman, le sam. 08 févr. 2020 08:27:24 -0500, a ecrit:
> Svante> Perhaps all [...] ought to leave the project, including
> Svante> those having package not being dependent on systemd.
>
> I am frustrated reading this.
> It sounds like you were suggesting that people should leave a
> "Svante" == Svante Signell writes:
>> Yes, this may mean that the support for a particular alternate
>> init system may be better in a downstream that focuses on that
>> system than in Debian itself.
Svante> Perhaps all Debian Developers and Maintainers opposing
Svante
> "Paul" == Paul Wise writes:
>> B) Using our own packages ensures that there is no diversion
>> between what Debian ships and what Debian uses, so it can be
>> bootstrapped on an island (which is the link to the DFSG) as a
>> whole, not only the software it distributes.
Svante Signell, le sam. 08 févr. 2020 13:03:20 +0100, a ecrit:
> On Thu, 2020-02-06 at 21:12 +, Sam Hartman wrote:
> > Unfortunately, I think that Debian has decided that's not directly our
> > focus.
>
> Just to make sure: If I submit patches for the Debian installer for support of
> more tha
On Thu, 2020-02-06 at 21:12 +, Sam Hartman wrote:
> > > > > > "Svante" == Svante Signell writes:
>
> Svante> When is
> Svante> Debian ever to offer a non-systemd alternative for
> Svante> installation?
>
> I hear your frustration that you'd like to see Debian committed to
> suppo
Package: wnpp
Severity: wishlist
Owner: Alexandre Mestiashvili
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: bustools
Version : 0.40.0
Upstream Author : Páll Melsted
* URL : https://bustools.github.io/
* License : BSD
Programming Lang: C++
D
On Sat, Feb 08, 2020 at 12:34:01PM +0200, Peter Pentchev wrote:
> > what do we gain by this?
> We do not let services start exposing information that was just lying
> there because something else - or someone else - created a /srv/ftp
> directory for some other use?
thanks, makes sense. (though I
On Sat, Feb 08, 2020 at 10:06:54AM +, Holger Levsen wrote:
> On Sat, Feb 08, 2020 at 03:05:20AM +, Paul Wise wrote:
> > That way, the layout of /srv is exclusively under the control of the
> > sysadmin and Debian packages never touch it unless directed to do so.
>
> what do we gain by thi
On Sat, Feb 08, 2020 at 03:05:20AM +, Paul Wise wrote:
> That way, the layout of /srv is exclusively under the control of the
> sysadmin and Debian packages never touch it unless directed to do so.
what do we gain by this?
--
cheers,
Holger
28 matches
Mail list logo
