#2545 Pagure over dist-git doesn't show diff of a commit
Opened 6 years ago by robert. Modified a year ago

In good old PkgDB times, a commit to rpms/<something> lead to an e-mail with a unified diff of the commit (or multiple e-mails for multiple commits when fast-forwarding). Since the switch to "Pagure over dist-git", there are just kind of "useless" e-mails now:

Date: Wed, 23 Aug 2017 22:09:12 +0000 (UTC)
From: pagure@pkgs.fedoraproject.org
Reply-To: reply+[…]@src.fedoraproject.org
To: […]@fedoraproject.org
Subject: [rpms/libburn1] New Commits To "rpms/libburn1" (epel7)
Message-Id: <[…]@bastion01.phx2.fedoraproject.org>
From pagure@pkgs.fedoraproject.org  Thu Aug 24 00:09:19 2017


The following commits were pushed to the repo "rpms/libburn1" on branch
"epel7", which you are following:
b6283ac646803133cc24ba75589fcb3a6f606013    Robert Scheck    Initial import



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/libburn1/commits/epel7

May I kindly request that you bring back the unified diff for e-mails again, please? At least optionally/configurable for users who would like to have that. It's a standard feature for similar systems like GitLab.


FMN should work as before, I am not sure this is related to pagure itself.

Note, this only affects newly created packages (since Pagure over dist-git) such as e.g. "libburn1", however not "libburn".

Could you forward me one of these emails (or paste it with headers and all) ?

@pingou this seems to be the email that Pagure sends when you chose to "watch commits" on a repo.

Could you forward me one of these emails (or paste it with headers and all) ?

From pagure@pkgs.fedoraproject.org  Fri Sep 15 01:21:05 2017
Return-Path: <pagure@pkgs.fedoraproject.org>
X-Spam-Level:
X-Spam-Status: No, score=-1.90 required=5.00 tests=BAYES_00,RP_MATCHES_RCVD
Received: from bastion.fedoraproject.org (bastion01.fedoraproject.org [209.132.181.2])
        by mail.linuxnetz.de (8.15.2/8.15.2) with ESMTPS id v8ENL1bk030065
        (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
        for <redhat@linuxnetz.de>; Fri, 15 Sep 2017 01:21:04 +0200
Received: by bastion01.phx2.fedoraproject.org (Postfix)
        id CDFF6618B8A1; Thu, 14 Sep 2017 23:21:00 +0000 (UTC)
Delivered-To: robert@fedoraproject.org
Received: from pkgs02.phx2.fedoraproject.org (pkgs02.phx2.fedoraproject.org [10.5.125.44])
        by bastion01.phx2.fedoraproject.org (Postfix) with ESMTP id B38B2606D3C4
        for <robert@fedoraproject.org>; Thu, 14 Sep 2017 23:21:00 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 bastion01.phx2.fedoraproject.org B38B2606D3C4
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Subject: [rpms/libburn1] New Commits To "rpms/libburn1" (epel7)
From: pagure@pkgs.fedoraproject.org
X-Auto-Response-Suppress: All
X-pagure: https://src.fedoraproject.org/
X-pagure-project: rpms/libburn1
List-ID: rpms/libburn1
List-Archive: https://src.fedoraproject.org/rpms/libburn1
To: robert@fedoraproject.org
Reply-To: reply+64a0a80d98566ea0590c0cf13326a5d2d82105a4f972b231ff66f9e9be55e34b2ab86ca6827981e3dc58b25194a854a1af8a07ea568589f6b50eab765501d050@src.fedoraproject.org
Mail-Followup-To: reply+64a0a80d98566ea0590c0cf13326a5d2d82105a4f972b231ff66f9e9be55e34b2ab86ca6827981e3dc58b25194a854a1af8a07ea568589f6b50eab765501d050@src.fedoraproject.org
Message-Id: <20170914232100.B38B2606D3C4@bastion01.phx2.fedoraproject.org>
Date: Thu, 14 Sep 2017 23:21:00 +0000 (UTC)
X-Scanned-By: MIMEDefang 2.81
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.linuxnetz.de id v8ENL1bk030065
Content-Length: 296
Lines: 9


The following commits were pushed to the repo "rpms/libburn1" on branch
"epel7", which you are following:
0e5113b0b904e8a5805a5a8d37b390f3e2d5755b    Robert Scheck    Upgrade to 1.4.8 (#1491478)



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/libburn1/commits/epel7

Metadata Update from @pingou:
- Issue tagged with: RFE, pkgs.fp

6 years ago

Ok, this is solved in the way that the emails are no longer sent (since it's FMN job to send them), but the underlying issue should still be fixed

Metadata Update from @wombelix:
- Issue set to the milestone: 6.0

a year ago

Login to comment on this ticket.

Metadata