Re: Port submission for aidadoc
Dear Mojca, I have made the recommended fixes and have just been attaching the modified Portfile (added as Portfile.2). This is Ticket #55808: https://trac.macports.org/ticket/55808 cheers, Bernard Le 5 mars 2018 à 12:22, Mojca Miklavec a écrit : > Dear Bernard, > > On 5 March 2018 at 12:06, Bernard Desgraupes wrote: >> Hi, >> >> I have submitted, three weeks ago, a new port via a submission ticket >> (https://trac.macports.org/ticket/55808) but it doesn't seem to have >> received any attention. >> It concerns the aidadoc project (see >> https://sourceforge.net/projects/aidadoc). >> No rush but could someone review my ticket ? >> Thanks in advance, > > Thanks for the reminder. > > As it turns out lately there are a couple more people who follow > GitHub Pull requests more regularly than the Trac tickets (or should I > say: the 1 plus epsilon people who merge most pull requests look > exclusively on GitHub), so despide the two submission options > supposedly being equal, the chances of getting feedback are much > higher on GitHub. > > Mojca
Re: Port submission for aidadoc
On 6 March 2018 at 09:10, Bernard Desgraupes wrote: > Dear Mojca, > > I have made the recommended fixes and have just been attaching the modified > Portfile (added as Portfile.2). > This is Ticket #55808: https://trac.macports.org/ticket/55808 Thanks, but for some reason I'm unable to download the file from SourceForge at the moment (it gets me some strange html file), so it's a bit more difficult to proceed. The command looks correct unless I'm missing something: ---> Attempting to fetch aida-1.4.2-src.tar.bz2 from http://freefr.dl.sourceforge.net/projects/aidadoc/files/1.4.2/ The files are here: https://sourceforge.net/projects/aidadoc/files/1.4.2/ I have a question for others: what's the "correct" way to run autoheader autoconf before configure? We do have autoconf.cmd for example, but I'm not sure about the best way to run more than one commands (unless I misuse automake.cmd :) Mojca
Re: Port submission for aidadoc
On 2018-3-6 19:27 , Mojca Miklavec wrote: > I have a question for others: what's the "correct" way to run > autoheader > autoconf > before configure? We do have autoconf.cmd for example, but I'm not > sure about the best way to run more than one commands (unless I misuse > automake.cmd :) This is what autoreconf does. - Josh
Re: Port submission for aidadoc
So, if I understand correctly, writing: use_autoreconfyes would enough to replace the following: pre-configure { system -W ${build.dir} autoheader } use_autoconfyes Am I right ? Thanks, Bernard Le 6 mars 2018 à 10:17, Joshua Root a écrit : > On 2018-3-6 19:27 , Mojca Miklavec wrote: >> I have a question for others: what's the "correct" way to run >>autoheader >>autoconf >> before configure? We do have autoconf.cmd for example, but I'm not >> sure about the best way to run more than one commands (unless I misuse >> automake.cmd :) > > This is what autoreconf does. > > - Josh
Re: Port submission for aidadoc
On 2018-3-6 20:23 , Bernard Desgraupes wrote: > So, if I understand correctly, writing: > use_autoreconfyes > > would enough to replace the following: > pre-configure { > system -W ${build.dir} autoheader > } > use_autoconfyes > > Am I right ? In most cases yes. - Josh
Re: [macports-ports] branch master updated: irssi: perl5.26 revbump
On Mar 3, 2018, at 20:59, Zero King wrote: > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/9f045bef9d96ad58591bcb71dbf2fc3a67303f82 > > The following commit(s) were added to refs/heads/master by this push: > > new 9f045be irssi: perl5.26 revbump > > 9f045be is described below > > > commit 9f045bef9d96ad58591bcb71dbf2fc3a67303f82 > > Author: Zero King > AuthorDate: Sun Mar 4 02:59:10 2018 + > > > irssi: perl5.26 revbump Why? The irssi portfile doesn't mention any specific version of perl.
Re: [macports-ports] branch master updated: irssi: perl5.26 revbump
On Tue, Mar 06, 2018 at 04:08:04AM -0600, Ryan Schmidt wrote: On Mar 3, 2018, at 20:59, Zero King wrote: Zero King (l2dy) pushed a commit to branch master in repository macports-ports. https://github.com/macports/macports-ports/commit/9f045bef9d96ad58591bcb71dbf2fc3a67303f82 The following commit(s) were added to refs/heads/master by this push: new 9f045be irssi: perl5.26 revbump 9f045be is described below commit 9f045bef9d96ad58591bcb71dbf2fc3a67303f82 Author: Zero King AuthorDate: Sun Mar 4 02:59:10 2018 + irssi: perl5.26 revbump Why? The irssi portfile doesn't mention any specific version of perl. port-rev-upgrade(1) told me that it's broken, probably because port:perl5 was updated to 5.26 in https://github.com/macports/macports-ports/commit/d52392c211739ca19889d774a7e16d9a15756d14#diff-5a4a6e75a9ad4228d6e8fbf1016561a9. -- Best regards, Zero King smime.p7s Description: S/MIME cryptographic signature
Re: [macports-ports] branch master updated: irssi: perl5.26 revbump
On Mar 6, 2018, at 04:18, Zero Kingwrote: > On Tue, Mar 06, 2018 at 04:08:04AM -0600, Ryan Schmidt wrote: >> >> On Mar 3, 2018, at 20:59, Zero King wrote: >> >>> Zero King (l2dy) pushed a commit to branch master >>> in repository macports-ports. >>> >>> >>> https://github.com/macports/macports-ports/commit/9f045bef9d96ad58591bcb71dbf2fc3a67303f82 >>> >>> The following commit(s) were added to refs/heads/master by this push: >>> >>> new 9f045be irssi: perl5.26 revbump >>> >>> 9f045be is described below >>> >>> >>> commit 9f045bef9d96ad58591bcb71dbf2fc3a67303f82 >>> >>> Author: Zero King >>> AuthorDate: Sun Mar 4 02:59:10 2018 + >>> >>> >>>irssi: perl5.26 revbump >> >> Why? The irssi portfile doesn't mention any specific version of perl. > > port-rev-upgrade(1) told me that it's broken, probably because > port:perl5 was updated to 5.26 in > https://github.com/macports/macports-ports/commit/d52392c211739ca19889d774a7e16d9a15756d14#diff-5a4a6e75a9ad4228d6e8fbf1016561a9. Ok, but if irssi is linking with a specific version of perl's dynamic library, it needs to declare a dependency on that specific version of perl, and not on perl5. perl5's default variant may have been recently changed, but users are always free to select a different variant. We don't want users who do exercise that freedom to have a broken irssi.
request for port peg command, to lock down a port at the currently installed version
It is fairly common for users to find an update to a port that won't build on their system for some reason. It would be nice to have a simple command, like port peg PORTNAME that stops the port from attempting to update until the peg is released. Such a command does exist in other package mgmt systems. This can be done manually with a local repo, but it is a bit of a PITA to do that for casual users. Perhaps MacPorts could have a built-in local repo, and "port peg PORTNAME" would copy the current portfile out of the installed registry in there. That sounds pretty easy to do. Perhaps there is some easy way to keep a list of ports that are ignored for port upgrade outdated. Best, Ken
Re: Port submission for aidadoc
On 6 March 2018 at 10:47, Joshua Root wrote: > On 2018-3-6 20:23 , Bernard Desgraupes wrote: >> So, if I understand correctly, writing: >> use_autoreconfyes >> >> would enough to replace the following: >> pre-configure { >> system -W ${build.dir} autoheader >> } >> use_autoconfyes >> >> Am I right ? > > In most cases yes. Thank you. The port is now committed. Btw, the master_sites was not set properly. Bernard: I assume you downloaded the file manually? Mojca
request for port create command, to build a portfile from a URL
It would be nice to have a command like port create URL that would download the URL, calc the checksums for it, and build a basic Portfile for it. It could ask for a category to use for the Port. In a more advance version, it could extract the URL and do some quick analysis on it. if there's a CMakeLists.txt file in the root, do the right things to make it a cmake based port. If there's a configure file in the root, do the right things for that. Might make things faster and easier for people to get started and up and running. Certainly would make it easier for people who want to use MacPorts infrastructure to build their own files, as many don't know how to properly set up the include and lib directories, etc. Best, Ken
Re: request for port create command, to build a portfile from a URL
Hi Ken - I think that's a great idea. In "GNU Radio" land, we have such a tool for creating out-of-tree GR modules, called "gr_modtool"; it's great for setting up the skeleton for such OOT GR scripts. The end-user still has to fill in many "blanks", but this tool provides the starting point. I could see something similar for MacPorts, much as you describe. Maybe this could be added to the GSoC wiki page? It shouldn't be too difficult to implement something like what you propose, whether directly in 'port' or as a tool separate from 'port'. Cheers! - MLD On Tue, Mar 6, 2018, at 9:58 AM, Ken Cunningham wrote: > It would be nice to have a command like > > port create URL > > that would download the URL, calc the checksums for it, and build a > basic Portfile for it. > > It could ask for a category to use for the Port. > > In a more advance version, it could extract the URL and do some quick > analysis on it. > > if there's a CMakeLists.txt file in the root, do the right things to > make it a cmake based port. > > If there's a configure file in the root, do the right things for that. > > Might make things faster and easier for people to get started and up and > running. > > Certainly would make it easier for people who want to use MacPorts > infrastructure to build their own files, as many don't know how to > properly set up the include and lib directories, etc.
Re: request for port create command, to build a portfile from a URL
On 2018-3-7 01:58 , Ken Cunningham wrote: > It would be nice to have a command like > > port create URL > > that would download the URL, calc the checksums for it, and build a basic > Portfile for it. > > It could ask for a category to use for the Port. > > In a more advance version, it could extract the URL and do some quick > analysis on it. > > if there's a CMakeLists.txt file in the root, do the right things to make it > a cmake based port. > > If there's a configure file in the root, do the right things for that. > > Might make things faster and easier for people to get started and up and > running. > > Certainly would make it easier for people who want to use MacPorts > infrastructure to build their own files, as many don't know how to properly > set up the include and lib directories, etc. There's a fairly basic tool called portfile-gen in contrib. Improvements are certainly welcome. I'd advise not just blindly setting whatever checksums the downloaded file happens to have though; the maintainer should be getting those from a secure source (e.g. https web site) and verifying that they match, or verifying the distfile against a gpg signature. If that can be automated somehow then great, but let's not encourage skipping it. - Josh
Re: request for port peg command, to lock down a port at the currently installed version
I've seen this in other managers as "pin". Anyway, this gets tricky with managing dependencies. As you say, this would probably need to copy the current portfile, but it would also need to pin and copy anything that depends or is dependent on this port. And that's going to extend recursively out from there. Plus, if the upgrade failure is only identified when trying to upgrade, it's too late to copy the current portfile and the portfile history isn't maintained locally. I agree this would be a nice feature, but it's potentially a very large problem to tackle. On Tue, Mar 6, 2018 at 9:50 AM, Ken Cunningham wrote: > It is fairly common for users to find an update to a port that won't build on > their system for some reason. > > It would be nice to have a simple command, like > > port peg PORTNAME > > that stops the port from attempting to update until the peg is released. Such > a command does exist in other package mgmt systems. > > This can be done manually with a local repo, but it is a bit of a PITA to do > that for casual users. > > Perhaps MacPorts could have a built-in local repo, and "port peg PORTNAME" > would copy the current portfile out of the installed registry in there. That > sounds pretty easy to do. > > Perhaps there is some easy way to keep a list of ports that are ignored for > port upgrade outdated. > > > Best, > > Ken -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448
Re: request for port create command, to build a portfile from a URL
I like the auto calculate hashes For grabbing something from url sounds like having a lot of switches, for archive type and depedencies what if link is a redirect to cdn, or something like Dropbox or symbolic > On Mar 6, 2018, at 06:58, Ken Cunningham > wrote: > > Best,
Re: request for port create command, to build a portfile from a URL
Hi, On 6 March 2018 at 15:58, Ken Cunningham wrote: > It would be nice to have a command like > > port create URL > > that would download the URL, calc the checksums for it, and build a basic > Portfile for it. > > It could ask for a category to use for the Port. > > In a more advance version, it could extract the URL and do some quick > analysis on it. > > if there's a CMakeLists.txt file in the root, do the right things to make it > a cmake based port. > > If there's a configure file in the root, do the right things for that. > > Might make things faster and easier for people to get started and up and > running. > > Certainly would make it easier for people who want to use MacPorts > infrastructure to build their own files, as many don't know how to properly > set up the include and lib directories, etc. I would make a GSOC project proposal for this :) This would certainly be nice functionality, it's just that someone needs to write it. Mojca
Re: request for port create command, to build a portfile from a URL
On 2018-03-06, at 7:22 AM, G Alexander wrote: > I like the auto calculate hashes > > For grabbing something from url sounds like having a lot of switches, > > for archive type and depedencies > I was kinda hoping that the archive type might be figured out from the tail of the URL. All the use_bzip2 yes business if plenty confusing for people. Even the whole idea of master_sites and distnames takes getting used to. dependencies would have to be manually specified. A basic template could be laid down for them, however, in the generated Portfile. > what if link is a redirect to cdn, or something like Dropbox or symbolic > some things would have to be manually done, unless AI can sort this out in ways I don't know how to do... K
Re: Port submission for aidadoc
Mojca, thank you very much for reviewing this port. The other two checksums (if needed) are md528acc622599ae70bd9027fd80cf9f9b8 sha1aece1dbfdc342c63995a1bf7d7de525067038748 I don’t know why the download fails. Indeed I already have a dist file locally in /opt/local/var/macports/distfiles/aidadoc (probably as a result of previous attempts with my portfile) and this is probably why ‘port install’ seems to skip the fetch phase when I test on my machine. I don’t really understand how the master-sites command works when it says master_sitessourceforge:projects/aidadoc/files/${version}/ The « real » download URL is https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download I ran ‘port distcheck aidadoc’ and it shows a lot of URLs like http://heanet.dl.sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2 but http://heanet.dl.sourceforge.net is not http://sourceforge.net so this is beyond my understanding. Bernard Le 6 mars 2018 à 15:58, Mojca Miklavec a écrit : > On 6 March 2018 at 10:47, Joshua Root wrote: >> On 2018-3-6 20:23 , Bernard Desgraupes wrote: >>> So, if I understand correctly, writing: >>> use_autoreconfyes >>> >>> would enough to replace the following: >>> pre-configure { >>>system -W ${build.dir} autoheader >>> } >>> use_autoconfyes >>> >>> Am I right ? >> >> In most cases yes. > > Thank you. > > The port is now committed. > Btw, the master_sites was not set properly. Bernard: I assume you > downloaded the file manually? > > Mojca
Re: Port submission for aidadoc
On 2018-3-7 06:52 , Bernard Desgraupes wrote: > I don’t really understand how the master-sites command works when it says > master_sitessourceforge:projects/aidadoc/files/${version}/ > > The « real » download URL is > https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download > > I ran ‘port distcheck aidadoc’ and it shows a lot of URLs like > http://heanet.dl.sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2 > > but http://heanet.dl.sourceforge.net is not http://sourceforge.net so this is > beyond my understanding. The "real" URL actually redirects to one of sourceforge's mirrors based on geolocation. You can watch this happen with curl: % curl -IL https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download HTTP/1.1 302 Found Server: nginx/1.13.9 Date: Tue, 06 Mar 2018 20:00:47 GMT Content-Type: text/html; charset=UTF-8 Content-Length: 15823 Connection: keep-alive Pragma: no-cache Cache-Control: no-cache X-UA-Compatible: IE=edge,chrome=1 X-Frame-Options: SAMEORIGIN Content-Security-Policy: upgrade-insecure-requests Set-Cookie: VISITOR=76b59e5a-2aa8-4028-8512-eef714df8635; expires="Fri, 03-Mar-2028 20:00:47 GMT"; httponly; Max-Age=31536; Path=/ Set-cookie: sourceforge=0ccfa617566af207bda51c71eebcf1d47ce2b2cdgAJ9cQEoVQVwcmVmc3ECfXEDVQ5fYWNjZXNzZWRfdGltZXEER0HWp7zb+P4NVQNrZXlxBVUkNzZiNTllNWEtMmFhOC00MDI4LTg1MTItZWVmNzE0ZGY4NjM1cQZVDl9jcmVhdGlvbl90aW1lcQdHQdanvNv4/glVA19pZHEIVSBmMjg1ZWRlYTdiZWU0MDdlYTE0ODk3ZjAxZTg3OTViNnEJdS4=; expires=Tue, 19-Jan-2038 03:14:07 GMT; httponly; Path=/; secure Location: https://downloads.sourceforge.net/project/aidadoc/1.4.2/aida-1.4.2-src.tar.bz2?r=&ts=1520366447&use_mirror=excellmedia X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=31536000 HTTP/1.1 302 Found Server: nginx/1.13.9 Date: Tue, 06 Mar 2018 20:00:48 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive content-disposition: attachment; filename="aida-1.4.2-src.tar.bz2" Set-Cookie: sf_mirror_attempt="aidadoc:excellmedia:1.4.2/aida-1.4.2-src.tar.bz2"; expires="Tue, 06-Mar-2018 20:02:48 GMT"; Max-Age=120; Path=/ Location: https://excellmedia.dl.sourceforge.net/project/aidadoc/1.4.2/aida-1.4.2-src.tar.bz2 HTTP/1.1 200 OK Date: Tue, 06 Mar 2018 20:00:49 GMT Server: Apache/2.2.15 (CentOS) Last-Modified: Tue, 04 Oct 2016 18:58:07 GMT ETag: "317d7b-18801-53e0ea4172dc0" Accept-Ranges: bytes Content-Length: 100353 Connection: close Content-Type: application/octet-stream - Josh
Buildbot idea(s) for GSOC
Dear Umesh, In case we would get any good students in that area, I would be grateful if someone would work on improving buildbot core & front-end in close collaboration with mentors directly from buildbot. I added this one idea on the list, but it needs some polishing: https://trac.macports.org/wiki/SummerOfCode#Buildbotideas However, in order to attract potential students, we would likely need to add a few suitable keywords to our "description", like perhaps "frontend". But we would also need to make it easier for such students who end up on our site to actually spot such projects without browsing through the full list. Buildbot participated in GSOC before, but did not apply this year. They would be willing to mentor and we really need some features implemented if we want to go for buildbot 1.0 setup one day. (That said, I would find it ok even if some project from buildbot mentorship is not strictly macports-oriented.) Another project we could put on the list would be figuring out how to start clean VMs for each build, but that might be tricky and the student would need to be able to figure that out on his own. Apparently buildbot supports that for Linux. Mojca
Re: request for port create command, to build a portfile from a URL
On 6 Mar 2018, at 16:19, Joshua Root wrote: > On 2018-3-7 01:58 , Ken Cunningham wrote: >> >> port create URL >> Might make things faster and easier for people to get started and up and >> running. > There's a fairly basic tool called portfile-gen in contrib. I took a bit to find it, so here's the link https://github.com/macports/macports-contrib/tree/master/portfile-gen. I learned to write a portfile following some article in the wild, then I went through the whole guide, landed eventually in the mailing list. While portfile-gen might help (homebrew has a similar feature), an *overview* of how to write a portfile is much needed.
Re: request for port create command, to build a portfile from a URL
On 2018-03-06, at 7:19 AM, Joshua Root wrote: > > There's a fairly basic tool called portfile-gen in contrib. Improvements > are certainly welcome. That is indeed a step towards what I was thinking of. I'll look at this. Ken
Re: request for port create command, to build a portfile from a URL
On 2018-03-06 23:00, db wrote: > [...] an *overview* of how to write a portfile is much needed. Isn't this what this chapter in the guide is supposed to provide? https://guide.macports.org/#development Rainer
Re: Buildbot idea(s) for GSOC
I think Travis already does most of this. You just a skeleton yml file and insert the port name as an env var On Tue, Mar 6, 2018 at 13:52 Mojca Miklavec wrote: > Dear Umesh, > > In case we would get any good students in that area, I would be > grateful if someone would work on improving buildbot core & front-end > in close collaboration with mentors directly from buildbot. > > I added this one idea on the list, but it needs some polishing: > https://trac.macports.org/wiki/SummerOfCode#Buildbotideas > > However, in order to attract potential students, we would likely need > to add a few suitable keywords to our "description", like perhaps > "frontend". But we would also need to make it easier for such students > who end up on our site to actually spot such projects without browsing > through the full list. > > Buildbot participated in GSOC before, but did not apply this year. > They would be willing to mentor and we really need some features > implemented if we want to go for buildbot 1.0 setup one day. (That > said, I would find it ok even if some project from buildbot mentorship > is not strictly macports-oriented.) > > > Another project we could put on the list would be figuring out how to > start clean VMs for each build, but that might be tricky and the > student would need to be able to figure that out on his own. > Apparently buildbot supports that for Linux. > > Mojca >
Re: Port submission for aidadoc
Dear Joshua, thank you for the insight. Everything is clear now and I discover the -I and -L options of curl by the way, very handy ! I thought that maybe the download issues encountered by Mojca are a result of the recent DoS attack on Sourceforge (see https://twitter.com/sfnet_ops) which may have affected the mirrors too. Just a guess. Cheers, Bernard Le 6 mars 2018 à 21:04, Joshua Root a écrit : > On 2018-3-7 06:52 , Bernard Desgraupes wrote: >> I don’t really understand how the master-sites command works when it says >> master_sitessourceforge:projects/aidadoc/files/${version}/ >> >> The « real » download URL is >> https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download >> >> I ran ‘port distcheck aidadoc’ and it shows a lot of URLs like >> http://heanet.dl.sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2 >> >> but http://heanet.dl.sourceforge.net is not http://sourceforge.net so this >> is beyond my understanding. > > The "real" URL actually redirects to one of sourceforge's mirrors based > on geolocation. You can watch this happen with curl: > > % curl -IL > https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download > HTTP/1.1 302 Found > Server: nginx/1.13.9 > Date: Tue, 06 Mar 2018 20:00:47 GMT > Content-Type: text/html; charset=UTF-8 > Content-Length: 15823 > Connection: keep-alive > Pragma: no-cache > Cache-Control: no-cache > X-UA-Compatible: IE=edge,chrome=1 > X-Frame-Options: SAMEORIGIN > Content-Security-Policy: upgrade-insecure-requests > Set-Cookie: VISITOR=76b59e5a-2aa8-4028-8512-eef714df8635; expires="Fri, > 03-Mar-2028 20:00:47 GMT"; httponly; Max-Age=31536; Path=/ > Set-cookie: > sourceforge=0ccfa617566af207bda51c71eebcf1d47ce2b2cdgAJ9cQEoVQVwcmVmc3ECfXEDVQ5fYWNjZXNzZWRfdGltZXEER0HWp7zb+P4NVQNrZXlxBVUkNzZiNTllNWEtMmFhOC00MDI4LTg1MTItZWVmNzE0ZGY4NjM1cQZVDl9jcmVhdGlvbl90aW1lcQdHQdanvNv4/glVA19pZHEIVSBmMjg1ZWRlYTdiZWU0MDdlYTE0ODk3ZjAxZTg3OTViNnEJdS4=; > expires=Tue, 19-Jan-2038 03:14:07 GMT; httponly; Path=/; secure > Location: > https://downloads.sourceforge.net/project/aidadoc/1.4.2/aida-1.4.2-src.tar.bz2?r=&ts=1520366447&use_mirror=excellmedia > X-Content-Type-Options: nosniff > Strict-Transport-Security: max-age=31536000 > > HTTP/1.1 302 Found > Server: nginx/1.13.9 > Date: Tue, 06 Mar 2018 20:00:48 GMT > Content-Type: text/html; charset=UTF-8 > Connection: keep-alive > content-disposition: attachment; filename="aida-1.4.2-src.tar.bz2" > Set-Cookie: > sf_mirror_attempt="aidadoc:excellmedia:1.4.2/aida-1.4.2-src.tar.bz2"; > expires="Tue, 06-Mar-2018 20:02:48 GMT"; Max-Age=120; Path=/ > Location: > https://excellmedia.dl.sourceforge.net/project/aidadoc/1.4.2/aida-1.4.2-src.tar.bz2 > > HTTP/1.1 200 OK > Date: Tue, 06 Mar 2018 20:00:49 GMT > Server: Apache/2.2.15 (CentOS) > Last-Modified: Tue, 04 Oct 2016 18:58:07 GMT > ETag: "317d7b-18801-53e0ea4172dc0" > Accept-Ranges: bytes > Content-Length: 100353 > Connection: close > Content-Type: application/octet-stream > > - Josh
Re: Port submission for aidadoc
I'd set a no cache flag so you don't get lots of cookie and cache garbage > On Mar 6, 2018, at 22:15, Bernard Desgraupes wrote: > > Dear Joshua, > > thank you for the insight. Everything is clear now and I discover the -I and > -L options of curl by the way, very handy ! > > I thought that maybe the download issues encountered by Mojca are a result of > the recent DoS attack on Sourceforge (see https://twitter.com/sfnet_ops) > which may have affected the mirrors too. Just a guess. > > Cheers, > Bernard > >> Le 6 mars 2018 à 21:04, Joshua Root a écrit : >> >>> On 2018-3-7 06:52 , Bernard Desgraupes wrote: >>> I don’t really understand how the master-sites command works when it says >>> master_sitessourceforge:projects/aidadoc/files/${version}/ >>> >>> The « real » download URL is >>> https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download >>> >>> I ran ‘port distcheck aidadoc’ and it shows a lot of URLs like >>> http://heanet.dl.sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2 >>> >>> but http://heanet.dl.sourceforge.net is not http://sourceforge.net so this >>> is beyond my understanding. >> >> The "real" URL actually redirects to one of sourceforge's mirrors based >> on geolocation. You can watch this happen with curl: >> >> % curl -IL >> https://sourceforge.net/projects/aidadoc/files/1.4.2/aida-1.4.2-src.tar.bz2/download >> HTTP/1.1 302 Found >> Server: nginx/1.13.9 >> Date: Tue, 06 Mar 2018 20:00:47 GMT >> Content-Type: text/html; charset=UTF-8 >> Content-Length: 15823 >> Connection: keep-alive >> Pragma: no-cache >> Cache-Control: no-cache >> X-UA-Compatible: IE=edge,chrome=1 >> X-Frame-Options: SAMEORIGIN >> Content-Security-Policy: upgrade-insecure-requests >> Set-Cookie: VISITOR=76b59e5a-2aa8-4028-8512-eef714df8635; expires="Fri, >> 03-Mar-2028 20:00:47 GMT"; httponly; Max-Age=31536; Path=/ >> Set-cookie: >> sourceforge=0ccfa617566af207bda51c71eebcf1d47ce2b2cdgAJ9cQEoVQVwcmVmc3ECfXEDVQ5fYWNjZXNzZWRfdGltZXEER0HWp7zb+P4NVQNrZXlxBVUkNzZiNTllNWEtMmFhOC00MDI4LTg1MTItZWVmNzE0ZGY4NjM1cQZVDl9jcmVhdGlvbl90aW1lcQdHQdanvNv4/glVA19pZHEIVSBmMjg1ZWRlYTdiZWU0MDdlYTE0ODk3ZjAxZTg3OTViNnEJdS4=; >> expires=Tue, 19-Jan-2038 03:14:07 GMT; httponly; Path=/; secure >> Location: >> https://downloads.sourceforge.net/project/aidadoc/1.4.2/aida-1.4.2-src.tar.bz2?r=&ts=1520366447&use_mirror=excellmedia >> X-Content-Type-Options: nosniff >> Strict-Transport-Security: max-age=31536000 >> >> HTTP/1.1 302 Found >> Server: nginx/1.13.9 >> Date: Tue, 06 Mar 2018 20:00:48 GMT >> Content-Type: text/html; charset=UTF-8 >> Connection: keep-alive >> content-disposition: attachment; filename="aida-1.4.2-src.tar.bz2" >> Set-Cookie: >> sf_mirror_attempt="aidadoc:excellmedia:1.4.2/aida-1.4.2-src.tar.bz2"; >> expires="Tue, 06-Mar-2018 20:02:48 GMT"; Max-Age=120; Path=/ >> Location: >> https://excellmedia.dl.sourceforge.net/project/aidadoc/1.4.2/aida-1.4.2-src.tar.bz2 >> >> HTTP/1.1 200 OK >> Date: Tue, 06 Mar 2018 20:00:49 GMT >> Server: Apache/2.2.15 (CentOS) >> Last-Modified: Tue, 04 Oct 2016 18:58:07 GMT >> ETag: "317d7b-18801-53e0ea4172dc0" >> Accept-Ranges: bytes >> Content-Length: 100353 >> Connection: close >> Content-Type: application/octet-stream >> >> - Josh >