Am Mittwoch, den 12.06.2019, 14:02 +0800 schrieb Paul Wise:
> On Wed, Jun 12, 2019 at 1:21 AM Benjamin Drung wrote:
>
> > * I had to patch reprepro to support multiple versions:
> > https://github.com/profitbricks/reprepro
>
> I think it would be very helpful to a lot of derivative distros and
>
On Wed, 12 Jun 2019, Vincent Bernat wrote:
> It's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570623
>
> Maintainer doesn't seem to be interested or have no time to consider the
> patch since many years.
Another sticking point with reprepro is the lack of Acquire-by-hash
support:
❦ 12 juin 2019 14:02 +08, Paul Wise :
>> * I had to patch reprepro to support multiple versions:
>> https://github.com/profitbricks/reprepro
>
> I think it would be very helpful to a lot of derivative distros and
> small or private apt repositories if this patch could be merged
> upstream and
On Wed, Jun 12, 2019 at 1:21 AM Benjamin Drung wrote:
> * I had to patch reprepro to support multiple versions:
> https://github.com/profitbricks/reprepro
I think it would be very helpful to a lot of derivative distros and
small or private apt repositories if this patch could be merged
upstream
Hi,
Am Donnerstag, den 06.06.2019, 14:32 -0400 schrieb Kyle Edwards:
> Hello all,
>
> I have been preparing Ubuntu releases for CMake on our own APT
> repository for several months now. We did this by preparing our own
> repository infrastructure - we have a machine that builds packages,
> and
>
On 2019-06-10 13:09:52 -0400 (-0400), Kyle Edwards wrote:
> On Mon, 2019-06-10 at 16:56 +, Jeremy Stanley wrote:
[...]
> > 6. To allow for easier manual verification of key transitions,
> > always sign new keys with their predecessors when creating them.
>
> We haven't signed the new key at
On Mon, 2019-06-10 at 16:56 +, Jeremy Stanley wrote:
> 2. Don't place all your trust key revocation, instead plan a
> rotation schedule so that even if a key falls into the wrong hands
> it's more likely users will smell something fishy when they see it
> used to sign new artifacts after
On 2019-06-10 11:18:35 -0400 (-0400), Kyle Edwards wrote:
[...]
> If you're using GPG on the published repository, how does your
> repository server handle its signing GPG key? Does someone have to type
> in a password every time it wants to publish a package, or is it
> unattended, with either an
On Sat, 2019-06-08 at 02:25 +0200, Matthias Klumpp wrote:
> Am Do., 6. Juni 2019 um 20:33 Uhr schrieb Kyle Edwards
> :
> >
> >
> > Hello all,
> >
> > I have been preparing Ubuntu releases for CMake on our own APT
> > repository for several months now. We did this by preparing our own
> >
On Sat, 08 Jun 2019 at 02:25:44 +0200, Matthias Klumpp wrote:
> Am Do., 6. Juni 2019 um 20:33 Uhr schrieb Kyle Edwards
> :
> > 2. According to https://wiki.debian.org/BuilddSetup, there seems to be
> > a distinction between the build broker (wanna-build) and the build
> > workers (buildd). Do
Am Do., 6. Juni 2019 um 20:33 Uhr schrieb Kyle Edwards
:
>
> Hello all,
>
> I have been preparing Ubuntu releases for CMake on our own APT
> repository for several months now. We did this by preparing our own
> repository infrastructure - we have a machine that builds packages, and
> a machine
Hello all,
I have been preparing Ubuntu releases for CMake on our own APT
repository for several months now. We did this by preparing our own
repository infrastructure - we have a machine that builds packages, and
a machine that hosts an Aptly instance and pushes the repository to our
web server.
12 matches
Mail list logo
