On Wed, Feb 5, 2014 at 12:08 AM, Charles Plessy wrote:
> The 3.0 (native) format is useful when packaging a work that is developped and
> distributed in a Git repository. Please leave us this possibility.
Can you elaborate a bit? From my understanding of your description I'd
consider your (git)
debconf-devel(7)[1] gives a brief example of managing a key=value
configuration file with debconf
"There are a lot of ways to do this, and most of them are wrong, and
will often earn you annoyed bug reports. Here is one right way to do it.
It assumes that your config file is really just a series
Hi! Thanks for your feedback.
After taking a look into the documentation you provided (and others), I
think there are reasonable doubts about the current status of the security
and privacy levels that Telegram provides to their users. I agree with
Holger that it is not a good idea to package for D
control: subscribe -1
> "Charles" == Charles Plessy writes:
Charles> The 3.0 (native) format is useful when packaging a work
Charles> that is developped and distributed in a Git repository.
Charles> Please leave us this possibility.
Let me describe the use case I have which is
Petter Reinholdtsen writes:
> Before concurrent running of init.d scripts were implemented in sysv-rc,
> the .sh scripts would be sourced by /etc/init.d/rc and /etc/init.d/rcS
> while the non-.sh scripts would be executed. This distinciton were
> removed when sysv-rc started to run scripts in pa
On 2014-02-05 10:57, Sam Hartman wrote:
> tarballs useful; anyone who is likely to want to build this from source
> probably has a copy of git and can checkout a tag.
Such a tag corresponds to an upstrema version?
> I'm happy to entertain other options rather than 3.0(native) but my
> requirement
[Benda]
> What a history! Provided that all the scripts are executed, is there
> any plan to strip the .sh suffix?
Not from me, at least. The advantage would be purely cosmetic, and
the effort to make sure every upgrade problem is handled would be
significant. But new scripts will not get the .s
> "Andreas" == Andreas Beckmann writes:
Andreas> On 2014-02-05 10:57, Sam Hartman wrote:
>> tarballs useful; anyone who is likely to want to build this from
>> source probably has a copy of git and can checkout a tag.
Andreas> Such a tag corresponds to an upstrema version?
y
I've tried to do a reasonable job with the krb5-config package of
updating a user-managed krb5.conf and keeping it in sync with debconf
data.
It's quite old and I doubt it's best practice any more but it is an
example of how to approach a non-shell-script package.
The debconf-managed comment is an
On Wed, 5 Feb 2014 12:21:30 +
Sam Hartman wrote:
> > "Andreas" == Andreas Beckmann writes:
>
> Andreas> On 2014-02-05 10:57, Sam Hartman wrote:
> >> tarballs useful; anyone who is likely to want to build this
> >> from source probably has a copy of git and can checkout a tag
Le Wed, Feb 05, 2014 at 12:46:09PM +0100, Andreas Beckmann a écrit :
>
> All this sounds like it can be done with git-buildpackage
Hello everybody,
I have the impression that we are arguing because of solution in search for a
problem.
Some things worked with the previous version of dpkg, with n
Hi.
I must be very bad at discriminating search engines results, but
couldn't spot any howto for packaging CGI-based Web apps in Debian (the
web apps policy somehow addresses CGIsn but not in a straightforward way,
an is really old :-/).
I'd welcome any such docs or at least examples of maintaine
Guillem writes, on the bug but not on debian-devel:
> Part of the definition of what's and what's not a native package is
> the version scheme, and I've never considered that a Debian specific
> thing specified by its policy. The fact that dpkg-source has been
> sloppy in the past for format 1.0 do
Package: wnpp
Severity: wishlist
Owner: Olivier Berger
* Package name: online-python-tutor
Version : 3
Upstream Author : Philip Guo (http://www.pgbovine.net/)
* URL : http://www.pythontutor.com/
* License : BSD
Programming Lang: Python, Javascript
Descripti
> "Neil" == Neil Williams writes:
That makes sense and I do something similar as appropriate. Even so, I
do not wish to maintain the upstream tarball as a maintained artifact.
There are cases where packaging release releases are made. Maintaining
pristine-tar commits for daily builds is a
* Sam Hartman [140205 13:27]:
> no, that means I have to maintain the artifact (namely the
> .orig.tar.gz).
> The archive software (both reprepro and dak were I to use that) require
> that the .orig.tar.gz not change checksums.
>
> I don't want my build machines to be able to push back to my mast
* Charles Plessy [140205 14:18]:
> Who benefited directly from the change of behavior ? Nobody ? Then please
> revert it; it was not necessary.
Most import are people starting to create Debian packages.
At least with 3.0 source packages they no longer have to care about the
different meanings o
> "Bernhard" == Bernhard R Link writes:
As I mentioned I have a packaging branch and an upstream branch.
I wish to use debian revisions to reflect packaging changes.
It's slightly more complex than changes to debian directory involve a
debian revision change; changes to other things involve
Hi!
On Wed, 2014-02-05 at 13:54:17 +, Ian Jackson wrote:
> Guillem writes, on the bug but not on debian-devel:
> > Part of the definition of what's and what's not a native package is
> > the version scheme, and I've never considered that a Debian specific
> > thing specified by its policy. The
When I do apt-get dist-upgrade I see this happen:
Use 'apt-get autoremove' to remove it.
The following packages will be upgraded:
linux-image-3.12-1-amd64
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
49 not fully installed or removed.
Need to get 0 B/29.6 MB of archives.
After
Package: wnpp
Severity: wishlist
Owner: "Darryl L. Pierce"
* Package name: qpid-dispatch
Version : 0.1
Upstream Author : Qpid Team
* URL : http://qpid.apache.org/
* License : Apache License, Version 2.0
Programming Lang: C/Python
Description : Dispatch
Hey Roelof,
> When I do apt-get dist-upgrade I see this happen:
>
> cannot copy extracted data for
> './lib/modules/3.12-1-amd64/kernel/net/l2tp/l2tp_ip6.ko' to
> '/lib/modules/3.12-1-amd64/kernel/net/l2tp/l2tp_ip6.ko.dpkg-new':
> I see a no space left on device. Which is wierd because I did a
Hi.
A few months ago I drafted an idea to rewrite init.d scripts to use a
common implementation and only specify the unique parts in the init.d
scripts themselves. That draft can be found on
http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
>.
The idea is
Ian Jackson writes:
> Secondly, there doesn't appear to be any support in policy for this
> restriction.
Policy definitely supports this restriction, as Guillem pointed out. I
want to echo that analysis as one of the people to have touched that
portion of the Policy document.
I have always con
On Wed, 5 Feb 2014 22:31:09 +0100
Petter Reinholdtsen wrote:
> Hi.
>
> A few months ago I drafted an idea to rewrite init.d scripts to use a
> common implementation and only specify the unique parts in the init.d
> scripts themselves. That draft can be found on
> http://people.skolelinux.org/p
Sam Hartman writes:
>> "Russ" == Russ Allbery writes:
> Russ> Ian Jackson writes:
> >> Secondly, there doesn't appear to be any support in policy for
> >> this restriction.
> Russ> Policy definitely supports this restriction, as Guillem
> Russ> pointed out. I want to e
> "Russ" == Russ Allbery writes:
Russ> Ian Jackson writes:
>> Secondly, there doesn't appear to be any support in policy for
>> this restriction.
Russ> Policy definitely supports this restriction, as Guillem
Russ> pointed out. I want to echo that analysis as one of the
[Neil Williams]
> Interesting idea - will there be a half-way implementation for daemons
> which require at least some command line options? e.g. logfile and
> loglevel? pidfile?
Sure. It should already support that, like this:
DAEMON_ARGS="-some option"
PIDFILE="/var/run/my.pid
Everything
> "Russ" == Russ Allbery writes:
>> Citation requested. I looked for this today and couldn't find
>> it.
Russ> Policy lacks a section that clearly defines native and
Russ> non-native packages, which is a long-standing bug in Policy.
Russ> Currently, that information is i
Sam Hartman writes:
> However, I cannot read that text to imply anything about what happens if
> the Debian revision is present:
> * Policy seems silent on whether the software MAY?SHOULD NOT/MUST NOT be
> written explicitly for Debian (I consider this a feature)
> * Policy appears silent abo
Petter Reinholdtsen writes:
> A few months ago I drafted an idea to rewrite init.d scripts to use a
> common implementation and only specify the unique parts in the init.d
> scripts themselves. That draft can be found on
> http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example
[Russ Allbery]
> It's probably worth mentioning that this is basically the path down
> which OpenRC went, except that OpenRC has taken the concept somewhat
> further to allow the dependencies to be specified in code instead of
> comments (using special shell functions). You may want to take a
> lo
Hi all,
I would like to add some optimization flags for amd64 arch in some packages
(mostly LV2 nad LADSPA plugins).
I found these as candidates for amd64 arch:
-msse
-msse2
-mfpmath=sse
-ffast-math
-ftree-vectorize
-mtune=generic
Can some of them be safely added for amd64 or is just bad idea?
S
On 06.02.2014 00:39, Jaromír Mikeš wrote:
>
> Hi all,
>
> I would like to add some optimization flags for amd64 arch in some
> packages (mostly LV2 nad LADSPA plugins).
> I found these as candidates for amd64 arch:
>
> -msse
> -msse2
> -mfpmath=sse
this is enabled by default on amd64
> -ffast-
On Wed, Feb 5, 2014 at 9:35 PM, Olivier Berger wrote:
> Thanks in advance for any pointers.
General principles are the same for all web apps regardless of technology.
Ship the code and data in /usr/share/.
Ship a tool to create web server configuration (vhosts or subURLs) in
/usr/sbin. You can'
On Thu, Feb 6, 2014 at 8:43 AM, Paul Wise wrote:
> Which CGI are we talking about? Perhaps we can give more specific advice.
I guess you mean Online Python Tutor (#737732).
Looking at the git repo, it includes a lot of embedded code copies of
various JavaScript libraries and other code. As per p
On 5 February 2014 20:08, Guillem Jover wrote:
> Hi!
>
> On Wed, 2014-02-05 at 13:54:17 +, Ian Jackson wrote:
>> Guillem writes, on the bug but not on debian-devel:
>> > Part of the definition of what's and what's not a native package is
>> > the version scheme, and I've never considered that
Greetings,
I've started packaging PasswordSafe (a GUI password manager) which ships
a binary named pwsafe.
Oldstable contains the pwsafe package (a command line password manager
based on an earlier version of PasswordSafe) which also ships a binary
named pwsafe.
The policy says:
"Two differ
Bill Blough writes:
> I've started packaging PasswordSafe (a GUI password manager) which ships
> a binary named pwsafe.
> Oldstable contains the pwsafe package (a command line password manager
> based on an earlier version of PasswordSafe) which also ships a binary
> named pwsafe.
Given that
在 2014年1月21日，下午9:51，Aníbal Monsalve Salazar 写道：
> On Tue, Jan 21, 2014 at 01:43:55PM +0100, Matthias Klose wrote:
>> Am 16.01.2014 13:31, schrieb Aníbal Monsalve Salazar:
>>> For mips/mipsel, I - fix toolchain issues together with other
>>> developers at ImgTec
>>
>> It is nice to see such a co
40 matches
Mail list logo
