Your message dated Fri, 04 Jul 2014 06:03:35 +
with message-id e1x2wat-0004bn...@franck.debian.org
and subject line Bug#753476: fixed in blt 2.5.3-1
has caused the Debian Bug report #753476,
regarding blt: new build against Tcl/Tk 8.6 crashes
to be marked as done.
This means that you claim
Se désinscrire de la liste:
http://link.email.wib.me/u/443/16bc80c6f0cbda97cb6600ee8b86f7fec1117f11875b2e4b
Avenue Abdelmoumen, Rue Calavon n 4, Casablanca, 2, Maroc
Se désinscrire de la liste:
http://link.email.wib.me/u/443/16bc80c6f0cbda97e29273455989cc9ac1117f11875b2e4b
Avenue Abdelmoumen, Rue Calavon n 4, Casablanca, 2, Maroc
Package: dnet-common
Version: 2.63
Severity: normal
Usertags: iproute-removal
Dear Maintainer,
The iproute package is now a transitional package to iproute2.
It will soon be removed.
Please update your suggests to iproute2.
-- System Information:
Debian Release: jessie/sid
APT prefers
Processing control commands:
severity -1 grave
Bug #740574 [libtirpc1] libtirpc1: Causes statd from the nfs-common package to
fail
Severity set to 'grave' from 'important'
found -1 0.2.3-1
Bug #740574 [libtirpc1] libtirpc1: Causes statd from the nfs-common package to
fail
Marked as found in
Control: severity -1 grave
Control: found -1 0.2.3-1
Hi,
I still experience the NFS failure (bug #740574) after upgrading to
libtirpc1/0.2.3-1:
[UPGRADE] libc6:amd64 2.19-1 - 2.19-4
[UPGRADE] libc6:i386 2.19-1 - 2.19-4
[UPGRADE] libc6-i386:amd64 2.19-1 - 2.19-4
[UPGRADE] libc6-i686:i386 2.19-1
vlock_2.2.2-4_amd64.changes uploaded successfully to localhost
along with the files:
vlock_2.2.2-4_amd64.deb
vlock_2.2.2-4.dsc
vlock_2.2.2-4.diff.gz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
--
To UNSUBSCRIBE, email to
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 04 Jul 2014 19:38:25 +0200
Source: vlock
Binary: vlock
Architecture: source amd64
Version: 2.2.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Helmut
libtirpc_0.2.3-2_amd64.changes uploaded successfully to localhost
along with the files:
libtirpc-dev_0.2.3-2_amd64.deb
libtirpc1_0.2.3-2_amd64.deb
libtirpc_0.2.3-2.dsc
libtirpc_0.2.3-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
--
To
Your message dated Fri, 04 Jul 2014 21:35:09 +
with message-id e1x3b8p-jm...@franck.debian.org
and subject line Bug#740574: fixed in libtirpc 0.2.3-2
has caused the Debian Bug report #740574,
regarding libtirpc1: Causes statd from the nfs-common package to fail
to be marked as done.
This
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 04 Jul 2014 23:13:14 +0200
Source: libtirpc
Binary: libtirpc-dev libtirpc1
Architecture: source amd64
Version: 0.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Package: tracker.debian.org
Severity: normal
Up to now, we have been using the following Trello board:
https://trello.com/b/faDgzjwO/pts-rewrite
We should scan all the cards there and file corresponding bugs in the BTS
when there's still something actionable and/or interesting to consider.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello List !
I am maintaining the tth Debian package [1].
A couple of weeks ago, the upstream source tarball was updated at SourceForge.
But, unfortunately, the update was not reflected in the last `checked at' field
and via uscan: any idea ?
Best
Hello,
I have just setup tracker.debian.org. It aims to replace
packages.qa.debian.org but I need your help to achieve this goal and
maintain it in the long term.
I would like to see a few people get familiar with this new code base
so that we have a real maintenance team (i.e. not only me). In
Package: tracker.debian.org
Severity: normal
Dear maintainer,
thanks for the new package tracker. ;)
Looking at [1] I find it strange, that it says:
'1 bug tagged help in the BTS'
While at the same time there is no open bug and indeed clicking on the
'1 bug' link leads to [2] without a bug.
On 4 July 2014 12:27, Raphael Hertzog hert...@debian.org wrote:
Hello,
I have just setup tracker.debian.org. It aims to replace
packages.qa.debian.org but I need your help to achieve this goal and
maintain it in the long term.
I would like to see a few people get familiar with this new code
Hi,
On Fri, 04 Jul 2014, Arturo Borrero Gonzalez wrote:
I would suggest to add a link in each developer QAs page, and in
packages.d.o as well.
This may sound a bit redundant with the PTS, but you (the tracker)
will get more visibility and others may want to collaborate.
What about just
On 4 July 2014 14:34, Raphael Hertzog hert...@debian.org wrote:
Hi,
On Fri, 04 Jul 2014, Arturo Borrero Gonzalez wrote:
I would suggest to add a link in each developer QAs page, and in
packages.d.o as well.
This may sound a bit redundant with the PTS, but you (the tracker)
will get more
On Fri, Jul 04, 2014 at 02:34:58PM +0200, Raphael Hertzog wrote:
What about just updating those links everywhere to point to the new
package tracker?
Do people feel that it's too early for this?
IMHO, the right way to go about this is having a grace period during
which both services are
On Fri, Jul 4, 2014 at 8:34 PM, Raphael Hertzog wrote:
Do people feel that it's too early for this?
I think it is too early for this, at minimum we need to audit the
templates for the old and new codebases to make sure there are at
least bugs filed for each missing/unsynchronised feature.
--
Package: tracker.debian.org
Severity: normal
I'm glad to see the new tracker picking up steam. One thing I'm missing
right now is a warning about autoremovals from testing.
Thanks!
-- System Information:
Debian Release: jessie/sid
APT prefers trusty-updates
APT policy: (500,
On Fri, Jul 04, 2014 at 12:27:00PM +0200, Raphael Hertzog wrote:
I have just setup tracker.debian.org. It aims to replace
packages.qa.debian.org but I need your help to achieve this goal and
maintain it in the long term.
I would like to see a few people get familiar with this new code base
22 matches
Mail list logo
