Package: salt
Version: 3004.1+dfsg-2.2
As I no longer use Salt or have regular access to a debian system, I am
unable to continue as an uploader/maintainer for the salt packages. This
has been the case for some time and is unlikely to change.
As such, please remove me from the uploaders for the
On Tue, Nov 3, 2015 at 10:19 PM, Benjamin Drung <
benjamin.dr...@profitbricks.com> wrote:
>
> After having commit access, the only remaining thing is to add me to
> the uploaders list in debian/control (which I could do myself).
>
>
Could you please do this? I'm going to be unable to do so for
Hi Ben,
On Fri, Oct 30, 2015 at 10:54 PM, Benjamin Drung <
benjamin.dr...@profitbricks.com> wrote:
>
> There were no progress recently. So I decided to go ahead and prepare
> an update to 2015.8.1. This includes adding a salt-proxy package,
> requiring python-crypto >= 2.6 and dropping
On Tue, Nov 3, 2015 at 11:17 PM, Benjamin Drung <
benjamin.dr...@profitbricks.com> wrote:
> Hi Joe,
>
> I pushed the current state. May you review these changes?
>
Those changes all look good.
I understand the rationale for removing the "Debian Source Package" from
the reproducible builds
Hi Ben,
I don't currently have access to an unstable machine - part way through
renovating and also suffering from a hardware failure. I expect to get
access the week after next, but until then, I will be fairly limited.
Are you able to help?
Thanks,
Joe
On Fri, Oct 9, 2015 at 11:23 PM, Benjamin Drung <
benjamin.dr...@profitbricks.com> wrote:
> Am Freitag, den 09.10.2015, 22:54 +1100 schrieb Joe Healy:
>
> I can help. Do you only need help to build and test it or also at doing
> the update?
>
Thinking about it, I should be
Thanks for reporting this.
I haven't ever used the api server so I'm not too sure. I am keen to fix
the issue though.
I suspect some configuration may be required - I would try asking on the
salt mailing list or IRC as I believe people have been using it
successfully.
I'll have a chance to look
Package: salt
Version: 2015.5.2+ds-1
Severity: important
bsdmainutils is required (cols) to parse the output of systemctl
If this is missing, then systemd service management fails.
This also applies to ubuntu 15.04+
-- System Information:
Debian Release: 7.5
APT prefers oldstable
APT
Thanks for sending this through.
I'm currently waiting on salt 2014.7.2 to progress through the NEW queue. I
suspect the best course of action now is to prepare a 2014.7.4 for a
sponsor to upload to the NEW queue and wait for its transition. I
guess/hope that the security issue is likely to mean
Hi Ben,
On Wed, Feb 11, 2015 at 9:18 PM, Benjamin Drung
benjamin.dr...@profitbricks.com wrote:
I'll make these changes. You are partially right - I/we do need a
sponsor, but I haven't asked for one yet as I want to make sure the
latest addition to the packaging (salt-api) is ok
Tags: + patch
I've attached a patch for a direct fix.
I'm delaying applying it for 24-48 hours until I hear from upstream if
salt-common should require python-msgpack or not.
A fair bit of the code implies python-msgpack should not be needed for
local (ie salt-call) use.
Joe
diff --git
Thanks very much for this Ben,
I'll make these changes. You are partially right - I/we do need a sponsor,
but I haven't asked for one yet as I want to make sure the latest addition
to the packaging (salt-api) is ok before I do (hence the -3...).
I suspect the latest version is fine and ready for
On Wed, Feb 11, 2015 at 9:18 PM, Benjamin Drung
benjamin.dr...@profitbricks.com wrote:
PS: Are you aware of the lintian warnings 'script-not-executable' [1].
Is the deploy directory needed in the package?
At least some of it is needed for salt-cloud. The bootstrap
script [1] is copied to
On Wed, Feb 11, 2015 at 8:43 PM, Benjamin Drung
benjamin.dr...@profitbricks.com wrote:
A patch against your master branch is attached.
debian/patches/make-log-file-group-readable.patch is a backport of the
patch
that was accepted upstream (in their develop branch).
Should this also be
)
* [6a17bb9] Added patch to prevent crash when unicode text is output from
salt
(Closes: 770909)
-- Joe Healy joehe...@gmail.com Thu, 27 Nov 2014 15:49:13 +1100
The debdiff is:
joe@debian-sid:~/jessie_freeze$ debdiff ~/2014.1.13/salt_2014.1.13+ds-
1_amd64.changes ./salt_2014.1.13+ds-2_amd64
Package: salt
Version: 2014.7.0+ds-2
Severity: normal
A new dependency has been added. This is not required for all operation, but is
required if the scheduler is to be used.
It should probably be added as either recommends, maybe to just the master
See:
Thanks Julien,
I'll apply this fix and upload tonight. I'll also look at the other fixes
made upstream on the 2014.1 branch.
Joe
On Wed, Nov 19, 2014 at 10:43 PM, Julien Cristau julien.cris...@logilab.fr
wrote:
Package: salt-common
Version: 2014.1.13+ds-1
Severity: grave
Tags: patch
Package: salt
Version: 2014.1.13+ds-1
Severity: normal
Dear Maintainer,
When a unicode character appears in the output of a command or a diff of a
file, then salt command crashes
* What led up to the situation?
Changing a file with a unicode character on the same line or running a command
On Thu, Sep 11, 2014 at 6:19 AM, Leo Antunes cost...@debian.org wrote:
Is there still time to upload the new upstream version before the freeze?
2014.7 has 40 new modules and 33 new states (judging by the diffs), so it
might be interesting to have it in jessie.
2014.7 is still only in
Yes, It can, I'll close it off.
Thanks,
Joe
On Jun 17, 2014 8:06 PM, Marcin Kulisz deb...@kulisz.net wrote:
Looks like in jessie and sid we already have python-libcloud_0.14.1-1, so
this
issue should go.
--
|_|0|_| |
|_|_|0| Heghlu'Meh
and means that any
side effects due to including pyobject can be isolated.
[1] https://groups.google.com/forum/#!topic/salt-users/97SwtpsoDvM
Cheers,
Joe
On Mon, May 26, 2014 at 12:03 PM, Joe Healy joehe...@gmail.com wrote:
I'm investigating how intrusive a patch would be.
For reference
I'm investigating how intrusive a patch would be.
For reference, the pull request that removed it is:
https://github.com/saltstack/salt/pull/11682
Joe
On Mon, May 26, 2014 at 8:07 AM, gustavo panizzo gfa g...@zumbi.com.arwrote:
Package: salt-common
Version: 2014.1.4+ds-2
Severity: normal
Upstream have made a fix, so I'll do a new release to fix this shortly.
https://github.com/saltstack/salt/commit/de4d823b9afdbd1f96735a796a3ecee295b3dcda
Thanks for the report.
https://github.com/saltstack/salt/issues/12766
I've submitted this bug upstream and will follow to see when it is resolved.
In the mean time, I'll have a quick look to see if i can patch the issue,
otherwise I'll look at depending on python-zmq.
Thanks,
Joe
Looks like this is an upstream bug.
I'm passing it upstream with some additional comments.
https://github.com/saltstack/salt/issues/11525
I think if you add:
ssh_user: root
to your /etc/salt/master config file, then it will work. You may also need
some similar options.
Thanks,
Joe
On
Package: salt-cloud
Version: 2014.1.0+ds-1
Severity: grave
Justification: renders package unusable
* What led up to the situation?
Running salt-cloud gives the following exception:
# salt-cloud
Traceback (most recent call last):
File /usr/bin/salt-cloud, line 10, in module
Had an unexpectedly busy couple of weeks.
Just finalising backports for 2014.1 and 17.5 now.
Apologies for the delay.
Joe
On Mon, Mar 3, 2014 at 10:34 PM, Julien Cristau
julien.cris...@logilab.frwrote:
On Sun, Feb 16, 2014 at 23:39:25 +1100, Joe Healy wrote:
Hi Avinash,
Now
Hi Avinash,
Now that 0.17.5+ds has reached testing, I am intending to backport this to
wheezy (and squeeze). I'm planning to do this over the next day or two.
Thanks,
Joe
On Fri, Feb 14, 2014 at 7:53 PM, Avinash Sultanpur avinas...@yukthi.comwrote:
Package: salt-minion
Version:
I'll add the override - that is trivial.
With the modernizr*.min.js file, the source is in
modernizr.custom.20463.jshttps://github.com/saltstack/salt/blob/develop/doc/_themes/saltstack/static/js/vendor/modernizr.custom.20463.js.
I'll get upstream to rename it for future releases and do a ds
That version was from me - hosted at debian.saltstack.com until I was
able to do an official backport. It should be identical.
I should remove it as the official backports are now available.
I'm happy to prepare the backport - though I can't remember if I can upload.
Thanks for cc'ing me.
Joe
On Sun, Dec 1, 2013 at 3:22 AM, Andreas Beckmann a...@debian.org wrote:
msgpack-python has changed its name to python-msgpack.
Even if the new package Provides: msgpack-python this does not seem to
be sufficient to allow automatic removal of the old package from the
archive.
Will do. What is
On Sat, Nov 30, 2013 at 4:44 PM, Ben Finney ben+deb...@benfinney.id.au wrote:
Package: salt-common
Version: 0.17.1+dfsg-1
Severity: minor
Administrating Salt requires understanding how it works and what it does.
Please set a “Suggests: salt-doc” dependency, so that administrators
choosing
Thanks for picking this up. A new upstream release is due shortly.
I'll fix this at the same time.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thu, Oct 24, 2013 at 9:38 AM, Andrii Senkovych
jolly_ro...@itblog.org.ua wrote:
Also asking Salt team if it's ok for me to maintain this library under
team Maintainership if such decision is made.
My understanding is that removal of m2crypto is an open issue for salt
upstream [1].
Whilst
On Mon, Oct 21, 2013 at 06:01:58AM -0400, Luke Faraone wrote:
Yes. If you don't want to modify the upstream tarball this is then the
recommended approach.
Thanks Luke, it turns out I need to modify the upstream tarball as
there are non DFSG files (fonts) in there.
So I'll remove these files
https://github.com/saltstack/salt/pull/7356/files
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thanks for picking these up and apologies for letting them through.
On Thu, Oct 10, 2013 at 08:05:18PM -0400, Luke Faraone wrote:
Please document
../doc/_themes/saltstack/static/css/bootstrap-responsive.css in
debian/copyright.
Will do.
Please also recreate the minified versions during
Package: ftp.debian.org
Severity: normal
Package has changed priority due to a reassessment and looking at
dependencies.
Same change to salt-master, salt-common and salt-syndic.
Smilar change to salt-doc. It should go to salt-doc:doc/extra
I think these overrides could actually be removed.
Package: salt-minion
Version: 0.16.3-1
Severity: normal
Since I refactored the init script for salt-minion to ensure that all
processes were killed off, salt is no longer able to upgrade itself.
Running:
salt '*' pkg.install salt-minion
will result in the minion (and the dpkg) process being
On Wed, Sep 11, 2013 at 4:51 PM, martin f krafft madd...@debian.org wrote:
also sprach Joe Healy joehe...@gmail.com [2013.09.11.0815 +0200]:
Running:
salt '*' pkg.install salt-minion
will result in the minion (and the dpkg) process being killed part
way through the upgrade and requiring
Package: python-zmq
Severity: minor
Dear Maintainer,
The current version in unstable has a build dependency on cython (= 0.13).
The source actually requires cython = 0.16 to build.
Thanks.
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500,
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Comment: Add Joe Healy joehe...@gmail.com as a Debian Maintainer
Date: Sun
Thanks Michael,
I'll include this on the next upload. We've just missed the last one.
We are looking to backport salt to squeeze and wheezy, is there
anything we need to consider or do we just remove the build dependency
on dh-systemd?
Cheers,
Joe
--
To UNSUBSCRIBE, email to
On Thu, Jun 20, 2013 at 4:36 AM, Michael Nelson
absoludity+deb...@gmail.com wrote:
Package: salt
Version: 0.15.1-1
Severity: important
Tags: upstream
Dear Maintainer,
* What led up to the situation?
I was using salt-minion from the salt PPA which is version 0.15.3, and
everything was
Looks like upstream have accepted your patch.
https://github.com/saltstack/salt/commit/404b769d25ee5158398c46cc62ff9ce4ab85f06c
Do I close this one now or when the next release is made?
Thanks,
Joe
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Having thought about it for awhile, I think a feasible design is
coming together:
We change via quilt the default config file location. This will deal
with new installations.
To deal with existing installations, we write a script which does the
following in postinst:
We read the
Franklin,
On Wed, Apr 10, 2013 at 5:13 AM, Franklin G. Mendoza
franklin.g.mend...@gmail.com wrote:
I think we can use quilt (as you write) and move the location to
/var/lib/salt/
[1] https://github.com/saltstack/salt/issues/3396
If you need help, well... we can do it together.
I think
Hi Martin,
I'm relatively new to this game so I just want to make sure I
understand your bug.
Please correct me if I am wrong.
Salt has recently updated the way it checks for systemd.
The way salt is doing so is incorrect and the appropriate way to do so
is in the patch.
This patch is not
Hi,
Is it appropriate to set the default config to a
/var/lib/salt/{master,minion}/pki location?
If so, I guess this would be done via a quilt patch.
People who are using package managed versions would need to be
notified, but the number of those should be small at this stage.
Thanks,
Joe
Package: yaird
Version: 0.0.12-3
Followup-For: Bug #345374
I have tried using the patch and some of the config options
(adding/moving ide-generic, etc) with no luck.
I get the same error as Roman Kalukiewicz [EMAIL PROTECTED]. Currently back
running 2.4 kernel, DMA works here.
I have added
50 matches
Mail list logo
