Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179192 > unrolled thread

new packages

Back to article view | Back to linux.debian.user

Contents

  new packages Pol Hallen <deben@fuckaround.org> - 2017-03-23 13:30 +0100
    Re: new packages Reco <recoverym4n@gmail.com> - 2017-03-23 14:40 +0100
    Re: new packages songbird <songbird@anthive.com> - 2017-03-23 19:50 +0100
      Re: new packages Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-23 20:50 +0100
        Re: new packages Dejan Jocic <jodejka@gmail.com> - 2017-03-23 21:10 +0100
          Re: new packages Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-23 21:50 +0100
        Re: new packages songbird <songbird@anthive.com> - 2017-03-24 02:30 +0100

#179192 — new packages

Hi all :-)

is there a tool to see periodically new packages added to 
repository?(mainly I use testing)

thanks!

Pol

[toc] | [next] | [standalone]

#179195

	Hi.

On Thu, 23 Mar 2017 13:17:18 +0100
Pol Hallen <deben@fuckaround.org> wrote:

> Hi all :-)
> 
> is there a tool to see periodically new packages added to 
> repository?(mainly I use testing)

aptitude forget-new
aptitude update
aptitude search ~N

Reco

[toc] | [prev] | [next] | [standalone]

#179212

Pol Hallen wrote:
> Hi all :-)
>
> is there a tool to see periodically new packages added to 
> repository?(mainly I use testing)
>
> thanks!

  when you run:

$ apt-get upgrade

it will not add any new programs, but when you run:

$ apt-get dist-upgrade

it will tell you which are new of the updates it is
going to perform (if any).

if you want the gui approach synaptic will show you 
which packages are new in the repository (under the
status option).

  those are the only two things i use for upgrades
these days (i purged aptitude a while ago after i
realized i never use it any longer).


  songbird

[toc] | [prev] | [next] | [standalone]

#179216

On Thu, Mar 23, 2017 at 02:42:20PM -0400, songbird wrote:
>   when you run:
> 
> $ apt-get upgrade
> 
> it will not add any new programs, but when you run:
> 
> $ apt-get dist-upgrade
> 
> it will tell you which are new of the updates it is
> going to perform (if any).

I strongly recommend using the half-documented -u option here:

apt-get -u upgrade

It's not in the man page, but it IS in the "apt-get -h" output.

That way you'll have some warning of which services are going to be
affected.  If, for example, you see that your database server is
going to be upgraded, and you know that this will impact your users,
you may want to wait until a less busy time to do the upgrade, and
shut down your database-client application(s), etc.

This is also one of the reasons why unattended upgrades are not on
by default.

[toc] | [prev] | [next] | [standalone]

#179217

On 23-03-17, Greg Wooledge wrote:
> On Thu, Mar 23, 2017 at 02:42:20PM -0400, songbird wrote:
> >   when you run:
> > 
> > $ apt-get upgrade
> > 
> > it will not add any new programs, but when you run:
> > 
> > $ apt-get dist-upgrade
> > 
> > it will tell you which are new of the updates it is
> > going to perform (if any).
> 
> I strongly recommend using the half-documented -u option here:
> 
> apt-get -u upgrade
> 
> It's not in the man page, but it IS in the "apt-get -h" output.
> 
> That way you'll have some warning of which services are going to be
> affected.  If, for example, you see that your database server is
> going to be upgraded, and you know that this will impact your users,
> you may want to wait until a less busy time to do the upgrade, and
> shut down your database-client application(s), etc.
> 
> This is also one of the reasons why unattended upgrades are not on
> by default.
> 
Actually, it is in the man page of apt-get:

 -u, --show-upgraded
            Show upgraded packages; print out a list of all packages
	    that are
	               to be upgraded. Configuration Item:
		       APT::Get::Show-Upgraded.


Also, another option that could be more useful:

-s, --simulate, --just-print, --dry-run, --recon, --no-act
    No action; perform a simulation of events that would occur based on
    the current system state but do not actually change the system.
    Locking will be disabled (Debug::NoLocking) so the system state
    could change while apt-get is running. Simulations can also be
    executed by non-root users which might not have read access to all
    apt configuration distorting the simulation. A notice expressing
    this warning is also shown by default for non-root users
    (APT::Get::Show-User-Simulation-Note). Configuration Item:
    APT::Get::Simulate.
		       
Have fun :)

[toc] | [prev] | [next] | [standalone]

#179219

On Thu, Mar 23, 2017 at 09:00:05PM +0100, Dejan Jocic wrote:
> Actually, it is in the man page of apt-get:
> 
>  -u, --show-upgraded

Hmm... missing in stretch.  Present in jessie.  Maybe stretch decided
to turn it on by default?  (Stretch documents a "--no-show-upgraded"
option with no short equivalent.  Also, the -u option is accepted
without complaint.  Backward compatibility?)

Also, the -u in "apt-get -h" was from jessie... my bad, for reading
the man page on stretch, but then using apt-get -h on jessie.  I didn't
expect there to be such a large difference between the two.

So, testing... yes.  It does appear that "apt-get upgrade" and
"apt-get -u upgrade" both do the same thing on stretch.  I'll probably
still type the -u anyway, out of habit, and because I have many older
systems that need it.

[toc] | [prev] | [next] | [standalone]

#179227

Greg Wooledge wrote:
> On Thu, Mar 23, 2017 at 02:42:20PM -0400, songbird wrote:
>>   when you run:
>> 
>> $ apt-get upgrade
>> 
>> it will not add any new programs, but when you run:
>> 
>> $ apt-get dist-upgrade
>> 
>> it will tell you which are new of the updates it is
>> going to perform (if any).
>
> I strongly recommend using the half-documented -u option here:
>
> apt-get -u upgrade
>
> It's not in the man page, but it IS in the "apt-get -h" output.
>
> That way you'll have some warning of which services are going to be
> affected.  If, for example, you see that your database server is
> going to be upgraded, and you know that this will impact your users,
> you may want to wait until a less busy time to do the upgrade, and
> shut down your database-client application(s), etc.
>
> This is also one of the reasons why unattended upgrades are not on
> by default.

  not to worry, only one person uses this system
and i never do unattended upgrades (running testing 
or unstable at times).

  when i ran a production system there was a whole
series of things needed to take the system down and
up again.  when people today complain that the system
takes a few seconds longer to boot i mention that
ours took 12hrs (or longer).


  songbird

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web