On Sun, 28 Oct 2018, Wouter Verhelst wrote:
> On Sun, Oct 28, 2018 at 01:14:13AM +, Ben Hutchings wrote:
> > Debian can't afford to pay developers in general, and previous
> > proposals to pay specific developers were not well received.
>
> That was over a decade ago. The circumstances at the
On Tue, Nov 06, 2018 at 01:09:50AM +0100, Adam Borowski wrote:
> But only the stock kernel, which turns it non-free software.
What is non-free? Signing stuff does not change the freeness of the
software.
Bastian
--
"That unit is a woman."
"A mass of conflicting impulses."
On Tue, Nov 06, 2018 at 10:08:10AM +0100, Bastian Blank wrote:
> On Tue, Nov 06, 2018 at 01:09:50AM +0100, Adam Borowski wrote:
> > But only the stock kernel, which turns it non-free software.
> What is non-free? Signing stuff does not change the freeness of the
> software.
it does introduce http
On Tue, Nov 06, 2018 at 02:43:44AM +0100, John Paul Adrian Glaubitz wrote:
> >> Why would I need to communicate that?
> > Because coordination needs involvement from all
> If the maintainer of a package doesn't understand which reverse
> dependencies his package has, he shouldn't be the maintain
On 11/6/18 11:51 AM, Holger Levsen wrote:
> please get of your high horse.
>
> I'm not sure it is said anywhere that one has to care about ports and/or
> some pet projects.
This isn't about caring about ports, this is about being respectful to
each other.
> Also, you wrote a mail to d-d-a that r
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
> I also bootstrapped the Rust compiler and helped fixing issues on armel,
> mips, mipsel, mips64el. Those are "strange" ports for you? Ok.
no (except armel..)
but as said, you just wrote a mail to d-d-a that rust has been
On Sat, Nov 03, 2018 at 10:53:12PM +0100, John Paul Adrian Glaubitz
wrote:
With this mail, I would like to protest the uncoordinated upload of the
rustified version of libsrvg to unstable. The maintainer of the package
There's no point dancing around the person's identity if you're going to
bri
On Tue, 2018-11-06 at 10:42 +, Holger Levsen wrote:
> On Tue, Nov 06, 2018 at 10:08:10AM +0100, Bastian Blank wrote:
> > On Tue, Nov 06, 2018 at 01:09:50AM +0100, Adam Borowski wrote:
> > > But only the stock kernel, which turns it non-free software.
> > What is non-free? Signing stuff does no
On Tue, 2018-11-06 at 09:14 +0800, Paul Wise wrote:
> AFAICT the Debian Secure Boot packages are not designed for the
> scenario where only Debian keys or per-user keys are trusted by the
> firmware, if they were then shim-signed would be named
> shim-signed-microsoft and there would be a shim-sign
Le mardi 06 novembre 2018 à 11:58:57+0100, John Paul Adrian Glaubitz a écrit :
> On 11/6/18 11:51 AM, Holger Levsen wrote:
> > please get of your high horse.
> >
> > I'm not sure it is said anywhere that one has to care about ports and/or
> > some pet projects.
>
> This isn't about caring about por
> There's no point dancing around the person's identity if you're going to
> bring -devel into this. All it does it cost the rest of us a small
> amount of effort to bother looking it up. Instead I think it would be
> both more polite and more effective to name them directly, AND ensure to
> CC the
On 2018-11-06 11:08, Holger Levsen wrote:
> > I also bootstrapped the Rust compiler and helped fixing issues on armel,
> > mips, mipsel, mips64el. Those are "strange" ports for you? Ok.
>
> no (except armel..)
I'm running Debian armel on, I don't know, 1000 or 2000 devices.
(Not myself, customers
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
Well, if it wasn't for me, we'd probably be shipping the 2.40-version of
librsrv in Debian Buster and Firefox would be missing on a couple of
release architectures.. But I guess the phrase "Thank you" doesn't exist
in Debi
Simon McVittie writes ("Re: Should libpam-elogind Provide libpam-systemd ?"):
> On Mon, 05 Nov 2018 at 13:32:40 +, Ian Jackson wrote:
> > pinentry-gnome3 and pulseaudio seem wrong to me. PINs should not be
> > shared between login sessions and sound control should be per-session,
> > not per-u
Simon McVittie writes ("Re: Should libpam-elogind Provide libpam-systemd ?"):
> I don't want this to turn into "us vs. them", and I'm trying not to get
> drawn into a debate about the merits of these approaches because I can
> already see how much time and motivation that will burn if it happens,
>
Hi,
2018-11-04 17:32 Ben Hutchings:
On Sun, 2018-11-04 at 13:15 +0100, Manuel A. Fernandez Montecelo wrote:
For example RISC-V / riscv64 will probably not have LLVM ready at least
until the LLVM stable released next March.
There are enough languages whose implementation depends on LLVM that
On Sun, Nov 4, 2018 at 2:30 PM Jeremy Bicha wrote:
> On Sun, Nov 4, 2018 at 11:33 AM Ben Hutchings wrote:
> > I do like the proposal of adding a librsvg-c for just the architectures
> > that don't have Rust (yet).
>
> This sounds reasonable. Thanks Samuel for the suggestion. Any
> volunteers to m
On Tue, 06 Nov 2018 12:29:10 +, Ian Jackson wrote:
> Simon McVittie writes ("Re: Should libpam-elogind Provide libpam-systemd
> ?"):
>> Similarly, I think pulseaudio's Recommends is because pulseaudio is
>> frequently a systemd user service (one per uid). One of pulseaudio's
>> control protoco
On Mon, Nov 5, 2018 at 10:32 AM Ian Jackson
wrote:
> So I promised that I would summarise. I found that trying to write a
> summary involved me doing a bit of research, and that not everyone in
> the thread seemed to agree about everything. To make a coherent
> picture I had to make some suppos
On Tue, Nov 06, 2018 at 12:37:30PM +, Jonathan Dowland wrote:
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
Well, if it wasn't for me, we'd probably be shipping the 2.40-version of
librsrv in Debian Buster and Firefox would be missing on a couple of
release archi
Jacob Adams writes:
> The consensus seems to be that people should enable email
> notifications in salsa and open a bug when filing a merge request.
>
> https://lists.debian.org/debian-devel/2018/08/msg00235.html
>
> https://lists.debian.org/debian-devel/2018/08/msg00259.html
Relatedly, what's
On Tue, Nov 06, 2018 at 03:00:03PM +, Matthew Vernon wrote:
>
> Relatedly, what's the etiquette about commits to master? I recently
> discovered that someone else had pushed a commit to the tip of master of
> one of the packages I maintain (and not notified me); when I complained
> I was told
Hi!
On Tue, 2018-11-06 at 15:00:03 +, Matthew Vernon wrote:
> Jacob Adams writes:
> > The consensus seems to be that people should enable email
> > notifications in salsa and open a bug when filing a merge request.
> >
> > https://lists.debian.org/debian-devel/2018/08/msg00235.html
> >
> > h
On 06/11/2018 15:32, Guillem Jover wrote:
> Because, I'm not sure what's the point of hosting a git repo, on a
> platform like gitlab with its trivial forking facilities, on a group
> with wide write permissions, if you don't want others to directly
> write to it? :)
Hm, I had not quite appreciat
On Tue, 06 Nov 2018 10:17:01 -0500, Roberto C. Sánchez wrote:
> On Tue, Nov 06, 2018 at 03:00:03PM +, Matthew Vernon wrote:
>>
>> Relatedly, what's the etiquette about commits to master? I recently
>> discovered that someone else had pushed a commit to the tip of master
>> of one of the packa
On Tue, Nov 06, 2018 at 03:43:41PM +, Felipe Sateler wrote:
>
> I disagree when it comes to the debian namespace, and the documentation
> agrees with me[1].
>
Interesting. I was not aware of that. Thanks for sharing.
Regards,
-Roberto
--
Roberto C. Sánchez
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
On 11/6/18 11:51 AM, Holger Levsen wrote:
Also, you wrote a mail to d-d-a that rust is now running on 14 archs, so
I was utterly surprised about your mail a few hours later blaming
someone who uploaded a rust library.
I
Holger Levsen writes:
> On Tue, Nov 06, 2018 at 10:08:10AM +0100, Bastian Blank wrote:
>> On Tue, Nov 06, 2018 at 01:09:50AM +0100, Adam Borowski wrote:
>>> But only the stock kernel, which turns it non-free software.
>> What is non-free? Signing stuff does not change the freeness of the
>> sof
Guillem Jover wrote:
> On Tue, 2018-11-06 at 15:00:03 +, Matthew Vernon wrote:
[...]
>> that at least a MR is something I should have expected as a package
>> maintainer, not just commits to master?
> Assuming that packages is under the Salsa Debian namespace, then I
> think that's what you (
On Tue, Nov 06, 2018 at 09:21:32AM -0800, Russ Allbery wrote:
> >> What is non-free? Signing stuff does not change the freeness of the
> >> software.
> > it does introduce https://en.wikipedia.org/wiki/Tivoisation however.
> I'm not sure how us signing our stuff does that.
you are right and I wa
On Sat, Nov 3, 2018 at 5:54 PM John Paul Adrian Glaubitz
wrote:
> I'm really annoyed and disappointed by this move and feel really let down by
> this
> behavior. No heads up, no coordination, no nothing.
There was some coordination but the coordination was for release
architectures. The coordina
Hi,
On Tue, Nov 6, 2018 at 11:07 AM Andreas Metzler wrote:
>
> Guillem Jover wrote:
> > On Tue, 2018-11-06 at 15:00:03 +, Matthew Vernon wrote:
> [...]
>
> >> that at least a MR is something I should have expected as a package
> >> maintainer, not just commits to master?
> cu And- plan for t
Package: wnpp
Severity: wishlist
Owner: Friedrich Beckmann
* Package name : libspread-sheet-widget
Version : 0.3
Upstream Author : John Darrington
* URL : https://savannah.gnu.org/projects/ssw
* License : GPL-3
Programming Lang : C
Description
33 matches
Mail list logo
