On Tue, Jul 14, 2020 at 17:23, Pirate Praveen
wrote:
On Tue, Jul 14, 2020 at 13:57, Pirate Praveen
wrote:
I think rebuilding ruby-json with ruby 2.7 might fix it.
But now we need to update our build scripts to build with ruby 2.7.
On Tue, Jul 14, 2020 at 13:57, Pirate Praveen
wrote:
I think rebuilding ruby-json with ruby 2.7 might fix it.
But now we need to update our build scripts to build with ruby 2.7.
https://git.fosscommunity.in/praveen/debian-scripts/-/blob/master/sbuild-fto
was how we used to build
On Sun, Jul 12, 2020 at 18:05, Thorsten Glaser
wrote:
On Sun, 12 Jul 2020, Pirate Praveen wrote:
> It also looks like buster-fasttrack is not set up correctly:
> its policy value is 500, not 100 (NotAutomatic: yes and
> ButAutomaticUpgrades: yes).
That is because we don't really
On Sun, Jul 12, 2020 at 19:16, Jessica Clarke wrote:
On 12 Jul 2020, at 18:39, Pirate Praveen
wrote:
On Sun, Jul 12, 2020 at 21:50, Pirate Praveen
wrote:
Erm… I did add buster-backports, the official one.
You absolutely cannot have a thing called buster-backports on the
fasttrack
On Sun, 12 Jul 2020 15:23:28 +0200 (CEST) Thorsten Glaser
wrote:
> But the installability problem has a different cause:
>
> […]
> Depends: ruby-faraday (>= 0.17.3~) but 0.15.4-3~bpo10+1 is to be
> installed
> […]
> $ apt-cache policy ruby-faraday
> ruby-faraday:
> Installed:
On 12 Jul 2020, at 18:39, Pirate Praveen wrote:
> On Sun, Jul 12, 2020 at 21:50, Pirate Praveen
> wrote:
>>> Erm… I did add buster-backports, the official one.
>>> You absolutely cannot have a thing called buster-backports on the
>>> fasttrack server because that’s too easily confused with the
On Sun, Jul 12, 2020 at 21:50, Pirate Praveen
wrote:
Erm… I did add buster-backports, the official one.
You absolutely cannot have a thing called buster-backports on the
fasttrack server because that’s too easily confused with the
official one.
Let me think about it.
Usually with the
On Sun, Jul 12, 2020 at 18:05, Thorsten Glaser
wrote:
On Sun, 12 Jul 2020, Pirate Praveen wrote:
> It also looks like buster-fasttrack is not set up correctly:
> its policy value is 500, not 100 (NotAutomatic: yes and
> ButAutomaticUpgrades: yes).
That is because we don't really
On Sun, 12 Jul 2020, Pirate Praveen wrote:
> > It also looks like buster-fasttrack is not set up correctly:
> > its policy value is 500, not 100 (NotAutomatic: yes and
> > ButAutomaticUpgrades: yes).
>
> That is because we don't really expect the packages to be upgradable to next
> stable
On Sun, Jul 12, 2020 at 15:23, Thorsten Glaser
wrote:
On Sun, 12 Jul 2020, Pirate Praveen wrote:
But gitlab is not in buster-backports
Then I don’t understand the problem.
gitlab is in buster-fasttrack, but buster-fasttrack is not self
contained, it needs buster-backports.
On Sun, 12 Jul 2020, Pirate Praveen wrote:
> But gitlab is not in buster-backports
Then I don’t understand the problem.
> apt/aptitude -t buster-backports install gitlab/buster-fasttrack does not
> work.
Why?
apt-get install gitlab/buster-fasttrack even should work,
in that case.
11 matches
Mail list logo
