On Sun, Mar 11, 2018 at 3:58 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Mar 11, 2018 at 02:22:49PM -0400, Nico Kadel-Garcia wrote:
>> On Sun, Mar 11, 2018 at 2:21 PM, Nico Kadel-Garcia wrote:
>> > On Sun, Mar 11, 2018 at 10:25 AM, Zbigniew Jędrzejewski-Szmek
>> > wrote:
>> >> On Sun, Mar 1
On Sun, Mar 11, 2018 at 02:22:49PM -0400, Nico Kadel-Garcia wrote:
> On Sun, Mar 11, 2018 at 2:21 PM, Nico Kadel-Garcia wrote:
> > On Sun, Mar 11, 2018 at 10:25 AM, Zbigniew Jędrzejewski-Szmek
> > wrote:
> >> On Sun, Mar 11, 2018 at 10:04:25AM -0400, Neal Gompa wrote:
> >>> On Sun, Mar 11, 2018 a
On Sun, Mar 11, 2018 at 10:25 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Mar 11, 2018 at 10:04:25AM -0400, Neal Gompa wrote:
>> On Sun, Mar 11, 2018 at 10:01 AM, Zbigniew Jędrzejewski-Szmek
>> wrote:
>> > I wanted to submit a PR for this, but I wasn't sure what the proper
>> > location is.
On Sun, Mar 11, 2018 at 2:21 PM, Nico Kadel-Garcia wrote:
> On Sun, Mar 11, 2018 at 10:25 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
>> On Sun, Mar 11, 2018 at 10:04:25AM -0400, Neal Gompa wrote:
>>> On Sun, Mar 11, 2018 at 10:01 AM, Zbigniew Jędrzejewski-Szmek
>>> wrote:
>
>>> > I wanted to submi
On Sun, Mar 11, 2018 at 10:04:25AM -0400, Neal Gompa wrote:
> On Sun, Mar 11, 2018 at 10:01 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Tue, Feb 13, 2018 at 08:18:20AM -0500, Neal Gompa wrote:
> >> On Tue, Feb 13, 2018 at 8:08 AM, Randy Barlow
> >> wrote:
> >> > On 02/12/2018 08:00 PM, Michal
On Sun, Mar 11, 2018 at 10:01 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, Feb 13, 2018 at 08:18:20AM -0500, Neal Gompa wrote:
>> On Tue, Feb 13, 2018 at 8:08 AM, Randy Barlow
>> wrote:
>> > On 02/12/2018 08:00 PM, Michal Schorm wrote:
>> >> The changelogs are long ass hell.
>> >> What about
On Tue, Feb 13, 2018 at 08:18:20AM -0500, Neal Gompa wrote:
> On Tue, Feb 13, 2018 at 8:08 AM, Randy Barlow
> wrote:
> > On 02/12/2018 08:00 PM, Michal Schorm wrote:
> >> The changelogs are long ass hell.
> >> What about keeping just 2 latest releases in it and deleting the rest?
> >> (It will be
Hello,
On Fri, Feb 9, 2018 at 10:57 PM, Michal Novotny wrote:
> Hello,
>
> On Fri, Feb 9, 2018 at 3:22 PM, Panu Matilainen
> wrote:
>
>> On 02/09/2018 03:34 PM, Josh Boyer wrote:
>>
>>> On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller
>>> wrote:
>>>
On Thu, Feb 08, 2018 at 05:02:10PM +0100,
On Fri, 2018-02-09 at 11:05 +0100, Vít Ondruch wrote:
> Dne 9.2.2018 v 09:21 Kevin Kofler napsal(a):
> > Matthew Miller wrote:
> > > Second, there's package maintainer changelogs. These are really
> > > redundant with the dist-git log. We don't really need this
> > > anymore.
> > > It's just a chor
On Wed, Feb 14, 2018 at 10:00:18AM +0100, nicolas.mail...@laposte.net wrote:
> Actually, the problem is we're all talking about changelogs, when users ask
> for release notes.
> That's not exactly the same thing.
Yes! Thanks, that puts nicely what I'm trying to say. Right now, the
git log is basi
On Tue, 2018-02-13 at 12:07 -0800, Adam Williamson wrote:
> On Mon, 2018-02-12 at 11:59 -0500, David Cantrell wrote:
> > The dist-git changelogs are mostly noise and I would prefer better
> > organized information about impacts to users and developers. Like
> > tell
> > me what things changed in t
On Tue, 2018-02-13 at 15:33 -0500, Josh Boyer wrote:
>
> The point is, we have LOTS of places where change information or
> discussion occurs. We should try and have a canonical location for
> the *descriptive summary* of these changes/discussions.
This hit home. Way back in the early 90s when
Hi,
Actually, the problem is we're all talking about changelogs, when users ask for
release notes.
That's not exactly the same thing.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Tue, 2018-02-13 at 12:07 -0800, Adam Williamson wrote:
> On Mon, 2018-02-12 at 11:59 -0500, David Cantrell wrote:
> > The dist-git changelogs are mostly noise and I would prefer better
> > organized information about impacts to users and developers. Like
> > tell
> > me what things changed in t
On Tue, Feb 13, 2018 at 3:24 PM, Matthew Miller
wrote:
> On Tue, Feb 13, 2018 at 12:07:27PM -0800, Adam Williamson wrote:
>> > The dist-git changelogs are mostly noise and I would prefer better
>> > organized information about impacts to users and developers. Like tell
>> > me what things changed
On Tue, Feb 13, 2018 at 12:07:27PM -0800, Adam Williamson wrote:
> > The dist-git changelogs are mostly noise and I would prefer better
> > organized information about impacts to users and developers. Like tell
> > me what things changed in the new glibc package, not that the glibc RPM
> > has bee
On Mon, 2018-02-12 at 11:59 -0500, David Cantrell wrote:
> The dist-git changelogs are mostly noise and I would prefer better
> organized information about impacts to users and developers. Like tell
> me what things changed in the new glibc package, not that the glibc RPM
> has been upgraded to th
On Tue, Feb 13, 2018 at 08:18:20AM -0500, Neal Gompa wrote:
> On Tue, Feb 13, 2018 at 8:08 AM, Randy Barlow
> wrote:
> > On 02/12/2018 08:00 PM, Michal Schorm wrote:
> >> The changelogs are long ass hell.
> >> What about keeping just 2 latest releases in it and deleting the rest?
> >> (It will be
On Tue, Feb 13, 2018 at 8:08 AM, Randy Barlow
wrote:
> On 02/12/2018 08:00 PM, Michal Schorm wrote:
>> The changelogs are long ass hell.
>> What about keeping just 2 latest releases in it and deleting the rest?
>> (It will be still kept in GIT history)
>> 2 releases could be 2-
>
> I usually trim
On 02/12/2018 08:00 PM, Michal Schorm wrote:
> The changelogs are long ass hell.
> What about keeping just 2 latest releases in it and deleting the rest?
> (It will be still kept in GIT history)
> 2 releases could be 2-
I usually trim my changelogs to the last year of entries. It's kinda
arbitrary
On Sat, Feb 10, 2018 at 10:25:48PM +0100, David Sommerseth wrote:
> I personally find it abusing shared resources throwing builds at it which has
> not been tested first. So I prefer to do local mockbuilds first, simply to
> lessen the load on shared resources. I'm not saying I haven't tossed fa
On Monday, February 12, 2018 5:59:57 PM CET David Cantrell wrote:
> On 02/09/2018 08:34 AM, Josh Boyer wrote:
> > On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller
> > wrote:
> >> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
> >>> It seems that a lot of people have %file, %check, %
On Tue, Feb 13, 2018 at 3:03 AM, J. Randall Owens <
jrowens.fed...@ghiapet.net> wrote:
>
> When you say 2 releases, are you talking about package or Fedora
> releases? I'd favour an approach of keeping all the changes since
> release, or since branching might be even better, or since the release
>
On 13/02/18 01:00, Michal Schorm wrote:
> 5)
> The changelogs are long ass hell.
> What about keeping just 2 latest releases in it and deleting the rest?
> (It will be still kept in GIT history)
> 2 releases could be 2-20 entries, depends of work done.
> But still it looks short enough for me.
Whe
I don't think, removing the changelog entirely is a good idea. We do not
have suitable replacement.
1)
I agree with said. GIT commit messages should describe the work of
developer.
Thus messages like "typo fix" "revert of revert of merge of ..." "forgot to
add new-sources" are common, and should s
On 02/09/2018 08:34 AM, Josh Boyer wrote:
> On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller
> wrote:
>> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
>>> It seems that a lot of people have %file, %check, %build, %whatsoever
>>> in their changelog section.
>>> Is there any reason I
On Fri, Feb 09, 2018 at 08:34:02AM -0500, Josh Boyer wrote:
> > Wherever it lives, this would be read by Bodhi, so there's
> > would be need to enter it more than once. And, perhaps a DNF plugin
> > could be made to read and display this information for systems
> > administrators.
>
> I fully supp
On Fri, Feb 09, 2018 at 08:12:43AM +0100, Igor Gnatenko wrote:
> * Many times people put some useless messages in there, so we
> probably don't want to convert old history to git-based changelogs
> and have point where we ask people to start writing useful commit
> messages.
There are lots of usel
On Thu, 8 Feb 2018 18:39:19 +0100, Petr Stodulka wrote:
> > The following:
> > %files
> > /some/directory/
> >
> > is equivalent to:
> > %files
> > %dir /some/directory
> > /some/directory/*
> >
> >
> > There's nothing wrong here.
> >
> >
>
> Exactly. IMHO, use of %dir macro for "top" pkg
On Thu, 8 Feb 2018 18:09:25 +, Tomasz Kłoczko wrote:
> I'm sure that in the past it was difference here :|
You are mistaken about that.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
On 10/02/18 12:54, Kevin Kofler wrote:
> David Sommerseth wrote:
>> I doubt Koji was primarily built for "does this work?"-builds. It exists
>> to build proper packages targeting Fedora repositories.
>
> But that is the point, to build a proper package:
>
> do {
> try build;
> } while (!build
I must agree with Kevin that taking every single commit message and putting
it into changelog without further tweaking
might just produce lots of redundant and not really desired lines in the
output. But I think something still can be done.
When you invoke `rpkg tag` (the same goes for `fedpkg tag`
David Sommerseth wrote:
> I doubt Koji was primarily built for "does this work?"-builds. It exists
> to build proper packages targeting Fedora repositories.
But that is the point, to build a proper package:
do {
try build;
} while (!build succeeded);
and the output is a working package.
> To
On 09/02/18 23:46, Kevin Kofler wrote:
> David Sommerseth wrote:
>> Doesn't 'fedpkg mockbuild' resolve those test builds? To my knowledge,
>> this is fairly close to what koji does under the hood. Then you'll have
>> everything tested locally, git tree can be cleaned up and be in a
>> reasonable
David Sommerseth wrote:
> Doesn't 'fedpkg mockbuild' resolve those test builds? To my knowledge,
> this is fairly close to what koji does under the hood. Then you'll have
> everything tested locally, git tree can be cleaned up and be in a
> reasonable shape before being pushed out.
I'm surely no
On 09/02/18 23:09, Kevin Kofler wrote:
> Kamil Dudka wrote:
>> Would not it be then better to work on this in a staging branch and rework
>> those commits before they are pushed to a production branch? I am myself
>> not interested in going through commits like "fix a typo", "forgot to bump
>> rel
Neal Gompa wrote:
> Mageia, OpenMandriva, and PLD all generate their changelogs from the
> source control system.
[snip]
> SUSE uses the Open Build Service VCS export to changes files which are
> converted into changelog entries at package build time.
All these distros have in common that their ch
Kamil Dudka wrote:
> Would not it be then better to work on this in a staging branch and rework
> those commits before they are pushed to a production branch? I am myself
> not interested in going through commits like "fix a typo", "forgot to bump
> release", "add missing BR", "revert the previous
Hello,
On Fri, Feb 9, 2018 at 3:22 PM, Panu Matilainen wrote:
> On 02/09/2018 03:34 PM, Josh Boyer wrote:
>
>> On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller
>> wrote:
>>
>>> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
>>>
It seems that a lot of people have %file, %check
On 09/02/18 16:53 +, Jonathan Wakely wrote:
On 09/02/18 08:34 -0500, Josh Boyer wrote:
Someone else suggested changelogs could be inserted during koji build
time. That would be interesting to look into.
If a koji build page just showed the Git commit logs since the last
build that could b
On 09/02/18 08:34 -0500, Josh Boyer wrote:
Someone else suggested changelogs could be inserted during koji build
time. That would be interesting to look into.
If a koji build page just showed the Git commit logs since the last
build that could be far more useful than showing hundreds of lines
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2018-02-08 at 13:32 -0500, Matthew Miller wrote:
> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
> > It seems that a lot of people have %file, %check, %build, %whatsoever
> > in their changelog section.
> > Is there any reaso
On Fri, Feb 9, 2018 at 9:22 AM, Panu Matilainen wrote:
>
>
> Koji, or fedpkg, or better yet some hook in rpm itself. It's not exactly
> rocket science we're talking about here if people are ready to give it a go.
>
> Neal, doesn't Mageia (and Mandriva) pull package changelogs from SCM
> already? D
On 02/09/2018 03:34 PM, Josh Boyer wrote:
On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller wrote:
On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
It seems that a lot of people have %file, %check, %build, %whatsoever
in their changelog section.
Is there any reason I should not go a
On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller wrote:
> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
>> It seems that a lot of people have %file, %check, %build, %whatsoever
>> in their changelog section.
>> Is there any reason I should not go and automatically escape them?
>
> T
Dne 9.2.2018 v 09:21 Kevin Kofler napsal(a):
> Matthew Miller wrote:
>> Second, there's package maintainer changelogs. These are really
>> redundant with the dist-git log. We don't really need this anymore.
>> It's just a chore.
> My %changelog entries are not identical to the dist-git commit mess
On Friday, February 9, 2018 9:21:27 AM CET Kevin Kofler wrote:
> Matthew Miller wrote:
>
> > Second, there's package maintainer changelogs. These are really
> > redundant with the dist-git log. We don't really need this anymore.
> > It's just a chore.
>
>
> My %changelog entries are not identica
On Friday, February 9, 2018 9:25:33 AM CET Igor Gnatenko wrote:
> On Fri, 2018-02-09 at 08:57 +0100, Pavel Raiskup wrote:
> > On Thursday, February 8, 2018 5:02:10 PM CET Igor Gnatenko wrote:
> > > Hello everyone,
> > >
> > > It seems that a lot of people have %file, %check, %build, %whatsoever in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2018-02-09 at 08:57 +0100, Pavel Raiskup wrote:
> On Thursday, February 8, 2018 5:02:10 PM CET Igor Gnatenko wrote:
> > Hello everyone,
> >
> > It seems that a lot of people have %file, %check, %build, %whatsoever in
> > their
> > changelog
De: "Przemek Klosowski"
Hi,
> Many environments (corporate, government) actually require keeping track
> of this stuff, so addressing it would help the acceptance of Fedora and
> Redhat in such environments
Then have Koji or Bohdi insert accurate changelogs at build time. Can't be less
reliab
Matthew Miller wrote:
> Second, there's package maintainer changelogs. These are really
> redundant with the dist-git log. We don't really need this anymore.
> It's just a chore.
My %changelog entries are not identical to the dist-git commit messages:
1. It often takes me several git commits to m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've went and fixed 493 packages (listed below). If it broke something, please
let me know. I checked diff briefly and don't think that I broke anything…
Maintainers by package:
389-console mreynolds nhosoi nkinder rmeggins
389-ds-base
On Thursday, February 8, 2018 5:02:10 PM CET Igor Gnatenko wrote:
> Hello everyone,
>
> It seems that a lot of people have %file, %check, %build, %whatsoever in their
> changelog section.
>
> Is there any reason I should not go and automatically escape them?
There's IMO no good reason why you sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2018-02-08 at 13:32 -0500, Matthew Miller wrote:
> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
> > It seems that a lot of people have %file, %check, %build, %whatsoever
> > in their changelog section.
> > Is there any reaso
On 02/08/2018 05:02 PM, Igor Gnatenko wrote:
> Hello everyone,
>
> It seems that a lot of people have %file, %check, %build, %whatsoever
> in their
> changelog section.
>
> Is there any reason I should not go and automatically escape them?
>
> %check → %%check
> %build → %%build
> %whatsoever → %%w
On 2018-02-08, 18:32 GMT, Matthew Miller wrote:
> This seems like a lot of churn. If we're going to do this,
> let's go big and get rid of RPM changelogs.
+1
Matej
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
How f
On 02/08/2018 01:32 PM, Matthew Miller wrote:
This seems like a lot of churn. If we're going to do this, let's go big
and get rid of RPM changelogs.
When we have a package update, there are basically two different kinds
of changelog information. Well, three.
[...]
Third, though, there's end-user
On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
> It seems that a lot of people have %file, %check, %build, %whatsoever
> in their changelog section.
> Is there any reason I should not go and automatically escape them?
This seems like a lot of churn. If we're going to do this, let's
On 8 February 2018 at 17:39, Petr Stodulka wrote:
[..]
> > There's nothing wrong here.
> >
> >
>
> Exactly. IMHO, use of %dir macro for "top" pkg directories is more clean
> solution, but
> doesn't matter in case the rpm is packaged correctly.
>
I'm sure that in the past it was difference here :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2018-02-08 at 16:56 +, Tomasz Kłoczko wrote:
> BTW some massively occurring errors in really big number Fedora of specs.
>
> Looks like many people don't know that %files entry like:
>
> /some/directory/
>
> does not include /some/dire
On 8.2.2018 18:33, Neal Gompa wrote:
> On Thu, Feb 8, 2018 at 11:56 AM, Tomasz Kłoczko
> wrote:
>> BTW some massively occurring errors in really big number Fedora of specs.
>>
>> Looks like many people don't know that %files entry like:
>>
>> /some/directory/
>>
>> does not include /some/directo
On Thu, Feb 8, 2018 at 11:56 AM, Tomasz Kłoczko
wrote:
> BTW some massively occurring errors in really big number Fedora of specs.
>
> Looks like many people don't know that %files entry like:
>
> /some/directory/
>
> does not include /some/directory into package but all files and
> subdirectories
On Thu, Feb 8, 2018 at 9:56 AM, Tomasz Kłoczko wrote:
> Looks like many people don't know that %files entry like:
>
> /some/directory/
>
> does not include /some/directory into package but all files and
> subdirectories which are in /some/directory.
That is incorrect. For example, the polyml spe
BTW some massively occurring errors in really big number Fedora of specs.
Looks like many people don't know that %files entry like:
/some/directory/
does not include /some/directory into package but all files and
subdirectories which are in /some/directory.
This is in how many specs such lines
Igor Gnatenko wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello everyone,
>
> It seems that a lot of people have %file, %check, %build, %whatsoever in
> their changelog section.
>
> Is there any reason I should not go and automatically escape them?
>
> %check → %%check
> %bu
On Thu, 2018-02-08 at 16:20 +, Sérgio Basto wrote:
> On Thu, 2018-02-08 at 17:02 +0100, Igor Gnatenko wrote:
> > Hello everyone,
> >
> > It seems that a lot of people have %file, %check, %build,
> > %whatsoever
> > in their
> > changelog section.
> >
> > Is there any reason I should not go an
On Thu, 2018-02-08 at 17:02 +0100, Igor Gnatenko wrote:
> Hello everyone,
>
> It seems that a lot of people have %file, %check, %build, %whatsoever
> in their
> changelog section.
>
> Is there any reason I should not go and automatically escape them?
>
> %check → %%check
> %build → %%build
> %wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello everyone,
It seems that a lot of people have %file, %check, %build, %whatsoever in their
changelog section.
Is there any reason I should not go and automatically escape them?
%check → %%check
%build → %%build
%whatsoever → %%whatsoever
Ther
68 matches
Mail list logo
