>>> repoman would be more useful for this
>> I wouldn't stop pkgcheck from supporting this, but repoman should as
>> well.
>>
>>
>>
> of course, that's what i meant ;)
Looks like it does now,
https://bugs.gentoo.org/702100
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bb5d7b074164ceae
On Fri, 06 Dec 2019 10:03:23 +0100
Alexis Ballier wrote:
> (*) and force the use of some handy git options like only commit paths
> starting from cwd even if other files had been git added, which i never
> remember what is the git cli option for this
There isn't so much a CLI option, more, there
On Fri, 6 Dec 2019 12:58:47 -0500
Michael Orlitzky wrote:
> $ git rebase -i
>
> to do a rebase starting at the one you'd like to fix.
Or, if you know the hash of the faulty commit, you can do:
$ git rebase -i DEADBEEF^1
( 1st parent of commit DEADBEEF )
Which absolves you from needin
On 12/6/19 11:29 AM, Alexis Ballier wrote:
>
> Without good integration from the checker it is probably a PITA to
> figure out that 23 too
If you're reading through your commit log and if you see something
wrong, you can
$ git rebase -i
to do a rebase starting at the one you'd like to fix.
On 06/12/19 16:28, Mike Gilbert wrote:
> On Fri, Dec 6, 2019 at 10:46 AM Michael 'veremitz' Everitt
> wrote:
>> I hope you're not suggesting a rebase of any sort in gentoo.git, Matt ;)
> He's talking about rebasing local commits that haven't yet been
> pushed. That's perfectly normal.
>
Fair
On Fri, Dec 6, 2019 at 10:46 AM Michael 'veremitz' Everitt
wrote:
> I hope you're not suggesting a rebase of any sort in gentoo.git, Matt ;)
He's talking about rebasing local commits that haven't yet been
pushed. That's perfectly normal.
On Fri, 6 Dec 2019 10:41:56 -0500
Matt Turner wrote:
> On Fri, Dec 6, 2019 at 5:51 AM Alexis Ballier
> wrote:
> >
> > On Fri, 6 Dec 2019 04:33:36 -0500
> > Tim Harder wrote:
> >
> > > On 2019-12-06 Fri 04:03, Alexis Ballier wrote:
> > > > it's not just like repoman and cvs since repoman commit
On 06/12/19 15:41, Matt Turner wrote:
> On Fri, Dec 6, 2019 at 5:51 AM Alexis Ballier wrote:
>> On Fri, 6 Dec 2019 04:33:36 -0500
>> Tim Harder wrote:
>>
>>> On 2019-12-06 Fri 04:03, Alexis Ballier wrote:
it's not just like repoman and cvs since repoman commit did push ;)
it will never
On Fri, Dec 6, 2019 at 5:51 AM Alexis Ballier wrote:
>
> On Fri, 6 Dec 2019 04:33:36 -0500
> Tim Harder wrote:
>
> > On 2019-12-06 Fri 04:03, Alexis Ballier wrote:
> > > it's not just like repoman and cvs since repoman commit did push ;)
> > > it will never be perfect but i really like repoman co
On 2019-12-06 Fri 06:33, Michał Górny wrote:
> If you need something convenient to commit, app-portage/mgorny-dev-
> scripts has pkgcommit tool which does the only useful part of what
> repoman did -- that is, prepends package name to the commit message.
> For pre-push checks, I use the following
On Fri, 2019-12-06 at 03:23 -0500, Tim Harder wrote:
> On 2019-12-05 Thu 17:00, Alexis Ballier wrote:
> > > > pkgcheck is mostly used by your CI checks for
> > > > producing huge reports, which is nice but addresses a different
> > > > problem
> > > There is nothing stopping you from running pkgche
On Fri, 6 Dec 2019 04:33:36 -0500
Tim Harder wrote:
> On 2019-12-06 Fri 04:03, Alexis Ballier wrote:
> > it's not just like repoman and cvs since repoman commit did push ;)
> > it will never be perfect but i really like repoman commit to refuse
> > to even commit if there's something obviously wr
On 2019-12-06 Fri 04:03, Alexis Ballier wrote:
> it's not just like repoman and cvs since repoman commit did push ;)
> it will never be perfect but i really like repoman commit to refuse to
> even commit if there's something obviously wrong
I'm more of the opinion (and am working towards that prac
On Fri, 2019-12-06 at 03:23 -0500, Tim Harder wrote:
> On 2019-12-05 Thu 17:00, Alexis Ballier wrote:
> > > > pkgcheck is mostly used by your CI checks for
> > > > producing huge reports, which is nice but addresses a different
> > > > problem
> > > There is nothing stopping you from running pkgche
On 2019-12-05 Thu 17:00, Alexis Ballier wrote:
> > > pkgcheck is mostly used by your CI checks for
> > > producing huge reports, which is nice but addresses a different
> > > problem
> > There is nothing stopping you from running pkgcheck locally. In
> > fact,
> > it should work out of the box the
On 2019-12-06 Fri 02:15, Michał Górny wrote:
> > I think that is not an apt description in my understanding of your original
> > post on the matter. The package.deprecated file is supposed to contain not
> > just (qualified) package names, but some sort of package dependency
> > specifications (
On Fri, 2019-12-06 at 01:36 +0100, Chí-Thanh Christopher Nguyễn wrote:
> Michał Górny schrieb:
> > +
> > +#
> > +# This file specifies packages that are considered deprecated
>
> I think that is not an apt description in my unders
Michał Górny schrieb:
+
+#
+# This file specifies packages that are considered deprecated
I think that is not an apt description in my understanding of your original
post on the matter. The package.deprecated file is supposed
On Thu, Dec 05, 2019 at 05:09:57PM +0100, Michał Górny wrote:
> Signed-off-by: Michał Górny
> ---
> profiles/package.deprecated | 17 +
> 1 file changed, 17 insertions(+)
> create mode 100644 profiles/package.deprecated
>
> diff --git a/profiles/package.deprecated b/profiles/pac
On Thu, 2019-12-05 at 19:04 +0100, Michał Górny wrote:
> On Thu, 2019-12-05 at 18:59 +0100, Alexis Ballier wrote:
> > On Thu, 2019-12-05 at 18:39 +0100, Michał Górny wrote:
> > > On Thu, 2019-12-05 at 17:36 +0100, Alexis Ballier wrote:
> > > > On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
Am Donnerstag, 5. Dezember 2019, 19:04:50 CET schrieb Michał Górny:
> On Thu, 2019-12-05 at 18:59 +0100, Alexis Ballier wrote:
> > unless i missed something, repoman is still the standard for pre-commit
> > checks and raising everyone's attention on potential
> > improvements/issues;
>
> Nope. P
On Thu, Dec 5, 2019 at 8:10 AM Michał Górny wrote:
> Signed-off-by: Michał Górny
> ---
> profiles/package.deprecated | 17 +
> 1 file changed, 17 insertions(+)
> create mode 100644 profiles/package.deprecated
>
>
This looks great Michał, thanks for putting it together.
-A
>
On Thu, 2019-12-05 at 18:59 +0100, Alexis Ballier wrote:
> On Thu, 2019-12-05 at 18:39 +0100, Michał Górny wrote:
> > On Thu, 2019-12-05 at 17:36 +0100, Alexis Ballier wrote:
> > > On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
> > > > +##
On Thu, 2019-12-05 at 18:39 +0100, Michał Górny wrote:
> On Thu, 2019-12-05 at 17:36 +0100, Alexis Ballier wrote:
> > On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
> > > +
> > >
> > > +#
> > > +# This file specifies packa
+1
5 декабря 2019 г. 19:09:57 GMT+03:00, "Michał Górny" пишет:
>Signed-off-by: Michał Górny
>---
> profiles/package.deprecated | 17 +
> 1 file changed, 17 insertions(+)
> create mode 100644 profiles/package.deprecated
>
>diff --git a/profiles/package.deprecated b/profiles/package
On Thu, 2019-12-05 at 17:36 +0100, Alexis Ballier wrote:
> On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
> > +
> > +#
> > +# This file specifies packages that are considered deprecated (but
> > not
> > +# masked yet). It
On Thu, 2019-12-05 at 10:53 -0600, William Hubbs wrote:
> On Thu, Dec 05, 2019 at 05:36:58PM +0100, Alexis Ballier wrote:
> > On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
> > > +
> > >
> > > +#
> > > +# This file specifi
On Thu, Dec 05, 2019 at 05:36:58PM +0100, Alexis Ballier wrote:
> On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
> > +
> > +#
> > +# This file specifies packages that are considered deprecated (but
> > not
> > +# masked yet
On Thu, Dec 5, 2019 at 11:10 AM Michał Górny wrote:
>
> Signed-off-by: Michał Górny
> ---
> profiles/package.deprecated | 17 +
> 1 file changed, 17 insertions(+)
> create mode 100644 profiles/package.deprecated
>
> diff --git a/profiles/package.deprecated b/profiles/package.dep
Am Donnerstag, 5. Dezember 2019, 17:09:57 CET schrieb Michał Górny:
[...]
> +# This file specifies packages that are considered deprecated (but not
> +# masked yet). It will trigger pkgcheck warnings whenever other
> +# packages depend on them.
Just saying, this is an awesome functionality, and w
On Thu, 2019-12-05 at 17:09 +0100, Michał Górny wrote:
> +
> +#
> +# This file specifies packages that are considered deprecated (but
> not
> +# masked yet). It will trigger pkgcheck warnings whenever other
> +# packages depend on
Signed-off-by: Michał Górny
---
profiles/package.deprecated | 17 +
1 file changed, 17 insertions(+)
create mode 100644 profiles/package.deprecated
diff --git a/profiles/package.deprecated b/profiles/package.deprecated
new file mode 100644
index ..b4803a4ce68f
--- /d
32 matches
Mail list logo
