Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 22218 - Ebuild for dev-libs/mm is out of date - update to 1.3.0
Summary: Ebuild for dev-libs/mm is out of date - update to 1.3.0
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Donny Davies (RETIRED)
URL: http://www.ossp.org/pkg/lib/mm/
Whiteboard:
Keywords: EBUILD
Depends on:
Blocks:
 
Reported: 2003-06-04 12:07 UTC by gentoo
Modified: 2003-06-18 14:42 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Sample ebuild for MM 1.3.0 - based on ebuild for MM 1.2.1 (mm-1.3.0.ebuild,814 bytes, text/plain)
2003-06-04 12:10 UTC, gentoo
Details
DIFF between ebuild for MM 1.2.1 and MM 1.3.0 (mm.ebuild.diff,262 bytes, patch)
2003-06-18 11:22 UTC, gentoo
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description gentoo 2003-06-04 12:07:20 UTC
Version 1.3.0 of 'mm' has been out for a few months now.  'mm' is a dependency of 
apache and is used for mod_ssl, among other things. 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 gentoo 2003-06-04 12:10:22 UTC
Created attachment 12789 [details]
Sample ebuild for MM 1.3.0 - based on ebuild for MM 1.2.1

No ebuild changes since version 1.2.1.
Comment 2 Donny Davies (RETIRED) gentoo-dev 2003-06-17 19:24:58 UTC
if you didnt change anything than why are you attaching anything at all?

you really dont think we just copy and paste submitted to the bugzilla
and then dump it right into CVS do you?!

in the future, please attach either in patch generated with diff -u
or if it's really small, just paste the text of said, thusly
generated patch, directly into the body of the bug report.
this will allow your report to be processed much faster.
Comment 3 gentoo 2003-06-17 23:49:03 UTC
Donny (woodchip): 
 
Whoa there.  Let me rephrase my request:  
 
"Please create a new ebuild for MM 1.3.0, based on the existing ebuild for MM 1.2.1, with no 
other changes.  This new ebuild should be named 'mm-1.3.0.ebuild' and placed in the '/dev-libs/' 
directory inside the portage tree." 
 
I didn't ask for you (or anyone) to directly copy my sample ebuild out of bugzilla and into the 
CVS tree.  That would be dumb.  This is why I clearly put the word "Sample" in the subject of 
that attachment.  
 
You're absolutely right - nothing changes for this version.  You inspected the ebuild and you 
obviously noticed that there was nothing version-specific inside the ebuild.  The only thing I am 
asking you to do is to go into the proper CVS directory, and make a COPY of the existing 
ebuild, name it 'mm-1.3.0.ebuild', then create the digest for this new ebuild.  
 
If there were any small changes to make, then I would have felt justified in attaching a diff.  In 
this circumstance, however, the diff produces zero lines.  If you want me to copy+paste *that* 
into a bugzilla comment, or make an attachment for a zero-byte file, I would be happy to do so.  
 
If you'd like me to make the resolution of this bug more clear for you, then I can give you the 
exact shell commands that *I* would use in my local portage directory to make a copy of this 
ebuild for the new version of the library, so you can understand my perspective as a user.  I 
would do something like this:  
 
# cd /usr/portage/dev-libs/mm/ 
# cp mm-1.2.1.ebuild mm-1.3.0.ebuild 
# ebuild mm-1.3.0.ebuild digest 
 
Just to make sure that you don't interpret this the wrong way, I'm not suggesting that you 
copy+paste these commands directly into any shell window unless you have inspected them 
and feel confident that they won't mess up your system or CVS directory.  You're a Gentoo 
developer so obviously you're smart enough know how to update an ebuild properly.  There's 
probably a whole lot more than just copying two files -- I would guess that some CVS 
commands are involved, but since I'm just a dumb user, not a Gentoo developer with CVS 
access, I don't know what those commands are, and if I did, I wouldn't have the authority to 
issue them.  That is why I filed the bug report in the first place.   
 
If you have a legitimate objection to updating this library to the latest available version, then let's 
address it here and now.  But if you're just trying to be difficult or avoid the work, then you'd be 
better off assigning this bug to somebody else who can resolve it.  There is absolutely no place 
in this community for snippy, emotional responses to a user-submitted bug.  Gentoo has built 
its strength on being responsive to the user community and tracking the most current versions 
of software, and neither you nor I should allow anything to compromise this.  
 
Please advise. 
 
Regards, 
-- Matt   
 
 
Comment 4 Donny Davies (RETIRED) gentoo-dev 2003-06-18 09:38:13 UTC
If you havent changed anything, then do not post an attachment.  Why would
you post an attachment when you havent changed anything at all?  Just
for the heck of it?

I gave you advice on how developers would like to see things in the bugzilla.
If you do not appreciate information on how to get a "submission" processed
more quickly in the future, then well, what can I tell you.

Have a nice day.
Comment 5 gentoo 2003-06-18 11:22:39 UTC
Created attachment 13478 [details, diff]
DIFF between ebuild for MM 1.2.1 and MM 1.3.0

Here is a diff which can be used on the forthcoming ebuild for
dev-libs/mm-1.3.0.ebuild.  Notice there is one line changed.
Comment 6 gentoo 2003-06-18 11:34:52 UTC
Donny, 
 
I have to correct myself.  In my last comment I said there was no difference in the file.  
This was incorrect -- I did change one line.  Had you actually run the 'diff' command on 
the file I originally attached, you would have seen this change: 
 
-SLOT="1.2" 
+SLOT="1.3" 
 
I have also attached a diff, as you have requested.  In the future, I will try to attach 
only diffs or patches to future bug submissions that get assigned to you.  I'm sorry 
that my earlier attachment was an obstacle for you.  My intent was not to mislead 
you.  Since it appears to have kept you from creating this new ebuild, I have marked 
that attachment as obsolete.  You can now use the new attachment to help create 
this new ebuild. 
 
If you need any more information from me, please don't hesitate to ask.  I am willing 
to work with you to test this ebuild and prepare it for release.  I have used this exact 
ebuild on my main Gentoo Linux web server at work (running apache, mod_php, and 
mm) and it works flawlessly. 
 
If you are unwilling to create this new ebuild, then reassign this bug to someone who 
can resolve it without griping.  If you do not appreciate "submissions" from users, or 
unwilling to work with users in a civil manner, then perhaps you should reconsider your 
status as a Gentoo developer. 
 
Regards, 
-- Matt 
 
Comment 7 Donny Davies (RETIRED) gentoo-dev 2003-06-18 14:12:24 UTC
This ebuild is broken because you have not used a correct SLOT.
If you would have simply posted an patchfile in the first place
(ok so you didnt know before, but now you do) then I would have
immediately spotted it.

In your rush to impress us all with your cleverly disguised,
condescending remarks, the only "clear and concise" thing
you've managed to communicate here, is, well, that you're a
jerk and apparently it is your belief that free software
developers and the volunteers on this project are open
targets to be ridiculed and harassed.  I tried to help
you too, that's the sad part.

Have a nice life, Matt.
Comment 8 gentoo 2003-06-18 14:42:31 UTC
Thank you for creating the new ebuild.  I will test it. 
 
Regards, 
-- Matt