All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lubomir Kundrak <lkundrak@redhat.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Extend the code to ignore junk files
Date: Thu, 17 Apr 2008 18:01:16 +0200	[thread overview]
Message-ID: <1208448076.770.68.camel@localhost.localdomain> (raw)
In-Reply-To: <200804151432.49014.Chris.Knadle@coredump.us>


On Tue, 2008-04-15 at 14:32 -0400, Chris Knadle wrote:
> On Tuesday 15 April 2008, Robert Millan wrote:
> > On Tue, Apr 15, 2008 at 12:22:48AM +0200, Lubomir Kundrak wrote:
> > > --- grub-1.96.orig/util/update-grub_lib.in	2008-04-15 00:16:12.000000000
> > > +0200 +++ grub-1.96/util/update-grub_lib.in	2008-04-15 00:15:04.000000000
> > > +0200 @@ -115,6 +115,8 @@ grub_file_is_not_garbage ()
> > >    if test -f "$1" ; then
> > >      case "$1" in
> > >        *.dpkg-dist|*.dpkg-old|*.dpkg-tmp) return 1 ;; # debian dpkg
> > > +      *.rpmnew|*.rpmsave) return 1 ;; # Fedora rpm
> > > +      *.bak|*~|.*.swp) return 1 ;;    # backup and swap files from
> > > editors
> >
> > This has the side-effect that Linux images whose name ends with ~ are
> > excluded, which is probably not that uncommon.  E.g.
> > /boot/vmlinuz-2.6.24.foobar~
> >
> > Is this really what we want?

Not uncommon; well -- I've never seen that, nor heard about if as being
a custom -- but it might be just that have not seen enough.

>    I don't know of any localversion policy requiring that the last character 
> not be a tilde character.

I think the localversion policy doesn't forbid the names ending
with .dpkg-dist or .bak as well.

> However, I can say that 'fakeroot make-kpkg 
> kernel_image' fails at the very last stage during making a .deb if the last 
> character in the localversion ends in a tilde.  i.e. you can't build a 
> kernel "the Debian way" that has a localversion ending in a tilde.
> 
>      dpkg-gencontrol: error: Illegal package name `linux-image-2.6.24.4-yee~'
>      make[1]: *** [debian/linux-image-2.6.24.4-yee~] Error 255

I'm fairly sure rpm doesn't allow this too.

-- 
Lubomir Kundrak (Red Hat Security Response Team)




      parent reply	other threads:[~2008-04-17 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 22:22 [PATCH] Extend the code to ignore junk files Lubomir Kundrak
2008-04-15 13:20 ` Robert Millan
2008-04-15 18:32   ` Chris Knadle
2008-04-15 18:56     ` Pavel Roskin
2008-04-17 16:01     ` Lubomir Kundrak [this message]

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=1208448076.770.68.camel@localhost.localdomain \
    --to=lkundrak@redhat.com \
    --cc=grub-devel@gnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.