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

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

repositories frozen since Mar 20th?

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

Contents

  repositories frozen since Mar 20th? Jörg-Volker Peetz <jvpeetz@web.de> - 2016-03-22 12:40 +0100
    Re: repositories frozen since Mar 20th? Sven Hartge <sven@svenhartge.de> - 2016-03-22 12:50 +0100
      Re: repositories frozen since Mar 20th? Jörg-Volker Peetz <jvpeetz@web.de> - 2016-03-22 13:20 +0100
      Re: repositories frozen since Mar 20th? David Wright <deblis@lionunicorn.co.uk> - 2016-03-24 02:20 +0100
      Re: repositories frozen since Mar 20th? David Wright <deblis@lionunicorn.co.uk> - 2016-03-25 19:20 +0100
    Re: repositories frozen since Mar 20th? Jörg-Volker Peetz <jvpeetz@web.de> - 2016-03-25 11:10 +0100
      Re: repositories frozen since Mar 20th? Henrique de Moraes Holschuh <hmh@debian.org> - 2016-03-25 17:20 +0100
      Re: repositories frozen since Mar 20th? Frank McCormick <debianlist@videotron.ca> - 2016-03-25 18:50 +0100
        Re: repositories frozen since Mar 20th? Sven Hartge <sven@svenhartge.de> - 2016-03-25 21:00 +0100
        Re: repositories frozen since Mar 20th? Frank McCormick <debianlist@videotron.ca> - 2016-03-25 23:10 +0100

#165820 — repositories frozen since Mar 20th?

Any clue to why the debian repositories, especially testing and sid, seem to be
unchanged since Mar 20th?

Regards,
jvp.

[toc] | [next] | [standalone]

#165821

Jörg-Volker Peetz <jvpeetz@web.de> wrote:

> Any clue to why the debian repositories, especially testing and sid,
> seem to be unchanged since Mar 20th?

Maybe this has something to do with the removal of the SHA1 checksums in
the Release file and the removal of gzipped Packages files? Perhaps
something internally broke and the mirrors are not updated correctly any
more.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

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

#165823

Sven Hartge wrote on 03/22/16 12:45:
> Jörg-Volker Peetz <jvpeetz@web.de> wrote:
> 
>> Any clue to why the debian repositories, especially testing and sid,
>> seem to be unchanged since Mar 20th?
> 
> Maybe this has something to do with the removal of the SHA1 checksums in
> the Release file and the removal of gzipped Packages files? Perhaps
> something internally broke and the mirrors are not updated correctly any
> more.
> 
> Grüße,
> Sven.
> 
Maybe I'd ask the same question on the developer.announce list then.

Regards,
jvp.

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

#165886

On Tue 22 Mar 2016 at 12:45:46 (+0100), Sven Hartge wrote:
> Jörg-Volker Peetz <jvpeetz@web.de> wrote:
> 
> > Any clue to why the debian repositories, especially testing and sid,
> > seem to be unchanged since Mar 20th?
> 
> Maybe this has something to do with the removal of the SHA1 checksums in
> the Release file and the removal of gzipped Packages files? Perhaps
> something internally broke and the mirrors are not updated correctly any
> more.

It's also preventing expiration of packages in my apt-cacher-ng
archive through its inability to download all the various types of
Packages and Sources files. Mind you, that may be a good thing because
the rather high number of packages tagged for removal might itself be
a consequence of the absence of those Packages files.

Cheers,
David.

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

#165947

On Tue 22 Mar 2016 at 12:45:46 (+0100), Sven Hartge wrote:
> Jörg-Volker Peetz <jvpeetz@web.de> wrote:
> 
> > Any clue to why the debian repositories, especially testing and sid,
> > seem to be unchanged since Mar 20th?
> 
> Maybe this has something to do with the removal of the SHA1 checksums in
> the Release file and the removal of gzipped Packages files? Perhaps
> something internally broke and the mirrors are not updated correctly any
> more.

Trusting that repository normalcy is restored, I ran apt-cacher-ng and
deleted 34 cached {Packages,Sources}{,.bz2} files that have no copy
in the repository, whereupon I could purge all my expired packages again.

It's a shame that apt-cacher-ng doesn't appear able to delete those
files when it has successfully downloaded their {.gz,.xz} equivalents
(even when it has both gz/xz).

It's also odd that, even after forcing a download of all the packages
files in full, it still hangs on to quite a collection of stale
package-diff files. I think I have to manually delete these.

Mustn't knock it though; in all other respects it does a great job.

Cheers,
David.

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

#165932

Meanwhile, the issue seems to be fixed. New packages appearing again in the
testing and sid repositories.

Regards,
jvp.

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

#165937

On Fri, Mar 25, 2016, at 07:05, Jörg-Volker Peetz wrote:
> Meanwhile, the issue seems to be fixed. New packages appearing again in
> the
> testing and sid repositories.

Yes, it is fixed. It was broken for two or three days, only.

Users of debmirror that have mirrors of testing or unstable will want to
switch to the version in Debian testing, though.  I will ask the
debmirror maintainer for a backports release or a stable update (if
nobody did it already), but meanwhile anyone that needs it can simply
download the source package for unstable and rebuild it in stable. It
works just fine.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique de Moraes Holschuh <hmh@debian.org>

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

#165945

On 25/03/16 12:15 PM, Henrique de Moraes Holschuh wrote:
> On Fri, Mar 25, 2016, at 07:05, Jörg-Volker Peetz wrote:
>> Meanwhile, the issue seems to be fixed. New packages appearing again in
>> the
>> testing and sid repositories.
> Yes, it is fixed. It was broken for two or three days, only.
>
> Users of debmirror that have mirrors of testing or unstable will want to
> switch to the version in Debian testing, though.  I will ask the
> debmirror maintainer for a backports release or a stable update (if
> nobody did it already), but meanwhile anyone that needs it can simply
> download the source package for unstable and rebuild it in stable. It
> works just fine.
>

    Last time I checked...last night...the google-chrome repository 
still wasn't fixed. However my system still downloaded and installed the 
latest google-chrome.

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

#165952

Frank McCormick <debianlist@videotron.ca> wrote:

>    Last time I checked...last night...the google-chrome repository 
> still wasn't fixed. However my system still downloaded and installed the 
> latest google-chrome.

That still is out of the hands of the Debian maintainers, this is
something Google has to fix on their end:

https://bugs.chromium.org/p/chromium/issues/detail?id=596074

Grüßem
Sven.

-- 
Sigmentation fault. Core dumped.

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

#165956

[Multipart message — attachments visible in raw view] — view raw

On 25/03/16 03:55 PM, Sven Hartge wrote:
> Frank McCormick <debianlist@videotron.ca> wrote:
>
>>     Last time I checked...last night...the google-chrome repository
>> still wasn't fixed. However my system still downloaded and installed the
>> latest google-chrome.
> That still is out of the hands of the Debian maintainers, this is
> something Google has to fix on their end:
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=596074
>
> Grüßem
> Sven.
>



    For further problems with other repositories this is the page to 
consult:


This page keeps track of repositories broken or half-broken by the SHA1 
removal. Please note that we intend to shut of SHA1 completely on 
January 1, 2017.

https://wiki.debian.org/Teams/Apt/Sha1Removal

[toc] | [prev] | [standalone]

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

csiph-web