On 08/10/2010 09:25 PM, Adam D. Barratt wrote:
>> > Chromium isn't meant to be released with Squeeze. We'll reevaluate for
>> > Squeeze+1.
> Is that still the case?
No, it isn't. Please see #581265 and in particular message #32, #37 and #44
Cheers,
Giuseppe.
signature.asc
Description: OpenPGP
Hi,
while working on a package I'm going to sponsor, it occurred to me with
all the DD, DM and sponsoring going on, that I'd like to have a field
in debian/control, like eg.
Bugs-To: some...@debian.org, ...
to have some...@debian.org automatically subscribed to the bugs for
this package, much
* Russ Allbery [100811 05:27]:
> If you're implementing 3.0 format, please don't hard-code the extensions that
> you "know" will be found in source packages, because as we add additional
> files listed in *.dsc, we may add other types of files.
Please be carefull with adding new extensions. Those
On Tue, 2010-08-10 at 18:08 +, Ian Zimmerman wrote:
> Steve Langasek debian.org> writes:
>
> > But again, as Thomas points out, you can address this use case with much
> > less per-package effort. A centralized ten-line shell script would be
> > enough to locate all the installed packages on
Steve Langasek writes:
> On Tue, Aug 10, 2010 at 11:53:10PM +0200, Goswin von Brederlow wrote:
>> Bruce Sass writes:
>
>> Note that there is /lib/libcrypt* (at least here). This is just the more
>> optimized flavour the ld.so picks when the cpu supports it.
>
> libcrypt != libcrypto.
Ups, sorry
Toni Mueller writes:
> while working on a package I'm going to sponsor, it occurred to me
> with all the DD, DM and sponsoring going on, that I'd like to have a
> field in debian/control, like eg.
>
> Bugs-To: some...@debian.org, ...
In the source package stanza, or the binary package stanza?
>
On Tue, Aug 10, 2010 at 08:27:24PM -0700, Russ Allbery wrote:
> source.debian.org is working on importing source packages into a Git
> repository and storing the history as one revision per new source package
> upload.
That gives a 404. source.debian.net doesn't, but gives you a page with
as full
On Wed, Aug 11, 2010 at 10:31 AM, Wouter Verhelst wrote:
> On Tue, Aug 10, 2010 at 08:27:24PM -0700, Russ Allbery wrote:
>> source.debian.org is working on importing source packages into a Git
>> repository and storing the history as one revision per new source package
>> upload.
>
> That gives a
Hi,
Toni Mueller wrote:
> in debian/control, like eg.
>
> Bugs-To: some...@debian.org, ...
This is the info which IMHO belongs to PTS and should stay there.
> I have found out that there are other ways to get at the bug reports
> for some random package, but this could probably simplify things f
On Tue, Aug 10, 2010 at 08:27:24PM -0700, Russ Allbery wrote:
> After a discussion on IRC, I organized a BoF at DebConf10 to discuss new
> source formats, specifically 3.0 (git). Below are the notes from that
> discussion. I tried to take reasonably comprehensive notes, but I'm sure
> that I miss
]] Russ Allbery
| After a discussion on IRC, I organized a BoF at DebConf10 to discuss new
| source formats, specifically 3.0 (git). Below are the notes from that
| discussion. I tried to take reasonably comprehensive notes, but I'm sure
| that I missed things. Other participants, please add a
Russ Allbery writes ("Notes from the DebConf Source Format BoF"):
> * Part of Joey's motivation is that if you look at GitHub, the
> people using it a lot consider Git to be a source package format,
I've been doing that for some non-Debian work. It turns out to be
incredibly convenient, if you'
Tollef Fog Heen writes:
> ]] Russ Allbery
> | After a discussion on IRC, I organized a BoF at DebConf10 to discuss new
> | source formats, specifically 3.0 (git). Below are the notes from that
> | discussion. I tried to take reasonably comprehensive notes, but I'm sure
> | that I missed things
On 08/11/2010 06:47 PM, Ian Jackson wrote:
Russ Allbery writes ("Notes from the DebConf Source Format BoF"):
* Part of Joey's motivation is that if you look at GitHub, the
people using it a lot consider Git to be a source package format,
I've been doing that for some non-Debian work. It tu
On Mon, Aug 9, 2010 at 4:58 PM, Thomas Goirand wrote:
> 2/ Ask for help for packaging swfupload
...
> How to fix the SWFUpload issue:
> - ---
> The SWFUpload is a client side file upload tool that uses a combination
...
AFAICT the source code is ActionScript 3 so you
On Tue, 2010-08-10 at 22:29 +0200, Andreas Tille wrote:
> I just tried to give some advise about proper placement of database
> files in a Debian package and I was sure I could simply link to the
> relevant paragraph in policy but there is none. Is the usage of
> /var/lib/ just a reasonable habit
On Tue, 2010-08-10 at 03:15 -0600, Bruce Sass wrote:
> I was curious so...
> $ for f in /bin/* /sbin/*; do if [ "`file $f | grep ELF`" != "" ] ; then
> /lib/ld-linux.so.2 (0x46bad000)
> libpcre.so.3 => /lib/libpcre.so.3 (0xb7856000)
>
> Are these bugs just waiting to bite, or
On Wed, Aug 11, 2010 at 09:15:49PM +0200, Christoph Anton Mitterer wrote:
> >
> > /var/my_super_duper_database
> >
> > and keep the data there? I do not actually intend to do so, but
> > shouldn't this be fixed somewhere in the policy. FHS[1] is not
> > giving any explicite advise here and
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: autopack
Version: 1.3.2
Upstream Author: Raymond Loy
URL: http://www.mcs.anl.gov/research/projects/autopack/
License: Free software
Description:
Autopack is a mes
Hi,
On Wed, 11.08.2010 at 17:48:09 +0300, Eugene V. Lyubimkin
wrote:
> Toni Mueller wrote:
> > in debian/control, like eg.
> > Bugs-To: some...@debian.org, ...
> This is the info which IMHO belongs to PTS and should stay there.
after rethinking the issue, I agree that it's better to not add a
Package: wnpp
Severity: wishlist
Owner: Matthew Gallagher
* Package name: turtleart
Version : 93+git20100803.9bee2c4
Upstream Author : Walter Bender
* URL : http://wiki.sugarlabs.org/go/Activities/Turtle_Art
* License : Expat
Programming Lang: Python
Desc
21 matches
Mail list logo