[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#492937: marked as done (apt-setup: inconsistent path handling for 'security' and 'volatile' services)



Your message dated Fri, 28 Feb 2014 21:51:04 +0100
with message-id <20140228205104.GA3662@mraw.org>
and subject line Re: Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services
has caused the Debian Bug report #492937,
regarding apt-setup: inconsistent path handling for 'security' and 'volatile' services
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
492937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492937
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
package: debian-installer
severity: wishlist

Hi,

I was looking at packages/apt-setup/generators/and noticed a difference between the way that 91security and 92volatile add lines
to the new sources.list file (subversion, r54582):

 91security does this -
 echo "deb http://$host/ $codename/updates $dists" >> $file

 92volatile does this -
 echo "deb http://$host/debian-volatile $codename/volatile $dists" >> $file

I noticed this when I was trying to preseed these settings, but using
a local apt-proxy machine instead of security.d.o and volatile.d.o.

At present I can preseed the security source like this
  d-i apt-setup/security_host      string      aptproxy:9999/security
and the "right thing" happens.

But to get volatile right I would have to preseed differently
  d-i apt-setup/volatile_host      string      aptproxy:9999
and use the path /debian-volatile on the apt-proxy.

This would look a bit odd to an unitiated reader of the preseeding file.

To me, the answer appears to allow additional variables
  apt-proxy/security_path
  apt-proxy/volatile_path

and default these to '' and '/debian-volatile', respectively, so you
can do e.g.
  echo "deb http://$host/$path $codename/volatile $dists" >> $file

Then I could preseed the settings for my apt-proxy as well, in a nicer way.

Does this seem sensible? This might also help #364650.

Cheers
Vince




--- End Message ---
--- Begin Message ---
Vincent McIntyre <Vince.McIntyre@atnf.csiro.au> (2008-07-30):
> I was looking at packages/apt-setup/generators/and noticed a
> difference between the way that 91security and 92volatile add
> lines to the new sources.list file (subversion, r54582):
> […]

volatile.d.o is now gone and updates are available in the main
archive (see generators/92updates). Closing this bug report
accordingly.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: