public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Alexey Sokolov <alexey+cygwin@asokolov.org>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn. Maintainers] perl-5.30.1 -- prepare for release
Date: Sat, 08 Feb 2020 21:35:00 -0000	[thread overview]
Message-ID: <2f378d4d-28b2-82e7-42f9-32ff9552b4a6@asokolov.org> (raw)
In-Reply-To: <87tv40iyx4.fsf@Rainer.invalid>

08.02.2020 21:53, Achim Gratz пишет:
> Achim Gratz writes:
>> In preparation of the release, please follow the instructions below to
>> upload the packages (re-)created with the new Perl version to the Cygwin
>> server.  Please be reminded that the new packages should not be "test"
>> versions so that setup.exe will offer them automatically when they are
>> distributed to the mirrors.
>>
>> 1. Please do not place the !ready cookie file!  When uploading via
>> cygport that means using the command "upload-stage" rather than
>> "upload".  This will ensure that all packages of the update get release
>> at the same time and that existing installations can be switched over to
>> the new Perl in a single update transaction.
>>
>> 2. Instead, please put a zero-size !perl cookie file (preferrably at the
>> package level).  You can either create that file manually (lftp: put
>> /dev/null -o pkgname/!perl) or touch that file into
>> pkgname/dist/pkgname/ before commanding cygport to do "upload-stage".
>>
>> 3. Please respond to this mail when you've done the above so that we can
>> keep track of what is staged in the upload area.
>>
>> If any of the above is unclear or you want assistance of any sort,
>> please ask.
> 
> I have all of my own / co-maintained packages staged now.
> 
> 
> The update will wait for:
> 
> subversion-perl
> 
> 
> Going through the list of packages collected during the 5.26 update we
> seem to be missing feedback from the respective maintainers for:
> 
> net-smtp
> texinfo
> weechat
> znc

Eh, it was ready a while ago, and I pinged you already about that :)

I've uploaded with !perl

> git-svn
> git
> grepmail
> nginx-mod_http_perl
> po4a
> pristine-tar
> sendxmpp
> 
> 
> Yaakov's packages will be updated later unless someone speaks up that
> one of them is indispensable:
> 
> perl-Alien-wxWidgets
> perl-Cairo
> perl-Cairo-GObject
> perl-GD
> perl-Glib
> perl-Glib-Object-Introspection
> perl-Gnome2
> perl-Gnome2-Canvas
> perl-Gnome2-GConf
> perl-Gnome2-Rsvg
> perl-Gnome2-VFS
> perl-Gnome2-Vte
> perl-Gnome2-Wnck
> perl-GStreamer1
> perl-Gtk2
> perl-Gtk2-GladeXML
> perl-Gtk2-Notify
> perl-Gtk2-SourceView2
> perl-Gtk2-Spell
> perl-Gtk2-Unique
> perl-Gtk2-WebKit
> perl-Gtk3
> perl-Pango
> perl-SGMLSpm
> perl-Win32-GUI
> perl-Wx
> gnumeric
> graphviz
> hexchat
> libproxy
> link-grammar
> marisa
> ming
> openbabel
> openwsman
> rxvt-unicode
> vim
> xfconf
> zbar
> zinnia
> 
> 
> Regards,
> Achim.
> 

  reply	other threads:[~2020-02-08 21:35 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 17:12 [Attn. Maintainers] perl-5.30.1 Achim Gratz
2019-11-10 20:58 ` Andrew Schulman via cygwin-apps
2019-11-10 21:38 ` Ken Brown
2019-11-17 18:28 ` Achim Gratz
2019-11-24 17:58   ` [Attn. Maintainers] Reminder: Package updates needed for the pending switch to perl-5.30.1 Achim Gratz
2019-11-25 16:33     ` Marco Atzeri
2019-12-16 18:41       ` Marco Atzeri
2019-12-16 18:51         ` Achim Gratz
2019-12-16 19:44           ` Marco Atzeri
2019-11-25 17:20     ` Jari Aalto
2019-11-25 17:27     ` [Attn. Maintainers] RFP: libmail-mbox-messageparser-perl (perl-5.30.1 rebuild) " Jari Aalto
2019-11-25 17:34       ` Achim Gratz
2019-11-25 18:02         ` Jari Aalto
2019-11-26 12:21           ` Achim Gratz
2019-11-26 19:42           ` Achim Gratz
2019-11-26 20:37     ` [Attn. Maintainers] Reminder: Package updates needed for the " Alexey Sokolov
2019-11-26 20:47       ` Achim Gratz
2020-01-09 18:58     ` Achim Gratz
2020-01-11 17:28       ` Achim Gratz
2020-01-20 16:11         ` Achim Gratz
2019-11-17 19:57 ` [Attn. Maintainers] perl-5.30.1 Achim Gratz
2019-11-18 22:35   ` Ken Brown
2019-11-18 23:25     ` Brian Inglis
2019-11-19  6:53     ` ASSI
2019-11-19 13:33       ` ASSI
2019-11-19 13:44       ` Ken Brown
2019-11-19 13:58         ` ASSI
2019-11-19 17:08           ` Achim Gratz
2019-11-19 19:30         ` Achim Gratz
2019-11-22 20:04           ` Ken Brown
2019-11-28  6:56 ` Achim Gratz
2019-11-29 21:22   ` Andrew Schulman via cygwin-apps
2019-12-01 12:42   ` Achim Gratz
2020-02-03 20:11 ` [Attn. Maintainers] perl-5.30.1 -- prepare for release Achim Gratz
2020-02-04 17:44   ` Marco Atzeri
2020-02-04 17:54   ` Ken Brown
2020-02-04 19:30   ` Andrew Schulman via cygwin-apps
2020-02-04 20:23     ` Achim Gratz
2020-02-05 12:54       ` Jon Turney
2020-02-06 17:53   ` David Rothenberger
2020-02-08  6:57     ` Marco Atzeri
2020-02-15 11:42     ` Marco Atzeri
2020-02-16  6:55       ` ASSI
2020-02-16  8:08         ` Marco Atzeri
2020-02-16 15:30           ` Jon Turney
2020-02-18 19:54             ` Marco Atzeri
2020-02-19 16:44               ` Jon Turney
2020-02-19 23:41                 ` Alexey Sokolov
2020-02-20 15:26                   ` Jon Turney
2020-02-18 16:43       ` David Rothenberger
2020-02-08 20:53   ` Achim Gratz
2020-02-08 21:35     ` Alexey Sokolov [this message]
2020-02-09  7:25       ` ASSI

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=2f378d4d-28b2-82e7-42f9-32ff9552b4a6@asokolov.org \
    --to=alexey+cygwin@asokolov.org \
    --cc=cygwin-apps@cygwin.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).