Bug#627221: pu: package nagios-plugins/1.4.15-3squeeze1
Hi Adam, On Saturday, 21. May 2011, Adam D. Barratt wrote: > Thanks for working on fixing this in stable; please go ahead with the > upload. I uploaded the fixed package last night. Thanks and with kind regards, Jan. -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part.
NEW changes in proposedupdates
Processing changes file: nagios-plugins_1.4.15-3squeeze1_i386.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qokk0-00027s...@franck.debian.org
Bug#626895: marked as done (pu: package samba/2:3..6~dfsg-3squeeze4)
Your message dated Sun, 22 May 2011 21:29:51 +0100
with message-id <1306096191.3491.12250.ca...@hathi.jungle.funky-badger.org>
and subject line Re: Bug#626895: pu: package samba/2:3..6~dfsg-3squeeze4
has caused the Debian Bug report #626895,
regarding pu: package samba/2:3..6~dfsg-3squeeze4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
626895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
Hello release team,
Here's another samba bug for which I would like to cherrypick the
upstream fix.
In #605728, it is reported fail to copy files to an SMB share using
signed SMB. This breaks Gnome desktop copying which is, IMHO,
important enough to deserve being fixed in squeeze.
I attach the relevant upstream commit to this request. Please
consider allowing this into s-p-u.
-- System Information:
Debian Release: wheezy/sid
Architecture: i386 (i686)
Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
commit 0afb2995a2177afa2eb7b8f99887a39cdaf23a15
Author: Jeremy Allison
Date: Wed Nov 10 17:59:05 2010 -0800
Fix bug #7791 - gvfsd-smb (Gnome vfs) fails to copy files from a SMB share
using SMB signing.
The underlying problem is that the old code invoked by cli_write()
increments
cli->mid directly when issuing outstanding writes. This should now be done
only
in libsmb/clientgen.c to make metze's new signing engine works correctly.
Just
deleting this code fixes the problem.
Jeremy.
Autobuild-User: Jeremy Allison
Autobuild-Date: Thu Nov 11 02:50:08 UTC 2010 on sn-devel-104
diff --git a/source3/libsmb/clireadwrite.c b/source3/libsmb/clireadwrite.c
index 370c068..cd95b17 100644
--- a/source3/libsmb/clireadwrite.c
+++ b/source3/libsmb/clireadwrite.c
@@ -703,8 +703,7 @@ static bool cli_issue_write(struct cli_state *cli,
off_t offset,
uint16 mode,
const char *buf,
- size_t size,
- int i)
+ size_t size)
{
char *p;
bool large_writex = false;
@@ -778,8 +777,6 @@ static bool cli_issue_write(struct cli_state *cli,
cli_setup_bcc(cli, p+size);
}
- SSVAL(cli->outbuf,smb_mid,cli->mid + i);
-
show_msg(cli->outbuf);
if (direct_writes) {
/* For direct writes we now need to write the data
@@ -828,7 +825,7 @@ ssize_t cli_write(struct cli_state *cli,
if (!cli_issue_write(cli, fnum, offset + bsent,
write_mode,
buf + bsent,
- size1, issued))
+ size1))
return -1;
issued++;
}
--- End Message ---
--- Begin Message ---
tag 626895 - confirmed
thanks
On Sun, 2011-05-22 at 19:28 +0200, Christian PERRIER wrote:
[...]
> > On Mon, 2011-05-16 at 09:51 +0200, Christian Perrier wrote:
> > > Here's another samba bug for which I would like to cherrypick the
> > > upstream fix.
> > >
> > > In #605728, it is reported fail to copy files to an SMB share using
> > > signed SMB. This breaks Gnome desktop copying which is, IMHO,
> > > important enough to deserve being fixed in squeeze.
[...]
> Doh, this fix is already in samba..:-)
>
> I was tricked by the fact that I made a mistake in 2:3.5.6~dfsg-2 and
> closed #605729 instead of 605728
>
> p-u upload no longer needed, then.
Thanks for letting us know. In that case, let's close the bug.
Regards,
Adam
--- End Message ---
Processed: Re: Bug#626895: pu: package samba/2:3..6~dfsg-3squeeze4
Processing commands for cont...@bugs.debian.org: > tag 626895 - confirmed Bug #626895 [release.debian.org] pu: package samba/2:3..6~dfsg-3squeeze4 Removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 626895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130609619926670.transcr...@bugs.debian.org
updating monkeysphere in stable
Hello again,
The monkeysphere package in stable suffers from an issue that makes key
revocation problematic (#607596). Fortunately, the fix is simply a two
line change to fix typos.
I would like to propose that monkeysphere be updated in a stable point
release to resolve this issue. The change has been in the monkeysphere
package for some time, long enough to now be available in wheezy as well
as backports, providing sufficient testing.
The diff below shows the change being proposed, and if the release team
approves, I can upload it to stable.
thanks!
micah
From 7e5d57f1a2cb5a05428ffca6701dc01bf7c7aeaf Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Sun, 19 Dec 2010 22:06:13 -0500
Subject: [PATCH 1/2] fix monkeysphere-host revoke-key (Closes: #607596)
---
debian/changelog |6 ++
debian/patches/607596.diff | 33 +
debian/patches/series |1 +
3 files changed, 40 insertions(+), 0 deletions(-)
create mode 100644 debian/patches/607596.diff
diff --git a/debian/changelog b/debian/changelog
index b03dff7..f150c68 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+monkeysphere (0.31-4) unstable; urgency=low
+
+ * fix monkeysphere-host revoke-key (Closes: #607596)
+
+ -- Daniel Kahn Gillmor Sun, 19 Dec 2010 22:04:03
-0500
+
monkeysphere (0.31-3) unstable; urgency=high
* avoid mis-escaping uids, fixes a security issue. (Closes: #600304)
diff --git a/debian/patches/607596.diff b/debian/patches/607596.diff
new file mode 100644
index 000..d2c525c
--- /dev/null
+++ b/debian/patches/607596.diff
@@ -0,0 +1,33 @@
+commit d37829e6c2dfdcac912a9d6e9203e62343f3dd01
+Author: Micah Anderson
+Date: Fri Oct 1 10:07:46 2010 -0400
+
+fix revoke_key typo in creating temporary directory
+fix variable specifying which key to revoke
+
+monkeysphere-host revoke-key would produce the following errors,
this
+commit fixes that:
+
+Really publish this cert to zimmermann.mayfirst.org ? (Y/n) y
+/usr/share/monkeysphere/mh/revoke_key: line 96: mkmstempdir: command not
found
+gpg: new configuration file `/root/.gnupg/gpg.conf' created
+gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during
this run
+gpg: "0x!" not a key ID: skipping
+
+diff --git a/src/share/mh/revoke_key b/src/share/mh/revoke_key
+index 5a013e0..9077e4c 100644
+--- a/src/share/mh/revoke_key
b/src/share/mh/revoke_key
+@@ -93,10 +93,10 @@ y
+ if [ "${really/n/N}" = 'N' ] ; then
+ printf "Not publishing.\n" >&2
+ else
+- local newhome=$(mkmstempdir)
++ local newhome=$(msmktempdir)
+ GNUPGHOME="$newhome" gpg --no-tty --quiet --import <
"$HOST_KEY_FILE"
+ GNUPGHOME="$newhome" gpg --no-tty --quiet --import <<< "$revcert"
+- GNUPGHOME="$newhome" gpg --keyserver "$KEYSERVER" --send
"0x${HOST_FINGERPRINT}!"
++ GNUPGHOME="$newhome" gpg --keyserver "$KEYSERVER" --send
"0x${keyID}!"
+ rm -rf "$newhome"
+ fi
+ fi
diff --git a/debian/patches/series b/debian/patches/series
index af8e9c7..6a5bbad 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
591118.diff
600304.diff
+607596.diff
--
1.7.5.1
From 83934a8cc953b7eee9145b212019032624abbf2d Mon Sep 17 00:00:00 2001
From: Micah Anderson
Date: Sun, 22 May 2011 16:12:20 -0400
Subject: [PATCH 2/2] switch suite from unstable to stable for proposed point
release update
---
debian/changelog |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index f150c68..7ee4de9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-monkeysphere (0.31-4) unstable; urgency=low
+monkeysphere (0.31-4) stable; urgency=low
* fix monkeysphere-host revoke-key (Closes: #607596)
--
1.7.5.1
--
pgpvi2ofXTOOb.pgp
Description: PGP signature
Re: Update puppet in stable
Hi,
Back in March, before the previous stable point release update, I had
written to debian-release about an annoying issue that came up with the
puppet package since the release. that was #573551 which has to do with
dependency-based boot scripts and how puppet enables/disables
services. In squeeze, it simply doesn't work correctly with puppet.
The fix that was proposed was flawed, so we backed out of that update
and pushed this around in the puppet team and upstream until a better
fix was found that actually addresses the issue properly. That fix has
been incorporated in the release that has gone through sid->wheezy and
is also in the version in backports, so it has had fairly decent testing
and seems to solve the issue.
So, now it would be good to get that into stable, so please find below
the diff, and if the release team approves, I can upload it to stable:
From 3e25618399f3993046e5170c6081ba33628d318f Mon Sep 17 00:00:00 2001
From: Max Martin
Date: Tue, 22 Mar 2011 16:54:53 -0700
Subject: [PATCH 1/2] (#5908) Add support for new update-rc.d disable API
Added support for the new disable API to update-rc.d and
added spec tests to check this functionality. This change was made
because in versions of sysv-rc >= 2.88, 'update-rc.d stop' is broken and
actually enables the service.
We only changed the disable case as the enable case still works on
systems which use sysv-rc 2.88 or greater (atm, only Debian Lenny). We
wanted to change as little as possible because update-rc.d prints a
message stating that the new enable/disable API is unstable and may
change in the future.
Paired-with:Matt Robinson, Jacob Helwig
---
lib/puppet/provider/service/debian.rb |8 ++--
spec/unit/provider/service/debian_spec.rb | 16 ++--
2 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/lib/puppet/provider/service/debian.rb
b/lib/puppet/provider/service/debian.rb
index 3d09e28..58b808a 100755
--- a/lib/puppet/provider/service/debian.rb
+++ b/lib/puppet/provider/service/debian.rb
@@ -22,8 +22,12 @@ Puppet::Type.type(:service).provide :debian, :parent =>
:init do
# Remove the symlinks
def disable
-update_rc "-f", @resource[:name], "remove"
-update_rc @resource[:name], "stop", "00", "1", "2", "3", "4", "5", "6", "."
+if `dpkg --compare-versions $(dpkg-query -W --showformat '${Version}'
sysv-rc) ge 2.88 ; echo $?`.to_i == 0
+ update_rc @resource[:name], "disable"
+else
+ update_rc "-f", @resource[:name], "remove"
+ update_rc @resource[:name], "stop", "00", "1", "2", "3", "4", "5", "6",
"."
+end
end
def enabled?
diff --git a/spec/unit/provider/service/debian_spec.rb
b/spec/unit/provider/service/debian_spec.rb
index 8dee2ee..440d449 100755
--- a/spec/unit/provider/service/debian_spec.rb
+++ b/spec/unit/provider/service/debian_spec.rb
@@ -52,8 +52,20 @@ describe provider_class do
end
describe "when disabling" do
-it "should call update-rc.d twice" do
- @provider.expects(:update_rc).twice
+it "should be able to disable services with newer sysv-rc versions" do
+ @provider.stubs(:`).with("dpkg --compare-versions $(dpkg-query -W
--showformat '${Version}' sysv-rc) ge 2.88 ; echo $?").returns "0"
+
+ @provider.expects(:update_rc).with(@resource[:name], "disable")
+
+ @provider.disable
+end
+
+it "should be able to enable services with older sysv-rc versions" do
+ @provider.stubs(:`).with("dpkg --compare-versions $(dpkg-query -W
--showformat '${Version}' sysv-rc) ge 2.88 ; echo $?").returns "1"
+
+ @provider.expects(:update_rc).with("-f", @resource[:name], "remove")
+ @provider.expects(:update_rc).with(@resource[:name], "stop", "00", "1",
"2", "3", "4", "5", "6", ".")
+
@provider.disable
end
end
--
1.7.5.1
From ea3f085953cb981803bfb971cadf286927e7a100 Mon Sep 17 00:00:00 2001
From: Micah Anderson
Date: Sun, 22 May 2011 15:50:07 -0400
Subject: [PATCH 2/2] update changelog to reflect fix for 573551
---
debian/changelog |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 56f05f7..fd4aab5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+puppet (2.6.2-5) stable; urgency=low
+
+ [ Micah Anderson ]
+ * Fix puppet service provider to properly use update-rc.d disable API,
+(Closes: #573551)
+
+ -- Micah Anderson Sun, 22 May 2011 15:49:13 -0400
+
puppet (2.6.2-4) unstable; urgency=low
* Normalize parameterized classes (Closes: #607294)
--
1.7.5.1
pgpaUqTS12iJ9.pgp
Description: PGP signature
Bug#626895: pu: package samba/2:3..6~dfsg-3squeeze4
On Mon, May 16, 2011 at 09:35:54PM +0100, Adam D. Barratt wrote: > Hi, > > On Mon, 2011-05-16 at 09:51 +0200, Christian Perrier wrote: > > Here's another samba bug for which I would like to cherrypick the > > upstream fix. > > > > In #605728, it is reported fail to copy files to an SMB share using > > signed SMB. This breaks Gnome desktop copying which is, IMHO, > > important enough to deserve being fixed in squeeze. > > Has this already been included in a version of samba uploaded to > unstable? I assumed that it would have been, given the date of the > upstream fix, but #605728 still appears to be marked as unfixed. Doh, this fix is already in samba..:-) I was tricked by the fact that I made a mistake in 2:3.5.6~dfsg-2 and closed #605729 instead of 605728 p-u upload no longer needed, then. signature.asc Description: Digital signature
Re: Bug#626559: postgresql-8.4: pg_upgrade_fix/8.4.8 needed for stable/squeeze
Hello Ivan, hello release team, Ivan Kohler [2011-05-12 15:49 -0700]: > Package: postgresql-8.4 > Version: 8.4.7-0squeeze2 > Severity: critical > Tags: squeeze > Justification: causes serious data loss > > http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix As Debian primarily uses pg_upgradecluster it wasn't that urgent, but I do realize that people on squeeze want to play around with upgrading to 9.0 (although for that you should use 9.0's pg_upgrade). Nevertheless, the upgrade also fixes other bugs [1], and as there have not been any regression reports so far, I think it is safe to allow 8.4.8 into squeeze now. I uploaded 8.4.8-0squeeze1 to the stable queue. It passes the upstream and postgresql-common integration test suite. The only packaging diff is the changelog. I can build an upstream debdiff if you want me to, but I suppose you generate those with debdiff on queue processing anyway? Thanks, Martin [1] http://www.postgresql.org/docs/8.4/static/release-8-4-8.html -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#627576: marked as done (nmu: rpm2html_1.11.2-2)
Your message dated Sun, 22 May 2011 11:19:16 +0200 with message-id <4dd8d514.20...@dogguy.org> and subject line Re: Bug#627576: nmu: rpm2html_1.11.2-2 has caused the Debian Bug report #627576, regarding nmu: rpm2html_1.11.2-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi it looks like I've uploaded rpm2html built against rpm 4.8, can you plase rebuilt it with new one: nmu rpm2html_1.11.2-2 . amd64 . -m "Rebuilt against rpm 4.9." Thanks - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJN2KOPAAoJEGo39bHX+xdNq9MQAJAE+i92yI/moZAhkrt6Hfpw xer+bRraR8H9qY70VMPRRL3vOUYK8JD5/cpARVCs8AKxvVc2u1ivw7xDt+zvNNB/ dKQPa0GcaXHgzdH1J0iBqHfXY7l32B35CxNsySBq0gRd+pDCLnX9cF+/+eSLYZj7 c94cqdqnpGcSkYWwHD+MRlbBnDgy05GSFcAvTez7VxsBD0BvLzp5s3aFpPGT9L91 KNOz7fWpcVyPVawIAjdEl34Kvsf0CQfB716RnX7SXbYghM+JaAfcKScdfWaA+jPH EyEcwlv0TJTt4mDBxFhV6d8jHD3lEJCIHTaIx4QtFwbZx7ad3p0QWLYj85gxJ16x jW4GBj0hhJkOc6yigqfedglHnJaGmXvgFiJs3Rfd/0p+BWuBgnFW/se/v3/IIdL8 igSE9qpoBfng12xBpnKJgUbn84BnXAxwidKo5kaG15Dr3OqNqRS0OZ1cB0vJAbuX fQ7ktSDllGnFpmvRFNi8TKlfY7/7q4IwEoMNPLKmwdodD4DtLomB1RzxEyprMDSP t9/DZTmz8JcTykT09c1DYWGD1YnT6hS/fA/NS03XZDFAcGb2xLubOaDJojaiTJoj nJYnwHpcgC/yedsDGVooKp72DVnBBwx1U/NP59EBgEa5K84q2Y2RWM3P9YA+6uD6 MsQIx4xHlWf8QoSoJ2gA =4fU4 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 05/22/2011 07:48 AM, Michal Čihař wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi > > it looks like I've uploaded rpm2html built against rpm 4.8, can you > plase rebuilt it with new one: > > nmu rpm2html_1.11.2-2 . amd64 . -m "Rebuilt against rpm 4.9." > Scheduled. Kind regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ --- End Message ---
Bug#627432: marked as done (nmu: libextractor_1:0.5.23+dfsg-7)
Your message dated Sun, 22 May 2011 11:22:11 +0200 with message-id <4dd8d5c3.9050...@dogguy.org> and subject line Re: Bug#627432: nmu: libextractor_1:0.5.23+dfsg-7 has caused the Debian Bug report #627432, regarding nmu: libextractor_1:0.5.23+dfsg-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi libextractor should be built against new rpm, it seems to build fine in my test environment. So please binNMU after rpm is available on all architectures. nmu libextractor_1:0.5.23+dfsg-7 . ALL . -m "Rebuild against new rpm." - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37.6-0.5-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJN1oBMAAoJEGo39bHX+xdNcQkP+wX2znnr4VCkZpJyuHQ+ivi7 q4gWIQiFZRKfK8+KdOr9N/saWm18uI6GgeTyMCl/Q69qdk4IHKsC7QFRElW3SIsT uhoBx//VkuBqig+tgOtrCmclskwFi9i3mR906E59mBk3HDLdMtx++0eYzdkNbO7E AEcaQWQW0lkQPu33AJv7C/ZFiF5iEE5CKsVg4vS/rz3/d9MRSLWBCYwHgwzjdwFl ltkhojpgv4JW1ChmotGbFISDrbAMWgyCMreLdUgBXQUYJL609/GXh7y5RJZLYDQH AoT0K/KgdYqJ6b0NK85PTMjjy2EalkzUsEwYXAJXO/c3+vXuReBRXXfWceRTMTxj ykmXrHFirR73I6wIBu6agk+nJTzYru/Saiz+L8fgCBYEmbrY/7QIDjoEFlDgbrEf l626LJc8NfVlYEdEF6oJioEWjwOtatYZVhCnmTaiI+fGIyWdR5ewvofTBILlQK7L T3rpnffHKnZrmnj1PBp+05YaMEmlL71WMDYaRRhXbw03YqNy7Dsu60clMMyWY2ST 2dA8IFDwVXQkUnhwFw9uhcaukuZ5c84LArh0LLYBEBh3S59baBdfpSn2zHFx3rBg VfJQqguYy6rk34nKl8EbiesItzs144B7pDMQY/8mOVeG4upD+QuaZX51IAXjMvBT Zta2VFeVO52uLQni3FGs =BVf5 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 05/20/2011 04:53 PM, Michal Čihař wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi > > libextractor should be built against new rpm, it seems to build fine in > my test environment. > > So please binNMU after rpm is available on all architectures. > > nmu libextractor_1:0.5.23+dfsg-7 . ALL . -m "Rebuild against new rpm." > Scheduled. Kind regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ --- End Message ---
Re: Bits from the Release Team - Kicking off Wheezy
On Tue, Mar 29, 2011 at 10:51:02AM +0100, Neil McGovern wrote: > Sprint > -- > We feel it would be useful for the Release Team as a whole to get > together to think about what the plans are for the next release. As > such, we're planning a sprint to meet in person. Details will follow > once diaries have been able to be synchronised! > Hi all, This now has a wiki page, at http://wiki.debian.org/Sprints/2011/Release We're hoping to hold this in two weeks time in Antwerp. Comments welcome! Neil -- <+Mulligan> Your folk tale is inconsistent and confusing. <+Mulligan> I shall round up your local population and tell them good CHRISTIAN folk tales. <+Mulligan> Then build churches on all your pagan temples in order to stamp out your heathen idolatry. <@Ulthar> How about I give you the finger, and you give me my temples back? <+Mulligan> Tell me Mr Ulthar. How will you gather faith when you have no followers? * Mulligan makes a gesture and converts everyone to Christianity. <+Mulligan> Wow. I think we just summarised 800 years of history in about six sentences. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110522082049.gr...@feta.halon.org.uk
