Hi,
Am Sonntag, den 08.08.2010, 02:25 -0300 schrieb Marco Túlio Gontijo e
Silva:
Excerpts from Joachim Breitner's message of Sáb Ago 07 11:34:05 -0300 2010:
(...)
looks like there went something more wrong with the git archive.
Attached is the diff between the sources as uploaded to the
Hello Peter,
I intended to have mozplugger 1.14.1 in Debian squeeze so I asked for
the permission to upload it (squeeze is frozen now).
Adam Barratt, a release manager, moved an objection which sounds
reasonable to me:
On Sat, Aug 7, 2010 at 6:38 PM, Adam D. Barratt
a...@adam-barratt.org.uk
Hi!
I've also expected the freeze to come later in August, and sadly didn't
prioritize uploading the new inetutils upstream release. So I'd like
to request approval to do so now, given the (previous and) following
arguments.
We currently have 1.6 in the archive and the biggest difference
On Sat, 07 Aug 2010 at 13:32:43 -0400, Adam D. Barratt wrote:
On Sat, August 7, 2010 12:50, Simon McVittie wrote:
Preferred: fix 0.8.5 and let it migrate
Please go ahead, and ping us once uploaded.
Uploaded, thanks. No changes since the diff I sent, other than `dch -r` and
medium urgency.
Hi there,
On Saturday 07 August 2010 20:12:27 David Martínez Moreno wrote:
I agree with Philip, that's the fastest way to proceed. I've already
filed bugs for both packages.
I think we can fix the problems later, but right now I agree with Manuel
that the kfreebsd and hppa are
Hi!
Please consider adding a freeze exception for logcheck 1.3.12[1]. I
haven't uploaded it yet as I'm waiting for a response to another
bugreport related to this issue (changing only one rule, actually,
#563348), but I want to get this addressed as soon as possible.
The request is
Hi,
please find attached a patch that fixes #592227. Upstream notified me
about a new upstream version which fixes #592227 but adds some other
changes. Therefore, I just backported the fix for the issue at hand.
If it's OK, I will upload the attached change to unstable (with no other
changes) as
Hi,
I would like to ask for a freeze exception for mercurial/1.6.2-1
Mercurial is a relatively important package. Currently, mercurial/1.6-2
is in unstable. It is not yet in testing due to #586907
mercurial/1.6.2-1 is a new upstream release. However, 1.6.X upstream
releases are only bugfix
Processing commands for cont...@bugs.debian.org:
retitle 592228 unblock: software-center/2.0.7debian3
Bug #592228 [release.debian.org] unblock: software-center/2.0.7debian2
Changed Bug title to 'unblock: software-center/2.0.7debian3' from 'unblock:
software-center/2.0.7debian2'
thanks
Stopping
retitle 592228 unblock: software-center/2.0.7debian3
thanks
On So, 2010-08-08 at 09:50 -0400, Philipp Kern wrote:
On 08/08/2010 09:07 AM, Julian Andres Klode wrote:
Please unblock package software-center
software-center (2.0.7debian2) unstable; urgency=low
* debian/changelog:
* Matthias Klose:
Or does everybody see openjdk as an alibi for Debian to build things
and then use the sun-java packages from non-free?
I know folks who use it in production, admittedly with compiler
excludes to work around some C2 bugs.
For those who are interested in an openjdk-6 update
Dear release team,
as far as I can see it all packages depending on libnifti have been
built properly against the new version and are ready to go. One of the
rdeps ('fsl' in non-free), however, just received a serious bug report
regarding a package file conflict. I added the appropriate conflict
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Release Team,
I would like to appeal to your generosity (as Neil McGovern suggested
may be available towards the end of the last bits mail) to request a
freeze exemption for libtrace3.
The current package in unstable and testing (3.0.6-1) is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Hi,
please remove libclass-isa-perl/0.36-1, libpod-plainer-perl/1.02-1,
libswitch-perl/2.16-1 from testing. They should not be released with
Squeeze, see #584468, #584466 and #584467.
Your message dated Sun, 8 Aug 2010 13:32:19 -0400
with message-id 20100808173219.ga3...@radis.liafa.jussieu.fr
and subject line Re: Bug#592248: RM: libclass-isa-perl, libpod-plainer-perl,
libswitch-perl
has caused the Debian Bug report #592248,
regarding RM: libclass-isa-perl,
On Sun, Aug 8, 2010 at 13:32:43 +0100, Simon McVittie wrote:
On Sat, 07 Aug 2010 at 13:32:43 -0400, Adam D. Barratt wrote:
On Sat, August 7, 2010 12:50, Simon McVittie wrote:
Preferred: fix 0.8.5 and let it migrate
Please go ahead, and ping us once uploaded.
Uploaded, thanks. No
Your message dated Sun, 8 Aug 2010 13:41:54 -0400
with message-id 20100808174154.gc3...@radis.liafa.jussieu.fr
and subject line Re: Bug#592229: unblock: apt-listchanges/2.85.3
has caused the Debian Bug report #592229,
regarding unblock: apt-listchanges/2.85.3
to be marked as done.
This means that
Salut Vince,
On Sun, Aug 8, 2010 at 15:49:14 +0200, Vincent Danjean wrote:
mercurial/1.6.2-1 can be seen here:
deb http://perso.debian.org/~vdanjean/debian unstable main
http://moais.imag.fr/membres/vincent.danjean/deb.html#mercurial
Any chance you can send the debdiff inline, or at
Hi,
please unblock gnome-commander 1.2.8.6-2, it fixes the important bug
#530925 and the normal bug #362268.
Here is the changelog entry:
gnome-commander (1.2.8.6-2) unstable; urgency=low
* Add myself as uploader.
* Re-add python plugins support (Closes: #530925).
* Suggests on
On 0, Gerfried Fuchs rho...@deb.at wrote:
Hi!
Please consider adding a freeze exception for logcheck 1.3.12[1].
Please go ahead.
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
I admit I was caught a bit off guard by the freeze announcement (was on a small
vacation) and need some directions on how to handle the current squid3 status.
Briefly:
- testing holds 3.1.3-2, which is affected by #584223 and is actually unusable
in its default configuration (and for those
On 0, Roland Stigge sti...@antcom.de wrote:
If it's OK, I will upload the attached change to unstable (with no other
changes) as guitarix 0.10.0-2.
OK.
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
On Fri, Aug 06, 2010 at 09:19:18PM +0100, Neil McGovern wrote:
Unfortunately, it seems that we haven't been able to fit this transition
in for the squeeze release, so it looks like perl 5.12 will have to be
targetted at squeeze+1.
OK, thanks for the note and all the work you're doing for the
On Sun, Aug 8, 2010 at 20:15:22 +0200, Luigi Gangitano wrote:
Hi,
I admit I was caught a bit off guard by the freeze announcement (was on a
small vacation) and need some directions on how to handle the current squid3
status.
Briefly:
- testing holds 3.1.3-2, which is affected by
close 568307 0.17.1-1
close 585531 0.17.1-1
close 558993 0.17.1-1
thanks
Neil McGovern wrote:
I note that there are 4 bugs left that aren't fixed yet (one pending),
do you know when these are likely to be ready to transition?
#58198{5,6,7} are trivial and can be uploaded right away. If the
Il giorno 08/ago/2010, alle ore 20.35, Julien Cristau ha scritto:
How big is the diff from 3.1.5 to 3.1.6? Do you have an idea of the
regression potential?
Full list of changes at
http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID_3_1_5_1.html
On 08/08/2010 02:32 PM, Jakub Wilk wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package netifaces. The new version contains only a fix
for an RC bug (#591992).
unblock netifaces/0.5-2.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock the packages geronimo-validation-1.0-spec,
geronimo-jacc-1.1-spec, and geronimo-jpa-2.0-spec.
The uploads just add the missing pom.xml files needed by reverse
Build-Depends
Your message dated Sun, 8 Aug 2010 23:19:51 +0200
with message-id 20100808211951.gh20...@dogguy.org
and subject line Re: Bug#592279: unblock: geronimo-validation-1.0-spec/1.1-2,
geronimo-jacc-1.1-spec/1.0.1-1.1, and geronimo-jpa-2.0-spec/1.1-2
has caused the Debian Bug report #592279,
regarding
On 0, Matt Brown ma...@debian.org wrote:
Please let me know if you will grant an exception for this package?
Please go ahead and tell us when the package hits unstable.
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of
Hi,
mldonkey/3.0.3-1 has been uploaded to unstable before the announce of
the freeze, but it seems blocked nonetheless (according to the PTS).
This is a new upstream release, and has many changes... but most of them
are bugfixes. The diff from the version in testing would be meaningless
(but can
Le 08/08/2010 17:13, Stéphane Glondu a écrit :
If yes, one more query: currently, it fails to build from source [...]
I meant on kfreebsd-*.
--
Stéphane
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Howdy release team,
Please allow the ‘python-coverage’ package version 3.2-1 into Squeeze.
The existing version (2.85-1) is far behind upstream, and most users
would not find it useful any more.
More importantly, version 3.2-1 improves the package for one of the
Squeeze release goals:
On
On Sun, Aug 8, 2010 at 20:53:31 +0200, Luigi Gangitano wrote:
Full list of changes at
http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID_3_1_5_1.html
http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID_3_1_6.html
is actually a small set of changes since translation
On Sun, Aug 8, 2010 at 19:46:24 +0200, Alessio Treglia wrote:
diff --git a/debian/changelog b/debian/changelog
index 2db35dc..783ae35 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+gnome-commander (1.2.8.6-2) unstable; urgency=low
+
+ * Add myself as uploader.
+
On Sun, Aug 8, 2010 at 18:49:23 -0400, Julien Cristau wrote:
Unblocked anyway.
Actually, no. It was pointed out on #d-python that you're using an
XS-Python-Support field in debian/control which is probably not what you
want (it's not used by any other package). Please double check.
Cheers,
On Mon, Aug 9, 2010 at 08:11:12 +1000, Ben Finney wrote:
Howdy release team,
Please allow the ‘python-coverage’ package version 3.2-1 into Squeeze.
The existing version (2.85-1) is far behind upstream, and most users
would not find it useful any more.
More importantly, version 3.2-1
On 08-Aug-2010, Julien Cristau wrote:
On Mon, Aug 9, 2010 at 08:11:12 +1000, Ben Finney wrote:
Please allow the ‘python-coverage’ package version 3.2-1 into
[…]
The other changes are, I believe, non-invasive for Squeeze.
The package is in NEW. That doesn't sound non-invasive.
Thanks
Package: release.debian.org
Severity: wishlist
User: release.debian@packages.debian.org
Usertags: freeze-exception
The following is just a heads up; I have not prepared the uploads yet.
XZ Utils 5.0.0 is likely to be released some time in the next few
weeks. As the upstream maintainer
user release.debian@packages.debian.org
usertags 592300 transition
thanks
On 0, Jonathan Nieder jrnie...@gmail.com wrote:
Package: release.debian.org
Severity: wishlist
User: release.debian@packages.debian.org
Usertags: freeze-exception
This is not a freeze-exception for your
Mehdi Dogguy wrote:
This is not a freeze-exception for your package only but rather a request
to start a new transition. Let me recall that there was a transition
freeze announced a while ago. Thus, it's very unlikely that we accept this
transition for Squeeze.
Please reread my message. I
On 0, Mehdi Dogguy me...@dogguy.org wrote:
This is not a freeze-exception for your package only but rather a request
to start a new transition. Let me recall that there was a transition
freeze announced a while ago.
Hum... actually, we are even frozen, which means no new transitions.
It
user release.debian@packages.debian.org
usertags 592300 freeze-exception
thanks
Mehdi Dogguy wrote:
This is not a freeze-exception for your package only but rather a request
to start a new transition.
Sorry about my last reply; I am a little sensitive about this because of
On 0, Jonathan Nieder jrnie...@gmail.com wrote:
Please reread my message. I would like not to bump the soname, since
there is nothing to bump soname for.
Right. I'll reread the patches then. My eyes saw:
* The soname of liblzma (upstream, at least) will be liblzma.so.5.
and my disk
Mehdi Dogguy wrote:
My eyes saw:
* The soname of liblzma (upstream, at least) will be liblzma.so.5.
and my disk said liblzma.so.2. They started to fight each other and I had
to answer quickly.
Quite understandable. This must be the least pleasant part of working on
the release team. :(
45 matches
Mail list logo
