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

Bug#915109: marked as done (apt upgrade needs limit or date cap)

Your message dated Fri, 30 Nov 2018 18:28:47 +0100
with message-id <20181130172846.GA30608@crossbow>
and subject line Re: Bug#915109: apt upgrade needs limit or date cap
has caused the Debian Bug report #915109,
regarding apt upgrade needs limit or date cap
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.)


-- 
915109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915109
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---

Package: apt
Version: apt 1.0.1ubuntu2 for amd64 compiled on Apr 12 2018 10:14:36


This is a much needed feature request but your Web site was totally unclear how to submit a feature request. apt upgrade needs some kind of limit or cap like:


sudo apt upgrade -asof=20180723


This is particularly necessary in the world of medical device developers and any other regulated industry where "Work Instructions" get filed with regulatory bodies on how to create, from scratch, a development environment. Many times these instructions say to install an LTS Debian based distro then


sudo apt update

sudo apt upgrade


The problem is, the repos have moved content wise since then and some update breaks the environment. A fantastic example as of today is the GUI software installer with Ubuntu 18.04 LTS. With a raw install of 18.04 you can copy in a .deb and use the GUI to install it. After applying all updates it no longer works.


The regulated world needs an "asof" qualifier so developer environments can be 100% recreatable without having to build an environment, disable apt, then make an ISO of said environment just so it can be reproducable.





------------------------------------------------------------------------
Disclaimer The information in this email and any attachments may contain proprietary and confidential information that is intended for the addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or use of the contents of this information is prohibited. When addressed to our clients or vendors, any information contained in this e-mail or any attachments is subject to the terms and conditions in any governing contract. If you have received this e-mail in error, please immediately contact the sender and delete the e-mail.

--- End Message ---
--- Begin Message --- 
Hi Roland Hughes

On Fri, Nov 30, 2018 at 03:12:51PM +0000, Roland Hughes wrote:
> This is a much needed feature request but your Web site was totally unclear how to submit a feature request.

For Debian details can actually be found here:
https://www.debian.org/Bugs/Reporting

You seem to be an Ubuntu user through, so your contact place would be launchpad:
https://bugs.launchpad.net/ubuntu/+source/apt

But that just as a remark to the general statement,
lets see about the rest of the mail now.


> The problem is, the repos have moved content wise since then and some update breaks the environment. A fantastic example as of today is the GUI software installer with Ubuntu 18.04 LTS. With a raw install of 18.04 you can copy in a .deb and use the GUI to install it. After applying all updates it no longer works.

If that is indeed the case it is at least not the fault of apt nor of
Debian. apt updating packages to fix security bugs is what you want;
such upgrades shouldn't "break the environment" through – but that is
a bug in whatever got upgraded, not in apt installing the upgrade.
Debian takes special care of this in its stable branch, I assume Ubuntu
applies similar care to their LTS, but maintainers of PPAs might not…

If you REALLY want a strong control over which state a repository is in
you need a repository with a stronger grip: Debian has
snapshots.debian.org which kinda does your asof on a repository level,
but usually it would be just as fine to run a local (partial) mirror all
your machines use as repository rather than some upstream mirror
directly.


So, as there is nothing Debian can do about this and apt itself performs
as intended I am closing this as not-a-bug (in apt), but please report
a bug against whatever broke in your environment in Ubuntu so they can
fix that!


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: