On 07/09/2015 06:32 AM, Andrei Borzenkov wrote:
> On Thu, Jul 9, 2015 at 12:43 PM, Armin K. wrote:
>> > Now, this might be an issue with my limited git knowledge, but
>> > I don't think that's related to the web interface not showing
>> > the commits in the correct order between two release tags.
On 07/09/2015 09:28 AM, Armin K. wrote:
> On 09.07.2015 12:32, Andrei Borzenkov wrote:
>> I clicked on release link and it downloaded file with name
>> systemd-222.tar.gz. I see that there could be an issue with dumb cli
>> clients not following redirections probably.
>>
>
> I suppose it's a gith
On 09.07.2015 12:32, Andrei Borzenkov wrote:
> On Thu, Jul 9, 2015 at 12:43 PM, Armin K. wrote:
>> So, my first question is: How do I get around this? Is there any
>> sane way of me knowing which exactly commits happened between
>> two release tags from the web interface? If not, is there any
>> o
On 09.07.2015 15:17, Martin Pitt wrote:
> Armin K. [2015-07-09 14:42 +0200]:
>> Still, man pages and html docs issue exists.
>
> That's by design. They are built from the docbook sources.
>
> Martin
>
Some new design? Previously, make dist would bundle the built sources
into distribution tarbal
Armin K. [2015-07-09 14:42 +0200]:
> Still, man pages and html docs issue exists.
That's by design. They are built from the docbook sources.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.as
Hi
2015-07-09 14:17 GMT+02:00 Armin K. :
> a is systemd-221 from fd.o, b is systemd-222 generated by make dist.
>
> TL;DR - files used to build the compat libs are missing even though
> --enable-compat libs was specified on ./configure line before
> make dist was built.
You need to run "make" bef
On 09.07.2015 14:17, Armin K. wrote:
> On 09.07.2015 13:44, Kay Sievers wrote:
>> On Thu, Jul 9, 2015 at 11:43 AM, Armin K. wrote:
>>
>>> I discovered a commit 2c8849add40805256156a36d7ef8c54cf019e29e
>>> by Kay Sievers which literally broke the make dist
>>> target. A lot of += were removed, maki
On 09.07.2015 13:44, Kay Sievers wrote:
> On Thu, Jul 9, 2015 at 11:43 AM, Armin K. wrote:
>
>> I discovered a commit 2c8849add40805256156a36d7ef8c54cf019e29e
>> by Kay Sievers which literally broke the make dist
>> target. A lot of += were removed, making a target that appears
>> more than once
On Thu, Jul 9, 2015 at 11:43 AM, Armin K. wrote:
> I discovered a commit 2c8849add40805256156a36d7ef8c54cf019e29e
> by Kay Sievers which literally broke the make dist
> target. A lot of += were removed, making a target that appears
> more than once redefine itself each time instead of appending
>
On Thu, Jul 9, 2015 at 12:43 PM, Armin K. wrote:
> Now, this might be an issue with my limited git knowledge, but
> I don't think that's related to the web interface not showing
> the commits in the correct order between two release tags.
>
Recently there was discussion about completely screwed u
10 matches
Mail list logo