Bug#893644: stretch-pu: package leap-archive-keyring/2016.03.08

[micah anderson]

Julien Cristau  writes:

> On Tue, Apr 03, 2018 at 01:00:41PM -0400, micah anderson wrote:
>> I went with 2017.11.24~deb9u1 because indeed, the changes since the
>> current version in stretch are appropriate for a stable update, namely:
>> 
>> 1. Providing keys in a second location, to aid in the transition from
>> jessie->stretch methods for how sources.list [signed-by=] method changed
>> to allow for both paths and fingerprints
>> 
>> 2. fix priority to be in-line with debian policy
>> 
>> 3. add a dependency on gnupg
>> 
>> 4. update the expirations on the keys themselves
>> 
>> I'm only unsure if changing the Priority section is allowed in a stable
>> point update?
>> 
> It's a no-op.  Priority and Section in the package are meaningless.
>
> I'm curious about 3 though, no explanation seems to be provided.

Indeed, I believe this could be a Recommends (like
debian-keyring). Would you like me to change that?

-- 
micah

Bug#893644: Dependency on gnupg

[micah anderson]

Actually, I was wrong in my previous message. The package
`leap-archive-keyring` Depends on gnupg because its .postinst has a
clean-up process from a previous package (2016.03.03) that removes keys
from the old /etc/apt/trusted.gpg.

In order to do that clean-up, gpg is necessary, thus the Depends.

-- 
micah

Bug#925164: RM: deltachat-core/0.39.0-1+ds2

[micah anderson]

Control tags -1 - moreinfo

Hi,

Niels Thykier  writes:

> I am adding the Debian maintainer of Delta Chat in Debian as:
>
>  * I do not know anything about Delta Chat nor its situation outside of
>Debian.  In Debian, it has zero bugs.

Indeed, the upstream Delta Chat authors have requested that it not be
put into stable, as too much is changing at the moment.

>  * I am not sure if the Debian maintainer has been informed of the
>situation (I got not easily way of knowing except asking).

Yes, I am aware, and glad that this was done.

Andre is listed as DM for this package, so I thought that it would not
be necessary to check this.

> @micah: Can you please comment on this and remove the moreinfo tag when
> you have done so.

done.

-- 
micah

Bug#893644: stretch-pu: package leap-archive-keyring/2016.03.08

[micah anderson]

"Adam D. Barratt"  writes:

> Control: tags -1 + moreinfo
>
> On Wed, 2018-03-21 at 14:07 +0100, micah wrote:
>> "Adam D. Barratt"  writes:
>> 
>> > Control: tags -1 + moreinfo
>> > 
>> > On Tue, 2018-03-20 at 16:32 -0400, micah wrote:
>> > > The leap-archive-keyring is a simple archive keyring package that
>> > > contains the
>> > > signing key for trusting the archive of the LEAP encryption
>> > > access
>> > > project. Unfortunately, the expiration date chosen for the key
>> > > that
>> > > is included
>> > > in the package in Stretch was too low, and it has expired.
>> > > 
>> > > The newer package that is available in testing, unstable, and
>> > > backports provides
>> > > a key with a sufficient length to cover the stable release cycle.
>> > > 
>> > > I would like to propose that this package be included in the next
>> > > stable release point update.
>> > 
>> > We'd need to see a debdiff of the proposed upload, built on and
>> > tested
>> > against stretch, please.
>> 
>> Sorry, I thought I had attached the debdiff, here it is:
>
> Ah, sorry, I meant of the source packages, not the binaries.

Of course, I should have assumed that. I've attached the source debdiff
to this email.

> (Also, as per above - "of the proposed upload, built on and tested
> against stretch". The provided debdiff is against the version that was
> uploaded to unstable.

Fixed.

> An upload to stretch at least needs a new changelog stanza with a
> different version number - most likely 2016.03.08+deb9u1, but possibly
> 2017.11.24~deb9u1 if you wish to argue that all of the changes since
> the current version in stretch are appropriate for a stable update.)

I went with 2017.11.24~deb9u1 because indeed, the changes since the
current version in stretch are appropriate for a stable update, namely:

1. Providing keys in a second location, to aid in the transition from
jessie->stretch methods for how sources.list [signed-by=] method changed
to allow for both paths and fingerprints

2. fix priority to be in-line with debian policy

3. add a dependency on gnupg

4. update the expirations on the keys themselves

I'm only unsure if changing the Priority section is allowed in a stable
point update?

Thanks!
Micah




leap-archive-keyring-src.debdiff
Description: Binary data


signature.asc
Description: PGP signature

Update puppet in stable

[micah anderson]

Hello,

There is one particularly annoying issue that has come up with puppet
since the release. That issue, #573551, has to do with dependency-based
boot scripts and how puppet disables/enables services, it simply doesn't
work properly in Squeeze.

One other trivial fix is included, an adjustment to the puppet
initscript LSB header to fix the name.

Please find below the diffs, if the release team approves, I will upload
to stable.

Thanks!

commit ad00e93381ce79173602f67d0fb2375535a74a96
Author: Micah Anderson 
Date:   Thu Mar 3 12:52:33 2011 -0500

update changelog to reflect the two cherry-picked issues

diff --git a/debian/changelog b/debian/changelog
index 56f05f7..7844f7f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+puppet (2.6.2-5) stable; urgency=low
+
+  [ Micah Anderson ]
+  * Use update-rc.d enable/disable in the "debian" provider for the 
+"service" type, thanks madduck! (Closes: #573551)
+  * Update Should-Start header for the puppet initscript
+
+ -- Micah Anderson   Thu, 03 Mar 2011 12:50:18 -0500
+
 puppet (2.6.2-4) unstable; urgency=low
 
   * Normalize parameterized classes (Closes: #607294)

commit 8d41bb0da2520e2236a524ab17fe6b5b0a6a9812
Author: Micah Anderson 
Date:   Thu Mar 3 12:48:26 2011 -0500

update Should-Start header for the puppet initscript

Conflicts:

debian/changelog

diff --git a/debian/puppet.init b/debian/puppet.init
index d6b4fb0..7791229 100644
--- a/debian/puppet.init
+++ b/debian/puppet.init
@@ -3,7 +3,7 @@
 # Provides:  puppet
 # Required-Start:$network $named $remote_fs $syslog
 # Required-Stop: $network $named $remote_fs $syslog
-# Should-Start:  puppetmaster
+# Should-Start:  puppet
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 ### END INIT INFO  
 

commit 6331667960185967d1355dba5253096c9939e33f
Author: martin f krafft 
Date:   Sat Jan 15 18:57:53 2011 +0100

Use update-rc.d enable/disable in the "debian" provider in the "service" 
type (Closes: #573551)

diff --git a/lib/puppet/provider/service/debian.rb 
b/lib/puppet/provider/service/debian.rb
index 3d09e28..f3ab221 100755
--- a/lib/puppet/provider/service/debian.rb
+++ b/lib/puppet/provider/service/debian.rb
@@ -23,7 +23,7 @@ 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", "."
+update_rc @resource[:name], "disable"
   end
 
   def enabled?
@@ -43,6 +43,6 @@ Puppet::Type.type(:service).provide :debian, :parent => :init 
do
 
   def enable
 update_rc "-f", @resource[:name], "remove"
-update_rc @resource[:name], "defaults"
+update_rc @resource[:name], "enable"
   end
 end



-- 



pgpCIJYt9obv4.pgp
Description: PGP signature

Re: Update puppet in stable

[micah anderson]

On Wed, 09 Mar 2011 06:59:13 -0500, micah anderson  wrote:

Uh, I just reverted this stupidity:

> +  * Update Should-Start header for the puppet initscript

...

> -# Should-Start:  puppetmaster
> +# Should-Start:  puppet
>  # Default-Start: 2 3 4 5
>  # Default-Stop:  0 1 6
>  ### END INIT INFO
>

The only change being proposed for the point release is the one fixing
#573551.

Sorry about that,
micah


pgp6xdUkh0CIM.pgp
Description: PGP signature

Re: Update puppet in stable

[micah anderson]

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

Re: Update puppet in stable

[micah anderson]

On Wed, 08 Jun 2011 20:29:14 +0100, "Adam D. Barratt" 
 wrote:
> On Sun, 2011-05-22 at 15:56 -0400, micah anderson wrote:
> > 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.
> 
> Thanks for this.  Overall, I'm happy with the patch but note that
> #573551 still appears to be open; assuming I'm reading the discussion in
> the bug log correctly, should it not have been marked as closed with the
> upload of 2.6.7-1 back in March?

Actually, the fix wasn't available upstream until 2.6.8, which was put
into unstable april 28th, and migrated to testing may 10th. It is true
that the bug was not properly closed in that upload. I've just marked
that bug as done with the right version number.

> I'm also guessing that there's a typo in this:
> 
> > 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
> 
> given that Lenny is the only supported Debian release which *doesn't*
> use 2.88 or later.

yes, that was a typo.

micah


pgpWZURodMDLY.pgp
Description: PGP signature

Re: updating monkeysphere in stable

[micah anderson]

On Fri, 17 Jun 2011 21:37:58 +0100, "Adam D. Barratt" 
 wrote:
> On Sun, 2011-05-22 at 16:19 -0400, micah wrote:
> > 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. 
> 
> Apologies for the delay in getting back to you, and thanks for working
> on this.  Please go ahead, bearing in mind that the acceptance window
> for 6.0.2 closes over the weekend.

I can get it uploaded tomorrow (saturday) first thing, I hope that is
soon enough.

micah


pgp2Vag0hCI9v.pgp
Description: PGP signature

Re: handling util-vserver regression

[Micah Anderson]

Hi release team,

I have not received a response to my original email on this subject, I
suspect because it may not have been sent out properly. I do not see my
original message in the lists.debian.org debian-release archive,
although I do see it archived in services such as gmane[0]...

Anyways, its for the best, because since then new issues have showed up
that further support uploading a new upstream release, specifically the
critical RC bug #506949[1] which seems to be a result of backporting
incomplete pieces, resulting in odd corner cases manifesting. 

As the work involved with either path is not trivial, I am hoping to get
a hint from you about which way I should proceed first.

Thanks,
micah

0. http://permalink.gmane.org/gmane.linux.debian.devel.release/27027
1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506949

* Micah Anderson <[EMAIL PROTECTED]> [2008-11-14 16:00-0500]:
> 
> Hi release team,
> 
> As I mentioned in #debian-release, and reported by weasel in #505521,
> the version of util-vserver that is currently scheduled to be shipped
> with Lenny (0.30.216~r2772-4) has an unfortunate regression from the
> etch version: namely that it does not support 2.6.27, whereas the
> earlier version does. If previous versions worked with 2.6.27, what
> broke to make it not work? Turns out that the snapshot I took of
> upstream's pre-release SVN happened to pull at the point where upstream
> had merged support for the first proposed PID namespace API, not soon
> afterwards it was decided that things weren't going to be done that
> way, so this was removed and replaced with a better way of doing
> things. This means that I pulled the snapshot when it had the first PID
> namespace API, but not the second. 
> 
> I believe that we froze before the second one was introduced, so the two
> possibilities were to ship util-vserver with a version that supports
> 2.6.26, but breaks 2.6.27, or not ship a version that supported
> 2.6.26. Obviously, if we wanted to support Lenny kernels, we were going
> to need to do the former, so thats what I did... 
> 
> So, now that 2.6.27 is released, and people are starting to use that,
> they are noticing that util-vserver doesn't work with 2.6.27 and are
> disappointed to hear that Lenny will not ship with a version that
> doesn't have this regression.
> 
> So, I have these options:
> 
> 1. backporting the upstream changes to get support of 2.6.27, there are
> a number of patches to get this to work, and I'm not exactly sure I know
> which they are. This would result in a backport of software that has not
> been tested by anyone.
> 
> 2. bring the package up to HEAD, where it has had some testing by the
> vserver community, will definitately support 2.6.27, incorporates the
> additional patches that I've picked from upstream to solve various
> RC-related things (which are already on their way to Lenny), but also
> includes some unrelated commits (such as some python and other
> stuff. Most of these I can disable in the ./configure line in
> debian/rules by adding --without-python --disable-versioning)
> 
> In my mind, the better path is to do #2, because I know that this
> version would absolutely work, however my suspicion is that the delta
> would be too large for the release team to accept. The problem is that
> the smaller delta that would result from me doing #1 would be more prone
> to problems and would be completely untested.
> 
> So, as requested by Luk, I've attached the diff to this email that would
> accomplish #2 and I am wondering which would be the better path to
> proecede on in order to get this into Lenny. 
> 
> As you will see in the patch below, there are some changes in there were
> I remove dpatches that are taken care of by upstream, they added various
> python and other stuff that would be disabled in the ./configure lines
> that I added, there are some redhat/rpm related changes that wouldn't
> bother us, and they added their GPL in their COPYING file, which was
> previously empty... and finally the patches that are necesary to get the
> 2.6.27 support to work again (which aren't trivial themselves). Here it
> is:

(diff snipped to help get this through the list, see the gmane
referenced URL for the full diff[0])


signature.asc
Description: Digital signature

Please hint util-vserver 0.30.216~r2772-5 [was: handling util-vserver regression]

[Micah Anderson]

Hi folks,

I've decided to go ahead and backport the pieces necessary to solve the
RC bugs that exist due to the capability problems, the disabled cron and
the kernel regression.

So, at your earliest convenience, please hint in 0.30.216~r2772-5 of
util-vserver. 

Thanks, and sorry for all the noise!#
micah


signature.asc
Description: Digital signature

Unblock request: backupninja 0.9.6-4

[Micah Anderson]

Hello!

Please consider unblocking backupninja 0.9.6-4, it has some trivial
fixes that would be nice if they were included in Lenny:

  * Fix df error message from cron (Closes: #497535)
  * Removed Lenny unsupported desturl example (Closes: #507679)
  * Fixed Lintain warning: maintainer-script-ignores-errors preinst

As you can see, from the below diff, the changes are quite small:

Index: debian/changelog
===
--- debian/changelog(revision 622)
+++ debian/changelog(revision 626)
@@ -1,3 +1,11 @@
+backupninja (0.9.6-4) unstable; urgency=low
+
+  * Fix df error message from cron (Closes: #497535)
+  * Removed Lenny unsupported desturl example (Closes: #507679)
+  * Fixed Lintain warning: maintainer-script-ignores-errors preinst
+  
+ -- Micah Anderson <[EMAIL PROTECTED]>  Mon, 08 Dec 2008 09:41:22 -0500
+
 backupninja (0.9.6-3) unstable; urgency=low
 
   * Removed configure.ac and regenerate the autoconf junk so 
Index: debian/backupninja.preinst
===
--- debian/backupninja.preinst  (revision 622)
+++ debian/backupninja.preinst  (revision 626)
@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/sh -e
 
 # Remove the erroneous /etc/logrotate.d/backupninja directory if it
 exists
 
Index: src/backupninja.in
===
--- src/backupninja.in  (revision 622)
+++ src/backupninja.in  (revision 626)
@@ -561,7 +561,7 @@
 previous=""
for i in $(ls "$configdirectory"); do
  backuploc=$(grep ^directory
  "$configdirectory"/"$i" | @AWK@
  '{print $3}')
-   if [ "$backuploc" !=
"$previous" ]; then
+if [ "$backuploc" != "$previous" -a -n
"$backuploc" ]; then
df -h "$backuploc"
previous="$backuploc"
fi
Index: examples/example.dup
===
--- examples/example.dup(revision 622)
+++ examples/example.dup(revision 626)
@@ -120,12 +120,6 @@
 #keep = 60
 #keep = yes
 
-# full destination URL, in duplicity format; if set, desturl overrides
-# sshoptions, destdir, desthost and destuser; it also disables
-# testconnect and
-# bandwithlimit. For details, see duplicity manpage, section "URL
-# FORMAT".
-#desturl = file:///usr/local/backup
-#desturl = rsync://[EMAIL PROTECTED]//var/backup/bla
-
 # bandwith limit, in kbit/s ; default is 0, i.e. no limit
 #bandwidthlimit = 128


signature.asc
Description: Digital signature

Please unblock dietlibc-0.31-1.1

[Micah Anderson]

 
Hello,

Due to namespace virtualization changes in the newer kernels that are
now in Lenny, there were changes that were made to util-vserver to
support the new mechanisms for unmounting and cleanup in guests (because
the chroot barrier is being faded out in favor of the new namespace and
pivot_root). 

These were fixed in the version of util-vserver that has a hint to
transition into lenny (-5), but it is not transitioning due to a build
failure on alpha and ia64. This is a build-regression for util-vserver,
which used to build on these architectures, but refuses now. Because of
these two architectures not building, its holding back the important
transition of util-vserver to Lenny.

Fortunately, the fix to dietlibc is relatively easy, I've got a patch
and tested it on all the different architectures, and have NMU'd (with
the maintainer, Gerrit Pape's approval), but it needs to be let into
Lenny so util-vserver can build against it.

So, if you wouldn't mind making a hint for 0.31-1.1 of dietlibc to
transition into Lenny, the diff is quite small, and is below:

--- a/syscalls.s/umount.S   9 Jan 2001 17:57:49 -   1.1
+++ b/syscalls.s/umount.S   10 Dec 2008 20:21:33 -
@@ -1,3 +1,7 @@
 #include "syscalls.h"
 
+#if defined(__NR_oldumount) && defined(__NR_umount)
+syscall(oldumount,umount)
+#else
 syscall(umount,umount)
+#endif
--- a/syscalls.s/umount2.S  4 Jan 2003 22:21:48 -   1.2
+++ b/syscalls.s/umount2.S  10 Dec 2008 20:21:33 -
@@ -1,5 +1,7 @@
 #include "syscalls.h"
 
-#ifdef __NR_umount2
+#if defined(__NR_umount2)
 syscall(umount2,umount2)
+#elif defined(__NR_oldumount) && defined(__NR_umount)
+syscall(umount,umount2)
 #endif



signature.asc
Description: Digital signature

Unblock request: util-vserver 0.30.216~r2772-6

[Micah Anderson]

Hi folks,

Thanks to Luk for allowing the dietlibc version to transition into Lenny
so that util-vserver can properly build on a few architectures. I could
do a binnmu to get those to build, but there were a couple new release
related fixes that I think should be let in. One resolves a release goal
of fixing bashisms (#486060) and another fixes a functionality
regression on powerpc through a simple change to the configure option on
that architecture.

So, with the hope that this is the last request I bother you with, would
you please unblock 0.30.216~r2772-6 of util-vserver?

Thanks,
micah


signature.asc
Description: Digital signature

Please allow util-vserver 0.30.212-1 into etch

[Micah Anderson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Dearest release team,

Due to changes in the vserver patch necessary for 2.6.19+, changes in
the user-space util-vserver package were required. The changes between
0.30.211-6 and 0.30.212-1 are important.

Version 0.30.212-1, which is in unstable, works for both 2.6.18 and
2.6.19+, and has been in unstable for nearly 90 days now without any
regression problems reported specific to this version.

As such I would humbly request that it be unblocked and allowed to
migrate to etch to make our lives a hair easier down the line. If
0.30.211-6 is left in etch, anyone upgrading to a newer kernel will find
some significant weirdness.

Micah

ps - although I am not listed officially as the maintainer of the
package, I am listed as the co-maintainer and you will see that I have
done a significant number of the uploads of this package in the last
year and commits to the svn repository. Nevertheless, I am CC'ing the
maintainer as a courtesy, I believe he will not disagree with this
request. :)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF6NDY9n4qXRzy1ioRAiPoAKCiy9PDpdrn+cP92Ag/46nbC84MpQCdEgWm
gXomXyGKuFj6HASW6Iv+1pw=
=hUAl
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Please allow util-vserver 0.30.212-1 into etch

[Micah Anderson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Micah Anderson <[EMAIL PROTECTED]> writes:
>> Due to changes in the vserver patch necessary for 2.6.19+, changes in
>> the user-space util-vserver package were required. The changes
>> between 0.30.211-6 and 0.30.212-1 are important.

Marc 'HE' Brockschmidt wrote:
> 161 files changed, 5326 insertions(+), 10685 deletions(-)

If I remove all the useless stuff (.svn stuff that crept in, upstream
Changelog which for some reason had a number of changes, autotools
noise, debian patches that have been incorporated into upstream, NOOP
RCS header date changes, fedora yum repo gpg key change (unrelated to
debian) gentoo initscript changes (unrelated to debian), redhat initpost
changes (unrelated to debian), documentation changes
(doc/configuration.html, configuration-xhtml.xsl, configuration.xml),
redhat spec file changes (unrelated to debian) and the THANKS change,
leaves:

58 files changed, 189 insertions(+), 446 deletions(-)

Removing the 20+ trivial fixes of:

- -   WRITE_MSG(2, " --help\" for more information.\n");
+   WRITE_MSG(2, " --help' for more information.\n");

Leaves 40 changes, 169 insertions(+), 426 deletions, not that much when
you consider a new kernel API is supported.

>This is simply not reviewable and we don't have kernels >= 2.6.19 in
>etch, so I'm really not convinced that letting this trought at this
>point of the freeze is a good idea.

The reason for requesting this is to make etch+.5 transition smoother,
and as I understand it, a newer kernel is expected to be introduced in
etch+.5, and anything newer than 2.6.18 will break all vserver support.
Additionally, any user who installs a backported kernel, or a
hand-rolled one, will be unable to use vservers with 0.30.211-6.

Micah
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF6yf+9n4qXRzy1ioRAo3nAKCIIwP0Rnb2Ds+m5UA3isgjCMxuAQCeOkpI
J5Z3C1tHQ3nelrXPv44cFNE=
=nJyM
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Please allow util-vserver 0.30.212-1 into etch

[Micah Anderson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Micah Anderson wrote:
> If I remove all the useless stuff (.svn stuff that crept in, upstream
> Changelog which for some reason had a number of changes, autotools
> noise, debian patches that have been incorporated into upstream, NOOP
> RCS header date changes, fedora yum repo gpg key change (unrelated to
> debian) gentoo initscript changes (unrelated to debian), redhat initpost
> changes (unrelated to debian), documentation changes
> (doc/configuration.html, configuration-xhtml.xsl, configuration.xml),
> redhat spec file changes (unrelated to debian) and the THANKS change,
> leaves:
> 
> 58 files changed, 189 insertions(+), 446 deletions(-)
> 
> Removing the 20+ trivial fixes of:
> 
> -   WRITE_MSG(2, " --help\" for more information.\n");
> +   WRITE_MSG(2, " --help' for more information.\n");
> 
> Leaves 40 changes, 169 insertions(+), 426 deletions, not that much when
> you consider a new kernel API is supported.

Attached cleaned up patch for review.

Micah
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF6yja9n4qXRzy1ioRAlujAKC3QtqSi/DRuJFO6GMohmfq3JVFBwCgtCkI
L+cG5Vhu2AytJvADG2LPALc=
=/4wu
-END PGP SIGNATURE-
diff -ur ./config.h.in ../0.30.212-1/config.h.in
--- ./config.h.in   2006-10-07 13:32:22.0 -0600
+++ ../0.30.212-1/config.h.in   2006-12-09 11:56:07.0 -0700
@@ -232,6 +232,9 @@
 /* Enable support for some obsoleted API of vserver 1.3.x */
 #undef VC_ENABLE_API_V13OBS
 
+/* Enable support for API of vserver 2.1.x */
+#undef VC_ENABLE_API_V21
+
 /* Version number of package */
 #undef VERSION
 
diff -ur ./ensc_wrappers/wrappers-vserver.hc 
../0.30.212-1/ensc_wrappers/wrappers-vserver.hc
--- ./ensc_wrappers/wrappers-vserver.hc 2007-03-04 12:25:45.0 -0700
+++ ../0.30.212-1/ensc_wrappers/wrappers-vserver.hc 2006-12-09 
11:56:07.0 -0700
@@ -132,15 +132,15 @@
 }
 
 inline static WRAPPER_DECL void
-Evc_set_namespace()
+Evc_set_namespace(xid_t xid, uint_least64_t mask)
 {
-  FatalErrnoError(vc_set_namespace()==-1, "vc_set_namespace()");
+  FatalErrnoError(vc_set_namespace(xid, mask)==-1, "vc_set_namespace()");
 }
 
 inline static WRAPPER_DECL void
-Evc_enter_namespace(xid_t xid)
+Evc_enter_namespace(xid_t xid, uint_least64_t mask)
 {
-  FatalErrnoError(vc_enter_namespace(xid)==-1, "vc_enter_namespace()");
+  FatalErrnoError(vc_enter_namespace(xid, mask)==-1, "vc_enter_namespace()");
 }
 
 inline static WRAPPER_DECL xid_t
diff -ur ./kernel/cacct_cmd.h ../0.30.212-1/kernel/cacct_cmd.h
--- ./kernel/cacct_cmd.h2007-03-04 12:25:45.0 -0700
+++ ../0.30.212-1/kernel/cacct_cmd.h2006-12-09 11:56:07.0 -0700
@@ -13,11 +13,4 @@
 };
 
 
-#ifdef __KERNEL__
-
-#include 
-
-extern int vc_sock_stat(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 #endif /* _VX_CACCT_CMD_H */
diff -ur ./kernel/context_cmd.h ../0.30.212-1/kernel/context_cmd.h
--- ./kernel/context_cmd.h  2007-03-04 12:25:45.0 -0700
+++ ../0.30.212-1/kernel/context_cmd.h  2006-12-09 11:56:07.0 -0700
@@ -6,10 +6,6 @@
 
 #define VCMD_task_xid  VC_CMD(VINFO, 1, 0)
 
-#ifdef __KERNEL__
-extern int vc_task_xid(uint32_t, void __user *);
-
-#endif /* __KERNEL__ */
 
 #define VCMD_vx_info   VC_CMD(VINFO, 5, 0)
 
@@ -19,10 +15,6 @@
/* more to come */
 };
 
-#ifdef __KERNEL__
-extern int vc_vx_info(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 
 #define VCMD_ctx_stat  VC_CMD(VSTAT, 0, 0)
 
@@ -32,10 +24,6 @@
/* more to come */
 };
 
-#ifdef __KERNEL__
-extern int vc_ctx_stat(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 
 /* context commands */
 
@@ -53,11 +41,6 @@
uint64_t flagword;
 };
 
-#ifdef __KERNEL__
-extern int vc_ctx_create(uint32_t, void __user *);
-extern int vc_ctx_migrate(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 
 
 /* flag commands */
@@ -70,11 +53,6 @@
uint64_t mask;
 };
 
-#ifdef __KERNEL__
-extern int vc_get_cflags(struct vx_info *, void __user *);
-extern int vc_set_cflags(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 
 
 /* context caps commands */
@@ -96,13 +74,6 @@
uint64_t cmask;
 };
 
-#ifdef __KERNEL__
-extern int vc_get_ccaps_v0(struct vx_info *, void __user *);
-extern int vc_set_ccaps_v0(struct vx_info *, void __user *);
-extern int vc_get_ccaps(struct vx_info *, void __user *);
-extern int vc_set_ccaps(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 
 
 /* bcaps commands */
@@ -115,9 +86,4 @@
uint64_t bmask;
 };
 
-#ifdef __KERNEL__
-extern int vc_get_bcaps(struct vx_info *, void __user *);
-extern int vc_set_bcaps(struct vx_info *, void __user *);
-
-#endif /* __KERNEL__ */
 #endif /* _VX_CONTEXT_CMD_H */
diff -ur ./kernel/cvirt_cmd.h ../0.30.212-1/kernel/cvirt_cmd.h
--- ./kern

Please unblock util-vserver

[Micah Anderson]

Hi,

I am writing to request the manual unblock of util-vserver
0.30.216~r2750-3 which was uploaded last night to fix a RC bug in the
package that was uploaded before the freeze, but had not migrated to
testing yet. This version of the package only has the fix for the RC bug
#491072 and no other changes.

Thank you, and here's to a great release!
micah


signature.asc
Description: Digital signature

Re: Scheduling linux-2.6 2.6.26-3

[Micah Anderson]

Hi release team,

I'm writing to request that a hint be added to allow util-vserver
0.30.216~r2772-1 to enter testing. As discussed on debian-kernel, this
version of the util-vserver user-space utilities is necessary in order
to work with the kernel targetted for lenny, and so I am requesting a
release exception to sync these up:

* Micah Anderson <[EMAIL PROTECTED]> [2008-08-21 15:31-0400]:
> * dann frazier <[EMAIL PROTECTED]> [2008-08-21 10:51-0400]:
> > On Thu, Aug 21, 2008 at 01:43:44PM -0400, Micah Anderson wrote:
> > > * dann frazier <[EMAIL PROTECTED]> [2008-08-20 17:59-0400]:
> > > This is a user-space issue, not a kernel issue. Using an older version
> > > of the user-space utilities work, and the kernel tests pass. I am
> > > working with upstream to determine the fix for this.
> > 
> > Cool, thank you!
> 
> Upstream expects a fix in approximately 2 days, will track this and
> request a release exception for lenny.

Thanks for your hard work!
Micah


signature.asc
Description: Digital signature

Please unblock util-vserver 0.30.216~r2772-2

[Micah Anderson]

Hi release team,

I'm writing to request that a hint be added to allow util-vserver
0.30.216~r2772-2 to enter testing. 

This version fixes two RC bugs (one reported to the BTS, one security
related issue that was introduced in the previous release which makes
read-only bind mounts revert to r/w unexpectedly):

  * Fix initscript stop blocking reboot/shutdown (Closes: #496803)  

  * Add 20securemount.dpatch and 30secmount_dev_fix.dpatch to fix -ro
bindmounts becoming -rw 
   


Micah

ps - As these utilities are closely tied with the kernel release that
will ship with Lenny, there is a chance that if the vserver patch is
updated in 2.6.26, another release unblock will be requested. I
apologize for that in advance.


signature.asc
Description: Digital signature

Please unblock facter 1.5.1-0.1

[Micah Anderson]

Hi folks,

The most recent upload of facter (1.5.1-0.1) should be allowed to go
into Lenny because the previous version (1.5.0) causes some serious RC
issues:

 * makes unrelated software on the system (or the whole system)
 break

The version of facter in Lenny right now causes the puppet package to
stop working, and leaves zombies all over the system.


   
 * makes the package in question unusable or mostly so  

   

The version of facter in Lenny essentially stops working very quickly
and become unresponsive.



In my my opinion, as the person who uploaded 1.5.0, the package that is
currently set to ship in lenny is unsuitable for release, and after
extensive testing of 1.5.1, this issue is solved. 

It is for these reasons I am requesting facter 1.5.1-0.1 be unblocked
and allowed to transition to Lenny.

Thanks for all your work during this period!

Micah


signature.asc
Description: Digital signature

Freeze exceptions

[Micah Anderson]

Hello release team,

I'm requesting hints to be added for the following two packages which
fix RC bugs:

util-vserver: added a versioned dependency on util-linux due to the fact
that the ionice binary was moved into this package and without this
dependency util-vserver can break mid-upgrade resulting in a partial
upgrade scenario: #499857

backupninja: fixed the autoconf junk that resulted in a substitution
variable not being set on configure, making some binaries not function
at all: #494728

Thanks!
micah


signature.asc
Description: Digital signature

Please unblock util-vserver 0.30.216~r2772-4

[Micah Anderson]

Hi release-team,

Please unblock util-vserver 0.30.216~r2772-4, this fixes a few important
remaining issues that would be unfortunte if they were included in
Lenny, it only includes these changes:

. Adds a patch from upstream to fix a potential future security issue
. Fixes a POSIX compliance issue (missing /dev/shm in guest builds)
. Fixes a pathing issue that failed to remove confusing unsupported legacy

Thanks, and here is to the greatest Debian release yet!
Micah


signature.asc
Description: Digital signature

Please allow backupninja into testing

[Micah Anderson]

I've just uploaded a fix to unstable for important bug #307620 in
package backupninja. It satisfies all the criteria outlined in the most
recent Release Update email which outlines what can move into testing:

Version is the same between testing and unstable.
Changes are not significant (only a handfull of echo lines added).
Changes are only related to fixing the bug in question.
Fix is for severity: Important bug #307620.
Package "backupninja" has priority of optional.

Thanks, I'm excited about the freeze, and looking forward to a
productive BSP.

Micah



- End forwarded message -


signature.asc
Description: Digital signature

Re: Please allow backupninja into testing

[Micah Anderson]

On Sat, 07 May 2005, Steve Langasek wrote:

> Hi Micah,
>
> What is the intent behind this undocumented change in the package?
> 
> --- backupninja-0.5.orig/etc/cron.d/backupninja
> +++ backupninja-0.5/etc/cron.d/backupninja
> @@ -3,4 +3,4 @@
>  PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>  
>  # run backupninja every hour on the hour
> -00 * * * * root if [ -x /usr/sbin/backupninja -a -f /etc/backupninja.conf ]; 
> then /usr/sbin/backupninja; fi
> +00 * * * * root if [ -x /usr/sbin/backupninja ]; then /usr/sbin/backupninja; 
> fi

Hi Steve,

This change is actually part of the documented change in the
changelog (pasted here for ease of reference:

  * Implemented fix to cause fatal errors in the backupninja script
itself to be reported, rather than be silently ignored (Closes: #307620)

The bug reporter correctly took issue with the fact that if there was
a fatal error in the backupninja script, there would be no report
generated indicating this. Fatal errors are:

1. Permission problems in /etc/backup.d
2. Permission problems on /etc/backupninja.con
3. Improper script directory specified in config

or, most importantly to this discussion:
4. Missing /etc/backupninja.conf

The script itself has an error reporting mechanism that would spit out
an error if /etc/backupninja.conf was missing. However, the cronjob
was setup such that it tested to see if the /etc/backupninja.conf file
existed, and if not it would simply not run (and not report this as a
fatal error). This means that if the initial cron statement were kept
in, the bug would still exist. By removing this duplicate check from
the cronjob, the check is left to the script itself which will report
an error if the configuration file does not exist.

Micah


signature.asc
Description: Digital signature

Please consider syslog-ng for testing

[Micah Anderson]

syslog-ng has a security hole in 1.6.5-2 as noted on
http://newraff.debian.org/~joeyh/testing-security.html

I've just backported the fix that appeared in 1.6.6 and was sent as a
patch to the debian bug by the upstream maintainer.

The version uploaded to unstable (1.6.5-2.1) contains the fix for the
security hole, two fixes for lintian errors (not warnings) and three
documentation updates:

  * Non-maintainer upload to fix security hole for sarge
  * Changed debian/control to use a versioned depends on util-linux
to fix lintian error
  * Converted debian/changelog to be valid UTF-8 by to fix lintian
error
  * Updated documentation: doc/syslog-ng.conf.5, doc/syslog-ng.8 to fix
outdated information and typos and language clarification on klogd
in doc/sgml/syslog-ng.sgml

Please consider allowing this version into sarge.

Thanks,
Micah


signature.asc
Description: Digital signature

Re: Please consider syslog-ng for testing

[Micah Anderson]

Joey Hess schrieb am Tuesday, den 10. May 2005:

> Micah Anderson wrote:
> > I've just backported the fix that appeared in 1.6.6 and was sent as a
> > patch to the debian bug by the upstream maintainer.
> > 
> > The version uploaded to unstable (1.6.5-2.1) contains the fix for the
> > security hole, two fixes for lintian errors (not warnings) and three
> > documentation updates:
> > 
> >   * Non-maintainer upload to fix security hole for sarge
> >   * Changed debian/control to use a versioned depends on util-linux
> > to fix lintian error
> >   * Converted debian/changelog to be valid UTF-8 by to fix lintian
> > error
> >   * Updated documentation: doc/syslog-ng.conf.5, doc/syslog-ng.8 to fix
> > outdated information and typos and language clarification on klogd
> > in doc/sgml/syslog-ng.sgml
> > 
> > Please consider allowing this version into sarge.
> 
> -Depends: ${shlibs:Depends}, util-linux
> +Depends: ${shlibs:Depends}, util-linux (>=2.12-10)
> 
> You're missing a space here.  ^^
> 
> Otherwise looks ok.

This space has been fixed. Additionally, the changelog which was not
converted properly to UTF-8 was also fixed. The new upload (1.6.5-2.2)
fixes these problems and should be considered for sarge.

Thanks,
micah


signature.asc
Description: Digital signature

Sourceful rebuild of lcrash

[Micah Anderson]

A sourceful upload was made of lcrash to trigger a rebuild against
binutils-dev 2.15-6 to get security fix for elf integer overflow bug
in the bfd archive library. Please consider allowing this new build of
lcrash (7.0.0.pre.cvs.20050322-3) with no source changes into testing
to solve this security irritant.

Thanks,
micah


signature.asc
Description: Digital signature

Please consider pike7.2

[Micah Anderson]

Pike7.2 has a FTBFS due to timestamp skew during patching of a file
that is a make dependency. I've applied the patch submitted to the BTS
by Steve Langasek which adds a simple touch in debian/rules solving
this problem. There were no other changes, so without further ado,
please consider allowing pike7.2_7.2.580-3.1 into testing.

Thanks,
micah


signature.asc
Description: Digital signature

Re: Please consider pike7.2

[Micah Anderson]

On Tue, 31 May 2005, Frank Lichtenheld wrote:

> On Fri, May 27, 2005 at 07:06:58PM -0500, Micah Anderson wrote:
> > Pike7.2 has a FTBFS due to timestamp skew during patching of a file
> > that is a make dependency. I've applied the patch submitted to the BTS
> > by Steve Langasek which adds a simple touch in debian/rules solving
> > this problem. There were no other changes, so without further ado,
> > please consider allowing pike7.2_7.2.580-3.1 into testing.
> 
> How did you manage to let the pike7.2-gl package not depend on
> xlibmesa-gl? All other versions and architecures do... And if
> I rebuild it, I get the dependency, too...
> 
> There may a binNMU on i386 needed here.

It looks like my system had a shared library problem with a dangling
symlink for /usr/lib/libGL.so when I built this, causing the
dh_shlibdeps not to pick up the right pieces. I'm rebuilding in a
fresh i386 environment and will binary NMU this once it is finished,
unless the maintainer gets to it first.

Micah


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#689194: unblock: puppet/2.7.18-2

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package puppet, to allow 2.7.18-2 to transition to
Wheezy, it fixes only the RC bug #683834 here is the differences:

diff --git a/debian/changelog b/debian/changelog
index c610376..3dea127 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+puppet (2.7.18-2) unstable; urgency=low
+
+  [ Faidon Liambotis ]
+  * Install all files required by vim-addon-manager (Closes: #683834)
+
+ -- Stig Sandbeck Mathisen   Wed, 19 Sep 2012 11:45:03 +0200
+
 puppet (2.7.18-1) unstable; urgency=high
 
   * New upstream release (CVE-2012-3864, CVE-2012-3865,
diff --git a/debian/vim-puppet.install b/debian/vim-puppet.install
index d605cd6..6d515e4 100644
--- a/debian/vim-puppet.install
+++ b/debian/vim-puppet.install
@@ -1,3 +1,5 @@
 debian/vim-puppet.yaml /usr/share/vim/registry
 ext/vim/ftdetect/puppet.vim /usr/share/vim/addons/ftdetect
+ext/vim/ftplugin/puppet.vim /usr/share/vim/addons/ftplugin
 ext/vim/syntax/puppet.vim /usr/share/vim/addons/syntax
+ext/vim/indent/puppet.vim /usr/share/vim/addons/indent
diff --git a/debian/vim-puppet.yaml b/debian/vim-puppet.yaml
index 2902b9b..bbeb191 100644
--- a/debian/vim-puppet.yaml
+++ b/debian/vim-puppet.yaml
@@ -2,5 +2,6 @@ addon: puppet
 description: "Syntax highlighting for puppet"
 files:
   - ftdetect/puppet.vim
+  - ftplugin/puppet.vim
   - indent/puppet.vim
   - syntax/puppet.vim

unblock puppet/2.8.18-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
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/20120930031843.9310.21287.report...@localhost.riseup.net

Bug#693275: RM: util-vserver/0.30.216-pre2864-2.1

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,

I'm requesting removal of util-vserver from wheezy. 

Due to the fact that the kernel team decided not to provide Linux-Vserver
patches, I have not updated the user-space utilities.  As a result, the version
that is in wheezy now is the same as is in squeeze. It is too late to update
them to a newer upstream version due to the freeze, so I am requesting the
removal as this version is too old to be useful for anyone.

Micah

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
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/20121115010759.30160.69753.report...@minnow.riseup.net

Bug#600545: unblock: puppet/2.6.2-1

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Hello release team!

I am writing on behalf of the puppet packaging team. We would like to request a
freeze exception for the puppet 2.6.2-1 package. The existing version in
Squeeze contains too many severe bugs, including a few RC regressions. If we
ship the version that is in Squeeze, puppet will be unusable for a very long 
time
in Debian.
 
How we got here was a case of bad timing. The upstream release of puppet 2.6.0
arrived (July 20th) right before the Debian freeze (August 6th). This resulted
in the package transitioning into Squeeze and then almost immediately after, we
froze. This was an unfortunate situation as the 2.6.0 version of the software
turned out to be significantly buggy and unsuitable for release. In fact, the
RC bug #597399 was filed which pointed out some severe regressions from the
previous version. Puppet 2.6.2 primarily is a bug fix release to fix a number
of usability issues, documentation fixes and license clarifications.

We attempted to go through a process of cherry-picking a number of commits from
2.6.1/2 to 2.6.0 to fix these important bugs, but there are still a large
number of unfixed issues in the debian package. Continuing to do this would
result in a Debian version of puppet that differs from both 2.6.0 and 2.6.1
which would be difficult to support in the long run, and confusing for the
users.

We also did some packaging restructuring for after 2.6.0 but have decided that
in the interests of fixing only the necessary bits for release, we have
reverted the packaging restructuring for the 2.6.2 version that we would like
to enter into Squeeze.

Let us know if you have any questions, and thank you very much for your hard
work on Squeeze, it is very appreciated! 

unblock puppet/2.6.2-1

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20101018002159.999.14389.report...@algae.riseup.net

Bug#602025: unblock: backupninja/0.9.8.1-1

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Hello release team!

I would like to request a freeze exception for the backupninja
0.9.8.1-1 package. This version of backupninja was prepared to
contain, what we think, were only the changes that would make this
package work well with Squeeze and deserve a freeze exception. 

All the issues were related to fixing documentation/man page issues,
fixing critical locking bugs that prevented multiple runs, problematic
and unnecessary locking of tables, or errors when no job has been
configured. Additionally, this version does the necessary changes to
support the versions of the various utilities that will be shipped in
squeeze (such as rdiff-backup, duplicity, mdadm and the lvm
utilities).

Let me know if you have any questions, and thank you very much for
your hard work on Squeeze, it is very appreciated!

unblock backupninja/0.9.8.1-1

Micah

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20101031211826.13399.42792.report...@algae.riseup.net

Bug#606430: unblock: puppet/2.6.2-3

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Hello!

There have been a number of issues that have come up in the puppet
package that really should be included in Squeeze. The puppet
packaging team have fixed them, and so I am writing to ask that you
please make a freeze exception for puppet 2.6.2-3.

The changes from the current version in Squeeze were made specifically
with an eye towards fixing simple things, but important ones:

  . a remote security issue
  . fixing log rotation
  . fixing initscript that failed to remove PID file
  . fixing initscript to actually use the /etc/default file
  . include a missing binary
  . update logcheck rules
  . add missing suggests for functionality
  . add missing directory in puppet-common.dirs
  . update documentation 

Let me know if you have any questions, and thanks again for your hard work on 
Squeeze, its very appreciated!

unblock puppet/2.6.2-3

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20101209045725.14245.49496.report...@algae.riseup.net

Bug#607165: unblock: facter/1.5.7-2

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi release team!

There have been a few issues that have come up in the facter package
that should really be included in Squeeze. The puppet packaging team
has fixed them and so I am writing to ask that you please make a 
freeze exception for facter 1.5.7-2.

The choice for what changes to include were chosen specifically because they
were simple, and important for Squeeze. This closes a number of bugs in the
process (#515726, #585867, #585867, #515591, #603001):

  . debian/NEWS item to alert people about potential upgrade problems
  . fixed lintian error in debian/NEWS
  . add missing versioned dependency (ruby1.8) 
  . removed unused dependency (cdbs)
  . fixed an important core fact (domain/fqdn) #515591
  . added Vcs/Homepage fields to debian/control
  * debian/NEWS: fix lintian syntax-error-in-debian-news-file
  * debian/facter.8: fix manpage-section-mismatch
  * cherry pick important upstream virtualization support

Let me know if you have any questions, and thanks again for your hard work on
Squeeze, i'm looking forward to this release! 

unblock facter/1.5.7-2

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20101215065220.24072.95958.report...@algae.riseup.net

Bug#607165: unblock: facter/1.5.7-2

[micah anderson]

Hi Mehdi,

> I'm not decided yet if I'll unblock the package (because I didn't finish the
> review yet) but I noticed something (that looks) odd (to me) in the Depends
> field. So, facter depends on:
> 
>   Depends: ruby1.8 (>= 1.8.7.72-3lenny1), net-tools, bind9-host | host,
> libopenssl-ruby1.8 | libopenssl-ruby1.9
> 
> Why does it depend on "libopenssl-ruby1.8 | libopenssl-ruby1.9" when
> it has a strong dependency on ruby1.8? I tend to think that putting
> "libopenssl-ruby1.9" as an alternative dependency is wrong in this
> case. (icbw though)

Facter will work with either ruby1.8 or ruby1.9, and its associated
libraries, but because ruby1.9 had not settled, we did not include a
potential depdency on 'ruby1.9'. You are right that its a little
strange, and probably removing libopenssl-ruby1.9 from the Depends would
resolve that.

A couple minor issues related to this, the changelog entry:

   * Add versioned dependency for ruby1.8 (Closes: #585867) 

is repeated twice in the upload that I did (oops), and the bug number is
wrong, it should be #545867. These are pretty minor, but I am happy to
fix them in an upload, if you would prefer?

micah


pgpu5awjz58X8.pgp
Description: PGP signature

Bug#607165: unblock: facter/1.5.7-2

[micah anderson]

On Thu, 23 Dec 2010 15:56:00 +0100, Mehdi Dogguy  wrote:
> On 17/12/2010 18:10, micah anderson wrote:
> >
> > Hi Mehdi,
> >
> >> I'm not decided yet if I'll unblock the package (because I didn't finish 
> >> the
> >> review yet) but I noticed something (that looks) odd (to me) in the Depends
> >> field. So, facter depends on:
> >>
> >>Depends: ruby1.8 (>= 1.8.7.72-3lenny1), net-tools, bind9-host | host,
> >> libopenssl-ruby1.8 | libopenssl-ruby1.9
> >>
> >> Why does it depend on "libopenssl-ruby1.8 | libopenssl-ruby1.9" when
> >> it has a strong dependency on ruby1.8? I tend to think that putting
> >> "libopenssl-ruby1.9" as an alternative dependency is wrong in this
> >> case. (icbw though)
> >
> > Facter will work with either ruby1.8 or ruby1.9, and its associated
> > libraries, but because ruby1.9 had not settled, we did not include a
> > potential depdency on 'ruby1.9'. You are right that its a little
> > strange, and probably removing libopenssl-ruby1.9 from the Depends would
> > resolve that.
> >
> 
> Please remove it.

Did it.

> 
> > A couple minor issues related to this, the changelog entry:
> >
> > * Add versioned dependency for ruby1.8 (Closes: #585867)
> >
> > is repeated twice in the upload that I did (oops), and the bug number is
> > wrong, it should be #545867. These are pretty minor, but I am happy to
> > fix them in an upload, if you would prefer?
> >
> 
> Go ahead.

Fixed up the changelog, and uploaded 1.5.7-3.

micah


pgp7MqPOsPACg.pgp
Description: PGP signature

Bug#607899: unblock: puppet/2.6.2-4

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Hi,

I'm sorry to keep bothering the release team, but there seems to be
one new issue that has come up in the puppet package that really
should be fixed for Squeeze, I really hope its the last.

Basically the puppet that is currently in Squeeze is supposed to
support a language feature called "parameterized classes", these are
in use by popular puppet modules, their usage is growing rapidly, and
is a documented language feature. Unfortunately, the version that we
have in Squeeze is broken in this regard, not supporting this is a
pretty big hit for the package in Squeeze, as the problems it uncovers
are non-trivial inheritance issues that are quite frustrating to
debug.

This is upstream bug #4534 [1] that was fixed in 2.6.3. We've got
2.6.2 in Squeeze, with various cherry-picked fixes from 2.6.3, but
this is one we are missing.

I've cherry-picked the fix for this[2], and it works well, not
exposing the bug any longer.

If I could bother you, hopefully one last time, to allow this fix into
Squeeze by doing an unblock puppet/2.6.2-4 it would be really
appreciated.

hopefully this will be the last you hear from me, thanks again!
Micah

  [1] https://projects.puppetlabs.com/issues/4534
  [2] 
https://projects.puppetlabs.com/projects/puppet/repository/revisions/65ef24e

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20101223213643.23504.72461.report...@algae.riseup.net

[Fwd: backupninja_0.9.4-5_i386.changes ACCEPTED]

[Micah Anderson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Please allow this package into etch as it fixes a RC bug, and has no
other changes. Danke.

micah

-  Original Message 
Subject: backupninja_0.9.4-5_i386.changes ACCEPTED
Date: Wed, 13 Dec 2006 06:02:02 +
From: Debian Installer <[EMAIL PROTECTED]>
To: Micah Anderson <[EMAIL PROTECTED]>


Accepted:
backupninja_0.9.4-5.diff.gz
  to pool/main/b/backupninja/backupninja_0.9.4-5.diff.gz
backupninja_0.9.4-5.dsc
  to pool/main/b/backupninja/backupninja_0.9.4-5.dsc
backupninja_0.9.4-5_all.deb
  to pool/main/b/backupninja/backupninja_0.9.4-5_all.deb


Override entries for your package:
backupninja_0.9.4-5.dsc - source admin
backupninja_0.9.4-5_all.deb - optional admin

Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 402679


Thank you for your contribution to Debian.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFgMQh9n4qXRzy1ioRAsOGAKCuCO0avXrrBrq4gmfMEq3st8+CrwCfYe6y
l6CVjrwSsT3/s+z2d7V/7qw=
=xvPk
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [Fwd: backupninja_0.9.4-5_i386.changes ACCEPTED]

[Micah Anderson]

Andreas Barth wrote:
> * Micah Anderson ([EMAIL PROTECTED]) [061214 04:39]:
>> Please allow this package into etch as it fixes a RC bug, and has no
>> other changes. Danke.
> 
> Hi,
> 
> did you just forgot to include the changelog from 0.9.4-4, or did you undo
> other changes as well?
> 
> Anyways, could you please upload a new version containing the full
> history (unless it was by purpose)?

It seems I got bitten by my local svn repository getting corrupted,
thank you for noticing this! I've uploaded a new version containing the
full history without the changes being undone. I used the same version
number as my previous upload (0.9.4-5), I presume that this is what I
should do, rather than increasing to -6?

Micah


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#783145: jessie-pu: package sqlcipher/3.2.0-1

[Micah Anderson]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hello!

It seems we missed the RC bug fix date, and now we are in the quiet
period. However, I have uploaded a NMU to unstable to fix #776987 so I
wanted to file a bug here, as was detailed in debian-devel-announce.

Please find attached the debdiff against the two source packages.

Micah


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru sqlcipher-3.2.0/debian/changelog sqlcipher-3.2.0/debian/changelog
--- sqlcipher-3.2.0/debian/changelog	2014-10-17 20:16:29.0 -0300
+++ sqlcipher-3.2.0/debian/changelog	2015-04-22 17:03:50.0 -0300
@@ -1,3 +1,11 @@
+sqlcipher (3.2.0-1.1) unstable; urgency=high
+
+  [ Ben Carrillo ]
+  * Non-maintainer upload.
+  * use a separate variable to track SQLCIPHER version (Closes: #776987)
+
+ -- Micah Anderson   Wed, 22 Apr 2015 10:38:05 -0400
+
 sqlcipher (3.2.0-1) unstable; urgency=low
 
   * updated to latest upstream: v3.2.0
diff -Nru sqlcipher-3.2.0/debian/patches/20-change-name-to-sqlcipher.patch sqlcipher-3.2.0/debian/patches/20-change-name-to-sqlcipher.patch
--- sqlcipher-3.2.0/debian/patches/20-change-name-to-sqlcipher.patch	2014-10-17 00:24:01.0 -0300
+++ sqlcipher-3.2.0/debian/patches/20-change-name-to-sqlcipher.patch	2015-04-22 17:03:50.0 -0300
@@ -1,7 +1,38 @@
 a/VERSION
-+++ b/VERSION
-@@ -1 +1 @@
--3.8.6
-\ No newline at end of file
+--- a/Makefile.in
 b/Makefile.in
+@@ -89,6 +89,7 @@ TCC += $(OPTS)
+ VERSION = @VERSION@
+ VERSION_NUMBER = @VERSION_NUMBER@
+ RELEASE = @RELEASE@
++SQLCIPHER_VERSION = @SQLCIPHER_VERSION@
+ 
+ # Filename extensions
+ #
+--- /dev/null
 b/VERSION_SQLCIPHER
+@@ -0,0 +1 @@
 +3.2.0
-\ No newline at end of file
+--- a/configure.ac
 b/configure.ac
+@@ -179,6 +179,10 @@ VERSION_NUMBER=[`cat $srcdir/VERSION \
+ AC_MSG_NOTICE(Version number set to $VERSION_NUMBER)
+ AC_SUBST(VERSION_NUMBER)
+ 
++SQLCIPHER_VERSION=[`cat $srcdir/VERSION_SQLCIPHER | sed 's/^\([0-9]*\.*[0-9]*\).*/\1/'`]
++AC_MSG_NOTICE(SQLCipher Version set to $SQLCIPHER_VERSION)
++AC_SUBST(SQLCIPHER_VERSION)
++
+ #
+ # Check to see if the --with-hints=FILE option is used.  If there is none,
+ # then check for a files named "$host.hints" and ../$hosts.hints where
+--- a/sqlcipher.pc.in
 b/sqlcipher.pc.in
+@@ -7,7 +7,7 @@ includedir=@includedir@
+ 
+ Name: SQLCipher
+ Description: SQL database engine
+-Version: @PACKAGE_VERSION@
++Version: @SQLCIPHER_VERSION@
+ Libs: -L${libdir} -lsqlcipher
+ Libs.private: @LIBS@
+ Cflags: -I${includedir}
diff -Nru sqlcipher-3.2.0/debian/patches/32-fix-pkgconfig-libname.patch sqlcipher-3.2.0/debian/patches/32-fix-pkgconfig-libname.patch
--- sqlcipher-3.2.0/debian/patches/32-fix-pkgconfig-libname.patch	2014-10-17 00:25:32.0 -0300
+++ sqlcipher-3.2.0/debian/patches/32-fix-pkgconfig-libname.patch	2015-04-22 17:03:50.0 -0300
@@ -1,7 +1,7 @@
 --- a/sqlcipher.pc.in
 +++ b/sqlcipher.pc.in
 @@ -10,4 +10,4 @@ Description: SQL database engine
- Version: @PACKAGE_VERSION@
+ Version: @SQLCIPHER_VERSION@
  Libs: -L${libdir} -lsqlcipher
  Libs.private: @LIBS@
 -Cflags: -I${includedir}

Bug#703999: RM: irssi-plugin-otr/0.3-2+b1

[Micah Anderson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

I would like to request the removal of the package irssi-plugin-otr, the reasons
being:

1. there is a +3 year outstanding security issue with emotes being sent in the
clear: #569506

2. there is an almost 3-year outstanding issue with dataloss due to regular and
frequent segfaults (bringing down all of irssi and all state) with it: #576696

3. i haven't bothered to file a bug about the awful memory leaks

4. none of the above are ever going to be resolved, based on upstream's
apparent abandoning of the code

5. there is a new irssi-plugin-otr that is about to be released, it is a
complete re-write that has none of these issues and is actually quite
stable. Having this broken one in wheezy forever is going to cause confusion and
unhappy upstream. I've discussed the state of the debian situation with them,
and they would like to have the existing one removed: #695150

It has the same version as in squeeze, and there has been no upload since 2009,
and has no r-deps.

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
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/20130326163059.15765.53516.report...@minnow.riseup.net