Package: wnpp
Severity: wishlist
Owner: Bas Wijnen <[EMAIL PROTECTED]>
* Package name: sdljump
Version : 0.91-1
Upstream Author : Juan Pedro Bol\('ivar Puente <[EMAIL PROTECTED]>
* URL : http://sdljump.sourceforge.net
* License : GPL
Des
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen <[EMAIL PROTECTED]>
* Package name: z80asm
Version : 0.1
Upstream Author : Bas Wijnen <[EMAIL PROTECTED]>
* URL : http://savannah.nongnu.org/projects/z80asm/
* License : GPL
Description : a
On Thu, Oct 05, 2006 at 12:57:51AM +0200, Michelle Konzack wrote:
> I would like to know what happen with him?
I don't know anything about Stan, but AFAIK these sort of queries should be
sent to [EMAIL PROTECTED], so they don't show up on google. It's not a nice
thing to have your name mentioned
On Thu, Feb 07, 2008 at 09:14:09PM +0500, Alexander E. Patrakov wrote:
>> Some of the USB devices I have, are missing in lsusb list, this ussue
>> is in Testing and Unstable.
>> In Ubuntu Linux and Debian Etch all my devices are listed.
>
> I suspect that there is some problem with udev (assuming
On Mon, Feb 11, 2008 at 02:48:33AM -0800, Mike Bird wrote:
> On Mon February 11 2008 02:20:26 Cyril Brulebois wrote:
> > On 11/02/2008, Mike Bird wrote:
> > > On *production* Debian systems, saving 30 seconds in a boot which
> > > may occur once a year for a kernel security update is not worth a
>
On Wed, Feb 13, 2008 at 06:41:57PM +0100, David Paleino wrote:
> Kapil Hari Paranjape <[EMAIL PROTECTED]> ha scritto:
> > I was wondering how to interpret the GR altering upload rules
> > (http://www.debian.org/vote/2007/vote_002) in practical terms.
>
> This is the relevant bit, I think:
>
> /-
On Wed, Feb 20, 2008 at 06:44:13PM +0200, Shachar Shemesh wrote:
>> W: fakeroot-ng: copyright-without-copyright-notice
>> N:
>> N: The copyright file for this package does not appear to contain a
>> N: copyright notice. You should copy the copyright notice from the
>> N: upstream source (or a
On Sat, Mar 01, 2008 at 08:49:05PM +0100, Romain Beauxis wrote:
> I figured out that all newcomers are required to have contributions in
> Debian, which means *new packages*.
Not at all. They must maintain at least one (but preferrably more)
packages (if they want to do packaging). They may be t
Hi,
On Thu, Mar 13, 2008 at 03:20:28PM +0100, Julian Andres Klode wrote:
> I would like to suggest two major improvements related to packages
> which are "Architecture: all".
>
> The first thing I want to suggest is the handling of dependencies.
> When building a package, you can use "Depends: pa
[Adding bug #437392 to Cc, which deals with this issue for normal NMUs,
because I'm making a suggestion about them.]
On Sat, Mar 15, 2008 at 11:52:55PM +, Adam D. Barratt wrote:
> devscripts 2.10.19 (soon to be uploaded) will modify the behaviour of
> "debchange --nmu" to version an NMU of a n
On Sun, Mar 16, 2008 at 03:47:56AM -0700, Steve Langasek wrote:
> The current binNMU numbering scheme was selected explicitly to allow
> security uploads to sort later by numbering as
> +; e.g., 1.2-5.1+etch1.
This could also lead to a problem in very rare cases: If a program has
the same version
On Sun, Mar 16, 2008 at 08:23:43PM +0900, Charles Plessy wrote:
> Le Sun, Mar 16, 2008 at 12:10:13PM +0100, Bas Wijnen a écrit :
> >
> > This could also lead to a problem in very rare cases: If a program has
> > the same version in stable and testing, and gets a security
On Sun, Mar 16, 2008 at 06:40:25PM +, Adam D. Barratt wrote:
> On Sun, 2008-03-16 at 11:22 -0700, Russ Allbery wrote:
> > "Adam D. Barratt" <[EMAIL PROTECTED]> writes:
> > > On Sun, 2008-03-16 at 09:06 +0100, Bas Wijnen wrote:
> [...]
> > >>
On Mon, Mar 17, 2008 at 02:38:19AM -0300, Martín Ferrari wrote:
> Following the trend to add metadata to the debian/control file that
> allows for the creation of new and powerful tools, I thought about the
> usefulness of a header that'd allow to automatically relate to
> upstream bug trackers.
I
On Mon, Mar 17, 2008 at 04:46:54PM +0100, Vincent Danjean wrote:
> Bas Wijnen wrote:
> > Ok, that makes sense. However, with +nmu1, there still is the problem
> > of how to name security uploads. With +s1, they sort after +nmu1, which
> > I think is wrong.
> >
On Wed, Mar 19, 2008 at 11:37:07AM -0700, Russ Allbery wrote:
> Bas Wijnen <[EMAIL PROTECTED]> writes:
>
> > You can base security uploads on NMUs, so I think you could get
> > +s1+nmu1+s1+nmu1, etc. Or should it go from +s1 to +s1+nmu1 to +s2 to
> > +s2+nmu1?
On Sun, Apr 06, 2008 at 03:18:58PM +0200, Martijn van Oosterhout wrote:
> On Sun, Apr 6, 2008 at 6:48 AM, Simon Richter <[EMAIL PROTECTED]> wrote:
> > The use case here are people downloading a tarball and building that.
> > These people are going to use a prebuilt configure script and expect the
Hi,
On Wed, Apr 16, 2008 at 01:08:05PM +0200, Ondrej Certik wrote:
> if I want to packge a new upstream version of DM-Upload-Allowed
> library (for example [1]), it changes the name of the binary package
> and thus goes to NEW.
>
> Last time I asked it wasn't possible for me, as a DM, to upload i
First of all, I skipped a large part of this thread, so I'm sorry if
this has come up before.
On Wed, Apr 16, 2008 at 03:53:03PM +0100, Neil Williams wrote:
> > And by this definition, it is the package _invoking_ pkg-config that
> > should Build-Depend on it, not the package that happens to ship
On Wed, Apr 16, 2008 at 07:57:00PM +0200, Gabor Gombas wrote:
> On Wed, Apr 16, 2008 at 07:15:53PM +0200, Goswin von Brederlow wrote:
>
> > You are missing the point.
> >
> > What if the library says "You must call /usr/bin/foo during build"?
>
> But the library can't say "foo must come from a D
On Thu, Apr 17, 2008 at 01:44:55AM -0500, Manoj Srivastava wrote:
> >> > What if the library says "You must call /usr/bin/foo during build"?
> >>
> >> How does the library say that? Why can't I just have gcc -o baz baz.c
> >> -lfoo
> >>
> >> How can the library make that not work?
>
> > By not s
On Wed, Apr 16, 2008 at 07:21:15PM +0100, Neil Williams wrote:
> > According to the suggested definition, if a package using this library
> > chooses to use foo-config, it doesn't call pkg-config directly (and it
> > may not call it at all, this depends on the inner workings of
> > foo-config).
>
On Fri, Apr 18, 2008 at 02:09:40PM -0500, Manoj Srivastava wrote:
> I would say they are making it very inconvenient, but still not
> forcing you. Push comes to shove, you can still build depend on a
> specific version, and use an explicit -L.
That is correct, of course. But if you're u
On Thu, Apr 17, 2008 at 12:54:32PM +0200, Gabor Gombas wrote:
> On Thu, Apr 17, 2008 at 12:02:20PM +0200, Bas Wijnen wrote:
>
> > How is this different with _any_ dependency on the system? Do you
> > suggest that iceweasel should drop its libgtk dependency, because users
>
Hi,
We (Bas Wijnen, Lucas Nussbaum) worked on a Debian Enhancement
Proposal[0] on the policies and workflows for Non Maintainer Uploads
(NMUs).
The main purpose of the proposal is:
* to explicitely allow fixing bugs of severity lower than important in
NMUs.
* to encourage the use of the
On Sun, May 18, 2008 at 04:11:09PM +0200, Pierre Habouzit wrote:
> IOW basically, just do your usual workflow, bts-link adds 0 overhead
> on your work, that's exactly why it's valuable.
Huh? This is just as true for the proposal we're discussing here, which
you seem to claim gives too much over
On Sun, May 18, 2008 at 03:18:12PM +0200, Pierre Habouzit wrote:
> But the problem we want to solve is making things easier for
> upstreams.
Oh? When I read the proposal, I understood that the problem we want to
solve is about tracking changes we make to upstream. If upstream wants
those changes
On Sun, Oct 12, 2014 at 04:33:46AM +0200, Michael Ole Olsen wrote:
> there is nothing wrong with urging people to reconsider if non-free is
> really what they want
+1.
> We shouldn't even be supporting non-free by hosting it, yet we do
That is not our reason for hosting it. We are hosting it to
[Moving this to -project, where it belongs; please follow up only
there, not on -user or -devel.]
On Sun, Oct 12, 2014 at 06:18:01PM +0200, lee wrote:
> Why doesn't Debian just do a GR on this issue?
Because for a GR, a member of Debian has to request it and it needs to
be seconded by at least 5
On Tue, Oct 14, 2014 at 11:20:02AM +0200, Andreas Tille wrote:
> I admit I expected *you* to know about Blends for a while - but
> considering the video recorded quote I think I was not wrong using this
> chance to point this out for other readers of this mail as it is really
> a fact that I always
Hi,
On Wed, Oct 15, 2014 at 09:31:36AM +0200, Andreas Tille wrote:
> You belong to a majority if I might conclude from my experience. I have
> no idea whether I should feel responsible for this but I'm fighting on
> several fronts like the extensive documentation[1] and countless
> talks[2] as we
Hello,
On Thu, Oct 16, 2014 at 08:47:19AM +0200, Andreas Tille wrote:
> > Would this use case also be a reason for creating a personal blend? Or
> > even an official one?
>
> Jonas has answered this question. I'd like to add that I'm no fan of
> "personal" things since you spoil the idea of for
On Thu, Oct 16, 2014 at 05:35:09PM +0100, Martin Read wrote:
> mormegil@cocytus:~$ cat /etc/apt/apt.conf.d/00dontbeanidiot
> Aptitude::ProblemResolver {
> SolutionCost "priority, removals, canceled-actions";
> }
That looks very useful, thanks!
Bas
signature.asc
Description: Digital signature
nd it is the first ever perl
program I wrote. So please don't insult me, but also don't hold back
when you see things that need to be improved. :-)
Thanks,
Bas
On Tue, Nov 26, 2013 at 06:16:19PM -0800, Russ Allbery wrote:
> Bas Wijnen writes:
>
> > What this means, is tha
On Fri, Oct 17, 2014 at 12:37:27PM +0800, Thomas Goirand wrote:
> On 10/17/2014 04:34 AM, Bas Wijnen wrote:
> > So debconf needs to read configuration files, but it doesn't know how to
> > parse them. So it does the only thing it can: it uses its cache. Which
> >
On Fri, Oct 17, 2014 at 03:51:04PM +0800, Thomas Goirand wrote:
> On 10/17/2014 01:41 PM, Bas Wijnen wrote:
> > Getting random packages from apt-cache rdepends debconf shows:
> >
> > - several packages that use debconf for questions that are only about
> > actions
Hi,
On Wed, Nov 19, 2014 at 12:40:00AM -0800, Keith Packard wrote:
>
> I'd like to apologize to the systemd maintainer team, and to Tollef in
> particular for my TC vote on the libpam-systemd bug.
>
> The discussion on this issue was an excellent model of the Debian
> community at work:
Thank y
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: python-lua
Version : 0.1
Upstream Author : Bas Wijnen
* URL : None, first publication will be in Debian
* License : GPL-3+
Programming Lang: Python
Description : library for using lua
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: wherpygo
Version : 0.1
Upstream Author : Bas Wijnen
* URL : None, first publication will be in Debian.
* License : AGPL-3+
Programming Lang: Python
Description : player for wherigo
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: python-wherigo
Version : 0.1
Upstream Author : Bas Wijnen
* URL : https://github.com/wijnen/python-wherigo
* License : AGPL-3+
Programming Lang: Python
Description : python module for
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: python-network
Version : 0.1
Upstream Author : Bas Wijnen
* URL : https://github.com/wijnen/python-network
* License : AGPL-3+
Programming Lang: Python
Description : python module for
On Mon, May 27, 2013 at 09:04:53AM +0200, Ondřej Surý wrote:
> On Sat, May 25, 2013 at 8:02 PM, Russ Allbery wrote:
> > He still files all upstream bugs with Debian, but I can't throw stones
> > there;
I do not think this is wrong. In fact, one of the reasons I like Debian, is
that I can report
ple to do all the work they would like
to do", then I agree. But setting up a different team with exactly the same
purpose under a new name isn't going to solve that problem.
> On Mon, May 27, 2013 at 4:21 PM, Bas Wijnen wrote:
> > I agree. On a completely different level, those
On Wed, Jun 19, 2013 at 07:56:26PM +0100, Ben Hutchings wrote:
> On Wed, Jun 19, 2013 at 09:12:37AM -0700, Steve Langasek wrote:
> [...]
> > The *only* argument for using local time in the system clock is so that the
> > time displayed in the timezone-ignorant BIOS will be correct. But who looks
>
On Fri, Sep 20, 2013 at 10:12:16PM -0700, Kees Cook wrote:
> This is absolutely a bug in glibc. While the spec can say "undefined", it
> is, in fact, not undefined. It worked in a very specific way for over a
> decade, so that's pretty well defined. ;) The fortify function has no need
> to change i
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: libpolyclipping
Version : 6.0.0
Upstream Author : Angus Johnson <http://sourceforge.net/projects/polyclipping>
* URL : http://sourceforge.net/projects/polyclipping
* License : GPL, BS
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: repsnapper
Version : 1.9.0
Upstream Author : Michael Meeks
* URL : http://reprap.org/wiki/RepSnapper_Manual:Introduction
* License : GPL2+
Programming Lang: C++
Description : STL to
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: vmmlib
Version : 0~svn540
Upstream Author : Stefan Eilemann , Jonas Boesch
, Susanne Suter
* URL : http://http://vmmlib.sourceforge.net/
* License : BSD
Programming Lang: C++
Description
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: slic3r
Version : 0.9.3
Upstream Author : Alessandro Ranellucci
* URL : http://slic3r.org/
* License : AGPL-3
Programming Lang: Perl, C++
Description : STL-to-GCODE translator for 3D
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: arduino-mighty-1284p
Version : 0~svn20130430
Upstream Author : http://maniacbug.wordpress.com/
* URL : https://github.com/maniacbug/mighty-1284p
* License : LGPL-2.1+, GPL-2+, GPL-3+, MIT
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: cura
Version : 13.04~git20130502-1
Upstream Author : David Braam (daid...@gmail.com)
* URL : http://daid.github.io/Cura/
* License : AGPL-3+
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: cura-engine
Version : 13.06~git20131109
Upstream Author : Daid
* URL : https://github.com/Ultimaker/CuraEngine
* License : AGPL
Programming Lang: C++
Description : commandline slicer
e configuration file. (in the postinst script)
Currently, many packages only do 2, and that is wrong.
Now I'll quote a piece from the bug log, because I think it's written
clear there:
On Sat, Oct 13, 2012 at 01:27:31PM -0400, Joey Hess wrote:
> Bas Wijnen wrote:
> > The proposed sol
On Tue, Nov 26, 2013 at 09:44:40PM -0400, Joey Hess wrote:
> Bas Wijnen wrote:
> > Currently, many packages only do 2
>
> (Citation needed.)
http://codesearch.debian.net/search?q=db_get+path%3A.*config%24
On Tue, Nov 26, 2013 at 06:16:19PM -0800, Russ Allbery wrote:
> > Cur
On Wed, Nov 27, 2013 at 12:38:38AM -0400, Joey Hess wrote:
> Bas Wijnen wrote:
> > > (Citation needed.)
> >
> > http://codesearch.debian.net/search?q=db_get+path%3A.*config%24
>
> If the presence of db_get in a config script was always a bug, then I
> [cw]oud m
On Wed, Nov 27, 2013 at 07:10:23AM -0400, Joey Hess wrote:
> Bas Wijnen wrote:
>
> (1)
>
> > It's not about overwriting.
>
> (2)
>
> > The point is that debconf will use its own
> > cache for defaults, which means that running dpkg-reconfigure and
On Wed, Nov 27, 2013 at 05:13:55PM +0100, Andreas Beckmann wrote:
> 1) manually configure $package using custom values
> 2) rm -rf /var/cache/debconf
> 3) DEBIAN_FRONTEND=noninteractive dpkg-reconfigure $package
...
> step 1 is the difficult part (someone needs to create custom
> preseeding for eve
On Wed, Nov 27, 2013 at 11:39:50AM -0400, Joey Hess wrote:
> Bas Wijnen wrote:
> > Debconf actively overwriting values is slightly different from it giving
> > you a wrong default which it then allows you to set to the desired value
> > again. The former is overwriting, th
> Date: Mon, 9 Dec 2013 15:27:11 +0100
> From: Holger Levsen
> To: 601455-d...@bugs.debian.org
> Subject: thats the way these init scripts are, use something else if you care
> about this
>
> I've decided to close this bug, as this "mis-feature" / bug is actually a
> main
> characteristic of s
On Sat, Dec 14, 2013 at 08:27:45PM +0530, V.Krishn wrote:
> On Friday, December 13, 2013 08:31:51 PM you wrote:
> > Was going through LSB Core 4.1.
> >
> > I am looking at LSB core section 20.8 ...
> >
> > Confirming set -e
> >
This is a useless quote. You mean:
> Conforming scripts shall
Hi,
On Thu, Mar 27, 2014 at 07:41:50PM -0700, Steve Langasek wrote:
> I can understand the ftp team's desire to sidestep any moral questions here,
> but in the process I think your guidelines have wound up vague and
> overbroad, as they suggest that as a project we will never take a stand for
> an
On Tue, Apr 01, 2014 at 11:04:43AM +0100, Philip Hands wrote:
> I think the real problem here is the user interface asking one to trust
> a site (forever, unless you're concentrating) at a point where you
> really don't care because all you're interested in is seeing the cute
> picture of an otter
First of all, I agree that we should provide a system that is as usable
as possible. If a desktop environment such as Gnome chooses to use an
inferior product, we don't have to let _our_ users suffer from that
choice. Having a client which integrates well with the system is nice,
but what's more
On Tue, Apr 01, 2014 at 10:49:15PM +0100, Kevin Chadwick wrote:
> > I think at Debian we all agree that it would be a good
> > thing if everything would be encrypted, so this is a very bad outcome.
>
> I beg to differ I'm afraid. SSL should be used where it is required
> otherwise you are opening
FTR: I like running autoreconf to make sure actual sources are used, and
to document the build process for users who want to change any source
file, including Makefile.am etc.
On Thu, Apr 17, 2014 at 07:08:30PM +0200, Jonas Smedegaard wrote:
> a) I dislike dh-autoreconf: It removes changed files
On Fri, Apr 25, 2014 at 01:27:02AM +0100, Manuel A. Fernandez Montecelo wrote:
> I don't think that this is different to my example of 'configure'
> script without corresponding .ac/.in; and I don't think that anybody
> is thinking about adding lintian errors for that or considering those
> scripts
On Fri, Apr 25, 2014 at 10:47:20AM +0100, Manuel A. Fernandez Montecelo wrote:
> Thus, the file itself being source code,
You are the only one who uses a definition of source code that includes
generated files. This is confusing; please don't do that.
> So I believe that the lintian error consid
On Sat, Apr 26, 2014 at 07:13:33PM +0100, Manuel A. Fernandez Montecelo wrote:
> I would argue that conceptually the same is true of well-known
> minified JS libs: you take the new unminified, substitute it, and are
> done with it -- that the exact source code changes is not important,
> as long as
On Fri, May 02, 2014 at 11:18:33AM -0700, Russ Allbery wrote:
> Paul Tagliamonte writes:
> > On Fri, May 02, 2014 at 06:40:26PM +0100, Ian Jackson wrote:
>
> >> I'm starting to get tempted. If we have a GR on it, regardless of the
> >> outcome, we can stop these arguments a bit sooner.
>
> > Pl
On Fri, May 02, 2014 at 09:21:15PM +0200, Svante Signell wrote:
> Does the Debian guidelines give any hints on who is responsible to
> report a patch upstream? Is it the bug submitters or the Debian package
> maintainers responsibility (in addition to eventually apply them to the
> packages)?
I do
On Fri, May 02, 2014 at 03:58:37PM -0400, Paul Tagliamonte wrote:
> On Fri, May 02, 2014 at 09:20:02PM +0200, Bas Wijnen wrote:
> > Is there any disagreement about this? As far as I've understood so far,
> > there
> > are only two points that keep being discussed:
>
On Sun, May 04, 2014 at 09:14:50AM +0200, Marc Haber wrote:
> >I don't think this is very clear from the guidelines, and I have had mixed
> >responses from maintainers when reporting upstream bugs, varying from
> >"thanks,
> >I'll report it upstream for you" to "stop wasting my time, report it ups
On Sun, May 04, 2014 at 05:36:53PM +0200, Jonas Smedegaard wrote:
> I cannot imagine *any* example of a bug reported reported according to
> guidelines being a waste of time.
>
> Can you provide examples of that kind of response?
I remember it happening only once, and it was quite a while ago.
On Tue, May 06, 2014 at 06:44:16PM -0700, Jose Luis Rivas wrote:
> I saw it and I fail to see what exactly they want to achieve with this
> change since AGPLv3 is for web apps.
I license almost all my work as AGPL, because I like that clause. The idea of
the GPL is to make sure that all end users
On Wed, May 07, 2014 at 05:18:36PM +1000, Ben Finney wrote:
> the problem is for the package maintainer to assert that *is* the
> corresponding source for a particular work.
>
> We should not, IMO, accept such an assertion without an independently
> verifiable guarantee that can be automated for e
On Wed, May 07, 2014 at 10:48:46PM +0200, Jean-Christophe Dubacq wrote:
> texlive-bin uses the software (gs), As you, yourself, said, the
> difference between the AGPL and the GPL is that the AGPL protects the
> user, not only the people that download the software. This means that by
> some interpr
On Fri, May 09, 2014 at 10:56:43AM -0700, Steve Langasek wrote:
> The default hasn't changed; sysvinit still lists sysvinit-core as the first
> alternative for its pre-dependency on /sbin/init. What is forcing
> systemd-sysv onto users systems in advance of this change?
Also, if the order of depe
On Fri, May 09, 2014 at 10:37:03PM +0200, Tollef Fog Heen wrote:
> It and upstart (and any other providers of /sbin/init) should also grow
> critical debconf warnings if you install them and you were previously using
> systemd as your init so it's symmetric.
Nobody is suggesting that systemd shoul
I think this is a good example of how not to respond to reports, as we recently
discussed on this list. Even though most parts are excellent. :-)
On Sat, May 10, 2014 at 03:36:26PM +0200, Laurent Bigonville wrote:
> The root cause of this bug is [...]
This part is useful.
> So please get dirmng
On Sun, May 11, 2014 at 08:20:33PM +0200, Svante Signell wrote:
> Can we please separate the bugs in this thread: This one is about
> dirnmgr not network-manager and gdm3 dragging in systemd as init
> default, #747535.
Speaking of that, I made a suggestion that AFAIK fixes the issue, which isn't
i
On Mon, May 12, 2014 at 11:54:43AM +0200, Josselin Mouette wrote:
> Systemd is the default init system for jessie, and it should be listed
> as the first alternative.
Can you please explain what is wrong with my reasoning?
A default is only relevant at the time the functionality is first installe
On Mon, May 12, 2014 at 09:19:40AM -0700, Josh Triplett wrote:
> Having libpam-systemd depend on "systemd-shim | systemd-sysv" will not
> properly
> handle systems that already have systemd installed but not systemd-sysv.
I don't think I understand what you mean. What does "having systemd instal
On Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett wrote:
> > In other words: what isn't handled properly? What should happen, and what
> > does
> > happen?
>
> Consider a system which has systemd installed, systemd-sysv *not* installed,
> and systemd used as PID 1 via init=/bin/systemd. S
On Mon, May 12, 2014 at 07:01:14PM -0700, Russ Allbery wrote:
> Dependency-based boot, the change to /bin/sh, and UUID-based mounting were
> all not drop-in replacements by that criteria.
Note that also none of them were forced on existing installations. The change
of /bin/sh to dash (which is wh
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: pvcam-dkms
Version : 4.1.0.
Upstream Author : Bas Wijnen
* URL : None yet, hopefully soon on http://alioth.debian.org.
* License : GPL
Programming Lang: C
Description : kernel module
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: libpvcam
Version : 2.7.0.0
Upstream Author : Unknown, unmaintained.
* URL : http://www.photometrics.com/support/downloads/lin_pvcam.php
* License : None
Programming Lang: Probably C
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: pvcam-utils
Version : 0.1
Upstream Author : Bas Wijnen
* URL : None yet, hopefully soon http://alioth.debian.org/.
* License : GPL
Programming Lang: C++
Description : utilities for
Hi,
On Thu, Jul 09, 2015 at 05:26:32PM +0200, Ansgar Burchardt wrote:
> I'm wondering about the shared library packaging requirements in Policy
> for the special case of scientific libraries that are not intended to be
> used by applications, but are to be used by end-users directly,
What does "t
On Mon, Jul 13, 2015 at 08:01:48PM -0500, Dirk Eddelbuettel wrote:
> | To make it work only when served by a webbrowser, use this:
> |
> |
>
> I think this is what I had in mind, thanks!
>
> | ...and make sure javascript-common is installed and in use by the
> | web-server (all libjs-* pack
On Tue, Jul 14, 2015 at 05:56:56AM -0500, Dirk Eddelbuettel wrote:
> | Can't you make a link in the directory of the file referencing it and use
> | a non-absolute path, i.e. src="MathJax.js"? That should work both locally
> and
> | through a browser without any configuration, right? (Except tha
On Tue, Jul 14, 2015 at 04:21:07PM +0200, Wouter Verhelst wrote:
> On Mon, Jul 06, 2015 at 02:10:08PM +0800, Paul Wise wrote:
> > Perhaps we could run everything in $PATH in virtual machines and log
> > all network beyond localhost.
>
> I look forward to not reading your emails anymore ;-P
>
> (o
On Wed, Jul 15, 2015 at 01:06:28AM +0200, Jakub Wilk wrote:
> POST
> https://safebrowsing.google.com/safebrowsing/downloads?client=Iceweasel&appver=38.1.0&pver=2.2&key=no-google-api-key
> + a few dozens of GET requests to https://safebrowsing.google.com/
>
> So nothing serious here. It's just cas
On Wed, Jul 15, 2015 at 01:26:16PM +0900, Mike Hommey wrote:
> On Wed, Jul 15, 2015 at 03:51:42AM +0200, Bas Wijnen wrote:
> > On Wed, Jul 15, 2015 at 01:06:28AM +0200, Jakub Wilk wrote:
> > > POST
> > > https://safebrowsing.google.com/safebrowsing/downloads?client=I
On Wed, Jul 15, 2015 at 07:56:42PM +0100, Ian Jackson wrote:
> Right. I find it disappointing to discover that in Debian we have
> deliberately modified Iceweasl to make this problem worse, even if
> only in a modest way.
...
> And one thing we could easily do (well, easily from a technical point
Hi,
On Thu, Jul 16, 2015 at 06:00:17PM +0200, Simon Richter wrote:
> Am 16.07.2015 um 16:57 schrieb Don Armstrong:
> > How easy would it be to modify the code so that it only gets the
> > favorite icons when the site is actually visited? [Does it already try
> > to update the icons when it visits
On Fri, Jul 17, 2015 at 05:30:04PM +0200, Ansgar Burchardt wrote:
> It's less of a library than an environment used for research. Compiling
> is just a required step to run your code, but applications are usually
> not distributed in binary form.
What is the benefit of providing a shared library a
On Sun, Jul 19, 2015 at 11:06:45AM +0200, Eduard Bloch wrote:
> > > It's less of a library than an environment used for research. Compiling
> > > is just a required step to run your code, but applications are usually
> > > not distributed in binary form.
> >
> > What is the benefit of providing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Aug 02, 2015 at 05:44:06PM +0200, Christoph Anton Mitterer wrote:
> Some ideas that pop up in my mind:
> - Would be yet another location of privacy leak in Debian, where the
> system automatically calls "home" to some more commercial than
> com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Aug 25, 2015 at 07:17:12PM +0200, Jonas Smedegaard wrote:
> Quoting Scott Kitterman (2015-08-25 17:57:11)
> > AFAIK we've only ever discussed the need to provide source. I don't
> > know why there would be a requirement to reminify.
>
> I se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Aug 25, 2015 at 07:08:06PM +0100, Ian Jackson wrote:
> Bas Wijnen writes ("Re: Security concerns with minified javascript code"):
> > AFAIK Debian doesn't *require* generated files to be rebuilt. For
> > example,
1 - 100 of 167 matches
Mail list logo
