Backports Archive on lore.kernel.org
 help / Atom feed
* New release after 1.0.7?
@ 2018-08-14 13:09 Luciano Coelho
  2018-08-14 13:19 ` [Cocci] " Julia Lawall
  0 siblings, 1 reply; 16+ messages in thread
From: Luciano Coelho @ 2018-08-14 13:09 UTC (permalink / raw)
  To: cocci; +Cc: backports

Hi,

Is there a plan for a new release after 1.0.7? 1.0.7 was not tagged and
no tarballs were released, so I'm not sure what is the status of it. 
Additionally, I've had problems compiling it, and bisected it to this
commit:

commit 7ab8f01b63d7cdec988e5f05065f3c18fdab7319 (refs/bisect/bad)
Author:     Thierry Martinez <thierry.martinez@inria.fr>
AuthorDate: Wed Jun 20 15:46:18 2018 +0200
Commit:     Thierry Martinez <thierry.martinez@inria.fr>
CommitDate: Wed Jun 20 15:46:18 2018 +0200

    Allow bytecode compilation for pyml/generate
    
    This change generalizes a patch submitted by
      Christopher Zimmermann <chrisz@openbsd.org>
    for allowing pyml/generate to be compiled by ocamlc if ocamlopt
    is not available.
    
    The rules are adapted from pyml-current/Makefile.

Nevertheless, the compilation problem I had seems to be fixed in the
latest master (commit 97695d059cd5).

We (in the Linux backports project) have made a change to support the
new attributes style[1], which was supposed to work with 1.0.6, but
that seems to be broken too.

We don't want to revert to using the pre-1.0.6 versions, so we are
waiting for new release to choose for our project.  So, my question
again, can we expect a new stable release any time soon?

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/commit/?id=98272f479c2126a135dfcb12484e93d5888164ab

--
Cheers,
Luca.
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-14 13:09 New release after 1.0.7? Luciano Coelho
@ 2018-08-14 13:19 ` " Julia Lawall
  2018-08-14 13:32   ` Luciano Coelho
  2018-09-10  7:24   ` [Cocci] New release after 1.0.7? Johannes Berg
  0 siblings, 2 replies; 16+ messages in thread
From: Julia Lawall @ 2018-08-14 13:19 UTC (permalink / raw)
  To: Luciano Coelho; +Cc: cocci, backports



On Tue, 14 Aug 2018, Luciano Coelho wrote:

> Hi,
>
> Is there a plan for a new release after 1.0.7? 1.0.7 was not tagged and
> no tarballs were released, so I'm not sure what is the status of it.
> Additionally, I've had problems compiling it, and bisected it to this
> commit:
>
> commit 7ab8f01b63d7cdec988e5f05065f3c18fdab7319 (refs/bisect/bad)
> Author:     Thierry Martinez <thierry.martinez@inria.fr>
> AuthorDate: Wed Jun 20 15:46:18 2018 +0200
> Commit:     Thierry Martinez <thierry.martinez@inria.fr>
> CommitDate: Wed Jun 20 15:46:18 2018 +0200
>
>     Allow bytecode compilation for pyml/generate
>
>     This change generalizes a patch submitted by
>       Christopher Zimmermann <chrisz@openbsd.org>
>     for allowing pyml/generate to be compiled by ocamlc if ocamlopt
>     is not available.
>
>     The rules are adapted from pyml-current/Makefile.
>
> Nevertheless, the compilation problem I had seems to be fixed in the
> latest master (commit 97695d059cd5).
>
> We (in the Linux backports project) have made a change to support the
> new attributes style[1], which was supposed to work with 1.0.6, but
> that seems to be broken too.
>
> We don't want to revert to using the pre-1.0.6 versions, so we are
> waiting for new release to choose for our project.  So, my question
> again, can we expect a new stable release any time soon?

Sorry, I'm not sure where 1.0.7 came from.  I think that the compilation
issues should not be resolved, although if someone still sees problems
with the github version please report them.  I'm surprised that the
attributes have degraded, since I don't recall a change with respect to
that recently.  Could you send a .c and .cocci file that shows the
problem?

I would indeed like to make a release now that the compiations issues are
resolved and things seem more stable.

julia


>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/commit/?id=98272f479c2126a135dfcb12484e93d5888164ab
>
> --
> Cheers,
> Luca.
> _______________________________________________
> Cocci mailing list
> Cocci@systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-14 13:19 ` [Cocci] " Julia Lawall
@ 2018-08-14 13:32   ` Luciano Coelho
  2018-08-14 13:43     ` Julia Lawall
       [not found]     ` <b417bf64-7970-8482-0246-ab00129b4657@users.sourceforge.net>
  2018-09-10  7:24   ` [Cocci] New release after 1.0.7? Johannes Berg
  1 sibling, 2 replies; 16+ messages in thread
From: Luciano Coelho @ 2018-08-14 13:32 UTC (permalink / raw)
  To: Julia Lawall; +Cc: cocci, backports

Hi Julia,

Thanks for the quick response!

On Tue, 2018-08-14 at 15:19 +0200, Julia Lawall wrote:
> 
> On Tue, 14 Aug 2018, Luciano Coelho wrote:
> 
> > Hi,
> > 
> > Is there a plan for a new release after 1.0.7? 1.0.7 was not tagged
> > and
> > no tarballs were released, so I'm not sure what is the status of
> > it.
> > Additionally, I've had problems compiling it, and bisected it to
> > this
> > commit:
> > 
> > commit 7ab8f01b63d7cdec988e5f05065f3c18fdab7319 (refs/bisect/bad)
> > Author:     Thierry Martinez <thierry.martinez@inria.fr>
> > AuthorDate: Wed Jun 20 15:46:18 2018 +0200
> > Commit:     Thierry Martinez <thierry.martinez@inria.fr>
> > CommitDate: Wed Jun 20 15:46:18 2018 +0200
> > 
> >     Allow bytecode compilation for pyml/generate
> > 
> >     This change generalizes a patch submitted by
> >       Christopher Zimmermann <chrisz@openbsd.org>
> >     for allowing pyml/generate to be compiled by ocamlc if ocamlopt
> >     is not available.
> > 
> >     The rules are adapted from pyml-current/Makefile.
> > 
> > Nevertheless, the compilation problem I had seems to be fixed in
> > the
> > latest master (commit 97695d059cd5).
> > 
> > We (in the Linux backports project) have made a change to support
> > the
> > new attributes style[1], which was supposed to work with 1.0.6, but
> > that seems to be broken too.
> > 
> > We don't want to revert to using the pre-1.0.6 versions, so we are
> > waiting for new release to choose for our project.  So, my question
> > again, can we expect a new stable release any time soon?
> 
> Sorry, I'm not sure where 1.0.7 came from.

This is the version bump in the git repo:

commit c1522bde1ffff0ba8b977fd1e9bd259635ef6a3a
Author:     Thierry Martinez <thierry.martinez@inria.fr>
AuthorDate: Wed Jul 4 16:06:35 2018 +0200
Commit:     Thierry Martinez <thierry.martinez@inria.fr>
CommitDate: Wed Jul 4 16:57:00 2018 +0200

    Release 1.0.7



>   I think that the compilation
> issues should not be resolved, although if someone still sees
> problems
> with the github version please report them.  I'm surprised that the
> attributes have degraded, since I don't recall a change with respect
> to
> that recently.  Could you send a .c and .cocci file that shows the
> problem?

I'm not sure it's a regression, but I just couldn't get the attributes
to work with 1.0.6 either with and without Johannes' changes to upgrade
it to the 1.0.6 syntax.

This is the cocci that doesn't work (which is supposed to work with
1.0.6):

https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/tree/patches/0027-genl-const/genl-const.cocci

And, IIRC, this is the file that it's supposed to alter:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/wireless/nl80211.c

> I would indeed like to make a release now that the compiations issues
> are
> resolved and things seem more stable.

Sounds good! :)

--
Cheers,
Luca.
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-14 13:32   ` Luciano Coelho
@ 2018-08-14 13:43     ` Julia Lawall
  2018-08-14 14:39       ` Luciano Coelho
       [not found]     ` <b417bf64-7970-8482-0246-ab00129b4657@users.sourceforge.net>
  1 sibling, 1 reply; 16+ messages in thread
From: Julia Lawall @ 2018-08-14 13:43 UTC (permalink / raw)
  To: Luciano Coelho; +Cc: cocci, backports

> I'm not sure it's a regression, but I just couldn't get the attributes
> to work with 1.0.6 either with and without Johannes' changes to upgrade
> it to the 1.0.6 syntax.
>
> This is the cocci that doesn't work (which is supposed to work with
> 1.0.6):
>
> https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/tree/patches/0027-genl-const/genl-const.cocci
>
> And, IIRC, this is the file that it's supposed to alter:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/wireless/nl80211.c

With the current version, I get the diff below.  Is it what you expect?

julia

--- nl80211.c
+++ /tmp/cocci-output-11687-71a383-nl80211.c
@@ -48,7 +48,7 @@ enum nl80211_multicast_groups {
 	NL80211_MCGRP_TESTMODE /* keep last - ifdef! */
 };

-static const struct genl_multicast_group nl80211_mcgrps[] = {
+static __genl_const struct genl_multicast_group nl80211_mcgrps[] = {
 	[NL80211_MCGRP_CONFIG] = { .name = NL80211_MULTICAST_GROUP_CONFIG },
 	[NL80211_MCGRP_SCAN] = { .name = NL80211_MULTICAST_GROUP_SCAN },
 	[NL80211_MCGRP_REGULATORY] = { .name = NL80211_MULTICAST_GROUP_REG },
@@ -12894,7 +12894,8 @@ static int nl80211_tx_control_port(struc
 					 NL80211_FLAG_CHECK_NETDEV_UP)
 #define NL80211_FLAG_CLEAR_SKB		0x20

-static int nl80211_pre_doit(const struct genl_ops *ops, struct sk_buff *skb,
+static int nl80211_pre_doit(__genl_const struct genl_ops *ops,
+			    struct sk_buff *skb,
 			    struct genl_info *info)
 {
 	struct cfg80211_registered_device *rdev;
@@ -12956,7 +12957,8 @@ static int nl80211_pre_doit(const struct
 	return 0;
 }

-static void nl80211_post_doit(const struct genl_ops *ops, struct sk_buff *skb,
+static void nl80211_post_doit(__genl_const struct genl_ops *ops,
+			      struct sk_buff *skb,
 			      struct genl_info *info)
 {
 	if (info->user_ptr[1]) {
@@ -12985,7 +12987,7 @@ static void nl80211_post_doit(const stru
 	}
 }

-static const struct genl_ops nl80211_ops[] = {
+static __genl_const struct genl_ops nl80211_ops[] = {
 	{
 		.cmd = NL80211_CMD_GET_WIPHY,
 		.doit = nl80211_get_wiphy,
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-14 13:43     ` Julia Lawall
@ 2018-08-14 14:39       ` Luciano Coelho
  2018-08-16  7:05         ` Johannes Berg
  0 siblings, 1 reply; 16+ messages in thread
From: Luciano Coelho @ 2018-08-14 14:39 UTC (permalink / raw)
  To: Julia Lawall; +Cc: cocci, backports

On Tue, 2018-08-14 at 15:43 +0200, Julia Lawall wrote:
> > I'm not sure it's a regression, but I just couldn't get the
> > attributes
> > to work with 1.0.6 either with and without Johannes' changes to
> > upgrade
> > it to the 1.0.6 syntax.
> > 
> > This is the cocci that doesn't work (which is supposed to work with
> > 1.0.6):
> > 
> > 
https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/tree/patches/0027-genl-const/genl-const.cocci
> > 
> > And, IIRC, this is the file that it's supposed to alter:
> > 
> > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/wireless/nl80211.c
> 
> With the current version, I get the diff below.  Is it what you
> expect?
> 
> julia
> 
> --- nl80211.c
> +++ /tmp/cocci-output-11687-71a383-nl80211.c
> @@ -48,7 +48,7 @@ enum nl80211_multicast_groups {
>  	NL80211_MCGRP_TESTMODE /* keep last - ifdef! */
>  };
> 
> -static const struct genl_multicast_group nl80211_mcgrps[] = {
> +static __genl_const struct genl_multicast_group nl80211_mcgrps[] = {
>  	[NL80211_MCGRP_CONFIG] = { .name =
> NL80211_MULTICAST_GROUP_CONFIG },
>  	[NL80211_MCGRP_SCAN] = { .name = NL80211_MULTICAST_GROUP_SCAN
> },
>  	[NL80211_MCGRP_REGULATORY] = { .name =
> NL80211_MULTICAST_GROUP_REG },
> @@ -12894,7 +12894,8 @@ static int nl80211_tx_control_port(struc
>  					 NL80211_FLAG_CHECK_NETDEV_UP)
>  #define NL80211_FLAG_CLEAR_SKB		0x20
> 
> -static int nl80211_pre_doit(const struct genl_ops *ops, struct
> sk_buff *skb,
> +static int nl80211_pre_doit(__genl_const struct genl_ops *ops,
> +			    struct sk_buff *skb,
>  			    struct genl_info *info)
>  {
>  	struct cfg80211_registered_device *rdev;
> @@ -12956,7 +12957,8 @@ static int nl80211_pre_doit(const struct
>  	return 0;
>  }
> 
> -static void nl80211_post_doit(const struct genl_ops *ops, struct
> sk_buff *skb,
> +static void nl80211_post_doit(__genl_const struct genl_ops *ops,
> +			      struct sk_buff *skb,
>  			      struct genl_info *info)
>  {
>  	if (info->user_ptr[1]) {
> @@ -12985,7 +12987,7 @@ static void nl80211_post_doit(const stru
>  	}
>  }
> 
> -static const struct genl_ops nl80211_ops[] = {
> +static __genl_const struct genl_ops nl80211_ops[] = {
>  	{
>  		.cmd = NL80211_CMD_GET_WIPHY,
>  		.doit = nl80211_get_wiphy,

Yes, this looks right! So it seems to be working with 1.0.8. :P

Thanks a lot for checking and helping here.

--
Cheers,
Luca.

--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] Adjustment for const qualification
       [not found]       ` <alpine.DEB.2.20.1808151127520.2309@hadrien>
@ 2018-08-16  5:45         ` SF Markus Elfring
  0 siblings, 0 replies; 16+ messages in thread
From: SF Markus Elfring @ 2018-08-16  5:45 UTC (permalink / raw)
  To: Julia Lawall; +Cc: Luciano Coelho, cocci, backports

> This is rejected by the semantic patch parser.

The software version “Coccinelle 1.0.7-00472-g99fc302b” accepts the following
SmPL script variant.

@replacement@
attribute name __genl_const;
@@
-const
+__genl_const
 struct
(genl_multicast_group
|genl_ops
)


Would it be nice if such a transformation approach can work also without
the specified metavariable?
https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/tree/patches/0027-genl-const/genl-const.cocci?id=694b78f1533eb72c638c83754e0567630a93f456

Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-14 14:39       ` Luciano Coelho
@ 2018-08-16  7:05         ` Johannes Berg
  2018-08-16  7:09           ` Luciano Coelho
  0 siblings, 1 reply; 16+ messages in thread
From: Johannes Berg @ 2018-08-16  7:05 UTC (permalink / raw)
  To: Luciano Coelho, Julia Lawall; +Cc: cocci, backports

On Tue, 2018-08-14 at 17:39 +0300, Luciano Coelho wrote:
> 
> Yes, this looks right! So it seems to be working with 1.0.8. :P

There is no 1.0.8 though.

Julia, can you clear up the confusion with 1.0.7 and perhaps make a
1.0.8 release? Right now, there's only a very old (1.0.4 I think)
release that can do this at all, but it isn't compatible with the
current syntax. We'd like to have a release that has this ability so we
can check for the (minimum) version.

Thanks,
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-16  7:05         ` Johannes Berg
@ 2018-08-16  7:09           ` Luciano Coelho
  0 siblings, 0 replies; 16+ messages in thread
From: Luciano Coelho @ 2018-08-16  7:09 UTC (permalink / raw)
  To: Johannes Berg, Julia Lawall; +Cc: cocci, backports

On Thu, 2018-08-16 at 09:05 +0200, Johannes Berg wrote:
> On Tue, 2018-08-14 at 17:39 +0300, Luciano Coelho wrote:
> > 
> > Yes, this looks right! So it seems to be working with 1.0.8. :P
> 
> There is no 1.0.8 though.

I know, I was just hinting that what works now should be released as
1.0.8. ;)


--
Luca.
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-08-14 13:19 ` [Cocci] " Julia Lawall
  2018-08-14 13:32   ` Luciano Coelho
@ 2018-09-10  7:24   ` Johannes Berg
  2018-09-10 10:43     ` Julia Lawall
  2018-09-12 10:14     ` Julia Lawall
  1 sibling, 2 replies; 16+ messages in thread
From: Johannes Berg @ 2018-09-10  7:24 UTC (permalink / raw)
  To: Julia Lawall, Luciano Coelho; +Cc: cocci, backports

Julia,

On Tue, 2018-08-14 at 15:19 +0200, Julia Lawall wrote:

> Sorry, I'm not sure where 1.0.7 came from. [...]

> I would indeed like to make a release now that the compiations issues are
> resolved and things seem more stable.

Were you able to clear this up?

I see now that the website advertises the 1.0.7 release, however

 * it's not tagged in git(hub) - all previous releases have a tag
 * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
   the website
 * it *looks* like the actual 1.0.7 release was cut from a much newer
   git commit, likely with the fix?

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-09-10  7:24   ` [Cocci] New release after 1.0.7? Johannes Berg
@ 2018-09-10 10:43     ` Julia Lawall
  2018-09-12 10:14     ` Julia Lawall
  1 sibling, 0 replies; 16+ messages in thread
From: Julia Lawall @ 2018-09-10 10:43 UTC (permalink / raw)
  To: Johannes Berg; +Cc: Luciano Coelho, cocci, backports



On Mon, 10 Sep 2018, Johannes Berg wrote:

> Julia,
>
> On Tue, 2018-08-14 at 15:19 +0200, Julia Lawall wrote:
>
> > Sorry, I'm not sure where 1.0.7 came from. [...]
>
> > I would indeed like to make a release now that the compiations issues are
> > resolved and things seem more stable.
>
> Were you able to clear this up?
>
> I see now that the website advertises the 1.0.7 release, however
>
>  * it's not tagged in git(hub) - all previous releases have a tag
>  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
>    the website
>  * it *looks* like the actual 1.0.7 release was cut from a much newer
>    git commit, likely with the fix?

I'm still somewhat lost about it.  There is now a 1.0.7 source code on the
web site, which is the proper 1.0.7.  But the binaries on the web site are
still 1.0.6.  The previous thing that seemed to be 1.0.7 was an accidental
side effect of a test of the release script.  I think that my engineer was
waiting me to confirm something before putting a tag in github, but I'm
not sure what I was to confirm.  I will try to clear everything up.  But
the source code on the Coccinelle website is the official 1.0.7.

julia
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-09-10  7:24   ` [Cocci] New release after 1.0.7? Johannes Berg
  2018-09-10 10:43     ` Julia Lawall
@ 2018-09-12 10:14     ` Julia Lawall
  2018-09-12 10:16       ` Johannes Berg
  1 sibling, 1 reply; 16+ messages in thread
From: Julia Lawall @ 2018-09-12 10:14 UTC (permalink / raw)
  To: Johannes Berg; +Cc: Luciano Coelho, cocci, backports



On Mon, 10 Sep 2018, Johannes Berg wrote:

> Julia,
>
> On Tue, 2018-08-14 at 15:19 +0200, Julia Lawall wrote:
>
> > Sorry, I'm not sure where 1.0.7 came from. [...]
>
> > I would indeed like to make a release now that the compiations issues are
> > resolved and things seem more stable.
>
> Were you able to clear this up?
>
> I see now that the website advertises the 1.0.7 release, however
>
>  * it's not tagged in git(hub) - all previous releases have a tag
>  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
>    the website
>  * it *looks* like the actual 1.0.7 release was cut from a much newer
>    git commit, likely with the fix?

There is now a tag for the official release of 1.0.7 in github.

julia
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-09-12 10:14     ` Julia Lawall
@ 2018-09-12 10:16       ` Johannes Berg
  2018-10-22 11:44         ` Arend van Spriel
  0 siblings, 1 reply; 16+ messages in thread
From: Johannes Berg @ 2018-09-12 10:16 UTC (permalink / raw)
  To: Julia Lawall; +Cc: Luciano Coelho, cocci, backports

On Wed, 2018-09-12 at 12:14 +0200, Julia Lawall wrote:

> > I see now that the website advertises the 1.0.7 release, however
> > 
> >  * it's not tagged in git(hub) - all previous releases have a tag
> >  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
> >    the website
> >  * it *looks* like the actual 1.0.7 release was cut from a much newer
> >    git commit, likely with the fix?
> 
> There is now a tag for the official release of 1.0.7 in github.

Great, thanks!

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-09-12 10:16       ` Johannes Berg
@ 2018-10-22 11:44         ` Arend van Spriel
  2018-10-22 11:45           ` Johannes Berg
  0 siblings, 1 reply; 16+ messages in thread
From: Arend van Spriel @ 2018-10-22 11:44 UTC (permalink / raw)
  To: Johannes Berg; +Cc: backports

On 9/12/2018 12:16 PM, Johannes Berg wrote:
> On Wed, 2018-09-12 at 12:14 +0200, Julia Lawall wrote:
>
>>> I see now that the website advertises the 1.0.7 release, however
>>>
>>>  * it's not tagged in git(hub) - all previous releases have a tag
>>>  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
>>>    the website
>>>  * it *looks* like the actual 1.0.7 release was cut from a much newer
>>>    git commit, likely with the fix?
>>
>> There is now a tag for the official release of 1.0.7 in github.
>
> Great, thanks!

Were you able to build this tag? I probably have dependency issues on 
our build server. I tried following the install.txt in coccinelle repo, 
but still getting failures. Some hints might be useful. The server runs 
ubuntu trusty which is pretty old of course.

Gr. AvS

--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-10-22 11:44         ` Arend van Spriel
@ 2018-10-22 11:45           ` Johannes Berg
  2018-10-22 19:49             ` Hauke Mehrtens
  0 siblings, 1 reply; 16+ messages in thread
From: Johannes Berg @ 2018-10-22 11:45 UTC (permalink / raw)
  To: Arend van Spriel; +Cc: backports

On Mon, 2018-10-22 at 13:44 +0200, Arend van Spriel wrote:
> On 9/12/2018 12:16 PM, Johannes Berg wrote:
> > On Wed, 2018-09-12 at 12:14 +0200, Julia Lawall wrote:
> > 
> > > > I see now that the website advertises the 1.0.7 release, however
> > > > 
> > > >  * it's not tagged in git(hub) - all previous releases have a tag
> > > >  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
> > > >    the website
> > > >  * it *looks* like the actual 1.0.7 release was cut from a much newer
> > > >    git commit, likely with the fix?
> > > 
> > > There is now a tag for the official release of 1.0.7 in github.
> > 
> > Great, thanks!
> 
> Were you able to build this tag? I probably have dependency issues on 
> our build server. I tried following the install.txt in coccinelle repo, 
> but still getting failures. Some hints might be useful. The server runs 
> ubuntu trusty which is pretty old of course.

Hmm. I built something, either that tag or the tarball?

johannes

--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-10-22 11:45           ` Johannes Berg
@ 2018-10-22 19:49             ` Hauke Mehrtens
  2018-10-22 20:46               ` Arend van Spriel
  0 siblings, 1 reply; 16+ messages in thread
From: Hauke Mehrtens @ 2018-10-22 19:49 UTC (permalink / raw)
  To: Johannes Berg, Arend van Spriel; +Cc: backports

[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]

On 10/22/2018 01:45 PM, Johannes Berg wrote:
> On Mon, 2018-10-22 at 13:44 +0200, Arend van Spriel wrote:
>> On 9/12/2018 12:16 PM, Johannes Berg wrote:
>>> On Wed, 2018-09-12 at 12:14 +0200, Julia Lawall wrote:
>>>
>>>>> I see now that the website advertises the 1.0.7 release, however
>>>>>
>>>>>  * it's not tagged in git(hub) - all previous releases have a tag
>>>>>  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
>>>>>    the website
>>>>>  * it *looks* like the actual 1.0.7 release was cut from a much newer
>>>>>    git commit, likely with the fix?
>>>>
>>>> There is now a tag for the official release of 1.0.7 in github.
>>>
>>> Great, thanks!
>>
>> Were you able to build this tag? I probably have dependency issues on 
>> our build server. I tried following the install.txt in coccinelle repo, 
>> but still getting failures. Some hints might be useful. The server runs 
>> ubuntu trusty which is pretty old of course.
> 
> Hmm. I built something, either that tag or the tarball?
> 
> johannes

I built the tag on Debian stable successfully, some older versions did
not build but this tag worked.

Hauke


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [Cocci] New release after 1.0.7?
  2018-10-22 19:49             ` Hauke Mehrtens
@ 2018-10-22 20:46               ` Arend van Spriel
  0 siblings, 0 replies; 16+ messages in thread
From: Arend van Spriel @ 2018-10-22 20:46 UTC (permalink / raw)
  To: Hauke Mehrtens, Johannes Berg; +Cc: backports

On 10/22/2018 9:49 PM, Hauke Mehrtens wrote:
> On 10/22/2018 01:45 PM, Johannes Berg wrote:
>> On Mon, 2018-10-22 at 13:44 +0200, Arend van Spriel wrote:
>>> On 9/12/2018 12:16 PM, Johannes Berg wrote:
>>>> On Wed, 2018-09-12 at 12:14 +0200, Julia Lawall wrote:
>>>>
>>>>>> I see now that the website advertises the 1.0.7 release, however
>>>>>>
>>>>>>  * it's not tagged in git(hub) - all previous releases have a tag
>>>>>>  * commit c1522bde ("Release 1.0.7") is NOT what's released as 1.0.7 on
>>>>>>    the website
>>>>>>  * it *looks* like the actual 1.0.7 release was cut from a much newer
>>>>>>    git commit, likely with the fix?
>>>>>
>>>>> There is now a tag for the official release of 1.0.7 in github.
>>>>
>>>> Great, thanks!
>>>
>>> Were you able to build this tag? I probably have dependency issues on
>>> our build server. I tried following the install.txt in coccinelle repo,
>>> but still getting failures. Some hints might be useful. The server runs
>>> ubuntu trusty which is pretty old of course.
>>
>> Hmm. I built something, either that tag or the tarball?
>>
>> johannes
>
> I built the tag on Debian stable successfully, some older versions did
> not build but this tag worked.

That is Debian 9.5 I take it?

Gr. AvS

--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, back to index

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-14 13:09 New release after 1.0.7? Luciano Coelho
2018-08-14 13:19 ` [Cocci] " Julia Lawall
2018-08-14 13:32   ` Luciano Coelho
2018-08-14 13:43     ` Julia Lawall
2018-08-14 14:39       ` Luciano Coelho
2018-08-16  7:05         ` Johannes Berg
2018-08-16  7:09           ` Luciano Coelho
     [not found]     ` <b417bf64-7970-8482-0246-ab00129b4657@users.sourceforge.net>
     [not found]       ` <alpine.DEB.2.20.1808151127520.2309@hadrien>
2018-08-16  5:45         ` [Cocci] Adjustment for const qualification SF Markus Elfring
2018-09-10  7:24   ` [Cocci] New release after 1.0.7? Johannes Berg
2018-09-10 10:43     ` Julia Lawall
2018-09-12 10:14     ` Julia Lawall
2018-09-12 10:16       ` Johannes Berg
2018-10-22 11:44         ` Arend van Spriel
2018-10-22 11:45           ` Johannes Berg
2018-10-22 19:49             ` Hauke Mehrtens
2018-10-22 20:46               ` Arend van Spriel

Backports Archive on lore.kernel.org

Archives are clonable: git clone --mirror https://lore.kernel.org/backports/0 backports/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 backports backports/ https://lore.kernel.org/backports \
		backports@vger.kernel.org backports@archiver.kernel.org
	public-inbox-index backports


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.backports


AGPL code for this site: git clone https://public-inbox.org/ public-inbox