Hi,
Le 09/09/10 21:40, Andreas Tille a écrit :
> On Thu, Sep 09, 2010 at 04:11:50PM +0200, Thibaut Paumard wrote:
>> And please, make all possible effort to warn your users about the
>> potential risk of using or having used the buggy version. And even if
>> it's only "I'm not sure, but it may wel
I wanted to let you know...that the laws of physics are on your
side...and that knowing this...I am giving you a gift. Time, is a factor
in writing code...that one day will keep up with the speed of light. A
dot time dot is the result.
The time between dots can vary...and even mean a lot more w
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 512 (new: 11)
Total number of packages offered up for adoption: 130 (new: 2)
Total number of packages reques
On 2010-09-09, Thomas Goirand wrote:
> Also, I have found that Pidgin would really have been a valid candidate
> for volatile: after few months, Yahoo, MSN and other networks are
> changing, and it becomes simply impossible to log into these networks
> unless you upgrade Pidgin (or some of its pro
On Thu, Sep 09, 2010 at 04:11:50PM +0200, Thibaut Paumard wrote:
> And please, make all possible effort to warn your users about the
> potential risk of using or having used the buggy version. And even if
> it's only "I'm not sure, but it may well be serious enough to KILL
> PEOPLE", bloody hell, w
On 09/09/2010 08:38 PM, Andreas Tille wrote:
> On Thu, Sep 09, 2010 at 04:43:53PM +0200, Mehdi Dogguy wrote:
>> Right. I was wondering why Andreas didn't contact the Release Team
>> to have our opinion on the subject. IMO, it qualifies as an RC bug
>> and the diff (0.7.8 ??? 0.7.9) doesn't look h
On Thu, Sep 09, 2010 at 06:35:03PM +0200, Salvatore Bonaccorso wrote:
> Did you had also sudo in the update? If yes, see the NEWS file, there
> was a change regarding the handling of $HOME and $MAIL. See:
>
> http://packages.qa.debian.org/s/sudo/news/20100908T204747Z.html
>
> Does this helps?
Un
On Thu, Sep 09, 2010 at 04:43:53PM +0200, Mehdi Dogguy wrote:
> Right. I was wondering why Andreas didn't contact the Release Team to have
> our opinion on the subject. IMO, it qualifies as an RC bug and the
> diff (0.7.8 ??? 0.7.9) doesn't look huge. It's even reasonable and acceptable,
> once doc
Hi there,
Jon Dowland wrote:
> Are you the upstream author? Are Thomas Goirand and Billy Zhe-Wei
> Lin the same person?
I was at the "Hacking Thursday" of the "Shanghai Linux User Group", and
I was trying to show "Billy Zhe-Wei", a Taiwanese living in Shanghai,
how he could package his applicatio
Stefano Zacchiroli wrote:
> PS regarding the other part of this thread about how to support, via
>backports, what I would call "rapidly evolving end-user apps", it is
>surely a worthwhile discussion, more general than Chromium. I believe
>it would be worth to have it elsewhere (e.g. -de
On Thu, Sep 09, 2010 at 06:18:56PM +0200, Joerg Jaspert wrote:
> On 12233 March 1977, Andreas Tille wrote:
> > I intended to upload this package to experimental, but just forgot to
> > change the target distribution. Is there any other chance to change
> > this rather than uploading a
>
> >gn
Hi Christoph
On Thu, Sep 09, 2010 at 06:24:36PM +0200, Christoph Goehre wrote:
> since the last update run in my sid cowbuilder, ccache didn't work fine.
> So, how to debug? I just print out the $PATH and $CCACHE_DIR vars with
> debian/rules and I wounder. It looks like this:
>
> sid cowbuilder:
Package: wnpp
Severity: wishlist
Owner: Oscar Morante
* Package name: ase
Version : 0.8.1-beta
Upstream Author : David Capello
* URL : http://www.aseprite.org/
* License : GPL
Programming Lang: C++
Description : Allegro Sprite Editor
ASE (Allegro Spri
Hi,
since the last update run in my sid cowbuilder, ccache didn't work fine.
So, how to debug? I just print out the $PATH and $CCACHE_DIR vars with
debian/rules and I wounder. It looks like this:
sid cowbuilder:
PATH is: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
CCACHE
On 12233 March 1977, Andreas Tille wrote:
> - Forwarded message from Andreas Tille -
> From: Andreas Tille
> To: debian-devel-chan...@lists.debian.org
> Date: Thu, 09 Sep 2010 07:32:12 +
> Subject: Accepted gnumed-client 0.8.1-1 (source all)
> gnumed-client (0.8.1-1) unstable; urgen
On 09/09/2010 16:11, Thibaut Paumard wrote:
>
> You have a bug that could potentially kill people? Fix it, upload ASAP
> and contact the security and release teams. And I don't care if it's
> not the "normal procedure" and if it can piss off people, it's not
> nearly as important as Doing What
Long Description:
Woof (Web Offer One File) is a tool to copy files between hosts. It can
serve a specified file on HTTP,just for a given number of times, and then
shutdown. It can be easily used to share files across the computers on a
net, and given that the other ends should have just a b
Hi guys,
This thread is just surrealistic.
Le 09/09/10 15:17, Andreas Tille a écrit :
> On Thu, Sep 09, 2010 at 10:34:09PM +1000, Ben Finney wrote:
>> >From your description, I'd guess one of ???causes serious data loss??? (???
>> ???critical???)
>
> Strictly speaking I do not really regard the
serious -- "in the package maintainer's or release manager's opinion, makes the
package unsuitable for release."
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201009
> From: Thomas Goirand
...
> Upstream Author : Billy Zhe-Wei Lin, 林哲瑋 (billy3321, 雨蒼)
>
Are you the upstream author? Are Thomas Goirand and Billy Zhe-Wei Lin the same
person?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
On Thu, Sep 09, 2010 at 08:42:39PM +0800, Thomas Goirand wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Billy Zhe-Wei Lin 林哲瑋
>
> * Package name: lazyscripts
> Version : 0.2.3.7
> Upstream Author : Billy Zhe-Wei Lin, 林哲瑋 (billy3321, 雨蒼)
>
> * URL : http://www.l
Hi,
On Donnerstag, 9. September 2010, Thomas Goirand wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Billy Zhe-Wei Lin 林哲瑋
>
> * Package name: lazyscripts
> Version : 0.2.3.7
> Upstream Author : Billy Zhe-Wei Lin, 林哲瑋 (billy3321, 雨蒼)
> * URL : http://www.lazyscri
On Thu Sep 09 14:42, Tshepang Lekhonkhobe wrote:
> > Rather than RC (which is only about whether the severity of the bug is
> > sufficient to delay the release of Debian), what is the severity of the
> > bug?
>
> AFAIK, this is not the sort of package that would delay Debian's
> release. At worst
On Thu, Sep 09, 2010 at 10:34:09PM +1000, Ben Finney wrote:
> >From your description, I'd guess one of ???causes serious data loss??? (???
> ???critical???)
Strictly speaking I do not really regard the problem in #596219 as a
data loss - the available data are just not properly handled which can
Package: wnpp
Severity: wishlist
Owner: Billy Zhe-Wei Lin 林哲瑋
* Package name: lazyscripts
Version : 0.2.3.7
Upstream Author : Billy Zhe-Wei Lin, 林哲瑋 (billy3321, 雨蒼)
* URL : http://www.lazyscripts.org
* License : GPL-2
Programming Lang: Python, bash
Descrip
On Thu, Sep 9, 2010 at 14:34, Ben Finney wrote:
> Andreas Tille writes:
>
>> with GNUmed we currently have a case where a bug is not RC regarding
>> the computer system and would not match our criterion of RC bugs.
>
> Rather than RC (which is only about whether the severity of the bug is
> suffi
Andreas Tille writes:
> with GNUmed we currently have a case where a bug is not RC regarding
> the computer system and would not match our criterion of RC bugs.
Rather than RC (which is only about whether the severity of the bug is
sufficient to delay the release of Debian), what is the severity
* Karsten Hilbert [2010-09-09 13:07 +0200]:
> Filed a bug:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596219
>
> but reportbug did not let me specify either of RC / critical
> / grave / serious / security ...
I just set this to serious. It may take some minutes until the BTS is
up
On Wed, Sep 08, 2010 at 04:58:21PM -0400, Joey Hess wrote:
> Incoming code of possible security significance should be reviewed for
> at least common classes of security holes. Instead, we get a thread where
> the ITPer is required to prove that nothing in Debian can do what his
> package does.
Yo
On Thu, Sep 09, 2010 at 12:38:05PM +0200, Michael Tautschnig wrote:
> > Here comes the bug: GNUmed will, given appropriate
> > circumstances, OVERWRITE the first allergy against Sugar.
...
> > You die in hospital because of a second anaphylactic
> > reaction to Sugar.
> [...]
>
> Altho
On 2010-09-09 11:35 +0200, Andreas Tille wrote:
> - Forwarded message from Andreas Tille -
>
> From: Andreas Tille
> To: debian-devel-chan...@lists.debian.org
> Date: Thu, 09 Sep 2010 07:32:12 +
> Subject: Accepted gnumed-client 0.8.1-1 (source all)
>
> gnumed-client (0.8.1-1) unsta
On 09.09.2010 11:58, gregor herrmann wrote:
On Thu, 09 Sep 2010 11:40:49 +0200, Andreas Tille wrote:
with GNUmed we currently have a case where a bug is not RC regarding the
computer system and would not match our criterion of RC bugs. However,
the influence of this bug might harm the health o
On Thu Sep 09 12:03, Karsten Hilbert wrote:
> Here comes the bug: GNUmed will, given appropriate
> circumstances, OVERWRITE the first allergy against Sugar.
Sounds like "grave: , or causes data loss, ..." to me, which is RC.
I was also going to suggest it could be considered a sec
[...]
>
> Here comes the bug: GNUmed will, given appropriate
> circumstances, OVERWRITE the first allergy against Sugar.
>
> Three years later, Debian 10 has been released and you
> return because of FatigueFromPackaging.
>
> I prescribe Sugar, which usually helps against
> FatigueF
On Thu, Sep 9, 2010 at 11:58, gregor herrmann wrote:
> On Thu, 09 Sep 2010 11:40:49 +0200, Andreas Tille wrote:
>
>> with GNUmed we currently have a case where a bug is not RC regarding the
>> computer system and would not match our criterion of RC bugs. However,
>> the influence of this bug migh
I have been looking into the packaging of bundles - that is packages
that have multiple upstream sources. There was recently an article on
the subject:
http://raphaelhertzog.com/2010/09/07/how-to-use-multiple-upstream-tarballs-in-debian-source-packages/
.
However one must notice this quote:
"T
On Thu, Sep 09, 2010 at 11:40:49AM +0200, Andreas Tille wrote:
> with GNUmed we currently have a case where a bug is not RC regarding the
> computer system and would not match our criterion of RC bugs. However,
> the influence of this bug might harm the health of patients of the
> doctor who migh
On Thu, 09 Sep 2010 11:40:49 +0200, Andreas Tille wrote:
> with GNUmed we currently have a case where a bug is not RC regarding the
> computer system and would not match our criterion of RC bugs. However,
> the influence of this bug might harm the health of patients of the
> doctor who might use
On Thu, Sep 09, 2010 at 11:54:31AM +0200, Adam Borowski wrote:
> On Thu, Sep 09, 2010 at 11:35:16AM +0200, Andreas Tille wrote:
> > I intended to upload this package to experimental, but just forgot to
> > change the target distribution. Is there any other chance to change
> > this rather than upl
On Thu, Sep 09, 2010 at 11:35:16AM +0200, Andreas Tille wrote:
> I intended to upload this package to experimental, but just forgot to
> change the target distribution. Is there any other chance to change
> this rather than uploading a
>
>gnumed-client (1:0.7.9-1) unstable;
>gnumed-client
Hi,
with GNUmed we currently have a case where a bug is not RC regarding the
computer system and would not match our criterion of RC bugs. However,
the influence of this bug might harm the health of patients of the
doctor who might use this version of GNUmed.
If needed upstream will give some mo
Hi,
- Forwarded message from Andreas Tille -
From: Andreas Tille
To: debian-devel-chan...@lists.debian.org
Date: Thu, 09 Sep 2010 07:32:12 +
Subject: Accepted gnumed-client 0.8.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
gnumed-client (0.8.1-1) unstable; urgenc
Rene Engelhard schrieb am Thursday, den 09. September 2010:
> On Wed, Sep 08, 2010 at 01:22:24PM -0700, Don Armstrong wrote:
> > 1: It's certainly a bug in the backported package using debhelper
> > improperly; it may also be an additional wishlist bug in debhelper.
>
> I disagree, the backported
On Wed, Sep 08, 2010 at 01:22:24PM -0700, Don Armstrong wrote:
> 1: It's certainly a bug in the backported package using debhelper
> improperly; it may also be an additional wishlist bug in debhelper.
I disagree, the backported package uses debhelper correctly. Especially
if you don't use the back
44 matches
Mail list logo
