Hi,
In light of the mass deletion of many orphaned as well as
not-really-orphaned packages, it would be nice if there were a way to
get a log of AUR activity so that users other than just a package's
maintainers can see that a package disappeared at some given point.
It was also mentioned that
On Wed, Aug 12, 2015 at 5:09 PM, Giancarlo Razzolini
grazzol...@gmail.com wrote:
For packages not migrated, I don't think there is a repo there.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Git_repository ?
Em 12-08-2015 11:54, Mark Laws escreveu:
In light of the mass deletion of many orphaned as well as
not-really-orphaned packages
They were really orphaned. And it was warned that orphaned packages
would be deleted on Aug 8th.
, it would be nice if there were a way to
get a log of AUR activity
On Thu, Aug 13, 2015 at 12:20 AM, Karol Blazewicz
karol.blazew...@gmail.com wrote:
https://wiki.archlinux.org/index.php/Arch_User_Repository#Git_repository ?
I was wondering if there was something like this. Thanks!
Cheers,
Mark Laws
--
|v\ /\ |\ | |_ /\ \^| //
Wed, 12 Aug 2015 12:09:51 -0300
Giancarlo Razzolini grazzol...@gmail.com:
They were really orphaned. And it was warned that orphaned packages
would be deleted on Aug 8th.
nitpick
The announced (and executed) deletion was about stale AUR3 metadata
(migrated packages that weren't 'git push'ed)
On Thu, 13 Aug 2015 at 04:20 Doug Newgard scim...@archlinux.info wrote:
On Wed, 12 Aug 2015 15:07:57 -0300
Giancarlo Razzolini grazzol...@gmail.com wrote:
Em 12-08-2015 15:01, Doug Newgard escreveu:
On the contrary, this is exactly the mechanism for that. You disown a
package
so that
On Thu, 13 Aug 2015 14:01 Sam S. sml...@gmail.com wrote:
Note that we do keep the Git repositories of deleted packages,
so if anybody wants to maintain the package later, he can always clone
the repository of the deleted package, fix the package and simply push
it afterwards
Can you
Note that we do keep the Git repositories of deleted packages,
so if anybody wants to maintain the package later, he can always clone
the repository of the deleted package, fix the package and simply push
it afterwards
Can you give some details on that?
For example the libtiff4 package
W dniu 11.08.2015 o 20:00, Jens Adam pisze:
They didn't disappear - they got deleted.
You got at least two mails informing about the AUR v4 reorganisation
and pending deletion of not migrated packages, the mailing lists were
full of it, plus there had been a prominent notice on the (old) AUR
Le 12 août 2015 07:51:28 GMT+02:00, Justin Dray jus...@dray.be a écrit :
On Wed, 12 Aug 2015 at 15:37 Rob McCathie korr...@gmail.com wrote:
On 12/08/15 13:49, Doug Newgard wrote:
In my case, I have some that I'm actively trying to get maintainers
for; in the mean time, I'm looking after
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 14 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 16 packages missing signoffs
* 0 packages older than 14
Em 12-08-2015 12:42, Jens Adam escreveu:
Our main issue here is about orphaned PKGBUILDs that got manually
deleted after the transition was over.
But these were migrated to and then orphaned on the new AUR right? I
don't think that it was wrong to hide these when the subdomain
migrated on Aug
W dniu 11.08.2015 o 20:00, Jens Adam pisze:
They didn't disappear - they got deleted.
You got at least two mails informing about the AUR v4 reorganisation
and pending deletion of not migrated packages,
Where those emails sent directly to each maintainer's email, or to AUR
mailing list only?
Wed, 12 Aug 2015 18:31:54 +0200
Maciej Sieczka msiec...@sieczka.org:
W dniu 11.08.2015 o 20:00, Jens Adam pisze:
They didn't disappear - they got deleted.
You got at least two mails informing about the AUR v4
reorganisation and pending deletion of not migrated packages,
Where those
Wed, 12 Aug 2015 13:54:31 -0300
Giancarlo Razzolini grazzol...@gmail.com:
I don't think that it was wrong to hide these when the subdomain
migrated on Aug 8th.
That wasn't what happened. Read the thread(s) again - a single TU went
around and deleted a bunch of freshly orphaned packages,
* Maciej Sieczka msiec...@sieczka.org (Wed, 12 Aug 2015 18:31:54
+0200):
W dniu 11.08.2015 o 20:00, Jens Adam pisze:
They didn't disappear - they got deleted.
You got at least two mails informing about the AUR v4
reorganisation and pending deletion of not migrated packages,
Where those
Em 12-08-2015 06:05, Lukas Fleischer escreveu:
Maybe you could at least add yourself as a co-maintainer for now. Or if
you are really *actively* trying to find new maintainers, it probably
wouldn't hurt if you were listed as a maintainer until you find
somebody.
I had some dependencies issues
On Wed, Aug 12, 2015 at 11:05 AM, Lukas Fleischer
lfleisc...@archlinux.org wrote:
Wikipedia defines orphan as
[...] a child whose parents are dead or have abandoned them
permanently
...but new parents may want to adopt them, if given the opportunity.
Deleting *long-time* orphaned
On Wed, 12 Aug 2015 11:05:08 +0200
Lukas Fleischer lfleisc...@archlinux.org wrote:
I consider this a slight abuse of the orphan/disown functionality.
Oh, and I also wanted to point out that this is just one use-case. There are
others, such as the v8 package that was recently dropped from
On Wed, 12 Aug 2015 11:05:08 +0200
Lukas Fleischer lfleisc...@archlinux.org wrote:
I consider this a slight abuse of the orphan/disown functionality.
Wikipedia defines orphan as
[...] a child whose parents are dead or have abandoned them
permanently.
In my opinion, orphan packages
So maybe we need to improve the way changing maintainership
works. Having a Give up for adoption button (that keeps the current
maintainer while allowing anybody to adopt the package) in addition to
Disown is one possibility.
What is the point of the disown button then, if it does the same
On Wed, 12 Aug 2015 15:07:57 -0300
Giancarlo Razzolini grazzol...@gmail.com wrote:
Em 12-08-2015 15:01, Doug Newgard escreveu:
On the contrary, this is exactly the mechanism for that. You disown a
package
so that someone else can adopt it. Why else would you disown a package?
Let me
Em 12-08-2015 14:10, Jens Adam escreveu:
That wasn't what happened. Read the thread(s) again - a single TU went
around and deleted a bunch of freshly orphaned packages, nothing to do
with the migration.
I really don't see the issue here, even if is this that happened. They
were orphaned,
On Wed, 12 Aug 2015 14:17:12 -0300
Giancarlo Razzolini grazzol...@gmail.com wrote:
Em 12-08-2015 14:10, Jens Adam escreveu:
That wasn't what happened. Read the thread(s) again - a single TU went
around and deleted a bunch of freshly orphaned packages, nothing to do
with the migration.
I
On Wed, 12 Aug 2015 14:54:56 -0300
Giancarlo Razzolini grazzol...@gmail.com wrote:
We already have a mechanism for disowning a package and allowing
others to maintain it without deleting it. It's called orphaning.
This is not the mechanism for that, and it is the reason why the
Em 12-08-2015 15:01, Doug Newgard escreveu:
On the contrary, this is exactly the mechanism for that. You disown a package
so that someone else can adopt it. Why else would you disown a package?
Let me rephrase it. Disowning a package isn't the mechanism for allowing
others to maintain a
On Thu, 13 Aug 2015 at 03:17 Giancarlo Razzolini grazzol...@gmail.com
wrote:
Em 12-08-2015 14:10, Jens Adam escreveu:
That wasn't what happened. Read the thread(s) again - a single TU went
around and deleted a bunch of freshly orphaned packages, nothing to do
with the migration.
I really
Em 12-08-2015 14:42, Justin Dray escreveu:
Perhaps seeing active comments or that the packages had to have been
updated within month since everything was cleared for AUR4?
Comments aren't the best way. A package can work so well as to not have
any comments for a long time. Or is simple enough
Em 12-08-2015 14:21, Justin Dray escreveu:
But by 'hidden' it also deletes all comments and votes, and stops
people being able to search for the package, see that it isn't
maintained and picking it up.
Well, the TU could have waited, I give you that.
Almost all of my packages have become
On Thu, 13 Aug 2015 03:36 Giancarlo Razzolini grazzol...@gmail.com wrote:
Em 12-08-2015 14:21, Justin Dray escreveu:
But by 'hidden' it also deletes all comments and votes, and stops
people being able to search for the package, see that it isn't
maintained and picking it up.
Well, the TU
30 matches
Mail list logo
