On Fri, Nov 09, 2018 at 09:29:30PM +0100, Mattia Rizzolo wrote:
I would like to start by highlighting one very important line from my
last email to you:
> > Do not contact me with regard to Debian bullshit.
And yet, you did. Fuck you. Do not contact me again. I shall consider
any further cont
On Fri, Nov 09, 2018 at 05:31:00AM +, Chris Knadle wrote:
> A logical place to check or the lack of BIOS virtualization features and show
> an
> error message for this would be within the .postinst script for the virtualbox
> package in Debian. This way when Virtualbox is installed the user i
> Or an user error. In either case, I don't get what a 32-bit _x86_ virtual
> machine would be good for. Are you teaching some code archeology?
Not at all.
We're trying to make it compulsory for first year students to have a Unix
installation on their personal machine. In practice, this means
> Filing a bug on src:virtualbox with severity 'wishlist' or 'normal' for this
> issue to discuss it with the maintainer of the virtualbox package(s) seems a
> logical thing to do.
Unfortunately, we're speaking about running Debian under VirtualBox under
Windows, so it would need to be something t
On Fri, Nov 09, 2018 at 07:42:13PM +, Holger Levsen wrote:
> Granted, when I first experienced a git push not working after I
> uploaded some package, I was also puzzled and a bit annoyed that someone
> pushed into the master branch of 'my' package, but upon reflection I
> decided:
>
> - this
On Fri, Nov 09, 2018 at 05:41:53PM +, Matthew Vernon wrote:
> Ian Jackson writes:
> > Matthew Vernon writes ("Re: salsa.debian.org: merge requests and such"):
> >> Colin Watson writes:
> >> > This seems like a little bit of an overreaction to somebody removing a
> >> > single redundant line f
Hi,
On Fri, Nov 09, 2018 at 10:56:57AM -0800, Matthew Wilcox wrote:
> For some reason, Debian as a project failed to notice that I had quit,
Probably because even at that time there were procedures that weren't
followed, and apparently nobody after then bothered to check your status
*and* follow
On Fri, Nov 09, 2018 at 05:41:53PM +, Matthew Vernon wrote:
> The particular commit was fine (and had it come as a MR or bug report or
> whatever I'd have had no problem with it at all).
I'm not sure why you are so bothered by it.
Granted, when I first experienced a git push not working afte
I quit Debian development back in 2004. This was a moral decision, based
on the malfeasance of the project secretary over the "Editorial changes"
GR.
For some reason, Debian as a project failed to notice that I had quit,
even though my wi...@debian.org email address was deliberately forwarded
t
Ian Jackson writes:
> Matthew Vernon writes ("Re: salsa.debian.org: merge requests and such"):
>> Colin Watson writes:
>> > This seems like a little bit of an overreaction to somebody removing a
>> > single redundant line from a control file, though. Is moving it really
>> > worth the added fri
Matthew Vernon writes ("Re: salsa.debian.org: merge requests and such"):
> Colin Watson writes:
> > This seems like a little bit of an overreaction to somebody removing a
> > single redundant line from a control file, though. Is moving it really
> > worth the added friction?
>
> It's more a reac
Jonathan Dowland writes:
> On Fri, Nov 09, 2018 at 11:54:50AM +, Matthew Vernon wrote:
>>Putting it under a personal namespace doesn't make it much less visible,
>>and folk can still open MRs...
>
> Oh I beg to differ, there's a huge difference of visibility between the
> "main" Debian projec
Colin Watson writes:
> On Fri, Nov 09, 2018 at 11:54:50AM +, Matthew Vernon wrote:
>> Jonathan Dowland writes:
>> > On Tue, Nov 06, 2018 at 03:42:01PM +, Matthew Vernon wrote:
>> >>Hm, I had not quite appreciated that was the expected behaviour. Ah
>> >>well, I can move it :)
>> >
>> > P
Package: wnpp
Severity: wishlist
Owner: Raúl Benencia
* Package name: golang-github-namsral-flag
Version : 1.7.4-alpha+git20170814.67f268f-1
Upstream Author : Lars Wiegman
* URL : https://github.com/namsral/flag
* License : BSD-3-clause
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Raúl Benencia
* Package name: golang-github-justinas-alice
Version : 0.0~git20171023.03f45bd-1
Upstream Author : Justinas Stankevičius
* URL : https://github.com/justinas/alice
* License : Expat
Programming Lang: Go
D
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss
* Package name: ethflux
Version : 1.0
Upstream Author : DCSO GmbH
* URL : https://github.com/DCSO/ethflux
* License : BSD-3-clause
Programming Lang: Go
Description : InfluxDB data gatherer for eth
On Fri, Nov 09, 2018 at 01:40:59PM +0100, Adam Borowski wrote:
If his students were doing code archaeology or deep embedded, such areas
require enough base skills that getting spooked by 32 vs 64 bits would be
beyond them.
Everyone starts somewhere, even code archaeologists. At my former School
(Please do not CC me, I am subscribed to the list and have set MFT
accordingly, or at least think I have.)
On Fri, Nov 09, 2018 at 11:54:50AM +, Matthew Vernon wrote:
Putting it under a personal namespace doesn't make it much less visible,
and folk can still open MRs...
Oh I beg to diffe
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss
* Package name: balboa
Version : 1.0
Upstream Author : DCSO GmbH
* URL : https://github.com/DCSO/balboa
* License : BSD-3-clause
Programming Lang: Go, C
Description : server for indexing and quer
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss
* Package name: slinkwatch
Version : 1.0
Upstream Author : DCSO GmbH
* URL : https://github.com/DCSO/slinkwatch
* License : GPL
Programming Lang: Go
Description : automatic enumeration and mainten
On Fri, Nov 09, 2018 at 11:54:50AM +, Matthew Vernon wrote:
> Jonathan Dowland writes:
> > On Tue, Nov 06, 2018 at 03:42:01PM +, Matthew Vernon wrote:
> >>Hm, I had not quite appreciated that was the expected behaviour. Ah
> >>well, I can move it :)
> >
> > Please re-consider whether this
On Fri, Nov 09, 2018 at 11:36:36AM +, Jonathan Dowland wrote:
> On Fri, Oct 26, 2018 at 10:41:32PM +0200, Adam Borowski wrote:
> > Or an user error. In either case, I don't get what a 32-bit _x86_ virtual
> > machine would be good for. Are you teaching some code archeology? Do you
> > want t
Jonathan Dowland writes:
> On Tue, Nov 06, 2018 at 03:42:01PM +, Matthew Vernon wrote:
>>Hm, I had not quite appreciated that was the expected behaviour. Ah
>>well, I can move it :)
>
> Please re-consider whether this trade-off (other people pushing to
> master) is a small price to pay for th
On Fri, Oct 26, 2018 at 10:41:32PM +0200, Adam Borowski wrote:
Or an user error. In either case, I don't get what a 32-bit _x86_ virtual
machine would be good for. Are you teaching some code archeology? Do you
want to prepare 32-bit images for something deeply embedded? Neither sounds
an acti
24 matches
Mail list logo
