On 23/07/16 01:07, Ferenc Wágner wrote:
>> - Can I push the backport branches to the repositories in [1]?
>
> Yes, please do so. Please discuss the necessary changes on our mailing
> list beforehand, I'd like to keep the delta small.
>
>> - What should the changelog entry look like? "Backport
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thank you very much for your review Gianfranco. :)
On 10/08/16 11:31, Gianfranco Costamagna wrote:
> 1) really? what about don't care to wheezy anymore?
What do you mean? Should backports only be done for jessie now?
Here is the backstory: we
main/x/xml-security-c/xml-securit
y-c_1.7.3-3~bpo7+1.dsc
More information about xml-security-c can be obtained from
http://santuario.apache.org/cindex.html.
Changes since the last upload (wheezy 1.6.1-5+deb7u2):
xml-security-c (1.7.3-3~bpo7+1) wheezy-backports-sloppy; urgency=medium
.
[ Etienne Dy
Thank you Alex :)
On 22/07/16 13:16, Alexander Wirt wrote:
>> - Can I push the backport branches to the repositories in [1]?
> The backports team doesn't care about the git, you will have to ask the other
> maintainers.
Ok
>> - What should the changelog entry look like? "Backport to "?
> That
On 22/07/16 14:15, Alexander Wirt wrote:
>> And the distribution field should be the backport target
>> (jessie-backports-sloppy), right?
> Depends on your backport. The one that matches to your backport. And
> jessie-backports-sloppy is in every case wrong at this point in time.
Ah right, yes!
Hello mentors,
I would like to backport Shibboleth packages [1] to jessie and wheezy.
- What branch name should I use?
Documentation for git-buildpackage [2] says "debian/" so that
would yield "debian/jessie-backports-sloppy", but I've seen
"backports/" earlier so I'm unsure.
- Can I push the
On 21/01/17 09:32, Ferenc Wágner wrote:
> Shall I upload the backport, or do you plan to add anything else?
Yes, please upload it. :) I updated the debian/jessie-backports branch
with the contents of the package on mentors.
Etienne
signature.asc
Description: OpenPGP digital signature
On 17/01/17 18:30, Niels Thykier wrote:
>>> E: libshibsp7: postinst-must-call-ldconfig
>>> usr/lib/x86_64-linux-gnu/libshibsp.so.7.0.0
>
> This lintian error:
>
> * is aimed at stretch or later, and
> * should be ignored for stable and stable-backports
Thanks Niels! :)
That's a bit strange
Hello mentors,
Since shibboleth-sp2 2.6.0+dfsg1-4 migrated to testing during the
holidays, I'm now backporting it to jessie. So far there is nothing to
change, however piuparts gives me the following error (which does not
appear on stretch):
> 0m34.6s ERROR: FAIL: Package purging left files on
On 17/01/17 18:30, Niels Thykier wrote:
>>> E: libshibsp7: postinst-must-call-ldconfig
>>> usr/lib/x86_64-linux-gnu/libshibsp.so.7.0.0
>
> This lintian error:
>
> * is aimed at stretch or later, and
> * should be ignored for stable and stable-backports
After having overridden this lintian
On 20/01/17 12:31, Ferenc Wágner wrote:
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html says:
>
> The postrm script is called after the package's files have been
> removed or replaced. The package whose postrm is being called may
> have previously been
On 19/01/17 23:46, Ferenc Wágner wrote:
> I couldn't reproduce this on a real jessie system, only in a piuparts
> chroot. I think the reason is that piuparts removes init-system-helpers
> (the home of deb-systemd-helper) before the shibboleth-sp2-utils postrm
> could instruct it to clean up. I'm
On 21/03/18 12:58, Mattia Rizzolo wrote:
> Like I said in my first post¹, just to fulfil my curiosity.
> As an admin of mentors.d.n (and as a chronically lazy person) I'm
> curious as to why anybody would go to the extra length of using a local
> configuration when both dput and dput-ng ship with
On 14/08/2019 21.15, Colin Sullivan wrote:
> Would you be willing to provide some guidance and sponsor us?
Hello Colin,
As a prospective user of NATS, I'd welcome its inclusion in Debian. :)
Have you already contacted the Debian Go Packaging team? [1] They can
probably help you prepare your
On 27/08/2019 22.43, Colin Sullivan wrote:
> Soft ping... Would you be willing to provide some guidance and
> sponsor us?
Hello Colin,
Are you subscribed to the mailing-list? Below is what I replied two
weeks ago. You'll also find another reply in the list archive. [3]
As a prospective user
15 matches
Mail list logo
