linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 17
Date: Wed, 17 Jul 2019 08:33:29 -0700	[thread overview]
Message-ID: <20190717153329.GC7116@magnolia> (raw)
In-Reply-To: <CA+icZUUhnSGkLQcCZBzYXCRxExiZ1F=KnzdeiNSbojHRfxRjOA@mail.gmail.com>

On Wed, Jul 17, 2019 at 05:30:47PM +0200, Sedat Dilek wrote:
> Hi Steven, Hi Darrick,
> 
> Unfortunately, my build-script is not working anymore.
> 
> I am using builddeb/mkdebian scripts.

Yeah, I accidentally uploaded an internal build patch yesterday which
got sucked into for-next.  It's been fixed in the iomap-for-next tree
and should disappear in Thursday's for-next tree.  Sorry about that. :(

--D

> [ BUILD-LOG ]
> ...
> set -e; mkdir -p include/config/; { echo "5.2.0$(/bin/bash
> ./scripts/setlocalversion .)"; } > include/config/kernel.release.tmp;
> if [ -r include/config/kernel.release ] && cmp -s
> include/config/kernel.release include/config/kernel.release.tmp; then
> rm -f include/config/kernel.release.tmp; else : '  UPD
> include/config/kernel.release'; mv -f
> include/config/kernel.release.tmp include/config/kernel.release; fi
> make -f ./scripts/Makefile.build obj=scripts/package bindeb-pkg
> /bin/bash ./scripts/package/mkdebian
> ./scripts/package/mkdebian: line 149: cd: source/: No such file or directory
> make[1]: *** [scripts/package/Makefile:79: bindeb-pkg] Error 1
> make: *** [Makefile:1442: bindeb-pkg] Error 2
> 
> Investigations revealed hardcoded stuff from the ...
> 
> Merge remote-tracking branch 'iomap/iomap-for-next'
> 
> $ git blame scripts/package/mkdebian | grep 'cd source'
> 87bdff62e470c (Darrick J. Wong    2019-06-27 17:30:15 -0700 149) (cd
> source/ ; stg ser | sed -e '/^-/d' -e 's/^. /  * /g') >>
> debian/changelog
> 
> $ git log --oneline --author="Darrick J. Wong" scripts/package/mkdebian
> 87bdff62e470 mtr: Build script adjustments
> 
> I do not think this was intended?
> 
> Reverting seems to be easy and fix it for me.
> 
> $ git revert --no-edit 87bdff62e470
> Führe Erkennung für ungenaue Umbenennung aus: 100% (2251440/2251440), Fertig.
> [5.2.0-3-amd64-cbl-asmgoto db8ec1968620] Revert "mtr: Build script adjustments"
>  Date: Wed Jul 17 17:27:26 2019 +0200
>  3 files changed, 10 insertions(+), 17 deletions(-)
> 
> Please make it work again for $WORLD.
> 
> Thanks.
> 
> Regards,
> - Sedat -
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/package/mkdebian?h=next-20190717

  reply	other threads:[~2019-07-17 15:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  4:29 linux-next: Tree for Jul 17 Stephen Rothwell
2019-07-17 15:30 ` Sedat Dilek
2019-07-17 15:33   ` Darrick J. Wong [this message]
2019-07-17 15:44     ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2025-07-17  9:36 Stephen Rothwell
2024-07-17  6:34 Stephen Rothwell
2023-07-17  3:46 Stephen Rothwell
2020-07-17 11:40 Stephen Rothwell
2018-07-17  9:05 Stephen Rothwell
2017-07-17  3:19 Stephen Rothwell
2015-07-17  5:26 Stephen Rothwell
2015-07-18 19:41 ` Paul Gortmaker
2015-07-20  3:00   ` Stephen Rothwell
2014-07-17  8:53 Stephen Rothwell
2013-07-17  4:13 Stephen Rothwell
2013-07-17  8:31 ` Mark Brown
2013-07-17 23:38   ` Stephen Rothwell
2013-07-18  2:09     ` Stephen Rothwell
2013-07-18  9:33       ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190717153329.GC7116@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).